Bug 215764 – GUI Installer fails on copying pam-0.99.9.0 to chroot enviroment

• Status: RESOLVED FIXED
• Product: Gentoo Release Media

[Description Rob Wilkinson 2008-04-01 19:49:32 UTC]

During install using GUI installer failed during extracting stage tarball pam-0.99.9.0 failed to copy to chroot

Reproducible: Always

Steps to Reproduce:
1.Run the gui instaler from x86 beta
2.
3.

Actual Results:  

GLI: April 01 2008 20:08:31 - Gentoo Linux Installer version 0.6.3
GLI: April 01 2008 20:09:39 - Mounted mountpoint: /
GLI: April 01 2008 20:09:39 - Mounted mountpoint: /boot
GLI: April 01 2008 20:09:39 - Mounted mountpoint: /home
GLI: April 01 2008 20:09:39 - Created mountpoint /usr/portage
GLI: April 01 2008 20:09:39 - Mounted mountpoint: /usr/portage
GLI: April 01 2008 20:18:25 - Exception received during 'Unpack stage tarball': CopyPackageToChrootError :FATAL: copy_pkg_to_chroot: Could not execute preinst for sys-libs/pam-0.99.9.0
GLI: April 01 2008 20:18:25 - Traceback (most recent call last):
GLI: April 01 2008 20:18:25 - File "/opt/installer/GLIClientController.py", line 122, in run
    func()
GLI: April 01 2008 20:18:25 - File "/opt/installer/GLIArchitectureTemplate.py", line 414, in unpack_stage_tarball
    self._portage.copy_pkg_to_chroot(pkg, True, ignore_missing=True)
GLI: April 01 2008 20:18:25 - File "/opt/installer/GLIPortage.py", line 227, in copy_pkg_to_chroot
    raise GLIException("CopyPackageToChrootError", 'fatal', 'copy_pkg_to_chroot', "Could not execute preinst for " + package)
GLI: April 01 2008 20:18:25 - GLIException: CopyPackageToChrootError :FATAL: copy_pkg_to_chroot: Could not execute preinst for sys-libs/pam-0.99.9.0



Expected Results:  
installed in usual manner

[Comment 1 Andrew Gaffney (RETIRED) 2008-04-01 19:57:46 UTC]

Please attach /tmp/compile_output.log

[Comment 2 Rob Wilkinson 2008-04-01 20:28:02 UTC]

Created attachment 147999 [details]
/tmp/compile_output.log

[Comment 3 Andrew Gaffney (RETIRED) 2008-04-04 12:04:16 UTC]

This one is just weird. The pam ebuild is acting like it's an upgrade. AFAIK, nobody else has reported this problem.

[Comment 4 Andrew Gaffney (RETIRED) 2008-04-04 14:20:57 UTC]

Did you have existing contents on these partitions before installing? It sounds like this would happen if you tried to install over an older install

[Comment 5 Rob Wilkinson 2008-04-04 16:30:55 UTC]

(In reply to comment #4)
> Did you have existing contents on these partitions before installing? It sounds
> like this would happen if you tried to install over an older install
> 

I did use existing partitions yes, from an arch install. However i did also run gparted first and formatted the partitions before commencing install. I will give it another go if you like but delete and redo the partitions first, i will report back with results, Thanks Andrew

[Comment 6 Andrew Gaffney (RETIRED) 2008-04-04 16:33:45 UTC]

Yes, please make absolutely sure that you format the partitions. The easiest way is to just delete and recreate them in the partitioning screen of the installer.

[Comment 7 Rob Wilkinson 2008-04-04 18:09:32 UTC]

(In reply to comment #6)
> Yes, please make absolutely sure that you format the partitions. The easiest
> way is to just delete and recreate them in the partitioning screen of the
> installer.
> 

Hi Andrew, that fixed the issue, so the 1st time I ran the installer I could not of deleted the partitions as I first thought. Thanks for the assist, I will pay more attention next time to my own log files

[Comment 8 Andrew Gaffney (RETIRED) 2008-04-05 15:27:24 UTC]

*** Bug 216313 has been marked as a duplicate of this bug. ***