Bug#1046248: marked as done (libapache2-mod-intercept-form-submit: Fails to build source after successful build)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sun, 23 Feb 2025 07:19:39 + with message-id and subject line Bug#1046248: fixed in libapache2-mod-intercept-form-submit 1.2.0-1 has caused the Debian Bug report #1046248, regarding libapache2-mod-intercept-form-submit: Fails to build source after successful build to be mar

Processed: Re: Bug#1098299: cinnamon-settings crashes without python3-pam

2025-02-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #1098299 [cinnamon] cinnamon-settings crashes without python3-pam Marked Bug as done -- 1098299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1035254: marked as done (singularity: please add autopkgtests (to add coverage for python3-numpy))

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sun, 23 Feb 2025 07:05:25 + with message-id and subject line Bug#1035254: fixed in singularity 1.0.0+git20241231-1 has caused the Debian Bug report #1035254, regarding singularity: please add autopkgtests (to add coverage for python3-numpy) to be marked as done. This means

Bug#1098217: marked as done (singularity: doesn't work with Numpy 2)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sun, 23 Feb 2025 07:05:25 + with message-id and subject line Bug#1098217: fixed in singularity 1.0.0+git20241231-1 has caused the Debian Bug report #1098217, regarding singularity: doesn't work with Numpy 2 to be marked as done. This means that you claim that the problem ha

Bug#1098687: marked as done (libfinance-quote-perl: Unable to retrieve quotes (YahooJSON))

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sun, 23 Feb 2025 01:51:01 + with message-id and subject line Bug#1098687: fixed in libfinance-quote-perl 1.64-3 has caused the Debian Bug report #1098687, regarding libfinance-quote-perl: Unable to retrieve quotes (YahooJSON) to be marked as done. This means that you claim

Bug#1081232: marked as done (pyroon: please remove extreneaous dependency on python3-six)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 23:54:54 + with message-id and subject line Bug#1081232: fixed in pyroon 0.1.6-3 has caused the Debian Bug report #1081232, regarding pyroon: please remove extreneaous dependency on python3-six to be marked as done. This means that you claim that the proble

Bug#873278: marked as done (gdb: core/exe mismatch warning is sometimes not accurate)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 18:24:40 -0500 with message-id <87h64l1s1z@debian.org> and subject line Closing has caused the Debian Bug report #873278, regarding gdb: core/exe mismatch warning is sometimes not accurate to be marked as done. This means that you claim that the problem has

Bug#933377: marked as done (gdb: dynamically-linked programs segfault on launch)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:56:52 -0500 with message-id <874j0l37wr@debian.org> and subject line Closing has caused the Debian Bug report #933377, regarding gdb: dynamically-linked programs segfault on launch to be marked as done. This means that you claim that the problem has been

Bug#519525: marked as done (gdb: TAB expansion for class members does not work)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 18:02:37 -0500 with message-id <87zfid1t2q@debian.org> and subject line Closing has caused the Debian Bug report #519525, regarding gdb: TAB expansion for class members does not work to be marked as done. This means that you claim that the problem has been d

Bug#411244: marked as done (killall -s SIGINT gdb doesn't interrupt anymore)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:51:14 -0500 with message-id <871pvp4mql@debian.org> and subject line Closing has caused the Debian Bug report #411244, regarding killall -s SIGINT gdb doesn't interrupt anymore to be marked as done. This means that you claim that the problem has been deal

Bug#555890: marked as done (gdb: Please consider enabling Fortran90 support by merging archer-jankratochvil-vla)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:43:37 -0500 with message-id <87frk54n3a@sergiodj.net> and subject line Re: Bug#555890: gdb: Please consider enabling Fortran90 support by merging archer-jankratochvil-vla has caused the Debian Bug report #555890, regarding gdb: Please consider enabling Fo

Bug#597629: marked as done (gdb: Fortran arrays cannot be printed)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:43:37 -0500 with message-id <87frk54n3a@sergiodj.net> and subject line Re: Bug#555890: gdb: Please consider enabling Fortran90 support by merging archer-jankratochvil-vla has caused the Debian Bug report #555890, regarding gdb: Fortran arrays cannot be pr

Bug#1002672: marked as done (gdb: please remove annoying license output)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:29:21 -0500 with message-id <874j0l7gvy@debian.org> and subject line Re: Bug#1002672: gdb: please remove annoying license output has caused the Debian Bug report #1002672, regarding gdb: please remove annoying license output to be marked as done. This mea

Bug#864741: marked as done (gdb-minimal provides gdb, causing rust debuginfo-gdb tests to fail)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:46:56 -0500 with message-id <875xl14mxr@debian.org> and subject line Closing as gdb-minimal doesn't exist anymore has caused the Debian Bug report #864741, regarding gdb-minimal provides gdb, causing rust debuginfo-gdb tests to fail to be marked as done.

Bug#470256: marked as done (gdb: suggest that the user install debugging packages)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:42:01 -0500 with message-id <87jz9h4n5y@sergiodj.net> and subject line Re: Bug#470256: gdb: suggest that the user install debugging packages has caused the Debian Bug report #470256, regarding gdb: suggest that the user install debugging packages to be ma

Bug#344930: marked as done (IA64 /build/buildd/gdb-6.3/gdb/doublest.c:662: internal-error: floatformat_from_type: Assertion `TYPE_CODE (type) == TYPE_CODE_FLT' failed.)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:45:28 -0500 with message-id <87bjut4n07@debian.org> and subject line Won't fix has caused the Debian Bug report #344930, regarding IA64 /build/buildd/gdb-6.3/gdb/doublest.c:662: internal-error: floatformat_from_type: Assertion `TYPE_CODE (type) == TYPE_CO

Bug#58322: marked as done (can't "p environ")

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:35:59 -0500 with message-id <87wmdh4ng0@sergiodj.net> and subject line Re: Bug#58322: can't "p environ" has caused the Debian Bug report #58322, regarding can't "p environ" to be marked as done. This means that you claim that the problem has been dealt wi

Bug#536024: marked as done (gdb gets wrong address for glibc optind variable)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:35:59 -0500 with message-id <87wmdh4ng0@sergiodj.net> and subject line Re: Bug#58322: can't "p environ" has caused the Debian Bug report #58322, regarding gdb gets wrong address for glibc optind variable to be marked as done. This means that you claim tha

Bug#231116: marked as done (gdb: env var so programs can tell if being debugged)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:32:52 -0500 with message-id <87zfid625n@sergiodj.net> and subject line Re: Bug#231116: how to implement without changing gdb has caused the Debian Bug report #231116, regarding gdb: env var so programs can tell if being debugged to be marked as done. This

Processed: closing 1087980

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1087980 6.1.90-1 Bug #1087980 [src:linux] linux-image-5.10.0-32-686-pae: does not boot on Atom D525 Marked as fixed in versions linux/6.1.90-1. Bug #1087980 [src:linux] linux-image-5.10.0-32-686-pae: does not boot on Atom D525 Marked Bug a

Processed: RFS: cglm/0.9.6-1 -- Optimized OpenGL Mathematics library for C

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1095905 Bug #1095905 [sponsorship-requests] RFS: cglm/0.9.6-1 -- Optimized OpenGL Mathematics library for C Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1095905: https://bugs.debian.org/

Bug#1098690: marked as done (adduser: Upgrade of network manager is failing due to missing API call in adduser)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 21:34:10 + with message-id and subject line Bug#1098690: fixed in adduser 3.141 has caused the Debian Bug report #1098690, regarding adduser: Upgrade of network manager is failing due to missing API call in adduser to be marked as done. This means that you

Bug#1098692: marked as done (adduser: Undefined subroutine &Debian::AdduserLogging::textdomain called)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 21:34:10 + with message-id and subject line Bug#1098692: fixed in adduser 3.141 has caused the Debian Bug report #1098692, regarding adduser: Undefined subroutine &Debian::AdduserLogging::textdomain called to be marked as done. This means that you claim th

Bug#1098690: marked as done (adduser: Upgrade of network manager is failing due to missing API call in adduser)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 21:34:10 + with message-id and subject line Bug#1098692: fixed in adduser 3.141 has caused the Debian Bug report #1098692, regarding adduser: Upgrade of network manager is failing due to missing API call in adduser to be marked as done. This means that you

Bug#1098692: marked as done (adduser: Undefined subroutine &Debian::AdduserLogging::textdomain called)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 21:34:10 + with message-id and subject line Bug#1098690: fixed in adduser 3.141 has caused the Debian Bug report #1098690, regarding adduser: Undefined subroutine &Debian::AdduserLogging::textdomain called to be marked as done. This means that you claim th

Bug#1098609: marked as done (python-renault-api: FTBFS: E assert 2 == 0)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 20:49:52 + with message-id and subject line Bug#1098609: fixed in python-renault-api 0.2.9-2 has caused the Debian Bug report #1098609, regarding python-renault-api: FTBFS: E assert 2 == 0 to be marked as done. This means that you claim that the probl

Bug#793376: marked as done (su-to-root: higher priority for kdesudo and gksudo)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 21:57:53 +0100 with message-id and subject line Re: Bug#793376: su-to-root: higher priority for kdesudo and gksudo has caused the Debian Bug report #793376, regarding su-to-root: higher priority for kdesudo and gksudo to be marked as done. This means that you

Bug#1098510: marked as done (libbcmatroska2-dev: Wrong INTERFACE_INCLUDE_DIRECTORIES)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 20:43:27 + with message-id and subject line Bug#1098510: fixed in bcmatroska2 5.3.101-2 has caused the Debian Bug report #1098510, regarding libbcmatroska2-dev: Wrong INTERFACE_INCLUDE_DIRECTORIES to be marked as done. This means that you claim that the pro

Bug#1074170: marked as done (linux: missing 5.10 backport of pfn_valid() changes from f6564fce256a3944aa1bc76cb3c40e792d97c1eb ?)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 21:17:07 +0100 with message-id and subject line Re: Bug#1074170: linux: missing 5.10 backport of pfn_valid() changes from f6564fce256a3944aa1bc76cb3c40e792d97c1eb ? has caused the Debian Bug report #1074170, regarding linux: missing 5.10 backport of pfn_valid()

Bug#1098414: marked as done (lua-ldap in debian stable segfaults on ldapsearch)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 20:15:06 + with message-id <29388931-469b-4c00-b9e1-aaf12693a...@torreviejawireless.org> and subject line Fwd: lua-ldap_1.4.0-1~bpo12+1_amd64.changes ACCEPTED into stable-backports has caused the Debian Bug report #1098414, regarding lua-ldap in debian stabl

Bug#1084134: marked as done (python3-dogtail: sniff fails to start on Wayland (No module named 'ponytail'))

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:34:28 + with message-id and subject line Bug#1084134: fixed in dogtail 1.0.0-5 has caused the Debian Bug report #1084134, regarding python3-dogtail: sniff fails to start on Wayland (No module named 'ponytail') to be marked as done. This means that you c

Bug#1098543: marked as done (dogtail: FTBFS: ModuleNotFoundError: No module named 'cairo')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:34:28 + with message-id and subject line Bug#1098543: fixed in dogtail 1.0.0-5 has caused the Debian Bug report #1098543, regarding dogtail: FTBFS: ModuleNotFoundError: No module named 'cairo' to be marked as done. This means that you claim that the prob

Bug#1095894: marked as done (lua-system: The fork used is outdated)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:37:49 + with message-id and subject line Bug#1095894: fixed in lua-system 0.4.5-1 has caused the Debian Bug report #1095894, regarding lua-system: The fork used is outdated to be marked as done. This means that you claim that the problem has been dealt w

Bug#1045631: marked as done (onetbb: Fails to build source after successful build)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:05:25 + with message-id and subject line Bug#1045631: fixed in onetbb 2022.0.0-2 has caused the Debian Bug report #1045631, regarding onetbb: Fails to build source after successful build to be marked as done. This means that you claim that the problem ha

Bug#1098364: marked as done (ITP: aiohttp-asyncmdnsresolver -- Async resolver for aiohttp supporting mDNS queries)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:00:10 + with message-id and subject line Bug#1098364: fixed in aiohttp-asyncmdnsresolver 0.1.1-1 has caused the Debian Bug report #1098364, regarding ITP: aiohttp-asyncmdnsresolver -- Async resolver for aiohttp supporting mDNS queries to be marked as don

Bug#1098505: marked as done (ITP: clatd -- CLAT and SIIT-DC ER with many XLAT engines)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:00:11 + with message-id and subject line Bug#1098505: fixed in clatd 2.0.0-1 has caused the Debian Bug report #1098505, regarding ITP: clatd -- CLAT and SIIT-DC ER with many XLAT engines to be marked as done. This means that you claim that the problem ha

Bug#1013345: marked as done (ITP: west -- Description: meta tool for Zephyr RTOS)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:00:28 + with message-id and subject line Bug#1013345: fixed in west 1.3.0-1 has caused the Debian Bug report #1013345, regarding ITP: west -- Description: meta tool for Zephyr RTOS to be marked as done. This means that you claim that the problem has been

Bug#1095308: marked as done (ITP: golang-github-crawshaw-sqlite -- Go SQLite3 driver)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:00:21 + with message-id and subject line Bug#1095308: fixed in golang-github-go-llsqlite-crawshaw 0.5.5-1 has caused the Debian Bug report #1095308, regarding ITP: golang-github-crawshaw-sqlite -- Go SQLite3 driver to be marked as done. This means that

Bug#1093250: marked as done (ITP: golang-github-invopop-jsonschema -- Generate JSON Schemas from Go types)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:00:21 + with message-id and subject line Bug#1093250: fixed in golang-github-invopop-jsonschema 0.13.0-1 has caused the Debian Bug report #1093250, regarding ITP: golang-github-invopop-jsonschema -- Generate JSON Schemas from Go types to be marked as don

Bug#1091355: marked as done (rust-pollster: unsatisfiable dependency librust-pollster-macro-0.4)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 19:00:27 + with message-id and subject line Bug#1091355: fixed in rust-pollster-macro 0.4.0-1 has caused the Debian Bug report #1091355, regarding rust-pollster: unsatisfiable dependency librust-pollster-macro-0.4 to be marked as done. This means that you c

Bug#1098629: marked as done (sphinx-theme-builder: FTBFS: E TypeError: CliRunner.__init__() got an unexpected keyword argument 'mix_stderr')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 18:51:07 + with message-id and subject line Bug#1098629: fixed in sphinx-theme-builder 0.2.0b2-5 has caused the Debian Bug report #1098629, regarding sphinx-theme-builder: FTBFS: E TypeError: CliRunner.__init__() got an unexpected keyword argument 'mi

Processed: control

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1015683 2022.0.0-1 Bug #1015683 [src:onetbb] tbb: ftbfs with LTO (link time optimization) enabled Marked as fixed in versions onetbb/2022.0.0-1. > close 1015683 Bug #1015683 [src:onetbb] tbb: ftbfs with LTO (link time optimization) enabled M

Bug#1098617: marked as done (python-yamlfix: FTBFS: E TypeError: CliRunner.__init__() got an unexpected keyword argument 'mix_stderr')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 20:33:14 +0200 with message-id and subject line Fixed in version 1.17.0-4 has caused the Debian Bug report #1098617, regarding python-yamlfix: FTBFS: E TypeError: CliRunner.__init__() got an unexpected keyword argument 'mix_stderr' to be marked as done.

Bug#1096399: marked as done (bvi: ftbfs with GCC-15)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 18:19:28 + with message-id and subject line Bug#1096399: fixed in bvi 1.4.2-3 has caused the Debian Bug report #1096399, regarding bvi: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Processed: control

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 746376 Bug #746376 [src:onetbb] tbb support for kfreebsd-* and hurd-i386? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 746376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746376 D

Processed: control

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 762655 2022.0.0-1 Bug #762655 [src:onetbb] assertion (EBX & rtm_ebx_mask)!=0: failed Marked as fixed in versions onetbb/2022.0.0-1. > close 762655 Bug #762655 [src:onetbb] assertion (EBX & rtm_ebx_mask)!=0: failed Marked Bug as done > thanks

