Hi, I have tripped onto this while following blindly the automatic
sbuild setup using sbuild-debian-developer-setup described here:
https://wiki.debian.org/sbuild#Automatic_setup_using_sbuild-debian-developer-setup
Alberto's workaround (sudo apt install -t bookworm-backports
debootstrap)
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
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
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
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.
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.
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.
Hi Andreas!
Il 11/07/23 22:27, Andreas Hasenack ha scritto:
So I took a stab at backporting the upstream patches, and there are many:
$ grep ^commit debian/patches/doc-build-with-newer-cairo-*.patch
debian/patches/doc-build-with-newer-cairo-1.patch:commit
Hi! sorry for the long delay, at last I'm looking at incorporating your
patch. It's now WIP here:
https://salsa.debian.org/debian/doxygen
Before I upload it to unstable, I was wandering:
1. what would be the easiest way to turn this on only for 32-bit builds?
2. what side effects can we expect?
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
Package: jenkins.debian.org
X-Debbugs-Cc: paolo.gre...@libpf.com
Severity: normal
Hi, I am looking at the reproducible build results for doxygen:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/doxygen.html
If I remember well, previously it was possible to download the build
Package: sddm
X-Debbugs-Cc: paolo.gre...@libpf.com
Version: 0.19.0-3
Severity: important
About 90% of the times after a fresh reboot, sddm shows a black page
with mouse pointer instead of the login screen.
The systemd sddm service is up and running. If I restart it on tty 1,
the login screen
Hi! thanks for the quick reaction.
Il 22/07/22 18:01, Sebastiaan Couwenberg ha scritto:
Control: tags -1 upstream
Control: forwarded -1 https://github.com/libgeos/geos/issues/654
On 7/22/22 17:37, Paolo Greppi wrote:
I am about to upload the current version of doxygen, before doing that
I ran
Package: liblog4c3
Version: 1.2.4-2
Severity: important
File: /usr/share/doc/liblog4c3/copyright
Tags: ftbfs
X-Debbugs-Cc: paolo.gre...@libpf.com
Hello,
I am about to upload the current version of doxygen, before doing that I
ran a quick scan of ~500 build-deps
Package: bamtools
Version: 2.5.1+dfsg-10+b1
Severity: important
Tags: ftbfs
X-Debbugs-Cc: paolo.gre...@libpf.com
Hello,
I am about to upload the current version of doxygen, before doing that I
run a quick scan of build-deps of doxygen
I installed the package above and when I tried the archivebox command I
got the same error about the missing atomicwrites module.
This is easy to fix by adding
lib/python3.9/site-packages/atomicwrites/__init__.py from
https://pypi.org/project/atomicwrites/ 1.4.1 as
Hi! and thanks for your efforts to package archivebox.
I have picked it up from there and tried to build the current version
(0.6.2). For that I have refreshed the patches, here is a MR:
https://salsa.debian.org/debian/archivebox/-/merge_requests/1
Feel free to pick up whatever you need from
Thanks for your bug report. This is caused by doxygen not reporting dot
failures, which is tracked at bug #818379.
Paolo
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
Hi! and thanks for reporting.
I am in the process of packaging doxygen 1.9.4 and this issue seems to
be fixed in that version.
To test, I did this twice:
cd `mktemp -d`
git clone https://github.com/BYVoid/OpenCC
cd OpenCC/
cd doc
# no need to run cmake etc. just quickly
I reproduced with the attached minimal example and no warning is printed.
Upstream issue is also closed.
Will now close.
P.
test.tar.xz
Description: application/xz
I reproduced with the attached minimal example and no warning is printed.
Upstream issue is also closed.
Will now close.
P.
test.tar.xz
Description: application/xz
Since some time doxygen has a WARN_AS_ERROR config option:
https://doxygen.nl/manual/config.html#cfg_warn_as_error
Since version 1.9.1 or 1.9.2 if that is set to YES, graphviz's dot is
absent but HAVE_DOT=YES is set, doxygen will stop and exit with status
of 1 (upstream choose this opt-in way
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.
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
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
I stumbled upon this thread related to packaging corepack for gentoo:
https://github.com/nodejs/corepack/issues/76
We now have node 16 in experimental, but our package does not bundle
corepack (as upstream does):
https://packages.debian.org/experimental/amd64/nodejs/filelist
I propose that
Il 11/12/21 18:29, Brian Thompson ha scritto:
Package: yarnpkg
Severity: important
Dear Maintainer,
After install yarnpkg for the first time and running `yarnpkg --version`, I
got the following error:
Error: Cannot find module '@babel/runtime/helpers/interopRequireWildcard'
I expected the
See https://bugs.debian.org/985857
Paolo
Hi,
Il 27/07/21 08:51, Daniel Baumann ha scritto:
Package: twitter-bootstrap4
Hi,
thanks a lot for maintaining bootstrap in Debian.
Do you already have an ETA for bootstrap 5 (probably a new package in
Debian I guess)?
Regards,
Daniel
thanks for your request but twitter-bootstrap4 is no
Control: noowner -1
Control: tags -1 - pending
Trying to make the upstream test suite, designed for jest 22, work with our
jest 26 is tricky.
Also some things defy intuition, i.e. I patch here:
Package: tracker.debian.org
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org
Severity: important
For yarnpkg: https://tracker.debian.org/pkg/node-yarnpkg
tracker.debian.org reports:
uscan had problems while searching for a new upstream version:
unrecognized option ctype=nodejs
Dear Xavier,
Il 27/01/21 06:30, Xavier ha scritto:
Le 27/01/2021 à 00:14, Paolo Greppi a écrit :
I fixed the error:
Cannot find module 'babel-preset-env'
but I am not sure if the fix is 100% right.
Now I get:
TypeError: Cannot read property 'mkdir' of undefined
5
I fixed the error:
Cannot find module 'babel-preset-env'
but I am not sure if the fix is 100% right.
Now I get:
TypeError: Cannot read property 'mkdir' of undefined
5 | export default function(filename?: string): Promise {
6 | return new Promise((resolve,
Package: ftp.debian.org
Severity: normal
This package has low popcon (1), and according to upstream:
https://github.com/i18next/i18next-xhr-backend
it is "[deprecated] can be replaced with i18next-http-backend".
The latter we already have in Debian:
Hi, I think I fixed the error:
Cannot find module 'babel-plugin-transform-inline-imports-commonjs'
with this commit:
https://salsa.debian.org/js-team/node-yarnpkg/-/commit/d055e01b6d1a7f6fad6df2ccdf6d0f7d01ddcbc2
but the tests still fail, all with this new error:
FAIL
I tried using the docker "official image" for node:
docker pull node
docker run -it --rm node bash
mkdir -p test/foo
cd test
yes '' | yarn init
yarn add file:foo
yields:
yarn add file:foo
yarn add v1.22.5
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching
With this WIP patch:
https://salsa.debian.org/js-team/node-yarnpkg/-/blob/master/debian/patches/18-uuid.diff
I can do:
rm -rf /tmp/test
mkdir -p /tmp/test/foo
cd /tmp/test
yes '' | yarn init
cd foo
yes '' | yarn init
cd ..
yarn add file:foo
and get:
yarn
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
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
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
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
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 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
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 02/01/21 02:51, Scott Talbert ha scritto:
On Sat, 2 Jan 2021, Paolo Greppi wrote:
The ext/wxWidgets/docs/doxygen/out/xml dir produced with doxygen 1.8.20 is 50
MB and contains 1812 files.
The ext/wxWidgets/docs/doxygen/out/xml dir produced with doxygen 1.9.0 is 42 MB
and contains 1583
Source: wxpython4.0
Severity: important
Dear Maintainer,
in a partial rebuild of the doxygen build dependencies against 1.9.0 from
experimental:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.0-1_amd64-partial
this package failed to build with this error:
Finished command:
libvigraimpex_1.11.1+dfsg-7.xz
Description: application/xz
Source: libvigraimpex
Severity: important
Dear Maintainer,
in a partial rebuild of the doxygen build dependencies against 1.9.0 from
experimental:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.0-1_amd64-partial
this package failed to build with this error:
Postprocessing
Source: breathe
Severity: important
Dear Maintainer,
in a partial rebuild of the doxygen build dependencies against 1.9.0 from
experimental:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.0-1_amd64-partial
this package failed to build with this error:
AssertionError
>
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:
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 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
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 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/
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:
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?
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
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
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
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
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)
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
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
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
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
>
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
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:
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
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
logs.tar.xz
Description: application/xz
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:
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: 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:
-
Also see https://bugs.debian.org/779970
Paolo
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]
>>
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
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
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
>
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
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
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
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
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
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
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, 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.
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,
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=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
1 - 100 of 543 matches
Mail list logo
