The upgrade from the older version of sup to this new one can be complex, as some configuration files may require manual migration. I have added some information in the NEWS.Debian file for users. I had envisioned using maintainer scripts to automate this migration, but this became extraordinarily complex. Instead, I have updated the Sup Wiki upstream and linked to that page from NEWS.Debian. If anyone has any suggestions, please let me know (or just add it).Yes, this is a hard nut... I think that we should at least ship the wiki text on how to migrate in /usr/share/docs, and also mention this in NEWS. I also raised this question on the supmua mailing list and got an answer that we might try, verify, and document https://groups.google.com/forum/#!topic/supmua/90UxVtnysPk
I have just updated the upstream wiki with detailed step-by-step instructions for migrating by backing up, running sup-config, and manually changing the source id. I am going to include these instructions in the NEWS file. Perhaps now the local copy of the wiki page is the unnecessary?
Caitlin -- To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/540a0b96.4020...@zoho.com
