Re: post-release package update policy
firstname.lastname@example.org (Dale Scheetz) wrote on 28.10.95 in <Pine.LNX.3.91.951028130436.8075A-100000@localhost>:
> On 28 Oct 1995, Kai Henningsen wrote:
> > email@example.com (Dale Scheetz) wrote on 26.10.95 in
> > > > [...]
> > > > > Product is. While trying to build a system, dpkg changed enough to
> > > > > loose it's old database (rather than provide a conversion) and
> > > > > "forgot" that it had installed the base package. When I went to
> > > > > remidy that problem, the only
> > > > [...]
> > Why do you think this wouldn't have hapened with the "release" package?
> Because the base package that WAS installed (even though dpkg didn't know
> it was) was working fine at the time I upgraded to the "new" base
> package. If that had been the "release" version, and were available on
> the ftp site, I could have simply reinstalled it.
Umm ... I thought the problem was that for whatever reason, dpkg "lost its
memory". (Besides, IIRC, it is still an open question why this happened
in the first place.)
In the first place, I don't really understand what sort of "going back and
reinstall" would make anything better here.
Secondly, you can only "go back" as long as what you want to go back to is
not only a release, but a release new enough to still be on the server.
> > Why could you not go back to whatever package you had installed
> > previously?
> It was originaly obtained via winsock ftp tranfered to floppy and
> installed. The floppies were never expected to hold the data for longer
> than was necessary to tranfer it and are no longer available.
So, it's because you decided not to save the stuff.
(And I repeat, I simply do not see how having those original packages
around would have helped you.)