Bug#833532: icedove crashes sometimes. To crash reproducibly, install calendar-google-provider

On 12.08.2016 08:56, Carsten Schoenert wrote: notfound 833532 calendar-google-provider/1:45.2.0-2 notfound 833532 iceowl-extension/1:45.2.0-2+b1 thanks The error is in the icedove package, not in any other related package from the source package. Hello Leon, On Fri, Aug 12, 2016 at 12:25:06AM

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

On Wed, Aug 10, 2016 at 11:59:14AM -0400, Joachim Breitner wrote: > we do have that for Haskell ABI changes, but I believe it does not > cover the names of shared C libraries. Maybe that can be considered a > bug, and something that can be fixed on the GHC side. If someone wants > to dig deeper,

Bug#834204: libsdl1.2: Nonfree file: src/video/fbcon/riva_mmio.h

Source: libsdl1.2 Version: 1.2.15+dfsg1-4 Severity: serious Justification: Policy 2.1 Dear Maintainer, The file src/video/fbcon/riva_mmio.h has a nonfree license that does not explicitly allow modification. The file is from xf86-video-nv, and has subsequently been relicensed under the MIT/Expat

Bug#834175: digikam: please depend on the default version of boost

Hi, I'll switch it back shortly. On Friday, August 12, 2016 7:37:33 PM CDT Mattia Rizzolo wrote: > for some reason you swapped your build-dependency on the metapackage > libboost-graph-dev to the versioned libboost-graph1.60-dev. Here's the story: I worked on digikam 5.0.0 a month ago, when

Bug#834201: ImportError: No module named '_xapian'

Package: python3-xapian Version: 1.4.0-2 Severity: grave Justification: renders package unusable I run into the following ImportError when I try to import the python3 xapian module: servo:~ 0$ python3 -c 'import xapian' Traceback (most recent call last): File "", line 1, in File

Bug#834195: unzip: recmatch in match.c has nonfree license

Package: unzip Version: 6.0-16+deb8u2 Severity: serious Justification: Policy 2.1 Dear Maintainer, The function recmatch in match.c has the following nonfree license, which forbids selling for profit: Copyright (C) 1990-1992 Mark Adler, Richard B. Wales, Jean-loup Gailly, Kai Uwe

Bug#789381: libpoe-api-peek-perl: FTBFS with perl 5.22: test failures

On Mon, 01 Aug 2016 08:57:07 -0300, Prof. Ernesto Hernández-Novich wrote: > On Sat, 30 Jul 2016 14:35:09 +0200 intrigeri wrote: > > A month later: any update on this side? > Nothing. webgui was removed from the archive. RoQA, #834084. Cheers, gregor -- .''`.

Bug#811984: marked as done (qscintilla2: FTBFS with GCC 6: symbol changes)

Your message dated Fri, 12 Aug 2016 22:31:47 + with message-id and subject line Bug#811984: fixed in qscintilla2 2.9.3+dfsg-2 has caused the Debian Bug report #811984, regarding qscintilla2: FTBFS with GCC 6: symbol changes to be marked as done. This

Bug#806606: marked as done (basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

Your message dated Fri, 12 Aug 2016 22:22:05 + with message-id and subject line Bug#806606: fixed in basemap 1.0.7+dfsg-3.1 has caused the Debian Bug report #806606, regarding basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On Aug 12, 2016, at 9:21 AM, Pete Batard wrote: > Okay. I have now gone through a dpkg -i install of all the (non dbgsym) .deb > I see on your server, and also issued a reboot for good measure, but I still > see the same problem with journald being failed, along with dependent

Bug#834169: marked as done (Apache2 can't be installed on testing/sid)

Your message dated Fri, 12 Aug 2016 22:21:29 + with message-id and subject line Bug#834169: fixed in apache2 2.4.23-4 has caused the Debian Bug report #834169, regarding Apache2 can't be installed on testing/sid to be marked as done. This means that you

Bug#833760: cufflinks: please use the default boost version

On Fri, Aug 12, 2016 at 10:59:11PM +0200, Andreas Tille wrote: > Sorry, this does not help. There is this large thread on > debian-devel[2] which I triggered and which IMHO goes totally in the > wrong direction nitpicking about copyrights inside binary packages which > is IMHO orthogonal to the

Bug#834189: php-common: php-maintscript-helper loses admin changes on package reinstall/upgrade

duplicate of #831807? Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature

Bug#806606: basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

On 08/12/2016 11:30 PM, Sebastiaan Couwenberg wrote: > On 08/12/2016 11:25 PM, Sandro Tosi wrote: >> please remove the upload, or move it to a longer wait queue, i'll deal >> with it this weekend > > Thanks for the feedback, I've rescheduled the upload to DELAYED/5. The changes file hasn't been

Bug#806606: basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

On 08/12/2016 11:25 PM, Sandro Tosi wrote: > please remove the upload, or move it to a longer wait queue, i'll deal > with it this weekend Thanks for the feedback, I've rescheduled the upload to DELAYED/5. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056

Processed: Re: basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Processing control commands: > tags -1 pending Bug #806606 [src:basemap] basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) pending. -- 806606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806606 Debian Bug Tracking System Contact

Bug#834189: php-common: php-maintscript-helper loses admin changes on package reinstall/upgrade

Package: php-common Version: 1:42 Severity: serious Justification: Policy 10.7.3 Policy says: local changes must be preserved during a package upgrade. And yet: % ls -l /etc/php/7.0/cli/conf.d/20-xdebug.ini lrwxrwxrwx 1 root root 38 Aug 12 16:15 /etc/php/7.0/cli/conf.d/20-xdebug.ini ->

Bug#806606: basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

please remove the upload, or move it to a longer wait queue, i'll deal with it this weekend On Fri, Aug 12, 2016 at 10:24 PM, Sebastiaan Couwenberg wrote: > Control: tags -1 pending > > Hi Sandro, > > On 08/02/2016 02:08 PM, Sebastiaan Couwenberg wrote: >> Because this RC bug

Bug#806606: basemap: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Control: tags -1 pending Hi Sandro, On 08/02/2016 02:08 PM, Sebastiaan Couwenberg wrote: > Because this RC bug is threatening the removal of several reverse > dependencies I had a look at fixing it. The attached patch adds the > build-arch target to the build-indep target dependencies to have

Bug#811984: marked as pending

tag 811984 pending thanks Hello, Bug #811984 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/qscintilla2.git;a=commitdiff;h=443de8c --- commit

Processed: tagging 811984

Processing commands for cont...@bugs.debian.org: > tags 811984 + pending Bug #811984 [qscintilla2] qscintilla2: FTBFS with GCC 6: symbol changes Ignoring request to alter tags of bug #811984 to the same tags previously set > thanks Stopping processing here. Please contact me if you need

Processed: Bug#811984 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 811984 pending Bug #811984 [qscintilla2] qscintilla2: FTBFS with GCC 6: symbol changes Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 811984:

Bug#833760: cufflinks: please use the default boost version

Hi Mattia, On Fri, Aug 12, 2016 at 07:33:06PM +, Mattia Rizzolo wrote: > Hi Andreas! :) > > On Mon, Aug 08, 2016 at 04:54:08PM +0200, Andreas Tille wrote: > > Currently I can't upload since > > cufflinks does not build. If the new version of liblemon would not have > > been rejected by

Bug#834187: libcereal: FTBFS: print_helper.hpp:47:5: error: static assertion failed: Type has to implement operator<< to be printable

Source: libcereal Version: 1.1.2-4 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, libcereal fails to build from source in unstable/amd64:

Bug#828178: afl: FTBFS: clang error unknown argument -fdebug-prefix-map=/build/afl-2.16b=.'

On Fri, Aug 12, 2016 at 01:55:50PM -0400, Daniel Kahn Gillmor wrote: > On Fri 2016-08-12 13:22:21 -0400, Santiago Vila wrote: > > On Mon, 27 Jun 2016, Daniel Kahn Gillmor wrote: > >> I think clang introduced -fdebug-prefix-map in 3.8.0 (see > >> https://bugs.debian.org/819185) and afl

Bug#834188: qsapecng: FTBFS: type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"

Source: qsapecng Version: 2.0.0-8 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, qsapecng fails to build from source in unstable/amd64:

Bug#834186: cpp-netlib: FTBFS: 94% tests passed, 1 tests failed out of 17

Source: cpp-netlib Version: 0.11.2+dfsg1-2 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, cpp-netlib fails to build from source in

Processed: found 834183 in 8:6.7.7.10-4

Processing commands for cont...@bugs.debian.org: > found 834183 8:6.7.7.10-4 Bug #834183 [src:imagemagick] Double free Marked as found in versions imagemagick/8:6.7.7.10-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 834183:

Bug#834035: kdb5_util hangs forever

On Thu, 11 Aug 2016, Greg Hudson wrote: > I do not understand the kernel behavior reflected in this trace > output. For fd 3 (principal.ok), we see: Yes, it would be good to get the kernel version from the reporter on the affected machine (and the unaffected ones, too, for comparison). (Using

Bug#826300: Share knowledge on fpc and powerpc issue

Hi Adam, During Debconf you found out what the issue was with fpc on powerpc (glibc update related). We haven't seen a solution yet (I expect you are too busy), but could you at least share your current knowledge such that others could investigate further and e.g. check that upstream doesn't

Bug#834183: Double free

Package: src:imagemagick Version: 8:6.7.7.10-5 Severity: grave Tags: patch security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org forwarded: https://www.imagemagick.org/discourse-server/viewtopic.php?f=3=30245 Double free in pwp file. Fixed by commit

Bug#834180: bristol: FTBFS: audioEngineJack.c:42:26: fatal error: alsa/iatomic.h: No such file or directory

Source: bristol Version: 0.60.11-2 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, bristol fails to build from source in unstable/amd64:

Processed: digikam: please depend on the default version of boost

Processing control commands: > block 833757 by -1 Bug #833757 [ftp.debian.org] RM: boost1.60 -- RoQA; superseded by boost1.61 833757 was blocked by: 833760 833759 833758 833757 was not blocking any bugs. Added blocking bug(s) of 833757: 834175 -- 833757:

Bug#834175: digikam: please depend on the default version of boost

source: digikam version: 4:5.1.0-1 severity: serious control: block 833757 by -1 Dear maintainer, for some reason you swapped your build-dependency on the metapackage libboost-graph-dev to the versioned libboost-graph1.60-dev. This is causing us some problems now as we don't want to release

Processed: bug#828853 affects all arches

Processing commands for cont...@bugs.debian.org: > retitle 828853 libexplain: FTBFS - 'FS_ECOMPR_FL' undeclared Bug #828853 [libexplain] libexplain: FTBFS on mips and mipsel - 'FS_ECOMPR_FL' undeclared Changed Bug title to 'libexplain: FTBFS - 'FS_ECOMPR_FL' undeclared' from 'libexplain: FTBFS

Bug#833760: cufflinks: please use the default boost version

Hi Andreas! :) On Mon, Aug 08, 2016 at 04:54:08PM +0200, Andreas Tille wrote: > > We would like to remove 1.60, so please either bump the dependency to > > 1.61 or (preferred) use the unversioned stuff as provided by > > src:boost-defaults. > > Currently I can't upload since > cufflinks does not

Bug#826806: ants: diff for NMU version 2.1.0-4.3

If it builds, awesome, no need to delay On August 11, 2016 7:12:17 AM EDT, Mattia Rizzolo wrote: >Control: tags 826806 + patch >Control: tags 826806 + pending > >Dear maintainer, > >I've prepared an NMU for ants (versioned as 2.1.0-4.3) and >uploaded it to DELAYED/2. Please

Bug#828178: afl: FTBFS: clang error unknown argument -fdebug-prefix-map=/build/afl-2.16b=.'

On Fri 2016-08-12 13:22:21 -0400, Santiago Vila wrote: > On Mon, 27 Jun 2016, Daniel Kahn Gillmor wrote: >> I think clang introduced -fdebug-prefix-map in 3.8.0 (see >> https://bugs.debian.org/819185) and afl build-depends on clang-3.7. >> >> I assume that it's the reproducible-builds toolchain

Bug#826806: marked as done (ants: OpenJPEG removal)

Your message dated Fri, 12 Aug 2016 19:18:46 + with message-id and subject line Bug#826806: fixed in ants 2.1.0+git635-g0752c29-1.1 has caused the Debian Bug report #826806, regarding ants: OpenJPEG removal to be marked as done. This means that you claim

Bug#826806: marked as done (ants: OpenJPEG removal)

Your message dated Fri, 12 Aug 2016 19:18:40 + with message-id and subject line Bug#826806: fixed in ants 2.1.0-4.3 has caused the Debian Bug report #826806, regarding ants: OpenJPEG removal to be marked as done. This means that you claim that the problem

Bug#834161: marked as done (mksh: /= operator has vanished)

Your message dated Fri, 12 Aug 2016 19:04:48 + with message-id and subject line Bug#834161: fixed in mksh 53a-1 has caused the Debian Bug report #834161, regarding mksh: /= operator has vanished to be marked as done. This means that you claim that the

Processed: tagging 834161

Processing commands for cont...@bugs.debian.org: > tags 834161 + pending Bug #834161 [mksh] mksh: /= operator has vanished Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 834161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834161 Debian

Bug#830318: marked as pending

tag 830318 pending thanks Hello, Bug #830318 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/django-uwsgi.git;a=commitdiff;h=a0b70a9 --- commit

Bug#830326: marked as pending

tag 830326 pending thanks Hello, Bug #830326 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/django-uwsgi.git;a=commitdiff;h=a0b70a9 --- commit

Processed: Bug#830326 marked as pending

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

Processed: Bug#830318 marked as pending

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

Bug#833591: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833698: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833698, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833934: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833698: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833698, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833698: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833698: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833698, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833635: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833698: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833698, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833934: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833635: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833635, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833698: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833635: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833635, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833532: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833698: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833698, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833635: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833591: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833591, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833591: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833591: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833591, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833635: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833635: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833635, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833532: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833591: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833591, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833934: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:58 + with message-id and subject line Bug#833532: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833532, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833591: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833635: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833635, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833934: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833591: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833591, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833532: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833635: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833635, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833698: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:59 + with message-id and subject line Bug#833591: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833591, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833635: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:58 + with message-id and subject line Bug#833532: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833532, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833532: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:58 + with message-id and subject line Bug#833532: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833532, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833698: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:58 + with message-id and subject line Bug#833532: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833532, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#833591: marked as done ("iceowl-extension causes icedove to segfault")

Your message dated Fri, 12 Aug 2016 18:25:58 + with message-id and subject line Bug#833532: fixed in icedove 1:45.2.0-3 has caused the Debian Bug report #833532, regarding "iceowl-extension causes icedove to segfault" to be marked as done. This means that

Bug#830471: Fixed in 4.6.7-1

found 830471 4.6.7-1 thanks Still FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/metview.html

Processed: Re: Fixed in 4.6.7-1

Processing commands for cont...@bugs.debian.org: > found 830471 4.6.7-1 Bug #830471 {Done: Alastair McKinstry } [src:metview] metview: FTBFS: TeDefines.h:208:11: error: '::isnan' has not been declared Marked as found in versions metview/4.6.7-1 and reopened. >

Processed: Bug#811844

Processing commands for cont...@bugs.debian.org: > found 811844 0.006.2+dfsg0-5 Bug #811844 {Done: Jaromír Mikeš } [composite] composite: FTBFS with GCC 6: no match for Marked as found in versions composite/0.006.2+dfsg0-5; no longer marked as fixed in versions

Bug#811844: fixed in composite 0.006.2+dfsg0-5

found -1 0.006.2+dfsg0-5 thanks Still FTBFS: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/composite_0.006.2+dfsg0-5.rbuild.log Thanks.

Bug#811987: fixed in ceres-solver 1.11.0~dfsg0-4

found 811987 1.11.0~dfsg0-5 thanks Still FTBFS: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.rbuild.log Thanks.

Processed: Re: Bug#811987: fixed in ceres-solver 1.11.0~dfsg0-4

Processing commands for cont...@bugs.debian.org: > found 811987 1.11.0~dfsg0-5 Bug #811987 {Done: Philipp Huebner } [ceres-solver] ceres-solver: FTBFS with GCC 6: the compiler can assume... There is no source info for the package 'ceres-solver' at version '1.11.0~dfsg0-5'

Bug#834161: /= operator vanished in mksh R53 (patch)

Dominik George dixit: >The bug is a simple typo in the new exprtok.h - it seems to have slipped in >while refactoring the operator list to this new header file. Indeed. Fixed: >Commit ID: 10057ADFDDA517E115F >Modified files: > bin/mksh : check.t exprtok.h sh.h > >Log message:

Bug#834170: arb: FTBFS with GCC 6

e consider uploading in source only form. That way we will see pretty build logs for "amd64" and "all" here: https://buildd.debian.org/status/package.php?p=arb Thanks. arb_6.0.3-1_amd64-20160812-1235.gz Description: application/gzip

Bug#834169: Apache2 can't be installed on testing/sid

Package: apache2 Version: 2.4.23-3 Severity: grave On a new fresh created Debian Sid ADM64 chroot, installing apache2 is not possible: $ sudo apt-get install -y apache2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were

Processed: Bug#828178: afl: FTBFS: clang error unknown argument -fdebug-prefix-map=/build/afl-2.16b=.'

Processing commands for cont...@bugs.debian.org: > found 828178 2.21b-1 Bug #828178 {Done: Daniel Stender } [src:afl] afl: clang-3.7 doesn't support -fdebug-prefix-map Marked as found in versions afl/2.21b-1. > thanks Stopping processing here. Please contact me if you need

Bug#828178: afl: FTBFS: clang error unknown argument -fdebug-prefix-map=/build/afl-2.16b=.'

found 828178 2.21b-1 thanks On Mon, 27 Jun 2016, Daniel Kahn Gillmor wrote: > Hi Daniel-- > > On Sat 2016-06-25 16:09:08 -0400, Daniel Stender wrote: > > AFL fails to build from source in reproducible builds test build > > environments like this (log from 2.16b-1 build): > > > > > > lang-3.7

Bug#805963: diff NMU for zipios++_0.1.5.9+cvs.2007.04.28-5.4

tags 805963 +pending +patch thanks Dear maintainer, I have prepared an NMU (versioned as 0.1.5.9+cvs.2007.04.28-5.4) and uploaded to DELAYED/5. Please fell free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best regards Anton nmu.debdiff Description: Binary

Processed: diff NMU for zipios++_0.1.5.9+cvs.2007.04.28-5.4

Processing commands for cont...@bugs.debian.org: > tags 805963 +pending +patch Bug #805963 [src:zipios++] zipios++: FTBFS when built with dpkg-buildpackage -A (no binary artifacts) Added tag(s) pending. Bug #805963 [src:zipios++] zipios++: FTBFS when built with dpkg-buildpackage -A (no binary

Bug#833860: marked as done (pexpect: accesses the internet during build)

Your message dated Fri, 12 Aug 2016 16:28:13 + with message-id and subject line Bug#833860: fixed in pexpect 4.2.0-1 has caused the Debian Bug report #833860, regarding pexpect: accesses the internet during build to be marked as done. This means that you

Bug#817187: marked as done (python-pep8: fails to upgrade from 'testing' - trying to overwrite /usr/lib/python2.7/dist-packages/pep8.py)

Your message dated Fri, 12 Aug 2016 16:28:03 + with message-id and subject line Bug#817187: fixed in pep8 1.7.0-3 has caused the Debian Bug report #817187, regarding python-pep8: fails to upgrade from 'testing' - trying to overwrite

Bug#823591: marked as done (pep8 - Need stricter dependencies: pkg_resources.VersionConflic)

Your message dated Fri, 12 Aug 2016 16:28:03 + with message-id and subject line Bug#823591: fixed in pep8 1.7.0-3 has caused the Debian Bug report #823591, regarding pep8 - Need stricter dependencies: pkg_resources.VersionConflic to be marked as done.

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Okay. I have now gone through a dpkg -i install of all the (non dbgsym) .deb I see on your server, and also issued a reboot for good measure, but I still see the same problem with journald being failed, along with dependent services

Bug#811794: marked as done (3dldf: FTBFS with GCC 6: error: reference is ambiguous)

Your message dated Fri, 12 Aug 2016 16:19:28 + with message-id and subject line Bug#811794: fixed in 3dldf 2.0.3+dfsg-5 has caused the Debian Bug report #811794, regarding 3dldf: FTBFS with GCC 6: error: reference is ambiguous to be marked as done. This

Bug#834013: marked as done (emboss,emboss-data: both packages ship /usr/share/man/man1/em_cons.1e.gz)

Your message dated Fri, 12 Aug 2016 16:20:51 + with message-id and subject line Bug#834013: fixed in emboss 6.6.0+dfsg-5 has caused the Debian Bug report #834013, regarding emboss,emboss-data: both packages ship /usr/share/man/man1/em_cons.1e.gz to be

Bug#834161: mksh: /= operator has vanished

Package: mksh Version: 53-1 Severity: grave Tags: upstream fixed-upstream Justification: renders package unusable Forwarded: https://www.mail-archive.com/miros-mksh@mirbsd.org/msg00628.html -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, the /= operator has vanished in mksh R53: $ mksh -c

Bug#832837: marked as done (ros-rviz: FTBFS: qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake': No such file or directory)

Your message dated Fri, 12 Aug 2016 16:02:02 + with message-id and subject line Bug#832837: fixed in ros-rviz 1.12.1+dfsg-1 has caused the Debian Bug report #832837, regarding ros-rviz: FTBFS: qmake: could not exec

Bug#831135: marked as done (ros-rviz: FTBFS with GCC 6: effort_display.h:39:37: error: unable to find string literal operator 'operator""fmt' with 'const char [28]', 'long unsigned int' arguments)

Your message dated Fri, 12 Aug 2016 16:02:02 + with message-id and subject line Bug#831135: fixed in ros-rviz 1.12.1+dfsg-1 has caused the Debian Bug report #831135, regarding ros-rviz: FTBFS with GCC 6: effort_display.h:39:37: error: unable to find

Bug#834162: freevo: obsolete

Package: freevo Severity: grave Justification: renders package unusable Dear everybody, 'freevo' is in "dormant state" since Feb 2014 [1] ; there are some patches around to revive it [2] and a github branch that had some activity [3], but in truth there was no activity in some years. In the

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On 12 August 2016 at 11:05, Pete Batard wrote: > Thanks Felipe. > > I installed libsystemd0_231-2_armhf.deb but shouldn't there be a > systemd_231-2_armhf.deb as well? Strangely there's a > systemd-dbgsym_231-2_armhf.deb but no non-dbgsym version, as opposed to > other .debs. Sorry

Bug#834156: yi: FTBFS: libicuuc.so.55: cannot open shared object file: No such file or directory

Source: yi Version: 0.12.5-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, yi fails to build from source in unstable/amd64: [..]

Bug#834157: libsmi: FTBFS: :16:16: error: conflicting types for 'smileng'

Source: libsmi Version: 0.4.8+dfsg2-11 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, libsmi fails to build from source in unstable/amd64:

Bug#834158: lvtk: FTBFS: boost/system/error_code.hpp:221: undefined reference to `boost::system::generic_category()'

Source: lvtk Version: 1.2.0~dfsg0-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, lvtk fails to build from source in unstable/amd64: [..]

Bug#834152: molly-guard: fails to remove: rmdir: failed to remove '/lib/molly-guard': No such file or directory

Package: molly-guard Version: 0.6.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing molly-guard (0.6.3) ... Removing 'diversion of

Bug#834153: gitolite3 should depend on openssh-client

Package: gitolite3 Version: 3.6.1-2+deb8u1 Severity: serious Hi, `gitolite setup` calls `ssh-keygen -l -f ` to check that is was passed a valid OpenSSH pubkey. When this binary is not present, `gitolite setup` fails (claiming the pubkey is not valid). As such, it seems that gitolite3 should

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

Thanks Felipe. I installed libsystemd0_231-2_armhf.deb but shouldn't there be a systemd_231-2_armhf.deb as well? Strangely there's a systemd-dbgsym_231-2_armhf.deb but no non-dbgsym version, as opposed to other .debs. The .dsc does mention a 'systemd' binary, and earlier, the idea was to

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 834147 + blender Bug #834147 [src:binutils] binutils: breaks mips and mipsel link of blender Added indication that 834147 affects blender > thanks Stopping processing here. Please contact me if you need assistance. -- 834147:

Bug#811794: Fix/Workaround for the 3dldf FTBFS

> tags 811794 +patch Thanks, included, tested, uploaded. All the best Norbert -- PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#833758: zegrapher: diff for NMU version 3.0-1.1

On Fri, Aug 12, 2016 at 01:46:11PM +0200, Georges Khaznadar wrote: > Dear Mattia, Hi Georges :) > thank you for the NMU. You're welcome! Shall I feel free to reschedule it to 0 day? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540

Bug#834013: emboss, emboss-data: both packages ship /usr/share/man/man1/em_cons.1e.gz

Hi, On 12/08/16 14:58, Andreas Tille wrote: > Hi, > > this version was a source only upload. If I build on my local machine > emboss-data does not contain any dir /usr/share/man. However, the > binary package on the Debian mirror contains /usr/share/man/man1 with > has two symlinks which are

  1   2   >