Bug#920672: marked as done (netdata: Incomplete debian/copyright?)
Your message dated Mon, 28 Jan 2019 09:30:47 +0100 with message-id <1548664247.3149642.1645029560.44b17...@webmail.messagingengine.com> and subject line has caused the Debian Bug report #920672, regarding netdata: Incomplete debian/copyright? 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.) -- 920672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netdata Version: 1.11.1+dfsg-5 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Daniel Baumann , ftpmas...@debian.org Hi, I just ACCEPTed netdata from NEW but noticed it was missing attribution in debian/copyright for at least a bunch of embedded code copies under collectors/python.d.plugin and Alon Bar-Le This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Duplicate of #920671.--- End Message ---
Bug#920305: marked as done (ITP: popper.js -- Javascript library to position poppers in web applications)
Your message dated Mon, 28 Jan 2019 09:00:20 + with message-id and subject line Bug#920305: fixed in popper.js 1.14.6+ds-1 has caused the Debian Bug report #920305, regarding ITP: popper.js -- Javascript library to position poppers in web applications 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.) -- 920305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Xavier Guimard * Package name: popper.js Version : 1.14.6 Upstream Author : Federico Zivolo * URL : https://popper.js.org/ * License : Expat Programming Lang: Javascript Description : Javascript library to position poppers in web applications A popper is an element on the screen which "pops out" from the natural flow of your application. Common examples of poppers are tooltips, popovers and drop-downs. This library is a dependency of twitter-bootstrap4 (RC bug #920188) --- End Message --- --- Begin Message --- Source: popper.js Source-Version: 1.14.6+ds-1 We believe that the bug you reported is fixed in the latest version of popper.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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated popper.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: Wed, 23 Jan 2019 22:13:00 +0100 Source: popper.js Binary: libjs-popper.js Architecture: source all Version: 1.14.6+ds-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Description: libjs-popper.js - Javascript library to position poppers in web applications Closes: 920305 Changes: popper.js (1.14.6+ds-1) unstable; urgency=low . * Initial release (Closes: #920305) Checksums-Sha1: c4eda52f01c582245bfb77c53db750803df0eaf3 1974 popper.js_1.14.6+ds-1.dsc bb13d8bbf314a132426a35e3d8a30f3283d9f2e0 269732 popper.js_1.14.6+ds.orig.tar.xz 20717559b9200feb117e0bee43d8bce03e341c2d 2236 popper.js_1.14.6+ds-1.debian.tar.xz 4461562ed9ef12970c8d54497ae84a5fcb9fe60f 97504 libjs-popper.js_1.14.6+ds-1_all.deb 46a219b6f8d76f23bd76885dec8f1d9f28e3f90b 5540 popper.js_1.14.6+ds-1_amd64.buildinfo Checksums-Sha256: 32ec73b6ec14c110f466eefd42ead674e61a9bf000cfd5e29bacb56226026fd6 1974 popper.js_1.14.6+ds-1.dsc 110733344f440a0337c0480f9c50b4345dbd8b80d91a26ce00e9e0ffed75cf1a 269732 popper.js_1.14.6+ds.orig.tar.xz cf913a452d4854c00f2720850e8b0f289ae0129bfd2797051e412e4ed40b7dab 2236 popper.js_1.14.6+ds-1.debian.tar.xz b8be8bb7ecbc4a3258f9695d2730c800f298411c5e01837f46a8ebd1c5ae9fd6 97504 libjs-popper.js_1.14.6+ds-1_all.deb c954f2a8c7d10cc4c67949c4354ec344a63631b5e29bea29a845793d7711624f 5540 popper.js_1.14.6+ds-1_amd64.buildinfo Files: 5c9a280328d6c68af24aa1d06ffc9aa8 1974 javascript optional popper.js_1.14.6+ds-1.dsc 82553573d40a7362e5e8bd21eb5005d5 269732 javascript optional popper.js_1.14.6+ds.orig.tar.xz e6c748da2b329c9a41e8b4ef7c32 2236 javascript optional popper.js_1.14.6+ds-1.debian.tar.xz fb2bcc9a3b8dc5fd026683b8da0724e1 97504 javascript optional libjs-popper.js_1.14.6+ds-1_all.deb dea7e9adfcaea345005fa3fe285a3dc9 5540 javascript optional popper.js_1.14.6+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxI5OUQHHlhZGRAZGVi aWFuLm9yZwAKCRD210ynyZnu6U8XEACTX4hAMKLXTtbDD6tS3gBpTNbw/uSY1QWg nz6rCB/NporQ5ZwgZ8CIGeMQFW3Qqmqg4t0QT1NxqRJ1easlHcwQQ1qag0mPS2ng 9WEwS1h2hqXoXQhZlAZvau/XSnGlmt//jmV8YvBougSyl1bAIvMdSKWZNXIhrIpD BvRLXmsfZ1E6p2bd+jqNJo3aqSIjRq2lyW7CadlYRVSmJFpRAP/3z5yq1Ri3Nwk2 UCJt1yQC0uNxdh+rDAhIlcE+YQdvhHhjUvNde24MEwK/9HtGeqkyJT5/tm3bEl/g z5UuEUR7JZRUuiiL0Trib6HH5VThA4qLUPNaSlR+JAtww3vG9TObWReYdVQy1nto zjqo4+yd9Z+/rUnnkAH+fi4+kzfmLLzbU6pfrNj/bCgeCQQhO+5LxCV2cW2ywNGf 8Ps1ftKkl82JS2t4kgNCQB7UtfSGyxRtQUAik/1H6gRT8p5DNOkRXnR2N0/mDz9l wKtcDAyDayGGPeQoux1P6b+m6PZ4PcKjZsvyD3hC6YAJPhpcdL5AJm8FRR8kCKTG eLa319bE8jtRpD3kbf3jKOgzMtdtivL3y1qFLWbb7MbsGnvFCRUpwhmW8gEU1aJq mr6rWBu9UWbHdM64YoNq1JUOd7xTCM40KI4h5M1UeYOlMPs3QPVrzNDQki91LHCq lTA0MSVYdA== =2FKe
Bug#914740: marked as done (agg FTCBFS: configures for the build architecture)
Your message dated Mon, 28 Jan 2019 09:00:10 + with message-id and subject line Bug#914740: fixed in agg 1:2.6.0-r132+dfsg1-1 has caused the Debian Bug report #914740, regarding agg FTCBFS: configures for the build architecture 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.) -- 914740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: agg Version: 1:2.4-r127+dfsg1-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap agg fails to cross build from source, because it configures for the build architecture by not passing the relevant --host flag. The easiest way of doing so is using dh_auto_configure. The attached patch implements that and makes agg cross buildable. Please consider applying it. Helmut diff --minimal -Nru agg-2.4-r127+dfsg1/debian/changelog agg-2.4-r127+dfsg1/debian/changelog --- agg-2.4-r127+dfsg1/debian/changelog 2017-08-14 00:32:15.0 +0200 +++ agg-2.4-r127+dfsg1/debian/changelog 2018-11-26 21:57:00.0 +0100 @@ -1,3 +1,10 @@ +agg (1:2.4-r127+dfsg1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_configure pass --host to configure. (Closes: #-1) + + -- Helmut Grohne Mon, 26 Nov 2018 21:57:00 +0100 + agg (1:2.4-r127+dfsg1-1) unstable; urgency=medium * I am taking over this package. Thank you Andrea Veri for your diff --minimal -Nru agg-2.4-r127+dfsg1/debian/rules agg-2.4-r127+dfsg1/debian/rules --- agg-2.4-r127+dfsg1/debian/rules 2017-06-19 06:27:04.0 +0200 +++ agg-2.4-r127+dfsg1/debian/rules 2018-11-26 21:57:00.0 +0100 @@ -2,7 +2,7 @@ FLAVOURS := pic nonpic -CONFIGURE_ARGS_COMMON := --prefix=/usr --disable-examples --x-includes=/usr/include --x-libraries=/usr/lib +CONFIGURE_ARGS_COMMON := --libdir=/usr/lib --disable-examples --x-includes=/usr/include --x-libraries=/usr/lib CONFIGURE_ARGS_pic := -with-pic CONFIGURE_ARGS_nonpic := --disable-gpc DESTDIR_nonpic := debian/libagg-dev @@ -19,7 +19,8 @@ mkdir -p $(CURDIR)/$(builddir) find $(CURDIR)/* -maxdepth 0 -not -path '$(CURDIR)/obj-*' | \ xargs cp -rlf -t $(CURDIR)/$(builddir) - cd $(builddir) && env NOCONFIGURE=1 sh autogen.sh && ./configure $(CONFIGURE_ARGS_COMMON) $(CONFIGURE_ARGS_$(1)) $(shell dpkg-buildflags --export=configure) + cd $(builddir) && env NOCONFIGURE=1 sh autogen.sh + dh_auto_configure --sourcedirectory=$(builddir) -- $(CONFIGURE_ARGS_COMMON) $(CONFIGURE_ARGS_$(1)) $(shell dpkg-buildflags --export=configure) touch $$@ build-$(1): build-$(1)-stamp --- End Message --- --- Begin Message --- Source: agg Source-Version: 1:2.6.0-r132+dfsg1-1 We believe that the bug you reported is fixed in the latest version of agg, 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. John Horigan (supplier of updated agg 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, 24 Jan 2019 18:33:41 -0800 Source: agg Binary: libagg-dev libagg2 libagg2-dbgsym libagg2-dev Architecture: source amd64 Version: 1:2.6.0-r132+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: John Horigan Changed-By: John Horigan Description: libagg-dev - AntiGrain Geometry graphical toolkit (static development files) libagg2- AntiGrain Geometry graphical toolkit (runtime files) libagg2-dev - AntiGrain Geometry graphical toolkit (static and shared developme Closes: 377270 914740 Changes: agg (1:2.6.0-r132+dfsg1-1) unstable; urgency=medium . * Upgrade to upstream version 2.6.0-r132 * Fix failure to cross-build from source (FTCBFS) by using dh_auto_configure to pass --host to configure. Applying rules patch from Helmut Grohne (Closes: #914740) * Support multi-arch. * Add two more binary packages: libagg2-dev with development files, including shared libraries; and libagg2 with just the so files. (Closes: #377270) * Removed no-pre-c89.patch, fixed in upstream. * Removed 03-pkg-config-pic.patch. A sed script in the rules file
Bug#863704: marked as done (ITP: node-yarnpkg -- a fast, reliable and secure npm)
Your message dated Mon, 28 Jan 2019 09:00:19 + with message-id and subject line Bug#843021: fixed in node-yarnpkg 1.13.0-1 has caused the Debian Bug report #843021, regarding ITP: node-yarnpkg -- a fast, reliable and secure npm 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.) -- 843021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: yarn Version : 0.16.0 Upstream Author : Yarn Developers * URL : https://yarnpkg.com/ * License : BSD Programming Lang: Javascript Description : Fast, reliable, and secure dependency management for JS Fast: Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever. Reliable: Using a detailed, but concise, lockfile format, and a deterministic algorithm for installs, Yarn is able to guarantee that an install that worked on one system will work exactly the same way on any other system. Secure: Yarn uses checksums to verify the integrity of every installed package before its code is executed. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: node-yarnpkg Source-Version: 1.13.0-1 We believe that the bug you reported is fixed in the latest version of node-yarnpkg, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated node-yarnpkg 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, 26 Jan 2019 08:49:57 +0100 Source: node-yarnpkg Binary: yarnpkg Architecture: source all Version: 1.13.0-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Paolo Greppi Description: yarnpkg- Fast, reliable and secure npm alternative Closes: 843021 Changes: node-yarnpkg (1.13.0-1) unstable; urgency=low . * Initial release (Closes: #843021) Checksums-Sha1: 88269c29b251436499301c6297af6255a5b5d734 6765 node-yarnpkg_1.13.0-1.dsc 986c1d06173fb020504830f4341e4cde5abc9d58 5712 node-yarnpkg_1.13.0.orig-babel-plugin-transform-inline-imports-commonjs.tar.gz c8ab7a57bcb0b41e88a8f5e38b2e786307e042d2 2745 node-yarnpkg_1.13.0.orig-decode-uri-component.tar.gz 2581f0a21ca4e3f1cea1a18244f4a9354ba0b55c 7892 node-yarnpkg_1.13.0.orig-dnscache.tar.gz 9f879c97244f5300b01b29556e1f8b9756ab5a3f 2493 node-yarnpkg_1.13.0.orig-gunzip-maybe.tar.gz 472f239b51568d85b4f0d90b16c478472a8a3524 8121 node-yarnpkg_1.13.0.orig-hash-for-dep.tar.gz 32d9d4c938b8bafd946ad3d9a79119f52ab3cd7f 1764 node-yarnpkg_1.13.0.orig-is-deflate.tar.gz c4c804aa0915ccb2e53c20d5ee9f518ab67f4870 1463 node-yarnpkg_1.13.0.orig-is-gzip.tar.gz 8ea19b0190f0f2659fa5b5a19cc24be3a75ac7be 3860 node-yarnpkg_1.13.0.orig-normalize-url.tar.gz d4da843abe522b1cf16dbdc6b110673c73a402f1 4837 node-yarnpkg_1.13.0.orig-npm-logical-tree.tar.gz 9ba088617cd86197517be5ceccf4b90391177664 3037 node-yarnpkg_1.13.0.orig-peek-stream.tar.gz 2b9c9055053a443f313b807c981140e77f84c831 4856 node-yarnpkg_1.13.0.orig-query-string.tar.gz e2faa0bf49359f12114522680b69df8687932453 1532 node-yarnpkg_1.13.0.orig-strict-uri-encode.tar.gz 3faaceb03602cc1dcb3aee88607a288174564ffd 7484 node-yarnpkg_1.13.0.orig-tar-fs.tar.gz 83755176014fe7ce7afec3f13a16e4dac8bb3851 4763 node-yarnpkg_1.13.0.orig-v8-compile-cache.tar.gz 534cf29da5330e13170bf946fc39aa927b471d84 74383363 node-yarnpkg_1.13.0.orig.tar.gz 1a9ba288b117ff1ebf1528091a63be8bbe8517c1 9376 node-yarnpkg_1.13.0-1.debian.tar.xz 62f15e9c7c81ec265162f4c41394199bedd05a9e 20525 node-yarnpkg_1.13.0-1_amd64.buildinfo bb3db1f5f659c94dee76680918885c7a4ca20ecb 490708 yarnpkg_1.13.0-1_all.deb Checksums-Sha256: 4b936afe8dbca89d11132aee58acab7407378916671b28199f1b2d5a885c95a3 6765 node-yarnpkg_1.13.0-1.dsc 08697ea0cf0d0a72df0020737dcf7ae9f71b24158d57cc9dfb2edf3ab7800c50 5712 node-yarnpkg_1.13.0.orig-babel-plugin-transform-inline-imports-commonjs.tar.gz
Bug#843021: marked as done (ITP: node-yarnpkg -- a fast, reliable and secure npm)
Your message dated Mon, 28 Jan 2019 09:00:19 + with message-id and subject line Bug#843021: fixed in node-yarnpkg 1.13.0-1 has caused the Debian Bug report #843021, regarding ITP: node-yarnpkg -- a fast, reliable and secure npm 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.) -- 843021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org --- Please fill out the fields below. --- Package name: yarn Version: 0.16.1 Upstream Author: Yarn Developers URL: https://github.com/yarnpkg/yarn License: BSD-2-Clause Description: Fast, reliable, and secure alternative for the npm client, compatible with the npm registry. . Fast: Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever. . Reliable: Using a detailed, but concise, lockfile format, and a deterministic algorithm for installs, Yarn is able to guarantee that an install that worked on one system will work exactly the same way on any other system. . Secure: Yarn uses checksums to verify the integrity of every installed package before its code is executed. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: node-yarnpkg Source-Version: 1.13.0-1 We believe that the bug you reported is fixed in the latest version of node-yarnpkg, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated node-yarnpkg 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, 26 Jan 2019 08:49:57 +0100 Source: node-yarnpkg Binary: yarnpkg Architecture: source all Version: 1.13.0-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Paolo Greppi Description: yarnpkg- Fast, reliable and secure npm alternative Closes: 843021 Changes: node-yarnpkg (1.13.0-1) unstable; urgency=low . * Initial release (Closes: #843021) Checksums-Sha1: 88269c29b251436499301c6297af6255a5b5d734 6765 node-yarnpkg_1.13.0-1.dsc 986c1d06173fb020504830f4341e4cde5abc9d58 5712 node-yarnpkg_1.13.0.orig-babel-plugin-transform-inline-imports-commonjs.tar.gz c8ab7a57bcb0b41e88a8f5e38b2e786307e042d2 2745 node-yarnpkg_1.13.0.orig-decode-uri-component.tar.gz 2581f0a21ca4e3f1cea1a18244f4a9354ba0b55c 7892 node-yarnpkg_1.13.0.orig-dnscache.tar.gz 9f879c97244f5300b01b29556e1f8b9756ab5a3f 2493 node-yarnpkg_1.13.0.orig-gunzip-maybe.tar.gz 472f239b51568d85b4f0d90b16c478472a8a3524 8121 node-yarnpkg_1.13.0.orig-hash-for-dep.tar.gz 32d9d4c938b8bafd946ad3d9a79119f52ab3cd7f 1764 node-yarnpkg_1.13.0.orig-is-deflate.tar.gz c4c804aa0915ccb2e53c20d5ee9f518ab67f4870 1463 node-yarnpkg_1.13.0.orig-is-gzip.tar.gz 8ea19b0190f0f2659fa5b5a19cc24be3a75ac7be 3860 node-yarnpkg_1.13.0.orig-normalize-url.tar.gz d4da843abe522b1cf16dbdc6b110673c73a402f1 4837 node-yarnpkg_1.13.0.orig-npm-logical-tree.tar.gz 9ba088617cd86197517be5ceccf4b90391177664 3037 node-yarnpkg_1.13.0.orig-peek-stream.tar.gz 2b9c9055053a443f313b807c981140e77f84c831 4856 node-yarnpkg_1.13.0.orig-query-string.tar.gz e2faa0bf49359f12114522680b69df8687932453 1532 node-yarnpkg_1.13.0.orig-strict-uri-encode.tar.gz 3faaceb03602cc1dcb3aee88607a288174564ffd 7484 node-yarnpkg_1.13.0.orig-tar-fs.tar.gz 83755176014fe7ce7afec3f13a16e4dac8bb3851 4763 node-yarnpkg_1.13.0.orig-v8-compile-cache.tar.gz 534cf29da5330e13170bf946fc39aa927b471d84 74383363 node-yarnpkg_1.13.0.orig.tar.gz 1a9ba288b117ff1ebf1528091a63be8bbe8517c1 9376 node-yarnpkg_1.13.0-1.debian.tar.xz 62f15e9c7c81ec265162f4c41394199bedd05a9e 20525 node-yarnpkg_1.13.0-1_amd64.buildinfo bb3db1f5f659c94dee76680918885c7a4ca20ecb 490708 yarnpkg_1.13.0-1_all.deb Checksums-Sha256: 4b936afe8dbca89d11132aee58acab7407378916671b28199f1b2d5a885c95a3 6765 node-yarnpkg_1.13.0-1.dsc 08697ea0cf0d0a72df0020737dcf7ae9f71b24158d57cc9dfb2edf3ab7800c50
Bug#920350: marked as done (ITP: pkg-js-autopkgtest -- collection of autopktest scripts for nodejs packages)
Your message dated Mon, 28 Jan 2019 09:00:19 + with message-id and subject line Bug#920350: fixed in pkg-js-tools 0.1 has caused the Debian Bug report #920350, regarding ITP: pkg-js-autopkgtest -- collection of autopktest scripts for nodejs packages 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.) -- 920350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Xavier Guimard * Package name: pkg-js-autopkgtest Version : 0.1 Upstream Author : Xavier Guimard * URL : https://salsa.debian.org/js-team/pkg-js-autopkgtest * License : GPL2+ Programming Lang: Shell Description : collection of autopktest scripts for nodejs packages This package contains test runners to be used with the autopkgtest infrastructure for nodejs packages. Packages using the tests with autopkgtests in this package will simply have to set "Testsuite: autopkgtest-pkg-js" in debian/control and write upstream test in debian/tests/pkg-js/test. This package provides also a test.mk file which can be include in debian/rule to avoid writing a override_dh_auto_test. The same test will be launched. This package is inspired from pkg-perl-autopkgtest. If accepted, a MR will be done on autodep8 project to include it. --- End Message --- --- Begin Message --- Source: pkg-js-tools Source-Version: 0.1 We believe that the bug you reported is fixed in the latest version of pkg-js-tools, 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. Xavier Guimard (supplier of updated pkg-js-tools 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, 27 Jan 2019 09:27:55 +0100 Source: pkg-js-tools Binary: pkg-js-autopkgtest pkg-js-tools Architecture: source all Version: 0.1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Description: pkg-js-autopkgtest - collection of autopktest scripts for Nodejs packages pkg-js-tools - collection of tools to aid packaging Node modules in Debian Closes: 920350 Changes: pkg-js-tools (0.1) unstable; urgency=medium . * Initial release (Closes: #920350) Checksums-Sha1: 4816690e2372678210efc25885397fd339d04e46 1868 pkg-js-tools_0.1.dsc 90819054ea67b708a8c0c0c93a04815bd6f5a640 5840 pkg-js-tools_0.1.tar.xz 9c96270db870eb83d1150242d4c5b0fc96472f94 2960 pkg-js-autopkgtest_0.1_all.deb 62bd27b2d03b80a28070f03ae9caa421bfcce6dc 4308 pkg-js-tools_0.1_all.deb 5b282ca5460bd07b2169c347e48e4bccc47b0ace 6648 pkg-js-tools_0.1_amd64.buildinfo Checksums-Sha256: 437efc3d5aea69eebe48068c768a76a9763fda84f958c709b2ceb54c10fba216 1868 pkg-js-tools_0.1.dsc 6cf21f4f07ad5cde6d54b99e5cd6aa60b06eec1f4aec095ecae34152f3ab4045 5840 pkg-js-tools_0.1.tar.xz 98b618efd91681acc445dbe3b931fc6e63cefddfcfc0abb2b0544685150e5466 2960 pkg-js-autopkgtest_0.1_all.deb c5813b9218556ad46b9f62f04707f87f5934830131b89e44297668c3224d808f 4308 pkg-js-tools_0.1_all.deb 647df3dbe8b582e9c0203e5211623c2ed14c8a7b04d7ba0ccc2f6f39b6332055 6648 pkg-js-tools_0.1_amd64.buildinfo Files: 5d3237e2739b2c4e7f7a6e350655c185 1868 devel optional pkg-js-tools_0.1.dsc 327105fd301cc4b0e1c0ac6ff5f961fe 5840 devel optional pkg-js-tools_0.1.tar.xz e128ef4f214c9e6d2e073cbce63de45a 2960 devel optional pkg-js-autopkgtest_0.1_all.deb 5f65af0968ca6c2af86ef30184fa7948 4308 devel optional pkg-js-tools_0.1_all.deb 12075648e8b53f0b5e0530892ec26b99 6648 devel optional pkg-js-tools_0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxOIgsACgkQ9tdMp8mZ 7ukX3w//TGwhjatEY8DWHIw/I4QXo82L/j5HPgBnTzpRVJ9Mzd7TJgpAw7cXCfXZ 3APCx3hslwD8LMj75bQV481yVpqtNyMzadZA/0I3KHcyCCuMasha/5LHneTbgJB4 OlNInVwdKN+l0rJRFsYrOubsFrpXO3Zkvl0JUPgsY0khHZxRq3KCo4DFH6YRyYoD sxpAbDL/bf34L1GzcskxvG9j64+q/SpTtHGCPmXI0+CrVzgIwfgCUz6uQ7rfHyaX B37khAQjy7HO66wuqYTya3POyfd0mhtoyztZTvHFDHzWs0rsQT216TlRguviCuqm xJiueHSKEdMC7W7Le/TkVr5atX/4y36nxn8bMlkIJwKMmTPwichAbjrbEl2PBopZ
Bug#867274: marked as done (ITP: libjs-webrtc-adapter -- shim to insulate apps from WebRTC spec changes and browser prefix differences)
Your message dated Mon, 28 Jan 2019 09:00:14 +
with message-id
and subject line Bug#867274: fixed in libjs-webrtc-adapter 7.2.0-1
has caused the Debian Bug report #867274,
regarding ITP: libjs-webrtc-adapter -- shim to insulate apps from WebRTC spec
changes and browser prefix differences
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.)
--
867274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Johannes Schauer
* Package name: node-webrtc-adapter
Version : 4.1.0
Upstream Author : Philipp Hancke
* URL : https://github.com/webrtc/adapter
* License : BSD-3-Clause
Programming Lang: JavaScript
Description : shim to insulate apps from WebRTC spec changes and browser
prefix differences
JavaScript client-side library providing a common wrapper around
differences in WebRTC implementations by different browser vendors.
Supports Google Chrome, Microsoft Edge, Mozilla Firefox and Apple Safari
browsers. WebRTC ("Web Real-Time Communication") is a collection of
communications protocols and application programming interfaces that
enable real-time communication over peer-to-peer connections.
The janus-demos package is currently in contrib because
node-webrtc-adapter is not yet packaged for Debian. Packaging
node-webrtc-adapter gets us one step closer to moving janus-demos into
main.
--- End Message ---
--- Begin Message ---
Source: libjs-webrtc-adapter
Source-Version: 7.2.0-1
We believe that the bug you reported is fixed in the latest version of
libjs-webrtc-adapter, 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.
Jonas Smedegaard (supplier of updated libjs-webrtc-adapter
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, 26 Jan 2019 15:42:58 +0100
Source: libjs-webrtc-adapter
Binary: libjs-webrtc-adapter node-webrtc-adapter
Architecture: source all
Version: 7.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Changed-By: Jonas Smedegaard
Description:
libjs-webrtc-adapter - shim to insulate apps from WebRTC quirks - browser
library
node-webrtc-adapter - shim to insulate apps from WebRTC quirks - Node.js
library
Closes: 867274
Changes:
libjs-webrtc-adapter (7.2.0-1) unstable; urgency=low
.
* Initial release
Closes: #867274.
Checksums-Sha1:
b9c76eb29fa88e5ef5d7129326ed5b3545c83414 2265 libjs-webrtc-adapter_7.2.0-1.dsc
b2d9d63f4597489cf49d11ef0c71c9a68a9b37d6 43991
libjs-webrtc-adapter_7.2.0.orig.tar.gz
6a406a45cfc18dd21816f304c79c6dfb7bbe4b2d 4176
libjs-webrtc-adapter_7.2.0-1.debian.tar.xz
d4b88591701bc46db6679ded5dff4a5c17b01530 167072
libjs-webrtc-adapter_7.2.0-1_all.deb
65a6b23c5e98da47a08468e530ce3805f3258ca5 12861
libjs-webrtc-adapter_7.2.0-1_amd64.buildinfo
7ccc4bafda6a036edfd12b33946430fd8f078f90 21816
node-webrtc-adapter_7.2.0-1_all.deb
Checksums-Sha256:
6db85b0a8ea6f634527236cfb5ca56a7139dfd00637a8ecd746fa368d329a324 2265
libjs-webrtc-adapter_7.2.0-1.dsc
aff8952bebd73fc3f41fc2f1e33e7544b9d3efcd5df97819441baf4a62242b45 43991
libjs-webrtc-adapter_7.2.0.orig.tar.gz
cfb6ff68fafe61aece335265b302450c1cd6ce6b78ae1d2577d8d900294fd962 4176
libjs-webrtc-adapter_7.2.0-1.debian.tar.xz
33c8135ee4603ea7ddab70375f45857def36ee9c322ba60351d0499c6a5d8177 167072
libjs-webrtc-adapter_7.2.0-1_all.deb
42280b5658a313b6718fa2b17caf8b089ac3aca51d868a176ab6b4d3241e42e2 12861
libjs-webrtc-adapter_7.2.0-1_amd64.buildinfo
45ff6434135219f5f6952f43000fdbff891df0861191870f931c384edb79eece 21816
node-webrtc-adapter_7.2.0-1_all.deb
Files:
5052e86ee399ebdde8bdbd75b7d3c80f 2265 javascript optional
libjs-webrtc-adapter_7.2.0-1.dsc
9f026f16a52fff9bdf394ccc4430d1da 43991 javascript optional
libjs-webrtc-adapter_7.2.0.orig.tar.gz
a323daaf6fae016b1b52e693a64269da 4176 javascript optional
libjs-webrtc-adapter_7.2.0-1.debian.tar.xz
1800d95a46f9ce614861af849ab58fde 167072 javascript optional
libjs-webrtc-adapter_7.2.0-1_all.deb
Bug#920516: marked as done (ITP: libjs-rtcpeerconnection-shim -- RTCPeerConnection API implemented ontop of ORTC)
Your message dated Mon, 28 Jan 2019 09:00:11 + with message-id and subject line Bug#920516: fixed in libjs-rtcpeerconnection-shim 1.2.14-1 has caused the Debian Bug report #920516, regarding ITP: libjs-rtcpeerconnection-shim -- RTCPeerConnection API implemented ontop of ORTC 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.) -- 920516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: libjs-rtcpeerconnection-shim Version : 1.2.14 Upstream Author : Philipp Hancke * URL : https://github.com/otalk/rtcpeerconnection-shim * License : BSD-3-clause Programming Lang: JavaScript Description : RTCPeerConnection API implemented ontop of ORTC RTCPeerConnection shim i an implementation of the W3C RTCPeerConnection API as a shim ontop of the ORTC API. . The RTCPeerConnection API enables audio and video communication between peers. It performs signal processing, codec handling, peer-to-peer communication, security, and bandwidth management. . Object Real-Time Communications (ORTC) provides a powerful API for the development of WebRTC based applications. . WebRTC (Web Real-Time Communication) is a project that provides web browsers and mobile applications with real-time communication (RTC) via simple application programming interfaces (APIs). This package is needed by libjs-webrtc-adapter (see bug#867274). The package will be maintained in the JavaScript team. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxMWloACgkQLHwxRsGg ASEVXA/8CbWk06+mxRL6xs8aEr4Xet6AIN3n9BdXMCch1YEwMVEpG6mKE4WcnNE6 AYVG1ZltLwKWYOHUlpxLgxnQeXJI/E/jE4GCdwEq5pMTjRwJwq3Shwrd/IRU2+JN j3cXJ5xIGyS/ZjmaPCewfXGy0a5eWY/5/sP5Zv76MDqJIS35h7lgDjS/BOJK4j8b SOaiQpu530Ay/O2uWAjdSAwRUQ7BarJ+tkyuMpV2c7Ztme640QYvngpi0Na+1i+B uQ7EGq63H/V0T8tPqtT0449uAzUf5Dx6lkR0rRhboMI1sqzIXOvozkuaXJKkKLqf Qj9/9/hSvjMKRKQuIjju+m2CcM0ZN7YC5QsHzjBZdKtOgnMA2J86/VJalGnGJYSm KqtulQvhL1SEnCmNVCaqdzec0J8Xc4RKbXpLvpPVBBa/LF98oNauD37YPBs4c2sV RZZBpmMoVMNlfH8sGqinrqwhUHmILxUSu3sDg/xC8R3sX57V5FpDYO1ZpJjwks+S LYxCbcEjxDzCnRhLM2qc+Ecs0JqkyZogDh+oB9Zv2RsxVa7JWiS53uQl29u4gqHp GTXqoIZGY3LxvDkugEl1lEKT9YXJNNWCUZh9bjbsMUeE8k35KBSjKlmGEESgv3fr Lp2JowhSyEmP/eiUVU9e8iNeqd+z48c7n5cRHVCUgTkdRBN15CM= =ruJp -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libjs-rtcpeerconnection-shim Source-Version: 1.2.14-1 We believe that the bug you reported is fixed in the latest version of libjs-rtcpeerconnection-shim, 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. Jonas Smedegaard (supplier of updated libjs-rtcpeerconnection-shim 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, 26 Jan 2019 14:12:16 +0100 Source: libjs-rtcpeerconnection-shim Binary: libjs-rtcpeerconnection-shim Architecture: source all Version: 1.2.14-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Description: libjs-rtcpeerconnection-shim - RTCPeerConnection API implemented ontop of ORTC Closes: 920516 Changes: libjs-rtcpeerconnection-shim (1.2.14-1) unstable; urgency=low . * Initial release. Closes: Bug#920516. Checksums-Sha1: 837523ddef3033a90cd1ee2ae65ed8546bd0fc55 2199 libjs-rtcpeerconnection-shim_1.2.14-1.dsc 9c5761acea72f9c9ede53f6279ee750e1cea99ba 90993 libjs-rtcpeerconnection-shim_1.2.14.orig.tar.gz 9fa29ff4f3417f198cf86744a7e075f05c90bdb0 3840 libjs-rtcpeerconnection-shim_1.2.14-1.debian.tar.xz 9da44ce6e93c94e7e11cd85008384766b670f1b8 46996 libjs-rtcpeerconnection-shim_1.2.14-1_all.deb 64cea65f3d78fe06fab9fbaaee1104a138df91d8 5820 libjs-rtcpeerconnection-shim_1.2.14-1_amd64.buildinfo Checksums-Sha256: 6dfc3683b6a179da858758bc9d38e8aff1cfe00d02ae086602a1fff1199c61a9 2199 libjs-rtcpeerconnection-shim_1.2.14-1.dsc 79fc91bc6b9589e6196b326011bf7d67d81c73346f32f3d154ec20984eab39f8 90993
Bug#898931: marked as done (ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough)
Your message dated Mon, 28 Jan 2019 09:00:15 + with message-id and subject line Bug#898931: fixed in looking-glass 0+a12-1 has caused the Debian Bug report #898931, regarding ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough 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.) -- 898931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Lennart Weller * Package name: looking-glass Version : 0+a10 Upstream Author : Geoffrey McRae * URL : https://github.com/gnif/LookingGlass/ * License : GPL2+ with OpenSSL Exception Programming Lang: C Description : An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough LookingGlass enables you to use shared memory to pass rendered frames from a virtual machine back to the host system. This is exceptionally useful for IOMMU/VFIO graphics card passthrough setups. --- End Message --- --- Begin Message --- Source: looking-glass Source-Version: 0+a12-1 We believe that the bug you reported is fixed in the latest version of looking-glass, 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 898...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lennart Weller (supplier of updated looking-glass 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, 25 Jan 2019 00:21:48 +0100 Source: looking-glass Binary: looking-glass-client looking-glass-client-dbgsym Architecture: source amd64 Version: 0+a12-1 Distribution: unstable Urgency: medium Maintainer: Lennart Weller Changed-By: Lennart Weller Description: looking-glass-client - Low latency KVM FrameRelay implementation for VGA Passthrough Closes: 898931 Changes: looking-glass (0+a12-1) unstable; urgency=medium . * Initial release. (Closes: #898931) Checksums-Sha1: 86f1e5e6ff136710741c0d1774999f2857f2143d 2007 looking-glass_0+a12-1.dsc 56ce77331f1a4e81e4c923fa633efa6f5c77c68c 109477 looking-glass_0+a12.orig.tar.gz 4b455bcc98f856a7475677a7bd77d7079fcc8896 4948 looking-glass_0+a12-1.debian.tar.xz d1b86158bd800b3080f37639c299c00390730a58 146044 looking-glass-client-dbgsym_0+a12-1_amd64.deb 598ec0d3dd09fded9284a1417da4b5734df4241c 49804 looking-glass-client_0+a12-1_amd64.deb 5712531fe1f0305acf8a9ae240d61de9887e0d6e 12413 looking-glass_0+a12-1_amd64.buildinfo Checksums-Sha256: 380bd07190aba9b65e895f694d2c10c0ebd9613856ce88fe4e628e6e3d22bb1a 2007 looking-glass_0+a12-1.dsc 75f0c27b2d24f8ba029155f9b6b14d55627213abdde9d44cc117b9813a64a774 109477 looking-glass_0+a12.orig.tar.gz b8fe232d513af26fb4bf90f2930d53784c2c029b7030d8ac47c9023ded63bb1f 4948 looking-glass_0+a12-1.debian.tar.xz f06eb9a8badeada1a3b7df32cf40e7c947a4ae8a4734f39ed32ca687ab999867 146044 looking-glass-client-dbgsym_0+a12-1_amd64.deb cb1afe2603dde66f381caff6ceec663a0600058fade179a49376f51aa8e0125e 49804 looking-glass-client_0+a12-1_amd64.deb 51978f070de1a94e2a7d72545f90f6a1112eb96435f9e365463240d7c7c93983 12413 looking-glass_0+a12-1_amd64.buildinfo Files: 417c1475f60e5d44dad2c4a34a3cb110 2007 net optional looking-glass_0+a12-1.dsc b858056381aafc9b9494eb35f149495b 109477 net optional looking-glass_0+a12.orig.tar.gz 4a3f965a72c469e2f42f5be48960489d 4948 net optional looking-glass_0+a12-1.debian.tar.xz 4852af6247bcf9477d877087bfa706c5 146044 debug optional looking-glass-client-dbgsym_0+a12-1_amd64.deb 1093edba92ec1207ddab54cf919e2d14 49804 net optional looking-glass-client_0+a12-1_amd64.deb d02c0092ba785033e2de77f80cd35068 12413 net optional looking-glass_0+a12-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlxKTS8PHHNyZUBkZWJp YW4ub3JnAAoJENju1/PIO/qakfYP/2We/tb8KbvtZlbijQ1hqAkWB3Lh3L/VNsZF 0TkcuePFnRo3W3pbc15R61Ld055ccxQVnGE27/Um59/rfzWLm5FH+rVzaVSpjciY usvPz0Qc8nTuE+Egt0Xpb+3wunO5mfC203Y6wG+vmfUve2M2gjoWA7MrCmqWBXAM YAUP/EAl3q+jvj4S53uc0d8Xm9XaaNHZRPYE/IL76PMUpqCx1RXpIZlk53p828LW 4s/n9FQltodyoUMpwnDvczpUO5OgZoGn1/vRvAmOB5PrSVw/wdb5xDIcqmeA7Y6F
Bug#847613: marked as done (ITP: nextcloud-client -- desktop client for nextcloud)
Your message dated Mon, 28 Jan 2019 09:00:18 + with message-id and subject line Bug#847613: fixed in nextcloud-desktop 2.5.1-1 has caused the Debian Bug report #847613, regarding ITP: nextcloud-client -- desktop client for nextcloud 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.) -- 847613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: RFP Nextcloud is the recent ownCloud fork. While I don't think it's probable Nextcloud itself will be packaged in Debian, having the desktop client would be very nice. At the moment the differences between Nextcloud and ownCloud are minor so the owncloud-client package still works. That will eventually change as the differences betweent the two grow Source: https://github.com/nextcloud/client_theming -- pollo signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nextcloud-desktop Source-Version: 2.5.1-1 We believe that the bug you reported is fixed in the latest version of nextcloud-desktop, 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 847...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Knauß (supplier of updated nextcloud-desktop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Jan 2019 22:32:03 +0100 Source: nextcloud-desktop Binary: nextcloud-desktop nextcloud-desktop-doc libnextcloudsync0 libnextcloudsync-dev nextcloud-desktop-common nextcloud-desktop-l10n nextcloud-desktop-cmd dolphin-nextcloud nautilus-nextcloud nemo-nextcloud caja-nextcloud Architecture: source all amd64 Version: 2.5.1-1 Distribution: unstable Urgency: medium Maintainer: ownCloud for Debian maintainers Changed-By: Sandro Knauß Description: caja-nextcloud - Nextcloud integration for Caja dolphin-nextcloud - Nextcloud integration for Dolphin libnextcloudsync-dev - Nextcloud folder synchronization - development files libnextcloudsync0 - Nextcloud folder synchronization - libraries nautilus-nextcloud - Nextcloud integration for Nautilus nemo-nextcloud - Nextcloud integration for Nemo nextcloud-desktop - Nextcloud folder synchronization tool nextcloud-desktop-cmd - folder synchronization with an Nextcloud server - cmd client nextcloud-desktop-common - Nextcloud folder synchronization - common data nextcloud-desktop-doc - Nextcloud folder synchronization - documentation nextcloud-desktop-l10n - Nextcloud folder synchronization - localization Closes: 847613 Changes: nextcloud-desktop (2.5.1-1) unstable; urgency=medium . * Initial release (Closes: #847613) Checksums-Sha1: c66e62c4f9c33cfe0fed3817aef63a30d220d96e 3150 nextcloud-desktop_2.5.1-1.dsc 74788ccf7a98853eab66232ac6fa86eed4567e6e 18916053 nextcloud-desktop_2.5.1.orig.tar.gz 65d34c4cd813bae7b1a7717de00489f981a2aa3c 9996 nextcloud-desktop_2.5.1-1.debian.tar.xz d07361932103f1c4ba734990ec49390c4040ae53 31408 caja-nextcloud_2.5.1-1_all.deb 08331e123ec619e7c30b1cf0a6e3ca1b7e063796 821616 dolphin-nextcloud-dbgsym_2.5.1-1_amd64.deb 888cb793bb898432016a24a68727ade9fa8759f8 52344 dolphin-nextcloud_2.5.1-1_amd64.deb b2238a751e66c3adf2ccc1d11b642429f919f318 43496 libnextcloudsync-dev_2.5.1-1_amd64.deb b8b6edeb67b938cf829fbd12f3e362c3e175f07a 11368544 libnextcloudsync0-dbgsym_2.5.1-1_amd64.deb 18bce7dd44a02f974eb92e5826d644e6687083f3 581936 libnextcloudsync0_2.5.1-1_amd64.deb 66a8574a050379f2cbe3a00f21a4f336322158d7 31296 nautilus-nextcloud_2.5.1-1_all.deb fecccd7135b3a47498b6d3db7594cc6cc5d18199 31264 nemo-nextcloud_2.5.1-1_all.deb e0543e31e5a17ce3cdff03d272dc54e0f0d07bc0 739316 nextcloud-desktop-cmd-dbgsym_2.5.1-1_amd64.deb fe5350afc6e597d57f7b141e57de8b498cbd002f 55988 nextcloud-desktop-cmd_2.5.1-1_amd64.deb 696b43f46a2bfb586d59818f77b47983d9ad3a36 724884 nextcloud-desktop-common_2.5.1-1_all.deb b6d22232efcb6651a75c26e6fea3c8c043dd18ca 18114848 nextcloud-desktop-dbgsym_2.5.1-1_amd64.deb 3b441e641756000415be63f6236d067c308c0ac6 2279660 nextcloud-desktop-doc_2.5.1-1_all.deb 655ad6f00d08875145394c0eeecaa160c0ae8967 410576
Bug#377270: marked as done (please package shared library)
Your message dated Mon, 28 Jan 2019 09:00:10 + with message-id and subject line Bug#377270: fixed in agg 1:2.6.0-r132+dfsg1-1 has caused the Debian Bug report #377270, regarding please package shared library 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.) -- 377270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: agg Version: 2.3-3 Severity: important matplotlib ships a copy of agg, but should be allowed to use the system agg library. --- End Message --- --- Begin Message --- Source: agg Source-Version: 1:2.6.0-r132+dfsg1-1 We believe that the bug you reported is fixed in the latest version of agg, 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 377...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Horigan (supplier of updated agg 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, 24 Jan 2019 18:33:41 -0800 Source: agg Binary: libagg-dev libagg2 libagg2-dbgsym libagg2-dev Architecture: source amd64 Version: 1:2.6.0-r132+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: John Horigan Changed-By: John Horigan Description: libagg-dev - AntiGrain Geometry graphical toolkit (static development files) libagg2- AntiGrain Geometry graphical toolkit (runtime files) libagg2-dev - AntiGrain Geometry graphical toolkit (static and shared developme Closes: 377270 914740 Changes: agg (1:2.6.0-r132+dfsg1-1) unstable; urgency=medium . * Upgrade to upstream version 2.6.0-r132 * Fix failure to cross-build from source (FTCBFS) by using dh_auto_configure to pass --host to configure. Applying rules patch from Helmut Grohne (Closes: #914740) * Support multi-arch. * Add two more binary packages: libagg2-dev with development files, including shared libraries; and libagg2 with just the so files. (Closes: #377270) * Removed no-pre-c89.patch, fixed in upstream. * Removed 03-pkg-config-pic.patch. A sed script in the rules file changes the library pointer to libagg_pic.a in libagg-dev. In libagg2-dev the shared library is selected. * Add patch to change ABI from 2:6:0 to 3:0:1 * Bump Standards-Version to 4.3.0.0 * Bumped debhelper/compat to level 10 Checksums-Sha1: 1aab4aec34c8696e3750039db8d06c67be5fcf7a 1943 agg_2.6.0-r132+dfsg1-1.dsc 5a2f1ddee3cc2f7a9d211499c684bdfbaabfe48b 1040112 agg_2.6.0-r132+dfsg1.orig.tar.xz 38838cb1f67967582e50b42ba25c3f4d968efee0 12004 agg_2.6.0-r132+dfsg1-1.debian.tar.xz ddd8d288ee78aaa9853a3c7d192fef8074df831a 10753 agg_2.6.0-r132+dfsg1-1_amd64.buildinfo 695799c9a7255dafba2e78577c371413fde60ae2 1380196 libagg-dev_2.6.0-r132+dfsg1-1_amd64.deb 36cb0048df775206f9316827b5807b7084f8eb6a 336784 libagg2-dbgsym_2.6.0-r132+dfsg1-1_amd64.deb 9963b3685ef9bb4d945ffcd9404e23063ac5db53 1379952 libagg2-dev_2.6.0-r132+dfsg1-1_amd64.deb ccd37e88a1ea5c98641f08e313a2c16fa4c4a3a5 84268 libagg2_2.6.0-r132+dfsg1-1_amd64.deb Checksums-Sha256: 97be66927bff307160a6924473cc8d6ee85e75810067d7fbae02e83fcc65995a 1943 agg_2.6.0-r132+dfsg1-1.dsc 1acb4cbe2d1f698eab23ce07374c624b4af820bc9c981f518c160c148c56e2a1 1040112 agg_2.6.0-r132+dfsg1.orig.tar.xz cf66ca54bd1d1a9017b91e5bba6f2a53eedba401564eafe259318f5f9c97fc24 12004 agg_2.6.0-r132+dfsg1-1.debian.tar.xz 408f353924b655e26e413a4068523f33ab4712053ac2389e7a978a52b4551e4a 10753 agg_2.6.0-r132+dfsg1-1_amd64.buildinfo a06fbff974187e671f31864a8849f37b1cb86b5a1a3e5c31712d1d14079b34ea 1380196 libagg-dev_2.6.0-r132+dfsg1-1_amd64.deb 898902c1c501dc39e919ba4bbc0d4843c7a3168f042f3486b86feb4f2f897caf 336784 libagg2-dbgsym_2.6.0-r132+dfsg1-1_amd64.deb b3cf7ba805229dfb0a502e7fa790662612b3a21f3f9128edfec1805fe2bcf4ac 1379952 libagg2-dev_2.6.0-r132+dfsg1-1_amd64.deb 413b063ee568e7b0ccef7c4beebcb88c4acf2ddad41f92dd9c41289a71494390 84268 libagg2_2.6.0-r132+dfsg1-1_amd64.deb Files: 04ac61aa637cb44a74bf54fde6c3f6fb 1943 libs optional agg_2.6.0-r132+dfsg1-1.dsc 0ac1af696a5f842ab913a538f5141c85 1040112 libs optional agg_2.6.0-r132+dfsg1.orig.tar.xz 9eb57c4a3bd24489318b9293d836dbce 12004 libs optional
Bug#920612: marked as done (ITP: libcatmandu-filestore-perl -- modules to make files persistent within the Catmandu framework)
Your message dated Mon, 28 Jan 2019 09:00:11 + with message-id and subject line Bug#920612: fixed in libcatmandu-filestore-perl 1.13-1 has caused the Debian Bug report #920612, regarding ITP: libcatmandu-filestore-perl -- modules to make files persistent within the Catmandu framework 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.) -- 920612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: libcatmandu-filestore-perl Version : 1.13 Upstream Author : Patrick Hochstenbach * URL : http://librecat.org/Catmandu/ * License : Artistic or GPL-1+ Programming Lang: Perl Description : modules to make files persistent within the Catmandu framework Each Catmandu::FileStore is a Catmandu::Store and inherits all its methods. . A Catmandu::FileStore is package to store and retrieve binary content in an filesystem, memory or a network. A Catmandu::FileStore contains one or more Catmandu::FileBag which is a kind of folder. . Each Catmandu::FileBag contains one or more files. . One special Catmandu::FileBag is the index which contains the listing of all Catmandu::FileBag in the Catmandu::FileStore. . Catmandu provides a suite of Perl modules to ease the import, storage, retrieval, export and transformation of metadata records. This package will be maintained in the Debian Perl team. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxNqNYACgkQLHwxRsGg ASF7uxAAiVwfRU6GIBbr4qgTLDjaxIU9KVflNtbbTcWYETtKlfpkpGTfX0ByMtbT oqlTiJFUkHIeZMdnxyTVpodbUOgmaSBBv9PCTSpvsqklt/mIoF/rSjwvwPIDX2If +xhaxjSOZaBWCIbPKZUUxujKu37O6REWdeTCXlvSjX3Bnlviq9MZthllNzIeKlUZ T2+J/HQYvUnVmi2drA/wtvnppju3YBi9K5vtgsMpNLBmVeZ72mybEUaFOhR8ziW/ wpGl401WUdWfGfSs1co6ysrDQHjDcRHme0Dx1UJaIjDuIw1tN+lttnfsHPGbFS1B riSAjpnvuBTFqx8NQn7IOEhflNXHyaEgvn6McS6XOft3qR6T0OpIkzfeElEIKg3v X8r/FqbRz5BdNrrdNMldEL7VcFOBTIbmaAYRYFWktZa8F4RMMTV2BT22y5zXsCyn yYTqvpwLv/eZ6f+1vkN+7Q0PV2lnl2iFxXFqzhvmKgtBRgFIYzxq0f9nRq5aL3L6 5EWrwrOb/V2M553rbtOWE7it8VWBdaQYZpi/ThoxWu8vjsb4iDlC9SF+puNNFnyy FHK9MMsZHhvWzRtm4yXa3J5KJzMm3cTlS5qQdOAPOx7o2X1DKNdtrMlMIeSNC4fL nGETNNiIRc2d1tccbElcGMIHnQGsI8pkvz1VCszJjsGnAlbuObQ= =A3mp -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libcatmandu-filestore-perl Source-Version: 1.13-1 We believe that the bug you reported is fixed in the latest version of libcatmandu-filestore-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated libcatmandu-filestore-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Jan 2019 14:10:51 +0100 Source: libcatmandu-filestore-perl Binary: libcatmandu-filestore-perl Architecture: source all Version: 1.13-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group Changed-By: Jonas Smedegaard Description: libcatmandu-filestore-perl - modules to make files persistent within the Catmandu framework Closes: 920612 Changes: libcatmandu-filestore-perl (1.13-1) unstable; urgency=low . * Initial Release. Closes: bug#920612. Checksums-Sha1: 26a7113352ca90da78cb8e897cf6e4d1356f2336 2507 libcatmandu-filestore-perl_1.13-1.dsc 85e71f22ea34ac06ac7d65fab82ff8ca8b3d65e0 386205 libcatmandu-filestore-perl_1.13.orig.tar.gz 697521993ba6868ba2d11460798b53fc01a42b16 3036 libcatmandu-filestore-perl_1.13-1.debian.tar.xz e430faf8651e43a48c4cd96bd03deddfe8780363 61508 libcatmandu-filestore-perl_1.13-1_all.deb 5ee77e317bff57e7086b74d5d0f79162fb1bf707 9139 libcatmandu-filestore-perl_1.13-1_amd64.buildinfo Checksums-Sha256: 384e62336c8a76f5784ea266efffe662146d94ce94d891b9b989df2cf66d8edd 2507 libcatmandu-filestore-perl_1.13-1.dsc 55b82aa4641b8c9c1be998bb6514d205a008ebee45a38c7ccb11f5f6121b2621 386205 libcatmandu-filestore-perl_1.13.orig.tar.gz 61b287d9631d395bf986222d95e8ce930e0442f496b47656412815aec642b9ad 3036
Bug#867272: marked as done (RFP: libjs-sdp -- SDP parsing and serialization utilities)
Your message dated Mon, 28 Jan 2019 09:00:12 + with message-id and subject line Bug#867272: fixed in libjs-sdp 2.9.0-1 has caused the Debian Bug report #867272, regarding RFP: libjs-sdp -- SDP parsing and serialization utilities 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.) -- 867272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Johannes Schauer * Package name: node-sdp Version : 2.2.0 Upstream Author : Philipp Hancke * URL : https://github.com/fippo/sdp * License : Expat Programming Lang: JavaScript Description : SDP parsing and serialization utilities Client-side JavaScript library for generating SDP from ORTC and vice versa. ORTC (Object Real-Time Communications) is on-the-wire compatible with WebRTC 1.0 and implemented in the Microsoft Edge browser. The library is required by the webrtc-adapter JavaScript library to provide a client-side shim for the Microsoft Edge browser. This package is required by the (to be created) package node-webrtc-adapter which in turn is required by the (existing) janus-demos package. The janus-demos package is currently in contrib because node-webrtc-adapter is not yet packaged for Debian. --- End Message --- --- Begin Message --- Source: libjs-sdp Source-Version: 2.9.0-1 We believe that the bug you reported is fixed in the latest version of libjs-sdp, 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. Jonas Smedegaard (supplier of updated libjs-sdp 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, 26 Jan 2019 11:57:56 +0100 Source: libjs-sdp Binary: libjs-sdp Architecture: source all Version: 2.9.0-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Description: libjs-sdp - SDP parsing and serialization utilities - browser library Closes: 867272 Changes: libjs-sdp (2.9.0-1) unstable; urgency=low . * Initial release. Closes: Bug#867272. Checksums-Sha1: 73a272f5b1652fa1aa5b10ab032b5c47bc9822d4 2048 libjs-sdp_2.9.0-1.dsc 5843f3076a9be6b5681e4062291e9f419af656eb 13854 libjs-sdp_2.9.0.orig.tar.gz f88baef25e388bbd355cec1bfcf9ac3abac580a7 3252 libjs-sdp_2.9.0-1.debian.tar.xz 0ccf2d74ef8f67ca9ab5f3f0f4cafbad2fc859c6 21432 libjs-sdp_2.9.0-1_all.deb 6474aa6e2a374bb87a97733143c9c6c0961c17e4 7287 libjs-sdp_2.9.0-1_amd64.buildinfo Checksums-Sha256: bebd5ea470f1b542536f646789d18bafe6975ea43c7d8a42571e2dc5c80c3aa0 2048 libjs-sdp_2.9.0-1.dsc db3ae6367f1d3fed79913872da1f4da5f76586c93b5e4687bd182d3251ead38b 13854 libjs-sdp_2.9.0.orig.tar.gz a2ea666dab5aad9b454dd3ff5558f1f38c37ad13c61b9a4ce45abcca2e1726fd 3252 libjs-sdp_2.9.0-1.debian.tar.xz d2f031a51165315f69b0f087f6a011c69f21a30d3549123a865c2f99e6e4aa80 21432 libjs-sdp_2.9.0-1_all.deb ec6207fa3809e93c3a1ef1b165718e412aea92317bdeef1eb63a683223f87159 7287 libjs-sdp_2.9.0-1_amd64.buildinfo Files: 48404349238d0bf1ccb13dedddc53d15 2048 javascript optional libjs-sdp_2.9.0-1.dsc 69654186ac619a45477b751a3d534922 13854 javascript optional libjs-sdp_2.9.0.orig.tar.gz 33e86c6f106e466afb9226c75a584b9d 3252 javascript optional libjs-sdp_2.9.0-1.debian.tar.xz 7a0fa26d4f599663036ef433d85626f2 21432 javascript optional libjs-sdp_2.9.0-1_all.deb 1f117ab147219e5bced7e34547bf1986 7287 javascript optional libjs-sdp_2.9.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxMQgQACgkQLHwxRsGg ASFPHg//dvqLnk54LV8QKodMfjVKXi79Dy6c18YQB5jRImbrClFl6lJxFPl9OumQ vWw7u//KlN9M/6LZKz67JiuqlnRTi2sxzUjFb9wyNKuv1yaIrK/iEeu9Fwsub/OF nbyaDBy1FjQ9U3qXYp10nh17L17GtAH5FYrNySKFR9rVpSXzHfgMejutS/uIVZqb L/xTNew35Fox/6wx2BBlbWo73IZHyFZD6ePshNZ3MDiZCC6CzAttLgug1kaGI+SK 9cImwfGI0agCy1uC7f88XwO4nRfcaNnAKjIfUVRw2Bspgy+sbWRgoSMWuSyF5Sor qg/2ltb2fyDCnSRmABNxg2z4h53PJO1eYzzMvGg9hR75aDBYsyv94yRRPuvAbhQf qsGzKZYdS0394l/uK4Tg5s+wcYMCAtU11BTSYz1EPGrjLzyCjV76pLs625ufgld4 9dpnBw32tXj/eonWB80GIa9q7m+bvBK13TXGrgluizwRo5/Yo3ivHCLak1y7cZI/
Bug#907997: marked as done (emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2)
Your message dated Mon, 28 Jan 2019 14:53:33 +0100 with message-id <3fbe04a7-64ec-05db-ee9d-5e0e3b7a7...@debian.org> and subject line Re: Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 has caused the Debian Bug report #907997, regarding emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 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.) -- 907997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emacs-lucid Severity: serious Version: 1:25.2+1-11 Hi Rob, I'm sorry, but the Breaks/Replaces headers still seem incomplete. I just experienced the following upgrade failure when I wanted to switch from emacs25 to emacs-lucid on a Raspberry Pi running Buster/Testing arm64: Preparing to unpack .../emacs_1%3a25.2+1-11_all.deb ... Unpacking emacs (1:25.2+1-11) over (47.0) ... Selecting previously unselected package emacs-lucid. Preparing to unpack .../emacs-lucid_1%3a25.2+1-11_arm64.deb ... Unpacking emacs-lucid (1:25.2+1-11) ... dpkg: error processing archive /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-11_arm64.deb (--unpack): trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-11_arm64.deb […] E: Sub-process /usr/bin/dpkg returned an error code (1) Processing triggers for mime-support (3.61) ... dpkg: dependency problems prevent configuration of emacs: emacs depends on emacs-gtk (>= 1:25) | emacs-lucid (>= 1:25) | emacs-nox (>= 1:25); however: Package emacs-gtk is not installed. Package emacs-lucid is not installed. Package emacs-nox is not installed. dpkg: error processing package emacs (--configure): dependency problems - leaving unconfigured […] The package currently has: Replaces: emacs-gtk, emacs-lucid (<< 1:25), emacs-nox But it should have (at least): Replaces: emacs-gtk, emacs-nox, emacs25, emacs25-lucid, emacs25-nox (I don't see why a package should have a Replaces header against an earlier, identically named version of itself, so I dropped the "emacs-lucid (<< 1:25)" part. Feel free to keep it though as it shouldn't do any harm there.) Having the same packages listed in Conflicts should be probably done, too. So please also replace Conflicts: emacs-gtk, emacs-nox with Conflicts: emacs-gtk, emacs-nox, emacs25, emacs25-lucid, emacs25-nox The same also needs to be done for emacs-gtk and emacs-nox with the according package being removed from the above examples and emacs-lucid added instead. --- End Message --- --- Begin Message --- On Sun, 13 Jan 2019 14:01:00 -0600 Rob Browning wrote: > I think this bug may now be "fixed" by the switch of the emacs package > to upstream 26.1, which should avoid including any of the conflicting > paths. I haven't seen anything related in my piuparts upgrade tests, so this seems to be really "fixed", thus closing. Andreas--- End Message ---
Bug#324542: marked as done (cjk-latex: Different horizontal/vertical DPI cause wrong size CJK characters and overprinting)
Your message dated Mon, 28 Jan 2019 15:25:01 +0100
with message-id <5e6cc28f-7e6f-b9ee-3094-26d62d28c...@web.de>
and subject line Re: Bug#324542: Update of cjk-latex (now latex-cjk)
has caused the Debian Bug report #324542,
regarding cjk-latex: Different horizontal/vertical DPI cause wrong size CJK
characters and overprinting
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.)
--
324542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cjk-latex
Version: 4.5.1-4
Severity: normal
I used \begin{CJK*}{GB}{song} .. \end{CJK*} around some
GB2312-encoded Chinese characters in a letter which I
intended to send by fax. Because I was going to fax it
using a fax modem, I used the -Pdfaxlo option of dvips
(see /etc/texmf/dvips/config.dfaxlo) so that Metafont is
set to generate optimal bitmaps for the G3 fax resolution
(204dpi horizontal, 98dpi vertical). This resulted in the
Chinese characters coming out as double height (as seen
in GhostScript) and partially overprinting the line above.
It seems that, when the CJK characters were involved,
Metafont ignored the fact that the vertical resolution was
only about half the horizontal resolution. This bug would
also affect people who want to use Metafont to optimise
the quality of old inkjet printers that have different
horizontal and vertical resolutions, although it may not
be so obvious.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.23
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to
en_GB)
Versions of packages cjk-latex depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libkpathsea32.0.2-30 path search library for teTeX (run
ii tetex-base 2.0.2c-8 Basic library files of teTeX
ii tetex-bin 2.0.2-30 The teTeX binary files
-- no debconf information
--- End Message ---
--- Begin Message ---
On 28.01.19 15:21, Silas S. Brown wrote:
Hi,
> Hi Hilmar, yes it's OK to close the bug now, sorry I forgot to reply before.
>
Thanks for reply. Closing then.
Hilmar
--
sigfault
#206401 http://counter.li.org
signature.asc
Description: OpenPGP digital signature
--- End Message ---
Bug#919876: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)
Your message dated Mon, 28 Jan 2019 15:12:56 + with message-id and subject line Bug#919876: fixed in java-string-similarity 0.24-2 has caused the Debian Bug report #919876, regarding javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:java-string-similarity Version: 0.24-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=maven dh_update_autotools_config -i -O--buildsystem=maven dh_autoreconf -i -O--buildsystem=maven dh_auto_configure -i -O--buildsystem=maven mh_patchpoms -plibjava-string-similarity-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i -O--buildsystem=maven /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [INFO] [INFO] < info.debatty:java-string-similarity >- [INFO] Building java-string-similarity 0.24 [INFO] [ jar ]- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ java-string-similarity --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /<>/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ java-string-similarity --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 25 source files to /<>/target/classes Use of target 1.5 is no longer supported, switching to 1.7 Use of source 1.5 is no longer supported, switching to 1.7 [INFO] [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ java-string-similarity --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ java-string-similarity --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 15 source files to /<>/target/test-classes Use of target 1.5 is no longer supported, switching to 1.7 Use of source 1.5 is no longer supported, switching to 1.7 [INFO] [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ java-string-similarity --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.1.1:jar (default-jar) @ java-string-similarity --- [INFO] Building jar: /<>/target/java-string-similarity-0.24.jar [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ java-string-similarity --- [INFO] Adding the --ignore-source-errors option [INFO] Loading source files for package info.debatty.java.stringsimilarity... Loading source files for package info.debatty.java.stringsimilarity.examples... Loading source files for package info.debatty.java.stringsimilarity.experimental... Loading source files for package info.debatty.java.stringsimilarity.interfaces... Constructing Javadoc information... Standard Doclet version 11.0.2 Building tree for all the packages and classes... Generating /<>/target/apidocs/info/debatty/java/stringsimilarity/CharacterSubstitutionInterface.html... Generating
Bug#669662: marked as done ([PATCH] prosper: Helping to update to packaging format 3.0)
Your message dated Mon, 28 Jan 2019 16:28:06 +0100 with message-id <20190128152806.kg2q4b7644bul...@haka.dresden.de> and subject line Re: Bug#669662: [PATCH] prosper: Helping to update to packaging format 3.0 has caused the Debian Bug report #669662, regarding [PATCH] prosper: Helping to update to packaging format 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prosper Severity: wishlist Tags: patch Hi, The dpatch patch management system has been deprecated for some time. The Lintian currently flags use of dpatch packages as an error. The new 3.0 packaging format is an improved version which, among other things, contains patch management built-in. For more information, see: http://wiki.debian.org/Projects/DebSrc3.0 I had some free time; see attached patch to migrate to new package format. Note that all files in debian/patches/* are canocalized to *.patch. Let me know if there is anything that needs adjusting or if it is ok to upload this version in a NMU in case you are working on other issues needing attention. Thanks, Jari >From a55acfeb4c4fa97268abce0802364683ba19be56 Mon Sep 17 00:00:00 2001 From: Jari Aalto Date: Fri, 20 Apr 2012 22:57:23 +0300 Subject: [PATCH] format-3.0 Organization: Private Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Signed-off-by: Jari Aalto --- debian/changelog | 15 +++ debian/compat|2 +- debian/control |5 +++-- debian/patches/00list|1 - debian/patches/01-kill-pstcol.patch | 15 +++ debian/patches/01_kill_pstcol.dpatch | 33 - debian/patches/series|1 + debian/rules | 12 ++-- debian/source/format |1 + debian/watch |2 ++ 10 files changed, 40 insertions(+), 47 deletions(-) delete mode 100644 debian/patches/00list create mode 100644 debian/patches/01-kill-pstcol.patch delete mode 100644 debian/patches/01_kill_pstcol.dpatch create mode 100644 debian/patches/series create mode 100644 debian/source/format create mode 100644 debian/watch diff --git a/debian/changelog b/debian/changelog index 0192b9f..11c3691 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,14 @@ +prosper (1.00.4+cvs.2007.05.01-4.1) unstable; urgency=low + + * Non-maintainer upload. + * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt". + * Update to Standards-Version to 3.9.3 and debhelper to 9. + * Add build-arch and build-indep targets; use dh_prep in rules file. + * Fix no-homepage-field (Lintian). + * Fix debian-watch-file-is-missing (Lintian). + + -- Jari Aalto Fri, 20 Apr 2012 22:55:41 +0300 + prosper (1.00.4+cvs.2007.05.01-4) unstable; urgency=low * Bumped to Standards-Version: 3.8.0. @@ -163,7 +174,3 @@ prosper (1.00.4-1) unstable; urgency=low * Initial Release. (closes: #82783) -- Adrian Bunk Fri, 16 Feb 2001 23:17:45 +0100 - -Local variables: -mode: debian-changelog -End: diff --git a/debian/compat b/debian/compat index b8626c4..ec63514 100644 --- a/debian/compat +++ b/debian/compat @@ -1 +1 @@ -4 +9 diff --git a/debian/control b/debian/control index efba7c9..4168f1f 100644 --- a/debian/control +++ b/debian/control @@ -2,9 +2,10 @@ Source: prosper Section: tex Priority: optional Maintainer: Masayuki Hatta (mhatta) -Build-Depends: debhelper (>> 4.0.0), dpatch +Build-Depends: debhelper (>= 9) Build-Depends-Indep: tex-common (>= 0.16) -Standards-Version: 3.8.0 +Standards-Version: 3.9.3 +Homepage: http://freecode.com/projects/prosper Package: prosper Architecture: all diff --git a/debian/patches/00list b/debian/patches/00list deleted file mode 100644 index 2cc0fc4..000 --- a/debian/patches/00list +++ /dev/null @@ -1 +0,0 @@ -01_kill_pstcol diff --git a/debian/patches/01-kill-pstcol.patch b/debian/patches/01-kill-pstcol.patch new file mode 100644 index 000..a96da32 --- /dev/null +++ b/debian/patches/01-kill-pstcol.patch @@ -0,0 +1,15 @@ +From: Masayuki Hatta +Subject: Makes prosper.cls not require pstcol, it has been causing much problem. + +diff -urN prosper-1.00.4+cvs.2004.03.29.orig/prosper.cls prosper-1.00.4+cvs.2004.03.29/prosper.cls +--- prosper-1.00.4+cvs.2004.03.29.orig/prosper.cls 2004-03-29 00:03:48.0 +0900 prosper-1.00.4+cvs.2004.03.29/prosper.cls 2004-03-29
Bug#919390: marked as done (udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules)
Your message dated Mon, 28 Jan 2019 12:51:45 +
with message-id
and subject line Bug#919390: fixed in systemd 240-5
has caused the Debian Bug report #919390,
regarding udev: network interface gets ID_NET_NAME even when NAME has been set
by /etc/udev/rules.d/70-persistent-net.rules
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.)
--
919390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 240-2
Severity: normal
Hi,
when updating from an older udev version I have noticed that my ethernet
interface got renamed to autogenerated (ID_NET_NAME) name even though I
have /etc/udev/rules.d/70-persistent-net.rules to rename it based on
the mac address as follows:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="28:f1:0e:31:04:16", KERNEL=="eth*", NAME="lan0"
The kernel log says that this gets applied:
[3.563937] e1000e :00:1f.6 lan0: renamed from eth0
[...]
[4.043437] e1000e :00:1f.6 enp0s31f6: renamed from lan0
Downgrading to 232-25+deb9u7 or adding net.ifnames=0 to kernel cmd line
makes the problem go away.
Let me know if you need an additional information.
Thanks!
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.0.0-rc1-1-g3bd6e94bec12 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages udev depends on:
ii adduser 3.118
ii libacl1 2.2.52-3+b1
ii libblkid12.33.1-0.1
ii libc62.28-2
ii libkmod2 25-2
ii libselinux1 2.8-1+b1
ii libudev1 240-2
ii lsb-base 10.2018112800
ii util-linux 2.33.1-0.1
udev recommends no packages.
udev suggests no packages.
Versions of packages udev is related to:
pn systemd
-- debconf information:
udev/title/upgrade:
udev/sysfs_deprecated_incompatibility:
udev/reboot_needed:
udev/new_kernel_needed: false
--
Michal Hocko
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-5
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt (supplier of updated systemd 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, 27 Jan 2019 21:33:07 +
Source: systemd
Architecture: source
Version: 240-5
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
Changed-By: Martin Pitt
Closes: 919390 920018
Changes:
systemd (240-5) unstable; urgency=medium
.
[ Felipe Sateler ]
* Revert interface renaming changes. (Closes: #919390)
.
[ Martin Pitt ]
* process-util: Fix memory leak (Closes: #920018)
Checksums-Sha1:
7ca4cf0e5237140b58f79cbd085aefd8d149ccf4 4898 systemd_240-5.dsc
10bd8179fbecdd2e1042dfa0bb3ff7af3b2c542e 165928 systemd_240-5.debian.tar.xz
35957a2ecd9e3d91ab8e2e24e2578302ede86cba 5785 systemd_240-5_source.buildinfo
Checksums-Sha256:
dfd3171ad9a140feaff6719abcd7586e3f4d46e5e5f048c3b04aa8504a8c94d8 4898
systemd_240-5.dsc
85022f13fd97467d10760917ac190f5f2960cf03b2349eed02b84dc3128dcb59 165928
systemd_240-5.debian.tar.xz
8236986f70863b5b8b79adb74a7d1ff789b2df0b3adaa22be11742e4468c0215 5785
systemd_240-5_source.buildinfo
Files:
02768a90ec1bc4eb87b61b7c149f1e54 4898 admin optional systemd_240-5.dsc
3349beba2d35cdbd1e3b4c0601b6bda5 165928 admin optional
systemd_240-5.debian.tar.xz
7d4c1fe5c542be96eeb55ea405d66b24 5785 admin optional
systemd_240-5_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#920018: marked as done (Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory)
Your message dated Mon, 28 Jan 2019 12:51:45 + with message-id and subject line Bug#920018: fixed in systemd 240-5 has caused the Debian Bug report #920018, regarding Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory 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.) -- 920018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 240-4 Severity: important Hi! Since systemd_240-4 journald seems to either leak memory or something strange is going on with my system. Soon after boot or journald restart, I get messages like this in my kernel log: [...] [31317.206261] systemd-journald[341]: Failed to write entry (29 items, 682 bytes), ignoring: Cannot allocate memory [31330.715806] systemd-journald[341]: Failed to write entry (21 items, 547 bytes), ignoring: Cannot allocate memory [31330.756475] systemd-journald[341]: Failed to write entry (21 items, 549 bytes), ignoring: Cannot allocate memory [31330.756946] systemd-journald[341]: Failed to write entry (21 items, 633 bytes), ignoring: Cannot allocate memory [31330.757454] systemd-journald[341]: Failed to write entry (21 items, 629 bytes), ignoring: Cannot allocate memory [31331.070486] systemd-journald[341]: Failed to write entry (22 items, 577 bytes), ignoring: Cannot allocate memory [31331.070625] systemd-journald[341]: Failed to write entry (22 items, 564 bytes), ignoring: Cannot allocate memory [31331.103742] systemd-journald[341]: Failed to write entry (22 items, 581 bytes), ignoring: Cannot allocate memory [31331.103878] systemd-journald[341]: Failed to write entry (22 items, 548 bytes), ignoring: Cannot allocate memory [31331.104589] systemd-journald[341]: Failed to write entry (22 items, 562 bytes), ignoring: Cannot allocate memory [31334.787786] systemd-journald[341]: Failed to write entry (24 items, 611 bytes), ignoring: Cannot allocate memory [31335.992491] systemd-journald[341]: Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory [...] Also the committed memory size as recored by munin (see attached image) spikes quickly. You can clearly spot in the graph, when I upgraded to systemd_240-4. You can also see the times where I manually restarted journald. (Yes, this system is a bit small for all the services running on it, hence the swap usage.) I now have downgraded to systemd_240-3 which resolves this issue for me. Other systems of mine show the same, but because they have more RAM, the problem is not as visible (yet). Grüße, Sven. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.13.2-3 ii libaudit11:2.8.4-2 ii libblkid12.33.1-0.1 ii libc62.28-5 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.6-1 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.5-2 ii libgpg-error01.33-3 ii libidn11 1.33-2.2 ii libip4tc01.8.2-3 ii libkmod2 25-2 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.2-1.3 ii libmount12.33.1-0.1 ii libpam0g 1.1.8-4 ii libseccomp2 2.3.3-3 ii libselinux1 2.8-1+b1 ii libsystemd0 240-4 ii mount2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus1.12.12-1 ii libpam-systemd 240-4 Versions of packages systemd suggests: ii policykit-10.105-25 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.132 ii udev 240-4 -- Configuration Files: /etc/systemd/journald.conf changed: [Journal] Storage=persistent ForwardToConsole=yes TTYPath=/dev/tty12 /etc/systemd/logind.conf changed: [Login] KillUserProcesses=no /etc/systemd/system.conf changed: [Manager] RuntimeWatchdogSec=60 -- debconf-show failed --- End Message --- --- Begin Message --- Source: systemd Source-Version: 240-5 We believe
Bug#920702: marked as done (RM: webdis [mips64el] -- RoQA; Unbuildable, blocking cruft removal)
Your message dated Mon, 28 Jan 2019 13:23:31 + with message-id and subject line Bug#920702: Removed package(s) from unstable has caused the Debian Bug report #920702, regarding RM: webdis [mips64el] -- RoQA; Unbuildable, blocking cruft removal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal Package is long-term unbuildable on mips64el (#907754) and is blocking removal of cruft binary libhiredis0.13. Scott K --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: webdis | 0.1.2+dfsg-2 | mips64el webdis-dbg | 0.1.2+dfsg-2 | mips64el --- Reason --- RoQA; Unbuildable, blocking cruft removal -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/920702 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#920668: marked as done (light-locker: debug mode crashes after unlock)
Your message dated Mon, 28 Jan 2019 13:36:36 + with message-id and subject line Bug#892290: fixed in light-locker 1.8.0-3 has caused the Debian Bug report #892290, regarding light-locker: debug mode crashes after unlock 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.) -- 892290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: light-locker Version: 1.8.0-2 Severity: normal Dear Maintainer, I tried to see what happens with light-locker when I experience screen wakeup issues. I then launched light-locker with the --debug option, which seemed to work, until I unlocked it which resulted in : [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:18): obj_path=(null) interface=(null) method=(null) destination=:1.2599 [switch_greeter_timeout] gs-manager.c:430 (08:53:27):Switch to greeter timeout [gs_listener_send_switch_greeter] gs-listener-dbus.c:139 (08:53:27): Send switch greeter [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:28): obj_path=/org/freedesktop/login1/session/_31013 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null) [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:28): obj_path=/org/freedesktop/login1/session/c17 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null) [listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (08:53:28): obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null) dbus[18962]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Abandon I guess this isn't the expected behaviour. Hope this helps, Best regards. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages light-locker depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libc62.28-5 ii libcairo21.16.0-2 ii libdbus-1-3 1.12.12-1 ii libdbus-glib-1-2 0.110-3 ii libglib2.0-0 2.58.2-3 ii libgtk-3-0 3.24.4-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libsystemd0 240-4 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxss1 1:1.2.3-1 ii lightdm 1.26.0-3 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information -- Olivier BERGER https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) --- End Message --- --- Begin Message --- Source: light-locker Source-Version: 1.8.0-3 We believe that the bug you reported is fixed in the latest version of light-locker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yves-Alexis Perez (supplier of updated light-locker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 14:18:26 +0100 Source: light-locker Architecture: source Version: 1.8.0-3 Distribution: unstable Urgency: medium Maintainer: Debian
Bug#892290: marked as done (light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect)
Your message dated Mon, 28 Jan 2019 13:36:36 + with message-id and subject line Bug#892290: fixed in light-locker 1.8.0-3 has caused the Debian Bug report #892290, regarding light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect 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.) -- 892290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: light-locker Version: 1.8.0-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, Light-locker crashes when I unlock my session. This means that my session is not locked the next time it should be, When I run light-locker at the command line I see: % light-locker --lock-after-screensaver=3600 dbus[26450]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Aborted I've installed light-locker-dbgsym but the didn't improve the error message. I have various XDG environment variables set. % env | grep XDG XDG_CONFIG_HOME=/home/stuart/.config XDG_MENU_PREFIX=lxde- XDG_VTNR=7 XDG_SESSION_ID=2 XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/stuart XDG_SESSION_TYPE=x11 XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/ XDG_SESSION_DESKTOP=LXDE XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 XDG_CURRENT_DESKTOP=LXDE XDG_SEAT=seat0 XDG_RUNTIME_DIR=/run/user/1000 XDG_DATA_HOME=/home/stuart/.local/share XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 XDG_CONFIG_DIRS=/etc/xdg -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages light-locker depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.1-3 ii libc62.27-1 ii libcairo21.15.10-2 ii libdbus-1-3 1.12.6-2 ii libdbus-glib-1-2 0.110-2 ii libglib2.0-0 2.54.3-2 ii libgtk-3-0 3.22.28-1 ii libpango-1.0-0 1.40.14-1 ii libpangocairo-1.0-0 1.40.14-1 ii libsystemd0 237-4 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxss1 1:1.2.2-1+b2 ii lightdm 1.18.3-4 light-locker recommends no packages. light-locker suggests no packages. -- Configuration Files: /etc/xdg/autostart/light-locker.desktop changed: [Desktop Entry] Type=Application Name=Screen Locker Name[ca]=Bloquejador de pantalla Name[cs]=Uzamykač obrazovky Name[da]=Skærmlås Name[de]=Bildschirmsperre Name[en_GB]=Screen Locker Name[es]=Bloqueador de pantalla Name[fa]=قفل صفحه Name[fi]=Näytön lukitusohjelma Name[fr]=Verrouilleur d'écran Name[gl]=Bloqueado da pantalla Name[gu]=સ્ક્રીન લૉકર Name[hi]=परदा अबरोधक Name[hu]=Képernyőzár Name[it]=Blocca schermo Name[ja]=スクリーンのロック Name[kk]=Экран блоктаушысы Name[lt]=Ekrano užrakinimas Name[nb]=Skjermlås Name[nl]=Schermvergrendeling Name[or]=ପରଦା ଅବରୋଧକ Name[pl]=Blokada ekranu Name[pt]=Bloqueio de Ecrã Name[pt_BR]=Bloqueio de Tela Name[ru]=Блокировщик экрана Name[sk]=Uzamykač obrazovky Name[tr]=Ekran Kilitleyici Name[zh_CN]=屏幕锁 Name[zh_TW]=螢幕鎖定 Comment=Launch screen locker program Comment[ca]=Obre el programa de bloqueig de la pantalla Comment[cs]=Spustit Uzamykač obrazovky Comment[da]=Start program for skærmlås Comment[de]=Bildschirmsperre starten Comment[en_GB]=Launch screen locker program Comment[es]=Abrir el programa de bloqueo de pantalla Comment[fi]=Käynnistä näytön lukitusohjelma Comment[fr]=Lancer le verrouilleur d'écran Comment[gl]=Iniciar o programa de bloqueo da pantalla Comment[gu]=સ્ક્રીન લૉકર પ્રક્રિયાને શરુ કરો Comment[hi]=परदा अबरोधक प्रोग्राम आरम्भ
Bug#920666: marked as done (light-locker: Please include upstream README in the packaged docs)
Your message dated Mon, 28 Jan 2019 13:36:36 + with message-id and subject line Bug#920666: fixed in light-locker 1.8.0-3 has caused the Debian Bug report #920666, regarding light-locker: Please include upstream README in the packaged docs 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.) -- 920666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: light-locker Version: 1.8.0-2 Severity: minor Dear Maintainer, Please include upstream's README in the packaged docs, which includes interesting details ligne the existence of light-locker-command to interact with the locker. Thanks in advance. Best regards, -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages light-locker depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libc62.28-5 ii libcairo21.16.0-2 ii libdbus-1-3 1.12.12-1 ii libdbus-glib-1-2 0.110-3 ii libglib2.0-0 2.58.2-3 ii libgtk-3-0 3.24.4-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libsystemd0 240-4 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxss1 1:1.2.3-1 ii lightdm 1.26.0-3 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information -- Olivier BERGER https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) --- End Message --- --- Begin Message --- Source: light-locker Source-Version: 1.8.0-3 We believe that the bug you reported is fixed in the latest version of light-locker, 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. Yves-Alexis Perez (supplier of updated light-locker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 14:18:26 +0100 Source: light-locker Architecture: source Version: 1.8.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers Changed-By: Yves-Alexis Perez Closes: 892290 920666 Changes: light-locker (1.8.0-3) unstable; urgency=medium . * d/patches: fallback to XDG_SESSION_ID if sd_session_id is NULL (closes: #892290) * d/patches: print an error if session_id is NULL * d/control: update standards version to 4.3.0 * drop consolekit support since it's not in Debian anymore * d/docs: add upstream README (closes: #920666) Checksums-Sha1: 30f861620447cbbe35a36e82654def06fde66f3b 1773 light-locker_1.8.0-3.dsc f3cdef898cd16a9a52cb05bd103e2554aa677684 3508 light-locker_1.8.0-3.debian.tar.xz 3e32a8d9dd9a0a8a5ea12e0237f12b40239909f3 15073 light-locker_1.8.0-3_amd64.buildinfo Checksums-Sha256: 6ce9a3d53540c5269c67fe002e3bc71d4641cc83e8f5da506bbd87c75b039073 1773 light-locker_1.8.0-3.dsc 5d7e137170317a20a0752ffd5add6e8477bc5ad0e4c264ec97bfe956e198d258 3508 light-locker_1.8.0-3.debian.tar.xz 21280035c0324f7580d85a82fd894f8fcec61346c916c3c6f95ba9fb124220f8 15073 light-locker_1.8.0-3_amd64.buildinfo Files: 0d6368af9b571a475d5ff49e2e12899e 1773 x11 optional light-locker_1.8.0-3.dsc 469b58347db48b6b97c44652318157d9 3508 x11 optional light-locker_1.8.0-3.debian.tar.xz 8c590f8d028875cec9b7eae637b2096b 15073 x11 optional light-locker_1.8.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#919407: marked as done (unattended-upgrades: Log includes too much "(Reading database ... X%)" spam lines)
Your message dated Mon, 28 Jan 2019 15:59:54 + with message-id and subject line Bug#919407: fixed in unattended-upgrades 1.10 has caused the Debian Bug report #919407, regarding unattended-upgrades: Log includes too much "(Reading database ... X%)" spam lines 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.) -- 919407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unattended-upgrades Version: 1.9 Severity: minor When receiving email notifications from "unattended-upgrades", it would be nice if they only included relevant information. Getting 20 lines of "(Reading database ... X%)" with X ranging from "" to "100%" in steps of 5%, * for * each * package * installed *[1], is quite some noise that could be removed from the output. Thanks a lot for considering that! Ad 1: Yes, I know - Unattended-Upgrade::MinimalSteps. But that's a feature and by design! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unattended-upgrades depends on: ii apt1.8.0~alpha3 ii apt-utils 1.8.0~alpha3 ii debconf [debconf-2.0] 1.5.69 ii init-system-helpers1.56+nmu1 ii lsb-base 10.2018112800 ii lsb-release10.2018112800 ii python33.7.1-3 ii python3-apt1.7.0 ii python3-dbus 1.2.8-2+b3 pn python3-distro-info ii ucf3.0038+nmu1 ii xz-utils 5.2.2-1.3 Versions of packages unattended-upgrades recommends: ii anacron 2.3-27 ii cron [cron-daemon] 3.0pl1-130 ii systemd-sysv240-2 Versions of packages unattended-upgrades suggests: ii bsd-mailx 8.1.2-0.20180807cvs-1 ii needrestart 3.3-2 ii postfix [mail-transport-agent] 3.3.2-1 ii powermgmt-base 1.33 ii python3-gi 3.30.4-1 -- --- End Message --- --- Begin Message --- Source: unattended-upgrades Source-Version: 1.10 We believe that the bug you reported is fixed in the latest version of unattended-upgrades, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey (supplier of updated unattended-upgrades package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 21:35:26 +0700 Source: unattended-upgrades Binary: unattended-upgrades Architecture: source Version: 1.10 Distribution: unstable Urgency: medium Maintainer: Michael Vogt Changed-By: Balint Reczey Description: unattended-upgrades - automatic installation of security upgrades Closes: 918323 919407 Launchpad-Bugs-Fixed: 1599646 Changes: unattended-upgrades (1.10) unstable; urgency=medium . * autopkgtest: Check if upgrading in minimal steps is the default * Comment out example blacklist item that slipped in to the default config * Don't print error on empty /var/run/reboot-required.pkgs * Fix filtering out dpkg progress indicator (LP: #1599646) (Closes: #919407) * Clear cache after checking upgrades against the blacklist again. This fixes the issue when the dirty cache caused all packages to be upgraded in the first "minimal" step. Thanks to Paul Wise * Populate cache for the fetcher after calculate_upgradable_pkgs() left it clean. Otherwise the packages are downloaded later skipping the conffile tests and possibly failing in a package installation step due to changed config files. (Closes: #918323) * Fix non-minimal upgrades Checksums-Sha1: baa578e96c6c86d4b4cc83f9b5326c2f05e63cc6 1869 unattended-upgrades_1.10.dsc
Bug#641858: marked as done (debian/control wording review)
Your message dated Mon, 28 Jan 2019 14:47:47 +0100
with message-id <20190128134747.pbc5yytfztiik...@haka.dresden.de>
and subject line Re: texlive-base: General update after the debconf review
process
has caused the Debian Bug report #641858,
regarding debian/control wording review
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.)
--
641858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Saturday, August 06, 2011, I notified you of the beginning of a review
process
concerning debconf templates for texlive-base.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading texlive-base with these changes
right now.
The second phase of this process will begin on Wednesday, August 24, 2011, when
I will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Wednesday, September 14, 2011. Please avoid uploading a package with
fixed or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Thursday, September 15, 2011, I will contact you again and will send a
final patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages tex-common depends on:
ii cdebconf [debconf-2.0] 0.157 Debian Configuration Management Sy
ii debconf [debconf-2.0]1.5.41 Debian configuration management sy
ii dpkg 1.16.0.3Debian package management system
ii ucf 3.0025+nmu2 Update Configuration File: preserv
Versions of packages tex-common suggests:
ii debhelper 8.9.4 helper programs for debian/rules
Versions of packages texlive-base is related to:
ii tex-common2.10 common infrastructure for building
ii texlive-binaries 2009-10Binaries for TeX Live
--- texlive-base.old/debian/templates 2011-08-04 09:44:52.381053401 +0200
+++ texlive-base/debian/templates 2011-08-21 14:08:35.301419040 +0200
@@ -1,20 +1,31 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: texlive-base/texconfig_ignorant
Type: error
-_Description: TeX configuration cannot handle the system paper size
${libpaperPaper}
- Your system-wide paper size is set to ${libpaperPaper}. However, the
+#flag:translate!:5
+_Description: Unmanageable system paper size (${libpaperPaper})
+ The currently defined system-wide paper size is ${libpaperPaper}. However, the
TeX configuration system cannot handle this paper size for ${binary}.
.
The setting will remain unchanged.
.
- For a list of paper sizes known for ${binary}, execute
+ The following command can show the list of known paper sizes for
+ ${binary}:
.
texconfig ${binary_commandline} paper
Template: texlive-base/binary_chooser
Type: multiselect
-_Description: Choose TeX binaries that should use system paper size
- Currently, the TeX binaries have
Bug#920193: marked as done (nmu: krita_1:4.1.7+dfsg-1)
Your message dated Mon, 28 Jan 2019 15:51:37 +0100 with message-id <25fdba27-663c-56e2-bc06-84bcfe9d1...@debian.org> and subject line Re: Bug#920193: nmu: krita_1:4.1.7+dfsg-1 has caused the Debian Bug report #920193, regarding nmu: krita_1:4.1.7+dfsg-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.) -- 920193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi! Accroding to #918370 Krtita was relying on a Qt bug to work. The fix is already in the archive, but it needs to be rebuilt against the current Qt version in order to be used (compile time checks). So please binNMU krita on all archs. nmu krita_1:4.1.7+dfsg-1 . ANY . unstable . -m "Rebuild against Qt 5.11.3" Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, armhf Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On 22/01/2019 16:10, Lisandro Damián Nicanor Pérez Meyer wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi! Accroding to #918370 Krtita was relying on a Qt bug to work. > The fix is already in the archive, but it needs to be rebuilt against > the current Qt version in order to be used (compile time checks). > > So please binNMU krita on all archs. > > nmu krita_1:4.1.7+dfsg-1 . ANY . unstable . -m "Rebuild against Qt 5.11.3" Scheduled. Emilio--- End Message ---
Bug#920662: marked as done (orthanc-mysql: uses $(DEB_VERSION) as SOVERSION)
Your message dated Mon, 28 Jan 2019 12:21:27 + with message-id and subject line Bug#920662: fixed in orthanc-mysql 2.0-2 has caused the Debian Bug report #920662, regarding orthanc-mysql: uses $(DEB_VERSION) as SOVERSION 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.) -- 920662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: orthanc-mysql Version: 1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, $ lintian orthanc-mysql_1.1-1+b1_amd64.deb W: orthanc-mysql: package-name-doesnt-match-sonames libOrthancMySQLIndex1.1-1+b1 libOrthancMySQLStorage1.1-1+b1 E: orthanc-mysql: ldconfig-symlink-missing-for-shlib usr/lib/libOrthancMySQLIndex.so.1.1-1+b1 usr/lib/libOrthancMySQLIndex.so.1.1-1 libOrthancMySQLIndex.so.1.1-1+b1 E: orthanc-mysql: ldconfig-symlink-missing-for-shlib usr/lib/libOrthancMySQLStorage.so.1.1-1+b1 usr/lib/libOrthancMySQLStorage.so.1.1-1 libOrthancMySQLStorage.so.1.1-1+b1 This is also reproducible with 2.0-1. Using $(DEB_VERSION) in the SONAME of the library is, well, insane. Since the library has a strange naming that makes it nearly impossible to be used as a regular shared library (and it seems to used rather as a plugin loaded via the .so extension, no no version weirdness involved), the question arises "why is it in/usr/lib nevertheless?" Andreas --- End Message --- --- Begin Message --- Source: orthanc-mysql Source-Version: 2.0-2 We believe that the bug you reported is fixed in the latest version of orthanc-mysql, 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. Sebastien Jodogne (supplier of updated orthanc-mysql package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 11:55:02 +0100 Source: orthanc-mysql Binary: orthanc-mysql orthanc-mysql-dbgsym Architecture: source amd64 Version: 2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Description: orthanc-mysql - Plugins to use MySQL or MariaDB as a database back-end to Orthanc Closes: 920662 Changes: orthanc-mysql (2.0-2) unstable; urgency=medium . * Removed $(DEB_VERSION) from SOVERSION. Closes: #920662 Checksums-Sha1: 6f783663a4befbf859e3defe41284f4982217e63 2168 orthanc-mysql_2.0-2.dsc 11ead7ff07ce3da9e35200f9e819adb180b777b9 1422764 orthanc-mysql_2.0-2.debian.tar.xz bf892d069b84cb51484469f5b15afc7e2e618656 14885808 orthanc-mysql-dbgsym_2.0-2_amd64.deb 8a5f5abef5e6150a813904e21931d652fc91fc23 13181 orthanc-mysql_2.0-2_amd64.buildinfo 8aaf03cec84e07516d217bdd324a8c88d1eaf33f 373140 orthanc-mysql_2.0-2_amd64.deb Checksums-Sha256: 7a602d7125fb0d0b30beffed59dc57223097b2a55da1d300e74ebb0c497a4fc0 2168 orthanc-mysql_2.0-2.dsc 9a5d7bdf632c192513032ffa93f6e3864337ab43a689e323ebeb523d99598778 1422764 orthanc-mysql_2.0-2.debian.tar.xz d334f15507fd57d1ce3aea31b3138072c9a804ea80f700e3efea0c2a3cb7fe84 14885808 orthanc-mysql-dbgsym_2.0-2_amd64.deb d0f5b789849a361bdf0ca063dc5e4b84313cd018f7eb30c0b40bb5f415ad75ad 13181 orthanc-mysql_2.0-2_amd64.buildinfo d26da053ab2e50ab621bfaeca0f1ef911590a96515a3e95c71d42e98a1e01b69 373140 orthanc-mysql_2.0-2_amd64.deb Files: b6ec9673f4cadf6438a9eb8167c15ee5 2168 science optional orthanc-mysql_2.0-2.dsc f87e94ad351055e35fca26965bf96c0f 1422764 science optional orthanc-mysql_2.0-2.debian.tar.xz 7d19afb3a343a13dd54a1888979cafe8 14885808 debug optional orthanc-mysql-dbgsym_2.0-2_amd64.deb 4990591bf83272c873d60c2c77134654 13181 science optional orthanc-mysql_2.0-2_amd64.buildinfo 39eeaa867c97a13d151cdb049c96a3e5 373140 science optional orthanc-mysql_2.0-2_amd64.deb -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAlxO7hkUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw10gcA/9GMtAdv82CpAtJ2C/Exg7A7JuKhk2
Bug#321198: marked as done (piwi: Apache::DBI not needed)
Your message dated Mon, 28 Jan 2019 12:31:24 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #321198, regarding piwi: Apache::DBI not needed 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.) -- 321198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: piwi Version: 0.8+20041206-3 Severity: important Hi, as far as I can tell, piwi works as a cgi script here. To confirm that, I mucked with my /var/lib/dpkg/status, removed libapache-dbi-perl and libapache-mod-perl packages, restarted Apache and piwi still works. The dependency on libapache-dbi-perl seems superfluous. What's more confusing, the provided /etc/piwi/httpd.conf sets up a cgi-handler for .pl files in piwi directory, but then loads a PerlModule (which AFAIK will not be used at all in a cgi). This looks Just Plain Wrong. A clean cgi-based default config looks fine as a solution: just remove the PerlModule line and replace libapache-dbi-perl dependency with libdbi-perl. If you want to stick with the mod_perl alternative, you could provide another httpd.conf (in doc/piwi/examples/?) with a clean mod_perl configuration (no cgi-handler stuff), and replace the dependency with "libdbi-perl | libapache-dbi-perl". I think there's no need to depend on mod_perl (and friends) if piwi can work without it. Regards, Zoran -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.31-grsec Locale: LANG=hr_HR, LC_CTYPE=hr_HR (charmap=ISO-8859-2) Versions of packages piwi depends on: ii apache [httpd]1.3.33-6 versatile, high-performance HTTP s ii libapache-dbi-perl0.94-2 Connect apache server to database ii libdate-calc-perl 5.4-3 Perl library for accessing dates ii libdbd-mysql-perl 2.9006-1 A Perl5 database interface to the ii mysql-client 4.0.24-10 mysql database client binaries ii perl 5.8.4-8Larry Wall's Practical Extraction ii postgresql-client 7.4.8-1cn0 front-end programs for PostgreSQL -- no debconf information --- End Message --- --- Begin Message --- Version: 0.8+20041206-4+rm Dear submitter, as the package piwi has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920679 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#920679: marked as done (RM: piwi -- Orphaned, not updated, buggy)
Your message dated Mon, 28 Jan 2019 12:31:18 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #920679, regarding RM: piwi -- Orphaned, not updated, buggy 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.) -- 920679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal The piwi package hasn't been updated upstream since 2004, was orphaned two years ago, and has bugs like https://bugs.debian.org/706244 with no response in 5+ years. Please remove it from unstable and testing. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: piwi | 0.8+20041206-4 | source, all --- Reason --- Orphaned, not updated, buggy -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/920679 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#838922: marked as done (O: piwi -- P(erl|relude) IDS Web Interface - A frontend to your Prelude database)
Your message dated Mon, 28 Jan 2019 12:31:24 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #838922, regarding O: piwi -- P(erl|relude) IDS Web Interface - A frontend to your Prelude database 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.) -- 838922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp The current maintainer of piwi, Mickael Profeta , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: piwi Binary: piwi Version: 0.8+20041206-3 Maintainer: Mickael Profeta Build-Depends-Indep: debhelper (>= 4.0.0) Architecture: all Standards-Version: 3.6.1.0 Format: 1.0 Files: b3fecf766e886efd114b7f8af8c2682d 581 piwi_0.8+20041206-3.dsc 6a41e2f352650c82f0b3b534851f78cb 162635 piwi_0.8+20041206.orig.tar.gz e336a52b258b60bb4bf7877b4916258c 2908 piwi_0.8+20041206-3.diff.gz Checksums-Sha256: c441b21c5dd1cdd36e38f5d58a68a3ffdbb4f35f134ad04eda20f771024d88d0 581 piwi_0.8+20041206-3.dsc 9d11cac2430a74ea43800b18c126a576bf209923e7b6d67a4099184de48093fb 2908 piwi_0.8+20041206-3.diff.gz d1e8c6313c7fd96f5d6515b6b910d8ba86f52132dd3bbbe64c8054533d1f857c 162635 piwi_0.8+20041206.orig.tar.gz Directory: pool/main/p/piwi Priority: source Section: admin Package: piwi Version: 0.8+20041206-3 Installed-Size: 1068 Maintainer: Mickael Profeta Architecture: all Depends: perl, apache | apache-ssl | apache-perl | httpd, mysql-client | postgresql-client, libapache-dbi-perl, libdbd-mysql-perl | libdbd-pg-perl, libdate-calc-perl Suggests: libgd-gd2-perl, geoip-bin Description: P(erl|relude) IDS Web Interface - A frontend to your Prelude database Description-md5: 30be9c3cee5be6b013f2e78b530dc70b Tag: devel::lang:sql, implemented-in::perl, interface::web, security::ids, web::application, works-with::db Section: admin Priority: optional Filename: pool/main/p/piwi/piwi_0.8+20041206-3_all.deb Size: 157764 MD5sum: 8b66a85b9bb2fe60fdcf34e21c90a0a8 SHA256: b6978332e71518eecea2b9b1fec9a1afce153a6574ac9a1b5c636ec138b72fe2 -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.8+20041206-4+rm Dear submitter, as the package piwi has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920679 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#706244: marked as done (piwi: Ships cache files in the binary package)
Your message dated Mon, 28 Jan 2019 12:31:24 + with message-id and subject line Bug#920679: Removed package(s) from unstable has caused the Debian Bug report #706244, regarding piwi: Ships cache files in the binary package 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.) -- 706244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: piwi Version: 0.8+20041206-3 Severity: normal Hi! This package ships cache files (under /var/cache/piwi/) on the binary package. This is wrong, as those files might get removed by the system at any time, they should be either generated at installation or ideally at runtime, because the program needs to work even if these are not present when starting. I don't know if this would be the the case here, but the software should consequently be checked to make sure it works even if the /var/cache/piwi/ directory or its contents have disappeared. Thanks, Guillem --- End Message --- --- Begin Message --- Version: 0.8+20041206-4+rm Dear submitter, as the package piwi has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920679 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#920264: marked as done (postfixadmin: please add postfixadmin-cli to PATH)
Your message dated Mon, 28 Jan 2019 15:23:40 + with message-id and subject line Bug#920264: fixed in postfixadmin 3.2.1-2 has caused the Debian Bug report #920264, regarding postfixadmin: please add postfixadmin-cli to PATH 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.) -- 920264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postfixadmin Version: 3.0.2-2 Severity: wishlist Dear Maintainer, I've stumbled upon /usr/share/postfixadmin/scripts/postfixadmin-cli mostly through it getting mentioned on IRC. It would be helpful if that script is already available directly. It doesn't even has execute permissions set there, so one would have to call it through bash. Probably putting it into /usr/sbin given that it needs access to files not readable by the general user. Thanks :) Rhonda --- End Message --- --- Begin Message --- Source: postfixadmin Source-Version: 3.2.1-2 We believe that the bug you reported is fixed in the latest version of postfixadmin, 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. Christoph Martin (supplier of updated postfixadmin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 14:16:05 +0100 Source: postfixadmin Binary: postfixadmin Architecture: source Version: 3.2.1-2 Distribution: unstable Urgency: medium Maintainer: Norman Messtorff Changed-By: Christoph Martin Description: postfixadmin - Virtual mail hosting interface for Postfix Closes: 920264 920564 Changes: postfixadmin (3.2.1-2) unstable; urgency=medium . * remove backported code which results in errors (closes: #920564) * link /usr/share/postfixadmin/scripts/postfixadmin-cli to /usr/bin closes: #920264) Checksums-Sha1: f9e5067712056d4220ff9a2dde8ee2e96eaf04e8 1979 postfixadmin_3.2.1-2.dsc 5e811f6235fff6dd4d7d66c69cccd3e7cdef3748 8768 postfixadmin_3.2.1-2.debian.tar.xz 7caa09e7121cb8b33eacdd7e154004ace32e75e0 7155 postfixadmin_3.2.1-2_amd64.buildinfo Checksums-Sha256: d7db3da3926e1f8c03a749d90d0a9f764293a64324125da35fe414b0945e854c 1979 postfixadmin_3.2.1-2.dsc e3f5a36abf9937d245eac7ec76e78b5b253e0d2be2ddae99641530d02853c109 8768 postfixadmin_3.2.1-2.debian.tar.xz f047b326e14a89f4bb8a0d0c4f7a16b290cdd1e6270d3e14261c8f5fecd9291f 7155 postfixadmin_3.2.1-2_amd64.buildinfo Files: 7e95efb5f04be2560885ad2da43a11a0 1979 admin optional postfixadmin_3.2.1-2.dsc 56ca80e49b8004626c7463d45856f852 8768 admin optional postfixadmin_3.2.1-2.debian.tar.xz 57f3b89b5f07fdbfcacaf8cac27390b7 7155 admin optional postfixadmin_3.2.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETwdS4qMJ+W/NthRq+m7tdFwC8X4FAlxPDB8ACgkQ+m7tdFwC 8X66ZxAAjeJTFR/YDDuZid4doVyTPpcyRYkK4nmYRCQbveg9g0IzZXFTZlcHKY2D ZvjUsMsE0DXupMP0/omObublRUj42q3WOtFq0zzG5zhLDrJXLJ7bOoIUc48rY5IA oJjhUzMv4Sj8ujPbiCE66FcFKbvx+Mkr+74ditYZUKare3pXzJQB34KLM7sa8V2/ 8ZcUkHV9pwAkVVvVmxkE8wUkuy6G9FKya5qJuai3mp3jdq9eWiuJoKDouupDYzVK WqKqlbMmEjshpbTFIpcNboTzOTqgn8HpEHGtgAsqVWIBKulS7kScNqobgqvrRNsP JvFORSPLrHO+gvsZ29jYTFA/XTQphl/IfH+BNNFflVC5FV2+6na2JDr1izhoMV2q 92+V+UvCW57sVgt1oxRa11z8Dh18VGZEnTyTVyuj4EsHwFwS9HcwDk+Cke+I5rzN gyZ5BFJMGHCevTVsL9URcopSwIdZ0u7+VQKY+5NVxECBG8HKEfEVNJbfAiO1+VD/ 7Jc0UAs4J/iNvjYn/e7yXkpGdT+ZenYluKMCrBX/SwVUpoxnisbpTiZrOgMB1SF1 lc6Dwg7n7gn0gs67SLH//3I9mWkYm8cDQSEtVa8vEM24EZTuV90h2oVcAbuBHp0u a6OqHBKkErNXM14O3mv7iDb+1e0JUJe11zZCYYYfyU71PIQGJFM= =SwZ1 -END PGP SIGNATURE End Message ---
Bug#920564: marked as done (Unknown configuration: password_expiration, show_vacation and show_disabled)
Your message dated Mon, 28 Jan 2019 15:23:40 +
with message-id
and subject line Bug#920564: fixed in postfixadmin 3.2.1-2
has caused the Debian Bug report #920564,
regarding Unknown configuration: password_expiration, show_vacation and
show_disabled
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.)
--
920564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: Postfixadmin
Version: 3.2.1-1
Severity: minor
Tags: patch fixed-upstream upstream
Dear maintainer!
There are new bugs introduced with 3.2.1...
* Issue 235:
https://github.com/postfixadmin/postfixadmin/issues/235#issuecomment-456551448
* Patch 1:
https://github.com/postfixadmin/postfixadmin/commit/d9326a1f38bf0ffe33e627fada9df71e0a00cc17.patch
* Patch 2:
https://github.com/postfixadmin/postfixadmin/commit/477ede0175abb100889bcc594ee95885503aa5a2.patch
It would be great if you could add a patch for this issue before Buster
release. I've attached an alternative patch which fixes all mentioned
errors, use whatever you prefer.
--
With kind regards,
Christian Schrötter
--- a/functions.inc.php 2019-01-12 21:46:34.0 +0100
+++ b/functions.inc.php 2019-01-24 01:44:34.971950615 +0100
@@ -2137,42 +2137,6 @@ function gen_show_status($show_alias) {
}
}
-// Vacation CHECK
-if ( $CONF['show_vacation'] == 'YES' ) {
-$stat_result = db_query("SELECT * FROM ". $CONF['database_tables']['vacation'] ." WHERE email = '" . $show_alias . "' AND active = '" . db_get_boolean(true) . "'") ;
-if ($stat_result['rows'] == 1) {
-$stat_string .= "" . $CONF['show_status_text'] . "";
-} else {
-$stat_string .= $CONF['show_status_text'] . "";
-}
-}
-
-// Disabled CHECK
-if ( $CONF['show_disabled'] == 'YES' ) {
-$stat_result = db_query("SELECT * FROM ". $CONF['database_tables']['mailbox'] ." WHERE username = '" . $show_alias . "' AND active = '" . db_get_boolean(false) . "'");
-if ($stat_result['rows'] == 1) {
-$stat_string .= "" . $CONF['show_status_text'] . "";
-} else {
-$stat_string .= $CONF['show_status_text'] . "";
-}
-}
-
-// Expired CHECK
-if ( Config::bool('password_expiration') && Config::bool('show_expired') ) {
-$now = 'now()';
-if (db_sqlite()) {
-$now = "datetime('now')";
-}
-
-$stat_result = db_query("SELECT * FROM ". $CONF['database_tables']['mailbox'] ." WHERE username = '" . $show_alias . "' AND password_expiry <= $now AND active = '" . db_get_boolean(true) . "'");
-
-if ($stat_result['rows'] == 1) {
-$stat_string .= "" . $CONF['show_status_text'] . "";
-} else {
-$stat_string .= $CONF['show_status_text'] . "";
-}
-}
-
// POP/IMAP CHECK
if ($CONF['show_popimap'] == 'YES') {
$stat_delimiter = "";
--- End Message ---
--- Begin Message ---
Source: postfixadmin
Source-Version: 3.2.1-2
We believe that the bug you reported is fixed in the latest version of
postfixadmin, 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.
Christoph Martin (supplier of updated postfixadmin
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Jan 2019 14:16:05 +0100
Source: postfixadmin
Binary: postfixadmin
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Norman Messtorff
Changed-By: Christoph Martin
Description:
postfixadmin - Virtual mail hosting interface for Postfix
Closes: 920264 920564
Changes:
postfixadmin (3.2.1-2) unstable; urgency=medium
.
* remove backported code which results in errors (closes: #920564)
* link /usr/share/postfixadmin/scripts/postfixadmin-cli to /usr/bin
closes: #920264)
Checksums-Sha1:
f9e5067712056d4220ff9a2dde8ee2e96eaf04e8 1979 postfixadmin_3.2.1-2.dsc
5e811f6235fff6dd4d7d66c69cccd3e7cdef3748 8768
postfixadmin_3.2.1-2.debian.tar.xz
7caa09e7121cb8b33eacdd7e154004ace32e75e0 7155
Bug#906811: marked as done (FTBFS: libconfig.h: No such file or directory)
Your message dated Mon, 28 Jan 2019 15:49:44 + with message-id and subject line Bug#906811: fixed in blasr 5.3.2+dfsg-1 has caused the Debian Bug report #906811, regarding FTBFS: libconfig.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 906811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blasr Version: 5.3+0-2 Severity: serious Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, When recompiling blasr for unstable it FTBFS with: make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build make -j1 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>' make[2]: git: Command not found g++ -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/pbseq -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -g -DSHA1_7=\"\" -std=c++0x -pedantic -Wall -We xtra -Wno-div-by-zero -Wno-overloaded-virtual -MMD -MP -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/pbseq /alignment -I/usr/include/pbseq/hdf -I/usr/include/pbseq/pbdata -I/usr/include -I/usr/include/hdf5/serial -I/usr/include/htslib -I/usr/include/boost -c -o Blasr.o Blasr.cpp In file included from iblasr/BlasrMiscs.hpp:4, from Blasr.cpp:3: iblasr/BlasrHeaders.h:24:10: fatal error: libconfig.h: No such file or directory #include ^ compilation terminated. make[2]: *** [: Blasr.o] Error 1 Full log attached. Thanks, _g. - -- System Information: Distributor ID: PureOS Description:PureOS GNU/Linux 8 Release:8 Codename: green Architecture: x86_64 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blasr depends on: ii libc62.27-5 ii libgcc1 1:8.2.0-3 ii libhdf5-100 1.10.0-patch1+docs-4+b2 ii libhdf5-cpp-100 1.10.0-patch1+docs-4+b2 pn libhts2 pn libpbbam pn libpbseq ii libstdc++6 8.2.0-3 ii zlib1g 1:1.2.11.dfsg-1 blasr recommends no packages. blasr suggests no packages. -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlt8Cu8ACgkQ7+hsbH/+ z4OhTQf/bZPsdSP7SzdhPH4n7kRghAx0aH+hiRpMbwIV+KbBKrFglcVV4G6X9LJM eAI2ovx0mk27VKLPjKFA7eYkin5j3JxEvKDrSiqwu4xk7YAtHf/4rfMIJfLs1za2 oXqaWkc7GlKhX834A+0B2kxCOnmOLLETOXAoPzJl0+TFt3Ec5uJbXQSd6QLF0iJO LTm4zx8kl/3KXxQPZUHkQibC/B6G5vDHl2KoXNnAqQHqyDjFrFE5wglu4mUV/u0X 2kVaNezD7+o1HGqLEOTKXFT9rLH13EWoL79/Tcblr66jjJdgn36tFqHggVc74d5v 42+SK5GWyaR5yXNPH27mj1NS/RSF7g== =0mhM -END PGP SIGNATURE- blasr_5.3+0-2_amd64-2018-08-21T11:40:43Z.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: blasr Source-Version: 5.3.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of blasr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated blasr 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: Mon, 28 Jan 2019 16:10:36 +0100 Source: blasr Binary: blasr Architecture: source Version: 5.3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: blasr - mapping single-molecule sequencing reads Closes: 906811 Changes: blasr (5.3.2+dfsg-1) unstable; urgency=medium . * Team upload . [ Andreas Tille ] * New upstream version * Build-Depends: libpbdata-dev Closes: #906811 * d/watch: point to Github since upstream is now tagging releases * Point Vcs fields to salsa.debian.org * debhelper 12 * Standards-Version:
Bug#918323: marked as done (unattended-upgrades: tried to upgrade package with conffile prompt)
Your message dated Mon, 28 Jan 2019 15:59:54 + with message-id and subject line Bug#918323: fixed in unattended-upgrades 1.10 has caused the Debian Bug report #918323, regarding unattended-upgrades: tried to upgrade package with conffile prompt 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.) -- 918323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unattended-upgrades Version: 1.9 Severity: serious unattended-upgrades tried to upgrade a package (lvm2) with a conffile prompt and failed because conffile prompts require user input. This meant that the upgrade of lvm2 failed and was the system was left in a partially broken state. Normally unattended-upgrades refuses to upgrade packages that need conffile prompts, so this seems like a regression. I've included the full log with debug info below: Unattended upgrade result: All upgrades installed Warning: A reboot is required to complete this upgrade, or a previous one. Packages that attempted to upgrade: antlr4 cppcheck dh-golang dmeventd dmsetup gir1.2-secret-1 gnome-shell-extension-suspend-button gnome-shell-extension-weather hub kpartx libantlr4-runtime-java libcdr-0.1-1 libdevmapper-event1.02.1 libdevmapper1.02.1 libdevmapper1.02.1-dbgsym libetonyek-0.1-1 libqxp-0.0-0 libsecret-1-0 libsecret-1-0-dbgsym libsecret-common libsecret-tools libwpd-0.10-10 lvm2 python-sqlalchemy Packages with upgradable origin but kept back: gimp gimp-data libgimp2.0 Package installation log: Log started: 2019-01-04 12:49:36 [master 31e4f0db] saving uncommitted changes in /etc prior to apt run 1 file changed, 0 insertions(+), 0 deletions(-) rewrite debdelta/gnupg/random_seed (100%) apt-listchanges: Reading changelogs... apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 460811 files and directories currently installed.) Preparing to unpack .../libdevmapper1.02.1-dbgsym_2%3a1.02.155-1_amd64.deb ... Unpacking libdevmapper1.02.1-dbgsym:amd64 (2:1.02.155-1) over (2:1.02.145-4.1) ... Preparing to unpack .../dmsetup_2%3a1.02.155-1_amd64.deb ... Unpacking dmsetup (2:1.02.155-1) over (2:1.02.145-4.1) ... Setting up dmsetup (2:1.02.155-1) ... update-initramfs: deferring update (trigger activated) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 460811 files and directories currently installed.) Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.155-1_amd64.deb ... Unpacking libdevmapper1.02.1:amd64 (2:1.02.155-1) over (2:1.02.145-4.1) ... Setting up libdevmapper1.02.1:amd64 (2:1.02.155-1) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 460811 files and directories currently installed.) Preparing to unpack .../00-antlr4_4.7.1-1_all.deb ... Unpacking antlr4 (4.7.1-1) over (4.6-2) ... Preparing to unpack .../01-libantlr4-runtime-java_4.7.1-1_all.deb ... Unpacking libantlr4-runtime-java (4.7.1-1) over (4.6-2) ... Preparing to unpack .../02-cppcheck_1.86-1_amd64.deb ... Unpacking
Processed: Re: distcc: deprecation of python-support
Processing control commands: > tag -1 - experimental Bug #785990 [src:distcc] distcc: deprecation of python-support Removed tag(s) experimental. > close -1 Bug #785990 [src:distcc] distcc: deprecation of python-support Marked Bug as done -- 785990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920624: marked as done (tzdata: raspberry pi 1 hangs during upgrade of tzdata to 2018i-0+deb8u1)
Your message dated Mon, 28 Jan 2019 14:57:38 +0100 with message-id <20190128135738.gd3...@aurel32.net> and subject line Re: Bug#920624: tzdata: raspberry pi 1 hangs during upgrade of tzdata to 2018i-0+deb8u1 has caused the Debian Bug report #920624, regarding tzdata: raspberry pi 1 hangs during upgrade of tzdata to 2018i-0+deb8u1 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.) -- 920624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tzdata Version: 2018i-0+deb8u1 Severity: normal Dear Maintainer, When trying to update the system with apt-get update, the newer version of tzdata was found and during the installation the system hanged (it did not respond to any keys sent, it didn't respond to ping, the only option was a reboot). This was on raspberry pi 1 beta (2011.12 model). The last output of the update command was: Fetched 19.2 MB in 16s (1141 kB/s) Reading changelogs... Done Preconfiguring packages ... (Reading database ... 104820 files and directories currently installed.) Preparing to unpack .../tzdata_2018i-0+deb8u1_all.deb ... Unpacking tzdata (2018i-0+deb8u1) over (2018e-0+deb8u1) ... This was attempted several times, always resulting in system hanging. One of the attempts was left over night, but in the morning the system was still unresponsive, so it was not just a slow process. Now, after changing the hardware to raspberry pi 3 the update was successful. I've just put the SD card into anothe pi and did the update. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 8.0 (jessie) Release:8.0 Codename: jessie Architecture: armv7l Kernel: Linux 4.9.35-v7+ (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tzdata depends on: ii debconf [debconf-2.0] 1.5.56+deb8u1 tzdata recommends no packages. tzdata suggests no packages. -- debconf information: tzdata/Zones/Asia: tzdata/Zones/Antarctica: tzdata/Zones/Africa: * tzdata/Zones/Europe: Warsaw tzdata/Zones/Indian: * tzdata/Areas: Europe tzdata/Zones/Atlantic: tzdata/Zones/Pacific: tzdata/Zones/US: tzdata/Zones/America: tzdata/Zones/SystemV: tzdata/Zones/Australia: * tzdata/Zones/Etc: UTC tzdata/Zones/Arctic: --- End Message --- --- Begin Message --- Hi, On 2019-01-27 16:25, Filip Stachowiak wrote: > Package: tzdata > Version: 2018i-0+deb8u1 > Severity: normal > > Dear Maintainer, > > When trying to update the system with apt-get update, > the newer version of tzdata was found and during the installation > the system hanged (it did not respond to any keys sent, it didn't respond to > ping, > the only option was a reboot). This was on raspberry pi 1 beta (2011.12 > model). > > The last output of the update command was: > > Fetched 19.2 MB in 16s (1141 kB/s) > Reading changelogs... Done > Preconfiguring packages ... > (Reading database ... 104820 files and directories currently installed.) > Preparing to unpack .../tzdata_2018i-0+deb8u1_all.deb ... > Unpacking tzdata (2018i-0+deb8u1) over (2018e-0+deb8u1) ... This happens at the unpacking phase, so I doubt it is related to tzdata itself. tzdata contains a lot of small files, that might be an issue on your system. > This was attempted several times, always resulting in system hanging. > One of the attempts was left over night, but in the morning the > system was still unresponsive, so it was not just a slow process. > > > Now, after changing the hardware to raspberry pi 3 the update > was successful. I've just put the SD card into anothe pi and > did the update. If it works on another system, it shows it's not a tzdata issue. I would guess it's kernel issue, more likely at the sd card driver issue. Please report the issue there. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net--- End Message ---
Bug#915325: marked as done (r-cran-rgenoud: autopkgtest needs update for new version of glibc)
Your message dated Mon, 28 Jan 2019 18:12:57 +0200
with message-id <48a3f48e-d5e6-99a9-44e5-69fce53ef...@debian.org>
and subject line r-cran-rgenoud: autopkgtest needs update for new version of
glibc
has caused the Debian Bug report #915325,
regarding r-cran-rgenoud: autopkgtest needs update for new version of glibc
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.)
--
915325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rgenoud
Version: 5.8-2.0-2
X-Debbugs-CC: debian...@lists.debian.org, gl...@packages.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:glibc
Dear maintainers,
With a recent upload of glibc the autopkgtest of r-cran-rgenoud fails in
testing when that autopkgtest is run with the binary packages of glibc
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
glibcfrom testing2.28-1
r-cran-rgenoud from testing5.8-2.0-2
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 glibc to testing [1]. Of course, glibc shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in glibc was intended and your package needs to update to the new
situation. If needed, please change the bug's severity.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from glibc should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
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
glibc/2.28-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=glibc
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rgenoud/1418394/log.gz
> test_check("rgenoud")
Loading required package: rgenoud
## rgenoud (Version 5.8-2.0, Build Date: 2018-04-03)
## See http://sekhon.berkeley.edu/rgenoud for additional documentation.
## Please cite software as:
## Walter Mebane, Jr. and Jasjeet S. Sekhon. 2011.
## ``Genetic Optimization Using Derivatives: The rgenoud package for R.''
## Journal of Statistical Software, 42(11): 1-26.
##
-- 1. Failure: Tests the new version of genoud() where the seeds are not
given (
biclaw1$value not equal to 1.65353.
1/1 mismatches
[1] 1.67 - 1.65 == 0.0176
-- 2. Failure: Tests the new version of genoud() where the seeds are not
given (
biclaw1$par not equal to c(-0.5001947, -0.5001947).
2/2 mismatches (average diff: 0.5)
[1] -1 - -0.5 == -0.5
[2] -1 - -0.5 == -0.5
-- 3. Failure: Tests the new version of genoud() where the seeds are not
given (
biclaw1$gradients not equal to c(-1.526799e-06, -8.571643e-07).
1/2 mismatches
[1] -3e-09 - -1.53e-06 == 1.52e-06
== testthat results
===
OK: 22 SKIPPED: 0 FAILED: 3
1. Failure: Tests the new version of genoud() where the seeds are not
given (@test-genoud_no_given_seed.R#84)
2. Failure: Tests the new version of genoud() where the seeds are not
given (@test-genoud_no_given_seed.R#85)
3. Failure: Tests the new version of genoud() where the seeds are not
given (@test-genoud_no_given_seed.R#86)
Error: testthat unit tests failed
Execution halted
autopkgtest [04:54:09]: test run-unit-test: ---]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 5.8-3.0-1
Failing test dropped by upstream [1] in version 5.8-3.0.
[1]
https://github.com/JasjeetSekhon/rgenoud/commit/52ccc3619619d4662b9483523045d6635d979fd0--- End Message ---
Bug#916817: marked as done (transition: remove python3.6)
Your message dated Mon, 28 Jan 2019 13:55:32 +0100 with message-id <5c795f9b-b7db-86d1-e781-2a456d454...@debian.org> and subject line Re: Bug#916817: transition: remove python3.6 has caused the Debian Bug report #916817, regarding transition: remove python3.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition Hi, We would like to go ahead with removing python3.6 from the supported python3 versions. I don't think we are ready yet, but I'm filing this bug for tracking purposes. I'd also welcome if somebody could come up with a ben tracker. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On 19/12/2018 02:18, Mattia Rizzolo wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > We would like to go ahead with removing python3.6 from the supported > python3 versions. > > I don't think we are ready yet, but I'm filing this bug for tracking > purposes. > > I'd also welcome if somebody could come up with a ben tracker. python3.6 is now gone from testing. Cheers, Emilio--- End Message ---
Bug#787472: marked as done (distcc: push 3.2 RC1 in unstable)
Your message dated Mon, 28 Jan 2019 14:06:08 +0100 with message-id <35a63aba-d429-7ed3-c81f-f433b4e72...@debian.org> and subject line Re: distcc: push 3.2 RC1 in unstable has caused the Debian Bug report #787472, regarding distcc: push 3.2 RC1 in unstable 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.) -- 787472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distcc Severity: important 3.2 RC1 has been released upstream in 2011 and has been in exp since mid 2013, it's time to push it to unstable, and let it transit to testing Regards, Sandro -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 3.3.2-1 distcc (3.3.2-1) unstable; urgency=medium * New maintainer. * New upstream release (Closes: #892973) * debian/watch Update to new upstream repsository (Closes: 916500) * Update Brazilian Portuguese debconf templates translation. Thanks to Diego Neves (Closes: #823366) * Fix typo in /etc/default/distcc (Closes: #680063) * fix bad English in /etc/default/distcc (Closes: #680064) -- Christian Marillat Sat, 22 Dec 2018 16:39:31 +0100--- End Message ---
Bug#886720: marked as done (/usr/bin/godoc: godoc needs a rebuild against the current golang version)
Your message dated Mon, 28 Jan 2019 14:09:40 + with message-id <543f694f-7630-beaa-4680-0e63442d4...@tincho.org> and subject line Already fixed has caused the Debian Bug report #886720, regarding /usr/bin/godoc: godoc needs a rebuild against the current golang version 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.) -- 886720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-golang-x-tools Version: 1:0.0~git20170707.0.bce9606b+ds-1 Severity: normal File: /usr/bin/godoc Dear Maintainer, the godoc tool needs a rebuild against the current golang version: $ godoc -http=:6060 2018/01/09 09:46:40 newDirectory(/): stat /usr/lib/go-1.8: no such file or directory 2018/01/09 09:46:40 godoc: corpus fstree is nil It searches the source path for go 1.8 and fails, since I have go 1.9 installed. $ which godoc /usr/bin/godoc Stefan -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages golang-golang-x-tools depends on: ii libc62.25-5 ii libjs-jquery 3.2.1-1 ii libjs-jquery-ui 1.12.1+dfsg-5 Versions of packages golang-golang-x-tools recommends: ii golang-doc 2:1.9~2 golang-golang-x-tools suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- This bug was already fixed, the current x/tools look for go-1.11. CLosing now. -- Martín Ferrari (Tincho)--- End Message ---
Bug#918748: marked as done (nmu: kadu_4.1-1.1)
Your message dated Mon, 28 Jan 2019 15:59:21 +0100 with message-id and subject line Re: Bug#918748: nmu: kadu_4.1-1.1 has caused the Debian Bug report #918748, regarding nmu: kadu_4.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.) -- 918748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-CC: sha...@debian.org Package with qxmpp library was updated today and is successfully built for all supported architectures: https://buildd.debian.org/status/package.php?p=qxmpp Please schedule the binNMUs for rebuilding of kadu packages with qxmpp/1.0.0-1. nmu kadu_4.1-1.1 . ANY . buster . -m "rebuild after update of qxmpp" This is my first binNMUs, so please correct me if I am doing anything wrong. Thanks, Boris --- End Message --- --- Begin Message --- On 19/01/2019 19:38, Boris Pek wrote: > control: reopen 918748 = > > > Hi, > >> Then qxmpp ABI was broken and that needs a SONAME bump on qxmpp. > > SONAME in qxmpp library is fixed now. > Please rebuild kadu with libqxmpp1. This is done. Closing. Emilio--- End Message ---
Bug#918415: marked as done (golang-golang-x-tools FTBFS with Go 1.11)
Your message dated Mon, 28 Jan 2019 15:10:45 +
with message-id
and subject line Bug#918415: fixed in golang-golang-x-tools
1:0.0~git20190125.d66bd3c+ds-1
has caused the Debian Bug report #918415,
regarding golang-golang-x-tools FTBFS with Go 1.11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
918415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-golang-x-tools
Version: 1:0.0~git20180501.d3e4ceb5+ds-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-golang-x-tools.html
...
=== RUN TestGuru
testdata/src/softerrs/main.go:8:6: i declared but not used
--- FAIL: TestGuru (115.50s)
guru_test.go:301: Guru tests for testdata/src/referrers/main.go failed:
exit status 1.
--- testdata/src/referrers/main.golden 2019-01-03 12:48:16.976984149
-1200
+++ testdata/src/referrers/main.got 2019-01-03 12:50:41.761147882
-1200
@@ -56,5 +56,5 @@
@referrers ref-type-U
references to type U int
-open nosuchfile.y: no such file or directory (+ 1 more refs in this
file)
+open testdata/src/referrers/nosuchfile.y: no such file or directory (+
1 more refs in this file)
...
=== RUN TestImportTestdata
--- FAIL: TestImportTestdata (1.15s)
gcimporter_test.go:93: testPath(./testdata/exports): reading export data:
testdata/exports.o: cannot import, possibly version skew (unknown export format
version -1 ("i\x00\x83")) - reinstall package
=== RUN TestVersionHandling
--- PASS: TestVersionHandling (0.00s)
=== RUN TestImportStdLib
--- FAIL: TestImportStdLib (0.02s)
gcimporter_test.go:93: testPath(archive/tar): reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/archive/tar.a: cannot import, possibly version
skew (unknown export format version -1
("i\x00\x8c\x16\xc1/!$GOROOT/src/archive/tar/common.go\x00\bTypeflag\x04Name\bLinkname\x04Size\x04Mode\x03Uid\x03Gid\x05Uname\x05Gname\aModTime\x04Time\x04time"))
- reinstall package
gcimporter_test.go:93: testPath(archive/zip): reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/archive/zip.a: cannot import, possibly version
skew (unknown export format version -1
("i\x00\xe0$\xb9E!$GOROOT/src/archive/zip/reader.go\x00\x01r\bReaderAt\x02io\x04File\aComment\rdecompressors\fDecompressor\x04init\x01z\x06Reader\x04size\x14RegisterDecompressor\x06method\x05dcomp\fdecompressor\aesc:0x1\x01f\x02os\x05Close\x02rc"))
- reinstall package
gcimporter_test.go:110: testing time used up
gcimporter_test.go:240: tested 0 imports
=== RUN TestImportedTypes
--- FAIL: TestImportedTypes (0.09s)
gcimporter_test.go:275: reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/math.a: cannot import, possibly version skew
(unknown export format version -1
Bug#920685: marked as done (ganeti-2.15: hardcoded MCL_* constants for mlockall are arch-dependent)
Your message dated Mon, 28 Jan 2019 15:08:56 + with message-id and subject line Bug#920685: fixed in ganeti 2.16.0-4 has caused the Debian Bug report #920685, regarding ganeti-2.15: hardcoded MCL_* constants for mlockall are arch-dependent 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.) -- 920685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ganeti-2.15 Version: 2.15.2-7+deb9u3 Severity: important User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team X-Debbugs-Cc: debian-ad...@lists.debian.org As seen in Linux sources: arch/alpha/include/uapi/asm/mman.h:#define MCL_CURRENT 8192 /* lock all currently mapped pages */ arch/mips/include/uapi/asm/mman.h:#define MCL_CURRENT 1 /* lock all current mappings */ arch/parisc/include/uapi/asm/mman.h:#define MCL_CURRENT 1 /* lock all current mappings */ arch/powerpc/include/uapi/asm/mman.h:#define MCL_CURRENT 0x2000 /* lock all currently mapped pages */ arch/sparc/include/uapi/asm/mman.h:#define MCL_CURRENT 0x2000 /* lock all currently mapped pages */ arch/xtensa/include/uapi/asm/mman.h:#define MCL_CURRENT 1 /* lock all current mappings */ include/uapi/asm-generic/mman.h:#define MCL_CURRENT 1 /* lock all current mappings */ ganeti hardcodes MCL_CURRENT = 1 and MCL_FUTURE = 2, so archs not using the generic value for MCL_CURRENT or MCL_FUTURE, such as powerpc, break with: ganeti-noded pid=81391 ERROR Cannot set memory lock: Invalid argument Cheers, Julien --- End Message --- --- Begin Message --- Source: ganeti Source-Version: 2.16.0-4 We believe that the bug you reported is fixed in the latest version of ganeti, 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. Apollon Oikonomopoulos (supplier of updated ganeti 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: Mon, 28 Jan 2019 11:37:36 +0200 Source: ganeti Binary: ganeti ganeti-2.16 ganeti-haskell-2.16 ganeti-htools ganeti-htools-2.16 ganeti-doc python-ganeti-rapi python3-ganeti-rapi ganeti-testsuite Architecture: source Version: 2.16.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Ganeti Team Changed-By: Apollon Oikonomopoulos Description: ganeti - cluster virtualization manager ganeti-2.16 - cluster virtualization manager - Python components ganeti-doc - cluster virtualization manager - documentation ganeti-haskell-2.16 - cluster virtualization manager - Haskell components ganeti-htools - cluster virtualization manager - tools (stand-alone) ganeti-htools-2.16 - cluster virtualization manager - tools for Ganeti 2.16 ganeti-testsuite - cluster virtualization manager - test suite python-ganeti-rapi - cluster virtualization manager - RAPI client library python3-ganeti-rapi - cluster virtualization manager - RAPI client library (Python 3) Closes: 918374 920685 920686 Changes: ganeti (2.16.0-4) unstable; urgency=medium . * Fix FTBFS with sphinx 1.8 (Closes: #918374) * Bump Standards-Version to 4.3.0; no changes needed * Detect arch-dependent libc/linux header values (Closes: #920685, #920686) * Fix process control with start-stop-daemon from dpkg 1.19.4 Checksums-Sha1: 1a2cec8f5fce3ad64cf3c1dad14b5a7a8fab 3483 ganeti_2.16.0-4.dsc fc8db26e40d7b94ca0f1e93947f5e71b17db276b 61240 ganeti_2.16.0-4.debian.tar.xz e20f2bb655d6734cc5952ec603a377ed63155491 14433 ganeti_2.16.0-4_source.buildinfo Checksums-Sha256: b72ec92b9f76a99cc291d2a9e5f9a66c7beeedaf9da5753a9a475c3fa8137a66 3483 ganeti_2.16.0-4.dsc c247d31dcba24186869fd656cef98f499c09da374bd5622e4fb04cfa50550665 61240 ganeti_2.16.0-4.debian.tar.xz 650aa55f2814a518f780ba0847b6ba933479a26b8573ea582bf4de8df4ec81cc 14433 ganeti_2.16.0-4_source.buildinfo Files: 19441869d78e1c2c846942a1069f0487 3483 admin optional ganeti_2.16.0-4.dsc a94276edcbd498288d3b11cfb0cdff4b 61240 admin optional ganeti_2.16.0-4.debian.tar.xz 9c9415224689d4dbe9e767c259788f2d 14433 admin
Bug#918374: marked as done (ganeti: FTBFS with Sphinx 1.8: cannot import name Directive)
Your message dated Mon, 28 Jan 2019 15:08:56 + with message-id and subject line Bug#918374: fixed in ganeti 2.16.0-4 has caused the Debian Bug report #918374, regarding ganeti: FTBFS with Sphinx 1.8: cannot import name Directive 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.) -- 918374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ganeti Version: 2.16.0-3 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.8 Dear Maintainer, ganeti fails to build with Sphinx 1.8, currently available in experimental: [...] /<>/./autotools/docpp < man/ganeti-cleaner.rst > man/ganeti-cleaner.gen ;\ ./autotools/check-man-references man/ganeti-cleaner.gen; \ trap - EXIT Traceback (most recent call last): File "/<>/./autotools/docpp", line 39, in from ganeti.build import sphinx_ext File "/tmp/gntbuild.KJeJdC3e/ganeti/build/sphinx_ext.py", line 50, in from sphinx.directives import Directive ImportError: cannot import name Directive The Directive class should be imported from docutils.parsers.rst module, not from sphinx.directives. -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ganeti Source-Version: 2.16.0-4 We believe that the bug you reported is fixed in the latest version of ganeti, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Apollon Oikonomopoulos (supplier of updated ganeti 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: Mon, 28 Jan 2019 11:37:36 +0200 Source: ganeti Binary: ganeti ganeti-2.16 ganeti-haskell-2.16 ganeti-htools ganeti-htools-2.16 ganeti-doc python-ganeti-rapi python3-ganeti-rapi ganeti-testsuite Architecture: source Version: 2.16.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Ganeti Team Changed-By: Apollon Oikonomopoulos Description: ganeti - cluster virtualization manager ganeti-2.16 - cluster virtualization manager - Python components ganeti-doc - cluster virtualization manager - documentation ganeti-haskell-2.16 - cluster virtualization manager - Haskell components ganeti-htools - cluster virtualization manager - tools (stand-alone) ganeti-htools-2.16 - cluster virtualization manager - tools for Ganeti 2.16 ganeti-testsuite - cluster virtualization manager - test suite python-ganeti-rapi - cluster virtualization manager - RAPI client library python3-ganeti-rapi - cluster virtualization manager - RAPI client library (Python 3) Closes: 918374 920685 920686 Changes: ganeti (2.16.0-4) unstable; urgency=medium . * Fix FTBFS with sphinx 1.8 (Closes: #918374) * Bump Standards-Version to 4.3.0; no changes needed * Detect arch-dependent libc/linux header values (Closes: #920685, #920686) * Fix process control with start-stop-daemon from dpkg 1.19.4 Checksums-Sha1: 1a2cec8f5fce3ad64cf3c1dad14b5a7a8fab 3483 ganeti_2.16.0-4.dsc fc8db26e40d7b94ca0f1e93947f5e71b17db276b 61240 ganeti_2.16.0-4.debian.tar.xz e20f2bb655d6734cc5952ec603a377ed63155491 14433 ganeti_2.16.0-4_source.buildinfo Checksums-Sha256: b72ec92b9f76a99cc291d2a9e5f9a66c7beeedaf9da5753a9a475c3fa8137a66 3483 ganeti_2.16.0-4.dsc c247d31dcba24186869fd656cef98f499c09da374bd5622e4fb04cfa50550665 61240 ganeti_2.16.0-4.debian.tar.xz 650aa55f2814a518f780ba0847b6ba933479a26b8573ea582bf4de8df4ec81cc 14433 ganeti_2.16.0-4_source.buildinfo Files: 19441869d78e1c2c846942a1069f0487 3483 admin optional ganeti_2.16.0-4.dsc a94276edcbd498288d3b11cfb0cdff4b 61240 admin optional ganeti_2.16.0-4.debian.tar.xz 9c9415224689d4dbe9e767c259788f2d 14433 admin optional ganeti_2.16.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAlxO9IITHGFwb2lrb3NA ZGViaWFuLm9yZwAKCRD1GxjHICSCJBwYD/47Ztb0pTw5MT6mIalSZPh+U4nq/+Rs BOxusaVsvwL2W2fnAywolm3k7abikBC4X42zfad6CNZABJ6/f6//TvuO6s/dZTo0 4X/XDM8sfdKE9K0rd5+Jfxt1jIbjfOvrEmNWmRmfhkC+J5T08ZcPemzhSlCeJ10B
Bug#920686: marked as done (ganeti-2.15: hardcoded ioctl constants are not arch-independent, breaking network on powerpc)
Your message dated Mon, 28 Jan 2019 15:08:56 +
with message-id
and subject line Bug#920686: fixed in ganeti 2.16.0-4
has caused the Debian Bug report #920686,
regarding ganeti-2.15: hardcoded ioctl constants are not arch-independent,
breaking network on powerpc
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.)
--
920686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganeti-2.15
Version: 2.15.2-7+deb9u3
Severity: important
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org
Hi,
take this small C program:
#include
#include
#include
int main() {
printf("0x%x\n", TUNGETFEATURES);
return 0;
}
On x86, it prints 0x800454cf.
On POWER, it prints 0x400454cf (because
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/include/uapi/asm/ioctl.h
overrides the generic values).
FWIW for the other ioctls:
TUNGETIFF = 0x400454d2
TUNSETIFF = 0x800454ca
Ganeti hardcodes the former value in
/usr/share/ganeti/2.15/ganeti/hypervisor/hv_kvm/netdev.py, and starting
a guest fails with:
2019-01-27 22:20:04,596: ganeti-noded pid=56691 WARNING ioctl(TUNGETFEATURES)
failed: [Errno 77] File descriptor in bad state
2019-01-27 22:20:04,596: ganeti-noded pid=56691 ERROR Hypervisor error: Failed
to allocate a new TAP device: [Errno 77] File descriptor in bad state
Traceback (most recent call last):
File "/usr/share/ganeti/2.15/ganeti/backend.py", line 2769, in StartInstance
hyper.StartInstance(instance, block_devices, startup_paused)
File "/usr/share/ganeti/2.15/ganeti/hypervisor/hv_kvm/__init__.py", line
1793, in StartInstance
self._ExecuteKVMRuntime(instance, kvm_runtime, kvmhelp)
File "/usr/share/ganeti/2.15/ganeti/hypervisor/hv_kvm/__init__.py", line
1607, in _ExecuteKVMRuntime
OpenTap(features=features, name=self._GenerateKvmTapName(nic))
File "/usr/share/ganeti/2.15/ganeti/hypervisor/hv_kvm/netdev.py", line 177,
in OpenTap
err)
HypervisorError: Failed to allocate a new TAP device: [Errno 77] File
descriptor in bad state
Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 2.16.0-4
We believe that the bug you reported is fixed in the latest version of
ganeti, 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.
Apollon Oikonomopoulos (supplier of updated ganeti 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: Mon, 28 Jan 2019 11:37:36 +0200
Source: ganeti
Binary: ganeti ganeti-2.16 ganeti-haskell-2.16 ganeti-htools ganeti-htools-2.16
ganeti-doc python-ganeti-rapi python3-ganeti-rapi ganeti-testsuite
Architecture: source
Version: 2.16.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team
Changed-By: Apollon Oikonomopoulos
Description:
ganeti - cluster virtualization manager
ganeti-2.16 - cluster virtualization manager - Python components
ganeti-doc - cluster virtualization manager - documentation
ganeti-haskell-2.16 - cluster virtualization manager - Haskell components
ganeti-htools - cluster virtualization manager - tools (stand-alone)
ganeti-htools-2.16 - cluster virtualization manager - tools for Ganeti 2.16
ganeti-testsuite - cluster virtualization manager - test suite
python-ganeti-rapi - cluster virtualization manager - RAPI client library
python3-ganeti-rapi - cluster virtualization manager - RAPI client library
(Python 3)
Closes: 918374 920685 920686
Changes:
ganeti (2.16.0-4) unstable; urgency=medium
.
* Fix FTBFS with sphinx 1.8 (Closes: #918374)
* Bump Standards-Version to 4.3.0; no changes needed
* Detect arch-dependent libc/linux header values (Closes: #920685, #920686)
* Fix process control with start-stop-daemon from dpkg 1.19.4
Checksums-Sha1:
1a2cec8f5fce3ad64cf3c1dad14b5a7a8fab 3483 ganeti_2.16.0-4.dsc
fc8db26e40d7b94ca0f1e93947f5e71b17db276b 61240 ganeti_2.16.0-4.debian.tar.xz
e20f2bb655d6734cc5952ec603a377ed63155491 14433
Bug#920359: marked as done (obitools: ships ecoPCR(1), ecofind(1) manpages already shipped in the ecopcr package)
Your message dated Mon, 28 Jan 2019 15:53:14 + with message-id and subject line Bug#920359: fixed in obitools 1.2.12+dfsg-2 has caused the Debian Bug report #920359, regarding obitools: ships ecoPCR(1), ecofind(1) manpages already shipped in the ecopcr package 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.) -- 920359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: obitools Version: 1.2.12+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package obitools. Preparing to unpack .../obitools_1.2.12+dfsg-1_amd64.deb ... Unpacking obitools (1.2.12+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/obitools_1.2.12+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/ecoPCR.1.gz', which is also in package ecopcr 1.0.0+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/obitools_1.2.12+dfsg-1_amd64.deb cheers, Andreas ecopcr=1.0.0+dfsg-1_obitools=1.2.12+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: obitools Source-Version: 1.2.12+dfsg-2 We believe that the bug you reported is fixed in the latest version of obitools, 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. Andreas Tille (supplier of updated obitools 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: Mon, 28 Jan 2019 16:24:48 +0100 Source: obitools Binary: obitools Architecture: source Version: 1.2.12+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: obitools - programs to analyze NGS data in a DNA metabarcoding context Closes: 920359 Changes: obitools (1.2.12+dfsg-2) unstable; urgency=medium . * Drop ecoPCR.1.gz and ecofind.1 from package Closes: #920359 * Section: science Checksums-Sha1: a21e19278d3442851ecfa0de2c6d03c9127c3703 2108 obitools_1.2.12+dfsg-2.dsc bbc83548688ddbbc2c5d8dcb5d7a9724fa68761e 18384 obitools_1.2.12+dfsg-2.debian.tar.xz Checksums-Sha256: 718484a09d1481fe0bdea4f4f1248f34c5334a8dafa6b1e704f433e145034d40 2108 obitools_1.2.12+dfsg-2.dsc 0cad16667f157eb54dcb9ec7ea6fd68f9ec869742430a8b61e9db519fe4bba0b 18384 obitools_1.2.12+dfsg-2.debian.tar.xz Files: b7af6177ad5dfdae440eb5b1a8782071 2108 science optional obitools_1.2.12+dfsg-2.dsc 3e5042a8a631352af78cbb64253c4909 18384 science optional obitools_1.2.12+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxPICwRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEy4w//XXr8XbftpjnD1bX3DojKbJDGOS7yBj7K hW8CVR/96iSgH9eEjfLwHNgLV/X9PvuW7zfXqN6APMi6lcY2FXv0mD9l94e6sHGX Eor5AZIA/9EscGQlrfbHtvkAvXJGd8C69lcqJpkiJ77WEj6fBANas1mUR11KXll3 RGuBu2t/bT2+Rc1b9Rx0HHvB6LWaJiQoYPt3brLndxYEtzsJQO/bZNFs4mi3sf9D N0PkqnOm41jGDaUo5cUh0tEWOzH8zvO0Cte8oY9iiW4juKuEarARX/La22PP8Ygo 09dydYxIGHyiHFniG7laTvRxS9PEDFsERkpei9ZFQdsQPG5H7jpdqfP/gLNlbUIL fbsYR5y8ilCwAG+CILkBaHhcAMwB8DWgHHttQ4Z4TzFMN+CYEoeViUsq8bUg+q77 4ZM0lG12TpmwqJvJ+ixM1fmmQUhqXpDbe1xSQGJ+Sc9earEcwllu+Yp5j9CaMvt0 yA6QJrB5ZE1wFcqGmMitTibF3o8HGUS4rd8nLssLPZ0lXX1w+uKNdwG6cHv9ngyx B7Am4r5DGJJCUzEVljZUOkfsnu5INEWZZFovwXwGIx0m/vyR90pjf+w9ZndfCtPF xQyQLrIkCH8rsgcG7pVfxeWPc0p3waTkgHiOfj01+mZMvWETqDuOcfMpBX6o6XVU HgwkgDxwDh4= =6WYw -END PGP SIGNATURE End Message ---
Bug#917962: marked as done (initscript lacks implementation of aa_log_action_start() and aa_log_action_end())
Your message dated Mon, 28 Jan 2019 18:49:26 + with message-id and subject line Bug#917962: fixed in apparmor 2.13.2-6 has caused the Debian Bug report #917962, regarding initscript lacks implementation of aa_log_action_start() and aa_log_action_end() 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.) -- 917962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apparmor Version: 2.13.2-2 Severity: normal Since 2.13.2-2 the initscript uses the upstream rc.apparmor.functions shell library, which expects its consumer to implement a bunch of logging functions. As reported initially on https://bugs.debian.org/917874#11, our initscript does not implement that interface. --- End Message --- --- Begin Message --- Source: apparmor Source-Version: 2.13.2-6 We believe that the bug you reported is fixed in the latest version of apparmor, 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. intrigeri (supplier of updated apparmor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 18:11:53 + Source: apparmor Architecture: source Version: 2.13.2-6 Distribution: unstable Urgency: medium Maintainer: Debian AppArmor Team Changed-By: intrigeri Closes: 917962 Changes: apparmor (2.13.2-6) unstable; urgency=medium . * initscript: implement missing aa_log_action_begin and aa_log_action_end functions (Closes: #917962). Checksums-Sha1: 793a509245b120b4e5044aa1398dea69ba0ef166 3363 apparmor_2.13.2-6.dsc 220d88d1ec75166c57f177af2d7b6d3e46c94156 96524 apparmor_2.13.2-6.debian.tar.xz 7263d2aa8752f549e67845648f6b304a60c0b1bb 12623 apparmor_2.13.2-6_amd64.buildinfo Checksums-Sha256: af775d4aa96d722df7a540e230c4ac0bd1e5c611ccf311430332815c962d626d 3363 apparmor_2.13.2-6.dsc 3c3c04b2a40c95ad366c5e3dc6051ba4d6330c283fb7b181e11439a143d0a5e4 96524 apparmor_2.13.2-6.debian.tar.xz a554c8712232da25ccf6a7f7957c6f5083b01d287e7601123ee1c3e6c897523e 12623 apparmor_2.13.2-6_amd64.buildinfo Files: 8ddca54c00322a78f39a7258d4ff0be9 3363 admin optional apparmor_2.13.2-6.dsc d84576361c2e6429b7d6a128f044b693 96524 admin optional apparmor_2.13.2-6.debian.tar.xz 92f5bd1d5027c403bd7453887bd52b68 12623 admin optional apparmor_2.13.2-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEcMAxqZeuB0p8dimNy2kI2AAOzf4FAlxPSk8ACgkQy2kI2AAO zf637Q/+JT12NqYG1VOpPcuUCQSYLfFtr1Yge9ouBo4NOVileJbTCh6p9pLSY7Gy gX3UPfOKH/uvBcnwGzXgtsQZODtSHjiV20cCCCtDCqKtbNsykdHs8yPnxwsJMm4X mUkqgIgOf5BP20eF+TP9R79e9T4a6iZ3wW25XICQGl5SULarZLHehh0rrGJ5rSyl dw7fgF68Ey6rU5rglc2/V/B2x8PVrDoQ5nfjuvjFh9hGeJjFPNo4hW4v/aUqENCR 8ZgM9Yf3tUkGnqNxyt10MnJ3x/yaSH7+8LRORgANypUYCjjrgf5xpwGT+CrXh3ad WmFHHpEIaC4I324aHSbJUq+m4GwKDsagWWNBF/ao8n8oV9XWu5D+8TjW/gKVsWij ttFPjm44EzhjAqJZcr4iQUfBqipGpZEUp6cmCIArP6mB6ZRdn+jkFcx4VoCFKer4 f9xxXfQgezg9ROkDaCgy8ZNiDtx9K6OTzarwrYnRs0+jDmXmVCAW1G+UXqT6hR59 X7Or09i1smy/dEZJu93shXzsz3co0Tm8cZL9wPYeql/hTEoOvaQ8BL4xR7nAQuIc yjmTey12Rz2hWlQSUbfCI4rzDYideeqBpdBhhcrTJtQ7BMfbBnnXdZl0dM7LmpFc 5g6yD2VVHs5y5Ez0Q9MUh88gqcVQ8UvsE1xZ1rKDlwUXFCIRZ6A= =SkEp -END PGP SIGNATURE End Message ---
Bug#920715: marked as done (RM: y-u-no-validate/2013052407-3)
Your message dated Mon, 28 Jan 2019 16:31:10 + with message-id <61268cf81718d7600210fd2eca465...@mail.adam-barratt.org.uk> and subject line Re: Bug#920715: RM: y-u-no-validate/2013052407-3 has caused the Debian Bug report #920715, regarding RM: y-u-no-validate/2013052407-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.) -- 920715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove y-u-no-validate from stretch, it's incompatible with Firefox >= 57. Cheers, Moritz --- End Message --- --- Begin Message --- On 2019-01-28 15:01, Moritz Muehlenhoff wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove y-u-no-validate from stretch, it's incompatible with Firefox >= 57. See #908405. Regards, Adam--- End Message ---
Bug#920716: marked as done (RM: mozvoikko/2.2-0.1)
Your message dated Mon, 28 Jan 2019 16:30:28 + with message-id and subject line Re: Bug#920716: RM: mozvoikko/2.2-0.1 has caused the Debian Bug report #920716, regarding RM: mozvoikko/2.2-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.) -- 920716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove mozvoikko from stable, it's broken with Firefox >= 57. Cheers, Moritz --- End Message --- --- Begin Message --- On 2019-01-28 15:02, Moritz Muehlenhoff wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove mozvoikko from stable, it's broken with Firefox >= 57. That's already #912465. Regards, Adam--- End Message ---
Processed: Re: Bug#911023: memory leak in the backlight control of the dell-laptop module
Processing control commands: > close -1 4.19.16-1 Bug #911023 [src:linux] memory leak in the backlight control of the dell-laptop module Marked as fixed in versions linux/4.19.16-1. Bug #911023 [src:linux] memory leak in the backlight control of the dell-laptop module Marked Bug as done -- 911023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918380: marked as done (FTBFS: test failures with new Web::API)
Your message dated Mon, 28 Jan 2019 17:21:25 +
with message-id
and subject line Bug#918380: fixed in libmail-chimp3-perl 0.06-1
has caused the Debian Bug report #918380,
regarding FTBFS: test failures with new Web::API
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.)
--
918380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmail-chimp3-perl
Version: 0.04-2
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
Forwarded: https://github.com/jdigory/p5-Mail-Chimp3/issues/4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As also seen on ci.debian.net and cpantesters, libmail-chimp3-perl's
tests fail with libweb-api-perl 2.3-1.
dh_auto_test
make -j4 test TEST_VERBOSE=1
make[1]: Entering directory '/build/libmail-chimp3-perl-0.04'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')"
t/*.t
# Failed test 'use Mail::Chimp3;'
# at t/01_load.t line 3.
# Tried to use 'Mail::Chimp3'.
# Error: You cannot overwrite a locally defined method (api_version) with
a reader at /build/libmail-chimp3-perl-0.04/blib/lib/Mail/Chimp3.pm line 664.
# Compilation failed in require at t/01_load.t line 3.
# BEGIN failed--compilation aborted at t/01_load.t line 3.
# Looks like you failed 1 test of 1.
t/01_load.t ..
not ok 1 - use Mail::Chimp3;
1..1
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
# Failed test 'use Mail::Chimp3;'
# at t/02_basic.t line 3.
# Tried to use 'Mail::Chimp3'.
# Error: You cannot overwrite a locally defined method (api_version) with
a reader at /build/libmail-chimp3-perl-0.04/blib/lib/Mail/Chimp3.pm line 664.
# Compilation failed in require at t/02_basic.t line 3.
# BEGIN failed--compilation aborted at t/02_basic.t line 3.
Attribute (base_url) is required
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
t/02_basic.t .
not ok 1 - use Mail::Chimp3;
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 1/1 subtests
t/03_live.t .. skipped: $ENV{MAILCHIMP_APIKEY} not set, skipping
live tests
t/author-critic.t skipped: these tests are for testing by the author
t/author-pod-coverage.t .. skipped: these tests are for testing by the author
t/author-pod-syntax.t skipped: these tests are for testing by the author
Test Summary Report
- ---
t/01_load.t(Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
t/02_basic.t (Wstat: 65280 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 255
Parse errors: No plan found in TAP output
Files=6, Tests=2, 1 wallclock secs ( 0.06 usr 0.01 sys + 0.60 cusr 0.07
csys = 0.74 CPU)
Result: FAIL
Failed 2/6 test programs. 2/2 subtests failed.
make[1]: *** [Makefile:849: test_dynamic] Error 255
make[1]: Leaving directory '/build/libmail-chimp3-perl-0.04'
dh_auto_test: make -j4 test TEST_VERBOSE=1 returned exit code 2
Cheers,
gregor
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlww49BfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgY0sQ/9HR0R/hOTQi4zqrQIAzJ7MvXTEcOhS7kiJwwxInzeDHpPHw+Grz/FkrFN
d0L9uOsQVJDv3R8gPuqW5EvSF5P4bqPEdwzMh+Q8aCa59Ms+COWHOK5RjKpiAe2B
5sMzKvtL2fJjEXMZ0dxJNCBdtXpoZeChKMGEeYg4ekiDh+WyCiRVsOJsGm6WMIER
9r3oXaA8jXMlj1EOt5F5nZr8mWEJNki+e9ktDbBNkjNK/X8yTEf3I4K/6jjO+PKc
K+UgNDTREGZNVR7l0WYdoCxBw4agKV6QeAfvwe3JcRFxar8t9jbPdAOROl2FtHFU
6jWTqt5SJ2X8y4qUDDTcGp+KT1ygltylZrmEqWgiq30UhihBIjJDOh59ZHV3uJZV
gZPw2Kq8B0pGrwx/g58pH3XcUGeL/2s+ZP07lFn32+5FRFqfP6tGRhWR2cUw2otN
PBPePHe3BaRna41RBhgfRb+xriPvcdSsePu952f0KyVUCKSHAyequBFXz6SW6Qhr
g5I1VlhEuL3fQmd5bfihzH6yIe7yJWne7TqNRDsK+KkHcA5XNvC3RTeUFy+YFYfZ
ufq/ddqoxJqqAk2C2jn7cv04XHXLxmGKu7Gv+eJjNXdiXExM8Fz0tUWR5l9g2o5O
z+otUD0G1ibsIfAAYrv5YHDiqYR2TsjaWZ+O3fFjFwrzI6G60uo=
=ypDi
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libmail-chimp3-perl
Source-Version: 0.06-1
We believe that the bug you reported is fixed in the latest version of
libmail-chimp3-perl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to
Bug#912220: marked as done (ifupdown: clarify netmask documentation)
Your message dated Mon, 28 Jan 2019 20:53:22 + with message-id and subject line Bug#912220: fixed in ifupdown 0.8.35 has caused the Debian Bug report #912220, regarding ifupdown: clarify netmask documentation 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.) -- 912220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifupdown Version: 0.8.34 Severity: wishlist The documentation note for inet netmask currently reads: Netmask (dotted quad or CIDR) I suggest changing that to be more like the inet6 netmask note, so: Netmask (dotted quad or number of bits, e.g., 24) Also it would be good to add to both inet and inet6 netmask a note that use of these keywords replaces the "/bits" notation in the address keyword. So the new inet netmask note would be something like: Netmask (dotted quad or number of bits, e.g., 24) used in lieu of "/netmask" in address Finally, it may be useful to note that the netmask keyword is a legacy/deprecated keyword that can be fully replaced with the current address syntax. Mike Stone --- End Message --- --- Begin Message --- Source: ifupdown Source-Version: 0.8.35 We believe that the bug you reported is fixed in the latest version of ifupdown, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guus Sliepen (supplier of updated ifupdown 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: Mon, 28 Jan 2019 21:37:33 +0100 Source: ifupdown Binary: ifupdown Architecture: source amd64 Version: 0.8.35 Distribution: unstable Urgency: medium Maintainer: Guus Sliepen Changed-By: Guus Sliepen Description: ifupdown - high level tools to configure network interfaces Closes: 900269 906894 912220 Changes: ifupdown (0.8.35) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/changelog: Remove trailing whitespaces . [ Guus Sliepen ] * Deprecate the netmask and broadcast options. Closes: #912220 * Bump Standards-Version and Build-Depends on debhelper-compat (= 12). * Make sure no systemd scripts are restarted on upgrades. Closes: #900269 * Use a DUID for DHCPv4 when using dhclient. Closes: #906894 Checksums-Sha1: e861464dddcf7488acb7c203612c8dac7f76887e 1533 ifupdown_0.8.35.dsc 7e45ef08b2a43b8615fb7520da9ef984c3601870 82368 ifupdown_0.8.35.tar.xz a33b10561b7430ecc9d7a482be209edb9c7e9448 70884 ifupdown-dbgsym_0.8.35_amd64.deb 64bc3c2e3d617b5aeaf110df9a4bfe89c9298f1e 6549 ifupdown_0.8.35_amd64.buildinfo bba027c7f35745d0606407dc61e3444d46381438 81524 ifupdown_0.8.35_amd64.deb Checksums-Sha256: 2daf19483ac8ce8eda7d7fd4b3d926f132f64f4a2735facf4ca066421d8b4e83 1533 ifupdown_0.8.35.dsc d754426562a63b7d0cf06e8b00abe353fe9fd7ac5aabe3745f6d4e294ca233a8 82368 ifupdown_0.8.35.tar.xz 95589a56f444306dc4416fb11f487ba7d49425951f10cb25c8b84fe4dad5c538 70884 ifupdown-dbgsym_0.8.35_amd64.deb 3ca677349652e32ca7bcb8a3edfc7553c95edaa8b90b48fefddc6d3d412c2758 6549 ifupdown_0.8.35_amd64.buildinfo f51217a82c022cff99390804dba6698e66923205195744cf6c83023175498e71 81524 ifupdown_0.8.35_amd64.deb Files: 153ab8500a7445774c2b53eb56f07875 1533 admin important ifupdown_0.8.35.dsc 3945c428c88bbf058c3d7a3ae684cf4d 82368 admin important ifupdown_0.8.35.tar.xz cbf93b93899ff8883812062b9f4f9f58 70884 debug optional ifupdown-dbgsym_0.8.35_amd64.deb 4105302195a365f1226d50d0d606cbe9 6549 admin important ifupdown_0.8.35_amd64.buildinfo b4f342b3b3fc65bd890003a054cfe11d 81524 admin important ifupdown_0.8.35_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEETRt3lsA+CDGZG91CP0kN64ce+foFAlxPaDoACgkQP0kN64ce +fqcGw//e8VBu9MllkLDgLFwFxiFeLF32s67ErGXse/yL5moweQWVVE0SEHXySAl +WI+SXoioLQSOrwRDiXYDuhononwG/JKLvi86ioE2cUpXU9DxlsCvGbe5EXmCM4T JmKdnsF0RTqYeitiJfe4A/zeoTNJWD1Jl20rPPpvqqotKfVAKt5zWVX5lNSFoSrO iRjb4BrbRQ7ilvdigUnGAK1Ww1lDh+w5w5kAdqqEA0YGUQRuFUkknyGgOYXp8Zcm b8implBqafy1YOGCyEnoH+Y07zsARBO+eiLhyt1e5gY8Lw5Xp1sIZSMa91z2t16d HmVxvBp6262jUg9570Qh17T5p40lYu6/NREujuOxDv0RrluSC1AkNziOBYXBszIH
Bug#906894: marked as done (dhclient should send client id)
Your message dated Mon, 28 Jan 2019 20:53:22 + with message-id and subject line Bug#906894: fixed in ifupdown 0.8.35 has caused the Debian Bug report #906894, regarding dhclient should send client id 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.) -- 906894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifupdown Version: 0.8.34 dhclient supports DHCPv4 and DHCPv6. In DHCPv4, usually the host's EUI-64 (MAC address) is used to identify it. Because this causes some problems [1], DHCPv6 introduced the `DHCP Unique Identifier` (DUID) [2], instead of relying on the EUI-64. If we want to operate a dual-stack network with DHCPv6 managed IP addresses, we now face a new problem altogether: - V4 hosts are identified by EUI-64 - V6 hosts are identified by DUID - How to correlate them? "Easy! Use the EUI-64 anyway" one might think. But when the DHCP server is not connected directly to the same link as the host and receives the request through a relay agent, then he will have no information of the hosts EUI-64 and it becomes almost impossible to correlate the requests, because in DHCPv6, the relay agent does not preserve the EUI-64 in it's RELAY-FORWARD message [3] (in contrast to the DHCPv4 relay agent). Fortunately, there is RFC 4361. It suggests that clients, which operate in a dual-stack environment, must send DUID (and IAID for that matter) to the server when requesting an IP via DHCPv4 [4] [5]. (There is also another RFC tackling this problem by suggesting that the DHCPv6 relay agent may optionally preserve the EUI-64 as an option [6] in the RELAY-FORWARD message.) Since dhclient-4.3.1-6+deb8u3 [7], dhclient knows the `-i` option. If the option is set, dhcpclient sends the DUID/IAID in requests to DHCPv4 servers according to RFC 4361. But ifupdown currently does not invoke dhclient with the `-i` option by default. Which presents the before-mentioned challenge for DHCP servers. Therefore I suggest the following changes to `inet.defn`: - In every "up" section, where `dhclient -4 -v ...` is invoked, invoke it with `dhclient -4 -v -i ...` instead. - In every "down" section, where `dhclient -4 -v ...` is invoked, invoke it with `dhclient -4 -v -i ...` instead. ~Chris PS: These changes should also be ported to ifupdown2. --- [1] https://tools.ietf.org/html/rfc4361#section-4 [2] https://tools.ietf.org/html/rfc3315#section-9 [3] https://tools.ietf.org/html/rfc3315#section-7 [4] https://tools.ietf.org/html/rfc4361#section-5 [5] https://tools.ietf.org/html/rfc4361#section-6.1 [6] https://tools.ietf.org/html/rfc6939 [7] https://sources.debian.org/src/isc-dhcp/4.3.1-6+deb8u3/ --- End Message --- --- Begin Message --- Source: ifupdown Source-Version: 0.8.35 We believe that the bug you reported is fixed in the latest version of ifupdown, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guus Sliepen (supplier of updated ifupdown 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: Mon, 28 Jan 2019 21:37:33 +0100 Source: ifupdown Binary: ifupdown Architecture: source amd64 Version: 0.8.35 Distribution: unstable Urgency: medium Maintainer: Guus Sliepen Changed-By: Guus Sliepen Description: ifupdown - high level tools to configure network interfaces Closes: 900269 906894 912220 Changes: ifupdown (0.8.35) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/changelog: Remove trailing whitespaces . [ Guus Sliepen ] * Deprecate the netmask and broadcast options. Closes: #912220 * Bump Standards-Version and Build-Depends on debhelper-compat (= 12). * Make sure no systemd scripts are restarted on upgrades. Closes: #900269 * Use a DUID for DHCPv4 when using dhclient. Closes: #906894 Checksums-Sha1: e861464dddcf7488acb7c203612c8dac7f76887e 1533 ifupdown_0.8.35.dsc 7e45ef08b2a43b8615fb7520da9ef984c3601870 82368 ifupdown_0.8.35.tar.xz a33b10561b7430ecc9d7a482be209edb9c7e9448 70884
Bug#900269: marked as done (ifupdown: last version breaks upgrade)
Your message dated Mon, 28 Jan 2019 20:53:22 + with message-id and subject line Bug#900269: fixed in ifupdown 0.8.35 has caused the Debian Bug report #900269, regarding ifupdown: last version breaks 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.) -- 900269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifupdown Version: 0.8.34 Severity: critical Justification: breaks the whole system Dear Maintainer, I now have been experiency three freeze during apt upgrade on three machines with the lattest update. When upgrading, you're stuck with the last message in console "setting up ifupdown" and nothing else. The machine dropped its ip address but seems to fails to acquire a new one. and stay like this for minutes. running ifup (if you still logged on another console) barks because of lock in /run. The problem is that headless machine with servers are then unmanageable without physical access. -- Package-specific info: --- /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface #auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp hostname r-x-ceva6380 iface wlan0 inet dhcp pre-up /etc/network/WirelessLanStartLiveBox.sh wlan0 hostname r-x-ceva6380 post-down /etc/network/WirelessLanStopLiveBox.sh wlan0 --- up and down scripts installed: /etc/network/if-down.d: total 8 -rwxr-xr-x 1 root root 372 Mar 17 2014 openvpn -rwxr-xr-x 1 root root 111 Feb 8 2010 umountnfs lrwxrwxrwx 1 root root 32 May 7 19:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-post-down.d: total 4 lrwxrwxrwx 1 root root 23 Apr 27 12:59 avahi-daemon -> ../if-up.d/avahi-daemon lrwxrwxrwx 1 root root 29 Apr 8 23:06 bridge -> /lib/bridge-utils/ifupdown.sh -rwxr-xr-x 1 root root 1409 Mar 24 2016 wireless-tools lrwxrwxrwx 1 root root 32 May 7 19:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-pre-up.d: total 12 lrwxrwxrwx 1 root root 29 Apr 8 23:06 bridge -> /lib/bridge-utils/ifupdown.sh -rwxr-xr-x 1 root root 344 Jun 7 2010 ethtool -rwxr-xr-x 1 root root 4178 Mar 24 2016 wireless-tools lrwxrwxrwx 1 root root 32 May 7 19:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-up.d: total 32 -rwxr-xr-x 1 root root 484 Mar 6 2013 avahi-daemon -rwxr-xr-x 1 root root 1685 Sep 22 2014 ethtool -rwxr-xr-x 1 root root 4958 Jun 8 2014 mountnfs -rwxr-xr-x 1 root root 109 Feb 8 2010 mountnfs.dpkg-old -rwxr-xr-x 1 root root 900 Apr 28 2016 ntpdate -rwxr-xr-x 1 root root 972 Mar 30 2017 openssh-server -rwxr-xr-x 1 root root 385 Jul 7 2015 openvpn lrwxrwxrwx 1 root root 32 May 7 19:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.43 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8), LANGUAGE= (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.117 ii iproute2 4.16.0-4 ii libc6 2.27-3 ii lsb-base 9.20170808 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.5-4 Versions of packages ifupdown suggests: ii ppp 2.4.7-2+2 pn rdnssd -- no debconf information --- End Message --- --- Begin Message --- Source: ifupdown Source-Version: 0.8.35 We believe that the bug you reported is fixed in the latest version of ifupdown, 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. Guus Sliepen (supplier of updated ifupdown 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: Mon, 28 Jan 2019
Bug#889525: marked as done (pytsk: Please make build compatible with -Wl,--as-needed)
Your message dated Mon, 28 Jan 2019 18:54:23 +
with message-id
and subject line Bug#889525: fixed in pytsk 20190121-2
has caused the Debian Bug report #889525,
regarding pytsk: Please make build compatible with -Wl,--as-needed
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.)
--
889525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pytsk
Version: 20171108-1
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch
Dear Hilko,
The latest version of pytsk has failed to build in Ubuntu, because the
changes to make pytsk statically link libtsk cause flags to be passed in a
way that's incompatible with -Wl,--as-needed, which is a default linker flag
in Ubuntu.
The attached debdiff updates your patch to setup.py so that dependent
libraries are listed last on the linker line, fixing the build failure in
Ubuntu. Please consider applying it in Debian.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru
pytsk-20171108/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
pytsk-20171108/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
---
pytsk-20171108/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
2017-11-09 13:30:00.0 -0800
+++
pytsk-20171108/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
2018-02-04 00:00:28.0 -0800
@@ -7,11 +7,11 @@
setup.py | 44
1 file changed, 12 insertions(+), 32 deletions(-)
-diff --git a/setup.py b/setup.py
-index b803021..e8db4c3 100755
a/setup.py
-+++ b/setup.py
-@@ -178,9 +178,9 @@ class BuildExtCommand(build_ext):
+Index: pytsk-20171108/setup.py
+===
+--- pytsk-20171108.orig/setup.py
pytsk-20171108/setup.py
+@@ -178,9 +178,9 @@
def run(self):
compiler = new_compiler(compiler=self.compiler)
# pylint: disable=attribute-defined-outside-init
@@ -23,7 +23,7 @@
if not os.access("pytsk3.c", os.R_OK):
# Generate the Python binding code (pytsk3.c).
-@@ -202,7 +202,7 @@ class BuildExtCommand(build_ext):
+@@ -202,7 +202,7 @@
class SDistCommand(sdist):
"""Custom handler for generating source dist."""
def run(self):
@@ -32,7 +32,7 @@
# sleuthkit submodule is not there, probably because this has been
# freshly checked out.
-@@ -280,32 +280,10 @@ class UpdateCommand(Command):
+@@ -280,32 +280,10 @@
subprocess.check_call(["git", "apply", patch_file], cwd="sleuthkit")
def run(self):
@@ -66,7 +66,7 @@
# Generate the Python binding code (pytsk3.c).
libtsk_header_files = [
-@@ -340,16 +318,18 @@ class ProjectBuilder(object):
+@@ -340,16 +318,19 @@
# The args for the extension builder.
self.extension_args = {
"define_macros": [],
@@ -76,10 +76,11 @@
-"libraries": []}
+"libraries": [
+ "talloc",
-+ # required by statically linked libtsk
-+ "afflib", "ewf", "stdc++", "z",
+],
-+"extra_link_args": ["-Wl,-Bstatic", "-ltsk", "-Wl,-Bdynamic"]}
++"extra_link_args": [
++ "-Wl,-Bstatic", "-ltsk", "-Wl,-Bdynamic",
++ "-lafflib", "-lewf", "-lstdc++", "-lz",
++]}
# The sources to build.
self._source_files = [
--- End Message ---
--- Begin Message ---
Source: pytsk
Source-Version: 20190121-2
We believe that the bug you reported is fixed in the latest version of
pytsk, 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 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hilko Bengen (supplier of updated pytsk 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:
Bug#918434: marked as done (golint: FTBFS (failing tests))
Your message dated Mon, 28 Jan 2019 20:53:10 + with message-id and subject line Bug#918434: fixed in golint 0.0+git20181214.8f45f77-1 has caused the Debian Bug report #918434, regarding golint: 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.) -- 918434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golint Version: 0.0+git20161013.3390df4-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --buildsystem=golang --with=golang dh_update_autotools_config -a -O--buildsystem=golang dh_auto_configure -a -O--buildsystem=golang dh_auto_build -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/<>/golint-0.0\+git20161013.3390df4/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/<>/golint-0.0\+git20161013.3390df4/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/golang/lint github.com/golang/lint/golint errors internal/cpu internal/bytealg internal/race runtime/internal/atomic runtime/internal/sys runtime sync/atomic [... snipped ...] go/parser text/tabwriter go/printer container/heap encoding/binary math/rand math/big go/constant go/types bufio path regexp/syntax regexp net/url text/template/parse text/template go/doc log context os/exec go/build text/scanner golang.org/x/tools/go/gcimporter15 github.com/golang/lint flag github.com/golang/lint/golint dh_auto_test -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/golang/lint github.com/golang/lint/golint === RUN TestAll --- FAIL: TestAll (0.04s) lint_test.go:94: Lint failed at errorf.go:29; /should replace.*t\.Error\(fmt\.Sprintf\(\.\.\.\)\).*t\.Errorf\(\.\.\.\)/ did not match lint_test.go:94: Lint failed at time.go:11; /Msec.*\*time.Duration/ did not match lint_test.go:94: Lint failed at time.go:13; /Secs.*time.Duration/ did not match lint_test.go:94: Lint failed at var-decl.go:18; /should.*\*http\.ServeMux.*inferred/ did not match lint_test.go:94: Lint failed at var-decl.go:74; /should omit.*io\.Writer/ did not match === RUN TestLine --- PASS: TestLine (0.00s) === RUN TestLintName --- PASS: TestLintName (0.00s) === RUN TestExportedType --- PASS: TestExportedType (0.00s) FAIL FAILgithub.com/golang/lint 0.043s ? github.com/golang/lint/golint [no test files] dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/golang/lint github.com/golang/lint/golint returned exit code 1 make: *** [debian/rules:4: build-arch] Error 1 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golint.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: golint Source-Version: 0.0+git20181214.8f45f77-1 We believe that the bug you reported is fixed in the latest version of golint, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated golint 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: Mon, 28 Jan 2019 20:30:26 + Source: golint Architecture: source Version: 0.0+git20181214.8f45f77-1 Distribution: unstable Urgency: high Maintainer: Debian Go Packaging Team Changed-By: Martín Ferrari Closes: 918434 Changes: golint (0.0+git20181214.8f45f77-1) unstable; urgency=high . [ Alexandre Viau ] * Point Vcs-* urls to salsa.debian.org. . [ Martín Ferrari ]
Bug#920733: marked as done (freedink: missing Breaks+Replaces: freedink-engine (<< 109.4))
Your message dated Mon, 28 Jan 2019 21:35:29 + with message-id and subject line Bug#920733: fixed in freedink 109.4-2 has caused the Debian Bug report #920733, regarding freedink: missing Breaks+Replaces: freedink-engine (<< 109.4) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freedink Version: 109.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../freedink_109.4-1_all.deb ... Unpacking freedink (109.4-1) ... dpkg: error processing archive /var/cache/apt/archives/freedink_109.4-1_all.deb (--unpack): trying to overwrite '/usr/share/metainfo/freedink.appdata.xml', which is also in package freedink-engine 109.2-1 Errors were encountered while processing: /var/cache/apt/archives/freedink_109.4-1_all.deb cheers, Andreas freedink-engine=109.2-1_freedink=109.4-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: freedink Source-Version: 109.4-2 We believe that the bug you reported is fixed in the latest version of freedink, 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. Sylvain Beucler (supplier of updated freedink package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 21:54:00 +0100 Source: freedink Binary: freedink freedink-engine freedink-engine-dbgsym Architecture: source amd64 all Version: 109.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Sylvain Beucler Description: freedink - humorous top-down adventure and role-playing game freedink-engine - humorous top-down adventure and role-playing game (engine) Closes: 920733 Changes: freedink (109.4-2) unstable; urgency=medium . * Use Breaks to move Appstream file from freedink-engine to freedink (Closes: #920733) Checksums-Sha1: 643cf6e7e27231e146a97faf7d852955d877adbb 2006 freedink_109.4-2.dsc eec65364c05f5a33da3f5dae6a26929c1be8b240 42992 freedink_109.4-2.debian.tar.xz 3feba27982080a5fcfca1725c2cf6c571f369260 1987152 freedink-engine-dbgsym_109.4-2_amd64.deb bbf5549123ea2078823abbb6d5145249c9c53eeb 272360 freedink-engine_109.4-2_amd64.deb ad8449a31d731a9ff653818e54a5ebcbcd5c38fa 58872 freedink_109.4-2_all.deb aca4aca3679222c6745b85816240d31e75e16217 11819 freedink_109.4-2_amd64.buildinfo Checksums-Sha256: 544641a0bf764cd7c5c2adee72aa88b5c1f3b44fdf146d22f70e7905727e42c7 2006 freedink_109.4-2.dsc cff7367677bf209bedc0973b8a2b35a1a5128d52f1f42b0e8658102b53ff5109 42992 freedink_109.4-2.debian.tar.xz 4025d0d27155b672e56d3779c05831e7dd8e9dc09968b1d96670c6d3dae0c8a1 1987152
Bug#919809: marked as done (freedom-maker: please don't depend on pxz which shall be removed for buster)
Your message dated Mon, 28 Jan 2019 21:35:35 + with message-id and subject line Bug#919809: fixed in freedom-maker 0.23 has caused the Debian Bug report #919809, regarding freedom-maker: please don't depend on pxz which shall be removed for buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freedom-maker Version: 0.22 Severity: important block 919616 by -1 Dear maintainer, freedom-maker currently depends on pxz, however even xz in Stretch now supports parallel compression with the -T switch. Therefore I would like to remove pxz from Buster, which is only possible if freedom-maker (and forensics-extra) drop the depends on pxz. See #919616. Thanks for maintaining freedom-maker! -- tschüß, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: freedom-maker Source-Version: 0.23 We believe that the bug you reported is fixed in the latest version of freedom-maker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Valleroy (supplier of updated freedom-maker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 16:13:29 -0500 Source: freedom-maker Architecture: source Version: 0.23 Distribution: unstable Urgency: medium Maintainer: FreedomBox Packaging Team Changed-By: James Valleroy Closes: 919809 Changes: freedom-maker (0.23) unstable; urgency=medium . [ Juan Carlos Romero ] * vagrant-package: Fix typo in error message . [ Sunil Mohan Adapa ] * passwd-in-image: Fix typo in error message . [ Joseph Nuthalapati ] * library: Remove dependency - pxz (Closes: #919809) Checksums-Sha1: d46f914d9354d5aa15ef72112c035568e73ab861 1960 freedom-maker_0.23.dsc e02bf5045b8809b7c2978284728e590417cc4c02 39264 freedom-maker_0.23.tar.xz 24d324a0e38cae4e0851a5b47332c28f8954431b 5936 freedom-maker_0.23_amd64.buildinfo Checksums-Sha256: 662e68b25715c7085937517d0005d0c651c4d6b5ea566db721f9f2ea87e8e1f1 1960 freedom-maker_0.23.dsc 71549368bde1a8ab43c3dcd32f9e1ad9f46935db485b1e49b4b3b29247e52eab 39264 freedom-maker_0.23.tar.xz c588f133837a63262ed51d71126b7d35e99cf982d4ae7c37906d9bb0f6d175eb 5936 freedom-maker_0.23_amd64.buildinfo Files: db4d551cad01803c63e4ec2a9fb64c45 1960 utils optional freedom-maker_0.23.dsc 90ee8e6374f97ba0c91d842c9bc358f6 39264 utils optional freedom-maker_0.23.tar.xz fdd72e8e93f4e50c55899f6e9d878400 5936 utils optional freedom-maker_0.23_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAlxPcrcWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICMkiEAC9Qm3jMOb8CWLuCR35Ajjkr5vx IrKRjThdQrC0TlLlbe4MLqe0LBodxrfsTeyBhKB/DUPRT6n1GalWMclirDSo4X4J +2+wU/iDp1zW1U5suOgmTluIvtfRTmsOze0zlZAfPXC7eQYd+8vf4dkk6Ygoz/pT FtfO3bDwqWlC/DsHD12REULH0RSKcNBNrkV9l6ueKQUkxyIC2Vt2vowjttVvOEvx w+/696tf0vdWq13LsWCMM5CnGJbWjYuuJYB20MaXZKLuvIbes+cQz5pazquJ55Qa deyvHh4QAg4X3XNX1sRSVwnNA1JQlkhVCG1vVjLX4+D714meCnzKbMgVmnYR16f7 fvskUUU3zuryq2SXppgqdIbqzbeIhI1soZlbPGvddRU3fK4qNEcUmnMp06fyelFT RFb1binxutOiy5uA9ueYBewAHYPNqx+T06cQ78T94UrFAGl/uGh3sATsNsyTU6cD jHbEkV1u6TXrkmcyQzcTAWXrLRpxqbWHBLVqMgX8CRai83z9Yyarbd5bCOjfyHxW FVu2Ta5+/Dz6KU6uXhUr6qxTzD+gYC8R3OEnnn1A/tbNyN+oG7gXsXfPlXYgbb9b ay2j7rHtJ4bBVscshDVPqEIBk51/oA/Nml8KhpAXmpf5kXnaVdkdk4+3RDL3PBxd TZ+4gI4uve9iewasDg== =0+Yx -END PGP SIGNATURE End Message ---
Bug#886393: marked as done (doesn't clean up inherited children)
Your message dated Mon, 28 Jan 2019 21:35:02 + with message-id and subject line Bug#886393: fixed in awesome 4.3-1 has caused the Debian Bug report #886393, regarding doesn't clean up inherited children 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.) -- 886393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: awesome Version: 4.2-4 Severity: normal Hi, Part of my ~.xsession looks like this: traystuff & confsynaptics setxkbmap -option compose:menu be light-locker & /usr/share/xscreensaver/xscreensaver-wrapper.sh -nosplash & exec awesome The last line means awesome now inherits the processes that were started in the background. Unfortunately, the result is that awesome does not appear to reap the zombies: wouter2375 0.2 0.4 550072 72876 ?Ssl 11:04 0:05 \_ awesome wouter2465 0.0 0.0 11096 2212 ?Ss 11:04 0:00 \_ /usr/bin/ssh-agent /usr/bin/im-launch /bin/bash /home/wouter/.xsession wouter 10348 0.0 0.0 28936 4880 ?S11:34 0:00 | \_ /usr/lib/openssh/ssh-pkcs11-helper wouter2555 0.0 0.0 0 0 ?Z11:04 0:00 \_ [traystuff] wouter2568 0.0 0.0 0 0 ?Z11:04 0:00 \_ [bash] wouter2569 0.0 0.0 0 0 ?Z11:04 0:00 \_ [xscreensaver] This does not appear to be proper. If you need further information, do ask. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, m68k, arm64 Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages awesome depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.2-1 ii dbus-x11 [dbus-session-bus] 1.12.2-1 ii gir1.2-freedesktop1.54.1-4 ii gir1.2-pango-1.0 1.40.14-1 ii libc6 2.26-1 ii libcairo-gobject2 1.15.8-3 ii libcairo2 1.15.8-3 ii libdbus-1-3 1.12.2-1 ii libgdk-pixbuf2.0-02.36.11-1 ii libglib2.0-0 2.54.2-5 ii liblua5.3-0 5.3.3-1 ii libstartup-notification0 0.12-5 ii libx11-6 2:1.6.4-3 ii libxcb-cursor00.1.1-4 ii libxcb-icccm4 0.4.1-1+b1 ii libxcb-keysyms1 0.4.0-1+b2 ii libxcb-randr0 1.12-1 ii libxcb-render01.12-1 ii libxcb-shape0 1.12-1 ii libxcb-util0 0.3.8-3+b2 ii libxcb-xinerama0 1.12-1 ii libxcb-xkb1 1.12-1 ii libxcb-xrm0 1.0-3 ii libxcb-xtest0 1.12-1 ii libxcb1 1.12-1 ii libxdg-basedir1 1.2.0-1 ii libxkbcommon-x11-00.7.1-2 ii libxkbcommon0 0.7.1-2 ii lua-lgi 0.9.2-1 it menu 2.1.47+b1 Versions of packages awesome recommends: ii awesome-extra 2017110501 ii feh2.22.2-1 ii rlwrap 0.42-3 ii x11-xserver-utils 7.7+7+b1 Versions of packages awesome suggests: pn awesome-doc -- no debconf information --- End Message --- --- Begin Message --- Source: awesome Source-Version: 4.3-1 We believe that the bug you reported is fixed in the latest version of awesome, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if
Bug#919232: marked as done (wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf)
Your message dated Mon, 28 Jan 2019 22:07:09 + with message-id and subject line Bug#919232: fixed in wireguard 0.0.20190123-1 has caused the Debian Bug report #919232, regarding wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf 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.) -- 919232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wireguard-dkms Version: 0.0.20181218-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, i686 Kernel: Linux 5.0.0-rc1+ (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireguard-dkms depends on: ii dkms 2.6.1-3 Versions of packages wireguard-dkms recommends: ii wireguard-tools 0.0.20181218-1 wireguard-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: wireguard Source-Version: 0.0.20190123-1 We believe that the bug you reported is fixed in the latest version of wireguard, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated wireguard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 14:31:53 -0500 Source: wireguard Binary: wireguard wireguard-dkms wireguard-tools Architecture: source Version: 0.0.20190123-1 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor Changed-By: Daniel Kahn Gillmor Description: wireguard - fast, modern, secure kernel VPN tunnel (metapackage) wireguard-dkms - fast, modern, secure kernel VPN tunnel (DKMS version) wireguard-tools - fast, modern, secure kernel VPN tunnel (userland utilities) Closes: 913446 919232 Changes: wireguard (0.0.20190123-1) unstable; urgency=medium . [ Fabian Grünbichler ] * wireguard.postinst: Add module reload on upgrade (Closes: #913446) . [ Daniel Kahn Gillmor ] * New upstream version (Closes: #919232) * Tighten dependencies and description of wireguard metapackage * Fine-tune module reload code on wireguard.postinst * Standards-Version: bump to 4.3.0 (no changes needed) * Update debian/copyright * override lintian warning version-substvar-for-external-package * move to debhelper-compat 12 Checksums-Sha1: 48db0a8719785d4b1c8d1eb5e8e1a85a6a3f0a11 1513 wireguard_0.0.20190123-1.dsc 8505de862160239786ae9d5891b2bb8fe7f3d2ac 323640 wireguard_0.0.20190123.orig.tar.xz 2df171fc84e402198cc57bfb1ab31fa8a964653a 24164 wireguard_0.0.20190123-1.debian.tar.xz 3579f8acf5932825bcbaf6ef5f7214fbfbf8fbd0 7145 wireguard_0.0.20190123-1_amd64.buildinfo Checksums-Sha256: 9d79598ac270d962802f53fc1b73a2476da9f32bdba4543eac0501e45946c833 1513 wireguard_0.0.20190123-1.dsc 7225ee835298e0c8fb9f211a4aaedaa259c5200441da25d497a60d09a03913c7 323640 wireguard_0.0.20190123.orig.tar.xz 7ade718e1c77daee71bfd8ceab9bbd9f6bed9a248bd8da7ecb1df3bf0cf48b9d 24164 wireguard_0.0.20190123-1.debian.tar.xz 8cc2f129b2905f41316b1989a91c7cf44c31444d056069b8f8df78e06d110a3b 7145 wireguard_0.0.20190123-1_amd64.buildinfo Files: 664670207418a0e2a207623fcab8d4b3 1513 net optional wireguard_0.0.20190123-1.dsc 4f001a203713e4e53ea022325bd6d317 323640 net optional wireguard_0.0.20190123.orig.tar.xz e7c4b700ebd8d937ecaa542270523e8b 24164 net optional wireguard_0.0.20190123-1.debian.tar.xz bc155cb1860aba76696e0f3f9192db29 7145 net optional wireguard_0.0.20190123-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTJDm02IAobkioVCed2GBllKa5f+AUCXE9szQAKCRB2GBllKa5f +AnZAQDcqGTGMhuJ80wLdHZToZTCRQEk/gbA5r6DuBdUYaDJDQD8Cd9V2+ehgcC8 IPCUBifUJouWEp8DOkd0Yk3FixDbcw0= =XC5e -END PGP
Bug#913446: marked as done (wireguard-tools: optionally reload module / interfaces on upgrade)
Your message dated Mon, 28 Jan 2019 22:07:09 + with message-id and subject line Bug#913446: fixed in wireguard 0.0.20190123-1 has caused the Debian Bug report #913446, regarding wireguard-tools: optionally reload module / interfaces on 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.) -- 913446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wireguard-tools Version: 0.0.20181018-1 Severity: wishlist Tags: patch as discussed on the WG mailing list[0], this would be nice to have - similar to what the Ubuntu PPA offers, but with debconf integration and a bit less noise on stdout. MR with a WIP implementation incoming on salsa. 0: https://lists.zx2c4.com/pipermail/wireguard/2018-November/003533.html -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages wireguard-tools depends on: ii debconf [debconf-2.0] 1.5.69 ii libc6 2.27-8 ii libmnl01.0.4-2 Versions of packages wireguard-tools recommends: ii wireguard-dkms 0.0.20181018-1 wireguard-tools suggests no packages. -- debconf information excluded --- End Message --- --- Begin Message --- Source: wireguard Source-Version: 0.0.20190123-1 We believe that the bug you reported is fixed in the latest version of wireguard, 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 wireguard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 14:31:53 -0500 Source: wireguard Binary: wireguard wireguard-dkms wireguard-tools Architecture: source Version: 0.0.20190123-1 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor Changed-By: Daniel Kahn Gillmor Description: wireguard - fast, modern, secure kernel VPN tunnel (metapackage) wireguard-dkms - fast, modern, secure kernel VPN tunnel (DKMS version) wireguard-tools - fast, modern, secure kernel VPN tunnel (userland utilities) Closes: 913446 919232 Changes: wireguard (0.0.20190123-1) unstable; urgency=medium . [ Fabian Grünbichler ] * wireguard.postinst: Add module reload on upgrade (Closes: #913446) . [ Daniel Kahn Gillmor ] * New upstream version (Closes: #919232) * Tighten dependencies and description of wireguard metapackage * Fine-tune module reload code on wireguard.postinst * Standards-Version: bump to 4.3.0 (no changes needed) * Update debian/copyright * override lintian warning version-substvar-for-external-package * move to debhelper-compat 12 Checksums-Sha1: 48db0a8719785d4b1c8d1eb5e8e1a85a6a3f0a11 1513 wireguard_0.0.20190123-1.dsc 8505de862160239786ae9d5891b2bb8fe7f3d2ac 323640 wireguard_0.0.20190123.orig.tar.xz 2df171fc84e402198cc57bfb1ab31fa8a964653a 24164 wireguard_0.0.20190123-1.debian.tar.xz 3579f8acf5932825bcbaf6ef5f7214fbfbf8fbd0 7145 wireguard_0.0.20190123-1_amd64.buildinfo Checksums-Sha256: 9d79598ac270d962802f53fc1b73a2476da9f32bdba4543eac0501e45946c833 1513 wireguard_0.0.20190123-1.dsc 7225ee835298e0c8fb9f211a4aaedaa259c5200441da25d497a60d09a03913c7 323640 wireguard_0.0.20190123.orig.tar.xz 7ade718e1c77daee71bfd8ceab9bbd9f6bed9a248bd8da7ecb1df3bf0cf48b9d 24164 wireguard_0.0.20190123-1.debian.tar.xz 8cc2f129b2905f41316b1989a91c7cf44c31444d056069b8f8df78e06d110a3b 7145 wireguard_0.0.20190123-1_amd64.buildinfo Files: 664670207418a0e2a207623fcab8d4b3 1513 net optional wireguard_0.0.20190123-1.dsc 4f001a203713e4e53ea022325bd6d317 323640 net optional wireguard_0.0.20190123.orig.tar.xz e7c4b700ebd8d937ecaa542270523e8b 24164 net optional wireguard_0.0.20190123-1.debian.tar.xz
Bug#920289: marked as done (nmu: pandoc-citeproc-preamble_1.2.3)
Your message dated Mon, 28 Jan 2019 20:53:10 +0100 with message-id <6fd0bb8a-be21-7fa7-edfc-054b20a37...@debian.org> and subject line Re: Bug#920289: nmu: pandoc-citeproc-preamble_1.2.3 has caused the Debian Bug report #920289, regarding nmu: pandoc-citeproc-preamble_1.2.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.) -- 920289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pandoc-citeproc-preamble_1.2.3 . ANY . buster . -m "Rebuild against newer libghc-pandoc-types-dev." pandoc-citeproc-preamble exits with a type error right now, but a simple rebuild is enough to fix the problem. I'm requesting the binnmu in the buster suite because that's what I'm running, but the problem is in both sid and buster. Please excuse my ignorance regarding the interactions between binNMUs in sid and in testing. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On 28/01/2019 17:57, Sean Whitton wrote: > Hello Emilio, > > On Mon 28 Jan 2019 at 03:49PM +01, Emilio Pozuelo Monfort wrote: > >>> nmu pandoc-citeproc-preamble_1.2.3 . ANY . buster . -m "Rebuild against >>> newer libghc-pandoc-types-dev." >>> >>> pandoc-citeproc-preamble exits with a type error right now, but a simple >>> rebuild is enough to fix the problem. >> >> Is that because of a change in an underlying pandoc lib? If so, shouldn't >> pandoc-citeproc-preamble depend on the appropriate virtual packages? > > pandoc-citeproc-preamble doesn't use the Haskell team's CDBS build > infrastructure, so it can't depend on the magic virtual packages. > > I'm filing a bug and making a note to change that, but since I doubt > this will come up again before the full freeze (CCing pandoc maintainer > to confirm), I would like to request the manual binnmu in the meantime. Normally I would request a proper fix, but since this is haskell I went ahead and did the binNMU. But please file the bug at severity >= important. Cheers, Emilio--- End Message ---
Bug#684920: marked as done (tried to just do NAT, blocks protocol 41)
Your message dated Mon, 28 Jan 2019 23:03:44 +0100 with message-id <7147a5073df6fa526a2afa40d21e9f0a251b54cd.ca...@g-e-u-e-r.de> and subject line Re: Bug#684920: tried to just do NAT, blocks protocol 41 has caused the Debian Bug report #684920, regarding tried to just do NAT, blocks protocol 41 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.) -- 684920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arno-iptables-firewall Version: 1.9.2.k-4 With the ipmasq package gone the way of the dodo, I needed NAT functionality on a computer w/ a first-class IPv4 address to run an iodine server on that host. That host already had IPv6 connectivity using the auto6to4 package (in experimental) which sets up a standard 6to4 tunnel to the standard IPv4 anycast address, which uses IPv4 protocol 41 packets. (Note, *protocol* 41, not port 41.) Installing arno-iptables-firewall and configuring it for NAT functionality and *nothing else* blocked the IPv4 protocol 41 packets and thus killed the 6to4 tunnel. When I tried the miredo package instead, that was also broken, for similar reasons. It would be nice if arno-iptables-firewall had a "NAT and no blocking" option, so it could be used as a plug-in replacement for ipmasq, and would be guaranteed not to mess up IPv6 connectivity via IPv4 tunnels. Or at least, if there were documentation. (Of course, this was on a "stable" machine running an old version. If this is fixed in more recent versions --- it doesn't seem to be judging from just changelog entries --- my apologies.) --Barak. -- Barak A. Pearlmutter Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ --- End Message --- --- Begin Message --- Tags: wontfix Hello Barak, On Wed, 22 Aug 2012 11:59:41 +0100 "Barak A. Pearlmutter" < ba...@cs.nuim.ie> wrote: > Okay, will check it out. > > But, could I ask you for precise instructions for installation? > What I want is: "set up NAT for private address blocks, and touch > nothing else", and I'm not sure how to express this with an > ipv6-over-ipv4 plugin. > > (I want the NAT in order to route addresses allocated by an iodine > server running on the machine, which grants its IP-over-DNS clients > addresses of the form 192.168.x.x.) > > --Barak. > > This doesn't look like a bug to me but like a discussion on how to configure the firewall to serve a specific purpose. Maybe you solved this issue with Arno's help back in 2012? Please feel free to open a new bug in case you still think there's really a bug with what you encountered in a more current version of arno-iptables-firewall. Regards, Sven--- End Message ---
Bug#919437: marked as done (winff: [INTL:pt] Updated Portuguese translation - prog messages)
Your message dated Mon, 28 Jan 2019 21:02:30 + with message-id and subject line Bug#919437: fixed in winff 1.5.5-6 has caused the Debian Bug report #919437, regarding winff: [INTL:pt] Updated Portuguese translation - prog messages 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.) -- 919437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: winff Version: 1.5.5-5 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for winff messages Translator: Américo Monteiro Feel free to use it. For translation updates please contact 'Last Translator' -- Melhores cumprimentos/Best regards, Américo Monteiro - winff_1.5.5-5_winff.pt.po.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: winff Source-Version: 1.5.5-6 We believe that the bug you reported is fixed in the latest version of winff, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated winff 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, 26 Jan 2019 22:46:03 +0100 Source: winff Binary: winff winff-gtk2 winff-qt winff-data winff-doc Architecture: source Version: 1.5.5-6 Distribution: unstable Urgency: medium Maintainer: Paul Gevers Changed-By: Paul Gevers Description: winff - graphical video and audio batch converter using ffmpeg or avconv winff-data - winff data files winff-doc - winff documentation winff-gtk2 - GTK+ variant of winff winff-qt - Qt variant of winff Closes: 919042 919437 Changes: winff (1.5.5-6) unstable; urgency=medium . * Update Portuguese translation (Closes: #919437) * Desktop file didn't mention ffmpeg * Description of winff was mentioning meta which isn't true anymore (Closes: #919042) Checksums-Sha1: fb5895823037b076f9720296730b9d9eb344218b 1925 winff_1.5.5-6.dsc 0b6a6f23db7925d36880bd909ae7d2f568946035 84792 winff_1.5.5-6.debian.tar.xz Checksums-Sha256: b5795bea2fcaedb96fd57480b44e6c86536b1f6fde80059e1ec9cc53f6029c73 1925 winff_1.5.5-6.dsc 7018fb48e75ed4a86667efde08fbc4fd590fb75f2f462cf29cfbac7941aebe59 84792 winff_1.5.5-6.debian.tar.xz Files: 6787e6f48f6ae3667b50aee7c5f28f60 1925 video optional winff_1.5.5-6.dsc 3f1307d7f9a07db6c26fd4e7d46a6c21 84792 video optional winff_1.5.5-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlxPYx0ACgkQnFyZ6wW9 dQponQf+KnA/IKw+Cynitipy3QV8s725Pzv7zhQ/pFxCR09LnhAk+KS7ruC/bHdG qtCK/uDNupr2++o7LmMMMv5bwk35ruVynTa7YymhiEu01+RSo9hZaLS/7Kbucez+ Esq1QgIGVr15DJMnashwWaVbSgClKrCOOrnMSl28ktDx6AZYxAiyETxsHUPyrjKn qNXfm41JCpW7mxPeXa0o0q64AJ+OEYrVQTKRl15iOsrtGq88LxUAUseU1YhSRupM OP1QKIHO3twbqqIb0ceJH+jYhXUpFxgPCKkAQgDzE0/9weN2ZT/n3koETi9VsAgp Ww5L3fCG4JwmsOT+Nub0YGwP9EMaJg== =nPAd -END PGP SIGNATURE End Message ---
Bug#919042: marked as done (This is not exactly a "metapackge" :-))
Your message dated Mon, 28 Jan 2019 21:02:30 + with message-id and subject line Bug#919042: fixed in winff 1.5.5-6 has caused the Debian Bug report #919042, regarding This is not exactly a "metapackge" :-) 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.) -- 919042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: winff Version: 1.5.5-5 Severity: minor Problem: The package description of the binary package winff states: | This package is a metapackage to pull in either the GTK+ or Qt variant. This is not exactly correct due to somewhat implicit action of debhelper to include /usr/share/applications/winff.desktop to winff package. Also, the desktop file mentions "avconv" while current situation uses FFmpeg and it is gtk even when it calls winff-qt. Background: When I installed only winff-gtk2 trusting package description of winff, winff didn't have GUI staring entry point. After looking into the git source at https://salsa.debian.org/pascal-team/winff, I realize it only has winff.desktop. I see the problem. Possible solution. Option 1 (simple but sloppy fix): Since winff-data is always called in by the dependency, move winff.desktop to winff-data package. This can be done simply by renaming debian/winff.desktop to winff-data.desktop ... this is easier but Category becomes incorrect for QT package Option 2 (good fix): Make winff-gtk2 and winff-qt package to contain desktop file of the respective package. For this, remove debian/winff.desktop and add: debian/winff-gtk2.desktop [Desktop Entry] Version=1.0 Name=WinFF Comment=GUI for FFmpeg MimeType=application/winff; Exec=winff-gtk2 %f Icon=winff Terminal=false Type=Application Categories=AudioVideo;AudioVideoEditing;GTK; Keywords=avconv;ffmpeg;wrapper;conversion;video;audio; GenericName=Video converter GenericName[en]=Video converter GenericName[nl]=Video converteerder debian/winff-gtk2.qt [Desktop Entry] Version=1.0 Name=WinFF Comment=GUI for FFmpeg MimeType=application/winff; Exec=winff-qt %f Icon=winff Terminal=false Type=Application Categories=AudioVideo;AudioVideoEditing;QT; Keywords=avconv;ffmpeg;wrapper;conversion;video;audio; GenericName=Video converter GenericName[en]=Video converter GenericName[nl]=Video converteerder Here, I fixed FFmpeg thing and QT thing. Regards, Osamu -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (10, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages winff depends on: ii winff-gtk2 1.5.5-5 winff recommends no packages. winff suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: winff Source-Version: 1.5.5-6 We believe that the bug you reported is fixed in the latest version of winff, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated winff 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, 26 Jan 2019 22:46:03 +0100 Source: winff Binary: winff winff-gtk2 winff-qt winff-data winff-doc Architecture: source Version: 1.5.5-6 Distribution: unstable Urgency: medium Maintainer: Paul Gevers Changed-By: Paul Gevers Description: winff - graphical video and audio batch converter using ffmpeg or avconv winff-data - winff data files winff-doc - winff documentation winff-gtk2 - GTK+ variant of winff winff-qt - Qt variant of winff Closes: 919042 919437 Changes: winff (1.5.5-6) unstable; urgency=medium . * Update Portuguese translation (Closes: #919437) * Desktop file didn't mention ffmpeg * Description of winff was mentioning meta which isn't true anymore (Closes: #919042) Checksums-Sha1: fb5895823037b076f9720296730b9d9eb344218b 1925 winff_1.5.5-6.dsc
Bug#913589: marked as done (pqiv FTCBFS: builds for the wrong architecture)
Your message dated Mon, 28 Jan 2019 22:19:46 +0100 with message-id and subject line has caused the Debian Bug report #913589, regarding pqiv FTCBFS: builds for the wrong architecture 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.) -- 913589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pqiv Version: 2.10.4-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap pqiv fails to cross build from source. For cross building pqiv, one is supposed to pass --cross to ./configure. Even then it fails, because its GNUmakefile (sic) fails to detect that X11 is needed using the wrong pkg-config. The attached patch fixes both and makes pqiv cross buildable. Please consider applying the attached patch. Helmut diff --minimal -Nru pqiv-2.10.4/debian/changelog pqiv-2.10.4/debian/changelog --- pqiv-2.10.4/debian/changelog2018-04-23 20:30:00.0 +0200 +++ pqiv-2.10.4/debian/changelog2018-11-12 17:38:48.0 +0100 @@ -1,3 +1,12 @@ +pqiv (2.10.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) ++ Pass --cross to ./configure. ++ cross.patch: Don't hard code the build architecture pkg-config. + + -- Helmut Grohne Mon, 12 Nov 2018 17:38:48 +0100 + pqiv (2.10.4-1) unstable; urgency=medium * New maintainer. diff --minimal -Nru pqiv-2.10.4/debian/patches/cross.patch pqiv-2.10.4/debian/patches/cross.patch --- pqiv-2.10.4/debian/patches/cross.patch 1970-01-01 01:00:00.0 +0100 +++ pqiv-2.10.4/debian/patches/cross.patch 2018-11-12 17:38:48.0 +0100 @@ -0,0 +1,11 @@ +--- pqiv-2.10.4.orig/GNUmakefile pqiv-2.10.4/GNUmakefile +@@ -94,7 +94,7 @@ + endif + + # We need X11 to workaround a bug, see http://stackoverflow.com/questions/18647475 +-ifeq ($(filter x11, $(shell pkg-config --errors-to-stdout --variable=target gtk+-$(GTK_VERSION).0; pkg-config --errors-to-stdout --variable=targets gtk+-$(GTK_VERSION).0)), x11) ++ifeq ($(filter x11, $(shell $(PKG_CONFIG) --errors-to-stdout --variable=target gtk+-$(GTK_VERSION).0; $(PKG_CONFIG) --errors-to-stdout --variable=targets gtk+-$(GTK_VERSION).0)), x11) + LIBS+=x11 + endif + diff --minimal -Nru pqiv-2.10.4/debian/patches/series pqiv-2.10.4/debian/patches/series --- pqiv-2.10.4/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ pqiv-2.10.4/debian/patches/series 2018-11-12 17:38:48.0 +0100 @@ -0,0 +1 @@ +cross.patch diff --minimal -Nru pqiv-2.10.4/debian/rules pqiv-2.10.4/debian/rules --- pqiv-2.10.4/debian/rules2018-04-23 20:30:00.0 +0200 +++ pqiv-2.10.4/debian/rules2018-11-12 17:38:43.0 +0100 @@ -4,12 +4,17 @@ export VERBOSE=1 export DEB_BUILD_MAINT_OPTIONS=hardening=+all +include /usr/share/dpkg/architecture.mk +ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) +CONFIGURE_FLAGS += --cross=$(DEB_HOST_GNU_TYPE) +endif + %: dh $@ override_dh_auto_configure: - ./configure --backends-build=shared + ./configure --backends-build=shared $(CONFIGURE_FLAGS) override_dh_shlibdeps: dh_shlibdeps -Xlib --- End Message --- --- Begin Message --- Version: 2.11-1 The changes should be included in 2.11-1.--- End Message ---
Bug#388267: marked as done (texlive-latex-recommanded: problem with subfig and beamer)
Your message dated Mon, 28 Jan 2019 21:23:09 +0100
with message-id <587090af-c55f-76f8-86fa-b882892e8...@web.de>
and subject line Re: Bug#388267: Info received (Bug#388267:
texlive-latex-recommanded: problem with subfig and beamer)
has caused the Debian Bug report #388267,
regarding texlive-latex-recommanded: problem with subfig and beamer
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.)
--
388267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-recommanded
Version: problem with subfig and beamer
Severity: normal
Hello
I am still using beamer for my presentation
if you use the attached file you will see that pdflatex hang with:
(/usr/share/texmf-texlive/tex/latex/beamer/beamerbasethemes.sty)
(/usr/share/texmf-texlive/tex/latex/beamer/themes/theme/beamerthemedefault.sty
(/usr/share/texmf-texlive/tex/latex/beamer/themes/font/beamerfontthemedefault.s
ty)
(/usr/share/texmf-texlive/tex/latex/beamer/themes/color/beamercolorthemedefault
..sty)
(/usr/share/texmf-texlive/tex/latex/beamer/themes/inner/beamerinnerthemedefault
..sty)
(/usr/share/texmf-texlive/tex/latex/beamer/themes/outer/beamerouterthemedefault
..sty))) (/usr/share/texmf-texlive/tex/latex/ucs/ucs.sty
(/usr/share/texmf-texlive/tex/latex/ucs/data/uni-global.def))
(/usr/share/texmf-texlive/tex/latex/base/inputenc.sty
(/usr/share/texmf-texlive/tex/latex/ucs/utf8x.def))
(/usr/share/texmf-texlive/tex/latex/subfig/subfig.sty
(/usr/share/texmf-texlive/tex/latex/caption/caption.sty
(/usr/share/texmf-texlive/tex/latex/caption/caption3.sty)
! LaTeX Error: \@makecaption undefined.
See the LaTeX manual or LaTeX Companion for explanation.
Type H for immediate help.
...
l.184 \renewcommand\@makecaption
[2]{%
So it seems that subfig do not works with beamer.
I check that without beamer the problem is not present.
using \documentclass{article} instead of \documentclass{beamer}
Have a nice day.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686-smp
Locale: LANG=fr_FR.UTF-8@euro, LC_CTYPE=fr_FR.UTF-8@euro (charmap=UTF-8)
\documentclass[11pt]{beamer}
\usepackage{ucs}
\usepackage[utf8x]{inputenc}
\usepackage{subfig}
\title{Présentation du logiciel de commande des diffractomètres}
\author{Picca Frédéric-Emmanuel}
\date{26 Septembre 2006, CSE}
\subject{Presentation Programs}
\institute[SOLEIL]{Soleil Synchrotron}
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\end{document}
--- End Message ---
--- Begin Message ---
Version: 2005.dfsg.2-2
On 02.05.14 17:00, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
Bug probably solved as clone has been closed log ago. Closing too.
H.
--
sigfault
#206401 http://counter.li.org
signature.asc
Description: OpenPGP digital signature
--- End Message ---
Bug#916814: marked as done (cacti: [1.2.0 Beta 4] Spike Kill not working (missing file))
Your message dated Mon, 28 Jan 2019 20:51:38 + with message-id and subject line Bug#916814: fixed in cacti 1.2.1+ds1-1 has caused the Debian Bug report #916814, regarding cacti: [1.2.0 Beta 4] Spike Kill not working (missing file) 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.) -- 916814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cacti Version: 1.2.0~beta4+ds1-1 Severity: normal Dear Maintainer, Spike Kill functionality is not working. Clicking on dry run generates an error message "Could not open input file: /usr/share/cacti/site/cli/removespikes.php". Problem was reported upstream, but they have suggested this is a packaging bug https://github.com/Cacti/cacti/issues/2218 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cacti depends on: ii dbconfig-common 2.0.11 ii dbconfig-mysql2.0.11 ii debconf [debconf-2.0] 1.5.69 ii fonts-dejavu-core 2.37-1 ii fonts-dejavu-extra2.37-1 ii fonts-font-awesome5.0.10+really4.7.0~dfsg-1 ii javascript-common 11 ii libapache2-mod-php2:7.3+68 ii libapache2-mod-php7.3 [libapache2-mod-ph 7.3.0-1 ii libjs-c3 0.4.11+dfsg-2 ii libjs-chartjs 1.0.2-1 ii libjs-d3 3.5.17-2 ii libjs-jquery 3.2.1-1 ii libjs-jquery-colorpicker 1.2.17-1 ii libjs-jquery-cookie 12-1.1 ii libjs-jquery-hotkeys 0~20130707+git2d51e3a9+dfsg-2 ii libjs-jquery-jstree 3.3.7+dfsg1-1 ii libjs-jquery-metadata 12-1.1 ii libjs-jquery-tablesorter 1:2.31.1+dfsg1-1 ii libjs-jquery-timepicker 1.2-1 ii libjs-jquery-ui 1.12.1+dfsg-5 ii libjs-jquery-ui-theme-smoothness 1.12.1+dfsg-1 ii libjs-jquery-ui-theme-south-street1.12.1+dfsg-1 ii libjs-jquery-ui-theme-ui-darkness 1.12.1+dfsg-1 ii libjs-jquery-ui-touch-punch 0.0~git20141218.2.4bc0091+dfsg1-2 ii libphp-phpmailer 5.2.14+dfsg-2.4 ii perl 5.28.1-3 ii php-gd2:7.3+68 ii php-ldap 2:7.3+68 ii php-mbstring 2:7.3+68 ii php-mysql 2:7.3+68 ii php-php-gettext 1.0.12-0.1 ii php-phpseclib 2.0.12-1 ii php-snmp 2:7.3+68 ii php-twig 2.5.0-1 ii php-xml 2:7.3+68 ii php7.3-cli [php-cli] 7.3.0-1 ii php7.3-gd [php-gd]7.3.0-1 ii php7.3-json [php-json]7.3.0-1 ii php7.3-ldap [php-ldap]7.3.0-1 ii php7.3-mbstring [php-mbstring]7.3.0-1 ii php7.3-snmp [php-snmp]7.3.0-1 ii php7.3-xml [php-xml] 7.3.0-1 ii rrdtool 1.7.0-1+b3 ii snmp 5.7.3+dfsg-4+b1 ii ucf 3.0038 Versions of packages cacti recommends: ii apache2 [httpd] 2.4.37-1 ii default-mysql-server1.0.4 ii iputils-ping3:20180629-2 ii logrotate 3.14.0-4 ii mariadb-server-10.1 [virtual-mysql-server] 1:10.1.37-3 ii php-gmp 2:7.3+68 ii php7.3-gmp [php-gmp]7.3.0-1 Versions of packages cacti suggests: pn cacti-spine pn moreutils pn snmpd -- debconf information excluded --- End Message --- --- Begin Message --- Source: cacti Source-Version: 1.2.1+ds1-1 We believe that the bug you reported is fixed in the latest version of cacti, which is due to be installed in the Debian
Bug#919817: marked as done (mysql-5.7: Security fixes from the January 2019 CPU)
Your message dated Mon, 28 Jan 2019 20:56:52 + with message-id and subject line Bug#919817: fixed in mysql-5.7 5.7.25-1 has caused the Debian Bug report #919817, regarding mysql-5.7: Security fixes from the January 2019 CPU 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.) -- 919817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-5.7 Version: 5.7.24-3 Severity: grave Tags: security upstream Justification: user security hole Hi Details at https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#AppendixMSQL Regards, Salvatore --- End Message --- --- Begin Message --- Source: mysql-5.7 Source-Version: 5.7.25-1 We believe that the bug you reported is fixed in the latest version of mysql-5.7, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lars Tangvald (supplier of updated mysql-5.7 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Jan 2019 08:03:45 +0100 Source: mysql-5.7 Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7 Architecture: source Version: 5.7.25-1 Distribution: unstable Urgency: high Maintainer: Debian MySQL Maintainers Changed-By: Lars Tangvald Description: libmysqlclient-dev - MySQL database development files libmysqlclient20 - MySQL database client library libmysqld-dev - MySQL embedded database development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.7 - MySQL database client binaries mysql-client-core-5.7 - MySQL database core client binaries mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.7 - MySQL database server binaries and system database setup mysql-server-core-5.7 - MySQL database server binaries mysql-source-5.7 - MySQL source mysql-testsuite - MySQL regression tests mysql-testsuite-5.7 - MySQL 5.7 testsuite Closes: 919817 Changes: mysql-5.7 (5.7.25-1) unstable; urgency=high (security fixes) . * Imported upstream version 5.7.25 to fix security issues: - https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html - CVE-2018-0734 CVE-2019-2420 CVE-2019-2434 CVE-2019-2455 - CVE-2019-2481 CVE-2019-2482 CVE-2019-2486 CVE-2019-2503 - CVE-2019-2507 CVE-2019-2510 CVE-2019-2528 CVE-2019-2529 - CVE-2019-2531 CVE-2019-2532 CVE-2019-2534 CVE-2019-2537 (Closes: #919817) Checksums-Sha1: f268bdacf122c1cee2c22b24178943c925fe39e3 3229 mysql-5.7_5.7.25-1.dsc cbec35bbe2f2540232105a307770c432380be352 49107578 mysql-5.7_5.7.25.orig.tar.gz ff3b9a8a74ce38fa89ce45794fc4770b373918ac 156756 mysql-5.7_5.7.25-1.debian.tar.xz Checksums-Sha256: 23c71f834fcefd5766b130243558844d578e51858271f5f10231e19ae92bf3bd 3229 mysql-5.7_5.7.25-1.dsc 354c427c8679c6a4774f60723ea211e54b4383307764d240940f960d110bf5cf 49107578 mysql-5.7_5.7.25.orig.tar.gz 40c4d766d4c154c54982fba3e6683279fdc11bb8ca89cdcb596415645d827e94 156756 mysql-5.7_5.7.25-1.debian.tar.xz Files: 7d30f684b59316b3112a58b955fc7380 3229 database optional mysql-5.7_5.7.25-1.dsc db53cbcc972276cec7a450b042956c57 49107578 database optional mysql-5.7_5.7.25.orig.tar.gz 31fe0ce87d8e78cbbc072319179f07b2 156756 database optional mysql-5.7_5.7.25-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJcT1+fAAoJEOVkucJ1vdUu5rwP/28rKR43o3juNnlnlfeqFoTp rbDnvtF1ltcoEDK52PsRZp3m4W6bI3DqtMy5pYTVklwKsB2hy7CaiLije/OqDqHo fSry/lAiOkh43VqFKYpgCBgDcMeMUVrTeZKsJI1k0WQk+NKeHPxm+r9Fz8Q6GCOg U5tXsw+AVug7w2VJpwB4LbW3LcuZ7vH+Hd19dwtUbxVM4J1+1zCE6h48K6C0F8oW VuHGvyH1Ltmw1zEgi9BjWBTmzvySqBO8UtKfObs3px7Xzjy3qH5pKlYUXfFOWyAg 3JHI8QNSrV+n4O7kGq8uPQ2uPNHFj8DwRElQakKvJUdTbkwnKIHgj7k/MKcYxO2P F2W6Kn7SLixSvaQwKqCTogEi/HYLOJDyOPTVxM/GZjjv8W25KUj89YUz4wS+YU9W FjoOhGW81GGXLnNWUMWRNk3FJM4Gm9WriNlKJ2vmWGFlwR1Utfe4Q9jfgrv2+RRM
Bug#894710: marked as done (awesome: move out of asciidoc)
Your message dated Mon, 28 Jan 2019 21:35:02 + with message-id and subject line Bug#894710: fixed in awesome 4.3-1 has caused the Debian Bug report #894710, regarding awesome: move out of asciidoc 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.) -- 894710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: awesome Version: 4.2-5 Severity: wishlist Dear Maintainer, Asciidoc is currently facing its end of life and I'm working with the different packages that depend on it to get its EOL go smooth. There are several alternatives to asciidoc like asciidoctor for example (which is the replacement recommended by asciidoc developers). Could you have your package migrated to an alternative system please? Note: I already pushed an upstream PR https://github.com/awesomeWM/awesome/pull/2234 in case it can help for follow-up. Thanks for your help, Joseph --- End Message --- --- Begin Message --- Source: awesome Source-Version: 4.3-1 We believe that the bug you reported is fixed in the latest version of awesome, 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 894...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated awesome package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 21:57:00 +0100 Source: awesome Architecture: source Version: 4.3-1 Distribution: unstable Urgency: medium Maintainer: Reiner Herrmann Changed-By: Reiner Herrmann Closes: 886393 894710 Changes: awesome (4.3-1) unstable; urgency=medium . * New upstream release. - handle SIGCHLD directly instead of through GLib (Closes: #886393) * Drop obsolete/applied patches and refresh remaining ones. * Build-depend on asciidoctor instead of asciidoc. (Closes: #894710) * Update Standards-Version to 4.3.0. - declare that debian/rules does not require root * Bump copyright years. * Install upstream release notes into /usr/share/doc/awesome/. * Build-depend on debhelper-compat and bump compat level to 12. * Update test dependencies. * Cherry-pick upstream patches to build example images reproducibly. Checksums-Sha1: d2d9c2274f8b17023e71d4c7663771e9aab2f885 2825 awesome_4.3-1.dsc 543f3b2ee17719176f37fbe3f0cfd1d046a9e1cc 1037816 awesome_4.3.orig.tar.xz c97fe5710cc853525f03d2ff93b257727cfbe7e5 488 awesome_4.3.orig.tar.xz.asc d29a5f9543b53ca5bfbdfd8ae932c08f84741ff4 21524 awesome_4.3-1.debian.tar.xz c85e08c2da42a9394469b8e539449a000dd9c311 12844 awesome_4.3-1_source.buildinfo Checksums-Sha256: ffe083e99ddb3077a5adfc59c5c68e9bd629bededff43d9c05bbdf69e4ef4580 2825 awesome_4.3-1.dsc 78264d6f012350b371e339127aca485260bc0aa935eff578ba75ce1a00e11753 1037816 awesome_4.3.orig.tar.xz 6afb73289caed82173d56a8e496658fdd338a0dadc436fd074f1261d2cd229fd 488 awesome_4.3.orig.tar.xz.asc bd5f766feb36b3e3e3f9ef72b7967d9a381d06f0225e61d3e585016aeb194680 21524 awesome_4.3-1.debian.tar.xz 7b6a03595d6954a6f90b5b5f46524474190fbddccd2ac0f6041d46e2298387fb 12844 awesome_4.3-1_source.buildinfo Files: 169562904be5a2d77e797bc28d127405 2825 x11 optional awesome_4.3-1.dsc 4d75cce54a86b6bbaa6e88a926cab5a7 1037816 x11 optional awesome_4.3.orig.tar.xz 7b375f04dd54542867f777f2abfb820b 488 x11 optional awesome_4.3.orig.tar.xz.asc fd79e93988c0a88b290d868a51e40f75 21524 x11 optional awesome_4.3-1.debian.tar.xz c15daf19de1824ca5d78bc6e246910c1 12844 x11 optional awesome_4.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAlxPbNoACgkQzPBJKNsO 6qdfORAA5KvBrWPKReZ9mm89dZ5DGyXi4przSFfssMZDS3oUoc97vf5syzCbdT/U WWRcop7KGvCRdXSO9ii4IFSr141413Wrt2aENf0RGZYhxhBzoyPz3F8+hEbN9bUv PoiJ6tyb4tcwUH6xwpLL+XjC+OpQrzlLTDnmUdysoZc8qlfSORYjzFX13W086kDs YDGltn9mD+HGXgFybbL2kYb/ccqjs+jcPNaFfWwepMVu4rWAGrcaqjeG7QNuqyUx pOmg1LqQi9U4cWWMnuJdbXSWPLOiziWWJXq2/ybGhnD+mClXEaJalE0cIuOVy8S1 D0kTomJA+VB8Tou82bQNnHeB1f7H541YU+cNMUzWjROEq+Pmh43ccstL3zQxW2tt iU97zGKNV6jMMqwlI7xlvNqqKn8Q4BBcc29U8xoGHDhrwP5XeDXIjwSNWITLQwtT ROyDTjA5U2++mKZ2dwZWqRNhX5/iMem7XxWZz5y4I2Qy5KhKaxToMuy7kjYtmm30
Bug#857191: marked as done (jabberd2: service file uses deprecated BindTo=)
Your message dated Mon, 28 Jan 2019 22:24:50 + with message-id and subject line Bug#857191: fixed in jabberd2 2.7.0-1 has caused the Debian Bug report #857191, regarding jabberd2: service file uses deprecated BindTo= 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.) -- 857191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jabberd2 Version: 2.4.0-3 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: obsolete-bind-to Hi, according to [1] your package jabberd2 ships one or more systemd service files which uses BindTo=. This option was renamed to BindsTo= quite a while ago [2]. For compatibility reasons the old name is still understood, but we want to avoid using the old, deprecated names. It would be great if you can change all occurences of BindTo= to BindsTo= and also send this change to upstream. Regards, Michael [1] https://codesearch.debian.net/search?q=BindTo%3D+package%3Ajabberd2 [2] https://github.com/systemd/systemd/commit/7f2cddae09fd2579ae24434df577bb5e5a157d86 --- End Message --- --- Begin Message --- Source: jabberd2 Source-Version: 2.7.0-1 We believe that the bug you reported is fixed in the latest version of jabberd2, 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 857...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Josefsson (supplier of updated jabberd2 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: Mon, 28 Jan 2019 22:29:15 +0100 Source: jabberd2 Binary: jabberd2 jabberd2-dbgsym Architecture: source amd64 Version: 2.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: Simon Josefsson Description: jabberd2 - Jabber instant messenger server Closes: 857191 917758 Changes: jabberd2 (2.7.0-1) unstable; urgency=medium . * New upstream version. - Adapt pkgname.diff. - Drop patches/systemd-bindsto.diff (fixed upstream). Closes: #857191. - Drop debian/patches/openssl11.diff (fixed upstream). - Fixes MySQL build problems. Closes: #917758 * Update Standards-Version from 4.1.3 to 4.3.0. * Rename tag in debian/source/lintian-overrides. * Drop trailing whitespace in debian/changelog. * Fix typo in debian/patches/man_hypen.diff. * Use https for Homepage: URL. Checksums-Sha1: d32dfdaf49333c3e26b2caf06ebfa2098e275f1c 1774 jabberd2_2.7.0-1.dsc 9200b9f22188caf603630d98d6f1c17c87a957b9 629992 jabberd2_2.7.0.orig.tar.gz 236d96db04f4ff2ebdf65848fdec288f830e75d9 17200 jabberd2_2.7.0-1.debian.tar.xz f4961ae1ca021651aba103dee5dc2d30ff74f6a8 2133516 jabberd2-dbgsym_2.7.0-1_amd64.deb c079831bb18ee4487f076be36d78805d120588bb 6754 jabberd2_2.7.0-1_amd64.buildinfo 4c81ac7c24e6df3a5e1f8257eae8dc92a6049a50 388504 jabberd2_2.7.0-1_amd64.deb Checksums-Sha256: fd856f208a95b6e9d52be1897afd48e6adc8a1f4062ff11b7bf303bfaa7787b5 1774 jabberd2_2.7.0-1.dsc 8ed7ae5952819d9e5bf1efb45735bfff3786b60144d9f60f8fe2788f552f1989 629992 jabberd2_2.7.0.orig.tar.gz 3218b920b9411ebb49986400b8b6f83fb7ae1f3a11626f32bb466593d76131b5 17200 jabberd2_2.7.0-1.debian.tar.xz e08a1d0a7ba3852e07413baca6293e95bb331ff756fa098b0ec414bd3530f936 2133516 jabberd2-dbgsym_2.7.0-1_amd64.deb 01a82c7d080561482337835852db88c0511d5e098fb6acd2c6735a073911092a 6754 jabberd2_2.7.0-1_amd64.buildinfo 3e7d4d723fe2c13c1317b1f6905961be07812550d525fe893ede0faaeb3f693e 388504 jabberd2_2.7.0-1_amd64.deb Files: 68bc56b2dc96c9bc0614ad48a62d8f91 1774 net optional jabberd2_2.7.0-1.dsc c2a01ab0c34b2d8f6a7e32f5cf6a2182 629992 net optional jabberd2_2.7.0.orig.tar.gz a6d94445adcc39ec755a2cf2f4438134 17200 net optional jabberd2_2.7.0-1.debian.tar.xz 3679a0fd3d4728067f55d554ec9498d0 2133516 debug optional jabberd2-dbgsym_2.7.0-1_amd64.deb d1b680e5358999e2edcfdfa4643c156c 6754 net optional jabberd2_2.7.0-1_amd64.buildinfo 1af4c54bcbbc8a7e593ef59be96f5bd7 388504 net optional jabberd2_2.7.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQFIBAEBCAAyFiEEmUFc4ZBdDlWp+IAmhgt/uzL4EZ0FAlxPezEUHHNpbW9uQGpv
Bug#917758: marked as done (jabberd2: FTBFS: mysql-related errors)
Your message dated Mon, 28 Jan 2019 22:24:50 + with message-id and subject line Bug#917758: fixed in jabberd2 2.7.0-1 has caused the Debian Bug report #917758, regarding jabberd2: FTBFS: mysql-related errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jabberd2 Version: 2.6.1-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/storage' > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time > -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > libstorage_la-storage.lo `test -f 'storage.c' || echo './'`storage.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time > -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > libstorage_la-object.lo `test -f 'object.c' || echo './'`object.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > authreg_anon.lo authreg_anon.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > authreg_db.lo authreg_db.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > storage_db.lo storage_db.c > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H > -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -funsigned-char -fdiagnostics-color -c -o > storage_fs.lo storage_fs.c > [01m[Kstorage_fs.c:[m[K In function '[01m[K_st_fs_put[m[K': > [01m[Kstorage_fs.c:173:64:[m[K [01;35m[Kwarning: [m[Kcast from > pointer to integer of different size [[01;35m[K-Wpointer-to-int-cast[m[K] > fprintf(f, "%s %d %d\n", key, ot, > ([01;35m[K([m[Kint)val != 0) ? 1 : 0); > > [01;35m[K^[m[K > [01m[Kstorage_fs.c:177:63:[m[K [01;35m[Kwarning: [m[Kcast from > pointer to integer of different size [[01;35m[K-Wpointer-to-int-cast[m[K] > fprintf(f, "%s %d %d\n", key, ot, > [01;35m[K([m[Kint) val); > > [01;35m[K^[m[K > [01m[Kstorage_fs.c:[m[K In function '[01m[K_st_fs_delete[m[K': > [01m[Kstorage_fs.c:383:34:[m[K [01;35m[Kwarning: > [m[K'[01m[K%s[m[K' directive output may be truncated writing up to 255 > bytes into a region of size between 0 and 1023 > [[01;35m[K-Wformat-truncation=[m[K] > snprintf(file, 1024, "%s/[01;35m[K%s[m[K", path, dirent->d_name); > [01;35m[K^~[m[K > In file included from [01m[K/usr/include/stdio.h:873[m[K, > from [01m[K../util/util.h:27[m[K, > from [01m[Kstorage.h:38[m[K, > from [01m[Kstorage_fs.c:36[m[K: > [01m[K/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10:[m[K > [01;36m[Knote: [m[K'[01m[K__builtin___snprintf_chk[m[K' output > between 2 and 1280 bytes into a destination of size 1024 >return [01;36m[K__builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL > - 1,[m[K > > [01;36m[K^~~~[m[K > [01;36m[K __bos (__s), __fmt,
Bug#903751: marked as done (basket: please remove the extra libsoprano-dev build dependency)
Your message dated Tue, 29 Jan 2019 02:46:08 + with message-id and subject line Bug#903751: fixed in basket 2.11~beta+git20180715.058ce7a-1 has caused the Debian Bug report #903751, regarding basket: please remove the extra libsoprano-dev build 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.) -- 903751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: basket Version: 2.10~beta+git20160425.b77687f-1 Severity: normal Tags: patch Hi, the libsoprano-dev build dependency was added in version 2.10~beta+git20150905.faa6dce-1; it is used to enable the nepomuk integration, which is not actually enabled since the nepomuk libraries are not available anymore (and shared-desktop-ontologies is not installed either). basket builds fine without the libsoprano-dev build dependency, so please remove it. Patch attached for it. Thanks, -- Pino --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: optional Maintainer: Debian KDE Extras Team Uploaders: Mark Purcell , Sune Vuorela , Luigi Toscano Build-Depends: debhelper (>= 9), pkg-kde-tools (>= 0.5), cmake, libx11-dev, pkg-config, libqimageblitz-dev, - shared-mime-info, libsoprano-dev, kdelibs5-dev, kdepimlibs5-dev (>=4:4.4.3), libgpgme11-dev + shared-mime-info, kdelibs5-dev, kdepimlibs5-dev (>=4:4.4.3), libgpgme11-dev Homepage: http://basket.kde.org/ Standards-Version: 3.9.8 Vcs-Git: https://anonscm.debian.org/git/pkg-kde/kde-extras/basket.git --- End Message --- --- Begin Message --- Source: basket Source-Version: 2.11~beta+git20180715.058ce7a-1 We believe that the bug you reported is fixed in the latest version of basket, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Toscano (supplier of updated basket 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: Mon, 28 Jan 2019 22:46:57 -0300 Source: basket Binary: basket basket-data Architecture: source Version: 2.11~beta+git20180715.058ce7a-1 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Luigi Toscano Description: basket - multi-purpose note-taking application for KDE basket-data - data files for BasKet Notepads Closes: 903751 Changes: basket (2.11~beta+git20180715.058ce7a-1) unstable; urgency=medium . [ Luigi Toscano ] * New git snapshot: - Bump version number, still use a git snapshot with additional fixes. * Update few metadata (URLs, emails): - maintainer list address (list.alioth->alioth-lists); - Vcs-Git/Vcs-Url (from alioth to salsa); - homepage (not a KDE project for a while). * Remove the dependency on libsoprano-dev (Closes: #903751). - not used anymore (no Nepomuk integration). Thanks Pino Toscano for the patch. * Various clean ups: - remove the trailing spaces from few packaging files (changelog, control, copyright, watch); - replace tabs with spaces in the copyright file; - run wrap-and-sort; - fix a typo in the copyright file. * Bump Standards-Version to 4.3.0, no changes required. . [ Lisandro Damián Nicanor Pérez Meyer ] * Remove last empty line in changelog as lintian detects it as a trailing space. Checksums-Sha1: d097838caf30455333e82f3febdc901b9e4dbc46 2338 basket_2.11~beta+git20180715.058ce7a-1.dsc 96eb57d8ad3dcedd9077f37577e9b69097682543 2846340 basket_2.11~beta+git20180715.058ce7a.orig.tar.xz df73143f22aa8d52c04cdaa480b8cfa4f6d13366 8180 basket_2.11~beta+git20180715.058ce7a-1.debian.tar.xz 86ec4085843a7d05f47f8566fc4dd430ee10a4d1 6053 basket_2.11~beta+git20180715.058ce7a-1_source.buildinfo Checksums-Sha256: 7612f0f9b8e05d8419fb784c5f435556e68117776e23fe6a019cabbce2fcc6bd 2338 basket_2.11~beta+git20180715.058ce7a-1.dsc 50bd189ff26053ffe6c66ad172d1b626fe523ebe8328db0e2e6126f613c66636 2846340 basket_2.11~beta+git20180715.058ce7a.orig.tar.xz 20f7cdbe9c3f21846029ac52285a5f601779013ba8a5211e4d6e70fc24483906 8180 basket_2.11~beta+git20180715.058ce7a-1.debian.tar.xz
Bug#919780: marked as done (Please provide compatibility link under /usr/lib/rustlib/src)
Your message dated Tue, 29 Jan 2019 02:56:00 + with message-id <04f124bf-2735-9e2d-d9fb-441e87a1e...@debian.org> and subject line Re: Please provide compatibility link under /usr/lib/rustlib/src has caused the Debian Bug report #919780, regarding Please provide compatibility link under /usr/lib/rustlib/src 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.) -- 919780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-src Version: 1.31.0+dfsg1-2 Hello, It seems the default upstream install places its source files in /usr/lib/rustlib/src/rust/src (two "src", apparently), and many tools default to that path. It would be great (and very convenient) if the rust-src package could provide a compatibility link such as: /usr/lib/rustlib/src/rust/src -> /usr/src/rustc-1.31.0/src This way the source is still, as per policy, in /usr/share/src, but we'd be saved from having to configure every tool to use that path, and/or to maintain a local symlink, and keep it updated. Thanks for considering, -d --- End Message --- --- Begin Message --- Control: notfound -1 1.31.0+dfsg1-2 On Sat, 19 Jan 2019 11:45:38 -0300 Dato =?utf-8?B?U2ltw7M=?= wrote: > Package: rust-src > Version: 1.31.0+dfsg1-2 > > Hello, > > It seems the default upstream install places its source files in > /usr/lib/rustlib/src/rust/src (two "src", apparently), and many > tools default to that path. > > It would be great (and very convenient) if the rust-src package > could provide a compatibility link such as: > > /usr/lib/rustlib/src/rust/src -> /usr/src/rustc-1.31.0/src > We already have a symlink /usr/lib/rustlib/src/rust -> /usr/src/rustc-1.31.0 in the version that reported this bug for. Does it not work for you? X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git--- End Message ---
Bug#912310: marked as done (erlang-erlware-commons FTBFS: ERROR: eunit failed while processing /<>/erlang-erlware-commons-1.2.0+dfsg: rebar_abort)
Your message dated Tue, 29 Jan 2019 03:19:45 +
with message-id
and subject line Bug#912310: fixed in erlang-erlware-commons 1.3.1+dfsg-1
has caused the Debian Bug report #912310,
regarding erlang-erlware-commons FTBFS: ERROR: eunit failed while processing
/<>/erlang-erlware-commons-1.2.0+dfsg: rebar_abort
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.)
--
912310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-erlware-commons
Version: 1.2.0+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=erlang-erlware-commons=sid
...
Total: 65%
DEBUG: Reconstruct kernel [{logger_level,notice},
{logger_sasl_compatible,false}]
DEBUG: Reconstruct rebar []
DEBUG: Reconstruct stdlib []
DEBUG: Reconstruct crypto [{fips_mode,false},{rand_cache_size,896}]
DEBUG: No processes to kill
ERROR: One or more eunit tests failed.
ERROR: eunit failed while processing
/<>/erlang-erlware-commons-1.2.0+dfsg: rebar_abort
make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:138: rebar_eunit]
Error 1
--- End Message ---
--- Begin Message ---
Source: erlang-erlware-commons
Source-Version: 1.3.1+dfsg-1
We believe that the bug you reported is fixed in the latest version of
erlang-erlware-commons, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu (supplier of updated
erlang-erlware-commons package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 29 Jan 2019 12:00:12 +0900
Source: erlang-erlware-commons
Architecture: source
Version: 1.3.1+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Erlang Packagers
Changed-By: Nobuhiro Iwamatsu
Closes: 912310
Changes:
erlang-erlware-commons (1.3.1+dfsg-1) experimental; urgency=medium
.
* New upstream release.
* Ignore fail of test. (Closes: #912310)
Checksums-Sha1:
43744bc049a5f94b7df47bfde6dd971503aab736 2194
erlang-erlware-commons_1.3.1+dfsg-1.dsc
bf4889a87905c7ead45cbc6d8de5e75bca803f73 46576
erlang-erlware-commons_1.3.1+dfsg.orig.tar.xz
11c69e5eff26551893a62a7006991008cea92832 3356
erlang-erlware-commons_1.3.1+dfsg-1.debian.tar.xz
6b28511eead5ad4348183ac031d70dc3cd7151a9 9295
erlang-erlware-commons_1.3.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
2adfe3d4fcaef312c2486d3ef61b9e17a5960042e8fdb6304a915986987088af 2194
erlang-erlware-commons_1.3.1+dfsg-1.dsc
615c672d8d0209bbbdcdf61ede86e097f68e86ad6631acaaff17c15ad23f10f4 46576
erlang-erlware-commons_1.3.1+dfsg.orig.tar.xz
b8398dcc0a0b24d868e3844459e896c22ed487ff7f5743d974cec844f03e4050 3356
erlang-erlware-commons_1.3.1+dfsg-1.debian.tar.xz
dca9fa7112320a3e574ede75e85abe0e3660f74ec94e2ed5c029fb74bba90aef 9295
erlang-erlware-commons_1.3.1+dfsg-1_amd64.buildinfo
Files:
243a02d47bd68ac0bc15a615669d63d3 2194 devel optional
erlang-erlware-commons_1.3.1+dfsg-1.dsc
cc046ccc48518400d74c87d0f5417dfe 46576 devel optional
erlang-erlware-commons_1.3.1+dfsg.orig.tar.xz
f8de49e6c6de48aedbaf672605b5a2c6 3356 devel optional
erlang-erlware-commons_1.3.1+dfsg-1.debian.tar.xz
dce628af951e945e561a576609b86f40 9295 devel optional
erlang-erlware-commons_1.3.1+dfsg-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlxPw0IACgkQMiR/u0Ct
H6Y3Sw//ZPLSzOWjhWMNvzwe9QyXRe5/AYr+u5C0pUHJErUC46Im/48l8fIbH9tY
GI9qVBgOUC6IkaTBFnP/BZZiN/tNAEqdrMAKt2oxQFmXhQKS9Zk1iqcTbJSK8qIz
+DfR4Cr9Xu8KxIY3nYlbqJuJXcwvioW3QiCVKoZtJolOJlEdUtYKJ38AyEJH1czo
VN3h7wpgQ9h6tg/qfDeq+BbbXEwAbs4KkhV2x0M0l6LmJ/c6kSAS9/hBZPBSceWC
JtG34AiepQYsu4RRiEDoo3Vn2KzMtR3c5sG2y8uKu4AJI/UiWvjA7xaNAVPbMpV2
+6lI/FxmCmh4P3wUUIF3FhWV+qWE5bK0d5Bhw+MVnTB0CPNeo0KTIIvwc9rlAy0u
UGgwcyjmXECZvQ8+QL5QKTcZA6PIotZpzISEl3RROLEl3dcQ1EcQmdQeUohktmgX
C6ViLtdrBYUbR1XjY4/PTxmvfDDG9Zo8hJ26XxS9YIhzxvEQHVUYyOgYYIr/HWik
LXDHAwa0lpnopBMM/PwxNTi13O+3R6rJnb3GqRdT46/eMwWzcj2E1q01PJQX3Mwl
/JoaFQ+HFVnkAipgNpfV8+mDSipxmCfU4EnEWDv98kMgr3D9+7HRglXOX+O6DdhR
WXO9GKwHDU140qCEl+EtmeU/y7zM110MUGDi7OQmK3OVdiedDlE=
=wRGo
-END PGP
Bug#920652: marked as done (ublock-origin: host list is not displayed, blocking does not seem to work)
Your message dated Mon, 28 Jan 2019 23:09:19 + with message-id and subject line Bug#920652: fixed in ublock-origin 1.18.2+dfsg-2 has caused the Debian Bug report #920652, regarding ublock-origin: host list is not displayed, blocking does not seem to work 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.) -- 920652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: webext-ublock-origin Version: 1.18.2+dfsg-1 Severity: important ublock origin version 1.18.2+dfsg-1 fails to display the list of blocked or existing hosts which you can see when you toggle "all". There is no indication that the addon blocks any content at the moment. All the menus appear to work though. I tried to debug the issue but could not find a solution hence the upload to experimental. When I use Firefox' debugging mode for addons, about:debugging, the console displays three errors: The first one is caused by a missing MIME entry for wasm files. This is Firefox bug https://bugzilla.mozilla.org/show_bug.cgi?id=1500710 You can add the line application/wasmwasm to /etc/mime.types and uBO's wasm modules will be loaded again. However that does not seem to address the issue at hand. Then I can see an Unchecked lastError value Error: Could not establish connection. Receiving end does not exist. webrequest.js:115 Finally there is also a TypeError Argument 1 of PrecompiledScript.executeInGlobal is not an Object ExtensionContent.jsm:497:18 I am at a loss at the moment. --- End Message --- --- Begin Message --- Source: ublock-origin Source-Version: 1.18.2+dfsg-2 We believe that the bug you reported is fixed in the latest version of ublock-origin, 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. Markus Koschany (supplier of updated ublock-origin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 23:14:43 +0100 Source: ublock-origin Architecture: source Version: 1.18.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Mozilla Extension Maintainers Changed-By: Markus Koschany Closes: 920652 Changes: ublock-origin (1.18.2+dfsg-2) unstable; urgency=medium . * Upload to unstable. * Drop do-not-open-sidebar-on-first-start.patch. Fixed upstream. * Reuse both flavors of webRequest wrapper in webext package. Thanks to Raymond Hill for the patch. (Closes: #920652) Checksums-Sha1: 4f5747a28e6e3c49da0d441f96aed0768c3645d3 2470 ublock-origin_1.18.2+dfsg-2.dsc a006740af81754b9370d86898e3cd1a0e7e4c6f3 37612 ublock-origin_1.18.2+dfsg-2.debian.tar.xz 40524b9081159890cae39d1a2993a938ef0cb763 7028 ublock-origin_1.18.2+dfsg-2_amd64.buildinfo Checksums-Sha256: 1b6c7769299ed2bb5b73b465e4d5d92311618ef35a3203225ec8e5e96af1a511 2470 ublock-origin_1.18.2+dfsg-2.dsc 44d0137640f08dd02c34a23c576a9c9f91d9dc205e182a424b4e93828b032abe 37612 ublock-origin_1.18.2+dfsg-2.debian.tar.xz ecf4fd53a8c589129a1166cb63db36d158186991a230d0ef27946240e0a31fe3 7028 ublock-origin_1.18.2+dfsg-2_amd64.buildinfo Files: 77340b859f4d035ad749d12cc14dbfb7 2470 web optional ublock-origin_1.18.2+dfsg-2.dsc c1329851674c1ba290050cc6d3d112e8 37612 web optional ublock-origin_1.18.2+dfsg-2.debian.tar.xz 70095423f6b3c3aa2f6093d6cc206540 7028 web optional ublock-origin_1.18.2+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlxPgEtfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkpdwP/0rqAAXQyPrfP7c8OZsrIYKhtumn7LJ75sjF SaMFafx3sJ9eusuDBFKGeOZVGJI7ZicAxj2CKnQylr0q+JieMmxvVJpwPVDHGrqp gpjC8kg5DougeRVi79209JD8BdkWxgDOnzXxRSfCM4qI01IkWVNJ2McTFxJ3lK9t CYbh4XCQgRxM9X1mam4U4dT+eAFRU87riNh/o85OH5wJUw64INx5jdO0VUGXhQ8T iyDnC5oHr0H+wbrCisjpKpJwSiARXBbhX1h8VfNpDyKRIgZfYzej+vbEZ1z33R+G NR9SM2QKCYBeA588P/mpy8morpPtERdCRkxbkfQgvkB6dVFzoIeEtAjBprOe5uUu ghoSgAhFQBdFJRuoJpwPXu1g7ciWg+cCUKK2OtakD00+EWocYp8FOZoR+u2uKO2m
Bug#920757: marked as done (please update package)
Your message dated Tue, 29 Jan 2019 01:04:39 + with message-id and subject line Bug#920757: fixed in social-auth-core 3.0.0-1 has caused the Debian Bug report #920757, regarding please update package 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.) -- 920757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: social-auth-core Version: 1.7.0-1 Severity: wishlist Current is 3.0, weblate needs at least 2.0. (I'm a team member and can update the package myself.) --- End Message --- --- Begin Message --- Source: social-auth-core Source-Version: 3.0.0-1 We believe that the bug you reported is fixed in the latest version of social-auth-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. W. Martin Borgert (supplier of updated social-auth-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 22:33:12 + Source: social-auth-core Binary: python3-social-auth-core Architecture: source all Version: 3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: W. Martin Borgert Description: python3-social-auth-core - This is the core component of the python-social-auth ecosystem Closes: 920757 Changes: social-auth-core (3.0.0-1) unstable; urgency=medium . * Team upload * New upstream version (Closes: #920757) . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Remove ancient X-Python-Version field Checksums-Sha1: 9a9e279c6748da622f8df6cd503ef5d90d4684d1 2090 social-auth-core_3.0.0-1.dsc 8335adeab5447488c726bf0ae8dc6d78bc2e2ce8 173055 social-auth-core_3.0.0.orig.tar.gz c7ba1af4a61302277c2a3c88878bc5a62f42c7e4 3244 social-auth-core_3.0.0-1.debian.tar.xz 203d4760ff38a21040d866ffc0c5037cb5feb8c0 81812 python3-social-auth-core_3.0.0-1_all.deb 01ff296e4f174a43fa73e0c87d457d550d49b757 6086 social-auth-core_3.0.0-1_amd64.buildinfo Checksums-Sha256: 20c6adad4c4bb346acd496a21cd46042e5dab85c5c2493f9833b768e0a8b900b 2090 social-auth-core_3.0.0-1.dsc d1b49c226a516e4fb66da37ebb721caccbab944d78aa603533c27d7d80546f9a 173055 social-auth-core_3.0.0.orig.tar.gz 5dcd498808efa04cc96ff418fa5dac38770f01b188b4b4a4768491d4f32f36e6 3244 social-auth-core_3.0.0-1.debian.tar.xz 99f3cd5aa14572123826525377676f6a8e7e191bb09f1222e4cbe148eca32c65 81812 python3-social-auth-core_3.0.0-1_all.deb 9cf58026acb4eb10349f0d236b8be34006ad04e2b98828d9fbe53eef153c259e 6086 social-auth-core_3.0.0-1_amd64.buildinfo Files: b80ed5884c903e822e8d84fe82c83e20 2090 python optional social-auth-core_3.0.0-1.dsc 50d894f17c1814de25ce7dd833d03cc6 173055 python optional social-auth-core_3.0.0.orig.tar.gz 9d0e3be4f246d6841c256d1661425f2c 3244 python optional social-auth-core_3.0.0-1.debian.tar.xz b0ceabcb708b5253c51feb360a34b481 81812 python optional python3-social-auth-core_3.0.0-1_all.deb 977c5dcaccb2ca0ae55ef726834ab9d2 6086 python optional social-auth-core_3.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAlxPo8sACgkQ4+Chwoa5 Y+rbNQ//ayhcNjPSxDFBTdvGOjZ+pvvW9rasfFzBU3JCNboZDk1/ZwGmC9g7b4C0 wa9Pxv9zjcJG2NXed2thF2mfB40yKqCgJoUN9SGPoBCXht2GwkIO3Q40MkPzRK13 qawz3Xj5G0oKiR5rRhkHbb2FlULZyKVr8lI7hluWl8PpFbuzMgYG2/GlmomvTclh 5wBR5LQKdtcRwLSHJ345nzCF03kANR6zEWt67FhP+k9qTjM2FsruFIlXxWHoOx2o 7ZMjEMXiqh3gyt2ZW6KMzlp9ip7FoNYWUapSUNJErQ+aPOhPXTDk7x/SCebyg3vd oAby8FLwppsQP9w23Qj+7zE9FQ1BnaLBt7CiN+vpxBUry6x71pPjISz9S1tOX9iH Kgvv6C12+Qp0z85jLBLtcHtsMapNOUN0fIeUQoE6Yk/9RCVlN2HtQbpw/bAP9uXd zhtg55wZBCpwKbF8vPynpdAzaEya0jROAIGR7sE1UOVQXjrkLNkxPiqWOhFswnhm zem/1Bs7Mq/Q7UsAN9xhCQmWzOwAnEJIC6Ox4wNNMXAUkFyRkhDonaYJR67gSEFn Rh+cRaHtusSQYKVT0Biugnx0e1AWZSzi7qd1orNM+34AKdkzRJeB5krbKkMAacik 8WUG6NBncb8lOwAgETY+q7WVdZplMZix3NEjovY0+oN5Q9lBRHE= =RcIo -END PGP SIGNATURE End Message ---
Bug#920703: marked as done (RM: mysql-connector-java -- ROM; replaced by mariadb-connector-java)
Your message dated Tue, 29 Jan 2019 01:06:36 + with message-id and subject line Bug#920703: Removed package(s) from unstable has caused the Debian Bug report #920703, regarding RM: mysql-connector-java -- ROM; replaced by mariadb-connector-java 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.) -- 920703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal Dear ftp team, please remove mysql-connector-java from Debian. It was replaced by mariadb-connector-java which is a drop-in-replacement. No other package depends on it anymore. See also https://bugs.debian.org/912916 Regards, Markus --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libmysql-java | 5.1.45-1 | all mysql-connector-java | 5.1.45-1 | source --- Reason --- ROM; replaced by mariadb-connector-java -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/920703 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#920721: marked as done (RM: requestpolicy -- RoQA; Broken with Firefox Quantum, unmaintained)
Your message dated Tue, 29 Jan 2019 01:07:06 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #920721, regarding RM: requestpolicy -- RoQA; Broken with Firefox Quantum, unmaintained 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.) -- 920721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal Please remove requestpolicy, it's broken with Firefox >= 57 and hasn't seen an upload for 2.5 years. Cheers, Moritz --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: requestpolicy | 1.0.0~beta12.3+dfsg-1 | source xul-ext-requestpolicy | 1.0.0~beta12.3+dfsg-1 | all --- Reason --- RoQA; Broken with Firefox Quantum, unmaintained -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/920721 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#920729: marked as done (RM: apmd -- RoQA; Broken, unmaintained)
Your message dated Tue, 29 Jan 2019 01:07:55 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #920729, regarding RM: apmd -- RoQA; Broken, unmaintained 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.) -- 920729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal Please remove apmd from unstable, it's broken (891698) and the last maintainer upload was in 2014. Cheers, Moritz --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: apmd | 3.2.2-15 | source apmd | 3.2.2-15+b2 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x libapm-dev | 3.2.2-15+b2 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x libapm1 | 3.2.2-15+b2 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x xapm | 3.2.2-15+b2 | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; Broken, unmaintained -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/920729 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#828836: marked as done (libmysql-java: ClassNotFound exception IF running in a v8 JVM)
Your message dated Tue, 29 Jan 2019 01:06:42 +
with message-id
and subject line Bug#920703: Removed package(s) from unstable
has caused the Debian Bug report #828836,
regarding libmysql-java: ClassNotFound exception IF running in a v8 JVM
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.)
--
828836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmysql-java
Version: 5.1.39-1~deb7u1
Severity: important
Tags: patch
Dear Maintainer,
The latest backport of libmysql-java in [security] crashes with a
ClassNotFound exception, *IF* running under a v8 virtual machine.
(I'm using a wheezy backport of OpenJDK-8 which is available here:
http://download.opensuse.org/repositories/home:/ods/Debian_7.0/ )
I investigated the source package and found the reason:
In several locations of the generic code, there is code like
this (pseudo-code follows):
if (Util.isJdbc42()) {
... invoke JDBC42 classes
} else {
... use older implementation specifics
}
The method Util.isJdbc4() returns true, if running under a v8 JVM.
In order to *COMPLETELY* disable invocation of JDBC42 specific code, the
method Util.isJdbc4() should *ALWAYS* return false.
The following patch fixes that:
=== SNIP =
--- a/src/com/mysql/jdbc/Util.java 2016-06-28 11:05:51.065799452 +0200
+++ b/src/com/mysql/jdbc/Util.java 2016-06-28 11:07:34.545802936 +0200
@@ -62,7 +62,7 @@
private static boolean isJdbc4;
-private static boolean isJdbc42;
+private static boolean isJdbc42 = false;
private static int jvmVersion = -1;
@@ -76,13 +76,6 @@
isJdbc4 = false;
}
-try {
-Class.forName("java.sql.JDBCType");
-isJdbc42 = true;
-} catch (Throwable t) {
-isJdbc42 = false;
-}
-
String jvmVersionString = System.getProperty("java.version");
int startPos = jvmVersionString.indexOf('.');
int endPos = startPos + 1;
=== SNIP =
Cheers
-Fritz
-- System Information:
Debian Release: 7.10
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- a/src/com/mysql/jdbc/Util.java 2016-06-28 11:05:51.065799452 +0200
+++ b/src/com/mysql/jdbc/Util.java 2016-06-28 11:07:34.545802936 +0200
@@ -62,7 +62,7 @@
private static boolean isJdbc4;
-private static boolean isJdbc42;
+private static boolean isJdbc42 = false;
private static int jvmVersion = -1;
@@ -76,13 +76,6 @@
isJdbc4 = false;
}
-try {
-Class.forName("java.sql.JDBCType");
-isJdbc42 = true;
-} catch (Throwable t) {
-isJdbc42 = false;
-}
-
String jvmVersionString = System.getProperty("java.version");
int startPos = jvmVersionString.indexOf('.');
int endPos = startPos + 1;
--- a/src/com/mysql/jdbc/Util.java 2016-06-28 11:05:51.065799452 +0200
+++ b/src/com/mysql/jdbc/Util.java 2016-06-28 11:07:34.545802936 +0200
@@ -62,7 +62,7 @@
private static boolean isJdbc4;
-private static boolean isJdbc42;
+private static boolean isJdbc42 = false;
private static int jvmVersion = -1;
@@ -76,13 +76,6 @@
isJdbc4 = false;
}
-try {
-Class.forName("java.sql.JDBCType");
-isJdbc42 = true;
-} catch (Throwable t) {
-isJdbc42 = false;
-}
-
String jvmVersionString = System.getProperty("java.version");
int startPos = jvmVersionString.indexOf('.');
int endPos = startPos + 1;
--- src/com/mysql/jdbc/Util.java.orig 2016-06-28 11:05:51.065799452 +0200
+++ src/com/mysql/jdbc/Util.java 2016-06-28 11:07:34.545802936 +0200
@@ -62,7 +62,7 @@
private static boolean isJdbc4;
-private static boolean isJdbc42;
+private static boolean isJdbc42 = false;
private static int jvmVersion = -1;
@@ -76,13 +76,6 @@
isJdbc4 = false;
}
-try {
-Class.forName("java.sql.JDBCType");
-isJdbc42 = true;
-} catch (Throwable t) {
-isJdbc42 = false;
-}
-
String jvmVersionString = System.getProperty("java.version");
int startPos =
Bug#135557: marked as done (libapm1: should have bsd support)
Your message dated Tue, 29 Jan 2019 01:08:09 +
with message-id
and subject line Bug#920729: Removed package(s) from unstable
has caused the Debian Bug report #135557,
regarding libapm1: should have bsd 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.)
--
135557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=135557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapm1
Version: 3.0.2-1.9
Severity: wishlist
This should really be a cross-platform library with support the the
BSD's, which have very similar apm reporting methods after all. I
have just ripped bsd support out of wmbattery and made it use libapm,
and I will just detail how that used to work in wmbattery. It will
probably need some adpation to go in libapm.
Kevin Christen did the openbsd port of
wmbattery, and Motoyuki Kasahara did the freebsd
port.
Here is how the bsd support works:
1. Configure checks. If this header exists then we're on a bsd system.
dnl NetBSD and OpenBSD need apmvar.h
AC_CHECK_HEADERS(i386/apmvar.h)
2. Header files.
#ifdef HAVE_MACHINE_APM_BIOS_H /* for FreeBSD */
#include
#endif
#ifdef HAVE_I386_APMVAR_H /* for NetBSD and OpenBSD */
#include
#endif
3. File to read apm info from. If there is a /dev/apm, use it on bsd
systems.
dnl Checks for the apm device other than /proc/apm.
AC_CHECK_FILES(/dev/apm)
#ifdef HAVE__DEV_APM
#define APM_PROC "/dev/apm"
#else
#define APM_PROC "/proc/apm"
#endif
4. Code.
#if defined (HAVE_MACHINE_APM_BIOS_H) || defined (HAVE_I386_APMVAR_H) /* BSD */
int apm_read(apm_info *i) {
int fd;
#ifdef HAVE_MACHINE_APM_BIOS_H /* FreeBSD */
unsigned long request = APMIO_GETINFO;
struct apm_info info;
#else /* NetBSD or OpenBSD */
unsigned long request= APM_IOC_GETPOWER;
struct apm_power_info info;
#endif
if ((fd = open(apm_status_file, O_RDONLY)) == -1) {
return 1;
}
if (ioctl(fd, request, ) == -1) {
return 1;
}
close(fd);
#ifdef HAVE_MACHINE_APM_BIOS_H /* FreeBSD */
i->ac_line_status = info.ai_acline;
i->battery_status = info.ai_batt_stat;
i->battery_flags = (info.ai_batt_stat == 3) ? 8: 0;
i->battery_percentage = info.ai_batt_life;
i->battery_time = info.ai_batt_time;
i->using_minutes = 0;
#else /* NetBSD or OpenBSD */
i->ac_line_status = info.ac_state;
i->battery_status = info.battery_state;
i->battery_flags = (info.battery_state == 3) ? 8: 0;
i->battery_percentage = info.battery_life;
i->battery_time = info.minutes_left;
i->using_minutes = 1;
#endif
return 0;
}
--- End Message ---
--- Begin Message ---
Version: 3.2.2-15+rm
Dear submitter,
as the package apmd has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/920729
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#920233: marked as done (evince: Add Illustrator (.ai) files to AppArmor profile)
Your message dated Tue, 29 Jan 2019 01:04:15 + with message-id and subject line Bug#920233: fixed in evince 3.30.2-3 has caused the Debian Bug report #920233, regarding evince: Add Illustrator (.ai) files to AppArmor profile 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.) -- 920233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: evince Version: 3.30.2-2 Severity: minor Dear Maintainer, Please add support for Adobe Illustrator '.ai' files to evince's AppArmor profile. Illustrator files are essentially either PDF or EPS files with a '.ai' file extension. Evince is able to open them since version 3.26. Since this extension is not listed in the AppArmor profile, evince cannot open them if they are outside the $HOME directory. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages evince depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii evince-common3.30.2-2 ii gsettings-desktop-schemas3.28.1-1 ii libatk1.0-0 2.30.0-2 ii libc62.28-5 ii libcairo-gobject21.16.0-2 ii libcairo21.16.0-2 ii libevdocument3-4 3.30.2-2 ii libevview3-3 3.30.2-2 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libglib2.0-0 2.58.2-4 ii libgnome-desktop-3-173.30.2-4 ii libgtk-3-0 3.24.3-1 ii libnautilus-extension1a 3.30.5-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libsecret-1-00.18.7-1 ii shared-mime-info 1.10-1 Versions of packages evince recommends: ii dbus-user-session [default-dbus-session-bus] 1.12.12-1 ii dbus-x11 [dbus-session-bus] 1.12.12-1 Versions of packages evince suggests: ii gvfs 1.38.1-2+b1 ii nautilus-sendto 3.8.6-3 ii poppler-data 0.4.9-2 pn unrar -- no debconf information --- End Message --- --- Begin Message --- Source: evince Source-Version: 3.30.2-3 We believe that the bug you reported is fixed in the latest version of evince, 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. Jeremy Bicha (supplier of updated evince package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Jan 2019 19:48:11 -0500 Source: evince Binary: evince evince-common libevdocument3-4 libevview3-3 libevince-dev gir1.2-evince-3.0 Architecture: source Version: 3.30.2-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Description: evince - Document (PostScript, PDF) viewer evince-common - Document (PostScript, PDF) viewer - common files gir1.2-evince-3.0 - GObject introspection data for the evince libraries libevdocument3-4 - Document (PostScript, PDF) rendering library libevince-dev - Document (PostScript, PDF) rendering library - development files libevview3-3 - Document (PostScript, PDF) rendering library - Gtk+ widgets Closes: 920233 Changes: evince (3.30.2-3) unstable; urgency=medium . [ Jason Crain ] * debian/apparmor-profile: Allow Illustrator .ai files (Closes: #920233) Checksums-Sha1: 28d8f52c15a946be6c542198c84c76ed0118b204 3038 evince_3.30.2-3.dsc aa386beb530983cbbdc36bc6083f54c03cab3863
Bug#853992: marked as done (xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions)
Your message dated Tue, 29 Jan 2019 01:07:13 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #853992, regarding xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions 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.) -- 853992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-requestpolicy Version: 1.0.0~beta12.3+dfsg-1 Severity: normal Dear Maintainer, First of all thank you for taking care of xul-ext-requestpolicy for so long. Was just browsing today and saw that 1.0beta12.4 was introduced few months back. The only addition according to the changelog https://github.com/RequestPolicyContinued/requestpolicy/blob/dev-1.0/ChangeLog.md is being compatible with WebExtensions which Mozilla is going to come up in the next few releases. https://wiki.mozilla.org/WebExtensions If possible, please update it so we are ready when the new Firefox arrives. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (600, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xul-ext-requestpolicy depends on: ii firefox 50.1.0-1 ii firefox-esr 45.7.0esr-1 ii iceweasel 45.7.0esr-1 ii libjs-jquery 3.1.1-2 xul-ext-requestpolicy recommends no packages. xul-ext-requestpolicy suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 --- End Message --- --- Begin Message --- Version: 1.0.0~beta12.3+dfsg-1+rm Dear submitter, as the package requestpolicy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920721 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#907712: marked as done (src:requestpolicy: please package upstream version 1.0.beta13.2)
Your message dated Tue, 29 Jan 2019 01:07:13 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #907712, regarding src:requestpolicy: please package upstream version 1.0.beta13.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:requestpolicy Version: 1.0.0~beta12.3+dfsg-1 Severity: wishlist according to https://github.com/RequestPolicyContinued/requestpolicy/releases a new beta release has been available for nearly a year. In git (https://github.com/RequestPolicyContinued/requestpolicy) there are many new commits on top of v1.0.beta13.2 as well, if you wanted to try to make an experimental package from a git snapshot. --dkg -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 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) --- End Message --- --- Begin Message --- Version: 1.0.0~beta12.3+dfsg-1+rm Dear submitter, as the package requestpolicy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920721 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#912916: marked as done (mysql-connector-java: removal from Debian)
Your message dated Tue, 29 Jan 2019 01:06:42 + with message-id and subject line Bug#920703: Removed package(s) from unstable has caused the Debian Bug report #912916, regarding mysql-connector-java: removal from Debian 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.) -- 912916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mysql-connector-java X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for mysql-connector-java. CVE-2018-3258[0]: | Vulnerability in the MySQL Connectors component of Oracle MySQL | (subcomponent: Connector/J). Supported versions that are affected are | 8.0.12 and prior. Easily exploitable vulnerability allows low | privileged attacker with network access via multiple protocols to | compromise MySQL Connectors. Successful attacks of this vulnerability | can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.8 | (Confidentiality, Integrity and Availability impacts). CVSS Vector: | (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). 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-2018-3258 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3258 Please adjust the affected versions in the BTS as needed. Regards, Markus signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 5.1.45-1+rm Dear submitter, as the package mysql-connector-java has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920703 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#118797: marked as done (Please handle multiple batteries (e.g., on Sony VAIO))
Your message dated Tue, 29 Jan 2019 01:08:09 +
with message-id
and subject line Bug#920729: Removed package(s) from unstable
has caused the Debian Bug report #118797,
regarding Please handle multiple batteries (e.g., on Sony VAIO)
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.)
--
118797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=118797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apmd
Version: 3.0.1-1
Severity: normal
- Forwarded message from Daniel Caujolle-Bert
-
Date: Thu, 08 Nov 2001 22:46:08 +0100
From: Daniel Caujolle-Bert
Subject: [PATCH] apmd don't see LOW_BATTERY on my VAIO
To: Avery Pennarun
Reply-To: segfa...@club-internet.fr
Hi Avery,
Well, this is another patch. As title said, i'm unable to
use proxy_cmd for battery change (i haven't track other events since
i only need this one). Don't ask me why 3.0final won't work, but if
you want, i can made some tests for you.
Cheers.
--
73's de Daniel, F1RMB.
-=- Daniel Caujolle-Bert -=- segfa...@club-internet.fr -=-
-=- f1...@f1rmb.ampr.org (AMPR NET) -=-
--- apmd/apmd.c Wed Dec 8 00:01:09 1999
+++ apmd.sony/apmd.cThu Nov 8 22:33:26 2001
@@ -603,6 +603,7 @@
double rate;
static int last_battery_status = 0;
+static int last_battery_status2 = 0;
static int last_ac_status = -1;
ADEBUG(4, "0x%04x\n", event);
@@ -633,6 +634,7 @@
synthetic_low_battery:
apmd_call_proxy(event, apmi);
last_battery_status = 1;
+ last_battery_status2 = 1;
apmd_low_battery(event, apmi);
break;
#ifdef APM_CAPABILITY_CHANGE
@@ -710,6 +712,11 @@
sprintf(msg, "Battery warning (%d%% %s)",
apmi->battery_percentage, apm_time_nosec(apmd_time(apmi)));
warn(msg);
+
+ if (last_battery_status != 1 && last_battery_status2 != 1) {
+ event = APM_LOW_BATTERY;
+ goto synthetic_low_battery;
+ }
/* ... if that's all we're doing, finish */
if (!logflag)
return;
- End forwarded message -
--- End Message ---
--- Begin Message ---
Version: 3.2.2-15+rm
Dear submitter,
as the package apmd has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/920729
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#870607: marked as done (xul-ext-requestpolicy: Please update to 1.0.beta13.0)
Your message dated Tue, 29 Jan 2019 01:07:13 + with message-id and subject line Bug#920721: Removed package(s) from unstable has caused the Debian Bug report #870607, regarding xul-ext-requestpolicy: Please update to 1.0.beta13.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 870607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-requestpolicy Version: 1.0.0~beta12.3+dfsg-1 Severity: normal Dear Maintainer, While I had already put up a bug-report to update it to 1.0.beta12.4 I now beseech you to update it to Version 1.0.beta13.0 Here is a brief update of the changes in this release (taken from upstream) https://github.com/RequestPolicyContinued/requestpolicy/blob/dev-1.0/ChangeLog.md#version-10beta130 Version 1.0.beta13.0 improvements When the "allow same domain" setting is set to false, allow http:80 to https:443 if the host is the same. DNS Prefetching: Besides network.dns.disablePrefetch, also take into account the network.dns.disablePrefetchFromHTTPS setting (#795) bugfixes Redirections made by Add-Ons via "nsIHttpChannel.redirectTo()" are now intercepted, and visible in the request log. (#775) new "internal request" whitelist entries (due to #783): view-source CSS file (#788) NoScript icon for blocked flash content (#788) pluginproblem URI (#797, #788) CSS files when viewing images, videos or text files directly in a tab When adding an allow rule via the redirection notification bar the redirection should actually be performed (#808). The menu does not open when the RP menu icon (flag) hasn't been visible in the current window yet (#815). Add-on compatibility: NewsFox showed a redirection notification when clicking on a news' title (#707) Browser compatibility: Firefox Accounts (#687) updated translations es-ES: #790 new translations pl: #806 minor changes Don't change the font color in RP's context menu entry (#31). Ignore clicks on [no origin] in the menu (#761). In default-allow mode, add the menu option "Block all requests from " (#559). Look forward to seeing the new version in Debian buster cycle soonish. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-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 xul-ext-requestpolicy depends on: ii firefox 54.0-2 ii firefox-esr 52.2.0esr-2 ii iceweasel 52.2.0esr-2 ii libjs-jquery 3.1.1-2 xul-ext-requestpolicy recommends no packages. xul-ext-requestpolicy suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 --- End Message --- --- Begin Message --- Version: 1.0.0~beta12.3+dfsg-1+rm Dear submitter, as the package requestpolicy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920721 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#100026: marked as done (Please document the apmlib API)
Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #100026, regarding Please document the apmlib API 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.) -- 100026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apmd Version: 3.0.1-1 Severity: wishlist There are currently no docs at all for apmlib. Except comments. :-) It would be nice if some basic documentation could be written, suitable to be put in a binary package. Just the existing comments and function prototypes would be a good start. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux silk 2.4.5 #1 Thu Jun 7 13:50:09 EDT 2001 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages apmd depends on: ii libc6 2.2.3-5GNU C Library: Shared libraries an ii libxaw7 4.0.3-4X Athena widget set library ii xlibs 4.0.3-4X Window System client libraries --- End Message --- --- Begin Message --- Version: 3.2.2-15+rm Dear submitter, as the package apmd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920729 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#228615: marked as done (please split out apmd_proxy)
Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #228615, regarding please split out apmd_proxy 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.) -- 228615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=228615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apmd Severity: wishlist X-Debbugs-CC: debian-powe...@lists.debian.org Hi, I'd be nice if I could use apmd_proxy from pmud (power management daemon on power mac hardware) since most programs care about apmd only. This would avoid code duplication and improve power management on macintosh hardware. Since pmud conflicts with apmd, apmd_proxy can't be called from pmud's scripts. Would you accept patches to split out apmd_proxy into a apmd-util package? Cheers, -- Guido -- System Information: Debian Release: testing/unstable Architecture: powerpc Kernel: Linux bogon 2.4.24-ben1-albook12 #1 Fri Jan 16 15:55:57 CET 2004 ppc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 --- End Message --- --- Begin Message --- Version: 3.2.2-15+rm Dear submitter, as the package apmd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920729 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#134595: marked as done (apmd: please make /usr/bin/apm suid root)
Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #134595, regarding apmd: please make /usr/bin/apm suid root 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.) -- 134595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apmd Version: 3.0.2-1.5 Severity: wishlist Could you please make /usr/bin/apm suid root? Its owner of course should be something like root.apm in that case, and the program should not be executable for others. This would make it possible for normal users (that are in the apm group) to suspend a laptop. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux kalypso 2.4.17 #3 Sun Feb 17 21:51:03 CET 2002 i686 Locale: LANG=en_GB, LC_CTYPE=nl_NL@euro Versions of packages apmd depends on: ii debconf 1.0.26 Debian configuration management sy ii libc6 2.2.5-3GNU C Library: Shared libraries an ii libxaw7 4.1.0-14 X Athena widget set library ii xlibs 4.1.0-14 X Window System client libraries --- End Message --- --- Begin Message --- Version: 3.2.2-15+rm Dear submitter, as the package apmd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920729 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#222759: marked as done (apmd: Curious messages from "apm" command)
Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #222759, regarding apmd: Curious messages from "apm" command 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.) -- 222759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: apmd: Foo Package: apmd Version: 3.0.2-1.19 Severity: wishlist xerxes:~# apm AC off-line, battery status high: 1% (0:00:00) It reported this right before the batteries ran out of juice. "battery status high"? (-: Maybe the "high"/"low"/whatever thing needs to be fixed. -- System Information Debian Release: 3.0 Kernel Version: Linux xerxes 2.4.22 #10 Tue Dec 2 07:59:37 EST 2003 i686 GNU/Linux Versions of the packages apmd depends on: ii debconf1.3.14 Debian configuration management system ii libapm13.0.2-1.19 Library for interacting with APM driver in k ii libc6 2.3.2-7GNU C Library: Shared libraries and Timezone ii powermgmt-base 1.6Common utils and configs for power managemen --- End Message --- --- Begin Message --- Version: 3.2.2-15+rm Dear submitter, as the package apmd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920729 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#231238: marked as done (apmd 3.2.1-2 suspend the system as soon as it has not been used for a few minutes)
Your message dated Tue, 29 Jan 2019 01:08:09 + with message-id and subject line Bug#920729: Removed package(s) from unstable has caused the Debian Bug report #231238, regarding apmd 3.2.1-2 suspend the system as soon as it has not been used for a few minutes 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.) -- 231238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=231238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apmd Version: 3.2.0-8 Severity: normal apmd suspends my laptop as soon as I stop using it for a few minutes. This bug report is about apmd 3.2.1-2. I have reinstalled a previous version to get rid of this bug. This started with the latest apmd update. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.24 Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro Versions of packages apmd depends on: ii debconf 1.4.8Debian configuration management sy hi libapm1 3.2.0-8 Library for interacting with APM d ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii powermgmt-base 1.17 Common utils and configs for power -- debconf information excluded --- End Message --- --- Begin Message --- Version: 3.2.2-15+rm Dear submitter, as the package apmd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/920729 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#918370: marked as done (Krita crashes with Qt 5.11.3 using tablet input)
Your message dated Mon, 28 Jan 2019 22:53:39 -0300 with message-id <22461097.NLPhRp2Yoe@tonks> and subject line Really closing. has caused the Debian Bug report #918370, regarding Krita crashes with Qt 5.11.3 using tablet input 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.) -- 918370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqt5gui5 Version: 5.11.3+dfsg-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Start krita use the use the huion pencil * What exactly did you do (or not do) that was effective (or ineffective)? Use the huion tablet pencil in krita. * What was the outcome of this action? Crash backtrace below. [New Thread 0x7fff8dffe700 (LWP 4662)] free(): double free detected in tcache 2 Thread 1 "krita" received signal SIGABRT, Aborted. 0x74baa85b in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread apply all backtrace Thread 36 (Thread 0x7fff8dffe700 (LWP 4662)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 35 (Thread 0x7fff8d7fd700 (LWP 4661)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 34 (Thread 0x7fff8cffc700 (LWP 4660)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 33 (Thread 0x7fff5bff4700 (LWP 4659)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 28 (Thread 0x7fffb0eef700 (LWP 4654)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 --Type for more, q to quit, c to continue without paging-- Thread 27 (Thread 0x7fffb1ef1700 (LWP 4653)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from
Bug#911151: marked as done (python-boto3: Please update to newer upstream version)
Your message dated Mon, 28 Jan 2019 23:38:31 + with message-id and subject line Bug#911151: fixed in python-boto3 1.9.86-1 has caused the Debian Bug report #911151, regarding python-boto3: Please update to newer upstream version 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.) -- 911151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-boto3 Version: 1.7.55-1 Severity: minor Dear Maintainer, please update python-boto3 to a newer upstream version. The current newest ist 1.9.24 and contains a lot of aws api changes. Regards Sascha -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages python-boto3 depends on: ii python 2.7.15-3 ii python-botocore1.12.16+repack-1 ii python-jmespath0.9.3-1 ii python-requests2.18.4-2 ii python-s3transfer 0.1.13-1 ii python-six 1.11.0-2 python-boto3 recommends no packages. python-boto3 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python-boto3 Source-Version: 1.9.86-1 We believe that the bug you reported is fixed in the latest version of python-boto3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 911...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander GQ Gerasiov (supplier of updated python-boto3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Jan 2019 02:07:32 +0300 Source: python-boto3 Binary: python-boto3 python3-boto3 Architecture: source Version: 1.9.86-1 Distribution: unstable Urgency: medium Maintainer: Eric Evans Changed-By: Alexander GQ Gerasiov Description: python-boto3 - Python interface to Amazon's Web Services - Python 2.x python3-boto3 - Python interface to Amazon's Web Services - Python 3.x Closes: 911151 Changes: python-boto3 (1.9.86-1) unstable; urgency=medium . * d/control: Update VCS fields. * New upstream version 1.9.86 (Closes: #911151) * do-not-use-vendored-code.patch: Refreshed. * d/rules: Remove DEB_BUILD_OPTIONS=nocheck. * d/control: Bump Standards-Version (no changes needed). Checksums-Sha1: ddca86c4b6379d36a9892a3761d0f71a6d5972d0 1780 python-boto3_1.9.86-1.dsc c6cfc39749e8ba680f0053885f26ea60fdc44367 251853 python-boto3_1.9.86.orig.tar.gz 252d38ae4cf5dfa319e15f853c59ae9acc8ba0b8 2528 python-boto3_1.9.86-1.debian.tar.xz 87f44ae8510f87d6199a3217d7d4fd49e647f4c4 6678 python-boto3_1.9.86-1_source.buildinfo Checksums-Sha256: 581024a571c300271edbb81924e77ffd9844fbe9c677afb444db5aa7d49da6ab 1780 python-boto3_1.9.86-1.dsc 5a47286ebc4f2b0583ff8096acb14033d1a910610c29fb6dc9d4772e1c06bc87 251853 python-boto3_1.9.86.orig.tar.gz f81fa5f1b2840fed6aa7d0553996ba52d83151d03b5e6059d96566527f201ac5 2528 python-boto3_1.9.86-1.debian.tar.xz ba6cb49504645bcf8de20308729855cad8eb81d3fb54552380d4bdca0a4da3dc 6678 python-boto3_1.9.86-1_source.buildinfo Files: 849a3b52af7b09a6baba80de6a251ce3 1780 python optional python-boto3_1.9.86-1.dsc 2544290ec983d10343b5425515c15ca8 251853 python optional python-boto3_1.9.86.orig.tar.gz 975065694a0c421c6b800aa112cbc9c7 2528 python optional python-boto3_1.9.86-1.debian.tar.xz 547857558569194c7f6581227f813817 6678 python optional python-boto3_1.9.86-1_source.buildinfo -BEGIN PGP SIGNATURE- iQFCBAEBCgAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAlxPjGIOHGdxQGRlYmlh bi5vcmcACgkQyofp6CqsM/FKEggAjzQ2cSJn405mtUUZY9DTsfARxJbIuPLfqnEJ KlUJtYdFxStsKaTwjhxom9CPTA6W39Akfn596xw09oG0bd7R2VPR26n9TRQErBgk kId5ZEnVn8L1vCsn92B9C3A3s0JfTX3Qc0GiOnZq1GhbYk6L0QXpW8q2oHYI6DZZ sKjG3Dnw3s4wRimlJRVucgSTJeaK8jn4xyEHq+JnbtZjchbQ58vDvesyw5bUQZ9g CRVxwQhgXU3rIEjHBsJYPKG8g3HeVTYArSINOCapuqWghotPB1aWU2ytf1VNYWIw jlsNG5M/Kn9w+GH1EUe5RHfdP3rbM3wnR2+MkgEpZ6eXSrvF3g==
Bug#913944: marked as done (flare-game: Loosing skill on load / level up / death)
Your message dated Tue, 29 Jan 2019 00:04:44 + with message-id and subject line Bug#913944: fixed in flare-engine 1.09.01-1 has caused the Debian Bug report #913944, regarding flare-game: Loosing skill on load / level up / death 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.) -- 913944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flare-game Version: 1.07-1 Severity: normal Tags: upstream In 1.07, when wearing an item that gives a skill bonus, this bonus is subtracted permanently from a random skill each time a character levels up, dies or a savegame is loaded. This makes such items pretty much unuseable; for unsuspecting players they can quickly make a character equipped with such items unplayable. This bug is fixed in the 1.08 upstream release. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flare-game depends on: ii flare-engine 1.07-1 ii fonts-liberation 1:1.07.4-8 ii ttf-unifont 1:11.0.02-1 flare-game recommends no packages. flare-game suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: flare-engine Source-Version: 1.09.01-1 We believe that the bug you reported is fixed in the latest version of flare-engine, 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. Manuel A. Fernandez Montecelo (supplier of updated flare-engine package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Jan 2019 00:24:23 +0100 Source: flare-engine Architecture: source Version: 1.09.01-1 Distribution: unstable Urgency: medium Maintainer: Manuel A. Fernandez Montecelo Changed-By: Manuel A. Fernandez Montecelo Closes: 913944 Changes: flare-engine (1.09.01-1) unstable; urgency=medium . * New upstream release (Closes: #913944) * d/copyright, d/watch: Update upstream URLs * d/copyright: use https in format URL * Bump Policy Standards-Version to 4.3.0 (no changes needed) Checksums-Sha1: 9c56fe834c39bd73221f1e0aae30eb66fcac401c 2046 flare-engine_1.09.01-1.dsc bd471274287dceaf9ae9d95b0aac541f6d244b15 3903036 flare-engine_1.09.01.orig.tar.xz e8e299a33080cc62ed10aa9723415bc474125876 12432 flare-engine_1.09.01-1.debian.tar.xz f2867a76a57b67c908c13f7ca361161cc5bb257c 12111 flare-engine_1.09.01-1_amd64.buildinfo Checksums-Sha256: de204ebd7d603557ee2dbcd29290311c7bbe14e96404db7f23eb822d2dd9114e 2046 flare-engine_1.09.01-1.dsc 4cd48759f79f3b80a087656e4aa88053d8818650a875cae9d62b4998faa5030b 3903036 flare-engine_1.09.01.orig.tar.xz 89b06f5f7b4057853e3b5ee16776b0180a72bf4e37c7711d025a32d0f3fb892c 12432 flare-engine_1.09.01-1.debian.tar.xz 33318d8950005d2e304f858022a787b6702da4f05dbeb78de0fa3c3b83950312 12111 flare-engine_1.09.01-1_amd64.buildinfo Files: 71b40f8ae9b330ee9b491715a4c0af79 2046 games optional flare-engine_1.09.01-1.dsc 8162b00a0b8c2f16f9b31bfd0048ed14 3903036 games optional flare-engine_1.09.01.orig.tar.xz 44c720eece3f8d1cc478027e1bbafcf0 12432 games optional flare-engine_1.09.01-1.debian.tar.xz 3dbfc07bfeb87ec89e134374a51945c2 12111 games optional flare-engine_1.09.01-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEKo6AUFxIYphDDdCTf3YGpEXcqA4FAlxPktoQHG1hZm1AZGVi aWFuLm9yZwAKCRB/dgakRdyoDptkEAC0iaqqcG6iFpDxx1Qx5RgknHzd3So8qv/x QdKZJAWIq7gxkpsX6jgd6DcEloHJeurRudaVsHGafrj7xwRwnxT49kqG7E8+KUuH NKD1jc08UvxjHO2XUlxUg660VYIf5Ctl2Xi/9gr7tKR9GPOvmwCKwtAvhlEAOTXL plj823uQDKN5BBvE9/gZFgwrW3lj1z68sZ46TjSz0cLd8l5RSBkMF9B9iqB0Dcjv TlHWDNYhl8jSnij0lkPqyqU7X6iC2HEi9V3/YHlZoxSI8WB97dwzDy9dbKxTD6mm 29SVcZ1DsUYFj7s0HoD/G83fDU68EvUZ1Bq8pvytA+a9Uv6gdfDALxt3V+bL/+1P
Bug#918814: marked as done (dot2tex: FTBFS with Sphinx 1.8: No module named pngmath)
Your message dated Tue, 29 Jan 2019 05:19:11 + with message-id and subject line Bug#918814: fixed in dot2tex 2.9.0-3 has caused the Debian Bug report #918814, regarding dot2tex: FTBFS with Sphinx 1.8: No module named pngmath to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dot2tex Version: 2.9.0-2.1 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.8 Dear Maintainer, dot2tex fails to build with Sphinx 1.8, currently available in experimental: /usr/bin/make -C docs/ html make[2]: Entering directory '/<>/docs' sphinx-build -b html -d _build/doctrees . _build/html Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath) The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1] in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which also has SVG support in addition to PNG. To me it looks like this extension is unused anyway: there are no “.. math::” directives or “:math:” roles, and the binary package does not have any generated PNG images. So maybe this extension can be simply removed from extensions in conf.py. [1]: https://github.com/sphinx-doc/sphinx/pull/4702 [2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: dot2tex Source-Version: 2.9.0-3 We believe that the bug you reported is fixed in the latest version of dot2tex, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated dot2tex 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: Mon, 28 Jan 2019 22:39:29 -0500 Source: dot2tex Binary: dot2tex Architecture: source all Version: 2.9.0-3 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Description: dot2tex- Graphviz to LaTeX converter Closes: 918814 Changes: dot2tex (2.9.0-3) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/watch: Use https protocol . [ Sandro Tosi ] * debian/patches/sphinx-1.8-gh-63.patch - fix FTBFS with sphinx 1.8 by removing pngmath extension; Closes: #918814 * debian/control - bump Standards-Version to 4.3.0 (no changes needed) * debian/copyright - extend packaging copyright years Checksums-Sha1: 92e0b44819b63050242173773fea2d2ac9b2cac4 2012 dot2tex_2.9.0-3.dsc 858be9f0f9746214b2e2cd388a419023bba5ce6a 6728 dot2tex_2.9.0-3.debian.tar.xz 5cf13ad64d17ebf50b89132a89ad34cf1103740a 333432 dot2tex_2.9.0-3_all.deb b5937a6e601e4737a55d00d4dea7c257a0a6afc1 8168 dot2tex_2.9.0-3_amd64.buildinfo Checksums-Sha256: baa52bc233390d4aa88423df247290b778e3c567524f5294622732d4f4e75f46 2012 dot2tex_2.9.0-3.dsc 8451dffdaad8e12616a891dd9b0f5532b4c924081cae6feab4cd631deaf285f5 6728 dot2tex_2.9.0-3.debian.tar.xz 623e39a91aca2acecafaa9b10c65f85353eb5d77af0c7d9443a21cdb146a9f02 333432 dot2tex_2.9.0-3_all.deb c8a0d6066b2e97bbf75aaa17c7d98f0703fbf9bc02a2ea6c0483555d8b8441b7 8168 dot2tex_2.9.0-3_amd64.buildinfo Files: 72ecb2891e1936ff55bc3aac8387f323 2012 graphics optional dot2tex_2.9.0-3.dsc 9155769337dad6a73743f00e247687bf 6728 graphics optional dot2tex_2.9.0-3.debian.tar.xz 61932b2f71e097f0c0158d2b6b0406c2 333432 graphics optional dot2tex_2.9.0-3_all.deb a3d7c394894d362f643cf034dccaf143 8168 graphics optional dot2tex_2.9.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAlxPy78ACgkQh588mTgB qU+jow//TLKXB/M4dHP8bclNA8fss/gULs4oGh6dCSqmBXpFaXv//Vd/jcaQ8Dk0 lHXNpfu90RTvO0Swizw76/C7uVEH4GdQfMBVDiCejYt85WDyHVQX/23CPo/lxQdb R6bry9crO4VQNvwi9GN6OWO4MvpgPCBktzniQ1TMh14Jk5KG4hFJ9tEPtuXy5gD5 ZL56oaVH3s+3yg4EBGNiRzUDnQ1LH3pTVjXqOMrhcpUoq/fo3WnV4o/niV4tU/Jw UolXCM0jnHYcykwiqrRWERQCkSPAkKVKn1ofY0OLgbRrDKFSfb9HLqvsvQSPM6GU
Bug#919623: marked as done (Remote code execution in scp support)
Your message dated Tue, 29 Jan 2019 05:50:04 +
with message-id
and subject line Bug#919623: fixed in rssh 2.3.4-9
has caused the Debian Bug report #919623,
regarding Remote code execution in scp 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.)
--
919623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rssh
Version: 2.3.4-8
Severity: grave
Tags: security upstream
https://sourceforge.net/p/rssh/mailman/message/36519118/ is the upstream
report. The reporter indicated they asked for a CVE but didn't include it
in the message.
scp allows remote code execution inside the server environment via several
methods due to inadequate command-line verification. This bug has been
present since the beginning of rssh.
I have a completely untested patch but haven't had time to test it yet.
Attaching it to this report for whatever it's worth.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 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)
LSM: AppArmor: enabled
Versions of packages rssh depends on:
ii debconf [debconf-2.0] 1.5.69
ii libc6 2.28-4
ii openssh-server 1:7.9p1-4
rssh recommends no packages.
Versions of packages rssh suggests:
ii cvs 2:1.12.13+real-26
pn makejail
pn rdist
ii rsync 3.1.3-1
ii subversion 1.10.3-1+b1
-- Configuration Files:
/etc/logcheck/ignore.d.server/rssh [Errno 13] Permission denied:
'/etc/logcheck/ignore.d.server/rssh'
/etc/rssh.conf changed [not included]
-- debconf information excluded
diff --git a/util.c b/util.c
index 56f67ad..4dde1a0 100644
--- a/util.c
+++ b/util.c
@@ -268,6 +268,45 @@ static int rsync_e_okay( char **vec )
}
+/*
+ * scp_okay() - take the command line and check that it is a hopefully-safe scp
+ * server command line, accepting only very specific options.
+ * Returns FALSE if the command line should not be allowed, TRUE
+ * if it is okay.
+ */
+static int scp_okay( char **vec )
+{
+ int saw_file = FALSE;
+ int saw_end = FALSE;
+
+ for ( ; vec && *vec; vec++ ){
+ /* Allowed options. */
+ if ( !saw_end ) {
+ if ( strcmp(*vec, "-v") == 0 ) continue;
+ if ( strcmp(*vec, "-r") == 0 ) continue;
+ if ( strcmp(*vec, "-p") == 0 ) continue;
+ if ( strcmp(*vec, "-d") == 0 ) continue;
+ if ( strcmp(*vec, "-f") == 0 ) continue;
+ if ( strcmp(*vec, "-t") == 0 ) continue;
+ }
+
+ /* End of arguments. One more argument allowed after this. */
+ if ( !saw_end && strcmp(*vec, "--") == 0 ){
+ saw_end = TRUE;
+ continue;
+ }
+
+ /* No other options allowed, but allow file starting with -. */
+ if ( *vec[0] == '-' && !saw_end ) return FALSE;
+ if ( saw_file ) return FALSE;
+ saw_file = TRUE;
+ }
+
+ /* We must have seen a single file. */
+ return saw_file;
+}
+
+
/*
* check_command_line() - take the command line passed to rssh, and verify
* that the specified command is one the user is
@@ -283,8 +322,11 @@ char *check_command_line( char **cl, ShellOptions_t *opts )
return PATH_SFTP_SERVER;
if ( check_command(*cl, opts, PATH_SCP, RSSH_ALLOW_SCP) ){
- /* filter -S option */
- if ( opt_filter(cl, 'S') ) return NULL;
+ if ( !scp_okay(cl) ){
+ fprintf(stderr, "\ninsecure scp option not allowed.");
+ log_msg("insecure scp option in scp command line");
+ return NULL;
+ }
return PATH_SCP;
}
--- End Message ---
--- Begin Message ---
Source: rssh
Source-Version: 2.3.4-9
We believe that the bug you reported is fixed in the latest version of
rssh, 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
Bug#919442: marked as done (python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Tue, 29 Jan 2019 05:19:37 + with message-id and subject line Bug#919442: fixed in python-dmidecode 3.12.2-7 has caused the Debian Bug report #919442, regarding python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE 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.) -- 919442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-dmidecode-dbg Version: 3.12.2-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: stretch -> buster For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 0m37.0s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-dmidecode-dbg/AUTHORS (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/AUTHORS (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/AUTHORS.upstream (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/AUTHORS.upstream (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/README (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/README (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/README.types (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/README.types (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/README.upstream.gz (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/README.upstream.gz (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/changelog.Debian.gz (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/changelog.Debian.gz (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/changelog.gz (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/changelog.gz (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode /usr/share/doc/python-dmidecode-dbg/copyright (python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/copyright (python-dmidecode) /usr/share/doc/python-dmidecode-dbg -> python-dmidecode cheers, Andreas python-dmidecode-dbg_3.12.2-6.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-dmidecode Source-Version: 3.12.2-7 We believe that the bug you reported is fixed in the latest version of python-dmidecode, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-dmidecode package) (This message was generated automatically at their request; if you believe that there is a
