Thank you Michael Orlitzky, it worked after cleaning the previous builds. I did, $ make maintainer-clean
Which is equivalent to, according to the Makefile, $ make distclean bootstrap-clean I thought the installation would replace the previous builds when new system packages are available. It is preferring old local spkg installs, if already present, than new versions in system. But if it is spkg only it is going for update. Is it needed to be fixed or is it usual? On Sat, 13 Jan 2024, 1:26 am Michael Orlitzky, <mich...@orlitzky.com> wrote: > On Fri, 2024-01-12 at 09:25 -0800, Niranjana K M wrote: > > Should I have had started by cleaning the previous builds? It may be > still > > using old Cython spkg, built when it was sage 10.0 release. Because in > venv > > site-packages, it still says > > sage/venv/lib64/python3.11/site-packages/Cython-0.29.32.dist-info. > > Very possibly. > > > > What are the right sequence of commands to update an existing sagemath > git > > installation? I just did: > > Personally I run `git clean -x -f -d` before ./bootstrap to remove > absolutely everything that isn't part of the repository. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/799606af358fb48cff6eeeca999a877c3e323ff3.camel%40orlitzky.com > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAMcUJ1vFg%2BoSndKNsKEW76ANiGYmxhb6sZwv1BAADh88QK_fqA%40mail.gmail.com.
