your log appears to show that Singular was not built correctly.
Can you look at logs/pkg/singular*.log,
or just post it here?
On Fri, 22 Jul 2022, 01:39 Lucas Tan, wrote:
> Hi Matthias,
>
> I restarted the installation from scratch and verified that python3 has
> been accepted. This issue has b
Dear All,
I pushed a commit to trac https://trac.sagemath.org/ticket/32181, the lint
and documentation build failed in the cloud testing, but the documentation
builds and pycodetest minimal passed and succeeded in my local machine. I'm
wondering if I should push it again, or is there anything
On Thursday, July 21, 2022 at 11:52:42 AM UTC-7 Nils Bruin wrote:
> Conda looks like it has potential too,
>
I'd say that's an understatement
> It's presently unclear to me [...] whether a "production" conda build
> could co-exist with a "development" conda build: is "conda activate"
> somet
On Thursday, July 21, 2022 at 11:52:42 AM UTC-7 Nils Bruin wrote:
> somehow register those packages *are* dependencies ... I guess that could
> be done by building a placeholder package (rpm or deb) that declares all
> the specific dependencies. And to "declare" these, one could install that
>
I have opened https://trac.sagemath.org/ticket/34207 with the goal of
adding documentation on best practices. Help welcome
On Thursday, July 21, 2022 at 11:31:35 AM UTC-7 Matthias Koeppe wrote:
> On Thursday, July 21, 2022 at 11:14:13 AM UTC-7 Nils Bruin wrote:
>
>> On Wednesday, 20 July 2022 a
On Thursday, 21 July 2022 at 11:31:35 UTC-7 Matthias Koeppe wrote:
>
> You really just need to stop your distribution from automatically
> uninstalling the old shared library packages when you do upgrades. Both the
> old version (needed for your from-source installation of Sage) and the new
> v
On Thursday, July 21, 2022 at 11:14:13 AM UTC-7 Nils Bruin wrote:
> On Wednesday, 20 July 2022 at 23:33:09 UTC-7 Antonio Rojas wrote:
>
>>
>> They are not, that's exactly the point of library soversions. The
>> soversion, if correctly used, is bumped when a release contains some ABI
>> incompati
On Wednesday, 20 July 2022 at 23:33:09 UTC-7 Antonio Rojas wrote:
>
> They are not, that's exactly the point of library soversions. The
> soversion, if correctly used, is bumped when a release contains some ABI
> incompatible change that requires a rebuild of consumers. So you can't just
> link
This is documented
in
https://doc.sagemath.org/html/en/installation/conda.html#sec-installation-conda-develop
On Thursday, July 21, 2022 at 1:02:22 AM UTC-7 Dima Pasechnik wrote:
>
>
> On Thu, 21 Jul 2022, 07:25 Nils Bruin, wrote:
>
>>
>> It seems that the correct way to use "system" packages
On Thu, 21 Jul 2022, 07:25 Nils Bruin, wrote:
>
> It seems that the correct way to use "system" packages in an
>> upgradeable way is to make sure that Sage is such a package itself.
>> Here "system" means either your OS, or Conda.
>> And Conda comes with a quite fresh version of Sage, so it looks
By reading the configure messages
On Thursday, July 21, 2022 at 12:37:08 AM UTC-7 lucas@gmail.com wrote:
> How do I verify that Cygwin python3 is accepted?
>
> On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
>
>> No, these system packages need to be installed. Otherwise you
How do I verify that Cygwin python3 is accepted?
On Thursday, 21 July 2022 at 15:12:29 UTC+8 Matthias Koeppe wrote:
> No, these system packages need to be installed. Otherwise you won't get
> Cygwin's python package accepted.
>
> I recommend to start from scratch. Run configure, read what it rec
No, these system packages need to be installed. Otherwise you won't get
Cygwin's python package accepted.
I recommend to start from scratch. Run configure, read what it recommends
to install via Cygwin, do this installation, then run configure again.
Before running "make", verify that it accepts
13 matches
Mail list logo
