Re: [sage-devel] Re: BUGS in tensor products of algebras

2018-03-06 Thread Travis Scrimshaw
> > I've created #24914. > IMO, would be better to have individual tickets for each file/issue as they are independent. If you decide to do that, you can either keep #24914 as a meta-ticket or recycle it as one of the tickets for one of the specific issues. > I will get around to it by

Re: [sage-devel] Re: Git push issues

2018-03-06 Thread Luca De Feo
> No problem. And this was a mistake *I* made. This is a side-effect I > did not consider and might want to think more about how to prevent... GitHub forbids using an ssh key twice. It seems the only reasonable thing to do. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Re: Git push issues

2018-03-06 Thread Erik Bray
On Tue, Mar 6, 2018 at 7:29 PM, Meghana.M Reddy wrote: > This was the mistake I made. It worked now. Thanks a lot for helping me out. No problem. And this was a mistake *I* made. This is a side-effect I did not consider and might want to think more about how to

Re: [sage-devel] Re: Git push issues

2018-03-06 Thread Meghana.M Reddy
Dear Erik, I'm able to push my branch now. Thank you for your quick reply and helping me with the SSH key. Regards, Meghana On Tuesday, March 6, 2018 at 9:35:01 PM UTC+5:30, Erik Bray wrote: > > Hi Meghana, > > I've manually deleted your duplicate SSH key, so you should be able to > push

[sage-devel] Re: Git push issues

2018-03-06 Thread Meghana.M Reddy
This was the mistake I made. It worked now. Thanks a lot for helping me out. On Tuesday, March 6, 2018 at 9:01:56 PM UTC+5:30, Eric Gourgoulhon wrote: > > Hi, > > Le mardi 6 mars 2018 13:17:56 UTC+1, Meghana.M Reddy a écrit : >> >> ! [remote rejected] HEAD -> t/24909/boruvka_algorithm_for_mst

Re: [sage-devel] Re: lib*.so conflict

2018-03-06 Thread Erik Bray
On Tue, Mar 6, 2018 at 5:20 PM, Ralf Stephan wrote: > Very good. Doesn't it only work if the user not only has the library but > also the respective headers, i.e., the corresponding xyz-devel package > installed? Depends on the package, but if one package is a build dependency

Re: [sage-devel] Re: lib*.so conflict

2018-03-06 Thread Ralf Stephan
Very good. Doesn't it only work if the user not only has the library but also the respective headers, i.e., the corresponding xyz-devel package installed? On Tuesday, March 6, 2018 at 4:54:12 PM UTC+1, Erik Bray wrote: > > On Mon, Mar 5, 2018 at 12:02 PM, Dima Pasechnik >

Re: [sage-devel] Re: Git push issues

2018-03-06 Thread Erik Bray
Hi Meghana, I've manually deleted your duplicate SSH key, so you should be able to push again for now. Best, E On Tue, Mar 6, 2018 at 5:02 PM, Erik Bray wrote: > There's also an issue that if you've made both a local account on the > Trac server, and you have logged in

Re: [sage-devel] can't install dot2tex package in Sage 8.1

2018-03-06 Thread Jeroen Demeyer
On 2018-03-06 14:42, Vít Tuček wrote: I tried install dot2tex in Sage 8.1 How? Which command did you run? and got error building mpfr. Which error did you get exactly? See https://www.chiark.greenend.org.uk/~sgtatham/bugs.html -- You received this message because you are subscribed to

Re: [sage-devel] Re: Git push issues

2018-03-06 Thread Erik Bray
There's also an issue that if you've made both a local account on the Trac server, and you have logged in with GitHub (i.e. your gh- username), and if you've saved the same SSH key with both accounts, then the push authorization scripts can fail. This is because "" and "gh-" are treated as

Re: [sage-devel] Re: lib*.so conflict

2018-03-06 Thread Erik Bray
On Mon, Mar 5, 2018 at 12:02 PM, Dima Pasechnik wrote: > > > On Monday, March 5, 2018 at 9:48:25 AM UTC, Ralf Stephan wrote: >> >> I'm interested in a fix because it prevents clean patchbot results on >> OpenSuSE > > > Erik has an implementation of such feature generically, on

[sage-devel] Re: Git push issues

2018-03-06 Thread Eric Gourgoulhon
Le mardi 6 mars 2018 16:31:56 UTC+1, Eric Gourgoulhon a écrit : > > > The target on trac does not seem correct; the syntax of the push command > should be > > git push trac HEAD:u/user_name/branch_name > > > For more details, see

[sage-devel] Re: Git push issues

2018-03-06 Thread Eric Gourgoulhon
Hi, Le mardi 6 mars 2018 13:17:56 UTC+1, Meghana.M Reddy a écrit : > > ! [remote rejected] HEAD -> t/24909/boruvka_algorithm_for_mst (hook > declined) > error: failed to push some refs to 'g...@trac.sagemath.org:sage.git' > > The target on trac does not seem correct; the syntax of the push

Re: [sage-devel] Re: BUGS in tensor products of algebras

2018-03-06 Thread Vít Tuček
Dne pátek 2. března 2018 0:08:46 UTC+1 Travis Scrimshaw napsal(a): > > > >>> Free abelian monoid... Hmmm... What free abelian monoid? sage: PBW.basis().keys().an_element() PBW[alpha[1]]^2*PBW[alphacheck[1]]^2*PBW[-alpha[1]]^3 So PBW.basis() is _indexed_

[sage-devel] can't install dot2tex package in Sage 8.1

2018-03-06 Thread Vít Tuček
Hi! I tried install dot2tex in Sage 8.1 and got error building mpfr. See the attached log. At first it actually failed with complaints about mpfr being too old (version 3.8 or something) so I did ./sage --package update mpfr 4.0.1 --url

[sage-devel] Git push issues

2018-03-06 Thread Meghana.M Reddy
Hi, I am new to sage and fairly new to git too. I am working on implementing an algorithm in Sage and I followed all the doc pages for setting up git trac. I have created a new ticket for the algorithm I implemented and would like to push my local branch to this ticket. The git trac push

Re: [sage-devel] Make JupyterLab a standard package

2018-03-06 Thread Jeroen Demeyer
On 2018-03-06 00:29, Samuel Lelièvre wrote: I opened a ticket to make JupyterLab a standard package: https://trac.sagemath.org/ticket/24904 Any opinions? Shouldn't it be an optional package first? -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] Re: Asking for advice: differential operators in the global namespace

2018-03-06 Thread Eric Gourgoulhon
Thank you all for your answers! The conclusion is pretty clear: the differential operators will *not* be added to the global namespace at start, even less be added silently when a pseudo-Riemannian manifold is constructed. The only way to get them will be an explicit demand from the user, in