SRU testing should be done with the actual package in -proposed, because it's binary-copied to -updates. This might seem pedantic, but in the past we have had regressions caused by race conditions in the source building process -- the lesson learned is to test the actual update that'll be pushed out.
On Apr 24, 2010, at 4:27 PM, Václav Šmilauer wrote: > I cannot test the proposed package as I am already at lucid. > > I was using the package with ajmitch's patch (which is what has become > now the propsoed package) and it worked just fine; therefore I think it > is safe to let this go to updates. > > It would be, of course, good if someone else could confirm that. Please. > > -- > [SRU, 9.10] libboost-python1.38 issues with __doc__ property in Python >= > 2.6.3 > https://bugs.launchpad.net/bugs/457688 > You received this bug notification because you are a member of Ubuntu > Stable Release Updates Team, which is a direct subscriber. -- [SRU, 9.10] libboost-python1.38 issues with __doc__ property in Python >= 2.6.3 https://bugs.launchpad.net/bugs/457688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
