05-10-2006
Jar patches
Hi,
This is definitely a dummy question, so I guess I'm in the right place.
I've got to install some solaris patches. I've downloaded the correct patches as .jar files and also as .zip files.
How do I extract these so that I can then use the patchadd command.
I've created a /var/spool/patch directory but when I try the jar extract or jar tf I get
java.util.zip.ZipException: invalid entry size (expected 4985 but got 4994 bytes)
Any help gratefully received
Thanks
8 More Discussions You Might Find Interesting
1. Solaris
I am a beginner to Solaris
In Solaris you will find 'jar'. I am used to 'tar' command in Linux.
What makes the differenced between 'jar' and 'tar' ?
Is 'jar' unique to Solaris?
I found a command called 'compress' too in Solaris.
It is not in my Linux. Is it something special to... (1 Reply)
Discussion started by: Angelo
1 Replies
2. Shell Programming and Scripting
Hi vgersh99,
Iam sorry for that. In future, I will start new threads for different topics. Assuming that we don't know what the name of the jar file, we are searching for is, do we have any way, of finding a string or a file in it. Is there any Unix command for it?
thanks. (2 Replies)
Discussion started by: pjanakir
2 Replies
3. UNIX for Dummies Questions & Answers
Hello sir,
I have created a jar file having some code in java.What it does is that it calls a shell code (a.sh) which is in the same directory.
Now my requirement is that I want to jar the a.sh also along with the other files and want to call the a.sh which is now inside the jar file and not... (1 Reply)
Discussion started by: nsharath
1 Replies
4. Solaris
hi all,
i am using jar as following :-
jar cvf file_name.txt.jar file_name.txt
but it is file by file
my problem is i have i want to run jar on all files in speaific directory
what can i do for this
this is for the first time
the secand time there was files already ended by... (5 Replies)
Discussion started by: xxmasrawy
5 Replies
5. Solaris
Hi ,
i use below command to create a jar from /home/surya
jar -cvf foldername.jar jarfolderpath
foldrename.jar= directorywhere jar file needs to be created including jar file name
jarfolderpath: directory which needs to be included to create a jar
Now taking below scenario:... (1 Reply)
Discussion started by: surya.jena
1 Replies
6. Shell Programming and Scripting
Hi,
Is there an option with jar command which allows us to copy some class files(already existing,want to override)to a jar file without exploding it.?
Thanks in advance. (1 Reply)
Discussion started by: dnam9917
1 Replies
7. Shell Programming and Scripting
Hi All,
I am having 7 jar files in a dir. abc like listed below
bash-3.00$ cd abc
bash-3.00$ ls
123.jar
23wdawd.jar
dfsa23.jar
dsa.jar
wew234.jar
adsd234234.jar
dfsda423.jarNow i want to assign all this jar files to a variable in the below format
... (6 Replies)
Discussion started by: natraj005
6 Replies
8. AIX
I need to find out list of installed patches from given list of patches.
I have tried using instfix -f <File containing list of patches> -i -c
But I was not able to understand the output of this command. It was like below.
bos.perf.tools: :0.0.0.0:?:
bos.rte.libc: :0.0.0.0:?: ... (4 Replies)
Discussion started by: Saurabh Agrawal
4 Replies
LEARN ABOUT DEBIAN
stg-sink
STG-SINK(1) StGit Manual STG-SINK(1)
NAME
stg-sink - Send patches deeper down the stack
SYNOPSIS
stg sink [-t <target patch>] [-n] [<patches>]
DESCRIPTION
This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable
patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be
more easily committed or pushed.
If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to
option allows to place them under any applied patch.
Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then
(unless --nopush is also given) pushing back into place the formerly-applied patches.
OPTIONS
-n, --nopush
Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed.
-t TARGET, --to TARGET
Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack.
-k, --keep
Keep the local changes.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SINK(1)