Bug#1013335: rust-hyper: impossible to install

2022-06-22 Thread Jonas Smedegaard
Source: rust-hyper Version: 0.12.35-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Main binary package, librust-hyper-dev, declares impossible to satisfy dependencies, and consequently all binary packages are impossible to install.

Processed: Re: markdown-it-py: FTBFS with flit < 3.4 (<3.3?)

2022-06-22 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #1013204 [src:markdown-it-py] markdown-it-py: FTBFS with flit < 3.4 (<3.3?) Severity set to 'wishlist' from 'serious' > retitle -1 markdown-it-py: backport for bullseye Bug #1013204 [src:markdown-it-py] markdown-it-py: FTBFS with flit < 3.4

Bug#1013348: test_elf.py fails with binutils in unstable

2022-06-22 Thread Matthias Klose
Package: src:diffoscope Version: 216 Severity: serious the test_elf.py test fails with binutils from the trunk: [...] FAILED tests/comparators/test_elf.py::test_diff - AssertionError FAILED tests/comparators/test_elf.py::test_lib_differences - AssertionError

Bug#1013204: markdown-it-py: FTBFS with flit < 3.4 (<3.3?)

2022-06-22 Thread Bastian Germann
Control: severity -1 wishlist Control: retitle -1 markdown-it-py: backport for bullseye On Sat, 18 Jun 2022 17:58:24 -0500 "David (Plasma) Paul" wrote: markdown-it-py fails to build from source with versions of flit earlier than 3.4 according to the package's pyproject.toml.[0] Attached is a

Bug#1013299: linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport

2022-06-22 Thread Diederik de Haas
On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote: > > So yes, this needs to also be fixed upstream (hence me including that tag > > when reporbugging), but perhaps Debian can quickfix. > > What I have observed so far is that a commit needs to be accepted upstream > (but doesn't have

Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack

2022-06-22 Thread Julien Cristau
On Wed, Jun 22, 2022 at 10:50:48AM +0200, Michael Biebl wrote: > Package: gnu-efi > Version: 3.0.13+git20210716.269ef9d-2 > Severity: serious > Forwarded: https://sourceforge.net/p/gnu-efi/bugs/28/ > > Hi, > > since the latest update of binutils to 2.38.50.20220615, > the systemd source package

Processed (with 2 errors): Re: Bug#1010747 closed by Debian FTP Masters

2022-06-22 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1010747 {Done: Georges Khaznadar } [shiboken2] Unusable with current python version 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer

Bug#1010747: closed by Debian FTP Masters

2022-06-22 Thread Bastian Germann
Control: reopen -1 Control: notfixed pyacidobasic/2.11.1-2 Control: notfixed pymecavideo/7.2.1-3 On Wed, 08 Jun 2022 15:03:50 +0200 Yuri D'Elia wrote: This bug was against shiboken2, but was fixed pyacidobasic? I just verified nothing has been fixed in shiboken2 yet. Georges, please pay

Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack

2022-06-22 Thread Michael Biebl
Am 22.06.22 um 11:49 schrieb Julien Cristau: On Wed, Jun 22, 2022 at 10:50:48AM +0200, Michael Biebl wrote: Marking as RC, as it causes a FTBFS Not using -Wl,--fatal-warnings might be a workaround for systemd until gnu-efi fixes this? Yeah, I'll probably add a workaround like diff

Bug#1013341: /usr/bin/ld.bfd: warning: /usr/lib/crt0-efi-x86_64.o: missing .note.GNU-stack section implies executable stack

2022-06-22 Thread Michael Biebl
Package: gnu-efi Version: 3.0.13+git20210716.269ef9d-2 Severity: serious Forwarded: https://sourceforge.net/p/gnu-efi/bugs/28/ Hi, since the latest update of binutils to 2.38.50.20220615, the systemd source package fails to build: ``` $ ninja -C build/ ninja: Entering directory `build/'

Bug#1011698: marked as done (voms-api-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven

2022-06-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jun 2022 10:55:09 + with message-id and subject line Bug#1011698: fixed in voms-api-java 3.3.2-2 has caused the Debian Bug report #1011698, regarding voms-api-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp

Processed: Re: test_elf.py fails with binutils in unstable

2022-06-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1013348 + pending Bug #1013348 [src:diffoscope] test_elf.py fails with binutils in unstable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013348:

Bug#1011714: gitless: FTBFS: ValueError: invalid argument: 'file || path'

2022-06-22 Thread Timo Röhling
Control: reassign -1 src:python-pygit2 Control: retitle -1 python-pygit2: import fails if /usr/lib/ssl/certs does not exist Looks like python-pygit2 needs the OpenSSL certificate paths set up properly to function. The problem disappears if the openssl package is installed. On Thu, 26 May 2022

Processed: Re: gitless: FTBFS: ValueError: invalid argument: 'file || path'

2022-06-22 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:python-pygit2 Bug #1011714 [src:gitless] gitless: FTBFS: ValueError: invalid argument: 'file || path' Bug reassigned from package 'src:gitless' to 'src:python-pygit2'. No longer marked as found in versions gitless/0.8.8-4. Ignoring request to alter

Bug#1013348: test_elf.py fails with binutils in unstable

2022-06-22 Thread Chris Lamb
tags 1013348 + pending thanks > the test_elf.py test fails with binutils from the trunk: Thanks for the report. I've fixed this earlier today with this commit: https://salsa.debian.org/reproducible-builds/diffoscope/commit/280ff40115af104685932b96e83ccb79f78afabb It fixes it in our Salsa CI

Bug#1013355: groovy: FTBFS with jansi 2.4.0-1

2022-06-22 Thread Markus Koschany
Package: groovy Version: 2.4.21-1 Severity: serious X-Debbugs-Cc: a...@debian.org groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or upgrade to a newer upstream release in the future. Markus

Bug#1011755: marked as done (gdb-doc: FTBFS: configure: error: GMP is missing or unusable)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jun 2022 17:04:16 + with message-id and subject line Bug#1011755: fixed in gdb-doc 12.1-1 has caused the Debian Bug report #1011755, regarding gdb-doc: FTBFS: configure: error: GMP is missing or unusable to be marked as done. This means that you claim that the

Bug#1013355: groovy: FTBFS with jansi 2.4.0-1

2022-06-22 Thread Emmanuel Bourg
Le 2022-06-22 17:54, Markus Koschany a écrit : groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or upgrade to a newer upstream release in the future. Please hold the upload, this is going to blow up Maven and Gradle. I've introduced jansi1 to try to work around the issue but

Bug#1013355: groovy: FTBFS with jansi 2.4.0-1

2022-06-22 Thread Markus Koschany
Forgot to CC the bug report Am Mittwoch, dem 22.06.2022 um 18:14 +0200 schrieb Emmanuel Bourg: > Le 2022-06-22 17:54, Markus Koschany a écrit : > > > groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or > > upgrade to a newer upstream release in the future. > > Please hold the

Processed: severity of 1013191 is wishlist

2022-06-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1013191 wishlist Bug #1013191 [src:mdurl] mdurl: FTBFS with flit < 3.2 Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1013191:

Bug#1012494: marked as done (gdb: FTBFS on ppc family: No rule to make target 'info' in build/default/sim/ppc)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jun 2022 16:34:01 + with message-id and subject line Bug#1012494: fixed in gdb 12.1-1 has caused the Debian Bug report #1012494, regarding gdb: FTBFS on ppc family: No rule to make target 'info' in build/default/sim/ppc to be marked as done. This means that you

Processed: forcemerge deal.ii FTBFS bugs

2022-06-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1011655 1012126 Bug #1011655 [src:deal.ii] deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb Bug #1012126 [src:deal.ii] deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental Severity set to 'important' from

Processed: fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected

2022-06-22 Thread Debian Bug Tracking System
Processing control commands: > found -1 fonttools/4.33.3-1 Bug #1013363 [src:fonttools, src:glyphslib] fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected Marked as found in versions fonttools/4.33.3-1. > found -1 glyphslib/5.3.2+ds1-1 Bug

Bug#1013364: dicomnifti: autopkgtest failure: number of repetitions is less than two

2022-06-22 Thread Paul Gevers
Source: dicomnifti Version: 2.33.1-4 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dicomnifti, great. However, it fails on i386 and s390x. Currently this failure is blocking the migration to

Bug#1013365: python-aiortc: autopkgtest regression on armhf: [Errno 542398533] Generic error in an external library

2022-06-22 Thread Paul Gevers
Source: python-aiortc Version: 1.3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-aiortc the autopkgtest of python-aiortc fails in testing on armhf when that autopkgtest is run with the binary packages of

Bug#1012544: marked as done (libworkflow1: Broken shared library packaging)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jun 2022 19:00:15 + with message-id and subject line Bug#1012544: fixed in workflow 0.10.1-1 has caused the Debian Bug report #1012544, regarding libworkflow1: Broken shared library packaging to be marked as done. This means that you claim that the problem has been

Processed: raise severity of deal.ii FTBFS bugs again

2022-06-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1011655 serious Bug #1011655 [src:deal.ii] deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb Bug #1012126 [src:deal.ii] deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental Severity set to 'serious' from

Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!

2022-06-22 Thread Paul Gevers
Hi Diederik, On 21-06-2022 23:19, Diederik de Haas wrote: I think that the install logs aren't that important (anymore) as the issue/ symptoms appear to be the same: - some swap action resulting in some failure - CPU gets stuck - watchdog triggers a reboot If the reboot would actually

Bug#1013360: src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el

2022-06-22 Thread Paul Gevers
Source: ruby3.0 Version: 3.0.3-1 Severity: serious Control: close -1 3.0.4-7 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), I know you know, but to track it, I'm still filing this bug. The Release Team considers packages that are

Processed: src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el

2022-06-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.0.4-7 Bug #1013360 [src:ruby3.0] src:ruby3.0: fails to migrate to testing for too long: causes autopkgtest failure on ppc64el Marked as fixed in versions ruby3.0/3.0.4-7. Bug #1013360 [src:ruby3.0] src:ruby3.0: fails to migrate to testing for too long:

Bug#1013362: src:alt-ergo: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel

2022-06-22 Thread Paul Gevers
Source: alt-ergo Version: 2.0.0-8 Severity: serious 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 60 days as having a Release

Bug#1013363: fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected

2022-06-22 Thread Paul Gevers
Source: fonttools, glyphslib Control: found -1 fonttools/4.33.3-1 Control: found -1 glyphslib/5.3.2+ds1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of fonttools the autopkgtest of glyphslib fails

Processed: severity of 1004579 is serious, severity of 1004594 is serious, severity of 1004596 is serious ...

2022-06-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004579 serious Bug #1004579 [src:mplayer] mplayer: FTBFS with ffmpeg 5.0 Severity set to 'serious' from 'important' > severity 1004594 serious Bug #1004594 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS with ffmpeg

Bug#1012600: marked as done (zfs-dkms: Compilation fails. ZFS completely non-functional after latest kernel upgrade.)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jun 2022 04:06:10 + with message-id and subject line Bug#1012600: fixed in zfs-linux 2.1.5-1 has caused the Debian Bug report #1012600, regarding zfs-dkms: Compilation fails. ZFS completely non-functional after latest kernel upgrade. to be marked as done. This

Bug#1002237: Any chance of re-introduction?

2022-06-22 Thread Bernhard
Dear maintainer Is there a chance of re-introduction in bullseye? The package "package-update-indicator" recommends "gnome-packagekit". For this, i created the bug #1010802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010802 Best regards and thank you Bernhard

Processed: Bug#1011714 marked as pending in python-pygit2

2022-06-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1011714 [src:python-pygit2] python-pygit2: import fails if /usr/lib/ssl/certs does not exist Added tag(s) pending. -- 1011714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011714 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!

2022-06-22 Thread Diederik de Haas
Hi Paul, On Wednesday, 22 June 2022 21:57:06 CEST Paul Gevers wrote: > On 21-06-2022 23:19, Diederik de Haas wrote: > > > I think that the install logs aren't that important (anymore) as the > > issue/symptoms appear to be the same: > > - some swap action resulting in some failure > > - CPU gets

Bug#1011714: marked as pending in python-pygit2

2022-06-22 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1011714 in python-pygit2 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#1011714: marked as done (python-pygit2: import fails if /usr/lib/ssl/certs does not exist)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jun 2022 21:37:45 + with message-id and subject line Bug#1011714: fixed in python-pygit2 1.8.0-3 has caused the Debian Bug report #1011714, regarding python-pygit2: import fails if /usr/lib/ssl/certs does not exist to be marked as done. This means that you claim

Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!

2022-06-22 Thread Diederik de Haas
On Wednesday, 22 June 2022 23:15:46 CEST Diederik de Haas wrote: > Via sources.list.erb I found that "<%= node['debian_release'] %>-backports" > gets enabled, which I assume results in Stable-backports. > It appears that various tools get installed (but I don't see qemu mentioned > (explicitly)),

Bug#1013364: dicomnifti: autopkgtest failure: number of repetitions is less than two

2022-06-22 Thread Valerio Luccio
Puzzling, this package has not changed since November 2017. Not sure what I'm supposed to do next. Thanks, On 6/22/22 4:15 PM, Paul Gevers wrote: Source: dicomnifti Version: 2.33.1-4 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently

Bug#1012596: marked as done (cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jun 2022 00:51:25 + with message-id and subject line Bug#1012596: fixed in timeshift 22.06.1-0.1 has caused the Debian Bug report #1012596, regarding cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron to be marked as done. This means

Bug#1005985: marked as done (Please migrate away from dpatch)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jun 2022 01:21:42 + with message-id and subject line Bug#1005985: fixed in scim-skk 0.5.2-7.3 has caused the Debian Bug report #1005985, regarding Please migrate away from dpatch to be marked as done. This means that you claim that the problem has been dealt with.

Bug#998953: marked as done (scim-skk: missing required debian/rules targets build-arch and/or build-indep)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jun 2022 01:21:42 + with message-id and subject line Bug#998953: fixed in scim-skk 0.5.2-7.3 has caused the Debian Bug report #998953, regarding scim-skk: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Processed: Correct bug closing info

2022-06-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 1012596 timeshift/22.06.1-0.1 Bug #1012596 {Done: Boyuan Yang } [cron-daemon-common] cron-daemon-common: missing versioned Breaks+Replaces against bcron, systemd-cron The source timeshift and version 22.06.1-0.1 do not appear to match

Bug#1004625: marked as done (libextractor: FTBFS with ffmpeg 5.0)

2022-06-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jun 2022 05:50:02 + with message-id and subject line Bug#1004625: fixed in libextractor 1:1.11-6 has caused the Debian Bug report #1004625, regarding libextractor: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt