Greetings Kristis:
Sorry for my late response.

I was able to get Scmbug 0.26.13 to work with Bugzilla version 3.08 and
Subversion version 1.4.6. This endeavor was part of a proof of concept
project since the company I work for  is looking for a set of tools to use
for development and testing.

I do think support for Bugzilla 3.2.x would be nice given that this
version's UI is so much better than previous version.

I thank you for your help and all future correspondences from me will be
sent to this mailing list.

Thanks
Yusupha



On Tue, Feb 24, 2009 at 9:28 AM, Kristis Makris <[email protected]>wrote:

> Hi Yusupha,
>
> Please send all communication to the mailing list.
>
> Which version of Scmbug are you running ? The 'eval { }' issue has been
> resolved in version 0.26.13.
>
> Can you list the output of the daemon logs ? How do you know that the
> issue seems to be in the Bugzilla.pm code module ?
>
> problems with Bugzilla 3.2. Bugzilla 3.2 is not "supported" yet. I can't
> say if there are workarounds, if I don't know yet what the issues are.
> But I'm sure that with little effort Bugzilla 3.2 can be supported. This
> was somewhat documented in:
>
> http://bugzilla.mkgnu.net/show_bug.cgi?id=1246
>
>
>
> On Mon, 2009-02-23 at 18:15 -0700, Yusupha Jow wrote:
> > Greetings:
> > I used the link on the scmbug website to contact you via email. I've
> > posted on the site but it appears the response to my question may take
> > a while and since, I've seen your name on several boards online, I
> > thought it may be a good idea to contact you.
> >
> > I am working on a proof of concept demo to show that Bugzilla,
> > Testopia, SVN (using Scmbug) can be tied together as one system. I
> > have the latest version of Bugzilla 3.2.2 installed on Ubuntu Server
> > here. There were some issues with getting Scmbug installed on the same
> > system such as the 'eval { }' issue. But I managed to use various
> > online resources to get the Integration Daemon to start and the
> > subsequent Glue process to successfully run. Now I am using Tortoise
> > SVN to attempt to commit changes against project and bug I've
> > specifically created for this. Here is the format:
> >
> >
> > Bug 15: Blah blah blah up to 50 characters
> >
> > Upon doing this I receive the following set of messages:
> >
> >
> > Commit temp\NewTestProject\rtf.rtf temp\NewTestProject\rtf.rtf Commit
> > failed (details follow): 'pre-commit' hook failed with error output:
> > Scmbug notice:
> > --------------------------------------------------------- Scmbug
> > notice: Preparing for VERIFICATION Scmbug notice: Processing activity
> > Scmbug notice: Submitting request Scmbug notice: Request submission
> > was not replied to Scmbug ERROR>
> > Connection.pm:366:Scmbug::Connection::submit_request -
> > ******************************************* ** ** ** Scmbug error 24:
> > The daemon-spawned connection handler exited abnormally. Please check
> > the daemon error logs.
> >
> > The issue seems to be in the Bugzilla.pm code module. I understand
> > these issues may just be par for the course as far as Scmbug
> > compatibility with Bugzilla 3.2.2 is concerned. Are there workarounds
> > for this incompatibility issue or is it not advisable to try this type
> > of integration? Thanks Yus
> >
> > Thanks
> > Yusupha
> >
>
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to