[arch-dev-public] Killing [unstable] for good
Any qualms about killing [unstable] from our FTP completely? We still have the directories and the "empty" databases sitting around. I think we've given plenty of warning to people that unstable no longer exists. At the very least, I'd rather have empty directories than the leftover databases we have there now that are sometimes breaking pacman because of the lone ./ entry inside of them. -Dan
Am Samstag 17 Januar 2009 19:13:16 schrieb Dan McGee:
Any qualms about killing [unstable] from our FTP completely? We still have the directories and the "empty" databases sitting around. I think we've given plenty of warning to people that unstable no longer exists.
Yes, just remove it. And please do the same for kde-unstable. I cannot remove that dir by myself. I think I am not in the ftp group. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
On Sat, Jan 17, 2009 at 7:13 PM, Dan McGee <dpmcgee@gmail.com> wrote:
Any qualms about killing [unstable] from our FTP completely? We still have the directories and the "empty" databases sitting around. I think we've given plenty of warning to people that unstable no longer exists.
At the very least, I'd rather have empty directories than the leftover databases we have there now that are sometimes breaking pacman because of the lone ./ entry inside of them.
Btw, does anyone have any idea how this archive was created? I am attaching it since it will be deleted soon :)
tar tvf unstable.db.tar.gz drwxr-xr-x thomas/users 0 2008-07-24 00:20 ./
On Sat, 2009-01-17 at 12:13 -0600, Dan McGee wrote:
Any qualms about killing [unstable] from our FTP completely? We still have the directories and the "empty" databases sitting around. I think we've given plenty of warning to people that unstable no longer exists.
It's only been missing from the mirror script for about a month now... http://wiki.archlinux.org/index.php/Local_Mirror Any mirror setup before then with this script will be throwing errors like mine is... Not a huge issue, it gives a detailed enough message to know that unstable doesn't exist anymore and the rest of the repos continue to sync... Dale
On Sat, Jan 17, 2009 at 4:57 PM, Dale Blount <dale@archlinux.org> wrote:
On Sat, 2009-01-17 at 12:13 -0600, Dan McGee wrote:
Any qualms about killing [unstable] from our FTP completely? We still have the directories and the "empty" databases sitting around. I think we've given plenty of warning to people that unstable no longer exists.
It's only been missing from the mirror script for about a month now... http://wiki.archlinux.org/index.php/Local_Mirror Any mirror setup before then with this script will be throwing errors like mine is...
Not a huge issue, it gives a detailed enough message to know that unstable doesn't exist anymore and the rest of the repos continue to sync...
The rsync stanza on gerolde has definitely been gone for a while, so removing the directories themselves will really only affect people that pull everything, right? And for them, it won't really matter because it is just another directory that gets mirrored. -Dan
On Sat, 2009-01-17 at 17:15 -0600, Dan McGee wrote:
On Sat, Jan 17, 2009 at 4:57 PM, Dale Blount <dale@archlinux.org> wrote:
On Sat, 2009-01-17 at 12:13 -0600, Dan McGee wrote:
Any qualms about killing [unstable] from our FTP completely? We still have the directories and the "empty" databases sitting around. I think we've given plenty of warning to people that unstable no longer exists.
It's only been missing from the mirror script for about a month now... http://wiki.archlinux.org/index.php/Local_Mirror Any mirror setup before then with this script will be throwing errors like mine is...
Not a huge issue, it gives a detailed enough message to know that unstable doesn't exist anymore and the rest of the repos continue to sync...
The rsync stanza on gerolde has definitely been gone for a while, so removing the directories themselves will really only affect people that pull everything, right? And for them, it won't really matter because it is just another directory that gets mirrored.
The script on the wiki pulls each repo directly so it does throw errors if you had unstable enabled in the SYNC_REPO array. Still not a big deal. Dale
participants (4)
-
Dale Blount
-
Dan McGee
-
Pierre Schmitz
-
Xavier