Arch Linux

metalfan

Member

Registered: 2007-11-22

Posts: 99

32bit chroot, bad request?

Hi,

ive used the 32bit chroot howto in the wiki to get a 32bit system installed (pacman.static -r /newroot -Sy base)
but it keeps coming up with:

pacman -Sy hal
:: Synchronizing package databases...

error: failed retrieving file 'core.db.tar.gz' from ftp.archlinux.org : Bad Request
error: failed retrieving file 'core.db.tar.gz' from locke.suu.edu : Bad Request
error: failed retrieving file 'core.db.tar.gz' from mirrors.unixheads.org : Bad Request
error: failed retrieving file 'core.db.tar.gz' from ftp-linux.cc.gatech.edu : Bad Request
error: failed retrieving file 'core.db.tar.gz' from mirror.cs.vt.edu : Bad Request
 core is up to date
error: failed retrieving file 'extra.db.tar.gz' from ftp.archlinux.org : Bad Request
error: failed retrieving file 'extra.db.tar.gz' from locke.suu.edu : Bad Request
error: failed retrieving file 'extra.db.tar.gz' from mirrors.unixheads.org : Bad Request
error: failed retrieving file 'extra.db.tar.gz' from ftp-linux.cc.gatech.edu : Bad Request
error: failed retrieving file 'extra.db.tar.gz' from mirror.cs.vt.edu : Bad Request
 extra is up to date
error: failed retrieving file 'community.db.tar.gz' from ftp.archlinux.org : Bad Request
error: failed retrieving file 'community.db.tar.gz' from locke.suu.edu : Bad Request
error: failed retrieving file 'community.db.tar.gz' from mirrors.unixheads.org : Bad Request
error: failed retrieving file 'community.db.tar.gz' from ftp-linux.cc.gatech.edu : Bad Request
error: failed retrieving file 'community.db.tar.gz' from mirror.cs.vt.edu : Bad Request
 community is up to date
error: 'hal': not found in sync db

Whats that about?
Usually it gave me the error but eventually it would find a working mirror. this is somehow a client problem since i dont get those errors from my not chrooted system nor from another one. Is this a 32/64bit problem somehow?

metalfan

Member

Registered: 2007-11-22

Posts: 99

Re: 32bit chroot, bad request?

The system works now on my PII without problems, still dont know where the chroot errors came from.