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 11C76138334 for ; Tue, 29 Oct 2019 13:51:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BD437E08F6; Tue, 29 Oct 2019 13:51:10 +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 77626E08EC for ; Tue, 29 Oct 2019 13:51:10 +0000 (UTC) Received: from pomiot (c134-66.icpnet.pl [85.221.134.66]) (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 5659D34C326; Tue, 29 Oct 2019 13:51:08 +0000 (UTC) Message-ID: <61b08adc910a6a0de82286ffd4ee832bb4502aec.camel@gentoo.org> Subject: Re: [gentoo-dev] New distfile mirror layout From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Cc: Fabian Groffen Date: Tue, 29 Oct 2019 14:51:04 +0100 In-Reply-To: References: <4c7465824f1fb69924c826f6bbe3ee73afa08ec8.camel@gentoo.org> <2d15507e-98ad-9466-75b7-7e8268ef2eb9@gentoo.org> <752be6c75f337df8ee8124a804247d2fb27e73b4.camel@gentoo.org> <20191029093401.GB22441@gentoo.org> <839D1F8E-35EE-43C9-B513-9895F087D77A@gentoo.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-GnRjYNyAbnUJMIZGrgvq" User-Agent: Evolution 3.32.4 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: ef0ee2e9-e5b7-4abc-a23c-70e12034bcd6 X-Archives-Hash: 5f98bf0f35f9c0c3046e311f99588d57 --=-GnRjYNyAbnUJMIZGrgvq Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2019-10-29 at 14:03 +0100, Ulrich Mueller wrote: > > > > > > On Tue, 29 Oct 2019, Micha=C5=82 G=C3=B3rny wrote: > > On Tue, 2019-10-29 at 13:23 +0100, Ulrich Mueller wrote: > > > So, what has to be be done to have it appear in the proper place? > > > Should the file be placed in a subdir of /space/distfiles-local/? > > > That seems to be error prone, and certainly could be automated? > > The file should be placed in SRC_URI, and emirrordist will take care > > of fetching it. >=20 > What if the file is hosted at a non-standard tcp port upstream (like > http://example.org:8080/)? The devmanual says that it _must_ be manually > uploaded to /space/distfiles-local/ in such cases. >=20 I can't really see why this wouldn't work. I've just did an experiment using app-benchmarks/forkbomb, and emirrordist fetched it just fine. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-GnRjYNyAbnUJMIZGrgvq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAl24Q8hfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM3 NkE4NDUwOTQwOThEMjhDQzhCMjZDNTYzOUFEQUUyMzI5RTI0MEUACgkQY5ra4jKe JA6vRwf9G5LAdbcz4gOJ5SuKV1VETLQoAjaO3J8aD7N66xaFFWrz7qb6ajyAuvD/ YWD+Ou0fy4qEdLq/Q/5W7wzYwiCgASeCmMKHklw7n8w6r7jKps2dK4EWJxAt6owh BYVH1ZcMaM/nBpLHoElByzDMopEqlT3d7GJj0jOeENJZLLs5e01AAS52emhjxA6U fyZtUVwegCr+RNOml7nsdZ0aQdMzWj0jaXiw/02zHo/0Hq9iLrhUDOgoxSuREhUM VKtcDh7xvWw2Cy5kWc0d19eW9ucLt+TvQs+PNWRJ2qzQn7UXYT0/U8XUZh29FhNO huT1jXMGwJBclfHZi8TCkH2rpRQ0sw== =Us0M -----END PGP SIGNATURE----- --=-GnRjYNyAbnUJMIZGrgvq--