Bug#1056709: node-nodemailer: FTBFS test proxy is stuck

2023-11-24 Thread Gianfranco Costamagna
Source: node-nodemailer Version: 6.9.4+~6.4.9-3 Severity: serious Hello, In my local machine, when I try a pbuilder sid build of the package, I get the build stuck 1) HTTP Proxy Client Tests should connect to a socket through proxy with auth: Uncaught AssertionError: expected

Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free

2023-11-24 Thread Helmut Grohne
User: helm...@debian.org Usertags: dep17p1 On Fri, Sep 01, 2023 at 07:13:13AM +0200, Helmut Grohne wrote: > firmware-carl9170 installs /lib/firmware/carl9170-1.fw, which is also > currently installed by firmware-linux-free. I see that this is quite > intentional as this piece of firmware is being

Bug#1056708: node-wikibase-cli: Using internet during tests

2023-11-24 Thread Gianfranco Costamagna
Source: node-wikibase-cli Version: 15.15.4-5 Severity: serious Hello, as said, there are multiple calls to wikidata.org, making the package FTBFS with tests disabled. Error: Command failed: export WB_CLIPBOARD=false WB_LANG=en WB_MAXLAG=100 ; ./bin/wd claims -c Q12569 P2586 FetchError:

Bug#1056705: marked as done (node-mqtt: Missing dependency to node-lru-cache)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Sat, 25 Nov 2023 04:36:26 + with message-id and subject line Bug#1056705: fixed in node-mqtt 4.3.7-3 has caused the Debian Bug report #1056705, regarding node-mqtt: Missing dependency to node-lru-cache to be marked as done. This means that you claim that the problem has

Processed: Bug#1056705 marked as pending in node-mqtt

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056705 [node-mqtt] node-mqtt: Missing dependency to node-lru-cache Added tag(s) pending. -- 1056705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1056705: marked as pending in node-mqtt

2023-11-24 Thread Yadd
Control: tag -1 pending Hello, Bug #1056705 in node-mqtt 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#1056705: node-mqtt: Missing dependency to node-lru-cache

2023-11-24 Thread Yadd
Package: node-mqtt Version: 4.3.7-2 Severity: serious Tags: patch Justification: Failure X-Debbugs-Cc: y...@debian.org Hi, node-mqtt autopkgtest shows that this package requires node-lru-cache, however it is not listed in debian/control and then start to fail when one of its dependencies no more

Bug#1054808: marked as done (x-tile: FTBFS: make: *** [debian/rules:4: clean] Error 25)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Sat, 25 Nov 2023 03:34:07 + with message-id and subject line Bug#1054808: fixed in x-tile 3.3+git20220708.9ec59c9-1 has caused the Debian Bug report #1054808, regarding x-tile: FTBFS: make: *** [debian/rules:4: clean] Error 25 to be marked as done. This means that you

Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol

2023-11-24 Thread Jérôme Charaoui
Hi Miguel, Le 2023-11-24 à 18 h 38, Miguel Landaeta a écrit : Thomas and Jérôme, Do you have any concerns with me uploading a fix for this issue? I'm working with some folks here in Cambridge MiniDebConf and I also have some cycles to spare to work on JRuby and maybe prepare a new upstream

Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones

2023-11-24 Thread Helmut Grohne
Hi, On Mon, Nov 20, 2023 at 04:05:31PM +0100, Helmut Grohne wrote: > I've attached the prospective change to this mail. It passes piuparts > and it passes my own test cases. I definitely think it should be > reviewed before uploaded. One thing I already see for possible > improvement is that

Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol

2023-11-24 Thread Miguel Landaeta
Thomas and Jérôme, Do you have any concerns with me uploading a fix for this issue? I'm working with some folks here in Cambridge MiniDebConf and I also have some cycles to spare to work on JRuby and maybe prepare a new upstream release for 9.3 and/or 9.4 series (experimental).

Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol

2023-11-24 Thread Miguel Landaeta
tags 1042129 + patch thanks Upstream handled this when they upgraded Joni dependency to 2.2 on JRuby 9.4 series. https://github.com/jruby/jruby/commit/3c94d31f1e198f294e9bfcb96b4188c315252b6b https://github.com/jruby/jruby/commit/783d14bcb140477bb2577310a90742d594a48896 See attached a fix for

Processed: Re: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1042129 + patch Bug #1042129 [src:jruby] jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol Added tag(s) patch. > thanks Stopping processing here. Please contact me

Processed: found 1055984 in 2.10.22-4, found 1055984 in 2.10.34-1

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1055984 2.10.22-4 Bug #1055984 {Done: Jeremy Bícha } [src:gimp] gimp: CVE-2023-1 CVE-2023-2 CVE-2023-3 CVE-2023-4 Marked as found in versions gimp/2.10.22-4. > found 1055984 2.10.34-1 Bug #1055984 {Done: Jeremy Bícha }

Bug#1054812: marked as done (lybniz: FTBFS: make: *** [debian/rules:8: clean] Error 25)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 22:04:25 + with message-id and subject line Bug#1054812: fixed in lybniz 3.0.4-6 has caused the Debian Bug report #1054812, regarding lybniz: FTBFS: make: *** [debian/rules:8: clean] Error 25 to be marked as done. This means that you claim that the problem

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

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 21:21:52 + with message-id and subject line Bug#1052770: fixed in flask-wtf 1.2.1-1 has caused the Debian Bug report #1052770, regarding flask-wtf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to

Bug#1055901: Acknowledgement (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)

2023-11-24 Thread Thorsten Glaser
Hi, this applies only to Raspian, not to Debian; in Debian, older releases used /boot/firmware as well. I suggest to go ask the Raspian people to fix what they broke. Mixing packages from other distributions (here Raspian) with Debian packages is not generally supported. bye, //mirabilos (not

Bug#1056699: node-wikibase-cli fails to build from source without Internet access

2023-11-24 Thread Jeremy Bícha
Source: node-wikibase-cli Version: 15.15.4-5 Severity: serious Tags: ftbfs sid trixie This is a follow up from https://bugs.debian.org/1042298 node-wikibase-cli still fails to build from source (during dh_auto_test) without Internet access. This can be seen in the Ubuntu build:

Bug#1054758: marked as done (sorl-thumbnail: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 19:37:46 + with message-id and subject line Bug#1054758: fixed in sorl-thumbnail 12.10.0-1 has caused the Debian Bug report #1054758, regarding sorl-thumbnail: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1 to be marked as done. This

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'normal' from 'serious' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

2023-11-24 Thread Matthias Klose
Control: severity -1 normal On 24.11.23 19:22, Thorsten Glaser wrote: Control: severity -1 serious thanks Matthias Klose dixit: musl is not part of the standard toolchain, not even on mips64el. Please build your package with the default toolchain This isn’t (just) an issue with a package

Bug#1056399: marked as done (libcryptx-perl: invalid opcode in CryptX.so)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 18:34:19 + with message-id and subject line Bug#1056399: fixed in libcryptx-perl 0.080-2 has caused the Debian Bug report #1056399, regarding libcryptx-perl: invalid opcode in CryptX.so to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'serious' from 'normal' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug

Bug#1056399: libcryptx-perl: invalid opcode in CryptX.so

2023-11-24 Thread gregor herrmann
On Fri, 24 Nov 2023 16:24:04 +0100, Benedikt Spranger wrote: > I rebuild the Package without these flags (-msse4.1 / -maes) and > everything works as expected. I also removed the -maes flag, since AES > is, like SSE4.1, is not part of the Debian amd64 architectural > baseline. Patch is attached.

Processed: severity of 1056399 is serious, tagging 1056399

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1056399 serious Bug #1056399 [libcryptx-perl] libcryptx-perl: invalid opcode in CryptX.so Severity set to 'serious' from 'important' > tags 1056399 + patch Bug #1056399 [libcryptx-perl] libcryptx-perl: invalid opcode in CryptX.so Added

Processed: retitle 1056282 to gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1056282 gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 > CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Bug #1056282 [src:gpac] gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Ignoring

Bug#1042222: marked as done (markdown-callouts: FTBFS: AssertionError: assert '\n')

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 17:07:57 + with message-id and subject line Bug#104: fixed in markdown-callouts 0.3.0+20231124-1 has caused the Debian Bug report #104, regarding markdown-callouts: FTBFS: AssertionError: assert '\n' to be marked as done. This means that you claim

Bug#1056348: FTBFS: tests fail in clean environment

2023-11-24 Thread Nicolas Mora
Hello, I've forwarded the bug upstream [1] and they made a patch [2]. Can you test their patch on your package, to check if the problem is fixed on your CI? Also, if this works, I suggest to apply their patch rather than yours to make the code more consistent with upstream, do you agree?

Bug#1053310: marked as done (exim4-base: Various severe CVE reports are outstanding)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 14:47:09 + with message-id and subject line Bug#1053310: fixed in exim4 4.96-15+deb12u3 has caused the Debian Bug report #1053310, regarding exim4-base: Various severe CVE reports are outstanding to be marked as done. This means that you claim that the

Bug#1056627: marked as done (cython3 has an undeclared file conflict)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 14:34:48 + with message-id and subject line Bug#1056627: fixed in cython 0.29.36-3 has caused the Debian Bug report #1056627, regarding cython3 has an undeclared file conflict to be marked as done. This means that you claim that the problem has been dealt

Bug#1056627: marked as done (cython3 has an undeclared file conflict)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 14:35:10 + with message-id and subject line Bug#1056627: fixed in cython 3.0.5-2 has caused the Debian Bug report #1056627, regarding cython3 has an undeclared file conflict to be marked as done. This means that you claim that the problem has been dealt

Processed: Close 1054750

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1054750 Bug #1054750 [src:reuse] reuse: FTBFS: make: *** [debian/rules:4: binary] Error 1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054750:

Bug#1036255: marked as done (python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check sy

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 14:32:12 + with message-id and subject line Bug#1036255: fixed in python3-onelogin-saml2 1.12.0-2+deb12u1 has caused the Debian Bug report #1036255, regarding python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the

Bug#1055962: marked as done (intel-microcode: CVE-2023-23583: INTEL-SA-00950)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 14:32:09 + with message-id and subject line Bug#1055962: fixed in intel-microcode 3.20231114.1~deb12u1 has caused the Debian Bug report #1055962, regarding intel-microcode: CVE-2023-23583: INTEL-SA-00950 to be marked as done. This means that you claim that

Bug#1055874: marked as done (intel-graphics-compiler: FTBFS in bookworm with intel-vc-intrinsics-dev 0.11)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 14:32:09 + with message-id and subject line Bug#1055874: fixed in intel-graphics-compiler 1.0.12504.6-1+deb12u1 has caused the Debian Bug report #1055874, regarding intel-graphics-compiler: FTBFS in bookworm with intel-vc-intrinsics-dev 0.11 to be marked

Processed: Bug#1056627 marked as pending in cython

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056627 [cython3] cython3 has an undeclared file conflict Ignoring request to alter tags of bug #1056627 to the same tags previously set -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact

Processed: Bug#1056627 marked as pending in cython

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056627 [cython3] cython3 has an undeclared file conflict Added tag(s) pending. -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1056627: marked as pending in cython

2023-11-24 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1056627 in cython 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#1056627: marked as pending in cython

2023-11-24 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1056627 in cython 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: Re: ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)'

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:ros2-performance-test-fixture Bug #1054676 [src:ros2-rosidl] ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)' Bug reassigned from

Bug#1054676: ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)'

2023-11-24 Thread Timo Röhling
Control: reassign -1 src:ros2-performance-test-fixture This bug can be resolved by a rebuild of ros2-performance-test-fixture. On Fri, 27 Oct 2023 21:15:54 +0200 Lucas Nussbaum wrote: > /usr/bin/ld: > /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: > undefined reference to >

Bug#1056634: marked as done (rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 12:20:15 + with message-id and subject line Bug#1056634: fixed in rust-unsigned-varint 0.8.0-1 has caused the Debian Bug report #1056634, regarding rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev to be marked as

Bug#1056639: marked as done (FTBFS: requires network during mandatory build steps)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 11:36:48 + with message-id and subject line Bug#1056639: fixed in rust-urlshortener 3.0.2-2 has caused the Debian Bug report #1056639, regarding FTBFS: requires network during mandatory build steps to be marked as done. This means that you claim that the

Bug#1051433: marked as done (mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 11:04:41 + with message-id and subject line Bug#1051433: fixed in mysql-workbench 8.0.32+dfsg-2 has caused the Debian Bug report #1051433, regarding mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’ to be marked as done. This means

Processed: Bug#1051433 marked as pending in mysql-workbench

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1051433 [src:mysql-workbench] mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’ Added tag(s) pending. -- 1051433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051433 Debian Bug Tracking System Contact

Bug#1051433: marked as pending in mysql-workbench

2023-11-24 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #1051433 in mysql-workbench 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#1055841: marked as done (spyder-kernels: Build-Depends on python3-xarray which is not in testing)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 10:34:56 + with message-id and subject line Bug#1055841: fixed in spyder-kernels 2.5.0-1 has caused the Debian Bug report #1055841, regarding spyder-kernels: Build-Depends on python3-xarray which is not in testing to be marked as done. This means that you

Processed: curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1037258 curl/8.2.1-1 Bug #1037258 [curl] curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance Marked as fixed in versions curl/8.2.1-1. > -- Stopping processing here. Please contact me if you need assistance. --

Processed: forwarded issue

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1055159 https://github.com/regebro/svg.path/issues/103 Bug #1055159 [src:python-svg.path] python-svg.path's autopkg tests fail with pillow 10.1.0 Set Bug forwarded-to-address to 'https://github.com/regebro/svg.path/issues/103'. >

Bug#1056608: timeshift: Timeshift cant restore RSYNC snapshots if your system installed on BTRFS with wrong subvolume

2023-11-24 Thread Alex Truescore
Note: By "upstream doesnt have that problem" i meant that Debian Testing and Debian Sid timeshift doesnt have that problem.

Bug#1055922: marked as done (rmatrix: ABI change in Matrix 1.6-2)

2023-11-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Nov 2023 10:28:35 + with message-id and subject line Re: Bug#1055922: rmatrix: ABI change in Matrix 1.6-2 has caused the Debian Bug report #1055922, regarding rmatrix: ABI change in Matrix 1.6-2 to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

2023-11-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'normal' from 'serious' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

2023-11-24 Thread Matthias Klose
Control: severity -1 normal musl is not part of the standard toolchain, not even on mips64el. Please build your package with the default toolchain, and report any other issues upstream yourself. On 27.08.23 17:07, Thorsten Glaser wrote: reassign 1050429 gcc-13 13.2.0-2 notfound 1050429

Bug#1056639: FTBFS: requires network during mandatory build steps

2023-11-24 Thread Sven Mueller
Package: rust-urlshortener Version: 3.0.2-1 Severity: grave Justification for severity: Policy violation During a rebuild of Debian testing, we ran into this test failing during an sbuild controlled build on a VM with limit network connectivity (only configured APT repositories usable). See log

Bug#1056281: closing 1056281

2023-11-24 Thread Salvatore Bonaccorso
close 1056281 thanks According to upstream information the issue dovered in the one CVE is only affecting Snort Open Source 3.x. Still likely snort should be removed from the archive?

Processed: closing 1056281

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1056281 Bug #1056281 [src:snort] snort: CVE-2023-20246 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1056281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056281 Debian Bug

Bug#1056637: debian-multimedia: depends on removed mjpegtools-gtk

2023-11-24 Thread Gianfranco Costamagna
Source: debian-multimedia Version: 0.10 Severity: serious mjpegtools-gtk has been dropped but multimedia-video multimedia-recording and multimedia-players still depend on it. Please update thanks G. OpenPGP_signature.asc Description: OpenPGP digital signature

Processed: affects 1056634

2023-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1056634 librust-multihash-dev librust-cid-dev librust-rust-unixfs-dev Bug #1056634 [src:rust-unsigned-varint] rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev Added indication that 1056634

Bug#1056634: rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev

2023-11-24 Thread Jonas Smedegaard
Source: rust-unsigned-varint Version: 0.7.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package is impossible to install: Depends on missing package librust-asynchronous-codec-0.6+default-dev -BEGIN PGP SIGNATURE-