I think I have this fixed now. The problem was that psycopg dropped backward compatibility with psycopg1, and Debian decided not to have pyscopg1 at all. I kept downgrading the package to a version with backward compatibility, but I don't like pinning (I always forget to unpin), so every time Debian corrected a typo in their scripts I got the incompatible version again. Roundup finally upgraded to psycopg2, so I was able to upgrade, and this should keep things together for a while. Steve Hauke Fath writes: > On Sun, 5 May 2019 06:00:11 +0900, Stephen J. Turnbull wrote: > > Hauke Fath writes: > > > DatabaseError: could not connect to server: Connection refused Is the > > > server running on host "localhost" (127.0.0.1) and accepting TCP/IP > > > connections on port 5432? > > > > Yeah, I'm out of the country and that appears to be a PostgreSQL > > upgrade problem. Looks like I'll need to migrate databases and don't > > want to do that remote. > > Hi Stephen, > > I have been getting a consistent > > The server is temporarily unable to service your request due to > maintenance downtime or capacity problems. Please try again later. > > from the tracker recently. Could you have a look, maybe? > > Cheerio, > Hauke > > -- > The ASCII Ribbon Campaign Hauke Fath > () No HTML/RTF in email Institut für Nachrichtentechnik > /\ No Word docs in email TU Darmstadt > Respect for open standards Ruf +49-6151-16-21344 > >