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. ** Changed in: systemd (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1878969 Title: time-epoch never changes in SRUs Status in ubuntu-core-initramfs: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
