This is just a heads up that there is a dependency chain of orphaned packages that would lead to problems in bodhi when retired. They will be retired in less than a month if nobody takes them.
See https://churchyard.fedorapeople.org/orphans.txt
(I wonder who takes care of bodhi when Randy is not available, ccing Aurelien who made some commits recently.)
On 8/17/19 2:25 AM, Miro Hrončok wrote:
This is just a heads up that there is a dependency chain of orphaned packages that would lead to problems in bodhi when retired. They will be retired in less than a month if nobody takes them.
See https://churchyard.fedorapeople.org/orphans.txt
(I wonder who takes care of bodhi when Randy is not available, ccing Aurelien who made some commits recently.)
Yeah, everyone in infra-sig group takes care of these packages, but as you know this is all coming at a bad time for us, since we are swamped with other work items and this is all on top. ;(
Anyhow, I hope later this week to go and try and sort this out.
kevin
On 8/20/19 9:31 AM, Kevin Fenzi wrote:
On 8/17/19 2:25 AM, Miro Hrončok wrote:
This is just a heads up that there is a dependency chain of orphaned packages that would lead to problems in bodhi when retired. They will be retired in less than a month if nobody takes them.
See https://churchyard.fedorapeople.org/orphans.txt
(I wonder who takes care of bodhi when Randy is not available, ccing Aurelien who made some commits recently.)
Yeah, everyone in infra-sig group takes care of these packages, but as you know this is all coming at a bad time for us, since we are swamped with other work items and this is all on top. ;(
Anyhow, I hope later this week to go and try and sort this out.
So, looking at our packaging state...
moksha* is python2 only as far as I can see, and hasn't had a release since 2013. We have a number of things that depend on this stack:
bugzilla2fedmsg fedmsg itself, I think? badges notifs packages pdc
So I assume we want to get off that, which means trying to finish the fedora-messaging transition and dropping/porting things.
I'm having trouble finding the orphans in the stack of bodhi deps. Does someone have a script that will take a package and list owners of all packages it depends on so I can find the orphans?
I see that mote fails to build/is python2. We could port it to python3, but perhaps we could come up with a better way to frontend our irc meeting logs thats not an app we maintain?
I'm sure there's more, but I ran out of time when looking at this yesterday.
kevin
On Mon, 2019-08-26 at 11:08 -0700, Kevin Fenzi wrote:
On 8/20/19 9:31 AM, Kevin Fenzi wrote:
On 8/17/19 2:25 AM, Miro Hrončok wrote:
This is just a heads up that there is a dependency chain of orphaned packages that would lead to problems in bodhi when retired. They will be retired in less than a month if nobody takes them.
See https://churchyard.fedorapeople.org/orphans.txt
(I wonder who takes care of bodhi when Randy is not available, ccing Aurelien who made some commits recently.)
Yeah, everyone in infra-sig group takes care of these packages, but as you know this is all coming at a bad time for us, since we are swamped with other work items and this is all on top. ;(
Anyhow, I hope later this week to go and try and sort this out.
So, looking at our packaging state...
moksha* is python2 only as far as I can see, and hasn't had a release since 2013. We have a number of things that depend on this stack:
bugzilla2fedmsg
The new version I keep trying to get us to deploy to production doesn't need it any more, as it is ported to Python 3 and fedora-messaging. Only the old fedmsg version needs it.
fedmsg itself, I think?
Yeah, fedmsg uses moksha.
badges
Ralph kicked it out of tahrir last year: https://github.com/fedora-infra/tahrir/commit/b8bbfdf36a82ed4781939bd985e82c... so again we just need a new version deployed there.
infrastructure@lists.fedoraproject.org
-
Adam Williamson -
Kevin Fenzi -
Miro Hrončok