Processed: 1009415 is forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 1009415 https://github.com/project-gemmi/gemmi/issues/212 Bug #1009415 [src:gemmi] gemmi: FTBFS with tao-pegtl v3 Set Bug forwarded-to-address to 'https://github.com/project-gemmi/gemmi/issues/212'. > thanks Stopping processing here. P

Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch

On 19/05/2022 06.34, Andreas Beckmann wrote: Yes, it's an arch detection problem and an attempt is made to build for armv8l instead of arm. But we fixed that long ago for i386 on amd64 kernel, so it should be manageable for armhf, too. Hi, could you try again and see whether the attached patc

Processed: forcibly merging 699328 691088

Processing commands for cont...@bugs.debian.org: > forcemerge 699328 691088 Bug #699328 {Done: Reinhard Tartler } [libavutil51] libavutil51: relocation error after upgrade Warning: Unknown package 'libavutil51' Bug #691088 {Done: Reinhard Tartler } [libavutil51] libavcodec-extra-53: symbol ff_sq

Processed: unarchiving 691088

Processing commands for cont...@bugs.debian.org: > unarchive 691088 Bug #691088 {Done: Reinhard Tartler } [libavutil51] libavcodec-extra-53: symbol ff_sqrt_tab, version LIBAVUTIL_51 not defined in file libavutil.so.51 with link time reference Warning: Unknown package 'libavutil51' Unarchived Bug

Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch

Thanks for the test run and the log! On 29/04/2022 08.25, Paul Gevers wrote: > Do you think it matters that armhf is tested in lxc (like all ci.d.n > workers) on an arm64 host with an arm64 kernel? Yes, it's an arch detection problem and an attempt is made to build for armv8l instead of arm. Bu

Bug#1011032: marked as done (libghc-hsopenssl-dev needs update for OpenSSL 3.0)

Your message dated Thu, 19 May 2022 04:19:25 + with message-id and subject line Bug#996424: fixed in haskell-hsopenssl 0.11.7.2-1 has caused the Debian Bug report #996424, regarding libghc-hsopenssl-dev needs update for OpenSSL 3.0 to be marked as done. This means that you claim that the prob

Bug#996424: marked as done (libghc-hsopenssl-dev needs update for OpenSSL 3.0)

Your message dated Thu, 19 May 2022 04:19:25 + with message-id and subject line Bug#996424: fixed in haskell-hsopenssl 0.11.7.2-1 has caused the Debian Bug report #996424, regarding libghc-hsopenssl-dev needs update for OpenSSL 3.0 to be marked as done. This means that you claim that the prob

Bug#996424: marked as done (libghc-hsopenssl-dev needs update for OpenSSL 3.0)

Your message dated Thu, 19 May 2022 04:19:26 + with message-id and subject line Bug#1011032: fixed in haskell-hsopenssl 0.11.7.2-1 has caused the Debian Bug report #1011032, regarding libghc-hsopenssl-dev needs update for OpenSSL 3.0 to be marked as done. This means that you claim that the pr

Bug#1011032: marked as done (libghc-hsopenssl-dev needs update for OpenSSL 3.0)

Your message dated Thu, 19 May 2022 04:19:26 + with message-id and subject line Bug#1011032: fixed in haskell-hsopenssl 0.11.7.2-1 has caused the Debian Bug report #1011032, regarding libghc-hsopenssl-dev needs update for OpenSSL 3.0 to be marked as done. This means that you claim that the pr

Bug#1010999: marked as done (cl-plus-ssl needs an upload for the ongoing OpenSSL 3.0 transition)

Your message dated Thu, 19 May 2022 00:03:38 + with message-id and subject line Bug#1010999: fixed in cl-plus-ssl 20220328.git8b91648-4 has caused the Debian Bug report #1010999, regarding cl-plus-ssl needs an upload for the ongoing OpenSSL 3.0 transition to be marked as done. This means that

Processed: closing 1011177

Processing commands for cont...@bugs.debian.org: > close 1011177 9.7.0-3 Bug #1011177 [src:opennds] opennds: binary-any FTBFS The source 'opennds' and version '9.7.0-3' do not appear to match any binary packages Marked as fixed in versions opennds/9.7.0-3. Bug #1011177 [src:opennds] opennds: bina

Bug#1010941: marked as done (FTBFS due to tests 56 tests failing)

Your message dated Wed, 18 May 2022 19:34:03 + with message-id and subject line Bug#1010941: fixed in python-argcomplete 1.12.3-0.2 has caused the Debian Bug report #1010941, regarding FTBFS due to tests 56 tests failing to be marked as done. This means that you claim that the problem has bee

Bug#1008435: marked as done (looking-glass: FTBFS: -- No package 'xpresent' found)

