12-24-2008
try this:
#cd /Desktop
# unpack-patches -r -q
and let me know how it goes
otherwise, try to uncompress the patch and use the patchadd command again
Last edited by DukeNuke2; 12-24-2008 at 05:03 PM..
8 More Discussions You Might Find Interesting
1. Solaris
Ok, I attempted to apply a patch to a V440 and it bailed part way through. When I tried to patchrm the patch (after booting from CD), patchrm said that I had to fully install the failed patch before I could delete it. Since installing it killed the system forcing a boot from CD, it sounds like a... (4 Replies)
Discussion started by: BOFH
4 Replies
2. Solaris
Hi,
I have a Sun fire V280R server and when i updated the kernel patch i got this error.
mdb not found: patchadd not safe.
/kernel/dacf/sparcv9/usb_ac_dacf: undefined symbol 'am_attach'
/kernel/dacf/sparcv9/usb_ac_dacf: undefined symbol 'am_src2'
/kernel/dacf/sparcv9/usb_ac_dacf: undefined... (3 Replies)
Discussion started by: Jartan
3 Replies
3. Solaris
Hello,
I'm trying to apply the patch on Solaris 9 :
$/jac/update$ patchadd ./112945-46
Checking installed patches...
One or more patch packages included in
112945-46 are not installed on this system.
Patchadd is terminating.
The error message is not really talkative so I had a... (7 Replies)
Discussion started by: Tex-Twil
7 Replies
4. Solaris
Greetings All-
I ran into this problem today and was curious if anyone else had seen it.
I am attempting to add patch 137402-02 on a v890 running Sol9.
Here's the error I get:
#> patchadd 137402-02
Checking installed patches...
Verifying sufficient filesystem capacity (dry run... (7 Replies)
Discussion started by: bluescreen
7 Replies
5. Solaris
greetings,
I am new to solaris, have a basic question.
I have to check for patch 137111-04 (as prerequisite) for installing Oracle.
# patchadd -p | grep 137111-04
# patchadd -p | grep 137111
Patch: 137137-09 Obsoletes: 120741-01 120986-12 120992-02 121008-02 121274-01 121414-01... (2 Replies)
Discussion started by: mubeenmd
2 Replies
6. Cybersecurity
How to limit patchadd command to root user only?
I'm running a solaris 10 5/09 server, I have 2 users other than root. One being able to use the patchadd command and one is unable to do so. What I'm trying to do is to limit the patchadd command so that only root is able to run it. (7 Replies)
Discussion started by: ShouTenraku
7 Replies
7. UNIX for Dummies Questions & Answers
HI Guys,
I hope you are well. I am trying to write a script that gets executed every time i open a shell (cshell). I have two questions about that
1) I need to enter these commands
$ echo $DISPLAY
$ setenv $DISPLAY output_of_echo_$display_command
How can i write a... (2 Replies)
Discussion started by: kaaliakahn
2 Replies
8. Solaris
Hi guys,
I am really new to Solaris. My question is about the patching package management. Now I was provided some old packages within that there are hard-coded codes written with commands like "patchadd", so anyway I can make them work with Solaris 11?
Cheers! (8 Replies)
Discussion started by: ethanzhou
8 Replies
LEARN ABOUT DEBIAN
stg-push
STG-PUSH(1) StGit Manual STG-PUSH(1)
NAME
stg-push - Push one or more patches onto the stack
SYNOPSIS
stg push [options] [<patch1>] [<patch2>] [<patch3>..<patch4>]
DESCRIPTION
Push one or more patches (defaulting to the first unapplied one) onto the stack. The push operation allows patch reordering by commuting
them with the three-way merge algorithm. If there are conflicts while pushing a patch, those conflicts are written to the work tree, and
the command halts. Conflicts raised during the push operation have to be fixed and the git add --update command run (alternatively, you may
undo the conflicting push with stg undo).
The command also notifies when the patch becomes empty (fully merged upstream) or is modified (three-way merged) by the push operation.
OPTIONS
-a, --all
Push all the unapplied patches.
-n NUMBER, --number NUMBER
Push the specified number of patches.
--reverse
Push the patches in reverse order.
--set-tree
Push the patches, but don't perform a merge. Instead, the resulting tree will be identical to the tree that the patch previously
created.
This can be useful when splitting a patch by first popping the patch and creating a new patch with some of the changes. Pushing the
original patch with --set-tree will avoid conflicts and only the remaining changes will be in the patch.
-k, --keep
Keep the local changes.
-m, --merged
Check for patches merged upstream.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-PUSH(1)