Processed (with 1 error): severity is serious

Processing commands for cont...@bugs.debian.org: > # this bug makes it impossible to use metapixel at all, so raising severity > to RC > severity 824229 grave Bug #824229 [metapixel] metapixel-prepare fails - metapixel: rwpng.c:199: open_png_file_writing: Assertion `0' failed. Severity set to

Bug#847542: libmozjs-24-0 24.2.0-4 breaks gnome-shell, preventing gdm3 from starting

same here; downgraded to testing version and everything works again

Bug#846228: Random FTBFS failures of joblib and what about team maintenance

On Sat, Dec 10, 2016 at 12:09:55AM +0100, Bernd Zeimetz wrote: > > I think python-joblib has several rdepends and thus it would IMHO be > > better maintained in DPMT than in a private Github repository. What > > do you think? > > On the other side, DPMT is nothing to drop packages one does not

Bug#847321: Could you please check the autobuilder for opensurgsim

Hi, On 2016-12-09 09:29, Andreas Tille wrote: > Hi Mips porters, > > I noticed that opensurgsim has not yet build on mips[1]. Since the > build process for this package needs some more powerful machine and I > learned in the past that there are different machines for mips available > I wonder

Processed: Fix for the jabberd2 FTBFS bugs

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

Bug#828360: Fix for the jabberd2 FTBFS bugs

Control: tags -1 patch Not a perfect solution but sufficient for stretch is the patch below to use OpenSSL 1.0.2 The "| libssl-dev (<< 1.1.0~)" is added for backports. --- debian/control.old 2016-12-10 06:48:51.0 + +++ debian/control 2016-12-10 06:49:02.0 + @@

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

On Sat, Dec 10, 2016 at 08:31:14AM +0200, Adrian Bunk wrote: >... > Sufficient for stretch (which might be the last Debian release with > sslscan) >... Please ignore the "which might be the last Debian release with sslscan", this is a paste error. cu Adrian -- "Is there not promise of

Processed: Fix for the jabberd2 FTBFS bugs

Processing control commands: > tags -1 patch Bug #845857 [jabberd2] jabberd2: switch to build depend on the metapackage default-libmysqlclient-dev Added tag(s) patch. -- 845857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845857 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: Building with OpenSSL 1.0.2 is sufficient for stretch

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

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

Control: tags -1 patch Sufficient for stretch (which might be the last Debian release with sslscan) is the patch below to use OpenSSL 1.0.2 The "| libssl-dev (<< 1.1.0~)" is added for backports. --- debian/control.old 2016-12-10 06:29:33.0 + +++ debian/control 2016-12-10

Bug#847641: obnam: FTBFS on all archs due to test failure

Source: obnam Version: 1.20.2-1 Justification: fails to build from source (but built successfully in the past) Severity: serious I checked the BTS but it doesn't look like this has been reported before; sorry if this is a duplicate report. obnam currently FTBFS on all archs in sid (for about a

Processed: severity of 845258 is grave

Processing commands for cont...@bugs.debian.org: > # should be fixed before the stretch release, marked as no-dsa though for > jessie, can be fixed via point release > severity 845258 grave Bug #845258 [src:mcabber] mcabber: remote attacker can modify the roster and intercept messages via a

Bug#846007: marked as done (node-grunt-contrib-concat: Incomplete debian/copyright)

Your message dated Sat, 10 Dec 2016 06:03:30 + with message-id and subject line Bug#846007: fixed in node-grunt-contrib-concat 1.0.1-2 has caused the Debian Bug report #846007, regarding node-grunt-contrib-concat: Incomplete debian/copyright to be marked

Bug#794438: Partition manager does not launch

Package: partitionmanager Version: 1.0.3-2.1 Followup-For: Bug #794438 Dear Maintainer, I am also see that partionmanager is failing to launch. * What led up to the situation? I upgraded from stretch to sid and then installed partitionmanager. * What exactly did you do (or not do) that

Bug#845106: x11vnc: configure does not find libssl, builds without OpenSSL support

On 2016-12-01, Fathi Boudra wrote: > On Thu, Dec 1, 2016 at 11:50 AM, Danny Edel wrote: >> On Sun, 20 Nov 2016 13:37:46 +0100 Hilko Bengen wrote: >>> after searching for "AC_CHECK_LIB(ssl, SSL_library_init" using >>> codesearch.debian.net and rebuilding

