On Thu, 2015-01-29 at 18:20 -0500, Greg Freemyer wrote:
On Thu, Jan 29, 2015 at 5:34 PM, Dimstar / Dominique Leuenberger
wrote: On Thu, 2015-01-29 at 15:46 -0500, Greg Freemyer wrote:
I'd find it more valuable if it confirmed the deps could be satisfied. As it is now a typo in a "Requires" statement isn't picked up until you manually try to install the RPM.
The problem with that is that any Requires would forcibly need to be available in the buildroot (so a BuildRequires)... whereas this is often the case, there are many cases where this assumption would only lead to much larger build cyles (especially true with python stuff - you need close to nothing to build/install it, but to run you might need a lot more).
When forwarding stuff to TW, though, it is ensured that at the time it is accepted, it is installable. Of course this can change over time (think changed libraries, wrongly executed package renames)
Cheers,
-- Dimstar / Dominique Leuenberger
"ensured" ?
Yes, repo-checker only gives a green light when it actually manages to install the beast.
Just this morning I had a package accepted (by you!) to factory that didn't have all the BuildRequires accepted yet. The missing BuidRequire has been in staging for a couple weeks and should show up in factory at some point, so I'm not complaining. https://build.opensuse.org/package/show/openSUSE:Factory/libfvalue
Hmm.. that seems to be an interesting case, I'll have to look at. Seems this package was marked to be in Staging:G, whereas it should actually be in Staging:F with all the others from your stack. And yes, :G was accepted yesterday (as libfvalue was actually not part of the testings there...) Will be a fun exercise to find the glitch in the toolchain... but then: missing BuildRequires is not as bad as missing Requires: this package simply won't build until the rest appears (not really wanted, but it doesn't harm)
Regardless, I'd love to see a mechanism to force a installability test in the devel/home projects.
In some projects I maintain I achieve this by a test package that
BuildRequires the ones I care for sufficiently to test. If that one
succees, it means it can install what I have in BR. Of course it's a
workaround.
For such a feature, I'd recommend to go to the OBS team and actually ASK
for it. Just wishing for it without expressing the wish to the devs in
question won't make it happen.
Oh, by the way: here is a list of install-issues currently in
Tumbleweed:
https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashbo...
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger