I didn't randomly delete configuration files I deleted the /etc/postgreql directory on purpose not randomly. The initial problem I had was that pg_dumpall wasn't working on a fresh system install (it wasn't able to dump template1). I hadn't changed any configuration files at that time so figured to just delete them. Unfortunately I can't recreate that problem to file a bug report on it (at least not without reinstalling the whole system which I'm not able to do at this time, I might try on a different system later though).
Also the system did still work as far as I could tell without that file it was just the error message I was reporting. Close the bug. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Pitt > Sent: Thursday, January 13, 2005 12:49 AM > To: Raby, Kenny G; [EMAIL PROTECTED] > Subject: Re: Bug#290078: postgresql: Error message on install > > Hi Raby! > > Raby, Kenny G [2005-01-12 9:25 -0800]: > > I am working on installing a new system. I installed postgresql then > > purged it. I then reinstalled and on the reinstall I get the message: > > Did this purging involved manually nuking /etc/postgresql? > > > chmod: cannot access `/etc/postgresql/postgresql.env': No such file or > > directory > > As Oliver already pointed out, you cannot randomly delete > configuration files and expect the system to work. Since with some > packages it does make sense to delete a configuration file, and this > choice must be respected (since it is sort of configuring, too), the > Debian Policy explicitly forbids automatic reconstruction of such > files anyway. > > Please do > > apt-get install --reinstall postgresql-client > > to fix your system again. > > Please confirm that you manually deleted this file, then we can close > this bug again. > > Have a nice day! > > Martin > > -- > Martin Pitt http://www.piware.de > Ubuntu Developer http://www.ubuntulinux.org > Debian GNU/Linux Developer http://www.debian.org
