Thanks for the report! I believe this is now fixed in commit 28beb20626ba5459df9a5e5c25ece6396b4214a3. Though I'm confused why just doing 'tup init' with a different version would appear to make the issue go away. Did you actually run an update with the older version? The issue was in the parser, so if the Tupfile is parsed with commit b80e17f29e6ae81041c240c2d1ec320a1ceddd5e (but not the latest fix), then it would fail.
-Mike On Thu, Nov 5, 2015 at 8:58 AM, Andrew Jensen <[email protected]> wrote: > Thanks so much for your help. I have opened issue 246: > > https://github.com/gittup/tup/issues/246 > > -- > -- > tup-users mailing list > email: [email protected] > unsubscribe: [email protected] > options: http://groups.google.com/group/tup-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "tup-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