Bug#846010: marked as done (node-cpr: Incomplete debian/copyright)

Your message dated Sat, 10 Dec 2016 05:33:30 + with message-id and subject line Bug#846010: fixed in node-cpr 2.0.0-2 has caused the Debian Bug report #846010, regarding node-cpr: Incomplete debian/copyright to be marked as done. This means that you claim

Bug#847133: marked as done (pion FTBFS on arm64: piontests fails)

Your message dated Sat, 10 Dec 2016 05:18:43 + with message-id and subject line Bug#847133: fixed in pion 5.0.7+dfsg-3 has caused the Debian Bug report #847133, regarding pion FTBFS on arm64: piontests fails to be marked as done. This means that you claim

Bug#847634: There is a LIBDIR variable you can use

Just found https://github.com/phhusson/quassel-irssi/commit/ cfbd67f8576e2f5e30ec769866e68326a3466adf from 2016-04-12 which explicitly allows setting the LIBDIR variable for downstream maintainers, so that looks like a way to solve this bug :) signature.asc Description: This is a digitally

Bug#847634: irssi-plugin-quassel: libquassel_core.so not in expected location

Package: irssi-plugin-quassel Version: 0~git20160612-1 Severity: grave Justification: renders package unusable I followed the instructions from the README.md on github, but when I got to the '/load quassel' part I got the following error: Irssi: Error loading module quassel/core:

Processed: found 845912 in 3.0.2-4, tagging 845912, found 845910 in 3.0.2-1, found 845905 in 0.10.16-1 ...

Processing commands for cont...@bugs.debian.org: > found 845912 3.0.2-4 Bug #845912 {Done: Michal Čihař } [stardict-tools] stardict-tools: switch to build depend on the metapackage default-libmysqlclient-dev Marked as found in versions stardict-tools/3.0.2-4. > tags 845912 +

Bug#843464: jmol: diff for NMU version 12.2.32+dfsg2-1.1

On Sun, 4 Dec 2016 11:32:43 -0800 tony mancill wrote: > Control: tags 843464 + patch > Control: tags 843464 + pending > > Dear maintainer, > > I've prepared an NMU for jmol (versioned as 12.2.32+dfsg2-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should

Bug#842702: marked as done (zabbix: CVE-2016-9140: API JSON-RPC remote code execution)

Your message dated Sat, 10 Dec 2016 03:05:15 + with message-id and subject line Bug#842702: fixed in zabbix 1:3.0.6+dfsg-1 has caused the Debian Bug report #842702, regarding zabbix: CVE-2016-9140: API JSON-RPC remote code execution to be marked as done.

Bug#845917: marked as done (zoneminder: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Sat, 10 Dec 2016 03:05:33 + with message-id and subject line Bug#845917: fixed in zoneminder 1.30.0+dfsg-2 has caused the Debian Bug report #845917, regarding zoneminder: switch to build depend on the metapackage

Processed: Re: Bug#775744: libapp-stacktrace-perl: FTBFS: Failed 1/4 test programs. 1/6 subtests failed.

Processing control commands: > tag -1 - pending Bug #775744 [src:libapp-stacktrace-perl] libapp-stacktrace-perl: FTBFS on many arches Removed tag(s) pending. -- 775744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775744 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#775744: libapp-stacktrace-perl: FTBFS: Failed 1/4 test programs. 1/6 subtests failed.

