On Saturday 29 Jul 2017 17:11:06 Alan McKinnon wrote: > Backup the postgres configs and database files, emerge -C all postgres > versions, make sure there are no files left with postgres in the name, > and emerge the version back that you want. Restore your backed up > configs just in case the ebuild wreaked them. Start postgres, the db > should be unaffected as all you did was replace binary code files.
Thank you Alan for your help. I reinstalled the previous version 9.5.7, ran eselect to (re)set postgresql to 9.6. Then uninstalled 9.5.7 and ended up with a boxfull of broken symlinks again. o_O At this stage I could have done what you suggested, but instead I ran: find /usr/include -type l | while read f; do if [ ! -e "$f" ]; then ls -l "$f"; fi; done which came up with a list of broken symlinks and repeated for /usr/bin and /var/lib64. Removed/restored all broken symlinks to point to the new version and restarted the database. Everything seems to be working as it should now. I don't know what to blame now. My upgrade process which seems to have gone sideways this time, or the eselect tool which may need to get cleverer with this package. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
