On 6/18/19 9:43 AM, John Covici wrote:
It would seem impossible for me to switch to profile 17.1.
"Impossible" seems a bit extreme to me. Maybe really difficult / annoying.
I say this because I can never run emerge --depclean . I have a
few packages which will not compile and one not in the tree anymore.
What compilation errors do you get?
I've got a couple packages that I keep the the ebuild around for. I
have always been able to copy things back into portage such that they
survive a --depclean. xfce4-mixer being one example.
I don't know how proper or safe this is. But it works for me!™ ;-)
the packages which will not compile are mono-4.4.1.0 and totem-3.30 --
I have filed bugs against both of them.
I'd have to see the bugs to have a snowball's chance in <REDACTED> of
having any clue.
Inn no longer configures and I have discussed this in another thread.
I thought that INN had been removed from the portage tree. (I've
lamented this elsewhere.)
I did run into a problem with a version not configuring because a
comparison was expecting a number and someone appended something to it
turning it into a string. I was able to remove what was appended and
get INN to configure and compile. Perhaps something like that is what
you're experiencing.
So, where can I go with this? I hate to just go forward, although these
packages look they don't have any lib32 dependencies. Wat do you thihnk
about this?
I've not tackled the 17.0 to 17.1 migration yet. I've been addressing
my own issues within 17.0 and recently gotten them to (what I think is)
a stable point. I'm letting backups run and stress testing things for a
few days. (Really until I find more time to do the 17.0 to 17.1
migration on a test system.)
Thanks in advance for any suggestions.
Good luck.
--
Grant. . . .
unix || die