Control: tag -1 - pending Hi again, Axel Beckert wrote: > Axel Beckert wrote: > > Niko Tyni wrote: > > > The attached patch makes the test suite pass again for me on amd64. > > > > Thanks. The patch works fine for me, too, at least on amd64 and armhf. > > But it now FTBFS on arm64 (where it

Bug#775744: libapp-stacktrace-perl: FTBFS: Failed 1/4 test programs. 1/6 subtests failed.

Hi, Axel Beckert wrote: > Niko Tyni wrote: > > The attached patch makes the test suite pass again for me on amd64. > > Thanks. The patch works fine for me, too, at least on amd64 and armhf. > But it now FTBFS on arm64 (where it built before): > > […] > t/release-pod-syntax.t skipped: these

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

On Sat, Dec 10, 2016 at 02:25:08AM +0100, Mattia Rizzolo wrote: > On Fri, Dec 09, 2016 at 08:11:54PM -0500, Bill Blough wrote: > > > >Or does anyone have other suggestions? > > I have one: please try to CC people (and/or MLs) sooner. I now noticed > that you asked for help more than one month

Processed: Bug#845917 tagged as pending

Processing commands for cont...@bugs.debian.org: > tag 845917 pending Bug #845917 [zoneminder] zoneminder: switch to build depend on the metapackage default-libmysqlclient-dev Added tag(s) pending. > -- Stopping processing here. Please contact me if you need assistance. -- 845917:

Bug#845917: tagged as pending

tag 845917 pending -- We believe that the bug #845917 you reported has been fixed in the Git repository. You can see the commit message below and/or inspect the commit contents at: http://anonscm.debian.org/cgit/collab-maint/zoneminder.git/diff/?id=87761aa (This message was generated

Bug#775744: libapp-stacktrace-perl: FTBFS: Failed 1/4 test programs. 1/6 subtests failed.

Control: tag -1 + pending Hi Niko, Niko Tyni wrote: > The attached patch makes the test suite pass again for me on amd64. Thanks. The patch works fine for me, too, at least on amd64 and armhf. But it now FTBFS on arm64 (where it built before): […] t/release-pod-syntax.t skipped: these

Processed: Re: Bug#775744: libapp-stacktrace-perl: FTBFS: Failed 1/4 test programs. 1/6 subtests failed.

Processing control commands: > tag -1 + pending Bug #775744 [src:libapp-stacktrace-perl] libapp-stacktrace-perl: FTBFS on many arches Added tag(s) pending. -- 775744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#847629: git-build-recipe: FTBFS in sid: tests fail, lintian is missing

Package: git-build-recipe Version: 0.3.4 Severity: serious Justification: fails to build from source Hi, git-build-recipe didn't build on the autobuilder: https://buildd.debian.org/status/fetch.php?pkg=git-build-recipe=all=0.3.4=1480435477 [...] debian/rules override_dh_auto_test make[1]:

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

On Fri, Dec 09, 2016 at 08:11:54PM -0500, Bill Blough wrote: > > >Or does anyone have other suggestions? I have one: please try to CC people (and/or MLs) sooner. I now noticed that you asked for help more than one month ago, but I wasn't aware of that at all. And now the freeze is hovering upon

Bug#846898: Fixed in 3.22.2-2

Am 10.12.2016 um 01:23 schrieb David Weinehall: > On Fri, 9 Dec 2016 09:24:15 +0200 David Weinehall > > wrote: >> On Tue, 6 Dec 2016 18:01:02 +0100 Raphael Hertzog > >> wrote: >> >

Bug#825402: marked as done (minlog: switch Depends from plt-scheme to racket)

Your message dated Sat, 10 Dec 2016 01:18:17 + with message-id and subject line Bug#825402: fixed in minlog 4.0.99.20100221-6 has caused the Debian Bug report #825402, regarding minlog: switch Depends from plt-scheme to racket to be marked as done. This

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

On Fri, Dec 09, 2016 at 11:07:54PM +, Gianfranco Costamagna wrote: > >Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I > >understand it correctly, it shouldn't have any effect on this, but I > >have no way to test it other than another upload. > > > I still prefer the

Bug#844882: ocserv: FTBFS: ./ocserv-args.h:1:1: error: unterminated comment

On Sat, Nov 19, 2016 at 07:47:50 +0100, Lucas Nussbaum wrote: > > In file included from sup-config/file.c:29:0: > > ./ocserv-args.h:1:1: error: unterminated comment > > /* -*- buffer-read-only: t -*- vi: set ro: > > ^ I can semi-reliably reproduce this and similar errors with sbuild -j32. It

Bug#846898: Fixed in 3.22.2-2

On Fri, 9 Dec 2016 09:24:15 +0200 David Weinehall wrote: > On Tue, 6 Dec 2016 18:01:02 +0100 Raphael Hertzog > wrote: > > Version: 3.22.2-2 > > > > I just uploaded a new version of mutter with the fix for that > > bug. I was not aware of this bug so

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

Hi Bill, >I'd really like to get this resolved before the freeze. > >Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I >understand it correctly, it shouldn't have any effect on this, but I >have no way to test it other than another upload. I still prefer the default -Ofoo

Bug#846228: Random FTBFS failures of joblib and what about team maintenance

On 12/07/2016 12:09 PM, Andreas Tille wrote: > Hi Yaroslav, > > I just want to make some noise amongst Python experts about bug #846228. > I admit I have no idea - but since there was no response for 10 days now > several packages git a testing removal notice. > > I think python-joblib has

Bug#843470: marked as done (mergechanges: doesn't know about new .buildinfo files)

Your message dated Fri, 09 Dec 2016 22:48:23 + with message-id and subject line Bug#843470: fixed in devscripts 2.16.12 has caused the Debian Bug report #843470, regarding mergechanges: doesn't know about new .buildinfo files to be marked as done. This

Bug#846711: marked as done (debuild: no longer checks whether lintian exists before implicitly running it)

Your message dated Fri, 09 Dec 2016 22:48:23 + with message-id and subject line Bug#846711: fixed in devscripts 2.16.12 has caused the Debian Bug report #846711, regarding debuild: no longer checks whether lintian exists before implicitly running it to be

Processed: Re: Bug#846410: kdevelop crahses when starting (5.0.1)

Processing commands for cont...@bugs.debian.org: > tag 846410 unreproducible moreinfo Bug #846410 [kdevelop] kdevelop crahses when starting (5.0.1) Added tag(s) moreinfo and unreproducible. > severity 846410 important Bug #846410 [kdevelop] kdevelop crahses when starting (5.0.1) Severity set to

Bug#846410: kdevelop crahses when starting (5.0.1)

tag 846410 unreproducible moreinfo severity 846410 important thanks Hi! I've tried to reproduce this bug in an up-to-date sid environment without luck. Please try again with an up to date system. If it still crashed please try with a clean environment (a new user). In case you can not

Bug#847542: libmozjs-24-0 24.2.0-4 breaks gnome-shell, preventing gdm3 from starting

I suffered this same bug and also downgrading to 24.2.0-3.1, from testing, worked fine. -- Nos leemos RASTER(Linux user #228804) ras...@rastersoft.com http://www.rastersoft.com

Processed: Re: Bug#846836: ruby-json-pure: Incomplete debian/copyright? (fwd)

Processing commands for cont...@bugs.debian.org: > close #846836 2.0.2+dfsg-2 Bug #846836 [src:ruby-json-pure] ruby-json-pure: Incomplete debian/copyright? Marked as fixed in versions ruby-json-pure/2.0.2+dfsg-2. Bug #846836 [src:ruby-json-pure] ruby-json-pure: Incomplete debian/copyright? Marked

Bug#847583: marked as done (titanion: FTBFS: usr/bin/ld: /tmp/ccx5V2eP.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile with -fPIC)

Your message dated Fri, 9 Dec 2016 22:42:11 +0100 with message-id <6d33e3c7-a20e-7a8e-0375-10f7f1dd7...@debian.org> and subject line Re: Bug#847615: a7xpg: FTBFS: /usr/bin/ld: /tmp/ccJGfpQx.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile

Bug#847582: marked as done (gunroar: FTBFS: /usr/bin/ld: /tmp/ccuUL66s.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile with -fPIC)

Your message dated Fri, 9 Dec 2016 22:42:11 +0100 with message-id <6d33e3c7-a20e-7a8e-0375-10f7f1dd7...@debian.org> and subject line Re: Bug#847615: a7xpg: FTBFS: /usr/bin/ld: /tmp/ccJGfpQx.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile

Bug#847615: marked as done (a7xpg: FTBFS: /usr/bin/ld: /tmp/ccJGfpQx.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile with -fPIC)

Your message dated Fri, 9 Dec 2016 22:42:11 +0100 with message-id <6d33e3c7-a20e-7a8e-0375-10f7f1dd7...@debian.org> and subject line Re: Bug#847615: a7xpg: FTBFS: /usr/bin/ld: /tmp/ccJGfpQx.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile

Processed: Re: Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

Processing control commands: > forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/320 Bug #846385 [imagemagick] imagemagick: Potential ABI break upstream (without SONAME change) Set Bug forwarded-to-address to 'https://github.com/ImageMagick/ImageMagick/issues/320'. -- 846385:

Processed: Re: gcr: FTBFS: FAIL: test-gnupg-collection 3 /gcr/gnupg-collection/reload

Processing commands for cont...@bugs.debian.org: > retitle 846728 gcr: FTBFS: FAIL: test-gnupg-collection 3 > /gcr/gnupg-collection/reload Bug #846728 [src:gcr] gcr: FTBFS: Test failures Changed Bug title to 'gcr: FTBFS: FAIL: test-gnupg-collection 3 /gcr/gnupg-collection/reload' from 'gcr:

Bug#846385: imagemagick: Potential ABI break upstream (without SONAME change)

control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/320 Dear realease team, What is the next step? Thank you On Tue, Dec 6, 2016 at 8:23 PM, Simon McVittie wrote: > Control: reopen 846385 > Control: severity 846385 serious > > tl;dr: yes, this is clearly

Processed: Re: cf-python: FTBFS: AttributeError: 'module' object has no attribute 'netcdftime'

Processing commands for cont...@bugs.debian.org: > retitle 846730 cf-python: FTBFS: AttributeError: 'module' object has no > attribute 'netcdftime' Bug #846730 [src:cf-python] cf-python: FTBFS: XXX Changed Bug title to 'cf-python: FTBFS: AttributeError: 'module' object has no attribute

Processed: Re: cinder: FTBFS: testtools.matchers._impl.MismatchError: None != 1

Processing commands for cont...@bugs.debian.org: > retitle 846749 cinder: FTBFS: testtools.matchers._impl.MismatchError: None != > 1 Bug #846749 [src:cinder] cinder: FTBFS: Test failures Changed Bug title to 'cinder: FTBFS: testtools.matchers._impl.MismatchError: None != 1' from 'cinder: FTBFS:

Processed: Re: python-bleach: FTBFS: ImportError: No module named sanitizer

Processing commands for cont...@bugs.debian.org: > retitle 844943 python-bleach: FTBFS: ImportError: No module named sanitizer Bug #844943 [src:python-bleach] python-bleach: FTBFS: Tests failures Changed Bug title to 'python-bleach: FTBFS: ImportError: No module named sanitizer' from

Bug#847542: libmozjs-24-0 24.2.0-4 breaks gnome-shell, preventing gdm3 from starting

Hi László, I have run into the same issue today and also can confirm that downgrading to 24.2.0-3.1 fixed it for me too. Bests, Csaba Dec  9 21:25:50 csaba-pc gnome-shell[641]: JS ERROR: TypeError: imports.ui is undefined Dec  9 21:25:50 csaba-pc gnome-shell[641]: Execution of main.js threw

Bug#847615: a7xpg: FTBFS: /usr/bin/ld: /tmp/ccJGfpQx.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile with -fPIC

Source: a7xpg Version: 0.11.dfsg1-9 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, a7xpg fails to build from source in unstable/amd64: […]

Bug#845749: marked as done (libwebp FTBFS on armhf: inlining failed in call to always_inline 'vtrnq_s32': target specific option mismatch)

Your message dated Fri, 09 Dec 2016 21:20:49 + with message-id and subject line Bug#845749: fixed in libwebp 0.5.1-4 has caused the Debian Bug report #845749, regarding libwebp FTBFS on armhf: inlining failed in call to always_inline 'vtrnq_s32': target

Bug#831946: marked as done (python-pcs: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

Your message dated Fri, 09 Dec 2016 21:21:16 + with message-id and subject line Bug#831946: fixed in python-pcs 0.5+debian-2 has caused the Debian Bug report #831946, regarding python-pcs: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary

Processed: node-yargs FTBFS in stretch due to missing node-cpr

Processing control commands: > block -1 by 846010 Bug #847614 [src:node-yargs] node-yargs FTBFS in stretch due to missing node-cpr 847614 was not blocked by any bugs. 847614 was not blocking any bugs. Added blocking bug(s) of 847614: 846010 -- 847614:

Bug#847614: node-yargs FTBFS in stretch due to missing node-cpr

Source: node-yargs Version: 6.4.0-2 Severity: serious Tags: stretch sid Control: block -1 by 846010 node-yargs build-depends on node-cpr, which is not in stretch due to #846010

Bug#846532: marked as done (mod-gnutls FTBFS in stretch due to missing monkeysphere)

Your message dated Fri, 9 Dec 2016 23:15:12 +0200 with message-id <20161209211511.dahsghdkicq5v...@bunk.spdns.de> and subject line monkeysphere is back in testing has caused the Debian Bug report #846532, regarding mod-gnutls FTBFS in stretch due to missing monkeysphere to be marked as done. This

Bug#847612: monitoring-plugins-basic lost OpenSSL support

Package: monitoring-plugins-basic Version: 2.2-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=monitoring-plugins=amd64=2.2-1=1481212864 ... checking openssl/ssl.h usability... no checking openssl/ssl.h presence... no checking for openssl/ssl.h... no checking openssl/x509.h

Bug#835800: transmission: FTBFS with openssl 1.1.0

On 2016-09-05 23:27:57 [+0100], Sandro Tosi wrote: > On Mon, Sep 5, 2016 at 10:59 PM, Sebastian Andrzej Siewior > wrote: > > control: tags -1 patch > > thanks for the patch, against which version is this based on? 2.92 > reached unstable after this bug was filed This

Processed (with 5 errors): Re: Processed: reopen,

Processing commands for cont...@bugs.debian.org: > clone 828266 -1 Bug #828266 [src:ckermit] ckermit: FTBFS with openssl 1.1.0 Bug 828266 cloned as bug 847611 > severity 828266 serious Bug #828266 [src:ckermit] ckermit: FTBFS with openssl 1.1.0 Severity set to 'serious' from 'important' > close

Processed: reopen,

Processing commands for cont...@bugs.debian.org: > # it still fails to build with openssl 1.1 > reopen 828266 Bug #828266 {Done: Andrey Rahmatullin } [src:ckermit] ckermit: FTBFS with openssl 1.1.0 'reopen' may be inappropriate when a bug has been closed with a version; all

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

I'd really like to get this resolved before the freeze. Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I understand it correctly, it shouldn't have any effect on this, but I have no way to test it other than another upload. Assuming that's not it, would someone be willing

Processed: Re: Bug#847585: gnome-shell: Gnome-shell fails to launch

Processing control commands: > reassign -1 libmozjs-24-0 Bug #847585 [gnome-shell] gnome-shell: Gnome-shell fails to launch Bug reassigned from package 'gnome-shell' to 'libmozjs-24-0'. No longer marked as found in versions gnome-shell/3.22.2-1. Ignoring request to alter fixed versions of bug

Bug#847585: gnome-shell: Gnome-shell fails to launch

Control: reassign -1 libmozjs-24-0 Control: forcemerge 847542 -1 Am 09.12.2016 um 17:30 schrieb Sergio Costas: > Package: gnome-shell > Version: 3.22.2-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > I updated some minutes ago my Debian SID system, and

Bug#822001: marked as done (libcorelinux: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Fri, 09 Dec 2016 18:37:02 + with message-id and subject line Bug#822001: fixed in libcorelinux 0.4.32-8 has caused the Debian Bug report #822001, regarding libcorelinux: Build arch:all+arch:any but is missing build-{arch,indep} targets

Bug#800232: marked as done (libcorelinux: Please migrate a supported debhelper compat level)

Your message dated Fri, 09 Dec 2016 18:37:02 + with message-id and subject line Bug#800232: fixed in libcorelinux 0.4.32-8 has caused the Debian Bug report #800232, regarding libcorelinux: Please migrate a supported debhelper compat level to be marked as

Bug#812053: marked as done (galib: FTBFS with GCC 6)

Your message dated Fri, 09 Dec 2016 18:04:58 + with message-id and subject line Bug#812053: fixed in galib 1:2.4.7-4 has caused the Debian Bug report #812053, regarding galib: FTBFS with GCC 6 to be marked as done. This means that you claim that the

Bug#843142: marked as done (src:galib needs epoch to regain ownership of libga-dev)

Your message dated Fri, 09 Dec 2016 18:04:58 + with message-id and subject line Bug#843142: fixed in galib 1:2.4.7-4 has caused the Debian Bug report #843142, regarding src:galib needs epoch to regain ownership of libga-dev to be marked as done. This

Bug#845823: marked as done (apr-util: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Fri, 09 Dec 2016 17:48:39 + with message-id and subject line Bug#845823: fixed in apr-util 1.5.4-3 has caused the Debian Bug report #845823, regarding apr-util: switch to build depend on the metapackage default-libmysqlclient-dev to be

Bug#847594: marked as done (ACCOUNT_KEY_JSON: unbound variable)

Your message dated Fri, 9 Dec 2016 18:41:28 +0100 with message-id <20161209174127.ga21...@mapreri.org> and subject line Re: [Letsencrypt-devel] Bug#847594: ACCOUNT_KEY_JSON: unbound variable has caused the Debian Bug report #847594, regarding ACCOUNT_KEY_JSON: unbound variable to be marked as

Processed: Re: [Letsencrypt-devel] Bug#847594: ACCOUNT_KEY_JSON: unbound variable

Processing commands for cont...@bugs.debian.org: > notfound 847594 0.3.0-1~bpo8+1 Bug #847594 [letsencrypt.sh] ACCOUNT_KEY_JSON: unbound variable No longer marked as found in versions letsencrypt.sh/0.3.0-1~bpo8+1. > found 847594 0.3.0-1 Bug #847594 [letsencrypt.sh] ACCOUNT_KEY_JSON: unbound

Bug#846455: marked as done (vtwm: add libfl-dev to Build-Depends)

Your message dated Fri, 09 Dec 2016 17:37:14 + with message-id and subject line Bug#846455: fixed in vtwm 5.4.7-3 has caused the Debian Bug report #846455, regarding vtwm: add libfl-dev to Build-Depends to be marked as done. This means that you claim that

Bug#847594: ACCOUNT_KEY_JSON: unbound variable

Package: letsencrypt.sh Version: 0.3.0-1~bpo8+1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I installed letsencrypt.sh version

Processed: user debian...@lists.debian.org, usertagging 838628, affects 838628

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 838628 piuparts There were no usertags set. Usertags are now: piuparts. > affects 838628 + libboost-mpi1.58-dev libboost-mpi-python1.58.0

Bug#828327: marked as done (gnubiff: FTBFS due to missing #include )

Your message dated Fri, 09 Dec 2016 17:05:22 + with message-id and subject line Bug#828327: fixed in gnubiff 2.2.16-2 has caused the Debian Bug report #828327, regarding gnubiff: FTBFS due to missing #include to be marked as done. This means that you

Bug#845913: marked as done (tarantool-lts: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Fri, 09 Dec 2016 16:35:21 + with message-id and subject line Bug#845913: fixed in tarantool-lts 1.5.5.37.g1687c02-1 has caused the Debian Bug report #845913, regarding tarantool-lts: switch to build depend on the metapackage

Bug#847355: marked as done (quagga-core: fails to install, remove, and install again)

Your message dated Fri, 09 Dec 2016 16:33:59 + with message-id and subject line Bug#847355: fixed in quagga 1.1.0-2 has caused the Debian Bug report #847355, regarding quagga-core: fails to install, remove, and install again to be marked as done. This

Bug#847585: gnome-shell: Gnome-shell fails to launch

Package: gnome-shell Version: 3.22.2-1 Severity: critical Justification: breaks the whole system Dear Maintainer, I updated some minutes ago my Debian SID system, and after rebooting, the gnome-shell session didn't start. I tried to run "gnome-shell --replace" from a terminal that I was able to

Bug#847397: marked as done (libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs)

Your message dated Fri, 09 Dec 2016 16:28:15 + with message-id and subject line Bug#847397: fixed in libimager-perl 1.005+dfsg-2 has caused the Debian Bug report #847397, regarding libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs to be

Bug#847583: titanion: FTBFS: usr/bin/ld: /tmp/ccx5V2eP.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile with -fPIC

Source: titanion Version: 0.3.dfsg1-6 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, titanion fails to build from source in unstable/amd64:

Bug#847582: gunroar: FTBFS: /usr/bin/ld: /tmp/ccuUL66s.o: relocation R_X86_64_PC32 against symbol `[..]' can not be used when making a shared object; recompile with -fPIC

Source: gunroar Version: 0.15.dfsg1-8 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, gunroar fails to build from source in unstable/amd64:

Bug#845833: marked as done (dballe: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Fri, 09 Dec 2016 16:24:54 + with message-id and subject line Bug#845833: fixed in dballe 7.21-1 has caused the Debian Bug report #845833, regarding dballe: switch to build depend on the metapackage default-libmysqlclient-dev to be

Bug#846533: marked as done (apertium-hbs FTBFS in stretch due to missing libhfst45-dev)

Your message dated Fri, 09 Dec 2016 16:22:48 + with message-id and subject line Bug#846533: fixed in apertium-hbs 0.5.0~r68212-2 has caused the Debian Bug report #846533, regarding apertium-hbs FTBFS in stretch due to missing libhfst45-dev to be marked as

Bug#845824: marked as done (argus-clients: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Fri, 09 Dec 2016 16:23:00 + with message-id and subject line Bug#845824: fixed in argus-clients 1:3.0.8.2-3 has caused the Debian Bug report #845824, regarding argus-clients: switch to build depend on the metapackage

Processed: pytest-httpbin: FTBFS (test_chunked_encoding[https] FAILED)

Processing control commands: > severity -1 normal Bug #844358 [src:pytest-httpbin] pytest-httpbin: FTBFS (test_chunked_encoding[https] FAILED) Severity set to 'normal' from 'serious' -- 844358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844358 Debian Bug Tracking System Contact

Bug#844358: pytest-httpbin: FTBFS (test_chunked_encoding[https] FAILED)

Control: severity -1 normal I've filed this about a FTBFS in reproducible builds CI on i386 in unstable. But this couldn't hardly be reproduced. The new package (0.2.3) doesn't contain a particular fix for this, but appears to build fine throughout. DEP-8 test doesn't brought up something,

Bug#847580: Embeds dietlibc (GPL) but does not have a Built-Using field

Package: util-vserver Version: 0.30.216-pre3120-1.1 Severity: serious Some binaries in util-vserver are statically linked to dietlibc which is licensed under GNU GPL. util-vserver must have a Built-Using field to record which version was used and ensure that the corresponding source package is

Bug#847579: Embeds dietlibc (GPL) but does not have a Built-Using field

Package: ngetty Version: 1.1-3 Severity: serious ngetty is statically linked to dietlibc which is licensed under GNU GPL. ngetty must have a Built-Using field to record which version was used and ensure that the corresponding source package is kept in the archive. Ben. -- System Information:

Bug#847577: Embeds dietlibc (GPL) but does not have a Built-Using field

Package: integrit Version: 4.1-1 Severity: serious integrit is statically linked to dietlibc which is licensed under GNU GPL. integrit must have a Built-Using field to record which version was used and ensure that the corresponding source package is kept in the archive. Ben. -- System

Bug#847576: Embeds dietlibc (GPL) but does not have a Built-Using field

Package: fgetty Version: 0.7-1 Severity: serious fgetty is statically linked to dietlibc which is licensed under GNU GPL. fgetty must have a Built-Using field to record which version was used and ensure that the corresponding source package is kept in the archive. Ben. -- System Information:

Bug#847575: Embeds dietlibc (GPL) but does not have a Built-Using field

Package: e2fsck-static Version: 1.43.3-1 Severity: serious e2fsck-static is statically linked to dietlibc which is licensed under GNU GPL. e2fsck-static must have a Built-Using field to record which version was used and ensure that the corresponding source package is kept in the archive. Ben.

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

On Fri, 09 Dec 2016 09:08:21 +0200, Niko Tyni wrote: > > > +# #847397 > > > +DEB_HOST_ARCH = $(shell dpkg-architecture -qDEB_HOST_ARCH) > > > +NOOPT = mips mipsel amd64 > > > +ifneq (,$(filter $(DEB_HOST_ARCH), $(NOOPT))) > > > +export DEB_CFLAGS_MAINT_STRIP:=-O2 > > > +export

Bug#828342: [Htt-developers] Building with OpenSSL 1.0.2 is sufficient for stretch

Thanks I'll have a look. Von meinem iPhone gesendet > Am 08.12.2016 um 22:28 schrieb Sebastian Andrzej Siewior > : > >> On 2016-11-10 13:53:44 [+0200], Adrian Bunk wrote: >> Control: tags -1 patch >> >> Not a perfect solution but sufficient for stretch is the

Bug#846648: [Pkg-chromium-maint] Bug#846648: another data point

On Tue, Dec 06, 2016 at 04:02:00PM -0500, Robert Lange wrote: > Debian stretch with chromium 55.0.2883.75-1 (and only chromium) pulled > in from unstable. With a brand new profile (i.e., by deleting > .cache/chromium and .config/chromium and starting Chromium) Chromium > aw-snaps on gfycat.com

Bug#817881: marked as done (fail2ban: FTBFS: AssertionError: None among ('Lines: 19 lines, 0 ignored, 13 matched, 6 missed',) was found in the log)

Your message dated Fri, 9 Dec 2016 09:40:12 -0500 with message-id <20161209144012.d2mn5kbiut2yy...@hopa.kiewit.dartmouth.edu> and subject line 0.9.5 build did not show this failure has caused the Debian Bug report #817881, regarding fail2ban: FTBFS: AssertionError: None among ('Lines: 19 lines, 0

  1   2   >