Processed: control

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 997804 2021.5.0-1 Bug #997804 [src:onetbb] libstdc++-11-dev: Link error when libtbb-dev is installed Marked as fixed in versions onetbb/2021.5.0-1. > close 997804 Bug #997804 [src:onetbb] libstdc++-11-dev: Link error when libtbb-dev is ins

Bug#1098388: marked as done (shairport-sync: New upstream release (4.3.7) available)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 17:46:34 + with message-id and subject line Re: Bug#1098388: fixed in shairport-sync 4.3.7-1 has caused the Debian Bug report #1098388, regarding shairport-sync: New upstream release (4.3.7) available to be marked as done. This means that you claim that the

Processed: control

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1025779 2022.0.0-1 Bug #1025779 [src:onetbb] onetbb: Please add patch to add support for ia64 Marked as fixed in versions onetbb/2022.0.0-1. > close 1025779 Bug #1025779 [src:onetbb] onetbb: Please add patch to add support for ia64 Marked Bu

Bug#1098267: marked as done (dns-root-data: root.key needs updating)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 18:28:54 +0100 with message-id and subject line Re: Bug#1098267: dns-root-data: root.key needs updating has caused the Debian Bug report #1098267, regarding dns-root-data: root.key needs updating to be marked as done. This means that you claim that the problem

Bug#1091496: marked as done (dns-root-data: will FTBFS during trixie support period)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 18:20:12 +0100 with message-id and subject line Re: Bug#1091496: dns-root-data: will FTBFS during trixie support period has caused the Debian Bug report #1091496, regarding dns-root-data: will FTBFS during trixie support period to be marked as done. This means

Processed: closing 1079461

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1079461 20250116-1 Bug #1079461 {Done: Marco d'Itri } [rpki-trust-anchors] [INTL:sv] Swedish strings for rpki-trust-anchors debconf Marked as fixed in versions rpki-trust-anchors/20250116-1; no longer marked as fixed in versions 20250116-1

Bug#827078: marked as done (baobab: invalid mime-types / baobab opens for inode/directory)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 16:35:31 + with message-id and subject line Bug#827078: fixed in baobab 48~alpha-1 has caused the Debian Bug report #827078, regarding baobab: invalid mime-types / baobab opens for inode/directory to be marked as done. This means that you claim that the pro

Bug#1096217: marked as done (rust-gtk4: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 16:06:02 + with message-id and subject line Bug#1096217: fixed in rust-gtk4 0.9.6-1 has caused the Debian Bug report #1096217, regarding rust-gtk4: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be marked as done. Th

Bug#1098608: marked as done (python-recipe-scrapers: FTBFS: AssertionError: Exception not raised : .instructions_list() was expected to raise an exception but it did not.)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 16:02:46 + with message-id and subject line Bug#1098608: fixed in python-recipe-scrapers 15.5.1-1 has caused the Debian Bug report #1098608, regarding python-recipe-scrapers: FTBFS: AssertionError: Exception not raised : .instructions_list() was expected to

Processed: reopening 1098505, closing 1098490, archiving 1098490

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1098505 Bug #1098505 {Done: ba...@debian.org} [wnpp] ITP: clatd -- CLAT and SIIT-DC ER with many XLAT engines Bug reopened Ignoring request to alter fixed versions of bug #1098505 to the same values previously set > close 1098490 Bug #109

Bug#924985: marked as done (Updating the libhtml-autopagerize-perl Uploaders list)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:54:54 + with message-id and subject line Bug#924985: fixed in libhtml-autopagerize-perl 0.02-2 has caused the Debian Bug report #924985, regarding Updating the libhtml-autopagerize-perl Uploaders list to be marked as done. This means that you claim that

Bug#1097859: marked as done (scitokens-cpp: ftbfs with GCC-15)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:12:08 + with message-id and subject line Bug#1097859: fixed in scitokens-cpp 1.1.2-2 has caused the Debian Bug report #1097859, regarding scitokens-cpp: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1098071: marked as done (voms: ftbfs with GCC-15)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:15:37 + with message-id and subject line Bug#1098071: fixed in voms 2.1.0-2 has caused the Debian Bug report #1098071, regarding voms: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1084138: marked as done (rust-axum: Please update to 0.7)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:10:53 + with message-id and subject line Bug#1084138: fixed in rust-axum 0.7.9-1 has caused the Debian Bug report #1084138, regarding rust-axum: Please update to 0.7 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1097948: marked as done (sunclock: ftbfs with GCC-15)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:13:02 + with message-id and subject line Bug#1097948: fixed in sunclock 3.57-14 has caused the Debian Bug report #1097948, regarding sunclock: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1098610: marked as done (python-scciclient: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:09:36 + with message-id and subject line Bug#1098610: fixed in python-pysnmp4 4.4.12-3 has caused the Debian Bug report #1098610, regarding python-scciclient: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets' to be marked as done. This

Bug#1098606: marked as done (python-pysmi-lextudio: FTBFS: E ModuleNotFoundError: No module named 'pyasn1.compat.octets')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:09:36 + with message-id and subject line Bug#1098606: fixed in python-pysnmp4 4.4.12-3 has caused the Debian Bug report #1098606, regarding python-pysmi-lextudio: FTBFS: E ModuleNotFoundError: No module named 'pyasn1.compat.octets' to be marked as done

Bug#1098605: marked as done (python-proliantutils: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:09:36 + with message-id and subject line Bug#1098605: fixed in python-pysnmp4 4.4.12-3 has caused the Debian Bug report #1098605, regarding python-proliantutils: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets' to be marked as done. Th

Bug#1098568: marked as done (ironic: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:09:36 + with message-id and subject line Bug#1098568: fixed in python-pysnmp4 4.4.12-3 has caused the Debian Bug report #1098568, regarding ironic: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets' to be marked as done. This means that

Bug#1098604: marked as done (python-pyasn1-modules: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:09:25 + with message-id and subject line Bug#1098604: fixed in python-pyasn1-modules 0.4.1-2 has caused the Debian Bug report #1098604, regarding python-pyasn1-modules: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets' to be marked as do

Bug#1098592: marked as done (pysmi: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets')

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:09:36 + with message-id and subject line Bug#1098592: fixed in python-pysnmp4 4.4.12-3 has caused the Debian Bug report #1098592, regarding pysmi: FTBFS: ModuleNotFoundError: No module named 'pyasn1.compat.octets' to be marked as done. This means that y

Bug#1098665: marked as done (mailscripts: please update suggests from python3-notmuch to python3-notmuch2)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 15:04:16 + with message-id and subject line Bug#1098665: fixed in mailscripts 30-2 has caused the Debian Bug report #1098665, regarding mailscripts: please update suggests from python3-notmuch to python3-notmuch2 to be marked as done. This means that you c

Bug#1040754: marked as done (chromium: Enable GTK4 backend to use IME for Wayland window)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 22:51:21 +0900 with message-id and subject line Re: Bug#1040754: chromium: Enable GTK4 backend to use IME for Wayland window has caused the Debian Bug report #1040754, regarding chromium: Enable GTK4 backend to use IME for Wayland window to be marked as done.

Bug#1093362: marked as done (thunderbird: FTBFS: According to "pip check", the current Python environment has package-compatibility issues.)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:48:29 + with message-id and subject line Bug#1093362: fixed in thunderbird 1:128.7.0esr-1 has caused the Debian Bug report #1093362, regarding thunderbird: FTBFS: According to "pip check", the current Python environment has package-compatibility issues.

Bug#1096178: marked as done (aptly: Segfault with database corruption on arm64)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 14:37:33 +0100 with message-id <871pvq85ia@g8.befour.org> and subject line Incorrect report has caused the Debian Bug report #1096178, regarding aptly: Segfault with database corruption on arm64 to be marked as done. This means that you claim that the proble

Processed: Re: cinnamon-control-center: Cinnamon Control Center won't load at all in Debian Sid

2025-02-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #1098398 [cinnamon-control-center] cinnamon-control-center: Cinnamon Control Center won't load at all in Debian Sid. This needs to be sorted out. Marked Bug as done -- 1098398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098398 Debian Bug Track

Bug#1096058: marked as done (linux-image-6.12.12-amd64: Please set CONFIG_INTEL_MEI_GSC_PROXY=m)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:10 + with message-id and subject line Bug#1096058: fixed in linux 6.12.16-1 has caused the Debian Bug report #1096058, regarding linux-image-6.12.12-amd64: Please set CONFIG_INTEL_MEI_GSC_PROXY=m to be marked as done. This means that you claim that th

Bug#1027306: marked as done (linux-kbuild-6.0: missing `resolve_btfids` and some scripts)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:10 + with message-id and subject line Bug#1093655: fixed in linux 6.12.16-1 has caused the Debian Bug report #1093655, regarding linux-kbuild-6.0: missing `resolve_btfids` and some scripts to be marked as done. This means that you claim that the probl

Bug#962708: marked as done (Please build dummy_hcd and g_mass_storage modules)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:10 + with message-id and subject line Bug#962708: fixed in linux 6.12.16-1 has caused the Debian Bug report #962708, regarding Please build dummy_hcd and g_mass_storage modules to be marked as done. This means that you claim that the problem has been

Bug#1093655: marked as done (linux-kbuild-6.12.5: Include tools/bpf/resolve_btfids in linux-kbuild package)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:10 + with message-id and subject line Bug#1093655: fixed in linux 6.12.16-1 has caused the Debian Bug report #1093655, regarding linux-kbuild-6.12.5: Include tools/bpf/resolve_btfids in linux-kbuild package to be marked as done. This means that you c

Bug#1094755: marked as done (linux: dubious CONFIG_SND_HDA_POWER_SAVE_DEFAULT=1)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:10 + with message-id and subject line Bug#1094755: fixed in linux 6.12.16-1 has caused the Debian Bug report #1094755, regarding linux: dubious CONFIG_SND_HDA_POWER_SAVE_DEFAULT=1 to be marked as done. This means that you claim that the problem has be

Bug#1072900: marked as done (ITP: qt6-quickeffectmaker -- Qt 6 Quick Effect Maker)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:22 + with message-id and subject line Bug#1072900: fixed in qt6-quickeffectmaker 6.8.2-1 has caused the Debian Bug report #1072900, regarding ITP: qt6-quickeffectmaker -- Qt 6 Quick Effect Maker to be marked as done. This means that you claim that the

Bug#1027304: marked as done (linux-kbuild-6.0: missing `resolve_btfids` and some scripts)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 13:00:10 + with message-id and subject line Bug#1093655: fixed in linux 6.12.16-1 has caused the Debian Bug report #1093655, regarding linux-kbuild-6.0: missing `resolve_btfids` and some scripts to be marked as done. This means that you claim that the probl

Bug#1080808: marked as done (Missing Build-Depends on python3-setuptools)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:21:12 + with message-id and subject line Bug#1080808: fixed in squaremap 1:1.0.5-2.1 has caused the Debian Bug report #1080808, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem has bee

Bug#970834: marked as done (python3-notmuch: Segfault in pwnm-sync)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:49:11 + with message-id and subject line Bug#970834: fixed in notmuch 0.39~rc0-1 has caused the Debian Bug report #970834, regarding python3-notmuch: Segfault in pwnm-sync to be marked as done. This means that you claim that the problem has been dealt wi

Bug#749890: marked as done (python3-notmuch: missing header in mbox message -> NullPointerError)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:49:11 + with message-id and subject line Bug#749890: fixed in notmuch 0.39~rc0-1 has caused the Debian Bug report #749890, regarding python3-notmuch: missing header in mbox message -> NullPointerError to be marked as done. This means that you claim that

Bug#893057: marked as done (python3-notmuch: random aborts on exit)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:49:11 + with message-id and subject line Bug#893057: fixed in notmuch 0.39~rc0-1 has caused the Debian Bug report #893057, regarding python3-notmuch: random aborts on exit to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1092047: marked as done (notmuch: saving draft causing missing header fields)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:49:11 + with message-id and subject line Bug#1092047: fixed in notmuch 0.39~rc0-1 has caused the Debian Bug report #1092047, regarding notmuch: saving draft causing missing header fields to be marked as done. This means that you claim that the problem ha

Bug#1098415: marked as done (python3-pampy: missed python3-six dependency)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:34:43 + with message-id and subject line Bug#1098415: fixed in python-pampy 2.0.2-2 has caused the Debian Bug report #1098415, regarding python3-pampy: missed python3-six dependency to be marked as done. This means that you claim that the problem has bee

Bug#1080849: marked as done (Missing Build-Depends on python3-setuptools)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:34:30 + with message-id and subject line Bug#1080849: fixed in med-fichier 4.1.0+repack-9 has caused the Debian Bug report #1080849, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem ha

Bug#1080663: marked as done (Missing Build-Depends on python3-setuptools)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:20:34 + with message-id and subject line Bug#1080663: fixed in logging-tree 1.9-1.2 has caused the Debian Bug report #1080663, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem has been

Bug#1080762: marked as done (Missing Build-Depends on python3-setuptools)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:05:36 + with message-id and subject line Bug#1080762: fixed in python-pyahocorasick 1.4.1-2 has caused the Debian Bug report #1080762, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem

Bug#1097132: marked as done (crun: FTBFS on i386: build-dependency not installable: libcriu-dev)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 12:05:27 + with message-id and subject line Bug#1097132: fixed in crun 1.20-1 has caused the Debian Bug report #1097132, regarding crun: FTBFS on i386: build-dependency not installable: libcriu-dev to be marked as done. This means that you claim that the pr

Bug#1080783: marked as done (Missing Build-Depends on python3-setuptools)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 11:50:13 + with message-id and subject line Bug#1080783: fixed in qt-material 2.14-2 has caused the Debian Bug report #1080783, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem has been d

Processed: RFS: python-jsbeautifier/1.15.3-1 -- JavaScript unobfuscator and beautifier

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1098653 Bug #1098653 [sponsorship-requests] RFS: python-jsbeautifier/1.15.3-1 -- JavaScript unobfuscator and beautifier Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1098653: https://bugs

Bug#1080567: marked as done (Missing Build-Depends on python3-setuptools)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 11:49:29 + with message-id and subject line Bug#1080567: fixed in cbflib 0.9.7+dfsg1-5 has caused the Debian Bug report #1080567, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem has been

Processed: closing 1086785

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1086785 Bug #1086785 [adduser] slashes in user name allowed, but slashes in home dirs not Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1086785: https://bugs.debian.org/cgi-bin/bugrepor

Processed: closing 541728

2025-02-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 541728 Bug #541728 [adduser] several minor improvement ideas Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 541728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541728 Debian Bug Tra

Bug#1098562: marked as done (golang-github-protonmail-go-crypto: FTBFS: clearsign_test.go:203: cannot create key: rsa: generated p == q, random source is broken)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 11:05:28 + with message-id and subject line Bug#1098562: fixed in golang-github-protonmail-go-crypto 1.1.5-2 has caused the Debian Bug report #1098562, regarding golang-github-protonmail-go-crypto: FTBFS: clearsign_test.go:203: cannot create key: rsa: gene

Bug#1098450: marked as done (slm: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 11:07:28 + with message-id and subject line Bug#1098450: fixed in slm 1.32-2 has caused the Debian Bug report #1098450, regarding slm: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This means that you claim that the p

Bug#1093858: marked as done (ITS: darkice)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 10:49:24 + with message-id and subject line Bug#1093858: fixed in darkice 1.5-1 has caused the Debian Bug report #1093858, regarding ITS: darkice 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#984027: marked as done (darkice: ftbfs with GCC-11)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 10:49:24 + with message-id and subject line Bug#984027: fixed in darkice 1.5-1 has caused the Debian Bug report #984027, regarding darkice: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1059012: marked as done (recording lost/overwritten when reconnecting to stream)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 10:49:24 + with message-id and subject line Bug#1059012: fixed in darkice 1.5-1 has caused the Debian Bug report #1059012, regarding recording lost/overwritten when reconnecting to stream to be marked as done. This means that you claim that the problem has

Bug#883126: marked as done (darkice cannot connect to IPv6 icecast server)

2025-02-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Feb 2025 10:49:24 + with message-id and subject line Bug#883126: fixed in darkice 1.5-1 has caused the Debian Bug report #883126, regarding darkice cannot connect to IPv6 icecast server to be marked as done. This means that you claim that the problem has been dealt

  1   2   >