Finally, the image server is back online. This was by far the worst update yet…

First, it was postgresql which underwent a major version change which happens every 5 years. This involved breaking changes and rendered the image database useless until properly migrated. Big learning curve. Then, there was a necessary extension which became flagged out of date at about the same time – vectorchord. No worries, I built 1.0 from upstream, configured postgres with it and rebuilt the database from scratch. Then I was able to dump the old database and migrate the data. Next issue, the image server. A new problem showed up when immich refused to use vchord greater than 0.6 – so, I had to alter the PKGBUILD, .SRCINFO and the source constraints file to allow up to 1.1, deleted the package files, and makepkg -i to rebuild and install it. No problem. So now, without docker, I have immich with postgresql 18.1, vectorchord 1.0, and immich 2.2.3… and it’s working! This was not easy. There were far more errors than successes, but I finally got it. Now things are likely to break again when immich updates, but the fix will not take days to figure out. As it is, there are a couple of extra steps involved with updating on my system. But, do I want to contribute vchord 1.0 to AUR? Or, fork a branch of immich? No. Definitely not. It’s enough work maintaining this server. So, once the system is done scanning the library for changes, of which there are approximately 11 thousand (which prompted the update to begin with), I will finally be back to sorting and organizing…