Bug 22308

Summary: urpmi fails - "transaction is too small: ruby-rdoc-5.0.0-15.mga7.noarch is rejected but it should notl"
Product: Mageia Reporter: Frank Griffin <ftg>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11, pterjan, thierry.vignaud
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: urpmi CVE:
Status comment:
Attachments: stdout/stderr

Description Frank Griffin 2018-01-03 18:13:21 CET
urpmi --auto-update fails on one of my cauldron systems (but not on another) claiming "transaction too small".  I'll attach the stdout/stderr.
Comment 1 Frank Griffin 2018-01-03 18:15:42 CET
Created attachment 9877 [details]
stdout/stderr
Comment 2 Marja Van Waes 2018-01-04 07:53:21 CET
confirmed by ankh on IRC
2018:01:04:07:16 < ankh> says urpmi -- transaction is too small: 
                         ruby-rdoc-5.0.0-9.mga7.noarch is rejected but it 
                         should not (current transaction: 
                         ruby-irb-2.5.0-8.mga7.noarch 
                         ruby-json-2.1.0-2.mga7.x86_64, requested: 
                         ruby-2.5.0-8.mga7.x86_64+ruby-json-2.1.0-2.mga7.x86_64)

Frank, if you add /^subversion/ in the skip list, then I think updating should work.

Of the packages that urpmi tried to update, subversion-tools is in the list that's given by

urpmq --whatrequires-recursive  ruby-rdoc | grep -v ruby

CC: (none) => marja11, pterjan, thierry.vignaud
Summary: urpmi fails - "transaction too small" => urpmi fails - "transaction is too small: ruby-rdoc-5.0.0-15.mga7.noarch is rejected but it should notl"
Assignee: bugsquad => mageiatools

Comment 3 Pascal Terjan 2018-01-05 19:30:43 CET
I notice in your output:

ruby-io-console-0.4.6-8.mga7.x86_64 (in order to keep ruby-io-console-0.4.6-15.mga7.x86_64)

I need to fix this one, hopefully that will help
Comment 4 Frank Griffin 2018-01-06 20:19:02 CET
Actually, this stopped happening before ruby was fixed.  Looks to be a SNO that was somehow triggered.

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

Comment 5 Marja Van Waes 2018-01-11 07:59:37 CET
(In reply to Frank Griffin from comment #4)
> Actually, this stopped happening before ruby was fixed.  Looks to be a SNO
> that was somehow triggered.

What's a SNO? :-)
Comment 6 Frank Griffin 2018-01-11 15:09:34 CET
Should Not Occur :-)
Comment 7 Marja Van Waes 2018-01-13 08:16:05 CET
(In reply to Frank Griffin from comment #6)
> Should Not Occur :-)

lol

thx :-)