Processed: raising severity for packages still build-depending on gcc-5

Processing commands for cont...@bugs.debian.org: > severity 835940 serious Bug #835940 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: non-standard gcc/g++ used for build (gcc-5) Severity set to 'serious' from 'important' > severity 835941 serious Bug #835941 [starpu-contrib] starpu-contrib:

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

Hi Paul, On Tue, Dec 13, 2016 at 09:07:11AM +0800, Paul Wise wrote: > > Any help would be really appreciated. > > Looking at the build logs, even the architectures that succeeded are > getting the warning about X11. So that is completely unrelated and the > issue is the segfault not the xvfb

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

On Tue, Dec 13, 2016 at 3:47 PM, Andreas Tille wrote: > Well, adding xvfb was the usual trick to cope with "unable to open X11 > display" messages and thus I added it ... To me it looks like you didn't add it yet, at least not to the version in Debian. -- bye, pabs

Bug#848012: glimpse: FTBFS: /usr/bin/ld: cannot find -lfl

Source: glimpse Version: 4.18.7-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, glimpse fails to build from source in unstable/amd64: […]

Bug#848013: node-temporary: FTBFS: Error: Cannot find module 'sinon'

Source: node-temporary Version: 0.0.8-1 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, node-temporary fails to build from source in

Bug#833252: marked as done (lbzip2: Uses obsolete compressor for .deb data.tar member)

Your message dated Tue, 13 Dec 2016 06:18:32 + with message-id and subject line Bug#833252: fixed in lbzip2 2.5-2 has caused the Debian Bug report #833252, regarding lbzip2: Uses obsolete compressor for .deb data.tar member to be marked as done. This

Bug#794466: VIrtualBox future in Debian

On Tue, 25 Oct 2016 17:29:39 +0200 Gianfranco Costamagna < locutusofb...@debian.org> wrote: > As per DSA-3699-1, security team thinks virtualbox can't be released with Stretch. Thanks for all your work in maintaining VirtuaBox in Debian. Could you answer the following questions so that I (and

Bug#847808: marked as done (ruby-jquery-ui-rails FTBFS)

Your message dated Tue, 13 Dec 2016 04:03:42 + with message-id and subject line Bug#847808: fixed in ruby-jquery-ui-rails 6.0.1+dfsg-2 has caused the Debian Bug report #847808, regarding ruby-jquery-ui-rails FTBFS to be marked as done. This means that you

Bug#847998: manpages: file conflicts with initscripts

On Tue, 13 Dec 2016 00:44:24 +0100 Sebastian Ramacher wrote: > Package: manpages > Version: 4.09-1 > Severity: serious > > manpages fails to install because it shares tmpfs(5) with initscripts: > > dpkg: error processing archive >

Processed: tagging 784181

Processing commands for cont...@bugs.debian.org: > tags 784181 + sid Bug #784181 [src:razorqt] razorqt: Razor-Qt dead upstream, superseded by LXDE-Qt Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 784181:

Bug#848006: gearhead2: purging deletes /etc/gearhead2.conf, owned by gearhead2-data

Package: gearhead2 Version: 0.630-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package removes files that were installed by another package. >From the attached log (scroll to the bottom...): 0m37.4s ERROR: FAIL: debsums

Bug#848004: imapproxy: fails to install: cp: cannot stat '/etc/localtime': No such file or directory

Package: imapproxy Version: 1.2.8~svn20161210-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity.

Bug#848003: firejail: Unable to add/remove users/groups when it is running

Package: firejail Version: 0.9.44-1~bpo8+1 Severity: critical Tags: upstream Justification: breaks unrelated software Dear Maintainer, When there is an instance of firejail running, and the package manager or myself attempt to add or remove an user or group (outside of the firejail sandbox) by

Bug#847997: [pkg-go] Bug#847997: golang-github-jessevdk-go-flags-dev: Cannot bo co-installed golang-go-flags-dev

Hi Hilko. Hey thanks for the bug report. Looks like it's totally my fault for not double checking that this package was not already in Debian under an old name. I think I'll probably ask the FTP Masters very nicely to remove the new package rather than mess with the reverse dependencies.

Processed: reassign 792852 to src:comgt, fixed 792852 in 0.32-3

Processing commands for cont...@bugs.debian.org: > reassign 792852 src:comgt 0.32-2 Bug #792852 {Done: Andreas "Jimmy" Gredler } [gcom] gcom: copyright file missing after upgrade (policy 12.5) Bug reassigned from package 'gcom' to 'src:comgt'. No longer marked as found in

Processed: reassign 846562 to mustache.js, fixed 846562 in 2.3.0-2, affects 846562

Processing commands for cont...@bugs.debian.org: > reassign 846562 mustache.js 2.3.0-1 Bug #846562 {Done: Martín Ferrari } [node-mustache,ruby-mustache] node-mustache, ruby-mustache: error when trying to install together: both ship /usr/bin/mustache Bug reassigned from

Bug#845734: pandas FTBFS on i386 due to test failures

On Mon, 12 Dec 2016, Sandro Tosi wrote: > On Sat, 26 Nov 2016 12:21:29 +0200 Adrian Bunk wrote: > > Source: pandas > > Version: 0.19.1-1 > > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=pandas=i386=0.19.1-1=1479504883 > the failures are now on more arch

Bug#845734: pandas FTBFS on i386 due to test failures

On Sat, 26 Nov 2016 12:21:29 +0200 Adrian Bunk wrote: > Source: pandas > Version: 0.19.1-1 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=pandas=i386=0.19.1-1=1479504883 the failures are now on more arch and even with 0.19.1-3 and 0.19.1+git174-g81a2f79-1

Bug#841208: fixed in monkeysphere 0.41-1

Hi Santiago-- thanks for the reportbacks- On Mon 2016-12-12 18:17:37 +0100, Santiago Vila wrote: > Hello. Sorry for the reopening but this issue is still happening in > this version. I attach two different build logs. thanks for the notes. the issue is now entropy starvation during

Bug#847820: kicad: FTBFS: cannot access .../kicad-common/...

