Bug#1041102: marked as done (qemu: CVE-2023-3019)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Aug 2023 05:58:33 + with message-id and subject line Bug#1041102: fixed in qemu 1:8.1.0+ds-1~exp1 has caused the Debian Bug report #1041102, regarding qemu: CVE-2023-3019 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1038486: marked as done (devscripts: FTBFS + autopkgtest failure with libgitlab-api-v4-perl 0.27-1)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Aug 2023 04:33:59 + with message-id and subject line Bug#1038486: fixed in devscripts 2.23.6 has caused the Debian Bug report #1038486, regarding devscripts: FTBFS + autopkgtest failure with libgitlab-api-v4-perl 0.27-1 to be marked as done. This means that you cla

Bug#1042238: marked as done (devscripts: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Aug 2023 04:33:59 + with message-id and subject line Bug#1038486: fixed in devscripts 2.23.6 has caused the Debian Bug report #1038486, regarding devscripts: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that you cl

Bug#1041220: marked as done (src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Aug 2023 04:33:59 + with message-id and subject line Bug#1038486: fixed in devscripts 2.23.6 has caused the Debian Bug report #1038486, regarding src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts to be

Bug#1045144: marked as done (grpc-java: binary-any FTBFS with recent jdupes )

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 23:34:13 + with message-id and subject line Bug#1045144: fixed in grpc-java 1.41.3+ds-2 has caused the Debian Bug report #1045144, regarding grpc-java: binary-any FTBFS with recent jdupes to be marked as done. This means that you claim that the problem has

Processed: closing 1050309

2023-08-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1050309 Bug #1050309 [mirrors] mirror submission for mirror.0x626b.com Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1050309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050309 De

Bug#1023545: marked as done (systemd --user and sd-pam processes keep running after logout (again))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 Aug 2023 00:21:44 +0200 with message-id <8f6b9ef2-1bd6-4622-960b-458cd12f5...@debian.org> and subject line Re: systemd --user and sd-pam processes keep running after logout (again) has caused the Debian Bug report #1023545, regarding systemd --user and sd-pam processes k

Bug#876261: marked as done (PathModified in path activation propagates to containing directory when file is deleted)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 23:44:35 +0200 with message-id <3adde7ef-5d5d-422b-b40d-aca371868...@debian.org> and subject line Re: PathModified in path activation propagates to containing directory when file is deleted has caused the Debian Bug report #876261, regarding PathModified in path

Bug#751486: marked as done (systemd: journald flooding logs if filesystem is mounted read-only)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 23:38:36 +0200 with message-id and subject line Re: systemd: journald flooding logs if filesystem is mounted read-only has caused the Debian Bug report #751486, regarding systemd: journald flooding logs if filesystem is mounted read-only to be marked as done.

Bug#810608: marked as done (systemd-sysv: on shutdown, fails to inform users that the system is going down)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 23:35:40 +0200 with message-id <674d22c0-b790-4540-a78b-aae57eeb6...@debian.org> and subject line Re: Bug#810608: systemd-sysv: on shutdown, fails to inform users that the system is going down has caused the Debian Bug report #810608, regarding systemd-sysv: on

Processed: fixed 1040149 in 252.12-1~deb12u1, closing 1040149

2023-08-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1040149 252.12-1~deb12u1 Bug #1040149 [systemd] systemd: services considered running after mainpid has exited Marked as fixed in versions systemd/252.12-1~deb12u1. > close 1040149 Bug #1040149 [systemd] systemd: services considered running

Bug#1048723: marked as done (lastpass-cli: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 21:06:38 + with message-id and subject line Bug#1048723: fixed in lastpass-cli 1.3.4-2 has caused the Debian Bug report #1048723, regarding lastpass-cli: Fails to build source after successful build to be marked as done. This means that you claim that the p

Bug#1048082: marked as done (libfiu: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 21:06:58 + with message-id and subject line Bug#1048082: fixed in libfiu 1.1-4 has caused the Debian Bug report #1048082, regarding libfiu: Fails to build source after successful build to be marked as done. This means that you claim that the problem has bee

Bug#1035609: marked as done (wpasupplicant: DBUS policy is installed in /etc instead of /usr)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 20:48:12 + with message-id and subject line Bug#1035609: fixed in wpa 2:2.10-13 has caused the Debian Bug report #1035609, regarding wpasupplicant: DBUS policy is installed in /etc instead of /usr to be marked as done. This means that you claim that the pro

Bug#1046084: marked as done (memcached: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 20:41:34 + with message-id and subject line Bug#1046084: fixed in memcached 1.6.21-2 has caused the Debian Bug report #1046084, regarding memcached: Fails to build source after successful build to be marked as done. This means that you claim that the proble

Bug#1047475: marked as done (hiredis: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 20:38:50 + with message-id and subject line Bug#1047475: fixed in hiredis 1.2.0-3 has caused the Debian Bug report #1047475, regarding hiredis: Fails to build source after successful build to be marked as done. This means that you claim that the problem has

Bug#1048815: marked as done (libkkc: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:40:03 + with message-id and subject line Bug#1048815: fixed in libkkc 0.3.5-8 has caused the Debian Bug report #1048815, regarding libkkc: Fails to build source after successful build to be marked as done. This means that you claim that the problem has b

Bug#977183: marked as done (zpspell FTCBFS: uses an unsupported pkg-config integration)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:24:55 + with message-id and subject line Bug#977183: fixed in zpspell 0.4.3-5 has caused the Debian Bug report #977183, regarding zpspell FTCBFS: uses an unsupported pkg-config integration to be marked as done. This means that you claim that the problem

Bug#1031995: marked as done (zpspell: Bzr repo does not exist anymore)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:24:55 + with message-id and subject line Bug#1031995: fixed in zpspell 0.4.3-5 has caused the Debian Bug report #1031995, regarding zpspell: Bzr repo does not exist anymore to be marked as done. This means that you claim that the problem has been dealt w

Bug#1031994: marked as done (zemberek-server: Bzr repo does not exist anymore)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:24:47 + with message-id and subject line Bug#1031994: fixed in zemberek-server 0.7.1-13 has caused the Debian Bug report #1031994, regarding zemberek-server: Bzr repo does not exist anymore to be marked as done. This means that you claim that the problem

Bug#1031992: marked as done (zemberek: Bzr repo does not exist anymore)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:24:40 + with message-id and subject line Bug#1031992: fixed in zemberek 2.1.1-9 has caused the Debian Bug report #1031992, regarding zemberek: Bzr repo does not exist anymore to be marked as done. This means that you claim that the problem has been dealt

Bug#1047687: marked as done (rime-wubi: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:12:10 -0400 with message-id <7be5f5154a1eee422a132d8a7f9432702c73f14a.ca...@debian.org> and subject line Re: rime-wubi: Fails to build source after successful build has caused the Debian Bug report #1047687, regarding rime-wubi: Fails to build source after suc

Bug#1045600: marked as done (rime-quick: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:09:37 -0400 with message-id <7c17091fe8461e48313b0f2f59d211f789849705.ca...@debian.org> and subject line Re: rime-quick: Fails to build source after successful build has caused the Debian Bug report #1045600, regarding rime-quick: Fails to build source after s

Bug#493368: marked as done (info2www: move to doc-base section "Help")

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:06:47 + with message-id and subject line Bug#493368: fixed in info2www 1.2.2.9-25 has caused the Debian Bug report #493368, regarding info2www: move to doc-base section "Help" to be marked as done. This means that you claim that the problem has been deal

Bug#493367: marked as done (info2www: s/fileutils/coreutils/g)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:06:47 + with message-id and subject line Bug#493367: fixed in info2www 1.2.2.9-25 has caused the Debian Bug report #493367, regarding info2www: s/fileutils/coreutils/g to be marked as done. This means that you claim that the problem has been dealt with.

Bug#493366: marked as done (info2www: typo in README.Debian)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 19:06:47 + with message-id and subject line Bug#493366: fixed in info2www 1.2.2.9-25 has caused the Debian Bug report #493366, regarding info2www: typo in README.Debian to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1050179: marked as done (dgit: unable to clone -security suites (?since bullseye))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 18:49:22 + with message-id and subject line Bug#1050179: fixed in dgit 11.2 has caused the Debian Bug report #1050179, regarding dgit: unable to clone -security suites (?since bullseye) to be marked as done. This means that you claim that the problem has be

Bug#1050294: marked as done (grep: Fails to build twice)

2023-08-22 Thread Debian Bug Tracking System
package twice reveals an issue with the clean target: dpkg-source: info: local changes detected, the modified files are: source_dir/doc/grep.info dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/grep_3.11-2+salsaci+20230822+19.diff.kbSnU8 The attached patch resolves the

Bug#1043584: marked as done (pbbam FTBFS with pbcopper 2.2.0)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 20:29:46 +0200 with message-id <58a388e3-c40f-f426-e16b-3d404e45e...@debian.org> and subject line Re: pbbam FTBFS with pbcopper 2.2.0 has caused the Debian Bug report #1043584, regarding pbbam FTBFS with pbcopper 2.2.0 to be marked as done. This means that you c

Bug#1049298: marked as done (rsnapshot: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 17:41:49 + with message-id and subject line Bug#1049298: fixed in rsnapshot 1.4.5-2 has caused the Debian Bug report #1049298, regarding rsnapshot: Fails to build source after successful build to be marked as done. This means that you claim that the problem

Bug#1046056: marked as done (qemu: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 17:41:40 + with message-id and subject line Bug#1046056: fixed in qemu 1:8.0.4+dfsg-3 has caused the Debian Bug report #1046056, regarding qemu: Fails to build source after successful build to be marked as done. This means that you claim that the problem ha

Bug#1050211: marked as done (openvpn-dco-dkms: module fails to build for kernel 6.4.0: fatal error: net/gso.h: No such file or directory)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:40:50 + with message-id and subject line Bug#1050211: fixed in openvpn-dco-dkms 0.0+git20230816-2 has caused the Debian Bug report #1050211, regarding openvpn-dco-dkms: module fails to build for kernel 6.4.0: fatal error: net/gso.h: No such file or direc

Bug#1049376: marked as done (meson: Drop libglib2.0-cil-dev build dep)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:40:42 + with message-id and subject line Bug#1049376: fixed in meson 1.2.1-3 has caused the Debian Bug report #1049376, regarding meson: Drop libglib2.0-cil-dev build dep to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1050076: marked as done (gtk4: 4.12 regression: FTBFS on i386: assertion failed (r == tests[i].r (+/- FLT_EPSILON)))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:39:27 + with message-id and subject line Bug#1050076: fixed in gtk4 4.12.0+ds-2 has caused the Debian Bug report #1050076, regarding gtk4: 4.12 regression: FTBFS on i386: assertion failed (r == tests[i].r (+/- FLT_EPSILON)) to be marked as done. This me

Bug#1049434: marked as done (gtk4: FTBFS on riscv64: SIGSEGV in gtk:gtk / templates test)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:39:27 + with message-id and subject line Bug#1049434: fixed in gtk4 4.12.0+ds-2 has caused the Debian Bug report #1049434, regarding gtk4: FTBFS on riscv64: SIGSEGV in gtk:gtk / templates test to be marked as done. This means that you claim that the prob

Bug#1050075: marked as done (gtk4: 4.12 regression: FTBFS on arm*|ppc64el|s390x: several checkerboard tests failing)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:39:27 + with message-id and subject line Bug#1050075: fixed in gtk4 4.12.0+ds-2 has caused the Debian Bug report #1050075, regarding gtk4: 4.12 regression: FTBFS on arm*|ppc64el|s390x: several checkerboard tests failing to be marked as done. This means

Bug#1044494: marked as done (gnome-mastermind: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:37:10 + with message-id and subject line Bug#1044494: fixed in gnome-mastermind 0.4.0-3 has caused the Debian Bug report #1044494, regarding gnome-mastermind: Fails to build source after successful build to be marked as done. This means that you claim th

Bug#1046653: marked as done (xine-lib-1.2: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:18:05 + with message-id and subject line Bug#1046653: fixed in xine-lib-1.2 1.2.13+hg20230710-2 has caused the Debian Bug report #1046653, regarding xine-lib-1.2: Fails to build source after successful build to be marked as done. This means that you clai

Bug#1048147: marked as done (pam-geoip: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:17:40 + with message-id and subject line Bug#1048147: fixed in pam-geoip 2.1.1-7 has caused the Debian Bug report #1048147, regarding pam-geoip: Fails to build source after successful build to be marked as done. This means that you claim that the problem

Bug#1049157: marked as done (luckybackup: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:17:18 + with message-id and subject line Bug#1049157: fixed in luckybackup 0.5.0-7 has caused the Debian Bug report #1049157, regarding luckybackup: Fails to build source after successful build to be marked as done. This means that you claim that the pro

Bug#1046679: marked as done (mlt: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:17:31 + with message-id and subject line Bug#1046679: fixed in mlt 7.18.0-2 has caused the Debian Bug report #1046679, regarding mlt: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been d

Bug#1040957: marked as done (xine-lib-1.2: FTBFS on hurd-i386)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:18:05 + with message-id and subject line Bug#1040957: fixed in xine-lib-1.2 1.2.13+hg20230710-2 has caused the Debian Bug report #1040957, regarding xine-lib-1.2: FTBFS on hurd-i386 to be marked as done. This means that you claim that the problem has bee

Bug#1047566: marked as done (kid3: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:13:05 + with message-id and subject line Bug#1047566: fixed in kid3 3.9.4-2 has caused the Debian Bug report #1047566, regarding kid3: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been

Bug#1043209: marked as done (call updatedb.plocate explicitly)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:05:32 + with message-id and subject line Bug#1043209: fixed in cruft-ng 0.9.57 has caused the Debian Bug report #1043209, regarding call updatedb.plocate explicitly to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1041302: marked as done (svt-av1: breaks ABI without SONAME bump)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:00:10 + with message-id and subject line Bug#1041302: fixed in svt-av1 1.6.0+dfsg-2 has caused the Debian Bug report #1041302, regarding svt-av1: breaks ABI without SONAME bump to be marked as done. This means that you claim that the problem has been dea

Bug#1001543: marked as done (cups-daemon: no printing at all because of ghostscript unrecoverable error)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:17:46 +0100 with message-id <22082023160846.0a54aef01...@desktop.copernicus.org.uk> and subject line Re: Bug#1001543: cups-daemon: no printing at all because of ghostscript unrecoverable error has caused the Debian Bug report #1001543, regarding cups-daemon:

Bug#815154: marked as done (systemd: localed wrote a /etc/default/keyboard without XKBMODEL)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 17:28:20 +0200 with message-id <5398c554-6b85-460e-a2e3-57e84b133...@debian.org> and subject line Re: systemd: localed wrote a /etc/default/keyboard withouth XKBMODEL has caused the Debian Bug report #765343, regarding systemd: localed wrote a /etc/default/keybo

Bug#841028: marked as done (cups-daemon: cupsd uses 100% CPU)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:54:52 +0100 with message-id <22082023154810.d5c956ebf...@desktop.copernicus.org.uk> and subject line Re: Bug#841028: cups-daemon: cupsd uses 100% CPU has caused the Debian Bug report #841028, regarding cups-daemon: cupsd uses 100% CPU to be marked as done. Th

Bug#754078: marked as done (crypt devices not brought online (backed by iscsi))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 17:26:05 +0200 with message-id <008d38ba-196b-4010-940a-bc78cbf79...@debian.org> and subject line Re: Bug#754078: crypt devices not brought online (backed by iscsi) has caused the Debian Bug report #754078, regarding crypt devices not brought online (backed by i

Bug#765343: marked as done (systemd: localed wrote a /etc/default/keyboard without XKBMODEL)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 17:28:20 +0200 with message-id <5398c554-6b85-460e-a2e3-57e84b133...@debian.org> and subject line Re: systemd: localed wrote a /etc/default/keyboard withouth XKBMODEL has caused the Debian Bug report #765343, regarding systemd: localed wrote a /etc/default/keybo

Bug#1036048: marked as done (puppet-module-sbitio-monit: Package description mentions unexistant below explanation)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:59:11 + with message-id and subject line Bug#1036048: fixed in puppet-module-sbitio-monit 1.0.0-5 has caused the Debian Bug report #1036048, regarding puppet-module-sbitio-monit: Package description mentions unexistant below explanation to be marked as d

Bug#1049087: marked as done (python-enmerkar: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:00:12 + with message-id and subject line Bug#1049087: fixed in python-enmerkar 0.7.1-6 has caused the Debian Bug report #1049087, regarding python-enmerkar: Fails to build source after successful build to be marked as done. This means that you claim that

Bug#1049312: marked as done (senlin-tempest-plugin: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:00:47 + with message-id and subject line Bug#1049312: fixed in senlin-tempest-plugin 1.7.1-3 has caused the Debian Bug report #1049312, regarding senlin-tempest-plugin: Fails to build source after successful build to be marked as done. This means that yo

Bug#1047298: marked as done (toil: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:01:32 + with message-id and subject line Bug#1047298: fixed in toil 5.12.0-2 has caused the Debian Bug report #1047298, regarding toil: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been

Bug#1031192: marked as done (toil: FTBFS (The job JobClass is requesting 2.0 cores))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:01:32 + with message-id and subject line Bug#1031192: fixed in toil 5.12.0-2 has caused the Debian Bug report #1031192, regarding toil: FTBFS (The job JobClass is requesting 2.0 cores) to be marked as done. This means that you claim that the problem has

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

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:00:04 + with message-id and subject line Bug#1018483: fixed in python-doc8 0.10.1-3 has caused the Debian Bug report #1018483, regarding python-doc8: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim

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

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:59:57 + with message-id and subject line Bug#1018479: fixed in python-django-compressor 4.0-4 has caused the Debian Bug report #1018479, regarding python-django-compressor: build-depends on python3-nose or uses it for autopkgtest to be marked as done. T

Bug#1040615: marked as done (ibus: Misplaced candidate window in gtk4 apps)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:57:15 + with message-id and subject line Bug#1040615: fixed in ibus 1.5.29~rc1-1 has caused the Debian Bug report #1040615, regarding ibus: Misplaced candidate window in gtk4 apps to be marked as done. This means that you claim that the problem has been

Bug#1049434: marked as done (gtk4: FTBFS on riscv64: SIGSEGV in gtk:gtk / templates test)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:56:45 + with message-id and subject line Bug#1049434: fixed in gtk4 4.10.5+ds-4 has caused the Debian Bug report #1049434, regarding gtk4: FTBFS on riscv64: SIGSEGV in gtk:gtk / templates test to be marked as done. This means that you claim that the prob

Bug#999449: marked as done (gnome-calculator: libgcalc-dev, libgci-dev packages?)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:56:11 + with message-id and subject line Bug#999449: fixed in gnome-calculator 1:45.0-2 has caused the Debian Bug report #999449, regarding gnome-calculator: libgcalc-dev, libgci-dev packages? to be marked as done. This means that you claim that the prob

Bug#1050228: marked as done (gnome-calculator: missing-pkgconfig-dependency gci-1 => gtk4)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:56:11 + with message-id and subject line Bug#1050228: fixed in gnome-calculator 1:45.0-2 has caused the Debian Bug report #1050228, regarding gnome-calculator: missing-pkgconfig-dependency gci-1 => gtk4 to be marked as done. This means that you claim tha

Bug#1036086: marked as done (Extended autopkgtest)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:50:30 + with message-id and subject line Bug#1036086: fixed in easy-rsa 3.1.6-1 has caused the Debian Bug report #1036086, regarding Extended autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1043751: marked as done (circlator: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:50:04 + with message-id and subject line Bug#1043751: fixed in circlator 1.5.6-10 has caused the Debian Bug report #1043751, regarding circlator: Fails to build source after successful build to be marked as done. This means that you claim that the proble

Bug#803468: marked as done (migrate to /etc/locale.conf or drop the locale.conf man page)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:39:31 +0200 with message-id and subject line Re: systemd: /etc/locale.conf locale variables are not set into the user locale has caused the Debian Bug report #803468, regarding migrate to /etc/locale.conf or drop the locale.conf man page to be marked as done

Bug#1042945: marked as done (rabbitmq-server: Please support conf.d drop-in directory)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 16:20:16 +0200 with message-id and subject line Not needed has caused the Debian Bug report #1042945, regarding rabbitmq-server: Please support conf.d drop-in directory to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1049527: marked as done (python-oslo.concurrency: Fails to build binary packages again after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:58:17 +0200 with message-id <77f44b9d-9bd5-c171-7d03-d78332a23...@debian.org> and subject line Duplicate has caused the Debian Bug report #1049527, regarding python-oslo.concurrency: Fails to build binary packages again after successful build to be marked as

Bug#1049471: marked as done (python-hacking: Fails to build binary packages again after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:55:57 +0200 with message-id <70d3a2e2-e4c2-0ce6-a4ca-2e33e36f8...@debian.org> and subject line This is a duplicate has caused the Debian Bug report #1049471, regarding python-hacking: Fails to build binary packages again after successful build to be marked as

Bug#1049479: marked as done (python-pbr: Fails to build binary packages again after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:56:43 +0200 with message-id <191f626e-649a-5d11-90e4-01076c059...@debian.org> and subject line Duplicate has caused the Debian Bug report #1049479, regarding python-pbr: Fails to build binary packages again after successful build to be marked as done. This m

Bug#1045826: marked as done (pyfastx: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:53:29 + with message-id and subject line Bug#1045826: fixed in pyfastx 1.1.0-2 has caused the Debian Bug report #1045826, regarding pyfastx: Fails to build source after successful build to be marked as done. This means that you claim that the problem has

Bug#1049302: marked as done (murano: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:53:16 + with message-id and subject line Bug#1049302: fixed in murano 1:15.0.0-4 has caused the Debian Bug report #1049302, regarding murano: Fails to build source after successful build to be marked as done. This means that you claim that the problem ha

Bug#1049307: marked as done (python-sphinx-feature-classification: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:53:37 + with message-id and subject line Bug#1049307: fixed in python-sphinx-feature-classification 1.1.0-3 has caused the Debian Bug report #1049307, regarding python-sphinx-feature-classification: Fails to build source after successful build to be mar

Bug#1045132: marked as done (fflas-ffpack: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:52:36 + with message-id and subject line Bug#1045132: fixed in fflas-ffpack 2.5.0-3 has caused the Debian Bug report #1045132, regarding fflas-ffpack: Fails to build source after successful build to be marked as done. This means that you claim that the p

Processed: RFS: awstats/7.8-4 [QA] -- powerful and featureful web server log analyzer

2023-08-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1040701 Bug #1040701 [sponsorship-requests] RFS: awstats/7.8-4 [QA] -- powerful and featureful web server log analyzer Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1040701: https://bugs.

Bug#1050162: marked as done (debootstrap: fix loong64 usrmerge)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 21:47:20 +0800 with message-id and subject line Close fix loong64 usrmerge has caused the Debian Bug report #1050162, regarding debootstrap: fix loong64 usrmerge to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1003835: marked as done (udev: XEN domU: Guest RX stalled, unreachable due to nw device naming change)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:50:20 +0200 with message-id <3a970a8d-f5e7-4bfc-914d-1517a9104...@debian.org> and subject line Re: Bug#1003835: udev: XEN domU: Guest RX stalled, unreachable due to nw device naming change has caused the Debian Bug report #1003835, regarding udev: XEN domU: G

Bug#1038994: marked as done (Upgrading systemd stopped GNOME session)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 15:45:14 +0200 with message-id <1764c540-c896-43d0-b3a3-d0010551f...@debian.org> and subject line Re: Bug#1038994: Upgrading systemd stopped GNOME session has caused the Debian Bug report #1038994, regarding Upgrading systemd stopped GNOME session to be marked as

Bug#1049288: marked as done (python-automaton: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:36:59 + with message-id and subject line Bug#1049288: fixed in python-automaton 3.1.0-3 has caused the Debian Bug report #1049288, regarding python-automaton: Fails to build source after successful build to be marked as done. This means that you claim th

Bug#1049262: marked as done (python-xstatic-js-yaml: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:37:17 + with message-id and subject line Bug#1049262: fixed in python-xstatic-js-yaml 3.8.1.0-2 has caused the Debian Bug report #1049262, regarding python-xstatic-js-yaml: Fails to build source after successful build to be marked as done. This means tha

Bug#1049235: marked as done (python-django-compressor: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:37:08 + with message-id and subject line Bug#1049235: fixed in python-django-compressor 4.0-3 has caused the Debian Bug report #1049235, regarding python-django-compressor: Fails to build source after successful build to be marked as done. This means tha

Bug#1049184: marked as done (horizon: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:36:09 + with message-id and subject line Bug#1049184: fixed in horizon 3:23.1.0-4 has caused the Debian Bug report #1049184, regarding horizon: Fails to build source after successful build to be marked as done. This means that you claim that the problem

Bug#1049654: marked as done (oxygencursors: Fails to build binary packages again after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:00 + with message-id and subject line Bug#1049654: fixed in oxygencursors 0.0.2012-06-kde4.8-5 has caused the Debian Bug report #1049654, regarding oxygencursors: Fails to build binary packages again after successful build to be marked as done. This

Bug#1049233: marked as done (python-xstatic-angular-schema-form: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:24 + with message-id and subject line Bug#1049233: fixed in python-xstatic-angular-schema-form 0.8.13.0-5 has caused the Debian Bug report #1049233, regarding python-xstatic-angular-schema-form: Fails to build source after successful build to be mark

Bug#1049217: marked as done (placement: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:11 + with message-id and subject line Bug#1049217: fixed in placement 9.0.0-4 has caused the Debian Bug report #1049217, regarding placement: Fails to build source after successful build to be marked as done. This means that you claim that the problem

Bug#1046998: marked as done (runit: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:42 + with message-id and subject line Bug#1046998: fixed in runit 2.1.2-56 has caused the Debian Bug report #1046998, regarding runit: Fails to build source after successful build to be marked as done. This means that you claim that the problem has be

Bug#1046465: marked as done (oxygencursors: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:00 + with message-id and subject line Bug#1046465: fixed in oxygencursors 0.0.2012-06-kde4.8-5 has caused the Debian Bug report #1046465, regarding oxygencursors: Fails to build source after successful build to be marked as done. This means that you c

Bug#1043419: marked as done (runit: ineffective trigger interest due to /usr-merge)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:42 + with message-id and subject line Bug#1043419: fixed in runit 2.1.2-56 has caused the Debian Bug report #1043419, regarding runit: ineffective trigger interest due to /usr-merge to be marked as done. This means that you claim that the problem has

Bug#1033542: marked as done (runit-services: dhclient spamming syslog (eth1 hardcoded))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:48 + with message-id and subject line Bug#1033542: fixed in runit-services 0.5.5 has caused the Debian Bug report #1033542, regarding runit-services: dhclient spamming syslog (eth1 hardcoded) to be marked as done. This means that you claim that the pr

Bug#1022837: marked as done (/lib/runit/run_sysv_scripts uses wrong test to skip initscripts)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:22:42 + with message-id and subject line Bug#1022837: fixed in runit 2.1.2-56 has caused the Debian Bug report #1022837, regarding /lib/runit/run_sysv_scripts uses wrong test to skip initscripts to be marked as done. This means that you claim that the pr

Bug#1050207: marked as done (fcitx5-pinyin-gui/experimental: undeclared file conflict with fcitx5-pinyin/unstable)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:19:56 + with message-id and subject line Bug#1050207: fixed in fcitx5-chinese-addons 5.1.0-1 has caused the Debian Bug report #1050207, regarding fcitx5-pinyin-gui/experimental: undeclared file conflict with fcitx5-pinyin/unstable to be marked as done.

Bug#1050016: marked as done (RFS: runit/2.1.2-56 -- system-wide service supervision)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 08:06:07 -0500 with message-id <65ac363f-1252-4e7b-93e3-e86663b43...@tsimonq2.net> and subject line Re: RFS: runit/2.1.2-56 -- system-wide service supervision has caused the Debian Bug report #1050016, regarding RFS: runit/2.1.2-56 -- system-wide service supervis

Bug#1049216: marked as done (python-xstatic-graphlib: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 13:06:58 + with message-id and subject line Bug#1049216: fixed in python-xstatic-graphlib 2.1.7.0-3 has caused the Debian Bug report #1049216, regarding python-xstatic-graphlib: Fails to build source after successful build to be marked as done. This means t

Bug#1043303: marked as done (RFS: runit-services/0.5.5 -- UNIX init scheme with service supervision (services))

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 08:07:32 -0500 with message-id <9238ec72-a990-4bb2-a5bf-9df0306bd...@tsimonq2.net> and subject line Re: RFS: runit-services/0.5.5 -- UNIX init scheme with service supervision (services) has caused the Debian Bug report #1043303, regarding RFS: runit-services/0.5

Bug#1050084: marked as done (RFS: oxygencursors/0.0.2012-06-kde4.8-5 [QA] -- Oxygen mouse cursor theme)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 08:03:55 -0500 with message-id and subject line Re: RFS: oxygencursors/0.0.2012-06-kde4.8-5 [QA] -- Oxygen mouse cursor theme has caused the Debian Bug report #1050084, regarding RFS: oxygencursors/0.0.2012-06-kde4.8-5 [QA] -- Oxygen mouse cursor theme to be m

Bug#1049189: marked as done (python-xstatic-angular-ui-router: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 12:53:16 + with message-id and subject line Bug#1049189: fixed in python-xstatic-angular-ui-router 0.3.1.2-4 has caused the Debian Bug report #1049189, regarding python-xstatic-angular-ui-router: Fails to build source after successful build to be marked as

Bug#1049187: marked as done (python-senlinclient: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 12:53:09 + with message-id and subject line Bug#1049187: fixed in python-senlinclient 3.0.0-3 has caused the Debian Bug report #1049187, regarding python-senlinclient: Fails to build source after successful build to be marked as done. This means that you cl

Bug#1034049: marked as done (RFS: wxmaxima/23.08.0-1 -- GUI for the computer algebra system Maxima)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 07:54:50 -0500 with message-id <1b9e5ef0-7715-46de-a4b0-aba7163d5...@tsimonq2.net> and subject line Re: RFS: wxmaxima/23.04.0-1 -- GUI for the computer algebra system Maxima has caused the Debian Bug report #1034049, regarding RFS: wxmaxima/23.08.0-1 -- GUI for

Bug#417621: marked as done (netpbm: pnmtops produces dark images for maxval < 255)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:46:18 +0200 with message-id and subject line Re: netpbm: pnmtops produces dark images for maxval < 255 has caused the Debian Bug report #417621, regarding netpbm: pnmtops produces dark images for maxval < 255 to be marked as done. This means that you claim t

Bug#375824: marked as done (netpbm: pgmtopbm -threshold -value 160 -> usage message)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 14:40:20 +0200 with message-id and subject line Re: Bug#375824: netpbm: pgmtopbm -threshold -value 160 -> usage message has caused the Debian Bug report #375824, regarding netpbm: pgmtopbm -threshold -value 160 -> usage message to be marked as done. This means

Bug#1049163: marked as done (trove-dashboard: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 12:36:34 + with message-id and subject line Bug#1049163: fixed in trove-dashboard 20.0.0-3 has caused the Debian Bug report #1049163, regarding trove-dashboard: Fails to build source after successful build to be marked as done. This means that you claim tha

Bug#1049053: marked as done (masakari: Fails to build source after successful build)

2023-08-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 Aug 2023 12:36:06 + with message-id and subject line Bug#1049053: fixed in masakari 15.0.0-3 has caused the Debian Bug report #1049053, regarding masakari: Fails to build source after successful build to be marked as done. This means that you claim that the problem

  1   2   >