Log file Viewer

[13:56:38] <redir> aclark

[13:56:43] <redir> ping

[13:59:48] <aclark> redir: pong

[14:00:24] <redir> aclark >> asked in #pone

[21:54:11] <xrogaan> jaraco: hay

[21:54:42] <xrogaan> jaraco: did you see, somebody is posting issues on the python-irclib@sf.net bug tracker

[21:55:29] <xrogaan> jaraco: you may want to migrate the whole shit on bitbucket

[21:56:43] <jaraco> xrogaan: I haven't seen on sf.net.

[21:57:07] <jaraco> I have been keeping the code live there.

[21:58:03] <xrogaan> jaraco: well, you are listed in the administrators

[21:58:35] <xrogaan> I don't know, the guy seems to have some weird issues with the lib

[21:58:53] <xrogaan> problem is: impossible to know which version he is using

[21:59:10] <jaraco> I'm reticent to take down the sf site... since I didn't set it up.

[22:00:10] <xrogaan> take down is a big word, just put a line stating that the active development changed to bitbucket. Send an email to the original authors. things like that

[22:00:39] <xrogaan> I doubt they (the olders contributors) will come again on this project

[22:00:47] <xrogaan> working on this project*

[22:00:54] <jaraco> not a good idea.

[22:01:02] <jaraco> *good idea* i mean

[22:02:32] <xrogaan> And to be very good: copy the current issues (that will probably get fixed) and put them on the bug tracker at bitbucket. But that's just luxury.

[22:05:07] <jaraco> xrogaan: thanks for the heads-up.

[22:05:45] <xrogaan> btw, I think my fix closes this one https://sourceforge.net/tracker/?func=detail&aid=3165329&group_id=38297&atid=421801

[22:06:09] <xrogaan> jaraco: don't thanks me, i'll be asking half of the money ! :p

[22:06:53] <xrogaan> here https://bitbucket.org/xrogaan/python-irclib/changeset/9710d61d58ac

[22:09:37] <jaraco> Do you have access to close that?

[22:10:17] <xrogaan> no, and I don't want the access. I can't stand the old sf.net bugtracker :)

[22:11:43] <xrogaan> don't forget to open the bitbucket bugtracker, just in case

[22:11:54] <xrogaan> or you could stay on sf.net

[22:13:48] <xrogaan> jaraco: the commit is in your repository too. I just couldn't find it right away.

[22:14:32] <xrogaan> if you look at the bitbucket fork/queue of your repository, you'll see the 'incoming' list empty.

[22:15:08] <xrogaan> I mean, upon fixing a bug, it's best to link to the master repostiory

[22:15:22] <xrogaan> reference

[22:15:38] <jaraco> agreed

[22:16:43] <xrogaan> a good set up is to use the sf.net mercurial clone as reference

[22:16:52] <xrogaan> and keep your bitbucket clone as personnal

[22:17:30] <xrogaan> but i'm not used to mercurial workflow, so I may not be the best guy giving advices :p

[22:24:02] <xrogaan> oh

[22:24:13] <xrogaan> jaraco: he is right for this one : https://sourceforge.net/tracker/?func=detail&aid=3516241&group_id=38297&atid=421801

[22:24:22] <xrogaan> you fucked up !

[22:25:08] <xrogaan> I mean, when you translated my hack into a more convenient way to do a persistant delayed call

[22:25:37] <xrogaan> https://bitbucket.org/jaraco/python-irclib/src/8373d5638cf7/lib/irclib.py#cl-403 <- the persistant is too much or you forgot to create it in the IRC class

[22:25:54] <xrogaan> > https://bitbucket.org/jaraco/python-irclib/src/8373d5638cf7/lib/irclib.py#cl-299