W dniu pią, 15.12.2017 o godzinie 22∶24 +1300, użytkownik Kent Fredric
napisał:
> On Sat, 09 Dec 2017 11:26:36 +0100
> Michał Górny <mgo...@gentoo.org> wrote:
> 
> I ran this on a chroot.
> 
> > 5. Run 'unsymlink-lib --migrate'.
> > 
> > 6. Reboot your system and see if it still boots, possibly test if
> > important programs work. Also check if emerge starts but don't install
> > anything. If your system is now broken, you can do
> > 'unsymlink-lib --rollback' to return to step 3.
> 
> I started a new chroot because there's no "boot" and it seemed to work fine.
> 
> > 
> > 7. Run 'unsymlink-lib --finish'.
> 
> I ran this, and it broke the chroot :/
> 
> Weird problems like: 
> 
> Removing /usr/lib64/lib64/sys/block/ram0 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/ram0'

Sounds like you've put some awful self-symlink into this directory.
The script incorrectly follows top-level symlinks when removing, I'll
fix that.

> Removing /usr/lib64/lib64/sys/block/sdb failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/sdb'
> Removing /usr/lib64/lib64/sys/block/ram9 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/ram9'
> Removing /usr/lib64/lib64/sys/block/ram7 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/ram7'
> Removing /usr/lib64/lib64/sys/block/loop6 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/loop6'
> Removing /usr/lib64/lib64/sys/block/ram14 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/ram14'
> Removing /usr/lib64/lib64/sys/block/ram5 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/ram5'
> Removing /usr/lib64/lib64/sys/block/loop4 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/loop4'
> Removing /usr/lib64/lib64/sys/block/ram12 failed: [Errno 20] Not a directory: 
> '/usr/lib64/lib64/sys/block/ram12'
> 
> and 
> 
> Removing /usr/lib64/lib64/usr/lib64/libpkgconf.a failed: [Errno 2] No such 
> file or directory: '/usr/lib64/lib64/usr/lib64/libpkgconf.a'
> Removing /usr/lib64/lib64/usr/lib64/libpkgconf.so failed: [Errno 2] No such 
> file or directory: '/usr/lib64/lib64/usr/lib64/libpkgconf.so'
> Removing /usr/lib64/lib64/usr/lib64/libpkgconf.so.2 failed: [Errno 2] No such 
> file or directory: '/usr/lib64/lib64/usr/lib64/libpkgconf.so.2'
> 
> Now in my chroot:
> 
>  # ls /lib/
> bash: ls: command not found
> 
> RIP.
> 

-- 
Best regards,
Michał Górny


Reply via email to