#10338 Recently retired packages left in inconsistent state (not blocked from koji)
Closed: Fixed 2 years ago by humaton. Opened 2 years ago by decathorpe.

  • Describe the issue

It looks like some recently retired packages are now stuck in an inconsistent state. For example, the "jaxb-fi" package was retired from the rawhide and f35 branches (dead.package files are in dist-git), but the package has only been blocked from koji for f35. Rawhide repositories still contain the package even after multiple successful composes.

The affected packages I found are:

  • jaxb
  • jaxb-dtd-parser
  • jaxb-fi
  • jaxb-istack-commons
  • jaxb-stax-ex
  • xmlstreambuffer

I'm not sure if there other packages in this inconsistent state. It might be worth investigating packages that were retired from rawhide at the same time as these packages.

I think they should be blocked from the f36 tag in koji, but I'm not sure if there's anything else wrong with the state of the affected packages.

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

Before F36 branch point, I guess? Otherwise retired packages will leak into F36 repositories, as well.

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

Never. Or at least, not once the packages are unretired (which might be never, given the state of Java packages in Fedora).

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

Unmaintained and retired packages, for which no bugs or new versions are tracked, will continue to leak into Fedora repositories.


Yep. Not sure we need both of these, but lets leave until we know more.

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

2 years ago

The underlying issue should be fixed in toddlers, all of the mentioned packages have a new maintainer.

Metadata Update from @humaton:
- 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