So why "rpm -U" do NOT use --nopostun --nopreun by default ???

shaybery · 12-27-2008, 05:47 AM

The command rpm -U is actually running rpm -i <rpm-v2> and then rpm -e <rpm-v1>.
This upgrade process can be a problematic, and this is the scenario:
there is rpm-v1 with post-uninstall script that "userdel testuser" if exist. BUT
there is rpm-v2 with post-install script that "useradd testuser" !!!

In this case if you run "rpm -i rpm-v1" and then do "rpm -U rpm-v2"
First it will run "useradd testuser" during the "rpm -i rpm-v1", and then
it will run "userdel testuser" during the "rpm -e rpm-v1".
So the testuser will not be defined on the system after upgrade. but this what we wanted to do in rpm-v2.

So why the rpm -U don't use by default the flag --nopostun and --nopreun?
because those flag disable the post\pre uninstall of the old rpm.

Simon Bridge · 12-27-2008, 10:59 PM

Why is this a problem?
Where are you getting this from?

shaybery · 12-28-2008, 02:11 AM

Quote:

Originally Posted by Simon Bridge

Why is this a problem?
Where are you getting this from?

The problem is when u have rpm that execute postuninstall script,
and when u upgrade this rpm to a newer, then the postuninstall script (which execute during the rpm -U <newer-rpm>) can damage your system!
This is happand because the "rpm -U" is actually run
first "rpm -i <newer-rpm>"
second "rpm -i <older-rpm>"

I think that "rpm -U" should use by default the --nopostun and --nopreun
in order to disable those pre\post uninstall scripts of the older-rpm.

Valery Reznic · 12-28-2008, 06:15 AM

Quote:

Originally Posted by shaybery

The problem is when u have rpm that execute postuninstall script,
and when u upgrade this rpm to a newer, then the postuninstall script (which execute during the rpm -U <newer-rpm>) can damage your system!
This is happand because the "rpm -U" is actually run
first "rpm -i <newer-rpm>"
second "rpm -i <older-rpm>"

I think that "rpm -U" should use by default the --nopostun and --nopreun
in order to disable those pre\post uninstall scripts of the older-rpm.

all rpm's pre/post/install/uninstall scripts get as first argument ($1) a number of package instances after operation is finished,
i.e same postuninstall script when do 'rpm -e ' will get '0' in $1, and in 'rpm -U' - $1 will be '1'.
Postinstall script should check $1 and do correct thing for erase and for update.

There is no reason to disable scripts by default

shaybery · 12-28-2008, 05:25 PM

Quote:

Originally Posted by Valery Reznic

all rpm's pre/post/install/uninstall scripts get as first argument ($1) a number of package instances after operation is finished,
i.e same postuninstall script when do 'rpm -e ' will get '0' in $1, and in 'rpm -U' - $1 will be '1'.
Postinstall script should check $1 and do correct thing for erase and for update.

There is no reason to disable scripts by default

So what you say that I need to right my pre\post unsiatll "right" with the use of the $1 parameter. $1=0 indicates that the rpm has been removed because rpm -e, $1=1 indicates that the rpm has been removed because rpm -U.

can you show me any rpm that use this $1 parameter?

shaybery · 12-29-2008, 01:02 AM

Quote:

Originally Posted by Valery Reznic

all rpm's pre/post/install/uninstall scripts get as first argument ($1) a number of package instances after operation is finished,
i.e same postuninstall script when do 'rpm -e ' will get '0' in $1, and in 'rpm -U' - $1 will be '1'.
Postinstall script should check $1 and do correct thing for erase and for update.

There is no reason to disable scripts by default

You are right!

This is exactly how people need to write rpms.
By using $1 parameter inside the pre\post uninstall it can be distinguished between pre\post uninstall scripts for uninstall that caused by upgrade and for uninstall that caused by a regular uninstall.

But the problem that most of the people that write rpm do not use this parameter, so in those cases I must run the upgrade by this command : "rpm -U --nopreun --nopostun <rpm-name>"

Thank you very much for your answer.

Valery Reznic · 12-29-2008, 01:20 AM

Quote:

Originally Posted by shaybery

So what you say that I need to right my pre\post unsiatll "right" with the use of the $1 parameter. $1=0 indicates that the rpm has been removed because rpm -e, $1=1 indicates that the rpm has been removed because rpm -U.

can you show me any rpm that use this $1 parameter?

Sure. for example bash.
It's post-uninstall looks like following:

Code:

%postun -p /bin/sh
if [ "$1" = 0 ]; then
    /bin/grep -v '^/bin/bash$' < /etc/shells | \
      /bin/grep -v '^/bin/sh$' > /etc/shells.new
    /bin/mv /etc/shells.new /etc/shells
fi

You can by yourself looks for the different spec files either in the sources or using
rpmrebuild (http://rpmrebuild.sf.net)

rpmrebuild -e <package> will do the trick

Valery

shaybery · 12-30-2008, 03:41 AM

Thanks u very much.