Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

On Sun, 16 Oct 2016 00:20:31 -0400 u...@debian.org (Aaron M. Ucko) wrote: > Is there some reason node-lex-parser has an Architecture value of any > rather than all? Its contents all appear to be architecture-independent > at first glance. Because it was created by dh-make as npm2deb was crashing

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

Pirate Praveen writes: > jison is now in the archive and we don't need npm. Once jison clears > NEW, I'll upload a fixed version. Thanks. Alas, the new version is unbuildable on architectures that previously failed -- e.g., node-lex-parser build-depends on: -

Bug#835760: marked as done (golang-golang-x-tools: FTBFS: Tests failures)

Your message dated Sun, 16 Oct 2016 01:36:14 + with message-id and subject line Bug#835760: fixed in golang-golang-x-tools 1:0.0~git20160826.0.a832035-1 has caused the Debian Bug report #835760, regarding golang-golang-x-tools: FTBFS: Tests failures to be

Bug#840767: peg is in NEW

Hello, Thank you for reporting. Peg and all of its dependencies are currently in NEW. Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature

Bug#840725: [Pkg-opencl-devel] Bug#840840: pocl: Does not build on several architectures

You shouldn't need libpoclu-dev to build OpenCL-using code, only ocl-icd-opencl-dev (which is available on all architectures). What does require an ICD is _running_ OpenCL code, including in the test suite (if any); as buildds are unlikely to have a GPU, build-time OpenCL-using tests can only be

Bug#840788: marked as done (vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev)

Your message dated Sat, 15 Oct 2016 22:47:10 + with message-id and subject line Bug#840788: fixed in vtk6 6.3.0+dfsg1-2 has caused the Debian Bug report #840788, regarding vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev to

Bug#840610: UnicodeEncodeError: 'ascii' codec can't encode character

Robert Luberda writes: > According to GNU gettext documentation[1]: "The variable LANGUAGE is > ignored if the locale is set to ‘C’." That exception was added on 2001-01-03, for glibc 2.2.1. In glibc 2.2, LANGUAGE used to override LC_ALL=C. In Python 2.0 (released on

Bug#840900: zorp: FTBFS (vector: No such file or directory)

Package: src:zorp Version: 3.9.5-7.1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Processed: Re: Bug#840610: UnicodeEncodeError: 'ascii' codec can't encode character

Processing commands for cont...@bugs.debian.org: > reassign 840610 python3 3.5.1-4 Bug #840610 [apt-listchanges] UnicodeEncodeError: 'ascii' codec can't encode character Bug reassigned from package 'apt-listchanges' to 'python3'. No longer marked as found in versions apt-listchanges/3.5.

Bug#811974: marked as done (tinyxml2: FTBFS with GCC 6: symbol changes)

Your message dated Sun, 16 Oct 2016 00:07:10 +0300 with message-id <20161015210710.3rlnknru74kgp...@bunk.spdns.de> and subject line This bug has already been fixed has caused the Debian Bug report #811974, regarding tinyxml2: FTBFS with GCC 6: symbol changes to be marked as done. This means that

Processed: Version tracking fixes

Processing commands for cont...@bugs.debian.org: > found 804272 1.13.0-2 Bug #804272 [akonadi-server] fails to synchronize caldav to OpenXChange without notice Marked as found in versions akonadi/1.13.0-2. > found 811974 2.2.0-1 Bug #811974 [tinyxml2] tinyxml2: FTBFS with GCC 6: symbol changes

Bug#817689: marked as done (tendra-doc: Removal of debhelper compat 4)

Your message dated Sat, 15 Oct 2016 23:52:11 +0300 with message-id <20161015205211.3xftpytykio2y...@bunk.spdns.de> and subject line tendra-doc has been removed from unstable has caused the Debian Bug report #817689, regarding tendra-doc: Removal of debhelper compat 4 to be marked as done. This

Bug#811560: marked as done (elasticache: FTBFS with nonexistant $HOME)

Your message dated Sat, 15 Oct 2016 23:39:58 +0300 with message-id <20161015203958.pmfke2rsnfsly...@bunk.spdns.de> and subject line elasticache has been removed from unstable has caused the Debian Bug report #811560, regarding elasticache: FTBFS with nonexistant $HOME to be marked as done. This

Bug#840725: Bug#840840: pocl: Does not build on several architectures

On Sat, Oct 15, 2016 at 08:39:08PM +0200, Andreas Beckmann wrote: > > So if the fact remains that pocl does not build anywhere else than on > > intel I need to restrict the set of architectures for libhmsbeagle as > > well. > > Or just restrict the use of OpenCL to the architectures that have

Bug#840725: Bug#840840: pocl: Does not build on several architectures

On Sat, Oct 15, 2016 at 08:39:08PM +0200, Andreas Beckmann wrote: > On 2016-10-15 19:57, Andreas Tille wrote: > > because libpoclu-dev is not available on most architectures. Since > > libhmsbeagle has build on all those architectures either the set of > > Build-Depends has changed (may be

Bug#835241: marked as done (pytest-mock: FTBFS against pytest 3.0.0)

Your message dated Sat, 15 Oct 2016 19:24:15 + with message-id and subject line Bug#835241: fixed in pytest-mock 1.2-1 has caused the Debian Bug report #835241, regarding pytest-mock: FTBFS against pytest 3.0.0 to be marked as done. This means that you

Bug#835241: marked as pending

tag 835241 pending thanks Hello, Bug #835241 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/pytest-mock.git;a=commitdiff;h=f3e6ab3 --- commit

Processed: Bug#835241 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 835241 pending Bug #835241 [src:pytest-mock] pytest-mock: FTBFS against pytest 3.0.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835241:

Bug#835336: marked as done (influxdb: FTBFS in testing (go generate returned exit code 1))

Your message dated Sat, 15 Oct 2016 18:54:12 + with message-id and subject line Bug#835336: fixed in influxdb 0.13.0+dfsg1-5 has caused the Debian Bug report #835336, regarding influxdb: FTBFS in testing (go generate returned exit code 1) to be marked as

Processed: Pending fixes for bugs in the influxdb package

Processing commands for cont...@bugs.debian.org: > tag 835336 + pending Bug #835336 [src:influxdb] influxdb: FTBFS in testing (go generate returned exit code 1) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835336:

Bug#840840: pocl: Does not build on several architectures

On 2016-10-15 19:57, Andreas Tille wrote: > because libpoclu-dev is not available on most architectures. Since > libhmsbeagle has build on all those architectures either the set of > Build-Depends has changed (may be together with khronos-opencl-clhpp?) > or there was a point in time when pocl

Bug#835336: Pending fixes for bugs in the influxdb package

tag 835336 + pending thanks Some bugs in the influxdb package are closed in revision f1edbb720ccf16d7ce2e028657b1382689a1fedd in branch 'master' by aviau The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/influxdb.git/commit/?id=f1edbb7 Commit message: Remove

Processed: retitle 840805 to libgd2: CVE-2016-8670: Stack Buffer Overflow in GD dynamicGetbuf

Processing commands for cont...@bugs.debian.org: > retitle 840805 libgd2: CVE-2016-8670: Stack Buffer Overflow in GD > dynamicGetbuf Bug #840805 [src:libgd2] libgd2: Stack Buffer Overflow in GD dynamicGetbuf Changed Bug title to 'libgd2: CVE-2016-8670: Stack Buffer Overflow in GD dynamicGetbuf'

Bug#840725: Bug#840840: pocl: Does not build on several architectures

On Sat, Oct 15, 2016 at 04:27:45PM +0200, Andreas Beckmann wrote: > On 2016-10-15 16:09, Andreas Tille wrote: > > > >https://buildd.debian.org/status/package.php?p=pocl > > Right, pocl FTBFS everywhere except linux-i386/amd64, and always has > (with maybe some spurious successes when tests

Bug#840756: marked as done (node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked)

Your message dated Sat, 15 Oct 2016 17:28:01 + with message-id and subject line Bug#840756: fixed in node-lex-parser 0.1.4-2 has caused the Debian Bug report #840756, regarding node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked to be

Bug#840760: marked as done (node-livescript: FTBFS (npm: Command not found))

Your message dated Sat, 15 Oct 2016 17:28:08 + with message-id and subject line Bug#840760: fixed in node-livescript 1.5.0+dfsg-2 has caused the Debian Bug report #840760, regarding node-livescript: FTBFS (npm: Command not found) to be marked as done.

Bug#840788: vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev

On Sat, 15 Oct 2016 13:36:31 +0200 Andreas Beckmann wrote: > On Fri, 14 Oct 2016 23:44:15 +0200 Bas Couwenberg > wrote: > > Please change the libmysqlclient-dev build dependency to > > default-libmysqlclient-dev. The vtk6 build dependencies are > > no longer installable now

Processed: Re: openscenegraph-3.4: FTBFS (internal compiler error: Segmentation fault)

Processing commands for cont...@bugs.debian.org: > notfound 840834 openscenegraph-3.4/3.4.0+dfsg1-4 Bug #840834 [src:openscenegraph-3.4] openscenegraph-3.4: FTBFS (internal compiler error: Segmentation fault) No longer marked as found in versions openscenegraph-3.4/3.4.0+dfsg1-4. > thanks

Bug#671469: marked as done ("FTBFS on arm*")

Your message dated Sat, 15 Oct 2016 20:01:48 +0300 with message-id <20161015170148.mayjgwbnrogjv...@bunk.spdns.de> and subject line This seems to be already fixed has caused the Debian Bug report #671469, regarding "FTBFS on arm*" to be marked as done. This means that you claim that the problem

Processed: Move to the correct package

Processing commands for cont...@bugs.debian.org: > reassign 671469 src:elmerfem 6.1.0.svn.5396.dfsg-5.1 Bug #671469 [src:elmer] "FTBFS on arm*" Warning: Unknown package 'src:elmer' Bug reassigned from package 'src:elmer' to 'src:elmerfem'. No longer marked as found in versions

Bug#698527: marked as done (elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries)

Your message dated Sat, 15 Oct 2016 19:54:28 +0300 with message-id <20161015165428.wyomoqygfuuvl...@bunk.spdns.de> and subject line Already fixed in oldstable has caused the Debian Bug report #698527, regarding elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible

Bug#606048: marked as done (perdition: package upgrade removes and does not regenerate .db files)

Your message dated Sat, 15 Oct 2016 19:37:53 +0300 with message-id <20161015163753.ijnz52qvnpdce...@bunk.spdns.de> and subject line Re: Bug#606048: Perdition package upgrade removes and does not regenerate .db files has caused the Debian Bug report #606048, regarding perdition: package upgrade

Bug#837236: marked as done (elixir-lang: FTBFS: Uncaught error in rebar_core: {'EXIT',)

Your message dated Sat, 15 Oct 2016 16:23:14 + with message-id and subject line Bug#837236: fixed in elixir-lang 1.3.3-2 has caused the Debian Bug report #837236, regarding elixir-lang: FTBFS: Uncaught error in rebar_core: {'EXIT', to be marked as done.

Bug#825261: marked as done (dvswitch: FTBFS in experimental)

Your message dated Sat, 15 Oct 2016 19:06:42 +0300 with message-id <20161015160642.pquvjtn7cuyzc...@bunk.spdns.de> and subject line dvswitch was removed from experimental has caused the Debian Bug report #825261, regarding dvswitch: FTBFS in experimental to be marked as done. This means that you

Bug#840841: digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded

Hello, Thanks for the bug report. On Saturday, October 15, 2016 3:35:24 PM CDT you wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. The output you quoted doesn't indicate WHY it was to be removed. Do you know? > # ok, lets try to install it in

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 Sat, 15 Oct 2016 19:01:56 +0300 with message-id <20161015160156.bdpcuotc2cinl...@bunk.spdns.de> and subject line This bug was already fixed has caused the Debian Bug report #824825, regarding liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite

Bug#822981: marked as done (tomcat-maven-plugin: FTBFS: [..] org.codehaus.plexus:plexus-component-metadata:jar:1.0-beta-3.0.7 has not been downloaded)

Your message dated Sat, 15 Oct 2016 18:58:07 +0300 with message-id <20161015155807.7qlcbzlhj5njp...@bunk.spdns.de> and subject line tomcat-maven-plugin was removed from Debian has caused the Debian Bug report #822981, regarding tomcat-maven-plugin: FTBFS: [..]

Bug#821701: [Pkg-php-pecl] Bug#821701: src:php-json: PHP 7.0 Transition

Adrian, it needs to go together with src:php5 that we still keep for s-p-u. But I was just going to ask security team if that's still needed since we are doing all updates via jessie-security anyway. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a

Bug#821701: [Pkg-php-pecl] Bug#821701: src:php-json: PHP 7.0 Transition

On Tue, Apr 19, 2016 at 10:17:50AM +0200, Ondřej Surý wrote: > Control: notfound -1 php-json/1:7.0+35 > Control: found -1 php-json/1.3.7-1 > Control: severity -1 serious Hi Ondřej, is there any reason for keeping the php-json source package in unstable, or should it be removed? Thanks Adrian

Processed: tagging 840841

Processing commands for cont...@bugs.debian.org: > tags 840841 + help Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 840841:

Processed: Fix/Workaround for the tagcoll2 FTBFS

Processing control commands: > tags 811863 +patch Bug #811863 [tagcoll2] tagcoll2: FTBFS with GCC 6: no matching function for call to Added tag(s) patch. -- 811863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#811863: Fix/Workaround for the tagcoll2 FTBFS

Control: tags 811863 +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

Bug#840488: bareos: Bareos crashes on "status dir"

Package: bareos Version: 15.2.4-1+b1 Followup-For: Bug #840488 Dear Maintainer, This bug also appears with: bconsole -> status all or if you enter just status and then select 5 ("All") It appears with postgresql 9.5 and 9.6 -- System Information: Debian Release: stretch/sid APT prefers

Bug#840840: pocl: Does not build on several architectures

On 2016-10-15 16:09, Andreas Tille wrote: > Hi Andreas, > > On Sat, Oct 15, 2016 at 03:59:16PM +0200, Andreas Beckmann wrote: >> Huh? The only architecture with outdated binaries is powerpcspe (which >> only "successfully" built them in the past thanks to a nocheck buildd). >> Feel free to get

Bug#840847: freezegun: FTBFS under some timezones (eg. GMT-14)

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

Bug#840840: pocl: Does not build on several architectures

Hi Andreas, On Sat, Oct 15, 2016 at 03:59:16PM +0200, Andreas Beckmann wrote: > Huh? The only architecture with outdated binaries is powerpcspe (which > only "successfully" built them in the past thanks to a nocheck buildd). > Feel free to get them decrufted as well. What about arm64:

Bug#840825: libtag1-dev: missing header files

Hi James, Le samedi 15 octobre 2016, 12:02:06 EDT James Cowgill a écrit : > taglib 1.11+dfsg.1-0.1 and 1.11+dfsg.1-0.2 are missing various include > files which should be shipped in /usr/include. These are reported by > dh_install: Thanks for reporting the problem and sorry for the trouble. I'll

Bug#840840: marked as done (pocl: Does not build on several architectures)

Your message dated Sat, 15 Oct 2016 15:59:16 +0200 with message-id and subject line Re: Bug#840840: pocl: Does not build on several architectures has caused the Debian Bug report #840840, regarding pocl: Does not build on several architectures to

Bug#839791: qtcreator: builds with clang support on armel

On miércoles, 5 de octubre de 2016 12:52:08 A. M. ART Emilio Pozuelo Monfort wrote: > Source: qtcreator > Version: 4.1.0-1 > Severity: serious > > Hi! > > qtcreator builds with LLVM 3.8 on armel, however LLVM 3.8 is not > available there. (Well, there is an old version still in the archive, >

Processed: Fw: Bug#837798: RFS: libcgicc/3.2.16-0.1 NMU -- C++ class library for writing CGI applications

Processing control commands: > tags -1 patch pending Bug #811988 [libcgicc] libcgicc: FTBFS with GCC 6: call overloaded is ambiguous Added tag(s) pending and patch. -- 811988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811988 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#840845: python-pygraphviz: FTBFS with /bin/sh as bash

Source: python-pygraphviz Version: 1.3.1-1 Severity: serious Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, Due to the commented-out "set -e; \" line (note the trailing backslash!), python-pygraphviz

Bug#840841: digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded

Package: digikam Version: 4:5.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails. >From the attached log (scroll to

Bug#840840: pocl: Does not build on several architectures

Source: pocl Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, the pocl source does not build on several architectures where it has built before. The problem seem to be failed tests. Please see:

Bug#839931: freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf

Followup-For: Bug #839931 Control: found -1 3.0.12+dfsg-1 Hi, there are still file overwrite problems in the latest version: Preparing to unpack .../07-freeradius_3.0.12+dfsg-1_amd64.deb ... Unpacking freeradius (3.0.12+dfsg-1) over (2.2.8+dfsg-0.1+b3) ... dpkg: warning: unable to delete

Processed: Re: freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf

Processing control commands: > found -1 3.0.12+dfsg-1 Bug #839931 {Done: Michael Stapelberg } [freeradius-config] freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf Marked as found in versions freeradius/3.0.12+dfsg-1; no

Bug#837281: manila-ui: FTBFS: compressor.exceptions.OfflineGenerationError: No template loaders defined. You must set TEMPLATE_LOADERS in your settings or set 'loaders' in your TEMPLATES dictionary.

Followup-For: Bug #837281 Hi, attached is a piuparts log from python-manila-ui_2.5.1-0 in stretch showing the same problem. This pulled in python-django all 1:1.10.1-1 python-django-horizon all 3:9.0.1-2 openstack-dashboard all 3:9.0.1-2 python-django-horizon and openstack-dashboard have

Processed: user debian...@lists.debian.org, usertagging 837281, affects 837281, reopening 837281

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 837281 piuparts Usertags were: qa-ftbfs qa-ftbfs-20160910. Usertags are now: qa-ftbfs piuparts qa-ftbfs-20160910. > affects 837281 +

Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere

Control: reopen -1 Control: found -1 2.1.2+20160831-1 Hi, On 14/10/16 10:21, Andreas Tille wrote: > Hi Emilio, > > this is a known issue which would be fixed if khronos-opencl-clhpp would > be accepted by ftpmaster in new queue. I've given a hint to frpmaster > about this hoping that this can

Processed: Version tracking fixes

Processing commands for cont...@bugs.debian.org: > found 833828 1.2.1-2 Bug #833828 [python3-django-markupfield] Migrations of stable's python3-django-markupfield (1.2.1) do not work with stable's django version (1.7.x). Marked as found in versions django-markupfield/1.2.1-2. > fixed 833828

Processed: Re: Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere

Processing control commands: > reopen -1 Bug #840725 {Done: Andreas Tille } [src:libhmsbeagle] libhmsbeagle: FTBFS and bd-uninstallable almost everywhere 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may

Bug#838671: marked as done (openchangeproxy: uninstallable in jessie, broken by samba)

Your message dated Sat, 15 Oct 2016 15:40:10 +0300 with message-id <20161015124010.cquf4kwha5fkz...@bunk.spdns.de> and subject line openchangeproxy has been removed from unstable has caused the Debian Bug report #838671, regarding openchangeproxy: uninstallable in jessie, broken by samba to be

Bug#839190:

hello dearest

Bug#840725: marked as done (libhmsbeagle: FTBFS and bd-uninstallable almost everywhere)

Your message dated Sat, 15 Oct 2016 12:25:47 + with message-id and subject line Bug#840725: fixed in libhmsbeagle 2.1.2+20160831-1 has caused the Debian Bug report #840725, regarding libhmsbeagle: FTBFS and bd-uninstallable almost everywhere to be marked

Bug#840826: marked as pending

tag 840826 pending thanks Hello, Bug #840826 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-security/princeprocessor.git;a=commitdiff;h=75e5860 --- commit

Processed: Bug#840826 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 840826 pending Bug #840826 [princeprocessor] princeprocessor: /usr/bin/pp64 is already used by polylib-utils Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 840826:

Bug#840831: libvirtuoso5.5-cil: fails to install: E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed

Package: libvirtuoso5.5-cil Version: 6.1.6+dfsg2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

I forgot to tell that I can reproduce this only on some machines but not in others. The machines on which it fails (there are more than one) seem to be the ones having some corporate firewall rules I can't disable. This is probably not just a coincidence. However, since packages are not supposed

Processed: retitle 840806 to libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr()

Processing commands for cont...@bugs.debian.org: > retitle 840806 libgd2: CVE-2016-6911: invalid read in > gdImageCreateFromTiffPtr() Bug #840806 [src:libgd2] libgd2: invalid read in gdImageCreateFromTiffPtr() Changed Bug title to 'libgd2: CVE-2016-6911: invalid read in

Bug#840826: princeprocessor: /usr/bin/pp64 is already used by polylib-utils

Hi Andreas, thanks for noticing this and letting me know. I will make sure to rename the single binary in this package to avoid the name clash. Cheers Sascha > On 15 Oct 2016, at 13:22, Andreas Beckmann wrote: > > Package: princeprocessor > Version: 0.21-2 > Severity:

Processed: user debian...@lists.debian.org, usertagging 840788, affects 840788, severity of 840788 is serious

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 840788 piuparts There were no usertags set. Usertags are now: piuparts. > affects 840788 + libvtk6-dev Bug #840788 [src:vtk6] vtk6:

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

Package: src:lucene-solr Version: 3.6.2+dfsg-8 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#840826: princeprocessor: /usr/bin/pp64 is already used by polylib-utils

Package: princeprocessor Version: 0.21-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Selecting previously unselected package princeprocessor.

Processed: libtag1-dev: missing header files

Processing control commands: > affects -1 kid3 Bug #840825 [libtag1-dev] libtag1-dev: missing header files Added indication that 840825 affects kid3 -- 840825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#840825: libtag1-dev: missing header files

Package: libtag1-dev Version: 1.11+dfsg.1-0.1 Severity: serious Control: affects -1 kid3 X-Debbugs-CC: m...@lm7.fr Hi, taglib 1.11+dfsg.1-0.1 and 1.11+dfsg.1-0.2 are missing various include files which should be shipped in /usr/include. These are reported by dh_install: dh_install

Processed: Re: Bug#840818: nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver

Processing control commands: > severity -1 normal Bug #840818 [nvidia-driver] nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver Severity set to 'normal' from 'serious' -- 840818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840818 Debian Bug

Bug#840818: nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver

Control: severity -1 normal On Sat, 2016-10-15 at 12:15 +0200, Domonkos Lezsák wrote: > Package: nvidia-driver > Severity: serious > Tags: upstream > Justification: Policy 1.1 No, it's not. If this is an issue, it is _very_ specific to one type of machine. It is not a general issue with the

Bug#840824: ruby-text-table: FTBFS (failing tests)

Package: src:ruby-text-table Version: 1.2.4-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#840823: execnet: FTBFS (failing tests)

Package: src:execnet Version: 1.4.1-2 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Processed: Re: [pkg-gnupg-maint] Bug#840680: dirmngr: Dirmngr not always responding

Processing control commands: > severity -1 grave Bug #840680 [dirmngr] dirmngr: Dirmngr not always responding Severity set to 'grave' from 'important' -- 840680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#840342: [nvidia-legacy-304xx-driver] Confirmation

Processing control commands: > retitle -1 nvidia-legacy-304xx-driver: OpenGL broken in 304.132 Bug #840342 [nvidia-legacy-304xx-driver] [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver Changed Bug title to 'nvidia-legacy-304xx-driver: OpenGL broken in 304.132' from

Bug#839987: marked as done (libcompress-raw-lzma-perl: Version Mismatch due to new src:xz-utils)

Your message dated Sat, 15 Oct 2016 10:39:41 + with message-id and subject line Bug#839987: fixed in libcompress-raw-lzma-perl 2.069-2 has caused the Debian Bug report #839987, regarding libcompress-raw-lzma-perl: Version Mismatch due to new src:xz-utils

Bug#840134: marked as done (asciinema: d/copyright has wrong license)

Your message dated Sat, 15 Oct 2016 10:24:22 + with message-id and subject line Bug#840134: fixed in asciinema 1.3.0-2 has caused the Debian Bug report #840134, regarding asciinema: d/copyright has wrong license to be marked as done. This means that you

Processed: Re: bamfdaemon: unowned directory after purge: /usr/share/applications/

Processing control commands: > severity -1 serious Bug #683757 {Done: Mike Gabriel } [bamfdaemon] bamfdaemon: unowned directory after purge: /usr/share/applications/ Severity set to 'serious' from 'important' > found -1 0.5.3-1~exp1 Bug #683757 {Done: Mike Gabriel

Bug#840818: nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver

Package: nvidia-driver Severity: serious Tags: upstream Justification: Policy 1.1 After installing nvidia-driver on a fresh installed debian (or on it's distributions too), the driver could not be loaded causes to boot in low-graphics mode. The main problem is here, that the package overwrites

Bug#839987: Pending fixes for bugs in the libcompress-raw-lzma-perl package

tag 839987 + pending thanks Some bugs in the libcompress-raw-lzma-perl package are closed in revision 898ccbda13fe5e910ae1a95f979e9afc92ad9784 in branch 'master' by gregor herrmann The full diff can be seen at

Processed: Pending fixes for bugs in the libcompress-raw-lzma-perl package

Processing commands for cont...@bugs.debian.org: > tag 839987 + pending Bug #839987 [libcompress-raw-lzma-perl] libcompress-raw-lzma-perl: Version Mismatch due to new src:xz-utils Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 839987:

Bug#840815: acl2: FTBFS on some architectures: HARD ACL2 ERROR in ASSERT$: Assertion failed:

Source: acl2 Version: 7.2dfsg-2 Severity: serious Hi, Your package failed to build on mips64el, as well as in some other (non-release) architectures. From the mips64el log: start address -T 0xc0c0f0 ;; Finished loading #p"boot-strap-pass-2.o" ;; Loading "defpkgs.lisp" [GC for 95 SYMBOL

Bug#838833: asterisk: AST-2016-006

The issue is tracked by the security team as https://security-tracker.debian.org/tracker/CVE-2016-7550 >. I guess the easiest fix is to upgrade the unstable version from upstream, as the older versions of Debian are not affected and a quick search did not point me to a patch. -- Happy hacking

Bug#840417: marked as done (pdf2htmlex: FTBFS with new release of fontforge)

Your message dated Sat, 15 Oct 2016 07:50:25 + with message-id and subject line Bug#840417: fixed in fontforge 1:20161005~dfsg-2 has caused the Debian Bug report #840417, regarding pdf2htmlex: FTBFS with new release of fontforge to be marked as done. This

Processed: Re: Bug#840736: gnome-maps: always offline cant browse any map

Processing control commands: > tags -1 + moreinfo Bug #840736 [gnome-maps] gnome-maps: always offline cant browse any map Added tag(s) moreinfo. -- 840736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#840736: gnome-maps: always offline cant browse any map

Control: tags -1 + moreinfo On Fri, Oct 14, 2016 at 08:58:34PM +1100, Fulano Diego Perez wrote: > cannot browse any maps > > always reports offline with active internet comms > > ignore missing pkgs below - report bug has confusion with this Also, are you able to access

Bug#840760: node-livescript: FTBFS (npm: Command not found)

Control: -1 tags pending On Fri, 14 Oct 2016 14:10:01 + Santiago Vila wrote: > npm install jison > make[1]: npm: Command not found jison is just uploaded to debian, so npm is no longer required. Once it clears NEW, I'll upload a fixed version that uses jison package via

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

Control: -1 tags pending On Friday 14 October 2016 07:29 PM, Aaron M. Ucko wrote: > Automatic builds of node-lex-parser all failed with either > > npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked > npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11) >