#11801 Please retarget f39-toolchain to rawhide/f40
Closed: Fixed 2 years ago by humaton. Opened 2 years ago by fweimer.

I hope this is the last request of this kind.

It would be nice to have Koji builder support for current rawhide with the instrumented gcc/redhat-rpm-config packages, to support: https://fedoraproject.org/wiki/Changes/PortingToModernC

As the name implies, f39-toolchain currently into Fedora 39. It's okay to rename the tag/build target, we don't need the Fedora 39 support anymore.


Metadata Update from @phsmoura:
- Issue tagged with: high-gain, high-trouble, ops

2 years ago

Hi, so ofcourse I misread the ticket and created f40-toolchain tag&target

$ koji taginfo f40-toolchain
Tag: f40-toolchain [78993]
Arches: i686 x86_64 aarch64 ppc64le s390x
Groups: appliance-build, build, livecd-build, livemedia-build, srpm-build
Tag options:
  mock.new_chroot : 1          [f40]
  mock.package_manager : 'dnf' [f40]
  sidetag_rpm_macros_allowed : '_with_bootstrap' [f40-build]
Targets that build into this tag:
  f40-toolchain (f40-toolchain, no active repo)
This tag is a buildroot for one or more targets
Current repo: no active repo
Targets that build from this tag:
  f40-toolchain
Inheritance:
  0    .... f40-build [71278] 

Also tagged the latest builds from f39-toolchain to the new tag

$ koji list-tagged f40-toolchain
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
gcc-13.1.1-4.implicits.6.fc39             f40-toolchain         fweimer
redhat-rpm-config-255-2.implicits.4.fc39  f40-toolchain         fweimer

Is it okay with you?

Also, I have one question regarding the time frame for the change. Do you think you will be able to make it for f40? I am asking because we can add it to our branching notes to create a new target while branching a new release.

Yes, it's fine, thanks. Will do some builds later today.

Metadata Update from @humaton:
- Issue assigned to humaton

2 years ago

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog