Processed: libproxy: diff for NMU version 0.4.13-1.1

Processing control commands: > tags 844956 + patch Bug #844956 [src:libproxy] libproxy: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DWITH_DOTNET=ON

Bug#844956: libproxy: diff for NMU version 0.4.13-1.1

Control: tags 844956 + patch Control: tags 844956 + pending Dear maintainer, I've prepared an NMU for libproxy (versioned as 0.4.13-1.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru libproxy-0.4.13/debian/changelog

Bug#845080: gss-ntlmssp FTBFS: test failures on big endian architectures

Source: gss-ntlmssp Version: 0.7.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=gss-ntlmssp=sid ... *** Test with NTLMv1 authTest GSSAPI conversation (user env file) Test: FAIL Test GSSAPI conversation (no SEAL) Test: FAIL Test GSSAPI conversation (with password) Test:

Bug#844081: Reproducer

Hello, I tried to reproduce the issue in my environment with: i=0;while true;do python -m pytest tests;ret=$?;i=$[ $i+1 ];echo "Run: $i"; [ $ret -ne 0 ] && break; done and in similar way with pbuilder that I am using and FTBFS didn't ever happen (tried 50+ builds). I have suspicion that these

Bug#845062: marked as done (ifrench-gut: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo: error: cannot fstat file ../ifrench-gut_1.0-31_amd64.deb))

Your message dated Sun, 20 Nov 2016 09:03:26 + with message-id and subject line Bug#845062: fixed in ifrench-gut 1:1.0-32 has caused the Debian Bug report #845062, regarding ifrench-gut: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo:

Bug#845058: [Pkg-fonts-devel] Bug#845058: fonts-noto: Installing the package freezes all graphical applications.

Hi Valentin, Quoting Valentin Lorentz (2016-11-19 23:58:44) > Installing fonts-noto on my computer leads to *all* of my graphic > applications to enter an infinite loop, using all my CPU cores, and > blocking aptitude. This persists until I stop aptitude and remove > fonts-noto. [...] >

Processed: net-tools: diff for NMU version 1.60+git20150829.73cef8a-2.1

Processing control commands: > tags 844073 + patch Bug #844073 [src:net-tools] net-tools: FTBFS: /usr/include/linux/ip.h:85:8: error: redefinition of 'struct iphdr' Added tag(s) patch. > tags 844073 + pending Bug #844073 [src:net-tools] net-tools: FTBFS: /usr/include/linux/ip.h:85:8: error:

Bug#844073: net-tools: diff for NMU version 1.60+git20150829.73cef8a-2.1

Control: tags 844073 + patch Control: tags 844073 + pending Dear maintainer, I've prepared an NMU for net-tools (versioned as 1.60+git20150829.73cef8a-2.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru

Bug#844796: gnome-shell: FTBFS: /<>/src/tmp-introspect2qs0g0tu/.libs/ShellMenu-0.1: error while loading shared libraries: libmutter-clutter-1.0.so: cannot open shared object file: No such

Hi, On 20/11/16 at 01:33 +0100, Michael Biebl wrote: > Builds fine in a stretch chroot. Have you tried in a sid chroot? I just tried and can still reproduce it. (but I did not manage to further isolate the problem) Lucas

Bug#844914: rsyslog: FTBFS: Tests failures

Hi, On 19/11/16 at 22:35 +0100, Michael Biebl wrote: > control: tags -1 + moreinfo unreproducible > > Am 19.11.2016 um 08:04 schrieb Lucas Nussbaum: > > >> === > >> need to be root to run this test - skipping > >> SKIP

Bug#845081: wmbiff FTBFS on s390x: test failure

Source: wmbiff Version: 0.4.29-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=wmbiff=s390x=0.4.29-1=1479607292 ... wmbiff/ imap4: Couldn't parse line imap:foo:mi@ta@bar/mybox (0) If this used to work, run wmbiff with the -relax option, and send mail to

Processed: Merge bugs caused by python-pycparser not being installable

Processing commands for cont...@bugs.debian.org: > reassign 844794 python-pycparser Bug #844794 [src:zaqar] zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1) Bug reassigned from package 'src:zaqar' to 'python-pycparser'. No longer marked as found in versions

Bug#845082: numexpr FTBFS on ppc64el: test failures

Source: numexpr Version: 2.6.1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=numexpr=ppc64el=2.6.1-1=1479607449 Lots of failures like: ... == FAIL: test_scalar0_int_aggressive_OPERATIONS_0309

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

On Sat, Nov 19, 2016 at 07:17:12PM +0100, Andreas Cadhalpun wrote: > 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

Processed: retitle 844141 to libsys-cpuaffinity-perl: FTBFS: Failed test 'bind to all processors successful 18446744073709551615 == 18446744073709551616-1'

Processing commands for cont...@bugs.debian.org: > retitle 844141 libsys-cpuaffinity-perl: FTBFS: Failed test 'bind to all > processors successful 18446744073709551615 == 18446744073709551616-1' Bug #844141 [src:libsys-cpuaffinity-perl] libsys-cpuaffinity-perl: FTBFS:

Processed: Re: Bug#828545: simutrans: FTBFS with openssl 1.1.0

Processing commands for cont...@bugs.debian.org: > severity 828545 serious Bug #828545 {Done: Markus Koschany } [src:simutrans] simutrans: FTBFS with openssl 1.1.0 Severity set to 'serious' from 'important' > block 827061 by 828545 Bug #827061 [release.debian.org] transition:

Bug#844956: marked as done (libproxy: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL

Your message dated Sun, 20 Nov 2016 09:48:49 + with message-id and subject line Bug#844956: fixed in libproxy 0.4.13-1.1 has caused the Debian Bug report #844956, regarding libproxy: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr

Bug#845084: pylucene FTBFS on mips, mipsel: [compile] Segmentation fault

Source: pylucene Version: 4.10.1+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=pylucene=sid ... rm -f lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar find /usr/share/maven-repo -name `basename lucene-java-4.10.x/lucene/expressions/lib/asm-commons-4.x.jar`

Bug#845083: pylucene FTBFS on armel, armhf: python2.7 test/test_TermRangeQuery.py terminated by signal 11

Source: pylucene Version: 4.10.1+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=pylucene=sid ... python2.7 test/test_TermRangeQuery.py xargs: python2.7: terminated by signal 11 Makefile:434: recipe for target 'test' failed make[2]: *** [test] Error 125

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 844807 libedit-dev Bug #844807 [src:ceph] ceph: FTBFS: ld: cannot find -lncurses Bug reassigned from package 'src:ceph' to 'libedit-dev'. No longer marked as found in versions ceph/0.80.11-1.1. Ignoring request to alter fixed versions of

Bug#845058: [Pkg-fonts-devel] Bug#845058: fonts-noto: Installing the package freezes all graphical applications.

Running `fc-cache -fs` before installing fonts-noto took only a few seconds. Installing fonts-noto while not being logged in worked, thanks. On 20/11/2016 00:10, Norbert Preining wrote: > On Sat, 19 Nov 2016, Valentin Lorentz wrote: >> killall fc-cache > > fc-cache might run for quite some

Bug#828458: marked as done (nordugrid-arc must (build-)depend on libssl1.0-dev)

Your message dated Sun, 20 Nov 2016 11:19:53 + with message-id and subject line Bug#828238: fixed in nordugrid-arc 5.3.0~rc1-1 has caused the Debian Bug report #828238, regarding nordugrid-arc must (build-)depend on libssl1.0-dev to be marked as done.

Bug#844549: network-console broken: no screen to be resumed matching sh

Martin Michlmayr writes: > * Samuel Thibault [2016-11-16 23:03]: >> But AIUI the intent was to have screen in ssh connections too. > > I'm not sure what the intent was. I assume you're right because Roger > didn't exclude screen from the network-console

Processed (with 1 error): clone glibc source issue

Processing commands for cont...@bugs.debian.org: > clone 844866 -1 Bug #844866 [src:cross-toolchain-base] cross-toolchain-base: FTBFS: ../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range (5 is not between 0 and 1) Bug 844866 cloned as bug 845096 > reassign -1 src:glibc

Bug#844721: libgtest-dev isn't replacing dir with symlink on upgrade

On Sat, Nov 19, 2016 at 10:06:17PM -0600, Steve M. Robbins wrote: > On Fri, Nov 18, 2016 at 01:29:07PM +0100, David Kalnischkies wrote: > > You should also update your README.Debian and the descriptions with the > > new paths and the transitional package as [...] > > Thanks. Updated

Bug#844914: rsyslog: FTBFS: Tests failures

Am 20.11.2016 um 08:50 schrieb Lucas Nussbaum: > > Test: ./empty-hostname.sh > > rsyslogd started with pid 71369 > imdiag[13500]: mainqueue empty > expected hostname

Processed: tagging 841571

Processing commands for cont...@bugs.debian.org: > tags 841571 + fixed-upstream Bug #841571 [src:lightspark] lightspark: FTBFS: abc.cpp:30:30: fatal error: llvm/PassManager.h: No such file or directory Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need

Bug#845111: mypaint: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo error)

Package: src:mypaint Version: 1.2.0-2 Severity: serious Tags: patch 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:

Bug#833225: Patch for the idle3-tools FTBFS

Control: tags -1 patch --- debian/rules.old2016-11-20 13:23:31.0 + +++ debian/rules2016-11-20 13:23:49.0 + @@ -9,5 +9,3 @@ override_dh_auto_install: dh_auto_install -- binprefix=/usr -override_dh_builddeb: - dh_builddeb -- -Zbzip2 -z9 cu

Processed: Patch for the idle3-tools FTBFS

Processing control commands: > tags -1 patch Bug #833225 [src:idle3-tools] idle3-tools: Uses obsolete compressor for .deb data.tar member Added tag(s) patch. -- 833225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833225 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#844013: marked as done (tiff: CVE-2016-9273)

Your message dated Sun, 20 Nov 2016 13:50:43 + with message-id and subject line Bug#844013: fixed in tiff 4.0.7-1 has caused the Debian Bug report #844013, regarding tiff: CVE-2016-9273 to be marked as done. This means that you claim that the problem has

Bug#828579: The patch is upstream

On 11/18/2016 01:46 AM, Hon Ching(Vicky) Lo wrote: > On Thu, 2016-11-17 at 14:18 -0500, Hon Ching(Vicky) Lo wrote: >> The patch that supports OpenSSL 1.1 (backward-compatible) is upstream: >> https://sourceforge.net/p/trousers/trousers/ci/05411ea68746acbaf4e69295be50b9a47cddb2fd/ >> >> >> Vicky >

Bug#828579: marked as done (trousers: FTBFS with openssl 1.1.0)

Your message dated Sun, 20 Nov 2016 17:06:27 + with message-id and subject line Bug#828579: fixed in trousers 0.3.14+fixed1-1 has caused the Debian Bug report #828579, regarding trousers: FTBFS with openssl 1.1.0 to be marked as done. This means that you

Processed: Also add the affects

Processing commands for cont...@bugs.debian.org: > affects 811835 src:opal Bug #811835 [src:ptlib] ptlib: FTBFS with GCC 6 Bug #811996 [src:ptlib] ptlib: FTBFS with GCC 6 Bug #837577 [src:ptlib] ptlib: FTBFS with GCC 6 Bug #843972 [src:ptlib] ptlib: FTBFS with GCC 6 Bug #844860 [src:ptlib] ptlib:

Bug#811835: Patch for the ptlib gcc 6 FTBFS

Control: reassign -1 src:ptlib Control: forcemerge 811996 -1 Control: retitle -1 ptlib: FTBFS with GCC 6 Control: tags -1 patch What broke the build is that gcc 6 changed the default C++ standard from C++98 to C++14. Not all valid C++98 code is also valid C++11 and C++14 code. Note that this

Processed: Patch for the ptlib gcc 6 FTBFS

Processing control commands: > reassign -1 src:ptlib Bug #811835 [opal] opal: FTBFS with GCC 6: no match for Bug reassigned from package 'opal' to 'src:ptlib'. No longer marked as found in versions 3.10.10~dfsg2-2. Ignoring request to alter fixed versions of bug #811835 to the same values

Bug#844900: sra-sdk: FTBFS: libncbi-vdb.so: undefined reference to `mbedtls_x509_crt_parse_file'

Control: reassign -1 libncbi-vdb2 Control: affects -1 src:sra-sdk Control: retitle -1 libncbi-vdb.so.2 is not linked with all libraries On Sat, Nov 19, 2016 at 07:50:15AM +0100, Lucas Nussbaum wrote: >... > > /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to > >

Processed: Re: Bug#844900: sra-sdk: FTBFS: libncbi-vdb.so: undefined reference to `mbedtls_x509_crt_parse_file'

Processing control commands: > reassign -1 libncbi-vdb2 Bug #844900 [libncbi-vdb2] libncbi-vdb.so.2 is not linked with all libraries Ignoring request to reassign bug #844900 to the same package > affects -1 src:sra-sdk Bug #844900 [libncbi-vdb2] libncbi-vdb.so.2 is not linked with all libraries

Processed: Re: Bug#844900: sra-sdk: FTBFS: libncbi-vdb.so: undefined reference to `mbedtls_x509_crt_parse_file'

Processing control commands: > reassign -1 libncbi-vdb2 Bug #844900 [src:sra-sdk] sra-sdk: FTBFS: libncbi-vdb.so: undefined reference to `mbedtls_x509_crt_parse_file' Bug reassigned from package 'src:sra-sdk' to 'libncbi-vdb2'. No longer marked as found in versions sra-sdk/2.7.0-1. Ignoring

Bug#844258: closed by Tianon Gravi <tia...@debian.org> (Bug#844258: fixed in golang-defaults 2:1.7~2)

On Sun, Nov 20, 2016 at 07:11:31PM +0100, Andreas Henriksson wrote: [...] > Please discuss this with ftp team. [...] Seconds after sending this mail I was pointed to #845003 Thanks for filing that and lets see how it goes. Regards, Andreas Henriksson

Bug#844549: marked as done (network-console broken: no screen to be resumed matching sh)

Your message dated Sun, 20 Nov 2016 16:35:04 + with message-id and subject line Bug#844549: fixed in rootskel 1.121 has caused the Debian Bug report #844549, regarding network-console broken: no screen to be resumed matching sh to be marked as done. This

Bug#828936: marked as done (python-mhash: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found)

Your message dated Sun, 20 Nov 2016 17:04:58 + with message-id and subject line Bug#828936: fixed in python-mhash 1.4-1.2 has caused the Debian Bug report #828936, regarding python-mhash: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found to be marked as

Bug#828514: Building with OpenSSL 1.0.2 is sufficient for stretch

Control: tags -1 patch Not a perfect solution but sufficient for stretch is the patch below to use OpenSSL 1.0.2 --- debian/control.old 2016-11-20 15:44:46.0 + +++ debian/control 2016-11-20 15:45:01.0 + @@ -4,7 +4,7 @@ Maintainer: Debian VoIP Team

Processed: Building with OpenSSL 1.0.2 is sufficient for stretch

Processing control commands: > tags -1 patch Bug #828514 [src:ptlib] ptlib: FTBFS with openssl 1.1.0 Added tag(s) patch. -- 828514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > unblock 844907 by 844366 Bug #844907 [src:python-tornado] python-tornado: FTBFS: Tests failures 844907 was blocked by: 844366 844907 was not blocking any bugs. Removed blocking bug(s) of 844907: 844366 > unblock 844234 by 844366 Bug #844234

Bug#844258: closed by Tianon Gravi <tia...@debian.org> (Bug#844258: fixed in golang-defaults 2:1.7~2)

Hello! On Sat, Nov 19, 2016 at 01:27:03AM +, Debian Bug Tracking System wrote: [...] > golang-defaults (2:1.7~2) unstable; urgency=medium > . >* Remove "s390x" again (Closes: #844258) I might be wrong, but I doubt this really fixes anything... You're only preventing the new upload

Processed: tagging 845122, closing 845122

Processing commands for cont...@bugs.debian.org: > tags 845122 + upstream Bug #845122 [sniffit] CVE-2014-5439: Root shell on Sniffit Added tag(s) upstream. > close 845122 0.3.7.beta-20 Bug #845122 [sniffit] CVE-2014-5439: Root shell on Sniffit Marked as fixed in versions sniffit/0.3.7.beta-20.

Bug#845122: tagging 845122, closing 845122

tags 845122 + upstream close 845122 0.3.7.beta-20 thanks

Bug#844660: marked as done (mkvtoolnix FTBFS with Qt 5.7)

Your message dated Sun, 20 Nov 2016 18:33:43 + with message-id and subject line Bug#844660: fixed in mkvtoolnix 9.5.0-2 has caused the Debian Bug report #844660, regarding mkvtoolnix FTBFS with Qt 5.7 to be marked as done. This means that you claim that

Bug#844914: rsyslog: FTBFS: Tests failures

Am 20.11.2016 um 16:17 schrieb Rainer Gerhards: > Lucas found the right root cause: It looks like the preload lib is not > loaded on that platform. See > https://github.com/rsyslog/rsyslog/issues/1268 I'm not sure. I can't reproduce the issue with a standard Debian /etc/hosts which contains

Bug#842205: [Python-modules-team] Bug#842205: musicbrainzngs: FTBFS: UsageError: authorization required; use auth(user, pass) first

I had a look at this and it seems like it may be related to the order in which the test cases run. I can reproduce it sometimes with the test setup from the packaging scripts, but not using the ones that we bundle with the package (`python setup.py test`). I've reported it upstream and will

Bug#844914: rsyslog: FTBFS: Tests failures

2016-11-20 17:45 GMT+01:00 Michael Biebl : > Am 20.11.2016 um 16:17 schrieb Rainer Gerhards: >> Lucas found the right root cause: It looks like the preload lib is not >> loaded on that platform. See >> https://github.com/rsyslog/rsyslog/issues/1268 > > I'm not sure. I can't

Bug#828577: The patch is upstream

On Thu, Nov 17, 2016 at 07:47:56PM -0500, Hon Ching(Vicky) Lo wrote: > On Thu, 2016-11-17 at 16:29 -0500, Hon Ching(Vicky) Lo wrote: > > Hi > > > > The patch is upstream: > > https://sourceforge.net/p/trousers/tpm-tools/ci/6fb8a3c5ad3bc6e62f6895a4fcf3540faa29b4f2/ > > > > > > Thanks, > > Vicky

Processed: Re: jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26] cannot find symbol

Processing commands for cont...@bugs.debian.org: > tags 844841 confirmed Bug #844841 [src:jruby-maven-plugins] jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26] cannot find symbol Added tag(s) confirmed. > thanks

Bug#844841: jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26] cannot find symbol

tags 844841 confirmed thanks It looks like this package is broken since several months ago because the FTBFS is due to missing classes in snakeyaml 1.17 that was uploaded in April 2016. This package has never been in a stable release and is only needed to package jruby 9k. I could upload a new

Bug#844953: marked as done (mongo-cxx-driver-legacy: FTBFS: Tests failures)

Your message dated Sun, 20 Nov 2016 18:48:38 + with message-id and subject line Bug#844953: fixed in mongo-cxx-driver-legacy 1.1.2-3 has caused the Debian Bug report #844953, regarding mongo-cxx-driver-legacy: FTBFS: Tests failures to be marked as done.

Bug#828329: [Pkg-gridengine-devel] Bug#828329: forwarded to https://arc.liv.ac.uk/trac/SGE/ticket/1572

Hi, Mark, على الأحد 20 تشرين الثاني 2016 ‫08:12، كتب Mark Hymers: > I've attached a patch in the upstream tracker to compile against OpenSSL > 1.1. The alternative would be to Build-Depend on openssl 1.0 for now > (which looks like it will be allowable for jessie) as gridengine doesn't > seem to

Bug#844638: marked as done (lua-sec needs Breaks: prosody (<< 0.9.11~))

Your message dated Sun, 20 Nov 2016 22:03:09 +0200 with message-id <20161120200309.hkszvaaxj5yrk...@bunk.spdns.de> and subject line This was fixed in lua-sec 0.6-2 has caused the Debian Bug report #844638, regarding lua-sec needs Breaks: prosody (<< 0.9.11~) to be marked as done. This means that

Bug#845146: pike8.0: build-depends on heimdal-dev, which is to be removed from testing

Source: pike8.0 Version: 8.0.276-1 Severity: serious Control: block 837728 with -1 Hi, Your package build-depends on heimdal-dev, but heimdal is going to be removed from testing (and possibly from the archive). See bugs #837728 and #834654 for the reasoning. You should stop build-depending on

Processed: Re: Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

Processing commands for cont...@bugs.debian.org: > severity 836597 important Bug #836597 [src:lightspark] lightspark: FTBFS on powerpc: segmentation fault during configure Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: pike8.0: build-depends on heimdal-dev, which is to be removed from testing

Processing control commands: > block 837728 with -1 Bug #837728 [release.debian.org] RM: heimdal/1.7~git20150920+dfsg-4 837728 was blocked by: 837628 806264 837716 836885 837724 837728 was not blocking any bugs. Added blocking bug(s) of 837728: 845146 -- 837728:

Bug#843898: Something to try

On Sun, 20 Nov 2016 19:17:49 +, Tobias Hansen wrote: > If you google this you see that tons of people have similar issues: > https://github.com/ipython/ipython/issues/9656 > https://github.com/ipython/ipython/issues/9815 >

Bug#845151: nomad FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: nomad Version: 0.4.0+dfsg-1 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 nomad build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Processed: nomad FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845151 [src:nomad] nomad FTBFS in stretch due to missing golang-github-docker-docker-dev 845151 was not blocked by any bugs. 845151 was not blocking any bugs. Added blocking bug(s) of 845151: 842806, 835686, 843530, and

Bug#844835: orthanc: FTBFS: build-dependency not installable: libssl-dev

Dear Gert, orthnac build depends on libdcmtk-dev, and this pulls in libssl1.0-dev (since dcmtk (a) does not yet support openssl-1.1 and (b) it is used by programs that require QT which conflicts with openssl-1.1). libssl1.0-dev conflicts with libssl-dev, and hence the build failure. The

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote: > So far I do not know why using libssl1.1 together with a > libssl1.0.2-using Qt wouldn't work. Well I don't know enough about the dynamic linker and about the internals of openssl to know if (indirectly) linking to both libraries

Bug#844393: blhc: diff for NMU version 0.07-0.2

Control: tags 844393 + patch Control: tags 844393 + pending Dear maintainer, I've prepared an NMU for blhc (versioned as 0.07-0.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, Eriberto diff -Nru blhc-0.07/debian/changelog

Processed: blhc: diff for NMU version 0.07-0.2

Processing control commands: > tags 844393 + patch Bug #844393 [blhc] blhc still uses dpkg architecture triplets Added tag(s) patch. > tags 844393 + pending Bug #844393 [blhc] blhc still uses dpkg architecture triplets Added tag(s) pending. -- 844393:

Bug#844874: opensurgsim: googletest related build failure

Control: retitle -1 opensurgsim: googletest related build failure The actual error is: ... -- Found GoogleMock: /usr/src/gmock CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the

Processed: opensurgsim: googletest related build failure

Processing control commands: > retitle -1 opensurgsim: googletest related build failure Bug #844874 [src:opensurgsim] opensurgsim: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' Changed Bug title to 'opensurgsim: googletest

Bug#844859: nfstrace: googletest related build failure

Control: retitle -1 nfstrace: googletest related build failure The actual error is: ... CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the same name already exists. The

Processed: cppformat: googletest related build failure

Processing control commands: > retitle -1 cppformat: googletest related build failure Bug #844843 [src:cppformat] cppformat: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' Changed Bug title to 'cppformat: googletest related build

Processed: nfstrace: googletest related build failure

Processing control commands: > retitle -1 nfstrace: googletest related build failure Bug #844859 [src:nfstrace] nfstrace: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create' Changed Bug title to 'nfstrace: googletest related build

Bug#844843: cppformat: googletest related build failure

Control: retitle -1 cppformat: googletest related build failure The actual error is: ... CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the same name already exists. The

Bug#841606: marked as done (dleyna-server: FTBFS: upnp.h:119:1: error: unknown type name 'GUPnPContextManager')

Your message dated Sun, 20 Nov 2016 22:18:59 + with message-id and subject line Bug#841606: fixed in dleyna-server 0.4.0-1.1 has caused the Debian Bug report #841606, regarding dleyna-server: FTBFS: upnp.h:119:1: error: unknown type name

Bug#844914: rsyslog: FTBFS: Tests failures

Am 20.11.2016 um 17:55 schrieb Rainer Gerhards: > 2016-11-20 17:45 GMT+01:00 Michael Biebl : >> Am 20.11.2016 um 16:17 schrieb Rainer Gerhards: >>> Lucas found the right root cause: It looks like the preload lib is not >>> loaded on that platform. See >>>

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote: > If SONAME change is needed it is needed when linking libcurl with > libssl1.0.2 too. (But when linking libcurl with libssl1.0.2 more > applications are affected due to the need of explicit initialization.) Upstream documentation

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote: > > Still, for 1.1 the SONAME change is definitely necessary. > > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and > compiled with OpenSSL 1.0 will probably suffice in that case. Wouldn't this still be a serious bug

Processed: forcibly merging 844817 845033

Processing commands for cont...@bugs.debian.org: > forcemerge 844817 845033 Bug #844817 [apache2-dev] cgit: FTBFS: build-dependency not installable: libssl-dev Bug #845033 [apache2-dev] apache2-dev: please provide separate package dh-apache2 Severity set to 'serious' from 'normal' Removed

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 20:48:44 +0100 Jan Niehusmann написал: > On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote: > > > Still, for 1.1 the SONAME change is definitely necessary. > > > > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and > > compiled with OpenSSL 1.0 will

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

20.11.2016 в 23:38:48 +0400 Stepan Golosunov написал: > 20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал: > > Still, for 1.1 the SONAME change is definitely necessary. > > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and > compiled with OpenSSL 1.0 will probably suffice in that

Bug#845148: consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev

Source: consul Version: 0.6.4~dfsg-3 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 consul build-depends on golang-github-fsouza-go-dockerclient-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Processed: consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845148 [src:consul] consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev 845148 was not blocked by any bugs. 845148 was not blocking any bugs. Added blocking bug(s) of 845148: 843530, 835686,

Processed: containerd FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845149 [src:containerd] containerd FTBFS in stretch due to missing golang-github-docker-docker-dev 845149 was not blocked by any bugs. 845149 was not blocking any bugs. Added blocking bug(s) of 845149: 843530, 835686,

Bug#845149: containerd FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: containerd Version: 0.2.1~ds1-3 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 containerd build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Bug#845150: gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev

Source: gitlab-ci-multi-runner Version: 1.7.1+dfsg-2 Severity: serious Tags: stretch Control: block -1 by 832103 835686 842806 843530 gitlab-ci-multi-runner build-depends on golang-github-docker-docker-dev, which is not in stretch due to #832103, #835686, #842806, #843530

Processed: gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev

Processing control commands: > block -1 by 832103 835686 842806 843530 Bug #845150 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev 845150 was not blocked by any bugs. 845150 was not blocking any bugs. Added blocking bug(s) of

Processed: bug 842205 is forwarded to https://github.com/alastair/python-musicbrainzngs/issues/211

Processing commands for cont...@bugs.debian.org: > forwarded 842205 https://github.com/alastair/python-musicbrainzngs/issues/211 Bug #842205 [src:musicbrainzngs] musicbrainzngs: FTBFS: UsageError: authorization required; use auth(user, pass) first Set Bug forwarded-to-address to

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

at bottom :- On 21/11/2016, shirish शिरीष wrote: > at bottom :- > Trying with the new versions got this (again) - > > [$] sudo aptitude reinstall cme libconfig-model-perl > libconfig-model-dpkg-perl fonts-arphic-uming > [1:46:39] > The following packages will be

Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

Control: tags -1 important On 20/11/16 13:58, Andrey Rahmatullin wrote: > Control: tags -1 + unreproducible > > On Sun, Sep 04, 2016 at 01:56:41PM +0200, Emilio Pozuelo Monfort wrote: >> Source: lightspark >> Version: 0.7.2+git20150512-2.1 >> Severity: serious >> >> Your package fails to build

Bug#844814: marked as done (swauth: FTBFS: build-dependency not installable: swift-proxy (>= 2.2.0))

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding swauth: FTBFS: build-dependency not installable: swift-proxy (>= 2.2.0) to be marked

Bug#844808: marked as done (nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev to be marked as

Bug#844840: marked as done (python-autobahn: FTBFS: unsatisfiable build-dependencies: python-nacl, python3-nacl)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding python-autobahn: FTBFS: unsatisfiable build-dependencies: python-nacl, python3-nacl

Bug#844714: marked as done (pycparser needs sourceful upload for new python-ply)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding pycparser needs sourceful upload for new python-ply to be marked as done. This means

Bug#844823: marked as done (swift-plugin-s3: FTBFS: build-dependency not installable: python-swift)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding swift-plugin-s3: FTBFS: build-dependency not installable: python-swift to be marked as

Bug#844811: marked as done (therion: FTBFS: build-dependency not installable: libvtk6-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding therion: FTBFS: build-dependency not installable: libvtk6-dev to be marked as done.

Bug#844832: marked as done (yade: FTBFS: build-dependency not installable: libvtk6-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding yade: FTBFS: build-dependency not installable: libvtk6-dev to be marked as done. This

Bug#844794: marked as done (zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1))

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1) to be

Bug#844791: marked as done (openmeeg: FTBFS: build-dependency not installable: libvtk6-dev)

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding openmeeg: FTBFS: build-dependency not installable: libvtk6-dev to be marked as done.

Bug#844827: marked as done (swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4))

Your message dated Sun, 20 Nov 2016 21:18:48 + with message-id and subject line Bug#844714: fixed in pycparser 2.17-2 has caused the Debian Bug report #844714, regarding swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4) to be marked as

  1   2   3   >