FS#8408 - x86_64 version of pacman.static fails to fetch
Attached to Project:
Pacman
Opened by Maik Beckmann (Salamander1978) - Wednesday, 24 October 2007, 20:25 GMT
Last edited by Xavier (shining) - Saturday, 12 September 2009, 10:53 GMT
Opened by Maik Beckmann (Salamander1978) - Wednesday, 24 October 2007, 20:25 GMT
Last edited by Xavier (shining) - Saturday, 12 September 2009, 10:53 GMT
|
Details
Description:
I wanted to install arch64 via chroot. The host is a recent Debian unstable x86 system. I installed a amd64 kernel from repository and booted this kernel. Running the x86_64 version of pacman.static on gives: error: failed retrieving file 'core.db.tar.gz' from ftp.archlinux.org : No address record ... # the same for all other servers ... error: failed to synchronize core: No address record error: failed to synchronize any databases Additional info: * package version(s) - pacman-3.0.6-1-x86_64 * related references I started this thread at http://bbs.archlinux.org/ which includes a workaround http://bbs.archlinux.org/viewtopic.php?id=39032 Steps to reproduce: Download ftp://ftp.archlinux.org/current/os/x86_64/pacman-3.0.6-1-x86_64.pkg.tar.gz unpack it and do cp /path/to/pacman-3.0.6-1-x86_64.pkg/etc/pacman.conf /etc cp /path/to/pacman-3.0.6-1-x86_64.pkg/etc/pacman.d /etc -r To reproce this bug its not necessary to create a new partition. Doing mkdir /path/to/test_pacman /path/to/pacman-3.0.6-1-x86_64.pkg/usr/bin/pacman.static -Sy -r /path/to/test_pacman is sufficient. |
This task depends upon
I tried the same on a pure Debian AMD64 system and 64-bit pacman.static runs perfect. So this bug is triggered only, if 64-bit pacman.static runs on a
32-bit system which runs a 64-bit kernel.
-Salamander
Now that I'm a happy new arch-x86_64 user I wanted to change my debian-i386 installation to arch-i686.
I moved /etc/pacman.conf /etc/pacmand.d to *_bak and tried to run
/path/to/pacman-3.0.6-1-i686.pkg/pacman.static
and guess what:
error: failed retrieving file 'core.db.tar.gz' from ftp.archlinux.org : No address record
...
# the same for all other servers
...
error: failed to synchronize core: No address record
error: failed to synchronize any databases
However, to me it seems that its always possible to ship around this bug. The following four cases cover all possibilities:
1.) i686 -> i686
To install arch-i686 from a running native DistroFoo-x86 installation do:
- get and unpack pacman-*-i686.pkg.tar.gz
- (if you're running a pacman based) backup /etc/pacman.*
- copy pacman-*-i686.pkg/etc/pacman.* to /etc
- run pacman-*-i686.pkg/usr/bin/pacman.static -Sy -r myarch-i686-dir
- ...
2.) x86_64 -> x86_64
To install arch-x86_64 from a running native DistroFoo-x86_64 installation do:
- get and unpack pacman-*-x86_64.pkg.tar.gz
- (if you're running a pacman based) backup /etc/pacman.*
- copy pacman-*-x86_64.pkg/etc/pacman.* to /etc
- run pacman-*-x86_64.pkg/usr/bin/pacman.static -Sy -r myarch-x86_64-dir
- ...
3.) x86_64 -> i686
To install arch-i686 from a running native DistroFoo-x86_64 installation do:
- get and unpack pacman-*-i686.pkg.tar.gz
- get and unpack pacman-*-x86_64.pkg.tar.gz
- (if you're running a pacman based) backup /etc/pacman.*
- copy pacman-*-i686.pkg/etc/pacman.* to /etc
- run pacman-*-x86_64.pkg/usr/bin/pacman.static -Sy -r myarch-i686-dir
- ...
4.) i686 -> x86_64
To install arch-x86_64 from a running DistroFoo-x86 installation do:
- install a x86_64 kernel and boot it, otherwise you chroot won't work!
- get and unpack pacman-*-i686.pkg.tar.gz
- get and unpack pacman-*-x86_64.pkg.tar.gz
- (if you're running a pacman based) backup /etc/pacman.*
- copy pacman-*-x86_64.pkg/etc/pacman.* to /etc
- run pacman-*-i686.pkg/usr/bin/pacman.static -Sy -r myarch-x86_64-dir
- ...
BTW: Is is possible to install a x86_64 kernel at arch-i686 ?
I didn't watched at pacman's source code, but it seems that x86_64/i686 pacman.static messes around with curl or something like that on a i686/x86_64.
However, IMHO this bug doesn't harm anyone and since its always possible to fool it I vote for spending your time on other things.
Regards,
- Maik Beckmann
I really am at a loss here seem to be getting nowhere on my own. Thanks.
"No address record" suggests that DNS is failing. Can you ping by hostname? By ip?
Let's look at the original bug reported :
"So this bug is triggered only, if 64-bit pacman.static runs on a
32-bit system which runs a 64-bit kernel."
I don't know, but doing that sounds really odd to me. So I would just close this as invalid, and just use proper pacman binaries for the proper architecture ...
The bug reported by Ryan is likely different and a network issue or misconfiguration of some sort. If you look at the bbs thread, he never even replied there, and it was 8 months ago !
Two people reported they had the same issues in that thread :
1) I experienced the same and I found out that a wrongful avahi configuration (missing nss-mdns package) was causing these dns resolution errors with wget but not with ping.
2) may bad, i left wrong export proxy in login script.
so nothing to do with pacman ...