Re: gcc-3.4 udebs gone?

2004-09-13 Thread Harald Dunkel 
Bob Proulx wrote:
It is possible that alioth may be getting overloaded.  Try one of the
following two mirrors.
  deb http://debian.inode.at/pure64/ sid main
  deb-src http://debian.inode.at/pure64/ sid main
  deb http://bach.hpc2n.umu.se/pure64 sid main
  deb-src http://bach.hpc2n.umu.se/pure64 sid main
debian.inode.at doesn't provide any packages built with
gcc-3.4 for amd64. On bach there is no debian-installer
directory.
Regards
Harri

Re: gcc-3.4 udebs gone?

2004-09-13 Thread Bob Proulx 
Harald Dunkel wrote:
 Bob Proulx wrote:
 It is possible that alioth may be getting overloaded.  Try one of the
 following two mirrors.
 
   deb http://debian.inode.at/pure64/ sid main
   deb-src http://debian.inode.at/pure64/ sid main
 
   deb http://bach.hpc2n.umu.se/pure64 sid main
   deb-src http://bach.hpc2n.umu.se/pure64 sid main
 
 debian.inode.at doesn't provide any packages built with
 gcc-3.4 for amd64. On bach there is no debian-installer
 directory.

Then you are stuck and will need to keep trying the main archive.

I think the mirrors are having problems because the main archive is
missing the files I mentioned in a previous mail about the alioth
archive not being in a consistent state.  They probably have not had a
good sync since it went inconsistent.

Bob


pgpe9MqAHckCz.pgp
Description: PGP signature

Re: gcc-3.4 udebs gone?

2004-09-13 Thread Goswin von Brederlow 
Harald Dunkel [EMAIL PROTECTED] writes:

 Kurt Roeckx wrote:
 Both binary-amd64/Packages and
 debian-installer/binary-amd64/Packages are empty.  I have no idea
 why.

 If it is allowed to make a wild guess: I would suggest to
 check the free disk space on the machine used to generate
 the Packages file.

/ on alioth was full again and then bash can't create 'here' documents
in /tmp, i.e. cat EOF fails. This tends to fix itself an hour after
/ is cleaned up.

 Good luck

 Harri

MfG
Goswin

Re: gcc-3.4 udebs gone?

2004-09-13 Thread Harald Dunkel 
Kurt Roeckx wrote:
Both binary-amd64/Packages and
debian-installer/binary-amd64/Packages are empty.  I have no idea
why.
If it is allowed to make a wild guess: I would suggest to
check the free disk space on the machine used to generate
the Packages file.
Good luck
Harri