Is the sage-combinat server offline? On Mar 13, 4:52 pm, Anne Schilling <a...@math.ucdavis.edu> wrote: > Hi Mark, > > Yesterday Nicolas wrote that the sage-combinat queue applies cleanly to > sage-5.0.beta7. Patches are still being merged into beta8. Hence it would > be better to work with sage-5.0.beta7 at this point. > > Best, > > Anne > > On 3/13/12 1:44 PM, Mark Shimozono wrote: > > > > > > > > > I just installed sage-5.0.beta8 (I think Nicolas suggested it) > > and then tried to install combinat. It failed when applying patches. > > I then tried to update and here is what happened. > > > --Mark > > > $ ./sage -combinat update > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Storing top applied patch > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Unapplying all the patches > > hg --config 'extensions.hgext.mq=' --config 'ui.username="sage- > > combinat script"' qpop -a > > popping trac_10817-generalized_associahedra-cs.patch > > patch queue now empty > > Pulling the new version of the patches from the patch server > > (cd .hg/patches ; hg --config 'extensions.hgext.mq=' --config > > 'ui.username="sage-combinat script"' pull > > -uhttp://combinat.sagemath.org/patches/) > > pulling fromhttp://combinat.sagemath.org/patches/ > > searching for changes > > no changes found > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Current non version guards: > > Updated non version guards: > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > Skip backward compatibility patches for sage 4.6.2 > > Skip backward compatibility patches for sage 4.6.2 > > Skip backward compatibility patches for sage 4.1.2 > > Skip backward compatibility patches for sage 4.3.1 > > Skip backward compatibility patches for sage 4.3.1 > > Skip backward compatibility patches for sage 4.3.2 > > Skip backward compatibility patches for sage 4.3.2 > > Skip backward compatibility patches for sage 4.3.3 > > Skip backward compatibility patches for sage 4.3.4 > > Skip backward compatibility patches for sage 4.4 > > Skip backward compatibility patches for sage 4.4 > > Skip backward compatibility patches for sage 4.4.1 > > Skip backward compatibility patches for sage 4.4.2 > > Skip backward compatibility patches for sage 4.4.3 > > Skip backward compatibility patches for sage 4.4.4 > > Skip backward compatibility patches for sage 4.5 > > Skip backward compatibility patches for sage 4.5.2 > > Skip backward compatibility patches for sage 4.5.3 > > Skip backward compatibility patches for sage 4.6 > > Skip backward compatibility patches for sage 4.6.1 > > Skip backward compatibility patches for sage 4.6.1 > > Skip backward compatibility patches for sage 4.6.2 > > Skip backward compatibility patches for sage 4.6.2 > > Skip backward compatibility patches for sage 4.7 > > Skip backward compatibility patches for sage 4.7 > > Skip backward compatibility patches for sage 4.7.1 > > Skip backward compatibility patches for sage 4.7.1 > > Skip backward compatibility patches for sage 4.7.2 > > Skip backward compatibility patches for sage 4.7.2 > > Skip backward compatibility patches for sage 4.7.2.alpha3 > > Skip backward compatibility patches for sage 4.7.2.alpha4 > > Skip backward compatibility patches for sage 4.8 > > Skip backward compatibility patches for sage 4.8 > > Skip backward compatibility patches for sage 4.8.alpha0 > > Skip backward compatibility patches for sage 5.0.beta0 > > Skip backward compatibility patches for sage 5.0.beta2 > > Skip backward compatibility patches for sage 5.0.beta4 > > Skip backward compatibility patches for sage 5.0.beta5 > > Skip backward compatibility patches for sage 5.0.beta6 > > Updating guards > > hg --config 'extensions.hgext.mq=' --config 'ui.username="sage- > > combinat script"' qselect -q -n > > hg --config 'extensions.hgext.mq=' --config 'ui.username="sage- > > combinat script"' qselect > > no active guards > > Switching to sage combinat root directory: /home/msshimo/ > > sage-5.0.beta8/devel/sage-combinat > > hg --config 'extensions.hgext.mq=' --config 'ui.username="sage- > > combinat script"' qpush trac_10817-generalized_associahedra-cs.patch > > applying trac_10817-generalized_associahedra-cs.patch > > file sage/combinat/root_system/associahedron.py already exists > > 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/ > > root_system/associahedron.py.rej > > patching file sage/combinat/root_system/cartan_type.py > > Hunk #1 succeeded at 1024 with fuzz 2 (offset 27 lines). > > patching file sage/combinat/root_system/root_lattice_realization.py > > Hunk #1 succeeded at 367 with fuzz 2 (offset 17 lines). > > Hunk #2 succeeded at 973 with fuzz 2 (offset 221 lines). > > patch failed, unable to continue (try -v) > > patch failed, rejects left in working dir > > errors during apply, please fix and refresh trac_10817- > > generalized_associahedra-cs.patch > > Abort
-- 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.
