My guess would be that you have another "sage" in the path, and when you run "sage -sh sage-fix-pkg-checksums" then you recompute the checksums for that installation. Run "./sage -sh sage-fix-pkg-checksums" from the SAGE_ROOT folder that you are working with. It doesn't matter what directory you are in, in only matters to call the right sage installation...
On Wednesday, July 2, 2014 2:17:11 PM UTC-4, Emmanuel Charpentier wrote: > > I wanted to update sages's R to 3.1.0. In order to do so, and following the > guide <http://www.sagemath.org/doc/developer/packaging.html> : > > - I grabbed the current (6.3beta5) tarball, compiled and tested it. > - I created a local (r3.1 branch) from the develop branch > - I replaced upstream/r-3.0.2.tar.bz2 by upstream/r-3.1.0.tar.gz > - I reviewed the cecessary changes in build/pkgs/r : they seemed > limited to updating package-version.txt, which I did. > > so far so good. but : > > > - I tried to run sage -sh sage-fix-pkg-checksums in upstream : I did > *not* see r-3.1.0 listed, but saw the (now absent) r-3.0.2. > - I tried sage -i r-3.1.0 : sage tried to download somethiong with > that name from the sage repository > - I tried to type "make" in the tree rot : ditto. > > > I certainly missed something : the build system still contains information > tellling it that R is still 3.0.2, but I do nit know how to fix it. > > A bit of helping hand would be useful. > > PS I did not (yet) create a track ticket to make this officuial : I wanted > first to check that I was able to create the patch. > > -- > Emmanuel Charpentier > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
