On Sun, Dec 13, 2009 at 06:32:56PM -0800, Don Armstrong wrote:
> There have always been possible to have several versions of the same
> binary package in the same suite (for different architectures) so this
> shouldn't come as a shock to anyone.
But in this case the different versions of one package end up in
different package files because they are for different architectures.
At least for the packages files you should have a unique entry
<package name> - <version> per architecture (in the sense of a
primary key in a database like UDD
"packages_pkey" PRIIMARY KEY
(package, version, architecture, distribution, release, component)
If this "key constraint" is violated in the packages file I have
no idea how parsers should guess "the right" entry.
Kind regards
Andreas.
Disclaimer: I havn't checked whether this is really the case just
trusting the investigation of Lucas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
