Discussion:
Processed: Re: Bug#828746: hwclock: RTC to wrong offset after reboot
(too old to reply)
Debian Bug Tracking System
2020-05-04 08:20:02 UTC
Permalink
tags -1 moreinfo
Bug #828746 [release-notes] hwclock: RTC to wrong offset after reboot
Ignoring request to alter tags of bug #828746 to the same tags previously set
--
828746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828746
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Andrei POPESCU
2020-05-04 08:20:02 UTC
Permalink
Control: tags -1 moreinfo

[not trimming to preserve context for -doc]
Control: tags -1 + moreinfo
Please check the contents of your /etc/adjtime for starters.
UTC as expected.
Given you're using systemd you're not even running hwclock during your
boot. Please see 'systemctl status hwclock.service'.
Please read up on the RTC handling strategy usually deployed when using
systemd. Please read the information already provided in misc bug
reports filed by people requesting to emulate the old strategy used by
https://wiki.archlinux.org/index.php/time
https://www.freedesktop.org/software/systemd/man/timedatectl.html
https://www.freedesktop.org/wiki/Software/systemd/timedated/
https://wiki.archlinux.org/index.php/systemd-timesyncd
Right. So systemd uses an entirely different strategy for time
adjustment than sysvinit did, in addition to which it comes with a
built-in NTP client (disabled by default on Debian, for whatever
reason) that can replace standalone NTP daemons. Great. Nice
features but they are badly documented, from the perspective of
systems that were migrated from sysvinit.
How much of this is still applicable for buster (or bullseye)?
At this point, I'm tempted to reassign this bug to release-notes,
since the migration on Debian from sysvinit as default to systemd as
default should have explained this, including the justification for
not enabling the built-in NTP client by default.
As you seem to be familiarised with the issue it would help a lot if you
provided a paragraph or two describing the issue and what admins have to
do.

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Debian Bug Tracking System
2021-03-13 22:00:01 UTC
Permalink
Your message dated Sat, 13 Mar 2021 22:48:10 +0100
with message-id <09596f35-fc42-a9f6-06a1-***@debian.org>
and subject line release notes bug for EOL Debian release
has caused the Debian Bug report #828746,
regarding hwclock: RTC to wrong offset after reboot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
828746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828746
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2021-03-13 22:00:01 UTC
Permalink
Your message dated Sat, 13 Mar 2021 22:48:10 +0100
with message-id <09596f35-fc42-a9f6-06a1-***@debian.org>
and subject line release notes bug for EOL Debian release
has caused the Debian Bug report #865120,
regarding release-notes: document i386/amd64 kernel changes for jessie->stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
865120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865120
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2021-03-13 22:00:02 UTC
Permalink
Your message dated Sat, 13 Mar 2021 22:48:10 +0100
with message-id <09596f35-fc42-a9f6-06a1-***@debian.org>
and subject line release notes bug for EOL Debian release
has caused the Debian Bug report #864160,
regarding Release notes should document how to compile 3rd party software against OpenSSL
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
864160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864160
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2021-03-13 22:00:02 UTC
Permalink
Your message dated Sat, 13 Mar 2021 22:48:10 +0100
with message-id <09596f35-fc42-a9f6-06a1-***@debian.org>
and subject line release notes bug for EOL Debian release
has caused the Debian Bug report #868817,
regarding release-notes: Example emulate3buttons snippet should include option "scrollmethod" "none"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
868817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868817
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2021-03-13 22:00:02 UTC
Permalink
Your message dated Sat, 13 Mar 2021 22:48:10 +0100
with message-id <09596f35-fc42-a9f6-06a1-***@debian.org>
and subject line release notes bug for EOL Debian release
has caused the Debian Bug report #864307,
regarding release-notes: Document openssh regression
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
864307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864307
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...