Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)

reopen 960327 thanks On Saturday, May 16 2020, Luigi Gangitano wrote: > Hi Sergio, > >> On 14 May 2020, at 05:42, Sergio Durigan Junior wrote: >> >> Here's a patch that fixes the issue above. >> >> Please note that even after fixing this specific issue, I still see >> another failure with

Bug#906870: marked as done (xul-ext-certificatepatrol no longer works with firefox-esr 60)

Your message dated Wed, 20 May 2020 13:39:05 + with message-id and subject line Bug#960959: Removed package(s) from unstable has caused the Debian Bug report #906870, regarding xul-ext-certificatepatrol no longer works with firefox-esr 60 to be marked as done. This means that you claim that

Processed: Re: Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)

Processing commands for cont...@bugs.debian.org: > reopen 960327 Bug #960327 {Done: Luigi Gangitano } [src:squid] squid: autopkgtest regression: test_daemons (__main__.BasicTest) 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you

Bug#961120: marked as done (nulib2 ftbfs on s390x (failing tests), built before)

Your message dated Wed, 20 May 2020 16:04:24 + with message-id and subject line Bug#961120: fixed in nulib2 3.1.0-4 has caused the Debian Bug report #961120, regarding nulib2 ftbfs on s390x (failing tests), built before to be marked as done. This means that you claim that the problem has

Bug#961126: marked as done (fig2dev fails autopkg test with stderr output on 32bit archs)

Your message dated Wed, 20 May 2020 16:49:03 + with message-id and subject line Bug#961126: fixed in fig2dev 1:3.2.7b-4 has caused the Debian Bug report #961126, regarding fig2dev fails autopkg test with stderr output on 32bit archs to be marked as done. This means that you claim that the

Processed: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

Processing control commands: > found -1 ucf/3.0039 Bug #961144 [src:ucf, src:bacula] ucf breaks bacula autopkgtest: Job for bacula-director.service failed Marked as found in versions ucf/3.0039. > found -1 bacula/9.6.3-1 Bug #961144 [src:ucf, src:bacula] ucf breaks bacula autopkgtest: Job for

Bug#961144: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

Source: ucf, bacula Control: found -1 ucf/3.0039 Control: found -1 bacula/9.6.3-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ucf the autopkgtest of bacula

Processed: bug 961126 is forwarded to https://sourceforge.net/p/mcj/tickets/94/

Processing commands for cont...@bugs.debian.org: > forwarded 961126 https://sourceforge.net/p/mcj/tickets/94/ Bug #961126 [src:fig2dev] fig2dev fails autopkg test with stderr output on 32bit archs Set Bug forwarded-to-address to 'https://sourceforge.net/p/mcj/tickets/94/'. > thanks Stopping

Processed: bcalm: diff for NMU version 2.2.2-1.1

Processing control commands: > tags 960876 + patch Bug #960876 [src:bcalm] bcalm: autopkgtest regression: python: command not found Added tag(s) patch. -- 960876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#960876: bcalm: diff for NMU version 2.2.2-1.1

Control: tags 960876 + patch Dear maintainer, I've prepared an NMU for bcalm (versioned as 2.2.2-1.1). The diff is attached to this message. Regards. SR diff -Nru bcalm-2.2.2/debian/bcalm.install bcalm-2.2.2/debian/bcalm.install --- bcalm-2.2.2/debian/bcalm.install 2020-05-05

Bug#960876: marked as done (bcalm: autopkgtest regression: python: command not found)

Your message dated Wed, 20 May 2020 16:18:47 + with message-id and subject line Bug#960876: fixed in bcalm 2.2.2-1.1 has caused the Debian Bug report #960876, regarding bcalm: autopkgtest regression: python: command not found to be marked as done. This means that you claim that the problem

Bug#961088: bug confirmed

Hi, I have the same problem with an HP Officejet 7310 AIO: sane-find-scanner reports: "found USB scanner (vendor=0x03f0 [HP], product=0x4211 [Officejet 7300 series]) at libusb:002:012" but "scanimage -L" fails: "No scanners were identified." Unfortunately, I wasn't able to downgrade to

Bug#959619: urwid: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13

I see this on the Launchpad buildds, building the package. Adding a build dependency on locales-all fixes this. I assume that the same dependency needs to be added for the autopkg test.

Bug#947827: marked as done (Missing symbols in -lblas ?)

Your message dated Wed, 20 May 2020 15:18:48 + with message-id and subject line Bug#947827: fixed in atlas 3.10.3-10 has caused the Debian Bug report #947827, regarding Missing symbols in -lblas ? to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Re: Bug#960773: gr-gsm: FTBFS on s390x

Processing control commands: > retitle -1 gr-gsm FTBFS on big endian Bug #960773 [src:gr-gsm] gr-gsm: FTBFS on s390x Changed Bug title to 'gr-gsm FTBFS on big endian' from 'gr-gsm: FTBFS on s390x'. -- 960773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960773 Debian Bug Tracking System

Bug#960773: gr-gsm: FTBFS on s390x

Control: retitle -1 gr-gsm FTBFS on big endian On Sat, May 16, 2020 at 03:09:07PM +0200, Sebastian Ramacher wrote: > Source: gr-gsm > Version: 0.42.2.20200214-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > gr-gsm failed to

Bug#961131: freecad: autopkgtest regression with opencascade 7.4

Source: freecad Version: 0.18.4+dfsg2-2 Tags: patch X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Freecad fails its autopkgtests with opencascade 7.4 [1]: testTaperedHole (PartDesignTests.TestHole.TestHole) ...

Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE

When I upgraded to buster I disabled deb-multimedia and I forgot to enable it again. After enabling deb-multimedia repository for buster and upgrading the packages, mkvtoolnix-gui worked again. Thanks for the advice. Regards -- Mauro On Wed, May 20, 2020, 04:35 Phil Wyett wrote: > On Wed,

Bug#961120: nulib2 ftbfs on s390x (failing tests), built before

Le 20/05/2020 13:02, Matthias Klose a écrit : nulib2 ftbfs on s390x (failing tests), built before: Thanks, the tests fail on all 64-bit big-endian platforms: ERROR: kNuAttrNumRecords 12884901888 vs 3 12884901888 is 0x3 ;-). I’ll look into it... Regards, Stephen

Bug#961126: fig2dev fails autopkg test with stderr output on 32bit archs

Package: src:fig2dev Version: 1:3.2.7b-3 Severity: serious Tags: sid bullseye patch fig2dev fails autopkg test with stderr output on 32bit archs make test1 make[1]: Entering directory '/tmp/autopkgtest.No5cFl/build.GqQ/src/fig2dev/tests' gcc -DHAVE_CONFIG_H -I. -I../..

Processed: Re: Bug#960892 closed by Debian FTP Masters (reply to to...@debian.org (Dr. Tobias Quathamer)) (Bug#960892: fixed in po4a 0.59-1)

Processing control commands: > reopen -1 Bug #960892 {Done: to...@debian.org (Dr. Tobias Quathamer)} [po4a] po4a: --srcdir ignored by [po_directory] '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 them. Bug

Processed: Partially solved

Processing control commands: > severity -1 important Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch Bug #960659 [src:cyrus-imapd] cyrus-imapd: Test failure on big endian Bug #960660 [src:cyrus-imapd] cyrus-imapd: Test failure on armhf (at least on armv8)

Bug#960658: Partially solved

Control: severity -1 important This bug is partially fixed in version 3.2.0-5. Keeping it opened due to: * some unimportant tests still fail (disabled in 3.2.0-5) * build still fail for hppa and sparc64 [1] [1]: https://buildd.debian.org/status/logs.php?pkg=cyrus-imapd=3.2.0-5

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

On Thu, May 07, 2020 at 07:52:31PM +0200, Julien Cristau wrote: > On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote: > > On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > > > This use of Provides is not acceptable. The systemctl package does not > > > in any way provide

Bug#959455: marked as done (fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers)

Your message dated Wed, 20 May 2020 22:03:42 + with message-id and subject line Bug#959455: fixed in fakeroot-ng 0.18-4.1 has caused the Debian Bug report #959455, regarding fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers to be marked as done. This means that you claim

Bug#961088: Acknowledgement (libsane-hpaio fails to detect HP MFDs)

Hi, my issue is plain and simple: libsane.hpaio.1.0.0 is no longer dlopen()able due to an unresolved symbol '_DBG', used in scan/sane/orblite.c:198. You can check this easily by running scanimage with envvar SANE_DEBUG_DLL=1: = ] jan@p53:~$ SANE_DEBUG_DLL=1 scanimage -d

Bug#959138: nipy: resolve nipy autopkgtest failure due to numpy testing decorators

Source: nipy Followup-For: Bug #959138 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy ubuntu-patch Dear Maintainer, While working on numpy proposed-migration for groovy, I realize nipy autopkgtest was failing. It appears that numpy changed the pass to the module decorators

Bug#960892: closed by Debian FTP Masters (reply to to...@debian.org (Dr. Tobias Quathamer)) (Bug#960892: fixed in po4a 0.59-1)

Control: reopen -1 Control: notfixed -1 0.59-1 Hi, Debian Bug Tracking System wrote: > - po4a tool: Fix --srcdir handling. This bug was breaking the build >of several packages, including dpkg. (Closes: #960892) I'm sorry to report, but this is not fixed for aptitude. > previously

Bug#961060: qmail-verify: CVE-2020-3811 CVE-2020-3812

Control: tags -1 + patch On Tue, May 19, 2020 at 07:30:53PM +0200, Salvatore Bonaccorso wrote: > Source: netqmail > Version: 1.06-6.1 > Severity: grave > Tags: security upstream > Justification: user security hole > Control: found -1 1.06-6 > Control: found -1 1.06-5 > > Hi > > See

Processed: Re: Bug#961060: qmail-verify: CVE-2020-3811 CVE-2020-3812

Processing control commands: > tags -1 + patch Bug #961060 [src:netqmail] qmail-verify: CVE-2020-3811 CVE-2020-3812 Added tag(s) patch. -- 961060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

Processing commands for cont...@bugs.debian.org: > tags 961144 +moreinfo Bug #961144 [src:ucf, src:bacula] ucf breaks bacula autopkgtest: Job for bacula-director.service failed Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 961144:

Bug#961144: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

The usage of ucf in debian/bacula-director.postinst seems fine. Manoj -- Nothing ever becomes real till it is experienced -- even a proverb is no proverb to you till your life has illustrated it. -- John Keats Manoj Srivastava 4096R/C5779A1C E37E 5EC5

Bug#961144: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

Hi, There is very little actionable in the bug report. We can’t see the ucf invocation, nor do we see any error messages that might point us to the root cause. The last lines in the logs: --8<---cut here---start->8--- service bacula-director

Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl

Package: libcolor-calc-perl Version: 1.074-2 Severity: grave Tags: bullseye sid X-Debbugs-Cc: libgraphics-colornames-p...@packages.debian.org Color::Calc uses Graphics::ColorNames::HTML, which was recently dropped from the libgraphics-colornames-perl package in Debian. Graphics::ColorNames::HTML

Bug#961148: libgraphics-colorobject-perl: broken by new libgraphics-colornames-perl

Package: libgraphics-colorobject-perl Version: 0.5.0-7.1 Severity: grave Tags: bullseye sid Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=127300 Graphics::ColorObject needs Graphics::ColorNames::HTML, which was recently dropped from the libgraphics-colornames-perl package in Debian.

Processed: Bug#961049 marked as pending in sra-sdk

Processing control commands: > tag -1 pending Bug #961049 [src:sra-sdk] sra-sdk FTBFS with libncbi-vdb-dev 2.10.6+dfsg-1 Added tag(s) pending. -- 961049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#961049: marked as pending in sra-sdk

Control: tag -1 pending Hello, Bug #961049 in sra-sdk 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#953897: marked as done (libncbi-vdb2 uses undefined symbols)

Your message dated Thu, 21 May 2020 02:36:31 + with message-id and subject line Bug#952627: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #952627, regarding libncbi-vdb2 uses undefined symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#953897: marked as done (libncbi-vdb2 uses undefined symbols)

Your message dated Thu, 21 May 2020 02:36:32 + with message-id and subject line Bug#953897: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #953897, regarding libncbi-vdb2 uses undefined symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#952623: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init')

Your message dated Thu, 21 May 2020 02:36:32 + with message-id and subject line Bug#953897: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #953897, regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' to

Bug#961049: marked as done (sra-sdk FTBFS with libncbi-vdb-dev 2.10.6+dfsg-1)

Your message dated Thu, 21 May 2020 02:36:39 + with message-id and subject line Bug#961049: fixed in sra-sdk 2.10.6+dfsg-1 has caused the Debian Bug report #961049, regarding sra-sdk FTBFS with libncbi-vdb-dev 2.10.6+dfsg-1 to be marked as done. This means that you claim that the problem has

Bug#952623: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init')

Your message dated Thu, 21 May 2020 02:36:31 + with message-id and subject line Bug#952623: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #952623, regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' to

Bug#961148: marked as done (libgraphics-colorobject-perl: broken by new libgraphics-colornames-perl)

Your message dated Thu, 21 May 2020 03:04:22 + with message-id and subject line Bug#961148: fixed in libgraphics-colorobject-perl 0.5.0-9 has caused the Debian Bug report #961148, regarding libgraphics-colorobject-perl: broken by new libgraphics-colornames-perl to be marked as done. This

Bug#952627: marked as done (libncbi-vdb2 uses undefined symbols)

Your message dated Thu, 21 May 2020 02:36:32 + with message-id and subject line Bug#953897: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #953897, regarding libncbi-vdb2 uses undefined symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#953897: marked as done (libncbi-vdb2 uses undefined symbols)

Your message dated Thu, 21 May 2020 02:36:31 + with message-id and subject line Bug#952623: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #952623, regarding libncbi-vdb2 uses undefined symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#952627: marked as done (libncbi-vdb2 uses undefined symbols)

Your message dated Thu, 21 May 2020 02:36:31 + with message-id and subject line Bug#952623: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #952623, regarding libncbi-vdb2 uses undefined symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#952627: marked as done (libncbi-vdb2 uses undefined symbols)

Your message dated Thu, 21 May 2020 02:36:31 + with message-id and subject line Bug#952627: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #952627, regarding libncbi-vdb2 uses undefined symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#952623: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init')

Your message dated Thu, 21 May 2020 02:36:31 + with message-id and subject line Bug#952627: fixed in ncbi-vdb 2.10.6+dfsg-2 has caused the Debian Bug report #952627, regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init' to

Bug#961191: src:python-traceback2: fails to migrate to testing for too long: makes python-unittest2 non-installable

Source: python-traceback2 Version: 1.4.0-5 Severity: serious Control: close -1 1.4.0-6 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing

Processed: src:python-traceback2: fails to migrate to testing for too long: makes python-unittest2 non-installable

Processing control commands: > close -1 1.4.0-6 Bug #961191 [src:python-traceback2] src:python-traceback2: fails to migrate to testing for too long: makes python-unittest2 non-installable Marked as fixed in versions python-traceback2/1.4.0-6. Bug #961191 [src:python-traceback2]

Bug#959236: Bonding doesn't work

Bonding doesn't work. Same behavior here. Debian bullseye/sid 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth (1000) reached

Bug#961103: headache FTBFS: Error: Unbound module UTF8

Source: headache Version: 1.03-30 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=headache=sid ... /usr/bin/make all make[2]: Entering directory '/<>' /usr/bin/ocamlc -I +extlib extLib.cma -c info.ml /usr/bin/ocamlc -I +extlib extLib.cma -c skip.ml /usr/bin/ocamlc -I

Processed: limit source to headache, tagging 961103

Processing commands for cont...@bugs.debian.org: > limit source headache Limiting to bugs with field 'source' containing at least one of 'headache' Limit currently set to 'source':'headache' > tags 961103 + pending Bug #961103 [src:headache] headache FTBFS: Error: Unbound module UTF8 Added

Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE

> On Tue, 2020-05-19 at 22:05 -0300, Mauro Dionisi wrote: > > Versions of packages mkvtoolnix-gui depends on: > > ii libebml4v5 1:1.3.9-dmo0+deb9u1 > > ii libmatroska6v5 1:1.4.5-dmo1 Hello, might this be related to the above packages being from the debian multimedia

Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE

On Wed, 2020-05-20 at 09:28 +0200, Bernhard Übelacker wrote: > > On Tue, 2020-05-19 at 22:05 -0300, Mauro Dionisi wrote: > > > Versions of packages mkvtoolnix-gui depends on: > > > ii libebml4v5 1:1.3.9-dmo0+deb9u1 > > > ii libmatroska6v5 1:1.4.5-dmo1 > > Hello, >

Bug#961104: t4kcommon FTBFS on !amd64

Source: t4kcommon Version: 0.1.1-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=t4kcommon=sid ... dh_missing -a dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.a exists in debian/tmp but is not installed to anywhere (related file:

Bug#961107: slic3r-prusa FTBFS on mipsel and i386

Source: slic3r-prusa Version: 2.2.0+dfsg1-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=mipsel=2.2.0%2Bdfsg1-1=1586422709=0 ... virtual memory exhausted: Cannot allocate memory make[3]: ***

Bug#961095: marked as done (mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE)

Your message dated Wed, 20 May 2020 09:05:37 +0200 with message-id <20200520070537.ga489...@ramacher.at> and subject line Re: Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE has caused the Debian Bug report #961095,

Processed: bug 956083 is forwarded to https://github.com/k0lter/autopostgresqlbackup/issues/2

Processing commands for cont...@bugs.debian.org: > forwarded 956083 https://github.com/k0lter/autopostgresqlbackup/issues/2 Bug #956083 [autopostgresqlbackup] autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups Set Bug forwarded-to-address to

Bug#961104: marked as done (t4kcommon FTBFS on !amd64)

Your message dated Wed, 20 May 2020 08:48:55 + with message-id and subject line Bug#961104: fixed in t4kcommon 0.1.1-9 has caused the Debian Bug report #961104, regarding t4kcommon FTBFS on !amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#960892: po4a: --srcdir ignored by [po_directory]

Hello, your patch was included in an upstream release. The debian package should be updated shortly. Thanks for your patience, Mt. -- You have a problem and decide to use floats. Now you have 2.0001 problems. signature.asc Description: PGP signature

Bug#959236: ifenslave bonding doesn't work. Same here

After the last dist-upgrade bonding stopped working. I am using bullseye/sid and 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux The "dist-upgrade" warned about not using ifenslave anymore but iproute2, so I tried to see how this would

Bug#961104: t4kcommon FTBFS on !amd64

Hi Adrian, On Wed, May 20, 2020 at 09:41:16AM +0300, Adrian Bunk wrote: > Source: t4kcommon > Version: 0.1.1-8 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=t4kcommon=sid > > ... >dh_missing -a > dh_missing: warning:

Bug#961104: t4kcommon FTBFS on !amd64

On Wed, May 20, 2020 at 11:17:49AM +0300, Adrian Bunk wrote: > the paths do not include "x86_64-linux-gnu" on other architectures, I was aware of this... > you should write these as > usr/lib/*/libt4k_common.a > usr/lib/*/libt4k_common.la but not that I could use wildcards here. Thank you!

Bug#926539: rootskel: steal-ctty no longer works on s390x

Similar change for console name on s390x was not accepted: https://lkml.org/lkml/2020/5/19/854 so please fix in rootskel. -- Valentin

Bug#961104: t4kcommon FTBFS on !amd64

On Wed, May 20, 2020 at 08:12:35AM +, Holger Levsen wrote: > Hi Adrian, Hi Holger, >... > I was surprised when I added these lines to debian/not-installed for > the 0.1.1-8 upload: > > usr/lib/x86_64-linux-gnu/libt4k_common.a > usr/lib/x86_64-linux-gnu/libt4k_common.la > > however as I

Bug#960998: marked as done (r-cran-av: broken symlink /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3)

Your message dated Wed, 20 May 2020 08:37:17 + with message-id and subject line Bug#960998: fixed in r-cran-av 0.5.0+dfsg-3 has caused the Debian Bug report #960998, regarding r-cran-av: broken symlink /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3 to be marked as done. This

Bug#960892: marked as done (po4a: --srcdir ignored by [po_directory])

Your message dated Wed, 20 May 2020 09:04:00 + with message-id and subject line Bug#960892: fixed in po4a 0.59-1 has caused the Debian Bug report #960892, regarding po4a: --srcdir ignored by [po_directory] to be marked as done. This means that you claim that the problem has been dealt with.

Bug#926539: rootskel: steal-ctty no longer works on s390x

Hi! On 5/20/20 11:00 AM, Valentin Vidić wrote: > Similar change for console name on s390x was not accepted: > > https://lkml.org/lkml/2020/5/19/854 > > so please fix in rootskel. I don't see any discussion in this thread. I would like to know the reasoning why kernel upstream thinks that

Bug#926539: rootskel: steal-ctty no longer works on s390x

On 5/20/20 11:17 AM, John Paul Adrian Glaubitz wrote: > I don't see any discussion in this thread. I would like to know the reasoning > why kernel upstream thinks that this naming inconsistency is correct. It > makes no sense, in my opinion and it can potentially trigger more problems. Ah, sorry.

Bug#961116: gnome-shell-extension-suspend-button: Does not work with gnome 3.36

Package: gnome-shell-extension-suspend-button Version: 0~git20191005-1 Severity: serious Control: tags -1 upstream Control: forwarded -1 https://github.com/laserb/gnome-shell-extension-suspend-button/issues/53 This extension is currently not compatible with gnome 3.36 and it is unclear if it

Bug#952868: marked as done (OpenSSL linking without license exception)

Your message dated Wed, 20 May 2020 10:23:02 + with message-id and subject line Bug#952868: fixed in wesnoth-1.14 1:1.14.12-1 has caused the Debian Bug report #952868, regarding OpenSSL linking without license exception to be marked as done. This means that you claim that the problem has

Bug#901382: node-katex is now split into katex (which include katex command and provides node-katex), libjs-katex and fonts-katex

Control: block -1 by 961005 This is fixed in git along with update to 0.10.2 but blocked by node-less (need new upstream version).

Processed: node-katex is now split into katex (which include katex command and provides node-katex), libjs-katex and fonts-katex

Processing control commands: > block -1 by 961005 Bug #901382 [node-katex] node-katex: must build binary packages fonts-katex and libjs-katex 901382 was not blocked by any bugs. 901382 was not blocking any bugs. Added blocking bug(s) of 901382: 961005 -- 901382:

Bug#945744: marked as done (wesnoth-1.14: Python2 removal in sid/bullseye)

Your message dated Wed, 20 May 2020 10:23:02 + with message-id and subject line Bug#945744: fixed in wesnoth-1.14 1:1.14.12-1 has caused the Debian Bug report #945744, regarding wesnoth-1.14: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#926539: rootskel: steal-ctty no longer works on s390x

On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote: > Ah, sorry. I was seeing the cached version of the thread, refreshing helped. > > In any case, the SPARC kernel maintainer (Dave Miller) had the same argument > that it would potentially break existing setups but

Bug#960660: cyrus-imapd: Test failure on armhf (at least on armv8)

Hi, with upstream help; I just built cyrus-imapd_3.2.0-4 which may fix this issue. @Adrian, could you test this on your armv8 ? Cheers, Xavier

Bug#960660: cyrus-imapd: Test failure on armhf (at least on armv8)

Le 20/05/2020 à 11:26, Xavier a écrit : > Hi, > > with upstream help; I just built cyrus-imapd_3.2.0-4 which may fix this > issue. > @Adrian, could you test this on your armv8 ? > > Cheers, > Xavier Note that there are still 4 tests that fail [1] (failed already at least with i386). I'm waiting

Bug#959225: libcap-ng: diff for NMU version 0.7.9-2.2

Package: libcap-ng Version: 0.7.9-2.1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for libcap-ng (versioned as 0.7.9-2.2) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards, Håvard diff -Nru libcap-ng-0.7.9/debian/changelog

Processed: gnome-shell-extension-suspend-button: Does not work with gnome 3.36

Processing control commands: > tags -1 upstream Bug #961116 [gnome-shell-extension-suspend-button] gnome-shell-extension-suspend-button: Does not work with gnome 3.36 Added tag(s) upstream. > forwarded -1 > https://github.com/laserb/gnome-shell-extension-suspend-button/issues/53 Bug #961116

Bug#961103: marked as done (headache FTBFS: Error: Unbound module UTF8)

Your message dated Wed, 20 May 2020 10:48:51 + with message-id and subject line Bug#961103: fixed in headache 1.04-1 has caused the Debian Bug report #961103, regarding headache FTBFS: Error: Unbound module UTF8 to be marked as done. This means that you claim that the problem has been dealt

Bug#926539: rootskel: steal-ctty no longer works on s390x

On 5/20/20 12:42 PM, Valentin Vidić wrote: > It is hard to tell, but it seems the current state is hardcoded > in different places: > > https://www.redhat.com/archives/libguestfs/2017-May/msg00068.html This wouldn't cause breakage as with your change, the console name would actually be ttysclp0.

Processed (with 1 error): merge bugs

Processing commands for cont...@bugs.debian.org: > merge 961056 926539 Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails due to incorrect serial device Unable to merge bugs because: severity of #926539 is 'serious' not 'important' package of #926539 is

Bug#961120: nulib2 ftbfs on s390x (failing tests), built before

Package: src:nulib2 Version: 3.1.0-3 Severity: serious Tags: sid bullseye nulib2 ftbfs on s390x (failing tests), built before: debian/rules override_dh_auto_test make[1]: Entering directory '/<>' nufxlib/samples/test-basic ERROR: kNuAttrNumRecords 12884901888 vs 3 Using NuFX library v3.1.0,

Processed: bug 960658 is forwarded to https://github.com/cyrusimap/cyrus-imapd/issues/3040

Processing commands for cont...@bugs.debian.org: > forwarded 960658 https://github.com/cyrusimap/cyrus-imapd/issues/3040 Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch Bug #960659 [src:cyrus-imapd] cyrus-imapd: Test failure on big endian Bug #960660

Processed: merge

Processing commands for cont...@bugs.debian.org: > reassign 961056 src:linux,rootskel Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails due to incorrect serial device Bug reassigned from package 'rootskel' to 'src:linux,rootskel'. Ignoring request to alter found

Bug#961122: giac: FTBFS on armhf

Source: giac Version: 1.5.0.87+dfsg1-1 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer d-workaround-armhf-hang.patch was recently dropped [1], however, as can be seen on buildds [2] and reproducibles builds [3], that giac still FTBFS on armhf with: E: Build killed with signal TERM

Bug#926539: rootskel: steal-ctty no longer works on s390x

On 20.05.20 12:42, Valentin Vidić wrote: > On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote: >> Ah, sorry. I was seeing the cached version of the thread, refreshing helped. >> >> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument >> that it would

Bug#926539: rootskel: steal-ctty no longer works on s390x

On 5/20/20 1:18 PM, Philipp Kern wrote: > But then I keep wondering how representative qemu is. Is VT220 SCLP even > something you get on a real z machine? Not that we shouldn't fix qemu, > of course. But Hercules might be closer to the real thing in this regard. Hercules shows the exact same

Bug#960963: status?

What's the status of this problem? Is anybody working on dovecot to have this fixed in Debian stable? *t