Bug 21321

There are currently tons of problems with dependencies, due to the upgrade of Perl from 5.22 to 5.26. It looks like not all dependencies have been successfully rebuilt with Perl 5.26, and you now have a mix of dependencies built against 5.26 together with dependencies built against 5.22, leaving cauldron in a "broken" state.

When I run urpmi --auto-update, I also get:

Certains paquetages demandés ne peuvent pas être installés :
drakx-net-2.32-1.mga6.noarch (Tentative de promouvoir perl-Gtk3)
drakxtools-17.88-2.mga7.x86_64 (car drakx-net est non satisfait, Tentative de promouvoir drakxtools, drakxtools)
gurpmi-8.110-1.mga6.noarch (afin de garder gurpmi-8.110-3.mga7.noarch)
gurpmi-8.110-2.mga6.noarch (afin de garder gurpmi-8.110-3.mga7.noarch)
harddrake-ui-17.88-2.mga7.x86_64 (car drakxtools[== 17.88-2.mga7] est non satisfait)
userdrake-2.16-2.mga7.x86_64 (car perl(ugtk3) est non satisfait)


It looks like there is a mix of packages from mga6 and from mga7.

CC: (none) => LpSolit

Just wait until the situation settles down after perl update and rebuilds are over.

This has now changed to be due to be about insufficient perl-base-5.26.0-2.mga7.i586 for perl-Cairo-GObject-1.4.0-13.mga7.i586

Summary: Trying to reinstall drakxtools or rpmdrake fails with "perl-Glib-Object-Introspection-0.43.0-1.mga7.x86_64 (due to insufficient libperl.so.5.22()(64bit))" => Trying to reinstall drakxtools or rpmdrake fails with "perl-Cairo-GObject-1.4.0-13.mga7.i586 (due to insufficient perl-base-5.26.0-2.mga7.i586)"

(In reply to Jani Välimaa from comment #2)
> Just wait until the situation settles down after perl update and rebuilds
> are over.

It isn't that simple: same here but whole system got borked, connections are gone, mounting dvd's hardly works. Trying to revive it is a helluva job. Boot only works with addition of 'audit=0" to boot parameter and no higher than runlevel 3. Can only get mga6 packages from a bootable M6 install DVD. No fun...

CC: (none) => dvgevers

(In reply to Dick Gevers from comment #4)
> (In reply to Jani Välimaa from comment #2)
> > Just wait until the situation settles down after perl update and rebuilds
> > are over.
> 
> It isn't that simple: same here but whole system got borked, connections are
> gone, mounting dvd's hardly works. Trying to revive it is a helluva job.
> Boot only works with addition of 'audit=0" to boot parameter and no higher
> than runlevel 3. Can only get mga6 packages from a bootable M6 install DVD.
> No fun...

Did you allow

  "The following packages have to be removed for others to be upgraded:" ?

Source RPM: (none) => perl
CC: (none) => marja11

(In reply to Marja van Waes from comment #5)

> Did you allow
> 
>   "The following packages have to be removed for others to be upgraded:" ?

Nope I did't. So there was nothing to install with urpmi (early afternoon yesterday). Then I looked with rpmdrake to see if there might be anything that could be installed (for example not depending on perl) and yes it was able to install about 34 packages. However when this transaction finished, rpmdrake segfaulted, I noticed some *rpmsave packages in /etc/sysconfig but ABSENCE of same *without* the *rpmsave in the name, which I fixed.

I saw my Mageia main menu (in XFCE4) was empty and then about 3 minutes after rpmdrake's segfault the whole system crashed: rebooted. All *drak* packages gone, 2 older kernels gone, current package for kernel not in rpmdb anymore (but still booting ), bootloader-utils gone, dracut gone....

With todays update IF perl-URPMI I can now install rpmdrake which seems to pull drakxtools and derivates with it so therefore I feel that this can be closed as RESOLVED FIXED.

Any objections?

Well I don't mind *if* the perl experts are aware that rpmdrake or friends can apparently blow up a well running system...

(In reply to Dick Gevers from comment #8)
> Well I don't mind *if* the perl experts are aware that rpmdrake or friends
> can apparently blow up a well running system...

Running Cauldron at the beginning of the release cycle *will* blow up a well running system yes. You should stay on Mageia 6 for a while until the major upgrades of core components are done, the current breakage on Cauldron is normal and being worked on.

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

Oops, didn't mean to close it in the end, reverting.

Resolution: OLD => (none)
Status: RESOLVED => REOPENED

I don't mind the breakage, as long as it is known ;)

Closing

Resolution: (none) => OLD
CC: (none) => thierry.vignaud
Status: REOPENED => RESOLVED