On Mon, Jul 31, 2006 at 11:54:06AM -0400, Juergen Fiedler wrote: > On Mon, Jul 31, 2006 at 11:13:30AM -0400, Matej Cepl wrote: > > Jon Dowland wrote: > > > Please note that you are advised to *not do this*, but to > > > *always* read the release notes for the relevant > > > > you certainly noticed that I had there aptitude upgrade (not dist-upgrade), > > right? > > It should be noted that the names for the operations are somewhat > misleading: 'aptitude upgrade' will happily upgrade your packages > across release boundaries (i.e., from woody to sarge). If I remember > correctly, 'dist-upgrade' got its name because it is smarter about > resolving the vast numbers of potentially altered dependencies; thus, > it makes upgrading to a new release easier (typically), but it is > certainly not the only tool to do it.
I remember I did the sarge->etch upgrade when etch wasn't stable yet. aptitude dist-upgrade did most of it, but then a few things still remained unupdated. Repeating aptitude dist-upgrade seemed to do the trick. All except a few holdouts whuch succumbed to an aptitude upgrade a few weeks later. Before etch becomes stable, all this kind of glitch should have been ironed out. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
