Your message dated Thu, 02 Jan 2025 07:34:07 +
with message-id
and subject line Bug#1030477: fixed in x52pro 0.2.0-1
has caused the Debian Bug report #1030477,
regarding libx52pro0: New upstream release 0.3.0
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Thu, 02 Jan 2025 07:34:07 +
with message-id
and subject line Bug#810466: fixed in x52pro 0.2.0-1
has caused the Debian Bug report #810466,
regarding x52pro: please switch to libusb 1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 02 Jan 2025 07:19:12 +
with message-id
and subject line Bug#1091601: fixed in golang-github-bradenaw-juniper 0.15.3-1
has caused the Debian Bug report #1091601,
regarding golang-github-bradenaw-juniper: FTBFS: dh_auto_test: error: cd _build
&& go test -vet=off -v -p 8
Your message dated Thu, 02 Jan 2025 07:19:01 +
with message-id
and subject line Bug#1088091: fixed in azote 1.14.1-1
has caused the Debian Bug report #1088091,
regarding azote: needs to declare dependency on python3-pil
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 02 Jan 2025 07:19:02 +
with message-id
and subject line Bug#1088092: fixed in azote 1.14.1-1
has caused the Debian Bug report #1088092,
regarding azote: declares dependency on libgtk-3-dev
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 02 Jan 2025 03:49:04 +
with message-id
and subject line Bug#1058872: fixed in colortest 20110624-10
has caused the Debian Bug report #1058872,
regarding colortest: typos in all debian manpages
to be marked as done.
This means that you claim that the problem has been de
Your message dated Thu, 02 Jan 2025 03:26:25 +
with message-id
and subject line Bug#1091181: fixed in module-assistant 0.11.12
has caused the Debian Bug report #1091181,
regarding v4l2loopback: autopkgtests do not work with make 4.4.1
to be marked as done.
This means that you claim that the p
Your message dated Thu, 02 Jan 2025 02:36:10 +
with message-id
and subject line Bug#1077499: fixed in pytorch-vision 0.20.1-1
has caused the Debian Bug report #1077499,
regarding pytorch-vision: debian/control requires torch but torch-cuda should
also be possible as alternative
to be marked a
Your message dated Thu, 02 Jan 2025 01:50:28 +
with message-id
and subject line Bug#928314: fixed in wakeonlan 0.41-13
has caused the Debian Bug report #928314,
regarding wakeonlan requires netbase as dependency
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Thu, 02 Jan 2025 01:50:14 +
with message-id
and subject line Bug#1091039: fixed in onetbb 2022.0.0-1
has caused the Debian Bug report #1091039,
regarding onetbb: FTBFS: make[1]: *** [debian/rules:50:
override_dh_auto_build-indep] Error 2
to be marked as done.
This means th
Your message dated Thu, 02 Jan 2025 01:05:52 +
with message-id
and subject line Bug#1057939: fixed in recommonmark 0.7.1+ds-6
has caused the Debian Bug report #1057939,
regarding recommonmark: FTBFS: FAIL: test_headings
(tests.test_sphinx.GenericTests.test_headings)
to be marked as done.
Thi
Your message dated Thu, 02 Jan 2025 01:05:26 +
with message-id
and subject line Bug#1091814: fixed in kwayland-integration 6.2.4-2
has caused the Debian Bug report #1091814,
regarding kwayland-integration: Update description to mention KF5 and KF6
status?
to be marked as done.
This means tha
Your message dated Thu, 02 Jan 2025 01:05:44 +
with message-id
and subject line Bug#1069772: fixed in pmbootstrap 3.1.0-1
has caused the Debian Bug report #1069772,
regarding pmbootstrap: description doesn't tell me what the package does
to be marked as done.
This means that you claim that th
Your message dated Thu, 2 Jan 2025 00:35:55 +
with message-id
and subject line Re: Bug#1058895: Status of sqlalchemy
has caused the Debian Bug report #1058895,
regarding python 3.12 slices are hashable, affects one area of Row for 1.4 only
to be marked as done.
This means that you claim that
Your message dated Thu, 02 Jan 2025 00:34:20 +
with message-id
and subject line Bug#1091792: fixed in meta-kde 5:154
has caused the Debian Bug report #1091792,
regarding kde-standard: depends on khelpcenter on all architectures
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 02 Jan 2025 00:04:37 +
with message-id
and subject line Bug#1058893: fixed in medusa 2.3~rc1-1
has caused the Debian Bug report #1058893,
regarding medusa FTCBFS: missing Build-Depends: libgcrypt-dev
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> close 1083210
Bug #1083210 [src:firewalld] firewalld: flaky autopkgtest: testsuite: 224 failed
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1083210: https://bugs.debian.org/cgi-bin/bugreport.
Your message dated Wed, 01 Jan 2025 23:34:39 +
with message-id
and subject line Bug#1091798: fixed in mumble 1.5.517-3
has caused the Debian Bug report #1091798,
regarding mumble-server: Unexpected conffile prompt when upgrading to testing
to be marked as done.
This means that you claim that
Your message dated Wed, 01 Jan 2025 23:34:39 +
with message-id
and subject line Bug#1032807: fixed in mumble 1.5.517-3
has caused the Debian Bug report #1032807,
regarding [INTL:ro] Romanian debconf templates translation of mumble
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 01 Jan 2025 23:35:02 +
with message-id
and subject line Bug#1089483: fixed in xringd 1.20-29
has caused the Debian Bug report #1089483,
regarding xringd: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 01 Jan 2025 23:34:39 +
with message-id
and subject line Bug#1082641: fixed in mumble 1.5.517-3
has caused the Debian Bug report #1082641,
regarding mumble-server: Exec command in mumble-server-user-wrapper is incorrect
to be marked as done.
This means that you claim th
Your message dated Wed, 01 Jan 2025 23:34:39 +
with message-id
and subject line Bug#1068504: fixed in mumble 1.5.517-3
has caused the Debian Bug report #1068504,
regarding mumble-server: wrong path for systemd-sysusers file
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#856216: fixed in dpkg 1.22.12
has caused the Debian Bug report #856216,
regarding dpkg: Should fallback to use more(1) or less(1) if pager(1) is not
present
to be marked as done.
This means that you claim tha
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#856216: fixed in dpkg 1.22.12
has caused the Debian Bug report #856216,
regarding dpkg: Should fallback to use more(1) or less(1) if pager(1) is not
present
to be marked as done.
This means that you claim tha
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#817955: fixed in dpkg 1.22.12
has caused the Debian Bug report #817955,
regarding dpkg-buildpackage: Please remove the "Use -d flag to override." line
to be marked as done.
This means that you claim that the p
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1091450: fixed in dpkg 1.22.12
has caused the Debian Bug report #1091450,
regarding dpkg: [INTL:pt_BR] Brazilian Portuguese translation for dpkg
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1090337: fixed in dpkg 1.22.12
has caused the Debian Bug report #1090337,
regarding dpkg: Adding GNUMAKEFLAGS to allowed environment variables
to be marked as done.
This means that you claim that the problem h
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1088244: fixed in dpkg 1.22.12
has caused the Debian Bug report #1088244,
regarding dpkg-dev: Add variable for Debian revision to pkg-info.mk
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1087459: fixed in dpkg 1.22.12
has caused the Debian Bug report #1087459,
regarding dpkg: [INTL:nl] Dutch translation for the dpkg package
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1083116: fixed in dpkg 1.22.12
has caused the Debian Bug report #1083116,
regarding dpkg: po: Update Swedish translation (main branch)
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1080212: fixed in dpkg 1.22.12
has caused the Debian Bug report #1080212,
regarding [INTL:ro] Updated translation of "dpkg" to Romanian
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 Jan 2025 23:19:04 +
with message-id
and subject line Bug#1061718: fixed in dpkg 1.22.12
has caused the Debian Bug report #1061718,
regarding dpkg: Please add Kali Linux to the list of distros with a merged-usr
layout
to be marked as done.
This means that you claim
Your message dated Wed, 1 Jan 2025 23:50:30 +0100
with message-id <60244018-6137-483a-9743-0395fc6a6...@kabelmail.de>
and subject line Fixed with libdrumstick 2.10.0
has caused the Debian Bug report #1081716,
regarding libdrumstick: FTBFS: dh_install: warning: libdrumstick-plugins
missing files: u
Your message dated Wed, 01 Jan 2025 17:47:26 -0500
with message-id <228fd557b049f59319f868c71dca4a4f4d114e25.ca...@debian.org>
and subject line Re: ITP: golang-github-containerd-nydus-snapshotter -- A
containerd snapshotter with data deduplication and lazy loading in P2P fashion
has caused the Deb
Your message dated Wed, 01 Jan 2025 22:35:17 +
with message-id
and subject line Bug#1089486: fixed in z8530-utils2 3.0-1-12
has caused the Debian Bug report #1089486,
regarding z8530-utils2: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 Jan 2025 23:30:25 +0100
with message-id <6592e363a460d577e772fc8b1e044dc2fffb4e38.ca...@debian.org>
and subject line Re: Bug#1085629: libssh-4: version 0.11.1 ABI-incompatible to
0.10.6, let qemu fail to access disk images via ssh
has caused the Debian Bug report #108562
Your message dated Wed, 01 Jan 2025 22:04:23 +
with message-id
and subject line Bug#1091351: fixed in apt 2.9.21
has caused the Debian Bug report #1091351,
regarding seccomp doesn't work with https transport
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 01 Jan 2025 22:04:23 +
with message-id
and subject line Bug#1091679: fixed in apt 2.9.21
has caused the Debian Bug report #1091679,
regarding apt: change of behaviour re. signed repos and .../trusted.gpg.d/
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 1 Jan 2025 22:55:46 +0100
with message-id <20250101225430.ga1086...@debian.org>
and subject line Re: Bug#1091631: apt: delay migration to testing
has caused the Debian Bug report #1091631,
regarding apt: delay migration to testing
to be marked as done.
This means that you c
Your message dated Wed, 01 Jan 2025 21:51:16 +
with message-id
and subject line Bug#1089476: fixed in xfsdump 3.1.11-1
has caused the Debian Bug report #1089476,
regarding xfsdump: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 Jan 2025 21:50:44 +
with message-id
and subject line Bug#570410: fixed in partman-base 231
has caused the Debian Bug report #570410,
regarding partman-base: Please default to GB
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 01 Jan 2025 21:50:07 +
with message-id
and subject line Bug#1091227: fixed in netavark 1.12.1-8
has caused the Debian Bug report #1091227,
regarding netavark: Upcoming update of env_logger to v0.11
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 01 Jan 2025 21:50:07 +
with message-id
and subject line Bug#1091318: fixed in netavark 1.12.1-8
has caused the Debian Bug report #1091318,
regarding netavark: default to nftables backend
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing control commands:
> close -1 0.2.4-1
Bug #1091881 [src:rust-virtio-bindings] src:rust-virtio-bindings: fails to
migrate to testing for too long
Marked as fixed in versions rust-virtio-bindings/0.2.4-1.
Bug #1091881 [src:rust-virtio-bindings] src:rust-virtio-bindings: fails to
migrate
Your message dated Wed, 1 Jan 2025 22:25:34 +0100
with message-id
and subject line Re: Bug#1090258: pgloader: FTBFS
has caused the Debian Bug report #1090258,
regarding pgloader: FTBFS: make[1]: *** [debian/rules:45:
override_dh_auto_build-arch] Error 1
to be marked as done.
This means that you
Your message dated Wed, 01 Jan 2025 21:19:03 +
with message-id
and subject line Bug#1086750: fixed in grub-installer 1.205
has caused the Debian Bug report #1086750,
regarding grub-installer still uses old grub-legacy
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 01 Jan 2025 21:19:03 +
with message-id
and subject line Bug#1091441: fixed in grub-installer 1.205
has caused the Debian Bug report #1091441,
regarding grub-installer should be disabled on non-EFI armhf
to be marked as done.
This means that you claim that the problem h
Processing control commands:
> close -1 0.16.1-4
Bug #1091883 [src:rust-vm-memory] src:rust-vm-memory: fails to migrate to
testing for too long
Marked as fixed in versions rust-vm-memory/0.16.1-4.
Bug #1091883 [src:rust-vm-memory] src:rust-vm-memory: fails to migrate to
testing for too long
Mark
Your message dated Wed, 01 Jan 2025 21:19:03 +
with message-id
and subject line Bug#1035085: fixed in grub-installer 1.205
has caused the Debian Bug report #1035085,
regarding Bookworm RC2 grub-installer/os-prober quirks
to be marked as done.
This means that you claim that the problem has bee
Your message dated Wed, 01 Jan 2025 21:19:03 +
with message-id
and subject line Bug#1086840: fixed in grub-installer 1.205
has caused the Debian Bug report #1086840,
regarding remove grub-legacy support
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Processing control commands:
> close -1 0.17.0-1
Bug #1091880 [src:rust-vhost-user-backend] src:rust-vhost-user-backend: fails
to migrate to testing for too long
Marked as fixed in versions rust-vhost-user-backend/0.17.0-1.
Bug #1091880 [src:rust-vhost-user-backend] src:rust-vhost-user-backend: f
Processing control commands:
> close -1 0.14.0-1
Bug #1091882 [src:rust-virtio-queue] src:rust-virtio-queue: fails to migrate to
testing for too long
Marked as fixed in versions rust-virtio-queue/0.14.0-1.
Bug #1091882 [src:rust-virtio-queue] src:rust-virtio-queue: fails to migrate to
testing fo
Processing control commands:
> close -1 0.13.0-1
Bug #1091879 [src:rust-vhost] src:rust-vhost: fails to migrate to testing for
too long
Marked as fixed in versions rust-vhost/0.13.0-1.
Bug #1091879 [src:rust-vhost] src:rust-vhost: fails to migrate to testing for
too long
Marked Bug as done
--
Processing control commands:
> close -1 1:10.30.11~ds-1
Bug #1091878 [src:eye] src:eye: fails to migrate to testing for too long
Marked as fixed in versions eye/1:10.30.11~ds-1.
Bug #1091878 [src:eye] src:eye: fails to migrate to testing for too long
Marked Bug as done
--
1091878: https://bugs.d
Processing control commands:
> close -1 20240607.gitc054c32-1
Bug #1091877 [src:cl-nibbles] src:cl-nibbles: fails to migrate to testing for
too long
Marked as fixed in versions cl-nibbles/20240607.gitc054c32-1.
Bug #1091877 [src:cl-nibbles] src:cl-nibbles: fails to migrate to testing for
too lon
Processing commands for cont...@bugs.debian.org:
> close 1090064 1.13.0-1
Bug #1090064 [src:rust-virtiofsd] rust-virtiofsd: Cannot fulfill the build
dependencies
The source 'rust-virtiofsd' and version '1.13.0-1' do not appear to match any
binary packages
Marked as fixed in versions rust-virtiof
Your message dated Thu, 2 Jan 2025 06:00:22 +0900
with message-id <20250101210022.ul66qhyyuhdvg...@glandium.org>
and subject line Re: Bug#1073870: as: Error: garbage following instruction --
`bne 01f' (firefox FTBFS on armhf)
has caused the Debian Bug report #1073870,
regarding as: Error: garbage
Your message dated Wed, 01 Jan 2025 20:36:02 +
with message-id
and subject line Bug#1082457: fixed in php-nesbot-carbon 2.69.0-5
has caused the Debian Bug report #1082457,
regarding php-nesbot-carbon: FTBFS with php8.4_8.4.0~beta4-1:
.PHP Fa
Your message dated Thu, 2 Jan 2025 07:24:18 +1100
with message-id
and subject line Re: Bug#1091673: procps: top :Refresh-Display now
seems to duplicate its action
has caused the Debian Bug report #1091673,
regarding procps: top :Refresh-Display now seems to duplicate its action
to be marked as
Your message dated Wed, 01 Jan 2025 19:38:23 +
with message-id
and subject line Bug#1089452: fixed in texify 1.20-5
has caused the Debian Bug report #1089452,
regarding texify: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 01 Jan 2025 19:20:44 +
with message-id
and subject line Bug#1089431: fixed in setserial 2.17-57
has caused the Debian Bug report #1089431,
regarding setserial: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 01 Jan 2025 19:20:44 +
with message-id
and subject line Bug#1082964: fixed in setserial 2.17-57
has caused the Debian Bug report #1082964,
regarding setserial: outdated package description
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 01 Jan 2025 19:19:56 +
with message-id
and subject line Bug#969289: fixed in meta-gnome3 1:47+5
has caused the Debian Bug report #969289,
regarding gnome package depends on two music managers
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Wed, 01 Jan 2025 19:19:57 +
with message-id
and subject line Bug#1079596: fixed in meta-gnome3 1:47+5
has caused the Debian Bug report #1079596,
regarding Install one or other, not both gnome-music / rhythmbox
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 Jan 2025 19:19:57 +
with message-id
and subject line Bug#1027995: fixed in meta-gnome3 1:47+5
has caused the Debian Bug report #1027995,
regarding gnome: rhythmbox functionality overlaps with gnome-music
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 01 Jan 2025 19:04:17 +
with message-id
and subject line Bug#1090199: fixed in cam2ip 1.6-4
has caused the Debian Bug report #1090199,
regarding cam2ip: FTBFS: cannot find package "nhooyr.io/websocket"
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 Jan 2025 19:00:14 +
with message-id
and subject line Bug#1091644: fixed in ppx-js-style 0.17.0-1
has caused the Debian Bug report #1091644,
regarding ITP: ppx-js-style -- code style checker for Jane Street packages
to be marked as done.
This means that you claim tha
Your message dated Wed, 01 Jan 2025 19:00:12 +
with message-id
and subject line Bug#1069910: fixed in ecl 24.5.10+ds-1
has caused the Debian Bug report #1069910,
regarding ecl: FTBFS with LTO
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 01 Jan 2025 19:00:13 +
with message-id
and subject line Bug#1091841: fixed in ocaml-monolith 0~20241126-1
has caused the Debian Bug report #1091841,
regarding ITP: ocaml-monolith -- framework for strong random testing of OCaml
libraries
to be marked as done.
This mean
Your message dated Wed, 01 Jan 2025 18:26:50 +
with message-id
and subject line Bug#1082502: Removed package(s) from unstable
has caused the Debian Bug report #1081738,
regarding vdk2-tutorial: no homepage field
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Wed, 1 Jan 2025 19:35:30 +0100
with message-id <20250101193530.536f26dd0bf5b08550df6...@mailbox.org>
and subject line Re: Bug#1034070: installation-reports: Successful netinstall
on RTL8822CE wlan (with included non-free firmware)
has caused the Debian Bug report #1034070,
regar
Your message dated Wed, 1 Jan 2025 19:37:07 +0100
with message-id <20250101193707.9a5ad44457f9af39aeb0a...@mailbox.org>
and subject line Re: Bug#1025186: installation-reports: Successful Installation
Report
has caused the Debian Bug report #1025186,
regarding installation-reports: Successful Insta
Your message dated Wed, 1 Jan 2025 19:32:16 +0100
with message-id <20250101193216.0ebf14d28c389688118aa...@mailbox.org>
and subject line Re: Bug#1060325: installation-reports: Successful installation
on Chrultrabooked Lenovo 300e Chromebook 2nd Gen (Intel)
has caused the Debian Bug report #1060325
Your message dated Wed, 01 Jan 2025 18:26:47 +
with message-id
and subject line Bug#1082502: Removed package(s) from unstable
has caused the Debian Bug report #1082502,
regarding RM: vdk2-tutorial -- RoQM, obsolete
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 1 Jan 2025 13:21:30 -0500
with message-id
and subject line
has caused the Debian Bug report #1091818,
regarding RM: sysdig [i386] -- ANAIS; Upstream build fails for i386, Debian
package is no longer built for i386
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 Jan 2025 18:21:14 +
with message-id
and subject line Bug#1086436: Removed package(s) from unstable
has caused the Debian Bug report #1086436,
regarding RM: falcosecurity-libs [i386] -- ANAIS; Upstream build fails for
i386, Debian package is no longer built for i386
Your message dated Wed, 01 Jan 2025 18:04:11 +
with message-id
and subject line Bug#681629: fixed in edac-utils 0.18+git16-g8fdc1d4-1
has caused the Debian Bug report #681629,
regarding edac-utils: config files not cleaned up
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 01 Jan 2025 18:04:11 +
with message-id
and subject line Bug#766926: fixed in edac-utils 0.18+git16-g8fdc1d4-1
has caused the Debian Bug report #766926,
regarding edac-utils: invalid key/value pair in file
/etc/udev/rules.d/z60_edac-utils.rules
to be marked as done.
Th
Your message dated Wed, 01 Jan 2025 18:04:11 +
with message-id
and subject line Bug#1076572: fixed in edac-utils 0.18+git16-g8fdc1d4-1
has caused the Debian Bug report #1076572,
regarding edac-utils: Add Appstream metainfo announcing HW support
to be marked as done.
This means that you claim
Your message dated Wed, 01 Jan 2025 18:04:11 +
with message-id
and subject line Bug#681629: fixed in edac-utils 0.18+git16-g8fdc1d4-1
has caused the Debian Bug report #681629,
regarding edac-utils: clean up legacy conffiles
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 Jan 2025 17:50:45 +
with message-id
and subject line Bug#940151: fixed in unattended-upgrades 2.12
has caused the Debian Bug report #940151,
regarding unattended-upgrades: issue with Debian Backports Origins
to be marked as done.
This means that you claim that the p
Your message dated Wed, 01 Jan 2025 17:50:45 +
with message-id
and subject line Bug#1029026: fixed in unattended-upgrades 2.12
has caused the Debian Bug report #1029026,
regarding [INTL:es] Spanish translation of the debconf template
to be marked as done.
This means that you claim that the pr
Your message dated Wed, 01 Jan 2025 17:50:45 +
with message-id
and subject line Bug#1031852: fixed in unattended-upgrades 2.12
has caused the Debian Bug report #1031852,
regarding unattended-upgrades: [INTL:tr] turkish debconf translation update
to be marked as done.
This means that you claim
Your message dated Wed, 01 Jan 2025 17:50:45 +
with message-id
and subject line Bug#1033760: fixed in unattended-upgrades 2.12
has caused the Debian Bug report #1033760,
regarding [INTL:ro] Romanian debconf templates translation of
unattended-upgrades
to be marked as done.
This means that yo
Your message dated Wed, 01 Jan 2025 17:50:24 +
with message-id
and subject line Bug#1089415: fixed in poppass-cgi 3-6.2
has caused the Debian Bug report #1089415,
regarding poppass-cgi: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 1 Jan 2025 17:21:24 +
with message-id
and subject line Re: Bug#1078700: Artifacts in some applications
has caused the Debian Bug report #1078700,
regarding Artifacts in some applications
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Wed, 01 Jan 2025 17:04:30 +
with message-id
and subject line Bug#1089377: fixed in logapp 0.16-3
has caused the Debian Bug report #1089377,
regarding logapp: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 01 Jan 2025 17:06:26 +
with message-id
and subject line Bug#1043589: fixed in synaptic 0.91.4
has caused the Debian Bug report #1043589,
regarding synaptic: Gibbrish symbols inside "component" column for packages
from "non-free-firmware" section.
to be marked as done.
Your message dated Wed, 1 Jan 2025 16:31:45 +0100
with message-id <8653c4db-bc02-4fed-8998-8478117cb...@thykier.net>
and subject line Re: rmagic: Supporting rootless builds by default
has caused the Debian Bug report #1089419,
regarding rmagic: Supporting rootless builds by default
to be marked as
Your message dated Wed, 01 Jan 2025 15:22:01 +
with message-id
and subject line Bug#1086452: fixed in rust-rustls-webpki 0.101.7-4
has caused the Debian Bug report #1086452,
regarding src:rust-rustls-webpki: unsatisfied build dependency in testing:
librust-base64-0.21+default-dev
to be marked
Your message dated Wed, 1 Jan 2025 16:14:36 +0100
with message-id
and subject line Re: Bug#1091846: no package libsfdo
has caused the Debian Bug report #1091846,
regarding no package libsfdo
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Your message dated Wed, 01 Jan 2025 15:06:22 +
with message-id
and subject line Bug#1089378: fixed in logtool 1.2.8-14
has caused the Debian Bug report #1089378,
regarding logtool: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 Jan 2025 15:04:37 +
with message-id
and subject line Bug#1091850: fixed in djbdns 1:1.05-18
has caused the Debian Bug report #1091850,
regarding djbdns: FTBFS: Oops. Your getgroups() returned 0, and setgroups()
failed
to be marked as done.
This means that you claim
Your message dated Wed, 01 Jan 2025 14:45:18 +
with message-id
and subject line Bug#1091807: fixed in nodejs 20.18.1+dfsg-2
has caused the Debian Bug report #1091807,
regarding nodejs: FTBFS against OpenSSL 3.4
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Wed, 01 Jan 2025 14:43:32 +
with message-id
and subject line Bug#1089385: fixed in memstat 1.1+nmu2
has caused the Debian Bug report #1089385,
regarding memstat: Supporting rootless builds by default
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 Jan 2025 14:43:44 +
with message-id
and subject line Bug#1091810: fixed in node-luxon 3.5.0+~3.4.2-1
has caused the Debian Bug report #1091810,
regarding node-luxon: FTBFS: FAIL test/datetime/relative.test.js Expected:
"next month" Received: "next year"
to be marked
Your message dated Wed, 01 Jan 2025 14:41:34 +
with message-id
and subject line Bug#1089351: fixed in ircd-irc2 2.11.2p3~dfsg-7.1
has caused the Debian Bug report #1089351,
regarding ircd-irc2: Supporting rootless builds by default
to be marked as done.
This means that you claim that the prob
Your message dated Wed, 01 Jan 2025 14:39:01 +
with message-id
and subject line Bug#1081372: fixed in dahdi-linux 1:3.1.0+git20230717~dfsg-8
has caused the Debian Bug report #1081372,
regarding dahdi-dkms: module fails to build with gcc-14: error: initialization
of 'int (*)(struct device *, c
Your message dated Wed, 01 Jan 2025 15:17:10 +0100
with message-id <173574103056.4106265.12471001125457419...@cairon.jones.dk>
and subject line Re: Bug#1091219: rust-isahc: Upcoming update to env_logger
v0.11
has caused the Debian Bug report #1091219,
regarding rust-isahc: Upcoming update to env_l
Your message dated Wed, 01 Jan 2025 13:34:43 +
with message-id
and subject line Bug#1081124: fixed in ocaml-luv 0.5.14-1
has caused the Debian Bug report #1081124,
regarding ocaml-luv: FTBFS with gcc-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
1 - 100 of 121 matches
Mail list logo