The problem with the original patch was that the code working with pubsub tables was changed between 2.0.1 and 2.0.2 in changeset [1] which fixed the issue [2].
The attached patch was verified to correctly upgrade pubsub tables (two nodes with two items published in each one) while upgrading from 1.1.2 to 2.0.1 with this patch integrated.
Torsten, if possible, could you please try to push the fixed version into Lenny? I understand that it's in the deep-freeze stage and this bug cannot be considered more severe than "serious" as most of ejabberd's functionality is unaffected, but 2.x series finally got "real" PubSub support which means many users would like to try it out.
If this is impossible, a note about manually deleting the "pubsub_node" table after upgrading while the server is stopped would be better than nothing. But I don't know whether to put one.
1. https://forge.process-one.net/changelog/ejabberd?cs=1491 2. https://support.process-one.net/browse/EJAB-669
pubsub_upgrade_tables.patch.gz
Description: application/gzip
