RE: Problem applying custom fields patch (bugID 91037) to bugzill a 2.18.2 and 2.18.3

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

RE: Problem applying custom fields patch (bugID 91037) to bugzill a 2.18.2 and 2.18.3

Tom Maddox
RE: Problem applying custom fields patch (bugID 91037) to bugzilla 2.18.2 and 2.18.3

Hi, Anna,

The most recent custom fields patch is for 2.18, so it's bound to have some incompatibilities with subsequent releases.  It looks like you have a couple of problems, one with buglist.cgi and one with Bug.pm.  For the buglist.cgi problem, you'll probably have to compare the rejected hunk with the patched file and see if you can figure out where that hunk is supposed to go, if anywhere.  If there's nothing obvious, you might wind up having to rewrite it for the new version.

For Bug.pm, it looks like the correct approach is to run "patch -p1" from within the top-level Bugzilla directory.

Now, having said that, my advice is to not use the custom fields patch at all.  I've implemented it at my site, and I wish I hadn't.  It meets certain basic requirements for providing custom fields, but it doesn't interface with Bugzilla's reporting features, nor does it work well with SSL, just as a couple of examples.

Good luck!

Tom

> -----Original Message-----
> From: [hidden email]
> [[hidden email]] On Behalf Of Anna Flynn
> Sent: Monday, July 25, 2005 3:29 PM
> To: [hidden email]
> Subject: Problem applying custom fields patch (bugID 91037)
> to bugzilla 2.18.2 and 2.18.3
>
> I'm clumsy/new with/to this perl and patching, so please
> excuse if 'problem exists between keyboard and chair'.  I
> want to use bugzilla but I need the custom fields patch.  I
> downloaded bugzilla 2.18.3 and tried applying the patch
> (perhaps incorrectly) and received some errors, so thinking
> that the custom fields patch might not be OK w/2.18.3, I
> downloaded and made a fresh install of bugzilla 2.18.2 and
> tried to apply the patch.  I received the same errors, so
> 'pebkac' is likely a factor.  Help/advice would be greatly
> appreciated.  What happened is pasted below.
>
> Thanks very much in advance!
>
> -Anna
>
> ====== what happened: ==================== $ patch <
> 2[1]_18_customfields2_patch (Stripping trailing CRs from
> patch.) patching file addcustomfield.pl (Stripping trailing
> CRs from patch.) patching file buglist.cgi Hunk #2 FAILED at 76.
> Hunk #3 succeeded at 486 with fuzz 2.
> Hunk #6 succeeded at 704 (offset -1 lines).
> Hunk #7 succeeded at 736 (offset -1 lines).
> Hunk #8 FAILED at 759.
> Hunk #9 succeeded at 783 with fuzz 1.
> Hunk #10 succeeded at 855 with fuzz 2.
> 2 out of 10 hunks FAILED -- saving rejects to file
> buglist.cgi.rej (Stripping trailing CRs from patch.) can't
> find file to patch at input line 231 Perhaps you should have
> used the -p or --strip option?
> The text leading up to this was:
> --------------------------
> |diff -Naur bugzilla_2.18/Bugzilla/Bug.pm
> bugzilla_2.18_cf/Bugzilla/Bug.pm
> |--- bugzilla_2.18/Bugzilla/Bug.pm      2005-03-18
> 10:41:31.000000000 +0000
> |+++ bugzilla_2.18_cf/Bugzilla/Bug.pm   2005-03-18
> 10:40:52.000000000 +0000
> --------------------------
> File to patch:
> ======= the end ======================
>
>
> _______________________________________________
> mozilla-webtools mailing list
> [hidden email]
> http://mail.mozilla.org/listinfo/mozilla-webtools
>