DistroSeriesDifference can't blacklist current version

[Michael Nelson]

Currently the model for DistroSeriesDifference stores the source package name only, and evaluates the currently published versions in both the derived and parent series.

After more discussion with users, we need to be able to blacklist a specific version of the package - implying that it will be automatically removed from the blacklist once a new version is detected. With the current model we can't do this.

I assume we'll delete the source_package_name column and make source_pub and parent_source_pub db-backed attributes rather than properties (as we'd originally planned).

[Michael Nelson (michael.nelson)]

So I started the schema change as above yesterday, (adding source_pub/parent_source_pub), but soon realised that I don't think we want that amount of redundancy. We'd need to ensure at a DB level that both publications reference the same source package name, and that the publications are for the derived/parent distro series respectively etc. AFAIK, this could only be done with triggers like this:

http://pastebin.ubuntu.com/490866/

So unless I hear otherwise, I'll instead store source_version/parent_source_version so that we can remove blacklists for specific versions when they are updated (they will not be writeable outside of the DistroSeriesDifference model).

[Launchpad QA Bot (lpqabot)]

Fixed in db-stable r9780 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/9780>.