[sage-combinat-devel] queue broken
Hi Travis, I think you broke the queue with sage-5.9.rc1. Could you please fix it immediately since we are working on patches. Perhaps you could put your patches further down in the queue to avoid these issues? applying disable_lazy_import_warning-nt.patch applying trac_10963-more_functorial_constructions-nt.patch patching file sage/categories/crystals.py Hunk #1 FAILED at 8 1 out of 3 hunks FAILED -- saving rejects to file sage/categories/crystals.py.rej patching file sage/categories/regular_crystals.py Hunk #2 succeeded at 503 with fuzz 1 (offset 5 lines). patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_10963-more_functorial_constructions-nt.patch Thanks, Anne -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken?
Ok,thanks! Just today there was another broken spot in the queue. (I upgraded to 5.8rc0 just in case, too.) I was wanting to rebase my affine permutations patch for the new documentation system so that it can finally get a review, and it was under the broken patch, so I just made the fixes and pushed... hope that's ok. applying trac_12876_category-fix_abstract_class-nt-rel11521.patch patching file sage/categories/homset.py Hunk #6 FAILED at 261 1 out of 11 hunks FAILED -- saving rejects to file sage/categories/homset.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_12876_category-fix_abstract_class-nt-rel11521.patch Abort On Saturday, March 16, 2013 12:57:22 AM UTC+3, Anne Schilling wrote: > > Hi Tom, > > Yes, I got the same error with sage-5.8.bet4. I rebased Ben Salisbury's > patch. > It should work now. > > Ben, please pull from the sage-combinat server before you keep working on > your patch! > > Best, > > Anne > > On 3/15/13 2:51 PM, tom d wrote: > > From tonight's attempt to apply the queue in Sage 5.7rc0: > > > > > > applying trac_4327-root_system_plot_refactor-nt.patch > > patching file sage/combinat/root_system/type_affine.py > > Hunk #1 succeeded at 237 with fuzz 2 (offset -54 lines). > > applying trac_14143-alcove-path-al.patch > > applying trac_14192-infinity_crystal-bs.patch > > patching file sage/combinat/crystals/all.py > > Hunk #1 FAILED at 11 > > 1 out of 1 hunks FAILED -- saving rejects to file > sage/combinat/crystals/all.py.rej > > patch failed, unable to continue (try -v) > > patch failed, rejects left in working dir > > errors during apply, please fix and refresh > trac_14192-infinity_crystal-bs.patch > > > > > > This persists after trying to qselect guards and recloning the combinat > branch. Is this happening for others or do I need to suck it up and move > on to true 5.7? > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken?
Hi Tom, Yes, I got the same error with sage-5.8.bet4. I rebased Ben Salisbury's patch. It should work now. Ben, please pull from the sage-combinat server before you keep working on your patch! Best, Anne On 3/15/13 2:51 PM, tom d wrote: > From tonight's attempt to apply the queue in Sage 5.7rc0: > > > applying trac_4327-root_system_plot_refactor-nt.patch > patching file sage/combinat/root_system/type_affine.py > Hunk #1 succeeded at 237 with fuzz 2 (offset -54 lines). > applying trac_14143-alcove-path-al.patch > applying trac_14192-infinity_crystal-bs.patch > patching file sage/combinat/crystals/all.py > Hunk #1 FAILED at 11 > 1 out of 1 hunks FAILED -- saving rejects to file > sage/combinat/crystals/all.py.rej > patch failed, unable to continue (try -v) > patch failed, rejects left in working dir > errors during apply, please fix and refresh > trac_14192-infinity_crystal-bs.patch > > > This persists after trying to qselect guards and recloning the combinat > branch. Is this happening for others or do I need to suck it up and move on > to true 5.7? -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] queue broken?
>From tonight's attempt to apply the queue in Sage 5.7rc0: applying trac_4327-root_system_plot_refactor-nt.patch patching file sage/combinat/root_system/type_affine.py Hunk #1 succeeded at 237 with fuzz 2 (offset -54 lines). applying trac_14143-alcove-path-al.patch applying trac_14192-infinity_crystal-bs.patch patching file sage/combinat/crystals/all.py Hunk #1 FAILED at 11 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/crystals/all.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_14192-infinity_crystal-bs.patch This persists after trying to qselect guards and recloning the combinat branch. Is this happening for others or do I need to suck it up and move on to true 5.7? -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7
Hello, The sage -combinat install failed for my sage-5.7 freshly installed with applying trac_12895-subcategory-methods-nt.patch patching file sage/categories/category_singleton.pyx Hunk #3 FAILED at 277 1 out of 3 hunks FAILED -- saving rejects to file sage/categories/category_singleton.pyx.rej patch failed, unable to continue Best, Vincent -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7
Hi Travis, Thank you for your work on this. > I did the quick rebase of #14090 over #11490. > > I also had to do some minor rebasing of the following patches: > > trac_12876_category-fix_abstract_class-nt-rel11521.patch over #9235. > > trac_12895-subcategory-methods-nt.patch and > trac_10963-more_functorial_constructions-nt.patch over #13370. > > After that, the queue applies for me on 5.8.beta1 and starts. Can someone > make sure the same occurs for 5.7? It works for me with sage-5.7. Best, Anne -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7
Hey Nicolas, On Tuesday, February 26, 2013 7:17:34 AM UTC-5, Travis Scrimshaw wrote: > > I'll check as soon as I get in that trac_13872-RC_bijections-ts.patch > still applies and reupload #13605 to trac. However on 5.8.beta1, I get this > reject: > > patching file doc/en/thematic_tutorials/index.rst > Hunk #1 FAILED at 4 > 1 out of 1 hunks FAILED -- saving rejects to file > doc/en/thematic_tutorials/index.rst.rej > patch failed, unable to continue (try -v) > patch failed, rejects left in working dir > errors during apply, please fix and refresh > trac_14090-thematic_tutorials-nt.patch > I did the quick rebase of #14090 over #11490. I also had to do some minor rebasing of the following patches: trac_12876_category-fix_abstract_class-nt-rel11521.patch over #9235. trac_12895-subcategory-methods-nt.patch and trac_10963-more_functorial_constructions-nt.patch over #13370. After that, the queue applies for me on 5.8.beta1 and starts. Can someone make sure the same occurs for 5.7? Thanks, Travis -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7
I'll check as soon as I get in that trac_13872-RC_bijections-ts.patch still applies and reupload #13605 to trac. However on 5.8.beta1, I get this reject: patching file doc/en/thematic_tutorials/index.rst Hunk #1 FAILED at 4 1 out of 1 hunks FAILED -- saving rejects to file doc/en/thematic_tutorials/index.rst.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_14090-thematic_tutorials-nt.patch I'll also look into this and fix this this morning. Best, Travis On Monday, February 25, 2013 10:32:56 PM UTC-5, Franco Saliola wrote: > > > Hello Nicolas, > > Thank you for the quick fix! > > Take care, > Franco > > -- > > On Mon, Feb 25, 2013 at 9:58 PM, Nicolas M. Thiery > > > wrote: > >> On Mon, Feb 25, 2013 at 09:01:52PM -0500, Franco Saliola wrote: >> >$ sage -v >> >Sage Version 5.7, Release Date: 2013-02-19 >> >$ sage -combinat update >> >... >> >applying trac_13605-partition_options-ts.patch >> >patching file >> sage/combinat/rigged_configurations/rigged_configurations.py >> >Hunk #1 FAILED at 930 >> >1 out of 1 hunks FAILED -- saving rejects to file >> >... >> >> I fixed my failing patch as well as Travis. The queue is functional >> again on 5.7. >> >> Cheers, >> Nicolas >> >> PS: Travis, I allowed myself to trim out the following trivial hunk >> out of trac_13605-partition_options-ts.patch >> >> -- >> Nicolas M. Thiéry "Isil" > >> http://Nicolas.Thiery.name/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-combinat-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-combinat-devel+unsubscr...@googlegroups.com . >> To post to this group, send email to >> sage-comb...@googlegroups.com >> . >> Visit this group at >> http://groups.google.com/group/sage-combinat-devel?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7
Hello Nicolas, Thank you for the quick fix! Take care, Franco -- On Mon, Feb 25, 2013 at 9:58 PM, Nicolas M. Thiery wrote: > On Mon, Feb 25, 2013 at 09:01:52PM -0500, Franco Saliola wrote: > >$ sage -v > >Sage Version 5.7, Release Date: 2013-02-19 > >$ sage -combinat update > >... > >applying trac_13605-partition_options-ts.patch > >patching file > sage/combinat/rigged_configurations/rigged_configurations.py > >Hunk #1 FAILED at 930 > >1 out of 1 hunks FAILED -- saving rejects to file > >... > > I fixed my failing patch as well as Travis. The queue is functional > again on 5.7. > > Cheers, > Nicolas > > PS: Travis, I allowed myself to trim out the following trivial hunk > out of trac_13605-partition_options-ts.patch > > -- > Nicolas M. Thiéry "Isil" > http://Nicolas.Thiery.name/ > > -- > You received this message because you are subscribed to the Google Groups > "sage-combinat-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-combinat-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-combinat-devel@googlegroups.com. > Visit this group at > http://groups.google.com/group/sage-combinat-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7 (fixed)
On Mon, Feb 25, 2013 at 09:58:29PM -0500, Nicolas M. Thiery wrote: > PS: Travis, I allowed myself to trim out the following trivial hunk > out of trac_13605-partition_options-ts.patch There it is ... diff --git a/sage/combinat/rigged_configurations/rigged_configurations.py b/sage/combinat/rigged_configurations/rigged_configurations.py --- a/sage/combinat/rigged_configurations/rigged_configurations.py +++ b/sage/combinat/rigged_configurations/rigged_configurations.py @@ -931,4 +931,4 @@ RiggedConfigurations.Element = RiggedCon #x2 = RC2(*x) # ret_list.append([x.to_tensor_product_of_Kirillov_Reshetikhin_tableaux(), # x2.to_tensor_product_of_Kirillov_Reshetikhin_tableaux()]) -#return ret_list \ No newline at end of file +#return ret_list Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] queue broken on 5.7
On Mon, Feb 25, 2013 at 09:01:52PM -0500, Franco Saliola wrote: >$ sage -v >Sage Version 5.7, Release Date: 2013-02-19 >$ sage -combinat update >... >applying trac_13605-partition_options-ts.patch >patching file sage/combinat/rigged_configurations/rigged_configurations.py >Hunk #1 FAILED at 930 >1 out of 1 hunks FAILED -- saving rejects to file >... I fixed my failing patch as well as Travis. The queue is functional again on 5.7. Cheers, Nicolas PS: Travis, I allowed myself to trim out the following trivial hunk out of trac_13605-partition_options-ts.patch -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] queue broken on 5.7
$ sage -v Sage Version 5.7, Release Date: 2013-02-19 $ sage -combinat update ... applying trac_13605-partition_options-ts.patch patching file sage/combinat/rigged_configurations/rigged_configurations.py Hunk #1 FAILED at 930 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/rigged_configurations/rigged_configurations.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_13605-partition_options-ts.patch Abort $ hg qpush -a applying trac_14000-doctests.patch applying trac_7886_conjugacy_classes_combined.patch transaction abort! rollback completed cleaning up working directory...done abort: decoding near 'Javier López Peñ': 'ascii' codec can't decode byte 0xc3 in position 8: ordinal not in range(128)! -- -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] queue broken on 5.6
> sage -combinat install ... des erreurs se sont produites durant l'application, veuillez corriger puis rafraîchir *trac_6495-part1-moving-files-link.patch* > hg qpush -a ... des erreurs se sont produites durant l'application, veuillez corriger puis rafraîchir *trac_6495_separate_inventory.patch* > hg qpush -a ... des erreurs se sont produites durant l'application, veuillez corriger puis rafraîchir *trac_13605-partition_options-ts.patch* > hg qpush -a ... des erreurs se sont produites durant l'application, veuillez corriger puis rafraîchir *trac_8392-check_permutation-ts.patch* plus others -- -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Queue broken under 5.6 because of error in series file with #13862
Hi, It seems that in the series file #13862 is incorrectly marked for merging in 5.7.beta2 whereas trac says that it is merged in 5.6-beta2. As a consequence, the queue does not currently apply to 5.6. I will update the series file and push the change to the queue. Anyone who objects is free to reply quickly or to reverse this change at their leisure:) Andrew -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] queue broken with
Hi! The sage-combinat queue currently seems broken with sage-5.6.rc0: applying trac_10193-graded_enumerated_sets-nt.patch patching file sage/combinat/integer_vector_weighted.py Hunk #1 FAILED at 0 Hunk #4 FAILED at 199 2 out of 4 hunks FAILED -- saving rejects to file sage/combinat/integer_vector_weighted.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_10193-graded_enumerated_sets-nt.patch Best, Anne -- 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.
Re: [sage-combinat-devel] queue broken for sage 5.3
On Tue, Sep 18, 2012 at 07:47:44AM -0700, Anne Schilling wrote: > Unfortunately, nobody can push until Nicolas fixes his patches! Oops, sorry, there was a missing guard on the patch I had just added. Well, it was an easy fix. Pushed. Cheers, Nicolas -- Nicolas M. Thiéry "Isil" 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.
Re: [sage-combinat-devel] queue broken for sage 5.3
Franco Saliola writes: > It's not clear what you are desperate for. The command I need some of the patches... > if you just want a working version old of the queue, the following might work > > cd SAGE_ROOT/devel/sage-combinat > sage -hg update -r XXX > sage -hg qpop -a > sage -hg qpush -a > > Here, XXX is a version of the queue that was still working on your > version of sage (if I don't make a mistake, for me XXX=7527 was > working for 5.3.rc1). Please report if this helps since others might > want to do the same if the queue is broken. > > Best, Christian Anne Schilling writes: > hg update -r 7570:f738ef433157 > > works with sage-5.3. Unfortunately, nobody can push until Nicolas > fixes his patches! Many many thanks!!! Martin -- 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.
Re: [sage-combinat-devel] queue broken for sage 5.3
hg update -r 7570:f738ef433157 works with sage-5.3. Unfortunately, nobody can push until Nicolas fixes his patches! Best, Anne On 9/18/12 7:20 AM, Christian Stump wrote: >> I'm rather desperate (I didn't update because I needed a stable >> environment, but now it seems that the operating system was updated >> :-()) > > if you just want a working version old of the queue, the following might work > > cd SAGE_ROOT/devel/sage-combinat > sage -hg update -r XXX > sage -hg qpop -a > sage -hg qpush -a > > Here, XXX is a version of the queue that was still working on your > version of sage (if I don't make a mistake, for me XXX=7527 was > working for 5.3.rc1). Please report if this helps since others might > want to do the same if the queue is broken. > > Best, Christian -- 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.
Re: [sage-combinat-devel] queue broken for sage 5.3
> I'm rather desperate (I didn't update because I needed a stable > environment, but now it seems that the operating system was updated > :-()) if you just want a working version old of the queue, the following might work cd SAGE_ROOT/devel/sage-combinat sage -hg update -r XXX sage -hg qpop -a sage -hg qpush -a Here, XXX is a version of the queue that was still working on your version of sage (if I don't make a mistake, for me XXX=7527 was working for 5.3.rc1). Please report if this helps since others might want to do the same if the queue is broken. Best, Christian -- 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.
Re: [sage-combinat-devel] queue broken for sage 5.3
On Tue, Sep 18, 2012 at 10:08 AM, Martin Rubey wrote: > Hi there, > > I just installed sage 5.3 from source and did > > sage -combinat install > > and got > > patching file sage/categories/category.py > Hunk #6 FAILED at 1803 > 1 out of 7 hunks FAILED -- saving rejects to file > sage/categories/category.py.rej > unable to find 'sage/categories/category_with_axiom.py' for patching > 1 out of 1 hunks FAILED -- saving rejects to file > sage/categories/category_with_axiom.py.rej > patch failed, unable to continue (try -v) > patch failed, rejects left in working dir > errors during apply, please fix and refresh > impose_mro_for_category_classes-nt.patch > Abort > > I'm rather desperate (I didn't update because I needed a stable > environment, but now it seems that the operating system was updated > :-()) It's not clear what you are desperate for. The command sage -b main will return you to the main sage branch. This will give you a working copy of sage without any combinat patches applied. Franco -- -- 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.
[sage-combinat-devel] queue broken for sage 5.3
Hi there, I just installed sage 5.3 from source and did sage -combinat install and got patching file sage/categories/category.py Hunk #6 FAILED at 1803 1 out of 7 hunks FAILED -- saving rejects to file sage/categories/category.py.rej unable to find 'sage/categories/category_with_axiom.py' for patching 1 out of 1 hunks FAILED -- saving rejects to file sage/categories/category_with_axiom.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh impose_mro_for_category_classes-nt.patch Abort I'm rather desperate (I didn't update because I needed a stable environment, but now it seems that the operating system was updated :-()) Many thanks, Martin -- 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.
Re: [sage-combinat-devel] queue broken
Hi Anne, > sage -hg qselect > sage -hg qpush -a I don't know why I constantly forget to do so. Thanks for the reminder... -- 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.
Re: [sage-combinat-devel] queue broken
Hi Christian, Did you try sage -hg qselect and then sage -hg qpush -a I had changed the guards on trac_11305-rigged_configurations-ts.patch and the patch trac_13403-bijection_KR_crystals_tableaux-ts.patch is based on it. That's what happened for me the first time I applied the queue after the change, but now it works. Best, Anne On 8/30/12 2:14 AM, Christian Stump wrote: > Hi, > > trac_13403-bijection_KR_crystals_tableaux-ts.patch doesn't apply on > 5.2 . Since it is the newest version, we might want the queue to apply > there (even if most people updated to 5.3.??? already - I am now doing > so with 5.3.rc0). > > Christian -- 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.
[sage-combinat-devel] queue broken
Hi, trac_13403-bijection_KR_crystals_tableaux-ts.patch doesn't apply on 5.2 . Since it is the newest version, we might want the queue to apply there (even if most people updated to 5.3.??? already - I am now doing so with 5.3.rc0). Christian -- 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.
[sage-combinat-devel] queue broken
Hi! The patch queue is currently broken with sage-5.1. Nicolas claims that he fixed this before lunch, so Chris, did you make changes since that break the queue? Thanks, Anne -- 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.
Re: [sage-combinat-devel] queue broken
On Mon, May 21, 2012 at 01:24:38PM -0700, Anne Schilling wrote: > On 5/21/12 12:52 AM, Nicolas M. Thiery wrote: > > -- > > To avoid import loops, I try to stick to the following order: > > > > - Python modules > > - Misc > > - Categories > > - Stuff in sage.structure > > - Basic parents (NN, QQ, ...) > > - Rest of the stuff > > > > and a module in one of the above items should only import modules from > > higher items. E.g. a module in sage.categories can import from a > > module in sage.misc, but not reciprocally. > > -- > > Is this a rule for the import statements at the beginning of the file? Yes. Well, that's the rule I follow myself, and would tend to recommend. I guess it's time to open the debate about this on sage-devel (though I won't be able to do it before I come back from China). > I am currently implementing an __iter__ method for the category of > Crystals. But without any further import statements, I get an import > loop just by adding this method. This should not occur. Make sure that this really is the only change. > How can I debug this? Usually the traceback is quite informative on which module import which. Then you have to figure out where it's most natural to break the loop. Cheers, Nicolas -- Nicolas M. Thiéry "Isil" 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.
Re: [sage-combinat-devel] queue broken
On 5/21/12 12:52 AM, Nicolas M. Thiery wrote: > On Mon, May 21, 2012 at 09:32:02AM +0200, Christian Stump wrote: >> Or are categories always considered to be "lower" ? > > Taken from: > http://groups.google.com/group/sage-combinat-devel/msg/15221ad8016af193 > (which btw should be discussed on sage-devel and put in the dev manual) > -- > To avoid import loops, I try to stick to the following order: > > - Python modules > - Misc > - Categories > - Stuff in sage.structure > - Basic parents (NN, QQ, ...) > - Rest of the stuff > > and a module in one of the above items should only import modules from > higher items. E.g. a module in sage.categories can import from a > module in sage.misc, but not reciprocally. > -- Is this a rule for the import statements at the beginning of the file? I am currently implementing an __iter__ method for the category of Crystals. But without any further import statements, I get an import loop just by adding this method. How can I debug this? Cheers, Anne -- 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.
Re: [sage-combinat-devel] queue broken
On Mon, May 21, 2012 at 09:55:15AM +0200, Christian Stump wrote: > thx, but don't forget to push, please! Good point :-) Done. Nicolas -- Nicolas M. Thiéry "Isil" 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.
Re: [sage-combinat-devel] queue broken
> "Fixed". See other thread (NCSF/trac_12940_affine_permutations-td.patch) thx, but don't forget to push, please! -- 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.
Re: [sage-combinat-devel] queue broken
On Mon, May 21, 2012 at 09:36:57AM +0200, Christian Stump wrote: > unfortunately, the queue is still broken at > trac_12940_affine_permutations-td.patch. "Fixed". See other thread (NCSF/trac_12940_affine_permutations-td.patch) Nicolas -- Nicolas M. Thiéry "Isil" 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.
Re: [sage-combinat-devel] queue broken
On Mon, May 21, 2012 at 09:32:02AM +0200, Christian Stump wrote: > Or are categories always considered to be "lower" ? Taken from: http://groups.google.com/group/sage-combinat-devel/msg/15221ad8016af193 (which btw should be discussed on sage-devel and put in the dev manual) -- To avoid import loops, I try to stick to the following order: - Python modules - Misc - Categories - Stuff in sage.structure - Basic parents (NN, QQ, ...) - Rest of the stuff and a module in one of the above items should only import modules from higher items. E.g. a module in sage.categories can import from a module in sage.misc, but not reciprocally. -- According to the above rules, a category file should not import stuff like DiGraph or CombinatorialFreeModule (but that's ok within its methods, or using lazy imports). > why does something "low level" like combinatorial free module or > modules with basis import weyl groups ? That's because of the "all" in: from sage.categories.all import ModulesWithBasis Given the above rules, it's in principle ok for combinatorial free module to import all categories. However, for extra safety, it would indeed be better to use "from sage.categories.modules_with_basis". Cheers, Nicolas -- Nicolas M. Thiéry "Isil" 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.
Re: [sage-combinat-devel] queue broken
Hi, unfortunately, the queue is still broken at trac_12940_affine_permutations-td.patch. Christian -- 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.
Re: [sage-combinat-devel] queue broken
Hi! > There is a break in sage between patch > > trac_12895-subcategory-methods-nt.patch > trac_8327_universal_cyclotomic_field-cs.patch fixed -- it was actually Mark closing the last link for the import loop by importing from sage.graphs.digraph import DiGraph in categories/weyl_groups. I updated his patch accordingly (Mark, please pull my changes before changing your patch!). I still don't know how to properly do the importing. E.g., here we have ... --> 243 from sage.combinat.free_module import CombinatorialFreeModule ... ---> 28 from sage.categories.all import ModulesWithBasis ... --> 126 from weyl_groups import WeylGroups 127 from finite_weyl_groups import FiniteWeylGroups 128 from affine_weyl_groups import AffineWeylGroups why does something "low level" like combinatorial free module or modules with basis import weyl groups ? Or are categories always considered to be "lower" ? Best, Christian -- 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.
[sage-combinat-devel] queue broken
Hi! There is a break in sage between patch trac_12895-subcategory-methods-nt.patch and trac_8327_universal_cyclotomic_field-cs.patch Christian or Nicolas, could you please fix this in your patches? Thanks, Anne Removing /Applications/sage-5.0/local/lib/python2.7/site-packages/sage-0.0.0-py2.7.egg-info Writing /Applications/sage-5.0/local/lib/python2.7/site-packages/sage-0.0.0-py2.7.egg-info -- | Sage Version 5.0, Release Date: 2012-05-14 | | Type notebook() for the GUI, and license() for information.| -- --- AttributeErrorTraceback (most recent call last) /Applications/sage-5.0/local/lib/python2.7/site-packages/IPython/ipmaker.pyc in force_import(modname, force_reload) 61 reload(sys.modules[modname]) 62 else: ---> 63 __import__(modname) 64 65 /Applications/sage-5.0/local/bin/ipy_profile_sage.py in () 5 preparser(True) 6 > 7 import sage.all_cmdline 8 sage.all_cmdline._init_cmdline(globals()) 9 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/all_cmdline.py in () 12 try: 13 ---> 14 from sage.all import * 15 from sage.calculus.predefined import x 16 preparser(on=True) /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/all.py in () 72 from sage.libs.all import * 73 ---> 74 from sage.rings.all import * 75 from sage.matrix.all import * 76 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/rings/all.pyc in () 166 167 # Universal Cyclotomic Field --> 168 from universal_cyclotomic_field.all import * 169 170 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/rings/universal_cyclotomic_field/all.py in () 1 > 2 from universal_cyclotomic_field import E, UniversalCyclotomicField 3 UCF = UniversalCyclotomicField() 4 5 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/misc/classcall_metaclass.so in sage.misc.classcall_metaclass.ClasscallMetaclass.__call__ (sage/misc/classcall_metaclass.c:820)() 323 324 --> 325 326 327 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/misc/cachefunc.so in sage.misc.cachefunc.WeakCachedFunction.__call__ (sage/misc/cachefunc.c:4293)() 876 877 --> 878 879 880 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/structure/unique_representation.pyc in __classcall__(cls, *args, **options) 464 True 465 """ --> 466 instance = typecall(cls, *args, **options) 467 assert isinstance( instance, cls ) 468 if instance.__class__.__reduce__ == UniqueRepresentation.__reduce__: /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/misc/classcall_metaclass.so in sage.misc.classcall_metaclass.typecall (sage/misc/classcall_metaclass.c:1140)() 511 512 --> 513 514 515 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/rings/universal_cyclotomic_field/universal_cyclotomic_field.pyc in __init__(self) 241 """ 242 # the data is stored as linear combinations of elements in the Zumbroich Basis --> 243 from sage.combinat.free_module import CombinatorialFreeModule 244 self._data = CombinatorialFreeModule( QQ, ZumbroichBasisIndices() ) 245 from sage.categories.fields import Fields /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/combinat/free_module.py in () 26 from sage.misc.all import lazy_attribute 27 from sage.categories.poor_man_map import PoorManMap ---> 28 from sage.categories.all import ModulesWithBasis 29 from sage.combinat.dict_addition import dict_addition, dict_linear_combination 30 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/categories/all.py in () 125 from coxeter_groups import CoxeterGroups 126 from finite_coxeter_groups import FiniteCoxeterGroups --> 127 from weyl_groups import WeylGroups 128 from finite_weyl_groups import FiniteWeylGroups 129 from affine_weyl_groups import AffineWeylGroups /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/categories/weyl_groups.py in () 14 from sage.rings.infinity import infinity 15 from sage.rings.rational_field import QQ 15 from sage.graphs.dot2tex_utils import assert_have_dot2tex /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/groups/perm_gps/__init__.py in () > 1 2 3 import all 4 5 /Applications/sage-5.0/local/lib/python2.7/site-packages/sage/groups/perm_gps/all.py in () 1 > 2 3 import permgroup as pg 4 5 from permgroup_named import (SymmetricGroup, A
Re: [sage-combinat-devel] queue broken
On 5/13/12 10:32 PM, Martin Rubey wrote: > Following advice of Volker, I installed 5.0rc1. This install went > fine. However, the combinat queue does not apply: > > patching file sage/combinat/partition.py > Hunk #1 FAILED at 428 > 1 out of 1 hunks FAILED -- saving rejects to file > sage/combinat/partition.py.rej > patch failed, unable to continue (try -v) > patch failed, rejects left in working dir > errors during apply, please fix and refresh > partition_k_boundary_speedup-fh.patch > > since this happens frequently: is there a way for me to fix it and help? In fact, I also get this reject in sage-5.0.beta14: applying dyck_word_print-fh.patch applying partition_constructor_speedup-fh.patch applying skew_partitions_init_speedup-fh.patch applying partition_k_boundary_speedup-fh.patch patching file sage/combinat/partition.py Hunk #1 FAILED at 428 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/partition.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh partition_k_boundary_speedup-fh.patch Abort Florent, could you fix this? Thanks, Anne -- 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.
Re: [sage-combinat-devel] queue broken
On 5/13/12 10:54 PM, Martin Rubey wrote: > Anne Schilling writes: > >> On 5/13/12 10:32 PM, Martin Rubey wrote: >>> Following advice of Volker, I installed 5.0rc1. This install went >>> fine. However, the combinat queue does not apply: >>> >>> patching file sage/combinat/partition.py >>> Hunk #1 FAILED at 428 >>> 1 out of 1 hunks FAILED -- saving rejects to file >>> sage/combinat/partition.py.rej >>> patch failed, unable to continue (try -v) >>> patch failed, rejects left in working dir >>> errors during apply, please fix and refresh >>> partition_k_boundary_speedup-fh.patch >>> >>> since this happens frequently: is there a way for me to fix it and help? >> >> I just got precisely the same problem. This is due to the fact that nobody >> has >> yet tried to run the queue with 5.0.rc1. Since this is Florent's patch it is >> probably best to wait till he refreshes it. >> >> Martin, as far as I understood Volker his patch is already in 5.0.rc1, so you >> won't need the sage-combinat queue. You can just do >> >> sage -br >> >> and try his commands. > > Yes, but I need combinat to generate the data :-) Then try to disable the offending patch in your series file and hope that nothing else after that depends on it ... otherwise you might have to wait till Florent refreshes his patch. Best, Anne -- 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.
Re: [sage-combinat-devel] queue broken
Anne Schilling writes: > On 5/13/12 10:32 PM, Martin Rubey wrote: >> Following advice of Volker, I installed 5.0rc1. This install went >> fine. However, the combinat queue does not apply: >> >> patching file sage/combinat/partition.py >> Hunk #1 FAILED at 428 >> 1 out of 1 hunks FAILED -- saving rejects to file >> sage/combinat/partition.py.rej >> patch failed, unable to continue (try -v) >> patch failed, rejects left in working dir >> errors during apply, please fix and refresh >> partition_k_boundary_speedup-fh.patch >> >> since this happens frequently: is there a way for me to fix it and help? > > I just got precisely the same problem. This is due to the fact that nobody has > yet tried to run the queue with 5.0.rc1. Since this is Florent's patch it is > probably best to wait till he refreshes it. > > Martin, as far as I understood Volker his patch is already in 5.0.rc1, so you > won't need the sage-combinat queue. You can just do > > sage -br > > and try his commands. Yes, but I need combinat to generate the data :-) Martin -- 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.
Re: [sage-combinat-devel] queue broken
On 5/13/12 10:32 PM, Martin Rubey wrote: > Following advice of Volker, I installed 5.0rc1. This install went > fine. However, the combinat queue does not apply: > > patching file sage/combinat/partition.py > Hunk #1 FAILED at 428 > 1 out of 1 hunks FAILED -- saving rejects to file > sage/combinat/partition.py.rej > patch failed, unable to continue (try -v) > patch failed, rejects left in working dir > errors during apply, please fix and refresh > partition_k_boundary_speedup-fh.patch > > since this happens frequently: is there a way for me to fix it and help? I just got precisely the same problem. This is due to the fact that nobody has yet tried to run the queue with 5.0.rc1. Since this is Florent's patch it is probably best to wait till he refreshes it. Martin, as far as I understood Volker his patch is already in 5.0.rc1, so you won't need the sage-combinat queue. You can just do sage -br and try his commands. Best, Anne -- 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.
[sage-combinat-devel] queue broken
Following advice of Volker, I installed 5.0rc1. This install went fine. However, the combinat queue does not apply: patching file sage/combinat/partition.py Hunk #1 FAILED at 428 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/partition.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh partition_k_boundary_speedup-fh.patch since this happens frequently: is there a way for me to fix it and help? Martin -- 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.
[sage-combinat-devel] queue broken
Salut, trac_10335-permgroup_domain-mh does not apply properly on 6.4.1. Best, Christian -- 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.
[sage-combinat-devel] queue broken
Sorry, Due to conflict with trac_8898 the combinat queue is currently broken... wait few minutes before pull and push. Vincent -- 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.
