Hi, I have filed a bug: http://masanjin.net/sup-bugs/issue52 The error message shows: This Sup version expects a v1 index, but you have an existing v2 index. Please downgrade to your previous version and dump your labels before upgrading to this version (then run sup-sync --restore). Can someone explain this error message? -- Peace and Love, Shreyank Gupta Blog: http://allsortsofshrink.blogspot.com
Excerpts from Shreyank Gupta''s message of Wed Jan 27 07:51:34 -0500 2010:> Can someone explain this error message?If you''re running from the git repo, have you reset your HEAD recently? There was a version bump in the index recently that you can''t easily just switch away from... -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20100127/8591cdf2/attachment.bin>
Reformatted excerpts from Shreyank Gupta''s message of 2010-01-27:> This Sup version expects a v1 index, but you have an existing v2 > index. Please downgrade to your previous version and dump your labels > before upgrading to this version (then run sup-sync --restore).You used git next before, and now you''re trying git master. There is a version incompatibility that will go away once a particular topic branch gets merged down to master. Workaround: use git next for now. -- William <wmorgan-sup at masanjin.net>
On Wed, Jan 27, 2010 at 6:51 PM, William Morgan <wmorgan-sup at masanjin.net> wrote:> Reformatted excerpts from Shreyank Gupta''s message of 2010-01-27: >> This Sup version expects a v1 index, but you have an existing v2 >> index. Please downgrade to your previous version and dump your labels >> before upgrading to this version (then run sup-sync --restore). > > You used git next before, and now you''re trying git master. There is a > version incompatibility that will go away once a particular topic branch > gets merged down to master. > > Workaround: use git next for now.git next gives me the following exception: http://masanjin.net/sup-bugs/file12/exception-log.txt I followed the instructions at http://sup.rubyforge.org/wiki/wiki.pl?UTF8 to solve UTF issues. Is that the reason ? -- Peace and Love, Shreyank Gupta Blog: http://allsortsofshrink.blogspot.com