RE: [opensuse-project] Site going down at release - solution
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2006-12-06 a las 13:06 -0500, Anthony Bryan escribió: [ You wrote to me direct, and I tried to answer direct; but comcast doesn't like my IP, so I have to answer in the list. As the subject may interest others and there is nothing private, I suppose there is no harm] [or we take it to a different list, if OT]
I'll mention that is is not possible to compile aria2-0.9.0.tar.bz2 in suse 10.1, a dependency problem: it needs libxml 2.6.24, and 10.1 has 2.6.23. That support is necesary for the metalink part of the program.
I opened a thread about this in opensuse, please answer there. I just want to call your attention to that; me and many others will not be able to use metalink this run, I'm afraid.
Thanks for checking that out Carlos. I wonder if the config files can be changed to depend on 2.6.23. It used to be 2.6.26, but was lowered for Ubuntu which depends on 2.6.24.
I don't know how to do that, it's over me. If you have a patch, or instructions, I can certainly try. I'm not a Linux developer; I was an MsDos one. For the few things I write for my use, I don't use configure scripts, no need, thus I don't know how they work, execpt vaguely. What I did was to try the previous aria version (aria2-0.8.1.tar.bz2) but it also has the same problem.
Or maybe a newer libxml2 could be supplied.
That's a no-no for suse: they never change package versions for a distro once delivered, unless forced to.
It would be really nice if people running SuSE could use metalink to download upgrades. It seems like binaries are available on most other platforms, so most others will be able to use it.
There is no link in the wiki page to any metalink client in rpm form: people are forced to compile their own. I have been pointed to one in the guru repository, but I don't trust it. I don't think many people will use metalink with so many dificulties... we from the mass are not using 10.2 yet. I'm running the configure for "wxDownload Fast" at this very moment. I'll see if I can use that client instead. [...] No problems there. Let's see the make... It "made" in 6 minutes, and it runs. I'll have to find something to try it on ;-) - -- Saludos Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFdzG9tTMYHG2NR9URAj8/AJwKT3q3P7Pt7/GcDrmX0rCmQoCGFACfWi3s isp/eqK9BZOjrRmm+ibO6jk= =KMSg -----END PGP SIGNATURE-----
On Wednesday 06 December 2006 21:10, Carlos E. R. wrote:
There is no link in the wiki page to any metalink client in rpm form: people are forced to compile their own. I have been pointed to one in the guru repository, but I don't trust it. I don't think many people will use metalink with so many dificulties... we from the mass are not using 10.2 yet.
I did just make this page today, but: http://en.opensuse.org/Metalinks That's the page I plan on pointing people to who are having problems downloading. I agree that at least aria2 should be in the main repository, but I think you underestimate the usage of Guru. The "masses" on SUSE all use Guru, as far as I've seen. It's *the* place to get amarok, for example. But of course that doesn't exclude the hundreds (thousands?) of other packages that are available there. It's only second to packman in terms of popular 3rd-party repositories. I see no reason to distrust it in the case of aria2. Kind thoughts, Francis. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-12-06 at 21:34 -0000, Francis Giannaros wrote:
On Wednesday 06 December 2006 21:10, Carlos E. R. wrote:
There is no link in the wiki page to any metalink client in rpm form: people are forced to compile their own. I have been pointed to one in the guru repository, but I don't trust it. I don't think many people will use metalink with so many dificulties... we from the mass are not using 10.2 yet.
I did just make this page today, but: http://en.opensuse.org/Metalinks That's the page I plan on pointing people to who are having problems downloading.
Point http://en.opensuse.org/Released_Version#Metalink to it, then.
I agree that at least aria2 should be in the main repository, but I think you underestimate the usage of Guru. The "masses" on SUSE all use Guru, as far as I've seen. It's *the* place to get amarok, for example.
My amarok is the one from SuSE and works fine ;-) But I had no way of knowing that aria2 was there.
But of course that doesn't exclude the hundreds (thousands?) of other packages that are available there. It's only second to packman in terms of popular 3rd-party repositories. I see no reason to distrust it in the case of aria2.
No, the "distrust" is because I don't know how it has been prepared, knowing that aria2 needs a xml library that is not in 10.1: ie, it refuses to make in 10.1. How was it built, then? My remark about the masses not being able to use metalink is because the download page does not point to rpms of metalink clients, only to sources, and one of them is not compilable. I have wxdfast sucesfully compiled, anyway. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFdz48tTMYHG2NR9URAjysAJ9gFAd9IZLUX1AxD5Lhr+mHUBO/igCfe/ok 4fyLcWE5W02NvOREVkLG9Ck= =tAuj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Wed, Dec 06, 2006 at 11:03:31PM +0100, Carlos E. R. wrote:
No, the "distrust" is because I don't know how it has been prepared, knowing that aria2 needs a xml library that is not in 10.1: ie, it refuses to make in 10.1. How was it built, then?
I personaly would not wory about that. Do you know how all the openSUSE stuff is build? I don't and I don't care. As long as it works, I am happy. Only if it isn't might I go and look why. Wether this is from Guru, Packman or openSUSE or any other source. houghi -- To have a nice mailinglist experience, follow the guidelines below:
Please do not toppost. Please turn off HTML Read http://en.opensuse.org/Opensuse_mailing_list_netiquette Read http://www.catb.org/~esr/faqs/smart-questions.html
To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Wednesday 06 December 2006 22:03, Carlos E. R. wrote:
Point http://en.opensuse.org/Released_Version#Metalink to it, then.
Done, now.
No, the "distrust" is because I don't know how it has been prepared, knowing that aria2 needs a xml library that is not in 10.1: ie, it refuses to make in 10.1. How was it built, then?
I don't know, but it works quite well here. Perhaps yaloki can add some points on this, or if you're quite interested I'm sure you could email him about it.
My remark about the masses not being able to use metalink is because the download page does not point to rpms of metalink clients, only to sources, and one of them is not compilable.
I think it'd be nice to get aria2 in by default, for sure. I've added the links onto the download page, now. Any feedback on this is appreciated. Would be nice to have them there for the 10.2 release tomorrow; I think they'll be quite handy. Regards, Francis. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Francis Giannaros wrote:
On Wednesday 06 December 2006 22:03, Carlos E. R. wrote:
Point http://en.opensuse.org/Released_Version#Metalink to it, then.
Done, now.
No, the "distrust" is because I don't know how it has been prepared, knowing that aria2 needs a xml library that is not in 10.1: ie, it refuses to make in 10.1. How was it built, then?
I don't know, but it works quite well here. Perhaps yaloki can add some points on this, or if you're quite interested I'm sure you could email him about it.
Well... 1) it doesn't need an XML library that is not in 10.1: libxml2 is used by tons of other packages and is obviously shipped with SUSE (including 10.1) 2) the only issue is that the configure script doesn't detect the libxml2 headers as being under /usr/include/libxml2 (I guess other distributions package it under /usr/include instead) I already sent a mail that explains how to build aria2. The trick is as simple as export CXXFLAGS="-I/usr/include/libxml2" ./configure ... && make && make install Finding out how I built it is as simple as unpacking the src.rpm and having a look at the .spec file.
My remark about the masses not being able to use metalink is because the download page does not point to rpms of metalink clients, only to sources, and one of them is not compilable.
I think it'd be nice to get aria2 in by default, for sure.
Indeed. It's a good CLI parallel/segmented downloader too (and it does bittorrent).
I've added the links onto the download page, now. Any feedback on this is appreciated. Would be nice to have them there for the 10.2 release tomorrow; I think they'll be quite handy.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-12-07 at 01:09 +0100, Pascal Bleser wrote:
2) the only issue is that the configure script doesn't detect the libxml2 headers as being under /usr/include/libxml2 (I guess other distributions package it under /usr/include instead)
They are detected, but it complains they are too old.
I already sent a mail that explains how to build aria2. The trick is as simple as export CXXFLAGS="-I/usr/include/libxml2" ./configure ... && make && make install
No... that doesn't work: *** An old version of libxml (2.6.23) was found. *** You need a version of libxml newer than 2.6.24. The latest version of - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFd4FjtTMYHG2NR9URAjHCAJ0To7NSJXSD+Urc7/7AKq+4pAb5wQCgmE42 zG6arPcXphvih2NSelvt/N4= =LqBj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
I think it'd be nice to get aria2 in by default, for sure.
Indeed. It's a good CLI parallel/segmented downloader too (and it does bittorrent).
I just wanted to echo this. I hope aria2 gets included in the next version of openSUSE. The more people that are exposed to it, the better. Whether you use ftp/http, bittorrent, or metalink to download the new ISOs, aria2 is a very handy CLI downloader. It doesn't use as many system resources as Azureus (which I use from time to time, good in certain cases but kinda bogs down my system). KDE4 will have a new version of KGet which should support metalink. The whole GUI aspect and integration should make metalink use more accessible to non CLI users. (( Anthony Bryan )) Metalink [ http://www.metalinker.org ] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-12-07 at 13:16 -0500, Anthony Bryan wrote:
I just wanted to echo this.
I hope aria2 gets included in the next version of openSUSE. The more people that are exposed to it, the better.
True.
Whether you use ftp/http, bittorrent, or metalink to download the new ISOs, aria2 is a very handy CLI downloader. It doesn't use as many system resources as Azureus (which I use from time to time, good in certain cases but kinda bogs down my system).
I have tried "wxdfast" with this release metalink, and it seems nice, but it was unable to download anything at all. It doesn't have an online help, nor man or info, no html doc. Hold on, there is a man page, but for some unknown reason, it doesn't work for me - ah, because it installed to /usr/local/share/man, instead of /usr/local/man. Anyway, it didn't work, it is probably in early development stages. Next time perhaps. So, I switched to aria2c from guru, and that one worked instantly and fast, maxing my adsl throughput. Very effective, though no eye candy. Pity I couldn't compile it myself earlier. The trick, by the way is editing the configure script: min_xml_version=2.6.23 # min_xml_version=2.6.24 Works fine, too :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFeJm6tTMYHG2NR9URAv20AJ4tundBJ4aLOECpwj6+va3o/9R72QCfXuHQ JqNbNM3vsnIe4sWTrs9y3SQ= =PEGW -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-12-07 at 23:46 +0100, Carlos E. R. wrote: ...
So, I switched to aria2c from guru, and that one worked instantly and fast, maxing my adsl throughput. Very effective, though no eye candy. Pity I couldn't compile it myself earlier.
aria2c finished the download with a checksum error - suposedly metalink had strong advanced error correction methods to avoid this very thing, but it doesn't work :-( I started it again to check, and it destroyed what was downloaded, starting from zero! :-// I'm sorry, but I have to recomend not to use metalink, nor aria2c. This is not ready for primetime, folks. I'll stay with torrent, thanks. Details and technical answers to the opensuse list, please. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFeMwPtTMYHG2NR9URAiiNAJwKBHY/cpo4JjUBGWVo6h5RCLdnQgCfViBu PXwKeFX1cX1TPWjMT4vyLeI= =bPkw -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hi, Carlos.
aria2c finished the download with a checksum error - suposedly metalink had strong advanced error correction methods to avoid this very thing, but it doesn't work :-(
I'm very sorry you had a negative experience with metalink. (Hope you will have good ones in the future, when you are ready to try again). Downloading ISOs, spending all that time and bandwidth, and ending up w/ errors is very frustrating. I've been there, and that's one thing I've tried to fix w/ metalink. Unfortunately, metalink clients don't do magic yet and can only work with what information they have. Regarding error correction: Some metalink files contain no full file checksums, some contain full file checksums, some contain segment AND full file checksums, and some contain FTP/HTTP mirror links AND torrents. The segment checksums allow portions of the download with errors to be discarded, and faulty mirrors as well. Only the portions that had errors will need to be re-downloaded - aria2 doesn't support this yet. metalink clients that support torrents can use the error correction of the torrents on data received from FTP/HTTP mirrors. The openSUSE metalinks at http://download.packages.ro/metalink/opensuse/ only contain mirrors and full file checksums. (Note: These metalinks are not generated by me). This means metalink clients will download from the mirrors, and basically run an automated 'md5sum filename' once the full file has transferred - this is more verification than error correction, because it only tells you if the file is exactly correct or wrong. With a full file checksum, you still have to re-download the whole file all over again if it doesn't match.
I started it again to check, and it destroyed what was downloaded, starting from zero! :-//
Definitely a bug in aria2, please report it at their page: http://aria2.sourceforge.net . I haven't seen that happen before.
I'm sorry, but I have to recomend not to use metalink, nor aria2c. This is not ready for primetime, folks. I'll stay with torrent, thanks.
Details and technical answers to the opensuse list, please.
When you say that, it translates to "I have to recommend not to use FTP/HTTP mirrors" since that is what aria2 is doing. FTP/HTTP is not error proof, there will be errors in transfers. One error in a whole 3GB transmission means the full file checksum will not match. Some recommendations: Encourage aria2 to support segment checksums. Then, only the segments with errors will need to be re-downloaded, instead of the whole file, saving a lot of time. Encourage metalink makers to include segment checksums. (( Anthony Bryan )) Metalink [ http://www.metalinker.org ] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-12-08 at 10:27 -0500, Anthony Bryan wrote:
aria2c finished the download with a checksum error - suposedly metalink had strong advanced error correction methods to avoid this very thing, but it doesn't work :-(
I'm very sorry you had a negative experience with metalink. (Hope you will have good ones in the future, when you are ready to try again).
Downloading ISOs, spending all that time and bandwidth, and ending up w/ errors is very frustrating. I've been there, and that's one thing I've tried to fix w/ metalink. Unfortunately, metalink clients don't do magic yet and can only work with what information they have.
Regarding error correction: Some metalink files contain no full file checksums, some contain full file checksums, some contain segment AND full file checksums, and some contain FTP/HTTP mirror links AND torrents.
The segment checksums allow portions of the download with errors to be discarded, and faulty mirrors as well. Only the portions that had errors will need to be re-downloaded - aria2 doesn't support this yet. metalink clients that support torrents can use the error correction of the torrents on data received from FTP/HTTP mirrors.
Too bad. I was misled to think this was handled properly.
The openSUSE metalinks at http://download.packages.ro/metalink/opensuse/ only contain mirrors and full file checksums. (Note: These metalinks are not generated by me). This means metalink clients will download from the mirrors, and basically run an automated 'md5sum filename' once the full file has transferred - this is more verification than error correction, because it only tells you if the file is exactly correct or wrong. With a full file checksum, you still have to re-download the whole file all over again if it doesn't match.
Too bad of Novell not to prepare partial chunk checks, but that would have been useless as aria2c doesn't support it.
I started it again to check, and it destroyed what was downloaded, starting from zero! :-//
Definitely a bug in aria2, please report it at their page: http://aria2.sourceforge.net . I haven't seen that happen before.
I'm so... disgusted that I don't think I'll bother. There it was the downloaded file, with an error somewhere, and when I restarted aria2c, instead of rechecking, or telling me that it was complete, it overwrote it with zeroes and started to download from the start. No warning! I know how to repair a download with errors, but I had no chance to try. So I have started again with btdownloadcurses, which is going three times slower than aria2c.
I'm sorry, but I have to recomend not to use metalink, nor aria2c. This is not ready for primetime, folks. I'll stay with torrent, thanks.
Details and technical answers to the opensuse list, please.
When you say that, it translates to "I have to recommend not to use FTP/HTTP mirrors" since that is what aria2 is doing. FTP/HTTP is not error proof, there will be errors in transfers. One error in a whole 3GB transmission means the full file checksum will not match.
Yes, but: I had assumed that the proclaimed reliability of the protocol meant that this was handled somehow: if a chunk is in error, repeat download of that single chunk. The end result most be perfect. If there is no chunk testing in aria2c (wxdfast did not work at all), and the metalink file (from Novell) contains no chunk info, this is no better than plain ftp or http (or even worse if a single mirror is broken and not traceable). I'm not testing it again till this is solved, sorry. If I had been bitten with a smaller download I would not be so disgusted. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFeYyntTMYHG2NR9URAvXbAJ95sJuHHRbdetgnSkdec8woHBX9DgCdHUFT 1do++fbcLWZU66avENw2tE4= =F+Ob -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (5)
-
Anthony Bryan -
Carlos E. R. -
Francis Giannaros -
houghi -
Pascal Bleser