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

> > > This has also been reported on devel [1,2] and might affect more Mac > users when upgrading to 8.9. Perhaps a copy of sage-dist-helpers could be > added back to src/bin for some deprecation period? > > A symlink could do it. > Very nice sleuthing all around. I do recommend something

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

On Thu, Aug 15, 2019 at 6:58 PM Markus Wageringel wrote: > > This also happened to me a few weeks ago. The underlying problem seems to be > that the uninstall script fails because it tries to call sage-dist-helpers, > but cannot find it. This file has recently been moved from src/bin to >

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

Yes, that fits. Now that I know to look, I see buried in my gap install log Uninstalling existing 'gap' Running pre-uninstall script for 'gap' /Users/jpalmier/Desktop/Sage/git/sage/local/var/lib/sage/scripts/gap/spkg-prerm: line 13:

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

This also happened to me a few weeks ago. The underlying problem seems to be that the uninstall script fails because it tries to call sage-dist-helpers, but cannot find it. This file has recently been moved from src/bin to build/bin, which the uninstall script cannot know about. Once upgraded

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

On Thu, Aug 15, 2019 at 2:22 PM kcrisman wrote: > > >> That's expected. The package build directory is under SAGE_LOCAL >> ($SAGE_LOCAL/var/tmp/sage/build/gap-4.10.0.p0) but the file's >> destination path ($SAGE_LOCAL) is appended to this. This is how it's >> supposed to work (DESTDIR

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

> That's expected. The package build directory is under SAGE_LOCAL > ($SAGE_LOCAL/var/tmp/sage/build/gap-4.10.0.p0) but the file's > destination path ($SAGE_LOCAL) is appended to this. This is how it's > supposed to work (DESTDIR installation). > > It's probably too late to diagnose now

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

On Thu, Mar 7, 2019 at 5: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 -> >

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

this is a MacOS only bug. Someone running it should work on fix... On Wed, 14 Aug 2019 20:35 kcrisman, wrote: > > > On Friday, March 8, 2019 at 8:18:02 AM UTC-5, Dima Pasechnik wrote: >> >> On Fri, Mar 8, 2019 at 12:40 PM kcrisman wrote: >> > >> > >> > >> > On Friday, March 8, 2019 at 3:24:45

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

On Friday, March 8, 2019 at 8:18:02 AM UTC-5, Dima Pasechnik wrote: > > 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 > >>

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

> 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 >

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

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

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

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

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

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