public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree
Date: Wed, 13 Jun 2007 07:58:04 -0700	[thread overview]
Message-ID: <20070613145804.GK5778@seldon> (raw)
In-Reply-To: <26924B32-9D3E-4B0D-B527-C90E5DBC8B82@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]

On Wed, Jun 13, 2007 at 04:35:31PM +0200, Robert Buchholz wrote:
> The problem is rather that the patches are gone from the distfiles
> mirror after two weeks. The sources often stay upstream, but could
> also be gone.
> 
> Is there an archive for these files I missed?

That archive ('purgatory' being the name used for it) isn't publically 
accessible; had suggested it in the past, but infra folks didn't 
think it would be needed.

Few issues if it were opened up;

1) it's not a true vcs, just a directory.  Meaning 

1.a) it's collapsing down the trees history of distfile names; if 
ebuild x refs 'patch', gets removed, 'patch' goes into purgatory.  If 
ebuild y refs 'patch', which is a different file, then gets removed, 
ebuild ys' version of 'patch' is whats is now in purgatory (last used 
basically).

1.b) skimped a bit in the description above; 'patch' gets removed from 
purgatory when ebuild 'y' is added to the tree- the chksums will 
differ, thus it throws out the copy that no longer is relevant to it's 
job (maintaining the mirror image).


2) if implemented, likely to be a single box- meaning stuff shouldn't 
rely on it as an upstream URI, they should mirror it themselves.

3) mirror maintenance, if an ebuild is added to the tree that uses 
that specific distfile name, as hinted at in 1.b, the file is removed 
from purgatory- this *includes* if the chksums match.  Basically, if 
the file is needed on the mirror image, it copies it over and wipes 
the purgatory copy of it (intention is to keep space usage down).
This obviously would break any ebuilds daftly ignoring #2, and using 
the purgatory host as an upstream URI.


Personally, I think at least for devs, having access to purgatory 
would be a good thing.  Folks seem to have learned over the last few 
years, but dealt with a lot of requests where a dev screwed up and 
needed to pull a file out of purgatory.  Perhaps they've gotten wiser 
since, dunno.  Either way, if trying to pull a file out of 
purgatory, bug your friendly infra monkey, or zmedico if you need a 
specific file out- they ought to have access.

For effectively random anonymous, http/ftp, not sure about 
that.  Think some form of access is needed, don't think it should 
really be usable as an upstream host.

~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-13 15:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  9:40 [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree cilly
2007-06-12  9:49 ` [gentoo-dev] " Christian Faulhammer
2007-06-12  9:53   ` cilly
2007-06-12  9:59 ` [gentoo-dev] " Luca Barbato
2007-06-12 10:04   ` Fernando J. Pereda
2007-06-12 10:01 ` Fernando J. Pereda
2007-06-12 10:14   ` cilly
2007-06-12 10:21     ` Fernando J. Pereda
2007-06-12 10:30       ` cilly
2007-06-12 10:40         ` Marijn Schouten (hkBst)
2007-06-12 10:48           ` cilly
2007-06-12 11:09             ` Marijn Schouten (hkBst)
2007-06-12 10:36   ` Richard Freeman
2007-06-12 10:46     ` Fernando J. Pereda
2007-06-12 10:53       ` cilly
2007-06-12 10:59         ` cilly
2007-06-12 11:27           ` Luca Barbato
2007-06-12 11:37             ` cilly
2007-06-12 11:29           ` Christoph Mende
2007-06-12 11:38             ` cilly
2007-06-13 14:35             ` Robert Buchholz
2007-06-13 14:58               ` Brian Harring [this message]
2007-06-12 16:55           ` [gentoo-dev] " Duncan
2007-06-13 14:44             ` banym tuxaner
2007-06-12 11:03         ` [gentoo-dev] " Fernando J. Pereda
2007-06-12 11:08           ` cilly
2007-06-12 16:05         ` Luis Francisco Araujo
2007-06-12 10:48     ` Luca Barbato
2007-06-12 10:50       ` cilly
2007-06-12 11:21         ` Petteri Räty
2007-06-12 11:50           ` cilly
2007-06-12 11:00     ` Marijn Schouten (hkBst)
2007-06-12 11:25     ` [gentoo-dev] " Christian Faulhammer
2007-06-12 11:52       ` cilly
2007-06-12 12:55 ` [gentoo-dev] " Marius Mauch
2007-06-12 12:59   ` cilly

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=20070613145804.GK5778@seldon \
    --to=ferringb@gmail.com \
    --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