Overview
Request History
rguenther created request
- Explicitly BuildRequire m4 (forwarded request 455769 from dimstar)
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added factory-repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
dimstar_suse set openSUSE:Factory:Staging:A as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:A"
dimstar_suse accepted review
Picked openSUSE:Factory:Staging:A
factory-repo-checker accepted review
Builds for repo devel:libraries:c_c++/openSUSE_Factory
coolo accepted review
jengelh accepted review
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory
this introduced a new cycle edge [('gmp', 'm4')] but this might what we have to accept to.
It was there implicitely already - 'm4' was in the set of packages pre-installed (not sure through which dependency). I suppose m4 depends on gmp only indirectly through gcc and thus this cycle was already there as well (effectively through gcc).
I think the goal here was it's planning to get m4 out of the buildroot.
... if possible
m4 pulls in coreutils, which is linked against libgmp10 - that's how m4 depends on gmp to build (and ye, that is clearly nothing new)
m4 being in the cycle is nothing we can avoid (either implicit or explicit)