I'd like to do a new upstream release of koji soon, to take advantage of createrepo improvements and to have a release with some of the bugfixes that I've found since our refresh to RHEL5/new mock. The builders are locally patched for the bugfixes but I'd rather have them in a package. Any objections to doing a release next week and scheduling an evening to roll out upgrades? A small outage will be needed on the hub, and then the builders can have a rolling outage. There are no significant changes that would require much coordination.
On Sunday 20 January 2008, Jesse Keating wrote:
I'd like to do a new upstream release of koji soon, to take advantage of createrepo improvements and to have a release with some of the bugfixes that I've found since our refresh to RHEL5/new mock. The builders are locally patched for the bugfixes but I'd rather have them in a package. Any objections to doing a release next week and scheduling an evening to roll out upgrades? A small outage will be needed on the hub, and then the builders can have a rolling outage. There are no significant changes that would require much coordination.
I have no issues with that at all. i would prefer we do it so we are not carrying patches. Id like to see the patches that i submitted included also. It will help in secondary arch ramp up over the next couple of weeks
Dennis
On Sun, 20 Jan 2008 20:32:46 -0600 Dennis Gilmore dennis@ausil.us wrote:
I have no issues with that at all. i would prefer we do it so we are not carrying patches. Id like to see the patches that i submitted included also. It will help in secondary arch ramp up over the next couple of weeks
https://fedorahosted.org/koji/changeset/6feae640c291ae24de8e855b8564ff786527... ? Where there others as of yet not committed?
On Sunday 20 January 2008, Jesse Keating wrote:
On Sun, 20 Jan 2008 20:32:46 -0600
Dennis Gilmore dennis@ausil.us wrote:
I have no issues with that at all. i would prefer we do it so we are not carrying patches. Id like to see the patches that i submitted included also. It will help in secondary arch ramp up over the next couple of weeks
https://fedorahosted.org/koji/changeset/6feae640c291ae24de8e855b8564ff78652 7dcb9 ? Where there others as of yet not committed?
https://www.redhat.com/archives/fedora-buildsys-list/2008-January/msg00045.h...
that one is not yet commited. It adds the config option so we dont spam maintainers with a bunch of email for successful builds.
Dennis
On Sunday 20 January 2008, Dennis Gilmore wrote:
On Sunday 20 January 2008, Jesse Keating wrote:
On Sun, 20 Jan 2008 20:32:46 -0600
Dennis Gilmore dennis@ausil.us wrote:
I have no issues with that at all. i would prefer we do it so we are not carrying patches. Id like to see the patches that i submitted included also. It will help in secondary arch ramp up over the next couple of weeks
https://fedorahosted.org/koji/changeset/6feae640c291ae24de8e855b8564ff786 52 7dcb9 ? Where there others as of yet not committed?
https://www.redhat.com/archives/fedora-buildsys-list/2008-January/msg00045. html
that one is not yet commited. It adds the config option so we dont spam maintainers with a bunch of email for successful builds.
Dennis
here is the updated patch. if its too late thats ok
Dennis
Dennis Gilmore wrote:
I have no issues with that at all. i would prefer we do it so we are not carrying patches. Id like to see the patches that i submitted included also. It will help in secondary arch ramp up over the next couple of weeks
Keep in mind, we'll probably be working from the shadow branch for a little while. We may need to build our own releases for secondary arch until the kinks are worked out.
(Of course changes that need to make it to koji.fp.o are a different story).
On Sun, Jan 20, 2008 at 09:11:41PM -0500, Jesse Keating wrote:
I'd like to do a new upstream release of koji soon, to take advantage of createrepo improvements and to have a release with some of the bugfixes that I've found since our refresh to RHEL5/new mock. The builders are locally patched for the bugfixes but I'd rather have them in a package. Any objections to doing a release next week and scheduling an evening to roll out upgrades? A small outage will be needed on the hub, and then the builders can have a rolling outage. There are no significant changes that would require much coordination.
Looks like we will need to update mock to get revised yum exclude= lines, at least. Two blockers to releasing current mock git: 1) waiting on patch from mbonnet for --unpriv mode for --chroot 2) Need some code review on changes to mock.util.do(), as it was a rather large change there. -- Michael
buildsys@lists.fedoraproject.org