#9552 Retire commits don't retire packages
Closed: Fixed 3 years ago by churchyard. Opened 3 years ago by churchyard.

  • Describe the issue

See https://pagure.io/releng/issue/9544 and https://pagure.io/releng/issue/9551

Since the DC move, retire commits in dist git don't mark packages as retired in PDC and/or they don't block them in Koji. Composes happened, but this hasn't been done automatically until releng intervention.

  • When do you need this? any time

  • When is this no longer needed or useful? when people don't retire packages?

  • If we cannot complete your request, what is the impact? maintainers will retire packages, but it won't in fact happen


This is caused by fedmsg bridge not working and pdc-updater is using fedmsg.

https://pagure.io/fedora-infrastructure/issue/9094

Metadata Update from @mohanboddu:
- Issue tagged with: groomed, medium-gain, medium-trouble

3 years ago

In the meantime, can I please get the rights to retire packages in PDC?

We've deployed the replacement (toddlers-based, thus using fedora-messaging) yesterday.

So far it only works on packages that are being retired, it didn't process the old ones, that's on my todo, hopefully for today.

Oh, thanks. There was no update in https://pagure.io/fedora-infrastructure/issue/9094 so I assumed this is still broken.

Here is the list of packages I've retired since yesterday, that you can use to check if it works properly: https://pagure.io/releng/issue/9585

Seems like it's fixed. Thanks.

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

3 years ago

Login to comment on this ticket.

Metadata