Bug 5004 - 2_b2, option to upgrade from Mandriva should be blocked
Summary: 2_b2, option to upgrade from Mandriva should be blocked
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-18 09:56 CET by Marja Van Waes
Modified: 2012-04-23 13:03 CEST (History)
11 users (show)

See Also:
Source RPM: draklive-install, drakx-installer-stage2
CVE:
Status comment:


Attachments

Description Marja Van Waes 2012-03-18 09:56:56 CET
+++ This bug was initially created as a clone of Bug #2629 +++

do whatever is needed to upgrade from mdv2011:
- rebuild rpm db
- downgrade rpm5 -> rpm.org
- ...

No time to do this was found, so this happens now:

(Reported by Jürgen PreuÃ)
https://bugs.mageia.org/show_bug.cgi?id=2629#c7

Hallo community,

without reading this snippets before I tried it with actual Mageia2beta2.

1. Replacement of urpmi repos of mdv2011 with mga2 ones on running mdv.

2. Upgrade with Mga2b2 DVD

Top 1:

There are some starting dependencies missing. Especially around rpm-tools. They
are forcing a downgrade from version 5.3 to 4.9.
I won't risk it atm.

Top 2:

After booting from DVD it detects a partition with mdv 2011.0 and asks for
actualisation. Next button leads to keyboard selection. ok.
Again next-button leads to selection of package groups and detects "core
media".

The next "next" results in message "Error: 9" with ok-button. Explanation is
"Can't call method" traverse_tag" on an undefined value."
"Ok" leads back to selection for further media and then loops to message
"Error: 9".

I was interested and went down to shell (CTRL-ALT-F2).

"rpm --version" gave 5.3.12; "which rpm" gave /mnt/bin/rpm.
"rpm -r /mnt/var/lib/rpm -qa" resulted in "dbiOpen: Assertion" error.

Interested in crossing I tried to query rpm-db of mga2 in mdv2011 and vice
versa. In mdv was no problem to "rpm -qa" with mga2 database. From mga2 it was
not possible to read mdv's repository.
Possibly I'd to delete __db.* files and rebuild them on foreign system. 

Result:
Not usable today. Option to upgrade from MDV2011 should be blocked after
detection of OS.
Marja Van Waes 2012-03-18 09:57:47 CET

Priority: Low => Normal
CC: (none) => mageia, tmb

Comment 1 Marja Van Waes 2012-03-18 10:05:31 CET
I'm not sure about the "Depends on" field, because, if that bug is solved, this one doesn't need to be solved and the other way around. Usually, when the "Depends on" field is used, it means the other bug needs to be solved first before this one can be solved.

Maybe in this case I should set this bug to depend on and to block the other one? That would make it clear there is an unusual relationship between the bugs.

CC: (none) => manuel
Source RPM: (none) => draklive-install, drakx-installer-stage2

Marja Van Waes 2012-03-18 10:09:29 CET

Assignee: bugsquad => thierry.vignaud

Comment 2 Marja Van Waes 2012-03-18 11:09:14 CET
Changed summary, because upgrade to 2 from Mdv 2010.2 isn't guaranteed, either, so there are no Mandriva versions left to upgrade from.

Summary: 2_b2, option to upgrade from mdv2011 should be blocked => 2_b2, option to upgrade from Mandriva should be blocked

Comment 3 Thierry Vignaud 2012-03-18 11:35:18 CET
I disagree, that was one of our goal.
What's more since we favor our packages in the installer, this should work pretty well
2011.x is special regarding rpm/rpmdb
Comment 4 Sander Lepik 2012-03-18 11:38:41 CET
Upgrade from mdv2011 hasn't been our goal. We do not support it.
Comment 5 Marja Van Waes 2012-03-18 12:11:49 CET
(In reply to comment #3)
> I disagree, that was one of our goal.
> What's more since we favor our packages in the installer, this should work
> pretty well
> 2011.x is special regarding rpm/rpmdb

Hi Thierry,

You only disgree to my statement that upgrade from Mdv 2010.2 to Mageia 2 isn't supported, correct?

I read that in a mail to dev-ml from someone who should know, but I admit that that could be his personal opinion instead of a decision that was taken.
Comment 6 Jürgen Preuà 2012-03-18 22:52:42 CET
(In reply to comment #2)
> Changed summary, because upgrade to 2 from Mdv 2010.2 isn't guaranteed, either,
> so there are no Mandriva versions left to upgrade from.

Hi Marja,

"guaranteed" is a buzzword of professionals. [I'm|We are] amateur(s) in this case, getting honnor and no money ;^)

As I read before, there was the goal to upgrade/replace on basis of mdv2010. Actually there is no real distinction between 2010.1 and 2010.2, if they are patched to latest. How deep migration assistance is going, is another part (may be a milestone definition/discussion).

I'll try some experiments with Top1 of my posting and will report about it.

Thanks for your assistance,

Juergen
Comment 7 Marja Van Waes 2012-03-19 06:51:53 CET
Hi Jürgen,

What I should have written is, that AFAIK upgrading to Mga2 from Mdv2010 is not being tested.

I'll cc QA, they know better than me.

Regards,
Marja

CC: (none) => qa-bugs

Comment 8 Anne Nicolas 2012-03-19 08:49:58 CET
Upgrade from 2010.2 to Mageia 1 is guaranted but not 2010.2 to Mageia 2. It will work for sure but may be bugged in some parts. Anyway we will not guarantee it, no QA tests on this.

CC: (none) => ennael1

Comment 9 Dave Hodgins 2012-03-19 18:40:49 CET
My understanding is that upgrading is only supposed to be supported
going from Mandriva 2010.2 to Mageia 1, or from Mageia 1 to Mageia 2.

In all other cases, a clean install should be done.

Mageia 2 should only be offering an upgrade from Mageia 1.

CC: (none) => davidwhodgins

Comment 10 Samuel Verschelde 2012-03-19 21:12:04 CET
I agree with Dave : it would be better if the installer would refuse to upgrade from anything but Mageia 1. Those who want to risk their installation by another type of upgrade can still use urpmi.

CC: (none) => stormi

Comment 11 Thierry Vignaud 2012-04-23 13:01:19 CEST
"Not offering to upgrade" doesn't depends on "making upgrading rpm5 works"...

Depends on: 2629 => (none)

Comment 12 Thierry Vignaud 2012-04-23 13:03:43 CEST
Fixed in git

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


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