Bug 2578 - x86_64 HTTP install needs arch-specific directory
Summary: x86_64 HTTP install needs arch-specific directory
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-31 16:54 CEST by Frank Griffin
Modified: 2012-01-23 15:18 CET (History)
2 users (show)

See Also:
Source RPM: drakx-installer
CVE:
Status comment:


Attachments

Description Frank Griffin 2011-08-31 16:54:46 CEST
A 64-bit HTTP install which is pointed at the cauldron directory fails immediately with the message:

Error: couldn't get file
(/mnt/cauldron/install/stage2/mdkinst.sqfs)

It appears that the HTTP install is not smart enough to realize that since it is running in a 64-bit boot.iso, it should look for this file in 

/mnt/cauldron/x86_64/install/stage2/mdkinst.sqfs

NFS and Hard-disk installs do this correctly, and so should HTTP.

Note that if you give the HTTP directory as /mnt/cauldron/x86_64, everything works fine.  This implies that later in the install, the i586 path is being set incorrectly to compensate for the error in the original path.
Manuel Hiebel 2011-08-31 17:08:20 CEST

Source RPM: (none) => drakx-installer

Comment 1 Marja Van Waes 2011-11-10 07:46:59 CET
IIUC, at the time when you filed this report you were not supposed to install cauldron, but to install Mga1 and then take the steps here http://www.mageia.org/wiki/doku.php?id=cauldron

@ Thierry
Did I misunderstand?

CC: (none) => marja11, thierry.vignaud

Comment 2 Marja Van Waes 2012-01-01 17:59:03 CET
No reply, so I guess this was user error. Closing as invalid.

Feel free to reopen if you think I'm wrong to do so, and explain why you think that.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 3 Thierry Vignaud 2012-01-23 14:15:32 CET
Yeah the HTTP path never got that kind of intelligence.
Only the disk ones (including NFS) got that over the years.
Fixed in git anyway (for HTTP).
Should be in next drakx-installer-binaries tomorrow.

Resolution: INVALID => FIXED

Comment 4 Frank Griffin 2012-01-23 15:18:08 CET
Thanks !

Sorry, Marja, somehow I missed the previous posts on this.

Note You need to log in before you can comment on or make changes to this bug.