I just noticed the subject of this bug is Asterisk bugs... Ooops! It should have read: Postgresql bug
> -----Original Message----- > From: Martin Pitt [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 18, 2006 8:20 AM > To: Jon Webster > Cc: [EMAIL PROTECTED] > Subject: Re: Bug#357400: Asterisk bugs > > If /var/lib/postgres is a separate partition (or, more precisely, on a > different partition than /var/lib/postgresql), then the upgrade will > not move the installation, since the dedicated partition should be > kept. If both paths are on the same partition, then the cluster should > have been moved to the new path. I'm only using one partition for these installations, so this wasn't an issue. > > > > [EMAIL PROTECTED]:/$ ls /var/lib/post* -d > > > > /var/lib/postgrsql > > > > > > Now, *that* looks wrng :) > > > > > > So, to be honest, I'm not sure what happened here. 'postgrsql' doesn't > > > appear anywhere in the postgresql nor postgresql-common sources, and I > > > never heard that this path was created at some time. Do you have an > > > idea how this directory could have been misnamed? > > > > > > > The most likely place is postgresql/sarge. > > Nope, I just checked. I cannot find this typo in the sources anyway. > The only way I can imagine how that happened is that you made that > typo when the Sarge package asked (with debconf) for the installation > path. Is that possible? > Whoops! That line should have read '/var/lib/postgresql', my mistake. I scanned the previous email and didn't read that as a splling rror, and assumed we were still talking about /var/lib/postgres. So, in closing, we've concluded this home directory problem is caused by not upgrading postgresql/stable to postgresql/unstable before installing postgresql-8.1. Bypassing the transitional package leaves the original /etc/passwd entry intact, with the old(wrong) home directory.
