On 5/31/19 9:13 AM, Peter Humphrey wrote:
On Thursday, 30 May 2019 16:32:01 BST »Q« wrote:
The 17.1 profiles are soon to be marked stable, so I went ahead and
migrated a little over a week ago, following the draft news item Michał
Górny recently posted to -dev. FWIW, the migration seemed to go
smoothly and I haven't noticed anything breaking except
app-office/kmymoney won't build, apparently because the ebuild expects
something to be in /lib which isn't there any more. But one dev said
it builds fine on his 17.1 test system, so I dunno. I filed a bug,
<https://bugs.gentoo.org/686750>.
Encouraged by this, I tried the migration this morning. I followed the enews
item that Mick quoted - I even printed it to keep myself straight.
Before the start:
$ eselect profile show
Current /etc/portage/make.profile symlink:
default/linux/amd64/17.0/desktop/plasma
I went through 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 under /lib /usr/lib
/usr/local/lib. These are supposed to be things which are arch
independent, 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?
