On Tue, Sep 1, 2009 at 8:03 AM, Stan Schymanski<schym...@gmail.com> wrote:
>
> Hi David,
>
> Thanks for your help. Yes, I did sage -clone myclone, which returned an
> error message, so I changed back to main (sage -b main), started sage,
> tried to apply the same patch in main without success and then I thought
> I should revert to the original by typing hg_sage.revert('--all')
> - without success, as described before.
>
...
>
> I only now noticed that sage was looking for something in my sage-4.0.2
> folder, which does not exist any more. Does this imply that my previous
> sage -upgrade did not work?
>
> Maybe I should recompile from scratch (?). Or just do sage -ba as
> suggested in the error message? Sorry about the mess.
Yes, I would create a new version by compiling from source. It seems like
your upgrade got corrupted somehow maybe?
>
> Cheers,
> Stan
>
> David Joyner wrote:
>> On Tue, Sep 1, 2009 at 6:03 AM, Stan Schymanski<schym...@gmail.com> wrote:
>>
>>> Dear all,
>>>
>>>
>> ...
>>
>>> I tried different ways of applying a patch with the only success that
>>> I probably made a bit of a
>>> mess in my repository. Is there a way to revert it back to a clean
>>> 4.1.1
>>> install?
>>>
>>
>> I'm not sure what you did to create the new repo.Can you provide details?
>>
>> For example, if you started with a new install of Sage, then did
>> sage -clone myclone
>> and then applied patched in myclone, you can
>> "clean it up" and start afresh by typing
>> sage -b main
>> sage -clone myclone2
>>
>> Is that what you want?
>>
>>
>>
>>> Thanks for your help!
>>>
>>> Stan
>>>
>>
>> >
>>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
