python-socksipy_1.02-2_amd64.changes ACCEPTED into unstable, unstable

2014-10-26 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Oct 2014 18:22:12 +0200 Source: python-socksipy Binary: python-socksipy python3-socksipy Architecture: source all Version: 1.02-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group

Bug#766752: marked as done (Please add support for python3)

2014-10-26 Thread Debian Bug Tracking System
Your message dated Sun, 26 Oct 2014 13:00:14 + with message-id e1xinqc-0004sj...@franck.debian.org and subject line Bug#766752: fixed in python-socksipy 1.02-2 has caused the Debian Bug report #766752, regarding Please add support for python3 to be marked as done. This means that you claim

Processing of imwheel_1.0.0pre12-12_amd64.changes

2014-10-26 Thread Debian FTP Masters
imwheel_1.0.0pre12-12_amd64.changes uploaded successfully to localhost along with the files: imwheel_1.0.0pre12-12.dsc imwheel_1.0.0pre12-12.debian.tar.xz imwheel_1.0.0pre12-12_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE,

imwheel_1.0.0pre12-12_amd64.changes ACCEPTED into unstable

2014-10-26 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 26 Oct 2014 15:53:50 -0400 Source: imwheel Binary: imwheel Architecture: source amd64 Version: 1.0.0pre12-12 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By:

Bug#755671: Merging a @debian.org account in a non @debian.org account leads to 403 Forbidden

2014-10-26 Thread Vincent Danjean
Package: tracker.debian.org Followup-For: Bug #755671 The reverse (merging a non-Debian account into a Debian account) leads to the same problem (403 error when trying to open the merge confirmation link while logged with the Debian account). Note that, to logout the Debian account, I needed to

Bug#766847: tracker.debian.org: subscriptions from old pts and from the new one seems independant

2014-10-26 Thread Vincent Danjean
Package: tracker.debian.org Severity: important Hi, subscriptions done from the old pts (and with the p...@qa.debian.org) do not appear in the tracker.debian.org interface. And, similarly, subscriptions done in the tracker.debian.org interface are not kwown from the p...@qa.debian.org

Bug#766857: debsources: import mirror suites as archive.d.o (AKA sticky) suites, without reimporting

2014-10-26 Thread Stefano Zacchiroli
Package: qa.debian.org Severity: normal User: qa.debian@packages.debian.org Usertags: debsources Currently, archive.debian.org suites are imported manually into Debsources (using bin/debsources-suite-archive), and not watched periodically by the cron job using bin/debsources-update. This

Bug#755671: Merging a @debian.org account in a non @debian.org account leads to 403 Forbidden

2014-10-26 Thread Raphael Hertzog
On Sun, 26 Oct 2014, Vincent Danjean wrote: The reverse (merging a non-Debian account into a Debian account) leads to the same problem (403 error when trying to open the merge confirmation link while logged with the Debian account). In fact, this 403 is unrelated. The problem is that the code

Bug#766847: tracker.debian.org: subscriptions from old pts and from the new one seems independant

2014-10-26 Thread Raphael Hertzog
Hi, On Sun, 26 Oct 2014, Vincent Danjean wrote: subscriptions done from the old pts (and with the p...@qa.debian.org) do not appear in the tracker.debian.org interface. And, similarly, subscriptions done in the tracker.debian.org interface are not kwown from the p...@qa.debian.org