How to move Sage to a different computer?

[Simon King]

Hi!

I have some Sage installation on one laptop, including many branches.
Now I want to move on a different laptop, keeping these branches.

I tried to do something like "cp -r", then checking out the latest
development version. I think it worked so far. But, when trying "make
distclean" or "make", I get a lot of AssertionErrors: Apparently
sage_bootstrap/package.py expects the package types 'base',
'standard', 'optional' or 'experimental', but nowadays many packages
have the type 'pip'.

How to find out what went wrong? And: What would be the recommended way
to get a working Sage installation on the new laptop that can use my old
branches?

Best regards,
Simon

[Simon King]

PS:

When I go to the master branch instead of develop branch, I do not have
the problem with the spkg type "pip" --- but "make" soon fails, because
when the "patch" spkg is built, configure claims that the C compiler
cannot create executables - which is wrong: I tested, and I can create
an executable from some "Hello World" program.

Again: How to debug? The only "failed program" mentioned in config.log
is with "#include <ac_nonexistent.h>" -- so, it is supposed to fail.

Best regards,
Simon

[Dima Pasechnik]

On Sat, Nov 13, 2021 at 10:42 PM Simon King <simon...@uni-jena.de> wrote:
> I have some Sage installation on one laptop, including many branches.
> Now I want to move on a different laptop, keeping these branches.
>
> I tried to do something like "cp -r", then checking out the latest
> development version. I think it worked so far. But, when trying "make
> distclean" or "make", I get a lot of AssertionErrors:

hmm, if you really checked out the latest version and have done
`make distclean`, then it should have worked (it does work, you know).

Do you mean to say that you merged in (or rebased over) the latest
develop branch, and getting errors trying to build?

Dima

> Apparently
> sage_bootstrap/package.py expects the package types 'base',
> 'standard', 'optional' or 'experimental', but nowadays many packages
> have the type 'pip'.
>
> How to find out what went wrong? And: What would be the recommended way
> to get a working Sage installation on the new laptop that can use my old
> branches?
>
> Best regards,
> Simon
>

> --
> You received this message because you are subscribed to the Google Groups "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/smpf07%24588%241%40ciao.gmane.io.

[Simon King]

Hi Dima,

On 2021-11-14, Dima Pasechnik <dim...@gmail.com> wrote:
> hmm, if you really checked out the latest version and have done
> `make distclean`, then it should have worked (it does work, you know).
>
> Do you mean to say that you merged in (or rebased over) the latest
> develop branch, and getting errors trying to build?

I did git checkout develop and git pull. Then, git status shows a lot of
"Unversionierte Dateien", in build/..., but also many things in src/....
No idea if that is because of permissions being corrupted when using
"cp -r". "git reset --hard" is no remedy.

Anyway, git log tells me the commit is
6ec717a56dcb0fd629ca850d9b9391ea8d96ccac,
Updated SageMath version to 9.5.beta6

Now, make distclean complains that the Sage source tree is unconfigured,
and I shall type "./configure". So, I did. Famous last words:

configure: error: The content of
"/home/king/Sage/git/py3/build/pkgs/beautifulsoup/type" must be
'base', 'standard', 'optional', or 'experimental'

autoreconf, to rebuild the configure script, didn't help either.

Best regards,
Simon

[Simon King]

PS:

On 2021-11-14, Simon King <simon...@uni-jena.de> wrote:
> On 2021-11-14, Dima Pasechnik <dim...@gmail.com> wrote:
>> hmm, if you really checked out the latest version and have done
>> `make distclean`, then it should have worked (it does work, you know).

In other words: With the latest develop version, even "make distclean"
didn't work. And with the latest master version, "make distclean" did
eventually work, but "make" didn't.

Best regards,
Simon

[Dima Pasechnik]

Hi Simon,

On Sun, Nov 14, 2021 at 1:26 AM Simon King <simon...@uni-jena.de> wrote:
>
> Hi Dima,
>
> On 2021-11-14, Dima Pasechnik <dim...@gmail.com> wrote:
> > hmm, if you really checked out the latest version and have done
> > `make distclean`, then it should have worked (it does work, you know).
> >
> > Do you mean to say that you merged in (or rebased over) the latest
> > develop branch, and getting errors trying to build?
>
> I did git checkout develop and git pull. Then, git status shows a lot of
> "Unversionierte Dateien", in build/..., but also many things in src/....
> No idea if that is because of permissions being corrupted when using
> "cp -r". "git reset --hard" is no remedy.

You need to clean old stuff, I suppose

git clean -fdx

should do it.

HTH
Dima

>
> Anyway, git log tells me the commit is
> 6ec717a56dcb0fd629ca850d9b9391ea8d96ccac,
> Updated SageMath version to 9.5.beta6
>
> Now, make distclean complains that the Sage source tree is unconfigured,
> and I shall type "./configure". So, I did. Famous last words:
>
> configure: error: The content of
> "/home/king/Sage/git/py3/build/pkgs/beautifulsoup/type" must be
> 'base', 'standard', 'optional', or 'experimental'
>
> autoreconf, to rebuild the configure script, didn't help either.
>
> Best regards,
> Simon
>
>

> --
> You received this message because you are subscribed to the Google Groups "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/smpojh%24h4k%241%40ciao.gmane.io.

[Simon King]

Dear Dima,

On 2021-11-14, Dima Pasechnik <dim...@gmail.com> wrote:
> You need to clean old stuff, I suppose
>
> git clean -fdx
>
> should do it.

Thank you! It seems that it did the trick.

In the development version, "make" now says to do "./configure" first
(which in the past was done automatically, but I guess ./configure is
the normal thing to do before "make" in most software), which
recommended to install further stuff (which I did), and now "make" is
running!

Best regards,
Simon

[Dima Pasechnik]

there are situations, where ./configure (or ./bootstrap+./configure)
has to be run manually,
even though make might invoke them in some way, too, but the latter is
not always with correct options.

So it's better to deprecate using make alone.

Dima

> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/smqhgq%24dun%241%40ciao.gmane.io.

[Simon King]

Hi Dima,

just for the record: Both the master and the develop version are now
built and they work.

Thank you! Best regards,
Simon