UNIX for Advanced & Expert Users

%prep is not the same as %pre... maybe there is no %pre section?

It's possible that the %{pdsdir}/shell/COMPONENT/postinstall or .../configure are causing those error messages; have you checked them for stty or su username -c '...' commands?

right %pre section is not present in spec file.

and I have not check for stty command.
I dont know how to check for stty command
can u tell me how i check for stty ?

Regards,
Amit

Just look in those scripts and see if it is there. Or maybe use grep if they are very long.

Hi Annihilannic,
thx for yr reply.

I do grep on all those script for stty but its not found.
if you want to see all .profile then also i can send you.

Regards,
Amit

Try changing this line as follows:

Code:

sh -x %{pdsdir}/shell/COMPONENT/postinstall && sh -x %{pdsdir}/shell/COMPONENT/configure

Then try rebuilding and installing the RPM, and hopefully it will give us a clue about when the stty errors are being triggered.

Hello Annihilannic,

Thanks for yr reply.

I done sh -x %{pdsdir}/shell/COMPONENT/postinstall && sh -x %{pdsdir}/shell/COMPONENT/configure

I found one things that I have total 10 rpm package and I got this stty error message in particular one packages.

another observation is that under configure function I m running

different shell scripts using su - admin -c commands..

when I install this particular package I got the following messages.


rpm -install DBASE-4.1.0.0.23-4.1.0.0.23-1.i386.rpm

export VDIR=/opt/avaya/pds
+ VDIR=/opt/avaya/pds
+ export VOICEDIR=/opt/avaya/pds
+ VOICEDIR=/opt/avaya/pds
+ export PATH=/usr/bin:/usr/rbin:/usr/sbin:/opt/avaya/pds/bin:/opt/avaya/pds/shell:::/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
+ PATH=/usr/bin:/usr/rbin:/usr/sbin:/opt/avaya/pds/bin:/opt/avaya/pds/shell:::/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
+ export ORACLE_HOME=/opt/dbase/OraHome1
+ ORACLE_HOME=/opt/dbase/OraHome1
+ exitval=0
++ /bin/basename /opt/avaya/pds/shell/DBASE/configure
+ FNAME=configure
+ print 'NOTE: Executing DBASE "configure"'

/bin/basename /opt/avaya/pds/shell/MTDBASE/configure
+ FNAME=configure
+ print 'NOTE: Executing MTDBASE "configure"'
/opt/avaya/pds/shell/MTDBASE/configure: line 279: print: command not found
+ case $FNAME in
+ configure
+ exitval=0
+ su - admin -c /opt/avaya/pds/etc/start_db
stty: standard input: Invalid argument
stty: standard input: Invalid argument
stdin: is not a tty
stty: standard input: Invalid argument


now tell me what should i do

Regards,
Amit

Well this is obviously the part that is causing the problem:

Code:

+ su - admin -c /opt/avaya/pds/etc/start_db
stty: standard input: Invalid argument
stty: standard input: Invalid argument
stdin: is not a tty
stty: standard input: Invalid argument

So have a look at the admin user's profile scripts, that is probably where you will find the stty commands. You can safely ignore those errors if you wish, but they look messy. You could also consider removing the - from the su command if you don't really need to load that user's profile. It is also possible, but unlikely, that the stty commands are in the start_db script.

Note also this error:

Code:

+ print 'NOTE: Executing MTDBASE "configure"'
/opt/avaya/pds/shell/MTDBASE/configure: line 279: print: command not found

print is a ksh-specific command, so if your scripts are not going to run under ksh then you should use echo instead.