9 More Discussions You Might Find Interesting
1. Solaris
I am trying to determine the date of the last patch on a Solaris machine. I know that I can get the last patch name with the uname -a command but that does give me any date info. Any ideas? (1 Reply)
Discussion started by: tdriley29
1 Replies
2. AIX
Hi all,
I am exploring how I can automate the download and patching of my AIX servers via a central management mechanism.
I will need to patch all my servers annually to a certain pre-determined Service Pack (SP) level.
So far I performed some online search and found 2 products that might... (6 Replies)
Discussion started by: pawpaw
6 Replies
3. UNIX for Advanced & Expert Users
Hi
I have a set of source files for the dwim utility, in the directory /usr/local/src/dwim-1.0.
I have a patch for adding an enhancement to dwim. The top line of the patch reads
diff -rc dwim-1.0-vanilla/Makefile dwim-1.0-raspberry-ripple/Makefile
Which commands should I use for applying the... (1 Reply)
Discussion started by: scofiled83
1 Replies
4. Solaris
Hello...
I'm looking for latest patch for automount and what it does on Solaris8, Thanks! :confused: (2 Replies)
Discussion started by: catwomen
2 Replies
5. Solaris
Can we get a script to find out a perticular patch installed on solaris 8, 9. (1 Reply)
Discussion started by: ddk2oo5
1 Replies
6. UNIX for Dummies Questions & Answers
Dear All ,
I have Sun Solaries 7 sparc server ... am runing perl , CGI , MD5 ... etc for new web mail am setting up .
now i have to install the patch ( xyz.pl.patch ) against a perl file for ex. xxx.pl
what exact command i have to use ,,, also i do not want to make damage for my system... (6 Replies)
Discussion started by: tamemi
6 Replies
7. Shell Programming and Scripting
Dear Guys ,
I use Linux Red Hat 9 ..
i installed a patch for a web mail i use , and i think it make a damage for my web mail i cannot see it anymore .
i get so many error messages .
what i want to ask is there any command on linux i can use to remove the patch !!!
i want to remove the... (1 Reply)
Discussion started by: tamemi
1 Replies
8. HP-UX
Hello,
I have to apply the patch PHSS_24302 on HPUX B.11.11 os version. When i look at the /var/adm/sw/swagentd.log it mentions that "this is not a valid depot". I downloaded the patch from HP web site. Please get back to me at the earliest as I'm dead in the water. Thanks,
Balaji K (3 Replies)
Discussion started by: bkrish
3 Replies
9. UNIX for Advanced & Expert Users
Is there a way to find out if a patch has been applied? I'm running Solaris 2.6 on an Ultra Sparc machine. Our UNIX System Admin has left the company and unfortunately for the time being I'm the man. I need to know if he installed Kernel patch 103640-05 and Thread patch 103920-05 before I can... (5 Replies)
Discussion started by: dman110168
5 Replies
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)