| 1 |
Grant Edwards wrote: |
| 2 |
> On 2018-07-05, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 3 |
>> As of today, I seem to be unable to a an "emerge --sync". |
| 4 |
>> |
| 5 |
>> The process either hangs forever at the "Refreshing keys from keyserver step: |
| 6 |
> [...] |
| 7 |
> |
| 8 |
>> Or, it fails because there are no public key to verify a manfest: |
| 9 |
> For now, I've had to set add "sync-rsync-verify-metamanifest = no" to |
| 10 |
> my repo conf file so that I can actually do updates, but that seems |
| 11 |
> like a dangerous work-around. |
| 12 |
> |
| 13 |
> Is access to a keyserver via TCP port 11371 now a requirement for |
| 14 |
> using portage? |
| 15 |
> |
| 16 |
> Is there any other way to get keys updated that only requires the |
| 17 |
> normal https and rsync access? |
| 18 |
> |
| 19 |
|
| 20 |
|
| 21 |
For those having this problem, may I suggest this. Look at the USE |
| 22 |
flags here for portage. |
| 23 |
|
| 24 |
|
| 25 |
[ebuild R ] sys-apps/portage-2.3.40-r1::gentoo USE="(ipc) |
| 26 |
native-extensions rsync-verify xattr -build -doc -epydoc -gentoo-dev |
| 27 |
(-selinux)" PYTHON_TARGETS="python2_7 python3_5 (-pypy) -python3_4 |
| 28 |
-python3_6" |
| 29 |
|
| 30 |
|
| 31 |
It seems to me that one could emerge portage with rsync-verify USE flag |
| 32 |
disabled. After that, do one update, hopefully that will update the |
| 33 |
keys etc and then emerge portage again with the USE flag enabled. |
| 34 |
Hopefully after that one time workaround, the keys will be updated and |
| 35 |
things will work like they should. |
| 36 |
|
| 37 |
It seems to me that a perfect set of problems popped up at a rather bad |
| 38 |
time. It seems some keys expired AND the verify option which requires |
| 39 |
those keys was enabled. Now you have a catch 22 problem since you can't |
| 40 |
get the new keys and verify at the same time due to the expired/bad |
| 41 |
keys. Add in the recent git issue and it has folks a little touchy |
| 42 |
about working around this problem. |
| 43 |
|
| 44 |
I suspect one could use some variable on the command line or in |
| 45 |
make.conf as a one time workaround as well. |
| 46 |
|
| 47 |
Would this work for everyone, rsync, websync and git or am I missing |
| 48 |
something else? Could this at least lead to a fix that everyone should |
| 49 |
be able to use??? |
| 50 |
|
| 51 |
Dale |
| 52 |
|
| 53 |
:-) :-) |
Archives