Hi! Working on #11298, the patchbot claims that my patch fails to apply. But it seems to me that the patchbot is in fact considering a patch from a different ticket, accidentally from me as well.
Details: #9976 (which is merged in some alpha version) is a dependency for #11298. In my patch queue, indeed I have first the patches from #9976, directly followed by the patch from #11298. However, this is the short log for #11298 produced by the patchbot: 2011-05-05 03:10:51 -0700 hg qpush trac11115-cached_cython.patch applying trac11115-cached_cython.patch patching file sage/misc/lazy_attribute.py Hunk #5 FAILED at 538 1 out of 5 hunks FAILED -- saving rejects to file sage/misc/ lazy_attribute.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac11115- cached_cython.patch popping trac11115-cached_cython.patch patch queue now empty None 2011-05-05 03:11:02 -0700 11 seconds Why the heck is it trying to apply trac11115-cached_cython.patch? It comes later in my patch queue, and is in fact not mentioned at all on the ticket? Do you have any explanation for that behaviour? How can I convince that patchbot that it should start with sage-4.7, apply #9976 and then proceed with #11298? Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
