Processed: tagging 811432

[Debian Bug Tracking System]

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

> tags 811432 + pending
Bug #811432 [krita] sid: unable to install, missing deps: libilmbase6 
libopenexr6
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811846: #811846: status?

[Pino Toscano]

Hi,

what's the status of this bug (xbase64 that FTBFS with GCC 6)?
Because of it, xbase64 was removed from testing a couple of months ago,
and now it will prevent calligra (which ships a sybase access driver
for kexi) to migrate to testing.

Any way I can help with this?

Thanks,
-- 
Pino Toscano

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

Bug#838050: GDM3-only behaviour; Wayland not totally broken; bad tablets break even that

[Andrew Chadwick]

The behaviour in gdm3 alone (outside of a user session) is different 
from tablet to tablet.


* Wacom Intuos5 USB: no crashes, pen functions as a second crosshair 
pointer
* HUION H610PRO USB: no crashes, pen functions as a second crosshair 
pointer
* Genius EasyPen i405X USB: crashes gnome-session in this environment 
as well, repeatedly, same segfault from gnome-shell. systemd appears to 
be desperately trying to launch Xorg instead afterwards? Which then 
*also* segfaults repeatedly.


The Huion and Wacom tablets work inside GNOME-on-Wayland user sessions, 
and gtk3-demo's "Touch and Drawing Tablets" module presents their extra 
axes (pressure, or pressure+tilt+distance, respectively). However using 
Wayland is not really a great workaround currently given how crashy it 
is (xwayland 2:1.18.4-1, pressing Alt kills Chromium, wow.)


The Genius tablet is well known as a horrid crashy mess generally, 
which is why I bought it. This behaviour is new even for that, however.


-8<-
Sep 18 03:17:32 spatula kernel: [50703.338856] usb 2-1: new low-speed 
USB device number 35 using xhci_hcd
Sep 18 03:17:32 spatula kernel: [50703.532827] usb 2-1: New USB device 
found, idVendor=0458, idProduct=5010
Sep 18 03:17:32 spatula kernel: [50703.532834] usb 2-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
Sep 18 03:17:32 spatula kernel: [50703.532838] usb 2-1: Product: 
EasyPen i405X
Sep 18 03:17:32 spatula kernel: [50703.532841] usb 2-1: Manufacturer: 
Genius
Sep 18 03:17:32 spatula kernel: [50703.561689] input: Genius EasyPen 
i405X as 
/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0/0003:0458:5010.0040/input/input175
Sep 18 03:17:32 spatula kernel: [50703.615183] kye 0003:0458:5010.0040: 
input,hiddev0,hidraw2: USB HID v1.11 Device [Genius EasyPen i405X] on 
usb-:00:14.0-1/input0
Sep 18 03:17:32 spatula mtp-probe: checking bus 2, device 35: 
"/sys/devices/pci:00/:00:14.0/usb2/2-1"
Sep 18 03:17:32 spatula mtp-probe: bus: 2, device: 35 was not an MTP 
device
Sep 18 03:17:33 spatula gnome-shell[29393]: Could not get tablet 
information for 'Genius EasyPen i405X': (null)
Sep 18 03:17:33 spatula kernel: [50704.317185] gnome-shell[29393]: 
segfault at 10 ip 7fd62869e844 sp 7ffe16cebae0 error 4 in 
libwacom.so.2.5.0[7fd62869b000+9000]

Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: (EE)
Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: Fatal server 
error:
Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: (EE) failed to 
dispatch Wayland events: Broken pipe

Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: (EE)
[... one more segfault ...]
Sep 18 03:17:35 spatula gdm3: Child process -29545 was already dead.
Sep 18 03:17:35 spatula gdm3: Child process 29534 was already dead.
Sep 18 03:17:35 spatula gdm3: Unable to kill session worker process
Sep 18 03:17:35 spatula systemd[1]: Started Session c22 of user 
Debian-gdm.
Sep 18 03:17:35 spatula udev-acl.ck[29583]: g_slice_set_config: 
assertion 'sys_page_size == 0' failed
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: (--) Log 
file renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-29585.log" 
to "/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: X.Org X 
Server 1.18.4
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: Release 
Date: 2016-07-19
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: X Protocol 
Version 11, Revision 0

[... starts up, then a stream of new segfaults ...]
->8-

Processed: bug 838050 control

[Debian Bug Tracking System]

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

> affects 838050 + libwacom2 gimp mypaint
Bug #838050 [gnome-shell] gnome-shell: gdm doesn't start due to a problem with 
gnome-shell crashing in libwacom2
Added indication that 838050 affects libwacom2, gimp, and mypaint
> tags 838050 + confirmed
Bug #838050 [gnome-shell] gnome-shell: gdm doesn't start due to a problem with 
gnome-shell crashing in libwacom2
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#838050: Breaks all tablets, no good workaround

[Andrew Chadwick]

My first through was the common Debian situation where there's a
mismatch between libwacom2 (which lags releases regularly) and GNOME
(which advances fast). It may well not be libwacom at fault, but
without a debugging trace we can't tell yet. A recent update to
libwacom 0.22 doesn't fix this issue, however. See also Bug#838047 <
https://bugs.debian.org/838047 >.

This breaks gnome-shell with all the Wacom and non-Wacom graphics
tablets I've tried, crashing gnome-shell at or shortly after the point
when they are connected. However the non-tablet USB devices I've tried
seem OK, including my (non-Wacom, non-pen, regular multitouch)
touchscreen. See bug 838047 for details and log traces.

I cannot get the suggested rmmod workaround to work on my system. The
non-Wacom tablets still cause gnome-shell to crash immediately upon
being plugged in, and when a Wacom tablet is plugged in, the "wacom"
kernel module is automatically loaded and stays loaded.

I am using Wayland gdm3, and Xorg user gnome-shell sessions.

gnome-shell   3.21.91-2
gdm3   3.21.90-1
libwacom2   0.22-1

-- 
Andrew Chadwick

Bug#838047: Confirmed: breaks *all* tablets

[Andrew Chadwick]

GNOME sessions with gnome-shell 3.21.91-2 and libwacom2 0.22-1 still
segfault when any any of my USB tablet devices are attached. This
includes the Wacom USB Wireless Accessory Kit: it's fine after being
plugged in initially without the tablet being turned on, but when the
tablet is turned on and begins communicating wirelessly, the session
dies just as above.

I've tried a plain old USB optical mouse, a USB keyboard, and a couple
of USB joypads too - those are unaffected.

>From the console, libwacom-list-local-devices 0.22 detects the plugged
device and lists its features like it should. No segfaults there.

Bug#822051: marked as done (lmbench: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Sun, 18 Sep 2016 00:34:04 +
with message-id 
and subject line Bug#822051: fixed in lmbench 3.0-a9-1.2
has caused the Debian Bug report #822051,
regarding lmbench: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lmbench
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package lmbench builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that lmbench builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to lmbench at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, lmbench will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: lmbench
Source-Version: 3.0-a9-1.2

We believe that the bug you reported is fixed in the latest version of
lmbench, 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 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated lmbench 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, 18 Sep 2016 02:12:05 +0200
Source: lmbench
Binary: lmbench lmbench-doc
Architecture: all amd64 i386 source
Version: 3.0-a9-1.2
Distribution: unstable
Urgency: medium
Maintainer: Al Stone 
Changed-By: Andreas Beckmann 
Closes: 817567 822051
Description: 
 lmbench- Utilities to benchmark UNIX systems
 lmbench-doc - Documentation for the lmbench benchmark suite
Changes:
 lmbench (3.0-a9-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build-arch/build-indep targets.  (Closes: #822051)
   * Switch to debhelper compat level 5.  (Closes: #817567)
Checksums-Sha1: 
 e1fb2281cbe3c87b76b7e214b57128cba52bb336 1765 lmbench_3.0-a9-1.2.dsc
 0abe9eb19e09a35936c391a8e3457c7ded808b44 14840 lmbench_3.0-a9-1.2.diff.gz
 166a87615ee13ca5f4f2e084e07e3a898e5363b0 52134 
lmbench-dbgsym_3.0-a9-1.2_amd64.deb
 3e39be5aed712250c1b8cba78c8224329cda3128 253162 lmbench-doc_3.0-a9-1.2_all.deb
 2c6b09af0b3af38c2424aa7d8751ec00ed351aa8 416122 lmbench_3.0-a9-1.2_amd64.deb
 157049c4f5fce1252d7aa8a7be1b19ecab6cf621 51918 
lmbench-dbgsym_3.0-a9-1.2_i386.deb
 687c1407c2818c57b4bba3fb1d913d62a80fd848 421492 lmbench_3.0-a9-1.2_i386.deb
Checksums-Sha256: 
 59af2d62e5655ca2c1c326fcce5745994de1e0f1d28b66013cbed73679e41fd7 1765 
lmbench_3.0-a9-1.2.dsc
 f2d673b9ba0a4979b0cb1bf18e4b2dae5dac3485973e1f38c35f2a245cf2845f 14840 
lmbench_3.0-a9-1.2.diff.gz
 02b698f0bf26a00d0eeac012f55a4790d65bc32542271d0f711dd5531846 52134 
lmbench-dbgsym_3.0-a9-1.2_amd64.deb
 ef25f33c75f4850667636d80c349738300fe7a45fbb9f8f65c852387a7ffdab7 253162 
lmbench-doc_3.0-a9-1.2_all.deb
 30e0eb1ecedead48514d6944f2b5d9118026115f50e9d3fd4fbcdd010f2d77e6 416122 
lmbench_3.0-a9-1.2_amd64.deb
 50e4fbfd67532337e065279fea006e0d5dead63bd42f268979a50be17c7364e9 51918 
lmbench-dbgsym_3.0-a9-1.2_i386.deb
 ef33c153fbad741ebaf3e95af14ce7fcfb77a5a60766b2d7d0b9985e738d61a5 421492 
lmbench_3.0-a9-1.2_i386.deb
Files: 
 333b6c436b008988ee010910e39211b3 1765 non-free/admin optional 
lmbench_3.0-a9-1.2.dsc
 bd4b85d724069335730a7ae199cc63a5 14840 non-free/admin optional 
lmbench_3.0-a9-1.2.diff.gz
 b08fb27678f6aaed9c199b1dea4af615 52134 non-free/debug extra 
lmbench-dbgsym_3.0-a9-1.2_amd64.deb
 52a366135cb1f9f500b256040c5662d2 253162 non-free/doc optional 
lmbench-doc_3.0-a9-1.2_all.deb
 c22292f45d262db2b2f64f3d78349bac 416122 non-free/admin optional 
lmbench_3.0-a9-1.2_amd64.deb
 

Bug#817567: marked as done (lmbench: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 18 Sep 2016 00:34:04 +
with message-id 
and subject line Bug#817567: fixed in lmbench 3.0-a9-1.2
has caused the Debian Bug report #817567,
regarding lmbench: Removal of debhelper compat 4
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.)


-- 
817567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lmbench
Severity: important
Usertags: compat-4-removal

Hi,

The package lmbench uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: lmbench
Source-Version: 3.0-a9-1.2

We believe that the bug you reported is fixed in the latest version of
lmbench, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated lmbench 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, 18 Sep 2016 02:12:05 +0200
Source: lmbench
Binary: lmbench lmbench-doc
Architecture: all amd64 i386 source
Version: 3.0-a9-1.2
Distribution: unstable
Urgency: medium
Maintainer: Al Stone 
Changed-By: Andreas Beckmann 
Closes: 817567 822051
Description: 
 lmbench- Utilities to benchmark UNIX systems
 lmbench-doc - Documentation for the lmbench benchmark suite
Changes:
 lmbench (3.0-a9-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build-arch/build-indep targets.  (Closes: #822051)
   * Switch to debhelper compat level 5.  (Closes: #817567)
Checksums-Sha1: 
 e1fb2281cbe3c87b76b7e214b57128cba52bb336 1765 lmbench_3.0-a9-1.2.dsc
 0abe9eb19e09a35936c391a8e3457c7ded808b44 14840 lmbench_3.0-a9-1.2.diff.gz
 166a87615ee13ca5f4f2e084e07e3a898e5363b0 52134 
lmbench-dbgsym_3.0-a9-1.2_amd64.deb
 3e39be5aed712250c1b8cba78c8224329cda3128 253162 lmbench-doc_3.0-a9-1.2_all.deb
 2c6b09af0b3af38c2424aa7d8751ec00ed351aa8 416122 lmbench_3.0-a9-1.2_amd64.deb
 157049c4f5fce1252d7aa8a7be1b19ecab6cf621 51918 
lmbench-dbgsym_3.0-a9-1.2_i386.deb
 687c1407c2818c57b4bba3fb1d913d62a80fd848 421492 lmbench_3.0-a9-1.2_i386.deb
Checksums-Sha256: 
 59af2d62e5655ca2c1c326fcce5745994de1e0f1d28b66013cbed73679e41fd7 1765 
lmbench_3.0-a9-1.2.dsc
 f2d673b9ba0a4979b0cb1bf18e4b2dae5dac3485973e1f38c35f2a245cf2845f 14840 
lmbench_3.0-a9-1.2.diff.gz
 02b698f0bf26a00d0eeac012f55a4790d65bc32542271d0f711dd5531846 52134 
lmbench-dbgsym_3.0-a9-1.2_amd64.deb
 ef25f33c75f4850667636d80c349738300fe7a45fbb9f8f65c852387a7ffdab7 253162 
lmbench-doc_3.0-a9-1.2_all.deb
 30e0eb1ecedead48514d6944f2b5d9118026115f50e9d3fd4fbcdd010f2d77e6 416122 
lmbench_3.0-a9-1.2_amd64.deb
 50e4fbfd67532337e065279fea006e0d5dead63bd42f268979a50be17c7364e9 51918 
lmbench-dbgsym_3.0-a9-1.2_i386.deb
 ef33c153fbad741ebaf3e95af14ce7fcfb77a5a60766b2d7d0b9985e738d61a5 421492 
lmbench_3.0-a9-1.2_i386.deb
Files: 
 333b6c436b008988ee010910e39211b3 1765 non-free/admin optional 
lmbench_3.0-a9-1.2.dsc
 bd4b85d724069335730a7ae199cc63a5 14840 non-free/admin optional 
lmbench_3.0-a9-1.2.diff.gz
 b08fb27678f6aaed9c199b1dea4af615 52134 non-free/debug extra 
lmbench-dbgsym_3.0-a9-1.2_amd64.deb
 52a366135cb1f9f500b256040c5662d2 253162 non-free/doc optional 
lmbench-doc_3.0-a9-1.2_all.deb
 c22292f45d262db2b2f64f3d78349bac 416122 non-free/admin optional 
lmbench_3.0-a9-1.2_amd64.deb
 2dff4ef7f0e2f6500ca4e16d974ceec2 51918 non-free/debug extra 
lmbench-dbgsym_3.0-a9-1.2_i386.deb
 781def5e0e2d62ce4de7f8ae147a2cbd 421492 non-free/admin optional 
lmbench_3.0-a9-1.2_i386.deb

-BEGIN PGP SIGNATURE-
Version: 

Bug#817516: marked as done (lakai: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 23:48:29 +
with message-id 
and subject line Bug#817516: fixed in lakai 0.1-1.1
has caused the Debian Bug report #817516,
regarding lakai: Removal of debhelper compat 4
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.)


-- 
817516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lakai
Severity: important
Usertags: compat-4-removal

Hi,

The package lakai uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: lakai
Source-Version: 0.1-1.1

We believe that the bug you reported is fixed in the latest version of
lakai, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gustavo Soares de Lima  (supplier of updated lakai 
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: Wed, 07 Sep 2016 16:41:52 +
Source: lakai
Binary: lakai
Architecture: source
Version: 0.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Free Ekanayaka 
Changed-By: Gustavo Soares de Lima 
Description:
 lakai  - transfers samples between a PC and an AKAI sampler
Closes: 449603 450202 817516 835651
Changes:
 lakai (0.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/compat:
   - Update level to 9. (Closes: #817516)
   * debian/control:
   - Added Homepage. (Closes: #835651)
   - Bumped level debhelper to 9.
   - Bumped Standards-Version to 3.9.8.
   * debian/watch:
   - Update. (Closes: #449603, #450202).
Checksums-Sha1:
 eb85a022cc9c158c575d0dd8d43e7076c804bc5d 1617 lakai_0.1-1.1.dsc
 245deda9478e93c005f0a93182b7b806317422b6 2299 lakai_0.1-1.1.diff.gz
Checksums-Sha256:
 4b94353b8c53f3cd0ed9cf30c96afdde349d528c24c6f8d76dd835ffe5932b5e 1617 
lakai_0.1-1.1.dsc
 811672d01e70007ca2c2631d4149b9efe44289a32cd033ae88af4e87765c37a4 2299 
lakai_0.1-1.1.diff.gz
Files:
 ad8d9d6e95cd7de55b83b9a0d7228f5c 1617 sound optional lakai_0.1-1.1.dsc
 15b143eaaa70c852ed5d02f935464f9a 2299 sound optional lakai_0.1-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX0J5+AAoJEN5juccE6+nvKUAP/0dgBltDHFQoslwLXK9UO9Nx
jnlcxfAdmBklJ0VHgQOdlVIMlnzQ4vb5dBDCec25gg9Lqbgd1W29G1zPiqBhe1Qm
8JQGjCOw/Prlm7UzZkBVG7p5LBuNQNaizxSitYDMCCBtk/K06zuRNPLuLX2Bc5+p
58uC+DYzuu/w1IRLdxt/gvnRmvU3PZh/EDhJt2GCxL7JZs2IAN/mexxaelhoH6t6
b/jfSvzIGpZ/F8zG3PvdEk04k1RVZ3d8kbp1bjyIDgkp+OY4KVb+ZHr20FXgNiKA
0Fo4PFZyEi8EAnFrg8F2Xox1TLRYWS4YmvQPCIStR7CEdzGWZffMSBEVRmnrVrhw
e9jAU/vjWLw8//uf/F11fyXLEVs3kDm0peK3ACk+RPL4hR/wm2cAlWlGOtyXNxi8
0jVXgFuHqJJ9EgDAQuqGtQVDWsqNtTWgew0EL+cPmuLInA6Nh6V6NYeXCPJ64+Fq
kYl5FJQLgDzeX9NqfVRxzfSmXB5THJjRVAp7IhgMwy5bA1O0AFVuvwc10oSPnPHr
2OvceINwfxEp+Bv0CUJ/bd5mP1QM4LBuF6ueMD2pe3htul/oupdTiabw6iUHqI2m
5Tw3AHSpVjdHlSjTbd5KtRuuuiyiyyhNr582Qx4raYXn1p7bDuOtNCWGJFBkwNYP
TKjoWNF0EgfA/CI2GXFZ
=eSdW
-END PGP SIGNATURE End Message ---

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:

> There is at one report of an OpenRD ultimate that would not boot with
> the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to
> unstable a few days ago. Would you be able to confirm if OpenRD variants
> that you have still work with the version in unstable?
> 
>  https://bugs.debian.org/837629
> 
> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
> so that u-boot 2016.09 can migrate to stretch... but it would be more
> ideal to fix it, of course! :)
> 
> 
> live well,
>  vagrant

Sorry!

It looks like you’ll have to pull OpenRD support out of this version.  I tried 
2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result with it as I got 
with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no response following u-boot 
“reset” command.

Enjoy!
Rick

Processed: Re: Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: 
rename involves overwriting `/usr/bin/qgis'
Added tag(s) pending.

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

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Andreas,

On 09/17/2016 06:39 PM, Andreas Beckmann wrote:
> still not completely resolved,

Will the third time be the charm?

I haven't been able to reproduce this issue with my piuparts setup, not
now and not before, I guess piuparts.d.o. does something more
complicated than:

 piuparts -d jessie -d stretch -a qgis

I have now been able reproduce this issue manually in a jessie
cowbuilder chroot by installing qgis (with recommended dependencies),
and upgrading it to stretch via the usual procedure (apt-get upgrade
followed by apt-get dist-upgrade).

> I'll try to find some time to look there myself.
> 
>   Preparing to unpack .../qgis_2.14.6+dfsg-3_amd64.deb ...
>   Unpacking qgis (2.14.6+dfsg-3) over (2.4.0-1+b1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/qgis_2.14.6+dfsg-3_amd64.deb (--unpack):
>trying to overwrite '/usr/bin/qbrowser.bin', which is the diverted version 
> of '/usr/bin/qbrowser' (package: qgis-plugin-grass)

Do you have a more complete log than the above?
piuparts.debian.org/jessie2stretch still reports:

 successfully-tested 2.14.5+dfsg-2

Since the unpack is already failing, I think the diversion should also
be removed by the maintainer scripts for qgis-plugin-grass, not just
qgis as it is now. I suspect the complete log to confirm that
qgis-plugin-grass is upgraded before qgis is, that's what I'm seeing in
my jessie to stretch upgrade.

Some testing of the above reveals that adding the maintainers scripts to
qgis-plugin-grass to remove the diversion is not sufficient. The jessie
version of qgis-plugin-grass only removes the diversion in postrm which
is called after the new package's files are unpacked which is too late
because the unpackaging causes the error.

I think the jessie version of qgis needs to be fixed to remove the
diversion in qgis-plugin-grass.prerm too, because a version of the
package is already "Installed".

Because the qgis-plugin-grass package is being upgraded, the new preinst
could also remove the diversions before the new package's files are
unpacked. But unfortunately that fails with:

dpkg-divert: error: rename involves overwriting `/usr/bin/qgis.bin' with
  different file `/usr/bin/qgis', not allowed

Just removing without renaming in qgis.preinst could be the actual
solution, it seems to give the desired results:

Preparing to unpack .../qgis_2.14.6+dfsg-4_amd64.deb ...
Removing 'diversion of /usr/bin/qgis to /usr/bin/qgis.bin by
qgis-plugin-grass'
Removing 'diversion of /usr/bin/qbrowser to /usr/bin/qbrowser.bin by
qgis-plugin-grass'
Unpacking qgis (2.14.6+dfsg-4) over (2.4.0-1+b1) ...

It's a much simpler change in addition to the one fixing #817176, I
should have thought of that sooner before you led me astray with your
suggestions in this issue.

I'm going to upload the above which should finally fix this issue.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#811584: marked as done (FTBFS with GCC 6: statement indented as if it were guarded by)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 22:28:01 +
with message-id 
and subject line Bug#811584: fixed in phalanx 22+d051004-14
has caused the Debian Bug report #811584,
regarding FTBFS with GCC 6: statement indented as if it were guarded by
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.)


-- 
811584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phalanx
Version: 22+d051004-13.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> gcc -O0 -Wall -Werror  -fomit-frame-pointer -std=c99 -D_GNU_SOURCE -march=k8 
> -DGNUFUN -DPBOOK_DIR=\"/usr/share/games/phalanx\" 
> -DSBOOK_DIR=\"/usr/lib/games/phalanx\" -DLEARN_DIR=\"/var/games\" 
> -DLEARN_FILE=\"phalanx.learn\" -DDEBIAN -c bcreate.c -o .o/bcreate.o
> bcreate.c: In function 'parsegame':
> bcreate.c:223:5: error: statement is indented as if it were guarded by... 
> [-Werror=misleading-indentation]
>  while( (c=getchar())==' ' || c=='\n' ) {}
>  ^
> 
> bcreate.c:216:5: note: ...this 'while' clause, but it is not
>{ while( (c=getchar()) != '.' && c!=EOF )
>  ^
> 
> cc1: all warnings being treated as errors
> makefile:37: recipe for target '.o/bcreate.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: phalanx
Source-Version: 22+d051004-14

We believe that the bug you reported is fixed in the latest version of
phalanx, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jose G. López  (supplier of updated phalanx 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: Sat, 17 Sep 2016 20:07:04 +0200
Source: phalanx
Binary: phalanx
Architecture: source
Version: 22+d051004-14
Distribution: unstable
Urgency: medium
Maintainer: Jose G. López 
Changed-By: Jose G. López 
Description:
 phalanx- Chess playing program
Closes: 811526 811584 835309
Changes:
 phalanx (22+d051004-14) unstable; urgency=medium
 .
   * Fix FTBS with GCC 6. (Closes: #811584)
   * Set myself as Maintainer. (Closes: #835309)
   * debian/compat: Upgrade to version 9.
   * debian/config: Fix lintian report 'maintainer-script-without-set-e'.
   * debian/control:
 - Bump to Standards-Version 3.9.8. No changes required.
 - Add Vcs-* fields to show where development is done.
   * debian/copyright: Update and change Format tag to the accepted one.
   * debian/install: Prefer book files in /usr/share/phalanx.
   * debian/patches:
 - 03_makefile_DEFINES.diff: Refresh to avoid arch specific flags, added
   hardening and install book dirs in /usr/share/phalanx.
 - 04_PG_setboard_command.diff: Update to remove 'setboard' as it is
   applied in other patch.
 - 25_arch_compiler-flags: Remove. Avoid arch specific flags.
   * debian/po:
 - pt_BR.po: New, thanks to Adriano Rafael Gomes. (Closes: #811526)
 - ca.po: Update to remove fuzzy translations.
   * debian/rules:
 - Remove conditional architecture build options. No optimized compilation.
 - Add hardening flags.
 - Add --parallel option to debhelper.
Checksums-Sha1:
 003f9aeac1e8e7116a7b04bde35b0622dccda431 1829 phalanx_22+d051004-14.dsc
 c46954030e0b1e99278de45036dac42df58202a8 18992 
phalanx_22+d051004-14.debian.tar.xz
Checksums-Sha256:
 b14f1f275513cb0309b7c1e29d16a3065029f5077bf9517583dab81dbd2c3537 1829 
phalanx_22+d051004-14.dsc
 a3d53c1d916b48557241a41ddc57b7b012d0a3bcaaa2aab7ad40006f9fa9c492 18992 
phalanx_22+d051004-14.debian.tar.xz

Bug#834960: marked as done (libdaemon-generic-perl: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 22:22:40 +
with message-id 
and subject line Bug#834960: fixed in libdaemon-generic-perl 0.84-2
has caused the Debian Bug report #834960,
regarding libdaemon-generic-perl: FTBFS too much often (failing tests)
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.)


-- 
834960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libdaemon-generic-perl
Version: 0.84-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Daemon::Generic
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1

[... snipped ...]

ok 28 - process 31310 is alive - event
ok 29 - config ok - event
ok 30 - running
ok 31 - kill message
ok 32 - process is dead - event
ok 33 - config ok
ok 34 - not running
ok 35 - restart message - start - event
ok 36 - restart message - kill
ok 37 - restart message - start - event
ok 38 - check
ok 39 - stop message
ok 40 - check - event
ok 41 - start message - anyevent
ok 42 - pid
ok 43 - counter1 - anyevent
ok 44 - logged output
ok 45 - daemonized
ok 46 - reconfig message
ok 47 - counter2
ok 48 - process 31381 is alive - anyevent
ok 49 - config ok - anyevent
ok 50 - running
ok 51 - kill message
ok 52 - process is dead - anyevent
ok 53 - config ok
ok 54 - not running
ok 55 - restart message - start - anyevent
ok 56 - restart message - kill
ok 57 - restart message - start - anyevent
ok 58 - check
ok 59 - stop message
ok 60 - check - anyevent
ok 61 - finished
1..61
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/61 subtests 

Test Summary Report
---
t/daemon.t (Wstat: 256 Tests: 61 Failed: 1)
  Failed test:  4
  Non-zero exit status: 1
Files=1, Tests=61, 33 wallclock secs ( 0.03 usr  0.01 sys +  1.78 cusr  0.18 
csys =  2.00 CPU)
Result: FAIL
Failed 1/1 test programs. 1/61 subtests failed.
Makefile:858: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense, and the fact that I was
doing "dpkg-buildpackage -A" does not mean anything special.

I attach three build logs. There are more here:

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

Thanks.

libdaemon-generic-perl_0.84-1_amd64-20160814T1442Z.gz
Description: application/gzip


libdaemon-generic-perl_0.84-1_amd64-20160816T2138Z.gz
Description: application/gzip


libdaemon-generic-perl_0.84-1_amd64-20160820T223119Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libdaemon-generic-perl
Source-Version: 0.84-2

We believe that the bug you reported is fixed in the latest version of
libdaemon-generic-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 834...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libdaemon-generic-perl 
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: Sat, 17 Sep 2016 23:47:32 +0200
Source: libdaemon-generic-perl
Binary: libdaemon-generic-perl
Architecture: source
Version: 0.84-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 

Bug#820401: marked as done (ciphersaber: FTBFS on binary-indep-only build)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 22:00:57 +
with message-id 
and subject line Bug#820401: fixed in ciphersaber 1.01-1
has caused the Debian Bug report #820401,
regarding ciphersaber: FTBFS on binary-indep-only build
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.)


-- 
820401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ciphersaber
Version: 0.61-4.2
Severity: serious
Justification: fails to build from source

Hi,

ciphersaber builds fine if a full build of the package is requested, but
fails if only the binary-indep packages are to be built (which should
produce the same packages):

https://buildd.debian.org/status/fetch.php?pkg=ciphersaber=all=0.61-4.2=1459571526

The binary-arch and binary-indep targets in debian/rules need to be
swapped: binary-arch should be the no-op one.


Andreas
--- End Message ---
--- Begin Message ---
Source: ciphersaber
Source-Version: 1.01-1

We believe that the bug you reported is fixed in the latest version of
ciphersaber, 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 820...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Hornburg (Racke)  (supplier of updated ciphersaber 
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: Sat, 17 Sep 2016 17:20:15 +0200
Source: ciphersaber
Binary: libcrypt-ciphersaber-perl
Architecture: source all
Version: 1.01-1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Stefan Hornburg (Racke) 
Description:
 libcrypt-ciphersaber-perl - Perl module implementing CipherSaber encryption
Closes: 329520 820401
Changes:
 ciphersaber (1.01-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #329520).
   * Use simple rules file and updates to control file (Closes: #820401).
   * Updated watch file from bartm.
Checksums-Sha1:
 2978cd45d44ab0ce3bbe612fba5258290659c014 1709 ciphersaber_1.01-1.dsc
 a763c294d864963e932c9552d1017c6aac628573 10197 ciphersaber_1.01.orig.tar.gz
 e9b6f70bd9d7540dd97e616930d17f2581072244 1830 ciphersaber_1.01-1.diff.gz
 1cb72b4f73ed37b6aef3356d9f9b6e883a357cff 10324 
libcrypt-ciphersaber-perl_1.01-1_all.deb
Checksums-Sha256:
 573561828582265f4336038abf1508fe5893f63f6874bd3df23e0aa24f0fe249 1709 
ciphersaber_1.01-1.dsc
 040cce0b7d4437072f6978aff9eecaf726533e29251493f049b51be168403afb 10197 
ciphersaber_1.01.orig.tar.gz
 93fc6430b3f261212d23b8f53cf3981a2cdd89b55489052350a8cfee08d05667 1830 
ciphersaber_1.01-1.diff.gz
 67e9282d5fdb6d791be7ec2e3e8d8c879acc732ca1fbacb16e587bfe5ecd3950 10324 
libcrypt-ciphersaber-perl_1.01-1_all.deb
Files:
 3186c4c7814c860c0a92513bde9e7500 1709 interpreters optional 
ciphersaber_1.01-1.dsc
 316e84710e272707cb319a322ac37f4f 10197 interpreters optional 
ciphersaber_1.01.orig.tar.gz
 06708c84285b32b7dd7e8b41d621e689 1830 interpreters optional 
ciphersaber_1.01-1.diff.gz
 0d6813363c985d3423c78045d7522f9c 10324 interpreters optional 
libcrypt-ciphersaber-perl_1.01-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX3WJhAAoJEFuTAVv6JyD4oBgQAJGTta0Fm6D85dio3x0/vgkG
a0hJEOe1szEVcCvGm0eEB6owaBH5L8Jni88u86/Nt2xTakOIdvOBxreFMZwcoyfu
zT1jmqO4khZqoJQ54kN07bY7rsWvsbuvBATLFNCoXCyJ7vyMvVjZCTkiwGYwAWqD
tnowuAQEtfe90NroZwudZsRxCwVIq6Qbm5TznuBunBTODdXGA6lrntWVwZ5omKGb
rxPq9CjIGQuBFhse0/vzxgWYJ3a6wG8MamxoNEAl6NBYlLJp4i1kJf0sV8krlu6x
Lg57tjPyYMPi9KB6t8hemUZINOenphKPoeWddz06/dFKPwBJZS5HFSwdeihdp8qW
6oWm2Ce0veBy8M1q81FLNRJWDRzPYbnjmARliXlF2CUhL2pdwlzqSWUwQWtep/mA
AxNKtCli4TmxtSz00t12VaKaB4gxQ7PyYmCE3GpOlv+NLTI1xXJggn8Jo6/h8yyj
e/wPLpy9VAZz4ZQt+HYo/J0kuvXYrJp5+G1N4ajOAwnh6lzuFJ2j5sBBUNMdk9bI
oa2Ath19h6PVdCSuIsJHUfG8GCb3ioJU7f2f8W8exRh0ejz0wuC09qqO5Rbr3z7R
Ki58EF8+7HlZqzGZaBjvKVitBKCoi9xsMjsNPK5IETTjJtXOOUREC9g7+lPhH+/l
X/MjiwWVqlPLcqkphlXh
=7pJL
-END PGP SIGNATURE End Message ---

Bug#834960: Pending fixes for bugs in the libdaemon-generic-perl package

[pkg-perl-maintainers]

tag 834960 + pending
thanks

Some bugs in the libdaemon-generic-perl package are closed in
revision 75331d5d9ccbf69f8b7c3a410ef189dd1eb791a2 in branch 'master'
by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdaemon-generic-perl.git/commit/?id=75331d5

Commit message:

Add patch to fix race condition in test suite.

Thanks: Niko Tyni for the patch.
Closes: #834960

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[gregor herrmann]

On Sat, 17 Sep 2016 21:27:33 +0300, Niko Tyni wrote:

> > From starting at t/daemon.t my guess is that we're seeing a race
> > condition or some other timing issue here -- the daemon writes to a
> > log file and the test reads the logfile, and in one case the log
> > message doesn't seem to be there (yet?). At least that's my current
> > guess.
> Indeed, the daemon first opens the file for writing and only then writes
> it (see the logger script at top of daemon.t), while the test waits for
> existence (-e) and then proceeds to check the file contents.
> 
> I think the attached patch should fix it. I was able to reproduce
> the issue sporadically without the patch, and couldn't get it to
> happen after applying this.

Great, thanks.
 
> > I'm tempted to mark this log-reading test as TODO since this seems a
> > bit fragile.
> No objections, but let's try the patch first?

Sure, a fix is always better than a workaround :)


Patch forwarded upstream, package uploaded.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tony Joe White: Goin' Down Rockin'


signature.asc
Description: Digital Signature

Processed: Pending fixes for bugs in the libdaemon-generic-perl package

[Debian Bug Tracking System]

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

> tag 834960 + pending
Bug #834960 [src:libdaemon-generic-perl] libdaemon-generic-perl: FTBFS too much 
often (failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#797481: marked as done (fw4spl: FTBFS - Doesn't support boost 1.58)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 21:41:10 +
with message-id 
and subject line Bug#838061: Removed package(s) from unstable
has caused the Debian Bug report #797481,
regarding fw4spl: FTBFS - Doesn't support boost 1.58
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.)


-- 
797481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fw4spl
Version: 0.9.2-3
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

fw4spl FTBFS with:
/tmp/buildd/fw4spl-0.9.2/SrcLib/core/fwDataIO/src/fwDataIO/reader/TriangularMeshReader.cpp:15:60:
 fatal error: boost/spirit/home/phoenix/statement/sequence.hpp: No such file or 
directory

This file exists in boost 1.55 but not in boost 1.58 which is the
default in unstable.

Please note that you have to disable parallel build to reproduce this
bug [1].

[1] 

Full build log on request.

Thanks,

_g.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJV44xlAAoJEO/obGx//s+DJM8H/2+287kKBkEMMPi8KI+U13cE
9wpiMagwTK4mX6y4wX1FEYKokAbZHaAw7SAWSAOpe0r9vDwJqiXAf913IwotH/7z
6SZrFrMnZdaZt85mZl8R9zjFheaOJ2m/VX9glk8fnOK6+52IO6sgo9D9G50sMmB2
zWzgWNBFswXMZAY/s1y2gEyfUXodqpTYxgYEO+FgkmpLDErCFHErT8pSa5ZNZv1R
H3JkoXuFHD8Qp5wND3ZjpUpJmrPH9NQyYmWYv6QSICvA5R7RLsQD9xtOJ0sCCAaf
icMGCBcgRviQWBNJyKPa36774f3m5NbByX3xVEvOXEQriqwD571GvRg9IQEQ64s=
=RvHZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.9.2-3+rm

Dear submitter,

as the package fw4spl 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/838061

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#821957: marked as done (fw4spl: Depends on insighttoolkit, which is about to be removed. Please port to insighttoolkit4)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 21:41:10 +
with message-id 
and subject line Bug#838061: Removed package(s) from unstable
has caused the Debian Bug report #821957,
regarding fw4spl: Depends on insighttoolkit, which is about to be removed. 
Please port to insighttoolkit4
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.)


-- 
821957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fw4spl
Severity: serious
Justification: Depends on to-be-removed packages
Control: block 795019 by -1

Another RC bug for fw4spl...
The title says it already: insighttoolkit is supposed to be removed, and this 
package
is blocking the removal (same as for e.g. vtk5)

--
tobi


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.9.2-3+rm

Dear submitter,

as the package fw4spl 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/838061

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#822118: marked as done (RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 21:41:10 +
with message-id 
and subject line Bug#838061: Removed package(s) from unstable
has caused the Debian Bug report #822118,
regarding RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of 
old packages
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.)


-- 
822118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fw4spl
Severity: serious
Justification: blocks-transitions

Dear maintainer / ftp-masters,

fw4spl is RC buggy with 5 bugs:
 #797475 fw4spl: does not support parallel build
 #797481 fw4spl: FTBFS - Doesn't support boost 1.58
 #809935 fw4spl: FTBFS with libpng16
 #820632 fw4spl: depends on vtk 5
 #821957 fw4spl: Depends on insighttoolkit, which is about to be removed. 
Please port to insighttoolkit4

With the first two filed August 2015; both of them did not receive any response 
from the maintainer, though
extra triggered again by Andreas in December.

(The other two bugs do not ahve a response too, but they are only a few days 
old)

The package blocks the boost, libpng and vtk transitions.

As it is now blocking other packages, I raise the question if it should be
removed from Debian.

Please response to this bug, if there is no response within a week, I will
reassign this bug to ftp.debian.org.

Please note, that if decide to keep it, you need to fix your pacakge ASAP.
The removal of libpng1.2 will NOT wait for root-system, and when removed,
at least the binary packages must go with it. (Which can lead to src removal)

Thanks for your understanding,

-- 
tobi



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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.9.2-3+rm

Dear submitter,

as the package fw4spl 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/838061

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#809935: marked as done (fw4spl: FTBFS with libpng16)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 21:41:10 +
with message-id 
and subject line Bug#838061: Removed package(s) from unstable
has caused the Debian Bug report #809935,
regarding fw4spl: FTBFS with libpng16
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.)


-- 
809935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fw4spl
Severity: important
User: lib...@packages.debian.org
Usertags: libpng16-transition

Dear fw4spl maintainer,

Currently we are preparing the transistion of libpng1.2 to libpng1.6.
The transistion bug is #650601.

A rebuilt of all packages depending on libpng-dev and libpng12-dev
has been done. The result with buildlogs can be found here:
https://libpng.sviech.de/

fw4spl FTBFS during this rebuild. The buildlog is available at
https://libpng.sviech.de/fw4spl.build

The Titanpad at https://titanpad.com/libpng16-transistion might give
you clues about what went wrong as well as some recipes/pointers how
to fix them. Please feel free to amend the information on the pad as
you might see fit. A plain-text, non java-script version is here:
https://titanpad.com/ep/pad/export/libpng16-transistion/latest 

Please try to make fw4spl compatible with libpng16 and then make sure
to B-D on libpng-dev only, if the fix makes it possible to compile it
against libdev12 and libdev16. If you can only make in a non-backward
compatible way, please B-D on libpng16-dev. 

This bug will become RC as soon as the transistion starts.

Best regards, 
-- 
tobi
--- End Message ---
--- Begin Message ---
Version: 0.9.2-3+rm

Dear submitter,

as the package fw4spl 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/838061

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#797475: marked as done (fw4spl: does not support parallel build)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 21:41:10 +
with message-id 
and subject line Bug#838061: Removed package(s) from unstable
has caused the Debian Bug report #797475,
regarding fw4spl: does not support parallel build
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.)


-- 
797475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fw4spl
Version: 0.9.2-3
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

It seems fw4spl doesn't support parallel build. When using
DEB_BUILD_OPTIONS="parallel=6" it fails repeatedly with:

Generating moc_CppHighlighter.cpp
Generating moc_PythonHighlighter.cpp
Generating moc_FrameLayoutManager.cpp
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
"BOOST_JOIN"
Generating moc_DumpEditor.cpp
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
"BOOST_JOIN"
Scanning dependencies of target ioVtkGdcm_rc
monitorQt/CMakeFiles/monitorQt_automoc.dir/build.make:52: recipe for target 
'monitorQt/CMakeFiles/monitorQt_automoc' failed
make[3]: Leaving directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:2535: recipe for target 
'monitorQt/CMakeFiles/monitorQt_automoc.dir/all' failed
make[3]: Leaving directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
make -f ioVtkGdcm/CMakeFiles/ioVtkGdcm_rc.dir/build.make 
ioVtkGdcm/CMakeFiles/ioVtkGdcm_rc.dir/build
make[3]: Entering directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_report 
/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/CMakeFiles 
[  4%] Generating ../Bundles/ioVtkGdcm_0-1/plugin.xml
cd /tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/ioVtkGdcm && cmake 
-DIN_FILE="/tmp/buildd/fw4spl-0.9.2/Bundles/LeafIO/ioVtkGdcm/rc/plugin.xml" 
-DOUT_FILE="/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/Bundles/ioVtkGdcm_0-1/plugin.xml"
 -DFWPROJECT_NAME="ioVtkGdcm" -DDASH_VERSION="0-1" -DPROJECT_VERSION="0.1" 
-DTARGET_TYPE="SHARED_LIBRARY" -P 
/tmp/buildd/fw4spl-0.9.2/CMake//build/configure_file.cmake
make[3]: Leaving directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_report 
/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/CMakeFiles 
[  4%] Built target ioVtkGdcm_rc
Generating moc_FuncSlot.cpp
Generating moc_QRangeSlider.cpp
Generating moc_QfwToolbox.cpp
fwGuiQt/CMakeFiles/fwGuiQt_automoc.dir/build.make:52: recipe for target 
'fwGuiQt/CMakeFiles/fwGuiQt_automoc' failed
make[3]: Leaving directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:1743: recipe for target 
'fwGuiQt/CMakeFiles/fwGuiQt_automoc.dir/all' failed
Generating moc_DynamicView.cpp
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
"BOOST_JOIN"
guiQt/CMakeFiles/guiQt_automoc.dir/build.make:52: recipe for target 
'guiQt/CMakeFiles/guiQt_automoc' failed
make[3]: Leaving directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:2197: recipe for target 
'guiQt/CMakeFiles/guiQt_automoc.dir/all' failed
Linking CXX shared library ../lib/fw4spl/libfwCore.so
cd /tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/fwCore && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/fwCore.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2  -O3 -DNDEBUG  -fPIE -pie 
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -shared -Wl,-soname,libfwCore.so.0 -o 
../lib/fw4spl/libfwCore.so.0.1 
CMakeFiles/fwCore.dir/src/fwCore/HiResClock.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/log/SpyLogger.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/log/ScopedMessage.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/LogicStamp.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/Demangler.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/Exception.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/HiResTimer.cpp.o 
CMakeFiles/fwCore.dir/src/fwCore/TimeStamp.cpp.o -lboost_regex 
-lboost_filesystem -lboost_date_time -lboost_chrono -lboost_log 
-lboost_log_setup -lboost_thread -lboost_system -lpthread 
-Wl,-rpath,::: 
cd /tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/fwCore && /usr/bin/cmake -E 
cmake_symlink_library ../lib/fw4spl/libfwCore.so.0.1 
../lib/fw4spl/libfwCore.so.0 ../lib/fw4spl/libfwCore.so
make[3]: Leaving directory '/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_report 
/tmp/buildd/fw4spl-0.9.2/obj-x86_64-linux-gnu/CMakeFiles  22
[  4%] Built target fwCore
make[2]: Leaving 

Bug#820632: marked as done (fw4spl: depends on vtk 5)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 21:41:10 +
with message-id 
and subject line Bug#838061: Removed package(s) from unstable
has caused the Debian Bug report #820632,
regarding fw4spl: depends on vtk 5
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.)


-- 
820632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fw4spl
Version: 0.9.2-3
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 798164 with -1

Dear Maintainer,

Your package depends on vtk 5.x, which should not be in stretch.
Please switch to vtk 6.x or drop the dependency.

More specifically, your package depends on libvtk5.8 which is keeping the
old netcdf (4.1.3-7.2) packages in unstable. Since vtk (5.10.1+dfsg-2.1)
is in unstable, you should at least rebuild with that to get rid of the
dependency on libvtk5.8.

Removing fw4spl from the archive via #817939 will solve all these
problems.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Version: 0.9.2-3+rm

Dear submitter,

as the package fw4spl 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/838061

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.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Processed: tagging 834960

[Debian Bug Tracking System]

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

> tags 834960 - unreproducible
Bug #834960 [src:libdaemon-generic-perl] libdaemon-generic-perl: FTBFS too much 
often (failing tests)
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#837192:

[Joseph Herlant]

Hi,

This bug is fixed with the latest version currently on the review
process in Mentors:
https://mentors.debian.net/package/gnome-shell-pomodoro
It will be uploaded when validated by my mentor.

If you feel like double checking the new package, every constructive
comment is welcome! :-)

Thanks,
Joseph

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Hilmar Preusse]

On 05.09.16 Matthias Klose (d...@debian.org) wrote:

Hi Matthias,

> This package builds using the hardening-includes package, which
> is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.
> 
> Please consider dropping the build dependency of hardening-includes
> and use the DEB_BUILD_MAINT_OPTIONS settings.
> 
Currently hardening is implemented like this:

./configure $(shell dpkg-buildflags --export=configure) (...)

..according to [1]. The only place where we use hardening-includes is
that line:

find $(CURDIR)/debian/tmp -type f \( -executable -o -name \*.so\* \) -exec 
hardening-check {} + || true

Is it OK to simply remove that check? Is there an replacement for
hardening-check?

Thanks,
  Hilmar

[1] 
https://wiki.debian.org/HardeningWalkthrough#rules_files_based_on_standard_debhelper_or_hand-written_rules_files
-- 
sigfault


signature.asc
Description: Digital signature

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[Niko Tyni]

On Sat, Sep 17, 2016 at 07:20:09PM +0200, gregor herrmann wrote:

> CPAN RT has one issue; don't know if it's related:
> https://rt.cpan.org/Public/Bug/Display.html?id=110239

I think it's a different issue.

> From starting at t/daemon.t my guess is that we're seeing a race
> condition or some other timing issue here -- the daemon writes to a
> log file and the test reads the logfile, and in one case the log
> message doesn't seem to be there (yet?). At least that's my current
> guess.

Indeed, the daemon first opens the file for writing and only then writes
it (see the logger script at top of daemon.t), while the test waits for
existence (-e) and then proceeds to check the file contents.

I think the attached patch should fix it. I was able to reproduce
the issue sporadically without the patch, and couldn't get it to
happen after applying this.

> I'm tempted to mark this log-reading test as TODO since this seems a
> bit fragile.

No objections, but let's try the patch first?
-- 
Niko
>From 96209b5ba3df009a495da31bee8e2540c3365ec5 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sat, 17 Sep 2016 21:16:16 +0300
Subject: [PATCH] Fix a race condition in the test suite waiting for daemon log
 output

There's a window where the daemon has created a log file but not yet
written anything into it. Wait for the file to become nonempty before
reading it to make sure we're past that window.

Bug-Debian: https://bugs.debian.org/834960
---
 t/daemon.t | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/daemon.t b/t/daemon.t
index 30763df..548af21 100644
--- a/t/daemon.t
+++ b/t/daemon.t
@@ -200,7 +200,7 @@ sub do_test
 	chomp($counter1);
 	like($counter1, qr/^\d+$/, "counter1 - $name");
 
-	expect { -e "$tmp/log" };
+	expect { -s "$tmp/log" };
 	like(read_file("$tmp/log"), qr/START LOG/, "logged output");
 
 	expect { my @l = read_file("$tmp/log"); @l > 1 };
-- 
2.9.3

Bug#835992: marked as done (spl-dkms: Fails to build against kernel package 4.7.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 18:28:46 +
with message-id 
and subject line Bug#835992: fixed in spl-linux 0.6.5.8-1
has caused the Debian Bug report #835992,
regarding spl-dkms: Fails to build against kernel package 4.7.0-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.)


-- 
835992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spl-dkms
Version: 0.6.5.7-1
Severity: important
Tags: upstream

Dear Maintainer,

due to changes in the Inode structure this version does not supprt kernel 4.7 
and newer.
There is an upstream patch to handle kernel 4.7(at least from the description):
https://github.com/zfsonlinux/spl/commit/fdbc1ba99d1f4d3958189079eee9b6c957e0264b

Regards

Achim

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages spl-dkms depends on:
ii  dkms  2.2.1.0+git20160527-1
ii  file  1:5.28-4
ii  libc6-dev [libc-dev]  2.23-5
ii  lsb-release   9.20160629

Versions of packages spl-dkms recommends:
ii  spl  0.6.5.7-1

spl-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: spl-linux
Source-Version: 0.6.5.8-1

We believe that the bug you reported is fixed in the latest version of
spl-linux, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated spl-linux 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, 18 Sep 2016 01:06:04 +0800
Source: spl-linux
Binary: spl-dkms spl
Architecture: source amd64 all
Version: 0.6.5.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers 

Changed-By: Aron Xu 
Description:
 spl- Solaris Porting Layer user-space utilities for Linux
 spl-dkms   - Solaris Porting Layer kernel modules for Linux
Closes: 835992 836578
Changes:
 spl-linux (0.6.5.8-1) unstable; urgency=medium
 .
   [ Petter Reinholdtsen ]
   * Fix invalid command in dkms (Closes: #836578)
 .
   [ Zhou Mo ]
   * control: bump standards version to 3.9.8
 .
   [ Aron Xu ]
   * Imported Upstream version 0.6.5.8 (Closes: #835992)
   * rules: allow parallel building
Checksums-Sha1:
 fea30e140ab50a0a8dc13232c3c5a6bb8cb36e29 1798 spl-linux_0.6.5.8-1.dsc
 903c28d258b269138842946fa675d47bdce2fdba 553270 spl-linux_0.6.5.8.orig.tar.gz
 6fdb915ad1945699ffac396f678d5774e70bba4a 8340 spl-linux_0.6.5.8-1.debian.tar.xz
 8165feb2251f58eb2256e9a0bbfde51d9841b0d3 21896 spl-dbgsym_0.6.5.8-1_amd64.deb
 f6e0bf91d75a1fee2c0ac1817279d43cbfb9e8d2 350128 spl-dkms_0.6.5.8-1_all.deb
 e1341721dde8a5020f1912535c629d57a22a3573 13000 spl_0.6.5.8-1_amd64.deb
Checksums-Sha256:
 208a1527ba1bd1d75b82928ba53793b77bfed799e2fcfe0a3a5197c941ccc46a 1798 
spl-linux_0.6.5.8-1.dsc
 2d2211710678d2b7da88cc657b7b9c44d281b1cc74d60761e52d33ab1155 553270 
spl-linux_0.6.5.8.orig.tar.gz
 1d6b44ffe7e28eb7a7823c31e83c14b0e4f45b3d5eaa39be079fcf0ef93e8a71 8340 
spl-linux_0.6.5.8-1.debian.tar.xz
 eca643419773f7fc6ff3e116577362f3c2f8df908cc021cd1bb723c156ffc5d8 21896 
spl-dbgsym_0.6.5.8-1_amd64.deb
 c9b9b717063952d85f01184cba9f8150c80c6a1ebd77eddc443c269db21bc34d 350128 
spl-dkms_0.6.5.8-1_all.deb
 3681390646c4a91784fccfecdf48560f5d855b9dd97993db290d11625537f60b 13000 
spl_0.6.5.8-1_amd64.deb
Files:
 63bed57120dc8c59e4f0226770a00cf2 1798 kernel optional spl-linux_0.6.5.8-1.dsc
 54b049cde051d0bd67f3f18ff58113c2 553270 kernel optional 
spl-linux_0.6.5.8.orig.tar.gz
 35613f5bd9ae226cd1fe83d29d9ab6e2 8340 kernel optional 
spl-linux_0.6.5.8-1.debian.tar.xz
 

Processed: owfs-common: missing Breaks: libow-2.8-15

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + owhttpd owftpd owfs-fuse owserver libow-dev libow-perl 
> libow-php5 libow-tcl owfs-dbg python-ow
Bug #838144 [owfs-common] owfs-common: missing Breaks: libow-2.8-15
Added indication that 838144 affects owhttpd, owftpd, owfs-fuse, owserver, 
libow-dev, libow-perl, libow-php5, libow-tcl, owfs-dbg, and python-ow

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

Bug#838144: owfs-common: missing Breaks: libow-2.8-15

[Andreas Beckmann]

Package: owfs-common
Version: 3.1p1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + owhttpd owftpd owfs-fuse owserver libow-dev libow-perl 
libow-php5 libow-tcl owfs-dbg python-ow

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch'.
After this upgrade a conffile has disappeared from a package, but that
(obsolete) package is still installed:

2m42.6s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/modprobe.d/libow-2.8-15.conf (from 
libow-2.8-15:amd64 package)

Since owfs-common "takes over" that conffile (to make it disappear),
it needs to break the packages that had shipped it in the past.

That problem already exists in stable (after the wheezy->jessie upgrade)
but we had ignored that error there so far.


Andreas


owhttpd_3.1p1-6.log.gz
Description: application/gzip

Processed: emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + oneliner-el
Bug #838143 [emacs24] emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1)
Added indication that 838143 affects oneliner-el

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

Bug#838143: emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1)

[Andreas Beckmann]

Package: emacs24
Version: 24.5+1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + oneliner-el

Hi,

during a test with piuparts I noticed that emacs24 is not compatible
with oneliner-el (that may have been left over from a long grown
wheezy installation. Please add an appropriate Breaks against it to
ensure it gets removed (or upgraded in case the package would get
updated at some pooint again) on upgrades to emacs24 in stretch.

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

  Setting up emacs24 (24.5+1-7) ...
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install oneliner-el for emacs24
  install/oneliner-el: Handling install for emacsen flavor emacs24
  Loading 00debian-vars...
  Loading /etc/emacs/site-start.d/20apel.el (source)...
  Loading /etc/emacs/site-start.d/50oneliner-el.el (source)...
  Loading /etc/emacs/site-start.d/51oneliner-el.el (source)...
  Error while loading 51oneliner-el: Cannot open load file: No such file or 
directory, poe
  
  In toplevel form:
  oneliner.el:225:1:Error: Cannot open load file: No such file or directory, poe
  ERROR: install script from oneliner-el package failed
  dpkg: error processing package emacs24 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up apel (10.8+0.20120427-15) ...
  Install emacsen-common for emacs23
  emacsen-common: Handling install of emacsen flavor emacs23
  Wrote /etc/emacs23/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs23/site-lisp/debian-startup.elc
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install apel for emacs23
  install/apel: byte-compiling for emacs23, logged in /tmp/elc.FITqQNEcTtCb
  install/apel: deleting /tmp/elc.FITqQNEcTtCb
  install/apel: byte-compiling for reverse dependency
  Install apel for emacs24
  install/apel: byte-compiling for emacs24, logged in /tmp/elc.v8FtAKxmFrHB
  install/apel: deleting /tmp/elc.v8FtAKxmFrHB
  install/apel: byte-compiling for reverse dependency


Andreas


oneliner-el_None.log.gz
Description: application/gzip

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[gregor herrmann]

On Sun, 21 Aug 2016 02:21:52 +0200, gregor herrmann wrote:

> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > (which is what the "Arch: all" autobuilder would do to build it)
> > but it failed:
> Builds fine for me (amd64 sind cowbuilder).

Some additional information:
cpantesters have very few failures, but they are all the same as what
we see in Santiago#s logs:
http://www.cpantesters.org/cpan/report/8fb11c8e-0653-11e6-a2e4-45f0fcd2507e
http://www.cpantesters.org/cpan/report/9c628bfa-2171-11e6-8c16-9a987137e9a4
http://www.cpantesters.org/cpan/report/66c774ca-7a7b-11e6-979d-6531eb7e2f12
http://www.cpantesters.org/cpan/report/a8b80e96-3132-11e5-8118-e820f1b6abcd

CPAN RT has one issue; don't know if it's related:
https://rt.cpan.org/Public/Bug/Display.html?id=110239


Personally I still can't reproduce the bug.

From starting at t/daemon.t my guess is that we're seeing a race
condition or some other timing issue here -- the daemon writes to a
log file and the test reads the logfile, and in one case the log
message doesn't seem to be there (yet?). At least that's my current
guess.

I'm tempted to mark this log-reading test as TODO since this seems a
bit fragile.


Thoughts?


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Pogues: Lullaby Of London


signature.asc
Description: Digital Signature

Bug#833965: tcsh: uses deprecated BSD union wait type

[Sascha Steinbiss]

Hi,

just a friendly ping whether this is still on anyone’s radar. I assume that 
#837026 [1]
is a direct consequence of this issue?

Cheers
Sascha

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837026

On Thu, 1 Sep 2016 13:02:17 +0200 Thomas Lange  
wrote:
> > On Thu, 1 Sep 2016 12:51:30 +0200, Aurelien Jarno  
> > said:
> 
> > bug to serious. If you don't have time to fix this bug, I can do a
> > non-maintainer upload with the patch which is in the bug log.
> Salut Aurelien,
> 
> feel free to do a NMU.
> 
> -- 
> regards Thomas
> 
> 

Processed: affects 765120, affects 811306, user debian...@lists.debian.org, usertagging 811306 ...

[Debian Bug Tracking System]

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

> affects 765120 + libmonogame-cil
Bug #765120 [src:monogame] monogame: support monodevelop 5
Added indication that 765120 affects libmonogame-cil
> affects 811306 + mmpong-gl
Bug #811306 [mmpong] FTBFS: mmpong-gl-data missing files: 
usr/share/games/mmpong-gl
Added indication that 811306 affects mmpong-gl
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 811306 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 765120 piuparts
Usertags were: qa-ftbfs-20141012 piuparts qa-ftbfs.
Usertags are now: qa-ftbfs-20141012 piuparts qa-ftbfs.
> thanks
Stopping processing here.

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

Bug#837759: network configuration stops working reliably

[Felipe Sateler]

On 15 September 2016 at 12:36, Felipe Sateler  wrote:
> On 14 September 2016 at 18:34, Wolfgang Walter  
> wrote:
>> On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote:
>>> Control: tags -1 moreinfo
>>>
>>> On 14 September 2016 at 06:59, Wolfgang Walter  
>>> wrote:
>>> > Package: systemd
>>> > Version: 231-6
>>> > Severity: grave
>>> >
>>> > Starting with version 231-6 the configuration of network interfaces stops
>>> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
>>> > problem.
>>> >
>>> > Symptoms: If a network interface is configured using
>>> > /etc/network/interfaces it seems that systemd now sometimes removes the
>>> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
>>> > to remove routes of network interfaces configured manually or with
>>> > /etc/network/interfaces if the link state changes.
>>> >
>>> > This seems not only be the case with interfaces configured via
>>> > /etc/network/ interfaces but with any interface one creates and assigns
>>> > ip addresses manually.
>>> >
>>> > I tested this with a script:
>>> >
>>> > #!/bin/sh
>>> > if [ "$1" = start ]; then
>>> > ip link del TEST >/dev/null 2>&1 || true
>>> > ip link add name TEST type dummy
>>> > ip -b - <<"EOF"
>>> > link set TEST up
>>> > addr add 10.10.10.10/32 dev TEST nodad
>>> > addr add 2a01:1:1:1::1/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::2/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::3/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::4/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::5/128 dev TEST nodad
>>> > EOF
>>> > ip addr ls TEST
>>> > sleep 2
>>> > elif [ "$1" = stop ]; then
>>> > ip addr flush dev TEST
>>> > ip link del TEST
>>> > fi
>>> >
>>> > which I start with as a systemd oneshot service with
>>> >
>>> > Before=systemd-networkd.service
>>> >
>>> > I can see in the journal that TEST has all adresses assigned but with
>>> > 231-6 it looses them again (probably when systemd-networkd.service
>>> > starts). With 231-5 or earlier this in not the case.
>>>
>>> It appears you are using systemd-networkd. Could you please attach
>>> your networkd configuration?
>>>
>>> Version 231-6 is built with iptables support, so that may be causing
>>> an interaction that was not visible before.
>>
>> I think this is the problem:
>>
>> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=debian/231-6=79e10aaee1cdd412bd42f13f26e558ba1cd2196b
>>
>> I suppose is that the check for LINK_STATE_UNMANAGED may be racy.
>> The interface may go down and up before LINK_STATE_UNMANAGED is set.
>> Maybe the state is LINK_STATE_PENDING ?
>
> Interesting. Did you test with that patch disabled? (sorry, I have not
> had time to test).

BTW, I have tested manually on my system during runtime and cannot
reproduce. If this is a race maybe my laptop while idle managed to
configure faster than networkd managed to react.

-- 

Saludos,
Felipe Sateler

Processed: Re: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.14.6+dfsg-3
Bug #836993 {Done: Bas Couwenberg } [qgis] qgis: fails to 
upgrade from 'jessie': dpkg-divert: error: rename involves overwriting 
`/usr/bin/qgis'
Marked as found in versions qgis/2.14.6+dfsg-3; no longer marked as fixed in 
versions qgis/2.14.6+dfsg-3 and reopened.

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

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Andreas Beckmann]

Followup-For: Bug #836993
Control: found -1 2.14.6+dfsg-3

Hi,

still not completely resolved, I'll try to find some time to look there
myself.

  Preparing to unpack .../qgis_2.14.6+dfsg-3_amd64.deb ...
  Unpacking qgis (2.14.6+dfsg-3) over (2.4.0-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/qgis_2.14.6+dfsg-3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/qbrowser.bin', which is the diverted version 
of '/usr/bin/qbrowser' (package: qgis-plugin-grass)
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Processing triggers for libc-bin (2.24-2) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/qgis_2.14.6+dfsg-3_amd64.deb


Andreas

Bug#836930: marked as done (mssstest: FTBFS with GCC 6: error: reference to 'rank' is ambiguous)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 16:35:14 +
with message-id 
and subject line Bug#836930: fixed in mssstest 3.0-5
has caused the Debian Bug report #836930,
regarding mssstest: FTBFS with GCC 6: error: reference to 'rank' is ambiguous
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.)


-- 
836930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mssstest
Version: 3.0-4
Severity: serious
Justification: fails to build from source

Hi,

mssstest FTBFS since the default compiler was switched to gcc-6:

 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/build/mssstest-3.0'
g++ -g -O2 -fdebug-prefix-map=/build/mssstest-3.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c neededroutines.cpp  -g -o neededroutines.o
neededroutines.cpp: In function 'float rankties(long unsigned int, float*, 
float*)':
neededroutines.cpp:172:3: error: reference to 'rank' is ambiguous
   rank(len, arr, intranks);
   ^~~~
neededroutines.cpp:138:6: note: candidates are: void rank(long unsigned int, 
float*, int*)
 void rank(unsigned long len, float arr[], int ranks[])
  ^~~~
In file included from /usr/include/c++/6/bits/move.h:57:0,
 from /usr/include/c++/6/bits/nested_exception.h:40,
 from /usr/include/c++/6/exception:171,
 from /usr/include/c++/6/ios:39,
 from /usr/include/c++/6/ostream:38,
 from /usr/include/c++/6/iostream:39,
 from neededroutines.h:1,
 from neededroutines.cpp:2:
/usr/include/c++/6/type_traits:1471:12: note: template 
struct std::rank
 struct rank
^~~~
makefile:10: recipe for target 'neededroutines.o' failed
make[1]: *** [neededroutines.o] Error 1
make[1]: Leaving directory '/build/mssstest-3.0'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Source: mssstest
Source-Version: 3.0-5

We believe that the bug you reported is fixed in the latest version of
mssstest, 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 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated mssstest 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: Sat, 17 Sep 2016 14:34:20 +
Source: mssstest
Binary: mssstest
Architecture: source amd64
Version: 3.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 mssstest   - Normalisation of disease scores for patients with Multiple Sclero
Closes: 836930
Changes:
 mssstest (3.0-5) unstable; urgency=medium
 .
   * Team upload.
   * Fix building with GCC 6.
 - Add missing qualifier.
 Closes: #836930
   * Bump Standards-Version.
   * Fix typo in README.Debian.
   * Add full hardening.
Checksums-Sha1:
 8f3f06f83ac013f2dc3ba22a57446b1237419409 1994 mssstest_3.0-5.dsc
 fef8223ca3a302c748bf61bec77554ded5944877 7264 mssstest_3.0-5.debian.tar.xz
 2b16ff24a1792060a8108fc7d2566451fe12aeff 43536 mssstest-dbgsym_3.0-5_amd64.deb
 0b066810f294469478bea7e354f1c3b396882c11 26130 mssstest_3.0-5_amd64.deb
Checksums-Sha256:
 d841839deb5638a6680a5c9789f5b4e2f5ec9f9db9226ca183101e6d8abc0d81 1994 
mssstest_3.0-5.dsc
 5973c24afd2a953f1fc81435aaf999f817315f88a451a7b14718e73ee07832f7 7264 
mssstest_3.0-5.debian.tar.xz
 e86b00ad3bb6ebc1a823001167877f807bf1c1349698dfbac5effca8b7ecda6b 43536 
mssstest-dbgsym_3.0-5_amd64.deb
 c61b7716641ce5a05d5e0fe4624aee6ed4142a8813c30b80252e912803c2e7af 26130 
mssstest_3.0-5_amd64.deb
Files:
 029299ee0823ffb650746218ef8e4402 1994 non-free/science optional 
mssstest_3.0-5.dsc
 1e658836eea15307f4e70fecb0208b0f 7264 non-free/science optional 
mssstest_3.0-5.debian.tar.xz
 aa6d132cbe627201f5e5ffc067941976 

Bug#836825: marked as done (ruby-sys-filesystem: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 16:37:56 +
with message-id 
and subject line Bug#836825: fixed in ruby-sys-filesystem 1.1.7-2
has caused the Debian Bug report #836825,
regarding ruby-sys-filesystem: FTBFS in testing (failing tests)
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.)


-- 
836825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-sys-filesystem
Version: 1.1.7-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

/<>/debian/ruby-sys-filesystem/usr/lib/ruby/vendor_ruby/sys/unix/sys/filesystem.rb:301:in
 `mounts'
/<>/test/test_sys_filesystem_unix.rb:22:in `setup'
===
: (0.000443)
  test_to_gb:   E
===
Error: test_to_gb(TC_Sys_Filesystem_Unix): Errno::ENOENT: No such file or 
directory - setmntent
/<>/debian/ruby-sys-filesystem/usr/lib/ruby/vendor_ruby/sys/unix/sys/filesystem.rb:301:in
 `mounts'
/<>/test/test_sys_filesystem_unix.rb:22:in `setup'
===
: (0.000468)
  test_to_kb:   E
===
Error: test_to_kb(TC_Sys_Filesystem_Unix): Errno::ENOENT: No such file or 
directory - setmntent
/<>/debian/ruby-sys-filesystem/usr/lib/ruby/vendor_ruby/sys/unix/sys/filesystem.rb:301:in
 `mounts'
/<>/test/test_sys_filesystem_unix.rb:22:in `setup'
===
: (0.000471)
  test_to_mb:   E
===
Error: test_to_mb(TC_Sys_Filesystem_Unix): Errno::ENOENT: No such file or 
directory - setmntent
/<>/debian/ruby-sys-filesystem/usr/lib/ruby/vendor_ruby/sys/unix/sys/filesystem.rb:301:in
 `mounts'
/<>/test/test_sys_filesystem_unix.rb:22:in `setup'
===
: (0.000455)
  test_version: E
===
Error: test_version(TC_Sys_Filesystem_Unix): Errno::ENOENT: No such file or 
directory - setmntent
/<>/debian/ruby-sys-filesystem/usr/lib/ruby/vendor_ruby/sys/unix/sys/filesystem.rb:301:in
 `mounts'
/<>/test/test_sys_filesystem_unix.rb:22:in `setup'
===
: (0.000448)

Finished in 0.028448514 seconds.
--
45 tests, 0 assertions, 0 failures, 45 errors, 0 pendings, 0 omissions, 0 
notifications
0% passed
--
1581.80 tests/s, 0.00 assertions/s
rake aborted!
Command failed with status (1): [ruby -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_sys_filesystem.rb" "test/test_sys_filesystem_unix.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-sys-filesystem 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Because the package is "Architecture: all", the failure does not seem
related to using "dpkg-buildpackage -A".

Once you fix this, please consider uploading the package in source-only
form, so that we have pretty official build logs available here:

https://buildd.debian.org/status/package.php?p=ruby-sys-filesystem

Thanks.
--- End 

Bug#838139: syslog-ng-mod-zmq: symbol lookup error with libzmq.so

[M. Dietrich]

Package: syslog-ng-mod-zmq
Version: 0.5.0-1
Severity: grave
Justification: renders package unusable

when using the plugin syslog-ng fails to start with

syslog-ng: symbol lookup error:
/usr/lib/syslog-ng/3.7/libzmq.so: undefined symbol:
init_sequence_number

a fix seems to be available at


https://github.com/balabit/syslog-ng-incubator/commit/ef62d1517041b7e3f6a0bcb4799351f0b24ac290

commit message sound familar:

the zmq destination need init_sequence_number. So we have
to include "misc.h".  Otherwise it crash when running.

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages syslog-ng-mod-zmq depends on:
ii  libc6 2.23-5
ii  libevtlog00.2.12-7
ii  libglib2.0-0  2.49.6-1
ii  libivykis00.36.2-1
ii  libzmq5   4.1.5-2
ii  syslog-ng-core [syslog-ng-abi-3.7-0]  3.7.3-1

syslog-ng-mod-zmq recommends no packages.

syslog-ng-mod-zmq suggests no packages.

-- no debconf information

Bug#815433: marked as done (libdata-messagepack-stream-perl: FTBFS with new msgpack-c library)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 16:33:39 +
with message-id 
and subject line Bug#815433: fixed in libdata-messagepack-stream-perl 1.01+ds-1
has caused the Debian Bug report #815433,
regarding libdata-messagepack-stream-perl: FTBFS with new msgpack-c library
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.)


-- 
815433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdata-messagepack-stream-perl
Version: 0.07-1
Severity: important
Tags: upstream patch

I have msgpack-c 1.4.0 staged in experimental, but this package FTBFS against
the new version of the library.  There were API changes to support the new
version of the msgpack spec.

I've submitted a patch series[0] for this upstream, but it will also require a 
new
libdata-messagepack-perl version (maintainer Cc'ed).

[0]: https://github.com/typester/Data-MessagePack-Stream/pull/6

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

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on freya.jamessan.com

+==+
| libdata-messagepack-stream-perl 0.07-1 (amd64) 17 Feb 2016 23:17 |
+==+

Package: libdata-messagepack-stream-perl
Version: 0.07-1
Source Version: 0.07-1
Distribution: experimental
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64

I: NOTICE: Log filtering will replace 
'build/libdata-messagepack-stream-perl-faQtqY/libdata-messagepack-stream-perl-0.07'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/libdata-messagepack-stream-perl-faQtqY' with '<>'
I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/experimental-amd64-sbuild-a4fde6bf-a2c2-436d-b4f0-e0c4c8bba598'
 with '<>'

+--+
| Update chroot|
+--+

Get:1 http://httpredir.debian.org/debian sid InRelease [287 kB]
Get:2 http://httpredir.debian.org/debian experimental InRelease [188 kB]
Get:3 http://httpredir.debian.org/debian sid/main Sources.diff/Index [27.9 kB]
Get:4 http://httpredir.debian.org/debian sid/main amd64 Packages.diff/Index 
[27.9 kB]
Get:5 http://httpredir.debian.org/debian sid/main Translation-en.diff/Index 
[27.9 kB]
Get:6 http://httpredir.debian.org/debian experimental/main Sources [385 kB]
Get:7 http://httpredir.debian.org/debian experimental/main amd64 Packages [645 
kB]
Get:8 http://httpredir.debian.org/debian experimental/main Translation-en [293 
kB]
Get:9 http://httpredir.debian.org/debian sid/main Sources 
2016-02-14-2058.10.pdiff [21.3 kB]
Get:10 http://httpredir.debian.org/debian sid/main Sources 
2016-02-15-0254.36.pdiff [6508 B]
Get:11 http://httpredir.debian.org/debian sid/main Sources 
2016-02-15-0853.29.pdiff [8618 B]
Get:12 http://httpredir.debian.org/debian sid/main Sources 
2016-02-15-1453.17.pdiff [20.2 kB]
Get:13 http://httpredir.debian.org/debian sid/main Sources 
2016-02-15-2054.35.pdiff [30.2 kB]
Get:14 http://httpredir.debian.org/debian sid/main Sources 
2016-02-16-0257.09.pdiff [14.1 kB]
Get:15 http://httpredir.debian.org/debian sid/main Sources 
2016-02-16-0851.51.pdiff [3512 B]
Get:16 http://httpredir.debian.org/debian sid/main Sources 
2016-02-16-1528.20.pdiff [14.9 kB]
Get:17 http://httpredir.debian.org/debian sid/main Sources 
2016-02-16-2054.53.pdiff [4035 B]
Get:18 http://httpredir.debian.org/debian sid/main Sources 
2016-02-17-0255.42.pdiff [28.6 kB]
Get:19 http://httpredir.debian.org/debian sid/main Sources 
2016-02-17-0853.45.pdiff [2638 B]
Get:20 http://httpredir.debian.org/debian sid/main Sources 
2016-02-17-1453.17.pdiff [18.8 kB]
Get:21 http://httpredir.debian.org/debian sid/main Sources 
2016-02-17-2054.23.pdiff [40.6 kB]
Get:22 http://httpredir.debian.org/debian sid/main Sources 
2016-02-18-0256.55.pdiff [18.4 kB]
Get:23 http://httpredir.debian.org/debian sid/main amd64 Packages 
2016-02-14-2058.10.pdiff [25.1 kB]
Get:24 http://httpredir.debian.org/debian sid/main amd64 Packages 

Bug#834170: marked as done (arb: FTBFS with GCC 6)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 16:21:37 +
with message-id 
and subject line Bug#834170: fixed in arb 6.0.3-2
has caused the Debian Bug report #834170,
regarding arb: FTBFS with GCC 6
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.)


-- 
834170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arb
Version: 6.0.3-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch.

Seems like a C++ problem with GCC 6.
The full build log is attached.

BTW: Before GCC 6, this package used to build ok with
"dpkg-buildpackage -A". Please consider uploading in source only form.
That way we will see pretty build logs for "amd64" and "all" here:

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

Thanks.

arb_6.0.3-1_amd64-20160812-1235.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: arb
Source-Version: 6.0.3-2

We believe that the bug you reported is fixed in the latest version of
arb, 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 834...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated arb 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: Sat, 17 Sep 2016 10:34:18 +
Source: arb
Binary: arb libarb libarb-dev arb-common arb-doc
Architecture: source all amd64
Version: 6.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 arb- phylogenetic sequence analysis suite - main program
 arb-common - phylogenetic sequence analysis suite - common files
 arb-doc- phylogenetic sequence analysis suite - documentation
 libarb - phylogenetic sequence analysis suite - libraries
 libarb-dev - phylogenetic sequence analysis suite - development files
Closes: 834170
Changes:
 arb (6.0.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix building with GCC 6.
 - Use correct return type in method definition.
 - Allow for newer __cplusplus versions.
 Closes: #834170
   * Use secure Vcs-Browser.
   * Do not depend on perl-modules.
   * Bump Standards-Version.
Checksums-Sha1:
 e1be0ad8154efcb3c8dfa8f44b12c85a3ad9ce6f 2556 arb_6.0.3-2.dsc
 e3da7b2d92d3a153a4d2750ee38bde577adce330 123828 arb_6.0.3-2.debian.tar.xz
 3682b96fbd13988cb28f5d513e18a4434e148399 3499846 arb-common_6.0.3-2_all.deb
 17033e7a4852d94bb6664c2a57a172832b4f781b 16740672 arb-dbgsym_6.0.3-2_amd64.deb
 2f9ed7add36fcbe3e6e8e4ef832f7c9931e4587b 275564 arb-doc_6.0.3-2_all.deb
 4406038f340adf886c45a11fbdca29a349a9057c 1983630 arb_6.0.3-2_amd64.deb
 a463f84597e24c66dd190e18ab2cd081b8a143ba 3499490 
libarb-dbgsym_6.0.3-2_amd64.deb
 8c3d14fa26f720cf77096aa56f903c2cbf0a4fbe 412788 libarb-dev_6.0.3-2_amd64.deb
 8eb893a612998fedba404ab900979530c5ea3d2b 576416 libarb_6.0.3-2_amd64.deb
Checksums-Sha256:
 4626ec81d44f14cfa32de9cb7a5edb77dff7a4ea06b2c8dfdb7c57dcb124a67a 2556 
arb_6.0.3-2.dsc
 19abf6058e51b26df448b432298428bb68f222b3558e139350272d50a69ef1c1 123828 
arb_6.0.3-2.debian.tar.xz
 6c3606b570cbb28c7994567ec39867787f728da4c322db28347dac0360b09c5a 3499846 
arb-common_6.0.3-2_all.deb
 b8a72c607deb43bb37b2d012b36caf75be68c9779a2438775c684f4d559bfec5 16740672 
arb-dbgsym_6.0.3-2_amd64.deb
 7d7410cbf9c772aaffdb45e3b297560f1f25f3e9c027d4f99c4936abf376b956 275564 
arb-doc_6.0.3-2_all.deb
 138e234d3c8b3dad6d6eb31c559355e1a4382c9d1553ded61d5e9924d15cf1d0 1983630 
arb_6.0.3-2_amd64.deb
 bcc143fc129cecebcf7bd1d00d124dbf7d97b8de092b75c5c4e27c67d9b348bc 3499490 
libarb-dbgsym_6.0.3-2_amd64.deb
 0c4448918e015d71d1777042268a633fb60461eeeac712c9fdf2fdcdc8babd5e 412788 
libarb-dev_6.0.3-2_amd64.deb
 73c2c33a735a2487f661dc3253b1f7f530b31d872a9be00505a72435509e8595 576416 
libarb_6.0.3-2_amd64.deb
Files:
 ee12d4d1664686ba825b13ff42bd1a9b 2556 non-free/science optional arb_6.0.3-2.dsc
 682d8c5da4fe5249de9dab0f6c648864 123828 non-free/science optional 
arb_6.0.3-2.debian.tar.xz
 

Bug#838137: critterding: FTBFS in experimental: be_command_system.cpp:13:94: error: '_1' was not declared in this scope

[Andreas Beckmann]

Source: critterding
Version: 1.0-beta14+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

critterding/experimental FTBFS, probably due to the default compiler now being 
GCC 6:

[ 34%] Building CXX object 
src/common/CMakeFiles/common.dir/be_command_system.cpp.o
cd /build/critterding-1.0-beta14+dfsg/obj-x86_64-linux-gnu/src/common && 
/usr/bin/c++   -DBOOST_FILESYSTEM_VERSION=3 -DGLEW_STATIC -DHAVE_OPENMP=1 
-DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_
OPENGL_LIB -DUNIX -I/usr/include/bullet -I/usr/include/SDL -isystem 
/usr/include/qt4 -isystem /usr/include/qt4/QtOpenGL -isystem 
/usr/include/qt4/QtDeclarative -isystem /usr/include/qt4/QtGui -isystem 
/usr/include/
qt4/QtCore -I/build/critterding-1.0-beta14+dfsg -I/usr/include/freetype2 
-I/build/critterding-1.0-beta14+dfsg/. 
-I/build/critterding-1.0-beta14+dfsg/src/. 
-I/build/critterding-1.0-beta14+dfsg/src/common/.  -g -O2 -
fdebug-prefix-map=/build/critterding-1.0-beta14+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c++0x 
-Wl,-Bstatic -fopenmp -o CMakeFiles/common.dir/be_comma
nd_system.cpp.o -c 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp

/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp: In 
constructor 'BeCommandSystem::BeCommandSystem()':
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp:13:94: 
error: '_1' was not declared in this scope
  registerStringCommand("settings_saveprofile", 
boost::bind(::saveProfile, settings, _1));

  ^~
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp:13:94: 
note: suggested alternatives:
In file included from /usr/include/boost/system/error_code.hpp:22:0,
 from /usr/include/boost/filesystem/path_traits.hpp:23,
 from /usr/include/boost/filesystem/path.hpp:25,
 from /usr/include/boost/filesystem.hpp:16,
 from 
/build/critterding-1.0-beta14+dfsg/src/./filesystem/be_dir.h:4,
 from 
/build/critterding-1.0-beta14+dfsg/src/./utils/settings.h:10,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.h:7,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp:1:
/usr/include/c++/6/functional:703:34: note:   'std::placeholders::_1'
 extern const _Placeholder<1> _1;
  ^~
In file included from /usr/include/boost/mpl/aux_/include_preprocessed.hpp:37:0,
 from /usr/include/boost/mpl/placeholders.hpp:43,
 from /usr/include/boost/iterator/iterator_categories.hpp:17,  
 from /usr/include/boost/iterator/iterator_facade.hpp:14,
 from /usr/include/boost/filesystem/path.hpp:28,
 from /usr/include/boost/filesystem.hpp:16,
 from 
/build/critterding-1.0-beta14+dfsg/src/./filesystem/be_dir.h:4,
 from 
/build/critterding-1.0-beta14+dfsg/src/./utils/settings.h:10,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.h:7,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp:1:
/usr/include/boost/mpl/aux_/preprocessed/gcc/placeholders.hpp:29:16: note:   
'mpl_::_1'
 typedef arg<1> _1;
^~
/usr/include/boost/mpl/aux_/preprocessed/gcc/placeholders.hpp:29:16: note:   
'mpl_::_1'
In file included from /usr/include/boost/bind/bind.hpp:2247:0,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp:2:
/usr/include/boost/bind/placeholders.hpp:46:38: note:   
'boost::placeholders::_1'
 BOOST_STATIC_CONSTEXPR boost::arg<1> _1;
  ^~
In file included from /usr/include/boost/mpl/aux_/include_preprocessed.hpp:37:0,
 from /usr/include/boost/mpl/placeholders.hpp:43,
 from /usr/include/boost/iterator/iterator_categories.hpp:17,  
 from /usr/include/boost/iterator/iterator_facade.hpp:14,
 from /usr/include/boost/filesystem/path.hpp:28,
 from /usr/include/boost/filesystem.hpp:16,
 from 
/build/critterding-1.0-beta14+dfsg/src/./filesystem/be_dir.h:4,
 from 
/build/critterding-1.0-beta14+dfsg/src/./utils/settings.h:10,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.h:7,
 from 
/build/critterding-1.0-beta14+dfsg/src/common/be_command_system.cpp:1:
/usr/include/boost/mpl/aux_/preprocessed/gcc/placeholders.hpp:29:16: note:   
'mpl_::_1'
 typedef arg<1> _1;
^~
src/common/CMakeFiles/common.dir/build.make:257: recipe for target 
'src/common/CMakeFiles/common.dir/be_command_system.cpp.o' failed
make[3]: *** 

Processed: owner 806617

[Debian Bug Tracking System]

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

> owner 806617 stapelb...@debian.org
Bug #806617 [src:freeradius] freeradius: FTBFS when built with 
dpkg-buildpackage -A (dh_install: freeradius-common missing files)
Owner recorded as stapelb...@debian.org.
> thanks
Stopping processing here.

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

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

[Erik Tews]

Am Samstag, den 17.09.2016, 09:37 +0200 schrieb Michael Biebl:
> Am 17.09.2016 um 01:09 schrieb Erik Tews:
> 
> > 
> > After startup, gdm doesn't show up and just shows a grey screen.
> > Looking at syslog reveals the reason:
> > 
> > syslog:Sep 16 23:27:25 matte kernel: [  172.983123] gnome-
> > shell[3206]: segfault 
> > at 10 ip 7f8e7c85d6c4 sp 7ffd151d0a80 error 4 in
> > libwacom.so.2.4.6[7f8e7
> > c85a000+9000]
> > 
> > Since I haven't updated libwacom2 in the last 2 weeks, but gnome-
> > shell was recently updated, I assume this is due to a problem in
> > gnome-shell.
> > 
> > There is also a temporary fix, just run: rmmod wacom, and then
> > restart gdm, and you can use it again, of course without the
> > touchscreen.
> > 
> > Unfortunately, in upstream, I cannot see any kind of commit between
> > 3.21.92 and 3.21.91 that might cause such a problem.
> 
> Can you downgrade gnome-shell (and gnome-shell-common) to version
> 3.21.91-2 (from testing), reboot and test if the problem is still
> reproducible?
> 
> If not, does downgrading libmutter0i, mutter-common, mutter to
> 3.21.91-2
> fix the problem?

Just downgrading gnome-shell with the dependencies didn't help, but
downgrading mutter and some related packages with gnome-shell solved
the problem. Right now I have the following versions of those packages,
everything else is on Debian unstable:

ii  gdm33.21.90-1amd64  
  GNOME Display Manager
ii  gir1.2-gdm-1.0  3.21.90-1amd64  
  GObject introspection data for the GNOME Display Manager
ii  gir1.2-mutter-3.0:amd64 3.21.91-2amd64  
  GObject introspection data for Mutter
ii  gnome-session   3.20.2-1 all
  GNOME Session Manager - GNOME 3 session
ii  gnome-session-bin   3.20.2-1 amd64  
  GNOME Session Manager - Minimal runtime
ii  gnome-session-common3.20.2-1 all
  GNOME Session Manager - common files
ii  gnome-shell 3.21.91-2amd64  
  graphical shell for the GNOME desktop
ii  gnome-shell-common  3.21.91-2all
  common files for the GNOME graphical shell
ii  gnome-shell-extensions  3.21.91-1all
  Extensions to extend functionality of GNOME Shell
ii  libgdm1 3.21.90-1amd64  
  GNOME Display Manager (shared library)
ii  libmutter0i:amd64   3.21.91-2amd64  
  window manager library from the Mutter window manager
ii  linux-base  4.4  all
  Linux image base package
ii  mutter  3.21.91-2amd64  
  lightweight GTK+ window manager
ii  mutter-common   3.21.91-2all
  shared files for the Mutter window manager

And gdm with gnome-shell works fine with wacom.

I also looked at the upstream git commits for mutter, but didn't find
an obvious one that causes the problem.

Is there any nice way of getting a stack backtrace when gnome-shell
launched by gdm crashes so that I can see how the call looks like and
through which library it went?

Erik

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

Processed: bug 836825 is forwarded to https://github.com/djberg96/sys-filesystem/issues/22

[Debian Bug Tracking System]

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

> forwarded 836825 https://github.com/djberg96/sys-filesystem/issues/22
Bug #836825 [src:ruby-sys-filesystem] ruby-sys-filesystem: FTBFS in testing 
(failing tests)
Set Bug forwarded-to-address to 
'https://github.com/djberg96/sys-filesystem/issues/22'.
> thanks
Stopping processing here.

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

Bug#836816: marked as done (calligra-l10-*: not installable in sid)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 16:24:53 +0200
with message-id <1608480.BXfNpC1VFq@pendragon>
and subject line Re: Bug#836816: calligra-l10-*: not installable in sid
has caused the Debian Bug report #836816,
regarding calligra-l10-*: not installable in sid
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.)


-- 
836816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: calligra-l10n-bs
Version: 1:2.8.5-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

I am filing this bug against calligra-l10n-bs but in fact it is the same
for all calligra-l10n-* packages. They are not installable in sid, at least
since 2015-09-11, since they depend on calligra-libs which does not exist
in sid.

Are these packages cruft? The calligra packages only exists in <= stable,
and as source in sid.

-Ralf.
--- End Message ---
--- Begin Message ---
Hi,

In data martedì 6 settembre 2016 09:55:22 CEST, Ralf Treinen ha scritto:
> Package: calligra-l10n-bs
> Version: 1:2.8.5-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-uninstallable
> 
> Hi,
> 
> I am filing this bug against calligra-l10n-bs but in fact it is the same
> for all calligra-l10n-* packages. They are not installable in sid, at least
> since 2015-09-11, since they depend on calligra-libs which does not exist
> in sid.

They are installable again now, since there's a new version of calligra
in the archive.

> Are these packages cruft? The calligra packages only exists in <= stable,
> and as source in sid.

No, they are not.  I'll upload a new version of calligra-l10n soon.

Thanks for your report,
-- 
Pino Toscano

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

Processed: severity of 837976 is serious, user debian...@lists.debian.org, usertagging 837222 ...

[Debian Bug Tracking System]

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

> severity 837976 serious
Bug #837976 [mmh] mmh: Fails to install if package pick is installed
Severity set to 'serious' from 'important'
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 837222 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20160910.
Usertags are now: piuparts qa-ftbfs qa-ftbfs-20160910.
> usertags 837238 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20160910.
Usertags are now: piuparts qa-ftbfs qa-ftbfs-20160910.
> thanks
Stopping processing here.

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

Bug#838116: libgpod-nogtk-dev: fails to install in sid/i386 with --install-recommends

[Andreas Beckmann]

Package: libgpod-nogtk-dev
Version: 0.8.3-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  The following packages have unmet dependencies:
   libgpod-nogtk-dev : Depends: libgpod4-nogtk (= 0.8.3-8) but it is not going 
to be installed
  E: Unable to correct problems, you have held broken packages.

This was observed during a test on i386 with --install-recommends enabled.
I cannot reproduce it on amd64.

There is an unsatisfiable Recommends: libgpod-common in libgpod4-nogtk

  libgpod-nogtk-dev
Depends: libgpod4-nogtk
  Recomends: libgpod-common
Depends: libgpod4
  Conflicts: libgpod4-nogtk
 
Package: libgpod-nogtk-dev
Source: libgpod
Version: 0.8.3-8
Architecture: i386
Depends: libgpod4-nogtk (= 0.8.3-8), libglib2.0-dev, libimobiledevice-dev
Suggests: libgpod-doc
Conflicts: libgpod-dev

Package: libgpod4-nogtk
Source: libgpod
Version: 0.8.3-8
Architecture: i386
Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.31.18), libimobiledevice6 (>= 
0.9.7), libplist3 (>= 1.11), libsqlite3-0 (>= 3.5.9), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.2.0)
Recommends: libgpod-common
Conflicts: libgpod4

Package: libgpod-common
Source: libgpod
Version: 0.8.3-8
Architecture: i386
Replaces: libgpod0 (<< 0.3.0-4)
Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.31.18), libgpod4 (>= 0.7.90), 
libimobiledevice6 (>= 0.9.7), libplist3 (>= 1.11), libsgutils2-2 (>= 1.27), 
libusb-1.0-0 (>= 2:1.0.8), libxml2 (>= 2.7.4)

