On 03/27/2012 08:40 AM, Philipp Kern wrote: > Yep, we sort the packages to build by source priority. My gut feeling is that > it should be the max priority of the set of binaries it builds to keep that > feature. OTOH the uploaded source packages do have a priority. (The one in > the > source stanza is replicated into the .changes.)
I don't think the Priority field is required in the source stanza. Also we should use the values from the overrides instead of the ones in the package itself which leaves two possibilities to implement this: a, Let gps2 use max(override_priority) of *uploaded* binary packages. (Maybe also store this in the override table.) b, Add a dak command to update the priority for source overrides to max(override_priority) of binary packages listed in the Package-List field of the .dsc; fallback to "Priority: extra". With a, the Priority could change as binaries for additional architectures arrive (that do not exist for the architectures already uploaded). As b, needs to look at all source packages, it probably should only run at dinstall. Priorities for new packages would be wrong until the next dinstall run. I believe it is also a bit more complicated to implement than a,. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
