:: Re: [DNG] problem with apt after re…
Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: terryc
Fecha:  
A: dng
Asunto: Re: [DNG] problem with apt after restore after crashed disk...
On Thu, 1 Jul 2021 10:41:05 +0100 (BST)
Jim Jackson <jj@???> wrote:

> On Thu, 1 Jul 2021, terryc wrote:
>
> > On Thu, 1 Jul 2021 09:46:02 +0100 (BST)
> > Jim Jackson <jj@???> wrote:
> >
> > > On Wed, 30 Jun 2021, Arnt Karlsen wrote:
> > >
> > > > On Mon, 28 Jun 2021 23:12:28 +0100 (BST), Jim wrote in message
> > > > <alpine.DEB.2.21.2106282312080.2360@???>:
> > > >
> > > > > On Mon, 28 Jun 2021, tempforever wrote:
> > > > >
> > > > > > Jim Jackson wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, 28 Jun 2021, ael wrote:
> > > > > >
> > > > > > On Mon, Jun 28, 2021 at 01:11:20PM +0100, Jim Jackson wrote:
> > > > > >
> > > > > > If not, can anyone tell where I can get the devuan
> > > > > > libapt-pkg5.0 package file?    

> > > >
> > > > ..try "aptitude update &&aptitude download libapt-pkg5.0 \
> > > > &&ll |grep libapt-pkg ".
> > > >
> > >
> > > I don't have aptitude installed :-(
> >
> > Err try sudo "apt-get install aptitude"
>
> Err... that's the problem with quoting the original problem :-)
>
> # apt-get
> apt-get: relocation
> error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0: symbol
> _ZN3URIcvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
> version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link
> time reference
>
> # apt
> apt: relocation
> error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0: symbol
> _ZN3URIcvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev
> version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link
> time reference
>
> After a restore of a backup with saving capabilities or extended
> attributes apt and apt-get are not functioning. Which is where I came
> in....


My 2c (I've not been following)

did you try to recover the mentioned file again?

Did you try to all/part recover again? aka restore might not have worked
first time, or worst case; back up is corrupted, in which case it is an
install and selected data recover.

The only other thing I can ask is 'did you do a complete restore'?

Do you have another machine that you could compare against to see if
the error relates top one or a few messed files?
Sort of diff {find / machive1} vs find / machine2)
/ could be / /usr /lib, etcf.
>