Bug#969577: marked as done (caml-crush: FTBFS with GCC 10: multiple definition of `my_arch')
Your message dated Fri, 02 Oct 2020 05:48:24 + with message-id and subject line Bug#969577: fixed in caml-crush 1.0.10-4 has caused the Debian Bug report #969577, regarding caml-crush: FTBFS with GCC 10: multiple definition of `my_arch' 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.) -- 969577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caml-crush Version: 1.0.9-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) caml-crush fails to build with GCC 10: | gcc -Wl,-z,relro,-z,now -shared -Wl,-soname,libp11clienttcpssl.so -fPIC -o libp11client"".so pkcs11_rpc_xdr.o pkcs11_rpc_clnt.o modwrap_"".o modwrap_crpc.o modwrap_crpc_ssl.o -lpthread -lssl -Wl,-z,relro; | /usr/bin/ld: modwrap_crpc.o:(.bss+0xa8): multiple definition of `my_arch'; modwrap_.o:(.bss+0xa8): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0xb0): multiple definition of `peer_arch'; modwrap_.o:(.bss+0xb0): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x8): multiple definition of `is_Blocking'; modwrap_.o:(.bss+0x0): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x20): multiple definition of `mutex'; modwrap_.o:(.bss+0x20): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x60): multiple definition of `linkedlist_mutex'; modwrap_.o:(.bss+0x60): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x88): multiple definition of `op_type'; modwrap_.o:(.bss+0x88): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x90): multiple definition of `request_data'; modwrap_.o:(.bss+0x90): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x98): multiple definition of `ssl'; modwrap_.o:(.bss+0x98): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0xa0): multiple definition of `ctx'; modwrap_.o:(.bss+0xa0): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x98): multiple definition of `ssl'; modwrap_.o:(.bss+0x98): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0xa0): multiple definition of `ctx'; modwrap_.o:(.bss+0xa0): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x18): multiple definition of `is_Blocking'; modwrap_.o:(.bss+0x0): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x20): multiple definition of `mutex'; modwrap_.o:(.bss+0x20): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x60): multiple definition of `linkedlist_mutex'; modwrap_.o:(.bss+0x60): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x88): multiple definition of `op_type'; modwrap_.o:(.bss+0x88): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x90): multiple definition of `request_data'; modwrap_.o:(.bss+0x90): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0xa8): multiple definition of `my_arch'; modwrap_.o:(.bss+0xa8): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0xb0): multiple definition of `peer_arch'; modwrap_.o:(.bss+0xb0): first defined here | collect2: error: ld returned 1 exit status | make[3]: *** [Makefile:39: crpc] Error 1 | make[3]: Leaving directory '/<>/build-SERVER/src/client-lib' | make[2]: *** [Makefile:19: client] Error 2 | make[2]: Leaving directory '/<>/build-SERVER' | dh_auto_build: error: cd build-SERVER && make -j1 CUSTOM_SONAME=libp11clienttcpssl.so returned exit code 2 | make[1]: *** [debian/rules:45: override_dh_auto_build-SERVER] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:53: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: caml-crush Source-Version: 1.0.10-4 Done: Thomas Calderon We believe that the bug you reported is fixed in the latest version of caml-crush, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Calderon (supplier of updated caml-crush 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-
Bug#969609: [Pkg-rust-maintainers] Bug#969609: Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe
Steve Langasek: > Ximin, > > On Tue, Sep 08, 2020 at 09:23:49PM +0100, Ximin Luo wrote: >> You keep filing these same bugs. I have told you this many times before >> already: this is just how rust packaging works, Britney's migration policy >> already prevents these packages from reaching Debian Testing, so there is >> no problem, no users are affected. > >> You filing these bug reports accomplishes nothing, except delay & annoy >> other Rust packagers who forget to close these pointless bugs, thereby >> unnecessarily blocking any fixed packages from actually reaching Debian >> Testing. Oftentimes the fix is also not to update the package itself, but >> to upload another package. Due to the idiosyncracies of the BTS, not >> everyone knows how to close these bugs correctly (notfound -1 $version) >> and it will result in further delays. > >> Please stop filing these bug reports, they only create extra unnecessary >> work for other people, and make Debian worse for users, by slowing down >> the stream of fixes. Britney already prevents Testing migration. > > It is not credible to me that this is "just how rust packaging works". The > bugs I am filing are against packages that have been uninstallable in > unstable for more than 4 months. The missing dependencies are not in the > NEW queue, and there are no ITP bugs filed for them. There is no reason to > believe, without filing these bugs, that anyone on the rust packaging team > is doing anything about these missing dependencies. > Why is it not credible? I am one of the main members of the team, and created about 80% of the current process. I am telling you it is simply how it works. If you want an in-depth description, see https://github.com/kpcyrd/cargo-debstatus/issues/2. In summary, it is because the Rust dependency system encodes complex dependency relationships in a more efficient way than the Debian dependency system, meaning the typical Rust package expresses more complex dependencies than most other Debian packages. But you can get this type of situation with other languages too, especially those with bootstrap loops. The only difference is in Rust it's much more common. (The NEW queue is another unresolved issue that is blocking Rust packaging - we have a policy disagreement with the FTP team and nobody has had time to resolve it. That is why things might not be on the NEW queue.) At the end of the day, it doesn't matter if people don't do anything about these missing dependencies, because *the britney migration script prevents migration to testing*. For the packages that matter, i.e. that need to be migrated to testing (& eventually stable), members of this team are forced to fix these issues anyway, and we have a documented process for doing this: https://salsa.debian.org/rust-team/debcargo-conf/-/blob/master/RELEASE.rst > And filing bug reports in the Debian BTS is the standard way in Debian to > document bugs in packages. > > And it is unacceptable that Debian maintainers don't know how to operate the > Debian BTS. > Most Debian Rust Team members are not regular Debian maintainers. And the Debian BTS user interface is really unintuitive. So I can't reasonably consider it "unacceptable", we have to be realistic regarding volunteer on-boarding. > So no, I will not stop filing bugs against RC-buggy packages that the Rust > maintainers are clearly not taking care of. If you don't want bug reports, > you have the option to stop uploading packages that are RC buggy from the > moment they're accepted into the archive. > I am explaining to you why the normal Debian process is inadequate and causes more work for everyone in this case. Please trust your fellow maintainers more on matters on which they have more expertise. After all of my explanations, what benefit do you suppose these bugs are giving?? You filing bug reports is not going to magically give people more free time to fix them; when they have the free time these problems are automatically and forcibly solved as part of our regular process. The bugs do not help this one bit. Best Ximin -- GPG: ed25519/56034877E1F87C35 https://github.com/infinity0/pubkeys.git
Bug#970883: marked as done (gjs: should not migrate to testing until GNOME Shell 3.38 is ready)
Your message dated Thu, 1 Oct 2020 22:55:42 +0100 with message-id <20201001215542.ga315...@espresso.pseudorandom.co.uk> and subject line Re: Bug#970883: gjs: should not migrate to testing until GNOME Shell 3.38 is ready has caused the Debian Bug report #970883, regarding gjs: should not migrate to testing until GNOME Shell 3.38 is ready 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.) -- 970883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gjs Version: 1.66.0-1 Severity: serious Justification: maintainer says so Tags: sid gjs 1.66.0 uses mozjs78, instead of the old mozj68 used in 1.64.x. Nobody is likely to have tested gjs 1.66 with GNOME 3.36 very thoroughly, if at all, so we should not let gjs migrate to testing until we're ready for GNOME 3.38 to migrate. I'm opening this RC bug to stop that happening. (I do not have any actual evidence that it doesn't work, but I don't think the GNOME team either upstream or in Debian is prepared to support partial upgrades for more than a very brief transitional period. We can add Breaks if we find that there are concrete things that don't work.) We can close this bug when the core GNOME packages (-shell, -session, -settings-daemon, gdm3, -control-center, -desktop and gsettings-desktop-schemas) are ready in unstable. smcv --- End Message --- --- Begin Message --- If I'm reading the excuses correctly, everything should be ready to migrate, so I'm closing this now. Worst-case we'll get gjs arriving in testing a day or two sooner than gnome-shell. smcv--- End Message ---
Bug#969141: marked as done (websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19)
Your message dated Thu, 01 Oct 2020 21:33:47 + with message-id and subject line Bug#969141: fixed in doxygen 1.8.20-3 has caused the Debian Bug report #969141, regarding websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19 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.) -- 969141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: websocketpp Severity: normal Dear Maintainer, while rebuilding the build dependencies of doxygen with the upcoming doxygen 1.8.19 (https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial) this package FTBFS. I attach the buildlogs: - buildlogs/websocketpp_0.8.2-1 (with doxygen 1.8.19) - buildlogs_recheck/websocketpp_0.8.2-1 (with doxygen 1.8.18) In both buildlogs doxygen reports: error: fixed-compilation-database: Error while opening fixed database: No such file or directory json-compilation-database: Error while opening JSON database: No such file or directory using clang compilation database path of: "(null)" error: /usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found [clang] error: /usr/include/sched.h:29:10: fatal error: 'stddef.h' file not found [clang] This then causes a segmentation fault with 1.8.19. Also doxygen is parsing the files readme.md, changelog.md and roadmap.md which is incorrect. You should fix the Doxyfile INPUT key and remove them (doxygen should only parse source code). The segmentation fault may well be a doxygen issue, but fixing the Doxyfile of websocketpp is the first step required to pinpoint the root issue. Paolo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: doxygen Source-Version: 1.8.20-3 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of doxygen, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated doxygen 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, 01 Oct 2020 23:23:51 +0200 Source: doxygen Architecture: source Version: 1.8.20-3 Distribution: unstable Urgency: medium Maintainer: Paolo Greppi Changed-By: Gianfranco Costamagna Closes: 969141 Changes: doxygen (1.8.20-3) unstable; urgency=medium . * Team upload (salsa.d.o namespace) * debian/patches/d067baf495d0415283ce724ad32cb9a08dc17c83.patch: - cherry-pick upstream fix for crash during parse with CLANG helper (Closes: #969141) Checksums-Sha1: d79d3d39af78cf8faa8b46eb160e68ec8ee65a57 2728 doxygen_1.8.20-3.dsc 49c0a4f80201e3e9b9d0408b785404e006ad89f8 29688 doxygen_1.8.20-3.debian.tar.xz ff9be745b7ff6b162dc0f3da07ecdb61e2979e66 12896 doxygen_1.8.20-3_source.buildinfo Checksums-Sha256: 9431dd4f438312267ce6a82d36d2f1e7e150586167d9cefe24e1ea6e24143a5f 2728 doxygen_1.8.20-3.dsc a5c97fa4e2c7930ed7fd1f3acd2ad7b8d46181fe3e611348681fb1d4b2c0776b 29688 doxygen_1.8.20-3.debian.tar.xz 0121f8e423a79144f9d3ad1430669f9b428c1e4a495730e1710603634270129a 12896 doxygen_1.8.20-3_source.buildinfo Files: cccfc97a44f24bc2efdb72c3eb13535f 2728 devel optional doxygen_1.8.20-3.dsc 56a5249e498566c753f411fb5b86a23e 29688 devel optional doxygen_1.8.20-3.debian.tar.xz a9014cdf9402e5ce91daf5363708d481 12896 devel optional doxygen_1.8.20-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl92ScIACgkQ808JdE6f XdnCCw//fhVtRxt4M+JSrsRtezfevwSaW9gMfZKXQXRADNgZzGjxc8OGLn02tahT gmGWums07DOldLXfWDck8DlV0oXNOPe0T3ppUfBLMP+iPlhKBxqRinhF+OB+JpgM jNOuOHqweu1F71mw2j3vEwfdsnj+NNZUpBOReTnxkNS7CZXVx0gOoLriAoHYHDzk
Bug#969141: websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19
control: tags -1 pending Since it is collaborative maintained, I just uploaded and committed the patch on git thanks! G.
Processed: Re: websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19
Processing control commands: > tags -1 pending Bug #969141 [doxygen] websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19 Added tag(s) pending. -- 969141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970341: marked as done (rampler: autopkgtest failure on arm64:)
Your message dated Thu, 01 Oct 2020 20:50:59 + with message-id and subject line Bug#970341: fixed in rampler 1.1.1-3 has caused the Debian Bug report #970341, regarding rampler: autopkgtest failure on arm64: 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.) -- 970341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rampler Version: 1.1.1-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package rampler, great. However, it fails on arm64. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The test could be a bit more verbose? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rampler https://ci.debian.net/data/autopkgtest/testing/amd64/r/rampler/6794192/log.gz autopkgtest [03:14:35]: test run-unit-test: [--- [93m[1mPreparation[0m [92m[1mPassed[0m [93m[1mTest 1[0m autopkgtest [03:14:35]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: rampler Source-Version: 1.1.1-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of rampler, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated rampler 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, 01 Oct 2020 23:14:59 +0530 Source: rampler Architecture: source Version: 1.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 970341 Changes: rampler (1.1.1-3) unstable; urgency=medium . * Team upload. * Add patch to fix tests on arm64 (Closes: #970341) Checksums-Sha1: a98e1ec85d44b8ef535343979d8e3dc201a42a28 2041 rampler_1.1.1-3.dsc e17b5c793251ff6de87cfa18a0a32804503be2e6 4472 rampler_1.1.1-3.debian.tar.xz 9cd0bc991d039190a6c22fc0562e202bdc5195ad 6642 rampler_1.1.1-3_amd64.buildinfo Checksums-Sha256: a90ed539c7d91c8a4250a679df7fdd011036136e71c967f38e0b99d7fae11d3c 2041 rampler_1.1.1-3.dsc fb2650d9e8e668c75995fbc45aeb3568789e8640bc00ea8ce6d1386cf124077b 4472 rampler_1.1.1-3.debian.tar.xz 7339c0947e51741cce0999844c90a62631b8aab199db4221bb62bba665ae3689 6642 rampler_1.1.1-3_amd64.buildinfo Files: 884a6f1dd3eefb8d7dddbae111385a89 2041 science optional rampler_1.1.1-3.dsc 73d913e5ef13cde0126fd85a8ac16df3 4472 science optional rampler_1.1.1-3.debian.tar.xz 2f23ddd7129c4c8d6ea1365e403a57e6 6642 science optional rampler_1.1.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl92O2YUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafHlOBAAs5uc2RriT9U9R2pBToCu7q8KYr1+ 81E1FmbQGNdvLmW6nv9KIwPhH3y4EKPLitFI+0RppEIy9MriswCPMucKjgptqu0Z UETxN2yOVDV04aaBn3K+KOD9NWXP04oDlwM7pAA5v22yqtvxvf4CHzeP8ctJdVT0 eUE/BIdiTbTPa9HYH94l78vD2WiYORC1GM+mTZBXJWGzWW5Tlck4x4uRvupUv0bL VAeJMngEFDKiarwLF3g3ujBpfT6zJYqp41YM3Z8RPMkbMPwSc3Ohsnd66lP7ShJh cL/INNhyzph1iXKjcoiNas8QXiFS+Bkj7wRIxDgwiCm4me/9hORGith9igN1LkY1 rVVvTZCHPF2DtIWYIExdkRXoaaAq2xc0uObMqAYG+JtnomQjpwsCuT/MI6mcvV1r s1YDog5Fucm+iNYsMcdySGuvDIeb9lhhoSeuj8eDr89BiOdSqCcGVXCLo/vXhUrX 7PjujvIz+OH9nDMHfAOyXlqAC2+ymW7iIkE3+8fYhk6S3ffdlhx35uAC2q4n1qEs m+2SBQGaoKAipxbtPIRx2hiiRlLX57jEu/fqPCGcYWtbzpJ9Jvo4fBDfWKsaC2tN peYSr1FRGrt5rvoYf65734rdTIgmB0Eh+UizyCtPI3x+qKlym7zKg/e2j8joT0aS nZbU728D75Dg5o8= =OsZ2 -END PGP SIGNATURE End Message ---
Bug#962596: Any updates?
Hey all, Is there a timeline on this? Still present in 20200601~deb10u1. Cheers, Amin
Bug#964190: marked as done (subliminal (stretch) is not working with current providers)
Your message dated Thu, 1 Oct 2020 22:08:39 +0200
with message-id <20201001200839.GA861363@pisco.westfalen.local>
and subject line Re: subliminal (stretch) is not working with current providers
has caused the Debian Bug report #964190,
regarding subliminal (stretch) is not working with current providers
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.)
--
964190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: subliminal
Version: 1.1.1-2
Severity: grave
Justification: renders package unusable
See also #961338 for the sid version of this package → requires update to
actual version 2.1
The package is missing in buster/bullseye.
The stretch version is also not working any more.
The following error output is emitted:
Traceback (most recent call last):
File "/usr/bin/subliminal", line 9, in
load_entry_point('subliminal==1.1.1', 'console_scripts', 'subliminal')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2793,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2411,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2417,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/subliminal/__init__.py", line 10, in
from .api import (ProviderPool, check_video, provider_manager,
download_best_subtitles, download_subtitles,
File "/usr/lib/python3/dist-packages/subliminal/api.py", line 13, in
from .subtitle import compute_score, get_subtitle_path
File "/usr/lib/python3/dist-packages/subliminal/subtitle.py", line 7, in
from guessit.matchtree import MatchTree
ModuleNotFoundError: No module named 'guessit.matchtree'
-- System Information:
Debian Release: 10.4
APT prefers stable
APT policy: (1000, 'stable'), (600, 'stable-updates'), (600, 'stable'), (500,
'oldstable-updates'), (500, 'oldstable'), (200, 'testing'), (101, 'unstable'),
(10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE=de_DE:de:en_US:en (charmap=UTF-8) (ignored:
LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages subliminal depends on:
ii python3 3.7.3-1
ii python3-subliminal 1.1.1-2
subliminal recommends no packages.
subliminal suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Jul 03, 2020 at 01:40:04PM +0200, H.-Dirk Schmitt wrote:
> Package: subliminal
> Version: 1.1.1-2
> Severity: grave
> Justification: renders package unusable
>
>
> See also #961338 for the sid version of this package → requires update to
> actual version 2.1
> The package is missing in buster/bullseye.
> The stretch version is also not working any more.
Thanks for the report, but Stretch is now in LTS mode for security fixes
only and such bugs no longer get fixed there. There are also no further
point relases for Stretch, so dropping the package is not an option either.
As such, closing the bug.
Cheers,
Moritz--- End Message ---
Bug#971556: golang-github-dgrijalva-jwt-go: CVE-2020-26160
Source: golang-github-dgrijalva-jwt-go
Version: 3.2.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for golang-github-dgrijalva-jwt-go.
CVE-2020-26160[0]:
| jwt-go before 4.0.0-preview1 allows attackers to bypass intended
| access restrictions in situations with []string{} for m["aud"] (which
| is allowed by the specification). Because the type assertion fails, ""
| is the value of aud. This is a security problem if the JWT token is
| presented to a service that lacks its own audience check.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2020-26160
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26160
[1] https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
Bug#957206: EXTERNAL: Re: Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)
[Please excuse the corporate-ese that comes with my email] Hi Andreas, We are readying another release. I actually have the time to work on the Debian package again. I will take care of it. Thanks, Amul -Original Message- From: Andreas Tille Sent: Thursday, October 01, 2020 9:52 AM To: 957206-mainto...@bugs.debian.org; Shah, Amul Subject: EXTERNAL: Re: Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10) Hi again On Fri, 7 Aug 2020 14:55:21 +, Shah, Amul wrote: > Thanks for the ping. We have a fix, just not enough time in a day. :( I think we should upload that fix in the near future. Kind regards Andreas. The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity
Thanks, Scott, it worked! https://buildd.debian.org/status/package.php?p=mrpt=sid JL
Bug#970763: bug report acknowledged
Dear Ryan, thank you for the bug report: wminput does segfault when it is called. I tried to modify the source to get rid of the build warnings, which in fact should be reported as errors. It appears to be a tough task, since many warnings are about unapropriate pointer casts, due to the mix of python2 and python3 concepts. I shall try to get some help from the last upstream developer who touched this software in source form. Best regards, Georges. -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature
Bug#971521: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI
Paul Gevers writes: > So, vanish stopped providing vanishabi-11.0 and vanish-modules needs > to be fixed, otherwise vanish is not allowed to migrate to testing > (until vanish-modules is removed from testing). vanish-modules in > unstable is broken now, we don't want that to happen in testing. Hello, The varnish-modules package fails to build due to the build erroring out on deprecated functions. The varnishabi bump should have happened in 6.5.0 but the 6.5.1 was released soon after to only bump the varnish version. Example from the build of varnish-modules against varnish 6.5.1: , | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/varnish -I../src/foreign -Wall -Werror -Wall -Wno-format-y2k -Wstrict-prototypes -Wmissing-prototypes -Werror=missing-field-initializers -Wpointer-arith -Wreturn-type -Wwrite-strings -Wcast-qual -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Wnested-externs -Wextra -Wno-sign-compare -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c vcc_saintmode_if.c -fPIC -DPIC -o .libs/vcc_saintmode_if.o | vmod_bodyaccess.c: In function ‘vmod_hash_req_body’: | vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated [-Werror=deprecated-declarations] | 205 | VSB_delete(vsb); | | ^~ | In file included from /usr/include/varnish/cache/cache_varnishd.h:36, | from vmod_bodyaccess.c:37: | /usr/include/varnish/vsb.h:79:8: note: declared here |79 | void VSB_delete(struct vsb *) v_deprecated_; | |^~ ` The upstream changelog for varnish 6.5.0 says: ,[ https://github.com/varnishcache/varnish-cache/blob/master/doc/changes.rst ] | * VSB support for dynamic vs. static allocations has been changed: | | For dynamic allocations use: | | VSB_new_auto() + VSB_destroy() | | For preexisting buffers use: | | VSB_init() + VSB_fini() | | VSB_new() + VSB_delete() are now deprecated. ` Varnish-modules uses VSB_new_auto() and VSB_delete() in vmod_bodyaccess and vmod_saintmode. The long term is obviously for varnish-modules to use one of the new VSB_ functions for allocations. I'm not sure what is the best short term fix. Any suggestions? My C skills are abysmal, so while I could probably get it to build, I'd not be comfortable with pushing the result... -- Stig Sandbeck Mathisen signature.asc Description: PGP signature
Processed: [bts-link] source package src:gemma
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gemma > # 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 #952190 (http://bugs.debian.org/952190) > # Bug title: gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit > code 2 > # * https://github.com/genetics-statistics/GEMMA/issues/216 > # * remote status changed: open -> closed > # * closed upstream > tags 952190 + fixed-upstream Bug #952190 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2 Added tag(s) fixed-upstream. > usertags 952190 - status-open Usertags were: status-open. Usertags are now: . > usertags 952190 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 952190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971541: astroquery: autopkgtest failure on armhf
Source: astroquery
Version: 0.4.1+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Autopkgtests have recently started running on armhf, and there
astroquery fails [1].
I've copied what I hope is the relevant part of the log below.
I've marked this as a regression as 0.3.9+dfsg-1 passes in Debian
stable, and 0.4+dfsg-3 passes in Ubuntu.
Regards
Graham
[1] https://ci.debian.net/packages/a/astroquery/testing/armhf/
=== FAILURES ===
_ test_all_tables[toi-query34] _
self =
cols = [,
,
, , , ...]
def _convert_vals(self, cols):
for col in cols:
# If a specific dtype was specified for a column, then use that
# to set the defaults, otherwise use the generic defaults.
default_converters = ([convert_numpy(col.dtype)] if col.dtype
else self.default_converters)
# If the user supplied a specific convert then that takes
precedence over defaults
converters = self.converters.get(col.name, default_converters)
col.converters = self._validate_and_copy(col, converters)
# Catch the last error in order to provide additional information
# in case all attempts at column conversion fail. The initial
# value of of last_error will apply if no converters are defined
# and the first col.converters[0] access raises IndexError.
last_err = 'no converters defined'
while not hasattr(col, 'data'):
try:
converter_func, converter_type = col.converters[0]
if not issubclass(converter_type, col.type):
raise TypeError('converter type does not match
column type')
> col.data = converter_func(col.str_vals)
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:960:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
vals = ['9048843364125']
def generic_converter(vals):
> return numpy.array(vals, numpy_type)
E OverflowError: Python int too large to convert to C long
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:904: OverflowError
During handling of the above exception, another exception occurred:
patch_get = <_pytest.monkeypatch.MonkeyPatch object at 0xf299fb08>
table = 'toi', query = {'where': 'toi=256.01'}
@pytest.mark.filterwarnings("error")
@pytest.mark.parametrize("table,query", ALL_TABLES)
def test_all_tables(patch_get, table, query):
> data = NasaExoplanetArchive.query_criteria(table, select="*", **query)
/usr/lib/python3/dist-packages/astroquery/nasa_exoplanet_archive/tests/test_nasa_exoplanet_archive.py:188:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/astroquery/utils/class_or_instance.py:25: in f
return self.fn(obj, *args, **kwds)
/usr/lib/python3/dist-packages/astroquery/utils/process_asyncs.py:29:
in newmethod
result = self._parse_result(response, verbose=verbose)
/usr/lib/python3/dist-packages/astroquery/nasa_exoplanet_archive/core.py:471:
in _parse_result
data = ascii.read(text, format="ipac", fast_reader=False,
converters=CONVERTERS)
/usr/lib/python3/dist-packages/astropy/io/ascii/ui.py:323: in read
dat = reader.read(table)
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:1209: in read
table = self.outputter(cols, self.meta)
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:990: in __call__
self._convert_vals(cols)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
cols = [,
,
, , , ...]
def _convert_vals(self, cols):
for col in cols:
# If a specific dtype was specified for a column, then use that
# to set the defaults, otherwise use the generic defaults.
default_converters = ([convert_numpy(col.dtype)] if col.dtype
else self.default_converters)
# If the user supplied a specific convert then that takes
precedence over defaults
converters = self.converters.get(col.name, default_converters)
col.converters = self._validate_and_copy(col, converters)
# Catch the last error in order to provide additional information
# in case all attempts at column conversion fail. The initial
# value of of last_error will apply if no converters are defined
# and the first col.converters[0] access raises IndexError.
last_err = 'no converters defined'
while not hasattr(col, 'data'):
try:
converter_func, converter_type = col.converters[0]
if not issubclass(converter_type, col.type):
Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)
Hi again On Fri, 7 Aug 2020 14:55:21 +, Shah, Amul wrote: > Thanks for the ping. We have a fix, just not enough time in a day. :( I think we should upload that fix in the near future. Kind regards Andreas. -- http://fam-tille.de
Bug#971135: marked as done (user-mode-linux: FTBFS: build-dependency not installable: linux-source-5.7)
Your message dated Thu, 01 Oct 2020 13:49:39 + with message-id and subject line Bug#971135: fixed in user-mode-linux 5.8um1 has caused the Debian Bug report #971135, regarding user-mode-linux: FTBFS: build-dependency not installable: linux-source-5.7 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.) -- 971135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: user-mode-linux Version: 5.7um1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>> 12.0.0), quilt, linux-source-5.7, > docbook-to-man, xz-utils, m4, kmod, libvdeplug2-dev, libpcap-dev, bc, dpkg > (>= 1.16.2), libssl-dev, bison, flex, gcc-multilib, build-essential, fakeroot > Filtered Build-Depends: debhelper (>> 12.0.0), quilt, linux-source-5.7, > docbook-to-man, xz-utils, m4, kmod, libvdeplug2-dev, libpcap-dev, bc, dpkg > (>= 1.16.2), libssl-dev, bison, flex, gcc-multilib, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [464 B] > Get:5 copy:/<>/apt_archive ./ Packages [549 B] > Fetched 1970 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: linux-source-5.7 but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/09/26/user-mode-linux_5.7um1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: user-mode-linux Source-Version: 5.8um1 Done: Ritesh Raj Sarraf We believe that the bug you reported is fixed in the latest version of user-mode-linux, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ritesh Raj Sarraf (supplier of updated user-mode-linux 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, 01 Oct 2020 16:54:44 +0530 Source: user-mode-linux Architecture: source Version: 5.8um1 Distribution: unstable Urgency: medium Maintainer: User Mode Linux Maintainers Changed-By: Ritesh Raj Sarraf Closes: 971135 Changes: user-mode-linux (5.8um1) unstable; urgency=medium . * [b7db191] Prepare for Linux 5.8 (Closes: #971135) * [9ca8d98] Update kernel configs for Linux 5.8 * [3d34593] Disable BPFILTER for architecture i386 - For reasons unclear, having BPFILTER enabled in the config makes kbuild think the config is incomplete.
Bug#957737: FTBFS Fixes
Hi, I wanted to let you know that I have today looked into the very same FTBFS and submitted the fixes upstream. https://lists.quagga.net/pipermail/quagga-dev/2020-October/033390.html https://lists.quagga.net/pipermail/quagga-dev/2020-October/033391.html With those two gcc-10 builds work. [1] contains an (Ubuntu) Test build with these applied. You might wait for upstream to integrate or apply them as-is to fix the FTFBS. Kind Regards, Christian [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4291/+packages -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
Bug#971217: marked as done (python-poppler-qt5: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip")
Your message dated Thu, 01 Oct 2020 13:04:05 +
with message-id
and subject line Bug#971217: fixed in python-poppler-qt5 0.75.0-2
has caused the Debian Bug report #971217,
regarding python-poppler-qt5: FTBFS: sip: Unable to find file
"QtCore/QtCoremod.sip"
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.)
--
971217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-poppler-qt5
Version: 0.75.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-poppler-qt5
> dpkg-buildpackage: info: source version 0.75.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Anthony Fok
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.8_poppler-qt5/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-poppler-qt5 using existing
> ./python-poppler-qt5_0.75.0.orig.tar.gz
> dpkg-source: info: building python-poppler-qt5 in
> python-poppler-qt5_0.75.0-1.debian.tar.xz
> dpkg-source: info: building python-poppler-qt5 in
> python-poppler-qt5_0.75.0-1.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_ext
> building 'popplerqt5' extension
> /usr/bin/sip -I /usr/share/sip -t POPPLER_V0_74_0 -c
> build/temp.linux-x86_64-3.8 -b build/temp.linux-x86_64-3.8/poppler-qt5.sbf -I
> /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_14_0 -t WS_X11 poppler-qt5.sip
> sip: Unable to find file "QtCore/QtCoremod.sip"
> error: command '/usr/bin/sip' failed with exit status 1
> E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3 setup.py build
> dh_auto_build: error: pybuild --build -i python{version} -p 3.8 returned exit
> code 13
> make: *** [debian/rules:8: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/python-poppler-qt5_0.75.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-poppler-qt5
Source-Version: 0.75.0-2
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
python-poppler-qt5, 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 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated python-poppler-qt5
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, 01 Oct 2020 15:49:01 +0300
Source: python-poppler-qt5
Architecture: source
Version: 0.75.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Dmitry Shachnev
Closes: 964131
Bug#971522: marked as done (parsnp: autopkgtest arm64 regression: raxmlHPC-PTHREADS not in system path!)
Your message dated Thu, 01 Oct 2020 12:20:05 + with message-id and subject line Bug#971522: fixed in parsnp 1.5.3+dfsg-2 has caused the Debian Bug report #971522, regarding parsnp: autopkgtest arm64 regression: raxmlHPC-PTHREADS not in system path! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parsnp Version: 1.5.3+dfsg-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of parsnp the autopkgtest of parsnp fails in testing on arm64 when that autopkgtest is run with the binary packages of parsnp from unstable. It passes when run with only packages from testing. In tabular form: passfail parsnp from testing1.5.3+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=parsnp https://ci.debian.net/data/autopkgtest/testing/arm64/p/parsnp/7238498/log.gz autopkgtest [21:17:40]: test run-unit-test: [--- [93m[1mTest 1: With GenBank Annotations[0m |--Parsnp 1.5.3--| For detailed documentation please see --> http://harvest.readthedocs.org/en/latest 13:17:40 - [1;31mCRITICAL[0m - raxmlHPC-PTHREADS not in system path! autopkgtest [21:17:40]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: parsnp Source-Version: 1.5.3+dfsg-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of parsnp, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated parsnp 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, 01 Oct 2020 17:23:41 +0530 Source: parsnp Architecture: source Version: 1.5.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 971522 Changes: parsnp (1.5.3+dfsg-2) unstable; urgency=medium . * Team Upload. * Use raxmlHPC instead of raxmlHPC-PTHREADS (Closes: #971522) Checksums-Sha1: 16058a3386df1dbaea62b52338d2730325e4d82b 2075 parsnp_1.5.3+dfsg-2.dsc b66e93b437d713760c4349e2c740be3a9df477cb 7584 parsnp_1.5.3+dfsg-2.debian.tar.xz 1704e73c6b27f7552090a0fa1dc01393fd0c8bb7 6642 parsnp_1.5.3+dfsg-2_amd64.buildinfo Checksums-Sha256: ee6604ba99cac7d4ac878f0f78718dac6e1cc2933c4ea0fa104c5720b21d61a4 2075 parsnp_1.5.3+dfsg-2.dsc 2eb5224053d5f11afb4d25e8cdef1d0d7d0ce01259b48ea2367c1c46f57db577 7584 parsnp_1.5.3+dfsg-2.debian.tar.xz 6e3ba72d6a2cbb3fceb6a31a4b2d44373bf4e379c6b8b1f614a7e0ecf365be04 6642 parsnp_1.5.3+dfsg-2_amd64.buildinfo Files: 980ba05f9aa5529e95a53e55628907f8 2075 science optional parsnp_1.5.3+dfsg-2.dsc 594c1f75f545b1051ad0346ab95ab8f9 7584 science optional parsnp_1.5.3+dfsg-2.debian.tar.xz 348fa1cfcc722bf7dafa836e39963ad0 6642 science optional parsnp_1.5.3+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl91xpsUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafFL+hAAi0gsY4yfMBTZpCOvCn6KDT8Y3fVx PrEUklgUZQ8NmNXefW0VTZ9tF2Ulr+wFwQebfwO8exUgerwJEXiozjgdolZinCuy JCB/gva1Bl9YoibT53v6LKyf+d8EWQJrE0W33iPn77LWJ6QtmYlrvy4/yZobgtbD jLEJF84uiIeEFT0YlPANSsodIUI1ucg9xVJRVE3m0BM63KHAdchQYu/xJXC4aWwY gZqngyn6oVfQcSYD9vlp+TWNhXMQfVQMcuZbVi55KgHu3MBhdGNntZIDrc4M/lTD Ci7r9t8JqfwyfeDJ/BeNKGMBX7+/M8NqeCttmO7HgSiT5p/Gvk41YurL9cRP82jI PGyVm81m0MkMNMFuky89JWd2wLPoTNlHyXPikiyaEf8LKqNhaGra5Bk3Uxu3UAtN vNZ+TRwUcwWRBJSCRsLn/0VN5n8+gyulzqIhckLCTBwlrab08fVrV2PuYFsSwCx4
Bug#971522: parsnp: autopkgtest arm64 regression: raxmlHPC-PTHREADS not in system path!
Hi Nilesh, On Thu, Oct 01, 2020 at 10:06:22AM +0200, Paul Gevers wrote: > autopkgtest [21:17:40]: test run-unit-test: [--- > [93m[1mTest 1: With GenBank Annotations[0m > |--Parsnp 1.5.3--| > For detailed documentation please see --> > http://harvest.readthedocs.org/en/latest > 13:17:40 - [1;31mCRITICAL[0m - raxmlHPC-PTHREADS not in system path! > autopkgtest [21:17:40]: test run-unit-test: ---] I think we should just call raxml instead of raxmlHPC-PTHREADS. The wrapper raxml **SHOULD** simply detect the best performing executable and call this. However, I'd be really if some additional pair of eyeballs would check this wrapper. So if you are at it and might test this - please have a look whether on amd64 architecture the final executable raxmlHPC-PTHREADS will be called when raxml is used in the command from parsnp. Kind regards Andreas. -- http://fam-tille.de
Bug#971519: [Pkg-javascript-devel] Bug#971519: Bug#971519: node-locate-character: Rebuild from sources
On Thu, Oct 1, 2020 at 09:44, Xavier wrote:
Upstream source are really missing, only repacked files are available.
Relevant bug: https://github.com/Rich-Harris/locate-character/issues/6
Attaching the diff between the two dist tarballs. Only addition seems
to be that of typings and switching from gitlab.com to github.com.
The missing commits seems to be present in the old repo at
https://gitlab.com/Rich-Harris/locate-character/-/commits/master
So we can just take the git snapshot from old repo.
diff -Nuar locate-character-2.0.1/CHANGELOG.md locate-character-2.0.5/CHANGELOG.md
--- locate-character-2.0.1/CHANGELOG.md 2017-05-21 20:21:43.0 +
+++ locate-character-2.0.5/CHANGELOG.md 2018-01-14 15:08:18.0 +
@@ -1,5 +1,17 @@
# locate-character changelog
+## 2.0.5
+
+* Fix incorrect `pkg.repository`
+
+## 2.0.4
+
+* Fix typings
+
+## 2.0.2-3
+
+* Add typings to package
+
## 2.0.1
* Port to TypeScript, add typings (no change in functionality)
diff -Nuar locate-character-2.0.1/dist/types/index.d.ts locate-character-2.0.5/dist/types/index.d.ts
--- locate-character-2.0.1/dist/types/index.d.ts 1970-01-01 00:00:00.0 +
+++ locate-character-2.0.5/dist/types/index.d.ts 2018-01-14 15:08:37.0 +
@@ -0,0 +1,17 @@
+export interface Options {
+offsetLine?: number;
+offsetColumn?: number;
+startIndex?: number;
+}
+export interface Location {
+line: number;
+column: number;
+character: number;
+}
+export declare function getLocator(source: string, options?: Options): {
+(search: string, startIndex?: number): Location;
+(search: number): Location;
+};
+declare function locate(source: string, search: string, options?: Options): Location;
+declare function locate(source: string, search: number, options?: Options): Location;
+export { locate };
diff -Nuar locate-character-2.0.1/package.json locate-character-2.0.5/package.json
--- locate-character-2.0.1/package.json 2017-05-21 20:21:58.0 +
+++ locate-character-2.0.5/package.json 2018-01-14 15:08:22.0 +
@@ -1,6 +1,6 @@
{
"name": "locate-character",
- "version": "2.0.1",
+ "version": "2.0.5",
"description": "Get the line and column number of a specific character in a string",
"main": "dist/locate-character.umd.js",
"jsnext:main": "dist/locate-character.es.js",
@@ -8,17 +8,15 @@
"scripts": {
"test": "mocha",
"pretest": "npm run build",
-"build": "rollup -c",
+"build": "rollup -c && tsc",
"prepublish": "npm test"
},
"files": [
-"dist",
+"dist/*.js",
+"dist/**/*.d.ts",
"README.md"
],
- "repository": {
-"type": "git",
-"url": "git+https://gitlab.com/Rich-Harris/locate-character.git;
- },
+ "repository": "Rich-Harris/locate-character",
"keywords": [
"string",
"character",
@@ -30,14 +28,14 @@
"author": "Rich Harris",
"license": "MIT",
"bugs": {
-"url": "https://gitlab.com/Rich-Harris/locate-character/issues;
+"url": "https://github.com/Rich-Harris/locate-character/issues;
},
- "homepage": "https://gitlab.com/Rich-Harris/locate-character#README;,
+ "homepage": "https://github.com/Rich-Harris/locate-character#README;,
"devDependencies": {
"mocha": "^3.0.1",
"rollup": "^0.34.7",
"rollup-plugin-typescript": "^0.8.1",
"typescript": "^2.3.2"
},
- "types": "./types.d.ts"
+ "types": "./dist/types/index.d.ts"
}
Bug#971518: Acknowledgement (libsnmp30: Depends on missing package)
Forgot this information. apt policy libsnmp30 libsnmp30: Installed: 5.7.3+dfsg-5+b2 Candidate: 5.7.3+dfsg-5+deb10u1 Version table: 5.7.3+dfsg-5+deb10u1 990 990 http://ftp.de.debian.org/debian unstable/main amd64 Packages *** 5.7.3+dfsg-5+b2 100 100 /var/lib/dpkg/status -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc https://pgp.key-server.io/pks/lookup?search=0xD3C9A00E mir datanom net https://pgp.key-server.io/pks/lookup?search=0xE501F51C mir miras org https://pgp.key-server.io/pks/lookup?search=0xE3E80917 -- /usr/games/fortune -es says: Lady Luck brings added income today. Lady friend takes it away tonight. pgpNOmLtBZ5e7.pgp Description: OpenPGP digital signature
Bug#971100: marked as done (dolfinx: FTBFS: unsatisfiable build-dependency: python3-llvmlite (< 0.34) but 0.34.0-1 is to be installed)
Your message dated Thu, 01 Oct 2020 18:37:13 +0800 with message-id <4091130f2559afdbad60d9981d186...@debian.org> and subject line fixed 971100 0.51.2-1 has caused the Debian Bug report #971100, regarding dolfinx: FTBFS: unsatisfiable build-dependency: python3-llvmlite (< 0.34) but 0.34.0-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dolfinx Version: 2019.2.0~git20200723.696fbc0-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake (>= 3.5), debhelper-compat (= 13), dh-python, > gfortran, chrpath, libboost-chrono-dev, libboost-dev (>= 1.56), > libboost-filesystem-dev, libboost-iostreams-dev, libboost-math-dev, > libboost-mpi-dev, libboost-program-options-dev, libboost-serialization-dev, > libboost-thread-dev, libboost-timer-dev, libeigen3-dev (>= 3.2.90), > libhdf5-mpi-dev, libsuitesparse-dev, libscotch-dev, libxml2-dev, > mpi-default-dev, libpetsc-real-dev (>= 3.7), libpetsc-complex-dev, > libslepc-real-dev (>= 3.7), libslepc-complex-dev, pybind11-dev (>= 2.2.0), > python3-setuptools, python3-petsc4py-real, python3-petsc4py-complex, > python3-slepc4py-real, python3-slepc4py-complex, pkg-config, python3-all-dev, > python3-cffi, python3-pkg-resources, python3-ffcx (>= 2019.2), python3-ffcx > (<< 2019.3), python3-ufl, python3-mpi4py, python3-numba, python3-numpy, > python3-ply, python3-sphinx, build-essential, fakeroot, doxygen, > libjs-mathjax, libjs-modernizr, python3-sphinx-rtd-theme > Filtered Build-Depends: cmake (>= 3.5), debhelper-compat (= 13), dh-python, > gfortran, chrpath, libboost-chrono-dev, libboost-dev (>= 1.56), > libboost-filesystem-dev, libboost-iostreams-dev, libboost-math-dev, > libboost-mpi-dev, libboost-program-options-dev, libboost-serialization-dev, > libboost-thread-dev, libboost-timer-dev, libeigen3-dev (>= 3.2.90), > libhdf5-mpi-dev, libsuitesparse-dev, libscotch-dev, libxml2-dev, > mpi-default-dev, libpetsc-real-dev (>= 3.7), libpetsc-complex-dev, > libslepc-real-dev (>= 3.7), libslepc-complex-dev, pybind11-dev (>= 2.2.0), > python3-setuptools, python3-petsc4py-real, python3-petsc4py-complex, > python3-slepc4py-real, python3-slepc4py-complex, pkg-config, python3-all-dev, > python3-cffi, python3-pkg-resources, python3-ffcx (>= 2019.2), python3-ffcx > (<< 2019.3), python3-ufl, python3-mpi4py, python3-numba, python3-numpy, > python3-ply, python3-sphinx, build-essential, fakeroot, doxygen, > libjs-mathjax, libjs-modernizr, python3-sphinx-rtd-theme > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [708 B] > Get:5 copy:/<>/apt_archive ./ Packages [782 B] > Fetched 2453 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-numba : Depends: python3-llvmlite (< 0.34) but 0.34.0-1 is to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/09/26/dolfinx_2019.2.0~git20200723.696fbc0-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild:
Bug#971518: libsnmp30: Depends on missing package
Package: libsnmp30 Version: 5.7.3+dfsg-5+b2 Severity: serious Justification: Policy 7.2 Dear Maintainer, sudo apt install libsnmp30 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsnmp30 : Depends: libperl5.28 (>= 5.28.0) but it is not installable E: Unable to correct problems, you have held broken packages. apt policy libperl5.28 libperl5.28: Installed: (none) Candidate: (none) Version table: dpkg --get-selections |grep libperl5 libperl5.30:amd64 install libperl5.30:i386install -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsnmp30 depends on: ii libc6 2.31-3 ii libpci3 1:3.7.0-3 ii libperl5.30 5.30.3-4 ii libsensors5 1:3.6.0-2 ii libsnmp-base 5.9+dfsg-3 ii libssl1.1 1.1.1g-1 ii libwrap0 7.6.q-30 libsnmp30 recommends no packages. libsnmp30 suggests no packages. -- no debconf information This mail was virus scanned and spam checked before delivery. This mail is also DKIM signed. See header dkim-signature.
Bug#966942: Fix is upstream
Hi,
I was facing the same issue in Ubuntu just recently and found that the
upstream fix [1] does address this issue. I wanted to let you know so
you can get this fixed as well a bit more easily - because from just
knowing the error this is a head-scratcher.
When you have fixed this you most likely will still fail as the
current build produces a slightly off-sized efi rom for the build, the
attached patch on top of [1] will fix that as well.
[2] has an Ubuntu build with it applied which makes it work with
gcc-10.2 + glibc 2.32 + binutils 2.35.1 again.
[1]:
https://github.com/ipxe/ipxe/commit/f982a712979619dbae2c6e0d741757e2ce94be11
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4289/+packages
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
From cd9c3f19ab148e5fdf39190e99ee79780632fdb6 Mon Sep 17 00:00:00 2001
From: Christian Ehrhardt
Date: Thu, 1 Oct 2020 11:00:20 +0200
Subject: [PATCH] d/util/geniso: fix FTBFS due to rounding issues
In some cases there can be rounding issues on the efi content to image
size. In those cases the build will fail with the image not being big
enough.
$ debian/util/geniso src/bin-combined/ipxe.iso src/bin-i386-pcbios/ipxe.lkrn \
src/bin-x86_64-efi/ipxe.efi
Disk full
Avoid this size-off-by-one by adding 1 block to the requested size.
Signed-off-by: Christian Ehrhardt
---
debian/util/geniso | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/util/geniso b/debian/util/geniso
index 13d9275e0..420533a45 100755
--- a/debian/util/geniso
+++ b/debian/util/geniso
@@ -32,7 +32,7 @@ cp /usr/lib/ISOLINUX/isolinux.bin ${dir}
cp /usr/lib/syslinux/modules/bios/ldlinux.c32 ${dir}
# generate EFI boot image
-blocks=$((($(stat -c %s "$EFI") / 1024 + 55) / 32 * 32 ))
+blocks=$$(stat -c %s "$EFI") / 1024 + 55) / 32 * 32 )+1))
mkfs.msdos -C ${dir}/efi.img $blocks >/dev/null
mmd -i ${dir}/efi.img ::efi
mmd -i ${dir}/efi.img ::efi/boot
--
2.28.0
Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Unfortunately, I seem to be suffering from the same issue. Initially I thought it was a hardware issue (system was ~10 years old), so I replaced the Intel DH67CF with core2duo processor by an Asrock H470M-ITX and Intel i5-10400 processor (and new case, new power supply; only SSD is re-used). A screenshot I made of a kernel crash ~3 weeks ago showed the same message as in the original bug report. With the new hardware, I suffered from a crash this weekend (still the 4.19.0-10-amd64 kernel). I wasn't able to reproduce the issue at will - it just happened randomly, it seems. But I did have the impression that, at least on three times, it happened when another Debian box was booted and made an NFS connection to the problematic machine. So could be ethernet related. And to agree with Mike above: indeed, I have a docker container operational. So far with the new kernel, no crash yet - but I did get this kernel call trace: Sep 30 08:24:30 vanaalten kernel: [159962.295249] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.19.0-11-amd64 #1 Debian 4.19.146-1 Sep 30 08:24:30 vanaalten kernel: [159962.295338] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS P1.20 05/18/2020 Sep 30 08:24:30 vanaalten kernel: [159962.295348] RIP: 0010:cpuidle_enter_state+0xb9/0x320 Sep 30 08:24:30 vanaalten kernel: [159962.295352] Code: e8 9c b5 b0 ff 80 7c 24 0b 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3b 02 00 00 31 ff e8 ce a7 b6 ff fb 66 0f 1f 44 00 00 <48> b8 ff ff ff ff f3 01 00 00 48 2b 1c 24 ba ff ff ff 7f 48 39 c3 Sep 30 08:24:30 vanaalten kernel: [159962.295354] RSP: 0018:be03019a3e90 EFLAGS: 0246 ORIG_RAX: ffde Sep 30 08:24:30 vanaalten kernel: [159962.295358] RAX: 9c1bcf5620c0 RBX: 917c1fc829ea RCX: 001f Sep 30 08:24:30 vanaalten kernel: [159962.295360] RDX: 917c1fc829ea RSI: 2c13c01d RDI: Sep 30 08:24:30 vanaalten kernel: [159962.295362] RBP: 9c1bc4d13000 R08: 0002 R09: 00021980 Sep 30 08:24:30 vanaalten kernel: [159962.295363] R10: 0001a685134b4b1d R11: 9c1bcf5610a8 R12: 0003 Sep 30 08:24:30 vanaalten kernel: [159962.295365] R13: 94aba518 R14: 0003 R15: Sep 30 08:24:30 vanaalten kernel: [159962.295368] FS: () GS:9c1bcf54() knlGS: Sep 30 08:24:30 vanaalten kernel: [159962.295370] CS: 0010 DS: ES: CR0: 80050033 Sep 30 08:24:30 vanaalten kernel: [159962.295372] CR2: 561438923229 CR3: 0001ef40a006 CR4: 003606e0 Sep 30 08:24:30 vanaalten kernel: [159962.295374] Call Trace: Sep 30 08:24:30 vanaalten kernel: [159962.295386] do_idle+0x228/0x270 Sep 30 08:24:30 vanaalten kernel: [159962.296362] cpu_startup_entry+0x6f/0x80 Sep 30 08:24:30 vanaalten kernel: [159962.296367] start_secondary+0x1a4/0x200 Sep 30 08:24:30 vanaalten kernel: [159962.296373] secondary_startup_64+0xa4/0xb0 ...but the system is still fully operational. No idea how serious above call trace is. Hopefully no further crashes. -- Matthijs
Bug#971521: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI
Hi Bastian, On 01-10-2020 10:02, Bastian Blank wrote: > On Thu, Oct 01, 2020 at 09:54:05AM +0200, Paul Gevers wrote: >> https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz > > Why is a simple ABI transition now also a autopkgtest failure? Because vanish-modules (in testing, but that's the same as in unstable) can't be installed with the vanish from unstable. > | The following packages have unmet dependencies: > | varnish-modules : Depends: varnishabi-11.0 > > In unstable I see: > > | Package: varnish > | Version: 6.5.1-1 > | Provides: varnishabi-12.0, > varnishabi-strict-1dae23376bb5ea7a6b8e9e4b9ed95cdc9469fb64 So, vanish stopped providing vanishabi-11.0 and vanish-modules needs to be fixed, otherwise vanish is not allowed to migrate to testing (until vanish-modules is removed from testing). vanish-modules in unstable is broken now, we don't want that to happen in testing. Paul signature.asc Description: OpenPGP digital signature
Bug#971521: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI
On Thu, Oct 01, 2020 at 09:54:05AM +0200, Paul Gevers wrote: > https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz Why is a simple ABI transition now also a autopkgtest failure? | The following packages have unmet dependencies: | varnish-modules : Depends: varnishabi-11.0 In unstable I see: | Package: varnish | Version: 6.5.1-1 | Provides: varnishabi-12.0, varnishabi-strict-1dae23376bb5ea7a6b8e9e4b9ed95cdc9469fb64 > Investigating (0) varnish-modules:amd64 < none -> 0.16.0-2 @un puN Ib > > Broken varnish-modules:amd64 Depends on libvarnishapi2:amd64 < none | > 6.5.1-1 @un uH > (>= 6.1.0) > Considering libvarnishapi2:amd64 0 as a solution to > varnish-modules:amd64 > Re-Instated libvarnishapi2:amd64 -- Only a fool fights in a burning house. -- Kank the Klingon, "Day of the Dove", stardate unknown
Bug#971522: parsnp: autopkgtest arm64 regression: raxmlHPC-PTHREADS not in system path!
Source: parsnp Version: 1.5.3+dfsg-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of parsnp the autopkgtest of parsnp fails in testing on arm64 when that autopkgtest is run with the binary packages of parsnp from unstable. It passes when run with only packages from testing. In tabular form: passfail parsnp from testing1.5.3+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=parsnp https://ci.debian.net/data/autopkgtest/testing/arm64/p/parsnp/7238498/log.gz autopkgtest [21:17:40]: test run-unit-test: [--- [93m[1mTest 1: With GenBank Annotations[0m |--Parsnp 1.5.3--| For detailed documentation please see --> http://harvest.readthedocs.org/en/latest 13:17:40 - [1;31mCRITICAL[0m - raxmlHPC-PTHREADS not in system path! autopkgtest [21:17:40]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature
Bug#971521: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI
Source: varnish-modules Version: 0.16.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, varn...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:varnish Dear maintainer(s), With a recent upload of varnish the autopkgtest of varnish-modules fails in testing when that autopkgtest is run with the binary packages of varnish from unstable. It passes when run with only packages from testing. In tabular form: passfail varnishfrom testing6.5.1-1 varnish-modulesfrom testing0.16.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. I'm not sure if varnish-modules just need a rebuild, or if there need to be more changes. Currently this regression is blocking the migration of varnish to testing [1]. Please fix the situation. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=varnish https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz Investigating (0) varnish-modules:amd64 < none -> 0.16.0-2 @un puN Ib > Broken varnish-modules:amd64 Depends on libvarnishapi2:amd64 < none | 6.5.1-1 @un uH > (>= 6.1.0) Considering libvarnishapi2:amd64 0 as a solution to varnish-modules:amd64 Re-Instated libvarnishapi2:amd64 signature.asc Description: OpenPGP digital signature
Processed: varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI
Processing control commands: > affects -1 src:varnish Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI Added indication that 971521 affects src:varnish -- 971521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970899: marked as done (libflame: add hypothesis to numpy autopkgtests dependencies)
Your message dated Thu, 01 Oct 2020 07:48:28 +
with message-id
and subject line Bug#970899: fixed in libflame 5.2.0-3
has caused the Debian Bug report #970899,
regarding libflame: add hypothesis to numpy autopkgtests dependencies
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.)
--
970899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libflame
Severity: serious
Hello,
please add hypothesis to the autopkgtests dependencies when testing numpy;
autopkgtest [03:28:25]: test numpy-with-default: python3 -c "import numpy as
np; np.test('full', verbose=3)"
autopkgtest [03:28:25]: test numpy-with-default: [---
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/numpy/_pytesttester.py", line 129, in
__call__
import hypothesis
ModuleNotFoundError: No module named 'hypothesis'
autopkgtest [03:28:26]: test numpy-with-default: ---]
autopkgtest [03:28:26]: test numpy-with-default: - - - - - - - - - - results -
- - - - - - - - -
autopkgtest [03:55:13]: test numpy-with-libflame: python3 -c "import numpy as
np; np.test('full', verbose=3)"
autopkgtest [03:55:13]: test numpy-with-libflame: [---
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/numpy/_pytesttester.py", line 129, in
__call__
import hypothesis
ModuleNotFoundError: No module named 'hypothesis'
autopkgtest [03:55:13]: test numpy-with-libflame: ---]
autopkgtest [03:55:14]: test numpy-with-libflame: - - - - - - - - - - results
- - - - - - - - - -
numpy-with-libflame FAIL non-zero exit status 1
it's not appropriate to add hypothesis to python3-numpy Depends since running
numpy tests is beyond the general use of the library, so at best it could be a
Suggests, which wont solve the failure of the autopkgtest.
RC severity since it's blocking the migration of numpy.
Regards,
Sandro
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libflame
Source-Version: 5.2.0-3
Done: Mo Zhou
We believe that the bug you reported is fixed in the latest version of
libflame, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mo Zhou (supplier of updated libflame 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, 01 Oct 2020 15:22:19 +0800
Source: libflame
Architecture: source
Version: 5.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Mo Zhou
Closes: 970899
Changes:
libflame (5.2.0-3) unstable; urgency=medium
.
* Autopkgtest: add the missing deps python3-hypothesis (Closes: #970899)
Checksums-Sha1:
9ecb30415a7f5a524fc4e542bd6c208cc46becb9 2291 libflame_5.2.0-3.dsc
bc7acb31d3ae7ab68434517258c180435933f8ba 24076 libflame_5.2.0-3.debian.tar.xz
14ecc30f542783ba55f5bd87f4270a4ada42d716 6178 libflame_5.2.0-3_source.buildinfo
Checksums-Sha256:
c4894bd72a017803c08763b7f035fe0b32bb485ea2a74123ea99dfa201d3a880 2291
libflame_5.2.0-3.dsc
90e5f597562fe2b783a4f1f70fa3c2434f627ea34fcd7c84a94057b3775e9f41 24076
libflame_5.2.0-3.debian.tar.xz
3db15635f56becb0dd3fc372fde37d2b211ad18aaeb845ba4a8a7d5088faa15a 6178
libflame_5.2.0-3_source.buildinfo
Files:
f609744b29da5f42e9ee02e20c1ac8f0 2291 math optional libflame_5.2.0-3.dsc
67dd3e581534c742871b3c8ba78adbc1 24076 math optional
libflame_5.2.0-3.debian.tar.xz
361e34a93d1565dff6b3981a09e2d1a5 6178 math optional
libflame_5.2.0-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl91hH0RHGx1bWluQGRl
Bug#971519: [Pkg-javascript-devel] Bug#971519: node-locate-character: Rebuild from sources
Le 01/10/2020 à 09:25, Pirate Praveen a écrit : > > > On 2020, ഒക്ടോബർ 1 12:23:20 PM IST, Xavier Guimard wrote: >> Package: node-locate-character >> Version: 2.0.5-1 >> Severity: serious >> Justification: source-is-missing >> >> 2.0.5 is packaged from npm registry temporarily to be able to build >> rollup 2. Upstream didn't push 2.0.5 source in git repo (last github >> release/HEAD is 2.0.1), then 2.0.5 was packaged from npm registry instead. >> >> This bug is a reminder to avoid having 2.0.5-1 pushed outside >> experimental >> > > We can just repack and rebuild if they don't update the repo I think. Upstream source are really missing, only repacked files are available. Relevant bug: https://github.com/Rich-Harris/locate-character/issues/6
Processed: bug 971519 is forwarded to https://github.com/Rich-Harris/locate-character/issues/6
Processing commands for cont...@bugs.debian.org: > forwarded 971519 https://github.com/Rich-Harris/locate-character/issues/6 Bug #971519 [node-locate-character] node-locate-character: Rebuild from sources Set Bug forwarded-to-address to 'https://github.com/Rich-Harris/locate-character/issues/6'. > thanks Stopping processing here. Please contact me if you need assistance. -- 971519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965310: marked as done (hwloc: lstopo crash with: CommandLine Error: Option 'polly' registered more than once!)
Your message dated Thu, 01 Oct 2020 07:33:30 + with message-id and subject line Bug#954849: fixed in mesa 20.1.9-1 has caused the Debian Bug report #954849, regarding hwloc: lstopo crash with: CommandLine Error: Option 'polly' registered more than once! 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.) -- 954849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hwloc Version: 2.2.0+dfsg-3 Severity: important Dear Maintainer, lstopo is crashing with error message: ": CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options" -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/24 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hwloc depends on: ii libc6 2.31-1 ii libcairo2 1.16.0-4 ii libhwloc15 2.2.0+dfsg-3 ii libtinfo6 6.2-1 ii libx11-62:1.6.9-2+b1 hwloc recommends no packages. hwloc suggests no packages. -- no debconf information -- Best regards, Roman Ondráček signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: mesa Source-Version: 20.1.9-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of mesa, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated mesa 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, 01 Oct 2020 10:12:00 +0300 Source: mesa Architecture: source Version: 20.1.9-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 954849 Changes: mesa (20.1.9-1) unstable; urgency=medium . * New upstream release. * control: Add libclang-cpp11-dev to build-depends. (Closes: #954849) Checksums-Sha1: 71f51b2d7a4e4aa09c5c8ca77ba4dbb245a7bb15 5495 mesa_20.1.9-1.dsc 9574460ed66647d2ca5cc204dfea0bc99c94ccbd 19913138 mesa_20.1.9.orig.tar.gz e449aa90549e151663bfb0385229534b139cbc2f 106952 mesa_20.1.9-1.diff.gz 9ef40d162528bca0b251d25201f5ae8a7976783d 9745 mesa_20.1.9-1_source.buildinfo Checksums-Sha256: d8867882d5648b7e3b937e352e6bd931a1f371c8043520bffdec4db7a65f4425 5495 mesa_20.1.9-1.dsc 63d9044938e6334dadd5f37a55aa1464d800410f3a4b57f7c84bb446bd197565 19913138 mesa_20.1.9.orig.tar.gz 8c46748cd9df7eefbb1086714e7f82f3a142758b79b5e7cf415e2aca6bea23f8 106952 mesa_20.1.9-1.diff.gz 2ead330aebe20867817685fd5d7b563e02afe0c7880802d3a8168a2151029478 9745 mesa_20.1.9-1_source.buildinfo Files: 2ec26ef551d8d81a3048c901393e0864 5495 graphics optional mesa_20.1.9-1.dsc e2a4cadf393c67f0ef61af7592481503 19913138 graphics optional mesa_20.1.9.orig.tar.gz 36d8b9035215af2e9065bc4125212663 106952 graphics optional mesa_20.1.9-1.diff.gz 3d6433169c22925dd98cd877f772bb52 9745 graphics optional mesa_20.1.9-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl91gVUACgkQy3AxZaiJ hNymHxAAl3y+ca/Rcru8X6nMV0BZsjbSOpa+9XnTbvz6e+lccJWqkOcimzKQ3u5i GMSlie3mLbwyvdB3J9raU8wB9UMzJetSpLT9Nz8ygFrSNU1lK5QGxDSQy8FXaZNG CxK+CevOboxUcY6G+UrFEJYtXtGOL9WxEiAuDasaOzMCsQzpMyKrYVHlG1TCWv1D pFE8eX7TsamKs4epr/DfX2Z4gcU+0hjrk6IjKcIa0bGl5WD3r4BFbcgFVXV4dn0r jLq1a6gGb5xG234Pxdkf8yBP3O72derN1UJmzjHpLzf4b+97MhfcGPJ4pjhdSzHG JPdpafqWRNKocSFvNN05vG+C+1dXbRIWXrVrUVPSw4sIOfC2rvcCWgguR4buhgYa cj1qF+LmRTmmBToZDzMiUu9A9GBp+yzLof5NUn3BzkKerhhAs2m4X/dEBgIKZTLq vA+Cq+0pl5Uzrdjt/uikTmye8H/0/nWnOO2pf0HQ+5GMbMkgcBAD5ourZx2BlFYr 57kJkn0/IU+a6mi/+9d1KI9Piw48uBZVV01nx5Mi2cyX3qttex0XIAAjI/9RuyAL
Bug#964973: marked as done (mesa-opencl-icd: Applications using OpenCL crash with : CommandLine Error: Option 'polly' registered more than once!)
Your message dated Thu, 01 Oct 2020 07:33:30 + with message-id and subject line Bug#954849: fixed in mesa 20.1.9-1 has caused the Debian Bug report #954849, regarding mesa-opencl-icd: Applications using OpenCL crash with : CommandLine Error: Option 'polly' registered more than once! 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.) -- 954849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mesa-opencl-icd Version: 20.1.2-1 Severity: important Dear Maintainer, After upgrading from version 19.1.6, applications using OpenCL are crashing with error message: ": CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options". For example: # clinfo : CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options -- Package-specific info: glxinfo: DISPLAY is not set. /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-14), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP Debian 5.7.6-1 (2020-06-24) Xorg X server log files on system: -- -rw-r--r--. 1 root root 51966 Mar 27 2019 /var/log/Xorg.0.log -rw-r--r--. 1 roman roman 23062 Apr 29 2019 /home/roman/.local/share/xorg/Xorg.2.log -rw-r--r--. 1 root root 22875 Apr 29 2019 /var/log/Xorg.3.log -rw-r--r--. 1 roman roman 41083 Jul 13 17:46 /home/roman/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/roman/.local/share/xorg/Xorg.0.log): -- [ 105.769] (--) Log file renamed from "/home/roman/.local/share/xorg/Xorg.pid-2221.log" to "/home/roman/.local/share/xorg/Xorg.0.log" [ 105.770] X.Org X Server 1.20.8 X Protocol Version 11, Revision 0 [ 105.770] Build Operating System: Linux 4.19.0-8-amd64 x86_64 Debian [ 105.770] Current Operating System: Linux Lenovo-B51-80 5.7.0-1-amd64 #1 SMP Debian 5.7.6-1 (2020-06-24) x86_64 [ 105.770] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.7.0-1-amd64 root=UUID=a5e403c0-734b-406d-b2a7-3a9d5aff0c7e ro security=selinux quiet apparmor=0 [ 105.771] Build Date: 31 March 2020 10:14:40AM [ 105.771] xorg-server 2:1.20.8-2 (https://www.debian.org/support) [ 105.771] Current version of pixman: 0.36.0 [ 105.771]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 105.771] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 105.771] (==) Log file: "/home/roman/.local/share/xorg/Xorg.0.log", Time: Mon Jul 13 17:11:29 2020 [ 105.772] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 105.773] (==) No Layout section. Using the first Screen section. [ 105.773] (==) No screen section available. Using defaults. [ 105.773] (**) |-->Screen "Default Screen Section" (0) [ 105.773] (**) | |-->Monitor "" [ 105.773] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 105.773] (==) Automatically adding devices [ 105.773] (==) Automatically enabling devices [ 105.773] (==) Automatically adding GPU devices [ 105.773] (==) Max clients allowed: 256, resource mask: 0x1f [ 105.774] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 105.774]Entry deleted from font path. [ 105.774] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 105.774] (==) ModulePath set to "/usr/lib/xorg/modules" [ 105.774] (II) The server relies on udev to provide the list of input devices. If no
Bug#965178: marked as done (opencl support is broken: LLVM ERROR: inconsistency in registered CommandLine option)
Your message dated Thu, 01 Oct 2020 07:33:30 + with message-id and subject line Bug#954849: fixed in mesa 20.1.9-1 has caused the Debian Bug report #954849, regarding opencl support is broken: LLVM ERROR: inconsistency in registered CommandLine option to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: darktable Version: 3.0.2-1 Severity: important Dear Maintainer, After transitioning opencl to llvm-10 and clang-10 darktable's opencl support is broken. $ darktable : CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options The same error occurs whatever llvm and clang version is used so maby upstream opencl support code brakes when opencl libraries are compiled using llvm-10 and clang-10? Since further details at upstreams buglist: https://github.com/darktable-org/darktable/issues/5761 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.31-1 ii libcairo21.16.0-4 ii libcolord-gtk1 0.1.26-2 ii libcolord2 1.4.4-2 ii libcups2 2.3.3-1 ii libcurl3-gnutls 7.68.0-1+b1 ii libexiv2-27 0.27.2-8 ii libgcc-s110.1.0-6 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.64.4-1 ii libgomp1 10.1.0-6 ii libgphoto2-6 2.5.25-2 ii libgphoto2-port122.5.25-2 ii libgraphicsmagick-q16-3 1.4+really1.3.35+hg16297-1 ii libgtk-3-0 3.24.20-1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo 1:2.0.5-1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libjson-glib-1.0-0 1.4.4-2 ii liblcms2-2 2.9-4+b1 ii liblensfun1 0.3.2-5 ii liblua5.3-0 5.3.3-1.1+b1 ii libopenexr24 2.3.0-6 ii libopenjp2-7 2.3.1-1 ii libosmgpsmap-1.0-1 1.1.0-7 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 ii libpng16-16 1.6.37-2 ii libpugixml1v51.10-1 ii librsvg2-2 2.48.7-1 ii libsecret-1-00.20.3-1 ii libsoup2.4-1 2.70.0-1 ii libsqlite3-0 3.32.3-1 ii libstdc++6 10.1.0-6 ii libtiff5 4.1.0+git191117-2 ii libwebp6 0.6.1-2+b1 ii libx11-6 2:1.6.9-2+b1 ii libxml2 2.9.10+dfsg-5+b1 ii libxrandr2 2:1.5.1-1 ii zlib1g 1:1.2.11.dfsg-2 darktable recommends no packages. darktable suggests no packages. -- no debconf information This mail was virus scanned and spam checked before delivery. This mail is also DKIM signed. See header dkim-signature. --- End Message --- --- Begin Message --- Source: mesa Source-Version: 20.1.9-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of mesa, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated mesa 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, 01 Oct 2020 10:12:00 +0300 Source: mesa Architecture: source Version: 20.1.9-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 954849 Changes: mesa (20.1.9-1) unstable; urgency=medium . * New upstream release. * control: Add libclang-cpp11-dev to
Bug#954849: marked as done (does not start: LLVM ERROR: inconsistency in registered CommandLine options)
Your message dated Thu, 01 Oct 2020 07:33:30 + with message-id and subject line Bug#954849: fixed in mesa 20.1.9-1 has caused the Debian Bug report #954849, regarding does not start: LLVM ERROR: inconsistency in registered CommandLine options 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.) -- 954849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice Version: 1:6.4.2-2 Severity: important Dear Maintainer, * What led up to the situation? After night upgrade libreoffice crash when is opened * What exactly did you do (or not do) that was effective (or ineffective)? Ineffective: reinstalling, trying install older version, change Windowmanager to other as Gnome * What was the outcome of this action? in console I get message: : CommandLine Error: Option 'limited-coverage-experimental' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.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 libreoffice depends on: ii libreoffice-base1:6.4.2-2 ii libreoffice-calc1:6.4.2-2 ii libreoffice-core1:6.4.2-2 ii libreoffice-draw1:6.4.2-2 ii libreoffice-impress 1:6.4.2-2 ii libreoffice-math1:6.4.2-2 ii libreoffice-report-builder-bin 1:6.4.2-2 ii libreoffice-writer 1:6.4.2-2 ii python3-uno 1:6.4.2-2 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2 ii fonts-crosextra-carlito 20130920-1 ii fonts-dejavu2.37-1 ii fonts-liberation1:1.07.4-11 ii fonts-liberation2 2.1.0-1 ii fonts-linuxlibertine5.3.0-4 ii fonts-noto-core 20200103-3 ii fonts-noto-extra20200103-3 ii fonts-noto-mono 20200103-3 ii fonts-noto-ui-core 20200103-3 ii fonts-sil-gentium-basic 1.102-1 ii libreoffice-java-common 1:6.4.2-2 ii libreoffice-nlpsolver 0.9+LibO6.4.2-2 ii libreoffice-report-builder 1:6.4.2-2 ii libreoffice-script-provider-bsh 1:6.4.2-2 ii libreoffice-script-provider-js 1:6.4.2-2 ii libreoffice-script-provider-python 1:6.4.2-2 ii libreoffice-sdbc-mysql 1:6.4.2-2 ii libreoffice-sdbc-postgresql 1:6.4.2-2 ii libreoffice-wiki-publisher 1.2.0+LibO6.4.2-2 Versions of packages libreoffice suggests: ii cups-bsd2.3.1-11 ii default-jre [java8-runtime] 2:1.11-72 ii firefox-esr 68.6.0esr-1 ii ghostscript 9.52~dfsg-1 pn gnupg pn gpa ii gstreamer1.0-libav 1.16.2-2 ii gstreamer1.0-plugins-bad1.16.2-2.1 ii gstreamer1.0-plugins-base 1.16.2-2 ii gstreamer1.0-plugins-good 1.16.2-2 ii gstreamer1.0-plugins-ugly 1.16.2-2 ii hunspell-ar [hunspell-dictionary] 3.2-1.1 ii hunspell-be [hunspell-dictionary] 0.53-3 ii hunspell-bg [hunspell-dictionary] 1:6.4.0~rc2-1 ii hunspell-bs [hunspell-dictionary] 1:6.4.0~rc2-1 ii hunspell-ca [hunspell-dictionary] 3.0.4+repack1-1 ii hunspell-cs [hunspell-dictionary] 1:6.4.0~rc2-1 ii hunspell-da [hunspell-dictionary] 1:6.4.0~rc2-1 ii hunspell-de-at [hunspell-dictionary]20161207-7 ii hunspell-de-ch [hunspell-dictionary]20161207-7 ii hunspell-de-de [hunspell-dictionary]20161207-7 ii hunspell-en-gb [hunspell-dictionary]1:6.4.0~rc2-1 ii
Bug#971519: [Pkg-javascript-devel] Bug#971519: node-locate-character: Rebuild from sources
On 2020, ഒക്ടോബർ 1 12:23:20 PM IST, Xavier Guimard wrote: >Package: node-locate-character >Version: 2.0.5-1 >Severity: serious >Justification: source-is-missing > >2.0.5 is packaged from npm registry temporarily to be able to build >rollup 2. Upstream didn't push 2.0.5 source in git repo (last github >release/HEAD is 2.0.1), then 2.0.5 was packaged from npm registry instead. > >This bug is a reminder to avoid having 2.0.5-1 pushed outside >experimental > We can just repack and rebuild if they don't update the repo I think. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Processed: notfound 971519 in 2.0.1-6
Processing commands for cont...@bugs.debian.org: > notfound 971519 2.0.1-6 Bug #971519 [node-locate-character] node-locate-character: Rebuild from sources Ignoring request to alter found versions of bug #971519 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 971519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971519: node-locate-character: Rebuild from sources
Package: node-locate-character Version: 2.0.5-1 Severity: serious Justification: source-is-missing 2.0.5 is packaged from npm registry temporarily to be able to build rollup 2. Upstream didn't push 2.0.5 source in git repo (last github release/HEAD is 2.0.1), then 2.0.5 was packaged from npm registry instead. This bug is a reminder to avoid having 2.0.5-1 pushed outside experimental
