Bug#919413: latest ratt job
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-generic or texlive-bibtex-extra) - only 9 show interesting errors For details see: https://salsa.debian.org/paolog-guest/doxygen/wikis/ratt6 Paolo
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 not followed. Fortunately, jquery is available as a Debian package. We had a similar issue with libmojolicious-perl. This package now: - removes jquery from source tarball [1] using debian/copyright Files-excluded parameter - depends on libjs-jquery - provides a symlink to Debian's query instead of the regular jquery file using debian/libmojolicious-perl.links file [2] HTH [1] https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/copyright#L7 [2] https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/libmojolicious-perl.links I 'm afraid we will not be able to avoid embedding jquery in doxygen, because it makes a weird use of it. The matter has been nicely put down by the former maintaners, see: https://salsa.debian.org/paolog-guest/doxygen/blob/master/debian/README.jquery Paolo
Bug#919413: ratt job complete
The latest full ratt job on amd64 is complete: https://salsa.debian.org/paolog-guest/doxygen/wikis/ratt4 In synthesis, of 730 build deps of doxygen 59 failed but 51 "maybe unrelated to new changes" and only 8 seem due to the new doxygen version. I think no new issues appeared. Paolo
Bug#919413: fix and status update
Following a suggestion by sthibault, I added texlive-plain-generic as build dep for doxygen-latex. With that change, I did a partial ratt job, focusing on the 9 build-dependencies of doxygen mentioned above. Details here: https://salsa.debian.org/paolog-guest/doxygen/wikis/ratt3 The new version fixed hwloc and starpu. For the remaining 7, they also fail without doxygen 1.8.15, so the FTBFS is "maybe unrelated to new changes". I have just launched a new full ratt job: https://salsa.debian.org/paolog-guest/doxygen/wikis/ratt4 P.
Bug#919413: Bug#921293: hwloc: FTBFS with upcoming doxygen 1.8.15
Il 04/02/19 09:15, Samuel Thibault ha scritto: > ... > Perhaps we just happen to use some doxygen commands which require this. > You can simply make doxygen-latex depend on the package that provides > listofitems.sty, texlive-plain-generic. > > Samuel good point ! doxygen-latex depends on texlive-latex-extra which only recommends texlive-plain-generic I'll make that change, rebuild all nine packages and post the results to bug 919413 Paolo
Bug#919413: here are the 9 bugs I created
BTW, I retried uhd and actually it does not fail. So I created 9 new bugs: hwloc: https://bugs.debian.org/921293 fltk1.3: https://bugs.debian.org/921294 wcslib: https://bugs.debian.org/921295 ccfits: https://bugs.debian.org/921296 qevercloud: https://bugs.debian.org/921297 libstxxl: https://bugs.debian.org/921298 caffe: https://bugs.debian.org/921299 frobby: https://bugs.debian.org/921300 starpu: https://bugs.debian.org/921301 Paolo
Bug#919413: ready for unstable
I ran ratt, 31 of 729 packages genuinely FTBFS due to doxygen 1.8.15. More details here: https://salsa.debian.org/paolog-guest/doxygen/wikis/ratt-job-for-doxygen-1.8.15 All these failures are related to an issue with texlive-base 2018.20190126-1: https://bugs.debian.org/920621 and ultimately due to the latex tabu extension: https://github.com/tabu-fixed/tabu/issues/1 https://github.com/doxygen/doxygen/issues/6769 With the help of Hilmar Preuße I patched doxygen so that is builds, and (almost always) generates tex files that are parseable by pdflatex from texlive-base 2018.20190126-1. This at the cost of producing ugly-looking PDFs, while we wait for a properly fixed tabu. With those fixes 20 of the failing packages above build fine. toulbar2 now FTBFS due to new latex even without new doxygen. We are left with 10 (in order of decreasing popcon): hwloc 13658 fltk1.3 12796 uhd 1119 wcslib 577 ccfits 526 qevercloud 285 libstxxl229 caffe 171 frobby 126 starpu 11 I will now file bugs with these 10 packages so that the maintainers are aware of the issue. The latest version of the package, ready for the upload to unstable, is here: https://salsa.debian.org/paolog-guest/doxygen Paolo
Bug#919413: RFS: doxygen/1.8.15-1~exp1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor to upload to experimental the version of doxygen that was released by upstream last month. I would like to maintain it with gbp, and I have created a git repo for that: https://salsa.debian.org/paolog-guest/doxygen To access further information about this package, please visit the following URL: https://mentors.debian.net/package/doxygen Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/doxygen/doxygen_1.8.15-1~exp1.dsc More information about doxygen can be obtained from https://www.example.com. Changes since the last upload: * doxygen 1.8.15 release. * Do not produce "Directory Reference" man pages. Closes: #742871. * Bump debhelper compat. * New maintainer. Closes: #888580. * Update homepage. * Fix lintian W binary-without-manpagefix. * Fix lintian P file-contains-trailing-whitespace. * Move repo to salsa. * Bump standard version * Disable LLVM support on alpha. Closes: #916532. * Switch to llvm-toolchain-7. Closes #912799. * Make the output of $year reproducible. Closes: #863054 -- Paolo Greppi Tue, 15 Jan 2019 18:17:17 +0100 Regards, Paolo Greppi
Bug#895812: Fwd: RFS: json-editor.js/0.7.28+ds-1 [ITP]
Ho Joel, thanks for your contribution ! Looking at your work there are a couple of things that can be improved: 1. I see that you set the Maintainer = Debian Javascript Maintainers. In that team normally we use git repos to keep track of the packaging; more precisely we use the git-buildpackage workflow. 2. All new repos nowadays are on salsa (https://salsa.debian.org), you can easily set up a guest account there with the self service webfrontend. 3. If you wish to maintain this package within this team, I'd suggest that you join the team ! Just drop a mail to the mailing list committing to follow the team policies, and indicate your salsa alias. One of the js-team group owners can then add you to the group on salsa. 4. The Debian Javascript Maintainers keeps all repos in the js-team group on salsa (https://salsa.debian.org/js-team); after moving your repo there you can update the Vcs-Browser and Vcs-Git fields in debian/control. 5. I tried to build your package, at the end lintian complains about: - co-maintained-package-with-no-vcs-fields (see previous point) - out-of-date-standards-version 4.1.1 (current is 4.1.4) - insecure-copyright-format-uri http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ - package-uses-old-debhelper-compat-version 10 (current is 11) - json-editor.js source: source-contains-prebuilt-javascript-object dist/jsoneditor.min.js see last point 6. This library comes with examples, so you could install those too. You can patch the examples so that they load the jsoneditor.js file from the default location /javascript/... which should point to /usr/share/javascript/... assuming apache2 alias from the javascript-common package is enabled ... 7. You are repackaging to exclude certain examples because they "link to libraries in external CDNs"; Sctually it should be possible to patch them to use the system installed libraries (I checked examples/select2.html, we do have jquery and libselect2) see: https://salsa.debian.org/js-team/vue.js/blob/master/debian/patches/00-examples.diff (those additional libraries needed to enjoy the examples could be recommended by the package...) 8. It would be super cool if we could enable tests ... but I am not sure how (selenium ?) Tests can be run during package build and in the debian CI infrastructure which helps improve the quality of debian and to avoid mishaps when dependencies are updated; 9. You must repackage for sure: to exclude dist. Else the package will certainly be rejected by the ftp-masters: the dist directory should be re-created from source during the debian build. Unfortunately debhelper does not yet support building with grunt out of the box (https://bugs.debian.org/845043) so you have to manually add that to debian/rules, see: https://codesearch.debian.net/search?q=grunt+build+path%3Adebian%2Frules https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt Paolo
