Bug#802191: bats: FTBFS: not ok 7 summary passing tests

[Yaroslav Halchenko]

On Sun, 25 Sep 2016, Santiago Vila wrote:

> On Sun, Sep 25, 2016 at 01:14:16AM +0200, Tobias Frost wrote:

> > I'd then NMU it tomorrow,,,

> I would skip this package, as I think the maintainer is around and not MIA.

NMUs are welcome if you see a clear workaround (force setting up some
TERM so tests pass?)


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#838804: chromium:Gtk: cannot open display:

[user]

Package: chromium
Version: 53.0.2785.113-1~deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I ran chromium and chromium --disable-namespace-sandbox from weston-terminal in 
weston
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I tried export DISPLAY=:0 and :0.0 neither worked and only changed err
   * What was the outcome of this action?
ERROR:browser_main_loop.cc(261) Gtk: cannot open display:
   * What outcome did you expect instead?
for chromium to run

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
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 chromium depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-18+deb8u6
ii  libcairo21.14.0-2.1+deb8u1
ii  libcups2 1.7.5-11+deb8u1
ii  libdbus-1-3  1.8.20-0+deb8u1
ii  libexpat12.1.0-6+deb8u3
ii  libfontconfig1   2.11.0-6.3+deb8u1
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.42.1-1+b1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-3+deb8u1
ii  libjpeg62-turbo  1:1.3.1-12
ii  libnspr4 2:4.10.7-1+deb8u1
ii  libnss3  2:3.17.2-1.1+deb8u2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-7
ii  libstdc++6   4.9.2-10
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+deb8u3
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.0~rc1+git20111210-7.4

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  
pn  chromium-l10n   

-- no debconf information

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

[Aliaksey Kandratsenka]

On my machine this is passing reliably. Given that KVM virtual machine
image was mentioned, maybe someone can share KVM image where this is
failing? I am still eager to debug this.

On Sun, Sep 18, 2016 at 4:07 AM, Santiago Vila  wrote:
>
> On Fri, 16 Sep 2016, Lucas Nussbaum wrote:
>
>> On 15/09/16 at 19:39 +0200, Santiago Vila wrote:
>
>> > Version 2.2.1-0.3 is the first one that does not *always* fail for me.
>> > This is a great achievement indeed.
>> >
>> > Now it builds sometimes, but 3/11 is not a very good ratio.
>>
>> I'm not sure, no. It's indeed possible that it's still failing randomly.
>
> Ok, based on available data, this package still FTBFS randomly, so I'm
> raising the severity to serious again.
>
> Since there is a new upstream release, maybe it does not make much
> sense to try to debug this in the current version.
>
> So I suggest the maintainer to disable the tests (trivial but untested
> patch attached) for this release and reenable them for the next
> upstream version.
>
> I don't use this package myself, and it is not my intention or desire
> to see it autoremoved for the sake of removing it.
>
> Everything I ask is that it builds ok, so if anybody reading this
> wants to see this package in stretch in its current form please consider
> contacting the maintainer and/or disabling the tests in a NMU.
>
> Upstream is willing to help here, but if the maintainer seems to be MIA,
> there is not much else we can do.
>
> Thanks.

Bug#818201: marked as done (kodi: Jasper removal)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 01:55:48 +
with message-id 
and subject line Bug#818201: fixed in kodi 17.0~beta2+dfsg1-1
has caused the Debian Bug report #818201,
regarding kodi: Jasper removal
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.)


-- 
818201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 17.0~beta2+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
kodi, 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.
Balint Reczey  (supplier of updated kodi 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, 24 Sep 2016 14:57:31 +0200
Source: kodi
Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev 
kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send 
kodi-addons-dev xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev 
xbmc-eventclients-wiiremote xbmc-eventclients-j2me xbmc-eventclients-ps3 
xbmc-eventclients-xbmc-send xbmc-addons-dev
Architecture: source amd64 all
Version: 17.0~beta2+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi   - Open Source Home Theatre (executable binaries)
 kodi-addons-dev - Open Source Home Theatre (Addons Dev package)
 kodi-bin   - Open Source Home Theatre (architecture-dependent files)
 kodi-data  - Open Source Home Theatre (arch-independent data package)
 kodi-eventclients-common - Open Source Home Theatre (Event Client Common 
package)
 kodi-eventclients-dev - Open Source Home Theatre (Event Client Dev package)
 kodi-eventclients-kodi-send - Open Source Home Theatre (Event Client Kodi-SEND 
package)
 kodi-eventclients-ps3 - Open Source Home Theatre (Event Client PS3 package)
 kodi-eventclients-wiiremote - Open Source Home Theatre (Event Client WII 
Remote support package
 xbmc   - transitional dummy package
 xbmc-addons-dev - transitional dummy package
 xbmc-bin   - transitional dummy package
 xbmc-eventclients-common - transitional dummy package
 xbmc-eventclients-dev - transitional dummy package
 xbmc-eventclients-j2me - transitional dummy package
 xbmc-eventclients-ps3 - transitional dummy package
 xbmc-eventclients-wiiremote - transitional dummy package
 xbmc-eventclients-xbmc-send - transitional dummy package
Closes: 818201
Changes:
 kodi (17.0~beta2+dfsg1-1) experimental; urgency=medium
 .
   * New upstream beta release 17.0 Beta 2
 See: https://kodi.tv/kodi-v17-krypton-beta-2/
   * Drop build-depenency on libjasper-dev (Closes: 818201)
   * Adjust packaging to new skin's font requirements.
 Add dependency on fonts-lato and texlive-fonts-extra, drop
 dependency on fonts-roboto-hinted, make symlinks to new
 fonts instead of shipping them.
   * Add transitional dummy packages from xbmc
   * Drop obsoleted dependencies and patches
   * Silence Lintian complaining for missing misc:Depends of transitional
 packages
   * Ignore failed clean of components without Lintian noticing
   * Build-depend on liblcms2-dev for Little CMS support
Checksums-Sha1:
 25ab4e6d30851aeb93054afd7ade1eedc2bac44c 5423 

Processed: Re: [Debichem-devel] Bug#838733: experimental version of avogadro FTBFS on armel and armhf

[Debian Bug Tracking System]

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

> Tags 838733 +patch
Bug #838733 [avogadro] experimental version of avogadro FTBFS on armel and armhf
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#836669: marked as pending

[Martin Wimpress]

tag 836669 pending
thanks

Hello,

Bug #836669 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-mate/caja.git;a=commitdiff;h=26ec68f

---
commit 26ec68f56233a8cc2b0427ab9bd2dad293cc8c59
Author: Martin Wimpress 
Date:   Sun Sep 25 00:29:54 2016 +0100

debian/changelog: (Closes: #836349, #837889, #838155, #834943, #838108, 
#836669).

diff --git a/debian/changelog b/debian/changelog
index 1bd2c88..f7b07ab 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 caja (1.16.0-1) UNRELEASED; urgency=medium
 
-  * New upstream release.
+  * New upstream release. (Closes: #836349, #837889, #838155, #834943,
+  #838108, #836669).
 
  -- Martin Wimpress   Fri, 23 Sep 2016 10:46:46 +0100
 

Bug#837965: marked as pending

[Martin Wimpress]

tag 837965 pending
thanks

Hello,

Bug #837965 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-mate/mate-power-manager.git;a=commitdiff;h=ed24a80

---
commit ed24a80c612140ca9e53c66dc22382edb3b206fc
Author: Martin Wimpress 
Date:   Sun Sep 25 00:33:50 2016 +0100

debian/changelog: (Closes: #827232, #837965, #838214).

diff --git a/debian/changelog b/debian/changelog
index 862ce28..05a776a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 mate-power-manager (1.16.0-1) UNRELEASED; urgency=medium
 
-  * New upstream release.
+  * New upstream release. (Closes: #827232, #837965, #838214).
 
  -- Martin Wimpress   Fri, 23 Sep 2016 10:46:47 +0100
 

Bug#837005: marked as pending

[Martin Wimpress]

tag 837005 pending
thanks

Hello,

Bug #837005 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-mate/mate-applets.git;a=commitdiff;h=4f464b8

---
commit 4f464b8ca765c400b126aae33cd9f82be2a3d95e
Author: Martin Wimpress 
Date:   Sun Sep 25 00:34:34 2016 +0100

debian/changelog: (Closes: #837005).

diff --git a/debian/changelog b/debian/changelog
index 64fc252..ea8293b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 mate-applets (1.16.0-1) UNRELEASED; urgency=medium
 
-  * New upstream release.
+  * New upstream release. (Closes: #837005)
 
  -- Martin Wimpress   Fri, 23 Sep 2016 10:46:48 +0100
 

Processed: Bug#837005 marked as pending

[Debian Bug Tracking System]

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

> tag 837005 pending
Bug #837005 [src:mate-applets] mate-applets: FTBFS: 
./cpufreq/src/cpufreq-monitor-libcpufreq.c:118: undefined reference to 
`cpupower_is_cpu_online'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#837965 marked as pending

[Debian Bug Tracking System]

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

> tag 837965 pending
Bug #837965 [mate-power-manager] mate-power-manager: segfaults in strtod
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#836669 marked as pending

[Debian Bug Tracking System]

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

> tag 836669 pending
Bug #836669 [caja] caja: Crashes due to theme errors
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831916: marked as done (winpdb: FTBFS with dpkg-buildpackage -A: winpdb.1: No such file or directory at /usr/bin/dh_installman line 131.)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 23:45:27 +
with message-id 
and subject line Bug#831916: fixed in winpdb 1.4.8-3
has caused the Debian Bug report #831916,
regarding winpdb: FTBFS with dpkg-buildpackage -A: winpdb.1: No such file or 
directory at /usr/bin/dh_installman line 131.
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.)


-- 
831916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: winpdb
Version: 1.4.8-2.1
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.

If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now. If not, debian/rules
should be modified so that the build-indep and binary-indep target generates
the architecture independent packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh --with python2 binary-indep
>dh_testroot -i
>dh_prep -i
>dh_installdirs -i
>dh_auto_install -i
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
>   python setup.py install --force --root=/<>/debian/winpdb 
> --no-compile -O0 --install-layout=deb
> running install
> running build
> running build_py
> running build_scripts
> running install_lib
> creating /<>/debian/winpdb/usr/lib
> creating /<>/debian/winpdb/usr/lib/python2.7
> creating /<>/debian/winpdb/usr/lib/python2.7/dist-packages
> copying build/lib.linux-x86_64-2.7/winpdb.py -> 
> /<>/debian/winpdb/usr/lib/python2.7/dist-packages
> copying build/lib.linux-x86_64-2.7/rpdb2.py -> 
> /<>/debian/winpdb/usr/lib/python2.7/dist-packages
> running install_scripts
> creating /<>/debian/winpdb/usr/bin
> copying build/scripts-2.7/winpdb -> /<>/debian/winpdb/usr/bin
> copying build/scripts-2.7/rpdb2 -> /<>/debian/winpdb/usr/bin
> changing mode of /<>/debian/winpdb/usr/bin/winpdb to 775
> changing mode of /<>/debian/winpdb/usr/bin/rpdb2 to 775
> running install_egg_info
> Writing 
> /<>/debian/winpdb/usr/lib/python2.7/dist-packages/winpdb-1.4.8.egg-info
>dh_install -i
>dh_installdocs -i
>dh_installchangelogs -i
>dh_installman -i
> winpdb.1: No such file or directory at /usr/bin/dh_installman line 131.
> debian/rules:10: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/winpdb_1.4.8-2.1_unstable_archallonly.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: winpdb
Source-Version: 1.4.8-3

We believe that the bug you reported is fixed in the latest version of
winpdb, 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.
Bernd Zeimetz  (supplier of updated winpdb 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, 24 Sep 2016 17:47:15 +0200
Source: winpdb

Processed (with 3 errors): These bugs are really the same

[Debian Bug Tracking System]

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

> severity 798296 serious
Bug #798296 [src:bats] bats own testsuite fails with TERM set to unknown
Severity set to 'serious' from 'important'
> forcemerge 798296 802191
Bug #798296 [src:bats] bats own testsuite fails with TERM set to unknown
Bug #798296 [src:bats] bats own testsuite fails with TERM set to unknown
Added tag(s) stretch and sid.
Bug #802191 [src:bats] bats: FTBFS: not ok 7 summary passing tests
Added tag(s) patch.
Merged 798296 802191
> It is my undesrtanding that these two bugs are really the same.
Unknown command or malformed arguments to command.
> It fails with sbuild (when run under cron, not manually from a
Unknown command or malformed arguments to command.
> terminal) because TERM is not set.
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#802191: These bugs are really the same

[Santiago Vila]

severity 798296 serious
forcemerge 798296 802191

It is my undesrtanding that these two bugs are really the same.

It fails with sbuild (when run under cron, not manually from a
terminal) because TERM is not set.

Bug#802191: bats: FTBFS: not ok 7 summary passing tests

[Santiago Vila]

On Sun, Sep 25, 2016 at 01:14:16AM +0200, Tobias Frost wrote:

> At the moment I cannot install sbuild due to the perl breakage...

Oh, that's why I like running testing (not unstable).

> But I think it is not necessary as you confirmed the issue is enough
> for me. 
> Can you try to apply the patch from #798296 to see if it builds?

Yes, it fixes the build when TERM is not set.

BTW: I've just discovered that running sbuild by hand makes TERM to be
inherited from my own bash session. I had to unset TERM to check that.

(The build logs I attached are created by sbuild as a child process
of cron, so that's why TERM is not set in such case).

> I'd then NMU it tomorrow,,,

I would skip this package, as I think the maintainer is around and not MIA.

> Greetings from the Salzburg BSP,

Good luck.

Thanks.

Bug#828896: marked as done (libopenraw: FTBFS: dh_strip: debug package libopenrawgnome1v5-dbg is not listed in the control file)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 23:27:27 +
with message-id 
and subject line Bug#828896: fixed in libopenraw 0.0.9-3.10
has caused the Debian Bug report #828896,
regarding libopenraw: FTBFS: dh_strip: debug package libopenrawgnome1v5-dbg is 
not listed in the control file
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.)


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

libopenraw fails to build from source in unstable/amd64:

  [..]

 ^
  pixbufload.c:71:4: warning: 'gdk_pixbuf_unref' is deprecated: Use 
'g_object_unref' instead [-Wdeprecated-declarations]
  gdk_pixbuf_unref(pixbuf);
  ^
  In file included from 
/usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:33:0,
   from ../gnome/include/libopenraw-gnome/gdkpixbuf.h:30,
   from pixbufload.c:27:
  /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:228:12: note: 
declared here
   void   gdk_pixbuf_unref(GdkPixbuf *pixbuf);
  ^
  /bin/bash ../libtool --tag=CC --mode=link /bin/bash ../shave cc gcc -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wextra -pedantic -g 
-Wall -L../gnome -static -Wl,-z,relro -Wl,-z,defs -o pixbufload pixbufload.o 
../gnome/libopenrawgnome.la -lstdc++ -ljpeg -lgdk_pixbuf-2.0 -lgobject-2.0 
-lglib-2.0 --shave-mode=link
  libtool: link: /bin/bash ../shave cc gcc -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wextra -pedantic -g -Wall -Wl,-z -Wl,relro 
-Wl,-z -Wl,defs -o pixbufload pixbufload.o --shave-mode=link  -L../gnome 
../gnome/.libs/libopenrawgnome.a 
/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib/.libs/libopenraw.a
 -lstdc++ -ljpeg -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra 
-pedantic -g -Wall -Wl,-z -Wl,relro -Wl,-z -Wl,defs -o pixbufload pixbufload.o 
-L../gnome ../gnome/.libs/libopenrawgnome.a 
/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib/.libs/libopenraw.a
 -lstdc++ -ljpeg -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/demo'
  Making all in tools
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/tools'
  g++ -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra -ansi 
-pedantic -g -Wall -Wshadow -c -o ordiag.o ordiag.cpp
  /bin/bash ../libtool --tag=CXX --mode=link /bin/bash ../shave cxx g++ -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wextra -ansi 
-pedantic -g -Wall -Wshadow -L../lib -static -Wl,-z,relro -Wl,-z,defs -o ordiag 
ordiag.o ../lib/libopenraw.la -lstdc++ -ljpeg --shave-mode=link
  libtool: link: /bin/bash ../shave cxx g++ -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wextra -ansi -pedantic -g -Wall -Wshadow 
-Wl,-z -Wl,relro -Wl,-z -Wl,defs -o ordiag ordiag.o --shave-mode=link  -L../lib 
../lib/.libs/libopenraw.a -lstdc++ -ljpeg
  g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra 
-ansi -pedantic -g -Wall -Wshadow -Wl,-z -Wl,relro -Wl,-z -Wl,defs -o ordiag 
ordiag.o -L../lib ../lib/.libs/libopenraw.a -lstdc++ -ljpeg
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/tools'
  Making all in include
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/include'
  Making all in libopenraw
  Making all in libopenraw++
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/include'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
 

Bug#838733: [Debichem-devel] Bug#838733: experimental version of avogadro FTBFS on armel and armhf

[peter green]

Tags 838733 +patch
thanks

On 24/09/16 23:19, Michael Banck wrote:

So it seems the fix is simply to replace Eigen::Vector3d with Eigen::Matrix<
qreal , 3 , 1>. I've just set off a test build with that change, will report
results in the morning.
 

Let us know how it goes.
   

I got it to build,  debdiff attatched, no intent to NMU.


diff -Nru avogadro-1.1.1/debian/changelog avogadro-1.1.1/debian/changelog
--- avogadro-1.1.1/debian/changelog 2016-08-04 17:06:58.0 +
+++ avogadro-1.1.1/debian/changelog 2016-09-24 02:16:01.0 +
@@ -1,3 +1,10 @@
+avogadro (1.1.1-1~exp3.2) UNRELEASED; urgency=medium
+
+  * Patch for BTS, no intent to NMU
+  * Fix qreal VS double issue.
+
+ -- Peter Michael Green   Sat, 24 Sep 2016 02:16:01 +
+
 avogadro (1.1.1-1~exp3.1) experimental; urgency=medium
 
   * Non-maintainer upload.
diff -Nru avogadro-1.1.1/debian/patches/fix-qreal-vs-double.patch 
avogadro-1.1.1/debian/patches/fix-qreal-vs-double.patch
--- avogadro-1.1.1/debian/patches/fix-qreal-vs-double.patch 1970-01-01 
00:00:00.0 +
+++ avogadro-1.1.1/debian/patches/fix-qreal-vs-double.patch 2016-09-24 
02:16:01.0 +
@@ -0,0 +1,95 @@
+Description: Fix qreal VS double issue.
+ Vector3d is an alias for Eigen::Matrix< double , 3 , 1> but electronDensity 
+ expects Eigen::Matrix< qreal , 3 , 1> therefore the code broke on arm
+ platforms where qreal is defined (in qt4) as float. This patch changes the
+ code to construct the correct type.
+Author: Peter Michael Green 
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 2016-09-24
+
+Index: avogadro-1.1.1/libavogadro/src/extensions/qtaim/qtaimcubature.cpp
+===
+--- avogadro-1.1.1.orig/libavogadro/src/extensions/qtaim/qtaimcubature.cpp
 avogadro-1.1.1/libavogadro/src/extensions/qtaim/qtaimcubature.cpp
+@@ -1189,7 +1189,7 @@ QList QTAIMEvaluateProperty(QL
+ 
+   QList valueList;
+ 
+-  double initialElectronDensity=eval.electronDensity( 
Eigen::Vector3d(x0,y0,z0) );
++  double initialElectronDensity=eval.electronDensity( Eigen::Matrix< qreal , 
3 , 1>(x0,y0,z0) );
+ 
+   // if less than some small value, then return zero for all integrands.
+   if( initialElectronDensity < 1.e-5 )
+@@ -1254,7 +1254,7 @@ QList QTAIMEvaluateProperty(QL
+   {
+ if( modeList.at(m) == 0 )
+ {
+-  valueList.append(eval.electronDensity( Eigen::Vector3d(x0,y0,z0) ));
++  valueList.append(eval.electronDensity( Eigen::Matrix< qreal , 3 , 
1>(x0,y0,z0) ));
+ }
+ else
+ {
+@@ -1472,7 +1472,7 @@ QList QTAIMEvaluatePropertyRTP
+ 
+   QList valueList;
+ 
+-  double initialElectronDensity=eval.electronDensity( 
Eigen::Vector3d(x0,y0,z0) );
++  double initialElectronDensity=eval.electronDensity( Eigen::Matrix< qreal , 
3 , 1>(x0,y0,z0) );
+ 
+   // if less than some small value, then return zero for all integrands.
+   if( initialElectronDensity < 1.e-5 )
+@@ -1540,7 +1540,7 @@ QList QTAIMEvaluatePropertyRTP
+ {
+   valueList.append(
+ 
+-  r0*r0*sin(t0)*eval.electronDensity( Eigen::Vector3d(x0,y0,z0) )
++  r0*r0*sin(t0)*eval.electronDensity( Eigen::Matrix< qreal , 3 , 
1>(x0,y0,z0) )
+ 
+   );
+ }
+@@ -1738,7 +1738,7 @@ void property_r(unsigned int ndim, const
+   {
+ if( mode==0 )
+ {
+-  fval[m]=r*r*eval.electronDensity( Eigen::Vector3d(x,y,z) );
++  fval[m]=r*r*eval.electronDensity( Eigen::Matrix< qreal , 3 , 1>(x,y,z) 
);
+ }
+   }
+ 
+@@ -1846,7 +1846,7 @@ QList QTAIMEvaluatePropertyTP(
+   qreal x=xyzl(0);
+   qreal y=xyzl(1);
+   qreal z=xyzl(2);
+-  qreal leftElectronDensity=eval.electronDensity( Eigen::Vector3d(x,y,z) );
++  qreal leftElectronDensity=eval.electronDensity( Eigen::Matrix< qreal , 3 , 
1>(x,y,z) );
+ 
+   if( leftElectronDensity < 1.e-5 )
+   {
+@@ -1896,7 +1896,7 @@ QList QTAIMEvaluatePropertyTP(
+   x=xyzr(0);
+   y=xyzr(1);
+   z=xyzr(2);
+-  qreal rightElectronDensity=eval.electronDensity( Eigen::Vector3d(x,y,z) );
++  qreal rightElectronDensity=eval.electronDensity( Eigen::Matrix< qreal , 3 , 
1>(x,y,z) );
+ 
+   if( rightElectronDensity < 1.e-5 )
+   {
+@@ -1959,7 +1959,7 @@ QList QTAIMEvaluatePropertyTP(
+ x=xyzm(0);
+ y=xyzm(1);
+ z=xyzm(2);
+-qreal midpointElectronDensity=eval.electronDensity( 
Eigen::Vector3d(x,y,z) );
++qreal midpointElectronDensity=eval.electronDensity( Eigen::Matrix< qreal 
, 3 , 1>(x,y,z) );
+ 
+ if( midpointElectronDensity < 1.e-5 )
+ {

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Scott Kitterman]

On September 24, 2016 3:02:28 PM EDT, Diederik de Haas  
wrote:
>Control: reopen -1
>
>On Sat, 24 Sep 2016 15:52:33 +0100 Chris Lamb  wrote:
>> > [plasma-discover] plasma-discover uninstalls packages during
>upgrades
>> > without asking for confirmation> 
>> This is due to the ongoing Perl migration. There was a mail sent to
>> debian-devel-announce but I believe it was unfortunately blocked.
>> 
>> I'm closing your bug as this is not an issue that can be resolved by
>> plasma-discover, alas. :(
>
>From my #debian-qt-kde logs:
>[27.08 01:43]  plasma-discover is a giant piece of junk and
>imo 
>should be removed from every meta package
>[27.08 01:43]   /rant
>[27.08 01:45]  for a change I used it's function and did
>happily 
>uninstall plasma-desktop, plasma-workspace, sddm and a number of other 
>essential programs
>[27.08 01:45]  without any warning that is. Trying to fix it
>with 
>aptitude seems to be a no go as it's not able to resolve conflicts
>[27.08 01:45]  I have _never_ seen/happen that before
>
>So this happened on 24th of August and then the perl migration wasn't 
>happening, thus reopening the bug.

In any case, the message about the Perl migration said not to file bugs about 
package uninstallability.  That's not what this bug is about.

This bug is about lack of user visibility when discover removes packages and 
the consequent risk of inappropriate removals causing system problems.

I do agree that as long as this is the case it's questionable is it's suitable 
for the default KDE install.  I'm not completely convinced it's suitable to be 
in the archive at all.

Scott K

Bug#838748: marked as done (cloud-init: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 23:23:07 +
with message-id 
and subject line Bug#838748: fixed in cloud-init 0.7.8-1
has caused the Debian Bug report #838748,
regarding cloud-init: FTBFS in testing (failing tests)
to be marked as done.

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

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


-- 
838748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cloud-init
Version: 0.7.7~bzr1215-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,systemd --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/cloudinit
copying cloudinit/patcher.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit

[... snipped ...]

 >> begin captured logging << 
cloudinit.url_helper: DEBUG: [0/1] open 
'http://metadata.google.internal./computeMetadata/v1/instance/id' with 
{'headers': {'User-Agent': 'Cloud-Init/0.7.7', 'X-Google-Metadata-Request': 
True}, 'method': 'GET', 'url': 
'http://metadata.google.internal./computeMetadata/v1/instance/id', 
'allow_redirects': True} configuration
cloudinit.sources.DataSourceGCE: DEBUG: url instance/id raised exception Header 
value True must be of type str or bytes, not 
cloudinit.sources.DataSourceGCE: DEBUG: required key instance-id returned 
nothing. not GCE
- >> end captured logging << -

==
ERROR: test_project_level_ssh_keys_are_used 
(tests.unittests.test_datasource.test_gce.TestDataSourceGCE)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/httpretty/core.py", line 1146, in wrapper
return test(*args, **kw)
  File "/<>/tests/unittests/test_datasource/test_gce.py", line 
141, in test_project_level_ssh_keys_are_used
self.ds.get_public_ssh_keys())
  File "/<>/cloudinit/sources/DataSourceGCE.py", line 142, in 
get_public_ssh_keys
return self.metadata['public-keys']
KeyError: 'public-keys'
 >> begin captured logging << 
cloudinit.url_helper: DEBUG: [0/1] open 
'http://metadata.google.internal./computeMetadata/v1/instance/id' with 
{'headers': {'User-Agent': 'Cloud-Init/0.7.7', 'X-Google-Metadata-Request': 
True}, 'method': 'GET', 'url': 
'http://metadata.google.internal./computeMetadata/v1/instance/id', 
'allow_redirects': True} configuration
cloudinit.sources.DataSourceGCE: DEBUG: url instance/id raised exception Header 
value True must be of type str or bytes, not 
cloudinit.sources.DataSourceGCE: DEBUG: required key instance-id returned 
nothing. not GCE
- >> end captured logging << -

==
FAIL: test_connection 
(tests.unittests.test_datasource.test_gce.TestDataSourceGCE)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/httpretty/core.py", line 1146, in wrapper
return test(*args, **kw)
  File "/<>/tests/unittests/test_datasource/test_gce.py", line 88, 
in test_connection
self.assertTrue(success)
AssertionError: False is not true
 >> begin captured logging << 
cloudinit.util: DEBUG: detected dns redirection: 
{'does-not-exist.example.com.': [': does-not-exist.example.com.'], 
'example.invalid.': [': example.invalid.'], 'FLdvbcRvW4hvHnSkS80knogwd0zAsU6m': 
[': FLdvbcRvW4hvHnSkS80knogwd0zAsU6m']}
cloudinit.url_helper: DEBUG: [0/1] open 
'http://metadata.google.internal./computeMetadata/v1/instance/id' with 
{'headers': {'User-Agent': 'Cloud-Init/0.7.7', 'X-Google-Metadata-Request': 
True}, 'method': 'GET', 'url': 
'http://metadata.google.internal./computeMetadata/v1/instance/id', 
'allow_redirects': True} configuration

Bug#837026: {t,}csh FTBFS

[Nicolas Braud-Santoni]

Hi,

I was working on this today at the Salzburg BSP and should finish
tomorrow.


Best,

  nicoo

Bug#838760: perl: Perl/Perl-base upgrade removes 141 packages (Sid/Unstable)

[Russ Allbery]

Cindy Sue Causey  writes:

> Hi! Thank you for all the hard work you all to so #poverty level folks
> have a chance to keep up with the tech world, too! As to why I'm
> writing, just tried to upgrade a select 30+ packages in
> Sid/Unstable. Apt-get is my chosen method to do so. Received the message
> that Received the advisement that:

> 2 upgraded, 2 newly installed, 141 to remove

> ALMOST let it happen because I was in a hurry and didn't immediately
> catch that message. Only thing I know to do in this kind of situation is
> to set Perl and Perl-base aside and wait for the next release so that's
> how I'm approaching it today.

For future reference, you get results like this mostly from apt-get
install of specific packages, since then apt-get goes to considerably more
lengths to try to do what you're telling it to do (including contemplating
removing temporarily conflicting packages).

If instead you do a whole-system upgrade with apt-get upgrade, you'll see
all these packages will just be held back until they can be safely
upgraded.  Even if you use the more aggressive apt-get dist-upgrade, right
now you get something (depending on the packages you have installed) like:

# apt dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libenchant1c2a : Depends: aspell-en but it is not going to be installed or
   myspell-dictionary or
   aspell-dictionary or
   ispell-dictionary or
   hunspell-dictionary
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

which is not horribly informative but at least doesn't do the wrong thing.

You probably have reasons to want to upgrade specific packages instead of
your system in better, but it's worth being aware that this is one case
where this can be less safe (if you don't watch apt-get closely) than
letting it use its normal upgrade semantics.  (Also, a general upgrade is
safer in that you'll always get security updates.)

-- 
Russ Allbery (r...@debian.org)   

Bug#802191: bats: FTBFS: not ok 7 summary passing tests

[Tobias Frost]

Am Sonntag, den 25.09.2016, 00:13 +0200 schrieb Santiago Vila:
> severity 802191 serious
> thanks
> 
> While reviewing unreproducible FTBFS bugs I found this one,
> which I can reproduce without any problem at all and it's
> not random at all.
> 
> I attach five different build logs from four different autobuilders,
> using sbuild.
> 
> I think downgrading a bug just because it does not happen with
> pbuilder is just wrong, because the official buildds use sbuild,
> not pbuilder (hence I'm raising to serious again).
> 
> If the TERM thing is an essential difference between pbuilder and
> sbuild, please consider filing a bug against pbuilder for that.
> 
> Tobias, could you please try with sbuild? In case you could still
> not reproduce this with sbuild, please contact me privately, maybe
> I can lend you a virtual machine as a last resort.

At the moment I cannot install sbuild due to the perl breakage...
But I think it is not necessary as you confirmed the issue is enough
for me. 
Can you try to apply the patch from #798296 to see if it builds?
I'd then NMU it tomorrow,,,


Greetings from the Salzburg BSP,

tobi

Bug#802191: bats: FTBFS: not ok 7 summary passing tests

[Santiago Vila]

I said:
> the official buildds use sbuild,

Just in case anybody want to argue that "this package does not need to
build in the official buildds because it's Arch: all".

Well, yes, it needs to be buildable in the "Arch: all" autobuilder
as well. That's precisely what release goal in Bug #830997 is about.
We should be able to upload every package in stretch in source only
form, and it should work.

Thanks.

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

[bret curtis]

We know what the problem is and are working on it.

Please see the following:
https://anonscm.debian.org/cgit/pkg-osg/openscenegraph-3.4.git/commit/?id=fa5b1385d2b82f3fec9cc6094fb3db498a36a9e3

OSG-3.4 had the same problem until this was commited, now the package
builds and OpenMW was unblocked. It too now fails and will be fixed
asap.

Cheers,
Bret

On Sat, Sep 24, 2016 at 11:25 PM, Andreas Beckmann  wrote:
> Package: openmw
> Version: 0.40.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Hi,
>
> openmw/experimental FTBFS on armhf:
>
> https://buildd.debian.org/status/fetch.php?pkg=openmw=armhf=0.40.0-1=1474694818
>
> In file included from /usr/include/osg/GL:113:0,
>  from /usr/include/osg/GLDefines:25,
>  from /usr/include/osg/GLExtensions:18,
>  from /usr/include/osg/State:18,
>  from /usr/include/osg/GraphicsContext:17,
>  from /usr/include/osgViewer/GraphicsWindow:17,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:19,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
> /usr/include/GLES2/gl2.h:69:25: error: conflicting declaration 'typedef 
> khronos_ssize_t GLsizeiptr'
>  typedef khronos_ssize_t GLsizeiptr;
>  ^~
> In file included from /usr/include/GL/gl.h:2055:0,
>  from /usr/include/qt4/QtOpenGL/qgl.h:88,
>  from /usr/include/qt4/QtOpenGL/QGLWidget:1,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:17,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
> /usr/include/GL/glext.h:468:19: note: previous declaration as 'typedef 
> ptrdiff_t GLsizeiptr'
>  typedef ptrdiff_t GLsizeiptr;
>^~
> In file included from /usr/include/osg/GL:113:0,
>  from /usr/include/osg/GLDefines:25,
>  from /usr/include/osg/GLExtensions:18,
>  from /usr/include/osg/State:18,
>  from /usr/include/osg/GraphicsContext:17,
>  from /usr/include/osgViewer/GraphicsWindow:17,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:19,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
> /usr/include/GLES2/gl2.h:70:26: error: conflicting declaration 'typedef 
> khronos_intptr_t GLintptr'
>  typedef khronos_intptr_t GLintptr;
>   ^~~~
> In file included from /usr/include/GL/gl.h:2055:0,
>  from /usr/include/qt4/QtOpenGL/qgl.h:88,
>  from /usr/include/qt4/QtOpenGL/QGLWidget:1,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:17,
>  from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
> /usr/include/GL/glext.h:469:19: note: previous declaration as 'typedef 
> ptrdiff_t GLintptr'
>  typedef ptrdiff_t GLintptr;
>^~~~
>
>
> Andreas

Processed: Re: libmsn: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> tags 836634 + pending patch
Bug #836634 [libmsn] libmsn: please drop the build dependency on 
hardening-wrapper
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Bug#836634: libmsn: please drop the build dependency on hardening-wrapper

[Chris Lamb]

tags 836634 + pending patch
thanks

I've uploaded libmsn 4.2.1+dfsg-1.1 to DELAYED/5:
  
  libmsn (4.2.1+dfsg-1.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Drop Build-Depends on hardening-wrapper. (Closes: #836634)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -Nru libmsn-4.2.1+dfsg/debian/changelog libmsn-4.2.1+dfsg/debian/changelog
--- libmsn-4.2.1+dfsg/debian/changelog  2015-08-31 09:52:20.0 +0200
+++ libmsn-4.2.1+dfsg/debian/changelog  2016-09-25 00:32:03.0 +0200
@@ -1,3 +1,10 @@
+libmsn (4.2.1+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Build-Depends on hardening-wrapper. (Closes: #836634)
+
+ -- Chris Lamb   Sun, 25 Sep 2016 00:32:03 +0200
+
 libmsn (4.2.1+dfsg-1) unstable; urgency=medium
 
   * Package new upstream version, which was actually the same as 4.2-2
diff -Nru libmsn-4.2.1+dfsg/debian/control libmsn-4.2.1+dfsg/debian/control
--- libmsn-4.2.1+dfsg/debian/control2015-08-31 09:47:37.0 +0200
+++ libmsn-4.2.1+dfsg/debian/control2016-09-25 00:32:03.0 +0200
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Pau Garcia i Quiles 
 DM-Upload-Allowed: yes
-Build-Depends: debhelper (>= 6.0.7), cmake, libssl-dev, hardening-wrapper
+Build-Depends: debhelper (>= 6.0.7), cmake, libssl-dev
 Standards-Version: 3.9.6.1
 Section: libs
 Homepage: http://libmsn.sourceforge.net
diff -Nru libmsn-4.2.1+dfsg/debian/rules libmsn-4.2.1+dfsg/debian/rules
--- libmsn-4.2.1+dfsg/debian/rules  2015-08-31 10:13:56.0 +0200
+++ libmsn-4.2.1+dfsg/debian/rules  2016-09-25 00:32:03.0 +0200
@@ -10,10 +10,10 @@
 #export DH_VERBOSE=1
 
 # enable the hardening wrapper
-DEB_BUILD_HARDENING = 1
+DPKG_EXPORT_BUILDFLAGS = 1
 # but disable PIE
-DEB_BUILD_HARDENING_PIE = 0
-export DEB_BUILD_HARDENING DEB_BUILD_HARDENING_PIE
+export DEB_BUILD_MAINT_OPTIONS=hardening=-pie 
+include /usr/share/dpkg/buildflags.mk
 
 get-orig-source:
$(CURDIR)/debian/get-orig-source.sh

Processed: Re: Bug#836999: strace: FTBFS: ../btrfs.c:68:8: error: redefinition of 'struct btrfs_ioctl_defrag_range_args'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #836999 [src:strace] strace: FTBFS: ../btrfs.c:68:8: error: redefinition of 
'struct btrfs_ioctl_defrag_range_args'
Added tag(s) fixed-upstream.

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

Bug#836999: strace: FTBFS: ../btrfs.c:68:8: error: redefinition of 'struct btrfs_ioctl_defrag_range_args'

[Sebastian Ramacher]

Control: tags -1 + fixed-upstream

On 2016-09-08 00:15:11, Lucas Nussbaum wrote:
> Source: strace
> Version: 4.12-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160906 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > gcc -DHAVE_CONFIG_H   -I./linux/x86_64 -I../linux/x86_64 -I./linux 
> > -I../linux -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wwrite-strings 
> > -Wsign-compare  -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -O2 -MT 
> > strace-btrfs.o -MD -MP -MF .deps/strace-btrfs.Tpo -c -o strace-btrfs.o 
> > `test -f 'btrfs.c' || echo '../'`btrfs.c
> > ../btrfs.c:68:8: error: redefinition of 'struct 
> > btrfs_ioctl_defrag_range_args'
> >  struct btrfs_ioctl_defrag_range_args {
> > ^
> > In file included from ../btrfs.c:36:0:
> > /usr/include/linux/btrfs.h:496:8: note: originally defined here
> >  struct btrfs_ioctl_defrag_range_args {
> > ^
> > Makefile:2619: recipe for target 'strace-btrfs.o' failed
> > make[3]: *** [strace-btrfs.o] Error 1

This bugs is caused by a bug in the configure script. A fix is available
upstream:
https://github.com/strace/strace/commit/7c0e8875a432f68f391518d11a38f91a7fe91f35

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#838733: [Debichem-devel] Bug#838733: experimental version of avogadro FTBFS on armel and armhf

[Michael Banck]

Hi Peter,

On Sat, Sep 24, 2016 at 03:19:53AM +0100, peter green wrote:
> package: avogadro
> version: 1.1.1-1~exp3.1
> severity: serious
> X-Debbugs-CC: po...@debian.org, gl...@debian.org, gin...@debian.org,
> mba...@debian.org
> 
> While discussing possible soloutions to bug 833770 Graham Inggs sugested
> >What about uploading version 1.1.1 from experimental to unstable?
> 
> Emilio Pozuelo Monfort pointed out.
> >Note that the experimental version fails to build on armel/armhf (at least).
> 
> I decided to take a look at this.

Thank you for working on it.

The current work-around towards 1.2.0 is disabling the QTAIM extension,
but that would be a shame.

> It appears that Eigen::Vector3d produces a Matrix but
> electronDensity expects a Matrix
> 
> On most architectures qreal is defined as double, so this works but on arm32
> architectures qreal
>  is defined as float so it breaks
> 
> The first thing I tried was changing stuff from qreal to double to make it
> match but that led down a massive rabbit hole.
> 
> So I then took a closer look at what Eigen::Vector3d was. Turns out it's a
> typedef for Eigen::Matrix< double , 3 , 1>
> 
> So it seems the fix is simply to replace Eigen::Vector3d with Eigen::Matrix<
> qreal , 3 , 1>. I've just set off a test build with that change, will report
> results in the morning.

Let us know how it goes.

Also, there'a pull request for 1.2.0 adapting the current Eigen3 patch
which discusses some related problems.  I guess this needs some GUI
testing once it comiles...

The PR is here: https://github.com/cryos/avogadro/pull/38


Michael

Processed: Re: bats: FTBFS: not ok 7 summary passing tests

[Debian Bug Tracking System]

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

> severity 802191 serious
Bug #802191 [src:bats] bats: FTBFS: not ok 7 summary passing tests
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#838789: Fwd: caffe-contrib: FTBFS: libcaffe.so.1.0.0-rc3: undefined reference to `H5LTget_dataset_ndims'

[Mattia Rizzolo]

On Sat, Sep 24, 2016 at 10:51:37PM +0200, Andreas Beckmann wrote:
> This is Bug#838789, but for some reason the BTS considers this as an
> unknown package, so you didn't get this forwarded ...

the reason is still a regression of experimental not having
{Sources,Packages}.gz anymore, but having .xz only.
I poked dondelelcaro several times over IRC, but only get a partial fix
in place.
[this is also the reason this bug came to me: I'm in unknown-package@]

> Oh, you did a source-only upload. That does not work in this case, since
> you have Build-Depends in non-free. You'll always have to do
> source+binary uploads (for *all* architectures you want).

yes.  All good reason to not have such packages, if you ask me...
But for that you need to poke his sponsor, Gianfranco...

> And having a
> source package without binaries for some time seems to have made the
> package "partially disappear" from the archive.

umh?
AFAIK such kind of behaviour only happens with arch:all binaries (where
binaries actually get autoremoved)

>  Forwarded Message 
> Subject: caffe-contrib: FTBFS: libcaffe.so.1.0.0-rc3: undefined
> reference to `H5LTget_dataset_ndims'
> Date: Sat, 24 Sep 2016 22:36:50 +0200
> From: Andreas Beckmann 
> To: Debian Bug Tracking System 
[...]
> In case it does matter:
> This was built against hdf5 1.8.16 from sid, not against 1.10 from
> experimental.
> IIRC some time ago apt changed how Build-Depends are resolved for
> packages in experimental, preferring packages from unstable unless
> a versioned constraint actually requires something from experimental.

that really depends on the resolver you use in your build daemon.  But
that always was the behaviour you had in experimental (unless you used
pbuilder and its broken idea of experimenal from version < 0.224)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#836627: grap: please drop the build dependency on hardening-wrapper

[Chris Lamb]

tags 836627 + pending patch
thanks

I've uploaded grap 1.44-1.1 to DELAYED/5:
  
  grap (1.44-1.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Drop Build-Depends on hardening-wrapper; they are automatically set by
  debhelper (with debian/compat level >= 9) when dh_auto_* commands are 
used.
  (Closes: #836627)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -Nru grap-1.44/debian/changelog grap-1.44/debian/changelog
--- grap-1.44/debian/changelog  2014-02-25 23:47:00.0 +0100
+++ grap-1.44/debian/changelog  2016-09-24 23:39:28.0 +0200
@@ -1,3 +1,11 @@
+grap (1.44-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Build-Depends on hardening-wrapper; automatically used by Debhelper 9
+/ dh_auto_* commands. (Closes: #836627)
+
+ -- Chris Lamb   Sat, 24 Sep 2016 23:39:28 +0200
+
 grap (1.44-1) unstable; urgency=low
 
   * New maintainer. Closes: #615895
diff -Nru grap-1.44/debian/rules grap-1.44/debian/rules
--- grap-1.44/debian/rules  2014-02-25 23:43:47.0 +0100
+++ grap-1.44/debian/rules  2016-09-24 23:39:28.0 +0200
@@ -1,8 +1,5 @@
 #!/usr/bin/make -f
 
-# Use security features with hardening-wrapper
-export DEB_BUILD_HARDENING=1
-
 %:
dh $@
 

Processed: Re: grap: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> tags 836627 + pending patch
Bug #836627 [grap] grap: please drop the build dependency on hardening-wrapper
Added tag(s) patch and pending.
> thanks
Stopping processing here.

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

Processed: gcc-avr: diff for NMU version 1:4.9.2+Atmel3.5.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 831174 + patch
Bug #831174 [src:gcc-avr] gcc-avr: FTBFS with GCC 6: cfns.gperf:101:1: error: 
'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 
'gnu_inline' attribute
Added tag(s) patch.
> tags 831174 + pending
Bug #831174 [src:gcc-avr] gcc-avr: FTBFS with GCC 6: cfns.gperf:101:1: error: 
'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 
'gnu_inline' attribute
Added tag(s) pending.

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

Bug#831174: gcc-avr: diff for NMU version 1:4.9.2+Atmel3.5.0-1.1

[Sebastian Ramacher]

Control: tags 831174 + patch
Control: tags 831174 + pending

Dear maintainer,

I've prepared an NMU for gcc-avr (versioned as 1:4.9.2+Atmel3.5.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -u gcc-avr-4.9.2+Atmel3.5.0/debian/changelog gcc-avr-4.9.2+Atmel3.5.0/debian/changelog
--- gcc-avr-4.9.2+Atmel3.5.0/debian/changelog
+++ gcc-avr-4.9.2+Atmel3.5.0/debian/changelog
@@ -1,3 +1,10 @@
+gcc-avr (1:4.9.2+Atmel3.5.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove an inlining attribute to fix build under GCC 6 (Closes: #831174)
+
+ -- Andreas Stührk   Sat, 24 Sep 2016 23:11:30 +0200
+
 gcc-avr (1:4.9.2+Atmel3.5.0-1) unstable; urgency=medium
 
   * New upstream release (closes: #790103)
diff -u gcc-avr-4.9.2+Atmel3.5.0/debian/patchlist gcc-avr-4.9.2+Atmel3.5.0/debian/patchlist
--- gcc-avr-4.9.2+Atmel3.5.0/debian/patchlist
+++ gcc-avr-4.9.2+Atmel3.5.0/debian/patchlist
@@ -1,0 +2 @@
+debian_patches/02_gcc6_fixes.diff
only in patch2:
unchanged:
--- gcc-avr-4.9.2+Atmel3.5.0.orig/debian/debian_patches/02_gcc6_fixes.diff
+++ gcc-avr-4.9.2+Atmel3.5.0/debian/debian_patches/02_gcc6_fixes.diff
@@ -0,0 +1,15 @@
+--- gcc.org/cp/cfns.h	2016-09-24 22:42:26.30400 +0200
 gcc/cp/cfns.h	2016-09-24 22:43:03.32400 +0200
+@@ -122,12 +122,6 @@
+   return hval + asso_values[(unsigned char)str[len - 1]];
+ }
+ 
+-#ifdef __GNUC__
+-__inline
+-#ifdef __GNUC_STDC_INLINE__
+-__attribute__ ((__gnu_inline__))
+-#endif
+-#endif
+ const char *
+ libc_name_p (register const char *str, register unsigned int len)
+ {


signature.asc
Description: PGP signature

Processed: Re: pwauth: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> tags 836760 + pending patch
Bug #836760 [pwauth] pwauth: please drop the build dependency on 
hardening-wrapper
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Bug#806867: python-scipy: FTBFS when built with dpkg-buildpackage -A (No module named scipy)

[Julian Taylor]

On 24.09.2016 23:14, Sebastian Humenda wrote:
> Just to let people know: I'm working on it and hope to upload a new package
> shortly.
> 

hm I wanted to do it tomorrow, but if you have it done go ahead.
note there is a new upstream version that should be uploaded to fix
other issues.

Bug#836760: pwauth: please drop the build dependency on hardening-wrapper

[Chris Lamb]

tags 836760 + pending patch
thanks

pwauth 2.3.11-0.2 uploaded to DELAYED/5. The corresponding debdiff is
attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -Nru pwauth-2.3.11/debian/changelog pwauth-2.3.11/debian/changelog
--- pwauth-2.3.11/debian/changelog  2014-05-06 12:46:28.0 +0200
+++ pwauth-2.3.11/debian/changelog  2016-09-24 22:43:40.0 +0200
@@ -1,3 +1,10 @@
+pwauth (2.3.11-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Build-Depends on hardening-wrapper. (Closes: #836760)
+
+ -- Chris Lamb   Sat, 24 Sep 2016 22:43:40 +0200
+
 pwauth (2.3.11-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru pwauth-2.3.11/debian/control pwauth-2.3.11/debian/control
--- pwauth-2.3.11/debian/control2014-05-06 11:43:16.0 +0200
+++ pwauth-2.3.11/debian/control2016-09-24 22:43:40.0 +0200
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Hai Zaar 
-Build-Depends: debhelper (>= 9~), libpam0g-dev, hardening-includes
+Build-Depends: debhelper (>= 9~), libpam0g-dev
 Standards-Version: 3.8.1
 
 Package: pwauth
diff -Nru pwauth-2.3.11/debian/rules pwauth-2.3.11/debian/rules
--- pwauth-2.3.11/debian/rules  2014-05-06 12:40:51.0 +0200
+++ pwauth-2.3.11/debian/rules  2016-09-24 22:43:40.0 +0200
@@ -1,12 +1,10 @@
 #!/usr/bin/make -f
 
-export DEB_BUILD_MAINT_OPTIONS:=hardening=+all
-
 %:
dh $@
 
 override_dh_auto_build:
-   make CFLAGS="`dpkg-buildflags --get CFLAGS`" LDFLAGS="`dpkg-buildflags 
--get LDFLAGS`" CPPFLAGS="`dpkg-buildflags --get CPPFLAGS`"
+   make $(shell dpkg-buildflags --export=cmdloine)
 
 override_dh_auto_install:
dh_auto_install

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

[Andreas Beckmann]

Package: openmw
Version: 0.40.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

openmw/experimental FTBFS on armhf:

https://buildd.debian.org/status/fetch.php?pkg=openmw=armhf=0.40.0-1=1474694818

In file included from /usr/include/osg/GL:113:0,
 from /usr/include/osg/GLDefines:25,
 from /usr/include/osg/GLExtensions:18,
 from /usr/include/osg/State:18,
 from /usr/include/osg/GraphicsContext:17,
 from /usr/include/osgViewer/GraphicsWindow:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:19,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GLES2/gl2.h:69:25: error: conflicting declaration 'typedef 
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^~
In file included from /usr/include/GL/gl.h:2055:0,
 from /usr/include/qt4/QtOpenGL/qgl.h:88,
 from /usr/include/qt4/QtOpenGL/QGLWidget:1,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GL/glext.h:468:19: note: previous declaration as 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^~
In file included from /usr/include/osg/GL:113:0,
 from /usr/include/osg/GLDefines:25,
 from /usr/include/osg/GLExtensions:18,
 from /usr/include/osg/State:18,
 from /usr/include/osg/GraphicsContext:17,
 from /usr/include/osgViewer/GraphicsWindow:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:19,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GLES2/gl2.h:70:26: error: conflicting declaration 'typedef 
khronos_intptr_t GLintptr'
 typedef khronos_intptr_t GLintptr;
  ^~~~
In file included from /usr/include/GL/gl.h:2055:0,
 from /usr/include/qt4/QtOpenGL/qgl.h:88,
 from /usr/include/qt4/QtOpenGL/QGLWidget:1,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt:17,
 from /«PKGBUILDDIR»/extern/osgQt/GraphicsWindowQt.cpp:14:
/usr/include/GL/glext.h:469:19: note: previous declaration as 'typedef 
ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^~~~


Andreas

Bug#806867: python-scipy: FTBFS when built with dpkg-buildpackage -A (No module named scipy)

[Sebastian Humenda]

Just to let people know: I'm working on it and hope to upload a new package
shortly.

Bug#811742: smpeg: diff for NMU version 0.4.5+cvs20030824-7.2

[Manuel A. Fernandez Montecelo]

Hi,

2016-09-24 20:39 GMT+02:00 Sebastian Ramacher :
> Control: tags 811742 + patch
> Control: tags 811742 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for smpeg (versioned as 0.4.5+cvs20030824-7.2) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Hmm, somehow I missed this RC bug in the last few months when tending
to Debian things -- although, due to time constraints, I've been less
active than in the last few years.

It's fine from my side, thanks!


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#836776: marked as done (SGI security bug)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:51:14 +
with message-id 
and subject line Bug#836776: fixed in imagemagick 8:6.8.9.9-5+deb8u5
has caused the Debian Bug report #836776,
regarding SGI security bug
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.)


-- 
836776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:imagemagick
version: 8:6.7.7.10-4
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org


According to upstream changelog a new bug
buffer overflow in SGI coders (bug report from
  pwchen of tencent


Author: Cristy 
Date:   Thu Aug 18 18:24:24 2016 -0400

Prevent buffer overflow in BMP & SGI coders (bug report from
pwchen of tencent)

diff --git a/ChangeLog b/ChangeLog
index 89ea234..b5b3f1e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,5 @@
 2016-08-15  6.9.5-8 Cristy  
-  * Prevent buffer overflow in BMP coder (bug report from
+  * Prevent buffer overflow in BMP & SGI coders (bug report from
  pwchen of tencent).

 2016-08-14  6.9.5-7 Cristy  
diff --git a/coders/sgi.c b/coders/sgi.c
index 756f7e6..96f18a0 100644
--- a/coders/sgi.c
+++ b/coders/sgi.c
@@ -355,13 +355,15 @@ static Image *ReadSGIImage(const ImageInfo
*image_info,ExceptionInfo *exception)
 image->rows=iris_info.rows;
 image->depth=(size_t) MagickMin(iris_info.depth,MAGICKCORE_QUANTUM_DEPTH);
 if (iris_info.pixel_format == 0)
-  image->depth=(size_t) MagickMin((size_t) 8*
-iris_info.bytes_per_pixel,MAGICKCORE_QUANTUM_DEPTH);
+  image->depth=(size_t) MagickMin((size_t) 8*iris_info.bytes_per_pixel,
+MAGICKCORE_QUANTUM_DEPTH);
 if (iris_info.depth < 3)
   {
 image->storage_class=PseudoClass;
 image->colors=iris_info.bytes_per_pixel > 1 ? 65535 : 256;
   }
+if (EOFBlob(image) != MagickFalse)
+  ThrowReaderException(CorruptImageError,"ImproperImageHeader");
 if ((image_info->ping != MagickFalse)  && (image_info->number_scenes != 0))
   if (image->scene >= (image_info->scene+image_info->number_scenes-1))
 break;
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.8.9.9-5+deb8u5

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

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

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated 
imagemagick 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, 21 Sep 2016 22:24:16 +0200
Source: imagemagick
Binary: imagemagick-common imagemagick-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers imagemagick libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-2 
libmagickcore-6.q16-2-extra libmagickcore-6.q16-dev libmagickwand-6.q16-2 
libmagickwand-6.q16-dev libmagick++-6.q16-5 libmagick++-6.q16-dev 
imagemagick-dbg libimage-magick-q16-perl perlmagick libmagickcore-dev 
libmagickwand-dev libmagick++-dev
Architecture: source all amd64
Version: 8:6.8.9.9-5+deb8u5
Distribution: jessie-security
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-common - image manipulation programs -- infrastructure
 imagemagick-dbg - debugging symbols for ImageMagick
 imagemagick-doc - document files of ImageMagick
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-5 - object-oriented C++ 

Bug#838789: Fwd: caffe-contrib: FTBFS: libcaffe.so.1.0.0-rc3: undefined reference to `H5LTget_dataset_ndims'

[Andreas Beckmann]

This is Bug#838789, but for some reason the BTS considers this as an
unknown package, so you didn't get this forwarded ...

Oh, you did a source-only upload. That does not work in this case, since
you have Build-Depends in non-free. You'll always have to do
source+binary uploads (for *all* architectures you want). And having a
source package without binaries for some time seems to have made the
package "partially disappear" from the archive.

(source-only uploads works for nvidia-cuda-toolkit since it no longer
Build-Depends on something from the non-free driver)


Andreas

 Forwarded Message 
Subject: caffe-contrib: FTBFS: libcaffe.so.1.0.0-rc3: undefined
reference to `H5LTget_dataset_ndims'
Date: Sat, 24 Sep 2016 22:36:50 +0200
From: Andreas Beckmann 
To: Debian Bug Tracking System 

Source: caffe-contrib
Version: 1.0.0~rc3-2
Severity: serious
Justification: fails to build from source

Hi,

caffe-contrib FTBFS in experimental:

[...]
[100%] Linking CXX executable ../../../test/test.testbin
cd "/build/caffe-contrib-1.0.0~rc3/caffe_cuda_build/src/caffe/test" &&
/usr/bin/cmake -E cmake_link_script CMakeFiles/test.testbin.dir/link.txt
--verbose=1
/usr/bin/g++-5   -g -O2
-fdebug-prefix-map=/build/caffe-contrib-1.0.0~rc3=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Wno-sign-comp
are -Wno-uninitialized -O3 -DNDEBUG   -fPIE -pie -Wl,-z,relro -Wl,-z,now
-Wl,--as-needed CMakeFiles/test.testbin.dir/test_accuracy_layer.cpp.o
CMakeFiles/test.testbin.dir/test_argmax_layer.cpp.o CMakeFiles/test.tes
tbin.dir/test_batch_norm_layer.cpp.o
CMakeFiles/test.testbin.dir/test_batch_reindex_layer.cpp.o
CMakeFiles/test.testbin.dir/test_benchmark.cpp.o
CMakeFiles/test.testbin.dir/test_bias_layer.cpp.o CMakeFiles/test.tes
tbin.dir/test_blob.cpp.o
CMakeFiles/test.testbin.dir/test_caffe_main.cpp.o
CMakeFiles/test.testbin.dir/test_common.cpp.o
CMakeFiles/test.testbin.dir/test_concat_layer.cpp.o
CMakeFiles/test.testbin.dir/test_contrast
ive_loss_layer.cpp.o
CMakeFiles/test.testbin.dir/test_convolution_layer.cpp.o
CMakeFiles/test.testbin.dir/test_data_layer.cpp.o
CMakeFiles/test.testbin.dir/test_data_transformer.cpp.o
CMakeFiles/test.testbin.dir/te
st_db.cpp.o CMakeFiles/test.testbin.dir/test_deconvolution_layer.cpp.o
CMakeFiles/test.testbin.dir/test_dummy_data_layer.cpp.o
CMakeFiles/test.testbin.dir/test_eltwise_layer.cpp.o
CMakeFiles/test.testbin.dir/test_e
mbed_layer.cpp.o
CMakeFiles/test.testbin.dir/test_euclidean_loss_layer.cpp.o
CMakeFiles/test.testbin.dir/test_filler.cpp.o
CMakeFiles/test.testbin.dir/test_filter_layer.cpp.o
CMakeFiles/test.testbin.dir/test_flatte
n_layer.cpp.o
CMakeFiles/test.testbin.dir/test_gradient_based_solver.cpp.o
CMakeFiles/test.testbin.dir/test_hdf5_output_layer.cpp.o
CMakeFiles/test.testbin.dir/test_hdf5data_layer.cpp.o
CMakeFiles/test.testbin.dir/
test_hinge_loss_layer.cpp.o
CMakeFiles/test.testbin.dir/test_im2col_layer.cpp.o
CMakeFiles/test.testbin.dir/test_image_data_layer.cpp.o
CMakeFiles/test.testbin.dir/test_infogain_loss_layer.cpp.o
CMakeFiles/test.tes
tbin.dir/test_inner_product_layer.cpp.o
CMakeFiles/test.testbin.dir/test_internal_thread.cpp.o
CMakeFiles/test.testbin.dir/test_io.cpp.o
CMakeFiles/test.testbin.dir/test_layer_factory.cpp.o
CMakeFiles/test.testbin.
dir/test_lrn_layer.cpp.o
CMakeFiles/test.testbin.dir/test_math_functions.cpp.o
CMakeFiles/test.testbin.dir/test_maxpool_dropout_layers.cpp.o
CMakeFiles/test.testbin.dir/test_memory_data_layer.cpp.o CMakeFiles/test.
testbin.dir/test_multinomial_logistic_loss_layer.cpp.o
CMakeFiles/test.testbin.dir/test_mvn_layer.cpp.o
CMakeFiles/test.testbin.dir/test_net.cpp.o
CMakeFiles/test.testbin.dir/test_neuron_layer.cpp.o CMakeFiles/test
.testbin.dir/test_platform.cpp.o
CMakeFiles/test.testbin.dir/test_pooling_layer.cpp.o
CMakeFiles/test.testbin.dir/test_power_layer.cpp.o
CMakeFiles/test.testbin.dir/test_protobuf.cpp.o
CMakeFiles/test.testbin.dir/t
est_random_number_generator.cpp.o
CMakeFiles/test.testbin.dir/test_reduction_layer.cpp.o
CMakeFiles/test.testbin.dir/test_reshape_layer.cpp.o
CMakeFiles/test.testbin.dir/test_scale_layer.cpp.o CMakeFiles/test.testb
in.dir/test_sigmoid_cross_entropy_loss_layer.cpp.o
CMakeFiles/test.testbin.dir/test_slice_layer.cpp.o
CMakeFiles/test.testbin.dir/test_softmax_layer.cpp.o
CMakeFiles/test.testbin.dir/test_softmax_with_loss_layer.cp
p.o CMakeFiles/test.testbin.dir/test_solver.cpp.o
CMakeFiles/test.testbin.dir/test_solver_factory.cpp.o
CMakeFiles/test.testbin.dir/test_split_layer.cpp.o
CMakeFiles/test.testbin.dir/test_spp_layer.cpp.o CMakeFiles
/test.testbin.dir/test_stochastic_pooling.cpp.o
CMakeFiles/test.testbin.dir/test_syncedmem.cpp.o
CMakeFiles/test.testbin.dir/test_tanh_layer.cpp.o
CMakeFiles/test.testbin.dir/test_threshold_layer.cpp.o CMakeFiles/t
est.testbin.dir/test_tile_layer.cpp.o
CMakeFiles/test.testbin.dir/test_upgrade_proto.cpp.o

Bug#838652: marked as done (Segmentation fault in openssl)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:51:43 +
with message-id 
and subject line Bug#838652: fixed in openssl 1.0.1t-1+deb8u5
has caused the Debian Bug report #838652,
regarding Segmentation fault in openssl
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.)


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

Package: openssl
Version: 1.0.1t-1+deb8u4
Severity: important

Dear OpenSSL maintainers,

the most recent Debian security update for openssl introduces a 
segmentation fault while running openssl:


# openssl x509 -noout -dates -subject -issuer -text -in 
/etc/ssl/certs/iserv.crt

notBefore=Oct  9 02:17:03 2015 GMT
notAfter=Oct  9 02:17:10 2017 GMT
subject= /C=DE/ST=Niedersachsen/L=Braunschweig/O=IServ 
GmbH/CN=dev2.iserv.eu/emailAddress=hostmas...@iserv.eu
issuer= /C=IL/O=StartCom Ltd./OU=Secure Digital Certificate 
Signing/CN=StartCom Class 2 Primary Intermediate Server CA

Certificate:
Data:
Version: 3 (0x2)
Serial Number:
08:28:21:16:be:a3:fe
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=IL, O=StartCom Ltd., OU=Secure Digital Certificate 
Signing, CN=StartCom Class 2 Primary Intermediate Server CA

Validity
Not Before: Oct  9 02:17:03 2015 GMT
Not After : Oct  9 02:17:10 2017 GMT
Subject: C=DE, ST=Niedersachsen, L=Braunschweig, O=IServ GmbH, 
CN=dev2.iserv.eu/emailAddress=hostmas...@iserv.eu

Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (4096 bit)
Modulus:
00:af:0c:91:61:91:4d:96:c4:30:87:e7:cc:e6:b4:
dc:5a:b4:73:6f:ef:ec:65:50:54:6c:2f:1c:84:df:
1d:38:b5:d2:f0:ac:83:e4:09:46:23:d5:02:23:ae:
2e:fa:48:3f:f2:82:c7:d6:4b:63:7d:65:98:9b:b0:
4c:ba:0d:96:12:7e:30:55:53:32:b9:99:0b:b9:9c:
8a:b2:79:60:30:4c:50:71:61:da:8c:6b:00:ee:39:
95:36:a1:b2:e3:38:fb:44:9e:ac:6f:ca:3c:d3:87:
ce:f8:20:fd:e4:bb:1a:70:57:4a:6e:05:64:3a:66:
aa:c8:b8:cb:91:49:ae:74:b0:38:3d:5d:15:45:0a:
77:31:f1:d3:bc:dd:f7:bd:8d:84:fc:7f:49:4e:f5:
b3:8f:87:ee:e0:12:18:6d:9f:f6:f1:56:26:23:ab:
78:cf:c9:00:7d:0b:ce:0c:eb:45:d1:e7:95:09:40:
d6:30:34:2b:ad:12:91:88:2b:d3:96:db:e2:ee:be:
72:eb:98:64:d0:17:de:56:21:a0:08:d4:58:7d:f1:
04:aa:06:ae:b0:83:12:0a:60:e1:59:cf:6e:41:66:
67:90:cf:b8:40:de:ef:fd:d3:e2:98:b8:a7:2b:98:
bd:9b:c3:9a:ec:fe:e9:06:82:22:b5:f7:e4:89:4d:
0b:bc:60:15:64:e3:0d:c6:fe:75:d8:ff:26:a5:d9:
d6:73:68:9a:61:4e:18:1c:d4:15:e6:b8:17:f0:18:
97:81:a9:a6:b4:41:17:1e:48:73:74:7b:42:61:f0:
30:56:ea:e2:36:31:55:0f:f3:86:5f:02:60:63:91:
6f:8a:80:91:e6:ce:d6:37:bb:2b:a3:a6:1c:be:4e:
f5:4f:d5:48:e5:b2:c8:76:1a:3e:1f:76:74:0d:80:
20:a4:31:f4:25:87:61:76:97:95:34:3b:70:cb:64:
4c:83:f0:a5:c3:d4:8a:64:08:ce:1b:13:b3:e8:52:
fe:18:2c:e3:dd:7e:7a:7f:e1:e3:d3:2a:59:af:bc:
c1:55:ce:bd:c3:b4:fe:b5:c5:ba:e8:12:7d:02:a7:
6f:4a:10:ba:8e:05:2b:c5:4e:cd:cc:22:0e:2b:ad:
6d:a1:6f:b3:60:75:93:75:56:7f:e6:a5:e4:e9:7b:
c2:c8:c3:95:ad:60:c6:4f:74:58:64:0e:76:7a:3f:
d0:66:16:0d:5b:ec:47:0d:16:27:f2:b9:d7:80:1b:
e0:5e:67:3c:75:5f:8b:4c:85:38:65:70:04:b6:02:
b6:5a:79:cc:bb:99:40:b3:e7:93:7c:15:a0:fd:61:
a4:56:62:ea:c4:01:4f:bb:07:ee:77:fa:ba:eb:88:
f7:20:13
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature, Key Encipherment, Key Agreement
X509v3 Extended Key Usage:
TLS Web Client Authentication, TLS Web Server 
Authentication

X509v3 Subject Key Identifier:
35:BD:44:3E:E6:27:C5:8D:EE:A5:7C:61:80:FF:8B:4A:87:2D:99:4E
X509v3 Authority Key Identifier:

keyid:11:DB:23:45:FD:54:CC:6A:71:6F:84:8A:03:D7:BE:F7:01:2F:26:86

X509v3 Subject Alternative Name:
 

Bug#836171: marked as done (TIFF divide by zero)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:51:14 +
with message-id 
and subject line Bug#836171: fixed in imagemagick 8:6.8.9.9-5+deb8u5
has caused the Debian Bug report #836171,
regarding TIFF divide by zero
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.)


-- 
836171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:imagemagick
version: 8:6.7.7.10-4
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

According to upstream changelog a new
commit f983dcdf9c178e0cbc49608a78713c5669aa1bb5
Author: Cristy 
Date:   Wed Aug 24 09:43:31 2016 -0400

Fix TIFF divide by zero (bug report from Donghai Zhu)
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.8.9.9-5+deb8u5

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

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

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated 
imagemagick 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, 21 Sep 2016 22:24:16 +0200
Source: imagemagick
Binary: imagemagick-common imagemagick-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers imagemagick libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-2 
libmagickcore-6.q16-2-extra libmagickcore-6.q16-dev libmagickwand-6.q16-2 
libmagickwand-6.q16-dev libmagick++-6.q16-5 libmagick++-6.q16-dev 
imagemagick-dbg libimage-magick-q16-perl perlmagick libmagickcore-dev 
libmagickwand-dev libmagick++-dev
Architecture: source all amd64
Version: 8:6.8.9.9-5+deb8u5
Distribution: jessie-security
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-common - image manipulation programs -- infrastructure
 imagemagick-dbg - debugging symbols for ImageMagick
 imagemagick-doc - document files of ImageMagick
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-5 - object-oriented C++ interface to ImageMagick
 libmagick++-6.q16-dev - object-oriented C++ interface to ImageMagick - 
development files
 libmagick++-dev - object-oriented C++ interface to ImageMagick
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-2 - low-level image manipulation library -- quantum depth 
Q16
 libmagickcore-6.q16-2-extra - low-level image manipulation library - extra 
codecs (Q16)
 libmagickcore-6.q16-dev - low-level image manipulation library - development 
files (Q16)
 libmagickcore-dev - low-level image manipulation library -- transition package
 libmagickwand-6-headers - image manipulation library - headers files
 libmagickwand-6.q16-2 - image manipulation library
 libmagickwand-6.q16-dev - image manipulation library - development files
 libmagickwand-dev - image manipulation library - transition for development 
files
 perlmagick - Perl interface to ImageMagick -- transition package
Closes: 835488 836171 836172 836776
Changes:
 imagemagick (8:6.8.9.9-5+deb8u5) jessie-security; urgency=medium
 .
   * Bug fix: "Regression after security update to 8:6.8.9.9-5+deb8u4,
 unable to convert PDF files in PHP", thanks to Tommie Van Mechgelen
 (Closes: #835488).
   * Prevent buffer overflow in SIXEL, PDB, MAP, and CALS coders.
 (Closes: #836172).
   * Fix TIFF file divide by zero.  (Closes: #836171).
   * Fix 

Bug#836172: marked as done (Prevent buffer overflow in SIXEL, PDB, MAP, and CALS coders (bug report from Donghai Zhu))

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:51:14 +
with message-id 
and subject line Bug#836172: fixed in imagemagick 8:6.8.9.9-5+deb8u5
has caused the Debian Bug report #836172,
regarding Prevent buffer overflow in SIXEL, PDB, MAP, and CALS coders (bug 
report from Donghai Zhu)
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.)


-- 
836172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:imagemagick
version: 8:6.7.7.10-4
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org


commit 10b3823a7619ed22d42764733eb052c4159bc8c1
Author: Cristy 
Date:   Tue Aug 23 17:41:17 2016 -0400

Prevent buffer overflow in SIXEL, PDB, MAP, and CALS coders (bug
report from Donghai Zhu)
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.8.9.9-5+deb8u5

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

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

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated 
imagemagick 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, 21 Sep 2016 22:24:16 +0200
Source: imagemagick
Binary: imagemagick-common imagemagick-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers imagemagick libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-2 
libmagickcore-6.q16-2-extra libmagickcore-6.q16-dev libmagickwand-6.q16-2 
libmagickwand-6.q16-dev libmagick++-6.q16-5 libmagick++-6.q16-dev 
imagemagick-dbg libimage-magick-q16-perl perlmagick libmagickcore-dev 
libmagickwand-dev libmagick++-dev
Architecture: source all amd64
Version: 8:6.8.9.9-5+deb8u5
Distribution: jessie-security
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-common - image manipulation programs -- infrastructure
 imagemagick-dbg - debugging symbols for ImageMagick
 imagemagick-doc - document files of ImageMagick
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-5 - object-oriented C++ interface to ImageMagick
 libmagick++-6.q16-dev - object-oriented C++ interface to ImageMagick - 
development files
 libmagick++-dev - object-oriented C++ interface to ImageMagick
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-2 - low-level image manipulation library -- quantum depth 
Q16
 libmagickcore-6.q16-2-extra - low-level image manipulation library - extra 
codecs (Q16)
 libmagickcore-6.q16-dev - low-level image manipulation library - development 
files (Q16)
 libmagickcore-dev - low-level image manipulation library -- transition package
 libmagickwand-6-headers - image manipulation library - headers files
 libmagickwand-6.q16-2 - image manipulation library
 libmagickwand-6.q16-dev - image manipulation library - development files
 libmagickwand-dev - image manipulation library - transition for development 
files
 perlmagick - Perl interface to ImageMagick -- transition package
Closes: 835488 836171 836172 836776
Changes:
 imagemagick (8:6.8.9.9-5+deb8u5) jessie-security; urgency=medium
 .
   * Bug fix: "Regression after security update to 8:6.8.9.9-5+deb8u4,
 unable to convert PDF files in PHP", thanks to Tommie Van Mechgelen
 (Closes: #835488).
   * Prevent buffer overflow in SIXEL, PDB, MAP, and CALS coders.
 (Closes: 

Bug#831117: gtkimageview: diff for NMU version 1.6.4+dfsg-1.1

[Sebastian Ramacher]

Control: tags 831117 + patch
Control: tags 831117 + pending

Dear maintainer,

I've prepared an NMU for gtkimageview (versioned as 1.6.4+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -Nru gtkimageview-1.6.4+dfsg/debian/changelog gtkimageview-1.6.4+dfsg/debian/changelog
--- gtkimageview-1.6.4+dfsg/debian/changelog	2016-02-24 22:20:19.0 +0100
+++ gtkimageview-1.6.4+dfsg/debian/changelog	2016-09-24 21:52:55.0 +0200
@@ -1,3 +1,10 @@
+gtkimageview (1.6.4+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix indentation to allow building with GCC 6. (Closes: #831117)
+
+ -- Johannes Brandstätter   Sat, 24 Sep 2016 21:52:55 +0200
+
 gtkimageview (1.6.4+dfsg-1) unstable; urgency=low
 
   * Replace gdk_pixbuf_new_from_inline() with gdk_pixbuf_new_from_resource()
diff -Nru gtkimageview-1.6.4+dfsg/debian/patches/gcc6.patch gtkimageview-1.6.4+dfsg/debian/patches/gcc6.patch
--- gtkimageview-1.6.4+dfsg/debian/patches/gcc6.patch	1970-01-01 01:00:00.0 +0100
+++ gtkimageview-1.6.4+dfsg/debian/patches/gcc6.patch	2016-09-24 21:52:55.0 +0200
@@ -0,0 +1,18 @@
+Description: Fix indentation to allow building with GCC 6.
+Author: Johannes Brandstätter 
+Bug-Debian: https://bugs.debian.org/831117
+Last-Update: <2016-09-24>
+
+--- gtkimageview-1.6.4+dfsg.orig/src/gtkimagenav.c
 gtkimageview-1.6.4+dfsg/src/gtkimagenav.c
+@@ -71,8 +71,8 @@ static Size
+ gtk_image_nav_get_preview_size (GtkImageNav *nav)
+ {
+ 	GdkPixbuf *pixbuf = gtk_image_view_get_pixbuf (nav->view);
+-if (!pixbuf)
+-return (Size){GTK_IMAGE_NAV_MAX_WIDTH, GTK_IMAGE_NAV_MAX_HEIGHT};
++	if (!pixbuf)
++		return (Size){GTK_IMAGE_NAV_MAX_WIDTH, GTK_IMAGE_NAV_MAX_HEIGHT};
+ 	int img_width = gdk_pixbuf_get_width (pixbuf);
+ 	int img_height = gdk_pixbuf_get_height (pixbuf);
+ 
diff -Nru gtkimageview-1.6.4+dfsg/debian/patches/series gtkimageview-1.6.4+dfsg/debian/patches/series
--- gtkimageview-1.6.4+dfsg/debian/patches/series	2016-02-24 22:07:50.0 +0100
+++ gtkimageview-1.6.4+dfsg/debian/patches/series	2016-09-24 21:51:10.0 +0200
@@ -1,2 +1,3 @@
 resource.patch
 g_mem_set_vtable
+gcc6.patch


signature.asc
Description: PGP signature

Processed: gtkimageview: diff for NMU version 1.6.4+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 831117 + patch
Bug #831117 [src:gtkimageview] gtkimageview: FTBFS with GCC 6: 
gtkimagenav.c:74:5: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
Added tag(s) patch.
> tags 831117 + pending
Bug #831117 [src:gtkimageview] gtkimageview: FTBFS with GCC 6: 
gtkimagenav.c:74:5: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
Added tag(s) pending.

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

Bug#838789: caffe-contrib: FTBFS: libcaffe.so.1.0.0-rc3: undefined reference to `H5LTget_dataset_ndims'

[Andreas Beckmann]

Source: caffe-contrib
Version: 1.0.0~rc3-2
Severity: serious
Justification: fails to build from source

Hi,

caffe-contrib FTBFS in experimental:

[...]
[100%] Linking CXX executable ../../../test/test.testbin
cd "/build/caffe-contrib-1.0.0~rc3/caffe_cuda_build/src/caffe/test" && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/test.testbin.dir/link.txt 
--verbose=1
/usr/bin/g++-5   -g -O2 -fdebug-prefix-map=/build/caffe-contrib-1.0.0~rc3=. 
-fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Wno-sign-comp
are -Wno-uninitialized -O3 -DNDEBUG   -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed CMakeFiles/test.testbin.dir/test_accuracy_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_argmax_layer.cpp.o CMakeFiles/test.tes
tbin.dir/test_batch_norm_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_batch_reindex_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_benchmark.cpp.o 
CMakeFiles/test.testbin.dir/test_bias_layer.cpp.o CMakeFiles/test.tes
tbin.dir/test_blob.cpp.o CMakeFiles/test.testbin.dir/test_caffe_main.cpp.o 
CMakeFiles/test.testbin.dir/test_common.cpp.o 
CMakeFiles/test.testbin.dir/test_concat_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_contrast
ive_loss_layer.cpp.o CMakeFiles/test.testbin.dir/test_convolution_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_data_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_data_transformer.cpp.o 
CMakeFiles/test.testbin.dir/te
st_db.cpp.o CMakeFiles/test.testbin.dir/test_deconvolution_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_dummy_data_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_eltwise_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_e
mbed_layer.cpp.o CMakeFiles/test.testbin.dir/test_euclidean_loss_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_filler.cpp.o 
CMakeFiles/test.testbin.dir/test_filter_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_flatte
n_layer.cpp.o CMakeFiles/test.testbin.dir/test_gradient_based_solver.cpp.o 
CMakeFiles/test.testbin.dir/test_hdf5_output_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_hdf5data_layer.cpp.o 
CMakeFiles/test.testbin.dir/
test_hinge_loss_layer.cpp.o CMakeFiles/test.testbin.dir/test_im2col_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_image_data_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_infogain_loss_layer.cpp.o CMakeFiles/test.tes
tbin.dir/test_inner_product_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_internal_thread.cpp.o 
CMakeFiles/test.testbin.dir/test_io.cpp.o 
CMakeFiles/test.testbin.dir/test_layer_factory.cpp.o CMakeFiles/test.testbin.
dir/test_lrn_layer.cpp.o CMakeFiles/test.testbin.dir/test_math_functions.cpp.o 
CMakeFiles/test.testbin.dir/test_maxpool_dropout_layers.cpp.o 
CMakeFiles/test.testbin.dir/test_memory_data_layer.cpp.o CMakeFiles/test.
testbin.dir/test_multinomial_logistic_loss_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_mvn_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_net.cpp.o 
CMakeFiles/test.testbin.dir/test_neuron_layer.cpp.o CMakeFiles/test
.testbin.dir/test_platform.cpp.o 
CMakeFiles/test.testbin.dir/test_pooling_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_power_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_protobuf.cpp.o CMakeFiles/test.testbin.dir/t
est_random_number_generator.cpp.o 
CMakeFiles/test.testbin.dir/test_reduction_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_reshape_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_scale_layer.cpp.o CMakeFiles/test.testb
in.dir/test_sigmoid_cross_entropy_loss_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_slice_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_softmax_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_softmax_with_loss_layer.cp
p.o CMakeFiles/test.testbin.dir/test_solver.cpp.o 
CMakeFiles/test.testbin.dir/test_solver_factory.cpp.o 
CMakeFiles/test.testbin.dir/test_split_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_spp_layer.cpp.o CMakeFiles
/test.testbin.dir/test_stochastic_pooling.cpp.o 
CMakeFiles/test.testbin.dir/test_syncedmem.cpp.o 
CMakeFiles/test.testbin.dir/test_tanh_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_threshold_layer.cpp.o CMakeFiles/t
est.testbin.dir/test_tile_layer.cpp.o 
CMakeFiles/test.testbin.dir/test_upgrade_proto.cpp.o 
CMakeFiles/test.testbin.dir/test_util_blas.cpp.o 
CMakeFiles/cuda_compile.dir/cuda_compile_generated_test_im2col_kernel.cu.o
  -o ../../../test/test.testbin -rdynamic ../../../lib/libgtest.a 
../../../lib/libcaffe.so.1.0.0-rc3 ../../../lib/libproto.a -lboost_system 
-lboost_thread -lboost_filesystem -lboost_chrono -lboost_date_time -lboost
_atomic -lpthread -lpthread -lglog -lgflags -lprotobuf -lhdf5_cpp 
/usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so -lpthread -lpthread -lglog 
-lgflags -lprotobuf -lhdf5_cpp /usr/lib/x86_64-linux-gnu/hdf5/serial/lib
hdf5.so -lsz -lz -ldl -lm -llmdb -lleveldb -lsnappy -lcudart -lcurand -lcublas 
-Wl,-Bstatic -lcublas_device -Wl,-Bdynamic 
/usr/lib/x86_64-linux-gnu/libopencv_highgui.so.2.4.9 
/usr/lib/x86_64-linux-gnu/libopencv_img
proc.so.2.4.9 

Processed: Re: bats: FTBFS: not ok 7 summary passing tests

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #802191 [src:bats] bats: FTBFS: not ok 7 summary passing tests
Severity set to 'important' from 'serious'

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

Bug#836657: switchsh: please drop the build dependency on hardening-wrapper

[Chris Lamb]

tags 836657 + pending patch
thanks

switchsh 0~20070801-3.3 uploaded to DELAYED/5. The corresponding debdiff is
attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -u switchsh-0~20070801/debian/changelog 
switchsh-0~20070801/debian/changelog
--- switchsh-0~20070801/debian/changelog
+++ switchsh-0~20070801/debian/changelog
@@ -1,3 +1,11 @@
+switchsh (0~20070801-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop build dependency on hardening-wrapper by moving to dpkg-buildflags.
+(Closes: #836657)
+
+ -- Chris Lamb   Sat, 24 Sep 2016 22:23:00 +0200
+
 switchsh (0~20070801-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u switchsh-0~20070801/debian/control switchsh-0~20070801/debian/control
--- switchsh-0~20070801/debian/control
+++ switchsh-0~20070801/debian/control
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Raphael Geissert 
-Build-Depends: debhelper (>= 5), cdbs, hardening-wrapper, quilt
+Build-Depends: debhelper (>= 5), cdbs, quilt
 Standards-Version: 3.8.0
 Homepage: http://www.linux.it/~md/software/
 XS-DM-Upload-Allowed: yes
diff -u switchsh-0~20070801/debian/rules switchsh-0~20070801/debian/rules
--- switchsh-0~20070801/debian/rules
+++ switchsh-0~20070801/debian/rules
@@ -1,8 +1,6 @@
 #!/usr/bin/make -f
 
-export DEB_BUILD_HARDENING=1
-
-CFLAGS += -pedantic -Werror -Wextra -Wformat -Wformat-security
+CFLAGS += $(shell dpkg-buildflags --get CFLAGS) -pedantic -Werror -Wextra 
-Wformat -Wformat-security
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/rules/patchsys-quilt.mk

Bug#802191: bats: FTBFS: not ok 7 summary passing tests

[Tobias Frost]

Control: severity -1 important

I also reproduce this FTBFS in a sid pbuilder enviorment when provoking
an unset TERM:

diff -Naur bats-0.4.0-orig/debian/rules bats-0.4.0/debian/rules
--- bats-0.4.0-orig/debian/rules2014-12-07 06:53:16.0
+0100
+++ bats-0.4.0/debian/rules 2016-09-24 22:23:13.569025103 +0200
@@ -3,6 +3,8 @@
 # output every command that modifies files on the build system.
 #DH_VERBOSE = 1
 
+undefine TERM
+
 # main packaging script based on dh7 syntax
 %:
dh $@

However I cannot reproduce it in a sid pbuilder, so I downgrade this
bug.

--
tobi

On Sun, 18 Oct 2015 09:08:37 +0100 "Chris West (Faux)"  wrote:
> Source: bats
> Version: 0.4.0-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:
> 
> make[1]: Entering directory '/bats-0.4.0'
> bin/bats --tap test
> 1..43
> ok 1 no arguments prints usage instructions
> ok 2 -v and --version print version number
> ok 3 -h and --help print help
> ok 4 invalid filename prints an error
> ok 5 empty test file runs zero tests
> ok 6 one passing test
> not ok 7 summary passing tests
> # (in test file test/bats.bats, line 46)
> #   `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
> not ok 8 summary passing and skipping tests
> # (in test file test/bats.bats, line 52)
> #   `[ "${lines[2]}" = "2 tests, 0 failures, 1 skipped" ]' failed
> not ok 9 summary passing and failing tests
> # (in test file test/bats.bats, line 58)
> #   `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
> not ok 10 summary passing, failing and skipping tests
> # (in test file test/bats.bats, line 64)
> #   `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
> ok 11 one failing test
> ok 12 one failing and one passing test
> 
> 
> 
> debian/rules:14: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 1
> make[1]: Leaving directory '/bats-0.4.0'
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/bats.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> 

Processed: Re: switchsh: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> tags 836657 + pending patch
Bug #836657 [switchsh] switchsh: please drop the build dependency on 
hardening-wrapper
Added tag(s) patch and pending.
> thanks
Stopping processing here.

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

Bug#831961: proftpd-dfsg: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop.

[Hilmar Preuße]

On 24.09.2016 11:29, Adrian Bunk wrote:
> On Wed, Aug 24, 2016 at 04:25:07PM -0700, Mahyuddin Susanto wrote:

Hi Adrian,

>> I have committed to proftpd-pkg git repository,
>> I will upload to mentos once the other diff has completed.
>> ...
> 
> what is the status of fixing this Release Critical bug?
> 
We have 3 RC bugs on proftp. For two of them there is a fix in git.
For the third one I/we do not know how to solve it (tag "help" is set).
I'd rather upload a fix for all of these three, as the uploaded package
won't migrate to testing if the third is still present.

I you disagree drop us a note.

Hilmar
-- 
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Bug#831844: [debian-mysql] Bug#831844: mysql-5.6: Multiple security fixes from the July 2016 CPU

[Otto Kekäläinen]

Hello!

2016-09-22 18:10 GMT+03:00 Dominic Hargreaves :
>
> As I need to have a MySQL 5.6 backport supported for the foreseeable
> future, I intend to NMU a new upstream release in the next few weeks.
>
> Does anyone have any objections to this?

I've accepted your Alioth join request.

So you only plan to upload to backports..? If you upload to unstable,
please note that the mysql-5.6 source is missing some important
packaging changes done in mysql-5.7 for Debian unstable (split to
mysql-defaults etc) and anyway uploading mysql-5.6 to unstable anymore
is not recommended, as mysql-5.7 is about to overtake it.

- Otto

Bug#817719: marked as done (weathermap4rrd: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:17:01 +
with message-id 
and subject line Bug#817719: fixed in weathermap4rrd 1.1.999+1.2rc3-3
has caused the Debian Bug report #817719,
regarding weathermap4rrd: 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.)


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

Hi,

The package weathermap4rrd 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: weathermap4rrd
Source-Version: 1.1.999+1.2rc3-3

We believe that the bug you reported is fixed in the latest version of
weathermap4rrd, 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.
Santiago Vila  (supplier of updated weathermap4rrd 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, 24 Sep 2016 19:04:30 +0200
Source: weathermap4rrd
Binary: weathermap4rrd
Architecture: source
Version: 1.1.999+1.2rc3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 weathermap4rrd - script that generates picture network links utilization
Closes: 612173 817719
Changes:
 weathermap4rrd (1.1.999+1.2rc3-3) unstable; urgency=medium
 .
   * QA upload.
   * Switch to dh.
   * Switch to "3.0 (quilt)" source format.
   * Move time 300s back also for RRDs v1.4. Closes: #612173.
   * Raise debhelper compat level to 9. Closes: #817719.
   * Package is orphaned (Bug #651929), set Maintainer to "Debian QA Group".
Checksums-Sha1:
 15db6a87155eb42a2924aaa3b00f4532d699d5eb 1415 
weathermap4rrd_1.1.999+1.2rc3-3.dsc
 4534b1f4dc9f70db13b20bd240d60825888cde03 2244 
weathermap4rrd_1.1.999+1.2rc3-3.debian.tar.xz
Checksums-Sha256:
 d55a0a714cdbb3c14665d089e7aa3f2e57f74c685676c0a37fae9a96a14af2f5 1415 
weathermap4rrd_1.1.999+1.2rc3-3.dsc
 b5c604c8beb7aa7686b532689b60c789a11f4ff3dd81c7f8a568f8c48f2cee52 2244 
weathermap4rrd_1.1.999+1.2rc3-3.debian.tar.xz
Files:
 2828548026f957a696acfd48d07ffa96 1415 net extra 
weathermap4rrd_1.1.999+1.2rc3-3.dsc
 b85a1e039b323966b2d84d64d6faef13 2244 net extra 
weathermap4rrd_1.1.999+1.2rc3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJX5rI4AAoJEEHOfwufG4syYFsH+wZWiuQPCQJk1TODh05NINxY
V8w4qoUGCrJH059g80vPPRaYy7qtDOeO/ORaryG2qRVPT20C09sGqKhvp0tRhI7v
6obspqJR/NC7cOebWxjSYLHtOSCR9U1JABNhIKs1vSw5jmthaMZnPkcTmrAqfe99
30RoD00xoD4RuIN/Y87yBH16pw9Tbmv3SVWTe8CsE2VRXeodXLBvEF43JworyiJu
sq9Mw+GqysPwf3Bu9PDMy18RgV6MC9VQWiChVa7y++P61utrqtSrJYXp4GApJ/Le
G5xvLMCLwjzcn2z3M8C9Hpak+BNRPxbZPH+E5kmp4h1MHKb2eBkvnlgn1LDyLoM=
=jAi+
-END PGP SIGNATURE End Message ---

Bug#838248: marked as done (unadf: CVE-2016-1243 and CVE-2016-1244)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:14:15 +
with message-id 
and subject line Bug#838248: fixed in unadf 0.7.11a-4
has caused the Debian Bug report #838248,
regarding unadf: CVE-2016-1243 and CVE-2016-1244
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.)


-- 
838248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unadf
Version: 0.7.11a-3
Severity: important
Tags: security patch

Hi,

Tuomas Räsänen discovered the following vulnerabilities for unadf.

CVE-2016-1243[0]: stack buffer overflow caused by blindly trusting on pathname 
lengths of archived files.
CVE-2016-1244[1]: execution of unsanitized input

The patch is available here: 
  
http://tmp.tjjr.fi/0001-Fix-unsafe-extraction-by-using-mkdir-instead-of-shel.patch

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1243
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1243
[1] https://security-tracker.debian.org/tracker/CVE-2016-1244
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1244
--- End Message ---
--- Begin Message ---
Source: unadf
Source-Version: 0.7.11a-4

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

Debian distribution maintenance software
pp.
Luciano Bello  (supplier of updated unadf 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, 24 Sep 2016 11:43:06 -0400
Source: unadf
Binary: unadf
Architecture: source amd64
Version: 0.7.11a-4
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Luciano Bello 
Description:
 unadf  - Extract files from an Amiga Disk File dump (.adf)
Closes: 838248
Changes:
 unadf (0.7.11a-4) unstable; urgency=high
 .
   * Orphan package with security issues.
   * Tuomas Räsänene discoveried two security issues (Closes: #838248):
 - CVE-2016-1243: stack buffer overflow caused by blindly trusting on
 pathname lengths of archived files.
 - CVE-2016-1244: execution of unsanitized input.
   * Standards-Version: 3.9.8
Checksums-Sha1:
 1ca4a450211d82969428bb13925a7aac4ffb5be4 1695 unadf_0.7.11a-4.dsc
 15a18d20546e0bbde7a9578987897da87ecaa9b8 17924 unadf_0.7.11a-4.debian.tar.xz
 67608a6e5488bee556cdf127bda5dbce8d0dd41b 71318 unadf-dbgsym_0.7.11a-4_amd64.deb
 5505b8917f7cd2c19d040bbcb76e1fefd369f8af 111052 unadf_0.7.11a-4_amd64.deb
Checksums-Sha256:
 925bce8be8fd58e30b24f1bdbe6b295e70fa7a1516d77f87ddadd6fe5f99f047 1695 
unadf_0.7.11a-4.dsc
 ff8873027d330cf3f87876149bd00fe737e0e9885debdda44ce6e3d27257eca3 17924 
unadf_0.7.11a-4.debian.tar.xz
 cbc5cca895055beddc23413363cbb4be10ff040f728f611cb377875057f92115 71318 
unadf-dbgsym_0.7.11a-4_amd64.deb
 a28f29a4854fea1738f3f2faf1587fd4a966afdbbc04a26f9050bb40cafd85df 111052 
unadf_0.7.11a-4_amd64.deb
Files:
 1ec6937000c5283fdbc33be85e4f6084 1695 utils optional unadf_0.7.11a-4.dsc
 042fd96d51e94e880e88f3adfbb01c03 17924 utils optional 
unadf_0.7.11a-4.debian.tar.xz
 235bb4a1c9bba4bcc7f4343567c29d6a 71318 debug extra 
unadf-dbgsym_0.7.11a-4_amd64.deb
 451348e43e3777bd8a3ab5bd19d534ec 111052 utils optional 
unadf_0.7.11a-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX5sW1AAoJEG7C3vaP/jd0iqIP/1eRKv65uXJrbhjag032SZA7
3ZYps+eco77DaqeJgkTKalE+c1F8JA4kSU0x05JpPz9uthrDyJqb2tAMlAdnoQBW
B+G/mTB0xtKP3uRR4aNm0L22WrA9t3oMGVcsIcAGW/ZbER+8dE6HZIw/vcrG5qQl
zxotWfSHl+8+HI5gFO367Z6547Xe1qtXaBVbAFGt/0fRGaq5Y93tiNHk7KoEWoGm
oUKg4vTWAr/vdHKOwUeRcFi8jY9O/PShfK4Kb5MJMyO28yczBq2vOHQTM83bGWOk
yN0EtRveIVv4d15c/8P2nzfzJ006srACIPL+d5pcmF+kaA3jTDt+vwdjZLg5kOFs
3DbCxKbWu1mxebg1nXjHj1sHCMkJophAujlj4pjT2TuMi/e0gpjemAAit67EBrwL
EXxESn5z8+q+AxH1d64VeIvasxl8NZ+ReLjHuIWf8UgyGaMeoDoJ5fc19rqk7O8g
5gYxdJM29cYjx+CMIzUHDltZWMaM/j5Q51C7ZeIZmz1P3YhvBk9PS8W/kKz/I6iZ

Bug#836934: frobtads: FTBFS with GCC 6: error: exception cleanup for this placement new selects non-placement operator delete

[Andreas Beckmann]

Control: reopen -1

On 2016-09-24 20:46, Sebastian Ramacher wrote:
> On 2016-09-07 13:09:40, Andreas Beckmann wrote:
>> frobtads FTBFS since the default compiler was switched to GCC 6 (which
>> defaults to -std=c++14):
>>
>> g++ -DHAVE_CONFIG_H -I. -I/build/frobtads-1.2.3/.  -DFROBTADS -DTC_TARGET_T3 
>> -DTADSNET  -DOS_DECLARATIVE_TLS  -DVMGLOB_VARS  -D_M_IX86_64 -DRUNFAST 
>> -I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads2 
>> -I/build/frobtads-1.2.3/./tads3 -I/build/frobtads-1.2.3/./tads3/unix  
>> -DT3_INC_DIR=\"/usr/share/frobtads/tads3/include\" 
>> -DT3_LIB_DIR=\"/usr/share/frobtads/tads3/lib\" 
>> -DT3_RES_DIR=\"/usr/share/frobtads/tads3/res\" 
>> -DT3_LOG_FILE=\"/tmp/frob.log\" -I/build/frobtads-1.2.3/./src 
>> -I/build/frobtads-1.2.3/./tads2 -I/build/frobtads-1.2.3/./src 
>> -I/build/frobtads-1.2.3/./tads3 -I/build/frobtads-1.2.3/./tads3/test 
>> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
>> -fdebug-prefix-map=/build/frobtads-1.2.3=. -fstack-protector-strong -Wformat 
>> -Werror=format-security -fno-strict-aliasing -pthread -c -o tads3/tcprs.o 
>> /build/frobtads-1.2.3/./tads3/tcprs.cpp
>> In file included from /build/frobtads-1.2.3/./tads3/tcprs.cpp:39:0:
>> /build/frobtads-1.2.3/./tads3/vmbignum.h: In static member function 'static 
>> vm_obj_id_t CVmObjBigNum::create(int, const bignum_t*)':
>> /build/frobtads-1.2.3/./tads3/vmbignum.h:585:45: error: exception cleanup 
>> for this placement new selects non-placement operator delete [-fpermissive]
>>  new (vmg_ id) CVmObjBigNum(vmg_ prec);

> frobtads builds fine in todays sid. Closing.

Nope. It builds fine on amd64, but fails on i386 (both in pbuilder on an
amd64 host).

Andreas

Processed: Re: Bug#836934: frobtads: FTBFS with GCC 6: error: exception cleanup for this placement new selects non-placement operator delete

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #836934 {Done: Sebastian Ramacher } [src:frobtads] 
frobtads: FTBFS with GCC 6: error: exception cleanup for this placement new 
selects non-placement operator delete
Bug reopened
Ignoring request to alter fixed versions of bug #836934 to the same values 
previously set

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

Processed: tagging 817437

[Debian Bug Tracking System]

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

> # dh compat 4 removal not relevant for stable
> tags 817437 + stretch sid
Bug #817437 [src:dpkg-sig] dpkg-sig: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817437 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#835526: marked as done (git-build-recipe: FTBFS in testing (broken by new git))

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 19:24:52 +
with message-id 
and subject line Bug#835526: fixed in git-build-recipe 0.3.3
has caused the Debian Bug report #835526,
regarding git-build-recipe: FTBFS in testing (broken by new git)
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.)


-- 
835526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:git-build-recipe
Version: 0.3.2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/deb_util.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/recipe.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/main.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/deb_version.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
creating /<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/test_deb_version.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/test_recipe.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/test_blackbox.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
LC_ALL=C.UTF-8 dh_auto_test
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m nose 
E.
==
ERROR: 
gitbuildrecipe.tests.test_recipe.BuildTreeTests.test_build_tree_merge_unrelated
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
348, in merge_branch
child_branch.commit)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
637, in git_call
**kwargs)
  File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
**kwargs).stdout
  File "/usr/lib/python3.5/subprocess.py", line 708, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', '-C', 'target', 'merge', 
'--commit', '-m', 'Merge HEAD', 'cffd324cab4213c080815e51045e11e544b4791a']' 
returned non-zero exit status 128

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests/test_recipe.py",
 line 620, in test_build_tree_merge_unrelated
build_tree(base_branch, "target")
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
464, in build_tree
_build_inner_tree(base_branch, target_path)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
388, in _build_inner_tree
instruction.apply(target_path)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
520, in apply
merge_branch(self.recipe_branch, target_path)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
350, in merge_branch
raise MergeFailed(e.output)
gitbuildrecipe.recipe.MergeFailed: git merge failed:
fatal: refusing to merge unrelated histories

 >> begin captured logging << 
root: INFO: Building tree.
root: INFO: Retrieving 'source1' to put at 'target'.
root: INFO: Merging 'source2' in to 'target'.
- >> end captured logging << -

Bug#836927: marked as done (assaultcube: FTBFS with GCC 6: error: 'float round(float)' conflicts with a previous declaration)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 19:21:38 +
with message-id 
and subject line Bug#836927: fixed in assaultcube 1.1.0.4+dfsg2-1.2
has caused the Debian Bug report #836927,
regarding assaultcube: FTBFS with GCC 6: error: 'float round(float)' conflicts 
with a previous declaration
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.)


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

Hi,

assaultcube FTBFS since the switch to GCC 6 (which defaults to -std=c++14) was 
made:

[...]
g++ -O3 -fomit-frame-pointer -g -Wall -fsigned-char -rdynamic -I. -Ibot 
-I../enet/include -I/usr/include `sdl-config --cflags` -idirafter ../include -o 
cube.h.gch.tmp cube.h
In file included from cube.h:8:0:
tools.h: In function 'float round(float)':
tools.h:58:34: error: 'float round(float)' conflicts with a previous declaration
 static inline float round(float x) { return floor(x + 0.5f); }
  ^
In file included from /usr/include/c++/6/math.h:36:0,
 from platform.h:9,
 from cube.h:7:
/usr/include/c++/6/cmath:1708:3: note: previous declaration 'constexpr float 
std::round(float)'
   round(float __x)
   ^
In file included from cube.h:53:0:
protos.h: In member function 'bool servercommandline::checkarg(const char*)':
protos.h:914:17: warning: this 'else' clause does not guard... 
[-Wmisleading-indentation]
 else if(ai > 0) maxdemos = ai; break;
 ^~~~
protos.h:914:48: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'else'
 else if(ai > 0) maxdemos = ai; break;
^
Makefile:138: recipe for target 'cube.h.gch' failed
make[1]: *** [cube.h.gch] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: assaultcube
Source-Version: 1.1.0.4+dfsg2-1.2

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

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

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

Debian distribution maintenance software
pp.
Johannes Brandstätter  (supplier of updated assaultcube 
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, 24 Sep 2016 19:42:32 +0200
Source: assaultcube
Binary: assaultcube
Architecture: source
Version: 1.1.0.4+dfsg2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Johannes Brandstätter 
Description:
 assaultcube - realistic first-person-shooter
Closes: 836927
Changes:
 assaultcube (1.1.0.4+dfsg2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix building with GCC 6. (Closes: #836927)
Checksums-Sha1:
 768d460cd60aa35a92e1ef8df764e0cf79d79654 2144 assaultcube_1.1.0.4+dfsg2-1.2.dsc
 84a78f9bf8ee2836d0b8fc7b00697873e2aa411a 9976 
assaultcube_1.1.0.4+dfsg2-1.2.debian.tar.xz
Checksums-Sha256:
 90a370c5d97a8387333f1ebe6f33ba991ce8cc4d589e9bc007ddf8383303d288 2144 
assaultcube_1.1.0.4+dfsg2-1.2.dsc
 16d15a36e71cba3f6496a37168985cfb43d3c5f3162d9bb79605b36f5408813c 9976 
assaultcube_1.1.0.4+dfsg2-1.2.debian.tar.xz
Files:
 a65e13f3a209c66018c381e5bfbc7b68 2144 contrib/games optional 
assaultcube_1.1.0.4+dfsg2-1.2.dsc
 9d129227981e5b63261654a4150d8b02 9976 contrib/games optional 
assaultcube_1.1.0.4+dfsg2-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX5sO/AAoJEGny/FFupxmTRDUP/AvaeNY+6MwMllT6xtgxAU/M
kPXuqsxjuKqMtE+DrdHd7KuJl/dULYLXx90m8mJVK4HAvrf8nmgdtV2ACztT0r9g
1Cxl/dogyYHtVYT2F7vJF50FD39zN73QYJv5syWjhPUnjVV3uyp7HZwQLBLARbVI
ho3X8AI+Lirx3XD2CaUpHeTrDgjyRZqV7D47vmJP+lftoTPuljUp2PdGBShfWOTh
Bij7weWvJHHsordiEvYCmBuT1WUZ8fb6UtK/5FyV6bPvt8K4XD9iqHVu+eI74VBq
LFfrPwTh2V+GHFFCbC5cnV9NPY1C5eV82emw44A/tuROnCY+IePvLHoXqYlPPuXl
rQQvfXWv0epaCeN0h6NK3rQtqNVCmIS2tykub7m+dZoWpUQHvS7k/+00gDmQB+nR

Processed: qqwing: diff for NMU version 1.3.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 811981 + patch
Bug #811981 [qqwing] qqwing: FTBFS with GCC 6: symbol changes
Added tag(s) patch.
> tags 811981 + pending
Bug #811981 [qqwing] qqwing: FTBFS with GCC 6: symbol changes
Added tag(s) pending.

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

Bug#812044: marked as done (scim: FTBFS with GCC 6: declared to take const reference)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 21:18:13 +0200
with message-id 

and subject line Builds fine in latest version
has caused the Debian Bug report #812044,
regarding scim: FTBFS with GCC 6: declared to take const reference
to be marked as done.

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

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


-- 
812044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scim
Version: 1.4.15-5
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

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
...
> make[4]: Entering directory '/<>/src'
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
>  -I.. -I../src -I.. -I../src -I../intl -DSCIM_DATADIR=\"/usr/share/scim\" 
> -DSCIM_LOCALEDIR=\"/usr/share/locale\" -DSCIM_SYSCONFDIR=\"/etc\" 
> -DSCIM_LIBEXECDIR=\"/usr/lib/x86_64-linux-gnu/scim-1.0\" 
> -DSCIM_ICONDIR=\"/usr/share/scim/icons\" 
> -DSCIM_MODULE_PATH=\"/usr/lib/x86_64-linux-gnu/scim-1.0\"  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o scim_backend.lo scim_backend.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../src -I.. -I../src 
> -I../intl -DSCIM_DATADIR=\"/usr/share/scim\" 
> -DSCIM_LOCALEDIR=\"/usr/share/locale\" -DSCIM_SYSCONFDIR=\"/etc\" 
> -DSCIM_LIBEXECDIR=\"/usr/lib/x86_64-linux-gnu/scim-1.0\" 
> -DSCIM_ICONDIR=\"/usr/share/scim/icons\" 
> -DSCIM_MODULE_PATH=\"/usr/lib/x86_64-linux-gnu/scim-1.0\" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c scim_backend.cpp  -fPIC -DPIC -o 
> .libs/scim_backend.o
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/ios:40,
>  from /usr/include/c++/6/ostream:38,
>  from /usr/include/c++/6/iostream:39,
>  from scim.h:193,
>  from scim_backend.cpp:33:
> /usr/include/c++/6/bits/stl_pair.h: In instantiation of 'struct 
> std::pair, 
> scim::Pointer >':
> scim_backend.cpp:117:82:   required from here
> /usr/include/c++/6/bits/stl_pair.h:205:17: error: 'constexpr std::pair<_T1, 
> _T2>::pair(const std::pair<_T1, _T2>&) [with _T1 = const 
> std::__cxx11::basic_string; _T2 = 
> scim::Pointer]' declared to take const reference, 
> but implicit declaration would take non-const
>constexpr pair(const pair&) = default;
>  ^~~~
> 
> Makefile:909: recipe for target 'scim_backend.lo' failed
> make[4]: *** [scim_backend.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 1.4.17-1

Not reproducible with latest version (1.4.17-1).
--- End Message ---

Bug#811981: qqwing: diff for NMU version 1.3.4-1.1

[Sebastian Ramacher]

Control: tags 811981 + patch
Control: tags 811981 + pending

Dear maintainer,

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

Regards.
-- 
Sebastian Ramacher
diff -Nru qqwing-1.3.4/debian/changelog qqwing-1.3.4/debian/changelog
--- qqwing-1.3.4/debian/changelog	2015-08-03 12:13:23.0 +0200
+++ qqwing-1.3.4/debian/changelog	2016-09-24 21:07:25.0 +0200
@@ -1,3 +1,10 @@
+qqwing (1.3.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Replacing symbol from template instatiation with newer version. (Closes: #811981)
+
+ -- Johannes Brandstätter   Sat, 24 Sep 2016 21:07:25 +0200
+
 qqwing (1.3.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru qqwing-1.3.4/debian/libqqwing2v5.symbols qqwing-1.3.4/debian/libqqwing2v5.symbols
--- qqwing-1.3.4/debian/libqqwing2v5.symbols	2015-07-03 23:40:52.0 +0200
+++ qqwing-1.3.4/debian/libqqwing2v5.symbols	2016-09-24 21:05:18.0 +0200
@@ -77,6 +77,4 @@
  _ZN6qqwing7LogItemD1Ev@Base 1.3.2
  _ZN6qqwing7LogItemD2Ev@Base 1.3.2
  _ZNKSt5ctypeIcE8do_widenEc@Base 1.3.2
- _ZNSt6vectorIPN6qqwing7LogItemESaIS2_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS2_S4_EERKS2_@Base 1.3.2
-
- 
\ No newline at end of file
+ (optional)_ZNSt6vectorIPN6qqwing7LogItemESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base 1.3.4


signature.asc
Description: PGP signature

Processed: Re: Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.7.3-1
Bug #838734 [plasma-discover] [plasma-discover] plasma-discover uninstalls 
packages during upgrades without asking for confirmation
Marked as found in versions plasma-discover/5.7.3-1.

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

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Diederik de Haas]

Control: found -1 5.7.3-1

On zaterdag 24 september 2016 21:02:28 CEST Diederik de Haas wrote:
> So this happened on 24th of August and then the perl migration wasn't 
> happening, thus reopening the bug.

As 5.7.4-1 was uploaded on 26th of August, my version was thus 5.7.3-1, 
marking this bug as such.

> I'll spare you my real opinion.

That didn't last long :-P

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

Processed: Re: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #838734 {Done: Chris Lamb } [plasma-discover] 
[plasma-discover] plasma-discover uninstalls packages during upgrades without 
asking for confirmation
Bug reopened
Ignoring request to alter fixed versions of bug #838734 to the same values 
previously set

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

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Diederik de Haas]

Control: reopen -1

On Sat, 24 Sep 2016 15:52:33 +0100 Chris Lamb  wrote:
> > [plasma-discover] plasma-discover uninstalls packages during upgrades
> > without asking for confirmation> 
> This is due to the ongoing Perl migration. There was a mail sent to
> debian-devel-announce but I believe it was unfortunately blocked.
> 
> I'm closing your bug as this is not an issue that can be resolved by
> plasma-discover, alas. :(

From my #debian-qt-kde logs:
[27.08 01:43]  plasma-discover is a giant piece of junk and imo 
should be removed from every meta package
[27.08 01:43]   /rant
[27.08 01:45]  for a change I used it's function and did happily 
uninstall plasma-desktop, plasma-workspace, sddm and a number of other 
essential programs
[27.08 01:45]  without any warning that is. Trying to fix it with 
aptitude seems to be a no go as it's not able to resolve conflicts
[27.08 01:45]  I have _never_ seen/happen that before

So this happened on 24th of August and then the perl migration wasn't 
happening, thus reopening the bug.

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

Bug#838746: marked as done (FTBFS: AttributeError: 'NoneType' object has no attribute 'literal_value')

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 19:00:13 +
with message-id 
and subject line Bug#838746: fixed in mozilla-gnome-keyring 0.11+git4-3
has caused the Debian Bug report #838746,
regarding FTBFS: AttributeError: 'NoneType' object has no attribute 
'literal_value'
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.)


-- 
838746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mozilla-gnome-keyring
Version: 0.11+git4-2
Severity: serious

Dear Maintainer,

mozilla-gnome-keyring FTBFS in sid. The full log is available from:

 
https://buildd.debian.org/status/fetch.php?pkg=mozilla-gnome-keyring=all=0.11%2Bgit4-2=1474545732

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mozilla-gnome-keyring
Source-Version: 0.11+git4-3

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated mozilla-gnome-keyring 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Sep 2016 11:29:52 +0200
Source: mozilla-gnome-keyring
Binary: xul-ext-gnome-keyring
Architecture: source all
Version: 0.11+git4-3
Distribution: unstable
Urgency: medium
Maintainer: Ximin Luo 
Changed-By: Ximin Luo 
Description:
 xul-ext-gnome-keyring - Store mozilla passwords in GNOME Keyring
Closes: 838746
Changes:
 mozilla-gnome-keyring (0.11+git4-3) unstable; urgency=medium
 .
   * Set maxVersion to 999. (Closes: #838746)
Checksums-Sha1:
 76125d5b5e0f49c62d9237ec62f56c5c15451a27 2046 
mozilla-gnome-keyring_0.11+git4-3.dsc
 dafe0c3bcba32036c6f097f8616b803ffca78b4b 2660 
mozilla-gnome-keyring_0.11+git4-3.debian.tar.xz
 607b1b6cd2d1ab897cfa8b1a1003cf587334f340 15454 
xul-ext-gnome-keyring_0.11+git4-3_all.deb
Checksums-Sha256:
 fc7a56902b7d37390c3f2b8857b67f2abb572b090dc72aee932b3fcd695476a5 2046 
mozilla-gnome-keyring_0.11+git4-3.dsc
 5846b99c3704abc0c9024d22cfc221c66a6c5bf5b8e7b2a2dcc6c1938771a32b 2660 
mozilla-gnome-keyring_0.11+git4-3.debian.tar.xz
 0a89c9e5ff8a30cf700da6c6c40db2aa8395189fc958bbcdd4708ae780263321 15454 
xul-ext-gnome-keyring_0.11+git4-3_all.deb
Files:
 874207f628470022f938685befbc6c07 2046 web optional 
mozilla-gnome-keyring_0.11+git4-3.dsc
 993c6ac1bb72ff96553e86465af3165f 2660 web optional 
mozilla-gnome-keyring_0.11+git4-3.debian.tar.xz
 7545b1c1a673a2b4247e2c6a18b89885 15454 web optional 
xul-ext-gnome-keyring_0.11+git4-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJX5lP5AAoJEIYN7zuPZQt5/SUP/2XVpqTQwdxrWTLyqgvM6JG4
F0nM9ELegKeOzrhnETMqOr26BXiUTmqjhfAH16/4aOjJ/sjOP5+R73GuectdOqNL
XeTIBtuWHjwUl6bQ721XeaJJnTjMBRZJ24HSETSLEe0Ul/hii3QVw3TLN4DaPYuU
q5r8VKloCE7dYsDE2Lr56PGdo1iiFTrvXGE47DNuvDHjUY894Y/i252evJMp5e9u
lmE9P4wNOfwVSLUAWD/oKWGya3x7F2Swh8Fo41JVtX6YSPypq6ILvQ6gsbjw13aM
nUuvGXCaBLRgjqSO5NBCjV3ir/84L/zRw8DDJNRnUY1+YTBGboq/+g6HOyIbs3Ri
/BCD+vNFvKGf+sDvh39W07hqmqnGGz96u4wHwOThfZWCByjZwh45sGXbVlTxylhA
i+OxMmhRrAYgWMAMgW6HFWTDJZ9V5+9PJaPeTn573KC+SvkNQwcm3YTXg53l/3N6
zAnb5fi/RVLp6Z4q6/G+YolfLvi3VpwsXqQKvW08nDI6mB3dl8EucGRawUdPs4mR
KIytYWa4sb3Jo+4gNZPUs3+n+2Wk2eFsMpjjw30ucceF0MVzPelklbujDPRXbCJR
tNBE7jqhjMmtAtGAPsTj0GVcjQjBtjDjdLBxOdeQoXwVkpIp3Tq6l/YzAUe60ADO
ihOeXL0q5UDlIPm2ycJa
=Vapo
-END PGP SIGNATURE End Message ---

Bug#811950: marked as done (openhpi: FTBFS with GCC 6: unable to find string literal operator)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:50:57 +0200
with message-id <1474743057.8947.4.ca...@2ds.eu>
and subject line 
has caused the Debian Bug report #811950,
regarding openhpi: FTBFS with GCC 6: unable to find string literal operator
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.)


-- 
811950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openhpi
Version: 2.14.1-1.4
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-literal-operator

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
...
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
> -I../../include -I../../utils -I../../utils -g -O2 -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall 
> -Wpointer-arith -Wformat=2 -Wformat-security -Wformat-nonliteral -Wcast-qual 
> -Wcast-align -Wshadow -Wwrite-strings -Wredundant-decls -Wno-strict-aliasing 
> -fno-strict-aliasing -Wno-unused-value -D_GNU_SOURCE -D_REENTRANT 
> -fexceptions -MT ipmi.lo -MD -MP -MF .deps/ipmi.Tpo -c ipmi.cpp  -fPIC -DPIC 
> -o .libs/ipmi.o
> In file included from ../../include/openhpi.h:29:0,
>  from ipmi_domain.h:36,
>  from ipmi.h:30,
>  from ipmi.cpp:22:
> ipmi.cpp: In function 'void* IpmiOpen(GHashTable*, unsigned int, 
> oh_evt_queue*)':
> ../../include/oh_error.h:49:37: error: unable to find string literal operator 
> 'operator""format' with 'const char [18]', 'long unsigned int' arguments
>syslog(3, "ERROR: (%s, %d, "format")", __FILE__, __LINE__,## __VA_ARGS__); 
> \
>  ^
> 
> ipmi.cpp:297:8: note: in expansion of macro 'err'
> err( "No config file provided.ooops!" );
> ^~~
> 
> ../../include/oh_error.h:51:35: error: unable to find string literal operator 
> 'operator""format' with 'const char [10]', 'long unsigned int' arguments
> fprintf(stderr, "%s:%d ("format")\n", __FILE__, __LINE__, ## 
> __VA_ARGS__); \
>^
> 
> ipmi.cpp:297:8: note: in expansion of macro 'err'
> err( "No config file provided.ooops!" );
> ^~~
> 
> ../../include/oh_error.h:49:37: error: unable to find string literal operator 
> 'operator""format' with 'const char [18]', 'long unsigned int' arguments
>syslog(3, "ERROR: (%s, %d, "format")", __FILE__, __LINE__,## __VA_ARGS__); 
> \
>  ^
> 
> ipmi.cpp:341:8: note: in expansion of macro 'err'
> err("cannot allocate handler");
> ^~~
> 
> ../../include/oh_error.h:51:35: error: unable to find string literal operator 
> 'operator""format' with 'const char [10]', 'long unsigned int' arguments
> fprintf(stderr, "%s:%d ("format")\n", __FILE__, __LINE__, ## 
> __VA_ARGS__); \
>^
> 
> ipmi.cpp:341:8: note: in expansion of macro 'err'
> err("cannot allocate handler");
> ^~~
> 
> ../../include/oh_error.h:49:37: error: unable to find string literal operator 
> 'operator""format' with 'const char [18]', 'long unsigned int' arguments
>syslog(3, "ERROR: (%s, %d, "format")", __FILE__, __LINE__,## __VA_ARGS__); 
> \
>  ^
> 
> ipmi.cpp:354:8: note: in expansion of macro 'err'
> err("cannot allocate RPT cache");
> ^~~
> 
> ../../include/oh_error.h:51:35: error: unable to find string literal operator 
> 'operator""format' with 'const char [10]', 'long unsigned int' arguments
> fprintf(stderr, "%s:%d ("format")\n", __FILE__, __LINE__, ## 
> __VA_ARGS__); \
...
--- End Message ---
--- Begin Message ---
Version: 3.6.1-2

Built fine on unstable/amd64, therefore closing.--- End Message ---

Bug#836934: marked as done (frobtads: FTBFS with GCC 6: error: exception cleanup for this placement new selects non-placement operator delete)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:46:38 +0200
with message-id <20160924184638.njppso4tw7xh2...@ramacher.at>
and subject line Re: Bug#836934: frobtads: FTBFS with GCC 6: error: exception 
cleanup for this placement new selects non-placement operator delete
has caused the Debian Bug report #836934,
regarding frobtads: FTBFS with GCC 6: error: exception cleanup for this 
placement new selects non-placement operator delete
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.)


-- 
836934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frobtads
Version: 1:1.2.3-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source

Hi,

frobtads FTBFS since the default compiler was switched to GCC 6 (which
defaults to -std=c++14):

g++ -DHAVE_CONFIG_H -I. -I/build/frobtads-1.2.3/.  -DFROBTADS -DTC_TARGET_T3 
-DTADSNET  -DOS_DECLARATIVE_TLS  -DVMGLOB_VARS  -D_M_IX86_64 -DRUNFAST 
-I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads2 
-I/build/frobtads-1.2.3/./tads3 -I/build/frobtads-1.2.3/./tads3/unix  
-DT3_INC_DIR=\"/usr/share/frobtads/tads3/include\" 
-DT3_LIB_DIR=\"/usr/share/frobtads/tads3/lib\" 
-DT3_RES_DIR=\"/usr/share/frobtads/tads3/res\" -DT3_LOG_FILE=\"/tmp/frob.log\" 
-I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads2 
-I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads3 
-I/build/frobtads-1.2.3/./tads3/test -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/build/frobtads-1.2.3=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-strict-aliasing -pthread -c -o tads3/tcprs.o 
/build/frobtads-1.2.3/./tads3/tcprs.cpp
In file included from /build/frobtads-1.2.3/./tads3/tcprs.cpp:39:0:
/build/frobtads-1.2.3/./tads3/vmbignum.h: In static member function 'static 
vm_obj_id_t CVmObjBigNum::create(int, const bignum_t*)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:585:45: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum(vmg_ prec);
 ^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
/build/frobtads-1.2.3/./tads3/vmbignum.h: In static member function 'static 
vm_obj_id_t CVmObjBigNum::create(int, const bignum_t&)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:596:45: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum(vmg_ prec);
 ^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
/build/frobtads-1.2.3/./tads3/vmbignum.h: In member function 'virtual void 
CVmMetaclassBigNum::create_for_image_load(vm_obj_id_t)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:1640:36: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum();
^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
/build/frobtads-1.2.3/./tads3/vmbignum.h: In member function 'virtual void 
CVmMetaclassBigNum::create_for_restore(vm_obj_id_t)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:1647:36: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum();
^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
Makefile:6604: recipe for target 'tads3/tcprs.o' failed
make[2]: *** [tads3/tcprs.o] Error 1


Andreas
--- End Message ---
--- Begin Message ---
On 2016-09-07 13:09:40, Andreas Beckmann wrote:
> Source: frobtads
> Version: 1:1.2.3-1
> Severity: serious
> Tags: sid stretch
> Justification: fails to build from source
> 
> Hi,
> 
> frobtads FTBFS since the default compiler was switched to GCC 6 (which
> defaults to -std=c++14):
> 
> g++ -DHAVE_CONFIG_H -I. -I/build/frobtads-1.2.3/.  -DFROBTADS -DTC_TARGET_T3 
> -DTADSNET  -DOS_DECLARATIVE_TLS  -DVMGLOB_VARS  -D_M_IX86_64 -DRUNFAST 
> -I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads2 
> -I/build/frobtads-1.2.3/./tads3 -I/build/frobtads-1.2.3/./tads3/unix  
> -DT3_INC_DIR=\"/usr/share/frobtads/tads3/include\" 
> 

Bug#683103: Same issue upgrading from wheezy to jessie

[Simó Albert i Beltran]

Hello,

I found the same issue upgrading a VPS from wheezy to jessie with the
version 2.88dsf-59.

$ ls -l /dev/shm
lrwxrwxrwx 1 root root 8 Nov 28  2014 /dev/shm -> /run/shm
$ ls -l /run/shm
lrwxrwxrwx 1 root root 8 Oct 13  2015 /run/shm -> /dev/shm
$ mountpoint /dev
/dev is not a mountpoint

Thanks.



signature.asc
Description: OpenPGP digital signature

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Diederik de Haas]

On zaterdag 24 september 2016 20:02:42 CEST JanKusanagi wrote:
> The thing is, a user upgrading with this program, might end up
> destroying their system. I'd consider this 'grave'.

Not just 'might', the one time I tried/used it, it removed plasma-desktop, 
sddm and a couple of more essential KDE packages, including their 
dependencies.
Apparently I only complained about it in #debian-qt-kde but didn't report it.

> From what I see, the real problem here is that plasma-discover's
> "upgrade" functionality is acting like a "aptitude full-upgrade",
> removing whatever's necessary, possible removing half your system,
> instead of acting like a "aptitude safe-upgrade", which would hold the
> problematic packages, and not remove anything.

This is exactly what seems to be happening and I consider this to be plain 
wrong. I'm actively trying to dissuade people from using full-upgrade (even) 
from the command-line, where you indeed at least have to give confirmation 
before removing your whole system.

On Sat, 24 Sep 2016 13:50:18 -0400 Scott Kitterman wrote:
> Developers are users too.  If your position is that Discover isn't suitable
> for use in testing/unstable then what that means is Discover gets released
> untested.  That's not a recipe for success.

My solution to the above problem was to make sure (apt-pinning) that plasma-
discover would NEVER be installed on any of my systems, ever.
It was available on my (new) laptop because I did a fresh install of KDE. As a 
lot of testing/unstable users have their system for quite a while, they likely 
don't even have plasma-discover installed.
Thus I consider the above statement from Scott a massive understatement (and 
it may even be meant that way).

> Discover is meant for users who have no idea what a "package" is, so
> prompting them with questions they don't understand will highly likely
> not happen

Maybe clicking the upgrade button is too confusing too, you may want to remove 
that.
And that's the most positive thing I can say about plasma-discover; I'll spare 
you my real opinion.


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

Bug#811742: smpeg: diff for NMU version 0.4.5+cvs20030824-7.2

[Sebastian Ramacher]

Control: tags 811742 + patch
Control: tags 811742 + pending

Dear maintainer,

I've prepared an NMU for smpeg (versioned as 0.4.5+cvs20030824-7.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -Nru smpeg-0.4.5+cvs20030824/debian/changelog smpeg-0.4.5+cvs20030824/debian/changelog
--- smpeg-0.4.5+cvs20030824/debian/changelog	2014-08-31 00:21:03.0 +0200
+++ smpeg-0.4.5+cvs20030824/debian/changelog	2016-09-24 20:30:31.0 +0200
@@ -1,3 +1,10 @@
+smpeg (0.4.5+cvs20030824-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix compilation with GCC 6. (Closes: #811742)
+
+ -- Johannes Brandstätter   Sat, 24 Sep 2016 20:30:31 +0200
+
 smpeg (0.4.5+cvs20030824-7.1) unstable; urgency=medium
 
   * Non-maintainer upload with maintainer permission. Thanks!
diff -Nru smpeg-0.4.5+cvs20030824/debian/patches/340_gcc6.diff smpeg-0.4.5+cvs20030824/debian/patches/340_gcc6.diff
--- smpeg-0.4.5+cvs20030824/debian/patches/340_gcc6.diff	1970-01-01 01:00:00.0 +0100
+++ smpeg-0.4.5+cvs20030824/debian/patches/340_gcc6.diff	2016-09-24 20:30:28.0 +0200
@@ -0,0 +1,40 @@
+Description: Fix compiling with GCC 6.
+Author: Johannes Brandstätter 
+Bug-Debian: https://bugs.debian.org/811742
+Last-Update: <2016-09-24>
+
+Index: smpeg-0.4.5+cvs20030824/audio/huffmantable.cpp
+===
+--- smpeg-0.4.5+cvs20030824.orig/audio/huffmantable.cpp
 smpeg-0.4.5+cvs20030824/audio/huffmantable.cpp
+@@ -9,6 +9,7 @@
+ #include "config.h"
+ #endif
+ 
++#include 
+ #include "MPEGaudio.h"
+ 
+ static const unsigned int
+@@ -550,11 +551,11 @@ htd33[ 31][2]={{ 16,  1},{  8,  1},{  4,
+ 
+ const HUFFMANCODETABLE MPEGaudio::ht[HTN]=
+ {
+-  { 0, 0-1, 0-1, 0,  0, htd33},
++  { 0, UINT_MAX, UINT_MAX, 0,  0, htd33},
+   { 1, 2-1, 2-1, 0,  7,htd01},
+   { 2, 3-1, 3-1, 0, 17,htd02},
+   { 3, 3-1, 3-1, 0, 17,htd03},
+-  { 4, 0-1, 0-1, 0,  0, htd33},
++  { 4, UINT_MAX, UINT_MAX, 0,  0, htd33},
+   { 5, 4-1, 4-1, 0, 31,htd05},
+   { 6, 4-1, 4-1, 0, 31,htd06},
+   { 7, 6-1, 6-1, 0, 71,htd07},
+@@ -564,7 +565,7 @@ const HUFFMANCODETABLE MPEGaudio::ht[HTN
+   {11, 8-1, 8-1, 0,127,htd11},
+   {12, 8-1, 8-1, 0,127,htd12},
+   {13,16-1,16-1, 0,511,htd13},
+-  {14, 0-1, 0-1, 0,  0, htd33},
++  {14, UINT_MAX, UINT_MAX, 0,  0, htd33},
+   {15,16-1,16-1, 0,511,htd15},
+   {16,16-1,16-1, 1,511,htd16},
+   {17,16-1,16-1, 2,511,htd16},
diff -Nru smpeg-0.4.5+cvs20030824/debian/patches/series smpeg-0.4.5+cvs20030824/debian/patches/series
--- smpeg-0.4.5+cvs20030824/debian/patches/series	2014-08-31 00:13:12.0 +0200
+++ smpeg-0.4.5+cvs20030824/debian/patches/series	2016-09-24 20:25:18.0 +0200
@@ -13,3 +13,4 @@
 310_deprecate_flags.diff
 320_gnu_stack.diff
 330_format_security.diff
+340_gcc6.diff


signature.asc
Description: PGP signature

Processed: smpeg: diff for NMU version 0.4.5+cvs20030824-7.2

[Debian Bug Tracking System]

Processing control commands:

> tags 811742 + patch
Bug #811742 [smpeg] smpeg: FTBFS with GCC 6: narrowing conversion
Added tag(s) patch.
> tags 811742 + pending
Bug #811742 [smpeg] smpeg: FTBFS with GCC 6: narrowing conversion
Added tag(s) pending.

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

Bug#811741: ragel: diff for NMU version 6.9-1.1

[Sebastian Ramacher]

Control: tags 811741 + patch
Control: tags 811741 + pending

Dear maintainer,

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

Regards.

-- 
Sebastian Ramacher
diff -u ragel-6.9/debian/changelog ragel-6.9/debian/changelog
--- ragel-6.9/debian/changelog
+++ ragel-6.9/debian/changelog
@@ -1,3 +1,11 @@
+ragel (6.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Explicitly set C++ standard to C++98 to fix compilation under GCC 6
+(Closes: #811741)
+
+ -- Andreas Stührk   Sat, 24 Sep 2016 20:28:04 +0200
+
 ragel (6.9-1) unstable; urgency=medium
 
   * New upstream release
diff -u ragel-6.9/debian/rules ragel-6.9/debian/rules
--- ragel-6.9/debian/rules
+++ ragel-6.9/debian/rules
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
 
 CFLAGS:=$(shell dpkg-buildflags --get CFLAGS)
+CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS) -std=gnu++98
 LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
 
 # for the m68k hack
@@ -9,7 +10,7 @@
 
 config.status: configure
 	dh_testdir
-	CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure --prefix=/usr --mandir=\$${prefix}/share/man 
+	CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)" CXXFLAGS="$(CXXFLAGS)" ./configure --prefix=/usr --mandir=\$${prefix}/share/man 
 
 build: build-arch build-indep
 build-arch: build-stamp


signature.asc
Description: PGP signature

Processed: ragel: diff for NMU version 6.9-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 811741 + patch
Bug #811741 [ragel] ragel: FTBFS with GCC 6: narrowing conversion
Added tag(s) patch.
> tags 811741 + pending
Bug #811741 [ragel] ragel: FTBFS with GCC 6: narrowing conversion
Added tag(s) pending.

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

Bug#811743: marked as done (sndobj: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 20:24:25 +0200
with message-id <20160924182425.hwtuyzglegq45...@ramacher.at>
and subject line Re: Bug#811743: sndobj: FTBFS with GCC 6: narrowing conversion
has caused the Debian Bug report #811743,
regarding sndobj: 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.)


-- 
811743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sndobj
Version: 2.6.6.1-5
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
...
> g++ -o src/PVBlur.os -c -O2 -fPIC -DALSA -DJACK -Iinclude -Iinclude/rfftw 
> src/PVBlur.cpp
> g++ -o src/PVRead.os -c -O2 -fPIC -DALSA -DJACK -Iinclude -Iinclude/rfftw 
> src/PVRead.cpp
> In file included from src/PVRead.h:29:0,
>  from src/PVRead.cpp:23:
> src/SndPVOCEX.h:74:1: error: narrowing conversion of '2199042498u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
>  };
>  ^
> 
> scons: *** [src/PVRead.os] Error 1
> scons: building terminated because of errors.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 2.6.6.1-5.1

On 2016-01-19 17:48:35, Martin Michlmayr wrote:
> Package: sndobj
> Version: 2.6.6.1-5
> 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
> ...
> > g++ -o src/PVBlur.os -c -O2 -fPIC -DALSA -DJACK -Iinclude -Iinclude/rfftw 
> > src/PVBlur.cpp
> > g++ -o src/PVRead.os -c -O2 -fPIC -DALSA -DJACK -Iinclude -Iinclude/rfftw 
> > src/PVRead.cpp
> > In file included from src/PVRead.h:29:0,
> >  from src/PVRead.cpp:23:
> > src/SndPVOCEX.h:74:1: error: narrowing conversion of '2199042498u' from 
> > 'unsigned int' to 'int' inside { } [-Wnarrowing]
> >  };
> >  ^
> > 
> > scons: *** [src/PVRead.os] Error 1
> > scons: building terminated because of errors.

sndobj (2.6.6.1-5.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Add patch from Philip Chung to fix compilation with GCC 6. (fixes #811743)

 -- Johannes Brandstätter   Sat, 24 Sep 2016 15:30:54 +0200

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#836927: assaultcube: diff for NMU version 1.1.0.4+dfsg2-1.2

[Sebastian Ramacher]

Control: tags 836927 + patch
Control: tags 836927 + pending

Dear maintainer,

I've prepared an NMU for assaultcube (versioned as 1.1.0.4+dfsg2-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -Nru assaultcube-1.1.0.4+dfsg2/debian/changelog assaultcube-1.1.0.4+dfsg2/debian/changelog
--- assaultcube-1.1.0.4+dfsg2/debian/changelog	2014-10-29 12:32:05.0 +0100
+++ assaultcube-1.1.0.4+dfsg2/debian/changelog	2016-09-24 19:42:32.0 +0200
@@ -1,3 +1,10 @@
+assaultcube (1.1.0.4+dfsg2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix building with GCC 6. (Closes: #836927)
+
+ -- Johannes Brandstätter   Sat, 24 Sep 2016 19:42:32 +0200
+
 assaultcube (1.1.0.4+dfsg2-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru assaultcube-1.1.0.4+dfsg2/debian/patches/gcc6.patch assaultcube-1.1.0.4+dfsg2/debian/patches/gcc6.patch
--- assaultcube-1.1.0.4+dfsg2/debian/patches/gcc6.patch	1970-01-01 01:00:00.0 +0100
+++ assaultcube-1.1.0.4+dfsg2/debian/patches/gcc6.patch	2016-09-24 19:40:05.0 +0200
@@ -0,0 +1,27 @@
+Description: Fix building with GCC 6.
+Author: Johannes Brandstätter 
+Bug-Debian: https://bugs.debian.org/836927
+Last-Update: <2016-09-24>
+
+--- assaultcube-1.1.0.4+dfsg2.orig/source/src/rendertext.cpp
 assaultcube-1.1.0.4+dfsg2/source/src/rendertext.cpp
+@@ -319,7 +319,7 @@ static void text_color(char c, char *sta
+ if(c=='r') c = stack[(sp > 0) ? --sp : sp]; // restore color
+ else if(c == 'b') stack[sp] *= -1;
+ else stack[sp] = c;
+-switch(abs(stack[sp]))
++switch(static_cast(abs(stack[sp])))
+ {
+ case '0': color = bvec( 2,  255,  128 ); break;   // green: player talk
+ case '1': color = bvec( 96,  160, 255 ); break;   // blue: team chat
+--- assaultcube-1.1.0.4+dfsg2.orig/source/src/tools.h
 assaultcube-1.1.0.4+dfsg2/source/src/tools.h
+@@ -55,8 +55,6 @@ static inline T min(T a, T b)
+ return a < b ? a : b;
+ }
+ 
+-static inline float round(float x) { return floor(x + 0.5f); }
+-
+ #define clamp(a,b,c) (max(b, min(a, c)))
+ #define rnd(max) (rand()%(max))
+ #define rnd_2x(max) (rand()%(max)+rand()%(max))
diff -Nru assaultcube-1.1.0.4+dfsg2/debian/patches/series assaultcube-1.1.0.4+dfsg2/debian/patches/series
--- assaultcube-1.1.0.4+dfsg2/debian/patches/series	2011-10-30 01:22:54.0 +0200
+++ assaultcube-1.1.0.4+dfsg2/debian/patches/series	2016-09-24 19:39:04.0 +0200
@@ -2,3 +2,4 @@
 20-fix-clean-target.patch
 30-build-with-debug-symbols.patch
 40-build-with-lX11.patch
+gcc6.patch


signature.asc
Description: PGP signature

Processed: assaultcube: diff for NMU version 1.1.0.4+dfsg2-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 836927 + patch
Bug #836927 [src:assaultcube] assaultcube: FTBFS with GCC 6: error: 'float 
round(float)' conflicts with a previous declaration
Added tag(s) patch.
> tags 836927 + pending
Bug #836927 [src:assaultcube] assaultcube: FTBFS with GCC 6: error: 'float 
round(float)' conflicts with a previous declaration
Added tag(s) pending.

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

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[JanKusanagi]

>From what I see, the real problem here is that plasma-discover's
"upgrade" functionality is acting like a "aptitude full-upgrade",
removing whatever's necessary, possible removing half your system,
instead of acting like a "aptitude safe-upgrade", which would hold the
problematic packages, and not remove anything.

Obviously, the second way would be much safer, and it would still result
in a proper upgrade on Debian Stable, or in the other suites as long as
there are no big migrations happening.


The thing is, a user upgrading with this program, might end up
destroying their system. I'd consider this 'grave'.

Also, the OP for this bug is not the first one to have this same
catastrophe happening. I remember someone on #debian-kde or
#debian-qt-kde with this same problem, and rightfully, hating
plasma-discover's guts.


Cheers!

-- 
Development blog: https://jancoding.wordpress.com

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Scott Kitterman]

On September 24, 2016 1:00:21 PM EDT, Matthias Klumpp  
wrote:
>2016-09-24 18:36 GMT+02:00 Ximo Baldó :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> No. Precisely, the bug I'm reporting is that  the package manager,
>plasma-discover, does not warn user about his intention to do that
>removing operation. So,  the user never has notice about these changes
>and as far I know this situation can be considered as grave bug as it
>can lead to an unusable system.
>
>Discover is meant for users who have no idea what a "package" is, so
>prompting them with questions they don't understand will highly likely
>not happen (they would just klick "yes" anyway). I wonder though if we
>could add some safeguard, like "ask for re-confirmation if more than
>50 packages are going to be removed".
>In any case, this is not a grave bug since it only ever happens on
>development suites, which no end-user sees. It's normal/important at
>max.

Developers are users too.  If your position is that Discover isn't suitable for 
use in testing/unstable then what that means is Discover gets released 
untested.  That's not a recipe for success.

If it breaks a system without warning, that's a grave bug.  Nothing about bug 
severities says that they only apply to stable.

What I think you want is for developers and advanced users to use Discover, at 
least occasionally, during development so we know it's well integrated with 
Debian prior to release.  That's not going to happen if it silently breaks 
systems.

Scott K

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

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 19:11:47 +0200
with message-id <20160924171147.nka4ah4wevwds...@ramacher.at>
and subject line Re: Bug#811645: FTBFS with GCC 6: cannot convert x to y
has caused the Debian Bug report #811645,
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.)


-- 
811645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ams
Version: 2.1.1-1
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++ -D_REENTRANT -DLADSPA_PATH=\"/usr/lib/ladspa:/usr/local/lib/ladspa\" 
> -DTRANSLATIONSDIR=\"/usr/share/ams/translations\" 
> -DDEMOFILEPATH=\"/usr/share/ams/demos\" 
> -DINSTRUMENTFILEPATH=\"/usr/share/ams/instruments\" -DHAVE_CONFIG_H -I.   
> -Wdate-time -D_FORTIFY_SOURCE=2 -DQT_SHARED -I/usr/include/qt4 
> -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4 -I/usr/include/qt4/QtGui 
> -I/usr/include/qt4 -I/usr/include/qt4/QtCore -Wall -m64 -msse -mfpmath=sse 
> -ffast-math -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -c -o ams-port.o `test -f 'port.cpp' || echo './'`port.cpp
> m_vocoder.cpp: In member function 'virtual void M_vocoder::generateCycle()':
> m_vocoder.cpp:293:52: error: incompatible types in assignment of 'float' to 
> 'fftw_complex {aka double [2]}'
>modinforward[l2] = modbuf[l1][l2] * window[l2];
> ^
> 
> m_vocoder.cpp:307:43: error: invalid array assignment
>modinbackward[l2] = modoutforward[l2];
>^
> 
> m_vocoder.cpp:316:60: error: cannot convert 'double*' to '__complex__ double' 
> for argument '1' to 'double creal(__complex__ double)'
>data[2][l1][l2] = logf(fabs (creal (modoutforward[l2])) + 1.0);
> ^
> 
> m_vocoder.cpp:330:27: error: incompatible types in assignment of 'int' to 
> 'fftw_complex {aka double [2]}'
>modinbackward[l2] = 0;
>^
> 
> m_vocoder.cpp:337:50: error: invalid array assignment
>modinbackward[ lclfrq ] = modoutforward [l2];
>   ^
> 
> m_vocoder.cpp:339:69: error: invalid array assignment
>modinbackward[fftsize - lclfrq] = modoutforward [ fftsize - l2];
>  ^
> 
> m_vocoder.cpp:345:43: error: invalid array assignment
>modoutforward[l2] = modinbackward[l2];
>^
> 
> m_vocoder.cpp:348:27: error: incompatible types in assignment of 'int' to 
> 'fftw_complex {aka double [2]}'
>modinbackward[l2] = 0;
>^
> 
> m_vocoder.cpp:362:55: error: invalid use of non-lvalue array
>  modinbackward[lclfrq] += modoutforward [l2];
>^
> 
> m_vocoder.cpp:362:55: error:   in evaluation of 'operator+=(fftw_complex {aka 
> double [2]}, fftw_complex {aka double [2]})'
> m_vocoder.cpp:363:76: error: invalid use of non-lvalue array
>  modinbackward[fftsize - lclfrq] += modoutforward [ fftsize - l2];
> ^
> 
> m_vocoder.cpp:363:76: error:   in evaluation of 'operator+=(fftw_complex {aka 
> double [2]}, fftw_complex {aka double [2]})'
> m_vocoder.cpp:371:30: error: cannot convert 'double*' to '__complex__ double' 
> for argument '1' to 'double cabs(__complex__ double)'
>   cabs (modoutforward [l2])
>   ^
> 
> m_vocoder.cpp:372:44: error: cannot convert 'double*' to '__complex__ double' 
> for argument '1' to 'double carg(__complex__ double)'
>   * cexp (I * ( carg (modoutforward [l2])
> ^
> 
> m_vocoder.cpp:375:41: error: cannot convert 'double*' to '__complex__ double' 
> for argument '1' to 'double cabs(__complex__ double)'
>   cabs (modoutforward [ fftsize - l2])
>  ^
> 
> m_vocoder.cpp:376:55: 

Processed: kyotocabinet: diff for NMU version 1.2.76-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 811627 + patch
Bug #811627 [kyotocabinet] FTBFS with GCC 6: cannot convert x to y
Added tag(s) patch.
> tags 811627 + pending
Bug #811627 [kyotocabinet] FTBFS with GCC 6: cannot convert x to y
Added tag(s) pending.

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

Bug#811627: kyotocabinet: diff for NMU version 1.2.76-4.2

[Sebastian Ramacher]

Control: tags 811627 + patch
Control: tags 811627 + pending

Dear maintainer,

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

Regards.
-- 
Sebastian Ramacher
diff -Nru kyotocabinet-1.2.76/debian/changelog kyotocabinet-1.2.76/debian/changelog
--- kyotocabinet-1.2.76/debian/changelog	2015-08-15 12:16:08.0 +0200
+++ kyotocabinet-1.2.76/debian/changelog	2016-09-24 17:59:10.0 +0200
@@ -1,3 +1,10 @@
+kyotocabinet (1.2.76-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix incompatibility with C++14/GCC 6 (Closes: #811627)
+
+ -- Andreas Stührk   Sat, 24 Sep 2016 17:58:05 +0200
+
 kyotocabinet (1.2.76-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru kyotocabinet-1.2.76/debian/patches/cpp-14.patch kyotocabinet-1.2.76/debian/patches/cpp-14.patch
--- kyotocabinet-1.2.76/debian/patches/cpp-14.patch	1970-01-01 01:00:00.0 +0100
+++ kyotocabinet-1.2.76/debian/patches/cpp-14.patch	2016-09-24 17:57:39.0 +0200
@@ -0,0 +1,16 @@
+Description: fix for c++14/GCC 6 compatibility
+Author: Andreas Stührk 
+Bug-Debian: https://bugs.debian.org/811627
+Last-Update: <2016-09-24>
+
+--- kyotocabinet-1.2.76.orig/kcdbext.h
 kyotocabinet-1.2.76/kcdbext.h
+@@ -1278,7 +1278,7 @@ class IndexDB {
+ if (omode_ == 0) {
+   set_error(_KCCODELINE_, BasicDB::Error::INVALID, "not opened");
+   *sp = 0;
+-  return false;
++  return nullptr;
+ }
+ if (!cache_) return db_.get(kbuf, ksiz, sp);
+ size_t dvsiz = 0;
diff -Nru kyotocabinet-1.2.76/debian/patches/series kyotocabinet-1.2.76/debian/patches/series
--- kyotocabinet-1.2.76/debian/patches/series	2012-07-13 14:07:13.0 +0200
+++ kyotocabinet-1.2.76/debian/patches/series	2016-09-24 17:55:25.0 +0200
@@ -6,3 +6,4 @@
 doc-kyotoproducts.pdf.patch
 kfreebsd-support-getsysinfo-on-GNU-kFreeBSD.patch
 gcc-4.7.patch
+cpp-14.patch


signature.asc
Description: PGP signature

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Matthias Klumpp]

2016-09-24 18:36 GMT+02:00 Ximo Baldó :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> No. Precisely, the bug I'm reporting is that  the package manager, 
> plasma-discover, does not warn user about his intention to do that removing 
> operation. So,  the user never has notice about these changes and as far I 
> know this situation can be considered as grave bug as it can lead to an 
> unusable system.

Discover is meant for users who have no idea what a "package" is, so
prompting them with questions they don't understand will highly likely
not happen (they would just klick "yes" anyway). I wonder though if we
could add some safeguard, like "ask for re-confirmation if more than
50 packages are going to be removed".
In any case, this is not a grave bug since it only ever happens on
development suites, which no end-user sees. It's normal/important at
max.

I'll ping the Discover upstream and maybe designers to see if
something can be done here.

Cheers,
Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/

Processed: Same issue upgrading from wheezy to jessie

[Debian Bug Tracking System]

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

> unarchive #683103
Bug #683103 {Done: Roger Leigh } [initscripts] mkdir: cannot 
create directory `/run/shm': File exists
Unarchived Bug 683103
> found #683103 sysvinit/2.88dsf-59
Bug #683103 {Done: Roger Leigh } [initscripts] mkdir: cannot 
create directory `/run/shm': File exists
Marked as found in versions sysvinit/2.88dsf-59 and reopened.
> thanks
Stopping processing here.

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

Bug#835583: marked as done (konversation: FTBFS: dh_install: Cannot find (any matches for) "usr/share/appdata/org.kde.konversation.appdata.xml" (tried in "." and "debian/tmp"))

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 16:44:03 +
with message-id 
and subject line Bug#835580: fixed in konversation 1.6.2-2
has caused the Debian Bug report #835580,
regarding konversation: FTBFS: dh_install: Cannot find (any matches for) 
"usr/share/appdata/org.kde.konversation.appdata.xml" (tried in "." and 
"debian/tmp")
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.)


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

konversation fails to build from source in unstable/amd64:

  [..]

  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  make[3]: Nothing to be done for 
'doc/sv/CMakeFiles/doc-sv-index-cache-bz2.dir/build'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  [ 21%] Built target doc-nl-index-cache-bz2
  [ 21%] Built target doc-sv-index-cache-bz2
  [ 22%] Built target doc-pt-BR-index-cache-bz2
  [ 23%] Built target doc-uk-index-cache-bz2
  [ 23%] Built target konversation_automoc
  make -f src/CMakeFiles/konversation.dir/build.make 
src/CMakeFiles/konversation.dir/depend
  [ 24%] Built target doc-it-index-cache-bz2
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2
 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/src
 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu/src
 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu/src/CMakeFiles/konversation.dir/DependInfo.cmake
 --color=
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  make -f src/CMakeFiles/konversation.dir/build.make 
src/CMakeFiles/konversation.dir/build
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  make[3]: Nothing to be done for 'src/CMakeFiles/konversation.dir/build'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  [100%] Built target konversation
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu/CMakeFiles
 0
  make -f CMakeFiles/Makefile2 preinstall
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  make[2]: Nothing to be done for 'preinstall'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/obj-x86_64-linux-gnu'
  Install the project...
  /usr/bin/cmake -P cmake_install.cmake
  -- Install configuration: "Debian"
  -- Installing: 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/debian/tmp/usr/share/locale/bg/LC_MESSAGES/konversation.mo
  -- Installing: 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/debian/tmp/usr/share/locale/bs/LC_MESSAGES/konversation.mo
  -- Installing: 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/debian/tmp/usr/share/locale/ca/LC_MESSAGES/konversation.mo
  -- Installing: 
/home/lamby/temp/cdt.20160827100020.XTN32semou.db.konversation/konversation-1.6.2/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/konversation.mo
  -- Installing: 

Bug#835580: marked as done (konversation: FTBFS in testing (org.kde.konversation.appdata.xml is not installed to anywhere))

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 16:44:03 +
with message-id 
and subject line Bug#835580: fixed in konversation 1.6.2-2
has caused the Debian Bug report #835580,
regarding konversation: FTBFS in testing (org.kde.konversation.appdata.xml is 
not installed to anywhere)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh  build-indep --with kf5 --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   dh_auto_configure --buildsystem=kf5 -i -O--parallel
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON
-- The C compiler identification is GNU 6.1.1
-- The CXX compiler identification is GNU 6.1.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/de/konversation/index.docbook
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/it/konversation/index.cache.bz2
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/it/konversation/index.docbook
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/nl/konversation/index.cache.bz2
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/nl/konversation/index.docbook
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/pt_BR/konversation/index.cache.bz2
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/pt_BR/konversation/index.docbook
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/index.cache.bz2
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/index.docbook
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/addchannel.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/addnetwork_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/addserver_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/channel_screen_tour_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/channellist_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/checkidentities.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/colorchooser_screen.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/dccstatus_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/first_channel_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/first_serverlist_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/highlighting_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/identities_adv_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/identities_away_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/identities_gen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/kimproxy_create_screen2.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/kimproxy_create_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/logviewer_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/nicksonline_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/nickthemes_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/notification_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/notifylist_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/osd_demo.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/osd_screen_co.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/quickbuttons_screen.png
-- Installing: 
/<>/debian/tmp/usr/share/doc/HTML/sv/konversation/quickconnect_screen.png
-- Installing: 

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Ximo Baldó]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

No. Precisely, the bug I'm reporting is that  the package manager, 
plasma-discover, does not warn user about his intention to do that removing 
operation. So,  the user never has notice about these changes and as far I know 
this situation can be considered as grave bug as it can lead to an unusable 
system.

On 24 de setembre de 2016 18:22:16 CEST, Chris Lamb  wrote:
>Ximo Baldó i Soriano wrote:
>
>> So... The ongoing Perl migration causes plasma-discover (or its
>backend) to
>> bypass user's decision to deinstall 347 packages from his system?
>
>There is no bypassing -- your package manager would have declared its
>intention to remove all those packages.
>
>
>Regards,
>
>--
>  ,''`.
> : :'  : Chris Lamb
> `. `'`  la...@debian.org / chris-lamb.co.uk
>   `-

- --
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-BEGIN PGP SIGNATURE-

iHQEAREKADQtHFhpbW8gQmFsZMOzIGkgU29yaWFubyA8ZXNwaW5kYXJnYUBnbWFp
bC5jb20+BQJX5quaAAoJEPLA9MdIi+gmFw0AoKDbA2+UIOSpIFEVbKlpl7xExwIU
AJ0QscmFLR8Bp/p8/uhyRkc2SKOrNA==
=xm9L
-END PGP SIGNATURE-

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Chris Lamb]

Ximo Baldó i Soriano wrote:

> So... The ongoing Perl migration causes plasma-discover (or its backend) to 
> bypass user's decision to deinstall 347 packages from his system?

There is no bypassing -- your package manager would have declared its
intention to remove all those packages.


Regards,

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

Bug#835354: libitext-java: uninstallable, makes other packages FTBFS

[Tobias Frost]

libitext-java-gcj needs to be removed so that -11 will show up in the
archives.

RM bug is already triggered (and set to block this bug)

Bug#837267: cfingerd: FTBFS: install: cannot stat 'src/cfingerd': No such file or directory

[Chris Lamb]

tags 837267 + pending patch
thanks

cfingerd 1.4.3-3.2 uploaded to DELAYED/5. Corresponding debdiff
attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -u cfingerd-1.4.3/debian/changelog cfingerd-1.4.3/debian/changelog
--- cfingerd-1.4.3/debian/changelog
+++ cfingerd-1.4.3/debian/changelog
@@ -1,3 +1,10 @@
+cfingerd (1.4.3-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due to lack of "." in Perl's @INC. (Closes: #837267)
+
+ -- Chris Lamb   Sat, 24 Sep 2016 17:37:58 +0200
+
 cfingerd (1.4.3-3.1) unstable; urgency=high
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- cfingerd-1.4.3.orig/Configure
+++ cfingerd-1.4.3/Configure
@@ -17,10 +17,10 @@
 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 # GNU General Public License for more details.
 
-require 'perl/question.pl';
-require 'perl/filemagic.pl';
-require 'perl/gethost.pl';
-require 'perl/generic.pl';
+require './perl/question.pl';
+require './perl/filemagic.pl';
+require './perl/gethost.pl';
+require './perl/generic.pl';
 
 $VERSION = "1.4.2";
 $| = 1;

Processed: Re: cfingerd: FTBFS: install: cannot stat 'src/cfingerd': No such file or directory

[Debian Bug Tracking System]

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

> tags 837267 + pending patch
Bug #837267 [src:cfingerd] cfingerd: FTBFS: install: cannot stat 
'src/cfingerd': No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: RM: libitext-java-gcj -- NBS; no longer built

[Debian Bug Tracking System]

Processing control commands:

> block 835354 by -1
Bug #835354 [src:libitext-java] libitext-java: uninstallable, makes other 
packages FTBFS
835354 was not blocked by any bugs.
835354 was blocking: 835729
Added blocking bug(s) of 835354: 838770

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

Bug#819790: marked as done (sooperlooper: FTBFS: error: no match for call to '(std::_Bind<sigc::bound_mem_functor3<void, SooperLooper::MidiBridge, int, int, SooperLooper::Engine*>(SooperLooper::Engine

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 17:54:00 +0200
with message-id <20160924155400.ybt4d2elmhnch...@ramacher.at>
and subject line Re: Bug#819790: sooperlooper: FTBFS: error: no match for call 
to '(std::_Bind(SooperLooper::Engine*)>)
has caused the Debian Bug report #819790,
regarding sooperlooper: FTBFS: error: no match for call to 
'(std::_Bind(SooperLooper::Engine*)>)
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.)


-- 
819790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sooperlooper
Version: 1.7.3~dfsg0-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,

sooperlooper fails to build from source in unstable/amd64:

  [..]

  /usr/include/sigc++-2.0/sigc++/functors/slot.h:724:98:   required from 
'sigc::slot2::slot2(const T_functor&) [with T_functor 
= std::_Bind(SooperLooper::Engine*)>; T_return = void; T_arg1 = int; 
T_arg2 = int]'
  /usr/include/sigc++-2.0/sigc++/functors/slot.h:1801:26:   required from 
'sigc::slot::slot(const T_functor&) [with T_functor = 
std::_Bind(SooperLooper::Engine*)>; T_return = void; T_arg1 = int; 
T_arg2 = int]'
  engine.cpp:316:91:   required from here
  /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:108:39: error: no 
match for call to '(std::_Bind(SooperLooper::Engine*)>) (const int&, const int&)'
   { return functor_(_A_arg1, _A_arg2); }
 ^
  In file included from /usr/include/sigc++-2.0/sigc++/reference_wrapper.h:22:0,
   from 
/usr/include/sigc++-2.0/sigc++/adaptors/bound_argument.h:24,
   from /usr/include/sigc++-2.0/sigc++/adaptors/bind.h:6,
   from /usr/include/sigc++-2.0/sigc++/adaptors/adaptors.h:23,
   from /usr/include/sigc++-2.0/sigc++/sigc++.h:107,
   from engine.hpp:26,
   from engine.cpp:37:
  /usr/include/c++/5/functional:1129:2: note: candidate: template _Result std::_Bind<_Functor(_Bound_args 
...)>::operator()(_Args&& ...) [with _Args = {_Args ...}; _Result = _Result; 
_Functor = sigc::bound_mem_functor3; _Bound_args = {SooperLooper::Engine*}]
operator()(_Args&&... __args)
^
  /usr/include/c++/5/functional:1129:2: note:   template argument 
deduction/substitution failed:
  /usr/include/c++/5/functional:1125:39: error: no match for call to 
'(sigc::bound_mem_functor3) (SooperLooper::Engine*&)'
= decltype( std::declval<_Functor&>()(
 ^
  In file included from 
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:9:0,
   from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
   from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
   from /usr/include/sigc++-2.0/sigc++/signal.h:8,
   from /usr/include/sigc++-2.0/sigc++/sigc++.h:104,
   from engine.hpp:26,
   from engine.cpp:37:
  /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:2219:12: note: candidate: 
T_return sigc::bound_mem_functor3::operator()(sigc::type_trait_take_t, 
sigc::type_trait_take_t, sigc::type_trait_take_t) const [with 
T_return = void; T_obj = SooperLooper::MidiBridge; T_arg1 = int; T_arg2 = int; 
T_arg3 = SooperLooper::Engine*; sigc::type_trait_take_t = const int&; 
sigc::type_trait_take_t = const int&; sigc::type_trait_take_t = 
SooperLooper::Engine* const&]
 T_return operator()(type_trait_take_t _A_a1, 
type_trait_take_t _A_a2, type_trait_take_t _A_a3) const
  ^
  /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:2219:12: note:   candidate 
expects 3 arguments, 1 provided
  In file included from 

Bug#811883: marked as done (calf: FTBFS with GCC 6: no matching function for call to)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 17:52:22 +0200
with message-id <20160924155222.xamfyny2eniiu...@ramacher.at>
and subject line Re: Bug#811883: calf: FTBFS with GCC 6: no matching function 
for call to
has caused the Debian Bug report #811883,
regarding calf: FTBFS with GCC 6: no matching function for call to
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.)


-- 
811883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: calf
Version: 0.0.60-1
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.. -I. -Wdate-time -D_FORTIFY_SOURCE=2 
> -ffast-math -finline-limit=80   -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/gdk-pixbuf-2.0 -I/usr/include/libpng12 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12   -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -O3 
> -finline-functions -finline-functions-called-once -Wall -c -o jack_client.o 
> jack_client.cpp
> jack_client.cpp: In member function 'void 
> calf_plugins::jack_client::calculate_plugin_order(std::vector&)':
> jack_client.cpp:229:71: error: no matching function for call to 
> 'make_pair(const int&, unsigned int&)'
>  run_before.insert(make_pair(p->second, i));
>^
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
>  from /usr/include/c++/6/bits/stl_tree.h:63,
>  from /usr/include/c++/6/map:60,
>  from ./calf/primitives.h:30,
>  from ./calf/giface.h:25,
>  from jack_client.cpp:25:
> /usr/include/c++/6/bits/stl_pair.h:406:5: note: candidate: template _T1, class _T2> constexpr std::pair std::__decay_and_strip<_Tp>::__type, typename 
> std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _T2&&)
>  make_pair(_T1&& __x, _T2&& __y)
>  ^
> 
> /usr/include/c++/6/bits/stl_pair.h:406:5: note:   template argument 
> deduction/substitution failed:
> jack_client.cpp:229:62: note:   cannot convert 
> 'p.std::_Rb_tree_const_iterator<_Tp>::operator-> >()->std::pair std::__cxx11::basic_string, int>::second' (type 'const int') to type 
> 'int&&'
>  run_before.insert(make_pair(p->second, i));
>~~~^~
> 
> Makefile:709: recipe for target 'jack_client.o' failed
> make[4]: *** [jack_client.o] Error 1
> make[4]: Leaving directory '/<>/src'
> Makefile:738: recipe for target 'all-recursive' failed

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

On 2016-01-19 18:55:09, Martin Michlmayr wrote:
> Package: calf
> Version: 0.0.60-1
> 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.. -I. -Wdate-time -D_FORTIFY_SOURCE=2 
> > -ffast-math -finline-limit=80   

Processed: your mail

[Debian Bug Tracking System]

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

> tag 831916 + pending
Bug #831916 [src:winpdb] winpdb: FTBFS with dpkg-buildpackage -A: winpdb.1: No 
such file or directory at /usr/bin/dh_installman line 131.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831185: marked as done (rumor: FTBFS with GCC 6: notator.cc:337:43: error: call of overloaded 'abs(unsigned int)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2016 17:43:12 +0200
with message-id <20160924154312.6qen2t7z5uuee...@ramacher.at>
and subject line Re: Bug#831185: rumor: FTBFS with GCC 6: notator.cc:337:43: 
error: call of overloaded 'abs(unsigned int)' is ambiguous
has caused the Debian Bug report #831185,
regarding rumor: FTBFS with GCC 6: notator.cc:337:43: error: call of overloaded 
'abs(unsigned int)' 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.)


-- 
831185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rumor
Version: 1.0.5-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. 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. -I..   -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -D_REENTRANT -pthread -I/usr/include/guile/2.0 -ggdb3 
> -O0 -Wall -pedantic -c -o notator.o notator.cc
> notator.cc: In member function 'std::__cxx11::string Notator::PitchName(int, 
> bool)':
> notator.cc:337:43: error: call of overloaded 'abs(unsigned int)' is ambiguous
>NumTics=(abs(RefPitch_wt-AbsPitch_wt)+3)/7;
>^
> 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/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/ostream:38,
>  from /usr/include/c++/6/iostream:39,
>  from rumor.hh:14,
>  from notator.cc:8:
> /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/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/ostream:38,
>  from /usr/include/c++/6/iostream:39,
>  from rumor.hh:14,
>  from notator.cc:8:
> /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]: *** [notator.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/rumor_1.0.5-2_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 ---
Version: 1.0.5-2.1

On 2016-07-14 09:25:29, Lucas Nussbaum wrote:
> Source: rumor
> Version: 1.0.5-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. For more information about GCC 6 and Stretch, see:
> - https://wiki.debian.org/GCC6
> -