Bug#797793: samtools update seems to breaks even more tests

[Andreas Tille]

Hi,

other uploaders of pysam in CC: When building htseq with current pysam
in unstable I get:

...
All 26 tests passed.

Doctest of tss.rst:
**
File "../doc/tss.rst", line 211, in tss.rst
Failed example:
for almnt in sortedbamfile[ window ]:
print almnt   #doctest:+ELLIPSIS +NORMALIZE_WHITESPACE
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
for almnt in sortedbamfile[ window ]:
  File "/build/htseq-0.6.1p1/build/lib.linux-x86_64-2.7/HTSeq/__init__.py", 
line 976, in __getitem__
if not self.sf._hasIndex():
AttributeError: 'pysam.csamfile.Samfile' object has no attribute '_hasIndex'
**
File "../doc/tss.rst", line 220, in tss.rst
Failed example:
almnt.iv.length = fragmentsize
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
almnt.iv.length = fragmentsize
AttributeError: 'NoneType' object has no attribute 'length'
**
File "../doc/tss.rst", line 221, in tss.rst
Failed example:
almnt
Expected:

Got:


...

NameError: name 'start_in_window' is not defined
**
1 items had failures:
   6 of  37 in tss.rst
***Test Failed*** 6 failures.
6 of 37 tests failed.


Any idea how to fix this.  Htslib upstream is unresponsive even to less
hard issues.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

[Sebastian Dröge]

On Sa, 2015-12-05 at 16:28 +0100, Soeren D. Schulze wrote:
> Am 12.11.2015 um 15:02 schrieb Sebastian Dröge:
> > On Do, 2015-11-12 at 14:41 +0100, Soeren D. Schulze wrote:
> > > Hello,
> > > 
> > > the problem does not seem to occur any more with
> > > gstreamer1.0-plugins-bad 1.6.1-1+b1 and iceweasel 38.4.0esr-1.
> > > 
> > > Do you have any specific packages for me to test?
> > 
> > Just a normal jessie installation without installing things from
> > other sources, including sid :) It is definitely fixed since gst-
> > plugins-bad 1.5.X, it's just not clear if the actual bug also
> > exists in jessie or not (and if it doesn't, the fix will also have
> > no effect for people who mix their packages with ones from other
> > sources).
> 
> Hello,
> 
> it is not fixed, alas.  The following SIGSEGV backtrace is with 
> gstreamer1.0-plugins-bad 1.6.1-1+b1 and iceweasel 38.4.0esr-1.  Such 
> crashes are rarer, but they do occur:

Hi,

this is a different bug than the stack corruption related to the faad
plugin though. It looks like broken error handling in iceweasel:
https://github.com/mozilla/gecko-dev/blob/GECKO3840esr_2015102720_RELBRANCH/dom/media/gstreamer/GStreamerReader.cpp#L1464

This line here should check if mapping actually succeeds. Apparently it
doesn't (for whatever reason which might be another bug), as in the
next stack frame all field in frame are 0.


Do you have, by any chance, gstreamer1.0-vaapi installed?

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

Bug#798167: camitk: depends on vtk 5

[Andreas Tille]

Hi Emmanuel and Nicolas,

I hope you realised the bug reported in Debian saying:

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

It would be great if you could adapt camitk and release a new version.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#807114: marked as done (python-acme: needs python-openssl >= 0.15, but dependency is unversioned)

[Debian Bug Tracking System]

Your message dated Sun, 06 Dec 2015 05:56:22 +
with message-id 
and subject line Bug#807114: fixed in python-acme 0.1.0-2
has caused the Debian Bug report #807114,
regarding python-acme: needs python-openssl >= 0.15, but dependency is 
unversioned
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.)


-- 
807114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-acme
Version: 0.1.0-1
Severity: serious

python-acme needs at least version 0.15 of python-openssl.  This is
reflected in the Build-Depends, but the binary packages have an
unversioned dependency on python-openssl.

Trying to use the letsencrypt client with older versions of
python-openssl results in an error, see
https://github.com/letsencrypt/letsencrypt/issues/885

Ansgar
--- End Message ---
--- Begin Message ---
Source: python-acme
Source-Version: 0.1.0-2

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

Debian distribution maintenance software
pp.
Francois Marier  (supplier of updated python-acme package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 05 Dec 2015 21:21:10 -0800
Source: python-acme
Binary: python-acme python3-acme python-acme-doc
Architecture: source all
Version: 0.1.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Francois Marier 
Description:
 python-acme - ACME protocol library for Python 2
 python-acme-doc - ACME protocol library for Python 2 - Documentation
 python3-acme - ACME protocol library for Python 3
Closes: 807114
Changes:
 python-acme (0.1.0-2) experimental; urgency=medium
 .
   * Version the python{,3}-openssl runtime dependency (closes: #807114)
Checksums-Sha1:
 22d20b1c402832121c72f8f3e08674182729b0de 2743 python-acme_0.1.0-2.dsc
 81455194381a7e98a6b4c42b2000ec097f3d4a60 4740 python-acme_0.1.0-2.debian.tar.xz
 0c121bb55bd562f67a34290a82bb5c8b06be3109 87902 python-acme-doc_0.1.0-2_all.deb
 249a591c9633e9dbec2da08b133131723f7f5137 55826 python-acme_0.1.0-2_all.deb
 ab6384bd9a6a76e3ffb5dada6007b4d3aa868875 55898 python3-acme_0.1.0-2_all.deb
Checksums-Sha256:
 9cad53df91660f4985a87f7eadcc8beef252b5f12089bc75cba1640b12c86d38 2743 
python-acme_0.1.0-2.dsc
 eacc1f26b48b02cf2e844bc9a21c9e45fd9ada98db58862eded27138e9ee2ff3 4740 
python-acme_0.1.0-2.debian.tar.xz
 94ff5f10bec183184c4885a78cc931fbdb7c218b4256be1f855a85ce079307e5 87902 
python-acme-doc_0.1.0-2_all.deb
 61ba683a374990b36a1c4eaa4b73b8fb17c2f29a69a8eb5486f42068f8c11f71 55826 
python-acme_0.1.0-2_all.deb
 d1361c33519b1ea740fd9ca2bd693ae9aed35f18fc1407129fb53857b4698b49 55898 
python3-acme_0.1.0-2_all.deb
Files:
 2668d10480212f3439d89498c3e29fd6 2743 python optional python-acme_0.1.0-2.dsc
 cafb250f847dd8955a9fee15830246f1 4740 python optional 
python-acme_0.1.0-2.debian.tar.xz
 f47228237095998f9c30648b2db1ca3b 87902 doc optional 
python-acme-doc_0.1.0-2_all.deb
 6fc3b35836a38c2b9fbac18af90d3bc2 55826 python optional 
python-acme_0.1.0-2_all.deb
 bdc0363f7bbc84aa6eb8eb44c4bf4692 55898 python optional 
python3-acme_0.1.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJWY8ZjXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4QzQ3MEIyQTBCMzE1NjhFMTEwRDQzMjUx
NjI4MUYyRTAwN0M5OEQxAAoJEBYoHy4AfJjRcY4P/0atjWv1ooxO0cN9S8w2y2ZU
f5eVe9Fv4f4mN7Eb8iLzV0ni6R2K8M5/taOul9o3IDAqOvTRYXB5YjxQeZlgymAX
MpwTaAjblOGs4pdp8wMUq9gVULwAGsnnqhb/qbWOPtd9+jZPIqeTIlVPagECEtRR
vSkvddQCB7FXD0MuJx79C24/TvbmQJI+aWoEk7DDrhs7DkOCsVKlX7fK8CH+3cvZ
cSS/gZs2RoXAWeECxNamVLy+7kymsK5uaesp0wvCyatpM2QTnuoG7+ifYW3pXS+K
zpIgM8NNqKC6Yiaezo0I9omLJCKXE1xZ8UvHGHdpIZ4V9UTO1JnnEGAlIWK2bAYO
a0qBMo5E2Fyceftcg3T4yQLMGP4o/oCn3R77C8yq8vvmvbdh3jJNe4R6X+3IgdF3
jPCn66OLzywOV2pm1hjwc/fsQNNB1W+9eH+qCA17khsLUVf5xx8mBeoo3NhY/fsA
vCfG5rWtkVDVbg5o6dG3psZqDgDbeIuUZJ8CnU9EzNAuupBLUdMQbkRPw6E5mGPJ
baVVk0s1CRV+4IhgnJmIDASbD9vmVzxFQV02ll2cqgzKjP7XXKeWe7KRgdNSNXi9

Bug#706928: marked as done (zemberek-server doesn't respect to the Java paths of the system)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 12:57:48 +
with message-id 
and subject line Bug#706928: fixed in zemberek-server 0.7.1-12.2
has caused the Debian Bug report #706928,
regarding zemberek-server doesn't respect to the Java paths of the system
to be marked as done.

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

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


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

Package: zemberek-server
Version: 0.7.1-12
Severity: important
Tags: patch

Hi,

During the development of our Debian derivative distro Pardus (We will 
join to the census shortly), I've found a bug in zemberek-server causes 
it to fail to start in 64bit systems. Cause of the problem is the 
wrapper in the package, which is located in /usr/sbin/zemberek-server, 
uses hard-coded Java paths. Normally, the package should run with the 
default Java of the system, provided by the debian-alternatives 
subsystem. I've developed a small patch which makes zemberek-server 
compatible with debian-alternatives and solves the problem. Currently 
tested on OpenJDK 6 & 7 without any problems.


Since it's my first patch, I welcome any feedback and improvements.

Cheers,

Hakan--- zemberek-server 2013-05-03 14:32:31.239764116 +0300
+++ /usr/sbin/zemberek-server   2013-05-03 14:32:47.914181369 +0300
@@ -5,7 +5,7 @@
 
 ZEMBEREK_DEPENDS="zemberek-server zemberek zemberek-tr mina-core slf4j-api 
slf4j-nop dbus unix"
 ZEMBEREK_LOGFILE=/var/log/zemberek-server.log
-JAVA_HOME=/usr/lib/jvm/java-6-openjdk
+JAVA=`update-alternatives --query java |grep ^Value: |awk '{print $2}'`
 
 # FIXME: Remove this hack when the upstream adds logging facility.
 if [ -n "$ZEMBEREK_LOGFILE"  ] && \
@@ -20,5 +20,5 @@
CLASSPATH=$JAVA_REPOS/${dep}.jar:$CLASSPATH
 done
 
-exec -a "zemberek-server" $JAVA_HOME/bin/java -classpath "$CLASSPATH" 
-DConfigFile=/etc/zemberek-server.conf \
+exec -a "zemberek-server" $JAVA -classpath "$CLASSPATH" 
-DConfigFile=/etc/zemberek-server.conf \
 -Djava.library.path=/usr/lib/jni net.zemberekserver.server.ZemberekServer
--- End Message ---
--- Begin Message ---
Source: zemberek-server
Source-Version: 0.7.1-12.2

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated zemberek-server 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, 25 Nov 2015 13:15:39 +0900
Source: zemberek-server
Binary: zemberek-server
Architecture: source all
Version: 0.7.1-12.2
Distribution: unstable
Urgency: medium
Maintainer: Rail Aliev 
Changed-By: Hideki Yamane 
Description:
 zemberek-server - Turkish spellcheck server
Closes: 706928 761646
Changes:
 zemberek-server (0.7.1-12.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control
 - update Homepage: to github since Google Code was shutdown.
 - add "Depends: dbus" to startup properly (Closes: #761646)
   * debian/copyright
 - update download site to github
   * remove unnecessary debian/watch with above update
   * update debian/zemberek-server-wrapper to specify Java path properly.
 Thanks to Hakan Bayındır  for the patch.
 (Closes: #706928)
Checksums-Sha1:
 1f88b93e59e3e24f0c0cadb670a3766e2b4fe2ae 2000 zemberek-server_0.7.1-12.2.dsc
 b885372bc3d7ff079ec6a0f37a37bb8abe702ffd 15790 
zemberek-server_0.7.1-12.2.diff.gz
 a7753870a0a7f5ab7e8472b77768dee36fb4e046 30236 
zemberek-server_0.7.1-12.2_all.deb
Checksums-Sha256:
 11e8659ee2464c68e098c13322add4bfc8455c3ad523a5b0958f4a7d3e23ff5a 2000 
zemberek-server_0.7.1-12.2.dsc
 72ad7aad690d586a53d00dc4cd1651944155d0aa5de7c561977dbfa514e6454e 15790 
zemberek-server_0.7.1-12.2.diff.gz
 2d4b38c6bc588b41032bde97c660c900ca67c55a6628f3d416beeb5116b2eb84 30236 
zemberek-server_0.7.1-12.2_all.deb
Files:
 d55165dc45e4eacd757e65bad350c569 2000 text optional 
zemberek-server_0.7.1-12.2.dsc
 

Bug#761646: marked as done (zemberek-server: missing dependency on dbus)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 12:57:48 +
with message-id 
and subject line Bug#761646: fixed in zemberek-server 0.7.1-12.2
has caused the Debian Bug report #761646,
regarding zemberek-server: missing dependency on dbus
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.)


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

Package: zemberek-server
Version: 0.7.1-12.1
Severity: serious

Even after fixing #706928, zemberek-server does not start:

org.freedesktop.dbus.exceptions.DBusException: Failed to connect to bus No such 
file or directory
   at org.freedesktop.dbus.DBusConnection.(DBusConnection.java:304)
   at 
org.freedesktop.dbus.DBusConnection.getConnection(DBusConnection.java:282)
   at net.zemberekserver.server.dbus.ZemberekDbus.start(Unknown Source)
   at net.zemberekserver.server.ZemberekServer.initDBusServer(Unknown 
Source)
   at net.zemberekserver.server.ZemberekServer.main(Unknown Source)


Installing dbus fixes the problem.


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

Kernel: Linux 3.16-1-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages zemberek-server depends on:
ii  adduser  3.113+nmu3
ii  default-jre-headless 2:1.7-52
ii  libcommons-logging-java  1.2-1
ii  libdbus-java 2.8-5
ii  libmatthew-debug-java0.7.3-1
ii  libmina-java 1.1.7.dfsg-11
ii  libslf4j-java1.7.7-1
ii  libunixsocket-java   0.7.3-1
ii  libzemberek-java 2.1.1-8.1
ii  libzemberek-tr-java  2.1.1-8.1

Versions of packages zemberek-server recommends:
pn  zpspell  

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: zemberek-server
Source-Version: 0.7.1-12.2

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated zemberek-server 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, 25 Nov 2015 13:15:39 +0900
Source: zemberek-server
Binary: zemberek-server
Architecture: source all
Version: 0.7.1-12.2
Distribution: unstable
Urgency: medium
Maintainer: Rail Aliev 
Changed-By: Hideki Yamane 
Description:
 zemberek-server - Turkish spellcheck server
Closes: 706928 761646
Changes:
 zemberek-server (0.7.1-12.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control
 - update Homepage: to github since Google Code was shutdown.
 - add "Depends: dbus" to startup properly (Closes: #761646)
   * debian/copyright
 - update download site to github
   * remove unnecessary debian/watch with above update
   * update debian/zemberek-server-wrapper to specify Java path properly.
 Thanks to Hakan Bayındır  for the patch.
 (Closes: #706928)
Checksums-Sha1:
 1f88b93e59e3e24f0c0cadb670a3766e2b4fe2ae 2000 zemberek-server_0.7.1-12.2.dsc
 b885372bc3d7ff079ec6a0f37a37bb8abe702ffd 15790 
zemberek-server_0.7.1-12.2.diff.gz
 a7753870a0a7f5ab7e8472b77768dee36fb4e046 30236 
zemberek-server_0.7.1-12.2_all.deb
Checksums-Sha256:
 11e8659ee2464c68e098c13322add4bfc8455c3ad523a5b0958f4a7d3e23ff5a 2000 
zemberek-server_0.7.1-12.2.dsc
 72ad7aad690d586a53d00dc4cd1651944155d0aa5de7c561977dbfa514e6454e 15790 
zemberek-server_0.7.1-12.2.diff.gz
 2d4b38c6bc588b41032bde97c660c900ca67c55a6628f3d416beeb5116b2eb84 30236 
zemberek-server_0.7.1-12.2_all.deb
Files:
 d55165dc45e4eacd757e65bad350c569 2000 text optional 
zemberek-server_0.7.1-12.2.dsc
 f8f0083b4b75de93c089bf5ccafdbc25 15790 text optional 
zemberek-server_0.7.1-12.2.diff.gz
 9a0c31c90f5197d8c3ff24a61c927bc0 30236 text optional 
zemberek-server_0.7.1-12.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#807114: python-acme: needs python-openssl >= 0.15, but dependency is unversioned

[Ansgar Burchardt]

Source: python-acme
Version: 0.1.0-1
Severity: serious

python-acme needs at least version 0.15 of python-openssl.  This is
reflected in the Build-Depends, but the binary packages have an
unversioned dependency on python-openssl.

Trying to use the letsencrypt client with older versions of
python-openssl results in an error, see
https://github.com/letsencrypt/letsencrypt/issues/885

Ansgar

Bug#797738: marked as done (gdcm: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 14:01:48 +
with message-id 
and subject line Bug#797738: fixed in gdcm 2.6.0+dfsg-1
has caused the Debian Bug report #797738,
regarding gdcm: 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.)


-- 
797738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 2.6.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
gdcm, 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.
Gert Wollny  (supplier of updated gdcm 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: Fri, 16 Oct 2015 18:21:58 +0200
Source: gdcm
Binary: libgdcm2.6 libgdcm-tools libgdcm2-dev libgdcm2.6-dbg libgdcm-cil 
php5-gdcm python-gdcm libvtkgdcm2.6 libvtkgdcm2-dev libvtkgdcm-cil php5-vtkgdcm 
python-vtkgdcm libvtkgdcm-tools gdcm-doc
Architecture: source all amd64
Version: 2.6.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 gdcm-doc   - Grassroots DICOM documentation
 libgdcm-cil - Grassroots DICOM CLI bindings
 libgdcm-tools - Grassroots DICOM tools and utilities
 libgdcm2-dev - Grassroots DICOM development libraries and headers
 libgdcm2.6 - Grassroots DICOM runtime libraries
 libgdcm2.6-dbg - Grassroots DICOM runtime libraries, debug version
 libvtkgdcm-cil - Grassroots DICOM VTK CLI bindings
 libvtkgdcm-tools - Grassroots DICOM VTK tools and utilities
 libvtkgdcm2-dev - Grassroots DICOM VTK development libraries and headers
 libvtkgdcm2.6 - Grassroots DICOM VTK runtime libraries
 php5-gdcm  - Grassroots DICOM PHP5 bindings
 php5-vtkgdcm - Grassroots DICOM VTK PHP bindings
 python-gdcm - Grassroots DICOM Python bindings
 python-vtkgdcm - Grassroots DICOM VTK/Python 

Bug#807113: golang-golang-x-net-dev and golang-golang-x-crypto-dev: error when trying to install together

[Ralf Treinen]

Package: golang-golang-x-crypto-dev,golang-golang-x-net-dev
Version: golang-golang-x-crypto-dev/1:0.0~git20151201.0.7b85b09-2
Version: golang-golang-x-net-dev'0.0+git20151007.b846920+dfsg-1@all, 
golang-golang-x-net-dev/1:0.0~git20151201.0.7b85b09-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-12-05
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package golang-golang-x-crypto-dev.
(Reading database ... 10929 files and directories currently installed.)
Preparing to unpack 
.../golang-golang-x-crypto-dev_1%3a0.0~git20151201.0.7b85b09-2_all.deb ...
Unpacking golang-golang-x-crypto-dev (1:0.0~git20151201.0.7b85b09-2) ...
Selecting previously unselected package golang-golang-x-net-dev.
Preparing to unpack 
.../golang-golang-x-net-dev_1%3a0.0~git20151201.0.7b85b09-1_all.deb ...
Unpacking golang-golang-x-net-dev (1:0.0~git20151201.0.7b85b09-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-golang-x-net-dev_1%3a0.0~git20151201.0.7b85b09-1_all.deb
 (--unpack):
 trying to overwrite 
'/usr/share/gocode/src/golang.org/x/crypto/blowfish/cipher.go', which is also 
in package golang-golang-x-crypto-dev 1:0.0~git20151201.0.7b85b09-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 
/var/cache/apt/archives/golang-golang-x-net-dev_1%3a0.0~git20151201.0.7b85b09-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/gocode/src/code.google.com/p/go.crypto
  /usr/share/gocode/src/golang.org/x/crypto/bcrypt/base64.go
  /usr/share/gocode/src/golang.org/x/crypto/bcrypt/bcrypt.go
  /usr/share/gocode/src/golang.org/x/crypto/bcrypt/bcrypt_test.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/block.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/blowfish_test.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/cipher.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/const.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/bn256.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/bn256_test.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/constants.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/curve.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/example_test.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/gfp12.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/gfp2.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/gfp6.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/optate.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/twist.go
  /usr/share/gocode/src/golang.org/x/crypto/cast5/cast5.go
  /usr/share/gocode/src/golang.org/x/crypto/cast5/cast5_test.go
  /usr/share/gocode/src/golang.org/x/crypto/codereview.cfg
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/const_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/cswap_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/curve25519.go
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/curve25519_test.go
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/doc.go
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/freeze_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/ladderstep_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/mont25519_amd64.go
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/mul_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/square_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/hkdf/example_test.go
  /usr/share/gocode/src/golang.org/x/crypto/hkdf/hkdf.go
  /usr/share/gocode/src/golang.org/x/crypto/hkdf/hkdf_test.go
  /usr/share/gocode/src/golang.org/x/crypto/md4/md4.go
  /usr/share/gocode/src/golang.org/x/crypto/md4/md4_test.go
  /usr/share/gocode/src/golang.org/x/crypto/md4/md4block.go
  /usr/share/gocode/src/golang.org/x/crypto/nacl/box/box.go
  /usr/share/gocode/src/golang.org/x/crypto/nacl/box/box_test.go
  /usr/share/gocode/src/golang.org/x/crypto/nacl/secretbox/secretbox.go
  

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

[Soeren D. Schulze]

Am 12.11.2015 um 15:02 schrieb Sebastian Dröge:

On Do, 2015-11-12 at 14:41 +0100, Soeren D. Schulze wrote:

Hello,

the problem does not seem to occur any more with
gstreamer1.0-plugins-bad 1.6.1-1+b1 and iceweasel 38.4.0esr-1.

Do you have any specific packages for me to test?


Just a normal jessie installation without installing things from other
sources, including sid :) It is definitely fixed since gst-plugins-bad
1.5.X, it's just not clear if the actual bug also exists in jessie or
not (and if it doesn't, the fix will also have no effect for people who
mix their packages with ones from other sources).


Hello,

it is not fixed, alas.  The following SIGSEGV backtrace is with 
gstreamer1.0-plugins-bad 1.6.1-1+b1 and iceweasel 38.4.0esr-1.  Such 
crashes are rarer, but they do occur:


#0  0x77bce79b in raise (sig=sig@entry=11) at 
../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37

resultvar = 0
pid = 
#1  0x7417ed77 in nsProfileLock::FatalSignalHandler (signo=11, 
info=0x7fffccafd370, context=0x7fffccafd240) at 
/tmp/buildd/iceweasel-38.4.0esr/profile/dirserviceprovider/nsProfileLock.cpp:180

unblock_sigs = {__val = {1024, 0 }}
oldact = 
#2  
No locals.
#3  0x73a11a76 in 
mozilla::GStreamerReader::ImageDataFromVideoFrame 
(this=this@entry=0x7fffd8624800, aFrame=aFrame@entry=0x7fffccafd850, 
aData=aData@entry=0x7fffccafd800) at 
/tmp/buildd/iceweasel-38.4.0esr/dom/media/gstreamer/GStreamerReader.cpp:1440

No locals.
#4  0x73a11fdf in mozilla::GStreamerReader::GetImageFromBuffer 
(this=this@entry=0x7fffd8624800, aBuffer=aBuffer@entry=0x7fffb7ec4500) 
at 
/tmp/buildd/iceweasel-38.4.0esr/dom/media/gstreamer/GStreamerReader.cpp:1466
frame = {info = {finfo = 0x0, interlace_mode = 
GST_VIDEO_INTERLACE_MODE_PROGRESSIVE, flags = GST_VIDEO_FLAG_NONE, width 
= 0, height = 0, size = 0, views = 0, chroma_site = 
GST_VIDEO_CHROMA_SITE_UNKNOWN, colorimetry = {range = 
GST_VIDEO_COLOR_RANGE_UNKNOWN, matrix = GST_VIDEO_COLOR_MATRIX_UNKNOWN, 
transfer = GST_VIDEO_TRANSFER_UNKNOWN, primaries = 
GST_VIDEO_COLOR_PRIMARIES_UNKNOWN}, par_n = 0, par_d = 0, fps_n = 0, 
fps_d = 0, offset = {0, 0, 0, 0}, stride = {0, 0, 0, 0}, ABI = {abi = 
{multiview_mode = GST_VIDEO_MULTIVIEW_MODE_MONO, multiview_flags = 
GST_VIDEO_MULTIVIEW_FLAGS_NONE}, _gst_reserved = {0x0, 0x0, 0x0, 0x0}}}, 
flags = GST_VIDEO_FRAME_FLAG_NONE, buffer = 0x0, meta = 0x0, id = 0, 
data = {0x0, 0x0, 0x0, 0x0}, map = {{memory = 0x0, flags = (unknown: 0), 
data = 0x0, size = 0, maxsize = 0, user_data = {0x0, 0x0, 0x0, 0x0}, 
_gst_reserved = {0x0, 0x0, 0x0, 0x0}}, {memory = 0x0, flags = (unknown: 
0), data = 0x0, size = 0, maxsize = 0, user_data = {0x0, 0x0, 0x0, 0x0}, 
_gst_reserved = {0x0, 0x0, 0x0, 0x0}}, {memory = 0x0, flags = (unknown: 
0), data = 0x0, size = 0, maxsize = 0, user_data = {0x0, 0x0, 0x0, 0x0}, 
_gst_reserved = {0x0, 0x0, 0x0, 0x0}}, {memory = 0x0, flags = (unknown: 
0), data = 0x0, size = 0, maxsize = 0, user_data = {0x0, 0x0, 0x0, 0x0}, 
_gst_reserved = {0x0, 0x0, 0x0, 0x0}}}, _gst_reserved = {0x0, 0x0, 0x0, 
0x0}}
data = {mYChannel = 0x0, mYStride = 0, mYSize = 
{> = {width = 0, 
height = 0},  = {}, fields>}, mYSkip = 0, mCbChannel = 0x0, mCrChannel = 0x0, mCbCrStride = 
0, mCbCrSize = {> = {width = 0, 
height = 0},  = {}, fields>}, mCbSkip = 0, mCrSkip = 0, mPicX = 0, mPicY = 0, mPicSize = 
{> = {width = 0, 
height = 0},  = {}, fields>}, mStereoMode = mozilla::StereoMode::MONO}

mem = 
image = {mRawPtr = 0x7fffaf8daf20}
#5  0x73a1243f in mozilla::GStreamerReader::DecodeVideoFrame 
(this=0x7fffd8624800, aKeyFrameSkip=, 
aTimeThreshold=) at 
/tmp/buildd/iceweasel-38.4.0esr/dom/media/gstreamer/GStreamerReader.cpp:824

buffer = 0x7fffb7ec4500
isKeyframe = 
timestamp = 41000
duration = 41708
image = {mRawPtr = 0x7fffaf8daf20}
offset = 
#6  0x73998ae1 in mozilla::MediaDecoderReader::RequestVideoData 
(this=0x7fffd8624800, aSkipToNextKeyframe=, 
aTimeThreshold=0) at 
/tmp/buildd/iceweasel-38.4.0esr/dom/media/MediaDecoderReader.cpp:245

p = {mRawPtr = 0x7fffcdf02970}
__func__ = "RequestVideoData"
skip = false
#7  0x73974a23 in 
mozilla::detail::MethodCallWithTwoArgs, 
mozilla::MediaDecoderReader, bool, long>::Invoke (this=) 
at /tmp/buildd/iceweasel-38.4.0esr/dom/media/MediaPromise.h:603

No locals.
#8  0x73996b56 in 
mozilla::detail::ProxyRunnable >::Run 
(this=0x7fffb6c9b200) at 
/tmp/buildd/iceweasel-38.4.0esr/dom/media/MediaPromise.h:620

p = {mRawPtr = 0x7fffcdf02970}
#9  0x73997637 in 

Bug#807091: [Pkg-xfce-devel] Bug#807091: xfce4-terminal fails to start with an error message

[Yves-Alexis Perez]

control: severity -1 important
control: tag -1 unreproducible moreinfo

On sam., 2015-12-05 at 11:04 +0100, Thomas Weber wrote:
> Package: xfce4-terminal
> Version: 0.6.3-2
> Severity: grave
> Justification: renders package unusable
> 
> Launching xfce4-terminal as normal user gives the following error message in
> an error window:
> "Failed to execute child
> grantpt failed: Operation not permitted"
> After closing the error message, the terminal window appears, but there
> is no shell started in it.
> If I gain superuser rights via su and execute xfce4-terminal, the
> terminal launches (with an error message saying "Failed to connect to
> session manager: [...]".
> 
> Some reports on the internet suggested that this might be a permission
> problem with /dev/pts. However, I do not have an entry for /dev/pts in
> my /etc/fstab and the rights are as follows:
> devpts on /dev/pts type devpts
> (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
> 
> This (non-)behaviour of xfce4-terminal is fairly new, but I cannot
> pinpoint it to any recent update as I usually keep up just one instance
> of the terminal for some time.

Well, I surely can't reproduce, so you'll need to investigate more on your
side. Try running it through strace to check exactly where the grantpt
operation is failed.

In any case, it doesn't look xfce4-terminal related at first sight.

Regards,
-- 
Yves-Alexis



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

Processed: Re: [Pkg-xfce-devel] Bug#807091: xfce4-terminal fails to start with an error message

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #807091 [xfce4-terminal] xfce4-terminal fails to start with an error message
Severity set to 'important' from 'grave'
> tag -1 unreproducible moreinfo
Bug #807091 [xfce4-terminal] xfce4-terminal fails to start with an error message
Added tag(s) unreproducible and moreinfo.

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

Bug#801228: marked as done (libopenjp2-7-dev should conflict with src:gdcm)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 14:01:48 +
with message-id 
and subject line Bug#801228: fixed in gdcm 2.6.0+dfsg-1
has caused the Debian Bug report #801228,
regarding libopenjp2-7-dev should conflict with src:gdcm
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.)


-- 
801228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdcm
Version: 2.4.4-4
Severity: serious
Justification: FTBFS

One cannot compile gdcm when libopenjp2-7-dev is installed. Make sure
to add a Build-Conflict and/or fix the code upstream.

[ 61%] Building CXX object
Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEG2000Codec.cxx.o
cd /tmp/gdcm-2.4.4/obj-x86_64-linux-gnu/Source/MediaStorageAndFileFormat
&& /usr/bin/c++   -DgdcmMSFF_EXPORTS -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  -fPIC
-I/tmp/gdcm-2.4.4/Source/Common
-I/tmp/gdcm-2.4.4/obj-x86_64-linux-gnu/Source/Common
-I/tmp/gdcm-2.4.4/Source/DataStructureAndEncodingDefinition
-I/tmp/gdcm-2.4.4/Source/DataDictionary
-I/tmp/gdcm-2.4.4/Source/InformationObjectDefinition
-I/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat
-I/tmp/gdcm-2.4.4/Utilities
-I/tmp/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities
-I/usr/include/openjpeg-2.1 -I/usr/include/json-c -I/usr/include/json
  -o CMakeFiles/gdcmMSFF.dir/gdcmJPEG2000Codec.cxx.o -c
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:
In function ‘void**
gdcm::opj_stream_create_memory_stream(gdcm::myfile*, OPJ_UINT32,
bool)’:
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:193:42:
error: too few arguments to function ‘void
opj_stream_set_user_data(void**, void*, opj_stream_free_user_data_fn)’
   opj_stream_set_user_data(l_stream,p_mem);
  ^
In file included from /tmp/gdcm-2.4.4/Utilities/gdcm_openjpeg2.h:20:0,
 from
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:29:
/usr/include/openjpeg-2.1/openjpeg.h:1154:27: note: declared here
 OPJ_API void OPJ_CALLCONV opj_stream_set_user_data (opj_stream_t*
p_stream, void * p_data, opj_stream_free_user_data_fn p_function);
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:
In member function ‘std::pair
gdcm::JPEG2000Codec::DecodeByStreamsCommon(char*, size_t)’:
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:465:35:
error: ‘CODEC_J2K’ was not declared in this scope
 dinfo = opj_create_decompress(CODEC_J2K);
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:468:35:
error: ‘CODEC_JP2’ was not declared in this scope
 dinfo = opj_create_decompress(CODEC_JP2);
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:509:46:
error: ‘J2K_STREAM_CHUNK_SIZE’ was not declared in this scope
   cio = opj_stream_create_memory_stream(fsrc,J2K_STREAM_CHUNK_SIZE, true);
  ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:525:8:
error: invalid conversion from ‘opj_image_t** {aka opj_image**}’ to
‘void**’ [-fpermissive]
 cio);
^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:525:8:
error: cannot convert ‘OPJ_INT32* {aka int*}’ to ‘opj_image_t** {aka
opj_image**}’ for argument ‘3’ to ‘OPJ_BOOL opj_read_header(void**,
void**, opj_image_t**)’
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:531:54:
error: ‘opj_get_reversible’ was not declared in this scope
   reversible = opj_get_reversible(dinfo,  );
  ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:535:32:
error: too few arguments to function ‘OPJ_BOOL opj_decode(void**,
void**, opj_image_t*)’
   image = opj_decode(dinfo, cio);
^
In file included from /tmp/gdcm-2.4.4/Utilities/gdcm_openjpeg2.h:20:0,
 from
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:29:
/usr/include/openjpeg-2.1/openjpeg.h:1299:31: note: declared here
 OPJ_API OPJ_BOOL OPJ_CALLCONV opj_decode(   opj_codec_t *p_decompressor,
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:539:40:
error: ‘check_comp_valid’ was 

Bug#797673: marked as done (Switch back to SWIB based C# layer in GDCM)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 14:01:48 +
with message-id 
and subject line Bug#797673: fixed in gdcm 2.6.0+dfsg-1
has caused the Debian Bug report #797673,
regarding Switch back to SWIB based C# layer in GDCM
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.)


-- 
797673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdcm
Version: 2.4.4-4
Severity: grave
Tags: patch

Now that upstream has clarified the situation with Activiz.NET:

http://public.kitware.com/pipermail/vtk-developers/2015-September/032491.html

I suggest that:

1. We revert back (temporarily for stretch) to the GDCM C# SWIG layer (this
is compatible with GDCM 2.2.x debian package),
2. Apply the attached patch,
3. Leave 65 open,
4. Leave mummy and activiz.net in current state, so they will get
auto-removed
5. once upstream (=kitware) updates Activiz.NET with a CastXML based build
system, revert the operations !

(I am not sure about the status of cableswig, but as above, I would not
touch it).

I've used the severity of grave, since otherwise GDCM will get removed
simply because if Activiz.NET which would otherwise imapct lots of
dependencies. Feel free to downgrade.

2cts


gdcm_dotnet.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 2.6.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
gdcm, 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.
Gert Wollny  (supplier of updated gdcm 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: Fri, 16 Oct 2015 18:21:58 +0200
Source: gdcm
Binary: libgdcm2.6 libgdcm-tools libgdcm2-dev libgdcm2.6-dbg libgdcm-cil 
php5-gdcm python-gdcm libvtkgdcm2.6 libvtkgdcm2-dev libvtkgdcm-cil php5-vtkgdcm 
python-vtkgdcm libvtkgdcm-tools gdcm-doc
Architecture: source all amd64
Version: 2.6.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 gdcm-doc   - Grassroots DICOM documentation
 libgdcm-cil - Grassroots DICOM CLI bindings
 libgdcm-tools - Grassroots DICOM tools and utilities
 libgdcm2-dev - Grassroots DICOM development libraries and headers
 libgdcm2.6 - Grassroots DICOM runtime libraries
 libgdcm2.6-dbg - Grassroots DICOM runtime libraries, debug version
 libvtkgdcm-cil - Grassroots DICOM VTK CLI bindings
 libvtkgdcm-tools - Grassroots DICOM VTK tools and utilities
 libvtkgdcm2-dev - Grassroots DICOM VTK development libraries and headers
 libvtkgdcm2.6 - Grassroots DICOM VTK runtime libraries
 php5-gdcm  - Grassroots DICOM PHP5 bindings
 php5-vtkgdcm - Grassroots DICOM VTK PHP bindings
 python-gdcm - Grassroots DICOM Python bindings
 python-vtkgdcm - Grassroots DICOM VTK/Python bindings
Closes: 797655 797673 797738 801228
Changes:
 gdcm (2.6.0+dfsg-1) unstable; urgency=medium
 .
   [Gert Wollny]
   * new upstream version. Closes: #797738
   * Apply patch provided by Mathieu (see below) Closes: #797673
   * d/* update all files to use 2.6 instead of 2.4
   * Transition to use vtk6, Related: #798164
   * remove java bindings because they depend on libvtk*-java but
 vtk6 currently doesn't provide these bindings Related: 798963
   * Add patch enable-vtk6-bindings.patch to correct bindings for VTK6
   * Add patch linkvtkdoc.patch to use compressed vtk6-doc helpers
 Related: #751395,  #751412
   * Add patches to properly sign C# files
   * d/copyright update copyrights to satisfy DEP5
   * add dependency on dh-python, Closes: #797655
   * removing some static VC++ libs from tarball to make it follow DFSG
   * add lintian overrides for
 - embedded javascript (rationale: src:doxygen/debian/Readme.jquery)
   * Add build-conflict: libopenjp2-7-dev, Closes: #801228
 .
   [Mathieu Malaterre]
   * Do not use activiz.net anymore
 .
   [Andreas Tille]
   * Switched to Sébastien Jodogne's correct e-mail

Bug#806243: [libminc] Test issues when building on mipsel architecture (#66)

[Andreas Tille]

Hi,

I'm just forwarding this mail from upstream.  From my perspective it is
possibly not a bug in libminc but rather a problem of certain mips
hardware.  I wonder in how far this is a serious bug of libminc and
should be downgraded to important (at maximum).

Kind regards

   Andreas.

On Sat, Dec 05, 2015 at 09:01:29AM -0800, Robert D Vincent wrote:
> I do not have access to any physical MIPS hardware, and the emulated system I 
> use does not exhibit the problem. I am trying to build an emulated system 
> using a more recent version of the OS to see if that has an impact, Is there 
> any way I can get remote access to a physical system of the right kind? Or, 
> failing that, does anyone have an emulated system that exhibits the problem?
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/BIC-MNI/libminc/issues/66#issuecomment-162223456

-- 
http://fam-tille.de

Bug#802356: Any news about this bug?

[Markus Koschany]

Am 05.12.2015 um 18:12 schrieb Andreas Tille:
> Hi,
> 
> I just noticed that the reverse depends of this package are removed from
> testing.  As you know I tried to help in resolving this bug but I was
> running out of ideas and contacting upstream was also not helpful.
> 
> Any news about this?
> 

Hi Andreas,

I am currently working on getting a newer version of bouncycastle into
unstable. This will fix all outstanding bugs in this package. Some
upgrading of reverse-dependencies is also needed. As soon as this is
done, I will take a look at svnclient.

Regards,

Markus







signature.asc
Description: OpenPGP digital signature

Bug#807128: gcc-5-base: Differing changelog.Debian.gz between :i386 and :amd64

[Matthias Klose]

no binNMU please.

On 05.12.2015 19:25, James McCoy wrote:

Control: reassign -1 release.debian.org
Control: retitle -1 nmu: gcc-5_5.3.0-3
Control: user release.debian@packages.debian.org
Control: usertag -1 binnmu

nmu gcc-5_5.3.0-3 . amd64 . unstable . -m "Rebuild to fix M-A installability"

On Sat, Dec 05, 2015 at 01:00:20PM -0500, James McCoy wrote:

Unpacking gcc-5-base:amd64 (5.3.0-3) over (5.2.1-27) ...
Preparing to unpack .../gcc-5-base_5.3.0-3_i386.deb ...
Unpacking gcc-5-base:i386 (5.3.0-3) over (5.2.1-27) ...
dpkg: error processing archive 
/var/cache/apt/archives/gcc-5-base_5.3.0-3_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/gcc-5-base/changelog.Debian.gz', 
which is different from other instances of package gcc-5-base:i386

The :amd64 package (built on the buildd) has unstable as the target
distribution in the changelog, but the (maintainer built) :i386 package
has experimental, thus causing the mismatch between the two.


Where :i386 and :amd64 were built is reversed, but the end result is the
same.

Cheers,

Bug#806243: libminc: FTBFS on mipsel

[Andreas Tille]

Hi Jurica,

On Fri, Dec 04, 2015 at 08:25:09PM +, Jurica Stanojkovic wrote:
> I have tried to build package libminc_2.3.00-2 for mipsel and mips64el on 
> diferent build boards: netlogic-xlp, cavium and loongson-3a.
> This package FTBFS only on loongson-3a (lemote). 
> On other build machines package was built from source successfully.

Thanks for the report.  I've forwarded this upstream.  For me the
problem looks like a typical integer overflow.  Is there any option
that the said boards featuring the issue are just broken and libminc
itself is fine?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#775118: [PATCH] Fix postinst

[Guido Günther]

Hi,
can we get a fixed version into at least experimental please? The bug is
already open since agx. I'm also happy to NMU.
Cheers,
 -- Guido

Bug#806243: libminc: FTBFS on mipsel

[Steve M. Robbins]

Hi,

[Adding minc-development as follow-up to previous email; 
http://www.bic.mni.mcgill.ca/pipermail/minc-development/2015-November/001223.html
 ]


On December 4, 2015 08:25:09 PM Jurica Stanojkovic wrote:
>  User: debian-m...@lists.debian.org
> 
> Hello,
> 
> I have tried to build package libminc_2.3.00-2 for mipsel and mips64el on
> diferent build boards: netlogic-xlp, cavium and loongson-3a. This package
> FTBFS only on loongson-3a (lemote).
> On other build machines package was built from source successfully.

That's interesting.  I have been able to reproduce the failure on the Debian's  
mipsel machine 'etler' which is longsoon.  I know Bert was trying to bring up 
a mipsel machine to test; not sure how far he got.  (Incidentally, Bert: I was 
working with the 'develop' branch as of Nov 19 and the failure persists.)

Jurica: is everything else the same between your good/bad environments, 
specifically: libc, compiler, and libnetcdf?  I mean: I assume they are both 
running 'sid', but are the specific versions of each package the same?

If all that is the same -- could it be something in the hardware?  The failing 
code is basically arithmetic mapping a double-value into another type, e.g. 
integer (of different sizes).  The failing test is for the mapping of 
-2*FLT_MAX, which should map to the low end of the output range but instead 
maps to the high end.  Is there anything different in the hardware that would 
maybe round things differently?  

Thanks,
-Steve


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

Bug#806243: [MINC-development] Bug#806243: libminc: FTBFS on mipsel

[Robert D. Vincent]

Steve et al,

I used an emulated mipsel environment using some other distributions (found
here: https://people.debian.org/~aurel32/qemu/mipsel/) - the bug was not
reproducible. I am in the process of building a QEMU environment for a more
recent release ("sid" from 20151023), I will try that as soon as possible.

-bert

On Sat, Dec 5, 2015 at 1:16 PM, Steve M. Robbins  wrote:

> Hi,
>
> [Adding minc-development as follow-up to previous email;
>
> http://www.bic.mni.mcgill.ca/pipermail/minc-development/2015-November/001223.html
> ]
>
>
> On December 4, 2015 08:25:09 PM Jurica Stanojkovic wrote:
> >  User: debian-m...@lists.debian.org
> >
> > Hello,
> >
> > I have tried to build package libminc_2.3.00-2 for mipsel and mips64el on
> > diferent build boards: netlogic-xlp, cavium and loongson-3a. This package
> > FTBFS only on loongson-3a (lemote).
> > On other build machines package was built from source successfully.
>
> That's interesting.  I have been able to reproduce the failure on the
> Debian's
> mipsel machine 'etler' which is longsoon.  I know Bert was trying to bring
> up
> a mipsel machine to test; not sure how far he got.  (Incidentally, Bert: I
> was
> working with the 'develop' branch as of Nov 19 and the failure persists.)
>
> Jurica: is everything else the same between your good/bad environments,
> specifically: libc, compiler, and libnetcdf?  I mean: I assume they are
> both
> running 'sid', but are the specific versions of each package the same?
>
> If all that is the same -- could it be something in the hardware?  The
> failing
> code is basically arithmetic mapping a double-value into another type, e.g.
> integer (of different sizes).  The failing test is for the mapping of
> -2*FLT_MAX, which should map to the low end of the output range but instead
> maps to the high end.  Is there anything different in the hardware that
> would
> maybe round things differently?
>
> Thanks,
> -Steve
>
> ___
> MINC-development mailing list
> minc-developm...@bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>
>

Bug#807113: marked as done (golang-golang-x-net-dev and golang-golang-x-crypto-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Sat, 5 Dec 2015 09:52:56 -0800
with message-id 

and subject line Fwd: 
golang-golang-x-net-dev_0.0+git20150817.66f0418-1_source.changes ACCEPTED into 
unstable
has caused the Debian Bug report #807113,
regarding golang-golang-x-net-dev and golang-golang-x-crypto-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.)


-- 
807113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-golang-x-crypto-dev,golang-golang-x-net-dev
Version: golang-golang-x-crypto-dev/1:0.0~git20151201.0.7b85b09-2
Version: golang-golang-x-net-dev'0.0+git20151007.b846920+dfsg-1@all, 
golang-golang-x-net-dev/1:0.0~git20151201.0.7b85b09-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-12-05
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package golang-golang-x-crypto-dev.
(Reading database ... 10929 files and directories currently installed.)
Preparing to unpack 
.../golang-golang-x-crypto-dev_1%3a0.0~git20151201.0.7b85b09-2_all.deb ...
Unpacking golang-golang-x-crypto-dev (1:0.0~git20151201.0.7b85b09-2) ...
Selecting previously unselected package golang-golang-x-net-dev.
Preparing to unpack 
.../golang-golang-x-net-dev_1%3a0.0~git20151201.0.7b85b09-1_all.deb ...
Unpacking golang-golang-x-net-dev (1:0.0~git20151201.0.7b85b09-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-golang-x-net-dev_1%3a0.0~git20151201.0.7b85b09-1_all.deb
 (--unpack):
 trying to overwrite 
'/usr/share/gocode/src/golang.org/x/crypto/blowfish/cipher.go', which is also 
in package golang-golang-x-crypto-dev 1:0.0~git20151201.0.7b85b09-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 
/var/cache/apt/archives/golang-golang-x-net-dev_1%3a0.0~git20151201.0.7b85b09-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/gocode/src/code.google.com/p/go.crypto
  /usr/share/gocode/src/golang.org/x/crypto/bcrypt/base64.go
  /usr/share/gocode/src/golang.org/x/crypto/bcrypt/bcrypt.go
  /usr/share/gocode/src/golang.org/x/crypto/bcrypt/bcrypt_test.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/block.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/blowfish_test.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/cipher.go
  /usr/share/gocode/src/golang.org/x/crypto/blowfish/const.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/bn256.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/bn256_test.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/constants.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/curve.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/example_test.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/gfp12.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/gfp2.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/gfp6.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/optate.go
  /usr/share/gocode/src/golang.org/x/crypto/bn256/twist.go
  /usr/share/gocode/src/golang.org/x/crypto/cast5/cast5.go
  /usr/share/gocode/src/golang.org/x/crypto/cast5/cast5_test.go
  /usr/share/gocode/src/golang.org/x/crypto/codereview.cfg
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/const_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/cswap_amd64.s
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/curve25519.go
  /usr/share/gocode/src/golang.org/x/crypto/curve25519/curve25519_test.go
  

Processed: fixed 806930 in 2015.11.22-1

[Debian Bug Tracking System]

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

> fixed 806930 2015.11.22-1
Bug #806930 [pianobar] pianobar needs update for new server SSL certificate
Marked as fixed in versions pianobar/2015.11.22-1.
> thanks
Stopping processing here.

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

Bug#807086: perl/experimental: FTBFS: cpan/podlators/t/devise-date failure

[Russ Allbery]

Niko Tyni  writes:

> Turns out the backported SOURCE_DATE_EPOCH support from podlators-4.00
> doesn't itself survive being build with SOURCE_DATE_EPOCH (or
> POD_MAN_DATE, for that matter) set. Patch attached.

Doh.  Thanks.  :)  I'll kick out a new version, probably this weekend.

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

Processed: found 806930 in 2014.06.08-1

[Debian Bug Tracking System]

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

> found 806930 2014.06.08-1
Bug #806930 [pianobar] pianobar needs update for new server SSL certificate
Marked as found in versions pianobar/2014.06.08-1.
> thanks
Stopping processing here.

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

Processed: found 806930 in 2012.05.06-2

[Debian Bug Tracking System]

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

> found 806930 2012.05.06-2
Bug #806930 [pianobar] pianobar needs update for new server SSL certificate
Marked as found in versions pianobar/2012.05.06-2.
> thanks
Stopping processing here.

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

Bug#802356: Any news about this bug?

[Andreas Tille]

Hi,

I just noticed that the reverse depends of this package are removed from
testing.  As you know I tried to help in resolving this bug but I was
running out of ideas and contacting upstream was also not helpful.

Any news about this?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#807113: [pkg-go] Bug#807113: golang-golang-x-net-dev and golang-golang-x-crypto-dev: error when trying to install together

[Tianon Gravi]

On 5 December 2015 at 05:45, Ralf Treinen  wrote:
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:

This whole mess was my fault. :(  (See #807002 for more details.)

I've just now uploaded src:golang-golang-x-net-dev version
1:0.0+git20150817.66f0418-1 which fixes the problem on the net side,
and src:golang-go.crypto version 1:0.0~git20151201.0.7b85b09-2 is
already through binNEW to fix this on the crypto side.

I'll plan to close this bug as soon as my net upload is accepted for
the archive.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807128: gcc-5-base: Differing changelog.Debian.gz between :i386 and :amd64

[James McCoy]

Package: gcc-5-base
Version: 5.3.0-3
Severity: serious

Unpacking gcc-5-base:amd64 (5.3.0-3) over (5.2.1-27) ...
Preparing to unpack .../gcc-5-base_5.3.0-3_i386.deb ...
Unpacking gcc-5-base:i386 (5.3.0-3) over (5.2.1-27) ...
dpkg: error processing archive 
/var/cache/apt/archives/gcc-5-base_5.3.0-3_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/gcc-5-base/changelog.Debian.gz', 
which is different from other instances of package gcc-5-base:i386

The :amd64 package (built on the buildd) has unstable as the target
distribution in the changelog, but the (maintainer built) :i386 package
has experimental, thus causing the mismatch between the two.

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

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

Bug#807128: gcc-5-base: Differing changelog.Debian.gz between :i386 and :amd64

[James McCoy]

Control: reassign -1 release.debian.org
Control: retitle -1 nmu: gcc-5_5.3.0-3
Control: user release.debian@packages.debian.org
Control: usertag -1 binnmu

nmu gcc-5_5.3.0-3 . amd64 . unstable . -m "Rebuild to fix M-A installability"

On Sat, Dec 05, 2015 at 01:00:20PM -0500, James McCoy wrote:
> Unpacking gcc-5-base:amd64 (5.3.0-3) over (5.2.1-27) ...
> Preparing to unpack .../gcc-5-base_5.3.0-3_i386.deb ...
> Unpacking gcc-5-base:i386 (5.3.0-3) over (5.2.1-27) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/gcc-5-base_5.3.0-3_i386.deb (--unpack):
>  trying to overwrite shared '/usr/share/doc/gcc-5-base/changelog.Debian.gz', 
> which is different from other instances of package gcc-5-base:i386
> 
> The :amd64 package (built on the buildd) has unstable as the target
> distribution in the changelog, but the (maintainer built) :i386 package
> has experimental, thus causing the mismatch between the two.

Where :i386 and :amd64 were built is reversed, but the end result is the
same.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Processed (with 2 errors): Re: Bug#807128: gcc-5-base: Differing changelog.Debian.gz between :i386 and :amd64

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #807128 [gcc-5-base] gcc-5-base: Differing changelog.Debian.gz between 
:i386 and :amd64
Bug reassigned from package 'gcc-5-base' to 'release.debian.org'.
No longer marked as found in versions gcc-5/5.3.0-3.
Ignoring request to alter fixed versions of bug #807128 to the same values 
previously set
> retitle -1 nmu: gcc-5_5.3.0-3
Bug #807128 [release.debian.org] gcc-5-base: Differing changelog.Debian.gz 
between :i386 and :amd64
Changed Bug title to 'nmu: gcc-5_5.3.0-3' from 'gcc-5-base: Differing 
changelog.Debian.gz between :i386 and :amd64'
> user release.debian@packages.debian.org
Unknown command or malformed arguments to command.

> usertag -1 binnmu
Unknown command or malformed arguments to command.


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

Bug#807038: marked as done (perl/experimental: FTBFS on powerpc: t/op/sprintf2.t failure)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 10:23:10 +
with message-id 
and subject line Bug#807038: fixed in perl 5.22.1~rc3-2
has caused the Debian Bug report #807038,
regarding perl/experimental: FTBFS on powerpc: t/op/sprintf2.t failure
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.)


-- 
807038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl
Version: 5.22.1~rc3-1
Severity: serious
Tags: upstream

This package failed to build on powerpc and ppc64.

  
https://buildd.debian.org/status/fetch.php?pkg=perl=powerpc=5.22.1%7Erc3-1=1449230321
  
https://buildd.debian.org/status/fetch.php?pkg=perl=ppc64=5.22.1%7Erc3-1=1449231009

  t/op/sprintf2 . # Failed test 
1451 - at op/sprintf2.t line 671
  #  got '0x1p+1020
  # '
  # expected /(?^:^0x1.0{522}1p\+1020$)/
  # Failed test 1452 - at op/sprintf2.t line 673
  #  got '0x1p+1021
  # '
  # expected /(?^:^0x1.0{523}8p\+1021$)/
  # Failed test 1453 - at op/sprintf2.t line 675
  #  got '0x1p+1022
  # '
  # expected /(?^:^0x1.0{523}4p\+1022$)/
  # Failed test 1454 - at op/sprintf2.t line 677
  #  got '0x1p+1023
  # '
  # expected /(?^:^0x1.0{523}2p\+1023$)/
  # Failed test 1455 - at op/sprintf2.t line 679
  #  got '0x1p+1023
  # '
  # expected /(?^:^0x1.0{523}1p\+1023$)/
  # Failed test 1456 - at op/sprintf2.t line 681
  #  got '0x1p+1023
  # '
  # expected /(?^:^0x1.0{524}8p\+1023$)/
  FAILED at test 1451
  
I'm reporting this upstream.
-- 
Niko Tyni   nt...@debian.org 
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.22.1~rc3-2

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated 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: Sat, 05 Dec 2015 11:03:44 +0200
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.22 libperl-dev perl-modules-5.22 
perl
Architecture: source
Version: 5.22.1~rc3-2
Distribution: experimental
Urgency: low
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Description:
 libperl-dev - Perl library: development files
 libperl5.22 - shared Perl library
 perl   - Larry Wall's Practical Extraction and Report Language
 perl-base  - minimal Perl system
 perl-debug - debug-enabled Perl interpreter
 perl-doc   - Perl documentation
 perl-modules-5.22 - Core Perl modules
Closes: 801523 807038 807086
Changes:
 perl (5.22.1~rc3-2) experimental; urgency=low
 .
   * Fix a podlators test failure when building under SOURCE_DATE_EPOCH.
 (Closes: #807086)
   * Apply upstream patch to skip tests only intended for long double
 configurations, failing on big-endian architectures. (Closes: #807038)
   * Slightly patch Devel-PPPort to make its XS code reproducible
 rather than vary with system file ordering. (Closes: #801523)
Checksums-Sha1:
 1abdbf02f6570ae8d505997b07edc53a1d5d4210 2348 perl_5.22.1~rc3-2.dsc
 db8591fc27d27ee7a97291bad008f9f8df758afd 110684 perl_5.22.1~rc3-2.debian.tar.xz
Checksums-Sha256:
 0585be9a8e9e6a49ff51cf136d42b7b99f3c8c781a8c6559af9b3ea0bff42fab 2348 
perl_5.22.1~rc3-2.dsc
 813da6979bcc22f4c2321d85590603860a8ca1c2b755e90c166c0a4801c52b77 110684 
perl_5.22.1~rc3-2.debian.tar.xz
Files:
 67cb64e70a458c85e3e1f13da944c4f1 2348 perl standard perl_5.22.1~rc3-2.dsc
 876eaa163ab032a5d574c04702fa8bcd 110684 perl standard 
perl_5.22.1~rc3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWYrb3AAoJEC7A/7O3MBsfckwQALspD4RpklctteNtbhcTejDd
D4O0dRJk2npULedBex5u+BdI+9MxqTa0tJymzdfObuiYPZaC+sLYDm09xSFvtIbz
94Sp087vWEE7HdUdjVPFma6etBPcRxbt0hB+UehzD443ZeLmAriMuGzfWPwpIge0
xnolO+3/c2dmKok/xBA997Wld8oPi9rOqy7y4q3Rt3MCj32gzHPvxX+1ufvlFNxb
NKdaRo4kRA5Gwq4mFc8sHR3Jislk9T/hhAQ6ovEdMQTUEA6+2hDuUgRUO1P0b7Se
GTWGlfoyfuKI312Q6xA0zqgfIlIqTOBGtSnv/yR1EfVnto/YDTDjIy6gQrxmy0kJ

Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

[Neil Williams]

Package: python-django
Version: 1.9-1
Severity: grave
Justification: renders package unusable

http://paste.debian.net/341382/

http://paste.debian.net/341383/

I had previously tested django1.9 from experimental and have prepared changes 
which allow
lava-server to run and for all the unit tests to pass. When the version from 
unstable appears,
localhost fails with a new HTTP500 import error and the unit tests fail with a 
new import
error.

Testing against experimental MUST provide a reliable indicator that the upgrade 
in unstable
will continue to operate or there is no point in having the upload in 
experimental in the
first place!

There hasn't been enough time between 1.8 and 1.9 to even get the upstream 
changes for 1.8
uploaded to unstable and now 1.9 has completely broken even those changes 
*despite* full
testing of 1.9 in experimental.

The django upgrade process in Debian is fundamentally broken and is wasting 
massive amounts
of time. There is no point watching or testing from experimental - taking a 
month of upstream
time to get the fixes in - when the actual version has unrelated breakage.

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

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

Versions of packages python-django depends on:
ii  python-django-common  1.9-1
pn  python:any

Versions of packages python-django recommends:
ii  libjs-jquery 1.11.3+dfsg-4
ii  python-sqlparse  0.1.18-1
ii  python-tz2012c+dfsg-0.1

Versions of packages python-django suggests:
pn  bpython
pn  geoip-database-extra | geoip-database-contrib  
ii  gettext0.19.6-1
pn  ipython
pn  libgdal1   
ii  python-bcrypt  0.4-2+b2
ii  python-django-doc  1.9-1
ii  python-flup1.0.2-5
pn  python-memcache
pn  python-mysqldb 
ii  python-pil 3.0.0-1
ii  python-psycopg22.6.1-1+b1
pn  python-sqlite  
ii  python-yaml3.11-3

-- no debconf information

Bug#807097: testing is fine, as *was* experimental.

[Neil Williams]

Downgrading to testing fixes both the server import error and the unit
test import error. Neither of these issues were seen with the version
of 1.9 that was actually in experimental.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpMEYlQysxlW.pgp
Description: OpenPGP digital signature

Bug#802461: marked as done (dolphin4: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/kde4/dolphinpart.so)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 11:22:03 +
with message-id 
and subject line Bug#802461: fixed in kde-baseapps 4:15.08.3-1
has caused the Debian Bug report #802461,
regarding dolphin4: fails to upgrade from 'jessie' - trying to overwrite 
/usr/lib/kde4/dolphinpart.so
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.)


-- 
802461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dolphin4
Version: 4:15.08.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package dolphin4.
  Preparing to unpack .../dolphin4_4%3a15.08.2-1_amd64.deb ...
  Unpacking dolphin4 (4:15.08.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dolphin4_4%3a15.08.2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/kde4/dolphinpart.so', which is also in package 
dolphin 4:4.14.2-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

andreas


dolphin=4%4.14.2-1_dolphin4=4%15.08.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kde-baseapps
Source-Version: 4:15.08.3-1

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

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

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated kde-baseapps 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 Dec 2015 12:38:39 +0100
Source: kde-baseapps
Binary: kde-baseapps kdebase-apps kde-baseapps-bin kdebase-bin 
kde-baseapps-data kdepasswd kfind dolphin4 konqueror konqueror-nsplugins 
konq-plugins libkonq5abi1 libkonq-common libkonq5-templates libkonq5-dev 
libkonqsidebarplugin4a libkonqsidebarplugin-dev plasma-widget-folderview 
kde-baseapps-dbg kdebase-dbg
Architecture: source
Version: 4:15.08.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 dolphin4   - file browser
 kde-baseapps - base applications from the official KDE release (meta-package)
 kde-baseapps-bin - core binaries for the KDE base applications
 kde-baseapps-data - shared data files for the KDE base applications
 kde-baseapps-dbg - debugging symbols for the KDE base applications module
 kdebase-apps - Transitional package for kde-baseapps
 kdebase-bin - Transitional package for new kde-baseapps
 kdebase-dbg - Transitional package for kde-baseapps-dbg
 kdepasswd  - graphical password changing utility
 kfind  - file search utility
 konq-plugins - plugins for Konqueror, the KDE file/web/document browser
 konqueror  - advanced file manager, web browser and document viewer
 konqueror-nsplugins - Netscape plugin support for Konqueror
 libkonq-common - core Konqueror library - support files
 libkonq5-dev - development files for the Konqueror libraries
 libkonq5-templates - data files for the Konqueror libraries
 libkonq5abi1 - core libraries for Konqueror
 libkonqsidebarplugin-dev - konqueror sidebar plugin library development files
 libkonqsidebarplugin4a - konqueror sidebar plugin library
 plasma-widget-folderview - plasma widget showing the content of a folder
Closes: 802461
Changes:
 kde-baseapps (4:15.08.3-1) unstable; urgency=medium
 .
   * Add missing Breaks/Replaces. (Closes: #802461) Thanks to Andreas Beckmann
   * New upstream release (15.08.3).
Checksums-Sha1:
 1277070c0997b169f6d0ab6c2515eed8ea0f7d61 3642 kde-baseapps_15.08.3-1.dsc
 8bfb48e04366f7db8806de1bd05fdfe1323187de 2051396 

Processed: reassign 807015 to xserver-xorg-core

[Debian Bug Tracking System]

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

> reassign 807015 xserver-xorg-core 2:1.17.2-2
Bug #807015 [xinit] xinit: startx freezes, mouse and keyboard don't work
Bug reassigned from package 'xinit' to 'xserver-xorg-core'.
No longer marked as found in versions xinit/1.3.4-3.
Ignoring request to alter fixed versions of bug #807015 to the same values 
previously set
Bug #807015 [xserver-xorg-core] xinit: startx freezes, mouse and keyboard don't 
work
Marked as found in versions xorg-server/2:1.17.2-2.
> thanks
Stopping processing here.

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

Bug#807086: marked as done (perl/experimental: FTBFS: cpan/podlators/t/devise-date failure)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 10:23:10 +
with message-id 
and subject line Bug#807086: fixed in perl 5.22.1~rc3-2
has caused the Debian Bug report #807086,
regarding perl/experimental: FTBFS: cpan/podlators/t/devise-date failure
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.)


-- 
807086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl
Version: 5.22.1~rc3-1
Severity: serious
Tags: upstream patch
X-Debbugs-Cc: Russ Allbery 

This package failed to build on ppc64el and mips64el:

  cpan/podlators/t/devise-date .. #   Failed 
test 'devise_date matches strftime'
  #   at t/devise-date.t line 20.
  #  got: '2015-12-04'
  # expected: '2015-12-05'
  # Looks like you failed 1 test of 6.
  FAILED at test 1
  
This is because we now set SOURCE_DATE_EPOCH to the latest
debian/changelog time stamp, and those builds happened on the next day.

Turns out the backported SOURCE_DATE_EPOCH support from podlators-4.00
doesn't itself survive being build with SOURCE_DATE_EPOCH (or
POD_MAN_DATE, for that matter) set. Patch attached.
-- 
Niko Tyni   nt...@debian.org
>From aee8ad90d019667a85e5653f8ec35fc74aa81491 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sat, 5 Dec 2015 10:08:13 +0200
Subject: [PATCH] Guard for building with SOURCE_DATE_EPOCH or POD_MAN_DATE set

The strftime test expects the current time rather than anything
in the environment.
---
 t/man/devise-date.t | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/t/man/devise-date.t b/t/man/devise-date.t
index a6ceba1..8a1c06e 100755
--- a/t/man/devise-date.t
+++ b/t/man/devise-date.t
@@ -14,6 +14,9 @@ use POSIX qw(strftime);
 
 use Test::More tests => 6;
 
+local $ENV{SOURCE_DATE_EPOCH};
+local $ENV{POD_MAN_DATE};
+
 # Check that the results of device_date matches strftime.  There is no input
 # file name, so this will use the current time.
 my $parser = Pod::Man->new;
-- 
2.6.2

--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.22.1~rc3-2

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated 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: Sat, 05 Dec 2015 11:03:44 +0200
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.22 libperl-dev perl-modules-5.22 
perl
Architecture: source
Version: 5.22.1~rc3-2
Distribution: experimental
Urgency: low
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Description:
 libperl-dev - Perl library: development files
 libperl5.22 - shared Perl library
 perl   - Larry Wall's Practical Extraction and Report Language
 perl-base  - minimal Perl system
 perl-debug - debug-enabled Perl interpreter
 perl-doc   - Perl documentation
 perl-modules-5.22 - Core Perl modules
Closes: 801523 807038 807086
Changes:
 perl (5.22.1~rc3-2) experimental; urgency=low
 .
   * Fix a podlators test failure when building under SOURCE_DATE_EPOCH.
 (Closes: #807086)
   * Apply upstream patch to skip tests only intended for long double
 configurations, failing on big-endian architectures. (Closes: #807038)
   * Slightly patch Devel-PPPort to make its XS code reproducible
 rather than vary with system file ordering. (Closes: #801523)
Checksums-Sha1:
 1abdbf02f6570ae8d505997b07edc53a1d5d4210 2348 perl_5.22.1~rc3-2.dsc
 db8591fc27d27ee7a97291bad008f9f8df758afd 110684 perl_5.22.1~rc3-2.debian.tar.xz
Checksums-Sha256:
 0585be9a8e9e6a49ff51cf136d42b7b99f3c8c781a8c6559af9b3ea0bff42fab 2348 
perl_5.22.1~rc3-2.dsc
 813da6979bcc22f4c2321d85590603860a8ca1c2b755e90c166c0a4801c52b77 110684 
perl_5.22.1~rc3-2.debian.tar.xz
Files:
 67cb64e70a458c85e3e1f13da944c4f1 2348 perl standard perl_5.22.1~rc3-2.dsc
 876eaa163ab032a5d574c04702fa8bcd 110684 perl standard 
perl_5.22.1~rc3-2.debian.tar.xz

-BEGIN PGP 

Bug#807015: xinit: startx freezes, mouse and keyboard don't work

[Laurent Bigonville]

On Sat, 5 Dec 2015 07:55:54 +1100 Craig Sanders  wrote:
> On Fri, Dec 04, 2015 at 01:57:53PM +0100, Laurent Bigonville wrote:
> > Are you using systemd?
>
> Nope, this particular machine is still sysvinit.
>
> It also has over 20 years worth of cruft on it, as i first built it in
> 1994 and have continuously upgraded it (with debian unstable) ever since.
>
> > is libpam-systemd installed on your machine?
>
> Yes, because without it several important packages would be uninstalled,
> including libvirt packages for some unfathomable reason - it's 
impossible to
> have a completely non-systemd machine in debian, you can either have 
systemd

> or you can have a hybrid of systemd + whatever else. systemd, or at least
> parts of it, is mandatory.
>
>
> It is not enabled in /etc/pam.d/ though. None of the files in there use
> it.
>
> and, yes, I have tried it with libpam_systemd enabled. Makes no 
difference.

>
>
> > If it's not the case, try to install xserver-xorg-legacy and look at
> > Xwrapper.config man page
>
> What good would that do? What would it fix, and how? I am running
> neither legacy drivers nor non-linux kernels.
>
> startx worked without this until recently, i'd rather not digress into
> installing and configuring random packages unless there's a good and
> clearly defined reason for it.

Since version 2:1.17.2-2, the xserver is trying running as non-root, but 
you need systemd  for this.


If you don't have systemd installed on your machine, you need a setuid 
wrapper so the server is still started as root. This wrapper is 
installed by the xserver-xorg-legacy package.


I don't think it's a good idea to add your user into the input group.

Laurent Bigonville

Bug#806243: [libminc] Test issues when building on mipsel architecture (#66)

[James Cowgill]

On Sat, 2015-12-05 at 18:21 +0100, Andreas Tille wrote:
> Hi,
> 
> I'm just forwarding this mail from upstream.  From my perspective it is
> possibly not a bug in libminc but rather a problem of certain mips
> hardware. 

I haven't looked at this build failure in particular, but I do know the
FPUs on the Loongson machines are a little suspect (giving _almost_
correct answers to _most_ things) so I would not be surprised if this
was a hardware problem.

> I wonder in how far this is a serious bug of libminc and should be
> downgraded to important (at maximum).

Since libminc has never successfully built on mipsel, this bug
shouldn't have been serious in the first place (regardless of what was
causing it).

James

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

Bug#807128: gcc-5-base: Differing changelog.Debian.gz between :i386 and :amd64

[cosimo]

On 05/12/2015 20:37, Matthias Klose wrote:
> no binNMU please.
>
> On 05.12.2015 19:25, James McCoy wrote:
>> Control: reassign -1 release.debian.org
>> Control: retitle -1 nmu: gcc-5_5.3.0-3
>> Control: user release.debian@packages.debian.org
>> Control: usertag -1 binnmu
>>
>> nmu gcc-5_5.3.0-3 . amd64 . unstable . -m "Rebuild to fix M-A
>> installability"
>>
>> On Sat, Dec 05, 2015 at 01:00:20PM -0500, James McCoy wrote:
>>> Unpacking gcc-5-base:amd64 (5.3.0-3) over (5.2.1-27) ...
>>> Preparing to unpack .../gcc-5-base_5.3.0-3_i386.deb ...
>>> Unpacking gcc-5-base:i386 (5.3.0-3) over (5.2.1-27) ...
>>> dpkg: error processing archive
>>> /var/cache/apt/archives/gcc-5-base_5.3.0-3_i386.deb (--unpack):
>>>   trying to overwrite shared
>>> '/usr/share/doc/gcc-5-base/changelog.Debian.gz', which is different
>>> from other instances of package gcc-5-base:i386
>>>
>>> The :amd64 package (built on the buildd) has unstable as the target
>>> distribution in the changelog, but the (maintainer built) :i386 package
>>> has experimental, thus causing the mismatch between the two.
>>
>> Where :i386 and :amd64 were built is reversed, but the end result is the
>> same.
>>
>> Cheers,
>>
>
Same thing here:

Preconfiguring packages ...
(Reading database ... 160353 files and directories currently installed.)
Preparing to unpack .../gcc-5-base_5.3.0-3_i386.deb ...
Unpacking gcc-5-base:i386 (5.3.0-3) over (5.2.1-27) ...
dpkg: error processing archive
/var/cache/apt/archives/gcc-5-base_5.3.0-3_i386.deb (--unpack):
 trying to overwrite shared
'/usr/share/doc/gcc-5-base/changelog.Debian.gz', which is different from
other instances of package gcc-5-base:i386
Errors were encountered while processing:
 /var/cache/apt/archives/gcc-5-base_5.3.0-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
dpkg: dependency problems prevent configuration of libgcc1:i386:
 libgcc1:i386 depends on gcc-5-base (= 5.3.0-3); however:
  Version of gcc-5-base:i386 on system is 5.2.1-27.

dpkg: error processing package libgcc1:i386 (--configure):
 dependency problems - leaving unconfigured
dpkg: error processing package gcc-5-base:amd64 (--configure):
 package gcc-5-base:amd64 5.3.0-3 cannot be configured because
gcc-5-base:i386 is at a different version (5.2.1-27)
dpkg: dependency problems prevent configuration of libgcc1:amd64:
 libgcc1:amd64 depends on gcc-5-base (= 5.3.0-3); however:
  Package gcc-5-base:amd64 is not configured yet.

dpkg: error processing package libgcc1:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libgcc1:i386
 gcc-5-base:amd64
 libgcc1:amd64




signature.asc
Description: OpenPGP digital signature

Bug#804586: marked as done (qtiplot: FTBFS: Error: pdflatex compilation failed)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 23:43:51 +
with message-id 
and subject line Bug#804586: fixed in qtiplot 0.9.8.9-11
has caused the Debian Bug report #804586,
regarding qtiplot: FTBFS: Error: pdflatex compilation 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.)


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

Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 21183/65536 hits=201203 misses=21385
finished...
/usr/bin/make -C manual -f Makefile all
make[2]: Entering directory '/qtiplot-0.9.8.9/manual'
docbook2html -d qtiplot.dsl docbook-en/index.docbook -e no-valid
Using catalogs: /etc/sgml/catalog
Using stylesheet: /qtiplot-0.9.8.9/manual/qtiplot.dsl
Working on: /qtiplot-0.9.8.9/manual/docbook-en/index.docbook
Done.
dblatex -o qtiplot-manual-en.pdf -c dblatex.conf docbook-en/index.docbook
Build the book set list...
/qtiplot-0.9.8.9/manual/docbook-en/reference.docbook:1103: element sect3: 
validity error : ID fft-cmd already defined

   ^
/qtiplot-0.9.8.9/manual/docbook-en/reference.docbook:1328: element sect2: 
validity error : ID recalculate-cmd already defined
 
() 
()
^
/qtiplot-0.9.8.9/manual/docbook-en/reference.docbook:1352: element sect2: 
validity error : ID smooth-cmd already defined
  
^
/qtiplot-0.9.8.9/manual/docbook-en/dialogs.docbook:420: element figure: 
validity error : ID fig-custom-curves-pie-2 already defined
  

...

Build index.docbook.pdf
pdflatex failed
index.docbook.tex:5947: Argument of \GTS@CdrTwo has an extra }.
index.docbook.tex:5947: leading text: \caption\label
index.docbook.tex:5947: Paragraph ended before \GTS@CdrTwo was complete.

...

index.docbook.aux:1366: Extra }, or forgotten \endgroup.
index.docbook.aux:1366: leading text: \newlabel{}{{5.57}{131}{\par }
index.docbook.aux:1366: Extra }, or forgotten \endgroup.
index.docbook.aux:1366: leading text: ...bel{}{{5.57}{131}{\par 
}{figure.5.57}{}}
Unexpected error occured
Error: pdflatex compilation failed
Makefile:13: recipe for target 'pdf' failed
make[2]: *** [pdf] Error 1

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated qtiplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 06 Dec 2015 00:07:21 +0100
Source: qtiplot
Binary: qtiplot qtiplot-doc
Architecture: source
Version: 0.9.8.9-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Description:
 qtiplot- data analysis and scientific plotting
 qtiplot-doc - data analysis and scientific plotting (documentation)
Closes: 804586 805534 805841 806871
Changes:
 qtiplot (0.9.8.9-11) unstable; urgency=medium
 .
   [ Damir Islamov ]
   * [846688b] Fix compilation with GSL2. (Closes: #805841)
 .
   [ Mirko Scholz ]
   * [fc32fcf] Fix stack overflow in Correlation.cpp. (Closes: #805534)
 .
   [ Anton Gladky ]
   * [9e62e36] Disable building of manual_en.pdf. (Closes: #804586, #806871)
   * [4fb51fd] Respect all versions of GSL.
Checksums-Sha1:
 a068259261ef84eb9ab6c84de3cfd033ae7c17c1 2532 qtiplot_0.9.8.9-11.dsc
 1fbd098b35b8bbe97361ac6f4627a11053296778 

Bug#807128: gcc-5-base: Differing changelog.Debian.gz between :i386 and :amd64

[James McCoy]

On Sat, Dec 05, 2015 at 08:37:15PM +0100, Matthias Klose wrote:
> no binNMU please.

Why?  Are you planning to do a sourceful upload?  If not, that would
resolve the installability issues that people are going to encounter.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Processed: affects 807128

[Debian Bug Tracking System]

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

> affects 807128 gcc-5-base libgcc1
Bug #807128 [release.debian.org] nmu: gcc-5_5.3.0-3
Added indication that 807128 affects gcc-5-base and libgcc1
> thanks
Stopping processing here.

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

Bug#802671: marked as done (CVE-2015-7940: bouncycastle: ECC private keys can be recovered via invalid curve attack)

[Debian Bug Tracking System]

Your message dated Sun, 06 Dec 2015 01:19:15 +
with message-id 
and subject line Bug#802671: fixed in bouncycastle 1.51-2
has caused the Debian Bug report #802671,
regarding CVE-2015-7940: bouncycastle: ECC private keys can be recovered via 
invalid curve attack
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.)


-- 
802671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bouncycastle
Version: 1.44+dfsg-2
Severity: serious
Tags: security
Control: fixed -1 1.51-1

Hello,

bouncycastle 1.49 in stable/testing/unstable (and 1.44 in wheezy/squeeze)
is vulnerable to an invalid curve attack as described here:
https://web-in-security.blogspot.ca/2015/09/practical-invalid-curve-attacks.html

This is fixed in version 1.51 (in experimental).

The upstream patches that fix this issue should be those ones:
https://github.com/bcgit/bc-java/commit/5cb2f05
https://github.com/bcgit/bc-java/commit/e25e94a

A CVE has been requested here:
http://www.openwall.com/lists/oss-security/2015/10/22/7

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: bouncycastle
Source-Version: 1.51-2

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated bouncycastle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Dec 2015 00:34:19 +0100
Source: bouncycastle
Binary: libbcprov-java libbcprov-java-doc libbcmail-java libbcmail-java-doc 
libbcpkix-java libbcpkix-java-doc libbcpg-java libbcpg-java-doc
Architecture: source
Version: 1.51-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libbcmail-java - Bouncy Castle generators/processors for S/MIME and CMS
 libbcmail-java-doc - Bouncy Castle generators/processors for S/MIME and CMS 
(Documenta
 libbcpg-java - Bouncy Castle generators/processors for OpenPGP
 libbcpg-java-doc - Bouncy Castle generators/processors for OpenPGP 
(Documentation)
 libbcpkix-java - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS, OCSP, 
CMP,
 libbcpkix-java-doc - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS... 
(Document
 libbcprov-java - Bouncy Castle Java Cryptographic Service Provider
 libbcprov-java-doc - Bouncy Castle Java Cryptographic Service Provider 
(Documentation)
Closes: 798343 799007 802671
Changes:
 bouncycastle (1.51-2) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable. (Closes: #799007)
   * The new upstream release 1.51 fixes CVE-2015-7940. (Closes: #802671)
   * Declare compliance with Debian Policy 3.9.6.
   * Vcs-Browser: Use https.
   * Add fix-encoding.patch.
 This prevents an error when creating javadoc which would otherwise lead to
 empty -doc packages. Drop 01_build.patch because it once tried to
 accomplish the same but it is obsolete now.
 Thanks to dean for the report. (Closes: #798343)
Checksums-Sha1:
 78558778214b1cd34438b25a16a3657e22972702 2662 bouncycastle_1.51-2.dsc
 febdf5b551d4ca7d5ac64c0cf54b8ea492ddf243 9596 bouncycastle_1.51-2.debian.tar.xz
Checksums-Sha256:
 0575ddd82dbdf3957efa4b3d4def9cbddd7baa1b3354d40f546f9aced08c4b75 2662 
bouncycastle_1.51-2.dsc
 8373101dc7d7c3fd1a61eef0169b996cd902637d7950238a35b9a45aabc377a0 9596 
bouncycastle_1.51-2.debian.tar.xz
Files:
 a465b952faecf683151896c687425731 2662 java optional bouncycastle_1.51-2.dsc
 

Bug#795141: marked as done (zeitgeist-explorer: FTBFS: invalid dates in changelog)

[Debian Bug Tracking System]

Your message dated Sun, 06 Dec 2015 01:23:47 +
with message-id 
and subject line Bug#795141: fixed in zeitgeist-explorer 0.2-1.1
has caused the Debian Bug report #795141,
regarding zeitgeist-explorer: FTBFS: invalid dates in changelog
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.)


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

The package fails to build.  dpkg has recently[1] been made more
sensitive to date formats in the changelog, although it does not give
good errors.  Please use standard[2] format dates in your changelog (dch
gets them right!).

The only error printed is, at some point during the build:
Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.20/Time/Piece.pm line 
469, <$filehandle> line 5.

[1]: https://tracker.debian.org/news/702682
[2]: https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/zeitgeist-explorer.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: zeitgeist-explorer
Source-Version: 0.2-1.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Dec 2015 02:07:20 +0100
Source: zeitgeist-explorer
Binary: zeitgeist-explorer
Architecture: source all
Version: 0.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Manish Sinha 
Changed-By: Laurent Bigonville 
Description:
 zeitgeist-explorer - GUI application for monitoring and debugging zeitgeist
Closes: 795141
Changes:
 zeitgeist-explorer (0.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix date in debian/changelog to fix FTBFS (Closes: #795141)
Checksums-Sha1:
 e69703f37cf24a6261ac26776388fefa76fb86fd 1570 zeitgeist-explorer_0.2-1.1.dsc
 1dccd5a462fd93ed948400cb993692ebc5c26949 2228 
zeitgeist-explorer_0.2-1.1.debian.tar.xz
 1de0aee202cedcb7599abed744ca1053bbfcb1e4 16946 
zeitgeist-explorer_0.2-1.1_all.deb
Checksums-Sha256:
 174e9f65f5bc824eced56b38a8116d0b2a06aa8d8ee38670726597494be81e08 1570 
zeitgeist-explorer_0.2-1.1.dsc
 9956f679b549ccc7abce67dfb0e4981b2d3eb06501f42be5ff5d407e04b9a048 2228 
zeitgeist-explorer_0.2-1.1.debian.tar.xz
 e22f56f2af9bbe25178ab6c92fe1d58c0bf6478915143c997fdd72699366d267 16946 
zeitgeist-explorer_0.2-1.1_all.deb
Files:
 1b00ea114541e4cc8f2221f879350aae 1570 devel extra 
zeitgeist-explorer_0.2-1.1.dsc
 4fb4a6eb20b5538486452ddfe25491dc 2228 devel extra 
zeitgeist-explorer_0.2-1.1.debian.tar.xz
 890be3b605720661606c0a9ac803dc9b 16946 devel extra 
zeitgeist-explorer_0.2-1.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEbBAEBCAAGBQJWY4tQAAoJEB/FiR66sEPVNDkH8gNYI1wVkZmJI9VrEGUpIGVL
QI0RgKAsh+G0StodFeydrk+TbpxYI3H2GMGh0D3ozTKeZ3I3t6EyZyTqPvGEWxKJ
iceW638uTVwLC8j85TG4ItgeB/i5ezbfqB+38dFZhawgMxocL3XhFo9mbNs93b+2
wFST0aVQ7iydAzRbhAbOCiEk/PJUcDkIfUn0xD1yvfhpl03beLE+n0fY0HbIOmrk
i5CK7d8phWeczlnvGLPL/66JlXGlwpgBRHXCuchVxIszNaaalA9dPlKW2nrkMO5U
YTQGh6ELxhnKom8xzjcT7gTjCyyKKorXJakjPuS49B54Mch1iUyMMbUj+FIFsg==
=lv2J
-END PGP SIGNATURE End Message ---

Bug#806769: marked as done (FTBS: failed test on mipsel architecture: random Bus error emitted from GOMP)

[Debian Bug Tracking System]

Your message dated Sun, 06 Dec 2015 01:22:55 +
with message-id 
and subject line Bug#806769: fixed in normaliz 3.0.0+ds-3
has caused the Debian Bug report #806769,
regarding FTBS: failed test on mipsel architecture: random Bus error emitted 
from GOMP
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.)


-- 
806769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: normaliz
Version: 3.0.0+ds-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hello Folks:

On mipsel architecture, normaliz is subject to random `Bus error(s)' 
that
are emitted from GOMP. A GDB backtrace typically reads:

--8><--
[...]
Starting program: /home/calculus/normaliz/normaliz-00/normaliz/_build/normaliz 
-h test-h/cut.in
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x77913450 (LWP 24948)]
[New Thread 0x77113450 (LWP 24949)]
[New Thread 0x76913450 (LWP 24950)]

Program received signal SIGBUS, Bus error.
[Switching to Thread 0x77113450 (LWP 24949)]
0x77b1ef60 in GOMP_loop_ull_dynamic_start () from 
/usr/lib/mipsel-linux-gnu/libgomp.so.1
#0  0x77b1ef60 in GOMP_loop_ull_dynamic_start () from 
/usr/lib/mipsel-linux-gnu/libgomp.so.1
#1  0x77b1ee7c in GOMP_loop_ull_dynamic_start () from 
/usr/lib/mipsel-linux-gnu/libgomp.so.1
Backtrace stopped: frame did not save the PC
(gdb)
--><8

For the record,
Jerome


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

Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages normaliz depends on:
ii  normaliz-bin  3.0.0+ds-1

normaliz recommends no packages.

Versions of packages normaliz suggests:
ii  singular  4.0.2-p2+ds-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: normaliz
Source-Version: 3.0.0+ds-3

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated normaliz 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: Tue, 01 Dec 2015 04:15:03 +
Source: normaliz
Binary: normaliz libnormaliz0 libnormaliz0-dev libnormaliz0-dev-common 
normaliz-bin libnormaliz0-dbg normaliz-doc
Architecture: source
Version: 3.0.0+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 libnormaliz0 - math computing tools for affine monoids, rational polytopes and 
c
 libnormaliz0-dbg - math computing tools for affine monoids, rational polytopes 
and c
 libnormaliz0-dev - math computing tools for affine monoids, rational polytopes 
and c
 libnormaliz0-dev-common - math computing tools for affine monoids, rational 
polytopes and c
 normaliz   - math computing tools for affine monoids, rational polytopes and c
 normaliz-bin - math computing tools for affine monoids, rational polytopes and 
c
 normaliz-doc - math computing tools for affine monoids, rational polytopes and 
c
Closes: 806769
Changes:
 normaliz (3.0.0+ds-3) unstable; urgency=medium
 .
   * FTBFS fix release (Closes: #806769), disable OMP support on mipsel arch.
   * Debianization:
 - debian/rule, see above.
Checksums-Sha1:
 217d563524791ad612b49a7e006a909052afe750 2510 normaliz_3.0.0+ds-3.dsc
 669903b810772ed39daec30e780edbb6baeb7a18 8720 normaliz_3.0.0+ds-3.debian.tar.xz
Checksums-Sha256:
 

Bug#805565: [Pkg-utopia-maintainers] Bug#805565: network-manager: ppp new upstream release; dh_ppp

[Chris Boot]

On 2015-12-04 23:38, Michael Biebl wrote:
> Hi
> 
> Am 04.12.2015 um 10:06 schrieb Chris Boot:
>> Control: severity serious
>>
>> Hi Michael,
>>
>> I have now uploaded ppp 2.4.7-1+1 to unstable, therefore the ppp plugin
>> this package ships is now broken in sid. Please upload a patched version
>> of your package as soon as possible.
>>
>> I would gladly upload an NMU myself but I cannot easily do so at the
>> moment (I am not yet a DD).
> 
> I looked at the resulting package. It has
> 
> Breaks: ppp (>= 2.4.7-2~), ppp (<< 2.4.7-1+~)
> 
> That's overly strict imho. I don't think I want to binNMU/upload NM
> every time there is a debian release of ppp.
> Could we relax those breaks to
> 
> Breaks: ppp (>= 2.4.8), ppp (<< 2.4.7)
> 
> It's unlikely that the plugin path changes in a Debian revision of ppp?

Hi Michael,

The issue is that we may need to break the ABI between upstream releases
of ppp, particularly if the upstream release cycle has huge gaps in like
there was betwen 2.4.5 (in 2009) and 2.4.6 (in 2014).

There is more to the ABI than just the plugin path as I'm sure you're
aware. Any patch affecting various structures or functions within pppd
itself could cause an ABI change that would break plugins, and I want to
avoid that being an issue going forward.

I have thought about this, and thus deliberately overload the version
number of the ppp package to contain an extra ABI component as well as
the normal revision number. See the ppp package's README.source for more
details:

https://sources.debian.net/src/ppp/2.4.7-1%2B1/debian/README.source/

Essentially, the version I uploaded yesterday is 2.4.7-1+1 and I will
only change the ABI revision field if it's absolutely necessary to do
so. I will definitely not be making a habit of changing the ABI in
regular uploads of ppp. My scheme is admittedly unconventional but it
was the neatest way I could think of to achieve my goals.

With that all in mind, though, if I do *need* to make such a bump it
should just be a matter of a binNMU for all the packages that build ppp
plugins, very much like what happens with a soname bump for a shared
library.

I hope this alleviates your concerns.

Regards,
Chris

-- 
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D  C918 F5C8 3C05 D9CE 



signature.asc
Description: OpenPGP digital signature

Bug#807091: xfce4-terminal fails to start with an error message

[Thomas Weber]

Package: xfce4-terminal
Version: 0.6.3-2
Severity: grave
Justification: renders package unusable

Launching xfce4-terminal as normal user gives the following error message in an 
error window:
"Failed to execute child
grantpt failed: Operation not permitted"
After closing the error message, the terminal window appears, but there
is no shell started in it.
If I gain superuser rights via su and execute xfce4-terminal, the
terminal launches (with an error message saying "Failed to connect to
session manager: [...]".

Some reports on the internet suggested that this might be a permission
problem with /dev/pts. However, I do not have an entry for /dev/pts in
my /etc/fstab and the rights are as follows:
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)

This (non-)behaviour of xfce4-terminal is fairly new, but I cannot
pinpoint it to any recent update as I usually keep up just one instance
of the terminal for some time.

Thanks
Thomas


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

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

Versions of packages xfce4-terminal depends on:
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.18.0-1
ii  libc6   2.21-3
ii  libgdk-pixbuf2.0-0  2.32.2-1
ii  libglib2.0-02.46.2-1
ii  libgtk2.0-0 2.24.28-1
ii  libpango-1.0-0  1.38.1-1
ii  libvte9 1:0.28.2-5+b1
ii  libx11-62:1.6.3-1
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-2

Versions of packages xfce4-terminal recommends:
ii  dbus-x11  1.10.6-1

xfce4-terminal suggests no packages.

-- no debconf information

Processed: tagging 807038

[Debian Bug Tracking System]

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

> tags 807038 + patch fixed-upstream
Bug #807038 [perl] perl/experimental: FTBFS on powerpc: t/op/sprintf2.t failure
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.

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

Bug#807038: Perl 5.22.1-RC3 is now available!

[Niko Tyni]

On Fri, Dec 04, 2015 at 02:08:01PM -0600, Craig A. Berry wrote:
> On Fri, Dec 4, 2015 at 12:24 PM, Niko Tyni  wrote:

> > doublekind='4'; looks like those tests get run only on linux
> > with that doublekind.
> 
> Right.  I hadn't noticed the linux-only part before.  These tests came
> in with a fix for a problem reported on Debian PPC64:
> 
> 
> 
> 
> 
> To me the configuration in that ticket looks awfully similar to the
> configuration that now sees test failures, but I could be missing
> something.

The difference was that we don't use -Duselongdouble. 

Jarkko says the tests were only intended for long double configurations
and has added more skip conditions with
 
http://perl5.git.perl.org/perl.git/commit/df3d8cc3eeca597a21c2d7ad7686adbef4df784b

I've tested that this works for us.
-- 
Niko Tyni   nt...@debian.org

Bug#807080: marked as done (libraw1394: Please drop obsolete MAKEDEV call)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 09:37:28 +
with message-id 
and subject line Bug#807080: fixed in libraw1394 2.1.1-2
has caused the Debian Bug report #807080,
regarding libraw1394: Please drop obsolete MAKEDEV call
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.)


-- 
807080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libraw1394
Version: 2.1.1-1
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

Hi Guus,

With the recent change to debhelper to no longer call ldconfig from
maintainer scripts but from triggers instead (debhelper 9.20151004), a bug
has been exposed in the postinst of libraw1394-11 that will make the package
uninstallable after a rebuild with new debhelper.

The maintainer script looks for /dev/MAKEDEV, which is long obsolete.  If it
finds it, it calls a series of commands:

  [ -x /dev/MAKEDEV ] && cd /dev && echo -n "Creating device node 
/dev/raw1394... " && ./MAKEDEV raw1394 && echo "done."

If it *doesn't* find it, the above chain will exit non-zero.

Because this non-zero exit code is part of an && command list, it does *not*
trigger an immediate non-zero exit of the shell, in spite of using set -e.
So with the current build of the package, the maintainer script succeeds,
*because this is not the last command in the script* (it's followed by the
debhelper-provided call to ldconfig).

On a simple rebuild of the package in unstable, this command list *does*
become the last command in the script.  The script therefore gets the exit
code of the last command, which is non-zero, and the package fails to
install.

This bug was discovered as part of the bootstrap of Ubuntu xenial for the
s390x architecture, where because libraw1394-11 is a newly-built package
using a current toolchain, it fails to install.

Since makedev is for all intents and purposes obsoleted by udev, I've
applied the attached patch in Ubuntu, which you are welcome to include in
Debian as well.  I remember seeing some discussion in years past on
debian-devel about how to continue supporting makedev properly for those who
don't want to use udev; if you want to do mailing list archaeology I guess
that's still an option, but Ubuntu doesn't support running without udev so
for us it's sufficient to drop the maintainer script.

Marking this as 'grave' since the package becomes uninstallable on a
no-change rebuild.

The patch has been uploaded to Ubuntu with the following changelog
explanation:

  * Drop buggy call to obsolete /dev/MAKEDEV in the maintainer script, which
if it's the last command (which it is now that ldconfig is being handled
by trigger from debhelper) causes the package to fail to install.


Thanks for considering the patch.
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libraw1394-2.1.1/debian/libraw1394-11.postinst libraw1394-2.1.1/debian/libraw1394-11.postinst
--- libraw1394-2.1.1/debian/libraw1394-11.postinst	2009-07-25 07:39:58.0 -0700
+++ libraw1394-2.1.1/debian/libraw1394-11.postinst	1969-12-31 16:00:00.0 -0800
@@ -1,7 +0,0 @@
-#!/bin/sh -e
-
-if [ "$1" = "configure" ]; then
-	[ -x /dev/MAKEDEV ] && cd /dev && echo -n "Creating device node /dev/raw1394... " && ./MAKEDEV raw1394 && echo "done."
-fi
-
-#DEBHELPER#
diff -Nru libraw1394-2.1.1/debian/libraw1394.postinst.in libraw1394-2.1.1/debian/libraw1394.postinst.in
--- libraw1394-2.1.1/debian/libraw1394.postinst.in	2009-07-25 07:39:58.0 -0700
+++ libraw1394-2.1.1/debian/libraw1394.postinst.in	1969-12-31 16:00:00.0 -0800
@@ -1,10 +0,0 @@
-#!/bin/sh -e
-
-. /usr/share/debconf/confmodule
-db_version 2.0
-
-if [ "$1" = "configure" ]; then
-	[ -x /dev/MAKEDEV ] && cd /dev && echo -n "Creating device node /dev/raw1394... " && ./MAKEDEV raw1394 && echo "done."
-fi
-
-#DEBHELPER#
--- End Message ---
--- Begin Message ---
Source: libraw1394
Source-Version: 2.1.1-2

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

Bug#807086: perl/experimental: FTBFS: cpan/podlators/t/devise-date failure

[Niko Tyni]

Package: perl
Version: 5.22.1~rc3-1
Severity: serious
Tags: upstream patch
X-Debbugs-Cc: Russ Allbery 

This package failed to build on ppc64el and mips64el:

  cpan/podlators/t/devise-date .. #   Failed 
test 'devise_date matches strftime'
  #   at t/devise-date.t line 20.
  #  got: '2015-12-04'
  # expected: '2015-12-05'
  # Looks like you failed 1 test of 6.
  FAILED at test 1
  
This is because we now set SOURCE_DATE_EPOCH to the latest
debian/changelog time stamp, and those builds happened on the next day.

Turns out the backported SOURCE_DATE_EPOCH support from podlators-4.00
doesn't itself survive being build with SOURCE_DATE_EPOCH (or
POD_MAN_DATE, for that matter) set. Patch attached.
-- 
Niko Tyni   nt...@debian.org
>From aee8ad90d019667a85e5653f8ec35fc74aa81491 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sat, 5 Dec 2015 10:08:13 +0200
Subject: [PATCH] Guard for building with SOURCE_DATE_EPOCH or POD_MAN_DATE set

The strftime test expects the current time rather than anything
in the environment.
---
 t/man/devise-date.t | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/t/man/devise-date.t b/t/man/devise-date.t
index a6ceba1..8a1c06e 100755
--- a/t/man/devise-date.t
+++ b/t/man/devise-date.t
@@ -14,6 +14,9 @@ use POSIX qw(strftime);
 
 use Test::More tests => 6;
 
+local $ENV{SOURCE_DATE_EPOCH};
+local $ENV{POD_MAN_DATE};
+
 # Check that the results of device_date matches strftime.  There is no input
 # file name, so this will use the current time.
 my $parser = Pod::Man->new;
-- 
2.6.2

Bug#805565: marked as done (network-manager: ppp new upstream release; dh_ppp)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 22:52:22 +
with message-id 
and subject line Bug#805565: fixed in network-manager 1.0.8-2
has caused the Debian Bug report #805565,
regarding network-manager: ppp new upstream release; dh_ppp
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.)


-- 
805565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager
Severity: important
Tags: sid stretch
User: p...@packages.debian.org
Usertags: ppp-2.4.7-dh-ppp

Dear maintainer,

I have uploaded a new upstream release of ppp to experimental. As you
may be aware, new upstream releases of ppp cause ABI breaks, so the
version of your package currently in sid will stop working. A new
upload of your package will be required in order for it to remain
functional.

With this release of ppp I am also including a new dh_ppp tool in the
ppp-dev package. This will help to avoid having to make manual changes
to packages in future by automatically generating the correct
dependencies on binary packages. If your package build system also
requires the path to the ppp plugins directory, the dh_ppp tool is able
to provide that.

This should allow future ABI transitions to be tracked using the
release team's "ben" transition tracker, and packages should only
require a binary-only NMU to build against the new ABI.

I have prepared a patch for your package to enable to build against the
new version of ppp currently in experimental. I will add the patch to
this bug very shortly (once I have a bug number to add to the
changelog).

I plan to upload ppp-2.4.7 to sid on Friday, 4 December 2015. You will
need to upload a patched version of your package on or shortly after
that date.

Regards,
Chris (ppp maintainer)

-- 
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D  C918 F5C8 3C05 D9CE 
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.0.8-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Dec 2015 22:07:15 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source
Version: 1.0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-dev  - GObject-based client library for NetworkManager (development file
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util2 - network management framework (shared library)
 libnm0 - GObject-based client library for NetworkManager
 network-manager - network management framework (daemon and userspace tools)
 network-manager-dbg - network management framework (debugging symbols)
 network-manager-dev - network management framework (development files)
Closes: 805565
Changes:
 network-manager (1.0.8-2) unstable; urgency=medium
 .
   [ Chris Boot ]
   * Use dh_ppp to generate Breaks for ppp and find the path to the plugin
 directory. (Closes: #805565)
Checksums-Sha1:
 4919bab987bf2f031c05b181c389a8bf7f077468 3541 network-manager_1.0.8-2.dsc
 200c331ee802d94ba91f608bce5a15ba1b5bea6a 46232 
network-manager_1.0.8-2.debian.tar.xz
Checksums-Sha256:
 

Bug#805566: marked as done (network-manager-pptp: ppp new upstream release; dh_ppp)

[Debian Bug Tracking System]

Your message dated Sat, 05 Dec 2015 22:52:27 +
with message-id 
and subject line Bug#805566: fixed in network-manager-pptp 1.0.8-2
has caused the Debian Bug report #805566,
regarding network-manager-pptp: ppp new upstream release; dh_ppp
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.)


-- 
805566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-pptp
Severity: important
Tags: sid stretch
User: p...@packages.debian.org
Usertags: ppp-2.4.7-dh-ppp

Dear maintainer,

I have uploaded a new upstream release of ppp to experimental. As you
may be aware, new upstream releases of ppp cause ABI breaks, so the
version of your package currently in sid will stop working. A new
upload of your package will be required in order for it to remain
functional.

With this release of ppp I am also including a new dh_ppp tool in the
ppp-dev package. This will help to avoid having to make manual changes
to packages in future by automatically generating the correct
dependencies on binary packages. If your package build system also
requires the path to the ppp plugins directory, the dh_ppp tool is able
to provide that.

This should allow future ABI transitions to be tracked using the
release team's "ben" transition tracker, and packages should only
require a binary-only NMU to build against the new ABI.

I have prepared a patch for your package to enable to build against the
new version of ppp currently in experimental. I will add the patch to
this bug very shortly (once I have a bug number to add to the
changelog).

I plan to upload ppp-2.4.7 to sid on Friday, 4 December 2015. You will
need to upload a patched version of your package on or shortly after
that date.

Regards,
Chris (ppp maintainer)

-- 
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D  C918 F5C8 3C05 D9CE 
--- End Message ---
--- Begin Message ---
Source: network-manager-pptp
Source-Version: 1.0.8-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Dec 2015 22:18:43 +0100
Source: network-manager-pptp
Binary: network-manager-pptp network-manager-pptp-gnome
Architecture: source
Version: 1.0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 network-manager-pptp - network management framework (PPTP plugin core)
 network-manager-pptp-gnome - network management framework (PPTP plugin GNOME 
GUI)
Closes: 805566
Changes:
 network-manager-pptp (1.0.8-2) unstable; urgency=medium
 .
   [ Chris Boot ]
   * Use dh_ppp to generate Depends on ppp and to locate the ppp plugins
 directory. (Closes: #805566)
Checksums-Sha1:
 329b31e6dcec35dd98c4897e7c6ceab33c36b0dd 2437 network-manager-pptp_1.0.8-2.dsc
 2c6df0a9ed3accbed62a65d68acf8ebd6c01cbea 6436 
network-manager-pptp_1.0.8-2.debian.tar.xz
Checksums-Sha256:
 fe84c3df0e9c203a9d117c61cecfc278eae723a140d9643c01b96225b1afa39c 2437 
network-manager-pptp_1.0.8-2.dsc
 4d5fafb125a220901949c8310c01ed062c7f0dfe8f19243ba41f130a6400c9dc 6436 
network-manager-pptp_1.0.8-2.debian.tar.xz
Files:
 49755e247a63b7dc49c828e954fb1380 2437 net optional 
network-manager-pptp_1.0.8-2.dsc
 8b570341181d9e8a84c8dc212810d3e4 6436 net optional 
network-manager-pptp_1.0.8-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWY1UcAAoJEGrh3w1gjyLc+xQP/2xwTare+KDn/E+sUokbLou+
nvA3veDq/7Bgf84EI7B2xxpgRhJlWXaxrA+jywRDXuL+0YxkH+Jh8jv3fTsSGOBD
4mSmeth7PqA3abwp40ueBlDHQ28r1EEyCkpFI8/m8EMX8BW6zvwvzavTTjatDJ29
xpngPcz/LQKu+AsWcnvL6Fmu1VfptgOPW/zw6a8oULNHP74wvI8Fb6uRyAkCB5z5
Fa7M+9Mvx8nwbsFqEYhoIIcy0A44eFG0cEd52Un00d8q3Jl9rkPh5n6SGvvmyU0C

Processed: gramps: FTBFS - fix is pending

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #805202 [src:gramps] gramps: FTBFS: test_regular_date_parsed_dmy: Failure: 
ImproperlyConfigured
Added tag(s) pending.

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

Bug#805202: gramps: FTBFS - fix is pending

[Ross Gammon]

Control: tags -1 pending

Hi,

I was expecting this issue as I had a preview of a similar failure in
Ubuntu when Python 3.5 is the default.

I had been waiting for Django 1.8, and now we have Django 1.9 and the
failure still exists.

As the Django webapp in Gramps is not yet enabled (not used), the
simplest thing to do is to exclude nose from looking in that directory
for now.

Regards,

Ross

Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

[Raphael Hertzog]

On Sat, 05 Dec 2015, Neil Williams wrote:
> http://paste.debian.net/341382/

So this one is fairly obvious, I already replied that it's
django.template.base.Origin that you should have used in the first place
since where the code actually is... relying on the fact that it was
also imported in django.template is not very future-proof (when not
documented).

> http://paste.debian.net/341383/

This one is actually documented, add_to_builtins has never been a public
API.

https://docs.djangoproject.com/en/1.9/releases/1.9/#django-template-base-add-to-builtins-is-removed

So what's left on your grave bug report?

Nothing except vitriol against the fact that it was uploaded a bit
hastily. Please take that somewhere else... or express it in a less
confrontional way.

Please close this bug unless you are able to show us a real problem.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#755632: [Python-modules-team] Bug#807101: python-django-voting: Too loose dependency on python-django

[Brian May]

Valentin Lorentz  writes:

> python-django-voting 0.2-1 (the current version in Sid) is not
> compatible with python-django 1.9-1 (the current version in Sid), but
> the dependency specification does not mention this incompatibility: it
> only requires: “python-django (>= 1.0)”.

This is somewhat a confusing report. python-django-voting in unstable
must be compatible with the python-django in unstable or it will not be
installable. Changing the depends to disallow it being installed with
Django 1.9 is not going to magically mean that the package is not
broken.

There is already a serious bug report against python-django-voting, for
Django 1.7 compatability. See #755632

Unfortunately it seems nobody in the python-modules-team is currently
interested in fixing it. I also note that upstream hasn't had a release
since 2012 either. So maybe the package should get dropped from
unstable?

As there is already a bug report that covers the issues on this package,
I will close #807101.

Regards
-- 
Brian May 

Bug#807097: [Python-modules-team] Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

[Brian May]

Raphael Hertzog  writes:

> This one is actually documented, add_to_builtins has never been a public
> API.
>
> https://docs.djangoproject.com/en/1.9/releases/1.9/#django-template-base-add-to-builtins-is-removed

I thought this was removed in Django 1.8 - I remember as it caused me
significant problems at the time.

In my commit message from April I reference the following upstream bug:
https://code.djangoproject.com/ticket/17085

So I don't think you can blame this one on Django 1.9.
-- 
Brian May 

Processed: fix severity

[Debian Bug Tracking System]

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

> severity 805746 serious
Bug #805746 [src:aghermann] aghermann: Fails to build with GSL 2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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