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
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)
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:
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
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,
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
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:
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: 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
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
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:
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:
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
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)
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: 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
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'
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.
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
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
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
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
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
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
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
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
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": {
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
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
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
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
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
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:
>
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
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
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
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
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
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
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.
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
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=doxygen
In any case all
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
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,
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,
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
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
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 symlink in
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
My understanding is that node-gulp-babel v8 should be used with babel7.
Same goes for node-babel-loader, you need v8 for babel7, but we only have
node-babel-loader 7 in Debian.
If we want babel6 to co-exist with babel7, then we don't want to just update
node-gulp-babel and node-babel-loader to
owner 958780 Paolo Greppi
With node-jest now in the NEW queue, I have started working on this here:
https://salsa.debian.org/js-team/node-yarnpkg/-/tree/jest
I have built jest from https://salsa.debian.org/js-team/node-jest assuming
commit b9255f45c22c030b863e7d42aaf78c207db43478 will be tagged as 24.9.0+ds-2
Hi Douglas,
see below.
Il 30/08/20 13:57, Torrance, Douglas ha scritto:
> Control: tags -1 confirmed
>
> On 8/28/20 3:43 AM, Paolo Greppi wrote:
>> while rebuilding the build dependencies of doxygen with the upcoming doxygen
>> 1.8.19
>> (https://salsa.debian
Also note that if doyxgen parses the correct and full configuration file, it
does not invoke dot
So please discard my initial suggestion to add graphviz as a build-dependency,
that was wrong !
Paolo
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
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
Package: libsord-dev
Version: 0.16.4-1
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
doxygen reports:
warning:
Source: sratom
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
This error comes up:
dh_install: warning: Cannot
Package: libfrobby0
Version: 0.9.1-1
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
This is the error:
sh: 1: dot:
Source: boost1.71
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
This is the error:
doxygen-action
Source: websocketpp
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
I attach the buildlogs:
-
Package: fcml
Version: 1.2.2-1
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
This is the error:
dh_doxygen:
Package: imagemagick
Version: 8:6.9.11.24+dfsg-1+b1
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
This is the
Package: aubio-tools
Version: 0.4.9-4+b1
Severity: normal
Dear Maintainer,
while rebuilding the build dependencies of doxygen with the upcoming doxygen
1.8.19
(https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
this package FTBFS.
This is the error:
sh: 1:
logs.tar.xz
Description: application/xz
Please note that a similar problem has been fixed by the fcml maintainer:
https://bugs.debian.org/969148
Paolo
Hi Stephen,
Il 28/08/20 12:22, Stephen Kitt ha scritto:
> Hi Paolo,
>
>> ...
>
> After building the package with doxygen from experimental, I get
>
> $ find . -name doxygen.\*
> ./docs/doxygen/doxygen.stamp
> ./docs/doxygen/html/doxygen.css
> ./docs/doxygen/html/doxygen.svg
>
Also see https://bugs.debian.org/779970
Paolo
This certainly makes sense and will be easier to digest by ftp-master (although
you'll have two packages in NEW).
For the tarballs, they are here:
https://gitlab.eumetsat.int/open-source/PublicDecompWT/-/tags
(click on the Download icon at the right).
gitlab works well with uscan, see for
See below ...
On Wed, 20 May 2020 18:08:29 +0200 =?UTF-8?Q?Ma=C3=ABl_Nison?=
wrote:
> Hi, I'm Maël, Yarn's lead maintainer.
>
> While cmdtest has a popcon score higher than the yarn package, it's mostly
> because Yarn isn't traditionally installed using the Debian package. For
> historical
The issue has been raised again on the yarnpkg side:
https://bugs.debian.org/940511
Antonio, what is your point of view ?
Do you think we can fix this for the Bookworm release ?
Thanks,
Paolo
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)
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
H, this was already in my todo list.
But it's good to know this release is of value for someone, I'll give it a
higher priority.
So I plan to upload to experimental in a week or so.
Before uploading to unstable I'd like to launch the usual ratt built (see wiki
on salsa) so it will take a bit
Updating that dependency is already in upsream's TODO list
https://github.com/yarnpkg/yarn/issues/6829
.. but they seem to lag on updating dependencies.
I guess it would require fixing against this breaking change:
https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md#-breaking-changes
and
Il 29/06/20 21:27, Akshat Agarwal ha scritto:
> Package: wnpp
> Followup-For: Bug #961337
> Owner: Akshat Agarwal
>
>
> * Package name: deno
> Version : 1.1.2
> Upstream Author : Deno authors
> * URL : https://github.com/denoland/deno
> * License : MIT
>
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]
>>
I have enabled he upstream test suite on salsa, it fails with many of these:
FAIL __tests__/commands/install/integration.js
● Test suite failed to run
Cannot find module 'babel-plugin-transform-inline-imports-commonjs'
Require stack:
...
See:
Package: texlive-latex-base
Version: 2020.20201203-1
Severity: important
Dear Maintainer,
doxygen FTBFS due to a failure to run pdflatex.
See this recent salsa build:
https://salsa.debian.org/debian/doxygen/-/jobs/1213110
The error is:
/usr/bin/pdflatex: Not writing to
Hi Norbert,
Il 04/12/20 23:29, Norbert Preining ha scritto:
Hi Paolo,
/usr/bin/pdflatex: Not writing to
../html/examples/group/latex//group__group2.aux (openout_any = p).
make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:81:
doc/CMakeFiles/doxygen_pdf] Error 1
Is this new?
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:
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
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
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
Hi Hilmar,
Il 09/12/20 23:44, Hilmar Preuße ha scritto:
Control: reassign -1 src:doxygen
...
As explained this issue is probably not related to changed in TL base, hence
I'm reassigning to src:doxygen .
For the other build failures, w/ docbook based documents I've opened Bug#976887
w/
I have run jest in the yarnpkg source tree with:
jest --ci __tests__/
having this jest.config.js to disable failing tests:
module.exports = {
testURL: "http://localhost/;,
testPathIgnorePatterns: [
"/node_modules/",
"/__tests__/index.js",
"/__tests__/integration.js",
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
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
Package: skopeo
Version: 1.2.0+dfsg1-2
Severity: important
Dear Maintainer,
I noticed that if skopeo is installed without buildah, a simple command such as:
skopeo copy docker://busybox oci:busybox
fails with:
FATA[] Error loading trust policy: open /etc/containers/policy.json: no
Il 08/01/21 11:35, Jonas Smedegaard ha scritto:
Quoting Paolo Greppi (2021-01-08 08:46:36)
I guess that's because the bullseye-slim image lacks the manpages.
A Debian install with man pages excluded seems to be an unsupported
system: Whatever hooks applied to do that trick should be extended
Package: node-babel7
Version: 7.12.11+~cs150.141.84-3
Severity: important
Dear Maintainer,
installing node-babel7 on official debian "bullseye-slim" docker image fails
like this:
docker pull debian:bullseye-slim
docker run --rm -it debian:bullseye-slim
apt update && apt install -y
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
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
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
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
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
401 - 500 of 543 matches
Mail list logo
