Pidgin Trac should now be running the Launchpad Trac plugin

Asked by Richard Laager

I followed the instructions to install the Launchpad Trac plugin on developer.pidgin.im, but I didn't know how to test it. I figured we'd find out anyway once you went to do the setup on your side. Please let me know if there is more I need to do. Thanks, Richard

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
Graham Binns Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Graham Binns (gmb) said :
#1

Hi Richard,

Thanks for installing the plugin on your Trac instance. What's the URL of the instance on which you've installed it? Once we've got that we'll be able to complete any setup work needed on our side (which should be minimal).

Cheers,

Graham

Revision history for this message
Graham Binns (gmb) said :
#2

My last message should have been an information request, not an answer.

Revision history for this message
Richard Laager (rlaager) said :
#3

As I mentioned in the message... ;)
http://developer.pidgin.im

Revision history for this message
Graham Binns (gmb) said :
#4

On 26/01/09 13:14, Richard Laager wrote:
> Question #58753 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/58753
>
> Status: Needs information => Open
>
> Richard Laager gave more information on the question:
> As I mentioned in the message... ;)
> http://developer.pidgin.im
>

Whoops, sorry. I guess it helps if you read message properly ;). I'll
get that sorted out this afternoon.

Many thanks again.

Revision history for this message
Richard Laager (rlaager) said :
#5

Any news here? Is this supposed to be done? I'm not seeing any bug numbers on our end.

Revision history for this message
Graham Binns (gmb) said :
#6

2009/1/29 Richard Laager <email address hidden>:
> Question #58753 on Launchpad Bugs changed:
> https://answers.launchpad.net/malone/+question/58753
>
> Status: Answered => Open
>
> Richard Laager is still having a problem:
> Any news here? Is this supposed to be done? I'm not seeing any bug
> numbers on our end.

Sorry, yes; it should all be done. It might be that our bug watch
checking process is a bit behind (thanks to
http://launchpad.net/bugs/300634).

I'll ask our sysadmins to run the process manually against the Pidgin
Trac so that we can make sure everything's working. Thanks for the
heads-up.

Revision history for this message
Graham Binns (gmb) said :
#7

For some reason the Pidgin bug watches don't seem to be getting
updated (we're checking them but for some reason bug statuses aren't
being imported). I'll look into this further tomorrow and get back to
you.

Revision history for this message
Richard Laager (rlaager) said :
#8

Any news? (On a side note, oddly, I'm not receiving any email from this item. Perhaps it's being blocked on my end or something.)

Revision history for this message
Graham Binns (gmb) said :
#9

> Richard Laager is still having a problem:
> Any news?

I'm still working on trying to fix the bug. Rest assured though, the
problem is on our end, not yours.

Sorry that this is taking so long to sort out. Our process for
updating bug watches is rather involved; unpicking the algorithm to
make it do the right thing is proving complex :).

> (On a side note, oddly, I'm not receiving any email from this
> item. Perhaps it's being blocked on my end or something.)

I've seen that problem myself this week, so I suspect it isn't just
you. I'll investigate further.

Revision history for this message
Richard Laager (rlaager) said :
#10

Ok. I *did* receive the email for that comment.

Revision history for this message
Richard Laager (rlaager) said :
#11

I didn't mean to mark this as answered.

Revision history for this message
Richard Laager (rlaager) said :
#12

Any news?

Revision history for this message
Graham Binns (gmb) said :
#13

No, bug 300634 hasn't yet been fixed. Looking at the logs over time, though (because Launchpad has been trying to pull in bugs from the Pidgin Trac occasionally) it appears that some runs are failing due to bug 301676, which we'd previously thought was an intermittent problem only.

To get further updates on this you can subscribe to

 * http://launchpad.net/bugs/300634
 * http://launchpad.net/bugs/301676

To get updates as those bugs are fixed.

Revision history for this message
Graham Binns (gmb) said :
#14

Hi Richard,

Tim Hatch has fixed bug 301676 today. Can you install the latest version of the Trac LP plugin on the Pidgin Trac please: http://edge.launchpad.net/trac-launchpad/trunk/0.1.2/+download/trac-launchpad-0.1.2-2.tar.gz?

Once that's in place synchronisation should start to behave more normally.

Revision history for this message
Richard Laager (rlaager) said :
#15

https://bugs.launchpad.net/trac-launchpad/+bug/301676/comments/6 says:
> Based on the two bugs listed on Pidgin with the launchpad bug field set

This was one of the questions I had about this Trac plugin... Do we need to manually enter the Launchpad bug ID in Pidgin Trac for each bug that's linked in Launchpad?

Revision history for this message
Richard Laager (rlaager) said :
#16

I've upgraded the plugin to 0.1.2-2.

Revision history for this message
Graham Binns (gmb) said :
#17

2009/2/18 Richard Laager <email address hidden>:
> This was one of the questions I had about this Trac plugin... Do we need
> to manually enter the Launchpad bug ID in Pidgin Trac for each bug
> that's linked in Launchpad?

No. Now that it's working properly Launchpad will do that for you
using the plugin's API.

Revision history for this message
Richard Laager (rlaager) said :
#18

The plugin didn't seem to automatically link the existing bugs. Is that expected? I've uninstalled it for now.

Revision history for this message
Graham Binns (gmb) said :
#19

On Wed, Apr 01, 2009 at 11:19:08AM -0000, Richard Laager wrote:
> Question #58753 on Launchpad Bugs changed:
> https://answers.launchpad.net/malone/+question/58753
>
> Status: Answered => Open
>
> Richard Laager is still having a problem:
> The plugin didn't seem to automatically link the existing bugs. Is that
> expected? I've uninstalled it for now.

The plugin simply adds an API to Trac. If things aren't getting linked
then it's possible that Launchpad is doing something wrong or that
there's something wrong with the plugin.

There has recently been a new release of the plugin [1] which solved a
problem that might well have caused bugs not to be linked properly. It
might be worth trying that. If that still doesn't work then we can
investigate further.

 [1] https://edge.launchpad.net/trac-launchpad/+download

Can you help with this problem?

Provide an answer of your own, or ask Richard Laager for more information if necessary.

To post a message you must log in.