Processed: [bts-link] source package src:libstatgen
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libstatgen > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #905368 (http://bugs.debian.org/905368) > # Bug title: libstatgen: FTBFS in sid > # * https://github.com/statgen/libStatGen/issues/19 > # * remote status changed: open -> closed > # * closed upstream > tags 905368 + fixed-upstream Bug #905368 [src:libstatgen] libstatgen: FTBFS in sid Warning: Unknown package 'src:libstatgen' Added tag(s) fixed-upstream. Warning: Unknown package 'src:libstatgen' > usertags 905368 - status-open Usertags were: status-open. Usertags are now: . > usertags 905368 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 905368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:khal
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:khal > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #908497 (http://bugs.debian.org/908497) > # Bug title: khal FTBFS with python-dateutil 2.7.3-1 > # * https://github.com/pimutils/khal/issues/780 > # * remote status changed: open -> closed > # * closed upstream > tags 908497 + fixed-upstream Bug #908497 [src:khal] khal FTBFS with python-dateutil 2.7.3-1 Added tag(s) fixed-upstream. > usertags 908497 - status-open Usertags were: status-open. Usertags are now: . > usertags 908497 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 908497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ruby-sentry-raven
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-sentry-raven > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #908258 (http://bugs.debian.org/908258) > # Bug title: ruby-sentry-raven: FTBFS with ruby-rspec 3.8 > # * https://github.com/getsentry/raven-ruby/issues/865 > # * remote status changed: open -> closed > # * closed upstream > tags 908258 + fixed-upstream Bug #908258 [src:ruby-sentry-raven] ruby-sentry-raven: FTBFS with ruby-rspec 3.8 Added tag(s) fixed-upstream. > usertags 908258 - status-open Usertags were: status-open. Usertags are now: . > usertags 908258 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 908258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891107: marked as done (geneagrapher: python-beautifulsoup is replaced with python-bs4)
Your message dated Thu, 20 Sep 2018 21:19:47 + with message-id and subject line Bug#891107: fixed in geneagrapher 1.0c2+git20180919-1 has caused the Debian Bug report #891107, regarding geneagrapher: python-beautifulsoup is replaced with python-bs4 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.) -- 891107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: geneagrapher Version: 1.0c2+git20120704-2 Severity: important Control: block 891087 by -1 beautifulsoup version 4 was replaced as a new package, bs4, which has been in Debian for over 5 years now. beautfiulsoup (3.x) hasn't seen any maintenance since then. It's high time to remove it from the archive. Most code written against Beautiful Soup 3 will work against Beautiful Soup 4 with one simple change. All you should have to do is change the package name from BeautifulSoup to bs4, and depend on python-bs4 instead of python-beautifulsoup. There is some documentation on the migration here: https://www.crummy.com/software/BeautifulSoup/bs4/doc/#porting-code-to-bs4 Thanks, SR --- End Message --- --- Begin Message --- Source: geneagrapher Source-Version: 1.0c2+git20180919-1 We believe that the bug you reported is fixed in the latest version of geneagrapher, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated geneagrapher 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 Sep 2018 16:47:01 -0400 Source: geneagrapher Binary: geneagrapher Architecture: source Version: 1.0c2+git20180919-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Doug Torrance Description: geneagrapher - Create tree from Mathematics Genealogy Project Closes: 891107 Changes: geneagrapher (1.0c2+git20180919-1) unstable; urgency=medium . * New upstream release (git snapshot). - Port to Beautiful Soup 4 (Closes: #891107). * debian/clean - Remove distribute files, as distribute is no longer used. - Update path to egg files. * debian/compat - Bump debhelper compatibility level to 11. * debian/control - Add dh-python, python-bs4, and python-lxml to Build-Depends. - Bump versioned dependency on debhelper to >= 11. - Bump Standards-Version to 4.2.1. - Update Homepage. - Update Vcs-* after move to Salsa. - Add DEP-8 testsuite. * debian/copyright - Use https in Format. - Remove entries for the now-deleted file bootstrap.py and the corresponding ZPL-2.1 license. * debian/docs - README.rst was renamed to README.md. * debian/patches/dont_download_distribute.patch - Remove patch; distribute is no longer used during build. * debian/patches/include-test-data.patch - New patch; include test data files. * debian/patches/skip-network-tests.patch - New patch; skip all tests requiring network connection. * debian/rules - Use pybuild. - Remove get-orig-source target. * debian/upstream/metadata - Add DEP-12 upstream metadata file. * debian/watch - Bump to uscan v4. - Use git mode to generate version number. In particular, we use 1.0c2+git%cd, as upstream has not released a new version since 1.0c2, but has been pushing new commits to git. Checksums-Sha1: 93c774eecc60497c14ecb665354cbbc45fb00856 2177 geneagrapher_1.0c2+git20180919-1.dsc f363e2d524ae5baa76d03b949be88482766d394e 211400 geneagrapher_1.0c2+git20180919.orig.tar.xz a9fd1455642411d638dd6e73bf242b2bbd2ac505 4728 geneagrapher_1.0c2+git20180919-1.debian.tar.xz Checksums-Sha256: 6ec842c208d094d5db42f87d0793db7bd1dbbf4d17d27e604a3acd67950a0ed2 2177 geneagrapher_1.0c2+git20180919-1.dsc a0834618afbade1d632175f133fe78cd334d80b3042039e2eb3ccff5112c69c8 211400 geneagrapher_1.0c2+git20180919.orig.tar.xz 9d172ce0896620907067e48488e460fa032000b464fe2d7d2f4446acbcebb26d 4728 geneagrapher_1.0c2+git20180919-1.debian.tar.xz Files: 1f5712876ef2c253632415bd3e5d4960 2177 math
Processed: Fix found version and mark as not in stretch
Processing commands for cont...@bugs.debian.org: > notfound 909244 0.5.1-9 Bug #909244 [kobodeluxe] kobodeluxe not playable - immediately pauses and can't be resumed There is no source info for the package 'kobodeluxe' at version '0.5.1-9' with architecture '' Unable to make a source version for version '0.5.1-9' No longer marked as found in versions 0.5.1-9. > found 909244 0.5.1-8 Bug #909244 [kobodeluxe] kobodeluxe not playable - immediately pauses and can't be resumed Marked as found in versions kobodeluxe/0.5.1-8. > tags 909244 buster sid Bug #909244 [kobodeluxe] kobodeluxe not playable - immediately pauses and can't be resumed Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 909244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 909215 in 3.8.8-1
Processing commands for cont...@bugs.debian.org:
> found 909215 3.8.8-1
Bug #909215 {Done: Patrick Matthäi } [glusterfs]
glusterfs: Multiple security issues
There is no source info for the package 'glusterfs' at version '3.8.8-1' with
architecture ''
Unable to make a source version for version '3.8.8-1'
Marked as found in versions 3.8.8-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
909215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#905368: marked as done (libstatgen: FTBFS in sid)
Your message dated Thu, 20 Sep 2018 19:35:02 + with message-id and subject line Bug#905368: fixed in libstatgen 1.0.14-2 has caused the Debian Bug report #905368, regarding libstatgen: FTBFS in sid 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.) -- 905368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libstatgen Version: 1.0.14-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build make -j1 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>' make[3]: Entering directory '/<>/samtools' ln -s ../samtools/bgzf.h ../include/bgzf.h ln -s ../samtools/knetfile.h ../include/knetfile.h ln -s ../samtools/khash.h ../include/khash.h [... snipped ...] ln -s ../general/SmithWaterman.h ../include/SmithWaterman.h ln -s ../general/Sort.h ../include/Sort.h ln -s ../general/STLUtilities.h ../include/STLUtilities.h ln -s ../general/StatGenStatus.h ../include/StatGenStatus.h ln -s ../general/StringAlias.h ../include/StringAlias.h ln -s ../general/StringArray.h ../include/StringArray.h ln -s ../general/StringBasics.h ../include/StringBasics.h ln -s ../general/StringHash.h ../include/StringHash.h ln -s ../general/StringMap.h ../include/StringMap.h ln -s ../general/Tabix.h ../include/Tabix.h ln -s ../general/UncompressedFileType.h ../include/UncompressedFileType.h ln -s ../general/Constant.h ../include/Constant.h ln -s ../general/CSG_MD5.h ../include/CSG_MD5.h ln -s ../general/Generic.h ../include/Generic.h ln -s ../general/GenomeSequenceHelpers.h ../include/GenomeSequenceHelpers.h ln -s ../general/GreedyTupleAligner.h ../include/GreedyTupleAligner.h ln -s ../general/InplaceMerge.h ../include/InplaceMerge.h ln -s ../general/LongHash.h ../include/LongHash.h ln -s ../general/LongInt.h ../include/LongInt.h ln -s ../general/MathConstant.h ../include/MathConstant.h ln -s ../general/PackedVector.h ../include/PackedVector.h ln -s ../general/PedigreeAlleles.h ../include/PedigreeAlleles.h ln -s ../general/Performance.h ../include/Performance.h ln -s ../general/ReusableVector.h ../include/ReusableVector.h ln -s ../general/SimpleStats.h ../include/SimpleStats.h ln -s ../general/TrimSequence.h ../include/TrimSequence.h ln -s ../general/UnitTest.h ../include/UnitTest.h g++ -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation -Wno-strict-overflow -I../include -I. -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o obj/BaseAsciiMap.o -c BaseAsciiMap.cpp -DVERSION="\"1.0.0\"" g++ -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation -Wno-strict-overflow -I../include -I. -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o obj/BaseQualityHelper.o -c BaseQualityHelper.cpp -DVERSION="\"1.0.0\"" g++ -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation -Wno-strict-overflow -I../include -I. -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o obj/BaseUtilities.o -c BaseUtilities.cpp -DVERSION="\"1.0.0\"" g++ -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation -Wno-strict-overflow -I../include -I. -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o obj/BasicHash.o -c BasicHash.cpp -DVERSION="\"1.0.0\"" g++ -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation -Wno-strict-overflow -I../include -I. -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o obj/BgzfFileType.o -c BgzfFileType.cpp -DVERSION="\"1.0.0\"" g++ -O4 -fPIC -pipe -Wall
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > severity 891551 serious Bug #891551 [src:faketime] faketime: FTBFS with GCC 8 - error: 'strncpy' specified bound 256 equals destination size Severity set to 'serious' from 'important' > forcemerge 891551 897747 Bug #891551 [src:faketime] faketime: FTBFS with GCC 8 - error: 'strncpy' specified bound 256 equals destination size Bug #897747 [src:faketime] faketime: ftbfs with GCC-8 Changed Bug forwarded-to-address to 'https://github.com/wolfcw/libfaketime/issues/150' from 'https://github.com/wolfcw/libfaketime/pull/161'. Marked as found in versions faketime/0.9.7-1. Bug #891551 [src:faketime] faketime: FTBFS with GCC 8 - error: 'strncpy' specified bound 256 equals destination size Marked as found in versions faketime/0.9.7-2. Added tag(s) sid and buster. Merged 891551 897747 > thanks Stopping processing here. Please contact me if you need assistance. -- 891551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891551 897747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909155: marked as done (apt-cache show multiple packages produces invalid output)
Your message dated Thu, 20 Sep 2018 19:19:14 + with message-id and subject line Bug#909155: fixed in apt 1.7.0~rc2 has caused the Debian Bug report #909155, regarding apt-cache show multiple packages produces invalid output 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.) -- 909155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 1.7.0~rc1 Severity: serious File: /usr/bin/apt-cache If you do a fresh sid debootstrap and then you can get the following interaction: $ apt-cache show gcc-8-base=installed libgcc1=installed Package: gcc-8-base Source: gcc-8 Version: 8.2.0-7 Installed-Size: 244 Maintainer: Debian GCC Maintainers Architecture: amd64 Breaks: gcc-4.4-base (<< 4.4.7), gcc-4.7-base (<< 4.7.3), gcj-4.4-base (<< 4.4.6-9~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.4-base (<< 4.4.6-3~), gnat-4.6 (<< 4.6.1-5~) Description: GCC, the GNU Compiler Collection (base package) Description-md5: b6e93638a6d08ea7a18929d7cf078e5d Multi-Arch: same Homepage: http://gcc.gnu.org/ Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/g/gcc-8/gcc-8-base_8.2.0-7_amd64.deb Size: 187052 MD5sum: 5ae3d2f575c9924ae67fa8dcc4af1e21 SHA256: 9e3dcd13005ccadbb57a8f117cde66aec8b8b8a21492e3aa02d6f54c1288bfb4 Package: libgcc1 Source: gcc-8 (8.2.0-7) Version: 1:8.2.0-7 Installed-Size: 116 Maintainer: Debian GCC Maintainers Architecture: amd64 Depends: gcc-8-base (= 8.2.0-7), libc6 (>= 2.14) Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2) Description: GCC support library Description-md5: bbd60d723e97d8e06c04228ee4c76f10 Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/g/gcc-8/libx32gomp1_8.2.0-7_amd64.deb Size: 77204 MD5sum: 61275848d23df37f647cb6a9b21f4135 SHA256: b8c56221460897e2640baf7bd6e1a9f645346d4178265508a18d48bf8c68e752 Package: libx32gomp1-dbg Source: gcc-8 Version: 8.2.0-7 Installed-Size: 346 Maintainer: Debian GCC Maintainers --- End Message --- --- Begin Message --- Source: apt Source-Version: 1.7.0~rc2 We believe that the bug you reported is fixed in the latest version of apt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Andres Klode (supplier of updated apt 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, 20 Sep 2018 21:03:54 +0200 Source: apt Binary: apt libapt-pkg5.0 libapt-inst2.0 apt-doc libapt-pkg-dev libapt-pkg-doc apt-utils apt-transport-https Architecture: source Version: 1.7.0~rc2 Distribution: unstable Urgency: medium Maintainer: APT Development Team Changed-By: Julian Andres Klode Description: apt- commandline package manager apt-doc- documentation for APT apt-transport-https - transitional package for https support apt-utils - package management related utility programs libapt-inst2.0 - deb package format runtime library libapt-pkg-dev - development files for APT's libapt-pkg and libapt-inst libapt-pkg-doc - documentation for APT development libapt-pkg5.0 - package management runtime library Closes: 909155 Changes: apt (1.7.0~rc2) unstable; urgency=medium . [ David Kalnischkies ] * Deal with descriptions embedded in displayed record correctly (Closes: #909155) Checksums-Sha1: 1021f1844ab96eac4b78c2745a8ee6b0259209a2 2775 apt_1.7.0~rc2.dsc f2df18cf217657f13abb1472e81474260d5f2d62 2150680 apt_1.7.0~rc2.tar.xz 740b15ea9f94e600bd0fff4130c508ebf4951676 7414 apt_1.7.0~rc2_source.buildinfo Checksums-Sha256: 7cf3059445f3d13580b889bfd76638a70c2c6b3febcf35edd2ddeda84f42ca8c 2775 apt_1.7.0~rc2.dsc e43871ce1eaf707a84b7b87741fb360dfa2fb97fa68fcc1a2aaac14678942eda 2150680 apt_1.7.0~rc2.tar.xz 364b36882b300ff84b5f9856997a3a2a1e9c9b77343d1f428c9286e4873225b9 7414 apt_1.7.0~rc2_source.buildinfo Files: 2f06031fa655a4089bda32c9fc5c71fe 2775 admin important apt_1.7.0~rc2.dsc f63357f07119f7518898d9cb17265707 2150680 admin important apt_1.7.0~rc2.tar.xz 436e090e1f32e55de81861bea11876bb 7414 admin important apt_1.7.0~rc2_source.buildinfo -BEGIN
Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload
Hey, just wanted to chime in here. I successfully backported the Buster version of enigmail to Stretch by removing the versioned dependency on gnupg. So far I haven't experienced any difficulties. Of course this isn't a solution for the OpenPGP.js problem but at least to me it seems that the gnupg version in Stretch works well with enigmail. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#909120: camitk FTBFS: tests segfault (Bug #909120)
Processing control commands: > tags -1 upstream Bug #909120 [src:camitk] camitk FTBFS: tests segfault Added tag(s) upstream. -- 909120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909120: camitk FTBFS: tests segfault (Bug #909120)
Control: tags -1 upstream
Hi Bernhard,
thanks a lot for your investigation. Emmanuel Promayon is Uploader and
Upstream and I think he will come back to you and hopefully will
implement the fix soon.
Kind regards
Andreas.
On Thu, Sep 20, 2018 at 06:01:38PM +0200, Bernhard Übelacker wrote:
> Hello all,
> I tried to reproduce this issue.
>
> Unfortunately I never get the "(SEGFAULT)" output for all tests,
> just "(Failed)" for most. But some do really segfault in my amd64 VM.
>
> I think the segfaults are caused by the line "delete component;", that
> invalidates the iterator by removing its element from the components vector.
>
> For some reason the iterator contains still the previous pointer
> and therefore we try to delete the same pointer twice.
>
>
> Attached patch tries to change the loop assuming that the
> deleted element will always be removed inside the delete operation.
>
> With that patch I do not get any segfault, but still tests
> fail for some reason.
>
>
> Kind regards,
> Bernhard
>
>
>
>
> # Here we crash:
>
> (gdb) bt
> #0 0x0061 in ?? ()
> #1 0x7fffeb32c0d6 in MultiComponent::deleteAllSubComponents
> (this=this@entry=0x56d98330) at
> ./modeling/libraries/pml/MultiComponent.cpp:50
> #2 0x7fffeb32c11f in MultiComponent::~MultiComponent
> (this=0x56d98330, __in_chrg=) at
> ./modeling/libraries/pml/MultiComponent.cpp:41
> #3 0x7fffeb32c149 in MultiComponent::~MultiComponent
> (this=0x56d98330, __in_chrg=) at
> ./modeling/libraries/pml/MultiComponent.cpp:38
> #4 0x7fffeb32ce3a in PhysicalModel::clear
> (this=this@entry=0x55705ef0) at
> ./modeling/libraries/pml/PhysicalModel.cpp:99
> #5 0x7fffeb32cf17 in PhysicalModel::~PhysicalModel (this=0x55705ef0,
> __in_chrg=) at ./modeling/libraries/pml/PhysicalModel.cpp:68
> #6 0x7fffeb32cf59 in PhysicalModel::~PhysicalModel (this=0x55705ef0,
> __in_chrg=) at ./modeling/libraries/pml/PhysicalModel.cpp:67
> #7 0x7fffeb317a3d in PMLComponent::~PMLComponent (this=0x55660a00,
> __in_chrg=) at
> ./modeling/components/pmlcomponent/PMLComponent.cpp:96
> #8 0x7fffeb3185a9 in PMLComponent::~PMLComponent (this=0x55660a00,
> __in_chrg=) at
> ./modeling/components/pmlcomponent/PMLComponent.cpp:93
> #9 0x77ec4ad7 in camitk::Application::close(camitk::Component*) ()
> at ./sdk/libraries/core/application/Application.cpp:623
> #10 0xbc5c in main () at
> ./sdk/applications/testcomponents/main.cpp:204
> #11 0x76e99b17 in __libc_start_main (main=0xb080 ,
> argc=9, argv=0x7fffe398, init=, fini=,
> rtld_fini=, stack_end=0x7fffe388) at
> ../csu/libc-start.c:310
> #12 0xc35a in _start () at
> ./sdk/applications/testcomponents/main.cpp:136
>
> (gdb) list -
> 46
> 47 // -- deleteAllSubComponents -
> 48 void MultiComponent::deleteAllSubComponents() {
> 49 for (auto& component : components) {
> 50 delete component;
> 51 }
> 52 components.clear();
> 53 }
>
>
>
>
> # Here the pointer being deleted is removed from the components vector
> # and that way invalidating the iterator.
>
> (gdb) bt
> #0 MultiComponent::removeSubComponent (c=0x579d70f0,
> this=0x56d98330) at ./modeling/libraries/pml/MultiComponent.h:134
> #1 Component::removeFromParents() () at
> ./modeling/libraries/pml/Component.cpp:60
> #2 0x7fffeb32c127 in MultiComponent::~MultiComponent
> (this=0x579d70f0, __in_chrg=) at
> ./modeling/libraries/pml/MultiComponent.cpp:44
> #3 0x7fffeb32c149 in MultiComponent::~MultiComponent
> (this=0x579d70f0, __in_chrg=) at
> ./modeling/libraries/pml/MultiComponent.cpp:38
> #4 0x7fffeb32c0d6 in MultiComponent::deleteAllSubComponents
> (this=this@entry=0x56d98330) at
> ./modeling/libraries/pml/MultiComponent.cpp:50
> #5 0x7fffeb32c11f in MultiComponent::~MultiComponent
> (this=0x56d98330, __in_chrg=) at
> ./modeling/libraries/pml/MultiComponent.cpp:41
> #6 0x7fffeb32c149 in MultiComponent::~MultiComponent
> (this=0x56d98330, __in_chrg=) at
> ./modeling/libraries/pml/MultiComponent.cpp:38
> #7 0x7fffeb32ce3a in PhysicalModel::clear
> (this=this@entry=0x55705ef0) at
> ./modeling/libraries/pml/PhysicalModel.cpp:99
> ...
>
> (gdb) list modeling/libraries/pml/MultiComponent.h:134
> 129 }
> 130 inline void MultiComponent::removeSubComponent(Component* c) {
> 131 auto it = std::find(components.begin(), components.end(), c);
> 132 if (it != components.end()) {
> 133 components.erase(it);
> 134 c->removeParentMultiComponent(this);
> 135 }
> 136 }
> From 52f172e553ebddf068b8e35601da5eefd295cf3d Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?=
> Date: Thu, 20 Sep 2018 17:42:14 +0200
> Subject: [PATCH] Make loop safe for removal of elements.
>
> Bug-Debian:
Bug#909286: firefox: "The bookmarks and history system will not be functional" message always
Package: firefox Version: 62.0-1 Severity: grave Tags: newcomer Justification: renders package unusable Dear Maintainer, * What led up to the situation? Upgraded firefox:amd64 (61.0.1-1, 62.0-1) * What exactly did you do (or not do) that was effective (or ineffective)? Start Firefox. * What was the outcome of this action? The "The bookmarks and history system will not be functional" message is displayed and history is not available. * What outcome did you expect instead? No errors?. Attempted the suggested troubleshooting steps: - Restart machine. - Move places.sqlite away so that FF creates a new one. - Create a new profile. The error remained after each of those steps. The solution: Even though firefox does not appear to link to sqlite (ldd showed no link to it), the solution was to upgrade sqlite: Upgrade: libsqlite3-0:amd64 (3.16.2-5+deb9u1, 3.24.0-1), sqlite3:amd64 (3.16.2-5+deb9u1, 3.24.0-1) -- Package-specific info: -- Addons package information -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'stable'), (800, 'testing'), (700, 'unstable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages firefox depends on: ii debianutils 4.8.1.1 ii fontconfig2.11.0-6.7+b1 ii libatk1.0-0 2.22.0-1 ii libc6 2.27-6 ii libcairo-gobject2 1.14.8-1 ii libcairo2 1.14.8-1 ii libdbus-1-3 1.10.26-0+deb9u1 ii libdbus-glib-1-2 0.108-2 ii libevent-2.1-62.1.8-stable-4 ii libffi6 3.2.1-6 ii libfontconfig12.13.0-5 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgdk-pixbuf2.0-02.36.5-2+deb9u2 ii libglib2.0-0 2.50.3-2 ii libgtk-3-03.22.11-1 ii libjsoncpp1 1.7.4-3 ii libnspr4 2:4.12-6 ii libnss3 2:3.39-1 ii libpango-1.0-01.40.5-1 ii libsqlite3-0 3.24.0-1 ii libstartup-notification0 0.12-4+b2 ii libstdc++66.3.0-18+deb9u1 ii libvpx5 1.7.0-3 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb-shm0 1.12-1 ii libxcb1 1.12-1 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.4-2+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1 ii procps2:3.3.12-3+deb9u1 ii zlib1g1:1.2.11.dfsg-1 Versions of packages firefox recommends: ii libavcodec57 7:3.2.12-1~deb9u1 Versions of packages firefox suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-3 ii libgssapi-krb5-2 1.15-1+deb9u1 ii libgtk2.0-02.24.31-2 -- no debconf information
Processed: severity of 909284 is serious
Processing commands for cont...@bugs.debian.org: > severity 909284 serious Bug #909284 [minidlna] minidlna: Minidlna needs libavcodec.so.57 which is not a dependancy Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 909284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working
On 18/09/18 21:45, Mike Hommey wrote: Incidentally, since you're talking about Javascript, I thought it might be relevant that I'm using the NoScript add-on, so I thought I'd try disabling that (which worked), and setting javascript.options.baselinejit and javascript.options.ion back to true. When I switched javascript.options.baselinejit back to true, Firefox instantly crashed. (But, of course, it's recoverable again via -safe-mode.) Setting only javascript.options.ion back to true *doesn't* crash Firefox, or prevent it from starting. Can you restore all the prefs and addons you changed to what they were before and try the following package? https://people.debian.org/~glandium/firefox-esr_60.2.0esr-1~deb9u2.2_i386.deb sha256: 4f092e11faf729316ea96be5b9f6ecca58ea1f001279c44406a8d505b021c17f I re-enabled NoScript and set javascript.options.ion and javascript.options.baselinejit back to true; then I installed your latest package, and it seems to work fine! Thanks for all your patient work on this. Tim <><
Bug#902341: marked as done (dns-root-data update breaks dnsmasq startup)
Your message dated Thu, 20 Sep 2018 23:46:07 +0200 with message-id <20180920214550.GA10412@novelo> and subject line dnsmasq: #902341 was fixed in 2.72-3+deb8u3 has caused the Debian Bug report #902341, regarding dns-root-data update breaks dnsmasq startup 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.) -- 902341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnsmasq Version: 2.72-3+deb8u2 Severity: critical Dear Maintainer, upgrading dns-root-data to 2017072601~deb8u2 breaks dnsmasq startup routine. Parsing /usr/share/dns/root.ds at /etc/init.d/dnsmasq (line 115) isn't working anymore because the format changed from . IN DS 19036 8 2 49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5 to . 172800 IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 . 172800 IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Please see also #860064 where a similar update caused the same problem. Downgrading to dns-root-data=2017072601~deb8u1 is a possible workaround at the moment. Best Regards Ansgar -- System Information: Debian Release: 8.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnsmasq depends on: ii dnsmasq-base 2.72-3+deb8u2 ii init-system-helpers 1.22 ii netbase 5.3 dnsmasq recommends no packages. Versions of packages dnsmasq suggests: pn resolvconf -- Configuration Files: /etc/dnsmasq.conf changed [not included] /etc/init.d/dnsmasq changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Version: 2.72-3+deb8u3 signature.asc Description: PGP signature --- End Message ---
Bug#909126: ompl-plannerarena: missing Breaks+Replaces: ompl-demos (<< 1.4)
Followup-For: Bug #909126 Control: found -1 1.4.0+ds1-2 You used a creative syntax in e830506, but that doesn't work. You will have to split in two lines. The tools will have emitted warnings about the unknown field... Andreas
Processed: Re: ompl-plannerarena: missing Breaks+Replaces: ompl-demos (<< 1.4)
Processing control commands:
> found -1 1.4.0+ds1-2
Bug #909126 {Done: Leopold Palomo-Avellaneda }
[ompl-plannerarena] ompl-plannerarena: missing Breaks+Replaces: ompl-demos (<<
1.4)
Marked as found in versions ompl/1.4.0+ds1-2; no longer marked as fixed in
versions ompl/1.4.0+ds1-2 and reopened.
--
909126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 909139 to src:linux, reassign 893074 to src:mutter
Processing commands for cont...@bugs.debian.org: > reassign 909139 src:linux Bug #909139 [i915] i915 missing Switch to turn off rc6 causes Screen Flicker on idle y910 Warning: Unknown package 'i915' Bug reassigned from package 'i915' to 'src:linux'. No longer marked as found in versions firmware-misc-nonfree. Ignoring request to alter fixed versions of bug #909139 to the same values previously set > reassign 893074 src:mutter Bug #893074 [libmutter-2-0] gnome-control-center: external tv device freezes gnome on wayland Bug #894306 [libmutter-2-0] external monitor resolution higher than 1920x1080 freezes rendering Warning: Unknown package 'libmutter-2-0' Bug reassigned from package 'libmutter-2-0' to 'src:mutter'. Bug reassigned from package 'libmutter-2-0' to 'src:mutter'. Ignoring request to alter found versions of bug #893074 to the same values previously set Ignoring request to alter found versions of bug #894306 to the same values previously set Ignoring request to alter fixed versions of bug #893074 to the same values previously set Ignoring request to alter fixed versions of bug #894306 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 893074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893074 894306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894306 909139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909283: dokuwiki: Dependency on php-phpseclib to weak, also fulfilled by php-seclib which doesn't suffice
Package: dokuwiki Version: 0.0.20180422.a-1 Severity: serious Justification: missing (not strict enough) dependency dokuwiki depends unversioned on php-phpseclib which can currently be fulfilled by either php-phpseclib/2.0.11-1 or by php-seclib/1.0.11-1 (which provides php-phpseclib). But if only php-seclib/1.0.11-1 is installed, the webserver returns a 500 for dokuwiki with these messages in the error.log: [Fri Sep 21 00:54:00.639686 2018] [php7:warn] [pid 2332] [client 127.0.0.1:48614] PHP Warning: require(/usr/share/php/phpseclib/bootstrap.php): failed to open stream: No such file or directory in /usr/share/dokuwiki/vendor/composer/autoload_real.php on line 66 [Fri Sep 21 00:54:00.639724 2018] [php7:error] [pid 2332] [client 127.0.0.1:48614] PHP Fatal error: require(): Failed opening required '/usr/share/php/phpseclib/bootstrap.php' (include_path='.:/usr/share/php') in /usr/share/dokuwiki/vendor/composer/autoload_real.php on line 66 The file /usr/share/php/phpseclib/bootstrap.php is only in php-phpseclib. As far as I can see this can be solved by depending versioned on php-phpseclib, e.g. on "php-phpseclib (>= 2)". (System information below is from after I've replaced php-seclib with php-phpseclib.) -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (300, 'unstable'), (299, 'unstable-debug'), (210, 'experimental'), (209, 'experimental-debug'), (110, 'buildd-unstable'), (105, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages dokuwiki depends on: ii debconf [debconf-2.0] 1.5.69 ii javascript-common 11 ii libjs-jquery 3.2.1-1 ii libjs-jquery-cookie12-1 ii libjs-jquery-ui1.12.1+dfsg-5 ii libphp-simplepie 1.3.1+dfsg-3.1 ii php1:7.2+62 ii php-geshi 1.0.8.11-3 ii php-phpseclib 2.0.11-1 ii php-random-compat 2.0.17-1 ii php-xml1:7.2+62 ii php7.2 [php] 7.2.9-1 ii php7.2-xml [php-xml] 7.2.9-1 ii ucf3.0038 Versions of packages dokuwiki recommends: ii imagemagick 8:6.9.10.8+dfsg-1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.8+dfsg-1 ii php-gd1:7.2+62 pn php-ldap | php-mysql | php-pgsql ii php7.2-cli [php-cli] 7.2.9-1 ii php7.2-gd [php-gd]7.2.9-1 ii wget 1.19.5-1 Versions of packages dokuwiki suggests: ii libapache2-mod-xsendfile 0.12-2 -- debconf information: * dokuwiki/wiki/policy: public * dokuwiki/wiki/superuser: admin * dokuwiki/system/purgepages: false * dokuwiki/wiki/title: Swiss Mechanical Keyboard Enthusiasts Community * dokuwiki/system/restart-webserver: false dokuwiki/system/localnet: 10.0.0.0/24 * dokuwiki/wiki/fullname: DokuWiki Administrator * dokuwiki/system/accessible: global * dokuwiki/system/documentroot: /dokuwiki * dokuwiki/wiki/email: abe+dokuwiki-some...@deuxchevaux.org * dokuwiki/wiki/license: cc-by-sa * dokuwiki/system/configure-webserver: apache2 * dokuwiki/system/writeplugins: false * dokuwiki/wiki/acl: true * dokuwiki/system/writeconf: true dokuwiki/wiki/failpass:
Bug#864827: Please go ahead adding explanations to the wiki
Hi Stefan, > This bug basically makes the package unusable. Unfortunately that's true. > I understand that adapting the packaging to the new structure of > Zotero-5 will take some time, but in the mean time, could someone add > a page to the Debian wiki outlining how to install Zotero-5 by hand on > a Debian system You are more than welcomed to do so. Everyone can contribute to the Debian wiki. Yours, Benda
Bug#909240: xorg-server: Unsatisfiable build-depends on libunwind-dev on s390x
Source: xorg-server Version: 2:1.20.1-2 Severity: serious Tags: ftbfs xorg-server no longer builds on s390x since libunwind-dev is not available on that architecture. (This also affects many ports.) https://buildd.debian.org/status/package.php?p=xorg-server https://buildd.debian.org/status/package.php?p=libunwind Thanks, Jeremy Bicha
Bug#909177: marked as done (snapper-gui should depend on snapper otherwise it crashes at start)
Your message dated Thu, 20 Sep 2018 06:04:37 +
with message-id
and subject line Bug#909177: fixed in snapper-gui 0git.960a94834f-3
has caused the Debian Bug report #909177,
regarding snapper-gui should depend on snapper otherwise it crashes at start
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.)
--
909177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snapper-gui
Version: 0git.960a94834f-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
snapper-gui doesnt work if snapper has not be previously installed.
I get:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in
activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
's', (bus_name,), **keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could
not get owner of name 'org.opensuse.Snapper': no such name
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/snapper-gui", line 11, in
load_entry_point('snappergui==0.1', 'gui_scripts', 'snapper-gui')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 484, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2707,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2325,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2331,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/snappergui/__init__.py", line 9, in
'/org/opensuse/Snapper'),
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in
activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in
start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.opensuse.Snapper was not provided by any .service files
Regards
Jean-Luc
- -- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unstable-debug'), (500,
'buildd-unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-rc4-i7-0.1 (SMP w/8 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages snapper-gui depends on:
ii gir1.2-gtksource-3.0 3.24.9-1
ii python3 3.6.6-1
snapper-gui recommends no packages.
snapper-gui suggests no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCW6IShwAKCRBR0YZfPMac
0I9RAKCL3Q19iSDNdj6cMUR3oKVNV8YVGgCdGb9Ji+puC7wx/1nR5eMn87OOtD4=
=rjRm
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: snapper-gui
Source-Version: 0git.960a94834f-3
We believe that the bug you reported is fixed in the latest version of
snapper-gui, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ritesh Raj Sarraf (supplier of updated snapper-gui 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
Bug#905379: Bug explanation
Hi, I hadn't launched anki since long and hence got stuck. Looking at the trace I see: self.focusProxy().installEventFilter(self) and an attribute error that NoneType has no installEventFilter, so it's quite clear what the problem is: self.focusProxy() returns None! That might mean that some versions of PyQT were having a default focus proxy and that line worked, but newer versions need an explicit setup. Commenting the line makes it possible to go further, with a few error windows showing up. I would suggest asking around. jpuydt on irc.debian.org
Bug#909215: marked as done (glusterfs: Multiple security issues)
Your message dated Thu, 20 Sep 2018 10:50:03 + with message-id and subject line Bug#909215: fixed in glusterfs 4.1.4-1 has caused the Debian Bug report #909215, regarding glusterfs: Multiple security issues 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.) -- 909215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glusterfs X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for glusterfs. CVE-2018-10904[0]: | It was found that glusterfs server does not properly sanitize file | paths in the "trusted.io-stats-dump" extended attribute which is used | by the "debug/io-stats" translator. Attacker can use this flaw to | create files and execute arbitrary code. To exploit this attacker | would require sufficient access to modify the extended attributes of | files on a gluster volume. CVE-2018-10907[1]: | It was found that glusterfs server is vulnerable to multiple stack | based buffer overflows due to functions in server-rpc-fopc.c | allocating fixed size buffers using 'alloca(3)'. An authenticated | attacker could exploit this by mounting a gluster volume and sending a | string longer that the fixed buffer size to cause crash or potential | code execution. CVE-2018-10911[2]: | A flaw was found in the way dic_unserialize function of glusterfs does | not handle negative key length values. An attacker could use this flaw | to read memory from other locations into the stored dict value. CVE-2018-10913[3]: | An information disclosure vulnerability was discovered in glusterfs | server. An attacker could issue a xattr request via glusterfs FUSE to | determine the existence of any file. CVE-2018-10914[4]: | It was found that an attacker could issue a xattr request via | glusterfs FUSE to cause gluster brick process to crash which will | result in a remote denial of service. If gluster multiplexing is | enabled this will result in a crash of multiple bricks and gluster | volumes. CVE-2018-10923[5]: | It was found that the "mknod" call derived from mknod(2) can create | files pointing to devices on a glusterfs server node. An authenticated | attacker could use this to create an arbitrary device and read data | from any device attached to the glusterfs server node. CVE-2018-10926[6]: | A flaw was found in RPC request using gfs3_mknod_req supported by | glusterfs server. An authenticated attacker could use this flaw to | write files to an arbitrary location via path traversal and execute | arbitrary code on a glusterfs server node. CVE-2018-10927[7]: | A flaw was found in RPC request using gfs3_lookup_req in glusterfs | server. An authenticated attacker could use this flaw to leak | information and execute remote denial of service by crashing gluster | brick process. CVE-2018-10928[8]: | A flaw was found in RPC request using gfs3_symlink_req in glusterfs | server which allows symlink destinations to point to file paths | outside of the gluster volume. An authenticated attacker could use | this flaw to create arbitrary symlinks pointing anywhere on the server | and execute arbitrary code on glusterfs server nodes. CVE-2018-10929[9]: | A flaw was found in RPC request using gfs2_create_req in glusterfs | server. An authenticated attacker could use this flaw to create | arbitrary files and execute arbitrary code on glusterfs server nodes. CVE-2018-10930[10]: | A flaw was found in RPC request using gfs3_rename_req in glusterfs | server. An authenticated attacker could use this flaw to write to a | destination outside the gluster volume. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-10904 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10904 [1] https://security-tracker.debian.org/tracker/CVE-2018-10907 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10907 [2] https://security-tracker.debian.org/tracker/CVE-2018-10911 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10911 [3] https://security-tracker.debian.org/tracker/CVE-2018-10913 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10913 [4] https://security-tracker.debian.org/tracker/CVE-2018-10914 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10914 [5] https://security-tracker.debian.org/tracker/CVE-2018-10923 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10923
Processed: Bug #873213 in aspectj marked as pending
Processing control commands:
> tag -1 pending
Bug #873213 {Done: Emmanuel Bourg } [src:aspectj] FTBFS with
Java 9
Added tag(s) pending.
--
873213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#909219: FTBFS in pbuilder, missed dependency
Processing control commands: > tag -1 moreinfo Bug #909219 [gimagereader] FTBFS in pbuilder, missed dependency Added tag(s) moreinfo. -- 909219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909244: kobodeluxe not playable - immediately pauses and can't be resumed
Hi, Am 20.09.18 um 11:00 schrieb Damyan Ivanov: > Package: kobodeluxe > Version: 0.5.1-9 > Severity: grave > Justification: renders package unusable > > Trying to start a game in kobodeluxe results in a "PAUSED" game, with no > possibility to resume it. The only way out is to press Esc and exit the game. > > Steps to reproduce: > - start kobodl > - press shift or space three times > > I tried this under gdm3/gnome3/wayland, lightdm/xfce4/Xorg and > lightdb/openbox/Xorg so it seems to be independent of the graphical > environment. > > Also tried with a new user account without success and after removing > apparmor > and rebooting. I can reproduce this issue in Buster. It doesn't occur in Stretch though and the package hasn't changed since then. After I changed some random options in the Video menu, the game started to work normally again. I guess this is somehow related to the new GCC-8 or the SDL library. Some kind of initialization bug? Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#907953: network-manager-strongswan FTBFS with glib 2.58
The official documentation for the most recent *stable* version 2.56.2 on https://developer.gnome.org/gobject/stable/gobject-Type-Information.html#g-type-class-add-private doesn't mention that this function/macro is deprecated or that it will be kicked out in the near or far future. There is no other documentation, AFAICS. Wouldn't you agree that network-manager-strongswan used the documented api? Please reassign. Thanx very much Harri
Bug#873213: marked as done (FTBFS with Java 9)
Your message dated Thu, 20 Sep 2018 10:49:19 +
with message-id
and subject line Bug#873213: fixed in aspectj 1.9.1-1
has caused the Debian Bug report #873213,
regarding FTBFS with Java 9
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.)
--
873213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspectj
Version: 1.8.9-2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9
Tags: fixed-upstream
This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls
Given aspectj is a, uh, complex piece of software, I think the solution
here may be to package 1.9-beta2 (or higher), which the download page
says is the first version to work on Java 9:
https://eclipse.org/aspectj/downloads.php
Build log:
[javac]
/build/aspectj-1.8.9/bcel-builder/src/org/aspectj/apache/bcel/generic/TABLESWITCH.java:62:
warning: SWITCH is internal proprietary API and may be removed in a future
release
[javac] import com.sun.org.apache.bcel.internal.generic.SWITCH;
...
packageAndPush:
[mkdir] Created dir: /build/aspectj-1.8.9/org.eclipse.jdt.core/classes
[iajc] error at class RefreshJob extends Job {
[iajc] ^
[iajc]
/build/aspectj-1.8.9/org.eclipse.jdt.core/src/org/aspectj/org/eclipse/jdt/internal/core/ExternalFoldersManager.java:432:0::0
The type java.lang.Comparable cannot be resolved. It is indirectly referenced
from required .class files
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: aspectj
Source-Version: 1.9.1-1
We believe that the bug you reported is fixed in the latest version of
aspectj, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg (supplier of updated aspectj 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, 20 Sep 2018 12:31:17 +0200
Source: aspectj
Binary: aspectj libaspectj-java aspectj-doc libaspectj-java-doc
Architecture: source
Version: 1.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: Emmanuel Bourg
Description:
aspectj- aspect-oriented extension for Java - tools
aspectj-doc - aspect-oriented extension for Java - documentation
libaspectj-java - aspect-oriented extension for Java - library
libaspectj-java-doc - aspect-oriented extension for Java - API documentation
Closes: 873213
Changes:
aspectj (1.9.1-1) unstable; urgency=medium
.
* Team upload.
* New upstream release
- Refreshed the patches
- Build depend on libaspectj-java (>= 1.9.0~beta5-1)
- Build depend on libasm-java (>= 6.1)
- Build with default-jdk (Closes: #873213)
* Replaced Damien Raude-Morvan as uploader
Checksums-Sha1:
4177a9040307616504eafb7b32fe9a93738f4b43 2667 aspectj_1.9.1-1.dsc
18eeec68021a103ccd05e4bb36cdcf724ffee46c 5463948 aspectj_1.9.1.orig.tar.xz
ba9775139065f1b6240d3f5e03bc45c2cc3ed5d6 17780 aspectj_1.9.1-1.debian.tar.xz
1b144571cab16ea380c5111890c85164dd7a244a 12435 aspectj_1.9.1-1_source.buildinfo
Checksums-Sha256:
bedd529f23ec2eb0cc718d584178a536c32bd24b1fc1c5de8e0a06e82b41dac0 2667
aspectj_1.9.1-1.dsc
812df33bbff002f4d6370cfa0fbb1cdccf19753bca0d8edfb7b66d1208429c92 5463948
aspectj_1.9.1.orig.tar.xz
85fd91277c0782d4c73ed91875848c42dcac445b3fc76bbd329dfb18dec31f48 17780
aspectj_1.9.1-1.debian.tar.xz
65feb8a7e2210cd17655433d7fc4b832cd57688a2427723eb3378c1da204c309 12435
aspectj_1.9.1-1_source.buildinfo
Files:
341bbe80490b75f7a23409a6641e410c 2667 java optional aspectj_1.9.1-1.dsc
2559a346952afa29d9e420e8bc42f88e 5463948 java optional
aspectj_1.9.1.orig.tar.xz
2f3f88f3ab55723e5d6356234aa8af18 17780 java optional
aspectj_1.9.1-1.debian.tar.xz
7fc14691ab0cf0139e4ede871f68c1d6 12435 java optional
aspectj_1.9.1-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlujd9ESHGVib3VyZ0Bh
Bug#873213: Bug #873213 in aspectj marked as pending
Control: tag -1 pending Hello, Bug #873213 in aspectj reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/aspectj/commit/91a2664bc1e22fce7968d0e7ebf8afc317da4425 Build with default-jdk (Closes: #873213) (this message was generated automatically) -- Greetings https://bugs.debian.org/873213
Bug#903802: marked as done (libomp5-7: missing Breaks+Replaces: libomp5)
Your message dated Thu, 20 Sep 2018 11:51:01 + with message-id and subject line Bug#903802: fixed in llvm-toolchain-7 1:7-2 has caused the Debian Bug report #903802, regarding libomp5-7: missing Breaks+Replaces: libomp5 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.) -- 903802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libomp5-7 Version: 1:7~svn336894-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libomp5-7_1%3a7~svn336894-1~exp1_amd64.deb ... Unpacking libomp5-7:amd64 (1:7~svn336894-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libomp5-7_1%3a7~svn336894-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libomp.so.5', which is also in package libomp5:amd64 6.0.1-1 Errors were encountered while processing: /var/cache/apt/archives/libomp5-7_1%3a7~svn336894-1~exp1_amd64.deb Maybe Conflicts+Replaces+Provides: libomp5 is the correct solution, otherwise we will have to revisit this issue for every new major llvm version. cheers, Andreas libomp5=6.0.1-1_libomp5-7=1%7~svn336894-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: llvm-toolchain-7 Source-Version: 1:7-2 We believe that the bug you reported is fixed in the latest version of llvm-toolchain-7, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-7 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 19 Sep 2018 14:12:34 +0200 Source: llvm-toolchain-7 Binary: clang-7 clang-tools-7 clang-format-7 clang-tidy-7 clang-7-doc libclang1-7 libclang-7-dev libclang-common-7-dev libfuzzer-7-dev python-clang-7 clang-7-examples libllvm7 llvm-7 llvm-7-runtime llvm-7-dev llvm-7-tools llvm-7-doc llvm-7-examples lld-7 liblld-7 liblld-7-dev lldb-7 liblldb-7 python-lldb-7 liblldb-7-dev libomp-7-dev libomp5-7 libomp-7-doc libc++1-7 libc++-7-dev libc++abi1-7 libc++abi-7-dev Architecture: source Version: 1:7-2 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang-7- C, C++ and Objective-C compiler clang-7-doc - C, C++ and Objective-C compiler - Documentation clang-7-examples - Clang examples clang-format-7 - Tool to format C/C++/Obj-C code clang-tidy-7 - clang-based C++ linter tool clang-tools-7 - clang-based tools for C/C++ developments libc++-7-dev - LLVM C++ Standard library (development files) libc++1-7 - LLVM C++ Standard library libc++abi-7-dev - LLVM low level support for a standard C++ library (development fi libc++abi1-7 - LLVM low level support for a standard C++ library libclang-7-dev - clang library - Development package libclang-common-7-dev - clang library - Common development package libclang1-7 - C interface to the clang library libfuzzer-7-dev - Library for coverage-guided fuzz testing liblld-7 - LLVM-based linker, library liblld-7-dev - LLVM-based linker, header files liblldb-7 - Next generation, high-performance debugger, library liblldb-7-dev - Next generation, high-performance debugger, header files libllvm7 - Modular compiler and toolchain technologies, runtime library libomp-7-dev - LLVM OpenMP runtime - dev package libomp-7-doc - LLVM OpenMP runtime - Documentation libomp5-7 - LLVM OpenMP runtime lld-7 - LLVM-based linker lldb-7 - Next generation, high-performance debugger llvm-7 - Modular compiler and toolchain technologies llvm-7-dev - Modular compiler and toolchain technologies, libraries and header llvm-7-doc - Modular compiler and toolchain
Bug#906057: linphone: Linphone "cannot start transport on port 5060, maybe this port is already used" although it is not.
On Mon, 13 Aug 2018 20:27:58 +0200 Eduardo Casais wrote: Package: linphone Version: 3.6.1-3 Severity: grave Tags: ipv6 Justification: renders package unusable Dear Maintainer, After upgrading from Jessie 8 to Stretch 9 (64bits), Linphone has become inoperative. All of the above, seconded. Of the test fixes I've tried which are listed in the original message, all had the same result as the OP.
Bug#908383: marked as done (libeclipse-core-commands-java: Build-Depends on non-existent libequinox-bidi-java)
Your message dated Thu, 20 Sep 2018 11:07:00 +0200 with message-id and subject line Re: libeclipse-core-commands-java: Build-Depends on non-existent libequinox-bidi-java has caused the Debian Bug report #908383, regarding libeclipse-core-commands-java: Build-Depends on non-existent libequinox-bidi-java to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 908383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eclipse-platform-ui Version: 4.7.3-1 Severity: serious Tags: ftbfs eclipse-platform-ui Build-Depend on libequinox-bidi-java but that package doesn't exist in Debian. You can see this on https://packages.debian.org/source/unstable/eclipse-platform-ui This kind of issue affects several of the new Eclipse related packages. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- libequinox-bidi-java has entered unstable yesterday.--- End Message ---
Bug#908800: nautilus: can't use nautilus without tracker
This problem was introduced by https://gitlab.gnome.org/GNOME/tracker/commit/ee07c990 Here are some options: 1) We could revert that commit but maybe that's not a good idea. Apps would still emit warnings when the tracker libraries can't find those ontology rules. 2) We could have the apps that build against tracker depend on tracker. Most already do, but this means nautilus, brasero, and the brasero fork kylin-burner. I'm not sure that the tracker integration in brasero works and I don't think it's very useful there, but the dependency probably wouldn't hurt. We have some good arguments for nautilus to now depend on tracker too. 3) We could introduce a tracker-common package including /usr/share/tracker/ and /usr/share/locale/ and have the tracker library packages depend on it. So I'm leaning towards #3 (and independently having nautilus depend on tracker). What do the rest of you think? Thanks, Jeremy Bicha
Bug#903802: marked as done (libomp5-7: missing Breaks+Replaces: libomp5)
Your message dated Thu, 20 Sep 2018 14:39:59 + with message-id and subject line Bug#903802: fixed in llvm-toolchain-snapshot 1:8~svn342638-1 has caused the Debian Bug report #903802, regarding libomp5-7: missing Breaks+Replaces: libomp5 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.) -- 903802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libomp5-7 Version: 1:7~svn336894-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libomp5-7_1%3a7~svn336894-1~exp1_amd64.deb ... Unpacking libomp5-7:amd64 (1:7~svn336894-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libomp5-7_1%3a7~svn336894-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libomp.so.5', which is also in package libomp5:amd64 6.0.1-1 Errors were encountered while processing: /var/cache/apt/archives/libomp5-7_1%3a7~svn336894-1~exp1_amd64.deb Maybe Conflicts+Replaces+Provides: libomp5 is the correct solution, otherwise we will have to revisit this issue for every new major llvm version. cheers, Andreas libomp5=6.0.1-1_libomp5-7=1%7~svn336894-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: llvm-toolchain-snapshot Source-Version: 1:8~svn342638-1 We believe that the bug you reported is fixed in the latest version of llvm-toolchain-snapshot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-snapshot 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 Sep 2018 12:13:15 +0200 Source: llvm-toolchain-snapshot Binary: clang-8 clang-tools-8 clang-format-8 clang-tidy-8 clang-8-doc libclang1-8 libclang-8-dev libclang-common-8-dev libfuzzer-8-dev python-clang-8 clang-8-examples libllvm8 llvm-8 llvm-8-runtime llvm-8-dev llvm-8-tools llvm-8-doc llvm-8-examples lld-8 liblld-8 liblld-8-dev lldb-8 liblldb-8 python-lldb-8 liblldb-8-dev libomp-8-dev libomp5-8 libomp-8-doc libc++1-8 libc++-8-dev libc++abi1-8 libc++abi-8-dev Architecture: source Version: 1:8~svn342638-1 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang-8- C, C++ and Objective-C compiler clang-8-doc - C, C++ and Objective-C compiler - Documentation clang-8-examples - Clang examples clang-format-8 - Tool to format C/C++/Obj-C code clang-tidy-8 - clang-based C++ linter tool clang-tools-8 - clang-based tools for C/C++ developments libc++-8-dev - LLVM C++ Standard library (development files) libc++1-8 - LLVM C++ Standard library libc++abi-8-dev - LLVM low level support for a standard C++ library (development fi libc++abi1-8 - LLVM low level support for a standard C++ library libclang-8-dev - clang library - Development package libclang-common-8-dev - clang library - Common development package libclang1-8 - C interface to the clang library libfuzzer-8-dev - Library for coverage-guided fuzz testing liblld-8 - LLVM-based linker, library liblld-8-dev - LLVM-based linker, header files liblldb-8 - Next generation, high-performance debugger, library liblldb-8-dev - Next generation, high-performance debugger, header files libllvm8 - Modular compiler and toolchain technologies, runtime library libomp-8-dev - LLVM OpenMP runtime - dev package libomp-8-doc - LLVM OpenMP runtime - Documentation libomp5-8 - LLVM OpenMP runtime lld-8 - LLVM-based linker lldb-8 - Next generation, high-performance debugger llvm-8 - Modular compiler and toolchain technologies llvm-8-dev - Modular compiler and toolchain technologies,
Bug#893378: marked as done (mp4parser FTBFS with openjdk-9)
Your message dated Thu, 20 Sep 2018 14:19:27 +0200 with message-id <771ca1e2-e455-fadb-db2e-0753ebeb1...@apache.org> and subject line Re: mp4parser FTBFS with openjdk-9 has caused the Debian Bug report #893378, regarding mp4parser FTBFS with openjdk-9 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.) -- 893378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp4parser Version: 1.0.4.2-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mp4parser.html ... [[1;34mINFO[m] Scanning for projects... [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mReactor Build Order:[m [[1;34mINFO[m] [[1;34mINFO[m] ISO Parser [[1;34mINFO[m] MP4 Parser Project [[1;34mINFO[m] [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1mBuilding ISO Parser 1.0.4.2[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.2:resources[m [1m(default-resources)[m @ [36misoparser[0;1m ---[m [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources. [[1;34mINFO[m] Copying 4 resources [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.2:compile[m [1m(default-compile)[m @ [36misoparser[0;1m ---[m [[1;34mINFO[m] Changes detected - recompiling the module! [[1;34mINFO[m] Compiling 326 source files to /build/1st/mp4parser-1.0.4.2/isoparser/target/classes Use of target 1.5 is no longer supported, switching to 1.7 Use of source 1.5 is no longer supported, switching to 1.7 [[1;34mINFO[m] /build/1st/mp4parser-1.0.4.2/isoparser/src/main/java/com/googlecode/mp4parser/boxes/mp4/objectdescriptors/ObjectDescriptorFactory.java: Some input files use or override a deprecated API. [[1;34mINFO[m] /build/1st/mp4parser-1.0.4.2/isoparser/src/main/java/com/googlecode/mp4parser/boxes/mp4/objectdescriptors/ObjectDescriptorFactory.java: Recompile with -Xlint:deprecation for details. [[1;34mINFO[m] /build/1st/mp4parser-1.0.4.2/isoparser/src/main/java/com/googlecode/mp4parser/util/RangeStartMap.java: Some input files use unchecked or unsafe operations. [[1;34mINFO[m] /build/1st/mp4parser-1.0.4.2/isoparser/src/main/java/com/googlecode/mp4parser/util/RangeStartMap.java: Recompile with -Xlint:unchecked for details. [[1;34mINFO[m] [[1;34mINFO[m] [1m--- [0;32maspectj-maven-plugin:1.10:compile[m [1m(default)[m @ [36misoparser[0;1m ---[m [[1;34mINFO[m] Showing AJC message detail for messages of types: [error, warning, fail] [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : [[1;31mERROR[m] can't find critical required type java.lang.Object : --- End Message --- --- Begin Message --- The upload of aspectj/1.9.1-1 fixed this issue.--- End Message ---
Processed: Re: Bug#906370: jmock2: FTBFS in buster/sid
Processing commands for cont...@bugs.debian.org: > retitle 906370 jmock2: FTBFS with Java 10 (ClassNotFoundException: > javax.xml.ws.handler.LogicalMessageContext) Bug #906370 [src:jmock2] jmock2: FTBFS in buster/sid Changed Bug title to 'jmock2: FTBFS with Java 10 (ClassNotFoundException: javax.xml.ws.handler.LogicalMessageContext)' from 'jmock2: FTBFS in buster/sid'. > user debian-j...@lists.debian.org Setting user to debian-j...@lists.debian.org (was ebo...@apache.org). > usertag 906370 + default-java10 There were no usertags set. Usertags are now: default-java10. > End of message, stopping processing here. Please contact me if you need assistance. -- 906370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 892256 is forwarded to https://github.com/zdohnal/system-config-printer/issues/94
Processing commands for cont...@bugs.debian.org: > forwarded 892256 https://github.com/zdohnal/system-config-printer/issues/94 Bug #892256 [system-config-printer] system-config-printer: Doesn't launch anymore Bug #899187 [system-config-printer] system-config-printer: command system-config-printer fails Set Bug forwarded-to-address to 'https://github.com/zdohnal/system-config-printer/issues/94'. Set Bug forwarded-to-address to 'https://github.com/zdohnal/system-config-printer/issues/94'. > thanks Stopping processing here. Please contact me if you need assistance. -- 892256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892256 899187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906370: Bug #906370 in jmock2 marked as pending
Control: tag -1 pending Hello, Bug #906370 in jmock2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/java-team/jmock2/commit/b347bb139a6924affd1fcb6a21b88b0ad278ac0a Fixed the test failure with Java 10 (Closes: #906370) (this message was generated automatically) -- Greetings https://bugs.debian.org/906370
Processed: Bug #906370 in jmock2 marked as pending
Processing control commands: > tag -1 pending Bug #906370 [src:jmock2] jmock2: FTBFS with Java 10 (ClassNotFoundException: javax.xml.ws.handler.LogicalMessageContext) Added tag(s) pending. -- 906370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909219: marked as done (FTBFS in pbuilder, missed dependency)
Your message dated Thu, 20 Sep 2018 17:11:22 +0200 with message-id <4168d49b-2549-567e-0fb1-254bfc00b...@siduction.org> and subject line Re: Bug#909219: FTBFS in pbuilder, missed dependency has caused the Debian Bug report #909219, regarding FTBFS in pbuilder, missed dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 909219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimagereader Version: 3.2.3-3.3 Severity: serious Dear maintainer, had to rebuild gimagereader because of the current libsane mess, result: -- Checking for module 'gtkmm-3.0' -- Package 'gl', required by 'epoxy', not found CMake Error at /usr/share/cmake-3.12/Modules/FindPkgConfig.cmake:436 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-3.12/Modules/FindPkgConfig.cmake:602 (_pkg_check_modules_internal) CMakeLists.txt:71 (PKG_CHECK_MODULES) Adding libgl1-mesa-dev solve that diff --git a/debian/control b/debian/control index 603c9eb..3ef3dbb 100644 --- a/debian/control +++ b/debian/control @@ -7,6 +7,7 @@ Build-Depends: debhelper (>= 10), intltool (>= 0.35.0), libcairomm-1.0-dev, + libgl1-mesa-dev, libgtkmm-3.0-dev, libgtksourceviewmm-3.0-dev, libgtkspellmm-3.0-dev (>= 3.0.4), The build now: -- Checking for module 'gtkmm-3.0' -- Found gtkmm-3.0, version 3.22.2 -- Checking for module 'gtksourceviewmm-3.0' Cheers Alf -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-rc3-siduction-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimagereader depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.0-1 ii libatkmm-1.6-1v5 2.24.2-3 ii libc62.27-6 ii libcairomm-1.0-1v5 1.12.2-3 ii libfontconfig1 2.13.0-5 ii libgcc1 1:8.2.0-7 ii libglib2.0-0 2.58.0-4 ii libglibmm-2.4-1v52.56.0-2 ii libgomp1 8.2.0-7 ii libgtk-3-0 3.24.0-3 ii libgtkmm-3.0-1v5 3.22.2-2 ii libgtksourceviewmm-3.0-0v5 3.18.0-3 ii libgtkspellmm-3.0-0v53.0.5+dfsg-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjson-glib-1.0-0 1.4.2-4 ii libpangomm-1.4-1v5 2.40.1-4 ii libpodofo0.9.5 0.9.5-11 ii libpoppler-glib8 0.63.0-2 ii libsane 1.0.27-2~2 ii libsigc++-2.0-0v52.10.0-2.1 ii libstdc++6 8.2.0-7 ii libtesseract44.00~git2904-07acc2b2-1 ii libxml++2.6-2v5 2.40.1-2 gimagereader recommends no packages. gimagereader suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- > I'm not seeing this problem, libgl1-mesa-dev gets installed by > the build-dependency resolver. My build log is attached. > Alf, please let us see your full build log. libepoxy (1.5.2-0.2) unstable; urgency=medium * Non-maintainer upload * libepoxy-dev Depends on libgl1-mesa-dev and libegl1-mesa-dev. Those packages provide gl.pc and egl.pc, which are depended on by epoxy.pc since 1.5.2 (Closes: #909173) * Work around #874077 by creating an Xvfb screen where GLX can work -- Simon McVittie Wed, 19 Sep 2018 10:39:51 +0100 I guess that you picked up the fixed libepoxy, which now depend on libgl-mesa-dev - i was just a few hours to early. Didn't see the bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909173 Sorry for the noise. Cheers Alf--- End Message ---
Processed: Re: Processed: Re: Bug#906370: jmock2: FTBFS in buster/sid
Processing commands for cont...@bugs.debian.org: > forwarded 906370 https://github.com/jmock-developers/jmock-library/pull/111 Bug #906370 [src:jmock2] jmock2: FTBFS with Java 10 (ClassNotFoundException: javax.xml.ws.handler.LogicalMessageContext) Set Bug forwarded-to-address to 'https://github.com/jmock-developers/jmock-library/pull/111'. > End of message, stopping processing here. Please contact me if you need assistance. -- 906370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#909218: nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam)
Processing control commands: > severity -1 serious Bug #909218 [nvidia-xconfig] nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam) Severity set to 'serious' from 'important' > tag -1 sid buster Bug #909218 [nvidia-xconfig] nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam) Added tag(s) buster and sid. -- 909218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 892256
Processing commands for cont...@bugs.debian.org: > tags 892256 + fixed-upstream Bug #892256 [system-config-printer] system-config-printer: Doesn't launch anymore Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 892256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 892256 899187
Processing commands for cont...@bugs.debian.org: > forcemerge 892256 899187 Bug #892256 [system-config-printer] system-config-printer: Doesn't launch anymore Bug #899187 [system-config-printer] system-config-printer: command system-config-printer fails Severity set to 'serious' from 'important' Marked as found in versions system-config-printer/1.5.11-1. Added tag(s) fixed-upstream. Bug #892256 [system-config-printer] system-config-printer: Doesn't launch anymore Marked as found in versions system-config-printer/1.5.11-2. Merged 892256 899187 > thanks Stopping processing here. Please contact me if you need assistance. -- 892256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892256 899187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907663: subdownloader: diff for NMU version 2.0.19-0.1
Control: tag -1 - pending On Wed, Sep 12, 2018 at 05:03:01PM +0300, Adrian Bunk wrote: > I've prepared an NMU for subdownloader (versioned as 2.0.19-0.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I should > cancel it. I'm adopting subdownloader, so I'm doing a full rewamp of the package. I've cancelled the NMU for now, but thanks for doing it! :) I forsee an upload soon, if I manage even today, but given that it's not yet ready I'm removing the pending tag. signature.asc Description: PGP signature
Processed: Re: Bug#907663: subdownloader: diff for NMU version 2.0.19-0.1
Processing control commands: > tag -1 - pending Bug #907663 [subdownloader] subdownloader depends on python-kaa-metadata Removed tag(s) pending. -- 907663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906370: marked as done (jmock2: FTBFS with Java 10 (ClassNotFoundException: javax.xml.ws.handler.LogicalMessageContext))
Your message dated Thu, 20 Sep 2018 15:49:38 + with message-id and subject line Bug#906370: fixed in jmock2 2.8.4-1 has caused the Debian Bug report #906370, regarding jmock2: FTBFS with Java 10 (ClassNotFoundException: javax.xml.ws.handler.LogicalMessageContext) 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.) -- 906370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jmock2 Version: 2.8.3-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i mh_patchpoms -plibjmock2-java --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [... snipped ...] [INFO] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 s - in org.jmock.test.unit.lib.concurrent.DeterministicSchedulerTests [INFO] Running org.jmock.test.unit.lib.concurrent.DeterministicExecutorTests [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 s - in org.jmock.test.unit.lib.concurrent.DeterministicExecutorTests [INFO] Running org.jmock.test.unit.lib.CurrentStateMatcherTests [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s - in org.jmock.test.unit.lib.CurrentStateMatcherTests [INFO] Running org.jmock.test.unit.MockeryTests [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 s - in org.jmock.test.unit.MockeryTests [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] ReturnDefaultCollectionTests.imposterisesUnsupportedMapTypes:72 NoClassDefFound [INFO] [ERROR] Tests run: 302, Failures: 0, Errors: 1, Skipped: 0 [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] jMock 2 Parent 2.8.3 ... SUCCESS [ 0.094 s] [INFO] jMock 2 Test Jar ... SUCCESS [ 0.905 s] [INFO] jMock 2 Core ... FAILURE [ 3.338 s] [INFO] jmock-junit3 ... SKIPPED [INFO] jmock-junit4 ... SKIPPED [INFO] jmock-legacy 2.8.3 . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.568 s [INFO] Finished at: 2018-08-09T10:51:40Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test (default-test) on project jmock: There are test failures. [ERROR] [ERROR] Please refer to /<>/jmock/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please
Bug#909120: camitk FTBFS: tests segfault (Bug #909120)
Hello all,
I tried to reproduce this issue.
Unfortunately I never get the "(SEGFAULT)" output for all tests,
just "(Failed)" for most. But some do really segfault in my amd64 VM.
I think the segfaults are caused by the line "delete component;", that
invalidates the iterator by removing its element from the components vector.
For some reason the iterator contains still the previous pointer
and therefore we try to delete the same pointer twice.
Attached patch tries to change the loop assuming that the
deleted element will always be removed inside the delete operation.
With that patch I do not get any segfault, but still tests
fail for some reason.
Kind regards,
Bernhard
# Here we crash:
(gdb) bt
#0 0x0061 in ?? ()
#1 0x7fffeb32c0d6 in MultiComponent::deleteAllSubComponents
(this=this@entry=0x56d98330) at
./modeling/libraries/pml/MultiComponent.cpp:50
#2 0x7fffeb32c11f in MultiComponent::~MultiComponent (this=0x56d98330,
__in_chrg=) at ./modeling/libraries/pml/MultiComponent.cpp:41
#3 0x7fffeb32c149 in MultiComponent::~MultiComponent (this=0x56d98330,
__in_chrg=) at ./modeling/libraries/pml/MultiComponent.cpp:38
#4 0x7fffeb32ce3a in PhysicalModel::clear (this=this@entry=0x55705ef0)
at ./modeling/libraries/pml/PhysicalModel.cpp:99
#5 0x7fffeb32cf17 in PhysicalModel::~PhysicalModel (this=0x55705ef0,
__in_chrg=) at ./modeling/libraries/pml/PhysicalModel.cpp:68
#6 0x7fffeb32cf59 in PhysicalModel::~PhysicalModel (this=0x55705ef0,
__in_chrg=) at ./modeling/libraries/pml/PhysicalModel.cpp:67
#7 0x7fffeb317a3d in PMLComponent::~PMLComponent (this=0x55660a00,
__in_chrg=) at
./modeling/components/pmlcomponent/PMLComponent.cpp:96
#8 0x7fffeb3185a9 in PMLComponent::~PMLComponent (this=0x55660a00,
__in_chrg=) at
./modeling/components/pmlcomponent/PMLComponent.cpp:93
#9 0x77ec4ad7 in camitk::Application::close(camitk::Component*) () at
./sdk/libraries/core/application/Application.cpp:623
#10 0xbc5c in main () at
./sdk/applications/testcomponents/main.cpp:204
#11 0x76e99b17 in __libc_start_main (main=0xb080 ,
argc=9, argv=0x7fffe398, init=, fini=,
rtld_fini=, stack_end=0x7fffe388) at ../csu/libc-start.c:310
#12 0xc35a in _start () at
./sdk/applications/testcomponents/main.cpp:136
(gdb) list -
46
47 // -- deleteAllSubComponents -
48 void MultiComponent::deleteAllSubComponents() {
49 for (auto& component : components) {
50 delete component;
51 }
52 components.clear();
53 }
# Here the pointer being deleted is removed from the components vector
# and that way invalidating the iterator.
(gdb) bt
#0 MultiComponent::removeSubComponent (c=0x579d70f0, this=0x56d98330)
at ./modeling/libraries/pml/MultiComponent.h:134
#1 Component::removeFromParents() () at
./modeling/libraries/pml/Component.cpp:60
#2 0x7fffeb32c127 in MultiComponent::~MultiComponent (this=0x579d70f0,
__in_chrg=) at ./modeling/libraries/pml/MultiComponent.cpp:44
#3 0x7fffeb32c149 in MultiComponent::~MultiComponent (this=0x579d70f0,
__in_chrg=) at ./modeling/libraries/pml/MultiComponent.cpp:38
#4 0x7fffeb32c0d6 in MultiComponent::deleteAllSubComponents
(this=this@entry=0x56d98330) at
./modeling/libraries/pml/MultiComponent.cpp:50
#5 0x7fffeb32c11f in MultiComponent::~MultiComponent (this=0x56d98330,
__in_chrg=) at ./modeling/libraries/pml/MultiComponent.cpp:41
#6 0x7fffeb32c149 in MultiComponent::~MultiComponent (this=0x56d98330,
__in_chrg=) at ./modeling/libraries/pml/MultiComponent.cpp:38
#7 0x7fffeb32ce3a in PhysicalModel::clear (this=this@entry=0x55705ef0)
at ./modeling/libraries/pml/PhysicalModel.cpp:99
...
(gdb) list modeling/libraries/pml/MultiComponent.h:134
129 }
130 inline void MultiComponent::removeSubComponent(Component* c) {
131 auto it = std::find(components.begin(), components.end(), c);
132 if (it != components.end()) {
133 components.erase(it);
134 c->removeParentMultiComponent(this);
135 }
136 }
From 52f172e553ebddf068b8e35601da5eefd295cf3d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?=
Date: Thu, 20 Sep 2018 17:42:14 +0200
Subject: [PATCH] Make loop safe for removal of elements.
Bug-Debian: https://bugs.debian.org/909120
Forwarded: no
Last-Update: 2018-09-20
---
modeling/libraries/pml/MultiComponent.cpp | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/modeling/libraries/pml/MultiComponent.cpp b/modeling/libraries/pml/MultiComponent.cpp
index 5a3a9ab..3f32d7b 100644
--- a/modeling/libraries/pml/MultiComponent.cpp
+++ b/modeling/libraries/pml/MultiComponent.cpp
@@ -46,8 +46,10 @@ MultiComponent::~MultiComponent() {
// -- deleteAllSubComponents -
void
Bug#909240: marked as done (xorg-server: Unsatisfiable build-depends on libunwind-dev on s390x)
Your message dated Thu, 20 Sep 2018 08:49:27 + with message-id and subject line Bug#909240: fixed in xorg-server 2:1.20.1-3 has caused the Debian Bug report #909240, regarding xorg-server: Unsatisfiable build-depends on libunwind-dev on s390x 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.) -- 909240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-server Version: 2:1.20.1-2 Severity: serious Tags: ftbfs xorg-server no longer builds on s390x since libunwind-dev is not available on that architecture. (This also affects many ports.) https://buildd.debian.org/status/package.php?p=xorg-server https://buildd.debian.org/status/package.php?p=libunwind Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: xorg-server Source-Version: 2:1.20.1-3 We believe that the bug you reported is fixed in the latest version of xorg-server, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xorg-server 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, 20 Sep 2018 11:26:11 +0300 Source: xorg-server Binary: xserver-xorg-core xserver-xorg-core-udeb xserver-xorg-dev xdmx xdmx-tools xnest xvfb xserver-xephyr xserver-common xorg-server-source xwayland xserver-xorg-legacy Architecture: source Version: 2:1.20.1-3 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: xdmx - distributed multihead X server xdmx-tools - Distributed Multihead X tools xnest - Nested X server xorg-server-source - Xorg X server - source files xserver-common - common files used by various X servers xserver-xephyr - nested X server xserver-xorg-core - Xorg X server - core server xserver-xorg-core-udeb - Xorg X server - core server (udeb) xserver-xorg-dev - Xorg X server - development files xserver-xorg-legacy - setuid root Xorg server wrapper xvfb - Virtual Framebuffer 'fake' X server xwayland - Xwayland X server Closes: 909240 Changes: xorg-server (2:1.20.1-3) unstable; urgency=medium . * xvfb-run*: Update default resolution and bitdepth to match upstream defaults. * Limit libunwind to archs that actually have it. (Closes: #909240) Checksums-Sha1: 47fefe1928fd85641748b239343928897f4017bf 4155 xorg-server_1.20.1-3.dsc 3ea179179c13b163925afdd5c89bfb217f010019 149339 xorg-server_1.20.1-3.diff.gz 171c5d64e9c4dd65e82ec1940fbf509c5c6efdbc 8415 xorg-server_1.20.1-3_source.buildinfo Checksums-Sha256: f853f7ce369df072dc224e8ce7ca726bf4962b8250caabeda1188f6ceca2806d 4155 xorg-server_1.20.1-3.dsc ffc8f004f4ba5c3ec9504c54dcd0f92e252cc5b4f4c7266cb209802ba40d8c22 149339 xorg-server_1.20.1-3.diff.gz 98b3c19a07c80a2c85bf48389b859bd375a06d97cad6bf1913e2c150ee8ad0dc 8415 xorg-server_1.20.1-3_source.buildinfo Files: bb7fbc644a172fa4dd95b368afcaccbd 4155 x11 optional xorg-server_1.20.1-3.dsc ba03af5f435fcb7563a4c03bdeb33302 149339 x11 optional xorg-server_1.20.1-3.diff.gz 66b13b26ba5455de74fe349e6c93320e 8415 x11 optional xorg-server_1.20.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlujWbkACgkQy3AxZaiJ hNyNQA/9HjuYW2ehs9UKFrECd7Z7oqTifODAD32QUg1wv3OvjotiNWa+1qW95a4h 4ZZs+B6NBhTAi+bnxv3BtiLcK3etyXU/8yzyI0HGGwylLIlDjf6ih4fEzrW6cuZU jim+HyATxkk/GXLWX4EkV/02Es/7Ct48A1/Da6k049H+h9VscRn8w45+1CkKGfEb Ef2Zyriu8e3nB7GuVDXdSmaSuRIUTzh3fvR9ZofIuGFRmRUXkw5WpDW9xnpGrY87 ScRFFdDX1LoP3SK7mOiKUQIiKXhJyUa3VIGsCw1PXwWEVy+ANKBTGy4/6HVrbDrx rGfV5A0NiQIpEpHJmEwsr7eIIWN9VGtURNrAk5pwe8XyEkpz3QpskcTKz5tl0oDx +SWaHlfifsIxhXtDgcYWq3HSu6IkjgHFNghzbRUuwabYI/z5aSHUIQQxw3V6OQKp feXW5XK5bhDVS860War2CaMG0KNRPAXoG7brQt8Z42HfQI4VPRfdnCk/OuHiWNf9 BSa2SsGGha4VxnWXhmRoDQHa/j8ulUMUwfHzz+KJmFD4VAtmS0TQVwDUgp4037vV 0MwtiPaePzwChK6f5Gp141+HfUOcrhnWc2wJt1eWa81A3gNbFVs8LAF+Uzwc6NER mkTFTi7yu0mV22m6M4wewceWT3wNobtwV1/AH4VGurIFsAmXNMs= =jeAg -END PGP SIGNATURE End Message ---
Bug#909244: kobodeluxe not playable - immediately pauses and can't be resumed
Package: kobodeluxe Version: 0.5.1-9 Severity: grave Justification: renders package unusable Trying to start a game in kobodeluxe results in a "PAUSED" game, with no possibility to resume it. The only way out is to press Esc and exit the game. Steps to reproduce: - start kobodl - press shift or space three times I tried this under gdm3/gnome3/wayland, lightdm/xfce4/Xorg and lightdb/openbox/Xorg so it seems to be independent of the graphical environment. Also tried with a new user account without success and after removing apparmor and rebooting. -- dam -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kobodeluxe depends on: ii kobodeluxe-data 0.5.1-9 ii libc62.27-6 ii libgcc1 1:8.2.0-7 ii libsdl-image1.2 1.2.12-8 ii libsdl1.2debian 1.2.15+dfsg2-2 ii libstdc++6 8.2.0-7 kobodeluxe recommends no packages. kobodeluxe suggests no packages. -- no debconf information
Bug#908486: marked as done (mozjs60: FTBFS on mips64el: error: no matching function for call to [...]: candidate expects 1 argument, 0 provided)
Your message dated Thu, 20 Sep 2018 10:20:36 +
with message-id
and subject line Bug#908486: fixed in mozjs60 60.2.1-1
has caused the Debian Bug report #908486,
regarding mozjs60: FTBFS on mips64el: error: no matching function for call to
[...]: candidate expects 1 argument, 0 provided
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.)
--
908486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs60
Version: 60.1.0-1
Severity: serious
Tags: ftbfs help
Justification: fails to build from source
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el
mozjs60 fails to build on mips64el. It looks as though some
mips64-specific code might need updating for API changes or similar?
We can't upgrade gjs to a version that uses mozjs60 until either this is
fixed somehow, or gjs and its dependencies (notably GNOME Shell) are
removed from mips64el.
/<>/js/src/jit/mips64/LIR-mips64.h: In constructor
'js::jit::LUnbox::LUnbox(const js::jit::LAllocation&)':
/<>/js/src/jit/mips64/LIR-mips64.h:18:47: error: no matching
function for call to 'js::jit::LInstructionHelper<1, 1,
0>::LInstructionHelper()'
explicit LUnbox(const LAllocation& input) {
^
In file included from /<>/js/src/jit/JitFrames-inl.h:12,
from /<>/js/src/vm/Interpreter.cpp:52:
/<>/js/src/jit/LIR.h:1176:14: note: candidate:
'js::jit::LInstructionHelper::LInstructionHelper(js::jit::LNode::Opcode) [with long unsigned int Defs
= 1; long unsigned int Operands = 1; long unsigned int Temps = 0]'
explicit LInstructionHelper(LNode::Opcode opcode)
^~
/<>/js/src/jit/LIR.h:1176:14: note: candidate expects 1
argument, 0 provided
/<>/js/src/jit/LIR.h:1171:7: note: candidate:
'js::jit::LInstructionHelper<1, 1,
0>::LInstructionHelper(js::jit::LInstructionHelper<1, 1, 0>&&)'
class LInstructionHelper : public
details::LInstructionFixedDefsTempsHelper
^~
/<>/js/src/jit/LIR.h:1171:7: note: candidate expects 1 argument,
0 provided
In file included from /<>/js/src/jit/LIR.h:2028,
from /<>/js/src/jit/JitFrames-inl.h:12,
from /<>/js/src/vm/Interpreter.cpp:52:
/<>/js/src/jit/mips64/LIR-mips64.h: In constructor
'js::jit::LDivOrModI64::LDivOrModI64(const js::jit::LAllocation&, const
js::jit::LAllocation&, const js::jit::LDefinition&)':
/<>/js/src/jit/mips64/LIR-mips64.h:54:91: error: no matching
function for call to 'js::jit::LBinaryMath<1>::LBinaryMath()'
LDivOrModI64(const LAllocation& lhs, const LAllocation& rhs, const
LDefinition& temp) {
^
In file included from /<>/js/src/jit/LIR.h:2012,
from /<>/js/src/jit/JitFrames-inl.h:12,
from /<>/js/src/vm/Interpreter.cpp:52:
/<>/js/src/jit/shared/LIR-shared.h:46:14: note: candidate:
'js::jit::LBinaryMath::LBinaryMath(js::jit::LNode::Opcode)
[with long unsigned int Temps = 1; long unsigned int ExtraUses = 0]'
explicit LBinaryMath(LNode::Opcode opcode)
^~~
/<>/js/src/jit/shared/LIR-shared.h:46:14: note: candidate
expects 1 argument, 0 provided
/<>/js/src/jit/shared/LIR-shared.h:43:7: note: candidate:
'js::jit::LBinaryMath<1>::LBinaryMath(js::jit::LBinaryMath<1>&&)'
class LBinaryMath : public LInstructionHelper<1, 2 + ExtraUses, Temps>
^~~
/<>/js/src/jit/shared/LIR-shared.h:43:7: note: candidate expects
1 argument, 0 provided
[... and more errors like those ...]
Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: mozjs60
Source-Version: 60.2.1-1
We believe that the bug you reported is fixed in the latest version of
mozjs60, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie (supplier of updated mozjs60 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 Sep 2018 09:02:56 +0100
Bug#907364: marked as done (mozjs60: tests non262/Date/timeclip.js, test262/language/types/number/S8.5_A2.1.js, test262/language/types/number/S8.5_A2.2.js fail on i386)
Your message dated Thu, 20 Sep 2018 10:20:36 +
with message-id
and subject line Bug#907363: fixed in mozjs60 60.2.1-1
has caused the Debian Bug report #907363,
regarding mozjs60: tests non262/Date/timeclip.js,
test262/language/types/number/S8.5_A2.1.js,
test262/language/types/number/S8.5_A2.2.js fail on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
907363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mozjs52
Version: 60.1.0-1
Severity: normal
I ran a test build of spidermonkey 60.1.0-1 package on the Ubuntu PPA builders
and had the following test failures on i386 build
## non262/Date/timeclip.js: rc = 3, run time = 0.048487
747197: TimeClip behavior for very large numbers
non262/Date/timeclip.js:19:1 Error: Assertion failed: got true, expected false
Stack:
@non262/Date/timeclip.js:19:1
TEST-UNEXPECTED-FAIL | non262/Date/timeclip.js | (args: "") [0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test":
"non262/Date/timeclip.js", "thread": "main", "time": 1535249793.461725}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source":
"jstests", "status": "FAIL", "test": "non262/Date/timeclip.js", "thread":
"main", "time": 1535249793.510212}
## test262/language/types/number/S8.5_A2.1.js: rc = 3, run time = 0.04355
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 -
1/65536.0; var z = x + y; var d = z - x; d === 0. Actual: 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.1.js | (args: "")
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test":
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time":
1535249586.113185}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source":
"jstests", "status": "FAIL", "test":
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time":
1535249586.156735}
## test262/language/types/number/S8.5_A2.2.js: rc = 3, run time = 0.044356
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 -
1/65536.0; var z = x + y; var d = z - x; d !== 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.2.js | (args: "")
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test":
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time":
1535249586.0153189}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source":
"jstests", "status": "FAIL", "test":
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time":
1535249586.059675}
Full logs
https://launchpadlibrarian.net/385368114/buildlog_ubuntu-cosmic-i386.mozjs60_60.1.0-ppa1_BUILDING.txt.gz
--- End Message ---
--- Begin Message ---
Source: mozjs60
Source-Version: 60.2.1-1
We believe that the bug you reported is fixed in the latest version of
mozjs60, 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 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie (supplier of updated mozjs60 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 Sep 2018 09:02:56 +0100
Source: mozjs60
Binary: libmozjs-60-0 libmozjs-60-dev
Architecture: source
Version: 60.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Simon McVittie
Description:
libmozjs-60-0 - SpiderMonkey JavaScript library
libmozjs-60-dev - SpiderMonkey JavaScript library - development headers
Closes: 905825 907363 908481 908485 908486 908554
Changes:
mozjs60 (60.2.1-1) unstable; urgency=medium
.
* Team upload
* New upstream release
- d/copyright: Update
* d/p/tests-Add-the-ability-to-skip-tests-according-to-dpkg-arc.patch:
Add patch to allow tests to be skipped or marked as random (flaky) or
fails (expected failure) according to dpkg-architecture variables
* Build with system ICU library (Closes: #908554)
- Leave the patches and workarounds in place, but gate them behind
a WITH_SYSTEM_ICU Make variable, to facilitate backporting
as mentioned on
Bug#908485: marked as done (mozjs60: FTBFS on mipsel: error: static assertion failed: MIPS32 jit only supports FR=0 fpu mode)
Your message dated Thu, 20 Sep 2018 10:20:36 + with message-id and subject line Bug#908485: fixed in mozjs60 60.2.1-1 has caused the Debian Bug report #908485, regarding mozjs60: FTBFS on mipsel: error: static assertion failed: MIPS32 jit only supports FR=0 fpu mode 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.) -- 908485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mozjs60 Version: 60.1.0-1 Severity: serious Tags: ftbfs help Justification: fails to build from source X-Debbugs-Cc: debian-m...@lists.debian.org User: debian-m...@lists.debian.org Usertags: mipsel mozjs60 fails to build on mipsel: /<>/js/src/jit/mips32/Architecture-mips32.h:55:26: error: static assertion failed: MIPS32 jit only supports FR=0 fpu mode. static_assert(__mips_fpr == 32, "MIPS32 jit only supports FR=0 fpu mode."); ^ We can't upgrade gjs to a version that uses mozjs60 until either this is fixed somehow, or gjs and its dependencies (notably GNOME Shell) are removed from mipsel. smcv --- End Message --- --- Begin Message --- Source: mozjs60 Source-Version: 60.2.1-1 We believe that the bug you reported is fixed in the latest version of mozjs60, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated mozjs60 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 Sep 2018 09:02:56 +0100 Source: mozjs60 Binary: libmozjs-60-0 libmozjs-60-dev Architecture: source Version: 60.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Description: libmozjs-60-0 - SpiderMonkey JavaScript library libmozjs-60-dev - SpiderMonkey JavaScript library - development headers Closes: 905825 907363 908481 908485 908486 908554 Changes: mozjs60 (60.2.1-1) unstable; urgency=medium . * Team upload * New upstream release - d/copyright: Update * d/p/tests-Add-the-ability-to-skip-tests-according-to-dpkg-arc.patch: Add patch to allow tests to be skipped or marked as random (flaky) or fails (expected failure) according to dpkg-architecture variables * Build with system ICU library (Closes: #908554) - Leave the patches and workarounds in place, but gate them behind a WITH_SYSTEM_ICU Make variable, to facilitate backporting as mentioned on #878362 - d/p/Skip-some-i18n-tests-because-we-are-now-using-system-ICU.patch: Skip tests that fail with the system ICU library * Don't ignore overall test results on any architecture. We can ignore individual failing tests instead. * d/p/tests-Use-DEB_HOST_ARCH_BITS-to-skip-some-tests-on-64-bit.patch: Generalize the previous d/p/tests-For-tests-that-are-skipped-on-64-bit-mips64-is-also.patch to skip the affected tests on every 64-bit architecture, including alpha and sparc64 (Closes: #905825) * d/p/tests-Expect-some-floating-point-tests-to-fail-on-i386.patch: Mark some floating point tests as expected to fail on any-i386 due to our use of the legacy i387 FPU, which has different rounding behaviour (Closes: #907363) * d/p/tests-Expect-a-test-to-fail-on-armel.patch: Expect a test involving floating-point NaN to fail on ARM softfloat (Closes: #908481) * d/p/Bug-1444303-MIPS-Fix-build-failures-after-Bug-1425580-par.patch, d/p/Bug-1444834-MIPS-Stubout-MacroAssembler-speculationBarrie.patch: Add patches from upstream via firefox-esr which hopefully fix FTBFS on mips64el * Disable JIT (ion) on mipsel and mips64el as well as mips. It appears that the patches above are only enough to compile, but not work, on mips64el (many tests fail). (Closes: #908486) - This also avoids a compile-time static assertion failure affecting mipsel (Closes: #908485) * Add another source-is-missing Lintian override * d/copyright: Remove more unused licenses * d/copyright: Add public domain license grants * d/watch: Update
Bug#908481: marked as done (mozjs60: FTBFS on armel: test262/built-ins/TypedArray/prototype/fill/fill-values-conversion-operations-consistent-nan.js: Test262Error: NaN value #2 (Testing with Float32Ar
Your message dated Thu, 20 Sep 2018 10:20:36 + with message-id and subject line Bug#908481: fixed in mozjs60 60.2.1-1 has caused the Debian Bug report #908481, regarding mozjs60: FTBFS on armel: test262/built-ins/TypedArray/prototype/fill/fill-values-conversion-operations-consistent-nan.js: Test262Error: NaN value #2 (Testing with Float32Array.) 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.) -- 908481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mozjs60 Version: 60.1.0-1 Severity: serious Tags: help X-Debbugs-Cc: debian-...@lists.debian.org User: debian-...@lists.debian.org Usertags: armel In mozjs60 (Spidermonkey 60, the standalone version of the Mozilla JavaScript interpreter corresponding to Firefox 60.x ESR), the test test262/built-ins/TypedArray/prototype/fill/fill-values-conversion-operations-consistent-nan.js fails on armel. The point of this test appears to be to check that a FloatArray filled with a particular encoding of NaN (Not-a-Number) using fill() has the same binary representation as a FloatArray that was explicitly initialized. This works for 0/0 and for Infinity/Infinity, but for some reason not for -(0/0). If this can't be fixed soon, we should skip this test or ignore the test failure and downgrade it to non-RC. smcv --- End Message --- --- Begin Message --- Source: mozjs60 Source-Version: 60.2.1-1 We believe that the bug you reported is fixed in the latest version of mozjs60, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated mozjs60 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 Sep 2018 09:02:56 +0100 Source: mozjs60 Binary: libmozjs-60-0 libmozjs-60-dev Architecture: source Version: 60.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Description: libmozjs-60-0 - SpiderMonkey JavaScript library libmozjs-60-dev - SpiderMonkey JavaScript library - development headers Closes: 905825 907363 908481 908485 908486 908554 Changes: mozjs60 (60.2.1-1) unstable; urgency=medium . * Team upload * New upstream release - d/copyright: Update * d/p/tests-Add-the-ability-to-skip-tests-according-to-dpkg-arc.patch: Add patch to allow tests to be skipped or marked as random (flaky) or fails (expected failure) according to dpkg-architecture variables * Build with system ICU library (Closes: #908554) - Leave the patches and workarounds in place, but gate them behind a WITH_SYSTEM_ICU Make variable, to facilitate backporting as mentioned on #878362 - d/p/Skip-some-i18n-tests-because-we-are-now-using-system-ICU.patch: Skip tests that fail with the system ICU library * Don't ignore overall test results on any architecture. We can ignore individual failing tests instead. * d/p/tests-Use-DEB_HOST_ARCH_BITS-to-skip-some-tests-on-64-bit.patch: Generalize the previous d/p/tests-For-tests-that-are-skipped-on-64-bit-mips64-is-also.patch to skip the affected tests on every 64-bit architecture, including alpha and sparc64 (Closes: #905825) * d/p/tests-Expect-some-floating-point-tests-to-fail-on-i386.patch: Mark some floating point tests as expected to fail on any-i386 due to our use of the legacy i387 FPU, which has different rounding behaviour (Closes: #907363) * d/p/tests-Expect-a-test-to-fail-on-armel.patch: Expect a test involving floating-point NaN to fail on ARM softfloat (Closes: #908481) * d/p/Bug-1444303-MIPS-Fix-build-failures-after-Bug-1425580-par.patch, d/p/Bug-1444834-MIPS-Stubout-MacroAssembler-speculationBarrie.patch: Add patches from upstream via firefox-esr which hopefully fix FTBFS on mips64el * Disable JIT (ion) on mipsel and mips64el as well as mips. It appears that the patches above are only enough to compile, but not work, on mips64el (many tests fail). (Closes: #908486) - This also
Bug#907363: marked as done (mozjs60: tests non262/Date/timeclip.js, test262/language/types/number/S8.5_A2.1.js, test262/language/types/number/S8.5_A2.2.js fail on i386)
Your message dated Thu, 20 Sep 2018 10:20:36 +
with message-id
and subject line Bug#907363: fixed in mozjs60 60.2.1-1
has caused the Debian Bug report #907363,
regarding mozjs60: tests non262/Date/timeclip.js,
test262/language/types/number/S8.5_A2.1.js,
test262/language/types/number/S8.5_A2.2.js fail on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
907363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mozjs52
Version: 60.1.0-1
Severity: normal
I ran a test build of Spidermonkey 60.1.0-1 on the Ubuntu ppa builders and had
the following test failures:
## non262/Date/timeclip.js: rc = 3, run time = 0.048487
747197: TimeClip behavior for very large numbers
non262/Date/timeclip.js:19:1 Error: Assertion failed: got true, expected false
Stack:
@non262/Date/timeclip.js:19:1
TEST-UNEXPECTED-FAIL | non262/Date/timeclip.js | (args: "") [0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test":
"non262/Date/timeclip.js", "thread": "main", "time": 1535249793.461725}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source":
"jstests", "status": "FAIL", "test": "non262/Date/timeclip.js", "thread":
"main", "time": 1535249793.510212}
## test262/language/types/number/S8.5_A2.1.js: rc = 3, run time = 0.04355
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 -
1/65536.0; var z = x + y; var d = z - x; d === 0. Actual: 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.1.js | (args: "")
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test":
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time":
1535249586.113185}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source":
"jstests", "status": "FAIL", "test":
"test262/language/types/number/S8.5_A2.1.js", "thread": "main", "time":
1535249586.156735}
## test262/language/types/number/S8.5_A2.2.js: rc = 3, run time = 0.044356
uncaught exception: Test262Error: #1: var x = 9007199254740994.0; var y = 1.0 -
1/65536.0; var z = x + y; var d = z - x; d !== 2
TEST-UNEXPECTED-FAIL | test262/language/types/number/S8.5_A2.2.js | (args: "")
[0.0 s]
{"action": "test_start", "pid": 20462, "source": "jstests", "test":
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time":
1535249586.0153189}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 20462, "source":
"jstests", "status": "FAIL", "test":
"test262/language/types/number/S8.5_A2.2.js", "thread": "main", "time":
1535249586.059675}
full logs:
https://launchpadlibrarian.net/385368114/buildlog_ubuntu-cosmic-i386.mozjs60_60.1.0-ppa1_BUILDING.txt.gz
upstream bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1486328
--- End Message ---
--- Begin Message ---
Source: mozjs60
Source-Version: 60.2.1-1
We believe that the bug you reported is fixed in the latest version of
mozjs60, 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 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie (supplier of updated mozjs60 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 Sep 2018 09:02:56 +0100
Source: mozjs60
Binary: libmozjs-60-0 libmozjs-60-dev
Architecture: source
Version: 60.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Simon McVittie
Description:
libmozjs-60-0 - SpiderMonkey JavaScript library
libmozjs-60-dev - SpiderMonkey JavaScript library - development headers
Closes: 905825 907363 908481 908485 908486 908554
Changes:
mozjs60 (60.2.1-1) unstable; urgency=medium
.
* Team upload
* New upstream release
- d/copyright: Update
* d/p/tests-Add-the-ability-to-skip-tests-according-to-dpkg-arc.patch:
Add patch to allow tests to be skipped or marked as random (flaky) or
fails (expected failure) according to dpkg-architecture variables
* Build with system ICU library (Closes: #908554)
- Leave the patches and workarounds in place, but gate them behind
a WITH_SYSTEM_ICU Make
Bug#907663: marked as done (subdownloader depends on python-kaa-metadata)
Your message dated Thu, 20 Sep 2018 16:49:12 + with message-id and subject line Bug#907663: fixed in subdownloader 2.0.19-1 has caused the Debian Bug report #907663, regarding subdownloader depends on python-kaa-metadata 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.) -- 907663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: subdownloader Version: 2.0.18-2.1 Severity: serious Tags: fixed-upstream Control: block -1 by 892751 subdownloader is the last reverse dependency of python-kaa-metadata which has already been removed from testing. Upstream version 2.0.19 supports pymediainfo as fallback. --- End Message --- --- Begin Message --- Source: subdownloader Source-Version: 2.0.19-1 We believe that the bug you reported is fixed in the latest version of subdownloader, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated subdownloader 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, 20 Sep 2018 18:13:26 +0200 Source: subdownloader Binary: subdownloader Architecture: source Version: 2.0.19-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Mattia Rizzolo Description: subdownloader - subtitle download/upload manager for video files Closes: 907663 Changes: subdownloader (2.0.19-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Remove trailing whitespaces . [ SVN → Git migration ] * Move the repository from SVN to Git. * Change the hosting from alioth.d.o to salsa.d.o. * Configure gbp to use DEP-14 branch names. . [ Mattia Rizzolo ] * New upstream version 2.0.19. * Run wrap-and-sort -ast. * d/control: + Add myself to Uploaders. + Bump debhlper compat level to 11. Also use the new debhelper-compat(=11) notation and drop d/compat. + Set Rules-Requires-Root:no. + Drop versioned dependency on python >= 2.6, the implied >= 2.7 is enough. + Bump Standards-Version to 4.2.1. + Update Homepage to the new location on GitHub. * d/control: Update dependencies: + Build-Depends: pyqt4-dev-tools → pyqt5-dev-tools. + Depends: - python-kaa-metadata → python-pymediainfo. Closes: #907663 - drop now unneeded dependency on python-crypto. - new dependency on python-progressbar. + Recommends: - python-qt4 → python-pyqt5. - New recommended packages: python-argcomplete, python-langdetect. * d/rules: + Rewrite using the dh sequencer. + Don't install a basically empty upstream changelog file. * d/subdownloader.menu: drop menu file, deprecated as of Policy v3.9.8. * d/copyright: + Rewrite using copyright-format 1.0. + Add myself for debian/* + Update. * d/watch: Rewrite pointing to GitHub. * d/patches: + follow-opensubtitles-download-link: remove, included upstream. + encoding-issue.diff: temporary disable. Checksums-Sha1: 57a40ae53b4eecff64b8afe9a5a428fb2b47b975 2127 subdownloader_2.0.19-1.dsc 4691dd7bd5578a963f8e99b97271e2cdec6121ba 1257110 subdownloader_2.0.19.orig.tar.gz cbd1335b47ef49369f0c62497ae87eaa14222973 25716 subdownloader_2.0.19-1.debian.tar.xz 9d39c03815cfe1cda0641eed40677118d3ce5f3f 9279 subdownloader_2.0.19-1_amd64.buildinfo Checksums-Sha256: c16fbb837a57e049730a9e070d3d69afd547fd45029631d9ed46dcaf66d407b7 2127 subdownloader_2.0.19-1.dsc cf3cc2842add043df647a31f4ba0831a6d0c4bfeec0573fcde1e8b24dffd0bb4 1257110 subdownloader_2.0.19.orig.tar.gz 353b834cf20e4bf1f2bb492234bc948245f25533056c0ee5ac0f67f50a8e301b 25716 subdownloader_2.0.19-1.debian.tar.xz 69a9b054065f9f8a521c6fa545e78df97db565786d318f43826f20e5127199e6 9279 subdownloader_2.0.19-1_amd64.buildinfo Files: d5f0ea07c771e085e47481c0e2a5affb 2127 utils optional subdownloader_2.0.19-1.dsc 0579bd29c8527be49a7aacb21b0a8cd6 1257110 utils optional subdownloader_2.0.19.orig.tar.gz 57c18a3bb8f19b9f2b82022584284d5c 25716 utils optional
Processed: forcibly merging 909000 909225
Processing commands for cont...@bugs.debian.org: > forcemerge 909000 909225 Bug #909000 [enigmail] Enigmail 2.0 needed in Stretch after Thunderbird 60 upload Bug #909001 [enigmail] enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1) Bug #909081 [enigmail] [enigmail] impossible install enigmail Bug #909225 [enigmail] enigmail cannot be installed on stretch Severity set to 'grave' from 'important' Marked as found in versions enigmail/2:1.9.9-1~deb9u1. Bug #909001 [enigmail] enigmail: Enigmail get uninstalled while upgrading thunderbird (60.0-3~deb9u1) Bug #909081 [enigmail] [enigmail] impossible install enigmail Merged 909000 909001 909081 909225 > thanks Stopping processing here. Please contact me if you need assistance. -- 909000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000 909001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909001 909081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909081 909225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 909263 is serious
Processing commands for cont...@bugs.debian.org: > severity 909263 serious Bug #909263 [postfixadmin] Postfixadmin 3.0 to 3.2 upgrade: SQLite upgrade fails Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 909263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #909155 in apt marked as pending
Processing control commands: > tag -1 pending Bug #909155 [apt] apt-cache show multiple packages produces invalid output Added tag(s) pending. -- 909155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909155: Bug #909155 in apt marked as pending
Control: tag -1 pending Hello, Bug #909155 in apt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/apt-team/apt/commit/6f1d622c84b3b7f821683bf69b8fcdb6dcf272a2 Deal with descriptions embedded in displayed record correctly The implementation of "apt-cache show" (not "apt show") incorrectly resets the currently used parser if the record itself and the description to show come from the same file (as it is the case if no Translation-* files are available e.g. after debootstrap). The code is more complex than you would hope to support some rather unusual setups involving Descriptions and their translations as tested for by ./test-bug-712435-missing-descriptions as otherwise this could be a one-line change. Regression-Of: bf53f39c9a0221b67074053ed36fc502d5a0 Closes: #909155 (this message was generated automatically) -- Greetings https://bugs.debian.org/909155
Processed: found 909215 in 4.1.3-1
Processing commands for cont...@bugs.debian.org:
> found 909215 4.1.3-1
Bug #909215 {Done: Patrick Matthäi } [glusterfs]
glusterfs: Multiple security issues
There is no source info for the package 'glusterfs' at version '4.1.3-1' with
architecture ''
Unable to make a source version for version '4.1.3-1'
Marked as found in versions 4.1.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
909215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
