Re: [sage-release] Sage 7.0 released
On Fri, Jun 10, 2016 at 3:01 PM, kcrisman wrote: > (Harald, an app dmg 7.2 ready for mac/intel at > http://www.math-cs.gordon.edu/~kcrisman/sage-7.2-OSX_10.7.5-x86_64.app.dmg - > thanks!) ok, done -- h -- 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] Sage 7.0 released
> > Actually, I realized this morning that probably the issue is I already > build Sage once but there was the error. So it finds that and of course > there is no branch there. I guess I could have worked on that one but > mgoerner's solution seems reasonable, if I had known that there was still a > 'local' Sage repo inside binary-pkg. So I'll try again with this first. > Yes, apparently that fixed it. (Harald, an app dmg 7.2 ready for mac/intel at http://www.math-cs.gordon.edu/~kcrisman/sage-7.2-OSX_10.7.5-x86_64.app.dmg - thanks!) -- 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] Sage 7.0 released
On Wednesday, June 8, 2016 at 9:25:22 PM UTC-4, kcrisman wrote: > > > repository: file:///Users/karl.crisman/Downloads/sage >> branch: osx-10-7 >> >> > Got it - I've never seen that syntax before since I've never had to clone > something already local before :) thank you very much. Though > unfortunately it still gives the same error message :( > > http://trac.sagemath.org/ticket/20789 > > I think what is happening is that > > def git_clone(config): > if os.path.exists(os.path.join(config.source_path, '.git')): > subprocess.check_call([ > 'git', 'checkout', config.branch > ], cwd=config.source_path) > subprocess.check_call([ > 'git', 'pull', '--ff-only' > ], cwd=config.source_path) > else: > subprocess.check_call([ > 'git', 'clone', config.repository, '-b', config.branch, > config.source_path > ]) > > is noting that my local path to the git repo does exist, > Actually, I realized this morning that probably the issue is I already build Sage once but there was the error. So it finds that and of course there is no branch there. I guess I could have worked on that one but mgoerner's solution seems reasonable, if I had known that there was still a 'local' Sage repo inside binary-pkg. So I'll try again with this first. -- 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] Sage 7.0 released
> repository: file:///Users/karl.crisman/Downloads/sage > branch: osx-10-7 > > Got it - I've never seen that syntax before since I've never had to clone something already local before :) thank you very much. Though unfortunately it still gives the same error message :( http://trac.sagemath.org/ticket/20789 I think what is happening is that def git_clone(config): if os.path.exists(os.path.join(config.source_path, '.git')): subprocess.check_call([ 'git', 'checkout', config.branch ], cwd=config.source_path) subprocess.check_call([ 'git', 'pull', '--ff-only' ], cwd=config.source_path) else: subprocess.check_call([ 'git', 'clone', config.repository, '-b', config.branch, config.source_path ]) is noting that my local path to the git repo does exist, but then $ git checkout osx-10-7 error: pathspec 'osx-10-7' did not match any file(s) known to git. which makes sense because that branch is not in binary-pkg (I couldn't figure out exactly where source_path was set). But I'd rather patch binary-pkg than try to do it otherwise at this point. Almost there! -- 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] Sage 7.0 released
You should be able to use local repos but only using the normal git syntax, i.e. repository: file:///Users/karl.crisman/Downloads/sage branch: osx-10-7 On Wednesday, June 8, 2016 at 3:28:07 PM UTC-4, kcrisman wrote: > > > We improved the mac app bundling script recently, seems like it is not > compatible with OSX 10.7 > > Volker: mgoerner helped me some at #20119: > > "I think you can just remove $(TARGET)/.DS_store from the non_app_files: > target in src/mac-app/Makefile and then build it on 10.7 -without the nice > arrangement of the icons and background image :( > > I am not sure how you can tell binary_pkg to pick up that change. I would > commit that change to a local repository and point binary_pkg's sage_yaml > to that local repository." > > > I did all this, and even > > > name: SageMath > > repository: /Users/karl.crisman/Downloads/sage > branch: osx-10-7 > > > doesn't seem to work. Does the file assume an online repository? I don't > know how to make it look right but certainly > > > $ ls ../sage/.git > > has the usual stuff. Any help is greatly appreciated! > -- 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] Sage 7.0 released
> We improved the mac app bundling script recently, seems like it is not compatible with OSX 10.7 Volker: mgoerner helped me some at #20119: "I think you can just remove $(TARGET)/.DS_store from the non_app_files: target in src/mac-app/Makefile and then build it on 10.7 -without the nice arrangement of the icons and background image :( I am not sure how you can tell binary_pkg to pick up that change. I would commit that change to a local repository and point binary_pkg's sage_yaml to that local repository." I did all this, and even name: SageMath repository: /Users/karl.crisman/Downloads/sage branch: osx-10-7 doesn't seem to work. Does the file assume an online repository? I don't know how to make it look right but certainly $ ls ../sage/.git has the usual stuff. Any help is greatly appreciated! -- 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] Sage 7.0 released
> We improved the mac app bundling script recently, seems like it is not > compatible with OSX 10.7 > >> >> I saw some posts about 10.8 not working but that was post 7.2, it was 7.3 betas, so I didn't think there would be a problem. Was this related to this? https://github.com/sagemath/binary-pkg/commit/4d827f34da028563e69b066bda5ffba91c937eaa No: https://github.com/sagemath/sage/commit/7b66c50be6c44f97d9779b40aaca15cd2ee035e4 and specifically this line failed https://github.com/sagemath/sage/blob/master/src/mac-app/tools/createDSStore/ds_store/buddy.py#L76 So is there any alternative? In the past one could "just make the bundle" and then drop the binary in. -- 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] Sage 7.0 released
We improved the mac app bundling script recently, seems like it is not
compatible with OSX 10.7
On Wednesday, June 8, 2016 at 8:54:24 AM UTC-4, kcrisman wrote:
>
> While trying binary-pkg for Sage 7.2 on OS X 10.7 (due to be upgraded to
> new computer within a week, so wanted to provide last binaries from that),
> apparently the tar and non-app dmg were created, but the app failed with
> the following. Any ideas? (Later today or tomorrow I can provide these
> for upload to mirrors, but not if I don't have the app version. I'll note
> I rarely had trouble creating bdist with the sage-bdist script...)
>
> total size is 2610034433 speedup is 1.00
> test -d
> sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/Contents/Resources/sage &&
> touch sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/Contents/Resources/sage
> rm -f sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/sage
> ln -s Contents/Resources/sage/sage
> sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/sage
> cp
> /Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/bin/sage-README-osx.txt
>
> sage-7.2-OSX_10.7.5_x86_64/README.txt
> rm -f sage-7.2-OSX_10.7.5_x86_64/.DS_Store
> tools/createDSStore/createDSStore.py sage-7.2-OSX_10.7.5_x86_64
> sage-7.2-OSX_10.7.5_x86_64 SageMath-7.2.app
> Traceback (most recent call last):
> File "tools/createDSStore/createDSStore.py", line 146, in
> app_name = sys.argv[3])
> File "tools/createDSStore/createDSStore.py", line 123, in createDSStore
> with ds_store.DSStore.open(filePath, 'w+') as d:
> File
> "/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/store.py",
>
> line 269, in open
> store = buddy.Allocator.open (file_or_name, mode)
> File
> "/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
>
> line 221, in open
> return Allocator (f)
> File
> "/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
>
> line 136, in __init__
> count, self._unknown2 = self._root.read('>II')
> File
> "/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
>
> line 76, in read
> return struct.unpack (size_or_format, data)
> struct.error: unpack requires a string argument of length 8
> make[2]: *** [sage-7.2-OSX_10.7.5_x86_64/.DS_Store] Error 1
> cp: SageMath/src/mac-app/sage-7.2-*.app.dmg: No such file or directory
> ERROR:root:Script failed:
>
> ERROR:root:DMG=/Users/karl.crisman/Downloads/binary-pkg/dist/sage-7.2-OSX_10.7.5-x86_64.app.dmg
> rm -f $DMG
> pwd
> (cd SageMath/src/mac-app && make)
> cp SageMath/src/mac-app/sage-7.2-*.app.dmg $DMG
>
> Traceback (most recent call last):
> File
> "/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
>
> line 170, in _run_module_as_main
> "__main__", mod_spec)
> File
> "/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
>
> line 85, in _run_code
> exec(code, run_globals)
> File "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/cmdline.py",
> line 78, in
> launch()
> File "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/cmdline.py",
> line 74, in launch
> package.dist_script.run()
> File
> "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/bash_script.py", line
> 37, in run
> ['bash', self._filename], cwd=self._cwd, env=self.env())
> File
> "/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
>
> line 561, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['bash',
> '/Users/karl.crisman/Downloads/binary-pkg/tmp/SageMath/tmp976sv49f.sh']'
> returned non-zero exit status 1
> make[1]: *** [dist-sage] Error 1
> make: *** [bdist-sage-osx] Error 2
>
>
--
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] Sage 7.0 released
While trying binary-pkg for Sage 7.2 on OS X 10.7 (due to be upgraded to
new computer within a week, so wanted to provide last binaries from that),
apparently the tar and non-app dmg were created, but the app failed with
the following. Any ideas? (Later today or tomorrow I can provide these
for upload to mirrors, but not if I don't have the app version. I'll note
I rarely had trouble creating bdist with the sage-bdist script...)
total size is 2610034433 speedup is 1.00
test -d sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/Contents/Resources/sage
&& touch sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/Contents/Resources/sage
rm -f sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/sage
ln -s Contents/Resources/sage/sage
sage-7.2-OSX_10.7.5_x86_64/SageMath-7.2.app/sage
cp
/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/bin/sage-README-osx.txt
sage-7.2-OSX_10.7.5_x86_64/README.txt
rm -f sage-7.2-OSX_10.7.5_x86_64/.DS_Store
tools/createDSStore/createDSStore.py sage-7.2-OSX_10.7.5_x86_64
sage-7.2-OSX_10.7.5_x86_64 SageMath-7.2.app
Traceback (most recent call last):
File "tools/createDSStore/createDSStore.py", line 146, in
app_name = sys.argv[3])
File "tools/createDSStore/createDSStore.py", line 123, in createDSStore
with ds_store.DSStore.open(filePath, 'w+') as d:
File
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/store.py",
line 269, in open
store = buddy.Allocator.open (file_or_name, mode)
File
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
line 221, in open
return Allocator (f)
File
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
line 136, in __init__
count, self._unknown2 = self._root.read('>II')
File
"/Users/karl.crisman/Downloads/binary-pkg/staging/OSX_mac_app/SageMath/src/mac-app/tools/createDSStore/ds_store/buddy.py",
line 76, in read
return struct.unpack (size_or_format, data)
struct.error: unpack requires a string argument of length 8
make[2]: *** [sage-7.2-OSX_10.7.5_x86_64/.DS_Store] Error 1
cp: SageMath/src/mac-app/sage-7.2-*.app.dmg: No such file or directory
ERROR:root:Script failed:
ERROR:root:DMG=/Users/karl.crisman/Downloads/binary-pkg/dist/sage-7.2-OSX_10.7.5-x86_64.app.dmg
rm -f $DMG
pwd
(cd SageMath/src/mac-app && make)
cp SageMath/src/mac-app/sage-7.2-*.app.dmg $DMG
Traceback (most recent call last):
File
"/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
line 170, in _run_module_as_main
"__main__", mod_spec)
File
"/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/runpy.py",
line 85, in _run_code
exec(code, run_globals)
File "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/cmdline.py",
line 78, in
launch()
File "/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/cmdline.py",
line 74, in launch
package.dist_script.run()
File
"/Users/karl.crisman/Downloads/binary-pkg/binary_pkg/bash_script.py", line
37, in run
['bash', self._filename], cwd=self._cwd, env=self.env())
File
"/Users/karl.crisman/Downloads/binary-pkg/tools/binary-pkg/lib/python3.4/subprocess.py",
line 561, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['bash',
'/Users/karl.crisman/Downloads/binary-pkg/tmp/SageMath/tmp976sv49f.sh']'
returned non-zero exit status 1
make[1]: *** [dist-sage] Error 1
make: *** [bdist-sage-osx] Error 2
--
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] Sage 7.0 released
On 05/26/16 09:58, Justin C. Walker wrote: One more thing: On May 25, 2016, at 14:39 , Justin C. Walker wrote: On May 25, 2016, at 13:58 , François Bissey wrote: [snip] It is technically a race condition. Those are fiddly to predict. Yep. Six is a requirement for several packages, which explains the issue (when coupled with the race issue). My next questions are: 1. After reviewing the doc for packaging, it's not clear to me how to set up the correct package structure from the "plain vanilla" upstream package. Pointers? 2. Is this a better forum than trac for this discussion? I forgot two possibly important questions: 3. I checked (I think) all 'dependencies' files in $SAGE_ROOT/build/pkgs on a system with a good build of 7.2. The log file for each of these packages claims that "six 1.10.0 is already the active version in easy-install.pth" I'm not sure what that means, but the logs don't seem to show any further concern about finding/installing "six". 4. I see an "egg" directory for "six" in $SAGE_ROOT/local/local/lib/python2.7/site-packages/ On my 10.6.8 system, some of the packages with dependence on "six" have successfully built. The others did not build prior to the build halting. What's up with that? I'm clearly missing something... If you were building in parallel (and I suspect that was the case) the thread building pathlib2 could have failed before the one that lead to the building of six. You should check the time stamps in logs/pkgs/. Francois -- 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] Sage 7.0 released
One more thing: On May 25, 2016, at 14:39 , Justin C. Walker wrote: > > On May 25, 2016, at 13:58 , François Bissey wrote: [snip] >> It is technically a race condition. Those are fiddly to >> predict. > > Yep. > > Six is a requirement for several packages, which explains the issue (when > coupled with the race issue). > > My next questions are: > 1. After reviewing the doc for packaging, it's not clear to me how to set > up the correct package structure from the "plain vanilla" upstream package. > Pointers? > 2. Is this a better forum than trac for this discussion? I forgot two possibly important questions: 3. I checked (I think) all 'dependencies' files in $SAGE_ROOT/build/pkgs on a system with a good build of 7.2. The log file for each of these packages claims that "six 1.10.0 is already the active version in easy-install.pth" I'm not sure what that means, but the logs don't seem to show any further concern about finding/installing "six". 4. I see an "egg" directory for "six" in $SAGE_ROOT/local/local/lib/python2.7/site-packages/ On my 10.6.8 system, some of the packages with dependence on "six" have successfully built. The others did not build prior to the build halting. What's up with that? I'm clearly missing something... Thanks! Justin -- Justin C. Walker Curmudgeon at Large Director Institute for the Enhancement of the Director's Income -- Build a man a fire and he'll be warm for a night. Set a man on fire and he'll be warm for the rest of his life. -- 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] Sage 7.0 released
On May 25, 2016, at 13:58 , François Bissey wrote:
> On 05/26/16 04:16, Justin C. Walker wrote:
>>
>>> On May 25, 2016, at 00:43, Francois Bissey
>>> wrote:
>>>
>>> Looks like “six” needs to be a build dependency of pathlib2.
>>> Installed
>>> /Users/Sage/sage-7.2/local/lib/python2.7/site-packages/pathlib2-2.1.0-py2.7.egg
>>> Processing dependencies for pathlib2==2.1.0
>>> Searching for six
>>> Reading https://pypi.python.org/simple/six/
>>> Download error on https://pypi.python.org/simple/six/: timed out -- Some
>>> packages may not be found!
>>> Couldn't find index page for 'six' (maybe misspelled?)
>>> Scanning index of all packages (this may take a while)
>>> Reading https://pypi.python.org/simple/
>>> Download error on https://pypi.python.org/simple/: timed out -- Some
>>> packages may not be found!
>>> No local packages or download links found for six
>>> error: Could not find suitable distribution for Requirement.parse('six’)
>>
>> Mayhap’s this is clear to the Initiata, but how is it that this just showed
>> up in my case, on only one of three systems.
>>
>> Admittedly, the system in question is kind of long in the tooth, but even so…
>>
> It is technically a race condition. Those are fiddly to
> predict.
Yep.
Six is a requirement for several packages, which explains the issue (when
coupled with the race issue).
My next questions are:
1. After reviewing the doc for packaging, it's not clear to me how to set
up the correct package structure from the "plain vanilla" upstream package.
Pointers?
2. Is this a better forum than trac for this discussion?
Thanks, as always.
Justin (new to the packaging world)
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
---
While creating wives, God promised men
that good and obedient wives would be
found in all corners of the world.
Then He made the earth round.
--
--
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] Sage 7.0 released
On 05/26/16 04:16, Justin C. Walker wrote:
On May 25, 2016, at 00:43, Francois Bissey
wrote:
Looks like “six” needs to be a build dependency of pathlib2.
Installed
/Users/Sage/sage-7.2/local/lib/python2.7/site-packages/pathlib2-2.1.0-py2.7.egg
Processing dependencies for pathlib2==2.1.0
Searching for six
Reading https://pypi.python.org/simple/six/
Download error on https://pypi.python.org/simple/six/: timed out -- Some
packages may not be found!
Couldn't find index page for 'six' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: timed out -- Some packages
may not be found!
No local packages or download links found for six
error: Could not find suitable distribution for Requirement.parse('six’)
Mayhap’s this is clear to the Initiata, but how is it that this just showed up
in my case, on only one of three systems.
Admittedly, the system in question is kind of long in the tooth, but even so…
It is technically a race condition. Those are fiddly to
predict.
Francois
--
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] Sage 7.0 released
> On May 25, 2016, at 00:43, Francois Bissey
> wrote:
>
> Looks like “six” needs to be a build dependency of pathlib2.
> Installed
> /Users/Sage/sage-7.2/local/lib/python2.7/site-packages/pathlib2-2.1.0-py2.7.egg
> Processing dependencies for pathlib2==2.1.0
> Searching for six
> Reading https://pypi.python.org/simple/six/
> Download error on https://pypi.python.org/simple/six/: timed out -- Some
> packages may not be found!
> Couldn't find index page for 'six' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading https://pypi.python.org/simple/
> Download error on https://pypi.python.org/simple/: timed out -- Some packages
> may not be found!
> No local packages or download links found for six
> error: Could not find suitable distribution for Requirement.parse('six’)
Mayhap’s this is clear to the Initiata, but how is it that this just showed up
in my case, on only one of three systems.
Admittedly, the system in question is kind of long in the tooth, but even so…
Thanks for clarifying.
--
Justin C. Walker, Curmudgeon-at-Large
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email
--
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] Sage 7.0 released
Looks like “six” needs to be a build dependency of pathlib2.
Installed
/Users/Sage/sage-7.2/local/lib/python2.7/site-packages/pathlib2-2.1.0-py2.7.egg
Processing dependencies for pathlib2==2.1.0
Searching for six
Reading https://pypi.python.org/simple/six/
Download error on https://pypi.python.org/simple/six/: timed out -- Some
packages may not be found!
Couldn't find index page for 'six' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: timed out -- Some packages
may not be found!
No local packages or download links found for six
error: Could not find suitable distribution for Requirement.parse('six')
François
> On 25/05/2016, at 19:24, Justin C. Walker wrote:
>
>
> On May 15, 2016, at 14:52 , Volker Braun wrote:
>
> > Obviously its "Sage 7.2 released"... it was a long day ;-)
> >
> >
> >
> > On Sunday, May 15, 2016 at 11:28:15 PM UTC+2, Volker Braun wrote:
> >>
> >> The "master" git branch has been updated to Sage-7.0. As always, you can
> >> get the latest beta version from the "develop" git branch. Alternatively,
> >> the self-contained source tarball is at
> >> http://www.sagemath.org/download-latest.html
>
> I discovered that, on my 10.6.8 system, I left the "MacPorts" commands open
> for access (via path). Since I've had quickly-aborted builds of the last
> several releases, I thought to try again, after moving into a corner.
>
> I was able to get the build of 7.2 farther than before.
>
> This time most packages were built, but the build did blow up on the package
> "pathlib2-2.1.0". The log is attached.
>
> Anyone got a clue to spare? I won't have time to dig in for a couple of
> days...
>
> Thanks for any pointers/suggestions.
>
> Justin
>
> --
> 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.
>
>
> --
> Justin C. Walker, Curmudgeon-At-Large
> Director
> Institute for the Enhancement of the Director's Income
>
> "Weaseling out of things is what separates us from the animals.
> Well, except the weasel."
> - Homer J Simpson
>
>
>
> --
> 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.
[sage-release] Sage 7.0 released
The "master" git branch has been updated to Sage-7.0. As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html f76401f Updated SageMath version to 7.2 17c23eb Trac #20604: failing doctest with coxeter3 7e96c30 Updated SageMath version to 7.2.rc2 -- 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] Sage 7.0 released
Are you sure you are not running out of memory in the doc build? You need > 2gb / process. -- 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] Sage 7.0 released
> On Jan 19, 2016, at 06:21, Volker Braun wrote: > > The "master" git branch has been updated to Sage-7.0. As always, you can get > the latest beta version from the "develop" git branch. Alternatively, the > self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > As a final reminder, there are no incremental updates from 6.x to 7.0: You > have to recompile all of Sage (make distclean && make) Following SLelievre’s suggestion, I reran the build, from scratch, as “make ptestlong”, no parallelism. The build completed, as did the doc build. However, the testing never got started; the doc build seemed to hang at the end. I tried to repeat this with earlier betas, with the same result, except that for the betas, the “-j24” builds did complete w/o problems (as for the final, the doc builds hung at the end). More to come as I try to figure out what’s hanging. This is all on 10.6.8 (Dual 6-core Xeons). Builds on 10.10 and 10.11 work w/o problems with successful testing (‘ptestlong’). Justin -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income "Weaseling out of things is what separates us from the animals. Well, except the weasel." - Homer J Simpson -- 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] Sage 7.0 released
On Feb 4, 2016, at 06:38 , Samuel Lelievre wrote: > > > 2016-01-31 23:39:30 Z, Justin C. Walker: >> >> >> On Jan 31, 2016, at 15:23 , Volker Braun wrote: >> >>> Is that a parallel build? the mashed-together log isn't very meaningful. >> >> Yes it is (-j24; Dual 6-core Xeons). >> >> With any luck, you will find a tarball of the logs directory attached. >> > > I think Volker's question could be expanded into the > following recommendation. > > When a parallel build fails, it's good to > - save the log files > - run a non-parallel build. > > If the non-parallel build also fails, it will provide > easier-to-analyze logs. > > Otherwise, you can report that the failure was > observed with the parallel build but not with > the non-parallel build. Thanks for the suggestion. 'Twould appear that the non-parallel build is successful, at least so far. It's quietly chugging along passing the 18th spkg now. More to come. Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- While creating wives, God promised men that good and obedient wives would be found in all corners of the world. Then He made the earth round. -- -- 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] Sage 7.0 released
2016-01-31 23:39:30 Z, Justin C. Walker: > > > On Jan 31, 2016, at 15:23 , Volker Braun wrote: > > > Is that a parallel build? the mashed-together log isn't very meaningful. > > Yes it is (-j24; Dual 6-core Xeons). > > With any luck, you will find a tarball of the logs directory attached. > I think Volker's question could be expanded into the following recommendation. When a parallel build fails, it's good to - save the log files - run a non-parallel build. If the non-parallel build also fails, it will provide easier-to-analyze logs. Otherwise, you can report that the failure was observed with the parallel build but not with the non-parallel build. -- 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] Sage 7.0 released
On Jan 31, 2016, at 15:23 , Volker Braun wrote: > Is that a parallel build? the mashed-together log isn't very meaningful. Yes it is (-j24; Dual 6-core Xeons). With any luck, you will find a tarball of the logs directory attached. -- 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. s7.tbz2 Description: Binary data -- Justin C. Walker Director Institute for the Enhancement of the Director's Income -- Fame is fleeting, but obscurity just drags on and on. F&E -- 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] Sage 7.0 released
Is that a parallel build? the mashed-together log isn't very meaningful. On Monday, February 1, 2016 at 12:09:34 AM UTC+1, Justin C. Walker wrote: > > > On Jan 19, 2016, at 06:21 , Volker Braun wrote: > > > The "master" git branch has been updated to Sage-7.0. As always, you can > > get the latest beta version from the "develop" git branch. > Alternatively, > > the self-contained source tarball is at > > http://www.sagemath.org/download-latest.html > > Built (make ptestlong) on three OS X systems: > 10.6.8 (Dual 6-core Xeons): build problems - see below > 10.10.5 (Quad-core Core i7): no problems; all tests passed. > 10.11.3 (Quad-core Core i7): no problems; all tests passed. > > The build on 10.6.8 blew up in early going: > > sh: /Users/Sage/sage-7.0/build/bin/mv: No such file or directory > make[6]: *** [stripslash.o] Error 127 > make[6]: *** Waiting for unfinished jobs > make[5]: *** [all] Error 2 > make[4]: *** [all-recursive] Error 1 > make[3]: *** [all] Error 2 > Error building GNU patch > > real0m24.921s > user0m11.104s > sys 0m12.731s > > Error installing package patch-2.7.5 > > Please email sage-devel (http://groups.google.com/group/sage-devel) > explaining the problem and including the relevant part of the log file > /Users/Sage/sage-7.0/logs/pkgs/patch-2.7.5.log > > I can send the whole log, but it seems the relevant part is the above. > Not sure why 'mv' was expected in the Sage tree... > > Justin > > -- > Justin C. Walker, Curmudgeon-at-Large > () The ASCII Ribbon Campaign > /\ Help Cure HTML Email > > > > -- 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] Sage 7.0 released
On Jan 19, 2016, at 06:21 , Volker Braun wrote: > The "master" git branch has been updated to Sage-7.0. As always, you can > get the latest beta version from the "develop" git branch. Alternatively, > the self-contained source tarball is at > http://www.sagemath.org/download-latest.html Built (make ptestlong) on three OS X systems: 10.6.8 (Dual 6-core Xeons): build problems - see below 10.10.5 (Quad-core Core i7): no problems; all tests passed. 10.11.3 (Quad-core Core i7): no problems; all tests passed. The build on 10.6.8 blew up in early going: sh: /Users/Sage/sage-7.0/build/bin/mv: No such file or directory make[6]: *** [stripslash.o] Error 127 make[6]: *** Waiting for unfinished jobs make[5]: *** [all] Error 2 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 Error building GNU patch real0m24.921s user0m11.104s sys 0m12.731s Error installing package patch-2.7.5 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Users/Sage/sage-7.0/logs/pkgs/patch-2.7.5.log I can send the whole log, but it seems the relevant part is the above. Not sure why 'mv' was expected in the Sage tree... Justin -- Justin C. Walker, Curmudgeon-at-Large () The ASCII Ribbon Campaign /\ Help Cure HTML Email -- 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.
[sage-release] Sage 7.0 released
The "master" git branch has been updated to Sage-7.0. As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As a final reminder, there are no incremental updates from 6.x to 7.0: You have to recompile all of Sage (make distclean && make) 1961f94 Updated Sage version to 7.0 94dd2e2 Trac #19843: Improve location change error message 858e8d9 Trac #19879: Move sage/rings/arith to sage/arith c857bbc Trac #19415: Deprecate composite_field() adef4de Updated Sage version to 7.0.rc1 -- 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.
