On Tue, 30 Dec 1997, Yann Dirson wrote:
> Robert D. Hilliard writes:
> > This is Bug#16260.
>
> Is this really a bug in timezones ? It seems quite similar to the
> problem I have myself (as the maintainer - never heard of anyone else
> speaking on this) while upgrading e2fsprogs to 1.10-9. I thought it
> might have been a bug in dpkg's dependency mechanism; I guess I
> reported that, but can't find out a copy in my folders, neither can I
> find it from the headers in "Unanswered pbs"...
I encountered this, among other problems, while testing the
rex==>>hamm upgrade path. When I posted my problems and asked for
comments, I was advised that it appeared to be a bug. Timezones
replaces and conflicts with timezone; since timezone is an essential
package, it was suggested that timezones should also provide timezone,
which would cause dpkg to remove essential package timezone in favor
of timezones.
I also encountered the e2fsprogs problem during my testing. I
posted that problem as follows:
"The rex system had e2fsprogs v1.06-3 installed, and version
1.10-9 was selected for installation. e2fslibsg was also selected for
installation. e2fslibsg conflicts with e2fsprogs (<= 1.10-7), so
dselect removed e2fsprogs v1.06-3. In the process, the selection of
1.10-9 was lost, so that the message "Skipping deselected package
e2fsprogs." was issued when it reached that program."
I have not filed a bug regarding this problem, since I wasn't
sure where the bug was. The dependency information for e2fsprogs
seems to be correct, and I doubt if it is a bug in dpkg, since similar
replacements are handled routinely by dpkg without problems.
Bob
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
