git repository rename into an existing package fails if this repository was "owner default" even if you turn that flag off in the rename
Bug #1730646 reported by
Andy Whitcroft
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I had a pre-existing git repository lp:~canonical-kernel/ubuntu/+source/linux-aws-trusty/+git/linux-aws-trusty which was marked "owner default". As this was actually a repository for the linux-aws package I wanted to rename this into that package. Using the +edit page I changed its name to trusty, the package to aws-trusty, and turned off "owner default". On saving the rename was rejected because there was already an "owner default" in the new package. Turning off the "owner default" flag as a separate action allowed the rename to succeed.
| summary: |
- git repository rename into an + git repository rename into an existing package fails if this repository + was "owner default" even if you turn that flag off in the rename |
Revision history for this message
| Andy Whitcroft (apw) wrote | #1 |
Revision history for this message
| Haw Loeung (hloeung) wrote | #2 |
| Changed in launchpad: | |
| status: | New → Confirmed |
To post a comment you must log in.
This is the exact error I get on a second package I am renaming:
"Canonical Kernel's default repository for 'linux-meta-aws in Ubuntu' is already set to ~canonical-