Re: Bug#698661: unblock: openmotif/2.3.3-7
Hi, Paul Gevers wrote (22 Jan 2013 19:02:07 GMT) : > Regarding your [1], where can I actually find this list? The lists are hardening/subgoal* in svn://svn.debian.org/secure-testing. > Not that I think openmotif is on it, but anyway. My checkout is a bit old, and I'm offline so I cannot check right now, but no, it does not look like openmotif is on the list. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/85pq0vfvoo@boum.org
Candidates for removal from testing (2013-01-24)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, We are considering removing the following packages from testing as they have unfixed RC bugs filed against them. The packages can be found in the attached dd-list. The bugs that put them on this list can be found in the removals file (also attached) just above the package name. The packages have been selected based on the following criteria: * The package had at least one RC bug without activity for the past 14 days. * If a bug is assigned to multiple packages, both packages will be affected. * The RC bug affects both unstable and testing. * The affected package does not have any reverse dependencies in testing. If the relevant RC bugs in the affected packages are not dealt with /before/ Thursday the 31th of Jan., the packages will be removed from testing. Note that "dealt with" may also include downgrading a severity-inflated bug or fixing affected versions in the BTS. Please remember to file unblock bugs for packages fixed via uploads to unstable (and tpu bugs for requests to fix the package via a tpu upload). Should you need a bit more time than given, please do not hesitate to contact us. It is also easier for us if we can avoid having to reintroduce a removed package. We will check the DELAYED queues before activing the removal hints, so NMUs in the DELAYED queues will be given a chance to reach unstable. Thanks, Niels (on behalf of the Release Team) The bugs were found using the tools from: svn://svn.debian.org/svn/collab-qa/rc-buggy-leaf-packages http://release.debian.org/wheezy/freeze_policy.html --8<8<-- dd-list --8<8<-- Debian Java Maintainers jenkins Debian QA Group bzr-gtk James Page jenkins (U) Pierre Chifflier glpi Romain Beauxis lastfmproxy Wouter Verhelst pmw --8<8<-- end of dd-list --8<8<-- --8<8<-- removals --8<8<-- # #697402 remove bzr-gtk/0.103.0+bzr792-3 # #694642 remove glpi/0.83.31-1 # #696816 remove jenkins/1.447.2+dfsg-2 # #694589 remove lastfmproxy/1.3b-2 # #696844 remove pmw/1:4.24-1 --8<8<-- end of removals --8<8<-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRAUhvAAoJEAVLu599gGRCdKoP/AouibtJnE4H4MGdGNxU4rJE G4kJaeqpR/aeKBiti30eXdUwKLfMNGE2dFqbrp0Wgp/YSE+vr22JyqyC43AHoKkD dLhpqcnFVKfQe97MvsdbVel6Ox5x45wwGFqkO5HwT6M5cLc9RClCm7sA0XyCsinQ dmq3nR0tJW9pfnTm97bwCRmisJ9DwVxtgjKqr082sfQFsUOkZP7OpM2q0ZDtwC84 X4/P+7rHSOor8Evj8lE75fN4rXu0e4bjq98yRprRuHHyWLSmqpuvFpniBlQFmsI3 kdMv2r5WL6NU3bT6IGDhjcx4gq8FouRbKYyTybhua2J8Ez9bkp4gbR5VMh3nmIrI e7BI0UEWIeYz2TmyclSp/1DCjQY+Rl9NmTJpklcJuAUgtDHt2pZCnVemz/iEvkjv mZbVhynfNeZrnlR0KQGQXdshm2K2amF0WoF9as71vU9EqMUI2DXiD8fDTgtQa2+B YuP1Pk5hEko5A9c9tAjSNfEOjnLaFfbUfW1+5gCplzF7Vd4FcY5JTiAKzOliwPpD lMrPL5XTgUDfz6d9sW2aGA2Iyk6ruhDk0d98YcpmviQE72aTyHuZ8m97zqhAprdt eaCD56R3TJfr2DKRh6933Ccq7AtLcUx4asOCZV6myEFKSg4kMd5LEAyVlziNYxxx Gp5OZE+O4xLtiMtU+MUy =/0Pa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130124144708.58796200ff...@thykier.net
Bug#697402: bzr-gtk: causes crash in pydoc -k when python-gtk2 is also installed
* Samuel Bronson , 2013-01-04, 16:20: from gi.repository import Gtk import _gtk The last line should read: from import _gtk This bug should be reassigned somewhere else, but I haven't decided where yet. Anyway, here are some ideas how to fix (or "fix") it: 1) Make pydoc more robust. It could spawn a worker process, which would do all the nasty import job. If the worked process segfaulted, it wouldn't be a big deal, as a new one could be spawned. 2) Fix both python-gtk2 and python-gi, so that ImportError is thrown early if you try to load Gtk$n bindings and Gtk$((5-n)) are already in sys.modules. This should be easy to do on the python-gtk2 side, and probably way more tricky on the python-gi side. Also, this solves the problem only partially, because there are other Python extensions linked to libgtk2 or libgtk3. (Certainly too many too fix them all. :/) 3) Make libgtk2 and libgtk3 use symbol versioning. Probably not something that would be accepted for wheezy. :/ -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130124224804.ga6...@jwilk.net
Bug#697402: bzr-gtk: causes crash in pydoc -k when python-gtk2 is also installed
* Jakub Wilk , 2013-01-24, 23:48: from gi.repository import Gtk import _gtk The last line should read: from import _gtk Third time lucky: from gtk import _gtk -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130124231741.ga8...@jwilk.net
