On Wed, May 11, 2011 at 04:01:19AM -0700, tom d wrote:
> Ah, the -v has to go before the update command; sorry.
> Here's the (hopefully relevant) excerpt from the verbose update
> command...
>
> <pre>
> patch queue now empty
> Pulling the new version of the patches from the patch server
> (cd .hg/patches ; /mnt/data/sage-4.6.2/sage -hg --config
> 'extensions.hgext.mq=' pull -u http://combinat.sagemath.org/patches/)
> pulling from http://combinat.sagemath.org/patches/
> searching for changes
> no changes found
> Current non version guards:
> Updated non version guards:
> Updating guards
> /mnt/data/sage-4.6.2/sage -hg --config 'extensions.hgext.mq='
> qselect -q -n
> /mnt/data/sage-4.6.2/sage -hg --config 'extensions.hgext.mq='
> qselect
> no active guards
> Warning: the former top patch 70 A trac_10998-categories-posets-
> nt.patch does not exist anymore
> Applying all patches
> /mnt/data/sage-4.6.2/sage -hg --config 'extensions.hgext.mq=' qpush -
> a
> </pre>
Thanks. What does:
hg qselect -s
give from within the sage-combinat directory?
Could you edit /opt/sage/local/bin/sage-combinat in
qselect_backward_compatibility_patches, and try to figure out why
version_guards seems to be empty at the end?
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <[email protected]>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-combinat-devel?hl=en.
