Hi Vincent,
thanks a lot for your detailled analysis and feedback. Indeed this
helps to narrow down the problem.
Vincent McIntyre [2007-07-17 14:13 +1000]:
The root cause in my case was the existing database was owned by a
UID that was in NIS. During the upgrade another 'postgres' UID was
I was upgrading from sarge to etch and had this symptom well.
My problems appear to be self-inflicted but there may actually be
a problem in the postinst. So the information below is for your
perusal, in case it helps resolve things.
The root cause in my case was the existing database was
2 matches
Mail list logo
