You are not logged in.
I don't know if this should go in newbies or what..I'm sure that I just missed something small. Here is the problem:
I followed the directions from here, to install an arch32 environment (so I can use firefox with java): http://wiki.archlinux.org/index.php/Arc … bit_system
I think I got all the steps, and I checked it over twice. But, when I try to install something with pacman, I get a lot of errors like this:
gcc: /usr/share/locale/fr/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/fr/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/ja/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/ja/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/nl/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/nl/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/ru/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/rw/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/rw/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/sr/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/sv/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/sv/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/tr/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/tr/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/uk/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/vi/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/zh_CN/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/zh_CN/LC_MESSAGES/gcc.mo exists in filesystem
gcc: /usr/share/locale/zh_TW/LC_MESSAGES/cpplib.mo exists in filesystem
gcc: /usr/share/locale/zh_TW/LC_MESSAGES/gcc.mo exists in filesystem
tcp_wrappers: /etc/hosts.allow exists in filesystem
tcp_wrappers: /etc/hosts.deny exists in filesystem
tcp_wrappers: /usr/include/tcpd.h exists in filesystem
tcp_wrappers: /usr/lib/libwrap.a exists in filesystem
tcp_wrappers: /usr/lib/libwrap.so exists in filesystem
tcp_wrappers: /usr/lib/libwrap.so.0 exists in filesystem
tcp_wrappers: /usr/lib/libwrap.so.0.7.6 exists in filesystem
tcp_wrappers: /usr/man/man3/hosts_access.3.gz exists in filesystem
tcp_wrappers: /usr/man/man3/hosts_ctl.3.gz exists in filesystem
tcp_wrappers: /usr/man/man3/request_init.3.gz exists in filesystem
tcp_wrappers: /usr/man/man3/request_set.3.gz exists in filesystem
tcp_wrappers: /usr/man/man5/hosts_access.5.gz exists in filesystem
tcp_wrappers: /usr/man/man5/hosts_options.5.gz exists in filesystem
tcp_wrappers: /usr/man/man8/safe_finger.8.gz exists in filesystem
tcp_wrappers: /usr/man/man8/tcpd.8.gz exists in filesystem
tcp_wrappers: /usr/man/man8/tcpdchk.8.gz exists in filesystem
tcp_wrappers: /usr/man/man8/tcpdmatch.8.gz exists in filesystem
tcp_wrappers: /usr/man/man8/try-from.8.gz exists in filesystem
tcp_wrappers: /usr/sbin/safe_finger exists in filesystem
tcp_wrappers: /usr/sbin/tcpd exists in filesystem
tcp_wrappers: /usr/sbin/tcpdchk exists in filesystem
tcp_wrappers: /usr/sbin/tcpdmatch exists in filesystem
tcp_wrappers: /usr/sbin/try-from exists in filesystem
tcp_wrappers: /usr/share/licenses/tcp_wrappers/license.txt exists in filesystemerrors occurred, no packages were upgraded.
I can force installation by using 'pacman -Sf' but this doesn't seem optimal.
I read in a different thread that there might be some locale issues... I don't think that is the case here, I have run locale.gen twice from within the arch32 environment.
Can anyone spot the problem?
Thanks, Jeff
Offline
Is this on ANY package, or only gcc and tcp_wrappers?
Offline
hello,
This happens for every package I try to install... I just pasted from a single instance. I could not even install some fonts without using the force switch in pacman.
Offline
I followed that wiki article to set up a 32-bit chroot on my system and it worked perfectly without any modifications or variations. Anyway, I know this is a dumb question but it does need to be asked: Are you sure that you are actually in the chroot environment when those errors occur (so, they occur after a successful "chroot /path/to/chroot")?
Offline
Hello,
I understand, its probably something simple like that
Unfortunately its not that particular problem. I made sure that I'm in the chroot environment by putting a file in "/opt/arch32" from a normal (non chroot) terminal. Then I chroot to /opt/arch32, and I can see the file is now in "/".
Offline
Hello,
I understand, its probably something simple like that
Unfortunately its not that particular problem. I made sure that I'm in the chroot environment by putting a file in "/opt/arch32" from a normal (non chroot) terminal. Then I chroot to /opt/arch32, and I can see the file is now in "/".
Does the problem recur if you try to install a package that isn't installed outside of the chroot?
Offline
Hello,
Yes, it occurs with any package, including packages that do not exist in 64-bit form. for instance, I cannot install wine without using -f in pacman. This package is not available in Arch64, so there must be some problem my chroot.
It is okay, I think I can get by for now..the error does not seem to be causing a problem, and neither does using the -f option. I will not need to install very many things in the chroot...just wine and firefox I think.
--Jeff
Offline
try this:
$ sudo linux32 chroot /path/to/chroot
Offline
I get the same problem too. Tried using sudo, but i was logged in as root anyway. Doesn't change the problem :-/
Unknown Horizons - Open source real-time strategy game with the comfy Anno 1602 feeling!
Offline
Same problem here, exact same error. I did not have much time to troubleshoot after installing the chroot this afternoon, hopefully I'll figure it out tonight after I get off of work.
-nate
Offline
Same problem here, exact same error. I did not have much time to troubleshoot after installing the chroot this afternoon, hopefully I'll figure it out tonight after I get off of work.
-nate
OK, I fixed it on my machine. The problem was:
I used:
# "pacman --root /opt/arch32 -S base base-devel"
to install the original chroot....
This chroot was installed via 64bit Pacman. Now when we use the 32bit Pacman, it is trying to install package dependencies that already exist, but 32bit Pacman has no record of ever installing the packages -- hence the "exists in filesystem" error.
I fixed it by issuing the following inside the chroot:
# "pacman -Sf base base-devel"
This forces 32bit Pacman to reinstall the packages I installed with 64bit Pacman, creating the proper package database and (on my system) eliminated all of the errors.
-nate
Offline