Bug#811720: marked as done (jackd2: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Mon, 25 Jul 2016 04:27:49 +
with message-id 
and subject line Bug#811720: fixed in jackd2 1.9.10+20150825git1ed50c92~dfsg-2
has caused the Debian Bug report #811720,
regarding jackd2: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jackd2
Version: 1.9.10+20150825git1ed50c92~dfsg-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> >/jackd2-1.9.10+20150825git1ed50c92~dfsg/build', 
> '-I/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg', '-DHAVE_DOXYGEN=0', 
> '-DHAVE_ALSA=1', '-DHAVE_FIREWIRE=1', '-DHAVE_FREEBOB=0', '-DHAVE_IIO=0', 
> '-DHAVE_PORTAUDIO=0', '-DHAVE_WINMME=0', '-DHAVE_CELT_API_0_11=0', 
> '-DHAVE_CELT_API_0_8=0', '-DHAVE_CELT_API_0_7=0', '-DHAVE_CELT_API_0_5=0', 
> '-DHAVE_CELT=0', '-DHAVE_OPUS=0', '-DHAVE_SAMPLERATE=1', '-DHAVE_SNDFILE=1', 
> '-DHAVE_READLINE=1', '-DHAVE_PPOLL=1', '-DUSE_CLASSIC_AUTOLAUNCH=1', 
> '-DCLIENT_NUM=64', '-DPORT_NUM_FOR_CLIENT=768', 
> '-DADDON_DIR="/usr/lib/x86_64-linux-gnu/jack"', '-DJACK_LOCATION="/usr/bin"', 
> '-DUSE_POSIX_SHM=1', '-DJACKMP=1', '-DJACK_DBUS=1', '-DHAVE_CONFIG_H', 
> '-DSERVER_SIDE', '-DHAVE_PPOLL', '-DHAVE_TIMERFD', '-DHAVE_SAMPLERATE=1', 
> '../common/JackNetOneDriver.cpp', '-c', '-o', 
> '/<>/jackd2-1.9.10+20150825git1ed50c92~dfsg/build/common/JackNetOneDriver.cpp.8.o']
> :0:0: warning: "HAVE_OPUS" redefined
> 
> :0:0: note: this is the location of the previous definition
> 
> :0:0: warning: "HAVE_OPUS" redefined
> 
> :0:0: note: this is the location of the previous definition
> ../tests/iodelay.cpp:170:49: error: narrowing conversion of '-1' from 'int' 
> to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
>  jack_latency_range_t   capture_latency = {-1, -1};
>  ^
> 
> ../tests/iodelay.cpp:170:49: error: narrowing conversion of '-1' from 'int' 
> to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
> ../tests/iodelay.cpp:171:50: error: narrowing conversion of '-1' from 'int' 
> to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
>  jack_latency_range_t   playback_latency = {-1, -1};
>   ^
> 
> ../tests/iodelay.cpp:171:50: error: narrowing conversion of '-1' from 'int' 
> to 'jack_nframes_t {aka unsigned int}' inside { } [-Wnarrowing]
> 
> :0:0: warning: "HAVE_OPUS" redefined

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: jackd2
Source-Version: 1.9.10+20150825git1ed50c92~dfsg-2

We believe that the bug you reported is fixed in the latest version of
jackd2, 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.
Felipe Sateler  (supplier of updated jackd2 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, 24 Jul 2016 23:18:31 -0400
Source: jackd2
Binary: jackd2 libjack-jackd2-0 jackd2-firewire libjack-jackd2-dev
Architecture: source
Version: 1.9.10+20150825git1ed50c92~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 jackd2 - JACK Audio Connection Kit (server and example clients)
 jackd2-firewire - JACK Audio Connection Kit (FFADO and FreeBoB backends)
 

Bug#832125: marked as done (chromium: Chromium immediately crashes)

[Debian Bug Tracking System]

Your message dated Mon, 25 Jul 2016 04:23:36 +
with message-id 
and subject line Bug#832125: fixed in chromium-browser 52.0.2743.82-2
has caused the Debian Bug report #832125,
regarding chromium: Chromium immediately crashes
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.)


-- 
832125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 51.0.2704.79-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I started chromium. It crashed immediately with SIGSEGV. dmesg(1) tells me:

--- snib ---
[153066.919129] chromium[15304]: segfault at 10 ip aa110788 sp bfb16160 error 4 
in libnettle.so.4.7[aa0ee000+33000]
--- snab ---

I expected chromium to not crash; it has worked fine a lot of times before.

Attached is strace output for the crash.

-- System Information:
Debian Release: 8.5
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.14.0-1
ii  libavcodec57 7:3.1.1-2
ii  libavformat577:3.1.1-2
ii  libavutil55  7:3.1.1-2
ii  libc62.19-18+deb8u4
ii  libcairo21.14.0-2.1+deb8u1
ii  libcups2 2.1.4-4
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.1.0-6+deb8u3
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3+deb8u1
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.48.1-2
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-3+deb8u1
ii  libharfbuzz0b0.9.35-2
ii  libjpeg62-turbo  1:1.3.1-12
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.3.1-1.1
ii  libspeechd2  0.8-7
ii  libstdc++6   6.1.1-9
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxml2  2.9.1+dfsg1-5+deb8u2
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+deb8u1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+2
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1.07.4-1

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information
execve("/usr/bin/chromium", ["chromium"], [/* 54 vars */]) = 0
brk(NULL)   = 0xb80f9000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb773
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=99503, ...}) = 0
mmap2(NULL, 99503, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7717000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\233\1\0004\0\0\0"..., 512) 
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1750780, ...}) = 0
mmap2(NULL, 1755772, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb756a000
mmap2(0xb7711000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a7000) = 0xb7711000
mmap2(0xb7714000, 10876, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7714000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7569000
set_thread_area({entry_number:-1, base_addr:0xb7569940, limit:1048575, 
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, 
useable:1}) = 0 (entry_number:6)
mprotect(0xb7711000, 8192, PROT_READ)   = 0
mprotect(0xb7773000, 4096, PROT_READ)   = 0
mprotect(0xb7754000, 4096, PROT_READ)   = 0
munmap(0xb7717000, 99503)   = 

Bug#811720: marked as pending

[Felipe Sateler]

tag 811720 pending
thanks

Hello,

Bug #811720 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=pkg-multimedia/jackd2.git;a=commitdiff;h=c173ba0

---
commit c173ba049f2e8b72beb573a4b7254128a1b0f06f
Author: Felipe Sateler 
Date:   Sun Jul 24 23:21:07 2016 -0400

Release

diff --git a/debian/changelog b/debian/changelog
index 453358b..846a4b1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+jackd2 (1.9.10+20150825git1ed50c92~dfsg-2) unstable; urgency=medium
+
+  * Team upload.
+  * Fix FTBFS with gcc 6. Closes: #811720
+
+ -- Felipe Sateler   Sun, 24 Jul 2016 23:18:31 -0400
+
 jackd2 (1.9.10+20150825git1ed50c92~dfsg-1) unstable; urgency=low
 
   * Make builds reproducible (Closes: #796807)

Processed: Bug#811720 marked as pending

[Debian Bug Tracking System]

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

> tag 811720 pending
Bug #811720 [jackd2] jackd2: FTBFS with GCC 6: narrowing conversion
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#832401: Mouse cursor disappeared when long-time playing

[M0xkLurk3r]

Package: src:vlc
Version: 2.2.4-2
Severity: grave

I know that VLC will hid the cursor when it stand still on the playback
interface during clips playing, but my problem is the cursor did not appears
again when I try to wake my mouse up. but in the meantime the mouse seems alive
indeed (I can move the cursor outside, even right-click on the playback could
still triggered the playback menu)

this bug always reproduce after a certain amount of time clip play. exactly
this is not a serious bug, but it's really hard to control my mouse without the
cursor ...



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

Kernel: Linux 4.6.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)

Versions of packages vlc depends on:
ii  dpkg1.18.9
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libc6   2.23-1
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.6-1+b1
ii  libegl1-mesa [libegl1-x11]  11.2.2-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreetype62.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:6.1.1-9
ii  libgl1-mesa-glx [libgl1]11.2.2-1
ii  libgles1-mesa [libgles1]11.2.2-1
ii  libgles2-mesa [libgles2]11.2.2-1
ii  libglib2.0-02.48.1-2
ii  libpulse0   9.0-1.1
ii  libqt5core5a5.6.1+dfsg-3
ii  libqt5gui5  5.6.1+dfsg-3
ii  libqt5widgets5  5.6.1+dfsg-3
ii  libqt5x11extras55.6.1-2
ii  librsvg2-2  2.40.16-1
ii  libsdl-image1.2 1.2.12-5+b6
ii  libsdl1.2debian 1.2.15+dfsg1-4
ii  libstdc++6  6.1.1-9
ii  libva-drm1  1.7.1-1
ii  libva-x11-1 1.7.1-1
ii  libva1  1.7.1-1
ii  libvlccore8 2.2.4-2
ii  libvncclient1   0.9.10+dfsg-3+b1
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.6-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.4-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.4-2
ii  vlc-plugin-samba   2.2.4-2
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  dpkg   1.18.9
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.1.1-2
ii  libass50.13.2-1
ii  libavahi-client3   0.6.32-1
ii  libavahi-common3   0.6.32-1
ii  libavc1394-0   0.5.4-4
ii  libbasicusageenvironment1  2016.06.26-1
ii  libbluray1 1:0.9.3-2
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.23-1
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2+b1
ii  libchromaprint01.3-1+b1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.8-1
ii  libdc1394-22   2.2.4-1
ii  libdca00.0.5-10
ii  libdirectfb-1.2-9  1.2.10.0-5.2+b1
ii  libdvbpsi101.3.0-4
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.4-1
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libfribidi00.19.7-1
ii  libgcc11:6.1.1-9
ii  libgcrypt201.7.1-2
ii  libgme00.6.0-3
ii  libgnutls303.4.14-1
ii  libgpg-error0  1.24-1
ii  libgroupsock8  2016.06.26-1
ii  libgsm11.0.13-4
ii  libjpeg62-turbo1:1.5.0-1
ii  libkate1   0.4.1-7+b1
ii  liblircclient0 0.9.0~pre1-1.2
ii  liblivemedia52 2016.06.26-1
ii  liblua5.2-05.2.4-1
ii  liblzma5   5.1.1alpha+20120614-2.1
ii  libmad00.15.1b-8
ii  libmatroska6v5 1.4.5-1
ii  libmodplug11:0.8.8.5-2
ii  libmp3lame03.99.5+repack1-9+b1
ii  libmpcdec6

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

[Debian Bug Tracking System]

Your message dated Mon, 25 Jul 2016 01:53:00 +
with message-id 
and subject line Bug#821996: fixed in jed 1:0.99.19-5
has caused the Debian Bug report #821996,
regarding jed: 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.)


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

Hi,

The package jed 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 jed builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to jed 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, jed 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: jed
Source-Version: 1:0.99.19-5

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

Debian distribution maintenance software
pp.
Wookey  (supplier of updated jed 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, 25 Jul 2016 01:51:23 +0100
Source: jed
Binary: jed xjed jed-common
Architecture: source all amd64
Version: 1:0.99.19-5
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Description:
 jed- editor for programmers (textmode version)
 jed-common - S-Lang runtime files for jed and xjed
 xjed   - editor for programmers (x11 version)
Closes: 611331 682453 804083 821996 830131 831557
Changes:
 jed (1:0.99.19-5) unstable; urgency=medium
 .
   * Remove compiled .slc files on removal (Closes: #682453)
   * Document -e (mode-setting) option in manpage
   * Update standards-version
   * Use dpkg-buildflags instead of hardening-wrapper
   * Ensure copyright file is in each binary package
   * Add build-arch/buld-indep targets (closes: #821996)
   * Switch from dpatch to "3.0 (quilt)"
   * Use dh_autoreconf to update configuery (Closes: #804083)
   * Update Uploaders list (Closes: #830131, #830131, #831557)
   * Use triggers for info installing (Closes: #611331)
Checksums-Sha1:
 3957c471d37462e90cc4abb6e9a36507d8c18648 2021 jed_0.99.19-5.dsc
 ba943525de42cd2985b25e90452fbd50472037f9 28928 jed_0.99.19-5.debian.tar.xz
 d7686152939309a73a4061b167a67d6e4446c54f 444322 jed-common_0.99.19-5_all.deb
 bfb0ec5457a32b72a2fcaac20e6d7bda3aedd087 270020 jed-dbgsym_0.99.19-5_amd64.deb
 7dc44a20dde1482943be5000739060f80ee72c0f 125532 jed_0.99.19-5_amd64.deb
 b34ed0db31638826dc7dee6fbe425319689620de 303712 xjed-dbgsym_0.99.19-5_amd64.deb
 26a31573a44321a1c58272f9c8176dcaed9bb7b6 140600 xjed_0.99.19-5_amd64.deb
Checksums-Sha256:
 3700d51e139a8f35cc8094225d51c9cd106de3bb843c4220695f5ce869a69243 2021 
jed_0.99.19-5.dsc
 7337139b3d24483143ca95cb43dae2ad23dd348f887b664613c162e50563dd0b 28928 
jed_0.99.19-5.debian.tar.xz
 7b2c9e48399eda5dcdfa69cbc54ecb8c5ec1cd11a7e7b328989e3af8084b34a3 444322 
jed-common_0.99.19-5_all.deb
 cae6d412f6f005047d1793d6023945b03a75fd44d5413f610bac489783e7ee0e 270020 
jed-dbgsym_0.99.19-5_amd64.deb
 92b65509e9fab7a9ba220b8f320758dfe09ca57df0ec278f8f28245cb4a79172 125532 
jed_0.99.19-5_amd64.deb
 c9b9e4a24f820970c1751b924d71b449073efaa73150fcbfa92e6dd50af16001 303712 
xjed-dbgsym_0.99.19-5_amd64.deb
 3900ff23414cc357e200d4e4f11db879aa5dfbee9c8b9581911bc9c28aee8d13 140600 
xjed_0.99.19-5_amd64.deb
Files:
 5b9e592d55b810c82a56e2abad1fb5f2 2021 editors optional jed_0.99.19-5.dsc
 bc1f1650baeeb25179b317da2fd4d345 28928 editors optional 

Bug#830636: marked as done (sorl-thumbnail: FTBFS: AppRegistryNotReady: Apps aren't loaded yet.)

[Debian Bug Tracking System]

Your message dated Mon, 25 Jul 2016 00:04:04 +
with message-id 
and subject line Bug#830636: fixed in sorl-thumbnail 12.3-3
has caused the Debian Bug report #830636,
regarding sorl-thumbnail: FTBFS: AppRegistryNotReady: Apps aren't loaded yet.
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.)


-- 
830636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sorl-thumbnail
Version: 12.3-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,

sorl-thumbnail fails to build from source in unstable/amd64:

  [..]

  I: pybuild base:184: python2.7 setup.py clean 
  running clean
  removing 
'/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-2.7' does not exist -- can't clean it
  I: pybuild base:184: python3.5 setup.py clean 
  running clean
  removing 
'/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_3.5/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not exist -- can't clean it
  'build/scripts-3.5' does not exist -- can't clean it
 debian/rules override_dh_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3'
  rm -rf .build tmp-locales tests/media/
  dh_clean
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3'
   debian/rules build
  dh build --with python2,python3,sphinxdoc --buildsystem=pybuild
 dh_testdir -O--buildsystem=pybuild
 dh_update_autotools_config -O--buildsystem=pybuild
 dh_auto_configure -O--buildsystem=pybuild
  I: pybuild base:184: python2.7 setup.py config 
  running config
  I: pybuild base:184: python3.5 setup.py config 
  running config
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3'
  dh_auto_build
  I: pybuild base:184: /usr/bin/python setup.py build 
  running build
  running build_py
  creating 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl
  copying sorl/__init__.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl
  creating 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/compat.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/__init__.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/parsers.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/fields.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/base.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/default.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/models.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/images.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/log.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/shortcuts.py -> 
/home/lamby/temp/cdt.20160709223822.TSNiXR0bGS.sorl-thumbnail/sorl-thumbnail-12.3/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
  copying sorl/thumbnail/helpers.py -> 

Processed: Bug#830636 marked as pending

[Debian Bug Tracking System]

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

> tag 830636 pending
Bug #830636 [src:sorl-thumbnail] sorl-thumbnail: FTBFS: AppRegistryNotReady: 
Apps aren't loaded yet.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#830636: marked as pending

[W . Martin Borgert]

tag 830636 pending
thanks

Hello,

Bug #830636 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/sorl-thumbnail.git;a=commitdiff;h=d3a88f4

---
commit d3a88f482cc61c81e6e6dfaf2a1fbb3d3112d4ac
Author: W. Martin Borgert 
Date:   Mon Jul 25 01:54:44 2016 +0200

prepare 12.3-3

diff --git a/debian/changelog b/debian/changelog
index 2a257ab..c610b5d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+sorl-thumbnail (12.3-3) unstable; urgency=medium
+
+  * Add build-dep on python-pytest-django (Closes: #830636).
+
+ -- W. Martin Borgert   Sun, 24 Jul 2016 23:52:40 +
+
 sorl-thumbnail (12.3-2) unstable; urgency=medium
 
   [ W. Martin Borgert  ]

Bug#832341: marked as done (python-pyscss: fails to install: error: alternative path /usr/bin/python-less2scss doesn't exist)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 22:36:53 +
with message-id 
and subject line Bug#832341: fixed in python-pyscss 1.3.5-2
has caused the Debian Bug report #832341,
regarding python-pyscss: fails to install: error: alternative path 
/usr/bin/python-less2scss doesn't exist
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.)


-- 
832341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyscss
Version: 1.3.5-1
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...):

  Selecting previously unselected package python-pyscss.
  (Reading database ... 
(Reading database ... 7308 files and directories currently installed.)
  Preparing to unpack .../python-pyscss_1.3.5-1_amd64.deb ...
  Unpacking python-pyscss (1.3.5-1) ...
  Setting up python-pyscss (1.3.5-1) ...
  update-alternatives: using /usr/bin/python2-pyscss to provide /usr/bin/pyscss 
(pyscss) in auto mode
  update-alternatives: error: alternative path /usr/bin/python-less2scss 
doesn't exist
  dpkg: error processing package python-pyscss (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   python-pyscss


cheers,

Andreas


python-pyscss_1.3.5-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pyscss
Source-Version: 1.3.5-2

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated python-pyscss 
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, 24 Jul 2016 21:54:19 +
Source: python-pyscss
Binary: python-pyscss python3-pyscss
Architecture: source amd64
Version: 1.3.5-2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-pyscss - SCSS compiler - Python 2.x
 python3-pyscss - SCSS compiler - Python 3.x
Closes: 832341 832343
Changes:
 python-pyscss (1.3.5-2) unstable; urgency=low
 .
   * Remove new less2scss alternatives (Closes: #832343)
   * Fix binary/manpage name in postinst (Closes: #832341)
 (thanks to Andreas Beckmann for both reports)
   * Add authoring date to manpages
Checksums-Sha1:
 946091dc66513adae8bbb2c171364e84ff971fa5 2348 python-pyscss_1.3.5-2.dsc
 8ec631c37015358f8d82a6bd4deb0fba40cba608 6120 
python-pyscss_1.3.5-2.debian.tar.xz
 43a929d0c55d0cfd3646fa215a22e45d9dc405db 26128 
python-pyscss-dbgsym_1.3.5-2_amd64.deb
 d08e0f7b75a67fb76073a70f9333e9c36734e088 105290 python-pyscss_1.3.5-2_amd64.deb
 04eab227a1e6040d930e4632b7dc17b3f0334b50 26908 
python3-pyscss-dbgsym_1.3.5-2_amd64.deb
 2062d6c56ea26fded0018e9a56e5b36d21d3524a 105546 
python3-pyscss_1.3.5-2_amd64.deb
Checksums-Sha256:
 661a5926b0ffbbe4c90a801167740d38a7ea5cdf2267b1b6487b5d1f8a739b5d 2348 
python-pyscss_1.3.5-2.dsc
 5b77489dba617d3e31e738fb0aa166cb9e2e1b38aeecf2510c1013408ea20197 6120 
python-pyscss_1.3.5-2.debian.tar.xz
 65926ae7adc6eb6f1035091ffe264e4d6cb82f29eca6b940cc9c41a76a9270ca 26128 
python-pyscss-dbgsym_1.3.5-2_amd64.deb
 77459c197ca044a80e8b919b8ef77e9d00d058cc9c7a8cf9d011d75407604ae9 105290 
python-pyscss_1.3.5-2_amd64.deb
 75bc94cd1df5310321caeba5efca8a7000a0f4abff3f2fc31474700b9eec7da2 26908 
python3-pyscss-dbgsym_1.3.5-2_amd64.deb
 0408e161c460382d9df09543655c73810673b0567e0af594b340dc7fbf0840bf 105546 
python3-pyscss_1.3.5-2_amd64.deb
Files:
 02cf329f02be6888c05204a6010069d6 2348 python extra python-pyscss_1.3.5-2.dsc
 90e0305e4efd14665c6b6700514faf4f 6120 python extra 
python-pyscss_1.3.5-2.debian.tar.xz
 d4039d290e007dffafc8bc3de34772d2 

Bug#832391: src:consensuscore2: python module packages come out empty on some architectures

[Afif Elghraoui]

Package: src:consensuscore2
Version: 0.12.0-1
Severity: serious

The package build is apparently unpredictable. On the various package pages
(like https://packages.debian.org/sid/python3-consensuscore2), the built
binary packages are empty. For the example below, those that are 2.6 kB only
contain package metadata, not any of the contents they're supposed to have:


Download python-consensuscore2
ArchitecturePackage SizeInstalled Size  Files
amd64   2.6 kB  11.0 kB [list of files]
i386353.6 kB1,349.0 kB  [list of files]
kfreebsd-amd64  2.6 kB  11.0 kB [list of files]
kfreebsd-i386   2.6 kB  11.0 kB [list of files] 

Download python3-consensuscore2
ArchitecturePackage SizeInstalled Size  Files
amd64   346.3 kB1,435.0 kB  [list of files]
i386353.6 kB1,349.0 kB  [list of files]
kfreebsd-amd64  2.6 kB  11.0 kB [list of files]
kfreebsd-i386   2.6 kB  11.0 kB [list of files]


None of the kfreebsd builds came out right, i386 worked for both, and am64
only worked with the python3 package. There was a similar situation in
the 0.12 version of the package currently in testing. I tested amd64
and i386 in sbuild before uploading the current version of the package
and it built fine in both cases for me, so I thought this problem would
not be coming up again. I'm not sure what's going on, so I'm filing this
bug to prevent the package from being released in this condition.

regards
Afif

Bug#811820: marked as done (xplanet: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 22:12:04 +
with message-id 
and subject line Bug#811820: fixed in xplanet 1.3.0-4
has caused the Debian Bug report #811820,
regarding xplanet: FTBFS with GCC 6: no match for
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.)


-- 
811820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xplanet
Version: 1.3.0-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I. -I../..  -I../../src -I/usr/include/freetype2 
> -I/usr/include -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o addArcs.o addArcs.cpp
> addArcs.cpp: In function 'void addArcs(PlanetProperties*, Planet*, View*, 
> ProjectionBase*, std::multimap&)':
> addArcs.cpp:261:65: error: no match for 'operator!=' (operand types are 
> 'std::basic_istream' and 'long int')
>  while (inFile.getline (line, MAX_LINE_LENGTH, '\n') != NULL)
> ~^~~~
> 
> addArcs.cpp:261:65: note: candidate: operator!=(int, long int) 
> addArcs.cpp:261:65: note:   no known conversion for argument 1 from 
> 'std::basic_istream' to 'int'
> In file included from /usr/include/c++/6/iosfwd:40:0,
>  from /usr/include/c++/6/ios:38,
>  from /usr/include/c++/6/istream:38,
>  from /usr/include/c++/6/fstream:38,
>  from addArcs.cpp:4:
> /usr/include/c++/6/bits/postypes.h:221:5: note: candidate: template _StateT> bool std::operator!=(const std::fpos<_StateT>&, const 
> std::fpos<_StateT>&)
>  operator!=(const fpos<_StateT>& __lhs, const fpos<_StateT>& __rhs)
>  ^~~~
> 
> /usr/include/c++/6/bits/postypes.h:221:5: note:   template argument 
> deduction/substitution failed:
> In file included from /usr/include/stdlib.h:32:0,
>  from /usr/include/c++/6/cstdlib:72,
>  from /usr/include/c++/6/ext/string_conversions.h:41,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/bits/locale_classes.h:40,
>  from /usr/include/c++/6/bits/ios_base.h:41,
>  from /usr/include/c++/6/ios:42,
>  from /usr/include/c++/6/istream:38,
>  from /usr/include/c++/6/fstream:38,
>  from addArcs.cpp:4:
> addArcs.cpp:261:68: note:   'std::basic_istream' is not derived from 
> 'const std::fpos<_StateT>'
>  while (inFile.getline (line, MAX_LINE_LENGTH, '\n') != NULL)
> ^
> 
--- End Message ---
--- Begin Message ---
Source: xplanet
Source-Version: 1.3.0-4

We believe that the bug you reported is fixed in the latest version of
xplanet, 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.
Steve McIntyre <93...@debian.org> (supplier of updated xplanet 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, 18 Jul 2016 00:20:55 +0100
Source: xplanet
Binary: xplanet xplanet-images
Architecture: source amd64 all
Version: 1.3.0-4
Distribution: unstable
Urgency: low
Maintainer: Steve McIntyre 

Bug#805200: marked as done (gip: FTBFS: dispatcher.h: fatal error: sigc++/class_slot.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 22:09:57 +
with message-id 
and subject line Bug#805200: fixed in gip 1.7.0-1-4
has caused the Debian Bug report #805200,
regarding gip: FTBFS: dispatcher.h: fatal error: sigc++/class_slot.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.)


-- 
805200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gip
Version: 1.7.0-1-3
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from src/main.cc:25:0:
src/dispatcher.h:26:31: fatal error: sigc++/class_slot.h: No such file or 
directory
compilation terminated.
+ ERR=1
+ set +x
Error during compilation of src/main.cc.
debian/rules:16: recipe for target 'override_dh_auto_install' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/gip.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: gip
Source-Version: 1.7.0-1-4

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

Debian distribution maintenance software
pp.
Ignace Mouzannar  (supplier of updated gip 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, 23 Jul 2016 23:45:32 -0400
Source: gip
Binary: gip
Architecture: source amd64
Version: 1.7.0-1-4
Distribution: unstable
Urgency: medium
Maintainer: Ignace Mouzannar 
Changed-By: Ignace Mouzannar 
Description:
 gip- IP calculator for GNOME desktop environment
Closes: 805200
Changes:
 gip (1.7.0-1-4) unstable; urgency=medium
 .
   * debian/patches:
 - 70-remove-header.diff: remove include to fix FTBFS with newer
   libsigc++. Patch imported from Ubuntu. (Closes: 805200)
 - 71-debian-hardening.diff: adds hardening compile-time options,
   as suggested and described here: https://wiki.debian.org/Hardening.
 - 72-desktop-file.diff: add Keywords field to the desktop file.
   * debian/compat:
 - Bumped compat version from 7 to 9.
   * debian/control:
 - Removed deprecated 'Dm-Upload-Allowed' field.
 - Removed Vcs-Svn and Vcs-Browser as they are out of date.
 - Removed obsolete hompage url.
 - Bumped Standards-Version to 3.9.8.
 - Updated debhelper dependency version to follow new compat version.
   * debian/gip.menu:
 - Removed file as recommended here:
   https://lists.debian.org/debian-devel-announce/2015/09/msg0.html
Checksums-Sha1:
 a3afc3d444a83f0f9ad5a57cac5a82ccbbef91de 1647 gip_1.7.0-1-4.dsc
 7a3e6ec9fa30bd9ff23620cf790adcdcd56e6aad 6964 gip_1.7.0-1-4.debian.tar.xz
 c11b1ac2fa30bb830a800076625bb117116abf75 528910 gip-dbgsym_1.7.0-1-4_amd64.deb
 1305c219056d00b90706d452fc73713e4be84ebf 87444 gip_1.7.0-1-4_amd64.deb
Checksums-Sha256:
 9e3aba8bea9b5425f75d9279f6657e3c291873b93869975a54809020ccde7633 1647 
gip_1.7.0-1-4.dsc
 ab7606e5357b8ab632f96e7362da7afb6c46168bd2902ffc3d98c53e0bb20ab9 6964 
gip_1.7.0-1-4.debian.tar.xz
 e24a1d5ed7a47bb6bd0f0d7e2dae285ee009d1d7fe562b41388eb1d2397ad7f0 528910 
gip-dbgsym_1.7.0-1-4_amd64.deb
 3bcd67cb9bcc8ecc2b72af326e9e108e1038c384937ec1fe34465acb8bd72845 87444 
gip_1.7.0-1-4_amd64.deb
Files:
 7fe458c3f8632c5242d5bb7d723acc57 1647 gnome optional gip_1.7.0-1-4.dsc
 218a57337393addf14386144bfc66ba3 6964 gnome optional 
gip_1.7.0-1-4.debian.tar.xz
 053856c26d941a779cd481880898a205 528910 debug extra 
gip-dbgsym_1.7.0-1-4_amd64.deb
 c3caed2d35448c8a0259845b2ebf0eaf 87444 gnome optional gip_1.7.0-1-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXlDx0AAoJELwssaJob/h/1M4P/3B4zUwK3N3hoqSsGWscuxZw
B7bXT6GhlswylHr+8/y3aZi/aVW7ThCslWprebr6EbztWKP3qeJhzPKGEW8Xq6MI

Bug#832344: marked as done (open-isns-server: unowned files after purge (policy 6.8, 10.8): /etc/isns/auth_key)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 22:11:17 +
with message-id 
and subject line Bug#832344: fixed in open-isns 0.96-2
has caused the Debian Bug report #832344,
regarding open-isns-server: unowned files after purge (policy 6.8, 10.8): 
/etc/isns/auth_key
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.)


-- 
832344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-isns-server
Version: 0.96-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m35.9s ERROR: FAIL: Package purging left files on system:
  /etc/isns/auth_key not owned


cheers,

Andreas


open-isns-server_0.96-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: open-isns
Source-Version: 0.96-2

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

Debian distribution maintenance software
pp.
Christian Seiler  (supplier of updated open-isns package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 21:57:27 +0200
Source: open-isns
Binary: open-isns-utils open-isns-server open-isns-discoveryd libisns0 
libisns-dev libisns0-udeb
Architecture: source
Version: 0.96-2
Distribution: unstable
Urgency: medium
Maintainer: Debian iSCSI Maintainers 

Changed-By: Christian Seiler 
Description:
 libisns-dev - Internet Storage Name Service - development files
 libisns0   - Internet Storage Name Service - shared libraries
 libisns0-udeb - Internet Storage Name Service - shared libraries (udeb)
 open-isns-discoveryd - Internet Storage Name Service - iSNS discovery daemon
 open-isns-server - Internet Storage Name Service - iSNS server
 open-isns-utils - Internet Storage Name Service - client utilities
Closes: 832344
Changes:
 open-isns (0.96-2) unstable; urgency=medium
 .
   * debian/*.postrm: ask user whether to delete auth_key etc. on purge
 (Closes: #832344)
   * debian/patches: fix FTBFS on kfreebsd-*
   * debian/patches: fix FTBFS on hurd-i386
   * debian/open-isns-server.postinst: prevent hang on sysvinit systems
Checksums-Sha1:
 dc425c5a06b4b340433963bc97c6fc0f945cc500 2358 open-isns_0.96-2.dsc
 6fcc4459747fe8bae6ea02f5458c1a6f2faa2e11 16800 open-isns_0.96-2.debian.tar.xz
Checksums-Sha256:
 514cab73bcc323854514108f4fe1617c534f80c1af38d8c294c1f36e7b831cfd 2358 
open-isns_0.96-2.dsc
 bcb713bcdaa0cc9c1240592eb7c64aae15c43940f0e6c92d7d88ea2bb733aedf 16800 
open-isns_0.96-2.debian.tar.xz
Files:
 00bf0995da3c60f61aadf48e97d3f218 2358 net optional open-isns_0.96-2.dsc
 b42c1d2bb7f7aa5e598d7b0434672102 16800 net optional 
open-isns_0.96-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXlR9tAAoJEGMjNFnNz6AY2tgQALAYKO8Av9+Wcmes3fXir/5D
PlkEqG5LC1zxN1vCOoQJrqZdgbfs6nnjBJsIDCmpZj4nZukbW4ZQ4AtpVDmYbcK3
7WsmkYylYKKSVt8VZ3wZUZ4FSXOJOv2xCnTAB0QIkk9JF+Cm4H/28dTm26wXIukZ
s4Z1dPk65sZkH2kE5JxT30CdRkvl3kfjWC7zfNfqpuu+Qrx8k150dmF9vIpLGceJ
VIm3v+A8tMiPBDe6WcGl3TiBjFKOQCEfz+kIryQ7sr4SbTBXVUNKSTRfGwIiJWjb
sMHKItP1/z9i7nPhhvMrp83UXuvT52IKYcXDbnk1ONxMDdDouRmRnfKzUbRfVdUg
lqiGDd9bXpZOuYy6JHHRv86z+0JD/LfPtLe+LZ6AmUgDFuaioPBB+hj8/lz/gHID
kIoSILxsXpD96bMXJqAyTIZREexTuWMkKr8Gk0DWKoOyVzcUw5yOHIczeanCJ0kj
lweGebI6Ym9R0il7lrfmzev9rt8orUU93+sqrAD03q08JVEyr4nuYgBS5vmIW5Po
TnpTR4Sc39EdM8KbNdZJC1JKU1Ez1lH1SrpUS3i20m2P+QHm4dzGSluvP8Yu0NzZ
RasQ643lEkc3UfUS/Vi5+3v8sPNgdVknp0DBouZNUwP+mUBj6xcw645ZYk4APRmm
xYOX7ug0gX5deS+tPjMq
=qwDT
-END PGP SIGNATURE End Message ---

Bug#811666: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 22:11:11 +
with message-id 
and subject line Bug#811666: fixed in mp3diags 1.2.02-4
has caused the Debian Bug report #811666,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mp3diags
Version: 1.2.02-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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
...
> g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fpermissive 
> -D_REENTRANT -Wall -W -DDISABLE_CHECK_FOR_UPDATES -DQT_NO_DEBUG -DQT_XML_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui 
> -I/usr/include/qt4/QtXml -I/usr/include/qt4 -Irelease -Iui-forms -o 
> release/moc_ConfigDlgImpl.o release/moc_ConfigDlgImpl.cpp
> ExportDlgImpl.cpp: In member function 'bool ExportDlgImpl::exportAsText(const 
> string&)':
> ExportDlgImpl.cpp:374:12: error: cannot convert 'ofstream_utf8 {aka 
> std::basic_ofstream}' to 'bool' in return
>  return out;
> ^~~
> 
> ExportDlgImpl.cpp: In member function 'bool ExportDlgImpl::exportAsM3u(const 
> string&)':
> ExportDlgImpl.cpp:427:12: error: cannot convert 'ofstream_utf8 {aka 
> std::basic_ofstream}' to 'bool' in return
>  return out;
> ^~~
> 
> ExportDlgImpl.cpp: In member function 'bool ExportDlgImpl::exportAsXml(const 
> string&)':
> ExportDlgImpl.cpp:764:12: error: cannot convert 'ofstream_utf8 {aka 
> std::basic_ofstream}' to 'bool' in return
>  return out;
> ^~~
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: mp3diags
Source-Version: 1.2.02-4

We believe that the bug you reported is fixed in the latest version of
mp3diags, 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.
Josue Ortega  (supplier of updated mp3diags package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 14:21:10 -0600
Source: mp3diags
Binary: mp3diags
Architecture: source amd64
Version: 1.2.02-4
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Description:
 mp3diags   - find issues in MP3 files and help to solve them
Closes: 811666
Changes:
 mp3diags (1.2.02-4) unstable; urgency=medium
 .
   * Adds debian/patches/01/fix-gcc6-compat.patch (Closes: #811666)
Checksums-Sha1:
 7180d63a511b283004c5540c60ca12e951d2a6bb 1926 mp3diags_1.2.02-4.dsc
 2cd9bc582487fb7398e538550ed465d094b71d3e 7252 mp3diags_1.2.02-4.debian.tar.xz
 b2b75d06e299cdc1459ca6616f2d267077b90cee 12765702 
mp3diags-dbgsym_1.2.02-4_amd64.deb
 c4a47e5c3567add4a0c5c88ffc1458cebce61056 1391466 mp3diags_1.2.02-4_amd64.deb
Checksums-Sha256:
 957731a227f8a6c67999b26ff0c934ea5c6481ac73715a7f6c31b1505688559f 1926 
mp3diags_1.2.02-4.dsc
 2edb321ca320f0970f2ee35e47d14739f1e594383f772d1cc7f92c8754024c10 7252 
mp3diags_1.2.02-4.debian.tar.xz
 434791cddedb6b7eea637d43c93854626d91333e7f17264c9072132e17e23c7a 12765702 
mp3diags-dbgsym_1.2.02-4_amd64.deb
 b5dbda972800642814f4ded9f88a9e0b0b34815d91a5390bae53953571d20e41 1391466 
mp3diags_1.2.02-4_amd64.deb
Files:
 1e448ca89c2c911951d52793b97e6281 1926 sound optional mp3diags_1.2.02-4.dsc
 8c5bfd56c0239d8a9eba62c6cc45a991 7252 sound optional 
mp3diags_1.2.02-4.debian.tar.xz
 

Bug#817387: marked as done (cappuccino: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 22:05:20 +
with message-id 
and subject line Bug#817387: fixed in cappuccino 0.5.1-2.3
has caused the Debian Bug report #817387,
regarding cappuccino: 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.)


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

Hi,

The package cappuccino 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: cappuccino
Source-Version: 0.5.1-2.3

We believe that the bug you reported is fixed in the latest version of
cappuccino, 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.
Bill Allombert  (supplier of updated cappuccino 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: SHA1

Format: 1.8
Date: Sun, 24 Jul 2016 16:17:42 +0200
Source: cappuccino
Binary: cappuccino
Architecture: source all
Version: 0.5.1-2.3
Distribution: unstable
Urgency: medium
Maintainer: Christian Surchi 
Changed-By: Bill Allombert 
Description:
 cappuccino - utility to let your boss think that you're working hard
Closes: 817387
Changes:
 cappuccino (0.5.1-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use debhelper 5. Closes: #817387
   * debian/rules clean: remove .grm.o files.
Checksums-Sha1:
 026bb9f8175f95db741ce7710504e1450af36bcf 1682 cappuccino_0.5.1-2.3.dsc
 401a9a049bf0ba105659e666c7b861360d5f32e4 1563 cappuccino_0.5.1-2.3.diff.gz
 02ed95764a1d55919f4925cd13057eed55dbc5e5 91030 cappuccino_0.5.1-2.3_all.deb
Checksums-Sha256:
 45cac0412bc74c008480e75a43c3ea286e940bebb415fd36fed7ee59ceea52a3 1682 
cappuccino_0.5.1-2.3.dsc
 9ec743ca0d302ed3f7062d0c76148bf79a57d66983ba39204145827a29f0906a 1563 
cappuccino_0.5.1-2.3.diff.gz
 40a2556160e46e84412dacf160429f85f5b0a42a5d35c1accaa554e68a9f877e 91030 
cappuccino_0.5.1-2.3_all.deb
Files:
 d429c21e98647b63554b4df5b7a709b2 1682 games optional cappuccino_0.5.1-2.3.dsc
 fb0792469eb2604eeb2bb44404fff499 1563 games optional 
cappuccino_0.5.1-2.3.diff.gz
 d57e6465839c1a049a8beb11e2768b56 91030 games optional 
cappuccino_0.5.1-2.3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXlRXgAAoJEI8OfCtFIuOH5lwP/jGjc83ShcR0u1Gv91DlS2y9
5QO4+2pPZwA219685jKR3vA/aOYINd5z0UgBgxkjibXtKW+bHSrVfTXm2sSubcMk
VN+Z7EtAHZjhy5qWC90bxAlMSIvmWKh5rqsbNqYc6QQlmlGm2+h/aDShNaBkOVOj
YufoPa7eBSMSpnZvrOtvnELlDMcxv2uj5kYgdteimzTKc+B6wysmxwsi/qVoBSj8
wfyZeGwd/ngOm+T2BwAu0GsgON6lo6HmednMvv7L1L2yfMjnO3CWZqe0JVGW5Uqm
4SDJyzZ+lNzSe52htblvDCxyquZsuwBC+dpGFs1v/DepibNUEwtg7Zr4ozNGuiR3
fSDG1jRHsNNu4lUhBtGHzdA3iL6k905fN667a/VsgIirJqbp3S/su36UlzS9FMQ3
xJ4SglrhY3NGVam8L1q0Rn/4yW6SjO07t5ArkisDi8EVjlHpR2qAVnUX/LU35svH
ba4wtMzYDB1u60m4iDH2gbt+Ke8HzcPvi7hQ/eG2kAswnnqk3TDBKy0pLkdrN0zq
p/8j6MN0VJABnwMybvBCzye1efQuoleQlM5ihHqdD+W4PkRdu9qcTBoWqq/DlB+J
OG5LK5TbHgZnW66XQM/0Ded/6xN1+c6PiXVzaOQmqOe2Xkd+C8vZtgZH6eGBsAHp
KfwPY4E5+0x4ywHFVIjw
=73Ku
-END PGP SIGNATURE End Message ---

Bug#832390: libgd2: FTBFS on *i386: FAIL: gdimagerotate/bug00067

[Aurelien Jarno]

Source: libgd2
Version: 2.2.2-43-g22cba39-1
Severity: serious

Dear Maintainer,

Your package fails to build on i386, kfreebsd-i386 and hurd-i386 with
the same testsuite failure, while it builds fine everywhere else:

| FAIL: gdimagerotate/bug00067
| 
|
| gdimagerotate/bug00067.c:46: Total pixels changed: 14143 with a maximum 
channel difference of 255.
| gdimagerotate/bug00067.c:47: comparing rotated image to 
./gdimagerotate/bug00067_150_exp.png failed.
| FAIL gdimagerotate/bug00067 (exit status: 1)

A full build log is available here:

https://buildd.debian.org/status/fetch.php?pkg=libgd2=i386=2.2.2-43-g22cba39-1=1469396971


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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)

Processed: severity of 800446 is serious

[Debian Bug Tracking System]

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

> severity 800446 serious
Bug #800446 [libltdl-dev] libltdl-dev:i386 fails to install on amd64 system
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#800446: marked as done (libltdl-dev:i386 fails to install on amd64 system)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 23:24:45 +0200
with message-id <20160724212445.ga14...@roeckx.be>
and subject line Re: Bug#800446: libltdl-dev:i386 fails to install on amd64 
system
has caused the Debian Bug report #800446,
regarding libltdl-dev:i386 fails to install on amd64 system
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.)


-- 
800446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libltdl-dev
Version: 2.4.2-1.11
Severity: normal

I am trying to install a i386 package on an amd64 system.  The package needs
libltdl-dev:i386 but it fails to install with the following error:

# apt-get install libltdl-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gnome-themes-standard:i386 gtk2-engines:i386 gtk2-engines-murrine:i386 gtk2
-engines-oxygen:i386 gtk2-engines-pixbuf:i386 gtk2-engines-qtcurve:i386 kde-
style-qtcurve:i386
  kwin-style-qtcurve:i386 libattica0.4:i386 libaudio2:i386 libavformat56:i386
libbonoboui2-0:i386 libclucene-core1:i386 libcurl3-gnutls:i386 libdb5.3:i386
libdbusmenu-qt2:i386
  libdlrestrictions1:i386 libexiv2-13:i386 libfam0:i386 libgail18:i386
libglade2-0:i386 libgnome-keyring0:i386 libgnomecanvas2-0:i386
libgnomeui-0:i386 libidl0:i386 libidn11:i386
  libiodbc2:i386 libkdecorations4abi2:i386 libkdecore5:i386 libkdeui5:i386
libkio5:i386 liblcms2-2:i386 libldap-2.4-2:i386 libmhash2:i386 libmng1:i386
libnepomuk4:i386 liborbit2:i386
  libqt4-dbus:i386 libqt4-network:i386 libqt4-svg:i386 libqt4-xml:i386
libqtcore4:i386 libqtdbus4:i386 libqtgui4:i386 libraptor2-0:i386
librasqal3:i386 librdf0:i386 librtmp1:i386
  libsasl2-2:i386 libsasl2-modules:i386 libsasl2-modules-db:i386 libsolid4:i386
libsoprano4:i386 libssh2-1:i386 libssl1.0.0:i386 libstreamanalyzer0:i386
libstreams0:i386 libxkbfile1:i386
  libxp6:i386 libxslt1.1:i386 libxss1:i386 libxt6:i386 libyajl2:i386
odbcinst1debian2:i386 soprano-daemon:i386
Use 'apt-get autoremove' to remove them.
Suggested packages:
  libtool-doc:i386
The following NEW packages will be installed:
  libltdl-dev:i386
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/159 kB of archives.
After this operation, 872 kB of additional disk space will be used.
Gtk-Message **: Failed to load module "canberra-gtk-module" at /usr/lib/x86_64
-linux-gnu/perl5/5.20/Gtk2.pm line 126, <> line 1.
Gtk-Message **: Failed to load module "canberra-gtk-module" at /usr/lib/x86_64
-linux-gnu/perl5/5.20/Gtk2.pm line 126, <> line 1.
(Reading database ... 173974 files and directories currently installed.)
Preparing to unpack .../libltdl-dev_2.4.2-1.11_i386.deb ...
Unpacking libltdl-dev:i386 (2.4.2-1.11) ...
dpkg: error processing archive /var/cache/apt/archives/libltdl-
dev_2.4.2-1.11_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/libtool/libltdl/Makefile.in', which is
different from other instances of package libltdl-dev:i386
Errors were encountered while processing:
 /var/cache/apt/archives/libltdl-dev_2.4.2-1.11_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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)

Versions of packages libltdl-dev depends on:
ii  libltdl7  2.4.2-1.11

Versions of packages libltdl-dev recommends:
ii  libtool  2.4.2-1.11

Versions of packages libltdl-dev suggests:
pn  libtool-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.4.6-0.1

On Tue, Sep 29, 2015 at 07:45:14AM -0500, Brent S. Elmer wrote:
> dpkg: error processing archive /var/cache/apt/archives/libltdl-
> dev_2.4.2-1.11_i386.deb (--unpack):
>  trying to overwrite shared '/usr/share/libtool/libltdl/Makefile.in', which is
> different from other instances of package libltdl-dev:i386
> Errors were encountered while processing:
>  /var/cache/apt/archives/libltdl-dev_2.4.2-1.11_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

This was cause by using a different version of the automake tool
for i386 and amd64.  I'll also get this fixed in stable.


Kurt--- End Message ---

Bug#826042: Spyder crashes on start

[Ghislain Vaillant]

On 24/07/16 21:10, Jitse Niesen wrote:

On 18/07/16 15:15, Ghislain Vaillant wrote:


If you want to be helpful, please consider reviewing whether the
current state of Debian unstable and check whether it contains all the
necessary dependencies for the packaging of Spyder 3.x to happen.


It's possible to run Spyder, but I don't think everything is ready for
it yet. Specifically, I can install (with "python setup.py install") and
run Spyder after I installed the following packages from Debian unstable:

python3 3.5.1-4
python3-docutils0.12+dfsg-1
python3-jinja2  2.8-1
python3-pickleshare 0.7.3-1
python3-qt4 4.11.4+dfsg-2
python3-qtawesome   0.3.3-3
python3-qtpy1.1.1-1
python3-sphinx  1.4.5-1
python3-zmq 15.2.0-1

However, Spyder complains of missing dependencies and while the basic
functionality is there, not all features work correctly. Some of them
can be installed from unstable:

python3-jedi0.9.0-1
python3-pep81.7.0-2
python3-psutil  4.2.0-1
python3-pyflakes1.2.3-1


Thanks Jitse for this listing. This is very helpful.


Spyder has three further dependencies that need more work:

* rope >= 0.9.4: There is a package python-rope version 0.10.2-1 but
  no Python3 version.

* qtconsole >= 4.2.0: Experimental has jupyter-qtconsole.

* nbconvert >= 4.0: As far as I can see, there is no nbconvert but
  there is an Intend-To-Package message at bug 801058.


As you can see here:

  https://lists.debian.org/debian-python/2015/09/msg00087.html

nbconvert is further along in the dependency chain, hence yourself not
finding an RFS for it yet. I believe Julien is working on it. Meanwhile
other dependencies like ipython and the jupyter core packages will have
to find their way to the archive (first via a trip to experimental)
first, before nbconvert is made available.

Regarding rope, the package has a wishlist bug for Python 3 and also a
CVE (which is bad). It might be worth checking with the package 
maintainer whether he still actively maintains it, and propose a

migration to the DPMT Git. I'll contact him and propose my help.

Cheers,
Ghis

Processed: severity of 832332 is important

[Debian Bug Tracking System]

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

> severity 832332 important
Bug #832332 [src:linux] linux-image-4.6.0-1-amd64: Flickering X display for 
Intel HD 4600 (i915 driver)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Andreas Beckmann]

Hi,

I think I've also seen this segfault in a spurious piuparts failure
(package: xrdp, upgrade: jessie -> sid). So the bug is out in the wild,
not only in a testsuite. Luckily I saw the debian-release@ discussion
about it before digging deeper into the piuparts failure.


Andreas

Processed: severity of 814762 is grave

[Debian Bug Tracking System]

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

> severity 814762 grave
Bug #814762 [kmail] kmail: CSS from HTML mail interfers with header layout
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#788546: nfs4 mount.nfs does not respect option "user" in fstab in Jessie

[Andreas Henriksson]

Hello Ingo.

On Fri, Jun 12, 2015 at 06:12:21PM +0200, Ingo wrote:
> Since upgrade of the client from Wheezy to Jessie I am no longer able to
> mount nfs4-exports from a host (leo) running Wheezy as a normal user
> (UID=1000):
[...]
> /etc/fstab entries on the clients (Jessi and Wheezy):
> leo:/Bilder /home/ingo/leo.Bilder nfs4 noauto,rw,user,soft,relatime 0 0
> 
> In Wheezy all works as expected, in Jessie mount fails with:
> $ LANG=en_US.UTF-8 mount leo:/Bilder
> mount: leo:/Bilder: No such file or directory

Are you sure this is the correct syntax? I would expect that you
should specify the mountpoint (target directory) rather than the
source of the mount. eg. mount /home/ingo/leo.Bilder
Do using that still give you the same problem?

Might also be useful to have a log of what strace tells you about
running the command.

> 
> However it is possible to perform the mount as "root".
> 
> Umount as user (UID=1000) fails with same "non informative" message:
> $ LANG=en_US.UTF-8 umount leo:/Bilder
> umount: leo:/Bilder: No such file or directory
> 
> This is a security flaw as users cannot mount/umount on demand without
> root-privileges.

(Well, it's not a security issue unless you hand out root access yourself
to untrusted people.)

Regards,
Andreas Henriksson

Bug#775541: nfs-utils bug report status after last nmu?

[Andreas Henriksson]

Control: tags -1 + moreinfo

Hello!

I think it would be useful if someone could provide a status
update on this bug report[1] indicating if this is still an
issue since nfs-utils NMU 1:1.2.8-9.1 which included native
systemd unit files with much more fine-grained dependency
specifications. Hopefully this should have resolved all
cases of ending up with a dependency loop, so please test
and provide feedback!


Regards,
Andreas Henriksson

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

Processed: nfs-utils bug report status after last nmu?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #775541 [nfs-common] NFS mounts from /etc/fstab can fail w/out 
network-manager
Added tag(s) moreinfo.

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

Processed: Re: nautilus closes on every start when using xorg server

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible moreinfo
Bug #828185 [nautilus] nautilus closes on every start when using xorg server
Added tag(s) moreinfo and unreproducible.
> severity -1 important
Bug #828185 [nautilus] nautilus closes on every start when using xorg server
Severity set to 'important' from 'grave'

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

Bug#828185: nautilus closes on every start when using xorg server

[Andreas Henriksson]

Control: tags -1 + unreproducible moreinfo
Control: severity -1 important

Hello.

On Sat, Jun 25, 2016 at 05:31:37PM -0430, Roberto De Oliveira wrote:
> Package: nautilus
> Version: 3.20.1-3
> Severity: grave
> Justification: renders package unusable
> 
> Using Wayland nautilus works fine, but using xorg nautilus closes on every 
> start.
> On console it is showed the following message:
> 
> (nautilus:5984): Gtk-WARNING **: Theme parsing error: :1:0: 
> Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' 
> does not exist
> **
> ERROR:nautilus-canvas-container.c:6019:finish_adding_new_icons: assertion 
> failed: (!container->details->auto_layout)
> Aborted

I'm not able to reproduce your problem and I've seen noone else 
mention any similar issue, thus I'm lowering the severity and tagging
the bug accordingly.
Can you reproduce this issue yourself if you add a new user to your
system and login using the new user?

> 
> it happens no matter what gtk theme it is used.

Thanks for testing that which would have been my first guess.
Guess we'll need to look elsewhere for the problem. Please keep
us posted about any useful information you get your hands on.

Regards,
Andreas Henriksson

Bug#831495: marked as done (totem does not start, Aborted.)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 21:38:20 +0200
with message-id <20160724193820.ga3...@fatal.se>
and subject line Re: Bug#831495: totem does not start, Aborted.
has caused the Debian Bug report #831495,
regarding totem does not start, Aborted.
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.)


-- 
831495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: totem
Version: 3.20.1-3
Severity: grave
Justification: renders package unusable

When starting totem the program does not start but exits directly with
"Aborted". I can provide more information if required.

$ totem
Aborted

Running with gdb:

$ gdb totem
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe36c2700 (LWP 16361)]
[New Thread 0x7fffe2ec1700 (LWP 16362)]
[New Thread 0x7fffdb7a4700 (LWP 16363)]
[New Thread 0x7fffd9b25700 (LWP 16364)]
[New Thread 0x7fffc700 (LWP 16365)]
[New Thread 0x7fffc76d5700 (LWP 16366)]
[New Thread 0x7fffc6ed4700 (LWP 16367)]
[New Thread 0x7fffc5e1d700 (LWP 16369)]
[New Thread 0x7fffc4a45700 (LWP 16370)]
[New Thread 0x7fffb759d700 (LWP 16371)]

Thread 11 "multiqueue0:src" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffb759d700 (LWP 16371)]
0x760c21c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) backtrace full
#0  0x760c21c8 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 16569
selftid = 16580
#1  0x760c364a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, 
sa_mask = {__val = {14073623472, 140736235985293, 142, 140736234748278, 
140735878070176, 8,
  140736220803665, 140735878069008, 16406223249348791808, 
140736240040192, 140735878070176, 140735878071360, 16406223249348791808, 1136, 
140736239850576,
  140735878070176}}, sa_flags = -1610286320, sa_restorer = 
0x7fffa004f800}
sigs = {__val = {32, 0 }}
#2  0x7fffb4fbaf5b in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.57
No symbol table info available.
#3  0x7fffb4fbb026 in avcodec_alloc_context3 () from 
/usr/lib/x86_64-linux-gnu/libavcodec.so.57
No symbol table info available.
#4  0x7fffb6962540 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
No symbol table info available.
#5  0x7fffb6958e53 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
No symbol table info available.
#6  0x7698e22d in g_type_class_ref () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#7  0x74f42da4 in gst_element_register () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
No symbol table info available.
#8  0x7fffb69595b3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
No symbol table info available.
#9  0x7fffb694be20 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
No symbol table info available.
#10 0x74f64537 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
No symbol table info available.
#11 0x74f66425 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
No symbol table info available.
#12 0x74f6712c in gst_plugin_load_by_name () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
No symbol table info available.
#13 0x74f67a8d in gst_plugin_feature_load () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
No symbol table info available.
#14 

Bug#830777: nfs-common: rpc.idmapd does not start under systemd on a pure client system

[Andreas Henriksson]

Hello Ben Harris.

Thanks for your bug report. Unlike all the other RC bugs for nfs-utils
this one was introduced by my NMU so I feel atleast partially
responsible. I'm not a nfs user myself though so beware that my
interest is limited.

On Mon, Jul 11, 2016 at 12:22:15PM +0100, Ben Harris wrote:
> Package: nfs-common
> Version: 1:1.2.8-9.1
> Severity: normal
> 
> Dear Maintainer,
> 
> I have a system that acts as an NFSv4 client.
> It does not have nfs-kernel-server installed. 

(Thanks very useful information.)

> After a recent reboot, I found that none of the files in my
> NFS-mounted home directory was owned by me any more:
> 
> bjh21@wraith:~/config/platforms-ansible$ ls -l ~/.ssh
> total 609
> -rw-r--r-- 1 4294967294 4294967294616 Aug 14  2015 authorized_keys
> ...
> 
> I found that rpc.idmapd was not running, and could not be started:
[...]
> When I copied /lib/systemd/system/nfs-idmapd.service to /etc/systemd/system
> and commented out the line "BindsTo=nfs-server.service", things got better
> and "service nfs-idmapd start" worked. 

The BindsTo= statement is documented at
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#BindsTo=
As you can see its said to be a variant of Requires= which means the
service in question won't start unless the referenced one also does.
Since you don't have nfs-kernel-server package installed, which is the
package shipping the nfs-server.service, you will not be able to start
nfs-idmapd.service in it's current state. No surprise here I guess
as you already figured that out.

The relevant upstream commit introducing the BindsTo= is
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=b5cea96efb1512340a536e25650c5b548fc6
with commit message
"Since rpc.idmapd is only used by the nfs server,
to do its id mapping, bind the rpc-idmapd service
to the nfs-server service so rpc.idmapd will
started and stopped with the server.Since rpc.idmapd is only used by the
nfs server,
to do its id mapping, bind the rpc-idmapd service
to the nfs-server service so rpc.idmapd will
started and stopped with the server."

So upstream seems to think rpc.idmapd is not useful without
nfs-kernel-server while you do. Any chance you could take this
issue upstream and discuss it there directly?

> After a few seconds, my home directory had the correct owner:
> 
> bjh21@wraith:~/config/platforms-ansible$ ls -l ~/.ssh
> total 609
> -rw-r--r-- 1 bjh21 bjh21616 Aug 14  2015 authorized_keys
> 
> I think that nfs-common should arrange that rpc.idmapd is started even on
> systems without nfs-kernel-server installed, or at least that there is a
> note in NEWS.Debian telling users how to turn it back on.

The unit files shipped comes basically verbatim from upstream. If
they're not correct we should be good citizens and help fix them
upstream rather than suggesting workarounds in my humble opinions.
Please discuss the issue upstream. If you describe your usecase
upstream might find a suitable solution for us.

Please see http://linux-nfs.org

Regards,
Andreas Henriksson

Processed: unrepr

[Debian Bug Tracking System]

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

> tags 831495 + unreproducible
Bug #831495 [totem] totem does not start, Aborted.
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#828826: nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd

[Andreas Henriksson]

On Tue, Jul 12, 2016 at 11:16:42PM +0200, Michael Biebl wrote:
> Control: severity -1 serious
> 
> On Tue, 28 Jun 2016 09:21:44 +0200 Christoph Hellwig  wrote:
> > Package: nfs-common
> > Version: 1:1.2.8-9
> > Severity: important
> > Tags: patch
> > 
> > Dear Maintainer,
> > 
> > commit ba649fa4 ("Migrate the rpc_pipefs mount out of /var/lib to /run, to
> > better support /var on NFS.") in the Debian packaging repo completely
> > broke blkmapd, which still looks for rpc_pipefs in the old place.
> > >From looking in the BTS gssd also seems to have the same problem (#632141).
> > 
> > diff --git a/utils/blkmapd/device-discovery.c 
> > b/utils/blkmapd/device-discovery.c
> > index 69f00fa..7b00c90 100644
> > --- a/utils/blkmapd/device-discovery.c
> > +++ b/utils/blkmapd/device-discovery.c
> > @@ -55,9 +55,9 @@
> >  #define EVENT_SIZE (sizeof(struct inotify_event))
> >  #define EVENT_BUFSIZE (1024 * EVENT_SIZE)
> >  
> > -#define BL_PIPE_FILE   "/var/lib/nfs/rpc_pipefs/nfs/blocklayout"
> > -#define NFSPIPE_DIR"/var/lib/nfs/rpc_pipefs/nfs"
> > -#define RPCPIPE_DIR"/var/lib/nfs/rpc_pipefs"
> > +#define BL_PIPE_FILE   "/run/rpc_pipefs/nfs/blocklayout"
> > +#define NFSPIPE_DIR"/run/rpc_pipefs/nfs"
> > +#define RPCPIPE_DIR"/run/rpc_pipefs"
> >  #define PID_FILE   "/run/blkmapd.pid"
> >  
> 
> Looks to me like this should be RC, i.e. needs to be fixed for the next
> Debian release.
> Thus bumping the severity.

FYI I think there's a fix for this (or atleast something similar) in
the remaining ubuntu delta for this package. As already mentioned
would be useful to investigate the remaining delta and pull in
the useful parts. This is however not a new issue and should
already affect the version of the package in Debian Jessie/Stable.

Regards,
Andreas Henriksson

Bug#817564: marked as done (lice: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 19:18:44 +
with message-id 
and subject line Bug#817564: fixed in lice 1:4.2.5i-2
has caused the Debian Bug report #817564,
regarding lice: 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.)


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

Hi,

The package lice 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: lice
Source-Version: 1:4.2.5i-2

We believe that the bug you reported is fixed in the latest version of
lice, 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.
Kurt Roeckx  (supplier of updated lice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 21:05:41 +0200
Source: lice
Binary: epic4-script-lice
Architecture: source
Version: 1:4.2.5i-2
Distribution: unstable
Urgency: medium
Maintainer: Kurt Roeckx 
Changed-By: Kurt Roeckx 
Description:
 epic4-script-lice - Very functional script for epic
Closes: 777006 817564
Changes:
 lice (1:4.2.5i-2) unstable; urgency=medium
 .
   * Switch to debhelper compatibility level 9 (Closes: #817564)
   * Use gzip -9 with -n to make it reproducible (Closes: #777006)
   * Use dh_prep instead of dh_clean -k
   * Add ${misc:Depends} to Depends
   * Add build-arch and build-indep targets
   * Use sh -e for postinst and prerm
Checksums-Sha1:
 f225220a33b819e56a39e450af010467c8a15ded 1614 lice_4.2.5i-2.dsc
 307c0296ab7fcc029a146996dd7a8ae6db73b341 6616 lice_4.2.5i-2.diff.gz
Checksums-Sha256:
 cf5a1e644f4ac1deaf4e0c3f4d3e7f3154ac454cac4c77c2d908b1af7d0c7749 1614 
lice_4.2.5i-2.dsc
 7ffb1231dd714c5e8d538d3ddc4f3e31e00ba335532d86ae9b308dc1bbb8f5a1 6616 
lice_4.2.5i-2.diff.gz
Files:
 b8dd49066476be18f467e2ac69e451f7 1614 net optional lice_4.2.5i-2.dsc
 d565d12967b0bdce287c6426d5e19608 6616 net optional lice_4.2.5i-2.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXlRM2AAoJEOPE3c0eTBJE48IP/0MBVelF/IqHA6MCrVHth9Bb
KG0/++gY6UWOHMzEMUssFTdjI8hblRZ1oYe9kPcDo1NU5yAN9s0es1xIhktvN40K
wAaEY7ukcTnz5RDDiVouiMSq1MFXemLdxlZhiiWMNd0rEHsEnaN4nWt96gwWQBM4
MNwBTGtft/vUFEM4Qb0li6fmUvRAxF5T55TEQzLP8dnqxNjwlKhuJIyNpGZJEUCy
7ilkbT5ZzSU0dR/r3UU0qmvXaE5g383YFm65SM0HFeGQhLH/w1W0fkdv8oQvvc6t
4X/WTThheWWKYLJoC8XMA4jf/UN9IVdytl6FKr4P4aYz7tp7unTBID+IO1masuYI
7awkWRe+iCX0Tmji5K1PD/gc3r58p3nvHfzzVesvKf0vpS/yhGPNnva8DKVQdO84
Goxds+DN1PQ5W3MWU+Zehqy1dt+Mz9k1zMVGwQsHRiEpa4M1+bhTl/4/vdo8RmGd
OhY5p6g3iFihM8PQnH/ClXdTgrKV2dGVItV7fThXRne+WuN01Ms8jR5vTC/JHuRg
FVPA3BxLch8LympmpdlCI5ChftNM6T3mgkHWTTRAqqs3p5qAbo1W7/fCG8V1Jad6
6vlyWDyZvyO+pIpin4EGlAftwiwY5V6MLIqkF0N7C/B/A/BsS+0hgVG2dH83roEp
FWdchEdhJiyG22rNftco
=sxHI
-END PGP SIGNATURE End Message ---

Bug#817565: marked as done (lice5: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 19:05:25 +
with message-id 
and subject line Bug#817565: fixed in lice5 1:5.2.7-2
has caused the Debian Bug report #817565,
regarding lice5: 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.)


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

Hi,

The package lice5 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: lice5
Source-Version: 1:5.2.7-2

We believe that the bug you reported is fixed in the latest version of
lice5, 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.
Kurt Roeckx  (supplier of updated lice5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 20:56:20 +0200
Source: lice5
Binary: epic5-script-lice
Architecture: source
Version: 1:5.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Kurt Roeckx 
Changed-By: Kurt Roeckx 
Description:
 epic5-script-lice - Very functional script for epic
Closes: 817565
Changes:
 lice5 (1:5.2.7-2) unstable; urgency=medium
 .
   * Switch to debhelper compatibility level 9 (Closes: #817565)
   * Replace dh_clean -k with dh_prep
Checksums-Sha1:
 e493bd2b5cd4d16b00861e4622b9e1fdf0c5bd55 1640 lice5_5.2.7-2.dsc
 62028865d4eecdd3b99c01a2d8153c6300f84180 4108 lice5_5.2.7-2.debian.tar.xz
Checksums-Sha256:
 a365ba7c63bc3f2199a7d2d0feb167fc5a16d40781b07a64c6ef6b9abbef9873 1640 
lice5_5.2.7-2.dsc
 1571abf05616852c74bef0056fba25f489ec241574735f57bc4173ff7fef4d07 4108 
lice5_5.2.7-2.debian.tar.xz
Files:
 ca6999afbd61911c1531f785f7779dbc 1640 net optional lice5_5.2.7-2.dsc
 a68c71c1db719cb9d9c03a77c38426b8 4108 net optional lice5_5.2.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXlQ+vAAoJEOPE3c0eTBJEuagP/RXiksqabkpaaqbgvKyZKI+4
lKkd5XeM8STmG9+zW+lGws1JdQY8Nu2LPo3gzSz63SonBGnop8uBfx29YmoGS8Ru
ImnMccc/ZUViVThn43OJJCgtYk3lq+370lMIa0w6buanIkuhlcR5nU/w5Yrd1r4M
0logKv19/Dq32wuzrH8XKdhPgniV5yShy16+OfZ7sWkrnmUyJCiGBunqQ1FgVtAU
0pWHx26drwRIliuL7zNrr8idIYInQXSYxW3VxzzwUmz2Z2r9Xdxi4ZqdNTuo8e5Q
WPu+tvezyveAr5gwyJpeH3t7OWZmIXqL0Y+3kOazGkB49tukRj+otkLf7FcXywIn
ZjJLqhDbea/8HQr6KcpeAOvRj3fUlsDtSG6lgsWiPGHbTAMDFWTtr37MG1o/ClBF
ipgkHN73hP8GT3d5xfVrePr263y/dIxgMJScW5551xCDyuE3F3f+BtMUS4YDzv34
kko37zciBgC2YYXPryEjpMj19Kvm+BaxeqWoW6FeF0vcE03AgR/7ifE8ABu1G+VC
DTPTXtSLpgX9UtwrAsce2Cwj946E6oNEVNgolHN9USiVwNwPfUzw9ynxh32wr8cK
Wpien3cpTJty1TKs5PpwDCGWruvVc8ch0CsNs5AnBSeNwNCTAt6oDJVOzpfg3/B1
nMDTSEDx/R5yvFTVJz78
=jQ8R
-END PGP SIGNATURE End Message ---

Bug#831205: marked as done (mednafen: FTBFS with GCC 6: cdrom/CDAccess_CCD.cpp:349:20: error: call of overloaded 'abs(size_t)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 19:05:35 +
with message-id 
and subject line Bug#831205: fixed in mednafen 0.9.38.7+dfsg-2
has caused the Debian Bug report #831205,
regarding mednafen: FTBFS with GCC 6: cdrom/CDAccess_CCD.cpp:349:20: error: 
call of overloaded 'abs(size_t)' 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.)


-- 
831205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mednafen
Version: 0.9.38.7+dfsg-1
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++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I../include 
> -I../include -I../intl   -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char  
> -Wall -Wshadow -Wempty-body -Wignored-qualifiers -Wvla -Wvariadic-macros 
> -Wdisabled-optimization  -fno-fast-math -fno-unsafe-math-optimizations 
> -fno-aggressive-loop-optimizations -fomit-frame-pointer -fwrapv  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> cdrom/CDAccess_CCD.o cdrom/CDAccess_CCD.cpp
> cdrom/CDAccess_CCD.cpp: In member function 'void 
> CDAccess_CCD::CheckSubQSanity()':
> cdrom/CDAccess_CCD.cpp:349:20: error: call of overloaded 'abs(size_t)' is 
> ambiguous
>   if(abs(lba - s) > 100)
> ^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/ext/string_conversions.h:41,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/stdexcept:39,
>  from /usr/include/c++/6/array:39,
>  from /usr/include/c++/6/tuple:39,
>  from /usr/include/c++/6/functional:55,
>  from /usr/include/c++/6/memory:79,
>  from cdrom/../types.h:22,
>  from cdrom/../mednafen.h:4,
>  from cdrom/CDAccess_CCD.cpp:18:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/ext/string_conversions.h:41:0,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/stdexcept:39,
>  from /usr/include/c++/6/array:39,
>  from /usr/include/c++/6/tuple:39,
>  from /usr/include/c++/6/functional:55,
>  from /usr/include/c++/6/memory:79,
>  from cdrom/../types.h:22,
>  from cdrom/../mednafen.h:4,
>  from cdrom/CDAccess_CCD.cpp:18:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int 
> std::abs(long long int)
>abs(long long __x) { return __builtin_llabs (__x); }
>^~~
> /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
>abs(long __i) { return __builtin_labs(__i); }
>^~~
> make[4]: *** [cdrom/CDAccess_CCD.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/mednafen_0.9.38.7+dfsg-1_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: mednafen
Source-Version: 0.9.38.7+dfsg-2

We believe that the bug you reported is fixed in the latest version of
mednafen, 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

Bug#832366: sineshaper: does not start

[Jaromír Mikeš]

2016-07-24 20:09 GMT+02:00 James Cowgill :
> Package: sineshaper
> Version: 0.4.2-8
> Severity: grave
>
> Hi,
>
> sineshaper does not start properly. When run it gives the jack-dssi-
> host usage message:
>
> Usage: sineshaper [-v] [-a] [-n] [-p ] [-c ] [-] 
> [:] [...]
> [...]
>
> This is because the sineshaper dssi plugin is installed into
> /usr/lib//dssi which is not in the dssi search path (only
> /usr/lib/dssi is).
>
> Given that a bug this serious has not been reported in two years, maybe
> no-one uses this package?

Yes popcon is quite low ... 88 ... And I am not sure if it is developed.
I will ask upstream.

best regards

mira

Bug#817527: marked as done (libid3tag: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 18:38:46 +
with message-id 
and subject line Bug#817527: fixed in libid3tag 0.15.1b-12
has caused the Debian Bug report #817527,
regarding libid3tag: 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.)


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

Hi,

The package libid3tag 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: libid3tag
Source-Version: 0.15.1b-12

We believe that the bug you reported is fixed in the latest version of
libid3tag, 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.
Kurt Roeckx  (supplier of updated libid3tag package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 20:07:55 +0200
Source: libid3tag
Binary: libid3tag0 libid3tag0-dev
Architecture: source
Version: 0.15.1b-12
Distribution: unstable
Urgency: medium
Maintainer: Mad Maintainers 
Changed-By: Kurt Roeckx 
Description:
 libid3tag0 - ID3 tag reading library from the MAD project
 libid3tag0-dev - ID3 tag reading library from the MAD project
Closes: 698959 723192 817527
Changes:
 libid3tag (0.15.1b-12) unstable; urgency=medium
 .
   * Switch to debhelper compat level 9 (Closes: #817527)
   * Add multiarch support. Patch from Frédéric Brière 
 (Closes: #698959, #723192)
   * Add ${misc:Depends} to the Depends lines
   * Switch to "3.0 (quilt)" source format.
   * Use ${binary:Version} instead of ${Source-Version}
   * Don't disable debugging.
   * Add symbols file
   * Remove libid3tag.la
Checksums-Sha1:
 16cbc7724e30ed7aae620047c0b281782196f9c4 1943 libid3tag_0.15.1b-12.dsc
 0298a6909886f760976e2a99c9f9b589ebdecc4f 7508 
libid3tag_0.15.1b-12.debian.tar.xz
Checksums-Sha256:
 0b4fdbfbf6764f1008c0a2082ed0cb0feac3931e97324eb73ae1b2edf4aba3c8 1943 
libid3tag_0.15.1b-12.dsc
 c14bebb05158526c4a5384122c8f850c856c13d3db5046966b5523d0f876af96 7508 
libid3tag_0.15.1b-12.debian.tar.xz
Files:
 31c5fd4330a10bd64a2a63018722474d 1943 sound optional libid3tag_0.15.1b-12.dsc
 e6bbaffa83e3902df64e254be5af890e 7508 sound optional 
libid3tag_0.15.1b-12.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXlQeTAAoJEOPE3c0eTBJEzoAQAIE5mWInkppl0z3KVExl17vP
ymjOl9TPdAeUiZfd39sS4/ynJwayAjn/6GODA5NeG/RfcoZkjH/fmAVzyB2pSS2j
vubmNi7mT7FIQvz+QX1QiC2Q5YNj85FnYmRz9ikSp5FwismJKUITCfBkmGXw5Xej
4GgtRZSXvqJjR4toCyU6XKt58CjBo/LYOqflsj6iaNxKtrtiVM49qjEJPy2iuxIc
uKd3T3Iu0H1Nzfv5THKCjEg/6Qy8DPnG/lwLymZbZJ+C9rSJk7QENy/02FzRiWZ5
uLmVJI+nrlb09iamOuCLQA0EAG/PI/O6zFLBypy9OulX1NBT0tPM74SFehIjnUSJ
LsihZYjYVbsl+XA3y6qnGDB+tEktWbr2azRt1rBxDNB/1rshuasrcbmis6YaCJTc
VckcY6tj5sG7zPYXjTuU7J6EfzwFwtKgj2FVz5lwmSByUIo5aA8AdBIIQIIoAnfs
rm8ccozvLaRgKsm5nJ1u0tICvhRYddqEqxn22KHyIfwfluLXGU4cLyt97fZi05o5
ZXUY9dGYSRDyhbeCSM3pgMzDJCcgb/d7XZEXbXXXbMtWPgTY6+7xvVBLaCOUl8Ui
dlbIRD+x6+hL/G5oP0ZgawdnN6K09YgZ5ihjMVY++0p6kr3aBr011pInoTuKv1T6
hAEBgLkHKSHQgBjbqfIT
=jSPt
-END PGP SIGNATURE End Message ---

Processed: reassign 832366 to sineshaper

[Debian Bug Tracking System]

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

> reassign 832366 sineshaper 0.4.2-8
Bug #832366 [ sineshaper] sineshaper: does not start
Bug reassigned from package ' sineshaper' to 'sineshaper'.
Ignoring request to alter found versions of bug #832366 to the same values 
previously set
Ignoring request to alter fixed versions of bug #832366 to the same values 
previously set
Bug #832366 [sineshaper] sineshaper: does not start
Marked as found in versions sineshaper/0.4.2-8.
> thanks
Stopping processing here.

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

Bug#832366: sineshaper: does not start

[James Cowgill]

Package: sineshaper
Version: 0.4.2-8
Severity: grave

Hi,

sineshaper does not start properly. When run it gives the jack-dssi-
host usage message:

Usage: sineshaper [-v] [-a] [-n] [-p ] [-c ] [-] 
[:] [...]
[...]

This is because the sineshaper dssi plugin is installed into
/usr/lib//dssi which is not in the dssi search path (only
/usr/lib/dssi is).

Given that a bug this serious has not been reported in two years, maybe
no-one uses this package?

Thanks,
James

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

Processed: Re: Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=95176
Bug #832332 [src:linux] linux-image-4.6.0-1-amd64: Flickering X display for 
Intel HD 4600 (i915 driver)
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=95176'.

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

Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

[Vincent Bernat]

control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=95176

 ❦ 24 juillet 2016 19:10 CEST, Bram Bolder  :

> It was set to 1, changing it to 0 did not solve the problem (I stopped xdm,
> set the 0 and started it again).
>
> I did some further checking (kernel 4.5 has enable_psr=0 as default). I also
> noticed that producing load removed the flickering (e.g. glxgears). It's 
> definitively
> a power saving feature.
>
> I then tried to set i915.enable_psr=0 as commandline option in grub and this 
> solved
> my problem! Hooray!
>
>
> My question now is how to proceed with this problem. I'm quite sure that you 
> don't want
> everyone with my (or a similar) hardware setup to file a bugreport to you. 
> Maybe this
> problem gets fixes upstream at some point...

The functionality exists since quite some time but has been disabled
until 4.6. On my laptop (Haswell), it started working correctly from 4.6
too. Previous kernels where exhibiting the same problems that you
observed (but I was able to enable/disable this functionnality without
restarting anything). Therefore, it seems that upstream put some work
into this functionnality but it doesn't work for everyone.

> Do you want to close this ticket? The problem is solved for me, but
> maybe other users might experience the same problem.

I can't say, I am not the maintainer of the kernel in Debian, just a
user. You can try 4.7-rc7 in experimental. It seems the bug is already
reported upstream (and not solved in 4.7-rc7):

https://bugs.freedesktop.org/show_bug.cgi?id=96704
https://bugs.freedesktop.org/show_bug.cgi?id=96736
https://bugs.freedesktop.org/show_bug.cgi?id=96916
https://bugs.freedesktop.org/show_bug.cgi?id=95124
https://bugs.freedesktop.org/show_bug.cgi?id=95176

I mark the last one as a forwarded address for this bug (this seems the
most active one).
-- 
Use uniform input formats.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#831878: marked as done (cyphesis-cpp: fails to install in chroot: update-rc.d: error: no runlevel symlinks to modify, aborting!)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 18:04:02 +
with message-id 
and subject line Bug#831878: fixed in cyphesis-cpp 0.6.0-5
has caused the Debian Bug report #831878,
regarding cyphesis-cpp: fails to install in chroot: update-rc.d: error: no 
runlevel symlinks to modify, aborting!
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.)


-- 
831878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyphesis-cpp
Version: 0.6.0-4
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...):

  Selecting previously unselected package cyphesis-cpp.
  (Reading database ... 
(Reading database ... 9077 files and directories currently installed.)
  Preparing to unpack .../cyphesis-cpp_0.6.0-4_amd64.deb ...
  Unpacking cyphesis-cpp (0.6.0-4) ...
  Setting up cyphesis-cpp (0.6.0-4) ...
  update-rc.d: error: no runlevel symlinks to modify, aborting!
  dpkg: error processing package cyphesis-cpp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   cyphesis-cpp


This may be related to the fact that piuparts installs the package in a 
minimal chroot, but I've never seen this error message from update-rc.d
(but there have been quite some changes w.r.t. the initscript helpers
recnetly) and most packages behave "sanely" in such a setup.


cheers,

Andreas


cyphesis-cpp_0.6.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cyphesis-cpp
Source-Version: 0.6.0-5

We believe that the bug you reported is fixed in the latest version of
cyphesis-cpp, 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.
Olek Wojnar  (supplier of updated cyphesis-cpp 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, 20 Jul 2016 20:12:09 -0400
Source: cyphesis-cpp
Binary: cyphesis-cpp cyphesis-cpp-clients cyphesis-cpp-mason
Architecture: source
Version: 0.6.0-5
Distribution: unstable
Urgency: high
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Description:
 cyphesis-cpp - WorldForge game server
 cyphesis-cpp-clients - WorldForge game server - clients to control the server
 cyphesis-cpp-mason - WorldForge game server - game data for Mason
Closes: 831878
Changes:
 cyphesis-cpp (0.6.0-5) unstable; urgency=high
 .
   * Fix error in update-rc.d (Closes: #831878)
Checksums-Sha1:
 6db309a38efbfa35933ac6dee1edba44231ee244 2393 cyphesis-cpp_0.6.0-5.dsc
 659090f13d9cf50d94719d31c7719a3c0f0e2d35 18340 
cyphesis-cpp_0.6.0-5.debian.tar.xz
Checksums-Sha256:
 0f6f1df137444a0aa72306080184a719e67360a561a7747f7746eefa8470671c 2393 
cyphesis-cpp_0.6.0-5.dsc
 5e4fa9f07e7dd72c0e3431765595ec7da126b93af93a2e472b071cac1e371b64 18340 
cyphesis-cpp_0.6.0-5.debian.tar.xz
Files:
 ed88972780868377429c21aaf313fd19 2393 games optional cyphesis-cpp_0.6.0-5.dsc
 c1aceac243e31b29e5617b64c979f57c 18340 games optional 
cyphesis-cpp_0.6.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXlQGTAAoJEJFk+h0XvV02hhcQANf4+T7szy5/hXuiYjYhhNHi
jkgXHn17v3BeevmmWfI5gd4Q6nLPfl0T8wrG8dMTU1TV8nHjiomORFQpSFlLWHCO
dZYA4XGUDVMYqEItjPRMPqF3Tku5ZY0v71AWO1yNWdxjqM1AVFL59xg+WPjm1/8n
2NimaGL+CCYIdP4FYPdeIgpaJgDJ1zWaSFzkFc5eIP1iNAb3kSNr1XwSajBpc9Ez
dQp/Boaq1gWq7WxNr+8+AhPVXd80/UrNMDW7DvtOprbBp+JFK1zA/9yvW3EMPzgS
KCgGu3hjuCS1CB1aMN6bJyDZp/3UlcE7bgOI5TVPifofXJqIyyied6RUmdInQFao
vsFCHDbQ6NSlHzgxWEeoNZ05FtJxUQDQBpC8fqK7UeNRUhedOi+Wkuo6z5+ehdzG
0Ml7XVhql3SQxd+yVxU1Xx9JMlZh3bq7pEwNv6XxDNgFrjeOm2FJWjh0U1PMBpH7
ISI+Wj+VCSAlRtryO255THaDS/CAoigS+UX2ZjwOtTtIShW7ICOm4ksNyaE+jfPg
4Uj3J+oP/6ZzekZdDU5SK0y+KlePCmbUoTE+Nsl4eABCfQGTMn85Avsw4heZFf7M

Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

[Bram Bolder]

Hello Vincent,

thanks for your reply.

On 07/24/2016 04:19 PM, Vincent Bernat wrote:

 ❦ 24 juillet 2016 13:45 CEST, Bram Bolder  :


after upgrading the meta package 'linux-image-amd64' from 
linux-image-4.5.0-2-amd64
to linux-image-4.6.0-1-amd64 (and rebooting), my laptop screen started to 
flicker
annoyingly. At first I thought it was a hardware defect (backlight lamp reaching
its end of life), but booting an Ubuntu or reverting to the 4.5.0-2 does not 
show
any flickering. The normal terminals (alt-F1 through alt-F6) do not flicker.

My laptop has seen many generations of Linux images while using 'Debian 
testing',
all without problems, so it must be related to this latest kernel version.
I tried a clean installation of SID (i.e. without explicitly configuring xorg),
but it reproduces the flickering.


Is /sys/module/i915/parameters/enable_psr set to 1? If yes, can you try
to set it to 0 and check if the problem goes away (no need to restart
anything).


It was set to 1, changing it to 0 did not solve the problem (I stopped xdm,
set the 0 and started it again).

I did some further checking (kernel 4.5 has enable_psr=0 as default). I also
noticed that producing load removed the flickering (e.g. glxgears). It's 
definitively
a power saving feature.

I then tried to set i915.enable_psr=0 as commandline option in grub and this 
solved
my problem! Hooray!


My question now is how to proceed with this problem. I'm quite sure that you 
don't want
everyone with my (or a similar) hardware setup to file a bugreport to you. 
Maybe this
problem gets fixes upstream at some point...

Do you want to close this ticket? The problem is solved for me, but maybe other 
users
might experience the same problem.


Thanks for your help,

Bram

Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Sun, 24 Jul 2016 11:43:19 -0500 Don Armstrong wrote:

[...]
> I'll try to check out snapshots
> later this week to see if I can figure out when the transition actually
> happened, or if there was something else going on in the archive to
> explain it.

Thanks for your help!
Please keep us informed, as the investigations go on.

Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpdGlHzJLlhD.pgp
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 17:00:11 +
with message-id 
and subject line Bug#821967: fixed in bitlbee 3.4.2-1.1
has caused the Debian Bug report #821967,
regarding bitlbee: 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.)


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

Hi,

The package bitlbee 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 bitlbee builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to bitlbee 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, bitlbee 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: bitlbee
Source-Version: 3.4.2-1.1

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

Debian distribution maintenance software
pp.
Michael Lustfield  (supplier of updated bitlbee 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: Mon, 18 Jul 2016 01:02:17 -0700
Source: bitlbee
Binary: bitlbee bitlbee-libpurple bitlbee-common bitlbee-dev bitlbee-plugin-otr 
bitlbee-plugin-skype skyped
Architecture: source all amd64
Version: 3.4.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Wilmer van der Gaast 
Changed-By: Michael Lustfield 
Description:
 bitlbee- IRC to other chat networks gateway (default version)
 bitlbee-common - IRC to other chat networks gateway (common files/docs)
 bitlbee-dev - IRC to other chat networks gateway (dev files)
 bitlbee-libpurple - IRC to other chat networks gateway (using libpurple)
 bitlbee-plugin-otr - IRC to other chat networks gateway (OTR plugin)
 bitlbee-plugin-skype - IRC to other chat networks gateway (Skype plugin)
 skyped - Daemon to control Skype remotely
Closes: 821967
Changes:
 bitlbee (3.4.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adding build-{arch,indep} targets. (Closes: #821967)
   * Added python to build depends.
Checksums-Sha1:
 467349fcbaf02f45ff9fdc965a7e2a1de129a640 2277 bitlbee_3.4.2-1.1.dsc
 f1a43e786c444f89fcb1f90c981df847b10c50be 22455 bitlbee_3.4.2-1.1.diff.gz
 c0f47bb996b5a35ef2c7af552be6f0b3922130bc 77700 bitlbee-common_3.4.2-1.1_all.deb
 dd2e74cc1d4780e25767032957bf782bea713183 29038 bitlbee-dev_3.4.2-1.1_all.deb
 b772b2d25f6fb970fe226812f94f2327c9eb85f9 123668 
bitlbee-libpurple_3.4.2-1.1_amd64.deb
 8bcd887ac9387b45bd7e607613ca01efdde0fefb 38696 
bitlbee-plugin-otr-dbgsym_3.4.2-1.1_amd64.deb
 c45bae6a195e773515cf5fc26aec9e7df5205d7b 17270 
bitlbee-plugin-otr_3.4.2-1.1_amd64.deb
 fb00efd81e02cb93b81fe210b2ae97f6cc71ae84 227642 bitlbee_3.4.2-1.1_amd64.deb
Checksums-Sha256:
 da0a2099c164c38a4d21f45802d1fd951f42948a0be1d93135e0af6e811b4472 2277 
bitlbee_3.4.2-1.1.dsc
 9ac1eebc6c962c3b03c73c7f4703fee9d649d54e162344336aa61723174a98a2 22455 
bitlbee_3.4.2-1.1.diff.gz
 5991264ba3ca3d3010d233ec1625e37c3caec63f921065bab2c309f8643a1eec 77700 
bitlbee-common_3.4.2-1.1_all.deb
 14c477fbc8ec0c7cd5b73aaf5dee3b30d3f0f6223d44964ed3a886be178dbac0 29038 
bitlbee-dev_3.4.2-1.1_all.deb
 d07fad4cbb70678a7ccc1f083af798559c23e5b721ade86d1a5cde983d702eda 123668 
bitlbee-libpurple_3.4.2-1.1_amd64.deb
 a02e5070ba673c43fec9f435a76e43ce81fd00efbf6af542138c202377b3e694 38696 
bitlbee-plugin-otr-dbgsym_3.4.2-1.1_amd64.deb
 

Bug#832361: marked as done (libmousex-getopt-perl: FTBFS: Failed 2/22 test programs. 2/356 subtests failed.)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 16:52:06 +
with message-id 
and subject line Bug#832361: fixed in libmousex-getopt-perl 0.37-1
has caused the Debian Bug report #832361,
regarding libmousex-getopt-perl: FTBFS: Failed 2/22 test programs. 2/356 
subtests failed.
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.)


-- 
832361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmousex-getopt-perl
Version: 0.36-1
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,

libmousex-getopt-perl fails to build from source in unstable/amd64:

  [..]

  ok 46 - ... libs is [] as expected
  ok 47 - ... details is { os => mac, name => foo } as expected
  ok 48 - An object of class 'App' isa 'App'
  ok 49 - ... verbosity is turned off as expected
  ok 50 - ... length is 24 as expected
  ok 51 - ... file is file.dat as expected
  ok 52 - ... libs is [] as expected
  ok 53 - ... details is {} as expected
  ok 54 - An object of class 'App' isa 'App'
  ok 55 - cmd_alias, but not using it
  ok 56 - An object of class 'App' isa 'App'
  ok 57 - cmd_alias, using long one
  ok 58 - An object of class 'App' isa 'App'
  ok 59 - cmd_alias, using short one
  ok 60 - An object of class 'App' isa 'App'
  ok 61 - cmd_alias+cmd_flag, using flag
  ok 62 - An object of class 'App' isa 'App'
  ok 63 - cmd_alias+cmd_flag, using alias
  ok 64 - An object of class 'App' isa 'App'
  ok 65 - _foo + cmd_flag
  ok 66 - An object of class 'App' isa 'App'
  ok 67 - ARGV accessor
  ok 68 - @ARGV unmangled
  ok 69 - extra_argv accessor
  ok
  t/007_nogetopt_trait.t  
  1..9
  ok 1 - use MouseX::Getopt;
  ok 2 - An object of class 'App' isa 'App'
  ok 3 - ... verbosity is off as expected
  ok 4 - ... length is 24 as expected
  ok 5 - ... data is file.dat as expected
  ok 6 - ... libs is [] as expected
  ok 7 - ... details is {} as expected
  ok 8 - ... private stuff is 713 as expected
  ok 9 - threw Regexp ((?^:Unknown option: private_stuff))
  ok
  t/008_configfromfile.t  
  1..37
  ok 1 - threw Regexp ((?^:Mandatory parameter 'required_from_config' missing))
  ok 2 - An object of class 'App::DefaultConfigFile' isa 
'App::DefaultConfigFile'
  ok 3 - ... required_from_config is from_config_1 as expected
  ok 4 - ... optional_from_config is from_config_2 as expected
  ok 5 - ... required_from_argv is 1 as expected
  ok 6 - ... config_from_override false as expected
  ok 7 - ... configfile is /notused/default as expected
  ok 8 - An object of class 'App::DefaultConfigFileCodeRef' isa 
'App::DefaultConfigFileCodeRef'
  ok 9 - ... required_from_config is from_config_1 as expected
  ok 10 - ... optional_from_config is from_config_2 as expected
  ok 11 - ... required_from_argv is 1 as expected
  ok 12 - ... config_from_override false as expected
  ok 13 - ... configfile is /notused/default as expected
  ok 14 - An object of class 'App' isa 'App'
  ok 15 - ... required_from_config is from_config_1 as expected
  ok 16 - ... optional_from_config is from_config_2 as expected
  ok 17 - ... required_from_argv is 1 as expected
  ok 18 - An object of class 'App::DefaultConfigFile' isa 
'App::DefaultConfigFile'
  ok 19 - ... required_from_config is from_config_1 as expected
  ok 20 - ... optional_from_config is from_config_2 as expected
  ok 21 - ... required_from_argv is 1 as expected
  ok 22 - ... config_from_override true as expected
  ok 23 - ... configfile is /notused as expected
  ok 24 - An object of class 'App::DefaultConfigFileCodeRef' isa 
'App::DefaultConfigFileCodeRef'
  ok 25 - ... required_from_config is from_config_1 as expected
  ok 26 - ... optional_from_config is from_config_2 as expected
  ok 27 - ... required_from_argv is 1 as expected
  ok 28 - ... config_from_override true as expected
  ok 29 - ... configfile is /notused as expected
  ok 30 - threw Regexp ((?^:Mandatory parameter 'required_from_argv' missing))
  ok 31 - An object of class 'App' isa 'App'
  ok 32 - ... required_from_config is override as expected
  ok 33 - ... optional_from_config is from_config_2 as expected
  ok 34 - An object of class 'App' isa 'App'
  ok 35 - ... required_from_config is noconfig as expected
  ok 36 - ... optional_from_config is undef as expected
  ok 37 - Can create DerivedApp
  ok
  t/009_gld_and_explicit_options.t .. 
  1..5
  ok 1 - use MouseX::Getopt;
  ok 2 - ... this 

Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Don Armstrong]

On Sun, 24 Jul 2016, Francesco Poli wrote:
> On Sun, 24 Jul 2016 16:24:19 +0100 Jonathan Wiltshire wrote:
> 
> > On 2016-07-24 16:00, Francesco Poli wrote:
> [...]
> > > Should  be contacted, perhaps?
> > 
> > Sure, if you'd like to.
> 
> Dear BTS owner,
> could you please investigate on what happened to bug #830267 on
> 2016-07-19T10:00 ?
> 
> Please take a look at
> https://bugs.debian.org/830267#20
> https://bugs.debian.org/830267#25
> for more context.

Hrm; it was shown as affecting testing at T0600 (and all subsequent
runs):

status-201607190600:number=830267
status-201607190600-testing=1
status-201607190600-unstable=1

but not on the immediately preceding run:

status-20160719:number=830267
status-20160719-testing=0
status-20160719-unstable=1

(You can check this out with grep -C 14 number=830267
/srv/bugs.debian.org/bugscan/stati/status-201607{19,20}*; on buxtehude or by
getting those status files from the web interface and examining them.)

That's really odd; I haven't changed anything on the BTS side during
that time period which would explain that happening.

Unfortunately, I don't know when the BTS thought that 1.18.9 was
actually in testing and not in unstable. I'll try to check out snapshots
later this week to see if I can figure out when the transition actually
happened, or if there was something else going on in the archive to
explain it.

-- 
Don Armstrong  https://www.donarmstrong.com

Americans can always be counted on to do the right thing, after they
have exhausted all other possibilities.
 -- W. Churchill

Bug#832344: [Pkg-iscsi-maintainers] Bug#832344: open-isns-server: unowned files after purge (policy 6.8, 10.8): /etc/isns/auth_key

[Christian Seiler]

On 07/24/2016 05:35 PM, Andreas Beckmann wrote:
> On 2016-07-24 17:10, Christian Seiler wrote:
>> Thinking about this again: since this package uses debconf
>> anyway, it's probably much easier to just ask the user whether
>> to delete auth_key or not in -server's postrm (with the default
>> being yes), instead of doing this pseudo-refcounted dance in
>> all postrms. It's probably also more transparent to the user.
> 
> If multiple packages make use of this facility, this sounds like
> management of the auth_key should be factored out to a separate package
> that is used by all the consumers. So you could get proper refcounting
> via Depends: isns-auth-key

The problem is that there are too many different ways of how that
file could be created, so I can't have a package actually own it
(otherwise I'd have made libisns0 itself own it), because there is
no sane default for it. (If you want to run a server, you'd want
to generate it; but if you don't want to run a server, you might
want to copy it from the server you've generated it on.) And if I
make it a default-missing conffile for another package, piuparts
will complain about a conffile of another package being modified.

I'll hence go the debconf route for now. But thank you for the
suggestion.

Regards,
Christian

Bug#824944: Bug #824944, upstream version confusion

[Roland Hieber]

On Mon, 4 Jul 2016 18:19:04 -0400 Jason Pleau  wrote:
> I also noticed the version string in debian/changelog didn't really
> match anything that upstream released. (I can't find 2.1.8 anywhere)

While trying to reproduce this, I cannot find lua-discount 2.1.8 on
upstream [0] either. Could it be that you confused the version of
lua-discount with that of the discount C library? Or has the upstream
URL changed to somewhere else?

[0]: either one of
 http://luaforge.net/projects/lua-discount/
 http://asbradbury.org/projects/lua-discount/
 https://github.com/asb/lua-discount/

Cheers,

 - Roland

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

[Colin Watson]

On Sun, Jul 24, 2016 at 01:38:25AM +0200, Michael Biebl wrote:
> I referenced in my other reply that the network.target ordering has just
> been added recently (in v230). So it is possible that previously there
> was still an issue on shutdown. This is fixed now.

Do you plan to update jessie with this fix?  I ask because I've had
requests to make this openssh change available in jessie-backports.

> Besides, there are many other reasons why you really want libpam-systemd
> in combination with SSH.
> You really want the user process be tracked as part of the user session,
> so you can properly apply resource limits or safely kill user sessions.

Sure.  But non-systemd users don't need libpam-systemd at all in this
case (I'm aware that there are other cases where they may do), and it's
just noise for them; and in the case of a package such as openssh-server
that's often installed on very minimal systems indeed, they may not
previously have needed to deal with resolving libpam-systemd's
dependencies.  Unfortunately there's no good way to say "Depends:
libpam-systemd, but only if systemd is pid 1".

It's unfortunate that we don't have a good way to simply be able to
assume that all systemd users have libpam-systemd installed, which is
what I'd really prefer to be able to do here.

> > I think I'll add a Recommends on it, but I really want
> > openssh-server to be usable on very minimal systems, including those
> > using other init systems, without having to deal with dependency
> > strangenesses.
> 
> Please disable the ssh-session-cleanup.service hack by default if you
> don't want to remove it. Or better, ship it as an example file.

Compromise proposal: how about I make it do nothing if libpam-systemd is
installed (e.g. "ConditionPathExists=!/usr/share/pam-configs/systemd",
which is probably the simplest available check without needing to deal
with multiarch paths), in which case presumably the hack isn't needed?
(For backports to jessie, such a check would need to be deleted, unless
you plan to backport the ordering fix as requested above.)

> I really don't what such service file be installed (and active) by
> default on every system. People might see it and think it's actually ok
> to apply such hacks.

I'd be happy to add a warning comment to discourage that.  The script is
short enough that such a comment would be unlikely to be overlooked.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#831725: marked as done (nut: FTBFS on some 64-bit architectures with symbols mismatches)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 16:22:39 +
with message-id 
and subject line Bug#831725: fixed in nut 2.7.4-3
has caused the Debian Bug report #831725,
regarding nut: FTBFS on some 64-bit architectures with symbols mismatches
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.)


-- 
831725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nut
Version: 2.7.4-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The builds of nut for arm64, mips64, and ppc64el all failed with
symbol mismatches:

  dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libnutclient0/DEBIAN/symbols doesn't match 
completely debian/libnutclient0.symbols
  --- debian/libnutclient0.symbols (libnutclient0_2.7.4-2_arm64)
  +++ dpkg-gensymbolsIJjzJg  2016-07-18 17:22:14.968019944 +
  @@ -1,4 +1,8 @@
   libnutclient.so.0 libnutclient0 #MINVER#
  + _ZN3nut8internal6Socket4readEPvm@Base 2.7.4-2
  + _ZN3nut8internal6Socket5writeEPKvm@Base 2.7.4-2
  + 
_ZN3nut9TcpClient7explodeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEm@Base
 2.7.4-2
  + 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St6vectorIS5_SaIS5_EEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base
 2.7.4-2
(c++)"nut::Client::Client()@Base" 2.7.3
(c++)"nut::Client::getDevice(std::__cxx11::basic_string const&)@Base" 2.7.3
(c++)"nut::Client::getDeviceVariableValues(std::__cxx11::basic_string const&)@Base" 2.7.3
  @@ -72,7 +76,7 @@
(c++)"nut::TcpClient::disconnect()@Base" 2.7.3
(c++)"nut::TcpClient::escape(std::__cxx11::basic_string const&)@Base" 2.7.3
(c++)"nut::TcpClient::executeDeviceCommand(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string 
const&)@Base" 2.7.3
  - (c++|arch=!alpha !amd64 
!s390x)"nut::TcpClient::explode(std::__cxx11::basic_string const&, unsigned int)@Base" 2.7.4
  +#MISSING: 2.7.4-2# (c++|arch=!alpha !amd64 
!s390x)"nut::TcpClient::explode(std::__cxx11::basic_string const&, unsigned int)@Base" 2.7.4
(c++|arch=alpha amd64 
s390x)"nut::TcpClient::explode(std::__cxx11::basic_string const&, unsigned long)@Base" 
2.7.4
(c++)"nut::TcpClient::get(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string 
const&)@Base" 2.7.3
(c++)"nut::TcpClient::getDevice(std::__cxx11::basic_string const&)@Base" 2.7.3

Please take advantage of modern dpkg-gensymbols' support for arch-bits
tags by substituting arch-bits=32 for "arch=!alpha !amd64 !s390x: and
arch-bits=64 for "arch=alpha amd64 s390x".  This feature first became
available in dpkg 1.18.0, so you probably ought to declare a versioned
build dependency because the version in stable is too old (1.17.27).

Thanks!
--- End Message ---
--- Begin Message ---
Source: nut
Source-Version: 2.7.4-3

We believe that the bug you reported is fixed in the latest version of
nut, 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.
Laurent Bigonville  (supplier of updated nut 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, 24 Jul 2016 16:40:24 +0200
Source: nut
Binary: nut nut-server nut-client nut-cgi nut-snmp nut-ipmi nut-xml 
nut-powerman-pdu nut-doc libupsclient4 libupsclient-dev libnutclient0 
libnutclient-dev 

Bug#832306: marked as done (dh-strip-nondeterminism: png file handling is messed up)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 16:22:58 +
with message-id 
and subject line Bug#832306: fixed in strip-nondeterminism 0.022-1
has caused the Debian Bug report #832306,
regarding dh-strip-nondeterminism: png file handling is messed up
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.)


-- 
832306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-strip-nondeterminism
Version: 0.020-1
Severity: grave

Hi,

The new version of dh-strip-nondeterminism messes up handling of png
files. This is a regression from 0.019-1

When run on kmidimon which I was working on, 0.020-1 gives (and doesn't
fail on):

dh_strip_nondeterminism -pkmidimon 
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/qjackctl.png: invalid length 
in ��I� header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/kmidimon1.png: invalid 
length in >�7H header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/kmidimon3.png: invalid 
length in R��k header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/kmidimon2.png: invalid 
length in 

��3 header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/qjackctl.png: invalid length 
in ��I� header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/kmidimon1.png: invalid 
length in >�7H header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/kmidimon3.png: invalid 
length in R��k header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/kmidimon2.png: invalid 
length in 

��3 header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/icons/hicolor/64x64/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/48x48/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/24x24/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/128x128/apps/kmidimon.png: invalid 
length in HYs header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/icons/hicolor/32x32/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/16x16/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.

It then proceeds to write out a load of dodgy looking files into the
package. Output from debc (note the random filenames which were not
there before):

drwxr-xr-x root/root 0 2016-07-24 00:17 ./usr/share/icons/hicolor/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/128x128/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/128x128/apps/
-rw-r--r-- root/root  4330 2016-07-23 21:03 
./usr/share/icons/hicolor/128x128/apps/kmidimon.png
-rw-r--r-- root/root  1893 2016-07-24 00:17 
./usr/share/icons/hicolor/128x128/apps/rCuFnLpl3Z
drwxr-xr-x root/root 0 2016-07-24 00:17 ./usr/share/icons/hicolor/16x16/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/16x16/apps/
-rw-r--r-- root/root33 2016-07-24 00:17 
./usr/share/icons/hicolor/16x16/apps/9wtJKNTsBO
-rw-r--r-- root/root   478 2016-07-23 21:03 
./usr/share/icons/hicolor/16x16/apps/kmidimon.png
drwxr-xr-x root/root 0 2016-07-24 00:17 ./usr/share/icons/hicolor/24x24/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/24x24/apps/
-rw-r--r-- root/root33 2016-07-24 00:17 
./usr/share/icons/hicolor/24x24/apps/a1X6RR9dWI
-rw-r--r-- root/root   694 2016-07-23 21:03 

Bug#828893: marked as done (epic4-help: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 16:21:36 +
with message-id 
and subject line Bug#828893: fixed in epic4-help 1:2.0+20050315-3
has caused the Debian Bug report #828893,
regarding epic4-help: FTBFS: dh_clean: Please specify the compatibility level 
in debian/compat
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.)


-- 
828893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: epic4-help
Version: 1:2.0+20050315-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,

epic4-help fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  epic4-help
   Version:  2.0+20050315-2
   Build architecture:   amd64
   Date: Tue, 28 Jun 2016 21:18:40 +0200
   Hostname: ef3d6f3c38d0
   Uname:Linux ef3d6f3c38d0 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'epic4-help-build-deps' in 
'../epic4-help-build-deps_2.0+20050315-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package epic4-help-build-deps.
  (Reading database ... 23073 files and directories currently installed.)
  Preparing to unpack epic4-help-build-deps_2.0+20050315-2_all.deb ...
  Unpacking epic4-help-build-deps (1:2.0+20050315-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up epic4-help-build-deps (1:2.0+20050315-2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=ef3d6f3c38d0
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160628211838.BnS7CqtsWh.epic4-help/epic4-help-2.0+20050315
  OLDPWD=/home/lamby/temp/cdt.20160628211838.BnS7CqtsWh.epic4-help
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building epic4-help 2.0+20050315-2 on amd64
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package epic4-help
  dpkg-buildpackage: info: source version 1:2.0+20050315-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Kurt Roeckx 
   dpkg-source --before-build epic4-help-2.0+20050315
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  rm -f build
  rm -rf debian/epic4-help debian/files* core debian/substvars
   

Bug#832361: libmousex-getopt-perl: FTBFS: Failed 2/22 test programs. 2/356 subtests failed.

[Chris Lamb]

Source: libmousex-getopt-perl
Version: 0.36-1
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,

libmousex-getopt-perl fails to build from source in unstable/amd64:

  [..]

  ok 46 - ... libs is [] as expected
  ok 47 - ... details is { os => mac, name => foo } as expected
  ok 48 - An object of class 'App' isa 'App'
  ok 49 - ... verbosity is turned off as expected
  ok 50 - ... length is 24 as expected
  ok 51 - ... file is file.dat as expected
  ok 52 - ... libs is [] as expected
  ok 53 - ... details is {} as expected
  ok 54 - An object of class 'App' isa 'App'
  ok 55 - cmd_alias, but not using it
  ok 56 - An object of class 'App' isa 'App'
  ok 57 - cmd_alias, using long one
  ok 58 - An object of class 'App' isa 'App'
  ok 59 - cmd_alias, using short one
  ok 60 - An object of class 'App' isa 'App'
  ok 61 - cmd_alias+cmd_flag, using flag
  ok 62 - An object of class 'App' isa 'App'
  ok 63 - cmd_alias+cmd_flag, using alias
  ok 64 - An object of class 'App' isa 'App'
  ok 65 - _foo + cmd_flag
  ok 66 - An object of class 'App' isa 'App'
  ok 67 - ARGV accessor
  ok 68 - @ARGV unmangled
  ok 69 - extra_argv accessor
  ok
  t/007_nogetopt_trait.t  
  1..9
  ok 1 - use MouseX::Getopt;
  ok 2 - An object of class 'App' isa 'App'
  ok 3 - ... verbosity is off as expected
  ok 4 - ... length is 24 as expected
  ok 5 - ... data is file.dat as expected
  ok 6 - ... libs is [] as expected
  ok 7 - ... details is {} as expected
  ok 8 - ... private stuff is 713 as expected
  ok 9 - threw Regexp ((?^:Unknown option: private_stuff))
  ok
  t/008_configfromfile.t  
  1..37
  ok 1 - threw Regexp ((?^:Mandatory parameter 'required_from_config' missing))
  ok 2 - An object of class 'App::DefaultConfigFile' isa 
'App::DefaultConfigFile'
  ok 3 - ... required_from_config is from_config_1 as expected
  ok 4 - ... optional_from_config is from_config_2 as expected
  ok 5 - ... required_from_argv is 1 as expected
  ok 6 - ... config_from_override false as expected
  ok 7 - ... configfile is /notused/default as expected
  ok 8 - An object of class 'App::DefaultConfigFileCodeRef' isa 
'App::DefaultConfigFileCodeRef'
  ok 9 - ... required_from_config is from_config_1 as expected
  ok 10 - ... optional_from_config is from_config_2 as expected
  ok 11 - ... required_from_argv is 1 as expected
  ok 12 - ... config_from_override false as expected
  ok 13 - ... configfile is /notused/default as expected
  ok 14 - An object of class 'App' isa 'App'
  ok 15 - ... required_from_config is from_config_1 as expected
  ok 16 - ... optional_from_config is from_config_2 as expected
  ok 17 - ... required_from_argv is 1 as expected
  ok 18 - An object of class 'App::DefaultConfigFile' isa 
'App::DefaultConfigFile'
  ok 19 - ... required_from_config is from_config_1 as expected
  ok 20 - ... optional_from_config is from_config_2 as expected
  ok 21 - ... required_from_argv is 1 as expected
  ok 22 - ... config_from_override true as expected
  ok 23 - ... configfile is /notused as expected
  ok 24 - An object of class 'App::DefaultConfigFileCodeRef' isa 
'App::DefaultConfigFileCodeRef'
  ok 25 - ... required_from_config is from_config_1 as expected
  ok 26 - ... optional_from_config is from_config_2 as expected
  ok 27 - ... required_from_argv is 1 as expected
  ok 28 - ... config_from_override true as expected
  ok 29 - ... configfile is /notused as expected
  ok 30 - threw Regexp ((?^:Mandatory parameter 'required_from_argv' missing))
  ok 31 - An object of class 'App' isa 'App'
  ok 32 - ... required_from_config is override as expected
  ok 33 - ... optional_from_config is from_config_2 as expected
  ok 34 - An object of class 'App' isa 'App'
  ok 35 - ... required_from_config is noconfig as expected
  ok 36 - ... optional_from_config is undef as expected
  ok 37 - Can create DerivedApp
  ok
  t/009_gld_and_explicit_options.t .. 
  1..5
  ok 1 - use MouseX::Getopt;
  ok 2 - ... this should work
  ok 3 - An object of class 'Testing::Foo' isa 'Testing::Foo'
  ok 4 - ... got the right values
  ok 5 - ... got the right values
  ok
  t/010_dashes.t  
  1..5
  ok 1 - use MouseX::Getopt;
  ok 2 - Dash in option name
  ok 3 - threw Regexp ((?^:Unknown option: some_thingy))
  ok 4 - Underscore in option name
  ok 5 - threw Regexp ((?^:Unknown option: another-thingy))
  ok
  t/100_gld_default_bug.t ... 
  1..5
  ok 1 - use MouseX::Getopt;
  ok 2 - An object of class 'Engine::Foo' isa 'Engine::Foo'
  ok 3 - ... got the right value (10), not the default (1)
  ok 4 - An object of class 'Engine::Foo' isa 'Engine::Foo'
  ok 5 - ... got the right value (1), without GLD needing to handle defaults
  ok
  t/101_argv_bug.t .. 
  1..3
  ok 1 - An object of class 'App' isa 'App'
  ok 2 - ... verbosity is turned on as expected
  ok 3 - ... 

Bug#832155: New ssh-session-cleanup.service kills ssh user session during upgrade

[Michael Biebl]

Am 24.07.2016 um 17:47 schrieb Colin Watson:
> On Sun, Jul 24, 2016 at 01:38:25AM +0200, Michael Biebl wrote:

>> I referenced in my other reply that the network.target ordering has just
>> been added recently (in v230). So it is possible that previously there
>> was still an issue on shutdown. This is fixed now.
> 
> Do you plan to update jessie with this fix? 

I can do that. Unfortunately I've already filed the jessie-pu bug for
systemd a couple of hours ago (#832336, for 8.6), but I could update the
pu request accordingly.
I see what I can do, otherwise it will be in the next stable point
release, i.e 8.7

> dependencies.  Unfortunately there's no good way to say "Depends:
> libpam-systemd, but only if systemd is pid 1".

Right, we do not have conditional Depends. But since sysvinit-core is
the only existing alternative in stretch, we could use Depends:
libpam-systemd | sysvinit-core. It's slighly ugly but would probably do
the trick.


> It's unfortunate that we don't have a good way to simply be able to
> assume that all systemd users have libpam-systemd installed, which is
> what I'd really prefer to be able to do here.

I am more and more inclined that we should simply make libpam-systemd a
hard dependency of either systemd or systemd-sysv.

>> Please disable the ssh-session-cleanup.service hack by default if you
>> don't want to remove it. Or better, ship it as an example file.
> 
> Compromise proposal: how about I make it do nothing if libpam-systemd is
> installed (e.g. "ConditionPathExists=!/usr/share/pam-configs/systemd",
> which is probably the simplest available check without needing to deal
> with multiarch paths), in which case presumably the hack isn't needed?
> (For backports to jessie, such a check would need to be deleted, unless
> you plan to backport the ordering fix as requested above.)

I'm still pretty much convinced that a hack like this should not be
shipped by default, which is totally unnecessary for a default
installation. It set's a wrong precedent.
If we start piling up hacks like this, in 10 years we are back at that
mess that sysvinit has become.

Regards,
Michael

-- 
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#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Sun, 24 Jul 2016 16:24:19 +0100 Jonathan Wiltshire wrote:

> On 2016-07-24 16:00, Francesco Poli wrote:
[...]
> > Should  be contacted, perhaps?
> 
> Sure, if you'd like to.

Dear BTS owner,
could you please investigate on what happened to bug #830267 on
2016-07-19T10:00 ?

Please take a look at
https://bugs.debian.org/830267#20
https://bugs.debian.org/830267#25
for more context.

Thanks for your time.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp7w_rRAV1H3.pgp
Description: PGP signature

Bug#832344: open-isns-server: unowned files after purge (policy 6.8, 10.8): /etc/isns/auth_key

[Andreas Beckmann]

On 2016-07-24 17:10, Christian Seiler wrote:
> Thinking about this again: since this package uses debconf
> anyway, it's probably much easier to just ask the user whether
> to delete auth_key or not in -server's postrm (with the default
> being yes), instead of doing this pseudo-refcounted dance in
> all postrms. It's probably also more transparent to the user.

If multiple packages make use of this facility, this sounds like
management of the auth_key should be factored out to a separate package
that is used by all the consumers. So you could get proper refcounting
via Depends: isns-auth-key


Andreas

Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Jonathan Wiltshire]

On 2016-07-24 16:00, Francesco Poli wrote:

I hope it's possible to investigate further, in order to find out what
really happened: needless to say, I think that the correctness of the
migration process is of great importance to the quality of Debian
testing (and, consequently, of future stable releases!).

Should  be contacted, perhaps?


Sure, if you'd like to.

--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Processed: Re: Bug#832357: bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director

[Debian Bug Tracking System]

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

> tags 832357 + pending
Bug #832357 
[bacula-director-sqlite3,bacula-director-mysql,bacula-director-pgsql] 
bacula-director-*: fails to upgrade from 'sid' - trying to overwrite 
/etc/init.d/bacula-director
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#832357: bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director

[Carsten Leonhardt]

tags 832357 + pending
thanks

Hi Andreas,

thank you for your bug report. The problem is already fixed in our git
repository, but we want to finish some further packaging changes before
the next upload.

Carsten

Processed: affects 831872, found 638426 in 2.02-0-1, found 673972 in 6.1.25~dfsg-1 ..., found 775385 in 1.18.2-2 ...

[Debian Bug Tracking System]

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

> affects 831872 + spamassassin-heatu
Bug #831872 [spamassassin] spamassassin: fails to install: error: gpg required 
but not found!
Added indication that 831872 affects spamassassin-heatu
> found 638426 2.02-0-1
Bug #638426 [aspell-sk] debsums reports that some aspell-sk files have changed
Marked as found in versions aspell-sk/2.02-0-1.
> found 673972 6.1.25~dfsg-1
Bug #673972 [sympa] sympa: unowned directories after purge: /var/spool/sympa/*
Marked as found in versions sympa/6.1.25~dfsg-1.
> found 690216 idutch/1:2.10-5
Bug #690216 [piuparts.debian.org] [bug for tracking] aspell dictionary hash 
handling upgrades that will be done in jessie+x
The source idutch and version 1:2.10-5 do not appear to match any binary 
packages
Marked as found in versions idutch/1:2.10-5.
> found 788253 gfarm/2.6.11+dfsg-2
Bug #788253 [init-system-helpers] gfsd: unowned files after purge (policy 6.8, 
10.8): /var/lib/systemd/deb-systemd-helper-masked/gfsd.service
Marked as found in versions gfarm/2.6.11+dfsg-2.
> found 775385 1.18.2-2
Bug #775385 [lightdm] lightdm: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions lightdm/1.18.2-2.
> found 771085 3.20.1-1
Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions gdm3/3.20.1-1.
> found 825121 4.4.2-3
Bug #825121 [libradcli4] libradcli4: prompting due to modified conffiles which 
were not modified by the user: /etc/radcli/dictionary
There is no source info for the package 'libradcli4' at version '4.4.2-3' with 
architecture ''
Unable to make a source version for version '4.4.2-3'
Marked as found in versions 4.4.2-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
638426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638426
673972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673972
690216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690216
771085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771085
775385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775385
788253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788253
825121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825121
831872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#832357: [pkg-bacula-devel] Bug#832357: bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director

[Sven Hartge]

On 24.07.2016 16:44, Andreas Beckmann wrote:

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

Yes, this is my fault and already fixed in GIT and will be fixed in the
archive with the next upload to experimental.

Grüße,
Sven.





signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#832344: open-isns-server: unowned files after purge (policy 6.8, 10.8): /etc/isns/auth_key

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #832344 [open-isns-server] open-isns-server: unowned files after purge 
(policy 6.8, 10.8): /etc/isns/auth_key
Removed tag(s) moreinfo.
> tags -1 + confirmed
Bug #832344 [open-isns-server] open-isns-server: unowned files after purge 
(policy 6.8, 10.8): /etc/isns/auth_key
Added tag(s) confirmed.
> severity -1 serious
Bug #832344 [open-isns-server] open-isns-server: unowned files after purge 
(policy 6.8, 10.8): /etc/isns/auth_key
Severity set to 'serious' from 'important'

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

Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Sun, 24 Jul 2016 13:51:45 +0100 Jonathan Wiltshire wrote:

> On 2016-07-24 11:20, Francesco Poli wrote:
[...]
> > Dear Release Team, could you please explain what I failed to understand
> > about the testing migration rules [2]?
> 
> Your understanding is correct - an RC bug affecting sid and not testing 
> is considered a regression and blocks migration, whereas one which 
> affects both suites does not.

Good, thanks for confirming!

> 
> Britney is fed that information from the BTS. The migration happened 
> because on 2016-07-18T22:00 #830267 was a regression, but on 
> 2016-07-19T10:00 it was marked as also affecting testing, so the package 
> was migrated. I don't know what happened in the BTS to cause that 
> change, certainly nothing on the bug log that I can see.

I hope it's possible to investigate further, in order to find out what
really happened: needless to say, I think that the correctness of the
migration process is of great importance to the quality of Debian
testing (and, consequently, of future stable releases!).

Should  be contacted, perhaps?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp7iCVI5JhDc.pgp
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> tags 831137 fixed-upstream
Bug #831137 [src:kodi] kodi: FTBFS with GCC 6: stl_algobase.h:243:56: error: 
macro "min" passed 3 arguments, but takes just 2
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Bug#832357: bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director

[Andreas Beckmann]

Package: bacula-director-sqlite3,bacula-director-mysql,bacula-director-pgsql
Version: 7.4.3+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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...):

  Preparing to unpack .../bacula-director-sqlite3_7.4.3+dfsg-2_amd64.deb ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of stop.
  Unpacking bacula-director-sqlite3 (7.4.3+dfsg-2) over (7.4.3+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/bacula-director-sqlite3_7.4.3+dfsg-2_amd64.deb 
(--unpack):
   trying to overwrite '/etc/init.d/bacula-director', which is also in package 
bacula-director-common 7.4.3+dfsg-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Preparing to unpack .../bacula-director-common_7.4.3+dfsg-2_amd64.deb ...
  Unpacking bacula-director-common (7.4.3+dfsg-2) over (7.4.3+dfsg-1) ...
  Preparing to unpack .../bacula-common_7.4.3+dfsg-2_amd64.deb ...
  Unpacking bacula-common (7.4.3+dfsg-2) over (7.4.3+dfsg-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/bacula-director-sqlite3_7.4.3+dfsg-2_amd64.deb

Same problem in the other bacula-director-* backends.

Does switching between e.g. bacula-director-sqlite3 and bacula-director-mysql
work without problems if both packages ship /etc/init.d/bacula-director?


cheers,

Andreas


bacula-director-sqlite3_7.4.3+dfsg-2.log.gz
Description: application/gzip

Processed: Bug#821992

[Debian Bug Tracking System]

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

> tags 821992 + patch
Bug #821992 [icinga] icinga: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Bug#821967

[Debian Bug Tracking System]

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

> tags 821967 + patch
Bug #821967 [bitlbee] bitlbee: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) patch.
> tags 821967 + pending
Bug #821967 [bitlbee] bitlbee: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#832355: ktap: module FTBFS for Linux 4.6: error: '__GFP_WAIT' undeclared

[Andreas Beckmann]

Package: ktap
Version: 0.4+git20160427-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

the module FTBFS for the current kernel in testing and unstable:

# less /var/lib/dkms/ktapvm/0.4+git20160427-1/build/make.log
DKMS make.log for ktapvm-0.4+git20160427-1 for kernel 4.6.0-1-amd64 (x86_64)
Sun Jul 24 14:13:51 UTC 2016
make: Entering directory '/usr/src/linux-headers-4.6.0-1-amd64'
CHK libelf
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/Makefile:108: No libelf found, 
disables symbol resolving, please install elfutils-libelf-devel
  CC [M]  /var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/amalg.o
  LD  /var/lib/dkms/ktapvm/0.4+git20160427-1/build/built-in.o
In file included from 
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/amalg.c:23:0:
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c: In function 
'kp_malloc':
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c:47:8: error: 
'__GFP_WAIT' undeclared (first use in this function)
 & ~__GFP_WAIT)
^
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c:59:23: note: in 
expansion of macro 'KTAP_ALLOC_FLAGS'
  addr = kmalloc(size, KTAP_ALLOC_FLAGS);
   ^
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c:47:8: note: each 
undeclared identifier is reported only once for each function it appears in
 & ~__GFP_WAIT)
^
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c:59:23: note: in 
expansion of macro 'KTAP_ALLOC_FLAGS'
  addr = kmalloc(size, KTAP_ALLOC_FLAGS);
   ^
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c: In function 
'kp_zalloc':
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c:47:8: error: 
'__GFP_WAIT' undeclared (first use in this function)
 & ~__GFP_WAIT)
^
/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/kp_obj.c:70:23: note: in 
expansion of macro 'KTAP_ALLOC_FLAGS'
  addr = kzalloc(size, KTAP_ALLOC_FLAGS);
   ^
/usr/src/linux-headers-4.6.0-1-common/scripts/Makefile.build:296: recipe for 
target '/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/amalg.o' failed
make[3]: *** [/var/lib/dkms/ktapvm/0.4+git20160427-1/build/runtime/amalg.o] 
Error 1
/usr/src/linux-headers-4.6.0-1-common/Makefile:1446: recipe for target 
'_module_/var/lib/dkms/ktapvm/0.4+git20160427-1/build' failed
make[2]: *** [_module_/var/lib/dkms/ktapvm/0.4+git20160427-1/build] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.6.0-1-amd64'


Andreas

PS: could you move the kernel module to a separate ktap-dkms package?

Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

[Vincent Bernat]

 ❦ 24 juillet 2016 13:45 CEST, Bram Bolder  :

> after upgrading the meta package 'linux-image-amd64' from 
> linux-image-4.5.0-2-amd64
> to linux-image-4.6.0-1-amd64 (and rebooting), my laptop screen started to 
> flicker
> annoyingly. At first I thought it was a hardware defect (backlight lamp 
> reaching
> its end of life), but booting an Ubuntu or reverting to the 4.5.0-2 does not 
> show
> any flickering. The normal terminals (alt-F1 through alt-F6) do not flicker.
>
> My laptop has seen many generations of Linux images while using 'Debian 
> testing',
> all without problems, so it must be related to this latest kernel version.
> I tried a clean installation of SID (i.e. without explicitly configuring 
> xorg),
> but it reproduces the flickering.

Is /sys/module/i915/parameters/enable_psr set to 1? If yes, can you try
to set it to 0 and check if the problem goes away (no need to restart
anything).
-- 
Don't just echo the code with comments - make every comment count.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#817491: marked as done (haskell98-tutorial: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 13:33:39 +
with message-id 
and subject line Bug#817491: fixed in haskell98-tutorial 26-2-1.2
has caused the Debian Bug report #817491,
regarding haskell98-tutorial: 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.)


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

Hi,

The package haskell98-tutorial 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: haskell98-tutorial
Source-Version: 26-2-1.2

We believe that the bug you reported is fixed in the latest version of
haskell98-tutorial, 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.
Bill Allombert  (supplier of updated haskell98-tutorial 
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: SHA1

Format: 1.8
Date: Sun, 24 Jul 2016 14:26:38 +0200
Source: haskell98-tutorial
Binary: haskell98-tutorial
Architecture: source all
Version: 26-2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Ian Lynagh (wibble) 
Changed-By: Bill Allombert 
Description:
 haskell98-tutorial - A Gentle Introduction to Haskell 98
Closes: 817491
Changes:
 haskell98-tutorial (26-2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control, debian/compat: move to debhelper 5. Closes: #817491
   * debian/rules: use dh_prep instead of dh_clean -k
Checksums-Sha1:
 0c6f087b5ae3c99a329ba91995ea73927c1cecbe 1803 
haskell98-tutorial_26-2-1.2.dsc
 7eb58ea28ab1ac0ff51cf725c2349d75e640a4d0 4008 
haskell98-tutorial_26-2-1.2.diff.gz
 7562f3872998e19673f5b905a0b949a0c95a3bd3 95450 
haskell98-tutorial_26-2-1.2_all.deb
Checksums-Sha256:
 c836dd00fbba95aa0eaea8420d64cdd9f3ec3b39865df69af276e87a75b276f4 1803 
haskell98-tutorial_26-2-1.2.dsc
 6105eafb0781a8c885e004947fc9b34e4f9b71670ba72021bba2ae7ebf66bd7f 4008 
haskell98-tutorial_26-2-1.2.diff.gz
 485624a782c649c3266a947fb2a5e9fa2d05756e349cd78552d6ae9d6250b0b5 95450 
haskell98-tutorial_26-2-1.2_all.deb
Files:
 30a31c35dc596b94490c06df0079 1803 doc optional 
haskell98-tutorial_26-2-1.2.dsc
 761a090d66a68d0647d1c87a02fca1b7 4008 doc optional 
haskell98-tutorial_26-2-1.2.diff.gz
 c70afd2a4e29783053c114943a19d7d6 95450 doc optional 
haskell98-tutorial_26-2-1.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXlLeQAAoJEI8OfCtFIuOHGA4P/0uc14y9+nhgrp97ACUaMZM6
kOlS5mPzozfZC022WBjkLgoI8I9z4w9fVl+iNm3IhG0QcrXbZKqlqk6OuOaxd3W5
xCx/Vtc3jVUlsWnZ+p18GSKiNis1PzEOJ1OinqpyeJAkG7S9rLoyM64p+myg2RjK
mAIfpu9OBd8EkaSFxPxGp8fv5z1lIZlR5/gq8D6KygNaBsvzx2LOjtAwNXTgz6LI
HIQ+AKUcxFr/6X5Um+LkaLQYiFpnwslNUa8nfJnxWc6hzhmOO3BwdTpUwoFEiMo0
2UKbYhY9y8MYC4sGG/AzhW4em0oy5R2cWpKtog1dY/bIAdsm2DBdrVyI130mjP6D
kNYeRcJCZiWMG3Rq6psuDKkhgsysu4+TwN0G5sprsxqr4CWWHZ/9a6VPktPnyWMo
zxiWCLTXtSkPhEQYrdnUG4M2VtmogoSSivCTYSNNfUk1uCMizoICt85S8a1z25R8
ZxvdbTfkVgI4YCRZdtZaFOcyl+/W+vzH5qfw+/NaBEAjXWI56dDDDRSnejN02C38
aWmJP1K8JmHomOxR0qmSGf+n+cpYF/OjmLECnaJUvHq0Wptr/x0GbapLqdSWyKRX
yp/F3Di66IOrLAEenNoZuKzoIa7cIzWnSmGBtxWBqTbEwbk1PPoP09rzxHYBEGmo
euEk83Y5a+JaAf8yn8ch
=d+aB
-END PGP SIGNATURE End Message ---

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Faidon Liambotis]

On Sun, Jul 24, 2016 at 02:53:57PM +0200, Sebastian Ramacher wrote:
> On 2016-07-24 14:19:36, Sebastian Ramacher wrote:
> > Thank you for the info. Could you please let us know the version of libva1 
> > and
> > i965-va-driver that you have installed?
> 
> … and the versions of all other libva1-* packages.

All of the above[1] are at 1.7.1-1. I run a pretty standard up-to-date
testing -- with the exception of all ffmpeg packages from sid, as
previously requested.

Faidon

1:
ii  i965-va-driver:amd64 1.7.1-1 amd64 VAAPI driver for Intel G45 & HD Graphics 
fami
ii  libva-drm1:amd64 1.7.1-1 amd64 Video Acceleration (VA) API for Linux -- 
DRM 
ii  libva-glx1:amd64 1.7.1-1 amd64 Video Acceleration (VA) API for Linux -- 
GLX 
ii  libva-wayland1:amd64 1.7.1-1 amd64 Video Acceleration (VA) API for Linux -- 
Wayl
ii  libva-x11-1:amd641.7.1-1 amd64 Video Acceleration (VA) API for Linux -- 
X11 
ii  libva1:amd64 1.7.1-1 amd64 Video Acceleration (VA) API for Linux -- 
runt

Bug#828120: view3dscene: FTBFS: convert: Non-conforming drawing primitive definition (push)

[Paul Gevers]

Upstream graphicsmagick created a fix for the issue. I prodded the
graphicsmagick maintainers to see if they are going to upload it to
Debian. Otherwise, we will work around it some other way.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#802081: marked as done (kmetronome: FTBFS: add_custom_target cannot create target "uninstall")

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 13:03:28 +
with message-id 
and subject line Bug#802081: fixed in kmetronome 0.10.1-2
has caused the Debian Bug report #802081,
regarding kmetronome: FTBFS: add_custom_target cannot create target "uninstall"
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.)


-- 
802081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmetronome
Version: 0.10.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

-- kmetronome 0.10.1 install prefix: /usr
CMake Warning (dev) at /usr/lib/automoc4/Automoc4Config.cmake:179 
(get_directory_property):
  Policy CMP0059 is not set: Do no treat DEFINITIONS as a built-in directory
  property.  Run "cmake --help-policy CMP0059" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.
Call Stack (most recent call first):
  /usr/lib/automoc4/Automoc4Config.cmake:243 (_add_automoc4_target)
  /usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:1026 
(_automoc4_kde4_pre_target_handling)
  src/CMakeLists.txt:71 (KDE4_ADD_EXECUTABLE)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Error at CMakeLists.txt:129 (ADD_CUSTOM_TARGET):
  add_custom_target cannot create target "uninstall" because another target
  with the same name already exists.  The existing target is a custom target
  created in source directory "/kmetronome-0.10.1".  See documentation for
  policy CMP0002 for more details.


-- Configuring incomplete, errors occurred!
See also "/kmetronome-0.10.1/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
See also "/kmetronome-0.10.1/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
"tail -v -n +0 CMakeCache.txt"

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/kmetronome.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: kmetronome
Source-Version: 0.10.1-2

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated kmetronome package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 13:26:08 +0100
Source: kmetronome
Binary: kmetronome
Architecture: source
Version: 0.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 kmetronome - ALSA MIDI Metronome
Closes: 802081
Changes:
 kmetronome (0.10.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Remove uninstall target from CMakeLists.txt, fixing FTBFS. (Closes: 
#802081)
   * Use debhelper compat 9 to ensure build flags are passed correctly.
   * Fix helper-templates-in-copyright lintian error.
   * Use canonical Vcs URLs.
   * Remove menu file per tech-ctte decision.
   * Bump standards to 3.9.8.
Checksums-Sha1:
 72b28ee3fd7abebad1cb29165b373aa452862b69 2086 kmetronome_0.10.1-2.dsc
 78b494b34bfb93cff17e3c191fd90cdfb4b0439d 2444 kmetronome_0.10.1-2.debian.tar.xz
Checksums-Sha256:
 cad1b326b0d2989c2f2f60d043da99fa725f6b016d0e83ebab069b38bab4211f 2086 
kmetronome_0.10.1-2.dsc
 e300fcf88c44cc1b468d0b80ecfde1b05a6e3ba0455788dafc329141427c6f70 2444 
kmetronome_0.10.1-2.debian.tar.xz
Files:
 c4f34620ed2573fbd5e909955f9ad93f 2086 sound extra kmetronome_0.10.1-2.dsc
 1a82d33a9a4595faec3d253daac418e8 2444 sound extra 
kmetronome_0.10.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXlLZ5AAoJEMfxZ23qLQHvvngQAJ9//HFDz042vP5yKGcLl05W
wgE6hP81Bh+ftxIHEaSVgtKQxmdS6+ip6Wm+czNNfo3Lxzn9x8bF5NybMI3XlXzl

Bug#803566: marked as done (kmidimon: FTBFS: add_custom_target cannot create target "uninstall")

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 13:03:33 +
with message-id 
and subject line Bug#803566: fixed in kmidimon 0.7.5-2
has caused the Debian Bug report #803566,
regarding kmidimon: FTBFS: add_custom_target cannot create target "uninstall"
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.)


-- 
803566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmidimon
Version: 0.7.5-1
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,

kmidimon fails to build from source in unstable/amd64:

  [..]

  -- checking for module 'drumstick-alsa>=0.5'
  --   found drumstick-alsa, version 0.5.0
  -- kmidimon 0.7.5 install prefix: /usr
  CMake Warning (dev) at /usr/lib/automoc4/Automoc4Config.cmake:179
  (get_directory_property):
Policy CMP0059 is not set: Do no treat DEFINITIONS as a built-in
directory
property.  Run "cmake --help-policy CMP0059" for policy details. 
Use the
cmake_policy command to set the policy and suppress this warning.
  Call Stack (most recent call first):
/usr/lib/automoc4/Automoc4Config.cmake:243 (_add_automoc4_target)
/usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:1026
(_automoc4_kde4_pre_target_handling)
src/CMakeLists.txt:68 (KDE4_ADD_EXECUTABLE)
  This warning is for project developers.  Use -Wno-dev to suppress it.
  
  CMake Error at CMakeLists.txt:135 (ADD_CUSTOM_TARGET):
add_custom_target cannot create target "uninstall" because another
target
with the same name already exists.  The existing target is a custom
target
created in source directory
"/home/lamby/temp/cdt.20151031125942.DIQJT2tM3F/kmidimon-0.7.5". 
See
documentation for policy CMP0002 for more details.
  
  
  -- Configuring incomplete, errors occurred!
  See also
  
"/home/lamby/temp/cdt.20151031125942.DIQJT2tM3F/kmidimon-0.7.5/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
  See also
  
"/home/lamby/temp/cdt.20151031125942.DIQJT2tM3F/kmidimon-0.7.5/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
  /usr/share/cdbs/1/class/cmake.mk:55: recipe for target
  'obj-x86_64-linux-gnu/CMakeCache.txt' failed
  make: *** [obj-x86_64-linux-gnu/CMakeCache.txt] Error 1

  [..]

The full build log is attached.


Regards,

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


kmidimon.0.7.5-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kmidimon
Source-Version: 0.7.5-2

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated kmidimon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 Jul 2016 13:26:55 +0100
Source: kmidimon
Binary: kmidimon
Architecture: source
Version: 0.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 kmidimon   - MIDI monitor using ALSA sequencer and KDE user interface
Closes: 803566
Changes:
 kmidimon (0.7.5-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Radovan Birdic ]
   * Remove uninstall target from CMakeLists.txt, fixing FTBFS. (Closes: 
#803566)
 .
   [ James Cowgill ]
   * Use canonical Vcs URLs.
   * Remove menu file per tech-ctte decision.
   * Bump standards to 3.9.8.
Checksums-Sha1:
 d0d4c249feaf508d0b7f72a34181755be503b08a 2040 kmidimon_0.7.5-2.dsc
 e7d5ebc5280731edfaa983edf0dc614f989db55c 2948 kmidimon_0.7.5-2.debian.tar.xz
Checksums-Sha256:
 8988ee5d9e57b99f2b36bf64b2d953c5e0ee72b0d251792eecdeea805dfcba3a 2040 
kmidimon_0.7.5-2.dsc
 fd98322e355d67a00a035fe777cb7d9ebe7e4162bed77b25d46dd975c310ee8d 2948 

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Sebastian Ramacher]

On 2016-07-24 14:19:36, Sebastian Ramacher wrote:
> Hi
> 
> On 2016-07-22 13:27:09, Faidon Liambotis wrote:
> > On Fri, Jul 22, 2016 at 10:21:05AM +0200, Sebastian Ramacher wrote:
> > > Unfortunately I am unable to reproduce the issue. Since there are some 
> > > accounts
> > > of random crashes when building ffmpeg with tree vectorization enabled, 
> > > I've
> > > uploaded 7:3.1.1-3 with vectorization disabled. Could you please check if 
> > > the
> > > issue disappears with -3?
> > 
> > I upgraded all ffmpeg packages to 7:3.1.1-3 but I'm still experiencing
> > crashes.
> > 
> > I then installed libavcodec57-dbgsym, libgstreamer1.0-0-dbg,
> > gstreamer1.0-libav-dbg and gstreamer1.0-plugins-good-dbg. The full
> > backtrace is below. The "codec = " seems
> > relevant, since this is on an Intel Broadwell, which may not be the case
> > for you. This looks a lot like #831529, doesn't it?
> > 
> > I still don't exactly understand how H.264/VA-API are related when playing
> > just a .wav file, though... This was with the same gstreamer pipeline,
> >   gst-launch-1.0 filesrc location=/usr/share/sounds/purple/alert.wav  !
> >   wavparse ! audioconvert ! fakesink
> > 
> > 
> > #0  0x76fc01c8 in __GI_raise (sig=sig@entry=6)
> > at ../sysdeps/unix/sysv/linux/raise.c:54
> > #1  0x76fc164a in __GI_abort () at abort.c:89
> > #2  0x7fffeda6260b in init_context_defaults (s=s@entry=0x70095720, 
> > codec=codec@entry=0x7fffee3a8900 )
> > at src/libavcodec/options.c:142
> > #3  0x7fffeda626d6 in avcodec_alloc_context3 (codec=0x7fffee3a8900 
> > ) at src/libavcodec/options.c:163
> > #4  0x7fffef360540 in gst_ffmpeg_cfg_install_property 
> > (klass=0x70095200, base=8) at gstavcfg.c:732
> > #5  0x7fffef356e53 in gst_ffmpegvidenc_class_init (klass=0x70095200)
> > at gstavvidenc.c:225
> > #6  0x7788c22d in g_type_class_ref (pclass=0x70094690, 
> > node=0x70094500) at 
> > /build/glib2.0-vjfO_h/glib2.0-2.48.1/./gobject/gtype.c:2241
> > #7  0x7788c22d in g_type_class_ref (type=type@entry=140737220527360)
> > at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./gobject/gtype.c:2956
> > #8  0x77b09da4 in gst_element_register 
> > (plugin=plugin@entry=0x69bbf0 [GstPlugin], name=name@entry=0x7006d110 
> > "avenc_h264_vaapi", rank=rank@entry=128, type=type@entry=140737220527360) 
> > at gstelementfactory.c:243
> > #9  0x7fffef3575b3 in gst_ffmpegvidenc_register 
> > (plugin=plugin@entry=0x69bbf0 [GstPlugin]) at gstavvidenc.c:1009
> > #10 0x7fffef349e20 in plugin_init (plugin=0x69bbf0 [GstPlugin])
> > at gstav.c:158
> > #11 0x77b2b537 in gst_plugin_register_func (plugin=0x69bbf0 
> > [GstPlugin], desc=0x7fffef578180 , user_data=0x0) at 
> > gstplugin.c:523
> > #12 0x77b2d425 in _priv_gst_plugin_load_file_for_registry 
> > (filename=0x6c2e20 
> > "/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so", registry=0x61c150 
> > [GstRegistry], registry@entry=0x0, error=error@entry=0x74de7bf0)
> > at gstplugin.c:826
> > #13 0x77b2dcea in gst_plugin_load_file (filename=, 
> > error=error@entry=0x74de7bf0) at gstplugin.c:680
> > #14 0x77b2e12c in gst_plugin_load_by_name (name=0x6c218d "libav")
> > at gstplugin.c:1265
> > #15 0x77b2ea8d in gst_plugin_feature_load 
> > (feature=feature@entry=0x6e58a0 [GstTypeFindFactory]) at 
> > gstpluginfeature.c:111
> > #16 0x77b547e3 in gst_type_find_factory_call_function 
> > (factory=0x6e58a0 [GstTypeFindFactory], find=0x74de7c90) at 
> > gsttypefindfactory.c:210
> > #17 0x75d89421 in gst_type_find_helper_for_data 
> > (obj=obj@entry=0x812070 [GstWavParse], data=, 
> > size=, prob=prob@entry=0x74de7db4) at 
> > gsttypefindhelper.c:535
> > #18 0x75d895a4 in gst_type_find_helper_for_buffer 
> > (obj=obj@entry=0x812070 [GstWavParse], buf=buf@entry=0x70003450, 
> > prob=prob@entry=0x74de7db4)
> > at gsttypefindhelper.c:591
> > #19 0x75b3546a in gst_wavparse_add_src_pad (wav=wav@entry=0x812070 
> > [GstWavParse], buf=0x70003450) at gstwavparse.c:1908
> > #20 0x75b35b47 in gst_wavparse_stream_data (wav=wav@entry=0x812070 
> > [GstWavParse]) at gstwavparse.c:2061
> > #21 0x75b3bbb1 in gst_wavparse_loop (pad=0x8042a0 [GstPad])
> > at gstwavparse.c:2202
> > #22 0x77b4fe71 in gst_task_func (task=0x81c050 [GstTask])
> > at gsttask.c:332
> > #23 0x775bc55e in g_thread_pool_thread_proxy (data=) 
> > at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthreadpool.c:307
> > #24 0x775bbbc5 in g_thread_proxy (data=0x81a800) at 
> > /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthread.c:780
> > #25 0x77335464 in start_thread (arg=0x74de8700) at 
> > pthread_create.c:333
> > #26 0x7707430d in clone () at 
> > ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> 
> Thank you for the info. Could you please let us know the version of libva1 and
> i965-va-driver that 

Bug#818830: marked as done (xless: FTBFS with libc 2.23: #error "The GNU C Library no longer implements .")

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 12:50:20 +
with message-id 
and subject line Bug#818830: fixed in xless 1.7-14.3
has caused the Debian Bug report #818830,
regarding xless: FTBFS with libc 2.23: #error "The GNU C Library no longer 
implements ."
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.)


-- 
818830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xless
Version: 1.7-14.2
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.23

This package fails to build with libc6 2.23 (2.23-0experimental0 from
experimental).

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> gcc -O2 -Wall -fno-strength-reduce -I/usr/X11R6/include -DDEBIAN -c util.c
> gcc -O2 -Wall -fno-strength-reduce -I/usr/X11R6/include -DDEBIAN -c 
> callbacks.c
> In file included from callbacks.c:39:0:
> /usr/include/regexp.h:30:2: error: #error "The GNU C Library no longer 
> implements ."
>  #error "The GNU C Library no longer implements ."
>   ^
> /usr/include/regexp.h:31:2: error: #error "Please update your code to use 
>  instead (no trailing 'p')."
>  #error "Please update your code to use  instead (no trailing 'p')."
>   ^
> callbacks.c: In function 'find':
> callbacks.c:163:3: error: unknown type name 'regex_t'
>regex_t pat;
>^
> callbacks.c:164:3: error: unknown type name 'regmatch_t'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: xless
Source-Version: 1.7-14.3

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

Debian distribution maintenance software
pp.
Bill Allombert  (supplier of updated xless 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: SHA1

Format: 1.8
Date: Sun, 24 Jul 2016 11:40:24 +0200
Source: xless
Binary: xless
Architecture: source amd64
Version: 1.7-14.3
Distribution: unstable
Urgency: medium
Maintainer: Felipe Augusto van de Wiel (faw) 
Changed-By: Bill Allombert 
Description:
 xless  - file browsing tool for the X Window System
Closes: 818830
Changes:
 xless (1.7-14.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Navin to fix FTBFS with new libc (Closes: #818830)
   * debian/rules:
 - use dh_prep instead of dh_clean -k
 - call dh_strip with --no-automatic-dbgsym
Checksums-Sha1:
 23e58c3622b29176aad668dcb838b9123b14e01a 1765 xless_1.7-14.3.dsc
 007acdb94eccb81d16ca44eabf8d5eea23151e1c 6845 xless_1.7-14.3.diff.gz
 8c63e6cf1e862759295e5cc9b008375931dab5d9 21480 xless_1.7-14.3_amd64.deb
Checksums-Sha256:
 1852913059e5a9d5197fc5dd376fd220fa1fe7cefda60ed0d178d396e80f7648 1765 
xless_1.7-14.3.dsc
 1b334fd872b639ca37433699be9a2e2ee68112c27b5ba50576e8ea74d335bfd7 6845 
xless_1.7-14.3.diff.gz
 c9db1ecfca5d1de9b749abf359e1205ebe6dc870cc6429377c771d0e22d23dac 21480 
xless_1.7-14.3_amd64.deb
Files:
 9e240147abeb97521033fd06949fa73a 1765 text optional xless_1.7-14.3.dsc
 1825170b1e2bf830d96134b657e4a83f 6845 text optional xless_1.7-14.3.diff.gz
 9448cf860d2b86c4ff88b84274930b5b 21480 text optional xless_1.7-14.3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXlKmHAAoJEI8OfCtFIuOHbP4P/26D70Kpdrbi8LLDIqg7kHZP
U53FmeNkpLjUl6c9y2ghr0XUcltwaZdoiX1cCMqyI8LWfaPOjcHZXjXQjFeL61+i
QiJjctdU0Bm4WWeSMPv0APijzkqCaSScE3T+iA2KdMFY+qYGwaWe64ucrM560Nul
1t93/P+kbw2Q/aG5hxoIPcRgOgAzcSbca2zJTgZeuqZShB/HMAIFz1wb5m85AXrh
Q1Een2/eFhUie7/xMbVON7CO/GamWw6XP83hsoFjWzxx+yfSCYZ9rMiylnMiV01G
SdCuQlbvlsRXAanJu6ucMYxOongKrhdXmUOZAaRU0t4G7szVWAQ5FSgaQTc4Fdf1
21Zllx2+OtMjiHjFdsjjaQV8YGTAEepBcL+BI8paYBG4KgKg/+VVxNcJyOrdq7HD
S384Rz4nuBXDlyZdnVQSd7RJMnVQDuD6rScj21gHS95E/hY2SJNvhT00k8B0wXjV
+j+dORVgMU8FR1v+no4COOXDy1HZICkpBLrap2sxYuLmuPfwFfPLWJNO5llhSPac
pWQn8nP1Y7DVcPHOf11Pt9k+T3QbiqBkbO3j20e+i3EzU4FfPgw/mSNLw7Y4N865
i+k3o8mGz4gHba3oFR8fZwzmjPeFJrFr2ZMFWjd9uP/Zm/UtlcBMEGlnfMeSB6n0
g7ed7rWGkRTf8INrk/AK
=HgpG
-END PGP SIGNATURE End 

Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Jonathan Wiltshire]

On 2016-07-24 11:20, Francesco Poli wrote:
In the meanwhile, dpkg/1.18.9 managed to migrate to testing [1], 
despite

introducing this RC bug: I wonder how that was even possible... do the
testing migration checks skip pending RC bugs?!? a pending bug is not a
fixed bug!!! I am Cc-ing the Release Team about this.

Dear Release Team, could you please explain what I failed to understand
about the testing migration rules [2]?


Your understanding is correct - an RC bug affecting sid and not testing 
is considered a regression and blocks migration, whereas one which 
affects both suites does not.


Britney is fed that information from the BTS. The migration happened 
because on 2016-07-18T22:00 #830267 was a regression, but on 
2016-07-19T10:00 it was marked as also affecting testing, so the package 
was migrated. I don't know what happened in the BTS to cause that 
change, certainly nothing on the bug log that I can see.


It now, of course, correctly affects both sid and testing, so it is no 
longer a regression and further migrations will happen (notwithstanding 
other bugs affecting dpkg in sid).


--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#817409: couriergraph: diff for NMU version 0.25-4.4

[Salvatore Bonaccorso]

Control: tags 817409 + patch
Control: tags 817409 + pending

Dear maintainer,

I've prepared an NMU for couriergraph (versioned as 0.25-4.4) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -u couriergraph-0.25/debian/control couriergraph-0.25/debian/control
--- couriergraph-0.25/debian/control
+++ couriergraph-0.25/debian/control
@@ -2,7 +2,7 @@
 Section: admin
 Priority: extra
 Maintainer: Jose Luis Tallon 
-Build-Depends: debhelper (>= 4.2)
+Build-Depends: debhelper (>= 9)
 Build-Depends-Indep: po-debconf (>= 0.8.2)
 Standards-Version: 3.7.3
 
diff -u couriergraph-0.25/debian/changelog couriergraph-0.25/debian/changelog
--- couriergraph-0.25/debian/changelog
+++ couriergraph-0.25/debian/changelog
@@ -1,3 +1,10 @@
+couriergraph (0.25-4.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump Debhelper compat level to 9 (Closes: #817409)
+
+ -- Salvatore Bonaccorso   Sun, 24 Jul 2016 14:45:40 +0200
+
 couriergraph (0.25-4.3) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u couriergraph-0.25/debian/compat couriergraph-0.25/debian/compat
--- couriergraph-0.25/debian/compat
+++ couriergraph-0.25/debian/compat
@@ -1 +1 @@
-4
+9

Processed: couriergraph: diff for NMU version 0.25-4.4

[Debian Bug Tracking System]

Processing control commands:

> tags 817409 + patch
Bug #817409 [src:couriergraph] couriergraph: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817409 + pending
Bug #817409 [src:couriergraph] couriergraph: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#826300: fpc: fp-compiler not installable on powerpc since glibc 2.23

[Gianfranco Costamagna]

On Thu, 7 Jul 2016 14:13:42 + (UTC) Gianfranco Costamagna 
 wrote:
> control: severity -1 serious
> 
> Hi, this is now RC with 2.23 on unstable.
> 
> and according to #695547 a new upload might be already on its way
> for unstable.
> 

ping?

according to gdb, I get this

Program received signal SIGSEGV, Segmentation fault.
0x0fe28230 in _IO_wsetb () from /lib/powerpc-linux-gnu/libc.so.6

I hope this helps!

G.



signature.asc
Description: OpenPGP digital signature

Bug#832341: python-pyscss: fails to install: error: alternative path /usr/bin/python-less2scss doesn't exist

[Andreas Beckmann]

Package: python-pyscss
Version: 1.3.5-1
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...):

  Selecting previously unselected package python-pyscss.
  (Reading database ... 
(Reading database ... 7308 files and directories currently installed.)
  Preparing to unpack .../python-pyscss_1.3.5-1_amd64.deb ...
  Unpacking python-pyscss (1.3.5-1) ...
  Setting up python-pyscss (1.3.5-1) ...
  update-alternatives: using /usr/bin/python2-pyscss to provide /usr/bin/pyscss 
(pyscss) in auto mode
  update-alternatives: error: alternative path /usr/bin/python-less2scss 
doesn't exist
  dpkg: error processing package python-pyscss (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   python-pyscss


cheers,

Andreas


python-pyscss_1.3.5-1.log.gz
Description: application/gzip

Bug#832340: poco: FTBFS: undefined reference to `_pcre_ucd_...

[Andreas Beckmann]

Source: poco
Version: 1.4.6p1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

poco/experimental FTBFS:

/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucd_stage1'
/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucd_records'
/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucp_gentype'
/build/poco-1.4.6p1/lib/Linux/x86_64/libPocoFoundation.so: undefined reference 
to `_pcre_ucd_stage2'
collect2: error: ld returned 1 exit status
/build/poco-1.4.6p1/build/rules/exec:58: recipe for target 
'/build/poco-1.4.6p1/PageCompiler/bin/Linux/x86_64/cpspc' failed
make[3]: *** [/build/poco-1.4.6p1/PageCompiler/bin/Linux/x86_64/cpspc] Error 1
make[3]: Leaving directory '/build/poco-1.4.6p1/PageCompiler'
Makefile:152: recipe for target 'PageCompiler-libexec' failed
make[2]: *** [PageCompiler-libexec] Error 2


Andreas

Processed: Bug#802081 marked as pending

[Debian Bug Tracking System]

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

> tag 802081 pending
Bug #802081 [src:kmetronome] kmetronome: FTBFS: add_custom_target cannot create 
target "uninstall"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#803566: marked as pending

[James Cowgill]

tag 803566 pending
thanks

Hello,

Bug #803566 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=pkg-multimedia/kmidimon.git;a=commitdiff;h=d172a9f

---
commit d172a9fff235917bfef557120a3acbc53b7d39c3
Author: James Cowgill 
Date:   Sun Jul 24 13:27:05 2016 +0100

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index e7ca283..4c85c7d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,16 @@
-kmidimon (0.7.5-2) UNRELEASED; urgency=medium
+kmidimon (0.7.5-2) unstable; urgency=medium
 
   * Team upload.
-  *
 
- -- James Cowgill   Sat, 23 Jul 2016 21:14:34 +0100
+  [ Radovan Birdic ]
+  * Remove uninstall target from CMakeLists.txt, fixing FTBFS. (Closes: 
#803566)
+
+  [ James Cowgill ]
+  * Use canonical Vcs URLs.
+  * Remove menu file per tech-ctte decision.
+  * Bump standards to 3.9.8.
+
+ -- James Cowgill   Sun, 24 Jul 2016 13:26:55 +0100
 
 kmidimon (0.7.5-1) unstable; urgency=low
 

Processed: Bug#803566 marked as pending

[Debian Bug Tracking System]

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

> tag 803566 pending
Bug #803566 [src:kmidimon] kmidimon: FTBFS: add_custom_target cannot create 
target "uninstall"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802081: marked as pending

[James Cowgill]

tag 802081 pending
thanks

Hello,

Bug #802081 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=pkg-multimedia/kmetronome.git;a=commitdiff;h=0189253

---
commit 018925333c218ba346161b20df6ef290d6e4d1e6
Author: James Cowgill 
Date:   Sun Jul 24 13:23:05 2016 +0100

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index 1b51e4d..c0cb7b0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,14 @@
-kmetronome (0.10.1-2) UNRELEASED; urgency=medium
+kmetronome (0.10.1-2) unstable; urgency=medium
 
   * Team upload.
-  *
-
- -- James Cowgill   Sat, 23 Jul 2016 23:41:00 +0100
+  * Remove uninstall target from CMakeLists.txt, fixing FTBFS. (Closes: 
#802081)
+  * Use debhelper compat 9 to ensure build flags are passed correctly.
+  * Fix helper-templates-in-copyright lintian error.
+  * Use canonical Vcs URLs.
+  * Remove menu file per tech-ctte decision.
+  * Bump standards to 3.9.8.
+
+ -- James Cowgill   Sun, 24 Jul 2016 13:26:08 +0100
 
 kmetronome (0.10.1-1) unstable; urgency=low
 

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Sebastian Ramacher]

Hi

On 2016-07-22 13:27:09, Faidon Liambotis wrote:
> On Fri, Jul 22, 2016 at 10:21:05AM +0200, Sebastian Ramacher wrote:
> > Unfortunately I am unable to reproduce the issue. Since there are some 
> > accounts
> > of random crashes when building ffmpeg with tree vectorization enabled, I've
> > uploaded 7:3.1.1-3 with vectorization disabled. Could you please check if 
> > the
> > issue disappears with -3?
> 
> I upgraded all ffmpeg packages to 7:3.1.1-3 but I'm still experiencing
> crashes.
> 
> I then installed libavcodec57-dbgsym, libgstreamer1.0-0-dbg,
> gstreamer1.0-libav-dbg and gstreamer1.0-plugins-good-dbg. The full
> backtrace is below. The "codec = " seems
> relevant, since this is on an Intel Broadwell, which may not be the case
> for you. This looks a lot like #831529, doesn't it?
> 
> I still don't exactly understand how H.264/VA-API are related when playing
> just a .wav file, though... This was with the same gstreamer pipeline,
>   gst-launch-1.0 filesrc location=/usr/share/sounds/purple/alert.wav  !
>   wavparse ! audioconvert ! fakesink
> 
> 
> #0  0x76fc01c8 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:54
> #1  0x76fc164a in __GI_abort () at abort.c:89
> #2  0x7fffeda6260b in init_context_defaults (s=s@entry=0x70095720, 
> codec=codec@entry=0x7fffee3a8900 )
> at src/libavcodec/options.c:142
> #3  0x7fffeda626d6 in avcodec_alloc_context3 (codec=0x7fffee3a8900 
> ) at src/libavcodec/options.c:163
> #4  0x7fffef360540 in gst_ffmpeg_cfg_install_property 
> (klass=0x70095200, base=8) at gstavcfg.c:732
> #5  0x7fffef356e53 in gst_ffmpegvidenc_class_init (klass=0x70095200)
> at gstavvidenc.c:225
> #6  0x7788c22d in g_type_class_ref (pclass=0x70094690, 
> node=0x70094500) at 
> /build/glib2.0-vjfO_h/glib2.0-2.48.1/./gobject/gtype.c:2241
> #7  0x7788c22d in g_type_class_ref (type=type@entry=140737220527360)
> at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./gobject/gtype.c:2956
> #8  0x77b09da4 in gst_element_register (plugin=plugin@entry=0x69bbf0 
> [GstPlugin], name=name@entry=0x7006d110 "avenc_h264_vaapi", 
> rank=rank@entry=128, type=type@entry=140737220527360) at 
> gstelementfactory.c:243
> #9  0x7fffef3575b3 in gst_ffmpegvidenc_register 
> (plugin=plugin@entry=0x69bbf0 [GstPlugin]) at gstavvidenc.c:1009
> #10 0x7fffef349e20 in plugin_init (plugin=0x69bbf0 [GstPlugin])
> at gstav.c:158
> #11 0x77b2b537 in gst_plugin_register_func (plugin=0x69bbf0 
> [GstPlugin], desc=0x7fffef578180 , user_data=0x0) at 
> gstplugin.c:523
> #12 0x77b2d425 in _priv_gst_plugin_load_file_for_registry 
> (filename=0x6c2e20 "/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so", 
> registry=0x61c150 [GstRegistry], registry@entry=0x0, 
> error=error@entry=0x74de7bf0)
> at gstplugin.c:826
> #13 0x77b2dcea in gst_plugin_load_file (filename=, 
> error=error@entry=0x74de7bf0) at gstplugin.c:680
> #14 0x77b2e12c in gst_plugin_load_by_name (name=0x6c218d "libav")
> at gstplugin.c:1265
> #15 0x77b2ea8d in gst_plugin_feature_load 
> (feature=feature@entry=0x6e58a0 [GstTypeFindFactory]) at 
> gstpluginfeature.c:111
> #16 0x77b547e3 in gst_type_find_factory_call_function 
> (factory=0x6e58a0 [GstTypeFindFactory], find=0x74de7c90) at 
> gsttypefindfactory.c:210
> #17 0x75d89421 in gst_type_find_helper_for_data 
> (obj=obj@entry=0x812070 [GstWavParse], data=, size= out>, prob=prob@entry=0x74de7db4) at gsttypefindhelper.c:535
> #18 0x75d895a4 in gst_type_find_helper_for_buffer 
> (obj=obj@entry=0x812070 [GstWavParse], buf=buf@entry=0x70003450, 
> prob=prob@entry=0x74de7db4)
> at gsttypefindhelper.c:591
> #19 0x75b3546a in gst_wavparse_add_src_pad (wav=wav@entry=0x812070 
> [GstWavParse], buf=0x70003450) at gstwavparse.c:1908
> #20 0x75b35b47 in gst_wavparse_stream_data (wav=wav@entry=0x812070 
> [GstWavParse]) at gstwavparse.c:2061
> #21 0x75b3bbb1 in gst_wavparse_loop (pad=0x8042a0 [GstPad])
> at gstwavparse.c:2202
> #22 0x77b4fe71 in gst_task_func (task=0x81c050 [GstTask])
> at gsttask.c:332
> #23 0x775bc55e in g_thread_pool_thread_proxy (data=) 
> at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthreadpool.c:307
> #24 0x775bbbc5 in g_thread_proxy (data=0x81a800) at 
> /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gthread.c:780
> #25 0x77335464 in start_thread (arg=0x74de8700) at 
> pthread_create.c:333
> #26 0x7707430d in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thank you for the info. Could you please let us know the version of libva1 and
i965-va-driver that you have installed? Do you have any other packags providing
va-driver installed?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#832306: closed by Chris Lamb <la...@debian.org> (Bug#832306: fixed in strip-nondeterminism 0.021-1)

[James Cowgill]

On Sun, 2016-07-24 at 12:06 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the dh-strip-nondeterminism package:
> 
> #832306: dh-strip-nondeterminism: png file handling is messed up
> 
> It has been closed by Chris Lamb .

From Git:
> diff --git a/lib/File/StripNondeterminism/handlers/png.pm 
> b/lib/File/StripNondeterminism/handlers/png.pm
> index 793250e..87235cd 100644
> --- a/lib/File/StripNondeterminism/handlers/png.pm
> +++ b/lib/File/StripNondeterminism/handlers/png.pm
> @@ -107,6 +107,11 @@ sub _normalize {
> $modified = 1;
> next;
> }
> +
> +   # Not a chunk we care about but we already read the
> +   # data so we cannot fall through
> +   print $tempfile $header . $data;
> +   next;
> }
>  
> print $tempfile $header;

This seems to break the IEND "garbage after png file" handling. The
testcase from #802057 fails after this.

James

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

Bug#832338: openstack-dashboard: fails to install: No template loaders defined.

[Andreas Beckmann]

Package: openstack-dashboard
Version: 3:10.0.0~b2-1
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...):

[...]
  1917 static files copied to '/usr/share/openstack-dashboard/static'.
  Traceback (most recent call last):
File "/usr/share/openstack-dashboard/manage.py", line 25, in 
  execute_from_command_line(sys.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 367, in execute_from_command_line
  utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 359, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 305, in run_from_argv
  self.execute(*args, **cmd_options)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 356, in execute
  output = self.handle(*args, **options)
File 
"/usr/lib/python2.7/dist-packages/compressor/management/commands/compress.py", 
line 286, in handle
  self.compress(sys.stdout, **options)
File 
"/usr/lib/python2.7/dist-packages/compressor/management/commands/compress.py", 
line 110, in compress
  raise OfflineGenerationError("No template loaders defined. You "
  compressor.exceptions.OfflineGenerationError: No template loaders defined. 
You must set TEMPLATE_LOADERS in your settings or set 'loaders' in your 
TEMPLATES dictionary.
  dpkg: error processing package openstack-dashboard (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   openstack-dashboard


cheers,

Andreas


openstack-dashboard_3:10.0.0~b2-1.log.gz
Description: application/gzip

Bug#811676: marked as done (FTBFS with GCC 6: could not convert a from x to y)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 12:03:45 +
with message-id 
and subject line Bug#811676: fixed in fbreader 0.12.10dfsg2-2
has caused the Debian Bug report #811676,
regarding FTBFS with GCC 6: could not convert a from x to y
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.)


-- 
811676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fbreader
Version: 0.12.10dfsg-10
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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 -MMD -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -pipe -fno-exceptions -Wall 
> -Wno-ctor-dtor-privacy -W -DLIBICONV_PLUG -DINSTALLDIR=\"/usr\" 
> -DBASEDIR=\"/usr/share\" -DLIBDIR=\"/usr/lib\" 
> -DIMAGEDIR=\"/usr/share/pixmaps\" 
> -DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
> -pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W -DLIBICONV_PLUG 
> -DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" -DLIBDIR=\"/usr/lib\" 
> -DIMAGEDIR=\"/usr/share/pixmaps\" 
> -DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I 
> /<>/fbreader/../zlibrary/core/include -I 
> /<>/fbreader/../zlibrary/text/include  BooksDB_BookTag.cpp
> BooksDB.cpp: In member function 'shared_ptr BooksDB::loadBook(const 
> string&)':
> BooksDB.cpp:148:10: error: could not convert 'false' from 'bool' to 
> 'shared_ptr'
>return false;
>   ^
> 
> /<>/fbreader/../makefiles/subdir.mk:14: recipe for target 
> 'BooksDB.o' failed
> make[2]: *** [BooksDB.o] Error 1
> make[2]: *** Waiting for unfinished jobs

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: fbreader
Source-Version: 0.12.10dfsg2-2

We believe that the bug you reported is fixed in the latest version of
fbreader, 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.
Eugene V. Lyubimkin  (supplier of updated fbreader 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, 24 Jul 2016 13:40:32 +0200
Source: fbreader
Binary: fbreader libzlcore0.13 libzlcore-data libzltext0.13 libzltext-data 
libzlui-gtk libzlui-qt4 libzlcore-dev libzltext-dev
Architecture: source amd64 all
Version: 0.12.10dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Eugene V. Lyubimkin 
Changed-By: Eugene V. Lyubimkin 
Description:
 fbreader   - e-book reader
 libzlcore-data - ZLibrary cross-platform development library (support files)
 libzlcore-dev - ZLibrary cross-platform development library (development files)
 libzlcore0.13 - ZLibrary cross-platform development library (shared library)
 libzltext-data - ZLibrary text model/viewer part (support files)
 libzltext-dev - ZLibrary text model/viewer part (development files)
 libzltext0.13 - ZLibrary text model/viewer part (shared library)
 libzlui-gtk - GTK+ interface module for ZLibrary
 libzlui-qt4 - Qt4 interface module for ZLibrary
Closes: 811676 824393
Changes:
 fbreader (0.12.10dfsg2-2) unstable; urgency=medium
 .
   * debian/patches:
 - New patch booksdb-avoid-converting-boolean-to-shared_ptr.patch. Fixes
   building with GCC6. Patch by Robert Bihlmeyer. (Closes: #811676)
   * debian/copyright:
 - Updated my e-mail address.
 - Removed obsolete statements for DocBook/XHTML entity files removed in
   the previous upload. (Closes: #824393)
Checksums-Sha1:
 

Bug#832306: marked as done (dh-strip-nondeterminism: png file handling is messed up)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 12:03:59 +
with message-id 
and subject line Bug#832306: fixed in strip-nondeterminism 0.021-1
has caused the Debian Bug report #832306,
regarding dh-strip-nondeterminism: png file handling is messed up
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.)


-- 
832306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-strip-nondeterminism
Version: 0.020-1
Severity: grave

Hi,

The new version of dh-strip-nondeterminism messes up handling of png
files. This is a regression from 0.019-1

When run on kmidimon which I was working on, 0.020-1 gives (and doesn't
fail on):

dh_strip_nondeterminism -pkmidimon 
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/qjackctl.png: invalid length 
in ��I� header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/kmidimon1.png: invalid 
length in >�7H header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/kmidimon3.png: invalid 
length in R��k header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/en/kmidimon/kmidimon2.png: invalid 
length in 

��3 header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/qjackctl.png: invalid length 
in ��I� header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/kmidimon1.png: invalid 
length in >�7H header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/kmidimon3.png: invalid 
length in R��k header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/doc/kde/HTML/ja/kmidimon/kmidimon2.png: invalid 
length in 

��3 header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm 
line 119.
debian/kmidimon/usr/share/icons/hicolor/64x64/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/48x48/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/24x24/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/128x128/apps/kmidimon.png: invalid 
length in HYs header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 119.
debian/kmidimon/usr/share/icons/hicolor/32x32/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.
debian/kmidimon/usr/share/icons/hicolor/16x16/apps/kmidimon.png: invalid length 
in HYs header at /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 
96.

It then proceeds to write out a load of dodgy looking files into the
package. Output from debc (note the random filenames which were not
there before):

drwxr-xr-x root/root 0 2016-07-24 00:17 ./usr/share/icons/hicolor/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/128x128/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/128x128/apps/
-rw-r--r-- root/root  4330 2016-07-23 21:03 
./usr/share/icons/hicolor/128x128/apps/kmidimon.png
-rw-r--r-- root/root  1893 2016-07-24 00:17 
./usr/share/icons/hicolor/128x128/apps/rCuFnLpl3Z
drwxr-xr-x root/root 0 2016-07-24 00:17 ./usr/share/icons/hicolor/16x16/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/16x16/apps/
-rw-r--r-- root/root33 2016-07-24 00:17 
./usr/share/icons/hicolor/16x16/apps/9wtJKNTsBO
-rw-r--r-- root/root   478 2016-07-23 21:03 
./usr/share/icons/hicolor/16x16/apps/kmidimon.png
drwxr-xr-x root/root 0 2016-07-24 00:17 ./usr/share/icons/hicolor/24x24/
drwxr-xr-x root/root 0 2016-07-24 00:17 
./usr/share/icons/hicolor/24x24/apps/
-rw-r--r-- root/root33 2016-07-24 00:17 
./usr/share/icons/hicolor/24x24/apps/a1X6RR9dWI
-rw-r--r-- root/root   694 2016-07-23 21:03 

Bug#832335: libthrift-java: libservlet2.5-java (tomcat 6) is gone

[Andreas Beckmann]

Package: libthrift-java
Version: 0.9.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

libservlet2.5-java is gone from unstable, finally.
Please update your dependencies to something modern.


Andreas

Bug#832334: freeipa: FTBFS in experimental: error: implicit declaration of function 'talloc_stackframe'

[Andreas Beckmann]

Source: freeipa
Version: 4.1.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

trying to rebuild freeipa/experimental failed:

Making all in ipa-sam
make[5]: Entering directory '/build/freeipa-4.1.4/daemons/ipa-sam'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I. -I. -I/usr/include/samba-4.0 -DPREFIX=\""/usr"\" -DBINDIR=\""/usr/bin"\" 
-DLIBDIR=\""/usr/lib/x86_64-linux-gnu"\" 
-DLIBEXECDIR=\""/usr/lib/x86_64-linux-gnu"\" -DDATADIR=\""/usr/share"\" 
-DLDAPIDIR=\""/var/run"\" -DHAVE_LDAP -I ../../util -DWITH_OPENLDAP 
-I/usr/include/nspr -I/usr/include/nss -I/usr/include/nspr -DUSE_OPENLDAP
-DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 
-DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
-I/usr/include/samba-4.0   -I/usr/include/nspr -I/usr/include/nss 
-I/usr/include/nspr  -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith 
-Wcast-align -Werror-implicit-function-declaration  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o ipa_sam.lo 
ipa_sam.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I. 
-I/usr/include/samba-4.0 -DPREFIX=\"/usr\" -DBINDIR=\"/usr/bin\" 
-DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" 
-DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DDATADIR=\"/usr/share\" 
-DLDAPIDIR=\"/var/run\" -DHAVE_LDAP -I ../../util -DWITH_OPENLDAP 
-I/usr/include/nspr -I/usr/include/nss -I/usr/include/nspr -DUSE_OPENLDAP 
-DHAVE_IMMEDIATE_STRUCTURES=1 -I/usr/include/samba-4.0 
-DHAVE_IMMEDIATE_STRUCTURES=1 -D_GNU_SOURCE=1 -DHAVE_IMMEDIATE_STRUCTURES=1 
-I/usr/include/samba-4.0 -I/usr/include/nspr -I/usr/include/nss 
-I/usr/include/nspr -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith 
-Wcast-align -Werror-implicit-function-declaration -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c ipa_sam.c  -fPIC 
-DPIC -o .libs/ipa_sam.o
ipa_sam.c:108:0: warning: "LDAP_PAGE_SIZE" redefined
 #define LDAP_PAGE_SIZE 1024
 ^
In file included from /usr/include/samba-4.0/smbldap.h:24:0,
 from ipa_sam.c:25:
/usr/include/samba-4.0/smb_ldap.h:81:0: note: this is the location of the 
previous definition
 #define LDAP_PAGE_SIZE 1000
 ^
ipa_sam.c: In function 'ldapsam_uid_to_sid':
ipa_sam.c:827:24: error: implicit declaration of function 'talloc_stackframe' 
[-Werror=implicit-function-declaration]
  TALLOC_CTX *tmp_ctx = talloc_stackframe();
^
ipa_sam.c:827:24: warning: initialization makes pointer from integer without a 
cast [-Wint-conversion]
ipa_sam.c: In function 'ldapsam_gid_to_sid':
ipa_sam.c:914:24: warning: initialization makes pointer from integer without a 
cast [-Wint-conversion]
  TALLOC_CTX *tmp_ctx = talloc_stackframe();
^
ipa_sam.c: In function 'pdb_init_ipasam':
ipa_sam.c:4426:2: error: implicit declaration of function 'trim_string' 
[-Werror=implicit-function-declaration]
  trim_string( uri, "\"", "\"" );
  ^
ipa_sam.c:4513:26: error: implicit declaration of function 'smb_xstrdup' 
[-Werror=implicit-function-declaration]
  ldap_state->domain_dn = smb_xstrdup(dn);
  ^
ipa_sam.c:4513:24: warning: assignment makes pointer from integer without a 
cast [-Wint-conversion]
  ldap_state->domain_dn = smb_xstrdup(dn);
^
cc1: some warnings being treated as errors
Makefile:550: recipe for target 'ipa_sam.lo' failed
make[5]: *** [ipa_sam.lo] Error 1


Andreas

Bug#832332: linux-image-4.6.0-1-amd64: Flickering X display for Intel HD 4600 (i915 driver)

[Bram Bolder]

Package: src:linux
Version: 4.6.4-1
Severity: serious

Dear Maintainer,

after upgrading the meta package 'linux-image-amd64' from 
linux-image-4.5.0-2-amd64
to linux-image-4.6.0-1-amd64 (and rebooting), my laptop screen started to 
flicker
annoyingly. At first I thought it was a hardware defect (backlight lamp reaching
its end of life), but booting an Ubuntu or reverting to the 4.5.0-2 does not 
show
any flickering. The normal terminals (alt-F1 through alt-F6) do not flicker.

My laptop has seen many generations of Linux images while using 'Debian 
testing',
all without problems, so it must be related to this latest kernel version.
I tried a clean installation of SID (i.e. without explicitly configuring xorg),
but it reproduces the flickering.

The flicker itself looks like an erratic pattern of brightness fluctuations 
(between
roughly 1 and 10Hz). Sometimes I notice an afterimage of the 'xdm' login screen.
Maybe of importance for narrowing down the bug: I don't use/never used any 
external
displays, only the normal display of this laptop (in native resolution 
1920x1080).

I filed this bug as 'serious', as working with a flickering display is not an 
option
for me.

I have googled a bit to find if anyone has a similar problem. The only thing I 
found
were some problematic DisplayPort initialization issues. I don't know, if this 
is
related, as this was already in kernel 4.3 AFAIR.

I also attached my Xorg.log, as this might contain useful information in 
tracing down
the bug.


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=d2d51710-e491-4deb-bc43-012275af6d98 ro quiet acpi_osi=

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[6.659488] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[6.659996] acpi device:56: registered as cooling_device4
[6.660062] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
[6.660085] [drm] Initialized i915 1.6.0 20160229 for :00:02.0 on minor 0
[6.661422] thinkpad_acpi: ThinkPad ACPI Extras v0.25
[6.661424] thinkpad_acpi: http://ibm-acpi.sf.net/
[6.661425] thinkpad_acpi: ThinkPad BIOS J4ET82WW(1.82), EC unknown
[6.661427] thinkpad_acpi: Lenovo ThinkPad L540, model 20AV002YGE
[6.662130] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
[6.662133] thinkpad_acpi: Disabling thinkpad-acpi brightness events by 
default...
[6.663733] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[6.663784] thinkpad_acpi: Console audio control enabled, mode: monitor 
(read only)
[6.665701] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input9
[6.715675] input: PC Speaker as /devices/platform/pcspkr/input/input10
[6.789295] EFI Variables Facility v0.08 2004-May-17
[6.800370] sr 0:0:0:0: Attached scsi generic sg0 type 5
[6.800489] sd 4:0:0:0: Attached scsi generic sg1 type 0
[6.829965] pstore: Registered efi as persistent store backend
[6.925800] fbcon: inteldrmfb (fb0) is primary device
[7.005259] iTCO_vendor_support: vendor-support=0
[7.039334] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3232: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[7.039335] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[7.039336] snd_hda_codec_realtek hdaudioC0D0:hp_outs=2 
(0x16/0x15/0x0/0x0/0x0)
[7.039337] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[7.039337] snd_hda_codec_realtek hdaudioC0D0:inputs:
[7.039338] snd_hda_codec_realtek hdaudioC0D0:  Dock Mic=0x19
[7.039339] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a
[7.039339] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[7.047440] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[7.047586] input: HDA Intel PCH Dock Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[7.047643] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[7.047703] input: HDA Intel PCH Dock Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[7.047761] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input15
[7.097081] Intel(R) Wireless WiFi driver for Linux
[7.097082] Copyright(c) 2003- 2015 Intel Corporation
[7.114746] iwlwifi :02:00.0: firmware: failed to load 
iwlwifi-7260-17.ucode (-2)
[7.114748] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
[7.128682] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-7260-16.ucode
[7.128894] iwlwifi :02:00.0: 

Processed: Re: dh-strip-nondeterminism: png file handling is messed up

[Debian Bug Tracking System]

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

> tags 832306 + pending
Bug #832306 [dh-strip-nondeterminism] dh-strip-nondeterminism: png file 
handling is messed up
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#832306: dh-strip-nondeterminism: png file handling is messed up

[Chris Lamb]

tags 832306 + pending
thanks

Thanks for the patch - alas I independently wrote a (simpler) one.

Uploading in a few minutes.


Regards,

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

Bug#831199: vlc: FTBFS with GCC 6: atomic:988:25: error: macro "atomic_compare_exchange_weak_explicit" passed 5 arguments, but takes just 4

[Sebastian Ramacher]

On 2016-07-14 09:29:45, Lucas Nussbaum wrote:
> Source: vlc
> Version: 2.2.4-2
> 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.

I've pushed a fix to git. But as new patches are currently discussed for
vlc_atomic [1], I'd like to wait for the outcome of the discussion.

Cheers

[1] https://mailman.videolan.org/pipermail/vlc-devel/2016-July/108715.html
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#832330: gnokii: FTBFS in experimental: undefined references to GUI_HideAbout, CloseLogosWindow

[Andreas Beckmann]

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

the build (for amd64) log ends with

libtool: link: gcc -I../include -pthread -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-DGTK_ENABLE_BROKEN -DLOCALEDIR=\"/usr/share/locale\" -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wno-pointer-sign -fvisibility=hidden -fno-strict-aliasing -Wl,-z -Wl,relro -o 
.libs/xgnokii xgnokii-xgnokii.o xgnokii-xgnokii_common.o 
xgnokii-xgnokii_contacts.o xgnokii-xgnokii_sms.o xgnokii-xgnokii_netmon.o 
xgnokii-xgnokii_dtmf.o xgnokii-xgnokii_cfg.o xgnokii-xgnokii_speed.o 
xgnokii-xgnokii_xkeyb.o xgnokii-xgnokii_calendar.o xgnokii-xgnokii_logos.o 
xgnokii-xgnok
 ii_xring.o xgnokii-xgnokii_lowlevel.o xgnokii-xgnokii_data.o -pthread  
-lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 
-lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig 
/usr/lib/x86_64-linux-gnu/libfreetype.so ../common/.libs/libgnokii.so 
../common/data/.libs/libDATA.a -pthread
xgnokii-xgnokii.o: In function `CreateAboutDialog':
/build/gnokii-0.6.31+dfsg/xgnokii/xgnokii.c:1188: undefined reference to 
`GUI_HideAbout'
xgnokii-xgnokii_logos.o:(.data+0x1c0): undefined reference to `CloseLogosWindow'
collect2: error: ld returned 1 exit status
Makefile:489: recipe for target 'xgnokii' failed
make[3]: *** [xgnokii] Error 1

A full build log resulting the the same problem is available from the buildd 
mips64el build:

https://buildd.debian.org/status/fetch.php?pkg=gnokii=mips64el=0.6.31%2Bdfsg-2=1459246517


Andreas

Bug#831199: marked as pending

[Sebastian Ramacher]

tag 831199 pending
thanks

Hello,

Bug #831199 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=pkg-multimedia/vlc.git;a=commitdiff;h=e4cb137

---
commit e4cb137f5f5c9cb6e33c3dc140d9cf107ff7678c
Author: Sebastian Ramacher 
Date:   Sun Jul 24 13:25:52 2016 +0200

Update changelog

diff --git a/debian/changelog b/debian/changelog
index 71678d5..f68aa23 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,15 @@
 vlc (2.2.4-3) UNRELEASED; urgency=medium
 
+  [ Mateusz Łukasik ]
   * debian/control:
 - Remove Clément Stenac from Uploaders. Thanks for your job!
 
- -- Mateusz Łukasik   Sun, 05 Jun 2016 19:50:30 +0200
+  [ Sebastian Ramacher ]
+  * Fix FTBFS with GCC 6 (Closes: #831199)
+- debian/patches/vlc_atomic*: Upstream patches to fix the use of atomic_*.
+- debian/rules: Build with -std=gnu11 and -std=gnu++98.
+
+ -- Sebastian Ramacher   Thu, 14 Jul 2016 10:41:37 +0200
 
 vlc (2.2.4-2) unstable; urgency=medium