From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New distfile mirror layout
Date: Tue, 29 Oct 2019 10:34:01 +0100 [thread overview]
Message-ID: <20191029093401.GB22441@gentoo.org> (raw)
In-Reply-To: <e57dee8d0a624eabb24661f943362179d5061b2e.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On 29-10-2019 05:27:37 +0100, Michał Górny wrote:
> On Tue, 2019-10-29 at 00:24 +0100, Chí-Thanh Christopher Nguyễn wrote:
> > Hi!
> >
> > > Today you get chastised for using /space/distfiles-local and not
> > > following policy changes. The devmanual states that it's deprecated
> > > since at least 2011, and talks of using d.g.o [1].
> > > [1]
> > https://devmanual.gentoo.org/general-concepts/mirrors/index.html#suitable-download-hosts
> >
> > Sorry I'm late to the party, but I would like to enquire about what happens
> > if a file with existing filename but different b2sum gets uploaded to
> > /space/distfiles-local now?
>
> The same as before. It gets put in top-level disfiles directory.
> Hashes are calculated from filenames, so this wouldn't affect it. That
> is, if it put those files in subdirectories in the first place because
> it doesn't.
/space/distfiles-local is no longer copied to the mirrors? or just not
copied in the subdir-hierarchy?
> > Doing so and updating the Manifest used to be another (not necessarily
> > preferred) method to address upstream remaking release packages.
> >
>
> It's no longer valid.
Just wondering. Do you mean it isn't valid that some upstreams do this
(yes horror)? We surely need a way to work around that ...
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-29 9:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 13:41 [gentoo-dev] New distfile mirror layout Michał Górny
2019-10-18 19:53 ` Richard Yao
2019-10-18 20:49 ` Michał Górny
2019-10-19 1:09 ` Richard Yao
2019-10-19 6:17 ` Michał Górny
2019-10-19 8:20 ` Richard Yao
2019-10-19 19:26 ` Richard Yao
2019-10-19 20:02 ` Michał Górny
2019-10-19 22:48 ` Richard Yao
2019-10-22 0:46 ` James Cloos
2019-10-19 13:31 ` Fabian Groffen
2019-10-19 13:53 ` Michał Górny
2019-10-19 23:24 ` Joshua Kinard
2019-10-19 23:57 ` Alec Warner
2019-10-20 0:14 ` Joshua Kinard
2019-10-20 6:51 ` Michał Górny
2019-10-20 8:25 ` Joshua Kinard
2019-10-20 8:32 ` Michał Górny
2019-10-20 9:21 ` Joshua Kinard
2019-10-20 9:44 ` Michał Górny
2019-10-20 20:57 ` Joshua Kinard
2019-10-21 0:05 ` Joshua Kinard
2019-10-21 5:51 ` Ulrich Mueller
2019-10-21 10:17 ` Kent Fredric
2019-10-21 21:34 ` Mikle Kolyada
2019-10-21 10:13 ` Kent Fredric
2019-10-23 5:16 ` Joshua Kinard
2019-10-29 16:35 ` Kent Fredric
2019-10-20 17:09 ` Matt Turner
2019-10-21 16:42 ` Richard Yao
2019-10-21 23:36 ` Matt Turner
2019-10-23 5:18 ` Joshua Kinard
2019-10-23 17:06 ` William Hubbs
2019-10-23 18:38 ` William Hubbs
2019-10-23 22:04 ` William Hubbs
2019-10-24 4:30 ` Michał Górny
2019-10-22 6:51 ` Jaco Kroon
2019-10-22 8:43 ` Ulrich Mueller
2019-10-22 8:46 ` Jaco Kroon
2019-10-23 23:47 ` ext4 readdir performance - was " Richard Yao
2019-10-24 0:01 ` Richard Yao
2019-10-23 1:21 ` Rich Freeman
2019-10-28 23:24 ` Chí-Thanh Christopher Nguyễn
2019-10-29 4:27 ` Michał Górny
2019-10-29 9:34 ` Fabian Groffen [this message]
2019-10-29 11:11 ` Michał Górny
2019-10-29 12:23 ` Ulrich Mueller
2019-10-29 12:43 ` Michał Górny
2019-10-29 13:03 ` Ulrich Mueller
2019-10-29 13:09 ` Ulrich Mueller
2019-10-29 13:52 ` Michał Górny
2019-10-29 14:17 ` Ulrich Mueller
2019-10-29 14:33 ` Fabian Groffen
2019-10-29 14:45 ` Michał Górny
2019-10-29 14:56 ` Fabian Groffen
2019-10-29 13:51 ` Michał Górny
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=20191029093401.GB22441@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-dev@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