Bug 9824 - NFS installation: wrong address of the local repository.
Summary: NFS installation: wrong address of the local repository.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-04-22 14:54 CEST by Jomar Francisco
Modified: 2014-12-02 16:49 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jomar Francisco 2013-04-22 14:54:13 CEST
Description of problem: When Mageia is installed via the NFS repository address "local" in "Configuring media" is wrong.


Version-Release number of selected component (if applicable): Mageia 2 e Mageia 3


How reproducible: 
Example:
Wrong -> /mnt/nfs/media/core
Correct -> /mnt/nfs/i586/media/core


Steps to Reproduce:In an NFS server, share a directory containing the installation DVD Mageia. On another computer give the boot CD network installation. After installation, run the "Mageia Control Center", open the "Setting Media" and edit the "Local - core media". Is missing 'i586 /'.

Reproducible: 

Steps to Reproduce:
David Walser 2013-04-22 22:59:50 CEST

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

Comment 1 Thierry Vignaud 2013-04-23 01:56:25 CEST
Please attach your /root/drakx/report.bug.xz.
I think you used a NFS path that didn't included the arch, didn't you?
Samuel Verschelde 2013-08-27 16:16:16 CEST

Keywords: (none) => NEEDINFO
CC: (none) => stormi

Comment 2 David Walser 2014-03-03 20:59:26 CET
This bug also exists for hard disk installations.  It just puts the mount point of the partition it installed from with /media/core appended in urpmi.cfg, and leaves out the entire path to the repository on that partition.
Comment 3 Dick Gevers 2014-12-02 16:49:06 CET
Missing reply since 19 months. Closing as OLD.

Please note pre-5 installers will not be fixed. You may reopen if the same occurs afain with current installer (5beta1 or higher). In such case please change the relevant headers & attach the report.bug.xz. Thanks.

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


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