Problems linking bug w/ upstream

Jonathan Jesse jjesse at iserv.net
Fri Nov 10 17:56:55 GMT 2006


> On Fri, Nov 10, 2006 at 08:18:18AM -0600, kiko at async.com.br wrote:
>> On Thu, Nov 09, 2006 at 03:59:22PM -0500, Jonathan Jesse wrote:
>> > > There is this bug:
>> > > https://launchpad.net/distros/ubuntu/+source/keep/+bug/41356, which
>> is
>> > > also been reported here: https://bugs.kde.org/show_bug.cgi?id=122484
>> and
>> > > when I click on Upstream, I'm prompted for the package, which I
>> think is
>> > > Keep as it affects Keep's current lack of documentation, however I
>> get an
>> > > error that a package is required, even if I type in Keep, or keep.
>> I
>> > > noticed that the bug lists the fact that if effects keep as the
>> package.
>>
>> Okay, you're on the right track, but the current UI is a bit confusing
>> and it's got you stuck. Copying Bjorn since he's been working in this
>> area lately and might have an idea to make it less confusing.
>>
>> The essential trick here is that when you click on "Upstream" you are
>> /not/ being prompted for a "package", but for a "product". Packages are
>> software in a distribution (like Ubuntu); products are the original
>> upstream software. Products are registered under
>>
>>     https://launchpad.net/products
>>
>> so when you choose "keep" it correctly doesn't find the "keep" product
>> because it isn't registered in Launchpad. To register it (which you may
>> do yourself -- any user can) just hop on to
>>
>>     https://launchpad.net/products/+new
>>
>> and register it. You can also indicate in its setup that it uses the KDE
>> bug tracker so that's already sorted out, too.
>>
>> One alternative to this setup is to have a single entry point to adding
>> new tasks, without the user deciding up-front whether it's a package or
>> an upstream. That would allow us to provide more help text in the first
>> page that could help answer this common question.
>
> This would help, and there's a bug open on doing it,
> https://launchpad.net/products/malone/+bug/1334.
>
> Another thing that would help is to have a meaningful error message. If
> a product can't be found, we should explain what that means, and what
> the user can do to correct it. This is bug
> https://launchpad.net/products/malone/+bug/1922, btw.
>
> Regards,
>
> Bjorn
>
>
Thanks for the quick response.

-- 
Jonathan Jesse





More information about the launchpad-users mailing list