rpm -ql sipx-freeswitch gives me; /etc/ld.so.conf.d/freeswitch.ld.so.conf /etc/monit.d /etc/monit.d/freeswitch.monitrc /etc/sysconfig/freeswitch /usr/local/freeswitch/*
> then do > rpm -e --justdb sipx-freeswitch-1.0.5-17188.16739.2.i386 Isn't there a problem with rpm or yum not always knowing what the other has installed? I've seen cases of this now and then. > 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 don't see any obvious 32bit files in the list. > 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. I can see this is going to lead to problems. This isn't good. Since I've not rebooted, I wonder if I can simply revert. I've been trying to find time to test the 4.4.0 system I've installed, maybe I could test that then backup/restore. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
