Bug#887727: [debhelper-devel] Bug#887727: debhelper, dh-dist-zilla: dh-dist-zilla based package builds no more run dh_auto_install (and maybe other dh_auto_*)

[Sascha Steinbiss]

Hi Niels and Axel,

> Niels Thykier wrote:
>> Could you please verify that the attached patch fixes the problem for you?
> 
> systray-mdstat and roary both build fine again with this patch applied
> on top of debhelper's git HEAD.

Confirmed, and new roary upload done [x].
Thanks to you both for the quick action!

Best regards
Sascha


signature.asc
Description: Message signed with OpenPGP

Bug#887664: [debhelper-devel] Bug#887688: debhelper: empty build of src:ck

[Niels Thykier]

Sven Joachim:
> On 2018-01-21 23:24 +0200, Adrian Bunk wrote:
> 
>> On Fri, Jan 19, 2018 at 07:51:00PM +, Niels Thykier wrote:
>>> ...
>>>   The question now is: How many packages are affected by it?  If it is
>>> sufficiently low, it might be worth doing the clean up now to simplify
>>> packaging in general.  But in worst case, we will have to revert for now
>>> and reintroduce this to compat 12.
>>
>> My current list for "builds with 11 and FTBFS with 11.1.3" is:
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apr.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ck.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cpputest.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-handbook.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/iaxmodem.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/moarvm.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openal-soft.html
[...]
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jscommunicator.html
[...]

Indeed; all of these just have a .PHONY build target and nothing else
(i.e. they won't also hit #887482 AFAICT).  They all basically just want
debhelper to ignore the explicit target and inline the sequence.

I will dig a bit in the code

>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/biojava-live.html
> 
> This ends in
> 
> ,
> | dh_installdocs
> | make[1]: Leaving directory '/build/1st/biojava-live-1.7.1'
> |  dpkg-genbuildinfo --build=binary
> | dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
> .buildinfo is meaningless
> | dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary subprocess 
> returned exit status 25
> `
> 
> In other words, dh_installdeb was not run, apparently because there is a 
> broken
> explicit rule for the binary-indep target.
> 

The rule being:

"""
> binary-indep: build install
>   dh_testdir
>   dh_testroot
>   dh_installchangelogs 
>   dh_installdocs
"""

So yes,  that is rather incomplete.  It was probably saved by #880840
previously.

>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jansson.html
> 
> [...]
> which seems to have a similar cause as #887482.
> 

Indeed.  The package uses a work around for #836699 that now triggers
this issue.  Let's keep the discussion for these problems in #887482.

>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scidavis.html
> 
> Failed because 'dh_makeshlibs --no-act' returned an error.  Niels might
> know why this is now the case and used to be different.
> 
> Cheers,
>Sven
> 
> [...]

Bug in --no-act code; fixed in master now - thanks for spotting it. :)

Thanks,
~Niels

Processed: bug 887930 is forwarded to b...@w3.org

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 887930 b...@w3.org
Bug #887930 [src:html-xml-utils] html-xml-utils: FTBFS with netcat-traditional 
installed (testsuite hangs in extract1.sh)
Set Bug forwarded-to-address to 'b...@w3.org'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887583: [Pkg-javascript-devel] Bug#887583: Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3

[Pirate Praveen]

On ഞായര്‍ 21 ജനുവരി 2018 11:08 വൈകു, Pirate Praveen wrote:
> My logs were from before mocha 4 is uploaded to unstable. Now we need to fix 
> the tests for mocha 4 (this bug), as well as chai 4 (the other bug I 
> reported).
> 

mocha.{css,js,min.js} files were missing from mocha binary package (they
were only in libjs-mocha). But even after adding them I see other
errors. mocha changes are pushed to alioth.

xvfb-run -a -s "-screen 0 640x480x16" ./script/test
Error loading resource http://localhost:3901/ (1). Details: Connection
refused
Failed to load the page. Check the url: http://localhost:3901/
TypeError: Attempting to change the setter of an unconfigurable property.
TypeError: Attempting to change the setter of an unconfigurable property.
Error loading resource
http://localhost:3901/node_modules/url-search-params/build/url-search-params.js
(203). Details: Error transferring
http://localhost:3901/node_modules/url-search-params/build/url-search-params.js
- server replied: Not Found
TypeError: mocha.setup is not a function. (In 'mocha.setup('tdd')',
'mocha.setup' is undefined)
mocha was not initialized within 1ms of the page loading. Make sure
to call `mocha.ui` or `mocha.setup`.
TypeError: Attempting to change the setter of an unconfigurable property.
TypeError: Attempting to change the setter of an unconfigurable property.



signature.asc
Description: OpenPGP digital signature

Bug#887969: nbdkit FTBFS: test failures

[Adrian Bunk]

Source: nbdkit
Version: 1.1.25-1
Severity: serious

Some recent change in unstable makes nbdkit FTBFS:

https://tests.reproducible-builds.org/debian/history/nbdkit.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nbdkit.html

...
FAIL: test-connect
==

/build/1st/nbdkit-1.1.25/src/nbdkit -U /tmp/nbdkitod2Ach/sock -P 
/tmp/nbdkitod2Ach/pid -f -v 
/build/1st/nbdkit-1.1.25/plugins/example1/.libs/nbdkit-example1-plugin.so
nbdkit: debug: TLS disabled: could not load TLS certificates
nbdkit: debug: registering 
/build/1st/nbdkit-1.1.25/plugins/example1/.libs/nbdkit-example1-plugin.so
nbdkit: debug: registered 
/build/1st/nbdkit-1.1.25/plugins/example1/.libs/nbdkit-example1-plugin.so (name 
example1)
nbdkit: debug: 
/build/1st/nbdkit-1.1.25/plugins/example1/.libs/nbdkit-example1-plugin.so: load
nbdkit: debug: 
/build/1st/nbdkit-1.1.25/plugins/example1/.libs/nbdkit-example1-plugin.so: 
config_complete
nbdkit: debug: bound to unix socket /tmp/nbdkitod2Ach/sock
nbdkit: debug: written pidfile /tmp/nbdkitod2Ach/pid
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: trace: set_backend "appliance"
libguestfs: trace: set_backend = 0
libguestfs: create: flags = 0, handle = 0x5557d4a15060, program = test-connect
libguestfs: trace: add_drive "" "format:raw" "protocol:nbd" 
"server:unix:/tmp/nbdkitod2Ach/sock"
libguestfs: trace: add_drive = 0
libguestfs: trace: launch
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: version
libguestfs: trace: version = 
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
libguestfs: launch: program=test-connect
libguestfs: launch: version=1.36.11
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=/tmp/libguestfsmRVUvn
libguestfs: launch: umask=0022
libguestfs: launch: euid=
libguestfs: is_openable: /dev/kvm: No such file or directory
libguestfs: trace: get_backend_setting "force_tcg"
libguestfs: trace: get_backend_setting = NULL (error)
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/x86_64-linux-gnu/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-/appliance.d
supermin: version: 5.1.19
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/.guestfs-/lock
supermin: if-newer: output does not need rebuilding
libguestfs: finished building supermin appliance
libguestfs: begin testing qemu features
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: checking for previously cached test results of 
/usr/bin/qemu-system-x86_64, in /var/tmp/.guestfs-
libguestfs: loading previously cached test results
libguestfs: qemu version: 2.11
libguestfs: qemu mandatory locking: yes
libguestfs: trace: get_sockdir
libguestfs: trace: get_sockdir = "/tmp"
libguestfs: finished testing qemu features
libguestfs: trace: get_backend_setting "gdb"
libguestfs: trace: get_backend_setting = NULL (error)
libguestfs: command: run: dmesg | grep -Eoh 'lpj=[[:digit:]]+'
dmesg: read kernel buffer failed: Operation not permitted
libguestfs: read_lpj_from_dmesg: external command exited with error status 1
libguestfs: read_lpj_from_files: no boot messages files are readable
[00149ms] /usr/bin/qemu-system-x86_64 \
-global virtio-blk-pci.scsi=off \
-enable-fips \
-nodefaults \
-display none \
-machine accel=kvm:tcg \
-m 500 \
-no-reboot \
-rtc driftfix=slew \
-no-hpet \
-global kvm-pit.lost_tick_policy=discard \
-kernel /var/tmp/.guestfs-/appliance.d/kernel \
-initrd /var/tmp/.guestfs-/appliance.d/initrd \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-pci,rng=rng0 \
-device virtio-scsi-pci,id=scsi \
-drive 
file=nbd:unix:/tmp/nbdkitod2Ach/sock,cache=writeback,format=raw,id=hd0,if=none \
-device scsi-hd,drive=hd0 \
-drive 
file=/var/tmp/.guestfs-/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw
 \
-device scsi-hd,drive=appliance \
-device virtio-serial-pci \
-serial stdio \
-device sga \
-chardev socket,path=/tmp/libguestfsooHB7t/guestfsd.sock,id=channel0 \
-device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
-append 'panic=1 console=ttyS0 edd=off udevtimeout=6000 

Bug#887968: zoneminder FTBFS with glibc 2.26

[Adrian Bunk]

Source: zoneminder
Version: 1.30.4+dfsg-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zoneminder.html

...
/build/1st/zoneminder-1.30.4+dfsg/src/zm_comms.h: In member function 'virtual 
int CommsBase::readV(const iovec*, int)':
/build/1st/zoneminder-1.30.4+dfsg/src/zm_comms.h:98:20: error: '::readv' has 
not been declared
 int nBytes = ::readv( mRd, iov, iovcnt );
^

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 887965 887964
Bug #887965 [python-matplotlib] python-matplotlib: missing dependency on 
python-backports.functools-lru-cache
Bug #887964 [python-matplotlib] python-matplotlib: missing dependency on 
python-backports.functools-lru-cache
Added indication that 887964 affects 
src:python-periodictable,src:python-shapely,src:python-cycler,src:nibabel,src:python-bumps,python-sphinx,src:python-scipy
Merged 887964 887965
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887964
887965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887967: transgui FTBFS with recent fpc: fpcmake: Error: Target "linux", package "rtl" not found

[Adrian Bunk]

Source: transgui
Version: 5.0.1-5
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgui.html

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/transgui-5.0.1'
fpcmake
Processing Makefile.fpc
Error: Target "linux", package "rtl" not found
debian/rules:17: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1

Bug#887964: python-matplotlib: missing dependency on python-backports.functools-lru-cache

[Stuart Prescott]

Package: python-matplotlib
Version: 2.1.1-1
Severity: serious
Justification: Policy 3.5, packages must specify all dependencies

Dear Maintainer,

Thanks for the new version of matplotlib!

The new version of matplotlib introduces a dependency on
python-backports.functools-lru-cache for the Python 2 version of the
package. Omitting this package makes matplotlib more or less
unusable:

$ python -c "import matplotlib"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/matplotlib/__init__.py", line 128, in 

from matplotlib.rcsetup import defaultParams, validate_backend, cycler
  File "/usr/lib/python2.7/dist-packages/matplotlib/rcsetup.py", line 29, in 

from matplotlib.fontconfig_pattern import parse_fontconfig_pattern
  File "/usr/lib/python2.7/dist-packages/matplotlib/fontconfig_pattern.py", 
line 32, in 
from backports.functools_lru_cache import lru_cache
ImportError: No module named backports.functools_lru_cache

The code in question does:

try:
from functools import lru_cache
except ImportError:
from backports.functools_lru_cache import lru_cache

python-backports.functools-lru-cache is included in the build-dependencies
and so the build-time tests pass, but the package tests do not:

https://ci.debian.net/packages/m/matplotlib/unstable/amd64/

cheers
Stuart

Processed: python-matplotlib: missing dependency on python-backports.functools-lru-cache

[Debian Bug Tracking System]

Processing control commands:

> affects -1 python-sphinx src:python-shapely src:python-cycler 
> src:python-scipy src:python-bumps src:python-periodictable src:nibabel
Bug #887965 [python-matplotlib] python-matplotlib: missing dependency on 
python-backports.functools-lru-cache
Added indication that 887965 affects python-sphinx, src:python-shapely, 
src:python-cycler, src:python-scipy, src:python-bumps, 
src:python-periodictable, and src:nibabel

-- 
887965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887965: python-matplotlib: missing dependency on python-backports.functools-lru-cache

[Adrian Bunk]

Package: python-matplotlib
Version: 2.1.1-1
Severity: serious
Control: affects -1 python-sphinx src:python-shapely src:python-cycler 
src:python-scipy src:python-bumps src:python-periodictable src:nibabel 

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-shapely.html

...
running build_sphinx
creating /build/1st/python-shapely-1.6.3/build/sphinx
creating /build/1st/python-shapely-1.6.3/build/sphinx/doctrees
creating /build/1st/python-shapely-1.6.3/build/sphinx/html
Running Sphinx v1.6.6

Extension error:
Could not import extension matplotlib.sphinxext.only_directives (exception: No 
module named backports.functools_lru_cache)
debian/rules:31: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1

Bug#887939: marked as done (libpdfbox-java FTBFS: rm: cannot remove debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 22 Jan 2018 04:19:28 +
with message-id 
and subject line Bug#887939: fixed in libpdfbox-java 1:1.8.13-2
has caused the Debian Bug report #887939,
regarding libpdfbox-java FTBFS: rm: cannot remove 
debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save:
 No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdfbox-java
Version: 1:1.8.13-1
Severity: serious

Some recent change in unstable makes libpdfbox-java FTBFS:

https://tests.reproducible-builds.org/debian/history/libpdfbox-java.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpdfbox-java.html

...
dh_installexamples
# empty directory since we remove the contents during repackaging.
rmdir --verbose --parents --ignore-fail-on-non-empty 
/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox/resources/pdfa
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox/resources/pdfa'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox/resources'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main'
rm 
/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save
rm: cannot remove 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save':
 No such file or directory
debian/rules:31: recipe for target 'override_dh_installexamples' failed
make[1]: *** [override_dh_installexamples] Error 1
--- End Message ---
--- Begin Message ---
Source: libpdfbox-java
Source-Version: 1:1.8.13-2

We believe that the bug you reported is fixed in the latest version of
libpdfbox-java, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libpdfbox-java package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Jan 2018 19:19:48 -0800
Source: libpdfbox-java
Binary: libpdfbox-java libpdfbox-java-doc libjempbox-java libjempbox-java-doc 
libfontbox-java libfontbox-java-doc
Architecture: source all
Version: 1:1.8.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 libfontbox-java - Java font library
 libfontbox-java-doc - Java font library (Documentation)
 libjempbox-java - XMP Compatible Java Library
 libjempbox-java-doc - XMP Compatible Java Library (documentation)
 libpdfbox-java - PDF library for Java
 libpdfbox-java-doc - PDF library for Java (documentation)
Closes: 887939
Changes:
 libpdfbox-java (1:1.8.13-2) unstable; urgency=medium
 .
   * Address FTBFS in debian/rules (Closes: #887939)
   * Use https URL for Homepage in debian/control
   * Bump Standards-Version to 4.1.3
   * Remove unused debian/patches.
Checksums-Sha1:
 

Bug#887939: Pending fixes for bugs in the libpdfbox-java package

[pkg-java-maintainers]

tag 887939 + pending
thanks

Some bugs in the libpdfbox-java package are closed in revision
c050728e2d3f05fa770977cfe4f61e49d31794b6 in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libpdfbox-java.git/commit/?id=c050728

Commit message:

Address FTBFS (Closes: #887939)

Processed: Pending fixes for bugs in the libpdfbox-java package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 887939 + pending
Bug #887939 [src:libpdfbox-java] libpdfbox-java FTBFS: rm: cannot remove 
debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save:
 No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#883872: bitlbee: Extremely incomplete d/copyright

[Wilmer van der Gaast]

severity 883872 minor

Machine-readable is optional, and although not all attributed by exact
file or directory, everything in the existing file *is* accounted for
(Lintux == me at, hmm, 16 years old, and various files also in lib/
still come from Gaim which is mentioned.)

Patches for a fully comprehensive copyright file are welcome :-)

Processed (with 5 errors): Re: Bug#883872: bitlbee: Extremely incomplete d/copyright

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 883872 minor
Bug #883872 [src:bitlbee] bitlbee: Extremely incomplete d/copyright
Severity set to 'minor' from 'serious'
> Machine-readable is optional, and although not all attributed by exact
Unknown command or malformed arguments to command.
> file or directory, everything in the existing file *is* accounted for
Unknown command or malformed arguments to command.
> (Lintux == me at, hmm, 16 years old, and various files also in lib/
Unknown command or malformed arguments to command.
> still come from Gaim which is mentioned.)
Unknown command or malformed arguments to command.
> Patches for a fully comprehensive copyright file are welcome :-)
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
883872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887952: Revert to Arch:all

[Felix Lechner]

Package: golang-github-jacobsa-crypto
Version: 0.0_git2016.0.293ce0c+dfsg1-5
Severity: serious

For a brief time, the package is being marked Arch:any to produce
detailed logs. We would like to support additional release
architectures, but the package is Golang source (and autopkgtest did
not run on the affected architectures).

The package should be marked Arch:all before being allowed into testing.

Bug#887818: marked as done (pylint FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 22 Jan 2018 00:05:46 +
with message-id 
and subject line Bug#887818: fixed in pylint 1.8.1-1
has caused the Debian Bug report #887818,
regarding pylint FTBFS: test failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint
Version: 1.7.4-2
Severity: serious

Some recent change in unstable makes pylint FTBFS:

https://tests.reproducible-builds.org/debian/history/pylint.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pylint.html

...
=== FAILURES ===
 
test_functionality[func_noerror_decorator_scope.py-/build/1st/pylint-1.7.4/pylint/test/messages/func_noerror_decorator_scope.txt-dependencies1]
 

module_file = 'func_noerror_decorator_scope.py'
messages_file = 
'/build/1st/pylint-1.7.4/pylint/test/messages/func_noerror_decorator_scope.txt'
dependencies = []

@pytest.mark.parametrize("module_file,messages_file,dependencies", 
gen_tests(FILTER_RGX))
def test_functionality(module_file, messages_file, dependencies):

LT = LintTestUpdate() if UPDATE else LintTestUsingModule()

LT.module = module_file.replace('.py', '')
LT.output = messages_file
LT.depends = dependencies or None
LT.INPUT_DIR = INPUT_DIR
>   LT._test_functionality()

pylint/test/test_func.py:65: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
pylint/testutils.py:287: in _test_functionality
self._test(tocheck)
pylint/testutils.py:306: in _test
self._check_result(self.linter.reporter.finalize())
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
got = "W: 11:Test: Unused variable '__class__'\n"

def _check_result(self, got):
>   assert self._get_expected().strip()+'\n' == got.strip()+'\n'
E   AssertionError

pylint/testutils.py:290: AssertionError
 
test_functionality[func_noerror_classes_meth_could_be_a_function.py-/build/1st/pylint-1.7.4/pylint/test/messages/func_noerror_classes_meth_could_be_a_function.txt-dependencies2]
 

module_file = 'func_noerror_classes_meth_could_be_a_function.py'
messages_file = 
'/build/1st/pylint-1.7.4/pylint/test/messages/func_noerror_classes_meth_could_be_a_function.txt'
dependencies = []

@pytest.mark.parametrize("module_file,messages_file,dependencies", 
gen_tests(FILTER_RGX))
def test_functionality(module_file, messages_file, dependencies):

LT = LintTestUpdate() if UPDATE else LintTestUsingModule()

LT.module = module_file.replace('.py', '')
LT.output = messages_file
LT.depends = dependencies or None
LT.INPUT_DIR = INPUT_DIR
>   LT._test_functionality()

pylint/test/test_func.py:65: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
pylint/testutils.py:287: in _test_functionality
self._test(tocheck)
pylint/testutils.py:306: in _test
self._check_result(self.linter.reporter.finalize())
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
...
=== 94 failed, 453 passed, 35 skipped, 1 deselected in 61.51 seconds ===
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: pylint
Source-Version: 1.8.1-1

We believe that the bug you reported is fixed in the latest version of
pylint, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pylint package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 17:26:49 -0500
Source: pylint
Binary: pylint pylint-doc pylint3
Architecture: source all
Version: 1.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 887447 network-manager
Bug #887447 [src:network-manager-ssh] network-manager-ssh FTBFS with 
network-manager 1.10.2-1
Bug reassigned from package 'src:network-manager-ssh' to 'network-manager'.
No longer marked as found in versions network-manager-ssh/1.2.6-1.
Ignoring request to alter fixed versions of bug #887447 to the same values 
previously set
> forcemerge 887815 887447
Bug #887815 {Done: Michael Biebl } [network-manager] 
network-manager-iodine FTBFS with network-manager 1.10.2-1
Bug #887447 [network-manager] network-manager-ssh FTBFS with network-manager 
1.10.2-1
Marked Bug as done
Added indication that 887447 affects network-manager-iodine
Marked as fixed in versions network-manager/1.10.2-2.
Marked as found in versions network-manager/1.10.2-1.
Added tag(s) buster and sid.
Merged 887447 887815
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887447
887815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#868393: marked as done (alleyoop: Please drop the (build-)dependency against gnome-vfs)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 23:10:19 +
with message-id 
and subject line Bug#887947: Removed package(s) from unstable
has caused the Debian Bug report #868393,
regarding alleyoop: Please drop the (build-)dependency against gnome-vfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
868393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alleyoop
Version: 0.9.8-1
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Version: 0.9.8-1+rm

Dear submitter,

as the package alleyoop has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887947

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#868418: marked as done (gnome-hearts: Please drop the (build-)dependency against gnome-vfs)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 23:09:30 +
with message-id 
and subject line Bug#887946: Removed package(s) from unstable
has caused the Debian Bug report #868418,
regarding gnome-hearts: Please drop the (build-)dependency against gnome-vfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
868418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-hearts
Version: 0.3-2.2
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Version: 0.3-2.2+rm

Dear submitter,

as the package gnome-hearts has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887946

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#887798: firefox-esr: impossible to connect to Google domains

[Vincent Lefevre]

On 2018-01-22 07:12:15 +0900, Mike Hommey wrote:
> On Sun, Jan 21, 2018 at 06:33:00PM +, Viktor Jägersküpper wrote:
> > On Sat, 20 Jan 2018 11:30:56 +0100 Vincent Lefevre 
> > wrote:
> > > (...)
> > > As a temporary and insecure workaround, I can avoid this error by
> > > setting security.OCSP.require to false, even though the error was
> > > not about OCSP.
> > 
> > Hello Vincent,
> > 
> > this is not a bug in Firefox (ESR). See this thread (works in Firefox
> > only with "security.OCSP.require" set to "false" at the moment):
> > https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/MMO3HSYghwQ/XLRuxWtJAwAJ
> > 
> > The Google engineers are working on fixing this issue, so that this OCSP
> > setting can be set to "true" again.
> 
> And they apparently fixed it now.

This is not fixed yet: I still get an error from Firefox, and also
from curl:

zira:~> curl --cert-status https://www.google.com
curl: (91) No OCSP response received

Actually the problem with Firefox 52 ESR is that its logic to give
the error message is broken: instead of SEC_ERROR_UNKNOWN_ISSUER,
it should have been an OCSP related error. But Firefox Nightly
correctly reports a SEC_ERROR_OCSP_SERVER_ERROR error.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#887934: marked as done (pd-zexy FTBFS on amd64: FAIL: runtests.sh)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 22:49:45 +
with message-id 
and subject line Bug#887934: fixed in pd-zexy 2.2.7-1
has caused the Debian Bug report #887934,
regarding pd-zexy FTBFS on amd64: FAIL: runtests.sh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-zexy
Version: 2.2.6-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes pd-zexy FTBFS on amd64:

https://tests.reproducible-builds.org/debian/history/pd-zexy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-zexy.html

...
/usr/bin/make  check-TESTS
make[3]: Entering directory '/build/1st/pd-zexy-2.2.6/tests'
make[4]: Entering directory '/build/1st/pd-zexy-2.2.6/tests'
FAIL: runtests.sh

Testsuite summary for zexy 2.2.6

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to zmoel...@iem.at

Makefile:561: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: pd-zexy
Source-Version: 2.2.7-1

We believe that the bug you reported is fixed in the latest version of
pd-zexy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-zexy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 23:29:12 +0100
Source: pd-zexy
Binary: pd-zexy
Architecture: source
Version: 2.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 pd-zexy- General Purpose addon library for Pd
Closes: 887934
Changes:
 pd-zexy (2.2.7-1) unstable; urgency=medium
 .
   * New upstream version 2.2.7
 Closes: #887934
 * Dropped patches aplied upstream
   * Patch to fix spelling errors
   * Fixed spelling error in long description
   * Switched homepage to https://
   * Modernized Vcs-* stanzas
   * Updated d/watch
   * Switched build-system to dh-11
 * Refreshed B-Ds for build-system switch
 * Dropped d/control.in
   * Use SOURCE_DATE_EPOCH to calculate build-date
   * Use https:// for d/copyright format URL
   * Bumped standards version to 4.1.3
Checksums-Sha1:
 a051d274551557ad5d31ecafc5be01b054740558 2058 pd-zexy_2.2.7-1.dsc
 3e0d541a4efe0cba3ba8a835f5b7fc8aba81a558 201865 pd-zexy_2.2.7.orig.tar.gz
 3335b8a4208626f22e98312935f68dbc2bd2e811 8492 pd-zexy_2.2.7-1.debian.tar.xz
 ab013a06908aecb82666da193aa4eb4d09da115e 5753 pd-zexy_2.2.7-1_amd64.buildinfo
Checksums-Sha256:
 2d8b2f4c1881549765aee5188ecffb069d27935ed932e8d90c2d26089c5e1b01 2058 
pd-zexy_2.2.7-1.dsc
 c23b8161bf8550aad6b50e265be60cab28599bc6fe037d4f4fd575684f261d76 201865 
pd-zexy_2.2.7.orig.tar.gz
 beacb09e6e3c9b6371fab6a7cf44332a1fc1997831bf056793cd1520fae4650d 8492 
pd-zexy_2.2.7-1.debian.tar.xz
 d598b1fe02aa8032f9d54d4d8d9deb2d4b626a95a84e519c6a9bda44fa06970a 5753 
pd-zexy_2.2.7-1_amd64.buildinfo
Files:
 f173e42774dd967bfa50f659b077eae1 2058 sound optional pd-zexy_2.2.7-1.dsc
 60944e8fe0327ab2953442e975149716 201865 sound optional 
pd-zexy_2.2.7.orig.tar.gz
 64240ccd01ec0f2e65e3a40abb8eee47 8492 sound optional 
pd-zexy_2.2.7-1.debian.tar.xz
 2bed14d53ca0d9d8c4dd6d0663013e2c 5753 sound optional 
pd-zexy_2.2.7-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlplFIAACgkQtlAZxH96
NvjS+g/8DncTBEXvg0Lv0VCSpiQ5RkgsF0r57k9YZPdPUclUMDXRaoZysK+Mdi+A
IJd7niBCHsBERFEdzb3GozAPzoUZKJVyw28EdXvfbKwEszYi8S2bNugk8RN6ydSm

Bug#887798: marked as done (firefox-esr: impossible to connect to Google domains)

[Debian Bug Tracking System]

Your message dated Mon, 22 Jan 2018 07:12:15 +0900
with message-id <20180121221213.khsjahvme2kya...@glandium.org>
and subject line Re: Bug#887798: firefox-esr: impossible to connect to Google 
domains
has caused the Debian Bug report #887798,
regarding firefox-esr: impossible to connect to Google domains
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 52.5.3esr-1
Severity: grave
Justification: renders package unusable

It is no longer possible to connect to Google domains. For instance:


Your connection is not secure

The owner of www.google.fr has configured their website improperly. To
protect your information from being stolen, Firefox has not connected
to this website.

This site uses HTTP Strict Transport Security (HSTS) to specify that
Firefox may only connect to it securely. As a result, it is not
possible to add an exception for this certificate.


And after clicking on "Advanced":


www.google.fr uses an invalid security certificate.

The certificate is not trusted because the issuer certificate is unknown. The 
server might not be sending the appropriate intermediate certificates. An 
additional root certificate may need to be imported.

Error code: SEC_ERROR_UNKNOWN_ISSUER


This occurs with various Google domains (google.com, google.fr,
goo.gl), with and without -safe-mode.

Opera, lynx, curl and wget do not have this problem.

-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.4
ii  fontconfig2.12.6-0.1
ii  libasound21.1.3-5
ii  libatk1.0-0   2.26.1-2
ii  libc6 2.26-4
ii  libcairo-gobject2 1.14.10-1
ii  libcairo2 1.14.10-1
ii  libdbus-1-3   1.12.2-1
ii  libdbus-glib-1-2  0.108-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.12.6-0.1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:7.2.0-19
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.3-1
ii  libgtk-3-03.22.26-2
ii  libgtk2.0-0   2.24.31-5
ii  libhunspell-1.6-0 1.6.2-1
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.16-1+b1
ii  libnss3   2:3.34.1-1
ii  libpango-1.0-01.40.14-1
ii  libsqlite3-0  3.21.0-1
ii  libstartup-notification0  0.12-5
ii  libstdc++67.2.0-19
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-5

firefox-esr recommends no packages.

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-3
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-1
pn  mozplugger 

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On Sun, Jan 21, 2018 at 06:33:00PM +, Viktor Jägersküpper wrote:
> On Sat, 20 Jan 2018 11:30:56 

Bug#887934: marked as pending

[IOhannes m zmölnig]

tag 887934 pending
thanks

Hello,

Bug #887934 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://anonscm.debian.org/git/pkg-multimedia/pd-zexy.git/commit/?id=12f57b0

---
commit 12f57b01bc47c4e7b7fc25d09c4c8b02ae8b1e31
Author: IOhannes m zmölnig 
Date:   Sun Jan 21 23:22:16 2018 +0100

Ready for upload to unstable.

diff --git a/debian/changelog b/debian/changelog
index 07596fd..a3d4368 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,22 @@
+pd-zexy (2.2.7-1) unstable; urgency=medium
+
+  * New upstream version 2.2.7
+Closes: #887934
+* Dropped patches aplied upstream
+  * Patch to fix spelling errors
+  * Fixed spelling error in long description
+  * Switched homepage to https://
+  * Modernized Vcs-* stanzas
+  * Updated d/watch
+  * Switched build-system to dh-11
+* Refreshed B-Ds for build-system switch
+* Dropped d/control.in
+  * Use SOURCE_DATE_EPOCH to calculate build-date
+  * Use https:// for d/copyright format URL
+  * Bumped standards version to 4.1.3
+
+ -- IOhannes m zmölnig (Debian/GNU)   Sun, 21 Jan 2018 
23:29:12 +0100
+
 pd-zexy (2.2.6-2) unstable; urgency=medium
 
   * Backported upstream fix for reproducible builds

Processed: Bug#887934 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 887934 pending
Bug #887934 [src:pd-zexy] pd-zexy FTBFS on amd64: FAIL: runtests.sh
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 887818 + pending
Bug #887818 [src:pylint] pylint FTBFS: test failures
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887664: Bug#887688: debhelper: empty build of src:ck

[Sven Joachim]

On 2018-01-21 23:24 +0200, Adrian Bunk wrote:

> On Fri, Jan 19, 2018 at 07:51:00PM +, Niels Thykier wrote:
>>...
>>   The question now is: How many packages are affected by it?  If it is
>> sufficiently low, it might be worth doing the clean up now to simplify
>> packaging in general.  But in worst case, we will have to revert for now
>> and reintroduce this to compat 12.
>
> My current list for "builds with 11 and FTBFS with 11.1.3" is:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apr.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ck.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cpputest.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-handbook.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/iaxmodem.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/moarvm.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openal-soft.html

Those all seem to have the same problem mentioned by Simon: a build/
directory exists, the build target is phony in debian/rules, but there
is no explicit build rule.

> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jscommunicator.html

Here make also considers that there is nothing to be done for 'build', but
this time there is no build directory in the source package.  Huh?

> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/biojava-live.html

This ends in

,
| dh_installdocs
| make[1]: Leaving directory '/build/1st/biojava-live-1.7.1'
|  dpkg-genbuildinfo --build=binary
| dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
| dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary subprocess 
returned exit status 25
`

In other words, dh_installdeb was not run, apparently because there is a broken
explicit rule for the binary-indep target.

> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jansson.html

Here the error is

,
| make[1]: Leaving directory '/build/1st/jansson-2.10'
|dh_update_autotools_config -Nlibjansson-doc
|dh_autoreconf -Nlibjansson-doc
| dh_autoreconf: Can only be run once, see dh-autoreconf(7)
| debian/rules:11: recipe for target 'build' failed
`

which seems to have a similar cause as #887482.

> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scidavis.html

Failed because 'dh_makeshlibs --no-act' returned an error.  Niels might
know why this is now the case and used to be different.

Cheers,
   Sven

Bug#887942: marked as done (node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling symlink)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 23:56:33 +0200
with message-id <20180121215633.GC20971@localhost>
and subject line Closing duplicate, sorry for the noise
has caused the Debian Bug report #887942,
regarding node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling 
symlink
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-node-uuid
Version: 1.4.7-1
Severity: serious
Control: affects -1 src:node-npmrc

/usr/lib/nodejs/node-uuid/index.js is a dangling symlink.
--- End Message ---
--- Begin Message ---
Closing duplicate, sorry for the noise.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Processed: node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling symlink

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:node-npmrc
Bug #887942 [node-node-uuid] node-node-uuid: /usr/lib/nodejs/node-uuid/index.js 
is a dangling symlink
Added indication that 887942 affects src:node-npmrc

-- 
887942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887942: node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling symlink

[Adrian Bunk]

Package: node-node-uuid
Version: 1.4.7-1
Severity: serious
Control: affects -1 src:node-npmrc

/usr/lib/nodejs/node-uuid/index.js is a dangling symlink.

Bug#887920: marked as done (speech-tools binary-all FTBFS: config/common_make_rules:49: ../config/system.mak: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 21:36:05 +
with message-id 
and subject line Bug#887920: fixed in speech-tools 1:2.5.0-4
has caused the Debian Bug report #887920,
regarding speech-tools binary-all FTBFS: config/common_make_rules:49: 
../config/system.mak: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: speech-tools
Version: 1:2.5.0-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=speech-tools=all=1%3A2.5.0-3=1516484001=0

...
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
cd doc && /usr/bin/make doc
make[2]: Entering directory '/<>/doc'
../config/common_make_rules:49: ../config/system.mak: No such file or directory
../config/common_make_rules:49: ../config/system.mak: No such file or directory
make[2]: *** No rule to make target '../config/system.mak'.  Stop.
--- End Message ---
--- Begin Message ---
Source: speech-tools
Source-Version: 1:2.5.0-4

We believe that the bug you reported is fixed in the latest version of
speech-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated speech-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 21:57:13 +0100
Source: speech-tools
Binary: libestools2.5 libestools-dev speech-tools speech-tools-doc
Architecture: source
Version: 1:2.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Paul Gevers 
Description:
 libestools-dev - Edinburgh Speech Tools Library - developer's libraries
 libestools2.5 - Edinburgh Speech Tools Library
 speech-tools - Edinburgh Speech Tools - user binaries
 speech-tools-doc - Documentation for the Edinburgh Speech Tools
Closes: 887920
Changes:
 speech-tools (1:2.5.0-4) unstable; urgency=medium
 .
   * Fix another FTBFS and missing documentation by also building the
 binary files on arch:all (Closes: #887920)
Checksums-Sha1:
 a0445c8fa001aa5fdf11e1f50fe6fe5af5228ce3 2044 speech-tools_2.5.0-4.dsc
 b5bef25e018f92d6de7fd0cdf94ed22380fa21ba 41024 
speech-tools_2.5.0-4.debian.tar.xz
Checksums-Sha256:
 3fae53d7b4c8a70d15d16c00e9f2d5ee0dad2b66705c02e636feff0a2432f545 2044 
speech-tools_2.5.0-4.dsc
 ee52507ed5c258b798cd3c11d39ae3f52a1a80f575db7623f9e0ebf947fdac0f 41024 
speech-tools_2.5.0-4.debian.tar.xz
Files:
 1fc0d9c1363e3976e9f5697a8cbf72ba 2044 sound optional speech-tools_2.5.0-4.dsc
 8f1766c3d128abacf5f73c1b566d2098 41024 sound optional 
speech-tools_2.5.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlpk/1AACgkQnFyZ6wW9
dQoF9Qf5AXO83+R7lECthbBXSNuIDL2ohc/NZLMFtr71Iz/xPaCHEyZgmSq84Bo6
HHLqp/WuyHruESzqrMOKXYL51ESQLBQ+k1hlqWaMfUEIB0yHdGilY1Y89CvBjDdr
bkPmJCXzSTh6/MmHwvpnoPsVsMj+LvA6cWlVBeZ/PT0Dd8+Lyo+AwMYETjmsJk9w
Npz9rX31dDAE10PRj/fSkVfkPJTcNPtehP2lp+6knLIv+ybVoUfoSTL9szKvGRab
N7v4f8S52jW/hIhQPk0Kq4hzpNi5+qH91ioHwR8DLgU2i8qD5hCB9n6a626UktgK
7tALCWbG+JwvUdsireEBk+lR6eRLoA==
=/lCA
-END PGP SIGNATURE End Message ---

Bug#884626: marked as done (liblinux-dvb-perl FTBFS with linux-libc-dev 4.14.2-1)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 21:35:30 +
with message-id 
and subject line Bug#884626: fixed in liblinux-dvb-perl 1.03-2
has caused the Debian Bug report #884626,
regarding liblinux-dvb-perl FTBFS with linux-libc-dev 4.14.2-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblinux-dvb-perl
Version: 1.03-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/liblinux-dvb-perl.html

...
   dh_auto_build
make -j1
make[1]: Entering directory '/build/1st/liblinux-dvb-perl-1.03'
cp DVB.pm blib/lib/Linux/DVB.pm
Running Mkbootstrap for DVB ()
chmod 644 "DVB.bs"
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- DVB.bs 
blib/arch/auto/Linux/DVB/DVB.bs 644
"/usr/bin/perl" "/usr/share/perl/5.26/ExtUtils/xsubpp"  -typemap 
'/usr/share/perl/5.26/ExtUtils/typemap' -typemap 
'/build/1st/liblinux-dvb-perl-1.03/typemap'  DVB.xs > DVB.xsc
mv DVB.xsc DVB.c
x86_64-linux-gnu-gcc -c   -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -DVERSION=\"1.03\" 
-DXS_VERSION=\"1.03\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE"   DVB.c
DVB.xs:193:10: error: 'DMX_KERNEL_CLIENT' undeclared here (not in a function)
   CONST (DMX_KERNEL_CLIENT),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:195:10: error: 'DMX_SOURCE_FRONT0' undeclared here (not in a function)
   CONST (DMX_SOURCE_FRONT0),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:196:10: error: 'DMX_SOURCE_FRONT1' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT0'?
   CONST (DMX_SOURCE_FRONT1),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:197:10: error: 'DMX_SOURCE_FRONT2' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT1'?
   CONST (DMX_SOURCE_FRONT2),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:198:10: error: 'DMX_SOURCE_FRONT3' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT2'?
   CONST (DMX_SOURCE_FRONT3),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:200:10: error: 'DMX_SOURCE_DVR0' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT0'?
   CONST (DMX_SOURCE_DVR0),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:201:10: error: 'DMX_SOURCE_DVR1' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_DVR0'?
   CONST (DMX_SOURCE_DVR1),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:202:10: error: 'DMX_SOURCE_DVR2' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_DVR1'?
   CONST (DMX_SOURCE_DVR2),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:203:10: error: 'DMX_SOURCE_DVR3' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_DVR2'?
   CONST (DMX_SOURCE_DVR3),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
Makefile:329: recipe for target 'DVB.o' failed
make[1]: *** [DVB.o] Error 1
--- End Message ---
--- Begin Message ---
Source: liblinux-dvb-perl
Source-Version: 1.03-2

We believe that the bug you reported is fixed in the latest version of
liblinux-dvb-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nick Morrott  (supplier of updated 

Bug#887941: golang-gitaly-proto: missing build dependency on a Go compiler package

[Adrian Bunk]

Source: golang-gitaly-proto
Version: 0.26.0+dfsg-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gitaly-proto.html

...
   dh_auto_build -O--buildsystem=golang -O--package=golang-gitaly-proto-dev
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-gitaly-proto-0.26.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-gitaly-proto-0.26.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1
Can't exec "go": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 358.
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-gitaly-proto-0.26.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-gitaly-proto-0.26.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 failed to execute: No child processes
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/golang-gitaly-proto-0.26.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/build/1st/golang-gitaly-proto-0.26.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 returned exit code 10
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2

Bug#887688: [debhelper-devel] Bug#887688: debhelper: empty build of src:ck

[Adrian Bunk]

On Fri, Jan 19, 2018 at 07:51:00PM +, Niels Thykier wrote:
>...
>   The question now is: How many packages are affected by it?  If it is
> sufficiently low, it might be worth doing the clean up now to simplify
> packaging in general.  But in worst case, we will have to revert for now
> and reintroduce this to compat 12.

My current list for "builds with 11 and FTBFS with 11.1.3" is:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apr.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/biojava-live.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cpputest.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-handbook.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/iaxmodem.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jansson.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jscommunicator.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/moarvm.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openal-soft.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scidavis.html

This list might not be complete, but I'd expect it to stay < 20.

This list is "builds with 11 and FTBFS with 11.1.3",
no effort has been made to check whether it is all the same problem.

> Thanks,
> ~Niels

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#885310: marked as done (jumpnbump: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 21:09:35 +
with message-id 
and subject line Bug#885310: fixed in jumpnbump 1.60-3
has caused the Debian Bug report #885310,
regarding jumpnbump: Depends on unmaintained pygtk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gumpnbump
Version: 1.60-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: jumpnbump
Source-Version: 1.60-3

We believe that the bug you reported is fixed in the latest version of
jumpnbump, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fabian Greffrath  (supplier of updated jumpnbump package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 20:41:57 +0100
Source: jumpnbump
Binary: jumpnbump
Architecture: source amd64
Version: 1.60-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Fabian Greffrath 
Description:
 jumpnbump  - cute multiplayer platform game with bunnies
Closes: 885310
Changes:
 jumpnbump (1.60-3) unstable; urgency=medium
 .
   * Do not build and install the jumpnbump-menu anymore (Closes: #885310).
   * Update Vcs-* to point to salsa.debian.org.
   * Remove trailing whitespace from debian/changelog.
   * Bump debhelper compat to 11.
   * Use secure debian/copyright format URI.
   * Bump Standards-Version to 4.1.3.
   * Install AppStream metadata to the proper location.
Checksums-Sha1:
 4bf2ac57a2cd3306529e018569c75db95a43f623 2041 jumpnbump_1.60-3.dsc
 cd69e6f5a42b64567138089abe36757276d9d4a1 8416 jumpnbump_1.60-3.debian.tar.xz
 9c528904aa3d563d933fa3792a929bc84901f969 101076 
jumpnbump-dbgsym_1.60-3_amd64.deb
 ce70daa776e465b346a07dfd6b18b0d6b998e4a2 11041 jumpnbump_1.60-3_amd64.buildinfo
 822a3384abb40070ec0a26f8de2019f0f6b66000 242568 jumpnbump_1.60-3_amd64.deb
Checksums-Sha256:
 c142648ba9e9292619b0d007045d46c3ddbf70257e0aa2b730759118fd7be360 2041 
jumpnbump_1.60-3.dsc
 db906a56e84205aff9b3f44db5cb22f6437487da6c86d5b9b13c7dd2d2655437 8416 
jumpnbump_1.60-3.debian.tar.xz
 d18badebd407b03c15841a2d812ab0f1ded3f15ee8bdce0db482bfab5e9b7fac 101076 
jumpnbump-dbgsym_1.60-3_amd64.deb
 37b3cce05a1591cd708f2ce9be3876634ff26e5acb31630d2d25eec850951dde 11041 
jumpnbump_1.60-3_amd64.buildinfo
 914b0fa93200608079ee7570540080b757b2055297d9b06ada8e94317d7daaf2 242568 
jumpnbump_1.60-3_amd64.deb
Files:
 5bb509e620d0f29f8ddd1846e7d302e2 2041 games optional jumpnbump_1.60-3.dsc
 d5c14aea967ffbe9b8580d069c0e698c 8416 games optional 
jumpnbump_1.60-3.debian.tar.xz
 4a65d82c008a03064078ec57b529eb20 101076 debug optional 
jumpnbump-dbgsym_1.60-3_amd64.deb
 ccb1e2bca62d4e0aeb16f80614cb412a 11041 games optional 
jumpnbump_1.60-3_amd64.buildinfo
 6737a5c6b94efa97353ead802bd713b8 242568 games optional 
jumpnbump_1.60-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlpk7jwSHGZhYmlhbkBk
ZWJpYW4ub3JnAAoJEMvqjpcMzVnfdrkQAJDOZJUAuAR6OroZJQ8x1ufSCi770e89
8OI99Z6qQZk5NBk9wnF4VUTMam1wq8WL+BGTYcN1841btFKoQyzYHFJM8I6VT8S7
9ENlC4V4VVMa2XepoHO1jEB+ISMr+fpfFVQ0HMkhj0JzqyQRHVlkUQTb/yYzATUP
YH5krF39uiVuZPFVztka1fhKhEou7uROFP2JKgCmNN9Jmjrs4sGLnZxF5n9ZrReS
+0RHehbt7cA/9BnYPpq7Y6E+1mWloy9PUeuze64HG2OrSCuNjhzggaqGksBFYMPU

Bug#887940: libpq-dev: changed version format in pg_config causes other packages to FTBFS

[Adrian Bunk]

Package: libpq-dev
Version: 10.1-3
Severity: serious
Control: affects -1 src:libpreludedb

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpreludedb.html

...
checking for ... checking for pg_config... /usr/bin/pg_config
checking for PostgreSQL libraries... yes
./configure: line 19300: test: too many arguments
...
   dh_install
dh_install: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/libpreludedb/plugins/sql/pgsql*" (tried in ., debian/tmp)

dh_install: libpreludedb7-pgsql missing files: 
debian/tmp/usr/lib/*/libpreludedb/plugins/sql/pgsql*
dh_install: missing files, aborting
debian/rules:27: recipe for target 'binary' failed
make: *** [binary] Error 25


Root cause:

postgresql-10 (10.1-3) unstable; urgency=medium
...
  * Include package version number in "extra version" so it is reported by
"psql --version" and friends.

https://sources.debian.org/src/autoconf-archive/20170321-1/m4/ax_lib_postgresql.m4/#L97

Processed: libpq-dev: changed version format in pg_config causes other packages to FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libpreludedb
Bug #887940 [libpq-dev] libpq-dev: changed version format in pg_config causes 
other packages to FTBFS
Added indication that 887940 affects src:libpreludedb

-- 
887940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887939: libpdfbox-java FTBFS: rm: cannot remove debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save: No such file or directory

[Adrian Bunk]

Source: libpdfbox-java
Version: 1:1.8.13-1
Severity: serious

Some recent change in unstable makes libpdfbox-java FTBFS:

https://tests.reproducible-builds.org/debian/history/libpdfbox-java.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpdfbox-java.html

...
dh_installexamples
# empty directory since we remove the contents during repackaging.
rmdir --verbose --parents --ignore-fail-on-non-empty 
/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox/resources/pdfa
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox/resources/pdfa'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox/resources'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache/pdfbox'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org/apache'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources/org'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main/resources'
rmdir: removing directory, 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/src/main'
rm 
/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save
rm: cannot remove 
'/build/1st/libpdfbox-java-1.8.13/debian/libpdfbox-java-doc/usr/share/doc/libpdfbox-java-doc/examples/pom.xml.save':
 No such file or directory
debian/rules:31: recipe for target 'override_dh_installexamples' failed
make[1]: *** [override_dh_installexamples] Error 1

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Egmont Koblinger]

Hi guys,

> We don't do c++ in d-i.

Unfortunately this sounds really problematic. As of version 0.42 vte
has been using (more and more) C++. This is not like Ubuntu's PCRE2
hack which is a matter of a few hours of work reverting and merging a
few commits. It's reasonably impossible to revert to plain C and
maintain that as a fork, and upstream has no intention to revert to C
either.

You might want to have a special libvte2.91 0.40 package, or revive
libvte2.90 0.36 for the installer. These are also abandoned by
upstream, but already significantly less buggier than 0.28, probably
good enough for the installer (after all, 0.28 was good enough until
now), and allow you to drop the gtk2 dependencies, potentially buying
you many more years (perhaps you'll be good until you decide to
replace gtk3 by gtk4 in the installer).

I understand it's far from ideal. Other possibilities include ditching
the "no c++" policy (pulling in a 1.5M lib for the sake of a 400k one,
sigh), maybe seeing if there's a good enough "minimal" replacement for
libstdc++ providing just the basics that are sufficient for VTE; or
finding a different terminal emulator solution.

cheers,
egmont

Bug#887934: pd-zexy FTBFS on amd64: FAIL: runtests.sh

[Adrian Bunk]

Source: pd-zexy
Version: 2.2.6-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes pd-zexy FTBFS on amd64:

https://tests.reproducible-builds.org/debian/history/pd-zexy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pd-zexy.html

...
/usr/bin/make  check-TESTS
make[3]: Entering directory '/build/1st/pd-zexy-2.2.6/tests'
make[4]: Entering directory '/build/1st/pd-zexy-2.2.6/tests'
FAIL: runtests.sh

Testsuite summary for zexy 2.2.6

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to zmoel...@iem.at

Makefile:561: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1

Processed: tagging 884626

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 884626 + pending
Bug #884626 [src:liblinux-dvb-perl] liblinux-dvb-perl FTBFS with linux-libc-dev 
4.14.2-1
Added tag(s) pending.
> forwarded 884626 https://rt.cpan.org/Public/Bug/Display.html?id=124165
Bug #884626 [src:liblinux-dvb-perl] liblinux-dvb-perl FTBFS with linux-libc-dev 
4.14.2-1
Changed Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=124165' from 
'schm...@schmorp.de'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872261: marked as done (matplotlib: FTBFS with Sphinx 1.6: Warning, treated as error: Footnote [2] is not referenced.)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 19:50:46 +
with message-id 
and subject line Bug#872261: fixed in matplotlib 2.1.1-1
has caused the Debian Bug report #872261,
regarding matplotlib: FTBFS with Sphinx 1.6: Warning, treated as error: 
Footnote [2] is not referenced.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
872261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib
Version: 2.0.0+dfsg1-2
Severity: important
Tags: fixed-upstream
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.6

Dear maintainer,

matplotlib fails to build with Sphinx 1.6, currently available in
experimental:

  Warning, treated as error:
  /<>/matplotlib-2.0.0+dfsg1/doc/devel/MEP/MEP12.rst:185:Footnote [2] 
is not referenced.
  Building HTML failed.
  debian/rules:21: recipe for target 'build-indep-stamp' failed
  make: *** [build-indep-stamp] Error 1

It looks like this upstream commit should fix the failure:
https://github.com/matplotlib/matplotlib/commit/3649684037a82747

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 2.1.1-1

We believe that the bug you reported is fixed in the latest version of
matplotlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 13:39:59 -0500
Source: matplotlib
Binary: python-matplotlib python3-matplotlib python-matplotlib-data 
python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg
Architecture: source all amd64
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-matplotlib - Python based plotting system in a style similar to Matlab
 python-matplotlib-data - Python based plotting system (data package)
 python-matplotlib-dbg - Python based plotting system (debug extension)
 python-matplotlib-doc - Python based plotting system (documentation package)
 python3-matplotlib - Python based plotting system in a style similar to Matlab 
(Python
 python3-matplotlib-dbg - Python based plotting system (debug extension, Python 
3)
Closes: 827361 866439 872261 885511
Changes:
 matplotlib (2.1.1-1) unstable; urgency=medium
 .
   * New upstream release; Closes: #827361, #872261
   * debian/control
 - replace python-imaging with python-pil; Closes: #866439
 - add pytest (tests) and sphinx-gallery, backports.functools-lru-cache,
   scipy (doc) to b-d
   * debian/rules
 - no longer install upstream CHANGELOG, it was removed from the tarball
 - install tutorials in the -doc pkg, and dont compress .py files
 - pass the right arguments to tests.py, now that it changed
 - dont compress HTML files
 - now doc cleanup works upstream, so comment the manual cleanup commands
   * debian/copyright
 - update extern/libqhull copyright and license
 - drop delaunay copyright/licence notices, removed upstream
 - update packaging copyright years
   * debian/patches/0009-dont-show-badgesidebar.html.patch
 - dont load badgesidebar.html into documentation webpages, so that we dont
   load external resources
   * debian/{control, setup.cfg}
 - stop building GTK/GTKAgg backends, and hence drop GTK2 dependencies;
   Closes: #885511
   * debian/patches/0010-disable-intersphinx.patch
 - disable intersphinx, so doc wont try to access the network during build
   * debian/patches/0011-remove-numpy-scipy-from-reference_url.patch
 - remove scipy and numpy from reference_url for sphinx_gallery, avoiding to
   access the network during doc build
   * debian/patches/20_matplotlibrc_path_search_fix.patch
 - update patch to still look at /etc/matplotlibrc with new upstream code;
   from https://github.com/QuLogic/matplotlib/commit/69b627b8

Bug#866439: marked as done (matplotlib: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 19:50:45 +
with message-id 
and subject line Bug#866439: fixed in matplotlib 2.1.1-1
has caused the Debian Bug report #866439,
regarding matplotlib: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
866439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:matplotlib
Version: 2.0.0+dfsg1-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 2.1.1-1

We believe that the bug you reported is fixed in the latest version of
matplotlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 866...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 13:39:59 -0500
Source: matplotlib
Binary: python-matplotlib python3-matplotlib python-matplotlib-data 
python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg
Architecture: source all amd64
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-matplotlib - Python based plotting system in a style similar to Matlab
 python-matplotlib-data - Python based plotting system (data package)
 python-matplotlib-dbg - Python based plotting system (debug extension)
 python-matplotlib-doc - Python based plotting system (documentation package)
 python3-matplotlib - Python based plotting system in a style similar to Matlab 
(Python
 python3-matplotlib-dbg - Python based plotting system (debug extension, Python 
3)
Closes: 827361 866439 872261 885511
Changes:
 matplotlib (2.1.1-1) unstable; urgency=medium
 .
   * New upstream release; Closes: #827361, #872261
   * debian/control
 - replace python-imaging with python-pil; Closes: #866439
 - add pytest (tests) and sphinx-gallery, backports.functools-lru-cache,
   scipy (doc) to b-d
   * debian/rules
 - no longer install upstream CHANGELOG, it was removed from the tarball
 - install tutorials in the -doc pkg, and dont compress .py files
 - pass the right arguments to tests.py, now that it changed
 - dont compress HTML files
 - now doc cleanup works upstream, so comment the manual cleanup commands
   * debian/copyright
 - update extern/libqhull copyright and license
 - drop delaunay copyright/licence notices, removed upstream
 - update packaging copyright years
   * debian/patches/0009-dont-show-badgesidebar.html.patch
 - dont load badgesidebar.html into documentation webpages, so that we dont
   load external resources
   * debian/{control, setup.cfg}
 - stop building GTK/GTKAgg backends, and hence drop GTK2 dependencies;
   Closes: #885511
   * debian/patches/0010-disable-intersphinx.patch
 - disable intersphinx, so doc wont try to access the network during build
   * debian/patches/0011-remove-numpy-scipy-from-reference_url.patch
 - remove scipy and numpy from reference_url for sphinx_gallery, avoiding to
   access the network during doc build
   * debian/patches/20_matplotlibrc_path_search_fix.patch
 - update patch to still look at /etc/matplotlibrc with new upstream code;
   from https://github.com/QuLogic/matplotlib/commit/69b627b8
Checksums-Sha1:
 7ff0569b8325669fca605248e52600de71c6473b 4021 matplotlib_2.1.1-1.dsc
 03275857dcd327c5e018b4420965aee2c8bb544d 35061936 

Processed: Update ownership

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 884626 Nick Morrott 
Bug #884626 [src:liblinux-dvb-perl] liblinux-dvb-perl FTBFS with linux-libc-dev 
4.14.2-1
Owner recorded as Nick Morrott .
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
884626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#866439 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 866439 pending
Bug #866439 [src:matplotlib] matplotlib: depends on obsolete python-imaging 
(replace with python3-pil or python-pil)
Ignoring request to alter tags of bug #866439 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
866439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#866439: marked as pending

[Sandro Tosi]

tag 866439 pending
thanks

Hello,

Bug #866439 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/matplotlib.git/commit/?id=c568688

---
commit c56868853df912d233e2a5f1ad7893b73252ad93
Author: Sandro Tosi 
Date:   Sun Nov 26 13:16:21 2017 -0500

replace python-imaging with python-pil; Closes: #866439

diff --git a/debian/changelog b/debian/changelog
index e0a22cc..8c2fa34 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,10 @@
 matplotlib (2.0.2-1) UNRELEASED; urgency=medium
 
   * New upstream release
+  * debian/control
+- replace python-imaging with python-pil; Closes: #866439
 
- -- Sandro Tosi   Sat, 27 May 2017 22:28:54 -0400
+ -- Sandro Tosi   Sun, 26 Nov 2017 13:15:56 -0500
 
 matplotlib (2.0.0+dfsg1-2) unstable; urgency=medium
 

Bug#887931: gazebo FTBFS with libtinyxml2-dev 6.0.0+dfsg-1

[Adrian Bunk]

Source: gazebo
Version: 7.8.1+dfsg-4
Severity: serious

https://buildd.debian.org/status/package.php?p=gazebo=sid

...
/<>/gazebo-7.8.1+dfsg/gazebo/util/LogPlay.cc: In member function 
'void gazebo::util::LogPlay::Open(const string&)':
/<>/gazebo-7.8.1+dfsg/gazebo/util/LogPlay.cc:121:51: error: 'class 
tinyxml2::XMLDocument' has no member named 'GetErrorStr1'; did you mean 
'ErrorStr'?
 const char *errorStr1 = this->dataPtr->xmlDoc.GetErrorStr1();
   ^~~~
   ErrorStr
/<>/gazebo-7.8.1+dfsg/gazebo/util/LogPlay.cc:122:51: error: 'class 
tinyxml2::XMLDocument' has no member named 'GetErrorStr2'; did you mean 
'ErrorStr'?
 const char *errorStr2 = this->dataPtr->xmlDoc.GetErrorStr2();
   ^~~~
   ErrorStr
gazebo/util/CMakeFiles/gazebo_util.dir/build.make:89: recipe for target 
'gazebo/util/CMakeFiles/gazebo_util.dir/LogPlay.cc.o' failed
make[3]: *** [gazebo/util/CMakeFiles/gazebo_util.dir/LogPlay.cc.o] Error 1

Bug#887930: html-xml-utils: FTBFS with netcat-traditional installed (testsuite hangs in extract1.sh)

[Daniel Schepler]

Source: html-xml-utils
Version: 7.5-1
Severity: serious

Recently, while rebuilding a bunch of packages in a chroot without
pbuilder, I discovered the following failure:

...
PASS: tests/xmlasc7.sh
PASS: tests/xmlasc4.sh
PASS: tests/xref3.sh
PASS: tests/xref1.sh
PASS: tests/xmlns1.sh
PASS: tests/xref5.sh
PASS: tests/xref4.sh
PASS: tests/xref2.sh
PASS: tests/xref6.sh
PASS: tests/xref7.sh

At this point, the build hangs, and a "ps" shows a bunch of "nc"
processes as children of "/bin/sh ./tests/extract1.sh".  At this
point, I have to terminate the build manually.

I was subsequently able to reproduce this using "pbuilder build
--extrapackages netcat-traditional html-xml-utils_7.5-1.dsc".

(By the way, I've been seeing the same thing in all the recent
uploads, starting with version 7.1-1 - though 7.5-1 is the only
version for which I've tried reproducing the issue with pbuilder.)
-- 
Daniel Schepler

Bug#887929: trigger-rally FTBFS with libtinyxml2-dev 6.0.0+dfsg-1

[Adrian Bunk]

Source: trigger-rally
Version: 0.6.5+dfsg-2
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/package.php?p=trigger-rally=sid

...
PEngine/util.cpp:234:43: error: 'class tinyxml2::XMLDocument' has no member 
named 'GetErrorStr1'; did you mean 'ErrorStr'?
 PUtil::outLog() << "TinyXML: " << doc.GetErrorStr1() << ", " << 
doc.GetErrorStr2() << std::endl;
   ^~~~
   ErrorStr
PEngine/util.cpp:234:73: error: 'class tinyxml2::XMLDocument' has no member 
named 'GetErrorStr2'; did you mean 'ErrorStr'?
 PUtil::outLog() << "TinyXML: " << doc.GetErrorStr1() << ", " << 
doc.GetErrorStr2() << std::endl;
 
^~~~
 
ErrorStr

Bug#887898: marked as done (graphviz: FTBFS with libgs-dev installed)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 19:20:09 +
with message-id 
and subject line Bug#887898: fixed in graphviz 2.38.0-19
has caused the Debian Bug report #887898,
regarding graphviz: FTBFS with libgs-dev installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graphviz
Version: 2.38.0-18
Severity: serious

Recently, while rebuilding a bunch of packages in a chroot without
pbuilder, I discovered the following build failure in graphviz:

...
Making all in gs
make[4]: Entering directory '/build/graphviz-2.38.0/plugin/gs'
/bin/bash ../../libtool  --tag=CC   --mode=compile
x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/common
-I../.. -I../../lib/common -I../../lib/pathplan -I../../lib/gvc
-I../../lib/cgraph -I../../lib/cdt  -I/us
r/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/li
bpng16 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/build/graphviz-2.38.0=. -fstack-protector-strong
-Wformat -Werror=format-security  -Wno-unknown-pragmas
-Wstrict-prototypes -Wpointer-arith -Wall -ffast-math
-MT gvplugin_gs.lo -MD -MP -MF .deps/gvplugin_gs.Tpo -c -o
gvplugin_gs.lo gvplugin_gs.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../..
-I../../lib/common -I../.. -I../../lib/common -I../../lib/pathplan
-I../../lib/gvc -I../../lib/cgraph -I../../lib/cdt
-I/usr/include/pango-1.0 -I/usr/include
/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng16 -Wdate-time -D_FORTIFY_SOUR
CE=2 -g -O2 -fdebug-prefix-map=/build/graphviz-2.38.0=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wno-unknown-pragmas -Wstrict-prototypes -Wpointer-arith -Wall
-ffast-math -MT gvplugin_gs.lo -MD -MP -MF .deps
/gvplugin_gs.Tpo -c gvplugin_gs.c  -fPIC -DPIC -o .libs/gvplugin_gs.o
mv -f .deps/gvplugin_gs.Tpo .deps/gvplugin_gs.Plo
/bin/bash ../../libtool  --tag=CC   --mode=compile
x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/common
-I../.. -I../../lib/common -I../../lib/pathplan -I../../lib/gvc
-I../../lib/cgraph -I../../lib/cdt  -I/us
r/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/li
bpng16 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/build/graphviz-2.38.0=. -fstack-protector-strong
-Wformat -Werror=format-security  -Wno-unknown-pragmas
-Wstrict-prototypes -Wpointer-arith -Wall -ffast-math
-MT gvloadimage_gs.lo -MD -MP -MF .deps/gvloadimage_gs.Tpo -c -o
gvloadimage_gs.lo gvloadimage_gs.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../..
-I../../lib/common -I../.. -I../../lib/common -I../../lib/pathplan
-I../../lib/gvc -I../../lib/cgraph -I../../lib/cdt
-I/usr/include/pango-1.0 -I/usr/include
/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng16 -Wdate-time -D_FORTIFY_SOUR
CE=2 -g -O2 -fdebug-prefix-map=/build/graphviz-2.38.0=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wno-unknown-pragmas -Wstrict-prototypes -Wpointer-arith -Wall
-ffast-math -MT gvloadimage_gs.lo -MD -MP -MF .d
eps/gvloadimage_gs.Tpo -c gvloadimage_gs.c  -fPIC -DPIC -o
.libs/gvloadimage_gs.o
gvloadimage_gs.c: In function 'gs_error':
gvloadimage_gs.c:75:16: error: 'e_VMerror' undeclared (first use in
this function); did you mean 'gs_error'?
if (err >= e_VMerror)
   ^
   gs_error
gvloadimage_gs.c:75:16: note: each undeclared identifier is reported
only once for each function it appears in
gvloadimage_gs.c:77:21: error: 'e_unregistered' undeclared (first use
in this function); did you mean 'register_t'?
else if (err >= e_unregistered)
^~
register_t
gvloadimage_gs.c:79:21: error: 'e_invalidid' undeclared (first use in
this function); did you mean 'gs_error_invalidid'?
else if (err >= e_invalidid)
^~~
gs_error_invalidid

Bug#887912: marked as done (python-parted-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/python-parted/HACKING.gz)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 18:53:41 +
with message-id 
and subject line Bug#887912: fixed in pyparted 3.11.1-5
has caused the Debian Bug report #887912,
regarding python-parted-doc: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/doc/python-parted/HACKING.gz
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-parted-doc
Version: 3.11.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python-parted-doc.
  Preparing to unpack .../python-parted-doc_3.11.1-4_all.deb ...
  Unpacking python-parted-doc (3.11.1-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-parted/HACKING.gz', which is also 
in package python-parted 3.11.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb


cheers,

Andreas


python-parted=3.11.1-1_python-parted-doc=3.11.1-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pyparted
Source-Version: 3.11.1-5

We believe that the bug you reported is fixed in the latest version of
pyparted, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated pyparted 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Jan 2018 15:29:49 -0200
Source: pyparted
Binary: python-parted python3-parted python-parted-doc
Architecture: source
Version: 3.11.1-5
Distribution: unstable
Urgency: medium
Maintainer: Herbert Parentes Fortes Neto 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 python-parted - Python interface for libparted
 python-parted-doc - Python 3 interface for libparted (common documentation)
 python3-parted - Python 3 interface for libparted
Closes: 887912
Changes:
 pyparted (3.11.1-5) unstable; urgency=medium
 .
   * Add Breaks, Replaces on *-doc package. (Closes: #887912)
 Thanks Andreas Beckmann.
Checksums-Sha1:
 f5469cebc493ac179d53eb066474a3149c33392e 2138 pyparted_3.11.1-5.dsc
 d25717d85228d59494a8a1c7b8d2c981a94b4607 100585 pyparted_3.11.1.orig.tar.gz
 4dda728da39c1ab1ab5c9431e76031515977c616 7168 pyparted_3.11.1-5.debian.tar.xz
 9194d9754fb2749f1710c260a8c67f73a60b0acd 8644 pyparted_3.11.1-5_amd64.buildinfo
Checksums-Sha256:
 886e7f6672aa30923e00325bc08a19f430492276b0ce74c2804473b2412f801e 2138 
pyparted_3.11.1-5.dsc
 983b5123742d0124b640eafbeee9c5413d23b5ada29fb0adb34c5940a4f43664 100585 
pyparted_3.11.1.orig.tar.gz
 b0acb6e4a2ea5ecdc9213e304b64268d0d487647e612cbd726180f59aa7cd9f8 7168 
pyparted_3.11.1-5.debian.tar.xz
 38ab8c2932896118bb7d130d7c8bb6b5aea867b068e12fedac45c8249fd560de 8644 
pyparted_3.11.1-5_amd64.buildinfo
Files:
 5ae941de40939e3f5e3554bbc7405fc6 2138 python optional pyparted_3.11.1-5.dsc
 2e511d560b9c0e350a678744f28fb862 100585 python optional 
pyparted_3.11.1.orig.tar.gz
 ac1c6273d4f25768e4ee09bcff583300 7168 python optional 
pyparted_3.11.1-5.debian.tar.xz
 1255f0021927a092f3a45d422d5a2094 8644 python optional 
pyparted_3.11.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEbiJhr5LBUJGFGPlCVSVvKKxgYRoFAlpk1wUQHGhwZm5AZGVi
aWFuLm9yZwAKCRBVJW8orGBhGqKWEACc/+cVCzoLV8LgWz3rCXUOBo0e7MABg7Kq
dbZhbWUb2Tz4Gd1rpyT4g7MSSsH8zbWvxO+X0MSpV0A+M9egq5pD+m4ZutvvaFtl
aDDWt2SuvVQU3HDCtAWChs6UA0FDgk+C8C3hATvhqHPBmc4KA1iLf4dTatlo3rSl

Processed: Add another affected package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 887785 src:commons-configuration
Bug #887785 [src:javacc-maven-plugin] javacc-maven-plugin and build-rdeps FTBFS 
with jtb 1.4.12-1
Added indication that 887785 affects src:commons-configuration
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#883957: Proposal

[Ms Melisa Mehmet]

-- 
Hello 

i want to invest in your region i have some funds under my management
please let me know if we can work together on this investment plan.

Regards 
Melisa Mehmet

Bug#887898: graphviz: FTBFS with libgs-dev installed

[GCS]

Control: tags -1 +pending

Hi Daniel,

On Sun, Jan 21, 2018 at 3:31 PM, Daniel Schepler  wrote:
> Source: graphviz
> Version: 2.38.0-18
> Severity: serious
[...]
> Fortunately, it appears that just adding "--without-ghostscript" to
> the configure command line in debian/rules will be sufficient to fix
> this, so no need for an ugly Build-Conflicts.
 Thanks for your proper QAs.
By the way, aren't you a DD with a debian.org email address?

Regards,
Laszlo/GCS

Processed: Re: Bug#887898: graphviz: FTBFS with libgs-dev installed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #887898 [src:graphviz] graphviz: FTBFS with libgs-dev installed
Added tag(s) pending.

-- 
887898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886506: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Ben Hutchings]

On Sun, 2018-01-21 at 12:18 +0100, Aurelien Jarno wrote:
> On 2018-01-21 00:47, Ben Hutchings wrote:
> > On Wed, 17 Jan 2018 12:31:06 +0100 Aurelien Jarno  
> > wrote:
> > [...]
> > > busybox is compiled with -mpreferred-stack-boundary=2 on i386 which has
> > > the same effect of reducing the default stack alignment from 16 bytes to
> > > 2 bytes. This comes from arch/i386/Makefile:
> > 
> > The argument is the log2 of the alignment, so this sets alignment to 4
> > bytes - which is compliant with the System V psABI for i386.
> 
> This is correct, but it is not compliant with the i386 GCC ABI which
> assumes the stack is 16-byte aligned (not just 4-byte aligned) when the
> call instruction in the caller was executed.

Yes, that's what I think the bug is - gcc's default ABI for
i386-linux-gnu was quietly changed.

> > Any assumption of 16-byte stack alignment in glibc on i386 will break
> > not only busybox but most binaries built with old versions of gcc
> > (before 4.2, if the comment in busybox is correct).  So this really
> > ought to be fixed there.
> 
> The 16-byte stack alignment in glibc on i386 comes from a GCC 7
> regression, reported as bug #887327. It has been fixed in the upstream
> gcc-7 branch in the mean time.
> 
> > I think that any libraries that need to maintain backward binary
> > compatibility will need to be compiled with the option
> > -mincoming-stack-boundary=2.  gcc will then fix up the stack alignment
> > in functions that need greater alignment for local variables.
> 
> If we allow any binary to be built with -mpreferred-stack-boundary=2,
> we need to build *all* libraries with -mincoming-stack-boundary=2, not
> only the ones that need to maintain backward binary compatibility.

That's true, but we could also specify that if you mess with stack
alignment you can only use libc6 and other libraries whose ABI pre-
dates the change in gcc.  (I don't know where we would do that; I
haven't seen any formal specifications of Debian architectures.)

> In that case we should make it the default in GCC.

I think there are quite few libraries where this would be necessary.  I
could be wrong.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.



signature.asc
Description: This is a digitally signed message part

Bug#887798: firefox-esr: impossible to connect to Google domains

[Viktor Jägersküpper]

On Sat, 20 Jan 2018 11:30:56 +0100 Vincent Lefevre 
wrote:
> (...)
> As a temporary and insecure workaround, I can avoid this error by
> setting security.OCSP.require to false, even though the error was
> not about OCSP.

Hello Vincent,

this is not a bug in Firefox (ESR). See this thread (works in Firefox
only with "security.OCSP.require" set to "false" at the moment):
https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/MMO3HSYghwQ/XLRuxWtJAwAJ

The Google engineers are working on fixing this issue, so that this OCSP
setting can be set to "true" again.

Regards,
Viktor

Bug#887924: slurm-drmaa FTBFS with slurm-llnl 17.11.2-1

[Adrian Bunk]

Source: slurm-drmaa
Version: 1.0.7-1
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/package.php?p=slurm-drmaa=sid

...
configure: checking for SLURM
checking for SLURM compile flags... -I/usr/include/slurm/
checking for SLURM library dir... /usr/lib/libslurm.so
checking for usable SLURM libraries/headers... *** The SLURM test program 
failed to link or run. See the file config.log
*** for the exact error that occured.
no
configure: error: 
SLURM libraries/headers not found;
add --with-slurm-inc and --with-slurm-lib with appropriate locations.
debian/rules:10: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1

Bug#887923: dablin: FTBFS on ppc* and baseline violation on i386

[Adrian Bunk]

Source: dablin
Version: 1.7.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=dablin=ppc64el=1.7.0-1=1516518386=0

...
[  6%] Building C object fec/CMakeFiles/fec.dir/init_rs_char.c.o
cc: error: unrecognized command line option '-faltivec'; did you mean 
'-maltivec'?
cd /<>/obj-powerpc64le-linux-gnu/fec && /usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wall -Wno-unused 
-fno-common -faltivec -o CMakeFiles/fec.dir/init_rs_char.c.o   -c 
/<>/fec/init_rs_char.c
fec/CMakeFiles/fec.dir/build.make:65: recipe for target 
'fec/CMakeFiles/fec.dir/encode_rs_char.c.o' failed
make[3]: *** [fec/CMakeFiles/fec.dir/encode_rs_char.c.o] Error 1


The bug is in fec/CMakeLists.txt:

if(CMAKE_COMPILER_IS_GNUCC OR CMAKE_COMPILER_IS_CLANGCC)
add_definitions(-Wall)
add_definitions(-Wno-unused)

if(TARGET_ARCH MATCHES "x64")
 add_definitions(-fPIC)
 add_definitions(-msse2)
elseif(TARGET_ARCH MATCHES "x86")
 add_definitions(-mmmx)
 add_definitions(-msse)
 add_definitions(-msse2)
elseif(TARGET_ARCH MATCHES "ppc|ppc64")
 add_definitions(-fno-common)
 add_definitions(-faltivec)
endif()

endif()



AltiVec is already enabled by default on ppc64el,
and must not be used on the other ppc ports where
it is not part of the baseline.

MMX and SSE are not part of the i386 port baseline.

Bug#887920: speech-tools binary-all FTBFS: config/common_make_rules:49: ../config/system.mak: No such file or directory

[Adrian Bunk]

Source: speech-tools
Version: 1:2.5.0-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=speech-tools=all=1%3A2.5.0-3=1516484001=0

...
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
cd doc && /usr/bin/make doc
make[2]: Entering directory '/<>/doc'
../config/common_make_rules:49: ../config/system.mak: No such file or directory
../config/common_make_rules:49: ../config/system.mak: No such file or directory
make[2]: *** No rule to make target '../config/system.mak'.  Stop.

Bug#887726: marked as done (debian-edu-config 1.946: rmdir: failed to remove '/var/lib/cfengine3': Directory not empty)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 17:49:17 +
with message-id 
and subject line Bug#887726: fixed in debian-edu-config 1.947
has caused the Debian Bug report #887726,
regarding debian-edu-config 1.946: rmdir: failed to remove 
'/var/lib/cfengine3': Directory not empty
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: debian-edu-config
version: 1.946
severity: serious

hi,

debian-edu-config fails the piuparts test, or more exactly, to purge
cfengine3:

quoting from https://piuparts.debian.org/sid/fail/debian-edu-config_1.946.log

  Purging configuration files for cfengine3 (3.10.2-4) ...
  rmdir: failed to remove '/var/lib/cfengine3': Directory not empty
  dpkg: error processing package cfengine3 (--purge):
   installed cfengine3 package post-removal script subprocess returned error 
exit status 1

Using serious severity cause this is a piuparts regression causing britney to 
not migrate d-e-c.


--
cheers,
Holger


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 1.947

We believe that the bug you reported is fixed in the latest version of
debian-edu-config, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated debian-edu-config 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Jan 2018 17:29:19 +
Source: debian-edu-config
Binary: debian-edu-config
Architecture: source
Version: 1.947
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Description:
 debian-edu-config - Configuration files for Skolelinux systems
Closes: 887726
Changes:
 debian-edu-config (1.947) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * debian/debian-edu-config.postrm: Also remove a generated cfengine3 config
 file. Thanks to Holger Levsen. (Closes: #887726).
   * Amend wording in two previous changelog entries.
   * Fix typo debian-debian-edu-config.postinst (cfengine log file removal).
 .
   [ Mike Gabriel ]
   * debian-edu-config/tools/gosa-*: White-space cleanups.
 .
   [ Holger Levsen ]
   * Add lintian overrides for package-contains-file-in-etc-skel as we do this
 since more than a decade.
Checksums-Sha1:
 be27e14a0eb7e5be1bbf27dad105e0f94cd40152 1852 debian-edu-config_1.947.dsc
 97a99220a92dde7f0f7d1abb100eca7b73119632 383968 debian-edu-config_1.947.tar.xz
 4e7c5bc725ac7eea2c6f9f7b4b7685c83bd9aad7 5180 
debian-edu-config_1.947_source.buildinfo
Checksums-Sha256:
 f73fb3f7ecab970ab23145168b52f467cccb2a8ea9856d589aae5b71c1d398dc 1852 
debian-edu-config_1.947.dsc
 30ba741a2363d25877b50b421de51189f1ab9e350657a4f0b8962f847f567231 383968 
debian-edu-config_1.947.tar.xz
 7ebca023d1cfad4769a42c3910fa8a2a0833625e4cc28c7a22295246773cb2a8 5180 
debian-edu-config_1.947_source.buildinfo
Files:
 60b23854cd4c70cd7e77f79699db0cd4 1852 misc optional debian-edu-config_1.947.dsc
 22078a78ce5c9fa5a885676a620fe3a9 383968 misc optional 
debian-edu-config_1.947.tar.xz
 92a14715723520abd6d4b06f0116f12f 5180 misc optional 
debian-edu-config_1.947_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAlpk0LEACgkQCRq4Vgaa
qhyG+RAAlInruTgK12Nqb27OHVr8WCRLut633/ya9Eug1nihflzFSJu60lifZ+bs
1SEKRMFh+2UsL3xd3dWLs48x4oaOsDfOXPfenMBlxtakAbFnDSsXITVbnQp68qMT
5r43xfUZ1VWu8lyWBXpZmYgCOFWnWO5E6WWHbD1I0uX35+qC5p1ntHUnn2gClhlE
Ik0pdgBy36NJpOGAS+tygLHEnum4QvWUddI/HlEt376KMEEyHe6Vx1GWZMjPnDQK
jby4kWNqVwjqLj6siWkXaF1GkYrJd3L5qIl+WoSaFYSYv3L/HZjaRGPSaFLwS3aF
dypzvriTic73vsMW9V0qMmVXYWUkcc69Slz/img1XZZ0WMz117m26/rCOHrwyDsk
Gi9+AiwrLVyV4ld9Wmc5OXLwd2SmaL1/iGmABGToKPRTDAnKBgQEwLwEXa1Jnm8c
FVvmZtqVVvaiu7mb0x3XYS1AEqn57KN2F0momzpFWzAcR7Mil2LGxoa//0A30c3D
airSwn9Z2NTO1GSRg00E+DfYJCcwOJii81qiOvxGTMlwg9AyAQzooFynTCtCB0lZ

Bug#887583: [Pkg-javascript-devel] Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3

[Pirate Praveen]

On 2018, ജനുവരി 21 10:19:24 PM IST, Ghislain Vaillant  
wrote:
>cc'd to Pirate Praveen who reported a similar issue for a version on
>experimental?
>
>Do you have an idea what's going on? Why is Adrian's log different to
>yours?
>

My logs were from before mocha 4 is uploaded to unstable. Now we need to fix 
the tests for mocha 4 (this bug), as well as chai 4 (the other bug I reported).

Bug#887912: python-parted-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/python-parted/HACKING.gz

[Herbert Fortes]

Em 21-01-2018 14:45, Andreas Beckmann escreveu:
> Package: python-parted-doc
> Version: 3.11.1-4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
> 
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package python-parted-doc.
>   Preparing to unpack .../python-parted-doc_3.11.1-4_all.deb ...
>   Unpacking python-parted-doc (3.11.1-4) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb (--unpack):
>trying to overwrite '/usr/share/doc/python-parted/HACKING.gz', which is 
> also in package python-parted 3.11.1-1
>   Errors were encountered while processing:
>/var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb

Thanks Andreas!

Bug#887912: python-parted-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/python-parted/HACKING.gz

[Herbert Fortes]

Em 21-01-2018 14:45, Andreas Beckmann escreveu:
> Package: python-parted-doc
> Version: 3.11.1-4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
> 
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package python-parted-doc.
>   Preparing to unpack .../python-parted-doc_3.11.1-4_all.deb ...
>   Unpacking python-parted-doc (3.11.1-4) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb (--unpack):
>trying to overwrite '/usr/share/doc/python-parted/HACKING.gz', which is 
> also in package python-parted 3.11.1-1
>   Errors were encountered while processing:
>/var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb

Thanks Andreas!

Bug#887876: marked as done (gir1.2-matepanelapplet-4.0: File conflict on upgrade from gir1.2-mate-panel)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 17:06:50 +
with message-id 
and subject line Bug#887876: fixed in mate-panel 1.18.7-4
has caused the Debian Bug report #887876,
regarding gir1.2-matepanelapplet-4.0: File conflict on upgrade from 
gir1.2-mate-panel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-matepanelapplet-4.0
Version: 1.18.7-3
Severity: serious
Justification: Policy 7.6.1

# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  ...
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  python3.6-2to3
The following NEW packages will be installed:
  .

...

Preparing to unpack .../111-gir1.2-matepanelapplet-4.0_1.18.7-3_amd64.deb ...
Unpacking gir1.2-matepanelapplet-4.0:amd64 (1.18.7-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-4ILkbt/111-gir1.2-matepanelapplet-4.0_1.18.7-3_amd64.deb 
(--unpack):
 trying to overwrite 
'/usr/lib/x86_64-linux-gnu/girepository-1.0/MatePanelApplet-4.0.typelib', which 
is also in package gir1.2-mate-panel 1.18.6-1

...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-4ILkbt/111-gir1.2-matepanelapplet-4.0_1.18.7-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
#

...
# apt-get --fix-broken install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libgeos-3.5.1 libilmbase12 libsodium18 libsuitesparseconfig4 
libtesseract-data libtesseract3
  python-olefile
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  gir1.2-matepanelapplet-4.0
The following NEW packages will be installed:
  gir1.2-matepanelapplet-4.0
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
433 not fully installed or removed.
Need to get 0 B/14.3 kB of archives.
After this operation, 45.1 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 213689 files and directories currently installed.)
Preparing to unpack .../gir1.2-matepanelapplet-4.0_1.18.7-3_amd64.deb ...
Unpacking gir1.2-matepanelapplet-4.0:amd64 (1.18.7-3) ...
...
# echo $?
0
#






-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8), 
LANGUAGE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gir1.2-matepanelapplet-4.0 depends on:
ii  gir1.2-glib-2.0   1.54.1-4
ii  gir1.2-gtk-3.03.22.26-2
ii  libmate-panel-applet-4-1  1.18.7-3

gir1.2-matepanelapplet-4.0 recommends no packages.

gir1.2-matepanelapplet-4.0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mate-panel
Source-Version: 1.18.7-4

We believe that the bug you reported is fixed in the latest version of
mate-panel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mate-panel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 17:43:53 +0100
Source: mate-panel
Binary: mate-panel mate-panel-common libmate-panel-applet-4-1 
libmate-panel-applet-dev libmate-panel-applet-doc gir1.2-matepanelapplet-4.0 
gir1.2-mate-panel
Architecture: source
Version: 1.18.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike 

Bug#887915: gir1.2-matepanelapplet-4.0: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/girepository-1.0/MatePanelApplet-4.0.typelib

[Andreas Beckmann]

Package: gir1.2-matepanelapplet-4.0
Version: 1.18.7-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gir1.2-matepanelapplet-4.0:amd64.
  Preparing to unpack .../11-gir1.2-matepanelapplet-4.0_1.18.7-3_amd64.deb ...
  Unpacking gir1.2-matepanelapplet-4.0:amd64 (1.18.7-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-NbeHlL/11-gir1.2-matepanelapplet-4.0_1.18.7-3_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/girepository-1.0/MatePanelApplet-4.0.typelib', which 
is also in package gir1.2-mate-panel 1.18.7-1


cheers,

Andreas


gir1.2-mate-panel=1.18.7-1_gir1.2-matepanelapplet-4.0=1.18.7-3.log.gz
Description: application/gzip

Bug#887078: Bug#887886: libc6 from experimental makes vlc crash (even after rebuilding from source)

[Eric Valette]

On 21/01/2018 17:16, Aurelien Jarno wrote:

control: forcemerge -1 887078

On 2018-01-21 14:12, Eric Valette wrote:

Package: libc6
Version: 2.26.9000+20180108.401311cf-0experimental0
Severity: critical
Justification: breaks unrelated software

launching vlc crash immediately with sigsegv. Downgrading to unstable makes
it work again.


The problem is the same that has already been reported [1] for mono, as
well as the already reported bug #887078. vlc is easier to debug than
amarok. Reverting the upstream commit f81ddabffd fixes the issue.

The issue is currently listed as a release blocker for the version 2.27
[2], so it will be either fixed or reverted for the final release.


Great. That for the explanation. As a side comment, it made kde 
multimedia configuration break (systemsettings) and also breaks phonon 
vlc backend. That's how I started investigating missing sound and 
remembering that clementine use gstreamer and was still working while 
other players were crashing...


-- eric

Processed: Bug#887876 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 887876 pending
Bug #887876 [gir1.2-matepanelapplet-4.0] gir1.2-matepanelapplet-4.0: File 
conflict on upgrade from gir1.2-mate-panel
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887914: gir1.2-matekbd-1.0: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/girepository-1.0/Matekbd-1.0.typelib

[Andreas Beckmann]

Package: gir1.2-matekbd-1.0
Version: 1.18.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gir1.2-matekbd-1.0:amd64.
  Preparing to unpack .../11-gir1.2-matekbd-1.0_1.18.2-2_amd64.deb ...
  Unpacking gir1.2-matekbd-1.0:amd64 (1.18.2-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-3ZZMyl/11-gir1.2-matekbd-1.0_1.18.2-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/girepository-1.0/Matekbd-1.0.typelib', which is also 
in package gir1.2-matekbd 1.18.2-1


cheers,

Andreas


gir1.2-matekbd=1.18.2-1_gir1.2-matekbd-1.0=1.18.2-2.log.gz
Description: application/gzip

Bug#887876: marked as pending

[Mike Gabriel]

tag 887876 pending
thanks

Hello,

Bug #887876 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/pkg-mate/mate-panel.git/commit/?id=4de02c3

---
commit 4de02c3f46155ec384e46e1099821097ec2cad03
Author: Mike Gabriel 
Date:   Sun Jan 21 17:48:35 2018 +0100

upload to unstable (debian/1.18.7-4)

diff --git a/debian/changelog b/debian/changelog
index fb0b479..2831e42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+mate-panel (1.18.7-4) unstable; urgency=medium
+
+  * debian/control:
++ Remove empty line at EOF.
++ Add another B:/R: couple for gir1.2-mate-panel (<< 1.18.7-3~) to
+  gir1.2-matepanelapplet-4.0. (Closes: #887876).
+
+ -- Mike Gabriel   Sun, 21 Jan 2018 17:43:53 +0100
+
 mate-panel (1.18.7-3) unstable; urgency=medium
 
   * Rename GIR package to match Debian Policy.

Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3

[Ghislain Vaillant]

cc'd to Pirate Praveen who reported a similar issue for a version on
experimental?

Do you have an idea what's going on? Why is Adrian's log different to
yours?

On Thu, 18 Jan 2018 09:23:11 +0200 Adrian Bunk  wrote:
> Source: libjs-fetch
> Version: 2.0.3-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/li
bjs-fetch.html
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/1st/libjs-fetch-2.0.3'
> xvfb-run -a -s "-screen 0 640x480x16" ./script/test
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
pbuilder1'
> Error loading resource http://localhost:3901/node_modules/mocha/mocha
.css (203). Details: Error transferring http://localhost:3901/node_modu
les/mocha/mocha.css - server replied: Not Found
> Error loading resource http://localhost:3901/node_modules/url-search-
params/build/url-search-params.js (203). Details: Error transferring ht
tp://localhost:3901/node_modules/url-search-params/build/url-search-
params.js - server replied: Not Found
> Error loading resource http://localhost:3901/node_modules/mocha/mocha
.js (203). Details: Error transferring http://localhost:3901/node_modul
es/mocha/mocha.js - server replied: Not Found
> ReferenceError: Can't find variable: Mocha
> ReferenceError: Can't find variable: suite
> TypeError: mocha.run is not a function. (In 'mocha.run()',
'mocha.run' is undefined)
> Likely due to external resource loading and timing, your tests
require calling `window.initMochaPhantomJS()` before calling any mocha
setup functions. See https://github.com/nathanboktae/mocha-phantomjs-co
re/issues/12
> TypeError: Attempting to change the setter of an unconfigurable
property.
> TypeError: Attempting to change the setter of an unconfigurable
property.
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
pbuilder1'
> Error loading resource http://localhost:3901/node_modules/mocha/mocha
.css (203). Details: Error transferring http://localhost:3901/node_modu
les/mocha/mocha.css - server replied: Not Found
> Error loading resource http://localhost:3901/node_modules/url-search-
params/build/url-search-params.js (203). Details: Error transferring ht
tp://localhost:3901/node_modules/url-search-params/build/url-search-
params.js - server replied: Not Found
> Error loading resource http://localhost:3901/node_modules/mocha/mocha
.js (203). Details: Error transferring http://localhost:3901/node_modul
es/mocha/mocha.js - server replied: Not Found
> ReferenceError: Can't find variable: Mocha
> Likely due to external resource loading and timing, your tests
require calling `window.initMochaPhantomJS()` before calling any mocha
setup functions. See https://github.com/nathanboktae/mocha-phantomjs-co
re/issues/12
> TypeError: Attempting to change the setter of an unconfigurable
property.
> TypeError: Attempting to change the setter of an unconfigurable
property.
> debian/rules:28: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 1
> 
> 

Bug#887912: python-parted-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/python-parted/HACKING.gz

[Andreas Beckmann]

Package: python-parted-doc
Version: 3.11.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python-parted-doc.
  Preparing to unpack .../python-parted-doc_3.11.1-4_all.deb ...
  Unpacking python-parted-doc (3.11.1-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-parted/HACKING.gz', which is also 
in package python-parted 3.11.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-parted-doc_3.11.1-4_all.deb


cheers,

Andreas


python-parted=3.11.1-1_python-parted-doc=3.11.1-4.log.gz
Description: application/gzip

Bug#883526: marked as done (geeqie build does not trap errors from make)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 17:15:38 +0100
with message-id <5a64bcab.d6c9190a.aec5e.6...@mx.google.com>
and subject line Re: geeqie build does not trap errors from make
has caused the Debian Bug report #883526,
regarding geeqie build does not trap errors from make
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
883526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geeqie
Version: 1:1.3-1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The upstream build system of geeqie does not trap all errors from
programs executed by make. In src/Makefile.am in the ui_icons.h target,
$(GDK_PIXBUF_CSOURCE) is chained with a semicolon. Thus a potential
failure is suppressed and a misbuild can result. This is why such
behaviour is prohibited by the Debian policy section 4.6. Indeed, cross
builds do exhibit exactly that behaviour. Inserting a "set -e;" into the
subshell is an easy fix.

Helmut
--- End Message ---
--- Begin Message ---
This is now fixed.

-- Andreas Rönnquist
gus...@debian.org--- End Message ---

Processed: Re: Bug#887886: libc6 from experimental makes vlc crash (even after rebuilding from source)

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 887078
Bug #887886 [libc6] libc6 from experimental makes vlc crash (even after 
rebuilding from source)
Bug #887078 [libc6] libc6: Amarok get SIGSEGV at start
Severity set to 'critical' from 'important'
Merged 887078 887886

-- 
887078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887078
887886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887886: libc6 from experimental makes vlc crash (even after rebuilding from source)

[Aurelien Jarno]

control: forcemerge -1 887078

On 2018-01-21 14:12, Eric Valette wrote:
> Package: libc6
> Version: 2.26.9000+20180108.401311cf-0experimental0
> Severity: critical
> Justification: breaks unrelated software
> 
> launching vlc crash immediately with sigsegv. Downgrading to unstable makes
> it work again.

The problem is the same that has already been reported [1] for mono, as
well as the already reported bug #887078. vlc is easier to debug than
amarok. Reverting the upstream commit f81ddabffd fixes the issue.

The issue is currently listed as a release blocker for the version 2.27
[2], so it will be either fixed or reverted for the final release.

Aurelien

[1] https://sourceware.org/ml/libc-alpha/2018-01/msg00178.html
[2] https://sourceware.org/glibc/wiki/Release/2.27

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#866469: closing 866469

[Michael Fladischer]

close 866469 1.3.0-1~exp2
thanks

Processed: fixed 866469 in 1.3.0-1~exp2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 866469 1.3.0-1~exp2
Bug #866469 {Done: Michael Fladischer } [src:python-scrapy] 
python-scrapy: depends on obsolete python-imaging (replace with python3-pil or 
python-pil)
Ignoring request to alter fixed versions of bug #866469 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
866469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 866469

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 866469 1.3.0-1~exp2
Bug #866469 [src:python-scrapy] python-scrapy: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Marked as fixed in versions python-scrapy/1.3.0-1~exp2.
Bug #866469 [src:python-scrapy] python-scrapy: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
866469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887062: marked as done (raspi3-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 15:14:35 +
with message-id 
and subject line Bug#887062: fixed in raspi3-firmware 1.20171201-3
has caused the Debian Bug report #887062,
regarding raspi3-firmware: postinst fails, makes bad assumption about existence 
of /boot/firmware/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20171201-2
Severity: serious
User: de...@kali.org
Usertags: origin-kali

My dailay builds of Kali armhf live images are now failing with this version of
raspi3-firmware with this error:

Setting up raspi3-firmware (1.20171201-2) ...
cp: cannot create regular file '/boot/firmware/bootcode.bin': No such file or 
directory
dpkg: error processing package raspi3-firmware (--configure):

I did not check the code but it looks like it assumes that /boot/firmware/ does 
exist
while it doesn't (at least not in the context of the chroot where the live
image is being built).

This was working fine a few days ago with the previous version that was in 
testing
(1.20171006-1, Kali is based on Debian Testing).

Cheers,

-- System Information:
Debian Release: buster/sid
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: raspi3-firmware
Source-Version: 1.20171201-3

We believe that the bug you reported is fixed in the latest version of
raspi3-firmware, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated raspi3-firmware 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Jan 2018 15:35:47 +0100
Source: raspi3-firmware
Binary: raspi3-firmware
Architecture: source
Version: 1.20171201-3
Distribution: unstable
Urgency: medium
Maintainer: pkg-raspi 
Changed-By: Michael Stapelberg 
Description:
 raspi3-firmware - Raspberry Pi 3 GPU firmware and bootloaders
Closes: 887062
Changes:
 raspi3-firmware (1.20171201-3) unstable; urgency=medium
 .
   * Ensure /boot/firmware exists (Closes: #887062)
Checksums-Sha1:
 c872dae9d5bf9bfa1f724b2dbe39dcd6a93df96a 2113 raspi3-firmware_1.20171201-3.dsc
 03702d3bb1a51bd0353c3a3ed59d922f7e787594 11056 
raspi3-firmware_1.20171201-3.debian.tar.xz
 8843f100fe7ae64727f87bf20da8b7bda969c62f 6241 
raspi3-firmware_1.20171201-3_source.buildinfo
Checksums-Sha256:
 8b6799ba1e341d3f93a53032739877bdf723f15743ef455e0bab2f76c7dcb0a2 2113 
raspi3-firmware_1.20171201-3.dsc
 d2307720d95a53683bbf91eeda050e8932ab51814a1881a7e2f6427c08573455 11056 
raspi3-firmware_1.20171201-3.debian.tar.xz
 4f101f0a4da078c7b56465634071f4538b07544d54162c0a9c723b959df243a6 6241 
raspi3-firmware_1.20171201-3_source.buildinfo
Files:
 da649aadeb103876e4e5d9bd8205eb4d 2113 non-free/misc optional 
raspi3-firmware_1.20171201-3.dsc
 fbdea1c27250206c1709a559cbcc832e 11056 non-free/misc optional 
raspi3-firmware_1.20171201-3.debian.tar.xz
 32ec9d04b8fffde8410f279b439c1e18 6241 non-free/misc optional 
raspi3-firmware_1.20171201-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAlpkpWgWHHN0YXBlbGJl
cmdAZGViaWFuLm9yZwAKCRBOcWDtSsjuHeccD/4vyxHNTldCgsxZEssLHOSoEuTX
ujEEtLvhBeF2Rb/lOew6kVjjqTHTs8VSi/HGEj9IwBJeOF3xSIZ1WMN+3Ptpd8wx
vD0l8uNeZ+H6aHTPp4qyiwylwZvIxKPACz5b+ytBtuH40jsaglKzfsTbATyUVh/C
giCa9ljkPEiuL7RWbGws0yalEO/jsc7CQQa67ivo0u1qdg5itfuus714F5yv9Dpt
N2Fod/zJx3rQ0KE2iUFuGVRQlYoBE2vl4s4XkxC8WNfwkYdeiGOUc0uXSEfRgt/O

Bug#887863: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Niko Tyni]

On Sun, Jan 21, 2018 at 05:32:01AM +0100, Guillem Jover wrote:
> On Sun, 2018-01-21 at 02:59:53 +0100, Andreas Beckmann wrote:
> > Control: clone -1 -2
> > Control: retitle -2 libglib2.0-dev: needs dummy empty prerm
> > Control: reassign -2 libglib2.0-dev 2.54.2-1
> > 
> > >> On Sat, Jan 20, 2018 at 05:07:30PM +0100, Andreas Beckmann wrote:>>> For 
> > >> now, I'd suggest the dummy empty libglib2.0-dev.prerm, but if this
> > Even if python is going to get fixed, this probably won't help
> > libglib2.0-dev (which drops the python dependency in buster), therefore
> > it will need to add the dummy empty prerm to mitigate this issue.
> 
> I don't see why this would be needed. If python gets fixed to use
> Pre-Depends, then it does not matter whether libglib2.0-dev stops
> depending on it, as python should then be always usable even when
> just unpacked.

stretch# apt --no-install-recommends install glib2.0-dev
[...]
stretch# dpkg --unpack libexpat1_2.2.5-3_amd64.deb # from sid
[...]
stretch# dpkg --unpack libglib2.0-dev_2.54.3-1_amd64.deb # from sid
/usr/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not 
found (required by /lib/x86_64-linux-gnu/libexpat.so.1)
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: error processing archive libglib2.0-dev_2.54.3-1_amd64.deb (--unpack):
 there is no script in the new version of the package - giving up
/usr/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not 
found (required by /lib/x86_64-linux-gnu/libexpat.so.1)
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 1

No python3 change in sid/buster is going to prevent this afaics?
-- 
Niko Tyni   nt...@debian.org

Bug#886814: marked as done (please replace myspell-nl with hunspell-nl)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 15:06:11 +
with message-id 
and subject line Bug#886814: fixed in boxer-data 10.6.3
has caused the Debian Bug report #886814,
regarding please replace myspell-nl with hunspell-nl
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
886814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-parl
Version: 1.9.13
Severity: serious

Hi,

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761032.

myspell-nl is (supposed to be) gone and renamed to hunspell-nl. Please adapt.

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: boxer-data
Source-Version: 10.6.3

We believe that the bug you reported is fixed in the latest version of
boxer-data, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 886...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated boxer-data package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Jan 2018 14:56:22 +0100
Source: boxer-data
Binary: boxer-data
Architecture: source all
Version: 10.6.3
Distribution: unstable
Urgency: medium
Maintainer: Boxer developers 
Changed-By: Jonas Smedegaard 
Description:
 boxer-data - classes and nodes usable by Boxer
Closes: 886814
Changes:
 boxer-data (10.6.3) unstable; urgency=medium
 .
   * Update class Console.design.painting:
 + Include package optipng (not inferior package pngcrush).
   * Update node huayruro-classmate:
 + Stop include class Desktop.office.gtk.
   * Update class Desktop.office.libreoffice.word-processor:
 + Stop avoid package libreoffice-emailmerge (since jessie):
   Obsolete.
   * Update classes Desktop.environment.xfce.base
 Desktop.environment.xfce.audio:
 + Include/avoid package xfce4-pulseaudio-plugin (since stretch).
 + Stop include/avoid xfce4-mixer xfce4-volumed.
   * Update class Console.media.audio.pulseaudio.client:
 + Include package pulsemixer (since buster).
   * Fix class Desktop.web.firefox.locale.de spuriously dropping all
 packages when included (since stretch): Single package commented out
 need "pkg:" declaration itself commented out.
   * Fix class l10n.hunspell.nl (since buster):
 + Include package hunspell-nl (not myspell-nl).
 Closes: Bug#886814. Thanks to Rene Engelhard.
   * Add some TODOs.
   * Add new classes:
 + Hardware.igp.intel.skylake
 + Hardware.laptop.purism
 + Hardware.motherboard.intel.skylake-u
 + Hardware.nic.atheros
 + Hardware.sound.intel.
Checksums-Sha1:
 96ce813b533da83845417aaab2b9e1ad4d6e57e5 1665 boxer-data_10.6.3.dsc
 cca48baa0072ee07b00a421507d6787471812152 93064 boxer-data_10.6.3.tar.xz
 bdef5a5d75be2e398b28c84c2811e393fdc2602f 184084 boxer-data_10.6.3_all.deb
 a63c805b929e29dd4b78dbac639adbf3a009e812 7771 boxer-data_10.6.3_amd64.buildinfo
Checksums-Sha256:
 b1c3dfcf555b414df0236d751c85b3fe2aef21e55ab59085dceb338f2763bc1e 1665 
boxer-data_10.6.3.dsc
 ccb4f48e49650357b6f6e2ec93a41c69b5a19fa9eaf7df428579e2fdd2adf3cc 93064 
boxer-data_10.6.3.tar.xz
 027fefcb723dc0ff60e232e7a0a8e5b7d97a2faa306a087aaf8ab81b926723a5 184084 
boxer-data_10.6.3_all.deb
 d3ab3cf9e6b71053efc4b38dffb1077916ea09c0cf59e1482943834f9754fc9d 7771 
boxer-data_10.6.3_amd64.buildinfo
Files:
 c677f5e7c9008a68584ef85f2cf69d02 1665 misc optional boxer-data_10.6.3.dsc
 b8549c374a076d1de3e8700ff0ab6a4e 93064 misc optional boxer-data_10.6.3.tar.xz
 3698f7767318021f53213658977b8d85 184084 misc optional boxer-data_10.6.3_all.deb
 7e36b66f92acb9df67293c26df3cafcb 7771 misc optional 
boxer-data_10.6.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlpkniEACgkQLHwxRsGg
ASEjoA/8C+DftOkRB9zpN3Yl/GRUULze8Rhl2dgef/ptHpbtStxq5HDkvoai3bCi
FCFPAUIduNi0o5MrrguFisEQknFbtPz2NRvnaGhSlifk9Jgj2cdSlo25Cp5NQWhr
8MrMxz9ov04jDnsyq3CwbBUhtbxRmb7WRK1XK6qPyiXKjvuWhRVCnkBK6qU+6N7m
7DhynnbIpAnHE1BwC1pmcdEzUm6lJqaVFtJSRRxU/33lE3XBcxMWgInONyTk86Oy

Bug#887902: qtwebchannel-opensource-src: FTBFS with cmake installed

[Daniel Schepler]

Source: qtwebchannel-opensource-src
Version: 5.9.2-3
Severity: serious

Recently, while rebuilding a bunch of packages in a chroot without
pbuilder, I discovered the following failure in building
qtwebchannel-opensource-src:

...
make[5]: Entering directory
'/build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake'
mkdir -p /build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake/build
&& cd /build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake/build
&& cmake /build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake
-DCMAKE_C_COMPI
LER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_VERBOSE_MAKEFILE=1
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_PREFIX_PATH="/build/qtwebchannel-opensource-src-5.9.2;/usr/lib/x86_64-linux-gnu/qt5"
-DQt5_MODULE_TEST_DEPENDS="Qml;Network;Core"
-DCMAKE_WebChannel_MODULE_MAJOR_VERSION=5
-DCMAKE_WebChannel_MODULE_MINOR_VERSION=9
-DCMAKE_WebChannel_MODULE_PATCH_VERSION=2
-DCMAKE_MODULES_UNDER_TEST="WebChannel" &&  ctest --output-on-failure
-- The C compiler identification is GNU 7.2.0
-- The CXX compiler identification is GNU 7.2.0
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/g++
-- Check for working CXX compiler: /usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMAKE_VERSION: 3.9.5
CMAKE_PREFIX_PATH:
/build/qtwebchannel-opensource-src-5.9.2;/usr/lib/x86_64-linux-gnu/qt5
CMAKE_MODULES_UNDER_TEST: WebChannel
CMAKE_WebChannel_MODULE_MAJOR_VERSION: 5
CMAKE_WebChannel_MODULE_MINOR_VERSION: 9
CMAKE_WebChannel_MODULE_PATCH_VERSION: 2
-- Configuring done
-- Generating done
-- Build files have been written to:
/build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake/build
Test project /build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake/build
   Start 1: module_includes
1/1 Test #1: module_includes ..***Failed1.20 sec
Internal cmake changing into directory:
/build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake/build/module_includes/build
Error: cmake execution failed
The C compiler identification is GNU 7.2.0
The CXX compiler identification is GNU 7.2.0
Check for working C compiler: /usr/bin/gcc
Configuring
Check for working C compiler: /usr/bin/gcc -- works
Detecting C compiler ABI info
Configuring
Detecting C compiler ABI info - done
Detecting C compile features
Configuring
Configuring
Configuring
Detecting C compile features - done
Check for working CXX compiler: /usr/bin/g++
Configuring
Check for working CXX compiler: /usr/bin/g++ -- works
Detecting CXX compiler ABI info
Configuring
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Configuring
Configuring
Configuring
Configuring
Detecting CXX compile features - done
CMake Error at 
/build/qtwebchannel-opensource-src-5.9.2/lib/cmake/Qt5WebChannel/Qt5WebChannelConfig.cmake:27
(message):
 The imported target "Qt5::WebChannel" references the file

"/build/include/x86_64-linux-gnu/qt5/"

 but this file does not exist.  Possible reasons include:

 * The file was deleted, renamed, or moved to another location.

 * An install or uninstall procedure did not complete successfully.

 * The installation package was faulty and contained


"/build/qtwebchannel-opensource-src-5.9.2/lib/cmake/Qt5WebChannel/Qt5WebChannelConfig.cmake"

 but not all the files it references.

Call Stack (most recent call first):
 
/build/qtwebchannel-opensource-src-5.9.2/lib/cmake/Qt5WebChannel/Qt5WebChannelConfig.cmake:63
(_qt5_WebChannel_check_file_exists)
 CMakeLists.txt:9 (find_package)


Configuring
Configuring incomplete, errors occurred!
See also 
"/build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake/build/module_includes/build/CMakeFiles/CMakeOutput.log".



0% tests passed, 1 tests failed out of 1

Total Test time (real) =   1.20 sec

The following tests FAILED:
 1 - module_includes (Failed)
Errors while running CTest
Makefile:243: recipe for target 'check' failed
make[5]: *** [check] Error 8
make[5]: Leaving directory
'/build/qtwebchannel-opensource-src-5.9.2/tests/auto/cmake'
Makefile:420: recipe for target 'sub-cmake-check' failed
make[4]: *** [sub-cmake-check] Error 2
make[4]: Leaving directory '/build/qtwebchannel-opensource-src-5.9.2/tests/auto'
Makefile:314: recipe for target 'sub-auto-check' failed
make[3]: *** [sub-auto-check] Error 2
make[3]: Leaving directory '/build/qtwebchannel-opensource-src-5.9.2/tests'
Makefile:421: recipe for target 'sub-tests-check' failed
make[2]: *** [sub-tests-check] Error 2
make[2]: Leaving directory '/build/qtwebchannel-opensource-src-5.9.2'
dh_auto_test: make -j1 check QT_QPA_PLATFORM=minimal
QML2_IMPORT_PATH=/build/qtwebchannel-opensource-src-5.9.2/test_root/usr/lib/x86_64-linux-gnu/qt5/qml
returned 

Bug#879452: marked as pending

[TANIGUCHI Takaki]

tag 879452 pending
thanks

Hello,

Bug #879452 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/python-git.git/commit/?id=7b41002

---
commit 7b41002f30f1f7918ea3e1eb457c5b995e47fe9c
Author: TANIGUCHI Takaki 
Date:   Sat Jan 20 18:46:36 2018 +0900

prepare release

diff --git a/debian/changelog b/debian/changelog
index 62695af..9fb03dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-git (2.1.7-2) unstable; urgency=medium
+
+  * new upstream (Closes: #880446)
+- Fix "Incompatible with git 2.15?" (Closes: #879452)
+  * debian/control: Replace python3-sphinx instead of python2-sphinx
+
+ -- TANIGUCHI Takaki   Sat, 20 Jan 2018 18:46:20 +0900
+
 python-git (2.1.7-1) unstable; urgency=medium
 
   * New upstream release

Processed: Bug#879452 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 879452 pending
Bug #879452 {Done: TANIGUCHI Takaki } [src:python-git] 
src:python-git: Incompatible with git 2.15?
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
879452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887898: graphviz: FTBFS with libgs-dev installed

[Daniel Schepler]

Source: graphviz
Version: 2.38.0-18
Severity: serious

Recently, while rebuilding a bunch of packages in a chroot without
pbuilder, I discovered the following build failure in graphviz:

...
Making all in gs
make[4]: Entering directory '/build/graphviz-2.38.0/plugin/gs'
/bin/bash ../../libtool  --tag=CC   --mode=compile
x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/common
-I../.. -I../../lib/common -I../../lib/pathplan -I../../lib/gvc
-I../../lib/cgraph -I../../lib/cdt  -I/us
r/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/li
bpng16 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/build/graphviz-2.38.0=. -fstack-protector-strong
-Wformat -Werror=format-security  -Wno-unknown-pragmas
-Wstrict-prototypes -Wpointer-arith -Wall -ffast-math
-MT gvplugin_gs.lo -MD -MP -MF .deps/gvplugin_gs.Tpo -c -o
gvplugin_gs.lo gvplugin_gs.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../..
-I../../lib/common -I../.. -I../../lib/common -I../../lib/pathplan
-I../../lib/gvc -I../../lib/cgraph -I../../lib/cdt
-I/usr/include/pango-1.0 -I/usr/include
/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng16 -Wdate-time -D_FORTIFY_SOUR
CE=2 -g -O2 -fdebug-prefix-map=/build/graphviz-2.38.0=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wno-unknown-pragmas -Wstrict-prototypes -Wpointer-arith -Wall
-ffast-math -MT gvplugin_gs.lo -MD -MP -MF .deps
/gvplugin_gs.Tpo -c gvplugin_gs.c  -fPIC -DPIC -o .libs/gvplugin_gs.o
mv -f .deps/gvplugin_gs.Tpo .deps/gvplugin_gs.Plo
/bin/bash ../../libtool  --tag=CC   --mode=compile
x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/common
-I../.. -I../../lib/common -I../../lib/pathplan -I../../lib/gvc
-I../../lib/cgraph -I../../lib/cdt  -I/us
r/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/li
bpng16 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/build/graphviz-2.38.0=. -fstack-protector-strong
-Wformat -Werror=format-security  -Wno-unknown-pragmas
-Wstrict-prototypes -Wpointer-arith -Wall -ffast-math
-MT gvloadimage_gs.lo -MD -MP -MF .deps/gvloadimage_gs.Tpo -c -o
gvloadimage_gs.lo gvloadimage_gs.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../..
-I../../lib/common -I../.. -I../../lib/common -I../../lib/pathplan
-I../../lib/gvc -I../../lib/cgraph -I../../lib/cdt
-I/usr/include/pango-1.0 -I/usr/include
/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng16 -Wdate-time -D_FORTIFY_SOUR
CE=2 -g -O2 -fdebug-prefix-map=/build/graphviz-2.38.0=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wno-unknown-pragmas -Wstrict-prototypes -Wpointer-arith -Wall
-ffast-math -MT gvloadimage_gs.lo -MD -MP -MF .d
eps/gvloadimage_gs.Tpo -c gvloadimage_gs.c  -fPIC -DPIC -o
.libs/gvloadimage_gs.o
gvloadimage_gs.c: In function 'gs_error':
gvloadimage_gs.c:75:16: error: 'e_VMerror' undeclared (first use in
this function); did you mean 'gs_error'?
if (err >= e_VMerror)
   ^
   gs_error
gvloadimage_gs.c:75:16: note: each undeclared identifier is reported
only once for each function it appears in
gvloadimage_gs.c:77:21: error: 'e_unregistered' undeclared (first use
in this function); did you mean 'register_t'?
else if (err >= e_unregistered)
^~
register_t
gvloadimage_gs.c:79:21: error: 'e_invalidid' undeclared (first use in
this function); did you mean 'gs_error_invalidid'?
else if (err >= e_invalidid)
^~~
gs_error_invalidid
Makefile:750: recipe for target 'gvloadimage_gs.lo' failed
make[4]: *** [gvloadimage_gs.lo] Error 1
make[4]: Leaving directory '/build/graphviz-2.38.0/plugin/gs'
Makefile:592: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/build/graphviz-2.38.0/plugin'
Makefile:833: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/build/graphviz-2.38.0'
Makefile:645: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/graphviz-2.38.0'
debian/rules:100: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

I have subsequently been able to reproduce it with "pbuilder build
graphviz_2.38.0-18.dsc 

Bug#867914: psad: should depends net-tools, iproute2

[Andreas Beckmann]

Followup-For: Bug #867914
Control: reopen -1
Control: retitle -1 psad: should depend on net-tools and iproute2

Hi,

net-tools does not seem to be sufficient - iproute2 seems to be missing
as well:

# service psad start
[*] Could not find ip, edit /etc/psad/psad.conf at /usr/sbin/psad line 10933.
Unable to start the daemon.
Starting Port Scan Attack Detector: psad failed!


Andreas

Processed: Re: psad: should depends net-tools, iproute2

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #867914 {Done: Adrian Bunk } [psad] psad: should depends 
net-tools
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions psad/2.4.3-1.1.
> retitle -1 psad: should depend on net-tools and iproute2
Bug #867914 [psad] psad: should depends net-tools
Changed Bug title to 'psad: should depend on net-tools and iproute2' from 
'psad: should depends net-tools'.

-- 
867914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#869919: [DRE-maint] Bug#869919: remove ruby-berkshelf-api-client?

[Hleb Valoshka]

On 1/21/18, Balasankar "Balu" C  wrote:
> Any update on this? Was the berkshelf update done? Can we remove this
> package?

Unfortunately, I had no enough time to prepare a new berkshelf, but
you can request removal of ruby-berkshelf-api-client if it prevents
other packages updates.

Bug#887815: marked as done (network-manager-iodine FTBFS with network-manager 1.10.2-1)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:49:54 +
with message-id 
and subject line Bug#887815: fixed in network-manager 1.10.2-2
has caused the Debian Bug report #887815,
regarding network-manager-iodine FTBFS with network-manager 1.10.2-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-iodine
Version: 1.2.0-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/network-manager-iodine.html

...
gcc -DHAVE_CONFIG_H -I. -I..  -pthread -I/usr/include/libnm 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2 
-DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -DG_DISABLE_DEPRECATED 
-DBINDIR=\"/usr/bin\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" 
-DVERSION="\"1.2.0\"" -DLIBDIR=\""/usr/lib/x86_64-linux-gnu"\" 
-DLIBEXECDIR=\""/usr/lib/NetworkManager"\" -DLOCALSTATEDIR=\""/var"\" 
-DDATADIR=\"/usr/share\" -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -std=gnu89 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wshadow 
-Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement 
-Wstrict-prototypes -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare 
-fno-strict-aliasing -Werror -c -o nm-iodine-service.o nm-iodine-service.c
In file included from /usr/include/libnm/nm-utils.h:38:0,
 from /usr/include/libnm/nm-setting-ip-config.h:31,
 from /usr/include/libnm/nm-setting-ip4-config.h:30,
 from /usr/include/libnm/NetworkManager.h:72,
 from nm-iodine-service.c:45:
/usr/include/libnm/nm-setting-tc-config.h:43:1: error: 'NMTCQdisc' is 
deprecated: Not available before 1.10.2 [-Werror=deprecated-declarations]
 voidnm_tc_qdisc_ref  (NMTCQdisc *qdisc);
 ^~~~
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.10.2-2

We believe that the bug you reported is fixed in the latest version of
network-manager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Jan 2018 14:32:55 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev 
gir1.2-networkmanager-1.0 gir1.2-nm-1.0 
network-manager-config-connectivity-debian
Architecture: source
Version: 1.10.2-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-networkmanager-1.0 - GObject introspection data for the 
libnm-glib/libnm-util library
 gir1.2-nm-1.0 - GObject introspection data for the libnm library
 libnm-dev  - GObject-based client library for NetworkManager (development file
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util2 - network management framework (shared library)
 libnm0 - GObject-based client library for NetworkManager
 network-manager - network management framework (daemon and userspace tools)
 network-manager-config-connectivity-debian - NetworkManager configuration to 
enable connectivity checking
 network-manager-dev - network management framework (development files)
Closes: 887815
Changes:
 network-manager (1.10.2-2) unstable; urgency=medium
 .
   * libnm-core/tc-config: remove deprecation guards from typedefs
 (Closes: #887815)
   * Bump debhelper compat level to 11
Checksums-Sha1:
 

Bug#887753: marked as done (hddtemp FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:49:36 +
with message-id 
and subject line Bug#887753: fixed in hddtemp 0.3-beta15-53
has caused the Debian Bug report #887753,
regarding hddtemp FTBFS with glibc 2.26
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hddtemp
Version: 0.3-beta15-52
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hddtemp.html

...
backtrace.c: In function 'backtrace_handler':
backtrace.c:71:16: error: dereferencing pointer to incomplete type 'struct 
ucontext'
  (void*)puc->uc_mcontext.gregs[REG_IP]);
^~
--- End Message ---
--- Begin Message ---
Source: hddtemp
Source-Version: 0.3-beta15-53

We believe that the bug you reported is fixed in the latest version of
hddtemp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated hddtemp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Jan 2018 14:19:42 +0100
Source: hddtemp
Binary: hddtemp
Architecture: source
Version: 0.3-beta15-53
Distribution: unstable
Urgency: medium
Maintainer: Aurelien Jarno 
Changed-By: Aurelien Jarno 
Description:
 hddtemp- hard drive temperature monitoring utility
Closes: 836424 887753
Changes:
 hddtemp (0.3-beta15-53) unstable; urgency=medium
 .
   * src/backtrace.c: rename "struct ucontext" into "struct ucontext_t" to
 fix FTBFS with glibc 2.26 (closes: bug#887753).
   * debian/control: change priority to optional.
   * debian/control: drop Suggests: ksensors.
   * debian/control: bumped Standards-Version to 4.1.3.
   * debian/rules: rewrite using dh.
   * Added Brazilian Portuguese debconf templates. Thanks to Diego Neves
 (closes: bug#836424).
Checksums-Sha1:
 2f7795b3d96fd7c6de77dbfb9bd2a0c05a789848 1741 hddtemp_0.3-beta15-53.dsc
 52cc87c39d431b6d3804826c46a108e005f81caf 52845 hddtemp_0.3-beta15-53.diff.gz
 adfac61c285a49b5a9276c1f532a4faea7778a5c 5195 
hddtemp_0.3-beta15-53_source.buildinfo
Checksums-Sha256:
 7baf86b5093242460e0eca743b581fb05ca921b43064b7c7dd94048a396693cd 1741 
hddtemp_0.3-beta15-53.dsc
 6f1ddaa9fbc90ea5c00b949e0981b78c5014e109de88804ae2512209091eae56 52845 
hddtemp_0.3-beta15-53.diff.gz
 9ecd2bac4658b1570d2c0104e868fdac3f0fa9d8012190e24bd010de2ad053f3 5195 
hddtemp_0.3-beta15-53_source.buildinfo
Files:
 b8529d38089cef7622d266ba87147ba6 1741 utils optional hddtemp_0.3-beta15-53.dsc
 199a9c4fae4740c40f1bee288a3a3a5d 52845 utils optional 
hddtemp_0.3-beta15-53.diff.gz
 9adc49d3c54908e70db0b19ae03376d6 5195 utils optional 
hddtemp_0.3-beta15-53_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlpklN8ACgkQE4jA+Jno
M2uzUBAAh6qMy1ChC0k1E3MHN2obOnvVUmCWA0if8pVPr4tnp3kPiaqTIvTl7mw2
AZYF38+/nW4sM4UKISvnvnrvj+NkqXyu2+cK+TmXvTN2HWT+dy5B1y1zv4Wzsvtf
r/JO4GctAYDXTEDUY5mgYo84UtRItvDWG2fngppRfcH4YdpPfKtMJdxOKh3tc1er
50aIeVz/uib/bkR4EkidW2eEOAR1aPpWoxTcRPkSal6j+vtXK7nHqudp7Hxjil26
NsDpTkc891GtvKq3OsFuwS6CaDFzI035rRkYGsi5DpIRbZ2H+lp1VK3WI1LFeNWr
w0phACx6wWN64toIqc4EImpjGH5fgz8wudOch37WT0Ko+ktmKK82dyZFqofQsYgU
zYV/fRzBSi5mwqdAhp3tUvm/6PK4I9KBAmJihFY42My3wcoWI7WZnunAW8RtAur4
riixc+Jd/hcV3Pwq+76NbEWk4VXTetxWbOXD0l0aFSy30NAaDPdLAlhYIZviZlvb
mQqu/rplUylOsYM0PVSWhPR8FTlWhAnTE3g3RdW87HDo7neyvQYziDftZ8gz0YqC
NPNeRarqUbxzvuz5ExNeQP9uivs0b1eu4m+jjIO++V/SvAPiYwh4J0aunlOMz94S
39JzauMmpFHRR3+IJCiqTjma0lH3sd6FNVrWcWgBby316tb4Ew4=
=BmE6
-END PGP SIGNATURE End Message ---

Bug#885690: marked as done (sanduhr: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:24:12 +
with message-id 
and subject line Bug#887859: Removed package(s) from unstable
has caused the Debian Bug report #885690,
regarding sanduhr: Depends on old GNOME libraries
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sanduhr
Version: 1.93-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf libgnomecanvas libgnomeui libbonobo
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- gconf
- libart-lgpl
- libbonobo
- libbonoboui
- libgnome
- libgnomecanvas
- libgnomeui
- libgnomevfs
- liborbit

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.93-4+rm

Dear submitter,

as the package sanduhr has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887859

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#875118: marked as done ([pykde4] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:18:39 +
with message-id 
and subject line Bug#887377: Removed package(s) from unstable
has caused the Debian Bug report #875118,
regarding [pykde4] Future Qt4 removal from Buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
875118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pykde4
Version: 4:4.14.3-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 4:4.14.3-4+rm

Dear submitter,

as the package pykde4 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887377

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#858489: marked as done (python-kde4-dev: broken symlink: /usr/bin/pykdeuic4 -> ../share/pyshared/PyQt4/uic/pykdeuic4.py)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:18:39 +
with message-id 
and subject line Bug#887377: Removed package(s) from unstable
has caused the Debian Bug report #858489,
regarding python-kde4-dev: broken symlink: /usr/bin/pykdeuic4 -> 
../share/pyshared/PyQt4/uic/pykdeuic4.py
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
858489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-kde4-dev
Version: 4:4.14.3-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

3m46.5s ERROR: FAIL: Broken symlinks:
  /usr/bin/pykdeuic4 -> ../share/pyshared/PyQt4/uic/pykdeuic4.py


This is now located at
  /usr/lib/python2.7/dist-packages/PyQt4/uic/pykdeuic4.py


cheers,

Andreas


python-kde4-dev_4:4.14.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 4:4.14.3-4+rm

Dear submitter,

as the package pykde4 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887377

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#872901: marked as done (node-node-redis: unused and unmaintained upstream)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:19:06 +
with message-id 
and subject line Bug#887386: Removed package(s) from unstable
has caused the Debian Bug report #872901,
regarding node-node-redis: unused and unmaintained upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
872901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-node-redis
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-node-redis has seen no upstream activity fo 4 years.

According to https://github.com/tim-smart/node-redis/issues/4 another
similar project node-redis is more active.

This package has no reverse dependencies.

Perhaps sensible to simply drop this package?

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmb+wIACgkQLHwxRsGg
ASFvOA//VAXwaiH/X7HXl0cYBfQMoiJK8fja3jsUJ6H21XzpqGv0YGGHIZEneqjB
u2Y4RFTeZwmQ3CuQq2+QoEx4d/Rl76YsI+ikSxW40oZC2Tj+qRbiSB5+txqMH5if
YWIW/zNCpTvlN3ISH7cru1JvdNq4tXEQoChqb9fPde6DwknSy/ZArHG0PkoUyUFF
RdkpF39hgk4ZDwQXG8SRnkmH+RcJGFWjp6Rmwg7Qw0aHZM7sL30uuoD5Gqgo3EMn
O1W4bHrKwuT4yiXai5dCXDuXHMFVXYn/rAybQ/MHP1PvPDJOgbu9ck/C4flZWkO+
QTQ8OQKjiCfq0TtiWwN8saMz/sj8TUnZsApJiqnTA73V1MlQXgv/iRr5AogehCAF
lfAjyX07CDYntTn4VZdk2XoY7RbODsB7A0utMBpFrwGWIiThMk7+hUw00pdixRi7
wDmpl0AcMTcqkl6qZjtvCbtGwQufjMLosw8SwolZ5qX3JFBlRxNeHsxZLF9UBbHi
TgqoqmTujnhU51BoaDWAGUYAWq4wScod76GFoCnwIwEWb6sl2vhTejMU3oWCDvjC
cXqIKnd/JYl1JrMrdVHxNVGvRTVfyTjiAMON6OaFM8QHOWdaeA3tUCCgwsFKfZsJ
1j19nIX4TV/jIjQQ3R27kC5NzIrj/7UxWYqD6AWtYXmypXW+arQ=
=2+ra
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.1.7-1+rm

Dear submitter,

as the package node-node-redis has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887386

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#885372: marked as done (python-gpyconf: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:19:41 +
with message-id 
and subject line Bug#887388: Removed package(s) from unstable
has caused the Debian Bug report #885372,
regarding python-gpyconf: Depends on unmaintained pygtk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gpyconf
Version: 0.2-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: sunwea...@debian.org

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.2-1+rm

Dear submitter,

as the package python-gpyconf has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887388

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#856099: marked as done (extace: Please drop the (build-)dependency against esound)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:20:07 +
with message-id 
and subject line Bug#887430: Removed package(s) from unstable
has caused the Debian Bug report #856099,
regarding extace: Please drop the (build-)dependency against esound
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
856099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: extace
Version: 1.9.9-7
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal

Dear maintainer,

Your package is {build-}depending against esound which is deprecated
for quite some times now.

We are planning to remove esound for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Version: 1.9.9-7+rm

Dear submitter,

as the package extace has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887430

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#790185: marked as done (pypar2: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:17:38 +
with message-id 
and subject line Bug#887357: Removed package(s) from unstable
has caused the Debian Bug report #790185,
regarding pypar2: depends on vte which is deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
790185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pypar2
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte

Hi,

pypar2 depends on python-vte / libvte9, which are deprecated in favor
of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove src:vte
from the archive. pypar2 should switch to the new vte version.

Please try to do this before the Stretch release as we're going to
try to remove src:vte this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing vte completely.

If you have any question don't hesitate to ask.

Emilio 
--- End Message ---
--- Begin Message ---
Version: 1.4-7+rm

Dear submitter,

as the package pypar2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887357

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#790145: marked as done (screenlets: depends on python-wnck which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:15:55 +
with message-id 
and subject line Bug#887044: Removed package(s) from unstable
has caused the Debian Bug report #790145,
regarding screenlets: depends on python-wnck which is deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
790145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: screenlets
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-wnck gnome-python-desktop

Hi,

screenlets depends on python-wnck, which is long deprecated and going
to be removed from the archive. screenlets should switch to using the
GObject Introspection bindings for gnome-keyring, gir1.2-wnck-3.0.

This would mean switching to GObject Introspection for other bindings
as well, e.g. GLib and GTK+, so making the switch to GTK+ 3 at the
same time would make a lot of sense.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove it this cycle.

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.1.2-8.1+rm

Dear submitter,

as the package screenlets has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887044

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#790602: marked as done (screenlets: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 21 Jan 2018 13:15:55 +
with message-id 
and subject line Bug#887044: Removed package(s) from unstable
has caused the Debian Bug report #790602,
regarding screenlets: depends on python-gnome2 which is deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
790602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: screenlets
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

screenlets depends on python-gnome2, which is long deprecated and
going to be removed from the archive. screenlets should be ported
away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove python-gnome2 this cycle.

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.1.2-8.1+rm

Dear submitter,

as the package screenlets has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/887044

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---