I just saw this one again. I found a relevant discussion here: https://lists.alioth.debian.org/pipermail/dbconfig-common- devel/2006-September/000627.html
Here's the relevant quote from Sean Finney (the maintainer of dbconfig- common): """ i can reproduce your problem... looking in my postgres logs i see: ERROR: database "zabbix" is being accessed by other users ERROR: role "zabbix" cannot be dropped because some objects depend on it i think this is because the zabbix server has the datbase open while the removal code is running in the prerm script. if you manually stop the zabbix server before purging i think you'll see what i'm talking about. as for how to workaround this... you could manually stop the server before calling dbc_go when $1 is set to "remove", or you could call the dbconfig hooks after the #DEBHELPER# macro. since this could be a general problem with other pgsql+daemon packages, i'd appreciate suggestions for how to mention this in documentation, assuming this solves your problem :) """ Reply from Michael Ablassmeier: """ yes, moving the stanza in prerm above the dbconfig-common call works nicely and the package successfully purges its database setup. Thanks for your time! (having a short note somewhere in the Docs might be helpful since i've discovered the same problem for the mysql part of the package, even tho mysql doesnt care about it that much) """ ** Changed in: maas Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044559 Title: apt-get remove maas --purge while maas is running prevents full database purge To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1044559/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