Package: libgpod4
Source: libgpod
Version: 0.8.3-8
Architecture: i386
Depends: libc6 (>= 2.4), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 
2.31.18), libimobiledevice6 (>= 0.9.7), libplist3 (>= 1.11), libsqlite3-0 (>= 
3.5.9), libxml2 (>= 2.7.4), zlib1g (>= 1:1.2.0)
Recommends: libgpod-common
Conflicts: libgpod4-nogtk


cheers,

Andreas


libgpod-nogtk-dev_0.8.3-8.log.gz
Description: application/gzip

Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

[Mattia Rizzolo]

control: found -1 4.3.1~dfsg-1

On Sat, Sep 17, 2016 at 03:42:49PM +0200, Jérémy Lal wrote:
> > Is this a regression in 4.4.7, or is 4.3.1 also affected? This is blocking
> > testing migration, which is preventing the mips64el binaries from entering
> > testing.
> 
> It's been like this forever.

so, marking as such, so that this won't be considered a regression and
testing migration can happen in the meantime.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.3.1~dfsg-1
Bug #830242 [src:nodejs] nodejs: accesses the internet during build
Marked as found in versions nodejs/4.3.1~dfsg-1.

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

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

[Rann Bar-On]

On Sat, 17 Sep 2016 09:37:48 +0200 Michael Biebl 
wrote:
> Am 17.09.2016 um 01:09 schrieb Erik Tews:
> 
> > After startup, gdm doesn't show up and just shows a grey screen.
Looking at syslog reveals the reason:
> > 
> > syslog:Sep 16 23:27:25 matte kernel: [  172.983123] gnome-
shell[3206]: segfault 
> > at 10 ip 7f8e7c85d6c4 sp 7ffd151d0a80 error 4 in
libwacom.so.2.4.6[7f8e7
> > c85a000+9000]
> > 
> > Since I haven't updated libwacom2 in the last 2 weeks, but gnome-
shell was recently updated, I assume this is due to a problem in gnome-
shell.
> > 
> > There is also a temporary fix, just run: rmmod wacom, and then
restart gdm, and you can use it again, of course without the
touchscreen.
> > 
> > Unfortunately, in upstream, I cannot see any kind of commit between
3.21.92 and 3.21.91 that might cause such a problem.
> 
> Can you downgrade gnome-shell (and gnome-shell-common) to version
> 3.21.91-2 (from testing), reboot and test if the problem is still
> reproducible?
> 
> If not, does downgrading libmutter0i, mutter-common, mutter to
3.21.91-2
> fix the problem?
> 
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 

Downgrading gnome-shell (and gnome-shell-common) does not help.
However, downgrading libmutter0i, mutter-common, and mutter does the
trick. Note that I also updated libwacom2 to 0.22-1, as specified in
bug 838047. On its own, that did not do the trick, but when I
downgraded the various mutter packages, the problem went away.

Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

[Jérémy Lal]

2016-09-17 15:20 GMT+02:00 Emilio Pozuelo Monfort :

> Hi,
>
> On Thu, 07 Jul 2016 16:38:15 +0200 Chris Lamb  wrote:
> > Source: nodejs
> > Version: 4.4.7~dfsg-2
> > Severity: serious
> > Justification: Policy 4.9
> > User: la...@debian.org
> > Usertags: network-access
> >
> > Dear Maintainer,
> >
> > Whilst nodejs builds successfully on unstable/amd64, according to
> > Debian Policy 4.9 packages may not attempt network access during
> > a build.
> >
> >   00:00:00.00 IP 60e0bdbdf45e.48831 > dnscache.uct.ac.za.domain:
> 36996+ A? localhost. (27)
> >   00:00:00.005147 IP dnscache.uct.ac.za.domain > 60e0bdbdf45e.48831:
> 36996* 1/1/1 A 127.0.0.1 (85)
> >   00:00:49.376504 IP 60e0bdbdf45e.34203 > dnscache.uct.ac.za.domain:
> 46038+ ? www.google.com. (32)
> >   00:00:49.376504 IP 60e0bdbdf45e.59241 > dnscache.uct.ac.za.domain:
> 21036+ A? www.google.com. (32)
> >
> >   [..]
> >
> > The full build log (including tcpdump output) is attached.
>
> Is this a regression in 4.4.7, or is 4.3.1 also affected? This is blocking
> testing migration, which is preventing the mips64el binaries from entering
> testing.
>


It's been like this forever.
See the discussion on -devel about all the packages having the same problem.
I'm going to fix this eventually, it's just that i'm really super busy
these days.

Anyone willing to help is welcome of course.

Jérémy

Bug#837786: mutter: Issues repainting the display on mouse movement

[John M.]

Since Wednesday, I've done as follows:
- Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1
(repaint/redraw issues).
- Tried to report the bug, but reportbug showed a version of mutter in
unstable.
- Upgraded to mutter 3.31.92-1 and gnome-shell 3.21.92-1
(repaint/redraw issues).
- Reported the bug.
- Downgraded to mutter 3.20.3-2 and gnome-shell 3.20.3-1 using dpkg and
/var/cache/archives.
- Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1 again
(repaint/redraw issues)
- Tried some DRI suggestions from ArchWiki, but none of them solve the
issue.
- Downgraded to mutter 3.20.3-2 and gnome-shell 3.20.3-1 using dpkg and
/var/cache/archives.
- Upgraded to mutter 3.21.91-2 and gnome-shell 3.21.91-1 again
(repaint/redraw issues)
- Tried disabling some files in modprobe, but it doesn't seem to solve
the issue.
- Downgraded to mutter 3.20.3-2 and gnome-shell 3.20.3-1 using dpkg and
/var/cache/archives.

So the problem is always reproducible.

--
John.




> Am 14.09.2016 um 17:16 schrieb JWM:
> 
> > > > After upgrading my system this morning and restarting a new gnome-
shell session
> > > > (by rebooting), everything being displayed fails to repaint
properly.
> > 
> > > > Everytime I launch an application and try to move the window it
leaves traces
> > > > (i.e., shadows of its previous positions). The same happens on
mouse hover.
> > 
> > > > Also, the clock (on the top desktop) flickers
constantly.  Something similar
> > happens with the title bar in certain applications (e.g., vivaldi).
> > 
> > > > Since the only packages upgraded were related to mutter and gnome-
shell, I
> > figure the one to blame is mutter.
> > 
> 
> 
> > Can you downgrade mutter to 3.21.91-2 (from testing), reboot and test
if
> the problem is reproducible?
> 
> 

Processed: limit source to imagemagick, tagging 836174

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 836174 + pending
Bug #836174 [src:imagemagick] Prevent runtime error: divide by zero
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831243: marked as done (nodejs: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 15:22:34 +0200
with message-id <220603eb-42db-125d-36a6-e42c5f449...@debian.org>
and subject line Re: nodejs: FTBFS: Tests failures
has caused the Debian Bug report #831243,
regarding nodejs: FTBFS: Tests 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.)


-- 
831243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 4.4.7~dfsg-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> /usr/bin/python tools/test.py -p tap --mode=release --flaky-tests=dontcare \
>   --arch=x64 --timeout=3000 message parallel sequential
> 1..1012
> ok 1 parallel/test-arm-math-exp-regress-1376
>   ---
>   duration_ms: 0.88
>   ...
> ok 2 parallel/test-assert
>   ---
>   duration_ms: 0.137
>   ...
> ok 3 parallel/test-assert-typedarray-deepequal
>   ---
>   duration_ms: 0.609
>   ...
> ok 4 parallel/test-async-wrap-check-providers
>   ---
>   duration_ms: 0.170
>   ...
> ok 5 parallel/test-async-wrap-disabled-propagate-parent
>   ---
>   duration_ms: 0.89
>   ...
> ok 6 parallel/test-async-wrap-propagate-parent
>   ---
>   duration_ms: 0.88
>   ...
> ok 7 parallel/test-async-wrap-throw-no-init
>   ---
>   duration_ms: 0.71
>   ...
> ok 8 parallel/test-bad-unicode
>   ---
>   duration_ms: 0.71
>   ...
> ok 9 parallel/test-beforeexit-event
>   ---
>   duration_ms: 0.88
>   ...
> ok 10 parallel/test-beforeexit-event-exit
>   ---
>   duration_ms: 0.71
>   ...
> ok 11 parallel/test-buffer
>   ---
>   duration_ms: 0.110
>   ...
> ok 12 parallel/test-buffer-arraybuffer
>   ---
>   duration_ms: 0.88
>   ...
> ok 13 parallel/test-buffer-ascii
>   ---
>   duration_ms: 0.71
>   ...
> ok 14 parallel/test-buffer-bytelength
>   ---
>   duration_ms: 0.89
>   ...
> ok 15 parallel/test-buffer-concat
>   ---
>   duration_ms: 0.89
>   ...
> ok 16 parallel/test-buffer-fakes
>   ---
>   duration_ms: 0.88
>   ...
> ok 17 parallel/test-buffer-indexof
>   ---
>   duration_ms: 0.89
>   ...
> ok 18 parallel/test-buffer-inheritance
>   ---
>   duration_ms: 0.71
>   ...
> ok 19 parallel/test-buffer-inspect
>   ---
>   duration_ms: 0.71
>   ...
> ok 20 parallel/test-buffer-iterator
>   ---
>   duration_ms: 0.71
>   ...
> ok 21 parallel/test-buffer-slow
>   ---
>   duration_ms: 0.89
>   ...
> ok 22 parallel/test-buffer-zero-fill-reset
>   ---
>   duration_ms: 0.72
>   ...
> ok 23 parallel/test-c-ares
>   ---
>   duration_ms: 0.89
>   ...
> ok 24 parallel/test-child-process-buffering
>   ---
>   duration_ms: 0.89
>   ...
> ok 25 parallel/test-child-process-constructor
>   ---
>   duration_ms: 0.89
>   ...
> ok 26 parallel/test-child-process-cwd
>   ---
>   duration_ms: 0.110
>   ...
> ok 27 parallel/test-child-process-default-options
>   ---
>   duration_ms: 0.89
>   ...
> ok 28 parallel/test-child-process-detached
>   ---
>   duration_ms: 0.170
>   ...
> ok 29 parallel/test-child-process-disconnect
>   ---
>   duration_ms: 0.211
>   ...
> ok 30 parallel/test-child-process-double-pipe
>   ---
>   duration_ms: 0.110
>   ...
> ok 31 parallel/test-child-process-env
>   ---
>   duration_ms: 0.89
>   ...
> ok 32 parallel/test-child-process-exec-buffer
>   ---
>   duration_ms: 0.89
>   ...
> ok 33 parallel/test-child-process-exec-cwd
>   ---
>   duration_ms: 0.110
>   ...
> ok 34 parallel/test-child-process-exec-env
>   ---
>   duration_ms: 0.110
>   ...
> ok 35 parallel/test-child-process-exec-error
>   ---
>   duration_ms: 0.110
>   ...
> ok 36 parallel/test-child-process-exit-code
>   ---
>   duration_ms: 0.263
>   ...
> ok 37 parallel/test-child-process-flush-stdio
>   ---
>   duration_ms: 0.110
>   ...
> ok 38 parallel/test-child-process-fork
>   ---
>   duration_ms: 0.212
>   ...
> ok 39 parallel/test-child-process-fork-and-spawn
>   ---
>   duration_ms: 0.264
>   ...
> ok 40 parallel/test-child-process-fork-close
>   ---
>   duration_ms: 0.170
>   ...
> ok 41 parallel/test-child-process-fork-dgram
>   ---
>   duration_ms: 0.328
>   ...
> ok 42 parallel/test-child-process-fork-exec-argv
>   ---
>   duration_ms: 0.263
>   ...
> ok 43 parallel/test-child-process-fork-exec-path
>   ---
>   duration_ms: 0.610
>   ...
> ok 44 parallel/test-child-process-fork-net
>   ---
>   duration_ms: 0.212
>   ...
> ok 45 parallel/test-child-process-fork-net2
>   ---
>   duration_ms: 0.409
>   ...
> 

Processed: limit source to libdata-messagepack-perl, tagging 827576

[Debian Bug Tracking System]

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

> limit source libdata-messagepack-perl
Limiting to bugs with field 'source' containing at least one of 
'libdata-messagepack-perl'
Limit currently set to 'source':'libdata-messagepack-perl'

> tags 827576 + pending
Bug #827576 [libdata-messagepack-perl] libdata-messagepack-perl: FTBFS with new 
msgpack-c (fixed in 1.00 upstream)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#830242: nodejs: accesses the internet during build

[Emilio Pozuelo Monfort]

Hi,

On Thu, 07 Jul 2016 16:38:15 +0200 Chris Lamb  wrote:
> Source: nodejs
> Version: 4.4.7~dfsg-2
> Severity: serious
> Justification: Policy 4.9
> User: la...@debian.org
> Usertags: network-access
> 
> Dear Maintainer,
> 
> Whilst nodejs builds successfully on unstable/amd64, according to
> Debian Policy 4.9 packages may not attempt network access during
> a build.
> 
>   00:00:00.00 IP 60e0bdbdf45e.48831 > dnscache.uct.ac.za.domain: 36996+ 
> A? localhost. (27)
>   00:00:00.005147 IP dnscache.uct.ac.za.domain > 60e0bdbdf45e.48831: 36996* 
> 1/1/1 A 127.0.0.1 (85)
>   00:00:49.376504 IP 60e0bdbdf45e.34203 > dnscache.uct.ac.za.domain: 46038+ 
> ? www.google.com. (32)
>   00:00:49.376504 IP 60e0bdbdf45e.59241 > dnscache.uct.ac.za.domain: 21036+ 
> A? www.google.com. (32)
> 
>   [..]
> 
> The full build log (including tcpdump output) is attached.

Is this a regression in 4.4.7, or is 4.3.1 also affected? This is blocking
testing migration, which is preventing the mips64el binaries from entering 
testing.

Cheers,
Emilio

Bug#838114: varnish-modules: FTBFS against varnish 5, GCC 6

[Andreas Beckmann]

Source: varnish-modules
Version: 0.9.1-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

varnish-modules against the recently uploaded varnish 5 and/or GCC 6

vmod_xkey.c:456:10: error: 'enum exp_event_e' declared inside parameter list 
will not be visible outside of this definition or declaration [-Werror]
 enum exp_event_e event, void *priv)
  ^~~
vmod_xkey.c:456:22: error: parameter 3 ('event') has incomplete type
 enum exp_event_e event, void *priv)
  ^
vmod_xkey.c: In function 'xkey_cb':
vmod_xkey.c:465:7: error: 'EXP_INSERT' undeclared (first use in this function)
  case EXP_INSERT:
   ^~
vmod_xkey.c:465:7: note: each undeclared identifier is reported only once for 
each function it appears in
vmod_xkey.c:466:7: error: 'EXP_INJECT' undeclared (first use in this function)
  case EXP_INJECT:
   ^~
vmod_xkey.c:469:7: error: 'EXP_REMOVE' undeclared (first use in this function)
  case EXP_REMOVE:
   ^~
vmod_xkey.c:456:22: error: unused parameter 'event' [-Werror=unused-parameter]
 enum exp_event_e event, void *priv)
  ^
vmod_xkey.c: In function 'purge':
vmod_xkey.c:511:18: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
   oc->objcore->exp.ttl <= (ctx->now - oc->objcore->exp.t_origin))
  ^~
vmod_xkey.c:511:54: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
   oc->objcore->exp.ttl <= (ctx->now - oc->objcore->exp.t_origin))
  ^~
vmod_xkey.c:524:19: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
oc->objcore->exp.grace, oc->objcore->exp.keep);
   ^~
vmod_xkey.c:524:43: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
oc->objcore->exp.grace, oc->objcore->exp.keep);
   ^~
vmod_xkey.c:526:38: error: 'struct objcore' has no member named 'exp'; did you 
mean 'keep'?
EXP_Rearm(oc->objcore, oc->objcore->exp.t_origin, 0,
  ^~
vmod_xkey.c: In function 'vmod_event':
vmod_xkey.c:559:8: error: implicit declaration of function 
'EXP_Register_Callback' [-Werror=implicit-function-declaration]
EXP_Register_Callback(xkey_cb, NULL);
^
vmod_xkey.c:572:4: error: implicit declaration of function 
'EXP_Deregister_Callback' [-Werror=implicit-function-declaration]
EXP_Deregister_Callback(_cb_handle);
^~~


Andreas


sid.build.gz
Description: application/gzip

Bug#838113: pathspider: missing dependency on python3-libtrace

[Iain R. Learmonth]

Package: pathspider
Version: 0.9.0-1
Severity: serious
Justification: Policy 3.5

Hi,

Need that dep.

Thanks,
Iain.

Bug#838112: uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr

[Andreas Beckmann]

Package: uctodata
Version: 0.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', 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/ch-relationships.html#s-replaces

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

  Selecting previously unselected package uctodata.
  Preparing to unpack .../uctodata_0.1.1-1_all.deb ...
  Unpacking uctodata (0.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uctodata_0.1.1-1_all.deb (--unpack):
   trying to overwrite '/etc/ucto/es.abr', which is also in package ucto 
0.5.3-3.1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/uctodata_0.1.1-1_all.deb


cheers,

Andreas


ucto=0.5.3-3.1+b1_uctodata=0.1.1-1.log.gz
Description: application/gzip

Bug#838047: Confirmed: breaks *all* tablets

[Rann Bar-On]

Upgraded to 0.22-1. No change, unfortunately.

[   12.990227] gnome-shell[1168]: segfault at 10 ip 7f35122ab844 sp
7ffd8efd9be0 error 4 in libwacom.so.2.5.0[7f35122a8000+9000]
[   14.569733] gnome-shell[1239]: segfault at 10 ip 7f724d4e6844 sp
7fffda2ec150 error 4 in libwacom.so.2.5.0[7f724d4e3000+9000]
[   14.884694] gnome-shell[1245]: segfault at 10 ip 7fe7d7128844 sp
7ffc5c90e4b0 error 4 in libwacom.so.2.5.0[7fe7d7125000+9000]

Note: see bug 838050

Bug#838047: Confirmed: breaks *all* tablets

[Rann Bar-On]

On Sat, 2016-09-17 at 09:34 +0300, Timo Aaltonen wrote:
> On 17.09.2016 02:47, a.t.chadw...@gmail.com wrote:
> Confirmed. This bug breaks all graphics tablets in GNOME (at least).
> It
> is not specific to the driver. See the attached logs.
> 
> Symptoms: when a graphics tablet is plugged in, within a few seconds
> the
> running X session terminates. Examining the logs reveals repeated
> segfaults from gnome-shell caused by libwacom2; the repetition is
> classed as the session respawning too fast by gnome-session, which
> gives
> up in disgust.
> 
> (As originally reported, sessions break with a blank screen if the
> tablet is plugged in at session start too.)
> 
> Affected hardware: all the tablets I own, namely:
> 
> * Genius i405x (evdev driver, horribly broken)
> * Huion H610PRO (libinput, normally works well)
> * Wacom Intuos5 M (wacom, normally works perfectly)
> 
> Expected behaviour: I would expect no segfaults which kill X when
> plugging in my graphics tablets.
> 
> I am using libwacom2 0.19-1, gnome-shell 3.21.91-2, and
> gnome-settings-daemon 3.21.92.1-1.
> 
> Libwacom 0.22 has been released upstream, and may be necessary for
> this
> version of GNOME. Please can that be tried? Libwacom mismatches have
> killed tablet support in the past
> 
> 
> sounds like gnome dependencies are wrong then.. anyway, 0.22-1
> uploaded,
> please test
> 
> 
> -- 
> t
> 
> 

I'll test when I see it appear in my apt update! In the meantime, this
is related to bug 838050.

Bug#835680: marked as done (mathgl: FTBFS: complex_io.cpp:32:18: fatal error: hdf5.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 12:32:12 +
with message-id 
and subject line Bug#835680: fixed in mathgl 2.3.4-1.1
has caused the Debian Bug report #835680,
regarding mathgl: FTBFS: complex_io.cpp:32:18: fatal error: hdf5.h: 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.)


-- 
835680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mathgl
Version: 2.3.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DHAVE_MEMRCHR 
> -DMGL_HAVE_GSL2 -DMGL_SRC -DNO_COLOR_ARRAY -Dmgl_EXPORTS 
> -I/<>/include -I/<>/obj-x86_64-linux-gnu/include 
> -I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
> -I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include
>  -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi 
> -I/<>/src/prc  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -fvisibility=hidden -fvisibility-inlines-hidden -fPIC   
> -o CMakeFiles/mgl.dir/complex_io.cpp.o -c /<>/src/complex_io.cpp
> /<>/src/complex_io.cpp:32:18: fatal error: hdf5.h: No such file 
> or directory
>  #include 
>   ^
> compilation terminated.
> src/CMakeFiles/mgl.dir/build.make:305: recipe for target 
> 'src/CMakeFiles/mgl.dir/complex_io.cpp.o' failed
> make[3]: *** [src/CMakeFiles/mgl.dir/complex_io.cpp.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/mathgl_2.3.4-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: mathgl
Source-Version: 2.3.4-1.1

We believe that the bug you reported is fixed in the latest version of
mathgl, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mathgl 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: Mon, 12 Sep 2016 10:41:06 +0100
Source: mathgl
Binary: mathgl udav libmgl7.4.1 libmgl-mpi7.4.1 libmgl-wnd7.4.1 
libmgl-glut7.4.1 libmgl-qt5-7.4.1 libmgl-fltk7.4.1 libmgl-wx7.4.1 libmgl-data 
libmgl-dev python-mathgl
Architecture: source all amd64
Version: 2.3.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Description:
 libmgl-data - library for scientific graphs (data files)
 libmgl-dev - library for scientific graphs (development files)
 libmgl-fltk7.4.1 - library for scientific graphs (fltk interface for windows)
 libmgl-glut7.4.1 - library for scientific graphs (glut interface for windows)
 libmgl-mpi7.4.1 - library for scientific graphs (mpi enhanced runtime library)
 libmgl-qt5-7.4.1 - library for scientific graphs (Qt interface for windows)
 libmgl-wnd7.4.1 - library for scientific graphs (windows runtime library)
 libmgl-wx7.4.1 - library for scientific graphs (wx interface for windows)
 libmgl7.4.1 - library for scientific graphs (main runtime library)
 mathgl - library for scientific graphs (utilities and examples)
 python-mathgl - library for scientific graphs (Python module)
 udav   - library for scientific graphs (window interface)
Closes: 835680
Changes:
 mathgl (2.3.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix from Bas  Couwenberg for HDF5 build issue. Closes: 

Bug#834683: marked as done (mini-buildd: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 12:32:37 +
with message-id 
and subject line Bug#834683: fixed in mini-buildd 1.0.19
has caused the Debian Bug report #834683,
regarding mini-buildd: FTBFS too much often (failing tests)
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.)


-- 
834683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mini-buildd
Version: 1.0.16
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python2,sphinxdoc,systemd
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
python setup.py build --force
I: Using setuptools: 20.10.1
I: Got version from changelog: 1.0.16
running build
running build_py

[... snipped ...]

mini_buildd.builder.Build.build
mini_buildd.builder.Build.clean
mini_buildd.builder.Build.distribution
mini_buildd.builder.Build.key
mini_buildd.builder.Build.package
mini_buildd.builder.Build.sbuildrc_path
mini_buildd.builder.Build.took
mini_buildd.builder.Build.upload
mini_buildd.builder.Build.upload_result_to
mini_buildd.builder.Build.version
mini_buildd.builder.LastBuild
mini_buildd.builder.LastBuild.__init__
mini_buildd.builder.LastBuild.__unicode__
mini_buildd.builder.build
mini_buildd.builder.build_close
mini_buildd.builder.run
0 tests in 25 items.
0 passed and 0 failed.
Test passed.
=> Doctest on mini_buildd/setup.py (mini_buildd.setup)
/<>/mini_buildd/misc.py:27: ImportWarning: Not importing directory 
'/<>/debian': missing __init__.py
  import debian.debian_support
/usr/lib/python2.7/dist-packages/registration/models.py:140: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name=_(u'user'))
/usr/lib/python2.7/dist-packages/registration/migrations/0001_initial.py:31: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name='user')),
2 items had no tests:
mini_buildd.setup
mini_buildd.setup.log_exception
0 tests in 2 items.
0 passed and 0 failed.
Test passed.
=> Doctest on mini_buildd/gnupg.py (mini_buildd.gnupg)
/<>/mini_buildd/misc.py:27: ImportWarning: Not importing directory 
'/<>/debian': missing __init__.py
  import debian.debian_support
/usr/lib/python2.7/dist-packages/registration/models.py:140: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name=_(u'user'))
/usr/lib/python2.7/dist-packages/registration/migrations/0001_initial.py:31: 
RemovedInDjango20Warning: on_delete will be a required arg for OneToOneField in 
Django 2.0. Set it to models.CASCADE on models and in existing migrations if 
you want to maintain the current default behavior. See 
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.ForeignKey.on_delete
  verbose_name='user')),
D: TmpDir /tmp/tmpvXY9eX
I: Calling: gpg --homedir=/tmp/tmpvXY9eX --display-charset=UTF-8 --batch 
--gen-key
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Build killed with signal TERM after 60 minutes of inactivity


I actually tried to build this package three times, and there was
only one successful build from those three. I don't think that's

Bug#837942: marked as done (gtk-doc-tools: Missing dependency on pkg-config)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 12:28:01 +
with message-id 
and subject line Bug#837942: fixed in gtk-doc 1.25-5
has caused the Debian Bug report #837942,
regarding gtk-doc-tools: Missing dependency on pkg-config
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.)


-- 
837942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk-doc-tools
Version: 1.25-4
Severity: serious

gtk-doc-tools in experimental is lacking a dependency on pkg-config,
GTK_DOC_CHECK will fail if it is missing.

