Bug#987469: marked as done (r-bioc-gsva FTBFS: ERROR: dependency ‘GSEABase’ is not available for package ‘GSVA’)
Your message dated Sat, 08 May 2021 06:19:04 + with message-id and subject line Bug#987469: fixed in r-bioc-gsva 1.38.2+ds-2 has caused the Debian Bug report #987469, regarding r-bioc-gsva FTBFS: ERROR: dependency ‘GSEABase’ is not available for package ‘GSVA’ 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.) -- 987469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-gsva Version: 1.38.2+ds-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/r-bioc-gsva.html https://buildd.debian.org/status/package.php?p=r-bioc-gsva&suite=sid ... I: Using built-time from d/changelog: Thu, 18 Feb 2021 22:07:45 +0100 mkdir -p /<>/r-bioc-gsva-1.38.2\+ds/debian/r-bioc-gsva/usr/lib/R/site-library R CMD INSTALL -l /<>/r-bioc-gsva-1.38.2\+ds/debian/r-bioc-gsva/usr/lib/R/site-library --clean . "--built-timestamp='Thu, 18 Feb 2021 22:07:45 +0100'" ERROR: dependency ‘GSEABase’ is not available for package ‘GSVA’ * removing ‘/<>/debian/r-bioc-gsva/usr/lib/R/site-library/GSVA’ dh_auto_install: error: R CMD INSTALL -l /<>/r-bioc-gsva-1.38.2\+ds/debian/r-bioc-gsva/usr/lib/R/site-library --clean . "--built-timestamp='Thu, 18 Feb 2021 22:07:45 +0100'" returned exit code 1 make: *** [debian/rules:4: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: r-bioc-gsva Source-Version: 1.38.2+ds-2 Done: Steffen Moeller We believe that the bug you reported is fixed in the latest version of r-bioc-gsva, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steffen Moeller (supplier of updated r-bioc-gsva 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, 08 May 2021 11:27:52 +0530 Source: r-bioc-gsva Architecture: source Version: 1.38.2+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Steffen Moeller Closes: 987469 Changes: r-bioc-gsva (1.38.2+ds-2) unstable; urgency=medium . [ Steffen Moeller ] * Added missing build-dependency (Closes: #987469) . [ Nilesh Patra ] * d/test/control: Add depends on r-cran-fastmatch * d/tests/autopkgtest-pkg-r.conf: Add extra depends to fix autodep8 test Checksums-Sha1: ac2d70acaef9932400aa526b1d9f50bd929580f7 2255 r-bioc-gsva_1.38.2+ds-2.dsc 06ebb06e711af9b2ff25a3c3e42b43dbc730a127 2928 r-bioc-gsva_1.38.2+ds-2.debian.tar.xz 0cf6bbaf14151aa5c1c36e7b17701ba5afe0f022 12109 r-bioc-gsva_1.38.2+ds-2_amd64.buildinfo Checksums-Sha256: 67c632fac289c10ab9c746091b29ca56e11c41495b782f62402d076dd62c09a1 2255 r-bioc-gsva_1.38.2+ds-2.dsc 659ec50e1a3660f83ba80996bc2124dffdd54d5ec9879a009e54854db5ca7c14 2928 r-bioc-gsva_1.38.2+ds-2.debian.tar.xz 30f8b1a5d82905bf2c51c396c2829ea41007938df5df3eaed09f167ba0f995bc 12109 r-bioc-gsva_1.38.2+ds-2_amd64.buildinfo Files: 0de2c4f15c95bca43f39e9ec0615bafb 2255 gnu-r optional r-bioc-gsva_1.38.2+ds-2.dsc f2ec6d2511462f0a1cbb504e54b5494e 2928 gnu-r optional r-bioc-gsva_1.38.2+ds-2.debian.tar.xz ca57368abc630be45516111d56871b71 12109 gnu-r optional r-bioc-gsva_1.38.2+ds-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmCWKpAUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafHYhQ//eA/hYLXMTj6M/AOokfECdDHSXLU7 1ch889z94RBd3Fz/fJycJBERZx7takBevDCDVXM2mQOV7XQMyAg6Kh643GXV+CXH 7P+s9GnxngKmHQQVRpe5U4YqZL60aSabo0AOlJn36Z9u9c6zcAcQl44vt3BfLVeK BDDFoJJITOkXYojAK9Ki8NuzCLbhYRW/4yapUZVu540ooEbh0EjsTyCuAAeNRqbs 83wVz6L1nmYDng1U8MBG+Snzjmgzd08itQ4Qp357P6fDvlqtGAyfhgcJscFnXPQT Mot/u5ewclT8x/y1POar5J0Kyij0F6ccg98/QRnh6q9o4lH+BjpQ1mdY4W020WPB wyX0e6ziQ+xSG54fMA8YsWAAL8+A0t7edzzbE1H7lwrE28uFDu4HsfT4EGZMYk+Z kW9AgwIdnwZUyjFtDRv3fAffjHHUAAJf6N/rxESPqJRRmtHNFJJ5HIz5VKNKsOk9 bSCE5Qz+ltKGPfXrbvdFlHL+sCGZy/e1dfxDNPfhhVzpiGpFfuRR7Dh3PFHYFeQF U9ylSljI6fgfwk9rCihxeEVHjqXkMM+hbBFRq+67cnMZ6mOZCDd97mI/jA6qOL+X 7gBlU09KyCtIIrNvAFHM6a6W9asUnnS4NwSQzflqgIFRkPMgPwJ8VeU7Je4TAbVb IphI3zyW4NM5D1o= =XmeR -END PGP SIGNATURE End Message ---
Processed: Re: Bug#988208: CVE-2021-32062
Processing control commands: > block -1 by 988224 988225 Bug #988208 [src:mapserver] CVE-2021-32062 988208 was not blocked by any bugs. 988208 was not blocking any bugs. Added blocking bug(s) of 988208: 988225 and 988224 -- 988208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988208: CVE-2021-32062
Control: block -1 by 988224 988225 On 5/8/21 6:41 AM, Sebastiaan Couwenberg wrote: > On 5/7/21 9:14 PM, Moritz Muehlenhoff wrote: >> Patch for branch-7-6: >> https://github.com/mapserver/mapserver/commit/927ac97cb9ece305306b5ab2b5600d3afe8c1732 >> > > That does not apply cleanly on 7.6.2 in bullseye, due to the changes in: > > > https://github.com/MapServer/MapServer/commit/b128dace3ec3e61bf063f7285d1279e9f9fd9e28 > > We'll need to include both in the update for bullseye, or hack the patch > to make it apply without those changes which I'm not very confident in. > > I'm not sure if the release team will accept the additional changes > though, for both the bullseye unblock and buster pu. The unblock for bullseye is requested in #988224 with both upstream commits as patches. The same changes have been applied for 7.2 in buster, pu #988225. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#988101: marked as done (golang-testify: failing tests on armhf)
Your message dated Sat, 08 May 2021 04:48:36 + with message-id and subject line Bug#988101: fixed in golang-testify 1.6.1-2 has caused the Debian Bug report #988101, regarding golang-testify: failing tests 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.) -- 988101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-testify Version: 1.6.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source User: de...@lists.apertis.org Usertags: apertis-ftbfs X-Debbugs-Cc: de...@lists.apertis.org Dear Maintainer, While preparing the pacakge for a derivative distribution, I have come to notice that the package's (some of the) tests, fail on the armhf architecture. The build failure snippet is below. I also noticed that the same has been seen on the reproducible builds too. === RUN TestBoolAssertionFunc === RUN TestBoolAssertionFunc/true === RUN TestBoolAssertionFunc/false --- PASS: TestBoolAssertionFunc (0.00s) --- PASS: TestBoolAssertionFunc/true (0.00s) --- PASS: TestBoolAssertionFunc/false (0.00s) === RUN TestErrorAssertionFunc === RUN TestErrorAssertionFunc/noError === RUN TestErrorAssertionFunc/error --- PASS: TestErrorAssertionFunc (0.00s) --- PASS: TestErrorAssertionFunc/noError (0.00s) --- PASS: TestErrorAssertionFunc/error (0.00s) PASS ok github.com/stretchr/testify/require 0.823s === RUN TestPassedReturnsTrueWhenAllTestsPass --- PASS: TestPassedReturnsTrueWhenAllTestsPass (0.00s) === RUN TestPassedReturnsFalseWhenSomeTestFails --- PASS: TestPassedReturnsFalseWhenSomeTestFails (0.00s) === RUN TestSuiteRequireTwice === RUN TestSuiteRequireTwice === RUN TestSuiteRequireTwice/TestRequireOne suite_test.go:42: Error Trace:suite_test.go:42 Error: Not equal: expected: 1 actual : 2 Test: TestSuiteRequireTwice/TestRequireOne === RUN TestSuiteRequireTwice/TestRequireTwo suite_test.go:47: Error Trace:suite_test.go:47 Error: Not equal: expected: 1 actual : 2 Test: TestSuiteRequireTwice/TestRequireTwo --- FAIL: TestSuiteRequireTwice (0.03s) --- FAIL: TestSuiteRequireTwice/TestRequireOne (0.01s) --- FAIL: TestSuiteRequireTwice/TestRequireTwo (0.00s) --- PASS: TestSuiteRequireTwice (0.03s) === RUN TestSuiteRecoverPanic === RUN TestPanicInSetupSuite suite.go:63: test panicked: oops in setup suite goroutine 21 [running]: runtime/debug.Stack(0x842dbc, 0x2f5ab0, 0x390fc0) /usr/lib/go-1.15/src/runtime/debug/stack.go:24 +0x78 github.com/stretchr/testify/suite.failOnPanic(0x904e00) /srv/build/golang-testify-1.6.1/obj-arm-linux-gnueabihf/src/github.com/stretchr/testify/suite/suite.go:63 +0x3c panic(0x2f5ab0, 0x390fc0) /usr/lib/go-1.15/src/runtime/panic.go:969 +0x158 github.com/stretchr/testify/suite.(*panickingSuite).SetupSuite(0x915260) /srv/build/golang-testify-1.6.1/obj-arm-linux-gnueabihf/src/github.com/stretchr/testify/suite/suite_test.go:63 +0x38 github.com/stretchr/testify/suite.Run(0x904e00, 0x3966d8, 0x915260) /srv/build/golang-testify-1.6.1/obj-arm-linux-gnueabihf/src/github.com/stretchr/testify/suite/suite.go:118 +0x45c github.com/stretchr/testify/suite.TestSuiteRecoverPanic.func1(0x904e00) /srv/build/golang-testify-1.6.1/obj-arm-linux-gnueabihf/src/github.com/stretchr/testify/suite/suite_test.go:108 +0x40 testing.tRunner(0x904e00, 0x35343c) /usr/lib/go-1.15/src/testing/testing.go:1123 +0xc8 created by testing.(*T).Run /usr/lib/go-1.15/src/testing/testing.go:1168 +0x220 --- FAIL: TestPanicInSetupSuite (0.01s) === RUN TestPanicInSetupTest === RUN TestPanicInSetupTest/Test suite.go:63: test panicked: oops in setup test goroutine 23 [running]: runtime/debug.Stack(0x89ed64, 0x2f5ab0, 0x390fc8) /usr/lib/go-1.15/src/runtime/debug/stack.go:24 +0x78 github.com/stretchr/testify/suite.failOnPanic(0x904fc0) /srv/build/golang-testify-1.6.1/obj-arm-linux-gnueabihf/src/github.com/stretchr/testify/suite/suite.go:63 +0x3c pa
Bug#988208: CVE-2021-32062
On 5/7/21 9:14 PM, Moritz Muehlenhoff wrote: > Patch for branch-7-6: > https://github.com/mapserver/mapserver/commit/927ac97cb9ece305306b5ab2b5600d3afe8c1732 > That does not apply cleanly on 7.6.2 in bullseye, due to the changes in: https://github.com/MapServer/MapServer/commit/b128dace3ec3e61bf063f7285d1279e9f9fd9e28 We'll need to include both in the update for bullseye, or hack the patch to make it apply without those changes which I'm not very confident in. I'm not sure if the release team will accept the additional changes though, for both the bullseye unblock and buster pu. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."
Processing control commands: > clone 975490 -1 Bug #975490 [u-boot-sunxi] u-boot-sunxi: Booting the system got stuck after "Starting kernel ..." Bug 975490 cloned as bug 988217 > retitle -1 bootefi causes boot failure with boot.scr Bug #988217 [u-boot-sunxi] u-boot-sunxi: Booting the system got stuck after "Starting kernel ..." Changed Bug title to 'bootefi causes boot failure with boot.scr' from 'u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."'. > tags -1 + fixed-upstream Bug #988217 [u-boot-sunxi] bootefi causes boot failure with boot.scr Added tag(s) fixed-upstream. > tags -1 + patch Bug #988217 [u-boot-sunxi] bootefi causes boot failure with boot.scr Added tag(s) patch. > severity -1 important Bug #988217 [u-boot-sunxi] bootefi causes boot failure with boot.scr Severity set to 'important' from 'critical' -- 975490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975490 988217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."
Control: clone 975490 -1 Control: retitle -1 bootefi causes boot failure with boot.scr Control: tags -1 + fixed-upstream Control: tags -1 + patch Control: severity -1 important On 2021-04-16, Bastian Germann wrote: > On a Lamobo R1, I can verify 2021.01 versions not to boot with a > default environment. However, 2020.10+dfsg-2 boots. Even though the > original issue has the same outcome, I guess it is caused by something > else. Different enough to warrant it's own bug, cloning... > I figured out my problem is caused by > https://github.com/u-boot/u-boot/commit/f3866909e35074ea6f50226d40487a180de1132f. > The > boot_efi_bootmgr will run and read a bad dtb, which makes a boot.scr > boot fail. This would definitely be good to fix in bullseye, but this is quite late in the release cycle. Will need to test failure and success cases with and without EFI as well as boot.scr and extlinux.conf to make sure this doesn't cause regressions in other boot paths... An ugly workaround in the meantime would be to add a no-op boot.scr on the media (e.g. mmc0) and then fall back to the other boot methods. live well, vagrant signature.asc Description: PGP signature
Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."
On Fri, 16 Apr 2021 17:06:37 +0200 Bastian Germann wrote: > The issue is fixed in 2021.04 (experimental) which has the same default environment as 2021.01. The upstream commit that fixed this is https://github.com/u-boot/u-boot/commit/82d01f04facef1276cede067efd02d2a731ffe83 It applies cleanly on 2021.01+dfsg-4. Please include it or change the config for the affected boards not to try EFI bootmanager. Any news on this? It would be great if that patch would be integrated into the bullseye version.
Processed: tagging 988208, bug 988208 is forwarded to https://github.com/mapserver/mapserver/issues/6313 ...
Processing commands for cont...@bugs.debian.org: > tags 988208 + upstream Bug #988208 [src:mapserver] CVE-2021-32062 Added tag(s) upstream. > forwarded 988208 https://github.com/mapserver/mapserver/issues/6313 Bug #988208 [src:mapserver] CVE-2021-32062 Set Bug forwarded-to-address to 'https://github.com/mapserver/mapserver/issues/6313'. > found 988208 7.6.2-1 Bug #988208 [src:mapserver] CVE-2021-32062 Marked as found in versions mapserver/7.6.2-1. > fixed 988208 7.6.3-1~exp1 Bug #988208 [src:mapserver] CVE-2021-32062 Marked as fixed in versions mapserver/7.6.3-1~exp1. > found 988208 7.2.2-1 Bug #988208 [src:mapserver] CVE-2021-32062 Marked as found in versions mapserver/7.2.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 988208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 988214 in 2:6.0.3.5+dfsg-1, tagging 988214
Processing commands for cont...@bugs.debian.org: > found 988214 2:6.0.3.5+dfsg-1 Bug #988214 [rails] CVE-2021-22885 CVE-2021-22902 CVE-2021-22904 Marked as found in versions rails/2:6.0.3.5+dfsg-1. > tags 988214 + upstream fixed-upstream Bug #988214 [rails] CVE-2021-22885 CVE-2021-22902 CVE-2021-22904 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 988214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 988141 is grave
Processing commands for cont...@bugs.debian.org: > severity 988141 grave Bug #988141 [src:impacket] impacket: CVE-2021-31800 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 988141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988214: CVE-2021-22885 CVE-2021-22902 CVE-2021-22904
Package: rails Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team CVE-2021-22904: https://github.com/rails/rails/commit/d861fa8ade353390c4419b53a6c6b41f3005b1f2 (v6.0.3.7) CVE-2021-22902: Fixed by: https://github.com/rails/rails/commit/446afbd15360a347c923ca775b21a286dcb5297a (v6.0.3.7) CVE-2021-22885: https://github.com/rails/rails/commit/f202249bdd701f908a57d733e633d366a982f8ce (v6.0.3.7) Cheers, Moritz
Bug#988147: marked as done (psychopy: unhandled symlink to directory conversion: /usr/share/doc/psychopy/examples)
Your message dated Fri, 07 May 2021 19:33:28 + with message-id and subject line Bug#988147: fixed in psychopy 2020.2.10+dfsg-2 has caused the Debian Bug report #988147, regarding psychopy: unhandled symlink to directory conversion: /usr/share/doc/psychopy/examples 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.) -- 988147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: psychopy Version: 2020.2.10+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: stretch -> buster (which had no psychopy package, thus keeping the stretch version installed) -> bullseye For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 2m50.7s ERROR: installs objects over existing directory symlinks: /usr/share/doc/psychopy/examples/color_changer.py (psychopy) != /usr/lib/python2.7/dist-packages/psychopy/demos/color_changer.py (?) /usr/share/doc/psychopy/examples -> ../../../lib/python2.7/dist-packages/psychopy/demos /usr/share/doc/psychopy/examples/demos (psychopy) != /usr/lib/python2.7/dist-packages/psychopy/demos/demos (?) /usr/share/doc/psychopy/examples -> ../../../lib/python2.7/dist-packages/psychopy/demos /usr/share/doc/psychopy/examples/psychopy_helloworld.py (psychopy) != /usr/lib/python2.7/dist-packages/psychopy/demos/psychopy_helloworld.py (?) /usr/share/doc/psychopy/examples -> ../../../lib/python2.7/dist-packages/psychopy/demos /usr/share/doc/psychopy/examples/run_coder.py (psychopy) != /usr/lib/python2.7/dist-packages/psychopy/demos/run_coder.py (?) /usr/share/doc/psychopy/examples -> ../../../lib/python2.7/dist-packages/psychopy/demos cheers, Andreas psychopy_2020.2.10+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: psychopy Source-Version: 2020.2.10+dfsg-2 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of psychopy, 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 988...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated psychopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 07 May 2021 20:57:53 +0200 Source: psychopy Architecture: source Version: 2020.2.10+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 988147 Changes: psychopy (2020.2.10+dfsg-2) unstable; urgency=medium . * Team upload * d/psychopy.maintscript: gracefully handle transition from symlink to regular directory of /usr/share/doc/psychopy/examples from Stretch t
Bug#988208: CVE-2021-32062
Source: mapserver Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team CVE-2021-32062: https://github.com/mapserver/mapserver/issues/6313 https://github.com/MapServer/MapServer/pull/6314 Patch for branch-7-6: https://github.com/mapserver/mapserver/commit/927ac97cb9ece305306b5ab2b5600d3afe8c1732 Cheers, Moritz
Bug#988147: [Debian-med-packaging] Bug#988147: psychopy: unhandled symlink to directory conversion: /usr/share/doc/psychopy/examples
Control: tag -1 pending Hi Andreas, Andreas Beckmann, on 2021-05-06 19:01:37 +0200: > This was observed on the following upgrade paths: > > stretch -> buster (which had no psychopy package, thus keeping the > stretch version installed) -> bullseye Thanks for testing the upgrade path since Stretch! :) I have impending changes to the package, but I still see some issues caused by libgssapi-krb5-2: 0m56.3s INFO: Warning: Package purging left files on system: /etc/gss/mech.d/README owned by: libgssapi-krb5-2:amd64 0m56.3s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/libgssapi-krb5-2:amd64.list not owned This is repeatable with piuparts on libgssapi-krb5-2 on stretch and warning on leftovers after purge. The first item is marked wontfix in #910344; #861218 provides the relevant background information. My common sense tells me the second item may well be a consequence of the file leftover; I might be wrong though. Anyways, for information to anyone wishing to reproduce the test... Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/8, please excuse my verbosity. signature.asc Description: PGP signature
Processed: Re: [Debian-med-packaging] Bug#988147: psychopy: unhandled symlink to directory conversion: /usr/share/doc/psychopy/examples
Processing control commands: > tag -1 pending Bug #988147 [psychopy] psychopy: unhandled symlink to directory conversion: /usr/share/doc/psychopy/examples Added tag(s) pending. -- 988147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988183: gemma ftbfs on buster, newer version builds fine one bullseye
Would a regular backport be the way to go?
Bug#988195: wine-development: starting wine-development failed due to wrong prefix
Package: wine-development Version: 5.9-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: a...@disroot.org After updated wine-development to 5.9-1, I executed finecfg and get this message: wine: chdir to /tmp/.wine-1000/server-804-8010e5 : No such file or directory I have check that $WINEPREFIX has empty value, so I think there is something wrong with the default setting. -- Package-specific info: /usr/bin/wine points to /usr/bin/wine-development. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (650, 'testing'), (550, 'unstable'), (500, 'testing-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE=zh_TW:zh Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wine-development depends on: ii wine32-development 5.9-1 ii wine64-development 5.9-1 wine-development recommends no packages. Versions of packages wine-development suggests: pn dosbox ii icoextract-thumbnailer [exe-thumbnailer] 0.1.2-2 pn playonlinux pn q4wine ii winbind 2:4.13.5+dfsg-1 pn wine-binfmt ii winetricks0.0+20210206-2 Versions of packages libwine-development depends on: ii libasound2 1.2.4-1.1 ii libc62.31-11 ii libfaudio0 21.02-1 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s110.2.1-6 ii libglib2.0-0 2.66.8-1 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgstreamer-plugins-base1.0-0 1.18.4-2 ii libgstreamer1.0-01.18.4-2 ii liblcms2-2 2.12~rc1-2 ii libldap-2.4-22.4.57+dfsg-2 ii libmpg123-0 1.26.4-1 ii libncurses6 6.2+20201114-2 ii libopenal1 1:1.19.1-2 ii libpcap0.8 1.10.0-2 ii libpulse014.2-2 ii libtinfo66.2+20201114-2 ii libudev1 247.3-5 ii libunwind8 1.3.2-2 ii libvkd3d11.1-5 ii libx11-6 2:1.7.0-2 ii libxext6 2:1.3.3-1.1 ii libxml2 2.9.10+dfsg-6.3+b1 ii libz-mingw-w64 1.2.11+dfsg-2 ii ocl-icd-libopencl1 [libopencl1] 2.2.14-2 Versions of packages libwine-development recommends: ii fonts-liberation 1:1.07.4-11 ii fonts-wine 5.0.3-3 ii gstreamer1.0-plugins-good 1.18.4-2 ii libasound2-plugins 1.2.2-2 ii libcapi20-31:3.27-3+b1 ii libcups2 2.3.3op2-3 ii libdbus-1-31.12.20-2 ii libgl1 1.3.2-1 ii libgl1-mesa-dri20.3.4-1 ii libglu1-mesa [libglu1] 9.0.1-1 ii libgnutls303.7.1-3 ii libgsm11.0.18-2 ii libgssapi-krb5-2 1.18.3-5 ii libjpeg62-turbo1:2.0.6-4 ii libkrb5-3 1.18.3-5 ii libodbc1 2.3.6-0.1+b1 ii libosmesa6 20.3.4-1 ii libpng16-161.6.37-3 ii libsdl2-2.0-0 2.0.14+dfsg2-3 ii libtiff5 4.2.0-1 ii libv4l-0 1.20.0-2 ii libvulkan1 1.2.162.0-1 ii libxcomposite1 1:0.4.5-1 ii libxcursor11:1.2.0-2 ii libxfixes3 1:5.0.3-2 ii libxi6 2:1.7.10-1 ii libxinerama1 2:1.1.4-2 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxslt1.1 1.1.34-4 ii libxxf86vm11:1.1.4-1+b2 Versions of packages libwine-development suggests: pn cups-bsd ii gstreamer1.0-libav 1.18.4-3 ii gstreamer1.0-plugins-bad 1.18.4-3 ii gstreamer1.0-plugins-ugly 1.18.4-2 pn ttf-mscorefonts-installer Versions of packages wine32-development depends on: ii libc62.31-11 ii libwine-development 5.9-1 wine32-development recommends no packages. Versions of packages wine32-development suggests: pn wine32-development-preloader Versions of packages wine64-development depends on: ii libc62.31-11 ii libwine-development 5.9-1 Versions of packages wine64-development recommends: ii wine32-development 5.9-1 Versions of packages wine64-development suggests: pn wine64-develop
Processed: Re: Bug#988052: dpkg-cross: does not convert path to dynamic loader in linker scripts
Processing control commands: > tags -1 + patch Bug #988052 [dpkg-cross] dpkg-cross: does not convert path to dynamic loader in linker scripts Added tag(s) patch. -- 988052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988052: dpkg-cross: does not convert path to dynamic loader in linker scripts
Control: tags -1 + patch On Wed, May 05, 2021 at 03:16:05PM +0200, Helmut Grohne wrote: > As a minimally invasive solution (until we understand why multiarch is > handled differently here), I propose handling the dynamic loader > specially and fixing it up regardless of whether the package is > multiarch. I'm attaching a patch to this end. It only fixes /lib, > /lib32, /lib64 and /libx32 as no other multilib ever contained a dynamic > loader. I've tried testing the patch on jenkins.d.n, but it presently tempfails all jobs. We cannot count on that. In those tests that ran, I couldn't find any regression nor could did I reencounter the relevant symptom. I therefore suggest moving forward with my path to get it into bullseye. Wookey, can you upload it? I can NMU if you are busy. Helmut
Processed: Problem is also in buster
Processing commands for cont...@bugs.debian.org:
> unarchive 935280
Bug #935280 {Done: Dimitri John Ledkov } [src:gcc-h8300-hms]
gcc-h8300-hms: FTBFS on arm64
Unarchived Bug 935280
> tags 935280 buster
Bug #935280 {Done: Dimitri John Ledkov } [src:gcc-h8300-hms]
gcc-h8300-hms: FTBFS on arm64
Added tag(s) buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
935280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 925847 is serious
Processing commands for cont...@bugs.debian.org:
> severity 925847 serious
Bug #925847 {Done: Ondřej Nový } [src:uvloop] uvloop FTBFS
with new OpenSSL
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
925847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#986286: marked as done (diaspora-installer: fails to install: Your bundle is locked to mimemagic (0.3.5), but that version could not be found)
Your message dated Fri, 07 May 2021 09:18:27 + with message-id and subject line Bug#986286: fixed in diaspora-installer 0.7.15.0+debian has caused the Debian Bug report #986286, regarding diaspora-installer: fails to install: Your bundle is locked to mimemagic (0.3.5), but that version could not be found 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.) -- 986286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: diaspora-installer Version: 0.7.14.0+debian2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up diaspora-installer (0.7.14.0+debian2) ... Download diaspora tarball version 0.7.14.0 from github.com... --2021-04-02 11:03:54-- https://github.com/diaspora/diaspora/archive/v0.7.14.0.tar.gz Resolving github.com (github.com)... 140.82.121.4 Connecting to github.com (github.com)|140.82.121.4|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/diaspora/diaspora/tar.gz/v0.7.14.0 [following] --2021-04-02 11:03:54-- https://codeload.github.com/diaspora/diaspora/tar.gz/v0.7.14.0 Resolving codeload.github.com (codeload.github.com)... 140.82.121.9 Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: '/var/cache/diaspora-installer/diaspora-0.7.14.0.tar.gz' /var/cach [<=> ] 0 --.-KB/s /var/cache [ <=>] 1.45M 7.11MB/s /var/cache/ [ <=> ] 3.79M 9.36MB/s /var/cache/d [ <=> ] 8.59M 14.2MB/s /var/cache/diaspora [<=> ] 9.45M 14.0MB/sin 0.7s 2021-04-02 11:03:55 (14.0 MB/s) - '/var/cache/diaspora-installer/diaspora-0.7.14.0.tar.gz' saved [9911008] Checking integrity of download... /var/cache/diaspora-installer/diaspora-0.7.14.0.tar.gz: OK Extracting files... Copying files to /usr/share/diaspora... diaspora archive to copy: diaspora-0.7.14.0 Copying source tarball to /var/lib/diaspora/public... Setting up environment varibales... Using /etc/diaspora/diaspora.conf... DB_NAME=diaspora_production Using system bundler... Installing gems with rubygems ... [ESC][33m[DEPRECATED] The `--frozen` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local frozen 'true'`, and stop using this flag[ESC][0m [ESC][33m[DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local path 'vendor/bundle'`, and stop using this flag[ESC][0m [ESC][33m[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'development test'`, and stop using this flag[ESC][0m [ESC][33m[DEPRECATED] The `--with` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local with 'postgresql'`, and stop using this flag[ESC][0m Fetching gem metadata from https://gems.diasporafoundation.org/.. Fetching gem metadata from https://rubygems.org/.. [ESC][31mYour bundle is locked to mimemagic (0.3.5), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of mimemagic (0.3.5) has removed it. You'll need to update your bundle to a version other than mimemagic (0.3.5) that hasn't been removed in order to install.[ESC][0m dpkg: error processing package diaspora-installer (--configure): installed diaspora-installer package post-installation script subprocess returned error exit status 7 Processing triggers for libc-bin (2.31-11) ... Processing triggers for ca-certificates (20210119) ... Upda
Processed: gemma FTBFS on i386 in buster
Processing control commands: > close -1 0.98.4+dfsg-3 Bug #988183 [src:gemma] gemma FTBFS on i386 in buster Marked as fixed in versions gemma/0.98.4+dfsg-3. Bug #988183 [src:gemma] gemma FTBFS on i386 in buster Marked Bug as done -- 988183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988183: gemma FTBFS on i386 in buster
Source: gemma Version: 0.98.1+dfsg-1 Severity: serious Tags: ftbfs Control: close -1 0.98.4+dfsg-3 https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/gemma.html ... ./bin/unittests-gemma Mismatch coordinates (1,0)0:3! This example computes real matrix C=alpha*A*B+beta*C using Intel(R) MKL function dgemm, where A, B, and C are matrices and alpha and beta are double precision scalars Initializing data for matrix multiplication C=A*B for matrix A(2000x200) and matrix B(200x1000) Allocating memory for matrices aligned on 64-byte boundary for better performance Intializing matrix data Computing matrix product using Intel(R) MKL dgemm function via CBLAS interface ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ unittests-gemma is a Catch v1.12.1 host application. Run with -? for options --- cblas_dgemm --- test/src/unittests-math.cpp:76 ... test/src/unittests-math.cpp:76: FAILED: due to a fatal error condition: SIGSEGV - Segmentation violation signal === test cases: 3 | 2 passed | 1 failed assertions: 25 | 18 passed | 7 failed make[2]: *** [Makefile:226: unittests] Segmentation fault
Bug#988181: julia FTBFS on i386 in buster
Source: julia Version: 1.0.3+dfsg-4 Severity: serious Tags: ftbfs Control: close -1 1.5.3+dfsg-3 https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/julia.html ... signal (11): Segmentation fault signal (11): Segmentation fault in expression starting at /build/julia-1.0.3+dfsg/usr/share/julia/stdlib/v1.0/Distributed/test/distributed_exec.jl:758 in expression starting at /build/julia-1.0.3+dfsg/usr/share/julia/stdlib/v1.0/Distributed/test/distributed_exec.jl:758 signal (11): Segmentation fault in expression starting at /build/julia-1.0.3+dfsg/usr/share/julia/stdlib/v1.0/Distributed/test/distributed_exec.jl:758 Distributed: Error During Test at /build/julia-1.0.3+dfsg/test/testdefs.jl:19 Got exception outside of a @test LoadError: Distributed test failed, cmd : `/build/julia-1.0.3+dfsg/usr/bin/julia --check-bounds=yes --startup-file=no --depwarn=error /build/julia-1.0.3+dfsg/usr/share/julia/stdlib/v1.0/Distributed/test/distributed_exec.jl` Stacktrace: [1] error(::String) at ./error.jl:33 in expression starting at /build/julia-1.0.3+dfsg/usr/share/julia/stdlib/v1.0/Distributed/test/runtests.jl:10 Distributed: Error During Test at none:1 Test threw exception Expression: Distributed Some tests did not pass: 0 passed, 0 failed, 1 errored, 0 broken. ... Error in testset Distributed: Error During Test at none:1 Test threw exception Expression: Distributed Some tests did not pass: 0 passed, 0 failed, 1 errored, 0 broken. ERROR: LoadError: Test run finished with errors in expression starting at /build/julia-1.0.3+dfsg/test/runtests.jl:61 make[2]: *** [Makefile:22: all] Error 1
Processed: julia FTBFS on i386 in buster
Processing control commands: > close -1 1.5.3+dfsg-3 Bug #988181 [src:julia] julia FTBFS on i386 in buster Marked as fixed in versions julia/1.5.3+dfsg-3. Bug #988181 [src:julia] julia FTBFS on i386 in buster Marked Bug as done -- 988181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
