Re: switching flavors
On Wed, Jun 07, 2017 at 08:57:40AM +0900, Mark Fletcher wrote:
> On Tue, Jun 06, 2017 at 04:55:01PM -0400, SDA wrote:
> > On Sun, Jun 04, 2017 at 06:44:10PM +0100, Joe wrote:
> > > On Sun, 4 Jun 2017 12:20:51 -0400
> > > SDA <marathon.durandal@gmail.com> wrote:
> > >
> > > > On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
> > > > > Yes - and based on some work I did earlier in the week if you keep
> > > > > the things simple I would say your upgrade should be uneventful.
> > > > >
> > > > > I changed the repo to unstable
> > > > >
> > > > > Then I did:
> > > > >
> > > > > apt-get update
> > > > >
> > > > > apt-get upgrade
> > > > >
> > > > > That was it.
> > > >
> > > > Nope, not done yet. You still need to do a full upgrade. In apt it's
> > > > 'apt full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure
> > > > what the eqivalent command is in apt-get.
> > > >
> > >
> > > Other way around, aptitude is safe-upgrade and full-upgrade, it's
> > > apt-get which has upgrade and dist-upgrade. apt mixes the two, with
> > > upgrade and full-upgrade.
> >
> > Not unless it was changed in aptitude just recently, (I've used it for years
> > prior). Aptitude has 'safe-upgrade' yes, but it also has 'upgrade' and
> > 'dist-upgrade'. So 3 options.
> >
>
> >From the man page for aptitude, search for dist-upgrade, in the section
> on full-upgrade -- "This command was originally named dist-upgrade for
> historical reasons, and aptitude still recognises dist-upgrade as a
> synonym for full-upgrade."
>
> The man page does not acknowledge just upgrade as a command. According
> to the man page, the two options are safe-upgrade and full-upgrade, but
> I can testify that upgrade still works (and I _think_ does a
> safe-upgrade).
Ah I see. Thanks Mark, it's been sometime since I've used Aptitude for
managing my packages.
Reply to: