Bug 3212 - mgaonline/update tries to perform update on a LiveCD
Summary: mgaonline/update tries to perform update on a LiveCD
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker minor
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2011-10-29 03:56 CEST by Kamil Rytarowski
Modified: 2012-04-07 22:23 CEST (History)
3 users (show)

See Also:
Source RPM: draklive
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Kamil Rytarowski 2011-10-29 03:56:58 CEST 
Description of problem:
When using Mageia LiveCD with preconfigured repositories it tries to update the system (install packages into RAM). This should be foolproof.

How reproducible:
Always

Steps to Reproduce:
1. Boot a LiveCD with Mageia
2. Have preconfigured repositories - package media
3. Wait a little bit
Kamil Rytarowski 2011-10-29 03:57:15 CEST

CC: (none) => krytarowski

Comment 1 Kamil Rytarowski 2011-11-20 21:51:55 CET 
Proposal fix
Put this one-liner somewhere:

use File::Slurp; read_file('/proc/cmdline')=~/cdrom/ and die "booted from cdrom, no updates.";
Manuel Hiebel 2011-11-20 21:56:26 CET

Keywords: (none) => PATCH

Comment 2 Thierry Vignaud 2011-12-10 05:55:26 CET 
Should actually be disabled by draklive like other stuff

CC: (none) => thierry.vignaud
Assignee: bugsquad => mageia
Source RPM: mgaonline-2.77.29-1.mga1 => draklive

Comment 3 Marja Van Waes 2012-03-14 21:53:48 CET 
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED

Setting version to cauldron because an existing live CD can't get fixed

CC: (none) => marja11
Version: 1 => Cauldron

Thierry Vignaud 2012-03-15 06:27:45 CET

Priority: Normal => release_blocker

Comment 4 Manuel Hiebel 2012-04-07 22:23:51 CEST 
autostart is set to false in /home/live/.Mgaonline/mgaonline, so I guess it's fixed (pre-beta3)

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.