#12626 Create Fedora 42 Beta candidates
Closed: Fixed a month ago by jnsamyak. Opened a month ago by kparal.

Time for a Fedora 42 Beta candidate compose. Please include:

Blockers

Releng commands

Untag all previous builds:

koji list-tagged f42-compose --quiet | awk '{print $1}' | xargs -rt koji untag-pkg f42-compose

and then tag the new builds:

blockers=(
anaconda-42.27.3-1.fc42 anaconda-webui-26-1.fc42
gcc-15.0.1-0.9.fc42
)
fes=(
)
koji tag-build f42-compose ${blockers[@]} ${fes[@]}

Metadata Update from @patrikp:
- Issue assigned to patrikp

a month ago

The PR for the fedora-beta.conf file can be found here:
https://pagure.io/pungi-fedora/pull-request/1456

Reviews are welcome.

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

a month ago

RC - 1.1 failed due to ambiguities in the fedora-beta config, I have fired a new 1.2 compose with the changes, let's see how that goes

For some context, I tried re-running the ./create-candidate-configs.py script this morning and now it looks identical to what Samyak created.
So it's certain that it was some human error on my part, e.g. running it on rawhide branch before actually switching to f42 or something like that. I'm not sure exactly what happened.

Should it not be synced to here (https://dl.fedoraproject.org/pub/alt/stage/)?

Okay so I was debugging and found out that the compose synced properly with the release candidate script and the correct ftpsync as the owner. However, there was an issue with directory permissions (drwxr-s---.). I’ve enabled the necessary permissions, and the compose can now be found at: https://dl.fedoraproject.org/pub/alt/stage/42_Beta-1.2/

Requesting another compose. Please include:

Blockers

(Not sure if it is clear, but we need that very lorax to build the RC images. I don't know if just including it in the request means it will also get used in the build process, so highlighting it just to make sure.)

(Not sure if it is clear, but we need that very lorax to build the RC images. I don't know if just including it in the request means it will also get used in the build process, so highlighting it just to make sure.)

If the process is done and the tag repo is regenerated before the compose, it will be used.

Unfortunately, just including the new lorax in the override repo really is not enough for it to be used to build the installer images, it seems. See the log and mock config at https://koji.fedoraproject.org/koji/taskinfo?taskID=130125658 - that's the Everything netinst build for 1.3. You can see it used lorax 42.5, not 42.6. It seems that the mock config just has the f42 buildroot repo in it, it does not have the f42-override repo in it.

So we need a 1.4. I have sent a stable push request to get lorax pushed stable. Once that is done, do a wait-repo to make really sure it is in the buildroot, then please run a new compose with no override packages.

RC-1.4 was fired, it's running, once it is finished, I'll put another comment for confirmation!

Metadata Update from @jnsamyak:
- Assignee reset

a month ago

Beta-1.4 is a GO, so closing this request now.

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

a month ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog