branches for deactivated projects are accessible
Bug #669750 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
When a project is deactivated by registry-admins its assets are meant to become inaccessible, but the bzr mapping doesn't take the active flag into account.
| Changed in launchpad-code: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 669750] Re: branches for deactivated projects are accessible | #1 |
| Changed in launchpad: | |
| importance: | Medium → High |
| tags: | added: easy |
To post a comment you must log in.
I'd like this to be high, because there are legal ramifications here:
we disable things we don't have the right to redistribute.
If we're not going to fix this promptly (and it should be an easy
fix), we need to update the CHR and losa docs to say 'delete all the
branches' - which would make undoing the disablement harder than
needed.