oops trying to create a code import if branch policy produces a private branch
Bug #380271 reported by
Diogo Matsubara
This bug report is a duplicate of:
Bug #268682: Trying to import a branch to a project which you're not allowed to crashes.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Tim Penhey |
Bug Description
Steps to reproduce:
1. Open https:/
2. Enter oops-tools in the project field
3. Enter a random git repository (e.g. git://github.
4. Click request import
5. OOPS-1241S110 BranchCreationF
This might be a dupe of bug 268682
tags: | added: code-import oops |
Changed in launchpad-code: | |
importance: | Undecided → High |
milestone: | none → 2.2.5 |
status: | New → Triaged |
importance: | High → Critical |
Changed in launchpad-code: | |
assignee: | nobody → Jonathan Lange (jml) |
Changed in launchpad-code: | |
assignee: | Jonathan Lange (jml) → Tim Penhey (thumper) |
To post a comment you must log in.
So it turns out that the problem is caused by the code import creation code passing the ~vcs-imports team as the registrant of the branch (which is bogus: the registrant should always be a person), and ~vcs-imports doesn't have the right to create a branch in the project Diogo was trying.
Hance, reduce importance, bump to next milestone.