curl causing troubles both from yast2 and zypper

English Install/Boot/Login
#1

I’ve always felt curl was a bad choice for package management, as its abilities for retrying a stale download or restarting/continueing a broken one just suck.

Now I have a real confirmation for that. Trying to install a package from the KDE:Extra repositories, yast2 says the following:

Download (curl) error for ‘http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm’:
Error code: User abort
Error message: Callback aborted

Trying curl from the command line:

curl http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm
<!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href=“http://ftp.halifax.rwth-aachen.de/opensuse/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm”>here</a>.</p>
<hr>
<address>Apache/2.2.10 (Linux/SUSE) Server at download.opensuse.org Port 80</address>
</body></html>

and the same with wget works fine:

wget http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm
asking libproxy about url ‘http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm’
libproxy suggest to use ‘direct://’
–2011-03-25 11:02:16-- http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm
Resolving download.opensuse.org… 195.135.221.134
Connecting to download.opensuse.org|195.135.221.134|:80… connected.
HTTP request sent, awaiting response… 302 Found
Location: http://ftp.halifax.rwth-aachen.de/opensuse/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm [following]
asking libproxy about url ‘http://ftp.halifax.rwth-aachen.de/opensuse/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm’
libproxy suggest to use ‘direct://’
–2011-03-25 11:02:16-- http://ftp.halifax.rwth-aachen.de/opensuse/repositories/KDE:/Extra/openSUSE_11.4/i586/plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm
Resolving ftp.halifax.rwth-aachen.de… 137.226.34.42
Connecting to ftp.halifax.rwth-aachen.de|137.226.34.42|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 229753 (224K) [application/x-redhat-package-manager]
Saving to: “plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm”

100%===================================================================================================================================================>] 229,753 1.36M/s in 0.2s

2011-03-25 11:02:16 (1.36 MB/s) - “plasmoid-yawp-debugutils-0.3.6-1.1.i586.rpm” saved [229753/229753]

#2

So presently I can download files from this repository:

http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/

Is it possible this was just a temporary network issue or maybe a repository update was going on while you were trying to use it? Did you attempt to remove this repository and then re-add it back it, thus causing YaST / Software / Software Repositories to redo its entry?

Thank You,

#3

Not had a problem with YasT, repos or network all day, and that includes two system upgrades with masses of package downloads.

#4

Trying curl from the command line:
curl http://download.opensuse.org/reposit...6-1.1.i586.rpm

Curl is doing exactly what you told it to, its going to http://download.opensuse.org/reposit...6-1.1.i586.rpm
The server on the other hand is telling the client that the content has moved, hence the message “The document has moved…”

Try curl with the -L switch and you should get the file. The -L switch tells curl to request the new page where the content has moved.


curl -L http://download.opensuse.org/reposit...6-1.1.i586.rpm

I’m not sure how yast is making the curl call…

Good luck,
Hiatt

#5

On 2011-03-26 00:06, jthiatt08 wrote:
> I’m not sure how yast is making the curl call…

That’s easy to find out: it is in the log.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)