Note that I cannot install the most recent updates at all because of this problem; not even via direct MCC invocation (much less the little red reminder in the status bar).

BTW All updates to this point have been successfully applied; NO problems until THIS update.

Upgraded this to high priority as I cannot update my system any longer at this time.

Priority: Normal => High

You can use this as root to update your system:

urpmi --auto-update

Thankyou for the report :)

What is displayed in the terminal if you run MageiaUpdate from the terminal after adding the following line before line 572 ("split_fullname") in /usr/lib/perl5/vendor_perl/5.14.2/Rpmdrake/pkg.pm :

    use Data::Dumper; warn Dumper \@meta_pkgs;

Keywords: (none) => NEEDINFO

(In reply to comment #4)
> You can use this as root to update your system:
> 
> urpmi --auto-update
> 
> Thankyou for the report :)

Thanks, this at least allowed me to update my system (and learn more about using urpmi from the command line).

(In reply to comment #5)
> What is displayed in the terminal if you run MageiaUpdate from the terminal
> after adding the following line before line 572 ("split_fullname") in
> /usr/lib/perl5/vendor_perl/5.14.2/Rpmdrake/pkg.pm :
> 
>     use Data::Dumper; warn Dumper \@meta_pkgs;

Hi:

I did so as requested (see below) and while it did not cause any problems, I cannot tell if it fixed my problme as the "urpmi --auto-update" completed all my currently-informed updates.

I suspect that I'll have to wait until the next update before I can really test this or is there an easy way to force this code path to be taken?

    my @meta_pkgs = grep { /^task-|^basesystem/ } keys %all_pkgs;

    my @gui_pkgs = map { chomp; $_ } cat_('/usr/share/rpmdrake/gui.lst');
    # add meta packages to GUI packages list (which expect basic names not fullnames):
    push @gui_pkgs, map { (split_fullname($_))[0] } @meta_pkgs;

    use Data::Dumper; warn Dumper \@meta_pkgs;   <<<<<<<<<<<<<<<<
    +{ urpm => $urpm,
       all_pkgs => \%all_pkgs,
       installed => \@installed_pkgs,
       installable => \@installable_pkgs,
       updates => \@updates,
       meta_pkgs => \@meta_pkgs,
       gui_pkgs => [ grep { member(($all_pkgs{$_}{pkg}->fullname)[0], @gui_pkgs) } keys %all_pkgs ],
       update_descr => $update_descr,
       backports => [ @inactive_backports, @active_backports ],
       inactive_backports => \@inactive_backports
   };

Please advise,
Thanks,
Marty

(In reply to comment #7)
> (In reply to comment #5)
> > What is displayed in the terminal if you run MageiaUpdate from the terminal
> > after adding the following line before line 572 ("split_fullname") in
> > /usr/lib/perl5/vendor_perl/5.14.2/Rpmdrake/pkg.pm :
> > 
> >     use Data::Dumper; warn Dumper \@meta_pkgs;
> 
> Hi:
> 
> I did so as requested (see below) and while it did not cause any problems, I
> cannot tell if it fixed my problme as the "urpmi --auto-update" completed all
> my currently-informed updates.
> 
> I suspect that I'll have to wait until the next update before I can really test
> this or is there an easy way to force this code path to be taken?
> 
>     my @meta_pkgs = grep { /^task-|^basesystem/ } keys %all_pkgs;
> 
>     my @gui_pkgs = map { chomp; $_ } cat_('/usr/share/rpmdrake/gui.lst');
>     # add meta packages to GUI packages list (which expect basic names not
> fullnames):
>     push @gui_pkgs, map { (split_fullname($_))[0] } @meta_pkgs;
> 
>     use Data::Dumper; warn Dumper \@meta_pkgs;   <<<<<<<<<<<<<<<<
>     +{ urpm => $urpm,
>        all_pkgs => \%all_pkgs,
>        installed => \@installed_pkgs,
>        installable => \@installable_pkgs,
>        updates => \@updates,
>        meta_pkgs => \@meta_pkgs,
>        gui_pkgs => [ grep { member(($all_pkgs{$_}{pkg}->fullname)[0],
> @gui_pkgs) } keys %all_pkgs ],
>        update_descr => $update_descr,
>        backports => [ @inactive_backports, @active_backports ],
>        inactive_backports => \@inactive_backports
>    };
> 
> Please advise,
> Thanks,
> Marty

I am happy to report that after testing this today on my system (the one this bug occurred on) that the bug appears fixed with the above-suggested fix.

As far as I'm concerned, this is now fix; feel free to close it as necessary.

Thanks again to everyone for the prompt attention to this problem.

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

err there has been no fix for this bug...

(In reply to comment #9)
> err there has been no fix for this bug...

You're exactly right. Sorry, but in my joy at having this fixed, I mis-stated. I'll put this back in the "new" state and let those that handle this take on the real fix (might it not be this workaround) as they see fit.

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

Put back in the "new" state as promised above.

Status: REOPENED => NEW

*** Bug 7487 has been marked as a duplicate of this bug. ***

CC: (none) => ranchhand

@Tom: if you can still reproduce this bug, could you either attach or sent me by email the bug7439.tar.xz file resulting from running as root the following commands:
urpmi --auto-select --bug bug7439
tar cfa bug7439{.tar.xz,}

IMPORTANT: answer "n" when asking to actually install the updates so that we can get a chance to fix this bug

Keywords: (none) => NEEDINFO

I am the feller that filed bug7487.

Unfortunately I can't get you the info you wanted.

After the thing crashed and the auto bug report tool came up, I filed the bug and then went about trying to get things to run.

One thing I had neglected to do was enable all the "debug" media.  I did that and logged out and back in to see if it would effect the update/upgrade tool.

It did and I ran those upgrades.

Today I popped over here and tried it again to see if it would work or crash.  I am sorry to say that it worked.  I can't duplicate the crash.

I am happy that it worked but that doesn't get you anywhere.

Will do better in the future.

Tested Ubuntu for several years and ran their dev releases as my production OS.  That does not, however, make me any more than a noob to Mageia and particularly RPM and your bug system.

Please feel free to jump my ass if I screw up.  I am a grumpy geezer and can take it.

I want to get up to speed on this stuff as fast as I can so that I can help support this fine project.

I've commited a workaround in SVN though I would love to know the root issue

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