Just as a heads-up, I just installed Ubuntu 11 on my laptop and rebuilt Sage and it's now having tis same problem on a second machine. Perhaps something to do with a piece of upgraded software in Ubuntu 11?
I'll play with this a bit more and see if I can make any headway in identifying the issue. -tom On May 15, 12:25 pm, "Nicolas M. Thiery" <nicolas.thi...@u-psud.fr> wrote: > On Sun, May 15, 2011 at 03:29:41AM -0700, tom d wrote: > > Yeah, so the failure's definitely happening in the check for version > >guards. I added a couple print statements in the update script to try > > to figure out what's happening; does this look like the right kind of > > thing to you? > > > current sage version: [4, 6, 2] > > hg_all_guards: ['guardsin series file:', ' 1 +4_1_2', ' 2 -4_3_1', > > ' 3 +4_3_1', ' 1 -4_3_2', ' 2 +4_3_2', ' 2 +4_3_3', ' 1 +4_3_3:', > > ' 2 +4_3_4', ' 1 -4_4', ' 1 +4_4', ' 2 +4_4_1', ' 1 +4_4_2', ' 1 > > +4_4_3', ' 1 +4_4_4', ' 2 -4_5', ' 4 +4_5', ' 3 -4_5_2', ' 1 > > +4_5_2', ' 1 +4_5_3', ' 1 -4_6', ' 1 +4_6', ' 9 -4_6_1', ' 1 > > +4_6_1', ' 4 -4_6_2', ' 2 +4_6_2', ' 1 -4_7', '45 +4_7', ' 7 > > +4_7_1', ' 1 +5_0', '150 NONE', ' 3 +coerce', '18 +disabled', ' 3 > > +experimental', ' 1 +free_to_assign', ' 1 +fun', ' 1 > > +keep_for_possible_future_use', ' 1 +long_compilation', ' 1 > > +needs_rebase', ' 1 +not_finished', ' 1 +not_wanted', ' 1 > > +power_zero', ' 2 +tentative_implementation', ' 1 +words_ng_fixme'] > > versionguards: [] > > allguards: [] > > > The script takes the output of the hg_all_guards() function (given > > above) and then uses a method to figure out if it's a new version > > guard or not; this check is apparently always returning false. So the > > question is whether the hg_all_guards output above looks sensible, or > > whether it's funky somehow (like, say, those leading numerals). > > Ah! The leading numerals seem funky indeed, and could well point to > the issue. I don't get them when I do > > > sage -hg qselect -s > +4_1_2 > -4_3_1 > ... > > Can you try disabling everything in your hgrc except for the > hgext.mq=, and see if sage -hg qselect -s returns to a normal > behaviour? > > Cheers, > Nicolas > -- > Nicolas M. Thi ry "Isil" <nthi...@users.sf.net>http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
