time-epoch never changes in SRUs

[Dimitri John Ledkov]

[Impact]

 * Systems without hwclock come up with a fixed time epoch which is not updated in SRUs
 * Ideally booting with a newer built of systemd should move time epoch to be at least when systemd was last built. For example to the value of SOURCE_DATE_EPOCH.

[Test Case]

 * Boot without network NTP or hwclock
 * Observe that the epoch is the same as the time when NEWS entry in the systemd source code was last touched.
 * Boot newer update of systemd, observe that the time epoch is at least 2020

[Regression Potential]

 * Bad epoch, may result in unable to perform TLS connections, validated GPG signatures, and snapd assertions. Changing epoch to be more recent is desired. Some machines may rely on the fact that "bionic" without hwclock always comes up in year 2018. But in practice that is incorrect thing to do.

[Other Info]

 * By default

option('time-epoch', type : 'integer', value : '-1',
       description : 'time epoch for time clients')

in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value to be compliant with the https://reproducible-builds.org/docs/timestamps/ specification.

[Dimitri John Ledkov (xnox)]

https://github.com/systemd/systemd/pull/15827

[Dimitri John Ledkov (xnox)]

Thank you balint for cherrypicking this! It builds with the debian/changelog time in groovy now!

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 245.5-3ubuntu1

---------------
systemd (245.5-3ubuntu1) groovy; urgency=medium

  [ Dan Streetman ]
  * Hotadd only offline memory and CPUs (LP: #1876018)
    File: debian/extra/rules-ubuntu/40-vm-hotadd.rules
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dc68569fb46b04791202a40326003799becae859

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian unstable
  - Dropped changes:
    * Cherry-pick fix from upstream master to adjust UseGateway= default
  * journald: stream pid change newline fix (LP: #1875708)
    Files:
    - debian/patches/debian/fsckd-daemon-for-inter-fsckd-communication.patch
    - debian/patches/lp1875708/journald-Increase-stdout-buffer-size-sooner-when-almost-f.patch
    - debian/patches/lp1875708/journald-rework-end-of-line-marker-handling-to-use-a-fiel.patch
    - debian/patches/lp1875708/journald-rework-pid-change-handling.patch
    - debian/patches/lp1875708/journald-use-log_warning_errno-where-appropriate.patch
    - debian/patches/lp1875708/journald-use-the-fact-that-client_context_release-returns.patch
    - debian/patches/lp1875708/man-document-the-new-_LINE_BREAK-type.patch
    - debian/patches/lp1875708/socket-util-introduce-type-safe-dereferencing-wrapper-CMS.patch
    - debian/patches/lp1875708/test-Add-a-test-case-for-15654.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=95302fbe53202bdac33f86031aa56026444a92d3

  [ Dimitri John Ledkov ]
  * meson: initialize time-epoch to reproducible builds compatible value
    (LP: #1878969)
    File: debian/patches/meson-initialize-time-epoch-to-reproducible-builds-compat.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6785dfd98f81dfe3e3d5273511ec33b196ddb0c3

systemd (245.5-3) unstable; urgency=medium

  [ Michael Biebl ]
  * Bump priority of libnss-systemd to standard
  * logind: avoid shadow lookups when doing userdb client side
  * Disable DNSSEC support by default in resolved.
    The upstream default, DNSSEC=allow-downgrade can lead to compatibility
    issues with certain network access points. Previously, DNSSEC support
    was only turned off when built for a stable Debian release, but it is
    safer and more consistent to just generally change the default to
    DNSSEC=no. (Closes: #959996)
  * Bump debhelper compatibility level to 13.
    Use the debhelper-compat package to declare the compatibility level and
    drop debian/compat.
  * Convert to dh_installsystemd and disable dh_installsystemduser
  * Drop custom initramfs update code.
    Now handled by dh_installinitramfs which is enabled by default in compat
    level 12 and above.

  [ Dan Streetman ]
  * Cherry-pick fix from upstream master to adjust UseGateway= default
    - network: change UseGateway= default to UseRoutes= setting
    - network: honor SetDNSRoutes= even if UseGateway=False
    (LP: #1867375)

  [ Topi Miettinen ]
  * Delete empty lines at end of file.
    Upstream commit hooks don't allow empty lines and of course they serve no
    purpose.

 -- Balint Reczey <email address hidden> Tue, 19 May 2020 19:43:50 +0200

[Ian Johnson (anonymouse67)]

Is there any timeline on when this will be considered for SRU'ing back to focal so it is usable in i.e. UC20?

[Dimitri John Ledkov (xnox)]

with core-initrd v40, each new initrd build increases time epoch.

This still means that for brand new account keys, one needs to wait or build a new kernel to be able to boot in UC20.

[Łukasz Zemczak (sil2100)]

Hello Dimitri, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Dimitri, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x)
linux-hwe-5.0/5.0.0-65.71 (i386)
linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
docker.io/19.03.8-0ubuntu1.20.04.2 (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Dan Streetman (ddstreet)]

@xnox can you verify this bug

[Dan Streetman (ddstreet)]

focal:

$ pull-lp-source systemd 245.4-4ubuntu3.4
...
$ stat -c '%y' systemd-245.4/NEWS
2020-04-01 13:23:42.000000000 -0400

$ lxc launch --vm ubuntu:focal lp1878969-f
...
$ lxc exec lp1878969-f systemctl disable systemd-timesyncd
Removed /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service.
Removed /etc/systemd/system/dbus-org.freedesktop.timesync1.service.

$ lxc stop lp1878969-f
$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start lp1878969-f
$ lxc console lp1878969-f
...
ubuntu@lp1878969-f:~$ dpkg -l systemd|grep systemd
ii systemd 245.4-4ubuntu3.4 amd64 system and service manager
ubuntu@lp1878969-f:~$ date
Wed Apr 1 17:24:01 UTC 2020

From https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5
" -- Ioanna Alifieraki <email address hidden> Tue, 23 Feb 2021 00:18:57 +0000"

$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start lp1878969-f
$ lxc console lp1878969-f
...
ubuntu@lp1878969-f:~$ systemctl status systemd-timesyncd.service --no-pager
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-timesyncd.service(8)
ubuntu@lp1878969-f:~$ dpkg -l systemd|grep systemd
ii systemd 245.4-4ubuntu3.5 amd64 system and service manager
ubuntu@lp1878969-f:~$ date
Tue Feb 23 00:19:42 UTC 2021

[Dan Streetman (ddstreet)]

bionic:

$ pull-lp-source systemd 237-3ubuntu10.44
...
$ stat -c '%y' systemd-237/NEWS
2018-01-28 10:58:17.000000000 -0500

$ lxc launch --vm ubuntu:bionic lp1878969-b
...
ubuntu@lp1878969-b:~$ sudo systemctl disable systemd-timesyncd
Removed /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service.

$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start lp1878969-b
$ lxc console lp1878969-b
...
ubuntu@lp1878969-b:~$ dpkg -l systemd|grep systemd
ii systemd 237-3ubuntu10.44 amd64 system and service manager
ubuntu@lp1878969-b:~$ date
Sun Jan 28 15:58:40 UTC 2018

From https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45
" -- Ioanna Alifieraki <email address hidden> Tue, 23 Feb 2021 03:45:01 +0200"

$ date
Mon Jan 1 00:03:39 UTC 1990
$ lxc start lp1878969-b
$ lxc console lp1878969-b
...
ubuntu@lp1878969-b:~$ systemctl status systemd-timesyncd --no-pager
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:systemd-timesyncd.service(8)
ubuntu@lp1878969-b:~$ dpkg -l systemd|grep systemd
ii systemd 237-3ubuntu10.45 amd64 system and service manager
ubuntu@lp1878969-b:~$ date
Tue Feb 23 01:45:52 UTC 2021

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 245.4-4ubuntu3.5

---------------
systemd (245.4-4ubuntu3.5) focal; urgency=medium

  [ Ioanna Alifieraki ]
  * d/p/lp1911187-systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch:
    Do not shutdown immediately when scheduled shutdown fails (LP: #1911187)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3899c9d5c171e84fc503c6ab46aea7cc9def7235

  [ Dimitri John Ledkov ]
  * d/p/lp1878969-meson-initialize-time-epoch-to-reproducible-builds-compat.patch:
    meson: initialize time-epoch to reproducible builds compatible value
    (LP: #1878969)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=84212797d21ed08031e1d71fe5e118bdd9873c0f

  [ Dan Streetman ]
  * d/p/lp1913189-test-accept-that-char-device-0-0-can-now-be-created-.patch:
    - Fix failing test case under 5.8 kernel (LP: #1913189)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=782a382017ce188dbf9a40adabd265943d7db119
  * d/p/lp1913423-hashmap-make-sure-to-initialize-shared-hash-key-atom.patch:
    Thread-safe init of hashmap shared key (LP: #1913423)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fc8dde7c4b1944d1583866f61c2314174b4dd06a
  * d/p/lp1902236-nss-systemd-don-t-synthesize-root-nobody-when-iterat.patch:
    Don't synthesize root/nobody when iterating (LP: #1902236)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4d20e415ecd5b0fd032b4cf45bd9fd344cc434ac
  * d/p/debian/patches/lp1880258-log-nxdomain-as-debug.patch:
    Change NXDOMAIN 'errors' to log level debug (LP: #1880258)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80163a2097aa876fe73b6071495ae4ad8749d04e
  * d/p/lp1913763-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
    Create symlink for hyperv-provided ptp device (LP: #1913763)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b02053da2ff3fee6221bd8310488af0f52b140f1

 -- Ioanna Alifieraki <email address hidden> Tue, 23 Feb 2021 00:18:57 +0000

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 237-3ubuntu10.45

---------------
systemd (237-3ubuntu10.45) bionic; urgency=medium

  [ Ioanna Alifieraki ]
  * d/p/lp1911187-systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch:
    Do not shutdown immediately when scheduled shutdown fails (LP: #1911187)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=257135a59455f4e4063e78cdd3f5cfeca2597b5b

  [ Dimitri John Ledkov ]
  * d/p/lp1878969-meson-initialize-time-epoch-to-reproducible-builds-compat.patch:
    meson: initialize time-epoch to reproducible builds compatible value
    (LP: #1878969)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6f5a0c94ff4a486ee0b72af926672b24d16ff5a8

  [ Dan Streetman ]
  * d/p/lp1913189-test-accept-that-char-device-0-0-can-now-be-created-.patch:
    - Fix failing test case under 5.8 kernel (LP: #1913189)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15143ec6cd584a18866390a042348a543e5aa22d
  * d/p/lp1913423-hashmap-make-sure-to-initialize-shared-hash-key-atom.patch:
    Thread-safe init of hashmap shared key (LP: #1913423)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=95c189adb9c3e22576b26b084c7edf001cbc8307
  * d/p/lp1890448-hwdb-Add-EliteBook-to-use-micmute-hotkey.patch:
    Add EliteBook to use micmute hotkey (LP: #1890448)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19b48bdac5129aa772fbcd2dbf8d1bb5c30c1510
  * d/p/debian/patches/lp1902553-test-disable-QEMU-based-testing-for-TEST-16-EXTEND-T.patch:
    Disable TEST-03 run under qemu (LP: #1902553)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4e37d20ec379d169cfd53088d0c3b4d7bb65d25b
  * d/p/debian/patches/lp1883447-seccomp-add-all-time64-syscalls.patch:
    Add *time64 syscalls (LP: #1883447)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a459492c67c5c5855b03daca4b44141705495376
  * d/p/lp1685754-pid1-by-default-make-user-units-inherit-their-umask-.patch:
    Inherit umask for --user processes (LP: #1685754)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00df8d0e76975594adb765182c587ef495262fe1
  * d/p/debian/patches/lp1880258-log-nxdomain-as-debug.patch:
    Change NXDOMAIN 'errors' to log level debug (LP: #1880258)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9684abed02669bfcf696763b887518cf54cd3f69
  * d/p/lp1913763-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
    Create symlink for hyperv-provided ptp device (LP: #1913763)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff2a9ed2ece6bbd86a3d57f42b26cb1a6ca2845a

 -- Ioanna Alifieraki <email address hidden> Tue, 23 Feb 2021 03:45:01 +0200

[Łukasz Zemczak (sil2100)]

Hello Dimitri, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.30 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

upstart/unknown (armhf)
umockdev/0.8.11-2 (i386)
systemd/229-4ubuntu21.30 (amd64)
linux-aws-hwe/unknown (arm64)
snapd/2.48.3 (i386)
gvfs/1.28.2-1ubuntu1~16.04.3 (amd64)
cloudprint/0.14-5 (ppc64el)
nplan/0.32~16.04.7 (ppc64el, amd64)
cups/2.1.3-4ubuntu0.11 (ppc64el)
apt/1.2.32ubuntu0.2 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Dan Streetman (ddstreet)]

xenial:

$ pull-lp-source systemd 229-4ubuntu21.30
...
$ stat -c '%y' systemd-229/NEWS
2016-02-11 11:28:00.000000000 -0500

$ lxc launch --vm ubuntu:xenial lp1878969-x

$ lxc console lp1878969-x
...
ubuntu@lp1878969-x:~$ sudo systemctl disable systemd-timesyncd.service
Removed symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service.

$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start lp1878969-x
$ lxc console lp1878969-x
...
ubuntu@lp1878969-x:~$ dpkg -l systemd|grep systemd
ii systemd 229-4ubuntu21.29 amd64 system and service manager
ubuntu@lp1878969-x:~$ date
Thu Feb 11 16:28:17 UTC 2016

From https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.30
" -- Dan Streetman <email address hidden> Wed, 17 Mar 2021 17:41:20 -0400"

$ date
Mon Jan 1 00:03:49 UTC 1990
$ lxc start lp1878969-x
$ lxc console lp1878969-x
...
ubuntu@lp1878969-x:~$ dpkg -l systemd|grep systemd
ii systemd 229-4ubuntu21.30 amd64 system and service manager
ubuntu@lp1878969-x:~$ date
Thu Feb 11 16:28:40 UTC 2016

verification failed, unfortunately; the patch didn't properly set the time epoch.

[Dan Streetman (ddstreet)]

Minor correction to the patch:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30bf11d2759499ec94d3b82eaf22f55583f4758b

Uploaded as the next xenial version to the upload queue

[Brian Murray (brian-murray)]

Hello Dimitri, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.31 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

linux-aws-hwe/unknown (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Dan Streetman (ddstreet)]

$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start ubuntu
$ lxc console ubuntu
ubuntu@ubuntu:~$ dpkg -l systemd|grep systemd
ii systemd 229-4ubuntu21.29 amd64 system and service manager
ubuntu@ubuntu:~$ date
Thu Feb 11 16:28:20 UTC 2016

From https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.31
" -- Dan Streetman <email address hidden> Thu, 01 Apr 2021 22:51:58 -0400"

$ sudo date -s '1990-01-01'
Mon Jan 1 00:00:00 UTC 1990
$ lxc start ubuntu
$ lxc console ubuntu
ubuntu@ubuntu:~$ dpkg -l systemd|grep systemd
ii systemd 229-4ubuntu21.31 amd64 system and service manager
ubuntu@ubuntu:~$ date
Fri Apr 2 02:52:11 UTC 2021

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (229-4ubuntu21.31) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

conntrack-tools/unknown (armhf)
pyudev/unknown (armhf)
linux-aws-hwe/unknown (arm64)
kwin/unknown (armhf)
nplan/0.32~16.04.7 (amd64, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 229-4ubuntu21.31

---------------
systemd (229-4ubuntu21.31) xenial; urgency=medium

  * d/p/lp1878969-time-epoch-use-source-date-epoch.patch:
    - Fix configure.ac change to set time epoch
      (LP: #1878969)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30bf11d2759499ec94d3b82eaf22f55583f4758b

systemd (229-4ubuntu21.30) xenial; urgency=medium

  * d/p/lp1878969-time-epoch-use-source-date-epoch.patch:
    - Set time epoch using $SOURCE_DATE_EPOCH
      (LP: #1878969)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9e1ad364d94b3619947c541b72aa506010ee3f38
  * d/p/lp1913763-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
    - Create symlink for hyperv-provided ptp device
      (LP: #1913763)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ae39f8878ca5dabb4e9d8ba5ebdb6ed003993b9f

 -- Dan Streetman <email address hidden> Thu, 01 Apr 2021 22:51:58 -0400