Bug#1051166: FTBFS with doxygen 1.9.8

Package: breathe-doc Version: 4.35.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More

Bug#1051165: FTBFS with doxygen 1.9.8

Package: libstxxl-doc Version: 1.4.1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More

Bug#1051162: FTBFS with doxygen 1.9.8

Package: netcdf-doc Version: 1:4.9.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More

Bug#1051156: FTBFS with doxygen 1.9.8

Package: seqan-raptor-doc Version: 3.0.1+ds-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it.

Bug#1051155: FTBFS with doxygen 1.9.8

Package: wxpython-tools Version: 4.2.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it.

Bug#1051154: FTBFS with doxygen 1.9.8

Package: libcaca-dev Version: 0.99.beta20-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it.

Bug#1015864: doxygen: diff for NMU version 1.9.4-3.1

Hi Adrian, Il 15/10/22 14:30, Adrian Bunk ha scritto: Control: tags 1015864 + patch Control: tags 1015864 + pending Dear maintainer, I've prepared an NMU for doxygen (versioned as 1.9.4-3.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian thanks

Bug#1000932: doxygen: diff for NMU version 1.9.1-2.1

Il 15/07/22 00:23, Sebastian Ramacher ha scritto: On 2022-07-14 16:23:16 +0200, Paolo Greppi wrote: ... ACK, I've canceled the NMU. Please consider that doxygen is a key package and thus effectively keeping llvm-toolchain-11 in testing. A timely fix for this issue would be much appreciated

Bug#1000932: doxygen: diff for NMU version 1.9.1-2.1

Hi Sebastian! Il 14/07/22 11:22, Sebastian Ramacher ha scritto: Control: tags 1000932 + patch Control: tags 1000932 + pending Dear maintainer, I've prepared an NMU for doxygen (versioned as 1.9.1-2.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer.

Bug#1012021: [Pkg-javascript-devel] Bug#1012021: unreproducible here

Il 29/05/22 21:34, Pirate Praveen ha scritto: On തി, മേയ് 30 2022 at 12:56:53 രാവിലെ +05:30:00 +05:30:00, Pirate Praveen wrote: On ഞാ, മേയ് 29 2022 at 09:34:45 രാവിലെ +02:00:00 +02:00:00, Paolo Greppi wrote: Hi Andreas! thanks for your report. To try to reproduce it, I set ... Finally

Bug#1012021: unreproducible here

Hi Andreas! thanks for your report. To try to reproduce it, I set up multiarch for docker (https://github.com/multiarch/qemu-user-static) then: docker run --rm -it arm64v8/debian:unstable bash apt update apt upgrade apt install curl yarnpkg curl -o package.json

Bug#977814: should be fixed with clazy 1.9-3

Hi I see "pass" for clazy/1.9-3 with llvm-toolchain-11/1:11.0.1-2: https://ci.debian.net/packages/c/clazy/testing/amd64/ I also tried this here on unstable and the autopkgtest did pass. Can you check and if confirmed as fixed close this bug? Thanks, Paolo

Bug#975931: should be fixed with pocl 1.6 ?

pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares that v1.6 includes "Support for Clang/LLVM 11". Can you try your reproducer now ? Thanks Paolo

Bug#979007: Processed: retitle and set severity to critical

Dear Melvin, Il 14/01/21 13:51, Melvin Vermeeren ha scritto: Hi Paolo, On Thursday, 14 January 2021 10:28:32 CET Paolo Greppi wrote: Doh I had not seen this: https://bugs.debian.org/976227 Let me put both the future Debian maintainer and the current upstream maintainer in Cc. Thanks

Bug#979007: Processed: retitle and set severity to critical

Il 14/01/21 09:40, Sebastian Ramacher ha scritto: ... The package is orphaned. If you a fix for it, please upload it. Best Doh I had not seen this: https://bugs.debian.org/976227 Let me put both the future Debian maintainer and the current upstream maintainer in Cc. I am a DM and currently

Bug#979007: Processed: retitle and set severity to critical

Hi Sebastian, Il 09/01/21 11:41, Sebastian Ramacher ha scritto: Control: severity -1 serious ... No, critical is not the correct severity for FTBFS bugs. That's serious. Sorry my fault. I just added a "forwarded upstream" link, it is possible that just by applying the patch provided by

Bug#977781: [Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

Hi Akshay, many thanks for the debugging ! see below Il 22/12/20 06:06, Akshay S Dinesh ha scritto: There are some 4 pipes before the finish event. I'm looking through each one of them to see if there's a mismatch. It seems to be tar-fs Please see

Bug#977781: real issue is, it does not pull not-yet-cached modules

Hi Pirate, what you want to put in ~/.yarnrc.yml could be installed globally to /etc/yarn/config or /etc/yarnrc, but that does not actually fix it. I think the real issue is that it does not pull not-yet-cached modules. To reproduce: # clear cache rm -rf ~/.cache/yarn # actual test

Bug#976495: also happens on amd64, should be worked around by 1.8.20-5 but the real fix will come with 1.8.20-6

Hi Lucas (is it you, or a bot?), thanks for the new bug report about doxygen 1.8.20-4 FTBFS on arm64: https://bugs.debian.org/976495 I had noticed this issue yesterday and worked around it with 1.8.20-5 but the real fix will come with 1.8.20-6, thanks to a tip from Norbert Preining:

Bug#976081: [Pkg-javascript-devel] Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen wrote: Control: clone -1 -2 Control: retitle -2 "Provide prebuilt yarnpkg in contrib" On Sat, Nov 28, 2020 at 22:07, Paolo Greppi wrote: >> 3. Build it using 'deb >> https://snapshot.debian.org/archive/debian/2020050

Bug#973741: [Pkg-javascript-devel] Bug#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

there is a 4th option, see below Il 28/11/20 20:28, Pirate Praveen ha scritto: ... So some options I can think, 1. Port yarn 1.x to build with babel 7 (but this has not been successfull) 2. Try to run ES6 code directly somehow, may be with newer nodejs and patches. I think Paolo tried this

Bug#973741: [Pkg-javascript-devel] Bug#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

See below Il 28/11/20 20:28, Pirate Praveen ha scritto: On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen wrote: ... So some options I can think, 1. Port yarn 1.x to build with babel 7 (but this has not been successfull) 2. Try to run ES6 code directly somehow, may be with newer nodejs and

Bug#972952: [Pkg-javascript-devel] Bug#972952: Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

Hi Xavier, Il 26/10/20 20:24, Xavier ha scritto: Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit : ... Hi JS Team, yarnpkg is not in testing due to babel problems. Do you agree to dicrease severity of this bug to allow mkdirp transition (or reassign this bug to node-yarnpkg)

Bug#969313: doxygen: fails to parse long configuration files from standard input

Package: doxygen Version: 1.8.19-1 Severity: serious when doxygen is invoked with the "-" parameter, it does not always do what is advertised in the doxygen manpage ("If - is used for configName doxygen will read from standard input") due to a buffer size limit, only 4096 characters of the

Bug#950675: upstream does support doxygen-latex, but ...

Hi Simon, thanks for revving the conversation on this bug. I'll summarize below my points. Il 20/08/20 11:08, Simon McVittie ha scritto: > On Wed, 05 Feb 2020 at 11:56:16 +0100, Paolo Greppi wrote: > ... > smcv > - in general printable documentation is less relevant now

Bug#960120: node-yarnpkg: I found an older commit that still builds

Il 15/08/20 14:00, Pirate Praveen ha scritto: >> With this build: >> https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 > >> I get a different error while building: >> [17:58:12] Starting 'build'... >> 2420[17:58:13] Error: [BABEL] >>

Bug#960120: different error during build

With this build: https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 I get a different error while building: [17:58:12] Starting 'build'... 2420[17:58:13] Error: [BABEL] /builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js: Cannot find module

Bug#943423: troubles generating refman.pdf

Hi, CCfits fails to generate refman.pdf on Debian unstable with doxygen 1.8.16 and pdflatex from texlive-latex-base 2019.20191208. To reproduce: wget https://heasarc.gsfc.nasa.gov/fitsio/CCfits/CCfits-2.5.tar.gz tar xf CCfits-2.5.tar.gz cd CCfits/ ./configure make docs make -C

Bug#943423: workaround

Hi, sorry for the trouble and not being able to help: I am a latex noob ! As a workaround (while we reach a consensus on the future of doxygen-latex, or some latex guru pops up and provides a solution) I suggest that you disable the generation of /usr/share/doc/libccfits-doc/refman.pdf.gz and

Bug#950675: upstream does support it, but ...

According to: grep-dctrl -n -w -F Build-Depends,Build-Depends-Indep -s Package doxygen-latex /var/lib/apt/lists/deb.debian.org_debian_dists_sid_main_source_Sources | sort | uniq | wc there are 60 packages that build-depend on doxygen-latex in sid. The last time I run a full rebuild of build

Bug#947364: please address this bug

Hi ! this is blocking migration of libglvnd from 1.1.0-1 to 1.3.0-5, which in turn is blocking migration of qtbase-opensource-src from 5.12.5+dfsg-2 to 5.12.5+dfsg-5, which in turn is blocking doxygen (that's where this hits me !). I have verified that libgl-dev 1.3.0-5 indeed breaks the 3depict

Bug#947074: proposed fix

The proposed fix is now here: https://salsa.debian.org/js-team/node-yarnpkg/commit/ec80b4e923f8513824b978f2fe0e4b25990f7987 To make sure the build is reproducible, I have based it on this code: https://sources.debian.org/src/mime-support/3.64/debian/rules/?hl=74#L74 Probably node-glob-stream

Bug#947117: reproducible

Thanks for reporting ! Can be patched by adding libegl-dev to the build deps, but I'd wait of the Qt gurus find a better way to fix it. Paolo

Bug#947074: upstream tarballs for certain components contain unreasonably timestamped files

Yes, those files get the timestamp from the upstream tarballs. To reproduce: dget https://deb.debian.org/debian/pool/main/n/node-yarnpkg/node-yarnpkg_1.21.1-1.dsc ls -R --full-time node-yarnpkg-1.21.1/ | egrep -v '( 2019-| 2018-| 2017-| 2016)' It could be fixed by re-uploading the tarballs

Bug#943623: I got this too with libclang-9-dev 9.0.0-2 for libclangTooling.a

See: https://salsa.debian.org/debian/doxygen/-/jobs/393296 ar x /usr/lib/llvm-9/lib/libclangTooling.a file *.o AllTUsExecution.cpp.o: LLVM IR bitcode ArgumentsAdjusters.cpp.o:LLVM IR bitcode CommonOptionsParser.cpp.o: LLVM IR bitcode

Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

First, I tripped on this one while testing yarnpkg 1.19.1 from experimental. For the record, this is how I found that node-lodash was the culprit: node --trace-deprecation /usr/bin/yarnpkg install yarn install v1.19.1 [1/4] Resolving packages... (node:29081) [DEP0016] DeprecationWarning: 'root'

Bug#934458: missing python-xdg ?

Seems the same as: https://bugs.debian.org/901780 Try again after: sudo apt install python-xdg P.S. note that linkchecker-gui is not anymore in stable Paolo

Bug#929829: [Pkg-javascript-devel] Bug#929829: Bug#929829: Bug#929829: Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

On 06/06/19 07:30, Xavier wrote: ... My reducejs tool gives a new analysis: * updates needed: - gulp-babel : 7.0.1 => 8.0.0 - rollup-plugin-babel : 3.0.3 => 4.3.2 * downgraded modules to embed - process-nextick-args : 2.0.0 => 1.0.7 * problems: - build fails with our

Bug#924858: doxygen: FTBFS: make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1

unreproducible here, relevant part: ... make[4]: ingresso nella directory "/tmp/doxygen-1.8.13/build" [100%] Generating Doxygen Manual PDF. cd /tmp/doxygen-1.8.13/build/latex && /usr/bin/cmake -E remove refman.tex cd /tmp/doxygen-1.8.13/build/latex && /usr/bin/cmake -E copy

Bug#921779: Bug#919413: cascade of FTBFS

Hi Dominique, see below Il 14/02/2019 15:16, Dominique Dumont ha scritto: On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote: I'm not sure how to deal with the jquery.js one since this is potentially an issue with lots of dependencies - I remember discussions about this which I did

Bug#921356: [Pkg-javascript-devel] Bug#921356: Not suitable for buster, package probably unmaintained

This is used in node-ws (popcon 92) Paolo

Bug#921369: [Pkg-javascript-devel] Bug#921369: Not suitable for buster, package probably unmaintained

This is used in: flashproxy (popcon 25), node-d3-request (popcon 2), node-xmlhttprequest-ssl (popcon 14) Paolo Il 04/02/19 17:35, Mike Gabriel ha scritto: > Package: node-xmlhttprequest > Version: 1.6.0-1 > Severity: serious > > Dear all, > > In 2016/12 I removed my name from this package's

Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15

Source: starpu Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: mv: cannot stat 'latex/refman.pdf': No such file or directory Paolo -- System Information: Debian Release:

Bug#921299: caffe: FTBFS with upcoming doxygen 1.8.15

Source: caffe Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release: buster/sid APT

Bug#921300: frobby: FTBFS with upcoming doxygen 1.8.15

Package: frobby Version: 0.9.0-5 Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release:

Bug#921298: libstxxl: FTBFS with upcoming doxygen 1.8.15

Source: libstxxl Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release: buster/sid APT

Bug#921297: qevercloud: FTBFS with upcoming doxygen 1.8.15

Source: qevercloud Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release: buster/sid APT

Bug#921295: wcslib: FTBFS with upcoming doxygen 1.8.15

Source: wcslib Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. popcon = 569 Paolo -- System Information: Debian Release:

Bug#921296: ccfits: FTBFS with upcoming doxygen 1.8.15

Source: ccfits Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: make[2]: *** [Makefile:8: refman.pdf] Error 1 Paolo -- System Information: Debian Release: buster/sid APT prefers

Bug#921293: hwloc: FTBFS with upcoming doxygen 1.8.15

Package: hwloc Version: 1.11.12-1 Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release:

Bug#921294: fltk1.3: FTBFS with upcoming doxygen 1.8.15

Source: fltk1.3 Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: cp: cannot stat 'latex/refman.pdf': No such file or directory Paolo -- System Information: Debian Release:

Bug#888903: [Pkg-javascript-devel] Bug#888903: Bug#888903: 888903

Il 31/01/19 12:52, Jonas Smedegaard ha scritto: > ... > I suggest this way forward: > > 1) Release node-js-beautify to unstable with no executable at all > 2) Release node-js-beautify to experimental adding python package > 3) Release node-js-beautify to unstable when 1) is in testing > > I

Bug#920982: deal.ii: FTFBFS with doxygen 1.8.15 draft package

Source: deal.ii Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680/artifacts/browse/debian/output/ and it FTBFS with this error: # Replace links to

Bug#888903: [Pkg-javascript-devel] Bug#888903: jsbeautifier, node-js-beautify: both ship /usr/bin/js-beautify

Il 31/01/19 01:15, Jérémy Lal ha scritto: > ... > Hi, > > i find it funny that no one even tried to solve this bug: > both packages (python-jsbeautifier, node-js-beautify) > have the same upstream ! > The solution here is to provide two dpkg-alternative to > /usr/bin/js-beautify. > > It's

Bug#884155: show be fixed in unstable & testing

chai 4.2 has landed in testing, and all tests pass. can this be closed now ? Paolo

Bug#892656: even more tests fail with version 2.0.2

Il 13/01/19 16:52, Paul Gevers ha scritto: > user debian-rele...@lists.debian.org > usertags 884543 bsp-2019-01-nl-venlo > thanks > > On Mon, 23 Apr 2018 14:36:00 +0200 Paolo Greppi > wrote: >> So I'd propose we go straight for option #3 (downgrade node-is-descriptor to

Bug#895316: node-once repo on salsa

FYI, I have manually migrated the git repo of node-once from: https://alioth-archive.debian.org/git/collab-maint/node-once.git.tar.xz to: https://salsa.debian.org/js-team/node-once I skipped all repos on collab-maint during the mass migration in April last year:

Bug#867943: this is fixed by upstream in 8.0.12

https://dev.mysql.com/doc/relnotes/workbench/en/wb-news-8-0-12.html Changes in MySQL Workbench 8.0.12 (2018-07-27, General Availability) ... Functionality Added or Changed ... libgnome-keyring was depreciated and replaced with libsecret in this release on Linux platforms. Some users with

Bug#878337: [Pkg-javascript-devel] Bug#878337: Remove the package?

Il 31/07/2018 17:07, Julien Puydt ha scritto: > 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

Bug#898997: fix

This fixes the issue: sudo apt install python-dnspython That package should be added to the dependencies. Paolo

Bug#834915: tentative fix

Hi and thanks for your thorough testing. My explanation is that for certain filesystem / CPU speed combinations, the temp.track() option (turned on on line 7) cleans up the temporary file as soon as it receives the .end() call, and faster than the assert on file existence on line 58 can pass.

Bug#900032: [Pkg-javascript-devel] Help with a RC bug in one of my package

Il 26/05/2018 21:33, Bastien ROUCARIES ha scritto: > Hi, > > I am clueless about #900032 ... > > I found a bug and pushed it due to build profile but the empty doc is strange > > It will be empty only on upgrade (install will create the symlink). I > use dpkg-maintscript-helper so normally dir

Bug#897156: [Pkg-javascript-devel] Bug#897156: node-cache-base: FTBFS and Debci failure with node-is-extendable 1.0.1-1

Il 29/04/2018 09:29, Adrian Bunk ha scritto: > Source: node-cache-base > Version: 0.8.4-1 > Severity: serious > > https://ci.debian.net/packages/n/node-cache-base/unstable/amd64/ > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cache-base.html > > ... > 39 passing

Bug#892656: even more tests fail with version 2.0.2

Il 12/04/2018 06:19, Pirate Praveen ha scritto: > > > On April 12, 2018 2:48:32 AM GMT+05:30, Paolo Greppi <paolo.gre...@libpf.com> > wrote: >> Normally you'd expect to fix bugs with a new version, in this case >> while trying to update node-define-property 1.0.0-1

Bug#892656: even more tests fail with version 2.0.2

Normally you'd expect to fix bugs with a new version, in this case while trying to update node-define-property 1.0.0-1 -> 2.0.2 the failing tests actually increased from 1 to 4. What puzzled me was that no tests fail on upstream's CI (travis), which also tests nodejs version 8. Turns out that

Bug#886120: thanks for the info

With my previous message I was trying to understand your purpose with your bug report, not to demonstrate anything nor to dismiss it. Adding the new info you provided, the chain of events triggered by your actions would be: 1) = as above 2) = as above 3) = as above 4) since doxygen is a “key

Bug#886120: doxygen = scapegoat ?

@kilobyte, let me see if I can understand your purpose with this bug report. What happened is: 1) you find a serious bug in ctpp2 (popcon: 14) 2) you decide it's RC 3) it's doxygen fault so you reassign it to doxygen (popcon: 8381), and it stays RC Now let's look at the effect of all this: 1)

Bug#861515: unreproducibile

Hi, this seems now to have gone away by itself, possibly thanks to the upgrade from nodejs 4.x to 8.x: I don't see any error on the buildds, and it works without the patch on my x86 VM here. So I have reset the repo to the debian/1.0.0-2 tag, and moved the patch to a separate branch

Bug#865892: reproducible

This is easily reproducible: just apt remove node-asnyc, and try the build. I am working on the fix while at the same time updating to 2.0.1 Paolo

Bug#863934: fix

According to upstream (https://github.com/felixge/node-dateformat/issues/21) "dateformat() doesn't really play well with timezones since the javascript Date() object itself doesn't really play well with timezones." We should be content with fixing the tests for the GMT timezone using the trick

Bug#861515: node-grunt-contrib-copy FTBFS on armhf i386

Hi all, re. https://bugs.debian.org/861515, since we haven't got any reply from upstream for almost a month (https://github.com/gruntjs/grunt-contrib-copy/issues/291), I have updated node-grunt-contrib-copy to simply skip the failing test:

Bug#861515: reproducibile here

I have set up an i386 debci lxc testbed with: debci_arch=i386 debci setup then confirmed that the lxc container has indeed been created: lxc-ls --fancy NAME STATE AUTOSTART GROUPS IPV4 IPV6 adt-sid-amd64 STOPPED 0 - -- adt-sid-i386 STOPPED 0 -

Bug#860634: fix for node-grunt-contrib-copy RC bug

Hi team there is a RC bug on node-grunt-contrib-copy, I have provided a fix and uploaded that to alioth. I have tested with pkg-ruby-extras/build and tested the reverse deps (node-rx) too. These two packages have an impressive popcon count of ... 7+5 ! But anyway please someone sponsor the

Bug#860634: reproducible here

This is easy to reproduce on stretch from the root of a source package against the currently installed package. Just make sure the tmp directory created during the build process is not present: make -f debian/rules clean or just: rm -rf tmp then run the tests in the local environment

Bug#853035: mmmh

In the log you attached this line:  [0m Error: timeout of 5000ms exceeded looks different from what you report in the bug:  [0m Error: timeout of 1ms exceeded The test suite is run by upstream (and by us) with this command: mocha -t 5000 -b -R spec

Bug#848749: set a different $HOME for build-time tests

As per this comment in the Pkg-javascript-devel mailing list: https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-December/016725.html I have changed the approach to set a different $HOME for build-time tests. This should fix the build-time tests. Paolo

Bug#848749: disable build-time tests

Il looks like node-expand-tilde returns a directory which does not exist (sbuild-nonexistent) at this line in node-fined/test/utils/get-userhome-file.js: var userHomeDir = expandTilde('~'); This in turn triggers the exception in the next line: var userHomeFiles = fs.readdirSync(userHomeDir);

Bug#847353: [Pkg-javascript-devel] Bug#847353: Bug#846961: recent update of libjs-jquery-ui broke gitlab

On 07/12/2016 14:54, Pirate Praveen wrote: > On Wed, 7 Dec 2016 17:12:12 +0530 Pirate Praveen wrote: >> I tested the patch, but that was not enough., I still get the same error :( > > I tested using embedded copy of jquery-ui in ruby-jquery-ui-rails and it > is working. So it

Bug#846228: It seems upstream is patching it

https://github.com/joblib/joblib/issues/413 (scroll to the comment by karandesai-96 on 2016-12-04) Paolo signature.asc Description: OpenPGP digital signature

Bug#834918: test failures

This was already observed with version 0.12.7, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753220 which was closed because unreproducible. The problem is also known to upstream (https://github.com/bottlepy/bottle/issues/618, https://github.com/bottlepy/bottle/issues/891), the author of

Bug#839075: confirmed on stretch as of today

I installed python3-jsonschema on clean debian stretch amd64 lxc container and could reproduce the issue installing python3-pkg-resources fixes it: # apt-get install python3-jsonschema ... # jsonschema Traceback (most recent call last): File "/usr/bin/jsonschema", line 5, in from

Bug#783553: numdiff: debian/copyright file is not complete

Hi the issue of switching the numdiff docs to the GPL was raised with upstream 2 years ago, and Ivano preferred to stick to GFDL. The actual issue with the incomplete debian/copyright file is also reported by lintian as warning file-without-copyright-information. Currently 272 packages cause this

Bug#709492: R: Re: Bug#709492: Numdiff doc is non free

All versions of GFDL are not compatible with Debian. Please switch the numdiff docs to the GPL or if you want to stick to GFDL, then skip the optional invariant sections clause. We will then repackage 5.6.2 with the new numdiff doc license. Thanks, Paolo On 23/05/2013 22:23, ivpr...@libero.it

Bug#709492: Numdiff doc is non free

docs/numdiff.info docs/numdiff.txi docs/numdiff.txt are under the gfdl with invariant section and thus non free. Please repackage, or ask upstream to relicence -- == Paolo Greppi +39 320 8960642 paolo.gre...@libpf.com http://www.libpf.com