Launchpad itself

Remote bug watch not working for amule

Asked by shankao

Take the bug https://bugs.launchpad.net/ubuntu/+source/amule/+bug/332180 as
an example: the remote bug (http://www.amule.org/abugs/view.php?id=1608) is
already closed, but launchpad didn't noticed.

As an indication of the problem, for that mantis bug tracker you need to be
logged in to see bug reports. Is there any way in which this can be
bypassed?

As a side note, I sent this question to the e-mail address in the launchpad's help, but then, received this response

>If you ask your question to
> https://edge.launchpad.net/malone
>Someone from the Launchpad bugs team can investigate the issue.
>
>--
>Curtis Hovey
>http://launchpad.net/~sinzui

Shouldn't the launchpad help text be changed to notice the change in helping procedure? Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
William Grant
Solved:
Last query:
Last reply:
Revision history for this message
Deryck Hodge (deryck) said : 		#1

Hi,

I've assigned this question to Graham Binns to see if he can help us here. I suspect the fact that you need to be logged in is causing issues with us detecting the remote status, but I could be completely wrong about that. Graham should respond in the next day or two when he knows something.

Cheers,
deryck

Revision history for this message
Best William Grant (wgrant) said : 		#2

If the Mantis installation requires authentication, Launchpad tries the usual guest/guest for username/password. amule's Mantis doesn't seem to accept that.

Revision history for this message
shankao (shankao) said : 		#3

Thanks William Grant, that solved my question.