Type rpm –Uvh ilta-acrophobia-3.1-1.i386.rpm. RPM will update files as needed. Your existing ePDF.conf will be renamed to ePDF.conf.rpmsave. Change to the /etc/ePDF directory and copy your old conf file back into place (cp ePDF.conf.rpmsave ePDF.conf)
If you used the “Smart Host” configuration in either RC1 or RC2, there may be an errant line from your sendmail configuration file. Edit /etc/mail/sendmail.mc and look for a line that looks like the following:
In particular, notice there is a null string between the single quotes, right after the opening parenthesis. The latter part of the line may be different for you. In any case, remove this line and save sendmail.mc.
This upgrade requires some cleanup, and all shares will be removed. Accordingly, you should not do this on a production box (unless you’ve kicked the users off for an hour or so).
Make sure samba is stopped. Type: service smb stop
Run the command: rpm -e lawnet-acrophobia. This will remove the python and shell scripts, but leave any custom settings in ePDF.conf intact (i.e. rpm will preserve ePDF.conf if you have updated it since the original install, otherwise rpm will remove it). The old ePDF.conf file is not compatible with Acrophobia v3.0. When you reinstall Acrophobia, the old file will be renamed to ePDF.conf.rpmsave. You can keep it around for reference, but you should not copy it back to ePDF.conf
Remove the Acrophobia config directory (rm -rf /etc/ePDF). Type this command carefully. If you slip, you can wipe out your linux box.
Remove the Acrophobia directory (rm -rf /var/spool/ePDF). Same warning as above.
Remove the driver directory (rm -rf /etc/samba/drivers). Same warning – you know the drill.
Remove Samba’s tdb files – they’ll be recreated when Samba restarts. Look in /var/cache/samba and delete all files in that directory and the subdirectories. LEAVE THE DIRECTORY STRUCTURE INTACT!!
Remove all of the print shares from smb.conf (they are all at the end, following [print$])
Remove the [print$] share from smb.conf
Reinstall Acrophobia according to the installation instructions in README.TXT.