Your message dated Wed, 18 May 2022 21:35:59 +0200 with message-id <2041aac2-d674-9007-7a13-707e99bff...@debian.org> and subject line Re: looking-glass: FTBFS: -- No package 'xpresent' found has caused the Debian Bug report #1008435, regarding looking-glass: FTBFS: -- No package 'xpresent' found

Processed: src:looking-glass: fails to migrate to testing for too long: maintainer built amd64 binaries

Processing control commands: > close -1 0+b5.0.1-2 Bug #1011248 [src:looking-glass] src:looking-glass: fails to migrate to testing for too long: maintainer built amd64 binaries Marked as fixed in versions looking-glass/0+b5.0.1-2. Bug #1011248 [src:looking-glass] src:looking-glass: fails to migra

Bug#1011248: src:looking-glass: fails to migrate to testing for too long: maintainer built amd64 binaries

Source: looking-glass Version: 0+b4+dfsg.1-1 Severity: serious Control: close -1 0+b5.0.1-2 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for

Bug#1011242: marked as done (thrift: No depends on libssl after rebuild against OpenSSL 3.0)

Your message dated Wed, 18 May 2022 20:56:23 +0200 with message-id and subject line Re: Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0 has caused the Debian Bug report #1011242, regarding thrift: No depends on libssl after rebuild against OpenSSL 3.0 to be marked as d

Processed: merging 1011114 1011243

Processing commands for cont...@bugs.debian.org: > merge 104 1011243 Bug #104 [src:nvidia-cuda-toolkit] nivdia-cuda-toolkit: hardcodes dependencies on libssl1.1 Bug #1011243 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: Hard dependency on libssl1.1 Merged 104 1011243 > thanks Stoppi

Processed: Bug#1008327 marked as pending in setbfree

Processing control commands: > tag -1 pending Bug #1008327 [src:setbfree] setbfree: FTBFS: ld: /tmp/ccVQW4B0.o: undefined reference to symbol 'glMaterialfv' Added tag(s) pending. -- 1008327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008327 Debian Bug Tracking System Contact ow...@bugs.

Bug#1008327: marked as pending in setbfree

Control: tag -1 pending Hello, Bug #1008327 in setbfree 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/multimedia-team/setbfree/-/commit/c9f63bd6a7c466487a6ca0

Processed: Bug#984040 marked as pending in drumgizmo

Processing control commands: > tag -1 pending Bug #984040 [src:drumgizmo] drumgizmo: ftbfs with GCC-11 Added tag(s) pending. -- 984040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984040: marked as pending in drumgizmo

Control: tag -1 pending Hello, Bug #984040 in drumgizmo 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/multimedia-team/drumgizmo/-/commit/d32f86c2b4d2620c3ee40

Processed: Re: Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0

Processing control commands: > tags -1 +unreproducible Bug #1011242 [src:thrift] thrift: No depends on libssl after rebuild against OpenSSL 3.0 Added tag(s) unreproducible. -- 1011242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011242 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0

Control: tags -1 +unreproducible On Wed, May 18, 2022 at 7:39 PM Kurt Roeckx wrote: > It seems that thrift does not depend on libssl after being rebuild > against OpenSSL 3.0, but did depend on libssl1.1. Are you sure? Which architecture did you check? I just checked amd64 [1], mipsel [2] and ar

Processed (with 1 error): merging 1011114 1011242

Processing commands for cont...@bugs.debian.org: > merge 104 1011242 Bug #104 [src:nvidia-cuda-toolkit] nivdia-cuda-toolkit: hardcodes dependencies on libssl1.1 Unable to merge bugs because: package of #1011242 is 'src:thrift' not 'src:nvidia-cuda-toolkit' Failed to merge 104: Did not

Bug#1011243: nvidia-cuda-toolkit: Hard dependency on libssl1.1

Source: nvidia-cuda-toolkit Version: 11.4.3-2 Severity: serious Tags: sid bookworm Hi, It seems build-depends on libssl1.1 and not on libssl-dev. It also depends on libssl1.1 and doesn't transition to libssl3 on rebuild. Can you please move to using libssl3? Kurt

Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0

Source: thrift Version: 0.16.0-5 Severity: serious Tags: sid bookworm Hi, It seems that thrift does not depend on libssl after being rebuild against OpenSSL 3.0, but did depend on libssl1.1. Kurt

Bug#1010166: marked as done (webkit2gtk: 2.36.1-1 apparent regression seen in devhelp autopkgtest)

Your message dated Wed, 18 May 2022 13:06:16 -0400 with message-id and subject line Re: Bug#1010166: webkit2gtk: 2.36.1-1 apparent regression seen in devhelp autopkgtest has caused the Debian Bug report #1010166, regarding webkit2gtk: 2.36.1-1 apparent regression seen in devhelp autopkgtest to b

Bug#1006559: marked as done (FTBFS with New Twisted)

Your message dated Wed, 18 May 2022 16:49:29 + with message-id and subject line Bug#1006559: fixed in python-scrapy 2.6.1-1 has caused the Debian Bug report #1006559, regarding FTBFS with New Twisted to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1006008: marked as done (python-cryptography: FTBFS with OpenSSL 3.0)

Your message dated Wed, 18 May 2022 16:49:21 + with message-id and subject line Bug#1006008: fixed in python-cryptography 3.4.8-2 has caused the Debian Bug report #1006008, regarding python-cryptography: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem h

Bug#1011187: redis: FTBFS: killed due to inactivity

Sebastian Ramacher wrote: > E: Build killed with signal TERM after 150 minutes of inactivity > [..] Hm, I requested a giveback using the automated service and it seems to build properly... this time. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris

Bug#1006560: marked as done (python-asyncssh: FTBFS with OpenSSL 3.0)

Your message dated Wed, 18 May 2022 16:19:09 + with message-id and subject line Bug#1006560: fixed in python-asyncssh 2.10.1-1 has caused the Debian Bug report #1006560, regarding python-asyncssh: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been

Bug#1006560: marked as pending in python-asyncssh

Control: tag -1 pending Hello, Bug #1006560 in python-asyncssh 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/python-team/packages/python-asyncssh/-/commit/08f

Processed: Bug#1006560 marked as pending in python-asyncssh

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

Bug#1006508: marked as pending in m2crypto

Control: tag -1 pending Hello, Bug #1006508 in m2crypto 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/python-team/packages/m2crypto/-/commit/6c4ac9d168022e8da

Processed: Bug#1006508 marked as pending in m2crypto

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

Processed: Bug#1006508 marked as pending in m2crypto

Processing control commands: > tag -1 pending Bug #1006508 [src:m2crypto] m2crypto: FTBFS with OpenSSL 3.0 Ignoring request to alter tags of bug #1006508 to the same tags previously set -- 1006508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006508 Debian Bug Tracking System Contact ow...

Bug#1006508: marked as pending in m2crypto

Control: tag -1 pending Hello, Bug #1006508 in m2crypto 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/python-team/packages/m2crypto/-/commit/626249735869cda5e

Bug#1006585: tpm2-tss-engine: FTBFS with OpenSSL 3.0

On 2022-02-27 23:37:35 [+], Luca Boccassi wrote: > This is known and expected, this package is an engine for OpenSSL 1.x. > The 3.x version is shipped as a separate and different project, already > uploaded to experimental: > > https://tracker.debian.org/pkg/tpm2-openssl > > Once OpenSSL 3.x

Bug#959600: marked as pending in jruby

Control: tag -1 pending Hello, Bug #959600 in jruby 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/java-team/jruby/-/commit/11fb2f597c50dbad481731942b32e91

Processed: Bug#959600 marked as pending in jruby

Processing control commands: > tag -1 pending Bug #959600 [src:jruby] jruby: FTBFS: [exec] Failure/Error: return gem_original_require(path) Added tag(s) pending. -- 959600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959600 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1006008: marked as pending in python-cryptography

Control: tag -1 pending Hello, Bug #1006008 in python-cryptography 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/python-team/packages/python-cryptography/-/co

Processed: Bug#1006008 marked as pending in python-cryptography

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

Bug#1006559: marked as pending in python-scrapy

Control: tag -1 pending Hello, Bug #1006559 in python-scrapy 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/python-team/packages/python-scrapy/-/commit/344cb04

Processed: Bug#1006559 marked as pending in python-scrapy

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

Processed: bug 1006508 is forwarded to https://gitlab.com/m2crypto/m2crypto/-/issues/310

Processing commands for cont...@bugs.debian.org: > forwarded 1006508 https://gitlab.com/m2crypto/m2crypto/-/issues/310 Bug #1006508 [src:m2crypto] m2crypto: FTBFS with OpenSSL 3.0 Set Bug forwarded-to-address to 'https://gitlab.com/m2crypto/m2crypto/-/issues/310'. > thanks Stopping processing her

Processed (with 5 errors): severity #992164 important

Processing commands for cont...@bugs.debian.org: > severity #992164 important Bug #992164 [calamares] calamares: Creating a new blank partition table GPT/UEFI results in failure Severity set to 'important' from 'critical' > thanks you Unknown command or malformed arguments to command. > Changing

Bug#1008539: marked as done (gnome-shell-extension-dashtodock: does not declare compatibility with GNOME Shell 42)

Your message dated Wed, 18 May 2022 11:03:43 + with message-id and subject line Bug#1008539: fixed in gnome-shell-extension-dashtodock 72-1 has caused the Debian Bug report #1008539, regarding gnome-shell-extension-dashtodock: does not declare compatibility with GNOME Shell 42 to be marked as

Bug#1011182: marked as done (xygrib build-depends on obsolete package)

Your message dated Wed, 18 May 2022 08:34:06 + with message-id and subject line Bug#1011182: fixed in xygrib 1.2.6.1-2 has caused the Debian Bug report #1011182, regarding xygrib build-depends on obsolete package to be marked as done. This means that you claim that the problem has been dealt

Bug#1010623: which dracut version

On 5/18/22 8:43 AM, Thomas Lange wrote: Which dracut version are you using? 051-1 according to aptitude. [ I realised after I'd posted this report that the issue was probably with dracut rather than the kernel. Apologies for any annoyance caused. ] -- Dick Middleton d...@lingbrae.com

Bug#1011176: marked as done (apertium-recursive: fails to detect EOF condition on unsigned char archs)

Your message dated Wed, 18 May 2022 08:22:13 + with message-id and subject line Bug#1011176: fixed in apertium-recursive 1.1.1-1 has caused the Debian Bug report #1011176, regarding apertium-recursive: fails to detect EOF condition on unsigned char archs to be marked as done. This means that

Processed: Re: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0

Processing control commands: > notfound 1011166 pidgin/2.14.9-2 Bug #1011166 [src:pidgin, src:chatty] pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0 No longer marked as found in versions pidgin/2.14.9-2. > tags 1011166 patch Bug #1011166 [src:pidgin, src:ch

Bug#1011166: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0

Control: notfound 1011166 pidgin/2.14.9-2 Control: tags 1011166 patch On 5/17/22 15:34, Paul Gevers wrote: I note that the library moved location from /usr/lib/purple-2/libjabber.so.0.0.0 to /usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0.0.0. I converted from an ancient compat version to m

Bug#1010747: marked as done (Unusable with current python version)

Your message dated Wed, 18 May 2022 07:49:24 + with message-id and subject line Bug#1010747: fixed in pymecavideo 7.2.1-3 has caused the Debian Bug report #1010747, regarding Unusable with current python version to be marked as done. This means that you claim that the problem has been dealt w

Bug#1010747: marked as done (Unusable with current python version)

Your message dated Wed, 18 May 2022 07:49:18 + with message-id and subject line Bug#1010747: fixed in pyacidobasic 2.11.1-2 has caused the Debian Bug report #1010747, regarding Unusable with current python version to be marked as done. This means that you claim that the problem has been dealt

Bug#1010623: which dracut version

Which dracut version are you using? -- viele Grüße Thomas

Processed: reopen 1010747

Processing commands for cont...@bugs.debian.org: > reopen 1010747 Bug #1010747 [shiboken2] Unusable with current python version Bug 1010747 is not marked as done; doing nothing. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010747: https://bugs.debian.org/cgi-b

Bug#1011041:

It should be fixed in upstream 3.2.0, which is the release just after 3.0.25. -- Informativa sulla Privacy: https://www.unibs.it/it/node/1452

Bug#1010962: marked as done (libstrophe FTBFS with OpenSSL 3.0)

Your message dated Wed, 18 May 2022 07:33:45 + with message-id and subject line Bug#1010962: fixed in libstrophe 0.12.0-2 has caused the Debian Bug report #1010962, regarding libstrophe FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1011176: apertium-recursive: fails to detect EOF condition on unsigned char archs

Fix applied upstream https://github.com/apertium/apertium-recursive and new release pushed to https://salsa.debian.org/science-team/apertium-recursive awaiting upload. -- Tino Didriksen

Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch

On 29/04/2022 08.25, Paul Gevers wrote: If you're otherwise stuck, I can temporarily give you access to our host, but if you know what you'd want to try out you can also just pass detailed instructions to me and I'll execute them in the container. Sorry, it took some time to prepare instructio

Bug#965446: marked as done (cappuccino: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Wed, 18 May 2022 07:18:41 + with message-id and subject line Bug#965446: fixed in cappuccino 0.5.1-10 has caused the Debian Bug report #965446, regarding cappuccino: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim tha

Bug#995242: isc-dhcp-server: omshell returns inconsistent results or segfaults

Hi, On Tue, 10 May 2022 10:13:11 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?= wrote: Control: forwarded -1 https://gitlab.isc.org/isc-projects/dhcp/-/issues/167 On Mon, 7 Mar 2022 14:41:23 -0800 Harris Enniss wrote: > We encountered this as well. It seems to be an issue with the way debian