Launchpad itself

Should not be able to flip privacy if any PackageUploads reference the archive

Bug #806273 reported by Steve Kowalik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

If a PackageUpload for an archive exists, the privacy setting should be disallowed by the UI and the API.

Tags: p3a privacy
Steve Kowalik (stevenk)
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Steve, can you add more details here. I know it came from a production issue, perhaps describing that in more detail will help anyone fixing this. Thanks.

Curtis Hovey (sinzui)
tags: added: p3a privacy
Revision history for this message
Julian Edwards (julian-edwards) wrote :

This bug is still lacking on enough detail to explain the problem

Changed in launchpad:
status: Triaged → Incomplete
Revision history for this message
Steve Kowalik (stevenk) wrote :

This bug was caused by a direct copy and a delayed copy being done at roughly the same time as the privacy of the archive was changed from public to private. The PackageUpload then causes process-accepted to OOPS.

This bug can be fixed in one of two ways:

1) Delete delayed copies.
2) Check for any unprocessed PackageUploads and denying the change to private if any exist.

Changed in launchpad:
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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