#10115 Side tag for Python 3.10
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by thrnciar.

  • For which release?
    35
  • Name of the side tag? (Generally fxx-pkg)
    f35-python
  • Number of builds that are expected in the side tag?
    thousands, ~4k unique packages
  • How long do you need the side tag?
    approximately 1-2 months
  • Any extra information?
    We need to disable mock's bootstrap option in order to prevent broken dependencies of dnf in the bootstrap chroot. A releng member can do that via:
koji edit-tag <name> -x 'mock.use_bootstrap=0'

We are doing this as part of this Python 3.10 Change. I'd like to kindly ask you to create the side tag before 25th of May, so we can start to rebuild packages as soon as 2nd beta of Python 3.10 is released. Thank you.


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

2 years ago

f35-python has been created:

$ koji add-tag f35-python --parent f35-build --arches 'armv7hl i686 x86_64 aarch64 ppc64le s390x'
$ koji add-target f35-python f35-python
$ koji edit-tag f35-python -x 'mock.use_bootstrap=0'

You can do builds with:

$ fedpkg build –target=f35-python
Let us know when you are done and we will move all the builds into f35.

Metadata Update from @mohanboddu:
- Issue tagged with: sidetarget

2 years ago

Should we enable autosigning on f35-python to avoid problems like #10134 ?

Yes please. We expect the side tag to be open for a while and signing on the fly will speed up the merge significantly. Thanks for the offer.

So, i finally just got to this. ;( So everything after this will be signed... but we need to likely re-tag everything into the side tag to make autosign resign it. we should do that and confirm all is signed before we merge it.

When I attempt to re-tag things, I get:

FAILED: TagError: build retext-7.1.0-6.fc35 already tagged (f35-python)

Do I tag them to f35-signing-pending or something similar?

nope, you have to either:
koji untag-pkg f35-python foo; koji tag-pkg f35-python foo

or

koji tag-pkg f35-python foo --force
(but that might require admin... not sure)

$ koji tag f35-python retext-7.1.0-6.fc35 --force
Created task 69392316
Watching tasks (this may be safely interrupted)...
69392316 tagBuild (noarch): free
69392316 tagBuild (noarch): free -> closed
  0 free  0 open  1 done  0 failed

69392316 tagBuild (noarch) completed successfully

How can I verify the build is (being) signed?

If I verify, shall I retag all the tagged packages myself?

$ koji list-tagged f35-python --latest --sigs
...
9867c58f retext-7.1.0-6.fc35.noarch
9867c58f retext-7.1.0-6.fc35.src
...

I guess that works, right?

I plan to run:

koji tag f35-python $(koji list-tagged f35-python --latest | cut -f1 -d' ') --force --nowait

But I'll wait for confirmation that it is OK for me to do it.

Yep. should be fine. :) Go for it.

All the builds we have now appear to be signed. Thanks.

Hit the merge button please.

gnurardio is still building, but we can tag that in later.

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

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog
Attachments 2
Attached 2 years ago View Comment
Attached 2 years ago View Comment