Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

Source: nodejs Version: 4.4.7~dfsg-2 Severity: serious Hi, I see you dropped support for armel in #818552 and requested the removal of the outdated armel binaries. That's fine. However, nodejs doesn't migrate to testing because the lack of armel binaries breaks a number of packages that depend

Processed: RM: node-xmlhttprequest [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838458 838457 838451 838449 838454 838450 838453 838452 838455 838440 was not blocking any bugs. Added blocking bug(s) of 838440:

Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

On 09/21/2016 11:34 AM, Jérémy Lal wrote: > 2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : >> I see you dropped support for armel in #818552 and requested the removal >> of the outdated armel binaries. That's fine. However, nodejs doesn't >> migrate to testing because the

Processed: RM: node-tilejson [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838466 838458 838468 838450 838452 838459 838469 838464 838451 838454 838460 838465 838453 838467 838457 838455 838449 838440 was

Processed: RM: node-mbtiles [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838457 838460 838451 838452 838464 838454 838449 838455 838450 838467 838459 838466 838468 838465 838453 838458 838440 was not

Processed: RM: node-millstone [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838470 838465 838468 838452 838464 838454 838449 838455 838453 838460 838459 838466 838469 838451 838467 838450 838458 838457

Processed: I can reproduce it in src:mako (not in sqlalchemy)

Processing commands for cont...@bugs.debian.org: > tags 830178 - unreproducible Bug #830178 [src:mako] mako: FTBFS: ValueError: too many values to unpack Removed tag(s) unreproducible. > severity 830178 serious Bug #830178 [src:mako] mako: FTBFS: ValueError: too many values to unpack Severity set

Processed: RM: node-body-parser [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838451 838460 838449 838453 838457 838458 838459 838452 838464 838455 838454 838450 838440 was not blocking any bugs. Added

Processed: RM: node-node-expat [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838449 838451 838452 838450 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838453 -- 838440:

Processed: RM: node-sqlite3 [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838452 838449 838451 838450 838453 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838454 -- 838440:

Processed: RM: node-topcube [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838453 838451 838452 838450 838454 838449 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838455 -- 838440:

Processed: RM: node-ws [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838453 838457 838452 838450 838455 838449 838454 838451 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838458

Processed: RM: node-websocket [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838455 838449 838453 838451 838450 838454 838452 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838457 --

Processed: RM: qtwebchannel5-examples [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838450 838458 838451 838453 838452 838457 838455 838459 838454 838449 838440 was not blocking any bugs. Added blocking bug(s) of

Processed: RM: node-ltx [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838452 838454 838455 838458 838450 838457 838465 838451 838466 838449 838464 838460 838453 838459 838440 was not blocking any

Bug#835747: marked as done (ivtools: FTBFS: src/Attribute/attrlist.cc:514:35: error: call of overloaded 'abs(unsigned int)' is ambiguous)

Your message dated Wed, 21 Sep 2016 11:22:06 + with message-id and subject line Bug#835747: fixed in ivtools 1.2.11a1-8 has caused the Debian Bug report #835747, regarding ivtools: FTBFS: src/Attribute/attrlist.cc:514:35: error: call of overloaded

Processed: RM: node-leveldown [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838450 838451 838449 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838452 -- 838440:

Processed: RM: node-groove [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838449 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838450 -- 838440:

Processed: RM: node-almond [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was not blocked by any bugs. 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838449 -- 838440:

Processed: RM: node-iconv [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838449 838450 838440 was not blocking any bugs. Added blocking bug(s) of 838440: 838451 -- 838440:

Processed: also execute the control commands

Processing commands for cont...@bugs.debian.org: > severity 815272 serious Bug #815272 {Done: Adrian Bunk } [nodejs] build failure in jessie while backporting Severity set to 'serious' from 'wishlist' > fixed 815272 4.4.5~dfsg-1 Bug #815272 {Done: Adrian Bunk }

Processed: Re: Bug#838463: libosmium: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory)

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

Bug#838463: libosmium: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory)

Control: tags -1 pending On 09/21/2016 12:08 PM, Santiago Vila wrote: > dh_installexamples > # Remove executable bit from .cpp files > chmod 0644 debian/*/usr/share/doc/*/examples/*.cpp > chmod: cannot access 'debian/*/usr/share/doc/*/examples/*.cpp': No such file > or directory Fix by making

Processed: your mail

Processing commands for cont...@bugs.debian.org: > owner 838415 ! Bug #838415 [gir1.2-urfkill-glib0] Wrong package name, installs typelib file into wrong directory Owner recorded as Keng-Yu Lin . > End of message, stopping processing here. Please contact me if you need

Bug#838445: libnss-wrapper: nss-wrapper fails to build on jessie

Package: libnss-wrapper Version: 1.1.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) I am trying to build nss-wrapper on jessie and it was failing. I was getting an error along the lines of: implicit declaration of function 'cmocka_unit_test'

Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : > Source: nodejs > Version: 4.4.7~dfsg-2 > Severity: serious > > Hi, > > I see you dropped support for armel in #818552 and requested the removal > of the outdated armel binaries. That's fine. However, nodejs doesn't > migrate

Processed: RM: groovebasin [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838455 838454 838457 838451 838458 838459 838452 838450 838460 838453 838449 838440 was not blocking any bugs. Added blocking

Processed: RM: node-raw-body [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838452 838450 838457 838449 838460 838455 838458 838464 838453 838451 838459 838465 838454 838440 was not blocking any bugs. Added

Bug#836904: marked as done (Depend eatmydata is unused and undesirable on productive systems)

Your message dated Wed, 21 Sep 2016 10:31:30 + with message-id and subject line Bug#836904: fixed in vsftpd 3.0.3-8 has caused the Debian Bug report #836904, regarding Depend eatmydata is unused and undesirable on productive systems to be marked as done.

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

Your message dated Wed, 21 Sep 2016 11:34:18 + with message-id and subject line Bug#838463: fixed in libosmium 2.9.0-2 has caused the Debian Bug report #838463, regarding libosmium: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or

Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

On 21/09/16 06:40, Rene Engelhard wrote: > tag 838418 + moreinfo > thanks [snip] > Especially as end of August we got Gtk 3.0 3.21.x What happens if you > downgrade > that one to 3.20.9? (see snapshot.debian.org? > > Regards, > > Rene I tried reverting to libgtk-3-0_3.20.9-1_amd64.deb and

Bug#838418: libreoffice-gtk3: Font corruption - both content and dialogs

Hi, On Wed, Sep 21, 2016 at 10:11:10AM +0100, Simon John wrote: > Regarding the version info, I didn't realise it was ok/possible to put > two versions in the tag, but I put it in the text anyway. Maybe file it > as a bug to the reportbug maintainers? The point is that you should not add two

Bug#806616: fixed + pending

control: tags -1 + fixed pending I am working on it. The issue is fixed in my fork, and the fix should be rolled with the next update which will include a new upstream release. Thanks, Ghis

Processed: fixed + pending

Processing control commands: > tags -1 + fixed pending Bug #806616 [src:fftw3] fftw3: FTBFS when built with dpkg-buildpackage -A (build-indep fails) Added tag(s) pending and fixed. -- 806616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806616 Debian Bug Tracking System Contact

Bug#838463: libosmium: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory)

Package: src:libosmium Version: 2.9.0-1 Severity: serious Tags: patch 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: RM: node-node-xmpp [armel] -- ROM; nodejs no longer built on armel

Processing control commands: > block 838440 by -1 Bug #838440 [src:nodejs] nodejs: can't migrate to testing because of lack of armel binaries 838440 was blocked by: 838467 838455 838460 838458 838449 838453 838452 838454 838464 838451 838457 838450 838459 838466 838465 838440 was not blocking

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

On Wed, Sep 21, 2016 at 08:57:34AM +0200, Svante Signell wrote: > A question: Why did you not apply the documentation patch threrby closing bug > #790664? From the build logs no texi files were processed, how come? because I could not figure what your patches actually did, and building without it

Processed: notfixed 836174 in 8:6.7.7.10-5+deb7u4, notfixed 836174 in 8:6.8.9.9-5+deb8u4 ...

Processing commands for cont...@bugs.debian.org: > # try to adjust tracking information > notfixed 836174 8:6.7.7.10-5+deb7u4 Bug #836174 {Done: Bastien Roucariès } [src:imagemagick] Prevent runtime error: divide by zero No longer marked as fixed in versions

Processed: Reassign an RC bug to the right package -- where it has been fixed already

Processing commands for cont...@bugs.debian.org: > reassign 835581 node-ast-util Bug #835581 [node-ast-utils] node-es6-promise: FTBFS in testing (compile-modules shows usage help) Warning: Unknown package 'node-ast-utils' Bug reassigned from package 'node-ast-utils' to 'node-ast-util'. Ignoring

Processed (with 1 error): Old node-ast-utils was triggering a FTBFS in node-es6-promise

Processing commands for cont...@bugs.debian.org: > reassign 835581 node-ast-utils Bug #835581 [src:node-es6-promise] node-es6-promise: FTBFS in testing (compile-modules shows usage help) Bug reassigned from package 'src:node-es6-promise' to 'node-ast-utils'. Warning: Unknown package

Processed: Re: [Debichem-devel] Bug#838299: Bug#838299: Bug#838299: espresso: FTBFS on various arches: test suite hangs

Processing commands for cont...@bugs.debian.org: > tags 838299 -pending Bug #838299 [src:espresso] espresso: FTBFS on various arches: test suite hangs Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 838299:

Processed: severity of 827744 is grave

Processing commands for cont...@bugs.debian.org: > severity 827744 grave Bug #827744 [src:bzip2] bzip2: CVE-2016-3189: heap use after free in bzip2recover Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 827744:

Bug#837615: Upload of MySQL 5.7 to unstable

Dear Release Team, I believe we're now pretty much ready for an upload of MySQL 5.7 to unstable. This would be src:mysql-5.7, which would eventually supersede src:mysql-5.6, with a general s/5.6/5.7/ in the binary package names. One significant change is the transition from libmysqlclient18 to

Bug#838299: [Debichem-devel] Bug#838299: Bug#838299: Bug#838299: espresso: FTBFS on various arches: test suite hangs

tags 838299 -pending thanks Hi, On Tue, Sep 20, 2016 at 09:23:03PM +0200, Michael Banck wrote: > I've committed a patch to svn just now to run their python script in > verbose mode, which should at least address this; Unfortunately, test builds of this showed it running the testsuite with -v,

Bug#833770: [Debichem-devel] Bug#833770: Bug#833770: avogadro: FTBFS with gcc6/boost1.61

On 19/09/16 19:30, Anton Gladky wrote: > One need to discuss it with Michael. Note that the experimental version fails to build on armel/armhf (at least). Cheers, Emilio

Bug#811674: FTBFS with GCC 6: multiple errors

On 20/09/16 23:38, Vincent Lefevre wrote: > Control: tags -1 patch > > On 2016-09-19 17:12:17 +0200, Emilio Pozuelo Monfort wrote: >> On Tue, 19 Jan 2016 16:50:22 -0800 Martin Michlmayr wrote: >>> This package fails to build with GCC 6. GCC 6 has not been released >>> yet, but

Bug#832364: marked as done (kodi: Crashes on trying to play any TV recording)

Your message dated Wed, 21 Sep 2016 16:46:39 +0200 with message-id and subject line Re: Bug#831591: ffmpeg: kodi crash has caused the Debian Bug report #831591, regarding kodi: Crashes on trying to play any TV recording to be

Bug#831591: marked as done (ffmpeg: kodi crash)

Your message dated Wed, 21 Sep 2016 16:46:39 +0200 with message-id and subject line Re: Bug#831591: ffmpeg: kodi crash has caused the Debian Bug report #831591, regarding ffmpeg: kodi crash to be marked as done. This means that

Bug#820794: [PATCH] Re: Bug#820794: smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares

Control: notfound -1 2:4.2.10+dfsg-0+debA Control: found -1 2:4.2.10+dfsg-0+deb8u3 Control: tag -1 + patch Control: forwarded -1 https://bugzilla.samba.org/show_bug.cgi?id=11822 Control: severity -1 grave Hi, raising the severity to grave as this definitely causes data loss: * Files are

Bug#838499: wsjt: 9.7.r3639+dfsg-1 depends on numeric module which has been replaced by numpy

Package: wsjt Version: 9.7.r3639+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, I just installed wsjt from the actual 'sid' releade. Unfortunately the package is broken because, as I understand, it is depending from the numeric module which has been replaced by

Bug#837786: mutter: Issues repainting the display on mouse movement

Version 3.22.0 (currently from unstable) still affected. Today`s update to Mesa 12.0.3-1 didn`t help. --- I am not familiar with Linux graphic stack. Frames that should not be displayed (because they are few seconds old) are still flickering into current proper frame, seems like framebuffer

Processed: Re: Please prepare for vala 0.34

Processing control commands: > severity -1 serious Bug #838335 [src:valabind] Please prepare for vala 0.34 Severity set to 'serious' from 'important' -- 838335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: [PATCH] Re: Bug#820794: smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares

Processing control commands: > notfound -1 2:4.2.10+dfsg-0+debA Bug #820794 [smbclient] smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares There is no source info for the package 'smbclient' at version '2:4.2.10+dfsg-0+debA' with architecture '' Unable

Processed: [PATCH] Re: Bug#820794: smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares

Processing control commands: > notfound -1 2:4.2.10+dfsg-0+debA Bug #820794 [smbclient] smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares There is no source info for the package 'smbclient' at version '2:4.2.10+dfsg-0+debA' with architecture '' Unable

Bug#831591: ffmpeg: kodi crash

Control: fixed -1 7:3.1.3-1 Hi Carl, 2016-09-07 20:21 GMT+02:00 Carl Eugen Hoyos : > Hi Bálint! > >> I went throught the unclassified bugs and set the >> proper state to help tracking them. > > This bug (#831591) and #832364 contain neither backtrace > nor bisect. Note that

Processed: Re: Bug#831591: ffmpeg: kodi crash

Processing control commands: > fixed -1 7:3.1.3-1 Bug #831591 [ffmpeg] ffmpeg: kodi crash Bug #832364 [ffmpeg] kodi: Crashes on trying to play any TV recording Marked as fixed in versions ffmpeg/7:3.1.3-1. Marked as fixed in versions ffmpeg/7:3.1.3-1. -- 831591:

Processed: Re: Please prepare for vala 0.34

Processing control commands: > severity -1 serious Bug #838334 [src:valadoc] Please prepare for vala 0.34 Severity set to 'serious' from 'important' -- 838334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#817656: root-tail: Removal of debhelper compat 4

On Wed, 21 Sep 2016 01:40:41 +0200 Axel Beckert wrote: > Hi Francesco, Hello Axel, thanks a lot for stepping in! [...] > root-tail has just been orphaned by the MIA team on behalf of Stephen > Gran, see https://bugs.debian.org/838406. > > I'm preparing a QA upload of root-tail fixing this bug

Bug#837786: mutter: Issues repainting the display on mouse movement

I confirm, same problem for me; - Even with Gnome 3.22.0 - Nvidia Graphic GTX660 with proprietary drivers

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

Processing control commands: > reassign -1 src:python-llfuse 1.1.1+dfsg-2 Bug #837254 [pytest] 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

Bug#837011: marked as done (ltrace: FTBFS: proc.c:245:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations])

Your message dated Wed, 21 Sep 2016 19:49:29 + with message-id and subject line Bug#837011: fixed in ltrace 0.7.3-6 has caused the Debian Bug report #837011, regarding ltrace: FTBFS: proc.c:245:3: error: 'readdir_r' is deprecated

Bug#837786: mutter: Issues repainting the display on mouse movement

I confirm, same problem for me; - Even with Gnome 3.22.0 - Nvidia Graphic 

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

Control: reassign -1 src:python-llfuse 1.1.1+dfsg-2 Please CC $pack...@packages.debian.org when you reassign bugs. Otherwise I have to find your mail with the explanation manually. On 2016-09-13 10:07:41, Nikolaus Rath wrote: > Control: reassign 837254 pytest > > On Sep 10 2016, Lucas Nussbaum

Bug#811700: marked as done (FTBFS with GCC 6: macro passed X arguments, takes Y)

Your message dated Wed, 21 Sep 2016 20:54:17 +0200 with message-id <1474484057.5923.3.ca...@gmx.com> and subject line Re: FTBFS with GCC 6: macro passed X arguments, takes Y has caused the Debian Bug report #811700, regarding FTBFS with GCC 6: macro passed X arguments, takes Y to be marked as

Bug#838516: FTBFS: conflicts between build dependencies

Source: k3d Version: 0.8.0.5-4 Severity: serious Hi, k3d 0.8.0.5-4 has Build-Depends: [...] libglew-dev, libglewmx-dev, [...] but libglewmx-dev 1.13.0-3 has Conflicts: libglew-dev

Bug#834928: This is fixed in ifupdown 0.8.11

This is a bug in ifupdown, not isc-dhcp-client. It's fixed in 0.8.11 by the change to ifupdown's wait-for-ll6.sh: --- ifupdown-0.8.10/wait-for-ll6.sh 2015-12-01 16:50:26.0 -0500 +++ ifupdown-0.8.11/wait-for-ll6.sh 2016-04-20 08:57:37.0 -0400 @@ -4,7 +4,7 @@

Processed: found 835243 in 0.15.2-3, notfound 835243 in 0.15.2

Processing commands for cont...@bugs.debian.org: > found 835243 0.15.2-3 Bug #835243 [src:python-future] python-future: FTBFS against pytest3.0.0 Marked as found in versions python-future/0.15.2-3. > notfound 835243 0.15.2 Bug #835243 [src:python-future] python-future: FTBFS against pytest3.0.0

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 834928 ifupdown Bug #834928 [isc-dhcp-client] isc-dhcp-client: ifup fails with "Can't bind to dhcp address: Cannot assign, requested address" Bug reassigned from package 'isc-dhcp-client' to 'ifupdown'. No longer marked as found in

Processed: fixed 835684 in 0.14.7+dfsg1-1

Processing commands for cont...@bugs.debian.org: > fixed 835684 0.14.7+dfsg1-1 Bug #835684 [src:syncthing] syncthing: FTBFS: dh_auto_test: go test -v -p 1 github.com/syncthing/syncthing/cmd/stbench github.com/syncthing/syncthing/cmd/stcompdirs github.com/syncthing/syncthing/cmd/stdisco

Bug#838516: FTBFS: conflicts between build dependencies

Hi Joachim, 2016-09-21 21:38 GMT+02:00 Joachim Reichel : > Source: k3d > Version: 0.8.0.5-4 > Severity: serious > > Hi, > > k3d 0.8.0.5-4 has > > Build-Depends: [...] libglew-dev, libglewmx-dev, [...] > > but libglewmx-dev 1.13.0-3 has > > Conflicts: libglew-dev > > (I want to

Bug#831153: openjdk-8-jre-dcevm: FTBFS with GCC 6: os.hpp:28:30: fatal error: jvmtifiles/jvmti.h: No such file or directory

The error "jvmtifiles/jvmti.h: No such file or directory" isn't the cause of the build failure. This error has been fixed upstream (see https://bugs.openjdk.java.net/browse/JDK-8152067) and it can be avoided by setting the USE_PRECOMPILED_HEADER=0 environment variable. The fatal errors are the

Bug#834684: marked as done (python-pbr: FTBFS too much often (failing tests))

Your message dated Wed, 21 Sep 2016 23:23:48 + with message-id and subject line Bug#834684: fixed in python-pbr 1.10.0-1 has caused the Debian Bug report #834684, regarding python-pbr: FTBFS too much often (failing tests) to be marked as done. This means

Bug#838414: gpick: colors.txt is non-free

Elías Alejandro writes: > Could you review this issue? What kind of review are you asking for? What new information has appeared that prompts a review? For what it's worth, I agree with the earlier assessment that the restriction on usage violates DFSG §6. Further, the term

Bug#838516: FTBFS: conflicts between build dependencies

On Wed, 2016-09-21 at 21:38 +0200, Joachim Reichel wrote: > Build-Depends: [...] libglew-dev, libglewmx-dev, [...] Why does it build-depend against both variants?                   > but libglewmx-dev 1.13.0-3 has >    > Conflicts: libglew-dev The background here is

Bug#799571: Release of libcwd version 1.0.6

Hi, I just released libcwd version 1.0.6 (http://downloads.sourceforge.net/project/libcwd/libcwd/1.0.6/libcwd-1.0.6.tar.gz) which adds support for g++ 6.2.0 and lower (tested 5.4.0, 4.9.4, 4.8.5, etc). I think that should solve this bug. -- Carlo Wood

Processed: tagging 831153

Processing commands for cont...@bugs.debian.org: > tags 831153 + help Bug #831153 [src:openjdk-8-jre-dcevm] openjdk-8-jre-dcevm: FTBFS with GCC 6: os.hpp:28:30: fatal error: jvmtifiles/jvmti.h: No such file or directory Added tag(s) help. > thanks Stopping processing here. Please contact me if

Bug#838536: kicad still depends on obsolete glew packages

Package: kicad Version: 4.0.4+dfsg1-1 Severity: serious The latest kicad successfully built against the new glew but the resulting binary package still has a dependency on "libglew1.13 | libglew1.10" in addition to the dependency on "libglew2.0 (>= 1.12.0)" The dependency on "libglew1.13 |

Bug#829752: lower the severity

Control: severity -1 whislist Hello I don't want to start a severity war, but I count on having netfilter-persistent when I install new systems using stretch. From the bts documentation [1] grave makes the package in question unusable or mostly so, or causes data loss, or introduces a

Processed: set affects for cups bug and gnome components

Processing commands for cont...@bugs.debian.org: > affects 838434 + gnome-settings-daemon gnome-control-center Bug #838434 [libcups2] gnome-settings-daemon 100% CPU usage on login Added indication that 838434 affects gnome-settings-daemon and gnome-control-center > thanks Stopping processing

Processed: Re: gnome-settings-daemon 100% CPU usage on login

Processing control commands: > reassign -1 libcups2 2.2.0-1 Bug #838434 [gnome-settings-daemon] gnome-settings-daemon 100% CPU usage on login Bug reassigned from package 'gnome-settings-daemon' to 'libcups2'. No longer marked as found in versions gnome-settings-daemon/3.21.92.1-1. Ignoring

Bug#838434: marked as done (gnome-settings-daemon 100% CPU usage on login)

Your message dated Wed, 21 Sep 2016 07:49:00 + with message-id and subject line Bug#838434: fixed in cups 2.2.0-2 has caused the Debian Bug report #838434, regarding gnome-settings-daemon 100% CPU usage on login to be marked as done. This means that you

Bug#836174: Not for stable and old stable

control: fixed -1 8:6.7.7.10-5+deb7u4 control: fixed -1 8:6.8.9.9-5+deb8u4 Statistic code does not compute histogram so bug not for stable and old stable So not affected

Processed: Not for stable and old stable

Processing control commands: > fixed -1 8:6.7.7.10-5+deb7u4 Bug #836174 {Done: Bastien Roucariès } [src:imagemagick] Prevent runtime error: divide by zero Marked as fixed in versions imagemagick/8:6.7.7.10-5+deb7u4. > fixed -1 8:6.8.9.9-5+deb8u4 Bug #836174

Bug#817626: src:poppassd: Co-maintain poppassd

On Wed, Sep 21, 2016 at 05:46:09PM -0400, Peter Colberg wrote: > Please clone the updated package using > > gbp clone ssh://git.debian.org/git/collab-maint/poppassd.git For verification, these are the current branch heads: git show-ref --heads 6e26c876530625d4cdc3451bef921ce635887658

Bug#838414: gpick: colors.txt is non-free

Dear Debian-legal team, On Tue, Sep 20, 2016 at 6:46 PM, Francesco Poli (wintermute) wrote: > Package: gpick > Version: 0.2.5-2 > Severity: serious > Justification: Policy 2.2.1 > > > Hello and thanks for maintaining this little tool in Debian! > > I noticed that the

Bug#817558: marked as done (libweather-com-perl: Removal of debhelper compat 4)

Your message dated Wed, 21 Sep 2016 22:27:42 + with message-id and subject line Bug#817558: fixed in libweather-com-perl 0.5.3-3 has caused the Debian Bug report #817558, regarding libweather-com-perl: Removal of debhelper compat 4 to be marked as done.

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote: > > Just after the upgrade of keyboard-configuration from 1.148 to 1.149, > I could see that my previous configuration was lost. More precisely, > config.dat changed in the following way: When /etc/default/keyboard is ok,

Bug#838534: chromium: ::MoveToNewUserNS().

Package: chromium Version: 53.0.2785.113-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? running chromium from a terminal in weston as root * What

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

Package: src:linux Version: 4.7.4-2 Severity: grave Justification: renders package unusable When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my filesystems fails to mount with: ext4_iget:4476: inode #8: comm mount: checksum invalid A fsck does not find any errors, though, and the

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

On Mon, 2016-09-19 at 14:28 +, Mattia Rizzolo wrote: > On Fri, Sep 16, 2016 at 09:58:07PM +, Mattia Rizzolo wrote: > > > > On Fri, Sep 16, 2016 at 10:57:59PM +0200, Svante Signell wrote: > > > > > > As fas as I understand it is OK to NMU this package, based on the > > > latest replies by

Bug#838429: marked as done (zsh-antigen: broken package - only contains an invalid symlink)

Your message dated Wed, 21 Sep 2016 07:07:25 + with message-id and subject line Bug#838429: fixed in zsh-antigen 1.1.2-2 has caused the Debian Bug report #838429, regarding zsh-antigen: broken package - only contains an invalid symlink to be marked as

Bug#836588: [Cupt-devel] Bug#836588: Bug#836588: cupt: FTBFS on armel/armhf: test failures

On 20.09.2016 16:06, Emilio Pozuelo Monfort wrote: > On 19/09/16 22:00, Eugene V. Lyubimkin wrote: >> On 18.09.2016 22:40, Eugene V. Lyubimkin wrote: >>> Thank you. Turned out it is reproducible in release build (at the least on >>> armel porterbox), but not in debug build. >>> >>> I'll look into

Processed: Merging bugs which are really the same

Processing commands for cont...@bugs.debian.org: > forcemerge 834920 835682 Bug #834920 [src:python-socketpool] python-socketpool: FTBFS too much often (UnicodeDecodeError) Bug #834920 [src:python-socketpool] python-socketpool: FTBFS too much often (UnicodeDecodeError) Added tag(s) sid and

Bug#817363: asterisk-prompt-es: Removal of debhelper compat 4

Control: tags -1 + patch [Niels Thykier] > The package asterisk-prompt-es uses debhelper with a compat level of 4, > which is deprecated and scheduled for removal. Here is a patch to fix this RC issue. diff -u asterisk-prompt-es-1.4/debian/rules asterisk-prompt-es-1.4/debian/rules ---

Processed: Re: asterisk-prompt-es: Removal of debhelper compat 4

Processing control commands: > tags -1 + patch Bug #817363 [src:asterisk-prompt-es] asterisk-prompt-es: Removal of debhelper compat 4 Added tag(s) patch. -- 817363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#838531: nose2: FTBFS in testing (failing tests)

Package: src:nose2 Version: 0.6.5-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. I'm attaching a single build log, but it fails every time I try, and it

Bug#817626: src:poppassd: Co-maintain poppassd

Hi Adam, With the stretch freeze getting close, I have imported the poppassd history into a collab-maint git repository and updated the packaging to fix #817626 and conform to Debian policy. Please note that I have *not* added myself to Uploaders. If you wish to continue to maintain the package