Whoops, forgot to send to the list.

---------- Forwarded message ----------
From: Kristis Makris <[email protected]>
Date: Tue, Sep 15, 2009 at 2:21 PM
Subject: Re: [scmbug-users] Scmbug with Bugzilla 3.4.1 - status changing
To: Robert G Ward <[email protected]>


Hi Robert,

What I can recommend is that you look at:

http://bugzilla.mkgnu.net/show_bug.cgi?id=1246
http://bugzilla.mkgnu.net/show_bug.cgi?id=1422

Some patches for supporting Bugzilla 3.2 and 3.4 have been proposed,
and I believe one of those handles status changes.

On Mon, Sep 14, 2009 at 2:53 AM, Robert G Ward
<[email protected]> wrote:
>
> I have upgraded my bugzilla to 3.4.1, not realising what an impact this was 
> going to have on ScmBug!  We are using ScmBug 0.26.15.

Aii canary.

>
> Firstly, the change status stuff was failing with the following message 
> because that function bz_lock_tables does not appear in the Bugzilla 3.4.1 
> code base.
>
>
>
> 2009/09/11 18:02:52 Scmbug ERROR> 
> Bugzilla.pm:714:Scmbug::Daemon::Bugzilla::integration_change_bug_resolution - 
> Can't locate object method "bz_lock_tables" via package "Bugzilla::DB::Mysql" 
> at /usr/share/scmbug/lib/Scmbug/Daemon/Bugzilla.pm line 714, <STDIN> line 34.
>
>
>
> As a heinous hack, I commented out the lock and unlock function calls.  
> However, even though the checkin now works successfully, the status change is 
> not applied.
>
>
>
> 1.       Has anyone else tried this with bugzilla version 3.4.1 (or am I the 
> first?)

Thanks for the feedback.
>
> 2.       Any suggestions of what I can try?
>
>
>
> On a similar note, does anyone have a suggestion of how to write ‘debug’ 
> messages into the code to write to the Scmbug logfile, so that I can diagnose 
> what is happening?  ‘print’ to console does not really work in this situation.

You can use the log_daemon_debug() call to add debugging code in
general. But, apparrently, this functionality is not available in the
individual backends, like Bugzilla.pm, or at least there wasn't an
attempt to support it there yet.

Worst case scenario:

open SOMEFILE, ">> /tmp/somefile";
print SOMEFILE Dumper ( $some_variable);
close SOMEFILE;
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to