Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: > Okay then. Attached is the new, improved Masterlister program. It should > just compile with "mcs Masterlister.cs", using the MCS compiler from > Mono. Usage is "Masterlister.exe path/to/source/masterlist" - a diff is > produced on STDOUT (with program info on STDERR, a bit like OggEnc). I guess the really nice thing to do would be to integrate this with http://www.de.debian.org/dmc/today/ Or it could be checked into the website cvs, though it would probably be best to put it under an actual defined license like the GPL first. > Also attached is another diff. Applied. -- see shy jo signature.asc Description: Digital signature
Re: amd64 situation in Mirrors.masterlist
Joey Hess wrote:
Jo Shields wrote:
Would it be useful to refine the rather rushed tools used to create the
diff, removing any manual steps from Mirrors.masterlist to .diff?
Yes.
Okay then. Attached is the new, improved Masterlister program. It should
just compile with "mcs Masterlister.cs", using the MCS compiler from
Mono. Usage is "Masterlister.exe path/to/source/masterlist" - a diff is
produced on STDOUT (with program info on STDERR, a bit like OggEnc).
This program goes through the source file, and for each Site: entry with
an Archive-http or Archive-ftp (HTTP preferred) will download a
directory listing for $MIRRORLOCATION/dists/sid/main/ to a temporary
location. Mirrors are tried only once, and given a 30 second timeout.
The listing file is then parsed using a simple regular expression to
build a hashtable of architectures held on a given mirror. The source
file is re-read, written verbatim to the temporary location, with
Archive-architecture: lines replaced where a replacement is stored in
the hashtable. Finally, diff is called to compare the source and new files.
Also attached is another diff. Due to a pair stupid 1-character typos on
my previous effort, FTP-only mirrors were being counted as bad, as were
HTTP mirrors whose HREFs didn't end with "/". New statistics are: 330
sites in Mirrors.masterlist, of which 289 are archive mirrors. 254 of
the archive mirrors are polled automatically without issue. Of those
254, only 2 returned bad directory listings (HTTP but not FTP on
ftp.is.co.za appears broken; ftp.mcc.ac.uk seems to have hiccuped as
it's fine via a web browser)
//
// Masterlister.cs: Reads Mirrors.masterlist file, attempts to contact
// the mirrors, and updates the Archive-architecture
// lines appropriately
//
// Author:
// Jo Shields ([EMAIL PROTECTED])
//
// Licensed under Do What The Fuck You Want To Public License (WTFPL)
// Version 2.
//
using System;
using System.Collections;
using System.Diagnostics;
using System.IO;
using System.Text.RegularExpressions;
namespace Masterlister
{
class MainClass
{
public static void Main(string[] args)
{
Console.Error.WriteLine( "Masterlister v0.01 by Jo Shields\n\n" );
if( args.Length != 1 )
ShowUsageThenExit( );
FileInfo SourceMasterlist = new FileInfo( args[0] );
if( !SourceMasterlist.Exists )
ShowUsageThenExit( );
string tempFolder = Path.Combine( Path.GetTempPath(), Path.GetTempFileName() );
File.Delete( tempFolder );
Directory.CreateDirectory( tempFolder );
GetMirrorListings( tempFolder, SourceMasterlist.FullName );
Hashtable HostedArches = GetHostedArches( tempFolder );
CreateNewMasterlist( tempFolder, SourceMasterlist.FullName, HostedArches );
Process diffProcess = new Process( );
diffProcess.StartInfo.FileName = "diff";
diffProcess.StartInfo.Arguments = "-u " + SourceMasterlist.FullName + " " + Path.Combine( tempFolder, "Mirrors.masterlist" );
diffProcess.Start( );
diffProcess.WaitForExit( );
Directory.Delete( tempFolder, true );
}
private static void ShowUsageThenExit( )
{
Console.Error.WriteLine( "Usage: masterlister.exe original-list\n\nDiffed list is written to STDOUT,\n program messages to STDERR" );
Environment.Exit( 0 );
}
private static void CreateNewMasterlist( string tempFolder, string sourceFile, Hashtable HostedArches )
{
StreamReader SourceReader;
StreamWriter TargetWriter;
string currentLine = "";
Regex HostMatch = new Regex( "Site: (.*)" );
Regex ArchMatch = new Regex( "Archive-architecture: (.*)" );
SourceReader = File.OpenText( sourceFile );
TargetWriter = File.CreateText( Path.Combine( tempFolder, "Mirrors.masterlist" ) );
currentLine = SourceReader.ReadLine();
string CurrentHost = "";
while( currentLine != null )
{
if( currentLine.Trim( ) == "" )
CurrentHost = "";
if( HostMatch.IsMatch( currentLine.Trim( ) ) )
CurrentHost = HostMatch.Split( currentLine.Trim( ) )[1];
if( ArchMatch.IsMatch( currentLine.Trim( ) ) )
{
if( CurrentHost != "" && HostedArches.ContainsKey( CurrentHost ) )
{
TargetWriter.Write( "Archive-architecture:" );
foreach( string Arch in (string[])(HostedArches[CurrentHost]) )
TargetWriter.Write( " {0}", Arch );
TargetWriter.WriteLine( );
CurrentHost = "";
}
else
TargetWriter.WriteLine( currentLine );
}
else
TargetWriter.WriteLine( currentLine );
currentLine = SourceReader.ReadLine( );
}
SourceReader.Close( );
TargetWriter.Close( );
}
private static Hashtable GetHostedArches( string tempFolder )
{
Hashtable Arches = new Hashtable( );
StreamReader MirrorReader;
ArrayList MirrorArches = new ArrayList( );
Regex ArchesMatch = new Regex( "binary-([a-zA-Z0-9-]+)" );
Fi
Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: > Would it be useful to refine the rather rushed tools used to create the > diff, removing any manual steps from Mirrors.masterlist to .diff? Yes. -- see shy jo signature.asc Description: Digital signature
Re: amd64 situation in Mirrors.masterlist
Joey Hess wrote: Jo Shields wrote: Done. Mirrors I couldn't update automatically are detailed in my earlier message (the 11 I couldn't contact, plus 65 that didn't provide a correct directory listing for dists/sid/main/). Thanks, applied. I hope you can do this again from time to time, although please send unified diffs in the future. I knew I forgot a flag of some kind. -u was it. Would it be useful to refine the rather rushed tools used to create the diff, removing any manual steps from Mirrors.masterlist to .diff? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: > Done. Mirrors I couldn't update automatically are detailed in my earlier > message (the 11 I couldn't contact, plus 65 that didn't provide a > correct directory listing for dists/sid/main/). Thanks, applied. I hope you can do this again from time to time, although please send unified diffs in the future. -- see shy jo signature.asc Description: Digital signature
Re: amd64 situation in Mirrors.masterlist
Goswin von Brederlow wrote: > Should the master list ignore the "sarge has no amd64" issue and just > list amd64 for mirrors that have it in etch/sid? > > Or should there be two entries for every mirror, one for sarge/!amd64 > and one for etch/sid with all archs? Mirrors.masterlist does not provide a way to limit a mirror to a given release. It's only used by d-i for etch anyway, and for the web site. > On the same note, should the sarge/amd64 mirrors get removed in > preparation of stable/etch having amd64? Those mirrors have already been removed. -- see shy jo signature.asc Description: Digital signature
Re: amd64 situation in Mirrors.masterlist
Joey Hess <[EMAIL PROTECTED]> writes: > A quick look at what Mirrors.masterlist says about mirrors carrying > amd64 finds a lot of probably wrong information: > > * 154 mirrors listed as mirroring !amd64, but having all other arches. This is > probably wrong for most of them ... it's definitly wrong for the couple I > spot-checked. That will only be true for sarge in nearly all cases. Etch/sid should have amd64. > * 69 mirrors listed as mirroring only amd64 and one or two other arches. > Probably correct for most of them. That will be only true for sarge and they should only list sarge. Should the master list ignore the "sarge has no amd64" issue and just list amd64 for mirrors that have it in etch/sid? Or should there be two entries for every mirror, one for sarge/!amd64 and one for etch/sid with all archs? On the same note, should the sarge/amd64 mirrors get removed in preparation of stable/etch having amd64? Iirc sarge D-I needed a patched list for amd64 anyway to work right so there is not even a point for those entries for a sarge point release. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Joey Hess wrote: Jo Shields wrote: I'm not actually sure what the correct format is for Archive-architecture when something's got all supported arches The best thing to do there is to list all the arches. Done. and I'm not sure what to do about the hosts I couldn't contact - but this should save someone some time. **BADMIRROR** lines need manual checking, I'm afraid. A patch that updates Mirrors.masterlist with the arch info for the mirrors you could reach would be helpful. Done. Mirrors I couldn't update automatically are detailed in my earlier message (the 11 I couldn't contact, plus 65 that didn't provide a correct directory listing for dists/sid/main/). 89c89 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 113c113 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 126c126 < Archive-architecture: !amd64 !alpha --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sh sparc 148c148 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 198c198 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 252c252 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 265c265 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 291c291 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 314c314 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 348c348 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 370c370 < Archive-architecture: amd64 hurd-i386 i386 sparc --- > Archive-architecture: amd64 hurd-i386 i386 powerpc sparc 387c387 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 427c427 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 443c443 < Archive-architecture: !amd64 --- > Archive-architecture: alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel > powerpc s390 sh sparc 495c495 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 520c520 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 541c541 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 569c569 < Archive-architecture: !hppa !hurd-i386 !s390 --- > Archive-architecture: alpha amd64 arm i386 ia64 m68k mips mipsel powerpc sparc 624c624 < Archive-architecture: !amd64 --- > Archive-architecture: amd64 i386 640c640 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 656c656 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 676c676 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 701c701 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 720c720 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 741c741 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 754c754 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 809c809 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 863c863 < Archive-architecture: i386 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 887c887 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel powerpc s390 sparc 939c939 < Archive-architecture: !amd64 --- > Archive-architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips > mipsel power
Re: amd64 situation in Mirrors.masterlist
Joey, Here's an update for my mirror: Old Site Name: mirror.mcs.anl.gov Updated entry: -- Site: mirror.anl.gov Aliases: n/a Type: leaf Archive-ftp: /pub/debian/ Archive-architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc Archive-http: /debian/ Mirrors-from: ftp.debian.org Maintainer: Brian Elliott Finley <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Country: US United States Location: Chicago, Illinois Sponsor: Argonne National Laboratory http://www.anl.gov/ Comment: This is a complete mirror, connected by Gigabit. Cheers, -Brian Thus spake Joey Hess ([EMAIL PROTECTED]): A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636&root=webwml&view=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) -- see shy jo -- Brian Elliott Finley Mobile: 630.631.6621 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: > I'm not actually sure what the correct format is for Archive-architecture > when something's got all supported arches The best thing to do there is to list all the arches. > and I'm not sure what to do about the hosts I > couldn't contact - but this should save someone some time. **BADMIRROR** > lines need manual checking, I'm afraid. A patch that updates Mirrors.masterlist with the arch info for the mirrors you could reach would be helpful. -- see shy jo signature.asc Description: Digital signature
Re: amd64 situation in Mirrors.masterlist
Andreas Barth wrote: > * Jo Shields ([EMAIL PROTECTED]) [060808 12:17]: > > What's the correct procedure for a) Defunct, unresponsive or incorrect > > mirror entries such as 'Site: www.zentek-international.com' (wrong > > Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six > > mirrors with "sh" architecture? > > Prodding the administrators, and, failing that, removing the entry. And bearing in mind that one or two mirrors are only accessible from inside their target country. (Which certianly makes it hard to check them..) -- see shy jo signature.asc Description: Digital signature
Re: amd64 situation in Mirrors.masterlist
* Jo Shields ([EMAIL PROTECTED]) [060808 12:17]: > What's the correct procedure for a) Defunct, unresponsive or incorrect > mirror entries such as 'Site: www.zentek-international.com' (wrong > Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six > mirrors with "sh" architecture? Prodding the administrators, and, failing that, removing the entry. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: Joey Hess wrote: A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636&root=webwml&view=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) What's the correct procedure for a) Defunct, unresponsive or incorrect mirror entries such as 'Site: www.zentek-international.com' (wrong Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six mirrors with "sh" architecture? I'm showing 288 responding archive mirrors, of which 65 have some error preventing automated querying (usually condition A above) The attached mirrorstatus file should be fairly easily to parse, both by eye and by machine. It's a list of each archive Site: entry and the architectures they actually host. The list was mostly generated by the attached C# source (the **TIMEOUT** entries are manual, as my cheap use of wget doesn't let me grab that info properly). I'm not actually sure what the correct format is for Archive-architecture when something's got all supported arches, and I'm not sure what to do about the hosts I couldn't contact - but this should save someone some time. **BADMIRROR** lines need manual checking, I'm afraid. 299 total archive mirrors (HTTP or FTP) made up of: 223 correct, valid, responding mirrors 65 BADMIRRORs (manual checking required) 11 TIMEOUTs (possible routing issues for me, or dead host) of the valid mirrors: 159 Alpha mirrors 208 AMD64 mirrors 149 ARM mirrors 147 HP PA-RISC mirrors 168 HURD-i386 mirrors 223 i386 mirrors 163 IA64 mirrors 149 Motorola 68000 mirrors 150 MIPS (big endian) mirrors 149 MIPS (little endian) mirrors 167 PowerPC mirrors 146 S/390 mirrors 170 SPARC mirrors 6 Hitachi SuperH mirrors (unofficial) ameba.sc-uni.ktu.lt:i386 archive.progeny.com:alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc carroll.aset.psu.edu: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc cdn.mirror.garr.it: **BADMIRROR*** cudlug.cudenver.edu:alpha amd64 hurd-i386 i386ia64powerpc sparc debian.2z.net: **BADMIRROR*** debian.3wsi.net:**BADMIRROR*** debian.balt.net:amd64 arm i386sparc debian.blueyonder.co.uk:alpha amd64 arm hppahurd-i386 i386ia64m68kmipsmipsel powerpc s390sparc debian.cites.uiuc.edu: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.cn99.com:amd64 i386 debian.crosslink.net: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.csie.ntu.edu.tw: amd64 hurd-i386 i386 debian.efis.ucr.ac.cr: **BADMIRROR*** debian.ens-cachan.fr: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.essentkabel.com: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.experimentos.cl: amd64 i386 debian.fastbull.org:amd64 hppai386ia64sparc debian.fastweb.it: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.fifi.org:amd64 i386sparc debian.funlam.edu.co: amd64 i386 debian.goldweb.com.au: hurd-i386 i386powerpc debian.hands.com: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.ihug.co.nz: alpha amd64 arm hppahurd-i386 i386 ia64mipsmipsel powerpc s390sh sparc debian.ihug.com.au: **BADMIRROR*** debian.indika.net.id: i386 debian.inf.elte.hu: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.inode.at:alpha amd64 arm i386powerpc sparc debian.internet
Re: amd64 situation in Mirrors.masterlist
Joey Hess wrote: A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636&root=webwml&view=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) What's the correct procedure for a) Defunct, unresponsive or incorrect mirror entries such as 'Site: www.zentek-international.com' (wrong Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six mirrors with "sh" architecture? I'm showing 288 responding archive mirrors, of which 65 have some error preventing automated querying (usually condition A above) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
amd64 situation in Mirrors.masterlist
A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636&root=webwml&view=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) -- see shy jo signature.asc Description: Digital signature
