[SOLVED] Mageia 2 package with Mageia 3 dependents

[eldiener]

After upgrading successfully from Mageia 2 to Mageia 3 I went about removing all leftover Mageia 2 packages. I found a single package, which is a Mageia 2 package, which amazingly has Mageia 3 dependents. This package is 'python-dbus version 0.84.0 release 1.mga2 arch x86_64'. It's Mageia3 dependents are:

- ibus-1.5.1-2.mga3.x86_64
- ibus-gtk-1.5.1-2.mga3.x86_64
- ibus-gtk3-1.5.1-2.mga3.x86_64
- plasma-applet-kimpanel-backend-ibus-4.10.2-1.mga3.x86_64
- python-slip-dbus-0.2.20-3.mga3.noarch
- sectool-0.9.5-7.mga3.x86_64
- system-config-printer-1.3.12-6.mga3.x86_64
- telepathy-butterfly-0.5.15-4.mga3.noarch

This is strange. Did the Mageia 3 developers forget to upgrade this package to a Mageia 3 version ?

All other Mageia 2 packages could be removed without affecting any Mageia 3 software installed.

[GlennsPref]

Hi, It's not that strange considering previous updates to mga2, progress to mga3, etcetera. (I don't think it matters, try cauldron!)

Updates may be available to fix that version number.

Removing packages by ver (mga2) is probably not that safe, but urpme --auto-orphans may be good and sometimes may not.

When doing this, I alway get a copy of the list and meticulously chop away at it. Carefully.

[eldiener]

Actually I found that ' urpme --auto-orphans' is not that good as it sometimes removes packages I want to keep. I was careful removing the mga2 packages so that no mga3 packages were affected. I will look forward to an update for python-dbus for mga3 which will enable me to delete the mga2 package. But if it does not happen I will not worry just as long as any of its dependents work properly with it.

[ghmitch]

You cannot remove it because in needs to be upgraded, not removed. The correct version is "python-dbus-1.1.1-2.mga3". You SHOULD be able to upgrade it from MCC as somehow it seems to have gotten missed on the initial upgrade process. This CAN happen sometimes and it is always a good idea when you find mga2 packages, to make sure there are not mga3 packages by the same name to upgrade to. This requires setting up MCC to pull packages off of a mirror rather than using the install disk as sometimes packages may get left off the install disk.

[jkerr82508]

After an upgrade it is advisable, after setting up the new online repo's, to run as root:

Code: Select all

urpmi --auto-update

This should update any remaining "old" packages.

It is important to be aware that there are .mga1 and .mga2 packages in the Mageia 3 repo's. These are packages that for some reason could not be re-built for Mageia 3, but can still be used in Mageia 3. So it is quite normal for there to be .mga1 and/or .mga2 packages on a Mageia 3 system.

Jim

[doktor5000]

Removing packages by ver (mga2) is probably not that safe, but urpme --auto-orphans may be good and sometimes may not.

Both can be very dangerous and destructive, if you don't pay close attention and know what all those packages are doing.

A good way to identify packages which should be investigated/updated is urpmq --not-available

--not-available
List packages that are not available on any media. This can help to find packages that are still installed but that are now obsolete because
they have been removed from the current version of Mageia Linux.

[eldiener]

You cannot remove it because in needs to be upgraded, not removed. The correct version is "python-dbus-1.1.1-2.mga3". You SHOULD be able to upgrade it from MCC as somehow it seems to have gotten missed on the initial upgrade process. This CAN happen sometimes and it is always a good idea when you find mga2 packages, to make sure there are not mga3 packages by the same name to upgrade to. This requires setting up MCC to pull packages off of a mirror rather than using the install disk as sometimes packages may get left off the install disk.

Installing "python-dbus-1.1.1-2.mga3" automatically removed the mga2 package. Thanks !

The Mageia developers did a pretty good job and just missed this one upgrade in my installation. Understandable.

[doktor5000]

The Mageia developers did a pretty good job and just missed this one upgrade in my installation. Understandable.

You read the last step at the release notes for upgrading?

On the first reboot use the command 'urpmi --auto-update' to make sure all packages were updated.

Apart from that, please mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks