Re: [gentoo-user] .tmp-unverified-download-quarantine

[Dale <rdalek1967@gmail.com>]

Mick wrote:
> On Sunday, 12 January 2020 23:32:16 GMT Neil Bothwick wrote:
>> On Sun, 12 Jan 2020 23:41:43 +0100, n952162 wrote:
>>>> I had a similar issue with the .tmp-unverified-download-quarantine
>>>> continually appearing, deleting it made no difference. In the end I
>>>> deleted the whole portage tree and resynced, then the problem
>>>> disappeared. This may or may not have a bearing on your profile issue,
>>>> but it's worth fixing first.
>>> I just finished running "emerge --sync" again, based on something I saw
>>> on the internet - it did the whole thing again, takes about 2 hours. 
>> Two hours? How slow is your connection?
> Assuming this is not the time it takes to run rsync (even on a dial-up 
> analogue modem connection?) I would guess the delay is caused by the post-sync 
> tree verification.  The .tmp-unverified-download-quarantine file is where the 
> sync is stored until the signature verification is performed.  Even on a 
> really old dual-core laptop with low RAM the sync and verification only takes 
> around 20 minutes.
>
>

I'm on DSL, fairly slow DSL but DSL is what they call it, and had a long
re-sync time until a month or so ago.  It started around the time the
verification part started so I assumed it was that.  Then it kept
getting slower and slower.  After a while, I decided to try something
else.  I found a different server to sync too.  The first one was a
little better but still slow.  I tried another one and hit the jackpot. 
It was several times faster than the original one. 

This may not be your problem but it may be worth looking into.  You can
use mirrorselect to help you find a good server.  Try a few and see what
changes.  For me at least, it pretty much maxes out my DSL.  Obviously
there is some things that take a while that is done on my end but if the
download is slow due to a slow server, maybe you can find a faster one.

I might add, I've always tried to get servers that are physically close
by because they *should* be faster.  I've found that not to be true in
every case. 

As I said, this may not be your problem but it may be worth looking into
at least.  Just in case.

Dale

:-)  :-)