Bug#886416: marked as done (libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU)

Your message dated Sat, 06 Jan 2018 13:49:28 + with message-id and subject line Bug#886416: fixed in libnih 1.0.3-10 has caused the Debian Bug report #886416, regarding libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

On Fri, 2017-11-17 at 07:39 +0100, Valentin Vidic wrote: > Hi, > > The problem seems to be caused by the new multi-queue xen blk driver > and I was advised by the Xen devs to increase the gnttab_max_frames=256 > parameter for the hypervisor. This has solved the blocking issue > for me and it has

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

On Sat, 06 Jan 2018 at 03:01:35 +0100, Axel Beckert wrote: > Axel Beckert wrote: > > I don't know if that test suite failure shows that expat broke libnih > > or if the test suite just needs to be adapted to the new expat > > version. > > > > - TEST_FILE_EQ (output, ("test:foo:2:0:

Bug#883526: closed by Andreas Rönnquist <gus...@debian.org> (Bug#883526: fixed in geeqie 1:1.4-1)

Control: reopen -1 Control: affects 882785 + src:geeqie On Wed, Jan 03, 2018 at 11:21:06PM +, Debian Bug Tracking System wrote: >* New upstream version 1.4 > - Really fixes the problems with trapping errors (Closes: 883526) I'm very sorry to reopen this bug again, but this fix

Bug#878338: gcc-defaults FTBFS with debhelper 10.9

> dh_compress: unknown option or error during option parsing; aborting > debian/rules:1354: recipe for target 'binary-native' failed > make: *** [binary-native] Error 25 I'm running into this on ia64 now but I'm not sure whom to blame. "Unknown option or error" doesn't make it seem that

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

STOP, STOP, STOP -> ALL THIS "Microcode-Patch" Infos! = If Intel, AMD, ARM, .. now communicating, that they can change the CPU/MMU-Microcode outside there secured factories; they send (with this) very dangerous messages to all hackers. Hackers can use "the

Processed: Re: Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

Processing control commands: > tag -1 + pending Bug #886416 [src:libnih] libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU Added tag(s) pending. -- 886416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886416

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

Control: tag -1 + pending Hi Simon, Simon McVittie wrote: > > > - TEST_FILE_EQ (output, ("test:foo:2:0: " > > > + TEST_FILE_EQ (output, ("test:foo:1:36: " > > >"Invalid object path in > > > name attribute\n")); […] > It

Processed: Re: Bug#883526 closed by Andreas Rönnquist <gus...@debian.org> (Bug#883526: fixed in geeqie 1:1.4-1)

Processing control commands: > reopen -1 Bug #883526 {Done: Andreas Rönnquist } [src:geeqie] geeqie build does not trap errors from make 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add

Bug#885989: Downgrade the severity of this bug, or close it

TLS guarantees you have established a secure connection to the host name you requested, nothing else. If a host name resolves to cloudflare's servers, that's the domain owner's decision. Almost every production deployment involves reverse proxies at one point or another (terminating TLS in the

Bug#878338: gcc-defaults FTBFS with debhelper 10.9

On Sat, Jan 06, 2018 at 02:09:44PM +0100, John Paul Adrian Glaubitz wrote: > > dh_compress: unknown option or error during option parsing; aborting > > debian/rules:1354: recipe for target 'binary-native' failed > > make: *** [binary-native] Error 25 > > I'm running into this on ia64 now but I'm

Processed: tagging 886485, affects 886485

Processing commands for cont...@bugs.debian.org: > tags 886485 - security Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs on boot at " node #0, CPUs:#1" Removed tag(s) security. > affects 886485 + security.debian.org Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

On Sat, Jan 06, 2018 at 02:03:21PM +0100, Axel Beckert wrote: > Yes, indeed, that looks much more sane now. Might be related to this > bug fix in expat 2.2.5: > >#137 #138 Fix a case of mistakenly reported parsing success where > XML_StopParser was called from an

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote: > According to that link, the fix seems to be configuration rather than code. > Does this mean this bug against the kernel should be closed? Yes, the problem seems to be in the Xen hypervisor and not the Linux kernel itself. The

Bug#886470: nvidia-kernel-dkms: FTBFS against linux 4.14.12-2

Control: tags -1 pending On Sat, 6 Jan 2018 14:51:40 +0100 Sebastian Ramacher wrote: > Package: nvidia-kernel-dkms > Version: 384.98-3 > Severity: grave > Justification: renders package unusable >  > The build of kernel module fails against linux 4.14.12-2: > | make:

Processed: Re: nvidia-kernel-dkms: FTBFS against linux 4.14.12-2

Processing control commands: > tags -1 pending Bug #886470 [nvidia-kernel-dkms] nvidia-kernel-dkms: FTBFS against linux 4.14.12-2 Added tag(s) pending. -- 886470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#886489: FTBFS: json_object.c:554:5: error: this statement may fall through [-Werror=implicit-fallthrough=]

Source: json-c Version: 0.12.1-1 Severity: serious Justification: fails to build from source Dear Maintainer, json-c fails to build from source due to a potential implicit fall-through in function json_object_get_int64() from json_object.c: libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time

Processed: ucarp: diff for NMU version 1.5.2-2.1

Processing control commands: > tags 753719 + patch Bug #753719 [ucarp] ucarp: please recommend iproute2 instead of iproute transitional package Bug #862852 [ucarp] ucarp: Please switch to iproute2 package Added tag(s) patch. Added tag(s) patch. > tags 753719 + pending Bug #753719 [ucarp] ucarp:

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 862847 buster sid Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package Added tag(s) sid and buster. > tags 824678 buster sid Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on iproute2

Processed: Re: Bug#885282: gameclock: Depends on unmaintained pygtk

Processing control commands: > forwarded -1 https://gitlab.com/anarcat/gameclock/issues/1 Bug #885282 [src:gameclock] gameclock: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://gitlab.com/anarcat/gameclock/issues/1'. -- 885282:

Bug#885282: gameclock: Depends on unmaintained pygtk

Control: forwarded -1 https://gitlab.com/anarcat/gameclock/issues/1 Understood.

Processed: still using transitional package dependency, will become uninstallable

Processing control commands: > severity 753723 serious Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute transitional package Bug #862853 [lsat] lsat: Please switch to iproute2 package Ignoring request to change severity of Bug 753723 to the same value. Ignoring request to

Processed: still using transitional package dependency, will become uninstallable

Processing control commands: > severity 753723 serious Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute transitional package Bug #862853 [lsat] lsat: Please switch to iproute2 package Ignoring request to change severity of Bug 753723 to the same value. Ignoring request to

Processed: still using transitional package dependency, will become uninstallable

Processing control commands: > severity 753723 serious Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute transitional package Bug #862853 [lsat] lsat: Please switch to iproute2 package Ignoring request to change severity of Bug 753723 to the same value. Ignoring request to

Bug#824679: still using transitional package dependency, will become uninstallable

Control: severity 753723 serious Control: severity 841001 serious Control: severity 824679 serious Control: severity 862847 serious Control: severity 862851 serious Apparently gedit (without closing the window after save) + mutt is not a good combination... The uploads are to DELAYED/5. Kind

Processed: still using transitional package dependency, will become uninstallable

Processing control commands: > severity 753723 serious Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute transitional package Bug #862853 [lsat] lsat: Please switch to iproute2 package Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > severity

Processed: still using transitional package dependency, will become uninstallable

Processing control commands: > severity 753723 serious Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute transitional package Bug #862853 [lsat] lsat: Please switch to iproute2 package Ignoring request to change severity of Bug 753723 to the same value. Ignoring request to

Bug#886476: caja-seahorse: Depends on deprecated libgnome-keyring

Source: caja-seahorse Version: 1.18.3-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs libgnome-keyring-removal Hi, The libgnome-keyring library is deprecated and its usage is strongly discouraged [1]. Your package caja-seahorse declares a

Processed: Re: Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

Processing control commands: > reassign -1 xen-hypervisor-4.8-amd64 Bug #880554 [linux-image-4.9.0-4-amd64] xen domu freezes with kernel linux-image-4.9.0-4-amd64 Bug reassigned from package 'linux-image-4.9.0-4-amd64' to 'xen-hypervisor-4.8-amd64'. No longer marked as found in versions

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

control: reassign -1 xen-hypervisor-4.8-amd64 On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote: > On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote: > > According to that link, the fix seems to be configuration rather than > > code. > > Does this mean this bug against the

Processed: Re: Bug#878338: gcc-defaults FTBFS with debhelper 10.9

Processing control commands: > tags -1 + pending Bug #878338 [src:gcc-defaults] gcc-defaults FTBFS with debhelper 10.9 Added tag(s) pending. -- 878338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#878338: gcc-defaults FTBFS with debhelper 10.9

Control: tags -1 + pending fixed in the packaging VCS On 06.01.2018 14:09, John Paul Adrian Glaubitz wrote: >> dh_compress: unknown option or error during option parsing; aborting >> debian/rules:1354: recipe for target 'binary-native' failed >> make: *** [binary-native] Error 25 > > I'm

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

Package: src:linux Version: 4.9.65-3+deb9u2 Severity: critical Tags: security Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Updated the system as requested in Debian

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

On Sat, 2018-01-06 at 15:46 +, LJ wrote: > Booting in recovery mode the final lines are: > > [ 0.058600] x86: Booting SMP configuration: > [ 0.058632] node #0, CPUs: :1 > > The cursor is flashing after the "#1" and the system hangs at that point. > > I have video and a

Processed: Re: Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

Processing control commands: > tags -1 +patch Bug #880246 [src:magic-wormhole] magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13 Added tag(s) patch. -- 880246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880246 Debian Bug Tracking System

Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

Control: tags -1 +patch On 2018-01-01 23:24:14, Harlan Lieberman-Berg wrote: > Hello Antoine, > > I ran into this recently, so I thought I'd take a quick whack at > seeing if I can fix it by updating to the latest version of > magic-wormhole. Unfortunately, that FTBFS as well, due to a bunch of

Bug#886125: marked as done (slic3r: Binaries except slic3r cannot find Slic3r.pm)

Your message dated Sat, 06 Jan 2018 09:36:37 + with message-id and subject line Bug#886125: fixed in slic3r 1.2.9+dfsg-9 has caused the Debian Bug report #886125, regarding slic3r: Binaries except slic3r cannot find Slic3r.pm to be marked as done. This

Bug#881205: Assistance for maintaining src:backintime

Dear Jonathan, I was suprised to discover that backintime had been removed from testing despite RC bug #881205 being fixed upstream [1]. For testing/unstable an update of the package to version 1.1.24 should do the trick, whilst stretch/wheezy will require a backport of this particular commit.

Bug#886433: #886433

Control: tag -1 confirmed pending The testing/ directory is new in recent in org-mode releases, and I missed it when repacking org-mode-doc. I'll fix correct this with the next upstream release. Cheers, --Seb

Bug#886385: marked as done (netsniff-ng: FTBFS: error: inlining failed in call to always_inline '__builtin_memset')

Your message dated Sat, 06 Jan 2018 09:06:05 + with message-id and subject line Bug#886385: fixed in netsniff-ng 0.6.4-1 has caused the Debian Bug report #886385, regarding netsniff-ng: FTBFS: error: inlining failed in call to always_inline

Bug#886434: marked as done (libcitadel FTBFS with "dpkg-buildpackage -B")

Your message dated Sat, 06 Jan 2018 09:19:13 + with message-id and subject line Bug#886434: fixed in libcitadel 917-2 has caused the Debian Bug report #886434, regarding libcitadel FTBFS with "dpkg-buildpackage -B" to be marked as done. This means that

Bug#886453: [src:zfs-linux]

Control: reassign -1 spl-linux 0.7.4-1 The bug affects building spl. Also for anyone trying to build this, you can build objtool in the tools/objtool directory of the linux source (apt source linux). Then copy it to /usr/src/linux-headers-4.14.0-3-amd64/tools/objtool/objtool

Processed: [src:zfs-linux]

Processing control commands: > reassign -1 spl-linux 0.7.4-1 Bug #886453 [src:zfs-linux] [src:spl-linux] Fails to build for 4.14.0-3 Bug reassigned from package 'src:zfs-linux' to 'spl-linux'. No longer marked as found in versions zfs-linux/0.7.4-1. Ignoring request to alter fixed versions of bug

Processed: #886433

Processing control commands: > tag -1 confirmed pending Bug #886433 [src:org-mode-doc] org-mode-doc: Incomplete debian/copyright? Added tag(s) confirmed and pending. -- 886433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886433 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#883987: boost1.62: FTBFS error: partial specialization ... after instantiation ... (with patch)

Hi all, Any news from the boost package maintainers for this bug ? A patch is available for this bug (see attachement) and it should be easy to fix it now. It affects the Rheolef package: there is a BinNMU issue still pending. Many thanks for your help and reactivity, Pierre --

Processed: merge 886470 886495

Processing commands for cont...@bugs.debian.org: > reassign 886495 nvidia-kernel-dkms Bug #886495 [nvidia-driver] nvidia-driver: Fails to build against 4.14.0-3 Bug reassigned from package 'nvidia-driver' to 'nvidia-kernel-dkms'. No longer marked as found in versions

Bug#856098: gnuboy: diff for NMU version 1.0.3-7.1

Control: tags 856098 + patch Control: tags 856098 + pending Control: tags 857666 + patch Control: tags 857666 + pending Dear maintainer, I've prepared an NMU for gnuboy (versioned as 1.0.3-7.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian --

Processed: gnuboy: diff for NMU version 1.0.3-7.1

Processing control commands: > tags 856098 + patch Bug #856098 [src:gnuboy] gnuboy: Please drop the (build-)dependency against esound Added tag(s) patch. > tags 856098 + pending Bug #856098 [src:gnuboy] gnuboy: Please drop the (build-)dependency against esound Added tag(s) pending. > tags

Processed: bug 883987 is forwarded to https://svn.boost.org/trac10/ticket/12534

Processing commands for cont...@bugs.debian.org: > forwarded 883987 https://svn.boost.org/trac10/ticket/12534 Bug #883987 [src:boost1.62] FTBFS error: partial specialization ... after instantiation ... (with patch) Bug #884184 [src:boost1.62] FTBFS error: partial specialization ... after

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

> Try also booting without 'quiet' and with 'debug earlyprintk'. Happy to try, but not sure how to do that - do I edit /boot/config-4.9.0-5-686-pae ? Couldn't see "QUIET" in there? > If you manage to get a kernel log (using a > serial port or maybe netconsole if it's not too early in the boot)

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

Package: polymake Version: 3.1-5 Severity: grave X-Debbugs-Cc: p...@packages.debian.org Running polymake currently fails with $ polymake Can't locate loadable object for module Polymake::Ext in @INC (@INC contains: /usr/share/polymake/perllib /usr/lib/polymake/perlx/5.26.0

Processed: basilisk2: diff for NMU version 0.9.20120331-4.1

Processing control commands: > tags 856075 + patch Bug #856075 [src:basilisk2] basilisk2: Please drop the (build-)dependency against esound Added tag(s) patch. > tags 856075 + pending Bug #856075 [src:basilisk2] basilisk2: Please drop the (build-)dependency against esound Added tag(s) pending.

Bug#856075: basilisk2: diff for NMU version 0.9.20120331-4.1

Control: tags 856075 + patch Control: tags 856075 + pending Control: tags 865145 + pending Dear maintainer, I've prepared an NMU for basilisk2 (versioned as 0.9.20120331-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not

Bug#883987: [pkg-boost-devel] Bug#883987: boost1.62: FTBFS error: partial specialization ... after instantiation ... (with patch)

On Saturday, January 6, 2018 5:25:28 AM CST Pierre Saramito wrote: > Hi all, > > Any news from the boost package maintainers for this bug ? > > A patch is available for this bug (see attachement) > and it should be easy to fix it now. Appreciate the reminder. I should be able to upload today.

Processed: found 874727 in 3.1.4~abc9f50+dfsg3-2, notfound 874727 in 3.1.4-abc9f50+dfsg3-2

Processing commands for cont...@bugs.debian.org: > found 874727 3.1.4~abc9f50+dfsg3-2 Bug #874727 [libcoin80v5] libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults. Marked as found in versions coin3/3.1.4~abc9f50+dfsg3-2. > notfound 874727

Bug#885793: marked as done (tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files))

Your message dated Sat, 06 Jan 2018 18:20:08 + with message-id and subject line Bug#885793: fixed in haskell-tldr 0.2.3-2 has caused the Debian Bug report #885793, regarding tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

> Looking at the lspci output you have a Xeon E3 from the 1200 series, but > you > could provide your full /proc/cpuinfo? Hi, sure... root@sam:~# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Celeron(R)

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

On Sat, 2018-01-06 at 18:04 +, LJ wrote: > > Looking at the lspci output you have a Xeon E3 from the 1200 series, but > > you > > could provide your full /proc/cpuinfo? > > Hi, sure... Thanks > > root@sam:~# cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu

Bug#866435: I'd volunteer to fix this bug and would move the packaging to Git

Hi Steve, it seems this package is not yet in Git. I'd volunteer to move it to Git and fix the bug. Is this OK for you? Kind regards Andreas. -- http://fam-tille.de

Bug#886512: broadcom-sta-dkms: Should depends on libelf-dev

Package: broadcom-sta-dkms Version: 6.30.223.271-7 Severity: grave Justification: renders package unusable Hi, After I updated the kernel to 4.14.0, I found that the wl.ko is gone, and I tried to rebuild manually by dpkg-reconfigure which triggers dkms build. But dkms logged the following

Bug#862851: marked as done (vblade-persist: Please switch to iproute2 package)

Your message dated Sun, 07 Jan 2018 04:19:05 + with message-id and subject line Bug#862851: fixed in vblade-persist 0.6-3 has caused the Debian Bug report #862851, regarding vblade-persist: Please switch to iproute2 package to be marked as done. This

Bug#886512: broadcom-sta-dkms: Should depends on libelf-devr

Control: retitle -1 broadcom-sta-dkms: /bin/sh: 1: [: Illegal number: Control: severity -1 important Hi, Yao Wei wrote: > After I updated the kernel to 4.14.0, I found that the wl.ko is gone, > and I tried to rebuild manually by dpkg-reconfigure which triggers dkms > build. > > But dkms logged

Processed: Re: Bug#886512: broadcom-sta-dkms: Should depends on libelf-devr

Processing control commands: > retitle -1 broadcom-sta-dkms: /bin/sh: 1: [: Illegal number: Bug #886512 [broadcom-sta-dkms] broadcom-sta-dkms: Should depends on libelf-dev Changed Bug title to 'broadcom-sta-dkms: /bin/sh: 1: [: Illegal number:' from 'broadcom-sta-dkms: Should depends on

Bug#866446: What branch of the git repository is featuring the latest packaging

Hi, I would volunteer to fix this bug but I do not understand the repository layout. It would be helpful if you would consider some standard layout or at least drop some description which one is the recent packaging branch. Somehow debian-release looks promising but this is way out of date.

Bug#886518: debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!?

Package: debhelper Version: 11.1 Severity: serious Control: affects -1 + src:file User: helm...@debian.org Usertags: rebootstrap Building file started to fail tonight. The new error comes from debhelper and debhelper was the thing that was uploaded. Very likely, debhelper is the culprit, but it

Processed: debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!?

Processing control commands: > affects -1 + src:file Bug #886518 [debhelper] debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!? Added indication that 886518 affects src:file -- 886518:

Bug#878674: marked as done (nodejs segfaults when building d3-* with webpack)

Your message dated Sun, 7 Jan 2018 12:53:48 +0530 with message-id and subject line Re: Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack has caused the Debian Bug report #878674, regarding

Bug#866458: Please update Git repository mentioned in VCS fields

Hi, I'd volunteer to work on this bug but the repository specified in the VCS fields is not up to date. Kind regards Andreas. -- http://fam-tille.de

Bug#866480: Bug was closed in 0.13.1-1

This bug was closed in the upload of 0.13.1-1 - no idea why it was not closed. -- http://fam-tille.de

Processed: Re: Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

Processing commands for cont...@bugs.debian.org: > reassign 885965 pylint3 1.7.4-2 Bug #885965 [src:distro-info] FTBFS: Test: Run pylint on Python source code ... FAIL Bug reassigned from package 'src:distro-info' to 'pylint3'. No longer marked as found in versions distro-info/0.17. Ignoring

Bug#886505: nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64

On 2018-01-06 23:29:01 +, Luca Boccassi wrote: > Same as 886470 and 886495, fixed in 384.111. OK. The build error was a bit invisible. :( -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work:

Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

reassign 885965 pylint3 1.7.4-2 thanks Am Montag, den 01.01.2018, 01:36 +0100 schrieb Adam Borowski: > Source: distro-info > Version: 0.17 > Severity: serious > Justification: fails to build from source (but built successfully in > the past) > > Hi! > I'm afraid your package fails to build with:

Processed: severity of 886474 is grave

Processing commands for cont...@bugs.debian.org: > severity 886474 grave Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: missing dependency on libelf-dev Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: Add affects

Processing commands for cont...@bugs.debian.org: > affects 885965 src:distro-info Bug #885965 [pylint3] FTBFS: Test: Run pylint on Python source code ... FAIL Added indication that 885965 affects src:distro-info > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Re: Bug#886510: Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

Processing control commands: > reassign -1 linux-headers-4.14.0-3-amd64 Bug #886510 [nvidia-legacy-304xx-kernel-dkms] Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel Bug reassigned from package

Bug#886510: OK now I installed libelf-dev, but...

OK now I did, # aptitude install libelf-dev The following NEW packages will be installed: libelf-dev The following packages will be REMOVED: linux-headers-4.14.0-1-amd64{pu} linux-headers-4.14.0-1-common{pu} (D: linux-headers-4.14.0-1-amd64) And now the error is gone, # aptitude reinstall

Processed: affects 886474

Processing commands for cont...@bugs.debian.org: > # See #886512 and #886510 > affects 886474 + nvidia-legacy-304xx-kernel-dkms broadcom-sta-dkms dkms Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: missing dependency on libelf-dev Bug #886510

Processed: merge 886470 886505

Processing commands for cont...@bugs.debian.org: > close 886505 Bug #886505 [nvidia-kernel-dkms] nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64 Marked Bug as done > merge 886470 886505 Bug #886470 {Done: Luca Boccassi } [nvidia-kernel-dkms]

Bug#886505: nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64

On Sat, 6 Jan 2018 23:48:07 +0100 Vincent Lefevre wrote: > Package: nvidia-kernel-dkms > Version: 384.98-3 > Severity: grave > Justification: renders package unusable >  > I get the following error when I want to start X: >  > [89.841] (EE) NVIDIA: Failed to initialize the

Bug#886417: linux-source-4.9: Kernel sources do not compile

Package: linux-source-4.9 Followup-For: Bug #886417 I am also using a custom config, trying to build a kernel for a old AMD Geode i386 machine (inside a i386 systemd-nspawn container running on a amd64 machine). -- System Information: Debian Release: 9.3 APT prefers stable-updates APT

Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

On Sat, Jan 6, 2018 at 12:45 PM, Antoine Beaupré wrote: > I'm fine with you pushing to collab-maint - this is what it's for after > all. :) Still, didn't want you to get surprised if you were working on it at the same time! > So even after this you still FTBFS? Did you

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

On 01/06/2018 08:08 PM, Niko Tyni wrote: > Running polymake currently fails with > > $ polymake > Can't locate loadable object for module Polymake::Ext in @INC > > Apparently this is because it was built with Perl 5.26.0, but > we've since moved to 5.26.1. > > I see two better alternatives: >

Bug#886382: Coming updates for meltdown/spectre

Hi Louis-Philippe! On Fri, 05 Jan 2018, Louis-Philippe Véronneau wrote: > > No, we don't know if they will release it *only* to vendors for a > > firmware update, or also for operating system updates. Also, for Zen > > and later one cannot just hope to update microcode through the operating > >

Bug#883987: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

Your message dated Sat, 06 Jan 2018 22:05:02 + with message-id and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5 has caused the Debian Bug report #883987, regarding FTBFS error: partial specialization ... after instantiation ... (with patch)

Bug#869994: proposed fix

Greetings all using FindBin and adding the current directory everywhere sql-ledger calls perl should fix the issue in all versions. An example perl script would be: perl -0777 -i.original -pe 's/(#!\/usr\/bin\/perl)/$1\n#perl 5.25 Fix:\nuse FindBin qw\(\$Bin\);\nuse lib \"\$Bin\"\;/igs' *.pl

Bug#884185: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

Your message dated Sat, 06 Jan 2018 22:05:02 + with message-id and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5 has caused the Debian Bug report #883987, regarding FTBFS error: partial specialization ... after instantiation ... (with patch)

Bug#884184: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

Your message dated Sat, 06 Jan 2018 22:05:02 + with message-id and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5 has caused the Debian Bug report #883987, regarding FTBFS error: partial specialization ... after instantiation ... (with patch)

Bug#884242: gdb-mingw-w64: diff for NMU version 10.4+nmu1

Control: tags 884242 + patch Control: tags 884242 + pending Dear maintainer, I've prepared an NMU for gdb-mingw-w64 (versioned as 10.4+nmu1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked

Processed: gdb-mingw-w64: diff for NMU version 10.4+nmu1

Processing control commands: > tags 884242 + patch Bug #884242 [src:gdb-mingw-w64] gdb-mingw-w64 FTBFS with g++-mingw-w64 7.2.0-16+20 Added tag(s) patch. > tags 884242 + pending Bug #884242 [src:gdb-mingw-w64] gdb-mingw-w64 FTBFS with g++-mingw-w64 7.2.0-16+20 Added tag(s) pending. -- 884242:

Bug#886489: FTBFS: json_object.c:554:5: error: this statement may fall through [-Werror=implicit-fallthrough=]

Control: forcemerge 853462 886489 Hey again, apparently I made a stupid mistake. This bug had already been filed and fixed some months ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853462 Since the NMU that fixed the bug had not been pushed to the packaging Git repo, I didn't spot it

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

Hi Christian and everyone else, Ack on reassign to Xen. On 01/06/2018 04:11 PM, Yves-Alexis Perez wrote: > control: reassign -1 xen-hypervisor-4.8-amd64 > > On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote: >> On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote: >>>

Processed: forcemerge

Processing commands for cont...@bugs.debian.org: > unarchive 853462 Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs with GCC-7 Unarchived Bug 853462 > forcemerge 853462 886489 Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs with

Bug#886505: nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64

Package: nvidia-kernel-dkms Version: 384.98-3 Severity: grave Justification: renders package unusable I get the following error when I want to start X: [89.841] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [89.841] (EE) NVIDIA: system's kernel log for

Bug#885989: chromium: MitM-ed TLS sites are being recognized as secure even though they are not

severity 885989 wishlist tags 885989 + wontfix thanks TemTem wrote: > A large portion of websites are being (willingly) attacked by > man-in-the-middles (MitM) such as Cloudflare. When someone commissions a service provider such as CloudFlare to host their web site CloudFlare then of course

Processed: Re: Bug#885989: chromium: MitM-ed TLS sites are being recognized as secure even though they are not

Processing commands for cont...@bugs.debian.org: > severity 885989 wishlist Bug #885989 [chromium] chromium: MitM-ed TLS sites are being recognized as secure even though they are not Severity set to 'wishlist' from 'grave' > tags 885989 + wontfix Bug #885989 [chromium] chromium: MitM-ed TLS

Processed: Close the bug

Processing control commands: > fixed 883526 1:1.4-3 Bug #883526 [src:geeqie] geeqie build does not trap errors from make Marked as fixed in versions geeqie/1:1.4-3. -- 883526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883526 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#883526: Close the bug

Control: fixed 883526 1:1.4-3 thanks Note to self: "Closing" doesn't close a bug, it must be "Closes". -- Andreas Rönnquist gus...@debian.org

Bug#856075: basilisk2: diff for NMU version 0.9.20120331-4.1

Quoting Adrian Bunk (2018-01-06 21:02:02) > I've prepared an NMU for basilisk2 (versioned as 0.9.20120331-4.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I should > cancel it. Excellent. Thanks a lot! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.:

Bug#856094: xpuzzles: diff for NMU version 7.7.1-1.1

Control: tags 856094 + patch Control: tags 856094 + pending Dear maintainer, I've prepared an NMU for xpuzzles (versioned as 7.7.1-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked

Processed: xpuzzles: diff for NMU version 7.7.1-1.1

Processing control commands: > tags 856094 + patch Bug #856094 [src:xpuzzles] xpuzzles: Please drop the (build-)dependency against esound Added tag(s) patch. > tags 856094 + pending Bug #856094 [src:xpuzzles] xpuzzles: Please drop the (build-)dependency against esound Added tag(s) pending. --

  1   2   >