Re: dpkg-scanpackage is ignoring newwe?
> Herbert Xu <email@example.com> writes:
> > dpkg-scanpackage just chooses the first one it sees. You can manually move
> > the old versions out before hand based on the embedded version numbers,
> > but that breaks when you've got epochs. Have a look at how apt-move handles
> > this.
On Mon, Aug 14, 2000 at 06:09:26AM +0200, firstname.lastname@example.org wrote:
> Couldn't it be changed so that the newer one will be taken (by date)
> or the versions are compared? Can't be that hard. Putting both in
> should also not make a problem, since you have the problem of multiple
> versions when using stable and unstable as well, so all relevant
> programms should cope with it.
> PS: Package pools will have a huge problem with this!
In the pool implementation at http://master.debian.org/~dld/pool/
dpkg-scanpackage isn't used. 'Packages' is generated directly from the pool
database by the packages program. Conversely, the pool database can be
generated from Packages using readpackage (after the debs/sources themselves
are uploaded to the pool using pinstall or other related programs). The
central table, pool, contains rows with references to a distribution, a deb
and an arch. potato-i386 for instance could have multiple versions of newwe
if the distribution maintainer decided that was a good idea. Sources ends
up with multiple versions if there are multiple versions between all of the
different arches as well.
dpkg-scanpackages would have a problem with pools, but not the other way