Bug#906679: marked as done (pam-p11 FTBFS on 32bit: error: comparison between signed and unsigned integer expressions)
Your message dated Sat, 03 Nov 2018 05:19:56 +
with message-id
and subject line Bug#906679: fixed in pam-p11 0.2.0-2
has caused the Debian Bug report #906679,
regarding pam-p11 FTBFS on 32bit: error: comparison between signed and unsigned
integer expressions
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.)
--
906679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pam-p11
Version: 0.2.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pam-p11=sid
...
pam_p11.c: In function 'randomize':
pam_p11.c:556:36: error: comparison between signed and unsigned integer
expressions [-Werror=sign-compare]
if (0 <= fd && read(fd, r, r_len) == r_len) {
^~
--- End Message ---
--- Begin Message ---
Source: pam-p11
Source-Version: 0.2.0-2
We believe that the bug you reported is fixed in the latest version of
pam-p11, 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 906...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Eric Dorland (supplier of updated pam-p11 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: Sat, 03 Nov 2018 00:04:44 -0400
Source: pam-p11
Binary: libpam-p11
Architecture: source
Version: 0.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSC Maintainers
Changed-By: Eric Dorland
Description:
libpam-p11 - PAM module for using PKCS#11 smart cards
Closes: 906679
Changes:
pam-p11 (0.2.0-2) unstable; urgency=medium
.
* Cherrypick unsigned comparison fix (Closes: 906679)
* Standards-Version to 4.2.1.4
* Add Rules-Requires-Root: no
Checksums-Sha1:
4649270f86111f84c424a41723612ea2f51175fe 1947 pam-p11_0.2.0-2.dsc
e91c96460ad91117e51938879e2fe61eb477d0d7 3928 pam-p11_0.2.0-2.debian.tar.xz
bc513f5ac2e35679b9e4999b4b6c5361e08b4ccd 6430 pam-p11_0.2.0-2_amd64.buildinfo
Checksums-Sha256:
91a00657ebd6f92503133327eaa4eee5ce28a1fb47993929bddc32b61e716b72 1947
pam-p11_0.2.0-2.dsc
9e3210f400357b65de681665dd398dbe10aa3f7a199e256d8c4da0387403f1a8 3928
pam-p11_0.2.0-2.debian.tar.xz
636db4b0f41fc7dbbf9104dc1dc3f3130011a385984743f691f95e078f18c386 6430
pam-p11_0.2.0-2_amd64.buildinfo
Files:
7969e6d264f6a78e68f4caacd4e5161e 1947 admin optional pam-p11_0.2.0-2.dsc
cee457c7f0cb25a2256125d56b632b92 3928 admin optional
pam-p11_0.2.0-2.debian.tar.xz
73da7b8ceb2b9073eecc3919d1c8ec02 6430 admin optional
pam-p11_0.2.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEQ88SKPcm/VtHTOliwlb71QAiHpMFAlvdKvYACgkQwlb71QAi
HpO3IRAAjxKNRovyK8wX71kdk5rOdPDccwq/jAMfuY+yDXWJ6IPTD9BbAhUotcE2
nWMWd9913fBVXN5FddDor9b6wDkcQqHckjYjMFWLEZbyCVFFwaWIZ9lJ3w51T3Nj
uGSjAdMHDjaElk7gEX818vIO1vo6anm8jhJ4UKUjWEuQ4HpmPt48Zr51Z3cSPzsV
WwlLiRpWnLfB6CfdUjts/fBvQdH6xhdi98Et8Dyp7By040UIcj87ohnMo1oJJSzC
rPKLICgQaOq717kOPO416uq/pslQsn/A29FaB6qKrrMuJvxn3sQB49XkRrIw2XpJ
El5/06syE8Hu6o2xeNzl/9ZqYKQCQjqMCVdJlCuDDFM87ronk3lHkaCg0ROHuJZp
XmFOBQEdn8/k+inXz+H9g0GvJHW3PMJei93AoLChnFL5Ar7tK6nWlRYn0GPpf7/Y
TXhfxjBpAdfGVUeMdgVB3NnkWcvr04QwQFK7w4eIwvT/qzVt9IhMwN7cXTX45nGE
joSlhXNEdqyo3bOCLHpUdNrVBq/ns/EjHcgRraIbMpWkj5h9JHpj83CZtDgESHL7
tPXfUabKtRShLMeLcPJTcxPQAn7gDywG82BReILGPlYjlcfi1gCpprHpWGxfdkaw
riu9JY4I8xHvSbsKcGE9YajpB/l9mPgNRZMNJOkFxyYQYmTMah4=
=DvBf
-END PGP SIGNATURE End Message ---
Bug#912709: Max. recursion depth with nested structures exceeded
Package: apt-show-versions Version: 0.22.8 Severity: grave # apt-show-versions Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux-gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Works fine when non-root though. P.S., # apt-show-versions -i Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux-gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. -- System Information: Debian Release: buster/sid APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages apt-show-versions depends on: ii apt 1.7.0 ii libapt-pkg-perl 0.1.34+b1 ii perl [libstorable-perl] 5.28.0-3 apt-show-versions recommends no packages. apt-show-versions suggests no packages. -- no debconf information
Bug#912370: marked as done (xapian-core: shlibs automatic update rule missing dependency)
Your message dated Sat, 03 Nov 2018 03:04:04 + with message-id and subject line Bug#912370: fixed in xapian-core 1.4.9-1 has caused the Debian Bug report #912370, regarding xapian-core: shlibs automatic update rule missing 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.) -- 912370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xapian-bindings, xapers Control: found -1 xapian-bindings/1.4.8-1 Control: found -1 xapers/0.8.2-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of xapian-bindings the autopkgtest of xapers fails in testing when that autopkgtest is run with the binary packages of xapian-bindings from unstable. It passes when run with only packages from testing. In tabular form: passfail xapian-bindingsfrom testing1.4.8-1 xapers from testing0.8.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Interestingly enough, the test reports 55 tests failed, but autopkgtest doesn't fail on that. The autopkgtest fails on the fact that there is output on stderr. Currently this regression is contributing to the delay of the migration of xapian-bindings to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from xapian-bindings/1.4.8-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=xapian-bindings https://ci.debian.net/data/autopkgtest/testing/amd64/x/xapers/1229318/log.gz autopkgtest [18:22:08]: test basic: - - - - - - - - - - results - - - - - - - - - - basicFAIL stderr: diff: /tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags: No such file or directory autopkgtest [18:22:08]: test basic: - - - - - - - - - - stderr - - - - - - - - - - diff: /tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags: No such file or directory cp: cannot stat '/tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags': No such file or directory diff: all.5.output: No such file or directory diff: /tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/02/bibtex: No such file or directory cp: cannot stat '/tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/02/bibtex': No such file or directory diff: all.8.output: No such file or directory diff: /tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags: No such file or directory cp: cannot stat '/tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags': No such file or directory diff: all.53.output: No such file or directory diff: /tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags: No such file or directory cp: cannot stat '/tmp/autopkgtest-lxc.rqz_vq45/downtmp/build.rsR/src/test/tmp.all/docs/01/tags': No such file or directory diff: all.55.output: No such file or directory signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: xapian-core Source-Version: 1.4.9-1 We believe that the bug you reported is fixed in the latest version of xapian-core, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated xapian-core 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
Bug#912343: marked as done (libxapian30: New term position bugs in 1.4.8)
Your message dated Sat, 03 Nov 2018 03:04:04 + with message-id and subject line Bug#912343: fixed in xapian-core 1.4.9-1 has caused the Debian Bug report #912343, regarding libxapian30: New term position bugs in 1.4.8 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.) -- 912343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxapian30 Version: 1.4.8-1 Severity: grave Tags: upstream Justification: causes non-serious data loss There's a bug introduced by the upstream 1.4.8 release with handling positional data. It only manifests when positional data is NOT added in ascending position order, which is probably a fairly rare case, but the consequences are that the encoded positional data can end up corrupted. I am currently testing a patch and will upload a new package once I'm happy with it - probably today or tomorrow. Cheers, Olly --- End Message --- --- Begin Message --- Source: xapian-core Source-Version: 1.4.9-1 We believe that the bug you reported is fixed in the latest version of xapian-core, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated xapian-core 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: Sat, 03 Nov 2018 15:27:44 +1300 Source: xapian-core Binary: libxapian30 libxapian-dev xapian-tools xapian-doc xapian-examples Architecture: source Version: 1.4.9-1 Distribution: unstable Urgency: medium Maintainer: Olly Betts Changed-By: Olly Betts Description: libxapian-dev - Development files for Xapian search engine library libxapian30 - Search engine library xapian-doc - Core Xapian documentation xapian-examples - Xapian simple example programs xapian-tools - Basic tools for Xapian search engine library Closes: 912343 912370 Changes: xapian-core (1.4.9-1) unstable; urgency=medium . * New upstream release + Fixes term position bugs introduced in 1.4.8. (Closes: #912343) * debian/rules: Add dependencies so regeneration of libxapian30.shlibs is triggered when required - this file should have been regenerated for 1.4.8-1 but wasn't due to the lack of such a dependency. (Closes: #912370) Checksums-Sha1: e6a32a2f5e75175b0b791e427bc6e5b49cc10cb0 2139 xapian-core_1.4.9-1.dsc 118a47b76b1002303f6761ba395eb42cb36f3b0e 2880024 xapian-core_1.4.9.orig.tar.xz 6bccfbb2c4b47074d5ebd0e0b7fb953b9ff409a5 19228 xapian-core_1.4.9-1.debian.tar.xz 1eacc3baa06f1c618f47c248083c88f39691041e 7955 xapian-core_1.4.9-1_amd64.buildinfo Checksums-Sha256: 7f8cbdd218833cf1e26392019eeaeda05534282a42a75cbaed38546fe015c581 2139 xapian-core_1.4.9-1.dsc cde9c39d014f04c09b59d9c21551db9794c10617dc69ab4c9826352a533df5cc 2880024 xapian-core_1.4.9.orig.tar.xz 84f36a62cf67486de5de46272b4c85b95c834712ed5625d08faeefe3275745c1 19228 xapian-core_1.4.9-1.debian.tar.xz 3ded8ce6218654d1ecd78dbb6327f38ce0939d1d06187586bcc0655cf67327cf 7955 xapian-core_1.4.9-1_amd64.buildinfo Files: a8cfd9b692559b8c97ef5e67cd45ac45 2139 libs optional xapian-core_1.4.9-1.dsc e0361d7994287edf1248d320758e9f84 2880024 libs optional xapian-core_1.4.9.orig.tar.xz 8d87a1e2bef856ca033d62acfa991ab4 19228 libs optional xapian-core_1.4.9-1.debian.tar.xz 63c761c46a1965296991a394e8d41098 7955 libs optional xapian-core_1.4.9-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAlvdCtAACgkQGBR7Bzut KwfSqQ/+JcOpFv1i3yBWwYTDlOT2gKNOs8gBKV96dkw1dMrp0ob78NaBU3C9xL08 ZDTEkFEh7kBW1osnFYQXwWAZrW/DXTO8wFySxDi6kW4n5CH7LSOOhhMxTuytPwTV G9neQzMoGa7WMl10sFBPXhwVLfsM9K8stKols0dNkmEV+fVwaZ58quSaU4w6Wt3w in+Uu/Eu0BQqy2aM00XbUWcvglJv+eWCAXfki2r7NEgGMoTAdSYo9Hf/nQMaOuc+ sKldNMW/cRA/NfrQ+5Qr79a/B3QJ4Y1u5LhhafsCSDgnkdiKn9WBFuRO/53mDEWX CxrXtS58mwm6lkOFFxqw1Np6x8nDUqTJlBgkU990tfTklrEO8DyzTQx5LY5b+hS8 LNbs7TNa0D2H2boHiqYCAZ9QYObC+lg2JydN/0/Epe7Td6/GCgeE16HPeywwXrbj TQ4sScrtydEH6ItU9NQAgtcZinsV7GvtDuWA+kKG+7l+yOdzboeGwvU/HWKSPZiM 2aBOc6hhI0cU6NcbvpShzfT4Bg8D+byeKIdgYG4ABnBZTiWmqf3sY7mAnC205q4u
Bug#912684: perl-modules-5.28 needs versioned Provides for modules it bundles
On Fri, 02 Nov 2018 22:03:43 +0200, Adrian Bunk wrote: > Package: perl-modules-5.28 > Version: 5.28.0-3 > Severity: serious > > perl-modules-5.28 has > Replaces+Breaks: libextutils-parsexs-perl (<< 3.39) > > This makes libextutils-parsexs-perl in unstable not installable. Right, thanks also for filing a bug against libextutils-parsexs-perl. (This happens for each release that some dual-lifed modules are newer in core than their separate equivalents on the CPAN. Either this fixes itself with a new separate release or we remove the package at some point.) > libextutils-parsexs-perl does have reverse dependencies > in unstable, including revers dependencies with versioned > dependencies. I checked all reverse (build) dependencies and didn't see any problems; all of them are either unversioned or have the form "perl (>= 5.x) | libextutils-parsexs-perl [(>= 3.x]). So I think we have no actual problem here. > Versioned Provides for such modules are required. That's a long story: https://bugs.debian.org/758100 As Niko wrote in #80: | These bugs are now fixed (and deployed on the Debian infrastructure), | so we could try again. | I think I want to do the 5.28 transition first, though. (Leaving handling of this bug to Niko/Dom.) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Rolling Stones: Lonely signature.asc Description: Digital Signature
Bug#912030: marked as done (vim-youcompleteme depends on ycmd (< 0+20161219+git486b809.1) but 0+20180708+git600f54d-1 is to be installed)
Your message dated Sat, 03 Nov 2018 01:19:54 + with message-id and subject line Bug#912030: fixed in vim-youcompleteme 0+20181101+gitfaa019a-0.1 has caused the Debian Bug report #912030, regarding vim-youcompleteme depends on ycmd (< 0+20161219+git486b809.1) but 0+20180708+git600f54d-1 is to be installed 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.) -- 912030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim-youcompleteme Version: 0+20161219+git194ff33-1 Severity: serious Tags: buster sid The following packages have unmet dependencies: vim-youcompleteme : Depends: ycmd (< 0+20161219+git486b809.1) but 0+20180708+git600f54d-1 is to be installed --- End Message --- --- Begin Message --- Source: vim-youcompleteme Source-Version: 0+20181101+gitfaa019a-0.1 We believe that the bug you reported is fixed in the latest version of vim-youcompleteme, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Kalnischkies (supplier of updated vim-youcompleteme 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: Sat, 03 Nov 2018 01:35:40 +0100 Source: vim-youcompleteme Binary: vim-youcompleteme Architecture: source Version: 0+20181101+gitfaa019a-0.1 Distribution: unstable Urgency: medium Maintainer: Onur Aslan Changed-By: David Kalnischkies Description: vim-youcompleteme - fast, as-you-type, fuzzy-search code completion engine for Vim Closes: 912030 Changes: vim-youcompleteme (0+20181101+gitfaa019a-0.1) unstable; urgency=medium . * Non-maintainer upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Sylvestre Ledru ] * New upstream release - Refresh path-to-server-script.patch . [ David Kalnischkies ] * New upstream version 0+20181101+gitfaa019a - Use uscan to generate tarball from upstream git HEAD - Refresh path-to-server-script.patch * Depend on ycmd via ycmd-core-version provides (Closes: #912030) * Don't use dpkg-parsechangelog directly in debian/rules * Switch from debhelper 9 to 11 * Bump Standards-Version to 4.2.1 (no changes) * Run nose-based tests at buildtime * Use https for upstream homepage * Set R³: no in debian/control Checksums-Sha1: 56512d15f545d02a8cf84038d5c6586502d2fca7 2335 vim-youcompleteme_0+20181101+gitfaa019a-0.1.dsc 273930d5c0b708bf53bb77df75c65e13ddc0cd6c 187420 vim-youcompleteme_0+20181101+gitfaa019a.orig.tar.xz 895ccfb0f533e6bd0531c08d104b123bc5d90a01 7824 vim-youcompleteme_0+20181101+gitfaa019a-0.1.debian.tar.xz 1ce94008e643fcc36725462a0228ab25ef2f9979 7167 vim-youcompleteme_0+20181101+gitfaa019a-0.1_amd64.buildinfo Checksums-Sha256: 298c3136d5b8d7568f54a9d56e0b75889033d8f22e22d61c42d93813cb248c56 2335 vim-youcompleteme_0+20181101+gitfaa019a-0.1.dsc 048613aef55db9bcc3bccf7c6db38f3d09a76e068328b1d84b8a8f4e02d0ac39 187420 vim-youcompleteme_0+20181101+gitfaa019a.orig.tar.xz 183db1ef9ff5a5e99a696beb69205df6810e860907a8e14317c2e027e9418188 7824 vim-youcompleteme_0+20181101+gitfaa019a-0.1.debian.tar.xz 333e4a36a28a7605e19cf4ee258a36c16433a96a89519a8b4fd6d7ae54408c27 7167 vim-youcompleteme_0+20181101+gitfaa019a-0.1_amd64.buildinfo Files: 85ddea5f781683ec9202058c52295dad 2335 editors optional vim-youcompleteme_0+20181101+gitfaa019a-0.1.dsc 25155d1b63bb2053877701c9aa36dbba 187420 editors optional vim-youcompleteme_0+20181101+gitfaa019a.orig.tar.xz b439bc8fc3023b5068d4b4db3225f99e 7824 editors optional vim-youcompleteme_0+20181101+gitfaa019a-0.1.debian.tar.xz 4e39643477b88f168b00c71dbacdca6b 7167 editors optional vim-youcompleteme_0+20181101+gitfaa019a-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5sn+Q4uCja/tn0GrMRvlz3HQeIMFAlvc8IITHGRvbmt1bHRA ZGViaWFuLm9yZwAKCRAxG+XPcdB4g41UD/927H4IXrJ7i4bPUKPufe374r5mHPpf nm2OwdOGz4b+XsTnjGZ78So/If+g9EtFYiP8w1ZSWN18GSYBIAGiQcD+0B2oJ4+A NIPFo2os68cDMFmQ0wjy9+NZ2uie4DXhfygcaVsCIUHesol6Grg3yEa9GcSG8gh6
Bug#912642: marked as done (activemq: FTBFS with Java 11 due to javax.annotation removal)
Your message dated Sat, 03 Nov 2018 00:04:31 + with message-id and subject line Bug#912642: fixed in activemq 5.15.7-1 has caused the Debian Bug report #912642, regarding activemq: FTBFS with Java 11 due to javax.annotation removal 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.) -- 912642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: activemq Version: 5.15.6-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/activemq.html ... [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /build/1st/activemq-5.15.6/activemq-client/src/main/java/org/apache/activemq/filter/DestinationMapEntry.java:[19,24] package javax.annotation does not exist [INFO] 1 error [INFO] - --- End Message --- --- Begin Message --- Source: activemq Source-Version: 5.15.7-1 We believe that the bug you reported is fixed in the latest version of activemq, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated activemq 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: Sat, 03 Nov 2018 00:24:44 +0100 Source: activemq Binary: libactivemq-java activemq Architecture: source Version: 5.15.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: activemq - Java message broker - server libactivemq-java - Java message broker core libraries Closes: 912642 Changes: activemq (5.15.7-1) unstable; urgency=medium . * Team upload. * New upstream version 5.15.7. * Fix FTBFS with OpenJDK 11 by build-depending on libactivation-java and libgeronimo-annotation-1.3-spec-java. (Closes: #912642) * Add java11.patch. Checksums-Sha1: ae6f072dd331b6d96dafdbb8270de3ebe3858184 3604 activemq_5.15.7-1.dsc c869cbebe153ba6d8a64a9678d8d8146bb7c18bf 2661740 activemq_5.15.7.orig.tar.xz e1bcb4d475bce39ea6b1d25c285bfe369f9073fd 16512 activemq_5.15.7-1.debian.tar.xz ae102c2ffd0a167ff0fb3e9624488d06838f84bc 18076 activemq_5.15.7-1_amd64.buildinfo Checksums-Sha256: 1452ad61488961389c096bc514a23bb0e256abf70cc02fb20253314af43e81f0 3604 activemq_5.15.7-1.dsc 18850fc66168305513d626797d5d6b359031639643c578eebaa11767e886d455 2661740 activemq_5.15.7.orig.tar.xz 70e431b4f6f8b6b3a1b1ee322291fc23582581ead9c4a6a07fed87dc552339ec 16512 activemq_5.15.7-1.debian.tar.xz 60553abc91ff380a47d5cd045135d58a537e5f40de997ec607bf369551b1e578 18076 activemq_5.15.7-1_amd64.buildinfo Files: e550f90e6e35c4acaf838646913cc45c 3604 java optional activemq_5.15.7-1.dsc 6270d51df5aab5e70d8a4a3738b9e291 2661740 java optional activemq_5.15.7.orig.tar.xz c19f72171324b7059e5bf31ddf20b281 16512 java optional activemq_5.15.7-1.debian.tar.xz dc8998bd3d5a1ff929c681c3da202173 18076 java optional activemq_5.15.7-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlvc31NfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1Hk1KgP/inu/QMauB6ps52U+Gnyxk14R8qZZ+cqt0rW 0hR/Vqo1TwlK2ESqpJJfR53Ns1UrfGQj9p7EADuBDwrPX1wgGSXXfizkFdK7FFFx Xhf5PAi+UK8qopagc/mRUeBxcVhsqrxZ71t28DYg0/fyFqmxDw6Ci5uHH4yGyo98 0kzIxhGu+44PVarXS/v9fnuYrE9uS5UQ1OMkYtWieB3bAl6KwFMDSsTTBPUjyVs1 JOmwqCrErXL+rZDNTD6ENKybSHDlzm81zGt8zRUCGQZe8/ygA/AG8xZXtN1dfm0m CjmUnzmu/ek7KogydA6xnh4bn8CsiKW5v2k5u26cqGthE/HBA3SiHQrGwWxOn1IK JjQP5DJeuT3Ejy7Ylo+Xl187YfwvRWf99/5xhHeGQrLeYo14Ey27I4L39WY6KtDT Nwh/67BVOt1Pze98aQYYMVOcPhPnUSyB6aHOp3U0Y3FvriHPe8ODYW2wdptl6Lih gW5glVGk36bGumkIRY8XzhOyjd+OFXzoMnH5LxnJUR6k1uBc1CQ4AVEghuR37Xll c7W5vQfn6fWd12euCPZyCX0SGsNEBDG8R6EFgszCD3Z74gFNXgX1nBhv1t2J0vOQ TZSotftzhjpEK2MhtX42my3778r7m4maGvSPHl4fQvy4ofmT98Yyl6ZH4MCYYJmB 2vSKT3+T =y6uW -END PGP SIGNATURE End Message ---
Processed: Bug #912642 in activemq marked as pending
Processing control commands: > tag -1 pending Bug #912642 [src:activemq] activemq: FTBFS with Java 11 due to javax.annotation removal Added tag(s) pending. -- 912642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912642: Bug #912642 in activemq marked as pending
Control: tag -1 pending Hello, Bug #912642 in activemq 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/activemq/commit/974a87ad4df217298cc7d464ee621eb7ac1e0653 Fix FTBFS with OpenJDK 11 by build-depending on libactivation-java. Closes: #912642 (this message was generated automatically) -- Greetings https://bugs.debian.org/912642
Bug#912547: marked as done (libpicocontainer-java: FTBFS with Java 11 due to javax.annotation removal)
Your message dated Fri, 02 Nov 2018 23:05:56 +
with message-id
and subject line Bug#912547: fixed in libpicocontainer-java 2.15-3
has caused the Debian Bug report #912547,
regarding libpicocontainer-java: FTBFS with Java 11 due to javax.annotation
removal
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.)
--
912547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpicocontainer-java
Version: 2.15-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpicocontainer-java.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/libpicocontainer-java-2.15'
jh_build --javadoc picocontainer-2.15.jar org
find org -name *.java -and -type f -print0 | xargs -s 512000 -0
/usr/lib/jvm/default-java/bin/javac -g -cp
/usr/share/java/paranamer.jar:debian/_jh_build.picocontainer-2.15 -d
debian/_jh_build.picocontainer-2.15 -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
org/picocontainer/lifecycle/JavaEE5LifecycleStrategy.java:13: error: package
javax.annotation does not exist
import javax.annotation.PostConstruct;
^
org/picocontainer/lifecycle/JavaEE5LifecycleStrategy.java:14: error: package
javax.annotation does not exist
import javax.annotation.PreDestroy;
^
org/picocontainer/lifecycle/JavaEE5LifecycleStrategy.java:41: error: cannot
find symbol
doLifecycleMethod(component, PostConstruct.class, true);
^
symbol: class PostConstruct
location: class JavaEE5LifecycleStrategy
org/picocontainer/lifecycle/JavaEE5LifecycleStrategy.java:50: error: cannot
find symbol
doLifecycleMethod(component, PreDestroy.class, false);
^
symbol: class PreDestroy
location: class JavaEE5LifecycleStrategy
org/picocontainer/lifecycle/JavaEE5LifecycleStrategy.java:101: error: cannot
find symbol
if (method.isAnnotationPresent(PreDestroy.class) ||
method.isAnnotationPresent(PostConstruct.class)) {
^
symbol: class PreDestroy
location: class JavaEE5LifecycleStrategy
org/picocontainer/lifecycle/JavaEE5LifecycleStrategy.java:101: error: cannot
find symbol
if (method.isAnnotationPresent(PreDestroy.class) ||
method.isAnnotationPresent(PostConstruct.class)) {
^
symbol: class PostConstruct
location: class JavaEE5LifecycleStrategy
org/picocontainer/injectors/Reinjector.java:141: warning: non-varargs call of
varargs method with inexact argument type for last parameter;
monitor, NO_LIFECYCLE, properties, key, implementation, null);
^
cast to Parameter for a varargs call
cast to Parameter[] for a non-varargs call and to suppress this warning
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
6 errors
2 warnings
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 123
--- End Message ---
--- Begin Message ---
Source: libpicocontainer-java
Source-Version: 2.15-3
We believe that the bug you reported is fixed in the latest version of
libpicocontainer-java, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Koschany (supplier of updated libpicocontainer-java
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: Fri, 02 Nov 2018 19:44:28 +0100
Source: libpicocontainer-java
Binary: libpicocontainer-java libpicocontainer-java-doc
Architecture: source
Version: 2.15-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Markus Koschany
Description:
Bug#910485: marked as done (libpsm2-2: times out on /dev/hfi1_0 device and causes test errors)
Your message dated Fri, 02 Nov 2018 22:50:25 + with message-id and subject line Bug#910485: fixed in libpsm2 11.2.68-2 has caused the Debian Bug report #910485, regarding libpsm2-2: times out on /dev/hfi1_0 device and causes test errors 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.) -- 910485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpsm2-2 Version: 11.2.68-1 Severity: serious Justification: causes other packages to fail tests; interferes with efficient execution; regression Programs running with libpsm2-2 11.2.68-1 now emit the warning: > ci-1538433288.12336hfi_wait_for_device: The /dev/hfi1_0 device failed to > appear after 15.0 seconds: Connection timed out which registers as an error in tests (I presume the warning is sent to stdout) This causes some tests and debci tests to fail, for instance petsc https://ci.debian.net/data/autopkgtest/unstable/amd64/p/petsc/1080389/log.gz I think it must fail because of the new involvement of stderr. Some other tests still pass, e.g. dolfin https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dolfin/1080544/log.gz In any case, this bug holds up execution for 15 secs or more, which itself is not good and is a regression from 10.3.58-2 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpsm2-2 depends on: ii libc6 2.27-6 ii libnuma1 2.0.12-1 libpsm2-2 recommends no packages. libpsm2-2 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libpsm2 Source-Version: 11.2.68-2 We believe that the bug you reported is fixed in the latest version of libpsm2, 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 910...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian T. Smith (supplier of updated libpsm2 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: Fri, 02 Nov 2018 16:26:42 -0500 Source: libpsm2 Binary: libpsm2-2 libpsm2-2-compat libpsm2-dev Architecture: source amd64 Version: 11.2.68-2 Distribution: unstable Urgency: medium Maintainer: Debian HPC team Changed-By: Brian T. Smith Description: libpsm2-2 - Intel PSM2 library libpsm2-2-compat - Compat library for Intel PSM2 libpsm2-dev - Development files for Intel PSM2 library Closes: 910485 Changes: libpsm2 (11.2.68-2) unstable; urgency=medium . * Correct hang in psm2_init() when there is no hfi1 device present. (Closes: #910485) Checksums-Sha1: 774643883aa7a77cad084c9f095fa7fed852e454 2119 libpsm2_11.2.68-2.dsc 2a83574887e6202bfe4cd5735c2600571155c1e3 482134 libpsm2_11.2.68.orig.tar.gz b8a35d001b7c6bbd5d8d29b4fe6505feb3eb8784 6968 libpsm2_11.2.68-2.debian.tar.xz 5a2fce639a162ccca2f4e648735640ce078c9134 24624 libpsm2-2-compat-dbgsym_11.2.68-2_amd64.deb dd229c2ff72b46bf0c1ad616b90c4a289f0545c8 6188 libpsm2-2-compat_11.2.68-2_amd64.deb 96a1393d0a31bf271ed5f92552159b2242090011 1198752 libpsm2-2-dbgsym_11.2.68-2_amd64.deb 4723c9d6884f283e0ed5771fc4702ee6dac54529 177092 libpsm2-2_11.2.68-2_amd64.deb 7f22ba5a78ec00bc3fddbe10552677f5ae7d08c7 245684 libpsm2-dev_11.2.68-2_amd64.deb 8b18124405482376329dd0fbf781055465d0be9e 6836 libpsm2_11.2.68-2_amd64.buildinfo Checksums-Sha256: 04f32ee84e276888ad423adebb9f310087da41bffe7c270af3807c5b4d4cba4a 2119 libpsm2_11.2.68-2.dsc 42e16a14fc8c90b50855dcea46af3315bee32fb1ae89d83060f9b2ebdce1ec26 482134 libpsm2_11.2.68.orig.tar.gz 87825f7c52c2c81b8473e4a1b98e03627123275152437f9fa361e860d6f4338e 6968 libpsm2_11.2.68-2.debian.tar.xz 7d89c18c578845e487cd8dda2f41ca9a3fb050b48a77ba1c31afd1a3b7706d46 24624 libpsm2-2-compat-dbgsym_11.2.68-2_amd64.deb
Bug#909442: outguess: patch for #909442
Em qua, 31 de out de 2018 às 06:33, Frédéric Bonnard escreveu: > > Hi Eriberto, > > the errors you see in the builds of 2018-10-29 are the same issues : I > initially tried to reproduce the bug but failed, so I asked a give back. > The new errors you see just occurred during that rebuild but are not > different issues. > So the merge request I sent should fix all the errors on amd64 and power > arches. > > F. Yeap! Thanks. I uploaded to experimental few days ago[1]. [1] https://buildd.debian.org/status/package.php?p=outguess=experimental Now, arm64 fails, so I can't upload to unstable. Do you think that it is a new issue from makefile.unix? Cheers, Eriberto
Processed: affects 912423
Processing commands for cont...@bugs.debian.org: > affects 912423 codelite maitreya Bug #912423 [libwxsqlite3-3.0-0] libwxsqlite3-3.0-0: switch to gtk3 breaks the ABI Added indication that 912423 affects codelite and maitreya > thanks Stopping processing here. Please contact me if you need assistance. -- 912423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908275: marked as done (dbus-test-runner FTBFS with glib 2.58)
Your message dated Fri, 02 Nov 2018 22:04:15 + with message-id and subject line Bug#908275: fixed in dbus-test-runner 16.10.0~bzr100+repack1-4 has caused the Debian Bug report #908275, regarding dbus-test-runner FTBFS with glib 2.58 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.) -- 908275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dbus-test-runner Version: 16.10.0~bzr100+repack1-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dbus-test-runner.html ... bustle.c: In function 'dbus_test_bustle_class_init': bustle.c:61:2: error: 'g_type_class_add_private' is deprecated [-Werror=deprecated-declarations] g_type_class_add_private (klass, sizeof (DbusTestBustlePrivate)); ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from ../libdbustest/task.h:28, from dbus-test.h:29, from bustle.c:26: /usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here void g_type_class_add_private (gpointerg_class, ^~~~ ... --- End Message --- --- Begin Message --- Source: dbus-test-runner Source-Version: 16.10.0~bzr100+repack1-4 We believe that the bug you reported is fixed in the latest version of dbus-test-runner, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated dbus-test-runner 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: Fri, 02 Nov 2018 22:43:17 +0100 Source: dbus-test-runner Binary: dbus-test-runner libdbustest1 libdbustest1-dev Architecture: source Version: 16.10.0~bzr100+repack1-4 Distribution: unstable Urgency: medium Maintainer: Mike Gabriel Changed-By: Mike Gabriel Description: dbus-test-runner - Runs tests under a new DBus session libdbustest1 - Runs tests under a new DBus session (shared library) libdbustest1-dev - Runs tests under a new DBus session (development files) Closes: 908275 Changes: dbus-test-runner (16.10.0~bzr100+repack1-4) unstable; urgency=medium . * debian/control: + Bump Standards-Version: to 4.2.1. No changes needed. * debian/patches: + Add 1002_new-gobject-private-api.patch. Port to newer GObject private ABI. (Closes: #908275). * debian/rules: + Add include line for pkg-info.mk. Checksums-Sha1: 1b85e2f2bde0a66204e487ffb9fbfa2dd2e64509 2416 dbus-test-runner_16.10.0~bzr100+repack1-4.dsc b72af6cf43fedab7b5184925f71c542573b713b7 17852 dbus-test-runner_16.10.0~bzr100+repack1-4.debian.tar.xz 732d16d801e085427949127a0c854b2351b857c7 10039 dbus-test-runner_16.10.0~bzr100+repack1-4_source.buildinfo Checksums-Sha256: 9855941392faad9b5dc5c1be9822e5b833d0d385164a22fcaf12f4a60df4796d 2416 dbus-test-runner_16.10.0~bzr100+repack1-4.dsc c1d1961e5a230fbbcc9e649bd456becdc4074d175d89c76ef2028341e7a4a588 17852 dbus-test-runner_16.10.0~bzr100+repack1-4.debian.tar.xz d344aa43eb2afdbb2ce0b9571bd60c204c9b6e26f984f69e08c9140c1c8d4679 10039 dbus-test-runner_16.10.0~bzr100+repack1-4_source.buildinfo Files: 15da0c896396a3178d81da0a0226861e 2416 devel optional dbus-test-runner_16.10.0~bzr100+repack1-4.dsc c7c944a159135062f184a656c51fd010 17852 devel optional dbus-test-runner_16.10.0~bzr100+repack1-4.debian.tar.xz 8bc1fe775dda8c39c5f1c2c4772ca2fa 10039 devel optional dbus-test-runner_16.10.0~bzr100+repack1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlvcx2wVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxRXYP+K20tMPUkrXcZhCi+EAs1//yDSkF hyNdY04vQKQfvwH03A9Vq7gRkVj7DQOHIsstmEg7f54LRuEx7aIuDwq26tjV5f5f ep7A0cUQ2FWTNyt04KQgVADOewCHnovuVUikwXaBkKrAVzdylQXOpe979SFWI6tJ 8xF8JOCgx9t47Xs/V2GkJxKlgDmsbWQ8xqjhSHtfiE5lL0qSzQQRbVCVOCwCpj62 SoW7vhheCQ7DkZhYO9sRAux3/naGuZG7FD/41aU201xQlg36qkaBzMGq9FfpvBE7
Bug#902755: marked as done (Python 3 version broken, throws exception immediately after connecting)
Your message dated Fri, 02 Nov 2018 22:02:11 +
with message-id
and subject line Bug#902755: fixed in python-imaplib2 2.55-1+deb9u2
has caused the Debian Bug report #902755,
regarding Python 3 version broken, throws exception immediately after connecting
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.)
--
902755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-imaplib2
Version: 2.57-2
Severity: grave
Hi,
Using this test program and Gmail as the IMAP server:
M = imaplib2.IMAP4_SSL(host=IMAP_SERVER, debug=IMAP_DEBUG)
M.login(IMAP_USERNAME, IMAP_PASSWORD)
if (compress):
M.enable_compression()
M.SELECT(mailbox=IMAP_MAILBOX, readonly=True)
M.FETCH('1:10', '(UID FLAGS)')
M.LOGOUT()
...the Python3 version of this package immediately throws an exception
after connecting and thus seems entirely broken:
imaplib2.error: IMAP4 protocol error: program error: -
cannot use a bytes pattern on a string-like object
Even after fixing this, there is an additional issue that shows up only
when enabling compression:
imaplib2.abort: command: EXAMINE => socket error: - a
bytes-like object is required, not 'str'
Note that even stretch's 2.55 presents the latter issue, but not the
former.
The attached patch fixes both of those issues and makes the above simple
test case work, although I haven't tried this any more complicated cases or
with different IMAP servers.
I went to upstream's GitHub in order to see if anyone else had reported
this or to submit a PR, but to my surprise, it seems like upstream's
repository has two different versions of imaplib2, one of them
designated as "py3" and reporting itself as v3.05. That version does not
exhibit any of these two issues above.
Regards,
Faidon
--- x/usr/lib/python3/dist-packages/imaplib2.py 2017-03-05 03:23:58.0 +0200
+++ /usr/lib/python3/dist-packages/imaplib2.py 2018-06-30 15:36:18.645224464 +0300
@@ -302,8 +302,8 @@
# These must be encoded according to utf8 setting in _mode_xxx():
-_literal = br'.*{(?P\d+)}$'
-_untagged_status = br'\* (?P\d+) (?P[A-Z-]+)( (?P.*))?'
+_literal = r'.*{(?P\d+)}$'
+_untagged_status = r'\* (?P\d+) (?P[A-Z-]+)( (?P.*))?'
continuation_cre = re.compile(r'\+( (?P.*))?')
mapCRLF_cre = re.compile(r'\r\n|\r|\n')
@@ -2215,13 +2215,13 @@
"""send(data)
Send 'data' to remote."""
+if bytes != str:
+data = bytes(data, 'utf8')
+
if self.compressor is not None:
data = self.compressor.compress(data)
data += self.compressor.flush(zlib.Z_SYNC_FLUSH)
-if bytes != str:
-data = bytes(data, 'utf8')
-
if hasattr(self.sock, "sendall"):
self.sock.sendall(data)
else:
--- End Message ---
--- Begin Message ---
Source: python-imaplib2
Source-Version: 2.55-1+deb9u2
We believe that the bug you reported is fixed in the latest version of
python-imaplib2, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated python-imaplib2
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, 03 Sep 2018 11:44:48 +0300
Source: python-imaplib2
Binary: python-imaplib2 python3-imaplib2
Architecture: source
Version: 2.55-1+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Ulises Vitulli
Changed-By: Ilias Tsitsimpis
Description:
python-imaplib2 - Threaded Python IMAP4 client
python3-imaplib2 - Threaded Python IMAP4 client (Python 3)
Closes: 899102 902755
Changes:
python-imaplib2 (2.55-1+deb9u2) stretch; urgency=medium
.
* Install the correct module for Python 3.
Until now, python3-imaplib2 installed the Python 2 version of this module.
Thanks to Faidon Liambotis for reporting this (Closes: 902755)
* Apply patch to remove TIMEOUT_MAX variable.
On some architectures, using threading.TIMEOUT_MAX for the timeout
parameter can overflow causing Condition.wait() to return immediately.
Bug#864800: marked as done (Mail::DeliveryStatus::BounceParser contains a live virus and some real spam/phishing mails)
Your message dated Fri, 02 Nov 2018 22:02:09 + with message-id and subject line Bug#864800: fixed in libmail-deliverystatus-bounceparser-perl 1.542+repacked-1~deb9u1 has caused the Debian Bug report #864800, regarding Mail::DeliveryStatus::BounceParser contains a live virus and some real spam/phishing mails 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.) -- 864800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmail-deliverystatus-bounceparser-perl Version: 1.531-1 Severity: serious X-Debbugs-CC: Ricardo Signes Control: forwarded -1 Ricardo Signes Control: found -1 1.536-1 Control: found -1 1.542-1 User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team The Mail::DeliveryStatus::BounceParser source contains a live virus and some real spam/phishing mails. This is leading to Netcraft and other virus detection systems on the Internet reporting Debian mirrors as malicious, which potentially reduces the reputation of debian.org on various anti-spam and anti-malware services. Please fix this in upstream git, with a new release on CPAN and in all Debian suites. https://incident.netcraft.com/w/b0d11ab53944/ https://incident.netcraft.com/w/ffb6f95e5301/ To fix this you will need to strip the account-password.zip attachment from t/corpus/virus-caused-multiple-weird-reports.msg and if possible strip the phishing/spam content from the other files, while ensuring that the tests still pass despite changes to the corpus but that the new files in the corpus do not trip any anti-virus checkers: https://www.virustotal.com/ $ clamdscan --fdpass --infected | sed "s|`pwd`/||" t/corpus/virus-caused-multiple-weird-reports.msg: Win.Worm.Mytob-331 FOUND t/corpus/spam-with-badly-parsed-email.msg: Sanesecurity.Phishing.Ivt.6456.UNOFFICIAL FOUND t/corpus/spam-lots-of-bogus-addresses.msg: Sanesecurity.Spam.8684.UNOFFICIAL FOUND --- SCAN SUMMARY --- Infected files: 3 Time: 0.087 sec (0 m 0 s) -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libmail-deliverystatus-bounceparser-perl Source-Version: 1.542+repacked-1~deb9u1 We believe that the bug you reported is fixed in the latest version of libmail-deliverystatus-bounceparser-perl, 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 864...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated libmail-deliverystatus-bounceparser-perl 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, 08 Oct 2018 06:57:36 +0200 Source: libmail-deliverystatus-bounceparser-perl Binary: libmail-deliverystatus-bounceparser-perl Architecture: source all Version: 1.542+repacked-1~deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian Perl Group Changed-By: Xavier Guimard Description: libmail-deliverystatus-bounceparser-perl - module for analyzing bounce messages Closes: 864800 Changes: libmail-deliverystatus-bounceparser-perl (1.542+repacked-1~deb9u1) stretch; urgency=medium . * Team upload * Repack excluding viruses found by uscan (Closes: #864800) Checksums-Sha1: 605b58219ffcb0e7740adffb4e81c1a85e3e117d 2611 libmail-deliverystatus-bounceparser-perl_1.542+repacked-1~deb9u1.dsc 51a846124bd138510f11c05b493625c100db7f57 134689 libmail-deliverystatus-bounceparser-perl_1.542+repacked.orig.tar.gz 82429dbc1e3605938f4eb54d5e215ace1b2212cc 2952 libmail-deliverystatus-bounceparser-perl_1.542+repacked-1~deb9u1.debian.tar.xz adb2aced2e8c8306d60f661d8379102c39f06036 24790 libmail-deliverystatus-bounceparser-perl_1.542+repacked-1~deb9u1_all.deb 743cb118d4b7bc83df2893acd6496432f3e379ee 6493 libmail-deliverystatus-bounceparser-perl_1.542+repacked-1~deb9u1_amd64.buildinfo Checksums-Sha256: a78387376fef70a82a80fb679caee20e8ac143a03f89218642ee0e1eca202297 2611 libmail-deliverystatus-bounceparser-perl_1.542+repacked-1~deb9u1.dsc d24c5032ca6caf9fdd42b93747280e02f8bb2b212b9be32e54e2e6d2d2fb2b90 134689
Bug#912695: apt-show-versions: breaks "apt-get update" and uninstallable after Perl 5.28 upgrade
Package: apt-show-versions Version: apt-show-versions Severity: critical Justification: breaks unrelated software Dear Maintainer, after the Perl 5.28 upgrade, if apt-show-versions (0.22.8) is installed, "apt- get update" fails with: # apt-get update Hit:1 https://repo.skype.com/deb stable InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://ftp.debian.org/debian sid InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux- gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'test -x /usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i' E: Sub-process returned an error code The error can be reproduced by running: # apt-show-versions -i Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux- gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. Workaround is to uninstall apt-show-versions with: apt-get purge apt-show-versions Following this removal, "apt-get update" works normally. Attempting to reinstall apt-show-versions fails with: # apt-get install apt-show-versions Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: apt-show-versions 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 32.1 kB of archives. After this operation, 93.2 kB of additional disk space will be used. Get:1 http://ftp.debian.org/debian sid/main amd64 apt-show-versions all 0.22.8 [32.1 kB] Fetched 32.1 kB in 3s (10.2 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package apt-show-versions. (Reading database ... 257503 files and directories currently installed.) Preparing to unpack .../apt-show-versions_0.22.8_all.deb ... Unpacking apt-show-versions (0.22.8) ... Setting up apt-show-versions (0.22.8) ... ** initializing cache. This may take a while ** Max. recursion depth with nested structures exceeded at /usr/lib/x86_64-linux- gnu/perl/5.28/Storable.pm line 278, at /usr/bin/apt-show-versions line 271. dpkg: error processing package apt-show-versions (--configure): installed apt-show-versions package post-installation script subprocess returned error exit status 25 Processing triggers for man-db (2.8.4-2+b1) ... Errors were encountered while processing: apt-show-versions E: Sub-process /usr/bin/dpkg returned an error code (1) Clean up with: apt-get purge apt-show-versions Kind regards, Ben. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-show-versions depends on: ii apt 1.7.0 ii libapt-pkg-perl 0.1.34+b1 ii perl [libstorable-perl] 5.28.0-3 apt-show-versions recommends no packages.
Bug#912423: codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Control: reassign -1 libwxsqlite3-3.0-0 3.4.1~dfsg-2 Control: tags -1 - confirmed Control: retitle -1 libwxsqlite3-3.0-0: switch to gtk3 breaks the ABI Control: affects -1 src:codelite src:maitreya Hi, On 31/10/2018 13:15, James Cowgill wrote: > Control: severity -1 grave > Control: tags -1 confirmed > Control: retitle -1 codelite: fails to start: GTK+ 2.x symbols detected. > Using GTK+ 2.x and GTK+ 3 in the same process is not supported > > Hi, > > On 31/10/2018 11:50, Larus wrote: >> Package: codelite >> Version: 10.0+dfsg-3 >> Severity: important >> >> Dear Maintainer, >> when starting codelite the process shuts down directly when starting. >> Reason: >> (codelite:1081): Gtk-ERROR **: 12:48:04.992: GTK+ 2.x symbols detected. >> Using GTK+ 2.x and GTK+ 3 in the same process is not supported >> Sadly I haven't been able to resolve this. > > Indeed I cannot start codelite in unstable either. As well as the above, > I also get a lot of other errors when trying to run it (below). This was caused by wxsqlite3 switching to GTK+3. This comes into conflict with codelite which is built against GTK+2. As the error above states, you cannot load the GTK+2 and GTK+3 libraries into the same process. This change is pretty much guaranteed to break all reverse dependencies of wxsqlite3 (because any existing rdep must have been compiled against GTK+2 to function). I think it makes most sense to handle this like a normal package transition and either rename the package, or add extra packages (like wxwidgets3.0 did). If you don't do that, you'll need to add a Breaks for all your rdeps (but this won't help if any user programs outside Debian link against wxsqlite). In theory, codelite does support building against GTK+3, but I haven't tried it. The other rdep is maitreya which doesn't link against any GTK+ version directly, so in theory changing the build dependencies to the GTK+3 versions should "Just Work" :) This means you can probably get away with a rename instead of adding extra packages. It's unfortunate this took a month to discover. I guess there's not many people using these packages :/ James signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#912423: codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Processing control commands: > reassign -1 libwxsqlite3-3.0-0 3.4.1~dfsg-2 Bug #912423 [codelite] codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Bug reassigned from package 'codelite' to 'libwxsqlite3-3.0-0'. No longer marked as found in versions codelite/10.0+dfsg-3. Ignoring request to alter fixed versions of bug #912423 to the same values previously set Bug #912423 [libwxsqlite3-3.0-0] codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Marked as found in versions wxsqlite3/3.4.1~dfsg-2. > tags -1 - confirmed Bug #912423 [libwxsqlite3-3.0-0] codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Removed tag(s) confirmed. > retitle -1 libwxsqlite3-3.0-0: switch to gtk3 breaks the ABI Bug #912423 [libwxsqlite3-3.0-0] codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Changed Bug title to 'libwxsqlite3-3.0-0: switch to gtk3 breaks the ABI' from 'codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported'. > affects -1 src:codelite src:maitreya Bug #912423 [libwxsqlite3-3.0-0] libwxsqlite3-3.0-0: switch to gtk3 breaks the ABI Added indication that 912423 affects src:codelite and src:maitreya -- 912423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 912187 in 20170929
Processing commands for cont...@bugs.debian.org: > fixed 912187 20170929 Bug #912187 [ca-certificates-java] Wrong jvm options for armhf Marked as fixed in versions ca-certificates-java/20170929. > thanks Stopping processing here. Please contact me if you need assistance. -- 912187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912685: debian/rules is not binNMU safe
Source: net-snmp Version: 5.7.3+dfsg-4 Severity: serious Hi, In debian/rules you have the following: UPSTREAM_VERSION = $(shell dpkg-parsechangelog | egrep '^Version:' | cut -f 2 -d ':' | sed 's/ //' | sed 's/~dfsg.*$$//') COMPAT_VERSION = $(UPSTREAM_VERSION)~dfsg [...] override_dh_makeshlibs: dh_makeshlibs -plibsnmp$(LIB_VERSION) -V"libsnmp$(LIB_VERSION) (>= $(COMPAT_VERSION))" When a binNMU is scheduled, UPSTREAM_VERSION is set to 5.7.3+dfsg-4+b1 and then COMPAT_VERSION is set to 5.7.3+dfsg-4+b1~dfsg which is completely boggus All the reverse-dependency will have this boggus version in their generated dependency list. Why aren't you using "dh_makeshlibs -V" or the version macro that are present in /usr/share/dpkg/pkg-info.mk ? Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#912684: perl-modules-5.28 needs versioned Provides for modules it bundles
Package: perl-modules-5.28 Version: 5.28.0-3 Severity: serious perl-modules-5.28 has Replaces+Breaks: libextutils-parsexs-perl (<< 3.39) This makes libextutils-parsexs-perl in unstable not installable. libextutils-parsexs-perl does have reverse dependencies in unstable, including revers dependencies with versioned dependencies. Versioned Provides for such modules are required.
Bug#912682: libextutils-parsexs-perl: version is older than Replaces+Breaks in perl-modules-5.28
Package: libextutils-parsexs-perl Version: 3.35-1 Severity: serious The following packages have unmet dependencies: perl-modules-5.28 : Breaks: libextutils-parsexs-perl (< 3.39)
Bug#911697: at-spi2-core: causes SIGSEGV because of improper quoting of G_LOG_DOMAIN
Hello, Jussi Pakkanen, le ven. 02 nov. 2018 21:38:01 +0200, a ecrit: > On Wed, Oct 24, 2018 at 10:32 AM Samuel Thibault wrote: > > > So the issue is in meson itself: it seems one can't get > > > > compile_args: [ '-DG_LOG_DOMAIN="dbind"' ], > > > > to be correctly interpreted as making G_LOG_DOMAIN #defined to "dbind" > > both for the binary compilation and for the documentation generation. > > > > FTR, this was working with meson 0.47.2-1 (see > > https://buildd.debian.org/status/fetch.php?pkg=at-spi2-core=amd64=2.30.0-2=1536983011=0 > > ), so I guess it's 0.48.0 which broke this. > > Can you test if the commit mentioned in > https://github.com/mesonbuild/meson/issues/4452#issuecomment-434870441 > fixes the issue for you? > > Simply running your build with current Meson trunk is enough to test the > issue. I simply applied the patch on top of my 0.48.1-1 package, and it fixed the documentation build without breaking the binary indeed. Samuel
Bug#910128: bash-completion: diff for NMU version 1:2.8-1.1
On 02 Nov 2018, Gabriel F. T. Gomes wrote: >On 28 Oct 2018, Emmanouil Kampitakis wrote: > >>I've prepared an NMU for bash-completion (versioned as 1:2.8-1.1) and >>uploaded it to DELAYED/5. Please feel free to tell me if I >>should delay it longer. > >Thanks for doing this, and sorry for taking too long to act. I'll >incorporate your changes into the git repository [1]. Once it's >integrated, I'll let you know. Now in the git repository (notice that I will *not* upload a new version to Debian... this is just to let you know that your NMU has been incorporated and that it will keep its intended effect when I upload a new version): https://salsa.debian.org/debian/bash-completion/commit/32b4dc89e47bd20920ea84929d445d0f0812706c
Bug#912346: marked as done (starjava-votable FTBFS with OpenJDK 11)
Your message dated Fri, 02 Nov 2018 19:39:44 + with message-id and subject line Bug#912346: fixed in starjava-votable 2.0+2018.10.31-1 has caused the Debian Bug report #912346, regarding starjava-votable FTBFS with OpenJDK 11 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.) -- 912346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: starjava-votable Version: 2.0+2018.05.01-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/starjava-votable.html ... run-tests: [junit] Testsuite: uk.ac.starlink.votable.CoosysTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.71 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.DOMTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.206 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.FitsPlusTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.547 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.LinkTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.379 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.MultiTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.842 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.ParameterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.231 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.ReferenceTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.324 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.SerializerTest [junit] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.752 sec [junit] [junit] Testcase: testURLs(uk.ac.starlink.votable.SerializerTest): Caused an ERROR [junit] Can't overwrite cause with java.io.FileNotFoundException: stest10126905822765568439.dat (No such file or directory) [junit] java.lang.IllegalStateException: Can't overwrite cause with java.io.FileNotFoundException: stest10126905822765568439.dat (No such file or directory) [junit] at java.base/java.lang.Throwable.initCause(Throwable.java:462) [junit] at uk.ac.starlink.votable.VOTableDOMBuilder$Worker.processFitsHref(VOTableDOMBuilder.java:156) [junit] at uk.ac.starlink.votable.SkeletonDOMBuilder$BasicContentHandler.startElement(SkeletonDOMBuilder.java:192) [junit] at uk.ac.starlink.votable.CustomDOMBuilder.startElement(CustomDOMBuilder.java:157) [junit] at uk.ac.starlink.votable.VOTableDOMBuilder.startElement(VOTableDOMBuilder.java:79) [junit] at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:510) [junit] at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:183) [junit] at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1377) [junit] at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2708) [junit] at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:605) [junit] at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:534) [junit] at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:888) [junit] at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824) [junit] at java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) [junit] at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1216) [junit] at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:635) [junit] at uk.ac.starlink.votable.VOElementFactory.parseToDOM(VOElementFactory.java:536) [junit] at uk.ac.starlink.votable.VOElementFactory.transformToDOM(VOElementFactory.java:391) [junit] at uk.ac.starlink.votable.VOElementFactory.makeVOElement(VOElementFactory.java:221) [junit] at
Processed: sane-backends: diff for NMU version 1.0.27-3.1
Processing control commands: > tags 908681 + patch Bug #908681 [libsane1] libsane1: pointless package rename Added tag(s) patch. > tags 908681 + pending Bug #908681 [libsane1] libsane1: pointless package rename Added tag(s) pending. -- 908681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911697: at-spi2-core: causes SIGSEGV because of improper quoting of G_LOG_DOMAIN
On Wed, Oct 24, 2018 at 10:32 AM Samuel Thibault wrote: > So the issue is in meson itself: it seems one can't get > > compile_args: [ '-DG_LOG_DOMAIN="dbind"' ], > > to be correctly interpreted as making G_LOG_DOMAIN #defined to "dbind" > both for the binary compilation and for the documentation generation. > > FTR, this was working with meson 0.47.2-1 (see > https://buildd.debian.org/status/fetch.php?pkg=at-spi2-core=amd64=2.30.0-2=1536983011=0 > ), so I guess it's 0.48.0 which broke this. Can you test if the commit mentioned in https://github.com/mesonbuild/meson/issues/4452#issuecomment-434870441 fixes the issue for you? Simply running your build with current Meson trunk is enough to test the issue. Thanks,
Bug#908681: sane-backends: diff for NMU version 1.0.27-3.1
Control: tags 908681 + patch Control: tags 908681 + pending Dear maintainer, I've prepared an NMU for sane-backends (versioned as 1.0.27-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. The diff is too big to be included here, diffstat bellow: $ debdiff sane-backends_1.0.27-3.dsc sane-backends_1.0.27-3.1.dsc|diffstat TROUBLESHOOTING.Debian |4 changelog |8 control | 10 libsane.NEWS| 19 libsane.README.Debian | 172 libsane.dirs|1 libsane.docs|1 libsane.install |2 libsane.postinst| 24 libsane.symbols.alpha | 7314 +++ libsane.symbols.amd64 | 7363 libsane.symbols.arm64 | 7257 +++ libsane.symbols.armel | 7314 +++ libsane.symbols.armhf | 7314 +++ libsane.symbols.hppa| 7257 +++ libsane.symbols.i386| 7314 +++ libsane.symbols.kfreebsd-amd64 | 7361 +++ libsane.symbols.kfreebsd-i386 | 7361 +++ libsane.symbols.m68k| 7257 +++ libsane.symbols.mips| 7257 +++ libsane.symbols.mips64el| 7257 +++ libsane.symbols.mipsel | 7257 +++ libsane.symbols.powerpc | 7257 +++ libsane.symbols.powerpcspe | 7257 +++ libsane.symbols.ppc64 | 7257 +++ libsane.symbols.ppc64el | 7257 +++ libsane.symbols.s390x | 7257 +++ libsane.symbols.sh4 | 7257 +++ libsane.symbols.sparc64 | 7257 +++ libsane.symbols.x32 | 7314 +++ libsane1.NEWS | 19 libsane1.README.Debian | 172 libsane1.dirs |1 libsane1.docs |1 libsane1.install|2 libsane1.postinst | 24 libsane1.symbols.alpha | 7314 --- libsane1.symbols.amd64 | 7363 libsane1.symbols.arm64 | 7257 --- libsane1.symbols.armel | 7314 --- libsane1.symbols.armhf | 7314 --- libsane1.symbols.hppa | 7257 --- libsane1.symbols.i386 | 7314 --- libsane1.symbols.kfreebsd-amd64 | 7361 --- libsane1.symbols.kfreebsd-i386 | 7361 --- libsane1.symbols.m68k | 7257 --- libsane1.symbols.mips | 7257 --- libsane1.symbols.mips64el | 7257 --- libsane1.symbols.mipsel | 7257 --- libsane1.symbols.powerpc| 7257 --- libsane1.symbols.powerpcspe | 7257 --- libsane1.symbols.ppc64 | 7257 --- libsane1.symbols.ppc64el| 7257 --- libsane1.symbols.s390x | 7257 --- libsane1.symbols.sh4| 7257 --- libsane1.symbols.sparc64| 7257 --- libsane1.symbols.x32| 7314 --- rules |8 58 files changed, 153234 insertions(+), 153226 deletions(-) The source package will be available in https://ftp-master.debian.org/deferred/ Regards.
Bug#912371: marked as done (java-common breaks starjava-votable autopkgtest)
Your message dated Fri, 02 Nov 2018 19:39:44 + with message-id and subject line Bug#912346: fixed in starjava-votable 2.0+2018.10.31-1 has caused the Debian Bug report #912346, regarding java-common breaks starjava-votable autopkgtest 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.) -- 912346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: java-common, starjava-votable Control: found -1 java-common/0.70 Control: found -1 starjava-votable/2.0+2018.05.01-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of java-common the autopkgtest of starjava-votable fails in testing when that autopkgtest is run with the binary packages of java-common from unstable. It passes when run with only packages from testing. In tabular form: passfail java-commonfrom testing0.70 starjava-votable from testing2.0+2018.05.01-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration of java-common to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=java-common https://ci.debian.net/data/autopkgtest/testing/amd64/s/starjava-votable/1225607/log.gz autopkgtest [18:58:51]: test command1: ant test -Dbuild.dir=$ADTTMP -Drunonly.install=true -Djunit.present=true -Djava.awt.headless=true autopkgtest [18:58:51]: test command1: [--- Buildfile: /tmp/autopkgtest-lxc.rb2iyjjs/downtmp/build.CnE/src/build.xml prepare: check_packages: build: compile-tests: [mkdir] Created dir: /tmp/autopkgtest-lxc.rb2iyjjs/downtmp/autopkgtest_tmp/testcases [javac] Compiling 17 source files to /tmp/autopkgtest-lxc.rb2iyjjs/downtmp/autopkgtest_tmp/testcases [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. run-tests: [junit] Testsuite: uk.ac.starlink.votable.CoosysTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.857 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.DOMTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.654 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.FitsPlusTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.849 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.LinkTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.67 sec [junit] [junit] - Standard Error - [junit] Oct 30, 2018 6:59:00 PM uk.ac.starlink.table.storage.AdaptiveByteStore getDefaultLimit [junit] INFO: AdaptiveByteStore default memory limit = 1872M * 0.125 = 234M [junit] - --- [junit] Testsuite: uk.ac.starlink.votable.MultiTest [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.998 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.ParameterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.31 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.ReferenceTest [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.38 sec [junit] [junit] Testsuite: uk.ac.starlink.votable.SerializerTest [junit] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.15 sec [junit] [junit] - Standard Error - [junit] Oct 30, 2018 6:59:04 PM uk.ac.starlink.fits.InputFactory createFileFactory [junit] INFO: Will map as single block: stest10223147168984043305.dat [junit] Oct 30, 2018 6:59:04 PM uk.ac.starlink.fits.SimpleMappedInput [junit] INFO: Mapping as single file: stest10223147168984043305.dat [junit] Oct 30, 2018 6:59:04 PM uk.ac.starlink.fits.InputFactory createFileFactory [junit]
Processed: libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config
Processing control commands: > affects -1 + src:gem Bug #912679 [libmagickcore-6.q16-dev] libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config Added indication that 912679 affects src:gem -- 912679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912679: libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config
Package: libmagickcore-6.q16-dev Version: 8:6.9.10.14+dfsg-5 Severity: serious Justification: missing dependency Control: affects -1 + src:gem libmagickcore-6.q16-dev does not depend on libmagickcore-6-arch-config. It does depend on libmagickcore-6-headers, which depends on libmagickcore-6-arch-config, but libmagickcore-6-headers is Multi-Arch: foreign. So you get some libmagickcore-6-arch-config and not necessarily one with matching architecture. The dependency is too weak. When building gem, this can become fatal: | /bin/bash ../../libtool --tag=CXX --mode=compile aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME='""Debian/1:0.93.3-18""' -DPD -I/usr/include/pd -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -c -o gem_imageMAGICK_la-imageMAGICK.lo `test -f 'imageMAGICK.cpp' || echo './'`imageMAGICK.cpp | libtool: compile: aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME=\"\"Debian/1:0.93.3-18\"\" -DPD -I/usr/include/pd -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -c imageMAGICK.cpp -fPIC -DPIC -o .libs/gem_imageMAGICK_la-imageMAGICK.o | In file included from /usr/include/ImageMagick-6/Magick++/Include.h:14, | from /usr/include/ImageMagick-6/Magick++.h:10, | from imageMAGICK.cpp:21: | /usr/include/ImageMagick-6/magick/magick-config.h:21:10: fatal error: magick/magick-baseconfig.h: No such file or directory | #include "magick/magick-baseconfig.h" | ^~~~ | compilation terminated. | make[3]: *** [Makefile:613: gem_imageMAGICK_la-imageMAGICK.lo] Error 1 | make[3]: Leaving directory '/<>/plugins/imageMAGICK' | make[2]: *** [Makefile:489: all-recursive] Error 1 | make[2]: Leaving directory '/<>/plugins' | make[1]: *** [Makefile:598: all-recursive] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: make -j1 returned exit code 2 | make: *** [debian/rules:82: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The dependency from libmagickcore-6-headers on libmagickcore-6-arch-config should be removed. It is always too week and needs to be lifted to a higher level. What can be done though is flipping the dependency. Have libmagickcore-6-arch-config depend on libmagickcore-6-headers and then replace any dependency on libmagickcore-6-headers with one on libmagickcore-6-arch-config. That should be fine, because both packages are considered implementation detail and do not have any reverse dependencies outside imagemagick. Helmut
Bug#912547: Bug #912547 in libpicocontainer-java marked as pending
Control: tag -1 pending Hello, Bug #912547 in libpicocontainer-java 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/libpicocontainer-java/commit/cb3ccefa4de6424edb69c46873f01983618215dd Fix FTBFS with OpenJDK 11 by depending on libactivation-java. Closes: #912547 (this message was generated automatically) -- Greetings https://bugs.debian.org/912547
Processed: Bug #912547 in libpicocontainer-java marked as pending
Processing control commands: > tag -1 pending Bug #912547 [src:libpicocontainer-java] libpicocontainer-java: FTBFS with Java 11 due to javax.annotation removal Added tag(s) pending. -- 912547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 912633
Processing commands for cont...@bugs.debian.org: > tags 912633 + buster sid Bug #912633 [courier-imap] courier-imap-ssl: No supported cipher suite with the recent switch to TLS 1.3 in OpenSSL 1.1.1. Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 912633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912599: [Pkg-nagios-devel] Bug#912599: icinga2-common: incinga2-common fails to install cleanly (hidden dep on icinga2)
On 11/2/18 6:58 PM, Lee Garrett wrote: > On 01/11/2018 20:15, Sebastiaan Couwenberg wrote:> Hi Lee, >> >> On 11/1/18 6:41 PM, Lee Garrett wrote: >>> installing icinga2-common on a system that does not have icinga2 installed >>> fails as follows: >>> >>> [...] >>> >>> Installing icinga2 directly, which pulls in icinga2-common, makes the >>> installation go through cleanly. >> >> Installing icinga2-common by itself makes no sense. > > I agree, though there might be corner cases where this might happen, like > during dist-upgrade. That's something piuparts would have found, and it didn't run into this issue. >>> Besides the policy violation it makes it hard to install icinga2 with the >>> chef >>> cookbook at https://supermarket.chef.io/cookbooks/icinga2, as it installs >>> every >>> package after each other (with a version number restriction). >> >> I have no sympathy for broken configuration management. The cookbook not >> working is something you need take up with its developer. > > Indeed, they unfortunately happen to be the cookbooks provided by upstream. > > Thanks for the quick fix! Note that only the version in unstable was fixed. The issue doesn't seem widespread enough to warrant a stable update. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#910128: bash-completion: diff for NMU version 1:2.8-1.1
Hi, Emmanouil, On 28 Oct 2018, Emmanouil Kampitakis wrote: >I've prepared an NMU for bash-completion (versioned as 1:2.8-1.1) and >uploaded it to DELAYED/5. Please feel free to tell me if I >should delay it longer. > >Previous diff was against stable. Attached diff is agains sid Thanks for doing this, and sorry for taking too long to act. I'll incorporate your changes into the git repository [1]. Once it's integrated, I'll let you know. [1] https://salsa.debian.org/debian/bash-completion/commits/master
Bug#912599: [Pkg-nagios-devel] Bug#912599: icinga2-common: incinga2-common fails to install cleanly (hidden dep on icinga2)
Hi Sebastiaan, On 01/11/2018 20:15, Sebastiaan Couwenberg wrote:> Hi Lee, > > On 11/1/18 6:41 PM, Lee Garrett wrote: >> installing icinga2-common on a system that does not have icinga2 installed fails >> as follows: >> >> [...] >> >> Installing icinga2 directly, which pulls in icinga2-common, makes the >> installation go through cleanly. > > Installing icinga2-common by itself makes no sense. I agree, though there might be corner cases where this might happen, like during dist-upgrade. > >> Besides the policy violation it makes it hard to install icinga2 with the >> chef >> cookbook at https://supermarket.chef.io/cookbooks/icinga2, as it installs >> every >> package after each other (with a version number restriction). > I have no sympathy for broken configuration management. The cookbook not > working is something you need take up with its developer. Indeed, they unfortunately happen to be the cookbooks provided by upstream. Thanks for the quick fix! Regards, Lee
Bug#912384: marked as done (obantoo: FTBFS with Java 11 due to JAXB removal)
Your message dated Fri, 02 Nov 2018 17:57:57 + with message-id and subject line Bug#912384: fixed in obantoo 2.1.12+ds1-2 has caused the Debian Bug report #912384, regarding obantoo: FTBFS with Java 11 due to JAXB removal 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.) -- 912384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: obantoo Version: 2.1.12+ds1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/obantoo.html ... compile: [mkdir] Created dir: /build/1st/obantoo-2.1.12+ds1/build/bin [javac] Compiling 154 source files to /build/1st/obantoo-2.1.12+ds1/build/bin [javac] warning: [options] bootstrap class path not set in conjunction with -source 6 [javac] warning: [options] source value 6 is obsolete and will be removed in a future release [javac] warning: [options] target value 1.6 is obsolete and will be removed in a future release [javac] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options. [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/JUnit/TestUeberweisung.java:19: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.JAXBException; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:13: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.JAXBContext; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:14: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.JAXBException; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:15: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.Marshaller; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:16: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.Unmarshaller; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:208: error: cannot find symbol [javac] SEPAException, JAXBException [javac] ^ [javac] symbol: class JAXBException [javac] location: class Basislastschrift [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Basislastschrift/Basislastschrift.java:250: error: cannot find symbol [javac] public void read(File file) throws JAXBException, SEPAException [javac] ^ [javac] symbol: class JAXBException [javac] location: class Basislastschrift [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:13: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlAccessType; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:14: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlAccessorType; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:15: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlElement; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:16: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlType; [javac] ^ [javac] /build/1st/obantoo-2.1.12+ds1/src/de/jost_net/OBanToo/SEPA/Nachricht/pain_008_002_02/CustomerDirectDebitInitiationV02.java:39: error: cannot find symbol [javac] @XmlAccessorType(XmlAccessType.FIELD) [javac] ^ [javac] symbol: class XmlAccessorType [javac]
Bug#912543: marked as done (libnetx-java: FTBFS with Java 11 due to SecurityManager.checkTopLevelWindow() removal)
Your message dated Fri, 02 Nov 2018 17:55:46 +
with message-id
and subject line Bug#912543: fixed in libnetx-java 0.5-4
has caused the Debian Bug report #912543,
regarding libnetx-java: FTBFS with Java 11 due to
SecurityManager.checkTopLevelWindow() removal
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.)
--
912543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnetx-java
Version: 0.5-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnetx-java.html
...
compile:
[mkdir] Created dir: /build/1st/libnetx-java-0.5/classes
[javac] /build/1st/libnetx-java-0.5/build.xml:20: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[javac] Compiling 70 source files to /build/1st/libnetx-java-0.5/classes
[javac]
/build/1st/libnetx-java-0.5/src/netx/jnlp/runtime/JNLPClassLoader.java:633:
warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public String getExtensionName() {
[javac] ^
[javac]
/build/1st/libnetx-java-0.5/src/netx/jnlp/runtime/JNLPClassLoader.java:649:
warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public String getExtensionHREF() {
[javac] ^
[javac]
/build/1st/libnetx-java-0.5/src/netx/jnlp/runtime/JNLPSecurityManager.java:297:
error: cannot find symbol
[javac] return super.checkTopLevelWindow(window);
[javac] ^
[javac] symbol: method checkTopLevelWindow(Object)
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 2 warnings
--- End Message ---
--- Begin Message ---
Source: libnetx-java
Source-Version: 0.5-4
We believe that the bug you reported is fixed in the latest version of
libnetx-java, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated libnetx-java 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: Fri, 02 Nov 2018 18:18:04 +0100
Source: libnetx-java
Binary: libnetx-java
Architecture: source
Version: 0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Description:
libnetx-java - An open-source JNLP client
Closes: 912543
Changes:
libnetx-java (0.5-4) unstable; urgency=medium
.
* Team upload.
* Fixed the build failure with Java 11 (Closes: #912543)
* Standards-Version updated to 4.2.1
* Switch to debhelper level 11
* Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
193c6f30218f3f1b0b43de2db9773f27d3df25d5 2013 libnetx-java_0.5-4.dsc
62c7f560361084a27b390bb6fed3910e3384a060 4420 libnetx-java_0.5-4.debian.tar.xz
4d0664866b06f250d29df3e15c7098b565a81a15 10432
libnetx-java_0.5-4_source.buildinfo
Checksums-Sha256:
f9d8aa8d639cdae2cb18d12ccf1b6fc7c1aa17b76b08c0c47aef125808c860c7 2013
libnetx-java_0.5-4.dsc
186a5b02c47da2848b48b4535e39533fd29cab2b2e75d7b48dc6bc7d7283abe4 4420
libnetx-java_0.5-4.debian.tar.xz
9c4c18ffd1c37558e5c7cb669d35ef61571c9d324f531314936a590b36c7a971 10432
libnetx-java_0.5-4_source.buildinfo
Files:
a29d0ad5cfb3950e67bae00cb167 2013 java optional libnetx-java_0.5-4.dsc
9a59018a0c4dc9ff1e0a3e9183386bd9 4420 java optional
libnetx-java_0.5-4.debian.tar.xz
42d678c7b05cd0759d000f82c948663a 10432 java optional
libnetx-java_0.5-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlvch6ISHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsbfEP/ji7An7ak1rQq8qVDWJQL9A7uWi31G26
C2bRngEpq5VYauaJFIJBtOgRB195Cp83MgpWHzGX6g1xqEAJFIgF8DR8k0NVGojs
Xr2FqI1KSIDZYkt5SLcRioewEC0u1V3TgRwe8kB/JrNn+huMbCg190TCMzJzfotZ
Bug#912539: marked as done (libjdom1-java: FTBFS with Java 11 due to CORBA removal)
Your message dated Fri, 02 Nov 2018 17:55:21 + with message-id and subject line Bug#912539: fixed in libjdom1-java 1.1.3-2 has caused the Debian Bug report #912539, regarding libjdom1-java: FTBFS with Java 11 due to CORBA removal 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.) -- 912539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjdom1-java Version: 1.1.3-1 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjdom1-java.html ... compile: [javac] /build/1st/libjdom1-java-1.1.3/test/build.xml:205: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Using javac -source 1.4 is no longer supported, switching to 6 [javac] Using javac -target 1.4 is no longer supported, switching to 6 [javac] Compiling 26 source files to /build/1st/libjdom1-java-1.1.3/test/build/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 6 [javac] warning: [options] source value 6 is obsolete and will be removed in a future release [javac] warning: [options] target value 1.6 is obsolete and will be removed in a future release [javac] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options. [javac] /build/1st/libjdom1-java-1.1.3/test/build/src/org/jdom/test/cases/TestElement.java:71: error: package org.omg.PortableInterceptor does not exist [javac] import org.omg.PortableInterceptor.SUCCESSFUL; [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 error [javac] 4 warnings BUILD FAILED /build/1st/libjdom1-java-1.1.3/build.xml:21: The following error occurred while executing this line: /build/1st/libjdom1-java-1.1.3/test/build.xml:205: Compile failed; see the compiler error output for details. Total time: 11 seconds make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1 --- End Message --- --- Begin Message --- Source: libjdom1-java Source-Version: 1.1.3-2 We believe that the bug you reported is fixed in the latest version of libjdom1-java, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated libjdom1-java 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: Fri, 02 Nov 2018 17:38:16 +0100 Source: libjdom1-java Binary: libjdom1-java libjdom1-java-doc Architecture: source Version: 1.1.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libjdom1-java - lightweight and fast library using XML libjdom1-java-doc - lightweight and fast library using XML - documentation Closes: 889351 912539 Changes: libjdom1-java (1.1.3-2) unstable; urgency=medium . * Fixed the build failure with Java 11 (Closes: #912539) * Removed Damien Raude-Morvan from the uploaders (Closes: #889351) * Standards-Version updated to 4.2.1 * Switch to debhelper level 11 Checksums-Sha1: 777f6a5004af1b0fe73b6ccb2b82c858c72684de 2226 libjdom1-java_1.1.3-2.dsc 2a6e4e35e7986f4ed5b52116d48ee136ddccb25e 6956 libjdom1-java_1.1.3-2.debian.tar.xz 623679d57aed79b9dca811398d83fada4302805a 12994 libjdom1-java_1.1.3-2_source.buildinfo Checksums-Sha256: 4e58286a620fe569fa89b96a24a16cb42768858c3cfde38d1e29bc95910c63f7 2226 libjdom1-java_1.1.3-2.dsc 114764e8d7f525becc545b20f8cfa0b6904f5fc27a487a495b7ea28e57d1a6d4 6956 libjdom1-java_1.1.3-2.debian.tar.xz 3b39d3c6d8e64ba68c6153213ca60214e38ff09efa2788ae1e459289e8ae1ce3 12994 libjdom1-java_1.1.3-2_source.buildinfo Files: cee258f99f8114f63962f8f45853d6d9 2226 java optional libjdom1-java_1.1.3-2.dsc b2374eccc0c6b03fcd484f504820cfcd 6956 java optional
Bug#912548: marked as done (jameica FTBFS with OpenJDK 11)
Your message dated Fri, 02 Nov 2018 17:53:45 + with message-id and subject line Bug#912548: fixed in jameica 2.8.2+dfsg-3 has caused the Debian Bug report #912548, regarding jameica FTBFS with OpenJDK 11 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.) -- 912548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jameica Version: 2.8.2+dfsg-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jameica.html ... compile: [mkdir] Created dir: /build/1st/jameica-2.8.2+dfsg/releases/tmp/bin [javac] Compiling 363 source files to /build/1st/jameica-2.8.2+dfsg/releases/tmp/bin [javac] warning: [options] bootstrap class path not set in conjunction with -source 7 [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/bookmark/BookmarkSearchProvider.java:17: error: package javax.annotation does not exist [javac] import javax.annotation.Resource; [javac]^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/bookmark/BookmarkService.java:17: error: package javax.annotation does not exist [javac] import javax.annotation.Resource; [javac]^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanStore.java:22: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.JAXBContext; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanStore.java:23: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.Marshaller; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanStore.java:24: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.Unmarshaller; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanContainer.java:17: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlAttribute; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanContainer.java:18: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlElement; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanContainer.java:19: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlElementWrapper; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanContainer.java:20: error: package javax.xml.bind.annotation does not exist [javac] import javax.xml.bind.annotation.XmlRootElement; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/store/BeanContainer.java:28: error: cannot find symbol [javac] @XmlRootElement [javac] ^ [javac] symbol: class XmlRootElement [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/services/ScriptingService.java:25: warning: [deprecation] Observable in java.util has been deprecated [javac] import java.util.Observable; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/services/ScriptingService.java:26: warning: [deprecation] Observer in java.util has been deprecated [javac] import java.util.Observer; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/messaging/FileChangedMessageConsumer.java:14: warning: [deprecation] Observable in java.util has been deprecated [javac] import java.util.Observable; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/messaging/FileChangedMessageConsumer.java:15: warning: [deprecation] Observer in java.util has been deprecated [javac] import java.util.Observer; [javac] ^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/services/BeanService.java:22: error: package javax.annotation does not exist [javac] import javax.annotation.PostConstruct; [javac]^ [javac] /build/1st/jameica-2.8.2+dfsg/src/de/willuhn/jameica/services/BeanService.java:23: error: package javax.annotation does not exist [javac] import javax.annotation.PreDestroy; [javac]
Bug#910128: marked as done (bash-completion parallel FTBFS)
Your message dated Fri, 02 Nov 2018 17:49:18 + with message-id and subject line Bug#910128: fixed in bash-completion 1:2.8-1.1 has caused the Debian Bug report #910128, regarding bash-completion parallel FTBFS 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.) -- 910128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bash-completion Version: 1:2.8-1 Severity: serious Tags: ftbfs bash-completion randomly fails to build from source in a parallel setting. The following log exhibits the failure: | make[3]: Entering directory '/<>/completions' | make[3]: Nothing to be done for 'install-exec-am'. | for file in 7za ; do \ | rm -f /<>/debian/bash-completion/usr/share/bash-completion/completions/$file && \ | ln -s 7z /<>/debian/bash-completion/usr/share/bash-completion/completions/$file ; \ | done | /bin/mkdir -p '/<>/debian/bash-completion/usr/share/bash-completion/completions' | ln: failed to create symbolic link '/<>/debian/bash-completion/usr/share/bash-completion/completions/7za': No such file or directory | make[3]: *** [Makefile:1103: symlinks] Error 1 | make[3]: *** Waiting for unfinished jobs | /usr/bin/install -c -m 644 2to3 7z a2x abook aclocal acpi adb add_members alias ant apache2ctl appdata-validate apt-build apt-cache apt-get aptitude arch arping arpspoof asciidoc aspe | /usr/bin/install -c -m 644 cfrun chage change_pw check_db check_perms checksec _chfn chgrp chkconfig chown chpasswd chronyc chrpath _chsh cksfv cleanarch clisp clone_member complete c | /usr/bin/install -c -m 644 dpkg-source dselect dsniff dumpdb dumpe2fs e2freefrag e2label ebtables _eject eog ether-wake evince explodepkg export faillog fbgs fbi feh file file-roller | /usr/bin/install -c -m 644 gm gnatmake gnokii gnome-mplayer gpasswd gpg gpg2 gphoto2 gprof groupadd groupdel groupmems groupmod growisofs grpck gzip hcitool hddtemp _hexdump hid2hci h | /usr/bin/install -c -m 644 ipsec iptables ipv6calc iscsiadm isql iwconfig iwlist iwpriv iwspy jar jarsigner java javaws jpegoptim jps jshint k3b kcov kill killall kldload kldunload ko | /usr/bin/install -c -m 644 lpr lrzip lsof lsscsi lsusb lua luac luseradd luserdel lvm lz4 lzip lzma lzop macof mailmanctl make makepkg man mc mcrypt mdadm mdtool medusa mii-diag mii-t | /usr/bin/install -c -m 644 mtx munindoc munin-node-configure munin-run munin-update mussh mutt mysql mysqladmin nc ncftp nethogs _newgrp newlist newusers ngrep nmap _nmcli nproc nsloo | /usr/bin/install -c -m 644 pkgrm pkgtool pkgutil plague-client pm-hibernate pm-is-supported pm-powersave pngfix portinstall portsnap portupgrade postcat postconf postfix postmap posts | /usr/bin/install -c -m 644 rdesktop remove_members removepkg _renice _repomanage reportbug _reptyr resolvconf _rfkill ri rmlist rmmod route rpcdebug rpm rpm2tgz rpmcheck rrdtool rsync | /usr/bin/install -c -m 644 sshow strace strings _su sudo svcadm svk _svn _svnadmin _svnlook sync_members synclient sysbench sysctl tar tcpdump tcpkill tcpnice timeout tipc tox tracepa | /usr/bin/install -c -m 644 vmstat vncviewer vpnc watch webmitm wget wine withlist wodim wol _write wsimport wtf wvdial xdg-mime xdg-settings xfreerdp xgamma xhost xm xmllint xmlwf xmm | make[3]: Leaving directory '/<>/completions' | make[2]: *** [Makefile:993: install-am] Error 2 | make[2]: Leaving directory '/<>/completions' | make[1]: *** [Makefile:485: install-recursive] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_install: make -j12 install DESTDIR=/<>/debian/bash-completion AM_UPDATE_INFO_DIR=no returned exit code 2 | make: *** [debian/rules:40: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Notably, the completion directory is created after adding symlinks into it. Looking at the generated completions/Makefile, one can see the cause: The symlinks target creates the symlinks and depends on $(targetdir), but there is no target for $(targetdir). Instead, the completion directory is created by install-bashcompDATA and these targets are fully independent. install-data-am depends on install-bashcompDATA and install-data-local. The latter depends on symlinks. We'd need a dependency from symlinks on install-bashcompDATA, but I have no clue how to add that in completions/Makefile.am. Hope this helps anyway Helmut --- End Message --- --- Begin Message --- Source: bash-completion Source-Version: 1:2.8-1.1 We believe that the bug you reported is fixed in the latest
Bug#912548: Bug #912548 in jameica marked as pending
Control: tag -1 pending Hello, Bug #912548 in jameica 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/jameica/commit/1070921c6d2f7d80a81107660fc5b12d8eced954 Add libjaxb-api-java build dependency Closes: #912548 (this message was generated automatically) -- Greetings https://bugs.debian.org/912548
Processed: Bug #912548 in jameica marked as pending
Processing control commands: > tag -1 pending Bug #912548 [src:jameica] jameica FTBFS with OpenJDK 11 Added tag(s) pending. -- 912548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #912543 in libnetx-java marked as pending
Processing control commands: > tag -1 pending Bug #912543 [src:libnetx-java] libnetx-java: FTBFS with Java 11 due to SecurityManager.checkTopLevelWindow() removal Added tag(s) pending. -- 912543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912543: Bug #912543 in libnetx-java marked as pending
Control: tag -1 pending Hello, Bug #912543 in libnetx-java 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/libnetx-java/commit/f5069a0047f0272a8119bd919cc9834909c890c5 Fixed the build failure with Java 11 (Closes: #912543) (this message was generated automatically) -- Greetings https://bugs.debian.org/912543
Processed: retitle 912391 to segment: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912391 segment: FTBFS with Java 11 due to JAXB removal Bug #912391 [src:segment] segment: FTBFS with Java 11 due to JAXB removal Ignoring request to change the title of bug#912391 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912477 to libcommons-collections4-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912477 libcommons-collections4-java: FTBFS with Java 11 due to > ambiguous Collection.toArray() method Bug #912477 [src:libcommons-collections4-java] libcommons-collections4-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method Ignoring request to change the title of bug#912477 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912359 to msv: FTBFS with Java 11 due to CORBA removal
Processing commands for cont...@bugs.debian.org: > retitle 912359 msv: FTBFS with Java 11 due to CORBA removal Bug #912359 [src:msv] msv: FTBFS with Java 11 due to CORBA removal Ignoring request to change the title of bug#912359 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912373 to libswingx1-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912373 libswingx1-java: FTBFS with Java 11 due to ambiguous > Collection.toArray() method Bug #912373 [src:libswingx1-java] libswingx1-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method Ignoring request to change the title of bug#912373 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912351 to stax-ex: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912351 stax-ex: FTBFS with Java 11 due to JAXB removal Bug #912351 [src:stax-ex] stax-ex: FTBFS with Java 11 due to JAXB removal Ignoring request to change the title of bug#912351 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912386 to rdp-readseq: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912386 rdp-readseq: FTBFS with Java 11 due to JAXB removal Bug #912386 [src:rdp-readseq] rdp-readseq FTBFS with OpenJDK 11 Changed Bug title to 'rdp-readseq: FTBFS with Java 11 due to JAXB removal' from 'rdp-readseq FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912388 to rdp-alignment: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912388 rdp-alignment: FTBFS with Java 11 due to JAXB removal Bug #912388 [src:rdp-alignment] rdp-alignment FTBFS with OpenJDK 11 Changed Bug title to 'rdp-alignment: FTBFS with Java 11 due to JAXB removal' from 'rdp-alignment FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912373 to libswingx1-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912373 libswingx1-java: FTBFS with Java 11 due to ambiguous > Collection.toArray() method Bug #912373 [src:libswingx1-java] libswingx1-java FTBFS with OpenJDK 11 Changed Bug title to 'libswingx1-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method' from 'libswingx1-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912385 to rdp-classifier: FTBFS with Java 11 due to java.se.ee module removal
Processing commands for cont...@bugs.debian.org: > retitle 912385 rdp-classifier: FTBFS with Java 11 due to java.se.ee module > removal Bug #912385 [src:rdp-classifier] rdp-classifier FTBFS with OpenJDK 11 Changed Bug title to 'rdp-classifier: FTBFS with Java 11 due to java.se.ee module removal' from 'rdp-classifier FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912231 to bnd: FTBFS with Java 11 due to conflict with OutputStream.nullOutputStream()
Processing commands for cont...@bugs.debian.org: > retitle 912231 bnd: FTBFS with Java 11 due to conflict with > OutputStream.nullOutputStream() Bug #912231 [src:bnd] bnd FTBFS with OpenJDK 11 Changed Bug title to 'bnd: FTBFS with Java 11 due to conflict with OutputStream.nullOutputStream()' from 'bnd FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912235 to figtree: FTBFS with Java 11 due to javax.activation and CORBA removal
Processing commands for cont...@bugs.debian.org: > retitle 912235 figtree: FTBFS with Java 11 due to javax.activation and CORBA > removal Bug #912235 [src:figtree] figtree FTBFS with OpenJDK 11 Changed Bug title to 'figtree: FTBFS with Java 11 due to javax.activation and CORBA removal' from 'figtree FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911436: marked as done (prometheus-haproxy-exporter: FTBFS undefined: prometheus.NewProcessCollectorPIDFn)
Your message dated Fri, 02 Nov 2018 16:02:13 + with message-id and subject line Bug#911436: fixed in prometheus-haproxy-exporter 0.9.0+git20180917+ds-1 has caused the Debian Bug report #911436, regarding prometheus-haproxy-exporter: FTBFS undefined: prometheus.NewProcessCollectorPIDFn 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.) -- 911436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prometheus-haproxy-exporter Version: 0.9.0-1 Severity: serious Tags: ftbfs Dear Maintainer, When rebuild prometheus-haproxy-exporter, it FTBFS, # github.com/prometheus/haproxy_exporter src/github.com/prometheus/haproxy_exporter/haproxy_exporter.go:506:19: undefined: prometheus.NewProcessCollectorPIDFn github.com/prometheus/client_golang removed NewProcessCollectorPIDFn in https://github.com/prometheus/client_golang/commit/773f502 This problem is fiexed in upstream https://github.com/prometheus/haproxy_exporter/commit/be645b2a6c65d2b443528c6f1cda858a343ae87d -- Shengjing Zhu --- End Message --- --- Begin Message --- Source: prometheus-haproxy-exporter Source-Version: 0.9.0+git20180917+ds-1 We believe that the bug you reported is fixed in the latest version of prometheus-haproxy-exporter, 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. Martín Ferrari (supplier of updated prometheus-haproxy-exporter 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: Fri, 02 Nov 2018 13:45:55 + Source: prometheus-haproxy-exporter Binary: prometheus-haproxy-exporter Architecture: source Version: 0.9.0+git20180917+ds-1 Distribution: unstable Urgency: high Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Description: prometheus-haproxy-exporter - HAProxy Exporter for Prometheus Closes: 909174 909175 911436 Changes: prometheus-haproxy-exporter (0.9.0+git20180917+ds-1) unstable; urgency=high . * New usptream snapshot, fixes build issues. Closes: #911436. * Add +ds suffix to mark repackaging. * Add myself to uploaders. * Match Files-Excluded with current repo. * Use new repo layout. * Use repackaging suffix in debian/watch. * Bring in line with other exporters: rename binary, add initscripts, create system user, install documentation and manpage. Closes: #909175, #909174. * Update Standards-Version with no changes. Checksums-Sha1: c985f62dffd580fd53728edceb41cdf1fb46945b 2538 prometheus-haproxy-exporter_0.9.0+git20180917+ds-1.dsc e50264db541e4837920a00e014fbd67334781fb6 28505 prometheus-haproxy-exporter_0.9.0+git20180917+ds.orig.tar.gz a48432c5c97486185c4b870036270c750de5e42b 5048 prometheus-haproxy-exporter_0.9.0+git20180917+ds-1.debian.tar.xz c5c058ea39314dfb9dfb7880a3691d949724c2b7 8070 prometheus-haproxy-exporter_0.9.0+git20180917+ds-1_amd64.buildinfo Checksums-Sha256: 208ee967236e4492a6c2e573b42c6e976b065f889b5524c8cc7e5d99d2e96e36 2538 prometheus-haproxy-exporter_0.9.0+git20180917+ds-1.dsc 6ee89edaef62476acb2af14a7b76023049a66acbc8103a3a6d5abf0d1e20dac4 28505 prometheus-haproxy-exporter_0.9.0+git20180917+ds.orig.tar.gz 863ccac37525c83217a405fa46deb3dd2bd47a3e501c3d4903ae22cca9d7bc45 5048 prometheus-haproxy-exporter_0.9.0+git20180917+ds-1.debian.tar.xz 3c72601129590bd3d5b49f62f52c73d4807ca4b8e4bf861a90719d0249e84ec7 8070 prometheus-haproxy-exporter_0.9.0+git20180917+ds-1_amd64.buildinfo Files: 458d4730c5958c8a91827312466dc57f 2538 devel optional prometheus-haproxy-exporter_0.9.0+git20180917+ds-1.dsc 9406d60a896453380c1b20d73bf15857 28505 devel optional prometheus-haproxy-exporter_0.9.0+git20180917+ds.orig.tar.gz 5ac10f992d4e522b09eef896c9a33f2e 5048 devel optional prometheus-haproxy-exporter_0.9.0+git20180917+ds-1.debian.tar.xz c28b7768849214a5d3b50e9bc84f46b9 8070 devel optional prometheus-haproxy-exporter_0.9.0+git20180917+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlvcVXUACgkQXdjgv5Gj 09rxgg//cswcN7S5Lv/017FM8TVZRqXaEd1USh9UQT9IZKjwe9viUvHbQjZAjjGR
Processed: retitle 912240 to gentlyweb-utils: FTBFS with Java 11 due to javax.activation removal
Processing commands for cont...@bugs.debian.org: > retitle 912240 gentlyweb-utils: FTBFS with Java 11 due to javax.activation > removal Bug #912240 [src:gentlyweb-utils] gentlyweb-utils FTBFS with OpenJDK 11 Changed Bug title to 'gentlyweb-utils: FTBFS with Java 11 due to javax.activation removal' from 'gentlyweb-utils FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912384 to obantoo: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912384 obantoo: FTBFS with Java 11 due to JAXB removal Bug #912384 [src:obantoo] obantoo FTBFS with OpenJDK 11 Changed Bug title to 'obantoo: FTBFS with Java 11 due to JAXB removal' from 'obantoo FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912261 to clojure: FTBFS with Java 11 due to overloaded Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912261 clojure: FTBFS with Java 11 due to overloaded > Collection.toArray() method Bug #912261 [src:clojure] clojure FTBFS with OpenJDK 11 Changed Bug title to 'clojure: FTBFS with Java 11 due to overloaded Collection.toArray() method' from 'clojure FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912270 to writer2latex: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912270 writer2latex: FTBFS with Java 11 due to JAXB removal Bug #912270 [src:writer2latex] writer2latex FTBFS with OpenJDK 11 Changed Bug title to 'writer2latex: FTBFS with Java 11 due to JAXB removal' from 'writer2latex FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912273 to unsafe-mock: FTBFS with Java 11 due to sun.reflect.Reflection removal
Processing commands for cont...@bugs.debian.org: > retitle 912273 unsafe-mock: FTBFS with Java 11 due to sun.reflect.Reflection > removal Bug #912273 [src:unsafe-mock] unsafe-mock FTBFS with OpenJDK 11 Changed Bug title to 'unsafe-mock: FTBFS with Java 11 due to sun.reflect.Reflection removal' from 'unsafe-mock FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912395 to resteasy3.0: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912395 resteasy3.0: FTBFS with Java 11 due to JAXB removal Bug #912395 [src:resteasy3.0] resteasy3.0 FTBFS with OpenJDK 11 Changed Bug title to 'resteasy3.0: FTBFS with Java 11 due to JAXB removal' from 'resteasy3.0 FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912545 to jruby-openssl: FTBFS with Java 11 due to javax.annotation removal
Processing commands for cont...@bugs.debian.org: > retitle 912545 jruby-openssl: FTBFS with Java 11 due to javax.annotation > removal Bug #912545 [src:jruby-openssl] jruby-openssl FTBFS with OpenJDK 11 Changed Bug title to 'jruby-openssl: FTBFS with Java 11 due to javax.annotation removal' from 'jruby-openssl FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891901: Info received (Progress on "java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory")
Ah yes, and (following [1]) I also changed the .pom file in /usr/share/java/slf4j-simple.jar to remove the "test" scope: --- pom.xml 2018-11-02 16:50:02.705092444 +0100 +++ pom.xml.orig2018-11-02 16:50:17.793353153 +0100 @@ -30,9 +30,9 @@ org.slf4j slf4j-api - + test-jar 1.7.25 - + test Perhaps that's needed as well, I didn't revert and re-test. Ad 1: https://stackoverflow.com/questions/12926899/java-lang-noclassdeffounderror-org-slf4j-loggerfactory/25621130
Processed: retitle 912543 to libnetx-java: FTBFS with Java 11 due to SecurityManager.checkTopLevelWindow() removal
Processing commands for cont...@bugs.debian.org: > retitle 912543 libnetx-java: FTBFS with Java 11 due to > SecurityManager.checkTopLevelWindow() removal Bug #912543 [src:libnetx-java] libnetx-java FTBFS with OpenJDK 11 Changed Bug title to 'libnetx-java: FTBFS with Java 11 due to SecurityManager.checkTopLevelWindow() removal' from 'libnetx-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 908068 0.3.0~dev-1~exp4
Bug #908068 {Done: Roger Shimizu } [torbrowser-launcher]
torbrowser-launcher fails with torbrowser 8.0
Marked as fixed in versions torbrowser-launcher/0.3.0~dev-1~exp4.
> fixed 908463 0.3.0~dev-1~exp4
Bug #908463 {Done: Roger Shimizu } [torbrowser-launcher]
torbrowser-launcher: Fails to start "Web Content" processes due to outdated
AppArmor policy
Marked as fixed in versions torbrowser-launcher/0.3.0~dev-1~exp4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
908068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908068
908463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 912351 to stax-ex: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912351 stax-ex: FTBFS with Java 11 due to JAXB removal Bug #912351 [src:stax-ex] stax-ex FTBFS with OpenJDK 11 Changed Bug title to 'stax-ex: FTBFS with Java 11 due to JAXB removal' from 'stax-ex FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912351 to stax-ex: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912351 stax-ex: FTBFS with Java 11 due to JAXB removal Bug #912351 [src:stax-ex] stax-ex: FTBFS with Java 11 due to JAXB removal Ignoring request to change the title of bug#912351 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912461 to jaxb: FTBFS with Java 11 due to javax.activation removal
Processing commands for cont...@bugs.debian.org: > retitle 912461 jaxb: FTBFS with Java 11 due to javax.activation removal Bug #912461 [src:jaxb] jaxb FTBFS with OpenJDK 11 Changed Bug title to 'jaxb: FTBFS with Java 11 due to javax.activation removal' from 'jaxb FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912391 to segment: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912391 segment: FTBFS with Java 11 due to JAXB removal Bug #912391 [src:segment] segment: FTBFS with Java 11 due to JAXB removal Ignoring request to change the title of bug#912391 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912391 to segment: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912391 segment: FTBFS with Java 11 due to JAXB removal Bug #912391 [src:segment] segment FTBFS with OpenJDK 11 Changed Bug title to 'segment: FTBFS with Java 11 due to JAXB removal' from 'segment FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891901: Progress on "java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory"
With libslf4j-java and libastylej-jni installed and
using this diff I got a bit further:
--- /usr/bin/arduino.orig 2018-11-02 16:15:19.374287467 +0100
+++ /usr/bin/arduino2018-11-02 16:14:29.159663536 +0100
@@ -22,6 +22,8 @@
java/lib/rt.jar \
java/lib/tools.jar \
lib/*.jar \
+/usr/share/java/slf4j-simple.jar \
+/usr/share/java/slf4j-api-1.7.25.jar \
;
do
CLASSPATH="${CLASSPATH}:${LIB}"
Now I just needed to fix up a symlink
# ln -sf /usr/lib/jni/x86_64-linux-gnu/libastylej.so /usr/share/arduino/lib/
(which was wrong, "x86_64-linux-gnu" was missing) and
got "arduino" working again.
Bug#912458: marked as done (jftp: FTBFS with OpenJDK 11 due to Thread.destroy() removal)
Your message dated Fri, 02 Nov 2018 15:28:21 + with message-id and subject line Bug#912458: fixed in jftp 1.60+dfsg-3 has caused the Debian Bug report #912458, regarding jftp: FTBFS with OpenJDK 11 due to Thread.destroy() removal 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.) -- 912458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jftp Version: 1.60+dfsg-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jftp.html ... compile: [javac] /build/1st/jftp-1.60+dfsg/build.xml:68: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 125 source files to /build/1st/jftp-1.60+dfsg/build/classes [javac] /build/1st/jftp-1.60+dfsg/src/java/net/sf/jftp/util/JReciever.java:95: error: cannot find symbol [javac] reciever.destroy(); [javac] ^ [javac] symbol: method destroy() [javac] location: variable reciever of type Thread [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 error BUILD FAILED /build/1st/jftp-1.60+dfsg/build.xml:68: Compile failed; see the compiler error output for details. Total time: 5 seconds dh_auto_build: ant -Duser.name debian -Dant.build.javac.source=1.6 -Dant.build.javac.target=1.6 jars returned exit code 1 make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: jftp Source-Version: 1.60+dfsg-3 We believe that the bug you reported is fixed in the latest version of jftp, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated jftp 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: Fri, 02 Nov 2018 14:48:53 +0100 Source: jftp Binary: jftp Architecture: source Version: 1.60+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: jftp - Java GUI client for FTP, SMB, SFTP and NFS Closes: 912458 Changes: jftp (1.60+dfsg-3) unstable; urgency=medium . * Team upload. * Fixed the build failure with Java 11 (Closes: #912458) * Standards-Version updated to 4.2.1 * Switch to debhelper level 11 * Use salsa.debian.org Vcs-* URLs Checksums-Sha1: 846037714c671746586017fd8e58abe88900f743 2130 jftp_1.60+dfsg-3.dsc 5d3e808c5f1de2e9b767a6e281b3d1e4734224f3 14892 jftp_1.60+dfsg-3.debian.tar.xz b42bf2d9f52d2910230dfb072c30e411b7086155 13160 jftp_1.60+dfsg-3_source.buildinfo Checksums-Sha256: 8bb9e98333e6d9f9ee31e749c5606cf388ef467c0b3fcc699768c55530255885 2130 jftp_1.60+dfsg-3.dsc f3e7c84d4b7db8503ec5133d5380255009f51ba322e98be9aa32b9876163a02c 14892 jftp_1.60+dfsg-3.debian.tar.xz 94b301890d62ae7d0422b9fd148c8c13db0ab72ccf20dfdf97ebb758e9e54978 13160 jftp_1.60+dfsg-3_source.buildinfo Files: d0a237d4576e6d7d5c182e2c98f172e5 2130 net optional jftp_1.60+dfsg-3.dsc 180064178489889914209cd31c599c1a 14892 net optional jftp_1.60+dfsg-3.debian.tar.xz 7c24a2797e5fddd261e36060e92f5d79 13160 net optional jftp_1.60+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlvcVogSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsF3sQAJ+LYqGrTH2OajDZ9ZBXHsjO+BisdO96 TQ//6fYlCz+JNxgirhhpsaO8gKioY0lMKq0WcpvAb4n0+TlN7kNIhIyJinX7JxzM URGeGr7q4xVqock14leTj+GF11QbVNRVxObTPbRr/vZRku+PWMSNtyskFx3R/E4G UTf+VQ6PWCIe1Zp8sRaT1bQLug9fLTJAtAJZ9zfi1kmKTSWz9YbvtsMhnpv+WE4X sEIJweNHWJMLElbpVUCusuVPSWUnIZcFCfac1gSXjxFUFR4lpY4SENRX/glTuqOT 9hJgM2WQKmN67jhj3Qd8htr1IeFO+oH7Le+dwiFH4DAiMcyngPCk7mne1HPQkVJf JZAqgg/0y4UbwDUgFDq9RoyyqLBU5yhn99QhQIOXSuOGcYU+xfQTQneiu7ZNCjMl I4nP9eH9vTK7XgLyyKompdKi8OZasPADtMWom9ErE6jcd8gpfsvOIQNyoi3Detzf
Processed: Re: Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related
Processing control commands: > reassign -1 akregator 4:18.08.1-1 Bug #910852 [libqt5webengine5] libqt5webengine5: Akregator crashes very often, WebEngine related Bug reassigned from package 'libqt5webengine5' to 'akregator'. No longer marked as found in versions qtwebengine-opensource-src/5.11.1+dfsg-5. Ignoring request to alter fixed versions of bug #910852 to the same values previously set Bug #910852 [akregator] libqt5webengine5: Akregator crashes very often, WebEngine related Marked as found in versions akregator/4:18.08.1-1. > retitle -1 Akregator crashes very often, WebEngine thread safety issue Bug #910852 [akregator] libqt5webengine5: Akregator crashes very often, WebEngine related Changed Bug title to 'Akregator crashes very often, WebEngine thread safety issue' from 'libqt5webengine5: Akregator crashes very often, WebEngine related'. -- 910852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related
Control: reassign -1 akregator 4:18.08.1-1 Control: retitle -1 Akregator crashes very often, WebEngine thread safety issue On Fri, Oct 19, 2018 at 06:48:37PM +0300, Dmitry Shachnev wrote: > I have reported this bug to Qt upstream, but they say it is not their bug, > but a thread safety issue in libkf5webengineviewer5. So I have now filed a > bug to KDE. > > I am not yet sure if I should reassign this to libkf5webengineviewer5 or > akregator, let's wait for KDE developers' response first. The upstream bug has a potential patch [1] for akregator, so reassigning to akregator. Please feel free to further reassing to some KF5 libraries if needed. [1]: https://bugs.kde.org/show_bug.cgi?id=371511#c4 -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#910500: marked as done (libqt5quick5: Sefault in applications using QWebEngineView)
Your message dated Fri, 2 Nov 2018 18:19:53 +0300
with message-id <20181102151953.ga13...@mitya57.me>
and subject line Re: Bug#910317: QtWebEngine in unstable is constantly crashing
has caused the Debian Bug report #910317,
regarding libqt5quick5: Sefault in applications using QWebEngineView
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.)
--
910317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5quick5
Version: 5.11.1-6
Severity: important
Hi,
I have a simple Qt application that's been segfaulting ever since
libqt5quick5 has been updated to 5.11.1-6. The crash does not happen
with 5.11.1-5, so I assume the problem is caused by the unaligned
memory access fix that's been backported.
See the following example to reproduce the problem. The crash may
happen while scrolling the page, if not as soon as page is loaded.
Not all the webpages can trigger the bug.
I can provide more info in case the example is not enough to
reproduce the problem.
Regards,
Gabriele
---
$ cat main.cpp
#include
#include
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
QWebEngineView view;
view.setUrl(QUrl("https://www.qt.io;));
view.resize(1024, 750);
view.show();
return app.exec();
}
$ cat example.pro
TEMPLATE = app
QT += webenginewidgets
SOURCES += main.cpp
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-00081-g078ad232623b (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libqt5quick5 depends on:
ii libc6 2.27-6
ii libqt5core5a [qtbase-abi-5-11-0] 5.11.1+dfsg-9
ii libqt5gui5 5.11.1+dfsg-9
ii libqt5network5 5.11.1+dfsg-9
ii libqt5qml5 [qtdeclarative-abi-5-11-0] 5.11.1-6
ii libstdc++6 8.2.0-7
libqt5quick5 recommends no packages.
libqt5quick5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.11.2+dfsg-1
On Thu, Oct 18, 2018 at 03:42:58PM +0300, Dmitry Shachnev wrote:
> I cannot reproduce this crash with 5.11.2 packages (now in unstable).
>
> Are you sure you are getting the same crash, maybe the stacktrace is a
> different one? Did you try to use the debugger to get stacktrace?
>
> In any case please paste the URL of page where Falkon is crashing, or
> attach the C++ example if you have it.
I just tried the original Python example with the latest packages from
unstable, and it does not crash anymore. So closing this bug.
If you still experience crashes then file a new bug with a fresh stacktrace.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
Bug#910317: marked as done (QtWebEngine in unstable is constantly crashing)
Your message dated Fri, 2 Nov 2018 18:19:53 +0300
with message-id <20181102151953.ga13...@mitya57.me>
and subject line Re: Bug#910317: QtWebEngine in unstable is constantly crashing
has caused the Debian Bug report #910317,
regarding QtWebEngine in unstable is constantly crashing
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.)
--
910317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyqt5.qtwebengine
Version: 5.11.2+dfsg-1
Severity: serious
X-Debbugs-CC: debian-qt-...@lists.debian.org
Control: affects -1 + libqt5webengine5
Dear Debian Qt/KDE maintainers and pyqt5.qtwebengine maintainers,
Current QtWebEngine in Debian Unstable would easily crash. That
happens after recent upgrade of libkf5.
For example, run the following script under python3:
$ export LC_ALL=C.UTF-8
$ export LANG=C
$ cat ./test.py
import sys
from PyQt5.QtWidgets import QApplication
from PyQt5.QtWidgets import QMainWindow
from PyQt5.QtWebEngineWidgets import QWebEngineView
from PyQt5.QtCore import QUrl
def main():
app = QApplication(sys.argv)
window = QMainWindow()
window.setWindowTitle('PyQt Demo')
window.setGeometry(320, 180, 960, 540)
view = QWebEngineView()
view.load(QUrl('http://leafletjs.com/')) # error here
window.setCentralWidget(view)
window.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
$ python3 ./test.py
[1004/140404.438632:WARNING:stack_trace_posix.cc(699)] Failed to open
file: /tmp/.glBfSxZo (deleted)
Error: No such file or directory
[8494:8515:1004/140404.647050:ERROR:nss_util.cc(727)] After loading
Root Certs, loaded==false: NSS error code: -8018
Received signal 11 SEGV_MAPERR 0010
#0 0x7fc98c03e76e
#1 0x7fc98c03e880
#2 0x7fc98c03eeb7
#3 0x7fc9969db8e0
#4 0x7fc990771604
#5 0x7fc98aa8d660
#6 0x7fc98aabde3c
#7 0x7fc98a0af500 QQuickWindowPrivate::updateDirtyNode()
#8 0x7fc98a0af963 QQuickWindowPrivate::updateDirtyNodes()
#9 0x7fc98a0b0e22 QQuickWindowPrivate::syncSceneGraph()
#10 0x7fc98a16ce49 QQuickRenderControl::sync()
#11 0x7fc989c7e0c6
#12 0x7fc989c7e2a6
#13 0x7fc994b0003b QObject::event()
#14 0x7fc99548ac6b QWidget::event()
#15 0x7fc989c81e2d QQuickWidget::event()
#16 0x7fc990771bf0
#17 0x7fc99544c4a1 QApplicationPrivate::notify_helper()
#18 0x7fc995453ae0 QApplication::notify()
#19 0x7fc995d1f11e
#20 0x7fc994ad6589 QCoreApplication::notifyInternal2()
#21 0x7fc994b27648 QTimerInfoList::activateTimers()
#22 0x7fc994b27ea4
#23 0x7fc9939acc3e g_main_context_dispatch
#24 0x7fc9939aced8
#25 0x7fc9939acf6c g_main_context_iteration
#26 0x7fc994b28233 QEventDispatcherGlib::processEvents()
#27 0x7fc97df51ee1
#28 0x7fc994ad525b QEventLoop::exec()
#29 0x7fc994add3d2 QCoreApplication::exec()
#30 0x7fc995ce214b
#31 0x005068bf
#32 0x0050a4e9 _PyEval_EvalFrameDefault
#33 0x00505d58
#34 0x00506a8d
#35 0x0050a4e9 _PyEval_EvalFrameDefault
#36 0x005088b8
#37 0x0050a023 PyEval_EvalCode
#38 0x00635f82
#39 0x0063603a PyRun_FileExFlags
#40 0x006397f8 PyRun_SimpleFileExFlags
#41 0x0063a38a Py_Main
#42 0x004ac090 main
#43 0x7fc996433b17 __libc_start_main
#44 0x005b35aa _start
r8: 17281b04 r9: 017ae3e0 r10: 17281b04
r11: 0001
r12: r13: 017651c0 r14: 7fc994b91660
r15: 017650e0
di: 01728da0 si: bp: 7ffc01652bc0
bx: 01713dd0
dx: 7fc994b91660 ax: 01082000 cx: 7fc994b91678
sp: 7ffc016527e0
ip: 7fc990771604 efl: 00010202 cgf: 002b0033
erf: 0004
trp: 000e msk: cr2: 0010
[end of stack trace]
Calling _exit(1). Core file will not be generated.
$
--
Thanks,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Version: 5.11.2+dfsg-1
On Thu, Oct 18, 2018 at 03:42:58PM +0300, Dmitry Shachnev wrote:
> I cannot reproduce this crash with 5.11.2 packages (now in unstable).
>
> Are you sure you are getting the same crash, maybe the stacktrace is a
> different one? Did you try to use the debugger to get stacktrace?
>
> In any case please paste the URL of page where Falkon is crashing, or
> attach the C++ example if you have it.
I just tried the original Python example with the latest packages from
unstable, and it does not crash anymore. So closing this bug.
If you still experience crashes then file a new bug with a fresh stacktrace.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message
Processed: retitle 912477 to libcommons-collections4-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912477 libcommons-collections4-java: FTBFS with Java 11 due to > ambiguous Collection.toArray() method Bug #912477 [src:libcommons-collections4-java] libcommons-collections4-java FTBFS with OpenJDK 11 Changed Bug title to 'libcommons-collections4-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method' from 'libcommons-collections4-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912515 to libcommons-collections3-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912515 libcommons-collections3-java: FTBFS with Java 11 due to > ambiguous Collection.toArray() method Bug #912515 [src:libcommons-collections3-java] libcommons-collections3-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method Ignoring request to change the title of bug#912515 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 912515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912515 to libcommons-collections3-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method
Processing commands for cont...@bugs.debian.org: > retitle 912515 libcommons-collections3-java: FTBFS with Java 11 due to > ambiguous Collection.toArray() method Bug #912515 [src:libcommons-collections3-java] libcommons-collections3-java FTBFS with OpenJDK 11 Changed Bug title to 'libcommons-collections3-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method' from 'libcommons-collections3-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912359 to msv: FTBFS with Java 11 due to CORBA removal
Processing commands for cont...@bugs.debian.org: > retitle 912359 msv: FTBFS with Java 11 due to CORBA removal Bug #912359 [src:msv] msv FTBFS with OpenJDK 11 Changed Bug title to 'msv: FTBFS with Java 11 due to CORBA removal' from 'msv FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912538 to libjaba-client-java: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912538 libjaba-client-java: FTBFS with Java 11 due to JAXB removal Bug #912538 [src:libjaba-client-java] libjaba-client-java FTBFS with OpenJDK 11 Changed Bug title to 'libjaba-client-java: FTBFS with Java 11 due to JAXB removal' from 'libjaba-client-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912539 to libjdom1-java: FTBFS with Java 11 due to CORBA removal
Processing commands for cont...@bugs.debian.org: > retitle 912539 libjdom1-java: FTBFS with Java 11 due to CORBA removal Bug #912539 [src:libjdom1-java] libjdom1-java FTBFS with OpenJDK 11 Changed Bug title to 'libjdom1-java: FTBFS with Java 11 due to CORBA removal' from 'libjdom1-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912267 to uddi4j: FTBFS with Java 11 due to JAXWS removal
Processing commands for cont...@bugs.debian.org: > retitle 912267 uddi4j: FTBFS with Java 11 due to JAXWS removal Bug #912267 [src:uddi4j] uddi4j FTBFS with OpenJDK 11 Changed Bug title to 'uddi4j: FTBFS with Java 11 due to JAXWS removal' from 'uddi4j FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912473 to jython: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912473 jython: FTBFS with Java 11 due to JAXB removal Bug #912473 [src:jython] jython FTBFS with OpenJDK 11 Changed Bug title to 'jython: FTBFS with Java 11 due to JAXB removal' from 'jython FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912377 to libxstream-java: FTBFS with Java 11 due to javax.activation removal
Processing commands for cont...@bugs.debian.org: > retitle 912377 libxstream-java: FTBFS with Java 11 due to javax.activation > removal Bug #912377 [src:libxstream-java] libxstream-java FTBFS with OpenJDK 11 Changed Bug title to 'libxstream-java: FTBFS with Java 11 due to javax.activation removal' from 'libxstream-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912390 to shiro: FTBFS with Java 11 due to javax.annotation removal
Processing commands for cont...@bugs.debian.org: > retitle 912390 shiro: FTBFS with Java 11 due to javax.annotation removal Bug #912390 [src:shiro] shiro FTBFS with OpenJDK 11 Changed Bug title to 'shiro: FTBFS with Java 11 due to javax.annotation removal' from 'shiro FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912467 to jasperreports: FTBFS with Java 11 due to javax.xml.soap removal
Processing commands for cont...@bugs.debian.org: > retitle 912467 jasperreports: FTBFS with Java 11 due to javax.xml.soap removal Bug #912467 [src:jasperreports] jasperreports FTBFS with OpenJDK 11 Changed Bug title to 'jasperreports: FTBFS with Java 11 due to javax.xml.soap removal' from 'jasperreports FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912392 to scilab: FTBFS with Java 11 due to javax.annotation removal
Processing commands for cont...@bugs.debian.org: > retitle 912392 scilab: FTBFS with Java 11 due to javax.annotation removal Bug #912392 [src:scilab] scilab FTBFS with OpenJDK 11 Changed Bug title to 'scilab: FTBFS with Java 11 due to javax.annotation removal' from 'scilab FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912394 to rsyntaxtextarea: FTBFS with Java 11 due to SecurityManager.checkSystemClipboardAccess() removal
Processing commands for cont...@bugs.debian.org: > retitle 912394 rsyntaxtextarea: FTBFS with Java 11 due to > SecurityManager.checkSystemClipboardAccess() removal Bug #912394 [src:rsyntaxtextarea] rsyntaxtextarea FTBFS with OpenJDK 11 Changed Bug title to 'rsyntaxtextarea: FTBFS with Java 11 due to SecurityManager.checkSystemClipboardAccess() removal' from 'rsyntaxtextarea FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912468 to java3d: FTBFS with Java 11 due to sun.applet.AppletAudioClip removal
Processing commands for cont...@bugs.debian.org: > retitle 912468 java3d: FTBFS with Java 11 due to sun.applet.AppletAudioClip > removal Bug #912468 [src:java3d] java3d FTBFS with OpenJDK 11 Changed Bug title to 'java3d: FTBFS with Java 11 due to sun.applet.AppletAudioClip removal' from 'java3d FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912546 to jackson-module-jaxb-annotations: FTBFS with Java 11 due to javax.activation removal
Processing commands for cont...@bugs.debian.org: > retitle 912546 jackson-module-jaxb-annotations: FTBFS with Java 11 due to > javax.activation removal Bug #912546 [src:jackson-module-jaxb-annotations] jackson-module-jaxb-annotations FTBFS with OpenJDK 11 Changed Bug title to 'jackson-module-jaxb-annotations: FTBFS with Java 11 due to javax.activation removal' from 'jackson-module-jaxb-annotations FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912476 to libapache-poi-java: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912476 libapache-poi-java: FTBFS with Java 11 due to JAXB removal Bug #912476 [src:libapache-poi-java] libapache-poi-java FTBFS with OpenJDK 11 Changed Bug title to 'libapache-poi-java: FTBFS with Java 11 due to JAXB removal' from 'libapache-poi-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912541 to libjackson-json-java: FTBFS with Java 11 due to javax.activation and JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912541 libjackson-json-java: FTBFS with Java 11 due to > javax.activation and JAXB removal Bug #912541 [src:libjackson-json-java] libjackson-json-java FTBFS with OpenJDK 11 Changed Bug title to 'libjackson-json-java: FTBFS with Java 11 due to javax.activation and JAXB removal' from 'libjackson-json-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912266 to tomcat7: FTBFS with Java 11 due to JAXB removal
Processing commands for cont...@bugs.debian.org: > retitle 912266 tomcat7: FTBFS with Java 11 due to JAXB removal Bug #912266 [src:tomcat7] tomcat7 FTBFS with OpenJDK 11 Changed Bug title to 'tomcat7: FTBFS with Java 11 due to JAXB removal' from 'tomcat7 FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912642 to activemq: FTBFS with Java 11 due to javax.annotation removal
Processing commands for cont...@bugs.debian.org: > retitle 912642 activemq: FTBFS with Java 11 due to javax.annotation removal Bug #912642 [src:activemq] activemq FTBFS with OpenJDK 11 Changed Bug title to 'activemq: FTBFS with Java 11 due to javax.annotation removal' from 'activemq FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 912547 to libpicocontainer-java: FTBFS with Java 11 due to javax.annotation removal
Processing commands for cont...@bugs.debian.org: > retitle 912547 libpicocontainer-java: FTBFS with Java 11 due to > javax.annotation removal Bug #912547 [src:libpicocontainer-java] libpicocontainer-java FTBFS with OpenJDK 11 Changed Bug title to 'libpicocontainer-java: FTBFS with Java 11 due to javax.annotation removal' from 'libpicocontainer-java FTBFS with OpenJDK 11'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
