First a few notes: I was directed to "report this bug" (see below), but not *where* to report -- I followed the links from http://www.ubuntu.com/testing/dapperbeta to here, then searched on "postgres" and didn't find anything like this reported. So a) don't yell at me if this isn't the place to report this problem and b) don't yell at me if it's already been reported. If this is NOT the place to report this bug, then email kindly letting me know where I should, would be appreciated. If this IS the place to report the bug, may I kindly suggest that the dialog box suggest where to report?
In the process of upgrading from breezy to dapper beta, using the gksudo "update-manager -d" command results eventually in a dialog message that says this:
Could not install 'postgresql-common'
The upgrade aborts now. Please report this bug.
Then in the window, it says: subprocess post-installation script returned error exit status
The output on the terminal window, in case that's useful:
beg@nemesis:~$ gksudo "update-manager -d"
warnings.warn("apt API not stable yet", FutureWarning)
/usr/lib/python2.4/site-packages/UpdateManager/MetaRelease.py:169: DeprecationWarning: Class MetaRelease is already GObject-registered; Please note that classes containing any of the attributes __gtype_name__, __gproperties__, or __gsignals__ are now automatically registered.
gobject.type_register(MetaRelease)
new_dist_available: dapper
on_button_dist_upgrade_clicked
extracting '/tmp/tmpXO_hhp/dapper.tar.gz'
authenticate '/tmp/tmpXO_hhp/dapper.tar.gz' against '/tmp/tmpXO_hhp/dapper.tar.gz.gpg'
/usr/lib/python2.4/site-packages/apt/__init__.py:17: FutureWarning: apt API not stable yet
warnings.warn("apt API not stable yet", FutureWarning)
Thanks for your bugreport!
If you upgraded using the upgrade tool (update-manager -d), could you please attach the logfiles in /var/log/
Thanks,
Michael