Bug#964109: Already reported upstream

Hi, I reported the issue to upstream 11 days ago : https://github.com/wbhart/flint2/issues/771 JP

Bug#962555: scilab: FTBFS with libicu (>= 66)

Hi, sorry I didn't find the time to answer faster. Le mardi 09 juin 2020 à 15:35 -0400, Boyuan Yang a écrit : > During a local rebuild of your package, it seems that package scilab > currently FTBFS against new version of libicu library: > > == > In file included from /usr/in

Bug#960041: On python-tornado4

Hi, do you have any reason for not filing a RM bug request to the ftp- master team? If it's an old fork with no rdepends, that looks like a good candidate. Cheers, JP

Bug#961122: 1.5.0.87+dfsg1-1 is out of the way already

Le samedi 23 mai 2020 à 22:37 +0300, Adrian Bunk a écrit : > On Fri, May 22, 2020 at 04:13:02PM +0200, Julien Puydt wrote: > > I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the > > 20th > > of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march

Bug#961122: 1.5.0.87+dfsg1-1 is out of the way already

Hi, I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the 20th of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march, and unstable had it since the 4th of march. Isn't the problem history already? JP

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#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#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#945214: marked as pending in testpath

Control: tag -1 pending Hello, Bug #945214 in testpath 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: https://salsa.debian.org/python-team/modules/testpath/commit/63a035699b7c884374aed

Bug#943526: marked as pending in node-typescript

Control: tag -1 pending Hello, Bug #943526 in node-typescript 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: https://salsa.debian.org/js-team/node-typescript/commit/034694bb9b64705215a

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#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#941353: marked as pending in node-magic-string

Control: tag -1 pending Hello, Bug #941353 in node-magic-string 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: https://salsa.debian.org/js-team/node-magic-string/commit/b110993a566ac9e

Bug#941575: marked as pending in node-typescript

Control: tag -1 pending Hello, Bug #941575 in node-typescript 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: https://salsa.debian.org/js-team/node-typescript/commit/70b420676f29dd3a6a3

Bug#933077: marked as pending in node-typescript

Control: tag -1 pending Hello, Bug #933077 in node-typescript 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: https://salsa.debian.org/js-team/node-typescript/commit/6ec246a02e7c1009d60

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 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 rem

Bug#934915: marked as pending in node-es6-promise

Control: tag -1 pending Hello, Bug #934915 in node-es6-promise 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: https://salsa.debian.org/js-team/node-es6-promise/commit/c07ec55a09ac008cb

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#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#934496: marked as pending in node-regexpu-core

Control: tag -1 pending Hello, Bug #934496 in node-regexpu-core 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: https://salsa.debian.org/js-team/node-regexpu-core/commit/d119d928ff3b4bc

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 to

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. JP

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#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

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

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

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 l

Bug#919971: Bug #919971 in node-rollup-pluginutils marked as pending

Control: tag -1 pending Hello, Bug #919971 in node-rollup-pluginutils 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: https://salsa.debian.org/js-team/node-rollup-pluginutils/commit/923

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 maintai

Bug#911488: Bug #911488 in path.py marked as pending

Control: tag -1 pending Hello, Bug #911488 in path.py 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: https://salsa.debian.org/python-team/modules/path.py/commit/ff9312b47133d880e6c85e

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 so

Bug#902826: Fixed in latest upload

Control: fixed -1 6.0.1-5 Hi, according to the buildd's logs, there is no problem building on i386 anymore. Thanks, jpuydt on irc.debian.org

Bug#905017: LXDE: Frozen display issue

Hi, Le 31/07/2018 à 17:53, Julien Puydt a écrit : I'll have to check what happens when disabling extensions... but for now I have a long-running program, so I don't want to risk breaking my session : it will have to wait a little before I can do some tests. I made some more tests

Bug#905017: LXDE: Frozen display issue

Hi, Le 31/07/2018 à 17:40, Carsten Schoenert a écrit : On Tue, Jul 31, 2018 at 04:50:08PM +0200, Julien Puydt wrote: Hi, Le 31/07/2018 à 16:23, Carsten Schoenert a écrit : Hello Julien, unfortunately all the interesting things are missing or could only be figured out partially from the the

Bug#878337: Remove the package?

Hi, is there any hope for this package? At one point node-source-map will need to be updated. For now I have a RC bug on node-source-map to remind me not to update it too fast, but it's a bit unfair : the problem doesn't stem from node-source-map if node-grunt-contrib-concat is abandoned...

Bug#905017: [workaround] Frozen display issue

Hi, Le 31/07/2018 à 16:23, Carsten Schoenert a écrit : Hello Julien, unfortunately all the interesting things are missing or could only be figured out partially from the the deep of your report. Do you have used reportbug to create this report? I never use reportbug, as I find it a pain to use

Bug#905017: [workaround] Frozen display issue

Package: thunderbird Version: 1:52.9.1-1 Severity: grave Launching thunderbird, my display would get half-frozen : only the mouse pointer was still moving, and changing (arrow, hand, etc) when it hovered over different things. I think I could still move windows around, because I could see it chan

Bug#875790: fixed in scilab 6.0.1-2

Hi, Le 29/05/2018 à 19:34, Emilio Pozuelo Monfort a écrit : > Control: reopen -1 > Control: retitle -1 scilab: depends on openjdk-8 > > On Mon, 14 May 2018 21:21:44 +0200 Emilio Pozuelo Monfort > wrote: >> On Fri, 04 May 2018 05:05:48 + Julien Puydt wrote: >>&

Bug#891351: Details

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

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#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#889620: Bug #889620 in jupyter-core marked as pending

Control: tag -1 pending Hello, Bug #889620 in jupyter-core 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: https://salsa.debian.org/python-team/modules/jupyter-core/commit/a1f315ba1d0f

Bug#889048: [node-source-map] FTBFS: lib/mappings.wasm

