Bug#1105796: marked as done (RFS: pdfmixtool/1.1.1+git20250512-1 [ITP] -- perform common editing operations on PDF files)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 06:50:54 - with message-id <20250516065054.4c269...@debian.org> and subject line Re: Bug#1105796: RFS: pdfmixtool/1.1.1+git20250512-1 [ITP] -- perform common editing operations on PDF files has caused the Debian Bug report #1105796, regarding RFS: pdfmixtool

Bug#1104271: marked as done (sm has an undeclared file conflict on /usr/share/man/man1/sm.1.gz)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 06:33:59 + with message-id and subject line Bug#1104271: fixed in screen-message 0.29-2 has caused the Debian Bug report #1104271, regarding sm has an undeclared file conflict on /usr/share/man/man1/sm.1.gz to be marked as done. This means that you claim th

Bug#437620: marked as done (netsed: not handling nostrip build option (policy 10.1))

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 05:05:21 + with message-id and subject line Bug#437620: fixed in netsed 1.4-1 has caused the Debian Bug report #437620, regarding netsed: not handling nostrip build option (policy 10.1) to be marked as done. This means that you claim that the problem has be

Bug#1094091: marked as done (netsed: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 05:05:21 + with message-id and subject line Bug#1094091: fixed in netsed 1.4-1 has caused the Debian Bug report #1094091, regarding netsed: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2 to be marked as done. This means that you claim that t

Bug#1105545: marked as done (libdatrie: FTBFS with make --shuffle=reverse: ln: failed to create symbolic link '/build/reproducible-path/libdatrie-0.2.13/debian/tmp/usr/bin/trietool-0.2': No such file

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 04:49:06 + with message-id and subject line Bug#1105545: fixed in libdatrie 0.2.13-4 has caused the Debian Bug report #1105545, regarding libdatrie: FTBFS with make --shuffle=reverse: ln: failed to create symbolic link '/build/reproducible-path/libdatrie-0

Bug#1105684: marked as done (pixelize: FTBFS with make --shuffle=reverse: Fatal error: can't create obj/menu.o: No such file or directory)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 03:49:00 + with message-id and subject line Bug#1105684: fixed in pixelize 2.0.0~git20220108.d1f9da9-2 has caused the Debian Bug report #1105684, regarding pixelize: FTBFS with make --shuffle=reverse: Fatal error: can't create obj/menu.o: No such file or di

Processed: ITP: golang-github-mattn-go-sixel -- Go library for DRCS Sixel graphics encoding and decoding

2025-05-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1105843 Bug #1105843 [wnpp] ITP: golang-github-mattn-go-sixel -- Go library for DRCS Sixel graphics encoding and decoding Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1105843: https://bu

Bug#1105205: marked as done (reportbug: nvidia-cuda-dev breaks libcuda1 < 545 (libcuda 535 in Sid))

2025-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 16 May 2025 01:49:41 + with message-id and subject line Bug#1105205: fixed in nvidia-graphics-drivers 545.29.06-2 has caused the Debian Bug report #1105205, regarding reportbug: nvidia-cuda-dev breaks libcuda1 < 545 (libcuda 535 in Sid) to be marked as done. This means

Bug#1094959: marked as done (vim-nox highlight visual cterm=reverse fails in trixie)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 20:24:48 -0400 with message-id and subject line Re: Bug#1094959: vim-nox highlight visual cterm=reverse fails in trixie has caused the Debian Bug report #1094959, regarding vim-nox highlight visual cterm=reverse fails in trixie to be marked as done. This mean

Bug#1035858: marked as done (libxc9: broken symlink: /usr/share/doc/libxc9/README -> README.md)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 20:34:57 + with message-id and subject line Bug#1035858: fixed in libxc 5.2.3-3 has caused the Debian Bug report #1035858, regarding libxc9: broken symlink: /usr/share/doc/libxc9/README -> README.md to be marked as done. This means that you claim that the p

Bug#1091947: marked as done (python-click-option-group: FTBFS: FAILED tests/test_click_option_group.py::test_missing_group_decl_first_api)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 19:48:58 + with message-id and subject line Bug#1091947: fixed in python-click-option-group 0.5.6-1.1 has caused the Debian Bug report #1091947, regarding python-click-option-group: FTBFS: FAILED tests/test_click_option_group.py::test_missing_group_decl_fir

Bug#1102961: marked as done (genx: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 --dir genx returned exit code 13)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 20:45:06 +0100 with message-id and subject line Re: Bug#1102961: genx: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 --dir genx returned exit code 13 has caused the Debian Bug report #1102961, regarding genx: FT

Bug#1103156: marked as done (Remmina)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 19:34:37 + with message-id and subject line Bug#1103156: fixed in remmina 1.4.40+dfsg-1 has caused the Debian Bug report #1103156, regarding Remmina to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#1105212: marked as done (remmina: New release 1.4.40)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 19:34:37 + with message-id and subject line Bug#1105212: fixed in remmina 1.4.40+dfsg-1 has caused the Debian Bug report #1105212, regarding remmina: New release 1.4.40 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1105616: marked as done (secure-delete: FTBFS with make --shuffle=reverse: ld: cannot find sdel-lib.o: No such file or directory)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 17:19:41 + with message-id and subject line Bug#1105616: fixed in secure-delete 3.1-12 has caused the Debian Bug report #1105616, regarding secure-delete: FTBFS with make --shuffle=reverse: ld: cannot find sdel-lib.o: No such file or directory to be marked

Bug#1104596: marked as done (rust-libphosh: FTBFS: error[E0425]: cannot find value `PANGO_FONT_MASK_VARIATIONS` in crate `ffi`)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 17:04:19 + with message-id and subject line Bug#1104596: fixed in rust-libphosh 0.0.6-3 has caused the Debian Bug report #1104596, regarding rust-libphosh: FTBFS: error[E0425]: cannot find value `PANGO_FONT_MASK_VARIATIONS` in crate `ffi` to be marked as do

Bug#1089203: marked as done (systemd-zram-generator: Removes user configuration on every update)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 17:04:38 + with message-id and subject line Bug#1089203: fixed in rust-zram-generator 1.2.1-2 has caused the Debian Bug report #1089203, regarding systemd-zram-generator: Removes user configuration on every update to be marked as done. This means that you c

Bug#1104997: marked as done (unblock: osspd/1.3.3-4)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 18:45:03 +0200 with message-id and subject line Re: Bug#1104997: unblock: osspd/1.3.3-4 has caused the Debian Bug report #1104997, regarding unblock: osspd/1.3.3-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1098477: marked as done (nginx-common: service fails to start after #1082373 dependency loop resolved)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 14:36:25 + with message-id and subject line Bug#1098477: fixed in nginx 1.26.3-3 has caused the Debian Bug report #1098477, regarding nginx-common: service fails to start after #1082373 dependency loop resolved to be marked as done. This means that you cla

Bug#1013232: marked as done (maxima: Incorrect remainder evaluation with unbound variables)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 10:26:45 -0400 with message-id <87o6vut0ey@maguirefamily.org> and subject line Re: [Maxima-discuss] maxima: Incorrect remainder evaluation with unbound variables has caused the Debian Bug report #1013232, regarding maxima: Incorrect remainder evaluation with

Bug#1105806: marked as done (net-tools: CVE-2025-46836)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 13:50:10 + with message-id and subject line Bug#1105806: fixed in net-tools 2.10-1.2 has caused the Debian Bug report #1105806, regarding net-tools: CVE-2025-46836 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1092577: marked as done (erlang-hex: Build with newer Elixir and Erlang)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 13:19:03 + with message-id and subject line Bug#1092577: fixed in erlang-hex 2.0.6-1 has caused the Debian Bug report #1092577, regarding erlang-hex: Build with newer Elixir and Erlang to be marked as done. This means that you claim that the problem has bee

Bug#1105185: marked as done (erlang-hex: Elixir requires newer hex version)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 13:19:03 + with message-id and subject line Bug#1105185: fixed in erlang-hex 2.0.6-1 has caused the Debian Bug report #1105185, regarding erlang-hex: Elixir requires newer hex version to be marked as done. This means that you claim that the problem has been

Processed: closing 1104273

2025-05-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1104273 3.0.11+~0.4.1-3 Bug #1104273 [src:rust-ureq] rust-ureq: autopkgtests fail on all archs Marked as fixed in versions rust-ureq/3.0.11+~0.4.1-3. Bug #1104273 [src:rust-ureq] rust-ureq: autopkgtests fail on all archs Marked Bug as done >

Bug#1104541: marked as done (cinder: [INTL:nl] Dutch debconf templates translation)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 11:34:19 + with message-id and subject line Bug#1104541: fixed in cinder 2:26.0.0-1.1 has caused the Debian Bug report #1104541, regarding cinder: [INTL:nl] Dutch debconf templates translation to be marked as done. This means that you claim that the problem

Bug#1104290: marked as done (cinder: [INTL:de] updated German debconf translation)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 11:34:19 + with message-id and subject line Bug#1104290: fixed in cinder 2:26.0.0-1.1 has caused the Debian Bug report #1104290, regarding cinder: [INTL:de] updated German debconf translation to be marked as done. This means that you claim that the problem

Bug#1009332: marked as done (maxima-emacs: Imaxima fails to render latex)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Wed, 14 May 2025 17:50:33 -0400 with message-id <877c2i7tg6@maguirefamily.org> and subject line maxima-emacs: Imaxima fails to render latex has caused the Debian Bug report #1009332, regarding maxima-emacs: Imaxima fails to render latex to be marked as done. This means that

Bug#1103902: marked as done (austin: Vcs-* fields incorrectly refer to upstream)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 10:18:56 + with message-id and subject line Bug#1103902: fixed in austin 3.7.0-1 has caused the Debian Bug report #1103902, regarding austin: Vcs-* fields incorrectly refer to upstream to be marked as done. This means that you claim that the problem has bee

Bug#1103802: marked as done (austin: does not work with Python >3.8)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 10:18:56 + with message-id and subject line Bug#1103802: fixed in austin 3.7.0-1 has caused the Debian Bug report #1103802, regarding austin: does not work with Python >3.8 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1105798: marked as done (unblock: rust-dysk/2.10.0-3)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:15:08 + with message-id and subject line unblock rust-dysk has caused the Debian Bug report #1105798, regarding unblock: rust-dysk/2.10.0-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#1105801: marked as done (unblock: rust-speakersafetyd/1.1.2-3)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:17:42 + with message-id and subject line unblock rust-speakersafetyd has caused the Debian Bug report #1105801, regarding unblock: rust-speakersafetyd/1.1.2-3 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1105377: marked as done (gsasl: FTBFS with make --shuffle=reverse: make[1]: *** [debian/rules:18: gen] Error 1 shuffle=reverse)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:34:40 + with message-id and subject line Bug#1105377: fixed in gsasl 2.2.2-2 has caused the Debian Bug report #1105377, regarding gsasl: FTBFS with make --shuffle=reverse: make[1]: *** [debian/rules:18: gen] Error 1 shuffle=reverse to be marked as done.

Bug#1105800: marked as done (unblock: rust-asahi-wifisync/0.2.2-5)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:16:57 + with message-id and subject line unblock rust-asahi-wifisync has caused the Debian Bug report #1105800, regarding unblock: rust-asahi-wifisync/0.2.2-5 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1105368: marked as done (hlins: FTBFS with make --shuffle=reverse: make[3]: *** [Makefile:52: hlins.cmo] Error 2 shuffle=reverse)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:19:09 + with message-id and subject line Bug#1105368: fixed in hlins 0.40-2 has caused the Debian Bug report #1105368, regarding hlins: FTBFS with make --shuffle=reverse: make[3]: *** [Makefile:52: hlins.cmo] Error 2 shuffle=reverse to be marked as done.

Bug#1105802: marked as done (unblock: rust-tiny-dfr/0.3.5-1)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:18:28 + with message-id and subject line unblock rust-tiny-dfr has caused the Debian Bug report #1105802, regarding unblock: rust-tiny-dfr/0.3.5-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#1105799: marked as done (unblock: rust-procs/0.14.10-1)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:16:11 + with message-id and subject line unblock rust-procs has caused the Debian Bug report #1105799, regarding unblock: rust-procs/0.14.10-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#1105797: marked as done (unblock: rust-du-dust/1.2.0-1)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:14:01 + with message-id and subject line unblock rust-du-dust has caused the Debian Bug report #1105797, regarding unblock: rust-du-dust/1.2.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1105779: marked as done (unblock: icingaweb2/2.12.4-2)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:09:55 + with message-id and subject line unblock icingaweb2 has caused the Debian Bug report #1105779, regarding unblock: icingaweb2/2.12.4-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#1105795: marked as done (unblock: rust-asahi-nvram/0.2.3-5)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:12:21 + with message-id and subject line unblock rust-asahi-nvram has caused the Debian Bug report #1105795, regarding unblock: rust-asahi-nvram/0.2.3-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1105791: marked as done (unblock: xstow/1.1.1-1)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:11:21 + with message-id and subject line unblock xstow has caused the Debian Bug report #1105791, regarding unblock: xstow/1.1.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#1105789: marked as done (unblock: xserver-xorg-input-aiptek/1:1.4.1-5)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:10:24 + with message-id and subject line unblock xserver-xorg-input-aiptek has caused the Debian Bug report #1105789, regarding unblock: xserver-xorg-input-aiptek/1:1.4.1-5 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1063234: marked as done (libxml2: CVE-2024-25062)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 08:34:49 + with message-id and subject line Bug#1063234: fixed in libxml2 2.12.7+dfsg+really2.9.14-1 has caused the Debian Bug report #1063234, regarding libxml2: CVE-2024-25062 to be marked as done. This means that you claim that the problem has been dealt

Bug#1103511: marked as done (libxml2: CVE-2025-32415)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 08:34:49 + with message-id and subject line Bug#1103511: fixed in libxml2 2.12.7+dfsg+really2.9.14-1 has caused the Debian Bug report #1103511, regarding libxml2: CVE-2025-32415 to be marked as done. This means that you claim that the problem has been dealt

Bug#1051230: marked as done (libxml2: CVE-2023-39615)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 08:34:49 + with message-id and subject line Bug#1051230: fixed in libxml2 2.12.7+dfsg+really2.9.14-1 has caused the Debian Bug report #1051230, regarding libxml2: CVE-2023-39615 to be marked as done. This means that you claim that the problem has been dealt

Bug#1053629: marked as done (libxml2: CVE-2023-45322)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 08:34:49 + with message-id and subject line Bug#1053629: fixed in libxml2 2.12.7+dfsg+really2.9.14-1 has caused the Debian Bug report #1053629, regarding libxml2: CVE-2023-45322 to be marked as done. This means that you claim that the problem has been dealt

Bug#1102521: marked as done (libxml2: CVE-2025-32414)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 08:34:49 + with message-id and subject line Bug#1102521: fixed in libxml2 2.12.7+dfsg+really2.9.14-1 has caused the Debian Bug report #1102521, regarding libxml2: CVE-2025-32414 to be marked as done. This means that you claim that the problem has been dealt

Bug#1105194: marked as done (unblock: anarchism/15.3-4)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 10:24:37 +0200 with message-id <876f87a9-57fb-427d-9b13-2dcfaec90...@debian.org> and subject line Re: Bug#1105194: unblock: anarchism/15.3-4 has caused the Debian Bug report #1105194, regarding unblock: anarchism/15.3-4 to be marked as done. This means that you

Bug#1103871: marked as done (unblock: vala-panel/24.05-3)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:42:00 +0200 with message-id <9739c4d3-9f1a-446b-99fe-892cb77e9...@debian.org> and subject line Re: Bug#1103871: unblock: vala-panel/24.05-3 has caused the Debian Bug report #1103871, regarding unblock: vala-panel/24.05-3 to be marked as done. This means that

Bug#1104534: marked as done (bacula-director-mysql: Upgrading 9 > 15 - Database not being converted)

2025-05-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 May 2025 09:42:48 +0200 with message-id <87ikm2pbev@arioch.leonhardt.eu> and subject line Re: [pkg-bacula-devel] Bug#1104534: bacula-director-mysql: Upgrading 9 > 15 - Database not being converted has caused the Debian Bug report #1104534, regarding bacula-director-m