[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lintian -- detecting hundrets of bugs within seconds...

Manoj Srivastava <srivasta@datasync.com> writes:

> >>"John" == John Goerzen <jgoerzen@complete.org> writes:
> >> 3) dinstall on master runs lintian over all newly uploaded packages
> >> and rejects packages with severe errors (there will be an override
> >> mechanism to bypass certain lintian scripts)
> John> Bad.  Adds even more delay into the package upload procedure.  I
> John> vote for #1.
> 	I am disturbed by this remark.
> 	And I say we should require this ``delay'' rather than pushing
>  broken packages to the world. Doing the wrong thing really fast does
>  not generally get one anywhere good.
> 	I think that all three should be implemented; it is about time
>  we got back on track to the goal of providing an *excellent*
>  distribution, rather than a distribution of many packages of
>  questionable quality.

I think John´s right here. Because there`re a lot of maintainers who do
not have a permanent connection to the net (and especially in Germany
it is very expensive to connect via the phone). The upload should be
as short as possible. 

Instead is it possible to disconnect the lintian check from uploading?
Either the packages are silently discarded and a bug report requesting
a new upload is filed, or the packages stay in "incoming" or whatever
until the bug report is closed, in case the maintainer knows what he
does. (Sorry, as you see i don`t really know what happens on upload
yet, but soon will be --- Anyway I think this is a what it should do.)

finger jens@unsolved.weh.rwth-aachen.de for pgp-key
(during normal european business time hours) 

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: