Hi, I just tried on sid with the attached changes file:
ratt ../texinfo_6.7.0.dfsg.2-5_amd64.changes
2020/04/25 16:41:15 Loading changes file
"../texinfo_6.7.0.dfsg.2-5_amd64.changes"
2020/04/25 16:41:15 - 6 binary packages: info info-dbgsym install-info
install-info-dbgsym texinfo texinf
Hi,
I set up a small example to try to reproduce this problem:
https://salsa.debian.org/paolog-guest/hello-doxygen/-/commits/368577
Note: I set CALL_GRAPH = YES in Doxyfile.
Call graphs are generated fine for me on buster with doxygen 1.8.13-10
(see attachment).
I'll close this bug unless someo
Hi, I just tried using the current master from
https://salsa.debian.org/debian/schroot and doxygen 1.8.13-10 from buster.
This is the log:
doxygen schroot.dox
warning: Tag `XML_SCHEMA' at line 1484 of file `schroot.dox' has become
obsolete.
To avoid this warning please remove this line
Hi.
this bug has been sitting idle for a long time.
Do you still have this problem ?
No one else in Debian project considered this issue worth bumping.
Can you please forward it upstream to:
https://github.com/doxygen/doxygen/issues
and tag this one as forwarded upstream ?
Thanks,
Paolo
Hi
this bug has been sitting idle for a long time.
Do you still have this problem ?
No one else in Debian project considered this issue worth bumping.
Can you please forward it upstream to:
https://github.com/doxygen/doxygen/issues?q=is%3Aissue+buffer+log+is%3Aclosed
and tag this one as forward
Hi,
do you still have this problem ?
Can you provide a minimal example to reproduce the problem ?
Maybe something based on this small project:
https://salsa.debian.org/paolog-guest/hello-doxygen
Thanks,
Paolo
Hi,
currently we depend on qtbase5-dev (>= 5.12.5+dfsg-3):
https://salsa.debian.org/debian/doxygen/-/blob/master/debian/control#L7
This bug report is probably not relevant anymore.
If you agree please close this bug.
Thanks,
Paolo
Hi !
I tried to reproduce your report with doxygen 1.8.13-10 on buster, see this
repo/branch:
https://salsa.debian.org/paolog-guest/hello-doxygen/-/commits/%23869998
But doxygen runs fine.
The generated documentation page for hello.cc is like in the screenshot, the
two example links point to:
Hi,
this bug has been sitting idle for a long time.
Clicking on the links you posted 14 years ago now redirects to vim homepage.
I have found here a repository of vim scripts but there seems to be several
doxygen plugins: https://github.com/vim-scripts?tab=repositories&q=doxygen
In any case all
Hi,
this bug has been sitting idle for a long time.
doxygen-latex is a pure dependency package.
It installs pretty much nothing, it just pulls in the right dependencies,
among them is doxygen itself, which it makes sure is on par or more recent than
its own version.
So it is similar to python3.7
owser because I have no time to test it (for example in laminar
UI).
meskio, can you test laminar with the new build ? Thanks
Paolo
Il 24/03/20 17:38, meskio ha scritto:
> Hello Paolo,
>
> Quoting Paolo Greppi (2019-10-31 18:39:16)
>> Hi Dmitry, I have fixed the dangling symlin
see: https://github.com/yarnpkg/yarn/issues/1390
upstream-provided package correctly reports the error:
docker run --rm -it debian:buster-slim /bin/bash
apt update && apt install -y curl gnupg2
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
echo "deb https://dl.yarnpkg.com/deb
1. hanging:
docker run --rm -it debian:buster-slim /bin/bash
apt update
apt install -y --no-install-recommends yarnpkg
yarnpkg add --verbose highlight.js
output:
yarn add v1.13.0
verbose 0.668 Checking for configuration file "/.npmrc".
verbose 0.668 Checking for configuration file "/usr
Package: yarnpkg
Version: 1.21.1-1
Severity: normal
if ca-certificates is not installed, yarnpkg will hang or quit abruptly without
any error message / error status.
To reproduce:
sudo apt install yarnpkg
sudo apt remove ca-certificates
cd $(mktemp -d)
cat > package.json
{
"dependencies": {
Hi !
did you assign the SMTP server for each of the accounts ?
In Edit->Account settings, in the left pane, click on the account name then
choose the SMTP server you want to use from the "Outgoing Server (SMTP)"
pulldown list.
(see screenshot)
Paolo
Il 18/02/20 08:32, Nicola ha scritto:
> P
Package: wnpp
Severity: wishlist
* Package name: whalebird
Version : 3.1.0
Upstream Author : AkiraFukushima
* URL : https://whalebird.org/
* License : MIT
Programming Lang: JavaScript
Description : A Mastodon and Pleroma client for the desktop
Whalebir
Upstream has moved the bug tracker to github, and the issue is now closed:
https://github.com/ledger/ledger/issues/1203
The commit is merged in master on 3 Dec 2019:
https://github.com/ledger/ledger/commit/12a74c66c6656bbf6a89bfae83b76e3df37d9199
but not yer released (v3.1.3 dates to 31 Mar 2019)
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 late
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 d
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 depe
Package: gulp
Version: 4.0.2-4
Severity: normal
Dear Maintainer,
while building yarnpkg on experimental, it fails while executing the gulp
command:
...
gulp build
[18:34:23] Local gulp not found in
/builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.21.1
[18:34:23] Try running: npm insta
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
Hi Samuel,
thanks for the report.
I have incorporated your patch in the WIP next version 1.8.16-3 here:
https://salsa.debian.org/debian/doxygen
Paolo
Il 30/12/19 11:36, Xavier ha scritto:
> ...
> I think that npm is needed when a package has to be build locally.
> That's why a "recommends" should be enough
>
Xavier, I have enabled salsa CI on node-es6-iterator repo and fixed it to run
tests with yarnpkg so that the dependency on npm can be dr
Hi Xavier, I did this on sid:
sudo apt install yarnpkg
sudo apt remove npm
sudo apt autoremove
git clone https://github.com/yarnpkg/yarn
cd yarn
rm -rf node_modules
yarnpkg
This works fine and installs all of yarnpkg dependencies in node_modules dir.
Can you provide a use case where it fails ?
I realized I had already reported in the past that doxygen may discard the exit
codes of other commands it invokes.
I have added a note about reporting this error here:
https://github.com/doxygen/doxygen/issues/6653#issuecomment-568584189
Paolo
This is fixed by node-vinyl-fs 3.0.3-3 from experimental as that version is
compatible with glob-stream 6.x:
https://github.com/gulpjs/vinyl-fs/blob/7e223749ee2ada1abd3b2fb326178d8ad8f39f2c/package.json#L30
I tried building yarnpkg with node-micromatch, gulp and node-glob-stream from
experimenta
Package: node-vinyl-fs
Version: 2.4.4-1
Severity: important
This package causes yarnpkg to FTBFS since node-glob-stream was updated.
A sample build log is:
https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/468304
The relevant part is:
...
gulp build
[12:14:44] Local gulp not found in
/builds
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 6.1
Hi ! and thanks for reporting.
I have reproduced it by building libvigraimpex from this branch:
https://salsa.debian.org/ametzler/libvigraimpex/tree/tmp-ametzler-python3
The error is non-fatal (the build completes successfully) but I can see the
same ghostscript error in the log.
BTW, don't you
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
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 with
Hi and thanks. I have incorporated your fix as follows:
https://salsa.debian.org/debian/doxygen/commit/e4a00bde1d8b864d4588554c5c21ae43b4519dee
I plan to release to unstable shortly.
Paolo
Package: ftp.debian.org
Severity: normal
This package has low popcon (10) and is only used by node-command-join (see
https://bugs.debian.org/945302).
If we ever need it again, it can be embedded (~ 200 LOC).
The maintainer is the Debian Javascript Maintainers team of which I am part of.
My inte
Package: ftp.debian.org
Severity: normal
This package has low popcon (6) and is not used anywhere in Debian.
When the ITP (https://bugs.debian.org/846218) was filed it was required for
yarnpkg, but they dropped the dependency:
https://github.com/yarnpkg/yarn/pull/3079
Also duck reports that the
Package: ftp.debian.org
Severity: normal
This package has low popcon (7) and is not used anywhere in Debian.
The maintainer is the Debian Javascript Maintainers team of which I am part of.
My intention to remove it was announced in the team mailing list about 3 weeks
ago:
https://alioth-lists.d
Package: ftp.debian.org
Severity: normal
This package has low popcon (4) and was a build-dep of node-commander, but that
dependency was removed with version 2.11.0:
https://github.com/tj/commander.js/blob/master/CHANGELOG.md#2110--2017-07-03
Also the upstream repo has last been updated 5 years a
Package: ftp.debian.org
Severity: normal
This package has low popcon (7) and is currently not used.
According to the ITP (https://bugs.debian.org/849255) it was required for lerna
which was a dependency of babel-cli.
But in the meantime lerna is stuck at RFP (https://bugs.debian.org/849258) and
Package: ftp.debian.org
Severity: normal
This package has low popcon (6) and is currently not used.
According to the ITP (https://bugs.debian.org/849254) it was required for lerna
which was a dependency of babel-cli.
But in the meantime lerna is stuck at RFP (https://bugs.debian.org/849258) and
according to this commit:
https://github.com/epam/Indigo/commit/292835731d4638d3a25bce2784c961dd2ebc8b67
upstream supports python3 since 1.2.2beta-r37 so it should be possible to
update this package to python3
Paolo
Package: indigo
Severity: normal
Dear Maintainer,
Upstream homepage link in d/control is broken:
http://ggasoftware.com/opensource/indigo
Updated links:
https://lifescience.opensource.epam.com/download/indigo/index.html
https://github.com/epam/Indigo
Paolo
-- System Information:
Debian Release
Hi Sylvestre and many thanks for the prompt response, see below.
On 02/11/19 11:59, Sylvestre Ledru wrote:
> Hello,
>
>
> Le 02/11/2019 à 11:52, Paolo Greppi a écrit :
>> Package: llvm-9
>> Version: 1:9.0.0-3
>> Severity: normal
> [...]
>> This does not se
Package: llvm-9
Version: 1:9.0.0-3
Severity: normal
Dear Maintainer,
when I tried upgrading to llvm-9 to build doxygen, it started to complain of
missing /usr/lib/x86_64-linux-gnu/libz3.so
This is surprising because we never needed this:
https://packages.debian.org/sid/libz3-4
Now apt-cache rde
I have "updated" the patch here:
https://salsa.debian.org/debian/doxygen/blob/master/debian/patches/doxygen-jquery.patch
like this:
--- doxygen.orig/src/htmlgen.cpp
+++ doxygen/src/htmlgen.cpp
@@ -775,7 +775,10 @@ void HtmlGenerator::init()
{
mgr.copyResourceAs("fixed_tabs.css",dname,"tabs
Hi Gard, see below
On 25/10/19 11:45, Gard Spreemann wrote:
> Hi,
>
> Paolo Greppi writes:
>
>> The 10 remaining packages all fail with latex-related errors.
>> Unfortunately I know nothing about latex so I cant' help with those.
>> But I filed bu
On Sat, 14 Sep 2019 09:53:18 + Dmitry Bogatov wrote:
> ...
> It does not build for me. Neither it builds on Salsa CI (I added
> debian/.gitlab-ci.yml on branch `wip').
>
> https://salsa.debian.org/js-team/vue-router.js/-/jobs/321533
> --
> Note, that I send and fetch email in batch, once in
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
Com
Source: doxygen
Severity: normal
Originally reported by Hunter Laux:
https://bugs.launchpad.net/ubuntu/+source/doxygen/+bug/1631169
The patch debian/patches/doxygen-jquery.patch is misapplied.
It looks like the upstream file src/htmlgen.cpp was modified by upstream
between their tags `Release_
Package: libppl-doc
Version: 1:1.2-7
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
pdflatex refman
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian)
(preloaded format=pdflatex)
restric
Package: openms-doc
Version: 2.4.0-real-1
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]pdfTeX warning (ext4): de
stination with the same identifier (na
Package: liblapack-doc
Version: 3.8.0-7
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
make[2]: Leaving directory '/<>'
# Remove directory reference files, because they include local build pathnames
# (but d
Package: fltk1.3-doc
Version: 1.3.4-9
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
/usr/bin/doxygen Doxybook
warning: Tag 'PERL_PATH' at line 1309 of file 'Doxybook' has become obsolete.
To avoid
Package: libccfits-doc
Version: 2.5+dfsg-1
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
/usr/bin/make -C latex
make[2]: Entering directory '/<>/latex'
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *
Package: sdformat-doc
Version: 6.2.0+dfsg-1
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
! LaTeX Error: File `listofitems.sty' not found.
The package texlive-plain-generic contains this file:
/usr/share/t
Package: librostlab-doc
Version: 1.0.20-8
Severity: normal
Dear Maintainer,
This package failed to build with doxygen 1.8.16-1~exp3 from experimental.
It FTBFS with this error:
! LaTeX Error: File `listofitems.sty' not found.
The package texlive-plain-generic contains this file:
/usr/share/tex
Same error as with doxygen 1.8.15.
The package texlive-plain-generic contains this file:
/usr/share/texlive/texmf-dist/tex/generic/listofitems/listofitems.sty
Paolo
Same error as with doxygen 1.8.15.
The package texlive-plain-generic contains this file:
/usr/share/texlive/texmf-dist/tex/generic/listofitems/listofitems.sty
Paolo
The error changes though:
! Undefined control sequence.
l.913 ...uotesingle{}} elements stored in $ N\text
{'}/B $ blocks (In practic...
?
! Emergency stop.
l.913 ...uotesingle{}} elements stored in $ N\text
Package: siscone-doc-html
Version: 2.0.6-2
Severity: normal
Dear Maintainer,
after installing siscone-doc-html I open with firefox:
file:///usr/share/doc/siscone-doc-html/html/index.html
then click on "Developper documentation" link and get a broken link at:
file:///usr/share/doc/siscone-doc-htm
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' is
Actually a similar patch is already included in the 1.8.16-1~exp3 package:
https://salsa.debian.org/debian/doxygen/blob/master/debian/patches/reproducible_year.diff
But thanks for forwarding upstream !
Paolo
... everything applies to buster:
apt-cache policy pkg-js-tools
pkg-js-tools:
Installato: 0.9.16~bpo10+1
...
add-node-component --version
0.2
P.
with:
cd `mktemp -d`
salsa checkout node-is-directory --group js-team
cd node-is-directory/
sudo apt install libjson-xs-perl
add-node-component rollup-plugin-node-builtins
Thread 1 terminated abnormally: Malformed upstream registry: JSON text must be
an object or array (but found number, string,
To reproduce:
cd `mktemp -d`
git clone https://salsa.debian.org/js-team/node-yarnpkg
cd node-yarnpkg
git fetch origin pristine-tar
git checkout pristine-tar
git fetch origin upstream
git checkout upstream
git checkout master
gbp import-orig --uscan --pristine-tar
at the end of the process, the ma
I have imported the upstream patch in a new version 1.13.0-3:
https://salsa.debian.org/js-team/node-yarnpkg/commit/6808cd918e8c12182e14666c715bb1d372d82449/pipelines
I have checked that it now uses https even if http links are present in
yarn.lock as follows:
mkdir /tmp/qw
cd /tmp/qw
yarnpkg add
one way to address this is importing this as a debian/patch:
https://github.com/yarnpkg/yarn/commit/2f08a7405cc3f6fe47c30293050bb0ac94850932
Paolo
Hi,
it now builds on sid:
https://salsa.debian.org/js-team/node-jest/pipelines/73174
but there's still a lot to do:
1) turn on tests of course (it tests itself)
2) this lintian message is worth investigating:
P: node-jest-cli: image-file-in-usr-lib
usr/lib/nodejs/jest-cli/build/assets/jest_log
Package: yarnpkg
Version: 1.13.0-1
Severity: normal
the package has autopkgtest enabled but there no test is run during the build
it would be safer to enable the upstream test suite, but this requires jest;
I have given it a try using jest 22.4.4 installed from a separate node_modules
dir and go
Package: yarnpkg
Version: 1.13.0-1
Severity: normal
please implement bash autocompletion for yarnpkg as we have for example in npm.
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel:
Hi Melvin,
thanks for raising this issue again.
We can't just symlink yarn to yarnpkg or rename yarnpkg -> yarn because there's
a already a yarn binary in Debian, see:
https://packages.debian.org/search?suite=sid§ion=all&arch=any&searchon=contents&keywords=yarn
This was extensively debated in th
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
I rebuilt yarnpkg 1.13 using webpack 4.7 from experimental and it worked fine.
I manually tested the resulting package and its yarnpkg executable seems to
work.
From visual inspection the webpack config that we are using seems compliant
with the requirements of webpack 4:
https://salsa.debian.o
Package: node-mixin-deep
Version: 1.1.3-3
Severity: important
Dear Maintainer,
node-mixin-deep 1.1.3-3 is affected by a prototype pollution vulnerability:
https://snyk.io/vuln/SNYK-JS-MIXINDEEP-450212
https://github.com/jonschlinkert/mixin-deep/issues/6
Please upgrade to either 1.3.2 or 2.0.1.
nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new Date(2018,
0, 1)}]));'
TZ='UTC' nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new
Date(2018, 0, 1)}]));'
TZ='EST' nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new
Date(2018, 0, 1)}]));'
T
I have the same.
This upstream bug seems matching:
https://bugs.kde.org/show_bug.cgi?id=407390
but it needs confirmation.
Paolo
I just filed a couple of RFPs for electron apps and immediately added this one
as a blocker:
https://bugs.debian.org/842420
So yes there are some trending messaging apps and code editors built with
electron !
Packaging it would be a huge task also because it is a mixed-language project.
slocco
Package: wnpp
Severity: wishlist
* Package name: ssb-patchwork
Version : 3.13.0
Upstream Author : Secure Scuttlebutt Consortium
* URL : https://github.com/ssbc/patchwork
* License : AGPL-3.0
Programming Lang: JavaScript
Description : A decentralized mes
See: https://medium.com/@wolovim/mist-migration-patterns-6bcf066ac383
Quote: "Mist Browser and Ethereum Wallet are no longer supported"
See: https://medium.com/@avsa/sunsetting-mist-da21c8e943d2
Quote: "Mist, the browser has outlived it’s usefulness: the ecosystem has matured so
much that now th
Package: wnpp
Severity: wishlist
* Package name: beaker
Version : 0.8.8
Upstream Author : Blue Link Labs
* URL : https://github.com/beakerbrowser/beaker
* License : MIT
Programming Lang: JavaScript
Description : Peer-to-peer web browser
Beaker is an ex
These are updated links to the fork mentioned by the submitter:
https://www.c-amie.co.uk/software/analog/
https://github.com/c-amie/analog-ce
It looks like the c-amie fork has diverged, from a quick diff it is missing
some ipv6 stuff we have in our version ..
Paolo
On 10/06/19 20:03, Paolo Greppi wrote:
...
Tomorrow I'll test the generated file inside laminar. If that works this is an
acceptable solution.
The last bit is to move this config change to debian/rollup-umd.js so that it
does not impact all builds..
Paolo
I tested with the non-min
On 11/06/19 08:03, Pirate Praveen wrote:
I think rollup-plugin-commonjs will also work without extra options, see
node-d3-fetch.
rollup-plugin-commonjs is already there in the upstream rollup config:
https://salsa.debian.org/js-team/vue-router.js/blob/master/build/configs.js#L4
P.
If I build manually the UMD version using the same command as in debian/rules:
NODE_PATH=debian/node_modules/ rollup -m -c debian/rollup-umd.js
I get this:
/home/paolog/Sviluppo/debian/vue-router.js/src/index.js → dist/vue-router.js...
(!) Unresolved dependencies
https://github.com/rollup/rollu
Hi, nice one !
It is reproducible when I use the laminar debs built from the WIP package here:
https://salsa.debian.org/debian/laminar
after these fixes:
https://bugs.debian.org/919181#27
Once started, the laminar service dashboard should be reachable from
localhost:8080 but it fails to load.
I
Hi, thanks for working on this !
I set out to try and reproduce 927254, using the laminar debs built from the
WIP package here:
https://salsa.debian.org/debian/laminar
But after apt install laminar the service would not start at first:
Jun 10 12:39:22 laminar systemd[1]: Started Laminar continu
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 readabl
Hi Hubert,
One cause for the issue you are having could be globally installed (or
otherwise reachable via your module search path) node modules that conflict
with those in our packaged yarnpkg.
Is NODE_PATH set ?
If you try:
npm root -g
it should return /usr/local/lib/node_modules
And:
ls
$ node -v
v10.15.2
$ yarnpkg -v
1.13.0
$ cd /tmp
$ mkdir foo
$ cd foo
$ yarnpkg init
yarn init v1.13.0
question name (foo):
question version (1.0.0):
question description:
question entry point (index.js):
question repository url:
question author:
question license (MIT):
question private:
success S
Source: mxml
Severity: normal
Dear Maintainer,
the VCS link reported in debian/control file:
https://salsa.debian.org/mckinstry/mxml.git
is broken. Please reinstate it.
Paolo
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x
Quick research:
https://www.npmjs.com/advisories/612
node-deep-extend popcon = ~1900
apt-cache rdepends node-deep-extend
node-deep-extend
Reverse Depends:
node-rc
the watch file for node-rc is not picking up new releases because upstream uses
the commit message to tag them instead of a real
Hi Antoine,
and thanks for the good and well documented report.
I agree that for consistency doxygen search should work with the PHP version we
ship in any given
Debian release.
And this issue also applies to buster as it will ship doxygen 1.8.13 and php
7.3.
Fixing it for buster is higher pr
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
/tmp/doxygen-1.8.13/bu
I ran a new full ratt job after texlive-base 2018.20190131-2 fixed #920459.
Of 732 packages built on amd64, 52 fail, but of those:
- 33 "maybe unrelated to new changes"
- 10 failed because of unsatisfied build dependencies (texlive-extra-utils,
texlive-latex-extra, texlive-science, texlive-plain
I got the same error on amd64 while running yarnpkg in root of vscode source:
git clone https://github.com/Microsoft/vscode
cd vscode
yarnpkg
...
[4/4] Building fresh packages...
[1/14] ⠠ gc-signals
[2/14] ⠠ keytar
[3/14] ⠠ native-is-elevated
[4/14] ⠐ native-keymap
error /root/vscode/node_modules
I looked at the status of this on buster:
uname -a
Linux localhost.localdomain 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17)
x86_64 GNU/Linux
and the issue still can be reproduced (in the sense that telnet.netkit network
access will not be blocked after enforcing the rule).
Except it is
I have given signal-desktop a first look.
In terms of dependencies, apart from electron (ehm...) this is what I found:
- to be updated:
1. node-chalk: 2.3.0 -> 2.4.1
2. node-espree: 3.5.1 -> 3.5.4
3. node-filesize: 3.5.11 -> 3.6.1
4. node-got: 7.1.0 -> 8.2.0
5. node-he: 1.1.1 -> 1.2.0
Package: node-react
Severity: normal
Dear Maintainer,
The react-dom node module:
https://yarnpkg.com/en/package/react-dom
has the same upstream as our existing source node-react.
I suppose it can be build from it.
node-react-dom is a dependency of signal-desktop:
https://bugs.debian.org/842943
Package: node-sqlite3
Version: 4.0.6+ds1-2
Severity: normal
Please build nodes-qlite3 with support for sqlcipher:
https://github.com/mapbox/node-sqlite3#building-for-sqlcipher
This is required to package signal-desktop (https://bugs.debian.org/842943)
It would allow us to simply depend on node-s
Hi Christof,
this worked for me:
cat /etc/default/lxc-net
USE_LXC_BRIDGE="true"
cat /etc/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
and don't forget to start the lxc-net service before star
Hi Enrico,
On 21/02/19 09:31, Enrico Zini wrote:
...
If I make one of those paths accessible on the web and include bootstrap
with something like:
Then I see the browser make this failed request on my HTTP server:
404 GET /static/bootstrap4/js/dist/js/bootstrap.js.map
...
it works fo
101 - 200 of 553 matches
Mail list logo
