Hi Alex, On Mon, Feb 1, 2010 at 8:23 PM, Alex Ghitza <[email protected]> wrote:
<SNIP> > Could it be that one of the repositories had uncommited changes? There is no uncommitted changes for the following files: * sage-banner * sage-gdb-commands * sage-maxima.lisp * sage-verify-pyc Before packaging up the Sage 4.3.2.alpha1 source tarball, I committed changes using Mercurial so that these files have their executable bits turned off, as they should be. What you reported above is harmless. Mercurial notices that the executable bits of these files are now off, whereas previously they were turned on for your Sage installation. To proceed with the upgrade, you could check in the changes that Mercurial reports. But in actual fact, there's not any changes to the content of these files. -- Regards Minh Van Nguyen -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
