Bug#881216: sagemath: Not using standard LaTeX fonts with plots using text()

Hi Jaimos, you can force use of the latex fonts by passing typeset="latex" as a parameter to any one of the three functions plot(), text() or show() that you're using. The documentation for sage.plot.graphics.show() says: - ``typeset`` -- (default: ``"default"``) string. The type of

Bug#892622: singular: on mips64el, crashes 50% of the time when ASLR is enabled (the default)

Package: singular Version: 1:4.1.0-p3+ds-2+b2 Severity: important Control: affects -1 sagemath Dear Maintainer, Singular on mips64el crashes 50% of the time when ASLR is enabled (the default). If one disables it (by using `setarch $(arch) -R`) then the segfaults go away. This affects sagemath,

Accepted sagemath 8.1-4 (source) into unstable

sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr Architecture: source Version: 8.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org> Changed-By: Ximin Luo <infini...@debian.org> Description: sagemath -

Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

ckages/cysignals_gdb/cysignals-CSI-helper.py but that is a Debian-specific innovation by the package maintainer that is slightly misleading; the file is just meant to be read into gdb rather than imported in a python program. Matthias Klose: > On 12.02.2018 15:41, Ximin Luo wrote: >>

Accepted gf2x 1.2-4 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Ximin Luo <infini...@debian.org> Description: libgf2x-dev - Routines for fast arithmetic in GF(2)[x] (development files) libgf2x1 - Routines for fast arithmetic in GF(2)[x] Closes: 890254 Changes: gf2x (1.2-4) unstable; urgency=medium . * Team upload.

Accepted gf2x 1.2-3 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Ximin Luo <infini...@debian.org> Description: libgf2x-dev - Routines for fast arithmetic in GF(2)[x] (development files) libgf2x1 - Routines for fast arithmetic in GF(2)[x] Changes: gf2x (1.2-3) unstable; urgency=medium . * Team upload. * Actuall

Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

Understood, but the entirety of sagemath is python2 at the moment and doesn't support python3 (upstream is working on it). What's the timeframe for removal of gdb-python2 and will there be a gdb-python3 alternative? X Matthias Klose: > Package: src:sagemath > Version: 8.2-3 > Severity:

Bug#890254: control

Control: fixed -1 1.2-3 Already fixed there, version in stretch still affected. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Ximin Luo: > Ximin Luo: >> Julien Puydt: >>> Le 19/10/2017 à 22:24, Ximin Luo a écrit : >>> >>>> I fixed things in git by removing MAKEFLAGS and rewriting d/rules to do >>>> the previous stuff in a cleaner way. I've rebuilt all of the reverse &g

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Ximin Luo: > Julien Puydt: >> Le 19/10/2017 à 22:24, Ximin Luo a écrit : >> >>> I fixed things in git by removing MAKEFLAGS and rewriting d/rules to do the >>> previous stuff in a cleaner way. I've rebuilt all of the reverse >>> dependencies () and they

Bug#849150: sagemath: FTBFS on arm64 and ppc64el: cannot allocate memory building docs

Control: notfixed -1 8.0-5 Control: reopen -1 Control: severity -1 minor You're right. I knew that we split the docbuild away (I did that, even) but I thought that the tests passing indicated that the bug was fixed. However I tried a full build on another ppc64el machine just now, and it seems

Bug#881218: sagemath: notebook() Worksheet Process Users not working

On Wed, 8 Nov 2017 14:35:11 -0700 Jaimos Skriletz wrote: > Package: sagemath > Version: 7.4-9 > Severity: normal > > Dear Maintainer, > > In upgrading to stretch from jessie I am trying to switch to using the > Debian package for sagemath from using the packages from

Bug#881236: flint-arb: tests fail on amd64 and i386

Control: reassign -1 src:flint Control: retitle -1 flint: omits __volatile__ in assembly division, causing faulty optimisations Control: affects -1 src:flint-arb The bug is in flint not flint-arb, see: https://gmplib.org/list-archives/gmp-bugs/2017-October/004231.html

Bug#880241: sagenb-export: FTBFS: Test failures

