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 <rbal...@ubuntu.com> Tue, 19 May 2020 19:43:50 +0200 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1878969 Title: time-epoch never changes in SRUs Status in ubuntu-core-initramfs: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: New 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/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp