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 tick

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

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 corruption

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

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

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 as done. This means that you claim tha

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 t

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

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' - trying to overwrite /usr/lib/glade/modu

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 done. This means that you claim that

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 that you claim that the problem has b

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 be marked as done. This means that you

Bug#840589: closed by Yaroslav Halchenko (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 im

Processed: Bug#840589 closed by Yaroslav Halchenko (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 be cleared, and you may n

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 Tha

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 default-libmysqlclient-dev to be marked as done. Th

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 l

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: http://bugs.debian.org/cgi-bin/bugr

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 Contact

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

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 pa

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 imp

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: http://bugs.debian.org/cgi-bin/bugreport

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

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&arch=i386&ver=0.19.1-1&stamp=1479504883 the failures are now on more arch and even with 0.19.1-3 and 0.19.1+git174-g81a2f79-1 (s

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&arch=i386&ver=0.19.1-1&stamp=1479504883 > the failures are now on more arch a

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 package 'node-mustache,rub

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 versions comgt/0.32-2. N

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

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 usi

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

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: http://bugs.debian.org/cgi-bin/bugreport

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 > /tmp/apt-dpkg-install-7sSPgR/26-manpages_4.09-1_all.deb (--unpac

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 claim that the problem has been dealt

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 ot

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 means that you claim that the problem has

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 unstable/amd6

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

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 https://wiki.debian.org/Paul

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

<    1   2