Bug#1103309: marked as done (dh-ros: FTBFS with the nocheck build profile)

Your message dated Thu, 17 Apr 2025 06:33:58 + with message-id and subject line Bug#1103309: fixed in dh-ros 0.14.2 has caused the Debian Bug report #1103309, regarding dh-ros: FTBFS with the nocheck build profile to be marked as done. This means that you claim that the problem has been dealt

Bug#1102564: marked as done (International character input broken since recent Chromium update)

Your message dated Thu, 17 Apr 2025 02:00:18 -0400 with message-id <866426af-b85f-44c0-b5ac-931f9ad38...@queued.net> and subject line Re: Bug#1102564: International character input broken since recent Chromium update has caused the Debian Bug report #1102564, regarding International character inpu

Bug#1099721: marked as done (gmtsar: Please add support for loong64)

Your message dated Thu, 17 Apr 2025 06:04:17 + with message-id and subject line Bug#1099721: fixed in gmtsar 6.5+ds-3 has caused the Debian Bug report #1099721, regarding gmtsar: Please add support for loong64 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1101152: marked as done (qemu-efi-aarch64: unable to boot arm64 kernel)

Your message dated Wed, 16 Apr 2025 22:39:21 + with message-id and subject line Bug#1101152: fixed in edk2 2025.02-7 has caused the Debian Bug report #1101152, regarding qemu-efi-aarch64: unable to boot arm64 kernel to be marked as done. This means that you claim that the problem has been dea

Bug#1015747: marked as done (libnotcurses-core-dev: missing dependency on libtinfo-dev)

Your message dated Thu, 17 Apr 2025 03:19:19 + with message-id and subject line Bug#1015747: fixed in notcurses 3.0.13+dfsg-4 has caused the Debian Bug report #1015747, regarding libnotcurses-core-dev: missing dependency on libtinfo-dev to be marked as done. This means that you claim that the

Bug#1103316: marked as done (notcurses: FTBFS with the nocheck build profile)

Your message dated Thu, 17 Apr 2025 00:22:18 + with message-id and subject line Bug#1103316: fixed in notcurses 3.0.13+dfsg-3 has caused the Debian Bug report #1103316, regarding notcurses: FTBFS with the nocheck build profile to be marked as done. This means that you claim that the problem h

Bug#279247: marked as done (FATAL: invalid command-line arguments for server process)

Your message dated Wed, 16 Apr 2025 14:57:49 -0700 with message-id <6124474.alqRGMn8q6@soren-desktop> and subject line FATAL: invalid command-line arguments for server process has caused the Debian Bug report #279247, regarding FATAL: invalid command-line arguments for server process to be marked a

Bug#1103197: marked as done (pympress: FTBFS: error: error in setup.cfg: command 'compile_catalog' has no such option 'use-fuzzy')

Your message dated Thu, 17 Apr 2025 00:51:30 + with message-id and subject line Bug#1103197: fixed in pympress 1.8.5-3 has caused the Debian Bug report #1103197, regarding pympress: FTBFS: error: error in setup.cfg: command 'compile_catalog' has no such option 'use-fuzzy' to be marked as done

Bug#1103184: marked as done (cairosvg: FTBFS: dh_install: warning: Cannot find (any matches for) "usr/bin/cairosvg")

Your message dated Thu, 17 Apr 2025 00:49:10 + with message-id and subject line Bug#1103184: fixed in cairosvg 2.7.1-2 has caused the Debian Bug report #1103184, regarding cairosvg: FTBFS: dh_install: warning: Cannot find (any matches for) "usr/bin/cairosvg" to be marked as done. This means

Processed: RFP: bees -- Deduplication daemon for the BTRFS filesystem

Processing commands for cont...@bugs.debian.org: > close 1103389 Bug #1103389 [wnpp] RFP: bees -- Deduplication daemon for the BTRFS filesystem Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1103389: https://bugs.debian.org/cgi-bin/bugreport.cgi?

Bug#1076292: marked as done (qt6-base: CVE-2024-39936)

Your message dated Thu, 17 Apr 2025 00:16:20 +0200 with message-id <4977519.GXAFRqVoOG@treadstone-71> and subject line has caused the Debian Bug report #1076292, regarding qt6-base: CVE-2024-39936 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1103317: marked as done (lomiri-online-accounts: FTBFS with the nocheck build profile)

Your message dated Wed, 16 Apr 2025 22:20:34 + with message-id and subject line Bug#1103317: fixed in lomiri-online-accounts 0.16-3 has caused the Debian Bug report #1103317, regarding lomiri-online-accounts: FTBFS with the nocheck build profile to be marked as done. This means that you claim

