#10976 Properly retire some packages from F37 that fell through the cracks during mass branching
Closed: Fixed by humaton. Opened by decathorpe.

Properly retire some packages from F37 that fell through the cracks during mass branching

  • Describe the issue

I retired some packages during what appears to be the exact few minutes where the mass branching script was run. :tired_face: Some of them were retired correctly, some were not (i.e. were not blocked from koji).

As far as I can tell, the list of affected packages (i.e. have dead.package in their f37 branch in dist-git, but are not blocked from the f37 tag in koji) is:

  • rust-cap-async-std
  • rust-cap-fs-ext
  • rust-cap-rand
  • rust-cap-time-ext
  • rust-system-interface
  • rust-wasi-cap-std-sync
  • rust-wasi-tokio
  • rust-wasmtime-wasi

Please block these packages from the f37 tag in koji (and do whatever else needs doing for them to be retired correctly).

Other people's packages might be affected too, but I don't have an easy way of checking this exhaustively for packages that aren't owned by me.

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

Before the F37 final freeze (2022-10-04)

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

Fedora 37 EOL (2023-11-14)

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

Retired and possibly broken packages litter fedora-37 repositories and the f37 tag in koji.


packages are now blocked in koji and EOL in pdc is set.

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

Yeah, looks good now. Thanks!

Metadata