On Sat, 28 Apr 2012 13:17:08 +0200 Dominik George <n...@naturalnet.de> wrote:
> Some Mnesia tables are not upgraded when upgrading to the newest > package version. > > Sometimes, upstream changes table schemas, as has happened with the > pubsub tables. > > As a result, pubsub stops working after upgrading from the version in > stable to the version in testing. Clients get a "Forbidden" error. > > Up to now, I only found deleting and recreating the tables as a > solution, which causes data loss in pubsub nodes, but I am sure that > upstream provides an update script that could easily be run in > postinst! To my knowledge, the Mnesia database upgrade logic is built into the ejabberd code directly (it was last time I looked at it a while back). So the real problem might be that "the jump" is too long: stable has 2.1.5 and testing has 2.1.10 (and upstream is just about to release 2.1.11). Since it's naturally for the upstream to only test upgrades from the directly adjacent previous version, such a big version span might in theory confuse the upgrade logic. I will try to debug this issue with the upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
