From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] .tmp-unverified-download-quarantine
Date: Mon, 13 Jan 2020 22:42:20 +0000 [thread overview]
Message-ID: <20200113224220.2d4daee4@digimed.co.uk> (raw)
In-Reply-To: <cb209855-fb18-f2da-14c0-0e1cbe184086@web.de>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
On Mon, 13 Jan 2020 12:37:11 +0100, n952162 wrote:
> >>> The portage tree is sync'ed to the portage tree mirrors. A newer fs
> >>> snapshot won't include the tree itself, but it will include the new
> >>> default fs locations for the portage directory.
> >>
> >> Not sure what you mean ... you mean that the portage tree only comes
> >> in with the emerge --sync?
> >>
> >> A preliminary copy isn't in the stage3 tarball?
> > That's correct.
> >
> >
> is this happening because I'm not using (the "optional") webrsync?
It happens because the stage 3 doesn't contain a tree. The handbook tells
you to run a sync after unpacking the stage 3 for that reason. webrsync
is just another way of syncing, one that is more efficient than rsync
when starting with an empty tree.
--
Neil Bothwick
An expert is nothing more than an ordinary person away from home.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-13 22:42 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 [this message]
2020-01-14 7:57 ` n952162
2020-01-13 10:42 ` Neil Bothwick
2020-01-13 11:15 ` Mick
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=20200113224220.2d4daee4@digimed.co.uk \
--to=neil@digimed.co.uk \
--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