Bug#421280: More info
Bill Brelsford a écrit :
> On Fri May 04 2007 at 02:00 AM +0200, Aurelien Jarno wrote:
>> If somebody is reading this bug log and still having the problem,
>> could you please send me the output of:
>> ls -l /etc/localtime
> lrwxrwxrwx 1 root root 24 Apr 14 18:22 /etc/localtime -> /usr/local/etc/localtime
> lrwxrwxrwx 1 root root 30 May 1 2006 /usr/local/etc/localtime -> /usr/share/zoneinfo/US/Pacific
> -rw-r--r-- 1 root root 1017 Apr 25 10:35 /usr/share/zoneinfo/US/Pacific
> -rw-r--r-- 1 root root 1017 Apr 14 18:21 /tmp/localtime
> This is on a laptop. I point to the common /usr/local/etc/localtime
> from stable, testing and unstable partitions so I can change
> timezones from one and keep all three up-to-date. On upgrade, when
> necessary, I save /etc/localtime in /tmp and re-define the symlink.
> Here /tmp/localtime (/etc/localtime from the Apr 14 2007e-3 upgrade)
> is identical to zoneinfo/US/Pacific. Pacific was replaced during
> the attempted Apr 30 e-6 upgrade, but /etc/localtime was not.
>> cat /etc/timezone
> Upgrades continue to fail, since aptitude first tries to configure
> tzdata and dies.
Thanks for the debugging info, I have been able to reproduce and fix the
The config script was messed by the fact that /etc/localtime was a
symlink and pointed outside of /usr/share/zoneinfo. Such situations are
now detected correctly, and moreover /etc/localtime is not modified
anymore during the upgrade, unless you use 'dpkg-reconfigure tzdata' to
change the timezone.
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' email@example.com | firstname.lastname@example.org
`- people.debian.org/~aurel32 | www.aurel32.net