Bug#1004111: unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures

Control: severity -1 normal Control: tags -1 + moreinfo Control: retitle -1 unattended-upgrades: upgrade of chromium-browser and others skipped on Raspberry Pi OS On Thu, 20 Jan 2022 16:42:21 -0600 Judah Richardson wrote: > This bug has showing up on this end in unattended-upgrades 2.8 on my > R

Processed: Re: unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures

Processing control commands: > severity -1 normal Bug #1004111 [unattended-upgrades] unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures Severity set to 'normal' from 'serious' > tags -1 + moreinfo Bug #1004111 [unattended-upgrades] u

Bug#1002872: Can this be unblocked now?

Looks like it should be just a build time config switch fix. Shmerl.

Bug#1003017: marked as done (dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found)

Your message dated Sun, 30 Jan 2022 00:18:44 + with message-id and subject line Bug#1003017: fixed in dulwich 0.20.31-1.1 has caused the Debian Bug report #1003017, regarding dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found to be marked as done. This means that

Bug#1003017: dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found

Hi Jelmer, On Sun, 2 Jan 2022 21:08:25 +0100 Paul Gevers wrote: > With a recent upload of dulwich the autopkgtest of dulwich fails in > testing when that autopkgtest is run with the binary packages of dulwich > from unstable. It passes when run with only packages from testing. In > tabular for

Processed: closing 997273

Processing commands for cont...@bugs.debian.org: > close 997273 Bug #997273 [libguestfs] virt-v2v: FTBFS: (.text+0x12a): undefined reference to `rpl_free' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 997273: https://bugs.debian.org/cgi-bin/b

Bug#1004505: marked as pending in nanoc

Control: tag -1 pending Hello, Bug #1004505 in nanoc 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/ruby-team/nanoc/-/commit/8ccd449a3e8f3c650bb9c11c924d397a46

Processed: Bug#1004505 marked as pending in nanoc

Processing control commands: > tag -1 pending Bug #1004505 [src:nanoc] nanoc_4.12.5-2_all-buildd.changes REJECTED Added tag(s) pending. -- 1004505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#998183: marked as done (mklibs: FTBFS with newer compilers)

Your message dated Sat, 29 Jan 2022 21:49:17 + with message-id and subject line Bug#998183: fixed in mklibs 0.1.45 has caused the Debian Bug report #998183, regarding mklibs: FTBFS with newer compilers to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#937054: marked as done (mklibs: Python2 removal in sid/bullseye)

Your message dated Sat, 29 Jan 2022 21:49:17 + with message-id and subject line Bug#937054: fixed in mklibs 0.1.45 has caused the Debian Bug report #937054, regarding mklibs: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Processed: [pyvo] CI failure with astropy 5.0.1; please update to version 1.2.1

Processing control commands: > affects -1 astropy Bug #1004517 [src:pyvo] [pyvo] CI failure with astropy 5.0.1; please update to version 1.2.1 Added indication that 1004517 affects astropy -- 1004517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004517 Debian Bug Tracking System Contact o

Bug#1004517: [pyvo] CI failure with astropy 5.0.1; please update to version 1.2.1

Source: pyvo Version: 1.1-1 Severity: serious Control: affects -1 astropy Dear maintainer, I just uploaded astropy-5.0.1 to unstable. It appears that pyvo 1.1 is no longer compatible and now leads to a CI test error: https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyvo/18800419/log.gz

Processed: cwltool breaks toil autopkgtest: No such file or directory: '/home/debci/tmp/tmpgxz5j85g'

Processing control commands: > found -1 cwltool/3.1.20220119140128-2 Bug #1004516 [src:cwltool, src:toil] cwltool breaks toil autopkgtest: No such file or directory: '/home/debci/tmp/tmpgxz5j85g' Marked as found in versions cwltool/3.1.20220119140128-2. > found -1 toil/5.6.0-2 Bug #1004516 [src:c

Bug#1004516: cwltool breaks toil autopkgtest: No such file or directory: '/home/debci/tmp/tmpgxz5j85g'

Source: cwltool, toil Control: found -1 cwltool/3.1.20220119140128-2 Control: found -1 toil/5.6.0-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of cwltool the

Bug#1004512: autodock-vina: autopkgtest regression on armhf: warning on stderr

Source: autodock-vina Version: 1.2.3-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of autodock-vina the autopkgtest of autodock-vina fails in testing when that autopkgtest is run with t

Bug#1004511: luajit breaks knot-resolver autopkgtest on ppc64el: Segmentation fault

Source: luajit, knot-resolver Control: found -1 luajit/2.1.0~beta3+git20210112+dfsg-2 Control: found -1 knot-resolver/5.4.4-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a re

Processed: luajit breaks knot-resolver autopkgtest on ppc64el: Segmentation fault

Processing control commands: > found -1 luajit/2.1.0~beta3+git20210112+dfsg-2 Bug #1004511 [src:luajit, src:knot-resolver] luajit breaks knot-resolver autopkgtest on ppc64el: Segmentation fault Marked as found in versions luajit/2.1.0~beta3+git20210112+dfsg-2. > found -1 knot-resolver/5.4.4-1 Bug

Processed: asterisk-opus: Depends on asterisk-1fb7f5c06d7a2052e38d021b3d8ca151 which is gone

Processing control commands: > affects -1 src:asterisk Bug #1004510 [src:asterisk-opus] asterisk-opus: Depends on asterisk-1fb7f5c06d7a2052e38d021b3d8ca151 which is gone Added indication that 1004510 affects src:asterisk -- 1004510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004510 Debi

Bug#1004510: asterisk-opus: Depends on asterisk-1fb7f5c06d7a2052e38d021b3d8ca151 which is gone

Source: asterisk-opus Version: 13.7+20171009-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, aster...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:asterisk Dear maintainer(s), With a recent upload of asterisk

Bug#1004509: pyfai: autopkgtest regression on armhf: images have different dimensions

Source: pyfai Version: 0.21.0+dfsg1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of pyfai the autopkgtest of pyfai fails in testing when that autopkgtest is run with the binary package

Bug#1004508: ocrad: autopkgtest regression: undefined reference to `png_g*

Source: ocrad Version: 0.28-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ocrad the autopkgtest of ocrad fails in testing when that autopkgtest is run with the binary packages of ocr

Bug#1004506: muscle breaks theseus autopkgtest: Unknown option maxiters

Source: muscle, theseus Control: found -1 muscle/1:5.1-1 Control: found -1 theseus/3.3.0-10 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of muscle the autopkgt

Processed: muscle breaks theseus autopkgtest: Unknown option maxiters

Processing control commands: > found -1 muscle/1:5.1-1 Bug #1004506 [src:muscle, src:theseus] muscle breaks theseus autopkgtest: Unknown option maxiters Marked as found in versions muscle/1:5.1-1. > found -1 theseus/3.3.0-10 Bug #1004506 [src:muscle, src:theseus] muscle breaks theseus autopkgtest

Bug#1004505: nanoc_4.12.5-2_all-buildd.changes REJECTED

Source: nanoc Version: 4.12.5-2 Severity: serious On 2022-01-29 16:19, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package ruby-nanoc-deploying, version > 1.0.1-2, for all, > however testing already has version 1.0.1-2. > Uploads to unstable must have

Bug#971223: marked as done (rust-redox-termios: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Sat, 29 Jan 2022 18:05:44 + with message-id and subject line Bug#971223: fixed in rust-redox-termios 0.1.2-1 has caused the Debian Bug report #971223, regarding rust-redox-termios: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be mar

Processed: bug #1002130: forwarded upstream

Processing commands for cont...@bugs.debian.org: > forwarded 1002130 https://github.com/enthought/apptools/issues/303 Bug #1002130 [src:python-apptools] python-apptools: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13 Set Bug forwarde

Bug#1004460: marked as done (ruby-html-proofer accesses the internet during the build)

Your message dated Sat, 29 Jan 2022 17:22:09 + with message-id and subject line Bug#1004460: fixed in ruby-html-proofer 3.19.2-4 has caused the Debian Bug report #1004460, regarding ruby-html-proofer accesses the internet during the build to be marked as done. This means that you claim that t

Processed: tagging 1004299

Processing commands for cont...@bugs.debian.org: > tags 1004299 + ftbfs Bug #1004299 [ruby-net-ssh] ruby-net-ssh: FTBFS in sid Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004299 De

Processed: severity of 1004299 is serious

Processing commands for cont...@bugs.debian.org: > severity 1004299 serious Bug #1004299 [ruby-net-ssh] ruby-net-ssh: FTBFS in sid Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1004299: https://bugs.debian.org/cgi-bin/bugr

Processed: Bug#1004460 marked as pending in ruby-html-proofer

Processing control commands: > tag -1 pending Bug #1004460 [src:ruby-html-proofer] ruby-html-proofer accesses the internet during the build Added tag(s) pending. -- 1004460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004460 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#1004460: marked as pending in ruby-html-proofer

Control: tag -1 pending Hello, Bug #1004460 in ruby-html-proofer 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/ruby-team/ruby-html-proofer/-/commit/30e52077df

Bug#1002115: marked as done (ruby-kramdown: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: invalid byte sequence in UTF-8)

Your message dated Sat, 29 Jan 2022 16:51:24 + with message-id and subject line Bug#1002115: fixed in ruby-kramdown 2.3.1-4 has caused the Debian Bug report #1002115, regarding ruby-kramdown: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: invalid byte sequence in UTF-8 to be marked as do

Processed: Bug#1002115 marked as pending in ruby-kramdown

Processing control commands: > tag -1 pending Bug #1002115 [src:ruby-kramdown] ruby-kramdown: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: invalid byte sequence in UTF-8 Added tag(s) pending. -- 1002115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002115 Debian Bug Tracking System

Bug#1002115: marked as pending in ruby-kramdown

Control: tag -1 pending Hello, Bug #1002115 in ruby-kramdown 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/ruby-team/ruby-kramdown/-/commit/c87ae632a49518700e

Processed: limit source to linux, tagging 1004495

Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1004495 + pending Bug #1004495 [linux] 5.16.3-1~exp1 FTBFS on i386 Added tag(s) pending. > thanks Stopping p

Bug#1002113: gr-gsm: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

[Lucas Nussbaum] > Relevant part (hopefully): > > /usr/bin/ld: CMakeFiles/cmTC_af046.dir/src.c.o: in function `main': > > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to > > `pthread_create' > > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: undefined

Processed: Re: Bug#1002192: kitinerary: FTBFS: 12: QWARN : ExtractorScriptEngineTest::testInfiniteLoop() org.kde.kitinerary: JS ERROR: [qrc://buggy.js]:0: Error: Interrupted

Processing commands for cont...@bugs.debian.org: > tags 1002192 patch Bug #1002192 [src:kitinerary] kitinerary: FTBFS: 12: QWARN : ExtractorScriptEngineTest::testInfiniteLoop() org.kde.kitinerary: JS ERROR: [qrc://buggy.js]:0: Error: Interrupted Added tag(s) patch. > thanks Stopping processing

Bug#1002192: kitinerary: FTBFS: 12: QWARN : ExtractorScriptEngineTest::testInfiniteLoop() org.kde.kitinerary: JS ERROR: [qrc://buggy.js]:0: Error: Interrupted

tags 1002192 patch thanks On Tue, Dec 21, 2021 at 05:02:35PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] > > test 29 > > Start 29: calendarhandlertest > > > > 29: Test command: > > /<>/obj-x86_64-linux-gnu/bin/cal

Bug#1004454: marked as done (kiwi-systemdeps-bootloaders is not installable on several architectures)

Your message dated Sat, 29 Jan 2022 12:19:38 + with message-id and subject line Bug#1004454: fixed in kiwi 9.24.19-1 has caused the Debian Bug report #1004454, regarding kiwi-systemdeps-bootloaders is not installable on several architectures to be marked as done. This means that you claim th

Processed: severity of 1002380 is normal

Processing commands for cont...@bugs.debian.org: > severity 1002380 normal Bug #1002380 [src:python-matrix-nio] python-matrix-nio: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me

Processed: Re: Bug#1004495: 5.16.3-1~exp1 FTBFS on i386

Processing control commands: > tags -1 + confirmed Bug #1004495 [linux] 5.16.3-1~exp1 FTBFS on i386 Added tag(s) confirmed. > forwarded -1 > https://lore.kernel.org/lkml/20220114075756.838243-1-sly...@gmail.com/ Bug #1004495 [linux] 5.16.3-1~exp1 FTBFS on i386 Set Bug forwarded-to-address to 'ht

Bug#1004495: 5.16.3-1~exp1 FTBFS on i386

Control: tags -1 + confirmed Control: forwarded -1 https://lore.kernel.org/lkml/20220114075756.838243-1-sly...@gmail.com/ Hi Daniel, On Sat, Jan 29, 2022 at 10:23:21AM +0100, Daniel Baumann wrote: > Package: linux > Version: 5.16.3-1~exp1 > Severity: serious > Tag: experimental > > Hi, > > unf

Bug#1004495: 5.16.3-1~exp1 FTBFS on i386

Package: linux Version: 5.16.3-1~exp1 Severity: serious Tag: experimental Hi, unfortunately the last upload to experimental failed to build on i386. Regards, Daniel

Bug#1004101: marked as done (ignition-fuel-tools: autopkgtest needs update for new version of ignition-common: Package 'ignition-common3' not found)

Your message dated Sat, 29 Jan 2022 08:36:40 + with message-id and subject line Bug#1004101: fixed in ignition-common 4.4.0+ds-5 has caused the Debian Bug report #1004101, regarding ignition-fuel-tools: autopkgtest needs update for new version of ignition-common: Package 'ignition-common3' no

Processed: reassign 1004101 to libignition-common-core-dev

Processing commands for cont...@bugs.debian.org: > reassign 1004101 libignition-common-core-dev 4.4.0+ds-1 Bug #1004101 [src:ignition-fuel-tools] ignition-fuel-tools: autopkgtest needs update for new version of ignition-common: Package 'ignition-common3' not found Bug reassigned from package 'src