[p4dti-discussion] P4DTI and Bugzilla 2.18.3
(CALL#1108491)
Stephen Vance
steve at vance.com
Wed Oct 5 17:59:24 BST 2005
Nick --
I checked permissions on defparams.pl and there are no differences.
Using the bugzilla-2.18 I downloaded from Ravenbrook, I experienced
the same problem. I installed and configured bugzilla and it worked
fine. I apply the patch, rerun checksetup.pl, and 500. I did have to
change the bugzilla root ownership. Apparently, checksetup.pl doesn't
manage that.
I am running mod_perl. I have to run to a client site, but I'll try
removing mod_perl when I get back and see if it makes a difference.
Steve
At 12:00 PM 10/5/2005, Nick Barnes wrote:
>At 2005-10-05 12:42:57+0000, Stephen Vance writes:
> > I added the call number from my existing contact with Perforce
> > Support to the subject so it will be tracked properly.
>
>Thanks.
>
> > I did not retain the shell output from applying the patch. I visually
> > inspected it and saw no errors or warnings. I was particularly
> > attentive to it because of the difference in point release. I am
> > including a newly generated patch output.
>
>Which looks OK.
>
> > The defparams.pl file is in the root of my bugzilla directory. There
> > are no .rej files in the directory tree.
>
>Good; good.
>
> > I have attached a gzip tar archive with the requested diff output,
> > defparams.pl and the patch output.
>
>All looks OK, so I'm basically mystified. Could it be the permissions
>on the defparams.pl file, caused by applying the patch? But the
>subsequent invocation of checksetup.pl should fix that.
>
>I have just attempted to reproduce this: installed Bugzilla 2.18.3
>from scratch, used it, applied the bugzilla-2.18-patch, run
>checksetup.pl, continued using the Bugzilla. No problems at all. The
>shell transcript of the patch and checksetup is below. You'll also
>see in that transcript that your post-patch defparams.pl is identical
>to mine.
>
>I'm running apache 1.3.29, but I don't see how that is going to change
>anything. Are you running mod_perl? I am not.
>
> > In the meantime, I'll try downloading vanilla 2.18. The security
> > patches don't matter to me. I'm doing an integration with the
> > Roundup defect tracker and want a working Bugzilla implementation as
> > a reference.
>
>OK. Let us know how it goes (both this problem, if you pursue it, and
>also your Roundup integration).
>
>Nick Barnes
>P4DTI Project
>Ravenbrook Limited
>
>$ cd bugzilla-2.18.3
>$ patch -p0 < ../p4dti-bugzilla-2.2.2/bugzilla-2.18-patch
>Hmm... Looks like a unified diff to me...
>The text leading up to this was:
>--------------------------
>|diff -r -u -N
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/Bugzilla/Bug.pm
>./Bugzilla/Bug.pm
>|---
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/Bugzilla/Bug.pm
>Fri Feb 4 14:12:38 2005
>|+++ ./Bugzilla/Bug.pm Fri Feb 4 14:12:28 2005
>--------------------------
>Patching file ./Bugzilla/Bug.pm using Plan A...
>Hunk #1 succeeded at 68.
>Hunk #2 succeeded at 498 with fuzz 2 (offset 7 lines).
>Hmm... The next patch looks like a unified diff to me...
>The text leading up to this was:
>--------------------------
>|diff -r -u -N
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/defparams.pl
>./defparams.pl
>|---
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/defparams.pl
>Fri Feb 4 14:12:39 2005
>|+++ ./defparams.pl Fri Feb 4 14:12:28 2005
>--------------------------
>Patching file ./defparams.pl using Plan A...
>Hunk #1 succeeded at 1191 (offset 1 line).
>Hmm... The next patch looks like a unified diff to me...
>The text leading up to this was:
>--------------------------
>|diff -r -u -N
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/doeditparams.cgi
>./doeditparams.cgi
>|---
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/doeditparams.cgi
>Fri Feb 4 14:12:39 2005
>|+++ ./doeditparams.cgi Fri Feb 4 14:12:29 2005
>--------------------------
>Patching file ./doeditparams.cgi using Plan A...
>Hunk #1 succeeded at 30.
>Hunk #2 succeeded at 49.
>Hunk #3 succeeded at 81.
>Hmm... The next patch looks like a unified diff to me...
>The text leading up to this was:
>--------------------------
>|diff -r -u -N
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/globals.pl
>./globals.pl
>|---
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/globals.pl
>Fri Feb 4 14:12:39 2005
>|+++ ./globals.pl Fri Feb 4 14:12:29 2005
>--------------------------
>Patching file ./globals.pl using Plan A...
>Hunk #1 succeeded at 1200 (offset 47 lines).
>Hmm... The next patch looks like a unified diff to me...
>The text leading up to this was:
>--------------------------
>|diff -r -u -N
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/long_list.cgi
>./long_list.cgi
>|---
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/long_list.cgi
>Fri Feb 4 14:12:40 2005
>|+++ ./long_list.cgi Fri Feb 4 14:12:29 2005
>--------------------------
>Patching file ./long_list.cgi using Plan A...
>Hunk #1 succeeded at 93.
>Hmm... The next patch looks like a unified diff to me...
>The text leading up to this was:
>--------------------------
>|diff -r -u -N
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/template/en/extension/hook/bug/comments.html.tmpl/aftercomments/p4dti.html.tmpl
>./template/en/extension/hook/bug/comments.html.tmpl/aftercomments/p4dti.html.tmpl
>|---
>/home/nb/info.ravenbrook.com/project/p4dti/import/2005-01-15/bugzilla-2.18/bugzilla-2.18/template/en/extension/hook/bug/comments.html.tmpl/aftercomments/p4dti.html.tmpl
>Thu Jan 1 01:00:00 1970
>|+++
>./template/en/extension/hook/bug/comments.html.tmpl/aftercomments/p4dti.html.tmpl
>Fri Feb 4 14:12:32 2005
>--------------------------
>(Creating file
>./template/en/extension/hook/bug/comments.html.tmpl/aftercomments/p4dti.html.tmpl...)
>Patching file
>./template/en/extension/hook/bug/comments.html.tmpl/aftercomments/p4dti.html.tmpl
>using Plan A...
>Hunk #1 succeeded at 1.
>done
>$ perl checksetup.pl
>
>Checking perl modules ...
>Checking for AppConfig (v1.52) ok: found v1.56
>Checking for CGI (v2.93) ok: found v3.04
>Checking for Data::Dumper (any) ok: found v2.102
>Checking for Date::Format (v2.21) ok: found v2.22
>Checking for DBI (v1.36) ok: found v1.48
>Checking for DBD::mysql (v2.1010) ok: found v2.9003
>Checking for File::Spec (v0.82) ok: found v0.86
>Checking for File::Temp (any) ok: found v0.12
>Checking for Template (v2.08) ok: found v2.13
>Checking for Text::Wrap (v2001.0131) ok: found v2001.0929
>
>The following Perl modules are optional:
>Checking for GD (v1.20) ok: found v2.07
>Checking for Chart::Base (v1.0) ok: found v2.3
>Checking for XML::Parser (any) ok: found v2.34
>Checking for GD::Graph (any) not found
>Checking for GD::Text::Align (any) not found
>Checking for PatchReader (v0.9.4) not found
>
>If you you want to see graphical bug reports (bar, pie and line charts of
>current data), you should install libgd and the following Perl modules:
>
>GD::Graph: perl -MCPAN -e 'install "GD::Graph"'
>GD::Text::Align: perl -MCPAN -e 'install "GD::Text::Align"'
>
>If you want to see pretty HTML views of patches, you should install the
>PatchReader module:
>PatchReader: perl -MCPAN -e 'install "PatchReader"'
>Checking user setup ...
>Removing existing compiled templates ...
>Precompiling templates ...
>Checking for MySQL Server (v3.23.41) ok: found v4.0.18
>
>Populating duplicates table...
>$ diff defparams.pl
>~/p4dti-support/steve-vance/bugzilla-2.18.3-p4dti/defparams.pl
>$ pkg_info | grep -i apache
>apache-1.3.29_3 The extremely popular Apache http server. Very
>fast, very
>mod_dav-1.0.3_2 An Apache module that provides DAV capabilities
>mod_php4-4.3.4_7,1 PHP Apache Module
>$ pkg_info | grep -i mod_php
>$
Stephen Vance
mailto:steve at vance.com
http://www.vance.com/
More information about the P4DTI-discussion
mailing list