Bug 17156 - ruby-RubyGems-2.4.8-3.mga6 dependency loop
Summary: ruby-RubyGems-2.4.8-3.mga6 dependency loop
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Pascal Terjan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-15 18:37 CET by Nikolay Malykh
Modified: 2015-11-16 06:37 CET (History)
3 users (show)

See Also:
Source RPM: ruby-RubyGems-2.4.8-3.mga6
CVE:
Status comment:

Attachments
debug output of urpmi --update (65.32 KB, application/gzip)
2015-11-15 20:06 CET, Florent Denoual 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Nikolay Malykh 2015-11-15 18:37:49 CET 
The "mgaapplet-update-checker" program crashed. Drakbug-17.1 caught it.

urpmi --auto-update

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.22.0/urpm/select.pm:347
urpm::select::resolve_dependencies() called from /bin/mgaapplet-update-checker:79

Theme name: Nodoka
Kernel version = 4.2.6-desktop-1.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=Intel(R) Xeon(R) CPU           E5645  @ 2.40GHz
Comment 1 Marja Van Waes 2015-11-15 19:47:32 CET 
Hi Nikolay

Can you please attach the file urpmi_debug.txt that is the result of (as root, of course):

urpmi --auto-update -vv --debug 2>&1 | tee urpmi_debug.txt

Keywords: (none) => NEEDINFO
CC: (none) => marja11, thierry.vignaud

Comment 2 Florent Denoual 2015-11-15 20:06:28 CET 
Created attachment 7203 [details]
debug output of urpmi --update

Hi

Same crash here

Gezipped result of urpmi --auto-update -vv --debug 2>&1 | tee urpmi_debug.txt in attachment

CC: (none) => littlebzh

Comment 3 Marja Van Waes 2015-11-15 21:09:12 CET 
On dev ml, Charles Edwards explained that it was the

rpm-mageia-setup < 2.17

conflict that was added to ruby-RubyGems-2.4.8-3.mga6

that causes this

Keywords: NEEDINFO => (none)
Assignee: bugsquad => pterjan
Summary: mgaapplet-update-checker crashed => ruby-RubyGems-2.4.8-3.mga6 dependency loop
Source RPM: mgaonline-3.15-1.mga5 => ruby-RubyGems-2.4.8-3.mga6

Comment 4 Florent Denoual 2015-11-15 21:33:22 CET 
(In reply to Marja van Waes from comment #3)
> On dev ml, Charles Edwards explained that it was the
> 
> rpm-mageia-setup < 2.17
> 
> conflict that was added to ruby-RubyGems-2.4.8-3.mga6
> 
> that causes this

It's true, after remove it, update works

I wanted to try to reinstall ruby-RubyGems-2.4.8-2.mga6 after update but it failed

debug said (coherant with your explaination)

...
installed package rpm-mageia-setup-2.16-1.mga6.x86_64 is conflicting with ruby-RubyGems-2.4.8-3.mga6.noarch (Conflicts: rpm-mageia-setup[< 2.17])
...
Comment 5 Pascal Terjan 2015-11-15 23:15:10 CET 
I don't know why it loops, it should just not be able to install ruby-RubyGems-2.4.8-3.mga6.noarch.

Anyway, tv submitted rpm-mageia-setup-2.17-1.mga6 which will make the problem go away
Comment 6 Florent Denoual 2015-11-15 23:37:09 CET 
(In reply to Pascal Terjan from comment #5)
> I don't know why it loops, it should just not be able to install
> ruby-RubyGems-2.4.8-3.mga6.noarch.
> 
> Anyway, tv submitted rpm-mageia-setup-2.17-1.mga6 which will make the
> problem go away

Juste tested

After update of rpm-mageia-setup and reinstallation of ruby, urpmi --auto-update performed without loop.

Thanks
Comment 7 Thierry Vignaud 2015-11-16 06:37:45 CET 
Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.