On Wed, May 25, 2011 at 11:28 AM, [email protected] <[email protected]> wrote: > Bit nervous about doing that because it removes others at the same time and > I'm not sure if I should use nodeps or not. > Too easy to break the system when things get into dep problems.
**** CAVEAT: I haven't tried this, just giving you an idea of an option that might work.... If you're nervous, you can do this rpm -ql sipx-freeswitch-1.0.5-17188.16739.2.i386 > file-list to get a list of the files installed first. then do rpm -e --justdb sipx-freeswitch-1.0.5-17188.16739.2.i386 to just trick the rpm database to think it's gone. It will orphan all the files on your disk. Then move or remove any/all files from the file-list by hand that you think are safe to remove. 32bit .so files for example. I wouldn't do --nodeps, but instead allow the command to fail and start at each of the packages that depend on sipx-freeswitch-1.0.5-17188.16739.2.i386 first and work your way up until you've removed all 32 bit sipxecs related rpms. NOTE: I think 64 systems come w/some 32 bit rpms installed, like openssl for some unported apps and such, leave those alone obviously. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
