releng

Clone
Source Code
GIT

#12212 Some of my packages on the F41 "need rebuild" list were retired for Rawhide in March 2024
Opened 10 months ago by music. Modified 10 months ago

Open
Close issue as:
Can't Fix Duplicate Fixed Get back later Grooming Insufficient data Invalid It's all good taiga upstream Fixed with Explanation
  • Describe the issue

Three of the packages under music in https://kojipkgs.fedoraproject.org/mass-rebuild/f41-need-rebuild.html were retired for Rawhide in March 2024.

  • libmetalink and parsertl14 are retired in F41, active in F40/F39/EPEL9
  • rust-libcramjam0.2 has always been an F39-only compat package; it was retired in F41 as soon as it was requested, and was never built there

(The other packages on the list under music, python-pybv and python-starlette are also on https://kojipkgs.fedoraproject.org/mass-rebuild/f41-failures.html, which I assume is normal.)

This does not appear to be an example of https://pagure.io/releng/issue/12192 because the packages in question were retired in March 2024.

After a quick triage in the “Fedora Release Engineering” Matrix channel, @kevin asked me to file an issue here.

  • When do you need this? (YYYY/MM/DD)

This doesn’t seem to affect me personally, but it would seem wise to investigate this before the F41 Final Freeze.

  • When is this no longer needed or useful? (YYYY/MM/DD)

Useful indefinitely.

  • If we cannot complete your request, what is the impact?

If this issue reflects a defect in package retirement or in the enumeration of packages that need rebuilding, and if it is not investigated, then that defect may continue to affect other packages in F41 and in future releases.

Metadata Update from @humaton:
- Issue tagged with: high-gain, investigation, medium-trouble
10 months ago

Piggybacking on this, https://src.fedoraproject.org/rpms/python39-zstd-epel was retired last year from Rawhide and somehow is still tagged into F41 and thus shows up in the 'needs rebuild' report

Ok I looked at the examples you mentioned (libmetalink); These weren't properly retired because I can see these are not blocked in koji properly :(

I think the the reason for this is https://pagure.io/releng/issue/12192#comment-920461 or maybe not :/

Tue Feb 13 21:44:19 2024 (eid 126057294) package owner music set for libmetalink in f41 by jnsamyak [still active]
    owner: music
Tue Feb 13 21:44:19 2024 (eid 126057294) package list entry created: libmetalink in f41 by jnsamyak [still active]
    blocked: False
    extra_arches: 
Tue Feb 13 21:48:29 2024 (eid 126102583) libmetalink-0.1.3-34.fc40 tagged into f41 by jnsamyak [still active]
Fri Mar 22 20:23:47 2024 (eid 128096094) package owner music set for libmetalink in f40-Beta by jnsamyak [still active]
    owner: music
Fri Mar 22 20:23:47 2024 (eid 128096094) package list entry created: libmetalink in f40-Beta by jnsamyak [still active]
    blocked: False
    extra_arches: 
Fri Mar 22 20:28:09 2024 (eid 128141580) libmetalink-0.1.3-34.fc40 tagged into f40-Beta by jnsamyak [still active]
Mon Jul  1 13:38:36 2024 (eid 133456774) libmetalink-0.1.3-5.el7 unt

The retirement didn't go through somehow, similarly, parsertl14 wasn't retired from koji as well :D
Edited 10 months ago by jnsamyak

Log in to comment on this ticket.

Metadata
None

medium-trouble investigation high-gain

None
None
None
None
None
None
Powered by Pagure 5.14.1
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.