Failure upgrading to Cauldron from MGA1

[zeke]

Reposted from Basic Support board at the suggestion of a member.....

I am trying to upgrade to Cauldron, and simply followed the wiki. I am getting a failure here:

Code: Select all

installing libwnck1_22-2.30.7-1.mga2.i586.rpm krdc-handbook-4.8.0-2.mga2.noarch.rpm krdc-4.8.0-2.mga2.i586.rpm libwnck-2.30.7-1.mga2.i586.rpm kopete-handbook-4.8.0-2.mga2.noarch.rpm libmediastreamer1-3.5.0-1.mga2.i586.rpm kopete-4.8.0-2.mga2.i586.rpm libavahi-ui1-0.6.30-6.mga2.i586.rpm libffado2-2.0.1-5.mga2.i586.rpm from /var/cache/urpmi/rpms
Installation failed:    file /usr/lib/libpng12.so.0.47.0 from install of libpng12_0-2:1.2.47-1.mga2.i586 conflicts with file from package libpng3-2:1.2.47-1.mga1.i586
        libgdk_pixbuf2.0_0 = 2.25.2-1.mga2 is needed by libgdk_pixbuf-gir2.0-2.25.2-1.mga2.i586
        libgdk_pixbuf2.0_0-loaders-png12 is needed by lsb-lib-4.1-10.mga2.i586
        libpng12_0 is needed by lsb-lib-4.1-10.mga2.i586
        soprano = 4:2.7.4 is needed by soprano-plugin-common-4:2.7.4-1.mga2.i586
        soprano-plugin-virtuoso = 4:2.6.0 is needed by (installed) soprano-4:2.6.0-0.1.mga1.i586
        mariadb-common-core(x86-32) >= 5.5.20-0.20120226.alpha.mga2 is needed by mariadb-extra-5.5.20-0.20120226.alpha.mga2.i586
        typelib(GdkPixbuf) = 2.0 is needed by libgtk-gir2.0-2.24.10-3.mga2.i586
        typelib(Gdk) = 2.0 is needed by libwnck1_22-2.30.7-1.mga2.i586
        typelib(GdkPixbuf) = 2.0 is needed by libwnck1_22-2.30.7-1.mga2.i586
        typelib(Gtk) = 2.0 is needed by libwnck1_22-2.30.7-1.mga2.i586


trying to urpme libpng3 wants to remove 603 dependent packages!

how do i get around this?

Thanks!

[jaywalker]

I had a similar problem with a different package and decided to let it remove the two-three hundred affected packages. I upgraded an Alpha 3 install to Beta1+ because many of the bugs logged against Alpha2 & 3 are now fixed in Beta1+ and I wanted to find out if there is a smooth upgrade path. I think the answer is No.

Some of the udisks auto-mounting problems I had are now gone (as of tonight's updates) but the updated Alpha3 system still has problems. There may be a way to do it but by the time I figure it out we'll have Beta2 and more. My best advice is to bite the bullet, grab a dvd iso (or a boot iso for a network install) and go straight to Beta1 + updates.

Richard.

PS. If you find the dependencies problem a little hard to get your head around and you think that it cannot possibly be right, then maybe we should start another thread to discuss this problem and explore some solutions. I found out yesterday that to install kaffeine (on a system already running xine) requires over 250 additional packages at hundreds of megabytes! Glad I'm not on dial-up, but then again, gladder still I can learn to live without kaffeine.

[doktor5000]

You should report that, see maybe https://wiki.mageia.org/en/How_to_report_a_bug_properly
Probably some minor dependency error, should definitely be fixed as Mageia 1 -> 2 is a supported upgrade path.

[jaywalker]

I don't think it is a bug, but I don't know enough about packaging to understand the decisions being made by packagers. I can understand how it might be a bug if a required package accidentally gets left out of a rebuild, but for applications to have other applications in their dependency tree and thus acquire all of the second application's dependencies seems to my mind to be somewhat bizarre.

By the way, I was speaking of an upgrade path within the Cauldron development history. I missed the point that the original poster was coming from MGA1. Another case of reading what I think is written, not what was written.

I reckon that jumping from my frozen Alpha3 system (frozen while I focussed on a couple of fresh Beta1 installs) to today's Beta1+ many updates is understandably a risky move. The difference between the two "versions" boot sequences and boot errors/warnings was quite distinct, with the Beta 1 startup being much quicker and less error-prone. Bear in mind that the raw Beta1 was only a day or so "newer" than the fully updated and much hacked-upon Alpha3, but it still had, until today, a whole raft of the same udisks problems and quite a few permissions/authorisations issues too. These now seem to have been fixed so I thought it would be a good idea to apply the current Cauldron state to the now quite old Alpha3.

So my original test system is now up to date with my Beta1 system and all of the disc access problems I had there have been fixed. However, there are still differences between the two in the boot process (and closedown) which I do not yet understand. As the newer test environment is working closer to "pretty damn good" I am inclined not to worry too much about why the older one still has issues.

It's the computer version of the old joke where an American tourist asks a farmer in the wilds of County Cork what is the best way to get to Dublin. The farmer's reply, after much thinking and chin stroking, is simple; "If I were you I wouldn't start from here".

[wilcal]

Mageia 1 -> 2 is a supported upgrade path.

So if I made a new install from DVD of Mageia 1, made no
updates to it, and then attempted to install ( upgrade )
Mageia 2 over it that should work?

[doktor5000]

@wilcal: Well, it should ...

@jaywalker: If the upgrade is not able to automatically upgrade all packages it definitely is a packaging bug.
Maybe just a typo, or the packager gave a wrong version number for some Requires tag or forgot to add some Conflicts.
I've sent the maintainer of those packages a message so that he's aware of the problem (which normally would be the pupose
of a bug report, that's why i've suggested that)

[fwang]

Reposted from Basic Support board at the suggestion of a member.....

I am trying to upgrade to Cauldron, and simply followed the wiki. I am getting a failure here:

Code: Select all

installing libwnck1_22-2.30.7-1.mga2.i586.rpm krdc-handbook-4.8.0-2.mga2.noarch.rpm krdc-4.8.0-2.mga2.i586.rpm libwnck-2.30.7-1.mga2.i586.rpm kopete-handbook-4.8.0-2.mga2.noarch.rpm libmediastreamer1-3.5.0-1.mga2.i586.rpm kopete-4.8.0-2.mga2.i586.rpm libavahi-ui1-0.6.30-6.mga2.i586.rpm libffado2-2.0.1-5.mga2.i586.rpm from /var/cache/urpmi/rpms
Installation failed:    file /usr/lib/libpng12.so.0.47.0 from install of libpng12_0-2:1.2.47-1.mga2.i586 conflicts with file from package libpng3-2:1.2.47-1.mga1.i586


trying to urpme libpng3 wants to remove 603 dependent packages!

how do i get around this?

Thanks!

Thanks for pointing this, it is caused by libpng12_0 from cauldron, should be fixed in latest libpng12_0-1.2.47-2.mga2 package in cauldron.

[zeke]

Thanks twang,

So If I try again tonight it should work? Or do I need to specifically install the libpng12_0-1.2.47-2.mga2 package?

[fwang]

Thanks twang,

So If I try again tonight it should work? Or do I need to specifically install the libpng12_0-1.2.47-2.mga2 package?

It should work, libpng3 will be replaced by libpng12_0. If there are other file conflicts or errors, please report. Thanks.

[zeke]

It did work, but the video driver/config got bunged up. (This is an NVIDIA ION netbook). I ended up going ahead and installing the beta iso over my OS partition. I am still having problems with the video driver though.

MGA1 automagically supports my driver and wlan interface, but MGA2 does not. I had to enable the nonfree and tainted repos to get the nvidia and broadcom wlan drivers. That was fine, but after installing the proprietary driver through XFdrake (seemingly with no problems), I get an error message at kde startup saying that the driver could not be found and so the system reverts to nouveau.

[doktor5000]

I get an error message at kde startup saying that the driver could not be found and so the system reverts to nouveau.

See the other thread about this particular issue: viewtopic.php?f=15&t=1992