| 1 |
Hi, |
| 2 |
|
| 3 |
What I would suggest is to try yo emerge @world first with a reduced |
| 4 |
list of USE flags, maybe the default, and after success you could |
| 5 |
introduce back the wanted USE flags and emerge @world once more. |
| 6 |
|
| 7 |
It could be a bit too much compilation, but if you have already binary |
| 8 |
packages, it will not be so expensive the second round, IMHO. |
| 9 |
|
| 10 |
Best |
| 11 |
|
| 12 |
On 11/5/22 11:57, Francisco Ares wrote: |
| 13 |
> Hello |
| 14 |
> |
| 15 |
> After a main HD failure, I'll have to reinstall Gentoo from almost |
| 16 |
> zero - I have a full and recent copy of the /etc directory and the |
| 17 |
> file /var/lib/portage/world in a secondary HD (along many personal |
| 18 |
> backups). |
| 19 |
> |
| 20 |
> Installation basics done, now it is time for an emerge world. |
| 21 |
> |
| 22 |
> Although the emerge lists is as huge as expected, it doesn't even |
| 23 |
> start, portage says there are cyclic USE flags that I should avoid at |
| 24 |
> the first moment, but may restore afterwards. |
| 25 |
> |
| 26 |
> But it doesn't say which are those USE flags that block each other. |
| 27 |
> |
| 28 |
> Is there any way to find those better than brute force? |
| 29 |
> |
| 30 |
> By the way, I also have a copy of all binary packages (I always use |
| 31 |
> the -b flag while emerging any package) in that second disk. But that |
| 32 |
> didn't help so far, even trying to use the -K flag. I thought on |
| 33 |
> un-tar'ing those binary packages by hand, but portage will be unaware |
| 34 |
> of this, not knowing the packages are installed. |
| 35 |
> |
| 36 |
> Any hint will be greatly appreciated! |
| 37 |
> |
| 38 |
> Thanks |
| 39 |
> |
| 40 |
> Francisco |
Archives