Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#4935 - Two bugs in Archboot

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Sunday, 02 July 2006, 00:07 GMT
Task Type Bug Report
Category Installation
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I've noticed two oddities in archboot, the first in the installation program (/arch/setup) and the second in the base system:

1. During the installation of Arch Linux, packages' .install files don't seem to be running properly. udev's install script (which runs migrate-udev) doesn't get run, so migrate-udev has to be done manually; the proper files in /etc/skel never get copied to /root, since said files don't exist as far as the installer is concerned; the symbolic linking that perl's install script should do fails in a barrage of "directory does not exist" error messages. There seem to be some serious issues here.

2. The 'mv' command cannot be used, since the necessary binary doesn't exist. I have a feeling that this might have something to do with the first bug, but I'm not sure it could explain everything.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 06 July 2006, 06:39 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Sunday, 02 July 2006, 07:25 GMT
well i think i know the error source it uses probably the wrong shell /bin/sh
and not the real bash shell. i'll try to fix this soon.
Comment by Tobias Powalowski (tpowa) - Sunday, 02 July 2006, 08:20 GMT
does it work now?
Comment by name withheld (Gullible Jones) - Sunday, 02 July 2006, 11:52 GMT
Will see today... Thanks for tackling this one so fast.
Comment by name withheld (Gullible Jones) - Sunday, 02 July 2006, 14:40 GMT
Nope, doesn't work. The 'mv' command is there, but every single package install script still fails spectacularly - according to the installer, /bin/true doesn't exist, /sbin/migrate-udev doesn't exist, the Perl libraries can't be symlinked because they don't exist... This resembles a great deal the stuff I saw with Archbootstrap, so I'll throw off a wild guess - that the install scripts will only work properly when the installer is chrooted into the new system's root directory.
Comment by name withheld (Gullible Jones) - Monday, 03 July 2006, 13:13 GMT
Okay, it looks like the missing /bin/true thing could be separate from the other failures, I'm fairly sure it happens with the Arch floppy installer without anything else failing. Still worth looking into though.

The udev and perl scripts failing though... That is bad. It looks as though perl has to be reinstalled after the initial installation.

(Also,I should have realized before... The creation of the initial ramdisks is done by kernel26's install script, and that works fine. It might be only a few install scripts that are really screwing up. I'll compile a list.)
Comment by James Rayner (iphitus) - Monday, 03 July 2006, 13:40 GMT
it needs to explicitly install bash and coreutils and their deps before anything else so pre-reqs are availbable for install scripts to run.

then it can install all of the packages, including those two and their dependencies AGAIN, so that their install scripts are respected as well.

It's important that those packages are installed a second time, because their install scripts fail on the initial run.

James
Comment by name withheld (Gullible Jones) - Tuesday, 04 July 2006, 03:26 GMT
I take it that that's what the floppy/CD installer does?
Comment by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 13:33 GMT
ok tried it now myself, db and gcc warning are harmless.
udev doesn't work because of a missing / in front of sbin/migrat...
perl is the same, seems pacman changed it's behaviour in using --root parameter.
the / seems to be needed in the install files, i'll inform judd about it.
Not that packages are changed and it needs to be without /
Comment by Tobias Powalowski (tpowa) - Wednesday, 05 July 2006, 10:48 GMT
ok archboot contains a wrong chroot binary that fixes the error
Comment by Tobias Powalowski (tpowa) - Wednesday, 05 July 2006, 14:07 GMT
please try new archboot-0.2-4 it should fix your problems.
Comment by name withheld (Gullible Jones) - Wednesday, 05 July 2006, 23:13 GMT
Yup, it's fixed now. Thanks.

Loading...