Bugzilla Patch Installation Notes

[Stefan Treacy]

Hi,

I have just performed a full install of Bugzilla, 2.18 rc2 on Linux
and now have it up and running. One of the requests for my Bugzilla
installation is to have multiple Component owners.

Bugzilla Bug 38922 provides a patch for this problem which will mean
that there will be a default CC Address List for each component.

The problem is that I do not know how to install Patches and cannot
find any documentation on the process. Please could some one point me
in the right direction as I do not seem to be able to locate any.

Any assistance will be appreciated.

Regards,

Stefan.

[Bleakcabal]

Post by Stefan Treacy
Hi,
I have just performed a full install of Bugzilla, 2.18 rc2 on Linux
and now have it up and running. One of the requests for my Bugzilla
installation is to have multiple Component owners.
Bugzilla Bug 38922 provides a patch for this problem which will mean
that there will be a default CC Address List for each component.
The problem is that I do not know how to install Patches and cannot
find any documentation on the process. Please could some one point me
in the right direction as I do not seem to be able to locate any.
Any assistance will be appreciated.
Regards,
Stefan.

I sucessfully applied another patch by looking at it, checking it and
making changes in the original file with copy and paste. Line with -
should be removed, + added and no symbol should not be changed.

[David Miller]

Post by Stefan Treacy
The problem is that I do not know how to install Patches and cannot
find any documentation on the process. Please could some one point me
in the right direction as I do not seem to be able to locate any.
Any assistance will be appreciated.

Make sure you do this first on a backup copy of your Bugzilla directory,
just to make sure it works. If it works clean with no errors, then you
can apply it to your production directory and run checksetup.pl to clean
up after it.

The "quick" way:
1) copy the URL to the patch attachment on bugzilla.mozilla.org
2) cd into your Bugzilla directory
3) lynx -source "<paste url here>" | patch -p0
4) run checksetup.pl

You can replace "lynx -source" with "curl" or "wget -O -" depending on
what command line tools you have available.

The "long" way:
1) download the patch attachment to a local file (I'll call it
"patchfile", you can call it whatever you want
2) cd into your Bugzilla directory
3) patch -p0 < /path/to/patchfile
4) run checksetup.pl

No matter which way you do it, make sure you don't get any result lines
that include the word "FAILED" in all caps in the output. If that
happens, then you'll have to go back to what Bleakcabal suggested and
apply it by hand, because the version you has changed too much since the
one the patch was made against.

The number after the -p in the patch command may need to be changed,
depending on how the patch was made. In almost all cases on
bugzilla.mozilla.org, it will be either -p0 or -p1, most will be -p0.
You can tell by looking in the patch at the lines that start with ---
and +++. If the pathname listed there starts with bugzilla/ or
bugzilla-2.18rc2/ or something that's obviously the directory containing
Bugzilla, then you'll need to use -p1. If the pathname starts with the
names of files within the bugzilla directory, then use -p0.

[Stefan Treacy]

Thanks for your assistance guys!!

I have now successfully applied the patch for bug 38922 and can now
assign default CC address for each component.

Stefan.

Post by David Miller

Post by Stefan Treacy
The problem is that I do not know how to install Patches and cannot
find any documentation on the process. Please could some one point me
in the right direction as I do not seem to be able to locate any.
Any assistance will be appreciated.

Make sure you do this first on a backup copy of your Bugzilla directory,
just to make sure it works. If it works clean with no errors, then you
can apply it to your production directory and run checksetup.pl to clean
up after it.
1) copy the URL to the patch attachment on bugzilla.mozilla.org
2) cd into your Bugzilla directory
3) lynx -source "<paste url here>" | patch -p0
4) run checksetup.pl
You can replace "lynx -source" with "curl" or "wget -O -" depending on
what command line tools you have available.
1) download the patch attachment to a local file (I'll call it
"patchfile", you can call it whatever you want
2) cd into your Bugzilla directory
3) patch -p0 < /path/to/patchfile
4) run checksetup.pl
No matter which way you do it, make sure you don't get any result lines
that include the word "FAILED" in all caps in the output. If that
happens, then you'll have to go back to what Bleakcabal suggested and
apply it by hand, because the version you has changed too much since the
one the patch was made against.
The number after the -p in the patch command may need to be changed,
depending on how the patch was made. In almost all cases on
bugzilla.mozilla.org, it will be either -p0 or -p1, most will be -p0.
You can tell by looking in the patch at the lines that start with ---
and +++. If the pathname listed there starts with bugzilla/ or
bugzilla-2.18rc2/ or something that's obviously the directory containing
Bugzilla, then you'll need to use -p1. If the pathname starts with the
names of files within the bugzilla directory, then use -p0.