---
AC_DEFUN([GTK_DOC_CHECK],
[
  AC_REQUIRE([PKG_PROG_PKG_CONFIG])
---

This only applies to experimental, sid fullfils this via the gnome-core
dependency.

cu Andreas 
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: gtk-doc
Source-Version: 1.25-5

We believe that the bug you reported is fixed in the latest version of
gtk-doc, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated gtk-doc 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: Sat, 17 Sep 2016 11:03:06 +0200
Source: gtk-doc
Binary: gtk-doc-tools
Architecture: source
Version: 1.25-5
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gtk-doc-tools - GTK+ documentation tools
Closes: 837942
Changes:
 gtk-doc (1.25-5) experimental; urgency=medium
 .
   * Make pkg-config a Depends and not just a Recommends. Virtually every
 package which uses gtk-doc does so via the GTK_DOC_CHECK macro and this
 macro requires pkg-config. (Closes: #837942)
Checksums-Sha1:
 c48aa89831e5bb4c01f3240494ffbf2b69d160c2 2324 gtk-doc_1.25-5.dsc
 3bfb6303d7f2097768cd154a4a318e3b893edd2f 14552 gtk-doc_1.25-5.debian.tar.xz
Checksums-Sha256:
 fb8f3553ae75e70977d0230dea3c84c4b2120810fe1e21df9e2dd96137322b50 2324 
gtk-doc_1.25-5.dsc
 d07748c07fa21e56a0a0495344ad2800ac171a9f2900dfb622abae90f623d14b 14552 
gtk-doc_1.25-5.debian.tar.xz
Files:
 1439d51825886b3e4b14d064257d8249 2324 gnome optional gtk-doc_1.25-5.dsc
 cb104669bc0ce9b3a8b8dd5fed385e39 14552 gnome optional 
gtk-doc_1.25-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJX3Qb7ERxiaWVibEBkZWJpYW4ub3JnAAoJEGrh3w1gjyLcQdYP
/3pmjE9Bnkb5B6eEynvGK2ThK6iUBKKqf3GsCOLZx5TXR2tzMfooE1QsszQe6fix
Dwbh14gQOz/VXFq7ck5FqOZP7nBCCoKWF9j5eX9QcxHsm16VFFrN9aagjlENRdKw
S/6M1rygK5FoUGspKYirKgHKqGX6hNW7L1YLv8a1u5GabTTdKvwA52d1b2Ls8Ffd
JE81OikIP0R22I/gaJOJdDjSLfL+D36YdPH+rg+HPWNV0p2SNfJfq+qN7K6I36iN
GgJr8poC1kEo9GJGEgz64ZdM0k1emsOj58ILxc/DNhR7Vmbt++a8m1ORWDYWULwi
QHvNHr+d9WNFRRkv+bHJwcq4BfMq0EX0N3i5cprHk5AlFtIfHdZnXrCPuiT2Ed+K
nWgcCbNVpDsK2PACYRMioEG3uiIEHdFSa/jk4E6xNNiBX85SkAaloFHolcDcrXI1
NYWh2q0Z3iVLUQtOQDMBOW/rpBd+2DsXqdDKUECT0cqIcWbFKCrP7T88kotCwV2V
ErhIsqHm0YG3gqPTD2kBhmQO+wehhfYRKZqMigrEymwn0FQVyhEbE8HTNmBr9MQI
6edipahVq3PkUhW6xsGsQ6ViME9Ll5NZizV3N/+dSdKYWD7JxTI3Fu2cka3EKCjE
RZuWj5VTsRSqmy5QxTDf+wWsnY/2jpCpo9rbaMbtv7NR
=g/Vd
-END PGP SIGNATURE End Message ---

Bug#838105: marked as done (libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 14:27:16 +0200
with message-id <20160917122715.plgveaomympvi...@roeckx.be>
and subject line Re: [Pkg-openssl-devel] Bug#838105: libssl1.1: relocation 
error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version 
OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference
has caused the Debian Bug report #838105,
regarding libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol 
X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 
with link time reference
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.)


-- 
838105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl1.1
Version: 1.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 cfengine3

Hi,

during a test with piuparts I noticed cfengine3/experimental failed to
install in experimental with a openssl symbol related problem.

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

  Selecting previously unselected package cfengine3.
  (Reading database ... 
(Reading database ... 6581 files and directories currently installed.)
  Preparing to unpack .../cfengine3_3.9.1-3_amd64.deb ...
  Unpacking cfengine3 (3.9.1-3) ...
  Setting up cfengine3 (3.9.1-3) ...
  cf-key: relocation error: /usr/lib/libpromises.so.3: symbol 
X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 
with link time reference
  dpkg: error processing package cfengine3 (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   cfengine3

(libpromises3 is built from src:cfengine3)

It may be sufficient to just binNMU src:cfengine3 against the
OpenSSL 1.1.0 release (it was built against 1.1.0~pre6-1).


cheers,

Andreas


cfengine3_3.9.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Sat, Sep 17, 2016 at 01:47:19PM +0200, Andreas Beckmann wrote:
> Package: libssl1.1
> Version: 1.1.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 cfengine3
> 
> Hi,
> 
> during a test with piuparts I noticed cfengine3/experimental failed to
> install in experimental with a openssl symbol related problem.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package cfengine3.
>   (Reading database ... 
> (Reading database ... 6581 files and directories currently installed.)
>   Preparing to unpack .../cfengine3_3.9.1-3_amd64.deb ...
>   Unpacking cfengine3 (3.9.1-3) ...
>   Setting up cfengine3 (3.9.1-3) ...
>   cf-key: relocation error: /usr/lib/libpromises.so.3: symbol 
> X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 
> with link time reference
>   dpkg: error processing package cfengine3 (--configure):
>subprocess installed post-installation script returned error exit status 
> 127
>   Errors were encountered while processing:
>cfengine3
> 
> (libpromises3 is built from src:cfengine3)

It was renamed, and there is a:
x509.h:#  define X509_get_notAfter X509_getm_notAfter

> It may be sufficient to just binNMU src:cfengine3 against the
> OpenSSL 1.1.0 release (it was built against 1.1.0~pre6-1).

binNMUs scheduled, so I'm closing this.


Kurt--- End Message ---

Bug#837783: marked as done (iio-sensor-proxy: hold transition to testing)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 12:28:22 +
with message-id 
and subject line Bug#837783: fixed in iio-sensor-proxy 1.3-1
has caused the Debian Bug report #837783,
regarding iio-sensor-proxy: hold transition to testing
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.)


-- 
837783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iio-sensor-proxy
Version: 1.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable

https://github.com/hadess/iio-sensor-proxy/issues/100

There are some issues that need to be ironed out with the new flip in
kernel 4.8. Also, for 1.2, one more change needs to be picked up.


Until all settles down, block this version's migration to testing.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'unstable'), (990, 'testing'), 
(500, 'unstable-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-rc6ulf+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.24-2
ii  libglib2.0-02.49.7-1
ii  libgudev-1.0-0  230-3
ii  systemd 231-6

iio-sensor-proxy recommends no packages.

iio-sensor-proxy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iio-sensor-proxy
Source-Version: 1.3-1

We believe that the bug you reported is fixed in the latest version of
iio-sensor-proxy, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated iio-sensor-proxy 
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: Sat, 17 Sep 2016 14:35:32 +0530
Source: iio-sensor-proxy
Binary: iio-sensor-proxy
Architecture: source amd64
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Description:
 iio-sensor-proxy - IIO sensors to D-Bus proxy
Closes: 837783
Changes:
 iio-sensor-proxy (1.3-1) unstable; urgency=medium
 .
   * [0eb91a9] New upstream version 1.3 (Closes: #837783)
Checksums-Sha1:
 1618d620cde37902fe6551d447c59f14b32530fc 1954 iio-sensor-proxy_1.3-1.dsc
 57ba4d2dd4609d0a3900903728dd188d6e271cfe 124724 
iio-sensor-proxy_1.3.orig.tar.xz
 fc839e0667ed00fc823ca888e4db951ab372c923 3120 
iio-sensor-proxy_1.3-1.debian.tar.xz
 ea6a37dd20318e0b3f61d25f99f0790fdb4359b0 72588 
iio-sensor-proxy-dbgsym_1.3-1_amd64.deb
 0afa9c3ed9123e650f0b5139badfcd78e5f8f28c 23780 iio-sensor-proxy_1.3-1_amd64.deb
Checksums-Sha256:
 34c6d75c8e406075c93e07694c1270310a97df70df224cf47bbb9eb34979a83c 1954 
iio-sensor-proxy_1.3-1.dsc
 b9b133b22745d7125d3e3e205ac3adfbca9ef388a92af04df0776b79051a6311 124724 
iio-sensor-proxy_1.3.orig.tar.xz
 fc4d3d56f81f63262b6fb4ee5c8008fec69dfdb349957dd37f05e98894ff12a0 3120 
iio-sensor-proxy_1.3-1.debian.tar.xz
 e1f5def40ff6af2c6ce9906cefc1942ec21446bac0c76e7c68a2410dbf6f1387 72588 
iio-sensor-proxy-dbgsym_1.3-1_amd64.deb
 64b57a5cf4760aee0db01a6f378d33e4fcfe4f796aae525a94b49212d898 23780 
iio-sensor-proxy_1.3-1_amd64.deb
Files:
 31f9cdf44e8698cb984742f22a8e454c 1954 utils optional iio-sensor-proxy_1.3-1.dsc
 6592993b382bb16923be143396b21be4 124724 utils optional 
iio-sensor-proxy_1.3.orig.tar.xz
 44e039a34a321fb985c1c86ecc22d0fd 3120 utils optional 
iio-sensor-proxy_1.3-1.debian.tar.xz
 1aa1f1c9166f4a663e5bc7b27716c011 72588 debug extra 
iio-sensor-proxy-dbgsym_1.3-1_amd64.deb
 39f78a201ed9875ec07b235f9dffe81a 23780 utils optional 
iio-sensor-proxy_1.3-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX3QfuAAoJEKY6WKPy4XVpuacP/iMV2edDgYFpTOacO+rdIWcS
mo/XkzcMwPk9K73VsBnkeQjOuDHTRhS05hL0+kbC48wjB2VRkTWccPQbMbWGc9k3
PNd/jS4/VShmzWJ41ZKuZR38JyFY+EW45NJ1iY530JbsXXxAIMzrh4ra4Pez0Vuq

Bug#831164: marked as done (aces3: FTBFS with GCC 6: ld: cannot find -lgfortranbegin)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 12:25:05 +
with message-id 
and subject line Bug#831164: fixed in aces3 3.0.8-5.1
has caused the Debian Bug report #831164,
regarding aces3: FTBFS with GCC 6: ld: cannot find -lgfortranbegin
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.)


-- 
831164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aces3
Version: 3.0.8-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -DMPIF2C -DMPI2 -DC_SUFFIX -DCB_SUFFIX -g -Wall -O2 -I../../sia/include 
> -I../sial -I../../aces/aces_library/a2driver/aces2/include/ 
> -I$MPIHOME/include  -I../../aces/aces_sial/ -L../../../lib -L/usr/lib -o sial 
> \
>sial.o  \
> -lsial -lsip_shared -laces2 -lgfortranbegin -lgfortran -ldl -lsip1 -lsip2 \
> && test -x sial || rm -f sial
> /usr/bin/ld: cannot find -lgfortranbegin
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/aces3_3.0.8-5_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: aces3
Source-Version: 3.0.8-5.1

We believe that the bug you reported is fixed in the latest version of
aces3, 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 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated aces3 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: Sat, 10 Sep 2016 11:05:40 +0100
Source: aces3
Binary: aces3 aces3-data
Architecture: source all amd64
Version: 3.0.8-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Alastair McKinstry 
Description:
 aces3  - Advanced Concepts in Electronic Structure III
 aces3-data - Advanced Concepts in Electronic Structure III
Closes: 831164
Changes:
 aces3 (3.0.8-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix obsolete use of libgfortranbegin. Closes: #831164.
Checksums-Sha1:
 d913d8e46a143855f337492dd6ff76e7d5eb6b8f 1976 aces3_3.0.8-5.1.dsc
 b14daa69859f7ac8932067fe954f6d11257cba89 46156 aces3_3.0.8-5.1.debian.tar.xz
 6c85c647927a7364cd47ee681c4a2435b1492ad7 8407446 aces3-data_3.0.8-5.1_all.deb
 602899e4e96285862536a529263924f976a1aba2 3563408 
aces3-dbgsym_3.0.8-5.1_amd64.deb
 25c64ab63c1e095f8870da1143ed176c77d9e432 39737844 aces3_3.0.8-5.1_amd64.deb
Checksums-Sha256:
 2a547aee71a149362e3f974cae7689c604dd22cba2d67295f965969ae04f27b5 1976 
aces3_3.0.8-5.1.dsc
 fe2266fe2a1b01faf756cd4c63c8cc88c432bacf2b1e5e5aa14acae6acdbffe7 46156 
aces3_3.0.8-5.1.debian.tar.xz
 e725c44b0454a0b35e1f3fcf76544e241274ffe9ae645092c1c874cce3967f52 8407446 
aces3-data_3.0.8-5.1_all.deb
 081599d7ca814afa47eba33e923dd39b7cc3dad09316ab33604e9c07155350e8 3563408 
aces3-dbgsym_3.0.8-5.1_amd64.deb
 9a499fddb79e5ec12f82d071b0434bee09637e819543da78b636a5c400d1f4a6 39737844 
aces3_3.0.8-5.1_amd64.deb
Files:
 7b75d5357cdc002a495d8867e4c10569 1976 science optional aces3_3.0.8-5.1.dsc
 69c3cfd76c095f21683d56ce87a5b719 46156 science optional 
aces3_3.0.8-5.1.debian.tar.xz
 03d0dc9c0b6c56f3bef397f8c5bd00bc 8407446 science optional 
aces3-data_3.0.8-5.1_all.deb
 964ec642baf83faf98254c7042783494 3563408 

Bug#785799: marked as done ([festvox-ca-ona-hts] Since las festival upgrade, catalan voice is not correctly recognized and does not work)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 12:25:49 +
with message-id 
and subject line Bug#785799: fixed in festvox-ca-ona-hts 1.3-1
has caused the Debian Bug report #785799,
regarding [festvox-ca-ona-hts] Since las festival upgrade, catalan voice is not 
correctly recognized and does not work
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.)


-- 
785799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: festvox-ca-ona-hts
Version: 1.2-1
Severity: important

--- Please enter the report below this line. ---

Since last festival package upgrade on May 11th, festvox-ca-ona-hts catalan 
voice for festival no longer works.

I'm using speech-dispatcher with festival as output module wit jovie (formerly 
ktts. kde text speech system). When I try to add a "talker", during 
configuration, all languages appear correctly recognized but catalan. Whith 
catalan voice, Catalan name does no appear on the list, it shows as "none", 
making it incorrectly configurable.


Here you can see, when starting Jovie, talker "Kanija" shows lang="es" 
correctly, and talker "Kaya" shows lang="none" instead lang="ca" (which I 
think is the correct form):

---
jovie(32650)/kttsd (daemon) SpeakerPrivate::readTalkerData: 
TalkerListWidget::loadTalkerCodes: talkerID =  "Kanija"
jovie(32650)/kttsd (daemon) SpeakerPrivate::readTalkerData: 
TalkerCodeWidget::loadTalkerCodes: talkerCode =  ""
jovie(32650)/kttsd (daemon) SpeakerPrivate::readTalkerData: 
TalkerListWidget::loadTalkerCodes: talkerID =  "Kaya"
jovie(32650)/kttsd (daemon) SpeakerPrivate::readTalkerData: 
TalkerCodeWidget::loadTalkerCodes: talkerCode =  ""
---

I don't know what info do you need, but when trying to selecto voice in 
festival and test it I get an aplay error:

festival> (voice.list)
(upc_ca_ona_hts el_diphone kal_diphone)
festival> (voice_el_diphone)
el_diphone
festival> (SayText "testing festival voices")
#
festival> (voice_kal_diphone)
kal_diphone
festival> (SayText "testing festival voices")
#
festival> (voice_upc_ca_ona_hts)
upc_ca_ona_hts
festival> (SayText "testing festival voices")

Warning: HTS_fopen: Cannot open hts/htsvoice.
aplay: main:593: bad speed value 0
#
festival> 

First two voices works correctly (spanish and english), but catalan voice 
gives an error.


As far I know, my config files are corrects, configured with festival and 
catalan 
as default module and voice:


~/.speech-dispatcher/speechd.conf:
 # Global configuration for Speech Dispatcher
 # ==
 
 # -SYSTEM OPTIONS-
 
 # CommunicationMethod specifies the method to be used by Speech Dispatcher to 
communicate with
 # its clients. Two basic methods are "unix_socket" and "inet_socket".
 #
 # unix_socket -- communication over Unix sockets represented by a file in the
 # filesystem (see SocketPath below). This method works only locally, but is
 # prefered for standard session setup, where every user runs his own instance 
of Speech
 # Dispatcher to get voice feedback on his own computer.
 #
 # inet_socket -- alternatively, you can start Speech Dispatcher on
 # a TCP port and connect to it via hostname/port. This allows for a more
 # flexible setup, where you can use Speech Dispatcher over network
 # from different machines. See also the Port and LocalhostAccessOnly
 # configuration variables.
 #
 # CommunicationMethod "unix_socket"
 
 # SocketPath is either "default" or a full path to the filesystem
 # where the driving Unix socket file should be created in case the
 # CommunicationMethod is set to "unix_socket". The default is
 # $XDG_RUNTIME_DIR/speech-dispatcher/speechd.sock where $XDG_RUNTIME_DIR
 # is the directory specified by the XDG Base Directory Specification.
 # Do not change this unless you have a reason and know what you are doing.
 
 # SocketPath "default"
 
 # The Port on which Speech Dispatcher should be available to clients if the 
"inet_socket"
 # communication method is used.
 
 # Port 6560
 
 # By default, if "inet_socket" communication method is used, the specified 
port is opened only
 # for connections comming from localhost. If LocalhostAccessOnly is set to 0 
it disables this
 # access controll. It means that the port will be accessible from all 
computers on the
 # network. If you turn off this option, please make sure you set up some 
system rules on what
 # computers are and are not allowed to access the Speech Dispatcher port.
 
 # LocalhostAccessOnly 1
 
 # -LOGGING CONFIGURATION-
 
 # The 

Processed: Re: [Pkg-alsa-devel] Bug#837590: Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed pending
Bug #837590 [src:alsa-tools] alsa-tools FTBFS on armel: gcc-6 narrowing 
conversions
Added tag(s) fixed and pending.

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

Bug#837590: [Pkg-alsa-devel] Bug#837590: Bug#837590: alsa-tools FTBFS on armel: gcc-6 narrowing conversions

[Elimar Riesebieter]

Control: tags -1 + fixed pending

* Elimar Riesebieter  [2016-09-12 18:57 +0200]:

> Control: forwarded -1 
> http://mailman.alsa-project.org/pipermail/alsa-devel/2016-September/112697.html
> 
> * Helmut Grohne  [2016-09-12 18:23 +0200]:
> 
> > Source: alsa-tools
> > Version: 1.1.0-1
> > Severity: serious
> > 
> > I noticed that alsa-tools fails to cross build from source for armel due
> > to gcc-6 narrowing conversion issues. Issues about narrowing conversions
> > are generally not cross compilation specific and reproducible natively.
> > Thus filing at RC severity. A full (cross) build log is attached. The
> > relevant excerpt is:
> > 
> > | arm-linux-gnueabi-g++ -DPACKAGE_NAME=\"hdspmixer\" 
> > -DPACKAGE_TARNAME=\"hdspmixer\" -DPACKAGE_VERSION=\"1.11\" 
> > -DPACKAGE_STRING=\"hdspmixer\ 1.11\" -DPACKAGE_BUGREPORT=\"\" 
> > -DPACKAGE_URL=\"\" -DPACKAGE=\"hdspmixer\" -DVERSION=\"1.11\" 
> > -DSTDC_HEADERS=1 -DHAVE_LIBASOUND=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  
> > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> > -Wformat -Werror=format-security   -I/usr/include/freetype2   
> > -D_THREAD_SAFE -D_REENTRANT -fno-exceptions -MT channelmap.o -MD -MP -MF 
> > .deps/channelmap.Tpo -c -o channelmap.o channelmap.cxx
> > | channelmap.cxx:59:1: error: narrowing conversion of '-1' from 'int' to 
> > 'char' inside { } [-Wnarrowing]
> > |  };
> > |  ^
> > 
> > Helmut
> 
> 
> > ___
> > Pkg-alsa-devel mailing list
> > pkg-alsa-de...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel
> 
> 
> -- 
>   Learned men are the cisterns of knowledge,
>   not the fountainheads ;-)
> 
> ___
> Pkg-alsa-devel mailing list
> pkg-alsa-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel
> 

-- 
  Do you smell something burning or is it me?

Bug#837276: python-mne: FTBFS: build-dependency not installable: mayavi2 (>= 4.4.3-1)

[Sascha Steinbiss]

Hi,

I am unable to reproduce this FTBFS in a current sid amd64 cowbuilder chroot.
See attached build log. I can see that the latest mayavi2 NMU (4.4.3-2.2) 
failed to build for amd64, but I was sure able to get 
4.4.3-2.1. 
I’m not sure I understand if this might be the reason for this failure you are 
reporting?

Thanks
Sascha

On Sat, 10 Sep 2016 09:37:14 +0200 Lucas Nussbaum  wrote:
> Source: python-mne
> Version: 0.12+dfsg-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160910 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > +--+
> > | Install package build dependencies
> >|
> > +--+
> > 
> > 
> > Setup apt archive
> > -
> > 
> > Merged Build-Depends: debhelper (>= 9), python-all, python-numpy, 
> > python-scipy, python-sphinx (>= 1.0~), python-nose, python-setuptools, 
> > python-matplotlib, python-joblib (>= 0.4.5), python-sklearn, mayavi2 (>= 
> > 4.4.3-1) | python-vtk6 | python-vtk, xvfb, xauth, libgl1-mesa-dri, 
> > python-coverage, libjs-jquery, libjs-jquery-ui, yui-compressor
> > Filtered Build-Depends: debhelper (>= 9), python-all, python-numpy, 
> > python-scipy, python-sphinx (>= 1.0~), python-nose, python-setuptools, 
> > python-matplotlib, python-joblib (>= 0.4.5), python-sklearn, mayavi2 (>= 
> > 4.4.3-1), xvfb, xauth, libgl1-mesa-dri, python-coverage, libjs-jquery, 
> > libjs-jquery-ui, yui-compressor
> > dpkg-deb: building package 'sbuild-build-depends-python-mne-dummy' in 
> > '/<>/resolver-6Al9S2/apt_archive/sbuild-build-depends-python-mne-dummy.deb'.
> > dpkg-scanpackages: warning: Packages in archive but missing from override 
> > file:
> > dpkg-scanpackages: warning:   sbuild-build-depends-python-mne-dummy
> > dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> > Ign:1 copy:/<>/resolver-6Al9S2/apt_archive ./ InRelease
> > Get:2 copy:/<>/resolver-6Al9S2/apt_archive ./ Release [957 B]
> > Ign:3 copy:/<>/resolver-6Al9S2/apt_archive ./ Release.gpg
> > Get:4 copy:/<>/resolver-6Al9S2/apt_archive ./ Sources [486 B]
> > Get:5 copy:/<>/resolver-6Al9S2/apt_archive ./ Packages [564 B]
> > Fetched 2007 B in 0s (0 B/s)
> > Reading package lists...
> > W: No sandbox user '_apt' on the system, can not drop privileges
> > Reading package lists...
> > 
> > Install python-mne build dependencies (apt-based resolver)
> > --
> > 
> > Installing build dependencies
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> > 
> > The following packages have unmet dependencies:
> >  sbuild-build-depends-python-mne-dummy : Depends: mayavi2 (>= 4.4.3-1) but 
> > it is not going to be installed
> > E: Unable to correct problems, you have held broken packages.
> > apt-get failed.
> 
> The full build log is available from:
>http://aws-logs.debian.net/2016/09/10/python-mne_0.12+dfsg-2_unstable.log
> (That DNS record was just updated. Use
> http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it

Processed: libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference

[Debian Bug Tracking System]

Processing control commands:

> affects -1 cfengine3
Bug #838105 [libssl1.1] libssl1.1: relocation error: /usr/lib/libpromises.so.3: 
symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file 
libcrypto.so.1.1 with link time reference
Added indication that 838105 affects cfengine3

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

Bug#838105: libssl1.1: relocation error: /usr/lib/libpromises.so.3: symbol X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference

[Andreas Beckmann]

Package: libssl1.1
Version: 1.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 cfengine3

Hi,

during a test with piuparts I noticed cfengine3/experimental failed to
install in experimental with a openssl symbol related problem.

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

  Selecting previously unselected package cfengine3.
  (Reading database ... 
(Reading database ... 6581 files and directories currently installed.)
  Preparing to unpack .../cfengine3_3.9.1-3_amd64.deb ...
  Unpacking cfengine3 (3.9.1-3) ...
  Setting up cfengine3 (3.9.1-3) ...
  cf-key: relocation error: /usr/lib/libpromises.so.3: symbol 
X509_get_notAfter, version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 
with link time reference
  dpkg: error processing package cfengine3 (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   cfengine3

(libpromises3 is built from src:cfengine3)

It may be sufficient to just binNMU src:cfengine3 against the
OpenSSL 1.1.0 release (it was built against 1.1.0~pre6-1).


cheers,

Andreas


cfengine3_3.9.1-3.log.gz
Description: application/gzip

Processed: raise severity for issues, because hardening-wrapper/hardening-includes is not installable

[Debian Bug Tracking System]

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

> severity 836634 serious
Bug #836634 [libmsn] libmsn: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836647 serious
Bug #836647 [postgresql-9.5] postgresql-9.5: please drop the build dependency 
on hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836651 serious
Bug #836651 [quisk] quisk: please drop the build dependency on hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836653 serious
Bug #836653 [shadow] shadow: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836753 serious
Bug #836753 [djmount] djmount: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836755 serious
Bug #836755 [gpick] gpick: please drop the build dependency on hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836757 serious
Bug #836757 [netatalk] netatalk: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836759 serious
Bug #836759 [proftpd-dfsg] proftpd-dfsg: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836760 serious
Bug #836760 [pwauth] pwauth: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836761 serious
Bug #836761 [srtp] srtp: please drop the build dependency on hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836762 serious
Bug #836762 [tor] tor: please drop the build dependency on hardening-wrapper
Severity set to 'serious' from 'important'
> severity 836617 serious
Bug #836617 [brltty] brltty: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
836617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836617
836634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836634
836647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836647
836651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836651
836653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836653
836753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836753
836755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836755
836757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836757
836759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836759
836760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836760
836761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836761
836762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 837786 in 3.21.91-2

[Debian Bug Tracking System]

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

> found 837786 3.21.91-2
Bug #837786 [mutter] mutter: Issues repainting the display on mouse movement
Marked as found in versions mutter/3.21.91-2.
> thanks
Stopping processing here.

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

Bug#837786: mutter: Issues repainting the display on mouse movement

[Roman Pavlík]

On Sat, 17 Sep 2016 09:18:45 +0200 Michael Biebl  wrote:

Am 14.09.2016 um 17:16 schrieb JWM:

> After upgrading my system this morning and restarting a new gnome-shell 
session
> (by rebooting), everything being displayed fails to repaint properly.
>
> Everytime I launch an application and try to move the window it leaves traces
> (i.e., shadows of its previous positions). The same happens on mouse hover.
>
> Also, the clock (on the top desktop) flickers constantly.  Something similar
> happens with the title bar in certain applications (e.g., vivaldi).
>
> Since the only packages upgraded were related to mutter and gnome-shell, I
> figure the one to blame is mutter.
>


Can you downgrade mutter to 3.21.91-2 (from testing), reboot and test if
the problem is reproducible?


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



Versions 3.21.92-1 and 3.21.91-2 are both affected

Versions without redraw issues are only 3.20

Downgrade to 3.20 from Debian snapshots helped:

gir1.2-mutter-3.0_3.20.3-2_amd64.deb
gnome-shell-common_3.20.3-1_all.deb
gnome-shell_3.20.3-1_amd64.deb
libmutter0h_3.20.3-2_amd64.deb
mutter-common_3.20.3-2_all.deb
mutter_3.20.3-2_amd64.deb

Bug#835581: node-es6-promise: FTBFS in testing (compile-modules shows usage help)

[Julien Puydt]

Hi,

node-ast-types 0.9.0-2 migrated to testing two weeks ago, so it should 
now be pretty trivial to check whether the problem is gone.


Can you confirm my intuition?

Thanks,

Snark on #debian-js

Bug#838080: bacula-director-pgsql: make_catalog_backup fails

[Carsten Leonhardt]

Package: bacula-director-pgsql
Version: 7.4.3+dfsg-6
Severity: serious

XXX_DBUSER_XXX is not replaced by the name of the database user in
make_catalog_backup:

user=${2:-XXX_DBUSER_XXX}

consequently, the catalog backup fails.

Bug#835185: mysql-workbench: Segfault when opening connection

[Martin Lutz]

The same problem here. On 6-Sep-2016 I updated libmysqlcppconn7v5 (sid), which 
solved the problem with Segfault. On 16-Sep-2016 I updated libreoffice (stretch) 
and the connection to the mysql server crashes again with SIGSEGV.


Here is gdbtrace.log:

warning: Currently logging to gdbtrace.log.  Turn the logging off and on to make 
the new setting effective.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe11a3700 (LWP 7867)]
[New Thread 0x7fffdd17d700 (LWP 7868)]
[New Thread 0x7fffdc97c700 (LWP 7869)]
[New Thread 0x7fffd70e8700 (LWP 7870)]
[New Thread 0x7fffd68e7700 (LWP 7871)]
[New Thread 0x7fffd5754700 (LWP 7872)]
[New Thread 0x7fffc3fff700 (LWP 7873)]
[New Thread 0x7fffc37fe700 (LWP 7874)]
[New Thread 0x7fffc2ffd700 (LWP 7877)]
[Thread 0x7fffc2ffd700 (LWP 7877) exited]
[Thread 0x7fffc37fe700 (LWP 7874) exited]
[New Thread 0x7fffc37fe700 (LWP 7878)]
[Thread 0x7fffdd17d700 (LWP 7868) exited]

Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
#0  0x in ?? ()
#1  0x7fffc09d1464 in ?? () from 
/usr/lib/libreoffice/share/extensions/mysql-connector-ooo/mysqlc.uno.so
#2  0x7fffc09d249a in ?? () from 
/usr/lib/libreoffice/share/extensions/mysql-connector-ooo/mysqlc.uno.so
#3  0x7fffc09b3769 in ?? () from 
/usr/lib/libreoffice/share/extensions/mysql-connector-ooo/mysqlc.uno.so
#4  0x7fffd4798f85 in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#5  0x7fffd479bf1d in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#6  0x7fffd47da532 in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#7  0x7fffd47daa50 in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#8  0x7fffd47dae4a in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#9  0x7fffd47db401 in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#10 0x7fffd47dbdcf in ?? () from 
/usr/lib/libreoffice/program/../program/libdbalo.so
#11 0x7fffc2421f7d in ?? () from 
/usr/lib/libreoffice/program/../program/libdbulo.so
#12 0x7fffc242373e in ?? () from 
/usr/lib/libreoffice/program/../program/libdbulo.so
#13 0x7fffc23436f0 in dbaui::OGenericUnoController::connect(rtl::OUString 
const&, rtl::OUString const&, dbtools::SQLExceptionInfo*) () from 
/usr/lib/libreoffice/program/../program/libdbulo.so
#14 0x7fffc22e039f in ?? () from 
/usr/lib/libreoffice/program/../program/libdbulo.so
#15 0x7fffc22cbfd7 in ?? () from 
/usr/lib/libreoffice/program/../program/libdbulo.so
#16 0x7fffc22feedf in ?? () from 
/usr/lib/libreoffice/program/../program/libdbulo.so

#17 0x7578c5ed in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#18 0x7578c712 in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#19 0x75791088 in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#20 0x75794c28 in SvtIconChoiceCtrl::MouseButtonDown(MouseEvent const&) 
() from /usr/lib/libreoffice/program/libmergedlo.so

#21 0x7636a8e3 in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#22 0x7636c1f6 in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#23 0x7fffdff21b2d in ?? () from 
/usr/lib/libreoffice/program/libvclplug_gtklo.so

#24 0x7fffdf9b299c in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#25 0x71483f85 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

#26 0x71495f92 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x7149e68f in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x7149efcf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

#29 0x7fffdfaca31c in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#30 0x7fffdf9b1134 in gtk_propagate_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#31 0x7fffdf9b14eb in gtk_main_do_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

#32 0x7fffdf625c9c in ?? () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#33 0x711ac697 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#34 0x711ac900 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x711ac9ac in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x7fffdff058a3 in ?? () from 
/usr/lib/libreoffice/program/libvclplug_gtklo.so
#37 0x7654e8b1 in Application::Yield() () from 
/usr/lib/libreoffice/program/libmergedlo.so
#38 0x76550d25 in Application::Execute() () from 
/usr/lib/libreoffice/program/libmergedlo.so

#39 0x7562fbfc in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#40 0x765545b6 in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#41 0x765546b2 in SVMain() () from 

Processed: Bug in xml-core which affects several packages

[Debian Bug Tracking System]

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

> affects 837620 src:w3-dtd-mathml
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837620 affects src:w3-dtd-mathml
Added indication that 837618 affects src:w3-dtd-mathml
Added indication that 837745 affects src:w3-dtd-mathml
> affects 837745 src:sgml-data
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837745 affects src:sgml-data
Added indication that 837618 affects src:sgml-data
Added indication that 837620 affects src:sgml-data
> affects 837745 src:docbook-simple
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837745 affects src:docbook-simple
Added indication that 837618 affects src:docbook-simple
Added indication that 837620 affects src:docbook-simple
> thanks
Stopping processing here.

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

Processed: Bug in xml-core which affects several packages

[Debian Bug Tracking System]

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

> reassign 837618 xml-core
Bug #837618 [src:docbook-slides] docbook-slides: FTBFS: dh_installxmlcatalogs: 
Unexpected debhelper version format
Bug reassigned from package 'src:docbook-slides' to 'xml-core'.
No longer marked as found in versions docbook-slides/3.4.0-5.
Ignoring request to alter fixed versions of bug #837618 to the same values 
previously set
> reassign 837620 xml-core
Bug #837620 [src:w3-dtd-mathml] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: 
Unexpected debhelper version format
Bug reassigned from package 'src:w3-dtd-mathml' to 'xml-core'.
No longer marked as found in versions w3-dtd-mathml/2.0.0.0-5.
Ignoring request to alter fixed versions of bug #837620 to the same values 
previously set
> affects 837618 src:docbook-slides
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837618 affects src:docbook-slides
> affects 837620 src:w3-dtd-mathml
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837620 affects src:w3-dtd-mathml
> # This one was already reassigned:
> affects 837745 src:sgml-data
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837745 affects src:sgml-data
> # And this one I discovered just today:
> affects 837745 src:docbook-simple
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837745 affects src:docbook-simple
> forcemerge 837618 837620 837745
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Removed indication that 837745 affects src:sgml-data and src:docbook-simple
Added indication that 837745 affects src:docbook-slides
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Marked as found in versions xml-core/0.13+nmu2.
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Removed indication that 837620 affects src:w3-dtd-mathml
Added indication that 837620 affects src:docbook-slides
Marked as found in versions xml-core/0.13+nmu2.
Merged 837618 837620 837745
> thanks
Stopping processing here.

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

Bug#835992: [Pkg-zfsonlinux-devel] Bug#835992: 835992

[Benjamin Eikel]

Dear Petter,

the build failure reported here is independent of the dkms problem in #836578. 
I applied the suggested patch from #836578, but the build still fails with 
Linux 4.7 (see attached /var/lib/dkms/spl/0.6.5.7/build/make.log). The changes 
of ZFS v0.6.5.8 [1] contain the compatibility with Linux 4.7. So maybe the 
easiest solution is packaging the new upstream release.

Kind regards
Benjamin

[1] https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.8DKMS make.log for spl-0.6.5.7 for kernel 4.7.0-1-amd64 (x86_64)
Sa 17. Sep 09:20:32 CEST 2016
make  all-recursive
make[1]: Verzeichnis „/var/lib/dkms/spl/0.6.5.7/build“ wird betreten
Making all in module
make[2]: Verzeichnis „/var/lib/dkms/spl/0.6.5.7/build/module“ wird betreten
make -C /lib/modules/4.7.0-1-amd64/build SUBDIRS=`pwd`  O=/lib/modules/4.7.0-1-amd64/build CONFIG_SPL=m modules
make[3]: Verzeichnis „/usr/src/linux-headers-4.7.0-1-amd64“ wird betreten
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-ctl.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-proc.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-kmem.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-taskq.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-random.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-kmem.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vmem.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-kmem-cache.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-mutex.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-thread.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-taskq.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-condvar.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-rwlock.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-thread.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-err.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-rwlock.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-time.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-kobj.o
In file included from /var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c:31:0:
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c: In function ‘spl_kern_path_locked’:
/var/lib/dkms/spl/0.6.5.7/build/include/linux/file_compat.h:79:45: error: ‘struct inode’ has no member named ‘i_mutex’
 #define spl_inode_lock(ip)  mutex_lock(&(ip)->i_mutex)
 ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c:356:2: note: in expansion of macro ‘spl_inode_lock’
  spl_inode_lock(parent.dentry->d_inode);
  ^
/var/lib/dkms/spl/0.6.5.7/build/include/linux/file_compat.h:80:49: error: ‘struct inode’ has no member named ‘i_mutex’
 #define spl_inode_unlock(ip)  mutex_unlock(&(ip)->i_mutex)
 ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c:360:3: note: in expansion of macro ‘spl_inode_unlock’
   spl_inode_unlock(parent.dentry->d_inode);
   ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c: In function ‘vn_remove’:
/var/lib/dkms/spl/0.6.5.7/build/include/linux/file_compat.h:80:49: error: ‘struct inode’ has no member named ‘i_mutex’
 #define spl_inode_unlock(ip)  mutex_unlock(&(ip)->i_mutex)
 ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c:408:2: note: in expansion of macro ‘spl_inode_unlock’
  spl_inode_unlock(parent.dentry->d_inode);
  ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c: In function ‘vn_rename’:
/var/lib/dkms/spl/0.6.5.7/build/include/linux/file_compat.h:80:49: error: ‘struct inode’ has no member named ‘i_mutex’
 #define spl_inode_unlock(ip)  mutex_unlock(&(ip)->i_mutex)
 ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c:438:2: note: in expansion of macro ‘spl_inode_unlock’
  spl_inode_unlock(old_parent.dentry->d_inode);
  ^
/var/lib/dkms/spl/0.6.5.7/build/include/linux/file_compat.h:80:49: error: ‘struct inode’ has no member named ‘i_mutex’
 #define spl_inode_unlock(ip)  mutex_unlock(&(ip)->i_mutex)
 ^
/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.c:446:2: note: in expansion of macro ‘spl_inode_unlock’
  spl_inode_unlock(new_parent.dentry->d_inode);
  ^
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-vnode.o
/usr/src/linux-headers-4.7.0-1-common/scripts/Makefile.build:294: die Regel für Ziel „/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.o“ scheiterte
make[7]: *** [/var/lib/dkms/spl/0.6.5.7/build/module/spl/spl-vnode.o] Fehler 1
make[7]: *** Es wird auf noch nicht beendete Prozesse gewartet...
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-kobj.o
  CC [M]  /var/lib/dkms/spl/0.6.5.7/build/module/splat/splat-atomic.o
  CC [M]  

Bug#837994: [debian-mysql] Bug#837994: Bug#837994: mysql-5.5: FTBFS on armhf

[Salvatore Bonaccorso]

Control: severity -1 important

Hi Lars, hi all,

It finally worked on another buildd, namely henze,
https://db.debian.org/machines.cgi?host=henze

I'm lowering the severity to important since we have now all builds.
But before eventually closing it would be nice if we can get an idea
why it failed on the other attempts on the other buildds.

Regards,
Salvatore

Processed: Re: [debian-mysql] Bug#837994: Bug#837994: mysql-5.5: FTBFS on armhf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #837994 [src:mysql-5.5] mysql-5.5: FTBFS on armhf
Severity set to 'important' from 'serious'

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

Bug#830609: marked as done (python-structlog: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 08:19:22 +
with message-id 
and subject line Bug#830609: fixed in python-structlog 16.1.0-1
has caused the Debian Bug report #830609,
regarding python-structlog: accesses the internet during build
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.)


-- 
830609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-structlog
Version: 16.0.0-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst python-structlog builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 9a053c9fe99a.44824 > dnscache.uct.ac.za.domain: 6034+ A? 
docs.python.org. (33)
  00:00:00.48 IP 9a053c9fe99a.44824 > dnscache.uct.ac.za.domain: 13621+ 
? docs.python.org. (33)
  00:00:00.325809 IP dnscache.uct.ac.za.domain > 9a053c9fe99a.44824: 6034 3/4/4 
CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A 
151.101.16.223 (259)
  00:00:00.326357 IP dnscache.uct.ac.za.domain > 9a053c9fe99a.44824: 13621 
2/1/0 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net. (178)
  00:00:00.326667 IP 9a053c9fe99a.50748 > 151.101.16.223.https: Flags [S], seq 
2467954815, win 29200, options [mss 1460,sackOK,TS val 110247693 ecr 
0,nop,wscale 7], length 0
  00:00:00.476336 IP 151.101.16.223.https > 9a053c9fe99a.50748: Flags [S.], seq 
1530825957, ack 2467954816, win 28560, options [mss 1440,sackOK,TS val 
1180086082 ecr 110247693,nop,wscale 9], length 0

  [..]

This appears to be caused by (at least) Sphinx's intersphinx mapping extension.
Please see #830186 for more information, including suggestions on how to fix it.

The full build log (including tcpdump output) is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


python-structlog.16.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-structlog
Source-Version: 16.1.0-1

We believe that the bug you reported is fixed in the latest version of
python-structlog, 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 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated python-structlog 
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: Sat, 17 Sep 2016 09:48:23 +0200
Source: python-structlog
Binary: python-structlog python3-structlog python-structlog-doc
Architecture: source all
Version: 16.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Vincent Bernat 
Description:
 python-structlog - structured logging for Python (2.x)
 python-structlog-doc - structured logging for Python (common documentation)
 python3-structlog - structured logging for Python (3.x)
Closes: 830609
Changes:
 python-structlog (16.1.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/control: add myself to uploaders.
   * d/control: bump Standards-Version.
   * d/control: make short descriptions unique.
   * d/control: update Vcs-* fields to use HTTPS.
   * d/rules: prevent network access by defining https_proxy. Closes: #830609.
Checksums-Sha1:
 69056f56b4384d654eb48af2b9cde103759d0544 2440 python-structlog_16.1.0-1.dsc
 f9a4757549c5bfa69a8f06d35b268b4a77409b58 153293 
python-structlog_16.1.0.orig.tar.gz
 653852d21a8da6be3712d750607a08a09913b592 31876 
python-structlog_16.1.0-1.debian.tar.xz
 cf78d3a84a8dc17d6da69335c8a8749762a80c74 142666 
python-structlog-doc_16.1.0-1_all.deb
 40bc877469a6c021a336dfce61eb9d0523266493 20784 
python-structlog_16.1.0-1_all.deb
 e69145ac0ae1b211dbe8f3f6c39524b09f23690d 20844 
python3-structlog_16.1.0-1_all.deb
Checksums-Sha256:
 407f6af09ef32781199508b90a5337b1654aeafaf91422fbfdd86cb26011f038 2440 
python-structlog_16.1.0-1.dsc
 

Processed (with 2 errors): merge bugs

[Debian Bug Tracking System]

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

> reassign 837227 src:rebar
Bug #837227 [rebar] neotoma: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837227 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837227 to the same values 
previously set
> reassign 837277 src:rebar
Bug #837277 [rebar] erlang-meck: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837277 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837277 to the same values 
previously set
> reassign 837275 src:rebar
Bug #837275 [rebar] erlang-jiffy: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837275 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837275 to the same values 
previously set
> reassign 837259 src:rebar
Bug #837259 [rebar] erlang-getopt: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837259 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837259 to the same values 
previously set
> reassign 837252 src:rebar
Bug #837252 [rebar] erlang-folsom: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837252 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837252 to the same values 
previously set
> reassign 837283 src:rebar
Bug #837283 [rebar] erlang-cuttlefish: FTBFS: Uncaught error in rebar_core: 
{'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837283 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837283 to the same values 
previously set
> reassign 837230 src:rebar
Bug #837230 [rebar] erlang-cowlib: FTBFS: src/cow_multipart.erl:427: 
crypto:rand_bytes/1 is deprecated and will be removed in a future release; use 
crypto:strong_rand_bytes/1
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837230 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837230 to the same values 
previously set
> reassign 837231 src:rebar
Bug #837231 [rebar] erlang-cherly: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837231 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837231 to the same values 
previously set
> reassign 837286 src:rebar
Bug #837286 [rebar] erlang-bitcask: FTBFS: Uncaught error in rebar_core: 
{'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837286 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837286 to the same values 
previously set
> reassign 837250 src:rebar
Bug #837250 [rebar] erlang-bear: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'rebar' to 'src:rebar'.
Ignoring request to alter found versions of bug #837250 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837250 to the same values 
previously set
> merge 837234 837227 837277 837275 837259 837252 837283  837231 837286
Bug #837234 {Done: Nobuhiro Iwamatsu } [src:rebar] rebar: 
FTBFS: Uncaught error in rebar_core: {'EXIT',
Unable to merge bugs because:
done of #837227 is '' not 'Nobuhiro Iwamatsu '
done of #837277 is '' not 'Nobuhiro Iwamatsu '
done of #837275 is '' not 'Nobuhiro Iwamatsu '
done of #837286 is '' not 'Nobuhiro Iwamatsu '
done of #837259 is '' not 'Nobuhiro Iwamatsu '
done of #837252 is '' not 'Nobuhiro Iwamatsu '
done of #837283 is '' not 'Nobuhiro Iwamatsu '
done of #837231 is '' not 'Nobuhiro Iwamatsu '
Failed to merge 837234: Did not alter merged bugs.

> merge 837234 837250 837230
Failed to merge 837234: failed to get lock on 
/org/bugs.debian.org/spool/lock/837234 -- Unable to lock 
/org/bugs.debian.org/spool/lock/837234 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/837234 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/837234 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/837234 Resource temporarily 
unavailable at 

Bug#830609: marked as pending

[Vincent Bernat]

tag 830609 pending
thanks

Hello,

Bug #830609 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://git.debian.org/?p=python-modules/packages/python-structlog.git;a=commitdiff;h=f5a148c

---
commit f5a148c97a4d2b5f050f09970a6258f0a0b8b3ff
Author: Vincent Bernat 
Date:   Sat Sep 17 09:48:28 2016 +0200

d/rules: prevent network access by defining https_proxy

diff --git a/debian/changelog b/debian/changelog
index 9ed029b..5954e5b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,8 +3,9 @@ python-structlog (16.1.0-1) UNRELEASED; urgency=medium
   * New upstream release.
   * d/control: add myself to uploaders.
   * d/control: bump Standards-Version.
+  * d/rules: prevent network access by defining https_proxy. Closes: #830609.
 
- -- Vincent Bernat   Sat, 17 Sep 2016 09:41:11 +0200
+ -- Vincent Bernat   Sat, 17 Sep 2016 09:48:23 +0200
 
 python-structlog (16.0.0-1) unstable; urgency=medium
 

Processed: Bug#830609 marked as pending

[Debian Bug Tracking System]

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

> tag 830609 pending
Bug #830609 [src:python-structlog] python-structlog: accesses the internet 
during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837942: gtk-doc-tools: Missing dependency on pkg-config

[Michael Biebl]

Am 15.09.2016 um 19:58 schrieb Andreas Metzler:
> Package: gtk-doc-tools
> Version: 1.25-4
> Severity: serious
> 
> gtk-doc-tools in experimental is lacking a dependency on pkg-config,
> GTK_DOC_CHECK will fail if it is missing.
> 
> ---
> AC_DEFUN([GTK_DOC_CHECK],
> [
>   AC_REQUIRE([PKG_PROG_PKG_CONFIG])
> ---
> 
> This only applies to experimental, sid fullfils this via the gnome-core
> dependency.

This was requested in the past in #260930:

gtk-doc (1.3-1.1) unstable; urgency=low

...
  * Recommend a sensible version of pkg-config, since gtk-doc-using
packages will need it, but don't make this a Depends, since
gtk-doc-tools itself doesn't require it.  (Closes: #260930)


Admittedly, a Recommends is not particularly helpful when it concerns
Build-Depends, as buildds won't consider it.

Strictly speaking, the changelog is correct. Using gtk-doc-tools doesn't
necessarily require using the GTK_DOC_CHECK macro.
On the other hand, basically every package I've seen using gtk-doc-tools
does actually use this macro.
So bumping Recommends: gtk-doc-tools to Depends: gtk-doc-tools is
probably justified.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#808055: marked as done (php-pinba: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null in /usr/share/php/PEAR/Command/Install.php on line 747)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 09:58:06 +0200
with message-id 
and subject line Re: Bug#808055: php-pinba: FTBFS: PHP Fatal error:  Call to a 
member function getFilelist() on null in 
/usr/share/php/PEAR/Command/Install.php on line 747
has caused the Debian Bug report #808055,
regarding php-pinba: FTBFS: PHP Fatal error:  Call to a member function 
getFilelist() on null in /usr/share/php/PEAR/Command/Install.php on line 747
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.)


-- 
808055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-pinba
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

php-pinba fails to build from source in unstable/amd64:

  [..]

 dh_auto_install -O--buildsystem=phppear
/usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php5-pinba -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P 
/home/lamby/temp/cdt.20151215162945.jSzid3ytVO/php-pinba-1.0.0/debian/php5-pinba
 --nobuild ./pinba-1.0.0/package.xml
  PHP Fatal error:  Call to a member function getFilelist() on null in 
/usr/share/php/PEAR/Command/Install.php on line 747
  dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php5-pinba -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P 
/home/lamby/temp/cdt.20151215162945.jSzid3ytVO/php-pinba-1.0.0/debian/php5-pinba
 --nobuild ./pinba-1.0.0/package.xml returned exit code 255
  debian/rules:8: recipe for target 'binary' failed
  make: *** [binary] Error 10

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


php-pinba.1.0.0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.1.0-1

<#secure method=pgpmime mode=sign>
 ❦ 15 décembre 2015 17:31 CET, Chris Lamb  :

> php-pinba fails to build from source in unstable/amd64:
>
>   [..]
>
>  dh_auto_install -O--buildsystem=phppear
>   /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
> include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
> php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
> doc_dir=/usr/share/doc/php5-pinba -d test_dir=/usr/share/php/tests install 
> --offline --nodeps -P 
> /home/lamby/temp/cdt.20151215162945.jSzid3ytVO/php-pinba-1.0.0/debian/php5-pinba
>  --nobuild ./pinba-1.0.0/package.xml
>   PHP Fatal error:  Call to a member function getFilelist() on null in 
> /usr/share/php/PEAR/Command/Install.php on line 747
>   dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
> include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
> php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
> doc_dir=/usr/share/doc/php5-pinba -d test_dir=/usr/share/php/tests install 
> --offline --nodeps -P 
> /home/lamby/temp/cdt.20151215162945.jSzid3ytVO/php-pinba-1.0.0/debian/php5-pinba
>  --nobuild ./pinba-1.0.0/package.xml returned exit code 255
>   debian/rules:8: recipe for target 'binary' failed
>   make: *** [binary] Error 10
>
>   [..]
>
> The full build log is attached.

It was fixed by bug 805222 in php-pear. I mark this one fixed in the
just-uploaded version of php-pinba.
-- 
Each module should do one thing well.
- The Elements of Programming Style (Kernighan & Plauger)--- End Message ---

Processed (with 2 errors): merge bugs

[Debian Bug Tracking System]

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

> reassign 837227 rebar
Bug #837227 [src:neotoma] neotoma: FTBFS: Uncaught error in rebar_core: {'EXIT',
Bug reassigned from package 'src:neotoma' to 'rebar'.
No longer marked as found in versions neotoma/1.7.3+dfsg-1.
Ignoring request to alter fixed versions of bug #837227 to the same values 
previously set
> reassign 837277 rebar
Bug #837277 [src:erlang-meck] erlang-meck: FTBFS: Uncaught error in rebar_core: 
{'EXIT',
Bug reassigned from package 'src:erlang-meck' to 'rebar'.
No longer marked as found in versions erlang-meck/0.8.4+dfsg-1.
Ignoring request to alter fixed versions of bug #837277 to the same values 
previously set
> reassign 837275 rebar
Bug #837275 [src:erlang-jiffy] erlang-jiffy: FTBFS: Uncaught error in 
rebar_core: {'EXIT',
Bug reassigned from package 'src:erlang-jiffy' to 'rebar'.
No longer marked as found in versions erlang-jiffy/0.14.6+dfsg-1.
Ignoring request to alter fixed versions of bug #837275 to the same values 
previously set
> reassign 837259 rebar
Bug #837259 [src:erlang-getopt] erlang-getopt: FTBFS: Uncaught error in 
rebar_core: {'EXIT',
Bug reassigned from package 'src:erlang-getopt' to 'rebar'.
No longer marked as found in versions erlang-getopt/0.8.2+dfsg-1.
Ignoring request to alter fixed versions of bug #837259 to the same values 
previously set
> reassign 837252 rebar
Bug #837252 [src:erlang-folsom] erlang-folsom: FTBFS: Uncaught error in 
rebar_core: {'EXIT',
Bug reassigned from package 'src:erlang-folsom' to 'rebar'.
No longer marked as found in versions erlang-folsom/0.8.2+dfsg-1.
Ignoring request to alter fixed versions of bug #837252 to the same values 
previously set
> reassign 837283 rebar
Bug #837283 [src:erlang-cuttlefish] erlang-cuttlefish: FTBFS: Uncaught error in 
rebar_core: {'EXIT',
Bug reassigned from package 'src:erlang-cuttlefish' to 'rebar'.
No longer marked as found in versions erlang-cuttlefish/2.0.7+dfsg-1.
Ignoring request to alter fixed versions of bug #837283 to the same values 
previously set
> reassign 837230 rebar
Bug #837230 [src:erlang-cowlib] erlang-cowlib: FTBFS: 
src/cow_multipart.erl:427: crypto:rand_bytes/1 is deprecated and will be 
removed in a future release; use crypto:strong_rand_bytes/1
Bug reassigned from package 'src:erlang-cowlib' to 'rebar'.
No longer marked as found in versions erlang-cowlib/1.3.0-1.
Ignoring request to alter fixed versions of bug #837230 to the same values 
previously set
> reassign 837231 rebar
Bug #837231 [src:erlang-cherly] erlang-cherly: FTBFS: Uncaught error in 
rebar_core: {'EXIT',
Bug reassigned from package 'src:erlang-cherly' to 'rebar'.
No longer marked as found in versions erlang-cherly/0.12.8+dfsg-5.
Ignoring request to alter fixed versions of bug #837231 to the same values 
previously set
> reassign 837286 rebar
Bug #837286 [src:erlang-bitcask] erlang-bitcask: FTBFS: Uncaught error in 
rebar_core: {'EXIT',
Bug reassigned from package 'src:erlang-bitcask' to 'rebar'.
No longer marked as found in versions erlang-bitcask/2.0.2+dfsg-1.
Ignoring request to alter fixed versions of bug #837286 to the same values 
previously set
> reassign 837250 rebar
Bug #837250 [src:erlang-bear] erlang-bear: FTBFS: Uncaught error in rebar_core: 
{'EXIT',
Bug reassigned from package 'src:erlang-bear' to 'rebar'.
No longer marked as found in versions erlang-bear/0.8.2+dfsg-1.
Ignoring request to alter fixed versions of bug #837250 to the same values 
previously set
> merge 837234 837227 837277 837275 837259 837252 837283  837231 837286
Bug #837234 [src:rebar] rebar: FTBFS: Uncaught error in rebar_core: {'EXIT',
Unable to merge bugs because:
package of #837286 is 'rebar' not 'src:rebar'
package of #837277 is 'rebar' not 'src:rebar'
package of #837259 is 'rebar' not 'src:rebar'
package of #837252 is 'rebar' not 'src:rebar'
package of #837227 is 'rebar' not 'src:rebar'
package of #837283 is 'rebar' not 'src:rebar'
package of #837231 is 'rebar' not 'src:rebar'
package of #837275 is 'rebar' not 'src:rebar'
Failed to merge 837234: Did not alter merged bugs.

> 837250 837230
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837227
837230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837230
837231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837231
837234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837234
837250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837250
837252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837252
837259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837259
837275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837275
837277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837277
837283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837283
837286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837234: marked as done (rebar: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Sat, 17 Sep 2016 07:48:50 +
with message-id 
and subject line Bug#837234: fixed in rebar 2.6.4-1
has caused the Debian Bug report #837234,
regarding rebar: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rebar
Version: 2.6.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./bootstrap
> Recompile: src/rebar
> Recompile: src/rebar_abnfc_compiler
> Recompile: src/rebar_app_utils
> Recompile: src/rebar_appups
> Recompile: src/rebar_asn1_compiler
> Recompile: src/rebar_base_compiler
> Recompile: src/rebar_cleaner
> Recompile: src/rebar_config
> Recompile: src/rebar_core
> Recompile: src/rebar_cover_utils
> Recompile: src/rebar_ct
> Recompile: src/rebar_deps
> Recompile: src/rebar_dia_compiler
> Recompile: src/rebar_dialyzer
> Recompile: src/rebar_edoc
> Recompile: src/rebar_erlc_compiler
> Recompile: src/rebar_erlydtl_compiler
> Recompile: src/rebar_escripter
> Recompile: src/rebar_eunit
> src/rebar_eunit.erl:296: Warning: random:seed/3: the 'random' module is 
> deprecated; use the 'rand' module instead
> src/rebar_eunit.erl:298: Warning: random:uniform/0: the 'random' module is 
> deprecated; use the 'rand' module instead
> Recompile: src/rebar_file_utils
> Recompile: src/rebar_getopt
> Recompile: src/rebar_lfe_compiler
> Recompile: src/rebar_log
> Recompile: src/rebar_metacmds
> Recompile: src/rebar_mustache
> Recompile: src/rebar_neotoma_compiler
> Recompile: src/rebar_otp_app
> Recompile: src/rebar_otp_appup
> Recompile: src/rebar_port_compiler
> Recompile: src/rebar_proto_compiler
> Recompile: src/rebar_proto_gpb_compiler
> Recompile: src/rebar_protobuffs_compiler
> Recompile: src/rebar_qc
> Recompile: src/rebar_rel_utils
> Recompile: src/rebar_reltool
> Recompile: src/rebar_require_vsn
> Recompile: src/rebar_shell
> Recompile: src/rebar_subdirs
> Recompile: src/rebar_templater
> Recompile: src/rebar_upgrade
> Recompile: src/rebar_utils
> Recompile: src/rebar_xref
> Recompile: src/rmemo
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {erl_eval,do_apply,6,
>   [{file,"erl_eval.erl"},{line,670}]},
>  {escript,eval_exprs,5,
>   [{file,"escript.erl"},{line,871}]},
>  {erl_eval,local_func,6,
>   [{file,"erl_eval.erl"},{line,557}]},
>  {escript,interpret,4,
>   [{file,"escript.erl"},{line,787}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]}]}}
> Makefile:9: recipe for target 'all' failed
> make[1]: *** [all] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/rebar_2.6.2-2_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rebar
Source-Version: 2.6.4-1

We believe that the bug you reported is fixed in the latest version of
rebar, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if 

Bug#837786: mutter: Issues repainting the display on mouse movement

[Michael Biebl]

Am 14.09.2016 um 17:16 schrieb JWM:

> After upgrading my system this morning and restarting a new gnome-shell 
> session
> (by rebooting), everything being displayed fails to repaint properly.
> 
> Everytime I launch an application and try to move the window it leaves traces
> (i.e., shadows of its previous positions). The same happens on mouse hover.
> 
> Also, the clock (on the top desktop) flickers constantly.  Something similar
> happens with the title bar in certain applications (e.g., vivaldi).
> 
> Since the only packages upgraded were related to mutter and gnome-shell, I
> figure the one to blame is mutter.
> 


Can you downgrade mutter to 3.21.91-2 (from testing), reboot and test if
the problem is reproducible?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#838050: gnome-shell: gdm doesn't start due to a problem with gnome-shell crashing in libwacom2

[Michael Biebl]

Am 17.09.2016 um 01:09 schrieb Erik Tews:

> After startup, gdm doesn't show up and just shows a grey screen. Looking at 
> syslog reveals the reason:
> 
> syslog:Sep 16 23:27:25 matte kernel: [  172.983123] gnome-shell[3206]: 
> segfault 
> at 10 ip 7f8e7c85d6c4 sp 7ffd151d0a80 error 4 in 
> libwacom.so.2.4.6[7f8e7
> c85a000+9000]
> 
> Since I haven't updated libwacom2 in the last 2 weeks, but gnome-shell was 
> recently updated, I assume this is due to a problem in gnome-shell.
> 
> There is also a temporary fix, just run: rmmod wacom, and then restart gdm, 
> and you can use it again, of course without the touchscreen.
> 
> Unfortunately, in upstream, I cannot see any kind of commit between 3.21.92 
> and 3.21.91 that might cause such a problem.

Can you downgrade gnome-shell (and gnome-shell-common) to version
3.21.91-2 (from testing), reboot and test if the problem is still
reproducible?

If not, does downgrading libmutter0i, mutter-common, mutter to 3.21.91-2
fix the problem?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): merge bugs

[Debian Bug Tracking System]

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

> merge 837234 837227 837277 837275 837259 837252 837283  837231 837286 837250
Bug #837234 [src:rebar] rebar: FTBFS: Uncaught error in rebar_core: {'EXIT',
Unable to merge bugs because:
package of #837227 is 'src:neotoma' not 'src:rebar'
package of #837283 is 'src:erlang-cuttlefish' not 'src:rebar'
package of #837277 is 'src:erlang-meck' not 'src:rebar'
package of #837286 is 'src:erlang-bitcask' not 'src:rebar'
package of #837252 is 'src:erlang-folsom' not 'src:rebar'
package of #837275 is 'src:erlang-jiffy' not 'src:rebar'
package of #837250 is 'src:erlang-bear' not 'src:rebar'
package of #837259 is 'src:erlang-getopt' not 'src:rebar'
package of #837231 is 'src:erlang-cherly' not 'src:rebar'
Failed to merge 837234: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837227
837231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837231
837234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837234
837250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837250
837252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837252
837259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837259
837275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837275
837277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837277
837283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837283
837286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#838047: Confirmed: breaks *all* tablets

[Timo Aaltonen]

On 17.09.2016 02:47, a.t.chadw...@gmail.com wrote:
> Confirmed. This bug breaks all graphics tablets in GNOME (at least). It
> is not specific to the driver. See the attached logs.
> 
> Symptoms: when a graphics tablet is plugged in, within a few seconds the
> running X session terminates. Examining the logs reveals repeated
> segfaults from gnome-shell caused by libwacom2; the repetition is
> classed as the session respawning too fast by gnome-session, which gives
> up in disgust.
> 
> (As originally reported, sessions break with a blank screen if the
> tablet is plugged in at session start too.)
> 
> Affected hardware: all the tablets I own, namely:
> 
> * Genius i405x (evdev driver, horribly broken)
> * Huion H610PRO (libinput, normally works well)
> * Wacom Intuos5 M (wacom, normally works perfectly)
> 
> Expected behaviour: I would expect no segfaults which kill X when
> plugging in my graphics tablets.
> 
> I am using libwacom2 0.19-1, gnome-shell 3.21.91-2, and
> gnome-settings-daemon 3.21.92.1-1.
> 
> Libwacom 0.22 has been released upstream, and may be necessary for this
> version of GNOME. Please can that be tried? Libwacom mismatches have
> killed tablet support in the past

sounds like gnome dependencies are wrong then.. anyway, 0.22-1 uploaded,
please test


-- 
t