Processing of libical3_3.0.1-1_amd64.changes

libical3_3.0.1-1_amd64.changes uploaded successfully to localhost along with the files: libical3_3.0.1-1.dsc libical3_3.0.1.orig.tar.gz libical3_3.0.1-1.debian.tar.xz libical3-dbgsym_3.0.1-1_amd64.deb libical3-dev_3.0.1-1_amd64.deb libical3_3.0.1-1_amd64.buildinfo libical3_3.0.1-1_amd

libical3_3.0.1-1_amd64.changes is NEW

binary:libical3 is NEW. binary:libical3-dev is NEW. binary:libical3 is NEW. binary:libical3-dev is NEW. source:libical3 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature an

Processed: xpdf: FTBFS with poppler 0.61.1

Processing control commands: > block 883514 with -1 Bug #883514 [release.debian.org] transition: poppler 883514 was blocked by: 883522 883519 883521 883518 883514 was not blocking any bugs. Added blocking bug(s) of 883514: 883523 -- 883514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88351

Bug#883523: xpdf: FTBFS with poppler 0.61.1

Package: xpdf Version: 3.04-5 Severity: important Control: block 883514 with -1 Hi, Your package fails to build with poppler 0.61.1 from experimental. This version introduces some API changes to the Object class which cause some problems to a few packages. In some cases upstream has already adapt

Bug#883530: vtun FTCBFS: uses the build architecture strip

Source: vtun Version: 3.0.3-4 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap vtun fails to cross build from source, because the install target of its Makefile runs the build architecture strip. Such stripping also prevents dh_strip from doing its job and generating useful -dbg

Processing of buildbot_0.8.14-1_source.changes

buildbot_0.8.14-1_source.changes uploaded successfully to localhost along with the files: buildbot_0.8.14-1.dsc buildbot_0.8.14.orig.tar.xz buildbot_0.8.14-1.debian.tar.xz buildbot_0.8.14-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of buildbot-slave_0.8.12-3_source.changes

buildbot-slave_0.8.12-3_source.changes uploaded successfully to localhost along with the files: buildbot-slave_0.8.12-3.dsc buildbot-slave_0.8.12-3.debian.tar.xz buildbot-slave_0.8.12-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

buildbot-slave_0.8.12-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Dec 2017 20:31:12 +0100 Source: buildbot-slave Binary: buildbot-slave Architecture: source Version: 0.8.12-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Matthias Klose Descri

buildbot_0.8.14-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Dec 2017 20:10:15 +0100 Source: buildbot Binary: buildbot Architecture: source Version: 0.8.14-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Matthias Klose Description: buil

Processing of libcdio_1.0.0-1_amd64.changes

libcdio_1.0.0-1_amd64.changes uploaded successfully to localhost along with the files: libcdio_1.0.0-1.dsc libcdio_1.0.0.orig.tar.gz libcdio_1.0.0-1.debian.tar.xz libcdio-dev_1.0.0-1_amd64.deb libcdio-utils-dbgsym_1.0.0-1_amd64.deb libcdio-utils_1.0.0-1_amd64.deb libcdio17-dbgsym_1.0.

Processing of python-characteristic_14.3.0-2_source.changes

python-characteristic_14.3.0-2_source.changes uploaded successfully to localhost along with the files: python-characteristic_14.3.0-2.dsc python-characteristic_14.3.0-2.debian.tar.xz python-characteristic_14.3.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host

libcdio_1.0.0-1_amd64.changes is NEW

binary:libcdio17 is NEW. binary:libcdio17 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely proces

python-characteristic_14.3.0-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Dec 2017 21:30:52 +0100 Source: python-characteristic Binary: python-characteristic python3-characteristic Architecture: source Version: 14.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Grou

Processed: Re: libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev

Processing commands for cont...@bugs.debian.org: > unarchive 628194 Bug #628194 {Done: Chow Loong Jin } [libgpod] libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev Unarchived Bug 628194 > reopen 628194 Bug #628194 {Done: Chow Loong Jin } [libgpod] libgpod should only depend o

Processing of libgpod_0.8.3-11_source.changes

libgpod_0.8.3-11_source.changes uploaded successfully to localhost along with the files: libgpod_0.8.3-11.dsc libgpod_0.8.3-11.debian.tar.xz libgpod_0.8.3-11_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#628194: marked as done (libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev)

Your message dated Tue, 05 Dec 2017 03:49:35 + with message-id and subject line Bug#628194: fixed in libgpod 0.8.3-11 has caused the Debian Bug report #628194, regarding libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev to be marked as done. This means that you claim that

libgpod_0.8.3-11_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Dec 2017 21:50:10 -0500 Source: libgpod Binary: libgpod-dev libgpod4 libgpod-common libgpod-doc python-gpod libgpod-cil libgpod-cil-dev Architecture: source Version: 0.8.3-11 Distribution: unstable Urgency: med