Hello,
I frequently see "red links" on Trac git branches with the message
"trac's automerging failed". But when I try to merge with latest develop
using the git command line, the merge succeeds without conflicts. Why is
this? What does the Trac git plugin do to merge?
And a different problem
On May 27, 2015, at 17:26 , Jason Grout wrote:
> On 5/27/15 18:38, Justin C. Walker wrote:
>>
>> On May 27, 2015, at 13:15 , Jason Grout wrote:
[snip]
>> Are you building multi-threaded?
>>
>
> I'm just typing "make" in the sage directory (after doing make distclean and
> git clean -df). So
On May 27, 2015, at 20:19 , Hal Snyder wrote:
>
> On Wednesday, May 27, 2015 at 9:09:51 PM UTC-5, jason wrote:
>>
>> On 5/27/15 18:38, Justin C. Walker wrote:
>>>
>>> On May 27, 2015, at 13:15 , Jason Grout wrote:
>>>
I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3
On Wednesday, May 27, 2015 at 9:09:51 PM UTC-5, jason wrote:
>
> On 5/27/15 18:38, Justin C. Walker wrote:
> >
> > On May 27, 2015, at 13:15 , Jason Grout wrote:
> >
> >> I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3
> with XCode 6.3.1. Here's the end of the build log (
On 5/27/15 18:38, Justin C. Walker wrote:
On May 27, 2015, at 13:15 , Jason Grout wrote:
I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3 with XCode
6.3.1. Here's the end of the build log (I can post the entire install log, if
needed). Is Sage supposed to compile on OS X
On 5/27/15 18:38, Justin C. Walker wrote:
On May 27, 2015, at 13:15 , Jason Grout wrote:
I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3 with XCode
6.3.1. Here's the end of the build log (I can post the entire install log, if
needed). Is Sage supposed to compile on OS X
On 5/27/15 18:18, Volker Braun wrote:
Thats what the OSX buildbot is on, so it should work. Do you actually
have commandline tools 6.3.1? Whats the output of clang --version?
% xcodebuild -version
Xcode 6.3.1
Build version 6D1002
% clang --version
Apple LLVM version 6.1.0 (clang-602.0.49) (ba
On May 27, 2015, at 13:15 , Jason Grout wrote:
> I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3 with
> XCode 6.3.1. Here's the end of the build log (I can post the entire install
> log, if needed). Is Sage supposed to compile on OS X 10.10.3 with XCode
> 6.3.1? I saw so
Thats what the OSX buildbot is on, so it should work. Do you actually have
commandline tools 6.3.1? Whats the output of clang --version?
On Wednesday, May 27, 2015 at 10:16:16 PM UTC+2, jason wrote:
>
> I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3 with
> XCode 6.3.1. He
On 27/05/15 22:27, Johan S. R. Nielsen wrote:
The behavior is bad but I would not call it a bug. You modified wrongly
the vector.
I disagree: from a user-point of view, a superficially perfectly reasonable
sequence of steps were taken, at the end of which Sage prints a result
which is mathemati
Hi
I only need install file not deps.
Also, the new PPA will include only EN and FR docs. Please let me know if
PPA users are inconvenienced by this. Maybe we have the time to split the
packages but adding back a language is quick.
Regards,
Jan
On 27 May 2015 at 20:13, Jan Groenewald wrote:
On 27/05/15 22:02, Volker Braun wrote:
IMHO the bug here is a lack of validation. Its perfectly fine to have
mutable elements of a vector subspace, but y.__setitem__ should then check
that the vector really is in the subspace or raise a ValueError. Of course
it would almost always raise, so its n
> The behavior is bad but I would not call it a bug. You modified wrongly
> the vector.
I disagree: from a user-point of view, a superficially perfectly reasonable
sequence of steps were taken, at the end of which Sage prints a result
which is mathematically incorrect, without any error or war
On Wed, May 27, 2015 at 11:38 AM, Johan S. R. Nielsen
wrote:
> Hi Sage-devel
>
> We just crashed our heads against a bug in our code due to extremely weird
> semantics of Sage. Consider the following code which creates a sub-space C
> of the four-dimensional vector space over the binary field, and
I'm running into an error compiling gcc in Sage 6.7 on OS X 10.10.3 with
XCode 6.3.1. Here's the end of the build log (I can post the entire
install log, if needed). Is Sage supposed to compile on OS X 10.10.3
with XCode 6.3.1? I saw some messages and trac tickets about compiling
gcc in Sage
Guiding principles for SageMath, Inc.:
http://sagemath.blogspot.com/2015/05/guiding-principles-for-sagemath-inc.html
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop recei
IMHO the bug here is a lack of validation. Its perfectly fine to have
mutable elements of a vector subspace, but y.__setitem__ should then check
that the vector really is in the subspace or raise a ValueError. Of course
it would almost always raise, so its not a particularly useful operation.
Hi
Looks like I need build/install and build/deps (checking whether I need
only one of them).
Regards,
Jan
On 27 May 2015 at 18:54, Jan Groenewald wrote:
> Hi
>
> On 27 May 2015 at 18:17, Jan Groenewald wrote:
>
>> Hi
>>
>> Apparently I do need something else (than local and doc/src/output):
Hi
On 27 May 2015 at 18:17, Jan Groenewald wrote:
> Hi
>
> Apparently I do need something else (than local and doc/src/output):
>
I added bootstrap but this still occurs.
Regards,
Jan
>
> 0 root@muizenberg:~#dpkg -i sagemath-upstream-binary_6.7ppa2_amd64.deb
> (Reading database ... 586682 f
On 27/05/15 17:38, Johan S. R. Nielsen wrote:
Hi Sage-devel
We just crashed our heads against a bug in our code due to extremely weird
semantics of Sage. Consider the following code which creates a sub-space C
of the four-dimensional vector space over the binary field, and then
modifies a *copy*
Hi
Apparently I do need something else (than local and doc/src/output):
0 root@muizenberg:~#dpkg -i sagemath-upstream-binary_6.7ppa2_amd64.deb
(Reading database ... 586682 files and directories currently installed.)
Preparing to unpack sagemath-upstream-binary_6.7ppa2_amd64.deb ...
Unpacking sage
Hi Sage-devel
We just crashed our heads against a bug in our code due to extremely weird
semantics of Sage. Consider the following code which creates a sub-space C
of the four-dimensional vector space over the binary field, and then
modifies a *copy* of a vector from the subspace:
F = GF(2)
VS
Thanks, Nathann, that is very helpful.
John
On 27 May 2015 at 13:13, Nathann Cohen wrote:
> Hello,
>
>> I am planning to make a new-style version of the option spkg
>> database_kohel -- is there somewhere (other than trac of course) where
>> I can record this plan, and (afterwards) the fact that
Hello,
I am planning to make a new-style version of the option spkg
> database_kohel -- is there somewhere (other than trac of course) where
> I can record this plan, and (afterwards) the fact that it has been
> done? Somewhere where the current state of optional spkgs is
> recorded?
>
Righ
Apart from the language selection, it’s all manual copy at this stage
but if there is will to incorporate stuff “upstream” I am quite willing to
make it happen in a better way.
I just fell overbooked and run over from left (work) and right (kids being
sick in rotation) at the moment so it won’t
> Has this historical data now just disappeared?
It is there:
http://mirror.switch.ch/mirror/sagemath/src/changelog.txt
It seems that the 'mirror' files are not present on www.sagemath.org?
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
>
>
> http://www.sagemath.org/mirror/src/changelog.txt
>
> Has this historical data now just disappeared?
>
And it's not in the Wayback Machine because
http://www.sagemath.org/robots.txt
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubs
More troubling:
http://www.sagemath.org/mirror/src/changelog.txt
Has this historical data now just disappeared?
On Wed, May 27, 2015 at 8:01 AM, Karl-Dieter Crisman
wrote:
> On it!
>
> On Wed, May 27, 2015 at 5:22 AM, Jeroen Demeyer
> wrote:
>
>> Release notes for 6.6:
>> http://boxen.math.wa
On it!
On Wed, May 27, 2015 at 5:22 AM, Jeroen Demeyer
wrote:
> Release notes for 6.6:
> http://boxen.math.washington.edu/home/jdemeyer/sage-git/logs/sage-6.6.txt
>
> (if you find mistakes, change the Trac tickets)
>
--
You received this message because you are subscribed to the Google Groups
Apart from local and src/doc/output I don't need anything else?
Regards,
Jan
On 27 May 2015 at 13:13, Volker Braun wrote:
> Sounds good to me!
>
> On Wednesday, May 27, 2015 at 1:10:20 PM UTC+2, François wrote:
>
>>
>> > On 27/05/2015, at 22:58, Volker Braun wrote:
>> >
>> > On Wednesday, May
On 27 May 2015 at 11:39, Jeroen Demeyer wrote:
> On 2015-05-27 12:22, John Cremona wrote:
>>
>> I am planning to make a new-style version of the option spkg
>> database_kohel -- is there somewhere (other than trac of course) where
>> I can record this plan, and (afterwards) the fact that it has be
Sounds good to me!
On Wednesday, May 27, 2015 at 1:10:20 PM UTC+2, François wrote:
>
>
> > On 27/05/2015, at 22:58, Volker Braun >
> wrote:
> >
> > On Wednesday, May 27, 2015 at 11:42:59 AM UTC+2, Jan Groenewald wrote:
> > Apart from the "local" folder to I actually need anything else here to
> On 27/05/2015, at 22:58, Volker Braun wrote:
>
> On Wednesday, May 27, 2015 at 11:42:59 AM UTC+2, Jan Groenewald wrote:
> Apart from the "local" folder to I actually need anything else here to run
> sage?
>
> The documentation output is unfortunately still under /src/doc/output.
> Patches w
On Wednesday, May 27, 2015 at 11:42:59 AM UTC+2, Jan Groenewald wrote:
>
> Apart from the "local" folder to I actually need anything else here to run
> sage?
>
The documentation output is unfortunately still under /src/doc/output.
Patches would be welcome!
--
You received this message because
On 2015-05-27 12:22, John Cremona wrote:
I am planning to make a new-style version of the option spkg
database_kohel -- is there somewhere (other than trac of course) where
I can record this plan, and (afterwards) the fact that it has been
done? Somewhere where the current state of optional spkg
No, its no different from how other changes to the Sage source are
recorded: Just use git + trac.
On Wednesday, May 27, 2015 at 12:23:29 PM UTC+2, John Cremona wrote:
>
> I am planning to make a new-style version of the option spkg
> database_kohel -- is there somewhere (other than trac of cou
I am planning to make a new-style version of the option spkg
database_kohel -- is there somewhere (other than trac of course) where
I can record this plan, and (afterwards) the fact that it has been
done? Somewhere where the current state of optional spkgs is
recorded?
John
--
You received this
Hi
I have to make some decisions for the PPA as well. Here the install is 1)
root-owned 2) I just removed .git and .gitignore from the PPA for
dpkg-specific reasons (a quilt package fails to build and a native package
fails if .git is included). Doing git stuff as root in a /usr/ filesystem
over f
Release notes for 6.6:
http://boxen.math.washington.edu/home/jdemeyer/sage-git/logs/sage-6.6.txt
(if you find mistakes, change the Trac tickets)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving ema
There is the SAGE_PEXPECT_LOG environment variable, it would IMHO be
reasonable to also use it to switch logging on or off.
On Wednesday, May 27, 2015 at 10:06:23 AM UTC+2, John Cremona wrote:
>
> On 26 May 2015 at 23:21, Andrey Novoseltsev > wrote:
> > Hello,
> >
> > There are apparently l
On 5/22/15 01:02, William Stein wrote:
I think the license of SageCell has always been BSD.
Like William and Rob said, the license has always been open source, and
the sage cell server has always been developed in the open. The license
of the source files is BSD, with the caveat that (to my
On 26 May 2015 at 23:21, Andrey Novoseltsev wrote:
> Hello,
>
> There are apparently log files written to .sage. This causes issues with
> SageMathCell which makes .sage immutable and there are commands that trigger
> creation of some of these files, but it looks like the list is growing,
> curren
42 matches
Mail list logo
