Project: additional git imports fail from the "Code" page

[Matteo Nastasi (mop)]

In a project page:
if I move to "Code" tab with an already imported Git To Git repository
I click "Configure code"
And I want to add a new mirrored repository using "Import a Git repository hosted somewhere else" form part CHANGING the "Git repository name" instead to do what I expected (like when you use "https://code.launchpad.net/+code-imports/+new" page)
the new imported repository substitute the original (without using the "Git repository name" passed and rename the old with the same name but with ~$user/$project/+git/$project_again

Hope is clear enough.

Using the "https://code.launchpad.net/+code-imports/+new" all works as expected.

Regards, Matteo.

[Colin Watson (cjwatson)]

I'm afraid I'm not following this at all. Could you give us:

 * exactly which URL you were on when you filled out the form
 * the exact contents of all form inputs
 * any error messages you received

? Thanks.

[Matteo Nastasi (mop) (nastasi)]

I try again:
  - create a new project <prj_name> and create a primary git repository using "git Import a Git repository hosted somewhere else" in the "https://code.launchpad.net/<prj_name>/+configure-code" page
  - after that go again in "https://code.launchpad.net/<prj_name>" and click "Configure Code"
  - landing here: "https://code.launchpad.net/<prj_name>/+configure-code"
  - now use again "git Import a Git repository hosted somewhere else" and setting a different "Git repository name:" and importing another repository
  - at this point take a look at "https://code.launchpad.net/<prj_name>"

I'm sorry but the repository now is working using the alternative approach ;).

Regards, Matteo.

[Colin Watson (cjwatson)]

I tried this on one of our staging sites and I'm not seeing the problem. What happened after you followed that procedure? Did you get an error message, or was some incorrect data displayed, or what?

[Colin Watson (cjwatson)]

Feel free to try this out on qastaging.launchpad.net, incidentally; I'd encourage you to do so in order to produce a clearer bug report so that we can understand the problem. The actual code import won't work there so branches won't be created, but everything else should work fine.

[Matteo Nastasi (mop) (nastasi)]

About #3: the latest uploadedrepository became the "project" repository and the first repo uploaded became "another" repository with the same name of the project.

I will try it tomorrow, thank you for the patience.

[Colin Watson (cjwatson)]

Oh. That's exactly what it's expected to do. The point of the "Configure Code" form is to configure what Launchpad regards as the default branch/repository of the project. It is intentional that specifying a different branch/repository causes that to be regarded as the new default. If that's the only issue here, then I'd say that it's not a bug, unless perhaps there's some way we can make things clearer.

[Matteo Nastasi (mop) (nastasi)]

If it is the case the normal workflow like "<package>" + "<package>-debian-files" repositories in a single project needs the "magic" page "https://code.launchpad.net/+code-imports/+new" to be accomplished that is never linked and/or explained in the project page.

AND: if expliciting a "Git repository name:" I expect to found this name somewhere.

Regards and thank you for the clarification, Matteo.