Hello, Am Mittwoch, 16. Januar 2013 schrieb Stefan Seyfried:
Am 16.01.2013 22:36, schrieb todd rme:
On Tue, Jan 15, 2013 at 11:23 AM, Stefan Seyfried
<stefan.seyfried@googlemail.com> wrote:
Well, but if the testsuite is split off, a broken (testsuite-failing) version of coreutils might be used to build all the dependencies. Do we want that?
As long as it isn't published, I don't see why that is a major problem. Only the testsuite package will not be published, the main package will be AFAIU.
Could this be a starting point? My proposal would be (untested): - add to coreutils-testsuite: Provides: coreutils-tested = %(rpm -q --qf '%{version}-%{release}' coreutils) - add to coreutils: Requires: coreutils-tested = %{version}-%{release} (Requires, not BuildRequires!) Can/will this work, or does it create a circular loop in the post-build checks? As an alternative, change the BuildRequires in lots of packages from coreutils to coreutils-testsuite (maybe using "substitute" in OBS). I know it's not really correct[tm], but I'm quite sure it would work ;-) Gruß Christian Boltz -- <suseROCKs> I hate email <suseROCKs> I hate internet <suseROCKs> I hate computers <suseROCKs> why can't we go back to old fashioned smoke signaling?? [from #opensuse-project] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org