Re: [sage-devel] Re: VotePlugin for trac?

[Jori Mäntysalo]

On Tue, 5 Jul 2016, leif wrote:


Yes. What is the point of voting for tickets?



Fun.


It would be nice to know what features of Sage are wanted or what bugs 
really annoy people. But would we really get that data from trac?


We don't have, say, function to compute crossing number (="how much 
non-planar measure") of a graph. How could we know if anyone wants that? 
Who would be interested in implementing it just because many people ask 
for it?


--
Jori Mäntysalo

[sage-devel] Re: branch is not clickable

[leif]

Paul Masson wrote:
> I just pushed to #9654 and the commit is not appearing. On a second push
> Git said everything is up to date, so I'm assuming the commit is there
> but not showing up in the web interface. What's up?

While it's tedious, you can always check
https://git.sagemath.org/sage.git/log/?h=u/paulmasson/9654 (provided you
know the branch).


-leif

> On Tuesday, July 5, 2016 at 1:15:55 PM UTC-7, Dima Pasechnik wrote:
> 
> I see errors like MethodNotFound: RPC method "search.branch" not found
> 
> in trac log. Erik was changing things today, perhaps this is the
> fallout of it.
> 
> 
> 
> On Tuesday, July 5, 2016 at 8:39:36 PM UTC+1, Frédéric Chapoton wrote:
> 
> It seems that something is broken in trac, as the branch name is
> not green or red, and not clickable
> 
> This is a very crucial tool for me, and for others too probably.
> 
> Frédéric


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

Re: [sage-devel] Method trait_names removed from units??

[Stan]

Dear Johan,

Thanks a lot, this is very helpful. And I agree that a deprecation warning 
would have been appropriate and also that keeping the trait_names() method 
active would help me at least. The problem with the _tab_completion() 
method is that it is not easily discoverable, as it does not show up when 
typing units.energy.. Ironic, isn't it?

Cheers
Stan

On Wednesday, July 6, 2016 at 1:50:08 AM UTC+2, Johan S. R. Nielsen wrote:
>
> Hi Stan, 
>
> It seems that trait_names() was originally added as part of a mechanism 
> for giving tab-completion to certain objects in IPython and the 
> Notebook, and this mechanism changed. Hence what used to be 
> trait_names() is now called _tab_completion() -- at least 
> units.energy._tab_completion() does exactly what 
> units.energy.trait_names() used to do, after #20410. You should be able 
> to change your existing code to use that instead. 
>
> But since trait_names() was a public API method, there should have 
> definitely been added a deprecation warning in #20410 instead of just 
> simply removing trait_names. Also, it seems the function is useful from 
> some user-perspectives, such as your own, so perhaps there should be a 
> publicly accessible version of _tab_completion() as well? 
>
> Best, 
> Johan 
>
>
> Stan writes: 
>
> > Dear all, 
> > 
> > After upgrading to 7.2, I found out that things such as 
> > units.energy.trait_names() do not work any more. I used this extensively 
> to 
> > loop through the different unit names and create variable names out of 
> > them. Why was this removed, and is there another way of doing this? I 
> want 
> > to be able to write e.g. 'joule' instead of 'units.energy.joule'. I 
> found a 
> > couple of tickets that may have led to the removal of trait_names for 
> units 
> > (see below), but I don't understand why, and how I can make my old 
> > worksheets compatible with sage 7.2! 
> > 
> > https://trac.sagemath.org/ticket/20410 
> > https://trac.sagemath.org/ticket/19951 
> > 
> > Thanks already for your help. 
> > 
> > Cheers 
> > Stan 
>
>
> -- 
>

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

Re: [sage-devel] Method trait_names removed from units??

[Johan S . H . Rosenkilde]

Hi Stan,

It seems that trait_names() was originally added as part of a mechanism
for giving tab-completion to certain objects in IPython and the
Notebook, and this mechanism changed. Hence what used to be
trait_names() is now called _tab_completion() -- at least
units.energy._tab_completion() does exactly what
units.energy.trait_names() used to do, after #20410. You should be able
to change your existing code to use that instead.

But since trait_names() was a public API method, there should have
definitely been added a deprecation warning in #20410 instead of just
simply removing trait_names. Also, it seems the function is useful from
some user-perspectives, such as your own, so perhaps there should be a
publicly accessible version of _tab_completion() as well?

Best,
Johan


Stan writes:

> Dear all,
>
> After upgrading to 7.2, I found out that things such as 
> units.energy.trait_names() do not work any more. I used this extensively to 
> loop through the different unit names and create variable names out of 
> them. Why was this removed, and is there another way of doing this? I want 
> to be able to write e.g. 'joule' instead of 'units.energy.joule'. I found a 
> couple of tickets that may have led to the removal of trait_names for units 
> (see below), but I don't understand why, and how I can make my old 
> worksheets compatible with sage 7.2!
>
> https://trac.sagemath.org/ticket/20410
> https://trac.sagemath.org/ticket/19951
>
> Thanks already for your help. 
>
> Cheers
> Stan


-- 

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

[sage-devel] Re: branch is not clickable

[Paul Masson]

I just pushed to #9654 and the commit is not appearing. On a second push 
Git said everything is up to date, so I'm assuming the commit is there but 
not showing up in the web interface. What's up?

On Tuesday, July 5, 2016 at 1:15:55 PM UTC-7, Dima Pasechnik wrote:
>
> I see errors like MethodNotFound: RPC method "search.branch" not found
>
> in trac log. Erik was changing things today, perhaps this is the fallout 
> of it.
>
>
>
> On Tuesday, July 5, 2016 at 8:39:36 PM UTC+1, Frédéric Chapoton wrote:
>>
>> It seems that something is broken in trac, as the branch name is not 
>> green or red, and not clickable
>>
>> This is a very crucial tool for me, and for others too probably.
>>
>> Frédéric
>>
>

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

[sage-devel] Method trait_names removed from units??

[Stan]

Dear all,

After upgrading to 7.2, I found out that things such as 
units.energy.trait_names() do not work any more. I used this extensively to 
loop through the different unit names and create variable names out of 
them. Why was this removed, and is there another way of doing this? I want 
to be able to write e.g. 'joule' instead of 'units.energy.joule'. I found a 
couple of tickets that may have led to the removal of trait_names for units 
(see below), but I don't understand why, and how I can make my old 
worksheets compatible with sage 7.2!

https://trac.sagemath.org/ticket/20410
https://trac.sagemath.org/ticket/19951

Thanks already for your help. 

Cheers
Stan

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

Re: [sage-devel] Problem installing sage 7.2 on SMC

[Rob H.]

One could begin by promoting 'make build'. Like, I was just following the 
instructions at the top 
of http://doc.sagemath.org/html/en/developer/manual_git.html. One could 
start by adding a comment there to the effect that 'make build' could be 
used instead of 'make'.

Rob

On Tuesday, July 5, 2016 at 3:57:25 PM UTC-6, William wrote:
>
> I begin to wish "make doc" we're a separate step
>
> On Tuesday, July 5, 2016, Rob H. > 
> wrote:
>
>> Thanks, William! It seemed like it was the documentation, but the fact 
>> that it crashed on 'make' scared me. Running sage seems to work, so I guess 
>> all is good.
>>
>> Best,
>>
>> Rob
>>
>> On Tuesday, July 5, 2016 at 3:41:03 PM UTC-6, William wrote:
>>>
>>> On Tue, Jul 5, 2016 at 2:25 PM, Rob H.  wrote: 
>>> > Hi, 
>>> > 
>>> > I was trying to set up a copy of Sage 7.2 on a SageMathCloud project 
>>> and the 
>>> > building process failed. This project was already housing an earlier 
>>> version 
>>> > of Sage (which I have since erased); it has the space for a copy of 
>>> Sage. I 
>>> > just cloned the sage.git repo, checked out the master branch, and 
>>> typed 
>>> > make. A few hours later, this happened: 
>>> > 
>>>
>>> It's only the documentation, not sage itself, that fails to build 
>>> (namely trying to build 3d images for the html reference manual). 
>>> I've reported this here last week and other people have the same 
>>> trouble: 
>>>
>>>
>>> https://groups.google.com/forum/#!searchin/sage-release/jmol$20%7Csort:date/sage-release/jQmE2nsnbDI/u32jH0vOAQAJ
>>>  
>>>
>>> Nobody uses the HTML documentation inside their build on SMC anyways... 
>>>
>>> William 
>>>
>>> -- 
>>> 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 receiving emails from it, send an 
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Sent from my massive iPhone 6 plus.
>

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

Re: [sage-devel] Problem installing sage 7.2 on SMC

[William Stein]

I begin to wish "make doc" we're a separate step

On Tuesday, July 5, 2016, Rob H.  wrote:

> Thanks, William! It seemed like it was the documentation, but the fact
> that it crashed on 'make' scared me. Running sage seems to work, so I guess
> all is good.
>
> Best,
>
> Rob
>
> On Tuesday, July 5, 2016 at 3:41:03 PM UTC-6, William wrote:
>>
>> On Tue, Jul 5, 2016 at 2:25 PM, Rob H.  wrote:
>> > Hi,
>> >
>> > I was trying to set up a copy of Sage 7.2 on a SageMathCloud project
>> and the
>> > building process failed. This project was already housing an earlier
>> version
>> > of Sage (which I have since erased); it has the space for a copy of
>> Sage. I
>> > just cloned the sage.git repo, checked out the master branch, and typed
>> > make. A few hours later, this happened:
>> >
>>
>> It's only the documentation, not sage itself, that fails to build
>> (namely trying to build 3d images for the html reference manual).
>> I've reported this here last week and other people have the same
>> trouble:
>>
>>
>> https://groups.google.com/forum/#!searchin/sage-release/jmol$20%7Csort:date/sage-release/jQmE2nsnbDI/u32jH0vOAQAJ
>>
>> Nobody uses the HTML documentation inside their build on SMC anyways...
>>
>> William
>>
>> --
>> 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 receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com
> 
> .
> To post to this group, send email to sage-devel@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my massive iPhone 6 plus.

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

Re: [sage-devel] Problem installing sage 7.2 on SMC

[Rob H.]

Thanks, William! It seemed like it was the documentation, but the fact that 
it crashed on 'make' scared me. Running sage seems to work, so I guess all 
is good.

Best,

Rob

On Tuesday, July 5, 2016 at 3:41:03 PM UTC-6, William wrote:
>
> On Tue, Jul 5, 2016 at 2:25 PM, Rob H. > 
> wrote: 
> > Hi, 
> > 
> > I was trying to set up a copy of Sage 7.2 on a SageMathCloud project and 
> the 
> > building process failed. This project was already housing an earlier 
> version 
> > of Sage (which I have since erased); it has the space for a copy of 
> Sage. I 
> > just cloned the sage.git repo, checked out the master branch, and typed 
> > make. A few hours later, this happened: 
> > 
>
> It's only the documentation, not sage itself, that fails to build 
> (namely trying to build 3d images for the html reference manual). 
> I've reported this here last week and other people have the same 
> trouble: 
>
>
> https://groups.google.com/forum/#!searchin/sage-release/jmol$20%7Csort:date/sage-release/jQmE2nsnbDI/u32jH0vOAQAJ
>  
>
> Nobody uses the HTML documentation inside their build on SMC anyways... 
>
> William 
>
> -- 
> 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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Problem installing sage 7.2 on SMC

[William Stein]

On Tue, Jul 5, 2016 at 2:25 PM, Rob H.  wrote:
> Hi,
>
> I was trying to set up a copy of Sage 7.2 on a SageMathCloud project and the
> building process failed. This project was already housing an earlier version
> of Sage (which I have since erased); it has the space for a copy of Sage. I
> just cloned the sage.git repo, checked out the master branch, and typed
> make. A few hours later, this happened:
>

It's only the documentation, not sage itself, that fails to build
(namely trying to build 3d images for the html reference manual).
I've reported this here last week and other people have the same
trouble:

   
https://groups.google.com/forum/#!searchin/sage-release/jmol$20%7Csort:date/sage-release/jQmE2nsnbDI/u32jH0vOAQAJ

Nobody uses the HTML documentation inside their build on SMC anyways...

William


> [plot3d   ] raise RuntimeError("Jmol failed to create file %s, see %s for
> details"%(repr(targetfile), repr(scratchout)))
> [plot3d   ] RuntimeError: Jmol failed to create file
> '/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/.sage/temp/compute5-us/16689/dir_xIpcHK/preview.
> png', see
> '/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/.sage/temp/compute5-us/16689/tmp_tKj6k6.txt'
> for details
> Error building the documentation.
> Traceback (most recent call last):
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python/runpy.py",
> line 162, in _run_module_as_main
> "__main__", fname, loader, pkg_name)
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python/runpy.py",
> line 72, in _run_code
> exec code in run_globals
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__main__.py",
> line 2, in 
> main()
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
> line 1629, in main
> builder()
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
> line 284, in _wrapper
> getattr(get_builder(document), 'inventory')(*args, **kwds)
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
> line 495, in _wrapper
> x.get(9)
>   File
> "/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python/multiprocessing/pool.py",
> line 567, in get
> raise self._value
> OSError: [plot3d   ]
> /projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage/plot/plot3d/platonic.py:docstring
> of
> sage.plot.plot3d.platonic:10: WARNING: Exception occurred in plotting
> platonic-1
>
> Makefile:1005: recipe for target 'doc-html' failed
> make[2]: *** [doc-html] Error 1
> make[2]: Leaving directory
> '/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/build/make'
> Makefile:828: recipe for target 'all' failed
> make[1]: *** [all] Error 2
> make[1]: Leaving directory
> '/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/build/make'
>
> real195m28.451s
> user169m51.508s
> sys 10m56.312s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
>
> * documentation: dochtml
>   log file:
> /projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/logs/pkgs/../dochtml.log
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> Makefile:16: recipe for target 'all' failed
> make: *** [all] Error 1
>
> Also, last night, I tried installing the development branch, but it failed
> too, albeit with a different error that I do not recall.
>
> Is there something I'm doing wrong? Is there a better forum in which to post
> this?
>
> Thanks,
>
> Rob
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Problem installing sage 7.2 on SMC

[Rob H.]

Hi,

I was trying to set up a copy of Sage 7.2 on a SageMathCloud project and 
the building process failed. This project was already housing an earlier 
version of Sage (which I have since erased); it has the space for a copy of 
Sage. I just cloned the sage.git repo, checked out the master branch, and 
typed make. A few hours later, this happened:

[plot3d   ] raise RuntimeError("Jmol failed to create file %s, see %s for 
details"%(repr(targetfile), repr(scratchout)))
[plot3d   ] RuntimeError: Jmol failed to create file 
'/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/.sage/temp/compute5-us/16689/dir_xIpcHK/preview.
png', see 
'/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/.sage/temp/compute5-us/16689/tmp_tKj6k6.txt'
 
for details
Error building the documentation.
Traceback (most recent call last):
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python/runpy.py",
 
line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python/runpy.py",
 
line 72, in _run_code
exec code in run_globals
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__main__.py",
 
line 2, in 
main()
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
 
line 1629, in main
builder()
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
 
line 284, in _wrapper
getattr(get_builder(document), 'inventory')(*args, **kwds)
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage_setup/docbuild/__init__.py",
 
line 495, in _wrapper
x.get(9)
  File 
"/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python/multiprocessing/pool.py",
 
line 567, in get
raise self._value
OSError: [plot3d   ] 
/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/local/lib/python2.7/site-packages/sage/plot/plot3d/platonic.py:docstring
 
of
sage.plot.plot3d.platonic:10: WARNING: Exception occurred in plotting 
platonic-1

Makefile:1005: recipe for target 'doc-html' failed
make[2]: *** [doc-html] Error 1
make[2]: Leaving directory 
'/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/build/make'
Makefile:828: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory 
'/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/build/make'
 
real195m28.451s
user169m51.508s
sys 10m56.312s
***
Error building Sage.
 
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
 
* documentation: dochtml
  log file: 
/projects/3e7bae8d-8ed0-45ff-83af-8517a03c8913/sage/logs/pkgs/../dochtml.log
 
The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
 
Makefile:16: recipe for target 'all' failed
make: *** [all] Error 1

Also, last night, I tried installing the development branch, but it failed 
too, albeit with a different error that I do not recall.

Is there something I'm doing wrong? Is there a better forum in which to 
post this?

Thanks,

Rob

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

Re: [sage-devel] Re: make giac/giacpy a standard package

[François Bissey]

On 06/07/16 04:16, leif wrote:

If so, should we change also the spkg name? (may be we should not, so
> people will really upgrade?)

That's not a problem, since Sage releases and specific spkg versions are
now stupidly tied together (even for optional spkgs).


Upgrade has to be handled carefully - the new spkg
has to remove the old install whatever its name is.

As for Leif's comment it has always been mostly the
case for sage the distribution.
I have a bit more freedom in sage-on-gentoo but not
all that much. If anything I am sometime pressured to
push upgrade in sage.

Francois

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

Re: [sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[William Stein]

On Tue, Jul 5, 2016 at 12:18 PM, leif  wrote:
> William Stein wrote:
>> On Tue, Jul 5, 2016 at 10:37 AM, leif  wrote:
>>> Erik Bray wrote:
 That could and probably should be fixed though.  In this case just
 changing decode('ascii') to decode('latin1') will go a long way (will
 result in mojibake for some code pages, but at least won't crash).
 Better still is to try utf-8 first and fall back on latin-1 if that
 fails.
>>>
>>> We do not even support spaces in the pathname (a common problem for
>>> MacOS X and Windoze users), since that already breaks a couple of
>>> upstream packages.
>>
>> We shouldn't actively discourage people from improving the quality of
>> Sage. Pointing out that Sage is broken in other ways is not a
>> compelling argument against fixing a build system bug.
>
> I'm absolutely not against fixing that /where we can/, I'm just saying
> we can hardly "fix" each and every package Sage includes, and we sadly
> have to live with that, at least for a while.  (Though as a disciple of
> Unix, I think putting spaces into filenames and especially folder names
> is a bad idea in the first place.  We should just give an /appropriate/
> error message, to the right time, i.e. asap.  In this case, Sage's
> top-level 'configure' should bail out until we support "non-ASCII"
> characters in the pathname of a Sage source tree.  Having a Sage
> installation reside in such a folder is by the way a related, but
> different problem, as long as you don't rebuild packages at least.)
>
> I was also especially referring to "[7-bit?] ASCII characters", where
> rather [a-zA-Z0-9_] was meant.  (Python btw. also implies restrictions
> on module-, package- and hence also filenames AFAIK.)

Thanks for clarifying --  I think we completely agree.And I
strongly agree with "We should just give an /appropriate/ error
message, to the right time, i.e. asap."

William

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



-- 
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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: branch is not clickable

[Dima Pasechnik]

I see errors like MethodNotFound: RPC method "search.branch" not found

in trac log. Erik was changing things today, perhaps this is the fallout of 
it.



On Tuesday, July 5, 2016 at 8:39:36 PM UTC+1, Frédéric Chapoton wrote:
>
> It seems that something is broken in trac, as the branch name is not green 
> or red, and not clickable
>
> This is a very crucial tool for me, and for others too probably.
>
> Frédéric
>

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

[sage-devel] branch is not clickable

[Frédéric Chapoton]

It seems that something is broken in trac, as the branch name is not green 
or red, and not clickable

This is a very crucial tool for me, and for others too probably.

Frédéric

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

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[leif]

William Stein wrote:
> On Tue, Jul 5, 2016 at 10:37 AM, leif  wrote:
>> Erik Bray wrote:
>>> That could and probably should be fixed though.  In this case just
>>> changing decode('ascii') to decode('latin1') will go a long way (will
>>> result in mojibake for some code pages, but at least won't crash).
>>> Better still is to try utf-8 first and fall back on latin-1 if that
>>> fails.
>>
>> We do not even support spaces in the pathname (a common problem for
>> MacOS X and Windoze users), since that already breaks a couple of
>> upstream packages.
> 
> We shouldn't actively discourage people from improving the quality of
> Sage. Pointing out that Sage is broken in other ways is not a
> compelling argument against fixing a build system bug.

I'm absolutely not against fixing that /where we can/, I'm just saying
we can hardly "fix" each and every package Sage includes, and we sadly
have to live with that, at least for a while.  (Though as a disciple of
Unix, I think putting spaces into filenames and especially folder names
is a bad idea in the first place.  We should just give an /appropriate/
error message, to the right time, i.e. asap.  In this case, Sage's
top-level 'configure' should bail out until we support "non-ASCII"
characters in the pathname of a Sage source tree.  Having a Sage
installation reside in such a folder is by the way a related, but
different problem, as long as you don't rebuild packages at least.)

I was also especially referring to "[7-bit?] ASCII characters", where
rather [a-zA-Z0-9_] was meant.  (Python btw. also implies restrictions
on module-, package- and hence also filenames AFAIK.)


-leif


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

Re: [sage-devel] make giac/giacpy a standard package

[Dima Pasechnik]

On Tuesday, July 5, 2016 at 7:33:50 PM UTC+1, tdumont wrote:
>
> Le 04/07/2016 23:10, Francois Bissey a écrit : 
> > I wouldn’t try to use one of these. Detecting blas/lapack automatically 
> is 
> > a fool’s errand. There are no standard naming scheme for the libraries 
> > and distress can mess things up on top of it. 
> > The only safe way is to get the stuff needed to link on the command 
> line. 
> > You may want to add detection of the fortran mangling, that suppose you 
> > will be making your code able to cope with that too. 
> > 
>
>
> Not sure... 
>
> I am a cmake user; I do not propose to include cmake in sage :-), but 
> cmake comes with a lot of scripts like FindBLAS.cmake and FindLAPACK.cmake 
>

cmake  is a Sage experimental package, in fact...
 

>
> I have used them on many linux distributions and it always worked. 
>
> So it is certainly possible to mimic what cmake is doing, say with a 
> python script. Maybe it already exists... 
>
> t.d. 
>
> > However I would like to know more about the particular lapack install 
> > you are trying to detect: 
> > 1) is it in /usr/lib(64) or /usr/local/lib? 
> > 2) is it all shared object or static [the way you look at gfortran, blas 
> and then 
> > lapack, suggests static] 
> > 
> > François 
> > 
>
>
>

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

[sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

I am opening  https://trac.sagemath.org/ticket/20946
to update the giac spkg

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

[sage-devel] Re: [sagemath-admins] Trac SSH keys

[David Roe]

On Jul 5, 2016 12:11, "Erik Bray"  wrote:
>
> Hi all,
>
> Several of you have had issues updating your SSH keys in Trac since
> the server upgrade (or adding new keys for new users).
>
> (I hope) the issue is resolved now, and I would like to give a brief
> post-mortem on the issue:
>
> - gitolite, the software that manages authorization for the git
> repository via SSH, was installed with a somewhat old version from
> Ubuntu's apt repository
>
> - gitolite throws a fit and fails to update its list of authorized
> keys if an invalid SSH key is added to its key repository
>
> - Andrew Ohana tells me at one point (we're not sure) he might have
> applied a patch to gitolite to make it more flexible with respect to
> invalid keys (throw a warning instead of die entirely); not clear if
> that patch would already exist in a newer version of gitolite or if
> this is still non-standard
>
> - additionally, there was a bug in Trac plugin for Sage that made it
> override any manual changes I made to the gitolite key repository
> (i.e. to remove invalid keys), so every time someone added a new key
> all the invalid keys I had deleted are restored as well
>
> - I fixed the above bug in the Trac plugin [1] and have also added a
> modicum of validation of SSH keys added through the web interface [2]
> so that this issue should not recur.
>
> Thanks for your patience,
> Erik
>
> P.S. In the process of working on this someone (Dima, I think)
> suggested adding an interface to add your SSH key from the command
> line via `git trac`.  I think it's a great idea, and something I'll
> consider in the future if there's more demand.  I also want to
> overhaul the web UI for managing SSH keys (make it more like GitHub)
> but I'll need a quiet rainy day for that.

That would be great: it's one of the features of the SageDev scripts that I
miss in git trac.

Thanks for the work on fixing the ssh-keys!
>
>
> [1]
https://github.com/sagemath/sage_trac_plugin/commit/abd272c292f985fb0adcdf537668642dd3a9b31a
> [2]
https://github.com/sagemath/sage_trac_plugin/commit/6b718e564c0c37430fd9d98aef7d29c4ea7191d8
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
"sagemath-admins" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to sagemath-admins+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: [sage-devel] make giac/giacpy a standard package

[Thierry Dumont]

Le 04/07/2016 23:10, Francois Bissey a écrit :
> I wouldn’t try to use one of these. Detecting blas/lapack automatically is
> a fool’s errand. There are no standard naming scheme for the libraries
> and distress can mess things up on top of it.
> The only safe way is to get the stuff needed to link on the command line.
> You may want to add detection of the fortran mangling, that suppose you
> will be making your code able to cope with that too.
>


Not sure...

I am a cmake user; I do not propose to include cmake in sage :-), but
cmake comes with a lot of scripts like FindBLAS.cmake and FindLAPACK.cmake

I have used them on many linux distributions and it always worked.

So it is certainly possible to mimic what cmake is doing, say with a
python script. Maybe it already exists...

t.d.

> However I would like to know more about the particular lapack install
> you are trying to detect:
> 1) is it in /usr/lib(64) or /usr/local/lib?
> 2) is it all shared object or static [the way you look at gfortran, blas and 
> then 
> lapack, suggests static]
> 
> François
> 


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

Re: [sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[William Stein]

On Tue, Jul 5, 2016 at 10:37 AM, leif  wrote:
> Erik Bray wrote:
>> That could and probably should be fixed though.  In this case just
>> changing decode('ascii') to decode('latin1') will go a long way (will
>> result in mojibake for some code pages, but at least won't crash).
>> Better still is to try utf-8 first and fall back on latin-1 if that
>> fails.
>
> We do not even support spaces in the pathname (a common problem for
> MacOS X and Windoze users), since that already breaks a couple of
> upstream packages.

We shouldn't actively discourage people from improving the quality of
Sage. Pointing out that Sage is broken in other ways is not a
compelling argument against fixing a build system bug.

 -- William


-- 
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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[leif]

Erik Bray wrote:
> That could and probably should be fixed though.  In this case just
> changing decode('ascii') to decode('latin1') will go a long way (will
> result in mojibake for some code pages, but at least won't crash).
> Better still is to try utf-8 first and fall back on latin-1 if that
> fails.

We do not even support spaces in the pathname (a common problem for
MacOS X and Windoze users), since that already breaks a couple of
upstream packages.


-leif

> On Tue, Jul 5, 2016 at 5:27 PM, Dima Pasechnik  wrote:
>> some parts of Sage do not work if Sage is installed in a directory with
>> non-ascii characters in its name. And you have that "Téléchargements" there.
>> Rename it to something ascii-only.


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

Re: [sage-devel] Re: VotePlugin for trac?

[William Stein]

On Tue, Jul 5, 2016 at 10:15 AM, leif  wrote:
> Dima Pasechnik wrote:
>> On Tuesday, July 5, 2016 at 3:32:09 PM UTC+1, vdelecroix wrote:
>>
>> On 05/07/16 10:25, Dima Pasechnik wrote:
>> > 1) well, there are always more tickets to work on than humanely
>> possible to
>> > handle quickly.
>> > It would be good to know which tickets are more urgent than others
>> from the
>> > community point of view.
>>
>> If only trac users are allowed to vote, I do not see the point of this
>> popularity contest. If everybody was allowed to vote, we would at least
>> have an idea of user needs.
>>
>>
>> the problem is that it is easy to abuse.
>> Somebody goes and votes on a ticket 100 times, just for "fun".
>>
>>
>> Moreover, I am not sure any developer would actually care about the
>> votes. How would you ensure that highly popular tickets are worked
>> on/reviewed in priority?
>>
>> Well, we certainly have an substantial anarchist element present here
>> :-), but given that
>> there are people paid to work on Sage...
>
> Yes, let's vote which work /they/ have to do! :P
>
>
>> > 2) WP7
>>
>> What does it mean?
>>
>>  https://github.com/OpenDreamKit/OpenDreamKit/issues/149
>
> Ah, Funding-SPAM!
>
>
> "We will survey the data needed to assess development models of
> large-scale academic open-source projects, such as the probable
> correlation between the size of the atomic contribution vs. the speed of
> the contribution making it into the code [ROFL!], and collect
> appropriate statistical data, to be published as a report (and possibly
> a conference publication) D7.1.
> The latter will require non-trivial amount of programming work, even
> only for ***the test system, SAGE***."

This is the first I've heard of this, and I have to say +1.   I'm for
using rigorous quantitative and testable approaches to trying to
improve the quality and efficiency of software development instead of
naive intuition and imagining that we are already optimal at what we
do.Thanks to whoever is doing this tedious project.

 -- William

>
> [...]
>
> "Open source projects tend to be fragile, in the community sense, and
> suffer from disagreements that ultimately result in “forks” and the
> resulting duplication of effort. We will analyse this phenomenon in the
> framework of algorithmic game theory, and try to design finely tuned
> systems of incentives and rewards for contribution so as to increase the
> stability of the community and its useful output.
>
> We will focus on three areas:
>  (1) prioritisation of bug fixes and feature requests to achieve
> reliable and useful systems;
>  (2) effective cooperation among multiple collaborative projects; and
>  (3) making decisions about the strategic direction of the system.
>
> We will use prioritisation as a testbed for designing incentives that
> encourage all participants to contribute towards sustained development
> of the most important parts of the system [Important to whom?]. To this
> end, we will use ideas from the burgeoning field of mechanism design
> [26] and in particular recent research on crowdsourcing in algorithmic
> mechanism design [34]. While doing so, ***we will apply outcomes to a
> case study system — SAGE***.
> The reason why prioritisation poses a challenge in the development of
> open-source academic software is that this process is task-driven:
> typically, tasks (also known as tickets) are posted on a website, and
> their priorities are set in an ad hoc manner. This model is usually good
> enough for simple bug fixing, but for more elaborate tasks it often
> leads to unacceptable delays. We will apply preference and opinion
> aggregation techniques [3] to develop a community prioritisation scheme
> for bugs and feature requests (which may rely on a reputation scores
> technique, such as one used on MathOverflow), and implement this scheme
> as a TRAC [39] add-on D7.2. As SAGE is using the TRAC server [2], this
> will be easy to test on our testbed system."
>
>
> So we all become experimentees...
>
>
> -leif
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[leif]

Dima Pasechnik:
> some parts of Sage do not work if Sage is installed in a directory with
> non-ascii characters in its name. And you have that "Téléchargements" there.
> Rename it to something ascii-only..

Đŏŵňłøåďş for example.


-leif


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

[sage-devel] Re: VotePlugin for trac?

[leif]

Dima Pasechnik wrote:
> On Tuesday, July 5, 2016 at 3:32:09 PM UTC+1, vdelecroix wrote:
> 
> On 05/07/16 10:25, Dima Pasechnik wrote:
> > 1) well, there are always more tickets to work on than humanely
> possible to
> > handle quickly.
> > It would be good to know which tickets are more urgent than others
> from the
> > community point of view.
> 
> If only trac users are allowed to vote, I do not see the point of this
> popularity contest. If everybody was allowed to vote, we would at least
> have an idea of user needs.
> 
> 
> the problem is that it is easy to abuse.
> Somebody goes and votes on a ticket 100 times, just for "fun". 
> 
> 
> Moreover, I am not sure any developer would actually care about the
> votes. How would you ensure that highly popular tickets are worked
> on/reviewed in priority?
> 
> Well, we certainly have an substantial anarchist element present here
> :-), but given that
> there are people paid to work on Sage...

Yes, let's vote which work /they/ have to do! :P


> > 2) WP7
> 
> What does it mean? 
> 
>  https://github.com/OpenDreamKit/OpenDreamKit/issues/149

Ah, Funding-SPAM!


"We will survey the data needed to assess development models of
large-scale academic open-source projects, such as the probable
correlation between the size of the atomic contribution vs. the speed of
the contribution making it into the code [ROFL!], and collect
appropriate statistical data, to be published as a report (and possibly
a conference publication) D7.1.
The latter will require non-trivial amount of programming work, even
only for ***the test system, SAGE***."

[...]

"Open source projects tend to be fragile, in the community sense, and
suffer from disagreements that ultimately result in “forks” and the
resulting duplication of effort. We will analyse this phenomenon in the
framework of algorithmic game theory, and try to design finely tuned
systems of incentives and rewards for contribution so as to increase the
stability of the community and its useful output.

We will focus on three areas:
 (1) prioritisation of bug fixes and feature requests to achieve
reliable and useful systems;
 (2) effective cooperation among multiple collaborative projects; and
 (3) making decisions about the strategic direction of the system.

We will use prioritisation as a testbed for designing incentives that
encourage all participants to contribute towards sustained development
of the most important parts of the system [Important to whom?]. To this
end, we will use ideas from the burgeoning field of mechanism design
[26] and in particular recent research on crowdsourcing in algorithmic
mechanism design [34]. While doing so, ***we will apply outcomes to a
case study system — SAGE***.
The reason why prioritisation poses a challenge in the development of
open-source academic software is that this process is task-driven:
typically, tasks (also known as tickets) are posted on a website, and
their priorities are set in an ad hoc manner. This model is usually good
enough for simple bug fixing, but for more elaborate tasks it often
leads to unacceptable delays. We will apply preference and opinion
aggregation techniques [3] to develop a community prioritisation scheme
for bugs and feature requests (which may rely on a reputation scores
technique, such as one used on MathOverflow), and implement this scheme
as a TRAC [39] add-on D7.2. As SAGE is using the TRAC server [2], this
will be easy to test on our testbed system."


So we all become experimentees...


-leif


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

Re: [sage-devel] Re: VotePlugin for trac?

[Vincent Delecroix]

On 05/07/16 12:51, leif wrote:

Vincent Delecroix wrote:

On 05/07/16 09:53, Dima Pasechnik wrote:

As an experiment, we would like to
install https://trac-hacks.org/wiki/VotePlugin
on trac.sagemath.org. This would allow voting on tickets (w.r.t. their
popularity, etc),
and probably more.

Voting would be restricted to people with a trac account.

Any substantial objections to this?


Yes. What is the point of voting for tickets?


Fun.


Except that:

- It would be one more thing to maintain
- It would introduce a bias in ticket order (maybe good, maybe bad)
- In the current proposal, it is not at all clear how these vote will be 
used


Anyway, if it is only for fun it is a -1 from me.

Vincent

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

[sage-devel] Re: VotePlugin for trac?

[leif]

Vincent Delecroix wrote:
> On 05/07/16 09:53, Dima Pasechnik wrote:
>> As an experiment, we would like to
>> install https://trac-hacks.org/wiki/VotePlugin
>> on trac.sagemath.org. This would allow voting on tickets (w.r.t. their
>> popularity, etc),
>> and probably more.
>>
>> Voting would be restricted to people with a trac account.
>>
>> Any substantial objections to this?
> 
> Yes. What is the point of voting for tickets?

Fun.


-leif


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

[sage-devel] Re: VotePlugin for trac?

[leif]

Dima Pasechnik wrote:
> As an experiment, we would like to
> install https://trac-hacks.org/wiki/VotePlugin 
> on trac.sagemath.org. This would allow voting on tickets (w.r.t. their
> popularity, etc),
> and probably more.
> 
> Voting would be restricted to people with a trac account.
> 
> Any substantial objections to this?

Provided we can vote on each comment, no.

But it seems we have no choice anyway... (read on)


-leif


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

