Re: Lintian based autorejects
Russ Allbery <rra@debian.org> writes:
> (On vacation with intermittant access, so it may be a while before I see
> responses.)
>
> Ryan Niebur <ryan@debian.org> writes:
>
>> this is probably a question more for lintian maintainers, but... what
>> should we do if lintian is buggy and falsely claims our package has
>> one of these tags?
>
> The same as what you would do with any other buggy package in Debian: file
> a bug. I don't know how ftpmaster wants to handle that case, but I
> suspect replying to the REJECT message to also let them know about the
> problem would be reasonable.
And then wait 6 month for them to find time to fix the issue?
Seriously?
If people start complaining to ftp-master about every lintian based
reject the opposite of the goal is achived. Ftp-master will be even
more busy with pointless work.
This must be fixable on the package level or the work will ne be
spread around. So someone better make damn sure that any non
overridable tag doesn't have false positives.
>> also, it would be nice to have a way to run lintian so that
>> it will only list problems that will cause a REJECT, and have it exit
>> with non-zero if any of those are not overriden (or are overriden but
>> not allowed to be overriden).
>
> This is definitely something I want to do in the near future in Lintian,
> but if you could file a wishlist bug against Lintian, that would ensure
> that we don't forget.
dpkg-buildpackage, debuild, apt-get -b source, pdebuilder, sbuild,
... should fail too.
If lintian based rejects are done on manual (source) uploads then
buildds should also run lintian on the packages and fail builds that
should be rejected before upload os both the buildd admin is notified
and the buildd logs show the problem. As mentioned having the DAK
reject auto-build packages would send the reject to the trashcan so
that isn't an option.
MfG
Goswin
Reply to: