Bug#847834: ruby-github-markup: FTBFS: IndexError: pop from empty list

2016-12-12 Thread Chris Lamb
Source: ruby-github-markup Version: 1.5.0+dfsg-3 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, ruby-github-markup fails to build from source in

Bug#839048: js24 crashes on ARM64

2016-12-12 Thread Zheng Xu
On 12 December 2016 at 13:59, Ben Hutchings wrote: > On Mon, 2016-12-12 at 13:51 +0800, Zheng Xu wrote: > > mozjs24 -- The patch is the back port version of the upstream one. It > > doesn't change the ABI. > > Unfortunately, the patch that was applied does change the ABI. > The patch I uploaded f

Bug#828267: [Pkg-citadel-devel] Bug#828267: reopen, it is still valid

2016-12-12 Thread Sebastian Andrzej Siewior
On 2016-12-11 21:07:14 [+0100], Michael Meskes wrote: > Sorry, wasn't precise enough it seems. I was wondering why you left out > the third possible option, namely the compatibility API in libssl 1.1. Ach. It does not work that way, this "compatibility" API is defined by the openssl build and shou

Bug#845753: marked as done (r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 09:04:55 + with message-id and subject line Bug#845753: fixed in r-cran-treescape 1.10.18-1 has caused the Debian Bug report #845753, regarding r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow to be marked as done. This means th

Processed: Reopen since problem persists

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 845753 Bug #845753 {Done: Andreas Tille } [src:r-cran-treescape] r-cran-treescape FTBFS on armhf, i386: Error: segfault from C stack overflow 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will

Bug#845753: Help: r-cran-treescape does not build on i386, armel and armhf any more

2016-12-12 Thread Andreas Tille
Hi Paul, On Thu, Nov 03, 2016 at 11:40:04AM +0800, Paul Wise wrote: > On Thu, Nov 3, 2016 at 12:20 AM, Andreas Tille wrote: > > > I used xauth and xvfb as Build-Depends successfully which works on most > > architectures - but failed on these ones. Any hint how to solve this? > > If you don't ha

Bug#847789: Possible fix

2016-12-12 Thread Julien Puydt
Hi, can you check the attached patch fixes the bug? I couldn't test it properly since several of node-vinyl-fs build-deps are not available in Debian yet and I'm a bit short on time this morning for a compilation spree. Snark on #debian-js Description: do not use default arguments (Debian's n

Bug#847888: after activate an other window the mailedit-window hangs

2016-12-12 Thread Jörg Frings-Fürst
Package: evolution Version: 3.22.2-1 Severity: grave Hi, since the update from today the Edit Window hangs after release the focus and reenter. After start via console I get: > evolution (evolution:17050): Gtk-WARNING **: Failed to get the GNOME session proxy: The name org.gnome.SessionManager

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

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 10:18:34 + with message-id and subject line Bug#822010: fixed in ng 1.5~beta1-4 has caused the Debian Bug report #822010, regarding ng: Build arch:all+arch:any but is missing build-{arch,indep} targets to be marked as done. This means that you claim that th

Bug#817593: marked as done (ng: Removal of debhelper compat 4)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 10:18:34 + with message-id and subject line Bug#817593: fixed in ng 1.5~beta1-4 has caused the Debian Bug report #817593, regarding ng: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#847764: Pending fixes for bugs in the prometheus package

2016-12-12 Thread pkg-go-maintainers
tag 847764 + pending thanks Some bugs in the prometheus package are closed in revision f6c40f3b2defb82b79f3d54d510d1614c8ae06ab in branch 'debian/sid' by Martín Ferrari The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/prometheus.git/commit/?id=f6c40f3 Commit message:

Bug#847789: [Pkg-javascript-devel] Bug#847789: Possible fix

2016-12-12 Thread Pirate Praveen
On തിങ്കള്‍ 12 ഡിസംബര്‍ 2016 03:22 വൈകു, Julien Puydt wrote: > Hi, > > can you check the attached patch fixes the bug? I couldn't test it > properly since several of node-vinyl-fs build-deps are not available in > Debian yet and I'm a bit short on time this morning for a compilation > spree. The

Processed: Pending fixes for bugs in the prometheus package

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 847764 + pending Bug #847764 [src:prometheus] prometheus FTBFS on armel: FAIL github.com/prometheus/prometheus/storage/local Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 847764: http:

Bug#845892: marked as done (pike7.8: switch to build depend on the metapackage default-libmysqlclient-dev)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 11:39:40 +0100 with message-id <2080633.BPmnSBW7Kv@hisingen> and subject line Was already done has caused the Debian Bug report #845892, regarding pike7.8: switch to build depend on the metapackage default-libmysqlclient-dev to be marked as done. This means tha

Bug#845893: marked as done (pike8.0: switch to build depend on the metapackage default-libmysqlclient-dev)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 11:38:01 +0100 with message-id <9945953.zODKopnZoT@hisingen> and subject line Was already done has caused the Debian Bug report #845893, regarding pike8.0: switch to build depend on the metapackage default-libmysqlclient-dev to be marked as done. This means tha

Bug#846562: marked as done (node-mustache, ruby-mustache: error when trying to install together: both ship /usr/bin/mustache)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 10:48:52 + with message-id and subject line Bug#846562: fixed in mustache.js 2.3.0-2 has caused the Debian Bug report #846562, regarding node-mustache, ruby-mustache: error when trying to install together: both ship /usr/bin/mustache to be marked as done.

Bug#817686: marked as done (tcm: Removal of debhelper compat 4)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 10:49:19 + with message-id and subject line Bug#817686: fixed in tcm 2.20+TSQD-5 has caused the Debian Bug report #817686, regarding tcm: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#847764: marked as done (prometheus FTBFS on armel: FAIL github.com/prometheus/prometheus/storage/local)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 10:49:04 + with message-id and subject line Bug#847764: fixed in prometheus 1.2.3+ds2-5 has caused the Debian Bug report #847764, regarding prometheus FTBFS on armel: FAIL github.com/prometheus/prometheus/storage/local to be marked as done. This means that

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

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 10:49:19 + with message-id and subject line Bug#822031: fixed in tcm 2.20+TSQD-5 has caused the Debian Bug report #822031, regarding tcm: Build arch:all+arch:any but is missing build-{arch,indep} targets to be marked as done. This means that you claim that

Processed: tagging 653376, found 784619 in 1.4.1-5, found 847353 in 1.12.1+dfsg-2 ...

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 653376 - pending Bug #653376 [tvtime] tvtime: Please switch to new upstream Removed tag(s) pending. > found 784619 1.4.1-5 Bug #784619 [src:creepy] [creepy] Qt4's WebKit removal Bug #844997 [src:creepy] creepy: Depends on PyQt4.QtWebKit Marke

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Sergey B Kirpichev
reopen 847196 thanks Please don't reply personally (unless you want to share some private info)! Either to bugtracker, or add CC to bugtracker. Meanwhile, bug reopened. Perhaps, backport is still broken. (Also, co-mantainers, please use git!) BTW, I can't reproduce this yet. Perhaps, this rel

Processed: Re: Bug#847196: monit segfault on stop and start

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 847196 Bug #847196 {Done: Jonas Meurer } [monit] monit segfault on stop and start '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

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Arthur Hoffmann
I just want to confirm that Monit is running again on all 5 Debian Wheezy (i386 and amd64) machines if I downgrade the package with "sudo apt-get install monit=1:5.4-2".

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

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 11:34:06 + with message-id and subject line Bug#845868: fixed in libterralib 4.3.0+dfsg.2-10 has caused the Debian Bug report #845868, regarding libterralib: switch to build depend on the metapackage default-libmysqlclient-dev to be marked as done. This me

Bug#842093: marked as done (libupnp: CVE-2016-8863)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 11:34:13 + with message-id and subject line Bug#842093: fixed in libupnp 1:1.6.19+git20160116-1.2 has caused the Debian Bug report #842093, regarding libupnp: CVE-2016-8863 to be marked as done. This means that you claim that the problem has been dealt with

Bug#811740: marked as done (nautic: FTBFS with GCC 6: narrowing conversion)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 11:49:41 + with message-id and subject line Bug#811740: fixed in nautic 1.5-2 has caused the Debian Bug report #811740, regarding nautic: FTBFS with GCC 6: narrowing conversion to be marked as done. This means that you claim that the problem has been dealt

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Sergey B Kirpichev
On Mon, Dec 12, 2016 at 12:24:31PM +0100, Arthur Hoffmann wrote: > I just want to confirm that Monit is running again on all 5 Debian Wheezy > (i386 and amd64) machines if I downgrade the package with "sudo apt-get > install monit=1:5.4-2". Unfortunately, I can't reproduce this on several testing

Bug#847888: Debian bug #847888

2016-12-12 Thread Jörg Frings-Fürst
Hi, I attach the apt history log. CU Jörg -- Jörg Frings-Fürst flyingpenguin.de UG (haftungsbeschränkt) Hauptstraße 75 D-56862 Pünderich Telefon +49 6542 934 8890 Amtsgericht Koblenz HRB 22160 USt-IdNr. DE273878135 Steuer-Nr. 40/659/01483 Start-Date: 2016-12-05 07:55:11 Commandline: apt-ge

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Arthur Hoffmann
Ok, now I have checked my config files and found out that it works with the latest package if I remove the following line: set mmonit https://USER:PASSWORD@URL:PORT/collector I'm using Monit with the latest M/Monit v3.6.2.

Processed: 1

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 847196 1:5.20.0-1 Bug #847196 [monit] monit segfault on stop and start Marked as fixed in versions monit/1:5.20.0-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 847196: http://bugs.debian.org/cg

Bug#847806: marked as done (libopenmpi2: broken SONAME links)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 12:19:44 + with message-id and subject line Bug#847806: fixed in openmpi 2.0.2~git.20161225-5 has caused the Debian Bug report #847806, regarding libopenmpi2: broken SONAME links to be marked as done. This means that you claim that the problem has been deal

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Sergey B Kirpichev
On Mon, Dec 12, 2016 at 01:11:38PM +0100, Arthur Hoffmann wrote: > Ok, now I have checked my config files and found out that it > works with the latest package if I remove the following line: > > set mmonit https://USER:PASSWORD@URL:PORT/collector Ok, I see. I don't use closed-source software, s

Bug#836759: marked as done (proftpd-dfsg: please drop the build dependency on hardening-wrapper)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 13:04:25 + with message-id and subject line Bug#836759: fixed in proftpd-dfsg 1.3.5b-1 has caused the Debian Bug report #836759, regarding proftpd-dfsg: please drop the build dependency on hardening-wrapper to be marked as done. This means that you claim th

Bug#831961: marked as done (proftpd-dfsg: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop.)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 13:04:25 + with message-id and subject line Bug#831961: fixed in proftpd-dfsg 1.3.5b-1 has caused the Debian Bug report #831961, regarding proftpd-dfsg: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop. to be marked as

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Martin Pala
Sorry for typo in the explanation ... the "token" comes *after* "strlen(D)" in the patch - in short: integer "strlen(D)" is used as string argument for "Cookie: securitytoken=%s\r\n" => CRASH string "token" is used as integer argument for "Content-Length: %d\r\n" ... harmless,

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Martin Pala
Hello, the problem is in debian patch (5.4-2+deb7u2): --- a/src/collector.c +++ b/src/collector.c @@ -64,10 +64,13 @@ */ static int data_send(Socket_T socket, Mmonit_T C, const char *D) { char *auth = Util_getBasicAuthHeader(C->url->user, C->url->password); +MD_T token; +

Bug#847556: marked as done (fossil: Cannot clone/sync over HTTPS)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 13:19:02 + with message-id and subject line Bug#847556: fixed in fossil 1:1.36-2 has caused the Debian Bug report #847556, regarding fossil: Cannot clone/sync over HTTPS to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Sergey B Kirpichev
On Mon, Dec 12, 2016 at 02:06:41PM +0100, Martin Pala wrote: > The securitytoken in collector is not needed at all - the CSRF > protection is related to Monit's own HTTP API (the securitytoken > cookie is not present in upstream). Ok, I see. Thank you, Martin. > To fix the problem, just drop the

Bug#817704: marked as done (uclmmbase: Removal of debhelper compat 4)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 13:35:29 + with message-id and subject line Bug#817704: fixed in uclmmbase 1.2.16.0-2 has caused the Debian Bug report #817704, regarding uclmmbase: Removal of debhelper compat 4 to be marked as done. This means that you claim that the problem has been deal

Bug#821893: marked as done (uclmmbase: FTBFS: mkdir: cannot create directory 'html': File exists)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 13:35:29 + with message-id and subject line Bug#821893: fixed in uclmmbase 1.2.16.0-2 has caused the Debian Bug report #821893, regarding uclmmbase: FTBFS: mkdir: cannot create directory 'html': File exists to be marked as done. This means that you claim th

Bug#833201: marked as done (uclmmbase: Uses obsolete Source-Version substvar)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 13:35:29 + with message-id and subject line Bug#833201: fixed in uclmmbase 1.2.16.0-2 has caused the Debian Bug report #833201, regarding uclmmbase: Uses obsolete Source-Version substvar to be marked as done. This means that you claim that the problem has b

Bug#847932: hexchat-otr: FTBFS: hexchat_otr.h:18:28: fatal error: hexchat-plugin.h: No such file or directory

2016-12-12 Thread Chris Lamb
Source: hexchat-otr Version: 0.2.1-2 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, hexchat-otr fails to build from source in unstable/amd64:

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Arthur Hoffmann
I'd like to help with what I can, but the problem is that I'm not a C/C++ developer, never seen the source code of monit and haven't got a development environment for that. Maybe I could setup and try it this weekend but I hope there is somebody else who can do it "easier". However I can test a

Bug#846252: kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed

2016-12-12 Thread Maximiliano Curia
Control: severity -1 important ¡Hola Chris! El 2016-11-29 a las 16:33 +0100, Chris Lamb escribió: Source: kf5-kdepim-apps-libs Version: 4:16.04.2-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: re

Processed: Re: Bug#846252: kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed

2016-12-12 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #846252 [src:kf5-kdepim-apps-libs] kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed Severity set to 'important' from 'serious' -- 846252: http://bugs.debian.org/c

Bug#835746: fixed in odin-2.0.3: FTBFS: seqgradspiral.cpp:30:71: error: no matching function for call to 'max(double, float)'

2016-12-12 Thread Thies Jochimsen
Hi Michael, just tested it on a current Debian stretch. It looks fine with the following Qt5/Qwt6 packages installed: dpkg -l | grep 'libqt5\|libqwt' | grep ^ii ii libqt5concurrent5:amd64 5.7.1~20161021+dfsg-6 amd64Qt 5 concurrent module ii libqt5core5a:amd64

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

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 15:00:13 + with message-id and subject line Bug#845873: fixed in mailutils 1:3.0-1 has caused the Debian Bug report #845873, regarding mailutils: switch to build depend on the metapackage default-libmysqlclient-dev to be marked as done. This means that you

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Arthur Hoffmann
It looks like this bug is fixed, I did "dpkg -i monit_5.4-2+deb7u3_amd64.deb", monit restarted and is running now. Thank you. Source package was uploaded to https://mentors.debian.net/package/monit amd64 deb attached.

Bug#847196: monit segfault on stop and start

2016-12-12 Thread Sergey B Kirpichev
On Mon, Dec 12, 2016 at 04:23:57PM +0100, Arthur Hoffmann wrote: > It looks like this bug is fixed, > I did "dpkg -i monit_5.4-2+deb7u3_amd64.deb", monit restarted and is > running > now. > Thank you. > >Source package was uploaded to > >https://mentors.debian.net/package/monit > >amd64 deb attache

Bug#845898: marked as done (proftpd-dfsg: switch to build depend on the metapackage default-libmysqlclient-dev)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 16:46:41 +0100 with message-id <28e47016-61d7-ae15-ab5d-8b6e55306...@web.de> and subject line Re: Bug#845898: proftpd-dfsg: switch to build depend on the metapackage default-libmysqlclient-dev has caused the Debian Bug report #845898, regarding proftpd-dfsg: swi

Bug#847956: libzorpll-6.0-10-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/zorp/blob.h

2016-12-12 Thread Andreas Beckmann
Package: libzorpll-6.0-10-dev Version: 6.0.10.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overw

Bug#828513: proftpd-dfsg: FTBFS with openssl 1.1.0

2016-12-12 Thread Hilmar Preuße
severity 828513 important stop On 26.06.2016 12:23, Kurt Roeckx wrote: Hi Kurt > 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/Attempte

Bug#847666: asterisk: AST-2016-008: Crash on SDP offer or answer from endpoint using Opus

2016-12-12 Thread Tzafrir Cohen
On Sat, Dec 10, 2016 at 03:52:26PM +0100, Salvatore Bonaccorso wrote: > Source: asterisk > Version: 1:13.12.2~dfsg-1 > Severity: grave > Tags: security upstream patch > Forwarded: https://issues.asterisk.org/jira/browse/ASTERISK-26579 > > Hi > > AST-2016-008 was announced at > > http://downloads

Processed: Re: Bug#828513: proftpd-dfsg: FTBFS with openssl 1.1.0

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 828513 important Bug #828513 [src:proftpd-dfsg] proftpd-dfsg: FTBFS with openssl 1.1.0 Severity set to 'important' from 'serious' > stop Stopping processing here. Please contact me if you need assistance. -- 828513: http://bugs.debian.o

Bug#847961: gitweb: missing dependency to libcgi-pm-perl

2016-12-12 Thread Mikko Rasa
Package: gitweb Version: 1:2.11.0-1 Severity: serious Justification: Policy 3.5 After running full-upgrade today I noticed that my gitweb server started returning internal server errors. Apache's error.log contained many repeats of this error: [Mon Dec 12 17:03:04.782271 2016] [cgi:error] [pid 2

Bug#846720: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
x32 debug symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856,

Bug#845730: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
Standard C++ Library v3 (development files) libx32stdc++6 - GNU Standard C++ Library v3 (x32) libx32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files) libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32) libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symb

Bug#846699: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
behaviour sanitizer (x32) libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR targ

Bug#845377: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
zer (x32) libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC),

Bug#846669: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856, PR libstdc++/77459, PR li

Bug#846726: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
x32 debug symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856,

Bug#846715: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
s) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856, PR li

Bug#846725: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
s) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856, PR li

Bug#846724: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
x32 debug symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856,

Bug#847666: asterisk: AST-2016-008: Crash on SDP offer or answer from endpoint using Opus

2016-12-12 Thread Salvatore Bonaccorso
Hi Tzafrir, On Mon, Dec 12, 2016 at 05:48:53PM +0200, Tzafrir Cohen wrote: > On Sat, Dec 10, 2016 at 03:52:26PM +0100, Salvatore Bonaccorso wrote: > > Source: asterisk > > Version: 1:13.12.2~dfsg-1 > > Severity: grave > > Tags: security upstream patch > > Forwarded: https://issues.asterisk.org/jir

Bug#846742: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
r (x32 debug symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstd

Bug#846712: marked as done (gdc-6 PIE build failures)

2016-12-12 Thread Debian Bug Tracking System
.2.1-6) unstable; urgency=high . * Update to SVN 20161212 (r243558, 6.2.1) from the gcc-6-branch. - Fix PR target/78426 (SH), PR fortran/78500, PR target/78101 (PPC), PR target/48863 (ARM32), PR inline-asm/70184, PR libstdc++/71856, PR libstdc++/77459, PR libstdc++/78326, PR l

Processed: notfound 847666 in 1:13.12.2~dfsg-1

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 847666 1:13.12.2~dfsg-1 Bug #847666 [src:asterisk] asterisk: AST-2016-008: Crash on SDP offer or answer from endpoint using Opus No longer marked as found in versions asterisk/1:13.12.2~dfsg-1. > thanks Stopping processing here. Please

Bug#811663: marked as done (FTBFS with GCC 6: cannot convert x to y)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 16:34:31 + with message-id and subject line Bug#811663: fixed in tora 2.1.3-3 has caused the Debian Bug report #811663, regarding FTBFS with GCC 6: cannot convert x to y to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#812280: marked as done (newmat: FTBFS with GCC 6: terminate called)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 16:48:35 + with message-id and subject line Bug#812280: fixed in newmat 1.10.4-6 has caused the Debian Bug report #812280, regarding newmat: FTBFS with GCC 6: terminate called to be marked as done. This means that you claim that the problem has been dealt w

Bug#847966: python-cylc: ails to upgrade from 'jessie' - trying to overwrite /usr/lib/python2.7/dist-packages/xdot.py

2016-12-12 Thread Andreas Beckmann
Package: python-cylc Version: 6.11.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'jessie', then the upgrade to 'sid' fails because it tries to overwrite other p

Bug#847970: sunpy FTBFS in stretch due to missing skimage

2016-12-12 Thread Adrian Bunk
Source: sunpy Version: 0.7.4-1 Severity: serious Tags: stretch sid Control: block -1 by 840589 node-yargs build-depends on python{,3}-skimage, which is not in stretch due to #840589

Processed: sunpy FTBFS in stretch due to missing skimage

2016-12-12 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 840589 Bug #847970 [src:sunpy] sunpy FTBFS in stretch due to missing skimage 847970 was not blocked by any bugs. 847970 was not blocking any bugs. Added blocking bug(s) of 847970: 840589 -- 847970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847970

Bug#847970: sunpy FTBFS in stretch due to missing skimage

2016-12-12 Thread Ole Streicher
Hi Adrian, I do not completely understand what the goal of this bug is: The missing build dependency is already noted in the package, and an autoremoval is filed (and sent out to me as the maintainer). So, I am already noted by the problem, and I don't see what the additional bug gives here except

Bug#841208: fixed in monkeysphere 0.41-1

2016-12-12 Thread Santiago Vila
found 841208 0.41-1 thanks Hello. Sorry for the reopening but this issue is still happening in this version. I attach two different build logs. Thanks. monkeysphere_0.41-1_amd64-20161211T041458Z.gz Description: application/gzip monkeysphere_0.41-1_amd64-20161211T043600Z.gz Description: applica

Processed: Re: Bug#841208: fixed in monkeysphere 0.41-1

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 841208 0.41-1 Bug #841208 {Done: Daniel Kahn Gillmor } [src:monkeysphere] monkeysphere: FTBFS (not enough entropy to generate keys) Marked as found in versions monkeysphere/0.41-1; no longer marked as fixed in versions monkeysphere/0.41-1

Bug#847970: sunpy FTBFS in stretch due to missing skimage

2016-12-12 Thread Adrian Bunk
On Mon, Dec 12, 2016 at 06:15:34PM +0100, Ole Streicher wrote: > Hi Adrian, Hi Ole, > I do not completely understand what the goal of this bug is: The missing > build dependency is already noted in the package, and an autoremoval is > filed (and sent out to me as the maintainer). So, I am already

Processed: [bts-link] source package src:gnucash

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gnucash > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debi

Bug#847974: xmds2: FTBFS in stretch

2016-12-12 Thread Santiago Vila
Package: src:xmds2 Version: 2.2.2+dfsg-2 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: ---

Bug#847975: python-matplotlib: All attempts to plot fail with "OverflowError: Python int too large to convert to C long"

2016-12-12 Thread Akkana Peck
Package: python-matplotlib Version: 1.5.3-1 Severity: grave Justification: renders package unusable Every Python script I have that uses matplotlib or pylab is now failing on Stretch with the following stack trace: Exception in Tkinter callback Traceback (most recent call last): File "/usr/lib/

Bug#847975: python-matplotlib: All attempts to plot fail with "OverflowError: Python int too large to convert to C long"

2016-12-12 Thread Sandro Tosi
On Mon, Dec 12, 2016 at 12:37 PM, Akkana Peck wrote: > These scripts all work fine on Jessie, and used to work until quite > recently on Stretch/Sid. did you upgrade something on your machine recently? i'm thinking about `python2.7` - you can check that in /var/log/apt/history.log -- Sandro "mo

Bug#844754: marked as done (xonsh FTBFS in stretch due to missing cloud-sptheme)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 17:51:21 + with message-id and subject line Bug#844754: fixed in xonsh 0.4.7+dfsg-2 has caused the Debian Bug report #844754, regarding xonsh FTBFS in stretch due to missing cloud-sptheme to be marked as done. This means that you claim that the problem has

Bug#847966: python-cylc: ails to upgrade from 'jessie' - trying to overwrite /usr/lib/python2.7/dist-packages/xdot.py

2016-12-12 Thread Alastair McKinstry
python-cylc is a new package which hasn't been in testing before (or tested properly against piuparts). xdot 0.7-2 supplies /usr/lib/python3/dist-packages/xdot.py instead. I'll need to add a versioned breaks / replaces for xdot, thanks. regards Alastair On 12/12/2016 16:54, Andreas Beckmann

Bug#846649: Squeeze ?

2016-12-12 Thread Oleg Moskalenko
I am not sure that I understand why this binary package is used with Squeeze, regardless of the kernel. This package is extensively using OpenSSL and it is very sensitive to the binary compatibility with OpenSSL libraries. The errors look exactly like something is wrong with the OpenSSL libraries c

Bug#844256: marked as done (jclic: all bugs have been resolved at mainstream, but Debian package has not been updated for more than 6 years)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 18:48:40 + with message-id and subject line Bug#844256: fixed in jclic 0.3.2.1-1 has caused the Debian Bug report #844256, regarding jclic: all bugs have been resolved at mainstream, but Debian package has not been updated for more than 6 years to be marked

Bug#828477: Building against openssl1.0 for the time being

2016-12-12 Thread Alberto Gonzalez Iniesta
Control: unblock 827061 by -1 Uploaded 2.4~rc1-1 build against openssl1.0 until upstream moves to 1.1 -- Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico mailto/sip: a...@inittab.org | en GNU/Linux y software libre Encrypted mail preferred| http://inittab.com Key fing

Processed: Building against openssl1.0 for the time being

2016-12-12 Thread Debian Bug Tracking System
Processing control commands: > unblock 827061 by -1 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828558 844254 829465 828461 828551 828340 828509 828391 828449 828607 828389 828513 828428 828310 828490 828354 828232 828504 828448 828369 828289 828457 844800 828234

Processed: Re: Bug#844523: Debian xserver freeze

2016-12-12 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #844523 [xserver-xorg] Debian xserver freeze Severity set to 'important' from 'critical' > reassign -1 xserver-xorg-core 2:1.16.4-1 Bug #844523 [xserver-xorg] Debian xserver freeze Bug reassigned from package 'xserver-xorg' to 'xserver-xorg-

Bug#844523: Debian xserver freeze

2016-12-12 Thread Emilio Pozuelo Monfort
Control: severity -1 important Control: reassign -1 xserver-xorg-core 2:1.16.4-1 On 16/11/16 15:30, Carmelo C wrote: > Package: xserver-xorg > Version: 1:7.7+7 > Severity: critical > Tags: security > Justification: breaks the whole system > > For some time I noticed that browsing with firefox on

Bug#839444: libgda5: FTBFS: tests failures annotations:

2016-12-12 Thread Emilio Pozuelo Monfort
Hi Santiago, On 21/10/16 17:32, Santiago Vila wrote: > retitle 839444 libgda5: FTBFS sometimes (check_data_proxy fails) > thanks > > Hello Lucas. > > You are reporting two different things here, this usually makes things > more difficult to maintainers. It is usually a lot better to report > dif

Bug#834654: Test failures

2016-12-12 Thread Emilio Pozuelo Monfort
Control: retitle -1 heimdal: FTBFS: test suite errors On Sat, 10 Dec 2016 19:29:35 + Jelmer =?utf-8?Q?Vernoo=C4=B3?= wrote: > I've uploaded a new Debian version to unstable packaging RC1. > Unfortunately there are a test failures on various > architectures. :( > > Note that not all of these

Processed: Re: Test failures

2016-12-12 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 heimdal: FTBFS: test suite errors Bug #834654 [src:heimdal] no upstream releases; severe bugs open Changed Bug title to 'heimdal: FTBFS: test suite errors' from 'no upstream releases; severe bugs open'. -- 834654: http://bugs.debian.org/cgi-bin/bugrepor

Processed: Re: Bug#844924: pygobject: FTBFS: Tests failures

2016-12-12 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=776009 Bug #844924 [src:pygobject] pygobject: FTBFS: Tests failures Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=776009'. -- 844924: http://bugs.debian.org/cgi-bin/bugreport.cgi

Processed: limit source to pygobject, tagging 844924

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source pygobject Limiting to bugs with field 'source' containing at least one of 'pygobject' Limit currently set to 'source':'pygobject' > tags 844924 + pending Bug #844924 [src:pygobject] pygobject: FTBFS: Tests failures Added tag(s) pendi

Bug#844924: pygobject: FTBFS: Tests failures

2016-12-12 Thread Emilio Pozuelo Monfort
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=776009 On 19/11/16 08:03, Lucas Nussbaum wrote: > Source: pygobject > Version: 3.22.0-1 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161118 qa-ftbfs > Justification: FTBFS on amd64

Processed: limit source to pygobject, tagging 844924

2016-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source pygobject Limiting to bugs with field 'source' containing at least one of 'pygobject' Limit currently set to 'source':'pygobject' > tags 844924 + pending Bug #844924 [src:pygobject] pygobject: FTBFS: Tests failures Ignoring request t

Bug#840589: marked as done (skimage FTBFS on multiple architectures testsuite failures.)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 19:49:06 + with message-id and subject line Bug#840589: fixed in skimage 0.12.3-2 has caused the Debian Bug report #840589, regarding skimage FTBFS on multiple architectures testsuite failures. to be marked as done. This means that you claim that the proble

Bug#844924: marked as done (pygobject: FTBFS: Tests failures)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 19:48:45 + with message-id and subject line Bug#844924: fixed in pygobject 3.22.0-2 has caused the Debian Bug report #844924, regarding pygobject: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#847196: marked as done (monit segfault on stop and start)

2016-12-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Dec 2016 20:56:05 +0100 with message-id <8de7c64e-7bd1-93e9-c3fd-9ed0e55c2...@freesources.org> and subject line Re: Bug#847196: monit segfault on stop and start has caused the Debian Bug report #847196, regarding monit segfault on stop and start to be marked as done. Thi

Bug#839444: libgda5: FTBFS: tests failures annotations:

2016-12-12 Thread Santiago Vila
On Mon, Dec 12, 2016 at 08:12:00PM +0100, Emilio Pozuelo Monfort wrote: > Unfortunately you're missing libc6-dbg and libsqlite3-0-dbg. Could you get a > backtrace with those, so that I can forward this upstream? Sure. Here it is: $ gdb tests/data-models/.libs/check_data_proxy tests/data-models/c

  1   2   >