https://bugzilla.novell.com/show_bug.cgi?id=464418
User mkoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464418#c2
Matthias Koenig changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |novell-web@zmi.at
--- Comment #2 from Matthias Koenig 2009-01-23 03:38:36 MST ---
1) This should be the case, even the old tables from portmap should be
preserved on update. There was some bugs around this problem, but finally the
following is done in the pre, post and postun scripts and seemed to work:
%pre
# upgrade case from portmap
# 1. if portmap is running, dump portmap tables
if /sbin/checkproc /sbin/portmap; then
rm -f %statefile
test -x /sbin/pmap_dump && /sbin/pmap_dump > %statefile
fi
# 2. disable portmap service to be able to enable rpcbind
if test -x /sbin/portmap && /sbin/chkconfig -c portmap 3; then
/sbin/insserv -f -r portmap
fi
%preun
%stop_on_removal rpcbind
%post
%fillup_and_insserv -y rpcbind
# if portmap is running, we need to stop portmap *now*,
# start rpcbind and restore the old tables
if test -r %statefile; then
/etc/init.d/portmap stop > /dev/null || :
/etc/init.d/rpcbind start > /dev/null || :
/sbin/pmap_set2 < %statefile
rm -f %statefile
fi
%postun
%restart_on_update rpcbind
%insserv_cleanup
If this has not worked for you, we would need the info how you did the update
and steps to reproduce, since this has been tested and works here.
At least the Yast2 logs would be needed (see below) to get some clue.
2. The dependencies of rpcbind are correct.
libraries are resolved automatically and actually don't depend on the package
name, but on the library version:
# rpm -q --requires rpcbind | grep tirpc
libtirpc.so.1()(64bit)
So I am wondering how rpcbindgot installed without the libtirpc library being
installed.
Could you please attach the Yast2 logs (http://en.opensuse.org/Bugs/YaST)?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.