Bug#1006702:

2022-03-05 Thread Daniel Black
They won't crash, because the CPU features are tested before any call to the optimized code is made. https://github.com/MariaDB/server/blob/10.6/mysys/crc32/crc32c.cc#L542-L564 As the Debian CI undoubtedly runs the basic unit tests that cover crc32 on the minimum hardware, and succeeds, it proves

Bug#984357: marked as done (synfigstudio: ftbfs with GCC-11)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sun, 06 Mar 2022 06:04:00 + with message-id and subject line Bug#984053: fixed in etl 1.4.0-2 has caused the Debian Bug report #984053, regarding synfigstudio: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#984355: marked as done (synfig: ftbfs with GCC-11)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sun, 06 Mar 2022 06:04:00 + with message-id and subject line Bug#984053: fixed in etl 1.4.0-2 has caused the Debian Bug report #984053, regarding synfig: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#984053: marked as done (etl: ftbfs with GCC-11)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sun, 06 Mar 2022 06:04:00 + with message-id and subject line Bug#984053: fixed in etl 1.4.0-2 has caused the Debian Bug report #984053, regarding etl: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: Bug#984053 marked as pending in etl

2022-03-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #984053 [src:etl] etl: ftbfs with GCC-11 Bug #984355 [src:etl] synfig: ftbfs with GCC-11 Bug #984357 [src:etl] synfigstudio: ftbfs with GCC-11 Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. -- 984053: https://bugs.debian.org/cg

Bug#984053: marked as pending in etl

2022-03-05 Thread Stuart Prescott
Control: tag -1 pending Hello, Bug #984053 in etl 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/etl/-/commit/0ac78f830d9f19d89f597a9903e4a93d1

Bug#1000229: binary package is missing /usr/sbin/memlockd

2022-03-05 Thread Paul Wise
Control: tags -1 + patch pending On Fri, 19 Nov 2021 23:02:53 +0100 Sven Hartge wrote: > The subject says it all: The package is missing the binary: This is caused by the install target in debian/rules doing things manually instead of leaving everything to dh_* scripts and configuration files fo

Processed: Re: binary package is missing /usr/sbin/memlockd

2022-03-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch pending Bug #1000229 [memlockd] binary package is missing /usr/sbin/memlockd Added tag(s) patch and pending. -- 1000229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966647: marked as done (libetpan: CVE-2020-15953)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 22:47:31 + with message-id and subject line Bug#966647: fixed in libetpan 1.9.3-2+deb10u1 has caused the Debian Bug report #966647, regarding libetpan: CVE-2020-15953 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1006537: dask: autopkgtest failure on 32 bit, mismatch in size of data structure.

2022-03-05 Thread Diane Trout
Hi, I had some time to work on this and worked around the test case that was failing, since it was failing because it was assuming it was running in a 64-bit environment. I submitted my comments to upstream here https://github.com/dask/dask/issues/8169#issuecomment-1059839906 I tested in a 32-bi

Bug#1006820: src:cryfs: fails to migrate to testing for too long: FTBFS on armel and armhf

2022-03-05 Thread Paul Gevers
Source: cryfs Version: 0.10.2-5 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 Criti

Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)

2022-03-05 Thread Paul Gevers
Hi Lev, On 04-03-2022 11:42, dogs...@riseup.net wrote: Do you confirm that this ABI change doesn't effect the other reverse build dependencies of src:swi-prolog? If that's the case I'm fine with removing the block. But I'm afraid (without checking from my side) that the other package don't have

Bug#1000618: ruby-gtk2: crashes with openssl: superclass mismatch for class Socket (TypeError)

2022-03-05 Thread Peter Michael Green
I noticed this bug while working on a derivative and decided to take a look. Note though that I am NOT a ruby guy. Upstream hasn't fixed the underlying issue, but has suggested it can be worked around by reordering requires/imports and has closed the bug. I took upstreams suggestion and turned

Bug#1006818: eye: (autopkgtest) failure on non-amd64

2022-03-05 Thread Paul Gevers
Source: eye Version: 19.0221.2026~ds-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You package has an autopkgtest, great. However, it fails on all architectures but amd64. Can you please investigate the situation and fix it? I copied some of

Bug#1006816: python-anyio: FTBFS in Ubuntu and local pbuilder (ipv6?)

2022-03-05 Thread Gianfranco Costamagna
Source: python-anyio Version: 3.5.0-2 Severity: serious Hello, in Ubuntu (where internet is really disabled your package FTBFS. Looks like some ipv6 translation is not really working, but what worries me more is: tests/test_sockets.py:1144: in test_getaddrinfo correct = await getaddrinfo('f

Bug#1006815: xmoto: autopkgtest often fails: Failed to connect to X-Moto: Connection refused

2022-03-05 Thread Simon McVittie
Source: xmoto Version: 0.6.1+repack-7 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky The superficial autopkgtest for xmoto seems to be failing intermittently, especially on ppc64el (for whatever reason), which is likely to block other p

Bug#994451: marked as done (golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 18:02:10 + with message-id and subject line Bug#994451: fixed in golang-github-opencontainers-specs 1.0.2.41.g7413a7f-1+deb11u1 has caused the Debian Bug report #994451, regarding golang-github-containers-common: secomp.json does not include newer syscall

Bug#994451: marked as done (golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 18:02:10 + with message-id and subject line Bug#994451: fixed in golang-github-containers-common 0.33.4+ds1-1+deb11u1 has caused the Debian Bug report #994451, regarding golang-github-containers-common: secomp.json does not include newer syscall used by st

Bug#1006812: kodi: Kodi Fails to Start

2022-03-05 Thread Vasyl Gello
Hi Stephen, 19.4 is out and I am preparing the release. This might take some time because I left all my infrastructure in Kharkiv, Ukraine and relevant Debian RT ticket is not yet processed. Once I get access to the beefy build machine I will upload everything. --  Vasyl Gello

Processed: Re: Bug#1006812: kodi: Kodi Fails to Start

2022-03-05 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:waylandpp 0.2.9-1 Bug #1006812 [kodi] kodi: Kodi Fails to Start Bug reassigned from package 'kodi' to 'src:waylandpp'. No longer marked as found in versions kodi/2:19.3+dfsg1-1. Ignoring request to alter fixed versions of bug #1006812 to the same valu

Bug#1006812: kodi: Kodi Fails to Start

2022-03-05 Thread Sebastian Ramacher
Control: reassign -1 src:waylandpp 0.2.9-1 Control: affects -1 kodi On 2022-03-05 11:50:48 -0500, SDA wrote: > Package: kodi > Version: 2:19.3+dfsg1-1+b1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: marathon.duran...@gmail.com > > Dear Maintainer, > > Since system

Bug#1006667: marked as done (python-biopython - build-dependencies unsatisfiable on most architectures.)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 16:52:53 + with message-id and subject line Bug#1006667: fixed in python-biopython 1.79+dfsg-3 has caused the Debian Bug report #1006667, regarding python-biopython - build-dependencies unsatisfiable on most architectures. to be marked as done. This means

Bug#1006812: kodi: Kodi Fails to Start

2022-03-05 Thread SDA
Package: kodi Version: 2:19.3+dfsg1-1+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: marathon.duran...@gmail.com Dear Maintainer, Since system update on Thursday or Friday. Starting from the command line throughs this output: failed to open zone.tab /usr/lib/x86_64-lin

Bug#1006081: marked as done (fonts-arapey: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 16:01:20 +0100 with message-id <83fa7e62ee5218107c3995016adb0...@phys.ethz.ch> and subject line the bug is not valid anymore has caused the Debian Bug report #1006081, regarding fonts-arapey: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0'

Bug#991040: marked as done (varnish: CVE-2021-36740: VSV00007)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 13:47:23 + with message-id and subject line Bug#991040: fixed in varnish 6.1.1-1+deb10u2 has caused the Debian Bug report #991040, regarding varnish: CVE-2021-36740: VSV7 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1004433: marked as done (CVE-2022-23959: VSV00008 Varnish HTTP/1 Request Smuggling Vulnerability)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 13:47:27 + with message-id and subject line Bug#1004433: fixed in varnish 6.1.1-1+deb10u3 has caused the Debian Bug report #1004433, regarding CVE-2022-23959: VSV8 Varnish HTTP/1 Request Smuggling Vulnerability to be marked as done. This means that you

Bug#1004433: marked as done (CVE-2022-23959: VSV00008 Varnish HTTP/1 Request Smuggling Vulnerability)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 13:17:12 + with message-id and subject line Bug#1004433: fixed in varnish 6.5.1-1+deb11u2 has caused the Debian Bug report #1004433, regarding CVE-2022-23959: VSV8 Varnish HTTP/1 Request Smuggling Vulnerability to be marked as done. This means that you

Bug#991040: marked as done (varnish: CVE-2021-36740: VSV00007)

2022-03-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Mar 2022 13:17:08 + with message-id and subject line Bug#991040: fixed in varnish 6.5.1-1+deb11u1 has caused the Debian Bug report #991040, regarding varnish: CVE-2021-36740: VSV7 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1006017: playitslowly doesn't start (hasn't for awhile)

2022-03-05 Thread Andreas Beckmann
On 04/03/2022 13.15, Tiago Bortoletto Vaz wrote: This package has indeed been broken for a long time already. Upstream is inactive since 2015 and I'm not willing to do all the fixes it would need. Therefore I requested its removal from Debian archive. Then we should probably get it removed from

Processed: tagging 1006763

2022-03-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1006763 + sid bookworm Bug #1006763 [python-reportlab] python-reportlab: fails to build with python3.10 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006763: https://bugs.deb