Hello, On May 23 11:21 Dirk Mueller wrote (shortened): > So far, the following checks are enabled: > > arch-dependent-file-in-usr-share 590 > infopage-not-gzipped 540 > wrong-script-interpreter 533 > arch-independent-package-contains-binary-or-object 499 > library-without-ldconfig-postun 400 > shlib-with-non-pic-code 223 > files-duplicated-waste 100 > summary-not-capitalized 63 > spurious-executable-perm 50 > devel-file-in-non-devel-package 50 > wrong-file-end-of-line-encoding 1 > ... > The number behind the check name above is the badness score > that was assigned to it. if any build has a score above 1000, > it is currently failed.
I do not understand why the badness of different errors are added at all. I think one single error is either severe enough to let the build fail or not. E.g. why is it built with one arch-dependent-file-in-usr-share and one library-without-ldconfig-postun error but not with one wrong-script-interpreter error and one arch-independent-package-contains-binary-or-object error? I suggest to compare the badness value for each single error with a threshold but not sum up anything. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
