Bug#920982: deal.ii: FTFBFS with doxygen 1.8.15 draft package
Control: severity -1 important Hi Paolo On Thu, 31 Jan 2019 at 11:09, Paolo Greppi wrote: > I tested your package against a draft package for doxygen 1.8.15: > https://bugs.debian.org/919413 > https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680/artifacts/browse/debian/output/ > > and it FTBFS with this error: I'm lowering the severity of this bug for now. Please raise it again once doxygen 1.8.15 has been uploaded to unstable. Regards Graham
Processed: Re: Bug#920982: deal.ii: FTFBFS with doxygen 1.8.15 draft package
Processing control commands: > severity -1 important Bug #920982 [src:deal.ii] deal.ii: FTFBFS with doxygen 1.8.15 draft package Severity set to 'important' from 'serious' -- 920982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 910295 with 919599, notfound 910295 in dput/1.0.2, tagging 910295
Processing commands for cont...@bugs.debian.org:
> block 910295 with 919599
Bug #910295 {Done: Ben Finney } [dput] dput: FTBFS: tests
fail to mock HTTP request
Bug #920019 {Done: Ben Finney } [dput] dput fails to build
on test errors
910295 was blocked by: 919599
910295 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #910295 to the same blocks
previously set
920019 was blocked by: 919599
920019 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #920019 to the same blocks
previously set
> notfound 910295 dput/1.0.2
Bug #910295 {Done: Ben Finney } [dput] dput: FTBFS: tests
fail to mock HTTP request
Bug #920019 {Done: Ben Finney } [dput] dput fails to build
on test errors
No longer marked as found in versions dput/1.0.2.
No longer marked as found in versions dput/1.0.2.
> tags 910295 - moreinfo
Bug #910295 {Done: Ben Finney } [dput] dput: FTBFS: tests
fail to mock HTTP request
Bug #920019 {Done: Ben Finney } [dput] dput fails to build
on test errors
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295
920019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reopening 880047
Processing commands for cont...@bugs.debian.org:
> reopen 880047
Bug #880047 {Done: Adrian Bunk } [postgrey] postgrey doesn't
start because it can't write its pid
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions postgrey/1.36-3+deb9u2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
880047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#900156: marked as done (puma: FTBFS against openssl 1.1.1)
Your message dated Sun, 10 Feb 2019 05:36:29 + with message-id and subject line Bug#900156: fixed in puma 3.12.0-1 has caused the Debian Bug report #900156, regarding puma: 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.) -- 900156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puma Version: 3.11.3-1 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 |TestPumaServerSSLClient#test_verify_client_cert = |E: Build killed with signal TERM after 150 minutes of inactivity might be due to the fact that once TLS1.3 is enabled, the SSL_read() function might return error SSL_ERROR_WANT_READ asking it for a retry. An "automatic" fix to this behaviour is currently discussed upstream [3] but it has been always part of the doccumentation - it just hardly occured before. [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/puma_3.11.3-1_amd64-2018-05-01T23%3A16%3A10Z [2] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/puma_3.11.3-1_amd64-2018-05-02T18%3A47%3A34Z [3] https://github.com/openssl/openssl/issues/6234 Sebastian --- End Message --- --- Begin Message --- Source: puma Source-Version: 3.12.0-1 We believe that the bug you reported is fixed in the latest version of puma, 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. Pirate Praveen (supplier of updated puma 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: Sun, 10 Feb 2019 10:56:59 +0530 Source: puma Binary: puma puma-dbgsym Architecture: source amd64 Version: 3.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Description: puma - threaded HTTP 1.1 server for Ruby/Rack applications Closes: 900156 Changes: puma (3.12.0-1) unstable; urgency=medium . [ Balint Reczey ] * New upstream version 3.12.0 * Refresh patches . [ Pirate Praveen ] * Fix OpenSSL 1.1.1 test failures with upstream patch (Closes: #900156) * Bump Standards-Version to 4.3.0 (no changes needed) * Add myself to uploaders Checksums-Sha1: 5c5fbb4e9f774c59eff7c88a5cab6826418ad94b 1952 puma_3.12.0-1.dsc 1a9411a70f5c98a5a555d37834da21332fc9203f 215213 puma_3.12.0.orig.tar.gz 860351e581ea45674d929cddd24aa8ae182bf179 6840 puma_3.12.0-1.debian.tar.xz 4592bdc3536ecefc38b7ddfe6bb309a896b96dcc 36964 puma-dbgsym_3.12.0-1_amd64.deb 3e19afbf4cf79c6d6f7fae447315ccedafd19da0 8941 puma_3.12.0-1_amd64.buildinfo 96d4406b3fc1a04382cf595c94aed59b6ac358c7 113416 puma_3.12.0-1_amd64.deb Checksums-Sha256: 7ebb2a45fb046449bf536403c66ab20482dc2a6f43957f520b80e5ed658c56ec 1952 puma_3.12.0-1.dsc c604674a201ca8698c4efa34a0d24dd10037de9b91301f349b063aa2ded0532a 215213 puma_3.12.0.orig.tar.gz 40c3f46798a6db9232d9dc66e0ead38b210c9856308c5aed76e796e3bee0297d 6840 puma_3.12.0-1.debian.tar.xz 1d444842d8db76baf01cdca4bfb8a8e25b507046b5a13db01b9214e453916975 36964 puma-dbgsym_3.12.0-1_amd64.deb 7b168e954ad87a0d65254d963add177d41f81224253792191e8df7d1d95a9a9d 8941 puma_3.12.0-1_amd64.buildinfo b13a9f2033304dc460b219c88cef15dbbd832c0134baa6aa71a96a9fee2e14fa 113416 puma_3.12.0-1_amd64.deb Files: 54c3bdee9ad8fd08c30a58e9f4609bb6 1952 ruby optional puma_3.12.0-1.dsc b89fdf9a5b89233c5d165080e555b306 215213 ruby optional puma_3.12.0.orig.tar.gz 4225a1037aafbf3d170eed143083a5b2 6840 ruby optional puma_3.12.0-1.debian.tar.xz cc2f75e1c6e8f4075846cb8da5c615c4 36964 debug optional puma-dbgsym_3.12.0-1_amd64.deb f579299b0a42999d1e0db479a5e832d4 8941 ruby optional puma_3.12.0-1_amd64.buildinfo 825bdd5093b2cc823046e77d8e36faeb 113416 ruby optional
Bug#907022: marked as done (puma: autopkgtest times out after update of openssl)
Your message dated Sun, 10 Feb 2019 05:36:29 + with message-id and subject line Bug#900156: fixed in puma 3.12.0-1 has caused the Debian Bug report #900156, regarding puma: autopkgtest times out after update of openssl 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.) -- 900156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puma Version: 3.11.3-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update timeout Control: affects -1 src:openssl Control: block 907015 by -1 Dear maintainers, With a recent upload of openssl the autpkgtest of puma started to time out in testing and unstable. Before the update of openssl, the test ran in ~1 minute, now it takes more than 2:47 hours. Currently this regression is contributing to the delay of the migration of openssl to testing [1]. Could you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity as appropriate. Of course openssl shouldn't break you package, but in this case it seems like you are not handling a failure mode in the test suite well and are waiting indefinitely for a certain reply. As such I can't blame openssl at all for that. However, if this is a real problem in your package, openssl should add a versioned Breaks on the unfixed version, hence I added a blocking relation on the openssl bug that tracks that (note, the Breaks is nice even if the issue is only in the autopkgtest). A quote from the openssl maintainer about the openssl update: ''' This is probably the result of the default openssl.cfg now having: [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=2 Where the SECLEVEL 2 requires a 112 / 2048 bit security level. ''' More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=openssl https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/867849/log.gz signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: puma Source-Version: 3.12.0-1 We believe that the bug you reported is fixed in the latest version of puma, 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. Pirate Praveen (supplier of updated puma 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: Sun, 10 Feb 2019 10:56:59 +0530 Source: puma Binary: puma puma-dbgsym Architecture: source amd64 Version: 3.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Description: puma - threaded HTTP 1.1 server for Ruby/Rack applications Closes: 900156 Changes: puma (3.12.0-1) unstable; urgency=medium . [ Balint Reczey ] * New upstream version 3.12.0 * Refresh patches . [ Pirate Praveen ] * Fix OpenSSL 1.1.1 test failures with upstream patch (Closes: #900156) * Bump Standards-Version to 4.3.0 (no changes needed) * Add myself to uploaders Checksums-Sha1: 5c5fbb4e9f774c59eff7c88a5cab6826418ad94b 1952 puma_3.12.0-1.dsc 1a9411a70f5c98a5a555d37834da21332fc9203f 215213 puma_3.12.0.orig.tar.gz 860351e581ea45674d929cddd24aa8ae182bf179 6840 puma_3.12.0-1.debian.tar.xz 4592bdc3536ecefc38b7ddfe6bb309a896b96dcc 36964 puma-dbgsym_3.12.0-1_amd64.deb 3e19afbf4cf79c6d6f7fae447315ccedafd19da0 8941 puma_3.12.0-1_amd64.buildinfo 96d4406b3fc1a04382cf595c94aed59b6ac358c7 113416 puma_3.12.0-1_amd64.deb Checksums-Sha256: 7ebb2a45fb046449bf536403c66ab20482dc2a6f43957f520b80e5ed658c56ec 1952 puma_3.12.0-1.dsc c604674a201ca8698c4efa34a0d24dd10037de9b91301f349b063aa2ded0532a 215213 puma_3.12.0.orig.tar.gz 40c3f46798a6db9232d9dc66e0ead38b210c9856308c5aed76e796e3bee0297d 6840 puma_3.12.0-1.debian.tar.xz 1d444842d8db76baf01cdca4bfb8a8e25b507046b5a13db01b9214e453916975 36964 puma-dbgsym_3.12.0-1_amd64.deb
Bug#879538: marked as done (mandos: (tries to) use GnuTLS OpenPGP support)
Your message dated Sun, 10 Feb 2019 05:26:20 + with message-id and subject line Bug#879538: fixed in mandos 1.8.0-1 has caused the Debian Bug report #879538, regarding mandos: (tries to) use GnuTLS OpenPGP support 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.) -- 879538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mandos Version: 1.7.16-1 Severity: normal Tags: upstream User: ametz...@bebt.de Usertags: deprecated-gnutls-3.6 Hello, plugins.d/mandos-client.c actually uses GnuTLS OpenPGP support. This code was marked deprecated in 3.5.9 and was removed in 3.6.0. Noop stub functions are still shipped to avoid ABI breakage but return GNUTLS_E_UNIMPLEMENTED_FEATURE. Please drop GnuTLS OpenPGP support in mandos. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --- End Message --- --- Begin Message --- Source: mandos Source-Version: 1.8.0-1 We believe that the bug you reported is fixed in the latest version of mandos, 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 879...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Teddy Hogeborn (supplier of updated mandos 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: Sun, 10 Feb 2019 05:52:49 +0100 Source: mandos Binary: mandos mandos-client mandos-client-dbgsym Architecture: source amd64 all Version: 1.8.0-1 Distribution: unstable Urgency: medium Maintainer: Mandos Maintainers Changed-By: Teddy Hogeborn Description: mandos - server giving encrypted passwords to Mandos clients mandos-client - do unattended reboots with an encrypted root file system Closes: 879538 916673 Changes: mandos (1.8.0-1) unstable; urgency=medium . * New upstream release. * Fix "(tries to) use GnuTLS OpenPGP support" by using raw public keys when available (Closes: #879538) * Fix "mandos : Depends: libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed" by now also allowing GnuTLS >= 3.6.6 (Closes: #916673) * debian/control (Standards-Version): Update to "4.3.0". (Package: mandos-client/Depends): Change from "cryptsetup" to "cryptsetup (<< 2:2.0.3-1) | cryptsetup-initramfs". Add "debconf (>= 1.5.5) | debconf-2.0". (Source: mandos/Build-Depends): Also allow libgnutls30 (>= 3.6.6). (Package: mandos/Depends): - '' - and add debconf (>= 1.5.5) | debconf-2.0". (Package: mandos/Description): Alter description to match new design. (Package: mandos-client/Description): - '' - (Package: mandos-client/Depends): Move "gnutls-bin | openssl" to here from "Recommends". * debian/mandos-client.README.Debian: Add --tls-privkey and --tls-pubkey options to test command. * debian/mandos-client.postinst (create_key): Renamed to "create_keys" - all callers changed - and also create TLS key files. Show notice if new TLS key files were created. * debian/mandos-client.postrm (purge): Also remove TLS key files. * debian/mandos-client.lintian-overrides: Override warnings. * debian/mandos-client.templates: New. * debian/mandos.lintian-overrides: Override warnings. * debian/mandos.postinst (configure): If GnuTLS 3.6.6 or later is detected, show an important notice (once) about the new key_id option required in clients.conf. * debian/mandos.templates: New. * debian/copyright: Update copyright year to 2019. Checksums-Sha1: ccec6ddfb8c81c1e0834c9cf77499a753bcdc697 2309 mandos_1.8.0-1.dsc 8c7869db7e221af04de77ab15ec1311224d7e8f6 185079 mandos_1.8.0.orig.tar.gz 3bf6b48e016f39274899140ee762af6b4dc2132c 17428 mandos_1.8.0-1.debian.tar.xz 274c3c454ecf993ed5043cc569f833ecc30cb9a9 174020 mandos-client-dbgsym_1.8.0-1_amd64.deb 65e5b433c576978c5dfe5fa6916f65ad43d62f7a 132380 mandos-client_1.8.0-1_amd64.deb 9f3f30ba01706af295de9efb2474842182925a6a 91144 mandos_1.8.0-1_all.deb 816538d8fac5d6240af509f9c121617d5951ba15 9210 mandos_1.8.0-1_amd64.buildinfo Checksums-Sha256:
Bug#921615: marked as done (prometheus: CVE-2019-3826: Stored DOM cross-site scripting (XSS) attack via crafted URL)
Your message dated Sun, 10 Feb 2019 05:26:58 + with message-id and subject line Bug#921615: fixed in prometheus 2.7.1+ds-1 has caused the Debian Bug report #921615, regarding prometheus: CVE-2019-3826: Stored DOM cross-site scripting (XSS) attack via crafted URL 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.) -- 921615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prometheus Version: 2.6.0+ds-1 Severity: grave Tags: security upstream Forwarded: https://github.com/prometheus/prometheus/pull/5163 Hi, The following vulnerability was published for prometheus. CVE-2019-3826[0]: Stored DOM cross-site scripting (XSS) attack via crafted URL 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-3826 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3826 [1] https://github.com/prometheus/prometheus/pull/5163 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: prometheus Source-Version: 2.7.1+ds-1 We believe that the bug you reported is fixed in the latest version of prometheus, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated prometheus 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: Sun, 10 Feb 2019 04:45:36 + Source: prometheus Architecture: source Version: 2.7.1+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Closes: 921615 Changes: prometheus (2.7.1+ds-1) unstable; urgency=medium . * New upstream release. Includes fix for CVE-2019-3826 (Stored DOM cross-site scripting (XSS) attack via crafted URL). Closes: #921615 * Refresh patches. * debian/control: Update tsdb version dependency. * Update Standards-Version with no changes. * Revert commit c7d83b2 as the feature it introduces pulls a new version of a dependency. To be removed soon. * debian/rules: Regenerate protobuf files at buildtime. * Use a different port for tests that run prometheus. Checksums-Sha1: 5122de3fef498685ff734c490237024a3ab9687c 3438 prometheus_2.7.1+ds-1.dsc d3eef4c8ac99a311102590f2fac384a9e4c9ee25 634122 prometheus_2.7.1+ds.orig.tar.gz 5fc36011a3b9e3e3e32e6435b9154b3a7d23e7af 34476 prometheus_2.7.1+ds-1.debian.tar.xz 0e672515481f447314eace4a36a7040e93e530a7 11828 prometheus_2.7.1+ds-1_amd64.buildinfo Checksums-Sha256: e966df49a95749ecc1f452eb59c21ea9b85cb9e83a505337e9ffd8ed292cbc5c 3438 prometheus_2.7.1+ds-1.dsc d43f86c934b98397a1431006222115a4945a9025e76ae1bdee03b997b8af42d6 634122 prometheus_2.7.1+ds.orig.tar.gz 336bf98e7dc2cafaaabd6e20b76222a0d54338cf103aca832770ebf98b3e63f7 34476 prometheus_2.7.1+ds-1.debian.tar.xz 734f05b2ae96bb997f1e904803c1b27d23af626fa7efc2d13bc74331b8d83eb9 11828 prometheus_2.7.1+ds-1_amd64.buildinfo Files: 256138492527986881bd93d6c11fd420 3438 net optional prometheus_2.7.1+ds-1.dsc 5448d97e42a3a421c163be247cb98029 634122 net optional prometheus_2.7.1+ds.orig.tar.gz c08ff1807fabb246a6677ba53d8e6acd 34476 net optional prometheus_2.7.1+ds-1.debian.tar.xz 8b51b3ff64e42f43c84e9f5cc4c08a18 11828 net optional prometheus_2.7.1+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlxfrTwACgkQXdjgv5Gj 09qbNg/+KqWD7qWOO9zDBTnP3KXB179PKjWv55MmLyjriTVGLT4dl7Z3HLw0IVYd bL8BfePiEU202rgD+us4lO9vYOK1VD1ahJMbxYXxe6fyM9eROcO2uVH7sD5Gqc32 JMMLJ8Kg1ezKYWLTa7AJx4otleNTY5OUGRw2749ttVCfZsgQWv4bpwTUZjA5Ol1Q cNzncQr1aRIeOneAoXXB19EIpre0B453AF+NuQ1AlhIVKl3GtMBo8BWeeTPwvMrs dY6sth7iQJ0u+Cm6P88FpPfaMiqmR29ISm5fYjxf6RH4dTeIFXVcl6rf8umROypE 6B1ibuQN5ervn8c9bPsYEtIi8pazNviEAqhayBubHHqXsEgkBJgQZP8jJP/4cual NxpZiFTOA6SEeR11KMtlChjOYqwZyrKh9iuB2zpUYc8fQhCz2fbU77Tu8YOvAwL2 egbE/48iHooP5uGW5LAh2vcsED/s7Du/8ENOP5k9IF4yHFO6ZLebB/4DWFZ2aXsn
Bug#916673: marked as done (mandos : Depends: libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed)
Your message dated Sun, 10 Feb 2019 05:26:20 + with message-id and subject line Bug#916673: fixed in mandos 1.8.0-1 has caused the Debian Bug report #916673, regarding mandos : Depends: libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mandos Version: 1.7.20-1 Severity: serious The following packages have unmet dependencies: mandos : Depends: libgnutls28-dev (< 3.6.0) but 3.6.5-2 is to be installed or libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed Additionally, the libgnutls28-dev alternative of the dependencies looks wrong - this should likely just be libgnutls30. --- End Message --- --- Begin Message --- Source: mandos Source-Version: 1.8.0-1 We believe that the bug you reported is fixed in the latest version of mandos, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Teddy Hogeborn (supplier of updated mandos 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: Sun, 10 Feb 2019 05:52:49 +0100 Source: mandos Binary: mandos mandos-client mandos-client-dbgsym Architecture: source amd64 all Version: 1.8.0-1 Distribution: unstable Urgency: medium Maintainer: Mandos Maintainers Changed-By: Teddy Hogeborn Description: mandos - server giving encrypted passwords to Mandos clients mandos-client - do unattended reboots with an encrypted root file system Closes: 879538 916673 Changes: mandos (1.8.0-1) unstable; urgency=medium . * New upstream release. * Fix "(tries to) use GnuTLS OpenPGP support" by using raw public keys when available (Closes: #879538) * Fix "mandos : Depends: libgnutls30 (< 3.6.0) but 3.6.5-2 is to be installed" by now also allowing GnuTLS >= 3.6.6 (Closes: #916673) * debian/control (Standards-Version): Update to "4.3.0". (Package: mandos-client/Depends): Change from "cryptsetup" to "cryptsetup (<< 2:2.0.3-1) | cryptsetup-initramfs". Add "debconf (>= 1.5.5) | debconf-2.0". (Source: mandos/Build-Depends): Also allow libgnutls30 (>= 3.6.6). (Package: mandos/Depends): - '' - and add debconf (>= 1.5.5) | debconf-2.0". (Package: mandos/Description): Alter description to match new design. (Package: mandos-client/Description): - '' - (Package: mandos-client/Depends): Move "gnutls-bin | openssl" to here from "Recommends". * debian/mandos-client.README.Debian: Add --tls-privkey and --tls-pubkey options to test command. * debian/mandos-client.postinst (create_key): Renamed to "create_keys" - all callers changed - and also create TLS key files. Show notice if new TLS key files were created. * debian/mandos-client.postrm (purge): Also remove TLS key files. * debian/mandos-client.lintian-overrides: Override warnings. * debian/mandos-client.templates: New. * debian/mandos.lintian-overrides: Override warnings. * debian/mandos.postinst (configure): If GnuTLS 3.6.6 or later is detected, show an important notice (once) about the new key_id option required in clients.conf. * debian/mandos.templates: New. * debian/copyright: Update copyright year to 2019. Checksums-Sha1: ccec6ddfb8c81c1e0834c9cf77499a753bcdc697 2309 mandos_1.8.0-1.dsc 8c7869db7e221af04de77ab15ec1311224d7e8f6 185079 mandos_1.8.0.orig.tar.gz 3bf6b48e016f39274899140ee762af6b4dc2132c 17428 mandos_1.8.0-1.debian.tar.xz 274c3c454ecf993ed5043cc569f833ecc30cb9a9 174020 mandos-client-dbgsym_1.8.0-1_amd64.deb 65e5b433c576978c5dfe5fa6916f65ad43d62f7a 132380 mandos-client_1.8.0-1_amd64.deb 9f3f30ba01706af295de9efb2474842182925a6a 91144 mandos_1.8.0-1_all.deb 816538d8fac5d6240af509f9c121617d5951ba15 9210 mandos_1.8.0-1_amd64.buildinfo Checksums-Sha256: 9f41add54831b69cb19db1167bec885a974a519c1af521c34a7293b57e1c6cb9 2309 mandos_1.8.0-1.dsc 3f134cdbfe0c502f796f0d129b21c14ec844c1fa985cb49e038f6078e6db1a3f 185079 mandos_1.8.0.orig.tar.gz
Bug#916898: linux-image-4.18.0-3-amd64: kernel oops and gdm fails to start
yes, 4.19 solved the problem. Thanks, On Sun, 2019-02-10 at 01:34 +, Ben Hutchings wrote: > Control: forcemerge 914495 -1 > On Wed, 19 Dec 2018 20:35:14 -0600 "Brent S. Elmer" > wrote: > > Package: src:linuxVersion: 4.18.20-2Severity: > > criticalJustification: breaks the whole system > > I upgraded to linux-image-4.18.0-3-amd64 and gdm fails to start. I > > can getinto the system remotely and get to the journal. There is a > > kernel oops in thejournal. > [...] > This looks like a bug that was fixed in 4.19. Let us know if > you'restill seeing the problem. > Ben. >
Bug#921539: marked as done (unbound fails to start after upgrade)
Your message dated Sun, 10 Feb 2019 02:59:38 + with message-id and subject line Bug#921538: fixed in unbound 1.9.0-2 has caused the Debian Bug report #921538, regarding unbound fails to start after upgrade 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.) -- 921538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unbound Version: 1.9.0-1 Severity: grave Justification: renders package unusable Immediately after installing 1.9.0-1, unbound refused to run after restart. System logs contained: Feb 6 11:00:24 annuminas package-helper[6142]: /var/lib/unbound/root.key has content Feb 6 11:00:24 annuminas unbound: [6146:0] notice: init module 0: subnet Feb 6 11:00:24 annuminas unbound: [6146:0] notice: init module 1: validator Feb 6 11:00:24 annuminas unbound: [6146:0] error: unable to open /var/lib/unbound/root.key for reading: No such file or directory Feb 6 11:00:24 annuminas systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE Feb 6 11:00:24 annuminas unbound: [6146:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key Feb 6 11:00:24 annuminas systemd[1]: unbound.service: Failed with result 'exit-code'. Feb 6 11:00:24 annuminas unbound: [6146:0] error: validator: error in trustanchors config Feb 6 11:00:24 annuminas unbound: [6146:0] error: validator: could not apply configuration settings. Feb 6 11:00:24 annuminas unbound: [6146:0] error: module init for module validator failed Feb 6 11:00:24 annuminas unbound: [6146:0] fatal error: failed to setup modules Feb 6 11:00:24 annuminas kernel: [1792989.896766] audit: type=1400 audit(1549468824.750:4639): apparmor="STATUS" operation="profile_replace" info="same as cur rent profile, skipping" profile="unconfined" name="/usr/sbin/unbound" pid=6149 comm="apparmor_parser" Feb 6 11:00:24 annuminas systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart. Feb 6 11:00:24 annuminas systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1. Feb 6 11:00:25 annuminas systemd[1]: unbound.service: Control process exited, code=killed, status=15/TERM Feb 6 11:00:25 annuminas systemd[1]: unbound.service: Succeeded. Commenting out the contents of /etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf allowed the process to start, presumably no longer validating DNSSEC. The /var/lib/unbound/root.key file is present and readable, as it was prior to the upgrade. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unbound depends on: ii adduser 3.118 ii dns-root-data 2018091102 ii libc6 2.28-6 ii libevent-2.1-6 2.1.8-stable-4 ii libfstrm0 0.4.0-1 ii libprotobuf-c1 1.3.1-1+b1 ii libpython3.73.7.2-2 ii libssl1.1 1.1.1a-1 ii libsystemd0 240-5 ii lsb-base10.2018112800 ii openssl 1.1.1a-1 ii unbound-anchor 1.9.0-1 unbound recommends no packages. Versions of packages unbound suggests: ii apparmor 2.13.2-7 --- End Message --- --- Begin Message --- Source: unbound Source-Version: 1.9.0-2 We believe that the bug you reported is fixed in the latest version of unbound, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Edmonds (supplier of updated unbound package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Feb 2019 21:10:52 -0500 Source: unbound Architecture: source Version: 1.9.0-2 Distribution: unstable Urgency: medium Maintainer: unbound packagers Changed-By: Robert Edmonds
Bug#921836: marked as done (ipywidgets: FTBFS (error TS2688: Cannot find type definition file for 'sizzle'))
Your message dated Sun, 10 Feb 2019 02:59:25 + with message-id and subject line Bug#921836: fixed in typescript-types 20190209-1 has caused the Debian Bug report #921836, regarding ipywidgets: FTBFS (error TS2688: Cannot find type definition file for 'sizzle') 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.) -- 921836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ipywidgets Version: 6.0.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config dh_auto_configure -- -d ./widgetsnbextension I: pybuild base:217: python2.7 setup.py config INFO:root:setup.py entered INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games running config I: pybuild base:217: python3.7 setup.py config INFO:root:setup.py entered INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games running config make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' /usr/bin/make -C debian -f fakewebpack.mk all make[2]: Entering directory '/<>/debian' /usr/bin/make -f "fakewebpack-prep-unpacked.mk" all make[3]: Entering directory '/<>/debian' cd "fakewebpack-unpacked/phosphor/" && tsc --moduleResolution Classic --project src mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../.. fakewebpack-helpers/css-loader-pack.py < "fakewebpack-unpacked/phosphor/styles/base.css.real" > "fakewebpack-unpacked/phosphor/styles/base.css" mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../.. -DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" > "fakewebpack-unpacked/phosphor/styles/base.css?f74d" printf "module.exports = $(cat "fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" > "fakewebpack-unpacked/jupyter-js-widgets/package.json" cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --moduleResolution Classic --project src ../../../../../../usr/lib/nodejs/@types/jquery/index.d.ts(28,23): error TS2688: Cannot find type definition file for 'sizzle'. ../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(27,33): error TS2503: Cannot find namespace 'Sizzle'. ../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(35,14): error TS2503: Cannot find namespace 'Sizzle'. ../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(43,17): error TS2503: Cannot find namespace 'Sizzle'. make[3]: *** [fakewebpack-prep-unpacked.mk:33: fakewebpack-unpacked/jupyter-js-widgets/lib.stamp] Error 1 make[3]: Leaving directory '/<>/debian' make[2]: *** [fakewebpack.mk:73: fakewebpack/widgetsnbextension-unpacked.stamp] Error 2 make[2]: Leaving directory '/<>/debian' make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ipywidgets.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: typescript-types Source-Version: 20190209-1 We believe that the bug you reported is fixed in the latest version of typescript-types, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous o
Bug#921538: marked as done (Fails to start since upgrade to 1.9.0-1)
Your message dated Sun, 10 Feb 2019 02:59:38 + with message-id and subject line Bug#921538: fixed in unbound 1.9.0-2 has caused the Debian Bug report #921538, regarding Fails to start since upgrade to 1.9.0-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.) -- 921538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unbound Version: 1.9.0-1 Severity: grave Since the upgrade to 1.9.0-1, unbound fails to start. Purging the package and reinstalling does not fix the issue. The errors seem to be due to being unable to read various configuration files. Feb 06 11:01:12 zeta unbound[28647]: [28647:0] error: unable to open /var/lib/unbound/root.key for reading: No such file or directory Feb 06 11:01:12 zeta package-helper[28648]: [1549468872] unbound-checkconf[28651:0] error: Could not open /etc/unbound//etc/unbound/unbound.conf: No such file or director -- rak@zeta:~$ sudo apt purge unbound && sudo apt install unbound Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apg bmon byobu ccze cmatrix ipsec-tools jp2a libconfuse-common libconfuse2 libipe7.2.7 moreutils pastebinit python-newt screen speedometer tree unbound-anchor Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: unbound* 0 upgraded, 0 newly installed, 1 to remove and 111 not upgraded. After this operation, 4,286 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 450489 files and directories currently installed.) Removing unbound (1.9.0-1) ... Processing triggers for man-db (2.8.5-1) ... (Reading database ... 450457 files and directories currently installed.) Purging configuration files for unbound (1.9.0-1) ... insserv: There is a loop between service sendsigs and racoon if stopped insserv: loop involving service racoon at depth 3 insserv: loop involving service sendsigs at depth 2 insserv: loop involving service bluetooth at depth 1 insserv: loop involving service rsyslog at depth 4 insserv: loop involving service avahi at depth 2 Processing triggers for systemd (240-5) ... Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apg bmon byobu ccze cmatrix ipsec-tools jp2a libconfuse-common libconfuse2 libipe7.2.7 moreutils pastebinit python-newt screen speedometer tree Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: unbound 0 upgraded, 1 newly installed, 0 to remove and 111 not upgraded. Need to get 0 B/795 kB of archives. After this operation, 4,286 kB of additional disk space will be used. Selecting previously unselected package unbound. (Reading database ... 450450 files and directories currently installed.) Preparing to unpack .../unbound_1.9.0-1_amd64.deb ... Unpacking unbound (1.9.0-1) ... Setting up unbound (1.9.0-1) ... Created symlink /etc/systemd/system/multi-user.target.wants/unbound.service → /lib/systemd/system/unbound.service. Created symlink /etc/systemd/system/unbound.service.wants/unbound-resolvconf.service → /lib/systemd/system/unbound-resolvconf.service. Job for unbound.service failed because the control process exited with error code. See "systemctl status unbound.service" and "journalctl -xe" for details. insserv: There is a loop between service sendsigs and racoon if stopped insserv: loop involving service racoon at depth 3 insserv: loop involving service sendsigs at depth 2 insserv: loop involving service bluetooth at depth 1 insserv: loop involving service rsyslog at depth 4 insserv: loop involving service avahi at depth 2 Job for unbound.service failed because the control process exited with error code. See "systemctl status unbound.service" and "journalctl -xe" for details. invoke-rc.d: initscript unbound, action "start" failed. ● unbound.service - Unbound DNS server Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2019-02-06 11:01:07 EST; 7ms ago Docs: man:unbound(8) Process: 28299 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS) Process: 28333 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS) Process:
Bug#921896: marked as done (json-js: FTBFS (ERROR: `cycle.min.map` is not a supported option))
Your message dated Sun, 10 Feb 2019 02:57:26 + with message-id and subject line Bug#921896: fixed in json-js 0~20180723-1 has caused the Debian Bug report #921896, regarding json-js: FTBFS (ERROR: `cycle.min.map` is not a supported option) 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.) -- 921896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:json-js Version: 0~20160510-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep test -x debian/rules mkdir -p "." Scanning upstream source for new/changed copyright notices... set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive --copyright --deb-fmt --ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints 2 combinations of copyright and licensing found. WARNING:New or changed notices discovered: Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ To fix the situation please do the following: 1) Examine debian/copyright_* and referenced files 2) Update debian/copyright as needed 3) Replace debian/copyright_hints with debian/copyright_newhints touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft uglifyjs --source-map cycle.min.map -o cycle.min.js cycle.js Supported options: content null filenamenull includeSources false rootnull url null ERROR: `cycle.min.map` is not a supported option at DefaultsError.get (eval at (/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :71:23) at fatal (/usr/lib/nodejs/uglify-js/bin/uglifyjs:291:53) at run (/usr/lib/nodejs/uglify-js/bin/uglifyjs:235:9) at Object. (/usr/lib/nodejs/uglify-js/bin/uglifyjs:160:5) at Module._compile (module.js:652:30) at Object.Module._extensions..js (module.js:663:10) at Module.load (module.js:565:32) at tryModuleLoad (module.js:505:12) at Function.Module._load (module.js:497:3) at Function.Module.runMain (module.js:693:10) make: *** [debian/rules:36: cycle.min.js] Error 1 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/json-js.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: json-js Source-Version: 0~20180723-1 We believe that the bug you reported is fixed in the latest version of json-js, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated json-js 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: Sun, 10 Feb 2019 03:07:09 +0100 Source: json-js Architecture: source Version: 0~20180723-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 921896 Changes: json-js (0~20180723-1) unstable; urgency=medium . [ upstream ] * New release(s). . [ Jonas Smedegaard ] * Simplify rules. Stop build-depend on licensecheck cdbs dh-buildinfo. * Fix update JavaScript optimization options. Tighten to build-depend on recent uglifyjs. Stop build-depend explicitly on node-source-map. Closes: Bug#921896. Thanks to Santiago Vila. * Declare compliance with Debian Policy 4.3.0. * Set Rules-Requires-Root: no. * Update Vcs-* fields: Maintenance moved to
Bug#904762: vulture: missing dependency on python3-pkg-resources
Followup-For: Bug #904762 Control: tag -1 pending Hi, I just backported the fix from sid, built the package for stretch, opened a stretch-pu request and uploaded the fix: https://bugs.debian.org/921910 Andreas
Processed: Re: vulture: missing dependency on python3-pkg-resources
Processing control commands:
> tag -1 pending
Bug #904762 {Done: Adrian Bunk } [vulture] vulture: missing
dependency on python3-pkg-resources
Added tag(s) pending.
--
904762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#921836: ipywidgets: FTBFS (error TS2688: Cannot find type definition file for 'sizzle')
Processing control commands: > reassign -1 src:typescript-types Bug #921836 [src:ipywidgets] ipywidgets: FTBFS (error TS2688: Cannot find type definition file for 'sizzle') Bug reassigned from package 'src:ipywidgets' to 'src:typescript-types'. No longer marked as found in versions ipywidgets/6.0.0-3. Ignoring request to alter fixed versions of bug #921836 to the same values previously set -- 921836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#826020: graphite-api.service: RequireMountsFor needs to be RequiresMountsFor
Followup-For: Bug #826020 Control: tag -1 pending Hi, I just extracted the fix from sid, rebuilt the package for stretch, opened a stretch-pu request and uploaded the fix: https://bugs.debian.org/921908 Andreas
Processed: Re: graphite-api.service: RequireMountsFor needs to be RequiresMountsFor
Processing control commands: > tag -1 pending Bug #826020 [graphite-api] graphite-api.service: RequireMountsFor needs to be RequiresMountsFor Added tag(s) pending. -- 826020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921836: ipywidgets: FTBFS (error TS2688: Cannot find type definition file for 'sizzle')
Control: reassign -1 src:typescript-types This is a problem with the typescript-types package, I will upload a fix shortly. X Santiago Vila: > Package: src:ipywidgets > Version: 6.0.0-3 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > > [...] > debian/rules build-indep > dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild >dh_update_autotools_config -i -O--buildsystem=pybuild >dh_autoreconf -i -O--buildsystem=pybuild >debian/rules override_dh_auto_configure > make[1]: Entering directory '/<>' > dh_auto_configure > I: pybuild base:217: python2.7 setup.py config > running config > I: pybuild base:217: python3.7 setup.py config > running config > dh_auto_configure -- -d ./widgetsnbextension > I: pybuild base:217: python2.7 setup.py config > INFO:root:setup.py entered > INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > running config > I: pybuild base:217: python3.7 setup.py config > INFO:root:setup.py entered > INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > running config > make[1]: Leaving directory '/<>' >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > /usr/bin/make -C debian -f fakewebpack.mk all > make[2]: Entering directory '/<>/debian' > /usr/bin/make -f "fakewebpack-prep-unpacked.mk" all > make[3]: Entering directory '/<>/debian' > cd "fakewebpack-unpacked/phosphor/" && tsc --moduleResolution Classic > --project src > mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../.. > fakewebpack-helpers/css-loader-pack.py < > "fakewebpack-unpacked/phosphor/styles/base.css.real" > > "fakewebpack-unpacked/phosphor/styles/base.css" > mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../.. > -DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" > > "fakewebpack-unpacked/phosphor/styles/base.css?f74d" > printf "module.exports = $(cat > "fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" > > "fakewebpack-unpacked/jupyter-js-widgets/package.json" > cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --moduleResolution > Classic --project src > ../../../../../../usr/lib/nodejs/@types/jquery/index.d.ts(28,23): error > TS2688: Cannot find type definition file for 'sizzle'. > ../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(27,33): error > TS2503: Cannot find namespace 'Sizzle'. > ../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(35,14): error > TS2503: Cannot find namespace 'Sizzle'. > ../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(43,17): error > TS2503: Cannot find namespace 'Sizzle'. > make[3]: *** [fakewebpack-prep-unpacked.mk:33: > fakewebpack-unpacked/jupyter-js-widgets/lib.stamp] Error 1 > make[3]: Leaving directory '/<>/debian' > make[2]: *** [fakewebpack.mk:73: > fakewebpack/widgetsnbextension-unpacked.stamp] Error 2 > make[2]: Leaving directory '/<>/debian' > make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:7: build-indep] Error 2 > dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit > status 2 > > > (The above is just how the build ends and not necessarily the most relevant > part) > > The build was made in my autobuilder with "dpkg-buildpackage -A" > and it also fails here: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ipywidgets.html > > where you can get a full build log if you need it. > > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the BTS web page for this package. > > Thanks. > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#920731: marked as done (elpa-projectile: fails to upgrade from 'stretch': projectile.el:1121:1:Error: Unknown upattern `(quote native)')
Your message dated Sun, 10 Feb 2019 01:19:06 +
with message-id
and subject line Bug#920731: fixed in projectile 2.0.0-2
has caused the Debian Bug report #920731,
regarding elpa-projectile: fails to upgrade from 'stretch':
projectile.el:1121:1:Error: Unknown upattern `(quote native)'
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.)
--
920731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-projectile
Version: 2.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.
>From the attached log (scroll to the bottom...):
Setting up elpa-projectile (2.0.0-1) ...
Install elpa-epl for emacs24
install/epl-0.9: Handling install of emacsen flavor emacs24
install/epl-0.9: byte-compiling for emacs24
Install emacsen-common for emacs24
emacsen-common: Handling install of emacsen flavor emacs24
Wrote /etc/emacs24/site-start.d/00debian-vars.elc
Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
Install elpa-pkg-info for emacs24
install/pkg-info-0.6: Handling install of emacsen flavor emacs24
install/pkg-info-0.6: byte-compiling for emacs24
Install elpa-projectile for emacs24
install/projectile-2.0.0: Handling install of emacsen flavor emacs24
install/projectile-2.0.0: byte-compiling for emacs24
In toplevel form:
projectile.el:968:1:Warning: Unused lexical argument `trash'
projectile.el:1121:1:Error: Unknown upattern `(quote native)'
ERROR: install script from elpa-projectile package failed
dpkg: error processing package elpa-projectile (--configure):
subprocess installed post-installation script returned error exit status 1
Note that this failure was observed during an
'apt-get upgrade && apt-get dist-upgrade' run in the 'upgrade'
phase, while direct 'apt-get dist-upgrade' succeeds.
This indicates that there may be some missing Breaks against
unsupported older emacs versions ...
cheers,
Andreas
elpa-projectile_2.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: projectile
Source-Version: 2.0.0-2
We believe that the bug you reported is fixed in the latest version of
projectile, 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.
Sean Whitton (supplier of updated projectile 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, 09 Feb 2019 17:54:37 -0700
Source: projectile
Binary: elpa-projectile projectile-doc
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team
Changed-By: Sean Whitton
Description:
elpa-projectile - project interaction library for Emacs
projectile-doc - project interaction library for Emacs - documentation
Closes: 919547 920731
Changes:
projectile (2.0.0-2) unstable; urgency=medium
.
[ Ben Finney ]
* Set “Homepage” to the current URL for the project.
Closes: bug#919547.
.
[ Sean Whitton ]
* Drop 'emacs' from Depends.
It was listed in both Depends and Recommends.
* Add Breaks against emacs24{,-lucid,nox} (<< 1:25.1) (Closes: #920731).
Thanks Andreas Beckmann for the report.
Checksums-Sha1:
9c7b0b0a7e5657c9124d5675f20719a4f0bdf5ec 2159 projectile_2.0.0-2.dsc
2ae778340e14ed896f512d45b49f57ae04c1cbb5 8060 projectile_2.0.0-2.debian.tar.xz
Checksums-Sha256:
84e24e2a155a3a3c74eb2ea887765a04dbdac1bc1fe136b6bd5a3d81a5f3830f 2159
projectile_2.0.0-2.dsc
4d87d1aeec09b9ddbdc175290525d16a7ea1b5abc9f8841c6c9f6c3c6e4b74b9 8060
projectile_2.0.0-2.debian.tar.xz
Files:
2a3201fabd9c62851acdb4caed4b633b 2159 lisp optional projectile_2.0.0-2.dsc
3d525a19f06ece642fc098160061deae 8060 lisp optional
projectile_2.0.0-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlxfdpYACgkQaVt65L8G
YkC/wA/+PmVDzG99scSJobjECUTlVjo6El6k0VMMkMyrdig+TPM6My9Dz6BPopst
Bug#921538: Fails to start since upgrade to 1.9.0-1
Simon Deziel wrote: > On 2019-02-06 11:12 a.m., Ryan Kavanagh wrote: > > Since the upgrade to 1.9.0-1, unbound fails to start. Purging the > > package and reinstalling does not fix the issue. The errors seem to be > > due to being unable to read various configuration files. > > > > Feb 06 11:01:12 zeta unbound[28647]: [28647:0] error: unable to open > > /var/lib/unbound/root.key for reading: No such file or directory > > Feb 06 11:01:12 zeta package-helper[28648]: [1549468872] > > unbound-checkconf[28651:0] error: Could not open > > /etc/unbound//etc/unbound/unbound.conf: No such file or director > > It seems like chroot'ing to /etc/unbound is attempted. To workaround you > can try this: > > cat << EOF > /etc/unbound/unbound.conf.d/chroot.conf > server: > chroot: "" > EOF > service unbound restart Automatic chroot'ing has been disabled in the unbound Debian package for a while, by this commit: https://salsa.debian.org/dns-team/unbound/commit/66bb04a0869e315f76c4b4efe8632914d860686c It looks like that change was lost in the 1.9.0-1 upload, compare these two revisions: https://salsa.debian.org/dns-team/unbound/blob/debian/1.8.1-1/util/config_file.c#L163-165 https://salsa.debian.org/dns-team/unbound/blob/debian/1.9.0-1/util/config_file.c#L169-171 Probably it's better to use the --with-chroot-dir= argument to configure rather than directly patching the source to change the default. -- Robert Edmonds edmo...@debian.org
Bug#921538: Fails to start since upgrade to 1.9.0-1
On 2019-02-09 8:28 p.m., Robert Edmonds wrote: > Probably it's better to use the --with-chroot-dir= argument to configure > rather than directly patching the source to change the default. Indeed and that's what's being proposed in the merge request. Regards, Simon
Bug#921838: ppl: FTBFS (LaTeX error)
Looks like this common issue is in fact #921272. (i.e. the currently-packaged tabu broke with recent TeX Live) James
Bug#916898: linux-image-4.18.0-3-amd64: kernel oops and gdm fails to start
Control: forcemerge 914495 -1 On Wed, 19 Dec 2018 20:35:14 -0600 "Brent S. Elmer" wrote: > Package: src:linux > Version: 4.18.20-2 > Severity: critical > Justification: breaks the whole system > > I upgraded to linux-image-4.18.0-3-amd64 and gdm fails to start. I can get > into the system remotely and get to the journal. There is a kernel oops in > the > journal. [...] This looks like a bug that was fixed in 4.19. Let us know if you're still seeing the problem. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Processed: Re: supercollider-emacs: fails to install with xemacs21
Processing control commands:
> tag -1 pending
Bug #916858 {Done: Georges Khaznadar }
[supercollider-emacs] supercollider-emacs: fails to install with xemacs21
Ignoring request to alter tags of bug #916858 to the same tags previously set
--
916858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#916858: supercollider-emacs: fails to install with xemacs21
Followup-For: Bug #916858 Control: tag -1 pending Hi, I cherry-picked that commit from sid, rebuilt the package for stretch and files a stretch-pu request: https://bugs.debian.org/921893 Andreas
Bug#888847: grokmirror: missing dependency on python-pkg-resources
Followup-For: Bug #47 Control: tag -1 pending Hi, I just rebuilt the package for stretch and filed a stretch-pu-request: https://bugs.debian.org/921907 Andreas
Processed: Re: grokmirror: missing dependency on python-pkg-resources
Processing control commands:
> tag -1 pending
Bug #47 {Done: Adrian Bunk } [src:grokmirror] grokmirror:
missing dependency on python-pkg-resources
Added tag(s) pending.
--
47: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 921838 in ppl/1:1.2-7, affects 921838
Processing commands for cont...@bugs.debian.org: > notfound 921838 ppl/1:1.2-7 Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) No longer marked as found in versions ppl/1:1.2-7. > affects 921838 src:ppl Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) Added indication that 921838 affects src:ppl > thanks Stopping processing here. Please contact me if you need assistance. -- 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919442: python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 2019-02-10 00:04, Sandro Tosi wrote: >> your .maintscript files are wrong. Obviously you wanted symlink_to_dir, >> but you used dir_to_symlink. > > mh not really, i want /usr/share/doc/python-dmidecode-dbg/ to be a > symlink to /usr/share/doc/python-dmidecode/ (and the same for the py3k > packages) - isnt symlink_to_dir the right helper to use in that case? Well, as long as the package ships a directory full of files in /usr/share/doc: /usr/share/doc/python-dmidecode-dbg /usr/share/doc/python-dmidecode-dbg/AUTHORS /usr/share/doc/python-dmidecode-dbg/AUTHORS.upstream /usr/share/doc/python-dmidecode-dbg/README /usr/share/doc/python-dmidecode-dbg/README.types /usr/share/doc/python-dmidecode-dbg/README.upstream.gz /usr/share/doc/python-dmidecode-dbg/changelog.Debian.gz /usr/share/doc/python-dmidecode-dbg/changelog.gz /usr/share/doc/python-dmidecode-dbg/copyright trying to use d-m-h to change that into a symlink will only cause a great mess. Andreas
Bug#883413: src:linux: Still reproducible with linux-image-4.15.0-rc8-amd64
Control: severity -1 important Control: tag -1 moreinfo On Mon, 29 Jan 2018 15:05:00 + Chris Boot wrote: > Package: src:linux > Followup-For: Bug #883413 > > Hi Ben, > > Unfortunately I can still reproduce this problem on 4.15-rc8 from > experimental. > > The cmdline for this boot was: > > BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8-amd64 > root=/dev/mapper/vg_tarquin-rootfs ro intel_iommu=on vsyscall=emulate > scsi_mod.use_blk_mq=Y dm_mod.use_blk_mq=Y intel_pstate=passive > i915.disable_display=Y i915.enable_gvt=Y apparmor=0 > systemd.unified_cgroup_hierarchy=1 console=ttyS1,115200n8 console=tty0 > > This triggers with DefaultMemoryAccounting=yes enabled in > /etc/systemd/system.conf, and NUT seems to regularly be involved in the > crash on my system. Sadly the systemd unit is very simple indeed, and > because my UPS is network-connected I'm not even doing dodgy things like > USB from within NUT. > > Quite how the kernel thinks that nut-server.service is using 16 ZiB of > memory is beyond me; presumably this is a slightly negative 64-bit int > bring cast unsigned. The following also feels like a smoking gun: > > [ 2982.158622] percpu ref (css_release) <= 0 (-197) after switching to atomic [...] Sorry for leaving this unanswered so long. Are you still seeing this? I found some apparently related reports on the Red Hat Bugzilla but not on anything newer than 4.17. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Processed: Re: src:linux: Still reproducible with linux-image-4.15.0-rc8-amd64
Processing control commands: > severity -1 important Bug #883413 [src:linux] linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c Severity set to 'important' from 'serious' > tag -1 moreinfo Bug #883413 [src:linux] linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c Added tag(s) moreinfo. -- 883413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): limit package to src:ppl, reassign 921838 to doxygen, affects 921838
Processing commands for cont...@bugs.debian.org: > limit package src:ppl Limiting to bugs with field 'package' containing at least one of 'src:ppl' Limit currently set to 'package':'src:ppl' > reassign 921838 doxygen Bug #921838 [src:ppl] ppl: FTBFS (LaTeX error) Bug reassigned from package 'src:ppl' to 'doxygen'. package: '"doxygen"' does not match at least one of "src:ppl" Failed to clear fixed versions and reopen on 921838: limit failed for bugs: 921838. > affects 921838 src:ppl package: '"doxygen"' does not match at least one of "src:ppl" Failed to mark 921838 as affecting package(s): limit failed for bugs: 921838. > thanks Stopping processing here. Please contact me if you need assistance. -- 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: breaks when #included after
Processing control commands: > reassign -1 libc6-dev Bug #898743 [linux-libc-dev,libc6-dev] breaks when #included after Bug reassigned from package 'linux-libc-dev,libc6-dev' to 'libc6-dev'. Ignoring request to alter found versions of bug #898743 to the same values previously set Ignoring request to alter fixed versions of bug #898743 to the same values previously set > severity -1 normal Bug #898743 [libc6-dev] breaks when #included after Severity set to 'normal' from 'serious' -- 898743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#898743: breaks when #included after
Control: reassign -1 libc6-dev Control: severity -1 normal On Tue, 15 May 2018 16:57:57 +0200 Helmut Grohne wrote: > Package: linux-libc-dev,libc6-dev > Severity: serious > Justification: makes systemd ftbfs > User: helm...@debian.org > Usertags: rebootstrap > Control: affects -1 + src:systemd libmount-dev > > systemd FTBFS here, because compiling load-fragment.c fails. I spent a while > minimizing that file and it boils down to: > > $ cat test.c > #include > #include > $ gcc -c test.c > In file included from test.c:1:0: > /usr/include/x86_64-linux-gnu/sys/mount.h:35:3: error: expected identifier > before numeric constant >MS_RDONLY = 1, /* Mount read-only. */ >^ > $ > > linux/fs.h #defines MS_RDONLY and then sys/mount.h tries to create an > enum containing MS_RDONLY. That's a problem. [...] has defined MS_RDONLY as a macro since before version 1.0, so this is a wontfix on the kernel side. was already defining MS_RDONLY as both enumerator and macro in jessie, so this doesn't seem to be a regression. Downgrading and reassigning to just libc6-dev, but I fully expect this to be wontfix on that side as well. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Bug#921895: bitlbee: does not build all binary packages by default
Hello Wilmer, On Sun 10 Feb 2019 at 12:10AM +00, Wilmer van der Gaast wrote: > Yeah, this has always been a little bit iffy. Thankfully the > Skype-related packages can go away altogether. I'm not tracking BitlBee > development anymore but would expect that they go away in 3.6 (I'll have > to do the upload for it within the next few days so I'll verify). Thank you for your response. Please be sure to my -1.2 NMU in your upload, as it fixes another bug too. -- Sean Whitton signature.asc Description: PGP signature
Bug#921895: bitlbee: does not build all binary packages by default
Yeah, this has always been a little bit iffy. Thankfully the Skype-related packages can go away altogether. I'm not tracking BitlBee development anymore but would expect that they go away in 3.6 (I'll have to do the upload for it within the next few days so I'll verify). signature.asc Description: OpenPGP digital signature
Bug#921473: marked as done (calibre: Invalid maintainer address)
Your message dated Sun, 10 Feb 2019 00:04:20 + with message-id and subject line Bug#921473: fixed in calibre 3.39.1+dfsg-2 has caused the Debian Bug report #921473, regarding calibre: Invalid maintainer address to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: calibre Version: 3.39.1+dfsg-1 Severity: serious Justification: Policy 3.3 Debian policy requires a valid maintainer address: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: prein...@debian.org Unrouteable address From: Debian FTP Masters Subject: Processing of calibre_3.39.1+dfsg-1_source.changes Date: Tue, 05 Feb 2019 22:27:18 + X-Debian: DAK X-DAK: DAK Precedence: bulk Auto-Submitted: auto-generated X-Debian-Package: calibre Message-Id: calibre_3.39.1+dfsg-1_source.changes uploaded successfully to localhost along with the files: calibre_3.39.1+dfsg-1.dsc calibre_3.39.1+dfsg.orig.tar.xz calibre_3.39.1+dfsg-1.debian.tar.xz calibre_3.39.1+dfsg-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --1549405639-eximdsn-1087713461-- Scott K --- End Message --- --- Begin Message --- Source: calibre Source-Version: 3.39.1+dfsg-2 We believe that the bug you reported is fixed in the latest version of calibre, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated calibre package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Feb 2019 17:41:17 +0900 Source: calibre Architecture: source Version: 3.39.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Norbert Preining Changed-By: Norbert Preining Closes: 921473 Changes: calibre (3.39.1+dfsg-2) unstable; urgency=medium . * update my email and VCS fields (Closes: #921473) Checksums-Sha1: 9a8638fa86462b262adb36e2d99c19973bc0f8c8 2901 calibre_3.39.1+dfsg-2.dsc ecc05cea555c9be7bdb8367e100614b5b215fff7 54140 calibre_3.39.1+dfsg-2.debian.tar.xz ba190779eedd0a007b584ad7aaded38863c86cac 17482 calibre_3.39.1+dfsg-2_amd64.buildinfo Checksums-Sha256: c01353fd85500f0bb451a6e02d96f8ce3d2ae5104b3ea3362bd44d1f229eeab3 2901 calibre_3.39.1+dfsg-2.dsc 2eb498819a8181b0a154816372b32960688e9898118020a230646c22e394b711 54140 calibre_3.39.1+dfsg-2.debian.tar.xz 5f85e468a696629c964239a007363e0825fafb8fc27602cfe876140a84182a05 17482 calibre_3.39.1+dfsg-2_amd64.buildinfo Files: e2938b5edb3a1ec131210fdd5c29d6ad 2901 text optional calibre_3.39.1+dfsg-2.dsc 04a3f3a47658b5feb8ab8c01ecb9c468 54140 text optional calibre_3.39.1+dfsg-2.debian.tar.xz eaf02b27327ec5f77d9af65473c3dc54 17482 text optional calibre_3.39.1+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE4qYmHjkArtfNxmcIWogwR199EGEFAlxfZ2ETHG5zdGVldmVz QGdtYWlsLmNvbQAKCRBaiDBHX30QYVMEEAC103N6XvK6WNKp1v3AEhwc1iQRRSXv U2gngGaVpGFCNJZ8TzKwEXwwvme4nIDLs3yEJ7972gkJ5qLf+UoHOd2QX9szP4lH xmvVB1mEajYrfH3uMNqZZlnmKktOmSGB3U8aY4TaUIzvKA5Wj2MjFRRK63cUpFg6 JgGUVjLWI3yT9nH0fGM6pOnOrLA3lukWakV5B8Dm3hgAIKqhKlA46bs78T2IGeF2 Zn8BtQbZOY42x3RkwmCEPSYZzxu9X8Y6TbWSc7OpvAmrEg7G9lbVsFhkI0SAS8DB RoVhZDHu1G77oQuvnPRFKpPJkvbcWCfhXx/Rx9yed7DA+X4V2ox17P+mFVa85rss 1cCJRJW0zrSbSmxPeGGaiw7FukmAb9dRDxo1aCtX3Tjv07STOzD6aGlOKhDcd2y4 7u+aL/9MqsiNakfSuBkWwYn4eD/vplgk9z77PWz6WCdKAJIltlpioy3SX/oTl+/Q gUgJ2kDwH2IhDghVu2TLTSTTHVeD18Dvng1B6l7bswgsrpwHOSXUSXbeoDP+Xxw+ mSMkkJSv8/FavlrZPEl5pbimkonY8VIJWAarGZyNV+Q6T7lRtdLs+ftrQtRpVEmD IXljaprR0U08PifJej9G5jad6ekPoj1iUQf9CxSPjlGYPRe1mfiPKHaHbk4cP+DM b3WTrcEezSZxUg== =9vgf -END PGP SIGNATURE End Message ---
Processed: bitlbee: diff for NMU version 3.5.1-1.2
Processing control commands: > tags 816200 + pending Bug #816200 [bitlbee-common] bitlbee-common: postinst script fails if there is already a bitlbee system user, but no /var/lib/bitlbee directory Ignoring request to alter tags of bug #816200 to the same tags previously set > tags 921895 + pending Bug #921895 [src:bitlbee] bitlbee: does not build all binary packages by default Ignoring request to alter tags of bug #921895 to the same tags previously set -- 816200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816200 921895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921895: bitlbee: diff for NMU version 3.5.1-1.2
Control: tags 816200 + pending
Control: tags 921895 + pending
Dear maintainer,
I've prepared an NMU for bitlbee (versioned as 3.5.1-1.2) and uploaded
it to DELAYED/5. Please feel free to tell me if I should delay it
longer.
Regards.
--
Sean Whitton
diff -u bitlbee-3.5.1/debian/bitlbee-common.postinst bitlbee-3.5.1/debian/bitlbee-common.postinst
--- bitlbee-3.5.1/debian/bitlbee-common.postinst
+++ bitlbee-3.5.1/debian/bitlbee-common.postinst
@@ -34,7 +34,9 @@
adduser --system --group --disabled-login --disabled-password --home /var/lib/bitlbee/ bitlbee
fi
-chmod 700 /var/lib/bitlbee/
+if [ -d /var/lib/bitlbee ]; then
+chmod 700 /var/lib/bitlbee/
+fi
## Can't do this in packaging phase: Don't know the UID yet. Access to
## the file should be limited, now that it stores passwords. Added
diff -u bitlbee-3.5.1/debian/changelog bitlbee-3.5.1/debian/changelog
--- bitlbee-3.5.1/debian/changelog
+++ bitlbee-3.5.1/debian/changelog
@@ -1,3 +1,23 @@
+bitlbee (3.5.1-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Comment out bitlbee-plugin-skype and skyped in d/control (Closes: #921895).
+These binary packages are not built by d/rules by default, and as such
+they are not currently in the archive. Commenting them out in order
+to avoid my NMU hitting binNEW; this caused the -1.1 source-only
+upload to fail.
+Thank you to Mattia Rizzolo for suggesting this fix.
+
+ -- Sean Whitton Sat, 09 Feb 2019 17:03:38 -0700
+
+bitlbee (3.5.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add existence check to chmod call in bitlbee-common.postinst
+(Closes: #816200).
+
+ -- Sean Whitton Fri, 25 Jan 2019 16:50:34 -0700
+
bitlbee (3.5.1-1) unstable; urgency=medium
* Crash bug fix. (Closes: #853282)
diff -u bitlbee-3.5.1/debian/control bitlbee-3.5.1/debian/control
--- bitlbee-3.5.1/debian/control
+++ bitlbee-3.5.1/debian/control
@@ -72,22 +72,22 @@
-Package: bitlbee-plugin-skype
-Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, bitlbee (= ${binary:Version}) | bitlbee-libpurple (= ${binary:Version}), bitlbee-common (= ${source:Version})
-Recommends: skyped
-Description: IRC to other chat networks gateway (Skype plugin)
- This program can be used as an IRC server which forwards everything you
- say to people on other chat networks: Jabber (which includes Google
- Talk), ICQ, AIM, MSN and Twitter.
- .
- This package contains a plugin that adds support for the Skype IM network.
- You need to download and install the Skype client for this to work.
+# Package: bitlbee-plugin-skype
+# Architecture: any
+# Depends: ${misc:Depends}, ${shlibs:Depends}, bitlbee (= ${binary:Version}) | bitlbee-libpurple (= ${binary:Version}), bitlbee-common (= ${source:Version})
+# Recommends: skyped
+# Description: IRC to other chat networks gateway (Skype plugin)
+# This program can be used as an IRC server which forwards everything you
+# say to people on other chat networks: Jabber (which includes Google
+# Talk), ICQ, AIM, MSN and Twitter.
+# .
+# This package contains a plugin that adds support for the Skype IM network.
+# You need to download and install the Skype client for this to work.
-Package: skyped
-Architecture: all
-Depends: ${misc:Depends}, ${shlibs:Depends}, python (>= 2.5), python-gnutls, python-skype (>=0.9.28.7)
-Recommends: skype
-Description: Daemon to control Skype remotely
- Daemon to control the GUI Skype client. Currently required to control Skype
- from the BitlBee IRC2IM gateway. Skyped and Skype can run on a different
- host than the BitlBee server, the communication is encrypted.
- .
- You need to download and install the Skype client for this to work.
+# Package: skyped
+# Architecture: all
+# Depends: ${misc:Depends}, ${shlibs:Depends}, python (>= 2.5), python-gnutls, python-skype (>=0.9.28.7)
+# Recommends: skype
+# Description: Daemon to control Skype remotely
+# Daemon to control the GUI Skype client. Currently required to control Skype
+# from the BitlBee IRC2IM gateway. Skyped and Skype can run on a different
+# host than the BitlBee server, the communication is encrypted.
+# .
+# You need to download and install the Skype client for this to work.
signature.asc
Description: PGP signature
Processed: bitlbee: diff for NMU version 3.5.1-1.2
Processing control commands: > tags 816200 + pending Bug #816200 [bitlbee-common] bitlbee-common: postinst script fails if there is already a bitlbee system user, but no /var/lib/bitlbee directory Ignoring request to alter tags of bug #816200 to the same tags previously set > tags 921895 + pending Bug #921895 [src:bitlbee] bitlbee: does not build all binary packages by default Added tag(s) pending. -- 816200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816200 921895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)
Package: src:win-iconv Version: 0.0.8-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_auto_configure -i debian/rules override_dh_auto_build-indep make[1]: Entering directory '/<>' for arch in x86_64-w64-mingw32 i686-w64-mingw32; do \ mkdir -p build-$arch && \ cd build-$arch && \ ln -s ../*.h ../*.c ../*.def ../Makefile ./ && \ /usr/bin/make CC=$arch-gcc AR=$arch-ar RANLIB=$arch-ranlib DLLTOOL=$arch-dlltool prefix=/usr/$arch \ || exit 1 ; \ cd .. ; \ done make[2]: Entering directory '/<>/build-x86_64-w64-mingw32' x86_64-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -c win_iconv.c -DMAKE_DLL x86_64-w64-mingw32-gcc -shared -o iconv.dll -Wl,-s -Wl,--out-implib=libiconv.dll.a -Wl,--export-all-symbols win_iconv.o x86_64-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -c win_iconv.c x86_64-w64-mingw32-ar rcs libiconv.a win_iconv.o x86_64-w64-mingw32-ranlib libiconv.a x86_64-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -s -o win_iconv.exe win_iconv.c -DMAKE_EXE make[2]: Leaving directory '/<>/build-x86_64-w64-mingw32' make[2]: Entering directory '/<>/build-i686-w64-mingw32' i686-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -c win_iconv.c -DMAKE_DLL i686-w64-mingw32-gcc -shared -o iconv.dll -Wl,-s -Wl,--out-implib=libiconv.dll.a -Wl,--export-all-symbols win_iconv.o i686-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -c win_iconv.c i686-w64-mingw32-ar rcs libiconv.a win_iconv.o i686-w64-mingw32-ranlib libiconv.a i686-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -s -o win_iconv.exe win_iconv.c -DMAKE_EXE make[2]: Leaving directory '/<>/build-i686-w64-mingw32' make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' cd build-x86_64-w64-mingw32 && WINEPREFIX=/<>/build-x86_64-w64-mingw32/.wine /usr/bin/make CC=x86_64-w64-mingw32-gcc AR=x86_64-w64-mingw32-ar RANLIB=x86_64-w64-mingw32-ranlib DLLTOOL=x86_64-w64-mingw32-dlltool test make[2]: Entering directory '/<>/build-x86_64-w64-mingw32' x86_64-w64-mingw32-gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -pedantic -Wall -DUSE_LIBICONV_DLL -DDEFAULT_LIBICONV_DLL=\"\" -s -o win_iconv_test.exe win_iconv_test.c wine ./win_iconv_test.exe it looks like wine32 is missing, you should install it. multiarch needs to be enabled first. as root, please execute "dpkg --add-architecture i386 && apt-get update && apt-get install wine32" wine: created the configuration directory '/<>/build-x86_64-w64-mingw32/.wine' wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory make[2]: *** [Makefile:51: test] Error 1 make[2]: Leaving directory '/<>/build-x86_64-w64-mingw32' make[1]: *** [debian/rules:40: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:19: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 E: Build killed with signal TERM after 60 minutes of inactivity (Additionally, the autobuilder hangs and sbuild has to kill remaining processes) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/win-iconv.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921899: rt-extension-calendar: FTBFS (mv: cannot stat 'Makefile': No such file or directory)
Package: src:rt-extension-calendar Version: 1.01-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' rm -rf inc/Module for ver in 4; do \ perl Makefile.PL RTHOME=/usr/share/request-tracker$ver INSTALLDIRS=vendor; \ mv Makefile Makefile$ver; \ done Cannot determine perl version info from lib/RTx/Calendar.pm Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny module) (@INC contains: inc /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40. include /<>/inc/Module/Install.pm include inc/Module/Install/RTx.pm include inc/Module/Install/Base.pm include inc/Module/Install/Metadata.pm include inc/Module/Install/Makefile.pm include inc/Module/Install/ReadmeFromPod.pm mv: cannot stat 'Makefile': No such file or directory make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-calendar.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921901: ruby-voight-kampff: FTBFS (expected: < 0.002, got: 0.002076509001199156)
Package: src:ruby-voight-kampff
Version: 1.1.3-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 --buildsystem=ruby --with ruby
dh_update_autotools_config -i -O--buildsystem=ruby
dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
dh_ruby --build
dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
dh_testroot -i -O--buildsystem=ruby
dh_prep -i -O--buildsystem=ruby
[... snipped ...]
â Install Rubygems integration metadata
â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
generating gemspec at
/<>/debian/ruby-voight-kampff/usr/share/rubygems-integration/all/specifications/voight_kampff-1.1.3.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Checking Rubygems dependency resolution on ruby2.5
â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
GEM_PATH=debian/ruby-voight-kampff/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -e gem\ \"voight_kampff\"
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Run tests for ruby2.5 from debian/ruby-tests.rake
â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
RUBYLIB=/<>/debian/ruby-voight-kampff/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-voight-kampff/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
rspec
.F..
Failures:
1) VoightKampff::Test after the first run is fast
Failure/Error: expect(Benchmark.realtime { 20.times {
VoightKampff::Test.new('anything').bot? } }).to be < 0.002
expected: < 0.002
got: 0.002076509001199156
# ./spec/lib/voight_kampff/test_spec.rb:33:in `block (3 levels) in '
Finished in 0.27072 seconds (files took 3.02 seconds to load)
44 examples, 1 failure
Failed examples:
rspec ./spec/lib/voight_kampff/test_spec.rb:32 # VoightKampff::Test after the
first run is fast
rake aborted!
Command failed with status (1): [rspec...]
/<>/debian/ruby-tests.rake:4:in `block in '
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-voight-kampff
returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-voight-kampff.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921897: morse-simulator: FTBFS (Could not import extension sphinx.ext.pngmath)
Package: src:morse-simulator Version: 1.4-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python3 dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DBUILD_DOC_SUPPORT=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 \ -DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON 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 -DBUILD_DOC_SUPPORT=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 -DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON .. -- 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 [... snipped ...] CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_SYSCONFDIR CPACK_DEBIAN_PACKAGE_DEPENDS -- Build files have been written to: /<>/obj-x86_64-linux-gnu make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' cp version.py obj-*/ dh_auto_build cd obj-x86_64-linux-gnu && make -j1 make[2]: 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/depend make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/man.dir/DependInfo.cmake --color= Scanning dependencies of target man make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' env PYTHONPATH=/<>/obj-x86_64-linux-gnu:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/fakeenv:/<>/src:/<>/testing:/<>/bindings/pymorse/src/:$PYTHONPATH PYTHONDONTWRITEBYTECODE="morse" MORSESOURCE=/<> /usr/bin/python3 /usr/bin/sphinx-build -b man -c /<>/obj-x86_64-linux-gnu/doc /<>/doc/man /<>/obj-x86_64-linux-gnu/doc/man && /bin/gzip -f /<>/obj-x86_64-linux-gnu/doc/man/*.1 Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named 'sphinx.ext.pngmath') make[4]: *** [CMakeFiles/man.dir/build.make:60: CMakeFiles/man] Error 2 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:140: CMakeFiles/man.dir/all] Error 2 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [Makefile:144: all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2 make[1]: *** [debian/rules:27: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/morse-simulator.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921898: pilkit: FTBFS (AssertionError: '.apng' != '.png')
Package: src:pilkit
Version: 2.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
I: pybuild base:217: python3.7 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/reference.png tests/assets/reference.png
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build
running build
[... snipped ...]
tests.test_processors.test_smartcrop ... ok
tests.test_processors.test_resizetofill ... ok
tests.test_processors.test_resizetofit ... ok
Regression test for matthewwithanm/pilkit#1 ... ok
tests.test_processors.test_resizetofit_mat ... ok
Test that the ColorOverlay processor ... ok
Test that the Resize processor antialiases. ... ok
Test that the upscale argument works as expected. ... ok
tests.test_processors.test_should_raise_exception_if_anchor_is_passed_and_crop_is_set_to_false
... ok
tests.test_processors.test_should_set_crop_to_true_if_anchor_is_passed_without_crop
... ok
tests.test_processors.test_should_raise_exception_when_crop_is_passed_without_height_and_width
... ok
tests.test_processors.test_make_gifs_opaque ... ok
tests.test_processors.test_should_call_resizetofill_when_crop_and_ancho_is_passed
... ok
tests.test_processors.test_should_call_resizetofit_when_crop_is_not_passed ...
ok
tests.test_processors.test_should_call_smartresize_when_crop_not_passed ... ok
tests.test_processors.test_should_repass_upscale_option_false ... ok
tests.test_processors.test_should_repass_upscale_option_true ... ok
tests.test_utils.test_extension_to_format ... ok
tests.test_utils.test_format_to_extension_no_init ... FAIL
tests.test_utils.test_unknown_format ... ok
tests.test_utils.test_unknown_extension ... ok
Ensure default extensions are honored. ... ok
tests.test_utils.test_filewrapper ... ok
Test that ``save_image`` accepts filename strings (not just file objects). ...
ok
Make sure formats are normalized by ``prepare_image()``. ... ok
Make sure the ``quiet`` util doesn't error if devnull is unwriteable. ... ok
==
FAIL: tests.test_utils.test_format_to_extension_no_init
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File
"/<>/.pybuild/cpython2_2.7_pilkit/build/tests/test_utils.py", line
19, in test_format_to_extension_no_init
eq_(format_to_extension('PNG'), '.png')
AssertionError: '.apng' != '.png'
--
Ran 26 tests in 0.205s
FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython2_2.7_pilkit/build; python2.7 -m nose -v tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:9: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pilkit.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#921902: sdb: FTBFS (error CS1617: Invalid -langversion option `future')
Package: src:sdb Version: 1.2-1.1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh --with cli build-indep dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_update_autotools_config -i dh_auto_configure -i dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use) debian/rules override_dh_auto_build make[1]: Entering directory '/<>' mkdir -p dep/ dh_auto_build dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 make[2]: Entering directory '/<>' mkdir -p bin cp LICENSE bin/LICENSE mkdir -p bin cp README.md bin/README cp `pkg-config --variable=Sources mono-options` dep/Options.cs cp `pkg-config --variable=Sources mono-lineeditor` dep/getline.cs mkdir -p bin cp `pkg-config --variable=Libraries mono-cecil` bin/ cp `pkg-config --variable=Libraries mono-debugger` bin/ mcs -debug -langversion:future -unsafe -warnaserror -keyfile:mono.snk -lib:bin -out:bin/sdb.exe -target:exe -r:Mono.Posix -r:Mono.Cecil.dll -r:Mono.Cecil.Mdb.dll -r:Mono.Debugger.Soft.dll -r:Mono.Debugging.dll -r:Mono.Debugging.Soft.dll -pkg:nrefactory dep/Options.cs dep/getline.cs src/Commands/AttachCommand.cs src/Commands/BacktraceCommand.cs src/Commands/BreakpointCommand.cs src/Commands/CatchpointCommand.cs src/Commands/ConfigCommand.cs src/Commands/ConnectCommand.cs src/Commands/ContinueCommand.cs src/Commands/DatabaseCommand.cs src/Commands/DecompileCommand.cs src/Commands/DirectoryCommand.cs src/Commands/DisassembleCommand.cs src/Commands/EnvironmentCommand.cs src/Commands/FrameCommand.cs src/Commands/HelpCommand.cs src/Commands/KillCommand.cs src/Commands/ListenCommand.cs src/Commands/PluginCommand.cs src/Commands/PrintCommand.cs src/Commands/QuitCommand.cs src/Commands/ResetCommand.cs src/Commands/RootCommand.cs src/Commands/RunCommand.cs src/Commands/SourceCommand.cs src/Com mands/StepCommand.cs src/Commands/ThreadCommand.cs src/Commands/WatchCommand.cs src/AssemblyInfo.cs src/Color.cs src/Command.cs src/CommandAttribute.cs src/CommandLine.cs src/Configuration.cs src/CustomLogger.cs src/Debugger.cs src/LibEdit.cs src/Log.cs src/MultiCommand.cs src/Plugins.cs src/Program.cs src/SessionKind.cs src/State.cs src/Utilities.cs error CS1617: Invalid -langversion option `future'. It must be `ISO-1', `ISO-2', Default, Latest or value in range 1 to 7.2 make[2]: *** [Makefile:187: bin/sdb.exe] Error 1 make[2]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make[1]: *** [debian/rules:9: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:16: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sdb.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921903: sorl-thumbnail: FTBFS (failing tests)
Package: src:sorl-thumbnail Version: 12.3+git20170708-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --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:217: python2.7 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>/sorl-thumbnail-12.3+git20170708' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build running build [... snipped ...] Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) tests/thumbnail_tests/test_templatetags.py::TemplateTestCaseB::test_portrait /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) tests/thumbnail_tests/test_templatetags.py::TemplateTestCaseB::test_url /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) tests/thumbnail_tests/test_templatetags.py::TemplateTestCaseClient::test_empty_error /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) /usr/lib/python2.7/dist-packages/pytest_django/plugin.py:630: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code apifun(*marker.args, **marker.kwargs) /usr/lib/python2.7/dist-packages/django/core/handlers/base.py:52: RemovedInDjango20Warning: Old-style middleware using settings.MIDDLEWARE_CLASSES is deprecated. Update your middleware and use settings.MIDDLEWARE instead. "instead.", RemovedInDjango20Warning -- Docs: https://docs.pytest.org/en/latest/warnings.html = 1 failed, 59 passed, 8 skipped, 125 warnings in 9.80 seconds = make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>/sorl-thumbnail-12.3+git20170708' make: *** [debian/rules:10: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sorl-thumbnail.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921900: rt-extension-smsnotify: FTBFS (dh_auto_configure fails)
Package: src:rt-extension-smsnotify Version: 1.04-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_auto_configure -i perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" Can't locate Capture/Tiny.pm in @INC (you may need to install the Capture::Tiny module) (@INC contains: inc . /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Module/Install/ReadmeFromPod.pm line 40. include /<>/inc/Module/Install.pm include inc/Module/Install/RTx.pm include inc/Module/Install/Base.pm include inc/Module/Install/Metadata.pm include inc/Module/Install/Makefile.pm include inc/Module/Install/ReadmeFromPod.pm dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" returned exit code 2 make: *** [debian/rules:6: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rt-extension-smsnotify.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921895: bitlbee: does not build all binary packages by default
Source: bitlbee Version: 3.5.1-1 Severity: serious Hello, This source package's rules file does not build all the binary packages listed in d/control unless special environment variable values are present. As a result, bin:skyped and bin:bitlbee-plugin-skype are not in the archive. This caused my source-only NMU of this package to be rejected, because dak wanted to put it in binNEW because of skyped and bitlbee-plugin-skype, but source-only uploads to binNEW are not allowed. I think this is a bug of RC-severity because it is a highly irregular use of the Debian source package format which is confusing to people trying to do NMUs. Perhaps the maintainer will disagree; a downgrade of the severity of this bug would make sense if it turns out I'm not aware of some workflow that not building all the binary packages by default enables. -- Sean Whitton signature.asc Description: PGP signature
Bug#921896: json-js: FTBFS (ERROR: `cycle.min.map` is not a supported option)
Package: src:json-js Version: 0~20160510-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep test -x debian/rules mkdir -p "." Scanning upstream source for new/changed copyright notices... set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive --copyright --deb-fmt --ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints 2 combinations of copyright and licensing found. WARNING:New or changed notices discovered: Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ To fix the situation please do the following: 1) Examine debian/copyright_* and referenced files 2) Update debian/copyright as needed 3) Replace debian/copyright_hints with debian/copyright_newhints touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft uglifyjs --source-map cycle.min.map -o cycle.min.js cycle.js Supported options: content null filenamenull includeSources false rootnull url null ERROR: `cycle.min.map` is not a supported option at DefaultsError.get (eval at (/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :71:23) at fatal (/usr/lib/nodejs/uglify-js/bin/uglifyjs:291:53) at run (/usr/lib/nodejs/uglify-js/bin/uglifyjs:235:9) at Object. (/usr/lib/nodejs/uglify-js/bin/uglifyjs:160:5) at Module._compile (module.js:652:30) at Object.Module._extensions..js (module.js:663:10) at Module.load (module.js:565:32) at tryModuleLoad (module.js:505:12) at Function.Module._load (module.js:497:3) at Function.Module.runMain (module.js:693:10) make: *** [debian/rules:36: cycle.min.js] Error 1 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/json-js.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#921248: marked as done (kicad: FTBFS with GLM 0.9.9.3)
Your message dated Sun, 10 Feb 2019 00:20:37 +0100 with message-id <13788122-b49a-e6f4-61b5-1efff6d6b...@t-online.de> and subject line Re: Bug#921248: kicad: FTBFS with GLM 0.9.9.3 has caused the Debian Bug report #921248, regarding kicad: FTBFS with GLM 0.9.9.3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kicad Version: 5.1~20190127.4fc692f+dfsg1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, kicad/experimental recently started to FTBFS with the new GLM: -- Found GLM: /usr/include (found suitable version "0.9.9.3", minimum required is "0.9.5.1") CMake Error at CMakeLists.txt:591 (MESSAGE): GLM version 0.9.9.3 is incompatible with KiCad using GCC. Please downgrade to GLM version 0.9.9.2 or older or use clang instead -- Configuring incomplete, errors occurred! Cheers, Andreas --- End Message --- --- Begin Message --- Version: 5.1~rc1+dfsg1-1 Am 03.02.19 um 16:04 schrieb Andreas Beckmann: > -- Found GLM: /usr/include (found suitable version "0.9.9.3", minimum > required is "0.9.5.1") > CMake Error > at CMakeLists.txt:591 (MESSAGE): > > > > > > > > GLM version 0.9.9.3 is incompatible with KiCad using GCC. > > > > > Please downgrade to GLM version > 0.9.9.2 or older or use clang instead > > >
Bug#921667: [pkg-lxc-devel] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends
Le samedi 09 février 2019 à 22:19:13+0100, Andreas Beckmann a écrit : > On 2019-02-09 21:51, Pierre-Elliott Bécue wrote: > > I'm not sure that there is something we can do regarding lxc. Am I > > wrong? > > You could try to figure out why lxc explodes. > Probably some package places some configuration file at some location > > > Andreas > > PS: I should be able to get a shell in the chroot after the failure > occurred, in case you want me to collect some information. That's a good idea. This error is not clear at all to me. Could you please try to run the .postinst of lxc manually with a set -x? The goal would be to check which part explodes. Best, -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Bug#919442: python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On Thu, Feb 7, 2019 at 11:24 AM Andreas Beckmann wrote: > > Followup-For: Bug #919442 > Control: affects -1 + python3-dmidecode-dbg > Control: found -1 3.12.2-7 > > Hi, > > your .maintscript files are wrong. Obviously you wanted symlink_to_dir, > but you used dir_to_symlink. mh not really, i want /usr/share/doc/python-dmidecode-dbg/ to be a symlink to /usr/share/doc/python-dmidecode/ (and the same for the py3k packages) - isnt symlink_to_dir the right helper to use in that case? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#919442: python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On Sat, Feb 9, 2019 at 6:04 PM Sandro Tosi wrote: > > On Thu, Feb 7, 2019 at 11:24 AM Andreas Beckmann wrote: > > > > Followup-For: Bug #919442 > > Control: affects -1 + python3-dmidecode-dbg > > Control: found -1 3.12.2-7 > > > > Hi, > > > > your .maintscript files are wrong. Obviously you wanted symlink_to_dir, > > but you used dir_to_symlink. > > mh not really, i want /usr/share/doc/python-dmidecode-dbg/ to be a > symlink to /usr/share/doc/python-dmidecode/ (and the same for the py3k > packages) - isnt symlink_to_dir the right helper to use in that case? what i meant to say is "isnt dir_to_symlink the right helper to use in that case?" (so from dir to symlink) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#921892: libtommath: fails to clean after build
Source: libtommath Version: 1.1.0-3~exp1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, libtommath/experimental fails to build twice in a row. Cleaning after the first build fails with fakeroot debian/rules clean dh clean dh_auto_clean make -j3 clean make[1]: Entering directory '/build/libtommath-1.1.0' rm -f *.gcda *.gcno *.gcov *.bat *.o *.a *.obj *.lib *.exe *.dll etclib/*.o demo/demo.o test timing mpitest mtest/mtest mtest/mtest.exe \ *.idx *.toc *.log *.aux *.dvi *.lof *.ind *.ilg *.ps *.log *.s mpi.c *.da *.dyn *.dpi tommath.tex `find . -type f | grep [~] | xargs` *.lo *.la rm -rf .libs/ make -C etc/ clean MAKE=make make[2]: Entering directory '/build/libtommath-1.1.0/etc' rm -f *.log *.o *.obj *.exe pprime tune mersenne drprime tune86 tune86l mont 2kprime pprime.dat \ *.da *.dyn *.dpi *~ make[2]: Leaving directory '/build/libtommath-1.1.0/etc' make -C doc/ clean MAKE=make make[2]: Entering directory '/build/libtommath-1.1.0/doc' make -C pics/ clean MAKE=make make[3]: Entering directory '/build/libtommath-1.1.0/doc/pics' rm -rf *.ps *.pdf .xvpics make[3]: Leaving directory '/build/libtommath-1.1.0/doc/pics' rm -f *.idx *.toc *.log *.aux *.dvi *.lof *.ind *.ilg *.ps *.log tommath.tex make[2]: Leaving directory '/build/libtommath-1.1.0/doc' make[1]: Leaving directory '/build/libtommath-1.1.0' debian/rules override_dh_clean make[1]: Entering directory '/build/libtommath-1.1.0' dh_clean tommath.out debian/libtool rm: cannot remove 'debian/libtool': Is a directory dh_clean: rm -f -- debian/libtommath-docs.substvars debian/libtommath-dev.substvars debian/libtommath1.substvars tommath.out debian/libtool debian/files returned exit code 1 make[1]: *** [debian/rules:51: override_dh_clean] Error 2 make[1]: Leaving directory '/build/libtommath-1.1.0' make: *** [debian/rules:21: clean] Error 2 Andreas libtommath_1.1.0-3~exp1_twice.log.gz Description: application/gzip
Bug#921884: wlroots: ABI break between 0.2 and 0.3
On Sat, Feb 09, 2019 at 10:35:22PM +0100, Guido Günther wrote: > This is well known to the users of wlroots and the reason why we did not > upload to unstable yet but it's good to have a bug tracking that. ahem… but that's not common knowledge outside that circle... Can I ask you at least try to minimize the disruption until a stable ABI comes around (hopefully soon…) by: * mentioning this fact in the package description * still adding a .symbols file so a diff of the gone symbols is available * bumping shlibs every time the ABI changes (you should do this regardless) * adding Breaks against everything in the archive that any random upload breaks Instead of the last two items, you could add a virtual package (e.g. libwlroots-abi-XXX) and have that XXX change any time the ABI change, and have shlibs issue that instead of the current "libwlroots0"; I would go as far as saying that doint this would also allow you to upload this package to unstable even with the ABI regularly breaking, as you'd de-facto enforce a transition every time you bump that virtual package. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#920728: marked as done (libgd2: CVE-2019-6978)
Your message dated Sat, 09 Feb 2019 21:47:26 + with message-id and subject line Bug#920728: fixed in libgd2 2.2.4-2+deb9u4 has caused the Debian Bug report #920728, regarding libgd2: CVE-2019-6978 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.) -- 920728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgd2 Version: 2.2.5-5 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/libgd/libgd/issues/492 Hi, The following vulnerability was published for libgd2. CVE-2019-6978[0]: | The GD Graphics Library (aka LibGD) 2.2.5 has a double free in the | gdImage*Ptr() functions in gd_gif_out.c, gd_jpeg.c, and gd_wbmp.c. | NOTE: PHP is unaffected. 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-6978 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6978 [1] https://github.com/libgd/libgd/issues/492 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: libgd2 Source-Version: 2.2.4-2+deb9u4 We believe that the bug you reported is fixed in the latest version of libgd2, 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. Salvatore Bonaccorso (supplier of updated libgd2 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, 02 Feb 2019 10:49:03 +0100 Source: libgd2 Binary: libgd-tools libgd-dev libgd3 Architecture: source Version: 2.2.4-2+deb9u4 Distribution: stretch-security Urgency: high Maintainer: GD team Changed-By: Salvatore Bonaccorso Closes: 920645 920728 Description: libgd-dev - GD Graphics Library (development version) libgd-tools - GD command line tools and example code libgd3 - GD Graphics Library Changes: libgd2 (2.2.4-2+deb9u4) stretch-security; urgency=high . * Non-maintainer upload by the Security Team. * Heap-based buffer overflow in gdImageColorMatch (CVE-2019-6977) (Closes: #920645) * Potential double-free in gdImage*Ptr() (CVE-2019-6978) (Closes: #920728) Checksums-Sha1: fab60b8ba18d41caa1ede6f9c629b0fb023f9b80 2346 libgd2_2.2.4-2+deb9u4.dsc f2825f40ee181d22ac7c7a332662980f52484377 30244 libgd2_2.2.4-2+deb9u4.debian.tar.xz Checksums-Sha256: 10d21c630e27d5984d71ee8c9df57431438f4f9198975d27070f36f4b3bb1351 2346 libgd2_2.2.4-2+deb9u4.dsc 99207705ac51c2e6ec915987531feadfbd5ab3fabd6c97998501d866443f88ef 30244 libgd2_2.2.4-2+deb9u4.debian.tar.xz Files: 8caef9413ab03bc2a0dc20e372fea579 2346 graphics optional libgd2_2.2.4-2+deb9u4.dsc 7070ecdee544d47e607f223374593af4 30244 graphics optional libgd2_2.2.4-2+deb9u4.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxVaJhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EyNoP/1IXf8pwuoK04SRlYxiHYdwqCVVnVGSX bRmWaQUxLd4LHg4t6Pj2hS/mWNIg/DXfTIOrab/VTxjqFUEKgQjw4OOweUz9bz3q Gz9lUYcSInCExy/3UX6EYydOm6F/UzznCku+vFpIfUdHy9wKfXDqIe22euPpZfSi 6benz08PYbJ1NM++2PnUIZ8iWl5Ulbp9p7wYTPiXRUFfvKKsgPWsBdbHAo9I0jUW B8qxVc+QjZKGHqttTiG7X4IYn2eDZMBnWAslbGn/lxiUxUjUey0gElfX4MaxvjAZ k5Fx0UlD8zRjlrwjKG2PwZx4BBNhGuDQmJtzhfyFpZpckctNIZ0fyQxRHy00VpBI +BXcqkDvuBYNXoS7vDNGBqxjvizDmWuUMYTp8MxZYu5OmfU+IfI+sF5WC2ooocMq Emczm06rBPqAOC/j3sCJkK3jSqpNUG2EKI7LUioIBlKNfeRCeymE6VrIv2HpE+y2 azKNKzExePHsL3vONRAmENxTJjjH1MN4SPk+Ms675lb6s6s5IETcuRHAasb+Y4mQ w+iWVIRLjSlhfR8D6VUnpF/9jlLgmY6kKbs6plOpH8IaEpUfYzVX25Gs8+ohJWq2 mt0jnJ2uNCXTvFOJaAqhSYt9OTcQkpHTCUPPk28oE0N/fvSwBI6gtEgDWkNpS+tJ HJo8aLmJllgb =yNy+ -END PGP SIGNATURE End Message ---
Bug#909387: marked as done (erlang-mode: fails to install with xemacs21)
Your message dated Sat, 09 Feb 2019 21:47:20 +
with message-id
and subject line Bug#909387: fixed in erlang 1:19.2.1+dfsg-2+deb9u2
has caused the Debian Bug report #909387,
regarding erlang-mode: fails to install with xemacs21
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.)
--
909387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: erlang-mode
Version: 1:19.2.1+dfsg-2+deb9u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 1:20.3.8.5+dfsg-1
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
This happens in stretch, I cannot reproduce it in sid/buster.
>From the attached log (scroll to the bottom...):
Selecting previously unselected package erlang-mode.
Preparing to unpack .../erlang-mode_1%3a19.2.1+dfsg-2+deb9u1_all.deb ...
Unpacking erlang-mode (1:19.2.1+dfsg-2+deb9u1) ...
Setting up erlang-mode (1:19.2.1+dfsg-2+deb9u1) ...
Install emacsen-common for xemacs21
emacsen-common: Handling install of emacsen flavor xemacs21
Loading /usr/share/emacs/site-lisp/debian-startup...
Loading 00debian...
Loading site-start...
Loading 00debian-vars...
Loading 50erlang-mode...
Error while loading 50erlang-mode: Cannot open load file: erlang-start
Compiling /etc/xemacs21/site-start.d/00debian-vars.el...
Wrote /etc/xemacs21/site-start.d/00debian-vars.elc
Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
Done
Install erlang-mode for xemacs21
install/erlang: Handling install for emacsen flavor xemacs21
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-edoc.el...
While compiling erlang-edoc-xml-context in file
/usr/share/xemacs21/site-lisp/erlang/erlang-edoc.el:
!! File error (("Cannot open load file" "xmltok"))
>>Error occurred processing erlang-edoc.el: Cannot open load file: xmltok
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-eunit.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-eunit.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-skels-old.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-skels-old.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-skels.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-skels.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang-start.el...
Wrote /usr/share/xemacs21/site-lisp/erlang/erlang-start.elc
Compiling /usr/share/xemacs21/site-lisp/erlang/erlang.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/erlang/erlang.el:
** Third arg to defvar erlang-font-lock-keywords-1 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords-2 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords-3 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords-4 is not a string:
erlang-font-lock-descr-string
** Third arg to defvar erlang-font-lock-keywords is not a string:
erlang-font-lock-descr-string
While compiling erlang-version:
** reference to free variable erlang-version
While compiling erlang-mode:
** reference to free variable eldoc-documentation-function
While compiling erlang-syntax-table-init:
** reference to free variable erlang-mode-syntax-table
** assignment to free variable erlang-mode-syntax-table
While compiling erlang-mode-variables:
** reference to free variable erlang-defun-prompt-regexp
While compiling erlang-font-lock-init:
** reference to free variable erlang-font-lock-syntax-table
** reference to free variable erlang-mode-syntax-table
** assignment to free variable erlang-font-lock-syntax-table
** reference to free variable erlang-font-lock-keywords
** reference to free variable erlang-font-lock-keywords-1
** reference to free variable erlang-font-lock-keywords-2
** reference to free variable erlang-font-lock-keywords-3
** reference to free variable erlang-font-lock-keywords-4
While compiling erlang-font-lock-level-1:
** reference to free variable erlang-font-lock-keywords-1
While compiling erlang-font-lock-level-2:
** reference to free variable erlang-font-lock-keywords-2
While compiling erlang-font-lock-level-3:
** reference to free variable erlang-font-lock-keywords-3
While compiling
Bug#917085: marked as done (pyzo: missing dependancy to python3-pkg-resources)
Your message dated Sat, 09 Feb 2019 21:47:51 + with message-id and subject line Bug#917085: fixed in pyzo 4.3.1-1+deb9u1 has caused the Debian Bug report #917085, regarding pyzo: missing dependancy to python3-pkg-resources 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.) -- 917085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyzo Severity: important Dear Maintainer, Installing pyzo does not install pkg_resources which prevents from launching pyzo. Regards, J. -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.67-07156-gc116f2c8c400 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: pyzo Source-Version: 4.3.1-1+deb9u1 We believe that the bug you reported is fixed in the latest version of pyzo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated pyzo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Feb 2019 12:43:46 +0100 Source: pyzo Binary: pyzo pyzo-doc iep Architecture: source Version: 4.3.1-1+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Beckmann Description: iep- transitional dummy package for IEP pyzo - interactive editor for scientific Python pyzo-doc - documentation for Pyzo Closes: 917085 Changes: pyzo (4.3.1-1+deb9u1) stretch; urgency=medium . [ Andreas Beckmann] * Non-maintainer upload. * Backport dependency fix from 4.4.3-1.2. . [ Adrian Bunk ] * Add the missing dependency on python3-pkg-resources, thanks to Julien Cervelle. (Closes: #917085) Checksums-Sha1: 6e3fa7d0474bb14f6bb7e00c4a76e3ce7bfa618c 2154 pyzo_4.3.1-1+deb9u1.dsc fb97d4235bc8cf2aa630d4dd44bcab2f5d77fa56 13468 pyzo_4.3.1-1+deb9u1.debian.tar.xz 08308854139b2999598cfaa1c30eeec1b9fd75c9 6826 pyzo_4.3.1-1+deb9u1_source.buildinfo Checksums-Sha256: d32a7e01f59192c81c9d9399269a7d711fa7e4f53eeb25d3dcddf4dfb4c48092 2154 pyzo_4.3.1-1+deb9u1.dsc 0a903011c17719aa2dddb81046eca31478a95db54a9c0a2f4376755a1b0ada4d 13468 pyzo_4.3.1-1+deb9u1.debian.tar.xz cdb1099e6d2b99973641a97b8a822599fab490f2c9b748b300c670adbbfdcc42 6826 pyzo_4.3.1-1+deb9u1_source.buildinfo Files: 8f136eea2945c68820685793fb38cc01 2154 science optional pyzo_4.3.1-1+deb9u1.dsc f529222e6cbe986b10895e999d659a77 13468 science optional pyzo_4.3.1-1+deb9u1.debian.tar.xz 54de8918288bc229716abcb66bb0f72e 6826 science optional pyzo_4.3.1-1+deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxevgMQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCAtGD/9gpDZLy7d8Yr1X0rwUYT5DkPk/kJriy8Vl FT6HFkTKoY7+6eHyCbVhsVbEw3oR2s4DzXdA0uNQMI3086O+9YuEHAVl4NrMmTK2 yvKfo0opFfm+0+3J9+cFxG8/nkyvfDjQ4mgcHEzm1rjfy6QMQVCo1nHgdawM5EvZ pj+tjogsCmgxBar9EVuQtKwwQTWBm0dCgif4fUmriGyguIotFxHFaSFNEeF6U8xD XZBEkjbq2kjlfc+BzzYj5zIXWjh/qTigHWTYbNZwUZekoHqSpzRsknWdTQWWMkqR TGJmbfgnhZnyEXNq8rZBuCzqTfMGqYhujwaPEgRzpxERJVHdMET7IWjGNQuRFw// ZFWsjuziGEga5oTIqh8pBpN2kwy3HTUatuRGothY6eWJre2LyExEbB1i1I/IaFic ST3oYtdbRblbHKIzld+a1xn7kwETWtC0QdOLWy7CdQfpMNkeYhmgx9zuONfVhh87 l8+yTQxLARnf4nf3b8ZMQJlGwr0qOZPk2O06On8HLg7B9TBoN0EfAWf46u3mX/4h JOGWZlQa0ia2rLDkVqGsZh2KLqUvEZyrMmHba6q/o8JWpaEM8fRdXGjjSwEsARli c610r/pBOK6gpJKUNBATv+ZWHXKTeZQk97AD/zVPeCBDVPldh/5flIWjPJSgCSts Zo8WLU8/sg== =6gOP -END PGP SIGNATURE End Message ---
Bug#914944: marked as done (gnupg: importing a key fails when there's no tty (regression from 2.1.18-8~deb9u2))
Your message dated Sat, 09 Feb 2019 21:47:23 + with message-id and subject line Bug#913614: fixed in gnupg2 2.1.18-8~deb9u4 has caused the Debian Bug report #913614, regarding gnupg: importing a key fails when there's no tty (regression from 2.1.18-8~deb9u2) 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.) -- 913614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnupg Version: 2.1.18-8~deb9u3 Severity: normal Hi, Importing the attached key fails when there's no tty. To reproduce: works fine: gpg --import kameleon.gpg doesn't work: setsid sh -c 'gpg --import kameleon.gpg' &>log it fails with: gpg: cannot open '/dev/tty': No such device or address It worked fine with 2.1.18-8~deb9u2. It also works with 2.2.10-3~bpo9+1. It doesn't work with 2.1.18-8~deb9u3. So it looks like a regression in the recent stable update. Thanks Lucas -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg depends on: ii gnupg-agent2.1.18-8~deb9u3 ii libassuan0 2.4.3-2 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.24-11+deb9u3 ii libgcrypt201.7.6-2+deb9u3 ii libgpg-error0 1.26-2 ii libksba8 1.3.5-2 ii libreadline7 7.0-3 ii libsqlite3-0 3.16.2-5+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages gnupg recommends: ii dirmngr 2.1.18-8~deb9u3 pn gnupg-l10n Versions of packages gnupg suggests: pn parcimonie pn xloadimage -- no debconf information kameleon.gpg Description: application/pgp-keys --- End Message --- --- Begin Message --- Source: gnupg2 Source-Version: 2.1.18-8~deb9u4 We believe that the bug you reported is fixed in the latest version of gnupg2, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated gnupg2 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: Thu, 07 Feb 2019 15:57:27 -0500 Source: gnupg2 Binary: gnupg-agent scdaemon gpgsm gnupg gnupg2 gpgv gpgv2 dirmngr gpgv-udeb gpgv-static gpgv-win32 gnupg-l10n Architecture: source Version: 2.1.18-8~deb9u4 Distribution: stretch Urgency: medium Maintainer: Debian GnuPG Maintainers Changed-By: Daniel Kahn Gillmor Description: dirmngr- GNU privacy guard - network certificate management service gnupg - GNU privacy guard - a free PGP replacement gnupg-agent - GNU privacy guard - cryptographic agent gnupg-l10n - GNU privacy guard - localization files gnupg2 - GNU privacy guard - a free PGP replacement (dummy transitional pa gpgsm - GNU privacy guard - S/MIME version gpgv - GNU privacy guard - signature verification tool gpgv-static - minimal signature verification tool (static build) gpgv-udeb - minimal signature verification tool (udeb) gpgv-win32 - GNU privacy guard - signature verification tool (win32 build) gpgv2 - GNU privacy guard - signature verification tool (dummy transition scdaemon - GNU privacy guard - smart card support Closes: 913614 Changes: gnupg2 (2.1.18-8~deb9u4) stretch; urgency=medium . * Avoid crash when importing without a TTY (Closes: #913614) Checksums-Sha1: b7c5cac094e05c9320e71fdb4be3eeac7e884037 2561 gnupg2_2.1.18-8~deb9u4.dsc 5c4e4ed9df261e16bd72f3207dae6b05a81df7c9 122023 gnupg2_2.1.18-8~deb9u4.debian.tar.bz2 8171ee3f8b9cb800ed036aed32806794d7f8dcb5 10499 gnupg2_2.1.18-8~deb9u4_source.buildinfo Checksums-Sha256: e42240a13af866a3c9db1704bfbbd2230abb071dca3c24d7c2a3b27e94d8aaa3 2561 gnupg2_2.1.18-8~deb9u4.dsc 81f6cf52bc22d77332a413ec2cd423e2127faea950705b50b50f84c8ed43521e 122023 gnupg2_2.1.18-8~deb9u4.debian.tar.bz2 b7feecce6ac92226b15188555eab65169f38ac2d283c65af50a02f0e9adb0715 10499
Bug#920645: marked as done (libgd2: CVE-2019-6977)
Your message dated Sat, 09 Feb 2019 21:47:26 + with message-id and subject line Bug#920645: fixed in libgd2 2.2.4-2+deb9u4 has caused the Debian Bug report #920645, regarding libgd2: CVE-2019-6977 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.) -- 920645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgd2 Version: 2.2.5-5 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 2.2.4-2+deb9u3 Control: found -1 2.2.4-2 Hi, The following vulnerability was published for libgd2. CVE-2019-6977[0]: | gdImageColorMatch in gd_color_match.c in the GD Graphics Library (aka | LibGD) 2.2.5, as used in the imagecolormatch function in PHP before | 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1, | has a heap-based buffer overflow. This can be exploited by an attacker | who is able to trigger imagecolormatch calls with crafted image data. 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-6977 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6977 [1] https://bugs.php.net/bug.php?id=77270 [2] https://gist.github.com/cmb69/1f36d285eb297ed326f5c821d7aafced Regards, Salvatore --- End Message --- --- Begin Message --- Source: libgd2 Source-Version: 2.2.4-2+deb9u4 We believe that the bug you reported is fixed in the latest version of libgd2, 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. Salvatore Bonaccorso (supplier of updated libgd2 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, 02 Feb 2019 10:49:03 +0100 Source: libgd2 Binary: libgd-tools libgd-dev libgd3 Architecture: source Version: 2.2.4-2+deb9u4 Distribution: stretch-security Urgency: high Maintainer: GD team Changed-By: Salvatore Bonaccorso Closes: 920645 920728 Description: libgd-dev - GD Graphics Library (development version) libgd-tools - GD command line tools and example code libgd3 - GD Graphics Library Changes: libgd2 (2.2.4-2+deb9u4) stretch-security; urgency=high . * Non-maintainer upload by the Security Team. * Heap-based buffer overflow in gdImageColorMatch (CVE-2019-6977) (Closes: #920645) * Potential double-free in gdImage*Ptr() (CVE-2019-6978) (Closes: #920728) Checksums-Sha1: fab60b8ba18d41caa1ede6f9c629b0fb023f9b80 2346 libgd2_2.2.4-2+deb9u4.dsc f2825f40ee181d22ac7c7a332662980f52484377 30244 libgd2_2.2.4-2+deb9u4.debian.tar.xz Checksums-Sha256: 10d21c630e27d5984d71ee8c9df57431438f4f9198975d27070f36f4b3bb1351 2346 libgd2_2.2.4-2+deb9u4.dsc 99207705ac51c2e6ec915987531feadfbd5ab3fabd6c97998501d866443f88ef 30244 libgd2_2.2.4-2+deb9u4.debian.tar.xz Files: 8caef9413ab03bc2a0dc20e372fea579 2346 graphics optional libgd2_2.2.4-2+deb9u4.dsc 7070ecdee544d47e607f223374593af4 30244 graphics optional libgd2_2.2.4-2+deb9u4.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlxVaJhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EyNoP/1IXf8pwuoK04SRlYxiHYdwqCVVnVGSX bRmWaQUxLd4LHg4t6Pj2hS/mWNIg/DXfTIOrab/VTxjqFUEKgQjw4OOweUz9bz3q Gz9lUYcSInCExy/3UX6EYydOm6F/UzznCku+vFpIfUdHy9wKfXDqIe22euPpZfSi 6benz08PYbJ1NM++2PnUIZ8iWl5Ulbp9p7wYTPiXRUFfvKKsgPWsBdbHAo9I0jUW B8qxVc+QjZKGHqttTiG7X4IYn2eDZMBnWAslbGn/lxiUxUjUey0gElfX4MaxvjAZ k5Fx0UlD8zRjlrwjKG2PwZx4BBNhGuDQmJtzhfyFpZpckctNIZ0fyQxRHy00VpBI +BXcqkDvuBYNXoS7vDNGBqxjvizDmWuUMYTp8MxZYu5OmfU+IfI+sF5WC2ooocMq Emczm06rBPqAOC/j3sCJkK3jSqpNUG2EKI7LUioIBlKNfeRCeymE6VrIv2HpE+y2 azKNKzExePHsL3vONRAmENxTJjjH1MN4SPk+Ms675lb6s6s5IETcuRHAasb+Y4mQ w+iWVIRLjSlhfR8D6VUnpF/9jlLgmY6kKbs6plOpH8IaEpUfYzVX25Gs8+ohJWq2 mt0jnJ2uNCXTvFOJaAqhSYt9OTcQkpHTCUPPk28oE0N/fvSwBI6gtEgDWkNpS+tJ HJo8aLmJllgb =yNy+ -END PGP SIGNATURE End Message ---
Bug#905908: marked as done (libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3)
Your message dated Sat, 09 Feb 2019 21:47:22 + with message-id and subject line Bug#905908: fixed in glx-alternatives 0.8.8~deb9u1 has caused the Debian Bug report #905908, regarding libGL.so.1: cannot open shared object file: No such file or directory when updating to 4.4.1~rc2-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 905908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: octave Version: 4.4.1~rc2-3 Severity: serious Justification: Policy 3.5 Dear Maintainer, When updating octave to 4.4.1~rc2-3, I received the following error: Setting up octave (4.4.1~rc2-3) ... /usr/bin/octave-cli: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory dpkg: error processing package octave (--configure): installed octave package post-installation script subprocess returned error exit status 127 It appears to be missing a dependency on a package that provides libGL. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages octave depends on: ii libamd21:5.3.0+dfsg-1 ii libarpack2 3.6.2-1 ii libasound2 1.1.6-1 ii libblas3 [libblas.so.3]3.8.0-1+b1 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.27-5 ii libcamd2 1:5.3.0+dfsg-1 ii libccolamd21:5.3.0+dfsg-1 ii libcholmod31:5.3.0+dfsg-1 ii libcolamd2 1:5.3.0+dfsg-1 ii libcxsparse3 1:5.3.0+dfsg-1 ii libfftw3-double3 3.3.8-1 ii libfftw3-single3 3.3.8-1 ii libfltk-gl1.3 1.3.4-7 ii libfltk1.3 1.3.4-7 ii libfreetype6 2.8.1-2 ii libgcc11:8.2.0-3 ii libgl1 1.0.0+git20180308-4 ii libglpk40 4.65-2 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libgomp1 8.2.0-3 ii libklu11:5.3.0+dfsg-1 ii liblapack3 [liblapack.so.3]3.8.0-1+b1 ii liboctave5 4.4.1~rc2-3 ii libopenblas-base [liblapack.so.3] 0.3.2+ds-1 ii libportaudio2 19.6.0-1 ii libqhull7 2015.2-4 ii libqrupdate1 1.1.2-2+b2 ii libqscintilla2-qt5-13 2.10.4+dfsg-1+b1 ii libqt5core5a 5.11.1+dfsg-6 ii libqt5gui5 5.11.1+dfsg-6 ii libqt5help55.11.1-5 ii libqt5network5 5.11.1+dfsg-6 ii libqt5opengl5 5.11.1+dfsg-6 ii libqt5printsupport55.11.1+dfsg-6 ii libqt5sql5 5.11.1+dfsg-6 ii libqt5widgets5 5.11.1+dfsg-6 ii libsndfile11.0.28-4 ii libstdc++6 8.2.0-3 ii libsuitesparseconfig5 1:5.3.0+dfsg-1 ii libumfpack51:5.3.0+dfsg-1 ii libx11-6 2:1.6.5-1 ii octave-common 4.4.1~rc2-3 ii texinfo6.5.0.dfsg.1-4 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages octave recommends: ii default-jre-headless 2:1.10-68 ii epstool 3.08+repack-7 ii gnuplot-qt [gnuplot-nox] 5.2.2+dfsg1-2 ii libopenblas-base 0.3.2+ds-1 ii octave-doc4.4.1~rc2-3 ii pstoedit 3.73-1+b1 Versions of packages octave suggests: pn liboctave-dev -- no debconf information --- End Message --- --- Begin Message --- Source: glx-alternatives Source-Version: 0.8.8~deb9u1 We believe that the bug you reported is fixed in the latest version of glx-alternatives, 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
Bug#881342: marked as done (rtkit: should depend on dbus and polkit)
Your message dated Sat, 09 Feb 2019 21:47:51 + with message-id and subject line Bug#881342: fixed in rtkit 0.11-4+deb9u1 has caused the Debian Bug report #881342, regarding rtkit: should depend on dbus and polkit 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.) -- 881342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dbus Version: 1.10.22-0+deb9u1 Severity: important Dear Maintainer, * What led up to the situation? Tried to install xorg hexchat k3b dolphin kdenlive gimp inkscape libreoffice calibre xpdf kate conky mplayer vlc using apt-get. It hung on: Setting up libkf5windowsystem-data (5.28.0-2) ... Setting up kde-runtime-data (4:16.08.3-2) ... Setting up libsodium18:amd64 (1.0.11-2) ... Setting up xml-core (0.17) ... Setting up javascript-common (11) ... Setting up libbdplus0:amd64 (0.1.2-2) ... Setting up libbcprov-java (1.56-1) ... sed: can't read /etc/java/security/classpath.security: No such file or directory Setting up libmad0:amd64 (0.15.1b-8) ... Setting up dbus (1.10.22-0+deb9u1) ... * What exactly did you do (or not do) that was effective (or ineffective)? Tried to kill dpkg since Ctrl-c wasn't working root 3173 0.0 0.0 0 0 ?S19:14 0:03 [kworker/0:0] root 3367 0.0 0.1 49880 3588 tty2 S+ 19:31 0:00 sudo apt-get install xorg k3b dolphin hexchat kdenlive libreoffice kate xpdf calibre conky mplayer vlc root 3368 0.3 2.3 92772 48196 tty2 S+ 19:31 0:09 apt-get install xorg k3b dolphin hexchat kdenlive libreoffice kate xpdf calibre conky mplayer vlc root 9805 0.0 0.0 0 0 ?S19:45 0:00 [kworker/u4:2] root 14407 0.0 0.3 26152 7200 pts/0Ss+ 19:50 0:00 /usr/bin/dpkg --status-fd 23 --configure --pending root 17742 0.0 0.0 0 0 ?S19:53 0:00 [kworker/1:0] * What was the outcome of this action? E: Sub-process /usr/bin/dpkg exited unexpectedly W: Operation was interrupted before it could finish * What outcome did you expect instead? The same LOGS--- daemon.log Nov 10 17:39:59 deathstar systemd[1]: Starting Cleanup of Temporary Directories... Nov 10 17:40:00 deathstar systemd[1]: Started Cleanup of Temporary Directories. Nov 10 19:06:55 deathstar systemd[1]: Reloading. Nov 10 19:06:56 deathstar systemd[1]: Reloading. Nov 10 19:06:58 deathstar systemd[1]: Reloading. Nov 10 19:07:45 deathstar systemd[1]: Reloading. Nov 10 19:07:47 deathstar systemd[1]: Reloading. Nov 10 19:07:47 deathstar systemd[1]: Reloading. Nov 10 19:08:35 deathstar systemd[1]: Reloading. Nov 10 19:08:35 deathstar systemd[1]: Reloading. Nov 10 19:08:36 deathstar systemd[1]: Reloading. Nov 10 19:08:57 deathstar systemd[1]: Reloading. Nov 10 19:08:57 deathstar systemd[1]: Reloading. Nov 10 19:08:57 deathstar systemd[1]: Reloading. Nov 10 19:08:58 deathstar systemd[1]: Reloading. Nov 10 19:39:24 deathstar systemd[1]: Reloading. Nov 10 19:39:24 deathstar systemd[1]: Reloading. Nov 10 19:43:35 deathstar systemd[1]: Mounting FUSE Control File System... Nov 10 19:43:35 deathstar systemd[1]: Mounted FUSE Control File System. Nov 10 19:49:43 deathstar systemd[1]: Reloading. Nov 10 19:51:02 deathstar systemd-udevd[233]: specified user 'usbmux' unknown Nov 10 19:52:01 deathstar systemd[1]: Reloading. Nov 10 19:52:01 deathstar systemd[1]: Reloading. Nov 10 19:52:01 deathstar systemd[1]: Listening on D-Bus System Message Bus Socket. Nov 10 19:52:01 deathstar systemd[1]: Starting RealtimeKit Scheduling Policy Service... Nov 10 19:52:01 deathstar systemd[1]: Started D-Bus System Message Bus. Nov 10 19:52:01 deathstar dbus-daemon[17738]: Failed to start message bus: Could not get UID and GID for username "messagebus" Nov 10 19:52:26 deathstar systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.RealtimeKit1': Connection timed out Nov 10 19:52:26 deathstar systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.login1': Connection timed out Nov 10 19:52:26 deathstar systemd[1]: Failed to subscribe to activation signal: Connection timed out Nov 10 19:52:26 deathstar systemd[1]: Failed to register name: Connection timed out Nov 10 19:52:26 deathstar systemd[1]: Failed to set up API bus: Connection timed out Nov 10 19:52:26 deathstar systemd[1]: dbus.service: Main process exited, code=exited, status=1/FAILURE Nov 10 19:52:26 deathstar systemd[1]: dbus.service: Unit entered failed state. Nov
Bug#914440: marked as done (photocollage: ValueError: Namespace Gtk not available)
Your message dated Sat, 09 Feb 2019 21:47:47 +
with message-id
and subject line Bug#914440: fixed in photocollage 1.4.3-2.1~deb9u1
has caused the Debian Bug report #914440,
regarding photocollage: ValueError: Namespace Gtk not available
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.)
--
914440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: photocollage
Version: 1.4.3-2
Severity: grave
Dear Maintainer,
I get the following error, when I try to start photocollage.
$ photocollage
Traceback (most recent call last):
File "/usr/bin/photocollage", line 21, in
from photocollage import gtkgui
File "/usr/lib/python3/dist-packages/photocollage/gtkgui.py", line 28, in
gi.require_version('Gtk', '3.0') # noqa
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages photocollage depends on:
ii python3 3.5.3-1
ii python3-gi-cairo 3.22.0-2
ii python3-pil 4.0.0-4
ii python3-six 1.10.0-3
photocollage recommends no packages.
photocollage suggests no packages.
-- no debconf information
Best regards,
Robert Pommrich
--- End Message ---
--- Begin Message ---
Source: photocollage
Source-Version: 1.4.3-2.1~deb9u1
We believe that the bug you reported is fixed in the latest version of
photocollage, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated photocollage package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 09 Feb 2019 09:04:00 +0100
Source: photocollage
Binary: photocollage
Architecture: source
Version: 1.4.3-2.1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Adrien Vergé
Changed-By: Andreas Beckmann
Description:
photocollage - Graphical tool to make photo collage posters
Closes: 914440
Changes:
photocollage (1.4.3-2.1~deb9u1) stretch; urgency=medium
.
* Non-maintainer upload.
* Rebuild for stretch.
.
photocollage (1.4.3-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add the missing dependency on gir1.2-gtk-3.0. (Closes: #914440)
Checksums-Sha1:
fd5ba68c29cb1f4fd9053c6e957c20b3df544204 1842 photocollage_1.4.3-2.1~deb9u1.dsc
55744d8061c4162bef661d0db17286ac34bf7ee7 8224
photocollage_1.4.3-2.1~deb9u1.debian.tar.xz
ea5998c62f0b48cfca62fa47ee462717196e85e6 6072
photocollage_1.4.3-2.1~deb9u1_source.buildinfo
Checksums-Sha256:
548a00cd1618631485a8a7ee94557d5c46570bc55aaf31d64eb3994dbdaa827a 1842
photocollage_1.4.3-2.1~deb9u1.dsc
8c78cc7aa0bcf7d46afac330019d935ee871e19c7c04e8d448f856702eee9792 8224
photocollage_1.4.3-2.1~deb9u1.debian.tar.xz
b12038819a866407182c7639b637bdddf6ae5674ea0f84f1c3bec719c110415c 6072
photocollage_1.4.3-2.1~deb9u1_source.buildinfo
Files:
bd3d467982e31d2294cc5c18ec24b728 1842 graphics optional
photocollage_1.4.3-2.1~deb9u1.dsc
d0125fe20f81d286ae1d3b1d29e8ae44 8224 graphics optional
photocollage_1.4.3-2.1~deb9u1.debian.tar.xz
5ffe25c0aa4df7aed0d96e3347bf65ea 6072 graphics optional
photocollage_1.4.3-2.1~deb9u1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxeiqwQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCAiyD/oD1ZmZr3HD+8XtqH/5zawzrRz4e0+4FK4+
kTYU1ml19dJGyeCQl296J2lKjdgc8JyBU4pqq07nq+HfwncDfGQzM4xYNGo54qbj
0GlWBYI1AAoc8WeguIDHZhXRHRqgn/n6V32WWz8yea3ThzwZVea4Bu4MNIB+aM5T
ithn5OEzgSIhLIRH9l1fMK0Oi5nd4cDAxSu+a/kaof27p0pmzLewq8H5NNkUUViV
a5fEqrU7In91uLSUiK2gVgBpXwS1K/It/+Fpl/u5LZhxT/4Iq/u+f2nUC3Pp/Q75
Bug#880047: marked as done (postgrey doesn't start because it can't write its pid)
Your message dated Sat, 09 Feb 2019 21:47:50 + with message-id and subject line Bug#880047: fixed in postgrey 1.36-3+deb9u2 has caused the Debian Bug report #880047, regarding postgrey doesn't start because it can't write its pid 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.) -- 880047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgrey Version: 1.36-3 Severity: grave Justification: renders package unusable Dear Maintainer, The default init script that comes with Postgrey on Debian 9 fails to start after a reboot. The installer creates /var/run/postgrey and writes its pid there but /var/run is a tmpfs file system and so on a reboot /var/run/postgrey ceases to exist. The init script for Postgrey does not attempt to create /var/run/postgrey and just fails to start when it can't write to /var/run/postgrey. When postgrey fails to start then Postfix starts complaining that it is misconfigured and begins bouncing emails. I was able to fix this by adding these lines to the do_start function in the init script: # Assure that /var/run/postgrey exists [ -d /var/run/postgrey ] || mkdir -p /var/run/postgrey if [ "$DAEMON_USER" != "root" ]; then chown "$DAEMON_USER" /var/run/postgrey fi -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgrey depends on: ii adduser3.115 ii debconf [debconf-2.0] 1.5.61 pn libberkeleydb-perl pn libnet-dns-perl pn libnet-server-perl pn libnetaddr-ip-perl ii perl 5.24.1-3+deb9u2 ii ucf3.0036 Versions of packages postgrey recommends: pn libnet-rblclient-perl pn libparse-syslog-perl ii postfix3.1.6-0+deb9u1 postgrey suggests no packages. --- End Message --- --- Begin Message --- Source: postgrey Source-Version: 1.36-3+deb9u2 We believe that the bug you reported is fixed in the latest version of postgrey, 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 880...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated postgrey 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, 09 Feb 2019 15:37:36 +0200 Source: postgrey Binary: postgrey Architecture: source Version: 1.36-3+deb9u2 Distribution: stretch Urgency: medium Maintainer: Antonio Radici Changed-By: Adrian Bunk Description: postgrey - greylisting implementation for Postfix Closes: 756813 880047 Changes: postgrey (1.36-3+deb9u2) stretch; urgency=medium . * Non-maintainer upload. * Revert the 1.36-3+deb9u1 change due to regression. (see #880047) . postgrey (1.36-3+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * debian/postgrey.init: create /var/run/postgrey if it does not exist, patch provided by Laurent Bigonville . (Closes: 756813, 880047) Checksums-Sha1: 3fe66346d4012775110c4a0c81129a8a6d39ea5f 1957 postgrey_1.36-3+deb9u2.dsc ce31fed428efecb8b0850c7d4111468e25ad2fd6 22164 postgrey_1.36-3+deb9u2.debian.tar.xz Checksums-Sha256: bc022b0906616ef8427e5afc381bed0c95414a866bca54bc22b092ecddd81617 1957 postgrey_1.36-3+deb9u2.dsc f254ed7d96e586317627867376921c5f4f51e1b190f2300de2f97e5766c8eaf8 22164 postgrey_1.36-3+deb9u2.debian.tar.xz Files: 04e67da31e16843c1d2a9c2cc9aa007e 1957 mail optional postgrey_1.36-3+deb9u2.dsc d874eb8893e4c295d75da1fdb228684c 22164 mail optional postgrey_1.36-3+deb9u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlxe2dIACgkQiNJCh6LY mLECnBAAx2EkmZOowELINd8JmSswqFS4kb+Pl8PHt+PJQa5HjP4NJReg4WHQuRrX 1NJz5atFEMi/wfAa1JMc/CRUDuYvDR9ItbEipbL6KthPT21pfIzMpqRY7KSNErBc
Bug#873719: marked as done (/usr/bin/sc-libtool: Command not found)
Your message dated Sat, 09 Feb 2019 21:47:32 + with message-id and subject line Bug#873719: fixed in mpqc 2.3.1-18+deb9u1 has caused the Debian Bug report #873719, regarding /usr/bin/sc-libtool: Command not found 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.) -- 873719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsc-dev Version: 2.3.1-16 Severity: important Tags: patch Dear Maintainer, libsc-dev contains sc-config and it calls sc-libtool, however, package doesn't contain it. Attached patch will fix it, could you check and apply it, please? P.S. Upstream moves to GitHub, you may have to update with it. https://github.com/ValeevGroup/mpqc diff -Nru mpqc-2.3.1/debian/changelog mpqc-2.3.1/debian/changelog --- mpqc-2.3.1/debian/changelog 2017-01-21 21:20:39.0 +0900 +++ mpqc-2.3.1/debian/changelog 2017-08-30 21:45:03.0 +0900 @@ -1,3 +1,11 @@ +mpqc (2.3.1-18.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * debian/libsc-dev.install +- Don't miss sc-libtool to install + + -- Hideki Yamane Wed, 30 Aug 2017 21:45:03 +0900 + mpqc (2.3.1-18) unstable; urgency=medium * Team upload. diff -Nru mpqc-2.3.1/debian/libsc-dev.install mpqc-2.3.1/debian/libsc-dev.install --- mpqc-2.3.1/debian/libsc-dev.install 2014-11-01 18:38:13.0 +0900 +++ mpqc-2.3.1/debian/libsc-dev.install 2017-08-30 21:45:03.0 +0900 @@ -1,5 +1,5 @@ usr/bin/scls usr/bin/scpr -usr/bin/sc-config +usr/bin/sc-* usr/lib/*so usr/include/sc --- End Message --- --- Begin Message --- Source: mpqc Source-Version: 2.3.1-18+deb9u1 We believe that the bug you reported is fixed in the latest version of mpqc, 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 873...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated mpqc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Feb 2019 14:24:50 +0100 Source: mpqc Binary: mpqc mpqc-openmpi libsc-dev libsc7v5 libsc-data libsc-doc mpqc-support Architecture: source Version: 2.3.1-18+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debichem Team Changed-By: Andreas Beckmann Description: libsc-data - Scientific Computing Toolkit (basis set and atom data) libsc-dev - Scientific Computing Toolkit (development files) libsc-doc - Scientific Computing Toolkit (documentation) libsc7v5 - Scientific Computing Toolkit (library) mpqc - Massively Parallel Quantum Chemistry Program mpqc-openmpi - Massively Parallel Quantum Chemistry Program (OpenMPI transitiona mpqc-support - Massively Parallel Quantum Chemistry Program (support tools) Closes: 873719 Changes: mpqc (2.3.1-18+deb9u1) stretch; urgency=medium . [ Andreas Beckmann ] * Non-maintainer upload. * Backport the sc-libtool fix from 2.3.1-19. . [ Michael Banck ] * debian/libsc-dev.install: Install sc-libtool as well, thanks to Hideki Yamane (closes: #873719). Checksums-Sha1: 2951dec6c85ecc1584d4c783a4d5015e0bbd897c 2389 mpqc_2.3.1-18+deb9u1.dsc 051d19e4b4c539549c74f72e4a9ccca4e4fcf7ef 29692 mpqc_2.3.1-18+deb9u1.debian.tar.xz ea872cd04b44427ac64c898c5dc108f2e2ee7af9 7496 mpqc_2.3.1-18+deb9u1_source.buildinfo Checksums-Sha256: a5d4d8c54ca4a9a4b7c989909c5654bc051b38356b8afa00f45cb09688413975 2389 mpqc_2.3.1-18+deb9u1.dsc c17171bf60a17d20930c6e25d30c0be606e65dc11e42d6318f5fdb70faaa0986 29692 mpqc_2.3.1-18+deb9u1.debian.tar.xz d584200d4265003a2d2c948cf32654df83f6ec972ac927482f9c5750b9aef99d 7496 mpqc_2.3.1-18+deb9u1_source.buildinfo Files: acf83ed87f3582e4dca4aaefc9053a2f 2389 science optional mpqc_2.3.1-18+deb9u1.dsc 87053f661502f77740187fcb6d27fcfa 29692 science optional mpqc_2.3.1-18+deb9u1.debian.tar.xz 0ff97d4dd74b3e1e71d88ae1edb6e1b9 7496 science optional mpqc_2.3.1-18+deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxe4BkQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCIVvD/oDUBdiY+FQjb9viNduZqBF383QmIYF0K7s amqAXOTHq9Xh4RoD6OHc2q/j14Jdikd69jEPOE44k6ZkClHn0k3mM+K3UDi5Kv5+
Bug#867418: marked as done (python3-arpy: missing python3 dependency)
Your message dated Sat, 09 Feb 2019 21:47:50 +
with message-id
and subject line Bug#867418: fixed in python-arpy 1.1.1-3~deb9u1
has caused the Debian Bug report #867418,
regarding python3-arpy: missing python3 dependency
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
867418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-arpy
Version: 1.1.1-2
Severity: serious
Tags: patch
Due to a cut'n'paste error the python3 dependency is missing.
Fix:
--- debian/control.old 2017-07-06 15:16:11.0 +
+++ debian/control 2017-07-06 15:16:20.0 +
@@ -28,7 +28,7 @@
Architecture: all
Depends: ${shlibs:Depends},
${misc:Depends},
- ${python:Depends}
+ ${python3:Depends}
Provides: ${python:Provides}
Description: library for accessing "ar" archives
arpy is a library for accessing the archive files and reading the
--- End Message ---
--- Begin Message ---
Source: python-arpy
Source-Version: 1.1.1-3~deb9u1
We believe that the bug you reported is fixed in the latest version of
python-arpy, 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 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated python-arpy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 09 Feb 2019 15:43:08 +0100
Source: python-arpy
Binary: python-arpy python3-arpy
Architecture: source
Version: 1.1.1-3~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Andreas Beckmann
Description:
python-arpy - library for accessing "ar" archives
python3-arpy - library for accessing "ar" archives
Closes: 867418
Changes:
python-arpy (1.1.1-3~deb9u1) stretch; urgency=medium
.
* Non-maintainer upload.
* Rebuild for stretch.
.
python-arpy (1.1.1-3) unstable; urgency=low
.
* Team upload.
.
[ Christoph Egger ]
* Add VCS-* headers
.
[ Ondřej Nový ]
* Fixed homepage (https)
* Fixed VCS URL (https)
.
[ Scott Kitterman ]
* Correct substitution variable for python3 interpreter depends (Closes:
#867418)
* Remove unneeded python:Provides
* Update homepage for move to github
* Add debian/watch
Checksums-Sha1:
fc558e688e4026cbdbfdfd6a998584223ebe4d9d 2178 python-arpy_1.1.1-3~deb9u1.dsc
5afd542123584affa2691cfa82de2e5ffd2d5e99 2600
python-arpy_1.1.1-3~deb9u1.debian.tar.xz
23275a741df759157c4291fefd88705a69e7e90c 6478
python-arpy_1.1.1-3~deb9u1_source.buildinfo
Checksums-Sha256:
3bb881df3271b230d2b900a98c8d6d12f38b70eb74b0d333f1d21890aacce929 2178
python-arpy_1.1.1-3~deb9u1.dsc
445a12aad2441e436caaa8c9cc6dc313b5dad5b4cdc128e8d0b40392bc69ec39 2600
python-arpy_1.1.1-3~deb9u1.debian.tar.xz
08d62664f284b30b438da8af0d51a363d889abe04e364e18e83a83f18ffe186c 6478
python-arpy_1.1.1-3~deb9u1_source.buildinfo
Files:
e85ffa6797cc0cba9f7d6d581e2185cd 2178 python optional
python-arpy_1.1.1-3~deb9u1.dsc
b1cd6d4fbe0140053e85b187c6c27acd 2600 python optional
python-arpy_1.1.1-3~deb9u1.debian.tar.xz
71c1a0ee8af9577610a397a88c62f2d4 6478 python optional
python-arpy_1.1.1-3~deb9u1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxe6RwQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCOgID/0Wz2eWyvORq2lIxzwVV2pIJrTKGPrMj8V5
J1ghIueG4d0cutZ2MP8fpvu8yKxe4dLzb6yvy34dXEVjK0K3WuzaFGiY2DcX5GfF
AURS5iwahLopjj9JYfTnkIDSb45kYgIPov+8eKgbaeSHAq14IWpxL8YB0o34LBHq
3BIN9oyxhWkLOjiQha0tIP9JEp1itAu7ljmB5paWJ3bWP7CZ9Eb5fpAKXALpWHg9
a8DGIv2CIYpe7cPJugjfXSHUO0uYFpjtNOsBH7amT3athIwuJ9Krr3EcpJyYnMLo
/WFmavlPc5NYolqsg9F4ytpGyzWvGUBO/3Gn6JA+XImuYVD7C9/XfYdc3pgvohbH
yICtnUTNkogj9xdN36ZksPpRAZji6KIw6+yTexxixxLod+s7t5X8rS8wr3mhUeLh
qc84rTKwUJjLLAZxbV1qReGepl7zln25kUQsYJwUmPCVkGSCspG6r8pq/IuKRqmh
Hs2DxG/7teA3kta7o0QY9VhJbxQmlxTXvZGGyoLz6qz8OgipJLMCXIxLJNViNyg7
d+8e76tvzIncq7EWrA7lN1htbziDTFWejc6saQOeoZ0dBjGRfHHeGIJKg6V++N/n
FUJ/idJsSihId0f/o4BqFqGY58W9hn1rXyCqUkbP+tRj2XAUHUu+jbRosFaAc4wU
5e5Q/mmTFg==
=Rx0S
-END PGP SIGNATURE End Message ---
Bug#909385: marked as done (vm: fails to install with xemacs21)
Your message dated Sat, 09 Feb 2019 21:47:53 + with message-id and subject line Bug#909385: fixed in vm 8.2.0b-2.1+deb9u1 has caused the Debian Bug report #909385, regarding vm: fails to install with xemacs21 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.) -- 909385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vm Version: 8.2.0b-2.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: fixed -1 8.2.0b-3 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. This happens in stretch, I cannot reproduce it in sid/buster. >From the attached log (scroll to the bottom...): Setting up vm (8.2.0b-2.1) ... Install emacsen-common for xemacs21 emacsen-common: Handling install of emacsen flavor xemacs21 Loading /usr/share/emacs/site-lisp/debian-startup... Loading 00debian... Loading site-start... Loading 00debian-vars... Loading 50vm... Compiling /etc/xemacs21/site-start.d/00debian-vars.el... Wrote /etc/xemacs21/site-start.d/00debian-vars.elc Compiling /usr/share/xemacs21/site-lisp/debian-startup.el... Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc Done Install vm for xemacs21 install/vm: Byte-compiling for xemacs21...ERROR: install script from vm package failed dpkg: error processing package vm (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: vm cheers, Andreas vm=8.2.0b-2.1_xemacs21.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: vm Source-Version: 8.2.0b-2.1+deb9u1 We believe that the bug you reported is fixed in the latest version of vm, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated vm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 08 Feb 2019 20:02:36 +0100 Source: vm Binary: vm Architecture: source Version: 8.2.0b-2.1+deb9u1 Distribution: stretch Urgency: medium Maintainer: Manoj Srivastava Changed-By: Andreas Beckmann Description: vm - mail user agent for Emacs Closes: 909385 Changes: vm (8.2.0b-2.1+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * Backport removal of xemacs21 support from 8.2.0b-4. (Closes: #909385) . [ Ian Jackson ] * Drop support for xemacs21, which is broken - see #914945. Checksums-Sha1: dced0888a985919c73086afc074521305dfb1582 1950 vm_8.2.0b-2.1+deb9u1.dsc 64482f03490310340e2e7e0a071ca3ee0a8eb25b 103430 vm_8.2.0b-2.1+deb9u1.diff.gz cc51fd49e3c49b2c560a082d63eb3fb12f78128d 4590 vm_8.2.0b-2.1+deb9u1_source.buildinfo Checksums-Sha256: c9233fb4038657fa194772258835963ddf595e4322e4fbc87fa04f3e06eb08ce 1950 vm_8.2.0b-2.1+deb9u1.dsc e860a3a208f05d509f2ded166732ea6ad004ca6f41a1b71804b90a757b54a16b 103430 vm_8.2.0b-2.1+deb9u1.diff.gz 83441e0abf51b89c0aeca2ad30169b56e52fc671c04641dac19832407fcff789 4590 vm_8.2.0b-2.1+deb9u1_source.buildinfo Files: e8b5874ee221a63d78849ed06ac96fda 1950 mail optional vm_8.2.0b-2.1+deb9u1.dsc e090e034a2d8b1e49f66043d7f335df7 103430 mail optional vm_8.2.0b-2.1+deb9u1.diff.gz 763a7f3a38a4c068acd021ab9e60c661 4590 mail optional vm_8.2.0b-2.1+deb9u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlxd030QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCOyKEACwSQg3lppnSwH9EraJ2mZHvKQCVkTo15Cv zJhsjOqVPZ/5d0xpA1w4YE1BfgkgvjtNFF/yLMOS5H0i05PPnLbMARep6dNrMymL W79A0LKbe9kbFUsglgOhvhueR+FYbwEcJm5D07ydrldK8IXj3x+1e0HerrRgNNur eASN8UyyM3aGWJ35Ul/zxm0ESaJq/jXR2g2JuP+QWiZ1YkfFgyzgU5xASLSywFk7 FYUXjZX6EOuY0ARoN+/4wNVcB6wCES2cgv4UpukP6/ITwTIXPbDmTXODBx960/vU ko+TqjoR0DTp6ES8PHfuB3gLsZ8JKN67BKYsXBp6VM0SC7uIbhMJaGkHap6nkT2y fEWTU1H8C9hTBSeEJD6c0mw4ZidzRSUV9RzBW9ZHVagjrbGR7+6OG/R1PRE1aS1l dg2Xbc+5EartAwixx6bcq63pA7TfpdEk3HaL6/wtP9mOBQQOZ2/Yqw/sOulxD/jq
Bug#913614: marked as done (gnupg2 fails with "cannot open '/dev/tty': No such device or address")
Your message dated Sat, 09 Feb 2019 21:47:23 + with message-id and subject line Bug#913614: fixed in gnupg2 2.1.18-8~deb9u4 has caused the Debian Bug report #913614, regarding gnupg2 fails with "cannot open '/dev/tty': No such device or address" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 913614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnupg Version: 2.1.18-8~deb9u3 Reproducer, run the following in an environment without a tty. For me, this is happening in a "docker build". It happens on old Docker versions as well as new. # apt install gnupg2 (2.1.18-8~deb9u3) $ gpg --verbose --keyserver hkp://keyserver.ubuntu.com:80 \ --keyserver-options timeout=5 --recv-keys \ ABAF11C65A2970B130ABE3C479BE3E4300411886 Error text: gpg: cannot open '/dev/tty': No such device or address If I manually download the debs for gnupg2, dirmngr, and gnupg-agent at '2.1.18-8~deb9u2', it works fine. I grabbed the 3 debs directly from snapshot.debian.org and then installed them with "apt install -V -y *.deb". Example of full failure output (multiple times across different gpg servers): https://travis-ci.org/boot2docker/boot2docker/builds/454166287#L1390-L1427 Thanks, Joe Ferguson --- End Message --- --- Begin Message --- Source: gnupg2 Source-Version: 2.1.18-8~deb9u4 We believe that the bug you reported is fixed in the latest version of gnupg2, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated gnupg2 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: Thu, 07 Feb 2019 15:57:27 -0500 Source: gnupg2 Binary: gnupg-agent scdaemon gpgsm gnupg gnupg2 gpgv gpgv2 dirmngr gpgv-udeb gpgv-static gpgv-win32 gnupg-l10n Architecture: source Version: 2.1.18-8~deb9u4 Distribution: stretch Urgency: medium Maintainer: Debian GnuPG Maintainers Changed-By: Daniel Kahn Gillmor Description: dirmngr- GNU privacy guard - network certificate management service gnupg - GNU privacy guard - a free PGP replacement gnupg-agent - GNU privacy guard - cryptographic agent gnupg-l10n - GNU privacy guard - localization files gnupg2 - GNU privacy guard - a free PGP replacement (dummy transitional pa gpgsm - GNU privacy guard - S/MIME version gpgv - GNU privacy guard - signature verification tool gpgv-static - minimal signature verification tool (static build) gpgv-udeb - minimal signature verification tool (udeb) gpgv-win32 - GNU privacy guard - signature verification tool (win32 build) gpgv2 - GNU privacy guard - signature verification tool (dummy transition scdaemon - GNU privacy guard - smart card support Closes: 913614 Changes: gnupg2 (2.1.18-8~deb9u4) stretch; urgency=medium . * Avoid crash when importing without a TTY (Closes: #913614) Checksums-Sha1: b7c5cac094e05c9320e71fdb4be3eeac7e884037 2561 gnupg2_2.1.18-8~deb9u4.dsc 5c4e4ed9df261e16bd72f3207dae6b05a81df7c9 122023 gnupg2_2.1.18-8~deb9u4.debian.tar.bz2 8171ee3f8b9cb800ed036aed32806794d7f8dcb5 10499 gnupg2_2.1.18-8~deb9u4_source.buildinfo Checksums-Sha256: e42240a13af866a3c9db1704bfbbd2230abb071dca3c24d7c2a3b27e94d8aaa3 2561 gnupg2_2.1.18-8~deb9u4.dsc 81f6cf52bc22d77332a413ec2cd423e2127faea950705b50b50f84c8ed43521e 122023 gnupg2_2.1.18-8~deb9u4.debian.tar.bz2 b7feecce6ac92226b15188555eab65169f38ac2d283c65af50a02f0e9adb0715 10499 gnupg2_2.1.18-8~deb9u4_source.buildinfo Files: e0427c074ffcbe2285eac1d6244d1921 2561 utils optional gnupg2_2.1.18-8~deb9u4.dsc b93eeff197da9129cfec1fddf5f18bc8 122023 utils optional gnupg2_2.1.18-8~deb9u4.debian.tar.bz2 2b0b357776074b843c785cabbc237b1d 10499 utils optional gnupg2_2.1.18-8~deb9u4_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTJDm02IAobkioVCed2GBllKa5f+AUCXFyp0QAKCRB2GBllKa5f +IQDAP9rJxMSFbj3EECyZ0NA3gOi1iVtmE+yJFBZgdYCad6fNgD/acBR70Ud5HMP ugKH/fWBaZhHzpcrhgrDcxz+so5zkwo= =Eifh -END PGP SIGNATURE End Message ---
Bug#875696: marked as done (courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm")
Your message dated Sat, 09 Feb 2019 21:47:08 + with message-id and subject line Bug#875696: fixed in courier 0.76.3-5+deb9u1 has caused the Debian Bug report #875696, regarding courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm" 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.) -- 875696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: courier-mlm Version: 0.76.3-5 Severity: grave Justification: renders package unusable Dear Maintainer, courier-mlm failed to install using the command: apt install courier-mlm Errors below: A instalar courier-mlm (0.76.3-5) ... Created symlink /etc/systemd/system/multi-user.target.wants/courier-mlm.service → /lib/systemd/system/courier-mlm.service. Job for courier-mlm.service failed because the control process exited with error code. See "systemctl status courier-mlm.service" and "journalctl -xe" for details. invoke-rc.d: initscript courier-mlm, action "start" failed. ● courier-mlm.service - Courier MLM Daemon Loaded: loaded (/lib/systemd/system/courier-mlm.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-09-13 18:16:10 WEST; 10ms ago Process: 19036 ExecStart=/usr/bin/webmlmd start /etc/courier/webmlmrc (code=exited, status=1/FAILURE) set 13 18:16:10 myhost systemd[1]: Starting Courier MLM Daemon... set 13 18:16:10 myhost webmlmd[19036]: @piddir@/webmlm: No such file or directory set 13 18:16:10 myhost systemd[1]: courier-mlm.service: Control process exited, code=exited status=1 set 13 18:16:10 myhost systemd[1]: Failed to start Courier MLM Daemon. set 13 18:16:10 myhost systemd[1]: courier-mlm.service: Unit entered failed state. set 13 18:16:10 myhost systemd[1]: courier-mlm.service: Failed with result 'exit-code'. dpkg: erro ao processar o pacote courier-mlm (--configure): subprocesso script post-installation instalado retornou erro do status de saída 1 A processar 'triggers' para systemd (232-25+deb9u1) ... Foram encontrados erros enquanto processava: courier-mlm E: Sub-process /usr/bin/dpkg returned an error code (1) I don't think it's relevant, but I'm running postfix for MTA -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8), LANGUAGE=pt:pt_BR:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages courier-mlm depends on: ii courier-base 0.76.3-5 ii init-system-helpers 1.48 ii libc62.24-11+deb9u1 ii libcourier-unicode1 1.4-3+b1 ii libgcc1 1:6.3.0-18 ii libgdbm3 1.8.3-14 ii libidn11 1.33-1 ii libstdc++6 6.3.0-18 ii maildrop 2.8.4-2 ii sysvinit-utils 2.88dsf-59.9 courier-mlm recommends no packages. Versions of packages courier-mlm suggests: ii courier-doc 0.76.3-5 -- no debconf information --- End Message --- --- Begin Message --- Source: courier Source-Version: 0.76.3-5+deb9u1 We believe that the bug you reported is fixed in the latest version of courier, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated courier package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Feb 2019 18:36:51 +0100 Source: courier Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl Architecture: source Version: 0.76.3-5+deb9u1 Distribution: stretch Urgency: medium Maintainer: Markus Wanner Changed-By: Andreas Beckmann Description: courier-base - Courier mail server - base system courier-doc - Courier mail server - additional documentation courier-faxmail - Courier mail
Bug#921884: wlroots: ABI break between 0.2 and 0.3
retitle: -1 no stable ABI Hi, On Sat, Feb 09, 2019 at 10:08:02PM +0100, Mattia Rizzolo wrote: > Source: wlroots > Version: 0.3-1 > Severity: serious > > 0.3 changed many symbols. > A full diff is below. As you can see manny symbols were added (alright, > that means you should have bumped shlibs, which you didn't), but also > several were renamed, which means a real full ABI break happened, but > the SONAME wasn't changed. > > I'm afraid this also means upstream is not good at proper ABI hygiene, > so you should be extra careful, starting by adding a .symbols file > (which is very easy since this is a C library!). > > > At the very least, this caused headaches while packaging sway, see > #821397. This is well known to the users of wlroots and the reason why we did not upload to unstable yet but it's good to have a bug tracking that. Cheers, -- Guido
Bug#921883:
Actually I have not made any local changes to config files, they are as provided by packages. This is my list of emacs-related installed packages: elpa-restart-emacs 0.1.1-2 all [installed] emacs-bin-common 1:26.1+1-3.2 amd64 [installed,automatic] emacs-common-non-dfsg 1:26.1+1-1 all [installed] emacs-common 1:26.1+1-3.2 all [installed,automatic] emacs-el 1:26.1+1-3.2 all [installed,automatic] emacs-gtk 1:26.1+1-3.2 amd64 [installed,automatic] emacs-intl-fonts 1.2.1-10 all [installed] emacs-jabber 0.8.92+git98dc8e-4 all [installed] emacs 1:26.1+1-3.2 all [installed] emacsen-common 3.0.4 all [installed,automatic] emacspeak-espeak-server 49.0+dfsg-2 amd64 [installed] emacspeak 49.0+dfsg-2 all [installed] maxima-emacs 5.42.1-1 all [installed] xemacs21-basesupport 2009.02.17.dfsg.2-4 all [installed,automatic] xemacs21-bin 21.4.24-7 amd64 [installed,automatic] xemacs21-mule 21.4.24-7 amd64 [installed,automatic] xemacs21-mulesupport 2009.02.17.dfsg.2-4 all [installed,automatic] xemacs21-support 21.4.24-7 all [installed,automatic] xemacs21 21.4.24-7 all [installed]
Bug#921667: [pkg-lxc-devel] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends
On 2019-02-09 21:51, Pierre-Elliott Bécue wrote: > I'm not sure that there is something we can do regarding lxc. Am I > wrong? You could try to figure out why lxc explodes. Probably some package places some configuration file at some location Andreas PS: I should be able to get a shell in the chroot after the failure occurred, in case you want me to collect some information.
Bug#921884: wlroots: ABI break between 0.2 and 0.3
Source: wlroots Version: 0.3-1 Severity: serious 0.3 changed many symbols. A full diff is below. As you can see manny symbols were added (alright, that means you should have bumped shlibs, which you didn't), but also several were renamed, which means a real full ABI break happened, but the SONAME wasn't changed. I'm afraid this also means upstream is not good at proper ABI hygiene, so you should be extra careful, starting by adding a .symbols file (which is very easy since this is a C library!). At the very least, this caused headaches while packaging sway, see #821397. --- 0.2/foo.symbols 2019-02-09 21:54:17.009104873 +0100 +++ 0.3/foo.symbols 2019-02-09 21:54:24.560855387 +0100 @@ -12,6 +12,7 @@ wlr_backend_is_headless@Base 0 wlr_backend_is_libinput@Base 0 wlr_backend_is_multi@Base 0 + wlr_backend_is_noop@Base 0 wlr_backend_is_wl@Base 0 wlr_backend_start@Base 0 wlr_box_closest_point@Base 0 @@ -44,14 +45,16 @@ wlr_cursor_warp@Base 0 wlr_cursor_warp_absolute@Base 0 wlr_cursor_warp_closest@Base 0 + wlr_data_control_device_v1_destroy@Base 0 + wlr_data_control_manager_v1_create@Base 0 + wlr_data_control_manager_v1_destroy@Base 0 wlr_data_device_manager_create@Base 0 wlr_data_device_manager_destroy@Base 0 wlr_data_source_accept@Base 0 - wlr_data_source_cancel@Base 0 + wlr_data_source_destroy@Base 0 wlr_data_source_dnd_action@Base 0 wlr_data_source_dnd_drop@Base 0 wlr_data_source_dnd_finish@Base 0 - wlr_data_source_finish@Base 0 wlr_data_source_init@Base 0 wlr_data_source_send@Base 0 wlr_dmabuf_attributes_finish@Base 0 @@ -76,6 +79,19 @@ wlr_egl_swap_buffers@Base 0 wlr_export_dmabuf_manager_v1_create@Base 0 wlr_export_dmabuf_manager_v1_destroy@Base 0 + wlr_foreign_toplevel_handle_v1_create@Base 0 + wlr_foreign_toplevel_handle_v1_destroy@Base 0 + wlr_foreign_toplevel_handle_v1_output_enter@Base 0 + wlr_foreign_toplevel_handle_v1_output_leave@Base 0 + wlr_foreign_toplevel_handle_v1_set_activated@Base 0 + wlr_foreign_toplevel_handle_v1_set_app_id@Base 0 + wlr_foreign_toplevel_handle_v1_set_maximized@Base 0 + wlr_foreign_toplevel_handle_v1_set_minimized@Base 0 + wlr_foreign_toplevel_handle_v1_set_title@Base 0 + wlr_foreign_toplevel_manager_v1_create@Base 0 + wlr_foreign_toplevel_manager_v1_destroy@Base 0 + wlr_fullscreen_shell_v1_create@Base 0 + wlr_fullscreen_shell_v1_destroy@Base 0 wlr_gamma_control_manager_create@Base 0 wlr_gamma_control_manager_destroy@Base 0 wlr_gamma_control_manager_v1_create@Base 0 @@ -86,8 +102,6 @@ wlr_gles2_texture_from_wl_drm@Base 0 wlr_gtk_primary_selection_device_manager_create@Base 0 wlr_gtk_primary_selection_device_manager_destroy@Base 0 - wlr_gtk_primary_selection_source_finish@Base 0 - wlr_gtk_primary_selection_source_init@Base 0 wlr_headless_add_input_device@Base 0 wlr_headless_add_output@Base 0 wlr_headless_backend_create@Base 0 @@ -160,6 +174,8 @@ wlr_multi_backend_remove@Base 0 wlr_multi_for_each_backend@Base 0 wlr_multi_is_empty@Base 0 + wlr_noop_add_output@Base 0 + wlr_noop_backend_create@Base 0 wlr_output_create_global@Base 0 wlr_output_cursor_create@Base 0 wlr_output_cursor_destroy@Base 0 @@ -184,6 +200,7 @@ wlr_output_init@Base 0 wlr_output_is_drm@Base 0 wlr_output_is_headless@Base 0 + wlr_output_is_noop@Base 0 wlr_output_is_wl@Base 0 wlr_output_layout_add@Base 0 wlr_output_layout_add_auto@Base 0 @@ -229,6 +246,14 @@ wlr_pointer_constraints_v1_create@Base 0 wlr_pointer_constraints_v1_destroy@Base 0 wlr_pointer_destroy@Base 0 + wlr_pointer_gestures_v1_create@Base 0 + wlr_pointer_gestures_v1_destroy@Base 0 + wlr_pointer_gestures_v1_send_pinch_begin@Base 0 + wlr_pointer_gestures_v1_send_pinch_end@Base 0 + wlr_pointer_gestures_v1_send_pinch_update@Base 0 + wlr_pointer_gestures_v1_send_swipe_begin@Base 0 + wlr_pointer_gestures_v1_send_swipe_end@Base 0 + wlr_pointer_gestures_v1_send_swipe_update@Base 0 wlr_pointer_init@Base 0 wlr_positioner_invert_x@Base 0 wlr_positioner_invert_y@Base 0 @@ -237,6 +262,9 @@ wlr_presentation_create@Base 0 wlr_presentation_destroy@Base 0 wlr_presentation_send_surface_presented@Base 0 + wlr_primary_selection_source_destroy@Base 0 + wlr_primary_selection_source_init@Base 0 + wlr_primary_selection_source_send@Base 0 wlr_region_confine@Base 0 wlr_region_create@Base 0 wlr_region_expand@Base 0 @@ -244,6 +272,10 @@ wlr_region_rotated_bounds@Base 0 wlr_region_scale@Base 0 wlr_region_transform@Base 0 + wlr_relative_pointer_manager_v1_create@Base 0 + wlr_relative_pointer_manager_v1_destroy@Base 0 + wlr_relative_pointer_manager_v1_send_relative_motion@Base 0 + wlr_relative_pointer_v1_from_resource@Base 0 wlr_render_ellipse@Base 0 wlr_render_ellipse_with_matrix@Base 0 wlr_render_quad_with_matrix@Base 0 @@ -273,8 +305,6 @@ wlr_seat_client_for_wl_client@Base 0 wlr_seat_client_from_pointer_resource@Base 0 wlr_seat_client_from_resource@Base 0 - wlr_seat_client_send_gtk_primary_selection@Base 0 -
Bug#921667: [pkg-lxc-devel] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends
Le jeudi 07 février 2019 à 20:29:45+0100, Andreas Beckmann a écrit : > Package: lxc,lava-dev > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + lava-dispatcher lava-server > Control: found -1 lxc/1:3.1.0+really3.0.3-2 > Control: found -1 lava/2019.01-3 > Control: found -1 lava/2019.01-4 > > Hi, > > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > > This was observed during a test of lava-dev with --install-recommends enabled. > > From the attached log (scroll to the bottom...): > > Setting up lxc (1:3.1.0+really3.0.3-2) ... > Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not > found > Cache read/write disabled: interface file missing. (Kernel needs AppArmor > 2.4 compatibility patch.) > Warning: unable to find a suitable fs in /proc/mounts, is it mounted? > Use --subdomainfs to override. > dpkg: error processing package lxc (--configure): >installed lxc package post-installation script subprocess returned error > exit status 1 > > I can reproduce this in both amd64 and i386 chroots. > I cannot reproduce it with lxc alone (regardles of whether > --install-recommends is enabled) > I cannot reproduce it with lava-dev without --install-recommends > > > cheers, Hi, I'm not sure that there is something we can do regarding lxc. Am I wrong? Best regards, -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Bug#900145: Proposal,
HELLO, FIRSTLY I APOLOGISE BECAUSE YOU DO NOT KNOW ME PERSONALLY I GOT YOUR EMAIL FOR A WEB JOURNAL AND I WAS WONDERING IF WE CAN WORK TOGETHER BECAUSE I HAVE A TRANSACTION FOR YOU CAN WE WORK TOGETHER ?
Processed: reopening 921882, submitter 921882, reassign 921882 to python3-httplib2 ...
Processing commands for cont...@bugs.debian.org:
> reopen 921882
Bug #921882 {Done: Sandro Tosi } [python3-pysimplesoap]
Incorrect check of httplib2 version
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pysimplesoap/1.16-2.1 and
pysimplesoap/1.16.2-1.
> submitter 921882 !
Bug #921882 [python3-pysimplesoap] Incorrect check of httplib2 version
Changed Bug submitter to 'Andreas Beckmann ' from 'Aiden
Woodruff '.
> reassign 921882 python3-httplib2 0.11.3-1
Bug #921882 [python3-pysimplesoap] Incorrect check of httplib2 version
Bug reassigned from package 'python3-pysimplesoap' to 'python3-httplib2'.
No longer marked as found in versions pysimplesoap/1.16-2.
Ignoring request to alter fixed versions of bug #921882 to the same values
previously set
Bug #921882 [python3-httplib2] Incorrect check of httplib2 version
Marked as found in versions python-httplib2/0.11.3-1.
> retitle 921882 python{,3}-httplib2: needs Breaks: python{,3}-pysimplesoap (<<
> 1.16-2.1)
Bug #921882 [python3-httplib2] Incorrect check of httplib2 version
Changed Bug title to 'python{,3}-httplib2: needs Breaks:
python{,3}-pysimplesoap (<< 1.16-2.1)' from 'Incorrect check of httplib2
version'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921772: marked as done (CVE-2018-1000652)
Your message dated Sat, 09 Feb 2019 20:42:20 + with message-id and subject line Bug#921772: fixed in jabref 3.8.2+ds-12 has caused the Debian Bug report #921772, regarding CVE-2018-1000652 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.) -- 921772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jabref Severity: grave Tags: security This was assigned CVE-2018-1000652: https://github.com/JabRef/jabref/issues/4229 https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e Cheers, Moritz --- End Message --- --- Begin Message --- Source: jabref Source-Version: 3.8.2+ds-12 We believe that the bug you reported is fixed in the latest version of jabref, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated jabref 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, 09 Feb 2019 00:54:59 +0100 Source: jabref Architecture: source Version: 3.8.2+ds-12 Distribution: unstable Urgency: high Maintainer: Debian Java Maintainers Changed-By: gregor herrmann Closes: 921772 Changes: jabref (3.8.2+ds-12) unstable; urgency=high . * Add patch from upstream commit to fix CVE-2018-1000652: XML External Entity attack. Thanks to Moritz Muehlenhoff for the bug report. (Closes: #921772) Checksums-Sha1: 2f6ef783e4cba8ef54d395ec270071a62598b60d 2762 jabref_3.8.2+ds-12.dsc f04e60130e303c21d419cb4639bc7d063a5a366e 50152 jabref_3.8.2+ds-12.debian.tar.xz 3f38bbb32d22cf84aeae2ae105fc5305b8eac0af 15816 jabref_3.8.2+ds-12_amd64.buildinfo Checksums-Sha256: cf4c81f5bf0034222833f555a9dedcb6cabca9eab51f55eb80192c6e39d8d762 2762 jabref_3.8.2+ds-12.dsc 0b69a1ed3f918554aa5147d6bb45c2dca8c19a0154967e041ca396bc17625eb0 50152 jabref_3.8.2+ds-12.debian.tar.xz 7020013fe6700dd6c3f4173003c9a83e5380917f24b080931ee454d55ec60c4b 15816 jabref_3.8.2+ds-12_amd64.buildinfo Files: 253c5b6ee1d208c7f86a444bf9c4c980 2762 tex optional jabref_3.8.2+ds-12.dsc 91b365a3c979c16801e573f0e41e7862 50152 tex optional jabref_3.8.2+ds-12.debian.tar.xz be34fe1ed3a5a5d9b3940087cdc329fc 15816 tex optional jabref_3.8.2+ds-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlxfLW0UHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZZ9BAAhArMIHWnd5QL0AxfXamnzoBec9Fp c3675kMgoqpg9mG4RfiU9WcLA4ZgbGN4bmtXbeBgSRmz/gobDHfqXABiV301QfEm LjJZ/X+RulvD39BjRbxU0IyZZKldWT0I2LjYeBHafYxDugtq+J8MjSnnR4HqQmC7 H2mOIeQUcr9ZZRoXI8X3y3+3LQxMfZ4AmPpPjAQ4mkYBrvlvIvpLyUSOJcDWViJQ JSyGomQCG3RBNssjldSfvvwUJFZMoz91+IjA0FaOW+ia/wp1H8krIDiXyfIbZlsl vWgUaAVjQTha8OudynQ7HRwTkWqKct78T8WP4jFk2pMjg2KTWmEQukEpBsYt/3P4 Ni7lZW4NtXe5p6zowUt0ws0lE8dP5ONc91QZ3C1nkTpo6s4p8rr/9uh1UBkpUd2O 9We281CfhtAZTDSOVuTa48g575vnz9rQfv8cucz9JDIzDkLZ9QgODMHrqjOuhWrk P1fozs1ooP7vq//FLumqkBDRnxd491J05o4aFTCtOQN2ysme8Lgz55wancIURCR+ ZtImxzvEiG9s1crF27cAfkIPSr5kY+qPFTTQexYMVO1ZaUdgP8LsFDOiG9lvqihK 3yJFuPjHD9Mg98syxZDZ6KUvvzx1sn0oKkMRS1AouNKHfFU07hMsdvdZT7JSHz/g asJTn/MmPTUM8lU= =V+op -END PGP SIGNATURE End Message ---
Bug#921777: marked as done (bugwarrior: FTBFS (failing tests))
Your message dated Sat, 09 Feb 2019 20:40:21 +
with message-id
and subject line Bug#921777: fixed in bugwarrior 1.6.0-3
has caused the Debian Bug report #921777,
regarding bugwarrior: FTBFS (failing tests)
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.)
--
921777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bugwarrior
Version: 1.6.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep --with python3,sphinxdoc --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:217: python3.7 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml bugwarrior/docs/
bugwarrior/docs/_build/html # HTML generator
Running Sphinx v1.7.9
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from http://docs.python.org/objects.inv...
[... snipped ...]
Traceback (most recent call last):
File "/<>/tests/test_db.py", line 78, in test_synchronize
db.synchronize(iter((issue,)), config, 'general')
File "/<>/bugwarrior/db.py", line 289, in synchronize
key_list = build_key_list(services)
File "/<>/bugwarrior/db.py", line 459, in build_key_list
keys[target] = get_service(target).ISSUE_CLASS.UNIQUE_KEY
File "/<>/bugwarrior/services/__init__.py", line 41, in
get_service
return epoint.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2345,
in load
self.require(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2368,
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (future 0.16.0 (/usr/lib/python3/dist-packages),
Requirement.parse('future!=0.16.0'))
==
ERROR: test_udas (tests.test_db.TestUDAs)
--
Traceback (most recent call last):
File "/<>/tests/test_db.py", line 146, in test_udas
udas = sorted(list(db.get_defined_udas_as_strings(config, 'general')))
File "/<>/bugwarrior/db.py", line 466, in
get_defined_udas_as_strings
uda_list = build_uda_config_overrides(services)
File "/<>/bugwarrior/db.py", line 507, in
build_uda_config_overrides
targets_udas.update(get_service(target).ISSUE_CLASS.UDAS)
File "/<>/bugwarrior/services/__init__.py", line 41, in
get_service
return epoint.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2345,
in load
self.require(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2368,
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (future 0.16.0 (/usr/lib/python3/dist-packages),
Requirement.parse('future!=0.16.0'))
--
Ran 117 tests in 0.666s
FAILED (SKIP=4, errors=2)
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bugwarrior.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: bugwarrior
Source-Version: 1.6.0-3
Processed: Re: Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3
Processing control commands:
> clone -1 -2
Bug #919001 {Done: Paul Gevers } [emacspeak] emacspeak:
fails to upgrade with emacs 1.26.1+1-3
Bug 919001 cloned as bug 921883
> reopen -2
Bug #921883 {Done: Paul Gevers } [emacspeak] emacspeak:
fails to upgrade with emacs 1.26.1+1-3
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions emacspeak/49.0+dfsg-2.
> retitle -2 emacspeak fails to byte-compile in some case
Bug #921883 [emacspeak] emacspeak: fails to upgrade with emacs 1.26.1+1-3
Changed Bug title to 'emacspeak fails to byte-compile in some case' from
'emacspeak: fails to upgrade with emacs 1.26.1+1-3'.
> tag -2 moreinfo
Bug #921883 [emacspeak] emacspeak fails to byte-compile in some case
Added tag(s) moreinfo.
--
919001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919001
921883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3
Control: clone -1 -2 Control: reopen -2 Control: retitle -2 emacspeak fails to byte-compile in some case Control: tag -2 moreinfo Hi Pavel, Although the symptoms look similar, the issue is very different. Your log says: """ emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil gc-cons-threshold 6400 load-source-file-function nil)' -l /usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l /usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l /usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l /usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l /usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l /usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el -f batch-byte-compile emacspeak-vm.el In toplevel form: emacspeak-vm.el:52:1:Error: Symbol's value as variable is void: vm-supported-sort-keys """ I fail to reproduce that locally. Can you explain more about your setup? If you care, please don't reply to this e-mail but use the new bug number that will be created by the commands I included at the top. Paul signature.asc Description: OpenPGP digital signature
Bug#921305: zfs-dkms: fails to upgrade from stretch
On 2019-02-09 18:53, Hilko Bengen wrote: > Andreas, > > I seem to have no way to test this in a chroot, but I'm pretty sure that > this issue could be fixed by adding a versioned Pre-Depends: spl-dkms to > zfs-dkms. > > Am I missing something? I don't think that will help, but one would have to try it. In my test the new spl-dkms was already installed and configured. The problematic part was: configure new spl-dkms (build for linux-headers-foo-old) install new linux-headers-foo configure new zfs-dkms (build for both linux-headers-foo-old and linux-headers-foo-new - misses spl for linux-headers-foo-new) Andreas
Processed (with 5 errors): Re: Incorrect check of httplib2 version
Processing control commands:
> clone -1 -2
Bug #906127 {Done: Sandro Tosi } [python3-pysimplesoap]
Incorrect check of httplib2 version
Bug 906127 cloned as bug 921882
Failed to clone 906127: Not altering archived bugs; see unarchive.
> submitter -2 !
Failed to set submitter on -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_submitter did not pass regex check
.
> tag -1 sid buster
Bug #906127 {Done: Sandro Tosi } [python3-pysimplesoap]
Incorrect check of httplib2 version
Added tag(s) sid and buster.
> reopen -2
Failed to reopen -2: The 'bug' parameter ("-2") to Debbugs::Control::set_done
did not pass regex check
.
> reassign -2 python3-httplib2 0.11.3-1
Failed to clear fixed versions and reopen on -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_package did not pass regex check
.
> retitle -2 python{,3}-httplib2: needs Breaks: python{,3}-pysimplesoap (<<
> 1.16-2.1)
Failed to set the title of -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_title did not pass regex check
.
--
906127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906127: Incorrect check of httplib2 version
Followup-For: Bug #906127
Control: clone -1 -2
Control: submitter -2 !
Control: tag -1 sid buster
Control: reopen -2
Control: reassign -2 python3-httplib2 0.11.3-1
Control: retitle -2 python{,3}-httplib2: needs Breaks: python{,3}-pysimplesoap
(<< 1.16-2.1)
Hi,
If I understood the problem correctly, it is the combination of
python3-pysimplesoap 1.16-2 (stretch) and python3-httplib2 0.11.3-1
(buster) that is going to break things.
So add some Breaks to python3-httplib2 in buster to prevent partial
upgrades from stretch leading to this combination.
Since python-pysimplesoap seems to use the same code as
python3-pysimplesoap, you probably need the Breaks in both
python-httplib2 and python3-httplib2 against the respective packages.
Andreas
Bug#921777: Bug #921777 in bugwarrior marked as pending
Control: tag -1 pending Hello, Bug #921777 in bugwarrior 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/tasktools-team/bugwarrior/commit/b257936e0e69a6243d70eb4bec0513a4f641a341 Unpin future version Closes: #921777 (this message was generated automatically) -- Greetings https://bugs.debian.org/921777
Processed: Re: courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm"
Processing control commands:
> tag -1 pending
Bug #875696 {Done: Markus Wanner } [courier-mlm]
courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc:
"PORT=@piddir@/webmlm"
Added tag(s) pending.
--
875696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#875696: courier-mlm: unsubstituted @piddir@ in /etc/courier/webmlmrc: "PORT=@piddir@/webmlm"
Followup-For: Bug #875696 Control: tag -1 pending Hi, I just backported the fix to stretch, prepared a stretch-pu request and uploaded the package: https://bugs.debian.org/921876 Andreas
Bug#915426: marked as done (git breaks git-remote-hg autopkgtest)
Your message dated Sat, 09 Feb 2019 19:29:12 + with message-id and subject line Bug#915426: fixed in git-remote-hg 1.0.0~ds-1 has caused the Debian Bug report #915426, regarding git breaks git-remote-hg autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git, git-remote-hg Control: found -1 git/1:2.20.0~rc2-1 Control: found -1 git-remote-hg/0.4-0.1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of git the autopkgtest of git-remote-hg fails in testing when that autopkgtest is run with the binary packages of git from unstable. It passes when run with only packages from testing. In tabular form: passfail gitfrom testing1:2.20.0~rc2-1 git-remote-hg from testing0.4-0.1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration of git to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from git/1:2.20.0~rc2-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=git https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-remote-hg/1428119/log.gz not ok 32 - pull tags # # test_when_finished "rm -rf hgrepo gitrepo" && # # ( # hg init hgrepo && # cd hgrepo && # echo one > content && # hg add content && # hg commit -m one # ) && # # git clone "hg::hgrepo" gitrepo && # # (cd hgrepo && hg tag v1.0) && # (cd gitrepo && git pull) && # # echo "v1.0" > expected && # git --git-dir=gitrepo/.git tag > actual && # test_cmp expected actual # ok 33 - push merged named branch ok 34 - light tag sets author ok 35 - push tag different branch ok 36 - cloning a removed file works ok 37 - cloning a file replaced with a directory ok 38 - clone replace directory with a file ok 39 - clone can ignore invalid refnames # 1 known breakage(s) vanished; please update test(s) # still have 2 known breakage(s) # failed 1 among remaining 36 test(s) 1..39 make: *** [Makefile:14: main.t] Error 1 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: git-remote-hg Source-Version: 1.0.0~ds-1 We believe that the bug you reported is fixed in the latest version of git-remote-hg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated git-remote-hg 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, 09 Feb 2019 19:42:14 +0100 Source: git-remote-hg Architecture: source Version: 1.0.0~ds-1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 915426 Changes: git-remote-hg (1.0.0~ds-1) unstable; urgency=medium . [ upstream ] * New release. + Fixes to support Mercurial 4.7. Closes: Bug#915426. Thanks to Paul Gevers. . [ Ondřej Nový ] * Update copyright info: Use https protocol in Format field * Use package section optional (not obsolete extra).
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 921778 + patch Bug #921778 [src:deap] deap: FTBFS (Could not import extension sphinx.ext.pngmath) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 921778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3
Hi Pavel, Can you please attach the /tmp/filedHvWsk file? Paul signature.asc Description: OpenPGP digital signature
Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3
This bug (or a very similar one) seems to trigger again when upgrading to emacs-gtk-1:26.1+1-3.2 with emacspeak-49.0+dfsg-2 : 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. WARNING: Unknown distro but dpkg found, assuming Debian Setting up emacs-gtk (1:26.1+1-3.2) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install emacspeak for emacs /usr/lib/emacsen-common/packages/install/emacspeak running in / Latest installed version: 49.0+dfsg-2 install/emacspeak: Handling install for emacsen flavor emacs Temporary log file is /tmp/filedHvWsk Byte-compiling (~0.7 min) ...ERROR: install script from emacspeak package failed dpkg: error processing package emacs-gtk (--configure): installed emacs-gtk package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of emacs: emacs depends on emacs-gtk (>= 1:26.1) | emacs-lucid (>= 1:26.1) | emacs-nox (>= 1:26.1); however: Package emacs-gtk is not configured yet. Package emacs-lucid is not installed. Package emacs-nox is not installed. dpkg: error processing package emacs (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: emacs-gtk emacs needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) On Mon, Jan 14, 2019 at 6:45 PM Paul Gevers wrote: > HI, > > On 13-01-2019 22:49, Pavel Kreuzt wrote: > > It's emacspeak-47.0+dfsg-6 > > I think I understand the issue. Will upload shortly. > > Paul > >
Processed: Downgrading severity while packages are still present
Processing commands for cont...@bugs.debian.org: > severity 921851 important Bug #921851 [src:binutils-xtensa-lx106] unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster Severity set to 'important' from 'serious' > severity 921855 important Bug #921855 [src:gcc-xtensa-lx106] outdated b-d's on libisl-0.18-dev and libcloog-isl-dev, to be removed in buster Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 921851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921851 921855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): Downgrading severity while packages are still present
Processing commands for cont...@bugs.debian.org: > severity important 921851 Unknown command or malformed arguments to command. > tags 921851 + pending Bug #921851 [src:binutils-xtensa-lx106] unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster Added tag(s) pending. > severity important 921855 Unknown command or malformed arguments to command. > tags 921855 + pending Bug #921855 [src:gcc-xtensa-lx106] outdated b-d's on libisl-0.18-dev and libcloog-isl-dev, to be removed in buster Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 921851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921851 921855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921778: deap: FTBFS (Could not import extension sphinx.ext.pngmath)
user debian-rele...@lists.debian.org usertag 921778 + bsp-2019-02-de-berlin thank you Dear maintainers, Greetings from the BSP at the DCSO office in Berlin. I have fixed this bug and attached a patch for the issue. Cheers Sascha diff --git a/debian/changelog b/debian/changelog index b1133ac..d799f8c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,10 +1,15 @@ -deap (1.0.2.post2-6) UNRELEASED; urgency=medium +deap (1.0.2.post2-6.1) UNRELEASED; urgency=medium + [ OndÅej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/watch: Use https protocol * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP - -- OndÅej Nový Tue, 13 Feb 2018 10:18:20 +0100 + [ Sascha Steinbiss ] + * Use imgmath Sphinx extension instead of deprecated pngmath. +Closes: #921778 + + -- Sascha Steinbiss Sat, 09 Feb 2019 19:28:44 +0100 deap (1.0.2.post2-5) unstable; urgency=medium diff --git a/debian/patches/0003-remove-pngmath.patch b/debian/patches/0003-remove-pngmath.patch new file mode 100644 index 000..ec000fb --- /dev/null +++ b/debian/patches/0003-remove-pngmath.patch @@ -0,0 +1,17 @@ +Description: replace pngmath with imgmath + The pngmath Sphinx extension has been deprecated in Sphinx 1.4 and + was removed for good in Sphinx 1.8. It can be replaced safely by the + imgmath extension, which is also available in 1.4 (so also in stretch). +Author: Sascha Steinbiss +Last-Update: 2019-02-09 +--- a/doc/conf.py b/doc/conf.py +@@ -27,7 +27,7 @@ + # coming with Sphinx (named 'sphinx.ext.*') or your custom ones + + extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.todo', +- 'sphinx.ext.pngmath', 'sphinx.ext.intersphinx', 'sphinx.ext.extlinks'] ++ 'sphinx.ext.imgmath', 'sphinx.ext.intersphinx', 'sphinx.ext.extlinks'] + + try: + import matplotlib diff --git a/debian/patches/series b/debian/patches/series index 233d16a..393233d 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,2 +1,3 @@ 0001-fix-docs.patch 0002-fix-tests.patch +0003-remove-pngmath.patch
Bug#921772: CVE-2018-1000652
On Sat, 09 Feb 2019 09:47:08 -0800, tony mancill wrote: > > Seems like we either need a new build dependency, or remove the > > logging part, or rewrite it … I'd be grateful for help from Java > > experts :) > Thank you for doing this. I guess upstream switched out the logging > implementation in their patch. I'll push an updated patch this weekend. Great, thanks Tony! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Leonard Cohen: I Can't Forget signature.asc Description: Digital Signature
Bug#890416: Leafpad over ssh erases file content upon saving
tags 890416 +moreinfo user debian-rele...@lists.debian.org usertag 890416 + bsp-2019-02-de-berlin thanks Behaves differently to me. When connecting with caja over ssh to localhost and opening a file, an empty file with title 'Untitled' is opened. When klicking on the save button, the location where to save to is asked for. versions: caja - 1.20.3-1+b1 leafpad - 0.8.18.1-5
Processed: Re: Leafpad over ssh erases file content upon saving
Processing commands for cont...@bugs.debian.org: > tags 890416 +moreinfo Bug #890416 [leafpad] Leafpad over ssh erases file content upon saving Added tag(s) moreinfo. > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was fgr...@freenet.de). > usertag 890416 + bsp-2019-02-de-berlin There were no usertags set. Usertags are now: bsp-2019-02-de-berlin. > thanks Stopping processing here. Please contact me if you need assistance. -- 890416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921305: zfs-dkms: fails to upgrade from stretch
Andreas, I seem to have no way to test this in a chroot, but I'm pretty sure that this issue could be fixed by adding a versioned Pre-Depends: spl-dkms to zfs-dkms. Am I missing something? Cheers, -Hilko
