[gentoo-user] How to emergency manual install of libffi-compat.
Alan Grimes
SOFTWARE that needs FFI thru python is broken, especially all portage
tooling...
Is there a repository and walkthru for installing this?
Am I really the world's unluckiest gentoo user or was the pooch really
screwed on this issue?
https://packages.gentoo.org/packages/dev-libs/libffi-compat
--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
Michael
> Apparently installing libffi-compat will un-hose my system where ALL
> SOFTWARE that needs FFI thru python is broken, especially all portage
> tooling...
>
> Is there a repository and walkthru for installing this?
https://wiki.gentoo.org/wiki/Project:Portage/Fixing_broken_portage
If that won't work for whatever reason, chroot into your system after you boot
with the latest Live-USB and try to update @system. Alternatively, reinstall.
Neil Bothwick
quickpkg it. Then you can untar the package into / before emerging it
properly.
In future, you should add buildpkg to FEATURES so that you always have
binary packages of software so you can roll back with tar in an emergency.
--
Neil Bothwick
We've all heard that a million monkeys banging on a million
typewriters will eventually reproduce the works of Shakespeare.
Now, thanks to the Internet, we know this is not true.
Andrea Conti
To recover, I followed these steps:
1. temporarily bring back /usr/lib/libffi.so.7
(/usr/lib64/libffi.so.7 if you're on amd64) from whatever source
you can find (backup, saved binpkg, livecd/usb). You will need to
copy both the actual library (libffi.so.7.x.y) and the versioned
symlink (libffi.so.7 -> libffi.so.7.x.y); make sure you do not
touch the existing libffi.so -> libffi.so.8.z.w symlink
2. re-emerge your main python version (the one you use to run
portage, see emerge --info)
3. finish your upgrade
4. remove the files you copied in 1
5. do a revdep-rebuild pass, just in case
I would not call installing dev-libs/libffi-compat a solution --
you still need a working python to do that, and it won't protect
you from future breakage like this.
It will not help in this case, since what's broken is python and not portage.
If that won't work for whatever reason, chroot into your system after you boot with the latest Live-USB and try to update @system. Alternatively, reinstall.
Neither will this, as you won't be able to execute python (i.e. run portage) inside the chroot.
HTH
andrea
Michael
> >> This may help:
> >>
> >> https://wiki.gentoo.org/wiki/Project:Portage/Fixing_broken_portage
>
> It will not help in this case, since what's broken is python and not
> portage.
> > If that won't work for whatever reason, chroot into your system after you
> > boot with the latest Live-USB and try to update @system. Alternatively,
> > reinstall.
> Neither will this, as you won't be able to execute python (i.e. run portage)
> inside the chroot.
get whatever parts of your toolchain are broken working again - but didn't
obviously didn't write so. :-)
I can't recall coming come across this problem myself, probably because I tend
to leave emerge updates to finish, or resume from where I had stopped an
update. Is this a an error portage should be able to deal with itself when an
update is interrupted, then restarted?
Mart Raudsepp
> I can't recall coming come across this problem myself, probably
> because I tend to leave emerge updates to finish, or resume from
> where I had stopped an update. Is this a an error portage should be
> able to deal with itself when an update is interrupted, then
> restarted?
/usr/lib/libffi.so.7 and it should have been fine enough. Not sure what
happened for him, maybe it has been disabled?
Mart