Bug#848850: linux: FTBFS on s390x

[Salvatore Bonaccorso]

Source: linux
Version: 4.8.15-1
Severity: serious
Justification: FTBFS

Hi,

src:linux FTBFS on s390x. I have not investigated the issue, so this
is to track the bug only.

Log: 
https://buildd.debian.org/status/fetch.php?pkg=linux=s390x=4.8.15-1=1482186706

[...]
  XZKERN  arch/s390/boot/compressed/vmlinux.bin.xz
  LD  arch/s390/boot/compressed/piggy.o
ld: arch/s390/boot/compressed/vmlinux.bin.xz: not in ELF format
/??PKGBUILDDIR??/arch/s390/boot/compressed/Makefile:70: recipe for target 
'arch/s390/boot/compressed/piggy.o' failed
make[7]: *** [arch/s390/boot/compressed/piggy.o] Error 1
/??PKGBUILDDIR??/arch/s390/boot/Makefile:22: recipe for target 
'arch/s390/boot/compressed/vmlinux' failed
make[6]: *** [arch/s390/boot/compressed/vmlinux] Error 2
arch/s390/Makefile:117: recipe for target 'bzImage' failed
make[5]: *** [bzImage] Error 2
make[5]: *** Waiting for unfinished jobs
  CC  arch/s390/appldata/appldata_mem.mod.o
[...]

Regards,
Salvatore

Bug#848768: biojava4-live: FTBFS: [javac] /<>/biojava4-live-4.2.4+dfsg/biojava-structure/src/main/java/org/biojava/nbio/structure/symmetry/core/QuatSymmetryDetector.java:27: error: package o

[olivier sallou]

Le mar. 20 déc. 2016 à 08:38, Andreas Tille <ti...@debian.org> a écrit :

> Hi Olivier and Ximin,
>
> I stripped the quote of the build log below but to me it seems to be
> related to the jmol upgrade.
>

I saw the bug this morning, I gonna have a look

>
> Any help to get this fixed would be really welcome.
>
> Kind regards
>
>   Andreas.
>
> On Mon, Dec 19, 2016 at 10:08:48PM +0100, Lucas Nussbaum wrote:
> > Source: biojava4-live
> > Version: 4.2.4+dfsg-1
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20161219 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> > ...
> > > [javac] UndirectedGraph<Integer, DefaultEdge>
> graph = new SimpleGraph<Integer, DefaultEdge>(
> > > [javac]
> ^
> > > [javac]   symbol:   class DefaultEdge
> > > [javac]   location: class SymmetryTools
> > > [javac]
> /<>/biojava4-live-4.2.4+dfsg/biojava-structure/src/main/java/org/biojava/nbio/structure/symmetry/utils/SymmetryTools.java:481:
> error: cannot find symbol
> > > [javac] DefaultEdge.class);
> > > [javac] ^
> > > [javac]   symbol:   class DefaultEdge
> > > [javac]   location: class SymmetryTools
> > > [javac] Note: Some input files use or override a deprecated API.
> > > [javac] Note: Recompile with -Xlint:deprecation for details.
> > > [javac] Note:
> /<>/biojava4-live-4.2.4+dfsg/biojava-structure/src/main/java/org/biojava/nbio/structure/io/mmcif/MetalBondConsumer.java
> uses unchecked or unsafe operations.
> > > [javac] Note: Recompile with -Xlint:unchecked for details.
> > > [javac] 67 errors
> > >
> > > BUILD FAILED
>
> --
> http://fam-tille.de
>

Bug#848809: cwltool: FTBFS: help2man: can't get `--help' info from cwltool/cwltest.py

[Andreas Tille]

Hi Michael,

I spent some time to work on 845982 and to me it seems cwltool is a
moving target with several new upstream releases.  I admit I have no
idea how to cope this.  Could you please take over from here and make
sure cwltool will be included in Stretch?

Kind regards

  Andreas.

On Mon, Dec 19, 2016 at 10:30:17PM +0100, Lucas Nussbaum wrote:
> Source: cwltool
> Version: 1.0.20160209222805-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161219 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > help2man cwltool/cwltest.py -I debian/cwltest.help2man -N -o 
> > debian/cwltest.1 --version-string "$(dpkg-parsechangelog  | grep Version:  
> > | cut -f2 -d\ )"
> > help2man: can't get `--help' info from cwltool/cwltest.py
> > Try `--no-discard-stderr' if option outputs to stderr
> > debian/rules:17: recipe for target 'debian/cwltest.1' failed
> > make[1]: *** [debian/cwltest.1] Error 1
> 
> The full build log is available from:
>
> http://aws-logs.debian.net/2016/12/19/cwltool_1.0.20160209222805-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#848709: marked as done (xserver-xorg-video-geode-dbg: depends on xserver-xorg-core-dbg, which is no longer built)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 07:48:41 +
with message-id 
and subject line Bug#848709: fixed in xserver-xorg-video-geode 2.11.19-1
has caused the Debian Bug report #848709,
regarding xserver-xorg-video-geode-dbg: depends on xserver-xorg-core-dbg, which 
is no longer built
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.)


-- 
848709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-geode-dbg
Version: 2.11.18-2
Severity: serious

Hi,

x-x-v-geode-dbg depends on xserver-xorg-core-dbg, but we no longer build
that, and rely on debhelper creating dbgsym packages instead. Thus, please
drop that dependency. Bonus points if you switch to -dbgsym packages too. :)

Emilio

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

Kernel: Linux 4.8.0-2-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)
--- End Message ---
--- Begin Message ---
Source: xserver-xorg-video-geode
Source-Version: 2.11.19-1

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

Debian distribution maintenance software
pp.
Martin-Éric Racine  (supplier of updated 
xserver-xorg-video-geode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Dec 2016 21:35:07 +0200
Source: xserver-xorg-video-geode
Binary: xserver-xorg-video-geode xserver-xorg-video-geode-dbg
Architecture: source
Version: 2.11.19-1
Distribution: unstable
Urgency: medium
Maintainer: Martin-Éric Racine 
Changed-By: Martin-Éric Racine 
Description:
 xserver-xorg-video-geode - X.Org X server -- Geode GX2/LX display driver
 xserver-xorg-video-geode-dbg - Geode GX2/LX display driver (debugging symbols)
Closes: 848709
Changes:
 xserver-xorg-video-geode (2.11.19-1) unstable; urgency=medium
 .
   * New upstream release.
 - Dropped all patches (merged upstream).
   * [debian/control] -dbg:
 = Downgraded Depends on xserver-xorg-core-dbg to Recommends.
 + Added Recommends on xserver-xorg-core-dbgsym (Closes: #848709).
Checksums-Sha1:
 bdcf6768385debd3636c28f97fedb345e5d6359e 2190 
xserver-xorg-video-geode_2.11.19-1.dsc
 235caa731a917683a3e419a5820cee091ecab6ee 852579 
xserver-xorg-video-geode_2.11.19.orig.tar.gz
 a1aa807396e3bd2de9b327f69315489a2987e1c4 15768 
xserver-xorg-video-geode_2.11.19-1.debian.tar.xz
Checksums-Sha256:
 43a674cea08f2611d3ba4f14dbcc47eee59c066d6a3b079aa08761b893612e80 2190 
xserver-xorg-video-geode_2.11.19-1.dsc
 46ef4e23eaf91abc48ffad394ec6479bf60b2482eded8803d6af93f4ccf51aed 852579 
xserver-xorg-video-geode_2.11.19.orig.tar.gz
 30f7cf091e108786dcca992a4ae093c5ff0a10629f3e548b4e112fa141c2739e 15768 
xserver-xorg-video-geode_2.11.19-1.debian.tar.xz
Files:
 b752ed8d33f563d9529e86794f692266 2190 x11 optional 
xserver-xorg-video-geode_2.11.19-1.dsc
 353b66ff39a4cd6d7af283660533020b 852579 x11 optional 
xserver-xorg-video-geode_2.11.19.orig.tar.gz
 a20c29896ae60bd52886b19b0b880a6c 15768 x11 optional 
xserver-xorg-video-geode_2.11.19-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIbBAEBCAAGBQJYWN5BAAoJENFO8V2v4RNHKAUP90H5D//qNCyrIW6lOJ9sX8If
rK0FpvPdBZLLLN2GljBartn+4tNqMcjW0kY4mUacOmBcmY2b5YerU6MnB3bCdNvy
Ea9if4bKD0s5I8yicOsZcIGPrXKZ7pSVYaeMGKgwR3gCJjYDtLt29iD+meSXCZsd
xgAAQPD8VYzVoRs331GE7HMXKNbFmPDIng8krLFRtcHOYD47ut+QGunCFd/X3obn
KHzS1gwAzx3RCMgl7OQDVo4mCgsXZgxXgTWnYFWN6cOkhcANbPqNdTFC6o7V2/WS
vDKkOo3S+oBml97YdRJRf1ueeNHQQgQEcpfOIqC8kzYL/He1OaD0rMMjznPvRDih
Ljgvl9yUYEdnde7SC9g0/rvsoI2mLR1IlEKNY2Et5mnDlUzw52ev0j8Bmz8iHJf9
86MtHWHoFYvMjjZDx7Tz4RhWajTQG2dczqYS+cnJpL4uNeewXVLCvlKKXCJS2adv

Bug#848410: python-biom-format: FTBFS randomly (failing tests)

[Daniel McDonald]

Try a different seed? Same issue: it's a stochastic test. Other option is
bump the number of iterations it performs.

Best,
Daniel

On Dec 19, 2016 23:32, "Andreas Tille"  wrote:

> Hi Daniel,
>
> thanks for the helpful hint.  I've uploaded a package with the suggested
> fix and I hope this random error will be solved now.  However, there seems
> to be another issue which happens on i386 architecture only:
>
>
> I: pybuild base:184: cd /«BUILDDIR»/python-biom-
> format-2.1.5+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
> 
> 
> 
> 
> ...S.
> --
> Ran 265 tests in 2.759s
>
> OK (SKIP=1)
> pybuild --test --test-nose -i python{version} -p 3.5
> I: pybuild pybuild:212: cp -r 
> /«BUILDDIR»/python-biom-format-2.1.5+dfsg/examples
> /«BUILDDIR»/python-biom-format-2.1.5+dfsg/tests /«BUILDDIR»/python-biom-
> format-2.1.5+dfsg/.pybuild/pythonX.Y_3.5/build
> I: pybuild base:184: cd /«BUILDDIR»/python-biom-
> format-2.1.5+dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 -m nose tests
> 
> 
> ..F.
> 
> ...S.
> ==
> FAIL: test_subsample (tests.test_table.SparseTableTests)
> --
> Traceback (most recent call last):
>   File "/«BUILDDIR»/python-biom-format-2.1.5+dfsg/.pybuild/
> pythonX.Y_3.5/build/tests/test_table.py", line 2263, in test_subsample
> (3, 1, 1)})
> AssertionError: Items in the second set but not the first:
> (3, 0, 0)
>
> --
> Ran 265 tests in 3.098s
>
> FAILED (SKIP=1, failures=1)
>
>
> You can find the full build log here:
>
>https://buildd.debian.org/status/fetch.php?pkg=python-
> biom-format=i386=2.1.5%2Bdfsg-6=1482186822
>
> Any idea what might be wrong here?
>
> Kind regards
>
>   Andreas.
>
> On Tue, Dec 20, 2016 at 05:25:10AM +1100, Daniel McDonald wrote:
> > Thanks, Greg.
> >
> > Andreas, the particular test that is failing as it is stochastic. It is
> > likely possible to just set a random seed at entry into the test here:
> >
> > https://github.com/biocore/biom-format/blob/master/tests/
> test_util.py#L48
> >
> > Specifically, doing something like "np.random.seed(123)"
> >
> > Best,
> > Daniel
> >
> > On Tue, Dec 20, 2016 at 5:15 AM, Greg Caporaso 
> > wrote:
> >
> > > Hi Andreas, I'm cc'ing Daniel McDonald on this message, who is the
> primary
> > > maintainer of the biom-format package these days. Daniel, could you
> follow
> > > up with Andreas?
> > >
> > > On Sat, Dec 17, 2016 at 3:53 PM, Andreas Tille 
> wrote:
> > >
> > >> Hi Greg,
> > >>
> > >> the Debian packaged biom-format received a bug report which leaves me
> > >> clueless how to track it down.  Is there possibly some way to make the
> > >> test suite more verbose to find out what part might cause the random
> > >> failure which you can see in the buil logs linked from the bug page
> > >>
> > >>https://bugs.debian.org/848410
> > >>
> > >> Thanks for any idea to track this down
> > >>
> > >>   Andreas.
> > >>
> > >> On Sat, Dec 17, 2016 at 01:34:49PM +0100, Santiago Vila wrote:
> > >> > Package: src:python-biom-format
> > >> > Version: 2.1.5+dfsg-5
> > >> > Severity: serious
> > >> >
> > >> > Dear maintainer:
> > >> >
> > >> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > >> > (which is what the "Arch: all" autobuilder would do to build it)
> > >> > but it failed:
> > >> >
> > >> > 
> > >> 
> > >> > [...]
> > >> >  debian/rules build-indep
> > >> > dh build-indep --with python2,python3,bash-completion,sphinxdoc
> > >> --buildsystem=pybuild
> > >> >dh_testdir -i -O--buildsystem=pybuild
> > >> >dh_update_autotools_config -i -O--buildsystem=pybuild
> > >> >dh_auto_configure -i -O--buildsystem=pybuild
> > >> >   pybuild --configure --test-nose -i python{version} -p 2.7
> > >> > I: pybuild base:184: python2.7 setup.py config
> > >> > running config
> > >> >   pybuild --configure --test-nose -i python{version} -p 3.5
> > >> > I: pybuild base:184: python3.5 setup.py config
> > >> > running config
> > >> >debian/rules override_dh_auto_build
> > >> > make[1]: Entering directory '/<>/python-biom-for
> > >> mat-2.1.5+dfsg'
> > >> >
> > >> > 

Bug#848848: alpine FTBFS on all architectures due to wrong build dependency order

[Adrian Bunk]

Source: alpine
Version: 2.20+dfsg1-4
Severity: serious

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

The unstable buildds only take the first alternative of build
dependencies into consideration, which means the following
cannot be fulfilled in unstable due to the incorrect order
of the packages:
  libssl-dev (<< 1.1) | libssl1.0-dev

Bug#848768: biojava4-live: FTBFS: [javac] /<>/biojava4-live-4.2.4+dfsg/biojava-structure/src/main/java/org/biojava/nbio/structure/symmetry/core/QuatSymmetryDetector.java:27: error: package o

[Andreas Tille]

Hi Olivier and Ximin,

I stripped the quote of the build log below but to me it seems to be
related to the jmol upgrade.

Any help to get this fixed would be really welcome.

Kind regards

  Andreas.

On Mon, Dec 19, 2016 at 10:08:48PM +0100, Lucas Nussbaum wrote:
> Source: biojava4-live
> Version: 4.2.4+dfsg-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161219 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> ...
> > [javac] UndirectedGraph<Integer, DefaultEdge> graph = 
> > new SimpleGraph<Integer, DefaultEdge>(
> > [javac] 
> >^
> > [javac]   symbol:   class DefaultEdge
> > [javac]   location: class SymmetryTools
> > [javac] 
> > /<>/biojava4-live-4.2.4+dfsg/biojava-structure/src/main/java/org/biojava/nbio/structure/symmetry/utils/SymmetryTools.java:481:
> >  error: cannot find symbol
> > [javac] DefaultEdge.class);
> > [javac] ^
> > [javac]   symbol:   class DefaultEdge
> > [javac]   location: class SymmetryTools
> > [javac] Note: Some input files use or override a deprecated API.
> > [javac] Note: Recompile with -Xlint:deprecation for details.
> > [javac] Note: 
> > /<>/biojava4-live-4.2.4+dfsg/biojava-structure/src/main/java/org/biojava/nbio/structure/io/mmcif/MetalBondConsumer.java
> >  uses unchecked or unsafe operations.
> > [javac] Note: Recompile with -Xlint:unchecked for details.
> > [javac] 67 errors
> > 
> > BUILD FAILED

-- 
http://fam-tille.de

Processed: bug 848847 is forwarded to https://trac.torproject.org/projects/tor/ticket/21018 ...

[Debian Bug Tracking System]

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

> forwarded 848847 https://trac.torproject.org/projects/tor/ticket/21018
Bug #848847 {Done: Debian FTP Masters } [tor] 
read past allocated buffer in hidden service descriptor parsing
Set Bug forwarded-to-address to 
'https://trac.torproject.org/projects/tor/ticket/21018'.
> retitle 848847 tor: CVE-2016-1254 (TROVE-2016-12-002): read past allocated 
> buffer in hidden service descriptor parsing
Bug #848847 {Done: Debian FTP Masters } [tor] 
read past allocated buffer in hidden service descriptor parsing
Changed Bug title to 'tor: CVE-2016-1254 (TROVE-2016-12-002): read past 
allocated buffer in hidden service descriptor parsing' from 'read past 
allocated buffer in hidden service descriptor parsing'.
> thanks
Stopping processing here.

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

Processed: bug 848349 is not forwarded, tagging 848349

[Debian Bug Tracking System]

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

> notforwarded 848349
Bug #848349 {Done: Salvatore Bonaccorso } [src:linux] 
TypeError: unsupported operand type(s) for +=: int and str
Unset Bug forwarded-to-address
> tags 848349 + stretch sid
Bug #848349 {Done: Salvatore Bonaccorso } [src:linux] 
TypeError: unsupported operand type(s) for +=: int and str
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#848410: python-biom-format: FTBFS randomly (failing tests)

[Andreas Tille]

Hi Daniel,

thanks for the helpful hint.  I've uploaded a package with the suggested
fix and I hope this random error will be solved now.  However, there seems
to be another issue which happens on i386 architecture only:


I: pybuild base:184: cd 
/«BUILDDIR»/python-biom-format-2.1.5+dfsg/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m nose tests
...S.
--
Ran 265 tests in 2.759s

OK (SKIP=1)
pybuild --test --test-nose -i python{version} -p 3.5
I: pybuild pybuild:212: cp -r 
/«BUILDDIR»/python-biom-format-2.1.5+dfsg/examples 
/«BUILDDIR»/python-biom-format-2.1.5+dfsg/tests 
/«BUILDDIR»/python-biom-format-2.1.5+dfsg/.pybuild/pythonX.Y_3.5/build
I: pybuild base:184: cd 
/«BUILDDIR»/python-biom-format-2.1.5+dfsg/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m nose tests
..FS.
==
FAIL: test_subsample (tests.test_table.SparseTableTests)
--
Traceback (most recent call last):
  File 
"/«BUILDDIR»/python-biom-format-2.1.5+dfsg/.pybuild/pythonX.Y_3.5/build/tests/test_table.py",
 line 2263, in test_subsample
(3, 1, 1)})
AssertionError: Items in the second set but not the first:
(3, 0, 0)

--
Ran 265 tests in 3.098s

FAILED (SKIP=1, failures=1)


You can find the full build log here:

   
https://buildd.debian.org/status/fetch.php?pkg=python-biom-format=i386=2.1.5%2Bdfsg-6=1482186822

Any idea what might be wrong here?

Kind regards

  Andreas.

On Tue, Dec 20, 2016 at 05:25:10AM +1100, Daniel McDonald wrote:
> Thanks, Greg.
> 
> Andreas, the particular test that is failing as it is stochastic. It is
> likely possible to just set a random seed at entry into the test here:
> 
> https://github.com/biocore/biom-format/blob/master/tests/test_util.py#L48
> 
> Specifically, doing something like "np.random.seed(123)"
> 
> Best,
> Daniel
> 
> On Tue, Dec 20, 2016 at 5:15 AM, Greg Caporaso 
> wrote:
> 
> > Hi Andreas, I'm cc'ing Daniel McDonald on this message, who is the primary
> > maintainer of the biom-format package these days. Daniel, could you follow
> > up with Andreas?
> >
> > On Sat, Dec 17, 2016 at 3:53 PM, Andreas Tille  wrote:
> >
> >> Hi Greg,
> >>
> >> the Debian packaged biom-format received a bug report which leaves me
> >> clueless how to track it down.  Is there possibly some way to make the
> >> test suite more verbose to find out what part might cause the random
> >> failure which you can see in the buil logs linked from the bug page
> >>
> >>https://bugs.debian.org/848410
> >>
> >> Thanks for any idea to track this down
> >>
> >>   Andreas.
> >>
> >> On Sat, Dec 17, 2016 at 01:34:49PM +0100, Santiago Vila wrote:
> >> > Package: src:python-biom-format
> >> > Version: 2.1.5+dfsg-5
> >> > Severity: serious
> >> >
> >> > Dear maintainer:
> >> >
> >> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> >> > (which is what the "Arch: all" autobuilder would do to build it)
> >> > but it failed:
> >> >
> >> > 
> >> 
> >> > [...]
> >> >  debian/rules build-indep
> >> > dh build-indep --with python2,python3,bash-completion,sphinxdoc
> >> --buildsystem=pybuild
> >> >dh_testdir -i -O--buildsystem=pybuild
> >> >dh_update_autotools_config -i -O--buildsystem=pybuild
> >> >dh_auto_configure -i -O--buildsystem=pybuild
> >> >   pybuild --configure --test-nose -i python{version} -p 2.7
> >> > I: pybuild base:184: python2.7 setup.py config
> >> > running config
> >> >   pybuild --configure --test-nose -i python{version} -p 3.5
> >> > I: pybuild base:184: python3.5 setup.py config
> >> > running config
> >> >debian/rules override_dh_auto_build
> >> > make[1]: Entering directory '/<>/python-biom-for
> >> mat-2.1.5+dfsg'
> >> >
> >> > [... snipped ...]
> >> >
> >> > ImportError: No module named _filter
> >> > /<>/python-biom-format-2.1.5+dfsg/doc/documentation/table_objects.rst:1:
> >> WARNING: autodoc: failed to import module u'biom.table'; the following
> >> exception was raised:
> >> > Traceback (most recent call last):
> >> >   File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line
> >> 526, in import_object
> >> > __import__(self.modname)
> >> >   

Bug#848749: set a different $HOME for build-time tests

[Paolo Greppi]

As per this comment in the Pkg-javascript-devel mailing list:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-December/016725.html

I have changed the approach to set a different $HOME for build-time
tests. This should fix the build-time tests.

Paolo

Processed: fixed 848847 in 0.2.9.8-1

[Debian Bug Tracking System]

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

> fixed 848847 0.2.9.8-1
Bug #848847 {Done: Debian FTP Masters } [tor] 
read past allocated buffer in hidden service descriptor parsing
Marked as fixed in versions tor/0.2.9.8-1.
> thanks
Stopping processing here.

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

Bug#848847: marked as done (read past allocated buffer in hidden service descriptor parsing)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2016 21:18:35 +
with message-id 
and subject line tor_0.2.9.8-1_weasel.changes ACCEPTED into experimental
has caused the Debian Bug report #848847,
regarding read past allocated buffer in hidden service descriptor parsing
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.)


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

It has been discovered that Tor may read one byte past an allocated
buffer while parsing hidden service descriptors.

This may enable a malicions hidden service to crash clients attempting
to access it in some circumstances.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/
--- End Message ---
--- Begin Message ---


pgpF_cePDTW8A.pgp
Description: PGP message
--- End Message ---

Bug#844245: Opening a file in vym works for me

[Adrian Bunk]

Control: severity -1 important

Opening a file in vym works for me.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Mention the actual problem in the title

[Debian Bug Tracking System]

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

> retitle 844967 picviz: FTBFS: CMake Error: install TARGETS given no ARCHIVE 
> DESTINATION for static library target "picviz"
Bug #844967 [src:picviz] picviz: FTBFS: cmake_minimum_required(VERSION 3.7)
Changed Bug title to 'picviz: FTBFS: CMake Error: install TARGETS given no 
ARCHIVE DESTINATION for static library target "picviz"' from 'picviz: FTBFS: 
cmake_minimum_required(VERSION 3.7)'.
> thanks
Stopping processing here.

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

Processed: Opening a file in vym works for me

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #844245 [vym] vym 2.5.0-2 crashes on opening a file
Severity set to 'important' from 'grave'

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

Bug#848847: read past allocated buffer in hidden service descriptor parsing

[Peter Palfrader]

Package: tor
Version: 0.2.0.8-alpha-1
Severity: serious

It has been discovered that Tor may read one byte past an allocated
buffer while parsing hidden service descriptors.

This may enable a malicions hidden service to crash clients attempting
to access it in some circumstances.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Processed: reassign 848696 to dpkg, forcibly merging 848413 848696

[Debian Bug Tracking System]

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

> reassign 848696 dpkg
Bug #848696 [valgrind] valgrind: prerm fails: dpkg-maintscript-helper: error: 
dpkg: error: version '' has bad syntax: version string is empty
Bug reassigned from package 'valgrind' to 'dpkg'.
No longer marked as found in versions valgrind/1:3.12.0~svn20160714-1.
Ignoring request to alter fixed versions of bug #848696 to the same values 
previously set
> forcemerge 848413 848696
Bug #848413 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: error: dpkg: error: version '' has bad syntax: version 
string is empty
Bug #848422 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: error: dpkg: error: version '' has bad syntax: version 
string is empty
Bug #848511 {Done: Guillem Jover } [dpkg] dirmngr: fails to 
install: dpkg-maintscript-helper: error: dpkg: error: version '' has bad 
syntax: version string is empty
Bug #848580 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: fails if optional version is not given
Bug #848511 {Done: Guillem Jover } [dpkg] dirmngr: fails to 
install: dpkg-maintscript-helper: error: dpkg: error: version '' has bad 
syntax: version string is empty
Removed indication that 848511 affects src:debian-edu, dirmngr, and src:gnupg2
Added indication that 848511 affects dirmngr,src:debian-edu,src:gnupg2
Removed indication that 848413 affects dirmngr, src:gnupg2, and src:debian-edu
Added indication that 848413 affects dirmngr,src:debian-edu,src:gnupg2
Removed indication that 848422 affects src:debian-edu, dirmngr, and src:gnupg2
Added indication that 848422 affects dirmngr,src:debian-edu,src:gnupg2
Removed indication that 848580 affects src:debian-edu, dirmngr, and src:gnupg2
Added indication that 848580 affects dirmngr,src:debian-edu,src:gnupg2
Marked as found in versions dpkg/1.18.15.
Ignoring request to alter found versions of bug #848413 to the same values 
previously set
Marked as found in versions dpkg/1.18.15.
Marked as found in versions dpkg/1.18.15.
Bug #848696 [dpkg] valgrind: prerm fails: dpkg-maintscript-helper: error: dpkg: 
error: version '' has bad syntax: version string is empty
Severity set to 'serious' from 'grave'
Marked Bug as done
Added indication that 848696 affects dirmngr,src:debian-edu,src:gnupg2
Marked as fixed in versions dpkg/1.18.17.
Marked as found in versions dpkg/1.18.16 and dpkg/1.18.15.
Bug #848422 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: error: dpkg: error: version '' has bad syntax: version 
string is empty
Bug #848580 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: fails if optional version is not given
Merged 848413 848422 848511 848580 848696
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 846418 848759
Bug #846418 [src:contextfree] contextfree: add libfl-dev to Build-Depends
Bug #846418 [src:contextfree] contextfree: add libfl-dev to Build-Depends
Marked as found in versions contextfree/3.0.5+dfsg1-2.2.
Bug #848759 [src:contextfree] contextfree: FTBFS: src-common/scanner.h:46:23: 
fatal error: FlexLexer.h: No such file or directory
Merged 846418 848759
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 846413 848776
Bug #846413 [src:at] at: add libfl-dev to Build-Depends
Bug #846413 [src:at] at: add libfl-dev to Build-Depends
Marked as found in versions at/3.1.20-1.
Bug #848776 [src:at] at: FTBFS: ./lex.yy.c:1258: undefined reference to `yywrap'
Merged 846413 848776
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 846426 848773
Bug #846426 [src:fped] fped: add libfl-dev to Build-Depends
Bug #846426 [src:fped] fped: add libfl-dev to Build-Depends
Marked as found in versions fped/0.1+201210-1.
Bug #848773 [src:fped] fped: FTBFS: ld: cannot find -lfl
Merged 846426 848773
> thanks
Stopping processing here.

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

Bug#848749: disable build-time tests

[Paolo Greppi]

Il looks like node-expand-tilde returns a directory which does not exist
(sbuild-nonexistent) at this line in
node-fined/test/utils/get-userhome-file.js:
var userHomeDir = expandTilde('~');

This in turn triggers the exception in the next line:
var userHomeFiles = fs.readdirSync(userHomeDir);

Google tells me that in an sbuild chroot HOME is indeed set to
/sbuild-nonexistent.

Node-expand-tilde has build and autopkgtests turned on, but they pass
because they do not check that the returned dir exist, only that they
are consistent !

I guess we have no choice but to disable build tests. I have done so in
the repo on alioth, autopkgtests are still on (although I had to disable
a few also related to tilde expansion).

Paolo

Bug#848756: ibus-table-chinese: FTBFS: [Errno 13] Permission denied: '/sbuild-nonexistent'

[Adrian Bunk]

Control: reassign -1 ibus-table 1.9.14-2
Control: reassign 848765 ibus-table 1.9.14-2
Control: forcemerge -1 848765
Control: affects -1 src:ibus-table-others src:ibus-table-chinese
Control: retitle -1 ibus-table-createdb fails on non-existing $HOME

On Mon, Dec 19, 2016 at 10:22:37PM +0100, Lucas Nussbaum wrote:
>...
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>'
> > [  4%] Building yong table
> > cd /<>/tables/yong && /usr/bin/ibus-table-createdb -n yong.db 
> > -s yong.txt
> > Traceback (most recent call last):
> >   File "/usr/share/ibus-table/engine/tabcreatedb.py", line 29, in 
> > import tabsqlitedb
> >   File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 36, in 
> > import ibus_table_location
> >   File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in 
> > 
> > __module_init = __ModuleInitializer()
> >   File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in 
> > __init__
> > _init()
> >   File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in 
> > _init
> > os.makedirs(ibus_table_location['data_home'])
> >   File "/usr/lib/python3.5/os.py", line 231, in makedirs
> > makedirs(head, mode, exist_ok)
> >   File "/usr/lib/python3.5/os.py", line 231, in makedirs
> > makedirs(head, mode, exist_ok)
> >   File "/usr/lib/python3.5/os.py", line 231, in makedirs
> > makedirs(head, mode, exist_ok)
> >   File "/usr/lib/python3.5/os.py", line 241, in makedirs
> > mkdir(name, mode)
> > PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent'
> > tables/yong/CMakeFiles/convert_yong.dir/build.make:63: recipe for target 
> > 'tables/yong/yong.db' failed
> > make[3]: *** [tables/yong/yong.db] Error 1
>...

Thanks for your report, this seems to be a regression
in ibus-table 1.9.14-2:

$ HOME=/foobar ibus-table-createdb
Traceback (most recent call last):
  File "/usr/share/ibus-table/engine/tabcreatedb.py", line 29, in 
import tabsqlitedb
  File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 36, in 
import ibus_table_location
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in 

__module_init = __ModuleInitializer()
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in 
__init__
_init()
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in _init
os.makedirs(ibus_table_location['data_home'])
  File "/usr/lib/python3.5/os.py", line 231, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.5/os.py", line 231, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.5/os.py", line 231, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.5/os.py", line 241, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/foobar'
$


ibus-table 1.9.1-4 in testing does not seem to have this problem:

$ HOME=/foobar ibus-table-createdb
Usage: tabcreatedb.py [options]

Options:
  -h, --helpshow this help message and exit
  -n NAME, --name=NAME  specifies the file name for the binary database for
the IME. The default is ''. If the file name of the
database is not specified, the file name of the source
file before the first '.' will be appended with '.db'
and that will be used as the file name of the
database.
  -s SOURCE, --source=SOURCE
specifies the file which contains the source of the
IME.  The default is ''.
  -e EXTRA, --extra=EXTRA
specifies the file name for the extra words for the
IME.  The default is ''.
  -p PINYIN, --pinyin=PINYIN
specifies the source file for the  pinyin.  The
default is '/usr/share/ibus-
table/data/pinyin_table.txt.bz2'.
  -o, --no-create-index
Do not create an index for a database (Only for
distrubution purposes, a normal user should not use
this flag!)
  -i, --create-index-only
Only create an index for an existing database.
Specifying the file name of the binary database with
the -n or --name option is required when this option
is used.
  -d, --debug   Print extra debug messages.

You need to specify the file which contains the source of the IME!
$


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#848756: ibus-table-chinese: FTBFS: [Errno 13] Permission denied: '/sbuild-nonexistent'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ibus-table 1.9.14-2
Bug #848756 [src:ibus-table-chinese] ibus-table-chinese: FTBFS: [Errno 13] 
Permission denied: '/sbuild-nonexistent'
Bug reassigned from package 'src:ibus-table-chinese' to 'ibus-table'.
No longer marked as found in versions ibus-table-chinese/1.8.2-2.
Ignoring request to alter fixed versions of bug #848756 to the same values 
previously set
Bug #848756 [ibus-table] ibus-table-chinese: FTBFS: [Errno 13] Permission 
denied: '/sbuild-nonexistent'
Marked as found in versions ibus-table/1.9.14-2.
> reassign 848765 ibus-table 1.9.14-2
Bug #848765 [src:ibus-table-others] ibus-table-others: FTBFS: PermissionError: 
[Errno 13] Permission denied: '/sbuild-nonexistent'
Bug reassigned from package 'src:ibus-table-others' to 'ibus-table'.
No longer marked as found in versions ibus-table-others/1.3.9-2.
Ignoring request to alter fixed versions of bug #848765 to the same values 
previously set
Bug #848765 [ibus-table] ibus-table-others: FTBFS: PermissionError: [Errno 13] 
Permission denied: '/sbuild-nonexistent'
Marked as found in versions ibus-table/1.9.14-2.
> forcemerge -1 848765
Bug #848756 [ibus-table] ibus-table-chinese: FTBFS: [Errno 13] Permission 
denied: '/sbuild-nonexistent'
Bug #848765 [ibus-table] ibus-table-others: FTBFS: PermissionError: [Errno 13] 
Permission denied: '/sbuild-nonexistent'
Merged 848756 848765
> affects -1 src:ibus-table-others src:ibus-table-chinese
Bug #848756 [ibus-table] ibus-table-chinese: FTBFS: [Errno 13] Permission 
denied: '/sbuild-nonexistent'
Bug #848765 [ibus-table] ibus-table-others: FTBFS: PermissionError: [Errno 13] 
Permission denied: '/sbuild-nonexistent'
Added indication that 848756 affects src:ibus-table-others and 
src:ibus-table-chinese
Added indication that 848765 affects src:ibus-table-others and 
src:ibus-table-chinese
> retitle -1 ibus-table-createdb fails on non-existing $HOME
Bug #848756 [ibus-table] ibus-table-chinese: FTBFS: [Errno 13] Permission 
denied: '/sbuild-nonexistent'
Bug #848765 [ibus-table] ibus-table-others: FTBFS: PermissionError: [Errno 13] 
Permission denied: '/sbuild-nonexistent'
Changed Bug title to 'ibus-table-createdb fails on non-existing $HOME' from 
'ibus-table-chinese: FTBFS: [Errno 13] Permission denied: 
'/sbuild-nonexistent''.
Changed Bug title to 'ibus-table-createdb fails on non-existing $HOME' from 
'ibus-table-others: FTBFS: PermissionError: [Errno 13] Permission denied: 
'/sbuild-nonexistent''.

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

Bug#847753: marked as done (sfcgal: FTBFS on mips, mipsel: out of memory)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 07:20:14 +0100
with message-id <4762b664-85a1-7ac4-5bce-2d2dbff22...@xs4all.nl>
and subject line Re: Bug#847753: sfcgal: FTBFS on mips, mipsel: out of memory
has caused the Debian Bug report #847753,
regarding sfcgal: FTBFS on mips, mipsel: out of memory
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.)


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

Hi,

the boost 1.62 binNMU failed on mips and mipsel because g++ ran out of
memory:

https://buildd.debian.org/status/fetch.php?pkg=sfcgal=mips=1.3.0-4%2Bb2=1480467714
https://buildd.debian.org/status/fetch.php?pkg=sfcgal=mipsel=1.3.0-4%2Bb2=1480489220


Andreas
--- End Message ---
--- Begin Message ---
notfound 847753 sfcgal/1.3.0-4
thanks

On 12/19/2016 10:19 AM, Bas Couwenberg wrote:
> On 2016-12-19 10:12, Andreas Beckmann wrote:
>> On 2016-12-19 07:15, Sebastiaan Couwenberg wrote:
>>> I'm tempted to downgrade the severity of this issue because there are
>>> not actual users of the affected packages on mips*, and having those
>>> packages removed from testing because of this issue is a disservice to
>>> our users.
>>
>> Ack, but shouldn't pinging the bug be sufficient to reset the AUTORM
>> timer?
> 
> Yes, that's why I haven't downgraded the severity yet.

ftp-master has removed sfcgal & its rdeps from mips*, that should fix
this issue. When we get better buildds for mips* that are able to build
it successfully the packages should automatically return.

Kind Regards,

Bas

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

Processed: Re: Bug#847753: sfcgal: FTBFS on mips, mipsel: out of memory

[Debian Bug Tracking System]

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

> notfound 847753 sfcgal/1.3.0-4
Bug #847753 [src:sfcgal] sfcgal: FTBFS on mips, mipsel: out of memory
No longer marked as found in versions sfcgal/1.3.0-4.
> thanks
Stopping processing here.

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

Bug#845037: marked as done (libschroedinger-1.0-0: is this package fit for stretch?)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 06:02:47 +
with message-id 
and subject line Bug#848828: Removed package(s) from unstable
has caused the Debian Bug report #845037,
regarding libschroedinger-1.0-0: is this package fit for stretch?
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.)


-- 
845037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libschroedinger-1.0-0
Version: 1.0.11-2.1
Severity: serious
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

libschroedinger contains various possibly security relevant bugs
(see #787957 for the tip of the iceberg).

Furthermore it is no longer maintained upstream:
 * last release from 2012
 * homepage vanished

Thus I think stretch would be better of without this library.

As replacement, ffmpeg has a decent dirac decoder and also a
vc2 encoder, which is the intra-only subset of dirac that
got standardized by the SMPTE.

Best regards,
Andreas


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

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libschroedinger-1.0-0 depends on:
ii  libc6  2.24-5
ii  libgcc11:6.2.0-13
ii  liborc-0.4-0   1:0.4.26-2
ii  libstdc++6 6.2.0-13
ii  multiarch-support  2.24-5

libschroedinger-1.0-0 recommends no packages.

libschroedinger-1.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.11-2.1+rm

Dear submitter,

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

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

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

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

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

Processed: severity of 848842 is important

[Debian Bug Tracking System]

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

> severity 848842 important
Bug #848842 [tracker-extract] /usr/lib/tracker/tracker-extract: Crashes with 
SIGSYS, and repeatedly restarts
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#848842: /usr/lib/tracker/tracker-extract: Crashes with SIGSYS, and repeatedly restarts

[Ben Longbons]

Package: tracker-extract
Version: 1.10.3-1
Severity: critical
File: /usr/lib/tracker/tracker-extract
Justification: breaks the whole system

Dear Maintainer,

During a recent apt run, my system became almost completely
unresponsive.

Luckily I was able to get to another terminal, find the offender with
`top`, and neutralize it.

/usr/lib/tracker/tracker-extract is dying with SIGSYS, backtrace below.

According to `coredumpctl list`, it restarted approximately 6000 times
before I replaced it with a symlink to /bin/true, which finally allowed
aptitude to finish. That auto-restart behavior, in itself, deserves a grave
bug at least.

I haven't got debug symbols, but I will follow-up after installing them.

# coredumpctl gdb
   PID: 23962 (tracker-extract)
   UID: 1000 (ben)
   GID: 1000 (ben)
Signal: 31 (SYS)
 Timestamp: Mon 2016-12-19 21:16:42 PST (12min ago)
  Command Line: /usr/lib/tracker/tracker-extract
Executable: /usr/lib/tracker/tracker-extract
 Control Group: /
 Slice: -.slice
   Boot ID: db830d9ceb0441bd97c414fa76830061
Machine ID: a9f5005691f11289cd92098b52b4f3f9
  Hostname: joyplim
   Storage: 
/var/lib/systemd/coredump/core.tracker-extract.1000.db830d9ceb0441bd97c414fa76830061.23962.1482211002.lz4
   Message: Process 23962 (tracker-extract) of user 1000 dumped core.

Stack trace of thread 23990:
#0  0x7fe59d43e4d7 mlock (libc.so.6)
#1  0x7fe5766da6f1 fluid_defsfont_load_sampledata 
(libfluidsynth.so.1)
#2  0x7fe5766de78a fluid_defsfont_load (libfluidsynth.so.1)
#3  0x7fe5766de8c1 fluid_defsfloader_load 
(libfluidsynth.so.1)
#4  0x7fe5766ebdc9 fluid_synth_sfload (libfluidsynth.so.1)
#5  0x7fe57698d276 n/a (libgstfluidsynthmidi.so)
#6  0x7fe58647d6de gst_element_change_state 
(libgstreamer-1.0.so.0)
#7  0x7fe58647de4f n/a (libgstreamer-1.0.so.0)
#8  0x7fe584266edd n/a (libgstplayback.so)
#9  0x7fe5842725c4 n/a (libgstplayback.so)
#10 0x7fe584272fe2 n/a (libgstplayback.so)
#11 0x7fe58427322f n/a (libgstplayback.so)
#12 0x7fe59dc41f75 g_closure_invoke (libgobject-2.0.so.0)
#13 0x7fe59dc53f82 signal_emit_unlocked_R 
(libgobject-2.0.so.0)
#14 0x7fe59dc5cbcc g_signal_emit_valist 
(libgobject-2.0.so.0)
#15 0x7fe59dc5cfaf g_signal_emit (libgobject-2.0.so.0)
#16 0x7fe59dc463a4 g_object_dispatch_properties_changed 
(libgobject-2.0.so.0)
#17 0x7fe586451634 n/a (libgstreamer-1.0.so.0)
#18 0x7fe59dc48979 g_object_notify_by_spec_internal 
(libgobject-2.0.so.0)
#19 0x7fe586492434 n/a (libgstreamer-1.0.so.0)
#20 0x7fe58649ded0 gst_pad_push_event 
(libgstreamer-1.0.so.0)
#21 0x7fe577397829 n/a (libgstmidi.so)
#22 0x7fe5864c8a11 n/a (libgstreamer-1.0.so.0)
#23 0x7fe59d98cd3e g_thread_pool_thread_proxy 
(libglib-2.0.so.0)
#24 0x7fe59d98c345 g_thread_proxy (libglib-2.0.so.0)
#25 0x7fe59d701464 start_thread (libpthread.so.0)
#26 0x7fe59d4429df __clone (libc.so.6)

Stack trace of thread 23964:
#0  0x7fe59d43e119 syscall (libc.so.6)
#1  0x7fe59d9aa14f g_cond_wait (libglib-2.0.so.0)
#2  0x7fe59d938ecb g_async_queue_pop_intern_unlocked 
(libglib-2.0.so.0)
#3  0x7fe59d98ce8d g_thread_pool_wait_for_new_task 
(libglib-2.0.so.0)
#4  0x7fe59d98c345 g_thread_proxy (libglib-2.0.so.0)
#5  0x7fe59d701464 start_thread (libpthread.so.0)
#6  0x7fe59d4429df __clone (libc.so.6)

Stack trace of thread 23962:
#0  0x7fe59d43956d poll (libc.so.6)
#1  0x7fe59d9649f6 g_main_context_poll (libglib-2.0.so.0)
#2  0x7fe59d964d82 g_main_loop_run (libglib-2.0.so.0)
#3  0x56523e970d47 n/a (/usr/lib/tracker/tracker-extract)

GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:

Bug#848389: marked as done (derby: Fails to build from source)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 05:33:38 +
with message-id 
and subject line Bug#848389: fixed in derby 10.13.1.1-2
has caused the Debian Bug report #848389,
regarding derby: Fails to build from source
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.)


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

derby fails to build from source. It looks to me like it's failing
because it's trying to connect to an external website and fails when
it can't load the URL.

I recommend doing a source-only upload next time to detect these issues sooner.

https://wiki.debian.org/SourceOnlyUpload

Build log excerpt below. You can see the full build log at
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/derby.html
Click rbuild on the left sidebar.

install_packagelists:
[mkdir] Created dir: /<>/packageListLoc-se-8
[mkdir] Created dir: /<>/packageListLoc-j2ee-7
  [get] Getting: http://docs.oracle.com/javase/8/docs/api/package-list
  [get] To: /<>/packageListLoc-se-8/package-list
  [get] Error getting
http://docs.oracle.com/javase/8/docs/api/package-list to
/<>/packageListLoc-se-8/package-list

BUILD FAILED
/<>/build.xml:948: The following error occurred while
executing this line:
/<>/build.xml:976: java.net.UnknownHostException: docs.oracle.com
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
at sun.net.www.http.HttpClient.(HttpClient.java:211)
at sun.net.www.http.HttpClient.New(HttpClient.java:308)
at 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1209)
at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1157)
at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
at 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
at org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:728)
at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:641)
at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:631)

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: derby
Source-Version: 10.13.1.1-2

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated derby 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, 18 Dec 2016 17:13:07 -0800
Source: derby
Binary: libderbyclient-java libderby-java derby-tools derby-doc
Architecture: source all
Version: 10.13.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 derby-doc  - Apache Derby API documentation and examples
 derby-tools - Apache Derby Tools
 libderby-java - Apache Derby Database Engine and Embedded JDBC Driver
 libderbyclient-java - Apache Derby Client JDBC Driver
Closes: 848389
Changes:
 derby (10.13.1.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add JavaSE and J2EE API package-list files to the source package
 so they are available at build time (instead of downloading them
 from Oracle).  Add patch 03 to create a local.properties file to
 refer the build.xml to these local resources. (Closes: #848389)
   * Update debian/README.source to document creation of package-list
 files.
Checksums-Sha1:
 5fcae1bb21bc832c34cb5a345d4d263daec57bad 2261 derby_10.13.1.1-2.dsc
 9238909e06ae064be5fbd0ffe785dbca9283da16 

Bug#848807: gnutls28: FTBFS: dh_install: missing files, aborting

[Helmut Grohne]

Control: reassign 848807 libunbound2
Control: forcemerge 848339 848807

On Mon, Dec 19, 2016 at 10:32:00PM +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[4]: Entering directory '/<>'
> > make[4]: Nothing to be done for 'install-exec-am'.
> > make[4]: Nothing to be done for 'install-data-am'.
> > make[4]: Leaving directory '/<>'
> > make[3]: Leaving directory '/<>'
> > make[2]: Leaving directory '/<>'
> > find debian/*/usr/lib/* -name '*.so.*.*' -type f -exec \
> > chrpath -d {} +
> > make[1]: Leaving directory '/<>'
> >dh_install -O--parallel
> > dh_install: Cannot find (any matches for) 
> > "debian/tmp/usr/lib/*/pkgconfig/gnutls-dane.pc" (tried in "." and 
> > "debian/tmp")
> > dh_install: libgnutls28-dev missing files: 
> > debian/tmp/usr/lib/*/pkgconfig/gnutls-dane.pc
> > dh_install: Cannot find (any matches for) 
> > "debian/tmp/usr/lib/*/libgnutls-dane.so.*" (tried in "." and "debian/tmp")
> > dh_install: libgnutls-dane0 missing files: 
> > debian/tmp/usr/lib/*/libgnutls-dane.so.*
> > dh_install: missing files, aborting
> > debian/rules:102: recipe for target 'binary' failed
> > make: *** [binary] Error 255

That's due to the unresolved fake_dsa symbol introduced in unbound
1.6.0-1.

Helmut

Processed: Re: Bug#848807: gnutls28: FTBFS: dh_install: missing files, aborting

[Debian Bug Tracking System]

Processing control commands:

> reassign 848807 libunbound2
Bug #848807 [src:gnutls28] gnutls28: FTBFS: dh_install: missing files, aborting
Bug reassigned from package 'src:gnutls28' to 'libunbound2'.
No longer marked as found in versions gnutls28/3.5.7-2.
Ignoring request to alter fixed versions of bug #848807 to the same values 
previously set
> forcemerge 848339 848807
Bug #848339 {Done: Robert Edmonds } [libunbound2] 
unbound-anchor: libunbound.so.2 unknown symbol fake_dsa
Bug #848339 {Done: Robert Edmonds } [libunbound2] 
unbound-anchor: libunbound.so.2 unknown symbol fake_dsa
Added tag(s) stretch and sid.
Bug #848807 [libunbound2] gnutls28: FTBFS: dh_install: missing files, aborting
Set Bug forwarded-to-address to 
'https://nlnetlabs.nl/bugs-script/show_bug.cgi?id=1188'.
848767 was blocked by: 848339
848767 was not blocking any bugs.
Added blocking bug(s) of 848767: 848807
Marked Bug as done
Added indication that 848807 affects src:gnutls28
Marked as fixed in versions unbound/1.6.0-2.
Marked as found in versions unbound/1.6.0-1.
Added tag(s) patch.
Merged 848339 848807

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

Bug#821500: marked as done (glpi: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 05:24:26 +
with message-id 
and subject line Bug#846067: Removed package(s) from unstable
has caused the Debian Bug report #821500,
regarding glpi: PHP 7.0 Transition
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.)


-- 
821500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glpi
Version: 0.84.8+dfsg.1-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The glpi package currently depends on libapache2-mod-php5 php5 php5-cgi
php5-cli php5-mysql php5-mysqlnd .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: glpi -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUprXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHvdUQAOUohBqFX286vbyCldYYUr3w
5Iwo+nck+lrc2mpQEQ6mSDQRKhf/y0aAG5iRUYluc74bzb2F7wUH5M9SYao1FGKr
tKnuhWe1wyeDCsVBFI8qHTvl37YFqz0C7pjpTCWgE7u+Fl23KXCf3UW5uNIGrLSA
e9yPP6vs2k3+wnV1lv3JxILoETu74wRq9+Slx1emPR3NOGbCk5fWqGDCgHp64qDk

Bug#846459: closed by Adam Borowski <kilob...@angband.pl> (Bug#846459: fixed in pam 1.1.8-3.4)

[Helmut Grohne]

Control: reopen -1
Control: found -1 pam/1.1.8-3.4

On Tue, Dec 20, 2016 at 01:39:05AM +, Debian Bug Tracking System wrote:
> pam will soon fail to build from source, beause flex drops its
> dependency on libfl-dev. Since pam uses parts of libfl-dev (e.g.
> libl.a, libfl.a or FlexLexer.h), it should add "libfl-dev,
> libfl-dev:native" to its Build-Depends. This change was previously
> announced[1] to debian-devel in accordance with DevRef 7.1.1. Please
> add the missing dependency.

The "libfl-dev:native" dependency is still missing.

Helmut

Bug#828510: marked as done (postgresql-9.5: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 05:23:09 +
with message-id 
and subject line Bug#839630: Removed package(s) from unstable
has caused the Debian Bug report #828510,
regarding postgresql-9.5: FTBFS with openssl 1.1.0
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.)


-- 
828510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-9.5
Version: 9.5.3-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/postgresql-9.5_9.5.3-1_amd64-20160529-1510

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Version: 9.5.4-3+rm

Dear submitter,

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

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

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

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

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

Processed: Patch is already in the bug

[Debian Bug Tracking System]

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

> tags 828555 patch
Bug #828555 [src:sqlcipher] sqlcipher: FTBFS with openssl 1.1.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#841569: marked as done (python-kinterbasdb: FTBFS: 'isc_info_db_SQL_dialect' undeclared)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 05:22:17 +
with message-id 
and subject line Bug#695608: Removed package(s) from unstable
has caused the Debian Bug report #841569,
regarding python-kinterbasdb: FTBFS: 'isc_info_db_SQL_dialect' undeclared
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.)


-- 
841569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-kinterbasdb
Version: 3.3.0-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> dh_testdir
> set -e; \
> for py in python2.7; do $py setup.py build; $py-dbg setup.py build; done
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./__init__.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./k_exceptions.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_naked.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_backcompat.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_23plus.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_fixed_stdlib.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_fixed_fixedpoint.py -> 
> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_datetime_naked.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_datetime_stdlib.py -> 
> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_datetime_mx.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_text_unicode.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./_array_descriptor.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./_connection_timeout.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./_request_buffer_builder.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_23plus_lowmem.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_24plus.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./typeconv_fixed_decimal.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> copying ./services.py -> build/lib.linux-x86_64-2.7/kinterbasdb
> creating build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/concurrency.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/tutorial.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/python-db-api-compliance.html -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/installation.html -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/index.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/search.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/license.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/beyond-python-db-api.html -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/changelog.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/links.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/genindex.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/Python-DB-API-2.0.html -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/thread-safety-overview.html -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> copying ./docs/modindex.html -> build/lib.linux-x86_64-2.7/kinterbasdb/docs
> creating build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/rightsidebar.css -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/doctools.js -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/sphinxdoc.css -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/traditional.css -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/navigation.png -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/stickysidebar.css -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/file.png -> 
> build/lib.linux-x86_64-2.7/kinterbasdb/docs/_static
> copying ./docs/_static/plus.png -> 
> 

Processed: Re: Bug#846459 closed by Adam Borowski <kilob...@angband.pl> (Bug#846459: fixed in pam 1.1.8-3.4)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #846459 {Done: Adam Borowski } [src:pam] pam: add 
libfl-dev to Build-Depends
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pam/1.1.8-3.4.
> found -1 pam/1.1.8-3.4
Bug #846459 [src:pam] pam: add libfl-dev to Build-Depends
Marked as found in versions pam/1.1.8-3.4.

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

Bug#844918: Patch is already in the bug

[Adrian Bunk]

Nicolas, can you upload a package with my fix?

Thanks
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Not RC - only one output (albeit the default) is broken for some users

[Debian Bug Tracking System]

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

> severity 840416 important
Bug #840416 [xine-ui] xine fails to start due to missing libvdpau_i965.so
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#844828: Fix for the cmtk build dependencies

[Adrian Bunk]

Control: tags -1 patch

The patch below fixes the build dependencies of cmtk.

The "| libssl-dev (<< 1.1.0~)" is added for backports.

--- debian/control.old  2016-12-20 04:57:36.0 +
+++ debian/control  2016-12-20 04:57:44.0 +
@@ -18,7 +18,7 @@
libwrap0-dev,
libcharls-dev | libdcmtk1-dev | libdcmtk2-dev (<< 3.6.0-8~),
libxml2-dev,
-   libssl-dev,
+   libssl1.0-dev | libssl-dev (<< 1.1.0~),
xvfb, bc, dc,
xauth,
 Standards-Version: 3.9.8


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Fix for the cmtk build dependencies

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #844828 [src:cmtk] cmtk: FTBFS: build-dependency not installable: libssl-dev
Added tag(s) patch.

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

Bug#848096: marked as done (guake: Provides x-terminal-emulator, but doesn't implement the requirements)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 05:03:25 +
with message-id 
and subject line Bug#848096: fixed in guake 0.8.8-1
has caused the Debian Bug report #848096,
regarding guake: Provides x-terminal-emulator, but doesn't implement the 
requirements
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.)


-- 
848096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: guake
Version: 0.8.7-1
Severity: serious
Justification: Policy 11.8.3

Dear Maintainer,

Quoting policy:

>To be an x-terminal-emulator, a program must:

> * Be able to emulate a DEC VT100 terminal, or a compatible terminal.

Guake does this one, at least.

> * Support the command-line option -e command, which creates a new terminal 
> window[106] and runs the specified command, interpreting the entirety of the 
> rest of the command line as a command to pass straight to exec, in the manner 
> that xterm does.

Guake implements this incorrectly - it uses the shell's -c option
rather than consuming the rest of the arguments.

This is the reason for gnome-terminal.wrapper, though the underlying
functionality will need to be implemented at all before a wrapper can be
written.

Also, it does not make the terminal visible, and behaves quite oddly
if run from outside an existing guake.

> * Support the command-line option -T title, which creates a new terminal 
> window with the window title title.

Guake does not implement this at all. The `-r` argument DTWT if already
within a guake terminal, doesn't make the terminal visible, and doesn't
block.


Since guake is a somewhat special-purpose terminal, the simplest solution is
to simply remove the `Provides:` header and the `update-alternatives` logic.
(This doesn't stop *users* from using guake primarily, of course).

If you *do* decide to implement the missing requirements, take care that
the caller blocks for the right duration in all cases: (if starting guake
for the first time; if guake was already running; if run from within guake).

-Ben


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

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

Versions of packages guake depends on:
ii  gconf2  3.2.6-4
ii  libgtk2.0-0 2.24.31-1
ii  notification-daemon 3.20.0-1
ii  plasma-workspace [notification-daemon]  4:5.8.2-1
ii  python  2.7.11-2
ii  python-dbus 1.2.4-1
ii  python-gconf2.28.1+dfsg-1.2
ii  python-glade2   2.24.0-5.1
ii  python-keybinder0.3.1-1
ii  python-notify   0.1.1-4
ii  python-vte  1:0.28.2-5+b1
ii  python-xdg  0.25-4
ii  python2.7   2.7.12-7
pn  python:any  

guake recommends no packages.

guake suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: guake
Source-Version: 0.8.8-1

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

Debian distribution maintenance software
pp.
Daniel Echeverry  (supplier of updated guake package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2016 12:55:53 -0500
Source: guake
Binary: guake
Architecture: source i386
Version: 0.8.8-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry 
Changed-By: Daniel Echeverry 
Description:
 guake  - Drop-down terminal 

Bug#844802: marked as done (shibboleth-resolver: FTBFS: unsatisfiable build-dependencies: libshibsp-dev (>= 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxmltooling-dev (>= 1.4))

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 06:56:32 +0200
with message-id <20161220045632.mmopzlbzoikr7...@bunk.spdns.de>
and subject line This has already been resolved
has caused the Debian Bug report #844802,
regarding shibboleth-resolver: FTBFS: unsatisfiable build-dependencies: 
libshibsp-dev (>= 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxmltooling-dev 
(>= 1.4)
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libshibsp-dev (>= 
> 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxerces-c-dev, 
> libxmltooling-dev (>= 1.4), libkrb5-dev (>= 1.9), liblog4shib-dev, 
> libboost-dev
> Filtered Build-Depends: debhelper (>= 9), libshibsp-dev (>= 
> 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxerces-c-dev, 
> libxmltooling-dev (>= 1.4), libkrb5-dev (>= 1.9), liblog4shib-dev, 
> libboost-dev
> dpkg-deb: building package 'sbuild-build-depends-shibboleth-resolver-dummy' 
> in 
> '/<>/resolver-VkSYYK/apt_archive/sbuild-build-depends-shibboleth-resolver-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-shibboleth-resolver-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-VkSYYK/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-VkSYYK/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-VkSYYK/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-VkSYYK/apt_archive ./ Sources [426 B]
> Get:5 copy:/<>/resolver-VkSYYK/apt_archive ./ Packages [515 B]
> Fetched 1898 B in 0s (177 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install shibboleth-resolver build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-shibboleth-resolver-dummy : Depends: libshibsp-dev (>= 
> 2.5+dfsg~moonshot1) but it is not going to be installed
>   Depends: libsaml2-dev (>= 
> 2.4) but it is not going to be installed
>   Depends: libxmltooling-dev 
> (>= 1.4) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/shibboleth-resolver_1.0.0-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
"apt-get build-dep shibboleth-resolver" works for me now.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#844980: Patch for the undertaker FTBFS bugs

[Adrian Bunk]

Control: tags -1 patch

The following patch fixes the undertaker FTBFS bugs:

--- debian/control.old  2016-12-20 04:46:08.0 +
+++ debian/control  2016-12-20 04:46:18.0 +
@@ -8,6 +8,7 @@
  check,
  debhelper (>= 9~),
  flex (>= 2.6.1),
+ libfl-dev,
  libboost-dev (>= 1.40),
  libboost-filesystem-dev (>= 1.40),
  libboost-regex-dev (>= 1.40),
--- debian/rules.old2016-12-20 04:46:09.0 +
+++ debian/rules2016-12-20 04:46:52.0 +
@@ -3,7 +3,7 @@
 UPSTREAM_VERSION=$(shell cat VERSION)
 
 %:
-   dh $@ --with python2 --parallel
+   dh $@ --with python2
 
 override_dh_auto_build:
cd undertaker && make REGENERATE_PARSERS=1 regenerate_parsers



cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Correct severity

[Debian Bug Tracking System]

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

> severity 848384 important
Bug #848384 [sponsorship-requests] RFS: xmacro/0.3pre-2911-7 [RC] [ITA]
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Patch for the undertaker FTBFS bugs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #846452 [src:undertaker] undertaker: add libfl-dev to Build-Depends
Added tag(s) patch.

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

Processed: Patch for the undertaker FTBFS bugs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #844980 [src:undertaker] undertaker: FTBFS in parallel builds
Added tag(s) patch.

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

Processed: Also tag patch

[Debian Bug Tracking System]

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

> tags 844213 patch
Bug #844213 [src:pyelliptic] Does not support OpenSSL 1.1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#844213: pyelliptic: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: ECDH_OpenSSL

[Adrian Bunk]

On Sat, Nov 26, 2016 at 03:00:14PM +0500, Andrey Rahmatullin wrote:
> Control: retitle -1 Does not support OpenSSL 1.1
> Control: forwarded -1 https://github.com/yann2192/pyelliptic/issues/50
> Control: tags -1 + upstream
> 
> On Sun, Nov 13, 2016 at 01:38:17PM +, Chris Lamb wrote:
> > File 
> > "/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_3.5/build/pyelliptic/openssl.py",
> >  line 180, in __init__
> >   self.ECDH_OpenSSL = self._lib.ECDH_OpenSSL
> > File "/usr/lib/python3.5/ctypes/__init__.py", line 360, in __getattr__
> >   func = self.__getitem__(name)
> > File "/usr/lib/python3.5/ctypes/__init__.py", line 365, in __getitem__
> >   func = self._FuncPtr((name_or_ordinal, self))
> >   AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined 
> > symbol: ECDH_OpenSSL
> Actually this means the module cannot work with libcrypto.so.1.1 as it
> expects functions that are not present anymore.
> Probably most of the used ones are still there but it still requires
> checking and patching because right now the module cannot be imported.

As a workaround, the attached patch works in combination with the 
following change to debian/control:

--- debian/control.old  2016-12-20 04:38:28.0 +
+++ debian/control  2016-12-20 04:38:47.0 +
@@ -2,7 +2,7 @@
 Section: python
 Priority: optional
 Maintainer: Riley Baird 
-Build-Depends: debhelper (>= 9), dh-python, python-all, python-setuptools, 
python3-all, python3-setuptools
+Build-Depends: debhelper (>= 9), dh-python, python-all, python-setuptools, 
python3-all, python3-setuptools, libssl1.0.2
 Standards-Version: 3.9.6
 Vcs-Git: git://anonscm.debian.org/collab-maint/pyelliptic.git
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/pyelliptic.git
@@ -10,7 +10,7 @@
 
 Package: python-pyelliptic
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, openssl
+Depends: ${python:Depends}, ${misc:Depends}, openssl, libssl1.0.2
 Description: High level Python wrapper for OpenSSL (Python 2)
  PyElliptic is a Python module that provides high level access to the
  OpenSSL library, featuring elliptic curve cryptography (ECC), symmetric
@@ -33,7 +33,7 @@
 
 Package: python3-pyelliptic
 Architecture: all
-Depends: ${python3:Depends}, ${misc:Depends}, openssl
+Depends: ${python3:Depends}, ${misc:Depends}, openssl, libssl1.0.2
 Description: High level Python wrapper for OpenSSL (Python 3)
  PyElliptic is a Python module that provides high level access to the
  OpenSSL library, featuring elliptic curve cryptography (ECC), symmetric


> WBR, wRAR

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Description: Use libcrypto.so.1.0.2
 The code does not work with libssl1.1
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/844213

--- pyelliptic-1.5.7.orig/pyelliptic/openssl.py
+++ pyelliptic-1.5.7/pyelliptic/openssl.py
@@ -519,7 +519,7 @@ class _OpenSSL:
 def get_error(self):
 return OpenSSL.ERR_error_string(OpenSSL.ERR_get_error(), None)
 
-libname = ctypes.util.find_library('crypto')
+libname = "libcrypto.so.1.0.2"
 if libname is None:
 # For Windows ...
 libname = ctypes.util.find_library('libeay32.dll')

Bug#828287: dsniff: FTBFS with openssl 1.1.0

[Adrian Bunk]

On Mon, Nov 07, 2016 at 10:24:34PM +0100, Christoph Biedl wrote:
> Sandro Tosi wrote...
> 
> > Hello Dug,
> > in Debian we started the transition to OpenSSL 1.1.0: do you have any
> > plan to port dsniff to that version?
> 
> Since I have some interest in keeping dsniff in Debian, I spent some
> time on that bug.
> 
> The patch attached:
> - replaces the access to struct elements with getter usage.
> - disables 3des as it's no longer supported by OpenSSL.
> 
> It's pretty much untested and could also take a review.

Can you make an NMU with your patch
(or by changing it to libssl1.0-dev)?

> Christoph

Thanks
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Actually add the tags

[Debian Bug Tracking System]

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

> tags 842715 confirmed patch
Bug #842715 [src:skrooge] skrooge: FTBFS with Qt 5.7.1
Added tag(s) confirmed and patch.
> thanks
Stopping processing here.

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

Bug#844829: marked as done (mahimahi: FTBFS: build-dependency not installable: apache2-dev)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2016 20:04:18 -0800
with message-id 

Bug#831965: Status of asciidoc upload?

[Joseph Herlant]

Hi guys,

I migrated the package from dpatch to quilt and cut the tag.
I don't know if you prefer to work directly from the repo or from
mentors, so I uploaded it to mentors too:
https://mentors.debian.net/package/asciidoc
Any feedback appreciated.

Thanks
Joseph

Bug#847398: marked as done (mahimahi FTBFS: error: 'const SSL_METHOD* TLSv1_client_method()' is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 03:09:02 +
with message-id 
and subject line Bug#847398: fixed in mahimahi 0.96-1
has caused the Debian Bug report #847398,
regarding mahimahi FTBFS: error: 'const SSL_METHOD* TLSv1_client_method()' is 
deprecated
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.)


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

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

...
g++ -DHAVE_CONFIG_H -I. -I../..  -I./../util -I./../http -I../protobufs 
-std=c++11 -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra 
-Weffc++ -Werror -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o secure_socket.o 
secure_socket.cc
secure_socket.cc: In function 'SSL_CTX* initialize_new_context(SSL_MODE)':
secure_socket.cc:80:51: error: 'const SSL_METHOD* TLSv1_client_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );
   ^~~
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1598:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* 
TLSv1.0 */
 ^
secure_socket.cc:80:71: error: 'const SSL_METHOD* TLSv1_client_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );
   ^
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1598:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* 
TLSv1.0 */
 ^
secure_socket.cc:80:75: error: 'const SSL_METHOD* TLSv1_server_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );
   
^~~
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1597:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* 
TLSv1.0 */
 ^
secure_socket.cc:80:95: error: 'const SSL_METHOD* TLSv1_server_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );

   ^
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1597:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* 
TLSv1.0 */
 ^
cc1plus: all warnings being treated as errors
Makefile:408: recipe for target 'secure_socket.o' failed
make[4]: *** [secure_socket.o] Error 1
make[4]: Leaving directory '/«PKGBUILDDIR»/src/httpserver'
Makefile:378: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
--- End Message ---
--- Begin Message ---
Source: mahimahi
Source-Version: 0.96-1

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

Debian distribution maintenance software
pp.
Keith Winstein  (supplier of updated mahimahi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact 

Bug#848831: libpicard-java: fails to install: libpicard-java : Depends: libhtsjdk-java (< 2.8~) but 2.8.1+dfsg-1 is to be installed

[Andreas Beckmann]

Package: libpicard-java
Version: 2.8.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m20.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpsRR12g', 
'apt-get', '-y', 'install', 'libpicard-java=2.8.0+dfsg-1']
0m20.5s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   libpicard-java : Depends: libhtsjdk-java (< 2.8~) but 2.8.1+dfsg-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.
0m20.5s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpsRR12g', 'apt-get', '-y', 'install', 
'libpicard-java=2.8.0+dfsg-1']


cheers,

Andreas


libpicard-java_2.8.0+dfsg-1.log.gz
Description: application/gzip

Processed: affects wheezy, but not sid

[Debian Bug Tracking System]

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

> found 848830 3.6.0-12
Bug #848830 [dcmtk] dcmtk: remote stack buffer overflow CVE-2015-8979
Marked as found in versions dcmtk/3.6.0-12.
> fixed 848830 3.6.1~20160216-1
Bug #848830 [dcmtk] dcmtk: remote stack buffer overflow CVE-2015-8979
Marked as fixed in versions dcmtk/3.6.1~20160216-1.
> thanks
Stopping processing here.

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

Bug#848830: dcmtk: remote stack buffer overflow CVE-2015-8979

[Balint Reczey]

Package: dcmtk
Severity: grave
Version: 3.6.0-15
Tags: security

Hi,

the following vulnerability was published for dcmtk.

CVE-2015-8979[0]:
remote stack buffer overflow

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8979
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8979
Please adjust the affected versions in the BTS as needed.

Bug#808634: cadabra in Debian

[Axel Beckert]

Hi Kasper,

Axel Beckert wrote on 3rd of October:
> Kasper Peeters wrote:
> > > Were you able to build it with an updated system using GCC 6.2.x?
> >  
> > An 'apt-get update' and 'apt-get dist-upgrade' still does not bring me
> > 6.2.x. Do I need to do anything else to get it on testing?
> 
> My fault, sorry: I mixed up the switch from gcc-5 to gcc-6 as default
> (which happened in testing in the middle of August) with the switch
> from gcc-6 6.1.x to gcc-6 6.2.x which did indeed not yet happen in
> testing.
> 
> According to https://packages.qa.debian.org/g/gcc-6.html it might
> happen in 2 or 3 days.

Were you able to reproduce the build failures in the meanwhile?

Unfortunately the deadline for getting into the next Debian stable
release is approaching quickly -- and I should do a working upload
before 24th of December (end of this week) to have a chance to get
into the next Debian Stable release.

You don't need to do a new release for that -- a working patch against
1.45 or the right compiler flags to get it compiling would suffice.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#846459: marked as done (pam: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 01:35:22 +
with message-id 
and subject line Bug#846459: fixed in pam 1.1.8-3.4
has caused the Debian Bug report #846459,
regarding pam: add libfl-dev to Build-Depends
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.)


-- 
846459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pam
Severity: important
User: helm...@debian.org
Usertags: libfldep

pam will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since pam uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add "libfl-dev,
libfl-dev:native" to its Build-Depends. This change was previously
announced[1] to debian-devel in accordance with DevRef 7.1.1. Please
add the missing dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: pam
Source-Version: 1.1.8-3.4

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated pam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Dec 2016 01:03:58 +0100
Source: pam
Binary: libpam0g libpam-modules libpam-modules-bin libpam-runtime libpam0g-dev 
libpam-cracklib libpam-doc
Architecture: source
Version: 1.1.8-3.4
Distribution: unstable
Urgency: medium
Maintainer: Steve Langasek 
Changed-By: Adam Borowski 
Description:
 libpam-cracklib - PAM module to enable cracklib support
 libpam-doc - Documentation of PAM
 libpam-modules - Pluggable Authentication Modules for PAM
 libpam-modules-bin - Pluggable Authentication Modules for PAM - helper binaries
 libpam-runtime - Runtime support for the PAM library
 libpam0g   - Pluggable Authentication Modules library
 libpam0g-dev - Development files for PAM
Closes: 812566 846459
Changes:
 pam (1.1.8-3.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add libfl-dev to Build-Depends, fixing FTBFS.  Closes: #846459
   * Move xsl stuff to Build-Depends from -Indep to fix misbuilt manpages.
 Closes: #812566
Checksums-Sha1:
 28e3f4fa44fc1a711ecc5760f3dc1233270638ea 2237 pam_1.1.8-3.4.dsc
 8dabac801fb08f2f5d8691f405042198b8f8ceeb 139127 pam_1.1.8-3.4.diff.gz
Checksums-Sha256:
 f2e574b89d8d17b11a357214344167a8fe04509dbd8ad0d940f8c62495c6b8ad 2237 
pam_1.1.8-3.4.dsc
 6db9c98362e19a94d13f6508cadcb64993aa55256a7f0270ef536e5ad07c7a78 139127 
pam_1.1.8-3.4.diff.gz
Files:
 df61b785099de3e49879fa88447c76e0 2237 libs optional pam_1.1.8-3.4.dsc
 453f2a68f9036bbcc4845615bff36401 139127 libs optional pam_1.1.8-3.4.diff.gz

-BEGIN PGP SIGNATURE-

iQFIBAEBCAAyFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlhV0qIUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQLDtDb+rGgQFIhAf8DuiZ3Rl+6vv8sIvvOEpI/Gt8r55J
R8+9r3/IxvphyOLBy+054s2EuABhbZpx6dbsMxbv4jwuJBsKSmiiuHQX3hxB2bCP
D5QIdJb75zOO8GITZIAYOhFv+E7so1WcAXPX1KBfxIX1q5VAjk/315jFjdPGPBQ3
I+1aasc/Tn9IfXmGGy4wNSldST/UAHO+MKbbX25NKu/kVVd+iXQNExGVd8EYv1Nn
qAtywS1yEHygbWp2eOjkmXlBvGe2Xx0cf2FIBi0flzYsGjiI6arMA8XCeCn86MoS
ffJa+96PZsXwO//Szs8Y95aT5IJHEpW6h9r9JbKCIicKtXB2K5J5yr5mbA==
=+nxt
-END PGP SIGNATURE End Message ---

Bug#848818: xterm: ctlseqs.txt is not rebuilt from ctlseq.ms

[Ben Longbons]

On Mon, Dec 19, 2016 at 3:48 PM, Thomas Dickey  wrote:
> On Mon, Dec 19, 2016 at 02:39:27PM -0800, Ben Longbons wrote:
>> The ctlseqs.txt file is not built from ctlseqs.ms if it is modified
>> (which it should be, since it is wrong in a few places).
>
> I don't recall any bug reports on the topic.

I was working on that when I hit this. Besides the one you mentioned,
the xterm-specific `DECSED 3` is missing, for example. I'm sure there
was something with one of the string controls too ...

> ctlseqs.txt is part of the upstream sources, has been since June 2006.

Source means "preferred format for modification", not "in a tarball
somewhere". By your definititon, all of Windows is open-source.

>> * Remove the -P options to preserve formatting, less can handle it.
>
> The makefile doesn't use -P.

By using environment variables and extra pipe commands. But in any
case, a version *without* stripping all that formatting info, viewable
in the terminal, would be nice.

> no.  It's an ASCII file.  Pretty bullets don't help much, considering that
> less than 1% of the file uses that.  For interesting typography, refer to
> the PDF.

That's a matter of opinion. Using the letter `o` for bullets is
particular ugly to me.

>> * -Thtml
>>
>> The html and pdf formats provide significant features not in the txt
>
> groff's html format isn't useful.  I don't use that anymore:

You mean the format that is identical to the format you produce, other
than the (admittedly better) filenames for the included `.png`s?

-Ben

Bug#848806: marked as done (golang: FTBFS: debian/rules:32: recipe for target 'override_dh_auto_test-arch' failed)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 14:24:39 +1300
with message-id 

Bug#848733: xapian-bindings: FTBFS: ../../../../java/org/xapian/TradWeight.java:15: error: cannot access XapianJNI

[Olly Betts]

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

On Mon, Dec 19, 2016 at 10:12:01PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

I've just tried to reproduce locally with "sbuild -dunstable xapian-bindings"
and "DEB_BUILD_OPTIONS=parallel=8\ nocheck sbuild -dunstable xapian-bindings"
(in case it was a parallel building issue) and both succeeded.

Cheers,
Olly

Processed: Re: Bug#848733: xapian-bindings: FTBFS: ../../../../java/org/xapian/TradWeight.java:15: error: cannot access XapianJNI

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #848733 [src:xapian-bindings] xapian-bindings: FTBFS: 
../../../../java/org/xapian/TradWeight.java:15: error: cannot access XapianJNI
Severity set to 'important' from 'serious'
> tags -1 +unreproducible
Bug #848733 [src:xapian-bindings] xapian-bindings: FTBFS: 
../../../../java/org/xapian/TradWeight.java:15: error: cannot access XapianJNI
Added tag(s) unreproducible.

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

Bug#848710: marked as done (compiz: FTBFS when built with dpkg-buildpackage -A (cannot create debian/compiz-gnome/DEBIAN/triggers: Directory nonexistent))

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 01:18:29 +
with message-id 
and subject line Bug#848710: fixed in compiz 1:0.9.13.0+16.10.20160818.2-4
has caused the Debian Bug report #848710,
regarding compiz: FTBFS when built with dpkg-buildpackage -A (cannot create 
debian/compiz-gnome/DEBIAN/triggers: Directory nonexistent)
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.)


-- 
848710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:compiz
Version: 1:0.9.13.0+16.10.20160818.2-3
Severity: serious
Tags: patch

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --with python2
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/compiz-0.9.13.0+16.10.20160818.2'
dh_auto_configure -- -DCOMPIZ_BUILD_WITH_RPATH=FALSE 
-DCMAKE_BUILD_TYPE=RelWithDebInfo -DCOMPIZ_PACKAGING_ENABLED=TRUE 
-DCOMPIZ_DISABLE_GS_SCHEMAS_INSTALL=OFF -DCOMPIZ_DISABLE_PLUGIN_KDE=ON 
-DCOMPIZ_BUILD_TESTING=OFF -DUSE_KDE4=OFF -DBUILD_XORG_GTEST=OFF 
-DBUILD_METACITY=OFF
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCOMPIZ_BUILD_WITH_RPATH=FALSE 
-DCMAKE_BUILD_TYPE=RelWithDebInfo -DCOMPIZ_PACKAGING_ENABLED=TRUE 
-DCOMPIZ_DISABLE_GS_SCHEMAS_INSTALL=OFF -DCOMPIZ_DISABLE_PLUGIN_KDE=ON 
-DCOMPIZ_BUILD_TESTING=OFF -DUSE_KDE4=OFF -DBUILD_XORG_GTEST=OFF 
-DBUILD_METACITY=OFF
-- The C compiler identification is GNU 6.2.1
-- The CXX compiler identification is GNU 6.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

make[1]: Leaving directory '/<>/compiz-0.9.13.0+16.10.20160818.2'
   dh_installdocs -i -O--parallel
   dh_installchangelogs -i -O--parallel
   dh_installman -i -O--parallel
   dh_python2 -i -O--parallel
W: dh_python2:479: Please add dh-python package to Build-Depends
   dh_lintian -i -O--parallel
   dh_icons -i -O--parallel
   dh_perl -i -O--parallel
   dh_link -i -O--parallel
   dh_strip_nondeterminism -i -O--parallel
   dh_compress -i -O--parallel
   dh_fixperms -i -O--parallel
   dh_installdeb -i -O--parallel
   debian/rules override_dh_gencontrol
make[1]: Entering directory '/<>/compiz-0.9.13.0+16.10.20160818.2'
dh_gencontrol -- -Vcoreabiversion=20151010
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
dpkg-gencontrol: warning: Depends field of package 
compizconfig-settings-manager: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
not NFS-safe
make[1]: Leaving directory '/<>/compiz-0.9.13.0+16.10.20160818.2'
   dh_md5sums -i -O--parallel
   debian/rules override_dh_builddeb
make[1]: Entering directory '/<>/compiz-0.9.13.0+16.10.20160818.2'
# Workaround for a possible dh_makeshlibs bug:
echo 'activate-noawait ldconfig' >> debian/compiz-gnome/DEBIAN/triggers
/bin/sh: 1: cannot create debian/compiz-gnome/DEBIAN/triggers: Directory 
nonexistent
debian/rules:76: recipe for target 'override_dh_builddeb' failed
make[1]: *** [override_dh_builddeb] Error 2
make[1]: Leaving directory '/<>/compiz-0.9.13.0+16.10.20160818.2'
debian/rules:82: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


This happens because we are creating arch-indep packages only,
so debian/compiz-gnome/[...] does not exist.

This could be fixed by overriding dh_builddeb only for arch-dependent builds.

Trivial (but untested) patch follows.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -72,7 +72,7 @@ override_dh_gencontrol:
 

Bug#831965: Status of asciidoc upload?

[Joseph Herlant]

Thanks Christian and Raphael,

>> I can sponsor the package but given that Alexander is no longer
>> interested, I guess he has no reason to oppose a switch to "3.0 (quilt)"
>> and drop dpatch.
>>
>> Once you have done that, I'm willing to review and upload your package.

I'll try to push the change about getting rid of dpatch tonight. I'll
let you know when it's done.

> Just that patch to sort out this severity serious bug. I'm not sure
> what else is in git, etc. If you need a sponsor for those changes, I
> could take a look though.

Thanks, 2 pairs of eyes are better than 1! ;)

I'll let you know when the migration to 3.0 (quilt) is pushed to git
so the review is ready.

Thanks! :)

Bug#848603: Enable innodb_large_prefix

[Christian Hofstaedtler]

* Otto Kekäläinen  [161219 22:21]:
> We live in a world where WordPress sites expect to be able to save
> emojis in comments :)

Sure, but other apps expect their indexes to work.

> We have had utf8mb4 as default in Debian and Ubuntu for a many years.

Possibly, but it's only now the provider for (default-)mysql-server.

> You are experiencing a corner case with a single app (which one?).

pdns-backend-mysql

Maybe next time when flipping providers, doing an rdep build and
install check is in order. Discovering that your package breaks
with no upload on your side - as such, a random discovery - is not
fun at all.

-- 
christian hofstaedtler 

Bug#831965: asciidoc: FTBFS with dpkg-buildpackage -A: doc/testasciidoc.1: No such file or directory at /usr/bin/dh_installman line 131.

[Christian Hofstaedtler]

* Joseph Herlant  [161219 19:21]:
> Did you upload al the last changes that happened to the repo since
> 2014 or only this particular patch?

Just that patch to sort out this severity serious bug. I'm not sure
what else is in git, etc. If you need a sponsor for those changes, I
could take a look though.

-- 
christian hofstaedtler 

Processed: Re: Bug#848710: compiz: FTBFS when built with dpkg-buildpackage -A (cannot create debian/compiz-gnome/DEBIAN/triggers: Directory nonexistent)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #848710 [src:compiz] compiz: FTBFS when built with dpkg-buildpackage -A 
(cannot create debian/compiz-gnome/DEBIAN/triggers: Directory nonexistent)
Added tag(s) pending.

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

Bug#848710: compiz: FTBFS when built with dpkg-buildpackage -A (cannot create debian/compiz-gnome/DEBIAN/triggers: Directory nonexistent)

[Cyril Brulebois]

Control: tag -1 patch pending

Hi,

Santiago Vila  (2016-12-19):
> Package: src:compiz
> Version: 1:0.9.13.0+16.10.20160818.2-3
> Severity: serious
> Tags: patch
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder already tried as well)
> but it failed:

Thanks so much for spotting this. I had to perform a source+amd64+all
upload for NEW, then switched to source only (no code changes…), and
almost missed it.

> This happens because we are creating arch-indep packages only,
> so debian/compiz-gnome/[...] does not exist.

Yeah, reproduced with sbuild -A --no-arch-any locally.

> This could be fixed by overriding dh_builddeb only for arch-dependent
> builds.
> 
> Trivial (but untested) patch follows.
> 
> Thanks.
> 
> --- a/debian/rules
> +++ b/debian/rules
> @@ -72,7 +72,7 @@ override_dh_gencontrol:
>  override_dh_auto_test:
>   #dh_auto_test
>  
> -override_dh_builddeb:
> +override_dh_builddeb-arch:
>   # Workaround for a possible dh_makeshlibs bug:
>   echo 'activate-noawait ldconfig' >> debian/compiz-gnome/DEBIAN/triggers
>   chmod 644 debian/compiz-gnome/DEBIAN/triggers

This fixed the FTBFS locally, and looking at a debdiff of all generated
arch:all packages before/after the change, packages are looking good to
me, so I'll upload this again.


Thanks again!
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: Digital signature

Bug#848824: marked as done (trigger-rally: File conflict: /usr/share/man/man6/trigger-rally.6.gz in both packages)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 00:49:26 +
with message-id 
and subject line Bug#848824: fixed in trigger-rally 0.6.5+dfsg-2
has caused the Debian Bug report #848824,
regarding trigger-rally: File conflict: /usr/share/man/man6/trigger-rally.6.gz 
in both packages
to be marked as done.

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

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


-- 
848824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trigger-rally
Version: 0.6.5+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With this version, the man page is now shipped in the -data package as
well as the main package.

You should remove it from the main package, and give appropiate
Breaks/Conflicts/Provides.


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

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

Versions of packages trigger-rally depends on:
ii  libalut0  1.1.0-5
ii  libc6 2.24-8
ii  libgcc1   1:7-20161201-1
ii  libgl1-mesa-glx [libgl1]  13.0.2-3
ii  libglew2.02.0.0-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libopenal11:1.17.2-4
ii  libphysfs12.0.3-3+b1
ii  libsdl2-2.0-0 2.0.5+dfsg1-1
ii  libsdl2-image-2.0-0   2.0.1+dfsg-2+b2
ii  libstdc++67-20161201-1
ii  libtinyxml2-4 4.0.1-1
ii  trigger-rally-data0.6.4+dfsg-2

trigger-rally recommends no packages.

trigger-rally suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: trigger-rally
Source-Version: 0.6.5+dfsg-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated trigger-rally 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: Tue, 20 Dec 2016 01:00:50 +0100
Source: trigger-rally
Binary: trigger-rally trigger-rally-data
Architecture: source
Version: 0.6.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 trigger-rally - free 3D rally racing car game
 trigger-rally-data - free 3D rally racing car game - data files
Closes: 848824
Changes:
 trigger-rally (0.6.5+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/rules: Install manpages only with the architecture-dependent
 dh_installman target. Thanks to Ben Longbons for the report.
 This error was exposed by building source-only packages. (Closes: #848824)
Checksums-Sha1:
 86a59ccd3255b519e98368301ddba1ee52eb585f 2426 trigger-rally_0.6.5+dfsg-2.dsc
 decc015e7bba2dac63b7e54e40c07d58d8b6d08c 17048 
trigger-rally_0.6.5+dfsg-2.debian.tar.xz
Checksums-Sha256:
 77c09bf858d1e301d59ad045d19d416c469c13083ca028b02c6fc19a75e919e5 2426 
trigger-rally_0.6.5+dfsg-2.dsc
 b1a3a31ab23a5fbe92b1314ff99121b5af0ea5c6e5c97c92d90cf1c0a4c01642 17048 
trigger-rally_0.6.5+dfsg-2.debian.tar.xz
Files:
 4a30b7089d7c4e0fbc8800d18905ff72 2426 games optional 
trigger-rally_0.6.5+dfsg-2.dsc
 82f6b4c994f83b1e4c3afbcd0fb940ef 17048 games optional 
trigger-rally_0.6.5+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlhYeGxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkyJYP/15+J0Hi9/4KywkNLadxf5UX3POBEZTIu84h
DecOb5Sx53tzZirE5yuRzR3ZEY/2jy541O84EzpBVpYZCEBfBUeEbB9Zagsy5GQE
ybae0g/tEdsN/VP/2aZ80uMIysLRAxZfSrVrKOtRp9Ssmn0H1jytZWOZT4JFdrzy

Processed: Re: clips: diff for NMU version 6.24-3.1

[Debian Bug Tracking System]

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

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

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

Bug#817394: clips: diff for NMU version 6.24-3.1

[Christoph Biedl]

Control: 821972 patch pending

> Find below the debdiff for a NMU I've prepared for clips (versioned as
> 6.24-3.1), upload to DELAYED/2 will follow shortly. Please feel free to
> tell me if I should delay it longer.

Later I realized there's a third issue in clips. Updated debdiff
below, upload to DELAYED/2 will follow in a few hours.

Christoph

diff -u clips-6.24/debian/changelog clips-6.24/debian/changelog
--- clips-6.24/debian/changelog
+++ clips-6.24/debian/changelog
@@ -1,3 +1,19 @@
+clips (6.24-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build-arch and build-indep targets to debian/rules. Patch by
+Santiago Vila. Closes: #821972
+
+ -- Christoph Biedl   Mon, 19 Dec 2016 
19:07:00 +0100
+
+clips (6.24-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Bump debhelper compat level. Closes: #817394
+  * Replace obsolete Source-Version substvar. Closes: #833208
+
+ -- Christoph Biedl   Mon, 19 Dec 2016 
00:00:20 +0100
+
 clips (6.24-3) unstable; urgency=low
 
   * Change the upstream page, as it is now http://clipsrules.sourceforge.net/:
diff -u clips-6.24/debian/compat clips-6.24/debian/compat
--- clips-6.24/debian/compat
+++ clips-6.24/debian/compat
@@ -1 +1 @@
-4
+10
diff -u clips-6.24/debian/rules clips-6.24/debian/rules
--- clips-6.24/debian/rules
+++ clips-6.24/debian/rules
@@ -38,6 +38,8 @@
--enable-xclips --with-clipssrc=../../clipssrc/ 
cd clipssrc && sh ./configure --prefix=$(CURDIR)/debian/xclips/usr 
 
+build-arch: build
+build-indep: build
 build: build-stamp
 build-stamp: configure
dh_testdir
@@ -151 +153 @@
-.PHONY: build build-x clean binary binary-arch binary-indep install
+.PHONY: build build-arch build-indep build-x clean binary binary-arch 
binary-indep install
diff -u clips-6.24/debian/control clips-6.24/debian/control
--- clips-6.24/debian/control
+++ clips-6.24/debian/control
@@ -2,7 +2,7 @@
 Section: interpreters
 Priority: optional
 Maintainer: Javier Fernandez-Sanguino Pen~a 
-Build-Depends: libncurses-dev, debhelper
+Build-Depends: libncurses-dev, debhelper (>= 10~)
 Standards-Version: 3.5.7
 Homepage: http://clipsrules.sourceforge.net
 
@@ -40,7 +40,7 @@
 Package: libclips-dev
 Architecture: any
 Section: libdevel
-Depends: libclips  (= ${Source-Version}), libc6-dev
+Depends: libclips  (= ${binary:Version}), libc6-dev
 Recommends: clips-doc
 Description: CLIPS shared libraries
  CLIPS 6.0 is an OPS-like forward chaining production system written 


signature.asc
Description: Digital signature

Bug#845037: libschroedinger-1.0-0: is this package fit for stretch?

[Andreas Cadhalpun]

On 22.11.2016 20:35, Andreas Cadhalpun wrote:
> That's fine. I'll also wait with fixing ffmpeg for the next upstream
> bugfix release that is expected soon.
> 
> I've now filed bugs #845361 - #845366 about the other packages.

This is now all done and the fixes migrated to testing.

Thus I've requested the removal of schroedinger (see #848828).

Best regards,
Andreas

Bug#811899: gnuift: FTBFS with GCC 6: declared in this scope

[Christoph Biedl]

Christoph Biedl wrote...

> There are several other issues in gnuift as [well] but given the relatively
> high popcon rank I decided to spend some time on this. Upload should
> follow within the next 48 hours. Testers wanted, drop me a line.

Tentative packaging available at
https://mentors.debian.net/debian/pool/main/g/gnuift/gnuift_0.1.14+ds-1.dsc

Christoph


signature.asc
Description: Digital signature

Bug#848779: marked as done (pyfits: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 00:04:36 +
with message-id <e1cj7v2-000bhl...@fasolo.debian.org>
and subject line Bug#848779: fixed in pyfits 1:3.4-4
has caused the Debian Bug report #848779,
regarding pyfits: FTBFS: dh_auto_test: pybuild --test --test-nose -i 
python{version} -p 2.7 returned exit code 13
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild --parallel 
>dh_testdir -O--buildsystem=pybuild -O--parallel
>dh_update_autotools_config -O--buildsystem=pybuild -O--parallel
>dh_auto_configure -O--buildsystem=pybuild -O--parallel
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild -O--parallel
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/file.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/card.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/verify.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/_numpy_hacks.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/py3compat.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/header.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/core.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/_release.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/column.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/util.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/convenience.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/diff.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> copying pyfits/fitsrec.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> copying pyfits/_compat/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> copying pyfits/_compat/weakref.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> copying pyfits/_compat/odict.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_odict_py2
> copying pyfits/_compat/_odict_py2/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_odict_py2
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_weakset_py2
> copying pyfits/_compat/_weakset_py2/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/_compat/_weakset_py2
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/extern
> copying pyfits/extern/six.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/extern
> copying pyfits/extern/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/extern
> creating /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/table.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/image.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/compressed.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/hdulist.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/streaming.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying pyfits/hdu/base.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pyfits/hdu
> copying 

Bug#828457: marked as done (nodejs: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2016 00:04:31 +
with message-id 
and subject line Bug#828457: fixed in nodejs 6.9.2~dfsg-1
has caused the Debian Bug report #828457,
regarding nodejs: FTBFS with openssl 1.1.0
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.)


-- 
828457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 4.4.3~dfsg-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/nodejs_4.4.3~dfsg-1_amd64-20160529-1457

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 6.9.2~dfsg-1

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs 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, 20 Dec 2016 00:42:16 +0100
Source: nodejs
Binary: nodejs-dev nodejs nodejs-dbg nodejs-legacy
Architecture: source
Version: 6.9.2~dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 nodejs - evented I/O for V8 javascript
 nodejs-dbg - evented I/O for V8 javascript (debug)
 nodejs-dev - evented I/O for V8 javascript (development files)
 nodejs-legacy - evented I/O for V8 javascript (legacy symlink)
Closes: 828457 841981
Changes:
 nodejs (6.9.2~dfsg-1) experimental; urgency=medium
 .
   * New upstream version 6.9.2~dfsg
   * Build-Depend libssl1.0-dev (Closes: #828457)
   * nodejs Recommends ca-certificates (Closes: #841981)
   * Skip two tests failing only in autopkgtest
   * Override workaround for source-is-missing (See: #848825)
   * Drop package-needs-versioned-debhelper-build-depends override.
Checksums-Sha1:
 9a37cae7fc19952cc959c4903ea14303ecb95344 2515 nodejs_6.9.2~dfsg-1.dsc
 14b412b636d2b5c9187bf94d9125b27523cf9ecd 11667995 nodejs_6.9.2~dfsg.orig.tar.gz
 b342e8008a4551957656a069dfbc844318741295 61364 
nodejs_6.9.2~dfsg-1.debian.tar.xz
Checksums-Sha256:
 8754e9c9a6ca134a1b39fc4340398bf889d522f351b9dd692a8da663b6be80e0 2515 
nodejs_6.9.2~dfsg-1.dsc
 2e31d7f42c501f21615de7993b02d755316ea693a0c9d832a6cb04144db5c6af 11667995 
nodejs_6.9.2~dfsg.orig.tar.gz
 88031cfe44a29f19a44c731c5af57543a39d277d16fe1325500dff351a7158fd 61364 
nodejs_6.9.2~dfsg-1.debian.tar.xz
Files:
 eedf34a5a9581812148eb82496e26eb6 2515 web - nodejs_6.9.2~dfsg-1.dsc
 a0fc8ac8f7dd89993b0015e0720384a4 11667995 web - nodejs_6.9.2~dfsg.orig.tar.gz
 37561273c3286a709438aef768db0a90 61364 web - nodejs_6.9.2~dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlhYcHESHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0QPYP/3205eNKNfIbCupTxCTi9rv1/TKq9JJ1
UP4F5UEZ2SPE1lqb9YkDMMVWqtf0Vbcdt8exvSpFlEdgVZLBJzStFQQ9OKS9K5jb
3mYd5H+8ElzpZh2RC04owwtLCSKmfNizedD6FdtyDQd82GaxrYDKVOrqlK1alBSz
6BIhQS8JsYmNS7S1xFQukLed7aRJUoJT5N0Jb+5eCiojK+cy6oSWNqhL73Fltjdu
GUdL1ks8KGHZKC1svB867/RfGUY9Kc8puskaf3rm8xCtGH9skaaCpg/00nNxMv3p
YkfyTEY7XVAgpQCHRPlsxEyKsb71UvTwB5F+biDclEFrvSaYOivZnO4wac9cLsmo
ikKYnYoxkpnRE5z3Sndfgou81+73y0+2TWD9ZFJQx7b6e8S7A3DY43sse3jqHieQ
0fKtUjk8dKs+9/cg6K9WOcg5ZZcFp2dOtne3QCiuTQL3MNgvd15hbEqS2VCpf2yJ
c3qqKMCE0RRmslBJHtUn4K2iX/NaMSM7a259jf35DRSbm09n4SW9MjatoO+Pp8xm

Bug#766298: An update on trust router and release status

[Sam Hartman]

There was a trust router release in October.
At one level, this release is probably functional enough that it would
be nice to have included in stretch.
At another level,there have been enough upstream bugs files that I
don't think it's stable enough to include and support for the lifetime
of stretch.

However, I think  we're in a good position to put something into
experimental (and then stretch-backports) very soon.  Also, now that
freeradius 3 is in Debian, we should be able to get that infrastructure
enabled.
I think shortly after the release of buster, we can close this bug and
let moonshot-trust-router migrate into testing.

Bug#848818: xterm: ctlseqs.txt is not rebuilt from ctlseq.ms

[Thomas Dickey]

On Mon, Dec 19, 2016 at 02:39:27PM -0800, Ben Longbons wrote:
> Package: xterm
> Version: 327-2
> Severity: serious

severity's incorrect.

You should change that.

> Justification: Policy 2.1
> 
> Dear Maintainer,
> 
> The ctlseqs.txt file is not built from ctlseqs.ms if it is modified
> (which it should be, since it is wrong in a few places).

I don't recall any bug reports on the topic.  The only to-do item for
ctlseqs.ms which I _have_ is a comment from a different person that at
least one item isn't ordered alphabetically.  I'm working on _that_,
now (another script to check the file).

ctlseqs.txt is part of the upstream sources, has been since June 2006.

Each time I make an update to ctlseqs.ms, I regenerate the ".txt" file
using the rule in the makefile.  If it's not, my test-builds would fail.

Since all of the upstream source has proper timestamps, there's
nothing to rebuild.  Debian builds from pristine upstream source, so
there's no reason for timestamp contamination, say, by pulling it from
someone's source repo.
 
> The command to bytewise-reproduce the existing file is:
> 
> $ groff -P{-c,-b,-o,-u} -Tascii -t -ms < ctlseqs.ms > ctlseqs.txt
> 
> Note: You need to add a build-dep on `groff`, not just `groff-base`,
> in order to install the macro packages `-ms`.
> 
> But there are some *better* command variants.
> 
> * Remove the -P options to preserve formatting, less can handle it.

The makefile doesn't use -P.

> * -Tutf8 (better quotes/bullets; the VT fonts have everything they need).

no.  It's an ASCII file.  Pretty bullets don't help much, considering that
less than 1% of the file uses that.  For interesting typography, refer to
the PDF.

> * -Tpdf

You can do this with the makefile.

> * -Thtml
> 
> The html and pdf formats provide significant features not in the txt

groff's html format isn't useful.  I don't use that anymore:

http://invisible-island.net/scripts/man2html.html

> version, though the PDF doesn't have a Table of Contents.

hmm - ms macros are said to support table of contents,

https://www.hactrn.net/ietf/rfcgen/textms.html

but I've not found it necessary, e.g, generated with man2html plus
a post-processing script to construct the navigation area:

http://invisible-island.net/xterm/ctlseqs/ctlseqs.html

> -Ben
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, x32, arm64
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages xterm depends on:
> ii  libc6   2.24-8
> ii  libfontconfig1  2.11.0-6.7
> ii  libice6 2:1.0.9-1+b1
> ii  libtinfo5   6.0+20161126-1
> ii  libutempter01.1.6-3
> ii  libx11-62:1.6.4-2
> ii  libxaw7 2:1.0.13-1
> ii  libxft2 2.3.2-1
> ii  libxinerama12:1.1.3-1+b1
> ii  libxmu6 2:1.1.2-2
> ii  libxpm4 1:3.5.11-1+b1
> ii  libxt6  1:1.1.5-1
> ii  xbitmaps1.1.1-2
> 
> Versions of packages xterm recommends:
> ii  x11-utils  7.7+3
> 
> Versions of packages xterm suggests:
> ii  xfonts-cyrillic  1:1.0.4
> 
> -- no debconf information
> 

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature

Processed: tagging 792002

[Debian Bug Tracking System]

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

> tags 792002 - moreinfo unreproducible
Bug #792002 {Done: Bastian Blank } [lvm2] lvm2-monitor 
service causes long delay at boot (encrypted root/swap)
Bug #774082 {Done: Bastian Blank } [lvm2] systemd: system 
with LVM and lvmetad does not bot after upgrade to jessie
Bug #782793 {Done: Bastian Blank } [lvm2] systemd: ext4 
filesystem on lvm on raid causes boot to enter emergency shell
Bug #782865 {Done: Bastian Blank } [lvm2] systemd: ext4 
filesystem on lvm on raid causes boot to enter emergency shell
Bug #791869 {Done: Bastian Blank } [lvm2] lvm2: updating 
src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other 
than / fails
Removed tag(s) unreproducible and moreinfo.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) unreproducible and moreinfo.
Removed tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Processed: Bug#848779 marked as pending

[Debian Bug Tracking System]

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

> tag 848779 pending
Bug #848779 [src:pyfits] pyfits: FTBFS: dh_auto_test: pybuild --test 
--test-nose -i python{version} -p 2.7 returned exit code 13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#848779: marked as pending

[Aurelien Jarno]

tag 848779 pending
thanks

Hello,

Bug #848779 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/pyfits.git;a=commitdiff;h=1172593

---
commit 11725934caf637225b5157cae10fe49688235d9a
Author: Aurelien Jarno 
Date:   Tue Dec 20 00:44:35 2016 +0100

Add patches/04-numpy-1.12.patch taken from astropy to fix the testsuite 
with numpy 1.12 (closes: #848779).

diff --git a/debian/changelog b/debian/changelog
index d1b4603..3313306 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,12 @@
 pyfits (1:3.4-4) UNRELEASED; urgency=medium
 
+  [ Ondřej Nový ]
   * Fixed VCS URL (https)
 
+  [ Aurelien Jarno ]
+  * Add patches/04-numpy-1.12.patch taken from astropy to fix the testsuite
+with numpy 1.12 (closes: #848779).
+
  -- Ondřej Nový   Tue, 29 Mar 2016 21:49:23 +0200
 
 pyfits (1:3.4-3) unstable; urgency=medium

Processed: Re: Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 lvm2
Bug #782793 [systemd] systemd: ext4 filesystem on lvm on raid causes boot to 
enter emergency shell
Bug reassigned from package 'systemd' to 'lvm2'.
No longer marked as found in versions systemd/215-16.
Ignoring request to alter fixed versions of bug #782793 to the same values 
previously set
> forcemerge 782865 -1
Bug #782865 {Done: Bastian Blank } [lvm2] systemd: ext4 
filesystem on lvm on raid causes boot to enter emergency shell
Bug #774082 {Done: Bastian Blank } [lvm2] systemd: system 
with LVM and lvmetad does not bot after upgrade to jessie
Bug #791869 {Done: Bastian Blank } [lvm2] lvm2: updating 
src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other 
than / fails
Bug #792002 {Done: Bastian Blank } [lvm2] lvm2-monitor 
service causes long delay at boot (encrypted root/swap)
Bug #782865 {Done: Bastian Blank } [lvm2] systemd: ext4 
filesystem on lvm on raid causes boot to enter emergency shell
Added tag(s) moreinfo and unreproducible.
Added tag(s) unreproducible and moreinfo.
Added tag(s) moreinfo and unreproducible.
Added tag(s) unreproducible and moreinfo.
Bug #782793 [lvm2] systemd: ext4 filesystem on lvm on raid causes boot to enter 
emergency shell
Severity set to 'grave' from 'important'
Marked Bug as done
There is no source info for the package 'lvm2' at version '1.02.126-3' with 
architecture ''
Unable to make a source version for version '1.02.126-3'
Marked as fixed in versions lvm2/2.02.126-3 and 1.02.126-3.
Marked as found in versions lvm2/2.02.122-2, lvm2/2.02.126-2, lvm2/2.02.122-1, 
and lvm2/2.02.111-2.2.
Bug #774082 {Done: Bastian Blank } [lvm2] systemd: system 
with LVM and lvmetad does not bot after upgrade to jessie
Bug #791869 {Done: Bastian Blank } [lvm2] lvm2: updating 
src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other 
than / fails
Bug #792002 {Done: Bastian Blank } [lvm2] lvm2-monitor 
service causes long delay at boot (encrypted root/swap)
Merged 774082 782793 782865 791869 792002

-- 
774082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774082
782793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782793
782865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782865
791869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791869
792002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#848285: jackd2: spits verbose output and exits immediately when the client stops sending audio

[Francesco Poli]

On Sun, 18 Dec 2016 22:56:00 + James Cowgill wrote:

[...]
> On 15/12/16 23:18, Francesco Poli (wintermute) wrote:
[...]
> > I experienced a grave bug: as soon as the client (audacious, firefox through
> > ALSA redirection in ~/.asoundrc, ...) stops sending audio to the jackd
> > sound server, the latter spits a bunch of output messages and exits
> > immediately (as if the --temporary option were passed, no!, even worse!).
> 
> Firstly, apologies for not testing this fully before uploading the most
> recent version :/

It may happen.
It's weird that nobody noticed in unstable, before the package managed
to migrate to testing, but anyway...

> 
> This appears this is a toolchain bug. Simply recompiling the latest
> version of jackd2 with gcc-6_6.2.0-6 (the version the -3 revision was
> compiled with) makes it work again. The toolchain bug will probably need
> reducing before anyone can look at it however.

Good that you are able to reproduce the bug and managed to pinpoint the
cause.
I hope this can be fixed soon.

Thanks for your helpfulness!
Bye.


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


pgpF3c5EHF69P.pgp
Description: PGP signature

Bug#848824: trigger-rally: File conflict: /usr/share/man/man6/trigger-rally.6.gz in both packages

[Ben Longbons]

Package: trigger-rally
Version: 0.6.5+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With this version, the man page is now shipped in the -data package as
well as the main package.

You should remove it from the main package, and give appropiate
Breaks/Conflicts/Provides.


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

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

Versions of packages trigger-rally depends on:
ii  libalut0  1.1.0-5
ii  libc6 2.24-8
ii  libgcc1   1:7-20161201-1
ii  libgl1-mesa-glx [libgl1]  13.0.2-3
ii  libglew2.02.0.0-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libopenal11:1.17.2-4
ii  libphysfs12.0.3-3+b1
ii  libsdl2-2.0-0 2.0.5+dfsg1-1
ii  libsdl2-image-2.0-0   2.0.1+dfsg-2+b2
ii  libstdc++67-20161201-1
ii  libtinyxml2-4 4.0.1-1
ii  trigger-rally-data0.6.4+dfsg-2

trigger-rally recommends no packages.

trigger-rally suggests no packages.

-- no debconf information

Processed: Re: gnuift: FTBFS with GCC 6: declared in this scope

[Debian Bug Tracking System]

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

> tags 811899 pending
Bug #811899 [gnuift] gnuift: FTBFS with GCC 6: declared in this scope
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811899: gnuift: FTBFS with GCC 6: declared in this scope

[Christoph Biedl]

tags 811899 pending
thanks

Martin Michlmayr wrote...

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

There are several other issues in gnuift as but given the relatively
high popcon rank I decided to spend some time on this. Upload should
follow within the next 48 hours. Testers wanted, drop me a line.

Christoph


signature.asc
Description: Digital signature

Bug#848798: slof: FTBFS: powerpc64-linux-gnu-ld: OF.fsi: not in ELF format

[Aurelien Jarno]

control: reassign -1 binutils
control: retitle -1 binutils: ld ignores -b binary
control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=20968
control: affects -1 slof

On 2016-12-19 22:35, Lucas Nussbaum wrote:
> Source: slof
> Version: 20160223+dfsg-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161219 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > make[6]: Entering directory 
> > '/<>/slof-20160223+dfsg/clients/net-snk'
> > [LD]client
> > [CC]paflof.o
> > [LD]OF.o
> > powerpc64-linux-gnu-ld: OF.fsi: not in ELF format
> > /<>/slof-20160223+dfsg/slof/Makefile.inc:72: recipe for target 
> > 'OF.o' failed
> > make[4]: *** [OF.o] Error 1
> 
> The full build log is available from:
>http://aws-logs.debian.net/2016/12/19/slof_20160223+dfsg-1_unstable.log

This is actually a binutils bug, reported upstream as PR/20968.
Reassigning the bug.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#841611: ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': /<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64

[Dirk Eddelbuettel]

Hi Balint,

On 19 December 2016 at 13:57, Bálint Réczey wrote:
| Hi Dirk,
| 
| 2016-12-19 0:30 GMT+01:00 Dirk Eddelbuettel :
| >
| > On 10 November 2016 at 13:22, Balint Reczey wrote:
| > | Control: reassign -1 gsl 2.2.1+dfsg-1
| > | Control: affects -1 ruby-gsl
| > |
| > |
| > | Hi Dirk,
| > |
| > | It seems ruby-gsl is missing some deprecated functions.
| > | Please re-enable debian/patches/dont-disable-deprecated to let ruby-gsl
| > | build again.
| >
| > Well I could -- but according to https://github.com/SciRuby/rb-gsl a current
| > ruby-gsl exists.
| >
| > Why are we stuck with the 1.* series? Should we not port forward?
| 
| I tried updating to 2.1.0 but it still uses deprecated functions,
| hence the reassignment.

Well I'd rather not. I think upstream would rather see a plainer versions.

Can you detail what is missing?

Also see https://github.com/SciRuby/rb-gsl/blob/master/ChangeLog#L3-L7 which 
says

== Fri March 4 2016
* Added compatibility for NMatrix interconversion with GSL::Vector and 
GSL::Matrix
* Added NMatrix compatibility to various to make them compatible with NMatrix 
data types.
* Gem is now compatible with GSL 2.1.
* Version bump to 2.1.0

Sounds to me it should work with our version.

Dirk

| 
| Cheers,
| Balint
| 
| >
| > Dirk
| >
| > | Cheers,
| > | Balint
| > |
| > | On Fri, 21 Oct 2016 15:37:05 +0200 Lucas Nussbaum  
wrote:
| > | > Source: ruby-gsl
| > | > Version: 1.16.0.6+dfsg1-2
| > | > Severity: serious
| > | > Tags: stretch sid
| > | > User: debian...@lists.debian.org
| > | > Usertags: qa-ftbfs-20161021 qa-ftbfs
| > | > Justification: FTBFS on amd64
| > | >
| > | > Hi,
| > | >
| > | > During a rebuild of all packages in sid, your package failed to build on
| > | > amd64.
| > | >
| > | > Relevant part (hopefully):
| > | > > /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
| > | > >   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
| > | > >   from 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/ruby/vendor_ruby/gsl.rb:6:in
 `'
| > | > >   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
| > | > >   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
| > | > >   from test_helper.rb:2:in `'
| > | > > ERROR: Test "ruby2.3" failed:
| > | >
| >
| > --
| > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#848796: pgapack: FTBFS: /bin/sh: 1: cd: can't cd to lib/linux/

[Dirk Eddelbuettel]

Lucas,

Thanks for running the checks.

I filed a RM request.  Time to retire this package.

Dirk

On 19 December 2016 at 22:35, Lucas Nussbaum wrote:
| Source: pgapack
| Version: 1.1.1-3
| Severity: serious
| Tags: stretch sid
| User: debian...@lists.debian.org
| Usertags: qa-ftbfs-20161219 qa-ftbfs
| Justification: FTBFS on amd64
| 
| Hi,
| 
| During a rebuild of all packages in sid, your package failed to build on
| amd64.
| 
| Relevant part (hopefully):
| >  debian/rules build
| > dh_testdir
| > test -d /usr/lib/openmpi && \
| > ./configure -arch linux -cc gcc -cflags "-O3 -fPIC -D_REENTRANT 
-Wall" \
| > -mpiinc /usr/lib/openmpi/include -mpilib 
/usr/lib/libmpi.so && \
| > cd source && /usr/bin/make && cd -
| > debian/rules:37: recipe for target 'build-stamp' failed
| > make: [build-stamp] Error 1 (ignored)
| > test -d /usr/include/mpich2 && \
| > ./configure -arch linux -cc mpicc.mpich2 -cflags "-O3 -fPIC 
-D_REENTRANT -Wall" \
| > -mpiinc /usr/include/mpich2 -mpilib 
/usr/lib/libmpich.so && \
| > cd source && /usr/bin/make && cd -
| > debian/rules:37: recipe for target 'build-stamp' failed
| > make: [build-stamp] Error 1 (ignored)
| > test -d /usr/include/lam && \
| > ./configure -arch linux -cc gcc -cflags "-O3 -fPIC -D_REENTRANT 
-Wall" \
| > -mpiinc /usr/include/lam -mpilib /usr/lib/liblam.so && \
| > cd source && /usr/bin/make && cd -
| > debian/rules:37: recipe for target 'build-stamp' failed
| > make: [build-stamp] Error 1 (ignored)
| > (cd lib/linux/  && \
| > mv -v libpgaO.a libpgapack-mpi1.a && \
| > gcc -shared -Wl,-soname,libpgapack-mpi1.so.1 -o 
libpgapack-mpi1.so.1.0 *.o && \
| > rm *.o)
| > /bin/sh: 1: cd: can't cd to lib/linux/
| > debian/rules:37: recipe for target 'build-stamp' failed
| > make: *** [build-stamp] Error 2
| 
| The full build log is available from:
|http://aws-logs.debian.net/2016/12/19/pgapack_1.1.1-3_unstable.log
| 
| A list of current common problems and possible solutions is available at
| http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
| 
| About the archive rebuild: The rebuild was done on EC2 VM instances from
| Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
| failed build was retried once to eliminate random failures.

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#848820: snakemake: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:snakemake
Version: 3.9.0+dfsg-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/snakemake-3.9.0+dfsg'
dh_auto_build
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build

[... snipped ...]

2   four
2   one
2   three
2   two
9
snakemake.logging: INFO: rule one:
input: a
output: 1.a
wildcards: sample=a
snakemake.logging: INFO: 
snakemake.logging: INFO: rule one:
input: b
output: 1.b
wildcards: sample=b
snakemake.logging: INFO: 
snakemake.logging: INFO: 1 of 9 steps (11%) done
snakemake.logging: INFO: rule two:
input: 1.a
output: 2.a
wildcards: sample=a
snakemake.logging: INFO: 
snakemake.logging: INFO: 2 of 9 steps (22%) done
snakemake.logging: INFO: rule two:
input: 1.b
output: 2.b
wildcards: sample=b
snakemake.logging: INFO: 
snakemake.logging: WARNING: Removing temporary output file 1.a.
snakemake.logging: INFO: 3 of 9 steps (33%) done
snakemake.logging: ERROR: WorkflowError:
File 2.a seems to be a broken symlink.
snakemake.logging: WARNING: Waiting at most 3 seconds for missing files.
- >> end captured logging << -

--
Ran 70 tests in 36.186s

FAILED (errors=1)
Error in job two while creating output file 2.b.
MissingOutputException in line 9 of 
/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build/tests/test_symlink_temp/Snakefile:
Missing files after 3 seconds:
2.b
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/snakemake-3.9.0+dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 returned 
exit code 13
debian/rules:16: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends. I attach three different build logs.

They happened while trying to build the package 100 times, so the failure
rate is about 3%. If you try to reproduce this, please try a lot of times.

Thanks.

snakemake_3.9.0+dfsg-1_amd64-20161219T213843Z.gz
Description: application/gzip


snakemake_3.9.0+dfsg-1_amd64-20161219T214637Z.gz
Description: application/gzip


snakemake_3.9.0+dfsg-1_amd64-20161219T215659Z.gz
Description: application/gzip

Bug#845737: New release

[Santiago Vila]

After testing 100 times, sbuild no longer hangs, which is good news.

But there are still failing tests. I'll report them in a different
bug report.

Thanks.

Bug#848818: xterm: ctlseqs.txt is not rebuilt from ctlseq.ms

[Ben Longbons]

Package: xterm
Version: 327-2
Severity: serious
Justification: Policy 2.1

Dear Maintainer,

The ctlseqs.txt file is not built from ctlseqs.ms if it is modified
(which it should be, since it is wrong in a few places).

The command to bytewise-reproduce the existing file is:

$ groff -P{-c,-b,-o,-u} -Tascii -t -ms < ctlseqs.ms > ctlseqs.txt

Note: You need to add a build-dep on `groff`, not just `groff-base`,
in order to install the macro packages `-ms`.

But there are some *better* command variants.

* Remove the -P options to preserve formatting, less can handle it.
* -Tutf8 (better quotes/bullets; the VT fonts have everything they need).
* -Tpdf
* -Thtml

The html and pdf formats provide significant features not in the txt
version, though the PDF doesn't have a Table of Contents.

-Ben


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

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

Versions of packages xterm depends on:
ii  libc6   2.24-8
ii  libfontconfig1  2.11.0-6.7
ii  libice6 2:1.0.9-1+b1
ii  libtinfo5   6.0+20161126-1
ii  libutempter01.1.6-3
ii  libx11-62:1.6.4-2
ii  libxaw7 2:1.0.13-1
ii  libxft2 2.3.2-1
ii  libxinerama12:1.1.3-1+b1
ii  libxmu6 2:1.1.2-2
ii  libxpm4 1:3.5.11-1+b1
ii  libxt6  1:1.1.5-1
ii  xbitmaps1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+3

Versions of packages xterm suggests:
ii  xfonts-cyrillic  1:1.0.4

-- no debconf information

Bug#848783: marked as done (pysal: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2016 22:21:19 +
with message-id <e1cj6j5-000hdx...@fasolo.debian.org>
and subject line Bug#848783: fixed in pysal 1.13.0-2
has caused the Debian Bug report #848783,
regarding pysal: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 
returned exit code 13
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh  build --with python2,python3 --buildsystem pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> file pysal.py (for module pysal) not found
> creating /<>/.pybuild/pythonX.Y_2.7/build/pysal
> copying pysal/common.py -> /<>/.pybuild/pythonX.Y_2.7/build/pysal
> copying pysal/test_NameSpace.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal
> copying pysal/config.py -> /<>/.pybuild/pythonX.Y_2.7/build/pysal
> copying pysal/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal
> copying pysal/version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal
> creating /<>/.pybuild/pythonX.Y_2.7/build/pysal/region
> copying pysal/region/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/region
> copying pysal/region/components.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/region
> copying pysal/region/maxp.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/region
> copying pysal/region/randomregion.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/region
> creating /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/Distance.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/user.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/spatial_lag.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/weights.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/spintW.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/util.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/Contiguity.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/_contW_binning.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/_contW_lists.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/_contW_rtree.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> copying pysal/weights/Wsets.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/weights
> creating /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/segmentLocator.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/shapes.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/locators.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/kdtree.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/sphere.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/comparators.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/standalone.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> copying pysal/cg/rtree.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pysal/cg
> creating /<>/.pybuild/pythonX.Y_2.7/bu

Bug#848786: [Syslog-ng-maintainers] Bug#848786: syslog-ng: FTBFS: build-dependency not installable: libmongoc-dev

[GCS]

Control: tags -1 +pending

On Mon, Dec 19, 2016 at 10:25 PM, Lucas Nussbaum <lu...@debian.org> wrote:
> Source: syslog-ng
> Version: 3.8.1-8
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161219 qa-ftbfs
> Justification: FTBFS on amd64
[...]
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
[...]
>> The following packages have unmet dependencies:
>>  sbuild-build-depends-syslog-ng-dummy : Depends: libmongoc-dev but it is not 
>> going to be installed
 Until now, libmongoc-dev was built with OpenSSL 1.0+ just like
syslog-ng; but recently it switched to build with OpenSSL 1.1+.
Currently syslog-ng doesn't build with the newer OpenSSL, but an
upstream patch exists[1] which needs porting.

Thanks for the report,
Laszlo/GCS
[1] 
https://github.com/balabit/syslog-ng/commit/55f1b97fd699a925db1bd8ea4201432b66484a42

Processed: Re: [Syslog-ng-maintainers] Bug#848786: syslog-ng: FTBFS: build-dependency not installable: libmongoc-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #848786 [src:syslog-ng] syslog-ng: FTBFS: build-dependency not installable: 
libmongoc-dev
Added tag(s) pending.

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

Bug#848770: trilinos: FTBFS: Test failures

[Nico Schlömer]

Thanks Lucas for the report.

A new version (12.10.1-2) has already been submitted to NEW, fixing the
test failures.

Cheers,
Nico

On Mon, Dec 19, 2016 at 10:43 PM Lucas Nussbaum <lu...@debian.org> wrote:

> Source: trilinos
> Version: 12.10.1-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161219 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > Stokhos  =  15.38 sec (52 tests)
> > Teko =  45.70 sec (19 tests)
> > Teuchos  =  10.19 sec (53 tests)
> > Thyra=  22.12 sec (80 tests)
> > Tpetra   =  31.81 sec (113 tests)
> > Triutils =   0.55 sec (2 tests)
> >
> > Total Test time (real) = 320.29 sec
> >
> > The following tests FAILED:
> >   592 - Isorropia_part_sizes_MPI_4 (Failed)
> >   630 - ShyLUCore_belos_driver_MPI_4 (Failed)
> >   631 - ShyLUCore_shylu_factor_MPI_4 (Failed)
> >   677 - Teko_ProbingFactory_MPI_1 (Failed)
> > Errors while running CTest
> > Makefile:152: recipe for target 'test' failed
>
> The full build log is available from:
>http://aws-logs.debian.net/2016/12/19/trilinos_12.10.1-1_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
>
>

Bug#848806: [pkg-golang-devel] Bug#848806: golang: FTBFS: debian/rules:32: recipe for target 'override_dh_auto_test-arch' failed

[Michael Hudson-Doyle]

Wait, there is still a golang source package in sid? It should be removed.

On 20 December 2016 at 10:32, Lucas Nussbaum <lu...@debian.org> wrote:

> Source: golang
> Version: 2:1.6.1-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161219 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > set -ex; \
> >   cd src; \
> >   export PATH="/<>/bin:$PATH"; \
> >   eval "$(go tool dist env)"; \
> >   bash run.bash -k -no-rebuild;
> > + cd src
> > + export PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:
> /usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> > + go tool dist env
> > + eval CC="gcc"
> > CC_FOR_TARGET="gcc"
> > GOROOT="/<>"
> > GOBIN="/<>/bin"
> > GOARCH="amd64"
> > GOOS="linux"
> > GOHOSTARCH="amd64"
> > GOHOSTOS="linux"
> > GOTOOLDIR="/<>/pkg/tool/linux_amd64"
> > + CC=gcc
> > + CC_FOR_TARGET=gcc
> > + GOROOT=/<>
> > + GOBIN=/<>/bin
> > + GOARCH=amd64
> > + GOOS=linux
> > + GOHOSTARCH=amd64
> > + GOHOSTOS=linux
> > + GOTOOLDIR=/<>/pkg/tool/linux_amd64
> > + bash run.bash -k -no-rebuild
> >
> > # Testing packages.
> > okarchive/tar 0.044s
> > okarchive/zip 0.141s
> > okbufio   0.192s
> > okbytes   0.315s
> > okcompress/bzip2  0.247s
> > okcompress/flate  0.868s
> > okcompress/gzip   0.070s
> > okcompress/lzw0.053s
> > okcompress/zlib   0.089s
> > okcontainer/heap  0.010s
> > okcontainer/list  0.014s
> > okcontainer/ring  0.028s
> > okcrypto/aes  0.044s
> > okcrypto/cipher   0.045s
> > okcrypto/des  0.028s
> > okcrypto/dsa  0.021s
> > okcrypto/ecdsa0.052s
> > okcrypto/elliptic 0.087s
> > okcrypto/hmac 0.017s
> > okcrypto/md5  0.033s
> > okcrypto/rand 0.055s
> > okcrypto/rc4  0.145s
> > okcrypto/rsa  0.192s
> > okcrypto/sha1 0.029s
> > okcrypto/sha256   0.022s
> > okcrypto/sha512   0.024s
> > okcrypto/subtle   0.045s
> > okcrypto/tls  2.756s
> > okcrypto/x509 3.129s
> > okdatabase/sql0.083s
> > okdatabase/sql/driver 0.009s
> > okdebug/dwarf 0.016s
> > okdebug/elf   0.076s
> > okdebug/gosym 0.536s
> > okdebug/macho 0.018s
> > okdebug/pe0.045s
> > okdebug/plan9obj  0.024s
> > okencoding/ascii850.022s
> > okencoding/asn1   0.024s
> > okencoding/base32 0.021s
> > okencoding/base64 0.015s
> > okencoding/binary 0.007s
> > okencoding/csv0.011s
> > okencoding/gob0.088s
> > okencoding/hex0.014s
> > okencoding/json   0.370s
> > okencoding/pem0.080s
> > okencoding/xml0.071s
> > okerrors  0.016s
> > okexpvar  0.111s
> > okflag0.018s
> > okfmt 0.223s
> > okgo/ast  0.034s
> > okgo/build0.156s
> > okgo/constant 0.027s
> > okgo/doc  0.089s
> > okgo/format   0.021s
> > okgo/internal/gccgoimporter   0.041s
> > okgo/internal/gcimporter  0.364s
> > okgo/parser   0.063s
> > okgo/printer  0.591s
> > okgo/scanner  0.016s
> > okgo/token0.047s
> > okgo/types1.856s
> > okhash/adler320.017s
> > okhash/crc32  0.067s
> > okhash/crc64  0.038s
> > okhash/fnv0.074s
> > okhtml0.079s
> > okhtml/template   0.084s
> > okimage   0.226s
> > okimage/color 0.119s
> > okimage/draw  0.133s
> > okimage/gif   0.118s
> > okimage/jpeg  0.347s
> > okimage/png   0.056s
> > okindex/suffixarray   0.049s
> > okinternal/golang.org/x/net/http2/hpack   0.009s
> > okinternal/singleflight   0.024s
> > okinternal/trace  0.074s
> > okio  0.061s
> > okio/ioutil   0.038s
> > oklog 0.084s
> > oklog/syslog  2.087s
> > okmath0.153s
> > okmath/big0.804s
> > okmath/

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 848795 src:python-os-api-ref
Bug #848795 [src:swift] swift: FTBFS: TypeError: unsupported operand type(s) 
for +=: 'int' and 'str'
Bug reassigned from package 'src:swift' to 'src:python-os-api-ref'.
No longer marked as found in versions swift/2.10.0-3.
Ignoring request to alter fixed versions of bug #848795 to the same values 
previously set
> reassign 848769 src:python-os-api-ref
Bug #848769 [src:heat] heat: FTBFS: TypeError: unsupported operand type(s) for 
+=: 'int' and 'str'
Bug reassigned from package 'src:heat' to 'src:python-os-api-ref'.
No longer marked as found in versions heat/1:7.0.0-1.
Ignoring request to alter fixed versions of bug #848769 to the same values 
previously set
> forcemerge 848647 848795 848769
Bug #848647 {Done: Ondřej Nový } [src:python-os-api-ref] 
python-os-api-ref: FTBFS with docutils 0.13: TypeError: unsupported operand 
type(s) for +=: 'int' and 'str'
Bug #848769 [src:python-os-api-ref] heat: FTBFS: TypeError: unsupported operand 
type(s) for +=: 'int' and 'str'
Set Bug forwarded-to-address to 'https://review.openstack.org/412227'.
Marked Bug as done
Added indication that 848769 affects src:swift
Marked as fixed in versions python-os-api-ref/0.3.0+dfsg1-3.
Marked as found in versions python-os-api-ref/0.3.0+dfsg1-2.
Added tag(s) upstream and patch.
Bug #848647 {Done: Ondřej Nový } [src:python-os-api-ref] 
python-os-api-ref: FTBFS with docutils 0.13: TypeError: unsupported operand 
type(s) for +=: 'int' and 'str'
Added tag(s) sid and stretch.
Bug #848795 [src:python-os-api-ref] swift: FTBFS: TypeError: unsupported 
operand type(s) for +=: 'int' and 'str'
Set Bug forwarded-to-address to 'https://review.openstack.org/412227'.
Marked Bug as done
Added indication that 848795 affects src:swift
Marked as fixed in versions python-os-api-ref/0.3.0+dfsg1-3.
Marked as found in versions python-os-api-ref/0.3.0+dfsg1-2.
Added tag(s) upstream and patch.
Merged 848647 848769 848795
> --
Stopping processing here.

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

Bug#848652: [Pkg-openssl-devel] Bug#848652: build fails on ppc64el, double free or corruption, stack suggests libssl

[Kurt Roeckx]

On Mon, Dec 19, 2016 at 09:57:42PM +0100, Daniel Pocock wrote:
> 
> 
> On 19/12/16 21:26, Sebastian Andrzej Siewior wrote:
> > On 2016-12-19 09:40:38 [+0100], Daniel Pocock wrote:
> >> Could this be a known issue on ppc64el or with libssl?
> > 
> > Nothing comes to mind. But it explodes the same way (but without the
> > fancy backtrace) on hurd, too.
> > 
> >> FAIL: stunTestVectors
> >> =
> >>
> >> INFO | 20161218-094209.416 |  | RESIP:TEST | 70366852992352 | 
> >> stunTestVectors.cxx:168 | All tests passed!
> >> *** Error in `/«PKGBUILDDIR»/reTurn/test/.libs/stunTestVectors': double 
> >> free or corruption (out): 0x01001be00e20 ***
> >> === Backtrace: =
> >> /lib/powerpc64le-linux-gnu/libc.so.6(+0x829e8)[0x3fff8ea529e8]
> >> /lib/powerpc64le-linux-gnu/libc.so.6(+0x8c098)[0x3fff8ea5c098]
> >> /lib/powerpc64le-linux-gnu/libc.so.6(+0x8cbec)[0x3fff8ea5cbec]
> >> /usr/lib/powerpc64le-linux-gnu/libcrypto.so.1.0.2(CRYPTO_free+0x60)[0x3fff8ef79430]
> >> /usr/lib/powerpc64le-linux-gnu/libssl.so.1.0.2(+0x4ded8)[0x3fff8f19ded8]
> >> /usr/lib/powerpc64le-linux-gnu/libcrypto.so.1.0.2(sk_pop_free+0x74)[0x3fff8f0134c4]
> >> /usr/lib/powerpc64le-linux-gnu/libssl.so.1.0.2(SSL_COMP_free_compression_methods+0x3c)[0x3fff8f1a0b6c]
> >> /«PKGBUILDDIR»/reTurn/test/.libs/stunTestVectors(_ZNSt15_Sp_counted_ptrIPN4asio3ssl6detail17openssl_init_base7do_initELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv+0x64)[0x5e41a044]
> >> /«PKGBUILDDIR»/reTurn/test/.libs/stunTestVectors(_ZNSt10shared_ptrIN4asio3ssl6detail17openssl_init_base7do_initEED1Ev+0xdc)[0x5e41a41c]
> > 
> > So a deconstructor in asio invokes SSL_COMP_free_compression_methods()
> > on the end and we explode while the list is cleaned up. Now lets look a
> > little… Oh what is this rutil/ssl/OpenSSLInit.cxx:
> > 
> > | OpenSSLInit::~OpenSSLInit()
> > | {
> > |mInitialized = false;
> > |ERR_remove_state(0);// free thread error queue
> > |EVP_cleanup();// Clean up data allocated during 
> > OpenSSL_add_all_algorithms
> > |CRYPTO_cleanup_all_ex_data();
> > |ERR_free_strings();// Clean up data allocated during 
> > SSL_load_error_strings
> > |sk_SSL_COMP_free (SSL_COMP_get_compression_methods()); 
> > | 
> > | //  CRYPTO_mem_leaks_fp(stderr);
> > |cerr << "HELLO" << endl;
> > | delete [] mMutexes;
> > | }
> >  
> > |(sid)bigeasy@debbuildd:/build/resiprocate-1.11.0~alpha8/reTurn/test$ 
> > ./stunTestVectors 
> > |INFO | 20161219-202446.416 |  | RESIP:TEST | 140378940325248 | 
> > stunTestVectors.cxx:168 | All tests passed!
> > |HELLO
> > 
> > Hmmm. It gives me the impression that exploding here is what should be
> > expected and libssl is the victim here.
> > 
> 
> Thanks for taking the time to look at this.
> 
> Is there an example of how this cleanup should be done, or is there a
> specific line of code there that you believe is out of place?
> 
> If it is definitely not an openssl issue then the bug can be moved back
> to src:resiprocate

You should use SSL_COMP_free_compression_methods() so that we can
put the internal pointer to NULL.


Kurt