Thanks a lot for the patches Ahzo. Especially fixing the file handle leak
should help a lot.
I guess it's too late for bullseye now, but I can at least upload a fixed
package to experimental. I'll also try to fix many of the failing tests by
including sage's (large) patch to support pari 2.13
Hi,
that's great, help on it is always appreciated. I'm not sure what exactly went
wrong, debuild should work. Please see
https://wiki.debian.org/DebianScience/Sage for instructions for building
directly from git.
Best,
Tobias
On 5/28/21 10:46 AM, erentar2002 wrote:
>
> Sagemath 9.3 got
Hi,
On 5/18/21 8:25 PM, Jochen Sprickerhof wrote:
>
> I think there are a number of problems:
> - Tests not being executed due to the open file limit ("Killing test" in
> the log). If you want to use the tests as an indicator if the build works,
> you should make sure the all tests are
Hi,
On 5/18/21 8:25 PM, Jochen Sprickerhof wrote:
>
> I think there are a number of problems:
> - Tests not being executed due to the open file limit ("Killing test" in
> the log). If you want to use the tests as an indicator if the build works,
> you should make sure the all tests are
Hi,
On 5/18/21 8:25 PM, Jochen Sprickerhof wrote:
>
> I think there are a number of problems:
> - Tests not being executed due to the open file limit ("Killing test" in
> the log). If you want to use the tests as an indicator if the build works,
> you should make sure the all tests are
On 12/9/20 4:56 PM, Bill Allombert wrote:
On Wed, Dec 09, 2020 at 04:21:39PM +, Tobias Hansen wrote:
On 12/9/20 4:15 PM, Bill Allombert wrote:
On Mon, Nov 16, 2020 at 11:16:58AM +0100, Bill Allombert wrote:
On Mon, Nov 16, 2020 at 12:19:07AM +, Tobias Hansen wrote:
Package: pari-gp
On 12/9/20 4:15 PM, Bill Allombert wrote:
On Mon, Nov 16, 2020 at 11:16:58AM +0100, Bill Allombert wrote:
On Mon, Nov 16, 2020 at 12:19:07AM +, Tobias Hansen wrote:
Package: pari-gp
Version: 2.13.0-2
Severity: normal
Hi,
with pari 2.13.0-2 the following code (which is a sagemath test
Hi,
thanks for the report. I am waiting for upstream to complete their support for
pari 2.13 [1].
I could already include their incomplete patch with ~150 failing doctests, or
might as well wait for the patch to be completed.
Best,
Tobias
[1] https://trac.sagemath.org/ticket/30801
On
Hi,
thanks for the report. I am waiting for upstream to complete their support for
pari 2.13 [1].
I could already include their incomplete patch with ~150 failing doctests, or
might as well wait for the patch to be completed.
Best,
Tobias
[1] https://trac.sagemath.org/ticket/30801
On
Package: pari-gp
Version: 2.13.0-2
Severity: normal
Hi,
with pari 2.13.0-2 the following code (which is a sagemath test and worked with
pari 2.11.4) hangs indefinitely in gp when calling rnfinit.
? default(parisizemax, 6400)
*** Warning: new maximum stack size = 6400 (61.035
Control: tags -1 + fixed-upstream patch
The bug was fixed upstream in the linked issue. Can we apply the attached
upstream patch?
Best,
Tobias
On Fri, 18 Sep 2020 18:09:01 +0200 Tobias Hansen wrote:
> Package: libopenblas0
> Version: 0.3.10+ds-3
> Severity: normal
>
> Hi,
Control: tags -1 + fixed-upstream patch
The bug was fixed upstream in the linked issue. Can we apply the attached
upstream patch?
Best,
Tobias
On Fri, 18 Sep 2020 18:09:01 +0200 Tobias Hansen wrote:
> Package: libopenblas0
> Version: 0.3.10+ds-3
> Severity: normal
>
> Hi,
Control: tags -1 + pending
It should be fixed in git, but before another upload cypari2 needs to be
updated.
Best,
Tobias
On 10/27/20 5:17 PM, Graham Inggs wrote:
> Control: reopen -1
>
> Hi
>
> The new upload of sagemath/9.2-1 still FTBFS [1] with Python 3.9 as
> default. I've copied what I
Control: tags -1 + pending
It should be fixed in git, but before another upload cypari2 needs to be
updated.
Best,
Tobias
On 10/27/20 5:17 PM, Graham Inggs wrote:
> Control: reopen -1
>
> Hi
>
> The new upload of sagemath/9.2-1 still FTBFS [1] with Python 3.9 as
> default. I've copied what I
Control: tags -1 + pending
It should be fixed in git, but before another upload cypari2 needs to be
updated.
Best,
Tobias
On 10/27/20 5:17 PM, Graham Inggs wrote:
> Control: reopen -1
>
> Hi
>
> The new upload of sagemath/9.2-1 still FTBFS [1] with Python 3.9 as
> default. I've copied what I
Package: libopenblas0
Version: 0.3.10+ds-3
Severity: normal
Hi,
a sagemath test segfaulted in libopenblas.so.0 / zgemm_oncopy_EMAG8180 when
building on arm-ubc-01.debian.org,
see
https://buildd.debian.org/status/fetch.php?pkg=sagemath=arm64=9.2%7Ebeta12-1=159992=0
openblas was called by
Package: libopenblas0
Version: 0.3.10+ds-3
Severity: normal
Hi,
a sagemath test segfaulted in libopenblas.so.0 / zgemm_oncopy_EMAG8180 when
building on arm-ubc-01.debian.org,
see
https://buildd.debian.org/status/fetch.php?pkg=sagemath=arm64=9.2%7Ebeta12-1=159992=0
openblas was called by
Control: tag -1 pending
Hello,
Bug #955082 in pexpect reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
since flint 2.6.3 is now in unstable, can this be fixed with a rebuild?
Best,
Tobias
On Wed, 29 Jul 2020 09:36:31 +0200 Jerome BENOIT wrote:
> Hello Lucas, thanks for the report. I am working on it. Jerome
> --
> Jerome BENOIT | calculus+at-rezozer^dot*net
>
Hi,
since flint 2.6.3 is now in unstable, can this be fixed with a rebuild?
Best,
Tobias
On Wed, 29 Jul 2020 09:36:31 +0200 Jerome BENOIT wrote:
> Hello Lucas, thanks for the report. I am working on it. Jerome
> --
> Jerome BENOIT | calculus+at-rezozer^dot*net
>
Control: tags 963338 + help
Just yesterday I just did a test build of vanilla sage (not the Debian package)
9.2.beta6 with the python 3.8 patch from [1] and Debian's python 3.8 to see if
the file handle leak that happens during parallel builds of the Debian package
also happens there. It
Control: tags 963338 + help
Just yesterday I just did a test build of vanilla sage (not the Debian package)
9.2.beta6 with the python 3.8 patch from [1] and Debian's python 3.8 to see if
the file handle leak that happens during parallel builds of the Debian package
also happens there. It
Control: tags 963338 + help
Just yesterday I just did a test build of vanilla sage (not the Debian package)
9.2.beta6 with the python 3.8 patch from [1] and Debian's python 3.8 to see if
the file handle leak that happens during parallel builds of the Debian package
also happens there. It
Control: severity -1 important
Please someone do this, having these small default sizes for /boot is really
annoying and has been the only reason I had to reinstall Debian on several
systems over the years. Let me explain.
I usually use guided partitioning to set up encrypted LVM. Doing this,
Control: severity -1 important
Please someone do this, having these small default sizes for /boot is really
annoying and has been the only reason I had to reinstall Debian on several
systems over the years. Let me explain.
I usually use guided partitioning to set up encrypted LVM. Doing this,
Source: gap-atlasrep
Version: 2.1.0-1
Severity: grave
Hi Bill,
during a test build of sage I noticed that the newly updated gap-atlasrep
package seems to be seriously broken. Trying the first commands from the
atlasrep tutorial yields this:
$ gap
┌───┐ GAP 4.10.2 of 19-Jun-2019
│ GAP
Source: gap-atlasrep
Version: 2.1.0-1
Severity: grave
Hi Bill,
during a test build of sage I noticed that the newly updated gap-atlasrep
package seems to be seriously broken. Trying the first commands from the
atlasrep tutorial yields this:
$ gap
┌───┐ GAP 4.10.2 of 19-Jun-2019
│ GAP
On 3/26/20 10:56 PM, Bill Allombert wrote:
> On Wed, Mar 25, 2020 at 08:32:59PM +0100, Tobias Hansen wrote:
>>> If I release 2.11.4-pre1 on April 3, would that be OK ?
>>>
>>> Cheers,
>> Sure, but that means that the fix would only be in Debian with the
>&
On 3/25/20 8:28 PM, Bill Allombert wrote:
> On Wed, Mar 25, 2020 at 03:02:48PM +0100, Tobias Hansen wrote:
>> On 3/25/20 1:08 PM, Bill Allombert wrote:
>>> On Wed, Mar 25, 2020 at 12:47:17PM +0100, Tobias Hansen wrote:
>>>> Hi Bill,
>>>>
>>
On 3/25/20 1:08 PM, Bill Allombert wrote:
> On Wed, Mar 25, 2020 at 12:47:17PM +0100, Tobias Hansen wrote:
>> Hi Bill,
>>
>> is pari 2.11.4-pre1 going to be released soon? Otherwise, could you
>> please consider backporting the patch for the Debian package? sagemath
On 3/11/20 11:27 PM, Tobias Hansen wrote:
> On 3/11/20 8:22 PM, Bill Allombert wrote:
>> On Wed, Mar 11, 2020 at 02:15:31PM +0000, Tobias Hansen wrote:
>>> Source: pari
>>> Version: 2.11.3-1
>>> Severity: normal
>>> Tags: patch
>>>
>
The reason for this is that src/scripts/cysignals-CSI calls python which is not
installed. The script has to be ported to python3.
Best,
Tobias
On 2/23/20 2:37 PM, Lucas Nussbaum wrote:
> Source: cysignals
> Version: 1.10.2+ds-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags:
The reason for this is that src/scripts/cysignals-CSI calls python which is not
installed. The script has to be ported to python3.
Best,
Tobias
On 2/23/20 2:37 PM, Lucas Nussbaum wrote:
> Source: cysignals
> Version: 1.10.2+ds-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags:
Control: block -1 by 953633
We have a patch for this but I'm waiting for a fix of a bug in pari that causes
test failures and a test timeout.
Best,
Tobias
On Wed, 29 Jan 2020 17:46:47 +0100 Tobias Hansen wrote:
> It does if applied first. But ok, the ipython 7 patch needed some sm
Control: block -1 by 953633
We have a patch for this but I'm waiting for a fix of a bug in pari that causes
test failures and a test timeout.
Best,
Tobias
On Wed, 29 Jan 2020 17:46:47 +0100 Tobias Hansen wrote:
> It does if applied first. But ok, the ipython 7 patch needed some sm
Control: block -1 by 953633
We have a patch for this but I'm waiting for a fix of a bug in pari that causes
test failures and a test timeout.
Best,
Tobias
On Wed, 29 Jan 2020 17:46:47 +0100 Tobias Hansen wrote:
> It does if applied first. But ok, the ipython 7 patch needed some sm
On 3/11/20 8:22 PM, Bill Allombert wrote:
> On Wed, Mar 11, 2020 at 02:15:31PM +0000, Tobias Hansen wrote:
>> Source: pari
>> Version: 2.11.3-1
>> Severity: normal
>> Tags: patch
>>
>> Hi Bill,
>>
>> please consider backporting the p
Source: pari
Version: 2.11.3-1
Severity: normal
Tags: patch
Hi Bill,
please consider backporting the patch for the pari bugs #2164 and #2208. It
seems to be a serious bug and it breaks several things in sagemath that worked
with 2.11.2.
The patch is at
Hi,
yes, it also looks more like doxygen bug to me. I didn't reassign yet because
if doxygen upstream does not want to fix it, a workaround in ppl (not pplpy)
might be needed.
Best,
Tobias
On 2/23/20 8:46 PM, Julien Puydt wrote:
> Hi,
>
> it looks more like a doxygen 1.8.16 bug than a pplpy
Hi,
yes, it also looks more like doxygen bug to me. I didn't reassign yet because
if doxygen upstream does not want to fix it, a workaround in ppl (not pplpy)
might be needed.
Best,
Tobias
On 2/23/20 8:46 PM, Julien Puydt wrote:
> Hi,
>
> it looks more like a doxygen 1.8.16 bug than a pplpy
Hi,
yes, it also looks more like doxygen bug to me. I didn't reassign yet because
if doxygen upstream does not want to fix it, a workaround in ppl (not pplpy)
might be needed.
Best,
Tobias
On 2/23/20 8:46 PM, Julien Puydt wrote:
> Hi,
>
> it looks more like a doxygen 1.8.16 bug than a pplpy
On 2/13/20 5:49 PM, Bill Allombert wrote:
> On Thu, Feb 13, 2020 at 05:28:10PM +0100, Tobias Hansen wrote:
>> Source: gap
>> Version: 4r10p2-2
>> Severity: normal
>>
>> Hi Bill,
>>
>> please keep in mind to create a library package for libgap and insta
a library
package.
Best,
Tobias
On 12/16/18 10:24 PM, Bill Allombert wrote:
> On Sun, Dec 16, 2018 at 08:25:17PM +0100, Tobias Hansen wrote:
>> + * Install libgap to /usr/lib/triplet.
>
> Do you need this now ? When the interface to libgap has stabilized, then
> probably we will
Hi Matthias,
you reassigned the two bugs #945522 and #949029 to brial, however I don't see
any connection to brial. Neither beancount nor python-bleach depends on brial,
which is a math library for dealing with polynomials over boolean rings by the
way.
Did you confuse brial with something
Hi Matthias,
you reassigned the two bugs #945522 and #949029 to brial, however I don't see
any connection to brial. Neither beancount nor python-bleach depends on brial,
which is a math library for dealing with polynomials over boolean rings by the
way.
Did you confuse brial with something
Hi Matthias,
you reassigned the two bugs #945522 and #949029 to brial, however I don't see
any connection to brial. Neither beancount nor python-bleach depends on brial,
which is a math library for dealing with polynomials over boolean rings by the
way.
Did you confuse brial with something
Hi,
looks like an instance of #907119 which was fixed in gsl 2.5+dfsg-5, however
you have gsl 2.5+dfsg-4 installed. Please update your packages to the versions
in unstable.
Best,
Tobias
On 2/2/20 9:13 AM, Kingsley G. Morse Jr. wrote:
> ImportError:
Hi,
looks like an instance of #907119 which was fixed in gsl 2.5+dfsg-5, however
you have gsl 2.5+dfsg-4 installed. Please update your packages to the versions
in unstable.
Best,
Tobias
On 2/2/20 9:13 AM, Kingsley G. Morse Jr. wrote:
> ImportError:
Thanks, that got lost in the other bug.
It is correct bash test syntax (see 'man test') where -a between two logical
expressions means 'and'. mips64 is the GNU name for the architecture, mips64el
is an invention of Debian.
Best,
Tobias
On 2/2/20 4:22 AM, John Scott wrote:
> On the off-chance
Thanks, that got lost in the other bug.
It is correct bash test syntax (see 'man test') where -a between two logical
expressions means 'and'. mips64 is the GNU name for the architecture, mips64el
is an invention of Debian.
Best,
Tobias
On 2/2/20 4:22 AM, John Scott wrote:
> On the off-chance
Package: libm4rie-0.0.20200125
Version: 20200125-1
Severity: serious
Hi,
seems that something went wrong with the binary upload of libm4rie on amd64. On
this architecture libm4rie-0.0.20200125 depends on libm4ri-0.0.20200115 which
makes it uninstallable. This might be fixable with a
Package: libm4rie-0.0.20200125
Version: 20200125-1
Severity: serious
Hi,
seems that something went wrong with the binary upload of libm4rie on amd64. On
this architecture libm4rie-0.0.20200125 depends on libm4ri-0.0.20200115 which
makes it uninstallable. This might be fixable with a
Package: libm4rie-0.0.20200125
Version: 20200125-1
Severity: serious
Hi,
seems that something went wrong with the binary upload of libm4rie on amd64. On
this architecture libm4rie-0.0.20200125 depends on libm4ri-0.0.20200115 which
makes it uninstallable. This might be fixable with a
It does if applied first. But ok, the ipython 7 patch needed some small
changes. I applied it in the branch python3.8 on salsa.
Best,
Tobias
On 1/29/20 5:35 PM, Matthias Klose wrote:
> On 1/29/20 5:20 PM, Tobias Hansen wrote:
>> Hi,
>>
>> Arch Linux has a pat
It does if applied first. But ok, the ipython 7 patch needed some small
changes. I applied it in the branch python3.8 on salsa.
Best,
Tobias
On 1/29/20 5:35 PM, Matthias Klose wrote:
> On 1/29/20 5:20 PM, Tobias Hansen wrote:
>> Hi,
>>
>> Arch Linux has a pat
Hi,
Arch Linux has a patch for that:
https://git.archlinux.org/svntogit/community.git/tree/trunk/sagemath-python-3.8.patch?h=packages/sagemath
We plan to apply it when the default Python switches to 3.8. If we apply it
now, the doctests will fail with Python 3.7. I haven't yet tried building
Hi,
Arch Linux has a patch for that:
https://git.archlinux.org/svntogit/community.git/tree/trunk/sagemath-python-3.8.patch?h=packages/sagemath
We plan to apply it when the default Python switches to 3.8. If we apply it
now, the doctests will fail with Python 3.7. I haven't yet tried building
Source: gfan
Version: 0.6.2-2
Severity: normal
Hi,
many of sagemath's doctests in the interface to gfan fail on riscv64 with the
following error:
gfan_*: src/application.cpp:42: char* tail(char*): Assertion `*p==*m' failed.
It looks like the pointer arithmetic in the function tail() in
Source: gfan
Version: 0.6.2-2
Severity: normal
Hi,
many of sagemath's doctests in the interface to gfan fail on riscv64 with the
following error:
gfan_*: src/application.cpp:42: char* tail(char*): Assertion `*p==*m' failed.
It looks like the pointer arithmetic in the function tail() in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 22 Jan 2020 22:37:42 +0100
Source: sagemath
Architecture: source
Version: 9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Tobias Hansen
Closes: 938426 944544 948212 948731 949287
Control: reassign -1 src:sagemath 8.9-3
Hi,
please wait for sagemath 9.0 with the bug reports. We know that sagemath 8.9 is
broken at the moment for various reasons. For one it has to be patched to work
with ipython 7 and there are several ongoing library transitions that break
sagemath 8.9.
Control: reassign -1 src:sagemath 8.9-3
Hi,
please wait for sagemath 9.0 with the bug reports. We know that sagemath 8.9 is
broken at the moment for various reasons. For one it has to be patched to work
with ipython 7 and there are several ongoing library transitions that break
sagemath 8.9.
Hi,
I think the point is that upsteam $0-version.sh is always available since the
script sage always comes with sage-version.sh in the same folder.
We just have to source sage-env before the problematic functions.
Best,
Tobias
On 1/18/20 1:31 PM, Julien Puydt wrote:
> Hi,
>
> I tried to have
Hi,
I think the point is that upsteam $0-version.sh is always available since the
script sage always comes with sage-version.sh in the same folder.
We just have to source sage-env before the problematic functions.
Best,
Tobias
On 1/18/20 1:31 PM, Julien Puydt wrote:
> Hi,
>
> I tried to have
Hi,
yes, we are building sagemath only for the default python. For transitioning to
python 3.8, upstream is still working on [1] doing it in a python 2 compatible
way I think. Since we don't have to support python 2 anymore we can just use
the patch from Arch Linux [2]. However the patch
Hi,
yes, we are building sagemath only for the default python. For transitioning to
python 3.8, upstream is still working on [1] doing it in a python 2 compatible
way I think. Since we don't have to support python 2 anymore we can just use
the patch from Arch Linux [2]. However the patch
t; Hi Tobias,
>
> I've just push to salsa the new upstream release. I will need sponsorship.
>
> Cheers,
> Arias Emmanuel
> @eamanu
> http://eamanu.com
>
> El vie., 17 de ene. de 2020 a la(s) 07:51, Tobias Hansen
> (than...@debian.org) escribió:
>>
>> Sour
t; Hi Tobias,
>
> I've just push to salsa the new upstream release. I will need sponsorship.
>
> Cheers,
> Arias Emmanuel
> @eamanu
> http://eamanu.com
>
> El vie., 17 de ene. de 2020 a la(s) 07:51, Tobias Hansen
> (than...@debian.org) escribió:
>>
>> Sour
t; Hi Tobias,
>
> I've just push to salsa the new upstream release. I will need sponsorship.
>
> Cheers,
> Arias Emmanuel
> @eamanu
> http://eamanu.com
>
> El vie., 17 de ene. de 2020 a la(s) 07:51, Tobias Hansen
> (than...@debian.org) escribió:
>>
>> Sour
Source: ipython
Version: 7.11.0-2
Severity: wishlist
Hi,
ipython 7.11.1 brought back some compatibility functions that are needed for
sagemath 9.0:
https://github.com/ipython/ipython/commit/9a8d1a345f48b7aa85e6a6da5841b65ee1f8de63#diff-230d8a7c9440fa2ab8c6a3ebe9a9f279
Could you please update
Source: ipython
Version: 7.11.0-2
Severity: wishlist
Hi,
ipython 7.11.1 brought back some compatibility functions that are needed for
sagemath 9.0:
https://github.com/ipython/ipython/commit/9a8d1a345f48b7aa85e6a6da5841b65ee1f8de63#diff-230d8a7c9440fa2ab8c6a3ebe9a9f279
Could you please update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 29 Dec 2019 01:11:19 +0100
Source: sludge
Architecture: source
Version: 2.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Tobias Hansen
Closes: 947663
Changes:
sludge (2.2.2-3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 01 Dec 2019 12:26:58 +
Source: sagemath
Architecture: source
Version: 8.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Tobias Hansen
Closes: 944648
Changes:
sagemath (8.9-3
Control: forwarded 944648 https://trac.sagemath.org/ticket/28795
On 11/28/19 2:09 AM, peter green wrote:
>> All three failures give the error message
>>
>> OverflowError: Python int too large to convert to C long
>>
>> from
>>
>> File "sage/rings/polynomial/polynomial_integer_dense_flint.pyx",
Control: forwarded 944648 https://trac.sagemath.org/ticket/28795
On 11/28/19 2:09 AM, peter green wrote:
>> All three failures give the error message
>>
>> OverflowError: Python int too large to convert to C long
>>
>> from
>>
>> File "sage/rings/polynomial/polynomial_integer_dense_flint.pyx",
Control: forwarded 944648 https://trac.sagemath.org/ticket/28795
On 11/28/19 2:09 AM, peter green wrote:
>> All three failures give the error message
>>
>> OverflowError: Python int too large to convert to C long
>>
>> from
>>
>> File "sage/rings/polynomial/polynomial_integer_dense_flint.pyx",
Version: 2.37.4-1+b1
Now trying to purge snapd leads directly to an error:
$ sudo apt purge snapd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
snapd*
0 upgraded, 0 newly installed, 1 to remove and 7 not
Package: ftp.debian.org
Severity: normal
Control: block 938427 by -1
Control: block 941693 by -1
Control: block -1 by 945397
Hi,
I'm requesting removal of sagenb on behalf of the Debian Science Team. There is
no Python 3 version and sagemath now uses Jupyter notebook instead (also see
Package: ftp.debian.org
Severity: normal
Hi,
since sagemath was switched over from Python 2 to Python 3 with version 8.9 it
has not yet been successfully built on armhf and i386. On these architectures
the sagemath 8.8 packages are still in unstable and depend on a large number of
Python 2
Source: three.js
Version: 80+dfsg2-2
Severity: important
Hi Jose,
thanks for reporting, I hereby filed it as a bug.
Best,
Tobias
On 11/13/19 8:57 AM, jose wrote:
> Please consider upgrading three.js to a more recent version. When trying to
> use plot3d I get only axes drawn (or even a black
It seems like the build failures are related to timeouts of jmol. These
timeouts started roughly at the time when the default Java version was changed
in java-common from 10 to 11 in October 2018.
There are also other reports of jmol being broken depending on the jre version,
see
It seems like the build failures are related to timeouts of jmol. These
timeouts started roughly at the time when the default Java version was changed
in java-common from 10 to 11 in October 2018.
There are also other reports of jmol being broken depending on the jre version,
see
It seems like the build failures are related to timeouts of jmol. These
timeouts started roughly at the time when the default Java version was changed
in java-common from 10 to 11 in October 2018.
There are also other reports of jmol being broken depending on the jre version,
see
Source: sagemath
Version: 8.9-2
Severity: serious
Since the switch to Python 3 in 8.9~beta9-1, sagemath fails to build from
source on i386. The reason are segmentation faults in the following three tests:
sage -t --long src/sage/schemes/elliptic_curves/isogeny_small_degree.py #
Killed due to
Source: sagemath
Version: 8.9-2
Severity: serious
Since the switch to Python 3 in 8.9~beta9-1, sagemath fails to build from
source on i386. The reason are segmentation faults in the following three tests:
sage -t --long src/sage/schemes/elliptic_curves/isogeny_small_degree.py #
Killed due to
Source: sagemath
Version: 8.9-2
Severity: serious
Since the switch to Python 3 in 8.9~beta9-1, sagemath fails to build from
source on i386. The reason are segmentation faults in the following three tests:
sage -t --long src/sage/schemes/elliptic_curves/isogeny_small_degree.py #
Killed due to
Hi,
it looks like prompt_toolkit was only added to sagemath because ipython depends
on it. So it could well be that the sagemath Debian package does not need a
direct dependency on it. Unfortunately sagemath does not say anywhere what are
its direct dependencies so the Debian package has some
Hi,
it looks like prompt_toolkit was only added to sagemath because ipython depends
on it. So it could well be that the sagemath Debian package does not need a
direct dependency on it. Unfortunately sagemath does not say anywhere what are
its direct dependencies so the Debian package has some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 10 Nov 2019 21:41:38 +0100
Source: sagemath
Architecture: source
Version: 8.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Tobias Hansen
Changes:
sagemath (8.9-2) unstable; urgency
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 10 Nov 2019 21:15:02 +0100
Source: brial
Architecture: source
Version: 1.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Tobias Hansen
Changes:
brial (1.2.5-2) unstable
Control: affects 941557 - src:maxima-sage
Thanks for providing the solution for the problem!
Best,
Tobias
On 10/29/19 2:24 PM, Norbert Preining wrote:
> reassign 941557 src:gri
> tags 941557 + patch
> retitle 941557 texi file need @documentencoding
> thanks
>
> With texinfo 6.7 finally the
Control: affects 941557 - src:maxima-sage
Thanks for providing the solution for the problem!
Best,
Tobias
On 10/29/19 2:24 PM, Norbert Preining wrote:
> reassign 941557 src:gri
> tags 941557 + patch
> retitle 941557 texi file need @documentencoding
> thanks
>
> With texinfo 6.7 finally the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 28 Oct 2019 19:48:29 +0100
Source: maxima-sage
Architecture: source
Version: 5.42.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Tobias Hansen
Closes: 943119
Changes:
maxima-sage
Control: reassign 941557 src:texinfo 6.7.0.dfsg.2-5
Control: affects 941557 + src:gri src:maxima-sage
Control: retitle 941557 texinfo: Malformed UTF-8 character in ParserNonXS.pm
This is probably a bug in texinfo, since both the program giving the error
(makeinfo) and the file it is complaining
Control: reassign 941557 src:texinfo 6.7.0.dfsg.2-5
Control: affects 941557 + src:gri src:maxima-sage
Control: retitle 941557 texinfo: Malformed UTF-8 character in ParserNonXS.pm
This is probably a bug in texinfo, since both the program giving the error
(makeinfo) and the file it is complaining
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 28 Oct 2019 20:11:38 +0100
Source: libzn-poly
Architecture: source
Version: 0.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Tobias Hansen
Closes: 943102
Changes:
libzn-poly (0.9.1
Hi Thierry,
thanks for the bug report. The relevant part of the log is this:
Success: 40 tests failed, up to 65 failures are tolerated
Error: critical test failures (e.g. timeout, segfault, etc.)
There is a segfault in
sage -t --long src/sage/calculus/riemann.pyx # Killed due to segmentation
Hi Thierry,
thanks for the bug report. The relevant part of the log is this:
Success: 40 tests failed, up to 65 failures are tolerated
Error: critical test failures (e.g. timeout, segfault, etc.)
There is a segfault in
sage -t --long src/sage/calculus/riemann.pyx # Killed due to segmentation
We already have sage 8.9 with Python 3 in Debian unstable. It is not migrating
to testing due to various crashes on i386, mipls64el and ppc64el but on amd64
it should work fine.
Best,
Tobias
On 10/15/19 10:50 AM, Dima Pasechnik wrote:
> This is a Debian-specific problem, I think they're
Hi,
thanks for the bug report. sagenb was not and as far as I know will not be
ported to Python 3. It was replaced by the Jupyter notebook. "sage -notebook"
leads me to a website informing about this and providing links to the Jupyter
as well as the old notebook. Running notebook() in sage
101 - 200 of 2885 matches
Mail list logo
