Bug#869856: [Pkg-openssl-devel] Bug#869856: openssl: FTBFS: Testsuite failures
On Wed, Jul 26, 2017 at 11:18:32PM -0700, Daniel Schepler wrote: > Source: openssl > Version: 1.1.0f-3 > Severity: serious > > From my pbuilder build log (on amd64): > > ... > Test Summary Report > --- > ../../test/recipes/70-test_sslrecords.t (Wstat: 0 Tests: 10 Failed: 0) > Parse errors: Tests out of sequence. Found (5) but expected (4) >Tests out of sequence. Found (6) but expected (5) >Tests out of sequence. Found (7) but expected (6) >Tests out of sequence. Found (8) but expected (7) >Tests out of sequence. Found (9) but expected (8) > Displayed the first 5 of 8 TAP syntax errors. Is that reproducible? This was most likely fixed upstream the day after the release. Kurt
Bug#869783: Security - upgrade NVidia driver to 375.82 in stable.
I keep on getting emails for Nvidia stuff, how can I stop this? On 26 Jul 2017 23:21, "Luca Boccassi" wrote: Control: tags -1 pending On Wed, 2017-07-26 at 13:48 +0200, Julien Aubin wrote: > Package: nvidia-driver > Version: 375.66-2 > Severity: critical > > Hi, > > NVidia driver is currently targetted by several critical > vulnerabilities as > disclosed by NVidia. Full description there : > https://nvidia.custhelp.com/app/answers/detail/a_id/4525 > > Some of the vulnerabilities affect Linux users with issues including > privilege escalation and denial of service. > > Updated package is 375.82. > > Could you please release quickly the updated packages ? > > Thanks Uploaded to unstable. Dear Security Team, CVE-2017-6257 and CVE-2017-6259 affect Stretch - how would you like to see this handled? - upload through security - upload through p/u - ignore I have tested this new version on a Stretch amd64 desktop and didn't encounter any issue. The debdiff from 375.66-2~deb9u1 to 375.82-1 is attached. Apart from the new upstream version, the other bug fixes are: - update binary library blobs symbols files reflecting upstream changes - allow parallel dkms builds if requested (#864639) - re-allow dkms ccache usage if enabled - switch watch files protocol to https, upstream deprecated ftp (#868815) - mark the dkms modules as build-tested on kernel 4.11 - add support for buster in the nvidia-detect script (#866126) Kind regards, Luca Boccassi
Bug#868919: marked as done (physamp: FTBFS: AlignmentOptimizer.cpp:39:32: fatal error: Bpp/Seq/Alphabet.all: No such file or directory)
Your message dated Thu, 27 Jul 2017 07:49:09 + with message-id and subject line Bug#868919: fixed in physamp 1.0.2-1 has caused the Debian Bug report #868919, regarding physamp: FTBFS: AlignmentOptimizer.cpp:39:32: fatal error: Bpp/Seq/Alphabet.all: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: physamp Version: 0.2.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170719 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): > cd /<>/obj-x86_64-linux-gnu/physamp && /usr/bin/c++ -Wall > -Weffc++ -Wshadow -Wconversion -o > CMakeFiles/bppalnoptim.dir/AlignmentOptimizer.cpp.o -c > /<>/physamp/AlignmentOptimizer.cpp > /<>/physamp/AlignmentOptimizer.cpp:39:32: fatal error: > Bpp/Seq/Alphabet.all: No such file or directory > #include > ^ > compilation terminated. > physamp/CMakeFiles/bppalnoptim.dir/build.make:65: recipe for target > 'physamp/CMakeFiles/bppalnoptim.dir/AlignmentOptimizer.cpp.o' failed > make[3]: *** [physamp/CMakeFiles/bppalnoptim.dir/AlignmentOptimizer.cpp.o] > Error 1 The full build log is available from: http://aws-logs.debian.net/2017/07/19/physamp_0.2.0-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: physamp Source-Version: 1.0.2-1 We believe that the bug you reported is fixed in the latest version of physamp, 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 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Dutheil (supplier of updated physamp 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: Thu, 20 Jul 2017 10:42:52 +0200 Source: physamp Binary: physamp Architecture: source amd64 Version: 1.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Julien Dutheil Description: physamp- sample sequence alignment according to its corresponding phylogen Closes: 868919 Changes: physamp (1.0.2-1) unstable; urgency=medium . [ Andreas Tille ] * New upstream version Closes: #868919 * d/watch pointing to Github * Fix homepage * debhelper 10 * Adjust versioned Build-Depends * Standards-Version: 4.0.0 (no changes needed) . [ Julien Y. Dutheil ] * Updated from upstream. Checksums-Sha1: 326b3aac1a8fa4aa6d6d2e5f88e1ea3db6abe76b 2013 physamp_1.0.2-1.dsc 5ef180fb1df7048ba5c2587ce81fbb151a10dae1 241626 physamp_1.0.2.orig.tar.gz 32d1e0e7d0a4c5f6e420e36b25e66c70929f8c8c 2440 physamp_1.0.2-1.debian.tar.xz 9e90ebb8d9d2905e0768664da179e87bceb273c1 34056 physamp-dbgsym_1.0.2-1_amd64.deb 51d1f17028510d2d8c4f0ab3fdb0a7738214c4bf 6774 physamp_1.0.2-1_amd64.buildinfo 2b58070d81eedcb3a04524dc7d0b6e69d6a56535 309688 physamp_1.0.2-1_amd64.deb Checksums-Sha256: a22fd9bace4342a54894c996aa76c15b3e5b48802429200440e4eb3d01a2bc40 2013 physamp_1.0.2-1.dsc 1f27ed7547a4dc51fa7eac4bdbb72c14c8ca87cd9a618f3c8a589a165baf46d5 241626 physamp_1.0.2.orig.tar.gz 3da461e74e5fbf9b3e37d54394b2c9198ef2d90043171fba214ba9a1503c90cb 2440 physamp_1.0.2-1.debian.tar.xz d21f6e537abc31414eec3e65e715eab6c0d7199c1625ecbe0fa5975b2c089a82 34056 physamp-dbgsym_1.0.2-1_amd64.deb 2c10464f2ceba54a9e1c3a6beba692e44ecd9391e6df3e18f876d13d2f9b39a1 6774 physamp_1.0.2-1_amd64.buildinfo a8c0a305cf24737dbe5c1a723f98075a1840ebc9a4dc1937c66bf539f8579ec2 309688 physamp_1.0.2-1_amd64.deb Files: 182d22bfcfff9ab34d525ee7102fe013 2013 science optional physamp_1.0.2-1.dsc f2ab7ec2a621e8a4f106632301fdfe6e 241626 science optional physamp_1.0.2.
Bug#869837: kdenlive: busy loop
Am 27.07.2017 um 00:32 schrieb Salvo Tomaselli:
> Package: kdenlive
> Version: 17.04.3-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> kdenlive does a busy loop, and is basically keeping the CPU too busy doing
> that, to actually do anything productive.
>
> When I start it, CPU jumps at 100%.
Could you reproduce this issue with kdenlive < 17.04.3? What happens if
you try it out with a fresh profile.
>
> with strace I get this:
>
> futex(0x4aafe807c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x4aafe807c0,
> FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
> writev(3,
> [{iov_base="\n\0\2\0\25\0\340\3\31\0\v\0\347\0\0\0\0\0\30\0\22\\tZ\347\0\0\0\25\0\340\3"...,
> iov_len=52}], 1) = 52
> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
> writev(3, [{iov_base="\2\0\4\0\33\0\340\3\0@\0\0\230\1\340\3", iov_len=16}],
> 1) = 16
> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
> writev(3, [{iov_base="\22\0\7\0\33\0\340\3y\1\0\0\6\0\0\0
> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
> futex(0x7ffd5a745bd0, FUTEX_WAKE_PRIVATE, 1) = 1
> futex(0x7ffd5a745bd4, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
> temporarily unavailable)
> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
> writev(3, [{iov_base="\22\0\7\0\25\0\340\3y\1\0\0\6\0\0\0
> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
> futex(0x7ffd5a745f40, FUTEX_WAKE_PRIVATE, 1) = 1
> futex(0x7ffd5a745f44, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
> temporarily unavailable)
> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>
> Over and over.
>
> Best.
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages kdenlive depends on:
> ii ffmpeg 7:3.2.6-1+b3
> ii kded55.28.0-1
> ii kdenlive-data17.04.3-1
> ii kinit5.28.0-1
> ii kio 5.28.0-2
> ii libc62.24-12
> ii libgcc1 1:7.1.0-10
> ii libgl1-mesa-glx [libgl1] 17.1.4-1
> ii libglu1-mesa [libglu1] 9.0.0-2.1
> ii libkf5archive5 5.28.0-2
> ii libkf5attica55.28.0-1
> ii libkf5auth5 5.28.0-2
> ii libkf5bookmarks5 5.28.0-1
> ii libkf5codecs55.28.0-1+b2
> ii libkf5completion55.28.0-1
> ii libkf5configcore55.28.0-2
> ii libkf5configgui5 5.28.0-2
> ii libkf5configwidgets5 5.28.0-2
> ii libkf5coreaddons55.28.0-2
> ii libkf5crash5 5.28.0-1
> ii libkf5dbusaddons55.28.0-1
> ii libkf5filemetadata3 5.28.0-1+b2
> ii libkf5guiaddons5 5.28.0-1
> ii libkf5i18n5 5.28.0-2
> ii libkf5iconthemes55.28.0-2
> ii libkf5itemviews5 5.28.0-1
> ii libkf5jobwidgets55.28.0-2
> ii libkf5kiocore5
Bug#865866: libreoffice-writer crash on startup Debian 9 i386 arch
Hi Rene, dated libreoffice up this morning, but no success. I deletd ~/.config/libreoffice and got this error message: *user@protheus7*:*~*$ libreoffice *user@protheus7*:*~*$ Hope, this helps. Best Hans
Bug#869864: dojo: New version available, watch file fails
Package: dojo Version: 1.11.0 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, the dojo package fails to build, which blocks the package tt-rss from entering testing. There is a new version available (1.12.2), which has not been recognized, sine the watch task fails with: uscan had problems while searching for a new upstream version: In watchfile debian/watch, reading webpage http://download.dojotoolkit.org/dojo-release-1.12.2-shrinksafe.tar.gz/ failed: 404 Not Found Maybe try github instead? https://github.com/dojo/dojo/releases Maybe a package upgrade and a small cleanup will make it build again. Stefan -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#869837: kdenlive: busy loop
I deleted all my .kdenlive data and downgraded to .2 and it doesn't
seem to have the issue.
But now it might be difficult to reproduce, because I didn't think of
keeping it or the cache.
2017-07-27 9:56 GMT+02:00 Patrick Matthäi :
> Am 27.07.2017 um 00:32 schrieb Salvo Tomaselli:
>> Package: kdenlive
>> Version: 17.04.3-1
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>> kdenlive does a busy loop, and is basically keeping the CPU too busy doing
>> that, to actually do anything productive.
>>
>> When I start it, CPU jumps at 100%.
>
> Could you reproduce this issue with kdenlive < 17.04.3? What happens if
> you try it out with a fresh profile.
>
>>
>> with strace I get this:
>>
>> futex(0x4aafe807c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x4aafe807c0,
>> FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
>> writev(3,
>> [{iov_base="\n\0\2\0\25\0\340\3\31\0\v\0\347\0\0\0\0\0\30\0\22\\tZ\347\0\0\0\25\0\340\3"...,
>> iov_len=52}], 1) = 52
>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>> writev(3, [{iov_base="\2\0\4\0\33\0\340\3\0@\0\0\230\1\340\3", iov_len=16}],
>> 1) = 16
>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>> writev(3, [{iov_base="\22\0\7\0\33\0\340\3y\1\0\0\6\0\0\0
>> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>> futex(0x7ffd5a745bd0, FUTEX_WAKE_PRIVATE, 1) = 1
>> futex(0x7ffd5a745bd4, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
>> temporarily unavailable)
>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>> writev(3, [{iov_base="\22\0\7\0\25\0\340\3y\1\0\0\6\0\0\0
>> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>> futex(0x7ffd5a745f40, FUTEX_WAKE_PRIVATE, 1) = 1
>> futex(0x7ffd5a745f44, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
>> temporarily unavailable)
>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>>
>> Over and over.
>>
>> Best.
>>
>>
>> -- System Information:
>> Debian Release: buster/sid
>> APT prefers unstable
>> APT policy: (500, 'unstable'), (500, 'testing')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
>> (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages kdenlive depends on:
>> ii ffmpeg 7:3.2.6-1+b3
>> ii kded55.28.0-1
>> ii kdenlive-data17.04.3-1
>> ii kinit5.28.0-1
>> ii kio 5.28.0-2
>> ii libc62.24-12
>> ii libgcc1 1:7.1.0-10
>> ii libgl1-mesa-glx [libgl1] 17.1.4-1
>> ii libglu1-mesa [libglu1] 9.0.0-2.1
>> ii libkf5archive5 5.28.0-2
>> ii libkf5attica55.28.0-1
>> ii libkf5auth5 5.28.0-2
>> ii libkf5bookmarks5 5.28.0-1
>> ii libkf5codecs55.28.0-1+b2
>> ii libkf5completion55.28.0-1
>> ii libkf5configcore55.28.0-2
>> ii libkf5configgui5 5.28.0-2
>> ii libkf5configwidgets5 5.28.0-2
>> ii libkf5coreaddons55.28.0-2
>> ii libkf5crash5
Bug#869837: kdenlive: busy loop
If I understood you correct you have started with .3, so if you upgrade,
delete again the config directories and try to use it again, still there
the issue?
Am 27.07.2017 um 10:23 schrieb Salvo Tomaselli:
> I deleted all my .kdenlive data and downgraded to .2 and it doesn't
> seem to have the issue.
>
> But now it might be difficult to reproduce, because I didn't think of
> keeping it or the cache.
>
> 2017-07-27 9:56 GMT+02:00 Patrick Matthäi :
>> Am 27.07.2017 um 00:32 schrieb Salvo Tomaselli:
>>> Package: kdenlive
>>> Version: 17.04.3-1
>>> Severity: grave
>>> Justification: renders package unusable
>>>
>>> Dear Maintainer,
>>> kdenlive does a busy loop, and is basically keeping the CPU too busy doing
>>> that, to actually do anything productive.
>>>
>>> When I start it, CPU jumps at 100%.
>> Could you reproduce this issue with kdenlive < 17.04.3? What happens if
>> you try it out with a fresh profile.
>>
>>> with strace I get this:
>>>
>>> futex(0x4aafe807c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x4aafe807c0,
>>> FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
>>> writev(3,
>>> [{iov_base="\n\0\2\0\25\0\340\3\31\0\v\0\347\0\0\0\0\0\30\0\22\\tZ\347\0\0\0\25\0\340\3"...,
>>> iov_len=52}], 1) = 52
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>>> writev(3, [{iov_base="\2\0\4\0\33\0\340\3\0@\0\0\230\1\340\3",
>>> iov_len=16}], 1) = 16
>>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>>> writev(3, [{iov_base="\22\0\7\0\33\0\340\3y\1\0\0\6\0\0\0
>>> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745bd0, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745bd4, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
>>> temporarily unavailable)
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> write(5, "\1\0\0\0\0\0\0\0", 8) = 8
>>> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
>>> writev(3, [{iov_base="\22\0\7\0\25\0\340\3y\1\0\0\6\0\0\0
>>> \0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745f40, FUTEX_WAKE_PRIVATE, 1) = 1
>>> futex(0x7ffd5a745f44, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
>>> temporarily unavailable)
>>> futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
>>>
>>> Over and over.
>>>
>>> Best.
>>>
>>>
>>> -- System Information:
>>> Debian Release: buster/sid
>>> APT prefers unstable
>>> APT policy: (500, 'unstable'), (500, 'testing')
>>> Architecture: amd64 (x86_64)
>>> Foreign Architectures: i386
>>>
>>> Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
>>> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
>>> (charmap=UTF-8)
>>> Shell: /bin/sh linked to /bin/dash
>>> Init: systemd (via /run/systemd/system)
>>>
>>> Versions of packages kdenlive depends on:
>>> ii ffmpeg 7:3.2.6-1+b3
>>> ii kded55.28.0-1
>>> ii kdenlive-data17.04.3-1
>>> ii kinit5.28.0-1
>>> ii kio 5.28.0-2
>>> ii libc62.24-12
>>> ii libgcc1 1:7.1.0-10
>>> ii libgl1-mesa-glx [libgl1] 17.1.4-1
>>> ii libglu1-mesa [libglu1] 9.0.0-2.1
>>> ii libkf5archive5 5.28.0-2
>>> ii libkf5attica55.28.0-1
>>> ii libkf5auth5 5.28.0-2
>>> ii libkf5bookmarks5
Bug#869837: kdenlive: busy loop
It no longer occurs now.
I think it was caused by old configuration/cache, from pre-17 version
that I had used years before, and remained around in my home.
However I now have deleted those files, so I don't know how to reproduce.
2017-07-27 10:42 GMT+02:00 Patrick Matthäi :
> If I understood you correct you have started with .3, so if you upgrade,
> delete again the config directories and try to use it again, still there
> the issue?
>
>
> Am 27.07.2017 um 10:23 schrieb Salvo Tomaselli:
>> I deleted all my .kdenlive data and downgraded to .2 and it doesn't
>> seem to have the issue.
>>
>> But now it might be difficult to reproduce, because I didn't think of
>> keeping it or the cache.
>>
>> 2017-07-27 9:56 GMT+02:00 Patrick Matthäi :
>>> Am 27.07.2017 um 00:32 schrieb Salvo Tomaselli:
Package: kdenlive
Version: 17.04.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
kdenlive does a busy loop, and is basically keeping the CPU too busy doing
that, to actually do anything productive.
When I start it, CPU jumps at 100%.
>>> Could you reproduce this issue with kdenlive < 17.04.3? What happens if
>>> you try it out with a fresh profile.
>>>
with strace I get this:
futex(0x4aafe807c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x4aafe807c0,
FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
writev(3,
[{iov_base="\n\0\2\0\25\0\340\3\31\0\v\0\347\0\0\0\0\0\30\0\22\\tZ\347\0\0\0\25\0\340\3"...,
iov_len=52}], 1) = 52
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{iov_base="\2\0\4\0\33\0\340\3\0@\0\0\230\1\340\3",
iov_len=16}], 1) = 16
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{iov_base="\22\0\7\0\33\0\340\3y\1\0\0\6\0\0\0
\0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745bd0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745bd4, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{iov_base="\22\0\7\0\25\0\340\3y\1\0\0\6\0\0\0
\0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745f40, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745f44, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
Over and over.
Best.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages kdenlive depends on:
ii ffmpeg 7:3.2.6-1+b3
ii kded55.28.0-1
ii kdenlive-data17.04.3-1
ii kinit
Bug#869572: marked as done (casacore-data-igrf FTBFS with casacore-tools 2.3.0-3)
Your message dated Thu, 27 Jul 2017 08:49:00 + with message-id and subject line Bug#869572: fixed in casacore-data-igrf 12-1 has caused the Debian Bug report #869572, regarding casacore-data-igrf FTBFS with casacore-tools 2.3.0-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 869572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: casacore-data-igrf Version: 10-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/casacore-data-igrf.html ... make[1]: Entering directory '/build/1st/casacore-data-igrf-10' ./debian/md.sh IGRF Create data tables for Measures --- measuresdata: Version 20110502wnb The requested type is: IGRF The processed type[s]: IGRF The data table directory: /build/1st/casacore-data-igrf-10/build Check and request mode only No forced refresh asked No explicit renew asked Testing IGRF measuresdata ended normally Create data tables for Measures --- measuresdata: Version 20110502wnb The requested type is: IGRF The processed type[s]: IGRF The data table directory: /build/1st/casacore-data-igrf-10/build The input data file: /build/1st/casacore-data-igrf-10/build/igrf12coeffs.txt The input data file is not readable debian/rules:7: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 1 --- End Message --- --- Begin Message --- Source: casacore-data-igrf Source-Version: 12-1 We believe that the bug you reported is fixed in the latest version of casacore-data-igrf, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated casacore-data-igrf 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: Thu, 27 Jul 2017 09:49:14 +0200 Source: casacore-data-igrf Binary: casacore-data-igrf Architecture: source Version: 12-1 Distribution: unstable Urgency: low Maintainer: Debian Astro Team Changed-By: Ole Streicher Description: casacore-data-igrf - International Geomagnetic Reference Field data for casacore Closes: 869572 Changes: casacore-data-igrf (12-1) unstable; urgency=low . * Fix Vcs-Git * New upstream version 12. Closes: #869572 * Push Standards-Version to 4.0.0. No changes required. Checksums-Sha1: b9e6ae86635320d898107e83c058157156db0fd0 2097 casacore-data-igrf_12-1.dsc 4609381b4b8683d79a412aa225eb068511c22b9c 5336 casacore-data-igrf_12.orig.tar.xz 8ea8725f2e2aeccffda73e4336f92a4bd4d8f72f 2768 casacore-data-igrf_12-1.debian.tar.xz Checksums-Sha256: b6f7a547ee074a3a6a38f0807e397e7313a3b6248a53e4f2e29615f882885dad 2097 casacore-data-igrf_12-1.dsc 677ec297e693129387f92ca389b325e388bd234fe93b65557d14e980cd4020d5 5336 casacore-data-igrf_12.orig.tar.xz ba392f62ff9d5b0b9da89512490fe18a3210b481cc3f5e4e12f8cb2536c768ed 2768 casacore-data-igrf_12-1.debian.tar.xz Files: e51d41cc8027060fe49c81dc1421f775 2097 science optional casacore-data-igrf_12-1.dsc 6150fc721fdd77f18f82842f8a8b325c 5336 science optional casacore-data-igrf_12.orig.tar.xz 6900d558cfa308af2bdfc168060f4a63 2768 science optional casacore-data-igrf_12-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAll5n4QACgkQcRWv0HcQ 3PfAPw//XrBG2/C+I5CCAbibwDEzq38prOW6+fnqo8wJqk5NihUayaWrJEI4FTKh qBg0CE13h9b7ztcv5gENCuBIKair2x/O3zadKAIdq3faubN2udcbGTk658Iiy3hC YAWwkiSb23DihVQ5OqfS40cJ9u6efmbMIH4n756yDR7W7AtB172iXbg/1iuQXuEc IYggKzUu52ns6b9//1Qy7k8BPjGC3ofnlHy+ZHjWTldhGtUpjM1rCxGiIrEzkd6g /ZdNQr6CjQknKIlrBTwHt+jTcAMsSgsU7SdqHXayFTEKRzgsAlCvcVqDuAMj1lwk 6WshD7hRZXlIEprpmPVLJxbBblnsOJ/FlgQ+v6MY3alKC9v5pbNVUKwqPYW3YX1l zhyWnhJFNbyIJJsWvNbf21NpPXTPLqMWH4rY5Mfyue5LnPW8P5nDdZjlScnpSGfK /HDFslHRTXBEfMR/jTBnjgdMlcw9mHNPxUiBsgcAiDGhuTJFRtOTGfJBsa+Hje0X 1peeVSqLDomuSIhjN4u9mGcsity058lDnGEMHlTtcTVFrnzACN7Ie8cQl6ykvgFP HKM9e/9QMfZmhv/naPE38CWqvC4XnwLAKXllSDfY0P8jPGCZ3SdaQZiRkeiI9H5W NP0a4rOr0XZ8V+ldMgxnL6WFtmovWTjT56m0o+CkiRUcHvP7pyY= =AoND -END PGP SIGNATURE---
Bug#863969: marked as pending
On Sat, Jun 03, 2017 at 08:31:28AM +, Sven Joachim wrote: > tag 863969 pending > thanks > > Hello, > > Bug #863969 reported by you has been fixed in the Git repository. You can > see the changelog below, and you can check the diff of the fix at: > > > https://anonscm.debian.org/cgit/collab-maint/ncurses.git/commit/?id=d5bc8bb > > --- > commit d5bc8bb04b3d0092f898263c8dc58f746dde9bae > Author: Sven Joachim > Date: Sat Jun 3 10:24:25 2017 +0200 > > Blacklist dvtm and dvtm-256color terminfo entries Actually the upstream dvtm description has more than one error, which I noticed (and fixed). > They are already shipped in the dvtm package. While it would be > desirable to take the files over in ncurses-term, this requires > consent from the dvtm maintainer who is currently unavailable as per > https://www.debian.org/News/2017/20170417. :-) > diff --git a/debian/changelog b/debian/changelog > index f3eacb8..58001ba 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -1,3 +1,10 @@ > +ncurses (6.0+20170408-2) UNRELEASED; urgency=low > + > + * Blacklist dvtm and dvtm-256color terminfo entries which are shipped > +in the dvtm package (Closes: #863969). > + > + -- Sven Joachim Sat, 03 Jun 2017 09:50:35 +0200 > + > ncurses (6.0+20170408-1) experimental; urgency=low > >* New upstream patchlevel. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Bug#862472: tack: FTBFS: ./tack.h:78:32: error: dereferencing pointer to incomplete type 'TERMINAL {aka struct term}'
On Sat, May 13, 2017 at 11:33:13AM +0200, Sven Joachim wrote:
> Source: tack
> Version: 1.07-1
> Tags: buster sid fixed-upstream
>
> With libncurses5-dev from experimental, tack FTBFS. From the build log:
>
> ,
> | gcc -c -DHAVE_CONFIG_H -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -DXTSTRINGDEFINES -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/tmp/tack-1.07=.
> -fstack-protector-strong -Wformat -Werror=format-security control.c
> | In file included from ./tack.h:51:0,
> | from control.c:22:
> | control.c: In function 'alloc_arrays':
> | ./tack.h:78:32: error: dereferencing pointer to incomplete type 'TERMINAL
> {aka struct term}'
> | #define CUR_TP (&(cur_term->type))
> | ^
> | ./tack.h:79:33: note: in expansion of macro 'CUR_TP'
> | #define MAX_STRINGS NUM_STRINGS(CUR_TP)
> | ^~
> | control.c:81:45: note: in expansion of macro 'MAX_STRINGS'
> |pads = (struct test_results **)calloc(MAX_STRINGS, sizeof(struct
> test_results *));
> | ^~~
> | Makefile:242: recipe for target '../tack-1.07/control.o' failed
> `
>
> The reason is the following change in ncurses:
>
> ,
> | 20170318
> | + change TERMINAL structure in term.h to make it opaque. Some
> | applications misuse its members, e.g., directly modifying it
> | rather than using def_prog_mode().
> `
>
> The latest upstream snapshot at
> ftp://ftp.invisible-island.net/ncurses/current/tack-1.07-20170318.tgz
> fixes the problem, it might be good to package it after the stretch
> release. Or persuade upstream to release tack 1.08, since 1.07 is
> already over seven years old.
Debian's package hasn't kept up with any of the other changes in tack.
Let's see how long it takes for it to be updated to 1.08:
http://invisible-island.net/ncurses/tack/CHANGES.html
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
Bug#869837: marked as done (kdenlive: busy loop)
Your message dated Thu, 27 Jul 2017 11:32:00 +0200
with message-id <879dc158-57ef-5f15-d340-82552632f...@debian.org>
and subject line Re: Bug#869837: kdenlive: busy loop
has caused the Debian Bug report #869837,
regarding kdenlive: busy loop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
869837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdenlive
Version: 17.04.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
kdenlive does a busy loop, and is basically keeping the CPU too busy doing
that, to actually do anything productive.
When I start it, CPU jumps at 100%.
with strace I get this:
futex(0x4aafe807c4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x4aafe807c0,
FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
writev(3,
[{iov_base="\n\0\2\0\25\0\340\3\31\0\v\0\347\0\0\0\0\0\30\0\22\\tZ\347\0\0\0\25\0\340\3"...,
iov_len=52}], 1) = 52
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\2\0\4\0\33\0\340\3\0@\0\0\230\1\340\3", iov_len=16}], 1)
= 16
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\22\0\7\0\33\0\340\3y\1\0\0\6\0\0\0
\0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745bd0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745bd4, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\22\0\7\0\25\0\340\3y\1\0\0\6\0\0\0
\0\0\0\1\0\0\0Sk\316\3\10\0\2\0"..., iov_len=40}], 1) = 40
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745f40, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd5a745f44, FUTEX_WAIT_PRIVATE, 1, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x4aafe80798, FUTEX_WAKE_PRIVATE, 1) = 0
Over and over.
Best.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages kdenlive depends on:
ii ffmpeg 7:3.2.6-1+b3
ii kded55.28.0-1
ii kdenlive-data17.04.3-1
ii kinit5.28.0-1
ii kio 5.28.0-2
ii libc62.24-12
ii libgcc1 1:7.1.0-10
ii libgl1-mesa-glx [libgl1] 17.1.4-1
ii libglu1-mesa [libglu1] 9.0.0-2.1
ii libkf5archive5 5.28.0-2
ii libkf5attica55.28.0-1
ii libkf5auth5 5.28.0-2
ii libkf5bookmarks5 5.28.0-1
ii libkf5codecs55.28.0-1+b2
ii libkf5completion55.28.0-1
ii libkf5configcore55.28.0-2
ii libkf5configgui5 5.28.0
Bug#869774: Corrections - propably wrong cause
Control: submitter -1 Shevek Mandragou On Wed, Jul 26, 2017 at 02:18:57PM +0200, Shevek Mandragou wrote: > Hi there, > > OP here, I'm sorry but I noticed that i made a couple of mistakes: > > a) the email address I submitted with the above bugreport no longer > exists. Please use this one instead. > > b) I though that enigmail broke after a recent upgrade, but according to > changelog > (http://metadata.ftp-master.debian.org/changelogs/main/e/enigmail/enigmail_1.8.2-4~deb8u1_changelog) > it seems that the last jessie upgrade of the package (a security > upgrade) was actually on 22 Nov 2015 (really!?!?) Your bug report says: > Versions of packages enigmail depends on: >... > ii thunderbird [icedove] 1:52.2.1-4~deb8u1 https://www.debian.org/security/2017/dsa-3918 The timing of your email mataches the Thunderbird 45 -> 52 upgrade in jessie, and this would not be the first time that a Thunderbird update requires an enigmail update in jessie. > Left with that, I currently have no more ideas how to find the real > source of the problem. Since we are using enigmail for work, this is an > outright desaster. I would appreciate any help in troubleshooting and > finding the actual cause of the problem. Installing the enigmail package from stretch or the latest one from unstable might fix your problem. Something like that is then also required for jessie (relevant people added to the recipients of this email). On Wed, Jul 26, 2017 at 03:20:41PM +0200, Paul van der Vlis wrote: >... > I have the same problem, I also get the error "This is an encrypted > OpenPGP message. In order to decrypt this mail, you need to install an > OpenPGP add-on." But Enigmail is installed. A reboot did not help. > > As a work-arround I've downloaded Enigmail from Debian 9, and installed > it using "dpkg -i". > > I can encrypt messages without a problem now, but when I decrypt a > message I get this alert: > -- > Enigmail alert: > > GnuPG reported an error in the communication with gpg-agent (a component > of GnuPG). >... After a short look at [1] there seem to be problems with Thunderbird 52 left in the enigmail 1.9.7 in Debian 9, that are either fixed in 1.9.8.1 in Debian unstable or might even require further upstream fixes. Is your problem fixed when you install the 2:1.9.8.1-1 package from unstable? cu Adrian [1] https://sourceforge.net/p/enigmail/bugs/687/ BTW: I am not the maintainer and not even a user of enigmail. -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#869774: Corrections - propably wrong cause
Processing control commands: > submitter -1 Shevek Mandragou Bug #869774 [enigmail] enigmail: Can no longer de- oder encrypt mails since update to 2:1.8.2-4~deb8u1 Changed Bug submitter to 'Shevek Mandragou ' from 'shevek '. -- 869774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raising severity since fixed in stable but not yet in unstable
Processing commands for cont...@bugs.debian.org: > severity 863840 serious Bug #863840 [src:qemu] qemu: CVE-2017-9310: net: infinite loop in e1000e NIC emulation Severity set to 'serious' from 'important' > severity 863943 serious Bug #863943 [src:qemu] qemu: CVE-2017-9330: usb: ohci: infinite loop due to incorrect return value Severity set to 'serious' from 'normal' > severity 864216 serious Bug #864216 [src:qemu] qemu: CVE-2017-9373 ide: ahci host memory leakage during hotunplug Severity set to 'serious' from 'normal' > severity 864219 serious Bug #864219 [src:qemu] qemu: CVE-2017-9375: usb: xhci infinite recursive call via xhci_kick_ep Severity set to 'serious' from 'normal' > severity 864568 serious Bug #864568 [src:qemu] qemu: CVE-2017-9374: usb: ehci host memory leakage during hotunplug Severity set to 'serious' from 'normal' > severity 866674 serious Bug #866674 [src:qemu] qemu: CVE-2017-10664: qemu-nbd: server breaks with SIGPIPE upon client abort Severity set to 'serious' from 'important' > severity 865755 serious Bug #865755 [src:qemu] qemu: CVE-2017-9524: nbd: segmentation fault due to client non-negotiation Severity set to 'serious' from 'important' > severity 869706 serious Bug #869706 [src:qemu] qemu: CVE-2017-10911 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 863840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863840 863943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863943 864216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864216 864219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864219 864568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864568 865755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865755 866674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866674 869706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Version tracking fix
Processing commands for cont...@bugs.debian.org: > found 869774 2:1.8.2-4 Bug #869774 [enigmail] enigmail: Can no longer de- oder encrypt mails since update to 2:1.8.2-4~deb8u1 Marked as found in versions enigmail/2:1.8.2-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 869774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.
Package: libreoffice Version: 1:5.3.5~rc1-3 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I did an update 3 days ago. * What exactly did you do (or not do) that was effective (or ineffective)? Nothing unusual. aptitude full-upgrade * What was the outcome of this action? LibreOffice doesn't work anymore. It crashes during startup. When started through the terminal it shows this: -- $ libreoffice X-Error: BadMatch (invalid parameter attributes) Major opcode: 154 Minor opcode: 5 Resource ID: 0x3400013 Serial No:218 (218) These errors are reported asynchronously, set environment variable SAL_SYNCHRONIZE to 1 to help debugging Application Error $ export SAL_SYNCHRONIZE=1 $ libreoffice X-Error: BadMatch (invalid parameter attributes) Major opcode: 154 Minor opcode: 5 Resource ID: 0x3400013 Serial No:364 (364) Application Error -- * What outcome did you expect instead? I'd love to edit some documents... Sorry, I can't be of more help here. Unless someone shows me how to do more debugging, I'm lost with a broken LO. Let me know, if I can do anything more! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice depends on: ii libreoffice-avmedia-backend-gstreamer 1:5.3.5~rc1-3 ii libreoffice-base 1:5.3.5~rc1-3 ii libreoffice-calc 1:5.3.5~rc1-3 ii libreoffice-core 1:5.3.5~rc1-3 ii libreoffice-draw 1:5.3.5~rc1-3 ii libreoffice-impress1:5.3.5~rc1-3 ii libreoffice-math 1:5.3.5~rc1-3 ii libreoffice-report-builder-bin 1:5.3.5~rc1-3 ii libreoffice-writer 1:5.3.5~rc1-3 ii python3-uno1:5.3.5~rc1-3 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-1 ii fonts-crosextra-carlito 20130920-1 ii fonts-dejavu2.37-1 ii fonts-linuxlibertine5.3.0-2 pn fonts-open-sans ii fonts-sil-gentium-basic 1.1-7 ii libreoffice-java-common 1:5.3.5~rc1-3 ii libreoffice-librelogo 1:5.3.5~rc1-3 ii libreoffice-nlpsolver 0.9+LibO5.3.5~rc1-3 ii libreoffice-ogltrans1:5.3.5~rc1-3 ii libreoffice-pdfimport 1:5.3.5~rc1-3 ii libreoffice-report-builder 1:5.3.5~rc1-3 ii libreoffice-script-provider-bsh 1:5.3.5~rc1-3 ii libreoffice-script-provider-js 1:5.3.5~rc1-3 ii libreoffice-script-provider-python 1:5.3.5~rc1-3 ii libreoffice-sdbc-postgresql 1:5.3.5~rc1-3 ii libreoffice-wiki-publisher 1.2.0+LibO5.3.5~rc1-3 Versions of packages libreoffice suggests: ii cups-bsd 2.2.4-3 ii default-jre [java6-runtime]2:1.8-59 ii gstreamer1.0-libav 1:1.12.2-dmo1 ii gstreamer1.0-plugins-bad 1:1.12.2-dmo1 ii gstreamer1.0-plugins-base 1.12.2-1 ii gstreamer1.0-plugins-good 1.12.2-1 ii gstreamer1.0-plugins-ugly 1:1.12.2-dmo1 ii hunspell-en-us [hunspell-dictionary] 20070829-7 ii hyphen-pt-pt [hyphen-hyphenation-patterns] 1:5.2.5-1 pn iceweasel | firefox | icedove | thunderbird | iceape- ii imagemagick8:6.9.7.4+dfsg-12+b1 ii imagemagick-6.q16 [imagemagick]8:6.9.7.4+dfsg-12+b1 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 pn libreoffice-gnome | libreoffice-kde pn libreoffice-grammarcheck pn libreoffice-help pn libreoffice-l10n pn libreoffice-officebean pn libsane ii libxrender11:0.9.10-1 pn myspell-dictionary pn mythes-thesaurus pn
Processed: Re: Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.
Processing commands for cont...@bugs.debian.org: > tag 869874 + moreinfo Bug #869874 [libreoffice] libreoffice: broken. LibreOffice crashes at during startup. Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 869874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.
tag 869874 + moreinfo thanks Hi, On Thu, Jul 27, 2017 at 12:03:43PM +0200, chris_blues wrote: > Severity: grave > > > Justification: renders package unusable So you claim it happens for everyone. I don't believe so. >* What was the outcome of this action? >LibreOffice doesn't work anymore. It crashes during startup. >When started through the terminal it shows this: > > -- > $ libreoffice > X-Error: BadMatch (invalid parameter attributes) > Major opcode: 154 > Minor opcode: 5 > Resource ID: 0x3400013 > Serial No:218 (218) > These errors are reported asynchronously, > set environment variable SAL_SYNCHRONIZE to 1 to help debugging > Application Error > > $ export SAL_SYNCHRONIZE=1 > $ libreoffice > X-Error: BadMatch (invalid parameter attributes) > Major opcode: 154 > Minor opcode: 5 > Resource ID: 0x3400013 > Serial No:364 (364) > Application Error > -- See http://bugs.debian.org/868507. Giving the information requested there would actually be nice. Try without the binary nvidia drivers if you used them? And/or try installing -gtk3 if you use a Gtk3-using desktop, that apparently helps for the original bug submitter... Regards, Rene
Bug#869880: CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839
Source: freerdp Severity: grave Tags: security Hi, please see: https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0341 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0340 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0339 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0338 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0337 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0336 Fix is here: https://github.com/FreeRDP/FreeRDP/pull/4055/commits/8292b4558f0684065ce1f58db7783cc426099223 Cheers, Moritz
Bug#869884: chemical-mime-data: Local copy of intltool-* fails with perl 5.26
Source: chemical-mime-data
Version: 0.1.94-6
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/chemical-mime-data.html
...
Making check in po
make[2]: Entering directory '/build/1st/chemical-mime-data-0.1.94/po'
INTLTOOL_EXTRACT=../intltool-extract srcdir=. ../intltool-update
--gettext-package chemical-mime-data --pot
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
m/^(.*)\${ <-- HERE ?([A-Z_]+)}?(.*)$/ at ../intltool-update line 875.
Makefile:95: recipe for target 'chemical-mime-data.pot' failed
make[2]: *** [chemical-mime-data.pot] Error 2
Bug#869774: Problems with enigmail
On Wed, 26 Jul 2017 15:20:41 +0200 Paul van der Vlis wrote: > As a work-arround I've downloaded Enigmail from Debian 9, and installed > it using "dpkg -i". > > I can encrypt messages without a problem now, (...) They are NOT encyrpted and sended in plain text! What I did now is this and it seems to be a working work-arround: apt remove thunderbird icedove apt install thunderbird=1:45.8.0-3~deb8u1 apt install thunderbird-l10n-nl=1:45.8.0-3~deb8u1 apt install lightning=1:45.8.0-3~deb8u1 apt install lightning-l10n-nl=1:45.8.0-3~deb8u1 apt install icedove=1:45.8.0-3~deb8u1 apt install enigmail=2:1.8.2-4~deb8u1 apt -t jessie-backports install xul-ext-sogo-connector After this you need also do some kind of pinning. With regards, Paul van der Vlis
Bug#869885: lacme FTBFS with pandoc 1.19.1
Source: lacme Version: 0.3-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lacme.html ... dh_auto_build make -j1 make[1]: Entering directory '/build/1st/lacme-0.3' jq: error (at :1): Cannot index object with number pandoc: Error in $: not enough input CallStack (from HasCallStack): error, called at src/Text/Pandoc/Error.hs:55:28 in pandoc-1.19.1-Fq5EX61fpM1KVuqnJRnI0N:Text.Pandoc.Error Makefile:7: recipe for target 'lacme-accountd.1' failed make[1]: *** [lacme-accountd.1] Error 1
Bug#869887: telepathy-logger-qt FTBFS: No such file or directory: spec-logger.xml
Source: telepathy-logger-qt Version: 15.04.0-2 Severity: serious Tags: buster sid Some recent change in unstable makes telepathy-logger-qt FTBFS: https://tests.reproducible-builds.org/debian/history/telepathy-logger-qt.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/telepathy-logger-qt.html ... [ 7%] Generating _gen/stable-spec.xml cd /build/1st/telepathy-logger-qt-15.04.0/obj-x86_64-linux-gnu/TelepathyLoggerQt && /usr/bin/python /build/1st/telepathy-logger-qt-15.04.0/tools/xincludator.py /build/1st/telepathy-logger-qt-15.04.0/TelepathyLoggerQt/stable-interfaces.xml > /build/1st/telepathy-logger-qt-15.04.0/obj-x86_64-linux-gnu/TelepathyLoggerQt/_gen/stable-spec.xml Traceback (most recent call last): File "/build/1st/telepathy-logger-qt-15.04.0/tools/qt-client-gen.py", line 547, in Generator(dict(options))() File "/build/1st/telepathy-logger-qt-15.04.0/tools/qt-client-gen.py", line 44, in __init__ ifacedom = xml.dom.minidom.parse(opts['--ifacexml']) File "/usr/lib/python2.7/xml/dom/minidom.py", line 1918, in parse return expatbuilder.parse(file) File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 922, in parse fp = open(file, 'rb') IOError: [Errno 2] No such file or directory: '/build/1st/telepathy-logger-qt-15.04.0/obj-x86_64-linux-gnu/TelepathyLoggerQt/_gen/spec-logger.xml' TelepathyLoggerQt/CMakeFiles/telepathy-logger-qt_autogen.dir/build.make:92: recipe for target 'TelepathyLoggerQt/_gen/cli-logger.h' failed
Bug#869880: CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839
Hi, On Thu, Jul 27, 2017 at 01:21:58PM +0200, Moritz Muehlenhoff wrote: > Source: freerdp > Severity: grave > Tags: security > > Hi, > please see: > https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0341 > https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0340 > https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0339 > https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0338 > https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0337 > https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0336 > > Fix is here: > https://github.com/FreeRDP/FreeRDP/pull/4055/commits/8292b4558f0684065ce1f58db7783cc426099223 This fix is for master. I'm working on a back port of it for 1.1 right now and will prepare a patch. Best regards, Bernhard
Bug#869874: [libreoffice]
Package: libreoffice Version: 1:5.3.4-4 Metooing here. Just updated LO and things started to go wrong: opening a document leads to a recovery warning dialog popping out which never ends. LO windows turned unusable and B&W colored. No gtk3, using KDE Plasma desktop and no NVIDIA drivers (Intel GPU). Regards, Antonio --- System information. --- Architecture: Kernel: Linux 4.11.0-1-amd64 Debian Release: buster/sid 500 testing ftp.es.debian.org 500 stable dl.google.com --- Package information. --- Depends(Version) | Installed -+- === libreoffice-base | 1:5.3.4-4 libreoffice-calc | 1:5.3.4-4 libreoffice-core (= 1:5.3.4-4) | 1:5.3.4-4 libreoffice-draw | 1:5.3.4-4 libreoffice-impress | 1:5.3.4-4 libreoffice-math | 1:5.3.4-4 libreoffice-report-builder-bin | 1:5.3.4-4 libreoffice-writer | 1:5.3.4-4 libreoffice-avmedia-backend-gstreamer| 1:5.3.4-4 OR libreoffice-avmedia-backend-vlc | python3-uno (>= 4.4.0~beta2) | 1:5.3.4-4 fontconfig | 2.12.3-0.2 fonts-opensymbol | 2:102.10+LibO5.3.4-4 libreoffice-common (>> 1:5.3.4) | 1:5.3.4-4 ure(>= 5.3.0~beta1~) | 5.3.4-4 libboost-date-time1.62.0 | 1.62.0+dfsg-4+b1 libc6 (>= 2.16) | libcairo2(>= 1.14.0) | libclucene-contribs1v5 (>= 2.3.3.4+dfsg) | libclucene-core1v5 (>= 2.3.3.4+dfsg) | libcmis-0.5-5v5 (>= 0.5.1+git20160603) | libcups2 (>= 1.4.0) | libcurl3-gnutls (>= 7.16.2) | libdbus-1-3 (>= 1.9.14) | libdbus-glib-1-2 (>= 0.78) | libdconf1(>= 0.14.0) | libeot0 | libepoxy0 (>= 1.0) | libexpat1 (>= 2.0.1) | libexttextcat-2.0-0 (>= 2.2-8) | libfontconfig1 (>= 2.12) | libfreetype6 (>= 2.3.5) | libgcc1 (>= 1:3.4) | libgl1-mesa-glx | OR libgl1 | libglib2.0-0 (>= 2.31.8) | libgltf-0.1-1| libgraphite2-3(>= 1.2.2) | libharfbuzz-icu0 (>= 0.9.42) | libharfbuzz0b(>= 0.9.42) | libhunspell-1.6-0| libhyphen0(>= 2.7.1) | libice6 (>= 1:1.0.0) | libicu57(>= 57.1-1~) | libjpeg62-turbo (>= 1.3.1) | liblcms2-2 (>= 2.2+git20110628) | libldap-2.4-2 (>= 2.4.7) | libmythes-1.2-0 | libneon27-gnutls | libnspr4 (>= 2:4.9-2~) | libnss3 (>= 2:3.16) | libodfgen-0.1-1 | liborcus-0.12-0 | libpcre3 | libpng16-16 (>= 1.6.2-1) | librevenge-0.0-0 | libsm6 | libstdc++6 (>= 5.2) | libx11-6 | libxext6 | libxinerama1
Bug#869888: otb FTBFS with cmake 3.9.0
Source: otb Version: 6.0.0+dfsg-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/otb.html ... -- Found LibSVM: /usr/lib/libsvm.so -- Found OpenCV: /usr/lib/x86_64-linux-gnu/libopencv_core.so (found version "2.4.9") -- Try to compile libsiftfast.cpp -- yes. CMake Error at Modules/ThirdParty/SiftFast/src/CMakeLists.txt:54 (else): A duplicate ELSE command was found inside an IF block. -- Configuring incomplete, errors occurred!
Bug#869889: bladerf FTBFS with cmake 3.9.0
Source: bladerf Version: 0.2016.06-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bladerf.html ... -- Looking for pthread.h -- Looking for pthread.h - found -- Looking for pthread_create -- Looking for pthread_create - not found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE -- libbladeRF version: 1.7.2-0.2016.06-1 -- Found Doxygen: /usr/bin/doxygen (found version "1.8.13") found components: doxygen missing components: dot -- Configured to build libbladeRF API documentation. -- nuand bladeRF udev rules will be installed to '/lib/udev/rules.d' upon running 'make install' CMake Error at host/misc/udev/CMakeLists.txt:44 (else): A duplicate ELSE command was found inside an IF block. -- Configuring incomplete, errors occurred!
Processed: Re: Bug#869888: otb FTBFS with cmake 3.9.0
Processing control commands: > tags -1 pending Bug #869888 [src:otb] otb FTBFS with cmake 3.9.0 Added tag(s) pending. -- 869888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869888: otb FTBFS with cmake 3.9.0
Control: tags -1 pending Hi Adrian, Thanks for reporting this issue. A patch has been added in git and a new upload to unstable will follow shortly. Kind Regards, Bas
Bug#868860: Preparation of the transition to OCaml 4.05.0: status update
Stéphane Glondu: > On 22/07/2017 19:48, Ximin Luo wrote: >> Sadly we now have one new failure, on arm64: >> >> https://buildd.debian.org/status/fetch.php?pkg=ocaml&arch=arm64&ver=4.05.0-5&stamp=1500739972&raw=0 >> >> E: Build killed with signal TERM after 150 minutes of inactivity >> >> Even though this was built in experimental, it was built with the binutils >> from sid: >> >> [..] >> Get:21 http://mirror.netcologne.de/debian unstable/main arm64 binutils-dev >> arm64 2.28-6 [2182 kB] >> [..] >> Selecting previously unselected package binutils-dev. >> Preparing to unpack .../19-binutils-dev_2.28-6_arm64.deb ... >> Unpacking binutils-dev (2.28-6) ... >> [..] >> >> This did not happen with the previous builds, and I didn't change anything >> relating to arm64. >> >> However after reading https://caml.inria.fr/mantis/view.php?id=7585 I wonder >> if this is just the same issue? Apparently ocaml will generated aarch64 >> instructions that on some corner cases (which I don't understand) are >> incorrect and the new binutils simply rejects these? Perhaps with the old >> binutils, these same faulty corner cases will sometimes result in these test >> suite timeouts? > > Did you see #868860? > > If nobody cares, maybe we could just drop native support on arm64? > We are making a bit of process over on the upstream mantis ticket. In the worst case scenario if there is no further progress, I think it will be possible to retain native support on arm64 but drop native-dynlink spport. I'll give it a few more days and if nothing further happens I'll do a upload like that. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Bug#869874: [libreoffice]
On Thu, Jul 27, 2017 at 12:41:06PM +0100, Antonio Marcos López Alonso wrote: > Package: libreoffice > Version: 1:5.3.4-4 > > Metooing here. > > Just updated LO and things started to go wrong: opening a document leads to a "Just"? To 5.3.4-4? That one was obsoleted sincd 6 days by 5.3.5 rc1. Which also is in testing since this morning. So how did you upgrade to 5.3.4-4 "just (now)"? > recovery warning dialog popping out which never ends. LO windows turned > unusable and B&W colored. And what makes you think it's the same symptoms like the bug you reply to? Regsrds, Rene
Bug#868618: marked as done (flightgear FTBFS: Could not find a package configuration file provided by "Qt5Qml")
Your message dated Thu, 27 Jul 2017 12:49:00 + with message-id and subject line Bug#868618: fixed in flightgear 1:2017.2.1+dfsg-2 has caused the Debian Bug report #868618, regarding flightgear FTBFS: Could not find a package configuration file provided by "Qt5Qml" 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.) -- 868618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flightgear Version: 1:2017.2.1+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=flightgear&suite=sid ... -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Checking for module 'dbus-1' -- Found dbus-1, version 1.10.20 -- Using DBus -- Qt launcher enabled, checking for Qt 5.1 / qmake CMake Warning at /usr/lib/aarch64-linux-gnu/cmake/Qt5/Qt5Config.cmake:26 (find_package): Could not find a package configuration file provided by "Qt5Qml" with any of the following names: Qt5QmlConfig.cmake qt5qml-config.cmake Add the installation prefix of "Qt5Qml" to CMAKE_PREFIX_PATH or set "Qt5Qml_DIR" to a directory containing one of the above files. If "Qt5Qml" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:314 (find_package) CMake Warning at CMakeLists.txt:314 (find_package): Found package configuration file: /usr/lib/aarch64-linux-gnu/cmake/Qt5/Qt5Config.cmake but it set Qt5_FOUND to FALSE so package "Qt5" is considered to be NOT FOUND. Reason given by package: Failed to find Qt5 component "Qml" config file at "/usr/lib/aarch64-linux-gnu/cmake/Qt5Qml/Qt5QmlConfig.cmake" -- Will enable Qt launcher GUI -- Qt5Widgets version: 5.7.1 -- Qt5Widgets include dir: /usr/include/aarch64-linux-gnu/qt5/;/usr/include/aarch64-linux-gnu/qt5/QtWidgets;/usr/include/aarch64-linux-gnu/qt5/QtGui;/usr/include/aarch64-linux-gnu/qt5/QtCore;/usr/lib/aarch64-linux-gnu/qt5//mkspecs/linux-g++;/usr/include -- /usr/include -- adding runtime JS dependencies -- Found PLIB: optimized;/usr/lib/libplibpuaux.so;debug;/usr/lib/libplibpuaux.so;optimized;/usr/lib/libplibjs.so;debug;/usr/lib/libplibjs.so;optimized;/usr/lib/libplibpu.so;debug;/usr/lib/libplibpu.so;optimized;/usr/lib/libplibfnt.so;debug;/usr/lib/libplibfnt.so;optimized;/usr/lib/libplibsg.so;debug;/usr/lib/libplibsg.so;optimized;/usr/lib/libplibul.so;debug;/usr/lib/libplibul.so -- Min Simgear version is 2017.2.0 -- Found ZLIB: /usr/lib/aarch64-linux-gnu/libz.so (found version "1.2.8") -- Looking for unistd.h -- Looking for unistd.h - found -- Looking for sys/time.h -- Looking for sys/time.h - found -- Looking for windows.h -- Looking for windows.h - not found -- RTI: DISABLED -- OpenMP: DISABLED -- SSE/SSE2 support: ENABLED -- Looking for mkfifo -- Looking for mkfifo - found -- Using GSM includes at: /usr/include -- Using GSM libraries: /usr/lib/aarch64-linux-gnu/libgsm.so -- Using speex includes at: /usr/include -- Using speex libraries: /usr/lib/aarch64-linux-gnu/libspeex.so -- Using speex extended library includes at: /usr/include -- Using speex extended library libraries: /usr/lib/aarch64-linux-gnu/libspeexdsp.so -- Using Flite includes at: /usr/include/flite -- Using Flite libraries: /usr/lib/aarch64-linux-gnu/libflite.so;/usr/lib/aarch64-linux-gnu/libflite_cmu_us_kal.so;/usr/lib/aarch64-linux-gnu/libflite_cmulex.so;/usr/lib/aarch64-linux-gnu/libflite_usenglish.so -- Using HTS engine includes for Flite/HTS Engine at: /usr/include -- Using HTS engine includes at: /usr/include -- Using HTS engine libraries: /usr/lib/aarch64-linux-gnu/libHTSEngine.so -- Found PNG: /usr/lib/aarch64-linux-gnu/libpng.so (found version "1.6.30") -- Could NOT find GLEW (missing: GLEW_INCLUDE_DIR GLEW_LIBRARY) -- Could NOT find Freetype (missing: FREETYPE_LIBRARY FREETYPE_INCLUDE_DIRS) CMake Warning at utils/fgpanel/CMakeLists.txt:7 (message): FGPanel enabled, but some dependencies are missing -- libPNG: TRUE -- OpenGL: TRUE -- GLEW: FALSE -- Freetype: FALSE -- Found OpenAL: /usr/lib/aarch64-linux-gnu/libopenal.so -- Tests: ENABLED -- Configuring done CMake Error at src/GUI/CMakeLists.txt:85 (add_library): Target "fglauncher" links to target "Qt5::Qml" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? CMake Error at src/Main/CMakeLists.txt:75 (add_executable): Target "fgfs" links to target "Qt5::Qml" but the target was not found. Perhaps a find_package() call is missing for an I
Bug#863631: marked as done (sympa: trashes configuration on update without asking)
Your message dated Thu, 27 Jul 2017 12:49:41 + with message-id and subject line Bug#863631: fixed in sympa 6.2.18~dfsg-1 has caused the Debian Bug report #863631, regarding sympa: trashes configuration on update without asking 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.) -- 863631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sympa Version: 6.2.16~dfsg-3 Severity: critical Justification: causes serious data loss The upgrade to 6.2.16~dfsg-3 from 6.2.16~dfsg-2 in stretch just ditched SYMPA's config files on my system, leaving it in a broken way, even in such a broken way that users who tried sending mails did not receive an error and thought things went through. I think some actions would even have led to destruction of database data. I have no idea why the maintainer scripts decided to do that. I recovered from etckeeper and a system backup. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sympa depends on: ii adduser 3.115 ii ca-certificates 20161130+nmu1 ii dbconfig-common 2.0.8 ii debconf [debconf-2.0] 1.5.60 ii fonts-font-awesome4.7.0~dfsg-1 ii init-system-helpers 1.48 ii libarchive-zip-perl 1.59-1 ii libc6 2.24-10 ii libcgi-fast-perl 1:2.12-1 ii libcgi-pm-perl4.35-1 ii libclass-singleton-perl 1.5-1 ii libcrypt-openssl-x509-perl1.8.7-3 ii libcrypt-smime-perl 0.19-2 ii libdatetime-format-mail-perl 0.4030-1 ii libdbd-csv-perl 0.4900-1 ii libdbd-mysql-perl 4.041-2 ii libdbd-pg-perl3.5.3-1+b2 ii libdbd-sqlite3-perl 1.54-1 ii libdbi-perl 1.636-1+b1 ii libfcgi-perl 0.78-2 ii libfile-copy-recursive-perl 0.38-1 ii libfile-nfslock-perl 1.27-1 ii libhtml-format-perl 2.12-1 ii libhtml-stripscripts-parser-perl 1.03-1 ii libhtml-tree-perl 5.03-2 ii libintl-perl 1.26-2 ii libio-stringy-perl2.111-2 ii libjs-jquery 3.1.1-2 ii libjs-jquery-migrate-11.4.1-1 ii libjs-jquery-placeholder 2.3.1-2 ii libjs-jquery-ui 1.12.1+dfsg-4 ii libjs-modernizr 2.6.2+ds1-1 ii libjs-twitter-bootstrap 2.0.2+dfsg-10 ii libmail-dkim-perl 0.40-1 ii libmailtools-perl 2.18-1 ii libmime-charset-perl 1.012-2 ii libmime-encwords-perl 1.014.3-2 ii libmime-lite-html-perl1.24-2 ii libmime-tools-perl5.508-1 ii libmsgcat-perl1.03-6+b3 ii libnet-cidr-perl 0.18-1 ii libnet-dns-perl 1.07-1 ii libnet-ldap-perl 1:0.6500+dfsg-1 ii libnet-netmask-perl 1.9022-1 ii libregexp-common-perl 2016060801-1 ii libsoap-lite-perl 1.20-1 ii libtemplate-perl 2.24-1.2+b3 ii libterm-progressbar-perl 2.18-1 ii libunicode-linebreak-perl 0.0.20160702-1+b1 ii libxml-libxml-perl2.0128+dfsg-1+b1 ii lsb-base 9.20161125 ii mhonarc 2.6.19-2 ii perl 5.24.1-2 pn perl:any ii postfix [mail-transport-agent]3.1.4-4 ii rsyslog [system-log-daemon] 8.24.0-1 ii sqlite3 3.16.2-3 Versions of packages sympa recommends: ii apache2-suexec-pristine [apache2-suexec] 2.4.25-3 ii doc-base 0.10.7 ii libapache2-mod-fcgid 1:2.3.9-1+b1 pn libcrypt-ciphersaber-perl ii libio-socket-ssl-perl 2.044-1 ii locales 2.24-10 ii logrotate 3.11.0-0.1 ii postgresql9.6+181 Versions of packages sympa suggests: ii apache2 [httpd-cgi] 2.4.25-3 pn libauthcas-perl pn libdbd-odbc-perl pn libdbd-oracle-
Bug#869880: CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839
We fixed it upstream on branch stable-1.1 as well now: https://github.com/FreeRDP/FreeRDP/commit/03ab68318966c3a22935a02838daaea7b7fbe96c Here is an updated version of the freerdp package with the patch included: https://github.com/bmiklautz/FreeRDP-debian/commit/68c33cec893630a6b6abbce82956739854158dca Best regards, Bernhard
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 869864 src:dojo Bug #869864 [dojo] dojo: New version available, watch file fails Bug reassigned from package 'dojo' to 'src:dojo'. No longer marked as found in versions 1.11.0. Ignoring request to alter fixed versions of bug #869864 to the same values previously set > forcemerge 852923 869864 Bug #852923 [src:dojo] dojo: FTBFS: OPTIMIZER FAILED: JavaException: java.lang.RuntimeException: null Bug #869864 [src:dojo] dojo: New version available, watch file fails Marked as found in versions dojo/1.11.0+dfsg-1. Added tag(s) sid, stretch, and buster. Merged 852923 869864 > tags 852923 fixed-upstream Bug #852923 [src:dojo] dojo: FTBFS: OPTIMIZER FAILED: JavaException: java.lang.RuntimeException: null Bug #869864 [src:dojo] dojo: New version available, watch file fails Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 852923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852923 869864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
Although lack of recent updates, we are still working on this problem. Barry (on CC) is allocated to work on this issue and should have updates soon.
Bug#868977: Confirm that I'm able to verify the problem
Hi, I was hoping that taking over the version from experimental to unstable might help to fix this bug but I can only confirm that I can reproduce the problem here. So it also happens for version 0.8.0. I've commited my attempt to Git and hope that somebody else might have a better clue. BTW, I failed to use gbp to build the package since the repository is lacking a pristine-tar branch and when I tried to import the existing tarball I've got so many conflicts with the Git repository that I simply gave up. Kind regards Andreas. -- http://fam-tille.de
Bug#869899: db5.3 FTBFS in buster.
Package: db5.3 Version: 5.3.28-13 Tags: buster Severity: serious db 5.3 fails to build in buster with libtool: error: 'libdb-5.3.la' is not a valid libtool archive I first noticed this in Raspbian but it is also happening on the Debian reproducible builds testing so it doesn't seem to be raspbian specific.
Bug#868977: Confirm that I'm able to verify the problem
On July 27, 2017 9:23:16 AM EDT, Andreas Tille wrote: >Hi, > >I was hoping that taking over the version from experimental to unstable >might help to fix this bug but I can only confirm that I can reproduce >the problem here. So it also happens for version 0.8.0. I've commited >my attempt to Git and hope that somebody else might have a better clue. > >BTW, I failed to use gbp to build the package since the repository is >lacking a pristine-tar branch and when I tried to import the existing >tarball I've got so many conflicts with the Git repository that I >simply >gave up. > >Kind regards > > Andreas. I can do it in 10 minutes.
Bug#868977: Confirm that I'm able to verify the problem
On Thu, 27 Jul 2017, Andreas Tille wrote: > Hi, > I was hoping that taking over the version from experimental to unstable > might help to fix this bug but I can only confirm that I can reproduce > the problem here. So it also happens for version 0.8.0. I've commited > my attempt to Git and hope that somebody else might have a better clue. > BTW, I failed to use gbp to build the package since the repository is > lacking a pristine-tar branch and when I tried to import the existing > tarball I've got so many conflicts with the Git repository that I simply > gave up. Is there any demand/requirement for debhelper 10 for this package? Could we settle on 9 (to ease backportability to old jessie and alike)? -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#868977: Confirm that I'm able to verify the problem
On Thu, 27 Jul 2017, Yaroslav Halchenko wrote: > Is there any demand/requirement for debhelper 10 for this package? > Could we settle on 9 (to ease backportability to old jessie and alike)? I would guess that the answers are no and yes, fixed up, building now, will upload whenever done Cheers and thanks! -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik signature.asc Description: PGP signature
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
Control: affects 869774 + thunderbird Control: retitle 869774 thunderbird 52 needs enigmail 1.9.8.1 or later Control: forwarded 869774 https://sourceforge.net/p/enigmail/bugs/687/ Hi there-- On Thu 2017-07-27 12:42:26 +0300, Adrian Bunk wrote: > After a short look at [1] there seem to be problems with Thunderbird 52 > left in the enigmail 1.9.7 in Debian 9, that are either fixed in 1.9.8.1 > in Debian unstable or might even require further upstream fixes. > > Is your problem fixed when you install the 2:1.9.8.1-1 package from unstable? I can confirm that enigmail 2:1.9.8.1-1 (from debian testing) installs successfully on jessie and that it appears to fix the underlying problem. I can also confirm that upstream doesn't expect enigmail 1.8.x to work with thunderbird 52. I'm looking into creating a patch for enigmail 1.9.8.1-1 on jessie, and will also look into such an update for stretch. I think this could have been avoided if the newer version of thunderbird had been marked as "Breaks: enigmail < 1.9.8" or something similar, though it's not clear how the t-bird maintainers are supposed to know that sort of information about every possible extension. Perhaps enigmail needs to be special cased since it seems to have more of a history of this kind of problem? --dkg
Processed: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
Processing control commands: > affects 869774 + thunderbird Bug #869774 [enigmail] enigmail: Can no longer de- oder encrypt mails since update to 2:1.8.2-4~deb8u1 Added indication that 869774 affects thunderbird > retitle 869774 thunderbird 52 needs enigmail 1.9.8.1 or later Bug #869774 [enigmail] enigmail: Can no longer de- oder encrypt mails since update to 2:1.8.2-4~deb8u1 Changed Bug title to 'thunderbird 52 needs enigmail 1.9.8.1 or later' from 'enigmail: Can no longer de- oder encrypt mails since update to 2:1.8.2-4~deb8u1'. > forwarded 869774 https://sourceforge.net/p/enigmail/bugs/687/ Bug #869774 [enigmail] thunderbird 52 needs enigmail 1.9.8.1 or later Set Bug forwarded-to-address to 'https://sourceforge.net/p/enigmail/bugs/687/'. -- 869774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868977: Confirm that I'm able to verify the problem
On Thu, 27 Jul 2017, Andreas Tille wrote: > Hi, > I was hoping that taking over the version from experimental to unstable > might help to fix this bug but I can only confirm that I can reproduce eh -- plain rebuild doesn't suffice -- tests still fail and some new failures happen: == ERROR: statsmodels.tsa.vector_ar.tests.test_var.TestVARResults.test_pickle -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/build/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/vector_ar/tests/test_var.py", line 463, in test_pickle res_unpickled = self.res.__class__.load(fh) File "/build/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/base/wrapper.py", line 77, in load return load_pickle(fname) File "/build/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/iolib/smpickle.py", line 32, in load_pickle return cPickle.load(fin) ValueError: non-string names in Numpy dtype unpickling and possibly more would need to dig in, may be later, meanwhile pushed my slight tune ups, feel welcome to fix up. You do know where to get the .orig.tar.gz ;) but just in case http://http.debian.net/debian/pool/main/s/statsmodels/statsmodels_0.8.0.orig.tar.gz -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
On Thu, Jul 27, 2017 at 09:59:46AM -0400, Daniel Kahn Gillmor wrote: > Control: affects 869774 + thunderbird > Control: retitle 869774 thunderbird 52 needs enigmail 1.9.8.1 or later > Control: forwarded 869774 https://sourceforge.net/p/enigmail/bugs/687/ > > Hi there-- > > On Thu 2017-07-27 12:42:26 +0300, Adrian Bunk wrote: > > After a short look at [1] there seem to be problems with Thunderbird 52 > > left in the enigmail 1.9.7 in Debian 9, that are either fixed in 1.9.8.1 > > in Debian unstable or might even require further upstream fixes. > > > > Is your problem fixed when you install the 2:1.9.8.1-1 package from > > unstable? > > I can confirm that enigmail 2:1.9.8.1-1 (from debian testing) installs > successfully on jessie and that it appears to fix the underlying > problem. > > I can also confirm that upstream doesn't expect enigmail 1.8.x to work > with thunderbird 52. > > I'm looking into creating a patch for enigmail 1.9.8.1-1 on jessie, and > will also look into such an update for stretch. We can provide a fixed 1.9.8.1-1 via jessie-security/stretch-security, but the current approach of providing Firefox/Thunderbird extensions in a stable release is madness and really needs to stop for buster. Neither the Firefox, Thunderbird maintainers or the security team can look after all these extensions. > I think this could have been avoided if the newer version of thunderbird > had been marked as "Breaks: enigmail < 1.9.8" or something similar, > though it's not clear how the t-bird maintainers are supposed to know > that sort of information about every possible extension. Perhaps > enigmail needs to be special cased since it seems to have more of a > history of this kind of problem? Every maintainer of a Firefox/Thunderbird extension needs to test older releases against the latest ESR once that reaches unstable. There's an overlap of several months during which we provide the old ESR in stable while the new ESR is available, this could've all been caught before release time. Cheers, Moritz
Bug#869909: qbs: fails to build anything
Package: qbs
Version: 1.8.1+dfsg-2
Severity: grave
Justification: renders package unusable
Hello!
Qbs always freezes when trying to build. I straced it and found out it was
looking for qbs_processlauncher in the wrong place (/usr/libexec/qbs/ instead
of /usr/lib/${DEB_HOST_MULTIARCH}/qbs/ where it is installed).
Snippet of the strace log:
execve("/usr/bin/../libexec/qbs/qbs_processlauncher",
["/usr/bin/../libexec/qbs/qbs_proc"..., "/tmp/qbs_processlauncher-5136"], [/*
81 vars */] = -1 ENOENT (No such file or directory)
I tried setting adding
QBS_RELATIVE_LIBEXEC_PATH=../lib/${DEB_HOST_MULTIARCH}/qbs to the qmake command
line but it broke some tests as it couldn't find qbs_processlauncher.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (980, 'testing'), (500, 'unstable-debug'),
(500, 'buildd-unstable'), (120, 'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel
Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages qbs depends on:
ii libc62.24-12
ii libgcc1 1:7.1.0-10
ii libqbscore1.81.8.1+dfsg-2
ii libqbsqtprofilesetup1.8 1.8.1+dfsg-2
ii libqt5core5a 5.7.1+dfsg-4
ii libqt5gui5 5.7.1+dfsg-4
ii libqt5network5 5.7.1+dfsg-4
ii libqt5widgets5 5.7.1+dfsg-4
ii libstdc++6 7.1.0-10
ii qbs-common 1.8.1+dfsg-2
qbs recommends no packages.
qbs suggests no packages.
-- no debconf information
Bug#869856: [Pkg-openssl-devel] Bug#869856: openssl: FTBFS: Testsuite failures
On Thu, Jul 27, 2017 at 12:02 AM, Kurt Roeckx wrote: > Is that reproducible? Yes, it's definitely reproducible on my machine. -- Daniel Schepler
Bug#867986: marked as done (CVE-2016-10396)
Your message dated Thu, 27 Jul 2017 15:22:11 + with message-id and subject line Bug#867986: fixed in ipsec-tools 1:0.8.2+20140711-9 has caused the Debian Bug report #867986, regarding CVE-2016-10396 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.) -- 867986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: racoon Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10396 Cheers, Moritz --- End Message --- --- Begin Message --- Source: ipsec-tools Source-Version: 1:0.8.2+20140711-9 We believe that the bug you reported is fixed in the latest version of ipsec-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 867...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated ipsec-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jul 2017 22:56:33 -0700 Source: ipsec-tools Binary: ipsec-tools racoon Architecture: source amd64 Version: 1:0.8.2+20140711-9 Distribution: unstable Urgency: medium Maintainer: pkg-ipsec-tools team Changed-By: Noah Meyerhans Description: ipsec-tools - IPsec utilities racoon - IPsec Internet Key Exchange daemon Closes: 867986 Changes: ipsec-tools (1:0.8.2+20140711-9) unstable; urgency=medium . * Import NetBSD's patch to address CVE-2016-10396 (Closes: #867986) * Update to debhelper compat level 10 * Update to policy 4.0 compliance. Checksums-Sha1: 176443cccd87855d55f4f77e6a6a94d71cd1bc44 2286 ipsec-tools_0.8.2+20140711-9.dsc 950cd6dd1cefef2284decc72714bdb5de68eada0 63828 ipsec-tools_0.8.2+20140711-9.debian.tar.xz 7494962b87d1067989a78239b49a059a40535336 112418 ipsec-tools-dbgsym_0.8.2+20140711-9_amd64.deb 8269d9b4486e1a1afdeb309a09752eed8b9e65e5 7081 ipsec-tools_0.8.2+20140711-9_amd64.buildinfo 79049fd22763da4f59bf4a2c0e29a2c7bb12e0fb 95090 ipsec-tools_0.8.2+20140711-9_amd64.deb ed0a30e6bd8ac331c27893c5d8c813ad101ab2cf 762474 racoon-dbgsym_0.8.2+20140711-9_amd64.deb 4f1349e97f6539c6ebf65f41e1eb455e0665e37c 385624 racoon_0.8.2+20140711-9_amd64.deb Checksums-Sha256: d8dca6866b1c622c1651843620df2ecd80129bfff71ccaa71ad8aeca23c715fd 2286 ipsec-tools_0.8.2+20140711-9.dsc 7d8f71e8b48f931cfef1790c436469cb8344a0336c9c31be55071dad6b0906f6 63828 ipsec-tools_0.8.2+20140711-9.debian.tar.xz 3df8239f025e8901b3fb23cf6398a6a9dc023111c0ebf27aa3be59cb2824a020 112418 ipsec-tools-dbgsym_0.8.2+20140711-9_amd64.deb f0e31c905cca398bdba3fd5cc2e892ae9d0005374526a8e74d2f1f7a560c 7081 ipsec-tools_0.8.2+20140711-9_amd64.buildinfo d5ad5847af2c42c8766872eb3110489635c5d83e428ab90e992ff659bdf277ca 95090 ipsec-tools_0.8.2+20140711-9_amd64.deb e23c5dbfe190e6f89344aebe116ec5e12b8d613aab6e865b52c3efec6c853c44 762474 racoon-dbgsym_0.8.2+20140711-9_amd64.deb a54b1371868f1c41f7488928e44e1e8a81aee67163146d1910efd321337da30e 385624 racoon_0.8.2+20140711-9_amd64.deb Files: 8d86a66ec94ea287ad56e130c0ceeb3a 2286 net extra ipsec-tools_0.8.2+20140711-9.dsc 22ac88a912f869e9fddfc12bd58696cd 63828 net extra ipsec-tools_0.8.2+20140711-9.debian.tar.xz e26fa9ccd14160e0f282175de2147d5a 112418 debug extra ipsec-tools-dbgsym_0.8.2+20140711-9_amd64.deb 8e1ade5da2eb56385288d73dc5829732 7081 net extra ipsec-tools_0.8.2+20140711-9_amd64.buildinfo b55ad1318095bfb0e424f5e722a7b12f 95090 net extra ipsec-tools_0.8.2+20140711-9_amd64.deb c02b0f78b57fca1be0350d20a29d4d37 762474 debug extra racoon-dbgsym_0.8.2+20140711-9_amd64.deb c0b4d6aed98b2a68d3eafb6a52e7350b 385624 net extra racoon_0.8.2+20140711-9_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEpNGebtPBMx7yU+olHNjYVP5CUsEFAll6AMQACgkQHNjYVP5C UsEppw/8D5mhRF8X0t6qW9Jp3qSNv5XSxaD83skGxhuq7XXA6+jLtYu87zJ/sgp3 y5Fn7p8LkJxR5r7J6Xqj/dW2svyeNo1LWfMIKf/e8TA1I31meJNofzn1AvTKw/FU 1TehooVopkbN9PS97W8v5J07ZdBr058a+jcoIGCFUggPmmRAYn7Kv7NvSKV9HLhc yKlCi8dm7uRAw3AObsgaYMhzFyV7RltzxzIYdlo/AfsxWDqytPRipjl7qvrLLNzt /mcQZZN+tOveX8s+FA1tQUcx2tUKcE289YJnKexLvGpRbVa6NmhwRYUh9xkERqO5 B/5UKs/ebEUI2niwO8RPUpGWBoMxBMtRa1t5cfN+c4tWpE3HqS6Ev8EDq5r67FZE yky31GqyLYpC3Qlm/Dk74
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
On Thu, 27 Jul 2017 09:59:46 -0400 Daniel Kahn Gillmor wrote: > I can confirm that enigmail 2:1.9.8.1-1 (from debian testing) installs > successfully on jessie and that it appears to fix the underlying > problem. My experience is different: it installs without a problem, it gives warnings while decrypting. And it looks-like it encrypts, but it sent plain text. When I install it from Mozilla, it has the same problem on my machine, I am now back to Thunderbird 45 as a work-arround, what works fine. With regards, Paul van der Vlis -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Bug#869888: marked as done (otb FTBFS with cmake 3.9.0)
Your message dated Thu, 27 Jul 2017 15:26:12 + with message-id and subject line Bug#869888: fixed in otb 6.0.0+dfsg-3 has caused the Debian Bug report #869888, regarding otb FTBFS with cmake 3.9.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 869888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: otb Version: 6.0.0+dfsg-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/otb.html ... -- Found LibSVM: /usr/lib/libsvm.so -- Found OpenCV: /usr/lib/x86_64-linux-gnu/libopencv_core.so (found version "2.4.9") -- Try to compile libsiftfast.cpp -- yes. CMake Error at Modules/ThirdParty/SiftFast/src/CMakeLists.txt:54 (else): A duplicate ELSE command was found inside an IF block. -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: otb Source-Version: 6.0.0+dfsg-3 We believe that the bug you reported is fixed in the latest version of otb, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated otb 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, 27 Jul 2017 14:04:03 +0200 Source: otb Binary: libotb-dev otb-testdriver libotbice-6.0-1 libotbiolum-6.0-1 libotbiomstar-6.0-1 libotbioonera-6.0-1 libotbiorad-6.0-1 libotbiotilemap-6.0-1 libotbiogdal-6.0-1 libotbiobsq-6.0-1 libotbiokml-6.0-1 libotbcurladapters-6.0-1 libotbopenthreadsadapters-6.0-1 libotbossimadapters-6.0-1 libotbsampling-6.0-1 libotbsiftfast-6.0-1 libotbstatistics-6.0-1 libotbossimplugins-6.0-1 libotbimagemanipulation-6.0-1 libotbimageio-6.0-1 libotbimagebase-6.0-1 libotbgdaladapters-6.0-1 libotbedge-6.0-1 libotbcommandline-6.0-1 libotbcommandlineparser-6.0-1 libotbcommon-6.0-1 libotbcarto-6.0-1 libotbpolarimetry-6.0-1 libotbstreaming-6.0-1 libotbextendedfilename-6.0-1 libotbmathparser-6.0-1 libotbfuzzy-6.0-1 libotbmetadata-6.0-1 libotbmonteverdicore-6.0-1 libotbmonteverdigui-6.0-1 libotbprojection-6.0-1 libotbrcc8-6.0-1 libotbtestkernel-6.0-1 libotbtransform-6.0-1 libotbvectordatabase-6.0-1 libotbvectordataio-6.0-1 libotbwavelet-6.0-1 libotbsupervised-6.0-1 libotbqtadapters-6.0-1 libotbqtwidget-6.0-1 libotbapplicationengine-6.0-1 libotb-apps monteverdi otb-bin otb-bin-qt otb-i18n python-otb libotb Architecture: source amd64 all Version: 6.0.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Description: libotb - ORFEO Toolbox library metapackage libotb-apps - Plugins for ORFEO Toolbox applications libotb-dev - Free library of image processing algorithms - development libotbapplicationengine-6.0-1 - ORFEO Toolbox library - OTBApplicationEngine libotbcarto-6.0-1 - ORFEO Toolbox library - OTBCarto libotbcommandline-6.0-1 - ORFEO Toolbox library - OTBCommandLine libotbcommandlineparser-6.0-1 - ORFEO Toolbox library - OTBCommandLinePaser libotbcommon-6.0-1 - ORFEO Toolbox library - OTBCommon libotbcurladapters-6.0-1 - ORFEO Toolbox library - OTBCurlAdapters libotbedge-6.0-1 - ORFEO Toolbox library - OTBEdge libotbextendedfilename-6.0-1 - ORFEO Toolbox library - OTBExtendedFileName libotbfuzzy-6.0-1 - ORFEO Toolbox library - OTBFuzzy libotbgdaladapters-6.0-1 - ORFEO Toolbox library - OTBGdalAdapters libotbice-6.0-1 - ORFEO Toolbox library - OTBIce libotbimagebase-6.0-1 - ORFEO Toolbox library - OTBImageBase libotbimageio-6.0-1 - ORFEO Toolbox library - OTBImageIO libotbimagemanipulation-6.0-1 - ORFEO Toolbox library - OTBImageManipulation libotbiobsq-6.0-1 - ORFEO Toolbox library - OTBIOBSQ libotbiogdal-6.0-1 - ORFEO Toolbox library - OTBIOGDAL libotbiokml-6.0-1 - ORFEO Toolbox library - OTBIOKML libotbiolum-6.0-1 - ORFEO Toolbox library - OTBIOLUM libotbiomstar-6.0-1 - ORFEO Toolbox library - OTBIOMSTAR libotbioonera-6.0-1 - ORFEO Toolbox library - OTBIOONERA libotbiorad-6.0-1 - ORFEO Toolbox library - OTBIORAD libotbiotilemap-6.0-1 - ORFEO Toolbox library - OTBIOTileMap libotbmathparser-6.0-1 - ORFEO Too
Processed: severity of 869907 is grave, severity of 869910 is grave, severity of 869913 is grave ...
Processing commands for cont...@bugs.debian.org: > severity 869907 grave Bug #869907 [src:ghostscript] ghostscript: CVE-2017-9835: heap-buffer-overflow in gs_alloc_ref_array(ialloc.c) Severity set to 'grave' from 'important' > severity 869910 grave Bug #869910 [src:ghostscript] ghostscript: CVE-2017-9739: heap-buffer-overflow in Ins_JMPR Severity set to 'grave' from 'important' > severity 869913 grave Bug #869913 [src:ghostscript] ghostscript: CVE-2017-9727: heap-buffer-overflow in gx_ttfReader__Read(base/gxttfb.c) Severity set to 'grave' from 'important' > severity 869915 grave Bug #869915 [src:ghostscript] ghostscript: CVE-2017-9726: heap-use-after-free in Ins_MDRP(base/ttinterp.c) Severity set to 'grave' from 'important' > severity 869916 grave Bug #869916 [src:ghostscript] ghostscript: CVE-2017-9612: heap-use-after-free in Ins_IP(base/ttinterp.c) Severity set to 'grave' from 'important' > severity 869917 grave Bug #869917 [src:ghostscript] ghostscript: CVE-2017-9611: heap-buffer-overflow in Ins_MIRP(base/ttinterp.c) Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 869907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869907 869910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869910 869913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869913 869915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869915 869916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869916 869917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869165: nemo: Nemo crash when exploring folders
Hi, I have rebuild the package nemo on my laptop because the debug symbol package was not available. The following backtrace contains more information. Thread 1 "nemo" received signal SIGSEGV, Segmentation fault. 0x7fa2575db95a in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (gdb) bt #0 0x7fa2575db95a in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #1 0x557652560cfb in handle_icon_slow_two_click (event=0x55765421cdc0, icon=0x5576548b2ca0, container=0x557654118630) at nemo-icon-container.c:6364 #2 nemo_icon_container_did_not_drag (event=0x55765421cdc0, container=0x557654118630) at nemo-icon-container.c:4473 #3 button_release_event (widget=, event=0x55765421cdc0) at nemo-icon-container.c:4803 #4 0x7fa25907dba1 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x7fa2575b71a4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7fa2575d13a1 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x7fa2575d1fbf in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7fa2591ca57c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #9 0x7fa25907ab2e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #10 0x7fa25907cbee in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #11 0x7fa258b8de15 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #12 0x7fa258bbeea2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #13 0x7fa2572dd7f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fa2572dda60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fa2572ddb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fa25789972d in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #17 0x557652477bcd in main (argc=1, argv=0x7fff2e4c6758) at nemo-main.c:106 On Fri, Jul 21, 2017 at 10:24 AM, William MARTIN < william.mar...@power-lan.com> wrote: > Package: nemo > Version: 3.2.2-3 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I have fresh install of Debian Stretch with Cinnamon. > I have no extra theme, just visual effets disabled. > > Nemo crash randomly very often. > > Here a backtrace : > > Thread 1 "nemo" received signal SIGSEGV, Segmentation fault. > 0x7f4e1a2b195a in g_type_check_instance_cast () from > /usr/lib/x86_64-linux- > gnu/libgobject-2.0.so.0 > (gdb) bt > #0 0x7f4e1a2b195a in g_type_check_instance_cast () from > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > #1 0x55ec17d23cfb in ?? () > #2 0x7f4e1bd53ba1 in ?? () from /usr/lib/x86_64-linux-gnu/ > libgtk-3.so.0 > #3 0x7f4e1a28d1a4 in ?? () from /usr/lib/x86_64-linux- > gnu/libgobject-2.0.so.0 > #4 0x7f4e1a2a73a1 in g_signal_emit_valist () from > /usr/lib/x86_64-linux- > gnu/libgobject-2.0.so.0 > #5 0x7f4e1a2a7fbf in g_signal_emit () from /usr/lib/x86_64-linux- > gnu/libgobject-2.0.so.0 > #6 0x7f4e1bea057c in ?? () from /usr/lib/x86_64-linux-gnu/ > libgtk-3.so.0 > #7 0x7f4e1bd50b2e in ?? () from /usr/lib/x86_64-linux-gnu/ > libgtk-3.so.0 > #8 0x7f4e1bd52bee in gtk_main_do_event () from /usr/lib/x86_64-linux- > gnu/libgtk-3.so.0 > #9 0x7f4e1b863e15 in ?? () from /usr/lib/x86_64-linux-gnu/ > libgdk-3.so.0 > #10 0x7f4e1b894ea2 in ?? () from /usr/lib/x86_64-linux-gnu/ > libgdk-3.so.0 > #11 0x7f4e19fb37f7 in g_main_context_dispatch () from > /lib/x86_64-linux- > gnu/libglib-2.0.so.0 > #12 0x7f4e19fb3a60 in ?? () from /lib/x86_64-linux-gnu/libglib- > 2.0.so.0 > #13 0x7f4e19fb3b0c in g_main_context_iteration () from > /lib/x86_64-linux- > gnu/libglib-2.0.so.0 > #14 0x7f4e1a56f72d in g_application_run () from /usr/lib/x86_64-linux- > gnu/libgio-2.0.so.0 > #15 0x55ec17c3abcd in ?? () > #16 0x7f4e190bc2b1 in __libc_start_main (main=0x55ec17c3aaf0, argc=1, > argv=0x7ffd9740c9c8, init=, fini=, > rtld_fini=, stack_end=0x7ffd9740c9b8) > at ../csu/libc-start.c:291 > #17 0x55ec17c3ac3a in ?? () > > I have produce a core dump (~ 600 MB), i can provide it privatly to the > maintainer. > > Best regards, > > > > > > -- System Information: > Debian Release: 9.0 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages nemo depends on: > ii desktop-file-utils 0.23-1 > ii gsettings-desktop-schemas 3.22.0-1 > ii gvfs 1.30.4-1 > ii libatk1.0-02.22.0-1 > ii libc6 2.24-11+deb9u1 > ii libcairo-gobject2 1.14.8-1 > ii libcairo2 1.14.8-1 > ii libcinnamon-desktop4
Bug#869919: remove ruby-berkshelf-api-client?
package: ruby-berkshelf-api-client version: 2.0.2-1 severity: serious Upstream readme has this "This gem has been fully deprecated, and its API has been moved inside the berkshelf gem itself." I bumped into this package when trying to update ruby-faraday as its gemspec declares a tight dependency on faraday ~> 0.9.1 Can we remove this package from debian? signature.asc Description: OpenPGP digital signature
Bug#869922: policykit-1: members of group sudo become root with pkexec while ignoring /etc/sudoers
Package: policykit-1 Version: 0.105-18 Severity: grave Tags: security Justification: user security hole Dear Maintainer, If an unprivileged user is member of group sudo, he can achieve unrestricted root privileges with pkexec and his user password (instead of root password). This happens regardless if or if not package sudo is installed, and regardless of existing or non-existing entries in /etc/sudoers. Command sudo and group sudo were designed to allow single privileged commands for unprivileged users. Instead, pkexec allows full root access for members of group sudo. I expect: - pkexec does not regard group sudo. (clean way, unlinking polkit from sudo) or - pkexec regards entries in /etc/sudoers. (dirty way, pkexec should not be mixed with sudo) (Not regarding group sudo would also avoid prompting non-sudo-group users for passwords of sudo-group users) Thanks! Martin -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages policykit-1 depends on: ii dbus 1.10.18-1 ii libc6 2.24-11+deb9u1 ii libglib2.0-0 2.50.3-2 ii libpam-systemd 232-25+deb9u1 ii libpam0g 1.1.8-3.6 ii libpolkit-agent-1-00.105-18 ii libpolkit-backend-1-0 0.105-18 ii libpolkit-gobject-1-0 0.105-18 policykit-1 recommends no packages. policykit-1 suggests no packages. -- debconf-show failed
Bug#869922: [Pkg-utopia-maintainers] Bug#869922: policykit-1: members of group sudo become root with pkexec while ignoring /etc/sudoers
Control: severity -1 normal Control: close -1 Am 27.07.2017 um 17:53 schrieb mviereck: > Package: policykit-1 > Version: 0.105-18 > Severity: grave > Tags: security > Justification: user security hole > > Dear Maintainer, > > If an unprivileged user is member of group sudo, he can achieve unrestricted > root privileges with pkexec > and his user password (instead of root password). This happens regardless if > or if not package sudo is installed, > and regardless of existing or non-existing entries in /etc/sudoers. > > Command sudo and group sudo were designed to allow single privileged commands > for unprivileged users. This is not correct. The default sudo config ships %sudo ALL=(ALL:ALL) ALL I.e., a user in group sudo can run every command with root privileges. > Instead, pkexec allows full root access for members of group sudo. > > I expect: > - pkexec does not regard group sudo. (clean way, unlinking polkit from sudo) > or > - pkexec regards entries in /etc/sudoers. (dirty way, pkexec should not be > mixed with sudo) > > (Not regarding group sudo would also avoid prompting non-sudo-group users for > passwords of sudo-group users) Granting root-like access via group sudo is intended and not a security hole and the policykit policy is in line with the sudo policy here. Regards, Michael signature.asc Description: OpenPGP digital signature
Processed: Re: [Pkg-utopia-maintainers] Bug#869922: policykit-1: members of group sudo become root with pkexec while ignoring /etc/sudoers
Processing control commands: > severity -1 normal Bug #869922 [policykit-1] policykit-1: members of group sudo become root with pkexec while ignoring /etc/sudoers Severity set to 'normal' from 'grave' > close -1 Bug #869922 [policykit-1] policykit-1: members of group sudo become root with pkexec while ignoring /etc/sudoers Marked Bug as done -- 869922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868977: Confirm that I'm able to verify the problem
Hi Yaroslav, On Thu, Jul 27, 2017 at 09:44:10AM -0400, Yaroslav Halchenko wrote: > Is there any demand/requirement for debhelper 10 for this package? > Could we settle on 9 (to ease backportability to old jessie and alike)? Just to answer this question: 1. There is no demand - I just choose the latest compat level. 2. debhelper 10 is backported to Jessie Feel free to override my decision. Kind regards Andreas. -- http://fam-tille.de
Bug#869856: [Pkg-openssl-devel] Bug#869856: openssl: FTBFS: Testsuite failures
On Thu, Jul 27, 2017 at 08:14:45AM -0700, Daniel Schepler wrote:
> On Thu, Jul 27, 2017 at 12:02 AM, Kurt Roeckx wrote:
> > Is that reproducible?
>
> Yes, it's definitely reproducible on my machine.
Does the attached patch fix it?
Kurt
>From b72668a0d3586ee2560f0536c43e18991a4cfc6f Mon Sep 17 00:00:00 2001
From: Matt Caswell
Date: Fri, 26 May 2017 13:06:08 +0100
Subject: [PATCH] Fix a Proxy race condition
Issue #3562 describes a problem where a race condition can occur in the
Proxy such that a test "ok" line can appear in the middle of other text
causing the test harness to miss it. The issue is that we do not wait for
the client process to finish after the test is complete, so that process may
continue to write data to stdout/stderr at the same time that the test
harness does.
This commit fixes TLSProxy so that we always wait for the client process to
finish before continuing.
Fixes #3562
Reviewed-by: Richard Levitte
(Merged from https://github.com/openssl/openssl/pull/3567)
---
util/TLSProxy/Proxy.pm | 15 +++
1 file changed, 15 insertions(+)
diff --git a/util/TLSProxy/Proxy.pm b/util/TLSProxy/Proxy.pm
index a826cb5257..5c363e76ed 100644
--- a/util/TLSProxy/Proxy.pm
+++ b/util/TLSProxy/Proxy.pm
@@ -49,6 +49,7 @@ sub new
clientflags => "",
serverconnects => 1,
serverpid => 0,
+clientpid => 0,
reneg => 0,
sessionfile => undef,
@@ -113,6 +114,7 @@ sub clearClient
$self->{message_list} = [];
$self->{clientflags} = "";
$self->{sessionfile} = undef;
+$self->{clientpid} = 0;
$is_tls13 = 0;
$ciphersuite = undef;
@@ -240,6 +242,7 @@ sub clientstart
}
exec($execcmd);
}
+$self->clientpid($pid);
}
# Wait for incoming connection from client
@@ -338,6 +341,10 @@ sub clientstart
waitpid( $self->serverpid, 0);
die "exit code $? from server process\n" if $? != 0;
}
+die "clientpid is zero\n" if $self->clientpid == 0;
+print "Waiting for client process to close: ".$self->clientpid."\n";
+waitpid($self->clientpid, 0);
+
return 1;
}
@@ -531,6 +538,14 @@ sub serverpid
}
return $self->{serverpid};
}
+sub clientpid
+{
+my $self = shift;
+if (@_) {
+$self->{clientpid} = shift;
+}
+return $self->{clientpid};
+}
sub fill_known_data
{
--
2.13.2
Bug#868977: Confirm that I'm able to verify the problem
Hi Yaroslav, On Thu, Jul 27, 2017 at 10:21:35AM -0400, Yaroslav Halchenko wrote: > > would need to dig in, may be later, meanwhile pushed my slight tune ups, feel > welcome to fix up. You do know where to get the .orig.tar.gz ;) Sure I know and I used it for building. What about simplifying things for your team mates and follow policy which does not require them downloading the source manually? :-P As I said, I would have added pristine-tar if this would not have messed up the repository for reasons I do not understand. It would be really cool if you would consider this for next version. Kind regards Andreas. -- http://fam-tille.de
Bug#862133: src:gnuradio: FTBFS with cppunit 1.14 (no C++11 support, required by cppunit)
Package: gnuradio
Version: 3.7.10.1-2
Followup-For: Bug #862133
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch
Hi Maitland,
While gnuradio currently configures itself to build under -std=c++98, it
appears that with the exception of one module, the code is compatible with
c++11 (builds and passes its build-time test suite). Attached is a patch
which switches the build to C++11 (with one module excepted) and lets
gnuradio build against current cppunit.
I know it's not a particularly pretty use of CMake (I'm not adept at CMake),
but this should unblock the cppunit transition.
I've uploaded gnuradio with this change to Ubuntu; please consider applying
the same, or something like it, in Debian. Or if you know of a reason that
this is a bad idea, let me know!
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gnuradio-3.7.10.1/debian/patches/series
gnuradio-3.7.10.1/debian/patches/series
--- gnuradio-3.7.10.1/debian/patches/series 2016-10-09 19:15:44.0
-0700
+++ gnuradio-3.7.10.1/debian/patches/series 2017-07-26 23:12:51.0
-0700
@@ -37,3 +37,4 @@
provide-example-grfreedv.grc-flowgraph
Convert-tabs-to-spaces
Get-the-FreeDV-demodulator-working
+use-cxx11
diff -Nru gnuradio-3.7.10.1/debian/patches/use-cxx11
gnuradio-3.7.10.1/debian/patches/use-cxx11
--- gnuradio-3.7.10.1/debian/patches/use-cxx11 1969-12-31 16:00:00.0
-0800
+++ gnuradio-3.7.10.1/debian/patches/use-cxx11 2017-07-26 23:14:12.0
-0700
@@ -0,0 +1,37 @@
+Description: use c++11 standard instead of c++98
+ cppunit now requires c++11, so use this for building.
+Author: Steve Langasek
+Bug-Debian: https://bugs.debian.org/862133
+
+Index: gnuradio-3.7.10.1/CMakeLists.txt
+===
+--- gnuradio-3.7.10.1.orig/CMakeLists.txt
gnuradio-3.7.10.1/CMakeLists.txt
+@@ -66,11 +66,11 @@
+ # set(CMAKE_CXX_STANDARD 98)
+
+ IF(CMAKE_CXX_COMPILER_ID STREQUAL "GNU")
+-SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++98")
++SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
+ ELSEIF(CMAKE_CXX_COMPILER_ID STREQUAL "Clang")
+-SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++98")
++SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
+ ELSEIF(CMAKE_CXX_COMPILER_ID STREQUAL "MSVC")
+-SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++98")
++SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
+ ELSE()
+ message(warning "C++ standard could not be set because compiler is not
GNU, Clang or MSVC.")
+ ENDIF()
+Index: gnuradio-3.7.10.1/gr-fec/CMakeLists.txt
+===
+--- gnuradio-3.7.10.1.orig/gr-fec/CMakeLists.txt
gnuradio-3.7.10.1/gr-fec/CMakeLists.txt
+@@ -46,6 +46,8 @@
+
+ SET(GR_PKG_FEC_EXAMPLES_DIR ${GR_PKG_DATA_DIR}/examples/fec)
+
++add_compile_options(-std=c++98)
++
+
+ # Begin conditional configuration
+
Processed: Re: Bug#868831: apport: CVE-2017-10708
Processing control commands: > tag -1 +pending Bug #868831 [src:apport] apport: CVE-2017-10708 Added tag(s) pending. -- 868831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868831: apport: CVE-2017-10708
Control: tag -1 +pending Thank you for the bug report. I just prepared an upload and it should clear the ftp archives soon. On Wed, 2017-07-19 at 06:26 +0200, Salvatore Bonaccorso wrote: > Source: apport > Version: 2.16.2-1 > Severity: grave > Tags: security upstream > Justification: user security hole > Forwarded: https://launchpad.net/bugs/1700573 > > Hi, > > the following vulnerability was published for apport. > > CVE-2017-10708[0]: > > An issue was discovered in Apport through 2.20.x. In > > apport/report.py, > > Apport sets the ExecutablePath field and it then uses the path to > > run > > package specific hooks without protecting against path traversal. > > This > > allows remote attackers to execute arbitrary code via a crafted > > .crash > > file. > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2017-10708 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10708 > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#868831: marked as done (apport: CVE-2017-10708)
Your message dated Thu, 27 Jul 2017 16:49:15 + with message-id and subject line Bug#868831: fixed in apport 2.20.4-2 has caused the Debian Bug report #868831, regarding apport: CVE-2017-10708 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.) -- 868831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apport Version: 2.16.2-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://launchpad.net/bugs/1700573 Hi, the following vulnerability was published for apport. CVE-2017-10708[0]: | An issue was discovered in Apport through 2.20.x. In apport/report.py, | Apport sets the ExecutablePath field and it then uses the path to run | package specific hooks without protecting against path traversal. This | allows remote attackers to execute arbitrary code via a crafted .crash | file. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-10708 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10708 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: apport Source-Version: 2.20.4-2 We believe that the bug you reported is fixed in the latest version of apport, 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 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ritesh Raj Sarraf (supplier of updated apport 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, 27 Jul 2017 21:31:12 +0530 Source: apport Binary: apport apport-notify python-problem-report python3-problem-report python-apport python3-apport apport-retrace apport-valgrind apport-gtk apport-kde dh-apport Architecture: source all amd64 Version: 2.20.4-2 Distribution: experimental Urgency: medium Maintainer: Ritesh Raj Sarraf Changed-By: Ritesh Raj Sarraf Description: apport - automatically generate crash reports for debugging apport-gtk - GTK+ frontend for the apport crash report system apport-kde - KDE frontend for the apport crash report system apport-notify - automatically generate crash reports for debugging apport-retrace - tools for reprocessing Apport crash reports apport-valgrind - valgrind wrapper that first downloads debug symbols dh-apport - debhelper extension for the apport crash report system python-apport - Python library for Apport crash report handling python-problem-report - Python library to handle problem reports python3-apport - Python 3 library for Apport crash report handling python3-problem-report - Python 3 library to handle problem reports Closes: 868831 Changes: apport (2.20.4-2) experimental; urgency=medium . * [4acc7ef] Refresh patches * [116a5d6] Fix security vulnerability in apport (CVE-2017-10708) (Closes: #868831) Checksums-Sha1: 71d3d98c010a87660419ce8b7ebfecdf65331129 3052 apport_2.20.4-2.dsc 3b7731bfed5f4803c080b09bd0ccc3a849446f6d 13580 apport_2.20.4-2.debian.tar.xz 7cecb0e6878f5c304e11e933798e55b21e25bca2 16268 apport-gtk_2.20.4-2_all.deb 0ef30e1284549c1a78cb94f053a0d941f79ce23c 25462 apport-kde_2.20.4-2_all.deb 4fde15f6cb98a858e7e92128b9e3029dc5422b8b 7080 apport-notify-dbgsym_2.20.4-2_amd64.deb 12fd39cc50fba47781dc7555fa5feb3135637733 8978 apport-notify_2.20.4-2_amd64.deb 1b75a69768238782189eb62233645fb64c992f27 16688 apport-retrace_2.20.4-2_all.deb dc7cdec1a642ff9807a3fafc677335dca97cdf55 9478 apport-valgrind_2.20.4-2_all.deb 96acac66abb77efacb718257684fac3d341bea93 336786 apport_2.20.4-2_all.deb 0927b6507aabfb069f768d2f72cfdb5428cc1293 18249 apport_2.20.4-2_amd64.buildinfo b03e632b00b9c236caa997fee7928dd6db4d0fab 9286 dh-apport_2.20.4-2_all.deb 4142e82b0213d959ac1735116bb78a2a349e31b2 83620 python-apport_2.20.4-2_all.deb aa9d63a1121eae718501edee9042f55c058a0833 12190 python-problem-report_2.20.4-2_all.deb 8295cad6b37d57a53dc83029f524eb62ca8e2ddf 83742 python3-apport_2.20.4-2_all.deb bd63f6f10133940025
Processed: [bts-link] source package src:resiprocate
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:resiprocate > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #869404 (http://bugs.debian.org/869404) > # Bug title: resiprocate: CVE-2017-11521: Adding too many media connections > may lead to memory exhaustion > # * https://github.com/resiprocate/resiprocate/pull/88 > # * remote status changed: (?) -> closed > # * closed upstream > tags 869404 + fixed-upstream Bug #869404 [src:resiprocate] resiprocate: CVE-2017-11521: Adding too many media connections may lead to memory exhaustion Added tag(s) fixed-upstream. > usertags 869404 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 869404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869929: partitionmanager depends and build-depends on cruft packages.
Package: partitionmanager Severity: serious Tags: buster sid Version: 3.0.1-1 Partitionmanager depends and build-depends on libkpmcore4 and libkpmcore4-dev respectively. These packages are no longer built by the kpmcore source package (they appear to have been replaced by libkpmcore5 and libkpmcore-dev).
Bug#867986: CVE-2016-10396
On Mon, Jul 10, 2017 at 11:18:35PM +0200, Moritz Muehlenhoff wrote: > > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10396 Hi Moritz. I assume your intent was not to issue a DSA for this since it's been a known issue for nearly a year. Under that assumption I've gone ahead with a package update targeting the next stable release update and am planning on updating oldstable as well. Apologies if I was incorrect in my assumption. noah signature.asc Description: PGP signature
Processed: [bts-link] source package src:imagemagick
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:imagemagick > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #869210 (http://bugs.debian.org/869210) > # Bug title: imagemagick: CVE-2017-11523: endless loop in ReadTXTImage > # * https://github.com/ImageMagick/ImageMagick/issues/591 > # * remote status changed: (?) -> closed > # * closed upstream > tags 869210 + fixed-upstream Bug #869210 [src:imagemagick] imagemagick: CVE-2017-11523: endless loop in ReadTXTImage Added tag(s) fixed-upstream. > usertags 869210 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 869210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package gdk-pixbuf
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gdk-pixbuf > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #858491 (http://bugs.debian.org/858491) > # Bug title: gdk-pixbuf: CVE-2017-6311: crash in gdk-pixbuf-thumbnailer > # * http://bugzilla.gnome.org/show_bug.cgi?id=778204 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 858491 + fixed-upstream Bug #858491 [libgdk-pixbuf2.0-bin] gdk-pixbuf: CVE-2017-6311: crash in gdk-pixbuf-thumbnailer Added tag(s) fixed-upstream. > usertags 858491 - status-NEW Usertags were: status-NEW. Usertags are now: . > usertags 858491 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 858491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869919: [DRE-maint] Bug#869919: remove ruby-berkshelf-api-client?
On 7/27/17, Pirate Praveen wrote: > Upstream readme has this "This gem has been fully deprecated, and its > API has been moved inside the berkshelf gem itself." > > I bumped into this package when trying to update ruby-faraday as its > gemspec declares a tight dependency on faraday ~> 0.9.1 > > Can we remove this package from debian? Yes we can but a bit later when I prepare an updated berkshelf, I'm working on its dependencies now.
Bug#867986: CVE-2016-10396
On Thu, Jul 27, 2017 at 10:35:36AM -0700, Noah Meyerhans wrote: > On Mon, Jul 10, 2017 at 11:18:35PM +0200, Moritz Muehlenhoff wrote: > > > > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10396 > > Hi Moritz. I assume your intent was not to issue a DSA for this since > it's been a known issue for nearly a year. Under that assumption I've > gone ahead with a package update targeting the next stable release > update and am planning on updating oldstable as well. Apologies if I was > incorrect in my assumption. Ack, that makes perfect sense. Cheers, Moritz
Bug#869608: marked as done (bareos-filedaemon: corrupts backups when signature=SHA1 in fileset)
Your message dated Thu, 27 Jul 2017 18:18:59 + with message-id and subject line Bug#869608: fixed in bareos 16.2.6-2 has caused the Debian Bug report #869608, regarding bareos-filedaemon: corrupts backups when signature=SHA1 in fileset 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.) -- 869608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bareos-filedaemon Version: 16.2.4-3 Severity: critical Justification: causes serious data loss to reproduce: 1) install bareos 16.2.4 client and server packages - all with defaults. 2) run a SelfTest backup of the client/server. 3) Restore a file from this backup - everything should be fine. 4) now change Signature = SHA1 in /etc/bareos/bareos-dir.d/fileset/SelfTest.conf 5) run another SelfTest Full backup 6) restore a file from this new backup The restored file is corrupted. I marked this critical because I upgraded a debian 8 client to debian 9 without any problems. Backups (bareos 15.2.2 Server) appeared to be running fine until I had to do a restore and ended up with broken files. Regards, Tom -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.10.17-1-pve (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de:en_US:en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages bareos-filedaemon depends on: ii adduser3.115 ii bareos-common 16.2.4-3 ii debconf [debconf-2.0] 1.5.61 ii init-system-helpers1.48 ii libacl12.2.52-3+b1 ii libc6 2.24-11+deb9u1 ii libcap21:2.25-1 ii libgcc11:6.3.0-18 ii libgnutls303.5.8-5+deb9u2 ii libjansson42.9-1 ii liblzo2-2 2.08-1.2+b2 ii libstdc++6 6.3.0-18 ii libwrap0 7.6.q-26 ii lsb-base 9.20161125 ii lsof 4.89+dfsg-0.1 ii zlib1g 1:1.2.8.dfsg-5 bareos-filedaemon recommends no packages. bareos-filedaemon suggests no packages. --- End Message --- --- Begin Message --- Source: bareos Source-Version: 16.2.6-2 We believe that the bug you reported is fixed in the latest version of bareos, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Geyer (supplier of updated bareos 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, 27 Jul 2017 19:50:17 +0200 Source: bareos Binary: bareos bareos-bconsole bareos-client bareos-common bareos-database-common bareos-database-postgresql bareos-database-mysql bareos-database-sqlite3 bareos-database-tools bareos-dbg bareos-devel bareos-director bareos-filedaemon bareos-storage bareos-storage-fifo bareos-storage-tape bareos-tools bareos-director-python-plugin bareos-filedaemon-ceph-plugin bareos-filedaemon-glusterfs-plugin bareos-filedaemon-python-plugin bareos-filedaemon-ldap-python-plugin bareos-storage-ceph bareos-storage-glusterfs bareos-storage-python-plugin bareos-traymonitor bareos-bat Architecture: source Version: 16.2.6-2 Distribution: unstable Urgency: medium Maintainer: Bareos Packaging Team Changed-By: Felix Geyer Description: bareos - Backup Archiving Recovery Open Sourced - metapackage bareos-bat - Backup Archiving Recovery Open Sourced - Bareos Admin Tool (BAT) bareos-bconsole - Backup Archiving Recovery Open Sourced - text console bareos-client - Backup Archiving Recovery Open Sourced - client metapackage bareos-common - Backup Archiving Recovery Open Sourced - common files bareos-database-common - Backup Archiving Recovery Open Sourced - common catalog files bareos-database-mysql - Backup Archiving Recovery Open Sourced - MySQL backend bareos-database-postgresql - Backup Archiving Recovery Open Sourced - PostgreSQL backend bareos-database-sqlite3 - Backup Archiving Recovery Open Sourced - SQLite backend bareos-datab
Bug#867362: isc-dchp-server: not starting after upgrade to stretch: more info
Hello all, I just had the same problem of DHCPD not starting after the stretch upgrade from jessie. Unfortunately the logs that the user gets shown by the upgrade process have an uncplete long line, otherwise the root cause would be obvious. When looking at /var/log/daemon.log here’s the error: Jul 27 20:18:21 hedwig isc-dhcp-server[17921]: Starting ISC DHCPv4 server: dhcpddhcpd service already running (pid file /var/run/dhcpd.pid currenty exists) ... failed! Hence, it seems the upgrade process leaves a dangling PID file around. Removing that PID file manually solved the problem for me. Thanks and cheers Mich - Michel Lanners | " Read Philosophy. Study Art. 23, Rue Paul Henkes|Ask Questions. Make Mistakes. L-1710 Luxembourg | email m...@lannersnet.lu | http://www.lannersnet.lu | Learn Always. "
Processed: found 869880 in 1.1.0~git20140921.1.440916e+dfsg1-4, tagging 869880
Processing commands for cont...@bugs.debian.org: > found 869880 1.1.0~git20140921.1.440916e+dfsg1-4 Bug #869880 [src:freerdp] CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839 Marked as found in versions freerdp/1.1.0~git20140921.1.440916e+dfsg1-4. > tags 869880 + upstream fixed-upstream Bug #869880 [src:freerdp] CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 869880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
On Thu 2017-07-27 16:21:21 +0200, Moritz Muehlenhoff wrote: > We can provide a fixed 1.9.8.1-1 via jessie-security/stretch-security, I've uploaded 1.9.8.1-1~deb8u1 for jessie-security and 1.9.8.1-1~deb9u1 for stretch-security, thanks! They're also available on the "jessie" and "stretch" branches at https://anonscm.debian.org/git/pkg-mozext/enigmail.git > but the current approach of providing Firefox/Thunderbird extensions in a > stable release is madness and really needs to stop for buster. Neither > the Firefox, Thunderbird maintainers or the security team can look after > all these extensions. I'm less concerned with "all these extensions" than i am with enigmail, which i think is an important one, until we manage to get it embedded in thunderbird directly :/ I understand that the release team has a larger scope, but dropping enigmail from debian stable would be a pretty bad outcome. >> I think this could have been avoided if the newer version of thunderbird >> had been marked as "Breaks: enigmail < 1.9.8" or something similar, >> though it's not clear how the t-bird maintainers are supposed to know >> that sort of information about every possible extension. Perhaps >> enigmail needs to be special cased since it seems to have more of a >> history of this kind of problem? > > Every maintainer of a Firefox/Thunderbird extension needs to test older > releases against the latest ESR once that reaches unstable. There's > an overlap of several months during which we provide the old ESR in > stable while the new ESR is available, this could've all been caught > before release time. i'm not sure which release time you're talking about. Thunderbird 52 has not been part of any release, afaict. i think it was pulled into jessie and stretch by way of security updates. We have known that thunderbird 52 is incompatible with prior versions of enigmail from earlier this year (~2 months ago, see the upstream bug report). We just failed to coordinate it properly for the security update of thunderbird in debian stable and oldstable. Sorry about that! At any rate, i think it's working now (modulo a follow up on Paul van der Vlis's experience of sending out cleartext mail as a separate issue, which i'm unable to reproduce). Please follow up if the updated packages haven't resolved your issues, Shevek. --dkg signature.asc Description: PGP signature
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later
On Thu 2017-07-27 17:23:25 +0200, Paul van der Vlis wrote: > On Thu, 27 Jul 2017 09:59:46 -0400 Daniel Kahn Gillmor > wrote: > >> I can confirm that enigmail 2:1.9.8.1-1 (from debian testing) installs >> successfully on jessie and that it appears to fix the underlying >> problem. > > My experience is different: it installs without a problem, it gives > warnings while decrypting. And it looks-like it encrypts, but it sent > plain text. yikes. this is a particularly scary failure mode, and i think it is distinct from the report here, which includes messages simply failing to send (esp. those with attachments) and some buttons or UI elements being unresponsive. Could you open this as a separate issue in the debian BTS? can you help me to reproduce the behavior you're describing? I haven't see that yet. > When I install it from Mozilla, it has the same problem on my machine, I > am now back to Thunderbird 45 as a work-arround, what works fine. glad there's a workaround, but it doesn't sound like something particularly sustainable long term. if you can help me replicate the "looks-encrypted-but-sends-in-the-clear" failure mode? --dkg
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
Hi Daniel On Thu, Jul 27, 2017 at 03:00:28PM -0400, Daniel Kahn Gillmor wrote: > On Thu 2017-07-27 16:21:21 +0200, Moritz Muehlenhoff wrote: > > We can provide a fixed 1.9.8.1-1 via jessie-security/stretch-security, > > I've uploaded 1.9.8.1-1~deb8u1 for jessie-security and 1.9.8.1-1~deb9u1 > for stretch-security, thanks! They're also available on the "jessie" > and "stretch" branches at > >https://anonscm.debian.org/git/pkg-mozext/enigmail.git Assuming Moritz's reply was an explicit ack to upload, I think the upload went to the wrong host ;-) It is now on ftp-master as enigmail | 2:1.9.8.1-1~deb9u1 | stable-new | source I do not see the jessie one yet there, but Jul 27 14:24:48 processing /enigmail_1.9.8.1-1~deb8u1_amd64.changes Jul 27 14:24:48 enigmail_1.9.8.1-1~deb8u1_amd64.changes processed successfully (uploader pkg-mozext-maintain...@lists.alioth.debian.org) [...] Jul 27 18:46:16 processing /enigmail_1.9.8.1-1~deb9u1_amd64.changes Jul 27 18:46:16 enigmail_1.9.8.1-1~deb9u1_amd64.changes processed successfully (uploader pkg-mozext-maintain...@lists.alioth.debian.org) OTOH I do not see any trace of it on security-master. Hope this helps, Regards, Salvatore
Bug#869774: thunderbird 52 needs enigmail 1.9.8 or later [was: Re: Bug#869774: Corrections - propably wrong cause]
On Thu 2017-07-27 21:41:18 +0200, Salvatore Bonaccorso wrote: > On Thu, Jul 27, 2017 at 03:00:28PM -0400, Daniel Kahn Gillmor wrote: >> On Thu 2017-07-27 16:21:21 +0200, Moritz Muehlenhoff wrote: >> > We can provide a fixed 1.9.8.1-1 via jessie-security/stretch-security, >> >> I've uploaded 1.9.8.1-1~deb8u1 for jessie-security and 1.9.8.1-1~deb9u1 >> for stretch-security, thanks! They're also available on the "jessie" >> and "stretch" branches at >> >>https://anonscm.debian.org/git/pkg-mozext/enigmail.git > > Assuming Moritz's reply was an explicit ack to upload, I think the > upload went to the wrong host ;-) It is now on ftp-master as dang, i thought that dupload would notice that the changelog suite is *-security and pick the right host for it. > enigmail | 2:1.9.8.1-1~deb9u1 | stable-new | source > > I do not see the jessie one yet there, This is apparently because source-only uploads aren't supported on jessie (no arch=all autobuilder). I've re-generated the upload and sent it to ftp.security.upload.debian.org instead. > but > > Jul 27 14:24:48 processing /enigmail_1.9.8.1-1~deb8u1_amd64.changes > Jul 27 14:24:48 enigmail_1.9.8.1-1~deb8u1_amd64.changes processed > successfully (uploader pkg-mozext-maintain...@lists.alioth.debian.org) > [...] > Jul 27 18:46:16 processing /enigmail_1.9.8.1-1~deb9u1_amd64.changes > Jul 27 18:46:16 enigmail_1.9.8.1-1~deb9u1_amd64.changes processed > successfully (uploader pkg-mozext-maintain...@lists.alioth.debian.org) > > OTOH I do not see any trace of it on security-master. and, i've gone ahead and re-uploaded the stretch version to ftp.security.upload.debian.org as well. hopefully i've got them all in the right place this time... --dkg
Bug#869934: cockpit: Incomplete debian/copyright?
Source: cockpit Version: 147-1 Severity: serious Justication: Policy 12.5 Hi, I just ACCEPTed cockpit from NEW but noticed it was missing attribution in debian/copyright for at least Nokia in mock-io-stream.c. (This is not exhaustive so please check over the entire package carefully and address these on your next upload.) I see there is some script to generate debian/copyright; perhaps it needs to be re-run, I'm not sure.. :) Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#869935: flightgear: FTBFS due to unit tests
Source: flightgear Version: 1:2017.2.1+dfsg-1 Severity: serious Tags: confirmed pending https://buildd.debian.org/status/package.php?p=flightgear&suite=sid The following tests FAILED: 1 - test_navs (Failed) 2 - test_flightplan (Failed) 4 - autosaveMigration (Failed) Looks like this is caused by running the tests in parallel. I'm working on a fix. Kind Regards Markus Wanner signature.asc Description: OpenPGP digital signature
Bug#869935: marked as done (flightgear: FTBFS due to unit tests)
Your message dated Thu, 27 Jul 2017 21:04:23 + with message-id and subject line Bug#869935: fixed in flightgear 1:2017.2.1+dfsg-3 has caused the Debian Bug report #869935, regarding flightgear: FTBFS due to unit tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 869935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flightgear Version: 1:2017.2.1+dfsg-1 Severity: serious Tags: confirmed pending https://buildd.debian.org/status/package.php?p=flightgear&suite=sid The following tests FAILED: 1 - test_navs (Failed) 2 - test_flightplan (Failed) 4 - autosaveMigration (Failed) Looks like this is caused by running the tests in parallel. I'm working on a fix. Kind Regards Markus Wanner signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: flightgear Source-Version: 1:2017.2.1+dfsg-3 We believe that the bug you reported is fixed in the latest version of flightgear, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Wanner (supplier of updated flightgear 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: Thu, 27 Jul 2017 22:02:00 +0200 Source: flightgear Binary: flightgear Architecture: source Version: 1:2017.2.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian FlightGear Crew Changed-By: Markus Wanner Description: flightgear - Flight Gear Flight Simulator Closes: 869935 Changes: flightgear (1:2017.2.1+dfsg-3) unstable; urgency=medium . * Fix a failure to build from source by de-parallelize unit test runs. Closes: #869935. Checksums-Sha1: ab5b09a39d4c6f99b53ace67e645728775b1875f 3427 flightgear_2017.2.1+dfsg-3.dsc 6ecc050e58bbb27d89359550820397b2beb82eb3 27372 flightgear_2017.2.1+dfsg-3.debian.tar.xz Checksums-Sha256: 4fca77e7e03d742e1d2807482c091a02f41383e940a60465f7ecd07064a919b5 3427 flightgear_2017.2.1+dfsg-3.dsc 3203326a9c88da226ab9fa8ea0005decf80d0e13ede37cd218e5dc0e4434e41e 27372 flightgear_2017.2.1+dfsg-3.debian.tar.xz Files: 12aec3ae143e6a0515ccfcb0b06e0dc7 3427 games extra flightgear_2017.2.1+dfsg-3.dsc 95e6335778190ef2c7d57abd3a93ca9a 27372 games extra flightgear_2017.2.1+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQQzBAEBCAAdFiEE7WdiNgeE4zHiUwPWAlr+layd8xsFAll6UfYACgkQAlr+layd 8xvP1B//WY4SD3zwlQbD4CjmDGT4uS59/tr0gO8ufvFS7k3FHTa6bl0vmMp+H0go I++RhmW2PgkOqgejCvQWdmr9q31wXPB5sr2r86xmGXGRaULMtj1s7kkwwf5lhXin 12jRKxqHDTRkVrjM0eaCx5tgdJ1JXMJwPejFiWb+40+aEAZA/EnUhNL0DEE4TCsZ D/kcrk/TsbXxMcAJVaEkyeAwuR8jDS+ReChkpmMPqrr27motdpW/eqDhLVD3+LgU UnpyqvtDCzmsuT+75T8i8YReYX8Zd1V69w9+qO/CxAAbk8oTE0Ty1hNgkfS6o6F3 SjHhFuIfDzpwMXCn0tTmp9DlUh91CSe9CR8NVwjbF3VYVkEi4Wrop8WtVbfghLHx DdOy0TdDRKlN0XtjlzHKbjWm/LMFr/ryV3LoJg5N4SkPHKkgIlHgmC2czhj3OWNk 6JWZqnDRSQ6ghwb6vDDRQJCyB/rTqz2bhtu8Azm54M4djDx3i+CIL6Umak/63BCm 3AUPi5zesbJMsl2yCBgxGUOV8fNcPAax85sTMQiecAEkTu8MDcfAebGs7tuQmrYS YdlsvdvBCVThxuAYo+BJyCQz0T4sSsLiF/36KHZwUF7HKXsJ0siT5HDARScA560t TIXMuAVLObkIvUiTgP6ewvLJP6/tPV9E1ANOyEzEXQP+H8nXkzfhT03E/Px5leMQ Xnu4f32Wn1stPGdoFDJYIwswZQyJwq+dhwLpiVznsn/Sxmj/CjhcIchx3E6OASkH dEOk+eto9M2wIDNxSdV+D8lNQ2epIjAzx/SVRCmWlkZRGSOjB62Q1QAuaM0IpXky nPYiWWnI5BdyyOLDcx9ucSldIfefKKv1fDloeCt46U/A7nfGAjoOYUcmGsGW8f4j kgFIKnRwqALrK5M5HIzOVo+JiM2lQt3uI5ajYD6mM8pxArbBauN5gJwBTcgyPHad Ny9PGM/ExVZgEdjqeQCJcMXQXmhTL934LRTLVvTNvG5IO3A+wcY9b+2ztTnoU+1K 8DOva8hrZWnb8LskIRqsmCW4rKpUwSFBVwrpG/o0dtt3wLBcFAvQ9P6cDC2ogs04 y5ywm0E7DHaMIpEutmLUYSeP4DAqkToe/3CY5VftXBedQMp38wrbN3pwyHE4nrGR /XS63Vy5JrOrdnhlcl52TS5Qc0bQCXyPX5ew/+43EgCqDNUh0Y4bUzsm9nD6CsHb SITCpGuSeq2S60l8PPLXxV21xpiPoIg8Yxhock21vJqUhWuove8S2H7oJn370KVf rBchMKuQNpohTpBOstGBFTEuMBJsXMRE3ZjwPA1u8s38vQ2iQ3qLogyAm4k82GD7 Gti9PevYm7UytvepriyDzd5ryp9a+g== =9UwN -END PGP SIGNATURE End Message ---
Processed: Reopen, to keep the bogus libgsl2 out of testing
Processing commands for cont...@bugs.debian.org:
> reopen 869778
Bug #869778 {Done: Dirk Eddelbuettel } [libgsl2] libgsl2:
soname change breaks dependencies
Bug #869779 {Done: Dirk Eddelbuettel } [libgsl2] bogofilter
dependencies on libgsl2
Bug #869781 {Done: Dirk Eddelbuettel } [libgsl2] libgsl2:
bumped library version without soname change, breaking reverse dependencies
Bug #869810 {Done: Dirk Eddelbuettel } [libgsl2] krita: Crash
on startup, missing libgsl.so.19
Bug reopened
Ignoring request to alter fixed versions of bug #869778 to the same values
previously set
Ignoring request to alter fixed versions of bug #869779 to the same values
previously set
Ignoring request to alter fixed versions of bug #869781 to the same values
previously set
Ignoring request to alter fixed versions of bug #869810 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
869778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869778
869779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869779
869781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869781
869810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#869880 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 869880 pending Bug #869880 [src:freerdp] CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 869880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869880: marked as pending
tag 869880 pending thanks Hello, Bug #869880 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-remote/freerdp.git/commit/?id=68c33ce --- commit 68c33cec893630a6b6abbce82956739854158dca Author: Bernhard Miklautz Date: Thu Jul 27 14:16:23 2017 +0200 add 0008-Fix-multiple-security-issues.patch This adds a fix for: * CVE-2017-2834 * CVE-2017-2835 * CVE-2017-2836 * CVE-2017-2837 * CVE-2017-2838 * CVE-2017-2839 Closes: #869880 diff --git a/debian/changelog b/debian/changelog index 6570976..f34579c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +freerdp (1.1.0~git20140921.1.440916e+dfsg1-14) UNRELEASED; urgency=high + + [ Bernhard Miklautz ] + * debian/patches + + Add fix for CVE-2017-2834, CVE-2017-2835, CVE-2017-2836, + CVE-2017-2837, CVE-2017-2838, CVE-2017-2839 (Closes: #869880) + + -- Bernhard Miklautz Thu, 27 Jul 2017 13:47:59 +0200 + freerdp (1.1.0~git20140921.1.440916e+dfsg1-13) unstable; urgency=medium [ James Clarke ]
Bug#869880: marked as done (CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839)
Your message dated Thu, 27 Jul 2017 22:04:47 + with message-id and subject line Bug#869880: fixed in freerdp 1.1.0~git20140921.1.440916e+dfsg1-14 has caused the Debian Bug report #869880, regarding CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839 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.) -- 869880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freerdp Severity: grave Tags: security Hi, please see: https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0341 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0340 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0339 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0338 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0337 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0336 Fix is here: https://github.com/FreeRDP/FreeRDP/pull/4055/commits/8292b4558f0684065ce1f58db7783cc426099223 Cheers, Moritz --- End Message --- --- Begin Message --- Source: freerdp Source-Version: 1.1.0~git20140921.1.440916e+dfsg1-14 We believe that the bug you reported is fixed in the latest version of freerdp, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated freerdp 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: Thu, 27 Jul 2017 23:03:30 +0200 Source: freerdp Binary: freerdp-x11 libfreerdp-cache1.1 libfreerdp-client1.1 libfreerdp-codec1.1 libfreerdp-common1.1.0 libfreerdp-core1.1 libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 libfreerdp-primitives1.1 libfreerdp-rail1.1 libfreerdp-utils1.1 libwinpr-asn1-0.1 libwinpr-bcrypt0.1 libwinpr-credentials0.1 libwinpr-credui0.1 libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 libwinpr-error0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 libwinpr-input0.1 libwinpr-interlocked0.1 libwinpr-io0.1 libwinpr-library0.1 libwinpr-path0.1 libwinpr-pipe0.1 libwinpr-pool0.1 libwinpr-registry0.1 libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-sspicli0.1 libwinpr-synch0.1 libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-timezone0.1 libwinpr-utils0.1 libwinpr-winhttp0.1 libwinpr-winsock0.1 libxfreerdp-client1.1 libfreerdp-plugins-standard libfreerdp-dev libwinpr-dev Architecture: source Version: 1.1.0~git20140921.1.440916e+dfsg1-14 Distribution: unstable Urgency: high Maintainer: Debian Remote Maintainers Changed-By: Mike Gabriel Description: freerdp-x11 - RDP client for Windows Terminal Services (X11 client) libfreerdp-cache1.1 - Free Remote Desktop Protocol library (cache library) libfreerdp-client1.1 - Free Remote Desktop Protocol library (client library) libfreerdp-codec1.1 - Free Remote Desktop Protocol library (codec library) libfreerdp-common1.1.0 - Free Remote Desktop Protocol library (common library) libfreerdp-core1.1 - Free Remote Desktop Protocol library (core library) libfreerdp-crypto1.1 - Free Remote Desktop Protocol library (freerdp-crypto library) libfreerdp-dev - Free Remote Desktop Protocol library (development files) libfreerdp-gdi1.1 - Free Remote Desktop Protocol library (GDI library) libfreerdp-locale1.1 - Free Remote Desktop Protocol library (locale library) libfreerdp-plugins-standard - RDP client for Windows Terminal Services (plugins) libfreerdp-primitives1.1 - Free Remote Desktop Protocol library (primitives library) libfreerdp-rail1.1 - Free Remote Desktop Protocol library (rail library) libfreerdp-utils1.1 - Free Remote Desktop Protocol library (freerdp-utils library) libwinpr-asn1-0.1 - Windows Portable Runtime library (ASN1 library) libwinpr-bcrypt0.1 - Windows Portable Runtime library (bcrypt library) libwinpr-credentials0.1 - Windows Portable Runtime library (credentials library) libwinpr-credui0.1 - Windows Portable Runtime library (credeui library) libwinpr-crt0.1 - Windows Portable Runtime library (crt library) libwinpr-c
Bug#869885: marked as done (lacme FTBFS with pandoc 1.19.1)
Your message dated Thu, 27 Jul 2017 22:49:14 + with message-id and subject line Bug#869885: fixed in lacme 0.4-1 has caused the Debian Bug report #869885, regarding lacme FTBFS with pandoc 1.19.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.) -- 869885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lacme Version: 0.3-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lacme.html ... dh_auto_build make -j1 make[1]: Entering directory '/build/1st/lacme-0.3' jq: error (at :1): Cannot index object with number pandoc: Error in $: not enough input CallStack (from HasCallStack): error, called at src/Text/Pandoc/Error.hs:55:28 in pandoc-1.19.1-Fq5EX61fpM1KVuqnJRnI0N:Text.Pandoc.Error Makefile:7: recipe for target 'lacme-accountd.1' failed make[1]: *** [lacme-accountd.1] Error 1 --- End Message --- --- Begin Message --- Source: lacme Source-Version: 0.4-1 We believe that the bug you reported is fixed in the latest version of lacme, 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 869...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated lacme 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, 28 Jul 2017 00:24:06 +0200 Source: lacme Binary: lacme lacme-accountd Architecture: source all Version: 0.4-1 Distribution: unstable Urgency: medium Maintainer: Guilhem Moulin Changed-By: Guilhem Moulin Description: lacme - ACME client written with process isolation and minimal privileges lacme-accountd - lacme account key manager Closes: 869885 Changes: lacme (0.4-1) unstable; urgency=medium . * Fix manpage generation with pandoc >=1.18. (Closes: #869885.) Checksums-Sha1: b2a95a07c1fcc29ff256d1f91ff2c9b172218c3d 1832 lacme_0.4-1.dsc 59484f6e91ac290a13b239dd85c7e34343dba412 45299 lacme_0.4.orig.tar.gz 940c497e4cec8d4e33ed6be009aa97de3b1e9f0e 3136 lacme_0.4-1.debian.tar.xz fbfdfc883df614846f9a8f6e8c6ad8c20bc99bcc 9902 lacme-accountd_0.4-1_all.deb d0e592300dc138643eba0b5c0d67a3d5dc7972d5 28874 lacme_0.4-1_all.deb 59ca4af9822d957af25b425a305c00d808cf6396 5717 lacme_0.4-1_amd64.buildinfo Checksums-Sha256: 4048aa0bb33d7a26e07268245e01a80c9c06c055038d95a8a5346489c9bf8ae9 1832 lacme_0.4-1.dsc 8dfed70da83702a09805ed8ca79d394709660b9961de763d415ea5e81f859958 45299 lacme_0.4.orig.tar.gz 634cd8abdc4cd543928a44266696bb17a16a58c921bc3340c1f5b4b8bf42e916 3136 lacme_0.4-1.debian.tar.xz b979add8df10846c700e2b67da1b934c9b96c74206d3a26afff9a3b4fb8c4efb 9902 lacme-accountd_0.4-1_all.deb d62683b7fcd093bc9ac3510a2f8379fb52689dab2e4b5900ad29260ac2730ecc 28874 lacme_0.4-1_all.deb c6711cfbb158aa3e4b0ad0dfa2f998b1b35d47e2d33bb7b1fed2f3787c7c4fdf 5717 lacme_0.4-1_amd64.buildinfo Files: 212cd5a0e949e5593b25c8b1765631b2 1832 utils optional lacme_0.4-1.dsc 863b81fe746afe27f52685938c797502 45299 utils optional lacme_0.4.orig.tar.gz 6eec5755f5b00fb224b3c50c2cbfb9a2 3136 utils optional lacme_0.4-1.debian.tar.xz 4fcd57edefaa16e88af3825eae2ed230 9902 utils optional lacme-accountd_0.4-1_all.deb 7a6f3a0bff94724da4abe402c342a518 28874 utils optional lacme_0.4-1_all.deb 3f7b29f9b494bf637be38fc6a7df56a1 5717 utils optional lacme_0.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAll6aqYACgkQ05pJnDwh pVI/sg/+J4EOs24n1OFauONdN8zRDKqlOMp6ycoRlP9FzyhbPGRn77Rgga/642wJ P50n+pkysVNOECAKb/aylhbMXgW2lzvYoMZ5KEQnwQd1UHPAicFHbvbeBH1PbqQh K3dGmtau2BipVFtsVCe48D4STvkyiiaikkMPOqBHkcr/rM65ss7ksHOvHaU8cWyR 8V4NmBfK3c2bWBlTA7pdNQ0NoQuxqIiJtHnUWtQVegWm8ryIg/0hYq9WYULIGsYM S6IGHSVsqu8hIivKRMDtig3xwL2kzx2aUjhwqJ4/R7ilfXNsRrHT6DIJbtaxYZXM I1iIKUP2q4i/wmooJ9+ep7PlIEYTtag22DvaAX6qbRzny4gvZ3dY5KK8aUw5EVvG l85R4OzZ959mbzl2l5FhwARYUR7Pq2YtA3T0F54u6oqFtImIvFKo+cxzKh5XBJU8 q1OMgzGuJ6AYIRDKiOKxGlKJHVJMkuXoe5NRZ1K3dUA1TKii+Uf6JjA3EIAK62Ps OfT9nW8dM/saYaRyFX1eHHoAH6SwgMHmtl4X0IUzTXmOxoB5SyvK8uJSGswODmS0 uuNleGaD6c3rFNMJcBs4hUabTJyUAUktqRHTwlCgzgdLjZeqGtOkuDskesXdGvxr ubLXxj30jhliTgjg+heWt6Any95SMJgd/fhoHr2VJoRdAQFNISA= =qfFb -END PGP SIG
Bug#839788: marked as done (trackballs: unable to play the game because it segfaults)
Your message dated Thu, 27 Jul 2017 23:50:08 + with message-id and subject line Bug#839788: fixed in trackballs 1.2.3-1 has caused the Debian Bug report #839788, regarding trackballs: unable to play the game because it segfaults 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.) -- 839788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trackballs Version: 1.1.4-4.2 Severity: grave Tags: help Dear maintainer, while I was preparing an NMU to fix #831119 and other bugs, I discovered that the game is unplayable because it segfaults as soon as I try to start a new game. This issue might be related to #306998. I can't get a full backtrace but gdb indicates that the issue is also related to guile-2.0. Maybe the 0003-Port-to-Guile-2.0.patch is incomplete. I don't think this game should be released with Stretch unless some is able to fix this bug. Regards, Markus -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect --- End Message --- --- Begin Message --- Source: trackballs Source-Version: 1.2.3-1 We believe that the bug you reported is fixed in the latest version of trackballs, 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 839...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated trackballs 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, 28 Jul 2017 00:11:52 +0200 Source: trackballs Binary: trackballs trackballs-data Architecture: source Version: 1.2.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Description: trackballs - OpenGL-based game of steering a marble through a labyrinth trackballs-data - Data files for trackballs Closes: 306998 621709 672946 839788 868983 Changes: trackballs (1.2.3-1) unstable; urgency=medium . * New maintainer: Debian Games Team with the consent of Ari Pollak. Add myself to Uploaders. * New upstream version 1.2.3. (Closes: #868983) - Fixes segmentation faults. The game is usable again. (Closes: #839788) - The game uses SDL2 now which provides much better fullscreen support and switching to different resolutions should not crash the X server anymore. (Closes: #306998) - We build-depend on zlib1g-dev now. (Closes: #672946) - The Slovak PO file declares and uses UTF-8 now. (Closes: #621709) * Switch to compat level 10. * wrap-and-sort -sa. * Declare compliance with Debian Policy 4.0.0. * Homepage field: Point to the new fork of trackballs at github.com. * Move the package to Git. * Drop deprecated menu file and xpm icon. * Switch from SDL1 to SDL2. New build-dependencies zlib1g-dev, gettext. New build system CMake. * Drop all patches. No longer needed. * Clean up debian/rules. Add get-orig-source target. * Don't recommend trackballs-music anymore because the music files are included now. * Remove the paragraph of the package description that mentions the obsolete trackballs-music package. * Drop postrm file. * Add Breaks and Replaces relation for trackballs-music. * Update debian/copyright to copyright format 1.0. * Add manpage.patch and fix some spelling mistakes and the Lintian warning bad whatis entry. * trackballs-data: Depend on fonts-freefont-ttf and symlink the font file to Debian's system package. * Add no-execstring.patch and remove the unnecessary Exec string from trackballs.desktop. Checksums-Sha1: 181d437735a1c616e1a6791e99e1c81353cbb517 2254 trackballs_1.2.3-1.dsc a35288c9ea52bc4934b1a7045edfadbb07fc0c99 33168935 trackballs_1.2.3.orig.tar.gz eeb17d086102c10a9b61139b0bf67d7af0cbdae3 9924 trackballs_1.2.3-1.debian.tar.xz 1b40feff1f39f157a966f847334888dd5d044060 12383 trackballs_1.2.3-1_amd64.buil
Bug#866627: marked as done (libwebp-dev: depends on libwebpdemux3, but src builds libwebpdemux2)
Your message dated Thu, 27 Jul 2017 17:15:22 -0700 with message-id and subject line libwebp-dev: depends on libwebpdemux3, but src builds libwebpdemux2 has caused the Debian Bug report #866627, regarding libwebp-dev: depends on libwebpdemux3, but src builds libwebpdemux2 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.) -- 866627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwebp-dev Version: 0.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is not installable in experimental: The following packages have unmet dependencies: libwebp-dev : Depends: libwebpdemux3 (= 0.6.0-1) but it is not installable Cheers, Andreas --- End Message --- --- Begin Message --- Fixed in 0.6.0-2 in experimental, and 0.6.0-3 in unstable. --- End Message ---
Bug#869856: [Pkg-openssl-devel] Bug#869856: openssl: FTBFS: Testsuite failures
On Thu, Jul 27, 2017 at 9:05 AM, Kurt Roeckx wrote: > Does the attached patch fix it? It appears so. (Though I did have to apply it by hand as there was no "clientsession" line for patch to sync to in hunk #2.) -- Daniel Schepler
Bug#869884: chemical-mime-data: Local copy of intltool-* fails with perl 5.26
Control: tag -1 + patch
On Thu, 27 Jul 2017 14:37:40 +0300, Adrian Bunk wrote:
> Making check in po
> make[2]: Entering directory '/build/1st/chemical-mime-data-0.1.94/po'
> INTLTOOL_EXTRACT=../intltool-extract srcdir=. ../intltool-update
> --gettext-package chemical-mime-data --pot
> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
> m/^(.*)\${ <-- HERE ?([A-Z_]+)}?(.*)$/ at ../intltool-update line 875.
> Makefile:95: recipe for target 'chemical-mime-data.pot' failed
> make[2]: *** [chemical-mime-data.pot] Error 2
Here's a debdiff with a new patch which fixes the embedded
intltool-update.
Cheers,
gregor
--
.''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`-
signature.asc
Description: Digital Signature
Processed: Re: Bug#869884: chemical-mime-data: Local copy of intltool-* fails with perl 5.26
Processing control commands: > tag -1 + patch Bug #869884 [src:chemical-mime-data] chemical-mime-data: Local copy of intltool-* fails with perl 5.26 Added tag(s) patch. -- 869884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867990: python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory
Package: src:python-pika Followup-For: Bug #867990 The file now appears to be called version_history.rst.txt This is presumably a change of behaviour between Sphinx 1.4.9 and 1.5.6? Christopher
Bug#867990: marked as pending
tag 867990 pending thanks Hello, Bug #867990 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/python-modules/packages/python-pika.git/commit/?id=86fadb7 --- commit 86fadb7bd9e99f72b458585f773197e28efce8ce Author: Christopher Hoskin Date: Fri Jul 28 04:26:32 2017 +0100 Fix "python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory" filename now version_history.rst.txt (Closes: #867990) diff --git a/debian/changelog b/debian/changelog index fb9571f..4c08168 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +python-pika (0.10.0-3) UNRELEASED; urgency=medium + + * Team upload. + * Fix "python-pika FTBFS: rm: cannot remove version_history.txt: No +such file or directory" filename now version_history.rst.txt (Closes: +#867990) + + -- Christopher Hoskin Fri, 28 Jul 2017 04:19:38 +0100 + python-pika (0.10.0-2) UNRELEASED; urgency=medium * Fixed VCS URL (https)
Processed: Bug#867990 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 867990 pending Bug #867990 [src:python-pika] python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867990: marked as done (python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory)
Your message dated Fri, 28 Jul 2017 04:19:06 + with message-id and subject line Bug#867990: fixed in python-pika 0.10.0-3 has caused the Debian Bug report #867990, regarding python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 867990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pika Version: 0.10.0-1 Severity: serious Tags: buster sid Some recent change in usntable makes python-pika FTBFS: https://tests.reproducible-builds.org/debian/history/python-pika.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pika.html ... debian/rules override_dh_installchangelogs make[1]: Entering directory '/build/1st/python-pika-0.10.0' dh_installchangelogs docs/version_history.rst make[1]: Leaving directory '/build/1st/python-pika-0.10.0' dh_installexamples -O--buildsystem=pybuild dh_python2 -O--buildsystem=pybuild dh_python3 -O--buildsystem=pybuild dh_perl -O--buildsystem=pybuild debian/rules override_dh_link make[1]: Entering directory '/build/1st/python-pika-0.10.0' rm /build/1st/python-pika-0.10.0/debian/python-pika-doc/usr/share/doc/python-pika-doc/html/_sources/version_history.txt rm: cannot remove '/build/1st/python-pika-0.10.0/debian/python-pika-doc/usr/share/doc/python-pika-doc/html/_sources/version_history.txt': No such file or directory debian/rules:25: recipe for target 'override_dh_link' failed make[1]: *** [override_dh_link] Error 1 --- End Message --- --- Begin Message --- Source: python-pika Source-Version: 0.10.0-3 We believe that the bug you reported is fixed in the latest version of python-pika, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 867...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Hoskin (supplier of updated python-pika 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, 28 Jul 2017 04:48:19 +0100 Source: python-pika Binary: python-pika python3-pika python-pika-doc Architecture: source Version: 0.10.0-3 Distribution: unstable Urgency: medium Maintainer: Jan Dittberner Changed-By: Christopher Hoskin Description: python-pika - AMQP client library for Python 2 python-pika-doc - AMQP client library documentation python3-pika - AMQP client library for Python 3 Closes: 867990 Changes: python-pika (0.10.0-3) unstable; urgency=medium . * Team upload. * Fix "python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory" filename now version_history.rst.txt (Closes: #867990) * Fix spelling in debian/python-pika-doc.doc-base * Add autopkgtests * Bump standards version from 3.9.6 to 4.0.0 (no change required) Checksums-Sha1: c0df6fad8e00d0464f11e785bb3a9bcfdaaf0beb 2413 python-pika_0.10.0-3.dsc 21964a3e93b44213f9a1994f5fadcb542eefe4ce 9348 python-pika_0.10.0-3.debian.tar.xz c250a64e5e8f543b8318349d3db03fa6a13aab59 8692 python-pika_0.10.0-3_amd64.buildinfo Checksums-Sha256: 8665cdd44acbb36ceee990d12791d26d83a95b96fe8f8102ee373b24c475cb35 2413 python-pika_0.10.0-3.dsc f27cba630dcbd3a8263b505fff564fd85b169d70882cc2608557fcea74604069 9348 python-pika_0.10.0-3.debian.tar.xz 427a51427a5188373b2243a09a4e302a4f325b11b74ae43707e1dde573ace369 8692 python-pika_0.10.0-3_amd64.buildinfo Files: c89f07a8f36da6187d477f334822fde2 2413 python optional python-pika_0.10.0-3.dsc f901c3ae576a328eabba12723f59564f 9348 python optional python-pika_0.10.0-3.debian.tar.xz 69fbfafaf21357aaedb84cfb51f0e4e1 8692 python optional python-pika_0.10.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAll6tUEACgkQf6qUsnUU SpqZug//fusRd/1Vig6Pf92xt62qjmoSE5J6RVeXVwpOgQjgVw2Sq6wjlE+ALSqL CrYgevOnvkzNjpgumUNxziBX/vTwY4p9caj1lMZ0q+b3Yqp2OVM8/FK6ebm/1Hgh xd2TwZZ6/Hl1P6nOnjthfODR7ymnifufA3E/2hpXKbnXo8sx97hFalaJrAg/Cgah twENqL86FPvCzA9U9SCQl45H8xajvxcgMcvC15g24v+8u8j9s0YTmp1SXuVSVE2K IpGIAEhJYOuf8JHfqGGrFYoEaEv0fzLiJ37K1GSg4AQ7ZygS2GKJ34gfCVU0a0gq co5j2Fa7TWy4cOd15VqjpC17JmvCnwNabGr4rhN4/edly1
Bug#869934: cockpit: Incomplete debian/copyright?
Control: found -1 146-1 Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/7397 Hello Chris, Chris Lamb [2017-07-27 21:11 +0100]: > I just ACCEPTed cockpit from NEW but noticed it was missing > attribution in debian/copyright for at least Nokia in mock-io-stream.c. Thanks for spotting! > (This is not exhaustive so please check over the entire package > carefully and address these on your next upload.) I went over the source again with a reasonably fine comb: git grep -i copyright | grep -Ev 'COPYING:|Red Hat' and spotted mock-io-stream.c and a few others. PR sent (see above). > I see there is some script to generate debian/copyright; perhaps it needs > to be re-run, I'm not sure.. :) That's only for the bundled JavaScript modules. It does get run with each upstream PR and release, and as soon as an upstream PR changes the included modules in a way that breaks automatic license detection it will fail CI, so I'm reasonably sure on that part. But this doesn't cover the C code in src/. Thanks, Martin
Processed: Re: Bug#869934: cockpit: Incomplete debian/copyright?
Processing control commands: > found -1 146-1 Bug #869934 [src:cockpit] cockpit: Incomplete debian/copyright? Marked as found in versions cockpit/146-1. > forwarded -1 https://github.com/cockpit-project/cockpit/pull/7397 Bug #869934 [src:cockpit] cockpit: Incomplete debian/copyright? Set Bug forwarded-to-address to 'https://github.com/cockpit-project/cockpit/pull/7397'. -- 869934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868652: marked as done (ros-vcstools FTBFS: CalledProcessError: Command 'git commit -m initial' returned non-zero exit status 128)
Your message dated Fri, 28 Jul 2017 06:20:39 +
with message-id
and subject line Bug#868652: fixed in ros-vcstools 0.1.39-5
has caused the Debian Bug report #868652,
regarding ros-vcstools FTBFS: CalledProcessError: Command 'git commit -m
initial' returned non-zero exit status 128
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.)
--
868652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-vcstools
Version: 0.1.39-3
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ros-vcstools.html
...
Checked out revision 1.
..
==
ERROR: test suite for
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in
setupContext
try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
File
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py",
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True,
cwd=self.remote_path)
File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git commit -m initial' returned non-zero exit
status 128
==
ERROR: test suite for
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in
setupContext
try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
File
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py",
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True,
cwd=self.remote_path)
File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git commit -m initial' returned non-zero exit
status 128
==
ERROR: test suite for
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in
setupContext
try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
File
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py",
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True,
cwd=self.remote_path)
File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git commit -m initial' returned non-zero exit
status 128
==
ERROR: test suite for
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in
setupContext
try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
File
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py",
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True,
cwd=self.remote_path)
File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessEr
Bug#865814: python-tablib needs new maintainer
To support the new upstream python-django-tables2 it would seem that python-tablib needs a new maintainer as the package is no longer used by the current openstack team. So #865855 is unlikely to be fixed. Would someone from the Debian Python Modules Team like to take over maintenance of python-tablib rather than me doing an NMU to keep django-tables in testing? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865855#19 -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpMK3WqSf8rE.pgp Description: OpenPGP digital signature
