| Summary: | CLI upgrade Mageia1 to Mageia2 | ||
|---|---|---|---|
| Product: | Websites | Reporter: | Ken Bergen <kbergen> |
| Component: | www.mageia.org | Assignee: | Atelier Team <atelier-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, rdalverny |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | console output | ||
|
Description
Ken Bergen
2012-05-28 00:09:24 CEST
For reference, http://www.mageia.org/en/1/migrate/ should be copied/updated for mga2 Or is there some other documentation you are referring to? CC:
(none) =>
doktor5000 https://wiki.mageia.org/en/Mageia_2_Release_Notes#Upgrading_from_Mageia_1 But I see that that's in the wiki and I can update that myself. Of course when http://www.mageia.org/en/1/migrate/ is copied/updated to /2/upgrade/ the advice to run the command twice should be included there. this seems not a but for me, for 2. this is normal since urpmi install first the needed package for urpmi for 3. have you log ? I'm pretty there was a fail (In reply to comment #3) > this seems not a but for me, > > for 2. this is normal since urpmi install first the needed package for urpmi > > for 3. have you log ? I'm pretty there was a fail For 2, As I said 316 packages were installed then urpmi restarted saying it was installing 2659 packages. It only installed 1419 of those and ended without an error message. For 3. Unfortunately I have no logs as I re-installed Mageia1. I'll do a clean install of 1 on a new disc then upgrade to 2 in the next days and attach any error logs I find here. Created attachment 2421 [details]
console output
New install and test.
Manuel you where correct in that there were lots of failures reported at the end of the first run.
However all of the packages that failed in the first run installed in the second run.
Here's the console output.
The upgrade procedure is described in the wiki. Should this bug be closed or? CC:
(none) =>
rdalverny (In reply to comment #6) > The upgrade procedure is described in the wiki. Should this bug be closed or? I added the advice to run the command twice to the wiki and as no one else has reported a problem it might as well by closed for now.
Romain d'Alverny
2012-06-13 01:08:19 CEST
Status:
NEW =>
RESOLVED
Marja Van Waes
2012-06-23 19:19:23 CEST
Attachment 2421 mime type:
application/octet-stream =>
text/plain |