Re: Comments on Debian 2.2/potato release notes
On Thu, Aug 17, 2000 at 12:36:08PM -0400, G. Del Merritt wrote:
> 1) Under section 3.2, "Necessary actions prior to the upgrade", you write:
> You should not do the upgrade using telnet, rlogin, rsh, or from an
> X session managed by xdm on the machine you are upgrading. That is
> because each of those services may well be terminated during the
> upgrade, which can result in an inaccessible system that is only
> half-upgraded.
>
> I installed slink from CD and then upgraded to potato several months
> ago; my experience indicated that you could not reliably do an apt-get
> from a GNU/Emacs shell buffer. I reported this issue, but, being new
> to the Debian world, I do not know if it was fixed or not. Joey Hess
> was helping me with this in June, bug #60963.
It seems this wasn't fixed in potato. I've added this info to the release
notes (in CVS) now, thanks.
> 2) A little later in section 3.2 you write:
> It is desirable to remove any holds before upgrading. If any package
> that is essential for the upgrade is on hold, the upgrade will fail.
> If you changed and recompiled a package locally, and didn't rename
> it or put an epoch in the
>
> This is confusing, since you suggest putting a hold on ssh.
Ssh is an exception to the rule...
> Given that suggestion, it seems that the paragraph in question might be
> better worded as:
> It is desirable to remove any holds before upgrading. If any package
> that is essential for the upgrade is on hold, the upgrade FOR THAT
> PACKAGE will fail. If you changed and recompiled a package locally,
> and didn't rename ...
>
> Obviously, you don't need to shout; I did all caps to highlight the
> change...
Upgrade for that package and for all packages depending on it, which is
usually a big bunch.
> Many thanks for your efforts; it's delightful to have this level of
> documentation available!
Glad to hear that :)
--
Digital Electronic Being Intended for Assassination and Nullification
Reply to: