Processing of apr-util_1.6.1-2_amd64.changes

2018-02-25 Thread Debian FTP Masters
apr-util_1.6.1-2_amd64.changes uploaded successfully to localhost along with the files: apr-util_1.6.1-2.dsc apr-util_1.6.1-2.debian.tar.xz apr-util_1.6.1-2_amd64.buildinfo libaprutil1-dbd-mysql_1.6.1-2_amd64.deb libaprutil1-dbd-odbc_1.6.1-2_amd64.deb

apr-util_1.6.1-2_amd64.changes ACCEPTED into unstable

2018-02-25 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Feb 2018 12:40:36 +0100 Source: apr-util Binary: libaprutil1 libaprutil1-ldap libaprutil1-dbd-mysql libaprutil1-dbd-sqlite3 libaprutil1-dbd-odbc libaprutil1-dbd-pgsql libaprutil1-dev libaprutil1-dbg

Bug#890108: marked as done (apr-util: FTBFS with debhelper/11.1 due to empty build target)

2018-02-25 Thread Debian Bug Tracking System
Your message dated Sun, 25 Feb 2018 12:04:48 + with message-id and subject line Bug#890108: fixed in apr-util 1.6.1-2 has caused the Debian Bug report #890108, regarding apr-util: FTBFS with debhelper/11.1 due to empty build target to be marked as done.

Accepted apr-util 1.6.1-2 (source amd64) into unstable

2018-02-25 Thread Stefan Fritsch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Feb 2018 12:40:36 +0100 Source: apr-util Binary: libaprutil1 libaprutil1-ldap libaprutil1-dbd-mysql libaprutil1-dbd-sqlite3 libaprutil1-dbd-odbc libaprutil1-dbd-pgsql libaprutil1-dev libaprutil1-dbg Architecture: source

Processed: tagging 890108

2018-02-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 890108 + pending Bug #890108 [src:apr-util] apr-util: FTBFS with debhelper/11.1 due to empty build target Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 890108:

Bug#889170: apr-util: build failure with new gdbm

2018-02-25 Thread Stefan Fritsch
On Friday, 2 February 2018 23:32:35 CET Gianfranco Costamagna wrote: > Hello, before uploading new gdbm in unstable, I tested all the > reverse-dependencies, except for the packages that were already broken/not > building. > > This sounds to be the case for this one, and now I don't know how to

Processing of apr_1.6.3-2_amd64.changes

2018-02-25 Thread Debian FTP Masters
apr_1.6.3-2_amd64.changes uploaded successfully to localhost along with the files: apr_1.6.3-2.dsc apr_1.6.3-2.debian.tar.xz apr_1.6.3-2_amd64.buildinfo libapr1-dbg_1.6.3-2_amd64.deb libapr1-dev_1.6.3-2_amd64.deb libapr1_1.6.3-2_amd64.deb Greetings, Your Debian queue daemon

apr_1.6.3-2_amd64.changes ACCEPTED into unstable

2018-02-25 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Feb 2018 16:35:41 +0100 Source: apr Binary: libapr1 libapr1-dev libapr1-dbg Architecture: source amd64 Version: 1.6.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers

Bug#888593: marked as done (apr: FTBFS with debhelper/11.1 due to empty build target)

2018-02-25 Thread Debian Bug Tracking System
Your message dated Sun, 25 Feb 2018 16:20:18 + with message-id and subject line Bug#888593: fixed in apr 1.6.3-2 has caused the Debian Bug report #888593, regarding apr: FTBFS with debhelper/11.1 due to empty build target to be marked as done. This means