Bug#799549: systemd: Provide system-log-daemon

Processed: tagging 955483

Processing commands for cont...@bugs.debian.org: > tags 955483 - fixed-upstream Bug #955483 [systemd] systemd fails to restart socket unit of already running service Removed tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 955483: https://bu

Processed: bug 955483 is forwarded to https://github.com/systemd/systemd/issues/8102

Processing commands for cont...@bugs.debian.org: > forwarded 955483 https://github.com/systemd/systemd/issues/8102 Bug #955483 [systemd] systemd fails to restart socket unit of already running service Changed Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8102' from 'htt

Bug#1012459: marked as done (systemd-logind fails on read-only filesystem)

Your message dated Thu, 9 Jun 2022 23:35:38 +0200 with message-id <83507436-5171-88ff-4145-b6528ad15...@debian.org> and subject line Re: No network connection: systemd-resolved fails to start on read-only filesystem has caused the Debian Bug report #1012459, regarding systemd-logind fails on read-

Bug#1012458: marked as done (No network connection: systemd-resolved fails to start on read-only filesystem)

Your message dated Thu, 9 Jun 2022 23:35:38 +0200 with message-id <83507436-5171-88ff-4145-b6528ad15...@debian.org> and subject line Re: No network connection: systemd-resolved fails to start on read-only filesystem has caused the Debian Bug report #1012458, regarding No network connection: system

Bug#976960: marked as done (systemd: Please package systemd-userdbd and systemd-homed)

Your message dated Thu, 09 Jun 2022 18:00:20 + with message-id and subject line Bug#976960: fixed in systemd 251.2-3 has caused the Debian Bug report #976960, regarding systemd: Please package systemd-userdbd and systemd-homed to be marked as done. This means that you claim that the problem h

Bug#990547: marked as done (libsystemd-shared broken in Multi-Arch)

Your message dated Thu, 09 Jun 2022 18:00:20 + with message-id and subject line Bug#990547: fixed in systemd 251.2-3 has caused the Debian Bug report #990547, regarding libsystemd-shared broken in Multi-Arch to be marked as done. This means that you claim that the problem has been dealt with.

systemd_251.2-3_amd64.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 08 Jun 2022 23:56:04 +0100 Source: systemd Binary: libnss-myhostname libnss-myhostname-dbgsym libnss-mymachines libnss-mymachines-dbgsym libnss-resolve libnss-resolve-dbgsym libnss-systemd libnss-systemd-dbgsym

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #955483 (http://bugs.debian.org/955483)