Bug 404 - Upgrading Mandriva 2010.1 to Mageia breaks on python 2.7
Summary: Upgrading Mandriva 2010.1 to Mageia breaks on python 2.7
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 56
  Show dependency treegraph
 
Reported: 2011-03-16 21:07 CET by Priscus
Modified: 2011-04-27 19:34 CEST (History)
6 users (show)

See Also:
Source RPM: urpmi-6.40-7.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Priscus 2011-03-16 21:07:18 CET
Description of problem:
Some packages available in Mandriva 2010.1 depend on (python < 2.7), for example python-pypdf or python-django. 
The upgrade stops when urpmi encounters this: no python or python-dependant package can be upgraded at all (that makes quite a lot of them, including infrastructure packages). 
Furthermore, the whole system upgrade stops, even if other packages could still be upgraded without trouble. 

It is possible to solve the conflict from the command line (live upgrade), but the DVD upgrade does not warn of the extent of the problem, and does not give the means to either abort before the upgrade has begun or remove the conflicting packages. 


Version-Release number of selected component (if applicable):
DVD alpha 2
urpmi 6.40-7


How reproducible:
Each and every time one tries to upgrade a distribution with a package depending on (python < 2.7)


Steps to Reproduce:
1. start from a Mandriva with a package dependiong on (python < 2.7), like pypdf
2. Try to upgrade it from either the DVD or a mirror
3. Get stuck (with little explanations and no control from the DVD)


Possible improvements
Improve the ordering of package upgrades
Detect these conflicts before actually starting the upgrade, and give the user the option to abort or remove (crucial for the DVD)


Reproducible: 

Steps to Reproduce:
Comment 1 AL13N 2011-03-18 18:19:12 CET
confirmed on upgrading mandriva 2010.1 x86_64 PWP to mageia 1 alpha 2 with x86_64 DVD.

but seems not only related to python, also perl-base stuff, and x11 related stuff seems also apparent. also file conflicts (documentation) from stuff that has been moved to other rpms.

I can click on OK, and it seems to just stop upgrading, but proceeding with configuration step...

CC: (none) => maarten.vanraes
Blocks: (none) => 56

Comment 2 Ahmad Samir 2011-03-19 19:22:46 CET
(In reply to comment #0)
> Description of problem:
> Some packages available in Mandriva 2010.1 depend on (python < 2.7), for
> example python-pypdf or python-django. 
> The upgrade stops when urpmi encounters this: no python or python-dependant
> package can be upgraded at all (that makes quite a lot of them, including
> infrastructure packages). 
> Furthermore, the whole system upgrade stops, even if other packages could still
> be upgraded without trouble. 
> 

That's not what I saw, urpmi asks the user about uninstalling those python packages, then proceeds with the upgrade as expected. A snippet from an upgrade-via-urpmi log:

getting exclusive lock on rpm
In order to satisfy the 'pinentry-gui' dependency, one of the following packages is needed:
 1- pinentry-qt4-0.8.1-2.mga1.x86_64: QT4 interface of pinentry (to install)
 2- pinentry-gtk2-0.8.1-2.mga1.x86_64: GTK+ interface of pinentry (to install)
What is your choice? (1-2) The following packages have to be removed for others to be upgraded:
gnome-shell-2.29.1-8.1mdv2010.1.x86_64
 (due to missing libgirepository-1.0.so.0()(64bit),
  due to missing mutter)
lib64exo-0.3_0-0.3.106-2mdv2010.1.x86_64
 (due to unsatisfied exo == 0.3.106-2mdv2010.1)
lib64girepository1.0_0-0.6.10-4mdv2010.1.x86_64
 (due to conflicts with gobject-introspection-0.10.4-3.mga1.x86_64)
lib64thunar1_2-1.0.1-7mdv2010.1.x86_64
 (due to missing libexo-hal-0.3.so.0()(64bit),
  due to missing libexo-0.3.so.0()(64bit))
mandriva-lxde-config-Free-0.5-2mdv2010.1.noarch
 (due to missing mandriva-release-Free)
mutter-2.29.1-4mdv2010.1.x86_64
 (due to missing libgirepository-1.0.so.0()(64bit))
python-pypdf-1.12-1mdv2010.0.noarch
 (due to unsatisfied python < 2.7)
xfce4-places-plugin-1.2.0-2mdv2010.1.x86_64
 (due to missing libexo-0.3.so.0()(64bit),
  due to missing libthunar-vfs-1.so.2()(64bit))
xfce4-volstatus-icon-0.1.0-13mdv2010.1.x86_64
 (due to missing libexo-hal-0.3.so.0()(64bit)) (y/N) 

To satisfy dependencies, the following packages are going to be installed:
   Package                        Version      Release       Arch   
(medium "Core Release")
  2mandvd                        1.5.3        1.mga1        x86_64  
  Default-kde4-config            1            0.15.mga1     noarch  
  GConf2                         2.32.0       1.mga1        x86_64  
  GConf2-sanity-check            2.32.0       1.mga1        x86_64  
  ORBit2                         2.14.19      1.mga1        x86_64  

it then proceeded to upgrade the system. The same thing happens automatically when using --auto, but without interaction from the user, i.e. urpmi proceeds with uninstalling those packages and upgrading the rest of the system.

python-django is already available in the Mageia repos and on the DVD, we'll need the report.bug.gz to see why did the upgrade stop.

Note that the DVD will never contain every package in the repos, so some packages are bound to be removed in situations like this (unless the user adds online sources during the upgrade).

CC: (none) => pterjan, thierry.vignaud

Comment 3 Dave Hodgins 2011-04-07 22:25:24 CEST
I encountered this in the install of beta 1, causing the second urpmi transaction to
fail.  From the install log ...

Installation failed:
	python-django is needed by (installed) python-django-tagging-0.3.1-1mdv2010.1.noarch

CC: (none) => davidwhodgins

Anne Nicolas 2011-04-19 12:17:20 CEST

CC: (none) => ennael1, misc

Comment 4 Michael Scherer 2011-04-19 14:30:13 CEST
The problem is not a python problem, but the fact that some packages were not imported or not rebuilt since python 2.7 upgrade. 

So we need to import python-django-tagging, python-pypdf.
Comment 5 Ahmad Samir 2011-04-20 19:30:00 CEST
(In reply to comment #4)
> The problem is not a python problem, but the fact that some packages were not
> imported or not rebuilt since python 2.7 upgrade. 
> 
> So we need to import python-django-tagging, python-pypdf.

Both packages are in the repos for some time now.
Comment 6 Anne Nicolas 2011-04-25 20:27:39 CEST
Reporter can you please test again and confirm all is ok now?
Comment 7 Priscus 2011-04-26 21:00:53 CEST
Tested today: it works beautifully with a live update. 

I haven't tried the DVD only test, as an update takes quite some time on my rather slow machine. I will if you think it necessary, though: just let me know.
Comment 8 Anne Nicolas 2011-04-26 21:01:52 CEST
Closing that bug then
Comment 9 Priscus 2011-04-27 19:34:44 CEST
Forgot to close the bug.
Done now. 
Hope nobody else has problems anymore...

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


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