Good morning everyone,
I just manually hotfix pkgdb2 for this fix: https://github.com/fedora-infra/pkgdb2/commit/e5ca8bcb2a1b8fed2a68c50ed959f3...
The idea is to keep allowing people who have the proper ACLs to commit on Orphaned packages (so that they can fix things). The bug was introduced in pkgdb (manually as well) by me yesterday morning before we went into freeze.
Could I please have two +1 in retro?
Thanks, Pierre
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 28 Aug 2014 15:42:36 +0200 Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good morning everyone,
I just manually hotfix pkgdb2 for this fix: https://github.com/fedora-infra/pkgdb2/commit/e5ca8bcb2a1b8fed2a68c50ed959f3...
The idea is to keep allowing people who have the proper ACLs to commit on Orphaned packages (so that they can fix things). The bug was introduced in pkgdb (manually as well) by me yesterday morning before we went into freeze.
Could I please have two +1 in retro?
+1 it is causing issues
Dennis
On Thu, 28 Aug 2014 15:42:36 +0200 Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good morning everyone,
I just manually hotfix pkgdb2 for this fix: https://github.com/fedora-infra/pkgdb2/commit/e5ca8bcb2a1b8fed2a68c50ed959f3...
The idea is to keep allowing people who have the proper ACLs to commit on Orphaned packages (so that they can fix things). The bug was introduced in pkgdb (manually as well) by me yesterday morning before we went into freeze.
Could I please have two +1 in retro?
+1 here.
kevin
I submitted a pull request to bodhi to get things working with the new EPEL7 tagging schema. I'd like to spin up a new release and get it deployed today to enable EPEL7 updates.
https://github.com/fedora-infra/bodhi/pull/87
There are plenty of places in the code that bodhi has to see if it's dealing with EPEL, and handle things a little differently. Previously, it would only look to see if the Release.name.startswith('EL'), and this patch changes it to look for just 'E'. This is an ugly hack to an existing ugly hack, but it is already resolved in the current bodhi2 codebase, so I'm cool with it.
luke
On Thu, Aug 28, 2014 at 03:42:36PM +0200, Pierre-Yves Chibon wrote:
Good morning everyone,
I just manually hotfix pkgdb2 for this fix: https://github.com/fedora-infra/pkgdb2/commit/e5ca8bcb2a1b8fed2a68c50ed959f3...
The idea is to keep allowing people who have the proper ACLs to commit on Orphaned packages (so that they can fix things). The bug was introduced in pkgdb (manually as well) by me yesterday morning before we went into freeze.
Could I please have two +1 in retro?
Thanks, Pierre _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
On Fri, 29 Aug 2014 11:09:43 -0600 Luke Macken lmacken@redhat.com wrote:
I submitted a pull request to bodhi to get things working with the new EPEL7 tagging schema. I'd like to spin up a new release and get it deployed today to enable EPEL7 updates.
https://github.com/fedora-infra/bodhi/pull/87There are plenty of places in the code that bodhi has to see if it's dealing with EPEL, and handle things a little differently. Previously, it would only look to see if the Release.name.startswith('EL'), and this patch changes it to look for just 'E'. This is an ugly hack to an existing ugly hack, but it is already resolved in the current bodhi2 codebase, so I'm cool with it.
+1
This would go on bodhi01/02 and releng04/relepel01?
kevin
On Fri, Aug 29, 2014 at 11:15:08AM -0600, Kevin Fenzi wrote:
On Fri, 29 Aug 2014 11:09:43 -0600 Luke Macken lmacken@redhat.com wrote:
I submitted a pull request to bodhi to get things working with the new EPEL7 tagging schema. I'd like to spin up a new release and get it deployed today to enable EPEL7 updates.
https://github.com/fedora-infra/bodhi/pull/87There are plenty of places in the code that bodhi has to see if it's dealing with EPEL, and handle things a little differently. Previously, it would only look to see if the Release.name.startswith('EL'), and this patch changes it to look for just 'E'. This is an ugly hack to an existing ugly hack, but it is already resolved in the current bodhi2 codebase, so I'm cool with it.
+1
This would go on bodhi01/02 and releng04/relepel01?
kevin
Yup, those boxes will need a new bodhi-server package. No client changes are needed.
luke
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 29 Aug 2014 11:15:08 -0600 Kevin Fenzi kevin@scrye.com wrote:
On Fri, 29 Aug 2014 11:09:43 -0600 Luke Macken lmacken@redhat.com wrote:
I submitted a pull request to bodhi to get things working with the new EPEL7 tagging schema. I'd like to spin up a new release and get it deployed today to enable EPEL7 updates.
https://github.com/fedora-infra/bodhi/pull/87There are plenty of places in the code that bodhi has to see if it's dealing with EPEL, and handle things a little differently. Previously, it would only look to see if the Release.name.startswith('EL'), and this patch changes it to look for just 'E'. This is an ugly hack to an existing ugly hack, but it is already resolved in the current bodhi2 codebase, so I'm cool with it.
+1
This would go on bodhi01/02 and releng04/relepel01?
kevin
+1 from me also
Dennis
infrastructure@lists.fedoraproject.org
-
Dennis Gilmore -
Kevin Fenzi -
Luke Macken -
Pierre-Yves Chibon