Hi, notice that I reverted the update to upstream version 0.7.0 (it broke too many things - sorry :-( ), so this file is no longer a problem : I'll lower the severity of this bug so it doesn't prevent testing migration, but I'll keep it open so it's under my eyes when I want to upgrade later. Sna

Bug#825095: [Python-modules-team] Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

able. The changelog is: python-backports-shutil-get-terminal-size (1.0.0-4) unstable; urgency=medium * Fix a typo in the substvar depends (Closes: #884687) * Refresh packaging: - Use https in d/copyright's Format. - Bump dh compat to 10. - Bump d/watch to version 4. - Bump std-ve

Bug#884033: scilab-celestlab

Hi, again, a number of heterogeneous strings, then I get a prompt after warnings, and quitting (several times) leads to a success. I haven't reproduced the segfault in this bug report, but I have found problems which indicate that the three listed packages do not support the most recent scilab ve

Bug#884033: Different error

Hi, I finally found some time to have a look and tried to reproduce the issue with scilab-plotlib, but I get a different problem: SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1 DOCBOOK_ROOT=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh \ /usr/bin/scilab -nw -f builder.sce Scilab 6.0.0 (Dec

Bug#884033: Scilab-ann : obsolete?

Hi, for scilab-ann, I tried to reproduce and got the following: - first a heterogeneous string ; - then the version test is bogus : it does check the main digit but the second, so 6.0.0 appears older than 5.3 ; - finally I get complaints "tbx_build_cleaner(name, path) is obsolete. Please use tbx_b

Bug#884687: marked as pending

=2c27e43 --- commit 2c27e43625342531739cf54e34582462060bfeff Author: Julien Puydt Date: Mon Dec 18 18:50:27 2017 +0100 Fix typo in the substvar deps (Closes: #884687) diff --git a/debian/changelog b/debian/changelog index 13beca8..54fa404 100644 --- a/debian/changelog +++ b/debian/changelog

Bug#876733: Licensing of jeuclid

Hi, according to bug #876733, there is a licensing problem with jeuclid : - the LICENSE.txt file [1] says Apache 2.0 ; - the NOTICE file [2] looks like an Apache 1.0. This RC bug will get jeuclid out of Debian, hence also scilab (which I just moved from O to ITA). My interpretation of the issue

Bug#877212: [Pkg-javascript-devel] Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing

Hi, Le 30/09/2017 à 21:06, Jérémy Lal a écrit : > > I did a quick check on acorn and rollup and i fail to see how > acorn-object-spread > is related to these modules. Even the github issue is not really explicit. > Can you explain please ? The dep thread is the following: rollup needs rollup-plug

Bug#872613: [Pkg-javascript-devel] Bug#872613: node-mocha FTBFS with nodejs 6.11.2: test failures

Hi, Le 19/08/2017 à 13:10, Adrian Bunk a écrit : > Source: node-mocha > Version: 1.20.1-7 > Severity: serious > Tags: buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mocha.html > > ... > [31m 4 failing > >  1) Suite .beforeAll() wraps the passed

Bug#872533: Easy to fix

Hi, to fix the problem, either try a newer chai (#868319), or change the expected strings to match the more precise error message we have now. Snark on #debian-js

Bug#872433: [Pkg-javascript-devel] Bug#872433: [with solution] Doesn't find modules installed in Debian directories

Hi, Le 17/08/2017 à 14:23, Bastien ROUCARIES a écrit : > Could you get a glimpse at node-minimatch debian/test/runtestsuite ? Won't work, since we don't have all the test deps in Debian (lacking object-keys -- beware we have object-key but that's not what it wants). > For the NMIU one lintian wa

Bug#872433: [Pkg-javascript-devel] Bug#872433: [with solution] Doesn't find modules installed in Debian directories

loader : commit 706643f1cc5c6a6d72b0fa092379ed6f029b6540 (HEAD -> master) Author: Julien Puydt Date: Thu Aug 17 13:54:36 2017 +0200 Remove useless build-dep on dh-buildinfo commit c5cf00738e9a7c597a86406ddb9ae1c7a8e086a3 Author: Julien Puydt Date: Thu Aug 17 13:52:23 2017 +0200 Add an

Bug#872433: [with solution] Doesn't find modules installed in Debian directories

Package: node-resolve Version: 1.1.7-2 Severity: grave Hi, I'm surprised nobody reported it yet since it basically makes the package useless as far as I see, but the current node resolve doesn't find modules installed in Debian directories : while working on another package, I was surprised that

Bug#871794: Applied

Hi, I just pushed a commit which also changes the python-2.7 test to python2. Thanks for the report and the fix! Snark on #debian-science

Bug#868298: Get out of Debian for better alternatives?

Package: node-evp-bytestokey Version: 1.0.0-3 Severity: grave Hi, the upstream homepage says to avoid using it, so perhaps it should get out of Debian and the other packages depending on it should be ported to something actually working? Snark on #debian-js

Bug#866508: Not able to reproduce

Hi, I haven't been able to reproduce your problem. I think that module is provided by sagemath-common -- can you try to re-install it? Thanks, Snark on #debian-science

Bug#866798: [Pkg-javascript-devel] Bug#866798: node-esprima FTBFS: error TS5023: Unknown compiler option 'strict'

Hi, Le 01/07/2017 à 21:20, Adrian Bunk a écrit : > Source: node-esprima > Version: 4.0.0+ds-1 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=node-esprima&arch=all&ver=4.0.0%2Bds-1&stamp=1498935187&raw=0 > > ... > make[1]: Entering directory '/<>/node-esprima-4.0.0+ds' > t

Bug#852007: But gcc-6 can't build flint on some architectures!

Hi, the flint package uses gcc-5 and g++-5 only on mips and mipsel, where the later compilers just give bad things ; from d/rules : # FTBFS on mips and mipsel seems to be caused by a bug in gcc 6, # see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176 What can I do here ? Snark on #debian-

Bug#849750: Crashes the (LXDE) desktop

Package: marsshooter Version: 0.7.6-1+b1 Severity: critical Hi, I installed the package, clicked on the menu entry and my lxde panel just disappeared. I restarted lxdm and retried : same effect! Restarting lxdm and launching in a terminal, I get : Cannot connect to server socket err = No suc

Bug#847789: On the new problem

Hi, I found the time to compile the deps to check for myself, as it would be easier than having you report issues one by one, but I'm stuck with node-glob-stream, which build-depends on node-extend (>= 2.0.0) (available) but depends on node-extend (>= 3.0.0), which isn't available, even in gi

Bug#847789: Possible fix

(Debian's nodejs is too old) Author: Julien Puydt Forwarded: no --- a/src/loose/state.js +++ b/src/loose/state.js @@ -4,7 +4,8 @@ export const pluginsLoose = {} export class LooseParser { - constructor(input, options = {}) { + constructor(input, options) { +if (!o

Bug#845565: If I open the door from local, remote works

Hi, this morning I made a small test : I signed a file from the local X session (I get a window for the passphrase), then I changed keyboard and tried to sign a file from remote : that worked (nothing asked). I think that confirms my hunch it's a problem of fallback : if the session from rem

Bug#845565: Unable to sign from remote

Package: src:pinentry Version: 0.9.7-9 Severity: grave I'm using a setup where I use mosh to connect to a remote host, with an attached tmux. I get a failure: $ LANG=C gpg -s /tmp/test gpg: signing failed: pinentry error gpg: signing failed: pinentry error I tried to strace the command above a

Bug#843898: Something to try

Hi, can all of you seeing the problem try to reproduce the following session, please, and send what you get: jpuydt@nox:~$ python Python 2.7.12+ (default, Nov 4 2016, 17:04:30) [GCC 6.2.0 20161027] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from back

Bug#843898: Isn't python-backport-shutil-get-terminal-size installed?!

Control: tags -1 +moreinfo Hi, the ipython package depends on python-ipython, which itself depends on python-backport-shutil-get-terminal-size, so that shouldn't happen -- can you check things are installed correctly? Thanks, Snark on #debian-python

Bug#841614: node-es6-promise: FTBFS: compile-modules shows help

Hi, On 31/10/2016 08:01, Lucas Nussbaum wrote: On 29/10/16 at 11:14 +0200, Julien Puydt wrote: Hi, I tried to "pbuilder create" a new base.tgz, but it still had tzdata and lsb-base, so I had to "pbuilder login --save-after-login" and remove them by hand using "dpk

Bug#841614: node-es6-promise: FTBFS: compile-modules shows help

Hi, I tried to "pbuilder create" a new base.tgz, but it still had tzdata and lsb-base, so I had to "pbuilder login --save-after-login" and remove them by hand using "dpkg --purge" (then "apt-get autoremove" that did nothing). I still had no problem building node-es6-promise. How can I get th

Bug#842333: Leaves :0 open on logout

Package: lxdm Version: 0.5.3-1 Severity: critical Hi, if I ssh (no -X) to a box running lxdm and try to run DISPLAY=:0 xeyes I get an error because I don't have the rights to the display. Now, if I log directly into lxdm on that box, then logout, and retry the ssh then DISPLAY=:0 xeyes from re

Bug#841614: I can't reproduce the FTBFS

Hi, this looks annoyingly like #835581, which I fixed a month ago. I checked your build log and saw node-ast-types 0.9.0-2 was used... and that was this version which got #835581 fixed. I removed my pbuilder base.tgz and created one anew to check the node-es6-promise 3.2.2+ds-1 build : no pr

Bug#835581: node-es6-promise: FTBFS in testing (compile-modules shows usage help)

Hi, node-ast-types 0.9.0-2 migrated to testing two weeks ago, so it should now be pretty trivial to check whether the problem is gone. Can you confirm my intuition? Thanks, Snark on #debian-js

Bug#835581: Is my theory correct?

Control: tags -1 +moreinfo Hi, can you test whether things compile well now? Thanks, Snark on #debian-js

Bug#835581: Possible fix for the FTBFS in node-es6-promise

Hi, I don't have a stretch box handy, but /usr/bin/compile-modules comes from the node-es6-module-transpiler package. Testing has node-es6-module-transpiler version 0.10.0.1, which depends on node-ast-util (in testing 0.6.0-1), which depends on node-ast-types (in testing 0.9.0-1). Things ge

Bug#835704: It's mostly fixed already!

Hi, today's upload of node-ast-types 0.9.0-2 fixes this problem in node-ast-utils (and all its rdepends). I don't know how to say to control@bugs.d.o that a problem in a package is fixed by an upload of another. When/how can I properly close this bug? Cheers, Snark on #debian-js

Bug#825095: marked as pending

=0e8bb0c --- commit 0e8bb0c1b7b094f59d2950cb61b384218f3cefd8 Author: Julien Puydt Date: Thu Jul 28 11:46:25 2016 +0200 Declare Breaks on old python-backports.ssl-match-hostname to really fix #825095 diff --git a/debian/changelog b/debian/changelog index 1684da9..458a66e 100644 --- a/debian

Bug#825095: python-backports-* packages clashing

Hi, On 24/07/2016 09:21, Andreas Beckmann wrote: On 2016-07-24 07:43, Julien Puydt wrote: Hi Andreas, you reported that 1.0.0-2 still had the problem even though I closed the bug with its upload. Are you sure you updated both python-backports-* packages to their latest versions? No, but

Bug#825095: python-backports-* packages clashing

Hi Andreas, you reported that 1.0.0-2 still had the problem even though I closed the bug with its upload. Are you sure you updated both python-backports-* packages to their latest versions? Snark on #debian-python

Bug#825095: marked as pending

=3dacd27 --- commit 3dacd27fe8387865f4e2b81bf4582802c1b73281 Author: Julien Puydt Date: Thu Jul 21 13:11:08 2016 +0200 Fixed file conflict with other python-backports-* packages. (Closes: 825095) diff --git a/debian/changelog b/debian/changelog index e9160a9..19e4c24 100644 --- a/debian/changelog

Bug#811847: givaro RC bug #811847

Hi Doug, On 17/07/2016 19:54, Doug Torrance wrote: I see that you've recently pushed some changes to git which close the RC bug #811847 [1]. Were you planning on uploading them? I ask because givaro is currently scheduled for auto-removal from testing. I'm also interested in givaro as it is a

Bug#830493: Confusion with minetest-mod-mobf

Hi, according to bug #827669 the current minetest-mod-mobf packaging is buggy/incomplete with a debian/ directory shipped within and probably missing directories ; in #830493 I pointed out that one of the missing directories was really a missing package on which to depend. After some more po

Bug#829150: Where is the repository

On 08/07/2016 15:10, James Cowgill wrote: On Fri, 2016-07-08 at 15:03 +0200, Julien Puydt wrote: I wanted to lend a hand on the matter, but unfortunately the git repository hasn't been updated in ages, so I can't do much... Are you sure? This repo was updated 13 days

Bug#830493: Lacks depends

Package: minetest-mod-mobf Version: 2.5.0-1 Severity: grave In fact, the new version of mobf needs minetest mods available within the animalmaterials modpack. Without those, it doesn't bring anything more than error messages on the screen (and that only if you disable the buggy appearance of a

Bug#829150: Where is the repository

Hi, I wanted to lend a hand on the matter, but unfortunately the git repository hasn't been updated in ages, so I can't do much... Snark on #debian-games

Bug#811787: On irrlicht and RC bug #811787

Hi, On 06/07/2016 17:46, Gianfranco Costamagna wrote: control: tags -1 pending control: tags -1 patch Shall I turn it in a NMU or do you maintainers/uploaders have something ready to shoot? I guess a team upload is perfectly fine! I'll do it in a few hours if nobody objects, thanks a lot fo

Bug#811787: [PATCH] Fixed in upstream's repository

Hi, it is fixed in upstream's repository : https://sourceforge.net/p/irrlicht/code/5253/ so it should just be a matter of adding that patch in debian/patches/ until upstream releases a stable version with the fix. I hope that helps, Snark on #debian-science

Bug#828107: FTBFS on armel (egr_bound isn't zero)

Package: eclib Version: 20160206-1 Severity: serious One of the checks breaks on armel : https://buildd.debian.org/status/fetch.php?pkg=eclib&arch=armel&ver=20160206-1&stamp=1460835373 I have been unable to reproduce it on the armhf box I have though. Snark on #debian-science

Bug#827035: Package is currently unusable

Package: node-recast Version: 0.11.4-1 Severity: grave The package is unusable : in fact, it should now depend on node-esprima, which Debian doesn't have (but I already pushed a package on mentors). I should have caught that sooner. Snark on #debian-js

Bug#826078: Confirm

Hi, yes, there's a syntax error in Python 2 on line 366. I also see a few lines down (387) a "yield from" which won't fly either. Snark on #debian-python

Bug#824858: marked as pending

b9d3efb2b8152f9e551cee0be738bdb1612b0a13 Author: Julien Puydt Date: Sat May 21 16:13:37 2016 +0200 Documented changes diff --git a/debian/changelog b/debian/changelog index 68a22e5..bc285b5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +pickleshare (0.7.2-2) UNRELEASED; urgency

Bug#818990: Is it really a flint problem?

Hi, On 19/04/2016 12:22, Mattia Rizzolo wrote: On Tue, Apr 19, 2016 at 10:04:31AM +0200, Julien Puydt wrote: Hi, (1) according to: https://buildd.debian.org/status/package.php?p=flint&suite=sid the version 2.5.2-3 of flint built perfectly on amd64. yeah, that's a past tense.

Bug#818990: Is it really a flint problem?

Hi, (1) according to: https://buildd.debian.org/status/package.php?p=flint&suite=sid the version 2.5.2-3 of flint built perfectly on amd64. (2) more recently (yesterday) : https://buildd.debian.org/status/package.php?p=flint&suite=experimental the version 2.5.2-4 of flint built perfectly on am

Bug#818990: Re: About bug #818990

On 12/04/2016 20:08, Mattia Rizzolo wrote: On Tue, Apr 12, 2016 at 07:47:23PM +0200, Julien Puydt wrote: What could be the difference? Don't know, sorry. Good luck! Well, does the box run unstable too? that box is a standard jessie system running standard chroots (either te

Bug#818990: Re: About bug #818990

Hi, On 12/04/2016 19:12, Chris Lamb wrote: Did you get your failures on the same box each time you saw the failure? Yes. We can also reproduce a FTBFS on the reproducible builds testing framework: https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/flint.html Uh... you tell me "Ye

Bug#818990: About bug #818990

Hi, On 11/04/2016 22:27, Chris Lamb wrote: dget http://mentors.debian.net/debian/pool/main/f/flint/flint_2.5.2-4.dsc This FTBFS for me. Build log attached. Regards, It is a good thing that you see 2.5.2-4 fail like 2.5.2-3 since I didn't touch anything related to your problem. That bein

Bug#818990: About bug #818990

Hi, I'm Snark on IRC ; this is about : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818990 where you have FTBFS on my flint 2.5.2-3 package (a failing unit test on amd64). When I tried to build my package, it failed because of a documentation problem, and not because of a unit test pro

Bug#818990: Couldn't reproduce

Hi, I made a patch to get around my documentation problem, and built the package without issue. On an amd64 like in your report. Can you get me more information on the issue? Does it happen again on the same box if you retry? Does it happen on another computer? Thanks, JP

Bug#818990: Another breakage in the documentation

Hi, I couldn't reproduce your failure... because I get a problem during the doc build: Overfull \hbox (24.5199pt too wide) in paragraph at lines 3768--3777 [][][][]\T1/aer/m/n/10 . The cur-rent lifted fac-tors are sup-plied in [][][] [129] [130] [131] [132] ! Argument of \zap@to@space has an

<    1   2   3   >