[debpool] Should Allow_Version distinguish different archs?

[Magnus Holmgren]

On Saturday 19 May 2007 14:07, Magnus Holmgren wrote:
> On Tuesday 24 April 2007 14:39, Free Ekanayaka wrote:
> > Actually I didn't have binNMUs in mind, but simply binary uploads, so
> > the situation is much simpler and very common.
>
> The temporary solution I'm thinking of is to add a list of arches to the
> "meta" record in $VersionDB.

I have committed this to branches/magnus now. Please test!

The log message:
> Temporarily solve the problem that DebPool wanted every upload to have a
> greater version than the existing one, even if it is binary-only. A list of
> architectures is stored in the "meta" record of the package (in addition to
> the list of binaries). If the uploaded version is equal to the existing
> version, that list will be consulted, and the upload will only be rejected
> if the uploaded architecture is already in the archive for the package in
> question.
>
> Backwards compatibility: If the architecture list is missing, it will be
> assumed that all architectures are already uploaded (a rather dumb
> assumption, actually).
>
> Bugs: We are not tracking versions of binaries per-arch, so all binaries of
> the same name (but different archs) need to have the same version.

-- 
Magnus Holmgren        holmgren at lysator.liu.se
                       (No Cc of list mail needed, thanks)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/debpool-devel/attachments/20070519/4dd40afd/attachment.pgp