>@Scott: this bug is reported for boost1.38 which is not in lucid (bug #539049 is for lucid version);
Yes - two bugs make sense: one for the SRU in karmic and one for a bug fix upload into lucid >will SRU request on libboost1.38 will get attention? The sponsors team is subscribed, they usually do a good job getting back. To get more attention, we should hop onto #ubuntu-devel and try to get someone from the stable release team to look at this bug (and the lucid one). I probably won't be able to do that for a day or two, so feel free to grab someone from irc to take a look at this. >Also, why is this "new" and not "confirmed" anymore? the stable release team, archives, and ubuntu-sponsors teams use different importance to track the progress of their inclusion of the patch. Once a team is subscribed, status doesn't matter (they will use it to signal to each other the status of the request). However, I'll make it triaged since that status is not reserved for their workflow. I'll fix the other bug's status as well. An example: https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue # The Status should be "New" for sync requests # The Status should be "Incomplete" for freeze exceptions # The Status should be "Confirmed" for bugs that represent a new candidate revision (e.g. bugfix uploads, merges.) In other words, use Status "Confirmed" when you have uploaded a debdiff that requires attention from a sponsor. ** Changed in: boost1.38 (Ubuntu) Status: New => Triaged -- [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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
