* todd rme (toddrme2178@gmail.com) [20130117 13:54]:
1. If you are modifying a package with a separate testsuite spec file, disable publishing until you can confirm the testsuite passed.
No use. The testsuite can fail because of changes in other packages like glibc so disabling publishing would have to be an automatic thing in order to be usefull.
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).
IMO the only viable way if such an approach is used. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org