8 More Discussions You Might Find Interesting
1. Linux
Hello,
I need to know regarding setting up of Local repositories so that I can update or install packages on other RHEL servers.
In our environment we have many servers with different RHEL versions.
Like RHEL 7.2, RHEL 7.3, RHEL 7.4, RHEL 7.5
Arch = x86_64
I have setup one Repo server;... (0 Replies)
Discussion started by: SunshineMLinux
0 Replies
2. Red Hat
i have a repository server for red hat and centos clients.
the repository contain all the rpms from the original install cd.
now lets say i will add for example the new BASH rpm that fixes the shellshock vaulnerbility. when the client machine will run the command: "yum update bash" did the yum... (1 Reply)
Discussion started by: guy3145
1 Replies
3. Solaris
Hi experts,
I have an X86 as my IPS server running ( uname -a SunOS 5.11 11.1 i86pc i386 i86pc). the IPS has the following package version:
prdb01b:~# pkg list -fa entire
NAME (PUBLISHER) VERSION IFO
entire ... (0 Replies)
Discussion started by: afadaghi
0 Replies
4. Solaris
Hi guys, long time no see
Today I installed Oracle Solaris 11.11 in virtualbox. My machine needs to be bulletproof for our production databases but :D
First problem is that I can't install anything using IPS where publisher is solars, default freeware repo for Oracle Solaris. I need... (9 Replies)
Discussion started by: solaris_user
9 Replies
5. Red Hat
Hi Friends,
I have succesfully configured a local yum repository using ios image.
Please let me know how i can synchronize the local repository with RHN.
Is it possible, so that i can update the local repository with latest updates.
Regards,
Arumon (1 Reply)
Discussion started by: arumon
1 Replies
6. Shell Programming and Scripting
Hi,
I have problem in writing the UNIX scripts,I have one SAP server and my local server .I want to take one file from SAP server to my local server weekly bases I want to write one UNIX scripts which will automatically takes that file from SAP server to my server.so I need not need to pull the... (1 Reply)
Discussion started by: Mohsin22021987
1 Replies
7. Shell Programming and Scripting
Hi,
This is deb, i have problem an a script for that i need some help and support.
problem is .....
i have a file called 'empdetails'
i want to add every update or modification of a particular employee to that file (like swap in or swap out,salary,emp id etc.)
and the file is... (2 Replies)
Discussion started by: deb.simply
2 Replies
8. UNIX for Dummies Questions & Answers
I would like automate the process of copying some logs files from a server to my local hard drive at a set time each week/day.
I don't really know anything about creating and scheduling jobs. Is this something I could setup relatively easily?
I would like to automatically copy all the logs... (1 Reply)
Discussion started by: Sepia
1 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)