Control: reassign -1 src:testpath Control: retitle -1 testpath does not install .egg-info or .dist-info, making it invisible to pip Control: affects -1 sagenb-export The sagenb-export FTBFS is caused by the python "testpath" module not installing a .egg-info file (or .dist-info directory) which

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Julien Puydt: > Le 19/10/2017 à 22:24, Ximin Luo a écrit : > >> I fixed things in git by removing MAKEFLAGS and rewriting d/rules to do the >> previous stuff in a cleaner way. I've rebuilt all of the reverse >> dependencies () and they all succeeded including tests. S

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Ximin Luo: > [..] > > I fixed things in git by removing MAKEFLAGS and rewriting d/rules to do the > previous stuff in a cleaner way. I've rebuilt all of the reverse dependencies > () and they all succeeded including tests. So I think we're good to go ahead > with the tr

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Julien Puydt: > > > Le 01/09/2017 à 00:03, Ximin Luo a écrit : >> Thanks for that. I forced the rebuild to continue by skipping the flint >> tests with DEB_BUILD_OPTIONS=nocheck sbuild --profiles=nocheck , and am >> pleased to report that singular and p

Bug#875611: sagenb: ruby-compass obsolete and now broken

Control: tags -1 + pending On Tue, 12 Sep 2017 18:04:56 +0200 Jonas Smedegaard wrote: > [..]> > Attached is a patch to make Sagenb use sassc with separately maintained > stylesheets. It needs to wait until the stylesheets have been approved, > though: Is in NEW queue now: >

Bug#875465: sagemath: FTBFS on arm64: partitions doctests fail

Control: severity -1 important The previous build success was an accident, I raised the ignore-test-failures threshold too high. These combinat tests that you mention, also failed in the "successful build". Further, that build did not get a chance to migrate to Debian testing, so it can

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Julien Puydt: > Hi, > >> [..] > > I could reproduce the matter, asked upstream if it was known, and since > it wasn't: > https://github.com/wbhart/flint2/issues/372 > Thanks for that. I forced the rebuild to continue by skipping the flint tests with DEB_BUILD_OPTIONS=nocheck sbuild

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Ximin Luo: > Julien Puydt: >> [..] >> >> I still pushed this work-in-progress, as it should be good enought for >> some tests already. >> > > I will have a go at testing it tomorrow/soon. Thanks! > eclib, giac, linbox succeeded but flint fails: [..

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Ximin Luo: > Julien Puydt: >> Hi, >> >> Le 29/08/2017 à 14:25, Tobias Hansen a écrit : >>> Now is a good time for the NTL transition. Julien, could you update the >>> package to 10.3.0? Then we can test-build the reverse dependencies and >>> ask f

Bug#864831: [Debian-science-sagemath] NTL update to 10.3.0

Julien Puydt: > Hi, > > Le 29/08/2017 à 14:25, Tobias Hansen a écrit : >> Now is a good time for the NTL transition. Julien, could you update the >> package to 10.3.0? Then we can test-build the reverse dependencies and >> ask for a transition. > > Indeed there was a soname version bump from 27

Bug#872259: sagemath: FTBFS with Sphinx 1.6: TypeError: frompickle() takes exactly 3 arguments (4 given)

Control: tags -1 + upstream Control: forwarded -1 https://trac.sagemath.org/ticket/23023 -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#872711: ntl: Please link against gf2x

Source: ntl Version: 9.9.1-3 Severity: wishlist Dear Maintainer, NTL has the ability to link against the gf2x library, but the current version in Debian does not seem to do so: Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libgmp10, libstdc++6 (>= 5.2) Sage uses NTL with gf2x, as follows:

Bug#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

Ximin Luo: > -#869778 > > Ximin Luo: >> [..] >> >> Hi, I see that libgsl23 was uploaded but who is taking care of the library >> transition? It seems that this process was not followed: >> https://wiki.debian.org/Teams/ReleaseTeam/Transitions >> &

Bug#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

-#869778 Ximin Luo: > [..] > > Hi, I see that libgsl23 was uploaded but who is taking care of the library > transition? It seems that this process was not followed: > https://wiki.debian.org/Teams/ReleaseTeam/Transitions > > The transition tracker detected the li

Bug#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

Control: block 870688 by 869778 Control: affects 869778 + sagemath Ximin Luo: > Tobias Hansen: >> [..] >> >> The accidental upload of cysignals 1.6.5 to unstable is now a RC bug >> (#870688). Not sure if we should fix it by downgrading cysignals, >> patching sage

Bug#870698: [Debian-science-sagemath] Possible fix for fplll/fpylll issue with default strategy path

Ximin Luo: > Ximin Luo: >> Julien Puydt: >>> Hi, >>> >>> I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which >>> would fix the recently reported issue with fpylll : I rewrote the patch >>> for the default strategies p

Bug#870698: [Debian-science-sagemath] Possible fix for fplll/fpylll issue with default strategy path

Ximin Luo: > Julien Puydt: >> Hi, >> >> I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which >> would fix the recently reported issue with fpylll : I rewrote the patch >> for the default strategies path changes. >> >> I'm a bit

Bug#870698: [Debian-science-sagemath] Possible fix for fplll/fpylll issue with default strategy path

Julien Puydt: > Hi, > > I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which > would fix the recently reported issue with fpylll : I rewrote the patch > for the default strategies path changes. > > I'm a bit at loss on how to check if that really fixes anything : I > tried to

Bug#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

Tobias Hansen: > [..]> > > Hi, > > good work on finding the fpylll issue! Now the main holdup for sage 8.0 > is still cypari2 being stuck in NEW. I wrote on June 21 to > ftpmas...@debian.org and August 2 directly to the ftpmaster who helped > us get sagemath through NEW in time for stretch.

Bug#849150: [Debian-science-sagemath] patch proposal

whoops, I forgot to CC Frédéric, the Debian BTS does not do this automatically. :( see my message below: Ximin Luo: > On Tue, 11 Jul 2017 13:24:02 +0200 Frédéric Bonnard > <fre...@linux.vnet.ibm.com> wrote: >> Tags: patch >> User: debian-powe...@lists.debian.

Bug#849150: patch proposal

On Tue, 11 Jul 2017 13:24:02 +0200 Frédéric Bonnard wrote: > Tags: patch > User: debian-powe...@lists.debian.org > Usertags: ppc64el > > -- > > Hi, > it just seems that there's too many space taken by different libraries > in the static TLS space. I contacted some

Bug#855078: giac: FTBFS: [algo.pdf] Error 139 (Segmentation fault)

Edmund Grimley Evans: >> http://xcas.e.ujf-grenoble.fr/XCAS/viewtopic.php?p=8963#p8963 >> >> Do you have any suggestions on how to move forward? The easiest option is >> just to give the test two possible things to diff against, but this buries >> the issue and does not really solve it. > >

Bug#855078: giac: FTBFS: [algo.pdf] Error 139 (Segmentation fault)

On Thu, 29 Jun 2017 20:40:26 +0100 Edmund Grimley Evans wrote: > This robopatch seems to fix the problem on arm64 with 48-bit addresses: > > perl -i -pe 's/longlong/ulonglong/g if /\(\s*longlong.*(<<|>>)/ && > !/gen\(longlong/;' src/*.cc > > The idea is to

Bug#868347: sagemath-common: /usr/share/sagemath/bin/sage-native-execute: firefox:elinks:w3m: not found

Control: severity -1 normal Control: tags -1 moreinfo Rogério Brito wrote: > Package: sagemath-common > Version: 7.6-2 > Severity: important > File: /usr/share/sagemath/bin/sage-native-execute > > > Hi, > > It seems that sage-native-execute doesn't respect the way that the

Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'

Control: tags -1 + pending upstream Control: forwarded -1 https://trac.sagemath.org/ticket/23364 Ximin Luo: > [..] > > Could you also explain why exactly dh_sphinxdoc checks for these - what > functionality is broken because these paths don't exist? I don't see that > anyone n

Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'

Dmitry Shachnev: > Hi Ximin! > > On Tue, Jul 04, 2017 at 07:35:00AM +0000, Ximin Luo wrote: >> I fixed our other issue in git and now I'm seeing these sphinxdoc errors: >> >> [..] >> make[1]: Entering directory '/home/infinity0/var/lib/sage/sagemath' >> dh_s

Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'

Tobias Hansen wrote: > On 06/28/2017 04:03 PM, Dmitry Shachnev wrote: > > Hi Tobias, and thanks for the quick response! > > > > On Wed, Jun 28, 2017 at 02:44:23PM +0100, Tobias Hansen wrote: > >> Hi Dmitry, > >> > >> would it be an option to upload sphinx 1.5 to unstable together with > >>

Bug#866508: sagemath: sage fail at starting with: ImportError: No module named 'sage'

Package: sagemath Followup-For: Bug #866508 Control: tags -1 + moreinfo unreproducible Control: severity -1 important Sorry, I can't reproduce this, even from a clean sid schroot. What does it say when you run each of the following: $ dpkg -S /usr/lib/python2.7/dist-packages/sage/__init__.py $

Bug#864831: ntl: New upstream version available

Source: ntl Version: 9.9.1-3 Severity: wishlist Dear Maintainer, There's a new upstream version available, 10.3.0. http://shoup.net/ntl/doc/tour-changes.html X -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,

Bug#863919: Acknowledgement (sympow segfaults with basic input)

th revisiting if you have time. X Jerome BENOIT: > Hello Ximin, thanks for your report. > > Do you meant that the issue happens on Stretch ? > I ask because I thought it happens on experimental and because the CI test > does not currently fail. > > Thanks, > Jerome >

Bug#863919: Acknowledgement (sympow segfaults with basic input)

BTW the stretch release date is soon: https://lists.debian.org/debian-devel-announce/2017/05/msg2.html The deadline for fixing this is June 9th and you'll need to file an unblock request, asking them to reduce the default migration time of 10 days. I'm not sure if this bug warrants raising

Bug#863919: sympow segfaults with basic input

Package: sympow Version: 1.023-8 Severity: important Dear Maintainer, sympow now segfaults with basic input, possibly due to libc upgrades - I didn't see these before when we were testing with Sage 7.4. The failure is definitely independent of Sage: $ gdb -q sympow Reading symbols from

Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

Control: reassign -1 r-base Control: forcemerge 861333 -1 Hey Andreas, I was told that this is a r-base issue, not an issue with r-cran-randomfields, and it is already being discussed in 861333. Ximin Andreas Tille: > tags 861684 sid > thanks > > I'm tagging this sid since it is not relevant

Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

Package: r-cran-randomfields Version: 3.1.36-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, This package FTBFS against r-base 3.4.0-1 which was uploaded to unstable recently. [..] make[1]: Leaving directory '/<>/src' make[1]:

Bug#855078: giac: FTBFS: [algo.pdf] Error 139 (Segmentation fault)

On Mon, 13 Feb 2017 16:12:14 -0500 "Aaron M. Ucko" wrote: > [..] > > xvfb-run ../../src/icas "algo.tex" > ./algo.tex:4: Warning: Command not found: \textheight > /usr/share/hevea/hyperref.hva:65: Warning: Ignoring option: 'pdftex' > /usr/share/hevea/hyperref.hva:65:

Bug#849150: sagemath: FTBFS on arm64 and ppc64el: cannot allocate memory building docs

Aaron M. Ucko: > Ximin Luo <infini...@debian.org> writes: > >> The error occurs right when the docbuild starts, before it actually >> attempts to build anything, so my guess is that it would also occur >> when starting the normal Sage CLI. So I don't think

Bug#849152: sagemath: FTBFS on i386: many tests fail

On Thu, 22 Dec 2016 18:59:24 -0500 "Aaron M. Ucko" wrote: > Source: sagemath > Version: 7.4-3 > Severity: important > Justification: fails to build from source > > The i386 build of sagemath failed with many test suite errors > (including some outright crashes), as detailed at >

Bug#849150: sagemath: FTBFS on arm64 and ppc64el: cannot allocate memory building docs

Hi, this does not look like a simple out-of-memory, but a bug involving libgomp. A quick Google search of the error message shows that there was some issue involving libgomp, dlopen and GCC years ago, but it's unclear if this is issue here is related. The error occurs right when the docbuild

Bug#848246: [Debian-science-sagemath] Fwd: sagemath_7.4-1_amd64.changes is NEW

Control: retitle -1 Document SYMPOW_CACHEDIR better and automatically try to create it Jerome BENOIT: > Hello SymPow enthusiasts, > > On 17/12/16 15:46, Jerome BENOIT wrote: >>> It would be good if sympow could automatically create SYMPOW_CACHEDIR if it doesn't exist. Otherwise, I would

Bug#848131: Acknowledgement (libmpich.so.12: cannot open shared object file: No such file or directory)

Control: reassign -1 libtachyon-mpich-0 Control: affects -1 tachyon-bin-nox Control: affects -1 tachyon-bin-ogl Note that the problem occurs only when you install libtachyon-mpich-0. (For some reason, that is what sbuild chose to satisfy sage's "tachyon" dependency. Probably I should remove my

Bug#848131: libmpich.so.12: cannot open shared object file: No such file or directory

Package: tachyon-bin-nox Version: 0.99~b6+dsx-6 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, This package is missing either a direct or indirect dependency libmpich12: (unstable-amd64-sbuild)infinity0:/build/sagemath-fBCYuv/sagemath-7.4$ tachyon-nox

Bug#847172: sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128)

will wait for the upstreams to pick the solutions I proposed. In the meantime, I will work around this FTBFS by overriding LC_CTYPE specially for the tests. X Ximin Luo: > I think I narrowed it down, could you try the build again with > LC_CTYPE="C.UTF-8" and see how it works? >

Bug#847172: sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128)

I think I narrowed it down, could you try the build again with LC_CTYPE="C.UTF-8" and see how it works? X Chris Lamb: > Ximin Luo wrote: > >> I can't reproduce this, even when setting the locale to various non-UTF >> values > > Not sure why you were tr

Bug#847172: sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128)

Hi Chris, I can't reproduce this, even when setting the locale to various non-UTF values. How are you building this? X Chris Lamb: > Source: sagenb-export > Version: 2.0-1 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org >

Re: sagenb-export_2.0-1_amd64.changes REJECTED

Thorsten Alteholz: > > Hi, > > in case the license is GPL-3, your License block should not contain > "or (at your option) any later version.". This doesn't seem to match. > > Thorsten > Whoops, my bad. I've fixed this and uploaded again. X -- GPG: ed25519/56034877E1F87C35 GPG:

Bug#840621: python-sympy: please apply 01_undeffun_sage.patch from sagemath

Package: python-sympy Version: 1.0-2 Severity: normal Tags: upstream patch Dear Maintainer, Please apply 01_undeffun_sage.patch in the next upload. I have already done this in git in the pu/undeffun_sage branch [1], so you can just merge from this branch before your next upload. This patch is

Bug#840481: [Debian-science-sagemath] Bug#840481: singular-ui: segfault when piping to stdin

Control: tags -1 upstream Control: forwarded -1 https://www.singular.uni-kl.de:8005/trac/ticket/775 Ximin Luo: > Package: singular-ui > Version: 4.0.3-p3+ds-1 > Severity: important > > Dear Maintainer, > > Some extra Sagemath test cases are failing since we upgraded to

Bug#840481: singular-ui: segfault when piping to stdin

Package: singular-ui Version: 4.0.3-p3+ds-1 Severity: important Dear Maintainer, Some extra Sagemath test cases are failing since we upgraded to Singular 4; minimal test case: $ echo '12345*54321;' | Singular [ fails spectacularly ] but it works if you run `Singular` and type it in manually.

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

; sse and sse2 build on top of mmx. X Ximin Luo: > Package: fflas-ffpack > Version: 2.2.1-1 > Severity: important > > Dear Maintainer, > > fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen > from the output of `pkg-config --cflags

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

Package: fflas-ffpack Version: 2.2.1-1 Severity: important Dear Maintainer, fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen from the output of `pkg-config --cflags fflas-ffpack`. This unfortunately makes it crash on amd64 machines that don't support these

Bug#830206: libmpfi-dev: undefined symbol: mpfi_is_strictly_neg_default

Package: libmpfi-dev Version: 1.5.1+ds-4 Severity: normal Dear Maintainer, When trying to compile Sage 7.1 as described in https://wiki.debian.org/DebianScience/Sage https://anonscm.debian.org/cgit/debian-science/packages/sagemath.git/ Sage compiles successfully but the resulting binary