Bug#923500: snapd: non-classic snap not confined

Hi, James Henstridge (2021-02-16): > 2. As for why Debian is not being considered for "full" support, > I suspect this is down to the out-of-tree patches to enable access > control for unix domain sockets. This will likely resolve itself > when snapd moves to use the new AppArmor 3.0 network featu

Bug#982890: marked as done (php-redis: Should depend on php-igbinary)

Your message dated Tue, 16 Feb 2021 07:49:52 + with message-id and subject line Bug#982890: fixed in php-redis 5.3.2+4.3.0-2+deb11u1 has caused the Debian Bug report #982890, regarding php-redis: Should depend on php-igbinary to be marked as done. This means that you claim that the problem ha

Bug#982886: marked as done (php-memcached: Should depend on php-igbinary and php-msgpack)

Your message dated Tue, 16 Feb 2021 07:49:41 + with message-id and subject line Bug#982886: fixed in php-memcached 3.1.5+2.2.0-5+deb11u1 has caused the Debian Bug report #982886, regarding php-memcached: Should depend on php-igbinary and php-msgpack to be marked as done. This means that you c

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

Done. Fixed php-redis, php-memcached, php-solr, php-pecl-http, and php-msgpack in one go. Thanks for noticing this and sorry for the trouble, Ondrej -- Ondřej Surý (He/Him) ond...@sury.org > On 15. 2. 2021, at 20:32, Grigory Ivanov wrote: > > Package: php-memcached > Version: 3.1.5+2.2.0-5 > S

Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

severity 982757 critical stop > Version: 20201218-3 > Severity: normal thank you for the report, oh boy this one is opens a can of trouble. It seems I was blissfully unaware that the Debian packaging did not take into account the symlinks of upstream linux-firmware WHENCE file. So this means we a

Processed: Re: Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

Processing commands for cont...@bugs.debian.org: > severity 982757 critical Bug #982757 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1) Severity set to 'critical' from 'normal' > stop Stopping processing here. Please contact me if you

Bug#982766: Chai no more depends on node-uglifyjs-webpack-plugin

Hi, for the record, I removed build dependency to node-uglifyjs-webpack-plugin from chai (src:node-chai). The browser package is no more minified but this is not important: libjs-chai has no reverse dependency. Cheers, Xavier

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

Right, I have a new mechanism for defining the dependencies in dh-php >= 2.0, but I wasn’t able to finish it in time for bullseye, but the memcached has been already updated. I’ll fix this and other affected PECL packages today. Thanks for the report. Ondřej -- Ondřej Surý (He/Him) > On 15.

Bug#982786: marked as done (growlight: autopkgtest regression)

Your message dated Tue, 16 Feb 2021 04:03:45 + with message-id and subject line Bug#982786: fixed in growlight 1.2.30-1 has caused the Debian Bug report #982786, regarding growlight: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#982503: marked as done (neurodebian: Build-Depends on xcftools which should not be released with bullseye)

Your message dated Tue, 16 Feb 2021 03:34:26 + with message-id and subject line Bug#982503: fixed in neurodebian 0.41.0 has caused the Debian Bug report #982503, regarding neurodebian: Build-Depends on xcftools which should not be released with bullseye to be marked as done. This means that

Bug#982786: growlight: autopkgtest regression

alright, with 1.2.30 (1.2.29 was never released), we pass the autopkgtests, huzzah.

Processed: Bug#982503 marked as pending in neurodebian

Processing control commands: > tag -1 pending Bug #982503 [src:neurodebian] neurodebian: Build-Depends on xcftools which should not be released with bullseye Ignoring request to alter tags of bug #982503 to the same tags previously set -- 982503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#982503: marked as pending in neurodebian

Control: tag -1 pending Hello, Bug #982503 in neurodebian 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: https://salsa.debian.org/neurodebian-team/neurodebian/-/commit/6480c19a1e13b72e

Bug#923500: snapd: non-classic snap not confined

I work on some parts of snapd at Canonical, so thought I'd weigh in. I've got a few of points to add: 1. In the "snap debug confinement" output, it says "policy:downgraded". This indicates that snapd didn't detect enough AppArmor features to enforce the full "strict confinement" sandbox, so it sw

Processed: Bug#982503 marked as pending in neurodebian

Processing control commands: > tag -1 pending Bug #982503 [src:neurodebian] neurodebian: Build-Depends on xcftools which should not be released with bullseye Ignoring request to alter tags of bug #982503 to the same tags previously set -- 982503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#982503: marked as pending in neurodebian

Control: tag -1 pending Hello, Bug #982503 in neurodebian 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: https://salsa.debian.org/neurodebian-team/neurodebian/-/commit/d0e0f642ed201067

Bug#982503: marked as pending in neurodebian

Control: tag -1 pending Hello, Bug #982503 in neurodebian 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: https://salsa.debian.org/neurodebian-team/neurodebian/-/commit/34808c4aa5c77d81

Processed: Bug#982503 marked as pending in neurodebian

Processing control commands: > tag -1 pending Bug #982503 [src:neurodebian] neurodebian: Build-Depends on xcftools which should not be released with bullseye Added tag(s) pending. -- 982503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982503 Debian Bug Tracking System Contact ow...@bugs.d

Bug#982786: growlight: autopkgtest regression

not so fast! while this does indeed fix the segfault when run without TERM, i still get an autopkgtest failure, this one tracked down to stdout being redirected =[. so i'm gonna address that as well. how embarrassing.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 982699 https://github.com/intake/intake/issues/550 Bug #982699 [src:intake] intake: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 Set Bug forwarded-to-address to 'https://github

Bug#982786: growlight: autopkgtest regression

Here's the upstream bug: https://github.com/dankamongmen/growlight/issues/139 Here's the (obvious, trivial) fix: https://github.com/dankamongmen/growlight/commit/297f487a8be84441ff75a22b5fa63305931cae70 A real brown-bagger =[. I'm going to cut 1.2.29 and upload it to unstable. If I ought prepare

Bug#982623: marked as done (apktool needs source-only upload for testing migration)

Your message dated Mon, 15 Feb 2021 23:33:25 + with message-id and subject line Bug#982623: fixed in apktool 2.5.0+dfsg.1-2 has caused the Debian Bug report #982623, regarding apktool needs source-only upload for testing migration to be marked as done. This means that you claim that the probl

Bug#982786: growlight: autopkgtest regression

Alright, I've got it locked down to the absence of a TERM environment variable in the autopkgtest environment. If I run the same command outside of autopkgtest, after running `unset TERM`, i get the exact same failure. So, this failure is IMHO definitely worth fixing, and I intend to do so now, bu

Bug#982786: growlight: autopkgtest regression

I can now reproduce this locally, and expect to have a fix this evening. I've looked over the rules for the Soft Freeze, and understand that it'll be acceptable to cut a new upstream release (I'm the upstream author) with this fix only (there have been no other changes since this release), upload t

Bug#980565: marked as done (php-enum: FTBFS with phpunit 9.5)

Your message dated Mon, 15 Feb 2021 22:18:26 + with message-id and subject line Bug#980565: fixed in php-enum 4.4.0-1 has caused the Debian Bug report #980565, regarding php-enum: FTBFS with phpunit 9.5 to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: cloning 982886, reassign 982886 to php-memcached ...

Processing commands for cont...@bugs.debian.org: > clone 982886 -1 Bug #982886 [php-redis] php-redis: Should depend on php-igbinary Bug 982886 cloned as bug 982890 > reassign 982886 php-memcached 3.1.5+2.2.0-5 Bug #982886 [php-redis] php-redis: Should depend on php-igbinary Bug reassigned from pac

Processed: limit source to php-enum, tagging 980565

Processing commands for cont...@bugs.debian.org: > limit source php-enum Limiting to bugs with field 'source' containing at least one of 'php-enum' Limit currently set to 'source':'php-enum' > tags 980565 + pending Bug #980565 [php-enum] php-enum: FTBFS with phpunit 9.5 Added tag(s) pending. > th

Processed (with 1 error): Re: Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

Processing control commands: > clone -1 Unknown command or malformed arguments to command. > reassign -1 php-redis 5.3.2+4.3.0-2 Bug #982886 [php-memcached] php-memcached: Should depend on php-igbinary and php-msgpack Bug reassigned from package 'php-memcached' to 'php-redis'. No longer marked a

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

Control: clone -1 Control: reassign -1 php-redis 5.3.2+4.3.0-2 Control: retitle -1 php-redis: Should depend on php-igbinary Le Mon, Feb 15, 2021 at 10:32:19PM +0300, Grigory Ivanov a écrit : > Package: php-memcached > Version: 3.1.5+2.2.0-5 > Severity: grave > Justification: renders package unusab

Bug#982865: meson: diff for NMU version 0.57.0+really0.56.2-0.1

On Mon, 15 Feb 2021 at 23:21, Sebastian Ramacher wrote: > Silently breaking hardening build flags of roughly 430 packages is > definitely a large and disruptive change. The rc was uploaded to experimental a week ago so that people could use it to flush out problems like these. Apparently no-one

Processed: cdparanoia: diff for NMU version 3.10.2+debian-13.1

Processing control commands: > tags 982321 + pending Bug #982321 [libcdparanoia-dev] libcdparanoia-dev: overly generic header name: /usr/include/utils.h Added tag(s) pending. -- 982321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982321 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#982321: cdparanoia: diff for NMU version 3.10.2+debian-13.1

Control: tags 982321 + pending Dear maintainer, I've prepared an NMU for cdparanoia (versioned as 3.10.2+debian-13.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru cdparanoia-3.10.2+debian/debian/changelog cdparanoi

Bug#982865: marked as done (meson: meson ignores CPPFLAGS)

Your message dated Mon, 15 Feb 2021 21:33:29 + with message-id and subject line Bug#982865: fixed in meson 0.57.0+really0.56.2-0.1 has caused the Debian Bug report #982865, regarding meson: meson ignores CPPFLAGS to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#982868: dpkg-cross generates erronous conflicts on like libc6-amd64:x32-i386-cross

Processing control commands: > tags -1 + patch Bug #982868 [dpkg-cross] dpkg-cross generates erronous conflicts on like libc6-amd64:x32-i386-cross Added tag(s) patch. > severity -1 serious Bug #982868 [dpkg-cross] dpkg-cross generates erronous conflicts on like libc6-amd64:x32-i386-cross Severit

Processed: meson: diff for NMU version 0.57.0+really0.56.2-0.1

Processing control commands: > tags 982865 + patch Bug #982865 [meson] meson: meson ignores CPPFLAGS Added tag(s) patch. -- 982865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#980211: libextractor: FTBFS (flaky tests)

On Wed, 10 Feb 2021 21:02:47 +0100 Bertrand Marc wrote: > Indeed, the original issue reported in this bug was fixed in 1.11-1. > However, the general issue of flaky tests is still there: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libextractor.html > > Would you consider

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

Package: php-memcached Version: 3.1.5+2.2.0-5 Severity: grave Justification: renders package unusable X-Debbugs-Cc: grun...@ololo.cc Dear Maintainer, Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php- igbinary and php-msgpack, but in fact it does, despite ldd could say. Depe

Processed: regina-rexx bug handling for debhelper migration

Processing commands for cont...@bugs.debian.org: > clone 930005 -1 Bug #930005 {Done: Agustin Martin Domingo } [regina-rexx] regina-rexx: rexxutil error Bug 930005 cloned as bug 982884 > retitle -1 regina-rexx: Consider migration to debhelper Bug #982884 {Done: Agustin Martin Domingo } [regina-re

Bug#982122: redis: experimental package OOMs s390x buildds

Hi Chris, On Mon, 2021-02-15 at 18:28 +, Chris Lamb wrote: > Ah, indeed, the failure mode means that the log never made it to > > buildd.d.o. > > Curious, not heard of that failure mode — is there someplace I can > learn about that? No worries if not. I'm not sure if it's documented, but in

Bug#930005: regina-rexx: rexxutil error

Package: regina-rexx Version: 3.6-2.2 Severity: wishlist El lun, 15 feb 2021 a las 13:40, Alen Zekulic () escribió: > > On Mon, Feb 15, 2021 at 13:16:58 +0100, Agustin Martin wrote: > > > I think I have something close to be ready for migration to debhelper. > > Me too. :) > > > ¿What do you prefe

Bug#982882: stellarium FTBFS on armel and mipsel

Source: stellarium Version: 0.20.4-1 Severity: serious Tags: ftbfs Hi Maintainer, Your last upload FTBFS on mipsel and armel. Paul https://buildd.debian.org/status/package.php?p=stellarium make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi' [ 24%] Built target translations-stellarium [ 24%]

Bug#952367: marked as done (uglifyjs: FTBFS: test failed)

Your message dated Mon, 15 Feb 2021 19:48:34 + with message-id and subject line Bug#952367: fixed in uglifyjs 2.8.29-8 has caused the Debian Bug report #952367, regarding uglifyjs: FTBFS: test failed to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#982865: meson: meson ignores CPPFLAGS

On 2021-02-15 20:34:20 +0100, Sebastian Ramacher wrote: > Control: severity -1 serious > > On 2021-02-15 23:43:24 +0800, Yangfl wrote: > > Package: meson > > Version: 0.57.0-1 > > > > When packaging https://salsa.debian.org/yangfl-guest/sequeler , I got > > blhc warning about CPPFLAGS missing (-D

Bug#952367: marked as pending in uglifyjs

Control: tag -1 pending Hello, Bug #952367 in uglifyjs 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: https://salsa.debian.org/js-team/uglifyjs/-/commit/1d34ed600793b1f3c5749cd0b5712c0

Processed: Re: Bug#982865: meson: meson ignores CPPFLAGS

Processing control commands: > severity -1 serious Bug #982865 [meson] meson: meson ignores CPPFLAGS Severity set to 'serious' from 'normal' -- 982865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#952367 marked as pending in uglifyjs

Processing control commands: > tag -1 pending Bug #952367 [src:uglifyjs] uglifyjs: FTBFS: test failed Added tag(s) pending. -- 952367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#980967: closed by Debian FTP Masters (reply to Yaroslav Halchenko ) (Bug#980967: fixed in bats 1.2.1-2)

On Mon, 15 Feb 2021, Paul Gevers wrote: > Hi Yaroslav, > On 15-02-2021 05:51, Debian Bug Tracking System wrote: > > bats (1.2.1-2) unstable; urgency=medium > > . > >* debian/patches > > - adopted patch from https://github.com/bats-core/bats-core/pull/387 to > >resolve "bats-e

Bug#982122: redis: experimental package OOMs s390x buildds

Hi Adam, > Ah, indeed, the failure mode means that the log never made it to > buildd.d.o. Curious, not heard of that failure mode — is there someplace I can learn about that? No worries if not. > I've attached a copy of the log from zani. Ah, thanks. Unfortunately, it does not point us straight

Bug#980967: closed by Debian FTP Masters (reply to Yaroslav Halchenko ) (Bug#980967: fixed in bats 1.2.1-2)

Hi Yaroslav, On 15-02-2021 05:51, Debian Bug Tracking System wrote: > bats (1.2.1-2) unstable; urgency=medium > . >* debian/patches > - adopted patch from https://github.com/bats-core/bats-core/pull/387 to >resolve "bats-exec-test: command not found" (Closes: #980967) This seem

Processed: Re: Bug#982684: subversion: FTBFS on armhf, mips64el: test failure

Processing control commands: > retitle -1 subversion: frequent FTBFS due to flaky test Bug #982684 [src:subversion] subversion: FTBFS on armhf, mips64el: test failure Changed Bug title to 'subversion: frequent FTBFS due to flaky test' from 'subversion: FTBFS on armhf, mips64el: test failure'. --

Bug#982684: subversion: FTBFS on armhf, mips64el: test failure

Control: retitle -1 subversion: frequent FTBFS due to flaky test On Sat, Feb 13, 2021 at 10:29:31AM -0500, James McCoy wrote: > Control: forwarded -1 > https://mail-archives.apache.org/mod_mbox/subversion-dev/202102.mbox/%3C20210212173613.2qji5xpfmcybulyl%40localhost%3E > > On Sat, Feb 13, 2021

Bug#982870: hotspot FTBFS on mips*

Source: hotspot Version: 1.3.0-1 Severity: serious Tags: ftbfs patch fixed-upstream Forwarded: https://github.com/KDAB/perfparser/commit/834db4506d1aeae02d32fe41065d558300491d84 https://buildd.debian.org/status/package.php?p=hotspot ... /<>/3rdparty/perfparser/app/perfregisterinfo.cpp:55:12: err

Bug#982869: datamash FTBFS on !x86 32bit: FAIL: tests/decorate-errors

Source: datamash Version: 1.7-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=datamash ... FAIL: tests/decorate-errors === decorate (GNU datamash) 1.7 Copyright (C) 2020 Assaf Gordon License GPLv3+: GNU GPL version 3 or later

Processed: [PATCH] Re: Bug#982717: udfclient: FTBFS: bmake[1]: no target to make.

Processing control commands: > tag -1 patch confirmed Bug #982717 [src:udfclient] udfclient: FTBFS: bmake[1]: no target to make. Added tag(s) patch and confirmed. -- 982717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982717 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#982717: [PATCH] Re: Bug#982717: udfclient: FTBFS: bmake[1]: no target to make.

Control: tag -1 patch confirmed The current bmake backend for debhelper no longer inherits from the autoconf backend. The attached patch devises an override that restores the old behaviour, and I've verified that it works. Regards, Dennis. udfclient-0.8.11-dhoverride.patch.gz Description: appli

Processed: bug 966935 is forwarded to https://github.com/nichtich/Pandoc-Wrapper/issues/43, tagging 966935

Processing commands for cont...@bugs.debian.org: > forwarded 966935 https://github.com/nichtich/Pandoc-Wrapper/issues/43 Bug #966935 [src:libpandoc-wrapper-perl] libpandoc-wrapper-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 1 Set Bug forwarded-to-address to '

Bug#980809: Matrix package default tolerance on s390x (Re: Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x)

Martin, I have this long-running bug report against Matrix, triggered by glmmTMB on s390x. Graham has been chasing this patiently and we are now at the level of checking on a shell account on the appropriate hardware. We validated that everything does in fact "still break" with CRAN-current p

Bug#982724: marked as done (panicparse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/maruel/panicparse github.com/maruel/panicparse/cmd/panic github.com/maruel/panicpar

Your message dated Mon, 15 Feb 2021 15:48:48 + with message-id and subject line Bug#982724: fixed in golang-1.15 1.15.8-4 has caused the Debian Bug report #982724, regarding panicparse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/maruel/panicparse github.com/m

Bug#982720: marked as done (snapd: FTBFS: dh_auto_test fails)

Your message dated Mon, 15 Feb 2021 15:48:48 + with message-id and subject line Bug#982720: fixed in golang-1.15 1.15.8-4 has caused the Debian Bug report #982720, regarding snapd: FTBFS: dh_auto_test fails to be marked as done. This means that you claim that the problem has been dealt with.

Bug#982714: marked as done (golang-github-jacobsa-ogletest: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcu

Your message dated Mon, 15 Feb 2021 15:48:48 + with message-id and subject line Bug#982714: fixed in golang-1.15 1.15.8-4 has caused the Debian Bug report #982714, regarding golang-github-jacobsa-ogletest: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.

Bug#982701: marked as done (golang-github-pkg-profile: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/profile returned exit code 1)

Your message dated Mon, 15 Feb 2021 15:48:48 + with message-id and subject line Bug#982701: fixed in golang-1.15 1.15.8-4 has caused the Debian Bug report #982701, regarding golang-github-pkg-profile: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/p

Processed: Bug#982734 marked as pending in golang

Processing control commands: > tag -1 pending Bug #982734 [src:golang-1.15] delve: FTBFS: failed test Added tag(s) pending. -- 982734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#982734: marked as pending in golang

Control: tag -1 pending Hello, Bug #982734 in golang 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: https://salsa.debian.org/go-team/compiler/golang/-/commit/25ddd5c4616e7a12316875d339

Processed: Bug#982701 marked as pending in golang

Processing control commands: > tag -1 pending Bug #982701 [src:golang-1.15] golang-github-pkg-profile: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/profile returned exit code 1 Added tag(s) pending. -- 982701: https://bugs.debian.org/cgi-bin/bu

Bug#982701: marked as pending in golang

Control: tag -1 pending Hello, Bug #982701 in golang 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: https://salsa.debian.org/go-team/compiler/golang/-/commit/25ddd5c4616e7a12316875d339

Bug#982864: perceptualdiff FTBFS with test failure on several architectures

Source: perceptualdiff Version: 2.1-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=perceptualdiff

Bug#971129: shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15+1533136590.3beb971-7)

Hi Steve, Thanks for the info. On Mon, Feb 15, 2021 at 12:43:33AM +, Steve McIntyre wrote: > >Could you clarify the timing for this, especially the timeline for getting > >the > >signature from Microsoft (as far as that can be predicted)? I'm trying to > >assess if this could become a blocke

Bug#982862: nagios-plugins-contrib autopkgtest regression on several architectures: check_ssl_cert: unable to write certificate

Source: nagios-plugins-contrib Version: 29.20210204 Severity: serious https://tracker.debian.org/pkg/nagios-plugins-contrib Migration status for nagios-plugins-contrib (28.20201207 to 29.20210204): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: a

Bug#982859: libcmis-dev: allowable-actions.hxx uses non-existing file boost/shared_ptr.hpp

Package: libcmis-dev Version: 0.5.2-2+b2 Severity: serious Configuring upstream's LibreOffice fails with an obscure error: checking whether g++ supports C++17... configure: error: no Error running configure at ./autogen.sh line 316. In the config.log file: configure:18900: checking whether g++

Bug#982857: All pages cut off due to IFRAME closing tag bungle

Package: imagemagick-6-common Version: 8:6.9.11.60+dfsg-1 Severity: grave In $ rgrep 'iframe.*/>' /usr/share/doc/imagemagick-6-common|wc -l 127 pages like file:///usr/share/doc/imagemagick-6-common/html/www/command-line-processing.html please replace https://github.com/sponsors/ImageMagic

Bug#981976: icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent package

... sorry i found im. On 2/15/21 2:22 PM, Andreas Beckmann wrote: > Control: reopen -1 > Control: severity -1 serious > Control: retitle -1 icingaweb2-module-businessprocess: depends on nonexistent > icingaweb2-ipl > > On Mon, 15 Feb 2021 10:58:40 +0100 David Kunz wrote: >> this bug has been fi

Processed: Re: Bug#982613: NetworkManager triggers assert in python-dbusmock test suite

Processing control commands: > reassign -1 network-manager 1.29.90-1 Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock test suite Ignoring request to reassign bug #982613 to the same package Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusm

Bug#982613: NetworkManager triggers assert in python-dbusmock test suite

Control: reassign -1 network-manager 1.29.90-1 Control: tag -1 upstream fixed-upstream Control: forwarded -1 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662 This eventually *did* turn out to be a bug in NetworkManager itself, and only became visible now because of the be

Bug#977542: golang-github-revel-revel: Depends on network in tests

Control: severity -1 important Dear release team, I'm writing as a member of the pkg-go team and am mostly concerned about potential removal of depending packages. The package itself appears to be fine. The tests fail if and only if the test setup doesn't provide (proper) internet connectivity.

Processed: golang-github-revel-revel: Depends on network in tests

Processing control commands: > severity -1 important Bug #977542 [golang-github-revel-revel] golang-github-revel-revel: Depends on network in tests Severity set to 'important' from 'serious' -- 977542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977542 Debian Bug Tracking System Contact o

Processed: gmsh

Processing commands for cont...@bugs.debian.org: > affects 982616 + src:pygmsh Bug #982616 [libvoro++1] libvoro++1: ABI break without soname change Bug #982729 [libvoro++1] octave-msh: FTBFS: msh2m_gmsh: the gmsh subprocess exited abnormally Added indication that 982616 affects src:pygmsh Added i

Processed: Re: Bug#981976: icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent package

Processing control commands: > reopen -1 Bug #981976 {Done: David Kunz } [icingaweb2-module-businessprocess] icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent package 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be c

Processed: Re: Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

Processing control commands: > notfixed -1 1.8.0-1 Bug #981975 {Done: David Kunz } [icingaweb2-module-director] icingaweb2-module-director is uninstallable: dependency on nonexistent package No longer marked as fixed in versions icingaweb2-module-director/1.8.0-1. -- 981975: https://bugs.debian

Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

Control: notfixed -1 1.8.0-1 On Mon, 15 Feb 2021 11:20:18 +0100 David Kunz wrote: > this bug has been fixed in above version, hence closing. icingaweb2-module-incubator 0.6.0-1 is in NEW. notfixed to not confuse the BTS with found and fixed in the same version. Andreas

Bug#930005: regina-rexx: rexxutil error

On Mon, Feb 15, 2021 at 13:16:58 +0100, Agustin Martin wrote: > I think I have something close to be ready for migration to debhelper. Me too. :) > ¿What do you prefer, a commit to salsa or a patch in the BTS? For now I prefer a patch in the BTS. Thanks, -- Alen Zekulic

Processed: tagging 980071

Processing commands for cont...@bugs.debian.org: > tags 980071 + moreinfo Bug #980071 [gnome-shell] gnome-shell: Using suspend in the gnome-shell power off/log out menu does log out and suspend in the wrong order Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you

Bug#930005: regina-rexx: rexxutil error

El lun, 15 feb 2021 a las 0:05, Agustin Martin () escribió: > > El vie, 12 feb 2021 a las 23:05, Alen Zekulic () > escribió: > > > > I agree, please go ahead! > > Uploaded. Hi, Seems this upload has been late for two days, so regina-rexx will not hit bullseye because of soft freeze (see https://

Bug#982700: marked as done (pygmsh: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

Your message dated Mon, 15 Feb 2021 13:08:09 +0100 with message-id and subject line voronoicell has caused the Debian Bug report #982700, regarding pygmsh: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 to be marked as done. This means that you claim t

Processed: Re: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8

Processing control commands: > retitle 969907 epdfinfo crashing with mismatched libpoppler102 and > libpoppler-glib8 Bug #969907 [libpoppler-glib8] libpoppler-glib8: introduces new ABI without bumping shlibs version Changed Bug title to 'epdfinfo crashing with mismatched libpoppler102 and libpo

Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8

Control: retitle 969907 epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8 Control: tags 969907 + patch Sorry, this reply should have gone to the clone in libpoppler-glib8, not to the archived original bug in epdfinfo (which I don't think was ever really an epdfinfo bug). On Mo

Processed: reassign 982613 to network-manager, found 982613 in 1.29.90-1, affects 982613

Processing commands for cont...@bugs.debian.org: > reassign 982613 network-manager Bug #982613 [python3-dbusmock] NetworkManager triggers assert in python-dbusmock test suite Bug reassigned from package 'python3-dbusmock' to 'network-manager'. No longer marked as found in versions python-dbusmock

Processed: tagging 982838

Processing commands for cont...@bugs.debian.org: > # this bug is just an archive workaround - not relevant for the release > tags 982838 + bullseye-ignore Bug #982838 [src:win32-loader] RoM: win32-loader must not migrate automatically Added tag(s) bullseye-ignore. > thanks Stopping processing here

Bug#982850: duperemove: first run fails errror 13?

Package: duperemove Version: 0.11.2-3 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: de...@roosoft.ltd.uk Dear Maintainer, So running duperemove for the first run. duperemove -r -A -h --skip-zeroes --hashfile=/var/cache/duperemove-home-user /home/user/ At t

Bug#981100: marked as done (FTBFS with bind9 >= 9.16.10)

Your message dated Mon, 15 Feb 2021 11:03:25 + with message-id and subject line Bug#981100: fixed in bind-dyndb-ldap 11.6-2 has caused the Debian Bug report #981100, regarding FTBFS with bind9 >= 9.16.10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#982705: marked as done (openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’)

Your message dated Mon, 15 Feb 2021 10:48:48 + with message-id and subject line Bug#982705: fixed in openssh 1:8.4p1-4 has caused the Debian Bug report #982705, regarding openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’ to be marked as done. This means that you claim t

Bug#980677: marked as done (espresso: FTBFS: Error: #error No fft_scalar backend selected!)

Your message dated Mon, 15 Feb 2021 10:48:30 + with message-id and subject line Bug#980677: fixed in espresso 6.7-2 has caused the Debian Bug report #980677, regarding espresso: FTBFS: Error: #error No fft_scalar backend selected! to be marked as done. This means that you claim that the probl

Bug#980042: Upstream has fixed the problem

http://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=07ee21c2db558106c8537600698db75e51ac1090

Bug#982705: openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’

On Mon, Feb 15, 2021 at 11:31:45AM +0100, Andreas Henriksson wrote: > On Mon, Feb 15, 2021 at 09:41:30AM +, Colin Watson wrote: > > FWIW, I think your patch in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982705#25 is correct > > (even if I prefer to take a different approach as a work

Bug#953093: reopen

close 953093 20190125-2 thanks Hi, this bug has been fixed in above version, hence closing. Regards, David

Processed: Re: Bug#953093: reopen

Processing commands for cont...@bugs.debian.org: > close 953093 20190125-2 Bug #953093 [icingaweb2-module-x509] icingaweb2-module-x509 is uninstallable, dependency on nonexistent package Marked as fixed in versions icingaweb2-module-x509/20190125-2. Bug #953093 [icingaweb2-module-x509] icingaweb2

Bug#982705: openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’

On Mon, Feb 15, 2021 at 09:41:30AM +, Colin Watson wrote: [...] > FWIW, I think your patch in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982705#25 is correct > (even if I prefer to take a different approach as a workaround for the > packaging) and could be forwarded upstream. Would yo

Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

close 981975 1.8.0-1 thanks Hi, this bug has been fixed in above version, hence closing. Regards,

Processed: Re: Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

Processing commands for cont...@bugs.debian.org: > close 981975 1.8.0-1 Bug #981975 [icingaweb2-module-director] icingaweb2-module-director is uninstallable: dependency on nonexistent package Marked as fixed in versions icingaweb2-module-director/1.8.0-1. Bug #981975 [icingaweb2-module-director]

Bug#977990: os-autoinst: FTBFS on i386: 3/3 Test #3: test-perl-testsuite ..............***Failed 332.81 sec

Hi, indeed Paul, the test is flaky, probably a timing issue. I had already changed some related parameter that made the tests pass reliably on my i386 builder, but saw afterward that it still failed on debian's builder and couldn't reproduce it : https://salsa.debian.org/debian/os-autoinst/-/commit

Bug#982705: marked as pending in openssh

Control: tag -1 pending Hello, Bug #982705 in openssh 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: https://salsa.debian.org/ssh-team/openssh/-/commit/d0cee71ebcde7400f7caa1fcbf0f9973

  1   2   >