Bug#837629: marked as done (u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate)

Your message dated Mon, 24 Oct 2016 05:50:41 + with message-id and subject line Bug#837629: fixed in u-boot 2016.09+dfsg1-2 has caused the Debian Bug report #837629, regarding u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate to be marked as done. This

Bug#812303: synergy: diff for NMU version 1.4.16-1.1

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

Processed: synergy: diff for NMU version 1.4.16-1.1

Processing control commands: > tags 812303 + patch Bug #812303 [synergy] synergy: FTBFS with GCC 6: test suite segfaults Added tag(s) patch. > tags 812303 + pending Bug #812303 [synergy] synergy: FTBFS with GCC 6: test suite segfaults Added tag(s) pending. -- 812303:

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

Hi Russell, > I think that preventing random failures from Debian build infrastructure > is the best I can do for the time being Well, not if the upstream library code itself is broken wrt to the timezones and its not just some peculiarity of the test. In fact, if the code is broken then

Bug#837854: marked as done (jana: FTBFS due to undeclared build dependencies)

Your message dated Mon, 24 Oct 2016 05:18:35 + with message-id and subject line Bug#837854: fixed in jana 0.0.0+git20091215.9ec1da8a-4 has caused the Debian Bug report #837854, regarding jana: FTBFS due to undeclared build dependencies to be marked as

Bug#841879: freetennis: FTBFS: libasmrun.a(backtrace.o): relocation R_X86_64_32 against symbol `caml_backtrace_last_exn' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld:

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

Bug#841880: virt-top: FTBFS: libasmrun.a(backtrace.o): relocation R_X86_64_32 against symbol `caml_backtrace_last_exn' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: fi

Source: virt-top Version: 1.0.7-1.1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, virt-top fails to build from source in unstable/amd64:

Bug#841867: marked as done (dgit cannot cope with some patches because it uses gbp-pq)

Your message dated Mon, 24 Oct 2016 05:07:35 + with message-id and subject line Bug#841867: fixed in dgit 2.7 has caused the Debian Bug report #841867, regarding dgit cannot cope with some patches because it uses gbp-pq to be marked as done. This means

Bug#812303:

This is an issue with the gmock-1.6.0 and gtest-1.6.0 test suite. I have created a patch to build against Debian's google-mock and libgtest-dev packages instead which will fix the issue. This also requires synergy's build dependencies to be updated to depend on google-mock and libgtest-dev. I

Processed: tagging 837489, owner 837489

Processing commands for cont...@bugs.debian.org: > tags 837489 + pending Bug #837489 [src:antlr] antlr: Please build libantlr.a with -fPIC Added tag(s) pending. > owner 837489 tmanc...@debian.org Bug #837489 [src:antlr] antlr: Please build libantlr.a with -fPIC Owner recorded as

Bug#837854: jana: FTBFS due to undeclared build dependencies

I'll fix this soon. -- PaulLiu (劉穎駿) E-mail: Ying-Chun Liu (PaulLiu) diff -Nru jana-0.0.0+git20091215.9ec1da8a/debian/changelog jana-0.0.0+git20091215.9ec1da8a/debian/changelog --- jana-0.0.0+git20091215.9ec1da8a/debian/changelog 2013-09-22

Processed: Re: Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

Processing commands for cont...@bugs.debian.org: > tags 831211 pending Bug #831211 [src:ucommon] ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 831211:

Bug#840728: marked as pending

tag 840728 pending thanks Hello, Bug #840728 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-opensc/libp11.git;a=commitdiff;h=9e2a79f --- commit

Processed: Bug#840728 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 840728 pending Bug #840728 {Done: Eric Dorland } [src:libp11] libp11: FTBFS: openssl-1.0.2/engines: No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

Control: severity -1 important Control: tag -1 moreinfo On Sun, 2016-10-23 at 22:17 +0200, Petra Ruebe-Pugliese wrote: > Package: src:linux > Version: 4.7.8-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > when performing this week's regular update on my

Processed: Re: Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

Processing control commands: > severity -1 important Bug #841850 [src:linux] linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41 Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #841850 [src:linux] linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on

Bug#841867: dgit cannot cope with some patches because it uses gbp-pq [and 1 more messages]

Ian Jackson writes ("dgit cannot cope with some patches because it uses gbp-pq"): > gbp pq cannot cope with all patches that dpkg-source can, because it > uses git-apply and git-apply is not very compatible. > > At the moment, this means that `dgit clone glibc' fails: ... > I think I need to

Processed: Re: Bug#841768: mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

Processing control commands: > tags -1 + wontfix Bug #841768 [src:mtasc] mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC Added tag(s) wontfix. -- 841768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841768 Debian Bug

Bug#841768: mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

Control: tags -1 + wontfix On Sun, 2016-10-23 at 11:56 +0100, Chris Lamb wrote: > mtasc fails to build from source in unstable/amd64: Sounds like the recent GCC changes broke ocaml. In either case, this won't be fixed in mtasc, because I want to remove it from Debian because it is obsoleted by

Bug#837663: [Pkg-kannel-devel] Bug#837663: Only a binNMU is required for kannel-dev

Quoting Adrian Bunk (2016-10-23 20:32:23) > Control: retitle -1 kannel-dev: libgwlib.a needs binNMU rebuild with MySQL > 5.7 and -fPIE > Control: severity -1 serious > Control: affects -1 = src:kannel-sqlbox > > Two issues appeared in unstable: > - MySQL 5.7 removes -lmysqlclient_r, which breaks

Bug#812532: marked as done (files with the same name installed in / and /usr)

Your message dated Sun, 23 Oct 2016 23:48:44 + with message-id and subject line Bug#812532: fixed in yp-tools 3.3-5 has caused the Debian Bug report #812532, regarding files with the same name installed in / and /usr to be marked as done. This means that

Bug#817733: marked as done (xkbset: Removal of debhelper compat 4)

Your message dated Sun, 23 Oct 2016 23:48:21 + with message-id and subject line Bug#817733: fixed in xkbset 0.5-5.2 has caused the Debian Bug report #817733, regarding xkbset: Removal of debhelper compat 4 to be marked as done. This means that you claim

Bug#840230: marked as done (When installing to rootfs on LVM, an empty subvol= is appended to rootflags)

Your message dated Sun, 23 Oct 2016 23:49:06 + with message-id and subject line Bug#840230: fixed in zipl-installer 0.0.35 has caused the Debian Bug report #840230, regarding When installing to rootfs on LVM, an empty subvol= is appended to rootflags to

Bug#837712: marked as done (xemacs21: FTBFS with bindnow and PIE enabled)

Your message dated Sun, 23 Oct 2016 23:48:15 + with message-id and subject line Bug#837712: fixed in xemacs21 21.4.24-4 has caused the Debian Bug report #837712, regarding xemacs21: FTBFS with bindnow and PIE enabled to be marked as done. This means that

Bug#817742: marked as done (yaret: Removal of debhelper compat 4)

Your message dated Sun, 23 Oct 2016 23:48:33 + with message-id and subject line Bug#817742: fixed in yaret 2.1.0-5.1 has caused the Debian Bug report #817742, regarding yaret: Removal of debhelper compat 4 to be marked as done. This means that you claim

Bug#839306: marked as done (translate-toolkit: FTBFS: Tests failures)

Your message dated Sun, 23 Oct 2016 23:46:28 + with message-id and subject line Bug#839306: fixed in translate-toolkit 2.0.0~b5-2 has caused the Debian Bug report #839306, regarding translate-toolkit: FTBFS: Tests failures to be marked as done. This means

Bug#841759: marked as done (smarty-gettext : Depends: php7-cli but it is not installable)

Your message dated Sun, 23 Oct 2016 23:44:57 + with message-id and subject line Bug#841759: fixed in smarty-gettext 1.4.0-2 has caused the Debian Bug report #841759, regarding smarty-gettext : Depends: php7-cli but it is not installable to be marked as

Bug#841713: marked as done (tunnelx: FTBFS with dpkg-buildpackage -A (chown error))

Your message dated Sun, 23 Oct 2016 23:46:33 + with message-id and subject line Bug#841713: fixed in tunnelx 20160713-2 has caused the Debian Bug report #841713, regarding tunnelx: FTBFS with dpkg-buildpackage -A (chown error) to be marked as done. This

Bug#831093: marked as done (qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing conversion of ''\37777777600'' from 'char' to 'uchar {aka unsigned char}' inside { } [-Wnarrowing])

Your message dated Sun, 23 Oct 2016 23:43:07 + with message-id and subject line Bug#831093: fixed in qterm 1:0.5.12-1.2 has caused the Debian Bug report #831093, regarding qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing conversion of

Bug#817627: marked as done (poster: Removal of debhelper compat 4)

Your message dated Sun, 23 Oct 2016 23:34:01 + with message-id and subject line Bug#817627: fixed in poster 1:20050907-1.1 has caused the Debian Bug report #817627, regarding poster: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#817613: marked as done (outguess: Removal of debhelper compat 4)

Your message dated Sun, 23 Oct 2016 23:31:33 + with message-id and subject line Bug#817613: fixed in outguess 1:0.2-7.1 has caused the Debian Bug report #817613, regarding outguess: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#824825: marked as done (liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm)

Your message dated Sun, 23 Oct 2016 23:27:23 + with message-id and subject line Bug#824825: fixed in lxqt-l10n 0.11.0-19-g717bd7e-4 has caused the Debian Bug report #824825, regarding liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

Yeah, I totally agree it's an upstream bug, the bug exists in not only this version but also the master branch so I can't backport a fix. I did have a quick look at the test code, and it's not obviously due to that, so it must be related to how they store or retrieve the offset in this case.

Bug#841442: marked as done (lintian: FTBFS: fail tests::shared-libs-non-pic-i386)

Your message dated Sun, 23 Oct 2016 23:21:13 + with message-id and subject line Bug#841442: fixed in lintian 2.5.49 has caused the Debian Bug report #841442, regarding lintian: FTBFS: fail tests::shared-libs-non-pic-i386 to be marked as done. This means

Bug#841625: marked as done (gupnp-tools: FTBFS: playlist-treeview.h:35:34: error: unknown type name 'GUPnPDeviceProxy')

Your message dated Sun, 23 Oct 2016 23:02:04 + with message-id and subject line Bug#841625: fixed in gupnp-tools 0.8.12-2 has caused the Debian Bug report #841625, regarding gupnp-tools: FTBFS: playlist-treeview.h:35:34: error: unknown type name

Bug#837568: marked as done (libctl-dev: Please build libctlgeom.a with -fPIC)

Your message dated Sun, 23 Oct 2016 23:10:56 + with message-id and subject line Bug#837568: fixed in libctl 3.2.2-3 has caused the Debian Bug report #837568, regarding libctl-dev: Please build libctlgeom.a with -fPIC to be marked as done. This means that

Bug#841707: marked as done (eximdoc4: FTBFS with bash as /bin/sh)

Your message dated Sun, 23 Oct 2016 22:44:56 + with message-id and subject line Bug#841707: fixed in eximdoc4 4.87-2 has caused the Debian Bug report #841707, regarding eximdoc4: FTBFS with bash as /bin/sh to be marked as done. This means that you claim

Bug#841082: marked as done (epiphany-browser: bump dependency on epiphany-browser-data)

Your message dated Sun, 23 Oct 2016 22:44:29 + with message-id and subject line Bug#841082: fixed in epiphany-browser 3.22.1-2 has caused the Debian Bug report #841082, regarding epiphany-browser: bump dependency on epiphany-browser-data to be marked as

Bug#817354: marked as done (aspell-br: Removal of debhelper compat 4)

Your message dated Sun, 23 Oct 2016 22:32:11 + with message-id and subject line Bug#817354: fixed in aspell-br 0.50-2-6.1 has caused the Debian Bug report #817354, regarding aspell-br: Removal of debhelper compat 4 to be marked as done. This means that

Bug#841064: marked as done (awscli: FTBFS: ImportError: No module named 's3transfer')

Your message dated Sun, 23 Oct 2016 22:32:29 + with message-id and subject line Bug#841064: fixed in awscli 1.11.7-2 has caused the Debian Bug report #841064, regarding awscli: FTBFS: ImportError: No module named 's3transfer' to be marked as done. This

Bug#841867: dgit cannot cope with some patches because it uses gbp-pq

Package: dgit Version: 2.6 Severity: serious gbp pq cannot cope with all patches that dpkg-source can, because it uses git-apply and git-apply is not very compatible. At the moment, this means that `dgit clone glibc' fails: gbp:error: Failed to apply

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

Package: ardour Version: 1:5.4.0~dfsg-1 Severity: grave Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to load any project. I am attaching a gdb run (from 1:5.4.0~dfsg-1). -- System

Bug#841548: marked as done (autopkgtest: FTBFS: Tests failures)

Your message dated Sun, 23 Oct 2016 21:28:50 + with message-id and subject line Bug#841548: fixed in wand 0.4.3-1 has caused the Debian Bug report #841548, regarding autopkgtest: FTBFS: Tests failures to be marked as done. This means that you claim that

Bug#841653: marked as done (Importing wand.image fails)

Your message dated Sun, 23 Oct 2016 21:28:50 + with message-id and subject line Bug#841548: fixed in wand 0.4.3-1 has caused the Debian Bug report #841548, regarding Importing wand.image fails to be marked as done. This means that you claim that the

Bug#839181: marked as done (transmission-remote-gtk: FTBFS: Option release requires an argument [pod2man --release=""] )

Your message dated Sun, 23 Oct 2016 21:28:06 + with message-id and subject line Bug#839181: fixed in transmission-remote-gtk 1.3.1-1 has caused the Debian Bug report #839181, regarding transmission-remote-gtk: FTBFS: Option release requires an argument

Bug#830392: marked as done (oidua: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

Your message dated Sun, 23 Oct 2016 21:22:14 + with message-id and subject line Bug#830392: fixed in oidua 0.16.1-8 has caused the Debian Bug report #830392, regarding oidua: FTBFS: dh_clean: Please specify the compatibility level in debian/compat to be

Bug#840728: marked as done (libp11: FTBFS: openssl-1.0.2/engines: No such file or directory)

Your message dated Sun, 23 Oct 2016 21:19:29 + with message-id and subject line Bug#840728: fixed in libp11 0.4.2-1 has caused the Debian Bug report #840728, regarding libp11: FTBFS: openssl-1.0.2/engines: No such file or directory to be marked as done.

Bug#841443: marked as done (hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h)

Your message dated Sun, 23 Oct 2016 21:18:56 + with message-id and subject line Bug#841443: fixed in libcrypto++ 5.6.4-2 has caused the Debian Bug report #841443, regarding hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h to be marked as

Bug#840841: marked as done (digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded)

Your message dated Sun, 23 Oct 2016 21:09:58 + with message-id and subject line Bug#841751: fixed in digikam 4:5.2.0-2 has caused the Debian Bug report #841751, regarding digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded to be

Bug#840841: marked as done (digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded)

Your message dated Sun, 23 Oct 2016 21:09:58 + with message-id and subject line Bug#840841: fixed in digikam 4:5.2.0-2 has caused the Debian Bug report #840841, regarding digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded to be

Bug#841751: marked as done (digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25)

Your message dated Sun, 23 Oct 2016 21:09:58 + with message-id and subject line Bug#841751: fixed in digikam 4:5.2.0-2 has caused the Debian Bug report #841751, regarding digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25 to be marked as done. This

Bug#841751: marked as done (digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25)

Your message dated Sun, 23 Oct 2016 21:09:58 + with message-id and subject line Bug#840841: fixed in digikam 4:5.2.0-2 has caused the Debian Bug report #840841, regarding digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25 to be marked as done. This

Processed: This is the same bug

Processing commands for cont...@bugs.debian.org: > reassign 841757 src:check Bug #841757 [src:mpc] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC Bug reassigned from package 'src:mpc' to 'src:check'. No longer marked as

Bug#841665: marked as done (boinc-client: The boinc-client init script has a badly constructed parameter for xhost)

Your message dated Sun, 23 Oct 2016 20:58:09 + with message-id and subject line Bug#841665: fixed in boinc 7.6.33+dfsg-2 has caused the Debian Bug report #841665, regarding boinc-client: The boinc-client init script has a badly constructed parameter for

Processed: Re: roboptim-core: FTBFS: dh_install: libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), aborting

Processing control commands: > tags -1 + patch Bug #808455 [src:roboptim-core] roboptim-core: FTBFS: dh_install: libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), aborting Added tag(s) patch. -- 808455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808455

Bug#808455: roboptim-core: FTBFS: dh_install: libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*), aborting

Control: tags -1 + patch [Chris Lamb 2015-12-20] > roboptim-core fails to build from source in unstable/amd64: It still fail to build. > dh_install: libroboptim-core2-plugin-base missing files > (usr/lib/*/roboptim-core/*.so.2*), aborting > debian/rules:26: recipe for target 'binary'

Bug#840853: Reassign

* Neil Williams: > The requirement for linuxboot_dma.bin is specific to QEMU 2.7 and is > not provided by the seabios package (which provides linuxboot_dma.bin). > As a workaround, symlinking linuxboot_dma.bin as linuxboot.bin > in /usr/share/seabios/ allows the guestfs operations to proceed.

Processed: Bug#841625 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 841625 pending Bug #841625 [src:gupnp-tools] gupnp-tools: FTBFS: playlist-treeview.h:35:34: error: unknown type name 'GUPnPDeviceProxy' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#841625: marked as pending

tag 841625 pending thanks Hello, Bug #841625 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-gnome/gupnp-tools.git;a=commitdiff;h=d756041 --- commit

Bug#841850: linux-image-4.7.0-1-686_4.7.8-1_i386.deb does not boot on Thinkpad T41

Package: src:linux Version: 4.7.8-1 Severity: critical Justification: breaks the whole system Dear Maintainer, when performing this week's regular update on my Debian Testing systems, linux-image-4.7.0-1-686 was updated from 4.7.6-1 to 4.7.8-1_i386.deb on two Thinkpads T41. On both of them, the

Bug#838897: jitsi: Replace the glassfish dependencies

On Mon, 26 Sep 2016 10:43:42 +0200 Emmanuel Bourg wrote: > jitsi still depends on glassfish-activation and glassfish-mail which are going > to be removed. glassfish-activation can be safely removed (the API has been > integrated to the standard JDK) and glassfish-mail should be

Bug#837658: libfl_pic.a needs more than a binNMU

Control: retitle 837658 libfl_pic.a is not compiled with -fPIC #837658 is different from many other PIE issues: This is a _pic.a library that includes the non-PIC objects instead of the PIC objects it should contain. A binNMU with -fPIE would not fix the root cause that this library is

Processed: libfl_pic.a needs more than a binNMU

Processing control commands: > retitle 837658 libfl_pic.a is not compiled with -fPIC Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be used when making a shared

Processed: Fix for the qterm FTBFS

Processing control commands: > tags -1 +patch Bug #831093 [src:qterm] qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing conversion of ''\3777600'' from 'char' to 'uchar {aka unsigned char}' inside { } [-Wnarrowing] Added tag(s) patch. -- 831093:

Bug#831093: Fix for the qterm FTBFS

Control: tags -1 +patch What broke the build is that gcc 6 changed the default C++ standard from C++98 to C++14. Not all valid C++98 code is also valid C++11 and C++14 code. Note that this just changed the default, when told to process C++98 code gcc 6 does not differ in any significant way

Bug#841635: marked as done (kannel-sqlbox: FTBFS: Kannel gwlib is required)

Your message dated Sun, 23 Oct 2016 22:10:45 +0300 with message-id <20161023191045.qjocu2psij7od...@bunk.spdns.de> and subject line Re: Bug#828362: Acknowledgement (kannel-sqlbox: FTBFS with openssl 1.1.0) has caused the Debian Bug report #841635, regarding kannel-sqlbox: FTBFS: Kannel gwlib is

Bug#841844: libtesseract3: shared data files shipped in shared library package

Package: libtesseract3 Version: 3.04.01-4.1 Severity: serious Justification: Debian Policy section 8.2 libtesseract3 includes data files in /usr/share/tesseract-ocr/tessdata. That filename is not versioned. After a soname bump, the new library package will thus conflict with libtesseract3. Such

Bug#811808: ns2: diff for NMU version 2.35+dfsg-2.1

Control: tags 727930 + patch Control: tags 727930 + pending Control: tags 811808 + patch Control: tags 811808 + pending Dear maintainer, I've prepared an NMU for ns2 (versioned as 2.35+dfsg-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. --

Processed: ns2: diff for NMU version 2.35+dfsg-2.1

Processing control commands: > tags 727930 + patch Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4 Ignoring request to alter tags of bug #727930 to the same tags previously set > tags 727930 + pending Bug #727930 [src:ns2] ns2: run dh-autoreconf

Processed: ns2: diff for NMU version 2.35+dfsg-2.1

Processing control commands: > tags 727930 + patch Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4 Added tag(s) patch. > tags 727930 + pending Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4

Processed: Only a binNMU is required for kannel-dev

Processing control commands: > retitle -1 kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 5.7 and > -fPIE Bug #837663 [kannel-dev] kannel-dev: Please build libgwlib.a with -fPIC Changed Bug title to 'kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 5.7 and -fPIE' from 'kannel-dev:

Processed: severity of 838897 is serious

Processing commands for cont...@bugs.debian.org: > severity 838897 serious Bug #838897 [src:jitsi] jitsi: Replace the glassfish dependencies Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 838897:

Bug#837490: libpapyrus3-dev: Please build libPapyrus3.a with -fPIC

On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote: > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libPapyrus3.a(PapyError3.c.o): > relocation > R_X86_64_32 against `.rodata.str1.8' can not be used when making a > shared object; recompile with -fPIC > ... The Ubuntu

Processed: Add tags

Processing commands for cont...@bugs.debian.org: > tags 804442 + pending Bug #804442 [src:python-memory-profiler] python-memory-profiler: FTBFS: NameError: name 'profile' is not defined Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#837490: libpapyrus3-dev: Please build libPapyrus3.a with -fPIC

On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote: > During a rebuild of all packages in sid, gdcm > failed to build on amd64 with patched GCC and dpkg. The root > cause seems to be that libPapyrus3.a is shipped as a non-PIC library. That cannot be the root cause. Debian Policy [1]

Processed: Re: [Debian-med-packaging] Bug#834856: python-pysam fails to build on mips64el arch.: failed test

Processing control commands: > severity -1 important Bug #834856 [python-pysam] python-pysam fails to build on mips64el arch.: failed test Severity set to 'important' from 'serious' > retitle -1 python-pysam: FTBFS on 32-bit architectures: segmentation fault in > testsuite Bug #834856

Bug#834856: [Debian-med-packaging] Bug#834856: python-pysam fails to build on mips64el arch.: failed test

control: severity -1 important control: retitle -1 python-pysam: FTBFS on 32-bit architectures: segmentation fault in testsuite On 2016-10-23 12:25, Emilio Pozuelo Monfort wrote: > On 23/10/16 00:48, Aurelien Jarno wrote: > > On 2016-10-21 15:15, James Cowgill wrote: > >> On 21/10/16 14:55,

Processed: severity of 837925 is normal

Processing commands for cont...@bugs.debian.org: > severity 837925 normal Bug #837925 {Done: Marco d'Itri } [usrmerge] usrmerge: fails to merge with molly-guard installed Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need

Processed: Re: Bug#837925: usrmerge: fails to merge with molly-guard installed

Processing control commands: > severity -1 grave Bug #837928 [molly-guard] usrmerge: fails to merge with molly-guard installed Severity set to 'grave' from 'important' -- 837928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837928 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#841759: smarty-gettext : Depends: php7-cli but it is not installable

> The following packages have unmet dependencies: > smarty-gettext : Depends: php7-cli but it is not installable > E: Unable to correct problems, you have held broken packages. should either be php-cli (as it has been before, prefered) or php7.0-cli. Wolfgang signature.asc Description:

Processed: Re: Bug#841098 closed by Andreas Henriksson <andr...@fatal.se> (Re: Bug#841098: not fixed in rygel 0.32.1-1)

Processing control commands: > reopen -1 Bug #841098 {Done: Andreas Henriksson } [src:rygel] rygel: FTBFS (rygel-media-engine-test fails) '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

Bug#841098: closed by Andreas Henriksson <andr...@fatal.se> (Re: Bug#841098: not fixed in rygel 0.32.1-1)

Control: reopen -1 Hi! On Thu, 2016-10-20 at 20:15:06 +, Debian Bug Tracking System wrote: > Date: Thu, 20 Oct 2016 22:14:11 +0200 > From: Andreas Henriksson > To: Santiago Vila > Cc: 841098-d...@bugs.debian.org > Subject: Re: Bug#841098: not fixed in

Processed (with 1 error): Re: Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

Processing commands for cont...@bugs.debian.org: > severity 841364 important Bug #841364 [clementine] clementine: no sound at all, "GStreamer encountered a general stream error." Severity set to 'important' from 'grave' > retitle 841364 clementine: unable to play anything in special Bug #841364

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

This is what I ended up doing.  Not sure if this is correct method but seems to have worked.  I can now perform an apt-get update && apt-get upgrade. sudo rm /usr/lib/go -Rf sudo rm /usr/share/doc/golang-doc/ -Rf sudo mkdir /usr/lib/go sudo apt-get -f install sudo apt-get update && apt-get

Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

severity 841364 important retitle 841364 clementine: unable to play anything in special configuration cases, "GStreamer encountered a general stream error" thanks Hi, @Adam, I tried many migrations and I still could not reproduce your bug. I still think that this is caused by a special use case

Processed: Re: vowpal-wabbit: FTBFS everywhere

Processing commands for cont...@bugs.debian.org: > retitle 836450 FTBFS: RunTests: test 5: FAILED: > ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr) Bug #836450 [src:vowpal-wabbit] vowpal-wabbit: FTBFS everywhere Changed Bug title to 'FTBFS: RunTests: test 5: FAILED:

Bug#836450: vowpal-wabbit: FTBFS everywhere

retitle 836450 FTBFS: RunTests: test 5: FAILED: ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr) thanks Looks like non-deterministic test timings...? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

What is the fix for this?  I have the same problem.  Cant update anything due to this problem.  Should any new sources be added to /etc/apt/sources.list? On Wed, 07 Sep 2016 23:18:47 +0200 Andreas Beckmann wrote: > Package: golang-doc > Version: 2:1.7~1 > Severity: serious >

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

Hi all, thanks John for the detailed explanation and the patches. >> So the real solution here is to revert your autoconf-archive to 6dc6cc5^ >> and use that unborked ax_with_curses.m4, which will in future be bundled >> with samtools. > > This should have been 0351b06^. I see. For now I have

Processed: Re: Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

Processing commands for cont...@bugs.debian.org: > forwarded 841532 https://github.com/libgit2/libgit2/issues/3970 Bug #841532 [src:libgit2] libgit2: FTBFS under some timezones (eg. GMT-14) Set Bug forwarded-to-address to 'https://github.com/libgit2/libgit2/issues/3970'. > thanks Stopping

Bug#841532: libgit2: FTBFS under some timezones (eg. GMT-14)

forwarded 841532 https://github.com/libgit2/libgit2/issues/3970 thanks Russell Sim wrote: > I have forwarded this bug report upstream > https://github.com/libgit2/libgit2/issues/3970 in the mean time I'll add > a fix to the existing package to force tests to run in GMT timezone. Be careful; it

Bug#841784: gnucash: FTBFS under some timezones (eg. GMT-14)

Source: gnucash Version: 1:2.6.13-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs timezone X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, gnucash fails to build from source in

Bug#841064: marked as pending

tag 841064 pending thanks Hello, Bug #841064 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/awscli.git;a=commitdiff;h=dfcad50 --- commit

Processed: Bug#841064 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 841064 pending Bug #841064 [src:awscli] awscli: FTBFS: ImportError: No module named 's3transfer' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 841064:

Bug#841763: unattended-upgrades: Breaks hard when apt is upgraded

Le dimanche 23 octobre 2016, 13 h 43 min 59 s CEST Santiago Vila a écrit : > Aha! I can reproduce this too. On the machines where this happens, > I believe I answered "yes" to a debconf question about restarting > services automatically (one of the times I upgraded by hand and not > using

Bug#841763: unattended-upgrades: Breaks hard when apt is upgraded

On Sun, Oct 23, 2016 at 12:08:53PM +0200, Stefan Fritsch wrote: > Package: unattended-upgrades > Version: 0.92 > Severity: grave > > Dear Maintainer, > > > When unattended-upgrades has to upgrade apt itself, it will be > terminated and leaves the system in a state that requires manual >

Bug#841769: libzypp: FTBFS: tests/zypp/Capabilities_test.cc:19:26: error: 'boost::test_tools::close_at_tolerance' has not been declared

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

Processed: bug 841110 is forwarded to https://github.com/mdadams/jasper/issues/32

Processing commands for cont...@bugs.debian.org: > forwarded 841110 https://github.com/mdadams/jasper/issues/32 Bug #841110 [src:jasper] jasper: CVE-2016-8693 Set Bug forwarded-to-address to 'https://github.com/mdadams/jasper/issues/32'. > thanks Stopping processing here. Please contact me if

Bug#841768: mtasc: FTBFS: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

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

Processed: forcibly merging 840841 841751

Processing commands for cont...@bugs.debian.org: > forcemerge 840841 841751 Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25 Bug #841751 [digikam] digikam: Rebuild

  1   2   >