Bug#1013460: marked as done (synfig: FTBFS with ffmpeg 5.0)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 05 Jul 2022 05:49:49 + with message-id and subject line Bug#1013460: fixed in synfig 1.5.1+dfsg-3 has caused the Debian Bug report #1013460, regarding synfig: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1013460: marked as pending in synfig

2022-07-04 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #1013460 in synfig 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:

Processed: Bug#1013460 marked as pending in synfig

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1013460 [src:synfig] synfig: FTBFS with ffmpeg 5.0 Added tag(s) pending. -- 1013460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1013929: marked as done (src:goffice: fails to migrate to testing for too long: FTBFS on mips64el)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 05 Jul 2022 05:18:50 + with message-id and subject line Bug#1013929: fixed in goffice 0.10.52-2 has caused the Debian Bug report #1013929, regarding src:goffice: fails to migrate to testing for too long: FTBFS on mips64el to be marked as done. This means that you

Bug#1012741: Subject: Re: Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-07-04 Thread Daniel Lewart
It's like déjà vu all over again: #942881 - snd-hda-codec-hdmi signature corruption https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881 Thank you! Dan Urbana, Illinois

Processed: Bug#1013929 marked as pending in goffice

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1013929 [src:goffice] src:goffice: fails to migrate to testing for too long: FTBFS on mips64el Added tag(s) pending. -- 1013929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013929 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1013929: marked as pending in goffice

2022-07-04 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #1013929 in goffice 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:

Processed: bug 1013929 is forwarded to https://gitlab.gnome.org/GNOME/goffice/-/issues/59

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1013929 https://gitlab.gnome.org/GNOME/goffice/-/issues/59 Bug #1013929 [src:goffice] src:goffice: fails to migrate to testing for too long: FTBFS on mips64el Set Bug forwarded-to-address to

Bug#1014353: Fwd: Processed: forcibly merging 1014314 1014353 [origin: ow...@bugs.debian.org]

2022-07-04 Thread Axel Beckert
Hi Marie, thanks for the hint in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014353#10 — your bug report is now marked as fixed: - Forwarded message from Debian Bug Tracking System - Date: Tue, 05 Jul 2022 02:45:06 + From: Debian Bug Tracking System To: Axel Beckert CC:

Processed: forcibly merging 1014314 1014353

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014353#10 > forcemerge 1014314 1014353 Bug #1014314 {Done: Bastian Blank } [lvm2] lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail Bug #1014353 [lvm2] lvm2:

Bug#1013662: core-async-clojure: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1

2022-07-04 Thread Jérôme Charaoui
Hello, I'm unable to reproduce this bug locally. When I diff, the build logs, the only relevant element I can find is that in my build environment, the "clojure_1.10.3-1" package is installed, whereas in the failing build log, it appears to be absent. I think it would be worth it to

Bug#1014368: dmesg: --human output not paged if less not installed

2022-07-04 Thread http
Package: util-linux Version: 2.38 Severity: serious The documentation for dmesg states that "A pager is enabled by default for --human output." However, if the less pager is not installed, the output is not sent to a pager unless the PAGER variable is set. This means that there is a

Bug#1013700: marked as done (python-qtpy: FTBFS: pytest7 regression, TypeError: the 'package' argument is required to perform a relative import)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 22:07:10 + with message-id and subject line Bug#1013700: fixed in python-qtpy 2.1.0-3 has caused the Debian Bug report #1013700, regarding python-qtpy: FTBFS: pytest7 regression, TypeError: the 'package' argument is required to perform a relative import to

Processed: Bug#1013700 marked as pending in python-qtpy

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1013700 [src:python-qtpy] python-qtpy: FTBFS: pytest7 regression, TypeError: the 'package' argument is required to perform a relative import Added tag(s) pending. -- 1013700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013700 Debian Bug

Bug#1013700: marked as pending in python-qtpy

2022-07-04 Thread Julian Gilbey
Control: tag -1 pending Hello, Bug #1013700 in python-qtpy 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#1013700: Strangely rare pytest 7.x bug report

2022-07-04 Thread Julian Gilbey
Hi Carles, It is utterly, utterly bizarre. But I think I've found the problem. There's a pytest.ini file in the package, but it's not copied into the test directory. So when pytest is run in the .pybuild directory, it climbs all the way back up the directory tree to the python-qtpy-2.1.0 until

Bug#1014282: marked as done (perl: autopkgtest failure: needs Provides/Replaces/Breaks for libtext-balanced-perl)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 21:13:37 + with message-id and subject line Bug#1014282: fixed in perl 5.34.0-5 has caused the Debian Bug report #1014282, regarding perl: autopkgtest failure: needs Provides/Replaces/Breaks for libtext-balanced-perl to be marked as done. This means that

Bug#1013720: marked as done (python-matrix-nio: FTBFS: pytest7 regression, deprecated pytest feature: -k-)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 21:13:58 + with message-id and subject line Bug#1013720: fixed in python-matrix-nio 0.19.0-4 has caused the Debian Bug report #1013720, regarding python-matrix-nio: FTBFS: pytest7 regression, deprecated pytest feature: -k- to be marked as done. This means

Bug#1013238: marked as done (src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 21:13:51 + with message-id and subject line Bug#1013238: fixed in pyspread 2.1-2.1 has caused the Debian Bug report #1013238, regarding src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary to be marked as done. This means

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-07-04 Thread Ansgar
Hi, On Mon, 2022-07-04 at 22:00 +0200, Ansgar wrote: > The correct signature (using OpenSSL) has: > > +--- > > 138 256:   OCTET STRING > >    : 00 00 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C B6 > +---[ data.ko.p7s.success ] > > The incorrect signature from the YK has: > >

Bug#1014358: src:why3: fails to migrate to testing for too long: blocked by dependency

2022-07-04 Thread Paul Gevers
Source: why3 Version: 1.4.1-2 Severity: serious Control: close -1 1.5.0-1 Tags: sid bookworm 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

Processed: src:why3: fails to migrate to testing for too long: blocked by dependency

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.5.0-1 Bug #1014358 [src:why3] src:why3: fails to migrate to testing for too long: blocked by dependency Marked as fixed in versions why3/1.5.0-1. Bug #1014358 [src:why3] src:why3: fails to migrate to testing for too long: blocked by dependency Marked

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-07-04 Thread Ansgar
Hi, I experimented a bit more and could reproduce the problem with a local YK (Yubikey 4, Firmware 4.3.7) and a known private key and certificate. The correct signature (using OpenSSL) has: +--- | 138 256: OCTET STRING |: 00 00 45 75 A8 93 B1 B1 37 0A 53 69 82 BB

Bug#1013700: Strangely rare pytest 7.x bug report

2022-07-04 Thread Carles Pina i Estany
Hi Julian, On Jul/04/2022, Julian Gilbey wrote: > Hi Carles, > > Thanks for your thoughts! Yes, indeed that seems to be the issue. > But what I don't understand is why the import is turned into > .pybuild.cpython3_3.9_qtpy.build.qtpy.tests and not just qtpy.tests or I see how pytest does it

Bug#1014114: installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds

2022-07-04 Thread Helmut Grohne
Hi, On Thu, Jun 30, 2022 at 05:15:32PM +0200, Helmut Grohne wrote: > > > For libsanitizer, crypt.h is needed to determine the size of a struct, the > > > library itself is not needed. Moving it to the MA location makes it > > > unavailable for the non-multilib builds. > > Again, the lack of

Bug#1013700: Strangely rare pytest 7.x bug report

2022-07-04 Thread Julian Gilbey
Hi Carles, Thanks for your thoughts! Yes, indeed that seems to be the issue. But what I don't understand is why the import is turned into .pybuild.cpython3_3.9_qtpy.build.qtpy.tests and not just qtpy.tests or a longer path, and why only this package fails in this way. Perhaps this is the only

Bug#1014314: marked as done (lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 18:34:08 + with message-id and subject line Bug#1014314: fixed in lvm2 2.03.15-2 has caused the Debian Bug report #1014314, regarding lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail to be marked as done. This means that you claim

Bug#1014351: hiredis: FTBFS test.c:151: send_hello: Assertion `reply != NULL && reply->type == expected' failed.

2022-07-04 Thread Andreas Beckmann
Source: hiredis Version: 1.0.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, hiredis/experimental recently started to FTBFS after some (transitive) build-dependency got updated. The package in sid is not affected. [...]

Processed: found 1011900 in 0.44-1

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1011900 0.44-1 Bug #1011900 [src:monkeysphere] monkeysphere: FTBFS: ...Could not chdir to home directory /home/user42: No such file or directory Marked as found in versions monkeysphere/0.44-1. > thanks Stopping processing here. Please

Bug#1013643: marked as done (deal.ii: FTBFS: src.c:(.text.startup+0x15): undefined reference to `pthread_create')

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 17:19:37 + with message-id and subject line Bug#1011655: fixed in deal.ii 9.4.0-1 has caused the Debian Bug report #1011655, regarding deal.ii: FTBFS: src.c:(.text.startup+0x15): undefined reference to `pthread_create' to be marked as done. This means

Bug#1011655: marked as done (deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 17:19:37 + with message-id and subject line Bug#1011655: fixed in deal.ii 9.4.0-1 has caused the Debian Bug report #1011655, regarding deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb to be marked as done. This means that you claim

Bug#1012126: marked as done (deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 17:19:37 + with message-id and subject line Bug#1011655: fixed in deal.ii 9.4.0-1 has caused the Debian Bug report #1011655, regarding deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental to be marked as done. This means that you claim that the problem

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-07-04 Thread Ben Hutchings
On Mon, 2022-07-04 at 14:04 +0200, Ansgar wrote: > On Sun, 19 Jun 2022 12:59:55 +0200 Ben Hutchings wrote: > > > I'm now looking at whether the missing bytes are recoverable (e.g. are > > > they always zeroes). > > [...] > > > > I wrote a script to try all possible byte values for 2 bytes before

Bug#1013700: Strangely rare pytest 7.x bug report

2022-07-04 Thread Carles Pina i Estany
Hi, I'm a lurker of debian-pyt...@lists.debian.org but seeing Python+Qt I wanted to have a look. I don't have a solution (I might look more another time if time permits) but I might have something that might help someone who knows the tools better. I am not familiar with Python Debian

Bug#1013660: marked as done (apertium-spa-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 15:04:56 + with message-id and subject line Bug#1013660: fixed in apertium-spa-ita 0.2.1-3 has caused the Debian Bug report #1013660, regarding apertium-spa-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met to be

Processed: severity of 1014323 is grave

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1014323 grave Bug #1014323 [wine-binfmt] wine-binfmt: postinst fails due to incorrect import directory Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1014323:

Bug#1014330: marked as done (highway: NEON and VFPv4 are not part of the armhf baseline)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 14:38:07 + with message-id and subject line Bug#1014330: fixed in highway 0.17.0-7 has caused the Debian Bug report #1014330, regarding highway: NEON and VFPv4 are not part of the armhf baseline to be marked as done. This means that you claim that the

Bug#1014314: Workaround

2022-07-04 Thread Damián Cinich
It seems that the package lvm2 renamed: - /lib/udev/rules.d/69-lvm-metad.rules To: - /lib/udev/rules.d/69-lvm.rules I needed to copy the file manually to workaround the issue: - cp -a /lib/udev/rules.d/69-lvm.rules /lib/udev/rules.d/69-lvm-metad.rules

Bug#1013419: marked as done (vcmi FTBFS with ffmpeg 5.0.1)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 13:34:43 + with message-id and subject line Bug#1013419: fixed in vcmi 0.99+dfsg+git20220621.54fab9f0-2 has caused the Debian Bug report #1013419, regarding vcmi FTBFS with ffmpeg 5.0.1 to be marked as done. This means that you claim that the problem has

Bug#1010856: marked as done (Please make libjxl-dev depend on all required libraries)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 13:34:19 + with message-id and subject line Bug#1010856: fixed in jpeg-xl 0.7.0~git20220704.de6a16a-1 has caused the Debian Bug report #1010856, regarding Please make libjxl-dev depend on all required libraries to be marked as done. This means that you

Bug#1014314: lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail

2022-07-04 Thread Anatoly Pugachev
Package: lvm2 Version: 2.03.15-1 Followup-For: Bug #1014314 Dear Maintainer, I have to remove offending lines from /usr/share/initramfs-tools/hooks/lvm2 file, so my "update-initramfs -u" to start working again. I don't have /etc/udev/rules.d/56-lvm.rules nor 69-lvm-metad.rules installed on my

Bug#1013652: marked as done (canl-java: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:testResources)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 13:19:06 + with message-id and subject line Bug#1013652: fixed in canl-java 2.7.0-4 has caused the Debian Bug report #1013652, regarding canl-java: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:testResources to be

