Bug#1022788: marked as done (cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 05:51:01 + with message-id and subject line Bug#1022788: fixed in cockpit 278-1 has caused the Debian Bug report #1022788, regarding cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures to be marked as done. This means that you claim that the

Processed: Re: Bug#1022788: cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 fixed-upstream pending Bug #1022788 [src:cockpit] cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures Added tag(s) pending and fixed-upstream. -- 1022788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022788 Debian Bug Tracking System

Bug#1022788: cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures

2022-10-28 Thread Martin Pitt
Control: tag -1 fixed-upstream pending Hello again, Martin Pitt [2022-10-26 6:04 +0200]: > Argh, this keeps haunting us. We already tried to fix that in [1] and [2], but > no way. Why must glib be so unpredictable?  > [2] https://github.com/cockpit-project/cockpit/pull/17755 Nevermind.. [2]

Bug#1021810: Should firefox-esr be dropped on 32bit architectures in bookworm?

2022-10-28 Thread Adrian Bunk
On Thu, Oct 20, 2022 at 09:25:34AM +0200, Axel Beckert wrote: >... > P.S.: Due to making this bug report "release critical", automatic > updates on stable with apt-listbugs stopped applying firefox-esr > security updates. Otherwise I wouldn't have noticed it. :-P The bug is tagged "bookworm,

Bug#1023009: golang-github-coredhcp-coredhcp: binary-all FTBFS

2022-10-28 Thread Adrian Bunk
Source: golang-github-coredhcp-coredhcp Version: 0.0.0+git.2022.04.07.a2552c5c1b-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=golang-github-coredhcp-coredhcp=all=0.0.0%2Bgit.2022.04.07.a2552c5c1b-3=1666975743=0 ... dh_install rm -f

Bug#1023008: fdroidserver: autopkgtest regression with openjdk-11 11.0.17+8-2

2022-10-28 Thread Adrian Bunk
Source: fdroidserver Version: 2.1.1-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/27601295/log.gz ... == ERROR: test_verify_jar_signature_succeeds (__main__.CommonTest)

Processed: mark relationship

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1021803 by 1017739 Bug #1021803 [src:gnuserv] "gnuserv seems to be affected badly by #1017739" 1021803 was not blocked by any bugs. 1021803 was blocking: 1020050 Added blocking bug(s) of 1021803: 1017739 > thanks Stopping processing here.

Bug#1023006: tpm2-pkcs11: binary-any FTBFS

2022-10-28 Thread Adrian Bunk
Source: tpm2-pkcs11 Version: 1.8.0-0.1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Bastian Germann https://buildd.debian.org/status/logs.php?pkg=tpm2-pkcs11=1.8.0-0.1 ... checking for module pyasn1_modules in python... configure: error: not found This should be moved from Build-Depends-Indep

Bug#1017845: New upload should resolve native compilation fork bomb problem

2022-10-28 Thread Axel Beckert
Control: fixed -1 1:28.2+1-3 Hi Sean, Sean Whitton wrote: > Thank you for testing so promptly. There's an additional patch that > just made it to upstream master that tries to address the trampoline > problem. I've just uploaded that to sid. Could you let me know whether > it helps, please?

Processed: Re: Bug#1017845: New upload should resolve native compilation fork bomb problem

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1:28.2+1-3 Bug #1017817 [emacs-common] emacs: new release seems to have funny ideas about byte-compiling process Bug #1017845 [emacs-common] emacs-common: Endless fork loop at installation and at run time: /usr/bin/emacs --batch -l

Processed: Re: Bug#1017845: New upload should resolve native compilation fork bomb problem

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1:28.2+1-3 Bug #1017845 [emacs-common] emacs-common: Endless fork loop at installation and at run time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-_{scroll_other_window,delete_frame}_0-.el Bug #1017817 [emacs-common] emacs: new release

Bug#922579: FTBFS against opencv 4.0.1 (exp)

2022-10-28 Thread Bo YU
Source: freeture Version: 1.3.0-1 Followup-For: Bug #922579 Dear Maintainer, I have tried to build it with switching to opencv4, but it fails. The searon failed is not only opencv4's api incompatibility, but also aravis need to upgrade from 0.6 to 0.8, this also leads to the api

Bug#1021109: marked as done (bash: non existent locale crashes bash)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 03:18:02 +0300 with message-id and subject line Fixed in 5.2-2 has caused the Debian Bug report #1021109, regarding bash: non existent locale crashes bash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1022934: closed by Adrian Bunk (Fixed in 0.8.58-1)

2022-10-28 Thread Adrian Bunk
On Fri, Oct 28, 2022 at 05:54:13PM +0200, Sebastian Ramacher wrote: > On 2022-10-28 15:45:05 +, Debian Bug Tracking System wrote: >... > > Version: 0.8.58-1 > > That version does not exist in the archive > > > libpappsomspp (0.8.58-1) bullseye; urgency=low > > … and that's the reason why.

Processed: Mark as affecting gcc-12

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1022991 ftbfs Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el Added tag(s) ftbfs. > affects 1022991 src:gcc-12 Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el Added indication that 1022991

Bug#1022300: marked as done (kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: QGpgME/RefreshOpenPGPKeysJob: No such file or directory)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 22:56:19 + with message-id and subject line Bug#1022300: fixed in kleopatra 4:22.08.2-1 has caused the Debian Bug report #1022300, regarding kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: QGpgME/RefreshOpenPGPKeysJob: No such file or

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-28 Thread Christoph Anton Mitterer
Hey Salvatore. On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote: > I did decide to still do so, so we can have the CVE fix migrate > finally to testing (which took some time as well given there was the > perl transition ongoing). Fine for me... I think it would be nice if there was

Bug#1021524: marked as done (lomiri-system-settings is not installable)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:59:54 + with message-id and subject line Bug#1021524: fixed in lomiri-system-settings 1.0~git20221028.ca6da85-1 has caused the Debian Bug report #1021524, regarding lomiri-system-settings is not installable to be marked as done. This means that you

Bug#1023000: dpdk: flaky autopkgtest on amd64 and ppc64el: pdump_autotest time out

2022-10-28 Thread Paul Gevers
Source: dpdk Version: 20.11.5-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on amd64 and ppc64el. From a cursory look it seems to have started around August

Bug#1017161: gringo: FTBFS: catch.hpp:6415:41: error: array bound is not an integer constant before ‘]’ token

2022-10-28 Thread s3v
Dear Maintainer, [...] > In file included from /<>/clasp/libpotassco/tests/main.cpp:19: > /<>/clasp/libpotassco/tests/catch.hpp:6415:41: error: array > bound is not an integer constant before ‘]’ token >  6415 | static char altStackMem[SIGSTKSZ]; >   | 

Processed: Re: Bug#1022991: libc6: broken y2038 support in fstatat on mips64el

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=29730 Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=29730'. -- 1022991:

Bug#1022991: libc6: broken y2038 support in fstatat on mips64el

2022-10-28 Thread Aurelien Jarno
control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=29730 On 2022-10-28 20:35, Aurelien Jarno wrote: > Package: libc6 > Version: 2.35-1 > Severity: critical > Tags: upstream > Justification: breaks unrelated software > > On mips64el the fstat/fstatat/lstat functions return

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

2022-10-28 Thread Tobias Hansen
Thanks! I will apply the patch once the pari version with the other fixes is uploaded. Best wishes, Tobias On 10/26/22 10:55, Bill Allombert wrote: > Also I consider the error message change > - PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC > (1 elts) > +

Bug#1021138: marked as done (php8.1: CVE-2022-31628 CVE-2022-31629)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:30:30 +0200 with message-id and subject line Re: Accepted php8.1 8.1.12-1 (source) into unstable has caused the Debian Bug report #1021138, regarding php8.1: CVE-2022-31628 CVE-2022-31629 to be marked as done. This means that you claim that the problem has

Bug#1016972: marked as done (php8.1: CVE-2022-31627)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:29:15 +0200 with message-id and subject line Re: Accepted php8.1 8.1.12-1 (source) into unstable has caused the Debian Bug report #1016972, regarding php8.1: CVE-2022-31627 to be marked as done. This means that you claim that the problem has been dealt

Processed: found 1016972 in 8.1.7-1

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1016972 8.1.7-1 Bug #1016972 [src:php8.1] php8.1: CVE-2022-31627 Marked as found in versions php8.1/8.1.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1016972:

Bug#1017845: New upload should resolve native compilation fork bomb problem

2022-10-28 Thread Axel Beckert
Hi Sean, Sean Whitton wrote: > > Ok, someone gave back emacs:all and it built now. > > Yeah, there's a flaky test. I see. > > Unfortunately the issue still shows up for me: > > Thank you for testing so promptly. You're welcome! Actually I'm very keen on seeing a (working ;-) Emacs 28 in

Bug#1022991: libc6: broken y2038 support in fstatat on mips64el

2022-10-28 Thread Aurelien Jarno
Package: libc6 Version: 2.35-1 Severity: critical Tags: upstream Justification: breaks unrelated software On mips64el the fstat/fstatat/lstat functions return EOVERFLOW when they are called on files with a mtime, atime or ctime that can't be represented within a 32-bit time_t. This should not

Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists

2022-10-28 Thread Gert
I suspect to have this same bug. In case it's useful, I got kernel logs via serial console, see attachment. Therein I have marked where VGA console output stops. Serial console goes a bit further. SysRq+B still works. My system: MSI 785GM-E51 (AMD 785G+SB710) + Dell Radeon R5 240 OEM (Oland). I

Bug#1017845: New upload should resolve native compilation fork bomb problem

2022-10-28 Thread Sean Whitton
Hello, On Thu 27 Oct 2022 at 12:47AM +02, Axel Beckert wrote: > Control: found -1 1:28.2+1-2 > > Hi Sean, > > Axel Beckert wrote: >> Sean Whitton wrote: >> > Could you see if the upload I just made, 28.2+1-2, still shows the >> > problem, please? It includes a backported upstream fix. Thanks.

Bug#1022854: debuerreotype: autopkgtest rebuilds with different toolchain and expects the same result

2022-10-28 Thread Tianon Gravi
On Fri, 28 Oct 2022 at 10:42, Luca Boccassi wrote: > (18:32:13) bluca: the debuerrotype maintainer explicitly asked not to, > and instead to ask for a migration hint > (18:32:46) elbrus: we'll not do that > (18:32:58) elbrus: as the autopkgtest regression in testing is RC Sorry, this was my

Bug#1022980: src:ruby-vcr: fails to migrate to testing for too long: ftbfs

2022-10-28 Thread Paul Gevers
Source: ruby-vcr Version: 6.0.0+really5.0.0-2 Severity: serious Control: close -1 6.0.0+really5.0.0-3 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1019674 Dear maintainer(s), The Release Team considers packages that are

Processed: src:ruby-vcr: fails to migrate to testing for too long: ftbfs

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 6.0.0+really5.0.0-3 Bug #1022980 [src:ruby-vcr] src:ruby-vcr: fails to migrate to testing for too long: ftbfs The source 'ruby-vcr' and version '6.0.0+really5.0.0-3' do not appear to match any binary packages Marked as fixed in versions

Processed: src:gnumach: fails to migrate to testing for too long: ftbfs on amd64

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2:1.8+git20220827-3 Bug #1022979 [src:gnumach] src:gnumach: fails to migrate to testing for too long: ftbfs on amd64 Marked as fixed in versions gnumach/2:1.8+git20220827-3. Bug #1022979 [src:gnumach] src:gnumach: fails to migrate to testing for too long:

Bug#1022979: src:gnumach: fails to migrate to testing for too long: ftbfs on amd64

2022-10-28 Thread Paul Gevers
Source: gnumach Version: 2:1.8+git20220218-3 Severity: serious Control: close -1 2:1.8+git20220827-3 Tags: sid bookworm ftbfs 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

Processed (with 1 error): Re: Bug#1022854: debuerreotype: autopkgtest rebuilds with different toolchain and expects the same result

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1022854 [debuerreotype] debuerreotype: autopkgtest rebuilds with different toolchain and expects the same result Severity set to 'serious' from 'important' > justification -1 breaks autopkgtest in testing Unknown command or malformed

Processed: src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.30.0-3 Bug #1022978 [src:atlas-ecmwf] src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x Marked as fixed in versions atlas-ecmwf/0.30.0-3. Bug #1022978 [src:atlas-ecmwf] src:atlas-ecmwf: fails to migrate to testing for

Bug#1022978: src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x

2022-10-28 Thread Paul Gevers
Source: atlas-ecmwf Version: 0.29.0-2 Severity: serious Control: close -1 0.30.0-3 Tags: sid bookworm ftbfs 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 more than

Bug#1022975: Fails to build for 6.0.0: error: implicit declaration of function ‘__grab_cache_page’

2022-10-28 Thread Ryan Kavanagh
Package: openafs-modules-dkms Version: 1.8.8.1-3 Severity: grave Justification: Renders package unusable The openafs DKMS module fails to build for kernel 6.0.0. Here are the relevant bits from the end of the attached build log /var/lib/dkms/openafs/1.8.8.1/build/make.log: In file included from

Bug#1020043: marked as done (pillow: FTBFS: ModuleNotFoundError: No module named 'PIL')

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 16:20:33 + with message-id and subject line Bug#1020043: fixed in pillow 9.2.0-1.1 has caused the Debian Bug report #1020043, regarding pillow: FTBFS: ModuleNotFoundError: No module named 'PIL' to be marked as done. This means that you claim that the

Bug#1022934: closed by Adrian Bunk (Fixed in 0.8.58-1)

2022-10-28 Thread Sebastian Ramacher
On 2022-10-28 15:45:05 +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:libpappsomspp package: > > #1022934: libpappsomspp: FTBFS on i386 > > It has been closed by Adrian Bunk . > > Their explanation is

Bug#877015: marked as done (fizmo FTBFS with debhelper 10.9)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:48:24 + with message-id and subject line Bug#1022757: Removed package(s) from unstable has caused the Debian Bug report #877015, regarding fizmo FTBFS with debhelper 10.9 to be marked as done. This means that you claim that the problem has been dealt

Bug#1022934: marked as done (libpappsomspp: FTBFS on i386)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 18:41:51 +0300 with message-id and subject line Fixed in 0.8.58-1 has caused the Debian Bug report #1022934, regarding libpappsomspp: FTBFS on i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#1022795: marked as done (libghc-crypto-numbers-doc: depends on non-existing haddock-interface-35)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:30 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1022795, regarding libghc-crypto-numbers-doc: depends on non-existing haddock-interface-35 to be marked as done. This means that

Bug#1021068: marked as done (Removal notice: obsolete)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:04 + with message-id and subject line Bug#1022876: Removed package(s) from unstable has caused the Debian Bug report #1021068, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1021067: marked as done (Removal notice: obsolete)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:30 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1021067, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1015291: marked as done (haskell-crypto-numbers FTBFS: error: Variable not in scope)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:30 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1015291, regarding haskell-crypto-numbers FTBFS: error: Variable not in scope to be marked as done. This means that you claim that

Bug#1017201: marked as done (haskell-crypto-pubkey: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.13.0.0-2f220, libghc-bytestring-dev-0.10.10.1-c40ee, libghc-crypto-random-dev-0.0.9-1612d

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:04 + with message-id and subject line Bug#1022876: Removed package(s) from unstable has caused the Debian Bug report #1017201, regarding haskell-crypto-pubkey: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.13.0.0-2f220,

Bug#1019611: marked as done (ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {})

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:20:24 + with message-id and subject line Bug#1019611: fixed in ruby-asset-sync 2.11.0-1.1 has caused the Debian Bug report #1019611, regarding ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||=

Bug#1020093: marked as done (python-dlt: FTBFS: AssertionError: 1 != 0 : Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after keyword)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:20:14 + with message-id and subject line Bug#1020093: fixed in python-dlt 2.0-3.1 has caused the Debian Bug report #1020093, regarding python-dlt: FTBFS: AssertionError: 1 != 0 : Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after

Processed: bug 1019612 is forwarded to https://github.com/dmendel/bindata/issues/144

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1019612 https://github.com/dmendel/bindata/issues/144 Bug #1019612 [src:ruby-bindata] ruby-bindata: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Set Bug forwarded-to-address to 'https://github.com/dmendel/bindata/issues/144'. >

Processed: Re: prometheus-openstack-exporter: FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +pending Bug #1021925 [src:prometheus-openstack-exporter] prometheus-openstack-exporter: FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13 Ignoring request to alter tags of bug #1021925 to the same tags previously

Bug#1021925: prometheus-openstack-exporter: FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13

2022-10-28 Thread Tobias Frost
Source: prometheus-openstack-exporter Followup-For: Bug #1021925 Control: tags -1 +pending Dear maintainer, I've uploaded Raúl's NMU to DELAYED/2. Let me know if I should delay it any longer. -- tobi signature.asc Description: PGP signature

Bug#1022957: nex: /usr/bin/nex is already provided by the nvi package

2022-10-28 Thread Andreas Beckmann
Package: nex Version: 0.0.0+git.2021.03.30.1a3320dab9-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the

Bug#949355: Removing simpleitk from Debian (Was: simpleitk FTBFS: test failures)

2022-10-28 Thread Andreas Tille
Hi Ghislain, I tried to upgrade simpleitk to latest upstream in Git but failed. IMHO only the latest upstream which is supposed to be compatible to ITK5 makes sense to support inside Debian. You are listed as Maintainer of the package. Do you think you are able to work on this package?

Bug#1022025: fixed in linux 5.10.149-2

2022-10-28 Thread Jorge Barreiro
Just wanted to report that version 5.10.149-2 fixed the issue for me. Using "AMD Ryzen 5 PRO 4650G with Radeon Graphics" with its integraded graphics.

Bug#1020593: marked as done (mmdebstrap: debootstrap installing empty lsb-base package prevents autopkgtest from passing)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:31:30 +0200 with message-id <166696029071.179823.17637090374395556686@localhost> and subject line Re: mmdebstrap: debootstrap installing empty lsb-base package prevents autopkgtest from passing has caused the Debian Bug report #1020593, regarding mmdebstrap:

Bug#1013157: Asking for removal from Debian (Was: nifti2dicom: vtk[6,7] removal)

2022-10-28 Thread Andreas Tille
Hi, I've added to the upstream issue[1] that I will ask ftpmaster for removal from Debian if there is no visible sign that there is any interest to port the code to recent VTK. Just to let readers of Debian Med know that this package is about to be removed. Kind regards Andreas. [1]

Bug#1022169: marked as done (llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat))

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 12:03:42 + with message-id and subject line Bug#1022169: fixed in llvm-toolchain-15 1:15.0.3-2 has caused the Debian Bug report #1022169, regarding llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat) to be

Bug#1022304: marked as done (lsp-mode: FTBFS: lsp-completion.el:166:8: Error: docstring wider than 80 characters)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 11:19:36 + with message-id and subject line Bug#1022304: fixed in lsp-mode 8.0.0-5 has caused the Debian Bug report #1022304, regarding lsp-mode: FTBFS: lsp-completion.el:166:8: Error: docstring wider than 80 characters to be marked as done. This means

Processed: Bug#1016070 marked as pending in sbuild

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1016070 [src:sbuild] sbuild: autopkgtest fails with "No space left on device" Added tag(s) pending. -- 1016070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1016070: marked as pending in sbuild

2022-10-28 Thread Johannes Schauer Marin Rodrigues
Control: tag -1 pending Hello, Bug #1016070 in sbuild 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#1019765: wxsvg: Please transition to wxwidgets3.2

2022-10-28 Thread Alec Leamas
On Wed, 14 Sep 2022 15:42:16 -0400 s...@techie.net wrote: Source: wxsvg Severity: normal Control: block 1019416 by -1 Hi, Please transition wxsvg from wxwidgets3.0 to wxwidgets3.2. wxsvg is basically a dependency of opencpn, I'm not aware of any other package depending on it. As such, the

Bug#1020819: marked as done (subtitlecomposer: Cannot load any video: "Option refcounted_frames not found" error (removed from FFmpeg))

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 10:06:31 + with message-id and subject line Bug#1020819: fixed in subtitlecomposer 0.7.1-4 has caused the Debian Bug report #1020819, regarding subtitlecomposer: Cannot load any video: "Option refcounted_frames not found" error (removed from FFmpeg) to be

Processed: tagging 1020056

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1020056 + pending Bug #1020056 [src:tango] tango: FTBFS: configure: error: Couldn't find a compatible zmq.hpp Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020056:

Processed: found 1019782 in 1.0.1-3

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Tell BTS that this RC bug doesn't affect stable > found 1019782 1.0.1-3 Bug #1019782 {Done: Ole Streicher } [src:gnudatalanguage] gnudatalanguage: Please transition to wxwidgets3.2 Marked as found in versions gnudatalanguage/1.0.1-3. > thanks

Bug#1020895: marked as done (whatmaps: postinst fails in clean chroot/container)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 08:41:47 + with message-id and subject line Bug#1020895: fixed in whatmaps 0.0.12-4 has caused the Debian Bug report #1020895, regarding whatmaps: postinst fails in clean chroot/container to be marked as done. This means that you claim that the problem has

Processed: affects 1022233

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1022233 src:rust-isahc Bug #1022233 [librust-tracing-subscriber-dev] librust-tracing-subscriber-dev: impossible to install Added indication that 1022233 affects src:rust-isahc > thanks Stopping processing here. Please contact me if you

Bug#1022297: marked as done (neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s')

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 09:18:42 +0200 with message-id and subject line Re: Bug#1022297: neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s' has caused the Debian Bug report #1022297, regarding neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3:

Processed: Re: Bug#1022297: neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1022297 20220429+dfsg1-2 Bug #1022297 [src:neomutt] neomutt: FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s' Marked as fixed in versions neomutt/20220429+dfsg1-2. > thanks Stopping processing here. Please

Bug#1022848: marked as done (6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 07:11:50 + with message-id and subject line Bug#1022848: fixed in linux 6.0.5-1 has caused the Debian Bug report #1022848, regarding 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems to be marked as done. This means that you

Bug#1022927: marked as done (libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 09:02:20 +0300 with message-id <20221028060220.6b7dfkdxzvkee...@iliastsi.net> and subject line Re: Bug#1022927: libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a has caused the Debian Bug report #1022927, regarding libghc-aeson-dev