Bug#1103127: marked as done (node-webfont: FTBFS in testing/i386: dh_auto_test: error: cd ./svgicons2svgfont && sh -ex ../debian/nodejs/svgicons2svgfont/test returned exit code 139)

Your message dated Wed, 16 Apr 2025 22:06:21 + with message-id and subject line Bug#1103127: fixed in node-webfont 11.4.0+dfsg2+~cs35.7.26-13 has caused the Debian Bug report #1103127, regarding node-webfont: FTBFS in testing/i386: dh_auto_test: error: cd ./svgicons2svgfont && sh -ex ../debia

Bug#1056351: marked as done (dicod: wrong quotes in MediaWiki snippets in `/etc/dicod.conf`)

Your message dated Wed, 16 Apr 2025 22:04:35 + with message-id and subject line Bug#1056351: fixed in dico 2.12-2 has caused the Debian Bug report #1056351, regarding dicod: wrong quotes in MediaWiki snippets in `/etc/dicod.conf` to be marked as done. This means that you claim that the proble

Bug#1101651: marked as done (msmtp: Update/add debconf template translation [INTL:ca])

Your message dated Wed, 16 Apr 2025 22:05:34 + with message-id and subject line Bug#1101651: fixed in msmtp 1.8.28-3 has caused the Debian Bug report #1101651, regarding msmtp: Update/add debconf template translation [INTL:ca] to be marked as done. This means that you claim that the problem h

Bug#369323: marked as done (Courier-authmysql incompatibility with MySQL 5)

Your message dated Wed, 16 Apr 2025 14:58:45 -0700 with message-id <2242073.C4sosBPzcN@soren-desktop> and subject line Courier-authmysql incompatibility with MySQL 5 has caused the Debian Bug report #369323, regarding Courier-authmysql incompatibility with MySQL 5 to be marked as done. This means

Bug#268298: marked as done (After upgrading from a previous version on debian/alpha the user auth with psql doesn't work anymore )

Your message dated Wed, 16 Apr 2025 14:54:25 -0700 with message-id <1956135.IobQ9Gjlxr@soren-desktop> and subject line After upgrading from a previous version on debian/alpha the user auth with psql doesn't work anymore has caused the Debian Bug report #268298, regarding After upgrading from a pre

Bug#922199: marked as done (courier-imap: Upgrade broken on non-systemd installations)

Your message dated Wed, 16 Apr 2025 14:51:45 -0700 with message-id <3698922.hdfAi7Kttb@soren-desktop> and subject line Re: Bug#922199: courier-imap: Upgrade broken on non-systemd installations has caused the Debian Bug report #922199, regarding courier-imap: Upgrade broken on non-systemd installat

Bug#208265: marked as done (courier-authdaemon bug in sarge)

Your message dated Wed, 16 Apr 2025 14:46:32 -0700 with message-id <2256542.1BCLMh4Saa@soren-desktop> and subject line courier-authdaemon bug in sarge has caused the Debian Bug report #208265, regarding courier-authdaemon bug in sarge to be marked as done. This means that you claim that the proble

Bug#906137: marked as done (courier-authlib-pipe: authdaemon passes the socket FD to the authProg worker, causing an usuccessful close for the first connecting client)

Your message dated Wed, 16 Apr 2025 14:44:27 -0700 with message-id <3306847.aV6nBDHxoP@soren-desktop> and subject line courier-authlib-pipe: authdaemon passes the socket FD to the authProg worker, causing an usuccessful close for the first connecting client has caused the Debian Bug report #906137

Bug#979816: marked as done (authdaemon fails in any other init system choice)

Your message dated Wed, 16 Apr 2025 14:45:28 -0700 with message-id <2910293.88bMQJbFj6@soren-desktop> and subject line authdaemon fails in any other init system choice has caused the Debian Bug report #979816, regarding authdaemon fails in any other init system choice to be marked as done. This me

Bug#256231: marked as done (PAM session module not called, or doing chdir too early)

Your message dated Wed, 16 Apr 2025 14:41:56 -0700 with message-id <4618205.8F6SAcFxjW@soren-desktop> and subject line PAM session module not called, or doing chdir too early has caused the Debian Bug report #256231, regarding PAM session module not called, or doing chdir too early to be marked as

Bug#1103310: marked as done (emacspeak: FTBFS with the nocheck build profile)

Your message dated Wed, 16 Apr 2025 21:36:07 + with message-id and subject line Bug#1103310: fixed in emacspeak 53.0+dfsg-5 has caused the Debian Bug report #1103310, regarding emacspeak: FTBFS with the nocheck build profile to be marked as done. This means that you claim that the problem has

Bug#1099630: marked as done (weechat-scripts: depends on base-files)

Your message dated Wed, 16 Apr 2025 21:24:03 + with message-id and subject line Bug#1099630: fixed in weechat-scripts 20250416-1 has caused the Debian Bug report #1099630, regarding weechat-scripts: depends on base-files to be marked as done. This means that you claim that the problem has

Bug#1098090: marked as done (weechat: ftbfs with GCC-15)

Your message dated Wed, 16 Apr 2025 21:23:52 + with message-id and subject line Bug#1098090: fixed in weechat 4.6.1-1 has caused the Debian Bug report #1098090, regarding weechat: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1102450: marked as done (weechat: upgrade to version 4.6.0)

Your message dated Wed, 16 Apr 2025 21:23:52 + with message-id and subject line Bug#1102450: fixed in weechat 4.6.1-1 has caused the Debian Bug report #1102450, regarding weechat: upgrade to version 4.6.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1100850: marked as done (gsequencer: documentation links to expired, domain-squatted libsoup.org)

Your message dated Wed, 16 Apr 2025 20:36:11 + with message-id and subject line Bug#1100850: fixed in gsequencer 7.7.5-1 has caused the Debian Bug report #1100850, regarding gsequencer: documentation links to expired, domain-squatted libsoup.org to be marked as done. This means that you clai

Bug#1103330: marked as done (sra-sdk: FTBFS with the nocheck build profile)

Your message dated Wed, 16 Apr 2025 20:59:07 + with message-id and subject line Bug#1103330: fixed in sra-sdk 3.2.1+dfsg-4 has caused the Debian Bug report #1103330, regarding sra-sdk: FTBFS with the nocheck build profile to be marked as done. This means that you claim that the problem has be

Bug#1034279: marked as done (courier: [INTL:tr] turkish translation of debconf messages)

Your message dated Wed, 16 Apr 2025 13:47:34 -0700 with message-id <6791473.4vTCxPXJkl@soren-desktop> and subject line courier: [INTL:tr] turkish translation of debconf messages has caused the Debian Bug report #1034279, regarding courier: [INTL:tr] turkish translation of debconf messages to be mar

Bug#338385: marked as done (courier: [INTL:sv] Swedish PO-template translation)

Your message dated Wed, 16 Apr 2025 13:41:56 -0700 with message-id <2145760.KlZ2vcFHjT@soren-desktop> and subject line courier: [INTL:sv] Swedish PO-template translation has caused the Debian Bug report #338385, regarding courier: [INTL:sv] Swedish PO-template translation to be marked as done. Thi

Bug#1103288: marked as done (courier-mta: add build-dependency on ca-certificates to make build reproducible)

Your message dated Wed, 16 Apr 2025 20:34:43 + with message-id and subject line Bug#1103288: fixed in courier 1.4.1-1 has caused the Debian Bug report #1103288, regarding courier-mta: add build-dependency on ca-certificates to make build reproducible to be marked as done. This means that you

Bug#1102516: marked as done (yubikey-manager_5.6.1-1_all-buildd.changes REJECTED)

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1102516: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1102516, regarding yubikey-manager_5.6.1-1_all-buildd.changes REJECTED to be marked as done. This means that you claim that t

Bug#1103039: marked as done (ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade)

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103039: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103039, regarding ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade to be m

Bug#1103022: marked as done (qt6-base: CVE-2025-3512)

Your message dated Wed, 16 Apr 2025 19:52:02 + with message-id and subject line Bug#1103022: fixed in qt6-base 6.8.2+dfsg-6 has caused the Debian Bug report #1103022, regarding qt6-base: CVE-2025-3512 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1103211: marked as done (yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext')

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103039: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103039, regarding yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' to be marked

Processed: closing 1037010

Processing commands for cont...@bugs.debian.org: > close 1037010 0.27.1-2 Bug #1037010 [python3-levenshtein] python3-levenshtein: pip does not recognize that apt package python3-levenshtein is installed Marked as fixed in versions python-levenshtein/0.27.1-2. Bug #1037010 [python3-levenshtein] py

Bug#1103211: marked as done (yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext')

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103211: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103211, regarding yubikey-manager: FTBFS: E ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' to be marked

Bug#1103039: marked as done (ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade)

Your message dated Wed, 16 Apr 2025 19:39:50 + with message-id and subject line Bug#1103211: fixed in yubikey-manager 5.6.1+repack1-1 has caused the Debian Bug report #1103211, regarding ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext' since 2.2.1-2 to 2.2.2-1 upgrade to be m

Bug#1103354: marked as done (TypeError: OsmGpsMap.MapTrack.add_point() takes exactly 2 arguments (1 given))

Your message dated Wed, 16 Apr 2025 18:35:15 + with message-id and subject line Bug#1103354: fixed in osm-gps-map 1.2.0-4 has caused the Debian Bug report #1103354, regarding TypeError: OsmGpsMap.MapTrack.add_point() takes exactly 2 arguments (1 given) to be marked as done. This means that y

Bug#1100539: marked as done (Is Lintian maintained maintained in a backwards incompatible way? Should stable releases use old Lintian versions?)

Your message dated Wed, 16 Apr 2025 14:48:03 -0400 with message-id <2a9270b5-bcf2-411c-8009-240851eaf...@debian.org> and subject line closing bug has caused the Debian Bug report #1100539, regarding Is Lintian maintained maintained in a backwards incompatible way? Should stable releases use old Li

Bug#1103285: marked as done (RM: idseq-bench [s390x] -- ROM; Not working on s390x)

Your message dated Wed, 16 Apr 2025 17:48:01 + (UTC) with message-id and subject line Re: RM: idseq-bench [s390x] -- ROM; Not working on s390x has caused the Debian Bug report #1103285, regarding RM: idseq-bench [s390x] -- ROM; Not working on s390x to be marked as done. This means that you c

Bug#1103286: marked as done (RM: nanostat [s390x] -- ROM; Should not be provided on s390x architecture)

Your message dated Wed, 16 Apr 2025 17:55:43 + (UTC) with message-id and subject line Re: RM: nanostat [s390x] -- ROM; Should not be provided on s390x architecture has caused the Debian Bug report #1103286, regarding RM: nanostat [s390x] -- ROM; Should not be provided on s390x architecture

Bug#1095360: marked as done (nghttp2: FTBFS: Could not import extension rubydomain.rubydomain)

Your message dated Wed, 16 Apr 2025 17:50:10 + with message-id and subject line Bug#1095360: fixed in nghttp2 1.64.0-1.1 has caused the Debian Bug report #1095360, regarding nghttp2: FTBFS: Could not import extension rubydomain.rubydomain to be marked as done. This means that you claim that t

Bug#1103279: marked as done (RM: cinnamon-desktop-environment [all armel] -- RoQA; follow-up from removing cjs on armel)

Your message dated Wed, 16 Apr 2025 17:42:34 + with message-id and subject line Bug#1103279: Removed package(s) from unstable has caused the Debian Bug report #1103279, regarding RM: cinnamon-desktop-environment [all armel] -- RoQA; follow-up from removing cjs on armel to be marked as done.

Bug#1103331: marked as done (spyne: FTBFS with the nocheck build profile)

Your message dated Wed, 16 Apr 2025 17:50:23 + with message-id and subject line Bug#1103331: fixed in spyne 2.14.0-7 has caused the Debian Bug report #1103331, regarding spyne: FTBFS with the nocheck build profile to be marked as done. This means that you claim that the problem has been dealt

Bug#1102955: marked as done (kicad: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _ZN14wxTranslations27GetBestAvailableTrans

Your message dated Wed, 16 Apr 2025 13:12:15 -0400 (EDT) with message-id and subject line Fixed in 4.2.3+dfsg-2 has caused the Debian Bug report #1102955, regarding kicad: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _Z

Bug#1101305: marked as done (libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set")

Your message dated Wed, 16 Apr 2025 17:20:04 + with message-id and subject line Bug#1101305: fixed in fuse3 3.17.1+git250416-1 has caused the Debian Bug report #1101305, regarding libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set" to be marked as done. Th

Bug#1102687: marked as done (chirp: ImportError on launch related to wx package)

Your message dated Wed, 16 Apr 2025 13:12:15 -0400 (EDT) with message-id and subject line Fixed in 4.2.3+dfsg-2 has caused the Debian Bug report #1102687, regarding chirp: ImportError on launch related to wx package to be marked as done. This means that you claim that the problem has been dealt w

Bug#1102946: marked as done (python-pyepics: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined symbol: _ZN14wxTranslations27GetBestAvail

Your message dated Wed, 16 Apr 2025 13:12:15 -0400 (EDT) with message-id and subject line Fixed in 4.2.3+dfsg-2 has caused the Debian Bug report #1102946, regarding python-pyepics: FTBFS in testing: ImportError: /usr/lib/python3/dist-packages/wx/_core.cpython-313-x86_64-linux-gnu.so: undefined s

Bug#1103057: marked as done (RM: numba [armel armhf i386 mips64el ppc64el s390x] -- RoQA; upstream only supports amd64 and arm64)

Your message dated Wed, 16 Apr 2025 17:16:15 + with message-id and subject line Bug#1103057: Removed package(s) from unstable has caused the Debian Bug report #1103057, regarding RM: numba [armel armhf i386 mips64el ppc64el s390x] -- RoQA; upstream only supports amd64 and arm64 to be marked a

Bug#1103344: marked as done (RM: python-pynndescent [ppc64el] -- RoQA; numba)

Your message dated Wed, 16 Apr 2025 17:11:11 + with message-id and subject line Bug#1103344: Removed package(s) from unstable has caused the Debian Bug report #1103344, regarding RM: python-pynndescent [ppc64el] -- RoQA; numba to be marked as done. This means that you claim that the problem h

Bug#1097822: marked as done (ruby-pg-query: ftbfs with GCC-15)

Your message dated Wed, 16 Apr 2025 16:37:15 + with message-id and subject line Bug#1103336: Removed package(s) from unstable has caused the Debian Bug report #1097822, regarding ruby-pg-query: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1103336: marked as done (RM: ruby-pg-query -- ROM; unused, leaf package)

Your message dated Wed, 16 Apr 2025 16:37:12 + with message-id and subject line Bug#1103336: Removed package(s) from unstable has caused the Debian Bug report #1103336, regarding RM: ruby-pg-query -- ROM; unused, leaf package to be marked as done. This means that you claim that the problem ha

Bug#1103341: marked as done (RM: python-cogent [mips64el ppc64el s390x] -- RoQA; numba)

Your message dated Wed, 16 Apr 2025 16:36:34 + with message-id and subject line Bug#1103341: Removed package(s) from unstable has caused the Debian Bug report #1103341, regarding RM: python-cogent [mips64el ppc64el s390x] -- RoQA; numba to be marked as done. This means that you claim that the

Bug#1103342: marked as done (RM: hyperspy [ppc64el] -- RoQA; numba)

Your message dated Wed, 16 Apr 2025 16:33:35 + with message-id and subject line Bug#1103342: Removed package(s) from unstable has caused the Debian Bug report #1103342, regarding RM: hyperspy [ppc64el] -- RoQA; numba to be marked as done. This means that you claim that the problem has been de

Bug#1103343: marked as done (RM: python-loompy [mips64el ppc64el s390x] -- RoQA; numba)

Your message dated Wed, 16 Apr 2025 16:33:19 + with message-id and subject line Bug#1103343: Removed package(s) from unstable has caused the Debian Bug report #1103343, regarding RM: python-loompy [mips64el ppc64el s390x] -- RoQA; numba to be marked as done. This means that you claim that the

Bug#1103258: marked as done (dolphin: Dolphin does not restore open tabs)

Your message dated Wed, 16 Apr 2025 16:19:27 + with message-id and subject line Bug#1103258: fixed in dolphin 4:25.03.90-3 has caused the Debian Bug report #1103258, regarding dolphin: Dolphin does not restore open tabs to be marked as done. This means that you claim that the problem has been

Bug#1103212: marked as done (flatbuffers: FTBFS: /usr/lib/python3/dist-packages/setuptools/dist.py:484: SetuptoolsDeprecationWarning: Pattern '../license' cannot contain '..')

Your message dated Wed, 16 Apr 2025 16:04:30 + with message-id and subject line Bug#1103212: fixed in flatbuffers 23.5.26+dfsg-4 has caused the Debian Bug report #1103212, regarding flatbuffers: FTBFS: /usr/lib/python3/dist-packages/setuptools/dist.py:484: SetuptoolsDeprecationWarning: Patte

Processed: close #1102489

Processing commands for cont...@bugs.debian.org: > fixed #1102489 1.2.1-2 Bug #1102489 [wnpp] ITP: jome -- keyboard centric emoji picker There is no source info for the package 'wnpp' at version '1.2.1-2' with architecture '' Unable to make a source version for version '1.2.1-2' Marked as fixed i

Bug#1101947: marked as done (firebuild: [INTL:pt] Portuguese translation - debconf messages)

Your message dated Wed, 16 Apr 2025 14:36:23 + with message-id and subject line Bug#1101947: fixed in firebuild 0.8.4-2 has caused the Debian Bug report #1101947, regarding firebuild: [INTL:pt] Portuguese translation - debconf messages to be marked as done. This means that you claim that the

Bug#1103337: marked as done (unblock: bornagain/22~git20250325170646.93042f5+ds3-3)

Your message dated Wed, 16 Apr 2025 13:21:35 + with message-id and subject line unblock bornagain has caused the Debian Bug report #1103337, regarding unblock: bornagain/22~git20250325170646.93042f5+ds3-3 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1103322: marked as done (python-goodvibes: FTBFS with the nocheck build profile)

