As most are probably aware, we are hitting a bug[0] in the yum depsolver when trying to mash dist-f7-updates-testing. Tim Lauridsen wrote a patch[1] that seems to fix the problem and allows us to compose updates-testing again (WOOOOOOOO!).
Tim sent the patch to yum-devel for review, but in the mean time I'd be happy to apply this to the yum on releng1 so we can get these repos back under testing. What do you guys think?
luke
[0]: https://bugzilla.redhat.com/show_bug.cgi?id=360291 [1]: https://bugzilla.redhat.com/show_bug.cgi?id=360291#c24
On Wed, Nov 07, 2007 at 04:20:26PM -0500, Luke Macken wrote:
As most are probably aware, we are hitting a bug[0] in the yum depsolver when trying to mash dist-f7-updates-testing. Tim Lauridsen wrote a patch[1] that seems to fix the problem and allows us to compose updates-testing again (WOOOOOOOO!).
Tim sent the patch to yum-devel for review, but in the mean time I'd be happy to apply this to the yum on releng1 so we can get these repos back under testing. What do you guys think?
Also worth noting that this patch does not break any of yums unittests:
python test/alltests.py ......................................................................................................................... ---------------------------------------------------------------------- Ran 121 tests in 0.286s
OK
luke
On Wed, 2007-11-07 at 18:55 -0500, Luke Macken wrote:
On Wed, Nov 07, 2007 at 04:20:26PM -0500, Luke Macken wrote:
As most are probably aware, we are hitting a bug[0] in the yum depsolver when trying to mash dist-f7-updates-testing. Tim Lauridsen wrote a patch[1] that seems to fix the problem and allows us to compose updates-testing again (WOOOOOOOO!).
Tim sent the patch to yum-devel for review, but in the mean time I'd be happy to apply this to the yum on releng1 so we can get these repos back under testing. What do you guys think?
Also worth noting that this patch does not break any of yums unittests:
But given that the tests are really only starting to be written, counting on them as the only indicator is perhaps not wise. I've got the patch flagged to look at later tonight or tomorrow
Jeremy
On Wed, 2007-11-07 at 19:28 -0500, Jeremy Katz wrote:
On Wed, 2007-11-07 at 18:55 -0500, Luke Macken wrote:
On Wed, Nov 07, 2007 at 04:20:26PM -0500, Luke Macken wrote:
As most are probably aware, we are hitting a bug[0] in the yum depsolver when trying to mash dist-f7-updates-testing. Tim Lauridsen wrote a patch[1] that seems to fix the problem and allows us to compose updates-testing again (WOOOOOOOO!).
Tim sent the patch to yum-devel for review, but in the mean time I'd be happy to apply this to the yum on releng1 so we can get these repos back under testing. What do you guys think?
Also worth noting that this patch does not break any of yums unittests:
But given that the tests are really only starting to be written, counting on them as the only indicator is perhaps not wise. I've got the patch flagged to look at later tonight or tomorrow
Okay, after looking closer, the patch seems sane to me
Jeremy
On Wed, Nov 07, 2007 at 04:20:26PM -0500, Luke Macken wrote:
As most are probably aware, we are hitting a bug[0] in the yum depsolver when trying to mash dist-f7-updates-testing. Tim Lauridsen wrote a patch[1] that seems to fix the problem and allows us to compose updates-testing again (WOOOOOOOO!).
Tim sent the patch to yum-devel for review, but in the mean time I'd be happy to apply this to the yum on releng1 so we can get these repos back under testing. What do you guys think?
Both Jeremy and Florian approved the patch, so I went ahead and patched yum on releng1 and mashed f7-updates-testing. So we should be back in action, after 16 days of updates-testing downtime.
luke
infrastructure@lists.fedoraproject.org