Deleting recipe leaves SourcePackageReleases with no traceability

[William Grant]

devel r11598 makes SourcePackageRecipe deletion nullify references on its SourcePackageReleases. This leaves us with a SourcePackageRelease for which we cannot determine an uploader. We really need to know who to blame.

[Tim Penhey (thumper)]

On Thu, 23 Sep 2010 10:23:45 you wrote:
> Public bug reported:
>
> devel r11598 makes SourcePackageRecipe deletion nullify references on
> its SourcePackageReleases. This leaves us with a SourcePackageRelease
> for which we cannot determine an uploader. We really need to know who to
> blame.
>
> ** Affects: launchpad-code
> Importance: Undecided
> Status: New

  importance high
  status triaged
  tag recipe

[Tim Penhey (thumper)]

What other ways can we have the traceability without keeping the recipe around? Where could we tag the build with useful information?

[William Grant (wgrant)]

You can't tag the build, since that's what you're inappropriately deleting. If you want to delete all sorts of important stuff, you will need to add some new field to store this information.

Also, this bug is not Incomplete. All the information about the problem is here, we just need to work out a solution.

[Aaron Bentley (abentley)]

Our current idea is to make the recipe column on SourcePackageRecipeBuild nullable and change recipe deletion to null that field instead of deleting the build record. Since source package recipe build URLs include their recipe, this will make them unreachable from the web UI and web service, but they'll be in the database if you really need them. Sound good?

[Launchpad QA Bot (lpqabot)]

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