Your message dated Wed, 16 Apr 2025 13:21:06 + with message-id and subject line Bug#1103322: fixed in python-goodvibes 3.2+dfsg-6 has caused the Debian Bug report #1103322, regarding python-goodvibes: FTBFS with the nocheck build profile to be marked as done. This means that you claim that th

Bug#1102779: marked as done (apktool: FTBFS: Could not resolve org.yaml:snakeyaml:1.x.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding apktool: FTBFS: Could not resolve org.yaml:snakeyaml:1.x. to be marked as done. This means that you claim th

Bug#1103193: marked as done (openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:1.1.13)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:

Bug#1103185: marked as done (clj-yaml-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.yaml:snakeyaml:jar:1.x has not been downloaded from i

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding clj-yaml-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the art

Bug#1102773: marked as done (resteasy: FTBFS: Could not resolve dependencies for project org.jboss.resteasy:resteasy-yaml-provider:jar:3.6.2.Final)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding resteasy: FTBFS: Could not resolve dependencies for project org.jboss.resteasy:resteasy-yaml-provider:jar:3.

Bug#1102777: marked as done (testng7: FTBFS: Could not find org.yaml:snakeyaml:1.33.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding testng7: FTBFS: Could not find org.yaml:snakeyaml:1.33. to be marked as done. This means that you claim that

Bug#1102778: marked as done (testng: FTBFS: [ERROR] dependency: org.yaml:snakeyaml:jar:1.x)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding testng: FTBFS: [ERROR] dependency: org.yaml:snakeyaml:jar:1.x to be marked as done. This means that you clai

Bug#1102768: marked as done (libspring-java: FTBFS: Could not resolve org.yaml:snakeyaml:1.17.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding libspring-java: FTBFS: Could not resolve org.yaml:snakeyaml:1.17. to be marked as done. This means that you

Bug#1102769: marked as done (logstash-logback-encoder: FTBFS: Could not resolve dependencies for project net.logstash.logback:logstash-logback-encoder:jar:7.2)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding logstash-logback-encoder: FTBFS: Could not resolve dependencies for project net.logstash.logback:logstash-lo

Bug#1102767: marked as done (jtreg7: FTBFS: Could not find org.yaml:snakeyaml:1.33.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jtreg7: FTBFS: Could not find org.yaml:snakeyaml:1.33. to be marked as done. This means that you claim that

Bug#1102766: marked as done (jackson-jaxrs-providers: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.jaxrs:jackson-jaxrs-yaml-provider:bundle:2.12.1)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jackson-jaxrs-providers: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.jaxrs:jacks

Bug#1102765: marked as done (jruby-maven-plugins: FTBFS: Could not resolve dependencies for project org.jruby.maven:ruby-tools:jar:3.0.1)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jruby-maven-plugins: FTBFS: Could not resolve dependencies for project org.jruby.maven:ruby-tools:jar:3.0.1

Bug#1102764: marked as done (jackson-dataformat-yaml: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:bundle:2.8.11)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding jackson-dataformat-yaml: FTBFS: Could not resolve dependencies for project com.fasterxml.jackson.dataformat:

Bug#1102762: marked as done (apache-curator: FTBFS: [ERROR] 'dependencies.dependency.version' for io.netty:netty-transport-native-epoll:jar: is missing.)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding apache-curator: FTBFS: [ERROR] 'dependencies.dependency.version' for io.netty:netty-transport-native-epoll:j

Bug#1102761: marked as done (apache-log4j2: FTBFS: Could not resolve dependencies for project org.apache.logging.log4j:log4j-core:jar:2.19.0)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding apache-log4j2: FTBFS: Could not resolve dependencies for project org.apache.logging.log4j:log4j-core:jar:2.1

Bug#1102763: marked as done (commons-configuration2: FTBFS: Could not resolve dependencies for project org.apache.commons:commons-configuration2:jar:2.11.0)

Your message dated Wed, 16 Apr 2025 13:21:28 + with message-id and subject line Bug#1102761: fixed in snakeyaml 2.0+ds+really1.33-1 has caused the Debian Bug report #1102761, regarding commons-configuration2: FTBFS: Could not resolve dependencies for project org.apache.commons:commons-config

Bug#1103291: marked as done (RM: xemacs21 -- RoQA; not in trixie; severely outdated)

Your message dated Wed, 16 Apr 2025 13:03:14 +0100 with message-id and subject line Re: Bug#1103291: RM: xemacs21 -- RoQA; not in trixie; severely outdated has caused the Debian Bug report #1103291, regarding RM: xemacs21 -- RoQA; not in trixie; severely outdated to be marked as done. This means

Bug#1103195: marked as done (orange3: FTBFS: error: error in setup.cfg: command 'config' has no such option 'with-htmlhelp')

Your message dated Wed, 16 Apr 2025 11:49:27 + with message-id and subject line Bug#1103195: fixed in orange3 3.38.1-3 has caused the Debian Bug report #1103195, regarding orange3: FTBFS: error: error in setup.cfg: command 'config' has no such option 'with-htmlhelp' to be marked as done. Thi

Bug#1102780: marked as done (ddnet: FTBFS: error: failed to select a version for the requirement `quote = "^1.0.35"` (locked to 1.0.37))

Your message dated Wed, 16 Apr 2025 11:34:12 + with message-id and subject line Bug#1102780: fixed in ddnet 19.1-2 has caused the Debian Bug report #1102780, regarding ddnet: FTBFS: error: failed to select a version for the requirement `quote = "^1.0.35"` (locked to 1.0.37) to be marked as do

Bug#691755: marked as done (RM: libxmltok -- RoQA; leaf package; successor available)

Your message dated Wed, 16 Apr 2025 11:30:15 + with message-id and subject line Bug#691755: Removed package(s) from unstable has caused the Debian Bug report #691755, regarding RM: libxmltok -- RoQA; leaf package; successor available to be marked as done. This means that you claim that the pr

Bug#1103178: marked as done (libxmltok: get out of testing)

Your message dated Wed, 16 Apr 2025 11:30:16 + with message-id and subject line Bug#691755: Removed package(s) from unstable has caused the Debian Bug report #1103178, regarding libxmltok: get out of testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1090743: marked as done (RM: woff-tools -- RoQA; dead upstream, unmaintained, up-to-date fork already in debian)

Your message dated Wed, 16 Apr 2025 11:31:47 + with message-id and subject line Bug#1090743: Removed package(s) from unstable has caused the Debian Bug report #1090743, regarding RM: woff-tools -- RoQA; dead upstream, unmaintained, up-to-date fork already in debian to be marked as done. This

Bug#1103266: marked as done (RM: ruby-icalendar -- ROM; unused leaf package)

Your message dated Wed, 16 Apr 2025 11:27:29 + with message-id and subject line Bug#1103266: Removed package(s) from unstable has caused the Debian Bug report #1103266, regarding RM: ruby-icalendar -- ROM; unused leaf package to be marked as done. This means that you claim that the problem ha

Bug#1048319: marked as done (ruby-icalendar: Fails to build source after successful build)

Your message dated Wed, 16 Apr 2025 11:27:31 + with message-id and subject line Bug#1103266: Removed package(s) from unstable has caused the Debian Bug report #1048319, regarding ruby-icalendar: Fails to build source after successful build to be marked as done. This means that you claim that

Bug#1103272: marked as done (RM: ruby-rack-rewrite/unstable -- ROM; rc buggy, unused)

Your message dated Wed, 16 Apr 2025 11:29:22 + with message-id and subject line Bug#1103272: Removed package(s) from unstable has caused the Debian Bug report #1103272, regarding RM: ruby-rack-rewrite/unstable -- ROM; rc buggy, unused to be marked as done. This means that you claim that the p

Bug#1103269: marked as done (RM: ruby-ice-cube -- ROM; rc buggy, unused)

Your message dated Wed, 16 Apr 2025 11:28:25 + with message-id and subject line Bug#1103269: Removed package(s) from unstable has caused the Debian Bug report #1103269, regarding RM: ruby-ice-cube -- ROM; rc buggy, unused to be marked as done. This means that you claim that the problem has be

Bug#1103268: marked as done (RM: ruby-omniauth-oauth -- ROM; rc buggy, unused)

Your message dated Wed, 16 Apr 2025 11:27:58 + with message-id and subject line Bug#1103268: Removed package(s) from unstable has caused the Debian Bug report #1103268, regarding RM: ruby-omniauth-oauth -- ROM; rc buggy, unused to be marked as done. This means that you claim that the problem

Bug#1100309: marked as done (ruby-ice-cube: FTBFS: Failures: 1) IceCube::Occurrence to_s accepts a format option to comply with ActiveSupport Failure/Error: expect(occurrence.to_s(:short)).to eq time_

Your message dated Wed, 16 Apr 2025 11:28:28 + with message-id and subject line Bug#1103269: Removed package(s) from unstable has caused the Debian Bug report #1100309, regarding ruby-ice-cube: FTBFS: Failures: 1) IceCube::Occurrence to_s accepts a format option to comply with ActiveSupport F

Bug#1103263: marked as done (RM: ruby-omniauth-twitter -- ROM; unused, originally packaged for diaspora)

Your message dated Wed, 16 Apr 2025 11:26:59 + with message-id and subject line Bug#1103263: Removed package(s) from unstable has caused the Debian Bug report #1103263, regarding RM: ruby-omniauth-twitter -- ROM; unused, originally packaged for diaspora to be marked as done. This means that

Bug#1102948: marked as done (ruby-omniauth-oauth: FTBFS in testing: ERROR: Test "ruby3.3" failed: expected # to be a kind of Open

Your message dated Wed, 16 Apr 2025 11:27:59 + with message-id and subject line Bug#1103268: Removed package(s) from unstable has caused the Debian Bug report #1102948, regarding ruby-omniauth-oauth: FTBFS in testing: ERROR: Test "ruby3.3" failed: expected # to be a kind of OpenSSL::SSL::SSLE

Bug#1094609: marked as done (RM: ruby-omniauth-twitter -- ROM; leaf package, has no rdeps, blocking transitions)

Your message dated Wed, 16 Apr 2025 11:27:02 + with message-id and subject line Bug#1103263: Removed package(s) from unstable has caused the Debian Bug report #1094609, regarding RM: ruby-omniauth-twitter -- ROM; leaf package, has no rdeps, blocking transitions to be marked as done. This mea

Bug#1099357: marked as done (ruby-ice-cube: missing build depdendency on tzdata)

Your message dated Wed, 16 Apr 2025 11:28:28 + with message-id and subject line Bug#1103269: Removed package(s) from unstable has caused the Debian Bug report #1099357, regarding ruby-ice-cube: missing build depdendency on tzdata to be marked as done. This means that you claim that the proble

Bug#1047167: marked as done (ruby-ice-cube: Fails to build source after successful build)

Your message dated Wed, 16 Apr 2025 11:28:28 + with message-id and subject line Bug#1103269: Removed package(s) from unstable has caused the Debian Bug report #1047167, regarding ruby-ice-cube: Fails to build source after successful build to be marked as done. This means that you claim that t

Bug#1103262: marked as done (RM: ruby-omniauth-tumblr -- ROM; unused, originally packaged for diaspora)

Your message dated Wed, 16 Apr 2025 11:26:27 + with message-id and subject line Bug#1103262: Removed package(s) from unstable has caused the Debian Bug report #1103262, regarding RM: ruby-omniauth-tumblr -- ROM; unused, originally packaged for diaspora to be marked as done. This means that y

Bug#1103035: marked as done (RM: linuxcnc [armel ppc64el riscv64 s390x] -- NBS; new build dependency python3-pyqt5.qtwebengine not available)

Your message dated Wed, 16 Apr 2025 11:25:28 + with message-id and subject line Bug#1103035: Removed package(s) from unstable has caused the Debian Bug report #1103035, regarding RM: linuxcnc [armel ppc64el riscv64 s390x] -- NBS; new build dependency python3-pyqt5.qtwebengine not available to

Bug#1103030: marked as done (RM: dxvk [armel] -- RoQA; build dependency wine no longer available on armel)

Your message dated Wed, 16 Apr 2025 11:24:01 + with message-id and subject line Bug#1103030: Removed package(s) from unstable has caused the Debian Bug report #1103030, regarding RM: dxvk [armel] -- RoQA; build dependency wine no longer available on armel to be marked as done. This means tha

Bug#1103031: marked as done (RM: alsa-oss [armel armhf] -- RoQA; package does not build on 32-bit with 64-bit time_t)

Your message dated Wed, 16 Apr 2025 11:24:18 + with message-id and subject line Bug#1103031: Removed package(s) from unstable has caused the Debian Bug report #1103031, regarding RM: alsa-oss [armel armhf] -- RoQA; package does not build on 32-bit with 64-bit time_t to be marked as done. Thi

Bug#1102992: marked as done (RM: qtstyleplugins-src -- ROM; dead upstream)

Your message dated Wed, 16 Apr 2025 11:23:48 + with message-id and subject line Bug#1102992: Removed package(s) from unstable has caused the Debian Bug report #1102992, regarding RM: qtstyleplugins-src -- ROM; dead upstream to be marked as done. This means that you claim that the problem has

Bug#967720: marked as done (qtstyleplugins-src: depends on deprecated GTK 2)

Your message dated Wed, 16 Apr 2025 11:23:50 + with message-id and subject line Bug#1102992: Removed package(s) from unstable has caused the Debian Bug report #967720, regarding qtstyleplugins-src: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem ha

  1   2   >