From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] .tmp-unverified-download-quarantine
Date: Mon, 13 Jan 2020 11:15:31 +0000 [thread overview]
Message-ID: <5873652.HNIFBk282c@localhost> (raw)
In-Reply-To: <20200113104257.0ba49a3a@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
On Monday, 13 January 2020 10:42:57 GMT Neil Bothwick wrote:
> On Mon, 13 Jan 2020 10:17:06 +0000, Mick wrote:
> > Right, I haven't changed them on this installation either and emerge
> > FEATURES include
> >
> > '... userfetch userpriv usersandbox usersync'.
> >
> > With 'userpriv' portage is meant to drop privileges to the owner of the
> > gentoo repo directory, but if the directory is owned by root to start
> > with I am not clear how userpriv is meant to work.
>
> According to the make.conf man page, userpriv will
>
> "Allow portage to drop root privileges and compile packages as
> portage:portage without a sandbox"
According to my emerge --info output I have sandbox, usersandbox and userpriv,
all set. The owner of my portage directory and all files therein is
root:root. Should the ownership be portage:portage? What is the default?
I haven't performed a full portage sync for a while now to confirm how long it
takes here, but a re-sync over a slow ADSL takes ~20 minutes on a dual core
ancient Intel, much less on my more modern PCs. More than 80% of this time is
spent on verifying the signatures of the downloaded tmp sync file. I would
think on a modern AMD Ryzen PC like the OP's it should take a fraction of the
time.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-13 11:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 20:51 [gentoo-user] .tmp-unverified-download-quarantine n952162
2020-01-12 15:48 ` james
2020-01-13 8:24 ` n952162
2020-01-16 21:01 ` james
2020-01-18 13:50 ` Wols Lists
2020-01-18 17:45 ` n952162
2020-01-18 17:58 ` Wols Lists
2020-01-16 21:03 ` james
2020-01-12 22:07 ` Neil Bothwick
2020-01-12 22:41 ` n952162
2020-01-12 23:32 ` Neil Bothwick
2020-01-13 8:22 ` Mick
2020-01-13 8:34 ` n952162
2020-01-13 8:41 ` Neil Bothwick
2020-01-13 10:17 ` Mick
2020-01-13 10:42 ` n952162
2020-01-13 10:48 ` Neil Bothwick
2020-01-13 11:37 ` n952162
2020-01-13 22:42 ` Neil Bothwick
2020-01-14 7:57 ` n952162
2020-01-13 10:42 ` Neil Bothwick
2020-01-13 11:15 ` Mick [this message]
2020-01-13 22:40 ` Neil Bothwick
2020-01-13 23:16 ` Mick
2020-01-14 8:04 ` n952162
2020-01-14 8:44 ` Neil Bothwick
2020-01-14 9:37 ` n952162
2020-01-14 9:47 ` Neil Bothwick
2020-01-14 10:10 ` Peter Humphrey
2020-01-14 11:07 ` n952162
2020-01-14 12:17 ` Dale
2020-01-14 15:47 ` Peter Humphrey
2020-01-14 18:36 ` Fw: " n952162
2020-01-15 9:17 ` Peter Humphrey
[not found] ` <48033839-c410-6e84-79ba-d5e061f4883a@web.de>
[not found] ` <3856247.qGUnUsoafO@peak>
2020-01-16 20:47 ` Fw: " n952162
2020-01-14 19:16 ` Neil Bothwick
2020-01-13 8:45 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5873652.HNIFBk282c@localhost \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox