Re: SOLVED: Re: Bug#8294: dpkg: Packages with epochs make old Debian installations not upgradable
On 25 Mar 1997, Guy Maor wrote:
> Michael Alan Dorman <firstname.lastname@example.org> writes:
> > This problem has already been solved by Guy, and the solution has been
> > posted to the list, and I believe put in the current policy/programmer
> > manuals.
> Not quite. This prevents an older version from attempting to install
> a package using epochs, but old versions of dselect are so broken that
> they will die if they see an epoched version in the available file.
> Downward incompatibilities in the Packages file aren't allowed so
> there's really no way to fix this.
Yes. This is the problem I was thinking of: The user selects "Update" in
his old dselect and dpkg won't work anymore. (I know how to fix this, but
probably our users don't know it.)
> (There actually is a way to fix it - by putting the epoch in a
> seperate field in the control file instead of attached to the version.
> The pre-epoch dpkg and dselect will both ignore unknown fields, but
> they will balk at upgrading one of these hypothetical "Epoch:" using
> packages. I don't know how hard it would be to implement something
> like this, but I don't think it's worth it.)
This seams to be the best solution.
Klee, is something like this easy to implement? We would have to do this
change _before_ 1.3.
-- Christian Schwarz
Don't know Perl? email@example.com, firstname.lastname@example.org
Visit PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA