be a symlink. What's the link pointing to?
> I'd be tempted to revert the unsymlink. Did you check the output of
> "unsymlink-lib --analyze" first?
After a pause for thought (quite a long one, with coffee), I went through the
process again and all has turned out just fine.
On 2019.06.19 14:10, Neil Bothwick wrote:
On Wed, 19 Jun 2019 20:45:03 +0800, Bill Kenworthy wrote:
> wifi ~ # unsymlink-lib --analyze
> /usr/lib needs to be a symlink to lib64!
> wifi ~ # ls -al /usr/lib
> lrwxrwxrwx 1 root root 10 Jan 4 13:37 /usr/lib -> /usr/lib64
> wifi ~
hrough the migration, step by step, but after step 7, "unsymlink-lib
--finish", I found 110 files still in /lib and /usr/lib (list attached), of
the >3000 before the migration attempt, and /usr/local/lib still a symlink.
This can't be right, can it?
It's perfectly OK for there to still be stuff
nt, such as config stuff and scripts. However, I'm pretty
> > sure none of them should still be a symlink. What's the link
> > pointing to? I'd be tempted to revert the unsymlink. Did you check
> > the output of "unsymlink-lib --analyze" first?
>
> After a pause for
On Wed, 19 Jun 2019 20:45:03 +0800, Bill Kenworthy wrote:
> wifi ~ # unsymlink-lib --analyze
> /usr/lib needs to be a symlink to lib64!
> wifi ~ # ls -al /usr/lib
> lrwxrwxrwx 1 root root 10 Jan 4 13:37 /usr/lib -> /usr/lib64
> wifi ~ #
>
> The symlink looks the sam
On Thursday, 20 June 2019 00:02:35 BST Bill Kenworthy wrote:
> On 20/6/19 2:26 am, Jack wrote:
> > Bill - you might try "rm /usr/lib" WITHOUT the trailing slash, to
> > remove the symlink. Then "ln -s lib64 /usr/lib" will recreate it in
> > the form un
/usr/lib" will recreate it in
>>> the form unsymlink-lib seems to require.
>> Thanks, nicely picked!
>>
>> Hair split and now all works as intended. Just found another system
>> with the same problem too.
> Why is it a problem? The instructions clearly state
On 20/6/19 2:26 am, Jack wrote:
> On 2019.06.19 14:10, Neil Bothwick wrote:
>> On Wed, 19 Jun 2019 20:45:03 +0800, Bill Kenworthy wrote:
>>
>> > wifi ~ # unsymlink-lib --analyze
>> > /usr/lib needs to be a symlink to lib64!
>> > wifi ~ # ls -al /usr/lib
&
On 2019.06.19 16:14, Neil Bothwick wrote:
On Wed, 19 Jun 2019 14:26:50 -0400, Jack wrote:
> On 2019.06.19 14:10, Neil Bothwick wrote:
> > On Wed, 19 Jun 2019 20:45:03 +0800, Bill Kenworthy wrote:
> >
> > > wifi ~ # unsymlink-lib --analyze
> > > /usr/l
er first as explained there.
The migration is performed using app-portage/unsymlink-lib tool.
The following steps can be used to upgrade your system:
1. Sync and upgrade your system to the newest package versions
to reduce the risk of issues.
2. Install the tool, e.g. via 'emerge -1v app-port
On 6/20/19 3:47 AM, Peter Humphrey wrote:
On Thursday, 20 June 2019 00:02:35 BST Bill Kenworthy wrote:
On 20/6/19 2:26 am, Jack wrote:
Bill - you might try "rm /usr/lib" WITHOUT the trailing slash, to
remove the symlink. Then "ln -s lib64 /usr/lib" will recreate it in
th
On Wed, 19 Jun 2019 14:26:50 -0400, Jack wrote:
> On 2019.06.19 14:10, Neil Bothwick wrote:
> > On Wed, 19 Jun 2019 20:45:03 +0800, Bill Kenworthy wrote:
> >
> > > wifi ~ # unsymlink-lib --analyze
> > > /usr/lib needs to be a symlink to lib64!
> > > w
be important. I noticed grub,
> nvidia, dracut and others that could cause issues if they failed. Is it
> really safe to just rm them or did I miss something? Do I need to do
> something else not mentioned in the news item for this?
Hmm ... having run 'unsymlink-lib --analyze/migrate/fin
/hardened (exp)
[32] olympus:default/linux/amd64/17.0/musl/hardened/selinux (exp)
[33] olympus:default/linux/amd64/17.0/uclibc (exp)
[34] olympus:default/linux/amd64/17.0/uclibc/hardened (exp)
wifi ~ # unsymlink-lib --analyze
/usr/lib needs to be a symlink to lib64!
wifi ~ # ls -al /usr/lib
> total 257136
> [snip ... x 257136 ]
>
>> As one can see, some of those could be important. I noticed grub,
>> nvidia, dracut and others that could cause issues if they failed. Is it
>> really safe to just rm them or did I miss something? Do I need to do
>> someth
ation, step by step, but after step 7, "unsymlink-lib
--finish", I found 110 files still in /lib and /usr/lib (list attached), of
the >3000 before the migration attempt, and /usr/local/lib still a symlink.
This can't be right, can it?
--
Regards,
Peter.
/lib:
total 3.7M
lrwxrwxrw
16 matches
Mail list logo
