[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#541436: marked as done (clock-setup: should not change hardware clock if the system time is not updated)

Your message dated Wed, 02 Sep 2009 16:54:02 +0000
with message-id <E1Mit5u-0000Ub-Ig@ries.debian.org>
and subject line Bug#541436: fixed in clock-setup 0.100
has caused the Debian Bug report #541436,
regarding clock-setup: should not change hardware clock if the system time is not updated
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 owner@bugs.debian.org
immediately.)


-- 
541436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541436
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: clock-setup

From a thread in -boot:

> On Thursday 13 August 2009, Uwe Bugla wrote:
> > a. as default installation I always use expert install
> > b. the NTP question I always answer with "Yes". The installer tells me
> > that my local time zone is "Europe / Berlin"
> > c. The UTC question I always answer with no, without having some crap
> > like Windoze installed on my HD. The question of what makes sense and
> > what does not I do leave open.....
> 
> Using local time for your hardware clock when you're only running Linux 
> really makes no sense at all.
> 
> The most obvious example is a notebook that you travel around with. If the 
> hardware clock is set to UTC you can take the notebook anywhere around 
> the world and always have the correct local time simply by changing the 
> time zone.
> 
> But even for systems that don't travel local time does not make any sense. 
> Why would you want to change the hardware clock when summer time 
> starts/ends? It does not improve the way the system is used in any way.
> 
> > d. After the installation is finished the clock setting of my BIOS was
> > trimmed by 2 hours which I wanted to avoid.
> 
> I agree that what you describe looks like a bug.
> 
> I suspect that the cause is the following:
> - the installer itself has no knowledge of timezones, it just runs in
>   "current" time, taken either from the hardware clock or rdate
> - rdate always updates the system time to UTC
> - we update the hardware clock from the /target chroot *after* configuring
>   the chroot to reflect that the hardware clock is supposed to be in local
>   time, but the time that gets written is the system's current time, which
>   is UTC.
> 
> So basically finish-install.d/10clock-setup is wrong and should run 
> hwclock --systohc --utc _before_ changing the local/utc setting in
> /etc/adjtime.
> But that should be done *only* if rdate was run successfully. In fact, I 
> don't think there is any reason to write the hardware clock at all if the 
> system time was not updated by rdate.
> 
> Uwe: please file a bug report against clock-setup with the details of the 
> problem, including the description of the choices you make during 
> installation and my analysis.


Well, I think that all needed info is in the above quote, so I take
responsibility for opening that bug (will reassign it to Uwe as
submitter). Uwe, no need for you to do it.

I agree with Frans (who, btw, corrected me on one point: when Windows
is detected on the system, defaults installs do *not* prompt about the
HW clock being UTC or not....as Windows nearly enforces having the HW
clock set to local time). We apparently have a bug here, that was not
discovered because very few people have the local time for the HW
clock.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: clock-setup
Source-Version: 0.100

We believe that the bug you reported is fixed in the latest version of
clock-setup, which is due to be installed in the Debian FTP archive:

clock-setup_0.100.dsc
  to pool/main/c/clock-setup/clock-setup_0.100.dsc
clock-setup_0.100.tar.gz
  to pool/main/c/clock-setup/clock-setup_0.100.tar.gz
clock-setup_0.100_amd64.udeb
  to pool/main/c/clock-setup/clock-setup_0.100_amd64.udeb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 541436@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frans Pop <fjp@debian.org> (supplier of updated clock-setup package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 02 Sep 2009 17:02:42 +0200
Source: clock-setup
Binary: clock-setup
Architecture: source amd64
Version: 0.100
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Frans Pop <fjp@debian.org>
Description: 
 clock-setup - set up clock (udeb)
Closes: 541436
Changes: 
 clock-setup (0.100) unstable; urgency=low
 .
   * finish-install: there's no need anymore to create a /dev/rtc symlink.
   * finish-install: don't modify /target/etc/adjtime directly. First of all
     it does not yet exist, and calling hwclock with the correct option has
     the same effect anyway. Closes: #541436.
   * finish-install: only set the hardware clock if the system time was
     updated using rdate.
 .
   [ Updated translations ]
   * Asturian (ast.po) by Marcos Antonio Alvarez Costales
   * Korean (ko.po) by Changwoo Ryu
Checksums-Sha1: 
 81d53612168b02e9a908f1cb079698970dcc8e79 861 clock-setup_0.100.dsc
 e276bf6e8869100eda2a60e04d52d23b6dbb5b23 73582 clock-setup_0.100.tar.gz
 4cc3b3951ba45059fb89a047339e6bb84162a032 51806 clock-setup_0.100_amd64.udeb
Checksums-Sha256: 
 de77cecd252474a85faaec4027408918664113812eff19f00d07dcc9639cabca 861 clock-setup_0.100.dsc
 341fa64b5091a2556321c29d3c8e71220b050e143b862559cfde4e0b9b15f768 73582 clock-setup_0.100.tar.gz
 c5e5acb9e101447fbf73127a4528af75682a078cea871bc92404c4b7b90171b6 51806 clock-setup_0.100_amd64.udeb
Files: 
 f3a3af2970e6c99e9e6b536783d6d384 861 debian-installer standard clock-setup_0.100.dsc
 fa05c3cfedfa7aa99cc54162a33c928a 73582 debian-installer standard clock-setup_0.100.tar.gz
 262dfaee9aa4aeaecab45d51870ad69a 51806 debian-installer standard clock-setup_0.100_amd64.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqeiTIACgkQgm/Kwh6ICoRvrwCeMPO6GxickvcPyXm9c5oCMGu3
fqwAoMM53EeJL2CrNhY9ABXT6lKn8DE0
=ZPpK
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: