On 5/8/23 21:22, Paul Gevers wrote:
Hi Tobias,
On Sat, 6 May 2023 10:24:41 + Tobias Hansen wrote:
Note that we could also just remove python3-sage and the autopkgtest.
I assume you mean python3-brial here.
Yes indeed.
Nothing in Debian depends on it
Not true (and it's too
for this:
https://wiki.debian.org/Javascript/Policy
This little package is basically holding sagemath and others hostage. It is the
reason we have sagemath 9.5 in bookworm instead of 9.7 or 9.8. See #1010735.
Best,
Tobias
On Sat, 21 Apr 2018 10:55:29 +0200 Tobias Hansen wrote:
Source: ipywidgets
On 5/2/23 14:20, plugwash wrote:
I've prepared a NMU, and intend to open a pre-approval
request with the release team. If you have any objections
to the NMU please tell me ASAP (I do not intend to upload
it until I receive a response from the release team, if you
would preffer to make the
Dear Jorge,
thanks for the bug report. I googled the error that you got and it seems a lot
of xfce users had similar problems over the years (unrelated to sagemath).
Maybe xfce trips over the space in the command? What happens if you change the
line
Exec=sage --notebook=jupyter
to
On 2/6/23 23:23, Adrian Bunk wrote:
> I can make a 0-day NMU if you don't want to upload giac.
>
> That's not a nice thing to do, but given the freeze deadline it's pretty
> urgent.
>
> cu
> Adrian
That would be great, thanks! It's team maintained, I don't think anyone will be
upset about it.
Control: block -1 by 1030687
I applied the patches and confirmed that the package builds now. I can upload
it once giac is fixed.
Hi Rogo,
awesome, that helps a lot! Thanks for figuring all this out. I had already
started determining which patches need to be applied, but wasn't finished yet.
Could you please file a bug against giac to get the uchar issue fixed?
Best,
Tobias
Control: retitle -1 "FTBFS with setuptools >= 64"
Control: block 1028345 by -1
Control: block 1013399 by -1
Control: block 1022254 by -1
Control: block 1022278 by -1
Control: block 1028433 by -1
Control: block 1025874 by -1
Just to clarify that the issue is simply that I can't build sagemath due
On 12/23/22 12:56, Nilesh Patra wrote:
> On Sat, 10 Dec 2022 18:07:53 +0530 Nilesh Patra wrote:
>> On Mon, 28 Nov 2022 21:05:07 +0000 Tobias Hansen wrote:
>>> On 11/27/22 19:24, Nilesh Patra wrote:
>>>> On Sun, Nov 27, 2022 at 05:35:17PM +, Tobias Hansen
On 11/27/22 19:24, Nilesh Patra wrote:
> On Sun, Nov 27, 2022 at 05:35:17PM +0000, Tobias Hansen wrote:
>> On 11/27/22 06:37, Nilesh Patra wrote:
>>> Tobias, since this is done, would you consider to check sagemath now and
>>> get the ball rolling? :-)
>> Hi
On 11/27/22 06:37, Nilesh Patra wrote:
> Tobias, since this is done, would you consider to check sagemath now and get
> the ball rolling? :-)
Hi,
I actually tried building with the new pari and gap versions a while ago (using
sagemath 9.5 with upstream patches for the new pari and gap
Thanks! I will apply the patch once the pari version with the other fixes is
uploaded.
Best wishes,
Tobias
On 10/26/22 10:55, Bill Allombert wrote:
> Also I consider the error message change
> - PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC
> (1 elts)
> +
Hi Ileana,
are you aware of the bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020436
Bill posted a suggestion how to fix this test there yesterday.
Best wishes,
Tobias
On 10/19/22 14:44, Ileana Dumitrescu wrote:
> Hi Julien,
>
> I applied pari.patch to fix the compile issues with new
I tried rebuilding with this patch from sagemath:
|diff --git a/src/pari.cc b/src/pari.cc index 76ce8e1..50d08ab 100644 ---
a/src/pari.cc +++ b/src/pari.cc @@ -40,6 +40,13 @@ using namespace std; #ifdef
HAVE_LIBPARI +// Anyarg disappeared from PARI 2.15.0 +#ifdef __cplusplus +#
define ANYARG
Control: block -1 by 1020436 1020456
Before sagemath can be fixed, cypari2 and giac have to be built against pari
2.15.
On 10/13/22 19:08, Paul Gevers wrote:
> Control: severity -1 serious
>
> Hi,
>
> On Fri, 23 Sep 2022 15:55:41 +0200 Bill Allombert wrote:
>> Please update sagemath so that
Hi,
not all tests are expected to pass in sagemath's test suite.
The issue is always described at the end:
Success: 62 tests failed, up to 100 failures are tolerated
Error: critical test failures (e.g. timeout, segfault, etc.)
And in the overview above that, it indicates a segfault:
Hi,
there is a Debian package fonts-fork-awesome. Isn't that what you need? (ITP
bug is 910256)
Best,
Tobias
On Tue, 26 Apr 2022 17:20:02 +0200 Roland Mas wrote:
>
> - fortawesome-fontawesome-free (see my other mail: no source available,
> and I don't know what to do; split the part of
Source: sagemath
Version: 9.5-4
Severity: normal
Control: block -1 by 950598
Control: block -1 by 896460
The need for ipywidgets >= 7 is getting even bigger in sagemath 9.6.
Sagemath now depends on jupyter-sphinx, see
https://trac.sagemath.org/ticket/33507
jupyter-sphinx is broken in Debian
Package: ftp.debian.org
Severity: normal
Please remove higan from unstable. It is superseded by ares, which I packaged
to replace higan. higan still exists as a slightly different version of the
same program, but ares is more user friendly and more actively maintained.
Thanks,
Tobias
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Tobias Hansen
Severity: wishlist
* Package name: python-lrcalc
Version : 2.1
Upstream Author : Anders S. Buch
* URL : http://www.math.rutgers.edu/~asbuch/lrcalc/
* License : GPL-3+
Programming
Package: ftp.debian.org
Severity: normal
Hi,
please remove the python3-sage package on armhf and mips64el from unstable.
They are no longer allowed in source as their builds were constantly failing
for a long time (#920147, #1004872).
Best wishes,
Tobias
Package: libglu1-mesa-dev
Version: 9.0.2-1
Severity: serious
Control: block 1008372 by -1
Hi,
recently sludge started to FTBFS with the following error, see #1008372:
Package 'opengl', required by 'glu', not found
I believe this is because glu.pc now depends on opengl.pc which means that
Hi,
this is not a regression, as the armhf and mips64el tests never passed, see
#1004872 and #920147. There was a bug in the package that caused the tests not
to be run when building with python 3.10, so the armhf and mips64el package
builds succeeded. The packages for these architectures
Source: myst-parser
Version: 0.16.1-1
Severity: normal
Hi,
myst-parser is not migrating to testing because of a failing autopkgtest on
i386 and armhf, see below.
This is also blocking testing migration of other packages such as primecountpy
and sagemath.
Best wishes,
Tobias
Source: pynac
Version: 0.7.29-2
Severity: normal
Hi Julien,
pynac was merged into sagemath 9.5, see https://trac.sagemath.org/ticket/32386
Since pynac has no other use than the one in sage (according to that ticket) I
suggest that you request removal of pynac from Debian unstable.
Best wishes,
Package: sagemath
Version: 9.0-1
Severity: normal
Control: tags -1 + ftbfs
We are getting test timeouts on armhf since sagemath 9.0-1. The exact spots
where it happens have changed over time, one that stayed the whole time is in
src/sage/modular/modform/constructor.py. From there one can see
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Tobias Hansen
Severity: wishlist
* Package name: primecountpy
Version : 0.1.0
Upstream Author : Dima Pasechnik
* URL : https://github.com/dimpase/primecountpy
* License : GPL
Programming Lang
>
> If it is ok, I can put an ITP.
>
> Best wishes,
> Jerome
>
> On 08/01/2022 12:14, Tobias Hansen wrote:
>> Hi,
>>
>> we need to package primecount and primecountpy for sagemath 9.5. Jerome, I
>> saw that you are already maintaining primesieve by t
Package: wnpp
Owner: Tobias Hansen
Severity: wishlist
* Package name: ares
Version : 126
Upstream Author : Near et al
* URL : https://ares-emulator.github.io/
* License : ISC
Programming Lang: C++
Description : Accurate multi-system emulator
ares
On 12/11/21 22:22, Jochen Sprickerhof wrote:
> Package: ecl
> Version: 21.2.1+ds-1
> Severity: critical
> X-Debbugs-Cc: jspri...@debian.org
>
> Hi,
>
> according to policy:
>
> "The run-time shared library must be placed in a package whose name
> changes whenever the SONAME of the shared
Hi,
we need to package primecount and primecountpy for sagemath 9.5. Jerome, I saw
that you are already maintaining primesieve by the same upstream. Are you
interested in packaging these two or should I take care of it?
Best wishes,
Tobias
On Sat, 08 Jan 2022 06:35:05 + Preetham Gujjula
Version: 9.4-1
Hi,
memory-allocator passed NEW now.
Best,
Tobias
On 12/24/21 10:33 PM, Alexandre Lymberopoulos wrote:
> Hi, Tobias.
>
> Thanks for the prompt elucidation.
>
> Best, Alexandre
>
> On December 24, 2021 6:17:16 PM GMT-03:00, Tobias Hansen
> wrote:
>
Hi,
memory-allocator is in NEW (https://ftp-master.debian.org/new.html) since two
weeks and waiting to be approved for inclusion in Debian. I uploaded sagemath
9.4 after memory-allocator but it passed NEW faster.
Best,
Tobias
On 12/24/21 9:45 PM, Alexandre Lymberopoulos wrote:
> Package:
Source: linbox
Version: 1.7.0-1
Severity: normal
Hi,
while building sagemath I noticed that linbox includes fplll.h in
algorithms/lattice.h and algorithms/short-vector.h. Hence I think liblinbox-dev
should depend on libfplll-dev.
Best,
Tobias
Package: singular
Version: 1:4.2.1-p2+ds-5
Severity: normal
Hi Jerome,
I noticed some sagemath doctests are failing because sagemath cannot find
singular.info. It uses the libsingular function feGetResource() to determine
the location of the file. You can see in resources/feResource.cc that it
Hi Cord,
I am also in favor of the creation of this list. I think we could then close
down debian-science-sagem...@alioth-lists.debian.net and move these discussions
to debian-math.
Best,
Tobias
On Sat, 13 Nov 2021 16:45:48 +0530 "Nilesh Patra" wrote:
> Dear list masters,
>
> Since a few
On 12/13/21 4:30 PM, Dirk Eddelbuettel wrote:
> Hi Alexandre,
>
> On 13 December 2021 at 09:08, Alexandre Lymberopoulos wrote:
> | Hi there, Dirk!
> |
> | I see that, libgslblasc0 is upgradable to version 2.7.1+dfsg-3 here, but
> | the upgrade available version of libgsl25 (2.6+dfsg-2 ->
Source: sphinx
Version: 4.3.1-1
Severity: normal
Hi,
sagemath uses a custom sphinx build where some of the search.html files load
searchindex.js like this:
This causes dh_sphinxdoc to throw an error:
dh_sphinxdoc: error: */search.html does not load searchindex.js
This was already
Source: lcalc
Version: 2.0.4-1
Severity: normal
Hi Julien,
I realized that there are some failing sagemath tests where lcalc claims that
-e is an invalid option. After some digging I found that this flag only exists
when lcalc is built against pari:
Package: wnpp
Owner: Tobias Hansen
Severity: wishlist
* Package name: memory-allocator
Version : 0.1.2
Upstream Author : The Sage Development Team
* URL : https://github.com/sagemath/memory_allocator
* License : GPL-3+
Programming Lang: Python
Description
Source: matplotlib
Version: 3.5.0-2
Severity: normal
Tags: patch fixed-upstream
Control: forwarded -1 https://github.com/matplotlib/matplotlib/issues/21683
Hi,
I am in the process of updateting sagemath and have problems building the
documentation because of this bug. Please apply this upstream
Hi Jerome,
any chance we could get an update of singular to 4.2.1.p0 in experimental? I
tried to do it myself once but the package has many patches and it was
difficult to get everything right.
Best,
Tobias
Source: sagemath
Version: 9.2-2
Severity: serious
Control: block -1 by 992003
Control: block 986527 by -1
Control: block 993149 by -1
I started updating sagemath to version 9.4, which is the first version that
supports pari 2.13 (which is already in Debian and causes a large part of the
failing
I started updating sagemath to version 9.4, which is the first version that
supports pari 2.13 (which is already in Debian and causes a large part of the
failing doctests). I got stuck for now because we need an update of singular
(see #992003).
Best,
Tobias
On 8/27/21 7:37 PM, Paul Gevers
Hi,
yes, this is probably because sagemath 9.2 uses threejs 117 while in Debian we
are using / trying to use the Debian package three.js which is at version 111.
Replacing js stuff with Debian packages is always fiddly...
Best,
Tobias
On 8/25/21 9:56 PM, Balbir Thomas wrote:
> Package:
Source: singular
Version: 1:4.1.2-p1+ds-2
Severity: wishlist
Hi Jerome,
I started packaging sagemath 9.4 and they are using singular 4.2.0p3 at the
moment. It seems tricky to get it to work with anything else than this version.
It would be great if we had it in experimental.
Best wishes,
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,
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
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 + 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
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: 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
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:
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
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,
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
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
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
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,
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
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
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
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
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: 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
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,
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
I'm almost ready to upload sagemath 8.8. If you agree I could also just revert
commit f5187d87 of sagemath-database-conway-polynomialsand upload.
Best,
Tobias
On 9/1/19 11:45 AM, Tobias Hansen wrote:
> Package: src:sagemath-database-conway-polynomials
> Version: 0.5-6
> Severity:
Package: src:sagemath-database-conway-polynomials
Version: 0.5-6
Severity: important
Hi Julien,
I'm currently updating sagemath to version 8.8 and since version 0.5-5
sagemath-database-conway-polynomials is pickled with Python 3 and is not
compatible with Python 2 sagemath. Could you please
On 7/19/19 2:19 AM, Julien Puydt wrote:
> Hi,
>
> Le 18/07/2019 à 21:55, Tobias Hansen a écrit :
>> On 7/18/19 3:17 PM, Julien Puydt wrote:
>>> Hi,
>>>
>>> Le 18/07/2019 à 20:12, Tobias Hansen a écrit :
>>>> I pushed it now to https://sa
On 7/18/19 3:17 PM, Julien Puydt wrote:
> Hi,
>
> Le 18/07/2019 à 20:12, Tobias Hansen a écrit :
>> I pushed it now to https://salsa.debian.org/science-team/pplpy/
>>
>> Feel free to work on / upload it.
> Excellent!
>
> I worked on it a little.
>
> B
Hi Julien,
I pushed it now to https://salsa.debian.org/science-team/pplpy/
Feel free to work on / upload it.
Thanks!
Tobias
On 7/18/19 10:27 AM, Julien Puydt wrote:
> Hi,
>
> how is the packaging of pplpy going?
>
> I wanted to lend a hand, but didn't find 'pplpy' on salsa.
>
> Cheers,
>
> JP
Hi,
yes, to run doctests one needs to set SAGE_SRC and SAGE_PKGS. From sagemath's
README.Debian:
One can run the tests using the installed sage packages. First, get the source
code for this package (`apt-get source sagemath`), and make sure the Debian
patches are applied. Then, from the 'sage'
1 - 100 of 531 matches
Mail list logo