Re: [sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[Erik Bray]

That could and probably should be fixed though.  In this case just
changing decode('ascii') to decode('latin1') will go a long way (will
result in mojibake for some code pages, but at least won't crash).
Better still is to try utf-8 first and fall back on latin-1 if that
fails.

On Tue, Jul 5, 2016 at 5:27 PM, Dima Pasechnik  wrote:
> some parts of Sage do not work if Sage is installed in a directory with
> non-ascii characters in its name. And you have that "Téléchargements" there.
> Rename it to something ascii-only.
>
>
> On Tuesday, July 5, 2016 at 3:57:50 PM UTC+1, Chakir Hilmi wrote:
>>
>> Hi all,
>>
>> I'm triying to install sage-7.2 on suse 13.2, but when i launch de make
>> command i have the following error telling me to contact you with joining
>> the error message file :
>>
>> Error message :
>>
>> Traceback (most recent call last):
>>   File "./spkg-install", line 596, in 
>> rc = build_tuning()
>>   File "./spkg-install", line 537, in build_tuning
>> rc = configure()
>>   File "./spkg-install", line 414, in configure
>> make_check_enums()
>>   File
>> "/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2/enums.py",
>> line 201, in make_check_enums
>> check_enums(output.decode('ascii'))
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 42:
>> ordinal not in range(128)
>>
>> real0m5.086s
>> user0m3.117s
>> sys 0m1.250s
>> 
>> Error installing package atlas-3.10.2.p2
>> 
>> Please email sage-devel (http://groups.google.com/group/sage-devel)
>> explaining the problem and including the relevant part of the log file
>>   /home/hilmi/Téléchargements/sage-7.2/logs/pkgs/atlas-3.10.2.p2.log
>> Describe your computer, operating system, etc.
>> If you want to try to fix the problem yourself, *don't* just cd to
>>
>> /home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2
>> and type 'make' or whatever is appropriate.
>> Instead, the following commands setup all environment variables
>> correctly and load a subshell for you to debug the error:
>>   (cd
>> '/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2'
>> && '/home/hilmi/Téléchargements/sage-7.2/sage' --sh)
>> When you are done debugging, you can type "exit" to leave the subshell.
>> 
>> Makefile:1074: recipe for target
>> '/home/hilmi/Téléchargements/sage-7.2/local/var/lib/sage/installed/atlas-3.10.2.p2'
>> failed
>> make[2]: ***
>> [/home/hilmi/Téléchargements/sage-7.2/local/var/lib/sage/installed/atlas-3.10.2.p2]
>> Error 1
>> make[2]: Leaving directory
>> '/home/hilmi/Téléchargements/sage-7.2/build/make'
>> Makefile:828: recipe for target 'all' failed
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory
>> '/home/hilmi/Téléchargements/sage-7.2/build/make'
>>
>> real0m8.856s
>> user0m6.227s
>> sys 0m1.880s
>> ***
>> Error building Sage.
>>
>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

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

[sage-devel] Re: make giac/giacpy a standard package

[leif]

Han Frederic wrote:
> Le mardi 5 juillet 2016 10:43:52 UTC+2, François a écrit :
> 
> 
> Han, I have looked at both giacpy and giacpy-sage now. They hardly
> have anything in common anymore.
> At least, it is not obvious from the repos.
> 
> Given that the split is already that wide, would there be an objection
> to them having different “name” in setup.py so they can be installed
> side by side?
> 
> François
> 
>  
>  Indeed  I think also that changing the name is slightly better than
> managing a non conflictual installation because one could install only
> the bad one.
> 
> May be giacpysage or giacpy_sage ?

sagiac, or sagiacpy.


> If so, should we change also the spkg name? (may be we should not, so
> people will really upgrade?)

That's not a problem, since Sage releases and specific spkg versions are
now stupidly tied together (even for optional spkgs).


-leif


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

[sage-devel] Trac SSH keys

[Erik Bray]

Hi all,

Several of you have had issues updating your SSH keys in Trac since
the server upgrade (or adding new keys for new users).

(I hope) the issue is resolved now, and I would like to give a brief
post-mortem on the issue:

- gitolite, the software that manages authorization for the git
repository via SSH, was installed with a somewhat old version from
Ubuntu's apt repository

- gitolite throws a fit and fails to update its list of authorized
keys if an invalid SSH key is added to its key repository

- Andrew Ohana tells me at one point (we're not sure) he might have
applied a patch to gitolite to make it more flexible with respect to
invalid keys (throw a warning instead of die entirely); not clear if
that patch would already exist in a newer version of gitolite or if
this is still non-standard

- additionally, there was a bug in Trac plugin for Sage that made it
override any manual changes I made to the gitolite key repository
(i.e. to remove invalid keys), so every time someone added a new key
all the invalid keys I had deleted are restored as well

- I fixed the above bug in the Trac plugin [1] and have also added a
modicum of validation of SSH keys added through the web interface [2]
so that this issue should not recur.

Thanks for your patience,
Erik

P.S. In the process of working on this someone (Dima, I think)
suggested adding an interface to add your SSH key from the command
line via `git trac`.  I think it's a great idea, and something I'll
consider in the future if there's more demand.  I also want to
overhaul the web UI for managing SSH keys (make it more like GitHub)
but I'll need a quiet rainy day for that.


[1] 
https://github.com/sagemath/sage_trac_plugin/commit/abd272c292f985fb0adcdf537668642dd3a9b31a
[2] 
https://github.com/sagemath/sage_trac_plugin/commit/6b718e564c0c37430fd9d98aef7d29c4ea7191d8

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

[sage-devel] Re: probleme installing sage-7.2 on suse 13.2

[Dima Pasechnik]

some parts of Sage do not work if Sage is installed in a directory with 
non-ascii characters in its name. And you have that "Téléchargements" there.
Rename it to something ascii-only.

On Tuesday, July 5, 2016 at 3:57:50 PM UTC+1, Chakir Hilmi wrote:
>
> Hi all,
>
> I'm triying to install sage-7.2 on suse 13.2, but when i launch de make 
> command i have the following error telling me to contact you with joining 
> the error message file :
>
> Error message : 
>
> Traceback (most recent call last):
>   File "./spkg-install", line 596, in 
> rc = build_tuning()
>   File "./spkg-install", line 537, in build_tuning
> rc = configure()
>   File "./spkg-install", line 414, in configure
> make_check_enums()
>   File 
> "/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2/enums.py",
>  
> line 201, in make_check_enums
> check_enums(output.decode('ascii'))
> *UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 42: 
> ordinal not in range(128)*
>
> real0m5.086s
> user0m3.117s
> sys 0m1.250s
> 
> Error installing package atlas-3.10.2.p2
> 
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the relevant part of the log file
>   */home/hilmi/Téléchargements/sage-7.2/logs/pkgs/atlas-3.10.2.p2.log*
> Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> /home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2 
> and type 'make' or whatever is appropriate.
> Instead, the following commands setup all environment variables
> correctly and load a subshell for you to debug the error:
>   (cd 
> '/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2'
>  
> && '/home/hilmi/Téléchargements/sage-7.2/sage' --sh)
> When you are done debugging, you can type "exit" to leave the subshell.
> 
> Makefile:1074: recipe for target 
> '/home/hilmi/Téléchargements/sage-7.2/local/var/lib/sage/installed/atlas-3.10.2.p2'
>  
> failed
> make[2]: *** 
> [/home/hilmi/Téléchargements/sage-7.2/local/var/lib/sage/installed/atlas-3.10.2.p2]
>  
> Error 1
> make[2]: Leaving directory 
> '/home/hilmi/Téléchargements/sage-7.2/build/make'
> Makefile:828: recipe for target 'all' failed
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> '/home/hilmi/Téléchargements/sage-7.2/build/make'
>
> real0m8.856s
> user0m6.227s
> sys 0m1.880s
> ***
> Error building Sage.
>
>
>
>
>

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

Re: [sage-devel] VotePlugin for trac?

[Dima Pasechnik]

On Tuesday, July 5, 2016 at 3:32:09 PM UTC+1, vdelecroix wrote:
>
> On 05/07/16 10:25, Dima Pasechnik wrote: 
> > 
> > 
> > On Tuesday, July 5, 2016 at 3:00:57 PM UTC+1, vdelecroix wrote: 
> >> 
> >> On 05/07/16 09:53, Dima Pasechnik wrote: 
> >>> As an experiment, we would like to 
> >>> install https://trac-hacks.org/wiki/VotePlugin 
> >>> on trac.sagemath.org. This would allow voting on tickets (w.r.t. 
> their 
> >>> popularity, etc), 
> >>> and probably more. 
> >>> 
> >>> Voting would be restricted to people with a trac account. 
> >>> 
> >>> Any substantial objections to this? 
> >> 
> >> Yes. What is the point of voting for tickets? 
> >> 
> > 
> > 1) well, there are always more tickets to work on than humanely possible 
> to 
> > handle quickly. 
> > It would be good to know which tickets are more urgent than others from 
> the 
> > community point of view. 
>
> If only trac users are allowed to vote, I do not see the point of this 
> popularity contest. If everybody was allowed to vote, we would at least 
> have an idea of user needs. 
>

the problem is that it is easy to abuse.
Somebody goes and votes on a ticket 100 times, just for "fun". 

>
> Moreover, I am not sure any developer would actually care about the 
> votes. How would you ensure that highly popular tickets are worked 
> on/reviewed in priority? 
>
Well, we certainly have an substantial anarchist element present here :-), 
but given that
there are people paid to work on Sage...


> > 2) WP7 
>
> What does it mean? 

 https://github.com/OpenDreamKit/OpenDreamKit/issues/149
 

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

Re: [sage-devel] probleme installing sage-7.2 on suse 13.2

[Vincent Delecroix]

Hello,

Please ask for help on the sage-support mailing list or the ask forum 
(http://ask.sagemath.org).


The problem comes from your repository "Téléchargements" which contains 
accents. Just move the sage directory somewhere else and relaunch make. 
from there.


Vincent

On 05/07/16 10:44, Chakir Hilmi wrote:

Hi all,

I'm triying to install sage-7.2 on suse 13.2, but when i launch de make
command i have the following error telling me to contact you with joining
the error message file :

Error message :

Traceback (most recent call last):
  File "./spkg-install", line 596, in 
rc = build_tuning()
  File "./spkg-install", line 537, in build_tuning
rc = configure()
  File "./spkg-install", line 414, in configure
make_check_enums()
  File
"/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2/enums.py",
line 201, in make_check_enums
check_enums(output.decode('ascii'))
*UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 42:
ordinal not in range(128)*

real0m5.086s
user0m3.117s
sys 0m1.250s

Error installing package atlas-3.10.2.p2

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
  */home/hilmi/Téléchargements/sage-7.2/logs/pkgs/atlas-3.10.2.p2.log*
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2
and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd
'/home/hilmi/Téléchargements/sage-7.2/local/var/tmp/sage/build/atlas-3.10.2.p2'
&& '/home/hilmi/Téléchargements/sage-7.2/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.

Makefile:1074: recipe for target
'/home/hilmi/Téléchargements/sage-7.2/local/var/lib/sage/installed/atlas-3.10.2.p2'
failed
make[2]: ***
[/home/hilmi/Téléchargements/sage-7.2/local/var/lib/sage/installed/atlas-3.10.2.p2]
Error 1
make[2]: Leaving directory '/home/hilmi/Téléchargements/sage-7.2/build/make'
Makefile:828: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/hilmi/Téléchargements/sage-7.2/build/make'

real0m8.856s
user0m6.227s
sys 0m1.880s
***
Error building Sage.






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

Re: [sage-devel] VotePlugin for trac?

[Vincent Delecroix]

On 05/07/16 10:25, Dima Pasechnik wrote:



On Tuesday, July 5, 2016 at 3:00:57 PM UTC+1, vdelecroix wrote:


On 05/07/16 09:53, Dima Pasechnik wrote:

As an experiment, we would like to
install https://trac-hacks.org/wiki/VotePlugin
on trac.sagemath.org. This would allow voting on tickets (w.r.t. their
popularity, etc),
and probably more.

Voting would be restricted to people with a trac account.

Any substantial objections to this?


Yes. What is the point of voting for tickets?



1) well, there are always more tickets to work on than humanely possible to
handle quickly.
It would be good to know which tickets are more urgent than others from the
community point of view.


If only trac users are allowed to vote, I do not see the point of this 
popularity contest. If everybody was allowed to vote, we would at least 
have an idea of user needs.


Moreover, I am not sure any developer would actually care about the 
votes. How would you ensure that highly popular tickets are worked 
on/reviewed in priority?



2) WP7


What does it mean?

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

Re: [sage-devel] VotePlugin for trac?

[Dima Pasechnik]

On Tuesday, July 5, 2016 at 3:00:57 PM UTC+1, vdelecroix wrote:
>
> On 05/07/16 09:53, Dima Pasechnik wrote: 
> > As an experiment, we would like to 
> > install https://trac-hacks.org/wiki/VotePlugin 
> > on trac.sagemath.org. This would allow voting on tickets (w.r.t. their 
> > popularity, etc), 
> > and probably more. 
> > 
> > Voting would be restricted to people with a trac account. 
> > 
> > Any substantial objections to this? 
>
> Yes. What is the point of voting for tickets? 
>

1) well, there are always more tickets to work on than humanely possible to 
handle quickly.
It would be good to know which tickets are more urgent than others from the 
community point of view.

2) WP7

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

Re: [sage-devel] VotePlugin for trac?

[Vincent Delecroix]

On 05/07/16 09:53, Dima Pasechnik wrote:

As an experiment, we would like to
install https://trac-hacks.org/wiki/VotePlugin
on trac.sagemath.org. This would allow voting on tickets (w.r.t. their
popularity, etc),
and probably more.

Voting would be restricted to people with a trac account.

Any substantial objections to this?


Yes. What is the point of voting for tickets?

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

[sage-devel] VotePlugin for trac?

[Dima Pasechnik]

As an experiment, we would like to 
install https://trac-hacks.org/wiki/VotePlugin 
on trac.sagemath.org. This would allow voting on tickets (w.r.t. their 
popularity, etc),
and probably more.

Voting would be restricted to people with a trac account.

Any substantial objections to this?
Thanks,
Dima
 

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

Re: [sage-devel] make giac/giacpy a standard package

[parisse]

1.2.2-67 is ready.

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

Re: [sage-devel] make giac/giacpy a standard package

[Han Frederic]

Le mardi 5 juillet 2016 10:43:52 UTC+2, François a écrit :
>
>
> Han, I have looked at both giacpy and giacpy-sage now. They hardly 
> have anything in common anymore. 
> At least, it is not obvious from the repos. 
>
> Given that the split is already that wide, would there be an objection 
> to them having different “name” in setup.py so they can be installed 
> side by side? 
>
> François

 
 Indeed  I think also that changing the name is slightly better than 
managing a non conflictual installation because one could install only the 
bad one.

May be giacpysage or giacpy_sage ? 
If so, should we change also the spkg name? (may be we should not, so 
people will really upgrade?)

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

[sage-devel] Could not import nbconvert // Sage 7.2 in virtual machine (CentOs 6.7) OVA file from May, 12th 2016

['Michael Olbrich' via sage-devel]

Hello,

I could only dowload my notebook as ipynb and not as HTML, py, PDFLatex, 
etc. 

The error messages is 

Could not import nbconvert: No module named entrypoints

I installed with yum pip and with pip entrypoints. 

The OVA runs on a Windows 7 64BIt 

Hopefully you could help me

Regards,

Michael

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

Re: [sage-devel] Re: ssh fail

[Parthasarathi Panda]

Hi Erik, 
I am still having the same error everytime i use git trac.

On Tuesday, July 5, 2016 at 4:03:10 PM UTC+5:30, Erik Bray wrote:
>
> On Tue, Jul 5, 2016 at 10:50 AM, Julien Lavauzelle 
> > wrote: 
> > Hi, 
> > 
> > I made the git-trac update and I got the same 'Permission denied' 
> problem 
> > with my new keys (new laptop also), when trying to push or to use 'ssh 
> -T 
> > g...@trac.sagemath.org '. But I didn't understand how tara 
> or eviatar fixed 
> > it. Could someone tell me ? 
>
> I have fixed it. 
>
> The invalid keys that I previously deleted from the key repository 
> mysteriously came back. 
>
> Turns out there was a bug in the sage trac plugin that would cause it 
> to overwrite any changes manually made to the key repository every 
> time someone added new keys through Trac.  That has been fixed. 
>

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

Re: [sage-devel] Re: ssh fail

[Erik Bray]

On Tue, Jul 5, 2016 at 10:50 AM, Julien Lavauzelle
 wrote:
> Hi,
>
> I made the git-trac update and I got the same 'Permission denied' problem
> with my new keys (new laptop also), when trying to push or to use 'ssh -T
> g...@trac.sagemath.org'. But I didn't understand how tara or eviatar fixed
> it. Could someone tell me ?

I have fixed it.

The invalid keys that I previously deleted from the key repository
mysteriously came back.

Turns out there was a bug in the sage trac plugin that would cause it
to overwrite any changes manually made to the key repository every
time someone added new keys through Trac.  That has been fixed.

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

Re: [sage-devel] Re: ssh fail

[Eviatar Bach]

Mine suddenly started working overnight. I know this was the case for at
least one other person. I assume something was done on the server.

Eviatar
On Jul 5, 2016 2:12 AM, "Julien Lavauzelle" 
wrote:

> Hi,
>
> I made the git-trac update and I got the same 'Permission denied' problem
> with my new keys (new laptop also), when trying to push or to use 'ssh -T
> g...@trac.sagemath.org'. But I didn't understand how tara or eviatar fixed
> it. Could someone tell me ?
>
> Best,
>
> Julien (login jlavauzelle)
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/BRv0wzw5kJ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-devel] Re: ssh fail

[Julien Lavauzelle]

Hi,

I made the git-trac update and I got the same 'Permission denied' problem 
with my new keys (new laptop also), when trying to push or to use 'ssh -T 
g...@trac.sagemath.org'. But I didn't understand how tara or eviatar fixed 
it. Could someone tell me ?

Best,

Julien (login jlavauzelle)

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

Re: [sage-devel] make giac/giacpy a standard package

[Francois Bissey]

> On 4/07/2016, at 22:17, Han Frederic  wrote:
> 
> I haven't gone through giacpy yet, but I don't like the fact there 
> is a sage specific version. Something could be done to only have one 
> source if my understanding of the issues and solution are correct. 
> 
> This need works and it could ends with another split (Ex the non sage version 
> have an experimental Qt output)
> giacpy status is different from giac: Giac has regular users through xcas 
> while giacpy is unknown, so the answer to Ralf's question could be different. 
> Any help to merge the 2 versions would be welcome but I would like to still 
> be able to cross build some giacpy for windows from linux.
>  

Han, I have looked at both giacpy and giacpy-sage now. They hardly 
have anything in common anymore.
At least, it is not obvious from the repos. 

Given that the split is already that wide, would there be an objection
to them having different “name” in setup.py so they can be installed
side by side?

François

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

Re: [sage-devel] Re: make giac/giacpy a standard package

[Ralf Stephan]

Bernard sent me earlier:
https://dev.geogebra.org/trac/browser/trunk/geogebra/giac/src/giac

On Tue, Jul 5, 2016 at 9:31 AM Dima Pasechnik  wrote:

>
>
> On Tuesday, July 5, 2016 at 7:48:51 AM UTC+1, François wrote:
>
>>
>> > On 5/07/2016, at 17:13, parisse  wrote:
>> >
>> > disable-gui should be working. If not, then I probably made a mistake
>> while copying the archive, you can try
>> http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz
>> 
>>
>> Yes that tarball has the goods. I’ll wait for a new 1.2.2-xx tarball
>> though. No self respecting
>> packager wants to deal with an upstream tarball which changes all the
>> times.
>
>
> We had this argument already. If you prefer to keep it this way, please
> provide us a  VCS (git preferred) repo
> off which we can label releases by the latest commit in the master branch,
> or something like this.
> This way at least meaningful bug reports can be filed. Please...
> We (or in fact any Linux/OSX distribution system) cannot work with
> different tarballs that are named the same, we do not have tools to support
> this. Each tarball change without name change triggers an alert screaming
> that it has been tampered with.
>
>
>
>
>
>
>
>
>
>> > I don't know what you mean by ETA, but disable-ao should also be
>> working.
>>
>> Dima answered that beautifully.
>>
>> > For lapack, it was a little nightmare before I got it working for the
>> various binaries of Xcas I provide on my site. I don't want to spend time
>> on this again since it works for me, and if it does not work for you, you
>> can patch configure.in or disable-lapack.
>> >
>>
>> You have my sympathy. That it works across the various binaries
>> you distribute is a small miracle in and of itself.
>> Auto detection of lapack without help of something like a .pc file
>> is a nut job. It only works for you because someone decided to
>> normalise the naming on the platforms you support.
>>
>> François
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/HI0uZra5_iI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [sage-devel] Re: make giac/giacpy a standard package

[Dima Pasechnik]

On Tuesday, July 5, 2016 at 7:48:51 AM UTC+1, François wrote:
>
>
> > On 5/07/2016, at 17:13, parisse  > wrote: 
> > 
> > disable-gui should be working. If not, then I probably made a mistake 
> while copying the archive, you can try 
> http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz 
> 
>  
>
> Yes that tarball has the goods. I’ll wait for a new 1.2.2-xx tarball 
> though. No self respecting 
> packager wants to deal with an upstream tarball which changes all the 
> times. 

 
We had this argument already. If you prefer to keep it this way, please 
provide us a  VCS (git preferred) repo
off which we can label releases by the latest commit in the master branch, 
or something like this.
This way at least meaningful bug reports can be filed. Please...
We (or in fact any Linux/OSX distribution system) cannot work with 
different tarballs that are named the same, we do not have tools to support 
this. Each tarball change without name change triggers an alert screaming 
that it has been tampered with.






  


> > I don't know what you mean by ETA, but disable-ao should also be 
> working. 
>
> Dima answered that beautifully. 
>
> > For lapack, it was a little nightmare before I got it working for the 
> various binaries of Xcas I provide on my site. I don't want to spend time 
> on this again since it works for me, and if it does not work for you, you 
> can patch configure.in or disable-lapack. 
> > 
>
> You have my sympathy. That it works across the various binaries 
> you distribute is a small miracle in and of itself. 
> Auto detection of lapack without help of something like a .pc file 
> is a nut job. It only works for you because someone decided to 
> normalise the naming on the platforms you support. 
>
> François

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