Processed: found 837714 in 3.1.2-11

Processing commands for cont...@bugs.debian.org: > found 837714 3.1.2-11 Bug #837714 [src:libarchive] libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite Marked as found in versions libarchive/3.1.2-11. > thanks Stopping processing here.

Bug#837714: libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite

On Tue, Sep 13, 2016 at 09:41:49PM +0200, Salvatore Bonaccorso wrote: > [0] https://security-tracker.debian.org/tracker/CVE-2016-5418 > [1] >

Bug#837263: marked as done (smlnj: FTBFS: Can't locate mltex.thm in @INC)

Your message dated Wed, 14 Sep 2016 04:31:02 + with message-id and subject line Bug#837263: fixed in smlnj 110.79-2 has caused the Debian Bug report #837263, regarding smlnj: FTBFS: Can't locate mltex.thm in @INC to be marked as done. This means that you

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

On Wed, 14 Sep 2016, László Böszörményi wrote: As Perl debug and libc6 debug symbols installed, I don't know which library / executable may contain points #0 and #1. Maybe log.c itself? At least the mentioned line in #2 is: LockSemaphoreInfo(log_semaphore); There were no functions added or

Bug#832077: Info received (emacs clutter screen on windows switch)

On Thu, 08 Sep 2016 10:38:09 +0900, Leon Meier wrote: > > By the way, I don't know who is the culprit: libgtk-3-0, emacs, or > someone else. So please consider my found / nofound tags just as > additional information on my configuration rather as a bug source > hint. Sorry about that.

Bug#837738: Fails to start, Invalid property: GtkScrolledWindow.propagate-natural-height

Package: nautilus Version: 3.21.92-1 Severity: grave When running nautilus, one get's (nautilus:28168): Gtk-CRITICAL **: Error building template class 'NautilusToolbar' for an instance of type 'NautilusToolbar': .:194:52 Invalid property: GtkScrolledWindow.propagate-natural-height Segmentation

Bug#837263: marked as pending

tag 837263 pending thanks Hello, Bug #837263 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=collab-maint/smlnj.git;a=commitdiff;h=84fa6e1 --- commit

Processed: Bug#837263 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 837263 pending Bug #837263 [src:smlnj] smlnj: FTBFS: Can't locate mltex.thm in @INC Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 837263:

Bug#837036: marked as done (gitolite3: uninstallable without . in @INC)

Your message dated Wed, 14 Sep 2016 00:19:27 + with message-id and subject line Bug#837036: fixed in gitolite3 3.6.6-1 has caused the Debian Bug report #837036, regarding gitolite3: uninstallable without . in @INC to be marked as done. This means that you

Processed: reassign 837727 to gnome-shell-extension-top-icons-plus

Processing commands for cont...@bugs.debian.org: > reassign 837727 gnome-shell-extension-top-icons-plus 15-2 Bug #837727 [src:gnome-shell-extension-top-icon-plus] gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92 Warning: Unknown package

Bug#837123: [anna] segfault in wheezy installer

On Tue, Sep 13, 2016 at 11:03:19PM +0200, Aurelien Jarno wrote: ... > > If all of that makes no difference, what would be the next step? > > What would be interesting would be to try to reproduce the issue in > qemu or virtualbox, with as many things as possible close to your > system. > Just

Bug#836768: marked as done (libphonenumber: FTBFS with glibc 2.24: int readdir_r() is deprecated)

Your message dated Tue, 13 Sep 2016 23:25:40 + with message-id and subject line Bug#836768: fixed in libphonenumber 7.1.0-5 has caused the Debian Bug report #836768, regarding libphonenumber: FTBFS with glibc 2.24: int readdir_r() is deprecated to be

Bug#837727: gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92

Control: reassign gnome-shell-extension-top-icons-plus 15-2 On Wed, 14 Sep 2016 01:20:14 +0200 bi...@debian.org wrote: > Source: gnome-shell-extension-top-icon-plus > Version: 15-2 > Severity: serious > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: gnome-shell-3-22 > > Hi, >

Bug#837595: gnome-shell-pomodoro: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837593: gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837594: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837592: gnome-shell-extension-suspend-button: Not compatible with gnome-shell 3.21.x/3.22

There are some recent updates: In the past, it was necessary to explicitly declare supported gnome-shell versions in metadata.json. This was lifted in gnome-shell 3.21.92 [1]. "Nowadays, the user interface has mostly stabilized with most changes happening under the hood. As a result, extensions

Bug#837726: gnome-shell-extension-mediaplayer: Not installable with gnome-shell >= 3.21.92

Source: gnome-shell-extension-mediaplayer Version: 0~git201600509-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-extension-mediaplayer declares a strictly versioned dependency on gnome-shell. We've uploaded

Bug#837727: gnome-shell-extension-top-icon-plus: Not installable with gnome-shell >= 3.21.92

Source: gnome-shell-extension-top-icon-plus Version: 15-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-extension-top-icon-plus declares a strictly versioned dependency on gnome-shell. We've uploaded gnome-shell

Bug#837725: gnome-shell-extension-caffeine: Not installable with gnome-shell >= 3.21.92

Source: gnome-shell-extension-caffeine Version: 0~git20160329-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-3-22 Hi, your package gnome-shell-extension-caffeine declares a strictly versioned dependency on gnome-shell. We've uploaded gnome-shell

Processed: severity of 836881 is normal

Processing commands for cont...@bugs.debian.org: > severity 836881 normal Bug #836881 [libhx509-5-heimdal] X509 card-based logins fail with SIGSEGV Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 836881:

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

Hi Bob, Niko, On Tue, Sep 13, 2016 at 11:15 PM, Bob Friesenhahn wrote: > On Tue, 13 Sep 2016, László Böszörményi wrote: >> On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni wrote: >>> This package is failing to build on ppc64el, but built successfully

Bug#834249: openbabel: FTBFS in testing

Control: tag -1 + patch On Sat, 13 Aug 2016 20:05:36 +0200, Santiago Vila wrote: > Package: openbabel > Version: 2.3.2+dfsg-2.3 > Severity: serious > > -- > /<>/openbabel-2.3.2+dfsg/src/alias.cpp: In static member > function

Processed: Re: Bug#834249: openbabel: FTBFS in testing

Processing control commands: > tag -1 + patch Bug #834249 [src:openbabel] openbabel: FTBFS in testing Added tag(s) patch. -- 834249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

On Tue, 13 Sep 2016, László Böszörményi wrote: On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni wrote: This package is failing to build on ppc64el, but built successfully in the past. As seen at https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el it regressed

Processed: (no subject)

Processing commands for cont...@bugs.debian.org: > tags 836669 + upstream fixed-upstream Bug #836669 [caja] caja: Crashes due to theme errors Added tag(s) upstream and fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 836669:

Bug#837123: [anna] segfault in wheezy installer

On 2016-09-10 11:30, Vincent McIntyre wrote: > On Fri, Sep 09, 2016 at 03:59:17PM +0200, Aurelien Jarno wrote: > > > > I don't talk about the software running on your DNS servers, but > > rather how they behave when they get queried. It might depends on > > many other things, like if your network

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

On Tue, Sep 13, 2016 at 10:42 PM, Niko Tyni wrote: > This package is failing to build on ppc64el, but built successfully > in the past. As seen at > https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el > it regressed with 1.3.24+hg20160808-1, and the version

Processed: block 830200 with 837719

Processing commands for cont...@bugs.debian.org: > # assuming ppc64el missing binaries currently block testing migration > block 830200 with 837719 Bug #830200 [release.debian.org] transition: perl 830200 was blocked by: 834795 825611 825609 836162 834796 836636 825014 825231 834799 834797

Processed: tagging 837036

Processing commands for cont...@bugs.debian.org: > tags 837036 + fixed-upstream Bug #837036 [gitolite3] gitolite3: uninstallable without . in @INC Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 837036:

Bug#837719: graphicsmagick: FTBFS on ppc64el: PerlMagick test failures

Package: graphicsmagick Version: 1.3.25-1 Severity: serious This package is failing to build on ppc64el, but built successfully in the past. As seen at https://buildd.debian.org/status/logs.php?pkg=graphicsmagick=ppc64el it regressed with 1.3.24+hg20160808-1, and the version currently in sid is

Bug#834597: kgb-bot: FTBFS in testing

On Thu, Aug 18, 2016 at 06:22:54PM +0200, gregor herrmann wrote: >... > Hm, I guess we should think about a release? Yes, it would be good if you could make a release. > Cheers, > gregor Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the

Bug#834087: marked as done (runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory)

Your message dated Tue, 13 Sep 2016 16:07:25 -0400 (EDT) with message-id and subject line Re: Bug#834087: Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or

Bug#837714: libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite

Source: libarchive Version: 3.2.1-2 Severity: grave Tags: security upstream patch Hi, the following vulnerability was published for libarchive. CVE-2016-5418[0]: |Archive Entry with type 1 (hardlink), but has a non-zero data size |file overwrite This corresponds to [1] and [2], which is

Bug#821481: PHP 7.0 support

Hi FYI, there is an upstream bug report open for PHP 7.0 support: https://jira.z-hub.io/projects/ZP/issues/ZP-804 Cheers, MJ -- Michael-John Turner * m...@mjturner.net * http://mjturner.net/

Bug#832077: Info received (emacs clutter screen on windows switch)

Are you using unstable? Then you have no right to be melodramatic about people "demolishing" the distro. It's not the maintainers fault if 3rd-party software is not up to date with the libraries on which it relies. And by using unstable or testing, the user accepts the very likely possibility of

Bug#837488: marked as done (python3-pyopencl: Broken install)

Your message dated Tue, 13 Sep 2016 18:51:17 + with message-id and subject line Bug#837488: fixed in pyopencl 2016.1+git20160809-2 has caused the Debian Bug report #837488, regarding python3-pyopencl: Broken install to be marked as done. This means that

Bug#836717: marked as done (alljoyn-services-1604 and alljoyn-services-1504: error when trying to install together)

Your message dated Tue, 13 Sep 2016 18:18:41 + with message-id and subject line Bug#836717: fixed in alljoyn-services-1604 16.04-2 has caused the Debian Bug report #836717, regarding alljoyn-services-1604 and alljoyn-services-1504: error when trying to

Bug#836719: marked as done (liballjoynservices1604 and liballjoynservices1504: error when trying to install together)

Your message dated Tue, 13 Sep 2016 18:18:41 + with message-id and subject line Bug#836719: fixed in alljoyn-services-1604 16.04-2 has caused the Debian Bug report #836719, regarding liballjoynservices1604 and liballjoynservices1504: error when trying to

Bug#836718: marked as done (alljoyn-services-1604 and alljoyn-services-1509: error when trying to install together)

Your message dated Tue, 13 Sep 2016 18:18:41 + with message-id and subject line Bug#836718: fixed in alljoyn-services-1604 16.04-2 has caused the Debian Bug report #836718, regarding alljoyn-services-1604 and alljoyn-services-1509: error when trying to

Bug#834558: marked as done (frog FTBFS)

Your message dated Tue, 13 Sep 2016 18:19:00 + with message-id and subject line Bug#834558: fixed in frog 0.13.5-1 has caused the Debian Bug report #834558, regarding frog FTBFS to be marked as done. This means that you claim that the problem has been

Bug#837700: gnutls: GNUTLS segfaults on initialization

On 2016-09-13 J Phelps wrote: > Package: libgnutls30 > Version: 3.5.4-2 > Severity: grave > File: gnutls > Justification: renders package unusable > The bug is caused by GNUTLS being compiled with the headers of and old > version of Nettle, but the package depending on (or

Processed: notfound 836717 in 15.04-4, notfound 836718 15.09-2, notfound 836719 15.04-4

Processing commands for cont...@bugs.debian.org: > notfound 836717 15.04-4 Bug #836717 [alljoyn-services-1504,alljoyn-services-1604] alljoyn-services-1604 and alljoyn-services-1504: error when trying to install together There is no source info for the package 'alljoyn-services-1604' at version

Bug#837700: gnutls: GNUTLS segfaults on initialization

Package: libgnutls30 Version: 3.5.4-2 Severity: grave File: gnutls Justification: renders package unusable The bug is caused by GNUTLS being compiled with the headers of and old version of Nettle, but the package depending on (or failing to account for a breaking change to) a newer version of

Bug#835731: marked as done (libdbix-class-perl: FTBFS: Tests failures)

Your message dated Tue, 13 Sep 2016 17:44:31 + with message-id and subject line Bug#835731: fixed in libdbix-class-perl 0.082840-2 has caused the Debian Bug report #835731, regarding libdbix-class-perl: FTBFS: Tests failures to be marked as done. This

Bug#837121: marked as done (gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.)

Your message dated Tue, 13 Sep 2016 17:42:35 + with message-id and subject line Bug#837121: fixed in gazebo 7.3.0+dfsg-5 has caused the Debian Bug report #837121, regarding gazebo: please restrict libkido-dev (build-)dependency to architectures where it

Bug#837614: Use and abuse of the unreproducible tag

On 13.09.2016 18:25, Adam D. Barratt wrote: > On 2016-09-13 12:55, Sebastiaan Couwenberg wrote: >> On 09/13/2016 01:49 PM, Santiago Vila wrote: >>> You can't reproduce it, or you don't want to reproduce it? >> >> I added the tag because I couldn't reproduce the issue in unstable where >> we build

Bug#835731: Pending fixes for bugs in the libdbix-class-perl package

tag 835731 + pending thanks Some bugs in the libdbix-class-perl package are closed in revision c7f237f72a1694e2c0a97177faad53528cee50cd in branch 'master' by gregor herrmann The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libdbix-class-perl.git/commit/?id=c7f237f

Processed: Pending fixes for bugs in the libdbix-class-perl package

Processing commands for cont...@bugs.debian.org: > tag 835731 + pending Bug #835731 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: Tests failures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835731:

Bug#837254: @pytest.skip outside test gives error

Control: reassign 837254 pytest On Sep 10 2016, Lucas Nussbaum wrote: >> collecting ... >> ERRORS >> >> __ ERROR collecting test_examples.py >> ___ >> Using

Processed: @pytest.skip outside test gives error

Processing control commands: > reassign 837254 pytest Bug #837254 [src:python-llfuse] python-llfuse: FTBFS: E: pybuild pybuild:276: test: plugin distutils failed with: exit code=2: cd /<>/python-llfuse-1.1.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest --installed "{dir}/test/" Bug

Bug#832077: Info received (emacs clutter screen on windows switch)

Hi, mate-term, caja, emacs etc. is also affected. Please roll back to 3.20.9-1 and test also with mate, if libgtk-3 work well with other software too. Please, please do not demolish debian. Please do less, but with care.

Bug#833753: marked as done (ledger: FTBFS on buildds after gcc6/icu57/boost1.61)

Your message dated Tue, 13 Sep 2016 16:37:25 + with message-id and subject line Bug#833753: fixed in ledger 3.1.2~pre1+g3a00e1c+dfsg1-1 has caused the Debian Bug report #833753, regarding ledger: FTBFS on buildds after gcc6/icu57/boost1.61 to be marked as

Bug#813722: marked as done (aces3: FTBFS on powerpc)

Your message dated Tue, 13 Sep 2016 16:11:52 +0100 with message-id <71331f6c-c0fb-0c07-3a6a-3ce7905c5...@debian.org> and subject line closed in 2.0.1-5 has caused the Debian Bug report #813722, regarding aces3: FTBFS on powerpc to be marked as done. This means that you claim that the problem has

Bug#814183: marked as done (openmpi 1.10.2 is broken on powerpc)

Your message dated Tue, 13 Sep 2016 16:11:52 +0100 with message-id <71331f6c-c0fb-0c07-3a6a-3ce7905c5...@debian.org> and subject line closed in 2.0.1-5 has caused the Debian Bug report #814183, regarding openmpi 1.10.2 is broken on powerpc to be marked as done. This means that you claim that the

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

Hi, Some time ago there was some activity with an upstream issue [1] about making the package ready for proper inclusion into Debian. Unfortunately upstream doesn't properly document dependencies and seems to have the habit to use locally patched versions of these dependencies if they feel like

Bug#837682: libconfig-model-itself-perl: FTBFS in unstable (failing tests)

On Tue, 13 Sep 2016 15:55:27 +0200 (CEST) Santiago Vila wrote: > I'm reporting this against libconfig-model-itself-perl because that's > the package which FTBFS, but of course it is completely possible (and > maybe likely) that this is still a bug in libconfig-model-perl. > >

Bug#837682: libconfig-model-itself-perl: FTBFS in unstable (failing tests)

Package: src:libconfig-model-itself-perl Version: 2.005-1 Affects: src:libconfig-model-itself-perl Severity: serious Dear maintainer: This package FTBFS in unstable, even when using libconfig-model-perl version 2.090-1, so this seems to be a problem different than the one that was reported in

Processed: Re: Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

Processing commands for cont...@bugs.debian.org: > retitle 837613 libconfig-model-itself-perl: FTBFS in testing (failing tests) Bug #837613 {Done: gregor herrmann } [src:libconfig-model-itself-perl] libconfig-model-itself-perl: FTBFS in sid (failing tests) Changed Bug title

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

retitle 837613 libconfig-model-itself-perl: FTBFS in testing (failing tests) reassign 837613 libconfig-model-perl forcemerge 837133 837613 thanks (Both bugs are equally closed, so don't worry). Explanation: I have compared the build logs for stretch and sid, and this error: Syntax error:

Bug#837059: NMU of abyss for FTBFS

Hi Alastair, thanks for the NMU. On Tue, Sep 13, 2016 at 01:43:36PM +0100, Alastair McKinstry wrote: > I have NMU's abyss 1.9.0 to DELAYED/5, to fix the FTBFS that is blocking > openmpi2. Just for the sake of interest: In how far is abyss blocking openmpi2? > The debdiff is attached for your

Bug#837268: bzr: FTBFS: Tests failures

On Tue, Sep 13, 2016 at 02:33:29PM +0200, Lucas Nussbaum wrote: > This is a case where there's no easy way to track affected releases. But > in doubt, it's better to err on the side of considering a release > affected. Yes, I fully agree, especially in this case where the build is made in

Bug#829085: --link-doc Was: [Pkg-freeipmi-devel] Bug#829085: freeipmi: not binNMU safe

Thank you Vincent for attending to freeipmi package! Here is my exploration of the issue: I was a bit bedazzled since original setup just closely followed established practice, e.g. see https://wiki.debian.org/binNMU according to which +b1 suffix should be stripped when establishing value of the

Bug#837059: NMU of abyss for FTBFS

Hi, I have NMU's abyss 1.9.0 to DELAYED/5, to fix the FTBFS that is blocking openmpi2. The debdiff is attached for your review, Best regards Alastair McKinstry -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting

Bug#837268: bzr: FTBFS: Tests failures

On 11/09/16 at 22:28 +0200, Santiago Vila wrote: > On Sun, Sep 11, 2016 at 09:53:34PM +0200, Lucas Nussbaum wrote: > > Hi, > > > > On 11/09/16 at 12:33 +0200, Santiago Vila wrote: > > > > Tags: stretch sid > > > > > > This bug should not happen in stretch (yet) because diffutils 3.5 > > > has

Bug#837614: The bugs are not reproducible in unstable

Sebastiaan Couwenberg, on Tue 13 Sep 2016 12:26:29 +0200, wrote: > The bug are not reproducible in unstable where we build our packages, we > don't build our packages in testing. But users do build their package in testing. That's one of the whole points of free software: being able to rebuild

Bug#832285: marked as done (libopenmpi2: fails to upgrade from 'sid' - trying to overwrite /usr/lib/openmpi/lib/libompitrace.so.0.0.0)

Your message dated Tue, 13 Sep 2016 12:38:09 +0100 with message-id <59b6d78d-e602-7b66-cad9-3d8cf0e46...@debian.org> and subject line closing has caused the Debian Bug report #832285, regarding libopenmpi2: fails to upgrade from 'sid' - trying to overwrite

Bug#837648: marked as done (ripe-atlas-tools: uninstallable in sid: Depends: python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 is to be installed)

Your message dated Tue, 13 Sep 2016 11:06:19 + with message-id and subject line Bug#837648: fixed in ripe-atlas-tools 2.0.1-2 has caused the Debian Bug report #837648, regarding ripe-atlas-tools: uninstallable in sid: Depends: python-ripe-atlas-sagan (<

Bug#834753: marked as done (android-platform-tools-base: FTBFS with only 1 CPU (Cannot set maxParallelForks to a value less than 1))

Your message dated Tue, 13 Sep 2016 11:00:10 + with message-id and subject line Bug#834753: fixed in android-platform-tools-base 2.0.0-1 has caused the Debian Bug report #834753, regarding android-platform-tools-base: FTBFS with only 1 CPU (Cannot set

Bug#835536: marked as done (request-tracker4: FTBFS with gnupg 2.1)

Your message dated Tue, 13 Sep 2016 11:00:18 + with message-id and subject line Bug#835536: fixed in request-tracker4 4.2.13-2 has caused the Debian Bug report #835536, regarding request-tracker4: FTBFS with gnupg 2.1 to be marked as done. This means that

Bug#836833: marked as done (request-tracker4: FTBFS with '.' removed from @INC)

Your message dated Tue, 13 Sep 2016 11:00:18 + with message-id and subject line Bug#836833: fixed in request-tracker4 4.2.13-2 has caused the Debian Bug report #836833, regarding request-tracker4: FTBFS with '.' removed from @INC to be marked as done.

Bug#829085: marked as done (freeipmi: not binNMU safe)

Your message dated Tue, 13 Sep 2016 10:53:59 + with message-id and subject line Bug#829085: fixed in freeipmi 1.4.11-1.1 has caused the Debian Bug report #829085, regarding freeipmi: not binNMU safe to be marked as done. This means that you claim that the

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

Rehi, On Mo, 2016-09-12 at 21:34 +0100, Santiago Vila wrote: > On Mon, Sep 12, 2016 at 07:34:09PM +0200, Daniel Kahn Gillmor wrote: > > > > > An even easier approach might be to do the following within the > > build: > > > >   * ln -sf /dev/urandom /dev/random > > > > why would we need the

Processed: reassign 814762 to kdepim-addons, fixed 814762 in 16.04.3-1, affects 814762 ..., usertagging 837488 ...

Processing commands for cont...@bugs.debian.org: > reassign 814762 kdepim-addons Bug #814762 {Done: Maximiliano Curia } [kmail] kmail: CSS from HTML mail interfers with header layout Bug reassigned from package 'kmail' to 'kdepim-addons'. No longer marked as found in versions

Bug#837648: ripe-atlas-tools: uninstallable in sid: Depends: python-ripe-atlas-sagan (< 1.1.11~) but 1.1.11-1 is to be installed

Package: ripe-atlas-tools Version: 2.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: ripe-atlas-tools : Depends:

Bug#830440: marked as done (mpi4py: FTBFS: ld: cannot find -llmpe)

Your message dated Tue, 13 Sep 2016 12:43:00 +0200 with message-id <1da52976-37c6-929c-716d-97e8a3aab...@xs4all.nl> and subject line Re: mpi4py: FTBFS: ld: cannot find -llmpe (not actual cause for build failures, test target is) has caused the Debian Bug report #830440, regarding mpi4py: FTBFS:

Processed: Re: mpi4py: FTBFS: ld: cannot find -llmpe (not actual cause for build failures, test target is)

Processing commands for cont...@bugs.debian.org: > fixed 830440 mpi4py/2.0.0-2 Bug #830440 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe Marked as fixed in versions mpi4py/2.0.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 830440:

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

Hi Daniel, Santiago, thx for the answer; I am not 100% satisfied, though ;). For me, it actually boils down to what notion we have: (1) The builder hosts must provide reasonable entropy. (2) Software testsuites generally must work fine even with low entropy. In the past, I tended to go with

Processed: The bugs are not reproducible in unstable

Processing commands for cont...@bugs.debian.org: > tags 837614 unreproducible Bug #837614 {Done: Sebastiaan Couwenberg } [src:python-geopandas] python-geopandas: FTBFS in testing (failing tests) Added tag(s) unreproducible. > tags 837622 unreproducible Bug #837622 {Done:

Processed: Re: Bug#831093: fixed in libterralib 4.3.0+dfsg.2-9

Processing control commands: > reopen -1 Bug #831093 {Done: Alastair McKinstry } [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] 'reopen' may be

Bug#831093: fixed in libterralib 4.3.0+dfsg.2-9

Control: reopen -1 On Tue, 02 Aug 2016 10:50:19 + Alastair McKinstry wrote: > libterralib (4.3.0+dfsg.2-9) unstable; urgency=medium > . >* Patch from Set C locale when archiving object files to get a > deterministic order. > Thanks to Eduard Sanou. Closes:

Bug#829178: marked as done (python-tidylib: FTBFS, test failures with tidy-html5)

Your message dated Tue, 13 Sep 2016 10:13:44 + with message-id and subject line Bug#829178: fixed in python-tidylib 0.2.4~dfsg-3 has caused the Debian Bug report #829178, regarding python-tidylib: FTBFS, test failures with tidy-html5 to be marked as done.

Bug#828900: marked as done (python-tidylib: FTBFS: ! LaTeX Error: File `iftex.sty' not found.)

Your message dated Tue, 13 Sep 2016 10:13:44 + with message-id and subject line Bug#828900: fixed in python-tidylib 0.2.4~dfsg-3 has caused the Debian Bug report #828900, regarding python-tidylib: FTBFS: ! LaTeX Error: File `iftex.sty' not found. to be

Processed: The bugs are reproducible in testing as the report says

Processing commands for cont...@bugs.debian.org: > tags 837614 - unreproducible Bug #837614 {Done: Sebastiaan Couwenberg } [src:python-geopandas] python-geopandas: FTBFS in testing (failing tests) Removed tag(s) unreproducible. > tags 837622 - unreproducible Bug #837622

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, thanks for your patch. In fact the issue was not in the Makefile.am as a X_LIBS was already present, but in the configure.ac where X_LIBS was set up but not SUBSTantiated. Is there a way to cancel the dealy, given that the revison -6 was

Bug#834281: libgnupg-interface-perl not migrating to testing

On Mon, Sep 12, 2016 at 23:32:50 +0200, gregor herrmann wrote: > And gnupg 2.x doesn't migrate because of #836259. > And libgnupg-interface-perl is about to be removed from testing > because of #834281 -- but, I think, this bug doesn't affect testing > since there's gnupg 1.4.x. So removing the

Bug#837614: The bugs are reproducible in testing as the report says

tags 837614 - unreproducible tags 837622 - unreproducible thanks Please don't use the unreproducible tag in this way. The bug says "FTBFS in testing", not simply "FTBFS", so the only way to reproduce it is by trying it in testing, where it was reported to fail. If a report said that "ls -l"

Bug#837261: marked as done (libconfig-model-dpkg-perl: FTBFS: Tests failures)

Your message dated Tue, 13 Sep 2016 10:06:51 + with message-id and subject line Bug#837261: fixed in libconfig-model-dpkg-perl 2.084 has caused the Debian Bug report #837261, regarding libconfig-model-dpkg-perl: FTBFS: Tests failures to be marked as done.

Processed: severity of 836585 is normal

Processing commands for cont...@bugs.debian.org: > # Cannot reproduce using clean stretch buildroot > severity 836585 normal Bug #836585 [src:celery] celery: FTBFS in testing (failing tests) Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

Hi, I had a look into ctk and since I did not intended to spent my time on 3 years old code I rewrote get-orig-source and moved the packaging to Git[1] since its no original download tarball and this simplifies the cooperation on the very same tarball. I also tried to bump the Build-Depends to

Bug#818448: fixed in imapcopy 1.04-2.1

Hi, >imapcopy (1.04-2.1) unstable; urgency=medium > * Non-maintainer upload > [Peter Michael Green] > * Fix build with fpc 3.0.0 (Closes: 818448) > > -- Gianfranco Costamagna and this is something I do almost everytime, except when the work is already

Bug#836585: celery: FTBFS in testing (failing tests)

On Tue, 13 Sep 2016, Paul Wise wrote: > On Sun, 4 Sep 2016 11:54:01 +0200 (CEST) Santiago Vila wrote: > > > 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: > > I can't reproduce this

Bug#837644: ruby-devise-async is not compatible with devise >= 4.0

package: ruby-devise-async version: 0.9.0-1 severity: serious This was introduced as a dependency for gitlab, but gitlab does not depend on it anymore (removed from Gemfile). We can safely remove the dependency in gitlab's debian/control. Once that version enters testing, we can remove

Processed: Re: Bug#837614: python-geopandas: FTBFS in testing (failing tests)

Processing commands for cont...@bugs.debian.org: > notfound 837614 python-geopandas/0.2.1-1 Bug #837614 [src:python-geopandas] python-geopandas: FTBFS in testing (failing tests) No longer marked as found in versions python-geopandas/0.2.1-1. > tags 837614 unreproducible Bug #837614

Bug#837614: marked as done (python-geopandas: FTBFS in testing (failing tests))

Your message dated Tue, 13 Sep 2016 11:10:20 +0200 with message-id and subject line Re: Bug#837614: python-geopandas: FTBFS in testing (failing tests) has caused the Debian Bug report #837614, regarding python-geopandas: FTBFS in testing (failing

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

Hi, I’m one of the nobodies that looks at my build logs. I noticed five instances of sh: 1: dot: not found error: Problems running dot: exit code=127, command='dot', arguments='"…/graph_legend.dot" -Tpng -o "…/graph_legend.png"' in the openafs build log, and indeed Doxygen is generating

Processed: notfound 837622 in python-stetl/1.0.9+ds-1, tagging 837622

Processing commands for cont...@bugs.debian.org: > notfound 837622 python-stetl/1.0.9+ds-1 Bug #837622 {Done: Sebastiaan Couwenberg } [src:python-stetl] python-stetl: FTBFS in testing (failing tests) No longer marked as found in versions python-stetl/1.0.9+ds-1. > tags 837622

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 816593 normal Bug #816593 [src:iceweasel] [FTBFS] iceweasel esr for wheezy on amd64 Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 816593:

Bug#837622: marked as done (python-stetl: FTBFS in testing (failing tests))

Your message dated Tue, 13 Sep 2016 10:45:29 +0200 with message-id <9526e4fd-1d0c-654e-6c2e-bd846dc09...@xs4all.nl> and subject line Re: Bug#837622: python-stetl: FTBFS in testing (failing tests) has caused the Debian Bug report #837622, regarding python-stetl: FTBFS in testing (failing tests) to

Bug#837638: ruby-devise-async: Incompatible with ruby-devise 4

Package: ruby-devise-async Version: 0.9.0-1 Severity: serious Ever since ruby-devise 4.1.1-2 was uploaded to Debian unstable, ruby-devise-async has been failing its autopkgtests. https://ci.debian.net/packages/r/ruby-devise-async/unstable/amd64/ I looked upstream and it's apparently a known

  1   2   >