| Summary: | Upgrading Mandriva 2010.1 to Mageia breaks on python 2.7 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Priscus <wizzard> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | alien, davidwhodgins, ennael1, misc, pterjan, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | urpmi-6.40-7.mga1.src.rpm | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 56 | ||
|
Description
Priscus
2011-03-16 21:07:18 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 (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 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 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. (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. Reporter can you please test again and confirm all is ok now? 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. Closing that bug then Forgot to close the bug. Done now. Hope nobody else has problems anymore... Status:
NEW =>
RESOLVED |