sourceforge.net download issues (was: Re: files not found when installing Gnome with garnome)

guenther <[email protected]>
Newsgroups gmane.comp.gnome.garnome
Message-ID <[email protected]>
> I took a look on sourceforge. It appears that version 1.71.0 has been
> removed.  I see version 1.70.1 [as well as 1.71.1 and 1.72].

Nope, docbook-xsl-1.71.0 still is available from sf.net.

I just tested this myself. And I paranoidly checked the latest GARNOME
release to ship this very version. ;)  I did, however, get the usual
sf.net hiccups.

This is just the well known sf.net infrastructure (read mirror) issue.
dl.sf.net is a round-robin DNS, pointing at varying mirrors for load
balancing reasons. Some of these mirrors apparently tend to time out,
instantly respond with a "404 Not Found" error, or in some rare cases
even have been caught serving some HTML file stating a "not found".
Obviously, the latter is plain wrong, and luckily doesn't seem to occur
often. A mirror timing out or just refusing to know about a tarball
happens more frequently, though.


> >  ==> Grabbing download/docbook-xsl-1.71.0.tar.bz2
> >         ==> Trying file//files/docbook-xsl-1.71.0.tar.bz2
> > make[1]: ** [file//files/docbook-xsl-1.71.0.tar.bz2] Erro 1

Normal GAR behavior. First, check if we provide the file.

> >         ==> Trying file///docbook-xsl-1.71.0.tar.bz2
> > make[1]: ** [file///docbook-xsl-1.71.0.tar.bz2] Erro 1

Next, try the GARCHIVE, if this file has been downloaded and archived
before. From the 3 slashes right in front of the file name I can tell
you did not set the GARCHIVE variable in gar.conf.mk -- which is
perfectly fine, unless you want to use it.

> >         ==> Trying http//dl.sourceforge.net/docbook/docbook-xsl-1.71.0.tar.bz2
> > --16:44:50--  http://dl.sourceforge.net/docbook/docbook-xsl-1.71.0.tar.bz2
> >            => `download/partial/docbook-xsl-1.71.0.tar.bz2'
> > Resolvendo dl.sourceforge.net... 150.65.7.130, 128.101.240.209,
> > 193.1.219.87, ...
> > Conectando a dl.sourceforge.net|150.65.7.130|:80... conectado.
> > HTTP requisição enviada, aguardando resposta... 404 Not Found
> > 16:44:51 ERRO 404: Not Found.
> > make[1]: ** [http//dl.sourceforge.net/docbook/docbook-xsl-1.71.0.tar.bz2] Erro 1

Then try the MASTER_SITES, as specified in the garballs Makefile. Here
we see the real issue -- a bad sf.net mirror.

> >         ==> Trying
> > http//ftp.gnome.org/pub/GNOME/sources/docbook-xsl/1.71/docbook-xsl-1.71.0.tar.bz2
> > --16:44:51--  http://ftp.gnome.org/pub/GNOME/sources/docbook-xsl/1.71/docbook-xsl-1.71.0.tar.bz2
> >            => `download/partial/docbook-xsl-1.71.0.tar.bz2'
> > Resolvendo ftp.gnome.org... 130.239.18.137, 2001:6b0:e:2018::137
> > Conectando a ftp.gnome.org|130.239.18.137|:80... conectado.
> > HTTP requisição enviada, aguardando resposta... 404 Not Found
> > 16:44:51 ERRO 404: Not Found.
> > make[1]: ** [http//ftp.gnome.org/pub/GNOME/sources/docbook-xsl/1.71/docbook-xsl-1.71.0.tar.bz2]
> > Erro 1

The last fallback resort is the globally defined MASTER_SITES of f.g.o,
which is the default for anything officially part of GNOME, and a lot of
other (extra as well as dependency) tarballs. Since this one is not
hosted at f.g.o, this fails, too.

Normal behavior. Since MASTER_SITES are explicitly defined, the failing
download before this one is the real issue.


> > looks like it failed to download from both Sourceforge and Gnome
> > repositories... what should I do? Just wait 'till one of the servers
> > gets back up, or is it more complicated than that? =/

Yes, it does. The reason why it does hopefully should be clear by the
above inline commenting of what really happened. :)


As long as the tarball actually still is at the expected download
location (which it is), there is one way to fix this kind of temporary
sf.net mirror glitch -- keep insisting. :)

$ cd bootstrap/docbook-xsl
$ make fetch

You will see the IP to download from changing. If it doesn't succeed,
try fetching again -- eventually, it will grab the tarball from a good
mirror. Once you got the tarball, simply cd back to where you started
the build in the first time (likely desktop/) and run the command again
you issued to start the build (make paranoid-install). GARNOME will pick
up where it left off.

  guenther


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

-- 
garnome-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/garnome-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.