Bug#1031462: marked as pending in libmemcached-libmemcached-perl

2023-02-17 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #1031462 in libmemcached-libmemcached-perl 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#1031462 marked as pending in libmemcached-libmemcached-perl

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1031462 [src:libmemcached-libmemcached-perl] libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 1031462:

Bug#1031431: marked as done (debian-installer-netboot-images: FTBFS: Building 20220917, but bookworm has 20230207, failing the build)

2023-02-17 Thread Debian Bug Tracking System
ing the build > Version not found in bookworm, no fallback defined > make[1]: *** [debian/rules:20: get-images-amd64] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/16/debian-installer-netboot-images_20220917+rebuild1_unstable.log All bugs filed during th

Bug#1031388: icingaweb2-module-pdfexport: server software depending on chromium?

2023-02-17 Thread Shengjing Zhu
On Thu, 16 Feb 2023 12:45:20 +0100 David Kunz wrote: > > > The current version of icingaweb2-module-pdfexport depends on chromium. > All versions are like thes. > > > icingaweb2 is a web service. Depending on a graphical browser in a web > > server component is not at all reasonable. > I know,

Bug#1031445: [Pkg-electronics-devel] Bug#1031445: camv-rnd: FTBFS: build-dependency not installable: librnd4-dev (>= 3.2.0)

2023-02-17 Thread Bdale Garbee
Lucas Nussbaum writes: > Source: camv-rnd > Version: 1.1.1-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230216 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64.

Bug#1031442: gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2

2023-02-17 Thread Yavor Doganov
Lucas Nussbaum wrote: > Source: gnustep-base > Version: 1.28.1+really1.28.0-5 > Severity: serious > Justification: FTBFS > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for the report; I believe this is due to tzdata #1031395. I cannot reproduce with

Bug#1031195: marked as done (os-autoinst: FTBFS on several release architectures)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 13:19:17 + with message-id and subject line Bug#1031195: fixed in os-autoinst 4.6.1674476646.0798a03c-2 has caused the Debian Bug report #1031195, regarding os-autoinst: FTBFS on several release architectures to be marked as done. This means that you claim

Bug#1031293: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031293 Control: affects -1 + src:python-zstandard

Processed: Re: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:python-zstandard Bug #1031293 [python3-zstandard] python3-zstandard 0.19.0-3 supports only libzstd 1.5.2 Added indication that 1031293 affects src:python-zstandard -- 1031293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031293 Debian Bug

Processed: Re: dm-writeboost-dkms: module fails to build for Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 fixed-upstream pending Bug #1029261 [dm-writeboost-dkms] dm-writeboost-dkms: module fails to build for Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’ Added tag(s) fixed-upstream and pending. > tag 1027870 pending Bug #1027870

Bug#1029261: dm-writeboost-dkms: module fails to build for Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’

2023-02-17 Thread Andreas Beckmann
Control: tag -1 fixed-upstream pending Control: tag 1027870 pending On Fri, 20 Jan 2023 13:37:01 +0100 Andreas Beckmann wrote: /var/lib/dkms/dm-writeboost/2.2.15/build/dm-writeboost.h:506:46: error: ‘struct dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’? This is fixed in

Bug#1030941: marked as done (librsb: build-depends unsatisfiable on armhf)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 09:49:56 + with message-id and subject line Bug#1030941: fixed in librsb 1.3.0.2+dfsg-2 has caused the Debian Bug report #1030941, regarding librsb: build-depends unsatisfiable on armhf to be marked as done. This means that you claim that the problem has

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:libzstd src:python-scrapy src:rpmlint Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504

Bug#1031449: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502 hardcoded in zstd

2023-02-17 Thread James Addison
Source: python-scrapy Followup-For: Bug #1031449 Control: package -1 python3-zstandard 0.19.0-3 Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint Control: merge -1 1031293

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031443 Control: affects -1 = src:python-scrapy src:libzstd src:rpmlint src:python-zstandard Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 = src:python-scrapy src:libzstd src:rpmlint src:python-zstandard Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned

Processed: Bug#1031396 marked as pending in pipewire

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1031396 [pipewire] Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade` Added tag(s) pending. -- 1031396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1031396: marked as pending in pipewire

2023-02-17 Thread Dylan Aïssi
Control: tag -1 pending Hello, Bug #1031396 in pipewire 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#1031394: Please re-enable RTTI support in Sid/Bookworm, needed by at least Ceph

2023-02-17 Thread Thomas Goirand
Hi Laszlo! On 2/16/23 20:25, László Böszörményi (GCS) wrote: Control: tags -1 +moreinfo Dear Thomas, On Thu, Feb 16, 2023 at 1:51 PM Thomas Goirand wrote: During my tests with Ceph, I noticed a grave regression: Ceph OSD (the process that does the actual storage for Ceph) cannot use Snappy

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031443 Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint Control: merge -1 1031293

Processed (with 1 error): Re: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-zstandard 0.19.0-3 Bug #1031449 [src:python-scrapy] python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502 hardcoded in zstd

Bug#1031449: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502 hardcoded in zstd

2023-02-17 Thread James Addison
Source: python-scrapy Followup-For: Bug #1031449 Control: reassign -1 python3-zstandard 0.19.0-3 Control: affects -1 + src:libzstd src:python-scrapy src:python-zstandard src:rpmlint Control: merge -1 1031293

Bug#979090: Legally problematic GPL-3+ readline dependency

2023-02-17 Thread Gregor Riepl
Is anybody already working on this? I will attempt to fix d/copyright and submit a patch or MR for review otherwise.

Bug#1031462: marked as done (libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 11:34:16 + with message-id and subject line Bug#1031462: fixed in libmemcached-libmemcached-perl 1.001801+dfsg-4 has caused the Debian Bug report #1031462, regarding libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1

Bug#1031431: debian-installer-netboot-images: FTBFS: Building 20220917, but bookworm has 20230207, failing the build

2023-02-17 Thread Cyril Brulebois
Lucas Nussbaum (2023-02-17): > OK, I remembered about skipping debian-installer, but wasn't sure about > debian-installer-netboot-images Thanks and sorry for being a pain, I know we're the usual ugly duckling in the project… Cheers, -- Cyril Brulebois (k...@debian.org)

Bug#1031396: Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`

2023-02-17 Thread Dylan Aïssi
Hi, This seems to be solved by adding pulseaudio-module-bluetooth in Conflicts and Replaces of pipewire-audio. pipewire-audio already conflicts and replaces pulseaudio for some reasons, but looks like it is not enough. Best regards, Dylan

Bug#1031396: Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`

2023-02-17 Thread Simon McVittie
Control: reassign -1 pipewire Control: affects -1 = gnome src:meta-gnome3 On Fri, 17 Feb 2023 at 13:25:47 +0100, Dylan Aïssi wrote: > This seems to be solved by adding pulseaudio-module-bluetooth in Conflicts and > Replaces of pipewire-audio. pipewire-audio already conflicts and replaces >

Processed: Re: Bug#1031396: Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 pipewire Bug #1031396 [gnome] Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade` Bug reassigned from package 'gnome' to 'pipewire'. No longer marked as found in versions meta-gnome3/1:43+1. Ignoring request to alter fixed versions of bug

Bug#1031449: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502 hardcoded in zstd

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031449 Control: affects -1 - src:rpmlint src:python-zstandard src:python-scrapy Control: affects -1 + src:rpmlint src:python-scrapy src:python-zstandard Control: merge -1 1031293

Processed (with 1 error): Re: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 - src:rpmlint src:python-zstandard src:python-scrapy Bug #1031449 [python3-zstandard] python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib,

Bug#1031477: marked as done (python-oslo.concurrency: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpxztykbsm/tmpyb1wyys0/file-0')

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 10:07:55 +0100 with message-id <2fe674d6-4b4a-d7f7-7b86-51538d2f1...@debian.org> and subject line Could not reproduce has caused the Debian Bug report #1031477, regarding python-oslo.concurrency: FTBFS: FileNotFoundError: [Errno 2] No such file or directory:

Processed: tagging 1001537, tagging 1027680, tagging 1031394, tagging 1031379 ..., tagging 1031346 ...

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1001537 - sid bookworm Bug #1001537 {Done: Yavor Doganov } [libgnustep-gui0.29] Cleanup in NSPopUpButtonCell -dealloc crashes gtamsanalyzer.app Removed tag(s) sid and bookworm. > tags 1027680 - sid bookworm Bug #1027680 {Done: Simon

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

2023-02-17 Thread James Addison
Source: python-zstandard Followup-For: Bug #1031443 Control: reassign -1 python3-zstandard 0.19.0-3 Control: affects -1 + src:python-zstandard Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-zstandard 0.19.0-3 Bug #1031443 [src:python-zstandard] python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in

Bug#1031293: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031293 Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint

Processed: Re: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:libzstd src:python-scrapy src:rpmlint Bug #1031293 [python3-zstandard] python3-zstandard 0.19.0-3 supports only libzstd 1.5.2 Added indication that 1031293 affects src:python-scrapy -- 1031293:

Bug#1031433: diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-17 Thread FC Stegerman
Should be fixed by [1] - FC [1] https://salsa.debian.org/reproducible-builds/diffoscope/-/merge_requests/126

Processed: Re: NVIDIA 340.108 driver gives Segmentation fault at launch all Qt software

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > merge -1 1031489 Bug #1031488 [qt] NVIDIA 340.108 driver gives Segmentation fault at launch all Qt software Warning: Unknown package 'qt' Bug #1031489 [qt] NVIDIA 340.108 driver gives Segmentation fault at launch all Qt software Merged 1031488 1031489 Warning:

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031443 Control: affects -1 - src:python-scrapy src:rpmlint Control: affects -1 + src:python-scrapy src:rpmlint Control: merge -1 1031293

Processed (with 1 error): Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 105

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 - src:python-scrapy src:rpmlint Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in

Bug#1031522: yt-dlp: Unable to extract uploader id

2023-02-17 Thread Peter Wienemann
Package: yt-dlp Version: 2023.01.06-1 Severity: grave Tags: fixed-upstream Justification: renders package unusable Dear Maintainer, it seems that version 2023.01.06-1 of yt-dlp suffers from the issue described in: https://github.com/yt-dlp/yt-dlp/issues/6247 Upstream has provided a fix for

Bug#1031396: marked as done (Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 15:56:00 + with message-id and subject line Bug#1031396: fixed in pipewire 0.3.65-3 has caused the Debian Bug report #1031396, regarding Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade` to be marked as done. This means that you claim that the

Processed (with 1 error): merging 1031509 1031513

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1031509 1031513 Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), CVE-2023-20032/CVE-2023-20052 Unable to merge bugs because: severity of #1031513 is 'grave' not 'important' Failed to merge 1031509: Did not alter merged

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

2023-02-17 Thread Russ Allbery
Adrian Bunk writes: > The image creators could just set the features they enable to what they > copied from /etc/mke2fs.conf from the target distribution, a label with > a timestamp wouldn'tbring much benefit here. That's a very good point and I'm embarrassed it wasn't immediately obvious to

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

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 17:19:48 + with message-id and subject line Bug#1031433: fixed in diffoscope 236 has caused the Debian Bug report #1031433, regarding diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to

Bug#1031512: docbook-defguide: non-free GFDL-licensed files

2023-02-17 Thread Bastian Germann
Source: docbook-defguide Severity: serious Version: 2.0.17+svn9912-2 Some files in the package are licensed under the non-free variant of the GFDL with explicit Invariant Section. Please repack to remove them.

Bug#1030464: aiomysql: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 'unknown'

2023-02-17 Thread s3v
Dear Maintainer, After adding python3-setuptools-scm to build depends, I was able to build your package in a sid chroot environment. Please note that the build creates a "aiomysql/_scm_version.py" file which prevents the next build: ... dpkg-source: info: using options from

Processed: tagging 982123

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 982123 + buster Bug #982123 [src:librsvg] librsvg: FTBFS on ppc64el in buster Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 982123:

Bug#1030967: marked as done (vip-manager2: autopkgtest failure)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 14:38:35 + with message-id and subject line Bug#1030967: fixed in vip-manager2 2.1.0-4 has caused the Debian Bug report #1030967, regarding vip-manager2: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 1022015

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1022015 + patch Bug #1022015 [src:elasticsearch-curator] elasticsearch-curator: Uses deprecated yaml.load Bug #1026566 [src:elasticsearch-curator] elasticsearch-curator: FTBFS: TypeError: load() missing 1 required positional argument:

Processed: Re: Bug#1031455: charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror]

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:fuse3 Bug #1031455 [src:charliecloud] charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror] Bug reassigned from package 'src:charliecloud' to 'src:fuse3'. No longer marked as found in versions charliecloud/0.31-1. Ignoring

Bug#1031455: charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror]

2023-02-17 Thread Peter Wienemann
Control: reassign -1 src:fuse3 Control: found -1 3.13.1-1 Control: forwarded -1 https://github.com/libfuse/libfuse/issues/729 Control: tags -1 + fixed-upstream Control: affects -1 src:charliecloud Dear Lucas, thanks for reporting this problem. It seems that the root cause of this FTBFS issue

Bug#1028840: marked as done (weather-util: FTBFS: ValueError: invalid mode: 'rUb')

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 18:08:08 + with message-id and subject line Bug#1028840: fixed in weather-util 2.4.4-1 has caused the Debian Bug report #1028840, regarding weather-util: FTBFS: ValueError: invalid mode: 'rUb' to be marked as done. This means that you claim that the

Bug#1031513: clamav: new upstream security release, CVE-2023-20032

2023-02-17 Thread Joost van Baal-Ilić
Package: clamav Severity: grave Hi, As you'll likely know there is https://security-tracker.debian.org/tracker/CVE-2023-20032 and https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html "CVE-2023-20032: Fixed a possible remote code execution vulnerability in the HFS+ file parser.

Bug#1030174: marked as done (iminuit FTBFS with scipy 1.10)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 16:57:47 + with message-id and subject line Bug#1030174: fixed in iminuit 2.11.2-4 has caused the Debian Bug report #1030174, regarding iminuit FTBFS with scipy 1.10 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: RC Bug #1031460: forward to upstream fix

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1031460 > https://github.com/Rockhopper-Technologies/enlighten/commit/1ede6ff4 Bug #1031460 [src:enlighten] enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

2023-02-17 Thread James Addison
Package: python3-zstandard Followup-For: Bug #1031443 Control: forcemerge -1 1031293 1031449

Processed: Re: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > forcemerge -1 1031293 1031449 Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in zstd headers,

Bug#1031379: kaffeine: does not work

2023-02-17 Thread Marco Mattiolo
Hi, I am not the package maintainer, but this bug report is almost useless. What's the issue? Is kaffeine not starting? Is it crashing? Or is just not showing what you expect? Which kind of DVB device are you using? Have you checked the device to work with other apps? Before flagging this

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

2023-02-17 Thread Theodore Ts'o
On Fri, Feb 17, 2023 at 08:51:33AM -0800, Russ Allbery wrote: > Adrian Bunk writes: > > > The image creators could just set the features they enable to what they > > copied from /etc/mke2fs.conf from the target distribution, a label with > > a timestamp wouldn'tbring much benefit here. > >

Processed: Re: [Pkg-clamav-devel] Processed (with 1 error): merging 1031509 1031513

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1031509 1031513 Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), CVE-2023-20032/CVE-2023-20052 Bug #1031513 [clamav] clamav: new upstream security release, CVE-2023-20032 Severity set to 'important' from 'grave'

Bug#1031435: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-17 Thread Lucas Nussbaum
Hi, On 17/02/23 at 20:17 +0100, Timo Röhling wrote: > Control: tags -1 + moreinfo > > Hi Lucas, > > this seems to be bug #1030493 again. > > On Fri, 17 Feb 2023 07:50:37 +0100 Lucas Nussbaum wrote: > > > E - '')] > > > E ? ^ > > > E > E + ''),

Bug#1031533: simka B-D on libgatbcore-dev which doesn't exist on s390x

2023-02-17 Thread Sergio Durigan Junior
Source: simka Version: 1.5.3-6 Severity: serious Hi, simka build-depends on libgatbcore-dev, but gatb-core has been recently patched and stopped building on several architectures, including s390x. simka's build will FTBFS on those architectures. Thank you, -- Sergio GPG key ID: 237A 54B1 0287

Bug#1031534: marked as done (firmware-linux-nonfree: Package removed from sid and bookworm)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 23:02:40 +0100 with message-id and subject line Re: Bug#1031534: firmware-linux-nonfree: Package removed from sid and bookworm has caused the Debian Bug report #1031534, regarding firmware-linux-nonfree: Package removed from sid and bookworm to be marked as

Processed: severity of 1031457 is important, tagging 1031457

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1031457 important Bug #1031457 [src:ruby-redis] ruby-redis: FTBFS: ERROR: Test "ruby3.1" failed. Severity set to 'important' from 'serious' > # builds just fine > tags 1031457 + moreinfo unreproducible Bug #1031457 [src:ruby-redis]

Bug#1031435: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-17 Thread Timo Röhling
Control: tags -1 + moreinfo Hi Lucas, this seems to be bug #1030493 again. On Fri, 17 Feb 2023 07:50:37 +0100 Lucas Nussbaum wrote: > E - '')] > E ? ^ > E > E + ''), > E ? ^ > E > E +

Processed: Re: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1031435 [src:python-inotify] python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Added tag(s) moreinfo. -- 1031435:

Processed: Re: Bug#1029260: vice: missing font license in d/copyright

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > found -1 2.1.dfsg-1 Bug #1029260 [src:vice] vice: missing font license in d/copyright Marked as found in versions vice/2.1.dfsg-1. > severity -1 important Bug #1029260 [src:vice] vice: missing font license in d/copyright Severity set to 'important' from 'serious'

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

2023-02-17 Thread Theodore Ts'o
On Fri, Feb 17, 2023 at 12:43:01PM -0700, Sam Hartman wrote: > > I am not entirely convinced that using current rather than guest > tools for image building is an anti-pattern. You've been working on > filesystems for a long time; I've been working on various image > building projects since my

Processed: growing image fails to boot: /scripts/local-bottom/growroot: line 97: wait-for-root: not found

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1027050 serious Bug #1027050 [cloud-initramfs-growroot] growing image fails to boot: /scripts/local-bottom/growroot: line 97: wait-for-root: not found Severity set to 'serious' from 'important' > tags 1027050 + patch Bug #1027050

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

2023-02-17 Thread Santiago Vila
severity 1014662 important thanks Note: I'm restoring the original severity because Martin Pitt says in #1027050 that the fatal failure is due to wait-for-root, not flock. (However, I could not imagine an upload fixing #1027050 which would not fix this one in the same upload as well). Thanks.

Processed: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1014662 important Bug #1014662 [cloud-initramfs-growroot] cloud-initramfs-growroot: Initramfs hook does not include `flock` command Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you

Processed: bug 1031309 is forwarded to https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/121

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1031309 > https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/121 Bug #1031309 [accountsservice] accountsservice: accounts-daemon service will prevent system boot if shadowconfig is off Set Bug

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

2023-02-17 Thread Santiago Vila
After applying the suggested patch, the reported error does not show anymore. Instead, I get this: /scripts/local-bottom/growroot: line 97: wait-for-root: not found Where does this "wait-for-root" come from? I can't find it in any package. Thanks.

Bug#972146: /usr/share/applications/mono-runtime-common.desktop: should not handle MIME type by executing arbitrary code

2023-02-17 Thread Salvatore Bonaccorso
Hi Gabriel, On Thu, Feb 16, 2023 at 11:37:57PM +0100, Gabriel Corona wrote: > Hi, > > Thanks for the patch! Thanks for staying on top of the issue! > > This has been fixed in Debian testing and sid. However, stable is still > affected. I believe it would make sense to port the patch to stable

Bug#1031531: mindthegap B-D on libgatbcore-dev which doesn't exist on several architectures

2023-02-17 Thread Sergio Durigan Junior
Source: mindthegap Version: 2.3.0-1 Severity: serious Hi, mindthegap build-depends on libgatbcore-dev, but gatb-core has been recently patched and stopped building on several architectures, including e.g. s390x, armhf, etc. bcalm's build will FTBFS on those architectures. Thank you, --

Bug#1031532: minia B-D on libgatbcore-dev which doesn't exist on several architectures

2023-02-17 Thread Sergio Durigan Junior
Source: minia Version: 3.2.6-2 Severity: serious Hi, minia build-depends on libgatbcore-dev, but gatb-core has been recently patched and stopped building on several architectures, including e.g. s390x, armhf, etc. bcalm's build will FTBFS on those architectures. Thank you, -- Sergio GPG key

Bug#1031534: firmware-linux-nonfree: Package removed from sid and bookworm

2023-02-17 Thread Gregor Riepl
Package: firmware-linux-nonfree Version: 20221214-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: onit...@gmail.com Dear Maintainer, With the recent upgrade to version 20230210 (or 20230117 on testing), the package has vanished from the apt cache of two of my bookworm/sid

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

2023-02-17 Thread undef
Given that upstream changes to this package haven't been integrated in years and this bug being pretty limiting to users, Mobian moved to systemd-repart. If it's possible for you I might recommend the same solution. Our experience has been that once implemented it is far more reliable. The

Bug#1031529: marked as done (bcalm B-D on libgatbcore-dev which doesn't exist on several architectures)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 23:04:03 + with message-id and subject line Bug#1031529: fixed in bcalm 2.2.3-4 has caused the Debian Bug report #1031529, regarding bcalm B-D on libgatbcore-dev which doesn't exist on several architectures to be marked as done. This means that you claim

Bug#1031530: marked as done (discosnp B-D on libgatbcore-dev which doesn't exist on several architectures)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 23:04:44 + with message-id and subject line Bug#1031530: fixed in discosnp 1:2.6.2-2 has caused the Debian Bug report #1031530, regarding discosnp B-D on libgatbcore-dev which doesn't exist on several architectures to be marked as done. This means that

Bug#1031531: marked as done (mindthegap B-D on libgatbcore-dev which doesn't exist on several architectures)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 23:04:53 + with message-id and subject line Bug#1031531: fixed in mindthegap 2.3.0-2 has caused the Debian Bug report #1031531, regarding mindthegap B-D on libgatbcore-dev which doesn't exist on several architectures to be marked as done. This means that

Bug#1031532: marked as done (minia B-D on libgatbcore-dev which doesn't exist on several architectures)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 23:05:01 + with message-id and subject line Bug#1031532: fixed in minia 3.2.6-3 has caused the Debian Bug report #1031532, regarding minia B-D on libgatbcore-dev which doesn't exist on several architectures to be marked as done. This means that you claim

Bug#1031533: marked as done (simka B-D on libgatbcore-dev which doesn't exist on s390x)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 23:07:06 + with message-id and subject line Bug#1031533: fixed in simka 1.5.3-7 has caused the Debian Bug report #1031533, regarding simka B-D on libgatbcore-dev which doesn't exist on s390x to be marked as done. This means that you claim that the problem

Bug#1030966: marked as pending in ruby-jekyll-remote-theme

2023-02-17 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #1030966 in ruby-jekyll-remote-theme 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#1030966 marked as pending in ruby-jekyll-remote-theme

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1030966 [src:ruby-jekyll-remote-theme] ruby-jekyll-remote-theme accesses the internet during the build Added tag(s) pending. -- 1030966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030966 Debian Bug Tracking System Contact

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

2023-02-17 Thread Theodore Ts'o
On Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote: > So enabling what may be > convenient, but ultimately an anti-pattern is something that hopefully > in the long-term Debian should be striving towards. Sigh, I managed to invert the sense of what I was trying to say. This should

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

2023-02-17 Thread Sam Hartman
> "Theodore" == Theodore Ts'o writes: Theodore> So enabling what may be convenient, but ultimately an Theodore> anti-pattern is something that hopefully in the long-term Theodore> Debian should be trying to *avoid*. That's certainly true. I am not entirely convinced that using

Bug#1031509: marked as done (clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), CVE-2023-20032/CVE-2023-20052)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 19:49:38 + with message-id and subject line Bug#1031509: fixed in clamav 1.0.1+dfsg-1 has caused the Debian Bug report #1031509, regarding clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0), CVE-2023-20032/CVE-2023-20052 to be marked as done. This means that

Bug#1031513: marked as done (clamav: new upstream security release, CVE-2023-20032)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 19:49:38 + with message-id and subject line Bug#1031509: fixed in clamav 1.0.1+dfsg-1 has caused the Debian Bug report #1031509, regarding clamav: new upstream security release, CVE-2023-20032 to be marked as done. This means that you claim that the

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

2023-02-17 Thread Paul Gevers
Hi, On 16-02-2023 23:34, Andreas Beckmann wrote: @elbrus: Why does britney try to migrate clinfo together with pocl? Honestly, I don't know. The logic that does that *is* rather greedy as often it helps (but not always). IMO clinfo should be able to migrate on its own without causing new

Bug#1031524: fuse3: setxattr is broken

2023-02-17 Thread Graham Inggs
Source: fuse3 Version: 3.13.0-1 Severity: serious Forwarded: https://github.com/libfuse/libfuse/issues/730 Control: affects -1 src:ostree Hi Maintainer Since the upload of 3.13.0-1, the 'name' string passed to fs->op.setxattr has the first 8 characters missing. Steps to reproduce: $ dget

Processed: fuse3: setxattr is broken

2023-02-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:ostree Bug #1031524 [src:fuse3] fuse3: setxattr is broken Added indication that 1031524 affects src:ostree -- 1031524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

2023-02-17 Thread Adrian Bunk
On Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote: >... > So enabling what may be > convenient, but ultimately an anti-pattern is something that hopefully > in the long-term Debian should be striving towards. Yes, it's > annoying and and extra work. So is using build chroots if we

Bug#1031480: marked as done (libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 21:49:48 + with message-id and subject line Bug#1031480: fixed in libreflectasm-java 1.11.9+dfsg-4 has caused the Debian Bug report #1031480, regarding libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25 to be marked as done. This means

Bug#1029300: src:tar: fails to migrate to testing for too long

2023-02-17 Thread Mechtilde Stehmann
Hello Paul, If it is better for the release, please remove my try to fix it. Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F

Bug#1031441: Relax oauth2 dependency

2023-02-17 Thread Daniel Leidert
I just rebuilt ruby-github-api by relaxing the dependency on oauth2. I pulled the test cases from github to check if anything happens. It built just fine. 6 tests failed, but none related to OAuth2 (seems some keywords/options mismatch). I think we could fix this by relaxing the dep on oauth2 for

Bug#1031455: marked as done (charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror])

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 19:19:56 + with message-id and subject line Bug#1031455: fixed in fuse3 3.14.0-1 has caused the Debian Bug report #1031455, regarding charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror] to be marked as done. This means that you

Bug#1031469: marked as done (botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1)

2023-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Feb 2023 19:19:34 + with message-id and subject line Bug#1031469: fixed in botch 0.24-2 has caused the Debian Bug report #1031469, regarding botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1 to be marked as done. This means that you claim that the

Processed: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

2023-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1014662 serious Bug #1014662 [cloud-initramfs-growroot] cloud-initramfs-growroot: Initramfs hook does not include `flock` command Severity set to 'serious' from 'important' > tags 1014662 + patch Bug #1014662 [cloud-initramfs-growroot]

  1   2   >