Hi, Error message says what to tweak (I usually try with -p0, -p1, -p2, ... until it succeeds. Another approach is to just check patch headers to see the relevant directory nesting). In our particular case: # cd /usr/share/scmbug # patch -p2 < scmbug-customization-0.26.22.patch
Regards, Yavor On Tue, Feb 22, 2011 at 13:07, Ramchander Namani <[email protected]>wrote: > You may send me your scmbug-server's > /usr/share/scmbug/lib/Scmbug/Daemon/Bugzilla.pm that works for Bugzilla 4 > (Feb 2011) file instead of all these patches. :) > > Thanks, > Ramchander. > > > On Tue, Feb 22, 2011 at 4:28 PM, Ramchander Namani <[email protected] > > wrote: > >> Hi Yavor, >> >> Could you please help as to where I am wrong. I got the following errors: >> >> [ramchander@ab01 share]$ sudo patch < >> bugzilla4_p1_version_number_support.patch >> can't find file to patch at input line 4 >> Perhaps you should have used the -p or --strip option? >> The text leading up to this was: >> -------------------------- >> |=== modified file 'scmbug/lib/Scmbug/Daemon/Bugzilla.pm' >> |--- scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-07-23 20:45:06 +0000 >> |+++ scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 20:00:53 +0000 >> -------------------------- >> File to patch: scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> patching file scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> Hunk #1 FAILED at 59. >> Hunk #2 succeeded at 497 with fuzz 2 (offset -97 lines). >> 1 out of 2 hunks FAILED -- saving rejects to file >> scmbug/lib/Scmbug/Daemon/Bugzilla.pm.rej >> >> >> [ramchander@ab01 share]$ sudo patch < >> bugzilla4_p2_version_status_change.patch >> can't find file to patch at input line 4 >> Perhaps you should have used the -p or --strip option? >> The text leading up to this was: >> -------------------------- >> |=== modified file 'scmbug/lib/Scmbug/Daemon/Bugzilla.pm' >> |--- scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 20:00:53 +0000 >> |+++ scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 20:19:39 +0000 >> -------------------------- >> File to patch: scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> patching file scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> Hunk #2 succeeded at 443 (offset -98 lines). >> Hunk #3 succeeded at 942 with fuzz 2 (offset 29 lines). >> Hunk #4 succeeded at 831 with fuzz 1 (offset -95 lines). >> Hunk #5 succeeded at 1008 (offset 44 lines). >> >> >> [ramchander@ab01 share]$ sudo patch < >> bugzilla4_p3_email_notification.patch >> can't find file to patch at input line 4 >> Perhaps you should have used the -p or --strip option? >> The text leading up to this was: >> -------------------------- >> |=== modified file 'scmbug/lib/Scmbug/Daemon/Bugzilla.pm' >> |--- scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 20:19:39 +0000 >> |+++ scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 20:24:18 +0000 >> -------------------------- >> File to patch: scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> patching file scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> Hunk #1 FAILED at 1779. >> 1 out of 1 hunk FAILED -- saving rejects to file >> scmbug/lib/Scmbug/Daemon/Bugzilla.pm.rej >> >> >> [ramchander@ab01 share]$ sudo patch < bugzilla4_p4_version_tagging.patch >> can't find file to patch at input line 4 >> Perhaps you should have used the -p or --strip option? >> The text leading up to this was: >> -------------------------- >> |=== modified file 'scmbug/lib/Scmbug/Daemon/Bugzilla.pm' >> |--- scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 20:24:18 +0000 >> |+++ scmbug/lib/Scmbug/Daemon/Bugzilla.pm 2010-11-11 21:35:44 +0000 >> -------------------------- >> File to patch: scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> patching file scmbug/lib/Scmbug/Daemon/Bugzilla.pm >> Hunk #1 FAILED at 1351. >> 1 out of 1 hunk FAILED -- saving rejects to file >> scmbug/lib/Scmbug/Daemon/Bugzilla.pm.rej >> >> And now I get the following error after starting scmbug-daemon init >> script. >> >> [ramchander@ab01 share]$ sudo /etc/init.d/scmbug-server start >> Starting SCM to bug-tracking integration daemon: scmbug_daemonGlobal >> symbol "$VERSION_4_0_0" requires explicit package name at >> /usr/share/scmbug/lib/Scmbug/Daemon/Bugzilla.pm line 863. >> Global symbol "$VERSION_4_0_0" requires explicit package name at >> /usr/share/scmbug/lib/Scmbug/Daemon/Bugzilla.pm line 917. >> Compilation failed in require at >> /usr/share/scmbug/lib/Scmbug/Daemon/Daemon.pm line 22. >> BEGIN failed--compilation aborted at >> /usr/share/scmbug/lib/Scmbug/Daemon/Daemon.pm line 22. >> Compilation failed in require at /usr/sbin/scmbug_daemon.pl line 25. >> BEGIN failed--compilation aborted at /usr/sbin/scmbug_daemon.pl line 25. >> . >> >> Much thank you for helping. I am sure you are the only person who can help >> me right now. >> >> Thanks, >> Ramchander. >> >> On Tue, Feb 22, 2011 at 4:13 PM, Yavor Nikolov >> <[email protected]>wrote: >> >>> Hi, >>> >>> So here is my patch (applied successfully on top of scmbug 0.26.22 and >>> I'm using Bugzilla 4.0 final) >>> >>> The new options in /etc/scmbug/daemon.conf which are expected (in >>> bugtracker section) are: >>> # Email notification >>> notification_enabled => 1, >>> >>> # Changer notification (email) >>> changer_notification_enabled => 1 >>> >>> --- --- >>> - If you don't need this e-mail notification stuff - you can just set >>> those flags to 0. >>> - Actually there is another way to implement e-mail notifications with >>> Bugzilla 4.0 but I'm still using my old patch since it allows me to also >>> notify changer (when you commit, you'll get an e-mail too). >>> >>> Regards, >>> Yavor >>> >>> >>> On Tue, Feb 22, 2011 at 12:41, Ramchander Namani <[email protected] >>> > wrote: >>> >>>> Hi Yavor, >>>> >>>> Many thanks for promptly helping. Awaiting eagerly for your new diff. :) >>>> >>>> Thank You, >>>> Ramchander. >>>> >>>> >>>> On Tue, Feb 22, 2011 at 4:04 PM, Yavor Nikolov <[email protected] >>>> > wrote: >>>> >>>>> Maybe the problem is that my patches are on top of scmbug which has >>>>> already been patched before the migration to bugzilla 4.0. >>>>> >>>>> It's not much different from original scmbug from functional point of >>>>> view: >>>>> - I'm just handling version compatibility checks in a bit different >>>>> way so that I can easier migrate when new Bugzilla versions are released >>>>> /Kristis was not convinced that my approach is worth moving upstream to >>>>> official scmbug/. (Sorry I haven't provided clean patches against official >>>>> scmbug). >>>>> - I have added additional configuration parameters to enable e-maling >>>>> from Bugzilla on bug change. >>>>> >>>>> I'll send a full diff my version vs scmbug 0.26.22. >>>>> >>>>> Regards, >>>>> Yavor >>>>> >>>>> >>>>> On Tue, Feb 22, 2011 at 12:18, Ramchander Namani < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Kristis Makris / Yavor, >>>>>> >>>>>> Thanks for providing information about Bugzilla 4 Subversion >>>>>> integration upgrade in SCMBUG (Bugzilla >>>>>> Ticket<http://bugzilla.mkgnu.net/show_bug.cgi?id=1498> >>>>>> ). >>>>>> >>>>>> Actual Results: >>>>>> =============== >>>>>> >>>>>> I did the following but no luck in integrating Bugzilla 4 with >>>>>> Subversion: >>>>>> >>>>>> 1) Apply the 4 patches given in this ticket but >>>>>> /usr/share/scmbug/lib/Scmbug/Daemon/Bugzilla.pm of >>>>>> scmbug-server-0.26.21-1 >>>>>> seems to be entirely different from the one you have used in the patch. >>>>>> >>>>>> 2) I also tried scmbug-server-0.26.22 but no luck with Bugzilla 4 >>>>>> integration. >>>>>> >>>>>> Expected Results: >>>>>> ================ >>>>>> >>>>>> 1) /etc/init.d/scmbug-server should run fine without any issues in >>>>>> /var/log/scmbug/activity.log >>>>>> >>>>>> >>>>>> Environment: >>>>>> >>>>>> I am using scmbug-server-0.26.21-1. >>>>>> >>>>>> Error message in /var/log/scmbug/activity.log >>>>>> -------------------------------------------- >>>>>> >>>>>> ** Scmbug error 79: Unsupported version '4.0.0'. This could be because >>>>>> this version was never tested. If you use a different version number and >>>>>> manage to get the integration working correctly please notify ' >>>>>> [email protected]'. >>>>>> Initialization of bug-tracking system 'Bugzilla' version '4.0.0' >>>>>> failed. This could be due to an unsupported version of this system, or >>>>>> misconfiguration. >>>>>> >>>>>> >>>>>> Could you please help in this regard as to how I should apply these >>>>>> patches to Bugzilla.pm. It looks like I need new patches for the current >>>>>> release of Bugzilla 4 released in Feb 2011. >>>>>> >>>>>> Thank you very much for reading this. >>>>>> Waiting for any kind of inputs from you. >>>>>> Ramchander. >>>>>> >>>>> >>>>> >>>> >>> >> >
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