Processed: lnav: FTBFS: 1 test fails due to quoting differences

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.9.0-2 Bug #1014335 [src:lnav] lnav: FTBFS: 1 test fails due to quoting differences Marked as found in versions lnav/0.9.0-2. -- 1014335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014335 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1014335: lnav: FTBFS: 1 test fails due to quoting differences

2022-07-04 Thread Andreas Beckmann
Source: lnav Version: 0.10.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: found -1 0.9.0-2 Hi, lnav in sid and experimental recently started to FTBFS, since some (transitive) build-depends seems to have changed the

Bug#1013700: Strangely rare pytest 7.x bug report

2022-07-04 Thread Julian Gilbey
Dear all, I wonder whether you might have any clue about https://bugs.debian.org/1013700 I have mostly worked out the "cause" of the bug, but I haven't quite got to the bottom of it. When running the command PYTHONPATH=. python3.10 -m pytest qtpy/tests in the directory

Processed: Re: Bug#1004769: digikam: FTBFS with ffmpeg 5.0

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1004769 [src:digikam] digikam: FTBFS with ffmpeg 5.0 Severity set to 'normal' from 'serious' -- 1004769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1004769: digikam: FTBFS with ffmpeg 5.0

2022-07-04 Thread Steven Robbins
control: severity -1 normal On Fri, 25 Feb 2022 22:55:12 +0100 Sebastian Ramacher wrote: > On 2022-02-21 16:05:37 -0600, Steven Robbins wrote: > > On Tue, 1 Feb 2022 21:01:39 +0100 Sebastian Ramacher > > wrote: > > > Source: digikam > > > Version: 4:7.1.0-2 > > > > I have just uploaded

Processed: your mail

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1014330 upstream Bug #1014330 [src:highway] highway: NEON and VFPv4 are not part of the armhf baseline Added tag(s) upstream. > forwarded 1014330 https://github.com/google/highway/issues/818 Bug #1014330 [src:highway] highway: NEON and

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-07-04 Thread Ansgar
On Sun, 19 Jun 2022 12:59:55 +0200 Ben Hutchings wrote: > > I'm now looking at whether the missing bytes are recoverable (e.g. are > > they always zeroes). > [...] > > I wrote a script to try all possible byte values for 2 bytes before or > after the short signature.  For this particular file,

Processed: closing 1011733

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1011733 3.4.0~a1-3 Bug #1011733 [src:androguard] androguard: FTBFS: AssertionError: The source 'androguard' and version '3.4.0~a1-3' do not appear to match any binary packages Marked as fixed in versions androguard/3.4.0~a1-3. Bug #1011733

Bug#1011733: closing 1011733

2022-07-04 Thread Jochen Sprickerhof
close 1011733 3.4.0~a1-3 thanks

Bug#1011713: marked as done (oscrypto: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did you mean: 'EVP_PKEY_free'?)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 11:19:12 + with message-id and subject line Bug#1011713: fixed in androguard 3.4.0~a1-3 has caused the Debian Bug report #1011713, regarding oscrypto: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did

Bug#1014330: highway: NEON and VFPv4 are not part of the armhf baseline

2022-07-04 Thread Adrian Bunk
Source: highway Version: 0.17.0-6 Severity: serious Tags: ftbfs X-Debbugs-Cc: Mathieu Malaterre NEON and VFPv4 are not part of the armhf baseline: https://wiki.debian.org/ArchitectureSpecificsMemo#armhf Plenty of hardware (inluding some of our buildds) do not support NEON. Plenty of hardware

Bug#1014329: anbox: Not working after removing ashmem module

2022-07-04 Thread Shengjing Zhu
Package: anbox Version: 0.0~git20211020-3 Severity: grave Justification: renders package unusable Forwarded: https://github.com/anbox/anbox/issues/2042 X-Debbugs-Cc: z...@debian.org ashmem_linux module has been removed from kernel 5.18.

Bug#1014115: uninstall does not properly remove enablement symlinks

2022-07-04 Thread Luca Boccassi
On Mon, 4 Jul 2022 at 11:55, Michael Biebl wrote: > > > Am 04.07.22 um 12:36 schrieb Luca Boccassi: > > I have uploaded i-s-h, should we close this one now? > > I've seen the upload. Thanks! > > I was debating with myself whether systemd-homed should get a tightened, > versioned Depends on i-s-h

Bug#1014115: uninstall does not properly remove enablement symlinks

2022-07-04 Thread Michael Biebl
Am 04.07.22 um 12:36 schrieb Luca Boccassi: I have uploaded i-s-h, should we close this one now? I've seen the upload. Thanks! I was debating with myself whether systemd-homed should get a tightened, versioned Depends on i-s-h to prevent this issue from happening. This would make a

Bug#1013931: marked as done (libtorrent-rasterbar2.0: Crash on exit)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 10:49:07 + with message-id and subject line Bug#1013931: fixed in libtorrent-rasterbar 2.0.6-4 has caused the Debian Bug report #1013931, regarding libtorrent-rasterbar2.0: Crash on exit to be marked as done. This means that you claim that the problem has

Bug#1014115: uninstall does not properly remove enablement symlinks

2022-07-04 Thread Luca Boccassi
On Sat, 2 Jul 2022 at 20:40, Michael Biebl wrote: > > Am 02.07.22 um 18:30 schrieb Luca Boccassi: > > On Fri, 1 Jul 2022 at 20:20, Michael Biebl wrote: > >> > >> > >> Am 30.06.22 um 22:31 schrieb Luca Boccassi: > >>> The problem is some files leftover, no? Just delete them in the > >>> postinst

Bug#1011713: marked as done (oscrypto: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did you mean: 'EVP_PKEY_free'?)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 10:19:58 + with message-id and subject line Bug#1011713: fixed in oscrypto 1.3.0-1 has caused the Debian Bug report #1011713, regarding oscrypto: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did you

Bug#1013529: marked as done (vulkan-validationlayers: FTBFS: vk_typemap_helper.h:3142:31: error: ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did you mean ‘VkVideoEncodeH264

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 10:06:21 + with message-id and subject line Bug#1013529: fixed in vulkan-validationlayers 1.3.216.0-1 has caused the Debian Bug report #1013529, regarding vulkan-validationlayers: FTBFS: vk_typemap_helper.h:3142:31: error:

Bug#1013575: marked as done (vulkan-tools: FTBFS: vk_typemap_helper.h:3141:31: error: ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did you mean ‘VkVideoEncodeH264VclFrameInf

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 10:06:13 + with message-id and subject line Bug#1013575: fixed in vulkan-tools 1.3.216.0+dfsg1-1 has caused the Debian Bug report #1013575, regarding vulkan-tools: FTBFS: vk_typemap_helper.h:3141:31: error: ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not

Bug#1012505: marked as done (debmutate: missing runtime python3-pcre dependency?)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 4 Jul 2022 10:00:06 + with message-id and subject line Please see #1013485 for field roundtripping issue has caused the Debian Bug report #1012505, regarding debmutate: missing runtime python3-pcre dependency? to be marked as done. This means that you claim that the

Processed: reassign 1013485 to python3-debian

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1013485 python3-debian Bug #1013485 [src:lintian-brush] lintian-brush: FTBFS: AssertionError: 1 != 0 Bug reassigned from package 'src:lintian-brush' to 'python3-debian'. No longer marked as found in versions lintian-brush/0.126. Ignoring

Processed: affects 1013485

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1013485 lintian-brush python3-debmutate python3-debian Bug #1013485 [src:lintian-brush] lintian-brush: FTBFS: AssertionError: 1 != 0 Added indication that 1013485 affects lintian-brush, python3-debmutate, and python3-debian > thanks

Processed: Bug#1014214 marked as pending in nodejs

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1014214 [nodejs] missing undici.fetch() Added tag(s) pending. -- 1014214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1014214: marked as pending in nodejs

2022-07-04 Thread Jérémy Lal
Control: tag -1 pending Hello, Bug #1014214 in nodejs 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#1013607: marked as done (binutils-m68hc1x: FTBFS: tar: /usr/src/binutils/binutils-2.38.50.20220622.tar.xz: Cannot open: No such file or directory)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 09:20:42 + with message-id and subject line Bug#1013607: fixed in binutils-m68hc1x 1:3.0.2 has caused the Debian Bug report #1013607, regarding binutils-m68hc1x: FTBFS: tar: /usr/src/binutils/binutils-2.38.50.20220622.tar.xz: Cannot open: No such file or

Bug#1013771: closing 1013771

2022-07-04 Thread Ilias Tsitsimpis
close 1013771 0.3.1-1 thanks

Bug#1013650: marked as done (apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp installed.)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 08:48:58 + with message-id and subject line Bug#1013650: fixed in apertium-urd-hin 0.1.0~r64379-4 has caused the Debian Bug report #1013650, regarding apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp installed. to be marked as done. This

Bug#1011916: marked as done (poolcounter: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 08:41:25 + with message-id and subject line Bug#1011916: fixed in poolcounter 1.1.3-2 has caused the Debian Bug report #1011916, regarding poolcounter: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that

Processed: closing 1013771

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1013771 0.3.1-1 Bug #1013771 [src:haskell-statestack] haskell-statestack FTBFS: Encountered missing or private dependencies: base >=4.8 && <4.14 Marked as fixed in versions haskell-statestack/0.3.1-1. Bug #1013771 [src:haskell-statestack]

Bug#1013645: marked as done (apertium-spa-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 08:35:02 + with message-id and subject line Bug#1013645: fixed in apertium-spa-cat 2.2.0-3 has caused the Debian Bug report #1013645, regarding apertium-spa-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met to be

Bug#1014180: marked as done (src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 07:49:12 + with message-id and subject line Bug#1014180: fixed in boost1.74 1.74.0-16.1 has caused the Debian Bug report #1014180, regarding src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+ to be marked as done. This means that

Bug#1014180: marked as done (src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 07:49:12 + with message-id and subject line Bug#1013530: fixed in boost1.74 1.74.0-16.1 has caused the Debian Bug report #1013530, regarding src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+ to be marked as done. This means that

Bug#1014180: marked as done (src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 07:49:12 + with message-id and subject line Bug#1013472: fixed in boost1.74 1.74.0-16.1 has caused the Debian Bug report #1013472, regarding src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+ to be marked as done. This means that

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

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 07:48:58 + with message-id and subject line Bug#1013362: fixed in alt-ergo 2.4.1-4 has caused the Debian Bug report #1013362, regarding src:alt-ergo: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel to be marked as done. This

Bug#1014180: src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+

2022-07-04 Thread Gianfranco Costamagna
Hello, since this bug is really impacting lots of packages, I'm NMUing right now. I spent lots of time trying to understand why cpprest and websocketpp were failing testsuite after printing "test OK", digged into openssl code, and after a while I got the issue on boost side. Better avoid

Bug#1009458: marked as done (vitables: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 07:35:08 + with message-id and subject line Bug#1009458: fixed in vitables 3.0.2-3 has caused the Debian Bug report #1009458, regarding vitables: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 to

Processed: Bug#1013362 marked as pending in alt-ergo

2022-07-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1013362 [src:alt-ergo] src:alt-ergo: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel Added tag(s) pending. -- 1013362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013362 Debian Bug Tracking System Contact

Bug#1013362: marked as pending in alt-ergo

2022-07-04 Thread Julien Puydt
Control: tag -1 pending Hello, Bug #1013362 in alt-ergo 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:

Processed: fixed 1014249 in 4.8.0-4, closing 1014249

2022-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1014249 4.8.0-4 Bug #1014249 {Done: Jonas Smedegaard } [src:node-terser] node-terser: autopkgtest regression Marked as fixed in versions node-terser/4.8.0-4. > close 1014249 Bug #1014249 {Done: Jonas Smedegaard } [src:node-terser]

Bug#1013715: marked as done (photutils: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 06:34:49 + with message-id and subject line Bug#1013715: fixed in photutils 1.4.0-4 has caused the Debian Bug report #1013715, regarding photutils: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone to be marked as done. This means

Bug#1013665: marked as done (apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)

2022-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2022 06:34:08 + with message-id and subject line Bug#1013665: fixed in apertium-spa-arg 0.5.0-2 has caused the Debian Bug report #1013665, regarding apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met to be

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

2022-07-04 Thread Christian Marillat
On 04 juil. 2022 08:22, Christian Marillat wrote: > On 27 juin 2022 18:47, Hilko Bengen wrote: > >> (It might be a good idea to add a Built-Using line to debian/control.) > > Built-Using doesn't work with virtual package. Well, virtual isn't the right word, but libboost-dev is an empty package

Bug#1013812: (no subject)

2022-07-04 Thread Jean Baptiste Favre
Control: fixed 1013812 9.1.2+ds-13 OpenPGP_signature Description: OpenPGP digital signature

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

2022-07-04 Thread Christian Marillat
On 27 juin 2022 18:47, Hilko Bengen wrote: > (It might be a good idea to add a Built-Using line to debian/control.) Built-Using doesn't work with virtual package. Christian