Package: systemd
Version: 243-5
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
systemd upgrade broke dbus, which in turn prevents normal operation of APT and
upgrade of packages that depend upon dbus messages.
**
$ sudo dpkg --configure --pending
Setting up
ke 13. marrask. 2019 klo 17.37 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Am 13.11.19 um 16:06 schrieb Martin-Éric Racine:
>
> >> Can you provide a dmesg dump and the output of journalctl -alb.
> >
> > Attached.
> >
> >> Please mark the time w
ke 13. marrask. 2019 klo 17.06 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ke 13. marrask. 2019 klo 16.44 Michael Biebl (bi...@debian.org) kirjoitti:
> >
> > Control: tags -1 moreinfo unreproducible
> > Am 13.11.19 um 10:34 schrieb Martin-Éric Racine
ke 13. marrask. 2019 klo 20.52 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Thanks a lot for the information so far.
>
> Am 13.11.19 um 16:53 schrieb Martin-Éric Racine:
>
> > Setting up udev (243-5) ...
>
> Could you add a "set -x" to
> /var/lib/dpkg
ke 13. marrask. 2019 klo 21.03 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Btw, this reminds me of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
>
> Is this the same host where this is happening (again)?
> Is this a Virtualbox guest?
Same host. This has never been a
ke 13. marrask. 2019 klo 23.16 Michael Biebl (bi...@debian.org) kirjoitti:
>
> Ok, at this point I guess it's best to involve upstream.
> Would you mind filing an upstream bug report at
> https://github.com/systemd/system/issues
> mentionting that a daemon-reload triggers an assert in
>
Package: systemd-cron
Version: 1.5.14-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since a recent upgrade, systemd complains loudly via dmesg:
[ 45.787544] systemd[1]: /lib/systemd/system/cron-failure@.service:11:
Special user nobody configured, this is not safe!
[
Package: systemd-cron
Version: 1.5.15-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[ 43.789346] systemd[1]: /lib/systemd/system/cron-failure@.service:11:
Special user nobody configured, this is not safe!
[ 43.824795] systemd[1]:
Since Bullseye already entered the freeze but upstream only got around
reacting to the bug report now, my possibilities for getting crashes
by upgrading something that comes with an init script are slim.
I've compiled systemd packages using this command:
$ DEB_BUILD_OPTIONS="nostrip noopt
Package: systemd-cron
Version: 1.5.17-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Setting up systemd-cron (1.5.17-1) ...
xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive,
ignoring previous --max-args value
- -- Package-specific info:
- --
Package: systemd-cron
Version: 1.5.17-2
Followup-For: Bug #993731
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Seems that the fix doesn't quite work:
Setting up systemd-cron (1.5.17-2) ...
stat: cannot statx '*': No such file or directory
stat: cannot statx '*': No such file or directory
trol: found -1 1.5.14-2
> Control: tags 992748 - security
>
> Hi Chris,
>
> On Sun, Sep 05, 2021 at 02:49:40PM +0200, Chris Hofstaedtler wrote:
> > Control: tags -1 + security
> >
> > * Alexandre Detiste [210905 12:47]:
> > > Le lun. 23 août 2021 à 04:57,
>
> So for this part help will be welcome.
>
> Greets,
>
> Le mer. 8 sept. 2021 à 07:21, Martin-Éric Racine
> a écrit :
>>
>> su 5. syysk. 2021 klo 18.41 Salvatore Bonaccorso (car...@debian.org)
>> kirjoitti:
>> >
>> > Control: clone
Package: systemd
Version: 247.9-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Setting up systemd (247.9-2) ...
Removing obsolete conffile /etc/dhcp/dhclient-exit-hooks.d/timesyncd ...
Removing obsolete conffile /etc/systemd/timesyncd.conf ...
Setting up systemd-timesyncd
pe 1. lokak. 2021 klo 23.39 Santiago Ruano Rincón
(santiag...@riseup.net) kirjoitti:
>
> El 01/10/21 a las 17:05, Martin-Éric Racine escribió:
> > pe 1. lokak. 2021 klo 16.21 Santiago Ruano Rincón
> > (santiag...@riseup.net) kirjoitti:
> > > On Wed, 17 Feb 2021 14:32:
Package: systemd-cron
Version: 1.15.18-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It would be desirable for systemd-cron to add support for /etc/cron.yearly
tasks.
Thanks!
Martin-Éric
- -- Package-specific info:
- -- output of systemd-delta
- -- System Information:
On Tue, Jan 18, 2022 at 11:52 AM Ansgar wrote:
>
> tag 1003931 + moreinfo
> thanks
>
> On Tue, 2022-01-18 at 11:40 +0200, Martin-Éric Racine wrote:
> > The stock configuration file that ships with systemd-timesyncd has
> > all options commented out.
>
> That s
Package: systemd-timesyncd
Version: 250.2-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The stock configuration file that ships with systemd-timesyncd has all options
commented out. Additionally, it doesn't set any default NTP server. This
essentially means that Debian
Package: systemd-cron
Version: 1.15.19-1
Followup-For: Bug #1002925
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks for enabling this.
Mind you, systemd-cron now ships with a /etc/cron.yearly/.placeholder file.
This probably should go in cron-daemon-common instead.
Martin-Éric
- --
Package: systemd
Version: 252~rc3-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Setting up systemd (252~rc3-2) ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Installing new version
Package: libsystemd0
Version: 252-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Setting up libsystemd0:i386 (252-2) ...
Setting up libsystemd-shared:i386 (252-2) ...
Setting up systemd (252-2) ...
Installing new version of config file /etc/systemd/logind.conf ...
On Sat, Nov 5, 2022 at 4:11 PM Martin-Éric Racine
wrote:
>
> On Sat, Nov 5, 2022 at 4:02 PM Michael Biebl wrote:
> >
> > Am 05.11.22 um 14:54 schrieb Martin-Éric Racine:
> > > On Sat, Nov 5, 2022 at 3:53 PM Michael Biebl wrote:
> > >>
> > >> Co
On Sat, Nov 5, 2022 at 3:53 PM Michael Biebl wrote:
>
> Control: tags -1 + moreinfo
>
> Am 05.11.22 um 10:25 schrieb Martin-Éric Racine:
> >
> > Message from syslogd@[localhost] at Nov 5 11:09:11 ...
> > systemd[1]: Caught from our own process.
> >
On Sat, Nov 5, 2022 at 4:02 PM Michael Biebl wrote:
>
> Am 05.11.22 um 14:54 schrieb Martin-Éric Racine:
> > On Sat, Nov 5, 2022 at 3:53 PM Michael Biebl wrote:
> >>
> >> Control: tags -1 + moreinfo
> >>
> >> Am 05.11.22 um 10:25 schrieb Mart
Package: systemd-cron
Version: 1.15.19-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Unpacking cron-daemon-common (3.0pl1-160) over (3.0pl1-156) ...
dpkg: error processing archive
/var/cache/apt/archives/cron-daemon-common_3.0pl1-160_all.deb (--unpack):
trying to overwrite
Package: systemd-cron
Version: 2.3.0-1~bpo12+1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
1) In its current form, systemd-cron mails the result of global cron jobs from
root@fqdn, which fails since we aren't FQDN's administrator.
2) As a result, systemd-cron tries to
to 1. helmik. 2024 klo 9.33 Alexandre Detiste
(alexandre.deti...@gmail.com) kirjoitti:
> 1)
>
> MAILFROM= is supported for a long time, is it enough ?
>
> v1.5.18 : 2020-12-26
>
>Various improvements to email on error:
>* Revert "Use DynamicUser=yes for error email generator"
>* Use
pe 2. helmik. 2024 klo 8.30 Alexandre Detiste
(alexandre.deti...@gmail.com) kirjoitti:
>
> Le jeu. 1 févr. 2024 à 09:11, Martin-Éric Racine
> a écrit :
> > > 1)
> > >
> > > MAILFROM= is supported for a long time, is it enough ?
> > >
> > > v
Package: systemd
Version: 255.5-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
$ adequate --all --tags -py-file-not-bytecompiled
systemd: broken-symlink /etc/modules-load.d/modules.conf -> ../modules
- -- Package-specific info:
- -- System Information:
Debian Release:
Package: systemd
Version: 256~rc3-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Setting up systemd (256~rc3-3) ...
/usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock",
ignoring.
- -- Package-specific info:
- -- System Information:
Debian Release:
30 matches
Mail list logo
