Stephan Kulow <[email protected]> writes: > On 9/10/19 12:35 PM, Dan Cermak wrote: >> Hi list, >> >> when collecting the dependencies of rubocop for a submission to Factory, >> I've found out that we have a duplicate gem: ruby-progressbar exists as >> rubygem-progressbar and rubygem-ruby-progressbar. >> >> If I haven't messed up the repoquery, then the following packages depend >> on rubygem-ruby-progressbar: >> - rubygem-fuubar >> - rubygem-rubocop >> - rubygem-minitest-reporters >> - rubygem-rails_best_practices >> >> In contrast to rubygem-dister which appears to be the only package >> depending on rubygem-progressbar. >> >> I would therefore propose to patch rubygem-dister so that it's >> dependencies are correct and subsequently delete rubygem-progressbar. >> >> >> Any objections/suggestion/ideas? >> > Well, it's not exactly a duplicate on our side: > > https://rubygems.org/gems/progressbar > https://rubygems.org/gems/ruby-progressbar > > https://github.com/jfelchner/ruby-progressbar/wiki/progressbar-Has-Been-Merged-Into-ruby-progressbar >
Yikes, completely missed that one. Thanks Stephan and Duncan for pointing that out. > So I guess this should be fixed in dister, I asume Flavio might even > read this mailing list :) It should be fixed upstream, but I don't know how likely that is going to happen, given that dister hasn't been touched since 2012 and is a tool to package rails applications for the now disabled SUSE Studio. @Flavio: what's your opinion on this? Cheers, Dan
signature.asc
Description: PGP signature
