On 08/28/2014 05:27 PM, Miroslav Suchý wrote:
On 08/28/2014 03:49 PM, Ralf Corsepius wrote:
> Examples? At least in some cases these likely are packaging bugs.
I was looking for those examples and I realized I lied a little. So
I saw a lot of examples where BR had *circular* dependencies because of
OK. this is not unusual. The "bootsrap" rpm flag trick
might be a proper
work-around for these
Note you'll have to build all packages twice. Once with a "bootstrap
flag" set during a "bootstrap" from scratch and a second time without
"bootstrap flag" set, when incrementally building.
(Initially I was suspecting some testsuites being run against older,
installed packages and not against the just having been built versions.
We've had some of these cases, in the past.).
For example whole Ruby On Rails stack. Huge amount of packages needs
some rubygems for %check, but those rubygems need that original gem as
BR of itself. E.g: rubygem-tilt, rubygem-thor, rubygem-fomatador,
rubygem-rspec-expectations, rubygem-mocks, rubygem-rack-protection,
My wild guess would be ruby likely is in a similar situation as perl
(which applies the bootstrap trick).