2007/5/8, Pierre Schmitz :

Am Dienstag, 8. Mai 2007 10:45:25 schrieb Roman Kyrylych:

...

2007/5/8, Scott Horowitz :

...

I get this error with pacman3 (almost?) every single time that I have to download multiple packages. Usually it will download the first package fine and then give the error "File unavailable (e.g., file not found, no access)" on the subsequent package.

Normal: Beginning upgrade process...

:: Retrieving packages from extra...

libbonoboui 381.9K 572.6K/s 00:00:01 [#########################################################] 100% error: failed retrieving file 'gnome-keyring-0.8.1-2.pkg.tar.gz' from locke.suu.edu : File unavailable (e.g., file not found, no access) error: failed retrieving file 'libgnomeui-2.18.1-2.pkg.tar.gz' from locke.suu.edu : File unavailable (e.g., file not found, no access) error: failed retrieving file 'gnome-desktop-2.18.1-1.pkg.tar.gz' from locke.suu.edu : File unavailable (e.g., file not found, no access) and so on...

Using --debug=3: http://pastebin.archlinux.org/2861

The whole CWD <random letter> seems awfully strange. Any ideas?

Did you try another mirror? Maybe some FTP server issues. :-/

I got the same problem. Pacman exists with "unkonwn error". But it does not seem to be reproduceable. Restarting pacman -Syu "solves" the problem.

I get Unknown error too, but thought it was due to my bad connection. Sometimes next file after error is downloading fine. I can post output when I'll get home (~in 10 hours). I wonder why I didn't notice that with pre-3.0.x releases. :-/ -- Roman Kyrylych (Роман Кирилич)

On 5/8/07, Xavier wrote:

Aaron just committed this : http://www.archlinux.org/pipermail/pacman-dev/2007-May/008231.html I find it strange he didn't answer here, but I believe he fixed the problem. Or at least, I needed to add a trailing slash to the Server in pacman.conf to reproduce the problem. eg : Server = ftp://mir1.archlinuxfr.org/archlinux/extra/os/i686/

and with aaron's patch, it works with the trailing slash too.

btw, the letter in argument to CWD isn't random, it's the first letter of the package each time, but that was the problem indeed :)

Yup, Aaron and I were debugging it on IRC and he discovered and fixed it. Scott