Bug 17416

Summary:	drakrpm-update crashed (detecting looping forever while trying to resolve dependancies)
Product:	Mageia	Reporter:	Ezequiel Partida <ezequiel_partida>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	rpmdrake-6.20-1.mga5	CVE:
Status comment:

Description Ezequiel Partida 2015-12-29 03:03:53 CET

The "drakrpm-update" program crashed. Drakbug-17.8 caught it.

I was just updating using: urpmi --auto-update -v

detecting looping forever while trying to resolve dependancies.
Aborting... Try again with '-vv --debug' options at /usr/lib/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/URPM/Resolve.pm line 1286.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/URPM/Resolve.pm:1286
URPM::resolve_requested__no_recommends_() called from /usr/lib/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/URPM/Resolve.pm:1168
URPM::resolve_requested__no_recommends() called from /usr/lib/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/URPM/Resolve.pm:1098
URPM::resolve_requested() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/pkg.pm:408
Rpmdrake::pkg::get_updates_list() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/pkg.pm:509
Rpmdrake::pkg::get_pkgs() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/gui.pm:642
Rpmdrake::gui::pkgs_provider() called from /usr/libexec/drakrpm-update:266
main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293

Theme name: Adwaita
Kernel version = 4.4.0-desktop-0.rc6.2.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz

Comment 1 Thierry Vignaud 2015-12-29 12:33:02 CET

Probably some temporary broken packages

CC: (none) => thierry.vignaud
Summary: drakrpm-update crashed => drakrpm-update crashed (detecting looping forever while trying to resolve dependancies)

Comment 2 Samuel Verschelde 2016-02-23 14:29:08 CET

Closing as OLD as per comment #1. Please reopen or create a new bug report if it happens again.

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