On Sat, Jul 09, 2011 at 09:49:08PM +0200, Ljubomir Ljubojevic wrote:
And if all mirrors were set properly this discussion would never happen.
And that's the whole point of all of this. Content is seeded in such a way that it is restricted from the public until the time that the read bit is enabled when the actual release announcement is made. Some mirrors, either willfully and knowingly, or perhaps by some automated means such as a script, have opened the directories up. So yes, this content is leaked. And it has been strongly cautioned on IRC and elsewhere that using this leaked content before official release was asking for trouble in the event that a reissue of components was made. And sure enough, such a reissue proved necessary in the case of the CentOS-6 release.
Leaks happen every single release. And at least one of the currently leaking mirrors has done this in the past so it's not a new story even for them. Running a mirror really isn't that difficult; generally, barring normal administration tasks of course, it's fire and forget.
But until the project does something to either slap the wrists of mirror operators that leak content in some manner, or just remove their mirror status perhaps for the case of repeat offenders, it's going to continue to occur.
As far as those _using_ the content? They should know better. There has been no official announcement of general CentOS-6 availability; they should know not to use that which is leaking out - especially if they had to actively search out such content.
This is an enterprise level distribution, some thought really is required.
John -- <DiscordianUK> deselect was written by someone who OD'ed on vi