1 |
On 2020-01-12 23:07, Neil Bothwick wrote: |
2 |
> On Sun, 12 Jan 2020 21:51:28 +0100, n952162 wrote: |
3 |
> |
4 |
>> While installing gentoo from scratch, after doing a "emerge --sync", the |
5 |
>> command: |
6 |
>> |
7 |
>> eselect profile list |
8 |
>> |
9 |
>> fails because it can't get any profiles, and I see that the 17.1 profile |
10 |
>> is in a .tmp-unverified-download-quarantine. |
11 |
>> |
12 |
>> 1. what do I have to do to get this going again? |
13 |
>> 2. how did I end up in this situation? Is this a known bug. I simply |
14 |
>> followed the handbook. |
15 |
> I had a similar issue with the .tmp-unverified-download-quarantine |
16 |
> continually appearing, deleting it made no difference. In the end I |
17 |
> deleted the whole portage tree and resynced, then the problem |
18 |
> disappeared. This may or may not have a bearing on your profile issue, |
19 |
> but it's worth fixing first. |
20 |
> |
21 |
> |
22 |
|
23 |
I just finished running "emerge --sync" again, based on something I saw |
24 |
on the internet - it did the whole thing again, takes about 2 hours. |
25 |
Same result. But I didn't delete "the whole portage tree". What does |
26 |
that mean? |
27 |
|
28 |
rm -rf /var/db/repos? |
29 |
|
30 |
or: |
31 |
|
32 |
rm -rf /var/db/pkg? |
33 |
|
34 |
And why should it work? Is it not rather something broken in the |
35 |
upstream repository? Or the 20200108 minimum cd image I'm using? It's |
36 |
otherwise a naked machine. |