Badly named weston import

Bug #1041864 reported by Darxus on 2012-08-26

This bug report was converted into a question: question #206962: Badly named weston import.

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Unassigned

Bug Description

https://code.launchpad.net/~wayland/wayland/trunk

I requested this last night, and it was created last night. The problem is, this is an import of weston, not wayland. It should be "wayland/weston", or (I'd prefer) just "weston". It's the reference compositor for wayland.

As you can see, it's importing:

git://anongit.freedesktop.org/wayland/weston
git://anongit.freedesktop.org/wayland/wayland <- while this is the location of wayland

Max Bowsher (maxb) wrote :

There are two possibilities:

1) Use the "Change branch details" link (right hand column) on https://code.launchpad.net/~wayland/wayland/trunk to change "trunk" to "weston".

2) Delete the import, register "weston" as a project in Launchpad in its own right, and recreate the import in the context of that project.

Max Bowsher (maxb) wrote :

This a request for help using Launchpad, rather than a bug or a feature request, so I'm converting it to a question.

Changed in launchpad:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions