There is documentation somewhere how to update those branches to have fedora:fedora/41/x86_64/silverblue point to fedora:fedora/41/x86_64/updates/silverblue but I can't find them right now.

Found it: https://docs.pagure.org/releng/sop_composing_fedora.html?highlight=ostree#changes-for-final-release

Note that the create part of those instructions will have to be skipped as those refs already exists.

I vaguely remember that we had moved that to a script somewhere but I don't remember where.

https://pagure.io/releng/issue/12072

So it's mainly https://pagure.io/releng/blob/main/f/scripts/update_ostree_refs.sh but WE SHOULD NOT RUN THIS AS IS as this will delete the update refs that we have right now.

Or maybe we should just run this and forget about the history from this weekend.

We'll have to trigger a new compose to get fresh Atomic Desktops builds.

The docs.pagure.org/releng is the 'old' docs. ;( Apparently this didn't make it into the new ones somehow. :(

So, that script, but with lines 19 and 21 commented/deleted, as we already have the updates ref, we just need to point the main one to it?

You mean another updates compose? Or ?

I'm afraid we got to a point where both have history and I don't know what we should do.

Well, we definitely cannot do another base 41 compose. We have already staged the release and switched everything.

We can (and will do) updates composes.

There shouldn't be anymore history on the base repo after the last compose on thursday... updates should have taken over after that, so I am not sure where we have history for both now?

OK, so let's keep the script as is and run it. This will "rewind" the updates branch to the state of the stable one but you're right that it does not matter and the next compose will update "both".

ok. Should I do a new compose right after (takes 1.5hr or so)?

Ideally yes, so that we get the branch updated immediately

And as always thanks a lot for helping. I realized this late :(

Well, it's only been this way/mattered since friday. ;)

So, I ran the script, will do a f41 compose after this f41-updates-testing finishes.

We need to add this to our stage release doc. So, lets keep this open for that...

Looking good now:

Silverblue  41               41-updates       41-testing
x86_64      41.20241028.1    41.20241028.1    41.20241028.0
aarch64     41.20241028.1    41.20241028.1    41.20241028.0
ppc64le     41.20241028.1    41.20241028.1    41.20241028.0

Kinoite     41               41-updates       41-testing   
x86_64      41.20241028.1    41.20241028.1    41.20241028.0
aarch64     41.20241028.1    41.20241028.1    41.20241028.0
ppc64le     41.20241028.1    41.20241028.1    41.20241028.0

Sericea     41               41-updates       41-testing   
x86_64      41.20241028.1    41.20241028.1    41.20241028.2
aarch64     41.20241028.1    41.20241028.1    41.20241028.2

Onyx        41               41-updates       41-testing   
x86_64      41.20241028.1    41.20241028.1    41.20241028.0

Thanks!

Great!

Can you link me to the new docs? Is it https://docs.fedoraproject.org/en-US/infra/release_guide/final_release/ ?

yes, and my pr is:

https://pagure.io/infra-docs-fpo/pull-request/326