Bug#750134: marked as done (portaudio: FTBFS - No rule to make target 'lib/')

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 07:15:17 +
with message-id 
and subject line Bug#756322: Removed package(s) from unstable
has caused the Debian Bug report #750134,
regarding portaudio: FTBFS - No rule to make target 'lib/'
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.)


-- 
750134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: portaudio
Version: 18.1-7.1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
Finished configure.

Type 'make' to build PortAudio and examples.
dh_testdir
/usr/bin/make lib/libportaudio.la
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-portaudio/portaudio-18.1'
make[1]: *** No rule to make target 'lib/', needed by 'lib/libportaudio.la'.  
Stop.
make[1]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-portaudio/portaudio-18.1'
debian/rules:51: recipe for target 'build-stamp' failed

Looking at Makefile.in, there is a rule to make lib, but not lib/ - apparently
make no longer unifies these.

The full build log is attached.

Best,
Michael



portaudio-build-log.txt.gz
Description: application/gunzip


pgpuIIYlATfP7.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 18.1-7.1+rm

Dear submitter,

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

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

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

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

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

Bug#797743: gromacs: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: gromacs
Version: 5.0.6-1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of gromacs, std::string appears in installed headers,
so it seems very likely that a transition is needed.

The transition normally consists of renaming the affected library packages,
adding a v5 suffix (.4v5, etc.). The SONAME should not be changed.
However, gromacs already does not package its shared library according to
Policy §8.1, so it will likely also need a versioned Breaks on
versions of votca-csg that do not depend on a separated shared library.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of gromacs:

* boost started its transition with 1.58
* everything else looks like a C ABI

so I think this is ready to go.

The package is likely to be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#797738: gdcm: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: gdcm
Version: 2.4.4-4
Severity: serious
Justification: breaks ABI without a package rename
Control: block -1 by 797673
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of gdcm, std::string appears in symbols that
are explicitly imported, so it seems very likely that a transition is needed.
The transition consists of renaming the affected library packages, adding a
v5 suffix (libgdcm2.4v5, etc.). The SONAME should not be changed.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

In the case of gdcm:

* poppler and vtk have started their transitions
* socket++ does not appear to need a transition
* the other library dependencies appear to be C APIs

so I think this is ready to go.

The package is likely to be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Processed: gdcm: ABI transition needed for libstdc++ v5

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 797673
Bug #797738 [src:gdcm] gdcm: ABI transition needed for libstdc++ v5
797738 was not blocked by any bugs.
797738 was not blocking any bugs.
Added blocking bug(s) of 797738: 797673

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

Bug#797416: marked as done (cqrlog FTBFS in unstable lazbuild hangs)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 09:13:10 +0100
with message-id <55e6af96.6050...@tuckley.org>
and subject line cqrlog FTBFS in unstable lazbuild hangs
has caused the Debian Bug report #797416,
regarding cqrlog FTBFS in unstable lazbuild hangs
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.)


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

package: cqrlog
version: 1.9.0-3
severity: serious
tags: patch sid

As you are probablly already aware lazbuild is currently broken on arm 
in sid (see bug 793991) and it looks like it may be some time before 
it's fixed. In the meantime  there are some cqrlog rc bugs that need 
fixing in testing.


So as a short to medium term fix for cqrlog here is a patch to build it 
without using lazbuild. Colin, can you test that the results of building 
with this patch work and if-so upload it to sid.



diff -Nru cqrlog-1.9.0/debian/changelog cqrlog-1.9.0/debian/changelog
--- cqrlog-1.9.0/debian/changelog   2015-08-24 15:38:07.0 +
+++ cqrlog-1.9.0/debian/changelog   2015-08-30 12:37:53.0 +
@@ -1,3 +1,10 @@
+cqrlog (1.9.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Avoid using lazbuild for now as it's broken on arm* in sid.
+
+ -- Peter Michael Green   Sun, 30 Aug 2015 12:37:31 +
+
 cqrlog (1.9.0-3) unstable; urgency=medium
 
   * Fix build dependency on fp-units-gtk -> fp-units-gtk2
diff -Nru cqrlog-1.9.0/debian/patches/makefile-no-lazbuild 
cqrlog-1.9.0/debian/patches/makefile-no-lazbuild
--- cqrlog-1.9.0/debian/patches/makefile-no-lazbuild1970-01-01 
00:00:00.0 +
+++ cqrlog-1.9.0/debian/patches/makefile-no-lazbuild2015-08-30 
13:56:31.0 +
@@ -0,0 +1,20 @@
+Description:  Avoid using lazbuild for now as it's broken on arm* in sid.
+Author: Peter Michael Green 
+
+Index: cqrlog-1.9.0/Makefile
+===
+--- cqrlog-1.9.0.orig/Makefile
 cqrlog-1.9.0/Makefile
+@@ -4,9 +4,11 @@ datadir  = $(DESTDIR)/usr/share/cqrlog
+ bindir   = $(DESTDIR)/usr/bin
+ sharedir = $(DESTDIR)/usr/share
+ tmpdir   = /tmp
++fpcarch := $(shell fpc -iTP)-$(shell fpc -iTO)
+ 
+ cqrlog: src/cqrlog.lpi
+-  $(CC) --ws=gtk2 --pcp=$(tmpdir)/.lazarus src/cqrlog.lpi
++  #$(CC) --ws=gtk2 --pcp=$(tmpdir)/.lazarus src/cqrlog.lpi
++  cd src && fpc -B -MObjFPC -Sghi -O3 -g -gl -l -vn- -vh- -vewilbq 
-Fl/usr/lib/lazarus/default/lcl -Fl/opt/gnome/lib -Fu$(CURDIR)/src/lnet/lib 
-Fu$(CURDIR)/src/mysql 
-Fu/usr/lib/lazarus/default/components/turbopower_ipro/units/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/tachart/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/sqldb/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/rtticontrols/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/memds/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/tdbf/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/printers/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/ideintf/units/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/synedit/units/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/sdf/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/lazcontrols/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/components/cairocanvas/lib/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/lcl/units/$(fpcarch)/gtk2 
-Fu/usr/lib/lazarus/default/lcl/units/$(fpcarch) 
-Fu/usr/lib/lazarus/default/components/codetools/units/$(fpcarch) 
-Fu/usr/lib/lazarus/default/components/lazutils/lib/$(fpcarch) 
-Fu/usr/lib/lazarus/default/packager/units/$(fpcarch) -Fu$(CURDIR)/src/ -dLCL 
-dLCLgtk2 -dNO_CONTEST cqrlog.lpr
+   $(ST) src/cqrlog
+   gzip tools/cqrlog.1 -c > tools/cqrlog.1.gz
+ 
diff -Nru cqrlog-1.9.0/debian/patches/series cqrlog-1.9.0/debian/patches/series
--- cqrlog-1.9.0/debian/patches/series  2015-07-28 19:18:07.0 +
+++ cqrlog-1.9.0/debian/patches/series  2015-08-30 12:39:32.0 +
@@ -1,3 +1,4 @@
 makefile-no-homedir-use
 desktop-keywords
 apparmor.patch
+makefile-no-lazbuild
--- End Message ---
--- Begin Message ---
The builds on arm* are now working.

Closing this bug so that it does not stop the package from migrating to
testing.

-- 
Colin Tuckley  |  +44(0)1223 830814  |  PGP/GnuPG Key Id
Debian Developer   |  +44(0)7799 143369  | 0x38C9D903--- End Message ---

Processed: tagging 795520

[Debian Bug Tracking System]

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

> tags 795520 + help
Bug #795520 [src:golang-uuid] golang-uuid: FTBFS: uuid_test.go:315: 
NodeInterface "" after SetInteface
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#791243: poco: library transition may be needed when GCC 5 is the default

[Simon McVittie]

On Tue, 04 Aug 2015 at 20:51:27 +0100, Jonathan Wiltshire wrote:
> This appears to be the case and we need an upload as soon as possible.
> Please upload directly to unstable.

I have uploaded a NMU to DELAYED/2 with the attached patch. Please tell me
if I should cancel or reschedule it, although given that "as soon as
possible" has taken almost a month, this seems unlikely.

S
diffstat for poco-1.3.6p1 poco-1.3.6p1

 changelog|   13 +++
 control  |  134 +--
 libpococrypto9-dbg.install   |1 
 libpococrypto9.install   |1 
 libpococrypto9v5-dbg.install |1 
 libpococrypto9v5.install |1 
 libpocodata9-dbg.install |1 
 libpocodata9.install |1 
 libpocodata9v5-dbg.install   |1 
 libpocodata9v5.install   |1 
 libpocofoundation9-dbg.install   |1 
 libpocofoundation9.install   |1 
 libpocofoundation9v5-dbg.install |1 
 libpocofoundation9v5.install |1 
 libpocomysql9-dbg.install|1 
 libpocomysql9.install|1 
 libpocomysql9v5-dbg.install  |1 
 libpocomysql9v5.install  |1 
 libpoconet9-dbg.install  |1 
 libpoconet9.install  |1 
 libpoconet9v5-dbg.install|1 
 libpoconet9v5.install|1 
 libpoconetssl9-dbg.install   |1 
 libpoconetssl9.install   |1 
 libpoconetssl9v5-dbg.install |1 
 libpoconetssl9v5.install |1 
 libpocoodbc9-dbg.install |1 
 libpocoodbc9.install |1 
 libpocoodbc9v5-dbg.install   |1 
 libpocoodbc9v5.install   |1 
 libpocosqlite9-dbg.install   |1 
 libpocosqlite9.install   |1 
 libpocosqlite9v5-dbg.install |1 
 libpocosqlite9v5.install |1 
 libpocoutil9-dbg.install |1 
 libpocoutil9.install |1 
 libpocoutil9v5-dbg.install   |1 
 libpocoutil9v5.install   |1 
 libpocoxml9-dbg.install  |1 
 libpocoxml9.install  |1 
 libpocoxml9v5-dbg.install|1 
 libpocoxml9v5.install|1 
 libpocozip9-dbg.install  |1 
 libpocozip9.install  |1 
 libpocozip9v5-dbg.install|1 
 libpocozip9v5.install|1 
 46 files changed, 124 insertions(+), 67 deletions(-)

diff -Nru poco-1.3.6p1/debian/changelog poco-1.3.6p1/debian/changelog
--- poco-1.3.6p1/debian/changelog	2014-11-23 11:57:01.0 +
+++ poco-1.3.6p1/debian/changelog	2015-09-02 08:29:12.0 +0100
@@ -1,3 +1,16 @@
+poco (1.3.6p1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Steve Langasek ]
+  * Rename library packages for g++5 ABI transition. (Closes: #791243)
+
+  [ Simon McVittie ]
+  * Revert addition of Lintian overrides for the v5 suffix, which are
+not needed with current Lintian
+
+ -- Simon McVittie   Wed, 02 Sep 2015 07:49:04 +0100
+
 poco (1.3.6p1-5) unstable; urgency=medium
 
   * Adds debian/patches/70_fix_CVE-2014-0350.dpatch (Closes: #746637).
diff -Nru poco-1.3.6p1/debian/control poco-1.3.6p1/debian/control
--- poco-1.3.6p1/debian/control	2014-11-23 11:57:01.0 +
+++ poco-1.3.6p1/debian/control	2015-09-02 08:29:12.0 +0100
@@ -12,8 +12,8 @@
 Package: libpoco-dev
 Section: libdevel
 Architecture: any
-Depends: libpococrypto9 (= ${binary:Version}), libpocodata9 (= ${binary:Version}), libpocofoundation9 (= ${binary:Version}), libpocomysql9 (= ${binary:Version}), libpoconet9 (= ${binary:Version}), libpoconetssl9 (= ${binary:Version}), libpocoodbc9 (= ${binary:Version}), libpocosqlite9 (= ${binary:Version}), libpocoutil9 (= ${binary:Version}), libpocoxml9 (= ${binary:Version}), libpocozip9 (= ${binary:Version})
-Suggests: libpoco-doc, libpococrypto9-dbg (= ${binary:Version}), libpocodata9-dbg (= ${binary:Version}), libpocofoundation9-dbg (= ${binary:Version}), libpocomysql9-dbg (= ${binary:Version}), libpoconet9-dbg (= ${binary:Version}), libpoconetssl9-dbg (= ${binary:Version}), libpocoodbc9-dbg (= ${binary:Version}), libpocosqlite9-dbg (= ${binary:Version}), libpocoutil9-dbg (= ${binary:Version}), libpocoxml9-dbg (= ${binary:Version}), libpocozip9-dbg (= ${binary:Version})
+Depends: libpococrypto9v5 (= ${binary:Version}), libpocodata9v5 (= ${binary:Version}), libpocofoundation9v5 (= ${binary:Version}), libpocomysql9v5 (= ${binary:Version}), libpoconet9v5 (= ${binary:Version}), libpoconetssl9v5 (= ${binary:Version}), libpocoodbc9v5 (= ${binary:Version}), libpocosqlite9v5 (= ${binary:Version}), libpocoutil9v5 (= ${binary:Version}), libpocoxml9v5 (= ${binary:Version}), libpocozip9v5 (= ${binary:Version})
+Suggests: libpoco-doc, libpococrypto9v5-dbg (= ${binary:Version}), libpocodata9v5-dbg (= ${binary:Version}), libpocofoundation9v5-dbg (= ${binary:Version}), libpocomysql9v5-dbg (= ${binary:Version}), 

Bug#797740: apt-show-source: Previous NMU FTBFS and binaries lost

[Scott Kitterman]

Package: apt-show-source
Version: 0.10+nmu1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

The last NMU FTBFS due to the way it was uploaded and then because of the way
the cruft report works, the old binaries were removed.  I'm going to do a no
change upload go resolve the FTBFS and get binaries back for this package.

NMU diff attached.
diff -Nru apt-show-source-0.10+nmu1/debian/changelog apt-show-source-0.10+nmu2/debian/changelog
--- apt-show-source-0.10+nmu1/debian/changelog	2015-08-20 16:16:45.0 -0400
+++ apt-show-source-0.10+nmu2/debian/changelog	2015-09-02 03:19:52.0 -0400
@@ -1,3 +1,10 @@
+apt-show-source (0.10+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild to fix FTBFS and restore lost binaries
+
+ -- Scott Kitterman   Wed, 02 Sep 2015 03:19:02 -0400
+
 apt-show-source (0.10+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.

Bug#797741: cgi-extratags-perl: Last NMU FTBFS and old binaries inadvertently removed

[Scott Kitterman]

Source: cgi-extratags-perl
Version: 0.03-1.1
Severity: serious
Tags: patch
Justification: fails to build from source

The last NMU FTBFS due to the way it was uploaded and then because of the way
the cruft report works, the old binaries were removed.  I'm going to do a no
change upload go resolve the FTBFS and get binaries back for this package.

NMU diff attached.
diff -u cgi-extratags-perl-0.03/debian/changelog cgi-extratags-perl-0.03/debian/changelog
--- cgi-extratags-perl-0.03/debian/changelog
+++ cgi-extratags-perl-0.03/debian/changelog
@@ -1,3 +1,10 @@
+cgi-extratags-perl (0.03-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild to fix FTBFS and restore lost binaries
+
+ -- Scott Kitterman   Wed, 02 Sep 2015 03:22:29 -0400
+
 cgi-extratags-perl (0.03-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.

Processed (with 2 errors): Re: Bug#797293: [Debichem-devel] Bug#797293: votca-csg: FTBFS: undefined reference to `votca::tools::RangeParser::Parse

[Debian Bug Tracking System]

Processing control commands:

> reassign 797293 votca-tools
Bug #797293 [src:votca-csg] votca-csg: FTBFS: undefined reference to 
`votca::tools::RangeParser::Parse
Bug reassigned from package 'src:votca-csg' to 'votca-tools'.
No longer marked as found in versions votca-csg/1.2.4-1.
Ignoring request to alter fixed versions of bug #797293 to the same values 
previously set
> found 797293 1.2.4-1
Bug #797293 [votca-tools] votca-csg: FTBFS: undefined reference to 
`votca::tools::RangeParser::Parse
There is no source info for the package 'votca-tools' at version '1.2.4-1' with 
architecture ''
Unable to make a source version for version '1.2.4-1'
Marked as found in versions 1.2.4-1.
> tag 797293 + sid stretch confirmed
Bug #797293 [votca-tools] votca-csg: FTBFS: undefined reference to 
`votca::tools::RangeParser::Parse
Added tag(s) confirmed, sid, and stretch.
> affects 797293 votca-csg
Bug #797293 [votca-tools] votca-csg: FTBFS: undefined reference to 
`votca::tools::RangeParser::Parse
Added indication that 797293 affects votca-csg
> retitle 797293 votca-tools: rename needed for libstdc++ ABI transition
Bug #797293 [votca-tools] votca-csg: FTBFS: undefined reference to 
`votca::tools::RangeParser::Parse
Changed Bug title to 'votca-tools: rename needed for libstdc++ ABI transition' 
from 'votca-csg: FTBFS: undefined reference to 
`votca::tools::RangeParser::Parse'
> user debian-...@lists.debian.org
Unknown command or malformed arguments to command.

> usertags 797293 + libstdc++-cxx11
Unknown command or malformed arguments to command.


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

Bug#795910: marked as done (python3-yaql: yaql not working: ImportError: No module named 'context')

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 09:52:39 +0200
with message-id <55e6aac7.2050...@debian.org>
and subject line Bug addressed and done
has caused the Debian Bug report #795910,
regarding python3-yaql: yaql not working: ImportError: No module named 'context'
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.)


-- 
795910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-yaql
Version: 0.2.3-2
Severity: grave
Tags: patch
Justification: renders package unusable

yaql (python 3 package) fails to launch or import because uses python 2 syntax.

2to3 seams to fix the issue.


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

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

Versions of packages python3-yaql depends on:
ii  dpkg 1.18.2
ii  python3-ply  3.4-5
ii  python3.43.4.3-7
pn  python3:any  

python3-yaql recommends no packages.

python3-yaql suggests no packages.
--- yaql/__init__.py	(original)
+++ yaql/__init__.py	(refactored)
@@ -12,8 +12,8 @@
 #License for the specific language governing permissions and limitations
 #under the License.
 
-import parser
-import context
+from . import parser
+from . import context
 from yaql.functions import builtin, extended
 
 __versioninfo__ = (0, 2, 3)
--- yaql/context.py	(original)
+++ yaql/context.py	(refactored)
@@ -14,7 +14,7 @@
 
 from functools import wraps
 import inspect
-from exceptions import NoArgumentFound
+from .exceptions import NoArgumentFound
 
 
 class Context():
--- yaql/exceptions.py	(original)
+++ yaql/exceptions.py	(refactored)
@@ -20,9 +20,9 @@
 
 class NoFunctionRegisteredException(YaqlException):
 def __init__(self, func_name, arg_num=None):
-self.func_name = func_name
+self.__name__ = func_name
 self.arg_num = arg_num
-msg = "No function called '{0}' is registered".format(self.func_name)
+msg = "No function called '{0}' is registered".format(self.__name__)
 if self.arg_num:
 msg += " which has {0} arguments".format(self.arg_num)
 super(NoFunctionRegisteredException, self).__init__(msg)
--- yaql/expressions.py	(original)
+++ yaql/expressions.py	(refactored)
@@ -13,8 +13,8 @@
 #under the License.
 
 import types
-from context import *
-from exceptions import YaqlExecutionException, NoFunctionRegisteredException
+from .context import *
+from .exceptions import YaqlExecutionException, NoFunctionRegisteredException
 import yaql
 
 
@@ -87,7 +87,7 @@
 fs = self._try_invoke(
 resolvers,
 [self.function_name, this], context) or []
-if not isinstance(fs, types.ListType):
+if not isinstance(fs, list):
 fs = [fs]
 except YaqlExecutionException:
 fs = []
@@ -223,7 +223,7 @@
 ok = True
 if arg_type:
 ok = ok and isinstance(arg_val, arg_type)
-if type(arg_val) == types.BooleanType:
+if type(arg_val) == bool:
 ok = ok and type(arg_val) == arg_type
 if custom_validator:
 ok = ok and custom_validator(arg_val)
--- yaql/parser.py	(original)
+++ yaql/parser.py	(refactored)
@@ -14,9 +14,9 @@
 
 import types
 import ply.yacc as yacc
-import expressions
-import exceptions
-import lexer
+from . import expressions
+from . import exceptions
+from . import lexer
 import tempfile
 
 
@@ -96,7 +96,7 @@
 """
 func : value '.' FUNC arg ')'
 """
-if isinstance(p[4], types.ListType):
+if isinstance(p[4], list):
 arg = p[4]
 else:
 arg = [p[4]]
@@ -114,7 +114,7 @@
 """
 func : FUNC arg ')'
 """
-if isinstance(p[2], types.ListType):
+if isinstance(p[2], list):
 arg = p[2]
 else:
 arg = [p[2]]
@@ -126,11 +126,11 @@
 arg : arg ',' arg
 """
 val_list = []
-if isinstance(p[1], types.ListType):
+if isinstance(p[1], list):
 val_list += p[1]
 else:
 val_list.append(p[1])
-if isinstance(p[3], types.ListType):
+if 

Bug#797744: gromacs: shared library in a package that is not renamed with its SONAME

[Simon McVittie]

Source: gromacs
Version: 5.0.6-1
Severity: serious
Justification: Policy 8.1

The gromacs binary package contains a public shared library
(libgromacs.so.0), and votca-csg depends on it.

Policy §8.1 says:

> The run-time shared library must be placed in a package whose name
> changes whenever the SONAME of the shared library changes.

In this case, the shared library package should be libgromacs0,
and gromacs should depend on it.

Not doing this makes SONAME transitions, C++ ABI transitions, etc.
more painful for no good reason.

S

Bug#797293: [Debichem-devel] Bug#797293: votca-csg: FTBFS: undefined reference to `votca::tools::RangeParser::Parse

[Simon McVittie]

Control: reassign 797293 votca-tools
Control: found 797293 1.2.4-1
Control: tag 797293 + sid stretch confirmed
Control: affects 797293 votca-csg
Control: retitle 797293 votca-tools: rename needed for libstdc++ ABI transition
Control: user debian-...@lists.debian.org
Control: usertags 797293 + libstdc++-cxx11

On Sat, 29 Aug 2015 at 08:48:21 -0600, Christoph Junghans wrote:
> 2015-08-29 3:45 GMT-06:00 Dominic Hargreaves :
> > CMakeFiles/csg_dump.dir/csg_dump.cc.o:(.data.rel.ro._ZTV10CsgDumpApp[_ZTV10CsgDu
> > mpApp]+0x28): undefined reference to 
> > `votca::tools::Application::VersionString[a
> > bi:cxx11]()'
>
> This is simple. votca-tools, the prime dependency of votca-csg, was
> compiled with a compiler with a different cxx11 abi, you will need to
> re-compile votca-tools with same compiler.

This implies that votca-tools needs an ABI transition.

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of votca-tools, Dominic's bug report indicates that a transition
is definitely required. The transition consists of renaming the affected
library packages, adding a v5 suffix (libgdcm2.4v5, etc.). The SONAME
should not be changed.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

In the case of votca-tools:

* boost has already started its transition
* the other library build-deps appear to have C ABIs

so I think this is ready to go.

The package is likely to be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#797227: segfault - gst_memory_unmap, libgstreamer

[Changwoo Ryu]

Yes, I just have tested the patch on faad plugin at the GNOME bugzilla
748571. And it fixes the problem.

Processed: Re: Bug#797120: redshift-plasmoid: Not usable anymore in Plasma5

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #797120 [redshift-plasmoid] redshift-plasmoid: Not usable anymore in Plasma5
Added tag(s) patch.

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

Bug#791264: qwtplot3d: library transition may be needed when GCC 5 is the default

[Gudjon I. Gudjonsson]

Hi Simon

Thanks for the clarifications.
> Gudjon, is there any possibility of a more minimal maintainer-upload
> which does this library transition, and nothing else intrusive, leaving
> the other changes (e.g. adding the Qt 5 library) until after the
> huge and painful distro-wide libstdc++ transition is over?

I have removed  the qt5 library but I find the other changes like hardening 
flags and symbols files quite important.
The dsc file can be found here, please take a look.
http://mentors.debian.net/debian/pool/main/q/qwtplot3d/qwtplot3d_0.2.7+svn191-8.dsc

Regards
Gudjon

Bug#797729: information

[Henri Salo]

I'm not sure why you are offensive or why your attitude is like that.
Communication is important key to get changes to Debian. I am replying to this
bug item so that you receive more information about Debian security related
aspects. Please note that if you want some changes to Debian you need to create
bug item per issue or work with the team or package maintainer to get patches
applied. Offensive bug reports like this one does not probably get you to your
goal.

Please see for details:

- Team website: https://www.debian.org/security/
- Wiki page: https://wiki.debian.org/Teams/Security
- Meetings: https://wiki.debian.org/DebianSecurity/Meetings (latest meeting is 
not
yet listed in here, which was held in DebConf)
- IRC-channel: irc://irc.debian.org/debian-security
- FAQ: https://www.debian.org/security/faq
- List of security features:
https://wiki.debian.org/Security/Features (not complete)
- Embedded code copies: https://wiki.debian.org/EmbeddedCodeCopies

Most of the actual security tracking work is done in Debian security-tracker.
Please see:

https://security-tracker.debian.org/tracker/
http://security-team.debian.org/security_tracker.html
http://lists.alioth.debian.org/pipermail/secure-testing-team/

Could you submit a bug to issue tracker about one issue at the time without
aggressive tone?

-- 
Henri Salo

Processed: tagging 797729

[Debian Bug Tracking System]

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

> tags 797729 + moreinfo
Bug #797729 [debian-maintainers] debian-maintainers: security not taken 
seriously
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#791140: marked as done (libmsn: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Wed, 2 Sep 2015 07:21:20 +0100
with message-id <20150902062120.ga12...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#791140: closed by Pau Garcia i Quiles 
 ()
has caused the Debian Bug report #791140,
regarding libmsn: library transition may be needed when GCC 5 is the default
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.)


-- 
791140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmsn
Version: 4.2-2
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Version: 4.2.1+dfsg-1

On Tue, 01 Sep 2015 at 17:17:06 +0200, Pau Garcia i Quiles wrote:
> On Tue, Sep 1, 2015 at 10:50 AM, Simon McVittie  wrote:
> > > The changes look good, and I'm preparing a sponsored upload.

This has reached unstable, closing the bug again.

> > >* Standards 3.9.6.1 (no changes required)
> >
> > This is unnecessary, although harmless, and is not usually done. Only
> > the first three components of the Policy version are relevant for Policy
> > compliance; the fourth, if present, indicates technical changes which do
> > not affect what Policy says you should do.
> >
> I was moving from 3.9.3 to 3.9.6(.1)

Ah, now I understand. You'd normally say 3.9.6 in this situation, because
compliance with Policy 3.9.6 requires exactly the same (lack of) action
as compliance with 3.9.6.x for any x.

S--- End Message ---

Bug#778114: marked as done (screader: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 07:16:34 +
with message-id 
and subject line Bug#797682: Removed package(s) from unstable
has caused the Debian Bug report #778114,
regarding screader: ftbfs with GCC-5
to be marked as done.

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

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


-- 
778114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:screader
Version: 1.8-7
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/screader_1.8-7_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
process.c:26:1: note: in expansion of macro 'RCS_ID'
 RCS_ID("$Id: process.c,v 1.27 1994/05/31 12:32:39 mlschroe Exp $ FAU")
 ^
gcc -c -I.-O2 -D__SCREADER -Wall display.c
In file included from display.c:24:0:
rcs.h:38:36: warning: 'rcs_id' defined but not used [-Wunused-function]
 #   define RCS_ID(id) static char *rcs_id() { return rcs_id(id); }
^
display.c:25:1: note: in expansion of macro 'RCS_ID'
 RCS_ID("$Id: display.c,v 1.16 1994/05/31 12:31:50 mlschroe Exp $ FAU")
 ^
gcc -c -I.-O2 -D__SCREADER -Wall comm.c
In file included from comm.c:24:0:
rcs.h:38:36: warning: 'rcs_id' defined but not used [-Wunused-function]
 #   define RCS_ID(id) static char *rcs_id() { return rcs_id(id); }
^
comm.c:25:1: note: in expansion of macro 'RCS_ID'
 RCS_ID("$Id: comm.c,v 1.10 1993/11/30 19:28:07 mlschroe Exp $ FAU")
 ^
gcc -c -I.-O2 -D__SCREADER -Wall kmapdef.c
gcc -c -I.-O2 -D__SCREADER -Wall acls.c
In file included from acls.c:23:0:
rcs.h:38:36: warning: 'rcs_id' defined but not used [-Wunused-function]
 #   define RCS_ID(id) static char *rcs_id() { return rcs_id(id); }
^
acls.c:24:1: note: in expansion of macro 'RCS_ID'
 RCS_ID("$Id: acls.c,v 1.12 1994/05/31 12:31:21 mlschroe Exp $ FAU")
 ^
gcc -c -I.-O2 -D__SCREADER -Wall scr.c
scr.c: In function 'getscr':
scr.c:91:39: warning: operation on 'j' may be undefined [-Wsequence-point]
   for (j = 1; j < width; linebuf[j++] = linebuf[j * X]);
   ^
gcc -c -I.-O2 -D__SCREADER -Wall tts.c
In file included from tts.c:13:0:
tts.h:31:1: warning: useless type name in empty declaration
 typedef scrstat;
 ^
gcc -s -o screader screader.o ansi.o fileio.o mark.o misc.o resize.o socket.o 
search.o tty.o term.o window.o utmp.o loadav.o putenv.o help.o termcap.o 
input.o attacher.o pty.o process.o display.o comm.o kmapdef.o acls.o scr.o 
tts.o -ltermcap -lcrypt
socket.o: In function `SendCreateMsg':
socket.c:(.text+0xe41): warning: the `getwd' function is dangerous and should 
not be used.
screader.o: In function `main':
screader.c:(.text.startup+0x22b8): undefined reference to `Auto_TTS'
collect2: error: ld returned 1 exit status
make[1]: *** [screader] Error 1
Makefile:65: recipe for target 'screader' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-stamp] Error 2
debian/rules:27: recipe for target 'build-stamp' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 1.8-7+rm

Dear submitter,

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

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

The version of this package 

Bug#737557: marked as done (screader: uses legacy BSD pseudoterminals)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 07:16:34 +
with message-id 
and subject line Bug#797682: Removed package(s) from unstable
has caused the Debian Bug report #737557,
regarding screader: uses legacy BSD pseudoterminals
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.)


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

Package: screader
Version: 1.8-7
Severity: grave

screader fails to start with error message "No more PTYs." and later 
"Sorry, could not find a PTY." To see why it is happening, I ran it 
under strace, which revealed that it tries to open legacy BSD 
pseudoterminals devices:


4392  open("/dev/ptyq0", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or 
directory)
4392  open("/dev/ptyq1", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or 
directory)
4392  open("/dev/ptyq2", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or 
directory)
4392  open("/dev/ptyq3", O_RDWR|O_NOCTTY) = -1 ENOENT (No such file or 
directory)
[... and so on ...]

Debian Linux kernels stopped supporting BSD pseudoterminals in 2007.


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

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages screader depends on:
ii  libc6  2.18-0experimental1
ii  libtinfo5  5.9+20140118-1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Version: 1.8-7+rm

Dear submitter,

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

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

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

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

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

Bug#795327: marked as done (knemo: FTBFS: error: 'IFF_POINTOPOINT' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 07:17:50 +
with message-id 
and subject line Bug#797716: Removed package(s) from unstable
has caused the Debian Bug report #795327,
regarding knemo: FTBFS: error: 'IFF_POINTOPOINT' was not declared in this scope
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.)


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

/knemo-0.7.6/src/knemod/backends/netlinkbackend.cpp: In member function ‘void 
NetlinkBackend::updateIfaceData(const QString&, BackendData*)’:
/knemo-0.7.6/src/knemod/backends/netlinkbackend.cpp:205:22: error: 
‘IFF_POINTOPOINT’ was not declared in this scope
 if ( flags & IFF_POINTOPOINT )
  ^
/knemo-0.7.6/src/knemod/backends/netlinkbackend.cpp:230:22: error: ‘IFF_UP’ was 
not declared in this scope
 if ( flags & IFF_UP )
  ^
/knemo-0.7.6/src/knemod/backends/netlinkbackend.cpp:235:32: error: 
‘IFF_POINTOPOINT’ was not declared in this scope
 if ( !(flags & IFF_POINTOPOINT) || data->addrData.size() )
^
src/knemod/CMakeFiles/knemo.dir/build.make:578: recipe for target 
'src/knemod/CMakeFiles/knemo.dir/backends/netlinkbackend.o' failed
make[3]: *** [src/knemod/CMakeFiles/knemo.dir/backends/netlinkbackend.o] Error 1

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.7.6-2+rm

Dear submitter,

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

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

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

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

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

Bug#763210: marked as done (libfile-spec-perl: uninstallable, current version superseded by perl 5.20.1)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 07:15:59 +
with message-id 
and subject line Bug#797619: Removed package(s) from unstable
has caused the Debian Bug report #763210,
regarding libfile-spec-perl: uninstallable, current version superseded by perl 
5.20.1
to be marked as done.

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

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


-- 
763210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfile-spec-perl
Version: 3.4700-1 
Severity: grave

This package is uninstallable because perl 5.20.1 bundles a newer version
of it and therefore breaks older separately packaged versions.

 Breaks: libfile-spec-perl (<< 3.4800)
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Version: 3.4700-1+rm

Dear submitter,

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

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

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

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

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

Bug#793260: [Pkg-ime-devel] Bug#793260: Bug#793260: marisa: change of type in system_error might break with GCC-5

[Guo Yixuan]

On Sep 2, 2015 12:52, "Mitsuya Shibata"  wrote:
>
> Control: owner !
>
> sorry for very late reply.
> I will tackle the bug in this weekend.

Thank you! If no renaming is needed, then you only need to bump the package
version, rebuild and upload.

Actually, after rebuilding with 5.2, there's only one symbol with cxx11 ABI
substring:
   U typeinfo for std::ios_base::failure[abi:cxx11]

Cheers,
Yixuan

Bug#797800: lvm2 configure.in, librt.so vs librt.pc

[Andreas Henriksson]

Hello Alasdair G Kergon.

I'm mailing you because of an issue I've run into which I think comes
from your commit:
https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=3cd644aeb5cac432a92ad50584973a3430168ed6

On Debian there's librt.so but no librt.pc.

Could you please add a PKG_CHECK_MODULES call in configure.in
to check if RT_PC should be set to "librt" or ""?

(Fwiw, I've file http://bugs.debian.org/797800 to track this and
another small issue on the Debian side.)

Regards,
Andreas Henriksson

Bug#797669: marked as done (rolldice: Rolldice does not roll any dice now)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 11:19:55 -0400
with message-id <55e7139b.4070...@gmail.com>
and subject line Rolldice does not roll any dice now
has caused the Debian Bug report #797669,
regarding rolldice: Rolldice does not roll any dice now
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.)


-- 
797669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rolldice
Version: 1.14-1
Severity: important

Dear Maintainer,

Rolldice runs now silently.
I suspect a library issue.
Here is the full strace report:

 Start 

execve("/usr/games/rolldice", ["rolldice", "1d4"], [/* 60 vars */]) = 0
brk(0)  = 0x8321000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7718000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=436334, ...}) = 0
mmap2(NULL, 436334, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb76ad000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libm.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0F\0\0004\0\0\0"..., 
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=280108, ...}) = 0
mmap2(NULL, 282784, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb7667000
mmap2(0xb76ab000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0xb76ab000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/libreadline.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\\322\0\0004\0\0\0"..., 512) 
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=280196, ...}) = 0
mmap2(NULL, 284172, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb7621000
mmap2(0xb7661000, 20480, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4) = 0xb7661000
mmap2(0xb7666000, 1548, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7666000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, 
"\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\233\1\0004\0\0\0"..., 512) 
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1738492, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb762
mmap2(NULL, 1743484, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb7476000
mmap2(0xb761a000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a4000) = 0xb761a000
mmap2(0xb761d000, 10876, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb761d000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/libtinfo.so.5", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@b\0\0004\0\0\0"..., 
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=141636, ...}) = 0
mmap2(NULL, 145548, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0xb7452000
mprotect(0xb7472000, 4096, PROT_NONE)   = 0
mmap2(0xb7473000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2) = 0xb7473000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7451000
set_thread_area({entry_number:-1, base_addr:0xb7451700, limit:1048575, 
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, 
useable:1}) = 0 (entry_number:6)
mprotect(0xb761a000, 8192, PROT_READ)   = 0
mprotect(0xb7473000, 8192, PROT_READ)   = 0
mprotect(0xb7661000, 4096, PROT_READ)   = 0
mprotect(0xb76ab000, 4096, PROT_READ)   = 0
mprotect(0x804a000, 4096, PROT_READ)= 0
mprotect(0xb773c000, 4096, PROT_READ)   = 0
munmap(0xb76ad000, 436334)  = 0
brk(0)  = 0x8321000
brk(0x8342000)  = 0x8342000
open("/dev/urandom", O_RDONLY)  = 3
exit_group(65)  = ?
+++ exited with 65 +++

 End 

-- System Information:
Debian Release: stretch/sid
  APT 

Bug#797804: pgadmin3 segfaults after rightclick

[Marc Neininger]

Package: pgadmin3
Version: 1.20.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

I tried to manage a local postgres installation but when trying to add a new
server pgadmin3 closes after segfaulting.
Message: $> Debug: Adding duplicate image handler for 'PNG file'

I found nearly the same bug description last year but it seems that the bug
returned.

I use a fully upgraded debian testing environment but when the bug appeared I
even upgraded pgadmin3 to experimental. This didn't help either.



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

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

Versions of packages pgadmin3 depends on:
ii  libc6   2.19-19
ii  libgcc1 1:5.1.1-14
ii  libpq5  9.4.4-1
ii  libssl1.0.0 1.0.2d-1
ii  libstdc++6  5.1.1-14
ii  libwxbase3.0-0  3.0.2+dfsg-1
ii  libwxgtk3.0-0   3.0.2+dfsg-1
ii  libxml2 2.9.1+dfsg1-5
ii  libxslt1.1  1.1.28-2+b2
ii  pgadmin3-data   1.20.0-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages pgadmin3 recommends:
ii  pgagent3.4.0-3
ii  postgresql-client-9.4 [postgresql-client]  9.4.4-1

Versions of packages pgadmin3 suggests:
pn  postgresql-contrib  

-- no debconf information

Bug#797793: htseq: FTBFS on 32bit archs (test failure)

[Julien Cristau]

Source: htseq
Version: 0.6.1p1-1
Severity: serious
Justification: fails to build from source

See logs at
https://buildd.debian.org/status/logs.php?pkg=htseq=0.6.1p1-1=sid

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#793260: [Pkg-ime-devel] Bug#793260: Bug#793260: marisa: change of type in system_error might break with GCC-5

[Mitsuya Shibata]

Control: owner !

sorry for very late reply.
I will tackle the bug in this weekend.

Bug#784933: marked as done (svgtune: FTBFS due to help2man error)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 15:26:41 +
with message-id 
and subject line Bug#784933: fixed in svgtune 0.2.0-2
has caused the Debian Bug report #784933,
regarding svgtune: FTBFS due to help2man error
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.)


-- 
784933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: svgtune
Version: 0.2.0-1
Severity: serious
Tags: patch
Justification: fails to build from source
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

svgtune currently FTBFS in Ubuntu [1] due to a help2man error (same thing
occurs in an amd64 Debian unstable pbuilder). This happens because help2man
tries to run svgtune --help, but svgtune requires python-lxml to run, which is
not present in the build dependencies for the package.

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on python-lxml to allow help2man to run svgtune.

Thanks for considering the patch.

Logan Rosen

[1] 
https://launchpadlibrarian.net/205809137/buildlog_ubuntu-wily-amd64.svgtune_0.2.0-1_BUILDING.txt.gz

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-16-generic (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)
diff -u svgtune-0.2.0/debian/control svgtune-0.2.0/debian/control
--- svgtune-0.2.0/debian/control
+++ svgtune-0.2.0/debian/control
@@ -2,7 +2,7 @@
 Section: graphics
 Priority: optional
 Maintainer: Yaroslav Halchenko 
-Build-Depends: cdbs, debhelper (>= 7), help2man, python
+Build-Depends: cdbs, debhelper (>= 7), help2man, python, python-lxml
 Standards-Version: 3.9.6
 Homepage: http://github.com/yarikoptic/svgtune
 Vcs-Git: git://github.com/yarikoptic/svgtune.git -b debian
--- End Message ---
--- Begin Message ---
Source: svgtune
Source-Version: 0.2.0-2

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated svgtune 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, 24 Jun 2015 00:09:25 -0400
Source: svgtune
Binary: svgtune
Architecture: source all
Version: 0.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Yaroslav Halchenko 
Description:
 svgtune- tool to generate a set of .svg files out of a single .svg file
Closes: 784933
Changes:
 svgtune (0.2.0-2) unstable; urgency=medium
 .
   * debian/control
 - added python-lxml to Build-Depends to make help2man run happy
   (Closes: #784933). Thanks Logan Rosen for the report
Checksums-Sha1:
 15dfe354aeef6d9c0e0bd2734a45f702c34aac72 1812 svgtune_0.2.0-2.dsc
 d6b51112c010ce44b688c678dd60082dd9de8cb2 1830 svgtune_0.2.0-2.diff.gz
 b84ca4742bfc289592a47fe6f44702d2631b4702 7130 svgtune_0.2.0-2_all.deb
Checksums-Sha256:
 f8faa3781fdb32d55a465bf54659fb41bb6021520dcd0ae543bfc9bad862a9a3 1812 
svgtune_0.2.0-2.dsc
 3550d51b369675d4bf9f6fb07c6ebfc9fbe49b75033689fb72a66f23ec387137 1830 
svgtune_0.2.0-2.diff.gz
 3cca6e0a24104d2f99f7914142e137c65b0aebfdfb92514c257e72c76f241cfd 7130 
svgtune_0.2.0-2_all.deb
Files:
 4e727e7de1be5a56c778a4209f06e943 1812 graphics optional svgtune_0.2.0-2.dsc
 e45b5c2ca48d2d0db8f933add2b6cae6 1830 graphics optional svgtune_0.2.0-2.diff.gz
 9ddb2e00af2f6c12dffb35c29573ef7d 7130 graphics optional svgtune_0.2.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV5w39AAoJEKLeI1Bi2jP6wwwP/0keSszGkFhSdqDxJLDj6ZeZ
troL1HiuNHCl7LD6fsJYylCP90DfvkXVwwZlZvbzm4FTkBq25F1BregqMcoByF8N

Processed: Downgrade severity

[Debian Bug Tracking System]

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

> severity 791449 normal
Bug #791449 [fpm2] fpm2: crashes with an invalid fpm.ini
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#796751: marked as done (ldc: FTBFS on armhf: gen/asm-x86.h:225:5: error: narrowing conversion of '-1' from 'int' to 'char' inside { })

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 15:22:29 +
with message-id 
and subject line Bug#796751: fixed in ldc 1:0.14.0.dfsg-1.1
has caused the Debian Bug report #796751,
regarding ldc: FTBFS on armhf: gen/asm-x86.h:225:5: error: narrowing conversion 
of '-1' from 'int' to 'char' inside { }
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.)


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

ldc was binNMU'd for the libstdc++ transition (specifically, "Rebuild
with libconfig++9v5".

The log:


You'll see there are lots of instances of:

In file included from /«PKGBUILDDIR»/gen/asmstmt.cpp:142:0:
/«PKGBUILDDIR»/gen/asm-x86.h:225:5: error: narrowing conversion of '-1' from 
'int' to 'char' inside { } [-Wnarrowing]

I'm a little confused as to why a file named asm-x86.h would be included
on the only non-x86 architecture supported by ldc, so perhaps that's the
bug here; or perhaps there's some good reason for it, and something
else is broken.

S
--- End Message ---
--- Begin Message ---
Source: ldc
Source-Version: 1:0.14.0.dfsg-1.1

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated ldc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 31 Aug 2015 13:46:20 +0100
Source: ldc
Binary: ldc libphobos2-ldc-dev libphobos2-ldc65 libphobos2-ldc-debug65
Architecture: source amd64
Version: 1:0.14.0.dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Konstantinos Margaritis 
Changed-By: Neil Williams 
Description:
 ldc- LLVM D Compiler
 libphobos2-ldc-debug65 - LLVM D Compiler - Phobos2 Standard Library, debug libs
 libphobos2-ldc-dev - LLVM D Compiler - Phobos2 Standard library, imports
 libphobos2-ldc65 - LLVM D Compiler - Phobos2 Standard library, shared objects
Closes: 796751
Changes:
 ldc (1:0.14.0.dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop armhf as the package attempts to use x86 assembly.
 (Closes: #796751)
Checksums-Sha1:
 f06be6d0a2a05ee25e160a02eb9c49ba5a91a9d6 2270 ldc_0.14.0.dfsg-1.1.dsc
 b41feeb97d296da2cff245743c89ea718e3cd0a8 9536 ldc_0.14.0.dfsg-1.1.debian.tar.xz
 a1b020dd464fe4c5b764c451ec09414b839eef86 7744626 ldc_0.14.0.dfsg-1.1_amd64.deb
 43d69c7eb80e1ae43410edf30f8a0218eb5f5f24 2489954 
libphobos2-ldc-debug65_0.14.0.dfsg-1.1_amd64.deb
 dab842df78d6612eb7538d59ca6813fcef888577 2896210 
libphobos2-ldc-dev_0.14.0.dfsg-1.1_amd64.deb
 059e2f221c584266f7bad33050c2c2a1a0cf56f0 873594 
libphobos2-ldc65_0.14.0.dfsg-1.1_amd64.deb
Checksums-Sha256:
 2730e3df1019afc7195c2963de003124822e3dfecb2a105ec3c8c31f7785d142 2270 
ldc_0.14.0.dfsg-1.1.dsc
 34effb0424bdc3f27ebc872985421d6459c6a642354e6ba5d287733b4f0ab763 9536 
ldc_0.14.0.dfsg-1.1.debian.tar.xz
 bfa7b88c99784312858e40dae95dcee43ce0726b9a8aa1f6541e657569cb976b 7744626 
ldc_0.14.0.dfsg-1.1_amd64.deb
 e015720e69f81e8233c63d680762d4b4406ee6c1d8272ca62de7ad490ffd0242 2489954 
libphobos2-ldc-debug65_0.14.0.dfsg-1.1_amd64.deb
 4f80d4f564eacf1c0e70a1fed71019e6926c76cf8cb81d3e37549efdc546b746 2896210 
libphobos2-ldc-dev_0.14.0.dfsg-1.1_amd64.deb
 a9731eae84abcf7a4f142ea9d6c44fd5dcceac4288ded9e3dac8d15da82e74e3 873594 
libphobos2-ldc65_0.14.0.dfsg-1.1_amd64.deb
Files:
 68b1cf02bc15546fbbbca4ff1c0100d8 2270 devel extra ldc_0.14.0.dfsg-1.1.dsc
 9f39119aad11daa9d776d0ede5c25d5d 9536 devel extra 
ldc_0.14.0.dfsg-1.1.debian.tar.xz
 01d120060619ba4467c4f30a9d011968 7744626 devel extra 
ldc_0.14.0.dfsg-1.1_amd64.deb
 f9f6ea8542a571615cbcaa3aa8b0 2489954 libdevel extra 
libphobos2-ldc-debug65_0.14.0.dfsg-1.1_amd64.deb
 1c8c89ea7c67ccf2b694bf58f4483ec5 2896210 

Bug#794259: marked as done (FTBFS: "JWT secure comparison returns true if strings are equal" fails)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 15:55:20 +
with message-id 
and subject line Bug#794259: fixed in ruby-jwt 1.0.0-3
has caused the Debian Bug report #794259,
regarding FTBFS: "JWT secure comparison returns true if strings are equal" fails
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.)


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

Dear Maintainer,

The package fails to build:
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
...FFF..

Failures:

  1) JWT secure comparison returns true if strings are equal
 Failure/Error: expect(JWT.secure_compare("Foo", "Foo")).to be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/jwt_spec.rb:127:in `block (3 levels) in '

  2) JWT secure comparison returns false if either input is nil or empty
 Failure/Error: expect(JWT.secure_compare(bad, "Foo")).to be_false
   expected false to respond to `false?` or perhaps you meant `be false` or 
`be_falsey`
 # ./spec/jwt_spec.rb:132:in `block (4 levels) in '
 # ./spec/jwt_spec.rb:131:in `each'
 # ./spec/jwt_spec.rb:131:in `block (3 levels) in '

  3) JWT secure comparison retuns false if the strings are different
 Failure/Error: expect(JWT.secure_compare("Foo", "Bar")).to be_false
   expected false to respond to `false?` or perhaps you meant `be false` or 
`be_falsey`
 # ./spec/jwt_spec.rb:138:in `block (3 levels) in '

Finished in 0.34342 seconds (files took 1.12 seconds to load)
23 examples, 3 failures

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-jwt
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated ruby-jwt 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, 02 Sep 2015 18:18:57 +0530
Source: ruby-jwt
Binary: ruby-jwt
Architecture: source all
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balasankar C 
Description:
 ruby-jwt   - JSON Web Token implementation in Ruby
Closes: 794259
Changes:
 ruby-jwt (1.0.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Port tests to RSpec3 (Closes: #794259)
Checksums-Sha1:
 74da660353afae1b3ab163268b9e464b65c525d4 2048 ruby-jwt_1.0.0-3.dsc
 007808bf38a6c4f086aa6367da56252699ac3b1d 2920 ruby-jwt_1.0.0-3.debian.tar.xz
 822dc940ccb71df6b6b190362272a1f2b2477db8 4818 ruby-jwt_1.0.0-3_all.deb
Checksums-Sha256:
 9cbc21278542c627899c1d3357568668d4b842df3d17f6af633292f22d9ab26f 2048 
ruby-jwt_1.0.0-3.dsc
 c28e163f280c4abb17cf67c5918966022b93185e392e7b4143b52b7dac3a6545 2920 
ruby-jwt_1.0.0-3.debian.tar.xz
 53c660d2dc211146bb3e3f2f0f755c24741cc1eaf9f6c099241b293ba8bb9ce8 4818 
ruby-jwt_1.0.0-3_all.deb
Files:
 55b15738a158eb92835fc92ee2ad90b3 2048 ruby optional ruby-jwt_1.0.0-3.dsc
 304b67e0c306c6a59ab9da5b4159b894 2920 ruby optional 
ruby-jwt_1.0.0-3.debian.tar.xz
 4dcccf3ec9e987ac5217517174788762 4818 ruby optional ruby-jwt_1.0.0-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV5xV5AAoJEM4fnGdFEsIqJqEP/i9lVF5Qh9O4d1jlBtZJaUEh

Bug#797800: libdevmapper-dev: Missing dependencies / brokenness in devmapper.pc

[Andreas Henriksson]

Package: libdevmapper-dev
Version: 2.02.127-1
Severity: serious

Dear Maintainer,

There are a couple of problems with the dependencies of libdevmapper-dev
and/or the included devmapper.pc file.

The /usr/lib/x86_64-linux-gnu/pkgconfig/devmapper.pc file
states:
Requires.private:  libudev librt

This means packages build against/using devmapper.pc
will fail to configure. As an example it might look like this:

configure:6523: checking for LVM_DEPS
configure:6533: $PKG_CONFIG --exists --print-errors "polkit-gobject-1 >= 0.92
 $POLKIT_REQUIREMENT
 lvm2app
 gudev-1.0 >= 164"
Package librt was not found in the pkg-config search path.
Perhaps you should add the directory containing `librt.pc'
to the PKG_CONFIG_PATH environment variable
Package 'librt', required by 'devmapper', not found
configure:6539: $? = 1
configure:6559: $PKG_CONFIG --exists --print-errors "polkit-gobject-1 >= 0.92
 $POLKIT_REQUIREMENT
 lvm2app
 gudev-1.0 >= 164"
Package librt was not found in the pkg-config search path.
Perhaps you should add the directory containing `librt.pc'
to the PKG_CONFIG_PATH environment variable
Package 'librt', required by 'devmapper', not found
configure:6565: $? = 1
configure:6582: result: no



The solution is to include a dependency on the package shipping
the relevant .pc files, eg libudev.pc and librt.pc.

The first one is easily fixed since libudev.pc file is included in
libudev-dev. Just make libdevmapper-dev depend on libudev-dev.

The librt.pc file does not seem to be shipped by any package in Debian.
Likely the generation of devmapper.pc was not right, since the
the Requires.prive line seems to be generated according to:
http://sources.debian.net/src/lvm2/2.02.127-1/libdm/libdevmapper.pc.in/#L11

My suspicion is that @RT_PC@ should have ended up empty on Debian.

The configure.in script seems to be flawed by assuming that if there's
a librt.so, then there's also a librt.pc
cf. AC_CHECK_LIB vs PKG_CHECK_MODULES.

As an alternative you might want to convince the glibc maintainers
to ship the/a librt.pc file.


Regards,
Andreas Henriksson

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

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

Processed: your mail

[Debian Bug Tracking System]

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

> owner 793260 !
Bug #793260 [src:marisa] marisa: change of type in system_error might break 
with GCC-5
Owner recorded as Mitsuya Shibata .
>
End of message, stopping processing here.

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

Processed: Rolldice does not roll any dice now

[Debian Bug Tracking System]

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

> fixed 797669 1.14-2
Bug #797669 [rolldice] rolldice: Rolldice does not roll any dice now
There is no source info for the package 'rolldice' at version '1.14-2' with 
architecture ''
Unable to make a source version for version '1.14-2'
Marked as fixed in versions 1.14-2.
> --
Stopping processing here.

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

Bug#797743: [Debichem-devel] Bug#797743: gromacs: ABI transition needed for libstdc++ v5

[Nicholas Breen]

On Wed, Sep 02, 2015 at 09:09:25AM +0100, Simon McVittie wrote:
> Source: gromacs
> Version: 5.0.6-1
> Severity: serious
> Justification: breaks ABI without a package rename
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: libstdc++-cxx11
> 
> Background[1]: libstdc++6 introduces a new ABI to conform to the
> C++11 standard, but keeps the old ABI to not break existing binaries.
> Packages which are built with g++-5 from experimental (not the one
> from testing/unstable) are using the new ABI.  Libraries built from
> this source package export some of the new __cxx11 or B5cxx11 symbols,
> dropping other symbols.  If these symbols are part of the API of
> the library, then this rebuild with g++-5 will trigger a transition
> for the library.
> 
> In the case of gromacs, std::string appears in installed headers,
> so it seems very likely that a transition is needed.

Isn't this just #791061 again?  To the best of my knowledge, nothing external
uses those.



-- 
Nicholas Breen
nbr...@debian.org

Bug#797284: pytango ftbfs in unstable

[PICCA Frederic-Emmanuel]

ok, I just uploaded a tango package which fix the FTBFS with gcc5.
I also made a libstdc++6 transition for tango.

so now I think that after tango acceptation into unstable a simple binNMU 
should fix this issue.

Processed: no patch yet

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #797809 [src:gazebo] gazebo ftbfs with SDF 3.0
Removed tag(s) patch.

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

Bug#797809: no patch yet

[Matthias Klose]

Control: tags -1 - patch

sorry, no patch yet.

there are multiple issues involved:

 - building with SD 3.0
 - building with -std=c++11
 - building with boost 1.58

Bug#797854: libsixel: Missing Build-Depends on python

[Chris Lamb]

Source: libsixel
Version: 1.5.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
Tags: patch

Dear Maintainer,

libsixel fails to build from source in unstable/amd64 due
to missing Build-Depends on python:

  [..]

  configure:15220: checking for a Python interpreter with version >= 2.3
  configure:15237: python -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python: command not found
  configure:15240: $? = 127
  configure:15237: python2 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python2: command not found
  configure:15240: $? = 127
  configure:15237: python3 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python3: command not found
  configure:15240: $? = 127
  configure:15237: python3.3 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python3.3: command not found
  configure:15240: $? = 127
  configure:15237: python3.2 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python3.2: command not found
  configure:15240: $? = 127
  configure:15237: python3.1 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python3.1: command not found
  configure:15240: $? = 127
  configure:15237: python3.0 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python3.0: command not found
  configure:15240: $? = 127
  configure:15237: python2.7 -c import sys # split strings by '.' and
  convert to numeric. Append some zeros # because we need at least 4
  digits for the hex conversion. # map returns an iterator in Python 3.0
  and a list in 2.x minver = list(map(int, '2.3'.split('.'))) + [0, 0,
  0] minverhex = 0 # xrange is not present in Python 3.0 and range
  returns an iterator for i in list(range(0, 4)): minverhex = (minverhex
  << 8) + minver[i] sys.exit(sys.hexversion < minverhex)
  ./configure: line 15238: python2.7: command not found
  configure:15240: $? = 127
  configure:15237: python2.6 -c import sys # split strings by '.' and
  

Bug#797381: marked as done (tex-common: postinst tries to create a temporary file in /)

[Debian Bug Tracking System]

Your message dated Thu, 03 Sep 2015 00:34:57 +
with message-id 
and subject line Bug#797381: fixed in tex-common 6.03
has caused the Debian Bug report #797381,
regarding tex-common: postinst tries to create a temporary file in /
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.)


-- 
797381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 6.02
Severity: serious
Justification: Policy 9.1

After `chattr +i /' the package fails to be configured, because it tries
to create some temporary file in the root directory:

   > sudo LC_ALL=C dpkg --configure -a
   Setting up tex-common (6.02) ...
   /usr/sbin/update-updmap: line 252: update-tl-conffile.texmf.new:
   Permission denied
   update-updmap: cannot write to the temporary file
   'update-tl-conffile.texmf.new'
   dpkg: error processing package tex-common (--configure):
subprocess installed post-installation script returned error exit status 1
   Errors were encountered while processing:
tex-common


The comments in update-updmap before the line 252 suggests that the file
should be created in the directory created in the line 234 instead, but
the script does not switch to the directory.


Regards,
robert

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'testing')
Architecture: i386 (i686)

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

Versions of packages tex-common depends on:
ii  dpkg  1.18.1
ii  ucf   3.0030

tex-common recommends no packages.

Versions of packages tex-common suggests:
ii  debhelper  9.20150628

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: tex-common
Source-Version: 6.03

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated tex-common 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: Thu, 03 Sep 2015 09:22:38 +0900
Source: tex-common
Binary: tex-common
Architecture: source all
Version: 6.03
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX maintainers 
Changed-By: Norbert Preining 
Description:
 tex-common - common infrastructure for building and installing TeX
Closes: 797381
Changes:
 tex-common (6.03) unstable; urgency=medium
 .
   * do not create temp files in / (Closes: #797381)
   * work on the documentation
Checksums-Sha1:
 04c3d80cb6acff634743db8344467cf25fe83d00 1731 tex-common_6.03.dsc
 5ca157bf2cd7187ffa53f677ef8a53f1405619bb 632190 tex-common_6.03.tar.gz
 d1349887edd8dab84d739ce6771e98424f1deb92 563496 tex-common_6.03_all.deb
Checksums-Sha256:
 6a977a14f0eaee8946f392212d805517c7999d3154e468f71033c4cbdcc62607 1731 
tex-common_6.03.dsc
 61b1d35e519741c850bddd56bd315ab4c3fa2eb111e3beaeb22bc2d26c663da4 632190 
tex-common_6.03.tar.gz
 cc3b916bec4510226c4f950dd0befae9c5142186f26395e6e39c1b0a1d9fe9a6 563496 
tex-common_6.03_all.deb
Files:
 6db7ab5a9980632e59c6c7de79f91ada 1731 tex optional tex-common_6.03.dsc
 4486a793ed671cf25bc2f39029828ccc 632190 tex optional tex-common_6.03.tar.gz
 f96e6e12eb697994b9d7467fb91a692e 563496 tex optional tex-common_6.03_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVeeTbmyspEiGDNwTAQjqJhAApK9nXDPb8haBov8LJtnOAZ/8VMSicoVs
+icQrNF+cW3B/ErbTXlDGtqsWzxZUoaSBWj61P3IgXsPsCWtnbOdnJvmcM8Jbr2f
cewoOKv55YMG4ZQEtVVETs7LTMYnN+UHYKTjPAmp8dHyMX8FI+GENktwD6Kn8IHP
NbQK+YuJjSnbCtIEI8A6DC25yYShIy0v1aQS/QxHvH1VBdNij5nRmuyKXPJiK4f+
9MHU0GYy7XMr44TK/prb2W+gHRqN96qX/v4Ay3A59bLXLWlawG66Y/KW8PVTTyKK
2zE1OsoLgM7GQdQjSN2LfQ1gFbsFHRDaNMX2B3pwvG8Pn9s87Wa+FXtAv0c2AgtS
+0ZiiSzZzeFzoBmNVfWR6885OzzI/mkH9S49GzP1PMAnguuVYOP1qA1CoS7y2KWe

Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source

[Chris Lamb]

Source: spice-gtk
Version: 0.29-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

Hi,

The spice-common/common/generated_* files are not reliably regenerated
from source.

Depending on the timezone of the build system, the package may FTBFS as
the `spice-common/python_modules/codegen.py` tool used to regenerate
these files requires python-six which is not included in the
Build-Depends.

(ie. I don't believe simply including python-six as a build-dependency
entirely resolves the issue)

Here's the build running in, for example,
TZ=/usr/share/zoneinfo/Etc/GMT-14

  [..]

  Making all in common
  make[5]: Entering directory
  '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/common'
GEN  generated_client_demarshallers.c
  Traceback (most recent call last):
File "../spice_codegen.py", line 7, in 
  from python_modules import spice_parser
File

"/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/python_modules/spice_parser.py",
line 10, in 
  from . import ptypes
File

"/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/python_modules/ptypes.py",
line 1, in 
  from . import codegen
File

"/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/python_modules/codegen.py",
line 2, in 
  import six
  ImportError: No module named six
  Makefile:788: recipe for target 'generated_client_demarshallers.c'
  failed
  make[5]: *** [generated_client_demarshallers.c] Error 1
  make[5]: Leaving directory
  '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common/common'
  Makefile:444: recipe for target 'all-recursive' failed
  make[4]: *** [all-recursive] Error 1
  make[4]: Leaving directory
  '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common'
  Makefile:376: recipe for target 'all' failed
  make[3]: *** [all] Error 2
  make[3]: Leaving directory
  '/tmp/buildd/spice-gtk-0.29/build-gtk3/spice-common'
  Makefile:667: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3'
  Makefile:570: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory '/tmp/buildd/spice-gtk-0.29/build-gtk3'
  debian/rules:42: recipe for target 'build-gtk3-stamp' failed
  make: *** [build-gtk3-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/spice-gtk_0.29-1.build2.log.gz


Regards,

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

Bug#793961: Update on TimGM6mb bug?

[Fabian Greffrath]

Hi Jack,

Am Mittwoch, den 26.08.2015, 00:20 +0200 schrieb Jack Underwood:
> Any news on this bug?  It looks like quite a simple fix, I would do it 
> myself but I don't know how to use the debian git system (I have only 
> ever used github before).

it should have made it to testing now.

Cheers,

Fabian


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

Bug#797855: spice-gtk:spice-common/common/generated_* not reliably generated from source

[Liang Guo]

Hi,

I cannot reproduce this error on my build environment. it looks this
is caused by lack dependency on python-six module.

I have added it in spice-gtk[1] git repository master branch, would you
like have a try ?

Thanks,

[1]
ssh://git.debian.org/git/collab-maint/spice-gtk.git

-- 
Liang Guo

Bug#793137: Also affects openscad - #797816

[Tiago Daitx]

The same issue has been reported in openscad for armhf. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797816

-- 
Tiago Stürmer Daitx
Software Engineer
tiago.da...@canonical.com

Bug#797825: file conflicts between librelion{+mpi}{+gui}-1.3-1{v5} packages

[Ralf Treinen]

Package: librelion-1.3-1
Version: 1.3+dfsg-3
Severity: serious
User: trei...@debian.org
Usertags: dose-file-overwrite

Hi,

there are file conflicts between the packages
librelion{+mpi}{+gui}-1.3-1{v5}. The concerned packages and their versions
are:

librelion-1.3-1/1.3+dfsg-2
librelion-1.3-1v5/1.3+dfsg-3
librelion+gui-1.3-1/1.3+dfsg-2
librelion+gui-1.3-1v5/1.3+dfsg-3
librelion+mpi-1.3-1/1.3+dfsg-2
librelion+mpi-1.3-1v5/1.3+dfsg-3
librelion+mpi+gui-1.3-1/1.3+dfsg-2
librelion+mpi+gui-1.3-1v5/1.3+dfsg-3

error on installing two packages together occurs since all these packages 
contain the files:

  /usr/lib/x86_64-linux-gnu/librelion-1.3.so.1
  /usr/lib/x86_64-linux-gnu/librelion-1.3.so.1.0.3

For instance:

Preparing to unpack .../librelion-1.3-1v5_1.3+dfsg-3_amd64.deb ...
Unpacking librelion-1.3-1v5:amd64 (1.3+dfsg-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/librelion-1.3-1v5_1.3+dfsg-3_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/librelion-1.3.so.1.0.3', which 
is also in package librelion+gui-1.3-1:amd64 1.3+dfsg-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.2-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/librelion-1.3-1v5_1.3+dfsg-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


-Ralf.

Bug#797743: marked as done (gromacs: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Wed, 2 Sep 2015 19:40:24 +0100
with message-id <55e74298.5090...@debian.org>
and subject line Re: [Debichem-devel] Bug#797743: gromacs: ABI transition 
needed for libstdc++ v5
has caused the Debian Bug report #797743,
regarding gromacs: ABI transition needed for libstdc++ v5
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.)


-- 
797743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gromacs
Version: 5.0.6-1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of gromacs, std::string appears in installed headers,
so it seems very likely that a transition is needed.

The transition normally consists of renaming the affected library packages,
adding a v5 suffix (.4v5, etc.). The SONAME should not be changed.
However, gromacs already does not package its shared library according to
Policy §8.1, so it will likely also need a versioned Breaks on
versions of votca-csg that do not depend on a separated shared library.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of gromacs:

* boost started its transition with 1.58
* everything else looks like a C ABI

so I think this is ready to go.

The package is likely to be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
On 02/09/15 19:03, Nicholas Breen wrote:
> On Wed, Sep 02, 2015 at 09:09:25AM +0100, Simon McVittie wrote:
>> In the case of gromacs, std::string appears in installed headers,
>> so it seems very likely that a transition is needed.
> 
> Isn't this just #791061 again?

You're right, there was already a bug (but for whatever reason, it
didn't end up on the Titanpad where the release team are tracking this
stuff).

> To the best of my knowledge, nothing external uses those.

They looked like they were intended to be public API to me, but you know
this code better than I do (I'd never seen it before this morning).
Closing, then. If you later discover that there should have been a
transition after all, you can do one at that point; it's not as if there
are many rdeps.

Sorry for the noise,
S--- End Message ---

Processed: tagging 753219

[Debian Bug Tracking System]

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

> tags 753219 - sid stretch
Bug #753219 {Done: Debian FTP Masters } 
[src:katoob] katoob: FTBFS: dpkg-source: error: expected ^--- in line 2 of diff 
`katoob-0.5.9.1/debian/patches/replace_fribidi-config_pkg-config.patch'
Removed tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#797823: amarok: Amarok crashes at startup with Qt5/Qt5 libs in stack

[Alex Dănilă]

Package: amarok
Version: 2.8.0-2.1+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Amarok crashes at startup with a stack containing both Qt4 and Qt5 libs. The 
system is a mix of Testing and Unstable, but Amarok from Unstable is not 
instalable due to dependencies.

The stack:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __strcmp_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29
#7  0x7fb099536c9f in QMetaType::registerNormalizedType(QByteArray const&, 
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void 
const*), int, QFlags, QMetaObject const*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb09982f060 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x7fb0c64ae9fa in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7ffdab1821b8, env=env@entry=0x7ffdab1821c8) at dl-init.c:78
#10 0x7fb0c64aeae3 in call_init (env=0x7ffdab1821c8, argv=0x7ffdab1821b8, 
argc=1, l=) at dl-init.c:36
#11 _dl_init (main_map=main_map@entry=0x2375aa0, argc=1, argv=0x7ffdab1821b8, 
env=0x7ffdab1821c8) at dl-init.c:126
#12 0x7fb0c64b2c48 in dl_open_worker (a=a@entry=0x7ffdab180658) at 
dl-open.c:577
#13 0x7fb0c64ae8b4 in _dl_catch_error 
(objname=objname@entry=0x7ffdab180648, 
errstring=errstring@entry=0x7ffdab180650, 
mallocedp=mallocedp@entry=0x7ffdab180647, operate=operate@entry=0x7fb0c64b2970 
, args=args@entry=0x7ffdab180658) at dl-error.c:187
#14 0x7fb0c64b243b in _dl_open (file=0x2369b50 
"/usr/lib/vlc/plugins/gui/libqt4_plugin.so", mode=-2147483647, 
caller_dlopen=, nsid=-2, argc=1, argv=0x7ffdab1821b8, 
env=0x7ffdab1821c8) at dl-open.c:661
#15 0x7fb0bd74202b in dlopen_doit (a=a@entry=0x7ffdab180870) at dlopen.c:66
#16 0x7fb0c64ae8b4 in _dl_catch_error (objname=0x20b9000, 
errstring=0x20b9008, mallocedp=0x20b8ff8, operate=0x7fb0bd741fd0 , 
args=0x7ffdab180870) at dl-error.c:187
#17 0x7fb0bd7425dd in _dlerror_run (operate=operate@entry=0x7fb0bd741fd0 
, args=args@entry=0x7ffdab180870) at dlerror.c:163
#18 0x7fb0bd7420c1 in __dlopen (file=, mode=) 
at dlopen.c:87
#19 0x7fb09fa4373f in ?? () from /usr/lib/libvlccore.so.8
#20 0x7fb09fa2787b in ?? () from /usr/lib/libvlccore.so.8
#21 0x7fb09fa27ba8 in ?? () from /usr/lib/libvlccore.so.8
#22 0x7fb09fa27b04 in ?? () from /usr/lib/libvlccore.so.8
#23 0x7fb09fa28084 in ?? () from /usr/lib/libvlccore.so.8
#24 0x7fb09fa2867a in ?? () from /usr/lib/libvlccore.so.8
#25 0x7fb09f9ae6fd in libvlc_InternalInit () from /usr/lib/libvlccore.so.8
#26 0x7fb09f77fa8b in libvlc_new () from /usr/lib/libvlc.so.5
#27 0x7fb09fcd1f6b in ?? () from 
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#28 0x7fb09fcb34d3 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#29 0x7fb09fcb4193 in qt_plugin_instance () from 
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#30 0x7fb0c39cd6d3 in QPluginLoader::instance (this=0x7ffdab1812c0) at 
plugin/qpluginloader.cpp:204
#31 0x7fb0a0348c1b in ?? () from 
/usr/lib/kde4/plugins/phonon_platform/kde.so
#32 0x7fb0a03493b7 in ?? () from 
/usr/lib/kde4/plugins/phonon_platform/kde.so
#33 0x7fb0c2cb2e06 in Phonon::FactoryPrivate::createBackend 
(this=this@entry=0x2207b50) at ../../phonon/factory.cpp:252
#34 0x7fb0c2cb4258 in Phonon::Factory::backend 
(createWhenNull=createWhenNull@entry=true) at ../../phonon/factory.cpp:576
#35 0x7fb0c2cb49a2 in Phonon::Factory::createAudioOutput (parent=0x20ebf00) 
at ../../phonon/factory.cpp:470
#36 0x7fb0c2ca803f in Phonon::AudioOutputPrivate::createBackendObject 
(this=0x21eb430) at ../../phonon/audiooutput.cpp:136
#37 0x7fb0c2ca552f in Phonon::AudioOutputPrivate::init (this=0x21eb430, 
c=Phonon::MusicCategory) at ../../phonon/audiooutput.cpp:103
#38 0x7fb0c6022af3 in EngineController::initializePhonon (this=0x2206120) 
at ../../src/EngineController.cpp:148
#39 0x7fb0c6029905 in EngineController::qt_static_metacall (_o=0x2206120, 
_id=, _a=, _c=) at 
./EngineController.moc:198
#40 0x7fb0c39f2bac in QMetaMethod::invoke (this=this@entry=0x7ffdab181a20, 
object=object@entry=0x2206120, 
connectionType=connectionType@entry=Qt::DirectConnection, returnValue=..., 
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., 
val8=..., val9=...) at kernel/qmetaobject.cpp:1664
#41 0x7fb0c39f50ee in QMetaObject::invokeMethod (obj=obj@entry=0x2206120, 
member=member@entry=0x7fb0c6193161 "initializePhonon", 
type=type@entry=Qt::DirectConnection, ret=..., val0=..., val1=..., val2=..., 
val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at 
kernel/qmetaobject.cpp:1179
#42 0x7fb0c60f11af in QMetaObject::invokeMethod (val9=..., val8=..., 
val7=..., val6=..., val5=..., val4=..., val3=..., 

Bug#797809: gazebo ftbfs with SDF 3.0

[Matthias Klose]

Package: src:gazebo
Version: 5.0.1+dfsg-2.1
Severity: serious
Tags: sid stretch patch

gazebo explicitly wants SDF 2.3, fails with 3.0.

Bug#753219: marked as done (katoob: FTBFS: dpkg-source: error: expected ^--- in line 2 of diff `katoob-0.5.9.1/debian/patches/replace_fribidi-config_pkg-config.patch')

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 18:16:30 +
with message-id 
and subject line Bug#797810: Removed package(s) from unstable
has caused the Debian Bug report #753219,
regarding katoob: FTBFS: dpkg-source: error: expected ^--- in line 2 of diff 
`katoob-0.5.9.1/debian/patches/replace_fribidi-config_pkg-config.patch'
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.)


-- 
753219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: katoob
Version: 0.5.9.1-4.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 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):
> Unpack source
> ─
> 
> gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file 
> open error
> gpgv: Signature made Sat Mar  8 07:57:14 2014 UTC using RSA key ID 93AA7172
> gpgv: Can't check signature: public key not found
> dpkg-source: warning: failed to verify signature on ./katoob_0.5.9.1-4.1.dsc
> dpkg-source: info: extracting katoob in katoob-0.5.9.1
> dpkg-source: info: unpacking katoob_0.5.9.1.orig.tar.gz
> dpkg-source: info: unpacking katoob_0.5.9.1-4.1.debian.tar.xz
> dpkg-source: error: expected ^--- in line 2 of diff 
> `katoob-0.5.9.1/debian/patches/replace_fribidi-config_pkg-config.patch'
> dpkg-source: info: applying replace_fribidi-config_pkg-config.patch
> dpkg-source: info: fuzz is not allowed when applying patches
> dpkg-source: info: if patch 'replace_fribidi-config_pkg-config.patch' is 
> correctly applied by quilt, use 'quilt refresh' to update it
> FAILED [dpkg-source died]

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/katoob_0.5.9.1-4.1_unstable.log

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

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

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Paul Richards Tagliamonte (the ftpmaster behind the curtain)--- End Message ---

Bug#797829: python-igraph ftbfs in unstable with igraph 0.7

[Matthias Klose]

Package: src:python-igraph
Version: 0.6.5-1
Severity: serious
Tags: sid stretch patch

python-igraph ftbfs in unstable with igraph 0.7

An updated upstream package is available from
https://launchpad.net/ubuntu/+source/python-igraph/0.7.1post6-0ubuntu2

Please also create a python3-igraph package.

Bug#768905: marked as done (FTBFS: fails test "CHECK INVALID KEY TYPE")

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 21:37:25 +
with message-id 
and subject line Bug#768905: fixed in keyutils 1.5.9-6
has caused the Debian Bug report #768905,
regarding FTBFS: fails test "CHECK INVALID KEY TYPE"
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.)


-- 
768905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:keyutils
Version: 1.5.9-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid that during a rebuild of jessie on armhf (using sbuild) your
package failed to build:

Running with session keyring RHTS/keyctl/16243
Joined session keyring: 900352959
=== /«PKGBUILDDIR»/tests/bugzillas/bz1033467/test.out ===
+++ ADD SANDBOX KEYRING
+++ ADD NESTED KEYRINGS
+++ ADD KEYS
+++ SEARCH KEYS
+++ COMPARE KEY LISTS
+++ SEARCH MISSES
Running with session keyring RHTS/keyctl/16462
Joined session keyring: 452861916
=== /«PKGBUILDDIR»/tests/keyctl/add/bad-args/test.out ===
+++ CHECK EMPTY KEY TYPE
+++ CHECK UNSUPPORTED KEY TYPE
+++ CHECK INVALID KEY TYPE
FAILED
+++ CHECK MAXLEN KEY TYPE
+++ CHECK OVERLONG KEY TYPE
+++ CHECK ADD KEYRING WITH PAYLOAD
+++ CHECK MAXLEN DESC
+++ CHECK OVERLONG DESC
+++ CHECK BAD KEY ID


I also tried on amd64, it fails as well.

Full log attached.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 3.8.13.28 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
sbuild (Debian sbuild) 0.65.0 (16 Oct 2014) on kholdan.angband.pl

╔══╗
║ keyutils 1.5.9-5 (armhf)   09 Nov 2014 23:14 ║
╚══╝

Package: keyutils
Version: 1.5.9-5
Source Version: 1.5.9-5
Distribution: jessie
Machine Architecture: armhf
Host Architecture: armhf
Build Architecture: armhf

I: NOTICE: Log filtering will replace 'build/keyutils-OfgnbA/keyutils-1.5.9' 
with '«PKGBUILDDIR»'
I: NOTICE: Log filtering will replace 'build/keyutils-OfgnbA' with '«BUILDDIR»'
I: NOTICE: Log filtering will replace 
'var/lib/schroot/mount/jessie-armhf-sbuild-ae51cb99-08f5-4ef6-9040-cb5330705049'
 with '«CHROOT»'

┌──┐
│ Update chroot│
└──┘

Get:1 http://apt.angband.pl:3142 jessie InRelease [191 kB]
Get:2 http://apt.angband.pl:3142 jessie/main Sources/DiffIndex [7876 B]
Get:3 http://apt.angband.pl:3142 jessie/main armhf Packages/DiffIndex [7876 B]
Get:4 http://apt.angband.pl:3142 jessie/main Translation-en/DiffIndex [7876 B]
Get:5 http://apt.angband.pl:3142 jessie/main armhf 2014-11-09-1442.26.pdiff 
[25.5 kB]
Get:6 http://apt.angband.pl:3142 jessie/main armhf 2014-11-09-1442.26.pdiff 
[25.5 kB]
Fetched 240 kB in 19s (12.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
  liblzma5 login passwd sed tar xz-utils
6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 2930 kB of archives.
After this operation, 37.9 kB disk space will be freed.
Get:1 http://apt.angband.pl:3142/ftp.pl.debian.org/debian/ jessie/main login 
armhf 1:4.2-2+b2 [715 kB]
Get:2 http://apt.angband.pl:3142/ftp.pl.debian.org/debian/ jessie/main sed 
armhf 4.2.2-4+b1 [237 kB]
Get:3 http://apt.angband.pl:3142/ftp.pl.debian.org/debian/ jessie/main tar 
armhf 1.27.1-2+b1 [651 kB]
Get:4 http://apt.angband.pl:3142/ftp.pl.debian.org/debian/ jessie/main liblzma5 
armhf 5.1.1alpha+20120614-2+b1 [188 kB]
Get:5 http://apt.angband.pl:3142/ftp.pl.debian.org/debian/ jessie/main passwd 
armhf 1:4.2-2+b2 [921 kB]
Get:6 http://apt.angband.pl:3142/ftp.pl.debian.org/debian/ jessie/main xz-utils 
armhf 5.1.1alpha+20120614-2+b1 [218 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 2930 kB in 0s (6762 kB/s)
(Reading database ... 12100 files and directories currently installed.)
Preparing to unpack .../login_1%3a4.2-2+b2_armhf.deb ...
Unpacking login (1:4.2-2+b2) over (1:4.2-2+b1) ...
Processing triggers for man-db (2.7.0.2-3) ...
Not building database; 

Bug#797835: libphonenumber: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: libphonenumber
Version: 6.3~svn698-4
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of libphonenumber, std::string appears in installed headers
and in the library's exported symbols, so it seems very likely that a
transition is needed. The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libphonenumber6v5).
The SONAME should not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is otherwise low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of libphonenumber, all the C++ libraries
seem to have started their transitions already, so it seems ready to go.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#624776: marked as done (different g++-, gcj-versions break pdftk)

[Debian Bug Tracking System]

Your message dated Thu, 3 Sep 2015 00:35:04 +0200
with message-id <55e77998.1000...@debian.org>
and subject line closing old bug
has caused the Debian Bug report #624776,
regarding different g++-, gcj-versions break pdftk
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.)


-- 
624776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-defaults
Version: 4.6.0-5
Severity: serious

Hi,

that g++ and gcj have different versions breaks the build of pdftk,
see e.g.
https://buildd.debian.org/fetch.cgi?pkg=pdftk=1.41%2Bdfsg-11%2Bb1=powerpc=1304254757=log


If fixing pdftk to just use the default version, it builds, but after
startup the following error happens:

$ pdftk
libgcj failure: gcj linkage error.
Incorrect library ABI version detected.  Aborting.


So it seems to me this can either only be avoided with having g++ and
gcj pointing to the same version, and/or explicitly depending on one
version in the build-dependencies of pdftk (which I would consider
more ugly - but YMMV).



Andi


--- End Message ---
--- Begin Message ---
there are no mismatching vesions anymore.--- End Message ---

Bug#797233: marked as done (libsndio-dev and libroar-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 21:44:57 +
with message-id 
and subject line Bug#797233: fixed in roaraudio 1.0~beta11-4
has caused the Debian Bug report #797233,
regarding libsndio-dev and libroar-dev: error when trying to install together
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.)


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

Package: libroar-dev
Version: 1.0~beta11-3
Severity: minor

I'm the (prospective) maintainer for sndio in Debian. libroar-dev 
presently contains /usr/include/sndio.h, seemingly intended only for 
building against roaraudio's sndio compatibility library without sndio 
itself present (it serves only to include libroarsndio/libroarsndio.h). 
As packages with sndio support should eventually build-depend on 
libsndio-dev, this will stop being useful when/if sndio enters sid, and 
at any rate will prevent packages from supporting both sndio and 
roaraudio. It would probably be best to simply remove this file, 
allowing packages that really want to use libroarsndio.h to include it 
directly.
--- End Message ---
--- Begin Message ---
Source: roaraudio
Source-Version: 1.0~beta11-4

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated roaraudio 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, 02 Sep 2015 19:31:18 +0200
Source: roaraudio
Binary: libroar2 libroar-dev roaraudio-dbg roaraudio roarclients 
libroar-compat2 libroar-compat-tools libroar-plugins-universal
Architecture: source amd64
Version: 1.0~beta11-4
Distribution: unstable
Urgency: medium
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 libroar-compat-tools - drop-in replacements for other sound libraries (tools 
package)
 libroar-compat2 - drop-in replacements for other sound libraries
 libroar-dev - header files and documentation for the RoarAudio libraries
 libroar-plugins-universal - Collection of host-independent plugins for libroar
 libroar2   - foundation libraries for the RoarAudio sound server and clients
 roaraudio  - sound server for audio mixing
 roaraudio-dbg - RoarAudio sound server for audio mixing (debugging symbols)
 roarclients - Collection of basic clients for the RoarAudio Sound System
Closes: 797233
Changes:
 roaraudio (1.0~beta11-4) unstable; urgency=medium
 .
   * Do not install sndio.h.
 Closes: #797233
   * Add patch 02-manpage-spelling-errors which fixes a few spelling errors in
 the manpages.
Checksums-Sha1:
 15afcc4d23267f1c4261a48e68405095e239b06d 2428 roaraudio_1.0~beta11-4.dsc
 22703de1a8bee8abc643bb65af683d62566c1487 26148 
roaraudio_1.0~beta11-4.debian.tar.xz
 8c2778d3c4f496faa6cc511a9b1b8b6d82754367 20786 
libroar-compat-tools_1.0~beta11-4_amd64.deb
 ea4e45ecd76137e4616f67434ef7f3f65ef0f05a 56444 
libroar-compat2_1.0~beta11-4_amd64.deb
 abcba78b25f8fd5190158acdba7a909fd9d12f6c 236296 
libroar-dev_1.0~beta11-4_amd64.deb
 0a87efbdf8b15254a2cd70c37ecd77dc10a36603 38684 
libroar-plugins-universal_1.0~beta11-4_amd64.deb
 e10530800691e714c12a8d8028ee2c42cc511d5a 182640 libroar2_1.0~beta11-4_amd64.deb
 422bd5389330569bd26d2493870a3d62a40eb802 1397634 
roaraudio-dbg_1.0~beta11-4_amd64.deb
 d737ae534284d92c2fe9bde2a5645595e149b2f5 147854 
roaraudio_1.0~beta11-4_amd64.deb
 6b70854f4644e856da105e68e386e80227140014 99300 
roarclients_1.0~beta11-4_amd64.deb
Checksums-Sha256:
 8b0f59258d102a4b55732172fd84c5849a2f1a518aff6de6088ed9f21b49def7 2428 
roaraudio_1.0~beta11-4.dsc
 0e6c010a7f7d2308cb9e679b8ff5a8c19f2d48a2edfb6b9e3d5a4abea2f95b88 26148 
roaraudio_1.0~beta11-4.debian.tar.xz
 c277d7392a5e73eb8b6d3719df0a7ff7bc1a52e9a28ba35a3f216edc7ffe600b 20786 
libroar-compat-tools_1.0~beta11-4_amd64.deb
 9ed6bacebbb1b791d888303469b68f75630e840d77a6c946b6d993ae2110e225 56444 
libroar-compat2_1.0~beta11-4_amd64.deb
 

Bug#795104: marked as done (FTBFS on powerpc: gcc: error trying to exec 'as': execvp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 22:28:40 +
with message-id 
and subject line Bug#795104: fixed in mediawiki2latex 7.20-1.1
has caused the Debian Bug report #795104,
regarding FTBFS on powerpc: gcc: error trying to exec 'as': execvp: No such 
file or directory
to be marked as done.

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

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


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

Hi,

From
  
https://buildd.debian.org/status/fetch.php?pkg=mediawiki2latex=powerpc=7.20-1=1433880385

  runhaskell Setup.lhs configure
  Configuring mediawiki2latex-7.20...
  gcc: error trying to exec 'as': execvp: No such file or directory

This is the same as #789458 (will be fixed with GHC 7.10, apparently).
You can work around it by avoiding the use of ghci. Once there's a bug #
I'll NMU a fix to DELAYED/7 for you to look at.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
--- End Message ---
--- Begin Message ---
Source: mediawiki2latex
Source-Version: 7.20-1.1

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

Debian distribution maintenance software
pp.
Iain Lane  (supplier of updated mediawiki2latex 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: Wed, 02 Sep 2015 22:02:26 +0100
Source: mediawiki2latex
Binary: mediawiki2latex
Architecture: source amd64
Version: 7.20-1.1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Huenniger 
Changed-By: Iain Lane 
Description:
 mediawiki2latex - Loads pages from MediaWiki and converts to LaTeX and PDF
Closes: 795104
Changes:
 mediawiki2latex (7.20-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Avoid using runhaskell (ghci), to work around bug on powerpc causing FTBFS
 (see Debian bug #789458) (Closes: #795104)
   * Generalise the lintian override to catch all binary-or-shlib-defines-rpath
 instances.
Checksums-Sha1:
 a35875487bd336960a9c80204bf09f52784b9479 2333 mediawiki2latex_7.20-1.1.dsc
 5202b774dea14ea3ff7cf5f7da0238e75d7da17f 5688 
mediawiki2latex_7.20-1.1.debian.tar.xz
 27a1fffa36e931cdd9110dee625b6e93b389ad10 3918250 
mediawiki2latex_7.20-1.1_amd64.deb
Checksums-Sha256:
 924cbff84c2ba3f6af5ffe6355a9a6741f5a459bdfa32f45884ebf893ccdd805 2333 
mediawiki2latex_7.20-1.1.dsc
 800d43686c4ae4676bb65d343bf935618e249fb3f6d182e57da028f9be648816 5688 
mediawiki2latex_7.20-1.1.debian.tar.xz
 1ae80e27433d343835124f5bf027791756c1e20514459b86e5325a900628a0a5 3918250 
mediawiki2latex_7.20-1.1_amd64.deb
Files:
 cb7d6490b74b90f92ea84542660b9b88 2333 misc optional 
mediawiki2latex_7.20-1.1.dsc
 551a1cc43efe9251cae4128facbc 5688 misc optional 
mediawiki2latex_7.20-1.1.debian.tar.xz
 50be48a7d107f390464f453306e5b4de 3918250 misc optional 
mediawiki2latex_7.20-1.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJV52y5AAoJEONS1cUcUEHU+nIQAIjF6GKX1VinXUeGRIC655Nf
iMjdo3lR/21lEObvkeIhyKspuk3YAuq5alBBCTB+kAF1yPfgwU/m5FfQR4Ycot+9
Gp8B/WRF2dpaQBBMRD5XbRy+2Ow8vTx2YRnuAG4MTY9kHMhRI4NA5LnMfmBRx6Mk
jK2OkUzhRHZxquOmyS0M2JptdnUFv+Fpe5EcrYbIAXoJMJb/2rQyfTrK+PuxZViI
ZF69mW39w7nf1s/O0cBRZHHVJgwO8VgH8+lM9+nhbobtTNOccfjAZA59h058oJd5
DhmJjWoltw07IYF2+aihIAiKc6ra4rZUphKa+a5N0V3aZLpUKwop4lLbcJk/R6Aq
un1RIlfP8ya3wpWh+6Zm0OXao3eKtCbU0m3MgCIp56fpKF3CbarfDiWUoZSz4hUs
K/WdtUGvV5pVvleoRW+8wgOz7bcVAt13FsIT/axbsAZsrqjMygIya3/xSoQyfKWd
/wJ+kD29KPmwpqNvYhSnziFvkuMBawo3ujAgu2KqWiPzKQ9ZMWh+4DwOVUlYZjGx
MXz/ltR0yFSu6hswxlMJrTGbpBS7ubSe7LrqRF22brd/cNUSaBuhMlRtQtI0uOAR
Ix1SMDghLMiSy9bj7h8nInSVV7YrTTNwIoiJjg9nBSoDJ+bLtwrsadwMwC+vuVuP
514GDbt3HPOmSn6U6Qpp
=ofyh
-END PGP SIGNATURE End Message ---

Bug#797841: build pdftk using the default g++/gcj

[Matthias Klose]

Package: src:pdftk
Version: 2.02-3
Severity: serious
Tags: sid stretch patch

please build the package using unversioned build dependencies. we definitely
will remove gcj-4.9 and g++-4.9 for the next release.
diff -Nru pdftk-2.02/debian/changelog pdftk-2.02/debian/changelog
--- pdftk-2.02/debian/changelog 2015-07-02 00:50:30.0 +0200
+++ pdftk-2.02/debian/changelog 2015-09-03 00:26:13.0 +0200
@@ -1,3 +1,10 @@
+pdftk (2.02-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using the default g++/gcj compilers.
+
+ -- Matthias Klose   Wed, 02 Sep 2015 22:25:42 +0200
+
 pdftk (2.02-3) unstable; urgency=medium
 
   * Fix bug that corrupts images in PDF files on (de)compressing.
diff -Nru pdftk-2.02/debian/control pdftk-2.02/debian/control
--- pdftk-2.02/debian/control   2014-10-20 23:50:30.0 +0200
+++ pdftk-2.02/debian/control   2015-09-03 00:27:46.0 +0200
@@ -2,7 +2,7 @@
 Section: text
 Priority: optional
 Maintainer: Johann Felix Soden 
-Build-Depends: debhelper (>= 9), gcj-4.9-jdk, g++-4.9
+Build-Depends: debhelper (>= 9), gcj-jdk
 Standards-Version: 3.9.6
 Homepage: http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/
 Vcs-Git: git://anonscm.debian.org/collab-maint/pdftk.git
diff -Nru pdftk-2.02/debian/rules pdftk-2.02/debian/rules
--- pdftk-2.02/debian/rules 2014-05-22 01:26:00.0 +0200
+++ pdftk-2.02/debian/rules 2015-09-03 00:27:31.0 +0200
@@ -5,7 +5,7 @@
 # VERSUFF=-$(shell gcj --version | sed -r -e '1s/.* ([0-9]+\.[0-9]+).*/\1/;q')
 
 # use (temporary) fixed gcj/g++ version from debian/control
-VERSUFF=$(shell grep -oP '(?<=gcj)-[0-9.]*' debian/control)
+#VERSUFF=$(shell grep -oP '(?<=gcj)-[0-9.]*' debian/control)
 
 DPKG_EXPORT_BUILDFLAGS = 1
 -include /usr/share/dpkg/buildflags.mk

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 793518 0.0~git20150730-1
Bug #793518 [src:golang-github-glacjay-goini] FTBFS: TestString fails: 
ini_test.go:167: Dict cannot be stringified as expected.
Marked as fixed in versions golang-github-glacjay-goini/0.0~git20150730-1.
>
End of message, stopping processing here.

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

Processed: Re: Bug#793260: [Pkg-ime-devel] Bug#793260: marisa: change of type in system_error might break with GCC-5

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #793260 [src:marisa] marisa: change of type in system_error might break 
with GCC-5
Severity set to 'serious' from 'important'

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

Processed: your mail

[Debian Bug Tracking System]

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

> close 793518 0.0~git20150730-1
Bug #793518 [src:golang-github-glacjay-goini] FTBFS: TestString fails: 
ini_test.go:167: Dict cannot be stringified as expected.
Ignoring request to alter fixed versions of bug #793518 to the same values 
previously set
Bug #793518 [src:golang-github-glacjay-goini] FTBFS: TestString fails: 
ini_test.go:167: Dict cannot be stringified as expected.
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#796917: snappy1.0.3-java: dependency on libsnappy1

[Andreas Tille]

Hi,

I guess the current dependency was injected due to the fact that the original
upstream source contained a copy if libsnappy.so and

  src/main/java/org/xerial/snappy/LoadSnappy.java

says:

 * This class loads a native library of snappy-java (snappyjava.dll,
 * libsnappy.so, etc.) according to the user platform (os.name and
 * os.arch). The natively compiled libraries bundled to snappy-java
 * contain the codes of the original snappy and JNI programs to access Snappy.
 *
 * In default, no configuration is required to use snappy-java, but you can load
 * your own native library created by 'make native' command.
 * 
 * LoadSnappy searches for native libraries (snappyjava.dll, libsnappy.so, etc.)
 * in the following order:
 * 
 * (System property: org.xerial.snappy.lib.path)/(System property:
 * org.xerial.lib.name)
 * One of the libraries embedded in snappy-java-(version).jar extracted into
 * (System property: java.io.tempdir or if
 * org.xerial.snappy.tempdir is set, use this folder.)
 * Folders in LD_PATH environment variable (This is the default path that
 * JVM searches for native libraries)
 * 
 * 
 * 
 * If you do not want to use folder java.io.tempdir, set the System
 * property org.xerial.snappy.tempdir. For example, to use
 * /tmp/leo as a temporary folder to copy native libraries, use -D option


On Tue, Aug 25, 2015 at 09:50:30PM +0200, Julien Cristau wrote:
> Source: snappy1.0.3-java
> Version: 1.0.3-rc3~dfsg-5
> Severity: serious
> 
> libsnappy1 is being replaced by libsnappy1v5.  Your arch:all package has
> a hardcoded dependency on the former (how does that even work?).


Before I simply add a hardcoded libsnappy1v5 I would like to ask for
comments whether there is some better way to solve this.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: insighttoolkit: ABI transition needed for libstdc++ v5

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 797738
Bug #797755 [src:insighttoolkit] insighttoolkit: ABI transition needed for 
libstdc++ v5
797755 was not blocked by any bugs.
797755 was not blocking any bugs.
Added blocking bug(s) of 797755: 797738

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

Bug#778081: marked as done (qapt: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 09:56:37 +
with message-id 
and subject line Bug#797753: Removed package(s) from unstable
has caused the Debian Bug report #778081,
regarding qapt: ftbfs with GCC-5
to be marked as done.

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

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


-- 
778081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qapt
Version: 1.3.0-2.1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/qapt_1.3.0-2.1_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
^
In file included from /«PKGBUILDDIR»/src/package.cpp:33:0:
/usr/include/apt-pkg/algorithms.h:146:24: note: declared here
APT_DEPRECATED void InstallProtect();
^
/«PKGBUILDDIR»/src/package.cpp: In member function 'void 
QApt::Package::setPurge()':
/«PKGBUILDDIR»/src/package.cpp:1264:24: warning: 'void 
pkgProblemResolver::InstallProtect()' is deprecated [-Wdeprecated-declarations]
 Fix.InstallProtect();
^
In file included from /«PKGBUILDDIR»/src/package.cpp:33:0:
/usr/include/apt-pkg/algorithms.h:146:24: note: declared here
APT_DEPRECATED void InstallProtect();
^
/«PKGBUILDDIR»/src/backend.cpp: In member function 'bool 
QApt::Backend::loadSelections(const QString&)':
/«PKGBUILDDIR»/src/backend.cpp:1247:24: warning: 'void 
pkgProblemResolver::InstallProtect()' is deprecated [-Wdeprecated-declarations]
 Fix.InstallProtect();
^
In file included from /«PKGBUILDDIR»/src/backend.cpp:31:0:
/usr/include/apt-pkg/algorithms.h:146:24: note: declared here
APT_DEPRECATED void InstallProtect();
^
/usr/bin/cmake -E cmake_progress_report 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
[ 83%] Building CXX object src/CMakeFiles/qapt.dir/moc_cache.o
cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -Dqapt_EXPORTS 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -std=c++0x -fno-threadsafe-statics -fvisibility=hidden 
-fvisibility-inlines-hidden -fPIC -I/«PKGBUILDDIR» 
-I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/usr/include/qt4 
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtDBus -I/usr/include/polkit-qt-1 
-I/«PKGBUILDDIR»/src -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src-o 
CMakeFiles/qapt.dir/moc_cache.o -c 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/moc_cache.cxx
/usr/bin/cmake -E cmake_progress_report 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 85
[ 84%] Building CXX object src/CMakeFiles/qapt.dir/moc_config.o
cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -Dqapt_EXPORTS 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -std=c++0x -fno-threadsafe-statics -fvisibility=hidden 
-fvisibility-inlines-hidden -fPIC -I/«PKGBUILDDIR» 
-I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/usr/include/qt4 
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtDBus -I/usr/include/polkit-qt-1 
-I/«PKGBUILDDIR»/src -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src-o 
CMakeFiles/qapt.dir/moc_config.o -c 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/moc_config.cxx
/usr/bin/cmake -E cmake_progress_report 
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
[ 84%] Building CXX object src/CMakeFiles/qapt.dir/moc_history.o
cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/c++   -Dqapt_EXPORTS 
-g -O2 

Bug#769148: marked as done (gstreamer1.0-qapt: fails to upgrade from 'sid' - trying to overwrite /usr/lib/kde4/libexec/qapt-gst-helper)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 09:56:37 +
with message-id 
and subject line Bug#797753: Removed package(s) from unstable
has caused the Debian Bug report #769148,
regarding gstreamer1.0-qapt: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/kde4/libexec/qapt-gst-helper
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.)


-- 
769148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gstreamer1.0-qapt
Version: 2.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package gstreamer1.0-qapt.
  Preparing to unpack .../gstreamer1.0-qapt_2.2.0-1_amd64.deb ...
  Unpacking gstreamer1.0-qapt (2.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gstreamer1.0-qapt_2.2.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/kde4/libexec/qapt-gst-helper', which is also 
in package gstreamer0.10-qapt 1.3.0-2.1


cheers,

Andreas


gstreamer0.10-qapt=1.3.0-2.1_gstreamer1.0-qapt=2.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.3.0-2.1+rm

Dear submitter,

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

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

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

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

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

Bug#796917: snappy1.0.3-java: dependency on libsnappy1

[Emmanuel Bourg]

I'm not sure snappy1.0.3-java even works. The native part isn't compiled
(the SnappyNative.h and SnappyNative.c files in
src/main/java/org/xerial/snappy). So the libsnappy1 dependency is bogus
and could be removed.

I suggest removing snappy1.0.3-java and use snappy-java instead. This
one is known to work. picard-tools is the only reverse dependency of
libsnappy1.0.3-java, I'll prepare an update.

Emmanuel Bourg

Bug#797740: marked as done (apt-show-source: Previous NMU FTBFS and binaries lost)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 11:00:08 +
with message-id 
and subject line Bug#797740: fixed in apt-show-source 0.10+nmu2
has caused the Debian Bug report #797740,
regarding apt-show-source: Previous NMU FTBFS and binaries lost
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.)


-- 
797740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-source
Version: 0.10+nmu1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

The last NMU FTBFS due to the way it was uploaded and then because of the way
the cruft report works, the old binaries were removed.  I'm going to do a no
change upload go resolve the FTBFS and get binaries back for this package.

NMU diff attached.
diff -Nru apt-show-source-0.10+nmu1/debian/changelog apt-show-source-0.10+nmu2/debian/changelog
--- apt-show-source-0.10+nmu1/debian/changelog	2015-08-20 16:16:45.0 -0400
+++ apt-show-source-0.10+nmu2/debian/changelog	2015-09-02 03:19:52.0 -0400
@@ -1,3 +1,10 @@
+apt-show-source (0.10+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild to fix FTBFS and restore lost binaries
+
+ -- Scott Kitterman   Wed, 02 Sep 2015 03:19:02 -0400
+
 apt-show-source (0.10+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
--- End Message ---
--- Begin Message ---
Source: apt-show-source
Source-Version: 0.10+nmu2

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated apt-show-source 
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, 02 Sep 2015 03:19:02 -0400
Source: apt-show-source
Binary: apt-show-source
Architecture: source all
Version: 0.10+nmu2
Distribution: unstable
Urgency: medium
Maintainer: OHURA Makoto 
Changed-By: Scott Kitterman 
Description:
 apt-show-source - Shows source-package information
Closes: 797740
Changes:
 apt-show-source (0.10+nmu2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild to fix FTBFS and restore lost binaries (Closes: 797740)
Checksums-Sha1:
 ff6916155320865245365a228b3889c9415c408e 1442 apt-show-source_0.10+nmu2.dsc
 f0d1b439237e5ac7879a8db0e95d6a223fa9b355 9187 apt-show-source_0.10+nmu2.tar.gz
 546cc1c457a6010f30c2d51dfb4a02ebb094b307 17666 
apt-show-source_0.10+nmu2_all.deb
Checksums-Sha256:
 964b7d540b02163b2859ad9c69f335f8412a724f5f08b0854eac51d2a7e05b8a 1442 
apt-show-source_0.10+nmu2.dsc
 4ad427cebad774c760e41487d7e3f0125ab2f6a1bf0d1e32041a051b12231701 9187 
apt-show-source_0.10+nmu2.tar.gz
 c7ecf341a0847cf0171f973a62dd7bf65301179a025606da660e59fb851a8c6f 17666 
apt-show-source_0.10+nmu2_all.deb
Files:
 86f1c1809e1fa96f5c381c434d49f6ad 1442 admin optional 
apt-show-source_0.10+nmu2.dsc
 3cc07e722d2a531d971d51b6bcd1f9c0 9187 admin optional 
apt-show-source_0.10+nmu2.tar.gz
 eacd2af4c41ca1df55c301240461956f 17666 admin optional 
apt-show-source_0.10+nmu2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV5qh+AAoJEHjX3vua1ZrxkoEQAKzP5uSd0valJ6KLoIMnAa4j
KqqWwDQrWnB63ERzWAuQC3RGlcXvKlkWQsPu7fhu0stqOxqIoFPS0f4BjEYtD2LA
9gRXYv2c+lXVvzEtbi8TtgV0lT+YYnboxyfW+iuH3KHCJirB9PvWg/7v6yz68A34
bfJ002XO5glWDEqCCSS2ssZJTK0yW70kdkVXo/cBRcQFSzEASa8//paa3lAQjFqH
ikD/CR09ESZPR9u75rR3rksaXr65bi4j3NM20rcH7XYk2Me42mKPGWWJ78O0r5l3
RJdfXfVZKMoDI19GG+efdXZ8xGAW3sS+D9rlF0MrYXokGC/pdEZFjS0GCLhZZm2s
d0L/NaimFJeEd/Z5FiT7RJvPP7q3fgnpeY14Y2oETzXAI9FHlbgAMVVsqzD4t619
nIFdWXbAsJZ9fWk+Ahz2jzWL6htaDrcOpkQHqQHHIgR28L123B/H91h78WO0ahLw
eVtqGKJy4g1XtXYMQD/O3kS4Ts9un2iYM2e4treoSELkUiXiPZ+mLeootPzs2USD
7IkI+/ScowOZH3CtqiCHjUCG6/H46IPHxhRcsn7lCrHyiIXFFpjsbecOM9e9wqC2
wBA5ZQysrYgUU3WO6YGRDR1cNLGpS+0+/sCBOxRpZz+ukdUFTt011r/n42pNoFk6
z9x2tlrRd4GLxV7Zb+it
=UuGI
-END PGP SIGNATURE End Message ---

Bug#797741: marked as done (cgi-extratags-perl: Last NMU FTBFS and old binaries inadvertently removed)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 11:00:09 +
with message-id 
and subject line Bug#797741: fixed in cgi-extratags-perl 0.03-1.2
has caused the Debian Bug report #797741,
regarding cgi-extratags-perl: Last NMU FTBFS and old binaries inadvertently 
removed
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.)


-- 
797741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cgi-extratags-perl
Version: 0.03-1.1
Severity: serious
Tags: patch
Justification: fails to build from source

The last NMU FTBFS due to the way it was uploaded and then because of the way
the cruft report works, the old binaries were removed.  I'm going to do a no
change upload go resolve the FTBFS and get binaries back for this package.

NMU diff attached.
diff -u cgi-extratags-perl-0.03/debian/changelog cgi-extratags-perl-0.03/debian/changelog
--- cgi-extratags-perl-0.03/debian/changelog
+++ cgi-extratags-perl-0.03/debian/changelog
@@ -1,3 +1,10 @@
+cgi-extratags-perl (0.03-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild to fix FTBFS and restore lost binaries
+
+ -- Scott Kitterman   Wed, 02 Sep 2015 03:22:29 -0400
+
 cgi-extratags-perl (0.03-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
--- End Message ---
--- Begin Message ---
Source: cgi-extratags-perl
Source-Version: 0.03-1.2

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated cgi-extratags-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 Sep 2015 03:22:29 -0400
Source: cgi-extratags-perl
Binary: libcgi-extratags-perl
Architecture: source all
Version: 0.03-1.2
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Scott Kitterman 
Description:
 libcgi-extratags-perl - Useful Extensions for the CGI Module
Closes: 797741
Changes:
 cgi-extratags-perl (0.03-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild to fix FTBFS and restore lost binaries (Closes: 797741)
Checksums-Sha1:
 403416e3b53d00a807b669e55af473443c243a09 1745 cgi-extratags-perl_0.03-1.2.dsc
 a4483820ab9b45089f73cd1265aa1659ddf7788e 669 
cgi-extratags-perl_0.03-1.2.diff.gz
 f19176a0a66b8a60b623a9b1432e8e058933df1c 7114 
libcgi-extratags-perl_0.03-1.2_all.deb
Checksums-Sha256:
 cdd957f4163e815366c35ddd4364b10c7151c1f852f03a4337941730114833a6 1745 
cgi-extratags-perl_0.03-1.2.dsc
 bb1391500ccb81e288646d5a744eb54579bd865f78bfe470f17d284c04a10451 669 
cgi-extratags-perl_0.03-1.2.diff.gz
 a91bbc3103c6f5d89d60c60cc69dd891aab940193490e1644bf7d22bfa9c 7114 
libcgi-extratags-perl_0.03-1.2_all.deb
Files:
 94e910e6d7b7051a13fc175f06c49dce 1745 interpreters optional 
cgi-extratags-perl_0.03-1.2.dsc
 78c5ec6be55d591848104599b4475af8 669 interpreters optional 
cgi-extratags-perl_0.03-1.2.diff.gz
 b6bbf0b110a2310efdef1d43b4f54458 7114 interpreters optional 
libcgi-extratags-perl_0.03-1.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV5qjkAAoJEHjX3vua1ZrxvlwQAKUBk1JikXjcXbDS5xt6+Jxo
64HqUq2oC4oircIQJzTvj3U9REv0yF0bNno3kCDbr5wGaC6SIBiDaUUbFbIQZLsy
nOuprqB+TRiIe5heFBVxEVBpXBVa6vEAbdT8BZTz4lEe8cPAyWhtTQmxZzplN7Nr
6CmOMdGUCJWKpZgDGtW9Vje4uU8kH2j/htj2UO662hESizwPoPuJasoSGm7aCqq2
SupMXGGkBfI5hslAxzSyeRVSAg6DD5xLgH6PJvOB3ZUe1BGrhPa2cMhNJV8TajYN
bS5xHu2VorFyPW/0bpTQCoqaAyJpd/wBYKxAx95fQHNqGHCpff7Wn+wB+TSmwF2+
Qp9wZEqHPPso4JxI/B5msVsTZBgBiKcDARhdHN8VUsyQ9wHTRgTexSgJv6Z9MM7t
wmKJyNKczONXOoBzjR0KN3+HwdLFXYOFd7V9AlarpfwpfDR3YxYN2y43P14S0Nze
tqJpMsxgl0SkATOljiQRXEnAptKscnBhhKs/4vw/+TJMQWGVks2oModpm+CPxTB9
EEZ7faB7jYr0M9wQJTSjVSqL8H/z1HYEzD+awCIN+44sLWyYeu6Tz21aGIMQ18m1
IUH7/vI6NEM5BhZyYQOonmrS1G9dK53r7L5HmblV1MEGyDHlq7RSaPEOhMliMPU3
uMgD9h6uAHDVXuE3hM8o
=TjmK
-END PGP SIGNATURE End Message ---

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Steve M. Robbins]

On September 2, 2015 10:55:01 AM you wrote:
> Source: insighttoolkit
> Version: 3.20.1+git20120521-6
> Severity: serious
> Justification: breaks ABI without a package rename
> Control: block -1 by 797738
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: libstdc++-cxx11
> 
> Background[1]: libstdc++6 introduces a new ABI to conform to the
> C++11 standard, but keeps the old ABI to not break existing binaries.
> Packages which are built with g++-5 from experimental (not the one
> from testing/unstable) are using the new ABI.  Libraries built from
> this source package export some of the new __cxx11 or B5cxx11 symbols,
> dropping other symbols.  If these symbols are part of the API of
> the library, then this rebuild with g++-5 will trigger a transition
> for the library.
> 
> In the case of insighttoolkit, std::string appears in installed headers,
> so it seems very likely that a transition is needed.

Do note that this packge is requested for removal (#795019) so there will be
no work done to transition it.

-Steve


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

Processed: fixed 797387 in 4.8.0-1

[Debian Bug Tracking System]

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

> fixed 797387 4.8.0-1
Bug #797387 [src:insighttoolkit4] insighttoolkit4: FTBFS (unsupported argument: 
--gccxml-gcc-options)
Marked as fixed in versions insighttoolkit4/4.8.0-1.
> thanks
Stopping processing here.

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

Bug#797257: marked as done (ruby-rack-protection: FTBFS: `block in expect_with': :stdlib is not supported (ArgumentError))

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 13:49:17 +
with message-id 
and subject line Bug#797257: fixed in ruby-rack-protection 1.5.3-2
has caused the Debian Bug report #797257,
regarding ruby-rack-protection: FTBFS: `block in expect_with': :stdlib is not 
supported (ArgumentError)
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.)


-- 
797257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack-protection
Version: 1.5.2-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:

┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/ruby-rack-protection-1.5.2/debian/ruby-rack-protection/usr/lib/ruby/vendor_ruby:.
 rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:656:in `block in 
expect_with': :stdlib is not supported (ArgumentError)
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:635:in `map'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:635:in 
`expect_with'
from /ruby-rack-protection-1.5.2/spec/spec_helper.rb:96:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from /ruby-rack-protection-1.5.2/spec/spec_helper.rb:95:in `'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /ruby-rack-protection-1.5.2/spec/authenticity_token_spec.rb:1:in 
`'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb 
failed
ERROR: Test "ruby2.1" failed. Exiting.

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

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

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated 
ruby-rack-protection 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, 02 Sep 2015 18:02:49 +0530
Source: ruby-rack-protection
Binary: ruby-rack-protection
Architecture: source all
Version: 1.5.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balasankar C 
Description:
 ruby-rack-protection - Protects against typical web attacks for Rack apps
Closes: 797257
Changes:
 ruby-rack-protection (1.5.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Port tests partially to RSpec3 and make them run (Closes: #797257)
Checksums-Sha1:
 

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Steve M. Robbins]

On September 2, 2015 01:33:35 PM Simon McVittie wrote:
> Control: tags 797755 + wontfix
> 
> On 02/09/15 13:05, Steve M. Robbins wrote:
> > On September 2, 2015 10:55:01 AM you wrote:
> >> In the case of insighttoolkit, std::string appears in installed headers,
> >> so it seems very likely that a transition is needed.
> > 
> > Do note that this packge is requested for removal (#795019) so there will
> > be no work done to transition it.
> 
> Marking this as wontfix on that basis.
> 
> However, I notice that the removal bug is marked moreinfo, because the
> ftp-masters will not remove insighttoolkit 3 while packages still depend
> on it, unless those packages are also removed. Please tell that bug how
> you plan to deal with this.

Well, insighttoolkit (v3) is also marked for autoremoval next week, so my plan 
is to let that happen -- and I presume the depending packages will also be 
removed at that time.

 
> Does insighttoolkit4 still have a C++ ABI involving std::string,
> std::list or other affected symbols? If it does, it will need a similar bug.

I haven't checked, but I will be conservative and assume it needs transition.  
I have already staged v4.8 in experimental for that purpose; see also #793250 
and #796561.

Apologies if I have gone about this the wrong way.


> Leaving insighttoolkit4 built with g++-4 is not a valid solution,

Agree.

-Steve


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

Bug#794359: marked as done (FTBFS: port tests to rspec 3 for updating to 1.5.2)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 13:35:28 +
with message-id 
and subject line Bug#794359: fixed in ruby-redis-namespace 1.5.2-2
has caused the Debian Bug report #794359,
regarding FTBFS: port tests to rspec 3 for updating to 1.5.2
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.)


-- 
794359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

package: ruby-redis-namespce
version: 1.4.1-2
severity: serious

log from pbuilder run with rspec 3, for 1.4.1-2

┌───
───┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
 │
└───
───┘

RUBYLIB=/tmp/buildd/ruby-redis-namespace-1.4.1/debian/ruby-redis-namespa
ce/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
...FFF...FFFF...
...

Failures:

  1) redis should be able to use a namespace with setbit
 Failure/Error: @namespaced.exists('virgin_key').should be_true
   expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
 # ./spec/redis_spec.rb:119:in `block (2 levels) in 
'

  2) redis should be able to use a namespace with mapped_msetnx
 Failure/Error: @namespaced.mapped_msetnx('foo'=>'1000',
'bar'=>'2000').should be_false
   expected false to respond to `false?` or perhaps you meant `be
false` or `be_falsey`
 # ./spec/redis_spec.rb:155:in `block (2 levels) in 
'

  3) redis should be able to use a namespace with hashes
 Failure/Error: @namespaced.hsetnx('foonx','nx',10).should be_true
   expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
 # ./spec/redis_spec.rb:176:in `block (2 levels) in 
'

  4) redis redis 2.6 commands should namespace bitcount FIXED
 Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
 # ./spec/redis_spec.rb:355

  5) redis redis 2.6 commands should namespace bitop FIXED
 Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
 # ./spec/redis_spec.rb:359

  6) redis redis 2.6 commands should namespace dump FIXED
 Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
 # ./spec/redis_spec.rb:363

  7) redis redis 2.6 commands should namespace restore FIXED
 Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
 # ./spec/redis_spec.rb:410

Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without
explicitly enabling the syntax is deprecated. Use the new `:expect`
syntax or explicitly enable `:should` with `config.expect_with(:rspec)
{ |c| c.syntax = :should }` instead. Called from
/tmp/buildd/ruby-redis-namespace-1.4.1/spec/redis_spec.rb:26:in `block
(2 levels) in '.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

1 deprecation warning total

Finished in 1.7 seconds (files took 1.83 seconds to load)
79 examples, 7 failures

Failed examples:

rspec ./spec/redis_spec.rb:117 # redis should be able to use a
namespace with setbit
rspec ./spec/redis_spec.rb:153 # redis should be able to use a
namespace with mapped_msetnx
rspec ./spec/redis_spec.rb:161 # redis should be able to use a
namespace with hashes
rspec ./spec/redis_spec.rb:355 # redis redis 2.6 commands should
namespace bitcount
rspec ./spec/redis_spec.rb:359 # redis redis 2.6 commands should
namespace bitop
rspec ./spec/redis_spec.rb:363 # redis redis 2.6 commands should
namespace dump
rspec ./spec/redis_spec.rb:410 # redis redis 2.6 commands should
namespace restore

/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-redis-namespace-1.4.1/debian/ruby-redis-namespace
returned exit code 1
debian/rules:23: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/tmp/buildd/ruby-redis-namespace-1.4.1'
debian/rules:15: recipe for target 'binary' 

Bug#794333: marked as done (cpl-plugin-naco-calib: fails to download naco-kit-4.4.0.tar.gz, does not exist)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 13:34:20 +
with message-id 
and subject line Bug#794333: fixed in cpl-plugin-naco 4.4.0+dfsg-2
has caused the Debian Bug report #794333,
regarding cpl-plugin-naco-calib: fails to download naco-kit-4.4.0.tar.gz, does 
not exist
to be marked as done.

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

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


-- 
794333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpl-plugin-naco-calib
Version: 4.4.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package cpl-plugin-naco-calib.
  (Reading database ... 
(Reading database ... 7758 files and directories currently installed.)
  Preparing to unpack .../cpl-plugin-naco-calib_4.4.0+dfsg-1_all.deb ...
  Unpacking cpl-plugin-naco-calib (4.4.0+dfsg-1) ...
  Setting up cpl-plugin-naco-calib (4.4.0+dfsg-1) ...
  --2015-08-01 07:47:48--  
ftp://ftp.eso.org/pub/dfs/pipelines/naco/naco-kit-4.4.0.tar.gz
 => '-'
  Resolving ftp.eso.org (ftp.eso.org)... 134.171.42.53, 134.171.42.54
  Connecting to ftp.eso.org (ftp.eso.org)|134.171.42.53|:21... connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /pub/dfs/pipelines/naco ... done.
  ==> SIZE naco-kit-4.4.0.tar.gz ... done.
  
  ==> PASV ... done.==> RETR naco-kit-4.4.0.tar.gz ... 
  No such file 'naco-kit-4.4.0.tar.gz'.
  
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  dpkg: error processing package cpl-plugin-naco-calib (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   cpl-plugin-naco-calib

There are naco-kit-4.4.0-1.tar.gz and naco-kit-4.4.0-3.tar.gz instead.


cheers,

Andreas


cpl-plugin-naco-calib_4.4.0+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-naco
Source-Version: 4.4.0+dfsg-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated cpl-plugin-naco 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, 02 Sep 2015 14:44:23 +0200
Source: cpl-plugin-naco
Binary: cpl-plugin-naco cpl-plugin-naco-doc cpl-plugin-naco-calib
Architecture: source all amd64
Version: 4.4.0+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Description:
 cpl-plugin-naco - ESO data reduction pipeline for the NaCo instrument
 cpl-plugin-naco-calib - ESO data reduction pipeline NaCo calibration data 
downloader
 cpl-plugin-naco-doc - ESO data reduction pipeline documentation for NaCo
Closes: 794333
Changes:
 cpl-plugin-naco (4.4.0+dfsg-2) unstable; urgency=low
 .
   * Reproducibly sort recipes in sphinx output.
   * Add simple CI test
   * Loop over all possible upstream package names when downloading
 calibration data
   * Adjust CPL library list for plugins. Closes: #794333
   * Fix FTBS for big endian (taken from cpl-plugin-fors)
   * Fix compilation problem on unstable/gcc5 (taken from cpl-plugin-fors)
Checksums-Sha1:
 c484402ebf49cdab3856db8c2edc5a43a02c8991 2348 cpl-plugin-naco_4.4.0+dfsg-2.dsc
 f5aa060bfe69048dfab3473b201f49d877a399fc 11804 
cpl-plugin-naco_4.4.0+dfsg-2.debian.tar.xz
 1bc8a7f89f1547cb0aa0764c6efd243beee49279 49418 
cpl-plugin-naco-calib_4.4.0+dfsg-2_all.deb
 

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Simon McVittie]

On 02/09/15 14:23, Steve M. Robbins wrote:
> Well, insighttoolkit (v3) is also marked for autoremoval next week, so my 
> plan 
> is to let that happen -- and I presume the depending packages will also be 
> removed at that time.

Autoremoval only removes packages from testing, and ftp-master removals
from unstable (unlike autoremovals from testing) are not normally
recursive. If you want the ftp-masters to remove reverse-dependencies
from unstable, someone needs to say so. For example, ogre-1.8 is another
C++ package in the same situation as insighttoolkit 3 ("this is obsolete
and the maintainer will not transition it, but things still depend on
it"). Neil Williams recently resolved that by asking the ftp-masters to
remove the remaining reverse-dependencies of ogre-1.8 from unstable.

Any C++ library in unstable that uses one of the affected features
(std::string, std::list, possibly std::function) will break its ABI when
rebuilt with g++-5, and all packages depending on affected libraries
need rebuilding; so all such libraries are part of the wider libstdc++
transition, even if they are RC-buggy or not present in testing. I think
non-rebuilt libraries might also prevent the old binary packages on
which they depend from being "decrufted" without manual intervention,
although I could be wrong.

How long ago were maintainers of packages depending on insighttoolkit 3
told that it was obsolete and going to be removed?

> I haven't checked, but I will be conservative and assume it needs transition. 
>  
> I have already staged v4.8 in experimental for that purpose; see also #793250 
> and #796561.

Thanks, I've noted those on the Titanpad. I will not open a separate bug
here, since #796561 can act as the tracking bug.

S

Processed: Please delete snappy1.0.3-java from Debian [Was: Bug#796917: snappy1.0.3-java: dependency on libsnappy1]

[Debian Bug Tracking System]

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

> reassign 796917 ftp.debian.org
Bug #796917 [src:snappy1.0.3-java] snappy1.0.3-java: dependency on libsnappy1
Bug reassigned from package 'src:snappy1.0.3-java' to 'ftp.debian.org'.
No longer marked as found in versions snappy1.0.3-java/1.0.3-rc3~dfsg-5.
Ignoring request to alter fixed versions of bug #796917 to the same values 
previously set
> retitle 796917 ROM: Please remove snappy1.0.3-java from unstable and testing
Bug #796917 [ftp.debian.org] snappy1.0.3-java: dependency on libsnappy1
Changed Bug title to 'ROM: Please remove snappy1.0.3-java from unstable and 
testing' from 'snappy1.0.3-java: dependency on libsnappy1'
> thanks
Stopping processing here.

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

Bug#793582: marked as done (FTBFS: geronimo/mail/Activator.java: error: package org.apache.geronimo.osgi.locator does not exist)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 09:49:55 +
with message-id 
and subject line Bug#793582: fixed in geronimo-javamail-1.4-spec 1.7.1-3
has caused the Debian Bug report #793582,
regarding FTBFS: geronimo/mail/Activator.java: error: package 
org.apache.geronimo.osgi.locator does not exist
to be marked as done.

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

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


-- 
793582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geronimo-javamail-1.4-spec
Version: 1.7.1-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build:


Get: 160 http://ftp.de.debian.org/debian/ unstable/main 
libgeronimo-osgi-support-java all 1.1-1 [22.6 kB]
Get: 161 http://ftp.de.debian.org/debian/ unstable/main 
libgeronimo-jpa-2.0-spec-java all 1.1-2 [81.0 kB]

[javac] 
/geronimo-javamail-1.4-spec-1.7.1/src/main/java/javax/mail/Session.java:43: 
error: package org.apache.geronimo.osgi.locator does not exist
[javac] import org.apache.geronimo.osgi.locator.ProviderLocator;
[javac]^
[javac] 
/geronimo-javamail-1.4-spec-1.7.1/src/main/java/org/apache/geronimo/mail/Activator.java:41:
 error: package org.apache.geronimo.osgi.locator does not exist
[javac] public class Activator extends 
org.apache.geronimo.osgi.locator.Activator {
[javac]^
[javac] 
/geronimo-javamail-1.4-spec-1.7.1/src/main/java/javax/mail/Session.java:492: 
error: cannot find symbol
[javac] clazz = 
ProviderLocator.loadClass(provider.getClassName(), this.getClass(), cl);


Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/geronimo-javamail-1.4-spec.html

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: geronimo-javamail-1.4-spec
Source-Version: 1.7.1-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
geronimo-javamail-1.4-spec 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, 02 Sep 2015 11:37:48 +0200
Source: geronimo-javamail-1.4-spec
Binary: libgeronimo-javamail-1.4-spec-java
Architecture: source all
Version: 1.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libgeronimo-javamail-1.4-spec-java - Geronimo API implementation of the 
JavaMail 1.4 spec
Closes: 793582
Changes:
 geronimo-javamail-1.4-spec (1.7.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build error caused by the geronimo-osgi-support update
 (Closes: #793582)
   * debian/control:
 - Standards-Version updated to 3.9.6 (no changes)
 - Use canonical URLs for the Vcs-* fields
 - Removed the deprecated DMUA flag
   * Switch to debhelper level 9
Checksums-Sha1:
 1637878b0e86a2d644ebe6c9187f29ad4f239e1e 2182 
geronimo-javamail-1.4-spec_1.7.1-3.dsc
 abef53b3eddbfb8a6142570227171f6a8a1ea37c 3324 
geronimo-javamail-1.4-spec_1.7.1-3.debian.tar.xz
 2aa78ac2101e0ac52e73b4bc1e8de4edd4036863 190168 
libgeronimo-javamail-1.4-spec-java_1.7.1-3_all.deb
Checksums-Sha256:
 e52493085173740073e6520006c356367cf30925d264eb53d7a7c9c952acdca2 2182 
geronimo-javamail-1.4-spec_1.7.1-3.dsc
 46f86679198d40cd878e72034d16b9c97551965934c380e64159aab64de1fee5 3324 
geronimo-javamail-1.4-spec_1.7.1-3.debian.tar.xz
 

Bug#797227: segfault - gst_memory_unmap, libgstreamer

[Sebastian Dröge]

On Mi, 2015-09-02 at 17:32 +0900, Changwoo Ryu wrote:
> Yes, I just have tested the patch on faad plugin at the GNOME 
> bugzilla 748571. And it fixes the problem.

Thanks for testing, question is if I should upload a new package with
the fix to unstable or we just wait until 1.6.0 is released... which
should happen in the next week or two.

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

Bug#793582: FTBFS: geronimo/mail/Activator.java: error: package org.apache.geronimo.osgi.locator does not exist

[Emmanuel Bourg]

Le 07/08/2015 22:38, Hans Joachim Desserud a écrit :

> I looked into this, and have attached a patch which makes the package
> build successfully.

Hi Hans,

Thank you for the patch. I've uploaded a slightly different fix, using
the unversioned jar allows to build with any version of
geronimo-osgi-support.


> To the person reviewing this: the 1.0 version is also mentioned in
> the pom.xml, and it is possible this should be updated also.
> However, the svn repo seemd to only contain the debian directory
> and I wasn't sure what would be best practice when patching it.

When the pom is installed the versions of the dependencies are
substituted by following the rules defined in debian/maven.rules. In
this case '1.0' is turned into 'debian' and matches the version
installed by libgeronimo-osgi-support-java which is also 'debian'. So
there is nothing to change here.

Emmanuel Bourg

Bug#738399: marked as done (libgroboutils-java: FTBFS: compile failed)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 09:34:58 +
with message-id 
and subject line Bug#738399: fixed in libgroboutils-java 5-3
has caused the Debian Bug report #738399,
regarding libgroboutils-java: FTBFS: compile failed
to be marked as done.

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

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


-- 
738399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgroboutils-java
Version: 5-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> cd . && /usr/lib/jvm/default-java/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/groboutils-testingautodoc-core.jar:/usr/share/java/groboutils-codecoverage-runtime.jar:/usr/share/java/groboutils-codecoverage-core.jar:/usr/share/java/groboutils-codecoverage-ant.jar:/usr/share/java/groboutils-classes-core.jar:/usr/share/java/junit.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/easymock.jar:/usr/share/java/bcel.jar:/usr/share/java/ant-apache-bcel.jar:/usr/share/java/ant-junit.jar:/usr/lib/jvm/default-java/lib/tools.jar
>   -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
> -Dcompile.optimize=true-propertyfile /«PKGBUILDDIR»/debian/ant.properties 
> main
> Buildfile: /«PKGBUILDDIR»/build.xml
> 
> main:
> 
> _shared.common.depend.jdk-checker:
> 
> check-grobo.autodoc.check:
> 
> check-grobo.autodoc.compile:
> 
> check-grobo.autodoc:
> 
> bootstrap-check:
> 
> check-ant.optional:
> 
> init:
> 
> testing-junit:
> 
> _shared.common.probe-offline:
> 
> _shared.common.depend.jdk-checker:
> 
> _shared.common.init:
>  [echo] 
>  [echo]   **
>  [echo]   Start of Compilation for groboutils-testingjunit-1.2.1
>  [echo]   **
>  [echo] 
>  [echo] Java classpath = 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/groboutils-testingautodoc-core.jar:/usr/share/java/groboutils-codecoverage-runtime.jar:/usr/share/java/groboutils-codecoverage-core.jar:/usr/share/java/groboutils-codecoverage-ant.jar:/usr/share/java/groboutils-classes-core.jar:/usr/share/java/junit.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/easymock.jar:/usr/share/java/bcel.jar:/usr/share/java/ant-apache-bcel.jar:/usr/share/java/ant-junit.jar:/usr/lib/jvm/default-java/lib/tools.jar
> 
> init:
> 
> _shared.common.depend.jdk.1_1:
> 
> javac-checkDependencies:
> 
> _shared.common.javac-dev:
> [mkdir] Created dir: /«PKGBUILDDIR»/testing-junit/work/classes/dev
> [javac] 
> /«PKGBUILDDIR»/_shared/common-ant/common-ant-tasks-javac.ant-inc.xml:18: 
> warning: 'includeantruntime' was not set, defaulting to 
> build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 20 source files to 
> /«PKGBUILDDIR»/testing-junit/work/classes/dev
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.4
> [javac] 
> /«PKGBUILDDIR»/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/SubTestTestCase.java:156:
>  warning: as of release 5, 'enum' is a keyword, and may not be used as an 
> identifier
> [javac] Enumeration enum = list.elements();
> [javac] ^
> [javac]   (use -source 5 or higher to use 'enum' as a keyword)
> [javac] 
> /«PKGBUILDDIR»/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/SubTestTestCase.java:157:
>  warning: as of release 5, 'enum' is a keyword, and may not be used as an 
> identifier
> [javac] while (enum.hasMoreElements())
> [javac]^
> [javac]   (use -source 5 or higher to use 'enum' as a keyword)
> [javac] 
> /«PKGBUILDDIR»/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/SubTestTestCase.java:159:
>  warning: as of release 5, 'enum' is a keyword, and may not be used as an 
> identifier
> [javac] Test test = (Test)enum.nextElement();
> [javac]   ^
> [javac]   (use -source 5 or higher to use 'enum' as a keyword)
> [javac] 
> /«PKGBUILDDIR»/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/iftc/InterfaceTestSuite.java:201:
>  warning: as of 

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: insighttoolkit
Version: 3.20.1+git20120521-6
Severity: serious
Justification: breaks ABI without a package rename
Control: block -1 by 797738
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of insighttoolkit, std::string appears in installed headers,
so it seems very likely that a transition is needed.
The transition consists of renaming the affected library packages, adding a
v5 suffix (libinsighttoolkit3.20v5). The SONAME should not be changed.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

In the case of insighttoolkit, vtk has started its transition already,
but gdcm has not (#797738), so you will have to wait for that.

The package is likely to be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#797756: lhapdf: ABI transition needed for libstdc++ v5

[Simon McVittie]

Source: lhapdf
Version: 5.9.1-3.1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of lhapdf, std::string appears in installed headers,
so it seems very likely that a transition is needed.

The transition normally consists of renaming the affected library packages,
adding a v5 suffix (liblhapdf0v5). The SONAME should not be changed.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of lhapdf, it might need to wait
for octave, which doesn't have a bug open yet. Everything else seems
fine.

The package is likely to be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Andreas Tille]

Hi Simon,

On Wed, Sep 02, 2015 at 10:55:01AM +0100, Simon McVittie wrote:
> ...
> The package is likely to be NMU'd if there is no maintainer response. The
> release team have declared a 2 day NMU delay[2] for packages involved
> in the libstdc++ transition, in order to get unstable back to a usable
> state in a finite time.

The Debian Med team is on the LowThresholdNmu list[1] so feel free to to
zero delay NMU if nobody from the team is able to beat you (also for
gdcm transition).

Thanks for your work on the transition

   Andreas.

[1] https://wiki.debian.org/LowThresholdNmu

-- 
http://fam-tille.de

Bug#797623: Bug#797625: xmltooling: transition needed for g++-5 ABIs

[Simon McVittie]

On 01/09/15 17:50, Russ Allbery wrote:
> Ferenc Wagner  writes:
>> Anyway, feel free to NMU these packages if that helps
>> unblocking other stuff, just don't be too concerned about the fate of
>> the current versions in unstable, expect new upstream versions after a
>> couple of weeks.
> 
> If you're changing the SONAME anyway, you don't have to do the renaming
> described here.  That's actually an even cleaner solution.

Yes, if the new SONAME is uploaded before the v5 rename, and the new
SONAME compiled with gcc < 5 has never been in Debian, then it makes the
v5 rename unnecessary.

I'm not sure how "a couple of weeks" is going to compare with the point
at which this transition becomes part of the critical path. I'll leave
the Shib stack alone for now, but I'll come back to this and NMU with
the "v5" names if it becomes a blocker for the C++ Transition of
Despair, because this process has taken long enough already.

S

Bug#796917: snappy1.0.3-java: dependency on libsnappy1

[Gianfranco Costamagna]

Hi Andreas,


> libsnappy1 is being replaced by libsnappy1v5.
>  Your arch:all package has

>a hardcoded dependency on the former (how does that even work?).>
>
>Before I simply add a hardcoded libsnappy1v5 I would like to ask for
>comments whether there is some better way to solve this.


Well, I'm not a java expert, but in general this approach is wrong.

however snappy-java code seems smart enough to understand where to find the 
library
at runtime (this isn't a build-time dependency, but a runtime one) and use it.


I'm not sure there is a smarter approach, to let shlibs to its job, because 
snappy is
used as a plugin in this particular case, so hardcoding the libsnappy1v5 might 
be
the best way to do the trick.

Did you try if the package works on different architectures?

cheers,

G.

Bug#797387: insighttoolkit4: FTBFS (unsupported argument: --gccxml-gcc-options)

[Steve M. Robbins]

Thanks.  The problem is known and fixed in 4.8.0 -- presently in experimental. 

-Steve


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

Bug#797264: marked as done (wagon: FTBFS: Missing: org.apache.maven.wagon:wagon-provider-test:jar:debian)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 12:19:45 +
with message-id 
and subject line Bug#797264: fixed in wagon 1.0.0-7
has caused the Debian Bug report #797264,
regarding wagon: FTBFS: Missing: 
org.apache.maven.wagon:wagon-provider-test:jar:debian
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.)


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

[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.maven.wagon:wagon-provider-test:jar:debian

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.maven.wagon 
-DartifactId=wagon-provider-test -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.maven.wagon 
-DartifactId=wagon-provider-test -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.maven.wagon:wagon-file:jar:1.0
2) org.apache.maven.wagon:wagon-provider-test:jar:debian

--
1 required artifact is missing.

for artifact: 
  org.apache.maven.wagon:wagon-file:jar:1.0

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated wagon 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, 02 Sep 2015 14:06:48 +0200
Source: wagon
Binary: libwagon-java libwagon-java-doc
Architecture: source all
Version: 1.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libwagon-java - tools to manage Maven artifacts and deployment
 libwagon-java-doc - tools to manage Maven artifacts and deployment - 
documentation
Closes: 797264
Changes:
 wagon (1.0.0-7) unstable; urgency=medium
 .
   * Team upload.
   * Ignore the dependency on wagon-provider-test (Closes: #797264)
Checksums-Sha1:
 c2f00bc7c23f0b1c67b1f9976461cfab6bc0f812 2786 wagon_1.0.0-7.dsc
 0d54df09e221f3cc509b4ca755c93288edc5600a 13156 wagon_1.0.0-7.debian.tar.xz
 6bf7d7e8fb2b03abd1bb02c24258bc3a2b61b800 682060 
libwagon-java-doc_1.0.0-7_all.deb
 9412cafaf299e4989d74475f7ac5d8808ba45ba2 133012 libwagon-java_1.0.0-7_all.deb
Checksums-Sha256:
 1155081b84a1b653811ceb1c92f573291066362a2f5aae4634d423f9d5420209 2786 
wagon_1.0.0-7.dsc
 f7211eb71efd95a7f3b7a890141fa6bd69546ea3c6f393ec58323ae527435df7 13156 
wagon_1.0.0-7.debian.tar.xz
 804fca33d390a65433f327135d34f1675e98d0d61dbb40377b5e39b925d8bd50 682060 
libwagon-java-doc_1.0.0-7_all.deb
 cb661c24c88e59a766b8b4c6aeca9264b7626955f2311dcc05b2f5a6ae3e8eb8 133012 
libwagon-java_1.0.0-7_all.deb
Files:
 a5967fab0fdb2d3123319b6f4011b0a4 2786 java optional wagon_1.0.0-7.dsc
 339c86595013697698e51c45249162dc 13156 java optional 
wagon_1.0.0-7.debian.tar.xz
 da0de8ff51eb3c0127bdee9c637530db 682060 doc optional 
libwagon-java-doc_1.0.0-7_all.deb
 93c849226c163b7110d7009062cb33aa 133012 java optional 
libwagon-java_1.0.0-7_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

Processed: severity of 797721 is serious

[Debian Bug Tracking System]

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

> # Maintainer's opinion. Should not migrate to testing with that. Won't 
> anyways, but still.
> severity 797721 serious
Bug #797721 [zsh] zsh frozen with zombie child due to the use of TRAPCHLD
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#797777: ntopng: Missing Build-Depends on pkg-config

[Chris Lamb]

Source: ntopng
Version: 1.2.1+dfsg1-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
Tags: patch

Dear Maintainer,

ntopng fails to build from source in unstable/amd64 due to missing
Build-Depends on pkg-config:

  [..]
  dh_auto_build
make -j1
  make[2]: Entering directory '/tmp/buildd/ntopng-1.2.1+dfsg1'
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  /bin/sh: 1: pkg-config: not found
  svn co https://svn.ntop.org/svn/ntop/trunk/nDPI/
  make[2]: svn: Command not found
  Makefile:136: recipe for target 'nDPI' failed
  make[2]: *** [nDPI] Error 127
  make[2]: Leaving directory '/tmp/buildd/ntopng-1.2.1+dfsg1'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:13: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/tmp/buildd/ntopng-1.2.1+dfsg1'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ntopng_1.2.1+dfsg1-2.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Tue Sep  1 08:04:44 GMT+12 2015
I: pbuilder-time-stamp: 1441137884
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9.0.0), dh-autoreconf, dh-systemd (>= 1.5), dpkg (>= 
1.15.7.2), coffeescript, libgeoip-dev, libhiredis-dev, libjson-c-dev, 
libluajit-5.1-dev, libndpi-dev (>= 1.4.0+svn8032), libpcap-dev, librrd-dev, 
libsqlite3-dev, libzmq3-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20255 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on dh-autoreconf; however:
  Package dh-autoreconf is not installed.
 pbuilder-satisfydepends-dummy depends on dh-systemd (>= 1.5); however:
  Package dh-systemd is not installed.
 pbuilder-satisfydepends-dummy depends on coffeescript; however:
  Package coffeescript is not installed.
 pbuilder-satisfydepends-dummy depends on libgeoip-dev; however:
  Package libgeoip-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libhiredis-dev; however:
  Package libhiredis-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libjson-c-dev; however:
  Package libjson-c-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libluajit-5.1-dev; however:
  Package libluajit-5.1-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libndpi-dev (>= 1.4.0+svn8032); 
however:
  Package libndpi-dev is not installed.
 pbuilder-satisfydepends-dummy depends on 
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
  autoconf{a} automake{a} autopoint{a} autotools-dev{a} coffeescript{a} 
  dh-autoreconf{a} dh-systemd{a} fontconfig{a} fontconfig-config{a} 
  fonts-dejavu-core{a} geoip-bin{a} libc-ares2{a} libcairo2{a} 
  libdatrie1{a} libdbi1{a} libexpat1{a} libfontconfig1{a} libfreetype6{a} 
  libgeoip-dev{a} libgeoip1{a} libgraphite2-3{a} libharfbuzz0b{a} 
  libhiredis-dev{a} 

Bug#797776: pygpgme: FTBFS: Ran 55 tests in 54.866s: FAILED (failures=2, errors=2)

[Chris Lamb]

Source: pygpgme
Version: 0.3-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,

pygpgme fails to build from source in unstable/amd64:

  [..]
 
  ==
  ERROR: test_sign_with_passphrase_cb
  (tests.test_passphrase.PassphraseTestCase)
  --
  Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_passphrase.py", line 60, in
test_sign_with_passphrase_cb
  key = ctx.get_key('EFB052B4230BBBC51914BCBB54DCBBC8DBFB9EB3')
  GpgmeError: (7, 16383, u'End of file')
  
  ==
  ERROR: test_sign_without_passphrase_cb
  (tests.test_passphrase.PassphraseTestCase)
  --
  Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_passphrase.py", line 37, in
test_sign_without_passphrase_cb
  key = ctx.get_key('EFB052B4230BBBC51914BCBB54DCBBC8DBFB9EB3')
  GpgmeError: (7, 16383, u'End of file')
  
  ==
  FAIL: test_import_concat (tests.test_import.ImportTestCase)
  --
  Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_import.py", line 105, in
test_import_concat
  self.assertEqual(result.considered, 3)
  AssertionError: 5 != 3
  
  ==
  FAIL: test_import_secret_file (tests.test_import.ImportTestCase)
  --
  Traceback (most recent call last):
File "/tmp/buildd/pygpgme-0.3/tests/test_import.py", line 58, in
test_import_secret_file
  self.assertEqual(result.considered, 1)
  AssertionError: 3 != 1
  
  --
  Ran 55 tests in 54.866s
  
  FAILED (failures=2, errors=2)
  Makefile:7: recipe for target 'check' failed
  make[2]: *** [check] Error 1
  make[2]: Leaving directory '/tmp/buildd/pygpgme-0.3'
  debian/rules:27: recipe for target 'test-python2.7' failed
  make[1]: *** [test-python2.7] Error 2
  make[1]: Leaving directory '/tmp/buildd/pygpgme-0.3'
  debian/rules:64: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/pygpgme_0.3-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Wed Sep  2 00:06:14 GMT+12 2015
I: pbuilder-time-stamp: 1441195574
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 8.1.0~), python-all-dev (>= 2.6.6-3~), python3-all-dev, 
libgpgme11-dev, python-all-dbg (>= 2.6.6-3~), python3-all-dbg, gnupg
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20255 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on python-all-dev (>= 2.6.6-3~); however:
  Package python-all-dev is not installed.
 pbuilder-satisfydepends-dummy depends on python3-all-dev; however:
  Package python3-all-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libgpgme11-dev; however:
  Package libgpgme11-dev is not installed.
 pbuilder-satisfydepends-dummy depends on python-all-dbg (>= 

Bug#795123: marked as done (ruby-warden: FTBFS: rspec3 port(?): undefined method `have' for #<RSpec...)

[Debian Bug Tracking System]

Your message dated Wed, 02 Sep 2015 13:19:25 +
with message-id 
and subject line Bug#795123: fixed in ruby-warden 1.2.3-2
has caused the Debian Bug report #795123,
regarding ruby-warden: FTBFS: rspec3 port(?): undefined method `have' for 
#http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-warden
Version: 1.2.3-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:

Failures:

  1) Warden::Config should allow to silence missing strategies
 Failure/Error: @config.silence_missing_strategies?.should be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/warden/config_spec.rb:29:in `block (2 levels) in '

  2) standard authentication hooks after_set_user should allow me to add an 
after_set_user hook
 Failure/Error: RAM._after_set_user.should have(1).item
 NoMethodError:
   undefined method `have' for 
#
 # ./spec/warden/hooks_spec.rb:24:in `block (3 levels) in '

  3) standard authentication hooks after_set_user should allow me to add 
multiple after_set_user hooks
 Failure/Error: RAM._after_set_user.should have(2).items
 NoMethodError:
   undefined method `have' for 
#
 # ./spec/warden/hooks_spec.rb:30:in `block (3 levels) in '

  4) standard authentication hooks after_set_user after_authentication should 
allow me to log out a user in an after_set_user block
 Failure/Error: env['warden'].authenticated?.should be_false
   expected false to respond to `false?` or perhaps you meant `be false` or 
`be_falsey`
 # ./spec/warden/hooks_spec.rb:130:in `block (4 levels) in '

...

215 examples, 14 failures

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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: ruby-warden
Source-Version: 1.2.3-2

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated ruby-warden 
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, 02 Sep 2015 12:18:15 +0530
Source: ruby-warden
Binary: ruby-warden
Architecture: source all
Version: 1.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balasankar C 
Description:
 ruby-warden - Rack middleware that provides authentication for rack application
Closes: 795123
Changes:
 ruby-warden (1.2.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Add rspec3-port.patch (Closes: #795123)
 - Ports the tests to support RSpec3 syntax
   * Bump Standards Version to 3.9.6 (no changes)
Checksums-Sha1:
 9f64dc02cc3284c615822422db3dc8d4a89fa8ab 2045 ruby-warden_1.2.3-2.dsc
 8d14241c6a2be462c4ca4c1d45833d563884c4ce 12980 
ruby-warden_1.2.3-2.debian.tar.xz
 d3977469b17d28f1a7f90bd6509566627e368e33 16204 ruby-warden_1.2.3-2_all.deb
Checksums-Sha256:
 4b4454f15a641b2a643380ce174a3e6a8ccd0e4fa01d115c197e9025c529f369 2045 
ruby-warden_1.2.3-2.dsc
 90df37546b96b8ba5c246cc1290ee5baf3b12b8bca436f233817efc28e02f207 12980 
ruby-warden_1.2.3-2.debian.tar.xz
 ecec857bbd32e13247e98530123eddaac898abcc0196269c5bc1da237185d4d4 16204 
ruby-warden_1.2.3-2_all.deb
Files:
 8bdd12da2fd098b03c76cc253b792ad3 2045 ruby optional ruby-warden_1.2.3-2.dsc
 1d06a0947c2b779f86cd2ae570efcf05 12980 ruby optional 
ruby-warden_1.2.3-2.debian.tar.xz
 ad16f7af6e4cb4860380040e2189e6eb 16204 ruby optional 
ruby-warden_1.2.3-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV5vZLAAoJEM4fnGdFEsIqYZUQAJPRZoxLIpHebAx+D6+gJ4Dl
kKWgKH9PHFXADLTg87Y0n0RcKmXX7wxegM3ELxLXvOpClaWgJh2g8jEsuU3oQ8cH
9J5F++zfGe6MW5rXFKSZya14tUd3rk/uTf5GnKlJuDyZAELYlw4khgOBpNJ8EJJI

Processed: Re: h5py: FTBFS - Broken test: test_file.py

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #797476 [src:h5py] h5py: FTBFS - Broken test: test_file.py
Severity set to 'normal' from 'serious'

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

Bug#797476: h5py: FTBFS - Broken test: test_file.py

[Gilles Filippini]

Control: severity -1 normal

Hi,

On Mon, 31 Aug 2015 00:06:23 +0200 Gilles Filippini  wrote:
> h5py now FTBFS because of a broken test:
> 
> ==
> FAIL: test_default (h5py.tests.old.test_file.TestFileOpen)
> Default semantics in the presence or absence of a file
> --
> Traceback (most recent call last):
>   File "h5py/tests/old/test_file.py", line 48, in test_default
> self.assertEqual(f.mode, 'r')
> AssertionError: 'r+' != 'r'
> 
> This is upstream issue 554:
> 

Downgrading severity to 'normal' because I couldn't reproduce this FTBFS
on another box with a clean sid + libhdf5-1.8.15 chroot.

For the record, the previous FTBFS is reproducible on debomatic-amd64 [1].

[1]


Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Debian Bug Tracking System]

Processing control commands:

> tags 797755 + wontfix
Bug #797755 [src:insighttoolkit] insighttoolkit: ABI transition needed for 
libstdc++ v5
Added tag(s) wontfix.

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

Bug#797770: shibboleth-sp2: library transition needed with GCC 5 as default

[Julien Cristau]

Source: shibboleth-sp2
Version: 2.5.3+dfsg-2.1
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

your library exposes std::string or std::list in its public API, and
therefore the library package needs to be renamed.

Cheers,
Julien

The following is a form letter:

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 are using the new ABI.  Libraries built
from this source package export some of the new __cxx11 or B5cxx11 symbols, and
dropping other symbols.  If these symbols are part of the API of the library,
then this rebuild with g++-5 will trigger a transition for the library.

What is needed:

 - Rebuild the library using g++/g++-5. Note that most likely all C++
   libraries within the build dependencies need a rebuild too. You can
   find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150813/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition



signature.asc
Description: Digital signature

Bug#796917: snappy1.0.3-java: dependency on libsnappy1

[Andreas Tille]

Hi Emmanuel,

On Wed, Sep 02, 2015 at 12:54:57PM +0200, Emmanuel Bourg wrote:
> I'm not sure snappy1.0.3-java even works. The native part isn't compiled
> (the SnappyNative.h and SnappyNative.c files in
> src/main/java/org/xerial/snappy). So the libsnappy1 dependency is bogus
> and could be removed.
> 
> I suggest removing snappy1.0.3-java and use snappy-java instead. This
> one is known to work. picard-tools is the only reverse dependency of
> libsnappy1.0.3-java, I'll prepare an update.

Cool. Thanks a lot for your upload and the commits to Git!
I'll go on ask ftpmaster for removal of snappy1.0.3-java which
should be unneeded now.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#797755: insighttoolkit: ABI transition needed for libstdc++ v5

[Simon McVittie]

Control: tags 797755 + wontfix

On 02/09/15 13:05, Steve M. Robbins wrote:
> On September 2, 2015 10:55:01 AM you wrote:
>> In the case of insighttoolkit, std::string appears in installed headers,
>> so it seems very likely that a transition is needed.
> 
> Do note that this packge is requested for removal (#795019) so there will be
> no work done to transition it.

Marking this as wontfix on that basis.

However, I notice that the removal bug is marked moreinfo, because the
ftp-masters will not remove insighttoolkit 3 while packages still depend
on it, unless those packages are also removed. Please tell that bug how
you plan to deal with this.

Does insighttoolkit4 still have a C++ ABI involving std::string,
std::list or other affected symbols? If it does, it will need a similar bug.

The transition can be done either by moving from one SONAME to another
(libinsighttoolkit4.7 -> libinsighttoolkit4.8), or by adding a v5 suffix
to 4.7. The people who have already spent a month fighting with this
transition would really prefer the short-term answer to be "whichever is
quicker and lower-risk", which seems likely to be the v5 suffix; you can
still do the 4.7 -> 4.8 transition later, after unstable is a usable
suite for development again.

Leaving insighttoolkit4 built with g++-4 is not a valid solution,
because it already needs to be rebuilt with g++-5 for the dcmtk2v5
sub-transition (although it FTBFS right now - I'll open a bug).

S

Bug#797729: marked as done (debian-maintainers: security not taken seriously)

[Debian Bug Tracking System]

Your message dated Wed, 2 Sep 2015 16:15:06 +0200
with message-id <20150902141506.ga11...@enricozini.org>
and subject line Re: Bug#797729: information
has caused the Debian Bug report #797729,
regarding debian-maintainers: security not taken seriously
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.)


-- 
797729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-maintainers
Severity: critical
Tags: upstream security
Justification: root security hole


Oh, lookie another bug report by ME. Gonna close it? DO SO AT YOUR OWN PERIL.

This entire week has a SLEW of bug closures(started from me), and I can guess
why.

1) Yall maintainers are too damn lazy (YAWN)
2) You REALLY DONT GIVE A SHIT about SECURITY (Lying to people? HMMM...)
3) You think that these are not issues OR are beyond scope to fix (nothing is)

LET ME put you all straight AGAIN.
Security is PROACTIVE, not an afterthought.

You are either ahead of the curve, or falling behind. 1 or a 0.

Not only have I told you were the ISSUES are, I ALSO have proposed
RESOLUTIONS.Certainly some things take time to fix, but REFUSING to PROCEED has
more consequences than you know.

Im not here to bash people into another language. Conversion is optional. BUT
IT IS MY DUTY to report where and why other languages SUPERSEDE and EXCEED
C.(And (Free)PASCAL does that very well)

I dont give a R-A if you like me, or what I have to say.Its backed by years of
programming experience, not OPINION.Dont think youre getting rid of me THAT
EASY.

Before you go hitting the whack-a-mole reply all or delete or close button,
know this.

REDHAT knows what Im talking about. They are making DRASTIC code compile
changes with Fedora 23.If I were you, Id try and figure out what they are
changing and why.Theyre obviously doing it for some reason.Then Id try and
implement these changes myself.

Non-free devs know you dont have the source code.Just let them know about the
issue so they can fix it.It is up to the rest of yall to fix the FREE stuff.
You have the sources. YOU HAVE the MAKEFILES. YOU CAN FIX IT.

Buggy apps like mupen64 are expected to be dropped until the programmer fixes
the SLOPPY code.It stack smashes.NO, its NOT SUPPOSED TO.Until it gets FIXED,
its SLOP.

But then again, you never bothered to check for things like that, did you? More
than likely, NOT.

So go ahead.Close me. Embarass yourself further. I REALLY could care less. But
the world will know that at least I gave a SHIT enough to warn you.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Wed, Sep 02, 2015 at 09:13:56AM +0300, Henri Salo wrote:

> Communication is important key to get changes to Debian. I am replying to this

Thanks Henri for being a wonderful example of it <3

Richard, "debian-maintainer" is the virtual package used to track issues
related to the workflow of getting Debian Maintainer status (see
https://wiki.debian.org/DebianMaintainer), so I am going to close this
bug because it does not fit here, and it lacks enough information to be
just reassigned to the 'general' virtual package.

If you have general complaints about Debian, you can send mail to the
debian-project list (https://lists.debian.org/debian-project/).

If you want to raise a general issue that you would like to be tracked,
you can report it against the "general" virtual package
(https://bugs.debian.org/general), and please be specific about what
your issue is, or there will be little that people can do to help.


Enrico

-- 
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini --- End Message ---