[SOLVED] New architecture feature breaks 32bit chroot functionality.

Dheart · 2010-06-24 08:57:34

The new architecture feature in pacman completely breaks the 32bit chroot for x86_64 users functionality as in:

[root@lightbringer dheart]# dchroot -d "pacman -Su"
(arch32) pacman -Su 
:: Starting full system upgrade...
warning: wine: local (1.2rc2-1) is newer than extra (1.1.44-1)
error: failed to prepare transaction (package architecture is not valid)
:: package glibc-2.12-3-i686 does not have a valid architecture
:: package libtool-2.2.10-1-i686 does not have a valid architecture
:: package libxfont-1.4.2-1-i686 does not have a valid architecture
:: package pm-utils-1.4.0-1-i686 does not have a valid architecture
:: package poppler-0.14.0-1-i686 does not have a valid architecture
:: package pygobject-2.21.3-1-i686 does not have a valid architecture
dchroot: Child exited non-zero.
dchroot: Operation failed.

I can't even downgrade pacman, cause it's not the valid architecture ;dddd
Apparently the 32bit chroot is recognized as x86_64.
Bug report.

Last edited by Dheart (2010-06-24 13:24:57)

berbae · 2010-06-24 09:26:26

As the pacman of the chrooted arch32 installation uses the pacman.conf inside the chrooted system, you have to put :

Architecture = i686

in it, instead of the default

Architecture = auto

The auto option uses 'uname -m' to determine the architecture, and inside the chrooted system, that command still gives the machine hardware name which stays the same, ie x86_64 ; so it's necessary to force the i686 value for the architecture.

I don't think it's a bug. That seems logical to me.

Allan · 2010-06-24 09:28:03

linux32

Dheart · 2010-06-24 13:24:31

Thank you for the fast responses.
Changing /etc/pacman.conf architecture line to i686 fixes the problem.

MyParanoya · 2010-12-09 06:50:40

Guys i have the same problem and your solution doesn't help me!

in /etc/pacman.conf i have "Architecture=i686", in /etc/pacman.d/mirrorlist i have only 1 server;

so i do "pacman -Syu" and all is ok but then it writes "package [package_name] does not have a valid architecture"

i changed my architecture on auto and it worked but them i had problems with my net and so this shit has happened.

tomk · 2010-12-09 07:11:50

MyParanoya, this thread concerns 32-bit chroots on 64-bit systems. Is that what you are asking about? If not, please start a new thread.

Either way, you need to describe the problems with your net, and how they relate to the architecture issue.

MyParanoya · 2010-12-09 07:27:32

no thats not my problem but i thought u can help me in 1 word u r so clever.
ok, i'll start a new tread

Dieter@be · 2010-12-10 20:37:50

I personally would prefer not having the Architecture feature, I also got stung by this. but never any issues "in the old days"

Last edited by Dieter@be (2010-12-10 20:38:56)

Allan · 2010-12-10 23:22:24

You are free to disable it... The number of people whose arse it has saved by stopping them installing packages from the wrong architecture more than justifies its inclusion.

Arch Linux

#1 2010-06-24 08:57:34

[SOLVED] New architecture feature breaks 32bit chroot functionality.

#2 2010-06-24 09:26:26

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#3 2010-06-24 09:28:03

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#4 2010-06-24 13:24:31

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#5 2010-12-09 06:50:40

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#6 2010-12-09 07:11:50

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#7 2010-12-09 07:27:32

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#8 2010-12-10 20:37:50

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

#9 2010-12-10 23:22:24

Re: [SOLVED] New architecture feature breaks 32bit chroot functionality.

Board footer