| 1 |
On 6/20/19 3:47 AM, Peter Humphrey wrote: |
| 2 |
> On Thursday, 20 June 2019 00:02:35 BST Bill Kenworthy wrote: |
| 3 |
>> On 20/6/19 2:26 am, Jack wrote: |
| 4 |
>> |
| 5 |
>>> Bill - you might try "rm /usr/lib" WITHOUT the trailing slash, to |
| 6 |
>>> remove the symlink. Then "ln -s lib64 /usr/lib" will recreate it in |
| 7 |
>>> the form unsymlink-lib seems to require. |
| 8 |
>> Thanks, nicely picked! |
| 9 |
>> |
| 10 |
>> Hair split and now all works as intended. Just found another system |
| 11 |
>> with the same problem too. |
| 12 |
> Why is it a problem? The instructions clearly stated that the symlink might |
| 13 |
> not be revmoved, and that you should remove it yourself in that case. |
| 14 |
The --analyze phase bailed out before even starting. I filed an issue |
| 15 |
upstream (mgorny's github repository) and he made a change (I didn't |
| 16 |
look at the actual commit) so this situation should now be handled |
| 17 |
correctly. I think he did want to accept anything that ended up |
| 18 |
pointing to the right place, but was afraid of ending up with an |
| 19 |
unpredictable result, so now it will accept either the relative or |
| 20 |
absolute form. I don't know when he will release a new version. |
Archives