Bug 6148 - Online upgrades fail because mgaonline does not enable necessary Non-Free repository
Summary: Online upgrades fail because mgaonline does not enable necessary Non-Free rep...
Status: RESOLVED DUPLICATE of bug 6061
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 12:41 CEST by Derek Jennings
Modified: 2012-05-29 12:50 CEST (History)
0 users

See Also:
Source RPM: mgaonline-2.77.33-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Derek Jennings 2012-05-29 12:41:47 CEST
Description of problem:

It is clear from reports in the forum that some Mga1 users have had difficulty doing an online upgrade to Mga2 because they have hardware requiring non-free drivers/firmware, and mgaapplet-upgrade-helper only enables Core Repositories. So when the upgrade has finished the user is left without working hardware.


Since the user has already indicated their preference for using Non-Free or Tainted repositories I believe the correct action for mgaapplet-upgrade-helper should be to enable those repositories if they were previously enabled.

Alternatively the user should be asked if they want those repositories enabled before the upgrade starts.



This bug applies to Cauldron, Mageia 2, and Mageia 1 


Upgrading using the DVD poses similar problems, but I suppose that should be another bug report.



Version-Release number of selected component (if applicable):
mgaonline-2.77.33-1.mga2


Steps to Reproduce:
1. set up a vbox with Mageia1 and all updates
2. When prompted by mgaapplet start an online upgrade
3.  Observe only Core repositories are enabled in /etc/urpmi/urpmi.cfg
Comment 1 Manuel Hiebel 2012-05-29 12:50:08 CEST
already reported

*** This bug has been marked as a duplicate of bug 6061 ***

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


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