Difference between revisions of "Talk:Migrating between architectures"

From ArchWiki
Jump to: navigation, search
(I got a bunch of errors when upgrading to 64bit using 'method 2'...)
 
(error installing lib32-glibc while 32 bit glibc is still installed)
Line 1: Line 1:
 +
== Couldn't install lib32-glibc ==
 +
 +
The article says "Alternatively, if migrating to 64 bits, now is the time to install the lib32-glibc fallback".  But when I tried to install lib32-glibc I got errors about conflicting files.  I didn't keep a record of the exact error message, but glibc and lib32-glibc both have these 2 files in them, so I guess that was the cause of the error:
 +
 +
/lib/ld-linux.so.2
 +
/usr/include/gnu/stubs-32.h
 +
 +
See http://www.archlinux.org/packages/core/i686/glibc/files/ and http://www.archlinux.org/packages/multilib/x86_64/lib32-glibc/files/ for the file lists - the article suggests installing lib32-glibc before upgrading glibc. --[[User:Dooglus|Dooglus]] 20:40, 9 November 2011 (EST)
 +
 +
== Errors Upgrading pacman, etc. ==
 +
 
I followed the instructions for method two (installing from a running system) to upgrade from 32 bit to 64 bit.  It went well until it came to reinstalling pacman and friends, then I saw a bunch of errors:
 
I followed the instructions for method two (installing from a running system) to upgrade from 32 bit to 64 bit.  It went well until it came to reinstalling pacman and friends, then I saw a bunch of errors:
  

Revision as of 01:40, 10 November 2011

Couldn't install lib32-glibc

The article says "Alternatively, if migrating to 64 bits, now is the time to install the lib32-glibc fallback". But when I tried to install lib32-glibc I got errors about conflicting files. I didn't keep a record of the exact error message, but glibc and lib32-glibc both have these 2 files in them, so I guess that was the cause of the error:

/lib/ld-linux.so.2
/usr/include/gnu/stubs-32.h

See http://www.archlinux.org/packages/core/i686/glibc/files/ and http://www.archlinux.org/packages/multilib/x86_64/lib32-glibc/files/ for the file lists - the article suggests installing lib32-glibc before upgrading glibc. --Dooglus 20:40, 9 November 2011 (EST)

Errors Upgrading pacman, etc.

I followed the instructions for method two (installing from a running system) to upgrade from 32 bit to 64 bit. It went well until it came to reinstalling pacman and friends, then I saw a bunch of errors:

[root@chris chris]# pacman -S pacman glibc libfetch libarchive openssl acl attr \
   xz-utils bzip2 zlib readline bash ncurses expat
warning: pacman-3.5.4-4 is up to date -- reinstalling
warning: glibc-2.14.1-1 is up to date -- reinstalling
warning: libfetch-2.33-3 is up to date -- reinstalling
warning: libarchive-2.8.5-2 is up to date -- reinstalling
warning: openssl-1.0.0.e-1 is up to date -- reinstalling
warning: acl-2.2.51-1 is up to date -- reinstalling
warning: attr-2.4.46-1 is up to date -- reinstalling
warning: xz-5.0.3-1 is up to date -- reinstalling
warning: bzip2-1.0.6-3 is up to date -- reinstalling
warning: zlib-1.2.5-4 is up to date -- reinstalling
warning: readline-6.2.001-3 is up to date -- reinstalling
warning: bash-4.2.010-2 is up to date -- reinstalling
warning: ncurses-5.9-2 is up to date -- reinstalling
warning: expat-2.0.1-7 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
 
Targets (14): glibc-2.14.1-1  ncurses-5.9-2  readline-6.2.001-3  bash-4.2.010-2 \
   zlib-1.2.5-4  bzip2-1.0.6-3  xz-5.0.3-1  attr-2.4.46-1  acl-2.2.51-1 \
   openssl-1.0.0.e-1  expat-2.0.1-7  libarchive-2.8.5-2  libfetch-2.33-3 \
   pacman-3.5.4-4
 
Total Download Size:    0.00 MB
Total Installed Size:   67.17 MB

Proceed with installation? [Y/n] y
call to execv failed (No such file or directory)
error: command failed to execute correctly
call to execv failed (No such file or directory)
error: command failed to execute correctly
error: command failed to execute correctly
warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew
[root@chris chris]# 

I don't know if they are 'expected' errors, or if they're a problem. I carried on with the

# pacman -S $(pacman -Qq)

command, which also produced some errors. I won't paste the whole output, since it is rather large, but some of the more serious looking errors were:

Proceed with installation? [Y/n] y
/tmp/alpm_nhTnAm/.INSTALL: line 6: sbin/init: No such file or directory
usr/sbin/locale-gen: line 16: /bin/rm: No such file or directory
Generating locales...
usr/sbin/locale-gen: line 33: /bin/sed: No such file or directory
  .UTF-8usr/sbin/locale-gen: line 35: /bin/sed: No such file or directory
...usr/sbin/locale-gen: line 38: /bin/sed: No such file or directory
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
/tmp/alpm_pnGmoW/.INSTALL: line 16: bin/grep: No such file or directory
groupadd: group 'optical' already exists

After that I ran both commands again, in the same order, and this time they both completed without errors, and my system appears to be fine as far as I can tell.

I don't know if the errors produced the first time through needed fixing, or if my solution (re-running both commands) is a good solution, but maybe someone who knows could update the article accordingly, either saying not to worry about the errors, or saying what how to fix them. --Dooglus 20:18, 9 November 2011 (EST)