Thanks Michal.
On Wed, 2009-03-11 at 07:29 -0700, Michu wrote: > On Feb 14 2008, 7:34 pm, Kristis Makris <[email protected]> > wrote: > > Hello Bugzilla Developers, > > > > We are experiencing a problem with Scmbug when Scmbug attempts to reuse > > the Bugzilla 3.0.3 API. It seems that checking for presence of the > > "Bugzilla.pm" package fails. > > > > The full thread of this discussion is at: > > > > http://lists.mkgnu.net/pipermail/scmbug-users/2008-February/001777.html > > > > John confirmed that this isn't due to a permissions error. His > > environment is: > > > > scmbug 0-23-4 > > bugzilla 3.0 and bugzilla 3.0.3 > > OS: Solaris 8 > > Perl 5.8.8 > > MySQL 5.0 > > > > My question to the Bugzilla developers is has a similar issue (I'm > > inclined to attribute this to Solaris) been reported before by people > > trying to use the Bugzilla API ? > > > > Incidentally, the code Scmbug uses to check for the presence of a > > package was copy-pasted from checksetup.pl:have_vers() from Bugzilla > > 2.20, which now seems to have been moved in Bugzilla 3.0 in > > Bugzilla/Install/Requirements.pm. Do you know if there are any issues > > related to have_vers on Solaris ? > > > > > >On Thu, 2008-02-14 at 10:58 -0500, John Coffie wrote: > > > > > It appears that I can get the scmbug_daemon to start if I do the > > > >following > > > > > in /proj/apps/scmbug/share/scmbug/lib/Scmbug/Common.pm: > > > > > > > sub package_exists { > > > > > : > > > > > : > > > > > }elsif ($package_name eq "Bugzilla) { > > > > > $cmd = "require Bugzilla::Bug"; > > > > > } else { > > > > > : > > > > > : > > > > > } > > > > > > > I hardcoded the package name 'Bugzilla' to 'Bugzilla::Bug'. > > > > > > > This enabled me to get past this higher level package. All subsequent > > > > > "Buzilla::XXX" packages processed fine. > > > > > > > The "Bugzilla.pm" file that is in the bugzilla installation directory > > > > > is > > > >not > > > > > found by the Common.pm package. It dies at the '( ! eval ($cmd)) > > > > > section > > > >of > > > > > 'Common.pm'. > > > > > > > Packages that work: > > > > > > > /proj/apps/bugzilla/Bugzilla/XXX.pm > > > > > > > package that doesn't work: > > > > > > > /proj/apps/bugzilla/Bugzilla.pm (this DOES exist and is the @INC when > > > > > printed to STDOUT). > > > > > > > What gives? > > > > > > > > signature.asc > > < 1KViewDownload > > > Hey there, this thread is pretty old, but still I thought I would > reply because some people may be having problems with error 79 even > now. > > We have Bugzilla 3.2.2 here and we had to lie to our Scmbug 0.26.13 > that we were using 3.0.0 to keep it from whining. > Then error 79 came up and even though we had our > `installation_directory` set correctly - it would not work. It looked > to me as some sort of a "class path" issue. > > Anyway, *here's the ugly hack we used*. > We edited the Common.pm file by adding the following line after > `require Exporter;` around line 30 of the file: > use lib "D:/Bugzilla" > and that did the trick; at least for now, because we still don't have > Scmbug fully functional. > > As you can see, we're on a Windows system (XP) and our Bugzilla is > installed in D:\Bugzilla folder, so obviously you should replace it > with your own installation path. I reckon it would work on Unix based > systems too. > > Best regards and good luck to everyone, > Michal Huniewicz
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
