Re: [sage-release] Re: Sage 8.7.beta6 released

2019-03-08 Thread kcrisman


> this is too blanket :-) 
> e.g. in this particular case it suffices to manually remove 
> SAGE_LOCAL/share/gap 
> and rebuild gap spkg 
> (and then run make, naturally...) 
>
>
Great, thanks!  Apparently that sufficed.
 

> Certainly there is never a guarantee that a "git pull"+"make" would 
> just work, as 
> the current state could be beyond repair... 
>
>
Yes, of course!  In this case I had a working Sage install at beta1 or 
beta2, though.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.7.beta6 released

2019-03-08 Thread Dima Pasechnik
On Fri, Mar 8, 2019 at 12:40 PM kcrisman  wrote:
>
>
>
> On Friday, March 8, 2019 at 3:24:45 AM UTC-5, Dima Pasechnik wrote:
>>
>> https://trac.sagemath.org/ticket/27388 fixed the permissions, but
>> because it's an upgrade from the state where there was a read-only
>> file, it breaks (on OSX only)
>
>
> Would that mean that, in general, upgrades from beta4 (which seems to be the 
> last version without this problem, according to one of the tickets) via git 
> pull and make will break indefinitely?  Should we have a blanket 
> recommendation to rebuild from scratch?

this is too blanket :-)
e.g. in this particular case it suffices to manually remove SAGE_LOCAL/share/gap
and rebuild gap spkg
(and then run make, naturally...)

Certainly there is never a guarantee that a "git pull"+"make" would
just work, as
the current state could be beyond repair...

> Thanks for any advice here - luckily from testing the app version I have some 
> still working Sage installs, but I like having my devel version separately 
> working.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.7.beta6 released

2019-03-08 Thread kcrisman


On Friday, March 8, 2019 at 3:24:45 AM UTC-5, Dima Pasechnik wrote:
>
> https://trac.sagemath.org/ticket/27388 fixed the permissions, but 
> because it's an upgrade from the state where there was a read-only 
> file, it breaks (on OSX only) 
>

Would that mean that, in general, upgrades from beta4 (which seems to be 
the last version without this problem, according to one of the tickets) via 
git pull and make will break indefinitely?  Should we have a blanket 
recommendation to rebuild from scratch?  Thanks for any advice here - 
luckily from testing the app version I have some still working Sage 
installs, but I like having my devel version separately working.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.7.beta6 released

2019-03-08 Thread Dima Pasechnik
https://trac.sagemath.org/ticket/27388 fixed the permissions, but
because it's an upgrade from the state where there was a read-only
file, it breaks (on OSX only)

On Thu, Mar 7, 2019 at 4:50 PM kcrisman  wrote:
>
> upgrading from some early 8.6 beta, I get something weird with file 
> permissions on gap.  Everything seems to go well, but:
>
>
>
> pkg/laguna-3.9.0 -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg
>
> pkg/polenta-1.3.8 -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg
>
> pkg/polycyclic-2.14 -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg
>
> pkg/resclasses-4.7.1 -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg
>
> pkg/sophus-1.24 -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg
>
> pkg/tomlib-1.2.7 -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/share/gap/pkg
>
> ../gap -> 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/bin/gap
>
>
> real 2m48.230s
>
> user 1m30.082s
>
> sys 0m59.461s
>
> Copying package files from temporary location 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst to 
> /Users/.../sage/local
>
> cp: cannot overwrite directory 
> /Users/.../sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src 
> with non-directory 
> /Users/.../sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/.../sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src
>
> cp: /Users/.../sage/local/./share/gap/pkg/ctbllib/tst/docxpl.tst: Permission 
> denied
>
> 
>
> Error copying files for gap-4.10.0.p0.
>
> 
>
>
> I have a feeling that there is a typo of some kind in the commit
>
>
> https://github.com/sagemath/sage/commit/ca94bd97d73ee544c273fbb28cb774b3af12ecb6#diff-a9a04fa360dca60daa488241916fdb9c
>
>
> though I can't say immediately where, because the full line is
>
>
> non-directory 
> /Users/karl.crisman/Downloads/sage/local/var/tmp/sage/build/gap-4.10.0.p0/inst/Users/karl.crisman/Downloads/sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src
>
>
> and indeed I don't see why there should be a file that has the entire path to 
> sage/local TWICE; probably should use a temp file if for some reason that was 
> the desired behavior? I did not do anything unusual in this setup.
>
>
> Thanks!  Everything else seems to be progressing normally.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.