Hi, On Tue, Jul 30, 2013 at 10:37:55PM +0200, Stephan Kulow wrote:
d) Too few people actually care and fix problems of importance
Or they maybe care, but don't know how to help. That's the case for me. I know lots of stuff about packaging, but I know that I will fail with more advanced issues. Packaging wise, but also with source code bugs. The main issues to stay away from helping are: - I get those emails for factory work and I never touched one of the packages, because I don't know if someone else already started to work on it. I would expect an email that tells me that the information from the previous mail is deprecated and the issue fixed. => a locking mechanism might be helpful here since fixing can take hours - it is hard to tell what might have caused the breakage with packages that I have never seen before. OBS should help with telling me what has changed and therefore might have caused the breakage. Does anyone want to compare build logs? :) => make transparent what has changed since the last successful build - documentation is not up-to-date, incomplete or missing. For instance rpmlint gives me a lot of errors, but even with hours of googling I wasn't able to fix one of my packages today. As an example this provides less information than the build log error message: http://en.opensuse.org/openSUSE:Packaging_checks#files-duplicate I usually search through my spec files, but this doesn't answer all my questions. => Some best practice spec files would be helpful for stuff like qmake, desktop files, etc. I would be willing to help with the documentation effort around it, but it is hard to judge where to start and if maybe anyone else is taking the same effort already. -- Bye, Stephan Barth SUSE MaintenanceSecurity - SUSE LINUX GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org