Processed: Bug#911620 in package dpkg marked as pending
Processing control commands:
> tag 911620 pending
Bug #911620 {Done: Guillem Jover } [dpkg]
shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster
Added tag(s) pending.
--
911620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#911620: in package dpkg marked as pending
Control: tag 911620 pending Hi! Bug #911620 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=7f43bf5f9 --- commit 7f43bf5f93c857bdb419892abfc014a5e9c3c273 Author: Guillem Jover Date: Tue Nov 6 03:06:33 2018 +0100 dpkg: Introduce a new dependency try level for trigger processing The introduction of dependency satisfiability for trigger processing, which was in the original spec but not the implementation, there has been countless problems with bogus detection of trigger cycles. The problem is that whenever we try to process triggers for a package, we might not be able to due to dependency unsatisfiaiblity, which means we have to put the package back into the queue. If we add the state into the cycle detection tracker, then multiple visits to these packages will hit the cycle detection for artificially generated cycles. But we cannot avoid performing the checks because that will miss dynamic cycles coming from maintainer scripts, for example. To avoid most of these problems (while possibly not fixing all potential ones), we should delay trigger processsing entirely until we have emptied the processing queue as much as possible. We do that by introducing a new dependency try level, after the dependency cycle breaking one. We will also make the trigger cycle detection unconditional of the dependency try, because for the trigproc try-queued it will not matter anymore as we will only ented on higher dependency tries, and for the other trigproc types we should not care about any queue-specific dependency try level. Closes: #810724, #854478, #911620 diff --git a/debian/changelog b/debian/changelog index f0d38635f..6b223549f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -42,6 +42,11 @@ dpkg (1.19.3) UNRELEASED; urgency=medium only reset the cycle detection in case we are not bailing out from the processing with an error, otherwise we could come back to this package and detect an artificial trigger cycle. + * dpkg: Introduce a new dependency try level for trigger processing. This +completely defers trigger processing until after the dependency cycle +breaking level, so to avoid generating artificial trigger cycles, when we +end up trying to process triggers with yet unsatisifiable dependencies. +Closes: #810724, #854478, #911620 * Perl modules: - Dpkg::Changelog::Debian: Preserve modelines at EOF. Closes: #916056 Thanks to Chris Lamb for initial test cases.
Bug#917735: marked as done (xr.sty: breaks \include handling)
Your message dated Wed, 23 Jan 2019 07:37:37 +
with message-id
and subject line Bug#917654: fixed in texlive-base 2018.20190122-1
has caused the Debian Bug report #917654,
regarding xr.sty: breaks \include handling
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
917654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bacula-doc
Version: 9.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/manuals/en/misc'
>
> Making output directories...
> echo "Output directories done"
> Output directories done
>
> Building external references for misc
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./misc.tex
> LaTeX2e <2018-12-01>
> (../../../latex/borgmanual.cls
> Document Class: borgmanual 2014/03/02 v1.0 Standard bacula.org Book LaTeX
> docum
> ent class
> (/usr/share/texlive/texmf-dist/tex/latex/eso-pic/eso-pic.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/atbegshi.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
> (../../../latex/atxy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texmf/tex/latex/html/html.sty
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) (./bacula.sty
> (/usr/share/texlive/texmf-dist/tex/latex/carlisle/ltxtable.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/varioref.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/xr-hyper.sty
>
> Package xr-hyper Warning: Load package `hyperref' after `xr-hyper'.
>
> ) (/usr/share/texlive/texmf-dist/tex/latex/tools/xr.sty)
> (../../../latex/external-references.tex
>
> Package xr Warning:
> No file ../main/sqlite.aux
> LABELS NOT IMPORTED.
> on input line 26.
>
>
> Package xr Warning:
> No file ../main/fileset.aux
> LABELS NOT IMPORTED.
> on input line 54.
>
>
> ! LaTeX Error: Missing \begin{document}.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H for immediate help.
> ...
>
> l.55 \externaldocument[main-]{../main/main}
>
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on ../pdf-and-html/misc/misc.log.
> make[2]:
Bug#917654: marked as done (xr.sty: breaks \include handling)
Your message dated Wed, 23 Jan 2019 07:37:37 +
with message-id
and subject line Bug#917654: fixed in texlive-base 2018.20190122-1
has caused the Debian Bug report #917654,
regarding xr.sty: breaks \include handling
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
917654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bacula-doc
Version: 9.4.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep --no-parallel
dh_update_autotools_config -i
dh_autoreconf -i
dh_auto_configure -i
dh_auto_build -i
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
Building external references file...==>Entering directory
/<>/manuals/en/console
make[2]: Entering directory '/<>/manuals/en/console'
Making output directories...
echo "Output directories done"
[... snipped ...]
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) (./bacula.sty
(/usr/share/texlive/texmf-dist/tex/latex/carlisle/ltxtable.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
(/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty))
(/usr/share/texlive/texmf-dist/tex/latex/tools/varioref.sty)
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
(/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
(/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/xr-hyper.sty
Package xr-hyper Warning: Load package `hyperref' after `xr-hyper'.
) (/usr/share/texlive/texmf-dist/tex/latex/tools/xr.sty)
(../../../latex/external-references.tex
Package xr Warning:
No file ../main/sqlite.aux
LABELS NOT IMPORTED.
on input line 30.
! LaTeX Error: Missing \begin{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H for immediate help.
...
l.41 \externaldocument[main-]{../main/main}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on ../pdf-and-html/utility/utility.log.
make[2]: *** [Makefile:115: external-references] Error 1
make[2]: Leaving directory '/<>/manuals/en/utility'
== Error in /<>/manuals/en/utility ==
make[1]: *** [Makefile:86: external-references] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 "INSTALL=install --strip-program=true" returned exit
code 2
make: *** [debian/rules:12: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bacula-doc.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2018.20190122-1
We believe that the bug you reported is fixed in the latest version of
texlive-base, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-base
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 22 Jan 2019 11:27:30 +0900
Source: texlive-base
Binary: texlive-base texlive-latex-base texlive-latex-recommended
Bug#919680: marked as done (anthy-el: does not work with emacs >= 24.3)
Your message dated Wed, 23 Jan 2019 07:14:22 + with message-id and subject line Bug#919680: fixed in anthy 1:0.3-8 has caused the Debian Bug report #919680, regarding anthy-el: does not work with emacs >= 24.3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: anthy-el Version: 1:0.3-7 Severity: grave Tags: patch upstream Justification: renders package unusable Dear Maintainer, pressing any key emits the following error, and cannot enter any characters: anthy-last-command-char: Symbol’s value as variable is void: last-command-char Attached is a patch which fixes this problem. Regards, -- YOSHINO Yoshihito -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages anthy-el depends on: ii anthy1:0.3-7 ii emacs-gtk [emacsen] 1:26.1+1-3 anthy-el recommends no packages. anthy-el suggests no packages. -- no debconf information --- a/src-util/anthy.el 2015-04-28 17:21:03.0 +0900 +++ b/src-util/anthy.el 2019-01-18 23:41:38.0 +0900 @@ -892,7 +892,7 @@ ((event-matches-key-specifier-p event 'backspace) 8) (t (char-to-int (event-to-character event) -last-command-char)) +last-command-event)) ;; ;; --- End Message --- --- Begin Message --- Source: anthy Source-Version: 1:0.3-8 We believe that the bug you reported is fixed in the latest version of anthy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. NOKUBI Takatsugu (supplier of updated anthy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Jan 2019 14:37:27 +0900 Source: anthy Binary: anthy anthy-common anthy-dbgsym anthy-el libanthy-dev libanthy1 libanthy1-dbgsym libanthyinput-dev libanthyinput0 libanthyinput0-dbgsym Architecture: source all i386 Version: 1:0.3-8 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: NOKUBI Takatsugu Description: anthy - Japanese kana-kanji conversion - utilities anthy-common - Japanese kana-kanji conversion - dictionary anthy-el - Japanese kana-kanji conversion - elisp frontend libanthy-dev - Japanese kana-kanji conversion - runtime library libanthy1 - Japanese kana-kanji conversion - runtime library libanthyinput-dev - Japanese kana-kanji conversion - runtime library for input libanthyinput0 - Japanese kana-kanji conversion - runtime library for input Closes: 919680 Changes: anthy (1:0.3-8) unstable; urgency=medium . * debian/patches/0001-work-with-emacs-24.3.1.patch: Re-add from https://sources.debian.org/src/anthy/9100h-25/debian/patches/work-with-emacs-24.3.1.patch/ (Closes: #919680). Checksums-Sha1: 1a8a6e363895517442fb391a3bff23da3ab26369 2379 anthy_0.3-8.dsc 9e539459cc4593d8bef4728106b2c321a6b85f37 12752 anthy_0.3-8.debian.tar.xz 99d4372c44f578af87171e9b73b28d4b705b7adf 5563648 anthy-common_0.3-8_all.deb 1ceda74d290145a7358cf24251e372caa7903a38 37096 anthy-dbgsym_0.3-8_i386.deb 02c25c7aad7a25754a2e4ee5b173676459595979 31048 anthy-el_0.3-8_all.deb 7f0d23e9a94d649944ee6a06b1cbaad736e8a85a 9149 anthy_0.3-8_i386.buildinfo 382ad3c81eaede31dc26bf014908b0388bc32707 26376 anthy_0.3-8_i386.deb 990aa974cdf7158d6c75e491167edb2c1c6955f0 123724 libanthy-dev_0.3-8_i386.deb d776f614ce1a09dca9cbd6e08937a36a726c76f9 192172 libanthy1-dbgsym_0.3-8_i386.deb b3795ec71d1bcc43d139aa9fcbca89113ae90f01 114084 libanthy1_0.3-8_i386.deb a27ed4772a56a210eb38ce9290921908289620c0 30560 libanthyinput-dev_0.3-8_i386.deb 667b827716a82c4e9062214e097e2b9a8e3574ba 34580 libanthyinput0-dbgsym_0.3-8_i386.deb
Bug#897806: Lmms fix uploaded
On 1/22/19 4:41 PM, Boyuan Yang wrote: > Hi all, > > 在 2019-01-21一的 00:26 +0100，Ross Gammon写道： >> tag 891756 + pending >> tag 897806 + pending >> tag 918242 + pending >> thanks >> >> I have uploaded a fix. It is unfortunately waiting for my new signing >> sub-key to be rolled into the Debian Keyring. > I've prepared an upload from git packaging repo onto DELAYED/3. Please let me > know if there's any other issues. > > -- > Thanks, > Boyuan Yang Thanks Boyuan. As long as that was from the new Debian Multimedia Team repo, that should be OK. signature.asc Description: OpenPGP digital signature
Bug#920242: start-stop-daemon: matching only on world-writable pidfile /dev/null is insecure (No such file or directory)
Source: dpkg Version: 1.19.3 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, Since the 1.19.3 upgrade pbuilder environment are broken: I: Extracting source /sbin/start-stop-daemon: matching only on world-writable pidfile /dev/null is insecure (No such file or directory) E: pbuilder: Failed extracting the source Should that really be a terminal error? Kind Regards, Bas
Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+
On 1/21/19 4:33 PM, Moritz Mühlenhoff wrote: > On Sat, Jan 19, 2019 at 04:18:06PM -0500, Louis-Philippe Véronneau wrote: >> Hello from the Montreal BSP! >> >> I tested the latest release of the upstream version (0.2.36) and it >> worked fine for me on the latest Thunderbird in testing. >> >> I migrated the nostalgy VCS from the Alioth archive to Salsa and updated >> it to the latest release: https://salsa.debian.org/webext-team/nostalgy >> >> After testing it, everything seems to work for me. I asked >> anar...@debian.org to upload it to the archive. > > Note that the original bug report is for Stretch. Are you also planning > to update stable as well? Hi! Sadly, one cannot simply update a package in Stretch (the current stable version) that easily. What makes Debian Stable is that packages aren't updated but for security reasons. I do not think this is a security issue. This package should be migrated to testing in about 2 days. You can then install it from there. -- ,''`. : :' : Louis-Philippe Véronneau `. `'` po...@debian.org / veronneau.org `- signature.asc Description: OpenPGP digital signature
Bug#905208: marked as done (emms: fails to upgrade from 'stretch': emms-setup.el:98:15:Error: Cannot open load file: No such file or directory, seq)
Your message dated Wed, 23 Jan 2019 04:49:14 + with message-id and subject line Bug#905208: fixed in emms 5.1-1 has caused the Debian Bug report #905208, regarding emms: fails to upgrade from 'stretch': emms-setup.el:98:15:Error: Cannot open load file: No such file or directory, seq to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 905208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emms Version: 5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log (scroll to the bottom...): Setting up emms (5.0-1) ... Install emacsen-common for emacs24 emacsen-common: Handling install of emacsen flavor emacs24 Wrote /etc/emacs24/site-start.d/00debian-vars.elc Wrote /usr/share/emacs24/site-lisp/debian-startup.elc Install emms for emacs24 install/emms: byte-compiling for emacs24, logging in /tmp/elc.Rs5KQDTWAN3v ERROR: install script from emms package failed dpkg: error processing package emms (--configure): installed emms package post-installation script subprocess returned error exit status 1 Setting up libtagc0:amd64 (1.11.1+dfsg.1-0.2+b1) ... Setting up librsvg2-2:amd64 (2.40.20-2) ... Setting up librsvg2-common:amd64 (2.40.20-2) ... Setting up adwaita-icon-theme (3.28.0-1) ... Setting up libgtk-3-0:amd64 (3.22.30-2) ... Setting up emacs25 (25.2+1-6+b2) ... update-alternatives: using /usr/bin/emacs25-x to provide /usr/bin/emacs (emacs) in auto mode Install emacsen-common for emacs25 emacsen-common: Handling install of emacsen flavor emacs25 Install emms for emacs25 install/emms: byte-compiling for emacs25, logging in /tmp/elc.Mo5TKnEAl1mc install/emms: deleting /tmp/elc.Mo5TKnEAl1mc Setting up emacs (47.0) ... Processing triggers for libc-bin (2.27-5) ... Processing triggers for systemd (239-7) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ... Errors were encountered while processing: emms The emacs24 logfile contains: Loading 00debian-vars... Loading /etc/emacs/site-start.d/50emms.el (source)... Wrote /usr/share/emacs24/site-lisp/emms/emms-auto.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-bookmarks.elc In toplevel form: emms-browser.el:292:1:Error: Cannot open load file: No such file or directory, seq Wrote /usr/share/emacs24/site-lisp/emms/emms-cache.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-compat.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-cue.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-history.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-i18n.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-info-libtag.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-info-metaflac.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-info-mp3info.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-info-ogginfo.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-info-opusinfo.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-info.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-last-played.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-librefm-scrobbler.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-librefm-stream.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-lyrics.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-maint.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-mark.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-metaplaylist-mode.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-mode-line-icon.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-mode-line.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mpd.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mpg321-remote.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mplayer.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mpv.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-simple.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-vlc.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-player-xine.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-playing-time.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-playlist-limit.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-playlist-mode.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-playlist-sort.elc Wrote /usr/share/emacs24/site-lisp/emms/emms-score.elc In toplevel form: emms-setup.el:98:15:Error: Cannot open load file: No such file or directory, seq Wrote
Bug#917968: marked as done (emms: relies on default-major-mode (replaced by major-mode in emacs 26))
Your message dated Wed, 23 Jan 2019 04:49:14 +
with message-id
and subject line Bug#917968: fixed in emms 5.1-1
has caused the Debian Bug report #917968,
regarding emms: relies on default-major-mode (replaced by major-mode in emacs
26)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
917968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emms
Version: 4.2-1.1
Severity: serious
It looks like emacs has removed the default-major-mode variable in favor
of major-mode. I tried just replacing the reference, and emms appears
to build successfully.
I noticed this because it breaks emacsspeak.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Source: emms
Source-Version: 5.1-1
We believe that the bug you reported is fixed in the latest version of
emms, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Arnaud Fontaine (supplier of updated emms package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 22 Jan 2019 19:33:40 +0900
Source: emms
Binary: emms emms-dbgsym
Architecture: source amd64
Version: 5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Fontaine
Changed-By: Arnaud Fontaine
Description:
emms - Emacs MultiMedia System
Closes: 905208 917968
Changes:
emms (5.1-1) unstable; urgency=medium
.
* New upstream release. Closes: #917968.
+ d/copyright: All the files have now FSF as the copyright holders.
* d/emacsen-install: >=5.0 uses seq.el available only from emacs >=
25 so ignore older flavors. Closes: #905208.
* Update package after emacs package unversioning (from 1:25.2+1-7). This
means no emacsXY flavors anymore, only emacs (and xemacs21). Keep emacs25
for backports.
+ d/control:
- Depends on emacsen-common only and move emacs* to Recommends.
- Add Enhances field against emacs* packages.
- Add Build-Depends on emacs | emacs-nox.
+ d/emacsen-{install,remove}: emacs flavor was ignored until now.
* d/copyright:
+ Update debian directory copyright years.
+ Update Source URL.
* d/control:
+ Bump Standards-Version to 4.3.0. No change needed.
* d/emacsen-install: Simplify and keep byte-compile log in ELDIR.
Checksums-Sha1:
14a4d571abecec3a36b23969fc2b3b48020b9597 2036 emms_5.1-1.dsc
9e2ee742cd5e596bd23b55e865e7542e6db2d3c9 312780 emms_5.1.orig.tar.gz
dbd8feac4520b1dd094ad59529c47bc68d7811cc 501 emms_5.1.orig.tar.gz.asc
6c13f6a543b80f36aac12dff629dc9409181996f 19220 emms_5.1-1.debian.tar.xz
3224c99d0f9e1fc5648771456ffc3c00b9fa2922 49780 emms-dbgsym_5.1-1_amd64.deb
9cc1413a7c319b6f8010292e0b5ed91ffd1b11a0 6435 emms_5.1-1_amd64.buildinfo
652809fc325e0223706171476e32ac7ebb78f1d8 329524 emms_5.1-1_amd64.deb
Checksums-Sha256:
fa94f4d792ad9cbe5ccc037bae53172af63d4eb339bb19aa551ae4da2e452ae5 2036
emms_5.1-1.dsc
a68b4ed7d77c51db3090a6a31d99278ee74069060fd94aec07a19bee3f6b2d91 312780
emms_5.1.orig.tar.gz
4854868507b77eb9972424040da76fa66b2918b2250d1043aa04237e9d0dc87a 501
emms_5.1.orig.tar.gz.asc
dc334cb86f5d4ad9714bb5864b53bcd8fd4d521deb8f8f6543ea860a6c6c9935 19220
emms_5.1-1.debian.tar.xz
a727d65db3758417ee173166c15055039d0cb53b091529d10c1d501e6b367069 49780
emms-dbgsym_5.1-1_amd64.deb
a4affc68d4003a51c7987d5de6d6ab64fd5f9ce1ffacd773254845d946716591 6435
emms_5.1-1_amd64.buildinfo
81c645101697d582d607151cf9a1e367b014eee1a97cd3bb74f46dc7d2b53427 329524
emms_5.1-1_amd64.deb
Files:
7fcd5eca688ab8e9dbec10e4f508e19f 2036 sound optional emms_5.1-1.dsc
43b6d13ead941bcfda15f3de51edbc3b 312780 sound optional emms_5.1.orig.tar.gz
7c2549e4e3e62297f4f7ad253eb64c26 501 sound optional emms_5.1.orig.tar.gz.asc
9b907d456593abef915b0daf7e95c17b 19220 sound optional emms_5.1-1.debian.tar.xz
002dd8a2fec1b6e5f71025086f2b5ee2 49780 debug optional
emms-dbgsym_5.1-1_amd64.deb
Bug#895482: marked as done (Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4)
Your message dated Wed, 23 Jan 2019 02:38:55 + with message-id and subject line Bug#895482: fixed in ca-certificates 20190110 has caused the Debian Bug report #895482, regarding Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 895482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates Version: 20180409 Severity: serious Upgrading ca-certificates from 20170717 to 20180409 fails for me as follows on one machine: Before unpacking, I have been shown this dialog, which I acknowledged by pressing enter: ┌┤ ca-certificates configuration ├─┐ │ During upgrades, new certificates will be added. Please choose those you trust. │ │ │ │ New certificates to activate: │ │ │ │[ ] mozilla/GDCA_TrustAUTH_R5_ROOT.crt │ │[ ] mozilla/SSL.com_EV_Root_Certification_Authority_ECC.crt │ │[ ] mozilla/SSL.com_EV_Root_Certification_Authority_RSA_R2.crt │ │[ ] mozilla/SSL.com_Root_Certification_Authority_ECC.crt │ │[ ] mozilla/SSL.com_Root_Certification_Authority_RSA.crt │ │[ ] mozilla/TrustCor_ECA-1.crt │ │[ ] mozilla/TrustCor_RootCert_CA-1.crt │ │[ ] mozilla/TrustCor_RootCert_CA-2.crt │ │ │ │ │ │ │ │ │ └──┘ Unpacking went fine: Preparing to unpack .../04-ca-certificates_20180409_all.deb ... Unpacking ca-certificates (20180409) over (20170717) ... The first as well as the second try to configure ca-certificates failed identically: Setting up ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... W: /usr/share/ca-certificates/mozilla/AddTrust_Public_Services_Root.crt not found, but listed in /etc/ca-certificates.conf. W: /usr/share/ca-certificates/mozilla/AddTrust_Qualified_Certificates_Root.crt not found, but listed in /etc/ca-certificates.conf. W: /usr/share/ca-certificates/mozilla/UTN_USERFirst_Hardware_Root_CA.crt not found, but listed in /etc/ca-certificates.conf. W: /usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt not found, but listed in /etc/ca-certificates.conf. rehash: skipping DST_ACES_CA_X6.pem, cannot open file rehash: skipping AddTrust_Qualified_Certificates_Root.pem, cannot open file rehash: skipping UTN_USERFirst_Hardware_Root_CA.pem, cannot open file rehash: skipping AddTrust_Public_Services_Root.pem, cannot open file dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 4 […] Errors were encountered while processing: ca-certificates […] E: Sub-process /usr/bin/dpkg returned an error code (1) […] Setting up ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... W: /usr/share/ca-certificates/mozilla/AddTrust_Public_Services_Root.crt not found, but listed in /etc/ca-certificates.conf. W: /usr/share/ca-certificates/mozilla/AddTrust_Qualified_Certificates_Root.crt not found, but listed in /etc/ca-certificates.conf. W: /usr/share/ca-certificates/mozilla/UTN_USERFirst_Hardware_Root_CA.crt not found, but listed in /etc/ca-certificates.conf. W: /usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt not found, but listed in /etc/ca-certificates.conf. rehash: skipping DST_ACES_CA_X6.pem, cannot open file rehash: skipping AddTrust_Qualified_Certificates_Root.pem, cannot open file rehash: skipping UTN_USERFirst_Hardware_Root_CA.pem, cannot
Bug#900299: leiningen-clojure: depends on openjdk-8
Elana Hashman writes: > So here's the issue with Leiningen and Java 11. We previously tracked > down some sort of bytecode incompatibilty problem. When Leiningen is > built with Java 11, it seems to recompile every time it's run, leading > to unacceptable performance, and it results in *different* help output, > which is baffling. > > Phil, have we attempted building Leiningen with Java 11 upstream? I've tried it but Leiningen won't build on Java 11 because of this bug in Clojure: https://dev.clojure.org/jira/browse/CLJ-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel It looks like it's been fixed in newer versions of Clojure, but we haven't bumped that in Leiningen yet. -Phil signature.asc Description: PGP signature
Bug#919154: marked as done (mailman3-web: mailman3-web-qcluster.service fails because ExecStart is missing absolute path to python3)
Your message dated Wed, 23 Jan 2019 00:20:54 + with message-id and subject line Bug#919154: fixed in mailman-suite 0+20180916-3 has caused the Debian Bug report #919154, regarding mailman3-web: mailman3-web-qcluster.service fails because ExecStart is missing absolute path to python3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mailman3-web Version: 0+20180916-2~bpo9+1 Severity: grave Dear Maintainer, mailman3-web-qcluster.service ExecStart is missing absolute path to python3: # systemctl cat mailman3-web-qcluster.service |egrep '^#|Exec' # /lib/systemd/system/mailman3-web-qcluster.service ExecStart=python3 /usr/bin/django-admin qcluster --pythonpath /usr/share/mailman3-web --settings settings This causes systemd (232-25+deb9u6) to fail with the following: [/lib/systemd/system/mailman3-web-qcluster.service:8] Executable path is not absolute, ignoring: python3 /usr/bin/django-admin qcluster --pythonpath /usr/share/mailman3-web --settings settings mailman3-web-qcluster.service: Service lacks both ExecStart= and ExecStop= setting. Refusing. Has this requirement been relaxed in systemd in stretch-backports? Is this a missing dependency? Regardless, just changing python3 to /usr/bin/python3 is enough: ExecStart=/usr/bin/python3 /usr/bin/django-admin qcluster --pythonpath /usr/share/mailman3-web --settings settings Then restarting the service works: # systemctl daemon-reload # systemctl restart mailman3-web-qcluster.service -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mailman3-web depends on: ii dbconfig-pgsql 2.0.8 ii dbconfig-sqlite3 2.0.8 ii debconf [debconf-2.0] 1.5.61 ii lsb-base 9.20161125 ii node-less 1.6.3~dfsg-2 ii python33.5.3-1 ii python3-django-hyperkitty 1.2.1-4~bpo9+1 ii python3-django-postorius 1.2.2-4~bpo9+2 ii python3-psycopg2 2.6.2-1 ii python3-whoosh 2.7.0-2 ii ruby-sass 3.4.23-1 ii ucf3.0036 ii uwsgi 2.0.14+20161117-3+deb9u2 ii uwsgi-plugin-python3 2.0.14+20161117-3+deb9u2 Versions of packages mailman3-web recommends: ii libapache2-mod-proxy-uwsgi 2.0.14+20161117-3+deb9u2 Versions of packages mailman3-web suggests: ii default-mysql-server1.0.2 ii mariadb-server-10.1 [virtual-mysql-server] 10.1.37-0+deb9u1 ii postgresql 9.6+181+deb9u2 -- Sampo Sorsa Sent with ProtonMail Secure Email. --- End Message --- --- Begin Message --- Source: mailman-suite Source-Version: 0+20180916-3 We believe that the bug you reported is fixed in the latest version of mailman-suite, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre-Elliott Bécue (supplier of updated mailman-suite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Jan 2019 00:39:29 +0100 Source: mailman-suite Binary: mailman3-web Architecture: source Version: 0+20180916-3 Distribution: unstable Urgency: medium Maintainer: Debian Mailman Team Changed-By: Pierre-Elliott Bécue Description: mailman3-web - Django project integrating Mailman3 Postorius and HyperKitty Closes: 917548 919154 919158 Changes: mailman-suite (0+20180916-3) unstable; urgency=medium . [ Jonas Meurer ] * d/mailman3-web.mailman3-web-qcluster.service: - Fix path to python3 interpreter (Closes: #919154) . [ Pierre-Elliott Bécue ] * d/mailman3-web.postinst: - Avoid dpkg -s call for the upgrade_fixes, and call the fix only on
Bug#919158: marked as done (mailman3-web: cronjobs should be run with flock to avoid them running amok)
Your message dated Wed, 23 Jan 2019 00:20:54 + with message-id and subject line Bug#919158: fixed in mailman-suite 0+20180916-3 has caused the Debian Bug report #919158, regarding mailman3-web: cronjobs should be run with flock to avoid them running amok to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mailman3-web Version: 0+20180916-2~bpo9+1 Severity: serious Dear Maintainer, mailman3-web cronjobs (django-admin runjobs minutely as worst) are run without flock. When the system is (temporarily) constrained on resources, this can cause a severe backlog of django-admin runjobs, grinding the system to a halt. This is not fun: root 961 0.0 0.0 76116 104 ?S10:44 0:00 /usr/sbin/CRON -f www-data 962 0.0 0.0 4288 0 ?Ss 10:44 0:00 /bin/sh -c [ -f /usr/bin/django-admin ] && python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings www-data 963 0.3 0.0 343884 1808 ?Sl 10:44 0:12 python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings root 1330 0.0 0.0 76116 108 ?S10:45 0:00 /usr/sbin/CRON -f www-data 1335 0.0 0.0 4288 0 ?Ss 10:45 0:00 /bin/sh -c [ -f /usr/bin/django-admin ] && python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings www-data 1337 0.2 0.2 339696 10836 ?Sl 10:45 0:08 python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings Ad infinitum # pidof -x python3 13186 12884 12592 12304 11987 11596 11154 11103 10890 10889 10888 10887 10886 10857 10607 10260 10206 10068 9671 9371 9021 8551 7579 7096 6646 6315 5983 5662 5351 5029 4705 4394 3974 3643 2976 2405 2357 2041 2036 1680 1337 963 # uptime 11:48:37 up 29 days, 3:46, 21 users, load average: 110.60, 99.61, 73.86 # kill -9 $(pidof -x python3) -bash: fork: Cannot allocate memory My PTSD now recommends prefixing each job in /etc/cron.d/mailman3-web with a flock -n call: * * * * * www-data[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings 2,17,32,47 * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.quarter_hourly python3 /usr/bin/django-admin runjobs quarter_hourly --pythonpath /usr/share/mailman3-web --settings settings @hourly www-data[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly python3 /usr/bin/django-admin runjobs hourly --pythonpath /usr/share/mailman3-web --settings settings @daily www-data[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.daily python3 /usr/bin/django-admin runjobs daily --pythonpath /usr/share/mailman3-web --settings settings @weekly www-data[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.weekly python3 /usr/bin/django-admin runjobs weekly --pythonpath /usr/share/mailman3-web --settings settings @monthlywww-data[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly python3 /usr/bin/django-admin runjobs monthly --pythonpath /usr/share/mailman3-web --settings settings @yearly www-data[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.yearly python3 /usr/bin/django-admin runjobs yearly --pythonpath /usr/share/mailman3-web --settings settings Let me know if you want a patch. By the way, is there a reason why /usr/share/mailman3-web/manage.py is not used throughout the mailman3-web package instead of "/usr/bin/django-admin --pythonpath /usr/share/mailman3-web --settings settings"? Because that's basically what the manage.py wrapper does. -- Sampo Sorsa --- End Message --- --- Begin Message --- Source: mailman-suite Source-Version: 0+20180916-3 We believe that the bug you reported is fixed in the latest version of mailman-suite, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug
Processed: change severity
Processing commands for cont...@bugs.debian.org: > severity 920147 important Bug #920147 [sagemath] sagemath FTBFS on mipsel and mips64el Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 920147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919907: marked as done (ntopng FTBFS with ndpi 2.6)
Your message dated Tue, 22 Jan 2019 23:05:18 + with message-id and subject line Bug#919907: fixed in ntopng 3.8+dfsg1-1 has caused the Debian Bug report #919907, regarding ntopng FTBFS with ndpi 2.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ntopng Version: 2.4+dfsg1-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ntopng.html ... g++ -g -Wall -I/build/1st/ntopng-3.2+dfsg1 -I/build/1st/ntopng-3.2+dfsg1/include -I/usr/local/include -D_FILE_OFFSET_BITS=64 -I/usr/include/hiredis -I/usr/include/hiredis -I/build/1st/ntopng-3.2+dfsg1/third-party/mongoose -I/usr/include/json-c -I/usr/include/ndpi/libndpi -I/build/1st/ntopng-3.2+dfsg1/third-party/LuaJIT-2.1.0-beta3/src -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.2 -I/usr/lib/x86_64-linux-gnu/pgm-5.2/include -I/usr/include/mariadb -I/usr/include/mariadb/mysql -Wdate-time -D_FORTIFY_SOURCE=2 -I/build/1st/ntopng-3.2+dfsg1 -I/build/1st/ntopng-3.2+dfsg1/include -I/usr/local/include -I/build/1st/ntopng-3.2+dfsg1/third-party/http-client-c/src/ -I/usr/include/openssl -DDATA_DIR='"/usr/share"' -I/build/1st/ntopng-3.2+dfsg1/third-party/libgeohash -I/build/1st/ntopng-3.2+dfsg1/third-party/patricia -g -O2 -ffile-prefix-map=/build/1st/ntopng-3.2+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -c src/AlertCounter.cpp -o src/AlertCounter.o In file included from src/AlertCounter.cpp:22: /build/1st/ntopng-3.2+dfsg1/include/ntop_includes.h:107:10: fatal error: ndpi_main.h: No such file or directory #include "ndpi_main.h" ^ compilation terminated. make[2]: *** [Makefile:153: src/AlertCounter.o] Error 1 --- End Message --- --- Begin Message --- Source: ntopng Source-Version: 3.8+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ntopng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovico Cavedon (supplier of updated ntopng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Jan 2019 17:46:18 -0800 Source: ntopng Binary: ntopng ntopng-data ntopng-doc Architecture: source all amd64 Version: 3.8+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Ludovico Cavedon Changed-By: Ludovico Cavedon Description: ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool ntopng-data - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d ntopng-doc - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d Closes: 887318 903154 910859 919907 Changes: ntopng (3.8+dfsg1-1) unstable; urgency=medium . * New upstream version 3.8+dfsg1 (Closes: #919907, #910859, #903154, #887318, CVE-2018-12520). * Drop get-orig-source target in favor of Files-Excluded in the copyright file. * Remove third-party/lua-5.* as we build against the system one. * Build-Depend against liblua5.3-dev. * Update copyright information. * Refresh patches and remove internal-luajit.patch (no longer applicable). * Update Build-Depend against libndpi-dev >= 2.6 * Build-depend on libmaxminddb-dev. * Add use-system-lua.patch to use system liblua insetad of the embedded one. * Bump Build-Dep on debhelper >= 10.8 to support the --doc-main-package option of dh_installdocs. * Migrate datadir from /var/tmp/ntopng to /var/lib/ntopng in postinst. * Use system libjs-html5shiv, libjs-jquery, and libjs-jquery-ui. * Make ntopng-utils-manage-config executable (needed for the web UI to be able to backup/restore the configuration). * Change systemd Restart to on-abnormal. * Update the list of README to install as docs. * Generate html documentation and register it with doc-base. Split documentation into ntopng-doc package. * Update Vcs headers to point to salsa.debian.org. * Remove httpdocs/geoip/README as recommended by lintian. * Bump Standards-Version to
Bug#920045: marked as done (ntopng FTBFS with new ndpi)
Your message dated Tue, 22 Jan 2019 23:05:18 + with message-id and subject line Bug#919907: fixed in ntopng 3.8+dfsg1-1 has caused the Debian Bug report #919907, regarding ntopng FTBFS with new ndpi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: ntomng version: 2.4+dfsg1-4 severity: serious ntopng fails to build from source with the new ndpi, which recently migrated to testing. This affects both the version in buster (as evidenced by the raspbian binnmu http://buildd.raspbian.org/status/fetch.php?pkg=ntopng=armhf=2.4%2Bdfsg1-4%2Bb3=1548089724 ) and the version in sid (as evidenced by reproducible builds https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ntopng_3.2+dfsg1-1.rbuild.log.gz ) --- End Message --- --- Begin Message --- Source: ntopng Source-Version: 3.8+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ntopng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovico Cavedon (supplier of updated ntopng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Jan 2019 17:46:18 -0800 Source: ntopng Binary: ntopng ntopng-data ntopng-doc Architecture: source all amd64 Version: 3.8+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Ludovico Cavedon Changed-By: Ludovico Cavedon Description: ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool ntopng-data - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d ntopng-doc - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d Closes: 887318 903154 910859 919907 Changes: ntopng (3.8+dfsg1-1) unstable; urgency=medium . * New upstream version 3.8+dfsg1 (Closes: #919907, #910859, #903154, #887318, CVE-2018-12520). * Drop get-orig-source target in favor of Files-Excluded in the copyright file. * Remove third-party/lua-5.* as we build against the system one. * Build-Depend against liblua5.3-dev. * Update copyright information. * Refresh patches and remove internal-luajit.patch (no longer applicable). * Update Build-Depend against libndpi-dev >= 2.6 * Build-depend on libmaxminddb-dev. * Add use-system-lua.patch to use system liblua insetad of the embedded one. * Bump Build-Dep on debhelper >= 10.8 to support the --doc-main-package option of dh_installdocs. * Migrate datadir from /var/tmp/ntopng to /var/lib/ntopng in postinst. * Use system libjs-html5shiv, libjs-jquery, and libjs-jquery-ui. * Make ntopng-utils-manage-config executable (needed for the web UI to be able to backup/restore the configuration). * Change systemd Restart to on-abnormal. * Update the list of README to install as docs. * Generate html documentation and register it with doc-base. Split documentation into ntopng-doc package. * Update Vcs headers to point to salsa.debian.org. * Remove httpdocs/geoip/README as recommended by lintian. * Bump Standards-Version to 4.3.0. Checksums-Sha1: 769b9e2c1bc0aaee1c9d4f2864a5de709e5e49ca 2321 ntopng_3.8+dfsg1-1.dsc c03fd8520421042e78213aaa33c5f4066a4c615f 30984974 ntopng_3.8+dfsg1.orig.tar.gz 1fa1c4e4919191a21a19fd0711c1ff60f46eec2f 27660 ntopng_3.8+dfsg1-1.debian.tar.xz cf57816dd05f0e3c3e29ccc451602204dbd6c48f 1867480 ntopng-data_3.8+dfsg1-1_all.deb 34f252b3f5dd2c5c8af26a7b4b55344c68467b81 3818508 ntopng-dbgsym_3.8+dfsg1-1_amd64.deb 99a7d4623692df5a6ca810f1c48350cb1396b09d 25123440 ntopng-doc_3.8+dfsg1-1_all.deb a6885a5112c2f046d871a7770f24187f096c78ed 12435 ntopng_3.8+dfsg1-1_amd64.buildinfo 147e0cf21b675e252fcdc6591dd1f5afd8f20a04 352664 ntopng_3.8+dfsg1-1_amd64.deb Checksums-Sha256: b1944b3ae5aea0c66adfa16e85e3152c99fdec2a295cdb34f174fea455f0c053 2321 ntopng_3.8+dfsg1-1.dsc 400be6391b4b97a2dfee2b6f5a879adce3b2527c913ff9e17d3fe77a7c02e00f 30984974 ntopng_3.8+dfsg1.orig.tar.gz 695e0f6d4aa927e0b56e94cad549b22e9690118553b0652f151acc20e4d14472 27660
Bug#887318: marked as done (ntopng FTBFS on ppc64el: No support for PowerPC 64 bit mode (yet))
Your message dated Tue, 22 Jan 2019 23:05:17 + with message-id and subject line Bug#887318: fixed in ntopng 3.8+dfsg1-1 has caused the Debian Bug report #887318, regarding ntopng FTBFS on ppc64el: No support for PowerPC 64 bit mode (yet) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 887318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ntopng Version: 3.2+dfsg1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=ntopng=ppc64el=3.2%2Bdfsg1-1=1514653837=0 ... Building LuaJIT 2.1.0-beta3 make -C src make[4]: Entering directory '/<>/ntopng-3.2+dfsg1/third-party/LuaJIT-2.1.0-beta3/src' lj_arch.h:428:2: error: #error "No support for PowerPC 64 bit mode (yet)" #error "No support for PowerPC 64 bit mode (yet)" ^ --- End Message --- --- Begin Message --- Source: ntopng Source-Version: 3.8+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ntopng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovico Cavedon (supplier of updated ntopng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Jan 2019 17:46:18 -0800 Source: ntopng Binary: ntopng ntopng-data ntopng-doc Architecture: source all amd64 Version: 3.8+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Ludovico Cavedon Changed-By: Ludovico Cavedon Description: ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool ntopng-data - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d ntopng-doc - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d Closes: 887318 903154 910859 919907 Changes: ntopng (3.8+dfsg1-1) unstable; urgency=medium . * New upstream version 3.8+dfsg1 (Closes: #919907, #910859, #903154, #887318, CVE-2018-12520). * Drop get-orig-source target in favor of Files-Excluded in the copyright file. * Remove third-party/lua-5.* as we build against the system one. * Build-Depend against liblua5.3-dev. * Update copyright information. * Refresh patches and remove internal-luajit.patch (no longer applicable). * Update Build-Depend against libndpi-dev >= 2.6 * Build-depend on libmaxminddb-dev. * Add use-system-lua.patch to use system liblua insetad of the embedded one. * Bump Build-Dep on debhelper >= 10.8 to support the --doc-main-package option of dh_installdocs. * Migrate datadir from /var/tmp/ntopng to /var/lib/ntopng in postinst. * Use system libjs-html5shiv, libjs-jquery, and libjs-jquery-ui. * Make ntopng-utils-manage-config executable (needed for the web UI to be able to backup/restore the configuration). * Change systemd Restart to on-abnormal. * Update the list of README to install as docs. * Generate html documentation and register it with doc-base. Split documentation into ntopng-doc package. * Update Vcs headers to point to salsa.debian.org. * Remove httpdocs/geoip/README as recommended by lintian. * Bump Standards-Version to 4.3.0. Checksums-Sha1: 769b9e2c1bc0aaee1c9d4f2864a5de709e5e49ca 2321 ntopng_3.8+dfsg1-1.dsc c03fd8520421042e78213aaa33c5f4066a4c615f 30984974 ntopng_3.8+dfsg1.orig.tar.gz 1fa1c4e4919191a21a19fd0711c1ff60f46eec2f 27660 ntopng_3.8+dfsg1-1.debian.tar.xz cf57816dd05f0e3c3e29ccc451602204dbd6c48f 1867480 ntopng-data_3.8+dfsg1-1_all.deb 34f252b3f5dd2c5c8af26a7b4b55344c68467b81 3818508 ntopng-dbgsym_3.8+dfsg1-1_amd64.deb 99a7d4623692df5a6ca810f1c48350cb1396b09d 25123440 ntopng-doc_3.8+dfsg1-1_all.deb a6885a5112c2f046d871a7770f24187f096c78ed 12435 ntopng_3.8+dfsg1-1_amd64.buildinfo 147e0cf21b675e252fcdc6591dd1f5afd8f20a04 352664 ntopng_3.8+dfsg1-1_amd64.deb Checksums-Sha256: b1944b3ae5aea0c66adfa16e85e3152c99fdec2a295cdb34f174fea455f0c053 2321 ntopng_3.8+dfsg1-1.dsc 400be6391b4b97a2dfee2b6f5a879adce3b2527c913ff9e17d3fe77a7c02e00f 30984974 ntopng_3.8+dfsg1.orig.tar.gz 695e0f6d4aa927e0b56e94cad549b22e9690118553b0652f151acc20e4d14472 27660
Bug#918421: marked as done (node-prelude-ls FTBFS with nodejs 10.15.0)
Your message dated Tue, 22 Jan 2019 22:35:52 + with message-id and subject line Bug#918421: fixed in node-prelude-ls 1.1.2+dfsg-3 has caused the Debian Bug report #918421, regarding node-prelude-ls FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-prelude-ls Version: 1.1.2+dfsg-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-prelude-ls.html ... 437 passing (337ms) 2 failing 1) negate zero: AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B: + expected - actual - 0 + -0 + expected - actual -0 +-0 at Context. (test/Num.ls:35:12) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 2) ceiling negative number: AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B: + expected - actual - 0 + -0 + expected - actual -0 +-0 at Context. (test/Num.ls:236:12) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) make[1]: *** [Makefile:40: test] Error 2 --- End Message --- --- Begin Message --- Source: node-prelude-ls Source-Version: 1.1.2+dfsg-3 We believe that the bug you reported is fixed in the latest version of node-prelude-ls, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-prelude-ls package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Jan 2019 23:15:52 +0100 Source: node-prelude-ls Binary: node-prelude-ls Architecture: source Version: 1.1.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 918421 Description: node-prelude-ls - functionally oriented utility library Changes: node-prelude-ls (1.1.2+dfsg-3) unstable; urgency=medium . * Team upload * Refresh patches * Add upstream/metadata * Add patch to disable failing tests (reported to upstream) (Closes: #918421) * Bump debheper compatibility level to 11 * Change section to javascript * Declare compliance with policy 4.3.0 * Update CVD fields to salsa * Update debian/copyright format url * Update homepage to https * Add minimal description to patches * Remove useless "make test" test in autopkgtest files Checksums-Sha1: 373e92d707679f0abce57971f1fa28ed05a83074 2097 node-prelude-ls_1.1.2+dfsg-3.dsc 53597c63c4132070a607c6ac2377d62ba07bcd7a 3248 node-prelude-ls_1.1.2+dfsg-3.debian.tar.xz Checksums-Sha256: 8ee3c345bd082c32819d07c9db0f9ee31e8fc70c59239b22f702daea5525425f 2097 node-prelude-ls_1.1.2+dfsg-3.dsc a50858e75ac4527486e1de548793ec0374fafa1a06d5e059c39feef901a1c7a6 3248 node-prelude-ls_1.1.2+dfsg-3.debian.tar.xz Files: 29cd5539ef514d6701eadb0fb8c93490 2097 javascript optional node-prelude-ls_1.1.2+dfsg-3.dsc c2fa4bc9171949aad14873a9c55737a6 3248 javascript optional node-prelude-ls_1.1.2+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE-
Bug#919196: Debian bug when running unit tests
Le mardi 22 janvier 2019 à 02:50:48+0100, Pierre-Elliott Bécue a écrit :
> Le mardi 22 janvier 2019 à 01:57:22+0100, Pierre-Elliott Bécue a écrit :
> > Le lundi 21 janvier 2019 à 14:37:36+0100, Thomas Goirand a écrit :
> > > Hi,
> > >
> > > Would you have any idea how to resolve this Debian bug?
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919196
> > >
> > > I'm not sure, but to me, it looks like the unit tests are running in
> > > loop in the ::handshake() method.
> >
> > The handshake fails, because gnutls doesn't accept the security level
> > offered by the handshake.
> >
> > It seems to me the issue is in the next test: t->send is called, and
> > send is defined as a looping function until the decrypted content is
> > received. As the handshake previously failed, t->send waits forever.
> >
> > I guess the tests should have a timeout method.
> >
> > Anyway, increasing the security of the handshake would make it work and
> > hence the current issue should be gone.
>
> I found out that a new upstream release includes fixes the security
> issue I mentioned before. Attempting to build this release works fine
> and the tests are passing without hanging.
>
> I'm not certain whether the fix is due to the addition of
> 'gnutls_certificate_set_x509_system_trust( m_credentials );' to
> tlsgnutlsclient.cpp or to the changes made to
> 'gnutls_priority_set_direct' in tlsgnutls{server,client}anon.cpp.
>
> This looks good to me.
>
> Vincent, I made a NMU branch which is just a fast-forward of master on
> the salsa repo[0]. The branch name is 1.0.22-0.1
>
> If you agree, I shall do an upload. Otherwise I'll let you taking care
> of it.
>
> Best regards,
>
> [0] https://salsa.debian.org/debian/gloox/commits/1.0.22-0.1
Hi,
I uploaded gloox 1.0.22-0.1 in DELAYED/7. Feel free to dcut rm if you're
not satisfied, or to speed up the upload if you think it's relevant.
Best regards,
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
signature.asc
Description: PGP signature
Processed: Re: Bug#893227: libbluray FTBFS with openjdk-9
Processing control commands: > severity -1 important Bug #893227 [src:libbluray] libbluray FTBFS with openjdk-9 Severity set to 'important' from 'serious' -- 893227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893227: libbluray FTBFS with openjdk-9
Control: severity -1 important On Tue, Jan 22, 2019 at 7:48 AM Emmanuel Bourg wrote: > OpenJDK 8 will be kept in Buster but it should be used in exceptional > cases (for example the lombok package requires both OpenJDK 8 and 11 to > build). The default Java runtime for Buster is OpenJDK 11 and the > packages have to work properly with it. > Thank you for this clarification. I agree that we should switch to OpenJDK 11 as soon as there is an upstream version available that allows this. Since openjdk-8 is going to be kept in Buster, I don't think we need to keep this bug at RC severity. I'm concerned that keeping this bug at RC severity might risk having libbluray being removed from testing, which I don't think is in the best interest of our users. -- regards, Reinhard
Bug#918421: Bug #918421 in node-prelude-ls marked as pending
Control: tag -1 pending Hello, Bug #918421 in node-prelude-ls reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-prelude-ls/commit/2c1937d104beff0437796965720bfa1f2e7b8718 Add patch to disable failing tests (reported to upstream) Closes: #918421) (this message was generated automatically) -- Greetings https://bugs.debian.org/918421
Processed: Re: Bug#920227: possible fix
Processing control commands: > tags -1 +patch Bug #920227 [sbuild] invalid file format generated for dependencies Added tag(s) patch. > notfound -1 0.77.1-2 Bug #920227 [sbuild] invalid file format generated for dependencies Ignoring request to alter found versions of bug #920227 to the same values previously set > found -1 0.78.0-2 Bug #920227 [sbuild] invalid file format generated for dependencies Ignoring request to alter found versions of bug #920227 to the same values previously set > forwarded -1 https://salsa.debian.org/debian/sbuild/merge_requests/5 Bug #920227 [sbuild] invalid file format generated for dependencies Set Bug forwarded-to-address to 'https://salsa.debian.org/debian/sbuild/merge_requests/5'. -- 920227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #918421 in node-prelude-ls marked as pending
Processing control commands: > tag -1 pending Bug #918421 [src:node-prelude-ls] node-prelude-ls FTBFS with nodejs 10.15.0 Added tag(s) pending. -- 918421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920227: possible fix
Control: tags -1 +patch
Control: notfound -1 0.77.1-2
Control: found -1 0.78.0-2
Control: forwarded -1 https://salsa.debian.org/debian/sbuild/merge_requests/5
I have verified this is a regression from 0.77.1. I can also confirm
there is an easy fix, attached and forwarded.
Thanks to James Clark for the patch, described on #debian-devel. :)
Cheers,
A.
--
I've got to design so you can put it together out of garbage cans. In
part because that's what I started from, but mostly because I don’t
trust the industrial structure—they might decide to suppress us
weirdos and try to deny us the parts we need.
- Lee Felsenstein
>From e3447e992c33f6162441aa757e2ab273afae2497 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?=
Date: Tue, 22 Jan 2019 17:16:05 -0500
Subject: [PATCH] fix syntax of generated Sources.gz files (Closes: #920227)
The rewrite of dpkg-scan* performed to fix #909847 introduced a
problem in 18f423619c176471d2adaafb7742cb204951a10c: Sources.gz
entries are not correctly separated by a newline. Furthermore, they
have Source: entries instead of Package:
This confuses older version of APT (previous to jessie) which have
extra sanity checks on the contents of those files, which breaks
building in older chroots.
---
lib/Sbuild/ResolverBase.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/Sbuild/ResolverBase.pm b/lib/Sbuild/ResolverBase.pm
index 6399c350..71dda196 100644
--- a/lib/Sbuild/ResolverBase.pm
+++ b/lib/Sbuild/ResolverBase.pm
@@ -1412,6 +1412,7 @@ sub hash_file($$)
open my $in, '<', $entry or die "cannot open $entry";
while (my $line = <$in>) {
next if $line eq "\n";
+ $line =~ s/^Source:/Package:/;
print $out $line;
if ($line eq "Checksums-Sha1:\n") {
print $out " $sha1 $size $entry\n";
@@ -1439,6 +1440,7 @@ sub hash_file($$)
}
print $out "Directory: .";
print $out "\n";
+ print $out "\n";
}
close $out;
closedir($dh);
--
2.20.1
Processed: bug 918421 is forwarded to https://github.com/gkz/prelude-ls/issues/116, tagging 918421
Processing commands for cont...@bugs.debian.org: > forwarded 918421 https://github.com/gkz/prelude-ls/issues/116 Bug #918421 [src:node-prelude-ls] node-prelude-ls FTBFS with nodejs 10.15.0 Set Bug forwarded-to-address to 'https://github.com/gkz/prelude-ls/issues/116'. > tags 918421 + upstream Bug #918421 [src:node-prelude-ls] node-prelude-ls FTBFS with nodejs 10.15.0 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 918421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920227: invalid file format generated for dependencies
Package: sbuild Version: 0.78.0-2 Severity: grave Tags: upstream Since the 0.78 upgrade, sbuild cannot build packages in jessie (and maybe other suites). The build during the setup phase, while trying to install the build-dependencies, with this error message: W: Failed to fetch gzip:/var/lib/apt/lists/partial/_build_systemd-asEYMr_resolver-48eHqy_apt%5farchive_._Sources.gz Invalid file format It looks like the Sources.gz generated for the build-dependencies resolver is incorrectly formatted, which freaks out apt in the chroot. This does not happen with sbuild 0.77.1-2. This seems to be a regression introduced in this commit: https://salsa.debian.org/debian/sbuild/commit/18f423619c176471d2adaafb7742cb204951a10c ... which was implemented to close bug #909847. In there, sbuild reimplements dpkg-scanpackages and dpkg-scansources internally, but it seems to do so incorrectly. Attached are the build logs and the faulty Sources.gz files. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sbuild depends on: ii adduser 3.118 ii libsbuild-perl 0.78.0-2 ii perl5.28.1-3 Versions of packages sbuild recommends: ii autopkgtest 5.8 ii debootstrap 1.0.114 ii schroot 1.6.10-6+b1 Versions of packages sbuild suggests: ii deborphan 1.7.31 ii e2fsprogs 1.44.5-1 ii kmod 25-2 ii wget 1.20.1-1 -- debconf-show failed sources.gz Description: application/gzip sbuild (Debian sbuild) 0.78.0 (09 January 2019) on curie.anarc.at +==+ | systemd 215-17+deb8u9 (amd64)Tue, 22 Jan 2019 21:39:27 + | +==+ Package: systemd Version: 215-17+deb8u9 Source Version: 215-17+deb8u9 Distribution: UNRELEASED Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/jessie-amd64-sbuild-3b476c6c-1cda-4a37-bd77-e77297a487a8' with '<>' I: NOTICE: Log filtering will replace 'build/systemd-x72Uu1/resolver-0MCIZ4' with '<>' +--+ | Update chroot| +--+ Ign http://deb.debian.org jessie InRelease Hit http://security.debian.org jessie/updates InRelease Hit http://deb.debian.org jessie-backports InRelease Hit http://deb.debian.org jessie Release.gpg Hit http://security.debian.org jessie/updates/main amd64 Packages Get:1 http://deb.debian.org jessie-backports/main amd64 Packages/DiffIndex [27.8 kB] Hit http://security.debian.org jessie/updates/contrib amd64 Packages Hit http://deb.debian.org jessie Release Hit http://security.debian.org jessie/updates/non-free amd64 Packages Hit http://deb.debian.org jessie/main Sources Hit http://deb.debian.org jessie/main amd64 Packages Fetched 27.8 kB in 2s (12.7 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Local sources - /home/anarcat/dist/systemd_215-17+deb8u9.dsc exists in /home/anarcat/dist; copying to chroot I: NOTICE: Log filtering will replace 'build/systemd-x72Uu1/systemd-215' with '<>' I: NOTICE: Log filtering will replace 'build/systemd-x72Uu1' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper (>= 9), pkg-config, xsltproc, docbook-xsl, docbook-xml, gtk-doc-tools, m4, dh-autoreconf, automake (>= 1.11), autoconf (>= 2.63), intltool, gperf, libcap-dev, libpam0g-dev, libaudit-dev, libdbus-1-dev (>= 1.3.2), libglib2.0-dev (>= 2.22.0), libcryptsetup-dev (>= 2:1.6.0), libselinux1-dev (>= 2.1.9), libacl1-dev, liblzma-dev, libgcrypt11-dev, libkmod-dev (>= 15), libblkid-dev (>= 2.20), libgirepository1.0-dev (>= 1.31.1), gobject-introspection (>= 1.31.1), python3-all-dev, python3-lxml, libglib2.0-doc, build-essential, fakeroot
Bug#917884: marked as done (mate-dock-applet: Adding a new dock does nothing)
Your message dated Tue, 22 Jan 2019 21:50:07 + with message-id and subject line Bug#917884: fixed in mate-dock-applet 0.87-2 has caused the Debian Bug report #917884, regarding mate-dock-applet: Adding a new dock does nothing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mate-dock-applet Version: 0.87-1 Severity: grave Dear Maintainer, After a recent system upgrade, I've lost the dock applet. It is no longer shown on the panel. As said in the subject, adding a new one does nothing. No new dock is shown on the panel either. This upgrade I did, did not affect the mate-dock-applet package itself, so it might be a problem with one of its dependencies instead. I've tried downgrading to version 0.75-1 but it didn't work. I also tried downgrading the following dependencies with no luck: gir1.2-freedesktop:amd64 (1.58.3-1 > 1.58.2-2) gir1.2-glib-2.0:amd64 (1.58.3-1 > 1.58.2-2) gir1.2-notify-0.7:amd64 (0.7.7-4 > 0.7.7-2) I'm sorry I couldn't help further, my knowledge here is limited. Please let me know if there's anything else I could try to debug this. Thanks a lot, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-dock-applet depends on: ii bamfdaemon 0.5.4-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gir1.2-bamf-30.5.4-1 ii gir1.2-gdkpixbuf-2.0 2.38.0+dfsg-7 ii gir1.2-glib-2.0 1.58.3-1 ii gir1.2-gtk-3.0 3.24.2-3 ii gir1.2-mate-panel1.20.3-1 ii gir1.2-notify-0.70.7.7-4 ii gir1.2-wnck-3.0 3.30.0-2 ii libglib2.0-bin 2.58.1-2 ii mate-panel 1.20.3-1 ii python3 3.7.1-3 ii python3-gi-cairo 3.30.4-1 ii python3-pil 5.3.0-1 ii python3-xdg 0.25-4 ii python3-xlib 0.23-2 mate-dock-applet recommends no packages. mate-dock-applet suggests no packages. -- no debconf information -- Rock Storm GPG KeyID: 4096R/C96832FD GPG Fingerprint: C304 34B3 632C 464C 2FAF C741 0439 CF52 C968 32FD --- End Message --- --- Begin Message --- Source: mate-dock-applet Source-Version: 0.87-2 We believe that the bug you reported is fixed in the latest version of mate-dock-applet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated mate-dock-applet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 22:32:53 +0100 Source: mate-dock-applet Binary: mate-dock-applet Architecture: source Version: 0.87-2 Distribution: unstable Urgency: medium Maintainer: Debian+Ubuntu Debian MATE Packaging Team Changed-By: Mike Gabriel Description: mate-dock-applet - MATE Panel dock applet Closes: 917884 Changes: mate-dock-applet (0.87-2) unstable; urgency=medium . * debian/control: + Bump Standards-Version: to 4.3.0. No changes needed. + Add D (mate-dock-applet): python3-dbus. (Closes: #917884). Checksums-Sha1: 31a96da61e7f1b079e77514b0ee042e6b134a145 2166 mate-dock-applet_0.87-2.dsc c8c44d73c8620703d836c495edb0a6ca2ac4d1cb 4004 mate-dock-applet_0.87-2.debian.tar.xz b4cec0c9b53f9dd00292d12230b48595f3052d1b 6900 mate-dock-applet_0.87-2_source.buildinfo Checksums-Sha256:
Bug#919443: marked as done (ifupdown2: leaves diversion after upgrade from stretch)
Your message dated Tue, 22 Jan 2019 21:49:30 + with message-id and subject line Bug#919443: fixed in ifupdown2 1.2.5-1 has caused the Debian Bug report #919443, regarding ifupdown2: leaves diversion after upgrade from stretch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifupdown2 Version: 1.2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove some diversions after upgrading from stretch and removing the package afterwards. >From the attached log (scroll to the bottom...): 0m51.2s ERROR: FAIL: Installed diversions (dpkg-divert) not removed by purge: diversion of /sbin/ifreload to /sbin/ifreload.disabled by ifupdown2 diversion of /etc/bash_completion.d/ifdown to /etc/bash_completion.d/ifdown.disabled by ifupdown2 diversion of /usr/share/man/man8/ifup.8.gz to /usr/share/man/man8/ifup.8.gz.disabled by ifupdown2 diversion of /usr/share/man/man8/ifquery.8.gz to /usr/share/man/man8/ifquery.8.gz.disabled by ifupdown2 diversion of /usr/share/bash-completion/completions/ifquery to /usr/share/bash-completion/completions/ifquery.disabled by ifupdown2 diversion of /usr/share/bash-completion/completions/ifdown to /usr/share/bash-completion/completions/ifdown.disabled by ifupdown2 diversion of /sbin/ifquery to /sbin/ifquery.disabled by ifupdown2 diversion of /sbin/ifdown to /sbin/ifdown.disabled by ifupdown2 diversion of /etc/bash_completion.d/ifup to /etc/bash_completion.d/ifup.disabled by ifupdown2 diversion of /sbin/ifup to /sbin/ifup.disabled by ifupdown2 diversion of /usr/share/man/man5/interfaces.5.gz to /usr/share/man/man5/interfaces.5.gz.disabled by ifupdown2 diversion of /usr/share/man/man8/ifreload.8.gz to /usr/share/man/man8/ifreload.8.gz.disabled by ifupdown2 diversion of /usr/share/man/man8/ifdown.8.gz to /usr/share/man/man8/ifdown.8.gz.disabled by ifupdown2 diversion of /usr/share/bash-completion/completions/ifreload to /usr/share/bash-completion/completions/ifreload.disabled by ifupdown2 diversion of /etc/bash_completion.d/ifquery to /etc/bash_completion.d/ifquery.disabled by ifupdown2 diversion of /etc/bash_completion.d/ifreload to /etc/bash_completion.d/ifreload.disabled by ifupdown2 diversion of /usr/share/bash-completion/completions/ifup to /usr/share/bash-completion/completions/ifup.disabled by ifupdown2 If these diversions were used in stretch, but not afterwards, you should remove them in the postinst script, i.e. on package upgrade. cheers, Andreas ifupdown2_1.2.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ifupdown2 Source-Version: 1.2.5-1 We believe that the bug you reported is fixed in the latest version of ifupdown2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Fortin (supplier of updated ifupdown2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Jan 2019 23:42:42 +8000 Source: ifupdown2 Binary: ifupdown2 Architecture: source all Version: 1.2.5-1 Distribution: unstable Urgency: medium Maintainer: Julien Fortin Changed-By: Julien Fortin Description: ifupdown2 - Network Interface Management tool similar to ifupdown Closes: 918775 919443 Changes: ifupdown2 (1.2.5-1) unstable; urgency=medium . * Fix: ifupdown2 scripts: log warning on EACCES exception (Fixes #89) * Fix: debian: install sysvinit script (closes: #918775) * Fix: debian: postinst: remove diversion after upgrade from stretch (closes: #919443) Checksums-Sha1: c7d206fe307579438ee3ebf189d1c0a833467ece 1803 ifupdown2_1.2.5-1.dsc df26f1dfab17e1ee97c889a726bab08f8b48f2cf 281408 ifupdown2_1.2.5.orig.tar.xz 75bfbd50606115f487965bb9cdded9d0e33cf285 8364 ifupdown2_1.2.5-1.debian.tar.xz 5b930280c5be2bba099fe8086b3ccfb23161d70f 196184 ifupdown2_1.2.5-1_all.deb 7a89d646141f8c41fa839a85148244203e4d31db 6526
Processed: notfound 919213 in 1.5.0-2
Processing commands for cont...@bugs.debian.org:
> notfound 919213 1.5.0-2
Bug #919213 {Done: Axel Beckert } [irqbalance] irqbalance:
endless loop during configure, system reaches maximum of open files
No longer marked as found in versions irqbalance/1.5.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug #917884 in mate-dock-applet marked as pending
Processing control commands: > tag -1 pending Bug #917884 [mate-dock-applet] mate-dock-applet: Adding a new dock does nothing Added tag(s) pending. -- 917884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912410: marked as done (python-igraph's tests fail with Python 3.7)
Your message dated Tue, 22 Jan 2019 21:35:04 +
with message-id
and subject line Bug#912410: fixed in python-igraph 0.7.1.post6-6
has caused the Debian Bug report #912410,
regarding python-igraph's tests fail with Python 3.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
912410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-igraph
Version: 0.7.1.post6-5
Severity: serious
Tags: sid buster
python-igraph's tests fail with Python 3.7, RC severity for the upcoming Python
3.7 transition.
testMSTofGRG (igraph.test.homepage.HomepageExampleTests) ... ok
==
ERROR: testFormula (igraph.test.generators.GeneratorTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/generators.py", line 72, in testFormula
g = Graph.Formula(formula)
File "/<>/igraph/formula.py", line 209, in
construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
File "/<>/igraph/formula.py", line 90, in generate_edges
raise SyntaxError(msg)
SyntaxError: invalid token found in edge specification: A
==
ERROR: testEigenvectorCentrality (igraph.test.structural.CentralityTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/structural.py", line 301, in
testEigenvectorCentrality
cent = g.evcent()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization
==
ERROR: testCohesiveBlocks2 (igraph.test.decomposition.CohesiveBlocksTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/decomposition.py", line 339, in
testCohesiveBlocks2
g = Graph.Formula("1-2:3:4:5:6, 2-3:4:5:7, 3-4:6:7, 4-5:6:7, "
File "/<>/igraph/formula.py", line 209, in
construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
File "/<>/igraph/formula.py", line 90, in generate_edges
raise SyntaxError(msg)
SyntaxError: invalid token found in edge specification: 1-2:3:4:5:6
==
ERROR: testAuthorityScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization
==
ERROR: testHubScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization
==
ERROR: testAuthorityScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization
==
ERROR: testHubScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization
==
FAIL: testEigenvectorCentrality (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
File "/<>/igraph/test/atlas.py", line 35, in
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for graph
#%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #5: Error at
Bug#917884: Bug #917884 in mate-dock-applet marked as pending
Control: tag -1 pending Hello, Bug #917884 in mate-dock-applet reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-mate-team/mate-dock-applet/commit/6582c01b59014eaee6f731b947e6310042a5eea6 debian/control: Add D (mate-dock-applet): python3-dbus. (Closes: #917884). (this message was generated automatically) -- Greetings https://bugs.debian.org/917884
Bug#877507: ppx-core FTBFS: E: Cannot find external tool 'ocamlbuild'
This can easily be fixed by adding ocamlbuild to the build-dependencies. But then: File "src/gen/common.ml", line 73, characters 24-34: Error: This expression has type Types.constructor_arguments but an expression was expected of type Types.type_expr list Command exited with code 2. -Ralf
Processed: bug 886664 is forwarded to https://github.com/d3/d3-timer/issues/37, tagging 886664
Processing commands for cont...@bugs.debian.org: > forwarded 886664 https://github.com/d3/d3-timer/issues/37 Bug #886664 [src:node-d3-timer] node-d3-timer FTBFS: test failure Set Bug forwarded-to-address to 'https://github.com/d3/d3-timer/issues/37'. > tags 886664 + upstream Bug #886664 [src:node-d3-timer] node-d3-timer FTBFS: test failure Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 886664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920226: gnome-menus: No menu categories displayed in budgie-desktop
Package: gnome-menus Version: 3.31.4-2 Severity: serious Justification: Policy 1.1 Dear Maintainer, Testing on Ubuntu Budgie 19.04 which has a patched version of v3.31.4-2 currently in Sid demonstrated a serious issue in budgie-desktop. No menu categories were visible. I then refreshed my Buster installation with the latest packages and confirmed that v3.31.4-2 had not yet migrated. Budgie Desktop correctly displayed menu-categories. I then downloaded the Sid version v3.31.4-2 gnome-menus and installed the binary. Immediately no menu categories were visible when the menu applet was opened. I rebooted to confirm that the issue is still present. I've marked this as Serious after consultation with Jeremy B (the last uploader of the package). I have also tried reverting the "Sundry" menu handling in budgie-desktop - Sundry is a menu category that has been removed by the new version of gnome-menus. This has not resolved the issue. Thus the problem is not immediately obvious to be due to budgie-desktop. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-menus depends on: ii python3 3.7.1-3 gnome-menus recommends no packages. gnome-menus suggests no packages. -- no debconf information
Bug#919965: marked as done (unyaffs: Non-working maintainer address)
Your message dated Tue, 22 Jan 2019 21:00:07 + with message-id and subject line Bug#919965: fixed in unyaffs 0.9.7-0.2 has caused the Debian Bug report #919965, regarding unyaffs: Non-working maintainer address to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unyaffs Version: 0.9.7-0.1 Severity: serious Justification: Policy 3.3 A working maintainer address is required: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: matthew.fisc...@ubuntu.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table Date: Sun, 06 Jan 2019 23:30:37 +0200 Source: unyaffs Binary: unyaffs Architecture: source Version: 0.9.7-0.1 Distribution: unstable Urgency: medium Maintainer: Matthew Fischer Changed-By: Adrian Bunk Scott K --- End Message --- --- Begin Message --- Source: unyaffs Source-Version: 0.9.7-0.2 We believe that the bug you reported is fixed in the latest version of unyaffs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier (supplier of updated unyaffs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Jan 2019 13:22:14 -0700 Source: unyaffs Binary: unyaffs Architecture: source Version: 0.9.7-0.2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: dann frazier Description: unyaffs- Extracts files from a YAFFS2 filesystem image Closes: 919965 Changes: unyaffs (0.9.7-0.2) unstable; urgency=medium . * Non-maintainer upload. * Package has been orphaned as per #920202 (and verified out-of-band). Therefore, change maintainer to Debian QA Group. (Closes: #919965) Checksums-Sha1: 7f77bf60cb523af4668688f801e32931a72157dd 1738 unyaffs_0.9.7-0.2.dsc 480994108aef39e163244751c0433ab0591b197c 1816 unyaffs_0.9.7-0.2.debian.tar.xz d42ffd5ca9afcc266aed19493843baff7e89 5521 unyaffs_0.9.7-0.2_source.buildinfo Checksums-Sha256: 1b5f21382a08a7e5799eb5d273db72f189b704b4b1e79da2a1f043215035 1738 unyaffs_0.9.7-0.2.dsc 7b6d35d0ce245ea1e12e0f130bec6819a1771cb391529cfdad38071c7a0e81c1 1816 unyaffs_0.9.7-0.2.debian.tar.xz 6a443996acb116c7332c0480ead2c04d1c1f48e81cbe19298ca41c20a77675fa 5521 unyaffs_0.9.7-0.2_source.buildinfo Files: b2c44883b6ac9d0606f770e785e10b05 1738 devel optional unyaffs_0.9.7-0.2.dsc 6bc708912aca753643c961bdd60dee05 1816 devel optional unyaffs_0.9.7-0.2.debian.tar.xz 6aa838b74863cdb7e5df419b2a1fe901 5521 devel optional unyaffs_0.9.7-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEECfR9vy0y7twkQ+vuG/g8XlT8hkAFAlxHfOMRHGRhbm5mQGRl Ymlhbi5vcmcACgkQG/g8XlT8hkBnBA//Z5DNnC1tk9KPnMY22S4kUTmoviKJXL/q ExHBu07+sDo9SjwKR14G3PHbcJgxvXYJQnSGejeKcXxAt+N71GqWuRMeKgwmW3hy Qw7ryA6U/sbY2iVX3g/9Gc9Eix2t+QM5xtMymbRbb5++M+p4HhgIdYe8M5WPqSD0 zu2RTBmT7t3fPA105z0KOJnaskluiOgBsCgkTPdBGnI+XvckMBLtMMSgsX7p/Zag ERkI/H61mVOuXQ7YQ2LQBxW/9fh8DcCjjtRLEvKnrh1fpSAbS6h/RPjWHX7TLOv2 K2Vo5xQd+EM51lFXdzOJFlF6/lPlaYxoZkJrkevcY7HViuokCzoIW5O7YKhiLKl2 ruWtKZjKXtJnuJIyrk+cK3AI5BM4mh+XCDTeRYqA1WNYvmsCwZyUgE/Plzx7snBD rpLeOTtljcdYXg7HI5b35k5j1Ip5G6IgKZc2heW8x6ncZFD6i4XFrKeW9/YRvgLG 7H95Q2dCaNXaNjjgXC5oihs3gVGgUNEnLx8owBZdeetRhtnEpziP3RYHG/jaRU3m dblYLBU6xTt2eQwZtNJxhmE/F9aN4ZbuJ3SoSlSRdVvM4QKZnYKwaE+udsUIKUDJ OyHnmS2FPX75UbPhtlGe+SfHKoBbqGiYbZybMP9wSGggn3IU2f12N4HT75d0uWWB WN32DIMoUGI= =qa9n -END PGP SIGNATURE End Message ---
Bug#917500: marked as done (liggghts: FTBFS (style_atom.h: No such file or directory))
Your message dated Tue, 22 Jan 2019 20:58:05 + with message-id and subject line Bug#917500: fixed in liggghts 3.8.0+repack1-4 has caused the Debian Bug report #917500, regarding liggghts: FTBFS (style_atom.h: No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:liggghts Version: 3.8.0+repack1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=cmake --builddirectory=/<>/liggghts-3.8.0+repack1/debian/build dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build dh_autoreconf -i -O--buildsystem=cmake -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build dh_auto_configure -i -O--buildsystem=cmake -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ../.. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done [... snipped ...] CMAKE_EXPORT_NO_PACKAGE_REGISTRY -- Build files have been written to: /<>/liggghts-3.8.0+repack1/debian/build dh_auto_build -i -O--buildsystem=cmake -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build cd debian/build && make -j1 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build' /usr/bin/cmake -S/<>/liggghts-3.8.0+repack1 -B/<>/liggghts-3.8.0+repack1/debian/build --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles /<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build' make -f src/CMakeFiles/libliggghts.dir/build.make src/CMakeFiles/libliggghts.dir/depend make[3]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build' cd /<>/liggghts-3.8.0+repack1/debian/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<>/liggghts-3.8.0+repack1 /<>/liggghts-3.8.0+repack1/src /<>/liggghts-3.8.0+repack1/debian/build /<>/liggghts-3.8.0+repack1/debian/build/src /<>/liggghts-3.8.0+repack1/debian/build/src/CMakeFiles/libliggghts.dir/DependInfo.cmake --color= Scanning dependencies of target libliggghts make[3]: Leaving directory '/<>/liggghts-3.8.0+repack1/debian/build' make -f src/CMakeFiles/libliggghts.dir/build.make src/CMakeFiles/libliggghts.dir/build make[3]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build' [ 0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle.cpp.o cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx -Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" -DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" -DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)" -I/usr/include/vtk-6.3 -I/usr/include/freetype2 -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp -I/usr/include/eigen3 -I/<>/liggghts-3.8.0+repack1 -I/<>/liggghts-3.8.0+repack1/src -g -O2 -fdebug-prefix-map=/<>/liggghts-3.8.0+repack1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC -o CMakeFiles/libliggghts.dir/angle.cpp.o -c /<>/liggghts-3.8.0+repack1/src/angle.cpp [ 0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx -Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)"
Processed: Bug #912410 in python-igraph marked as pending
Processing control commands: > tag -1 pending Bug #912410 [src:python-igraph] python-igraph's tests fail with Python 3.7 Added tag(s) pending. -- 912410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917884: mate-dock-applet: Adding a new dock does nothing
On Tue, Jan 22, 2019 at 10:25:24AM +, Mike Gabriel wrote: > I think, the missing dependency is python3-dbus. > > Do you think you can re-test the installation procedure, reproduce this bug > and then try to install python3-dbus and see if that fixes things? If I You are right. Went back to system status with the non-working mate dock. Installed just 'python3-dbus' and dock was back again in the panel. I wish I could provide some kind of tracebacks here but I'm relying purely on whether I see the panel or not. > The question is: is python3-dbus the only dep that is missing. All I can say for certain is that 'python3-dbus' is the only dependency I was missing. If another dependency is missing from the list but I happen to have it installed by any chance, I could not say. Thanks, -- Rock Storm GPG KeyID: 4096R/C96832FD GPG Fingerprint: C304 34B3 632C 464C 2FAF C741 0439 CF52 C968 32FD signature.asc Description: PGP signature
Bug#912410: Bug #912410 in python-igraph marked as pending
Control: tag -1 pending
Hello,
Bug #912410 in python-igraph reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/modules/python-igraph/commit/0a493106dbb3eef393167a11e33099d2055f5407
Disable buggy tests causing FTBFS
* Thanks to Nicolas Boulenguez for his patch suggestions !
* debian/patches:
- Disable buggy tests causing FTBFS (Closes: #912410).
- Refresh patches.
* Bump compat to 11.
* debian/control:
- Bump Standards-Version to 4.3.0.
- Add python{3,}-numpy test dependency.
- Add python{3,}-texttable dependency, stop using version from vendors/.
- Bump debhelper dependency to >= 11.
- Enable autopkgtest.
* Bump copyright years.
* Convert to git-dpm and run wrap-and-sort -a.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/912410
Processed: Re: screenie-qt: Should this package be removed?
Processing control commands: > severity -1 serious Bug #904374 [src:screenie-qt] screenie-qt: Should this package be removed? Severity set to 'serious' from 'important' -- 904374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920223: gnome-keysign: fails to build because of test failures
Source: gnome-keysign Version: 1.0.1-1 Severity: serious Tags: ftbfs gnome-keysign fails to build from source in a clean unstable chroot as seen on Ubuntu and with Debian Reproducible Builds. The build tests are failing. By the way, I encourage you to do source-only uploads: https://wiki.debian.org/SourceOnlyUpload Build logs - https://launchpad.net/ubuntu/+source/gnome-keysign/1.0.1-1/+build/16309497 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-keysign.html Thanks, Jeremy Bicha
Bug#920220: apache2: CVE-2019-0190: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1
Source: apache2 Version: 2.4.37-1 Severity: grave Tags: patch security upstream Hi (Stefan), I agree the severity is not the best choosen one for this issue, it is more to ensure we could release buster with an appropriate fix already before the release. If you disagree, please do downgrade. The following vulnerability was published for apache2. CVE-2019-0190[0]: mod_ssl 2.4.37 remote DoS when used with OpenSSL 1.1.1 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-0190 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0190 [1] https://marc.info/?l=oss-security=154817901921421=2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: Re: Bug#920136: libgnutls30: symbol lookup error...undefined symbol: __gmpz_limbs_write
Processing control commands: > severity -1 serious Bug #920136 [libgnutls30] libgnutls30: symbol lookup error...undefined symbol: __gmpz_limbs_write Severity set to 'serious' from 'critical' -- 920136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911620: marked as done (shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster)
Your message dated Tue, 22 Jan 2019 18:49:41 + with message-id and subject line Bug#911620: fixed in dpkg 1.19.3 has caused the Debian Bug report #911620, regarding shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 911620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: shared-mime-info,gconf2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 1.10-1 Control: found -1 3.2.6-5 Control: affects -1 + microhope Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log (scroll to the bottom...): Setting up libgl1-mesa-glx:amd64 (18.1.7-1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: shared-mime-info -> gconf2 packages' pending triggers which are or may be unresolvable: shared-mime-info: /usr/share/mime/packages libc-bin: ldconfig gconf2: /usr/share/gconf/schemas dpkg: error processing package shared-mime-info (--configure): triggers looping, abandoned This was observed during a 2-stage upgrade from stretch to buster: apt-get upgrade && apt-get dist-upgrade Both shared-mime-info and gconf2 were already upgraded successfully during the first stage. The package being tested was microhope. IIRC shared-mime-info switched to no-await triggers - so this trigger cycle problem should have vanished... cheers, Andreas microhope_4.4.4+dfsg-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: dpkg Source-Version: 1.19.3 We believe that the bug you reported is fixed in the latest version of dpkg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated dpkg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Jan 2019 14:26:04 +0100 Source: dpkg Architecture: source Version: 1.19.3 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers Changed-By: Guillem Jover Closes: 810724 818618 854478 901127 910707 910734 910819 911620 912023 912024 913012 913816 914478 915610 915881 916056 916456 916799 917098 917813 Changes: dpkg (1.19.3) unstable; urgency=medium . [ Guillem Jover ] * dpkg-source: Stop filtering @builddeps@ from Testsuite-Triggers field. Closes: #910734 * dpkg-genchanges: Only reference binary packages being uploaded, which means that for a source-only upload, the Binary and Description fields should be empty. Closes: #818618 * dpkg-scanpackages: Do not compute unnecessary checksums when using the --hash argument. Based on a patch by Chris Lamb . Closes: #916456 * dpkg-scanpackages: Emit a warning with the list of repeat packages. Prompted by Johannes Schauer . * start-stop-daemon: Check whether standalone --pidfile use is secure. Prompted by Michael Orlitzky . * start-stop-daemon: Print complete verbose lines, instead of partial lines with no newlines and a final print with a newline. * start-stop-daemon: Add new --notify-await and --notify-timeout options, which implement the systemd readiness protocol for services. Closes: #910707 * update-alternatives: Add new --debug option. * update-alternatives: Fix removal of obsolete slaves from the linked list. Reported by Andreas Beckmann . Closes: #916799 * vendor.mk: Fix dpkg_vendor_derives_from macro documentation. Thanks to Colin Watson . Closes: #913816 * vendor.mk: Add support for an improved dpkg_vendor_derives_from macro. Version the macros so that both can be used, and default the unversioned one to the version 0 macro. * dpkg: Mark the package we are giving up on a trigger cycle as "istobe" normal, so that the dependency checks know they cannot expect this package to be processed anymore.
Bug#920136: libgnutls30: symbol lookup error...undefined symbol: __gmpz_limbs_write
Control: severity -1 serious On 2019-01-22 James Van Zandt wrote: > Package: libgnutls30 > Version: 3.6.5-2 > Severity: critical > Justification: breaks unrelated software Hello, I am downgrading severity. apt is not "unrelated", it *uses* gnutls. > Dear Maintainer, > Sun 20 Jan 2019 10:25:49 PM EST > I upgraded several packages on Jan 16. Since then, many programs > (including cupsd, apt-get, and apt) fail like this: > /usr/lib/apt/methods/http: symbol lookup error: > /usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: > __gmpz_limbs_write Could you please show which package versions are installed? dpkg -l libc6 libgmp10 libhogweed4 libidn2-0 libnettle6 libp11-kit0 libtasn1-6 libunistring2 Does ldd -r /usr/lib/apt/methods/http reproduce the error? [...] > Searching for libraries that refer to that symbol: > jrv@home:/usr/lib/x86_64-linux-gnu$ grep __gmpz_limbs_write > libgnutls.so.30 > ...so it's apparently not used or defined in version 3.5.19-1 of that file. > (It also wasn't mentioned in version 3.6.5-2 of the file.) > jrv@home:/usr/lib/x86_64-linux-gnu$ grep __gmpz_limbs_write *.so* > grep: libcasa_python3.so: No such file or directory > Binary file libgmp.so matches > Binary file libgmp.so.10 matches > Binary file libgmp.so.10.3.2 matches > grep: libgnutls.so: No such file or directory ^ That looks fishy. /usr/lib/x86_64-linux-gnu/libgnutls.so should either not exist (libgnutls28-dev not installed) or not be a broken symlink. I suspect second local installation of gmp/nettle/gnutls in /usr/local. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#920209: galera-3: FTBFS on mipsel
Source: galera-3 Version: 25.3.25-1 Severity: serious Tags: ftbfs Control: block 904316 by -1 Dear maintainer, your new upload of galera-3 FTBFS on mipsel. https://buildd.debian.org/status/fetch.php?pkg=galera-3=mipsel=25.3.25-1=1547845354=0 It seems to be a failed test of sort: | Running suite(s): gu::RecordSet | 83%: Checks: 6, Failures: 0, Errors: 1 | galerautils/tests/gu_rset_test.cpp:395:E:RecordSet v1:ver1:0: (after this point) Test timeout expired It has already been tried twice, so it's not a transient thing. Incidentally, this seems to be the last blocker to remove boost1.62 from testing (once 2 other packages are (auto)removed and third migrates), so please do fix it :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: galera-3: FTBFS on mipsel
Processing control commands: > block 904316 by -1 Bug #904316 [release.debian.org] transition: boost-defaults 904316 was not blocked by any bugs. 904316 was not blocking any bugs. Added blocking bug(s) of 904316: 920209 -- 904316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904316 920209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917725: marked as done (python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Tue, 22 Jan 2019 18:19:49 + with message-id and subject line Bug#917725: fixed in python-acora 2.2-1 has caused the Debian Bug report #917725, regarding python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-acora Version: 2.1-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f acora/_acora.c acora/_cacora.c > dh_auto_clean > I: pybuild base:217: python2.7 setup.py clean > WARNING: Generated .c files are missing, enabling Cython compilation > Building with Cython 0.28.4 > Compiling acora/_acora.py because it changed. > Compiling acora/_cacora.pyx because it changed. > [1/2] Cythonizing acora/_acora.py > [2/2] Cythonizing acora/_cacora.pyx > running clean > removing '/<>/.pybuild/cpython2_2.7_acora/build' (and everything > under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-2.7' does not exist -- can't clean it > I: pybuild base:217: python3.7 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.7_acora/build' (and everything > under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-3.7' does not exist -- can't clean it > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-acora using existing > ./python-acora_2.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > python-acora-2.1/acora/_acora.c > python-acora-2.1/acora/_acora.html > python-acora-2.1/acora/_cacora.c > python-acora-2.1/acora/_cacora.html > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-acora_2.1-1.diff.T8mOsr > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2018-12-29T12:29:03Z The full build log is available from: http://aws-logs.debian.net/2018/12/29/python-acora_2.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: python-acora Source-Version: 2.2-1 We believe that the bug you reported is fixed in the latest version of python-acora, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated python-acora package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 18:58:57 +0100 Source: python-acora Binary: python-acora python3-acora Architecture: source Version: 2.2-1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Description: python-acora - fast multi-keyword text search engine (Python 2) python3-acora - fast multi-keyword text search engine (Python 3) Closes: 917725 Changes: python-acora (2.2-1) unstable; urgency=medium . * New upstream version 2.2 - Builds just fine (Closes: 917725) * Bump Debhelper compat level * Bump Standards-Version * Drop patch Checksums-Sha1: f961977469d39bdff66734cbe1f0796083acd55e 2079 python-acora_2.2-1.dsc
Processed: Re: kopanocore: wrong installation directories
Processing commands for cont...@bugs.debian.org: > found 920189 8.6.92-1 Bug #920189 [src:kopanocore] kopanocore: wrong installation directories Marked as found in versions kopanocore/8.6.92-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 920189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: kopanocore: wrong installation directories
Processing commands for cont...@bugs.debian.org: > severity 920189 serious Bug #920189 [src:kopanocore] kopanocore: wrong installation directories Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 920189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919356: Fw: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear
[need to re-CC debian-legal again, sorry.] On Tue, Jan 22, 2019 at 06:05:37PM +0100, Domenico Andreoli wrote: > On Mon, Jan 21, 2019 at 03:58:19PM +, MJ Ray wrote: > > Missed the bug off the CC for this. Sorry. > > It seems it did not arrive to debian-legal either. > > > Begin forwarded message: > > > > Date: Mon, 21 Jan 2019 13:34:13 + > > From: MJ Ray > > To: debian-le...@lists.debian.org > > Subject: Re: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear > > > > > > Domenico Andreoli skribis: > > > > > the situation of dwarves-dfsg improved a lot over the weekend, the > > > only knot left is now the license of hash.h > > > > > > This file is also present in the kernel [0] with an updated copyright > > > but still without license. > > > > > > I received a private email from somebody in the kernel community who > > > already tried to contact Nadia in the past but did not get any reply. > > > [...] > > > [0] > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/hash.h > > > > > > > One of the commits to that file is from Nadia. Sorry if I'm being > > dense, but where does the doubt that it is under the kernel's licence > > arise? > > The file does not mention any license. While the kernel has its blanket > license, dwarves has not any. > > Can I simply claim it's a GPL-2.0-only? I mean, I think it's reasonable > and, as you said, it's unlikely that Nadia did not notice it was in > the kernel but I wanted a second opinion. > > Do you thin I could even add the SPDX? > > Thanks, > Domenico > > -- > 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 -- 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 signature.asc Description: PGP signature
Bug#919356: Fw: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear
On Mon, Jan 21, 2019 at 03:58:19PM +, MJ Ray wrote: > Missed the bug off the CC for this. Sorry. It seems it did not arrive to debian-legal either. > Begin forwarded message: > > Date: Mon, 21 Jan 2019 13:34:13 + > From: MJ Ray > To: debian-le...@lists.debian.org > Subject: Re: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear > > > Domenico Andreoli skribis: > > > the situation of dwarves-dfsg improved a lot over the weekend, the > > only knot left is now the license of hash.h > > > > This file is also present in the kernel [0] with an updated copyright > > but still without license. > > > > I received a private email from somebody in the kernel community who > > already tried to contact Nadia in the past but did not get any reply. > > [...] > > [0] > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/hash.h > > > > One of the commits to that file is from Nadia. Sorry if I'm being > dense, but where does the doubt that it is under the kernel's licence > arise? The file does not mention any license. While the kernel has its blanket license, dwarves has not any. Can I simply claim it's a GPL-2.0-only? I mean, I think it's reasonable and, as you said, it's unlikely that Nadia did not notice it was in the kernel but I wanted a second opinion. Do you thin I could even add the SPDX? Thanks, Domenico -- 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 signature.asc Description: PGP signature
Bug#920173: marked as done (pmacct is missing build-dependencies)
Your message dated Tue, 22 Jan 2019 17:06:08 + with message-id and subject line Bug#920173: fixed in pmacct 1.7.2-3 has caused the Debian Bug report #920173, regarding pmacct is missing build-dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pmacct Version: 1.7.2-2 Severity: serious Tags: sid buster pmacct ftbfs everywhere, missing b-d: [...] checking for jansson.h... yes checking whether to enable Avro support... no checking whether to enable Confluent schema-registry support... no checking whether to enable nDPI support... yes checking for NDPI... yes checking for ndpi_init_detection_module in -lndpi... yes checking libndpi/ndpi_main.h usability... no checking libndpi/ndpi_main.h presence... no checking for libndpi/ndpi_main.h... no configure: error: ERROR: missing nDPI static library and probably missing Avro support/b-d as well --- End Message --- --- Begin Message --- Source: pmacct Source-Version: 1.7.2-3 We believe that the bug you reported is fixed in the latest version of pmacct, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernd Zeimetz (supplier of updated pmacct package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 17:45:45 +0100 Source: pmacct Binary: pmacct Architecture: source Version: 1.7.2-3 Distribution: unstable Urgency: medium Maintainer: Bernd Zeimetz Changed-By: Bernd Zeimetz Description: pmacct - promiscuous mode traffic accountant Closes: 920173 Changes: pmacct (1.7.2-3) unstable; urgency=medium . * [7e3d753] Disable ndpi again. Builds with 2.2, fails with 2.6. (Closes: #920173) Checksums-Sha1: 837494bc0b58ba9ba3edebc7632d5070cac7e4fb 2048 pmacct_1.7.2-3.dsc c266626932785b8970ed9df2f32c5a315aad8beb 12540 pmacct_1.7.2-3.debian.tar.xz 4fbadb38fdce9ec1830addfefb9226e684ac 7061 pmacct_1.7.2-3_source.buildinfo Checksums-Sha256: 233fae64ad4df354742434befc62d22d6eccf9f80ad238437c5bf54d593b3b9d 2048 pmacct_1.7.2-3.dsc 1843077d55ce9db26408ebaf5fd28192fea6ee1fa5d3ac4f8ca88d318b4fb177 12540 pmacct_1.7.2-3.debian.tar.xz 1457daa1522a31105e67a0fdeb7e715f083d544cfe02d50c6c3b3e708d139097 7061 pmacct_1.7.2-3_source.buildinfo Files: 90310a0d2ae4e0715b39058ec0b3ea95 2048 net optional pmacct_1.7.2-3.dsc 069d8da8cb14db4dcba11cc62ee19967 12540 net optional pmacct_1.7.2-3.debian.tar.xz 5a684fdfff76e121f43877f4497bb24a 7061 net optional pmacct_1.7.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAlxHSWoACgkQ6zYXGm/5 Q1+pRA//UOzLrrMFkZ+wHAbU03z/k+igAiIpBWb4Hv5PRdMsM/6MWqdxAk+yVyhh 01DckEe03stvdepk5d0d7cWi9FDJWXgda6HJnivogwZMHCxaD8NuSKJ/QM2Qiavo OUl9HexCrwwHS6dHxh9VQcoN1JdBhMQm9nAHbDu06r/JUu3NNtebSZZgiEfkE0NP L1L4n9MnBM1FgP/T5oSdBUQXV/lKahmAbVVDtn+ZNcDtLu3N8w0edcIw1OYHB/Yp 9oVI3i6wfgi6Hov+y838eofODzzB93MbEKy8SYU2O4Mr8hqARZ8eJhhQwB9/neZa l6ebFjqqVvh/52mwVoKziZiNAcB2nPmkA0dWui1eT5jGhRpcx6+mhVHJ2RQxrZt+ upNm2CZUxvF2t2qKZhJMvoj+bNRE4nOswhH1AVuxD8ANMyU0ls+RHMM5A/xEVyft I0KZIdUpGuGeg/A+OLxuQ4xELcWVH9YQZ8UCq5bRYob2euuaPa/O4pqbNYIW1W+r kLOpSRFfbT4QYAhr/6qSlbglLfyOMdzS5VPqeKi0WSpBT5RypXmkkuP+1tOK7+2G OWtMD54cJvK30WigYBXEwlbBF1S+Prg7n/3+thzM1TfHNjW1V3mKo2lV2TTdvY+0 P+jTBRq8VRE0qwY/qVjAGNTLABg7hHv54HFD0cHfCJ50tw2QiOA= =zBYt -END PGP SIGNATURE End Message ---
Bug#919734: marked as done (node-yauzl: FTBFS (TypeError: FdSlicer is not a constructor))
Your message dated Tue, 22 Jan 2019 16:22:07 +
with message-id
and subject line Bug#919734: fixed in node-yauzl 2.10.0-1
has caused the Debian Bug report #919734,
regarding node-yauzl: FTBFS (TypeError: FdSlicer is not a constructor)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-yauzl
Version: 2.1.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 8 in use)
dh_update_autotools_config -i
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/test.js
/<>/index.js:44
var fdSlicer = new FdSlicer(fd, {autoClose: true});
^
TypeError: FdSlicer is not a constructor
at /<>/index.js:44:20
at FSReqWrap.oncomplete (fs.js:153:5)
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-yauzl.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: node-yauzl
Source-Version: 2.10.0-1
We believe that the bug you reported is fixed in the latest version of
node-yauzl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard (supplier of updated node-yauzl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 22 Jan 2019 16:58:33 +0100
Source: node-yauzl
Binary: node-yauzl
Architecture: source
Version: 2.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard
Changed-By: Xavier Guimard
Closes: 894956 909886 919734
Description:
node-yauzl - yet another unzip library - Node.js module
Changes:
node-yauzl (2.10.0-1) unstable; urgency=medium
.
[ Andrew Kelley ]
* Imported Upstream version 2.3.1
.
[ Xavier Guimard ]
* New upstream version 2.10.0 (Closes: #919734)
* Add node-buffer-crc32 in dependencies
* Add node-bl in build dependencies
* Bump debhelper compatibility level to 11
* Declare compliance with policy 4.3.0
* Update VCS fields to salsa
* Change section from extra to optional
* Change section to javascript
* Add upstream/metadata
* Update debian/copyright format link
* Ignore lintian errors on index.js (false positive)
* Remove unnecessary Testsuite field
* Ignore test if nocheck is set
* Remove useless quotes in autopkgtest control file (Closes: #894956)
* Install examples
* Add upstream test in autopkgtest
* Replace Andrew Kelley by me in uploaders. Thanks for your work!
(Closes: #909886)
Checksums-Sha1:
98a12165c6d8d099fb3d349606682c4ccb08003e 2051 node-yauzl_2.10.0-1.dsc
4e644bc8440dfe7063d2b1167f411e38d9b8e11a 40947 node-yauzl_2.10.0.orig.tar.gz
70e5b881219e92345eddc7fd74f0d177e9e5a6db 3096 node-yauzl_2.10.0-1.debian.tar.xz
Checksums-Sha256:
20c7b39ec5f2320f49312c96b38e64fc6a8b5d8ac0689d0a12268acf52a1bf9f 2051
node-yauzl_2.10.0-1.dsc
4faee9fc77bb0cea6d066ec9c3914d1117ede92321aefa796aa8775efaedacce 40947
node-yauzl_2.10.0.orig.tar.gz
d48a3958254c493bca866509c7f16fb8812accba369d0f9dcad6735cc8db2588 3096
node-yauzl_2.10.0-1.debian.tar.xz
Files:
d9565fbccd1b9b15e404a94eafa523fe 2051 javascript optional
node-yauzl_2.10.0-1.dsc
20c51ada7cb7f21aba6bc42b757ab325 40947 javascript optional
Bug#916168: marked as done (python3-sphinx-autorun: pycon calls "python" - not "python3")
Your message dated Tue, 22 Jan 2019 16:22:25 +
with message-id
and subject line Bug#916168: fixed in sphinx-autorun 1.1.0-3
has caused the Debian Bug report #916168,
regarding python3-sphinx-autorun: pycon calls "python" - not "python3"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
916168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sphinx-autorun
Version: 1.1.0-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The extension called as
.. runblock pycon:
always executes with the interpreter "python" rather than the
expect
"python3" for this build (python3-sphinx-autorun) of the package.
The problem is in line 28 of
/usr/lib/python3/dist-packages/sphinx_autorun/__init__.py
where the code reads
config = dict(
pycon='python ' + pycon,
...
where it _should_ be
config = dict(
pycon='python3 ' + pycon,
...
Exactly how to fix this, is not clear to me.
There is a workaround by defining the autorun languages in the conf.py
file
import sphinx_autorun
import inspect
pycon = inspect.getfile(sphinx_autorun).replace("__init__","pycon")
autorun_languages = dict(pycon='python3 ' + pycon,
pycon_prefix_chars=4,
pycon_show_source=False,
console='bash',
console_prefix_chars=1)
but it's a bit of a hack I think.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-sphinx-autorun depends on:
ii python3 3.7.1-2
ii python3-sphinx 1.7.9-1
python3-sphinx-autorun recommends no packages.
python3-sphinx-autorun suggests no packages.
-- no debconf information
--
Christian Holm Christensen
-
Niels Bohr Institute, Blegdamsvej 17, DK-2100 Copenhagen
http://cern.ch/cholm, +4524618591
--- End Message ---
--- Begin Message ---
Source: sphinx-autorun
Source-Version: 1.1.0-3
We believe that the bug you reported is fixed in the latest version of
sphinx-autorun, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Félix Sipma (supplier of updated sphinx-autorun
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 24 Dec 2018 19:17:35 +0100
Source: sphinx-autorun
Binary: python3-sphinx-autorun
Architecture: source all
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Félix Sipma
Description:
python3-sphinx-autorun - Code execution extension for Sphinx (Python 3)
Closes: 916168
Changes:
sphinx-autorun (1.1.0-3) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
.
[ Félix Sipma ]
* let pycon call python3 instead of python. (Closes: #916168)
Thanks, Christian Holm Christensen.
* bump Standards-Version to 4.3.0 (no change required)
Checksums-Sha1:
7950bd793a144e7df795914c8327d0d7944bc30c 2100 sphinx-autorun_1.1.0-3.dsc
3d0622a6b1ad18a2ad2ac173c7148e359f529fb6 2944
sphinx-autorun_1.1.0-3.debian.tar.xz
a0b00472520e9095ac77b411ed7fd6bd989cb2be 6100
python3-sphinx-autorun_1.1.0-3_all.deb
a3f666da51d45f0c84c66e350c3a5122212d204e 7302
sphinx-autorun_1.1.0-3_amd64.buildinfo
Checksums-Sha256:
854d74aa184ea4bad3d0789c0c3985f2c774b766aae3a8f10ed3ba9b37f85695 2100
sphinx-autorun_1.1.0-3.dsc
7ecbd56d780d09248e5b626e7364752b6603452fc26eda72769c2054e79d25d4 2944
sphinx-autorun_1.1.0-3.debian.tar.xz
Bug#915774: marked as done (python-fakeredis FTBFS: AttributeError: 'module' object has no attribute 'BasePipeline')
Your message dated Tue, 22 Jan 2019 16:07:26 +
with message-id
and subject line Bug#915774: fixed in python-fakeredis 1.0~rc1-1
has caused the Debian Bug report #915774,
regarding python-fakeredis FTBFS: AttributeError: 'module' object has no
attribute 'BasePipeline'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
915774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fakeredis
Version: 0.14.0-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-fakeredis.html
...
==
ERROR: test_pipeline_as_context_manager (test_fakeredis.TestFakeStrictRedis)
--
Traceback (most recent call last):
File
"/build/1st/python-fakeredis-0.14.0/.pybuild/cpython2_2.7_fakeredis/build/test_fakeredis.py",
line 2796, in test_pipeline_as_context_manager
self.assertTrue(isinstance(p, redis.client.BasePipeline)
AttributeError: 'module' object has no attribute 'BasePipeline'
==
ERROR: test_pipeline_as_context_manager
(test_fakeredis.TestFakeStrictRedisDecodeResponses)
--
Traceback (most recent call last):
File
"/build/1st/python-fakeredis-0.14.0/.pybuild/cpython2_2.7_fakeredis/build/test_fakeredis.py",
line 2796, in test_pipeline_as_context_manager
self.assertTrue(isinstance(p, redis.client.BasePipeline)
AttributeError: 'module' object has no attribute 'BasePipeline'
--
Ran 1973 tests in 80.511s
FAILED (SKIP=932, errors=2)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/python-fakeredis-0.14.0/.pybuild/cpython2_2.7_fakeredis/build;
python2.7 -m nose -v
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:10: build] Error 25
--- End Message ---
--- Begin Message ---
Source: python-fakeredis
Source-Version: 1.0~rc1-1
We believe that the bug you reported is fixed in the latest version of
python-fakeredis, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Nový (supplier of updated python-fakeredis package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 22 Jan 2019 16:31:15 +0100
Source: python-fakeredis
Binary: python-fakeredis python3-fakeredis
Architecture: source all
Version: 1.0~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Ondřej Nový
Description:
python-fakeredis - Fake version of a redis-py - Python 2.x
python3-fakeredis - Fake version of a redis-py - Python 3.x
Closes: 915774
Changes:
python-fakeredis (1.0~rc1-1) unstable; urgency=medium
.
* New upstream release (Closes: #915774)
* Use d/pybuild.testfiles instead of manual cp+rm
* Run only tests which doesn't requires running Redis
* Add python{,3}-six and python{,3}-sortedcontainers into B-D
* Bump Standards-Version to 4.3.0 (no changes)
Checksums-Sha1:
043141f50ca146286e2614a2de8a3693fe4d07c3 2455 python-fakeredis_1.0~rc1-1.dsc
d89a315402c4501d6d1c2f31def000204cab90e8 60170
python-fakeredis_1.0~rc1.orig.tar.gz
9ac17c333091591492634bd489ab5de2025ac23c 40028
python-fakeredis_1.0~rc1-1.debian.tar.xz
dab15bfd3055fedc8dc5771cddd05bd7a115e33e 70256
python-fakeredis_1.0~rc1-1_all.deb
c68036effeff405cc626795a58010d26923f7f01 7223
python-fakeredis_1.0~rc1-1_amd64.buildinfo
320d2860dc489c99cbb1cc1c4d38a8f4522b697a 70312
python3-fakeredis_1.0~rc1-1_all.deb
Checksums-Sha256:
17d69b42113b269106ff4496a3ea6b44663939bbf2e7a4547443472e03f7be1f 2455
python-fakeredis_1.0~rc1-1.dsc
632c0d280e825e76c84e80bf109c16dc6389cedd85d6b19edc7f84cf29dbd4ec 60170
python-fakeredis_1.0~rc1.orig.tar.gz
94ad428872d58372740b5ef53d74fdc271b2260d01b831dc56569c04aac47b98 40028
Bug#918552: marked as done (lombok FTBFS: The import org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup cannot be resolved)
Your message dated Tue, 22 Jan 2019 16:07:03 +
with message-id
and subject line Bug#918552: fixed in lombok 1.16.22-6
has caused the Debian Bug report #918552,
regarding lombok FTBFS: The import
org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup cannot be resolved
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
918552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lombok
Version: 1.16.22-5
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lombok.html
...
Compile errors:
--
46. ERROR in
/build/1st/lombok-1.16.22/src/eclipseAgent/lombok/launch/PatchFixesHider.java
(at line 64)
import org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup;
^
The import org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup cannot
be resolved
--
47. ERROR in
/build/1st/lombok-1.16.22/src/eclipseAgent/lombok/launch/PatchFixesHider.java
(at line 597)
public static SearchResultGroup[]
createFakeSearchResult(SearchResultGroup[] returnValue,
^
SearchResultGroup cannot be resolved to a type
--
48. ERROR in
/build/1st/lombok-1.16.22/src/eclipseAgent/lombok/launch/PatchFixesHider.java
(at line 597)
public static SearchResultGroup[]
createFakeSearchResult(SearchResultGroup[] returnValue,
^
SearchResultGroup cannot be resolved to a type
--
49. ERROR in
/build/1st/lombok-1.16.22/src/eclipseAgent/lombok/launch/PatchFixesHider.java
(at line 611)
return new SearchResultGroup[]
{new SearchResultGroup(null, new SearchMatch[1])};
^
SearchResultGroup cannot be resolved to a type
--
50. ERROR in
/build/1st/lombok-1.16.22/src/eclipseAgent/lombok/launch/PatchFixesHider.java
(at line 611)
return new SearchResultGroup[]
{new SearchResultGroup(null, new SearchMatch[1])};
^
SearchResultGroup cannot be resolved to a type
--
BUILD FAILED
/build/1st/lombok-1.16.22/build.xml:251: Compilation not successful
Total time: 10 seconds
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: lombok
Source-Version: 1.16.22-6
We believe that the bug you reported is fixed in the latest version of
lombok, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated lombok package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 22 Jan 2019 16:46:16 +0100
Source: lombok
Binary: liblombok-java
Architecture: source
Version: 1.16.22-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Description:
liblombok-java - Reduce boilerplate code in Java projects
Closes: 918552
Changes:
lombok (1.16.22-6) unstable; urgency=medium
.
* Team upload.
* Added the missing dependency on libeclipse-jdt-core-manipulation-java
(Closes: #918552)
* Standards-Version updated to 4.3.0
Checksums-Sha1:
38fabda11491a833eb5a74e5f9faae7b94d423d7 2226 lombok_1.16.22-6.dsc
5bf6369e25a5922c073756e74782a14121963d09 8340 lombok_1.16.22-6.debian.tar.xz
eaa090190c5751e1d6ab5b678ab6635e5ddb6b9c 18678
lombok_1.16.22-6_source.buildinfo
Checksums-Sha256:
3ccfacaa201e994acf935fe8b5287df78d42d13942d98a88d0d4cb406ed43d5e 2226
lombok_1.16.22-6.dsc
eda015c96c44e6b590bbf3eb85d45dd869f9c2938c7d91cda893f3691df962e5 8340
lombok_1.16.22-6.debian.tar.xz
80b73a53931a1004ea581f8208bfa4e0a5ae96d73b1a3617d7822c349e955f98 18678
lombok_1.16.22-6_source.buildinfo
Files:
Bug#920197: preload: FTBFS (configure: error: unrecognized option: --runstatedir=/run)
Package: src:preload
Version: 0.6.4-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
dh_autoreconf -a
dh_autoreconf: Only runs once, see dh-autoreconf(7)
dh_auto_configure -a
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
configure: error: unrecognized option: --runstatedir=/run
Try `./configure --help' for more information.
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
make: *** [debian/rules:10: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
It also fails here in every arch: (except amd64, where the package was not
built officially)
https://buildd.debian.org/status/package.php?p=preload
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#918552: Bug #918552 in lombok marked as pending
Control: tag -1 pending Hello, Bug #918552 in lombok reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/lombok/commit/c2721ae83c0f09cc3a83bd37a07835a36bba435d Added the missing dependency on libeclipse-jdt-core-manipulation-java (Closes: #918552) (this message was generated automatically) -- Greetings https://bugs.debian.org/918552
Processed: Bug #918552 in lombok marked as pending
Processing control commands: > tag -1 pending Bug #918552 [src:lombok] lombok FTBFS: The import org.eclipse.jdt.internal.corext.refactoring.SearchResultGroup cannot be resolved Added tag(s) pending. -- 918552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897806: Lmms fix uploaded
Hi all, 在 2019-01-21一的 00:26 +0100，Ross Gammon写道： > tag 891756 + pending > tag 897806 + pending > tag 918242 + pending > thanks > > I have uploaded a fix. It is unfortunately waiting for my new signing > sub-key to be rolled into the Debian Keyring. I've prepared an upload from git packaging repo onto DELAYED/3. Please let me know if there's any other issues. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#892398: marked as done (kfreebsd-10: build-depends on GCC 6)
Your message dated Tue, 22 Jan 2019 15:35:52 + with message-id and subject line Bug#892398: fixed in kfreebsd-10 10.3~svn300087-4 has caused the Debian Bug report #892398, regarding kfreebsd-10: build-depends on GCC 6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 892398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kfreebsd-10 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-6-rm Hi, kfreebsd-10 build-depends on GCC 6. We now have GCC 7 (default) and GCC 8 in the archive, so please make your package build with a newer compiler (preferably the default one) again, since we'd like to remove GCC 6 from testing before the buster release. Cheers, Emilio --- End Message --- --- Begin Message --- Source: kfreebsd-10 Source-Version: 10.3~svn300087-4 We believe that the bug you reported is fixed in the latest version of kfreebsd-10, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Clarke (supplier of updated kfreebsd-10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Jan 2019 14:15:46 + Source: kfreebsd-10 Binary: kfreebsd-source-10.3 kfreebsd-headers-10.3-0 kfreebsd-image-10.3-0-amd64 kfreebsd-image-10-amd64 kfreebsd-headers-10.3-0-amd64 kfreebsd-headers-10-amd64 kernel-image-10.3-0-amd64-di nic-modules-10.3-0-amd64-di nic-wireless-modules-10.3-0-amd64-di nic-shared-modules-10.3-0-amd64-di serial-modules-10.3-0-amd64-di usb-serial-modules-10.3-0-amd64-di ppp-modules-10.3-0-amd64-di cdrom-modules-10.3-0-amd64-di scsi-core-modules-10.3-0-amd64-di scsi-modules-10.3-0-amd64-di scsi-extra-modules-10.3-0-amd64-di plip-modules-10.3-0-amd64-di floppy-modules-10.3-0-amd64-di loop-modules-10.3-0-amd64-di ipv6-modules-10.3-0-amd64-di nls-core-modules-10.3-0-amd64-di ext2-modules-10.3-0-amd64-di isofs-modules-10.3-0-amd64-di reiserfs-modules-10.3-0-amd64-di fat-modules-10.3-0-amd64-di zfs-modules-10.3-0-amd64-di nfs-modules-10.3-0-amd64-di nullfs-modules-10.3-0-amd64-di md-modules-10.3-0-amd64-di parport-modules-10.3-0-amd64-di nic-usb-modules-10.3-0-amd64-di sata-modules-10.3-0-amd64-di acpi-modules-10.3-0-amd64-di i2c-modules-10.3-0-amd64-di crypto-modules-10.3-0-amd64-di crypto-dm-modules-10.3-0-amd64-di mmc-core-modules-10.3-0-amd64-di mmc-modules-10.3-0-amd64-di sound-modules-10.3-0-amd64-di zlib-modules-10.3-0-amd64-di kfreebsd-image-10.3-0-486 kfreebsd-image-10-486 kfreebsd-headers-10.3-0-486 kfreebsd-headers-10-486 kfreebsd-image-10.3-0-686 kfreebsd-image-10-686 kfreebsd-headers-10.3-0-686 kfreebsd-headers-10-686 kfreebsd-image-10.3-0-xen kfreebsd-image-10-xen kfreebsd-headers-10.3-0-xen kfreebsd-headers-10-xen kernel-image-10.3-0-486-di nic-modules-10.3-0-486-di nic-wireless-modules-10.3-0-486-di nic-shared-modules-10.3-0-486-di serial-modules-10.3-0-486-di usb-serial-modules-10.3-0-486-di ppp-modules-10.3-0-486-di cdrom-modules-10.3-0-486-di scsi-core-modules-10.3-0-486-di scsi-modules-10.3-0-486-di scsi-extra-modules-10.3-0-486-di plip-modules-10.3-0-486-di floppy-modules-10.3-0-486-di loop-modules-10.3-0-486-di ipv6-modules-10.3-0-486-di nls-core-modules-10.3-0-486-di ext2-modules-10.3-0-486-di isofs-modules-10.3-0-486-di reiserfs-modules-10.3-0-486-di fat-modules-10.3-0-486-di zfs-modules-10.3-0-486-di nfs-modules-10.3-0-486-di nullfs-modules-10.3-0-486-di md-modules-10.3-0-486-di parport-modules-10.3-0-486-di nic-usb-modules-10.3-0-486-di sata-modules-10.3-0-486-di acpi-modules-10.3-0-486-di i2c-modules-10.3-0-486-di crypto-modules-10.3-0-486-di crypto-dm-modules-10.3-0-486-di mmc-core-modules-10.3-0-486-di mmc-modules-10.3-0-486-di sound-modules-10.3-0-486-di zlib-modules-10.3-0-486-di Architecture: source Version: 10.3~svn300087-4 Distribution: unstable Urgency: medium Maintainer: GNU/kFreeBSD Maintainers Changed-By: James Clarke Description: acpi-modules-10.3-0-486-di - ACPI support modules (udeb) acpi-modules-10.3-0-amd64-di - ACPI support modules (udeb)
Bug#920194: python-xarray is missing build dependencies and fetching them from the net instead
Package: src:python-xarray
Version: 0.11.2-1
Severity: serious
Tags: sid buster
make[2]: Entering directory '/<>/doc'
sphinx-build -b html -d _build/doctrees . _build/html
Running Sphinx v1.7.9
python exec: /usr/bin/python3
sys.path: ['/usr/share/sphinx/scripts/python3', '/<>',
'/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload',
'/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages']
numpy: 1.14.5, /usr/lib/python3/dist-packages/numpy/
scipy: 1.1.0, /usr/lib/python3/dist-packages/scipy/
pandas: 0.23.3, /usr/lib/python3/dist-packages/pandas/
matplotlib: 2.2.2, /usr/lib/python3/dist-packages/matplotlib/
dask: 1.0.0+dfsg, /usr/lib/python3/dist-packages/dask/
IPython: 5.8.0, /usr/lib/python3/dist-packages/IPython/
seaborn: 0.8.0, /usr/lib/python3/dist-packages/seaborn/
cartopy: 0.17.0, /usr/lib/python3/dist-packages/cartopy/
netCDF4: 1.4.2, /usr/lib/python3/dist-packages/netCDF4/
rasterio: 1.0.13, /usr/lib/python3/dist-packages/rasterio/
no zarr
no iris
no flake8
sphinx_gallery: 0.2.0, /usr/lib/python3/dist-packages/sphinx_gallery/
cftime: 1.0.3.4, /usr/lib/python3/dist-packages/cftime/
xarray: 0.11.2, /<>/xarray/__init__.py
loading pickled environment... not yet created
[autosummary] generating autosummary for: README.rst, api-hidden.rst, api.rst,
combining.rst, computation.rst, contributing.rst, dask.rst, data-structures.rst,
examples.rst, examples/monthly-means.rst, ..., interpolation.rst, io.rst,
pandas.rst, plotting.rst, related-projects.rst, reshaping.rst, roadmap.rst,
time-series.rst, whats-new.rst, why-xarray.rst
[autosummary] generating autosummary for:
/<>/doc/generated/xarray.CFTimeIndex.rst,
/<>/doc/generated/xarray.CFTimeIndex.shift.rst,
/<>/doc/generated/xarray.CFTimeIndex.to_datetimeindex.rst,
/<>/doc/generated/xarray.DataArray.T.rst,
/<>/doc/generated/xarray.DataArray.__getitem__.rst,
/<>/doc/generated/xarray.DataArray.__setitem__.rst,
/<>/doc/generated/xarray.DataArray.all.rst,
/<>/doc/generated/xarray.DataArray.any.rst,
/<>/doc/generated/xarray.DataArray.argmax.rst,
/<>/doc/generated/xarray.DataArray.argmin.rst, ...,
/<>/doc/generated/xarray.ufuncs.signbit.rst,
/<>/doc/generated/xarray.ufuncs.sin.rst,
/<>/doc/generated/xarray.ufuncs.sinh.rst,
/<>/doc/generated/xarray.ufuncs.sqrt.rst,
/<>/doc/generated/xarray.ufuncs.square.rst,
/<>/doc/generated/xarray.ufuncs.tan.rst,
/<>/doc/generated/xarray.ufuncs.tanh.rst,
/<>/doc/generated/xarray.ufuncs.trunc.rst,
/<>/doc/generated/xarray.where.rst,
/<>/doc/generated/xarray.zeros_like.rst
loading intersphinx inventory from https://matplotlib.org/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
WARNING: intersphinx inventory 'https://matplotlib.org/objects.inv' not
fetchable due to : ('intersphinx
inventory %r not fetchable due to %s: %s', 'https://matplotlib.org/objects.inv',
, ConnectionError(...))
loading intersphinx inventory from
http://scitools.org.uk/iris/docs/latest/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
WARNING: intersphinx inventory
'http://scitools.org.uk/iris/docs/latest/objects.inv' not fetchable due to
: ('intersphinx inventory %r not
fetchable due to %s: %s', 'http://scitools.org.uk/iris/docs/latest/objects.inv',
, ConnectionError(...))
loading intersphinx inventory from /usr/share/doc/python3/html/objects.inv...
loading intersphinx inventory from
/usr/share/doc/python-pandas-doc/html/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
WARNING: intersphinx inventory
'/usr/share/doc/python-pandas-doc/html/objects.inv' not fetchable due to : [Errno 2] No such file or directory:
'/usr/share/doc/python-pandas-doc/html/objects.inv'
loading intersphinx inventory from
/usr/share/doc/python-numpy-doc/html/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
WARNING: intersphinx inventory
'/usr/share/doc/python-numpy-doc/html/objects.inv' not fetchable due to : [Errno 2] No such file or directory:
'/usr/share/doc/python-numpy-doc/html/objects.inv'
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 29 source files that are out of date
updating environment: 398 added, 0 changed, 0 removed
Bug#897156: marked as done (node-cache-base: FTBFS and Debci failure with node-is-extendable 1.0.1-1)
Your message dated Tue, 22 Jan 2019 15:06:40 + with message-id and subject line Bug#897156: fixed in node-cache-base 0.8.4-2 has caused the Debian Bug report #897156, regarding node-cache-base: FTBFS and Debci failure with node-is-extendable 1.0.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 (460ms) 5 failing 1) cache-base .union() should union a string value: TypeError: union-value expects the first argument to be an object. at Function.unionValue (/usr/lib/nodejs/union-value/index.js:10:11) at Cache.union (index.js:111:11) at Context. (test/test.js:69:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 2) cache-base .union() should union multiple string values: TypeError: union-value expects the first argument to be an object. at Function.unionValue (/usr/lib/nodejs/union-value/index.js:10:11) at Cache.union (index.js:111:11) at Context. (test/test.js:74:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 3) cache-base .union() should union multiple arrays: TypeError: union-value expects the first argument to be an object. at Function.unionValue (/usr/lib/nodejs/union-value/index.js:10:11) at Cache.union (index.js:111:11) at Context. (test/test.js:81:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 4) cache-base .union() should union nested string values: TypeError: union-value expects the first argument to be an object. at Function.unionValue (/usr/lib/nodejs/union-value/index.js:10:11) at Cache.union (index.js:111:11) at Context. (test/test.js:88:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 5) cache-base .union() should union and uniquify arrays: TypeError: union-value expects the first argument to be an object. at Function.unionValue (/usr/lib/nodejs/union-value/index.js:10:11) at Cache.union (index.js:111:11) at Context. (test/test.js:95:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate.
Processed: Bug #919846 in ruby-rails-assets-highlightjs marked as pending
Processing control commands: > tag -1 pending Bug #919846 [ruby-rails-assets-highlightjs] ruby-rails-assets-highlightjs: missing Depends: libjs-highlight.js Added tag(s) pending. -- 919846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919846: Bug #919846 in ruby-rails-assets-highlightjs marked as pending
Control: tag -1 pending Hello, Bug #919846 in ruby-rails-assets-highlightjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-rails-assets-highlightjs/commit/05d8e10750d501794abd6e2557433c06d7924927 Depend on libjs-highlight.js (Closes: #919846) (this message was generated automatically) -- Greetings https://bugs.debian.org/919846
Processed: Re: [Pkg-javascript-devel] Bug#920190: node-isobject, node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js'
Processing control commands: > reassign -1 node-get-value 3.0.1+~3.0.1-1 Bug #920190 [node-isobject,node-get-value] node-isobject,node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js' Bug reassigned from package 'node-isobject,node-get-value' to 'node-get-value'. Ignoring request to alter found versions of bug #920190 to the same values previously set Ignoring request to alter fixed versions of bug #920190 to the same values previously set Bug #920190 [node-get-value] node-isobject,node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js' Marked as found in versions node-get-value/3.0.1+~3.0.1-1. > close -1 1:3.0.1-2 Bug #920190 [node-get-value] node-isobject,node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js' Marked as fixed in versions node-get-value/1:3.0.1-2. Bug #920190 [node-get-value] node-isobject,node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js' Marked Bug as done -- 920190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920190: [Pkg-javascript-devel] Bug#920190: node-isobject, node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js'
Control: reassign -1 node-get-value 3.0.1+~3.0.1-1 Control: close -1 1:3.0.1-2 On Tue, Jan 22, 2019 at 03:44:28PM +0100, Christoph Berg wrote: > Package: node-isobject,node-get-value > Severity: serious > > node-isobject and node-get-value cannot be installed together: > > Unpacking node-get-value (3.0.1+~3.0.1-1) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-F6WG6i/026-node-get-value_3.0.1+~3.0.1-1_all.deb > (--unpack): > trying to overwrite '/usr/lib/nodejs/isobject/index.js', which is also in > package node-isobject 3.0.1-1 Already fixed, see version info above. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#920191: coda ftbfs on ppc64el
Package: src:coda Version: 2.20-2 Severity: serious Tags: sid buster coda ftbfs on ppc64el: [...] checking build Java interface... no [...] make[1]: Leaving directory '/<>' dh_install -a install -d debian/coda//usr/bin cp --reflink=auto -a debian/tmp/usr/bin/codacheck debian/tmp/usr/bin/codacmp debian/tmp/usr/bin/codadd debian/tmp/usr/bin/codadump debian/tmp/usr/bin/codaeval debian/tmp/usr/bin/codafind debian/coda//usr/bin/ install -d debian/.debhelper/generated/coda install -d debian/libcoda15//usr/lib/powerpc64le-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/powerpc64le-linux-gnu/libcoda.so.15.0.0 debian/libcoda15//usr/lib/powerpc64le-linux-gnu/ install -d debian/.debhelper/generated/libcoda15 install -d debian/libcoda-dev//usr/include cp --reflink=auto -a debian/tmp/usr/include/coda.h debian/tmp/usr/share/coda/fortran/coda.inc debian/libcoda-dev//usr/include/ install -d debian/libcoda-dev//usr/lib/powerpc64le-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/powerpc64le-linux-gnu/libcoda.a debian/libcoda-dev//usr/lib/powerpc64le-linux-gnu/ dh_install: Cannot find (any matches for) "usr/share/coda/java/libcoda_jni.so" (tried in ., debian/tmp) dh_install: libcoda-jni missing files: usr/share/coda/java/libcoda_jni.so dh_install: missing files, aborting There is no reason to disable that just on ppc64el.
Bug#920190: node-isobject,node-get-value: trying to overwrite '/usr/lib/nodejs/isobject/index.js'
Package: node-isobject,node-get-value Severity: serious node-isobject and node-get-value cannot be installed together: Unpacking node-get-value (3.0.1+~3.0.1-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-F6WG6i/026-node-get-value_3.0.1+~3.0.1-1_all.deb (--unpack): trying to overwrite '/usr/lib/nodejs/isobject/index.js', which is also in package node-isobject 3.0.1-1 Christoph
Bug#919792: marked as done (gyoto,gyoto-doc: both packages ship /usr/share/doc/gyoto/README.md)
Your message dated Tue, 22 Jan 2019 14:43:43 + with message-id and subject line Bug#919792: fixed in gyoto 1.3.1-1 has caused the Debian Bug report #919792, regarding gyoto,gyoto-doc: both packages ship /usr/share/doc/gyoto/README.md to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gyoto,gyoto-doc Version: 1.3.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package gyoto-doc. Preparing to unpack .../gyoto-doc_1.3.0-1_all.deb ... Unpacking gyoto-doc (1.3.0-1) ... dpkg: error processing archive /var/cache/apt/archives/gyoto-doc_1.3.0-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/gyoto/README.md', which is also in package gyoto 1.3.0-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gyoto-doc_1.3.0-1_all.deb cheers, Andreas gyoto=1.3.0-1_gyoto-doc=1.3.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gyoto Source-Version: 1.3.1-1 We believe that the bug you reported is fixed in the latest version of gyoto, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thibaut Paumard (supplier of updated gyoto package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 14:19:22 +0100 Source: gyoto Binary: gyoto gyoto-bin libgyoto7 libgyoto7-dev yorick-gyoto python-gyoto python3-gyoto gyoto-doc Architecture: source Version: 1.3.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Thibaut Paumard Description: gyoto - General relativistic geodesic integration and ray-tracing gyoto-bin - General relativistic ray-tracing command-line interface gyoto-doc - documentation for the Gyoto library libgyoto7 - Gyoto framework main library an standard plug-in libgyoto7-dev - development files for libgyoto python-gyoto - General relativistic geodesic integration for the Python 2 langua python3-gyoto - General relativistic geodesic integration for the Python 3 langua yorick-gyoto - General relativistic geodesic integration for the Yorick language Closes: 919792 919983 Changes: gyoto (1.3.1-1) unstable; urgency=medium . * Bug fix: "both packages ship /usr/share/doc/gyoto/README.md", thanks to Andreas Beckmann (Closes: #919792). * Bug fix: "autopkgtest failure on i386", thanks to Graham Inggs (Closes: #919983). Checksums-Sha1: 9abbc9a81a54b0bf5e65c3fa53481feb1d03ee94 3061 gyoto_1.3.1-1.dsc db46412d1e17967654291442869fafa7877f798e 1968254 gyoto_1.3.1.orig.tar.gz a7b81efa5833d3ba859dda9f3de26e6b4ce97d22 11656 gyoto_1.3.1-1.debian.tar.xz cc082e704a2631a1c6ed01de71cbc40c7a9a21a0 16736 gyoto_1.3.1-1_amd64.buildinfo Checksums-Sha256: f59e7a6ea7501dbfa98bf562de161993f4a026b8d337749c124dfb1e6aa96089 3061 gyoto_1.3.1-1.dsc c78d3c508a83f01a4344406bb188a15ba91188f9db719924e440fb291cab9f35 1968254 gyoto_1.3.1.orig.tar.gz 3c6325f8027b2f2f8d078fe5e4119214f2d712482d12ef67853bf7bd3b4a4cbc 11656 gyoto_1.3.1-1.debian.tar.xz dea46876d4fcfa4abc936c1f3bc75082c206c98cd5e4ca924f1f721356321bbd 16736 gyoto_1.3.1-1_amd64.buildinfo Files: fe7c4d8def420f302bddb4d5df40425e 3061 science optional gyoto_1.3.1-1.dsc 98405aa010967434625b4c006496e421 1968254 science optional gyoto_1.3.1.orig.tar.gz 35bbdff49d2232ca526156811604d641 11656 science optional gyoto_1.3.1-1.debian.tar.xz 2b0a81db85d14bd886d6d068105d87e0 16736 science optional gyoto_1.3.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEvK37UrQZmNdNmdmOk5RTSODcKEAFAlxHJj4THHRoaWJhdXRA ZGViaWFuLm9yZwAKCRCTlFNI4NwoQG6ZD/9fVrzANEP7tR8Nwdr7xpAgizxt/tqx
Bug#919064: marked as done (jarjar: ASM class ModuleHashesAttribute is missing)
Your message dated Tue, 22 Jan 2019 14:43:50 + with message-id and subject line Bug#919064: fixed in jarjar 1.4+svn142-10 has caused the Debian Bug report #919064, regarding jarjar: ASM class ModuleHashesAttribute is missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scala Version: 2.11.12-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scala.html ... BUILD FAILED /build/1st/scala-2.11.12/build.xml:117: The following error occurred while executing this line: /build/1st/scala-2.11.12/build-ant-macros.xml:8: The following error occurred while executing this line: /build/1st/scala-2.11.12/build.xml:1216: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute at com.tonicsystems.jarjar.asm.commons.ClassRemapper.visitAttribute(ClassRemapper.java:120) at com.tonicsystems.jarjar.asm.ClassReader.accept(ClassReader.java:642) at com.tonicsystems.jarjar.asm.ClassReader.accept(ClassReader.java:391) at com.tonicsystems.jarjar.KeepProcessor.process(KeepProcessor.java:70) at com.tonicsystems.jarjar.ext_util.JarProcessorChain.process(JarProcessorChain.java:40) at com.tonicsystems.jarjar.MainProcessor.process(MainProcessor.java:92) at com.tonicsystems.jarjar.ext_util.AntJarProcessor.zipFile(AntJarProcessor.java:70) at org.apache.tools.ant.taskdefs.Zip.zipFile(Zip.java:1873) at org.apache.tools.ant.taskdefs.Zip.addResource(Zip.java:1079) at org.apache.tools.ant.taskdefs.Zip.addResources(Zip.java:1004) at org.apache.tools.ant.taskdefs.Zip.addResources(Zip.java:1110) at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:725) at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java:628) at com.tonicsystems.jarjar.ext_util.AntJarProcessor.execute(AntJarProcessor.java:51) at com.tonicsystems.jarjar.JarJarTask.execute(JarJarTask.java:49) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at java.base/java.util.Vector.forEach(Vector.java:1387) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:67) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:391) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at
Bug#920188: broken: required library Popper.js missing
Package: libjs-bootstrap4 Version: 4.2.1+dfsg-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bootstrap4 requires Popper.js, but package libjs-bootstrap4 is built with it. Solution is to package node-poppler.js and have libjs-bootstrap4 be compiled with that library embedded. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxHJ4MACgkQLHwxRsGg ASFTEA//blmuivBYm/arNvdICF6JcWpAJZoIGnptUSSrhL64WuekXGEPhz1WAc6V CFOpoTjP/GjrYqWJ2xvNdYX/IlN2rIhaB2Y0Eb6IbZyKbDawokT7HanPIKlBDrEL lp6Bh42qozgF6gyPHZYbD2I/3j9692uHdYWOasYPKblSaZv7pwfiFJ00IrTNkZOU z8XkecQ6yYPXHIkvdkL3GaW3aA8+/vv9l/g6kvVY/JXN3pPZJh8I9T58TrXsVp8u TdIUNOO3XcXl51J4vhg2xktN4pvp81/fhbOffHUhmZaICb3yF88IDYqIuQMoRSyb ZA6Nj+m9X15rDVD4m0RXC0OypSOt5SCZwDe9ZCLFxU1UDjG+t0pEvkgycVvbHocC aU4D4U6gHrxYs58rn7P8h45FqYMOy8NIRalJ8x97+qtghmciQ6pKEQavk/WdKt7j L0KUJWHXzZUAjeuuvKac2XEEkWg6dwJefEZi5aTIg00iiUYGYLM3kT6DowRWDGSE 0HLFB2ZJHK/YUbDwaOtUy/av/4daUhopPPJz21eHGdgX5x/NIlT+l87fSv5oz/yK ADIVwZLG+2NaiO6huwETIMj6uzA7R3hPBBcN6zDVaLUtqjBzmi/BTZnfkZ0EqVH3 HbK+vpkfpXrThmVCg7npyf7zHSqsIK/45ah0PTwhnUVI84IsMso= =J6Tc -END PGP SIGNATURE-
Processed: Bug #919064 in jarjar marked as pending
Processing control commands: > tag -1 pending Bug #919064 [libjarjar-java] jarjar: ASM class ModuleHashesAttribute is missing Added tag(s) pending. -- 919064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919064: Bug #919064 in jarjar marked as pending
Control: tag -1 pending Hello, Bug #919064 in jarjar reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/jarjar/commit/1808732905069364dc97ae7cb2666ad8c1795594 Embed all the asm-commons classes (Closes: #919064) (this message was generated automatically) -- Greetings https://bugs.debian.org/919064
Bug#897156: node-cache-base: FTBFS and Debci failure with node-is-extendable 1.0.1-1
An update of node-union-value fixes the problem. Let's do it
Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)
found 917500 3.8.0+repack1-3 thanks Hi. Sorry for the reopening but this does not seem fixed. I can still reproduce the error in our test machine (using sbuild) and it also fails (with a different error) in reproducible-builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/liggghts.html (More to the point, my autobuilders normally have LC_ALL=C in the environment, so setting LC_ALL=C explicitly is unlikely to have any effect). Thanks.
Processed: liggghts: FTBFS (style_atom.h: No such file or directory)
Processing commands for cont...@bugs.debian.org:
> found 917500 3.8.0+repack1-3
Bug #917500 {Done: Anton Gladky } [src:liggghts] liggghts:
FTBFS (style_atom.h: No such file or directory)
Marked as found in versions liggghts/3.8.0+repack1-3; no longer marked as fixed
in versions liggghts/3.8.0+repack1-3 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#919064: scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute
Processing control commands: > reassign -1 libjarjar-java Bug #919064 [src:scala] scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute Bug reassigned from package 'src:scala' to 'libjarjar-java'. No longer marked as found in versions scala/2.11.12-4. Ignoring request to alter fixed versions of bug #919064 to the same values previously set > affects -1 src:scala Bug #919064 [libjarjar-java] scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute Added indication that 919064 affects src:scala > retitle -1 jarjar: ASM class ModuleHashesAttribute is missing Bug #919064 [libjarjar-java] scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute Changed Bug title to 'jarjar: ASM class ModuleHashesAttribute is missing' from 'scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute'. -- 919064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919064: scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute
Control: reassign -1 libjarjar-java Control: affects -1 src:scala Control: retitle -1 jarjar: ASM class ModuleHashesAttribute is missing Le 20/01/2019 à 08:06, Andreas Tille a écrit : > I've seen that there is a new upstream > version (2.12.8) - may be I should give it a try but I have no idea > about consequences of exchanging a package that has lots or rdepends > currently and whether this would qualify as "transition". It definitely would, but I doubt any human being is able to package SBT and Scala 2.12 in time before the freeze anyway (I'm offering a bottle of Champagne if someone does). The good news is, we won't have to go that route, because this issue isn't caused by Scala but by jarjar. It embeds a subset of the ASM classes and at least one is missing. I'll upload a fix today. Emmanuel Bourg
Bug#920182: marked as done (node-get-value: Circular dependency)
Your message dated Tue, 22 Jan 2019 14:09:51 +0100 with message-id <20190122130950.ge28...@mapreri.org> and subject line Re: [Pkg-javascript-devel] Bug#920182: node-get-value: Circular dependency has caused the Debian Bug report #920182, regarding node-get-value: Circular dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-get-value Version: 3.0.1+~3.0.1-1 Severity: serious Tags: upstream node-get-value build-depends on node-micromatch which depends on node-get-value via some packages -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (600, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On Tue, Jan 22, 2019 at 01:57:52PM +0100, Xavier Guimard wrote: > node-get-value build-depends on node-micromatch which depends on > node-get-value via some packages That's not a problem as long as everything stays installable. I manually built the new node-get-value and uploaded it now. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message ---
Processed: Bug #920182 in node-get-value marked as pending
Processing control commands: > tag -1 pending Bug #920182 [node-get-value] node-get-value: Circular dependency Added tag(s) pending. -- 920182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920182: Bug #920182 in node-get-value marked as pending
Control: tag -1 pending Hello, Bug #920182 in node-get-value reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-get-value/commit/14b75131462c7a4a0438ae83e3f0c0036ff9e998 Disable mocha test and remove related build dependencies Closes: #920182 (this message was generated automatically) -- Greetings https://bugs.debian.org/920182
Bug#920182: node-get-value: Circular dependency
Package: node-get-value Version: 3.0.1+~3.0.1-1 Severity: serious Tags: upstream node-get-value build-depends on node-micromatch which depends on node-get-value via some packages -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (600, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#893227: libbluray FTBFS with openjdk-9
Hi Reinhard, Le 22/01/2019 à 12:14, Reinhard Tartler a écrit : > Can you please give us an update on the roadmap for Java? > What's the status on removing openjdk-8 from buster? OpenJDK 8 will be kept in Buster but it should be used in exceptional cases (for example the lombok package requires both OpenJDK 8 and 11 to build). The default Java runtime for Buster is OpenJDK 11 and the packages have to work properly with it. @Petri: Thank you for fixing the OpenJDK 11 issues. I suggest ignoring the JDK 9 and 10 issues since these versions are now EOL. The general consensus in the Java community is to support only the LTS releases (Java 8, 11, 17, etc). Emmanuel Bourg
Bug#919801: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgoogle-gson-java
Version: 2.8.5-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with javahelper --buildsystem=maven
dh_update_autotools_config -i -O--buildsystem=maven
dh_autoreconf -i -O--buildsystem=maven
dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibgoogle-gson-java --debian-build --keep-pom-version
--maven-repo=/<>/debian/maven-repo
[ERROR] Cannot find parent dependency
com.google.code.gson:gson-parent:pom:2.8.5, use --no-parent option to resolve
this issue or install the parent POM in the Maven repository
jh_linkjars -i -O--buildsystem=maven
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp -Rvp gson/src/main/java-templates/* gson/src/main/java/
'gson/src/main/java-templates/com/google/gson/internal/GsonBuildConfig.java' ->
'gson/src/main/java/com/google/gson/internal/GsonBuildConfig.java'
sed -i s/\$\{project.version\}/2.8.5/
gson/src/main/java/com/google/gson/internal/GsonBuildConfig.java
dh_auto_build
[... snipped ...]
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:87:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:100:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:102:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:103:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:104:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:105:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:123:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:125:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:126:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:127:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:128:
warning - invalid usage of tag >
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Expose.java:37:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Expose.java:38:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Expose.java:39:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:34:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:43:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:51:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:62:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:68:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/SerializedName.java:38:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/SerializedName.java:39:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Since.java:39:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Since.java:40:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Since.java:41:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Until.java:41:
warning - invalid usage of tag
[ERROR]
/<>/gson/src/main/java/com/google/gson/annotations/Until.java:42:
warning - invalid usage of tag
[ERROR]
[ERROR] Command line
Bug#919800: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #919798, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jackson-databind Version: 2.9.8-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibjackson2-databind-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo jh_linkjars -i dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [... snipped ...] [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/DeserializationFeature.java:87: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/DeserializationFeature.java:87: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/DeserializationFeature.java:89: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/deser/std/EnumMapDeserializer.java:22: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/deser/std/EnumMapDeserializer.java:22: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:635: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:646: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:658: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:998: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1010: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1023: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:635: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:646: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:658: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:998: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1010: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1023: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/module/SimpleModule.java:17: warning - Tag @link: reference not found: Module [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/node/ArrayNode.java:311: warning - invalid usage of tag > [ERROR]
Bug#919798: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 +
with message-id
and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:antlr4
Version: 4.7.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
dh_auto_configure -i
mh_patchpoms -pantlr4 --debian-build --keep-pom-version
--maven-repo=/<>/debian/maven-repo
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp -r debian/generated-sources/antlr4/* runtime/Java/src/
dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/<>
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/<>/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
com.google.inject.internal.cglib.core.$ReflectUtils$1
(file:/usr/share/maven/lib/guice.jar) to method
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of
com.google.inject.internal.cglib.core.$ReflectUtils$1
[... snipped ...]
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules
but the packages defined in https://docs.oracle.com/javase/7/docs/api/ are in
the unnamed module.
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/CharStreams.java:27:
warning - invalid usage of tag >
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/CodePointCharStream.java:19:
warning - invalid usage of tag >
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/ParserInterpreter.java:72:
warning - invalid usage of tag >
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/ParserInterpreter.java:72:
warning - invalid usage of tag >
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:34:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:35:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:37:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:51:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:52:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:53:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/RuleContext.java:166:
warning - invalid usage of tag {@see ParseTree#setParent}
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:16:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:18:
warning - invalid usage of tag >
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:23:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:37:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:23:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:37:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/tree/ParseTreeListener.java:15:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:23:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:37:
warning - invalid usage of tag <
[ERROR]
/<>/runtime/Java/src/org/antlr/v4/runtime/atn/CodePointTransitions.java:23:
warning - invalid
Bug#919800: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #920020, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jackson-databind Version: 2.9.8-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibjackson2-databind-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo jh_linkjars -i dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [... snipped ...] [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/DeserializationFeature.java:87: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/DeserializationFeature.java:87: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/DeserializationFeature.java:89: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/deser/std/EnumMapDeserializer.java:22: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/deser/std/EnumMapDeserializer.java:22: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:635: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:646: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:658: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:998: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1010: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1023: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:635: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:646: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:658: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:998: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1010: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/AnnotationIntrospector.java:1023: warning - invalid usage of tag > [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/module/SimpleModule.java:17: warning - Tag @link: reference not found: Module [ERROR] /<>/src/main/java/com/fasterxml/jackson/databind/node/ArrayNode.java:311: warning - invalid usage of tag > [ERROR]
Bug#919883: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #920020, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice Version: 1:6.1.4-1 Severity: serious The arch all build for libreoffice 1:6.1.5~rc1-1 ( https://buildd.debian.org/status/fetch.php?pkg=libreoffice=all=1%3A6.1.5%7Erc1-1=1547977527=0 ) failed with javadoc: error - The code being documented uses modules but the packages defined inhttp://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. According to the reproducible builds site ( https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/libreoffice_6.1.4-4.rbuild.log.gz ) this also affects the existing version in testing 1:6.1.4-1 --- End Message --- --- Begin Message --- Source: openjdk-11 Source-Version: 11.0.2+9-1 We believe that the bug you reported is fixed in the latest version of openjdk-11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 13:15:59 +0100 Source: openjdk-11 Binary: openjdk-11-jdk-headless openjdk-11-jre-headless openjdk-11-jdk openjdk-11-jre openjdk-11-demo openjdk-11-source openjdk-11-doc openjdk-11-dbg openjdk-11-jre-zero Architecture: source Version: 11.0.2+9-1 Distribution: unstable Urgency: high Maintainer: OpenJDK Team Changed-By: Matthias Klose Description: openjdk-11-dbg - Java runtime based on OpenJDK (debugging symbols) openjdk-11-demo - Java runtime based on OpenJDK (demos and examples) openjdk-11-doc - OpenJDK Development Kit (JDK) documentation openjdk-11-jdk - OpenJDK Development Kit (JDK) openjdk-11-jdk-headless - OpenJDK Development Kit (JDK) (headless) openjdk-11-jre - OpenJDK Java runtime, using openjdk-11-jre-headless - OpenJDK Java runtime, using (headless) openjdk-11-jre-zero - Alternative JVM for OpenJDK, using Zero openjdk-11-source - OpenJDK Development Kit (JDK) source files Closes: 919798 920020 Changes: openjdk-11 (11.0.2+9-1) unstable; urgency=high . * OpenJDK 11.0.2 release (build 9). . [ Matthias Klose ] * Backport the fix for S8212233. Closes: #920020, #919798. . [ Tiago Stürmer Daitx ] * debian/buildwatch.sh: use same code from openjdk-8. * debian/control.in, debian/control: - add fixed build depends for jtreg and xfvb. - remove Conflicts: oracle-java11-installer. (LP: #1782630) * debian/rules: - call the same testsuites scripts used for autopkgtest. - removed jtreg and xvfb build dependency logic and moved the bdeps into debian/control.in. - added gen-autopackage rule to generate autopkgtest scripts from templates. - copy flight recorder configuration files. - fix logging in langtools testing. - don't ignore/exclude the release file from the jdk package, it is required by jtreg tests and autopkgtests will fail without it. - don't run nashorn testsuite. * update dep8 tests: - debian/tests/control: updated to run openjdk-11 tests. - debian/tests/hotspot, debian/tests/jaxp, debian/tests/jdk, debian/tests/langtools: use the new jt .sh scripts. - debian/tests/jtdiff-autopkgtest.sh: diff build time and autopkgtest JTreports to show what changed. - debian/tests/jtreg-autopkgtest.in: template to generate the jtreg script used by the autopkgtest tests. - debian/tests/jtdiff-autopkgtest.sh: used by the scripts to report any differences between the autopkgtest and the tests results generated during the openjdk package build. - debian/tests/jtreg-autopkgtest.sh: used by the scripts to run jtreg and put the resulting
Bug#919875: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #919798, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:commons-csv Version: 1.5-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibcommons-csv-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.commons:commons-csv:jar:1.5 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ org.apache.commons:commons-parent:debian, /<>/debian/maven-repo/org/apache/commons/commons-parent/debian/commons-parent-debian.pom, line 277, column 12 [WARNING] 'build.plugins.plugin.version' for org.apache.felix:maven-bundle-plugin is missing. @ org.apache.commons:commons-parent:debian, /<>/debian/maven-repo/org/apache/commons/commons-parent/debian/commons-parent-debian.pom, line 310, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-site-plugin:3.3: Plugin org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from it before. [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded from it before. [WARNING] The POM for org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 has not been downloaded from it before. [WARNING] The POM for
Bug#919895: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #919798, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-11-jdk-headless Version: 11.0.2+7-1 Severity: serious Dear Java Maintainers: There are a number of packages failing to build from source due to a regression in javadoc. As I didn't find a bug for that in the openjdk packages, I'm filing this report as the "main" bug and will reassign and merge all the other bugs to this one. Thanks. --- End Message --- --- Begin Message --- Source: openjdk-11 Source-Version: 11.0.2+9-1 We believe that the bug you reported is fixed in the latest version of openjdk-11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 13:15:59 +0100 Source: openjdk-11 Binary: openjdk-11-jdk-headless openjdk-11-jre-headless openjdk-11-jdk openjdk-11-jre openjdk-11-demo openjdk-11-source openjdk-11-doc openjdk-11-dbg openjdk-11-jre-zero Architecture: source Version: 11.0.2+9-1 Distribution: unstable Urgency: high Maintainer: OpenJDK Team Changed-By: Matthias Klose Description: openjdk-11-dbg - Java runtime based on OpenJDK (debugging symbols) openjdk-11-demo - Java runtime based on OpenJDK (demos and examples) openjdk-11-doc - OpenJDK Development Kit (JDK) documentation openjdk-11-jdk - OpenJDK Development Kit (JDK) openjdk-11-jdk-headless - OpenJDK Development Kit (JDK) (headless) openjdk-11-jre - OpenJDK Java runtime, using openjdk-11-jre-headless - OpenJDK Java runtime, using (headless) openjdk-11-jre-zero - Alternative JVM for OpenJDK, using Zero openjdk-11-source - OpenJDK Development Kit (JDK) source files Closes: 919798 920020 Changes: openjdk-11 (11.0.2+9-1) unstable; urgency=high . * OpenJDK 11.0.2 release (build 9). . [ Matthias Klose ] * Backport the fix for S8212233. Closes: #920020, #919798. . [ Tiago Stürmer Daitx ] * debian/buildwatch.sh: use same code from openjdk-8. * debian/control.in, debian/control: - add fixed build depends for jtreg and xfvb. - remove Conflicts: oracle-java11-installer. (LP: #1782630) * debian/rules: - call the same testsuites scripts used for autopkgtest. - removed jtreg and xvfb build dependency logic and moved the bdeps into debian/control.in. - added gen-autopackage rule to generate autopkgtest scripts from templates. - copy flight recorder configuration files. - fix logging in langtools testing. - don't ignore/exclude the release file from the jdk package, it is required by jtreg tests and autopkgtests will fail without it. - don't run nashorn testsuite. * update dep8 tests: - debian/tests/control: updated to run openjdk-11 tests. - debian/tests/hotspot, debian/tests/jaxp, debian/tests/jdk, debian/tests/langtools: use the new jt .sh scripts. - debian/tests/jtdiff-autopkgtest.sh: diff build time and autopkgtest JTreports to show what changed. - debian/tests/jtreg-autopkgtest.in: template to generate the jtreg script used by the autopkgtest tests. - debian/tests/jtdiff-autopkgtest.sh: used by the scripts to report any differences between the autopkgtest and the tests results generated during the openjdk package build. - debian/tests/jtreg-autopkgtest.sh: used by the scripts to run jtreg and put the resulting artifacts in the right places, by default will remove all non .jtr files after it is done to preserve space. - debian/tests/hotspot, debian/tests/jaxp, debian/tests/jdk, debian/tests/langtools: run same testsuites as
Bug#919883: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #919798, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice Version: 1:6.1.4-1 Severity: serious The arch all build for libreoffice 1:6.1.5~rc1-1 ( https://buildd.debian.org/status/fetch.php?pkg=libreoffice=all=1%3A6.1.5%7Erc1-1=1547977527=0 ) failed with javadoc: error - The code being documented uses modules but the packages defined inhttp://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. According to the reproducible builds site ( https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/libreoffice_6.1.4-4.rbuild.log.gz ) this also affects the existing version in testing 1:6.1.4-1 --- End Message --- --- Begin Message --- Source: openjdk-11 Source-Version: 11.0.2+9-1 We believe that the bug you reported is fixed in the latest version of openjdk-11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 13:15:59 +0100 Source: openjdk-11 Binary: openjdk-11-jdk-headless openjdk-11-jre-headless openjdk-11-jdk openjdk-11-jre openjdk-11-demo openjdk-11-source openjdk-11-doc openjdk-11-dbg openjdk-11-jre-zero Architecture: source Version: 11.0.2+9-1 Distribution: unstable Urgency: high Maintainer: OpenJDK Team Changed-By: Matthias Klose Description: openjdk-11-dbg - Java runtime based on OpenJDK (debugging symbols) openjdk-11-demo - Java runtime based on OpenJDK (demos and examples) openjdk-11-doc - OpenJDK Development Kit (JDK) documentation openjdk-11-jdk - OpenJDK Development Kit (JDK) openjdk-11-jdk-headless - OpenJDK Development Kit (JDK) (headless) openjdk-11-jre - OpenJDK Java runtime, using openjdk-11-jre-headless - OpenJDK Java runtime, using (headless) openjdk-11-jre-zero - Alternative JVM for OpenJDK, using Zero openjdk-11-source - OpenJDK Development Kit (JDK) source files Closes: 919798 920020 Changes: openjdk-11 (11.0.2+9-1) unstable; urgency=high . * OpenJDK 11.0.2 release (build 9). . [ Matthias Klose ] * Backport the fix for S8212233. Closes: #920020, #919798. . [ Tiago Stürmer Daitx ] * debian/buildwatch.sh: use same code from openjdk-8. * debian/control.in, debian/control: - add fixed build depends for jtreg and xfvb. - remove Conflicts: oracle-java11-installer. (LP: #1782630) * debian/rules: - call the same testsuites scripts used for autopkgtest. - removed jtreg and xvfb build dependency logic and moved the bdeps into debian/control.in. - added gen-autopackage rule to generate autopkgtest scripts from templates. - copy flight recorder configuration files. - fix logging in langtools testing. - don't ignore/exclude the release file from the jdk package, it is required by jtreg tests and autopkgtests will fail without it. - don't run nashorn testsuite. * update dep8 tests: - debian/tests/control: updated to run openjdk-11 tests. - debian/tests/hotspot, debian/tests/jaxp, debian/tests/jdk, debian/tests/langtools: use the new jt .sh scripts. - debian/tests/jtdiff-autopkgtest.sh: diff build time and autopkgtest JTreports to show what changed. - debian/tests/jtreg-autopkgtest.in: template to generate the jtreg script used by the autopkgtest tests. - debian/tests/jtdiff-autopkgtest.sh: used by the scripts to report any differences between the autopkgtest and the tests results generated during the openjdk package build. - debian/tests/jtreg-autopkgtest.sh: used by the scripts to run jtreg and put the resulting
Bug#920020: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #920020, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-11-jdk Version: 11.0.2+7-1 Severity: grave Tags: patch Justification: renders package unusable [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on project octopus-rpctunnel: MavenReportException: Error while generating Javadoc: [ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. The cause for this is: https://bugs.openjdk.java.net/browse/JDK-8212233 The fix is (not tested by myself): http://hg.openjdk.java.net/jdk/jdk/rev/8ce4083fc831 via: https://bugs.openjdk.java.net/browse/JDK-8217177 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages openjdk-11-jdk depends on: ii libc62.28-5 ii openjdk-11-jdk-headless 11.0.2+7-1 ii openjdk-11-jre 11.0.2+7-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages openjdk-11-jdk recommends: pn libxt-dev Versions of packages openjdk-11-jdk suggests: pn openjdk-11-demo pn openjdk-11-source pn visualvm -- no debconf information --- End Message --- --- Begin Message --- Source: openjdk-11 Source-Version: 11.0.2+9-1 We believe that the bug you reported is fixed in the latest version of openjdk-11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated openjdk-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jan 2019 13:15:59 +0100 Source: openjdk-11 Binary: openjdk-11-jdk-headless openjdk-11-jre-headless openjdk-11-jdk openjdk-11-jre openjdk-11-demo openjdk-11-source openjdk-11-doc openjdk-11-dbg openjdk-11-jre-zero Architecture: source Version: 11.0.2+9-1 Distribution: unstable Urgency: high Maintainer: OpenJDK Team Changed-By: Matthias Klose Description: openjdk-11-dbg - Java runtime based on OpenJDK (debugging symbols) openjdk-11-demo - Java runtime based on OpenJDK (demos and examples) openjdk-11-doc - OpenJDK Development Kit (JDK) documentation openjdk-11-jdk - OpenJDK Development Kit (JDK) openjdk-11-jdk-headless - OpenJDK Development Kit (JDK) (headless) openjdk-11-jre - OpenJDK Java runtime, using openjdk-11-jre-headless - OpenJDK Java runtime, using (headless) openjdk-11-jre-zero - Alternative JVM for OpenJDK, using Zero openjdk-11-source - OpenJDK Development Kit (JDK) source files Closes: 919798 920020 Changes: openjdk-11 (11.0.2+9-1) unstable; urgency=high . * OpenJDK 11.0.2 release (build 9). . [ Matthias Klose ] * Backport the fix for S8212233. Closes: #920020, #919798. . [ Tiago Stürmer Daitx ] * debian/buildwatch.sh: use same code from openjdk-8. * debian/control.in, debian/control: - add fixed build depends for jtreg and xfvb. - remove Conflicts: oracle-java11-installer. (LP: #1782630) * debian/rules: - call the same testsuites scripts used for autopkgtest. - removed jtreg and xvfb build dependency logic and moved the bdeps into debian/control.in. - added gen-autopackage rule to generate autopkgtest scripts from templates. - copy flight recorder configuration files. - fix
Bug#919878: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #919798, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:servlet-api Version: 4.0.1-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibservlet-api-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [INFO] [INFO] --< javax.servlet:javax.servlet-api >--- [INFO] Building Java Servlet API 4.0.1 [INFO] [ jar ]- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ javax.servlet-api --- [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 11 resources [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ javax.servlet-api --- [INFO] Changes detected - recompiling the module! [WARNING] File encoding has not been set, using platform encoding ANSI_X3.4-1968, i.e. build is platform dependent! [INFO] Compiling 77 source files to /<>/target/classes [INFO] [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ javax.servlet-api --- [INFO] [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ javax.servlet-api --- [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /<>/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ javax.servlet-api --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ javax.servlet-api --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.1.1:jar (default-jar) @ javax.servlet-api --- [INFO] Building jar: /<>/target/javax.servlet-api-4.0.1.jar [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (default) @ javax.servlet-api --- [WARNING] Source files encoding has not been set, using platform encoding ANSI_X3.4-1968, i.e. build is platform dependent! [INFO] Adding the --ignore-source-errors option [INFO] Loading source file /<>/src/main/java/javax/servlet/SessionCookieConfig.java... Loading source file /<>/src/main/java/javax/servlet/ServletRequestAttributeListener.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpSessionBindingEvent.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpServletMapping.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpSession.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpFilter.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpServletResponse.java... Loading source file
Bug#919874: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#919798: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #919798, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bsaf Version: 1.9.2-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibbetter-appframework-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jdesktop.bsaf:bsaf:jar:1.9.2 [WARNING] 'dependencies.dependency.systemPath' for javax.jnlp:jnlp:jar should use a variable instead of a hard-coded path /usr/share/java/netx.jar @ line 129, column 16 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] ---< org.jdesktop.bsaf:bsaf >--- [INFO] Building bsaf 1.9.2 [INFO] [ jar ]- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bsaf --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 7 resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ bsaf --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 38 source files to /<>/target/classes [WARNING] bootstrap class path not set in conjunction with -source 6 [WARNING] source value 6 is obsolete and will be removed in a future release [WARNING] target value 1.6 is obsolete and will be removed in a future release [WARNING] To suppress warnings about obsolete options, use -Xlint:-options. [WARNING] /<>/src/main/java/org/jdesktop/application/SessionStorage.java:[13,19] java.applet.Applet in java.applet has been deprecated [WARNING] /<>/src/main/java/org/jdesktop/application/ResourceMap.java:[15,16] java.awt.Event in java.awt has been deprecated [WARNING] /<>/src/main/java/org/jdesktop/application/SessionStorage.java:[210,84] java.applet.Applet in java.applet has been deprecated [WARNING] /<>/src/main/java/org/jdesktop/application/Application.java:[232,18] isAccessible() in java.lang.reflect.AccessibleObject has been deprecated [WARNING] /<>/src/main/java/org/jdesktop/application/ResourceMap.java:[1257,31] isAccessible() in java.lang.reflect.AccessibleObject has been deprecated [WARNING] /<>/src/main/java/org/jdesktop/application/ResourceMap.java:[1277,27] isAccessible() in java.lang.reflect.AccessibleObject has been deprecated [WARNING] /<>/src/main/java/org/jdesktop/application/ResourceMap.java:[1511,74] getMenuShortcutKeyMask() in java.awt.Toolkit has been deprecated [WARNING]
Bug#919878: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Tue, 22 Jan 2019 12:42:24 + with message-id and subject line Bug#920020: fixed in openjdk-11 11.0.2+9-1 has caused the Debian Bug report #920020, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:servlet-api Version: 4.0.1-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibservlet-api-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [INFO] [INFO] --< javax.servlet:javax.servlet-api >--- [INFO] Building Java Servlet API 4.0.1 [INFO] [ jar ]- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ javax.servlet-api --- [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 11 resources [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ javax.servlet-api --- [INFO] Changes detected - recompiling the module! [WARNING] File encoding has not been set, using platform encoding ANSI_X3.4-1968, i.e. build is platform dependent! [INFO] Compiling 77 source files to /<>/target/classes [INFO] [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ javax.servlet-api --- [INFO] [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ javax.servlet-api --- [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /<>/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ javax.servlet-api --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ javax.servlet-api --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.1.1:jar (default-jar) @ javax.servlet-api --- [INFO] Building jar: /<>/target/javax.servlet-api-4.0.1.jar [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (default) @ javax.servlet-api --- [WARNING] Source files encoding has not been set, using platform encoding ANSI_X3.4-1968, i.e. build is platform dependent! [INFO] Adding the --ignore-source-errors option [INFO] Loading source file /<>/src/main/java/javax/servlet/SessionCookieConfig.java... Loading source file /<>/src/main/java/javax/servlet/ServletRequestAttributeListener.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpSessionBindingEvent.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpServletMapping.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpSession.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpFilter.java... Loading source file /<>/src/main/java/javax/servlet/http/HttpServletResponse.java... Loading source file
