Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
Correction. I said: > "dpkg-buildpackage -B" (to generate arch-indep packages). but really meant this: "dpkg-buildpackage -B" (to generate arch-dep packages). Sorry for the confusion.
Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
On Sat, Feb 23, 2019 at 01:15:49AM +0100, Hans van Kranenburg wrote: > Can you please help me by formulating a clear problem / question and if > possible some expected things that you would like to have as a result? Sure. This is a packaging bug in debian/rules. Packages must build for the end user with plain "dpkg-buildpackage" but also in the official autobuilders by doing "dpkg-buildpackage -A" (to generate arch-all packages) or "dpkg-buildpackage -B" (to generate arch-indep packages). Either of those failing is a FTBFS bug, hence the serious severity. To reproduce the problem, please try building the package with "dpkg-buildpackage -A", which is exactly what the arch:all autobuilder would do if the package was uploaded in source-only form. The hint of splitting dh_foo into dh_foo-arch and dh_foo-indep usually works for packages that use dh and have this bug, i.e. for packages which build ok when built with plain "dpkg-buildpackage" but not with "dpkg-buildpackage -A" or "dpkg-buildpackage -B". Thanks.
Bug#857973: marked as done (dstat: uses network during build)
Your message dated Sat, 23 Feb 2019 02:38:49 + with message-id and subject line Bug#857973: fixed in dstat 0.7.3-1.1 has caused the Debian Bug report #857973, regarding dstat: uses network during build 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.) -- 857973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dstat Version: 0.7.3-1 Severity: serious Justification: Policy 4.9 Hi, When running the testsuite, the ntp dstat plugin tries to get the time using NTP from 0.fedora.pool.ntp.org. As policy says, accessing the network in this way is not permitted for packages in the main archive. Thanks, James signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: dstat Source-Version: 0.7.3-1.1 We believe that the bug you reported is fixed in the latest version of dstat, 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. Emanuele Rocca (supplier of updated dstat 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, 23 Feb 2019 02:10:18 +0100 Source: dstat Binary: dstat Architecture: source all Version: 0.7.3-1.1 Distribution: unstable Urgency: high Maintainer: Andrew Pollock Changed-By: Emanuele Rocca Description: dstat - versatile resource statistics tool Closes: 852927 857973 Changes: dstat (0.7.3-1.1) unstable; urgency=high . * Non-maintainer upload * Fix crash in top-int plugin (closes: #852927) * Exclude ntp plugin from --all-plugins, used by make test (closes: #857973) Checksums-Sha1: d501acb30b4a60d08c9965560e1e07602343976a 1772 dstat_0.7.3-1.1.dsc defff5821dcb50bbae111390ec0b3121d6f09ced 6140 dstat_0.7.3-1.1.debian.tar.xz 52a046cc1fb5d55f8c3b4fd6d9f732b26cf778c1 61624 dstat_0.7.3-1.1_all.deb 4353b98ae53b1043131db6232b9d2d26e67b7a99 5988 dstat_0.7.3-1.1_amd64.buildinfo Checksums-Sha256: 97e14872ee437dbf686bb705f40ffb9a485256b334a83f0044952e4a2e3347a0 1772 dstat_0.7.3-1.1.dsc 274805e506e9aaeb51916bf28d2a8a47b0e2715f36f93c3c66d9ff30637b1b0a 6140 dstat_0.7.3-1.1.debian.tar.xz 74e2b7515c08b4525f1e6934dc098839ab40c65d4b4246f1f533c1923be63093 61624 dstat_0.7.3-1.1_all.deb a688a2fcb08552736581028e3e5f8ecd6f701a173e0030712244844040d8398e 5988 dstat_0.7.3-1.1_amd64.buildinfo Files: 8ae14fabbcaf8eeeb5c3226a18be9ef4 1772 admin optional dstat_0.7.3-1.1.dsc b680f55778d91b310ff4c732bae58739 6140 admin optional dstat_0.7.3-1.1.debian.tar.xz 6371e80732634989670dd03655c09de4 61624 admin optional dstat_0.7.3-1.1_all.deb a8ab5ecb613924890226d28b5ea15d6b 5988 admin optional dstat_0.7.3-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAlxwpLMPHGVtYUBkZWJp YW4ub3JnAAoJENUIWgdQ/bejRW8QAICJesnW68g4QanVuS0WqcdE9b/qK/B40jo8 QH4YdxS1C090snLTUolgSLWkHQVaD+6kXocuvKQmprfY0WCFC3A+aLp2rTnsbMIY qjycJVApxYf4mbTdfrctae0adAGYMuNxAkQ9ipM8gfPNv1POHmHJduY8ozrp+4C0 /aNpU7OEZf/1ieHOAG7zWbLb9tjr0XblshA620PtLe9Fig/NAFxf68LQNQ7OYsbQ UGDMW8DW47/rYYPLri24dm7HIum+GJXZPngC5QKjjusN8EMzrDGuHqdtKDTXxz6E X5Xm4gTTwbsXIFc6e/lfHsm5zPt7d0XegcO0NZV/ErqGm62cZzYY9ieNcwWGUZpw H0K95DOgy46UVePwErVUJCZeZfCBCjsziXIudnpmefB/nESnod/mG0FRmyCwP94b hnn9Ti9bz3kxAFqHiJ9P9h8cdvlUhoOriU+q0AyrAQCA3rZ6J7fzTONNhuqItw49 2t0q8r+m7t8mwYzVSRblI+nQxMI24tpoDVN0isCNIQBYE3kCxDceUt7eT9tvW5JA RxpxiggbL1T6MB/rY39jhmjA4f9KSqZtPh+f8rDLc/U5LrZl60H/z29CKmKekkL8 +XkRULxTTXOHDRBHrpCFatvQghsoAj001qSm/A3RZW/JrR+hkOwhkqk/3Yk7MTg0 VTlZwjlj =Xq3A -END PGP SIGNATURE End Message ---
Bug#852927: marked as done (dstat: FTBFS: Test failures)
Your message dated Sat, 23 Feb 2019 02:38:49 + with message-id and subject line Bug#852927: fixed in dstat 0.7.3-1.1 has caused the Debian Bug report #852927, regarding dstat: FTBFS: Test failures 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.) -- 852927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dstat Version: 0.7.3-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170128 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Module dstat_zfs_arc failed to load. (Cannot open file > /proc/spl/kstat/zfs/arcstats) > Module dstat_zfs_l2arc failed to load. (Cannot open file > /proc/spl/kstat/zfs/arcstats) > Module dstat_zfs_zil failed to load. (Cannot open file > /proc/spl/kstat/zfs/zil) > [7lTraceback (most recent call last): > File "./dstat", line 2842, in > main() > File "./dstat", line 2703, in main > scheduler.run() > File "/usr/lib/python2.7/sched.py", line 117, in run > action(*argument) > File "./dstat", line 2797, in perform > o.extract() > File "/<>/plugins/dstat_top_int.py", line 40, in extract > total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed > IndexError: list index out of range > Makefile:36: recipe for target 'test' failed The full build log is available from: http://aws-logs.debian.net/2017/01/28/dstat_0.7.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: dstat Source-Version: 0.7.3-1.1 We believe that the bug you reported is fixed in the latest version of dstat, 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 852...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated dstat 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, 23 Feb 2019 02:10:18 +0100 Source: dstat Binary: dstat Architecture: source all Version: 0.7.3-1.1 Distribution: unstable Urgency: high Maintainer: Andrew Pollock Changed-By: Emanuele Rocca Description: dstat - versatile resource statistics tool Closes: 852927 857973 Changes: dstat (0.7.3-1.1) unstable; urgency=high . * Non-maintainer upload * Fix crash in top-int plugin (closes: #852927) * Exclude ntp plugin from --all-plugins, used by make test (closes: #857973) Checksums-Sha1: d501acb30b4a60d08c9965560e1e07602343976a 1772 dstat_0.7.3-1.1.dsc defff5821dcb50bbae111390ec0b3121d6f09ced 6140 dstat_0.7.3-1.1.debian.tar.xz 52a046cc1fb5d55f8c3b4fd6d9f732b26cf778c1 61624 dstat_0.7.3-1.1_all.deb 4353b98ae53b1043131db6232b9d2d26e67b7a99 5988 dstat_0.7.3-1.1_amd64.buildinfo Checksums-Sha256: 97e14872ee437dbf686bb705f40ffb9a485256b334a83f0044952e4a2e3347a0 1772 dstat_0.7.3-1.1.dsc 274805e506e9aaeb51916bf28d2a8a47b0e2715f36f93c3c66d9ff30637b1b0a 6140 dstat_0.7.3-1.1.debian.tar.xz 74e2b7515c08b4525f1e6934dc098839ab40c65d4b4246f1f533c1923be63093 61624 dstat_0.7.3-1.1_all.deb a688a2fcb08552736581028e3e5f8ecd6f701a173e0030712244844040d8398e 5988 dstat_0.7.3-1.1_amd64.buildinfo Files: 8ae14fabbcaf8eeeb5c3226a18be9ef4 1772 admin optional dstat_0.7.3-1.1.dsc b680f55778d91b310ff4c732bae58739 6140 admin optional dstat_0.7.3-1.1.debian.tar.xz 6371e80732634989670dd03655c09de4 61624 admin optional dstat_0.7.3-1.1_all.deb a8ab5ecb613924890226d28b5ea15d6b 5988 admin optional dstat_0.7.3-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAlxwpLMPHGVtYUBkZWJp YW4ub3JnAAoJENUIWgdQ/bejRW8QAICJesnW68g4QanVuS0WqcdE9b/qK/B40jo8 QH4YdxS1C090snLTUolgSLWkHQVaD+6kXocuvKQmprfY0WCFC3A+aLp2rTnsbMIY
Bug#852927: dstat: FTBFS: Test failures
tag 852927 patch
thanks
On 28/01 09:25, Lucas Nussbaum wrote:
> > [7lTraceback (most recent call last):
> > File "./dstat", line 2842, in
> > main()
> > File "./dstat", line 2703, in main
> > scheduler.run()
> > File "/usr/lib/python2.7/sched.py", line 117, in run
> > action(*argument)
> > File "./dstat", line 2797, in perform
> > o.extract()
> > File "/<>/plugins/dstat_top_int.py", line 40, in extract
> > total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
> > IndexError: list index out of range
> > Makefile:36: recipe for target 'test' failed
Fixed in 0.7.3-1.1. NUM diff attached.
diff -Nru dstat-0.7.3/debian/changelog dstat-0.7.3/debian/changelog
--- dstat-0.7.3/debian/changelog 2017-01-18 11:12:16.0 +0100
+++ dstat-0.7.3/debian/changelog 2019-02-23 02:10:18.0 +0100
@@ -1,3 +1,11 @@
+dstat (0.7.3-1.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Fix crash in top-int plugin (closes: #852927)
+ * Exclude ntp plugin from --all-plugins, used by make test (closes: #857973)
+
+ -- Emanuele Rocca Sat, 23 Feb 2019 02:10:18 +0100
+
dstat (0.7.3-1) unstable; urgency=medium
* New upstream release (closes: #851494)
diff -Nru dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973
--- dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 2019-02-23 02:10:18.0 +0100
@@ -0,0 +1,20 @@
+Description: exclude ntp from --all-plugins
+ dstat allows to specify --all-plugins, a CLI option used by `make test` for
+ testing purposes. Exclude the ntp plugin from the list as it performs network
+ access.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/857973
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/dstat
dstat-0.7.3/dstat
+@@ -177,6 +177,9 @@ class Options:
+ ### Make list unique in a fancy fast way
+ plugins = {}.fromkeys(allplugins).keys()
+ plugins.sort()
++# Do not include ntp plugin as it performs network access. See
++# https://bugs.debian.org/857973
++plugins.remove('ntp')
+ self.plugins += plugins
+ elif opt in ['--bits']:
+ self.bits = True
diff -Nru dstat-0.7.3/debian/patches/series dstat-0.7.3/debian/patches/series
--- dstat-0.7.3/debian/patches/series 2014-03-24 03:02:19.0 +0100
+++ dstat-0.7.3/debian/patches/series 2019-02-23 02:10:18.0 +0100
@@ -1 +1,3 @@
fix_629680
+top_int_plugin_852927
+all_plugins_exclude_ntp_857973
diff -Nru dstat-0.7.3/debian/patches/top_int_plugin_852927 dstat-0.7.3/debian/patches/top_int_plugin_852927
--- dstat-0.7.3/debian/patches/top_int_plugin_852927 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/top_int_plugin_852927 2019-02-23 02:08:28.0 +0100
@@ -0,0 +1,21 @@
+Description: avoid crashing in top-int plugin
+ The first intset can have less elements than the second one. Catch IndexError
+ to avoid crashing if that is the case.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/852927
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/plugins/dstat_top_int.py
dstat-0.7.3/plugins/dstat_top_int.py
+@@ -37,7 +37,10 @@ class dstat_plugin(dstat):
+ self.intset2 = [ long(int) for int in line[3:] ]
+
+ for i in range(len(self.intset2)):
+-total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++try:
++total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++except IndexError:
++continue
+
+ ### Put the highest value in self.val
+ if total > self.val['total']:
Processed: Re: dstat: FTBFS: Test failures
Processing commands for cont...@bugs.debian.org: > tag 852927 patch Bug #852927 [src:dstat] dstat: FTBFS: Test failures Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 852927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857973: dstat: uses network during build
tag 857973 patch
thanks
On 16/03 07:48, James Cowgill wrote:
> When running the testsuite, the ntp dstat plugin tries to get the time
> using NTP from 0.fedora.pool.ntp.org. As policy says, accessing the
> network in this way is not permitted for packages in the main archive.
Fixed by excluding ntp from --all-plugins. NMU diff attached.
diff -Nru dstat-0.7.3/debian/changelog dstat-0.7.3/debian/changelog
--- dstat-0.7.3/debian/changelog 2017-01-18 11:12:16.0 +0100
+++ dstat-0.7.3/debian/changelog 2019-02-23 02:10:18.0 +0100
@@ -1,3 +1,11 @@
+dstat (0.7.3-1.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Fix crash in top-int plugin (closes: #852927)
+ * Exclude ntp plugin from --all-plugins, used by make test (closes: #857973)
+
+ -- Emanuele Rocca Sat, 23 Feb 2019 02:10:18 +0100
+
dstat (0.7.3-1) unstable; urgency=medium
* New upstream release (closes: #851494)
diff -Nru dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973
--- dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 2019-02-23 02:10:18.0 +0100
@@ -0,0 +1,20 @@
+Description: exclude ntp from --all-plugins
+ dstat allows to specify --all-plugins, a CLI option used by `make test` for
+ testing purposes. Exclude the ntp plugin from the list as it performs network
+ access.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/857973
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/dstat
dstat-0.7.3/dstat
+@@ -177,6 +177,9 @@ class Options:
+ ### Make list unique in a fancy fast way
+ plugins = {}.fromkeys(allplugins).keys()
+ plugins.sort()
++# Do not include ntp plugin as it performs network access. See
++# https://bugs.debian.org/857973
++plugins.remove('ntp')
+ self.plugins += plugins
+ elif opt in ['--bits']:
+ self.bits = True
diff -Nru dstat-0.7.3/debian/patches/series dstat-0.7.3/debian/patches/series
--- dstat-0.7.3/debian/patches/series 2014-03-24 03:02:19.0 +0100
+++ dstat-0.7.3/debian/patches/series 2019-02-23 02:10:18.0 +0100
@@ -1 +1,3 @@
fix_629680
+top_int_plugin_852927
+all_plugins_exclude_ntp_857973
diff -Nru dstat-0.7.3/debian/patches/top_int_plugin_852927 dstat-0.7.3/debian/patches/top_int_plugin_852927
--- dstat-0.7.3/debian/patches/top_int_plugin_852927 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/top_int_plugin_852927 2019-02-23 02:08:28.0 +0100
@@ -0,0 +1,21 @@
+Description: avoid crashing in top-int plugin
+ The first intset can have less elements than the second one. Catch IndexError
+ to avoid crashing if that is the case.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/852927
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/plugins/dstat_top_int.py
dstat-0.7.3/plugins/dstat_top_int.py
+@@ -37,7 +37,10 @@ class dstat_plugin(dstat):
+ self.intset2 = [ long(int) for int in line[3:] ]
+
+ for i in range(len(self.intset2)):
+-total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++try:
++total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++except IndexError:
++continue
+
+ ### Put the highest value in self.val
+ if total > self.val['total']:
Processed: Re: dstat: uses network during build
Processing commands for cont...@bugs.debian.org: > tag 857973 patch Bug #857973 [src:dstat] dstat: uses network during build Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 857973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923016: marked as done (systemtap: scripts fail to compile with recent kernels)
Your message dated Sat, 23 Feb 2019 00:50:24 +
with message-id
and subject line Bug#923016: fixed in systemtap 4.0-1
has caused the Debian Bug report #923016,
regarding systemtap: scripts fail to compile with recent kernels
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.)
--
923016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemtap
Version: 3.3-1
Severity: grave
Justification: renders package unusable
SystemTap 3.3-1 does not work with the kernel currently in sid,
linux-image-4.19.0-3-amd64 4.19.20-1.
$ sudo stap -e 'probe oneshot { println("hello world") }'
In file included from
/tmp/stapBznfoX/stap_7c11b6c20586a98b7853a74fee0e49f4_979_src.c:298:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c: In function
‘stp_tracepoint_coming’:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c:281:6: error: assignment
to ‘struct tracepoint *’ from ‘tracepoint_ptr_t’ {aka ‘const int’} makes
pointer from integer without a cast [-Werror=int-conversion]
tp = tp_mod->mod->tracepoints_ptrs[i];
^
/usr/share/systemtap/runtime/linux/stp_tracepoint.c: In function
‘stp_tracepoint_going’:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c:323:6: error: assignment
to ‘struct tracepoint *’ from ‘tracepoint_ptr_t’ {aka ‘const int’} makes
pointer from integer without a cast [-Werror=int-conversion]
tp = tp_mod->mod->tracepoints_ptrs[i];
^
cc1: all warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-4.19.0-3-common/scripts/Makefile.build:308:
/tmp/stapBznfoX/stap_7c11b6c20586a98b7853a74fee0e49f4_979_src.o] Error 1
make[2]: *** [/usr/src/linux-headers-4.19.0-3-common/Makefile:1535:
_module_/tmp/stapBznfoX] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
The latest upstream version (4.0) does however work fine. I'm gonna package it
right away to get a working SystemTap in Buster.
--- End Message ---
--- Begin Message ---
Source: systemtap
Source-Version: 4.0-1
We believe that the bug you reported is fixed in the latest version of
systemtap, 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 923...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emanuele Rocca (supplier of updated systemtap 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, 23 Feb 2019 01:04:03 +0100
Source: systemtap
Binary: systemtap systemtap-client systemtap-common systemtap-dbgsym
systemtap-doc systemtap-runtime systemtap-runtime-dbgsym systemtap-sdt-dev
systemtap-server systemtap-server-dbgsym
Architecture: source amd64 all
Version: 4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf
Changed-By: Emanuele Rocca
Description:
systemtap - instrumentation system for Linux
systemtap-client - instrumentation system for Linux (client for compile server)
systemtap-common - instrumentation system for Linux (common component)
systemtap-doc - documentation and examples for SystemTap
systemtap-runtime - instrumentation system for Linux (runtime component)
systemtap-sdt-dev - statically defined probes development files
systemtap-server - instrumentation system for Linux (compile server)
Closes: 923016
Changes:
systemtap (4.0-1) unstable; urgency=medium
.
[Emanuele Rocca]
* New upstream version (Closes: #923016)
* Add myself to uploaders
* Update upstream signing key
* Do not pass --parallel to dh, default since debhelper 10
* Do not build depend on dh-autoreconf, debhelper enables it by default
since version 10
* Bump Standards Version
.
[Ondřej Nový]
* d/changelog: Remove trailing whitespaces
* d/control: Remove trailing whitespaces
* d/control: Fix wrong Vcs-*
Checksums-Sha1:
f97ace7cbb612d6f2c91a7d962a60537b71a86f7 2882 systemtap_4.0-1.dsc
40a21d71b0d42bc216f75befd3fca82701821211 5282312 systemtap_4.0.orig.tar.gz
Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
On 2/23/19 1:15 AM, Hans van Kranenburg wrote: > Hi, > > On 2/23/19 12:59 AM, Santiago Vila wrote: >> >>> Hint: Try splitting override_dh_compress into override_dh_compress-arch >>> and override_dh_compress-indep. >> >> Not really sure that this is a good hint in this case. The first rule >> showing an >> error is certainly this one: >> >> find: 'debian/xen-hypervisor-*/usr/lib/debug': No such file or directory >> >> but maybe it's override_dh_missing the one that would benefit from an >> -arch/-indep split. > > Can you please help me by formulating a clear problem / question and if > possible some expected things that you would like to have as a result? > > What I see flying by is: A B C and also X Y Z and you might R S T, and > also, by the way: F G H. Also, your new bts results in an... "Serious (policy violations or makes package unfit for release)" ...listed for our packages, which is not nice, in this phase of the release freeze cycle, because... The whole thing builds just fine in sid and also in stretch here. Can you explain why you want to do this? Hans
Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
Hi, On 2/23/19 12:59 AM, Santiago Vila wrote: > >> Hint: Try splitting override_dh_compress into override_dh_compress-arch >> and override_dh_compress-indep. > > Not really sure that this is a good hint in this case. The first rule showing > an > error is certainly this one: > > find: 'debian/xen-hypervisor-*/usr/lib/debug': No such file or directory > > but maybe it's override_dh_missing the one that would benefit from an > -arch/-indep split. Can you please help me by formulating a clear problem / question and if possible some expected things that you would like to have as a result? What I see flying by is: A B C and also X Y Z and you might R S T, and also, by the way: F G H. Hans
Bug#923016: systemtap: scripts fail to compile with recent kernels
Package: systemtap
Version: 3.3-1
Severity: grave
Justification: renders package unusable
SystemTap 3.3-1 does not work with the kernel currently in sid,
linux-image-4.19.0-3-amd64 4.19.20-1.
$ sudo stap -e 'probe oneshot { println("hello world") }'
In file included from
/tmp/stapBznfoX/stap_7c11b6c20586a98b7853a74fee0e49f4_979_src.c:298:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c: In function
‘stp_tracepoint_coming’:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c:281:6: error: assignment
to ‘struct tracepoint *’ from ‘tracepoint_ptr_t’ {aka ‘const int’} makes
pointer from integer without a cast [-Werror=int-conversion]
tp = tp_mod->mod->tracepoints_ptrs[i];
^
/usr/share/systemtap/runtime/linux/stp_tracepoint.c: In function
‘stp_tracepoint_going’:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c:323:6: error: assignment
to ‘struct tracepoint *’ from ‘tracepoint_ptr_t’ {aka ‘const int’} makes
pointer from integer without a cast [-Werror=int-conversion]
tp = tp_mod->mod->tracepoints_ptrs[i];
^
cc1: all warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-4.19.0-3-common/scripts/Makefile.build:308:
/tmp/stapBznfoX/stap_7c11b6c20586a98b7853a74fee0e49f4_979_src.o] Error 1
make[2]: *** [/usr/src/linux-headers-4.19.0-3-common/Makefile:1535:
_module_/tmp/stapBznfoX] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
The latest upstream version (4.0) does however work fine. I'm gonna package it
right away to get a working SystemTap in Buster.
Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
Hmm, I said: > Hint: Try splitting override_dh_compress into override_dh_compress-arch > and override_dh_compress-indep. Not really sure that this is a good hint in this case. The first rule showing an error is certainly this one: find: 'debian/xen-hypervisor-*/usr/lib/debug': No such file or directory but maybe it's override_dh_missing the one that would benefit from an -arch/-indep split. Thanks.
Bug#922926: marked as done (commit-patch: fails to install along xemacs21: Invalid read syntax: "Weird old-backquote syntax")
Your message dated Fri, 22 Feb 2019 23:49:41 +
with message-id
and subject line Bug#922926: fixed in commit-patch 2.6-2
has caused the Debian Bug report #922926,
regarding commit-patch: fails to install along xemacs21: Invalid read syntax:
"Weird old-backquote syntax"
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.)
--
922926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: commit-patch
Version: 2.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up commit-patch (2.6-1) ...
Install emacsen-common for xemacs21
emacsen-common: Handling install of emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
Done
Install commit-patch for xemacs21
install/commit-patch: Handling install for emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Compiling /usr/share/xemacs21/site-lisp/commit-patch/commit-patch-buffer.el...
Loading dired-mule...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/commit-patch/commit-patch-buffer.el:
!! Invalid read syntax (("Weird old-backquote syntax"))
>>Error occurred processing commit-patch-buffer.el:
Invalid read syntax: "Weird old-backquote syntax"
Done
ERROR: install script from commit-patch package failed
dpkg: error processing package commit-patch (--configure):
installed commit-patch package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
commit-patch
cheers,
Andreas
commit-patch=2.6-1_xemacs21.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: commit-patch
Source-Version: 2.6-2
We believe that the bug you reported is fixed in the latest version of
commit-patch, 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 922...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Caldwell (supplier of updated commit-patch package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 22 Feb 2019 04:09:12 -0800
Source: commit-patch
Binary: commit-patch
Architecture: source all
Version: 2.6-2
Distribution: unstable
Urgency: medium
Maintainer: David Caldwell
Changed-By: David Caldwell
Description:
commit-patch - utility to commit fine grained patches to source code control
rep
Closes: 922926
Changes:
commit-patch (2.6-2) unstable; urgency=medium
.
* Don't attempt to byte compile on xemacs (not supported by upstream)
(Closes: 922926)
Checksums-Sha1:
a9cb8543908b7b6678d05bd376cca94f6b7ae999 1801 commit-patch_2.6-2.dsc
fe1dae8f112388d2339e2a9463a3d07d931dbbc6 4432 commit-patch_2.6-2.debian.tar.xz
35de79201c3df5b0c40915bcf14f0eb057fe0f12 20136 commit-patch_2.6-2_all.deb
0ac35fa0a091c5fc83fcb9fb31b5af003262ea40 5823
commit-patch_2.6-2_amd64.buildinfo
Checksums-Sha256:
83aa72faa25cc99fc71893f835b1a9086e6366dd73dff1bcb8072e1423470235 1801
commit-patch_2.6-2.dsc
63c56e9b18f4e6de0f4762f02ac70c6369058eafb8e6830ec6c53952d44b105e 4432
commit-patch_2.6-2.debian.tar.xz
d2dfe258d35dffe91f8744258d70352b51b6fffab1c96a891b96626e40788e0e 20136
commit-patch_2.6-2_all.deb
052655b48616ad83ed70fb625ef19e84ce99cff9e350f86c55ec6e6eff5d2a47 5823
commit-patch_2.6-2_amd64.buildinfo
Files:
1f978625de907fc5537396d6d78936ce 1801 vcs optional commit-patch_2.6-2.dsc
bfd7402f3fcf574e9825c67171d0cceb 4432 vcs optional
commit-patch_2.6-2.debian.tar.xz
dbbf8e0daa6c7809bcc4017331ff1c27 20136 vcs optional commit-patch_2.6-2_all.deb
a87f92ac9933879484a3e7ad1a4f6ad0 5823 vcs optional
commit-patch_2.6-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
Package: src:xen
Version: 4.11.1+26-g87f51bf366-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid with "dpkg-buildpackage -A" but it failed:
[...]
debian/rules build-indep
dh build-indep --with=python2
debian/rules override_dh_update_autotools_config
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
cp /usr/share/misc/{config.sub,config.guess} .
make[1]: Leaving directory '/<>/xen-4.11.1+26-g87f51bf366'
dh_autoreconf -i
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
cp debian/xen-kconfig xen/.config
make -C xen olddefconfig XEN_COMPILE_ARCH=x86_64 XEN_TARGET_ARCH=x86_64
make[2]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366/xen'
make -f
/<>/xen-4.11.1+26-g87f51bf366/xen/tools/kconfig/Makefile.kconfig
ARCH=x86_64 SRCARCH=x86 HOSTCC="gcc" HOSTCXX="g++" olddefconfig
make[3]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366/xen'
[... snipped ...]
dh_perl -i
dh_link -i
dh_strip_nondeterminism -i
debian/rules override_dh_compress
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
rdfind -makehardlinks true -makeresultsfile false \
debian/xenstore-utils/usr/bin
Now scanning "debian/xenstore-utils/usr/bin", found 0 files.
Now have 0 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 0 bytes or 0 B
Removed 0 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making hard links.
Making 0 links.
:
dh_compress
find debian/xen-hypervisor-*/usr/lib/debug -type f -print0 \
| xargs -0r gzip -9vn
find: 'debian/xen-hypervisor-*/usr/lib/debug': No such file or directory
make[1]: Leaving directory '/<>/xen-4.11.1+26-g87f51bf366'
dh_fixperms -i
debian/rules override_dh_missing
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
dh_missing --fail-missing
dh_missing: etc/bash_completion.d/xl.sh exists in debian/tmp but is not
installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with
files per package)
* dh_install: libxen-dev (30), libxencall1 (2), libxendevicemodel1
(2), libxenevtchn1 (2), libxenforeignmemory1 (2), libxengnttab1 (2),
libxenmisc4.11 (14), libxenstore3.0 (2), libxentoolcore1 (2), libxentoollog1
(2), xen-doc (1), xen-hypervisor-4.11-amd64 (3), xen-hypervisor-4.11-arm64 (0),
xen-hypervisor-4.11-armhf (0), xen-hypervisor-common (1), xen-system-amd64 (0),
xen-system-arm64 (0), xen-system-armhf (0), xen-utils-4.11 (4),
xen-utils-common (18), xenstore-utils (13)
* dh_installdocs: libxen-dev (0), libxencall1 (0), libxendevicemodel1
(0), libxenevtchn1 (0), libxenforeignmemory1 (0), libxengnttab1 (0),
libxenmisc4.11 (0), libxenstore3.0 (0), libxentoolcore1 (0), libxentoollog1
(0), xen-doc (0), xen-hypervisor-4.11-amd64 (0), xen-hypervisor-4.11-arm64 (0),
xen-hypervisor-4.11-armhf (0), xen-hypervisor-common (0), xen-system-amd64 (0),
xen-system-arm64 (0), xen-system-armhf (0), xen-utils-4.11 (0),
xen-utils-common (0), xenstore-utils (0)
* dh_installexamples: libxen-dev (0), libxencall1 (0),
libxendevicemodel1 (0), libxenevtchn1 (0), libxenforeignmemory1 (0),
libxengnttab1 (0), libxenmisc4.11 (0), libxenstore3.0 (0), libxentoolcore1 (0),
libxentoollog1 (0), xen-doc (0), xen-hypervisor-4.11-amd64 (0),
xen-hypervisor-4.11-arm64 (0), xen-hypervisor-4.11-armhf (0),
xen-hypervisor-common (0), xen-system-amd64 (0), xen-system-arm64 (0),
xen-system-armhf (0), xen-utils-4.11 (0), xen-utils-common (1), xenstore-utils
(0)
If the missing files are installed by another tool, please file a bug
against it.
When filing the report, if the tool is not part of debhelper itself,
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide
for debhelper (10.6.3+).
(in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
make[1]: *** [debian/rules:316: override_dh_missing] Error 2
make[1]: Leaving directory '/<>/xen-4.11.1+26-g87f51bf366'
make: *** [debian/rules:147: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
Hint: Try splitting override_dh_compress into override_dh_compress-arch
and
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 921189 https://github.com/roehling/postsrsd/pull/90 Bug #921189 [src:postsrsd] postsrsd FTBFS on 64bit big endian: AllTests (Failed) Set Bug forwarded-to-address to 'https://github.com/roehling/postsrsd/pull/90'. > tag 921189 + patch Bug #921189 [src:postsrsd] postsrsd FTBFS on 64bit big endian: AllTests (Failed) Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 921189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859784: validns: diff for NMU version 0.8+git20160720-3.1
Dear maintainer,
I've prepared an NMU for validns (versioned as 0.8+git20160720-3.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.
Regards.
Sebastian
diff -Nru validns-0.8+git20160720/debian/changelog validns-0.8+git20160720/debian/changelog
--- validns-0.8+git20160720/debian/changelog 2016-12-14 16:01:55.0 +0100
+++ validns-0.8+git20160720/debian/changelog 2019-02-22 23:52:58.0 +0100
@@ -1,3 +1,12 @@
+validns (0.8+git20160720-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Avoid a warning regarding string truncation (Closes: #897882).
+ * Get it compiled against OpenSSL 1.1+ (Closes: #859784).
+ * Use priority optional instead of extra.
+
+ -- Sebastian Andrzej Siewior Fri, 22 Feb 2019 23:52:58 +0100
+
validns (0.8+git20160720-3) unstable; urgency=medium
* debian/copyright Add License: statement.
diff -Nru validns-0.8+git20160720/debian/control validns-0.8+git20160720/debian/control
--- validns-0.8+git20160720/debian/control 2016-12-14 16:01:55.0 +0100
+++ validns-0.8+git20160720/debian/control 2019-02-22 23:52:58.0 +0100
@@ -1,9 +1,9 @@
Source: validns
Section: net
-Priority: extra
+Priority: optional
Maintainer: Casper Gielen
Uploaders: Joost van Baal-Ilić
-Build-Depends: debhelper (>= 9), libssl1.0-dev, libjudy-dev, libtest-command-simple-perl, dpkg-dev (>= 1.16.1~)
+Build-Depends: debhelper (>= 9), libssl-dev, libjudy-dev, libtest-command-simple-perl, dpkg-dev (>= 1.16.1~)
Standards-Version: 3.9.8
Homepage: http://www.validns.net/
Vcs-Git: https://anonscm.debian.org/git/collab-maint/validns.git
diff -Nru validns-0.8+git20160720/debian/patches/fix-compilation-on-openssl-1.1.patch validns-0.8+git20160720/debian/patches/fix-compilation-on-openssl-1.1.patch
--- validns-0.8+git20160720/debian/patches/fix-compilation-on-openssl-1.1.patch 1970-01-01 01:00:00.0 +0100
+++ validns-0.8+git20160720/debian/patches/fix-compilation-on-openssl-1.1.patch 2019-02-22 23:50:11.0 +0100
@@ -0,0 +1,248 @@
+From: Author: "Chris West (Faux)"
+Date: Fri, 22 Feb 2019 23:39:34 +0100
+Subject: [PATCH] fix compilation on openssl 1.1
+
+BTS: https://bugs.debian.org/859784
+bigeasy: drop locking, check for OOM during allocation.
+Signed-off-by: Sebastian Andrzej Siewior
+---
+ dnskey.c | 9 +--
+ nsec3checks.c | 29 +-
+ rrsig.c | 69 ++-
+ 3 files changed, 42 insertions(+), 65 deletions(-)
+
+diff --git a/dnskey.c b/dnskey.c
+index fecc62abfd21..fda220c14d08 100644
+--- a/dnskey.c
b/dnskey.c
+@@ -154,6 +154,7 @@ int dnskey_build_pkey(struct rr_dnskey *rr)
+ unsigned int e_bytes;
+ unsigned char *pk;
+ int l;
++ BIGNUM *n, *e;
+
+ rsa = RSA_new();
+ if (!rsa)
+@@ -174,11 +175,15 @@ int dnskey_build_pkey(struct rr_dnskey *rr)
+ if (l < e_bytes) /* public key is too short */
+ goto done;
+
+- rsa->e = BN_bin2bn(pk, e_bytes, NULL);
++ e = BN_bin2bn(pk, e_bytes, NULL);
+ pk += e_bytes;
+ l -= e_bytes;
+
+- rsa->n = BN_bin2bn(pk, l, NULL);
++ n = BN_bin2bn(pk, l, NULL);
++ if (!e || !n)
++ goto done;
++
++ RSA_set0_key(rsa, n, e, NULL);
+
+ pkey = EVP_PKEY_new();
+ if (!pkey)
+diff --git a/nsec3checks.c b/nsec3checks.c
+index 69c655345bad..2abac9efa1bf 100644
+--- a/nsec3checks.c
b/nsec3checks.c
+@@ -28,7 +28,7 @@
+ static struct binary_data name2hash(char *name, struct rr *param)
+ {
+ struct rr_nsec3param *p = (struct rr_nsec3param *)param;
+- EVP_MD_CTX ctx;
++ EVP_MD_CTX *ctx;
+ unsigned char md0[EVP_MAX_MD_SIZE];
+ unsigned char md1[EVP_MAX_MD_SIZE];
+ unsigned char *md[2];
+@@ -45,26 +45,31 @@ static struct binary_data name2hash(char *name, struct rr *param)
+
+ /* XXX Maybe use Init_ex and Final_ex for speed? */
+
+- EVP_MD_CTX_init();
+- if (EVP_DigestInit(, EVP_sha1()) != 1)
++ ctx = EVP_MD_CTX_new();
++ if (ctx == NULL)
+ return r;
+- digest_size = EVP_MD_CTX_size();
+- EVP_DigestUpdate(, wire_name.data, wire_name.length);
+- EVP_DigestUpdate(, p->salt.data, p->salt.length);
+- EVP_DigestFinal(, md[mdi], NULL);
++ if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
++ goto out;
++ digest_size = EVP_MD_CTX_size(ctx);
++ EVP_DigestUpdate(ctx, wire_name.data, wire_name.length);
++ EVP_DigestUpdate(ctx, p->salt.data, p->salt.length);
++ EVP_DigestFinal(ctx, md[mdi], NULL);
+
+ for (i = 0; i < p->iterations; i++) {
+- if (EVP_DigestInit(, EVP_sha1()) != 1)
+- return r;
+- EVP_DigestUpdate(, md[mdi], digest_size);
++ if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
++ goto out;
++
++ EVP_DigestUpdate(ctx, md[mdi], digest_size);
+ mdi = (mdi + 1) % 2;
+- EVP_DigestUpdate(, p->salt.data, p->salt.length);
+- EVP_DigestFinal(, md[mdi], NULL);
++ EVP_DigestUpdate(ctx, p->salt.data, p->salt.length);
++ EVP_DigestFinal(ctx, md[mdi], NULL);
+ }
+
+ r.length = digest_size;
+ r.data = getmem(digest_size);
+ memcpy(r.data, md[mdi], digest_size);
++out:
++
Bug#923010: fauhdlc: FTBFS (FAUhdlParser.yy:13.9-27: error: syntax error, unexpected string, expecting identifier)
Package: src:fauhdlc Version: 20180504-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch ./autogen.sh configure.ac:8: installing 'scripts/compile' configure.ac:6: installing 'scripts/install-sh' configure.ac:6: installing 'scripts/missing' Makefile.am: installing './INSTALL' Makefile.am:17: warning: source file 'frontend/ast/NodeFactory.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. Makefile.am:17: warning: source file 'frontend/ast/Location.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/AstNode.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/AttributableDeclaration.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/AttributeDeclaration.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/AttributeSpecification.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/Name.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/PhysicalType.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/SubtypeIndication.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/RecordType.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/Types.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/ConstInteger.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/DiscreteRange.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/Expression.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/SimpleName.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/SymbolDeclaration.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/ast/ValDeclaration.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/Driver.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/DeclarativeRegion.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/Symbol.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/SymbolTable.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/BuiltinSymbolTable.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/NameLookup.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/RegisterBuiltins.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/misc/RangeSet.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file 'frontend/reporting/AmbiguousTypes.cpp' is in a subdirectory, Makefile.am:17: but option 'subdir-objects' is disabled Makefile.am:17: warning: source file
Bug#923011: nuxwdog: FTBFS (/usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private')
Package: src:nuxwdog
Version: 1.0.5-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 --no-parallel --with javahelper
dh_update_autotools_config -a
dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
configure.ac:59: installing './compile'
configure.ac:52: installing './missing'
Makefile.am: installing './depcomp'
jh_linkjars -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mkdir stash
cp lib/perl/Nuxwdogclient/*.inc stash
dh_auto_build -- -Dproduct.ui.flavor.prefix="" -Dproduct.prefix=""
-Dproduct="nuxwdog" -Dversion="1.0.5"
ant -Duser.name debian -Dproduct.ui.flavor.prefix= -Dproduct.prefix=
-Dproduct=nuxwdog -Dversion=1.0.5
Buildfile: /<>/build.xml
clean:
[echo] Removing 'nuxwdog' component directories ...
[echo] Completed removing 'nuxwdog' component directories.
clean_javadocs:
[echo] Removing 'nuxwdog' javadocs directory ...
[echo] Nothing to do!
[echo] Completed removing 'nuxwdog' javadocs directory.
compile_java:
[echo] Compiling 'nuxwdog' java code from 'src' into 'build/classes' ...
[mkdir] Created dir: /<>/build/classes
[javac] /<>/build.xml:59: warning: 'includeantruntime' was not
set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 1 source file to /<>/build/classes
[echo] Completed compiling 'nuxwdog' java code from 'src' into
'build/classes'.
build_jars:
[echo] Generating 'nuxwdog' jar files ...
[mkdir] Created dir: /<>/build/jars
[jar] Building jar: /<>/build/jars/nuxwdog.jar
[echo] Completed generating 'nuxwdog' jar files.
build_jni_headers:
[echo] Generating 'nuxwdog' java header files ...
[mkdir] Created dir: /<>/build/include
[echo] Completed generating 'nuxwdog' java header files.
build_header_files:
[echo] ${begin.build.headers.log.message}
[mkdir] Created dir: /<>/build/usr/include
[copy] Copying 2 files to /<>/build/usr/include
build:
[echo] Built classes, jars, and jni headers for the 'nuxwdog' component.
compose_javadocs:
[echo] Composing 'nuxwdog' javadocs ...
[echo] Nothing to do!
[echo] Completed composing 'nuxwdog' javadocs.
document:
[echo] Documented 'nuxwdog' javadocs.
distribute_binaries:
[echo] Creating 'nuxwdog' binary distributions ...
[mkdir] Created dir: /<>/dist/binary
[echo] Creating 'nuxwdog' binary wrappers ...
[echo] Nothing to do!
[echo] Completed creating 'nuxwdog' binary wrappers.
[echo] Creating 'nuxwdog' binary zip files ...
[zip] Building zip: /<>/dist/binary/nuxwdog-1.0.5.zip
[echo] Completed creating 'nuxwdog' binary zip files.
[echo] Creating 'nuxwdog' binary tar files ...
[tar] Building tar: /<>/dist/binary/nuxwdog-1.0.5.tar
[echo] Completed creating 'nuxwdog' binary tar files.
[echo] Creating 'nuxwdog' binary gzip files ...
[gzip] Building: /<>/dist/binary/nuxwdog-1.0.5.tar.gz
[delete] Deleting: /<>/dist/binary/nuxwdog-1.0.5.tar
[echo] Completed creating 'nuxwdog' binary gzip files.
[echo] Completed creating 'nuxwdog' binary distributions.
distribute_source:
[echo] Creating 'nuxwdog' source distributions ...
[mkdir] Created dir: /<>/dist/source
[echo] Creating 'nuxwdog' source zip files ...
[zip] Building zip: /<>/dist/source/nuxwdog-1.0.5.zip
[echo] Completed creating 'nuxwdog' source zip files.
[echo] Creating 'nuxwdog' source tar files ...
[tar] Building tar: /<>/dist/source/nuxwdog-1.0.5.tar
[echo] Completed creating 'nuxwdog' source tar files.
[echo] Creating 'nuxwdog' source gzip files ...
[gzip] Building: /<>/dist/source/nuxwdog-1.0.5.tar.gz
[delete] Deleting: /<>/dist/source/nuxwdog-1.0.5.tar
[echo] Completed creating 'nuxwdog' source gzip files.
[echo] Completed creating 'nuxwdog' source distributions.
distribute:
[echo] Distributed 'nuxwdog' distribution packages.
main:
[echo] Built, verified, documented, and distributed a fresh 'nuxwdog'
component.
BUILD SUCCESSFUL
Total time: 9 seconds
# run this here
dh_auto_configure -- \
--enable-64bit
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info
Bug#923012: squirrel3: FTBFS (Could not import extension sphinx.ext.pngmath)
Package: src:squirrel3
Version: 3.1-5
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
dh_autoreconf -a
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=cmake -- \
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu \
-DINSTALL_INC_DIR=include/squirrel3 \
-DDISABLE_STATIC="" -DLONG_OUTPUT_NAMES=""
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu -DINSTALL_INC_DIR=include/squirrel3
-DDISABLE_STATIC= -DLONG_OUTPUT_NAMES= ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
DISABLE_STATIC
LONG_OUTPUT_NAMES
-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
dh_auto_build -a
cd obj-x86_64-linux-gnu && make -j1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start
/<>/obj-x86_64-linux-gnu/CMakeFiles
/<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make -f squirrel/CMakeFiles/squirrel.dir/build.make
squirrel/CMakeFiles/squirrel.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends
"Unix Makefiles" /<> /<>/squirrel
/<>/obj-x86_64-linux-gnu
/<>/obj-x86_64-linux-gnu/squirrel
/<>/obj-x86_64-linux-gnu/squirrel/CMakeFiles/squirrel.dir/DependInfo.cmake
--color=
Scanning dependencies of target squirrel
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f squirrel/CMakeFiles/squirrel.dir/build.make
squirrel/CMakeFiles/squirrel.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 4%] Building CXX object squirrel/CMakeFiles/squirrel.dir/sqapi.cpp.o
cd /<>/obj-x86_64-linux-gnu/squirrel && /usr/bin/c++ -D_SQ64
-Dsquirrel_EXPORTS -I/<>/include -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -pedantic -fno-exceptions -fno-strict-aliasing
-fno-rtti -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -fno-rtti -std=c++0x -fPIC
-fno-exceptions -fno-strict-aliasing -Wall -Wextra -pedantic -Wcast-qual -o
CMakeFiles/squirrel.dir/sqapi.cpp.o -c /<>/squirrel/sqapi.cpp
/<>/squirrel/sqapi.cpp: In function 'SQRESULT
sq_setdelegate(HSQUIRRELVM, SQInteger)':
/<>/squirrel/sqapi.cpp:961:13: warning: this 'if' clause does not
guard... [-Wmisleading-indentation]
if(!_table(self)->SetDelegate(_table(mt))) return sq_throwerror(v,
_SC("delagate cycle")); v->Pop();}
^~
/<>/squirrel/sqapi.cpp:961:104: note: ...this statement, but the
latter is misleadingly indented as if it were guarded by the 'if'
if(!_table(self)->SetDelegate(_table(mt))) return sq_throwerror(v,
_SC("delagate cycle")); v->Pop();}
^
In file included from /<>/squirrel/sqobject.h:5,
from /<>/squirrel/sqpcheader.h:17,
from /<>/squirrel/sqapi.cpp:4:
/<>/squirrel/squtils.h: In instantiation of 'void
sqvector::remove(SQUnsignedInteger) [with T = SQObjectPtr; SQUnsignedInteger
= long long unsigned int]':
/<>/squirrel/sqarray.h:83:27: required from here
/<>/squirrel/squtils.h:97:20: warning: 'void* memmove(void*, const
void*, size_t)' writing to an object of type 'struct SQObjectPtr' with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memmove(&_vals[idx], &_vals[idx+1], sizeof(T) *
Processed: found 923008 in 3.2.18+dfsg-1, bug 923008 is forwarded to https://github.com/etcd-io/etcd/pull/10366 ...
Processing commands for cont...@bugs.debian.org: > found 923008 3.2.18+dfsg-1 Bug #923008 [src:etcd] CVE-2018-16886 Marked as found in versions etcd/3.2.18+dfsg-1. > forwarded 923008 https://github.com/etcd-io/etcd/pull/10366 Bug #923008 [src:etcd] CVE-2018-16886 Set Bug forwarded-to-address to 'https://github.com/etcd-io/etcd/pull/10366'. > tags 923008 + upstream Bug #923008 [src:etcd] CVE-2018-16886 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 923008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923009: seafile: CVE-2013-7469
Source: seafile Version: 6.2.11-1 Severity: grave Tags: security upstream Forwarded: https://github.com/haiwen/seafile/issues/350 Hi, The following vulnerability was published for seafile. CVE-2013-7469[0]: | Seafile through 6.2.11 always uses the same Initialization Vector (IV) | with Cipher Block Chaining (CBC) Mode to encrypt private data, making | it easier to conduct chosen-plaintext attacks or dictionary attacks. 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-2013-7469 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7469 [1] https://github.com/haiwen/seafile/issues/350 Regards, Salvatore
Processed: severity of 917030 is grave
Processing commands for cont...@bugs.debian.org: > severity 917030 grave Bug #917030 [src:python-pykmip] python-pykmip: CVE-2018-1000872 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 917030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923008: CVE-2018-16886
Source: etcd Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16886 and https://security-tracker.debian.org/tracker/CVE-2018-16886 Cheers, Moritz
Processed: Re: etcd: CVE-2018-1098 CVE-2018-1099
Processing commands for cont...@bugs.debian.org: > severity 921156 important Bug #921156 [src:etcd] etcd: CVE-2018-1098 CVE-2018-1099 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 921156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921156: etcd: CVE-2018-1098 CVE-2018-1099
severity 921156 important thanks On Tue, Feb 19, 2019 at 11:24:47PM -0600, Stephen Gelman wrote: > On Tue, 12 Feb 2019 09:32:48 +0700 Arnaud Rebillout > wrote: > > I looked into this a bit yesterday. > > > > As mentioned in the issue upstream at > > https://github.com/etcd-io/etcd/issues/9353, the fix has been merged in > > the master branch of etcd in March 2018, almost a year ago. The > > conversation also mentions that this will be part of the next release > > v3.4. However v3.4 has not been released yet. > > > > And I don't think we want to package a random commit from the master > > branch of etcd. So if we want to solve this bug simply by updating the > > package, we'll have to wait for v3.4 to be released. > > > > The other alternative is to cherry-pick the patch. > > > > If I'm not mistaken, the fix can be found in this MR: > > https://github.com/etcd-io/etcd/pull/9372/files. It's not a trivial > > patch. It's unlikely that we can apply it without modification on the > > etcd currently packaged in debian. > > > > I personally can't do that, as I know nothing about etcd anyway. I don't > > know if someone feels up to the task, or have a better idea about how to > > solve that. > > > > Cheers, > > > > Arnaud > > Since upstream still hasn't released a version that fixes the CVE is > this still considered a RC bug? Obviously it's better to fix it asap > but if upstream doesn't consider it critical I'm not sure this should > be RC. Let's downgrade and revisit when a fix has been backported to a 3.2.x release. Cheers, Moritz
Processed: found 923003 in 4:4.8.7+dfsg-17, tagging 923003
Processing commands for cont...@bugs.debian.org: > found 923003 4:4.8.7+dfsg-17 Bug #923003 [src:qt4-x11] CVE-2018-19873 CVE-2018-19871 CVE-2018-19870 Marked as found in versions qt4-x11/4:4.8.7+dfsg-17. > tags 923003 + upstream Bug #923003 [src:qt4-x11] CVE-2018-19873 CVE-2018-19871 CVE-2018-19870 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 923003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923003: CVE-2018-19873 CVE-2018-19871 CVE-2018-19870
Source: qt4-x11 Severity: grave Tags: security Three security issues fixed in QT5 also affect qt4-x11: https://blog.qt.io/blog/2018/12/04/qt-5-11-3-released-important-security-updates/ CVE-2018-19873: https://github.com/qt/qtbase/commit/621ab8ab59901cc3f9bd98be709929c9eac997a8 CVE-2018-19871: https://github.com/qt/qtimageformats/commit/7cfe47a8fe2f987fb2a066a696fb3d9d0afe4d65 (qt4-x11 affected in src/plugins/imageformats/tga/qtgafile.cpp) CVE-2018-19870: https://github.com/qt/qtbase/commit/2841e2b61e32f26900bde987d469c8b97ea31999 (qt4-x11 affected in src/gui/image/qgifhandler.cpp) Cheers, Moritz
Bug#921774: marked as done (ask: FTBFS (LaTeX error))
Your message dated Fri, 22 Feb 2019 21:49:04 +
with message-id
and subject line Bug#921774: fixed in ask 1.1.1-3
has caused the Debian Bug report #921774,
regarding ask: FTBFS (LaTeX error)
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.)
--
921774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ask
Version: 1.1.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2
dh_update_autotools_config -i
dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
make -C doc/
make[2]: Entering directory '/<>/doc'
pdflatex -shell-escape ask-manual.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian)
(preloaded format=pdflatex)
\write18 enabled.
entering extended mode
(./ask-manual.tex
LaTeX2e <2018-12-01>
[... snipped ...]
(/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.sty
(/usr/share/texlive/texmf-dist/tex/generic/xstring/xstring.tex))
(/usr/share/texlive/texmf-dist/tex/latex/framed/framed.sty)
(/usr/share/texlive/texmf-dist/tex/latex/float/float.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))system
returned with code 256
! Package minted Error: You must have `pygmentize' installed to use this packag
e.
See the minted package documentation for explanation.
Type H for immediate help.
...
l.17 \begin{document}
?
! Emergency stop.
...
l.17 \begin{document}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on ask-manual.log.
make[2]: *** [Makefile:22: ask-manual-1.1.1.pdf] Error 1
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:18: doc] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ask.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: ask
Source-Version: 1.1.1-3
We believe that the bug you reported is fixed in the latest version of
ask, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated ask 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
Bug#922995: marked as done (pycsw: FTBFS: dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1")
Your message dated Fri, 22 Feb 2019 21:21:12 + with message-id and subject line Bug#922995: fixed in pycsw 2.2.0+dfsg-6 has caused the Debian Bug report #922995, regarding pycsw: FTBFS: dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.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.) -- 922995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pycsw Version: 2.2.0+dfsg-5 Severity: serious Justification: fails to build from source Hi, pycsw recently started to FTBFS in a minimal up-to-date sid pbuilder environment: [...] debian/rules override_dh_install make[1]: Entering directory '/build/pycsw-2.2.0+dfsg' dh_install --list-missing dh_install: Please use dh_missing --list-missing/--fail-missing instead dh_install: This feature will be removed in compat 12. # Remove empty directories rmdir debian/*/usr/share/pycsw/tests/functionaltests/suites/harvesting/data/ rmdir debian/*/usr/share/pycsw/tests/functionaltests/suites/manager/data/ # Remove documentation outside usr/share/doc rm -f debian/*/usr/share/pycsw/tests/README.txt rm -f debian/*/usr/share/pycsw/tests/functionaltests/suites/apiso/data/README.txt rm -f debian/*/usr/share/pycsw/tests/functionaltests/suites/cite/data/README.txt make[1]: Leaving directory '/build/pycsw-2.2.0+dfsg' dh_apache2 -O--buildsystem=pybuild -O--parallel dh_installdocs -O--buildsystem=pybuild -O--parallel dh_sphinxdoc -O--buildsystem=pybuild -O--parallel dh_installchangelogs -O--buildsystem=pybuild -O--parallel dh_installexamples -O--buildsystem=pybuild -O--parallel dh_installman -O--buildsystem=pybuild -O--parallel dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1" (tried in .) dh_installman: Aborting due to earlier error make: *** [debian/rules:7: binary] Error 25 Andreas pycsw_2.2.0+dfsg-5.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pycsw Source-Version: 2.2.0+dfsg-6 We believe that the bug you reported is fixed in the latest version of pycsw, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated pycsw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Feb 2019 21:42:35 +0100 Source: pycsw Binary: pycsw pycsw-doc pycsw-wsgi python-pycsw python-pycsw-doc python-pycsw-wsgi python3-pycsw Architecture: source all Version: 2.2.0+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Description: pycsw - OGC compliant metadata (Catalogue Service for the Web) server pycsw-doc - OGC compliant metadata (Catalogue Service for the Web) server - d pycsw-wsgi - WSGI Apache CSW service based on pycsw python-pycsw - OGC compliant metadata (Catalogue Service for the Web) server - P python-pycsw-doc - Transitional dummy package to pycsw-doc python-pycsw-wsgi - Transitional dummy package to pycsw-wsgi python3-pycsw - OGC compliant metadata (Catalogue Service for the Web) server - P Closes: 922995 Changes: pycsw (2.2.0+dfsg-6) unstable; urgency=medium . * Team upload. * Bump Standards-Version to 4.3.0, no changes. * Fix man page installation. (closes: #922995) Checksums-Sha1: 6073baf86704d980f82ead48913c93ffa24f9833 2819 pycsw_2.2.0+dfsg-6.dsc 2515ee436c576692d6915563edd8a01f1aa6d904 17392 pycsw_2.2.0+dfsg-6.debian.tar.xz 18c702cdd35f569764c71075476998dc776b2785 98136 pycsw-doc_2.2.0+dfsg-6_all.deb 5db24bc3c238b1949f34d45306e3b6adc023554b 124336 pycsw-wsgi_2.2.0+dfsg-6_all.deb 812719575be8e4c80062cec29192ffb5c6d9a39c 20796 pycsw_2.2.0+dfsg-6_all.deb dd91fb0f915f0a83863599e3256099bdd81f4e07 12643 pycsw_2.2.0+dfsg-6_amd64.buildinfo 99d86be831ea16a92d2bd4fa7fc4ca1505c04ef1 12084 python-pycsw-doc_2.2.0+dfsg-6_all.deb d0e6c1ae4565c2a14d1c11734ec340173c67ca06 12088 python-pycsw-wsgi_2.2.0+dfsg-6_all.deb 02e399731fafb1351289d2bcd2a9f9d8993f66db 243892 python-pycsw_2.2.0+dfsg-6_all.deb a802540d8714992d3075150c8c9ff20572e5a4d5
Processed: Re: Bug#922995: pycsw: FTBFS: dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1"
Processing control commands: > tags -1 pending Bug #922995 [src:pycsw] pycsw: FTBFS: dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1" Added tag(s) pending. -- 922995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922995: pycsw: FTBFS: dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1"
Control: tags -1 pending On 2/22/19 8:27 PM, Andreas Beckmann wrote: > dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1" > (tried in .) ronn apparently changed behaviour: ronn debian/man/pycsw-admin.md roff: debian/man/pycsw-admin.md.1 html: debian/man/pycsw-admin.md.1.html +man Fixed by renaming the file. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#921590: marked as done (xen-utils-4.11: pygrub bails out with "ImportError: No module named fsimage")
Your message dated Fri, 22 Feb 2019 21:22:03 +0100
with message-id
and subject line Re: [Pkg-xen-devel] Bug#921590: xen-utils-4.11: pygrub bails
out with "ImportError: No module named fsimage"
has caused the Debian Bug report #921590,
regarding xen-utils-4.11: pygrub bails out with "ImportError: No module named
fsimage"
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.)
--
921590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xen-utils-4.11,xen-utils-common
Version: 4.11.1-1
Severity: serious
Control: affects -1 xen-tools
Hi,
both, /usr/lib/xen-4.11/bin/pygrub as well as /usr/bin/pygrub bail out
for me as follows on Buster:
# /usr/bin/pygrub
Traceback (most recent call last):
File "/usr/bin/pygrub", line 23, in
import fsimage
ImportError: No module named fsimage
This is a regression from Stretch and breaks many DomUs after upgrade as
well as most DomUs generated with xen-tools' defaults (which uses
pygrub). It especially severly harms the release testing for the
xen-tools pending 4.8 release. :-(
This seems related (and partially mentioned), but not identical to
#912441 as pygrub is present for me, just not working at all. Which
means: This bug report is about pygrub being present, but completely
broken.
There aren't many differences between pygrub in Stretch and Buster:
1c1
< #! /usr/bin/python2.7
---
> #! /usr/bin/python
22,23d21
<
< sys.path.insert(1, sys.path[0] + '/../lib/python')
That's all differences.
The latter removal of a search path is very likely the reason for this
issue. (Already hinted towards that in #912441, too.)
As a (very ugly) workaround I tried to copy over pygrub from a Stretch
Dom0, i.e. from xen-utils-4.8, but this helped only partially:
# pygrub
Traceback (most recent call last):
File "/usr/bin/pygrub", line 25, in
import fsimage
ImportError: libfsimage.so: cannot open shared object file: No such file or
directory
Note the different error message on the last line. Now it doesn't find
libfsimage.so.
"strace /usr/lib/xen-4.11/bin/pygrub" reveals that pygrub from
xen-utils-4.8, when copied onto a Buster system, indeed tries to access
that /usr/lib/xen-4.11/lib/python/fsimage.so, just doesn't use it:
# strace /usr/lib/xen-4.11/bin/pygrub |& fgrep -A20 lib/python/fsimage.so
--color
openat(AT_FDCWD, "/usr/lib/xen-4.11/bin/../lib/python/fsimage.so", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=16128, ...}) = 0
openat(AT_FDCWD, "/usr/lib/xen-4.11/bin/../lib/python/fsimage.so",
O_RDONLY|O_CLOEXEC) = 4
read(4, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0p\21\0\0\0\0\0\0"...,
832) = 832
fstat(4, {st_mode=S_IFREG|0644, st_size=16128, ...}) = 0
mmap(NULL, 18352, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0x7f1af1082000
mmap(0x7f1af1083000, 4096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x1000) = 0x7f1af1083000
mmap(0x7f1af1084000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4,
0x2000) = 0x7f1af1084000
mmap(0x7f1af1085000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x2000) = 0x7f1af1085000
close(4)= 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=49493, ...}) = 0
mmap(NULL, 49493, PROT_READ, MAP_PRIVATE, 4, 0) = 0x7f1af0f92000
close(4)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/x86_64/libfsimage.so",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64/x86_64", 0x7fff92e70430) = -1 ENOENT (No
such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/libfsimage.so",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff92e70430) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/libfsimage.so",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff92e70430) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/libfsimage.so", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls", 0x7fff92e70430) = -1 ENOENT (No such file or
directory)
Reason for this seems to be that the linker doesn't find libfsimage.so:
# ldd /usr/lib/xen-4.11/lib/python/fsimage.so
linux-vdso.so.1 (0x7fff1bbb5000)
libfsimage.so
Bug#859553: pidentd: Please migrate to openssl1.1 in buster
On Thu, Feb 21, 2019 at 11:37:02PM +0100, Sebastian Andrzej Siewior wrote: > The debian maintainer of this package looks MIA. Nobody spoke up for > keeping it so far. I'm happy to NMU it so it builds against libssl-dev > but I see little to no reason for it. I think we have alternatives which > *are* in Buster. > Would you mind filling a RM request? I've just filed a RM bug. Cheers, Moritz
Bug#919755: marked as done (libimagequant doesn't use the baseline on i386)
Your message dated Fri, 22 Feb 2019 19:49:37 + with message-id and subject line Bug#919755: fixed in libimagequant 2.12.2-1.1 has caused the Debian Bug report #919755, regarding libimagequant doesn't use the baseline on i386 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.) -- 919755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libimagequant Version: 2.12.1-2 Severity: serious Tags: sid buster the package is built using -DUSE_SSE=1 -msse -mfpmath=sse on i386, which is not the i386 baseline. --- End Message --- --- Begin Message --- Source: libimagequant Source-Version: 2.12.2-1.1 We believe that the bug you reported is fixed in the latest version of libimagequant, 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. Adrian Bunk (supplier of updated libimagequant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 07 Feb 2019 20:39:50 +0200 Source: libimagequant Architecture: source Version: 2.12.2-1.1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Adrian Bunk Closes: 919755 Changes: libimagequant (2.12.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix the baseline violation on i386. (Closes: #919755) Checksums-Sha1: 43cee2d4b4b4e374087a75b35134f8632a914cae 2139 libimagequant_2.12.2-1.1.dsc db72696ef767c232fcefd81b3e4709dbc74b7330 2712 libimagequant_2.12.2-1.1.debian.tar.xz Checksums-Sha256: 5a0a4fbdf96910eb5df9481d67c7cf98906ca31adb228ccc33046e5b6bb7b782 2139 libimagequant_2.12.2-1.1.dsc a86d06e81e925255f0d73b3942f8a3fcf3d880cc0a3dc903ed8ffb39a91c2fd6 2712 libimagequant_2.12.2-1.1.debian.tar.xz Files: 7199fa77699cdbf1baca157c2c15a2b1 2139 graphics optional libimagequant_2.12.2-1.1.dsc 5efdd95c5a0fc0e1d90fb1e80197b083 2712 graphics optional libimagequant_2.12.2-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlxcfNkACgkQiNJCh6LY mLGWKw//cLxDTzqmy0PNVRQaAj1M3zsq5JD5SLPhmXPDk3fDhTpxIrdAqoUxX4nN IuTDFF1rv+fL7NwhW7kONwvux9UDagnLyXRO57xDtFebV5QD5I0GDMrTQsdU5N85 5TCXL9niLdyaw5NsthDZxUTIy3Dn3c5UFc/SASPcZ4I0aZcrYjV/kz9JCPfeRr5t MahnZUVmPR4R2QJUXUfnjcAQH2yrmN/rb4SeMgCGUXIJXjceR6HOgN4BkZNxSqCN kA8pt7E4CrnrmyZyETtgEm2F+OkJIaDhn7YApnKE7xI8c3LlY4J+ErEdgEqTBnRz XYnWwzTPGwPkLdnoJlNyh2f+qRZqE2oiEOW7UTsYiOikkqfFlRr8Pgb34fxSvK3X SpK+DXuMsSIeNKCIOBBDhiSUOqNLORGZnfblOrFJUiFJmuu2St3WoR0RFhgvXEGy /bk7R/iMKe3Ydfyrie4/tRVdmu/2iV+2WGicEbqrZ6sHzN9tITCQ0LZ60bIZdVTN tU7DqWyGpAcoJqVLj0vrePSXTDl7RM19LAlehNtZ3A6XkASq8Bf1Xa/nrvERWuls Pv1UmRZ1cpQknjI+cT7KvqIG+SUV4O4XImcSrinIN79wNuwwuKP1ztG2FK1Pyat2 fjVp3S1b544imk2x84nJTLM+Azb1ox9CZJtRoY5jMylqH5g9OkI= =NfwH -END PGP SIGNATURE End Message ---
Bug#922995: pycsw: FTBFS: dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1"
Source: pycsw Version: 2.2.0+dfsg-5 Severity: serious Justification: fails to build from source Hi, pycsw recently started to FTBFS in a minimal up-to-date sid pbuilder environment: [...] debian/rules override_dh_install make[1]: Entering directory '/build/pycsw-2.2.0+dfsg' dh_install --list-missing dh_install: Please use dh_missing --list-missing/--fail-missing instead dh_install: This feature will be removed in compat 12. # Remove empty directories rmdir debian/*/usr/share/pycsw/tests/functionaltests/suites/harvesting/data/ rmdir debian/*/usr/share/pycsw/tests/functionaltests/suites/manager/data/ # Remove documentation outside usr/share/doc rm -f debian/*/usr/share/pycsw/tests/README.txt rm -f debian/*/usr/share/pycsw/tests/functionaltests/suites/apiso/data/README.txt rm -f debian/*/usr/share/pycsw/tests/functionaltests/suites/cite/data/README.txt make[1]: Leaving directory '/build/pycsw-2.2.0+dfsg' dh_apache2 -O--buildsystem=pybuild -O--parallel dh_installdocs -O--buildsystem=pybuild -O--parallel dh_sphinxdoc -O--buildsystem=pybuild -O--parallel dh_installchangelogs -O--buildsystem=pybuild -O--parallel dh_installexamples -O--buildsystem=pybuild -O--parallel dh_installman -O--buildsystem=pybuild -O--parallel dh_installman: Cannot find (any matches for) "debian/man/pycsw-admin.1" (tried in .) dh_installman: Aborting due to earlier error make: *** [debian/rules:7: binary] Error 25 Andreas pycsw_2.2.0+dfsg-5.log.gz Description: application/gzip
Processed: closing 922955, closing 922954, closing 922953
Processing commands for cont...@bugs.debian.org: > close 922955 1:9.11.5.P4+dfsg-1 Bug #922955 [src:bind9] bind9: CVE-2019-6465: Zone transfer controls for writable DLZ zones were not effective The source 'bind9' and version '1:9.11.5.P4+dfsg-1' do not appear to match any binary packages Marked as fixed in versions bind9/1:9.11.5.P4+dfsg-1. Bug #922955 [src:bind9] bind9: CVE-2019-6465: Zone transfer controls for writable DLZ zones were not effective Marked Bug as done > close 922954 1:9.11.5.P4+dfsg-1 Bug #922954 [src:bind9] bind9: CVE-2018-5745: An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys The source 'bind9' and version '1:9.11.5.P4+dfsg-1' do not appear to match any binary packages Marked as fixed in versions bind9/1:9.11.5.P4+dfsg-1. Bug #922954 [src:bind9] bind9: CVE-2018-5745: An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys Marked Bug as done > close 922953 1:9.11.5.P4+dfsg-1 Bug #922953 [src:bind9] bind9: CVE-2018-5744: A specially crafted packet can cause named to leak memory The source 'bind9' and version '1:9.11.5.P4+dfsg-1' do not appear to match any binary packages Marked as fixed in versions bind9/1:9.11.5.P4+dfsg-1. Bug #922953 [src:bind9] bind9: CVE-2018-5744: A specially crafted packet can cause named to leak memory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 922953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922953 922954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922954 922955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922953: closing 922955, closing 922954, closing 922953
close 922955 1:9.11.5.P4+dfsg-1 close 922954 1:9.11.5.P4+dfsg-1 close 922953 1:9.11.5.P4+dfsg-1 thanks Close bugs accordingly as the fixes landed in the 1:9.11.5.P4+dfsg-1 version.
Bug#922986: Invalid user/group name or numeric ID, ignoring: systemd-journal,postdrop
Package: prometheus-postfix-exporter Version: 0.1.2-2 Severity: serious Hi, Systemd is complaining about: Invalid user/group name or numeric ID, ignoring: systemd-journal,postdrop Apparently the separator is a white space, not a coma. Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prometheus-postfix-exporter depends on: ii libc62.28-7 pn postfix ii python 2.7.15-4 ii rsyslog [system-log-daemon] 8.40.0-1+b1 ii systemd-sysv 241-1 prometheus-postfix-exporter recommends no packages. prometheus-postfix-exporter suggests no packages.
Processed: severity 922772 normal
Processing commands for cont...@bugs.debian.org: > severity 922772 normal Bug #922772 [redmine] redmine: start via unicorn fails Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 922772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921953: marked as done (apacheds: Apacheds fails to start after clean installation)
Your message dated Fri, 22 Feb 2019 15:04:14 + with message-id and subject line Bug#921953: fixed in apache-directory-server 2.0.0~M24-3 has caused the Debian Bug report #921953, regarding apacheds: Apacheds fails to start after clean installation 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.) -- 921953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apacheds Version: 2.0.0~M24-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Fresh installation of buster using default options, then tried to install apacheds. * What exactly did you do (or not do) that was effective (or ineffective)? apt-get install apacheds * What was the outcome of this action? Feb 10 14:35:14 testdap2 systemd[1]: Started Apache Directory Server. Feb 10 14:35:17 testdap2 sh[46942]: [2019-35-10T14:35:17.017+] ERROR [org.apache.directory.server.UberjarMain] - Failed to start the service. Feb 10 14:35:17 testdap2 sh[46942]: org.apache.directory.api.ldap.model.exception.LdapOperationException: /usr/share/apacheds/instances/default/conf/ou=config.ldif (Permission denied) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.core.partition.ldif.LdifPartition.addEntry(LdifPartition.java:790) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.core.partition.ldif.LdifPartition.add(LdifPartition.java:263) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.config.ConfigPartitionInitializer.initConfigPartition(ConfigPartitionInitializer.java:181) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.initConfigPartition(ApacheDsService.java:335) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:187) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:153) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.start(UberjarMain.java:151) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.main(UberjarMain.java:77) Feb 10 14:35:17 testdap2 sh[46942]: Caused by: java.io.FileNotFoundException: /usr/share/apacheds/instances/default/conf/ou=config.ldif (Permission denied) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.open0(Native Method) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.(FileOutputStream.java:237) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.(FileOutputStream.java:187) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileWriter.(FileWriter.java:96) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.core.partition.ldif.LdifPartition.addEntry(LdifPartition.java:784) Feb 10 14:35:17 testdap2 sh[46942]: ... 7 more Feb 10 14:35:17 testdap2 systemd-journald[10273]: Forwarding to syslog missed 7 messages. Feb 10 14:35:17 testdap2 sh[46942]: [2019-35-10T14:35:17.017+] ERROR [org.apache.directory.server.UberjarMain] - Failed to start the service. Feb 10 14:35:17 testdap2 sh[46942]: java.lang.NullPointerException Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.stop(ApacheDsService.java:635) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.stop(UberjarMain.java:219) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.start(UberjarMain.java:158) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.main(UberjarMain.java:77) Feb 10 14:35:17 testdap2 systemd[1]: apacheds.service: Main process exited, code=exited, status=1/FAILURE Feb 10 14:35:17 testdap2 systemd[1]: apacheds.service: Failed with result 'exit-code'. * What outcome did you expect instead? A running apacheds instance. I also looked for a README.Debian in the /usr/share/doc/apacheds folder for any other instructions, but no such file. Regards, Johan -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.15.18-10-pve (SMP w/24 CPU cores) Kernel taint flags:
Bug#916375: [debian-mysql] Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded
Potentially related: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916375 apache2: Segmentation fault when mod_perl.so is enabled - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918988 libmysqlclient symbol conflict segfaulted Apache - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920619 libaprutil1-dbd-mysql should also be added to the Breaks-list
Bug#921488: Bug #921488 in mariadb-10.3 marked as pending
Control: tag -1 pending Hello, Bug #921488 in mariadb-10.3 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/21008f9fdfe0f13a360c61034ead65d3ae144606 Use bundled SSL libraries instead of system OpenSSL (Closes: #921488) It has been disputed whether MySQL and MariaDB can license-wise use OpenSSL or not. Building with '-DWITH_SSL=bundled' makes the server use YaSSL and the Connector/C use GnuTLS. Once OpenSSL 3.0 is released, switch back to it. Since OpenSSL is missing, libmariadb3 will lack the sha256_password plugin. (this message was generated automatically) -- Greetings https://bugs.debian.org/921488
Processed: Bug #921488 in mariadb-10.3 marked as pending
Processing control commands: > tag -1 pending Bug #921488 [libmariadb3] libmariadb3: OpenSSL license contamination of GPL reverse-dependencies Added tag(s) pending. -- 921488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Please test again: my_print_defaults and Akonadi for a freash installation
Processing control commands: > tags -1 +moreinfo Bug #910902 [mariadb-server] mariadb-server-core: do not provides my_print_defaults anymore Added tag(s) moreinfo. -- 910902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910902: Please test again: my_print_defaults and Akonadi for a freash installation
Control: tags -1 +moreinfo Hello! > mariadb moved my_print_defaults from mysql-server-core to mariadb-server. > So akonadi-backend-mysql do now need to depend at mariadb-server. As > "my_print_defaults" is only needed at first start of akonadi it is a pity if > we > would that for now rely on a full istalled mariadb-server. Can you please > clearify why this move was done? If you look at https://packages.debian.org/stretch/amd64/mariadb-server-core-10.1/filelist there is no my_print_defaults However since 10.3 there is: https://packages.debian.org/sid/amd64/mariadb-server-core-10.3/filelist /usr/bin/my_print_defaults .. /usr/share/man/man1/my_print_defaults.1.gz Your question is the other way around. Can you please test again if this is actually a issue with MariaDB 10.3 or something else? Are you using the MariaDB from official Debian repositories?
Bug#920584: marked as done (python-plastex: cannot correctly import PIL; cannot process images)
Your message dated Fri, 22 Feb 2019 13:20:03 +
with message-id
and subject line Bug#920584: fixed in plastex 1.0.0-1
has caused the Debian Bug report #920584,
regarding python-plastex: cannot correctly import PIL; cannot process images
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.)
--
920584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-plastex
Version: 0.9.2-1.2
Severity: serious
Tags: + patch
Justification: Renders package (almost) useless
Dear Maintainer,
Various python-imaging/python-pil imports have changed over time and plastex
in Debian has almost kept up with them. It currently depends on python-pil but
does not correctly import from PIL and so claims that python-pil is not
installed; images within the documentation cannot be processed in this state.
Since (almost) all documentation contains images, this means that plastex
misrenders the documentation. (The only build-rdep of plastex in the archive
makes heavy use of images in its documentation and is affected by this bug.)
Patch attached and MR to follow.
regards
Stuart
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages python-plastex depends on:
ii dvipng 1.15-1.1
ii python 2.7.15-4
ii python-pil 5.4.1-1
ii texlive-latex-base 2018.20190122-1
Versions of packages python-plastex recommends:
ii python-cheetah 3.1.0-3
ii python-genshi 0.7-6
ii python-kid 0.9.6-3
python-plastex suggests no packages.
-- no debconf information
commit 156f57a99896710e64ce3b42248abc849e52f7b6
Author: Stuart Prescott
Date: Sun Jan 27 18:44:28 2019 +1100
Fix import of PIL after rename
diff --git a/debian/changelog b/debian/changelog
index 2f22e5d..f5d3226 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,15 @@
plastex (0.9.2-2) UNRELEASED; urgency=medium
+ [ Ondřej Nový ]
* d/changelog: Remove trailing whitespaces
* d/control: Remove trailing whitespaces
* Remove debian/pycompat, it's not used by any modern Python helper
* Convert git repository from git-dpm to gbp layout
* d/watch: Use https protocol
+ [ Stuart Prescott ]
+ * Correctly import PIL
+
-- Ondřej Nový Mon, 12 Mar 2018 23:22:35 +0100
plastex (0.9.2-1.2) unstable; urgency=low
diff --git a/debian/patches/pilimport.diff b/debian/patches/pilimport.diff
new file mode 100644
index 000..1bd4f91
--- /dev/null
+++ b/debian/patches/pilimport.diff
@@ -0,0 +1,15 @@
+diff --git a/plasTeX/Imagers/__init__.py b/plasTeX/Imagers/__init__.py
+index 199fafe..ac26238 100644
+--- a/plasTeX/Imagers/__init__.py
b/plasTeX/Imagers/__init__.py
+@@ -13,8 +13,8 @@ depthlog = getLogger('render.images.depth')
+ status = getLogger('status')
+
+ try:
+-import Image as PILImage
+-import ImageChops as PILImageChops
++from PIL import Image as PILImage
++from PIL import ImageChops as PILImageChops
+ except ImportError:
+ PILImage = PILImageChops = None
+
diff --git a/debian/patches/series b/debian/patches/series
index 20a73cb..d64a4e1 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
03_template_icon_links.diff
remove_cgpdfpng.patch.diff
02_shebang.diff
+pilimport.diff
--- End Message ---
--- Begin Message ---
Source: plastex
Source-Version: 1.0.0-1
We believe that the bug you reported is fixed in the latest version of
plastex, 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 plastex 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, 22 Feb 2019 13:50:23 +0100
Source: plastex
Binary: python-plastex python-plastex-doc
Architecture: source
Version: 1.0.0-1
Bug#922956: marked as done (libgd-perl: no longer Provides libgd-gd2-noxpm-perl and libgd-gd2-perl )
Your message dated Fri, 22 Feb 2019 12:50:16 + with message-id and subject line Bug#922956: fixed in libgd-perl 2.71-2 has caused the Debian Bug report #922956, regarding libgd-perl: no longer Provides libgd-gd2-noxpm-perl and libgd-gd2-perl 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.) -- 922956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgd-perl Version: 2.71-1 Severity: serious In the switch from cdbs to dh (commit f8669559ff6c), libgd-perl lost its Provides for libgd-gd2-noxpm-perl and libgd-gd2-perl. This breaks various reverse dependencies. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-rc7-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgd-perl depends on: ii libc6 2.28-7 ii libgd3 2.2.5-5.1 ii perl5.28.1-4 pn perlapi-5.28.1 libgd-perl recommends no packages. libgd-perl suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libgd-perl Source-Version: 2.71-2 We believe that the bug you reported is fixed in the latest version of libgd-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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libgd-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: Fri, 22 Feb 2019 13:33:25 CET Source: libgd-perl Binary: Architecture: source Version: 2.71-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Description: Closes: 922956 Changes: libgd-perl (2.71-2) unstable; urgency=medium . * Team upload. * Add back Provides/Replaces/Breaks on libgd-gd2-noxpm-perl and libgd- gd2-perl which got lost in the cdbs → dh transition. Thanks to Sven Joachim for the bug report. (Closes: #922956) Checksums-Sha256: 319ba8c1257c0082df259251c700e597072b2829387495f077fbe3b2068cd36a 2369 libgd-perl_2.71-2.dsc 9dbcd58ffa839642c26d9f747e4979d64061218a03153036009828743213ce59 14572 libgd-perl_2.71-2.debian.tar.xz 958f14ddb65260a4f643ade796029aef3565a8ad352fd6defd7e8cd0950c307b 7363 libgd-perl_2.71-2_sourceonly.buildinfo Checksums-Sha1: 82f5e50159dd44379cb5768368174285f76852bd 2369 libgd-perl_2.71-2.dsc dd3687fd0b90f1bdda0c73156a14b5c559465d4f 14572 libgd-perl_2.71-2.debian.tar.xz b0e43c3b4dde5ee5a55d727ec31500246453f22b 7363 libgd-perl_2.71-2_sourceonly.buildinfo Files: 9be40a5db296ac8277a4d25a41b4caa6 2369 perl optional libgd-perl_2.71-2.dsc 5981972f7c8b09d3157eba5597d9e14e 14572 perl optional libgd-perl_2.71-2.debian.tar.xz 2ac1d6283bf50c4dce096f841248e131 7363 - - libgd-perl_2.71-2_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlxv7BVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbnfBAAwxZFyG7JZkGQJ4PFNGSjlT8a/+qia5L88/LHZsF7mgVG4m5nBBawxLq2 pjipTUZlA8NFfw6tXxJs4ep3Mgpd5xd2pOaAF0dhHl0Q9J79OfRZYzouKA6VOMgr VP8dau6GESbxMv0ZXLRd9G95+Z2GfNrKpvTY3qLvcvr1oI8V7aoS89HgWaOPyUyJ NlhQySLnCXVdXGnlO+c14TTL7G7DdrQneyLEkG86zptg9bwBdkn4OJa4YZI+t3mB 3QyPGQkL5RDRpKA8O/Gku1veBMo9Gywq+yUFrqSoD2duQkqOrdWVz3V5Af+CL3lw 87sfTngkbBS7+5ISXyCw9aIFzC5U1dUs00MP9qpYSnrYcfy6u88qV35h7fa99Cz5 id5ncAxKS/EPahNjKi/3YkW4qzJPeTrc/grZF+jUX+qruvKVNSASEZG8HpZC71h9 kD8C3Gyjut8SfbNi2lfpArKkLDxdI0Lc7rkI57I99bykZE4bRaYiZbbjHylo/Uod sO/7SgEDrFoyG+JSOfCUIbEFhpYtQGlvplGD8RBpqHRLz/NFtAYZeQ9PKHBvY7hF i6rkOwhgQImdT0LCxxG6yK/flbO8RWRE4vXXzHfArMDfeNdGUTQ073AvZ6eNFv+5 0qWP9vO2n3lJibcJv9lN8mFyGucrQF+x9d/IBmgPNGUT2puK4yA= =834O -END PGP SIGNATURE End Message ---
Processed: Re: Bug#922960: new libcapstone-dev pkg-config does not provide include path, breaks compatibility
Processing control commands: > severity -1 serious Bug #922960 [libcapstone-dev] new libcapstone-dev pkg-config does not provide include path, breaks compatibility Severity set to 'serious' from 'normal' -- 922960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921897: marked as done (morse-simulator: FTBFS (Could not import extension sphinx.ext.pngmath))
Your message dated Fri, 22 Feb 2019 10:50:47 + with message-id and subject line Bug#921897: fixed in morse-simulator 1.4-5 has caused the Debian Bug report #921897, regarding morse-simulator: FTBFS (Could not import extension sphinx.ext.pngmath) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:morse-simulator Version: 1.4-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python3 dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DBUILD_DOC_SUPPORT=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 \ -DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_DOC_SUPPORT=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 -DCPACK_DEBIAN_PACKAGE_DEPENDS=python3-all-dev -DPYMORSE_SUPPORT=ON .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done [... snipped ...] CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_SYSCONFDIR CPACK_DEBIAN_PACKAGE_DEPENDS -- Build files have been written to: /<>/obj-x86_64-linux-gnu make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' cp version.py obj-*/ dh_auto_build cd obj-x86_64-linux-gnu && make -j1 make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/depend make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/man.dir/DependInfo.cmake --color= Scanning dependencies of target man make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' env PYTHONPATH=/<>/obj-x86_64-linux-gnu:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/fakeenv:/<>/src:/<>/testing:/<>/bindings/pymorse/src/:$PYTHONPATH PYTHONDONTWRITEBYTECODE="morse" MORSESOURCE=/<> /usr/bin/python3 /usr/bin/sphinx-build -b man -c /<>/obj-x86_64-linux-gnu/doc /<>/doc/man /<>/obj-x86_64-linux-gnu/doc/man && /bin/gzip -f /<>/obj-x86_64-linux-gnu/doc/man/*.1 Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named 'sphinx.ext.pngmath') make[4]: *** [CMakeFiles/man.dir/build.make:60: CMakeFiles/man] Error 2 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:140: CMakeFiles/man.dir/all] Error 2 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [Makefile:144: all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2 make[1]: *** [debian/rules:27: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here:
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Le lundi, 18 février 2019, 08.58:53 h CET Didier 'OdyX' Raboud a écrit :
> Dear Technical Committee members,
> (CC'ed to submitter, and debootstrap maintainers for information and
> feedack)
>
> Here's the current state of the draft resolution; which `master` is at
> https://salsa.debian.org/debian/tech-ctte/blob/master/914897_merged_usr/ball
> ot.md
>
> I will submit it to vote on Friday 22.; the discussion period is open!
Thank you for the various comments. I have amended the ballot (which is more a
"explanation text + short ballot" incorporating the suggestions from the IRC
meeting as well as taking into accounts remarks on this bug.
I intend to answer some mails on that bug, and call for a vote on Sunday I
guess.
See:
https://salsa.debian.org/debian/tech-ctte/blob/master/914897_merged_usr/ballot.md
for the markdown-rendered version; and below:
# #914897: tech-ctte: Should debootstrap disable merged `/usr` by default?
## What is "merged `/usr`"
"Merged `/usr`" describes a possible future standard directories scheme in
which the `/{bin,sbin,lib*}/` directories have been made superfluous through
replacing them by symlinks to their `/usr` equivalents
(`/usr/{bin,sbin,lib*}`).
The motivation to get Debian systems to converge towards such a scheme is
vastly documented elsewhere ([FDO's TheCaseForTheUsrMerge][0],
[wiki.d.o UsrMerge][1]) but can be summarized as the following points:
* having separate `/` and `/usr` filesystems has been useful in the past for
booting without initramfs onto a minimal root filesystem that carried just
enough to mount the `/usr` filesystem later in the boot process. Given the
evolution of physical hosts' capabilities, initramfs'es have been default in
Debian (and elsewhere) for a long time, and most systems no longer have an
intermediate state during boot in which they have only `/`, but not `/usr`,
mounted. Booting hosts through that intermediate state is not systematically
tested in Debian anymore.
* another use-case is to share system files from `/usr` between hosts (over a
network link) or containers (locally) which use different data or
configuration. Having all software under `/usr` (instead of spread between `/`
and `/usr`) makes the centralized update and the sharing easier.
* the packaging infrastructure to install files outside of `/usr` (e.g.
installing libs under `/lib` instead of `/usr/lib`) is not standard and
represents technical debt.
* given its status as remnant "folklore", the distinction between what _needs_
to be shipped in `/` and what can stay in `/usr` is often interpreted
arbitrarily;
* allowing shipment of identically-named libraries or binaries in different
paths can confuse common understanding of paths precedence.
[0]: https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
[1]: https://wiki.debian.org/UsrMerge
The arguments against moving the base directories' scheme towards
"merged `/usr`" are as follows:
* there's no gain in disrupting something that is not inherently broken;
* `/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks create confusing
views of the system (`/bin/cat` and `/usr/bin/cat` are the same file), and
dpkg doesn't support this situation cleanly:
[#134758](https://bugs.debian.org/134758).
* it is possible for distributions to converge towards having all system files
in `/usr` in finite time instead of shortcutting this migration with
`/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks.
The compatibility symbolic links `/lib` → `/usr/lib` and `/lib64` →
`/usr/lib64` are required by the various CPUs' platform ABIs (for example i386
requires `/lib/ld-linux.so.2` to resolve to glibc's `ld.so`, and amd64
requires `/lib64/ld-linux-x86-64.so.2`) so there are no plans to remove them
altogether. Similarly, removing `/bin` is not under consideration because it
would break the assumption that `/bin/sh` exists, and removing `/sbin` would
break the assumption that `/sbin/fsck.*` and `/sbin/mount.*` exist.
## "merged `/usr`" in Debian
In Debian buster, the current testing suite, "merged `/usr`" is only
considered for implementation with symlinks (there are no proposals for simply
dropping `/{bin,sbin,lib*}`) and is implemented in two main ways:
* existing hosts can be made to have a "merged `/usr`" by installing the
[usrmerge][2] package;
* new hosts get the `/{bin,sbin,lib*}/`→ `/usr/{bin,sbin,lib*}/` symlinks by
default when using debootstrap >= 1.0.102.
The usrmerge package contains a `/usr/lib/convert-usrmerge` perl executable
that runs in `postinst`, that will move the contents of `/{bin,sbin,lib*}/`
and replace these directories with symlinks when empty.
It is also possible to merge `/usr` in other ways, for example with
`debootstrap --merged-usr` or by bootstrapping into a chroot that already
contains the necessary symlinks.
[2]: https://tracker.debian.org/pkg/usrmerge
## Issues from "merged `/usr`"
Since the default change in debootstrap 1.0.102, some issues have arisen.
Due to the fact that
Bug#922957: python-igraph's tests fail with Python 3.7 on Windows10 (version python-igraph/0.7.1.post6-6)
Package: src:python-igraph
Version: 0.7.1.post6-6
Severity: serious
python-igraph's tests fail with Python 3.7, RC severity for the upcoming Python
3.7 transition.
..E.E..E...
==
ERROR: testFormula (igraph.test.generators.GeneratorTests)
--
Traceback (most recent call last):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\test\generators.py",
line 72, in testFormula
g = Graph.Formula(formula)
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 209, in construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 90, in generate_edges
raise SyntaxError(msg)
File "", line None
SyntaxError: invalid token found in edge specification: A
==
ERROR: testPickle (igraph.test.foreign.ForeignTests)
--
Traceback (most recent call last):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\test\foreign.py",
line 207, in testPickle
g = Graph.Read_Pickle(pickle)
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\__init__.py",
line 1829, in Read_Pickle
fp = open(fname, "rb")
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: invalid
start byte
==
ERROR: testCohesiveBlocks2 (igraph.test.decomposition.CohesiveBlocksTests)
--
Traceback (most recent call last):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\test\decomposition.py",
line 329, in testCohesiveBlocks2
g = Graph.Formula("1-2:3:4:5:6, 2-3:4:5:7, 3-4:6:7, 4-5:6:7, "
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 209, in construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 90, in generate_edges
raise SyntaxError(msg)
File "", line None
SyntaxError: invalid token found in edge specification: 1-2:3:4:5:6
--
Ran 307 tests in 2.798s
FAILED (errors=3)
Bug#922956: libgd-perl: no longer Provides libgd-gd2-noxpm-perl and libgd-gd2-perl
Package: libgd-perl Version: 2.71-1 Severity: serious In the switch from cdbs to dh (commit f8669559ff6c), libgd-perl lost its Provides for libgd-gd2-noxpm-perl and libgd-gd2-perl. This breaks various reverse dependencies. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-rc7-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgd-perl depends on: ii libc6 2.28-7 ii libgd3 2.2.5-5.1 ii perl5.28.1-4 pn perlapi-5.28.1 libgd-perl recommends no packages. libgd-perl suggests no packages. -- no debconf information
Processed: tagging 922953
Processing commands for cont...@bugs.debian.org: > tags 922953 + upstream Bug #922953 [src:bind9] bind9: CVE-2018-5744: A specially crafted packet can cause named to leak memory Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 922953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bind9: CVE-2019-6465: Zone transfer controls for writable DLZ zones were not effective
Processing control commands: > found -1 1:9.10.3.dfsg.P4-12.3+deb9u4 Bug #922955 [src:bind9] bind9: CVE-2019-6465: Zone transfer controls for writable DLZ zones were not effective Marked as found in versions bind9/1:9.10.3.dfsg.P4-12.3+deb9u4. > found -1 1:9.10.3.dfsg.P4-12.3 Bug #922955 [src:bind9] bind9: CVE-2019-6465: Zone transfer controls for writable DLZ zones were not effective Marked as found in versions bind9/1:9.10.3.dfsg.P4-12.3. -- 922955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922955: bind9: CVE-2019-6465: Zone transfer controls for writable DLZ zones were not effective
Source: bind9 Version: 1:9.11.5.P1+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1:9.10.3.dfsg.P4-12.3+deb9u4 Control: found -1 1:9.10.3.dfsg.P4-12.3 Hi, The following vulnerability was published for bind9. CVE-2019-6465[0]: Zone transfer controls for writable DLZ zones were not effective If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6465 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6465 [1] https://kb.isc.org/docs/cve-2019-6465 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#922954: bind9: CVE-2018-5745: An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys
Source: bind9 Version: 1:9.11.5.P1+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1:9.10.3.dfsg.P4-12.3+deb9u4 Control: found -1 1:9.10.3.dfsg.P4-12.3 Hi, The following vulnerability was published for bind9. CVE-2018-5745[0]: | An assertion failure can occur if a trust anchor rolls over to an | unsupported key algorithm when using managed-keys 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-5745 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5745 [1] https://kb.isc.org/docs/cve-2018-5745 Regards, Salvatore
Bug#922953: bind9: CVE-2018-5744: A specially crafted packet can cause named to leak memory
Source: bind9 Version: 1:9.11.5.P1+dfsg-2 Severity: grave Tags: security Justification: user security hole Hi, The following vulnerability was published for bind9. CVE-2018-5744[0]: A specially crafted packet can cause named to leak memory 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-5744 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5744 [1] https://kb.isc.org/docs/cve-2018-5744 Please adjust the affected versions in the BTS as needed, if I researched correctly then for the 9.10 branch this was only introduced in 9.10.7b1 and not affecting stretch. Regards, Salvatore
Processed: bind9: CVE-2018-5745: An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys
Processing control commands: > found -1 1:9.10.3.dfsg.P4-12.3+deb9u4 Bug #922954 [src:bind9] bind9: CVE-2018-5745: An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys Marked as found in versions bind9/1:9.10.3.dfsg.P4-12.3+deb9u4. > found -1 1:9.10.3.dfsg.P4-12.3 Bug #922954 [src:bind9] bind9: CVE-2018-5745: An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys Marked as found in versions bind9/1:9.10.3.dfsg.P4-12.3. -- 922954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922936: marked as done (ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update.)
Your message dated Fri, 22 Feb 2019 09:34:25 + with message-id and subject line Bug#922936: fixed in ganeti 2.16.0-5 has caused the Debian Bug report #922936, regarding ganeti: KVM/QEMU Virtual machines won't start after the last qemu-system-x86_64 update. 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.) -- 922936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ganeti Version: 2.16.0-4 Severity: grave Tags: newcomer Justification: renders package unusable Dear Maintainer, After performing the usual apt upgrade on my system, I found Ganeti was unable to start my virtual machines. The error message, from qemu, was that -balloon was an invalid option. Searching the man showed no reference on Buster, but on Stretch it was there. Looking over the change log for qemu 3.1 (https://wiki.qemu.org/ChangeLog/3.1#Incompatible_changes) the 4th entry mentioned `-balloon` had changed to `-device virtio-balloon` Hopefully this can be resolved by a simple search and replace within the Python scripts powering Ganeti. As of yet, I haven't had a look. There will likely be other options that will be affected by the update to qemu. -- Package-specific info: Version symlinks: /etc/ganeti/share -> /usr/share/ganeti/2.16 /etc/ganeti/lib -> /usr/lib/ganeti/2.16 Cluster config version: 2.16.0 Address family: IPv4 Enabled hypervisors: kvm kvm hypervisor parameters: acpi=True boot_order=disk cpu_cores=0 cpu_mask=all cpu_sockets=1 cpu_threads=0 disk_aio=threads disk_cache=default disk_discard=default disk_type=paravirtual kernel_args=ro keymap=en-gb kvm_path=/usr/bin/kvm kvm_pci_reservations=12 migration_bandwidth=32 migration_downtime=30 migration_mode=live migration_port=8102 nic_type=paravirtual reboot_behavior=reboot root_path=/dev/vda1 scsi_controller_type=lsi security_model=none serial_console=True serial_speed=38400 spice_ip_version=0 spice_playback_compression=True spice_tls_ciphers=HIGH:-DES:-3DES:-EXPORT:-DH spice_use_tls=False spice_use_vdagent=True use_chroot=False use_guest_agent=False use_localtime=False user_shutdown=False vhost_net=False virtio_net_queues=1 vnc_bind_address=0.0.0.0 vnc_tls=False vnc_x509_verify=False vnet_hdr=True -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ganeti depends on: ii adduser 3.118 ii ganeti-2.16 2.16.0-4 ii ganeti-haskell-2.16 2.16.0-4 ii ganeti-htools-2.16 2.16.0-4 ii lsb-base 10.2018112800 ii python 2.7.15-4 Versions of packages ganeti recommends: ii drbd-utils 9.5.0-1 ii fdisk2.33.1-0.1 ii ganeti-instance-debootstrap 0.16-6 ii ndisc6 1.0.4-1 ii qemu-kvm 1:3.1+dfsg-4 Versions of packages ganeti suggests: pn blktap-dkms pn ganeti-doc pn molly-guard -- no debconf information --- End Message --- --- Begin Message --- Source: ganeti Source-Version: 2.16.0-5 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 922...@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: Fri, 22 Feb 2019 09:50:10 +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 all amd64 Version: 2.16.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Ganeti Team
Bug#922745: marked as done (gdb needs a backport for PR binutils/23919)
Your message dated Fri, 22 Feb 2019 09:35:35 + with message-id and subject line Bug#922745: fixed in gdb 8.2.1-2 has caused the Debian Bug report #922745, regarding gdb needs a backport for PR binutils/23919 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.) -- 922745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gdb Version: 8.2.1-1 Severity: serious Tags: sid buster gdb needs a backport for PR binutils/23919. The PR fixes an issue with compressed debug sections, and is needed so that gdb can handle the fixed debug sections. elfutils already has the fix. The patch can be taken from the binutils 2.31 branch. --- End Message --- --- Begin Message --- Source: gdb Source-Version: 8.2.1-2 We believe that the bug you reported is fixed in the latest version of gdb, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated gdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Feb 2019 09:46:36 +0100 Source: gdb Architecture: source Version: 8.2.1-2 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Closes: 917806 922030 922745 922796 Changes: gdb (8.2.1-2) unstable; urgency=medium . * debian/patches: binutils PR/23919 (Closes: #922745) * debian/patches: fix gdb PR/23712 (Closes: #922030) * debian/rules: include riscv* in multiarch targets (Closes: #922796) * Bump standards version * fix kfreebsd-any build (Closes: #917806) Checksums-Sha1: 852d777c88a106a531dd477b0e72d48f43bae2d4 2979 gdb_8.2.1-2.dsc 86eb031c69a80dda1eb470bd4ce6c4d568f70ee0 64628 gdb_8.2.1-2.debian.tar.xz 7d018c59e18a76f5595227eb16f2215ac5bad0ce 10243 gdb_8.2.1-2_source.buildinfo Checksums-Sha256: 88d60500af8b9defac1546be722d765c5341eac80847eb4e56e8e28561827676 2979 gdb_8.2.1-2.dsc 09344fa4280ad2f6f4c6608e09f1099a6db8a4f4eafcf7ec39e41354c6c9f148 64628 gdb_8.2.1-2.debian.tar.xz c69d477412bbc68080e51083dbfcae94866426ac1f3e3d982767946b3443de81 10243 gdb_8.2.1-2_source.buildinfo Files: b08900db3a882e3ffc3817d86ecac98d 2979 devel optional gdb_8.2.1-2.dsc da5bcef928a36b7f5dd620496a157912 64628 devel optional gdb_8.2.1-2.debian.tar.xz 94920c09d4b75c69a2e61efb2006ac3f 10243 devel optional gdb_8.2.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAlxvvq4ACgkQryKDqnbi rHuR8BAAq1G6+GkUXU8KpCulEeJmaJCNOt9USwxEEte73oXkv+9gwMdXC0vu53bm GtU8Lb579M9oivnndlgQRmen+BSqJc/wUKNbKVCELh/HbdAJG0mRUjioCFBdgSBv gJlBjlET9GQEPbRQFJsl0ii5QTbigOTOyXJuniw2sp1zq1JQLHN/ZGo+QYTsT/8U kZvhaP8Kg4F4VF0aoLeJ5EuB6TdpyQnB5VGGX36MIdsUOg02GjkfzKO3fojuwKjQ eTEYuepV3Vpow8It/qUz8Z0iWS/x0DTAFwa5iBmwAJqoSkupCWyNkguhL5Nwf/YK +qrDtXdcOZX9oeTeDLtrqOd7sp9LcSVdFN+aB4xtasewJ8LlrBevEQFg5IbziwSS o3NlZFjwvv9miciXDQI+5ptVoZeWdVoHiitYzU3TjOvBsRvg3T+IeP7jb4a1KFuw clc0l1DzST8Wlnsptt8nj8Q2jQPEUVLzXdu2TX43p6Rb3rcZXwc/oXe9lYkqC0Re 6VTWLV2vE3ui8s5UCdZBteL6blNQuEaHgmsOSQTf40dLtDxtXV7K3mUKEghYfLUB Al6uN1HhxKACh04SExFQNU8shjcig6M0vEDDwn+3VMArXhUo1c9XARfgd6AsCnGO ujNm/JlhYsXwQ9X5yATUwg1PHt07HUOtR5EkbRlb02Et1sOZ4wg= =zU24 -END PGP SIGNATURE End Message ---
Bug#921131: taking over yum-utils
hi Markus, please adopt yum-utils and get the changes from experiemental into sid/buster before the freeze is fully in effect. You still have almost a week to do that! ;) Also if you do that, please dont forget to include the changes from my NMU. If you need any help or advice, please shout! -- tschau, 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
Bug#920547: Crashes every few hours
Hi Ben, On Mon, Jan 28, 2019 at 12:42:37AM +, Ben Hutchings wrote: > When you say "data loss", are you talking about data in memory or > corruption of files that were saved and sync'd to disk? do you need further information, and when you suggested that I file the bug upstream, what classification should I use? Cheers, Toni
Bug#921296: ccfits: FTBFS with upcoming doxygen 1.8.15
Hi, I'm forwarding some remark to bug #916715 which might shade some light on this issue. Since I was bored watching toulbar2 and reseting removal from testing time over and over I deactivated PDF generation for the time beeing. Not nice, but users can read HTML and PDF can be activated later. Kind regards Andreas. - Forwarded message from Thomas Schiex - Date: Tue, 19 Feb 2019 12:29:46 +0100 From: Thomas Schiex To: Andreas Tille , Debian Developers , Thomas Schiex , debian-rele...@lists.debian.org CC: 920...@bugs.debian.org, 916...@bugs.debian.org, Adrian Bunk Subject: Re: toulbar2: What will happen if testing migration takes longer than removal from testing > Hi Thomas, >> Dear Andreas, >> >> Thanks for taking care of toulbar2. I did spend some time to try to go >> around this #920459 bug but even a postprocessing of the LaTeX output of >> doxygen (removing inclusion of the xcolor package that generates the >> LaTeX compilation issue) did not work (another bug popped up, that was >> apparently already met by other people using doxygen using the same >> TexLive update but I found no workaround). > I think doxygen is severly broken and just skipping refman.pdf (finally > users can read other format) the only safe solution to keep the package > in. I added several FIXMEs to get it back for Buster+1. My current (partial) understanding is that TexLive/LaTeX is broken (not doxygen): TeXlive provides the tabu LaTeX package (https://ctan.org/pkg/tabu) that doxygen uses but this tabu package does not work anymore in TeXlive (not only for doxygen, but for all tabu users). See #920621/#921272 saying that "upstream is working on it". Probably this will not be fast as the README.md of tabu on CTAN says: The original author of tabu appears out of contact, and tabu had not been updated for several years, finally becoming unusable in 2019 as updates to other packages mean some of its patched code did not work as intended. The package is not being actively maintained however any major required fixes may be reported to the https://github.com/tabu-fixed/tabu repository and volunteers there (currently members of the LATEX3 Team) will attempt to update the package with any fixes required. Getting rid of the PDF output as you suggest for eg. HTML is probably best. Thomas - End forwarded message - -- http://fam-tille.de
Bug#874109: marked as done (pngcrush: CVE-2015-7700)
Your message dated Fri, 22 Feb 2019 08:35:20 + with message-id and subject line Bug#874109: fixed in pngcrush 1.8.13-0.1 has caused the Debian Bug report #874109, regarding pngcrush: CVE-2015-7700 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.) -- 874109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pngcrush Version: 1.7.65-0.1 Severity: important Tags: security upstream patch Hi, the following vulnerability was published for pngcrush. CVE-2015-7700[0]: | Double-free vulnerability in the sPLT chunk structure and png.c in | pngcrush before 1.7.87 allows attackers to have unspecified impact via | unknown vectors. 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-2015-7700 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7700 [1] http://sourceforge.net/p/pmt/code/ci/e8ae5a842e86324f0bee91f4d98245fddb8ea5dd Regards, Salvatore --- End Message --- --- Begin Message --- Source: pngcrush Source-Version: 1.8.13-0.1 We believe that the bug you reported is fixed in the latest version of pngcrush, 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 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pngcrush 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, 22 Feb 2019 09:07:23 +0100 Source: pngcrush Binary: pngcrush Architecture: source Version: 1.8.13-0.1 Distribution: unstable Urgency: medium Maintainer: Margarita Manterola Changed-By: Andreas Tille Description: pngcrush - optimizes PNG (Portable Network Graphics) files Closes: 874109 Changes: pngcrush (1.8.13-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream version * Decide for latest upstream but found in upstream changelog: Version 1.7.87 (built with libpng-1.6.18 and zlib-1.2.8) Fixed a double-free bug (CVE-2015-7700). There was a "free" of the sPLT chunk structure in pngcrush and then again in png.c (Bug report by Brian Carpenter). Closes: #874109 * Standards-Version: 4.3.0 * Remove custom compression settings in debian/source/options * hardening=+all Checksums-Sha1: 36c3c08299bd7206a47e3944c5c6df4b030f9a1f 1991 pngcrush_1.8.13-0.1.dsc 20654cd63a90afa9fec947cd7547edd3cf9ea975 66104 pngcrush_1.8.13.orig.tar.xz 1e4fb2720e66910d847bd5714a2e6a40e12a9214 14300 pngcrush_1.8.13-0.1.debian.tar.xz Checksums-Sha256: 4fa7134d80352bd445b5075853a608197f0a9046962ffca2939cb7103d8e5b6a 1991 pngcrush_1.8.13-0.1.dsc 3b4eac8c5c69fe0894ad63534acedf6375b420f7038f7fc003346dd352618350 66104 pngcrush_1.8.13.orig.tar.xz 211b1b20798bdb38d2c407200e6008753f3a4cb5145138bab29b607bafdbdc42 14300 pngcrush_1.8.13-0.1.debian.tar.xz Files: 0ef800f538212411bee5c9334dbd50cf 1991 graphics optional pngcrush_1.8.13-0.1.dsc 3ef6abefa978dc021bd3dd41c602e822 66104 graphics optional pngcrush_1.8.13.orig.tar.xz e4c18146fe56f16e48b22d01329a114c 14300 graphics optional pngcrush_1.8.13-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxvrlkRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHWMQ//cLssmUJE/ocKJSmqbvAd6/ahHp2E6rSq 5ELSrgLCcDnbm5htJJxNjGRh8girECmJyeXYumcprI5lzdjYvslv6QQgUbNw6Xao gs+SdddKSK8DeZAgTdSGUb+VrvKzhxE+cflD5ZdEBvuIbq04yUuYbubz+Qu+aABF 5Nq0UUDYjxo35+if5I6ozxRpxY+MQb2NaC964aZ2+kRBXQIurNnRdr/4jxojB82s Ue7fN5L0WaUg7uSar0QBmte6d4pfd+UxRvmGt4fidts+pvsos0277UGovMXr9y1K TgYGwZ3xTpASLOZWZrUCwWTTZPuRsYEDtTB4hWaVubr/h3rwDijQduOTSvJdkHF8 S+HaDcl8W28lMNqAQv7BRld1JwT3CCRMR3HNjVcCJA5KKhIIntMeLrVdS5b3iPDc XeHvPJ7ZhL4K9tYI5ga1R47rdok3NwlFiWYHiLyDqI99UJdZICgZMEnIFuCfjeJq MZtU/urc+Vwohi7JdyMpX3GYFbv4POesNP7kwcXmGLBkKOkUkQWPTyqe3+N4zw7w fvzxTuKaa74lgdC+82fEG7VroF+XrWx/PQHcyL2CHkQ1upPyqC6qRs0Mrd9x3qJf Q5iAnQaGwb96rb1jqYWeoSGXjCO/6EjKNLdOTLeY+z3902bzWT06WLnGVmClRIXc kBzDnSjanp4= =tme3 -END PGP SIGNATURE End Message ---
