Bug#844789: [Debian-science-sagemath] gap: bad interaction between SAGE/atomic_write and GAP/SaveWorkspace [WAS: issue related to compressed manual.six]

2016-11-22 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, On 22/11/16 22:28, Bill Allombert wrote: > On Tue, Nov 22, 2016 at 05:52:11AM +, Jerome BENOIT wrote: >> I guess that the random bytes in /tmp/gapsage.log are not expected at >> all, and that they somehow feed some GAP variable. >> My

Bug#844789: [Debian-science-sagemath] gap: bad interaction between SAGE/atomic_write and GAP/SaveWorkspace [WAS: issue related to compressed manual.six]

2016-11-22 Thread Bill Allombert
On Tue, Nov 22, 2016 at 05:52:11AM +, Jerome BENOIT wrote: > I guess that the random bytes in /tmp/gapsage.log are not expected at > all, and that they somehow feed some GAP variable. > My current assumption is that the unpatched GAP (i.e., the upstream > version) is blind to those random

Bug#844789: [Debian-science-sagemath] gap: bad interaction between SAGE/atomic_write and GAP/SaveWorkspace [WAS: issue related to compressed manual.six]

2016-11-21 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I am getting a better picture of what is going on. On 20/11/16 00:54, Jerome BENOIT wrote: > > > On 19/11/16 18:37, Jerome BENOIT wrote: >> Hello, > >> On 19/11/16 17:43, Bill Allombert wrote: >>> On Sat, Nov 19, 2016 at 05:18:37AM