Bug#954622: marked as done (jitterdebugger: FTBFS: jitterdebugger.c:139:14: error: static declaration of ‘gettid’ follows non-static declaration)

Your message dated Mon, 23 Mar 2020 03:50:28 + with message-id and subject line Bug#954622: fixed in jitterdebugger 0.3.1+git20200117.b90ff3a-1 has caused the Debian Bug report #954622, regarding jitterdebugger: FTBFS: jitterdebugger.c:139:14: error: static declaration of ‘gettid’ follows

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

On Sun, 2020-03-22 at 20:45 -0700, Felix Lechner wrote: > Well, that's what I did with xdeb, but it is causing #954415. BTW, re the lintian binary-is-wrong-architecture tag description, Emdebian no longer exists so it would be best to not mention it. > My inclination is yes, although personal

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Hi Paul, On Sun, Mar 22, 2020 at 8:40 PM Paul Wise wrote: > > Will the new Perl tests be enabled by default? Well, that's what I did with xdeb, but it is causing #954415. My inclination is yes, although personal profiles will soon become very tweakable. Kind regards Felix Lechner

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

On Sun, 2020-03-22 at 19:50 -0700, Felix Lechner wrote: > Regarding the 'affects' setting That just means that folks reporting bugs against lintian are more likely to see the existing pkg-perl-tools bug rather than filing another duplicate bug report like I did. > please know that the checks in

Bug#892344: literki: Please use 'pkg-config' to find FreeType 2

Package: literki Version: 0.0.0+20100113.git1da40724-1.2 Followup-For: Bug #892344 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/control: Build-depend on pkg-config. *

Bug#939260: marked as done (websploit: Python2 removal in sid/bullseye)

Your message dated Mon, 23 Mar 2020 03:09:08 + with message-id and subject line Bug#939260: fixed in websploit 4.0.4-1 has caused the Debian Bug report #939260, regarding websploit: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Hi Paul, On Sun, Mar 22, 2020 at 7:44 PM Paul Wise wrote: > > Yeah, doing with this mail. Regarding the 'affects' setting, please know that the checks in pkg-perl-tools will soon become part of Lintian (except perhaps the one requiring network access). It will reduce problems like this. Kind

Bug#938759: marked as done (urwid: Python2 removal in sid/bullseye)

Your message dated Mon, 23 Mar 2020 02:50:35 + with message-id and subject line Bug#938759: fixed in urwid 2.0.1-3 has caused the Debian Bug report #938759, regarding urwid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#954762: systraq: Annoying as Hell

Package: systraq Version: 20160803-3 Severity: critical Tags: security Justification: breaks unrelated software Dear Maintainer, You annoyed me with your jackass hourly cron job (once a day is sufficient) Now I'm annoying you. Enjoy Jackass Solution: uninstall Debian, go with a distro that

Bug#938294: marked as done (pyusb: Python2 removal in sid/bullseye)

Your message dated Mon, 23 Mar 2020 02:50:08 + with message-id and subject line Bug#938294: fixed in pyusb 1.0.2-2 has caused the Debian Bug report #938294, regarding pyusb: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Processing control commands: > reassign -1 pkg-perl-tools Bug #954761 [lintian] lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious Bug reassigned from package 'lintian' to 'pkg-perl-tools'. No longer marked as found in versions lintian/2.59.0 and

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Control: reassign -1 pkg-perl-tools Control: forcemerge 954331 -1 On Sun, 2020-03-22 at 18:35 -0700, Felix Lechner wrote: > This is #954331 in pkg-perl-tools, which is already done. > > Not sure how to best close this bug. Maybe 'forcemerge'? Yeah, doing with this mail. -- bye, pabs

Processed: affects 954761

Processing commands for cont...@bugs.debian.org: > affects 954761 lintian Bug #954761 [lintian] lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious Added indication that 954761 affects lintian > thanks Stopping processing here. Please contact me if you

Bug#954512: nextepc: FTBFS: sysctl.h:21:2: error: #warning "The header is deprecated and will be removed." [-Werror=cpp]

Hi Lucas, nextepc was deprecated. Please use open5gs( https://github.com/open5gs/open5gs) project. Thanks and regards, Sukchan On Sun, Mar 22, 2020 at 4:39 AM Lucas Nussbaum wrote: > Source: nextepc > Version: 0.3.10+nods-3 > Severity: serious > Justification: FTBFS on amd64 > Tags:

Bug#938759: marked as pending in urwid

Control: tag -1 pending Hello, Bug #938759 in urwid reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#938759 marked as pending in urwid

Processing control commands: > tag -1 pending Bug #938759 [src:urwid] urwid: Python2 removal in sid/bullseye Added tag(s) pending. -- 938759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#938294 marked as pending in pyusb

Processing control commands: > tag -1 pending Bug #938294 [src:pyusb] pyusb: Python2 removal in sid/bullseye Added tag(s) pending. -- 938294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#938294: marked as pending in pyusb

Control: tag -1 pending Hello, Bug #938294 in pyusb reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#954712 marked as pending in consul

Processing control commands: > tag -1 pending Bug #954712 [src:consul] consul: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 -short -failfast -timeout 8m github.com/hashicorp/consul [...] github.com/hashicorp/consul/version returned exit code 1 Added tag(s) pending. --

Bug#954712: marked as pending in consul

Control: tag -1 pending Hello, Bug #954712 in consul reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Hi Paul, On Sun, Mar 22, 2020 at 6:30 PM Paul Wise wrote: > > Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x556c92ea6f30), > "/usr/share/lintian/tags/pkg-perl/module-build-tiny-needs-newe"...) This is #954331 in pkg-perl-tools, which is already done. Not sure how to best close

Processed: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Processing control commands: > found -1 2.59.0 Bug #954761 [lintian] lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious Marked as found in versions lintian/2.59.0. -- 954761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954761 Debian Bug Tracking

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Package: lintian Version: 2.58.0 Severity: serious Control: found -1 2.59.0 Usertags: crash Whenever I run lintian (either source or binaries) I get the following crash. The configuration file and options used don't appear to cause this crash. It appears to happen with all packages I try. $

Bug#954639: gftp: FTBFS: pty.c:65:10: fatal error: stropts.h: No such file or directory

Package: gftp Version: 2.0.19-5 Followup-For: Bug #954639 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/glibc-2.30.patch: Fix FTBFS against glibc >= 2.30 with cherrypicked patch

Bug#953749: marked as done (ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x)

Your message dated Mon, 23 Mar 2020 00:22:10 + with message-id and subject line Bug#953749: fixed in ceph 14.2.8-2 has caused the Debian Bug report #953749, regarding ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x to be marked as done. This means that you claim that the problem

Bug#954482: marked as done (src:pyx3: Autopkgtest failure due to use of py3versions -i)

Your message dated Mon, 23 Mar 2020 00:09:10 + with message-id and subject line Bug#954482: fixed in pyx3 0.15-3 has caused the Debian Bug report #954482, regarding src:pyx3: Autopkgtest failure due to use of py3versions -i to be marked as done. This means that you claim that the problem has

Processed: Bug#953749 marked as pending in ceph

Processing control commands: > tag -1 pending Bug #953749 [src:ceph] ceph: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x Added tag(s) pending. -- 953749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#953749: marked as pending in ceph

Control: tag -1 pending Hello, Bug #953749 in ceph reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#954555: marked as done (safeclib: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

Your message dated Sun, 22 Mar 2020 23:37:01 + with message-id and subject line Bug#954555: fixed in safeclib 3.5-3 has caused the Debian Bug report #954555, regarding safeclib: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that

Bug#954756: puppet-module-aboe-chrony depends on obsolete transitional package.

Package: puppet-module-aboe-chrony Version: 0.2.4-2 Severity: serious puppet-module-aboe-chrony depends on the puppet-common transitional package which is no longer built by the puppet source package. Please update your dependencies.

Bug#954706: closing 954706

close 954706 2.2.7+dfsg-1 thanks this has been fixed with the upload of 2.2.7+dfsg-1 yesterday.

Bug#951916: proftpd-mod-vroot: proftpd cannot load mod_vroot

Control: severity -1 important Control: tags -1 + moreinfo Am 23.02.2020 um 04:27 teilte Nikolai Lusan mit: > Trying to run proftpd with mod_vroot. The following error causes hosts using > vroot to not be loaded: > > # service proftpd check-config > 2020-02-23 13:19:36,841 kiev

Processed: Re: Bug#951916: proftpd-mod-vroot: proftpd cannot load mod_vroot

Processing control commands: > severity -1 important Bug #951916 [proftpd-mod-vroot] proftpd-mod-vroot: proftpd cannot load mod_vroot Severity set to 'important' from 'grave' > tags -1 + moreinfo Bug #951916 [proftpd-mod-vroot] proftpd-mod-vroot: proftpd cannot load mod_vroot Added tag(s)

Bug#954555: safeclib: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

On Sun, Mar 22, 2020 at 09:24:01AM +0100, Lucas Nussbaum wrote: > Source: safeclib > Version: 3.5-2 > Severity: serious > Justification: FTBFS on amd64 > > FAIL: t_towfc_s > > === > > > > test_towfc_s 211 Error: towfc(U+A7C7) => A7C7 "A7C8" status=C LATIN > > CAPITAL LETTER D WITH

Bug#954644: marked as done (proftpd-mod-tar: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:22:51 +0100 with message-id <862c72d7-c54b-6e72-7702-fc15df0cd...@web.de> and subject line Re: Bug#954644: proftpd-mod-tar: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954644, regarding

Processed: closing 954706

Processing commands for cont...@bugs.debian.org: > close 954706 2.2.7+dfsg-1 Bug #954706 [src:vagrant] vagrant: FTBFS: Failed to load /dev/null because it doesn't contain valid YAML hash Marked as fixed in versions vagrant/2.2.7+dfsg-1. Bug #954706 [src:vagrant] vagrant: FTBFS: Failed to load

Bug#954526: marked as done (proftpd-mod-msg: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:19:35 +0100 with message-id <6204f1c6-98a9-2e02-ffd2-00ac6612f...@web.de> and subject line Re: Bug#954526: proftpd-mod-msg: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954526, regarding

Bug#954567: marked as done (proftpd-mod-fsync: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:17:27 +0100 with message-id and subject line Re: Bug#954567: proftpd-mod-fsync: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954567, regarding proftpd-mod-fsync: FTBFS: conf.h:57:11: fatal error:

Bug#954575: marked as done (proftpd-mod-dnsbl: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:14:34 +0100 with message-id and subject line Re: Bug#954575: proftpd-mod-dnsbl: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954575, regarding proftpd-mod-dnsbl: FTBFS: conf.h:57:11: fatal error:

Bug#885468: bumping severity of pygtk bugs

On Sun, Dec 15, 2019 at 10:40:56PM +0100, Moritz Mühlenhoff wrote: > On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote: > > Control: severity -1 serious > > Control: tags -1 -buster > > > > > > As part of the Python2 removal, it is our intent that pygtk will be removed > > from

Bug#954494: marked as done (proftpd-mod-counter: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:11:53 +0100 with message-id <6f8140a0-892b-3f8b-5eb7-60b855f15...@web.de> and subject line Re: Bug#954494: proftpd-mod-counter: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954494, regarding

Bug#954618: marked as done (proftpd-mod-clamav: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:10:06 +0100 with message-id <2928387a-5a0a-56fe-609b-5ab3ced7c...@web.de> and subject line Re: Bug#954618: proftpd-mod-clamav: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954618, regarding

Bug#954545: marked as done (proftpd-mod-autohost: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 23:06:59 +0100 with message-id and subject line Re: Bug#954545: proftpd-mod-autohost: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954545, regarding proftpd-mod-autohost: FTBFS: conf.h:57:11: fatal

Bug#954561: marked as done (proftpd-mod-case: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 22:54:45 +0100 with message-id <0cde1da8-f02f-401c-a247-94f742d71...@web.de> and subject line Re: Bug#954561: proftpd-mod-case: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954561, regarding

Bug#954621: marked as done (proftpd-mod-vroot: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory)

Your message dated Sun, 22 Mar 2020 22:51:04 +0100 with message-id <8205386b-f68c-f7a2-62d0-1315b380c...@web.de> and subject line Re: Bug#954621: proftpd-mod-vroot: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory has caused the Debian Bug report #954621, regarding

Processed: py2removal bugs severity updates - 2020-03-22 21:36:54.482537+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

Control: reassign -1 libdns-export1110 I think I see the problem: (sid-amd64)root@calcifer:/home/ondrej# ldd /usr/sbin/dhcpd linux-vdso.so.1 (0x7ffe5236a000) libeatmydata.so => /usr/lib/x86_64-linux-gnu/libeatmydata.so (0x7efc93c96000) libdns-export.so.1109 =>

Processed: Re: Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

Processing control commands: > reassign -1 libdns-export1110 Bug #954736 [bind9] Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT Bug reassigned from package 'bind9' to 'libdns-export1110'. No longer marked as found in versions bind9/1:9.16.1-2. Ignoring request to alter fixed versions of bug

Bug#954693: marked as done (node-promise: FTBFS: Error: Cannot find module 'acorn/dist/walk')

Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > node build > internal/modules/cjs/loader.js:

Bug#954720: marked as done (node-entities: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

Version: 2.0.0+dfsg-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' >

Bug#954694: marked as done (twitter-bootstrap4: FTBFS: Error: Too many arguments.)

: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p dist/css dist/js dist/tm

Bug#934842: marked as done (libbusiness-hours-perl: FTBFS in stretch)

Your message dated Sun, 22 Mar 2020 20:41:55 + with message-id and subject line Bug#934842: fixed in libbusiness-hours-perl 0.13-0+deb9u1 has caused the Debian Bug report #934842, regarding libbusiness-hours-perl: FTBFS in stretch to be marked as done. This means that you claim that the

Bug#830726: marked as done (xtrlock: CVE-2016-10894: xtrlock does not block multitouch events)

Your message dated Sun, 22 Mar 2020 20:42:49 + with message-id and subject line Bug#830726: fixed in xtrlock 2.8+deb9u1 has caused the Debian Bug report #830726, regarding xtrlock: CVE-2016-10894: xtrlock does not block multitouch events to be marked as done. This means that you claim that

Processed: Re: Bug#954573: quilt: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

Processing commands for cont...@bugs.debian.org: > reopen 954573 Bug #954573 {Done: Lucas Nussbaum } [src:quilt] quilt: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Bug reopened Ignoring request to alter fixed versions of bug #954573 to the same values previously

Bug#954689: ocsinventory-server: FTBFS: Error: Too many arguments.

Le 22/03/2020 à 14:56, Lucas Nussbaum a écrit : > Source: ocsinventory-server > Version: 2.5+dfsg1-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200322 ftbfs-bullseye > > Hi, > > During a rebuild of all packag

Bug#953488: marked as done (powder: binaries for non-free not auto-built)

Your message dated Sun, 22 Mar 2020 21:17:21 +0100 with message-id <20200322201721.gb8...@angband.pl> and subject line Re: powder_118+dfsg1-3_amd64.changes ACCEPTED into unstable, unstable has caused the Debian Bug report #953488, regarding powder: binaries for non-free not auto-built to be

Processed: Bug#954693 marked as pending in node-promise

Processing control commands: > tag -1 pending Bug #954693 [src:node-promise] node-promise: FTBFS: Error: Cannot find module 'acorn/dist/walk' Added tag(s) pending. -- 954693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954693 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#954693: marked as pending in node-promise

Control: tag -1 pending Hello, Bug #954693 in node-promise reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#954236: marked as done (python-bleach: CVE-2020-6816: mutation XSS)

Your message dated Sun, 22 Mar 2020 19:52:17 + with message-id and subject line Bug#954236: fixed in python-bleach 3.1.2-0+deb10u1 has caused the Debian Bug report #954236, regarding python-bleach: CVE-2020-6816: mutation XSS to be marked as done. This means that you claim that the problem

Bug#953322: marked as done (src:sec: fails to migrate to testing for too long)

Your message dated Sun, 22 Mar 2020 19:49:59 + with message-id and subject line Bug#953322: fixed in sec 2.8.2-1.1 has caused the Debian Bug report #953322, regarding src:sec: fails to migrate to testing for too long to be marked as done. This means that you claim that the problem has been

Bug#953320: marked as done (src:python-sievelib: fails to migrate to testing for too long)

Your message dated Sun, 22 Mar 2020 19:49:52 + with message-id and subject line Bug#953320: fixed in python-sievelib 1.1.1-3.1 has caused the Debian Bug report #953320, regarding src:python-sievelib: fails to migrate to testing for too long to be marked as done. This means that you claim

Processed: Bug#954694 marked as pending in twitter-bootstrap4

Processing control commands: > tag -1 pending Bug #954694 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: Error: Too many arguments. Added tag(s) pending. -- 954694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954694 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#954719: [Pkg-javascript-devel] Bug#954719: node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

Control: fixed -1 0.4.10-5 Le 22/03/2020 à 16:27, Lucas Nussbaum a écrit : > Source: node-immutable-tuple > Version: 0.4.10-3 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200322 ftbfs-bullseye > > Hi, > > Du

Bug#954694: marked as pending in twitter-bootstrap4

Control: tag -1 pending Hello, Bug #954694 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Re: [Pkg-javascript-devel] Bug#954719: node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

Processing control commands: > fixed -1 0.4.10-5 Bug #954719 [src:node-immutable-tuple] node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 Marked as fixed in versions node-immutable-tuple/0.4.10-5. -- 954719:

Bug#954719: marked as done (node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

-immutable-tuple Version: 0.4.10-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering direct

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

The src:bind9 package doesn’t even provide -dev package, so you are still compiling against 9.11. Ondrej -- Ondřej Surý > On 22 Mar 2020, at 20:09, Sven Hartge wrote: > > On 22.03.20 19:07, Sven Hartge wrote: > >> Interestingly, isc-dhcp-server 4.4.1 does not even compile against the >>

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

> On 22 Mar 2020, at 19:39, Sven Hartge wrote: > > Interestingly, isc-dhcp-server 4.4.1 does not even compile against the > current 9.16 libs from Sid right now. Something is very broken here. It should not. There’s bind9-libs compatibility package for isc-dhcp and others. Let’s keep the bug

Bug#954686: marked as done (mapsforge: FTBFS: Could not resolve :osmosis-core-0.47:.)

Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Set version string correctly

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

On 22.03.20 19:07, Sven Hartge wrote: > Interestingly, isc-dhcp-server 4.4.1 does not even compile against the > current 9.16 libs from Sid right now. Something is very broken here. I have to correct that part. It seems my checkout from Salsa was wrong, as recompiling the source package works.

Processed (with 1 error): forcibly merging 954574 949109

Processing commands for cont...@bugs.debian.org: > forcemerge 954574 949109 Bug #954574 [src:wmnd] wmnd: FTBFS: ../../src/drivers.c:36:10: fatal error: sys/stropts.h: No such file or directory Unable to merge bugs because: package of #949109 is 'wmnd' not 'src:wmnd' Failed to forcibly merge

Bug#938929: Dependency problem with iptables and libvirt-daemon-system

Control: severity -1 normal Control: tags -1 moreinfo Hi, On Fri, Aug 30, 2019 at 12:45:16PM +0200, Julian Hyordey wrote: > apt show libvirt-daemon-system > Package: libvirt-daemon-system > Version: 5.0.0-4 > Priority: optional > Section: admin > Source: libvirt > Maintainer: Debian Libvirt

Processed: Re: Dependency problem with iptables and libvirt-daemon-system

Processing control commands: > severity -1 normal Bug #938929 [libvirt-daemon-system] Dependency problem with iptables and libvirt-daemon-system Severity set to 'normal' from 'grave' > tags -1 moreinfo Bug #938929 [libvirt-daemon-system] Dependency problem with iptables and

Bug#925709: marked as done (gsasl: ftbfs with GCC-9)

Your message dated Sun, 22 Mar 2020 19:35:03 +0100 with message-id <20200322183501.ga6...@debian.org> and subject line Re: gsasl: ftbfs with GCC-9 has caused the Debian Bug report #925709, regarding gsasl: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

Package: bind9 Version: 1:9.16.1-2 Severity: critical Justification: breaks unrelated packages Hi! The recent upgrade from 1:9.11.16+dfsg-2 to 1:9.16.1-1 causes isc-dhcp-server to die upon start with SIGABRT, creating the following backtrace: 8<

Processed: tagging 932725

Processing commands for cont...@bugs.debian.org: > # mips is no longer in testing or unstable > tags 932725 + buster Bug #932725 [src:libunwind] libunwind8: segfault on MIPS, fix needs backporting Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#954610: marked as done (golang-logrus: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/sirupsen/logrus github.com/sirupsen/logrus/hooks/syslog github.com

Your message dated Sun, 22 Mar 2020 18:22:08 + with message-id and subject line Bug#954610: fixed in golang-logrus 1.4.2.98.gd417be0-1 has caused the Debian Bug report #954610, regarding golang-logrus: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4

Bug#954729: src:mesa: X won't start after upgrading mesa

On 22.3.2020 17.38, Chow Loong Jin wrote: > Package: src:mesa > Version: 20.0.2-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > >> * What led up to the situation? > > Upgraded mesa packages from 19.3.3-1 to 20.0.2-1. > >> * What exactly did you do (or not

Bug#954579: datalad-container: FTBFS: build-dependency not installable: datalad (>= 0.11.5~)

On Sun, 22 Mar 2020, Lucas Nussbaum wrote: > Source: datalad-container > Version: 0.5.0-1 Thank you for the report. 1.0.0-1 was built but forgotten to be uploaded at the end of Feb. Now it would need to wait until datalad 0.12.4 is uploaded first which would resolve incompatibilities with

Processed: bug 954549 is forwarded to https://github.com/json-iterator/go/issues/419

Processing commands for cont...@bugs.debian.org: > forwarded 954549 https://github.com/json-iterator/go/issues/419 Bug #954549 [src:golang-github-json-iterator-go] golang-github-json-iterator-go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4

Bug#954675: marked as done (phpdox: FTBFS: dh_installman: error: Could not determine section for ./debian/tmp/phpdox.1)

: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir debian/tmp > cd de

Processed: limit source to phpdox, tagging 954675

Processing commands for cont...@bugs.debian.org: > limit source phpdox Limiting to bugs with field 'source' containing at least one of 'phpdox' Limit currently set to 'source':'phpdox' > tags 954675 + pending Bug #954675 [src:phpdox] phpdox: FTBFS: dh_installman: error: Could not determine

Bug#954451: marked as done (src:tox: Please remove python2 autopkgtests that use virtualenv)

Your message dated Sun, 22 Mar 2020 16:34:45 + with message-id and subject line Bug#954451: fixed in tox 3.13.2-2 has caused the Debian Bug report #954451, regarding src:tox: Please remove python2 autopkgtests that use virtualenv to be marked as done. This means that you claim that the

Bug#954690: [Pkg-utopia-maintainers] Bug#954690: udisks2: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

Am 22.03.20 um 14:43 schrieb Lucas Nussbaum: > Source: udisks2 > Version: 2.8.4-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200322 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your pack

Bug#954451: marked as pending in tox

Control: tag -1 pending Hello, Bug #954451 in tox reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#954451 marked as pending in tox

Processing control commands: > tag -1 pending Bug #954451 [src:tox] src:tox: Please remove python2 autopkgtests that use virtualenv Added tag(s) pending. -- 954451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#954583 marked as pending in sahara

Processing control commands: > tag -1 pending Bug #954583 [src:sahara] sahara: FTBFS: make[1]: pyversions: Command not found Added tag(s) pending. -- 954583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#954583: marked as pending in sahara

Control: tag -1 pending Hello, Bug #954583 in sahara reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: tagging 954566

Processing commands for cont...@bugs.debian.org: > tags 954566 + confirmed Bug #954566 [src:cura-engine] cura-engine: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me

Bug#954729: src:mesa: X won't start after upgrading mesa

Package: src:mesa Version: 20.0.2-1 Severity: critical Justification: breaks the whole system Dear Maintainer, > * What led up to the situation? Upgraded mesa packages from 19.3.3-1 to 20.0.2-1. > * What exactly did you do (or not do) that was effective (or > ineffective)? Tried to boot >

Processed: fixed 952946 in 1:9.11.17-1, fixed 952946 in 1:9.16.0-1

Processing commands for cont...@bugs.debian.org: > fixed 952946 1:9.11.17-1 Bug #952946 [src:bind9] bind9: Replace PKCS11 headers provided by OASIS The source 'bind9' and version '1:9.11.17-1' do not appear to match any binary packages Marked as fixed in versions bind9/1:9.11.17-1. > fixed

Bug#954722: spring: FTBFS: unistd_ext.h:34:16: error: conflicting declaration of ‘__pid_t gettid()’ with ‘C’ linkage

Source: spring Version: 104.0+dfsg-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux

Bug#954720: node-entities: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

Source: node-entities Version: 2.0.0+dfsg-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

Bug#954721: pry: FTBFS: ERROR: Test "ruby2.7" failed. Could not find 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] (Gem::MissingSpecVersionError)

Source: pry Version: 0.12.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-t

Bug#954723: golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/scopestack returned exit code 2

Source: golang-github-mendersoftware-scopestack Version: 0.0~git20180403.c2f5599-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

Bug#954725: datatables-extensions: FTBFS: Parse error

Source: datatables-extensions Version: 0.0+git20150910.28fd64e+dfsg-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#954726: mftrace: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2

Source: mftrace Version: 1.2.20+git20191022.3b4bc2e-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > mak

Bug#954719: node-immutable-tuple: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

Source: node-immutable-tuple Version: 0.4.10-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

Bug#954724: ruby-guard: FTBFS: ERROR: Test "ruby2.7" failed. Could not find 'method_source' (~> 0.9.0) - did find: [method_source-1.0.0] (Gem::MissingSpecVersionError)

Source: ruby-guard Version: 2.16.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200322 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/

Processed: Bug#952199 marked as pending in golang-github-boltdb-bolt

Processing control commands: > tag -1 pending Bug #952199 [src:golang-github-boltdb-bolt] golang-github-boltdb-bolt: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt returned exit code 1 Added tag(s)

  1   2   3   4   5   >