Re: [gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
On Tuesday 24 October 2006 02:08, Brian Harring wrote: > freebsd stages being the usual example [1]. s/stages/source tarballs/ The stages are in another section of the mirror, the source tarballs were there when we were not in the main tree. Now the same tecnique is used by openbsd/netbsd. -- Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpN8yZ3Ga2Nl.pgp Description: PGP signature
[gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
Francesco Riosa schrieb: > Also I'm offering again, some space and bandwidth in germany Maybe we could also set up the box from bug #108379 (as mirror?) for patches. It has plenty of bandwith sitting around and not doing that much currently ;) Greetz Jokey -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
On Tue, Oct 24, 2006 at 12:51:59AM +0200, Stefan Schweizer wrote: > Alec Warner wrote: > >> Those get uploaded and look fine but after 6 months they are suddenly > >> being removed by the script. > >> > > > > There is a distfiles whitelist[1] for this exact purpose...isn't there? > > > > [1] > > http://www.gentoo.org/proj/en/infrastructure/mirrors/overview-distfile.xml > > Thanks for the heads up. I was not aware of this when I was looking for a > solution badly back then. Must be a rather recent development. Looks easy > and straightforward - even deleting is possible. Good job, guys :) I added whitelist over 18 months ago... not a new feature, although infra finally updated the documentation to finally be accurate :) And correcting vapier in this email, mirror-dist has been running the show since around 04/05 - 05/05; not june/july of this year... > Still the developer needs to know about it and think of it in the moment of > adding mirror restrictions to an ebuild with mirror://gentoo sources. A > risk that is not going to be taken in any of my ebuilds. Whitelist protects files that have a long term (> 2 weeks) refcount of 0; freebsd stages being the usual example [1]. mirror restricted ebuilds that have mirror://gentoo/ (and just mirror://gentoo/) have a refcount of 1, thus they do *not* need to be whitelisted. In general, ebuild maintainers have no valid reason to be screwing with whitelists unless they're doing stages, or (odd case) need to ensure a file is on mirrors for test purposes, mirrorselect in this case. Thats a polite way of saying the impolite "stick random crap in the whitelist, and I'll make a dev cut off your balls" :) Whitelist totally bypasses all measures to keep the mirror image at a sane size; it's intended strictly for material that is *not* ref'd by an ebuild, and has a *valid* reason to be in the mirror tier. Short version: if you're not a stage monkey, you shouldn't be touching whitelists. > I hope the people that prefer mirror://gentoo know about the issue and the > solution :) Think you need to lay out other reasons... thus far you seem to be forgetting about a change *you* forced through. ~harring [1] http://dev.gentoo.org/~zmedico/infra/distfiles/failure.xml#doc_chap6 pgpGJQMKZ7aZ1.pgp Description: PGP signature
Re: [gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
On Monday 23 October 2006 18:51, Stefan Schweizer wrote: > Thanks for the heads up. I was not aware of this when I was looking for a > solution badly back then. Must be a rather recent development. i guess that depends on your definition of "recent" ... it's been in place since June/July > Still the developer needs to know about it and think of it in the moment of > adding mirror restrictions to an ebuild with mirror://gentoo sources. *shrug* the document itself could be linked from the gentoo handbook, but it isnt like it's a secret ... it was announced/discussed on -core or -dev > A risk that is not going to be taken in any of my ebuilds. lame -mike pgpYcqPA1HIQj.pgp Description: PGP signature
Re: [gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
Stefan Schweizer wrote: Alec Warner wrote: Those get uploaded and look fine but after 6 months they are suddenly being removed by the script. There is a distfiles whitelist[1] for this exact purpose...isn't there? [1] http://www.gentoo.org/proj/en/infrastructure/mirrors/overview-distfile.xml Thanks for the heads up. I was not aware of this when I was looking for a solution badly back then. Must be a rather recent development. Looks easy and straightforward - even deleting is possible. Good job, guys :) Still the developer needs to know about it and think of it in the moment of adding mirror restrictions to an ebuild with mirror://gentoo sources. A risk that is not going to be taken in any of my ebuilds. I agree it could use a bit more...Preaching. I think the innards of really how our mirroring system works is lost on some people. They know the abstraction; "it's automated and does X,Y,Z" but they don't really know how it all works. -Alec Warner [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
Grant Goodyear wrote: > Truly, the sarcasm doesn't help. It takes a potentially reasonable > grievance and reduces it to just the author appearing to be a jerk. Sorry, I have no intention to cause any ill fate. Is meant explanatory. - Stefan -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: mirroring distfiles/patches on patches.gentoo.org
Alec Warner wrote: >> Those get uploaded and look fine but after 6 months they are suddenly >> being removed by the script. >> > > There is a distfiles whitelist[1] for this exact purpose...isn't there? > > [1] > http://www.gentoo.org/proj/en/infrastructure/mirrors/overview-distfile.xml Thanks for the heads up. I was not aware of this when I was looking for a solution badly back then. Must be a rather recent development. Looks easy and straightforward - even deleting is possible. Good job, guys :) Still the developer needs to know about it and think of it in the moment of adding mirror restrictions to an ebuild with mirror://gentoo sources. A risk that is not going to be taken in any of my ebuilds. I hope the people that prefer mirror://gentoo know about the issue and the solution :) Thanks, Stefan -- gentoo-dev@gentoo.org mailing list