Bug#1077314: unblock: pytest-jupyter/0.9.1-2

2024-07-28 Thread Paul Gevers
Hi Julian, On 28-07-2024 11:10, Julian Gilbey wrote: It's failing the autopkgtest on riscv64 quite badly. It's a new package, and I have no idea where in the toolchain the problem lies; given that pytest also fails on this architecture, it's probably not pytest-jupyter itself that is

Bug#1072920: marked as done (release.debian.org: force-skiptest debusine/0.3.2/riscv64)

2024-07-28 Thread Debian Bug Tracking System
Your message dated Mon, 29 Jul 2024 06:48:36 +0200 with message-id and subject line Re: Bug#1072920: release.debian.org: force-skiptest debusine/0.3.2/riscv64 has caused the Debian Bug report #1072920, regarding release.debian.org: force-skiptest debusine/0.3.2/riscv64 to be marked as done.

Re: [Pkg-rust-maintainers] Debian Trixie and Rust 2024

2024-07-28 Thread Fabian Grünbichler
On Sun, Jul 28, 2024, at 1:49 AM, Travis Cross wrote: > Greetings. We understand there to be ongoing discussions about the > selection of the Rust release to include in Debian Trixie, and > relatedly, discussions about the freeze schedule for Trixie. We've > heard there may be tentative plans to

Processed: New of imagemagick7

2024-07-28 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - moreinfo Bug #1060103 [release.debian.org] transition: imagemagick7 Removed tag(s) moreinfo. -- 1060103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1060103: New of imagemagick7

2024-07-28 Thread Bastien Roucariès
control: tags -1 - moreinfo Hi, Last reverse deps of lib magick pipeline is not really bad https://salsa.debian.org/debian/imagemagick/-/pipelines/708187 A lot of failure are due to broken package or does not use pkgconfig I suppose we could go to experimental Bastien signature.asc

Processed: tagging 1072466

2024-07-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # ffmpeg 7.0 uploaded to unstable > tags 1072466 = confirmed Bug #1072466 [release.debian.org] transition: ffmpeg Added tag(s) confirmed; removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1077325: bullseye-pu: package poe.app/0.5.1-6+deb11u1

2024-07-28 Thread Yavor Doganov
Package: release.debian.org Severity: normal Tags: bullseye X-Debbugs-Cc: poe@packages.debian.org Control: affects -1 + src:poe.app User: release.debian@packages.debian.org Usertags: pu This is basically the same as bookworm-pu #1077323 but since I cannot be sure that the same SRM will

Processed: bullseye-pu: package poe.app/0.5.1-6+deb11u1

2024-07-28 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:poe.app Bug #1077325 [release.debian.org] bullseye-pu: package poe.app/0.5.1-6+deb11u1 Added indication that 1077325 affects src:poe.app -- 1077325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077325 Debian Bug Tracking System Contact

Processed: bookworm-pu: package poe.app/0.5.1-6+deb12u1

2024-07-28 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:poe.app Bug #1077323 [release.debian.org] bookworm-pu: package poe.app/0.5.1-6+deb12u1 Added indication that 1077323 affects src:poe.app -- 1077323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077323 Debian Bug Tracking System Contact

Bug#1077323: bookworm-pu: package poe.app/0.5.1-6+deb12u1

2024-07-28 Thread Yavor Doganov
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: poe@packages.debian.org Control: affects -1 + src:poe.app User: release.debian@packages.debian.org Usertags: pu [ Reason ] I would like to fix #1076829 in stable as currently the package is completely unusable. The

Bug#1077314: unblock: pytest-jupyter/0.9.1-2

2024-07-28 Thread Julian Gilbey
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pytest-jupyter [ Reason ] It's failing the autopkgtest on riscv64 quite badly. It's a new package, and I have no idea where in the toolchain the problem lies; given