Series initialization might end up as a partially initialised series

Bug #801112 reported by Raphaël Badin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Series initialization uses the packagecopier which works in an atomic way, so it might deny the copy of all the sources because of a simple conflict with one source. This might lead to a partially initialised series which we currently have no way to recover from.

Tags: derivation
description: updated
Changed in launchpad:
importance: Undecided → Low
Revision history for this message
Julian Edwards (julian-edwards) wrote :

This is part of a bigger problem where we have the choice of
a) a long transaction that allows us to atomically roll back in case of errors (and we know long transactions are bad)
b) many short transactions but a partially initialised series

In the case of (b) we have a lot of code that will break when a series is partially initialised. It needs to be tracked down and fixed to use a new boolean on the Distroseries table. For example, many places use IArchive.getPublishedSources() to see if the series has got packages in it.

Changed in launchpad:
importance: Low → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Moving to low priority since the transaction times will probably be small for most ops.

Changed in launchpad:
importance: High → Low
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.