tags 847820 + pending thanks Hello Santiago and Aaron, On Tue, Dec 13, 2016 at 12:17:00AM +0100, Santiago Vila wrote: > Patch (untested) based on the hints by Aaron. > > (I would also remove the CURDIR thing, it's not required). I disagree a little bit on this point, explicit is better than

Processed: Re: Bug#847820: kicad: FTBFS: cannot access .../kicad-common/...

Processing commands for cont...@bugs.debian.org: > tags 847820 + pending Bug #847820 [src:kicad] kicad: FTBFS: cannot access .../kicad-common/... Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 847820:

Bug#847998: manpages: file conflicts with initscripts

Package: manpages Version: 4.09-1 Severity: serious manpages fails to install because it shares tmpfs(5) with initscripts: dpkg: error processing archive /tmp/apt-dpkg-install-7sSPgR/26-manpages_4.09-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man5/tmpfs.5.gz', which is also in

Processed: golang-github-jessevdk-go-flags-dev: Cannot bo co-installed golang-go-flags-dev

Processing control commands: > tag -1 patch Bug #847997 [golang-github-jessevdk-go-flags-dev] golang-github-jessevdk-go-flags-dev: Cannot bo co-installed golang-go-flags-dev Added tag(s) patch. -- 847997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847997 Debian Bug Tracking System

Bug#847997: golang-github-jessevdk-go-flags-dev: Cannot bo co-installed golang-go-flags-dev

Package: golang-github-jessevdk-go-flags-dev Version: 1.1-1 Severity: grave Control: tag -1 patch Dear Maintainer, when trying to install golang-github-jessevdk-go-flags-dev, I got the following error: , | Preparing to unpack .../0-golang-github-jessevdk-go-flags-dev_1.1-1_all.deb ... |

Processed: severity 846649 normal

Processing commands for cont...@bugs.debian.org: > severity 846649 normal Bug #846649 [coturn] Frequent segfaults of coturn Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 846649:

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

On 09/12/16 22:37, roucaries bastien wrote: > control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/320 > > Dear realease team, > > What is the next step? In which version was the ABI break introduced? In general I would prefer the change to be reverted, but depending on how

Bug#845821: marked as done (aolserver4-nsmysql: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Mon, 12 Dec 2016 23:18:23 + with message-id and subject line Bug#845821: fixed in aolserver4-nsmysql 0.6-11 has caused the Debian Bug report #845821, regarding aolserver4-nsmysql: switch to build depend on the metapackage

Bug#847820: kicad: FTBFS: cannot access .../kicad-common/...

Patch (untested) based on the hints by Aaron. (I would also remove the CURDIR thing, it's not required). BTW: Please consider uploading in source-only form (dpkg-buildpackage -S). It's always a good thing to have official build logs here: https://buildd.debian.org/status/package.php?p=kicad

Processed: Bug#840589 closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#840589: fixed in skimage 0.12.3-2)

Processing commands for cont...@bugs.debian.org: > reopen 840589 Bug #840589 {Done: Yaroslav Halchenko } [skimage] skimage FTBFS on multiple architectures testsuite failures. 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will

Bug#840589: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#840589: fixed in skimage 0.12.3-2)

reopen 840589 thanks * debian/patches - changeset_6807f4ee8f5501703e447f95701190c836deaae1.diff to initialize value of firstbg to avoid segfaults (Closes: #840589 ) Unfortunately it seems this upload only marginally

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

Your message dated Mon, 12 Dec 2016 23:03:32 + with message-id and subject line Bug#845834: fixed in dbf2mysql 1.14a-5 has caused the Debian Bug report #845834, regarding dbf2mysql: switch to build depend on the metapackage default-libmysqlclient-dev to

Bug#792852: marked as done (gcom: copyright file missing after upgrade (policy 12.5))

Your message dated Mon, 12 Dec 2016 22:48:26 + with message-id and subject line Bug#792852: fixed in comgt 0.32-3 has caused the Debian Bug report #792852, regarding gcom: copyright file missing after upgrade (policy 12.5) to be marked as done. This means

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

Your message dated Mon, 12 Dec 2016 22:48:26 + with message-id and subject line Bug#821974: fixed in comgt 0.32-3 has caused the Debian Bug report #821974, regarding comgt: Build arch:all+arch:any but is missing build-{arch,indep} targets to be marked as

Bug#843931: marked as done (libgtkdatabox-0.9.3-0-{, lib}glade: fails to upgrade from 'testing' - trying to overwrite /usr/lib/glade/modules/libgladedatabox.a, ...)

Your message dated Mon, 12 Dec 2016 22:21:05 + with message-id and subject line Bug#843931: fixed in libgtkdatabox 1:0.9.3.0+dfsg-3 has caused the Debian Bug report #843931, regarding libgtkdatabox-0.9.3-0-{, lib}glade: fails to upgrade from 'testing' -

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

On Mon, Dec 12, 2016 at 10:32:30PM +0100, Emilio Pozuelo Monfort wrote: > I need the full log. Run valgrind like this: > > valgrind --tool=memcheck --leak-check=full --leak-resolution=high > --num-callers=20 --log-file=vgdump.txt .libs/check_data_proxy > > And attach vgdump.txt Ok, here it

Bug#833061: marked as done (dvdauthor: FTBFS with 'error: conflicting types for 'FriBidiCharType'')

Your message dated Mon, 12 Dec 2016 21:33:21 + with message-id and subject line Bug#833061: fixed in dvdauthor 0.7.0-2 has caused the Debian Bug report #833061, regarding dvdauthor: FTBFS with 'error: conflicting types for 'FriBidiCharType'' to be marked

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

On 12/12/16 22:19, Santiago Vila wrote: > On Mon, Dec 12, 2016 at 09:54:57PM +0100, Emilio Pozuelo Monfort wrote: > >> Huh, this is crashing in libc's malloc(). >> >> Can you run the test under valgrind's memcheck? Maybe there's some memory >> corruption that would explain this. > > Do you mean

Bug#828387: libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0

On Mon, 12 Dec 2016 21:51:01 +0100, Sebastian Andrzej Siewior wrote: > > If we can't get an upstream reaction (which seems probable), maybe > > Petr and Sebastian can at least cross-check their patches and come up > > with a common one? > Gregor, is there anything you want me to do? The

Bug#745405: [src:opal] Source package contains non-free IETF RFC/I-D

On Sat, 16 Jan 2016 16:15:56 +0100 Francesco Poli wrote: > On Sat, 16 Jan 2016 13:40:53 +0100 Eugen Dedu wrote: [...] > > I have forgotten about this bug... > > > > In that commit I removed > > plugins/audio/iLBC/iLBC/draft-ietf-avt-ilbc-codec-05.txt file, but it > > remains several rfc files.

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

On Mon, Dec 12, 2016 at 09:54:57PM +0100, Emilio Pozuelo Monfort wrote: > Huh, this is crashing in libc's malloc(). > > Can you run the test under valgrind's memcheck? Maybe there's some memory > corruption that would explain this. Do you mean this? valgrind the-test-that-we-want-to-debug How

Bug#847750: rmysql: FTBFS on mips64el

Hi Otto, On 12 December 2016 at 23:02, Otto Kekäläinen wrote: | Hello! | | Have you tried compiling both with libmariadb-dev and | libmariadbclient18-dev, does it fail with only with libmariadb-dev? | | The libmariadb-dev is MariaDB Connector C/C++, an improved version of | libmariadbclient18.

Bug#847750: rmysql: FTBFS on mips64el

Hello! Have you tried compiling both with libmariadb-dev and libmariadbclient18-dev, does it fail with only with libmariadb-dev? The libmariadb-dev is MariaDB Connector C/C++, an improved version of libmariadbclient18. Sometimes however the older version is better due to some rare API issues.

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

Based on the stack trace, the exception is thrown because a managed buffer that is being freed isn't actually registered to the buffer manager. This shouldn't happen, since the only way to get a buffer is to request it from the manager in the first place. It's possible there's a memory

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

On 12/12/16 21:38, Santiago Vila wrote: > 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

Bug#828387: libcrypt-openssl-rsa-perl: FTBFS with openssl 1.1.0

On 2016-11-26 16:18:44 [+0100], gregor herrmann wrote: > I also mentioned your patch in the upstream bug: > https://rt.cpan.org/Ticket/Display.html?id=117481 > which contains a different patch from Petr Písař. > > No reaction there from either Petr or the upstream authors. > I just pinged the

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

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

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

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.

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

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

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

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.

Processed: limit source to pygobject, tagging 844924

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

Processed: limit source to pygobject, tagging 844924

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)

Bug#844924: pygobject: FTBFS: Tests failures

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

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

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:

Processed: Re: Test failures

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:

Bug#834654: Test failures

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

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

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 >

Bug#844523: Debian xserver freeze

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

Processed: Re: Bug#844523: Debian xserver freeze

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

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

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

Processed: Building against openssl1.0 for the time being

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

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)

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

Bug#846649: Squeeze ?

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

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

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

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

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

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

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

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

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

Bug#847974: xmds2: FTBFS in stretch

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:

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

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

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

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

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

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

Bug#841208: fixed in monkeysphere 0.41-1

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:

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

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

Processed: sunpy FTBFS in stretch due to missing skimage

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:

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

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

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

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

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

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

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

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

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

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#846712: marked as done (gdc-6 PIE build failures)

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), PR ta

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

ibx32ubsan0 - UBSan -- undefined 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 (S

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

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:

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

32ubsan0 - UBSan -- undefined 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),

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

n -- undefined 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/

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

n -- undefined 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,

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

32ubsan0 - UBSan -- undefined 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),

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

(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++/71

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

ary 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 symbols) Closes: 845377 Changes: gcc-6 (6.2.1-6) unstable; urgency=high . * Updat

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

nitizer (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 (P

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

n -- undefined 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/785

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

32ubsan0 - UBSan -- undefined 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),

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

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

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

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:

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

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 > >

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

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: >

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

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

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

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:

Bug#847196: monit segfault on stop and start

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

Bug#847196: monit segfault on stop and start

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#845873: marked as done (mailutils: switch to build depend on the metapackage default-libmysqlclient-dev)

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

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

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

  1   2   >