[sage-support] Re: Error building 9.8 on Ubuntu 23.04

2023-04-09 Thread Matthias Koeppe 
Try if "make sage_conf" fixes this problem.
If this persists, please post the file "config.log".

On Saturday, April 8, 2023 at 3:19:13 PM UTC-7 Eric Majzoub wrote:

> Thank you, this allows sage to complete the build. However, now I have 
> another problem. When I run sage from its install directory it gives the 
> error:
>
> AttributeError: module 'sage_conf' has no attribute '_main'
>
> And then strangely, it starts Sage 9.5, the version installed on my system 
> through apt. I didn't want to remove this version using apt because I 
> thought it would remove a lot of packages that I need for other programs. 
> Here is the full output.
>
> ./sage 
> Traceback (most recent call last): 
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 33, in <
> module> 
>sys.exit(load_entry_point('sage-conf', 'console_scripts', 
> 'sage-config')()) 
> ^^^ 
>
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 25, in i
> mportlib_load_entry_point 
>return next(matches).load() 
>    
>  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 204, in 
> load 
>return functools.reduce(getattr, attrs, module) 
>    
> AttributeError: module 'sage_conf' has no attribute '_main' 
> Traceback (most recent call last): 
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 33, in <
> module> 
>sys.exit(load_entry_point('sage-conf', 'console_scripts', 
> 'sage-config')()) 
> ^^^ 
>
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 25, in i
> mportlib_load_entry_point 
>return next(matches).load() 
>    
>  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 204, in 
> load 
>return functools.reduce(getattr, attrs, module) 
>    
> AttributeError: module 'sage_conf' has no attribute '_main' 
> ┌┐ 
> │ SageMath version 9.5, Release Date: 2022-01-30 │ 
> │ Using Python 3.11.2. Type "help()" for help.   │ 
> └┘
>
>
>
> On Friday, April 7, 2023 at 4:53:15 PM UTC-5 John H Palmieri wrote:
>
>> Some recent versions of Singular don't seem to work with Sage. You could 
>> try "make distclean" (to start over) and "./configure 
>> --with-system-singular=no" to force Sage to build its own Singular. Then 
>> "make".
>>
>> On Friday, April 7, 2023 at 2:22:20 PM UTC-7 Eric Majzoub wrote:
>>
>>> Following the procedure outlined on the Sage install page for Ubuntu.
>>>
>>> make fails showing:
>>> Error building Sage. 
>>>
>>> The following package(s) may have failed to build (not necessarily 
>>> during this run of 'make all-start'): 
>>>
>>> * package: sagelib-9.8 
>>>  last build time: Apr 7 15:48 
>>>  log file:/home/packages/SOURCE/sage/logs/pkgs/sagelib-9.8.log
>>>
>>> The log file is attached. It shows that gcc exits with status 1, but 
>>> doesn't give any specific error output from gcc itself. It fails on 
>>> building multi_polynomial_libsingular.
>>>
>>> Any help is appreciated.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/d0d508eb-6bbd-4928-8c0f-f00c760976f8n%40googlegroups.com.

Re: [sage-support] Testing forked branches

2023-04-09 Thread G. M.-S. 
You are right, John.  I did not read it carefully enough.

Guillermo

On Sun, 9 Apr 2023 at 05:38, John H Palmieri  wrote:

> I have found the instructions at
> https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
> useful for me, as someone used to the old trac interface.
>
> On Saturday, April 8, 2023 at 1:23:06 PM UTC-7 G. M.-S. wrote:
>
>>
>> Thanks Dima and Drew.
>>
>> I had the very same question, but zero ways for doing it, so I did not
>> dare ask…
>>
>> Guillermo
>>
>> On Sat, 8 Apr 2023 at 22:14, Dima Pasechnik  wrote:
>>
>>>
>>> On Sat, 8 Apr 2023, 20:24 Drew Shotwell,  wrote:
>>>
 I'm looking into working on an issue in git, and I'm wondering how to
 properly go about testing someone else's branch. Let's take for instance
 https://github.com/sagemath/sage/pull/35414.
>>>
>>>
>>> suppose you have remote foo set to
>>> https://github.com/sagemath/sage
>>> 
>>>
>>> then
>>>
>>> git fetch foo pull/35414 
>>> /head:pr35414
>>>
>>> will create the branch named pr35414 you want
>>>
>>> Essentially what I want to do is get the code changes from the forked
 branch videlec:complex-root-of-to-algebraic into my repository so I can
 test them in parallel with the develop branch. My own research has opened
 an overwhelming number of different ways for doing this, so I figured I'd
 ask here to get the most straight forward answer. Thank you.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CANnG18-p_u8WaHggnxdwte%2BfnNLJL33vyJszfBUb2Oe_QDHyoA%40mail.gmail.com.

Re: [sage-support] Testing forked branches

2023-04-09 Thread Dima Pasechnik 
another option is to use gh tool from GitHub.

 gh pr checkout 35414

would do the same as

 git fetch foo pull/35414/head:pr35414 && git checkout pr35414


On Sun, Apr 9, 2023 at 4:38 AM John H Palmieri  wrote:
>
> I have found the instructions at 
> https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
>  useful for me, as someone used to the old trac interface.
>
>
> On Saturday, April 8, 2023 at 1:23:06 PM UTC-7 G. M.-S. wrote:
>>
>>
>> Thanks Dima and Drew.
>>
>> I had the very same question, but zero ways for doing it, so I did not dare 
>> ask…
>>
>> Guillermo
>>
>> On Sat, 8 Apr 2023 at 22:14, Dima Pasechnik  wrote:
>>>
>>>
>>> On Sat, 8 Apr 2023, 20:24 Drew Shotwell,  wrote:

 I'm looking into working on an issue in git, and I'm wondering how to 
 properly go about testing someone else's branch. Let's take for instance 
 https://github.com/sagemath/sage/pull/35414.
>>>
>>>
>>> suppose you have remote foo set to
>>> https://github.com/sagemath/sage
>>>
>>> then
>>>
>>> git fetch foo pull/35414/head:pr35414
>>>
>>> will create the branch named pr35414 you want
>>>
>>>
 Essentially what I want to do is get the code changes from the forked 
 branch videlec:complex-root-of-to-algebraic into my repository so I can 
 test them in parallel with the develop branch. My own research has opened 
 an overwhelming number of different ways for doing this, so I figured I'd 
 ask here to get the most straight forward answer. Thank you.
>>
>>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-support+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/04a58ebe-6365-4439-904a-2f8827dd2a47n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAAWYfq2%3DLyxNe0MsBN6YWeLxQbwLU8%2B5FSh_9A%3D97pmXc5uBcQ%40mail.gmail.com.