Unable to build sage after git trac config

74 views
Skip to first unread message

Vipul Gupta

unread,
Jan 29, 2020, 6:04:12 PM1/29/20
to sage-devel
Hello,
I am using Ubuntu 18.04.3 LTS with sage version 9.1 beta 2
 After using below command
cd sage
git checkout develop
make
source git-trac-command/enable.sh
echo $PATH
cd git-trac-command
ln -s `pwd`/git-trac ~/bin/
git trac config --user USERNAME --pass 'PASSWORD'
ssh-add
I was unable to build sage
I tried using './sage -br' and 'make' also.
But it is still not working 
I am attaching the log file here.
Kindly help me with this I am new here.
Regards 
Vipul  Gupta

output.txt

Dima Pasechnik

unread,
Jan 29, 2020, 6:14:36 PM1/29/20
to sage-devel
you don't need git-trac-command to build Sage.
What do you see after

git clone git://github.com/sagemath/sage.git
cd sage
git checkout develop
make

?

By the way, please make sure you install packages mentioned in
https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation
> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2BSFJRdJk7dUMYDQVQM7x5kUMQeq1eN6%3DPixjeeF%2Bz0eE82Bnw%40mail.gmail.com.

Vipul Gupta

unread,
Jan 29, 2020, 10:06:02 PM1/29/20
to sage-...@googlegroups.com
Hello, 


On Thu, 30 Jan, 2020, 4:44 am Dima Pasechnik, <dim...@gmail.com> wrote:
you don't need git-trac-command to build Sage.
What do you see after

git clone git://github.com/sagemath/sage.git
cd sage
git checkout develop
make

?
Yeah Sage works fine after that. But I wanted to contribute to sage and therefore config my git trac account as mentioned in the this link https://doc.sagemath.org/html/en/developer/git_trac.html

By the way, please make sure you install packages mentioned in
https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation
I have installed all these packages. 
Regards 
Vipul Gupta

Eric Gourgoulhon

unread,
Jan 30, 2020, 4:17:02 AM1/30/20
to sage-devel
Hi,

Le jeudi 30 janvier 2020 04:06:02 UTC+1, Vipul Gupta a écrit :

Yeah Sage works fine after that. But I wanted to contribute to sage and therefore config my git trac account as mentioned in the this link https://doc.sagemath.org/html/en/developer/git_trac.html


Welcome to Sage development!
I would  recommend not to use the git-trac commands, but plain git.
There are regularly some issues with git-trac and using plain git is much more robust than git-trac.
I would even vote for removing the git-trac section from the developer manual.

Best wishes,

Eric.

Simon King

unread,
Jan 30, 2020, 7:35:17 AM1/30/20
to sage-...@googlegroups.com
Hi Eric,

On 2020-01-30, Eric Gourgoulhon <egourg...@gmail.com> wrote:
> I would even vote for removing the git-trac section from the developer
> manual.

-1

I do use "git trac".

Best regards,
Simon

David Roe

unread,
Jan 30, 2020, 9:07:58 AM1/30/20
to sage-devel
On Thu, Jan 30, 2020 at 7:35 AM Simon King <simon...@uni-jena.de> wrote:
Hi Eric,

On 2020-01-30, Eric Gourgoulhon <egourg...@gmail.com> wrote:
> I would even vote for removing the git-trac section from the developer
> manual.

-1

I do use "git trac".

Agreed.  I would absolutely not advocate removing git-trac from the manual.  I find that it makes some tasks easier than using plain git.

For the original poster, what problems are you having with git-trac?
David


Best regards,
Simon


--
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+...@googlegroups.com.

Dima Pasechnik

unread,
Jan 30, 2020, 9:15:58 AM1/30/20
to sage-devel
I think git-trac should not be mentioned in the manual as the preferred way to use git.

Imho the majority of devs here use plain git...

Vipul Gupta

unread,
Jan 30, 2020, 10:16:36 AM1/30/20
to sage-devel
Can someone help me with guidelines to make contribution using only git? 
Regards
Vipul Gupta

Dima Pasechnik

unread,
Jan 30, 2020, 10:31:37 AM1/30/20
to sage-devel
Are you familiar with using github server and  CLI to checkout specific branches and pushing into a github repo?
(there are excellent tutorials on this).

In fact, you can create your own fork of sagemath on github and practice there.
Our workflow is similar, except that it has a much cruder web interface.

There is also a description on this in our development manual, but it is a bit too terse.



Simon King

unread,
Jan 30, 2020, 10:36:01 AM1/30/20
to sage-...@googlegroups.com
Hi Dima,

On 2020-01-30, Dima Pasechnik <dim...@gmail.com> wrote:
> I think git-trac should not be mentioned in the manual as the preferred way
> to use git.

OK. Stating that "being able to use plain git is a useful skill" is
fine, and of course elaborating how to use plain git to work with trac
is fine, too. But please do not remove the customised scripts or their
documentation.

Best regards,
Simon

Vipul Gupta

unread,
Jan 30, 2020, 10:37:45 AM1/30/20
to sage-devel
Yeah I am familiar with github and its features. But I am not sure how to incorporate ticket features of sage issues and contribute to them?  
Briefly, I want to ask how to work with tickets using git only. There are no clear manuals for this also. 
Regards 
Vipul Gupta

Dima Pasechnik

unread,
Jan 30, 2020, 10:55:41 AM1/30/20
to sage-devel


On Thu, 30 Jan 2020, 15:37 Vipul Gupta, <vipul.gu...@gmail.com> wrote:
Yeah I am familiar with github and its features. But I am not sure how to incorporate ticket features of sage issues and contribute to them?  
Briefly, I want to ask how to work with tickets using git only. There are no clear manuals for this also. 

there is not much to document. 

You create/update named branches and push them to the trac git repository for reviewing. The branch name is entered into a field on the ticket form, and so it (more precisely, the diff against the current develop branch) gets displayed nicely. Reviewers look at it, test it, there is also some CI happening.

Once it gets a positive review, the release manager will merge it into the main branches.

Details like how to name branches, and how to set "git remote" are documented.





John H Palmieri

unread,
Jan 30, 2020, 1:32:52 PM1/30/20
to sage-devel


On Wednesday, January 29, 2020 at 3:04:12 PM UTC-8, Vipul Gupta wrote:
Hello,
I am using Ubuntu 18.04.3 LTS with sage version 9.1 beta 2
 After using below command
cd sage
git checkout develop
make

Okay up to here. Before doing the next command, cd to a different directory: there is no reason to clone the git-trac-command repository within the Sage directory, and I suppose it could cause problems.
 
source git-trac-command/enable.sh
echo $PATH
cd git-trac-command

Rather than the following command, I would recommend the directions in the file README.md, included with git-trac-command.
 
ln -s `pwd`/git-trac ~/bin/

git trac config --user USERNAME --pass 'PASSWORD'
ssh-add
I was unable to build sage

What went wrong? Just installing git-trac-command should not interfere with building Sage. Could you provide the file `logs/install.log`? (Maybe delete that file first, then run `make`, which will produce a new log file, and attach the new one.)
 
I tried using './sage -br' and 'make' also.
But it is still not working 
I am attaching the log file here.

The file output.txt has strange entries at the top, and the official log file might be more helpful.

Vipul Gupta

unread,
Jan 31, 2020, 8:47:19 AM1/31/20
to sage-devel
Thanks you very much for your guidelines.
It solved my problem.
Regards 
Vipul Gupta 

Reply all
Reply to author
Forward
0 new messages