Bug#924811: marked as done (derpconf: FTBFS: build-dependency not installable: python-tox)
Your message dated Tue, 19 Mar 2019 22:25:24 -0300 with message-id and subject line Done in 0.8.2-2 has caused the Debian Bug report #924811, regarding derpconf: FTBFS: build-dependency not installable: python-tox 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.) -- 924811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: derpconf Version: 0.8.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), python-setuptools (>= 0.6b3), > python-all (>= 2.6.6-3), dh-python, python-pyvows, python-gevent, > python-coverage, python-colorama, python-tox, python-six > Filtered Build-Depends: debhelper (>= 9), python-setuptools (>= 0.6b3), > python-all (>= 2.6.6-3), dh-python, python-pyvows, python-gevent, > python-coverage, python-colorama, python-tox, python-six > dpkg-deb: building package 'sbuild-build-depends-derpconf-dummy' in > '/<>/resolver-8N74jH/apt_archive/sbuild-build-depends-derpconf-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-derpconf-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-8N74jH/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-8N74jH/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-8N74jH/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-8N74jH/apt_archive ./ Sources [558 B] > Get:5 copy:/<>/resolver-8N74jH/apt_archive ./ Packages [636 B] > Fetched 2157 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install derpconf build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-derpconf-dummy : Depends: python-tox but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/derpconf_0.8.2-1_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 0.8.2-2 -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org http://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#924814: Bug #924814 in grub2 marked as pending
Control: tag -1 pending Hello, Bug #924814 in grub2 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/grub-team/grub/commit/b561c734e249f8e2d6ad9f998095fddf0bbd8325 Make signed packages depend on a matching version of grub-common This is an attempt to prevent incorrect testing migrations. Closes: #924814 (this message was generated automatically) -- Greetings https://bugs.debian.org/924814
Processed: Bug #924814 in grub2 marked as pending
Processing control commands: > tag -1 pending Bug #924814 [src:grub-efi-amd64-signed] grub-efi-amd64-signed: FTBFS: build-dependency not installable: grub-efi-amd64-bin (= 2.02+dfsg1-11) Added tag(s) pending. -- 924814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922947: retroarch-assets: please don’t use hinted Roboto fonts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Control: severity -1 normal The RC issue was fixed in version 1.3.6+git20160731+dfsg1-2. Let's keep this bug open for Debian 11. For Buster we can still depend on the hinted fonts thus there is no risk of breaking anything. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlyRhLJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7 UeRbaxAAvnN9EO/0Nl2YY1T8wJ9nYdeKVw7zsA5KH//MNHx05BspVHl5ee6xDZn4 zc9LVS+URHt9s1IvrfaW2E1DTPrCplft/h0mFyQAnNZJ0PJwyT2aALeqOHFWThEK aUt0mukelF+VXvsdknQtFt/7AZO/3v7Z4z9NKjHtmTwejM+16mOtJ1GsytuH2Udu 9Mpnh2vNtXV/tQePlwKawzpJrbIA08vGSSVOvjtC8afrELV20ZPqTMwq55oMmSgA YEsrlGdn1W70iV31DdzYbAkbm6TLWl/ubgKglc+nIZZvh2crVcoGfArUWL3jP4xb zBVH/BjlunBTxXnT4+8hADBcjc+xdC7njXGHOisOyClqVcolzEjkEGUv/byNWZ+E 2zxVSUuiezpSgSMOXm2TcObAjaCjqeB/mgmQqpjjaohuvHy25zVo/BoH2yYolwxU 70n7+eaxG79JZjCxmukFgoHFSuUToN3KoF0MfC74XoCUzJb8JSQKqZe8rSxdr+zv bMrJtjeIyZa3ZDiA3pJPhS6C49sv4qeJp+UUgoGxgF0BrDWwt5PEcWb+5zz22tul V29LkJd7tvQUGx4jCdGwgvJ4O6SuZMJazRABotB6xjCgXcF3euKEdcYWCLFs6ESY jQZUIIuVM5M01Civ3y/zX7okdxTYPgGY2naEqtWvTxKn7dN8XnE= =6wrM -END PGP SIGNATURE-
Processed: Re: retroarch-assets: please don’t use hinted Roboto fonts
Processing control commands: > severity -1 normal Bug #922947 [retroarch-assets] retroarch-assets: please don’t use hinted Roboto fonts Severity set to 'normal' from 'serious' -- 922947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924941: d-shlibmove: fails in opensuse build service
Control: severity -1 normal Hi Lenz, failing to backport a package to some ancient release is not release critical. Let me see if I managed to understand what you want to achieve: * your target architecture is i386 (any other achitectures?) * you want to backport src:libsrtp2 to jessie (and maybe wheezy, too) * which version? libsrtp2 | 2.0.0+20170123-1 | stable | source libsrtp2 | 2.2.0-1 | testing| source libsrtp2 | 2.2.0-1 | unstable | source Rebuilding libsrtp2 2.0.0+20170123-1 in a jessie+jessie-backports chroot just worked fine for me. Trying this in a wheezy+wheezy-backports chroot fails with a lot of unsatisfied dependencies: The following packages have unmet dependencies: pbuilder-satisfydepends-dummy : Depends: licensecheck which is a virtual package. Depends: pkg-kde-tools but it is not going to be installed. Depends: pkg-config but it is not going to be installed. Depends: libpcap0.8-dev but it is not going to be installed. Depends: psmisc but it is not going to be installed. Depends: miscfiles but it is not going to be installed. Depends: d-shlibs but it is not going to be installed. Depends: doxygen-latex but it is not going to be installed. I'm not going to look into details :-) Don't forget: Support for wheezy-LTS has ended nearly a year ago in May 2018! Andreas
Processed: Re: Bug#924941: d-shlibmove: fails in opensuse build service
Processing control commands: > severity -1 normal Bug #924941 [src:d-shlibs] d-shlibmove: fails in opensuse build service Severity set to 'normal' from 'serious' -- 924941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922947: retroarch-assets: please don’t use hinted Roboto fonts
Control: tags -1 confirmed pending On Fri, 22 Feb 2019 09:18:51 +0100 Andrej Shadura wrote: > Package: retroarch-assets > Severity: normal > > Dear Maintainer, > > The Roboto upstream no longer provides hinted fonts, so > fonts-roboto-hinted is now a transitional package providing symlinks to > the unhinted fonts. Please modify your package to use the unhinted fonts > instead. Andrej, you should have also reverted fonts-roboto to depend on fonts-roboto-hinted again when you fixed #922457. In case of retroarch-assets which depends on fonts-roboto | fonts-roboto-hinted this will pull in fonts-roboto-unhinted now when fonts-roboto-hinted is not installed. I'm going to fix this issue now in retroarch-assets by only depending on fonts-roboto-hinted but such changes should not be made without proper testing before a full freeze. :/ Markus signature.asc Description: OpenPGP digital signature
Processed: Re: retroarch-assets: please don’t use hinted Roboto fonts
Processing control commands: > tags -1 confirmed pending Bug #922947 [retroarch-assets] retroarch-assets: please don’t use hinted Roboto fonts Added tag(s) pending and confirmed. -- 922947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 917738 in 1.16.3-1, found 924233 in 2.9.4-2, notfixed 924837 in mpich/3.3-3
Processing commands for cont...@bugs.debian.org:
> fixed 917738 1.16.3-1
Bug #917738 {Done: tony mancill }
[src:openhft-chronicle-threads] openhft-chronicle-threads: FTBFS: [ERROR]
/<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32]
cannot find symbol
Marked as fixed in versions openhft-chronicle-threads/1.16.3-1.
> found 924233 2.9.4-2
Bug #924233 [obs-server] obs-server: fails to purge: delgroup: `obsservicerun'
still has `obsrun' as their primary group!
Marked as found in versions open-build-service/2.9.4-2.
> notfixed 924837 mpich/3.3-3
Bug #924837 {Done: Alastair McKinstry } [src:adios]
adios: FTBFS: mpicxx.h:22:4: error: #error 'Please use the same version of GCC
and g++ for compiling MPICH and user MPI programs'
No longer marked as fixed in versions mpich/3.3-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917738
924233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924233
924837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#900152: nsca-ng: FTBFS against openssl 1.1.1
* Kurt Roeckx [2019-03-19 22:59]: > On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote: > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ > > unexpectedly returns NULL. I now avoid the function to work around the > > issue. > > This is documented here: > https://wiki.openssl.org/index.php/TLS1.3#PSKs Thanks. I'm still using the TLSv1.2 callbacks indeed, but from reading that text it's not obvious to me why SSL_get_psk_identity() would fail. (Note that I'm not using identity *hints* anywhere, which is the thing TLSv1.3 dropped.) However, I can easily imagine the bug(?) being related to the changes mentioned in that text.
Bug#900152: nsca-ng: FTBFS against openssl 1.1.1
On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote: > Just for the record: > > * Sebastian Andrzej Siewior [2018-11-05 00:28]: > > It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the > > testsuite passes. > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ > unexpectedly returns NULL. I now avoid the function to work around the > issue. This is documented here: https://wiki.openssl.org/index.php/TLS1.3#PSKs Kurt
Bug#925117: mariadb-10.3: drop the transitional libmariadbclient18 package
Source: mariadb-10.3 Version: 1:10.3.13-1 Severity: serious Hi Otto, please drop the transitional libmariadbclient18 package with the next upload. I think this will prevent a lot of upgrade problems, because packages from stretch will not suddenly start to use libmariadb3. (I just remember the two packages we hat to add Breaks against so far. And I expect users will hit more similar problems.) anbe@coccia:~$ dak rm -Rn -b libmariadbclient18 -s testing Will remove the following packages from testing: libmariadbclient18 | 1:10.3.13-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x Maintainer: Debian MySQL Maintainers --- Reason --- -- Checking reverse dependencies... # Broken Depends: qt4-x11: libqt4-sql-mysql [amd64 armel i386] Dependency problem found. The qt4-x11 FTBFS does seem unrelated to mariadb. Andreas
Bug#900152: nsca-ng: FTBFS against openssl 1.1.1
Just for the record: * Sebastian Andrzej Siewior [2018-11-05 00:28]: > It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the > testsuite passes. Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ unexpectedly returns NULL. I now avoid the function to work around the issue. ¹ https://www.openssl.org/docs/man1.1.1/man3/SSL_get_psk_identity.html
Bug#925051: diffoscope: FTBFS in stretch (failing tests)
Hi Santiago, > The relevant thing, IMO, is that proposed-updates and point > releases still exist for stretch, so I don't see it overkill Sure. Can you still loop the SRMs in on this before I backport this patch and create a stretchpu bug, etc. etc.? Thanks. :) > I don't see how the release cycle of buster is related. (Only in that one's efforts and energies might be best-placed directed towards buster, rather than stretch.) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#925051: diffoscope: FTBFS in stretch (failing tests)
On Tue, Mar 19, 2019 at 03:29:52PM -0400, Chris Lamb wrote: > Hi Santiago, > > > Ok, but this still should be fixed in stretch, right? > > (Packages in stretch must build in stretch). > > Sure thing, but this would require a stable update which seems a > little overkill, especially at this point in the buster release cycle…? I don't see how the release cycle of buster is related. The relevant thing, IMO, is that proposed-updates and point releases still exist for stretch, so I don't see it overkill at all. Thanks.
Bug#925051: diffoscope: FTBFS in stretch (failing tests)
Hi Santiago, > Ok, but this still should be fixed in stretch, right? > (Packages in stretch must build in stretch). Sure thing, but this would require a stable update which seems a little overkill, especially at this point in the buster release cycle…? Fancy pinging the SRMs on this? Not had to deal with this before. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#925051: diffoscope: FTBFS in stretch (failing tests)
On Tue, Mar 19, 2019 at 03:22:26PM -0400, Chris Lamb wrote: > I believe this was address on the diffoscope side here: > > > https://salsa.debian.org/reproducible-builds/diffoscope/commit/4a35e55497fac9845ca55be28fbd9e25b4e8576f > > ... which was released in diffoscope 112. Ok, but this still should be fixed in stretch, right? (Packages in stretch must build in stretch). Thanks.
Processed: Re: Bug#925051: diffoscope: FTBFS in stretch (failing tests)
Processing commands for cont...@bugs.debian.org: > fixed 925051 112 Bug #925051 [src:diffoscope] diffoscope: FTBFS in stretch (failing tests) Marked as fixed in versions diffoscope/112. > thanks Stopping processing here. Please contact me if you need assistance. -- 925051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925051: diffoscope: FTBFS in stretch (failing tests)
fixed 925051 112 thanks Hi Santiago, > I tried to build this package in stretch but it failed: […] This is because ghostscript was updated in stretch and it (unfortunately) now generates different output. I believe this was address on the diffoscope side here: https://salsa.debian.org/reproducible-builds/diffoscope/commit/4a35e55497fac9845ca55be28fbd9e25b4e8576f ... which was released in diffoscope 112. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#924712: crypt() not available _XOPEN_SOURCE is defined
* Laurent Bigonville: > Package: libc6-dev > Version: 2.28-8 > Severity: serious > > Hi, > > The crypt.3 manpage, state that _XOPEN_SOURCE should be define for > crypt() to be available. > > But it looks that it's currently the opposite, if _XOPEN_SOURCE is > defined, the function cannot be found. Can you compile the software using _DEFAULT_SOURCE (well, the default) or _GNU_SOURCE instead? We do not want to provide the CRYPT extension anymore because it implies not just support for the crypt function, but also for the DES encryption functions, which definitely do not want. In _XOPEN_SOURCE mode, it's either all of these functions or none of them (and we chose the latter because of DES), otherwise glibc wouldn't conform to the interface specification. We definitely should update the manual page, though.
Bug#924473: Corrected path
On Sun, Mar 17, 2019 at 07:09:52PM +0100, Bruno Kleinert wrote: Hi Jonathan, please find attached a debdiff that updates the path to the manpage. Thanks for this, I will endeavour to apply and upload Tomorrow (hit a snag locally, my sbuild environment hath borken)
Bug#900152: marked as done (nsca-ng: FTBFS against openssl 1.1.1)
Your message dated Tue, 19 Mar 2019 17:49:24 + with message-id and subject line Bug#900152: fixed in nsca-ng 1.6-1~exp1 has caused the Debian Bug report #900152, regarding nsca-ng: FTBFS against openssl 1.1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 900152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nsca-ng Version: 1.5-2 Severity: important User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-1.1.1 The new openssl 1.1.1 is currently in experimental [0]. This package failed to build against this new package [1] while it built fine against the openssl version currently in unstable [2]. Could you please have a look? The Error in the testsuite could be due to: 1.1.1~~pre6-1 changelog): | * Increase default security level from 1 to 2. This moves from the 80 bit | security level to the 112 bit securit level and will require 2048 bit RSA | and DHE keys. [0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be [1] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/nsca-ng_1.5-2_amd64-2018-05-01T20%3A31%3A09Z [2] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/nsca-ng_1.5-2_amd64-2018-05-02T18%3A46%3A37Z Sebastian --- End Message --- --- Begin Message --- Source: nsca-ng Source-Version: 1.6-1~exp1 We believe that the bug you reported is fixed in the latest version of nsca-ng, 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 900...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated nsca-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Mar 2019 18:15:45 +0100 Source: nsca-ng Binary: nsca-ng-client nsca-ng-client-dbgsym nsca-ng-server nsca-ng-server-dbgsym Architecture: source amd64 Version: 1.6-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Nagios Maintainer Group Changed-By: Bas Couwenberg Description: nsca-ng-client - Send monitoring commands to NSCA-ng server nsca-ng-server - Monitoring command acceptor Closes: 861315 900152 Changes: nsca-ng (1.6-1~exp1) experimental; urgency=medium . * Team upload. * New upstream release. (closes: #900152) * Drop autopkgtest to test installability. * Add lintian override for testsuite-autopkgtest-missing. * Bump Standards-Version to 4.3.0, no changes. * Update watch file to use GitHub releases. * Add gbp.conf to use pristine-tar by default. * Recommend icinga2 instead of icinga-core. (closes: #861315) * Update copyright file, changes: - Change Source URL to GitHub repository - Add Alexander Golovko to copyright holders - Add license & copyright for libev, pidfile, uthash & xprint sources - Add license & copyright for Perl bindings * Update command_file path for Icinga 2. * Update branch in gbp.conf & Vcs-Git URL. * Update Homepage URL to GitHub repository. * Update External Commands documentation in README.Debian for Icinga 2. * Update docs file list. * Drop package name from lintian overrides. * Drop unused lintian override for debian-watch-uses-insecure-uri. * Add upstream metadata. Checksums-Sha1: a28dd7ed3dbc01d1fb2f0ac2e6a3e814f688819d 2091 nsca-ng_1.6-1~exp1.dsc 659c7a5d45ac9a5f453060580762f5913330d8bb 233554 nsca-ng_1.6.orig.tar.gz 332d8935d76819dcc63cc73f4a598d501b7741cf 8252 nsca-ng_1.6-1~exp1.debian.tar.xz c44a223c3c973e8c9c3974f13e4b3c5b9b6fb5d1 58588 nsca-ng-client-dbgsym_1.6-1~exp1_amd64.deb b4f3097cb812ebe7aedd3202ddd0bc4761b3a1a1 38092 nsca-ng-client_1.6-1~exp1_amd64.deb 6f387b287744751ee1080fa317d036be5533f341 76768 nsca-ng-server-dbgsym_1.6-1~exp1_amd64.deb f86dc7f0b0042e57f14af4acfc49dc1f62a8c0a1 39632 nsca-ng-server_1.6-1~exp1_amd64.deb e5ffa5e43e859dcf71ea9f45ac4a3fbb104abb32 7182 nsca-ng_1.6-1~exp1_amd64.buildinfo Checksums-Sha256: 3c999f4dd5d1d61f0d4b75eeeaa51d04dbc5a6e724ba46577d3a0051f82fa5ef 2091 nsca-ng_1.6-1~exp1.dsc
Bug#900152: marked as done (nsca-ng: FTBFS against openssl 1.1.1)
Your message dated Tue, 19 Mar 2019 17:49:10 + with message-id and subject line Bug#900152: fixed in nsca-ng 1.5-4 has caused the Debian Bug report #900152, regarding nsca-ng: FTBFS against openssl 1.1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 900152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nsca-ng Version: 1.5-2 Severity: important User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-1.1.1 The new openssl 1.1.1 is currently in experimental [0]. This package failed to build against this new package [1] while it built fine against the openssl version currently in unstable [2]. Could you please have a look? The Error in the testsuite could be due to: 1.1.1~~pre6-1 changelog): | * Increase default security level from 1 to 2. This moves from the 80 bit | security level to the 112 bit securit level and will require 2048 bit RSA | and DHE keys. [0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be [1] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/nsca-ng_1.5-2_amd64-2018-05-01T20%3A31%3A09Z [2] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/nsca-ng_1.5-2_amd64-2018-05-02T18%3A46%3A37Z Sebastian --- End Message --- --- Begin Message --- Source: nsca-ng Source-Version: 1.5-4 We believe that the bug you reported is fixed in the latest version of nsca-ng, 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 900...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated nsca-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Mar 2019 18:32:59 +0100 Source: nsca-ng Binary: nsca-ng-client nsca-ng-client-dbgsym nsca-ng-server nsca-ng-server-dbgsym Architecture: source amd64 Version: 1.5-4 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group Changed-By: Bas Couwenberg Description: nsca-ng-client - Send monitoring commands to NSCA-ng server nsca-ng-server - Monitoring command acceptor Closes: 900152 Changes: nsca-ng (1.5-4) unstable; urgency=medium . * Team upload. * Drop autopkgtest to test installability. * Add lintian override for testsuite-autopkgtest-missing. * Bump Standards-Version to 4.3.0, no changes. * Add upstream patch to fix FTBFS with OpenSSL 1.1.1. (closes: #900152) Checksums-Sha1: f41d043ef82270d955453955e2aae59bd0762596 2046 nsca-ng_1.5-4.dsc 9cb698cd808d47d348fff7174583e4169480da97 7760 nsca-ng_1.5-4.debian.tar.xz 4a3a1a9e9825781f03d209429bea7b31e811725d 58352 nsca-ng-client-dbgsym_1.5-4_amd64.deb b513b37bd9f964bcc5965a41850a3dc63e35a8eb 50456 nsca-ng-client_1.5-4_amd64.deb f2e6f288c760069abe7c0e8cbffadb1923c3a64d 76764 nsca-ng-server-dbgsym_1.5-4_amd64.deb 2283e6a591c7b7e2a41e0e3ae654c50ddbfa0e1a 52508 nsca-ng-server_1.5-4_amd64.deb b20e7700350a9c8b5940cb0ac948911671668684 7102 nsca-ng_1.5-4_amd64.buildinfo Checksums-Sha256: 0e39a90eec1cdb4772a7151a9f536974013ef530c54ae23e789eda4f955766c8 2046 nsca-ng_1.5-4.dsc f30836cd39286ef044d5663804141955c3c177d90a1c213d5a698dc2795875c0 7760 nsca-ng_1.5-4.debian.tar.xz 795242f81e38cc5a878c645c877a010349bccd73108bb8cb76c24d3d6fa75e8b 58352 nsca-ng-client-dbgsym_1.5-4_amd64.deb 291f4a42f3be0feecb28a0133401ab73b88a4788749f114451584f261e6b9f21 50456 nsca-ng-client_1.5-4_amd64.deb a90127b5a78dc2a62381caa90667c323447b9ebf24f4a993282fff14935f87c0 76764 nsca-ng-server-dbgsym_1.5-4_amd64.deb ad5111dba31921ffe6a71daec9460180806b72258f2a8c5629c89a50c806e5ee 52508 nsca-ng-server_1.5-4_amd64.deb 48149470e75826e4801430b02b6b35094b3897dfd8a1f13d0acf7fafc4690ae1 7102 nsca-ng_1.5-4_amd64.buildinfo Files: 4336265564c199b03eff1d26ec47582e 2046 net optional nsca-ng_1.5-4.dsc fc966cdcf67fa2fe4f1dba88d990c7e6 7760 net optional nsca-ng_1.5-4.debian.tar.xz 4f6fcd9ae3423b70ec5d66f46a71a38b 58352 debug optional nsca-ng-client-dbgsym_1.5-4_amd64.deb 8d5278f86a9029a6319b58a329c098d0 50456 net optional nsca-ng-client_1.5-4_amd64.deb
Processed: fixed 915723 in 8u202-b26-1
Processing commands for cont...@bugs.debian.org: > fixed 915723 8u202-b26-1 Bug #915723 [src:openjdk-8] openjdk-8 needs a build dependency preventing build attempts on zero architectures Marked as fixed in versions openjdk-8/8u202-b26-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 915723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920709: marked as done (distcc: fails to upgrade from 'testing': causes dpkg trigger loop)
Your message dated Tue, 19 Mar 2019 17:34:16 + with message-id and subject line Bug#920709: fixed in distcc 3.3.2-8 has caused the Debian Bug report #920709, regarding distcc: fails to upgrade from 'testing': causes dpkg trigger loop 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.) -- 920709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: distcc Version: 3.3.2-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): dpkg: dependency problems prevent processing triggers for distcc: distcc depends on python3; however: Package python3 is not configured yet. dpkg: error processing package distcc (--configure): dependency problems - leaving triggers unprocessed [...] dpkg: dependency problems prevent processing triggers for distcc: distcc depends on python3; however: Package python3 is not configured yet. dpkg: error processing package distcc (--configure): dependency problems - leaving triggers unprocessed dpkg: too many errors, stopping Errors were encountered while processing: distcc distcc distcc distcc [...] distcc distcc distcc distcc Processing was halted because there were too many errors. cheers, Andreas distcc_3.3.2-7.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: distcc Source-Version: 3.3.2-8 We believe that the bug you reported is fixed in the latest version of distcc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Marillat (supplier of updated distcc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Mar 2019 18:14:45 +0100 Source: distcc Binary: distcc distcc-dbgsym distcc-pump distcc-pump-dbgsym distccmon-gnome distccmon-gnome-dbgsym Architecture: source amd64 Version: 3.3.2-8 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Description: distcc - simple distributed compiler client and server distcc-pump - pump mode for distcc a distributed compiler client and server distccmon-gnome - GTK+ monitor for distcc a distributed client and server Closes: 920709 920888 923113 Changes: distcc (3.3.2-8) unstable; urgency=medium . * Back to perl script update-distcc-symlinks as in -5 (Closes: #920709) * Update Danish and Russian translation of the debconf templates (Closes: #923113, #920888) Checksums-Sha1: 29c3311e2532f8a5cdd52ebeee689d0d1c8e9087 1954 distcc_3.3.2-8.dsc f4440766a6b0d4c67ec84f85bb98a88d38bca5c4 45960 distcc_3.3.2-8.debian.tar.xz aa90e757a213eeb1195bb36158571276829fed04 399812 distcc-dbgsym_3.3.2-8_amd64.deb 6a8830277f564793b1fb0fe60d34c60e87884572 93108 distcc-pump-dbgsym_3.3.2-8_amd64.deb 6e3d8db455abe82ffca88260f372707b20af6dab 152104 distcc-pump_3.3.2-8_amd64.deb 4b32671f6fcf27cb7ec88ec384651a0ba66ee7a8 12659 distcc_3.3.2-8_amd64.buildinfo 7c8ddf293d584bbcedf74294c3f60d0bd8de9dd1 208852 distcc_3.3.2-8_amd64.deb c69e0330bbe6b9edfa2199bdbb2b7e7ac5c4c423 77732 distccmon-gnome-dbgsym_3.3.2-8_amd64.deb f802da7932897c03c3dc7a2196b6dba02cf54e5c 68916 distccmon-gnome_3.3.2-8_amd64.deb Checksums-Sha256: d1b73161c928249a05b2f3f17827817b50ad61dd09a7e2607f8731440f6ea0ea 1954 distcc_3.3.2-8.dsc 3e95e8ee0ed7b8a5bd716cf246088da4b10033495e9990fb39951d197d001ace 45960 distcc_3.3.2-8.debian.tar.xz 0c59cbcf0c066e7e975969ffdaa09feb3349f94ee10aba77f297add59498e7f7 399812 distcc-dbgsym_3.3.2-8_amd64.deb b6cbaed2292cb938140bc4e46ebd558a77c7a61442de5bf76ab61eb7cc94296d 93108 distcc-pump-dbgsym_3.3.2-8_amd64.deb 67478b971aca6fd1a9092afa1a07a06323f7eb2ada02c51d08626df0dccafe20 152104 distcc-pump_3.3.2-8_amd64.deb ba9867b0e26727b4aead5e9e333680995577e7a0cb273dcc039ba0892402d6d1 12659 distcc_3.3.2-8_amd64.buildinfo
Processed: found 920709 in 3.3.2-6
Processing commands for cont...@bugs.debian.org: > found 920709 3.3.2-6 Bug #920709 [distcc] distcc: fails to upgrade from 'testing': causes dpkg trigger loop Marked as found in versions distcc/3.3.2-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 920709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925066: lirc: prompting due to modified conffiles which were not modified by the user: /etc/lirc/lirc_options.conf
Package: lirc Version: 0.10.1-5.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#behavior, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." https://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In https://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Setting up lirc (0.10.1-5.1) ... Configuration file '/etc/lirc/lirc_options.conf' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** lirc_options.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package lirc (--configure): end of file on stdin at conffile prompt Setting up python3-distutils (3.7.3~rc1-1) ... Setting up dh-python (3.20190308) ... Processing triggers for libc-bin (2.28-8) ... Errors were encountered while processing: lirc This was observed on an upgrade from stretch to sid. cheers, Andreas lirc_0.10.1-5.1.log.gz Description: application/gzip
Bug#924805: marked as done (python-molotov: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13)
Your message dated Tue, 19 Mar 2019 16:49:11 +
with message-id
and subject line Bug#924805: fixed in python-molotov 1.6-3
has caused the Debian Bug report #924805,
regarding python-molotov: FTBFS: dh_auto_test: pybuild --test --test-pytest -i
python{version} -p 3.7 returned exit code 13
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.)
--
924805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-molotov
Version: 1.6-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYTHONPATH=. dh_auto_test
> I: pybuild base:217: python3.7 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.7.2+, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
> rootdir: /<>, inifile:
> collected 86 items
>
> molotov/tests/test_api.py ...[
> 8%]
> molotov/tests/test_fmwk.py ..[
> 29%]
> molotov/tests/test_listeners.py .. [
> 31%]
> molotov/tests/test_quickstart.py ... [
> 34%]
> molotov/tests/test_run.py .s.[
> 70%]
> molotov/tests/test_session.py F..FF..FF..[
> 83%]
> molotov/tests/test_sharedconsole.py .. [
> 86%]
> molotov/tests/test_sharedcounter.py [
> 90%]
> molotov/tests/test_slave.py sss [
> 94%]
> molotov/tests/test_util.py .
> [100%]
>
> === FAILURES
> ===
> __ TestLoggedClientSession.test_add_listener
> ___
>
> self = testMethod=test_add_listener>
> loop = <_UnixSelectorEventLoop running=False closed=True debug=True>
> console =
> results = {'WORKER': , 'REACHED': ,
> 'RATIO': , 'OK': , 'FAILED': 0>, 'MINUTE_OK': , 'MINUTE_FAILED': }
>
> @async_test
> async def test_add_listener(self, loop, console, results):
> class MyListener(BaseListener):
> def __init__(self):
> self.responses = []
>
> def on_response_received(self, **options):
> self.responses.append(options['response'])
>
> lis = MyListener()
> async with self._get_session(loop, console,
> verbose=2) as session:
> session.eventer.add_listener(lis)
> request = Request()
> binary_body = b''
> > response = Response(body=binary_body)
>
> molotov/tests/test_session.py:32:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> method = 'GET', status = 200, body = b''
>
> def Response(method='GET', status=200, body=b'***'):
> if util.IS_AIOHTTP2:
> response = LoggedClientResponse(method, URL('/'))
> else:
> > response = LoggedClientResponse(method, URL('/'), **_respkw())
> E TypeError: __init__() got an unexpected keyword argument
> 'auto_decompress'
>
> molotov/tests/support.py:155: TypeError
> _ TestLoggedClientSession.test_empty_response
> __
>
> self = testMethod=test_empty_response>
> loop = <_UnixSelectorEventLoop running=False closed=True debug=True>
> console =
> results = {'WORKER': , 'REACHED': ,
> 'RATIO': , 'OK': , 'FAILED': 0>, 'MINUTE_OK': , 'MINUTE_FAILED': }
>
> @async_test
> async def test_empty_response(self, loop, console, results):
> async with self._get_session(loop, console,
> verbose=2) as session:
> request = Request()
> binary_body = b''
> > response = Response(body=binary_body)
>
> molotov/tests/test_session.py:46:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> method = 'GET', status = 200, body = b''
>
> def Response(method='GET', status=200, body=b'***'):
> if util.IS_AIOHTTP2:
> response = LoggedClientResponse(method, URL('/'))
Bug#918578: Just ping this bug
Just ping this bug since even if a fix would be uploaded now a fixed package will not reach testing before the autoremoval would have removed the package. Andreas. -- http://fam-tille.de
Bug#924697: marked as done (elpa-cider: broken by leiningen 2.9.0)
Your message dated Tue, 19 Mar 2019 16:04:04 + with message-id and subject line Bug#924697: fixed in cider 0.19.0+dfsg-2 has caused the Debian Bug report #924697, regarding elpa-cider: broken by leiningen 2.9.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 924697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-cider Version: 0.19.0+dfsg-1 Severity: grave Tags: sid patch upstream X-debbugs-cc: pkg-clojure-maintain...@lists.alioth.debian.org Control: forwarded -1 https://github.com/clojure-emacs/cider/issues/2581 Hello, CIDER crashes against leiningen 2.9.0, which is now in sid. Cherry-picking upstream commit a48af155d8acf64e7c3025146027ef2d62f1cc2e fixes the problem, and the test suite passes, though that commit does cause CIDER to use cider-middleware 0.21.0, which is somewhat uncomfortable. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: cider Source-Version: 0.19.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of cider, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated cider package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Mar 2019 08:49:20 -0700 Source: cider Architecture: source Version: 0.19.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Emacs addons team Changed-By: Sean Whitton Closes: 924697 Changes: cider (0.19.0+dfsg-2) unstable; urgency=medium . * Cherry pick upstream commit a48af155d8acf64e7c3025146027ef2d62f1cc2e (Closes: #924697). Checksums-Sha1: 83a88bc2a67c34883b320aeddb3a718510dc00a9 2266 cider_0.19.0+dfsg-2.dsc d3fb110edcc21d2d89aeec7b264334186b3c7052 8400 cider_0.19.0+dfsg-2.debian.tar.xz Checksums-Sha256: 9350b8500bf0282e7b022e8a747d00ea51c21c8db7a1cf631e1b759c1113138e 2266 cider_0.19.0+dfsg-2.dsc 3c46e93160ad3ce05634f40404e2c91eed8900acc92c07c957c25f6b2dc7f0ce 8400 cider_0.19.0+dfsg-2.debian.tar.xz Files: ef9578bbc5c2101b52e2c01e06a94b18 2266 lisp optional cider_0.19.0+dfsg-2.dsc f45bc71748628a6a33d86f364d08a03b 8400 lisp optional cider_0.19.0+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlyRD6oACgkQaVt65L8G YkAZhw/9HKxq94F+2V8+RYZit2Fk8QvWmRrnEqccCzZNSzZUv2pHi4TLAC+cvPTp 9nXfrSiMK4KEOE8Tyqv7s2n2ghlNEa2VY33MH8Qa/N6sN4uZsphPiajmKFcoKxgW HeK9G3BFpzvQgXclh/DmPlPmmA/YWVMZkjm8ObsHki4vDPR8/kx7f80qV9fnJZBp v8KQhnS1hggZIRwajfKvMGRvwDukNAHUUdPjCQhLfVsE+xoPea10fn/JdPidc198 e8L+uLzJhXZdrCpTnUACOhlZtj3lNC9ezDcdBQzZMQ2yJQr+B1m1bQrrh6DeoZSD YneqtDqLOJib3QvCnFsRkIrUgsqRAYUXwrFexbVsfNBvb4Tbs5IwRjvljOkqzdOj YMNfPQuML+ZZpV40r7iXfLWKJAKl1PAEbAdP2XY6s6LE9g7YXM6vvW2xYQctoGuF yhzq/R74d35RfT59/sarkRsZwcY9uG6Zal3GgxOiI6QaHMRcWVjWrxyCVji/30r8 G0gA0EKxpiItVElhwo3b2k++G2yFEzc+gu1mIb/a/1MH2jCuUq3iyJso90YZcr3M LMG6uJzoacXCqL00mIMxU071EqREJ5rb0Qf3M0oW5qcOfXTA9VcZgaZpaIhUAhpI MhRrm7Qow0PHF8R6xOVs1YMxV7HZ0P24kx200hmGC/hyreUjfZQ= =C6Yj -END PGP SIGNATURE End Message ---
Bug#923012: marked as done (squirrel3: FTBFS (Could not import extension sphinx.ext.pngmath))
Your message dated Tue, 19 Mar 2019 16:04:12 +
with message-id
and subject line Bug#923012: fixed in squirrel3 3.1-6
has caused the Debian Bug report #923012,
regarding squirrel3: FTBFS (Could not import extension sphinx.ext.pngmath)
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.)
--
923012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:squirrel3
Version: 3.1-5
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
dh_autoreconf -a
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=cmake -- \
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu \
-DINSTALL_INC_DIR=include/squirrel3 \
-DDISABLE_STATIC="" -DLONG_OUTPUT_NAMES=""
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu -DINSTALL_INC_DIR=include/squirrel3
-DDISABLE_STATIC= -DLONG_OUTPUT_NAMES= ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
DISABLE_STATIC
LONG_OUTPUT_NAMES
-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
dh_auto_build -a
cd obj-x86_64-linux-gnu && make -j1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start
/<>/obj-x86_64-linux-gnu/CMakeFiles
/<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make -f squirrel/CMakeFiles/squirrel.dir/build.make
squirrel/CMakeFiles/squirrel.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends
"Unix Makefiles" /<> /<>/squirrel
/<>/obj-x86_64-linux-gnu
/<>/obj-x86_64-linux-gnu/squirrel
/<>/obj-x86_64-linux-gnu/squirrel/CMakeFiles/squirrel.dir/DependInfo.cmake
--color=
Scanning dependencies of target squirrel
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f squirrel/CMakeFiles/squirrel.dir/build.make
squirrel/CMakeFiles/squirrel.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 4%] Building CXX object squirrel/CMakeFiles/squirrel.dir/sqapi.cpp.o
cd /<>/obj-x86_64-linux-gnu/squirrel && /usr/bin/c++ -D_SQ64
-Dsquirrel_EXPORTS -I/<>/include -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -pedantic -fno-exceptions -fno-strict-aliasing
-fno-rtti -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -fno-rtti -std=c++0x -fPIC
-fno-exceptions -fno-strict-aliasing -Wall -Wextra -pedantic -Wcast-qual -o
CMakeFiles/squirrel.dir/sqapi.cpp.o -c /<>/squirrel/sqapi.cpp
/<>/squirrel/sqapi.cpp: In function 'SQRESULT
sq_setdelegate(HSQUIRRELVM, SQInteger)':
/<>/squirrel/sqapi.cpp:961:13: warning: this 'if' clause does not
guard... [-Wmisleading-indentation]
if(!_table(self)->SetDelegate(_table(mt))) return sq_throwerror(v,
_SC("delagate cycle")); v->Pop();}
^~
/<>/squirrel/sqapi.cpp:961:104: note: ...this statement, but the
latter is misleadingly indented as if it were guarded by the 'if'
Bug#925051: diffoscope: FTBFS in stretch (failing tests)
Package: src:diffoscope Version: 78 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch but it failed: [...] debian/rules build-indep dh build-indep --with python3 --with bash-completion --buildsystem=pybuild dh_testdir -i -O--buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:184: python3.5 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' register-python-argcomplete diffoscope > debian/diffoscope.bash-completion rst2man debian/diffoscope.1.rst debian/diffoscope.1 dh_auto_build -O--buildsystem=pybuild I: pybuild base:184: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/main.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/excludes.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/locale.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/tempfiles.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/difference.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/progress.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/changes.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/exc.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/tools.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/config.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/logging.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/profiling.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/external_tools.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope copying diffoscope/diff.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope creating /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/macho.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/xz.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/fonts.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/binary.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/rpm_fallback.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/debian.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/debian_fallback.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/zip.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/haskell.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/tar.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/openssh.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/sqlite.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/ps.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/rust.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/ipk.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/ar.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/gettext.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/fsimage.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/missing_file.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/gzip.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/ppu.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/png.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/llvm.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/mono.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/image.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/javascript.py -> /<>/.pybuild/pythonX.Y_3.5/build/diffoscope/comparators copying diffoscope/comparators/device.py ->
Processed: tagging 924697
Processing commands for cont...@bugs.debian.org: > tags 924697 + buster Bug #924697 [elpa-cider] elpa-cider: broken by leiningen 2.9.0 Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 924697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 921599 is serious
Processing commands for cont...@bugs.debian.org: > #this is an important feature not limited to the python bindings > severity 921599 serious Bug #921599 [src:mariadb-10.3] python-mysqldb: always connects to localhost ignoring host entry in option file Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 921599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924495: marked as done (shimdandy: FTBFS (Could not resolve dependencies for project org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0))
Your message dated Tue, 19 Mar 2019 15:19:26 + with message-id and subject line Bug#924495: fixed in shimdandy 1.2.0-3 has caused the Debian Bug report #924495, regarding shimdandy: FTBFS (Could not resolve dependencies for project org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 924495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:shimdandy Version: 1.2.0-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibshimdandy-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] shimdandy-api [jar] [INFO] shimdandy-impl [jar] [INFO] shimdandy-parent [pom] [INFO] [INFO] ---< org.projectodd.shimdandy:shimdandy-api >--- [INFO] Building shimdandy-api 1.2.0 [1/3] [INFO] [ jar ]- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ shimdandy-api --- [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /<>/api/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ shimdandy-api --- [INFO] Changes detected - recompiling the module! [WARNING] File encoding has not been set, using platform encoding ANSI_X3.4-1968, i.e. build is platform dependent! [INFO] Compiling 1 source file to /<>/api/target/classes [INFO] /<>/api/src/main/java/org/projectodd/shimdandy/ClojureRuntimeShim.java: /<>/api/src/main/java/org/projectodd/shimdandy/ClojureRuntimeShim.java uses or overrides a deprecated API. [INFO] /<>/api/src/main/java/org/projectodd/shimdandy/ClojureRuntimeShim.java: Recompile with -Xlint:deprecation for details. [INFO] [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ shimdandy-api --- [INFO] Not copying test resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ shimdandy-api --- [INFO] Not compiling test sources [INFO] [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ shimdandy-api --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.1.1:jar (default-jar) @ shimdandy-api --- [INFO] Building jar: /<>/api/target/shimdandy-api-1.2.0.jar [INFO] [INFO] --< org.projectodd.shimdandy:shimdandy-impl >--- [INFO] Building shimdandy-impl 1.2.0 [2/3] [INFO] [ jar ]- [WARNING] The POM for org.clojure:clojure:jar:1.9.x is missing, no dependency information available [INFO] [INFO] Reactor
Processed: tagging 919481
Processing commands for cont...@bugs.debian.org: > tags 919481 - pending Bug #919481 [src:guile-2.0] guile-2.0 ftbfs on ppc64el Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 919481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884463: marked as done (passenger: CVE-2017-16355: arbitrary file read)
Your message dated Tue, 19 Mar 2019 14:39:17 + with message-id and subject line Bug#884463: fixed in passenger 5.0.30-1.1 has caused the Debian Bug report #884463, regarding passenger: CVE-2017-16355: arbitrary file read 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.) -- 884463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: passenger Version: 5.0.30-1 Severity: important Tags: patch security upstream fixed-upstrream Hi, the following vulnerability was published for passenger. CVE-2017-16355[0]: | In agent/Core/SpawningKit/Spawner.h in Phusion Passenger 5.1.10 (fixed | in Passenger Open Source 5.1.11 and Passenger Enterprise 5.1.10), if | Passenger is running as root, it is possible to list the contents of | arbitrary files on a system by symlinking a file named REVISION from | the application root folder to a file of choice and querying | passenger-status --show=xml. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-16355 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16355 [1] https://blog.phusion.nl/2017/10/13/passenger-security-advisory-5-1-11/ [2] https://github.com/phusion/passenger/commit/4043718264095cde6623c2cbe8c644541036d7bf Regards, Salvatore --- End Message --- --- Begin Message --- Source: passenger Source-Version: 5.0.30-1.1 We believe that the bug you reported is fixed in the latest version of passenger, 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 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated passenger 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, 16 Mar 2019 08:54:26 +0100 Source: passenger Architecture: source Version: 5.0.30-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Salvatore Bonaccorso Closes: 884463 921767 Changes: passenger (5.0.30-1.1) unstable; urgency=medium . * Non-maintainer upload. * arbitrary file read via REVISION symlink (CVE-2017-16355) (Closes: #884463) * Fix privilege escalation in the Nginx module (CVE-2018-12029) (Closes: #921767) Checksums-Sha1: f3c73ccc2e44ff6cb2b87360f8d01d5047f8e902 2736 passenger_5.0.30-1.1.dsc 432fe5d87acb14a99bbfad794582d7430489d401 17588 passenger_5.0.30-1.1.debian.tar.xz d76b3b5d7c0723362f66faa7395f5ef9a7435914 7064 passenger_5.0.30-1.1_source.buildinfo Checksums-Sha256: 1dd5d8997cfb0d174b80f869cdc49ecad358ee6eceab1b6f689b5462c99a4c44 2736 passenger_5.0.30-1.1.dsc f347829a1dbfbf470ba8d6ce2e3f4b96c26a087d1a4cedd7393ac0c6bbdd8c48 17588 passenger_5.0.30-1.1.debian.tar.xz d7aafa222fb1161e3b50cf28e3dbdf7446823090a6f90ebdfdd7b89ae4696ba9 7064 passenger_5.0.30-1.1_source.buildinfo Files: 16cda8efa5591927b3c79413e58a2bb9 2736 ruby optional passenger_5.0.30-1.1.dsc 1bc06787da90b78e5ef5abf09492ff7e 17588 ruby optional passenger_5.0.30-1.1.debian.tar.xz 8034b43d1abbedffa82bab75c8e4738a 7064 ruby optional passenger_5.0.30-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlyMrChfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EeL4P/ioZCVTaLXA6SFJ5uujTvNmqxGQUpi6C ojl+F0d+E/VxYay7MNmcwBCUidWAzmNKwgZJJt6hvD75OcCMBg9jKlR05s+HeYs+ AixRJpPhfYM3vfkw+TX9w6vckfw71Ui8POQjRDyL0vQ1w+6wv/zHAjqEsJgAOTZ3 2kEbCsU4he9h9TGVfurn/8xCp+I4VBT+04LVGg5sozlyiPPSqif+xEPb9bcKeU6h ZFQP5PnCOsqIT2EFncHSUas+jRoGNEqQNWu3Hy+h26ioXrwB9IqB1M8Pq1cYRodU CkgLG4FXBzff0Fnoli9vI4lqbNAKofGIkyviHR0k1Gb74rilPGgq7yf7Lk9vG/Ec BbNh+nAU5hMWGuBmkKncidDHrUFc0QDj6xMfRKNRxgZLJ2HF88DHJwaOiaWoY25+ 8bJR78ZRxyWYtEG377R9pLYUZbee2iNcoxjrvSeCump4HUGX7arsuwDRAJECDcsl YLPNV2QqjT19Fp4+6NUjflZiAutyTQD1X7lwlegW2s3J6FT5DSYNljWBGgntk17G fTqMu9y7FBM00X+rp4XiuMXebNSC/+ew40FqVHVfrd3kiMEHYWbD6hE9ExJwiXE1
Bug#919481: Fix for RC #919481
Package: src:guile-2.0 Version: 2.0.13+1-5 Control: tags -1 patch pending -- I forgot to mention, the issue now appears because schroots seem to have all locale created which was not the case before and the tests were just skipped as UNRESOLVED (see the build log history). Now they run.. and fail, but the issue should be there since some time. F. pgpfq7F8qBBy0.pgp Description: PGP signature
Processed: Re: Fix for RC #919481
Processing control commands: > tags -1 patch pending Bug #919481 [src:guile-2.0] guile-2.0 ftbfs on ppc64el Added tag(s) patch and pending. -- 919481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924916: RM: python-django-openstack-auth -- RoM; provided by python3-django-horizon
On 2019-03-18 15:29, Thomas Goirand wrote: > On 3/18/19 12:56 PM, Andreas Beckmann wrote: >> I'm again investigating openstack-dashboard related upgrade failures. > Indeed, django-openstack-auth has been removed upstream and included > directly in django-horizon. I'm not sure what's the best way to get > completely rid of it on upgrades and get Horizon the best way > possible... I thought I did well, but you're telling me the opposite. > So, any advice would be welcome. I just reran the openstack-dashboard upgrade test locally which now succeeded. The removal from sid (which propagated to testing already) seems to have been sufficient to no longer give apt the opportunity to take a wrong decision :-) Investigating (0) python3-django-horizon:amd64 < none -> 3:14.0.2-2 @un uN Ib > Broken python3-django-horizon:amd64 Conflicts on python-django-horizon:amd64 < 3:10.0.1-1 @ii mK > Considering python-django-horizon:amd64 -3 as a solution to python3-django-horizon:amd64 0 Added python-django-horizon:amd64 to the remove list Broken python3-django-horizon:amd64 Conflicts on python-django-openstack-auth:amd64 < 2.4.1-2 @ii mK > Considering python-django-openstack-auth:amd64 -2 as a solution to python3-django-horizon:amd64 0 Added python-django-openstack-auth:amd64 to the remove list Fixing python3-django-horizon:amd64 via remove of python-django-horizon:amd64 Fixing python3-django-horizon:amd64 via remove of python-django-openstack-auth:amd64 Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: python-django-horizon python-django-openstack-auth The following NEW packages will be installed: [...] The following packages will be upgraded: [...] I think that looks fine now :-) Waiting for the rdepends to be tested ... Andreas
Bug#919481: Fix for RC #919481
Hi, this bug is actually not ppc64el specific, I could also reproduce it on barriere.d.o (amd64). That said, it seems to be an encoding issue. In i18n tests, some test fail because of strings not being lexicographically equal, specifically due to the nonbreaking space. The tests convert values to strings which insert a "locale-thousands-separator" which, in this case, is a non-breaking space. This string is compared to the hardcoded expected result which contains a standard space (UTF8 hex. 20) As the file is UTF8, this patch replace the bad space with the UTF8 non-breaking space equivalent hex. C2 A0 . Thanks for reviewing the attached patch. F. Description: Fix unicode non-breaking spaces In i18n tests, some test fail because of non-breaking spaces not being matched. The tests convert values to strings in fr_FR.iso88591 which insert a "locale-thousands-separator" which, in this case, is a non-breaking space. This string is compared to the hardcoded expected result which contains a standard space (UTF8 hex. 20) As the file is UTF8, this patch replace the bad space with the UTF8 non-breaking space equivalent hex. C2 A0 . Author: Frédéric Bonnard --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ Index: guile-2.0-2.0.13+1/test-suite/tests/i18n.test === --- guile-2.0-2.0.13+1.orig/test-suite/tests/i18n.test 2016-10-22 22:09:34.0 +0200 +++ guile-2.0-2.0.13+1/test-suite/tests/i18n.test 2019-03-19 13:36:43.022766801 +0100 @@ -514,19 +514,19 @@ (under-french-locale-or-unresolved (lambda () (let ((fr (make-locale LC_ALL %french-locale-name))) - (string=? "123 456" (number->locale-string 123456 #t fr)) + (string=? "123 456" (number->locale-string 123456 #t fr)) (pass-if "fraction" (under-french-locale-or-unresolved (lambda () (let ((fr (make-locale LC_ALL %french-locale-name))) - (string=? "1 234,567" (number->locale-string 1234.567 #t fr)) + (string=? "1 234,567" (number->locale-string 1234.567 #t fr)) (pass-if "fraction, 1 digit" (under-french-locale-or-unresolved (lambda () (let ((fr (make-locale LC_ALL %french-locale-name))) - (string=? "1 234,5" + (string=? "1 234,5" (number->locale-string 1234.567 1 fr (with-test-prefix "format ~h" @@ -542,7 +542,7 @@ (lambda () (if (null? (locale-digit-grouping %french-locale)) (throw 'unresolved) - (string=? "12 345,6789" + (string=? "12 345,6789" (format #f "~:h" 12345.6789 %french-locale))) (with-test-prefix "English" @@ -564,12 +564,12 @@ (under-french-locale-or-unresolved (lambda () (let ((fr (make-locale LC_ALL %french-locale-name))) - (string=? "123 456 +EUR" + (string=? "123 456 +EUR" (monetary-amount->locale-string 123456 #f fr)) (pass-if "fraction" (under-french-locale-or-unresolved (lambda () (let ((fr (make-locale LC_ALL %french-locale-name))) - (string=? "1 234,56 EUR " + (string=? "1 234,56 EUR " (monetary-amount->locale-string 1234.567 #t fr pgpWtSvgdprWz.pgp Description: PGP signature
Bug#925020: scilab terminates immediately when started from the desktop
Package: src:scilab Version: 6.0.1-7 Severity: serious Tags: sid buster scilab terminates immediately when started from the desktop, while starting from a terminal works. patch taken from upstream, at http://launchpadlibrarian.net/415737336/scilab_6.0.1-7build2_6.0.1-7ubuntu1.diff.gz
Bug#924495: Bug #924495 in shimdandy marked as pending
Control: tag -1 pending Hello, Bug #924495 in shimdandy 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/shimdandy/commit/193cb48b5d54971e5373ec5924a6882d76103e23 Build with Clojure 1.10 (Closes: #924495) New upstream version Signed-off-by: Tom Marble (this message was generated automatically) -- Greetings https://bugs.debian.org/924495
Processed: Bug #924495 in shimdandy marked as pending
Processing control commands: > tag -1 pending Bug #924495 [src:shimdandy] shimdandy: FTBFS (Could not resolve dependencies for project org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0) Added tag(s) pending. -- 924495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#924973: g3dviewer: 'debian/rules clean' after build causes removal of mkinstalldirs
Processing control commands: > severity -1 important Bug #924973 [g3dviewer] g3dviewer: 'debian/rules clean' after build causes removal of mkinstalldirs Severity set to 'important' from 'serious' > block -1 with 670796 Bug #924973 [g3dviewer] g3dviewer: 'debian/rules clean' after build causes removal of mkinstalldirs 924973 was not blocked by any bugs. 924973 was not blocking any bugs. Added blocking bug(s) of 924973: 670796 -- 924973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924973: g3dviewer: 'debian/rules clean' after build causes removal of mkinstalldirs
Control: severity -1 important Control: block -1 with 670796 On 2019-03-19 12:00, Sven Eckelmann wrote: > Looks like dh-autoreconf (used by debhelper by default) bug #670796. Also Thanks. Andreas
Bug#924973: g3dviewer: 'debian/rules clean' after build causes removal of mkinstalldirs
On Tuesday, 19 March 2019 11:30:07 CET Andreas Beckmann wrote: [...] > g3dviewer/experimental fails to build twice in a row. The first build > succeeds, but during subsequent debian/rules clean the following files > disappear: [...] > causing the second build to fail: > > [...] > Making install in po > make[4]: Entering directory '/build/g3dviewer-0.2.99.5~svn130/po' > if test -r ".././mkinstalldirs"; then \ > .././mkinstalldirs > /build/g3dviewer-0.2.99.5~svn130/debian/g3dviewer/usr/share; \ > else \ > /bin/bash ../mkinstalldirs > /build/g3dviewer-0.2.99.5~svn130/debian/g3dviewer/usr/share; \ > fi > /bin/bash: ../mkinstalldirs: No such file or directory > make[4]: *** [Makefile:136: install-data-yes] Error 127 > make[4]: Leaving directory '/build/g3dviewer-0.2.99.5~svn130/po' > [...] > > There is no explicit deletion command being shown during make distclean. > Full buildlog attached. Looks like dh-autoreconf (used by debhelper by default) bug #670796. Also disabling it doesn't really work here because we need the autoreconf stuff - and using --without autoreconf and then calling it explicitly in a subdirectory caused #924756. Kind regards, Sven [1] https://bugs.debian.org/670796 signature.asc Description: This is a digitally signed message part.
Bug#924977: Building devscripts messes with $HOME
Package: devscripts Version: 2.19.3 Severity: grave Running `dpkg-buildpackage` in a devscripts git checkout does weird things to $HOME. I don't think it's deleting any files (or else I would have opened this as critical), but this needs some attention. The first symptom is that there's temporary files in $HOME after building/trying to build: drwxrwxr-x 6 cbe cbe 4096 Mär 19 11:44 foo-0.0/ -rw-rw-r-- 1 cbe cbe 301 Mär 19 11:44 foo-0.0.tar.gz -rw-rw-r-- 1 cbe cbe 833 Mär 19 11:44 foo-0.0.tar.gz.asc drwxrwxr-x 6 cbe cbe 4096 Mär 19 11:44 foo-1.0/ -rw-rw-r-- 1 cbe cbe 301 Mär 19 11:44 foo-1.0.tar.gz -rw-rw-r-- 1 cbe cbe 833 Mär 19 11:44 foo-1.0.tar.gz.asc drwxrwxr-x 6 cbe cbe 4096 Mär 19 11:44 foo-2.0/ -rw-rw-r-- 1 cbe cbe 301 Mär 19 11:44 foo-2.0.tar.gz -rw-rw-r-- 1 cbe cbe 833 Mär 19 11:44 foo-2.0.tar.gz.asc One build attempt showed a lot of this on the console at which point I hit ^C: find: ‘./.wine/dosdevices/z:/sys/class/thermal/thermal_zone2/device/driver/LNXTHERM:01/thermal_zone/cdev7/device/physical_node/node0/cpu7/firmware_node/subsystem/devices/device:2d/device:30/physical_node/device/driver/2-1.2/2-1.2:1.2/subsystem/devices/2-1/port/firmware_node/device:23/physical_node/device/2-1.1:1.0/0003:413C:2003.0001/driver/0003:1050:0407.000C/subsystem/devices/0003:413C:3012.0004/input/input2/mouse0/subsystem/input9/device/device/subsystem/devices/:00:1f.2/ata2/ata_port/ata2/subsystem/ata1/device/host0/target0:0:0/0:0:0:0/block/sda/bdi/subsystem/7:0/subsystem’: Zu viele Ebenen aus symbolischen Links find: ‘./.wine/dosdevices/z:/sys/class/thermal/thermal_zone2/device/driver/LNXTHERM:01/thermal_zone/cdev7/device/physical_node/node0/cpu7/firmware_node/subsystem/devices/device:2d/device:30/physical_node/device/driver/2-1.2/2-1.2:1.2/subsystem/devices/2-1/port/firmware_node/device:23/physical_node/device/2-1.1:1.0/0003:413C:2003.0001/driver/0003:1050:0407.000C/subsystem/devices/0003:413C:3012.0004/input/input2/mouse0/subsystem/input9/device/device/subsystem/devices/:00:1f.2/ata2/ata_port/ata2/subsystem/ata1/device/host0/target0:0:0/0:0:0:0/block/sda/bdi/subsystem/253:6/subsystem’: Zu viele Ebenen aus symbolischen Links I think the problem is around the uscan test: 127.0.0.1 - - [19/Mar/2019 11:54:41] code 404, message File not found 127.0.0.1 - - [19/Mar/2019 11:54:41] "HEAD /foo-1.tgz.sign HTTP/1.1" 404 - testGitHead mktemp: konnte das Verzeichnis nicht mittels Schablone „/home/cbe/tmp/tmp.CPAf1zk7Db/tmp.XX“ erstellen: Datei oder Verzeichnis nicht gefunden mkdir: das Verzeichnis „/foo“ kann nicht angelegt werden: Keine Berechtigung mkdir: das Verzeichnis „/foo“ kann nicht angelegt werden: Keine Berechtigung mkdir: das Verzeichnis „/repo“ kann nicht angelegt werden: Keine Berechtigung ./test_uscan_git: 36: cd: can't cd to /repo Bestehendes Git-Repository in /home/cbe/debian/devscripts/devscripts/test/.git/ neuinitialisiert Auf Branch master Unversionierte Dateien: Makefile bashisms/ [...] test_uscan_online uscan/ nichts zum Commit vorgemerkt, aber es gibt unversionierte Dateien [master 158990d] Releasing 1.0 2 files changed, 3 insertions(+) fatal: Tag 'v1.0' existiert bereits [master a406494] Releasing 2.0 2 files changed, 3 insertions(+) fatal: Tag 'v2.0' existiert bereits ./test_uscan_git: 73: eval: cannot create /foo/debian/watch: Directory nonexistent ./test_uscan_git: 79: eval: cannot create /foo/debian/changelog: Directory nonexistent ./test_uscan_git: 86: eval: cannot create /foo/debian/source/format: Directory nonexistent cp: reguläre Datei '/foo/debian/upstream/signing-key.asc' kann nicht angelegt werden: Datei oder Verzeichnis nicht gefunden ./test_uscan_git: 103: eval: cannot create /foo/debian/watch: Directory nonexistent ./test_uscan_git: 120: cd: can't cd to /foo testExcludeXZ testRepackZip_XZ ok 147 ok 148 [...] testSuffix Ran 2 tests. FAILED (failures=1) make[3]: *** [Makefile:24: test_debrepro.test] Fehler 1 make[3]: *** Es wird auf noch nicht beendete Prozesse gewartet gpgv: Signatur vom Di 19 Mär 2019 11:54:42 CET gpgv:mittels RSA-Schlüssel CF218F0E7EABF584B7E20402C77E2D6872543FAF gpgv: Korrekte Signatur von "uscan test key (no secret) " 127.0.0.1 - - [19/Mar/2019 11:54:43] "GET / HTTP/1.1" 200 - uscan: Newest version of foo on remote site is 1, local version is 0+dfsg1 (mangled local version is 0) uscan:=> Newer package available from http://localhost:46747/foo-1.tar.gz 127.0.0.1 - - [19/Mar/2019 11:54:43] "GET /foo-1.tar.gz HTTP/1.1" 200 - 127.0.0.1 - - [19/Mar/2019 11:54:43] code 404, message File not found 127.0.0.1 - - [19/Mar/2019 11:54:43] "HEAD /foo-1.tar.gz.asc HTTP/1.1" 404 - 127.0.0.1 - - [19/Mar/2019 11:54:43] code 404, message File not found 127.0.0.1 - - [19/Mar/2019 11:54:43] "HEAD /foo-1.tar.gz.gpg HTTP/1.1" 404 - 127.0.0.1 - - [19/Mar/2019 11:54:43] code 404, message File not found 127.0.0.1 - - [19/Mar/2019 11:54:43] "HEAD /foo-1.tar.gz.pgp HTTP/1.1" 404 -
Bug#867681: fixed in software-properties 0.96.24.32.7-1
Hi, On Sun, 27 Jan 2019 15:35:35 + Julian Andres Klode wrote: > Source: software-properties > Binary: python3-software-properties software-properties-common > software-properties-gtk software-properties-kde > Architecture: source > Version: 0.96.24.32.7-1 > Distribution: experimental Do you upload it to unstable, too? For buster release, this is one of the RC bugs. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#924972: marked as done (openjdk-11-jre-dcevm: Incompatible with openjdk/11.0.3+1-1 (Error occurred during initialization of VM))
Your message dated Tue, 19 Mar 2019 11:06:42 + with message-id and subject line Bug#924972: fixed in openjdk-11-jre-dcevm 11.0.3+1-1 has caused the Debian Bug report #924972, regarding openjdk-11-jre-dcevm: Incompatible with openjdk/11.0.3+1-1 (Error occurred during initialization of VM) 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.) -- 924972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-11-jre-dcevm Version: 11.0.1+8-1 Severity: grave Justification: renders package unusable Forwarded: https://github.com/HotswapProjects/openjdk-jdk11u-dcevm/issues/2 openjdk-11-jre-dcevm doesn't work with openjdk-11/11.0.3+1-1, any invocation of 'java -dcevm' returns the following error: $ java -dcevm Test Error occurred during initialization of VM Unable to load native library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: symbol JVM_InitClassName version SUNWprivate_1.1 not defined in file libjvm.so with link time reference openjdk-11-jre-dcevm needs to be aligned to the same openjdk-11 version (11.0.3+1) Emmanuel Bourg --- End Message --- --- Begin Message --- Source: openjdk-11-jre-dcevm Source-Version: 11.0.3+1-1 We believe that the bug you reported is fixed in the latest version of openjdk-11-jre-dcevm, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated openjdk-11-jre-dcevm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Mar 2019 11:13:57 +0100 Source: openjdk-11-jre-dcevm Architecture: source Version: 11.0.3+1-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 924972 Changes: openjdk-11-jre-dcevm (11.0.3+1-1) unstable; urgency=medium . * New upstream release (Closes: #924972) Checksums-Sha1: b39c55dd86d5ba2391880ef264f8dc23407af2a4 2273 openjdk-11-jre-dcevm_11.0.3+1-1.dsc 6f64bfb48c76bf496179a5a8ad31906b08c97ef8 16983448 openjdk-11-jre-dcevm_11.0.3+1.orig.tar.xz 9e852c4632f6bd2b022fa7baaa33ca8e9f36583e 5632 openjdk-11-jre-dcevm_11.0.3+1-1.debian.tar.xz 3244d1ebcd9e0a9d63441dd34c7f09da9100941e 11652 openjdk-11-jre-dcevm_11.0.3+1-1_source.buildinfo Checksums-Sha256: 46294b8930396984f953e4698c30b92b4ab68ee61247a3d25ab04b88177efb21 2273 openjdk-11-jre-dcevm_11.0.3+1-1.dsc 74214d6f9f59ccda7e7ffa2a8abad62b123a7a5ee974e5f6ee04b8de6563c84b 16983448 openjdk-11-jre-dcevm_11.0.3+1.orig.tar.xz 4010c4ed77d2c18ae887b75d382eafff039ddc25db76d8a6672601dd4fb0b130 5632 openjdk-11-jre-dcevm_11.0.3+1-1.debian.tar.xz f7cb4249cb28373fab68780626ccfd56e28c70ffb8b22ea01f7bee7e417d49b1 11652 openjdk-11-jre-dcevm_11.0.3+1-1_source.buildinfo Files: d1bc4c49105b008044e1dc9d28495873 2273 java optional openjdk-11-jre-dcevm_11.0.3+1-1.dsc 897d6e4f002bdd67b7063ca3dae38735 16983448 java optional openjdk-11-jre-dcevm_11.0.3+1.orig.tar.xz 02fd9d72ad9d0144e222a9bc2e4dfccf 5632 java optional openjdk-11-jre-dcevm_11.0.3+1-1.debian.tar.xz c98fdd062db5176fd8f2465ddb9c8eb2 11652 java optional openjdk-11-jre-dcevm_11.0.3+1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlyQw0kSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsedsQAISEQciNYVeTkWZEgbGKUgzhW5bd+eb/ 2oaA8PEqiEO+JYrst2Bv/nmvs3vsv6ZRnjS3eO7140W+OjaB6U00naF24GPE8apv 1T+rN//5haz1eCnJUcCAmHRzVDGx+cBfIldrJWgkXa2P5okz2XZhl0TwHg8BehvM +BwVWhAk1CE+LTvUBzq4LZrzXq/y1oPsOJmfjZZfY1Kg7p1Lh7w5Xrr6u95cqdmC uYr2HUEGlfBIITyBFLYEQgsvBz+9kAviuH8DF1EL3GOGn2QUgUPLFrrsgnYnM6p4 hIHTir9eBqxRv1/d6FWjs80og27z/WRckeCAGKjOWnkRdEk8PEFOzLrmxK/Nc2UA 6DZ4D63fjw6h/MFC1yiPP2YpvxL32oip4E6x5gTkIoVWo9q2fYxJhVwmftat8Vbr oj2NLNy2sGQFiRct2zZdh+VdUto6ZzYnL5fXRym1fj27TBYvpq0Fmu0AvEGTrBHj r6Bl57+ovz9gYQI53em0q2bLr45rXb8xjTKEMnTPmKNwMu+0toV5iJ/YhU5mREvW noAIporCALii5VoDzLKBwypgP6RPvTMxK1bg+HvYWNIajZ2TEnMiBVWwnGUsBDdH VYOIJSX6JhUm4TjwhSsVxV5VtVlpCwepRazK1SZnBwyZ6MxIaEj3EtphYV/qgw5v AIyfGZ1LToWU =k6cI -END PGP SIGNATURE End Message ---
Bug#924976: python3-celery: Incompatible with python3-redis/python3-kombu versions
Package: python3-celery Version: 4.2.1-3 Severity: grave Justification: renders package unusable Should be fixed in the upstream, but current versions in repository are incompatible. https://github.com/celery/celery/issues/5175 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.0.1-1-MANJARO (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages python3-celery depends on: ii python33.7.2-1 ii python3-billiard 3.6.0.0-1 ii python3-dateutil 2.7.3-3 ii python3-ephem 3.7.6.0-7+b1 ii python3-kombu 4.2.1-2 ii python3-memcache 1.59-1 ii python3-pkg-resources 40.8.0-1 ii python3-pyparsing 2.2.0+dfsg1-2 ii python3-tz 2018.9-1 python3-celery recommends no packages. Versions of packages python3-celery suggests: pn python-celery-doc ii python3-redis 3.2.0-2 ii python3-sqlalchemy 1.2.18+ds1-1 -- no debconf information
Processed: fixed 924839 0.11-3.1
Processing commands for cont...@bugs.debian.org: > fixed 924839 0.11-3.1 Bug #924839 [src:sphinxcontrib-programoutput] sphinxcontrib-programoutput: FTBFS: tests failed Marked as fixed in versions sphinxcontrib-programoutput/0.11-3.1. > End of message, stopping processing here. Please contact me if you need assistance. -- 924839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924973: g3dviewer: 'debian/rules clean' after build causes removal of mkinstalldirs
Package: g3dviewer Version: 0.2.99.5~svn130-9 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, g3dviewer/experimental fails to build twice in a row. The first build succeeds, but during subsequent debian/rules clean the following files disappear: compile missing depcomp ltmain.sh mkinstalldirs Makefile.in aclocal.m4 INSTALL configure install-sh config.h.in pixmaps/Makefile.in m4/Makefile.in glade/Makefile.in src/Makefile.in thumbnailer/Makefile.in man/Makefile.in examples/Makefile.in causing the second build to fail: [...] Making install in po make[4]: Entering directory '/build/g3dviewer-0.2.99.5~svn130/po' if test -r ".././mkinstalldirs"; then \ .././mkinstalldirs /build/g3dviewer-0.2.99.5~svn130/debian/g3dviewer/usr/share; \ else \ /bin/bash ../mkinstalldirs /build/g3dviewer-0.2.99.5~svn130/debian/g3dviewer/usr/share; \ fi /bin/bash: ../mkinstalldirs: No such file or directory make[4]: *** [Makefile:136: install-data-yes] Error 127 make[4]: Leaving directory '/build/g3dviewer-0.2.99.5~svn130/po' [...] There is no explicit deletion command being shown during make distclean. Full buildlog attached. Andreas g3dviewer_0.2.99.5~svn130-9_twice.log.gz Description: application/gzip
Processed: Bug #924972 in openjdk-11-jre-dcevm marked as pending
Processing control commands: > tag -1 pending Bug #924972 [openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: Incompatible with openjdk/11.0.3+1-1 (Error occurred during initialization of VM) Added tag(s) pending. -- 924972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924972: Bug #924972 in openjdk-11-jre-dcevm marked as pending
Control: tag -1 pending Hello, Bug #924972 in openjdk-11-jre-dcevm 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/openjdk-11-jre-dcevm/commit/f640e3a44c44e7633b883554faf89d2b89102ffc New upstream release (Closes: #924972) (this message was generated automatically) -- Greetings https://bugs.debian.org/924972
Bug#924972: openjdk-11-jre-dcevm: Incompatible with openjdk/11.0.3+1-1 (Error occurred during initialization of VM)
Package: openjdk-11-jre-dcevm Version: 11.0.1+8-1 Severity: grave Justification: renders package unusable Forwarded: https://github.com/HotswapProjects/openjdk-jdk11u-dcevm/issues/2 openjdk-11-jre-dcevm doesn't work with openjdk-11/11.0.3+1-1, any invocation of 'java -dcevm' returns the following error: $ java -dcevm Test Error occurred during initialization of VM Unable to load native library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: symbol JVM_InitClassName version SUNWprivate_1.1 not defined in file libjvm.so with link time reference openjdk-11-jre-dcevm needs to be aligned to the same openjdk-11 version (11.0.3+1) Emmanuel Bourg
Processed: Re: busybox ip --oneline displays nothing
Processing commands for cont...@bugs.debian.org: > severity 924374 serious Bug #924374 [busybox] busybox ip -oneline link show displays nothing Severity set to 'serious' from 'important' > # breaks other packages > End of message, stopping processing here. Please contact me if you need assistance. -- 924374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924970: openhft-chronicle-threads: FTBFS: package net.openhft.chronicle.core.threads does not exist
Source: openhft-chronicle-threads Version: 1.16.3-1 Severity: serious Justification: fails to build from source Hi, openhft-chronicle-threads/experimental recently started to FTBFS: [...] [ESC[1;34mINFOESC[m] - [ESC[1;33mWARNINGESC[m] COMPILATION WARNING : [ESC[1;34mINFOESC[m] - [ESC[1;33mWARNINGESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/TimingPauser.java:[35,10] pause(long,java.util.concurrent.TimeUnit) in net.openhft.chronicle.threads.Paus er has been deprecated [ESC[1;33mWARNINGESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/TimeoutPauser.java:[66,17] pause(long,java.util.concurrent.TimeUnit) in net.openhft.chronicle.threads.Pau ser has been deprecated [ESC[1;33mWARNINGESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/BusyTimedPauser.java:[44,17] pause(long,java.util.concurrent.TimeUnit) in net.openhft.chronicle.threads.P auser has been deprecated [ESC[1;33mWARNINGESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/LongPauser.java:[105,17] pause(long,java.util.concurrent.TimeUnit) in net.openhft.chronicle.threads.Pause r has been deprecated [ESC[1;34mINFOESC[m] 4 warnings [ESC[1;34mINFOESC[m] - [ESC[1;34mINFOESC[m] - [ESC[1;31mERRORESC[m] COMPILATION ERROR : [ESC[1;34mINFOESC[m] - [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/BusyPauser.java:[22,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/PauserMonitor.java:[19,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/PauserMonitor.java:[20,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/PauserMonitor.java:[21,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/PauserMonitor.java:[31,39] cannot find symbol symbol: class EventHandler [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/PauserMonitor.java:[50,36] cannot find symbol symbol: class InvalidEventHandlerException location: class net.openhft.chronicle.threads.PauserMonitor [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/PauserMonitor.java:[85,12] cannot find symbol symbol: class HandlerPriority location: class net.openhft.chronicle.threads.PauserMonitor [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java:[23,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java:[24,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java:[25,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java:[26,42] package net.openhft.chronicle.core.threads does not exist [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java:[49,42] cannot find symbol symbol: class EventLoop [ESC[1;31mERRORESC[m] /build/openhft-chronicle-threads-1.16.3/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java:[55,26] cannot find symbol symbol: class EventHandler [...] Andreas openhft-chronicle-threads_1.16.3-1.log.gz Description: application/gzip
Processed: severity of 922717 is serious
Processing commands for cont...@bugs.debian.org:
> severity 922717 serious
Bug #922717 {Done: Edward Betts } [src:uap-core] uap-core:
CVE-2018-20164
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies
Control: tag -1 moreinfo Re: Robie Basak 2019-03-18 <20190318165800.gc12...@mal.justgohome.co.uk> > It is well understood that the OpenSSL license is not "compatible" with > the GPL (either version 2 or 3); and furthermore, Debian has long taken > the position that, unless a license exception is granted by the > copyright holders, a package which is distributed under the GPL must > only link to libraries whose licenses are also GPL-compatible in order > for it to be included in Debian. How is that a problem in libpq5, and not in the other packages? Christoph
Processed: Re: Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies
Processing control commands: > tag -1 moreinfo Bug #924937 [libpq5] libpq5: OpenSSL license contamination of GPL reverse-dependencies Added tag(s) moreinfo. -- 924937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pdns: CVE-2019-3871: Insufficient validation in the HTTP remote backend
Processing control commands: > found -1 4.0.3-1+deb9u3 Bug #924966 [src:pdns] pdns: CVE-2019-3871: Insufficient validation in the HTTP remote backend Marked as found in versions pdns/4.0.3-1+deb9u3. > found -1 4.0.3-1 Bug #924966 [src:pdns] pdns: CVE-2019-3871: Insufficient validation in the HTTP remote backend Marked as found in versions pdns/4.0.3-1. -- 924966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924966: pdns: CVE-2019-3871: Insufficient validation in the HTTP remote backend
Source: pdns Version: 4.1.6-1 Severity: grave Tags: security upstream Forwarded: https://github.com/PowerDNS/pdns/issues/7573 Control: found -1 4.0.3-1+deb9u3 Control: found -1 4.0.3-1 Hi, The following vulnerability was published for pdns. CVE-2019-3871[0]: Insufficient validation in the HTTP remote backend If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-3871 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3871 [1] https://www.openwall.com/lists/oss-security/2019/03/18/4 [2] https://github.com/PowerDNS/pdns/issues/7573 [3] https://docs.powerdns.com/authoritative/security-advisories/powerdns-advisory-2019-03.html [4] https://downloads.powerdns.com/patches/2019-03/ Regards, Salvatore
Processed: libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863
Processing control commands: > found -1 1.7.0-1 Bug #924965 [src:libssh2] libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863 Marked as found in versions libssh2/1.7.0-1. -- 924965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924965: libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863
Source: libssh2 Version: 1.8.0-2 Severity: grave Tags: security upstream Control: found -1 1.7.0-1 Hi, The following vulnerabilities were published for libssh2. CVE-2019-3855[0]: Possible integer overflow in transport read allows out-of-bounds write CVE-2019-3856[1]: |Possible integer overflow in keyboard interactive handling allows |out-of-bounds write CVE-2019-3857[2]: |Possible integer overflow leading to zero-byte allocation and |out-of-bounds write CVE-2019-3858[3]: Possible zero-byte allocation leading to an out-of-bounds read CVE-2019-3859[4]: |Out-of-bounds reads with specially crafted payloads due to unchecked |use of `_libssh2_packet_require` and `_libssh2_packet_requirev` CVE-2019-3860[5]: Out-of-bounds reads with specially crafted SFTP packets CVE-2019-3861[6]: Out-of-bounds reads with specially crafted SSH packets CVE-2019-3862[7]: Out-of-bounds memory comparison CVE-2019-3863[8]: |Integer overflow in user authenicate keyboard interactive allows |out-of-bounds writes If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-3855 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3855 [1] https://security-tracker.debian.org/tracker/CVE-2019-3856 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3856 [2] https://security-tracker.debian.org/tracker/CVE-2019-3857 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3857 [3] https://security-tracker.debian.org/tracker/CVE-2019-3858 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3858 [4] https://security-tracker.debian.org/tracker/CVE-2019-3859 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3859 [5] https://security-tracker.debian.org/tracker/CVE-2019-3860 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3860 [6] https://security-tracker.debian.org/tracker/CVE-2019-3861 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3861 [7] https://security-tracker.debian.org/tracker/CVE-2019-3862 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3862 [8] https://security-tracker.debian.org/tracker/CVE-2019-3863 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3863 Regards, Salvatore
Bug#901148: raise severity of #901148 to critical because it affect usability of over packages
On Fri, Aug 03, 2018 at 02:47:44PM +0200, Thomas Pierson wrote: > severity 901148 critical > found 901148 2.14.0-8 > thanks > > Hi, > > I just spend 1 hour of time debugging my sound playback to finally > discover it was just the timidity package that get the sound device blocked. > Same experience here. The first warning was the mute button LED on my Thinkpad X220 no longer lit when pressed. Initially I thought it might be a failure of pulseaudio's udev detection, but static configuration also provided negative results. Finally I found this bug, purged timidity, and as soon as the daemon was killed received a desktop notification of found device. > I raise the severity of this bug to critical because it clearly render > other packages unusable starting by pulseaudio itself. > Agreed. Cheers, Nicholas signature.asc Description: PGP signature
