Bug#1011166: [Debian-on-mobile-maintainers] Bug#1011166: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0
On 5/19/22 04:04, Evangelos Ribeiro Tzaras wrote: Thanks for the patch! I'll upload a fixed version soon. If you upload a new version, you (or I) can then close the binNMU request, bug #1011201. -- Richard OpenPGP_signature Description: OpenPGP digital signature
Bug#1010726: marked as done (libricohcamerasdk-dev must have the same architecture list as libricohcamerasdk)
Your message dated Thu, 19 May 2022 22:11:23 + (UTC) with message-id and subject line Bug#1010726: fixed in libricohcamerasdk 1.1.0-3 has caused the Debian Bug report #1010726, regarding libricohcamerasdk-dev must have the same architecture list as libricohcamerasdk 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.) -- 1010726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libricohcamerasdk-dev Version: libricohcamerasdk-dev Severity: serious ∙ libricohcamerasdk-dev/armel has unsatisfiable dependency ∙ libricohcamerasdk-dev/i386 has unsatisfiable dependency Building libricohcamerasdk-dev on architectures where its dependency libricohcamerasdk is not being built makes libricohcamerasdk-dev uninstallable. --- End Message --- --- Begin Message --- Source: libricohcamerasdk Source-Version: 1.1.0-3 Done: Thorsten Alteholz Forgot to close it with the upload, so manually closing it now. Thorsten--- End Message ---
Processed: Re: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen
Processing commands for cont...@bugs.debian.org: > tags 1004740 upstream fixed-upstream Bug #1004740 [exim4] exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen Added tag(s) upstream and fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 1004740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#980957: llvm-toolchain-11 autopkgtest segfaults on armhf
Processing control commands:
> clone -1 -2
Bug #980957 [src:llvm-toolchain-11] llvm-toolchain-11 autopkgtest segfaults on
armhf
Bug 980957 cloned as bug 1011312
> reassign -2 src:llvm-toolchain-14
Bug #1011312 [src:llvm-toolchain-11] llvm-toolchain-11 autopkgtest segfaults on
armhf
Bug reassigned from package 'src:llvm-toolchain-11' to 'src:llvm-toolchain-14'.
No longer marked as found in versions llvm-toolchain-11/1:11.0.0-2.
Ignoring request to alter fixed versions of bug #1011312 to the same values
previously set
> retitle -2 llvm-toolchain-14 autopkgtest segfaults on armhf
Bug #1011312 [src:llvm-toolchain-14] llvm-toolchain-11 autopkgtest segfaults on
armhf
Changed Bug title to 'llvm-toolchain-14 autopkgtest segfaults on armhf' from
'llvm-toolchain-11 autopkgtest segfaults on armhf'.
> notforwarded -2
Bug #1011312 [src:llvm-toolchain-14] llvm-toolchain-14 autopkgtest segfaults on
armhf
Unset Bug forwarded-to-address
> severity -2 serious
Bug #1011312 [src:llvm-toolchain-14] llvm-toolchain-14 autopkgtest segfaults on
armhf
Ignoring request to change severity of Bug 1011312 to the same value.
> block 1009923 by -1
Bug #1009923 {Done: Paul Gevers } [src:cvise] src:cvise:
fails to migrate to testing for too long: build depends on package that fails
to migrate
1009923 was not blocked by any bugs.
1009923 was not blocking any bugs.
Added blocking bug(s) of 1009923: 980957
--
1009923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009923
1011312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011312
980957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980957: llvm-toolchain-11 autopkgtest segfaults on armhf
Control: clone -1 -2 Control: reassign -2 src:llvm-toolchain-14 Control: retitle -2 llvm-toolchain-14 autopkgtest segfaults on armhf Control: notforwarded -2 Control: severity -2 serious Control: block 1009923 by -1 On Tue, Sep 21, 2021 at 04:28:12PM -0400, Nicholas D Steeves wrote: > Hi Gianfranco, > > On Sun, Mar 28, 2021 at 09:11:49PM +0200, Gianfranco Costamagna wrote: > > control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27659 > > control: affects -1 src:binutils > > > > Invoking the clang with -V shows a failure in ld.bdf linker, a failure that > > doesn't happen with gold linker and with object files (crt*.o) copied on > > local directory. > > > > I opened a bug against binutils people to track it down, hopefully they can > > sort what is segfaulting there. > > > > Does the following upstream reverted commit unblock this bug, thus > unblocking llvm-toolchain-12 from migrating to testing? > > https://sourceware.org/bugzilla/show_bug.cgi?id=27659#c17 It is now included in the binutils in unstable, and does not appear to have fixed it. This issue is also present in llvm-toolchain-14, and currently blocking testing migration there: https://ci.debian.net/packages/l/llvm-toolchain-14/unstable/armhf/ > Regards, > Nicholas cu Adrian
Processed: unarchiving 987216, unarchiving 991351, fixed 987216 in 390.144-1~deb9u1 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 987216
Bug #987216 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2021-1076,
CVE-2021-1077
Unarchived Bug 987216
> unarchive 991351
Bug #991351 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2021-1093,
CVE-2021-1094, CVE-2021-1095
Unarchived Bug 991351
> fixed 987216 390.144-1~deb9u1
Bug #987216 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2021-1076,
CVE-2021-1077
The source 'nvidia-graphics-drivers' and version '390.144-1~deb9u1' do not
appear to match any binary packages
Marked as fixed in versions nvidia-graphics-drivers/390.144-1~deb9u1.
> fixed 991351 390.144-1~deb9u1
Bug #991351 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2021-1093,
CVE-2021-1094, CVE-2021-1095
The source 'nvidia-graphics-drivers' and version '390.144-1~deb9u1' do not
appear to match any binary packages
Marked as fixed in versions nvidia-graphics-drivers/390.144-1~deb9u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
987216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987216
991351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1011272 to buster-pu: package nvidia-graphics-drivers-legacy-390xx/390.151-1~deb10u1 ...
Processing commands for cont...@bugs.debian.org:
> retitle 1011272 buster-pu: package
> nvidia-graphics-drivers-legacy-390xx/390.151-1~deb10u1
Bug #1011272 [release.debian.org] bullseye-pu: package
nvidia-graphics-drivers-legacy-390xx/390.151-1~deb11u1
Changed Bug title to 'buster-pu: package
nvidia-graphics-drivers-legacy-390xx/390.151-1~deb10u1' from 'bullseye-pu:
package nvidia-graphics-drivers-legacy-390xx/390.151-1~deb11u1'.
> tags 1010230 - unreproducible
Bug #1010230 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers-legacy-390xx]
nvidia-graphics-drivers-legacy-390xx: spurious module build failure in
autopkgtest on armhf
Removed tag(s) unreproducible.
> tags 104 - bookworm sid
Bug #104 [src:nvidia-cuda-toolkit] nivdia-cuda-toolkit: hardcodes
dependencies on libssl1.1
Bug #1011243 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: Hard dependency on
libssl1.1
Removed tag(s) sid and bookworm.
Removed tag(s) sid and bookworm.
> tags 1010691 + experimental
Bug #1010691 {Done: Paul Gevers }
[src:golang-github-sylabs-sif] src:golang-github-sylabs-sif: fails to migrate
to testing for too long: autopkgtest regression
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010230
1010691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010691
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
1011243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011243
1011272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010998: simh: Upstream license change conflicts with DFSG
As an alternative, Bob Supnik's "classic" version continues to release - version 2.12-2 just released 25 April 2022 - and would be an excellent replacement. http://simh.trailing-edge.com/ Unfortunately, that version still must overcome the licensing issues outlined in Debian bug #824883.
Processed: closing 987325
Processing commands for cont...@bugs.debian.org: > close 987325 8.0.28-1 Bug #987325 [src:mysql-8.0] mysql-8.0: Security fixes from the April 2021 CPU Bug #988718 [src:mysql-8.0] Security fixes from the April 2021 Patch Update Marked as fixed in versions mysql-8.0/8.0.28-1. Marked as fixed in versions mysql-8.0/8.0.28-1. Bug #987325 [src:mysql-8.0] mysql-8.0: Security fixes from the April 2021 CPU Bug #988718 [src:mysql-8.0] Security fixes from the April 2021 Patch Update Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 987325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987325 988718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987325: closing 987325
close 987325 8.0.28-1 thanks
Processed: Re: luajit SEGFAULTS on ppc64el
Processing commands for cont...@bugs.debian.org: > clone 1004511 -1 -14 Bug #1004511 [src:luajit] luajit SEGFAULTs on ppc64el Bug 1004511 cloned as bugs 1011296-1011297 1008069 was blocked by: 1004511 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011296 1008069 was blocked by: 1004511 1011296 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011297 > block 1004511 by -1 Bug #1004511 [src:luajit] luajit SEGFAULTs on ppc64el 1004511 was not blocked by any bugs. 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011296 > retitle -1 please replace (build) dependency luajit with lua on ppc64el Bug #1011296 [src:luajit] luajit SEGFAULTs on ppc64el Changed Bug title to 'please replace (build) dependency luajit with lua on ppc64el' from 'luajit SEGFAULTs on ppc64el'. > retitle 1004511 RM: luajit [ppc64el] -- ROP; segfaults Bug #1004511 [src:luajit] luajit SEGFAULTs on ppc64el Changed Bug title to 'RM: luajit [ppc64el] -- ROP; segfaults' from 'luajit SEGFAULTs on ppc64el'. > severity 1004511 normal Bug #1004511 [src:luajit] RM: luajit [ppc64el] -- ROP; segfaults Severity set to 'normal' from 'serious' > reassign 1004511 ftp.debian.org Bug #1004511 [src:luajit] RM: luajit [ppc64el] -- ROP; segfaults Bug reassigned from package 'src:luajit' to 'ftp.debian.org'. No longer marked as found in versions luajit/2.1.0~beta3+git20210112+dfsg-2. Ignoring request to alter fixed versions of bug #1004511 to the same values previously set > clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 Bug #1011296 [src:luajit] please replace (build) dependency luajit with lua on ppc64el Bug 1011296 cloned as bugs 1011298-1011309 1004511 was blocked by: 1011296 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011298 1004511 was blocked by: 1011298 1011296 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011299 1004511 was blocked by: 1011296 1011299 1011298 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011300 1004511 was blocked by: 1011298 1011296 1011299 1011300 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011301 1004511 was blocked by: 1011300 1011299 1011301 1011296 1011298 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011302 1004511 was blocked by: 1011299 1011300 1011301 1011296 1011302 1011298 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011303 1004511 was blocked by: 1011303 1011300 1011299 1011301 1011302 1011298 1011296 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011304 1004511 was blocked by: 1011303 1011301 1011299 1011304 1011300 1011296 1011298 1011302 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011305 1004511 was blocked by: 1011303 1011305 1011301 1011300 1011299 1011304 1011296 1011298 1011302 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011306 1004511 was blocked by: 1011303 1011305 1011306 1011301 1011304 1011300 1011299 1011296 1011298 1011302 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011307 1004511 was blocked by: 1011305 1011306 1011303 1011299 1011304 1011300 1011301 1011296 1011302 1011298 1011307 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011308 1004511 was blocked by: 1011308 1011303 1011306 1011305 1011301 1011300 1011304 1011299 1011298 1011302 1011307 1011296 1004511 was blocking: 1008069 Added blocking bug(s) of 1004511: 1011309 1008069 was blocked by: 1011296 1004511 1011297 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011298 1008069 was blocked by: 1011298 1011296 1011297 1004511 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011299 1008069 was blocked by: 1011298 1011296 1011297 1011299 1004511 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011300 1008069 was blocked by: 1011298 1011296 1011297 1011300 1011299 1004511 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011301 1008069 was blocked by: 1011298 1011296 1011297 1004511 1011301 1011299 1011300 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011302 1008069 was blocked by: 1004511 1011301 1011299 1011300 1011297 1011296 1011298 1011302 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011303 1008069 was blocked by: 1011297 1011300 1011299 1011301 1004511 1011303 1011302 1011298 1011296 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011304 1008069 was blocked by: 1011301 1011304 1011299 1011300 1011303 1004511 1011297 1011296 1011298 1011302 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011305 1008069 was blocked by: 1011297 1011305 1011301 1011296 1011303 1004511 1011300 1011299 1011304 1011298 1011302 1008069 was not blocking any bugs. Added blocking bug(s) of 1008069: 1011306 1008069 was blocked by: 1011300 1011304 1011299 1011303 1004511 1011298 1011302 1011297 1011301 1011306 1011305
Bug#1004511: luajit SEGFAULTS on ppc64el
clone 1004511 -1 -14 block 1004511 by -1 retitle -1 please replace (build) dependency luajit with lua on ppc64el retitle 1004511 RM: luajit [ppc64el] -- ROP; segfaults severity 1004511 normal reassign 1004511 ftp.debian.org clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 reassign -1 src:aegisub 3.2.2+dfsg-6 reassign -2 src:ettercap 1:0.8.3.1-6 reassign -3 src:knot-resolver 5.4.4-1 reassign -4 src:love 11.3-1 reassign -5 src:luakit 1:2.3-1 reassign -6 src:nageru 2.1.0-1 reassign -7 src:nginx 1.20.2-2 reassign -8 src:obs-studio 27.2.4+dfsg1-1 reassign -9 src:rspamd 3.2-1 reassign -10 src:snort 2.9.15.1-6 reassign -11 src:sysbench 1.0.20+ds-2 reassign -12 src:trafficserver 9.1.2+ds-1 reassign -13 src:uwsgi-plugin-luajit 0.0.7 retitle -14 please prevent successful build on ppc64el until it works thanks Hi, On 19-05-2022 16:34, Frédéric Bonnard wrote: Hi Paul, sorry for the late reply. As I said on debian-devel, I've not enough expertise nor hope on that topic. Switching to lua is the way I went a few times, instead on relying on luajit. F. On Mon, 02 May 2022 07:55:50 +0200 Paul Gevers wrote: If this issue is difficult to fix, how about removing luajit from ppc64el? I noticed that the only reverse (build) dependent key package of luajit (src:efl) already switched to plain lua on ppc64el (probably because of this issue). Not convinced I'm totally right there's no key packages in the list above, but let's go this route unless somebody puts up the effort to *maintain* the ppc64el parts. The list above only includes direct depends of libluajit-5.1, I still need to figure out which packages build depend on libluajit-5.1-dev on ppc64el and successfully build there. For the bug which remains assigned to luajit, I want it to ensure that in the future we don't accidentally have a successful build on ppc64el with broken content, so please either drop ppc64el from the list of architectures for which it builds or, better, add a build-time test that fails while luajit segfaults. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Clarify found package
Processing commands for cont...@bugs.debian.org:
> found 1000866 debianutils/5.5-1
Bug #1000866 {Done: Bastian Blank } [src:debianutils] Source
package is missing files required to make a derived work
Marked as found in versions debianutils/5.5-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1000866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package gpaste
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gpaste > # 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 #1010901 (http://bugs.debian.org/1010901) > # Bug title: missing license information > # * https://github.com/Keruspe/GPaste/issues/398 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1010901 + fixed-upstream Bug #1010901 [gpaste] missing license information Added tag(s) fixed-upstream. > usertags 1010901 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:q2cli
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:q2cli
> # 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 #997488 (http://bugs.debian.org/997488)
> # Bug title: q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
> -i python{version} -p 3.9 returned exit code 13
> # * https://github.com/qiime2/q2cli/issues/259
> # * remote status changed: open -> closed
> # * closed upstream
> tags 997488 + fixed-upstream
Bug #997488 [src:q2cli] q2cli: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) fixed-upstream.
> usertags 997488 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 997488 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1011279: marked as done (node-dateformat CJS file does not provide the same API than ES file)
Your message dated Thu, 19 May 2022 17:19:42 + with message-id and subject line Bug#1011279: fixed in node-dateformat 5.0.3-5 has caused the Debian Bug report #1011279, regarding node-dateformat CJS file does not provide the same API than ES file 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.) -- 1011279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-dateformat Version: 5.0.3-1 Severity: serious Tags: ftbfs Justification: FTBFS Control: affects -1 grunt node-lightgallery Following upstream doc, `import d from 'dateformat'` is a function. The file built with `babeljs --plugins @babel/transform-modules-commonjs` produces an Object, usable function is d.default. This breaks grunt (try to build node-lightgallery for example). This can be fixed using `mjs2cjs -a` and a custom `debian/index.cjs` --- End Message --- --- Begin Message --- Source: node-dateformat Source-Version: 5.0.3-5 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of node-dateformat, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-dateformat 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, 19 May 2022 22:15:41 +0530 Source: node-dateformat Architecture: source Version: 5.0.3-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 1011279 Changes: node-dateformat (5.0.3-5) unstable; urgency=medium . * Team upload . [ Yadd ] * Declare compliance with policy 4.6.1 * Fix commonjs export (Closes: #1011279) Checksums-Sha1: de2e3eb6c23d34e9f4d1c0e06179f019ca624fc7 2243 node-dateformat_5.0.3-5.dsc 09c91b9c80a74609ff54655fe1dce75900e09b86 4136 node-dateformat_5.0.3-5.debian.tar.xz 1ade690910d9122d5cb07ba39883011589dc32eb 14038 node-dateformat_5.0.3-5_amd64.buildinfo Checksums-Sha256: 9705146557ebc3179b36642ac573480e78e4ffbf6a78c2b2ee17072969eb7eb3 2243 node-dateformat_5.0.3-5.dsc b836ead42701125e5e72bd9286a30f10166b547d3bc31e8d0d2bf4e0f34f2201 4136 node-dateformat_5.0.3-5.debian.tar.xz ea1f750db36c9933ee19c74eabf857dc02bd955f35aea376a017b8883645b3b2 14038 node-dateformat_5.0.3-5_amd64.buildinfo Files: 3f4f52f4906c702784a4d73407bda2fe 2243 javascript optional node-dateformat_5.0.3-5.dsc db234cd19aaec00bfa6127b9838ab792 4136 javascript optional node-dateformat_5.0.3-5.debian.tar.xz 1072f320f12dc3afa824e46dd19d81aa 14038 javascript optional node-dateformat_5.0.3-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmKGeXoACgkQj1PgGTsp S3VAcw/+PGJR8bAaAQTw5PaGhtiEgPkgZj92N+CSOqjfFutF07nxq6LW3ZD3KjAD ZZyIjRGIIFuefpWNjZzkDhppByHj0MeDyV5oKSAzwU+gJKZ7gXwy1FdTUfcWFwUu mBsuvDgRtZ6njDFJk3z7kPG/zG+pPkyO7xRRD54LjMiYzzUdN7EprquZIUZ3mOwE Dm+UXvcf689utDCKZjm7S4qFFxSToZ4K0yvl2NKE7ejXOw+0UWc2EdV3e8eDgZUq 0xnAQP6aY8d02wEcc08UjxV5Ljzi+b1A624XSqxGxkXHXLngYOfMQWzOSb5LLLRN EpAYlFraFnU0SeuUFvvY+pShJ/s00VvyMATw/YaxP3UObsm2X5CjO4ydGya10nM2 0mDLfylou8o3UCOKiR1a6AW/uQ0XX1M4LGjQcycbOi5scwZnVqoI+uaMLwl5YkvH f98wR6uFiOZBsZNDBun/4RWbEsqReXjIpqEUr8JVGsmQfxpDrVjkM2oYXvW+fTq6 lLJikv2gkD2cL/PlVDoy9BUopdG1ouY512UrIG+ksnlBRZvbCSYoIVYbOStqGx+L NE623m029J090dLBppL6eFzP8gH2e+Pul1E5xDAWkkZRihxA+ir3z9SXo9GZ7dZb UsRd60cZJt2hLaM4TtXTUvvFE1CCWDGt0ORUwsMfurEpypp9Kxk= =3WUW -END PGP SIGNATURE End Message ---
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Control: severity -1 normal Hey, > # envfrom2srs > Traceback (most recent call last): > File "/usr/bin/envfrom2srs", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > # srs2envtol > Traceback (most recent call last): > File "/usr/bin/srs2envtol", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > No need to clutter the archive with broken and untested packages. > Please remove can you please use a less offensive language. It is only the two example scripts, that are not properly ported to Python 3. With a big warning in the top of the file: # Use only if absolutely necessary. It is *very* inefficient and # a security risk. This was fixed upstream, but they not have released a new version. Regards, hefee signature.asc Description: This is a digitally signed message part.
Processed: Re: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Processing control commands: > severity -1 normal Bug #1008829 [pysrs-bin] pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser' Severity set to 'normal' from 'grave' -- 1008829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1011279 marked as pending in node-dateformat
Processing control commands: > tag -1 pending Bug #1011279 [node-dateformat] node-dateformat CJS file does not provide the same API than ES file Added tag(s) pending. -- 1011279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011279: marked as pending in node-dateformat
Control: tag -1 pending Hello, Bug #1011279 in node-dateformat 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-dateformat/-/commit/83b246a24e56b5f8d3fc7a9676b7886d1299 Fix commonjs export Closes: #1011279 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011279
Bug#996287: marked as done (git-crypt: FTBFS with OpenSSL 3.0)
Your message dated Thu, 19 May 2022 16:05:48 +
with message-id
and subject line Bug#996287: fixed in git-crypt 0.7.0-0.1
has caused the Debian Bug report #996287,
regarding git-crypt: FTBFS with OpenSSL 3.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
996287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-crypt
Version: 0.6.0-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
crypto-openssl-10.cpp: In constructor
Aes_ecb_encryptor::Aes_ecb_encryptor(const unsigned char*):
crypto-openssl-10.cpp:59:60: warning: int AES_set_encrypt_key(const unsigned
char*, int, AES_KEY*) is deprecated: Since OpenSSL 3.0
[-Wdeprecated-declarations]
59 | if (AES_set_encrypt_key(raw_key, KEY_LEN * 8, &(impl->key)) != 0) {
|^
In file included from crypto-openssl-10.cpp:38:
/usr/include/openssl/aes.h:51:5: note: declared here
51 | int AES_set_encrypt_key(const unsigned char *userKey, const int bits,
| ^~~
crypto-openssl-10.cpp: In member function void Aes_ecb_encryptor::encrypt(const
unsigned char*, unsigned char*):
crypto-openssl-10.cpp:74:41: warning: void AES_encrypt(const unsigned char*,
unsigned char*, const AES_KEY*) is deprecated: Since OpenSSL 3.0
[-Wdeprecated-declarations]
74 | AES_encrypt(plain, cipher, &(impl->key));
| ^
In file included from crypto-openssl-10.cpp:38:
/usr/include/openssl/aes.h:57:6: note: declared here
57 | void AES_encrypt(const unsigned char *in, unsigned char *out,
| ^~~
crypto-openssl-10.cpp: At global scope:
crypto-openssl-10.cpp:78:11: error: field ctx has incomplete type HMAC_CTX {aka
hmac_ctx_st}
78 | HMAC_CTX ctx;
| ^~~
In file included from /usr/include/openssl/evp.h:26,
from /usr/include/openssl/hmac.h:21,
from crypto-openssl-10.cpp:40:
/usr/include/openssl/types.h:132:16: note: forward declaration of HMAC_CTX {aka
struct hmac_ctx_st}
132 | typedef struct hmac_ctx_st HMAC_CTX;
|^~~
crypto-openssl-10.cpp: In destructor Hmac_sha1_state::~Hmac_sha1_state():
crypto-openssl-10.cpp:92:2: error: HMAC_cleanup was not declared in this scope;
did you mean EVP_cleanup?
92 | HMAC_cleanup(&(impl->ctx));
| ^~~~
| EVP_cleanup
make[1]: *** [: crypto-openssl-10.o] Error 1
Kurt
--- End Message ---
--- Begin Message ---
Source: git-crypt
Source-Version: 0.7.0-0.1
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
git-crypt, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated git-crypt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 14 May 2022 11:20:28 -0400
Source: git-crypt
Architecture: source
Version: 0.7.0-0.1
Distribution: unstable
Urgency: high
Maintainer: Andrew Ayer
Changed-By: Boyuan Yang
Closes: 917346 996287
Changes:
git-crypt (0.7.0-0.1) unstable; urgency=high
.
* Non-maintainer upload.
* New upstream release.
* Cherry-pick Ubuntu patch to fix compatibility with OpenSSL 3.0.
(Closes: #996287)
* debian/control: Drop obsolete build-dependency libssl1.0-dev.
(Closes: #917346)
Checksums-Sha1:
e6619f60c4d7df2a75636b92b441a539393fc30d 1836 git-crypt_0.7.0-0.1.dsc
5dc652405e94e6918bf3865aa054d2014a1b91c4 57621 git-crypt_0.7.0.orig.tar.gz
dcad314d95d44a0d6160c7ad5999a0bc63ab32bb 10312
git-crypt_0.7.0-0.1.debian.tar.xz
d29af15d9a260ec3c8c73dd563a288ae5e89f3b7 6251
git-crypt_0.7.0-0.1_amd64.buildinfo
Checksums-Sha256:
70a546084c03d49b502c26de362b88329420797d3a0a099ae6f6c44c2c8ec588 1836
git-crypt_0.7.0-0.1.dsc
50f100816a636a682404703b6c23a459e4d30248b2886a5cf571b0d52527c7d8 57621
git-crypt_0.7.0.orig.tar.gz
Bug#1009433: marked as done (projectile: FTBFS: Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav' instead.)
Your message dated Thu, 19 May 2022 16:07:44 + with message-id and subject line Bug#1009433: fixed in projectile 2.1.0-1.1 has caused the Debian Bug report #1009433, regarding projectile: FTBFS: Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav' instead. 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.) -- 1009433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: projectile Version: 2.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with elpa --with mkdocs >dh_update_autotools_config >dh_autoreconf >dh_auto_configure >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > LANG=C.UTF-8 LC_ALL=C.UTF-8 mkdocs build --clean > [33mWARNING - [0mConfig value: 'site_favicon'. Warning: Unrecognised > configuration name: site_favicon > [31mERROR- [0mConfig value: 'pages'. Error: The configuration option > 'pages' was removed from MkDocs. Use 'nav' instead. > Aborted with 1 Configuration Errors! > make[1]: *** [debian/rules:8: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/projectile_2.1.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results 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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: projectile Source-Version: 2.1.0-1.1 Done: Thomas Koch We believe that the bug you reported is fixed in the latest version of projectile, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Koch (supplier of updated projectile 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, 19 May 2022 17:10:12 +0300 Source: projectile Architecture: source Version: 2.1.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: Thomas Koch Closes: 1009433 Changes: projectile (2.1.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS due to mkdocs changes. (Closes: #1009433) Checksums-Sha1: b104323a492911ae66b4934523d484eb6a1f0005 2052 projectile_2.1.0-1.1.dsc 4135eb1ce87573711ee6ff98dcac5c0cb99bad57 8784 projectile_2.1.0-1.1.debian.tar.xz Checksums-Sha256: a4c98538878ad6f162b7019b289374f9d0c5c1d2673fa99e5dcd0c4d8a8b98fe 2052 projectile_2.1.0-1.1.dsc f679a0e558c4bcca347aa74630b5e1611556ded59b23ba1ba190ca7dcb52959a 8784 projectile_2.1.0-1.1.debian.tar.xz Files: e25c915bf612ae331f9b92f11652b803 2052 lisp optional projectile_2.1.0-1.1.dsc 0f60af293007059f3745506128ace548 8784 lisp optional projectile_2.1.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdgQCBVl/ppbxMTvKB/xIkQQrploFAmKGZuUACgkQB/xIkQQr ploIGA/+N+uXfWOJbEyykopN0Ajr+HmFQ7gHP372L6ngc00fJyG+Gv3sAZm+LBOc aT1mDQPsUB5ZK288nUBYVSk9BTLCEtY30632dJUnb5lQxGTrBI4/9HcIOzFokOLC 7DBxoVBcGQ2WUC6tCTKmk8xGepbjGkOfH6Cg4z/49CwSVe8enDqnLSzqcunm08fK 4U/2HeGXcHvzwS6vI7d1ImQZwAU17H2pepaCxDgNlbX/Lwrex60JfuzLk5QkldA7 +ogfbqa32e4QaxGmol2R8j1VXfyJy1Q5bG76dbY/6K/A60nGttjjMUUrvfFCgopr ehHAAnTn6ANoCs2afXvI11kgBCSO+bcZj7KsCzQm+kHREbeVkbqnIoZHs5zeJ+ke J4smSqmCFxUpkXLsw3tUkCQ+fkIpszqdFBN41KD6Ahy068tYqNLhzw93oLDy7aKO
Bug#976439: marked as done (wminput: Aborts with "undefined symbol: PyVarObject_CallFunction")
Your message dated Thu, 19 May 2022 15:48:46 + with message-id and subject line Bug#976439: fixed in cwiid 0.6.91-4 has caused the Debian Bug report #976439, regarding wminput: Aborts with "undefined symbol: PyVarObject_CallFunction" 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.) -- 976439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wminput Version: 0.6.91-2+b1 Severity: important X-Debbugs-Cc: f...@debian.org Hello Georges, First of all, thank you so much for adopting cwiid and trying to port it to Python 3. I was trying get my Wiimote to work with RetroArch / RetroPie, and was following guides such as https://retropie.org.uk/docs/Wiimote-Controller/ to get it working, but when it comes time to run wminput, I was greeted with the following error: $ wminput ImportError: /usr/lib/python3/dist-packages/cwiid.cpython-39-x86_64-linux-gnu.so: undefined symbol: PyVarObject_CallFunction After some investigation, I suspect PyObject_CallFunction is not supposed to be renamed to PyVarObject_CallFunction even for porting from Python 2 to Python 3. Looking further, it seems that the port to Python 3 has already been done by Thomas Vitureau (a.k.a. azzra): Port of python-cwiid compatible with Python3 * https://pypi.org/project/cwiid/ * https://github.com/azzra/python3-wiimote Azzra based his work on Cwiid author Donnie Smith's own repository on GitHub at https://github.com/abstrakraft/cwiid , though probably for simplicity sake or for building a pure Python 3 module, Azzra decided to "Delete lswm, wmdemo, wminput, wmgui" from his python3-wiimote fork. Incidentally, there is a fork of Cwiid by Ivica Ico Bukvic and friends from Virgina Tech's L2Ork (Linux Laptop Orchestra): * https://github.com/pd-l2ork/cwiid though unfortunately it was forked before Donnie Smith converted his repo from svn to git, and there is essentially no commit history found in pd-l2ork/cwiid, and despite some contributed Python 3 related pull request, it fails to build successfully with Python 3 out of the box. So, what is the way forward? As a working Python 3 port already exists, I propose updating the Debian cwiid package with these existing works, though I admit that it would require some work to cherry-pick from azzra's python3-wiimote repo and to get wminput working with the Python-related code changes. Here are my recommendation: 1. Start by upgrading Debian's cwiid with Donnie Smith's latest code. I suggest modifying debian/watch to track his repo like so: version=4 opts="mode=git, pgpmode=none, pretty=0.6.91+git%cd.%h" \ https://github.com/abstrakraft/cwiid.git \ HEAD debian and run e.g. "gbp import-orig --sign-tags --uscan" to upgrade to this latest upstream snapshot from 2010. 2. Then, choose one of the following: a) Cherry-pick and modify the new commits from https://github.com/azzra/python3-wiimote/commits/master and place them in debian/patches/, or b) Fork https://github.com/abstrakraft/cwiid as https://github.com/Debian/cwiid (for example) to merge azzra/python3-wiimote while keeping lswm, wminput, etc. c) Build Debian's cwiid (from abstrakraft/cwiid) without Python 3 support, and package azzra/python3-wiimote as a separate source package producing the python3-cwiid binary package. What do you think? :-) If you like, I would be very happy to collaborate too if time allows. Cheers, Anthony -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wminput depends on: ii libbluetooth3 5.55-1 ii libc6 2.31-4 ii libcwiid1 0.6.91-2+b1 ii libpython3.9 3.9.0-5 ii python3-cwiid 0.6.91-2+b1 wminput recommends no packages. wminput suggests no packages. -- Configuration Files: /etc/cwiid/wminput/gamepad changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: cwiid Source-Version: 0.6.91-4 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of cwiid, which is due to be installed in the
Processed: severity of 1010441 is serious ..., tagging 1010441
Processing commands for cont...@bugs.debian.org: > # Python 3.10 incompatibility > severity 1010441 serious Bug #1010441 [torbrowser-launcher] torbrowser-launcher fails to download browser bundle when launched for the first time Severity set to 'serious' from 'important' > forwarded 1010441 https://github.com/micahflee/torbrowser-launcher/pull/599 Bug #1010441 [torbrowser-launcher] torbrowser-launcher fails to download browser bundle when launched for the first time Set Bug forwarded-to-address to 'https://github.com/micahflee/torbrowser-launcher/pull/599'. > # https://github.com/micahflee/torbrowser-launcher/pull/599 and others > tags 1010441 + patch Bug #1010441 [torbrowser-launcher] torbrowser-launcher fails to download browser bundle when launched for the first time Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005719: bug #1005719: mumble: FTBFS with OpenSSL 3.0
Mumble 1.3 is not buildable with OpenSSL 3.0 and there is no patch available to allow doing so. There was an upstream attempt to backport patches for Mumble 1.4 for Mumble 1.3 but there were enough issues that the effort had to be abandoned. https://github.com/mumble-voip/mumble/pull/5354 I'm currently trying to package Mumble 1.4 which could resolve the problem, but running into issues with the build refactoring including a switch to using CMake. I'm working with upstream to try to resolve the build failures. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#976439: wminput: Aborts with "undefined symbol: PyVarObject_CallFunction"
Hallo Bernd, many thanks for your MR! this is a great job. Best regards, Georges. Bernd Zeimetz a écrit : > > > Hi, > > with this MR applied, it does not crash at least. > https://salsa.debian.org/georgesk/cwiid/-/merge_requests/1 > > Not tested yet. > > Bernd > > -- > Bernd ZeimetzDebian GNU/Linux Developer > http://bzed.dehttp://www.debian.org > GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- 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#1004511: luajit SEGFAULTS on ppc64el
Hi Paul, sorry for the late reply. As I said on debian-devel, I've not enough expertise nor hope on that topic. Switching to lua is the way I went a few times, instead on relying on luajit. F. On Mon, 02 May 2022 07:55:50 +0200 Paul Gevers wrote: > Hi, > > On 24-04-2022 12:00, Paul Gevers wrote: > > On Sat, 29 Jan 2022 19:32:53 +0100 Paul Gevers wrote: > >> With a recent upload of luajit the autopkgtest of knot-resolver fails > >> in testing when that autopkgtest is run with the binary packages of > >> luajit from unstable. It passes when run with only packages from > >> testing. In tabular form: > > > > knot-resolver has been removed from testing due to this bug report, but > > can't migrate back because a newer version fails to build on ppc64el. > > Also other reverse dependencies of luajit show SEGFAULT in their > > autopkgtest on ppc64el, so this seems a problem in luajit. Unfortunately > > (Release Team member opinion) luajit is a key package so can't be > > trivially removed. Can you (maintainer and ppc64el porters) please have > > a look? > > If this issue is difficult to fix, how about removing luajit from > ppc64el? I noticed that the only reverse (build) dependent key package > of luajit (src:efl) already switched to plain lua on ppc64el (probably > because of this issue). > > Paul signature.asc Description: PGP signature
Processed: bug 1011279 is forwarded to https://github.com/felixge/node-dateformat/pull/183#issuecomment-1131754364
Processing commands for cont...@bugs.debian.org: > forwarded 1011279 > https://github.com/felixge/node-dateformat/pull/183#issuecomment-1131754364 Bug #1011279 [node-dateformat] node-dateformat CJS file does not provide the same API than ES file Set Bug forwarded-to-address to 'https://github.com/felixge/node-dateformat/pull/183#issuecomment-1131754364'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1011279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011279: [Pkg-javascript-devel] Bug#1011279: node-dateformat CJS file does not provide the same API than ES file
On 19/05/2022 15:50, Yadd wrote:
Package: node-dateformat
Version: 5.0.3-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Control: affects -1 grunt node-lightgallery
Following upstream doc, `import d from 'dateformat'` is a function. The
file built with `babeljs --plugins @babel/transform-modules-commonjs`
produces an Object, usable function is d.default. This breaks grunt (try
to build node-lightgallery for example).
This can be fixed using `mjs2cjs -a` and a custom `debian/index.cjs`
Grunt code:
// lib/grunt/template.js
template.date = require('dateformat');
// ...
return template.date(now, format);
// => error: template.date is not a function
Bug#1006519: Already fixed in 2.6.0~git20220510+dco-1 in experimental
On Sun, 15 May 2022 16:02:48 +0300 Adrian Bunk wrote: Version: 2.6.0~git20220510+dco-1 openvpn (2.6.0~git20220510+dco-1) experimental; urgency=medium ... * Build against OpenSSL 3.0 -- Bernhard Schmidt Fri, 13 May 2022 00:01:35 +0200 Berni, would you mind uploading this version to unstable? OpenPGP_signature Description: OpenPGP digital signature
Bug#1011279: node-dateformat CJS file does not provide the same API than ES file
Package: node-dateformat Version: 5.0.3-1 Severity: serious Tags: ftbfs Justification: FTBFS Control: affects -1 grunt node-lightgallery Following upstream doc, `import d from 'dateformat'` is a function. The file built with `babeljs --plugins @babel/transform-modules-commonjs` produces an Object, usable function is d.default. This breaks grunt (try to build node-lightgallery for example). This can be fixed using `mjs2cjs -a` and a custom `debian/index.cjs`
Processed: node-dateformat CJS file does not provide the same API than ES file
Processing control commands: > affects -1 grunt node-lightgallery Bug #1011279 [node-dateformat] node-dateformat CJS file does not provide the same API than ES file Added indication that 1011279 affects grunt and node-lightgallery -- 1011279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008412: marked as done (golang-github-pin-tftp: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/pin/tftp github.com/pin/tftp/netascii returned exit code 1)
Your message dated Thu, 19 May 2022 13:18:57 +
with message-id
and subject line Bug#1008412: fixed in golang-github-pin-tftp 2.2.0-3
has caused the Debian Bug report #1008412,
regarding golang-github-pin-tftp: FTBFS: dh_auto_test: error: cd _build && go
test -vet=off -v -p 8 github.com/pin/tftp github.com/pin/tftp/netascii returned
exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1008412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pin-tftp
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
> cd _build && go install -trimpath -v -p 8 github.com/pin/tftp
> github.com/pin/tftp/netascii
> internal/unsafeheader
> internal/goos
> internal/goarch
> internal/goexperiment
> internal/race
> internal/cpu
> runtime/internal/atomic
> runtime/internal/syscall
> sync/atomic
> unicode
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> unicode/utf8
> math/bits
> internal/itoa
> golang.org/x/net/internal/iana
> golang.org/x/sys/internal/unsafeheader
> internal/nettrace
> internal/bytealg
> math
> runtime
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> internal/testlog
> runtime/cgo
> errors
> sort
> io
> strconv
> internal/oserror
> path
> vendor/golang.org/x/net/dns/dnsmessage
> syscall
> bytes
> github.com/pin/tftp/netascii
> strings
> reflect
> internal/syscall/unix
> internal/syscall/execenv
> time
> context
> internal/poll
> io/fs
> internal/fmtsort
> encoding/binary
> os
> golang.org/x/sys/unix
> internal/godebug
> fmt
> internal/intern
> net/netip
> net
> golang.org/x/net/bpf
> golang.org/x/net/internal/socket
> golang.org/x/net/ipv6
> golang.org/x/net/ipv4
> github.com/pin/tftp
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
> cd _build && go test -vet=off -v -p 8 github.com/pin/tftp
> github.com/pin/tftp/netascii
> === RUN TestZeroLengthSinglePort
> --- PASS: TestZeroLengthSinglePort (0.00s)
> === RUN TestSendReceiveSinglePort
> --- PASS: TestSendReceiveSinglePort (0.66s)
> === RUN TestSendReceiveSinglePortWithBlockSize
> --- PASS: TestSendReceiveSinglePortWithBlockSize (0.49s)
> === RUN TestServerSendTimeoutSinglePort
> panic: test timed out after 10m0s
>
> goroutine 3166 [running]:
> testing.(*M).startAlarm.func1()
> /usr/lib/go-1.18/src/testing/testing.go:2029 +0x8e
> created by time.goFunc
> /usr/lib/go-1.18/src/time/sleep.go:176 +0x32
>
> goroutine 1 [chan receive, 9 minutes]:
> testing.(*T).Run(0xc000117520, {0x61e3a2?, 0x4d1845?}, 0x62ae48)
> /usr/lib/go-1.18/src/testing/testing.go:1487 +0x37a
> testing.runTests.func1(0xc000109770?)
> /usr/lib/go-1.18/src/testing/testing.go:1839 +0x6e
> testing.tRunner(0xc000117520, 0xc000157cd8)
> /usr/lib/go-1.18/src/testing/testing.go:1439 +0x102
> testing.runTests(0xc00011d360?, {0x791c60, 0x1d, 0x1d}, {0x7fabe3c6d108?,
> 0x40?, 0x797800?})
> /usr/lib/go-1.18/src/testing/testing.go:1837 +0x457
> testing.(*M).Run(0xc00011d360)
> /usr/lib/go-1.18/src/testing/testing.go:1719 +0x5d9
> main.main()
> _testmain.go:103 +0x1aa
>
> goroutine 35 [chan receive, 9 minutes]:
> github.com/pin/tftp.(*Server).internalGC(0xc0001ae000)
> /<>/_build/src/github.com/pin/tftp/single_port.go:121 +0x70
> created by github.com/pin/tftp.(*Server).EnableSinglePort
> /<>/_build/src/github.com/pin/tftp/server.go:129 +0x16f
>
> goroutine 3246 [chan send, 9 minutes]:
> github.com/pin/tftp.(*Server).Shutdown(0xc0001ae1c0)
> /<>/_build/src/github.com/pin/tftp/server.go:310 +0x65
> github.com/pin/tftp.serverTimeoutSendTest(0xc0001ae1c0, 0xc000c7af30,
> 0xc03ba0)
> /<>/_build/src/github.com/pin/tftp/tftp_test.go:575 +0x3b7
> github.com/pin/tftp.TestServerSendTimeoutSinglePort(0x11?)
> /<>/_build/src/github.com/pin/tftp/single_port_test.go:32
> +0x2f
> testing.tRunner(0xc03ba0, 0x62ae48)
> /usr/lib/go-1.18/src/testing/testing.go:1439
Bug#1008439: marked as done (golang-github-cloudflare-circl: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -timeout 30m github.com/cloudflare/circl github.com/cloudfl
Your message dated Thu, 19 May 2022 11:20:36 + with message-id and subject line Bug#1008439: fixed in golang-github-cloudflare-circl 1.0.0+20200724-2 has caused the Debian Bug report #1008439, regarding golang-github-cloudflare-circl: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -timeout 30m github.com/cloudflare/circl github.com/cloudflare/circl/dh github.com/cloudflare/circl/dh/csidh github.com/cloudflare/circl/dh/curve4q [...] github.com/cloudflare/circl/simd/keccakf1600 returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-cloudflare-circl Version: 1.0.0+20200724-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- -timeout 30m > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -timeout 30m > github.com/cloudflare/circl github.com/cloudflare/circl/dh > github.com/cloudflare/circl/dh/csidh github.com/cloudflare/circl/dh/curve4q > github.com/cloudflare/circl/dh/sidh > github.com/cloudflare/circl/dh/sidh/internal/common > github.com/cloudflare/circl/dh/sidh/internal/p434 > github.com/cloudflare/circl/dh/sidh/internal/p503 > github.com/cloudflare/circl/dh/sidh/internal/p751 > github.com/cloudflare/circl/dh/x25519 github.com/cloudflare/circl/dh/x448 > github.com/cloudflare/circl/ecc github.com/cloudflare/circl/ecc/fourq > github.com/cloudflare/circl/ecc/goldilocks > github.com/cloudflare/circl/ecc/p384 > github.com/cloudflare/circl/internal/conv > github.com/cloudflare/circl/internal/shake > github.com/cloudflare/circl/internal/test github.com/cloudflare/circl/math > github.com/cloudflare/circl/math/fp25519 > github.com/cloudflare/circl/math/fp448 > github.com/cloudflare/circl/math/mlsbset github.com/cloudflare/circl/sign > github.com/cloudflare/circl/sign/dilithium > github.com/cloudflare/circl/sign/dilithium/internal/common > github.com/cloudflare/circl/sign/dilithium/internal/common/params > github.com/cloudflare/circl/sign/dilithium/mode1 > github.com/cloudflare/circl/sign/dilithium/mode1/internal > github.com/cloudflare/circl/sign/dilithium/mode1aes > github.com/cloudflare/circl/sign/dilithium/mode1aes/internal > github.com/cloudflare/circl/sign/dilithium/mode2 > github.com/cloudflare/circl/sign/dilithium/mode2/internal > github.com/cloudflare/circl/sign/dilithium/mode2aes > github.com/cloudflare/circl/sign/dilithium/mode2aes/internal > github.com/cloudflare/circl/sign/dilithium/mode3 > github.com/cloudflare/circl/sign/dilithium/mode3/internal > github.com/cloudflare/circl/sign/dilithium/mode3aes > github.com/cloudflare/circl/sign/dilithium/mode3aes/internal > github.com/cloudflare/circl/sign/dilithium/mode4 > github.com/cloudflare/circl/sign/dilithium/mode4/internal > github.com/cloudflare/circl/sign/dilithium/mode4aes > github.com/cloudflare/circl/sign/dilithium/mode4aes/internal > github.com/cloudflare/circl/sign/ed25519 > github.com/cloudflare/circl/sign/ed448 > github.com/cloudflare/circl/sign/eddilithium3 > github.com/cloudflare/circl/sign/eddilithium4 > github.com/cloudflare/circl/simd github.com/cloudflare/circl/simd/keccakf1600 > ? github.com/cloudflare/circl [no test files] > ? github.com/cloudflare/circl/dh [no test files] > === RUN TestCompare64 > --- PASS: TestCompare64 (0.00s) > === RUN TestEphemeralKeyExchange > --- PASS: TestEphemeralKeyExchange (0.41s) > === RUN TestPrivateKeyExportImport > --- PASS: TestPrivateKeyExportImport (0.00s) > === RUN TestValidateNegative > --- PASS: TestValidateNegative (0.00s) > === RUN TestPublicKeyExportImport > --- PASS: TestPublicKeyExportImport (0.96s) > === RUN TestKAT > --- PASS: TestKAT (0.52s) > === RUN TestXAdd > --- PASS: TestXAdd (0.00s) > === RUN TestXDbl > --- PASS: TestXDbl (0.00s) > === RUN TestXDblAddNominal > --- PASS: TestXDblAddNominal (0.00s) > === RUN TestXDblAddVSxDblxAdd > --- PASS: TestXDblAddVSxDblxAdd (0.00s) > === RUN TestXMul > --- PASS: TestXMul (0.00s) > === RUN TestMappointHardcoded3 > --- PASS: TestMappointHardcoded3 (0.00s) > === RUN TestMappointHardcoded5 > --- PASS: TestMappointHardcoded5 (0.00s) > === RUN TestFp512Mul3_Nominal > --- PASS: TestFp512Mul3_Nominal (0.00s) > ===
Bug#1011142: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185)
Your message dated Thu, 19 May 2022 10:36:14 + with message-id and subject line Bug#1011142: fixed in nvidia-graphics-drivers-legacy-390xx 390.151-1 has caused the Debian Bug report #1011142, regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185 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.) -- 1011142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-28181, CVE-2022-28185 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-28181, CVE-2022-28185, CVE-2022-28192 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-28181, CVE-2022-28185, CVE-2022-28192 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 Control: tag -6 + wontfix Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5353 CVE-2022-28181 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where an unprivileged regular user on the network can cause an out-of-bounds write through a specially crafted shader, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The scope of the impact may extend to other components. CVE-2022-28183 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where an unprivileged regular user can cause an out-of-bounds read, which may lead to denial of service and information disclosure. CVE-2022-28184 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape, where an unprivileged regular user can access administrator- privileged registers, which may lead to denial of service, information disclosure, and data tampering. CVE-2022-28185 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the ECC layer, where an unprivileged regular user can cause an out-of-bounds write, which may lead to denial of service and data tampering. CVE-2022-28191 NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (nvidia.ko), where uncontrolled resource consumption can be triggered by an unprivileged regular user, which may lead to denial of service. CVE-2022-28192 NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (nvidia.ko), where it may lead to a use-after-free, which in turn may cause denial of service. This attack is complex to carry out because the attacker needs to have control over freeing some host side resources out of sequence, which requires elevated privileges. Driver Branch CVE IDs Addressed R510 and R470 CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 R450CVE-2022-28181, CVE-2022-28185, CVE-2022-28192 R390CVE-2022-28181, CVE-2022-28185 Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-legacy-390xx Source-Version: 390.151-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-legacy-390xx, which is due to be installed in the
Bug#1010230: marked as done (nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf)
Your message dated Thu, 19 May 2022 10:36:14 +
with message-id
and subject line Bug#1010230: fixed in nvidia-graphics-drivers-legacy-390xx
390.151-1
has caused the Debian Bug report #1010230,
regarding nvidia-graphics-drivers-legacy-390xx: spurious module build failure
in autopkgtest on armhf
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.)
--
1010230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.147-4
Severity: serious
X-Debbugs-CC: d...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dkms
Dear maintainer(s),
With a recent upload of dkms the autopkgtest of
nvidia-graphics-drivers-legacy-390xx fails in testing when that
autopkgtest is run with the binary packages of dkms from unstable on
armhf. It passes when run with only packages from testing. In tabular form:
passfail
dkms from testing3.0.3-1
nvidia-graphics-drivers-legacy-390xx from testing390.147-4
all others from testingfrom testing
I copied some of the output at the bottom of this report. As I
understand it, the dkms changes extend the testing drastically and show
a real issue.
Currently this regression is blocking the migration of dkms to testing
[1]. Of course, dkms shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in dkms was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from dkms should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
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=dkms
https://ci.debian.net/data/autopkgtest/testing/armhf/n/nvidia-graphics-drivers-legacy-390xx/21184047/log.gz
At top level:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:999:5:
error: unknown type name ‘NV_WORKQUEUE_DATA_T’; did you mean
‘NV_WORKQUEUE_FLUSH’?
999 | NV_WORKQUEUE_DATA_T *data
| ^~~
| NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c: In
function ‘nv_flush_caches’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c:225:5:
error: implicit declaration of function ‘NV_ON_EACH_CPU’
[-Werror=implicit-function-declaration]
225 | NV_ON_EACH_CPU(nv_flush_cache, NULL);
| ^~
cc1: some warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.o] Error 1
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_queue_work_item’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:5:
error: implicit declaration of function ‘NV_WORKQUEUE_INIT’; did you
mean ‘NV_WORKQUEUE_FLUSH’? [-Werror=implicit-function-declaration]
1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
| ^
| NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:36:
error: ‘os_execute_work_item’ undeclared (first use in this function);
did you mean ‘rm_execute_work_item’?
1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
|^~~~
|rm_execute_work_item
In file included from
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_is_efi_enabled’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:224:26:
warning: returning ‘bool (*)(int)’ {aka ‘_Bool (*)(int)’} from a
function with return type ‘NvS32’ {aka ‘int’} makes integer from pointer
without a cast [-Wint-conversion]
224 | #define NV_EFI_ENABLED() efi_enabled
| ^~~
Bug#1010885: marked as done (dkms breaks nvidia-graphics-drivers-tesla-510 autopkgtest on arm64 and ppc64el: unmet dependencies)
Your message dated Thu, 19 May 2022 12:59:03 +0300 with message-id <20220519095903.GA564@localhost> and subject line Re: Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies has caused the Debian Bug report #1010885, regarding dkms breaks nvidia-graphics-drivers-tesla-510 autopkgtest on arm64 and ppc64el: unmet 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.) -- 1010885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dkms, nvidia-graphics-drivers-tesla-510 Control: found -1 dkms/3.0.3-1 Control: found -1 nvidia-graphics-drivers-tesla-510/510.47.03-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of dkms the autopkgtest of nvidia-graphics-drivers-tesla-510 fails in testing when that autopkgtest is run with the binary packages of dkms from unstable. It passes when run with only packages from testing. In tabular form: passfail dkms from testing3.0.3-1 nvidia-graphics-drivers-tesla-510 from testing510.47.03-2 all othersfrom testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of dkms to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? 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=dkms https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers-tesla-510/21592376/log.gz I: Removing binary package nvidia-tesla-510-kernel-dkms, to get clean state I: Installing binary package nvidia-tesla-510-kernel-dkms Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe nvidia-tesla-510-alternative nvidia-tesla-510-kernel-support update-glx Suggested packages: libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any Recommended packages: nvidia-tesla-510-driver | libnvidia-tesla-510-cuda1 The following NEW packages will be installed: glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe nvidia-tesla-510-alternative nvidia-tesla-510-kernel-dkms nvidia-tesla-510-kernel-support update-glx 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 50.4 MB of archives. After this operation, 95.1 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx arm64 1.2.1 [10.6 kB] Get:2 http://deb.debian.org/debian testing/contrib arm64 glx-alternative-mesa arm64 1.2.1 [9912 B] Get:3 http://deb.debian.org/debian testing/contrib arm64 nvidia-installer-cleanup arm64 20220217+1 [19.4 kB] Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions arm64 1.2.1 [12.6 kB] Get:5 http://deb.debian.org/debian testing/contrib arm64 glx-alternative-nvidia arm64 1.2.1 [10.9 kB] Get:6 http://deb.debian.org/debian testing/non-free arm64 nvidia-tesla-510-alternative arm64 510.47.03-2 [246 kB] Get:7 http://deb.debian.org/debian testing/contrib arm64 nvidia-kernel-common arm64 20220217+1 [10.9 kB] Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe arm64 510.68.02-1 [20.5 kB] Get:9 http://deb.debian.org/debian testing/non-free arm64 nvidia-tesla-510-kernel-support arm64 510.47.03-2 [20.7 MB] Get:10 http://deb.debian.org/debian testing/non-free arm64 nvidia-tesla-510-kernel-dkms arm64 510.47.03-2 [29.4 MB] debconf: delaying package configuration, since apt-utils is not installed Fetched 50.4 MB in 5s (10.2 MB/s) Selecting previously unselected package update-glx. (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 ...
Bug#1010884: marked as done (dkms breaks nvidia-graphics-drivers-tesla-470 autopkgtest on arm64 and ppc64el: unmet dependencies)
Your message dated Thu, 19 May 2022 12:59:03 +0300 with message-id <20220519095903.GA564@localhost> and subject line Re: Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies has caused the Debian Bug report #1010884, regarding dkms breaks nvidia-graphics-drivers-tesla-470 autopkgtest on arm64 and ppc64el: unmet 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.) -- 1010884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dkms, nvidia-graphics-drivers-tesla-470 Control: found -1 dkms/3.0.3-1 Control: found -1 nvidia-graphics-drivers-tesla-470/470.103.01-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of dkms the autopkgtest of nvidia-graphics-drivers-tesla-470 fails in testing when that autopkgtest is run with the binary packages of dkms from unstable. It passes when run with only packages from testing. In tabular form: passfail dkms from testing3.0.3-1 nvidia-graphics-drivers-tesla-470 from testing470.103.01-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of dkms to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? 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=dkms https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers-tesla-470/21589790/log.gz I: Removing binary package nvidia-tesla-470-kernel-dkms, to get clean state I: Installing binary package nvidia-tesla-470-kernel-dkms Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe nvidia-tesla-470-alternative nvidia-tesla-470-kernel-support update-glx Suggested packages: libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any Recommended packages: nvidia-tesla-470-driver | libnvidia-tesla-470-cuda1 The following NEW packages will be installed: glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe nvidia-tesla-470-alternative nvidia-tesla-470-kernel-dkms nvidia-tesla-470-kernel-support update-glx 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 25.9 MB of archives. After this operation, 50.2 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx arm64 1.2.1 [10.6 kB] Get:2 http://deb.debian.org/debian testing/contrib arm64 glx-alternative-mesa arm64 1.2.1 [9912 B] Get:3 http://deb.debian.org/debian testing/contrib arm64 nvidia-installer-cleanup arm64 20220217+1 [19.4 kB] Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions arm64 1.2.1 [12.6 kB] Get:5 http://deb.debian.org/debian testing/contrib arm64 glx-alternative-nvidia arm64 1.2.1 [10.9 kB] Get:6 http://deb.debian.org/debian testing/non-free arm64 nvidia-tesla-470-alternative arm64 470.103.01-2 [242 kB] Get:7 http://deb.debian.org/debian testing/contrib arm64 nvidia-kernel-common arm64 20220217+1 [10.9 kB] Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe arm64 510.68.02-1 [20.5 kB] Get:9 http://deb.debian.org/debian testing/non-free arm64 nvidia-tesla-470-kernel-support arm64 470.103.01-2 [241 kB] Get:10 http://deb.debian.org/debian testing/non-free arm64 nvidia-tesla-470-kernel-dkms arm64 470.103.01-2 [25.3 MB] debconf: delaying package configuration, since apt-utils is not installed Fetched 25.9 MB in 5s (5151 kB/s) Selecting previously unselected package update-glx. (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
Bug#1010883: marked as done (dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies)
Your message dated Thu, 19 May 2022 12:59:03 +0300 with message-id <20220519095903.GA564@localhost> and subject line Re: Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies has caused the Debian Bug report #1010883, regarding dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet 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.) -- 1010883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dkms, nvidia-graphics-drivers Control: found -1 dkms/3.0.3-1 Control: found -1 nvidia-graphics-drivers/470.103.01-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of dkms the autopkgtest of nvidia-graphics-drivers fails in testing when that autopkgtest is run with the binary packages of dkms from unstable. It passes when run with only packages from testing. In tabular form: passfail dkmsfrom testing3.0.3-1 nvidia-graphics-drivers from testing470.103.01-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of dkms to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? 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=dkms https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers/21589789/log.gz I: Removing binary package nvidia-kernel-dkms, to get clean state I: Installing binary package nvidia-kernel-dkms Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-support nvidia-modprobe update-glx Suggested packages: libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any Recommended packages: nvidia-driver | libcuda1 The following NEW packages will be installed: glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support nvidia-modprobe update-glx 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 25.9 MB of archives. After this operation, 50.2 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx arm64 1.2.1 [10.6 kB] Get:2 http://deb.debian.org/debian testing/contrib arm64 glx-alternative-mesa arm64 1.2.1 [9912 B] Get:3 http://deb.debian.org/debian testing/contrib arm64 nvidia-installer-cleanup arm64 20220217+1 [19.4 kB] Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions arm64 1.2.1 [12.6 kB] Get:5 http://deb.debian.org/debian testing/contrib arm64 glx-alternative-nvidia arm64 1.2.1 [10.9 kB] Get:6 http://deb.debian.org/debian testing/non-free arm64 nvidia-alternative arm64 470.103.01-3 [240 kB] Get:7 http://deb.debian.org/debian testing/contrib arm64 nvidia-kernel-common arm64 20220217+1 [10.9 kB] Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe arm64 510.68.02-1 [20.5 kB] Get:9 http://deb.debian.org/debian testing/non-free arm64 nvidia-kernel-support arm64 470.103.01-3 [239 kB] Get:10 http://deb.debian.org/debian testing/non-free arm64 nvidia-kernel-dkms arm64 470.103.01-3 [25.3 MB] debconf: delaying package configuration, since apt-utils is not installed Fetched 25.9 MB in 2s (16.5 MB/s) Selecting previously unselected package update-glx. (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 ... 29721 files and directories currently
Processed: Bug#1010386 marked as pending in golang-v2ray-core
Processing control commands:
> tag -1 pending
Bug #1010386 {Done: Roger Shimizu } [src:golang-v2ray-core]
golang-v2ray-core: FTBFS on armel and armhf
Added tag(s) pending.
--
1010386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010386: marked as pending in golang-v2ray-core
Control: tag -1 pending Hello, Bug #1010386 in golang-v2ray-core 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/go-team/packages/golang-v2ray-core/-/commit/19ecbaa06ef95033c736ee7506dd4d8c8205ebce Prepare to release 4.34.0-6 * debian/patches: - Amend patch 02 to skip 1 tests to fix ftbfs on armel and armhf. Closes: #1010386 (this message was generated automatically) -- Greetings https://bugs.debian.org/1010386
Bug#1010386: marked as done (golang-v2ray-core: FTBFS on armel and armhf)
Your message dated Thu, 19 May 2022 09:18:42 + with message-id and subject line Bug#1010386: fixed in golang-v2ray-core 4.34.0-6 has caused the Debian Bug report #1010386, regarding golang-v2ray-core: FTBFS on armel and armhf 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.) -- 1010386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-v2ray-core Version: 4.34.0-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org golang-v2ray-core FTBFS on armel and armhf: ok v2ray.com/core/transport/internet/websocket 5.116s === RUN TestPipeReadWrite --- PASS: TestPipeReadWrite (0.00s) === RUN TestPipeInterrupt --- PASS: TestPipeInterrupt (0.00s) === RUN TestPipeClose --- PASS: TestPipeClose (0.00s) === RUN TestPipeLimitZero --- PASS: TestPipeLimitZero (2.00s) === RUN TestPipeWriteMultiThread --- PASS: TestPipeWriteMultiThread (0.10s) === RUN TestInterfaces --- PASS: TestInterfaces (0.00s) PASS ok v2ray.com/core/transport/pipe 2.130s FAIL dh_auto_test: error: cd obj-arm-linux-gnueabi && go test -vet=off -v -p 4 -timeout 30m v2ray.com/core v2ray.com/core/app v2ray.com/core/app/commander v2ray.com/core/app/dispatcher v2ray.com/core/app/dns v2ray.com/core/app/log v2ray.com/core/app/log/command v2ray.com/core/app/policy v2ray.com/core/app/proxyman v2ray.com/core/app/proxyman/command v2ray.com/core/app/proxyman/inbound v2ray.com/core/app/proxyman/outbound v2ray.com/core/app/reverse v2ray.com/core/app/router v2ray.com/core/app/router/command v2ray.com/core/app/stats v2ray.com/core/app/stats/command v2ray.com/core/common v2ray.com/core/common/antireplay v2ray.com/core/common/bitmask v2ray.com/core/common/buf v2ray.com/core/common/bytespool v2ray.com/core/common/cmdarg v2ray.com/core/common/crypto v2ray.com/core/common/crypto/internal v2ray.com/core/common/dice v2ray.com/core/common/errors v2ray.com/core/common/errors/errorgen v2ray.com/core/common/log v2ray.com/core/common/mux v2ray.com/core/common/net v2ray.com/core/common/peer v2ray.com/core/common/platform v2ray.com/core/common/platform/ctlcmd v2ray.com/core/common/platform/filesystem v2ray.com/core/common/protocol v2ray.com/core/common/protocol/bittorrent v2ray.com/core/common/protocol/dns v2ray.com/core/common/protocol/http v2ray.com/core/common/protocol/tls v2ray.com/core/common/protocol/tls/cert v2ray.com/core/common/protocol/udp v2ray.com/core/common/retry v2ray.com/core/common/serial v2ray.com/core/common/session v2ray.com/core/common/signal v2ray.com/core/common/signal/done v2ray.com/core/common/signal/pubsub v2ray.com/core/common/signal/semaphore v2ray.com/core/common/strmatcher v2ray.com/core/common/task v2ray.com/core/common/uuid v2ray.com/core/features v2ray.com/core/features/dns v2ray.com/core/features/dns/localdns v2ray.com/core/features/inbound v2ray.com/core/features/outbound v2ray.com/core/features/policy v2ray.com/core/features/routing v2ray.com/core/features/routing/dns v2ray.com/core/features/routing/session v2ray.com/core/features/stats v2ray.com/core/infra/conf v2ray.com/core/infra/conf/command v2ray.com/core/infra/conf/json v2ray.com/core/infra/conf/serial v2ray.com/core/infra/control v2ray.com/core/infra/control/main v2ray.com/core/infra/vprotogen v2ray.com/core/main v2ray.com/core/main/confloader v2ray.com/core/main/confloader/external v2ray.com/core/main/distro/all v2ray.com/core/main/distro/debug v2ray.com/core/main/json v2ray.com/core/main/jsonem v2ray.com/core/proxy v2ray.com/core/proxy/blackhole v2ray.com/core/proxy/dns v2ray.com/core/proxy/dokodemo v2ray.com/core/proxy/freedom v2ray.com/core/proxy/http v2ray.com/core/proxy/mtproto v2ray.com/core/proxy/shadowsocks v2ray.com/core/proxy/socks v2ray.com/core/proxy/trojan v2ray.com/core/proxy/vless v2ray.com/core/proxy/vless/encoding v2ray.com/core/proxy/vless/inbound v2ray.com/core/proxy/vless/outbound v2ray.com/core/proxy/vmess v2ray.com/core/proxy/vmess/aead v2ray.com/core/proxy/vmess/encoding v2ray.com/core/proxy/vmess/inbound v2ray.com/core/proxy/vmess/outbound v2ray.com/core/testing/mocks v2ray.com/core/testing/scenarios v2ray.com/core/testing/servers/http v2ray.com/core/testing/servers/tcp v2ray.com/core/testing/servers/udp v2ray.com/core/transport v2ray.com/core/transport/internet v2ray.com/core/transport/internet/domainsocket v2ray.com/core/transport/internet/headers/http v2ray.com/core/transport/internet/headers/noop
Bug#1008460: marked as done (shadowsocks-v2ray-plugin: FTBFS: cannot find package "github.com/marten-seemann/qtls-go1-18")
Your message dated Thu, 19 May 2022 18:11:09 +0900 with message-id and subject line Re: shadowsocks-v2ray-plugin: FTBFS: cannot find package "github.com/marten-seemann/qtls-go1-18" has caused the Debian Bug report #1008460, regarding shadowsocks-v2ray-plugin: FTBFS: cannot find package "github.com/marten-seemann/qtls-go1-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.) -- 1008460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shadowsocks-v2ray-plugin Version: 1.3.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/shadowsocks/v2ray-plugin > src/github.com/lucas-clemente/quic-go/internal/qtls/go118.go:13:2: cannot > find package "github.com/marten-seemann/qtls-go1-18" in any of: > /usr/lib/go-1.18/src/github.com/marten-seemann/qtls-go1-18 (from > $GOROOT) > > /<>/obj-x86_64-linux-gnu/src/github.com/marten-seemann/qtls-go1-18 > (from $GOPATH) > dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/shadowsocks/v2ray-plugin returned exit code 1 > make: *** [debian/rules:14: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/03/26/shadowsocks-v2ray-plugin_1.3.1-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- I tried to build in sid, and found it built successfully. I guess the situation is same as #1008445 that ftbfs previously occurred, but now it can be built without problem. So I'm closing this ticket. If there's new issue, please reopen, or create new ticket. Thank you! -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1--- End Message ---
Bug#1011166: [Debian-on-mobile-maintainers] Bug#1011166: pidgin breaks chatty autopkgtest: error while loading shared libraries: libjabber.so.0
Hi,
On Wed, 2022-05-18 at 03:04 -0500, Richard Laager wrote:
> Control: notfound 1011166 pidgin/2.14.9-2
> Control: tags 1011166 patch
>
> On 5/17/22 15:34, Paul Gevers wrote:
> > I note that
> > the library moved location from /usr/lib/purple-
> > 2/libjabber.so.0.0.0 to
> > /usr/lib/x86_64-linux-gnu/purple-2/libjabber.so.0.0.0.
>
> I converted from an ancient compat version to modern debhelper. This
> brought in multiarch support. Rather than fight it, I just went with
> that, since the problem looked tractable.
>
> > Naively I would
> > have expected it to be picked up, but maybe the /purple-2 in the
> > middle
> > of the path is preventing that.
>
> -- BEGIN RED HERRING --
>
> I would expect it to be picked up.
>
> libpurple/plugin.c sets up the search path for that purple-2
> directory
> (which is where all libpurple plugins are installed):
> purple_plugins_add_search_path(LIBDIR);
>
> In libpurple/Makefile.am, AM_CPPFLAGS has:
> -DLIBDIR=\"$(libdir)/purple-$(PURPLE_MAJOR_VERSION)/\"
>
> This should cause us to find libxmpp.so, the protocol plugin. It then
> needs to bring in libjabber.so, an internal library. It should be
> finding this with RUNPATH, I believe:
>
> $ readelf -a /usr/lib/x86_64-linux-gnu/purple-2/libxmpp.so | grep -i
> path
> 0x001d (RUNPATH) Library runpath:
> [/usr/lib/x86_64-linux-gnu/purple-2]
>
> If I run: LD_DEBUG=libs pidgin -n
>
> That is indeed what happens:
> 43864: find library=libjabber.so.0 [0]; searching
> 43864: search
> path=/usr/lib/x86_64-linux-gnu/purple-2/glibc-hwcaps/x86-64-
> v3:/usr/lib/x86_64-linux-gnu/purple-2/glibc-hwcaps/x86-64-
> v2:/usr/lib/x86_64-linux-gnu/purple-
> 2/tls/haswell/x86_64:/usr/lib/x86_64-linux-gnu/purple-
> 2/tls/haswell:/usr/lib/x86_64-linux-gnu/purple-
> 2/tls/x86_64:/usr/lib/x86_64-linux-gnu/purple-2/tls:/usr/lib/x86_64-
> linux-gnu/purple-2/haswell/x86_64:/usr/lib/x86_64-linux-gnu/purple-
> 2/haswell:/usr/lib/x86_64-linux-gnu/purple-2/x86_64:/usr/lib/x86_64-
> linux-gnu/purple-2
> (RUNPATH from file
> /usr/lib/x86_64-linux-gnu/purple-2/libxmpp.so)
>
> If I run: LD_DEBUG=libs chatty
>
> It fails:
>
> 43926:find library=libjabber.so.0 [0]; searching
> 43926: search path=/usr/lib/purple-2 (RUNPATH from
> file chatty)
> 43926: trying file=/usr/lib/purple-2/libjabber.so.0
> 43926: search cache=/etc/ld.so.cache
> 43926: search
> path=/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3:/lib/x86_64-linux-
> gnu/glibc-hwcaps/x86-64-v2:/lib/x86_64-linux-
> gnu/tls/haswell/x86_64:/lib/x86_64-linux-gnu/tls/haswell:/lib/x86_64-
> linux-gnu/tls/x86_64:/lib/x86_64-linux-gnu/tls:/lib/x86_64-linux-
> gnu/haswell/x86_64:/lib/x86_64-linux-gnu/haswell:/lib/x86_64-linux-
> gnu/x86_64:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/glibc-
> hwcaps/x86-64-v3:/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-
> v2:/usr/lib/x86_64-linux-gnu/tls/haswell/x86_64:/usr/lib/x86_64-
> linux-gnu/tls/haswell:/usr/lib/x86_64-linux-
> gnu/tls/x86_64:/usr/lib/x86_64-linux-gnu/tls:/usr/lib/x86_64-linux-
> gnu/haswell/x86_64:/usr/lib/x86_64-linux-gnu/haswell:/usr/lib/x86_64-
> linux-gnu/x86_64:/usr/lib/x86_64-linux-gnu:/lib/glibc-hwcaps/x86-64-
> v3:/lib/glibc-hwcaps/x86-64-
> v2:/lib/tls/haswell/x86_64:/lib/tls/haswell:/lib/tls/x86_64:/lib/tls:
> /lib/haswell/x86_64:/lib/haswell:/lib/x86_64:/lib:/usr/lib/glibc-
> hwcaps/x86-64-v3:/usr/lib/glibc-hwcaps/x86-64-
> v2:/usr/lib/tls/haswell/x86_64:/usr/lib/tls/haswell:/usr/lib/tls/x86_
> 64:/usr/lib/tls:/usr/lib/haswell/x86_64:/usr/lib/haswell:/usr/lib/x86
> _64:/usr/lib
> (system search path)
>
> At first glance, it felt like the RUNPATH from chatty was winning
> over
> that from libxmpp.so.
>
> -- END RED HERRING --
>
> Upon further investigation, the real issue is that chatty is directly
> linking to libjabber.so, and they're setting a RUNPATH to do it.
>
> chatty's src/meson.build has:
> executable('chatty', chatty_sources, resources,
> include_directories: src_inc,
> dependencies: chatty_deps,
> link_with: libchatty.get_static_lib(),
> install: true,
> install_rpath: purple_plugdir,
> )
>
> Note the install_rpath.
>
> and src/purple/meson.build has (manual wrapping added for email):
>
> purple_plugdir = purple_dep.get_pkgconfig_variable('plugindir')
> jabber = meson.get_compiler('c').find_library(
> 'jabber', dirs: purple_plugdir)
>
> In terms of "Who is at fault?", I blame chatty for explicitly linking
> to
> an internal library. However, in fairness, I understand that they
> have
> their reasons and a better solution was never found with upstream (at
> least in part because no significant changes are going to go into
> purple
> 2 at this point):
> https://source.puri.sm/Librem5/chatty/-/issues/266
>
thanks for the thorough analysis!
> The good news here is that a rebuild of chatty is all that's
> necessary.
Indeed. I noticed this
Processed: src:kpcli: fails to migrate to testing for too long: uploader built arch:all binaries
Processing control commands: > close -1 3.6-1 Bug #1011266 [src:kpcli] src:kpcli: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions kpcli/3.6-1. Bug #1011266 [src:kpcli] src:kpcli: fails to migrate to testing for too long: uploader built arch:all binaries Marked Bug as done -- 1011266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011266: src:kpcli: fails to migrate to testing for too long: uploader built arch:all binaries
Source: kpcli Version: 3.1-3.1 Severity: serious Control: close -1 3.6-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:kpcli 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 bookworm, 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=kpcli OpenPGP_signature Description: OpenPGP digital signature
Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch
Hi, On 19-05-2022 07:57, Andreas Beckmann wrote: could you try again and see whether the attached patch fixes the issue? See attached transcript. If I understand correctly it worked. Paul paul@mulciber ~/debian-maint/ci.d.n-config $ rake login:ci-worker-armel-01 Linux ci-worker-armel-01 5.10.0-14-arm64 #1 SMP Debian 5.10.113-1 (2022-04-29) aarch64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed May 18 20:18:52 2022 from 45.91.56.150 root@ci-worker-armel-01:~# lxc-copy -n autopkgtest-unstable-armhf -N elbrus root@ci-worker-armel-01:~# lxc-start elbrus root@ci-worker-armel-01:~# lxc-attach elbrus root@elbrus:~# apt install --no-recommends wget E: Command line option --no-recommends is not understood in combination with the other options root@elbrus:~# apt install --no-install-recommends wget Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libpsl5 Recommended packages: publicsuffix The following NEW packages will be installed: libpsl5 wget 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,013 kB of archives. After this operation, 3,606 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://deb.debian.org/debian unstable/main armhf libpsl5 armhf 0.21.0-1.2 [56.1 kB] Get:2 http://deb.debian.org/debian unstable/main armhf wget armhf 1.21.3-1+b1 [957 kB] Fetched 1,013 kB in 1s (1,477 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libpsl5:armhf. (Reading database ... 13289 files and directories currently installed.) Preparing to unpack .../libpsl5_0.21.0-1.2_armhf.deb ... Unpacking libpsl5:armhf (0.21.0-1.2) ... Selecting previously unselected package wget. Preparing to unpack .../wget_1.21.3-1+b1_armhf.deb ... Unpacking wget (1.21.3-1+b1) ... Setting up libpsl5:armhf (0.21.0-1.2) ... Setting up wget (1.21.3-1+b1) ... Processing triggers for libc-bin (2.33-7) ... root@elbrus:~# export parallel_jobs=1 root@elbrus:~# apt-get install nvidia-legacy-390xx-kernel-dkms --no-install-recommends Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: cpp cpp-11 dctrl-tools distro-info-data dkms gcc gcc-11 gcc-11-base glx-alternative-mesa glx-alternative-nvidia glx-diversions kmod libasan6 libatomic1 libcc1-0 libgcc-11-dev libgomp1 libisl23 libmpc3 libmpdec3 libmpfr6 libpython3-stdlib libpython3.10-stdlib libubsan1 lsb-release media-types nvidia-installer-cleanup nvidia-kernel-common nvidia-legacy-390xx-alternative nvidia-legacy-390xx-kernel-support nvidia-modprobe python3 python3.10 update-glx Suggested packages: cpp-doc gcc-11-locales debtags menu gcc-multilib manpages-dev autoconf automake libtool flex bison gdb gcc-doc gcc-11-doc libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any python3-doc python3-tk python3-venv python3.10-venv python3.10-doc Recommended packages: fakeroot sudo linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers libc6-dev | libc-dev libc6-dev nvidia-legacy-390xx-driver | libnvidia-legacy-390xx-cuda1 The following NEW packages will be installed: cpp cpp-11 dctrl-tools distro-info-data dkms gcc gcc-11 gcc-11-base glx-alternative-mesa glx-alternative-nvidia glx-diversions kmod libasan6 libatomic1 libcc1-0 libgcc-11-dev libgomp1 libisl23 libmpc3 libmpdec3 libmpfr6 libpython3-stdlib libpython3.10-stdlib libubsan1 lsb-release media-types nvidia-installer-cleanup nvidia-kernel-common nvidia-legacy-390xx-alternative nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-kernel-support nvidia-modprobe python3 python3.10 update-glx 0 upgraded, 35 newly installed, 0 to remove and 0 not upgraded. Need to get 38.3 MB of archives. After this operation, 99.0 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://deb.debian.org/debian unstable/main armhf media-types all 8.0.0 [33.4 kB] Get:2 http://deb.debian.org/debian unstable/main armhf libmpdec3 armhf 2.5.1-2 [74.9 kB] Get:3 http://deb.debian.org/debian unstable/main armhf libpython3.10-stdlib armhf 3.10.4-4+b1 [1,622 kB] Get:4 http://deb.debian.org/debian unstable/main armhf python3.10 armhf 3.10.4-4+b1 [537 kB] Get:5 http://deb.debian.org/debian unstable/main armhf libpython3-stdlib armhf 3.10.4-1+b1 [21.9 kB] Get:6 http://deb.debian.org/debian unstable/main armhf python3 armhf 3.10.4-1+b1 [38.4 kB] Get:7 http://deb.debian.org/debian unstable/main armhf distro-info-data all 0.53 [7,656 B] Get:8 http://deb.debian.org/debian unstable/main armhf lsb-release all 11.1.0 [27.9
Processed: 1009415 is forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 1009415 https://github.com/project-gemmi/gemmi/issues/212 Bug #1009415 [src:gemmi] gemmi: FTBFS with tao-pegtl v3 Set Bug forwarded-to-address to 'https://github.com/project-gemmi/gemmi/issues/212'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch
On 19/05/2022 06.34, Andreas Beckmann wrote: Yes, it's an arch detection problem and an attempt is made to build for armv8l instead of arm. But we fixed that long ago for i386 on amd64 kernel, so it should be manageable for armhf, too. Hi, could you try again and see whether the attached patch fixes the issue? It's rather a HACK that just remaps arm64 to arm since the 390xx series does not support arm64 at all. Thanks Andreas Author: Andreas Beckmann Description: (HACK!) fix ARCH detection for armhf running on arm64 since the 390xx series does not support arm64 at all, just map aarch64 to arm, too, to fix building the kernel module in armhf chroots running on arm64 hosts --- a/Makefile +++ b/Makefile @@ -54,6 +54,7 @@ else ifndef ARCH ARCH := $(shell uname -m | sed -e 's/i.86/i386/' \ -e 's/armv[0-7]\w\+/arm/' \ + -e 's/armv8l/arm/' \ -e 's/aarch64/arm64/' \ -e 's/ppc64le/powerpc/' \ )
