kcollectd is marked for autoremoval from testing
kcollectd 0.9-5 is marked for autoremoval from testing on 2018-09-05 It (build-)depends on packages with these RC bugs: 897724: collectd: ftbfs with GCC-8
vzdump is marked for autoremoval from testing
vzdump 1.2.6-5 is marked for autoremoval from testing on 2018-09-04 It (build-)depends on packages with these RC bugs: 897884: vzquota: ftbfs with GCC-8
ifhp is marked for autoremoval from testing
ifhp 3.5.20-15 is marked for autoremoval from testing on 2018-08-20 It is affected by these RC bugs: 891556: ifhp: FTBFS with GCC 8 - error: 'strncpy' specified bound 128 equals destination size 897771: ifhp: ftbfs with GCC-8
hovercraft is marked for autoremoval from testing
hovercraft 2.1-3 is marked for autoremoval from testing on 2018-08-23 It (build-)depends on packages with these RC bugs: 903524: manuel: manuel FTBFS with Python 3.7 as supported version
vzquota is marked for autoremoval from testing
vzquota 3.1-3 is marked for autoremoval from testing on 2018-09-04 It is affected by these RC bugs: 897884: vzquota: ftbfs with GCC-8
vzctl is marked for autoremoval from testing
vzctl 4.9.4-5 is marked for autoremoval from testing on 2018-09-04 It (build-)depends on packages with these RC bugs: 897884: vzquota: ftbfs with GCC-8
simulavr is marked for autoremoval from testing
simulavr 0.1.2.2-7 is marked for autoremoval from testing on 2018-08-18 It is affected by these RC bugs: 897860: simulavr: ftbfs with GCC-8
Bug#905802: changetrack: cron script accesses internal dpkg database
Source: changetrack
Source-Version: 4.7-5
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-db-access-blocker
Hi!
This package contains a cron script [M], which directly accesses
the dpkg internal database. Instead of using one of the public
interfaces provided by dpkg. The code could be replaced with something
like «dpkg-query --showformat '${Conffiles}\n' --show |
grep -E -v '(^\s*|\.schemas)$' | cut -d\ -f2 | sort | uniq».
[M] debian/cron.daily
This a problem for multiple reasons. Even though the layout and format
of the dpkg database is administrator friendly, and it's expected that
those might need to mess with it, in case of emergency, this interface
does not extend to other programs besides the dpkg suite of tools. The
admindir can also be configured differently at dpkg build or run-time.
And finally, the contents and its format, will be changing in the near
future.
In addition the .conffiles in the database never get updated even after
conffile take overs by another package.
Thanks,
Guillem
Bug#905788: FTBFS: cannot find -lgpod
Package: src:libgpod Version: 0.8.3-11 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: ftbfs Trying to build the package in a fresh sid sbuild chroot I get libtool: warning: relinking '_gpod.la' libtool: install: (cd /<>/build/python2.7/bindings/python; /bin/bash "/<>/build/python2.7/libtool" --tag CC --mode=relink gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -module -avoid-version -shared -Wl,-z,relro -Wl,-O1 -Wl,--as-needed -o _gpod.la -rpath /usr/lib/python2.7/dist- packages/gpod _gpod_la-gpod_wrap.lo -lgobject-2.0 -lsqlite3 -lplist -Wl,-- export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lxml2 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lgobject-2.0 -lglib-2.0 ../../src/libgpod.la -inst- prefix-dir /<>/debian/tmp) Byte-compiling python modules (optimized versions) ... __init__.pygtkpod.pyipod.py Byte-compiling python modules (optimized versions) ... gpod.py libtool: relink: gcc -shared -fPIC -DPIC .libs/_gpod_la-gpod_wrap.o -L/<>/debian/tmp/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux- gnu -lsqlite3 -lplist -lgmodule-2.0 -lxml2 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lgpod -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-O1 -Wl,--as-needed -Wl,--export-dynamic -pthread -pthread -Wl,-soname -Wl,_gpod.so -o .libs/_gpod.so /usr/bin/ld: cannot find -lgpod collect2: error: ld returned 1 exit status libtool: error: error: relink '_gpod.la' with the above command before installing it -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash -- WBR, wRAR signature.asc Description: PGP signature
Bug#896230: python-gpod: gpod fails to import
On Mon, Apr 23, 2018 at 08:28:22PM +0100, Mark Williams wrote: > Installing python-gobject seems to work around this. Suggest this is added > to dependencies. Thank you for this observation, it seems dh_python2 --depends=gobject doesn't produce the correct depends on python-gobject-2. -- WBR, wRAR signature.asc Description: PGP signature
Bug#905761: backuppc: FTBFS with merged /usr
Package: backuppc
Version: 3.3.1-5
Severity: serious
Hi,
backuppc fails to build with merged /usr in a sbuild chroot, created with
current debootstrap. Debootstrap enabled merged /usr since version 1.0.85, see
https://bugs.debian.org/839046
The build fails when a patch is applied to the generated config.pl file. Since
the path to cat is now /usr/bin/cat instead of /bin/cat, the patch fails to
apply.
Here's the failing part of the patch:
-
@@ -224,7 +227,7 @@
# Full path to various commands for archiving
#
$Conf{SplitPath} = '/usr/bin/split';
-$Conf{ParPath} = '/usr/bin/par2';
+$Conf{ParPath} = '/usr/bin/par2' if -x '/usr/bin/par2';
$Conf{CatPath} = '/bin/cat';
$Conf{GzipPath} = '/bin/gzip';
$Conf{Bzip2Path} = '/bin/bzip2';
-
And here's the failing part of the build log:
--
install --mode=644 debian/apache.conf debian/backuppc/etc/backuppc
rmdir debian/backuppc/var/lib/backuppc/conf/
rmdir: failed to remove 'debian/backuppc/var/lib/backuppc/conf/': No such file o
r directory
make: [debian/rules:67: install] Error 1 (ignored)
(cd debian/backuppc/usr/share/backuppc/cgi-bin; ln -s ../image; ln -s /usr/lib/b
ackuppc/cgi-bin/index.cgi )
patch --no-backup-if-mismatch -p0 < debian/config.pl.diff
patching file debian/backuppc/etc/backuppc/config.pl
Hunk #2 FAILED at 227.
Hunk #4 succeeded at 1021 (offset -3 lines).
1 out of 7 hunks FAILED -- saving rejects to file debian/backuppc/etc/backuppc/c
onfig.pl.rej
make: *** [debian/rules:69: install] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit
status 2
-
Full build log attached.
Apparently, the official builds' chroots didn't use merged /usr when the
package was last built (February 2018), but at some point some of them will,
leading to inability to build backuppc on official infrastructure.
IMO, adapting the patch to the merged /usr would not work, since then the patch
will fail on systems without merged /usr.
-- dam
sbuild (Debian sbuild) 0.77.0 (06 July 2018) on pc1.creditreform.bg
+==+
| backuppc 3.3.1-5 (amd64) Wed, 08 Aug 2018 14:22:31 + |
+==+
Package: backuppc
Version: 3.3.1-5
Source Version: 3.3.1-5
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/sid+exp-perl-amd64-b67b90b7-ae44-4d20-b602-62f9cb7b4d9a'
with '<>'
I: NOTICE: Log filtering will replace 'build/backuppc-t497R0/resolver-4nL5LG'
with '<>'
+--+
| Update chroot|
+--+
Get:1 http://proxy:/debian sid InRelease [233 kB]
Get:2 http://proxy:/debian experimental InRelease [101 kB]
Get:3 http://perl.debian.net/test-repo perl-5.28 InRelease [2871 B]
Get:4 http://proxy:/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Get:5 http://proxy:/debian sid/main amd64 Packages 2018-08-04-0814.44.pdiff
[20.5 kB]
Get:6 http://proxy:/debian sid/main amd64 Packages 2018-08-04-1411.17.pdiff
[9739 B]
Get:7 http://proxy:/debian sid/main amd64 Packages 2018-08-04-2013.33.pdiff
[17.8 kB]
Get:8 http://proxy:/debian sid/main amd64 Packages 2018-08-05-0209.24.pdiff
[15.5 kB]
Get:9 http://proxy:/debian sid/main amd64 Packages 2018-08-05-0806.31.pdiff
[2966 B]
Get:10 http://proxy:/debian sid/main amd64 Packages
2018-08-05-1409.33.pdiff [18.0 kB]
Get:11 http://proxy:/debian sid/main amd64 Packages
2018-08-05-2014.01.pdiff [9558 B]
Get:12 http://proxy:/debian sid/main amd64 Packages
2018-08-06-0208.11.pdiff [4773 B]
Get:13 http://proxy:/debian sid/main amd64 Packages
2018-08-06-0809.42.pdiff [5408 B]
Get:14 http://proxy:/debian sid/main amd64 Packages
2018-08-06-1412.59.pdiff [16.0 kB]
Get:15 http://proxy:/debian sid/main amd64 Packages
2018-08-06-2047.08.pdiff [31.4 kB]
Get:16 http://proxy:/debian sid/main amd64 Packages
2018-08-07-0215.15.pdiff [9234 B]
Get:17 http://proxy:/debian sid/main amd64 Packages
2018-08-07-0814.06.pdiff [5576 B]
Get:18 http://proxy:/debian sid/main amd64 Packages
2018-08-07-1417.50.pdiff [17.6 kB]
Get:19 http://proxy:/debian sid/main amd64 Packages
2018-08-07-2009.40.pdiff [13.1 kB]
Get:20 http://proxy:/debian sid/main amd64 Packages
2018-08-08-0208.47.pdiff [4775 B]
Get:21 http://proxy:/debian sid/main amd64 Packages
2018-08-08-0809.52.pdiff [7784 B]
Get:21 http://proxy:/debian sid/main amd64 Packages
2018-08-08-0809.52.pdiff [7784 B]
Get:22
