systemd-cron_1.5.17-3_source.changes uploaded successfully to localhost
along with the files:
systemd-cron_1.5.17-3.dsc
systemd-cron_1.5.17-3.debian.tar.xz
systemd-cron_1.5.17-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Wed, 08 Sep 2021 21:05:38 +
with message-id
and subject line Bug#992748: fixed in systemd-cron 1.5.17-3
has caused the Debian Bug report #992748,
regarding systemd-cron: postinst error
to be marked as done.
This means that you claim that the problem has been dealt with.
If
https://salsa.debian.org/debian/cron/-/commit/230478512cc82d879d727f6dfc18040bdd48c9d9
same as 892720, 892721, 892724 :-( ... will sync again
with the latest cron.postinst and reupload
Le mer. 8 sept. 2021 à 20:03, Daniel Serpell
a écrit :
>
> Package: systemd-cron
> Version: 1.5.17-2
>
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 Sep 2021 22:45:08 +0200
Source: systemd-cron
Architecture: source
Version: 1.5.17-3
Distribution: unstable
Urgency: high
Maintainer: Debian Systemd Maintainers
Changed-By: Alexandre Detiste
Closes: 992748
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
Processing commands for cont...@bugs.debian.org:
> fixed 993731 1.5.17-2
Bug #993731 {Done: Alexandre Detiste }
[systemd-cron] systemd-cron: CVE-2017-9525: group crontab to root escalation
via postinst
Marked as fixed in versions systemd-cron/1.5.17-2.
> thanks
Stopping processing here.
Please
Hi.
I will fix unstable today but I don't know how to learn again to fix the
old releases in a timely maner between so many things to handle at home and
work.
Forking from old git tags and pasting the same new postinst over ?
So for this part help will be welcome.
Greets,
Le mer. 8 sept. 2021
Your message dated Wed, 08 Sep 2021 08:45:21 +
with message-id
and subject line Bug#992748: fixed in systemd-cron 1.5.17-2
has caused the Debian Bug report #992748,
regarding systemd-cron: postinst error
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2021 08:45:21 +
with message-id
and subject line Bug#993731: fixed in systemd-cron 1.5.17-2
has caused the Debian Bug report #993731,
regarding systemd-cron: CVE-2017-9525: group crontab to root escalation via
postinst
to be marked as done.
This means that you
systemd-cron_1.5.17-2_source.changes uploaded successfully to localhost
along with the files:
systemd-cron_1.5.17-2.dsc
systemd-cron_1.5.17-2.debian.tar.xz
systemd-cron_1.5.17-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Alexandre,
Thanks for fixing unstable.
Unless I'm mistaken, I think that the second bug was intentionally
cloned by Chris to track the issue in stable and oldstable. I'm thus
not sure if it was meant to be closed via the same upload.
Martin-Éric
ke 8. syysk. 2021 klo 9.36 Alexandre Detiste
Hi
On Wed, Sep 08, 2021 at 01:12:44PM +0300, Martin-Éric Racine wrote:
> Alexandre,
>
> Thanks for fixing unstable.
>
> Unless I'm mistaken, I think that the second bug was intentionally
> cloned by Chris to track the issue in stable and oldstable. I'm thus
> not sure if it was meant to be
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 Sep 2021 09:57:42 +0200
Source: systemd-cron
Architecture: source
Version: 1.5.17-2
Distribution: unstable
Urgency: high
Maintainer: Debian Systemd Maintainers
Changed-By: Alexandre Detiste
Closes: 992748
On Wed, Sep 08, 2021 at 08:36:32AM +0200, Alexandre Detiste wrote:
> Hi.
>
> I will fix unstable today but I don't know how to learn again to fix the
> old releases in a timely maner between so many things to handle at home and
> work.
>
> Forking from old git tags and pasting the same new
Package: systemd-timesyncd
Version: 247.3-6
Severity: important
Hi!
On upgrade from Buster to Bullseye I have seen my machines, without Internet
ntp access, loose their time sync because of the upgrade.
On the upgrade to the new packages, the old /etc/systemd/timesyncd.conf file
which specifies
Am 08.09.21 um 14:04 schrieb Santiago Garcia Mantinan:
Package: systemd-timesyncd
Version: 247.3-6
Severity: important
Hi!
On upgrade from Buster to Bullseye I have seen my machines, without Internet
ntp access, loose their time sync because of the upgrade.
On the upgrade to the new packages,
Am 08.09.21 um 19:25 schrieb Michael Biebl:
We do have some custom maintainer scripts code where we try to preserve
local modifications:
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/systemd-timesyncd.postinst
Apparently this does not work properly.
Needless to
Package: systemd-cron
Version: 1.5.17-2
Followup-For: Bug #992748
Hi,
After the fix, I now have:
---
Preparing to unpack .../systemd-cron_1.5.17-2_amd64.deb ...
Unpacking systemd-cron (1.5.17-2) over (1.5.17-1) ...
Setting up
18 matches
Mail list logo
