Bug 26747 - After Install from ISO on hardrive the repositories from the ISO point to wrong directory
Summary: After Install from ISO on hardrive the repositories from the ISO point to wro...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-08 23:21 CEST by katnatek
Modified: 2021-09-07 14:09 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description katnatek 2020-06-08 23:21:39 CEST
Description of problem:

If you use the network images to install from a ISO of a Classic DVD image in a Hard Disk after a successfully installation the repositories of the ISO points to /tmp/image/media in urpmi.cfg while the ISO  is on /mnt/Mageia-<version>-<arch> in fstab, no symlink is created by the installation process so urpmi and rpmdrake can't use the repositories of the ISO

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Boot from network image
2. Select Hard Drive as source
3. Select the Hard Drive and/or partition where you have the DVD ISO
4. Select folder where the ISOs is stored (if is necessary)
5. Select the DVD ISO
6. Pass for the install process (i only use ISOs repositories)
7. After boot in the installed system check urpmi.cfg and fstab
8. You'll see the ISO repositories don't point to usable path
Comment 1 Lewis Smith 2020-06-09 21:08:03 CEST
Thank you for the report; it is strange that this has gone unnoticed for M7 up to now. [If it has already been reported, I cannot find that].

> 7. After boot in the installed system check urpmi.cfg and fstab
> 8. You'll see the ISO repositories don't point to usable path
Could you please post what these two files do actually look like.

In anticipation of which, assigning to MageiaTools, CC ISO team.

CC: (none) => isobuild
Assignee: bugsquad => mageiatools

Comment 2 katnatek 2020-06-09 23:10:55 CEST
(In reply to Lewis Smith from comment #1)
> Thank you for the report; it is strange that this has gone unnoticed for M7
> up to now. [If it has already been reported, I cannot find that].
> 
> > 7. After boot in the installed system check urpmi.cfg and fstab
> > 8. You'll see the ISO repositories don't point to usable path
> Could you please post what these two files do actually look like.
> 
> In anticipation of which, assigning to MageiaTools, CC ISO team.

Your welcome, i don't think is useful in their current state as long as i made changes to both files.

By memory in urpmi.cfg the repositories of the DVD ISO file point to a correspondent subfolder of /tmp/image where i suppose the ISO is mounted in the install process

And the fstab the ISO /mnt/hd/<isos-folder>/Mageia-<version>-<arch>.iso is mounted on /mnt/Mageia-<version>-<arch> (and with noauto option)

So when you add remote repositories when install a rpm of the release media that are on the ISO, instead of take from the ISO, the rpm is downloaded from the remote version.

I think this is the more unusual case of installation so the issue not bite to anyone, but recently i have to made a clean install of my system and dump the network-nonfree image to USB key to make the installation described.
Comment 3 Aurelien Oudelet 2020-09-20 17:45:02 CEST
Hi,
This bug is against our Installer DrakX.

@Developers/Packagers: Feel free to reassign to correct person.
Also, if you are working on this, please change the status of this bug to "Assigned".
Feel free to close this if already fixed.

@All
Thanks making DrakX even better.
Comment 4 Marja Van Waes 2021-09-07 14:09:52 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

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


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