fix branches damaged by non-preservation of git.db files

Bug #398722 reported by Michael Hudson-Doyle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Michael Hudson-Doyle

Bug Description

This is more of a task than a defect.

A bunch of git imports failed (after a successful initial import) for reasons that can be ameliorated by preserving the git.db file.

We now preserve this file, but the existing imports don't have one. The easiest way to fix them is to delete the branch data we have for these imports currently.

I'll work with Steve tomorrow to get this done.

Tags: lp-code
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I think this is all done now, but we need to verify the fix for samba.

(That import takes a while!)

Changed in launchpad-code:
status: Triaged → In Progress
Changed in launchpad-code:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.