:: Re: [DNG] Only a few packages now s…
Forside
Slet denne besked
Besvar denne besked
Skribent: Arnt Karlsen
Dato:  
Til: dng
Emne: Re: [DNG] Only a few packages now still on hold
On Sun, 1 Aug 2021 21:58:47 -0400, Hendrik wrote in message
<20210802015847.d7gxxdu7ts753dt3@???>:

> On Sun, Aug 01, 2021 at 09:54:33PM -0400, Hendrik Boom wrote:
> > On Sun, Aug 01, 2021 at 01:13:26PM -0400, Hendrik Boom wrote:
> > > On Sun, Aug 01, 2021 at 05:33:23PM +0200, Bernard Rosset via Dng
> > > wrote:
> > > > On 31/07/2021 22:03, Hendrik Boom wrote:
> > > > > I'm practicing upgrades on my spare laptop, getting ready for
> > > > > doing my server upgrade from ascii to beowulf..
> > > > >
> > > > > They are both running ascii.
> > > > >
> > > > > Starting, of course, by making the ascii up to date still as
> > > > > ascii, before I try tye upgrade to beowulf.
> > > > >
> > > > > Having trouble doing even this innocuous act.
> > > > >
> > > > > I tried starting by using interactive aptitude to just update
> > > > > and upgrade.
> > > >
> > > > After changing your sources to point to the new release,
> > >
> > > I have not yet changed my sources. I figured I should make sure
> > > the ascii system is up-to-date as an ascii system before I start
> > > to upgrade to beowulf.
> > >
> > > > have you run
> > > > "apt-get upgrade" or "apt-get dist-upgrade"?
> > > > It looks to me as if you did the former.
> > >
> > > I used the update and upgrade inside the interactive aptitude.
> > >
> > > I guess I have to do dist-upgrade outside the interacctive
> > > aptitude.
> >
> > And today I did aptitude update and aptitude upgrade in the CLI
> > instead of in the interactive apttude. Just about everything just
> > worked, except for 3 packages:
> > elogind
> > libpam-elogind
> > libelogind0
> > They do nog get upgraded.
> >
> > Following this with
> > aptitude dist-upgrade
> > tells me these will be upgraded, but then balks, telling me to
> > remove libpam-elogind
>
> This is what it says:
>
> root@notlookedfor:~# aptitude dist-upgrade
> The following packages will be upgraded:
> elogind libelogind0 libpam-elogind{b}
> 3 packages upgraded, 0 newly installed, 0 to remove and 0 not
> upgraded. Need to get 861 kB of archives. After unpacking 0 B will be
> used. The following packages have unmet dependencies:
> libpam-elogind : Breaks: libpam-ck-connector but 0.4.6-6 is installed
> The following actions will resolve these dependencies:
>
>      Remove the following packages:            
> 1)     libpam-elogind [234.4-1+devuan1.5 (now)]


..this IME often happens when a newer version needs the old version
stopping it's service(s) and a purge before installing and starting
up the new version.

>
>
> Accept this solution? [Y/n/q/?]


..hit [q], then restart aptitude in the interactive mode, mark
libpam-elogind [234.4-1+devuan1.5 (now)] for removal, as it whines
"Error", hit [e] and browse aptitude's suggestions with [,] and [.]
to see if you can agree on any solution, if not, [q] out and find
aptitude's opinion on "Broken packages" with [B].

..my _guess_ is you may be able to find old lib config files
blocking the removal of libpam-ck-connector or some such.
Purge them.

..hitting [e] and then [Enter] on a package, will find possible
version numbers of that package at the bottom, picking another
newer or older version may also solve your conflict.

..as Tito, Mark, Tom, Rod and I advices, apt, apt-get and probably
a few more, solves package conflicts differently from each other
and from aptitude, IME I can often use e.g. apt-get or even dpkg
when aptitude fails me. Options I remember throwing around also
includes --safe-update and --full-update.

> >
> > How safe is this? isn't elogind kind of important?
> >
> > I'm still just upgrading from ascii to ascii. Beowulf is not in my
> > sights yet.
> >
> > -- hendrik



--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.