Bug#892139: Forwarded upstream

Hi, I forwarded the report upstream: https://github.com/JohnCremona/eclib/issues/36 So hopefully there will be a fixed version soon. Cheers, Snark on #debian-science

Bug#882655: bump

Hi, Le 11/04/2018 à 12:51, Paolo Greppi a écrit : > Hi, node-nanomatch >= 1.2.9 is required to update node-micromatch to 3.1.10: > https://salsa.debian.org/js-team/node-micromatch/wikis/home > > I have noticed there is a repo here: >

Bug#882655: Bug#882655: bump

Hi, Le 11/04/2018 à 12:51, Paolo Greppi a écrit : > Hi, node-nanomatch >= 1.2.9 is required to update node-micromatch to 3.1.10: > https://salsa.debian.org/js-team/node-micromatch/wikis/home > > I have noticed there is a repo here: >

Bug#882619: Bug#882619: bump

Hi, Le 11/04/2018 à 12:51, Paolo Greppi a écrit : > Hi, node-object.pick is required to update node-micromatch to 3.1.10: > https://salsa.debian.org/js-team/node-micromatch/wikis/home > > I have noticed there is a repo here: > https://anonscm.debian.org/git/pkg-javascript/node-object.pick.git >

Bug#894786: RFP: python-pytest-flake8 -- pytest plugin to check FLAKE8 requirements

Package: wnpp Severity: wishlist X-Debbugs-Cc: debian-pyt...@lists.debian.org * Package name: python-pytest-flake8 Version : 1.0.0 Upstream Author : Thorsten Lockert * URL : https://github.com/tholo/pytest-flake8 * License : BSD Programming Lang: Python

Bug#891351: Details

Hi, can you install scilab-cli to see if it works better? Snark on #debian-science

Bug#892018: Won't work without grunt!

Package: node-grunt-cli Version: 1.2.0-3 Severity: grave It is really depending on grunt -- but doesn't, so it's possible to install the package in a broken state. Snark on #debian-js

Bug#892052: Please add support for the flit build system

Package: dh-python Version: 2.20170125 Severity: wishlist The flit build system is for trivial packages, so it would be nice if pybuild could auto-detect its use and do things itself. I have had good results with the following code in d/rules for the terminado package: export

Bug#889515: Re: Re: Review of persepolis

Hi, Le 01/03/2018 à 01:24, Moein Alinaghian a écrit : > > I would be happy in case he makes it sometime in the next week. I am > patient :) And thanks again for the spending time helping me as well > as helping Debian. > My AM reviewed your package and found two things : - in d/control, the

Bug#891710: ITP: node-compare-versions -- Version string comparison for Node.js

Package: wnpp Severity: wishlist Owner: Julien Puydt <julien.pu...@laposte.net> X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-compare-versions Version : 3.1.0 Upstream Author : Ole Bjørn Michelsen <o...@michelsen.dk> * URL : https:

Bug#891729: ITP: node-tippex -- Erase comments and strings from JavaScript code for Node.js

Package: wnpp Severity: wishlist Owner: Julien Puydt <julien.pu...@laposte.net> X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-tippex Version : 3.0.0 Upstream Author : Rich Harris * URL : https://github.com/Rich-Harris/tippex#readme * L

Bug#885137: It's also a dep for rollup-plugin-terser

Hi, serialize-javascript is also a dep for rollup-plugin-terser, which is now needed for rollup. Embedding it in copy-webpack-plugin as it is small will not allow to share it, so perhaps it should still be pushed as a separate package? jpuydt on irc.debian.org

Bug#911367: New upstream is out

Package: node-acorn Version: 5.5.3+ds3-1 Severity: wishlist Hi, I need a more recent version of this package to update the node-buble package. Thanks, jpuydt on irc.debian.org

Bug#911366: New upstream is out

Package: node-acorn-jsx Version: 4.4.1-2 Severity: wishlist Hi, I need a more recent version of this package to update the node-buble package. Thanks, jpuydt on irc.debian.org

Bug#911365: New upstream is out

Package: node-acorn-dynamic-import Version: 3.0.0-1 Severity: wishlist Hi, I need a more recent version of this package to update the node-buble package. Thanks, jpuydt on irc.debian.org

Bug#911218: ITP: minetest-mod-mobs-animal -- Minetest module to add animals

Package: wnpp Severity: wishlist Owner: Julien Puydt * Package name: minetest-mod-mobs-animal Version : 20181016 Upstream Author : TenPlus1 * URL : https://notabug.org/TenPlus1/mobs_animal * License : Expat Programming Lang: lua Description : Minetest

Bug#911212: ITP: minetest-mod-mobs-redo -- Minetest module to add mobs programming interface

Package: wnpp Severity: wishlist Owner: Julien Puydt * Package name: minetest-mod-mobs-redo Version : 20181016 Upstream Author : TenPlus1 * URL : https://notabug.org/TenPlus1/mobs_redo * License : Expat Programming Lang: lua Description : Minetest

Bug#911442: ITP: minetest-mod-ethereal -- Minetest module to add a map generator enhancer

Package: wnpp Severity: wishlist Owner: Julien Puydt * Package name: minetest-mod-mobs-animal Version : 20181016 Upstream Author : TenPlus1 * URL : https://notabug.org/TenPlus1/mobs_animal * License : Expat Programming Lang: lua Description : Minetest

Bug#913492: ITP: minetestmapper -- map generator from minetest worlds

Package: wnpp Severity: wishlist * Package name: minetestmapper Version : 20180325 Upstream Author : Miroslav Bendik * URL : https://github.com/minetest/minetestmapper * License : BSD-2-clause Programming Lang: C++ Description : map generator from

Bug#913671: ITP: minetest-mod-basic-materials

Package: wnpp Severity: wishlist * Package name: minetest-mod-basic-materials Version : 20181109.2 Upstream Author : Vanessa Ezekowitz * URL : https://gitlab.com/VanessaE/basic_materials * License : LGPL-3, CC-BY-SA-4.0 Programming Lang: lua Description

Bug#913670: ITP: minetest-mod-currency -- Minetest mod providing shops and currency

Package: wnpp Severity: wishlist * Package name: minetest-mod-currency Version : 20181109 Upstream Author : Vanessa Ezekowitz * URL : https://gitlab.com/VanessaE/currency * License : LGPL-3, CC-BY-SA-4.0 Programming Lang: lua Description : Minetest mod

Bug#905379: Bug explanation

Hi, I hadn't launched anki since long and hence got stuck. Looking at the trace I see: self.focusProxy().installEventFilter(self) and an attribute error that NoneType has no installEventFilter, so it's quite clear what the problem is: self.focusProxy() returns None! That might mean that

Bug#907607: scilab-cli doesn't start

Hi, Le 21/09/2018 à 14:51, Sylvestre Ledru a écrit : Le 30/08/2018 à 09:07, Sylvestre Ledru a écrit : Package: scilab-cli Version: 6.0.1-5 Severity: important Hello scilab-cli is failing on startup. STR: $ sudo apt-get install scilab-cli $ scilab-cli commons module not found.

Bug#919971: node-rollup-pluginutils: autopkgtestsuite failure

Hi, I had not updated this package precisely because I couldn't get the autopkgtestsuite to run properly : https://github.com/rollup/rollup-pluginutils/issues/38 If you have a fix, that's a good news. I might have the time to have a look in two days ; if you're in a hurry, it's team

Bug#914476: flint-arb FTCBFS: ./configure needs to be told, about crossing

Hi, I pushed the proposed changes to salsa, and uploaded a new 2.15.1-2 to experimental. jpuydt on irc.debian.org

Bug#926180: New trouble

Hi, the trouble seems to be that when generating the documentation, it tries to run examples to generate picture, and doesn't find a graphic card (even a virtual one). I suggest to move the bug against libjogl2-java, as it might miss a depend on whatever is needed for correct operation.

Bug#923226: Compiling shader doesn't work - game doesn't work

Package: openarena Version: 0.8.8+dfsg-2 Severity: grave Hi, openarena doesn't work anymore because it doesn't manage to compile its shaders. jpuydt on irc.debian.org ioq3 1.36+u20181222.e5da13f~dfsg-1/Debian linux-x86_64 Jan 14 2019 SSE instruction set enabled - FS_Startup - We are

Bug#923226: Compiling shader doesn't work - game doesn't work

Hi, Le 07/03/2019 à 09:51, Simon McVittie a écrit : On Tue, 26 Feb 2019 at 07:51:27 +, Simon McVittie wrote: Does the opengl1 renderer work? (See /usr/share/doc/ioquake3/NEWS.Debian.gz) If not, does an older version of ioquake3 from snapshot.debian.org work? Please could you try this on

Bug#923226: Compiling shader doesn't work - game doesn't work

Le 07/03/2019 à 18:39, Simon McVittie a écrit : On Thu, 07 Mar 2019 at 13:30:57 +0100, Julien Puydt wrote: Just changing the ioquake3 binary package (which makes dpkg complain about ioquake3-server, but it's normal): 1.36+u20181017.09166ba~dfsg-2 works 1.36+u20181222.e5da13f~dfsg-1 fails

Bug#923226: Compiling shader doesn't work - game doesn't work

Hi, Le 07/03/2019 à 18:39, Simon McVittie a écrit : On Thu, 07 Mar 2019 at 13:30:57 +0100, Julien Puydt wrote: Just changing the ioquake3 binary package (which makes dpkg complain about ioquake3-server, but it's normal): 1.36+u20181017.09166ba~dfsg-2 works 1.36+u20181222.e5da13f~dfsg-1 fails

Bug#923226: Compiling shader doesn't work - game doesn't work

Hi, Le 08/03/2019 à 09:48, Simon McVittie a écrit : Please try the attached patch, also available at . If that works, I think it or something similar is going to be the best solution. Test binaries:

Bug#926180: scilab: FTBFS on all - New trouble

Hi, On 12/05/2019 11:46, Alexis Murzeau wrote: > I saw that there is a bugfix release 6.0.2 with many fixes [0]. I had started to package 6.0.2 on salsa already in february. I removed the patch about Linenum as that was supposed to have been reworked and fixed, and it now fails with : ocamlopt

Bug#927944: [Pkg-javascript-devel] Bug#927944: node-unicode-data: FTBFS with unicode-data >= 12.0.0

Hi, On 25/04/2019 10:55, Alastair McKinstry wrote: > Source: node-unicode-data > Version: 0~20181101+gitaddfb440-1 > Severity: serious > Justification: Policy 4.2 > > node-unicode-data FTBFS with unicode-data 12.0.0 and needs to be updated. > There is a newer version in NEW which is supposed

Bug#934915: node-es6-promise doesn't work anymore

Package: node-es6-promise Version: 4.2.8-4 Severity: grave The package is unusable as far as I can tell : it builds, but is giving the following error on loading (ie: require-ing it fails): /usr/lib/nodejs/es6-promise/dist/es6-promise.js:10 })(window, function() { ^ ReferenceError: window is

Bug#896460: Do you need help?

Hi, if you need help with packaging a newer ipywidgets, I can perhaps lend a hand? JP

Bug#934915: node-es6-promise doesn't work anymore

Hi, Le 19/08/2019 à 15:23, Pirate Praveen a écrit : > On 2019, ഓഗസ്റ്റ് 19 6:26:14 PM IST, Julien Puydt > wrote: >> Hi, >> >> Le 16/08/2019 à 18:49, Pirate Praveen a écrit : >>> Try removing target 'web' option. (On phone now). >> >> I removed th

Bug#933077: Clear solution?

). + + -- Julien Puydt Mon, 12 Aug 2019 09:10:30 +0200 + node-typescript (3.5.3-2) unstable; urgency=medium * Correct d/copyright (following upstream #11469). diff --git a/debian/links b/debian/links index 762a0b247..9e0a12fa9 100644 --- a/debian/links +++ b/debian/links @@ -1,2 +1,2 @@ usr/lib/nodejs

Bug#934915: node-es6-promise doesn't work anymore

Hi, Le 16/08/2019 à 18:49, Pirate Praveen a écrit : > Try removing target 'web' option. (On phone now). I removed that line: no better. And since then, a commit even broke the build ; I complained to the author, but don't try anything before it's cleaned up... JP

Bug#940299: RM: minetest-mod-torches -- RoM; obsolete and abandoned upstream

Package: ftp.debian.org The newer versions of the minetest game have better than what it provides It's abandoned upstream. This package has no rdeps. I'm the package maintainer (within the Debian Games Team), and I'm proposing to drop it off Debian unstable (and testing, with another bug

Bug#940300: RM: minetest-mod-torches -- RoM; obsolete and abandoned upstream

Package: release.debian.org User: release.debian@packages.debian.org Usertags: rm The newer versions of the minetest game have better than what it provides It's abandoned upstream. This package has no rdeps. I'm the package maintainer (within the Debian Games Team), and I'm proposing to

Bug#932965: Fix ES module exports in node-magic-string : what is left?

Hi, the original report was about shipping the files correctly and fixing the ES module exports. For the first part you already committed a fix, and for the later, I had a look and the end of dist/magic-string.es.js is: export { Bundle, SourceMap }; export default MagicString$1; //#

Bug#929848: How is the packaging of pplpy going?

Hi, how is the packaging of pplpy going? I wanted to lend a hand, but didn't find 'pplpy' on salsa. Cheers, JP

Bug#929848: How is the packaging of pplpy going?

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. But I don't understand the lines in d/rules where you put "export whatever=whatever" as

Bug#929848: How is the packaging of pplpy going?

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://salsa.debian.org/science-team/pplpy/ >>> >>> Feel free to w

Bug#932445: ITP: sagemath-database-cremona-ellcurve -- Database of elliptic curves over the rationals

Package: wnpp Severity: wishlist Owner: Julien Puydt * Package name: sagemath-database-cremona-ellcurve Version : 2016-10-17 Upstream Author : John Cremona * URL : https://github.com/JohnCremona/ecdata * License : Public domain Programming Lang: None

Bug#896218: Add the dep to a test

Hi, another way to break the circular dep is that the problem only appears when one tries to _use_ the module. Perhaps we can add an autopkgtest file to try to "import brial", with the depends declaring it needs sagemath? JP

Bug#930268: Making typescript run better

Hi, yes, I had to drop the patch https://salsa.debian.org/js-team/node-typescript/commit/5f0227be9710bff56f99d36741beb5e0f522b23b because it wasn't working correctly ; I don't remember exactly what the problem was. I'll try to see if I can come up with something better, but if you have a clue,

Bug#943697: RM: node-stringset -- RoM, abandoned upstream

Package: node-stringset Hi, I'm the maintainer of this package within the Debian Javascript Maintainer team. It's not used anymore, abandoned upstream, so I'd like to see it removed from unstable. Thanks! JP

Bug#943698: RM: node-es6-module-transpiler -- RoM; abandoned upstream

Package: ftp.debian.org I'm the maintainer of the package within the Debian Javascript Maintainer team. This package is of no use anymore, so I'd like to see it removed from unstable. That will probably allow the removal of a few other old packages down the line, hence more such bugs are to

Bug#943700: RM: node-simple-fmt -- RoM; abandoned upstream

Package: ftp.debian.org I'm the maintainer of this package within the Debian Javascript Maintainer Team. It's not used anymore in Debian and abandoned upstream, so I'd like to see it removed. Thanks, JP

Bug#942809: [Pkg-javascript-devel] Bug#942809: Bug#942809: Why embed ts-node in node-typescript?

Le mardi 22 octobre 2019 à 14:25 +0530, Pirate Praveen a écrit : > I don't think that is right characterization. NEW queue is not same > for all packages, javascript packages are treated differently from > other languages. ruby packages get cleared in days or maximum weeks. > Also ftp masters

Bug#942809: [Pkg-javascript-devel] Bug#942809: Why embed ts-node in node-typescript?

Le mardi 22 octobre 2019 à 10:01 +0200, Xavier a écrit : > Le Mardi, Octobre 22, 2019 09:10 CEST, Julien Puydt < > julien.pu...@laposte.net> a écrit: > > If you want to have ts-node, why not package it properly, with a > > RFP or > > ITP? > > > >

Bug#942809: Why embed ts-node in node-typescript?

If you want to have ts-node, why not package it properly, with a RFP or ITP? I don't see the point into packaging those together... JP

Bug#943526: [Pkg-javascript-devel] Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit : > Hi JS team, > > why did node-typescript have such link ? > > /usr/share/nodejs/tslib -> typescript/lib > > This creates this conflict. > Well, isn't node-typescript supposed to provide that lib? JP

Bug#943526: [Pkg-javascript-devel] Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

Le mardi 29 octobre 2019 à 12:45 +0100, Xavier a écrit : > Control: reassign -1 node-typescript > > Le 29/10/2019 à 08:29, Julien Puydt a écrit : > > Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit : > > > Hi JS team, > > > > > &

Bug#949974: Upstream?

Hi, isn't it an upstream issue? Cheers, JP

Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal

Package: ftp.debian.org Severity: normal X-Debbugs-CC: debian-pyt...@lists.debian.org The src:ipykernel-py2 package provides python-ipykernel, which is to be removed for the Python 2 removal transition. Notice that for most packages, a single src:foo package provides both python-foo and

Bug#615439: Closing as the problem doesn't appear anymore

Hi, I checked and couldn't reproduce the problem : it looks like everything is alright now. Cheers, JP

Bug#933739: Better link for the upstream report

Hi, my report was in fact a duplicate of: https://github.com/pypa/setuptools_scm/issues/246 So upstream is aware of the matter, has some kind of plan, but doesn't really move forward on it. JP

Bug#950450: libm4ri and libm4rie

Hi, indeed, the NEW queue wasn't processed in the same order as the uploads, so the first library it still in and the second already got through... Let's be patient. JP

Bug#951687: #951687 mawk vs gawk incompatibility

Le jeudi 20 février 2020 à 05:04 -0500, Thomas Dickey a écrit : > The referenced script uses "asort", which is a gawk extension (rather > than, for instance, being a POSIX feature). It's not part of BWK > (one-true-awk), either. > > According to the bug-reporting guidelines, that makes this a

Bug#952396: Strange pydist warning about cysignals package not being found

Package: python3-cysignals-pari Version: 1.10.2+ds-3 Hi, while building pplpy, I noticed the following warning: I: dh_python3 pydist:228: Cannot find package that provides cysignals. Please add package that provides it to Build-Depends or add "cysignals python3-cysignals" line to

Bug#943451: Is that bug really pplpy's problem?

Hi, it looks more like a doxygen 1.8.16 bug than a pplpy issue, isn't it? If that is so, then it should be marked as affecting pplpy, but assigned to doxygen. Thanks, JP

Bug#951687: mawk vs gawk incompatibility

Package: mawk Version: 1.3.4.20200120-2 Hi, I have a package where mawk can't be used instead of gawk ; here is the shell script with the problematic command : https://gitlab.com/freedroid/freedroid-src/-/blob/master/po/update-potfiles I see three outcomes to this report : - find there's a bug

Bug#948475: GP stuck when parisize is too high on armel and a few others

Package: pari-gp Version: 2.11.2-1 When starting with a big parisize on armel (and armhf, mipsel and powerpc, if I remember well), gp can get stuck on simple computations : parisize = 10, primelimit = 50, nbthreads = 4 ? isprime(293911884200387681576093) *** isprime: Warning: not

Bug#949023: Problems with Python 3.8

Package: sagemath Version: 8.9-3 I had problem getting brial's autopkgtest to run, and it turns out the problem comes from sagemath. With python 3.7, "import sage.misc.lazy_import" works. With python 3.8, it fails : the package isn't found. I have no clue why yet, but I'm going to investigate.

Bug#949023: Found the problem

Hi, I had a deeper look : the problematic packages are those which come with some cython-compiled code, as this is versioned. For example: lazy_import.cpython-37m-x86_64-linux-gnu.so which means that we should provide the Python 3.8 versions of those if we want it to pass. Cheers, JP

Bug#948212: Solution to the bug : one-liner change

Hi, I fixed the brial package which was the culprit for the missing symbols, and can confirm that what is needed is only : modify env.py so SAGE_SCRIPTS_DIR points to /usr/share/sagemath/bin after that, "from sage import *" works with Python 3.7. See #949023 for the case of Python 3.8. JP

Bug#949023: Correction: cpython 3.8

Hi, I realise I mention cython in my last message, but the file name says it's actually about cpython : probably we build something only for the default Python 3 and not for all available versions. I'll ask on the Debian Python Module Team mailing list for insight on the matter in a few days if

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

Le samedi 18 janvier 2020 à 02:38 +, peter green a écrit : > I just took a look at the "add python3.8 transition tracker", and > split the remaining "bad" packages into categories. There's another kind of issue ; here is an example : - sagemath builds only for Python 3.7, so some of this

Bug#948731: Shouldn't work upstream either

Hi, I tried to have a look at this bug : I don't even understand how it is supposed to work upstream, so I reported it there: https://trac.sagemath.org/ticket/29036 JP

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

Le dimanche 19 janvier 2020 à 00:54 +, peter green a écrit : > > There's another kind of issue > Yeah, sadly the transition tracker only looks at unstable, so > packages that are fixed in unstable but haven't migrated to testing > for some reason won't show up. > > ; here is an example : > >

Bug#948212: Found the source : better env.py proposition

Hi, I investigated : the problem is that SAGE_SCRIPTS_DIR seems to be set to /usr/bin, so sage-maxima.lisp is searched as /usr/bin/sage- maxima.lisp. I modified env.py so SAGE_SCRIPTS_DIR points to /usr/share/sagemath/bin, and things got further. The next error is a symbol not found:

Bug#933739: Problems of setuptools-scm with debian/1.9-4 tags : forwarded upstream

Hi, I forwarded the bug report to upstream : https://github.com/pypa/setuptools_scm/issues/402 Cheers, JP

Bug#948212: Solution to the bug : one-liner change

Hi, Le jeudi 16 janvier 2020 à 11:57 -0500, John Scott a écrit : > On Thu, 16 Jan 2020 17:36:21 +0100 Julien Puydt < > julien.pu...@laposte.net> > wrote: > > I fixed the brial package which was the culprit for the missing > > symbols, and can confirm that what is neede

Bug#947827: Missing symbols in -lblas ?

Package: libatlas3-base Version: 3.10.3-9 I tried to work on the scilab package, but couldn't get very far : for some reason, the configure script was failing to detect the umfpack library. But looking in config.log, I found out the reason was that the BLAS used is atlas, and linking to it gives

Bug#948212: sage-maxima.lisp isn't found correctly

Package: sagemath Version: 8.9-3 Running "import sage" in Python 3 works, but probably only because of some lazy loading ; indeed: >>> from sage import * Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/sage/all.py", line 84, in from

Bug#947500: Missing -latomic on mipsel & armel only?

Package: g++-9 Version: 9.2.1-21 I have a package which fails to build on both Debian armel and mipsel with this g++ package, and with the same error: /usr/bin/ld: ./.libs/libfplll.so: undefined reference to `__atomic_store_8' /usr/bin/ld: ./.libs/libfplll.so: undefined reference to

Bug#947827: Missing symbols in -lblas ?

Hi, Le samedi 07 mars 2020 à 10:36 +0100, Sébastien Villemot a écrit : > Dear Julien, > > Sorry for my late reply. I don't think the problem is still current, since I have recently worked on scilab and managed to prepare an upload. > Le mardi 31 décembre 2019 à 11:53 +0100,

Bug#955775: ipython3 and entry_points

Hi, I think your report strange : using #!/usr/bin/env python as a shebang shouldn't really solve the issue : it points to Python 2 ! The Fedora script is interesting : I should have a look. Thanks! JP

Bug#953795: Multi-tarball vs new package

Hi, I have a preference for new packages instead of multi-tarball ones, but indeed it's the maintainer's choice ; I'll just update node-unicode- tr51 to work with whatever will be available... if it is still of use, since I don't know what still uses it! Cheers, JP

Bug#953979: RM: node-unicode-tr51 -- RoM; FTBFS; abandoned upstream

Package: ftp.debian.org Severity: normal I'm the maintainer of the node-unicode-tr51 package (within the JavaScript team), and : - a FTBFS bug (#953793) has been filled against the package because it doesn't build with unicode 13.0.0 ; - so I checked upstream, where the front page says it is

Bug#721197: minetest-mod-technic from RFP to ITP

retitle 721197 ITP: minetest-mod-technic -- Minetest module for extensive machinery owner 721197 jpu...@debian.org thanks I am trying to package this for Debian. For this reason, I already asked upstream to clarify the versioning : https://github.com/minetest-mods/technic/issues/541 and started

Bug#955560: ITP: minetest-mod-throwing-arrows -- Minetest mod - Throwables

Package: wnpp Severity: wishlist * Package name: minetest-mod-throwing-arrows Version : 1.1 Upstream Author : Eurythmia team * URL : https://github.com/minetest-mods/throwing_arrows * License : MPL-2.0 Programming Lang: lua Description : Minetest mod -

Bug#955694: scilab: FTBFS: Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).

Hi, Le jeudi 23 avril 2020 à 00:20 +0200, Gilles Filippini a écrit : > Gilles Filippini a écrit le 22/04/2020 à 09:59 : > > I think I've eventually found a fix for Scilab. Please hold. > > Here it is, attached. I'm checking it right now. Thanks! JP

Bug#911218: DFSG-incompatible sound (or even sounds?)

Hi, I did package it, and didn't notice any problem, but ftpmasters did find a clearly non-redistributable file, and upstream wouldn't confirm the status of the other sound files nor fix the panda one : https://notabug.org/TenPlus1/mobs_animal/issues/15 So I'm a bit at loss here : should I

Bug#959224: buster-pu: package scilab/6.0.1-10

lso follow it. Thanks, JP PS: here it is: commit 55df6269e8ac1a5a4200dbb759c3661bbd1249f2 Author: Julien Puydt Date: Thu Apr 30 17:22:15 2020 +0200 Add patch from Gilles Filippini to fix library path loading with the recent openjdk 11.0.7 upload. (Closes: #955694, #959034) diff --

Bug#959224: buster-pu: package scilab/6.0.1-10

Le vendredi 01 mai 2020 à 11:21 +0100, Adam D. Barratt a écrit : > Just to confirm, does scilab with this patch still work if used in > conjunction with OpenJDK 11.0.6? (11.0.7 isn't currently available on > a few architectures.) No... it's either with Gilles' patch and it works with 11.0.7 or

Bug#959224: buster-pu: package scilab/6.0.1-10

Le vendredi 01 mai 2020 à 11:59 +0100, Adam D. Barratt a écrit : > On Fri, 2020-05-01 at 12:37 +0200, Julien Puydt wrote: > > Le vendredi 01 mai 2020 à 11:21 +0100, Adam D. Barratt a écrit : > > > Just to confirm, does scilab with this patch still work if used > >

Bug#959224: buster-pu: package scilab/6.0.1-10

Le vendredi 01 mai 2020 à 11:59 +0100, Adam D. Barratt a écrit : > On Fri, 2020-05-01 at 12:37 +0200, Julien Puydt wrote: > > No... it's either with Gilles' patch and it works with 11.0.7 or > > without and it works with 11.0.6... any other combination doesn't > > work.

Bug#959224: buster-pu: package scilab/6.0.1-10

h loading + with the recent openjdk 11.0.7 upload. (Closes: #955694, #959034) + + -- Julien Puydt Fri, 01 May 2020 16:47:40 +0200 + scilab (6.0.1-10) unstable; urgency=medium [ Alexis Murzeau ] diff --git a/debian/patches/addLibraryPath.patch b/debian/patches/addLibraryPath.patch new

Bug#959224: buster-pu: package scilab/6.0.1-10

Le vendredi 01 mai 2020 à 16:38 +0100, Adam D. Barratt a écrit : > Thanks, please feel free to upload that. Done. Thanks, JP

Bug#957782: Reported upstream

Hi, I notified upstream that their fortran code is going to break : http://bugzilla.scilab.org/show_bug.cgi?id=16422 Cheers, JP

Bug#808839: How does it affect scilab?

Hi, can I know how it affects scilab? Cheers, JP

Bug#959034: Scilab 6.0.1 with openjdk 11.0.7 ?

Hi, openjdk 11.0.7 in buster? It's annoying, because it breaks scilab... Testing has a fixed scilab, 6.1.0+dfsg1-2 but it's not supposed to get to stable unfortunately. I'm a bit a loss to what I could propose... I'll ask around for directions, JP

Bug#744073: New maintainer needs an update

Hi, I have been the most active maintainer of scilab in Debian recently, and I'm reviewing old bugs : is ubuntu still having issues with the scilab packaging in Debian? Cheers, JP

Bug#844134: Is it current in scilab?

Hi, sorry, but is that a problem with scilab? If it's a currently active problem with scilab, I'll see what I can do. If not, I'll just close it. Cheers, JP

Bug#953437: Sample code not crashing

Hi, I tried the sample code, and it worked well: (sid_mipsel-dchroot)jpuydt@eller:~$ ./hypergeom hypergeom(5.50e+00, 2.279935e+00)=8.363951e-07 (sid_mipsel-dchroot)jpuydt@eller:~$ ./hypergeom 0.6 0.5 hypergeom(6.00e-01, 5.00e-01)=9.166128e-01 (sid_mipsel-dchroot)jpuydt@eller:~$

Bug#953437: Flint problem reported upstream

Le samedi 09 mai 2020 à 09:04 -0300, David Bremner a écrit : > Julien Puydt writes: > > > I forwarded the problem upstream : > > > > https://github.com/wbhart/flint2/issues/699 > > > > I'll update the package when a fix will be available. > > > >

Bug#953437: Flint problem reported upstream

Le samedi 09 mai 2020 à 09:19 -0300, David Bremner a écrit : > Julien Puydt writes: > > > Well, that will be something to check when we'll have a fixed > > package > > (be it with a patch or a new upstream version). > > > > And if it doesn't fi

<    4   5   6   7   8   9   10   11   12   13   >