Bug#1022788: marked as done (cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 05:51:01 + with message-id and subject line Bug#1022788: fixed in cockpit 278-1 has caused the Debian Bug report #1022788, regarding cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures to be marked as done. This means that you claim that the prob

Bug#1011378: marked as done (tpm2-pkcs11: uscan unrecognized option)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 00:25:16 + with message-id and subject line Bug#1011378: fixed in tpm2-pkcs11 1.8.0-0.1 has caused the Debian Bug report #1011378, regarding tpm2-pkcs11: uscan unrecognized option to be marked as done. This means that you claim that the problem has been dea

Bug#1011376: marked as done (tpm2-pkcs11: Please import new upstream version)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 00:25:16 + with message-id and subject line Bug#1011376: fixed in tpm2-pkcs11 1.8.0-0.1 has caused the Debian Bug report #1011376, regarding tpm2-pkcs11: Please import new upstream version to be marked as done. This means that you claim that the problem has

Bug#1021109: marked as done (bash: non existent locale crashes bash)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 03:18:02 +0300 with message-id and subject line Fixed in 5.2-2 has caused the Debian Bug report #1021109, regarding bash: non existent locale crashes bash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Processed: RFS: audacious-plugins/4.2-1 -- Base plugins for audacious

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1022997 Bug #1022997 [sponsorship-requests] RFS: audacious-plugins/4.2-1 -- Base plugins for audacious Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1022997: https://bugs.debian.org/cgi-b

Processed: RFS: audacious/4.2-1 -- small and fast audio player which supports lots of formats

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1022996 Bug #1022996 [sponsorship-requests] RFS: audacious/4.2-1 -- small and fast audio player which supports lots of formats Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1022996: https

Bug#1005400: marked as done (firmware-nonfree: Please package AMD SEV firmware.)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 01:14:09 +0200 with message-id <2150816.NgBsaNRSFp@bagend> and subject line Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware. has caused the Debian Bug report #1005400, regarding firmware-nonfree: Please package AMD SEV firmware. to be marked a

Bug#989087: marked as done (rtw_8822ce: firmware crash)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 01:05:19 +0200 with message-id <5311533.Sb9uPGUboI@bagend> and subject line Re: Bug#989087: rtw_8822ce: firmware crash has caused the Debian Bug report #989087, regarding rtw_8822ce: firmware crash to be marked as done. This means that you claim that the problem

Bug#1016945: marked as done (firmware-qlogic: Firmware required by debiantesting kernel not available in firmware-qlogic)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 00:56:49 +0200 with message-id <45056616.fMDQidcC6G@bagend> and subject line Re: Bug#1016945: firmware-qlogic: Firmware required by debiantesting kernel not available in firmware-qlogic has caused the Debian Bug report #1016945, regarding firmware-qlogic: Firmwa

Bug#1022300: marked as done (kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: QGpgME/RefreshOpenPGPKeysJob: No such file or directory)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 22:56:19 + with message-id and subject line Bug#1022300: fixed in kleopatra 4:22.08.2-1 has caused the Debian Bug report #1022300, regarding kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: QGpgME/RefreshOpenPGPKeysJob: No such file or di

Bug#967929: marked as done (kalarm: Doen't instal properly. It nedd instalation of Akonadi, kdepin-runtime, Kderun, etc...)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 22:53:40 + with message-id and subject line Bug#967929: fixed in kalarm 4:22.08.2-1 has caused the Debian Bug report #967929, regarding kalarm: Doen't instal properly. It nedd instalation of Akonadi, kdepin-runtime, Kderun, etc... to be marked as done. Thi

Bug#1004424: marked as done (kalarm: Package information shows invalid homepage)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 22:53:40 + with message-id and subject line Bug#1004424: fixed in kalarm 4:22.08.2-1 has caused the Debian Bug report #1004424, regarding kalarm: Package information shows invalid homepage to be marked as done. This means that you claim that the problem has

Processed: RFS: evilwm/1.4.0-1 -- minimalist window manager for X11

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1022995 Bug #1022995 [sponsorship-requests] RFS: evilwm/1.4.0-1 -- minimalist window manager for X11 Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1022995: https://bugs.debian.org/cgi-bin

Bug#1003920: marked as done (akonadi: reproducible-builds: BuildId differences triggered by RPATH)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 22:49:22 + with message-id and subject line Bug#1003920: fixed in akonadi 4:22.08.2-1 has caused the Debian Bug report #1003920, regarding akonadi: reproducible-builds: BuildId differences triggered by RPATH to be marked as done. This means that you claim t

Bug#855226: marked as done (firmware-linux-nonfree: missing firmware for Broadcom bluetooth device)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 00:40:26 +0200 with message-id <1836501.CQOukoFCf9@bagend> and subject line Re: firmware-linux-nonfree: missing firmware for Broadcom bluetooth device has caused the Debian Bug report #855226, regarding firmware-linux-nonfree: missing firmware for Broadcom bluet

Bug#1009334: marked as done (firmware-amd-graphics: Freeze for VCN videos)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 00:27:03 +0200 with message-id <1740886.VLH7GnMWUR@bagend> and subject line Re: Bug#1009334: firmware-amd-graphics: Freeze for VCN videos has caused the Debian Bug report #1009334, regarding firmware-amd-graphics: Freeze for VCN videos to be marked as done. This

Bug#1000541: marked as done (firmware-iwlwifi: are some firmwares missing or is the boot looking upstream unavailable ones?)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Oct 2022 00:12:06 +0200 with message-id <3196099.aeNJFYEL58@bagend> and subject line Re: Bug#1000541: firmware-iwlwifi: are some firmwares missing or is the boot looking upstream unavailable ones? has caused the Debian Bug report #1000541, regarding firmware-iwlwifi: are

Bug#1021524: marked as done (lomiri-system-settings is not installable)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:59:54 + with message-id and subject line Bug#1021524: fixed in lomiri-system-settings 1.0~git20221028.ca6da85-1 has caused the Debian Bug report #1021524, regarding lomiri-system-settings is not installable to be marked as done. This means that you clai

Bug#1022998: marked as done (RFS: smplayer/22.7.0~ds0-1 -- Complete front-end for MPlayer and mpv)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 23:50:28 +0200 with message-id and subject line Re: Bug#1022998: RFS: smplayer/22.7.0~ds0-1 -- Complete front-end for MPlayer and mpv has caused the Debian Bug report #1022998, regarding RFS: smplayer/22.7.0~ds0-1 -- Complete front-end for MPlayer and mpv to be

Bug#1022832: marked as done (firmware-iwlwifi: Failed to load firmware for Intel Wireless AX211)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 23:46:49 +0200 with message-id <1832472.tdWV9SEqCh@bagend> and subject line Re: Bug#1022832: firmware-iwlwifi: Failed to load firmware for Intel Wireless AX211 has caused the Debian Bug report #1022832, regarding firmware-iwlwifi: Failed to load firmware for Int

Bug#1022007: marked as done (caja-extensions: transition to gssdp/gupnp 1.6)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:49:41 + with message-id and subject line Bug#1022007: fixed in caja-extensions 1.26.1-1.1 has caused the Debian Bug report #1022007, regarding caja-extensions: transition to gssdp/gupnp 1.6 to be marked as done. This means that you claim that the problem

Processed: RFS: vertcoin/0.18.0-1 [ITP] -- peer-to-peer network based digital currency - CLI tools

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1009765 Bug #1009765 [sponsorship-requests] RFS: vertcoin/0.18.0-1 [ITP] -- peer-to-peer network based digital currency - CLI tools Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1009765:

Bug#996789: marked as done (msmtp: [INTL:nl] Dutch translation of debconf messages)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#996789: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #996789, regarding msmtp: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the problem has b

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

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#999789: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #999789, regarding msmtp: [INTL:de] updated German debconf translation to be marked as done. This means that you claim that the problem has been

Bug#995012: marked as done (msmtp being setgid breaks its libsecret support on some bookworm systems)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#995012: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #995012, regarding msmtp being setgid breaks its libsecret support on some bookworm systems to be marked as done. This means that you claim tha

Bug#945024: marked as done (msmtp: Doesn't generate a Message-Id)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#945024: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #945024, regarding msmtp: Doesn't generate a Message-Id to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#944188: marked as done (/etc/msmtprc password disclosure)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#944188: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #944188, regarding /etc/msmtprc password disclosure to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1020758: marked as done (msmtp: upgrade to current upstream version)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#1020758: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #1020758, regarding msmtp: upgrade to current upstream version to be marked as done. This means that you claim that the problem has been dealt

Bug#1017455: marked as done ([INTL:es] Spanish translation of the debconf template)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#1017455: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #1017455, regarding [INTL:es] Spanish translation of the debconf template to be marked as done. This means that you claim that the problem has

Bug#1000761: marked as done (msmtp: [INTL:pt] Updated Portuguese translation - debconf messages)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:47:54 + with message-id and subject line Bug#1000761: fixed in msmtp 1.8.22-1 has caused the Debian Bug report #1000761, regarding msmtp: [INTL:pt] Updated Portuguese translation - debconf messages to be marked as done. This means that you claim that the

Bug#805278: marked as done (RFP: heka -- Stream processing software system developed by Mozilla)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 22:00:35 +0200 with message-id <87h6znhg64@msgid.hilluzination.de> and subject line HEKA has been deprecated for 6 years, closing bug has caused the Debian Bug report #805278, regarding RFP: heka -- Stream processing software system developed by Mozilla to be

Processed: control

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1011460 17-1 Bug #1011460 [wnpp] ITP: gnome-shell-extension-flypie -- an innovative marking menu written as a GNOME Shell extension There is no source info for the package 'wnpp' at version '17-1' with architecture '' Unable to make a sour

Bug#1021138: marked as done (php8.1: CVE-2022-31628 CVE-2022-31629)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:30:30 +0200 with message-id and subject line Re: Accepted php8.1 8.1.12-1 (source) into unstable has caused the Debian Bug report #1021138, regarding php8.1: CVE-2022-31628 CVE-2022-31629 to be marked as done. This means that you claim that the problem has b

Bug#1016972: marked as done (php8.1: CVE-2022-31627)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 21:29:15 +0200 with message-id and subject line Re: Accepted php8.1 8.1.12-1 (source) into unstable has caused the Debian Bug report #1016972, regarding php8.1: CVE-2022-31627 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#999825: marked as done (linux-image-5.14.0-0.bpo.2-amd64: amdgpu modules warning but it's installed)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#999825: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #999825, regarding linux-image-5.14.0-0.bpo.2-amd64: amdgpu modules warning but it's installed to be marked as done. This means th

Bug#1020962: marked as done (firmware-nonfree is too old for 12Gen Intel CPU)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1020962: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1020962, regarding firmware-nonfree is too old for 12Gen Intel CPU to be marked as done. This means that you claim that the probl

Bug#1019847: marked as done (firmware-amd-graphics: missing yellow_carp* firmware for AMD Rembrandt / Ryzen 9 6900HS / Radeon 680M)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1019847: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1019847, regarding firmware-amd-graphics: missing yellow_carp* firmware for AMD Rembrandt / Ryzen 9 6900HS / Radeon 680M to be ma

Bug#1016058: marked as done (firmware-iwlwifi: Please update the firmware-iwlwifi package)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1016058: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1016058, regarding firmware-iwlwifi: Please update the firmware-iwlwifi package to be marked as done. This means that you claim t

Bug#1015728: marked as done (Please upgrade to current linux-firmware release)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1015728: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1015728, regarding Please upgrade to current linux-firmware release to be marked as done. This means that you claim that the prob

Bug#1017839: marked as done (Missing firmwares for i915)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1014651: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1014651, regarding Missing firmwares for i915 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1014651: marked as done (Missing firmwares for i915)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1014651: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1014651, regarding Missing firmwares for i915 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1009618: marked as done (Firmware "beige-goby*", for Radeon RX6500XT, missing from package)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1009618: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1009618, regarding Firmware "beige-goby*", for Radeon RX6500XT, missing from package to be marked as done. This means that you cl

Bug#1019854: marked as done (firmware-nonfree: Please consider to update this package and its binaries)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1009316: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1009316, regarding firmware-nonfree: Please consider to update this package and its binaries to be marked as done. This means th

Bug#1011410: marked as done (Please update non-free firmware to the latest version)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1009316: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1009316, regarding Please update non-free firmware to the latest version to be marked as done. This means that you claim that the

Bug#1009316: marked as done (firmware-linux-nonfree: new upstream release (20220610))

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1009316: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1009316, regarding firmware-linux-nonfree: new upstream release (20220610) to be marked as done. This means that you claim that t

Bug#1006638: marked as done (firmware-misc-nonfree: /lib/firmware/i915/adlp_dmc_ver2_12.bin missing)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1006638: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1006638, regarding firmware-misc-nonfree: /lib/firmware/i915/adlp_dmc_ver2_12.bin missing to be marked as done. This means that y

Bug#1006500: marked as done (Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:20:40 + with message-id and subject line Bug#1006500: fixed in firmware-nonfree 20220913-1 has caused the Debian Bug report #1006500, regarding Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16 to be marked as done. This means that yo

Processed: forcibly merging 1022544 1022981

2022-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1022544 1022981 Bug #1022544 {Done: Salvatore Bonaccorso } [src:linux] linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2 Bug #1022558 {Done: Salvatore Bonaccorso } [src:linux] linux-image-6.0.0-2-amd64: Audio fails to

Bug#1022970: marked as done (cryptsetup: autopkgtest failures with systemd/udev v252)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:04:04 + with message-id and subject line Bug#1022970: fixed in cryptsetup 2:2.5.0-6 has caused the Debian Bug report #1022970, regarding cryptsetup: autopkgtest failures with systemd/udev v252 to be marked as done. This means that you claim that the prob

Bug#1021427: marked as done (cryptsetup: no input on kernel 6.0)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 20:05:24 +0200 with message-id and subject line Re: Bug#1021427: cryptsetup: no input on kernel 6.0 has caused the Debian Bug report #1021427, regarding cryptsetup: no input on kernel 6.0 to be marked as done. This means that you claim that the problem has been

Bug#962686: marked as done (ITP: s2geometry -- Computational geometry and spatial indexing on the sphere http://s2geometry.io/)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 18:00:10 + with message-id and subject line Bug#962686: fixed in s2geometry 0.10.0-1 has caused the Debian Bug report #962686, regarding ITP: s2geometry -- Computational geometry and spatial indexing on the sphere http://s2geometry.io/ to be marked as done.

Bug#1010049: marked as done (qt6-base-dev: should provide a QT_HOST_PATH directory for cross building)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:52:31 +0200 with message-id and subject line Re: Bug#1010049: qt6-base-dev: should provide a QT_HOST_PATH directory for cross building has caused the Debian Bug report #1010049, regarding qt6-base-dev: should provide a QT_HOST_PATH directory for cross build

Processed: src:ruby-vcr: fails to migrate to testing for too long: ftbfs

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 6.0.0+really5.0.0-3 Bug #1022980 [src:ruby-vcr] src:ruby-vcr: fails to migrate to testing for too long: ftbfs The source 'ruby-vcr' and version '6.0.0+really5.0.0-3' do not appear to match any binary packages Marked as fixed in versions ruby-vcr/6.0.0+real

Processed: src:gnumach: fails to migrate to testing for too long: ftbfs on amd64

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2:1.8+git20220827-3 Bug #1022979 [src:gnumach] src:gnumach: fails to migrate to testing for too long: ftbfs on amd64 Marked as fixed in versions gnumach/2:1.8+git20220827-3. Bug #1022979 [src:gnumach] src:gnumach: fails to migrate to testing for too long:

Processed: src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x

2022-10-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.30.0-3 Bug #1022978 [src:atlas-ecmwf] src:atlas-ecmwf: fails to migrate to testing for too long: ftbfs on mips64el and s390x Marked as fixed in versions atlas-ecmwf/0.30.0-3. Bug #1022978 [src:atlas-ecmwf] src:atlas-ecmwf: fails to migrate to testing for

Bug#1022976: marked as done (plasma-workspace-data: digital clock widget lacks a module)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 19:16:23 +0200 with message-id <8eb29f9f-5693-4655-9108-07e226a5e...@coucouf.fr> and subject line Re: Bug#1022976: Acknowledgement (plasma-workspace-data: digital clock widget lacks a module) has caused the Debian Bug report #1022976, regarding plasma-workspace-

Bug#1020043: marked as done (pillow: FTBFS: ModuleNotFoundError: No module named 'PIL')

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 16:20:33 + with message-id and subject line Bug#1020043: fixed in pillow 9.2.0-1.1 has caused the Debian Bug report #1020043, regarding pillow: FTBFS: ModuleNotFoundError: No module named 'PIL' to be marked as done. This means that you claim that the proble

Bug#877015: marked as done (fizmo FTBFS with debhelper 10.9)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:48:24 + with message-id and subject line Bug#1022757: Removed package(s) from unstable has caused the Debian Bug report #877015, regarding fizmo FTBFS with debhelper 10.9 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1022146: marked as done (diffoscope: detect ordering-only differences in XML files)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:49:08 + with message-id and subject line Bug#1022146: fixed in diffoscope 225 has caused the Debian Bug report #1022146, regarding diffoscope: detect ordering-only differences in XML files to be marked as done. This means that you claim that the problem

Bug#1022757: marked as done (RM: src:fizmo -- NVIU; replaced by other real packages)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:48:21 + with message-id and subject line Bug#1022757: Removed package(s) from unstable has caused the Debian Bug report #1022757, regarding RM: src:fizmo -- NVIU; replaced by other real packages to be marked as done. This means that you claim that the pr

Bug#1022145: marked as done (diffoscope: detect ordering-only differences in text files)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:49:08 + with message-id and subject line Bug#1022145: fixed in diffoscope 225 has caused the Debian Bug report #1022145, regarding diffoscope: detect ordering-only differences in text files to be marked as done. This means that you claim that the problem

Bug#1022934: marked as done (libpappsomspp: FTBFS on i386)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 18:41:51 +0300 with message-id and subject line Fixed in 0.8.58-1 has caused the Debian Bug report #1022934, regarding libpappsomspp: FTBFS on i386 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#1021768: marked as done (RM: remove nvptx-tools binaries on mipsel and mips64el)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:42:49 + with message-id and subject line Bug#1021768: Removed package(s) from unstable has caused the Debian Bug report #1021768, regarding RM: remove nvptx-tools binaries on mipsel and mips64el to be marked as done. This means that you claim that the pr

Bug#1019264: marked as done (RM: libphobos2-ldc-sharedXX -- RoQA; NBS)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 11:39:29 -0400 with message-id <2501104.rbVep46VgM@zini-1880> and subject line Re: RM: libphobos2-ldc-sharedXX -- RoQA; NBS has caused the Debian Bug report #1019264, regarding RM: libphobos2-ldc-sharedXX -- RoQA; NBS to be marked as done. This means that you cl

Bug#1018829: marked as done (RM: NBS binaries not built anymore from gcc-defaults-ports)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 11:36:02 -0400 with message-id <2075244.SBy9fNd9Su@zini-1880> and subject line Re: RM: NBS binaries not built anymore from gcc-defaults-ports has caused the Debian Bug report #1018829, regarding RM: NBS binaries not built anymore from gcc-defaults-ports to be mar

Bug#1022882: marked as done (RM: golang-github-bep-inflect -- ROM; Obsolete, superseeded by golang-github-gobuffalo-flect-dev)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:55 + with message-id and subject line Bug#1022882: Removed package(s) from unstable has caused the Debian Bug report #1022882, regarding RM: golang-github-bep-inflect -- ROM; Obsolete, superseeded by golang-github-gobuffalo-flect-dev to be marked as d

Bug#1022883: marked as done (RM: golang-github-markbates-inflect -- ROM; Obsolete, superseeded by golang-github-gobuffalo-flect-dev)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:28:59 + with message-id and subject line Bug#1022883: Removed package(s) from unstable has caused the Debian Bug report #1022883, regarding RM: golang-github-markbates-inflect -- ROM; Obsolete, superseeded by golang-github-gobuffalo-flect-dev to be marke

Bug#1022878: marked as done (RM: haskell-crypto-numbers -- ROM; obsolete)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:25 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1022878, regarding RM: haskell-crypto-numbers -- ROM; obsolete to be marked as done. This means that you claim that the problem has b

Bug#1022876: marked as done (RM: haskell-crypto-pubkey -- ROM; obsolete)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:00 + with message-id and subject line Bug#1022876: Removed package(s) from unstable has caused the Debian Bug report #1022876, regarding RM: haskell-crypto-pubkey -- ROM; obsolete to be marked as done. This means that you claim that the problem has be

Bug#1022795: marked as done (libghc-crypto-numbers-doc: depends on non-existing haddock-interface-35)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:30 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1022795, regarding libghc-crypto-numbers-doc: depends on non-existing haddock-interface-35 to be marked as done. This means that you

Bug#1015291: marked as done (haskell-crypto-numbers FTBFS: error: Variable not in scope)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:30 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1015291, regarding haskell-crypto-numbers FTBFS: error: Variable not in scope to be marked as done. This means that you claim that th

Bug#1021067: marked as done (Removal notice: obsolete)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:30 + with message-id and subject line Bug#1022878: Removed package(s) from unstable has caused the Debian Bug report #1021067, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1021068: marked as done (Removal notice: obsolete)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:04 + with message-id and subject line Bug#1022876: Removed package(s) from unstable has caused the Debian Bug report #1021068, regarding Removal notice: obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1017201: marked as done (haskell-crypto-pubkey: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.13.0.0-2f220, libghc-bytestring-dev-0.10.10.1-c40ee, libghc-crypto-random-dev-0.0.9-1612d

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:27:04 + with message-id and subject line Bug#1022876: Removed package(s) from unstable has caused the Debian Bug report #1017201, regarding haskell-crypto-pubkey: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.13.0.0-2f220, libghc-bytestring-

Bug#1022859: marked as done (RM: govendor -- RoQA; superseded by Go modules; upstream discontinued)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:26:34 + with message-id and subject line Bug#1022859: Removed package(s) from unstable has caused the Debian Bug report #1022859, regarding RM: govendor -- RoQA; superseded by Go modules; upstream discontinued to be marked as done. This means that you cl

Bug#1022801: marked as done (RM: python-hplefthandclient -- ROM; unmaintained upstream, no reverse depends)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:26:08 + with message-id and subject line Bug#1022801: Removed package(s) from unstable has caused the Debian Bug report #1022801, regarding RM: python-hplefthandclient -- ROM; unmaintained upstream, no reverse depends to be marked as done. This means th

Bug#696332: marked as done (lsb-release: release/codename depend on a successful apt-get)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 17:25:09 +0200 with message-id and subject line Re: Bug#696332: lsb-release: release/codename depend on a successful apt-get has caused the Debian Bug report #696332, regarding lsb-release: release/codename depend on a successful apt-get to be marked as done.

Bug#1018510: marked as done (python-hplefthandclient: build-depends on python3-nose or uses it for autopkgtest)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:26:12 + with message-id and subject line Bug#1022801: Removed package(s) from unstable has caused the Debian Bug report #1018510, regarding python-hplefthandclient: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This mean

Bug#1022700: marked as done (node-yargs: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:19:58 + with message-id and subject line Bug#1022700: fixed in node-yargs 16.2.0+~16.0.4-6 has caused the Debian Bug report #1022700, regarding node-yargs: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has

Bug#1020093: marked as done (python-dlt: FTBFS: AssertionError: 1 != 0 : Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after keyword)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:20:14 + with message-id and subject line Bug#1020093: fixed in python-dlt 2.0-3.1 has caused the Debian Bug report #1020093, regarding python-dlt: FTBFS: AssertionError: 1 != 0 : Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after key

Bug#1019611: marked as done (ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {})

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:20:24 + with message-id and subject line Bug#1019611: fixed in ruby-asset-sync 2.11.0-1.1 has caused the Debian Bug report #1019611, regarding ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(:

Bug#1022930: marked as done (ITP: golang-github-iancoleman-strcase -- converting string case to various cases)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:00:12 + with message-id and subject line Bug#1022930: fixed in golang-github-iancoleman-strcase 0.2.0-1 has caused the Debian Bug report #1022930, regarding ITP: golang-github-iancoleman-strcase -- converting string case to various cases to be marked as

Bug#1022929: marked as done (ITP: golang-github-coredhcp-coredhcp -- multithreaded, modular and extensible DHCP server)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:00:11 + with message-id and subject line Bug#1022929: fixed in golang-github-coredhcp-coredhcp 0.0.0+git.2022.04.07.a2552c5c1b-1 has caused the Debian Bug report #1022929, regarding ITP: golang-github-coredhcp-coredhcp -- multithreaded, modular and exte

Bug#1022877: marked as done (ITP: golang-github-chappjc-logrus-prefix -- text formatter based on logrus.TextFormatter)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:00:10 + with message-id and subject line Bug#1022877: fixed in golang-github-chappjc-logrus-prefix 0.0.0+git.2018.02.26.3a1d64819a-1 has caused the Debian Bug report #1022877, regarding ITP: golang-github-chappjc-logrus-prefix -- text formatter based on

Bug#1022928: marked as done (ITP: golang-github-d-tux-go-fstab -- simple fstab parser)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:00:12 + with message-id and subject line Bug#1022928: fixed in golang-github-d-tux-go-fstab 0.0.0+git.2014.12.04.eb4090f265-1 has caused the Debian Bug report #1022928, regarding ITP: golang-github-d-tux-go-fstab -- simple fstab parser to be marked as do

Bug#1020538: marked as done (ITP: golang-github-gopacket-gopacket -- Provides packet processing capabilities for Go)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:00:12 + with message-id and subject line Bug#1020538: fixed in golang-github-gopacket-gopacket 0.0~git20220825.b6a42f7-1 has caused the Debian Bug report #1020538, regarding ITP: golang-github-gopacket-gopacket -- Provides packet processing capabilities

Bug#1009225: marked as done (ITP: odr-dabmux -- Digital Audio Broadcasting multiplexer compliant to ETSI EN 300 401)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:00:14 + with message-id and subject line Bug#1009225: fixed in odr-dabmux 4.2.1-1 has caused the Debian Bug report #1009225, regarding ITP: odr-dabmux -- Digital Audio Broadcasting multiplexer compliant to ETSI EN 300 401 to be marked as done. This mean

Bug#1022699: marked as done (node-yargs-parser: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:37:15 + with message-id and subject line Bug#1022699: fixed in node-yargs-parser 21.1.1+~21.0.0-2 has caused the Debian Bug report #1022699, regarding node-yargs-parser: Unable to build with rollup 3 to be marked as done. This means that you claim that t

Bug#1022698: marked as done (node-sourcemap-codec: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:36:56 + with message-id and subject line Bug#1022698: fixed in node-sourcemap-codec 1.4.8-7 has caused the Debian Bug report #1022698, regarding node-sourcemap-codec: Unable to build with rollup 3 to be marked as done. This means that you claim that the

Bug#1022697: marked as done (node-yaml: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:37:07 + with message-id and subject line Bug#1022697: fixed in node-yaml 2.1.2-2 has caused the Debian Bug report #1022697, regarding node-yaml: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has been dealt

Bug#1022694: marked as done (node-magic-string: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:36:37 + with message-id and subject line Bug#1022694: fixed in node-magic-string 0.26.2-2 has caused the Debian Bug report #1022694, regarding node-magic-string: Unable to build with rollup 3 to be marked as done. This means that you claim that the probl

Bug#1022696: marked as done (node-puka: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:36:44 + with message-id and subject line Bug#1022696: fixed in node-puka 1.0.1+dfsg-3 has caused the Debian Bug report #1022696, regarding node-puka: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has been

Bug#1022695: marked as done (node-rollup-plugin-string: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:36:50 + with message-id and subject line Bug#1022695: fixed in node-rollup-plugin-string 3.0.0-9 has caused the Debian Bug report #1022695, regarding node-rollup-plugin-string: Unable to build with rollup 3 to be marked as done. This means that you claim

Bug#1022955: marked as done (gnome-network-displays: fails to find remote display)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 15:01:26 +0100 with message-id and subject line Re: Bug#1022955: Acknowledgement (gnome-network-displays: fails to find remote display) has caused the Debian Bug report #1022955, regarding gnome-network-displays: fails to find remote display to be marked as don

Bug#1022693: marked as done (node-katex: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 13:28:57 + with message-id and subject line Bug#1022693: fixed in node-katex 0.16.2+~cs6.1.0-5 has caused the Debian Bug report #1022693, regarding node-katex: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem ha

Bug#1022692: marked as done (node-fetch: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 13:28:44 + with message-id and subject line Bug#1022692: fixed in node-fetch 2.6.7+~2.6.1-2 has caused the Debian Bug report #1022692, regarding node-fetch: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has b

Bug#1022691: marked as done (node-fecha: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 13:28:35 + with message-id and subject line Bug#1022691: fixed in node-fecha 4.2.1+dfsg1-2 has caused the Debian Bug report #1022691, regarding node-fecha: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has be

Bug#1022690: marked as done (node-esquery: Unable to build with rollup 3)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 13:28:29 + with message-id and subject line Bug#1022690: fixed in node-esquery 1.4.0~ds-2 has caused the Debian Bug report #1022690, regarding node-esquery: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has b

Bug#681598: marked as done (/usr/share/pyshared/lsb_release.py: release detection fails with http.debian.net redirector in sources.list)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:57:22 +0200 with message-id <3fd93973-18ac-88ea-d842-0540e413b...@svario.it> and subject line Re: Bug#681598: /usr/share/pyshared/lsb_release.py: release detection fails with http.debian.net redirector in sources.list has caused the Debian Bug report #681598,

Bug#543180: marked as done (jaaa: segfaults if DISPLAY is unset)

2022-10-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Oct 2022 14:26:01 +0200 with message-id <039e9ac3-9809-42b0-141f-081ae115e...@kabelmail.de> and subject line Re: jaaa: segfaults if DISPLAY is unset has caused the Debian Bug report #543180, regarding jaaa: segfaults if DISPLAY is unset to be marked as done. This means t

  1   2   >