<br></div><div dir="auto">Is there any way to find those better than brute force?</div><div dir="auto"><br></div><div dir="auto">By the way, I also have a copy of all binary packages (I always use the -b flag while emerging any package) in that seconddisk. But that didn't help so far, even trying to use the -K flag. I thought on un-tar'ing those binary packages by hand, but portage will be unaware of this, not knowing the packages are installed.</div><div dir="auto"><br></div><div dir="auto">
Hello
After a main HD failure, I'll have to reinstall Gentoo from almost zero - I have a full and recent copy of the /etc directory and the file /var/lib/portage/world in a secondary HD (along many personal backups).
Installation basics done, now it is time for an emerge world.
Although the emerge lists is as huge as expected, it doesn't even start, portage says there are cyclic USE flags that I should avoid at the first moment, but may restore afterwards.
But it doesn't say which are those USE flags that block each other.
Is there any way to find those better than brute force?
By the way, I also have a copy of all binary packages (I always use the -b flag while emerging any package) in that second disk. But that didn't help
so far, even trying to use the -K flag. I thought on un-tar'ing those
binary packages by hand, but portage will be unaware of this, not knowing
the packages are installed.
Any hint will be greatly appreciated!
Thanks
Francisco
Hello
After a main HD failure, I'll have to reinstall Gentoo from almost
zero - I have a full and recent copy of the /etc directory and the
file /var/lib/portage/world in a secondary HD (along many personal
backups).
Installation basics done, now it is time for an emerge world.
Although the emerge lists is as huge as expected, it doesn't even
start, portage says there are cyclic USE flags that I should avoid at
the first moment, but may restore afterwards.
But it doesn't say which are those USE flags that block each other.
Is there any way to find those better than brute force?
By the way, I also have a copy of all binary packages (I always use
the -b flag while emerging any package) in that second disk. But that
didn't help so far, even trying to use the -K flag. I thought on
un-tar'ing those binary packages by hand, but portage will be unaware
of this, not knowing the packages are installed.
Any hint will be greatly appreciated!
Thanks
Francisco
Although the emerge lists is as huge as expected, it doesn't even start, portage says there are cyclic USE flags that I should avoid at the first moment, but may restore afterwards.
But it doesn't say which are those USE flags that block each other.
Is there any way to find those better than brute force?
Alternatively, fully update the system before putting in your world
file, and then instead of copying in the world file all at once just
run a loop to emerge the lines in it one at a time.
On Wed, 11 May 2022 16:45:31 +0000, Laurence Perkins wrote:
Alternatively, fully update the system before putting in your world
file, and then instead of copying in the world file all at once just
run a loop to emerge the lines in it one at a time.
Now you mention it, that's what I did last time, although my loop emerge
ten lines at a time to cut down on the number of dependency
recalculations.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 302 |
Nodes: | 16 (0 / 16) |
Uptime: | 97:02:29 |
Calls: | 6,764 |
Calls today: | 2 |
Files: | 12,295 |
Messages: | 5,376,370 |
Posted today: | 1 |