Re: Checking new packages (Re: Status of Potato)
Chris Leishman <email@example.com> writes:
> On Sat, Nov 06, 1999 at 12:27:52PM +0900, Changwoo Ryu wrote:
> > > a) make sure that packages are uploaded correctly (ie, all files are present
> > > and complete) before they get installed into the tree.
> > > b) the maintainer signature is correct.
> > >
> > >
> > > I'm sure there are other advantages to the system as well (that I just don't
> > > know about).
> > a) and b) are automatically done by dinstall. AFAIK, new packages are
> > checked by human beings for (1) DFSG compliance and (2) the correct
> > section.
> > But I don't see why these two checks are needed. The checks are not
> > complete anyway; we often see license-related grave bugs filed. New
> > package upload could be disabled at freezing time, but I don't
> > understand why this bottleneck exists at the development dist.
> But these first two steps still require a place to upload to, so that dinstall
> can run through them, do the checks and if they pass put them in the
> distribution tree. Hence we need an incoming directory - rather than just
> installing straight into the distribution tree.
I, of course, don't insist that we don't need the incoming directory
at all. It's about the new package checks by the dinstall
administrator(s). I'm sure Sami Dalouche had the same intent.