From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6A1FD138334 for ; Sun, 8 Jul 2018 06:54:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 53DA5E08D1; Sun, 8 Jul 2018 06:54:07 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D6404E07D3 for ; Sun, 8 Jul 2018 06:54:06 +0000 (UTC) Received: from [10.109.152.208] (public-gprs393068.centertel.pl [37.47.166.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 2114B335C7F; Sun, 8 Jul 2018 06:54:02 +0000 (UTC) Date: Sun, 08 Jul 2018 08:53:51 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [gentoo-dev] News Item: Portage rsync hardlink support To: gentoo-dev@lists.gentoo.org,Zac Medico ,gentoo development From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= Message-ID: <7594901D-54AF-4100-A1B8-7CEA2D1CC82D@gentoo.org> X-Archives-Salt: 8736b33e-575f-4bb2-ae10-a2650bd9572f X-Archives-Hash: 2609b3a6be2bb2fe07a8398474ce65ba Dnia 8 lipca 2018 08:08:31 CEST, Zac Medico napisa= =C5=82(a): >Please review=2E > >Title: Portage rsync hardlink support >Author: Zac Medico >Posted: 2018-07-11 >Revision: 1 >News-Item-Format: 2=2E0 >Display-If-Installed: sys-apps/portage > >For users of the rsync tree, beginning with sys-apps/portage-2=2E3=2E42, >the default behavior for sync operations will use hardlinks in order >to ensure that a repository remains in a valid state if something >goes wrong [1]=2E For example, if signature verification fails during a >sync operation, the new hardlink behavior will preserve the previous >state of the repository=2E > >The new behavior may conflict with configurations that restrict the >use of hardlinks, such as overlay filesystems=2E Therefore, users will >have to set "sync-allow-hardlinks =3D no" in repos=2Econf if they have >a configuration that restricts the use of hardlinks, but this should >not be very common: > >[DEFAULT] >sync-allow-hardlinks =3D no > >[1] https://bugs=2Egentoo=2Eorg/660410 sys-apps/portage: use rsync > --link-dest to implement atomic repository updates (and abort if > signature verification fails) Is safe git syncing implemented already? If not, maybe finish it first and= cover both with a single news item=2E Git is going to be more efficient he= re, so people may want to learn they have an alternative=2E --=20 Best regards, Micha=C5=82 G=C3=B3rny (by phone)