Your message dated Wed, 01 May 2024 16:20:58 +
with message-id
and subject line Bug#1059016: fixed in kicad 8.0.2+dfsg-1
has caused the Debian Bug report #1059016,
regarding kicad: add loongarch64 support
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 01 May 2024 18:19:17 +
with message-id
and subject line Bug#1070032: fixed in elogind 255.5-1debian1
has caused the Debian Bug report #1070032,
regarding elogind: add NEWS for 255.4.1, suspend now default to s2idle instead
of s2ram
to be marked as done.
This means
Your message dated Wed, 01 May 2024 14:58:50 +
with message-id
and subject line Bug#1070161: fixed in ramond 0.5-5
has caused the Debian Bug report #1070161,
regarding ITS: ramond
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Wed, 01 May 2024 14:58:50 +
with message-id
and subject line Bug#1066551: fixed in ramond 0.5-5
has caused the Debian Bug report #1066551,
regarding ramond: FTBFS: src/main.c:164:17: error: implicit declaration of
function ‘LOG’ [-Werror=implicit-function-declaration]
to
Your message dated Wed, 01 May 2024 15:19:24 +
with message-id
and subject line Bug#1067311: fixed in ipywidgets 8.1.2-1
has caused the Debian Bug report #1067311,
regarding ipywidgets: FTBFS: unsatisfiable build-dependency:
jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is
Your message dated Wed, 01 May 2024 15:19:24 +
with message-id
and subject line Bug#1067311: fixed in ipywidgets 8.1.2-1
has caused the Debian Bug report #1067311,
regarding matplotlib: FTBFS: unsatisfiable build-dependency:
jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is
Your message dated Wed, 1 May 2024 19:03:50 +0200
with message-id
and subject line Re: Bug#1068336: kicad-footprints: The version is too high,
the other packages are still 7.0.1 and not compatible
has caused the Debian Bug report #1068336,
regarding kicad-footprints: The version is too high, the
Your message dated Wed, 01 May 2024 16:37:56 +
with message-id
and subject line Bug#1067884: fixed in kicad-footprints 8.0.2-1
has caused the Debian Bug report #1067884,
regarding kicad: KiCad no longer recognize its own libraries after update
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 16:37:56 +
with message-id
and subject line Bug#1068408: fixed in kicad-footprints 8.0.2-1
has caused the Debian Bug report #1068408,
regarding Kicad bundle broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 1 May 2024 12:38:14 -0400
with message-id
and subject line Mark bug 1010021 as done
has caused the Debian Bug report #1010021,
regarding ramond: diff for NMU version 0.5-4.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 01 May 2024 17:56:11 +
with message-id
and subject line Bug#1070062: fixed in waylandpp 1.0.0-6
has caused the Debian Bug report #1070062,
regarding waylandpp: Missing build-depends libwayland-egl1-mesa
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 May 2024 18:07:41 +
with message-id
and subject line Bug#1070075: fixed in kwartz-client 3.0-10
has caused the Debian Bug report #1070075,
regarding kwartz-client: [INTL:nl] Dutch debconf templates translation
to be marked as done.
This means that you claim that
Your message dated Wed, 01 May 2024 17:00:10 +
with message-id
and subject line Bug#1069989: fixed in bmusb 0.7.8-1
has caused the Debian Bug report #1069989,
regarding bmusb: Add Appstream metainfo announcing HW support
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 May 2024 16:43:31 +
with message-id
and subject line Bug#1067884: fixed in kicad-packages3d 8.0.2-1
has caused the Debian Bug report #1067884,
regarding kicad: KiCad no longer recognize its own libraries after update
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 16:43:50 +
with message-id
and subject line Bug#1067884: fixed in kicad-symbols 8.0.2-1
has caused the Debian Bug report #1067884,
regarding kicad: KiCad no longer recognize its own libraries after update
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 16:44:01 +
with message-id
and subject line Bug#1067884: fixed in kicad-templates 8.0.2-1
has caused the Debian Bug report #1067884,
regarding kicad: KiCad no longer recognize its own libraries after update
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 16:43:31 +
with message-id
and subject line Bug#1068408: fixed in kicad-packages3d 8.0.2-1
has caused the Debian Bug report #1068408,
regarding Kicad bundle broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 01 May 2024 16:43:50 +
with message-id
and subject line Bug#1068408: fixed in kicad-symbols 8.0.2-1
has caused the Debian Bug report #1068408,
regarding Kicad bundle broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 01 May 2024 16:44:02 +
with message-id
and subject line Bug#1068408: fixed in kicad-templates 8.0.2-1
has caused the Debian Bug report #1068408,
regarding Kicad bundle broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 1 May 2024 13:54:29 -0700
with message-id
and subject line Re: Bug#1069898: mariadb-server: Command History is shared for
all users
has caused the Debian Bug report #1069898,
regarding mariadb-server: Command History is shared for all users
to be marked as done.
This
Your message dated Wed, 01 May 2024 18:01:41 +
with message-id
and subject line Bug#1065481: fixed in pynx 2023.1.2-1
has caused the Debian Bug report #1065481,
regarding ITP: pynx -- Python tools for Nano-structures Crystallography
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 18:01:40 +
with message-id
and subject line Bug#1070149: fixed in jack 4~git20230906.795fba0-1
has caused the Debian Bug report #1070149,
regarding ITP: jack -- Rip and encode CDs with one command
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 18:51:26 +
with message-id
and subject line Bug#1063935: fixed in stac-validator 3.3.2+ds-3
has caused the Debian Bug report #1063935,
regarding stac-validator: Vcs-Git field points to wrong repo
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 21:20:13 +
with message-id
and subject line Bug#1070015: fixed in haskell-pandoc 3.1.3-2
has caused the Debian Bug report #1070015,
regarding haskel-pandoc: FTBFS on armel: Couldn't match expected type:
WriterState -> m a
to be marked as done.
This means
Your message dated Wed, 01 May 2024 21:20:13 +
with message-id
and subject line Bug#1069165: fixed in haskell-pandoc 3.1.3-2
has caused the Debian Bug report #1069165,
regarding haskell-pandoc build failed in loong64
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 21:20:13 +
with message-id
and subject line Bug#1069165: fixed in haskell-pandoc 3.1.3-2
has caused the Debian Bug report #1069165,
regarding haskell-pandoc: Disable tests on loong64
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 21:19:22 +
with message-id
and subject line Bug#1069752: fixed in freerdp3 3.5.1+dfsg1-3
has caused the Debian Bug report #1069752,
regarding freerdp3: CVE-2024-32658 CVE-2024-32659 CVE-2024-32660 CVE-2024-32661
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> close 1070209
Bug #1070209 [udev] udev maliciously removed its own init script, breaking boot
with SysVinit
Marked Bug as done
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1070209:
Your message dated Wed, 1 May 2024 21:22:48 -0400
with message-id <20240501212248.2e973dd3@success>
and subject line easy come, easy go
has caused the Debian Bug report #1060322,
regarding linux-image-5.10.0-27-amd64: Panic on poweroff after upgrade from
5.10.0-26 to 5.10.0-27
to be marked as
Your message dated Wed, 01 May 2024 22:51:08 +
with message-id
and subject line Bug#1051418: fixed in obs-studio 30.1.2+dfsg-1
has caused the Debian Bug report #1051418,
regarding obs-studio: clicking on an xcomposite window source makes obs segfault
to be marked as done.
This means that you
Your message dated Thu, 02 May 2024 03:59:56 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #1058652,
regarding RM: python-boto -- ROM; orphaned upstream, replaced by python-boto3
to be marked as done.
This means that you
Your message dated Thu, 02 May 2024 04:01:15 +
with message-id
and subject line Bug#1064233: Removed package(s) from unstable
has caused the Debian Bug report #1064233,
regarding RM: rust-axum-core -- RoM; superseded by rust-axum
to be marked as done.
This means that you claim that the
Your message dated Thu, 02 May 2024 04:00:31 +
with message-id
and subject line Bug#1065045: Removed package(s) from unstable
has caused the Debian Bug report #1058419,
regarding pyannotate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 3.11" returned
Your message dated Thu, 02 May 2024 04:00:28 +
with message-id
and subject line Bug#1065045: Removed package(s) from unstable
has caused the Debian Bug report #1065045,
regarding RM: pyannotate -- ROM; leaf package
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 02 May 2024 04:01:52 +
with message-id
and subject line Bug#1070202: Removed package(s) from experimental
has caused the Debian Bug report #1070202,
regarding RM: rust-atk-sys/experimental -- ROM; RoM; unmaintained library
to be marked as done.
This means that you
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #782251,
regarding python-boto: S3 upload using sigv4 crash
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #838286,
regarding python-boto: request for jessie-backports
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #843099,
regarding Please backport current testing version to Jessie
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #1058237,
regarding python-boto: FTBFS: ModuleNotFoundError: No module named 'imp'
to be marked as done.
This means that you claim
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #873293,
regarding ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
(_ssl.c:719)
to be marked as done.
This means that
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #933182,
regarding python-boto: upadting to 2.49.0-2 causes CERTIFICATE_VERIFY_FAILED
with duplicity
to be marked as done.
This
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #1018466,
regarding python-boto: build-depends on python3-nose or uses it for autopkgtest
to be marked as done.
This means that you
Your message dated Thu, 02 May 2024 02:34:47 +
with message-id
and subject line Bug#1058834: fixed in ponyprog 3.1.3+ds-1.1
has caused the Debian Bug report #1058834,
regarding ponyprog: use udev.pc to place udev rules
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 02 May 2024 02:34:12 +
with message-id
and subject line Bug#1058773: fixed in caddy 2.6.2-6.1
has caused the Debian Bug report #1058773,
regarding caddy: use systemd.pc to place systemd units
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 1 May 2024 22:33:43 -0400
with message-id <20240502023343.ga2265...@mit.edu>
and subject line mark #1060481 as done
has caused the Debian Bug report #1060481,
regarding e2fsprogs: Please switch Build-Depends to systemd-dev
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 21:05:31 +
with message-id
and subject line Bug#1070167: fixed in openrc 0.54-2
has caused the Debian Bug report #1070167,
regarding openrc: postinst fails with not executable script in /etc/init.d/
to be marked as done.
This means that you claim that the
Your message dated Wed, 1 May 2024 21:01:12 +
with message-id <20240501210112.4k2xybnwlgeub...@satie.tumbleweed.org.za>
and subject line Re: Bug#1070203: python3-pip: app silently lost in upgrade to
Bookworm + pip3 lost track of the status (4 bugs)
has caused the Debian Bug report #1070203,
Your message dated Wed, 01 May 2024 21:50:27 +
with message-id
and subject line Bug#1004057: fixed in evolution-ews 3.52.1-1
has caused the Debian Bug report #1004057,
regarding evolution-ews: reproducible-builds: build path embedded in
libecalbackendews.so and RPATH
to be marked as done.
Your message dated Wed, 01 May 2024 21:49:15 +
with message-id
and subject line Bug#1052298: fixed in context-modules 20240428-2
has caused the Debian Bug report #1052298,
regarding metafun.mp refers to inexistent metafun.mpii
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 1 May 2024 09:32:09 +0300
with message-id <6003336d-b07f-4694-bb54-4ae23d971...@tls.msk.ru>
and subject line Re: qemu-system: Please provide useful defaults for machine
and cpu
has caused the Debian Bug report #1040212,
regarding qemu-system: Please provide useful defaults
Your message dated Wed, 01 May 2024 08:47:00 +0200
with message-id
and subject line Accepted xsok 1.02-20 (source) into unstable
has caused the Debian Bug report #1021470,
regarding xsok: reproducible-builds: build path embedded in /usr/games/xsok
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 06:06:51 +
with message-id
and subject line Bug#1070059: fixed in p11-kit 0.25.3-5
has caused the Debian Bug report #1070059,
regarding p11-kit FTBFS with gcc-14 due to -Wincompatible-pointer-types having
become an error
to be marked as done.
This means
Your message dated Wed, 01 May 2024 07:49:32 +
with message-id
and subject line Bug#1069740: fixed in kitty 0.34.1-1
has caused the Debian Bug report #1069740,
regarding kitty: incorrectly acts like mouse button is pressed
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> close 1070122
Bug #1070122 [apt] apt-cache rdepends with an exact match name
Marked Bug as done
--
1070122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 01 May 2024 09:54:03 +
with message-id
and subject line Bug#1068660: fixed in mpv 0.38.0-1
has caused the Debian Bug report #1068660,
regarding mpv: No sound. Please backport upstream patch.
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 10:20:30 +
with message-id
and subject line Bug#1066703: fixed in rxtx 2.2.0+dfsg-3
has caused the Debian Bug report #1066703,
regarding rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of
function ‘major’
Your message dated Wed, 1 May 2024 13:27:42 +0530
with message-id
and subject line Added suggests on fonts-noto-color-emoji
has caused the Debian Bug report #1069750,
regarding kitty: should recommend or at least suggest fonts-noto-color-emoji
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 09:22:14 +
with message-id
and subject line Bug#1064956: fixed in libh3 4.1.0-3
has caused the Debian Bug report #1064956,
regarding libh3-dev: Using find_package(h3) can't be resolved
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 May 2024 13:27:24 +0200
with message-id <87v83xu5xf@giraffe.home.nonempty.org>
and subject line
has caused the Debian Bug report #1047834,
regarding python-pyspike: Fails to build source after successful build
to be marked as done.
This means that you claim that
Your message dated Wed, 1 May 2024 14:03:41 +0200
with message-id <58a306bd-5b55-45fa-9b3a-f35a10138...@debian.org>
and subject line fixed upstream now
has caused the Debian Bug report #1059268,
regarding rust-coreutils: add loongarch64 support
to be marked as done.
This means that you claim that
Your message dated Wed, 1 May 2024 14:03:41 +0200
with message-id <58a306bd-5b55-45fa-9b3a-f35a10138...@debian.org>
and subject line fixed upstream now
has caused the Debian Bug report #992126,
regarding rust-coreutils: please make the build reproducible
to be marked as done.
This means that you
Your message dated Wed, 01 May 2024 12:13:26 +
with message-id
and subject line Bug#1070093: Removed package(s) from unstable
has caused the Debian Bug report #1070093,
regarding RM: rust-gdk-sys -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 May 2024 12:13:51 +
with message-id
and subject line Bug#1070094: Removed package(s) from unstable
has caused the Debian Bug report #1070094,
regarding RM: rust-gtk3-macros -- RoM; unmaintained library
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 12:13:02 +
with message-id
and subject line Bug#1070092: Removed package(s) from unstable
has caused the Debian Bug report #1064375,
regarding rust-gtk: Unmaintained library should not be included in Trixie
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 12:12:05 +
with message-id
and subject line Bug#1070090: Removed package(s) from unstable
has caused the Debian Bug report #1070090,
regarding RM: rust-gdkx11 -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 May 2024 12:12:32 +
with message-id
and subject line Bug#1070091: Removed package(s) from unstable
has caused the Debian Bug report #1070091,
regarding RM: rust-gdk -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 May 2024 12:12:58 +
with message-id
and subject line Bug#1070092: Removed package(s) from unstable
has caused the Debian Bug report #1070092,
regarding RM: rust-gtk -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> close 1031120 643-1
Bug #1031120 [less] does not reset hyperlinks with -R
Marked as fixed in versions less/643-1.
Bug #1031120 [less] does not reset hyperlinks with -R
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if
Your message dated Wed, 01 May 2024 13:37:36 +
with message-id
and subject line Bug#1059268: fixed in rust-coreutils 0.0.26-1
has caused the Debian Bug report #1059268,
regarding rust-coreutils: add loongarch64 support
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 13:37:36 +
with message-id
and subject line Bug#1067897: fixed in rust-coreutils 0.0.26-1
has caused the Debian Bug report #1067897,
regarding rust-coreutils - FTBFS with new rust-uutils-term-grid.
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 13:37:36 +
with message-id
and subject line Bug#1069413: fixed in rust-coreutils 0.0.26-1
has caused the Debian Bug report #1069413,
regarding rust-coreutils: FTBFS on arm64: make[2]: *** [GNUmakefile:289: test]
Error 101
to be marked as done.
This means
Your message dated Wed, 01 May 2024 12:08:23 +
with message-id
and subject line Bug#1070061: Removed package(s) from unstable
has caused the Debian Bug report #1070061,
regarding RM: python-ospurge -- ROM; unmaintained upstream, RC buggy
to be marked as done.
This means that you claim that
Your message dated Wed, 01 May 2024 12:08:27 +
with message-id
and subject line Bug#1070061: Removed package(s) from unstable
has caused the Debian Bug report #1022392,
regarding python-ospurge: FTBFS: AttributeError: Mock object has no attribute
'detach_policy_from_cluster'
to be marked as
Your message dated Wed, 01 May 2024 12:08:52 +
with message-id
and subject line Bug#1070070: Removed package(s) from unstable
has caused the Debian Bug report #1070070,
regarding RM: moonshot-trust-router -- ROM; poorly maintained upstream
to be marked as done.
This means that you claim that
Your message dated Wed, 01 May 2024 12:07:00 +
with message-id
and subject line Bug#1070030: Removed package(s) from unstable
has caused the Debian Bug report #1070030,
regarding RM: erfs -- ROM; no longer functional
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 12:07:28 +
with message-id
and subject line Bug#1070045: Removed package(s) from unstable
has caused the Debian Bug report #1070045,
regarding RM: heat-cfntools -- ROM; unmaintained upstream, RC buggy
to be marked as done.
This means that you claim that
Your message dated Wed, 01 May 2024 12:07:57 +
with message-id
and subject line Bug#1070060: Removed package(s) from unstable
has caused the Debian Bug report #1070060,
regarding RM: networking-mlnx -- ROM; unmaintained upstream, FTBFS
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 12:08:00 +
with message-id
and subject line Bug#1070060: Removed package(s) from unstable
has caused the Debian Bug report #1021924,
regarding networking-mlnx: FTBFS test failures:
sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this
Your message dated Wed, 01 May 2024 12:07:31 +
with message-id
and subject line Bug#1070045: Removed package(s) from unstable
has caused the Debian Bug report #1058242,
regarding heat-cfntools: FTBFS: ModuleNotFoundError: No module named 'imp'
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 12:07:31 +
with message-id
and subject line Bug#1070045: Removed package(s) from unstable
has caused the Debian Bug report #1068923,
regarding heat-cfntools: Remove from Debian?
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 12:07:03 +
with message-id
and subject line Bug#1070030: Removed package(s) from unstable
has caused the Debian Bug report #1069614,
regarding erfs: no longer functional, should be removed
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 May 2024 12:11:36 +
with message-id
and subject line Bug#1070089: Removed package(s) from unstable
has caused the Debian Bug report #1070089,
regarding RM: rust-gdkx11-sys -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 May 2024 12:10:16 +
with message-id
and subject line Bug#1070087: Removed package(s) from unstable
has caused the Debian Bug report #1070087,
regarding RM: rust-atk -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 May 2024 12:10:44 +
with message-id
and subject line Bug#1070088: Removed package(s) from unstable
has caused the Debian Bug report #1070088,
regarding RM: rust-atk-sys -- RoM; unmaintained library
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 May 2024 12:09:52 +
with message-id
and subject line Bug#1070072: Removed package(s) from unstable
has caused the Debian Bug report #836116,
regarding moonshot-ui: please check for XDG_RUNTIME_DIR/bus before running
dbus-launch
to be marked as done.
This means
Your message dated Wed, 01 May 2024 12:09:52 +
with message-id
and subject line Bug#1070072: Removed package(s) from unstable
has caused the Debian Bug report #1066616,
regarding moonshot-ui: FTBFS: src/moonshot-futils.c:41:34: error: implicit
declaration of function ‘getuid’; did you mean
Your message dated Wed, 01 May 2024 12:09:19 +
with message-id
and subject line Bug#1070071: Removed package(s) from unstable
has caused the Debian Bug report #1070071,
regarding RM: moonshot-gss-eap -- ROM; poorly maintained upstream
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 12:09:49 +
with message-id
and subject line Bug#1070072: Removed package(s) from unstable
has caused the Debian Bug report #1070072,
regarding RM: moonshot-ui -- ROM; poorly maintained upstream
to be marked as done.
This means that you claim that the
Your message dated Wed, 01 May 2024 12:17:44 +
with message-id
and subject line Bug#1070165: Removed package(s) from unstable
has caused the Debian Bug report #785670,
regarding auth_pgsql: documentation examples incomplete: AuthBasicProvider
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 12:17:44 +
with message-id
and subject line Bug#1070165: Removed package(s) from unstable
has caused the Debian Bug report #785669,
regarding auth_pgsql: user is a reserved word
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 May 2024 12:17:44 +
with message-id
and subject line Bug#1070165: Removed package(s) from unstable
has caused the Debian Bug report #947039,
regarding libapache2-mod-auth-pgsql: AuthType Basic configured without
corresponding module
to be marked as done.
This
Your message dated Wed, 01 May 2024 12:17:44 +
with message-id
and subject line Bug#1070165: Removed package(s) from unstable
has caused the Debian Bug report #865553,
regarding libapache2-mod-auth-pgsql: segfault when using unsupported hash format
to be marked as done.
This means that you
Your message dated Wed, 01 May 2024 12:17:44 +
with message-id
and subject line Bug#1070165: Removed package(s) from unstable
has caused the Debian Bug report #1020889,
regarding libapache2-mod-auth-pgsql: reproducible-builds: Embedded build paths
in mod_auth_pgsql.so
to be marked as done.
Your message dated Wed, 01 May 2024 12:17:15 +
with message-id
and subject line Bug#1070156: Removed package(s) from unstable
has caused the Debian Bug report #1061694,
regarding gnome-video-arcade: Please stop using libsoup2.4
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 May 2024 12:17:12 +
with message-id
and subject line Bug#1070156: Removed package(s) from unstable
has caused the Debian Bug report #1070156,
regarding RM: gnome-video-arcade -- ROM; Abandoned upstream, uses oldlibs
to be marked as done.
This means that you claim
Your message dated Wed, 01 May 2024 12:17:38 +
with message-id
and subject line Bug#1070165: Removed package(s) from unstable
has caused the Debian Bug report #1070165,
regarding RM: libapache2-mod-auth-pgsql -- RoQA; RC-buggy, unmaintained, not in
stable
to be marked as done.
This means
Your message dated Wed, 01 May 2024 12:17:15 +
with message-id
and subject line Bug#1070156: Removed package(s) from unstable
has caused the Debian Bug report #1061696,
regarding gnome-video-arcade: Remove unmaintained package?
to be marked as done.
This means that you claim that the problem
97 matches
Mail list logo
