From: whiteman808 <whiteman808@paraboletancza.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Shared distfiles directory between different virtual machines
Date: Wed, 6 Nov 2024 18:39:28 +0100 [thread overview]
Message-ID: <3b23ce99-ad20-4131-be2a-47df87708e2c@paraboletancza.org> (raw)
In-Reply-To: <bab1daaa-3bae-e500-5521-9a2d52993f6a@applied-asynchrony.com>
What in case when two lock files are being created at the same time? How
can I prevent in this case emerge fail?
On 11/6/24 18:24, Holger Hoffstätte wrote:
> On 2024-11-06 18:16, whiteman808 wrote:
>> How can I prevent portage from overwriting the same source files in
>> the distfiles directory and possible checksum mismatches caused by
>> that behavior if I tell emerge to update @world simultaneously on
>> these different binary package servers?
>
> portage uses a lockfile for every download, so the problem does not exist.
>
> -h
>
next prev parent reply other threads:[~2024-11-06 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 17:16 [gentoo-user] Shared distfiles directory between different virtual machines whiteman808
2024-11-06 17:24 ` [gentoo-user] " Holger Hoffstätte
2024-11-06 17:39 ` whiteman808 [this message]
2024-11-06 17:53 ` Filip Kobierski
2024-11-07 0:34 ` Grant Taylor
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=3b23ce99-ad20-4131-be2a-47df87708e2c@paraboletancza.org \
--to=whiteman808@paraboletancza.org \
--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