#8583 Orphan github2fedmsg
Closed: Fixed 4 years ago by churchyard. Opened 4 years ago by churchyard.


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

4 years ago

cc @ralph - I think we have some things depending on github messages coming through on our fedmsg or fedora messaging bus, right?

Oop, yes we do. I could re-take this one.

OTOH, the instance we run is using EPEL7. We could let this get retired in rawhide and just maintain that?

I would very much like to get it retired. Its dependencies are orphaned, it doesn't currently install, nobody answers for bugzillas. It got orphaned for a reason, claiming it back is your right, but makes no sense.

Yeah, let's let it let it go in rawhide. I can still maintain the service in EPEL7.

For that, @churchyard - should I claim the package but then explicitly retire it. Would that work?

are the deps also orphaned in epel?

are the deps also orphaned in epel?

I guess, as long as those are the same packages. See https://churchyard.fedorapeople.org/orphans.txt - grep for ralph.

should I claim the package but then explicitly retire it. Would that work?

I can retire it as a provenpackager. just give me ack.

Login to comment on this ticket.

Metadata