On Thu, Jan 17, 2013 at 12:30 PM, Christian Boltz <cb@cboltz.de> wrote:
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.
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
The whole point of building the test separately is so other packages will not need to wait for the testsuite before building. Personally I see two approaches: 1. If you are modifying a package with a separate testsuite spec file, disable publishing until you can confirm the testsuite passed. 2. Add a new repository configuration option that allows project maintainers to specify a package as a "blocker" that will prevent the repository from publishing if it doesn't build successfully (I am not sure what this would be called). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org