Re: Timezone upgrading problem
-----BEGIN PGP SIGNED MESSAGE-----
On 25 Jan 1998, Greg Stark wrote:
> firstname.lastname@example.org writes:
> > In fact, while it is true that, selecting timezones, the old package
> > goes correctly replaced
> Actually in my case I had to recreate the /etc/localtime link.
> At least I assume there was one before, I never checked.
> It might also be because dselect didn't automatically replace timezone, it
> just uninstalled it. Leaving its conffiles. Later i got fed up with having
> another removed/obsolete package so I purged it. That may have removed the
An empty "timezone" package with version number 99 could be created, so
that timezones conflicts with the old timezone but not with the new
This dummy "timezone" package would have no conffile at all, and upgrading
from the old one to the new one would keep /etc/timezone in place.
Moreover, it would be great if the new timezones package (the one from
glibc) would not have /etc/timezone inside the package but it is created
in the postinst. This reduces dpkg prompting when upgrading, which is a
requirement of our policy.
Would there be any problem with this?
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .