Re: new source package producing "old" deb's is not regarded as NEW
On Tue, Oct 04, 2005 at 07:01:07PM +0200, Frank Küster wrote:
> this week I uploaded a new source package, libkpathsea3, that produces
> existing binary packages (libkpathsea3, libkpathsea-dev). I was
> surprised to learn that this package was not subject to NEW processing,
> but rather was simply treated as any existing package.
Your observations are correct, this is indeed what happens. The override file,
which determines what packages are allowed in and what packages get in NEW for
manual review, is simply a list of allowed package names. The assumption is
here indeed that only if a totally new name comes about, it should be manually
checked. There is a list for binary package names and for source package
names, currently source packages are allowed if they occur in *either* of
those two lists.
As it happens, due to some changes in the details of the override file
handling, new source package names will soon make the package go to NEW too,
even though there already exists a binary package by that name. That the new
source package name already exists as binary package name is quite
exceptional, but in this case indeed it matters.
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)