» Call for testing openSUSE 11.2 with newer aria2

As you might now, Zypp (the package management stack of openSUSE) uses the very powerful aria2 application to perform its downloads, both for repository metadata and RPM files. Before that, it used curl. Since openSUSE 11.2, the Zypp stack defaults to using aria2 (unless the environment variable ZYPP_ARIA2C is set to 0, in which case it falls back to curl). But currently, we have two issues with the aria2 version we ship in 11.2 (which is version 1.5.2):

• it still performs AAAA IPv6 lookups even when IPv6 is turned off
• there seems to be a problem with proxy support (has also been reported by Andrea Florio on IRC)

Providing an online update normally means that we backport individual, minimalistic patches that fix the reported issues, in order to avoid introducing new bugs. The policy says that version upgrades must be avoided at all costs. But in this case, it is quite tricky, as the aria2 version that fixes the two above mentioned problems is 1.8.2, and the one that ships with 11.2 is 1.5.2, which is.. erm.. quite a bump. Now, if you feel like you'd like to contribute, please upgrade your aria2 package with the one that is available in the network:utilities repository, and let us know (sending me an email at pascal.bleser at our project's email domain (which is opensuse followed by a dot and then by org) is fine too) whether that newer aria2 version works for you or not. By "works" I mean that both the zypper command-line client and YaST2's software management module function properly. Even better if you disable IPv6 or if you're behind a proxy and it suddenly works :) Here is the procedure to follow, from a terminal, running as root (can be copy/pasted as is):

zypper ar -r \
http://download.opensuse.org/repositories/network:/utilities/\
openSUSE_11.2/network:utilities.repo

zypper up -t package aria2

And then just use zypper and YaST2 as usual. Then please send me feedback (either on bugzilla or by email, as mentioned above) on whether it works for you or if you run into problems. Note that a very few initial tests show that it works very well, so it is not actually expected that it could break the whole package management stack ;) Thanks for testing!