Bug#977649:
upstream: https://github.com/ksnip/kImageAnnotator/issues/185[1] Sincerely yours Damir Islamov email: da...@secretlaboratory.ru [1] https://github.com/ksnip/kImageAnnotator/issues/185 signature.asc Description: This is a digitally signed message part.
Processed: closing 973167
Processing commands for cont...@bugs.debian.org:
> close 973167 0.5.2-1
Bug #973167 [src:ufonormalizer] ufonormalizer: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Marked as fixed in versions ufonormalizer/0.5.2-1.
Bug #973167 [src:ufonormalizer] ufonormalizer: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
973167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Hi Vincas, > Package: libkwaylandserver5 > Version: 5.20.4-2 > /usr/bin/kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: > undefined symbol: > _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShe > llSurfaceInterfaceE Which version of kwin do you have installed? Seems like a missing breaks against old versions of kwin or so. > It seems that I have go perform `full-upgrade` that removes `user-manager`. > After that KDE desktop works. Yes, user-manager is going away. It is now a kcm and not a separate program. Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Processed: Re: Bug#977329: krita segfaults when try to open with libQt5Gui.so.5.15.1
Processing commands for cont...@bugs.debian.org: > reassign 977329 lxqt-qtplugin Bug #977329 [krita] krita segfaults when try to open with libQt5Gui.so.5.15.1 Bug reassigned from package 'krita' to 'lxqt-qtplugin'. No longer marked as found in versions krita/1:4.4.1+dfsg-1. Ignoring request to alter fixed versions of bug #977329 to the same values previously set > retitle 977329 lxqt-plugin: platform theme needs fixes for Qt 5.15 Bug #977329 [lxqt-qtplugin] krita segfaults when try to open with libQt5Gui.so.5.15.1 Changed Bug title to 'lxqt-plugin: platform theme needs fixes for Qt 5.15' from 'krita segfaults when try to open with libQt5Gui.so.5.15.1'. > tag 977329 = fixed-upstream Bug #977329 [lxqt-qtplugin] lxqt-plugin: platform theme needs fixes for Qt 5.15 Added tag(s) fixed-upstream; removed tag(s) moreinfo. > severity 977329 serious Bug #977329 [lxqt-qtplugin] lxqt-plugin: platform theme needs fixes for Qt 5.15 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 977329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:sublime-music: fails to migrate to testing for too long: Dependencies can't migrate
Processing control commands:
> close -1 0.11.10-1
Bug #978035 [src:sublime-music] src:sublime-music: fails to migrate to testing
for too long: Dependencies can't migrate
Marked as fixed in versions sublime-music/0.11.10-1.
Bug #978035 [src:sublime-music] src:sublime-music: fails to migrate to testing
for too long: Dependencies can't migrate
Marked Bug as done
> block -1 by 972803
Bug #978035 {Done: Paul Gevers } [src:sublime-music]
src:sublime-music: fails to migrate to testing for too long: Dependencies can't
migrate
978035 was not blocked by any bugs.
978035 was not blocking any bugs.
Added blocking bug(s) of 978035: 972803
--
978035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#978035: src:sublime-music: fails to migrate to testing for too long: Dependencies can't migrate
Source: sublime-music Version: 0.9.1-2 Severity: serious Control: close -1 0.11.10-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 972803 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:sublime-music in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=sublime-music OpenPGP_signature Description: OpenPGP digital signature
Processed: src:tools-cli-clojure: fails to migrate to testing for too long: maintainer built arch:all binaries
Processing control commands: > close -1 1.0.194-1 Bug #978034 [src:tools-cli-clojure] src:tools-cli-clojure: fails to migrate to testing for too long: maintainer built arch:all binaries Marked as fixed in versions tools-cli-clojure/1.0.194-1. Bug #978034 [src:tools-cli-clojure] src:tools-cli-clojure: fails to migrate to testing for too long: maintainer built arch:all binaries Marked Bug as done -- 978034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978034: src:tools-cli-clojure: fails to migrate to testing for too long: maintainer built arch:all binaries
Source: tools-cli-clojure Version: 0.3.5-2 Severity: serious Control: close -1 1.0.194-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:tools-cli-clojure in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=tools-cli-clojure OpenPGP_signature Description: OpenPGP digital signature
Bug#977900: marked as done (node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path')
Your message dated Thu, 24 Dec 2020 20:49:46 + with message-id and subject line Bug#977900: fixed in node-autoprefixer 10.1.0+~cs11.3.2.0-1 has caused the Debian Bug report #977900, regarding node-autoprefixer: FTBFS: ENOENT: no such file or directory, open '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.) -- 977900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-autoprefixer Version: 10.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, node-autoprefixer/experimental recently started to FTBFS: debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs mkdir node_modules ln -s ../colorette node_modules/colorette ln -s ../num2fraction node_modules/num2fraction debian/rules override_dh_auto_build make[1]: Entering directory '/build/node-autoprefixer-10.0.0' rollup --config debian/rollup.config.js debian/autoprefixer.js → dist/autoprefixer.js... [!] Error: Could not load path (imported by ../../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such file or directory, open 'path' Error: Could not load path (imported by ../../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such file or directory, open 'path' make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1 make[1]: Leaving directory '/build/node-autoprefixer-10.0.0' make: *** [debian/rules:11: binary] Error 2 A previous build on Oct 28 has been successful, so this current failure is probably caused by some updated (transitive) build-depends. Andreas node-autoprefixer_10.0.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-autoprefixer Source-Version: 10.1.0+~cs11.3.2.0-1 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of node-autoprefixer, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-autoprefixer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Dec 2020 01:59:39 +0530 Source: node-autoprefixer Architecture: source Version: 10.1.0+~cs11.3.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 977900 Changes: node-autoprefixer (10.1.0+~cs11.3.2.0-1) unstable; urgency=medium . * Drop colorette component (now provided by node-postcss) * New upstream version 10.1.0+~cs1.2.2 * Bump Standards-Version to 4.5.1 (no changes needed) * Include autoprefixer-rails gem as component * New upstream version 10.1.0+~cs11.3.2.0 * Adjust plugin order in rollup.config.js (Closes: #977900) Use node-polyfills plugin before node-resolve and commonjs plugins * Build using upstream rollup.config.js * Exclude autoprefixer-rails component from binary package Checksums-Sha1: e733b5ddd55ae0bfcd4d640bea4acf2105925cdb 3327 node-autoprefixer_10.1.0+~cs11.3.2.0-1.dsc 13849c005f3c0be468b05c5c83531cac04944e28 699935 node-autoprefixer_10.1.0+~cs11.3.2.0.orig-autoprefixer-rails.tar.gz 6f682b6a027a4e9ddfa4564cd2589d1d4e669ede 2694 node-autoprefixer_10.1.0+~cs11.3.2.0.orig-num2fraction.tar.gz da229bf402782a1abbb322285b08629c5569cbf7 248171 node-autoprefixer_10.1.0+~cs11.3.2.0.orig.tar.gz 07940d0e54ba3ce36aafa571b167c7ed46b4943c 15016 node-autoprefixer_10.1.0+~cs11.3.2.0-1.debian.tar.xz 2538ac863c186f85533f24c99c1467c1fddf45a6 10134 node-autoprefixer_10.1.0+~cs11.3.2.0-1_amd64.buildinfo Checksums-Sha256: 7fa582ac020fe1a48143bbb5ab2cb280bf9d6ab0f9527d9330dc877383b883ef 3327 node-autoprefixer_10.1.0+~cs11.3.2.0-1.dsc d23d4ac1038f453628e25117c13c702859122acf51c39db0740307dd5201f3c0 699935 node-autoprefixer_10.1.0+~cs11.3.2.0.orig-autoprefixer-rails.tar.gz 0225f46ed6c6fb9538c6219dc953b7aa4e74a4b6d2c92ebd58d07be3e8388133 2694 node-autoprefixer_10.1.0+~cs11.3.2.0.orig-num2fraction.tar.gz df8b05104d81e710592fdadcabc493e572ae2576a57bfc98dbdf857
Bug#978032: python-cobra: autopkgtest regression in testing
Source: python-cobra
Version: 0.19.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The autopkgtests of python-cobra recently started to fail in testing [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/p/python-cobra/testing/amd64/
ERRORS
__ ERROR at setup of TestManipulation.test_escape_ids __
filename = '/usr/lib/python3/dist-packages/cobra/test/data/textbook.xml.gz'
number =
f_replace = {'F_GENE': ,
'F_GENE_REV': , 'F_GROUP':
, 'F_GROUP_REV': , ...}
kwargs = {}
doc = >
cobra_error = CobraSBMLError('Something went wrong reading the SBML
model. Most likely the SBML model is not valid. Please check
tha...ame)`\nIf the model is valid and cannot be read please open an
issue at https://github.com/opencobra/cobrapy/issues .')
Bug#961283: libhttp-tiny-perl: Don't release with bullseye
Hi gregor, On 24-12-2020 02:57, gregor herrmann wrote: > So this looks like a potential for improvement for the tooling to > detect "key packages", namely to take Provides into account. Our tooling [1] already does that, but IIRC it prefers real packages over Provides. Paul https://salsa.debian.org/qa/udd/-/blob/master/scripts/update-key-packages.pl OpenPGP_signature Description: OpenPGP digital signature
Processed: retitle this bug correctly
Processing commands for cont...@bugs.debian.org: > retitle 971271 rainloop: ftbfs with node-postcss 8.0 Bug #971271 [rainloop] rainloop: ftbfs with node-postcss 8.0 in experimental Changed Bug title to 'rainloop: ftbfs with node-postcss 8.0' from 'rainloop: ftbfs with node-postcss 8.0 in experimental'. > End of message, stopping processing here. Please contact me if you need assistance. -- 971271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: rainloop: ftbfs with node-postcss 8.0 in experimental
Processing control commands: > retitle rainloop: ftbfs with node-postcss 8.0 Unknown command or malformed arguments to command. > severity -1 serious Bug #971271 [rainloop] rainloop: ftbfs with node-postcss 8.0 in experimental Severity set to 'serious' from 'important' -- 971271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978026: kvpm: crash after launch
Package: kvpm Version: 0.9.10-1 Severity: grave Justification: renders package unusable Dear Maintainer, I can't launch kvpm it crashes after launch ! kvpm: symbol lookup error: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: undefined symbol: ucol_open_63 I get the same kind of problem with reportbug-ng crashing after launch : File "/usr/bin/reportbug-ng", line 26, in from PyQt5 import QtCore, QtWidgets ImportError: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: undefined symbol: ucol_strcoll_63 The problem seems to be with Qt5 core ? My system : CPU : Intel(R) Core(TM) i5-5675C CPU @ 3.10GHz RAM : 16Go Some disks mostly using RAID 1 Mother board : Gigabyte H97N-WIFI Regards JP P -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kvpm depends on: ii libblkid1 2.33.1-0.1 ii libc6 2.28-10 ii libdevmapper1.02.1 2:1.02.155-3 ii libgcc1 1:8.3.0-6 ii libkf5configcore5 5.54.0-1+deb10u1 ii libkf5configgui55.54.0-1+deb10u1 ii libkf5configwidgets55.54.0-1 ii libkf5coreaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5kdelibs4support5 5.54.0-1 ii libkf5widgetsaddons55.54.0-1 ii libkf5xmlgui5 5.54.0-1 ii liblvm2app2.2 2.02.168-2 ii libparted2 3.2-25 ii libqt5core5a5.11.3+dfsg1-1+deb10u4 ii libqt5gui5 5.11.3+dfsg1-1+deb10u4 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u4 ii libstdc++6 8.3.0-6 Versions of packages kvpm recommends: ii dosfstools 4.1-2 ii jfsutils 1.1.15-4 pn ntfs-3g ii reiserfsprogs 1:3.6.27-3 ii xfsprogs 4.20.0-1 Versions of packages kvpm suggests: ii btrfs-progs [btrfs-tools] 5.9-1~bpo10+1 pn reiser4progs -- no debconf information
Processed: [bts-link] source package swi-prolog
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package swi-prolog > # 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 #977657 (http://bugs.debian.org/977657) > # Bug title: swi-prolog: FTBFS with OpenSSL 1.1.1i > # * https://github.com/SWI-Prolog/packages-ssl/issues/159 > # * remote status changed: (?) -> closed > # * closed upstream > tags 977657 + fixed-upstream Bug #977657 [swi-prolog] swi-prolog: FTBFS with OpenSSL 1.1.1i Added tag(s) fixed-upstream. > usertags 977657 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 977657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com
Processing control commands: > forwarded -1 https://github.com/seccomp/libseccomp-golang/issues/61 Bug #976943 [src:golang-github-seccomp-libseccomp-golang] golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libseccomp-golang returned exit code 1 Set Bug forwarded-to-address to 'https://github.com/seccomp/libseccomp-golang/issues/61'. > severity -1 important Bug #976943 [src:golang-github-seccomp-libseccomp-golang] golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libseccomp-golang returned exit code 1 Severity set to 'important' from 'serious' -- 976943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libsec
Control: forwarded -1 https://github.com/seccomp/libseccomp-golang/issues/61 Control: severity -1 important On Thu, Dec 24, 2020 at 9:12 PM Lucas Nussbaum wrote: > > On 14/12/20 at 14:36 -0500, Reinhard Tartler wrote: > > > > > > > === RUN TestRuleAddAndLoad > > > seccomp_test.go:588: Syscall should have returned error code! > > > --- FAIL: TestRuleAddAndLoad (0.00s) > > This has been reported to upstream on Nov 29. There's no bug in the library itself. Just the test doesn't take ppc64le into account. The behavior of this library on ppc64le has no difference with the C version libseccomp2. So I'm downgrading this bug severity. -- Shengjing Zhu
Bug#978022: libopenmpi3 Runtime failure opal_pmix_base_select failed
Package: libopenmpi3 Version: 3.1.3-11 Severity: serious Even with the fixed libpmix2_4.0.0~rc1-2, I am getting runtime failures trying to run MPI programs, e.g. the nwchem autopkgtests all fail like this: | Running tests/water/water_md | | cleaning scratch | copying input and verified output files | running nwchem (/usr/bin/nwchem) with 1 processors | | NWChem execution failed |[kohn:13218] [[5127,0],0] ORTE_ERROR_LOG: Not found in file ../../../../../../orte/mca/ess/hnp/ess_hnp_module.c at line 320 |-- |It looks like orte_init failed for some reason; your parallel process is |likely to abort. There are many reasons that a parallel process can |fail during orte_init; some of which are due to configuration or |environment problems. This failure appears to be an internal failure; |here's some additional information (which may only be relevant to an |Open MPI developer): | | opal_pmix_base_select failed | --> Returned value Not found (-13) instead of ORTE_SUCCESS |-- Not sure whether this is libopenmpi3, openmpi-bin, libpmix2 or something else, so please reassign as needed. But at least the openmpi excuses is full of ci.debian.net regressions: https://qa.debian.org/excuses.php?package=openmpi Or is there something needed on the application side, like a new environment variable or library to be linked in? Michael
Bug#928526: testing bug existence
hi is this bug existed in testing kernel 5.9.11 ?
Bug#977645: linux-image-5.10.0-trunk-arm64: Both 5.10.1 and .2 do work on RPi3B+ with ext4 rootfs on sdcard
Package: src:linux Version: 5.10.2-1~exp1 Followup-For: Bug #977645 Just wanted to mention that this version as well as 5.10.1 do boot on a RPi3B+. It's not in any way contradicting this bug, but may be useful to know nonetheless. -- Package-specific info: ** Version: Linux version 5.10.0-trunk-arm64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-1) 10.2.1 20201207, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.2-1~exp1 (2020-12-22) ** Command line: video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 dma.dmachans=0x7f35 bcm2709.boardrev=0xa020d3 bcm2709.serial=0x4db4eb14 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=29 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:B4:EB:14 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=tty0 console=ttyS1,115200 root=/dev/mmcblk0p2 rw fsck.repair=yes net.ifnames=0 cma=64M rootwait disable_fw_kms_setup=1 ** Tainted: C (1024) * staging driver was loaded ** Kernel log: [ 13.233771] systemd[1]: Mounted POSIX Message Queue File System. [ 13.269941] systemd[1]: Mounted RPC Pipe File System. [ 13.301879] systemd[1]: Mounted Kernel Debug File System. [ 13.334267] systemd[1]: Mounted Kernel Trace File System. [ 13.369388] systemd[1]: Started Journal Service. [ 15.264660] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer [ 15.277293] vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 15.684981] alg: No test for fips(ansi_cprng) (fips_ansi_cprng) [ 15.895410] hid: raw HID events driver (C) Jiri Kosina [ 16.001054] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 16.020592] cfg80211: Loaded X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf' [ 16.021187] libphy: Fixed MDIO Bus: probed [ 16.040951] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328' [ 16.070420] usbcore: registered new interface driver usbhid [ 16.077020] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 16.088116] usbhid: USB HID core driver [ 16.127572] platform regulatory.0: firmware: direct-loading firmware regulatory.db [ 16.146777] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [ 16.208404] cryptd: max_cpu_qlen set to 1000 [ 16.372179] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed [ 16.410860] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 16.437335] usbcore: registered new interface driver brcmfmac [ 16.445395] libphy: lan78xx-mdiobus: probed [ 16.493071] brcmfmac mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.bin [ 16.516817] brcmfmac mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt [ 16.655211] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 16.707881] input: mini keyboard as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/0003:1997:2433.0001/input/input0 [ 16.716699] mc: Linux media interface: v0.10 [ 16.718052] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 16.718219] brcmfmac mmc1:0001:1: firmware: failed to load brcm/brcmfmac43455-sdio.clm_blob (-2) [ 16.718222] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 16.718230] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 16.718961] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 [ 16.729295] debugfs: Directory '3f902000.hdmi' with parent 'vc4-hdmi' already present! [ 16.766644] hid-generic 0003:1997:2433.0001: input,hidraw0: USB HID v1.01 Keyboard [ mini keyboard] on usb-3f98.usb-1.1.2/input0 [ 16.767079] usbcore: registered new interface driver lan78xx [ 16.784405] videodev: Linux video capture interface: v2.00 [ 16.800597] input: mini keyboard Mouse as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:1997:2433.0002/input/input1 [ 17.064785] input: mini keyboard System Control as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:1997:2433.0002/input/input2 [ 17.113125] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name! [ 17.120695] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 17.136657] input: mini keyboard Consumer Control as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:1997:2433.0002/input/input3 [ 17.140203] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4]) [ 17.140452] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4]) [ 17.140575] vc4-drm s
Bug#977901: Bug#963711: Found in 87 line
Hi! On Thu, 24 Dec 2020 14:37:09 +0100 Michel Le Bihan wrote: > Hello, > > This issue is about Chromium crashing just after startup with debug > when it did not crash that quickly without debug. Is Chromium as stable > with debug as without it? > > All Chromium packages in Debian unstable and the build on my website > were affected by https://bugs.debian.org/977901 . If it's the issue you > are writing about, then a new package that should fix this was uploaded > today and should be built soon. > Sorry, I replied to the wrong bug. The version I have currently installed is 87.0.4280.88-0.3, this is the one that is not crashing. the old version, 87.0.4280.88-0.2 crashed all the time. Regards, Daniel.
Bug#973433: reproducing bug
is this bug happen in the current testing kernel 5.9.11 ?
Processed: Re: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'
Processing control commands: > tags -1 pending Bug #977900 [src:node-autoprefixer] node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path' Added tag(s) pending. -- 977900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'
Control: tags -1 pending On Tue, 22 Dec 2020 16:25:36 +0100 Andreas Beckmann wrote: > debian/autoprefixer.js → dist/autoprefixer.js... > [!] Error: Could not load path (imported by ./../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such file or directory, open 'path' > Error: Could not load path (imported by ./../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such file or directory, open 'path' > > make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1 > make[1]: Leaving directory '/build/node-autoprefixer-10.0.0' > make: *** [debian/rules:11: binary] Error 2 > > A previous build on Oct 28 has been successful, so this current failure is probably > caused by some updated (transitive) build-depends. It is fixed by changing the order of plugins used in rollup.config.js, rollup-plugin-polyfills should come before commonjs and node-resolve plugins.
Bug#976583: marked as done (ompl: FTBFS: Failed to copy 'usr/bin/ompl_benchmark_statistics.py': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 51, <> line 2.)
Your message dated Thu, 24 Dec 2020 15:00:12 + with message-id and subject line Bug#976583: fixed in ompl 1.5.1+ds1-1 has caused the Debian Bug report #976583, regarding ompl: FTBFS: Failed to copy 'usr/bin/ompl_benchmark_statistics.py': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 51, <> line 2. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ompl Version: 1.4.2+ds1-6 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > make[3]: Entering directory '/<>/build' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: > /<>/debian/tmp/usr/lib/aarch64-linux-gnu/pkgconfig/ompl.pc > -- Installing: > /<>/debian/tmp/usr/share/ompl/cmake/omplConfig.cmake > -- Installing: > /<>/debian/tmp/usr/share/ompl/cmake/omplConfigVersion.cmake > -- Installing: /<>/debian/tmp/usr/share/ompl/ompl.conf > -- Installing: /<>/debian/tmp/usr/include/ompl > -- Installing: /<>/debian/tmp/usr/include/ompl/config.h > -- Installing: /<>/debian/tmp/usr/include/ompl/geometric > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/HillClimbing.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/PathHybridization.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/SimpleSetup.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/PathSimplifier.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/GeneticSearch.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/PathGeometric.h > -- Installing: /<>/debian/tmp/usr/include/ompl/geometric/planners > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/PlannerIncludes.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/experience > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/experience/ThunderRetrieveRepair.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/experience/LightningRetrieveRepair.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/sbl > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/sbl/SBL.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/sbl/pSBL.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/pRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/RRTXstatic.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/VFRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/LBTRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/InformedRRTstar.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/RRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/LazyRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/RRTsharp.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/TRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/SORRTstar.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/BiTRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/RRTstar.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/LazyLBTRRT.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/rrt/RRTConnect.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/cforest > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/cforest/CForestStateSampler.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/cforest/CForest.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/cforest/CForestStateSpaceWrapper.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/est > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/est/EST.h > -- Installing: > /<>/debian/tmp/usr/include/ompl/geometric/planners/est/ProjEST.h > -- Installing: > /<>/debian/tmp/us
debian-bugs-rc@lists.debian.org
Your message dated Thu, 24 Dec 2020 15:00:09 + with message-id and subject line Bug#973999: fixed in armnn 20.08-1 has caused the Debian Bug report #973999, regarding armnn: FTBFS: error: no matching function for call to ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const arm_compute::PoolingType&)’ 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.) -- 973999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: armnn Version: 19.11.1-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org armnn fails to build arm64: | [ 1%] Building CXX object src/backends/reference/workloads/CMakeFiles/armnnRefBackendWorkloads.dir/ArgMinMax.cpp.o | cd /<>/build-area/src/backends/reference/workloads && /usr/bin/c++ -DARMCOMPUTECL_ENABLED -DARMCOMPUTENEON_ENABLED -DARMNNREF_ENABLED -DARMNN_SERIALIZER -DARMNN_SERIALIZER_SCHEMA_PATH=\"/<>/src/armnnSerializer/ArmnnSchema.fbs\" -DBOOST_ALL_DYN_LINK -DBOOST_ALL_NO_LIB -I/<>/include -I/<>/src/armnn -I/<>/src/armnnUtils -I/<>/src/backends -I/<>/src/profiling -isystem /<>/third-party -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -Wall -Werror -Wold-style-cast -Wno-missing-braces -Wconversion -Wsign-conversion -fPIC -o CMakeFiles/armnnRefBackendWorkloads.dir/ArgMinMax.cpp.o -c /<>/src/backends/reference/workloads/ArgMinMax.cpp | /<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp: In function ‘arm_compute::PoolingLayerInfo armnn::armcomputetensorutils::BuildArmComputePoolingLayerInfo(const armnn::Pooling2dDescriptor&, bool)’: | /<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp:160:57: error: no matching function for call to ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const arm_compute::PoolingType&)’ | 160 | return arm_compute::PoolingLayerInfo(poolingType); | | ^ | In file included from /usr/include/aarch64-linux-gnu/arm_compute/core/ITensorInfo.h:30, | from /usr/include/aarch64-linux-gnu/arm_compute/core/ITensor.h:27, | from /<>/src/backends/aclCommon/ArmComputeTensorUtils.hpp:10, | from /<>/src/backends/aclCommon/ArmComputeTensorUtils.cpp:5: | /usr/include/aarch64-linux-gnu/arm_compute/core/Types.h:1255:14: note: candidate: ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(arm_compute::PoolingType, arm_compute::DataLayout)’ See https://buildd.debian.org/status/fetch.php?pkg=armnn&arch=arm64&ver=19.11.1-1%2Bb2&stamp=1604748678&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: armnn Source-Version: 20.08-1 Done: Wookey We believe that the bug you reported is fixed in the latest version of armnn, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wookey (supplier of updated armnn package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Dec 2020 18:21:50 + Source: armnn Binary: libarmnn-cpuacc-backend22 libarmnn-cpuacc-backend22-dbgsym libarmnn-cpuref-backend22 libarmnn-cpuref-backend22-dbgsym libarmnn-dev libarmnn-gpuacc-backend22 libarmnn-gpuacc-backend22-dbgsym libarmnn22 libarmnn22-dbgsym libarmnnaclcommon22 libarmnnaclcommon22-dbgsym libarmnntfliteparser-dev libarmnntfliteparser22 libarmnntfliteparser22-dbgsym python3-pyarmnn python3-pyarmnn-dbgsym Architecture: source arm64 Version: 20.08-1 Distribution: unstable Urgency: medium Maintainer: Francis Murtagh Changed-By: Wookey Description: libarmnn-cpuacc-backend22 - Arm NN is an inference engine for CPUs, GPUs and NPUs libarmnn-cpuref-backend22 - Arm NN is an inference engine for CPUs, GPUs and NPUs libarmnn-dev - Arm NN is an inference engine for CPUs, GPUs and NPUs libarmnn-gpuacc-backend22 - Arm NN is an inference engine for CPUs, GPUs and NPUs libarmnn22
Processed: Re: node-css-loader: please embed additional postcss extensions
Processing control commands: > block -1 by 977900 Bug #977688 [node-css-loader] node-css-loader: please embed additional postcss extensions 977688 was not blocked by any bugs. 977688 was not blocking any bugs. Added blocking bug(s) of 977688: 977900 > tag 977900 help Bug #977900 [src:node-autoprefixer] node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path' Added tag(s) help. -- 977688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977688 977900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> forcemerge 973848 975060
Bug #973848 {Done: Michel Le Bihan } [chromium] chromium:
Unsupported version, many security bugs unfixed
Bug #973858 {Done: Michel Le Bihan } [chromium] chromium:
Outdated version, more than 100 open security issues
Bug #973848 {Done: Michel Le Bihan } [chromium] chromium:
Unsupported version, many security bugs unfixed
There is no source info for the package 'chromium' at version
'87.0.4280.66~linuxmint1+debbie' with architecture ''
Unable to make a source version for version '87.0.4280.66~linuxmint1+debbie'
Marked as found in versions 87.0.4280.66~linuxmint1+debbie.
Marked as found in versions 87.0.4280.66~linuxmint1+debbie.
Bug #975060 [chromium] chromium: Chromium stuck in version 83
Severity set to 'grave' from 'normal'
Marked Bug as done
The source chromium and version 87.0.4280.88-0.1 do not appear to match any
binary packages
Marked as fixed in versions chromium/87.0.4280.88-0.1.
There is no source info for the package 'chromium' at version
'87.0.4280.66~linuxmint1+debbie' with architecture ''
Unable to make a source version for version '87.0.4280.66~linuxmint1+debbie'
Marked as found in versions chromium/83.0.4103.116-3.1 and
chromium/84.0.4147.105-1.
Added tag(s) security.
Bug #973858 {Done: Michel Le Bihan } [chromium] chromium:
Outdated version, more than 100 open security issues
Merged 973848 973858 975060
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
973848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848
973858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973858
975060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org:
> merge 973848 975060
Bug #973848 {Done: Michel Le Bihan } [chromium] chromium:
Unsupported version, many security bugs unfixed
Bug #973858 {Done: Michel Le Bihan } [chromium] chromium:
Outdated version, more than 100 open security issues
Unable to merge bugs because:
severity of #975060 is 'normal' not 'grave'
done of #975060 is '' not 'Michel Le Bihan '
Failed to merge 973848: Did not alter merged bugs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
973848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848
973858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973858
975060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > merge 975060 973848 Bug #975060 [chromium] chromium: Chromium stuck in version 83 Unable to merge bugs because: severity of #973858 is 'grave' not 'normal' done of #973858 is 'Michel Le Bihan ' not '' severity of #973848 is 'grave' not 'normal' done of #973848 is 'Michel Le Bihan ' not '' Failed to merge 975060: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 973848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848 973858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973858 975060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977960: marked as done (dangling /usr/share/javascript/jquery/jquery.js symlink)
Your message dated Thu, 24 Dec 2020 13:33:53 + with message-id and subject line Bug#977960: fixed in node-jquery 3.5.1+dfsg+~3.5.5-3 has caused the Debian Bug report #977960, regarding dangling /usr/share/javascript/jquery/jquery.js symlink 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.) -- 977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjs-jquery Version: 3.5.1+dfsg+~3.5.5-1 Severity: serious Tags: sid bullseye There's at least one dangling /usr/share/javascript/jquery/jquery.js symlink $ dpkg -S /usr/share/javascript/jquery/jquery.js libjs-jquery: /usr/share/javascript/jquery/jquery.js $ ls -l /usr/share/javascript/jquery/jquery.js lrwxrwxrwx 1 root root 34 Dec 22 08:27 /usr/share/javascript/jquery/jquery.js -> ../../nodejs/jquery/dist/jquery.js $ ls -lL /usr/share/javascript/jquery/jquery.js ls: cannot access '/usr/share/javascript/jquery/jquery.js': No such file or directory --- End Message --- --- Begin Message --- Source: node-jquery Source-Version: 3.5.1+dfsg+~3.5.5-3 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-jquery, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-jquery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 Dec 2020 14:20:06 +0100 Source: node-jquery Architecture: source Version: 3.5.1+dfsg+~3.5.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 977960 Changes: node-jquery (3.5.1+dfsg+~3.5.5-3) unstable; urgency=medium . * Team upload * libjs-jquery must require node-jquery with the same version (Closes: #977960) Checksums-Sha1: 55d147cf1cd153ed4686dbb53975e6ae553a2596 2689 node-jquery_3.5.1+dfsg+~3.5.5-3.dsc 1695602b07d1c0dbfb975fc5d4f41ae34ff332ea 5572 node-jquery_3.5.1+dfsg+~3.5.5-3.debian.tar.xz Checksums-Sha256: dafd54356f4b08a5aa9f463cba6993b7bdd8609c5db47347d7c38d648283fcf1 2689 node-jquery_3.5.1+dfsg+~3.5.5-3.dsc 615aa800977cd808a73c6b6f6a893b5947da16259100360fea5625cf3d6c57a6 5572 node-jquery_3.5.1+dfsg+~3.5.5-3.debian.tar.xz Files: d7b061503d086968dc86d2fdc0139125 2689 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-3.dsc 5cc3275df27514b31fc217d80be94047 5572 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/klb8ACgkQ9tdMp8mZ 7un4URAAln8lp6cJj/7c9UhEOOHVWwNZML9UXcMOm+/XQPWVb3cTvXjCsQbST4o3 rgPg0HniW204Q1AlvehZvjo6/WkPVNZETnc0blC8OJemMSOyXZj0OsVQN+V6AeR9 v2feLuRW2IeJFjBIitTaQ/bmwbaw4xzuOrGF3XJnGEMOGvGxwYS9TWcde/QcIVIU BR7FtBp++4ydfdAsjLdtu5HylTZy05RRHY92dug9uv0e4kKj+s/NKVuJ0YHUpmqZ QOTFbOqlvZ0avzjLCsU7FirIYvNMyTIjdy64Op9LpaniI3VyLIE+jNnbqx2j09xz iwT90dnPr1MD3MlCZP557/VAef6RO4SfOYxXCGXUaWLx5HwtqXvHLQADldva1hQI UvhsHQKyvnEkF/IOIMDNm9F+FREx+7yqDQnAj5+34HIP/PD1dVhv7X/9Hxa2i+3t BAP3HDnt1ctFY2F9zq1z8I3bc++v6+nmWZCa61Z9K8Q/ERZbnQ/grutSRowkPluZ u2StvbF7EkfuAUtGJz5q50OZP5ATKfFpdmsFErG92DYDOxrEEt2+ivEqqIkOPxAt IwCEt/exuVUDGaAOQq21lM+WgQ1aR7rQ4wU0K2VBcgExeOfM6IybvdXU1bnMF02l dbP/+5E4W50UfkEqgAMdhogcSI7lL1AxUCH06IyynE/mjqouyKo= =206H -END PGP SIGNATURE End Message ---
Processed: python-blosc: FTBFS on ppc64el: KeyError: 'flags'
Processing commands for cont...@bugs.debian.org: > forwarded 976910 https://github.com/Blosc/python-blosc/issues/227 Bug #976910 [src:python-blosc] python-blosc: FTBFS on ppc64el: KeyError: 'flags' Set Bug forwarded-to-address to 'https://github.com/Blosc/python-blosc/issues/227'. > thanks Stopping processing here. Please contact me if you need assistance. -- 976910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977243: Still not fixed
tags 977243 -pending
thanks
CC-ing on of upstream contributors.
@Casey could you please take a look? This part of the code
fails with the newer boost_1.74? Thanks!
It looks like the last version in git still fails to build.
===
ceph/src/common/async/completion.h: In instantiation of 'void
ceph::async::detail::CompletionImpl::destroy_defer(std::tuple&&) [with Executor1 =
boost::asio::io_context::basic_executor_typ
e, 0>; Handler =
boost::asio::detail::coro_handler,
boost::asio::exec
ution::detail::blocking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boos
t::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > > >, void>;
T = void; Args = {boost::system::error_code}]':
/root/mod1/ceph/src/common/async/completion.h:188:8: required from
here
/root/mod1/ceph/src/common/async/completion.h:194:29: error:
'boost::asio::executor_work_guard,
boost::asio::execution::detail::blo
cking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution
::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > >, void>::executor_type' {aka
'class
boost::asio::execution::any_executor,
boost::asio::execution::detail::blocking::never_t<0>
,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only >,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only > >'} has no member named 'defer'; did you mean 'prefer'?
194 | w.second.get_executor().defer(std::move(f), alloc2);
| ^
| prefer
ceph/src/common/async/completion.h: In instantiation of 'void
ceph::async::detail::CompletionImpl::destroy_dispatch(std::tuple&&) [with Executor1 =
boost::asio::io_context::basic_executor_
type, 0>; Handler =
boost::asio::detail::coro_handler,
boost::asio::e
xecution::detail::blocking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, b
oost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > > >,
void>; T = void; Args = {boost::system::error_code}]':
/root/mod1/ceph/src/common/async/completion.h:196:8: required from here
/root/mod1/ceph/src/common/async/completion.h:202:29: error:
'boost::asio::executor_work_guard,
boost::asio::execution::detail::blo
cking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution
::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > >, void>::executor_type' {aka
'class
boost::asio::execution::any_executor,
boost::asio::execution::detail::blocking::never_t<0>
,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only >,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only > >'} has no member named 'dispatch'
202 | w.second.get_executor().dispatch(std::move(f), alloc2);
| ^~~~
ceph/src/common/async/completion.h: In instantiation of 'void
ceph::async::detail::CompletionImpl::destroy_post(std::tuple&&) [with Executor1 =
boost::asio::io_context::basic_executor_type
, 0>; Handler =
boost::asio::detail::coro_handler,
boost::asio::execu
tion::detail::blocking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost
::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > > >, void>;
T = void; Args = {boost::system::error_code}]':
/root/mod1/ceph/src/common/async/completion.h:204:8: required from here
/root/mod1/ceph/src/common/async/completion.h:210:29: error:
'boost::asio::executor_work_guard,
boost::asio::execution::detail::blo
cking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution
::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > >, void>::executor_type' {aka
'class
boost::asio::execution::any_executor,
boost::asio::execution::detail::blocking::never_t<0>
,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only >,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only > >'} has no member named 'post'
210 | w.second.get_executor().post(std::move(f), alloc2);
| ^~~~
===
Best regards
Anton
Processed: Still not fixed
Processing commands for cont...@bugs.debian.org: > tags 977243 -pending Bug #977243 [src:ceph] ceph FTBFS with Boost 1.74 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 977243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#977960 marked as pending in node-jquery
Processing control commands: > tag -1 pending Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js symlink Added tag(s) pending. -- 977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977960: marked as pending in node-jquery
Control: tag -1 pending Hello, Bug #977960 in node-jquery reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jquery/-/commit/555703e2657d244a7a105851ec1cfd0c30d32aa5 libjs-jquery must require node-jquery with the same version Closes: #977960 (this message was generated automatically) -- Greetings https://bugs.debian.org/977960
Bug#976430: marked as done (libfreecad-python3-0.19: missing Breaks+Replaces: libfreecad-python3-0.18)
Your message dated Thu, 24 Dec 2020 13:18:29 + with message-id and subject line Bug#976430: fixed in freecad 0.19~pre1+git20201221.3b449e1ce9+dfsg1-2 has caused the Debian Bug report #976430, regarding libfreecad-python3-0.19: missing Breaks+Replaces: libfreecad-python3-0.18 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.) -- 976430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfreecad-python3-0.19 Version: 0.19~pre1+git20201123.8d73c8f0+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libfreecad-python3-0.19. Preparing to unpack .../5-libfreecad-python3-0.19_0.19~pre1+git20201123.8d73c8f0+dfsg1-1_amd64.deb ... Unpacking libfreecad-python3-0.19 (0.19~pre1+git20201123.8d73c8f0+dfsg1-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-ZRBq6k/5-libfreecad-python3-0.19_0.19~pre1+git20201123.8d73c8f0+dfsg1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/freecad-python3/lib/DraftUtils.so', which is also in package libfreecad-python3-0.18 0.18.4+dfsg2-6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-ZRBq6k/5-libfreecad-python3-0.19_0.19~pre1+git20201123.8d73c8f0+dfsg1-1_amd64.deb cheers, Andreas libfreecad-python3-0.18=0.18.4+dfsg2-6_libfreecad-python3-0.19=0.19~pre1+git20201123.8d73c8f0+dfsg1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: freecad Source-Version: 0.19~pre1+git20201221.3b449e1ce9+dfsg1-2 Done: Kurt Kremitzki We believe that the bug you reported is fixed in the latest version of freecad, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated freecad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 Dec 2020 06:54:50 -0600 Source: freecad Architecture: source Version: 0.19~pre1+git20201221.3b449e1ce9+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 976430 Changes: freecad (0.19~pre1+git20201221.3b449e1ce9+dfsg1-2) unstable; urgency=medium . * [2ce772e] Add Breaks+Replaces for libfreecad-python3-0.19 over 0.18 (Closes: #976430) * [0046d46] Always only --list-missing Checksums-Sha1: 967c4a883fbea67de693a9380b03ab83ce1113ad 3510 freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2.dsc ca364f609ea96c1f4b873944319e2035635e000c 26828 freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2.debian.tar.xz 9e728adfa43a214622ea8ba6da4e152e6bf8a3eb 31277 freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2_source.buildinfo Checksums-Sha256: 7cb56ec48fcc9d6e12a654b3e9c8649d606afa052aeec38b8ae44c686b6c17a5 3510 freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2.dsc deeb37294cd63e8e1fbde368c3040bb2f9fddd8219a52eafe1f5970ffd690a43 26828 freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2.debian.tar.xz 329bdd0872aa43a8e41e32e3cb1e6eac13050c7ae6eff74661a5da7db09918f2 31277 freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2_source.buildinfo Files: 2b13ff5c20bca5381c36a3ff121f4d2d 3510 science optional freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2.dsc 5da60a35d478d792bd524044d2edf7c1 26828 science optional freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2.debian.tar.xz e9c037e0602eeab52838fbd480c853a4 31277 science optional freecad_0.19~pre1+git20201221.3b449e1ce9+dfsg1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAl/kkHAWHGtr
Bug#976911: marked as done (node-opencv: FTBFS on ppc64el: not ok 197 Error: Command failed: node /<>/examples/motion-track.js terminate called after throwing an instance of 'cv::Exceptio
Your message dated Thu, 24 Dec 2020 14:08:55 +0100 with message-id <20201224130855.gc12...@xanadu.blop.info> and subject line Re: node-opencv: FTBFS on ppc64el: not ok 197 Error: Command failed: node /<>/examples/motion-track.js terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.2.0) ../modules/imgproc/src/color.cpp:182: error: (-215:Assertion failed) !_src.empty() in function 'cvtColor' Aborted has caused the Debian Bug report #976911, regarding node-opencv: FTBFS on ppc64el: not ok 197 Error: Command failed: node /<>/examples/motion-track.js terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.2.0) ../modules/imgproc/src/color.cpp:182: error: (-215:Assertion failed) !_src.empty() in function 'cvtColor' Aborted 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.) -- 976911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-opencv Version: 7.0.0+git20200310.6c13234-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm marking this bug as severity:serious since your package currently has ppc64el binary packages in unstable (so this is a regression). Relevant part (hopefully): > make[1]: Entering directory '/<>' > npm test > > > opencv@7.0.0 test > > node test/unit.js > > TAP version 13 > # Smoke tests / Can Import > ok 1 imported fine > ok 2 version is there:4.2 > ok 3 point is there > ok 4 matrix is there > # importing library multiple times is ok > ok 5 null > ok 6 null > # Point > ok 7 should be truthy > ok 8 cannot call without new > ok 9 should be equal > ok 10 should be equal > ok 11 should be equal > ok 12 should be equal > ok 13 Points are immutable > ok 14 Points are immutable > ok 15 should be truthy > ok 16 should be equal > # Matrix constructor > ok 17 should be truthy > ok 18 should be truthy > ok 19 should be truthy > ok 20 should be truthy > ok 21 should be truthy > # Matrix accessors > ok 22 should be equivalent > ok 23 should be equal > ok 24 should be equal > ok 25 should be equal > ok 26 should be equal > ok 27 should be equivalent > ok 28 should be equal > ok 29 should be equal > ok 30 should be equivalent > ok 31 should be equivalent > ok 32 should be equivalent > ok 33 should be equivalent > ok 34 should be equal > ok 35 should be equivalent > # Matrix functions > ok 36 should be equal > ok 37 should be equal > ok 38 should be equal > ok 39 GetRotationMatrix2D > # .norm > ok 40 should be truthy > ok 41 should be truthy > ok 42 should be equal > ok 43 should be equal > # Matrix toBuffer > ok 44 should be truthy > # Matrix toBuffer Async > (node:29380) [DEP0005] DeprecationWarning: Buffer() is deprecated due to > security and usability issues. Please use the Buffer.alloc(), > Buffer.allocUnsafe(), or Buffer.from() methods instead. > ok 45 null > ok 46 should be truthy > ok 47 should be truthy > # detectObject > ok 48 null > ok 49 should be truthy > ok 50 should be equal > # .absDiff and .countNonZero > ok 51 should be truthy > ok 52 should be truthy > ok 53 should be equal > # .bitwiseXor > ok 54 should be equal > # Image read from file > ok 55 should be truthy > ok 56 should be equal > ok 57 should be equal > ok 58 should be equal > ok 59 should be equal > # Multi-page image read from file > ok 60 should be truthy > ok 61 should be equal > ok 62 should be truthy > ok 63 should be equal > ok 64 should be equal > ok 65 should be equal > ok 66 should be equal > ok 67 should be truthy > ok 68 should be equal > ok 69 should be equal > ok 70 should be equal > ok 71 should be equal > ok 72 should be truthy > ok 73 should be equal > ok 74 should be equal > ok 75 should be equal > ok 76 should be equal > ok 77 should be truthy > ok 78 should be equal > ok 79 should be equal > ok 80 should be equal > ok 81 should be equal > ok 82 should be truthy > ok 83 should be equal > ok 84 should be equal > ok 85 should be equal > ok 86 should be equal > ok 87 should be truthy > ok 88 should be equal > ok 89 should be equal > ok 90 should be equal > ok 91 should be equal > ok 92 should be truthy > ok 93 should be equal > ok 94 should be equal > ok 95 should be equal > ok 96 should be equal > ok 97 should be truthy > ok 98 should be equal > ok 99 should be equal > ok 100 should be equal > ok 101 should be equal > ok 102 should be truthy > ok 103 should
Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libsec
On 14/12/20 at 14:36 -0500, Reinhard Tartler wrote: > > > > === RUN TestRuleAddAndLoad > > seccomp_test.go:588: Syscall should have returned error code! > > --- FAIL: TestRuleAddAndLoad (0.00s) > > > Source code is here: > https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589 > > This test is basically loading a seccomp rule and expects that the > getpid() syscall fails with the rule loaded, but in that test it seems > to pass. This might mean that seccomp isn't working on that box. > > Lucas, can you elaborate a bit what kind of test system you were using? > Do you have any explanation what might be going on with the test setup that > would make seccomp not work or only under certain conditions? Hi, This is a system running plain debian stable with an unstable chroot (using sbuild). I cannot think of something strange. I tried disabling SMT (hyperthreading) because with it enabled, the system has 160 visible cores, which breaks some builds. But it did not change anything. # uname -a Linux drac-6.grenoble.grid5000.fr 4.19.0-13-powerpc64le #1 SMP Debian 4.19.160-2 (2020-11-28) ppc64le GNU/Linux I also tried with a Debian testing image and could reproduce it. Kernel was linux-image-5.9.0-1-powerpc64le 5.9.1-1 Lucas
Bug#976918: memkind: FTBFS on ppc64el: GetArenaTest.test_TC_MEMKIND_ThreadHash failed
Hi Adam, On 18/12/20 at 08:46 +0100, Adam Borowski wrote: > Control: tags -1 + moreinfo unreproducible > > Hi Lucas! > > > On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote: > > > Source: memkind > > > > During a rebuild of all packages in sid, your package failed to build > > > on ppc64el. At the same time, it did not fail on amd64. > > > > > I'm marking this bug as severity:serious since your package currently has > > > ppc64el binary packages in unstable (so this is a regression). > > > > > [ RUN ] GetArenaTest.test_TC_MEMKIND_ThreadHash > > > > test/get_arena_test.cpp:67: Failure > > > > Expected: (max_collisions) <= (collisions_limit), actual: 10 vs 5 > > > > [ FAILED ] GetArenaTest.test_TC_MEMKIND_ThreadHash (184 ms) > > Ping: > > Is that fail reproducible for you? I have a possible fix, but have no way > > of verifying it -- the package builds successfully on all machines I have > > access to, and did build fine on buildds (no major changes to toolchain > > since then). > > The underlying code uses an assumption on the internal working for glibc, > that might possibly be invalid in some cases. Even if it happens to be > wrong, correctness is not violated, there's just a performance loss. > > The test that fails could thus be removed -- however, I'd like to know how > it did fail in the first place. No matter how I tried, I did not manage to > reproduce the failure. > > There are also multiple ways to improve this hash (an explicit mapping, a > "random" hash, etc) but as this code is used in large performance-critical > parts, I'd prefer to first understand. Sorry for the late reply. This machine has SMT with 10 threads per core (so a total of 160 "cpus" in /proc/cpuinfo), and this proved to cause some issues. I tried again building 1.10.1-1, and: - the build succeeded with SMT off - the build failed again with SMT on Lucas
Bug#973154: apertium-kaz-tat: FTBFS: hfst-concatenate: .deps/any-symbol.hfst is not a valid transducer file
HI Nilesh On Thu, 24 Dec 2020 at 10:48, Nilesh wrote: > > I can't seem to reproduce this, can you initiate a rebuild for this? > > I suspect if new apertium upload fixed this somehow. Attaching the log in any > case. Reproducible builds [1] shows apertium-kaz-tat is currently building successfully, so this bug can be closed, but apertium-kaz-tat needs a source-only upload anyway: "Not built on buildd: arch all binaries uploaded by kartik, a new source-only upload is needed to allow migration" Regards Graham [1] https://tests.reproducible-builds.org/debian/history/amd64/apertium-kaz-tat.html
Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
I've reproduced same issue on VM. It seems that I have go perform `full-upgrade` that removes `user-manager`. After that KDE desktop works. If I try to install `user-manager` again, I get suggestion to remove whole kde-plasma-dekstop & friends...
Processed: still not fixed in 3.5.1+dfsg+~3.5.5-2
Processing control commands:
> reopen -1
Bug #977960 {Done: Xavier Guimard } [libjs-jquery] dangling
/usr/share/javascript/jquery/jquery.js symlink
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-jquery/3.5.1+dfsg+~3.5.5-2.
> found -1 3.5.1+dfsg+~3.5.5-2
Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js
symlink
Marked as found in versions node-jquery/3.5.1+dfsg+~3.5.5-2.
--
977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#977960: still not fixed in 3.5.1+dfsg+~3.5.5-2
Control: reopen -1 Control: found -1 3.5.1+dfsg+~3.5.5-2 $ ls -l /usr/share/nodejs/jquery/dist/ total 0 lrwxrwxrwx 1 root root 34 Dec 23 22:00 jquery.js -> ../../nodejs/jquery/dist/jquery.js lrwxrwxrwx 1 root root 38 Dec 23 22:00 jquery.min.js -> ../../nodejs/jquery/dist/jquery.min.js lrwxrwxrwx 1 root root 45 Dec 23 22:00 jquery.min.js.brotli -> ../../nodejs/jquery/dist/jquery.min.js.brotli lrwxrwxrwx 1 root root 41 Dec 23 22:00 jquery.min.js.gz -> ../../nodejs/jquery/dist/jquery.min.js.gz lrwxrwxrwx 1 root root 39 Dec 23 22:00 jquery.min.map -> ../../nodejs/jquery/dist/jquery.min.map lrwxrwxrwx 1 root root 46 Dec 23 22:00 jquery.min.map.brotli -> ../../nodejs/jquery/dist/jquery.min.map.brotli lrwxrwxrwx 1 root root 42 Dec 23 22:00 jquery.min.map.gz -> ../../nodejs/jquery/dist/jquery.min.map.gz please could you check an upgrade path from the last versions? snapshot.debian.org should have these packages. You also could create such a directory with the symlinks and check that the upgrade works. Matthias
Bug#976069: bugs
Dear colleagues, Thanks for reporting this! Unfortunately I got the reference to the bug only from kodi tracker.d.o page. I will investigate the issue and upload the fix to Git. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 signature.asc Description: PGP signature
Bug#978001: marked as done (snapcast: switch to default libboost-dev)
Your message dated Thu, 24 Dec 2020 11:04:13 + with message-id and subject line Bug#978001: fixed in snapcast 0.22.0+dfsg1-1 has caused the Debian Bug report #978001, regarding snapcast: switch to default libboost-dev 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.) -- 978001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snapcast Version: 0.19.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 978000 by -1 snapcast currently has build dependency on libboost1.71-dev but we are trying to remove boost 1.71 from bullseye. So, please switch to the unversioned libboost-dev which currently points to 1.74. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: snapcast Source-Version: 0.22.0+dfsg1-1 Done: Felix Geyer We believe that the bug you reported is fixed in the latest version of snapcast, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Geyer (supplier of updated snapcast package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 Dec 2020 11:57:39 +0100 Source: snapcast Architecture: source Version: 0.22.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Felix Geyer Changed-By: Felix Geyer Closes: 978001 Changes: snapcast (0.22.0+dfsg1-1) unstable; urgency=medium . * New upstream release. * Repackage orig tarball to exclude libflac.js which is missing the source code. - Disable snapweb as it relies on the javascript library. * Build-depend on libboost-dev >= 1.70 instead of libboost1.71-dev. (Closes: #978001) Checksums-Sha1: 08be78d56ab685f99571f972afcc7df2846ab9c8 2076 snapcast_0.22.0+dfsg1-1.dsc b3b8eca8132d7230d43720e9b1a86fef1e88b656 855708 snapcast_0.22.0+dfsg1.orig.tar.xz 616d97561dc94f679601436c7cab4194e404cb66 6084 snapcast_0.22.0+dfsg1-1.debian.tar.xz Checksums-Sha256: 352edca254c8bcdc7544eac58a571ba6ef3b2fb17fe93e254db4753904b34adc 2076 snapcast_0.22.0+dfsg1-1.dsc 02d186513cf4483fb2ff2efb6743fc01bef0ccb29003e9c5eefbe4e8596bc138 855708 snapcast_0.22.0+dfsg1.orig.tar.xz 95d703449b3c0a7ed19c994d493c9bc1f52bb570ccd8eb8f313cdcb01a3fd8c0 6084 snapcast_0.22.0+dfsg1-1.debian.tar.xz Files: 420470a593d2740f64fd03dab183066d 2076 sound optional snapcast_0.22.0+dfsg1-1.dsc 3cc60353e5b2df59a49cb5c91cb8ca80 855708 sound optional snapcast_0.22.0+dfsg1.orig.tar.xz abc9fb04fb81fff7cf03368226007385 6084 sound optional snapcast_0.22.0+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAl/kdIcACgkQ/iLG/YMT XUXf1w//dk4zrDcdLHn+IS7dxTIoGcZiXNazvEBz40ae6yA4tHvZ/unTZEEo/GBk ToUvY6pZ+aAQrCmGAtEesvYkChCZoux2mcnAVPRmPeiXwxdgjJ2e/oXuNj7SOul2 oXpqdSf2GWcoLmUpmq+JO1b44UEkvEeEj4PUrxHoA/IeeoIPfeZfQZPb3NoG6oAu 16LMmDESK6MPobQnivVR1bvoB16s5MfypRcuGza3CcqpjCjhOiJwSYJu4A3HGUmz xqWOZ05+htIW9qbmdBoTd2aWe8HqwpU3k7n8jXTW0VUPcqq1N1rQ32Eatug8YEul KJ0ZnSxNJmT3Z+AVsv2G6uK2KdbNRTtqxxvKjKaHdtZMqGKs1TZSQsW1PEuV6fn2 H4sEm5UKEYg9S4TuORX6GclkOpFBeuKnEVQmxzHEBGizuyor2fUovN1L3OXjCkC0 aHbAiCHgLSUl6QQGziN9SzQw2tSejOYq9kRlmIpQjT+JOBJW5CIlXNSmsC/SwdcC KThltE2Zh2/VNnfly3/mCaa7Jay4/SEh0FG3mGCcG/XV73+eX3eX4o+bSMENgCan H6Cn8FjlIzrBSOVI/9mYmbxLDPf75zOIMIbZewjZKe63mgurKEb33NTWJ4/DvUx2 UAPYoTwufiDJYfM1JAbbBYakJPXnOF/mfnoPa52f2s7a/dEper8= =IuCc -END PGP SIGNATURE End Message ---
Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Package: libkwaylandserver5 Version: 5.20.4-2 Severity: grave Justification: renders package unusable Dear Maintainer, After today Sid upgrades my KDE desktop failed to fully load after login. I see background and KDE spinner, but desktop does not appear. I've found this in `~/.xsession-errors`: ``` /usr/bin/kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShe llSurfaceInterfaceE ``` I've downgraded libkwaylandserver5 (to 5.19.5-2), kwayland-integration (to 5.19.5-3) and kwayland-data (to 4:5.74.0-2), rebooted and it started working again. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#974779: [Pkg-julia-devel] Bug#974779: severity - Julia: Please upgrade to llvm-toolchain-11
On 2020-12-24 09:04:50 +0900, Norbert Preining wrote: > Hi, > > > Control: severity -1 serious > > Pushing severity will not change the fact that the released version of > Julia does not support llvm11 and cannot be built with it. > As far as I see support for llvm11 is included in the 1.6.0 branch of > Julia, but that is probbly far off, and definitely not ready to be > released. > > That leaves either Julia being removed from testing/bullseye (very bad > idea) and keeping llvm10 in bullseye (nothing I can evaluate). We currently have 3 versions of llvm-toolchain in bullseye. That's 2 versions too many to support. We are aware that getting rid of llvm-toolchain-9 and llvm-toolchain-10 is likely not possible, but one of them will be removed and llvm-toolchain-10 is the most likely candidate for removal. If julia does not work with llvm-toolchain-11, please go back to llvm-toolchain-9. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#977901: marked as done (chromium: Inconsistent SEGV)
Your message dated Thu, 24 Dec 2020 09:34:00 + with message-id and subject line Bug#977901: fixed in chromium 87.0.4280.88-0.3 has caused the Debian Bug report #977901, regarding chromium: Inconsistent SEGV 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.) -- 977901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 87.0.4280.88-0.2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 3 crashes this morning, 4th session ran fine for about 30 minutes. Logs from latest: % chromium [2411401:2411401:1222/094248.490375:ERROR:gl_implementation.cc(282)] Failed to load /usr/lib/chromium/libGLESv2.so: /usr/lib/chromium/libGLESv2.so: cannot open shared object file: No such file or directory [2411401:2411401:1222/094248.491776:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization Received signal 11 SEGV_MAPERR 5501bc870647 #0 0x55d9b3c3fca9 (/usr/lib/chromium/chromium+0x542fca8) #1 0x55d9b3bb4623 (/usr/lib/chromium/chromium+0x53a4622) #2 0x55d9b3c3f88b (/usr/lib/chromium/chromium+0x542f88a) #3 0x7f432c14a140 (/lib/x86_64-linux-gnu/libpthread-2.31.so+0x1413f) #4 0x7f4327a7f80c (/lib/x86_64-linux-gnu/libc-2.31.so+0x8680b) #5 0x7f4327a816f5 (/lib/x86_64-linux-gnu/libc-2.31.so+0x886f4) #6 0x7f4327a83239 __libc_malloc #7 0x55d9b3c5779e operator new() #8 0x7f4327d0bcfc std::__cxx11::basic_string<>::reserve() #9 0x7f4327d01768 std::__cxx11::basic_stringbuf<>::overflow() #10 0x7f4327d0a31a std::basic_streambuf<>::xsputn() #11 0x7f4327cfc9e4 std::__ostream_insert<>() #12 0x55d9b3c3fd79 (/usr/lib/chromium/chromium+0x542fd78) #13 0x55d9b3c400a4 (/usr/lib/chromium/chromium+0x54300a3) #14 0x55d9b3bc5b2c (/usr/lib/chromium/chromium+0x53b5b2b) #15 0x55d9b3bc624e (/usr/lib/chromium/chromium+0x53b624d) #16 0x55d9b3bc7c4a (/usr/lib/chromium/chromium+0x53b7c49) #17 0x55d9b25bc78b (/usr/lib/chromium/chromium+0x3dac78a) #18 0x55d9b25bc7ce (/usr/lib/chromium/chromium+0x3dac7cd) #19 0x55d9b1addca7 (/usr/lib/chromium/chromium+0x32cdca6) #20 0x55d9b25657c3 (/usr/lib/chromium/chromium+0x3d557c2) #21 0x55d9b259bd99 (/usr/lib/chromium/chromium+0x3d8bd98) #22 0x55d9b25eb921 (/usr/lib/chromium/chromium+0x3ddb920) #23 0x55d9b25ebbde (/usr/lib/chromium/chromium+0x3ddbbdd) #24 0x55d9b25b8847 (/usr/lib/chromium/chromium+0x3da8846) #25 0x55d9b25b889e (/usr/lib/chromium/chromium+0x3da889d) #26 0x55d9b25bc7a0 (/usr/lib/chromium/chromium+0x3dac79f) #27 0x55d9b25bc7ce (/usr/lib/chromium/chromium+0x3dac7cd) #28 0x55d9b1addca7 (/usr/lib/chromium/chromium+0x32cdca6) #29 0x55d9b1e54403 (/usr/lib/chromium/chromium+0x3644402) #30 0x55d9b21f2e3c (/usr/lib/chromium/chromium+0x39e2e3b) #31 0x55d9b41cff9f (/usr/lib/chromium/chromium+0x59bff9e) #32 0x55d9b41d65a7 (/usr/lib/chromium/chromium+0x59c65a6) #33 0x55d9b41d48b9 (/usr/lib/chromium/chromium+0x59c48b8) #34 0x55d9b41d370e (/usr/lib/chromium/chromium+0x59c370d) #35 0x55d9b41cd128 (/usr/lib/chromium/chromium+0x59bd127) #36 0x55d9b41e6ebe (/usr/lib/chromium/chromium+0x59d6ebd) #37 0x55d9b41e7336 (/usr/lib/chromium/chromium+0x59d7335) #38 0x55d9b3c057d4 (/usr/lib/chromium/chromium+0x53f57d3) #39 0x55d9b3c15aa9 (/usr/lib/chromium/chromium+0x5405aa8) #40 0x55d9b3c157ac (/usr/lib/chromium/chromium+0x54057ab) #41 0x55d9b3bc98da (/usr/lib/chromium/chromium+0x53b98d9) #42 0x55d9b3c1610d (/usr/lib/chromium/chromium+0x540610c) #43 0x55d9b3bec1a0 (/usr/lib/chromium/chromium+0x53dc19f) #44 0x55d9b3da164c (/usr/lib/chromium/chromium+0x559164b) #45 0x55d9b21878a2 (/usr/lib/chromium/chromium+0x39778a1) #46 0x55d9b2189842 (/usr/lib/chromium/chromium+0x3979841) #47 0x55d9b21847dd (/usr/lib/chromium/chromium+0x39747dc) #48 0x55d9b3b8f491 (/usr/lib/chromium/chromium+0x537f490) #49 0x55d9b3b8f0c4 (/usr/lib/chromium/chromium+0x537f0c3) #50 0x55d9b3b8ca4b (/usr/lib/chromium/chromium+0x537ca4a) #51 0x55d9b3b8d32e (/usr/lib/chromium/chromium+0x537d32d) #52 0x55d9b14b3c13 ChromeMain #53 0x7f4327a1fd0a __libc_start_main #54 0x55d9b14b3aaa _start r8: 0077 r9: r10: 006e r11: 0050 r12: 7f4327bb7b80 r13: 7f4327bb7b90 r14: 55d9bd0921e0 r15: 0020 di: 0021 si: 0004 bp: 0020 bx: 5501bc87063f dx: 7f4327bb7be0 ax: 55d9bd07c160 cx: 5501bc87063f sp: 7ffd9917eb80 ip: 7f4327a7f80c efl: 00010206 cgf: 002b0033 erf: 0004 trp: 000e msk: cr2: 5501bc870647 [end of stack trace] Calling _exit(1)
Processed: Re: Bug#974778: llvmlite: Please upgrade to llvm-toolchain-11
Processing control commands: > retitle -1 llvmlite: stop using llvm-toolchain-10 Bug #974778 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11 Bug #974824 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11 Changed Bug title to 'llvmlite: stop using llvm-toolchain-10' from 'llvmlite: Please upgrade to llvm-toolchain-11'. Changed Bug title to 'llvmlite: stop using llvm-toolchain-10' from 'llvmlite: Please upgrade to llvm-toolchain-11'. > severity -1 serious Bug #974778 [src:llvmlite] llvmlite: stop using llvm-toolchain-10 Bug #974824 [src:llvmlite] llvmlite: stop using llvm-toolchain-10 Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' -- 974778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974778 974824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973154: apertium-kaz-tat: FTBFS: hfst-concatenate: .deps/any-symbol.hfst is not a valid transducer file
I can't seem to reproduce this, can you initiate a rebuild for this? I suspect if new apertium upload fixed this somehow. Attaching the log in any case. sbuild (Debian sbuild) 0.79.1 (22 April 2020) on debian +==+ | apertium-kaz-tat 0.2.1~r57554-2 (amd64) Thu, 24 Dec 2020 08:25:40 + | +==+ Package: apertium-kaz-tat Version: 0.2.1~r57554-2 Source Version: 0.2.1~r57554-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-b27305c8-3be6-49f0-9b40-e92c932753f1' with '<>' I: NOTICE: Log filtering will replace 'build/apertium-kaz-tat-9yNg7D/resolver-JCSpih' with '<>' +--+ | Update chroot| +--+ Get:1 http://127.0.0.1:3142/ftp.debian.org/debian sid InRelease [153 kB] Get:2 http://127.0.0.1:3142/ftp.debian.org/debian sid/main Sources.diff/Index [27.9 kB] Get:3 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 kB] Get:4 http://127.0.0.1:3142/ftp.debian.org/debian sid/main Sources 2020-12-23-1401.30.pdiff [17.2 kB] Get:5 http://127.0.0.1:3142/ftp.debian.org/debian sid/main Sources 2020-12-23-2000.32.pdiff [20.5 kB] Get:6 http://127.0.0.1:3142/ftp.debian.org/debian sid/main Sources 2020-12-24-0200.31.pdiff [11.4 kB] Get:7 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 Packages 2020-12-23-1401.30.pdiff [35.6 kB] Get:8 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 Packages 2020-12-23-2000.32.pdiff [18.5 kB] Get:6 http://127.0.0.1:3142/ftp.debian.org/debian sid/main Sources 2020-12-24-0200.31.pdiff [11.4 kB] Get:9 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 Packages 2020-12-24-0200.31.pdiff [15.9 kB] Get:9 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 Packages 2020-12-24-0200.31.pdiff [15.9 kB] Fetched 328 kB in 4s (73.1 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages were automatically installed and are no longer required: alsa-topology-conf alsa-ucm-conf bsdextrautils ca-certificates krb5-locales libnss-nis libnss-nisplus netbase openssl sensible-utils Use 'apt autoremove' to remove them. The following packages will be upgraded: binutils binutils-common binutils-x86-64-linux-gnu libbinutils libctf-nobfd0 libctf0 tzdata 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 5102 kB of archives. After this operation, 4096 B of additional disk space will be used. Get:1 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 tzdata all 2020e-1 [284 kB] Get:2 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 libctf0 amd64 2.35.1-6 [53.4 kB] Get:3 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 libctf-nobfd0 amd64 2.35.1-6 [109 kB] Get:4 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 binutils-x86-64-linux-gnu amd64 2.35.1-6 [1806 kB] Get:5 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 libbinutils amd64 2.35.1-6 [571 kB] Get:6 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 binutils amd64 2.35.1-6 [60.4 kB] Get:7 http://127.0.0.1:3142/ftp.debian.org/debian sid/main amd64 binutils-common amd64 2.35.1-6 [2218 kB] Preconfiguring packages ... Fetched 5102 kB in 0s (12.6 MB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17629 files and directories currently installed.) Preparing to unpack .../0-tzdata_2020e-1_all.deb ... Unpacking tzdata (2020e-1) over (2020d-1) ... Preparing to unpack .../1-libctf0_2.35.1-6_amd64.deb ... Unpacking libctf0:amd64 (2.35.1-6) over (2.35.1-5) ... Preparing to unpack .../2-libctf-nobfd0_2.35.1-6_amd64.deb ... Unpacking libctf-nobfd0:amd64 (2.35.1-6) over (2.35.1-5) ... Preparing to unpack .../3-binutils-x86-64-linux-gnu_2.35.1-6_amd64.deb ... Unpacking binutils-x86-64-linux-gnu (2.35.1-6) over (2.35.1-5) ... Preparing to unpack .../4-libbinutils_2.35.1-6_amd64.deb ... Unpacking libbinutils:amd64 (2.35.1-6) over (2.35.1-5) ... Preparing to unpack .../5-binutils_2.35
Bug#978002: clfft: autopkgtest regression
Source: clfft Version: 2.12.2-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org clfft is unable to migrate to testing due to autopkgtest regressions: | autopkgtest [23:13:07]: test build-examples: [--- | cp: cannot stat '/usr/share/doc/libclfft-doc/examples/*': No such file or directory | autopkgtest [23:13:08]: test build-examples: ---] | autopkgtest [23:13:08]: test build-examples: - - - - - - - - - - results - - - - - - - - - - | build-examples FAIL non-zero exit status 1 https://ci.debian.net/data/autopkgtest/testing/amd64/c/clfft/9036543/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: snapcast: switch to default libboost-dev
Processing control commands: > block 978000 by -1 Bug #978000 [src:boost1.71] boost1.71: should not be part of bullseye 978000 was not blocked by any bugs. 978000 was not blocking any bugs. Added blocking bug(s) of 978000: 978001 -- 978000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978000 978001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978001: snapcast: switch to default libboost-dev
Source: snapcast Version: 0.19.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 978000 by -1 snapcast currently has build dependency on libboost1.71-dev but we are trying to remove boost 1.71 from bullseye. So, please switch to the unversioned libboost-dev which currently points to 1.74. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#978000: boost1.71: should not be part of bullseye
Source: boost1.71 Version: 1.71.0-7 Severity: serious X-Debbugs-Cc: sramac...@debian.org With boost 1.74 as the default, let's make sure that boost 1.71 is not part of bullseye. Once the remanining reverse dependencies are fixed, please reassign this bug to ftp.debian.org and get it removed. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#977901: chromium: Inconsistent SEGV
Hello, Yes, I gave you the wrong file. Just uploaded the correct one under the same url. Michel Le Bihan Le mercredi 23 décembre 2020 à 23:01 -0600, Boyd Stephen Smith Jr. a écrit : > On Wednesday, December 23, 2020 4:16:19 PM CST Michel Le Bihan wrote: > > Could you please test if you are still getting > > this issue in https://lebihan.pl/files/chromium.tar.gz ? > > Chromium ran for several hours continuously with all my extensions > enabled, > but did eventually crash (attached), with a similar back trace: > ~ServiceWorkerRegistrationObjectHost ... std::_Rb_tree<>::_M_erase > ... > ~ServiceWorkerRegistrationObjectHost > > Note that I'm not sure the link you gave is correct and up-to-date, > as the > version of packages that I downloaded from there and installed (via > dpkg) is > less than the current version in sid: > > ---8<--- > % apt-cache policy chromium > chromium: > Installed: 87.0.4280.88-0.1 > Candidate: 87.0.4280.88-0.1 > Version table: > 87.0.4280.88-0.2 -1 > 500 http://deb.debian.org/debian sid/main amd64 Packages > *** 87.0.4280.88-0.1 100 > 100 /var/lib/dpkg/status > --->8--- > > Let me know what I can do to help.
