Bug#995200: r-bioc-dropletutils: autopkgtest failures
# Reduce severity severity 995200 important thanks As per discussion here[1], we ignored these two tests for now, hence decreasing the severity, so everything migrates timely. [1]: https://lists.debian.org/debian-r/2021/09/msg00127.html Nilesh signature.asc Description: PGP signature
Bug#995204: marked as done (r-bioc-metapod: autopkgtest failures)
Your message dated Tue, 28 Sep 2021 11:02:08 +0530
with message-id
and subject line Re: r-bioc-metapod: autopkgtest failures
has caused the Debian Bug report #995204,
regarding r-bioc-metapod: autopkgtest failures
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.)
--
995204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-metapod
Version: 1.0.0+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
| > test_check("metapod")
| autopkgtest [00:12:43]: ERROR: timed out on command "su -s /bin/bash debci -c
set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; .
~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.fq0j71sv/downtmp/build.BVG/src"; mkdir -p -m
1777 -- "/tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.fq0j71sv/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.fq0j71sv/downtmp/autopkgtest_tmp"; export
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=48; unset LANGUAGE LC_CTYPE
LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME
LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd
"$buildtree"; chmod +x
/tmp/autopkgtest-lxc.fq0j71sv/downtmp/build.BVG/src/debian/tests/run-unit-test;
touch /tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stdout
/tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stderr;
/tmp/autopkgtest-lxc.fq0j71sv/downtmp/build.BVG/src/debian/tests/run-unit-test
2> >(tee -a /tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stderr >&2) >
>(tee -a /tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stdout);" (kind:
test)
and
| > test_check("metapod")
| terminate called after throwing an instance of
'__gnu_cxx::recursive_init_error'
| what(): std::exception
| Aborted
See
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-metapod/15217942/log.gz
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Control: fixed 995204 1.0.0+dfsg-3
amd64 autopkgtest is still in progress, but arm, i386 are passing
already, the problem has been fixed.
https://ci.debian.net/data/autopkgtest/testing/arm64/r/r-bioc-metapod/15586577/log.gz
There is a failure in armhf, but that one is unrelated. I'm at it,
please don't file another bug for that one.
Thanks for reporting!
Nilesh
signature.asc
Description: PGP signature
--- End Message ---
Processed: Re: r-bioc-dropletutils: autopkgtest failures
Processing commands for cont...@bugs.debian.org: > # Reduce severity > severity 995200 important Bug #995200 [src:r-bioc-dropletutils] r-bioc-dropletutils: autopkgtest failures Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 995200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995220: FTBFS: build broken by typescript update
Package: ts-node
Version: 9.1.1-4
Severity: serious
Tags: sid
ts-node is broken by typescript update. This fix first part of build:
--- a/src/repl.ts
+++ b/src/repl.ts
@@ -98,6 +98,7 @@ export function createRepl (options: Cre
console.error(error)
}
} else {
+// @ts-ignore
err = error
}
}
but later:
./debian/tests/test_modules/typescript-json-schema/bin/typescript-json-schema
\
--topRef --refs --validationKeywords allOf \
--out tsconfig.schema.json tsconfig.json TsConfigSchema
/<>/debian/tests/test_modules/typescript-json-schema/dist/typescript-json-schema.js:965
throw new Error("type " + symbolName + " not found");
^
Error: type TsConfigSchema not found
at JsonSchemaGenerator.getSchemaForSymbol
(/<>/debian/tests/test_modules/typescript-json-schema/dist/typescript-json-schema.js:965:19)
at generateSchema
(/<>/debian/tests/test_modules/typescript-json-schema/dist/typescript-json-schema.js:1151:26)
at Object.exec
(/<>/debian/tests/test_modules/typescript-json-schema/dist/typescript-json-schema.js:1200:22)
at Object.run
(/<>/debian/tests/test_modules/typescript-json-schema/dist/typescript-json-schema-cli.js:51:30)
at Object.
(/<>/debian/tests/test_modules/typescript-json-schema/bin/typescript-json-schema:3:5)
[...]
Bug#995208: marked as done (r-bioc-rhdf5filters: autopkgtest regression)
Your message dated Tue, 28 Sep 2021 05:48:21 + with message-id and subject line Bug#995208: fixed in r-bioc-rhdf5filters 1.4.0+dfsg-3 has caused the Debian Bug report #995208, regarding r-bioc-rhdf5filters: autopkgtest regression 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.) -- 995208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-rhdf5filters Version: 1.4.0+dfsg-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org | E: Unable to locate package r-cran-rhdf5 | pkg-r-autopkgtestFAIL badpkg | blame: r-bioc-rhdf5filters See https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-rhdf5filters/15560573/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: r-bioc-rhdf5filters Source-Version: 1.4.0+dfsg-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-bioc-rhdf5filters, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated r-bioc-rhdf5filters 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: Tue, 28 Sep 2021 10:58:01 +0530 Source: r-bioc-rhdf5filters Architecture: source Version: 1.4.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 995208 Changes: r-bioc-rhdf5filters (1.4.0+dfsg-3) unstable; urgency=medium . * Team Upload. * d/t/autopkgtest-pkg-r.conf: Fix the name of test-depends, r-cran-rhdf5 => r-bioc-rhdf5 (Closes: #995208) Checksums-Sha1: 3efd0b76f4dfdd24f9683729ff8062cc39cff89d 2205 r-bioc-rhdf5filters_1.4.0+dfsg-3.dsc 9c6bb5f8c478052f4025c69a3ca6922d12b4b8a2 5064 r-bioc-rhdf5filters_1.4.0+dfsg-3.debian.tar.xz 0884b82ec6eb695393f3c93cd1092500db83adb9 11018 r-bioc-rhdf5filters_1.4.0+dfsg-3_amd64.buildinfo Checksums-Sha256: 394c941287b5eff9806d95c1eefda1c255997a1d15b420b3f6d447a9105cbb91 2205 r-bioc-rhdf5filters_1.4.0+dfsg-3.dsc 1b2b2a9f1b1f8a9becc427b1c95bccddc9eddcd048e2c8c2ef47262e133a59a3 5064 r-bioc-rhdf5filters_1.4.0+dfsg-3.debian.tar.xz 223f66e19c383041aef0e9d1ceabfc47c9c2812d550d3b74c8c3a3f4876a860c 11018 r-bioc-rhdf5filters_1.4.0+dfsg-3_amd64.buildinfo Files: 85a4eef34b3593b51a6ba89f6e7eecad 2205 gnu-r optional r-bioc-rhdf5filters_1.4.0+dfsg-3.dsc 1f21b766e700530a9fdd494b7b042d0a 5064 gnu-r optional r-bioc-rhdf5filters_1.4.0+dfsg-3.debian.tar.xz ef1320f9d8f6edc5800b1e3eafcfb585 11018 gnu-r optional r-bioc-rhdf5filters_1.4.0+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmFSqwoUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafGTmA/8CLpndpIY/ygpklnap5TVSRJeNg6F vru4k+wGv5be66j8SY5QlT1oHLTAxJuFNXPcI83E35ZAWrnyuCnk6bIshiXDHPLf OOqYQOI8u3nktqtPadRAoBLdqDXZM4k8dZKrvTe8Tln2NsYIA2AJKfkXv92wZYNd jNMis3mmgX79bwd85rSprzGTj0z5e3toTUIz57X9jzURjjxiKoTTvmAsVC/m8RoZ zf7YVw6IrGaP4EcYwtVBrtoIlN1lnMGEQ6CZB+UPDzfzRvOzyBZTPGgpNeKx/sPy GMtFRyatYJvSa6MaQYufqTYCv63kLn/yGRcko2nV36Wqp14cA8xlJb1qZVKZBJ08 vOG8pwRNLWK4NkHrdlDRjgBTLYy3lSCn4Z9wxNWthwRGyR3QpyizAMIdCPuZo+Sk spTNBScI4HVsP7koB2fkV3VVghYqSSnPAltYV2r4QB2Q0N9yKaBhGFWAFXiLE+3t pgpZGTNTxaDl6QaCCrwGpyIQYXWdue1YOhd82pduOJ3D8R7lidLSZCYkai45+ANw +4kSO+tZvMuxd+2xWPngek7Kkm1wbSTEoCv+1xb6xhjd3vfasGklCKHG1g37C8e/ WbSGlsexQTu+zl83eQjQst7vKbeNRBXKw3I8y2bes5D4HpNk72gCBUYHFu5xlNdB WFByLguYyQOWVpc= =JM7A -END PGP SIGNATURE End Message ---
Processed: close and fix
Processing commands for cont...@bugs.debian.org:
> reopen 995204
Bug #995204 {Done: Nilesh Patra } [src:r-bioc-metapod]
r-bioc-metapod: autopkgtest failures
Bug reopened
Ignoring request to alter fixed versions of bug #995204 to the same values
previously set
> fixed 995204 1.0.0+dfsg-3
Bug #995204 [src:r-bioc-metapod] r-bioc-metapod: autopkgtest failures
Marked as fixed in versions r-bioc-metapod/1.0.0+dfsg-3.
> close 995204
Bug #995204 [src:r-bioc-metapod] r-bioc-metapod: autopkgtest failures
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
995204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#993029: Have we found a fix for this issue yet?
What's the status of this bug right now? Have we notified upstream? Abraham Raji -- Mea navis aëricumbens anguillis abundat.
Bug#993198: gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40
Hello Leo, > On Fri, Sep 24, 2021 at 10:07 PM Samuel Henrique wrote: > > Leo, from my side you're free to push your changes whenever you want. > > I will as soon as someone gives me access to the repo ;) > Just requested access to the Gnome group, but that may take a while. I gave you permission to that repo (best I can do on my side), and I set an expiration date of the end of this year, until then you will end up in the salsa group and inherit permissions so it should be good. > > Let's try to coordinate things, feel free to perform changes to the > > packaging, I will wait until I get your ack to go ahead (if there's > > any work left to be done). > > I'm not a gnome-extension expert, so I'll push my changes so that the > package is at least gpb-buildable, and you can then maybe check that > the build makes sense and upload it yourself if you want. Awesome, I can do that. Alternatively, I can also push your changes myself, if you push them to your own repo and give me a go ahead. Thank you! -- Samuel Henrique
Processed: Re: Bug#995207: chrony: Using 'bindacqdevice' directive causes a SIGSYS error
Processing control commands: > tags -1 - upstream + moreinfo Bug #995207 [chrony] chrony: Using 'bindacqdevice' directive causes a SIGSYS error Removed tag(s) upstream. Bug #995207 [chrony] chrony: Using 'bindacqdevice' directive causes a SIGSYS error Added tag(s) moreinfo. > severity -1 important Bug #995207 [chrony] chrony: Using 'bindacqdevice' directive causes a SIGSYS error Severity set to 'important' from 'critical' -- 995207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995207: chrony: Using 'bindacqdevice' directive causes a SIGSYS error
Control: tags -1 - upstream + moreinfo Control: severity -1 important Hi, Le 2021-09-27 17:31, Steve Egbert a écrit : > Package: chrony > Version: 4.0-8 > Severity: critical > Tags: upstream > X-Debbugs-Cc: s.egb...@sbcglobal.net > > Dear Maintainer, > > > Wanted to use the 'bindacqdevice' due to my host having a dynamic IP > interface. > > Using that 'bindacqdevice' directive keyword anywhere in my > /etc/chrony/chrony.conf file results in a signal 31 (according to Linux > auditd). > > My guess is that attempts to do a Chrony as a NTP server (disbursing out > NTP beacons), we need to have an socket open on this dynamic IP interface. > > This is the setting of the systemd resource. > > Removing the 'bindacqdevice' directive, and all works perfectly. > > Was half-expecting to be able to use 'bindacqdevice' configuration directive > here. After having stopped chronyd, please run the command below when using the 'bindacqdevice' directive and attach the chronyd_debug.txt file. # strace -o chronyd_debug.txt chronyd -d -F -1 Cheers, Vincent signature.asc Description: PGP signature
Bug#995208: r-bioc-rhdf5filters: autopkgtest regression
Source: r-bioc-rhdf5filters Version: 1.4.0+dfsg-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org | E: Unable to locate package r-cran-rhdf5 | pkg-r-autopkgtestFAIL badpkg | blame: r-bioc-rhdf5filters See https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-rhdf5filters/15560573/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#995207: chrony: Using 'bindacqdevice' directive causes a SIGSYS error
Package: chrony Version: 4.0-8 Severity: critical Tags: upstream X-Debbugs-Cc: s.egb...@sbcglobal.net Dear Maintainer, Wanted to use the 'bindacqdevice' due to my host having a dynamic IP interface. Using that 'bindacqdevice' directive keyword anywhere in my /etc/chrony/chrony.conf file results in a signal 31 (according to Linux auditd). My guess is that attempts to do a Chrony as a NTP server (disbursing out NTP beacons), we need to have an socket open on this dynamic IP interface. This is the setting of the systemd resource. Removing the 'bindacqdevice' directive, and all works perfectly. Was half-expecting to be able to use 'bindacqdevice' configuration directive here. -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.46 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chrony depends on: ii adduser 3.118 ii init-system-helpers 1.60 ii iproute2 5.10.0-4 ii libc62.31-13 ii libcap2 1:2.44-1 ii libedit2 3.1-20191231-2+b1 ii libgnutls30 3.7.1-5 ii libnettle8 3.7.3-1 ii libseccomp2 2.5.1-1 ii tzdata 2021a-1 ii ucf 3.0043 chrony recommends no packages. Versions of packages chrony suggests: ii bind9-dnsutils [dnsutils] 1:9.16.15-1 pn networkd-dispatcher -- Configuration Files: /etc/default/chrony changed: DAEMON_OPTS="-F 1 -L 0" -- no debconf information
Bug#995206: r-bioc-altcdfenvs: autopkgtest regression
Source: r-bioc-altcdfenvs Version: 1:2.54.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org | E: Unable to locate package r-cran-r-unit | pkg-r-autopkgtestFAIL badpkg | blame: r-bioc-altcdfenvs Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#995204: r-bioc-metapod: autopkgtest failures
Source: r-bioc-metapod
Version: 1.0.0+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
| > test_check("metapod")
| autopkgtest [00:12:43]: ERROR: timed out on command "su -s /bin/bash debci -c
set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; .
~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.fq0j71sv/downtmp/build.BVG/src"; mkdir -p -m
1777 -- "/tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.fq0j71sv/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.fq0j71sv/downtmp/autopkgtest_tmp"; export
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=48; unset LANGUAGE LC_CTYPE
LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME
LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd
"$buildtree"; chmod +x
/tmp/autopkgtest-lxc.fq0j71sv/downtmp/build.BVG/src/debian/tests/run-unit-test;
touch /tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stdout
/tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stderr;
/tmp/autopkgtest-lxc.fq0j71sv/downtmp/build.BVG/src/debian/tests/run-unit-test
2> >(tee -a /tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stderr >&2) >
>(tee -a /tmp/autopkgtest-lxc.fq0j71sv/downtmp/run-unit-test-stdout);" (kind:
test)
and
| > test_check("metapod")
| terminate called after throwing an instance of
'__gnu_cxx::recursive_init_error'
| what(): std::exception
| Aborted
See
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-metapod/15217942/log.gz
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#995073: gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".
On 26 September 2021 8:14:08 pm IST, Ondrej Zary wrote: >> yarn 3.0 needs nodejs 12. So this was a work around used to force yarn >> 2.x. Looks like there is no way to install 2.x versions of yarn anymore :( >> >> So we will have to update minimum version of nodejs to 12 (already done >> for latest versions in bullseye) and use yarn set version berry. I guess >> you will have to use nodejs from official repos or we will have to >> backport nodejs 12 to buster. > >I've built nodejs 12 and added "yarnpng set version berry" before >"yarnpkg set version 2.4.2". >It downloaded tons of random crap from somewhere during the "fetch step". >Is that normal? Not sure which packages it pulls in that step. >Otherwise it seems to work. >Webpack failed, as always...3 kinds of errors this time. > >Installing node modules... >(node:22064) [DEP0005] DeprecationWarning: Buffer() is deprecated due to >security and usability issues. Please use the Buffer.alloc(), >Buffer.allocUnsafe(), or Buffer.from() methods instead. >Resolving berry to a url... >Downloading >https://github.com/yarnpkg/berry/raw/master/packages/berry-cli/bin/berry.js... >Saving it into /var/lib/gitlab/.yarn/releases/yarn-berry.js... >Updating /var/lib/gitlab/.yarnrc.yml... >Done! >➤ YN: Retrieving >https://repo.yarnpkg.com/2.4.2/packages/yarnpkg-cli/bin/yarn.js >➤ YN: Saving the new release in .yarn/releases/yarn-2.4.2.cjs >➤ YN: Done in 1s 327ms >➤ YN: ┌ Resolution step >➤ YN0061: │ document-register-element@npm:1.14.3 is deprecated: V0 is gone and >the best V1 polyfill is now @ungap/custom-elements >➤ YN0061: │ axios@npm:0.20.0 is deprecated: Critical security vulnerability >fixed in v0.21.1. For more information, see >https://github.com/axios/axios/pull/3410 >➤ YN0061: │ urix@npm:0.1.0 is deprecated: Please see >https://github.com/lydell/urix#deprecated >➤ YN0061: │ smooshpack@npm:0.0.62 is deprecated: Package moved to >@codesandbox/sandpack-client >➤ YN0061: │ resolve-url@npm:0.2.1 is deprecated: >https://github.com/lydell/resolve-url#deprecated >➤ YN0061: │ uuid@npm:3.3.2 is deprecated: Please upgrade to version 7 or >higher. Older versions may use Math.random() in certain circumstances, which >is known to be problematic. See https://v8.dev/blog/math-random for details. >➤ YN0061: │ popper.js@npm:1.16.1 is deprecated: You can find the new Popper v2 >at @popperjs/core, this package is dedicated to the legacy v1 >➤ YN0061: │ querystring@npm:0.2.0 is deprecated: The querystring API is >considered Legacy. new code should use the URLSearchParams API instead. >➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are >discouraged >➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are >discouraged >➤ YN0032: │ evp_bytestokey@npm:1.0.3: Implicit dependencies on node-gyp are >discouraged >➤ YN0002: │ apollo-link-batch@npm:1.1.15 doesn't provide graphql (pf2c3f), >requested by apollo-link >➤ YN0002: │ bootstrap-vue@npm:2.17.3 doesn't provide jquery (p8724c), >requested by bootstrap >➤ YN0002: │ bootstrap-vue@npm:2.17.3 doesn't provide vue (p74d19), requested >by portal-vue >➤ YN0060: │ root-workspace-0b6124@workspace:. provides @babel/core (p8d5b6) >with version 0.0.0, which doesn't satisfy what babel-loader requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides popper.js (pb3b3d) with >version 0.0.0, which doesn't satisfy what bootstrap requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (p02edf) with >version 0.0.0, which doesn't satisfy what portal-vue requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (pa125f) with >version 0.0.0, which doesn't satisfy what tiptap requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (p6c5ff) with >version 0.0.0, which doesn't satisfy what @gitlab/ui requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (p4a08d) with >version 0.0.0, which doesn't satisfy what @tiptap/vue-2 requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (pc6a59) with >version 0.0.0, which doesn't satisfy what @toast-ui/vue-editor requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (p082e1) with >version 0.0.0, which doesn't satisfy what tiptap-extensions requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (paa947) with >version 0.0.0, which doesn't satisfy what vue-resize requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue (p1dfac) with >version 0.0.0, which doesn't satisfy what vuex requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue-template-compiler >(pb49ea) with version 0.0.0, which doesn't satisfy what tiptap requests >➤ YN0060: │ root-workspace-0b6124@workspace:. provides vue-template-compiler >(p659ff) with version 0.0.0, which doesn't satisfy what tiptap-extensions >requests >➤ YN: │ Some peer dependencies are incorrectly met; run yarn explain >peer-requirements for details, where is the
Bug#995202: horst FTBFS: error: format not a string literal and no format arguments
Source: horst
Version: 5.1-2
Severity: serious
Tags: ftbfs
horst fails to build from source in unstable on amd64 due to ncurses
having become stricter about format strings. A build now ends as
follows:
| cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -std=gnu99 -Wall -Wextra -g -I.
-DVERSION=\"5.1\" -DDO_DEBUG -I/usr/include/libnl3 -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o display-main.o display-main.c
| display-main.c: In function ‘print_dump_win’:
| display-main.c:56:2: error: format not a string literal and no format
arguments [-Werror=format-security]
|56 | wprintw(dump_win, str);
| | ^~~
| display-main.c: In function ‘print_node_list_line’:
| display-main.c:255:40: warning: format ‘%d’ expects argument of type ‘int’,
but argument 5 has type ‘long unsigned int’ [-Wformat=]
| 255 | mvwprintw(list_win, line, COL_SIG, "%3d",
-ewma_read(>phy_sig_avg));
| | ~~^ ~~~
| || |
| |int long unsigned int
| | %3ld
| display-main.c: In function ‘update_dump_win’:
| display-main.c:455:21: warning: too many arguments for format
[-Wformat-extra-args]
| 455 | wprintw(dump_win, "%-7s", "ARP", ip_sprintf(p->ip_src));
| | ^~
| display-main.c:481:31: warning: format ‘%llx’ expects argument of type ‘long
long unsigned int’, but argument 4 has type ‘uint64_t’ {aka ‘long unsigned
int’} [-Wformat=]
| 481 |wprintw(dump_win, "'%s' %llx", p->wlan_essid,
| |~~~^
| | |
| | long long unsigned int
| |%lx
| 482 | p->wlan_tsf);
| | ~~~
| | |
| | uint64_t {aka long unsigned int}
| display-main.c: In function ‘sort_input’:
| display-main.c:129:11: warning: this statement may fall through
[-Wimplicit-fallthrough=]
| 129 | do_sort = c;
| | ^~~
| display-main.c:131:2: note: here
| 131 | case '\r': case KEY_ENTER:
| | ^~~~
| cc1: some warnings being treated as errors
| make[1]: *** [: display-main.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:19: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#995199: r-bioc-ioniser: autopkgtest regression
Source: r-bioc-ioniser Version: 2.16.0+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org | ══ Failed tests | ── Error (test_Fast5Summary.R:5:1): (code run outside of `test_that()`) | Error: there is no package called ‘minionSummaryData’ | Backtrace: | █ | 1. └─utils::data(s.typhi.rep2, package = "minionSummaryData") test_Fast5Summary.R:5:0 | 2. └─base::find.package(package, lib.loc, verbose = verbose) | ── Error (test_plotting.R:5:1): (code run outside of `test_that()`) | Error: there is no package called ‘minionSummaryData’ | Backtrace: | █ | 1. └─utils::data(s.typhi.rep2, package = "minionSummaryData") test_plotting.R:5:0 | 2. └─base::find.package(package, lib.loc, verbose = verbose) | | [ FAIL 2 | WARN 2 | SKIP 0 | PASS 1 ] | Error: Test failures See https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-ioniser/15560558/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#995200: r-bioc-dropletutils: autopkgtest failures
Source: r-bioc-dropletutils Version: 1.12.2+ds-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org | ══ Failed tests | ── Error (test-read10x.R:129:5): read10xCounts works correctly for HDF5 counts, version < 3 ── | Error: BiocParallel errors | element index: 1 | first error: Error in h5checktype(). Argument not of class H5IdComponent. | Backtrace: | █ | 1. └─DropletUtils::read10xCounts(tmph5) test-read10x.R:129:4 | 2. ├─BiocParallel::bplapply(...) | 3. └─BiocParallel::bplapply(...) | ── Error (test-read10x.R:155:5): read10xCounts works correctly for HDF5 counts, version >= 3 ── | Error: BiocParallel errors | element index: 1 | first error: Error in h5checktype(). Argument not of class H5IdComponent. | Backtrace: | █ | 1. └─DropletUtils::read10xCounts(tmph5) test-read10x.R:155:4 | 2. ├─BiocParallel::bplapply(...) | 3. └─BiocParallel::bplapply(...) | | [ FAIL 2 | WARN 4 | SKIP 0 | PASS 970 ] See https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-dropletutils/15560540/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: severity of 995120 is important
Processing commands for cont...@bugs.debian.org: > severity 995120 important Bug #995120 [src:linux] linux-image-5.14.0-1-amd64: Raven Ridge cannot boot with secure memory encryption Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 995120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994451: golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm
User: release.debian@packages.debian.org Usertags: pu Tags: bullseye Severity: normal stop sorry for the abrupt ending of the previous mail. I'm attaching the debdiffs for the three uploads to this email. I'm happy to do the 3 uploads at any time. Please let me know what you think. On Mon, Sep 27, 2021 at 12:08 PM Reinhard Tartler wrote: > > On Thu, Sep 16, 2021 at 4:18 AM Bastien Roucariès < > roucaries.bast...@gmail.com> wrote: > >> Package: golang-github-containers-common >> Version: 0.33.4+ds1-1 >> Severity: critical >> Tags: upstream >> Forwarded: >> https://github.com/containers/common/commit/42d1db16bfc0dbaee5781d230dc2bcbaa0849c6e >> Control: fixed -1 0.42.1+ds1-1 >> >> Dear Maintainer, >> >> golang-github-containers-common in stable does not include recent syscall >> used >> by stable kernel/glibc breaking in my case simple container that do >> unattended- >> upgrade on arm >> particularly syscall=436 that is timer_settime64 >> >> I believe this should be fixed in a point release. >> > > I agree. I realized that these syscall changes also affect amd64. I was > able to reproduce the issue > by running a distribution that ships with glibc 2.34, such as ubuntu > impish. The testcase would be: > > $ podman run --rm -it ubuntu:impish sh -c 'apt update -qq && apt -y > full-upgrade && apt install -y libc6 jq' > > The symptom is described in more detail at > https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1943049 > > The problem here is that the issue is not simply dealt with updating the > secomp.json file, but also some code changes are required > that allow setting the default return value for some syscalls. This means > that in order to fix this issue in stable, 3 uploads are needed: > > - golang-github-opencontainers-specs > - golang-github-containers-common > - libpod > > I'm cloning this bug appropriately so that these uploads can be tracked > separately. > For now,I've backported and verified the changes. For your convenience, > I've uploaded the packages I got so far to > https://people.debian.org/~siretart/bug.994451/ > > >> BTW I strongly believe that seccomp.json is a config file and should be >> shipped in /etc and 988443 should also be shipped in stable. >> > > I could get convinced if the issue was fixable by just upading the > seccomp.json policy file. > Sadly, that's not the case. > > Stable Release team, I think this bug should be cloned with those > instructions: > > > -- > regards, > Reinhard > -- regards, Reinhard golang-github-opencontainers-specs.debdiff Description: Binary data golang-github-opencontainers-specs.debdiff Description: Binary data podman.debdiff Description: Binary data
Bug#995018: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#995018: fixed in jupyter-server 1.11.0-1)
Hi, On 27-09-2021 08:36, Debian Bug Tracking System wrote: > jupyter-server (1.11.0-1) unstable; urgency=medium > . >* Declare versioned dep on anyio (Closes: #995018). That was implemented via *build*-depends. It doesn't seem to have propagated to the Depends as the tests still fail. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: [bts-link] source package src:hcxtools
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:hcxtools > # 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 #994790 (http://bugs.debian.org/994790) > # Bug title: hcxtools: CVE-2021-32286 > # * https://github.com/ZerBea/hcxtools/issues/155 > # * remote status changed: (?) -> closed > # * closed upstream > tags 994790 + fixed-upstream Bug #994790 [src:hcxtools] hcxtools: CVE-2021-32286 Added tag(s) fixed-upstream. > usertags 994790 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 994790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package vdirsyncer
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package vdirsyncer > # 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 #994119 (http://bugs.debian.org/994119) > # Bug title: vdirsyncer: Random cannot import name 'metasync' with python3.9 > # * https://github.com/pimutils/vdirsyncer/issues/862 > # * remote status changed: (?) -> closed > # * closed upstream > tags 994119 + fixed-upstream Bug #994119 [vdirsyncer] vdirsyncer: Random cannot import name 'metasync' with python3.9 Added tag(s) fixed-upstream. > usertags 994119 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 994119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993478: marked as done (src:fricas: fails to migrate to testing for too long: maintainer built arch:all binaries)
Your message dated Mon, 27 Sep 2021 12:58:57 -0400 with message-id <87sfxq0xbi@transcendence.maguirefamily.org> and subject line Re: src:fricas: fails to migrate to testing for too long: maintainer built arch:all binaries has caused the Debian Bug report #993478, regarding src:fricas: fails to migrate to testing for too long: maintainer built arch:all binaries 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.) -- 993478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fricas Version: 1.3.6-6 Severity: serious Control: close -1 1.3.7-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As announced [1] last year, the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:fricas has been trying to migrate for 62 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 really 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=fricas OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1.3.6-6 Greetings, and thank you so much for your report! I have uploaded several identical versions of the package. The build only fails on one host, arm-conova-02, whether building armhf or armel, and when exercising orthogonal sections of linker code. The failure is unreproducible on Debian porterboxes. All other autobuilders in either architecture correctly build the package. The armel and armhf autobuilders have successfully built 1.3.7-3 at the moment so migration is imminent. I will follow up with debian admin and request access to the offending machine to investigate further, but this is a problem with the machine, not the package, as far as can be discerned at present. Take care, -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah--- End Message ---
Bug#994451: golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm
Le lun. 27 sept. 2021 à 16:08, Reinhard Tartler a écrit : > > > On Thu, Sep 16, 2021 at 4:18 AM Bastien Roucariès > wrote: >> >> Package: golang-github-containers-common >> Version: 0.33.4+ds1-1 >> Severity: critical >> Tags: upstream >> Forwarded: >> https://github.com/containers/common/commit/42d1db16bfc0dbaee5781d230dc2bcbaa0849c6e >> Control: fixed -1 0.42.1+ds1-1 >> >> Dear Maintainer, >> >> golang-github-containers-common in stable does not include recent syscall >> used >> by stable kernel/glibc breaking in my case simple container that do >> unattended- >> upgrade on arm >> particularly syscall=436 that is timer_settime64 >> >> I believe this should be fixed in a point release. > > > I agree. I realized that these syscall changes also affect amd64. I was able > to reproduce the issue > by running a distribution that ships with glibc 2.34, such as ubuntu impish. > The testcase would be: > > $ podman run --rm -it ubuntu:impish sh -c 'apt update -qq && apt -y > full-upgrade && apt install -y libc6 jq' > > The symptom is described in more detail at > https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1943049 > > The problem here is that the issue is not simply dealt with updating the > secomp.json file, but also some code changes are required > that allow setting the default return value for some syscalls. This means > that in order to fix this issue in stable, 3 uploads are needed: > > - golang-github-opencontainers-specs > - golang-github-containers-common > - libpod > > I'm cloning this bug appropriately so that these uploads can be tracked > separately. > For now,I've backported and verified the changes. For your convenience, I've > uploaded the packages I got so far to > https://people.debian.org/~siretart/bug.994451/ > >> >> BTW I strongly believe that seccomp.json is a config file and should be >> shipped in /etc and 988443 should also be shipped in stable. > > > I could get convinced if the issue was fixable by just upading the > seccomp.json policy file. > Sadly, that's not the case. It seems that recent version of this package allow to change at exec time the seccomp.json file. But for this version, you take the point it need rebuilt. Note that I have fixed this problem by manually using the unstable version on my stable. Bastien > Stable Release team, I think this bug should be cloned with those > instructions: > > > -- > regards, > Reinhard
Bug#994451: golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm
On Thu, Sep 16, 2021 at 4:18 AM Bastien Roucariès < roucaries.bast...@gmail.com> wrote: > Package: golang-github-containers-common > Version: 0.33.4+ds1-1 > Severity: critical > Tags: upstream > Forwarded: > https://github.com/containers/common/commit/42d1db16bfc0dbaee5781d230dc2bcbaa0849c6e > Control: fixed -1 0.42.1+ds1-1 > > Dear Maintainer, > > golang-github-containers-common in stable does not include recent syscall > used > by stable kernel/glibc breaking in my case simple container that do > unattended- > upgrade on arm > particularly syscall=436 that is timer_settime64 > > I believe this should be fixed in a point release. > I agree. I realized that these syscall changes also affect amd64. I was able to reproduce the issue by running a distribution that ships with glibc 2.34, such as ubuntu impish. The testcase would be: $ podman run --rm -it ubuntu:impish sh -c 'apt update -qq && apt -y full-upgrade && apt install -y libc6 jq' The symptom is described in more detail at https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1943049 The problem here is that the issue is not simply dealt with updating the secomp.json file, but also some code changes are required that allow setting the default return value for some syscalls. This means that in order to fix this issue in stable, 3 uploads are needed: - golang-github-opencontainers-specs - golang-github-containers-common - libpod I'm cloning this bug appropriately so that these uploads can be tracked separately. For now,I've backported and verified the changes. For your convenience, I've uploaded the packages I got so far to https://people.debian.org/~siretart/bug.994451/ > BTW I strongly believe that seccomp.json is a config file and should be > shipped in /etc and 988443 should also be shipped in stable. > I could get convinced if the issue was fixable by just upading the seccomp.json policy file. Sadly, that's not the case. Stable Release team, I think this bug should be cloned with those instructions: -- regards, Reinhard
Bug#995187: qtwebengine-opensource-src FTBFS on mips*: unistd_nr_{n32,n64,o32}.h no linger exported by the kernel
Source: qtwebengine-opensource-src Version: 5.15.5+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mips64el=5.15.6%2Bdfsg-1=1632387575=0 ... FAILED: obj/sandbox/linux/seccomp_bpf/syscall_set.o /usr/bin/g++ -MMD -MF obj/sandbox/linux/seccomp_bpf/syscall_set.o.d -DSANDBOX_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DOPENSSL_NO_ASM -Igen -I../../3rdparty/chromium -I../../3rdparty/chromium/third_party/perfetto/include -Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/abseil-cpp -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -pthread -D__SANE_USERSPACE_TYPES__ -mips64r2 -Wa,-mips64r2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned -Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -std=gnu++14 -Wno-narrowing -Wno-class-memaccess -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type -Wno-deprecated-copy -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c ../../3rdparty/chromium/sandbox/linux/bpf_dsl/syscall_set.cc -o obj/sandbox/linux/seccomp_bpf/syscall_set.o In file included from ../../3rdparty/chromium/sandbox/linux/bpf_dsl/syscall_set.cc:12: ../../3rdparty/chromium/sandbox/linux/bpf_dsl/linux_syscall_ranges.h:47:10: fatal error: asm/unistd_nr_n64.h: No such file or directory 47 | #include // for __NR_64_Linux and __NR_64_Linux_syscalls | ^ compilation terminated. ... Context: https://sources.debian.org/src/qtwebengine-opensource-src/5.15.6+dfsg-1/debian/patches/mipsel-linux-5.patch/ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccb21774863a
Bug#995185: flint-arb FTBFS on 32bit: gamma_fmpq test fails
Source: flint-arb Version: 1:2.21.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=flint-arb=1%3A2.21.0-1 (some 32bit ports architectures are building with nocheck) ... euler_number_fmpzPASS expPASS exp_arf_bbPASS exp_arf_rs_genericPASS exp_invexpPASS exp_sum_bs_powtabPASS exp_tabPASS exp_taylor_rsPASS expm1PASS fac_uiPASS floorPASS fmaPASS gammaPASS gamma_fmpqmake[3]: *** [../Makefile.subdirs:84: ../build/arb/test/t-gamma_fmpq_RUN] Aborted make[3]: *** Waiting for unfinished jobs
Processed: retitle 995175 to request-tracker4: CVE-2021-38562
Processing commands for cont...@bugs.debian.org: > retitle 995175 request-tracker4: CVE-2021-38562 Bug #995175 [src:request-tracker4] new upstream (5.0.2) [CVE-2021-38562] Changed Bug title to 'request-tracker4: CVE-2021-38562' from 'new upstream (5.0.2) [CVE-2021-38562]'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 995167, reassign -1 to src:request-tracker4, found -1 in 4.4.3-2
Processing commands for cont...@bugs.debian.org: > clone 995167 -1 Bug #995167 [request-tracker5] new upstream (5.0.2) [CVE-2021-38562] Bug 995167 cloned as bug 995175 > reassign -1 src:request-tracker4 4.4.4+dfsg-2 Bug #995175 [request-tracker5] new upstream (5.0.2) [CVE-2021-38562] Bug reassigned from package 'request-tracker5' to 'src:request-tracker4'. No longer marked as found in versions request-tracker5/5.0.1+dfsg-1. Ignoring request to alter fixed versions of bug #995175 to the same values previously set Bug #995175 [src:request-tracker4] new upstream (5.0.2) [CVE-2021-38562] Marked as found in versions request-tracker4/4.4.4+dfsg-2. > found -1 4.4.3-2 Bug #995175 [src:request-tracker4] new upstream (5.0.2) [CVE-2021-38562] Marked as found in versions request-tracker4/4.4.3-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 995167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995167 995175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995150: openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all
Source: openmpi Followup-For: Bug #995150 Installing libopenmpi3-dbgsym gives a little more detail in the backtrace (gdb) bt #0 0x in ?? () #1 0x7fffad13ea84 in MPIOI_File_iwrite_all (fh=, offset=offset@entry=0, file_ptr_type=file_ptr_type@entry=101, buf=, count=13, datatype=0x73d27700 , myname=0x7fffad17be80 "MPI_FILE_IWRITE_ALL", request=0x7fffad54ce90) at ../../../../../../../ompi/mca/io/romio321/romio/mpi-io/iwrite_all.c:124 #2 0x7fffad13ebd3 in mca_io_romio_dist_MPI_File_iwrite_all (fh=, buf=, count=, datatype=, request=) at ../../../../../../../ompi/mca/io/romio321/romio/mpi-io/iwrite_all.c:58
Bug#995150: openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all
Source: openmpi
Followup-For: Bug #995150
gdb on amd64 run locally confirms the segfault, running test_io.py
alone. Refines the problem to MPIOI_File_iwrite_all in
mca_io_romio321.so
$ gdb python3
(gdb) run -m pytest test_io.py
Starting program: /usr/bin/python3 -m pytest test_io.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x73f2b640 (LWP 3398120)]
...
Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x7fffad13ea84 in MPIOI_File_iwrite_all () from
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so
#2 0x7fffad13ebd3 in mca_io_romio_dist_MPI_File_iwrite_all () from
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so
#3 0x7fffad13c4c3 in mca_io_romio321_file_iwrite_all () from
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so
#4 0x73c86b4c in PMPI_File_iwrite_all () from
/lib/x86_64-linux-gnu/libmpi.so.40
#5 0x73e80d0c in __pyx_pf_6mpi4py_3MPI_4File_62Iwrite_all
(__pyx_v_buf=, __pyx_v_self=0x7fffacf8db40) at
src/mpi4py.MPI.c:159094
#6 __pyx_pw_6mpi4py_3MPI_4File_63Iwrite_all (__pyx_v_self=, __pyx_args=__pyx_args@entry=(,), __pyx_kwds=__pyx_kwds@entry=0x0)
at src/mpi4py.MPI.c:27957
#7 0x0052b141 in method_vectorcall_VARARGS_KEYWORDS (func=, args=0x1461818, nargsf=, kwnames=0x0) at
../Objects/descrobject.c:346
#8 0x005127fb in _PyObject_VectorcallTstate (kwnames=0x0,
nargsf=, args=0x1461818, callable=, tstate=0x968fb0)
at ../Include/cpython/abstract.h:118
#9 PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x1461818,
callable=) at
../Include/cpython/abstract.h:127
#10 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x968fb0) at ../Python/ceval.c:5075
#11 _PyEval_EvalFrameDefault (tstate=, f=,
throwflag=) at ../Python/ceval.c:3504
#12 0x005291c3 in _PyEval_EvalFrame (throwflag=0,
f=Frame 0x1461640, for file /projects/python/build/mpi4py/test/test_io.py,
line 306, in testIReadIWriteAll
(self=,
parent=,
parent=,
parent=, parent=None,
_markers={'mpi4py': True}) at remote 0x7fffb69c0850>, own_markers=[],
extra_keyword_matches=set(), testsfailed=1, testscollected=28,
shouldstop=False, shouldfail=False,
trace=, tags=('collection',)) at remote 0x7fffb69c0910>,
startdir=,
_initialpaths=frozenset({}), _bestrelpathcache=<_best...(truncated),
tstate=0x968fb0) at ../Include/internal/pycore_ceval.h:40
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#995167: new upstream (5.0.2) [CVE-2021-38562]
Package: request-tracker5 Version: 5.0.1+dfsg-1 Severity: serious Tags: security Hi, upstream has fixed the following issue in 5.0.2: "In previous versions, RT's native login system is vulnerable to user enumeration through a timing side-channel attack. This means an external entity could try to find valid usernames by attempting logins and comparing the time to evaluate each login attempt for valid and invalid usernames. This vulnerability does not allow any access to the RT system. This vulnerability is assigned CVE-2021-38562 and is fixed in this release." It would be nice if you could upgrade (or cherry-pick) that fix, please also mention 'CVE-2021-38562' in the changelog when doing so. Regards, Daniel
Processed: Re: Bug#992693: bullseye-pu: package glibc/2.31-13+deb11u1
Processing control commands: > tags -1 + confirmed d-i Bug #992693 [release.debian.org] bullseye-pu: package glibc/2.31-13+deb11u1 Added tag(s) confirmed. > fixed 994042 2.32-3 Bug #994042 [libc6] libc6: debconf text fallback failed to accept input, had to be killed leading to broken dist-upgrade Marked as fixed in versions glibc/2.32-3. -- 992693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992693 994042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994457: r-cran-gnm autopkgtest needs to be adapted for lapack 3.10
Hi Heather, thanks a lot for your quick response. We do not have any deadline since Debian 11 was "just" released. Kind regards Andreas. On Mon, Sep 27, 2021 at 12:01:20PM +0100, Heather Turner wrote: > Hi Andreas, > > Thanks for forwarding this bug report and thanks to Sébastien for the > detailed and accurate analysis. I will need to submit an update to CRAN, > which should be feasible in the next week or two. Is there a deadline that I > need to work to? > > Best wishes, > > Heather > > On Mon, Sep 27, 2021, at 10:12 AM, Andreas Tille wrote: > > Control: tags -1 upstream > > Control: forwarded -1 Heather Turner > > > > Hi Heather, > > > > the Debian packaged gnm recieved a bug report about a failing test in > > connection with the upgrade to lapack 3.10.0 on the machine running the > > test. Please read the bug report below. > > > > We admit we need your help to solve this issue that might affect > > other systems as well. > > > > Kind regards > > > > Andreas. > > > > On Thu, Sep 16, 2021 at 10:59:19AM +0200, Sébastien Villemot wrote: > >> Package: r-cran-gnm > >> Version: 1.1-1-2 > >> Severity: serious > >> Tags: sid bookworm > >> X-Debbugs-CC: debian...@lists.debian.org > >> User: debian...@lists.debian.org > >> Usertags: needs-update > >> > >> Dear Maintainer, > >> > >> Since the upload of lapack 3.10.0-1, the autopkgtest of r-cran-gnm > >> fails in unstable. See for example: > >> https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-gnm/15155026/log.gz > >> > >> More precisely, test-biplot.R fails, because some results have the > >> opposite sign compared to the one which is expected. > >> > >> My understanding is that this comes from the SVD of barleyMatrix in > >> that test file, which is different between lapack 3.9 and 3.10. > >> Mathematically, the SVD is not unique, and lapack 3.10 returns a > >> different (still valid) solution. More precisely, I verified that one > >> of the right-singular vector of that matrix has the opposite sign in > >> lapack 3.10. I also verified that the decomposition is correct by > >> checking that: > >> > >> max(abs(barleySVD$u %*% diag(barleySVD$d) %*% t(barleySVD$v) - > >> barleyMatrix)) > >> > >> is a small value (about 2e-14). > >> > >> Also note that the hardcoded expected values already partially differ > >> from those of the original research paper mentioned in that test > >> (Gabriel (1998): Generalised bilinear regression). More precisely, half > >> of the values were hardcoded with the opposite sign. It seems that now > >> all values need to be hardcoded with the opposite sign. > >> > >> The testsuite of r-cran-gnm thus needs to be adapted, by being more > >> tolerant to such sign changes. > >> > >> N.B. : when trying to reproduce the problem, please ensure that your > >> lapack alternative (as given by “update-alternatives --display > >> liblapack.so.3-x86_64-linux-gnu) points to /usr/lib/x86_64-linux- > >> gnu/lapack/liblapack.so.3, and not to the binary provided by either > >> openblas or atlas (because these two have not yet been recompiled > >> against lapack 3.10, and thus do not expose the problem). > >> > >> Best regards, > >> > >> -- > >> ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot > >> ⣾⠁⢠⠒⠀⣿⡁ Debian Developer > >> ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name > >> ⠈⠳⣄ https://www.debian.org > >> > > > > > > > >> ___ > >> R-pkg-team mailing list > >> r-pkg-t...@alioth-lists.debian.net > >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team > > > > > > -- > > http://fam-tille.de > -- http://fam-tille.de
Bug#995165: key-mapper: file conflict with unrelated package 'keymapper': /usr/lib/python3/dist-packages/keymapper/__init__.py
Package: key-mapper Version: 1.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package key-mapper. Preparing to unpack .../92-key-mapper_1.0.0-2_all.deb ... Unpacking key-mapper (1.0.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2ISUCX/92-key-mapper_1.0.0-2_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/keymapper/__init__.py', which is also in package keymapper 0.6.2 Errors were encountered while processing: /tmp/apt-dpkg-install-2ISUCX/92-key-mapper_1.0.0-2_all.deb /usr/lib/python3/dist-packages/keymapper/__init__.py is the only file name used by both packages. The 'keymapper' package has been in the archive since 2004 (and also has the better match on the conflicting file name), so 'key-mapper' should probably rename its (internal?) python module. Note: Conflicts/Breaks/Replaces are *NOT* a valid solution in this case where unrelated packages are involved. cheers, Andreas keymapper=0.6.2_key-mapper=1.0.0-2.log.gz Description: application/gzip
Bug#995164: golang-github-skip2-go-qrcode-dev: missing Breaks+Replaces: go-qrcode (<< 0.0~git20200617.da1b656)
Package: golang-github-skip2-go-qrcode-dev Version: 0.0~git20200617.da1b656-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../golang-github-skip2-go-qrcode-dev_0.0~git20200617.da1b656-2_all.deb ... Unpacking golang-github-skip2-go-qrcode-dev (0.0~git20200617.da1b656-2) ... dpkg: error processing archive /var/cache/apt/archives/golang-github-skip2-go-qrcode-dev_0.0~git20200617.da1b656-2_all.deb (--unpack): trying to overwrite '/usr/share/gocode/src/github.com/skip2/go-qrcode/bitset/bitset.go', which is also in package go-qrcode 0.0~git20190110.dc11ecd-2+b6 Errors were encountered while processing: /var/cache/apt/archives/golang-github-skip2-go-qrcode-dev_0.0~git20200617.da1b656-2_all.deb cheers, Andreas go-qrcode=0.0~git20190110.dc11ecd-2+b6_golang-github-skip2-go-qrcode-dev=0.0~git20200617.da1b656-2.log.gz Description: application/gzip
Bug#995163: golang-github-jessevdk-go-flags-dev: missing Breaks+Replaces: golang-go-flags-dev (<< 1.4.0-3~)
Package: golang-github-jessevdk-go-flags-dev Version: 1.4.0-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../golang-github-jessevdk-go-flags-dev_1.4.0-4_all.deb ... Unpacking golang-github-jessevdk-go-flags-dev (1.4.0-4) ... dpkg: error processing archive /var/cache/apt/archives/golang-github-jessevdk-go-flags-dev_1.4.0-4_all.deb (--unpack): trying to overwrite '/usr/share/gocode/src/github.com/jessevdk/go-flags/arg.go', which is also in package golang-go-flags-dev 1.4.0-2 Errors were encountered while processing: /var/cache/apt/archives/golang-github-jessevdk-go-flags-dev_1.4.0-4_all.deb The exising Breaks+Replaces are insufficiently versioned: (<< 1.4.0-2~) they don't cover the last version (1.4.0-2) before the package rename. cheers, Andreas golang-go-flags-dev=1.4.0-2_golang-github-jessevdk-go-flags-dev=1.4.0-4.log.gz Description: application/gzip
Bug#994457: r-cran-gnm autopkgtest needs to be adapted for lapack 3.10
Hi Andreas, Thanks for forwarding this bug report and thanks to Sébastien for the detailed and accurate analysis. I will need to submit an update to CRAN, which should be feasible in the next week or two. Is there a deadline that I need to work to? Best wishes, Heather On Mon, Sep 27, 2021, at 10:12 AM, Andreas Tille wrote: > Control: tags -1 upstream > Control: forwarded -1 Heather Turner > > Hi Heather, > > the Debian packaged gnm recieved a bug report about a failing test in > connection with the upgrade to lapack 3.10.0 on the machine running the > test. Please read the bug report below. > > We admit we need your help to solve this issue that might affect > other systems as well. > > Kind regards > > Andreas. > > On Thu, Sep 16, 2021 at 10:59:19AM +0200, Sébastien Villemot wrote: >> Package: r-cran-gnm >> Version: 1.1-1-2 >> Severity: serious >> Tags: sid bookworm >> X-Debbugs-CC: debian...@lists.debian.org >> User: debian...@lists.debian.org >> Usertags: needs-update >> >> Dear Maintainer, >> >> Since the upload of lapack 3.10.0-1, the autopkgtest of r-cran-gnm >> fails in unstable. See for example: >> https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-gnm/15155026/log.gz >> >> More precisely, test-biplot.R fails, because some results have the >> opposite sign compared to the one which is expected. >> >> My understanding is that this comes from the SVD of barleyMatrix in >> that test file, which is different between lapack 3.9 and 3.10. >> Mathematically, the SVD is not unique, and lapack 3.10 returns a >> different (still valid) solution. More precisely, I verified that one >> of the right-singular vector of that matrix has the opposite sign in >> lapack 3.10. I also verified that the decomposition is correct by >> checking that: >> >> max(abs(barleySVD$u %*% diag(barleySVD$d) %*% t(barleySVD$v) - >> barleyMatrix)) >> >> is a small value (about 2e-14). >> >> Also note that the hardcoded expected values already partially differ >> from those of the original research paper mentioned in that test >> (Gabriel (1998): Generalised bilinear regression). More precisely, half >> of the values were hardcoded with the opposite sign. It seems that now >> all values need to be hardcoded with the opposite sign. >> >> The testsuite of r-cran-gnm thus needs to be adapted, by being more >> tolerant to such sign changes. >> >> N.B. : when trying to reproduce the problem, please ensure that your >> lapack alternative (as given by “update-alternatives --display >> liblapack.so.3-x86_64-linux-gnu) points to /usr/lib/x86_64-linux- >> gnu/lapack/liblapack.so.3, and not to the binary provided by either >> openblas or atlas (because these two have not yet been recompiled >> against lapack 3.10, and thus do not expose the problem). >> >> Best regards, >> >> -- >> ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot >> ⣾⠁⢠⠒⠀⣿⡁ Debian Developer >> ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name >> ⠈⠳⣄ https://www.debian.org >> > > > >> ___ >> R-pkg-team mailing list >> r-pkg-t...@alioth-lists.debian.net >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team > > > -- > http://fam-tille.de
Bug#994786: marked as done (spectral-cube: autopkgtest needs update for new version of radio-beam: warning message changed)
Your message dated Mon, 27 Sep 2021 09:53:05 +
with message-id
and subject line Bug#994786: fixed in spectral-cube 0.5.0-4
has caused the Debian Bug report #994786,
regarding spectral-cube: autopkgtest needs update for new version of
radio-beam: warning message changed
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.)
--
994786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spectral-cube
Version: 0.5.0-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, radio-b...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:radio-beam
Dear maintainer(s),
With a recent upload of radio-beam the autopkgtest of spectral-cube
fails in testing when that autopkgtest is run with the binary packages
of radio-beam from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
radio-beam from testing0.3.3-1
spectral-cube from testing0.5.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report. It seems to me
that there was an *addition* warning raised and thus the check fails.
Currently this regression is blocking the migration of radio-beam to
testing [1]. Of course, radio-beam shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
radio-beam 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 radio-beam 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
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
radio-beam/0.3.3-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=radio-beam
https://ci.debian.net/data/autopkgtest/testing/amd64/s/spectral-cube/15365768/log.gz
=== FAILURES
===
___ test_parallel_bad_params
___
data_adv =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_parallel_bad_params0/adv.fits')
@pytest.mark.skipif('not scipyOK')
def test_parallel_bad_params(data_adv):
# This function only makes sense for the plain SpectralCube class
cube, data = cube_and_raw(data_adv, use_dask=False)
with pytest.raises(ValueError,
match=("parallel execution was not requested,
but "
"multiple cores were: these are
incompatible "
"options. Either specify num_cores=1 or "
"parallel=True")):
cube.spectral_smooth_median(3, num_cores=2, parallel=False,
update_function=update_function)
with warnings.catch_warnings(record=True) as wrn:
cube.spectral_smooth_median(3, num_cores=1, parallel=True,
update_function=update_function)
> assert ("parallel=True was specified but num_cores=1. "
"Joblib will be used to run the task with a "
"single thread.") in str(wrn[-1].message)
E assert 'parallel=True was specified but num_cores=1. Joblib will
be used to run the task with a single thread.' in "'datfix' made the
change 'Set MJD-OBS to 50982.687794 from DATE-OBS'."
E+ where "'datfix' made the change 'Set MJD-OBS to 50982.687794
from DATE-OBS'." = str(FITSFixedWarning("'datfix' made the change 'Set
MJD-OBS to 50982.687794 from DATE-OBS'."))
E+where FITSFixedWarning("'datfix' made the change 'Set
MJD-OBS to 50982.687794 from DATE-OBS'.") = .message
/usr/lib/python3/dist-packages/spectral_cube/tests/test_spectral_cube.py:2279:
AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source:
Bug#995132: marked as done (libhtml-treebuilder-libxml-perl: autopkgtest regression between 5 September 2021 and 25 September 2021)
Your message dated Mon, 27 Sep 2021 09:49:15 + with message-id and subject line Bug#995132: fixed in libhtml-treebuilder-libxml-perl 0.26-2 has caused the Debian Bug report #995132, regarding libhtml-treebuilder-libxml-perl: autopkgtest regression between 5 September 2021 and 25 September 2021 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.) -- 995132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libhtml-treebuilder-libxml-perl Version: 0.26-1 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org Dear maintainer(s), Your package has an autopkgtest, great! However, somewhere between last month and today it started to fail [1]. Unfortunately our migration setup didn't catch this because it's either caused by something external to the archive, or the package that caused it is in not a direct (build) dependency of your packages. Can you fix the situation? Paul [1] https://ci.debian.net/packages/libh/libhtml-treebuilder-libxml-perl/ https://ci.debian.net/data/autopkgtest/testing/amd64/libh/libhtml-treebuilder-libxml-perl/15530611/log.gz not ok 7 - 2 atts on same element # TODO I don't know, this order is required for xpath spec, or not?? # Failed (TODO) test '2 atts on same element' # at t/HTML-TreeBuilder-XPath.t line 39. # got: 'foomyspan' # expected: 'myspanfoo' not ok 8 - 2 atts on same element # TODO I don't know, this order is required for xpath spec, or not?? # Failed (TODO) test '2 atts on same element' # at t/HTML-TreeBuilder-XPath.t line 40. # got: 'foomyspan' # expected: 'myspanfoo' not ok 9 - 2 atts on same element (unsorted) # TODO I don't know, this order is required for xpath spec, or not?? # Failed (TODO) test '2 atts on same element (unsorted)' # at t/HTML-TreeBuilder-XPath.t line 41. # got: 'foomyspan' # expected: 'myspanfoo' OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libhtml-treebuilder-libxml-perl Source-Version: 0.26-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libhtml-treebuilder-libxml-perl, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libhtml-treebuilder-libxml-perl 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: Mon, 27 Sep 2021 11:25:29 +0200 Source: libhtml-treebuilder-libxml-perl Architecture: source Version: 0.26-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 995132 Changes: libhtml-treebuilder-libxml-perl (0.26-2) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Bump debhelper dependency to >= 9, since that's what is used in debian/compat. * Bump debhelper from old 9 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.4.1, no changes needed. * Update standards version to 4.5.0, no changes needed. . [ gregor herrmann ] * Add patch from upstream merge request: compatibility with newer libxml2. Thanks to Paul Gevers for the bug report. (Closes: #995132) * Use debhelper-compat 13. * Declare compliance with Debian Policy 4.6.0. Checksums-Sha1: 92868efdd30b6073f6536a25a0a20bab7b3ac3b4 2668 libhtml-treebuilder-libxml-perl_0.26-2.dsc 54c09eb6518eda066578a1dac1032ca3d8378b4c 4992 libhtml-treebuilder-libxml-perl_0.26-2.debian.tar.xz Checksums-Sha256: 30ef20f3757acb7354f54090eb16f189d7ad5b290cbe3fe60f01afa83cd19fb4 2668 libhtml-treebuilder-libxml-perl_0.26-2.dsc d496be6334e50ee29ca7e6a774bd4596394e71a51ef663a7491b1ab8df9908db 4992 libhtml-treebuilder-libxml-perl_0.26-2.debian.tar.xz Files: 09444d6f662d92b81bb3f369f0c8890f 2668 perl optional libhtml-treebuilder-libxml-perl_0.26-2.dsc
Bug#995132: marked as pending in libhtml-treebuilder-libxml-perl
Control: tag -1 pending Hello, Bug #995132 in libhtml-treebuilder-libxml-perl 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/perl-team/modules/packages/libhtml-treebuilder-libxml-perl/-/commit/344bdf6ae1fcafa5934b73090fa8d879eeff961e Add patch from upstream merge request: compatibility with newer libxml2. Thanks: Paul Gevers for the bug report. Closes: #995132 (this message was generated automatically) -- Greetings https://bugs.debian.org/995132
Processed: Bug#995132 marked as pending in libhtml-treebuilder-libxml-perl
Processing control commands: > tag -1 pending Bug #995132 [src:libhtml-treebuilder-libxml-perl] libhtml-treebuilder-libxml-perl: autopkgtest regression between 5 September 2021 and 25 September 2021 Added tag(s) pending. -- 995132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 995132
Processing commands for cont...@bugs.debian.org: > tags 995132 + sid bookworm ftbfs Bug #995132 [src:libhtml-treebuilder-libxml-perl] libhtml-treebuilder-libxml-perl: autopkgtest regression between 5 September 2021 and 25 September 2021 Added tag(s) ftbfs, bookworm, and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 995132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981902: marked as done (facterdb: autopkgtest failure)
Your message dated Mon, 27 Sep 2021 09:18:53 + with message-id and subject line Bug#981902: fixed in facterdb 1.8.0-1 has caused the Debian Bug report #981902, regarding facterdb: autopkgtest failure 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.) -- 981902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: facterdb Version: 1.6.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/f/facterdb/10218718/log.gz ... Failures: 1) FacterDB.facterdb_fact_files returns the deduplicated combination of .default_fact_files and .external_fact_files Failure/Error: expect(facterdb_fact_files.count).to eq(described_class.default_fact_files.count) expected: 1577 got: 1702 (compared using ==) # ./spec/facterdb_spec.rb:153:in `block (3 levels) in ' 2) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.2/archlinux-x86_64.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 3) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.2/aix-53-powerpc.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 4) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.2/aix-61-powerpc.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 5) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.2/aix-71-powerpc.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 6) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/1.7/archlinux-x86_64.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 7) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.1/archlinux-x86_64.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 8) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.3/archlinux-x86_64.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 9) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.0/ubuntu-15.10-x86_64.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 10) Default Facts ../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.0/ubuntu-15.10-i386.facts contains an ipaddress fact Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty expected: not nil got: nil ...and: expected nil to respond to `empty?` # ./spec/facts_spec.rb:105:in `block (4 levels) in ' 11) Default Facts
Processed: bug 995132 is forwarded to https://github.com/tokuhirom/HTML-TreeBuilder-LibXML/issues/16
Processing commands for cont...@bugs.debian.org: > forwarded 995132 > https://github.com/tokuhirom/HTML-TreeBuilder-LibXML/issues/16 Bug #995132 [src:libhtml-treebuilder-libxml-perl] libhtml-treebuilder-libxml-perl: autopkgtest regression between 5 September 2021 and 25 September 2021 Set Bug forwarded-to-address to 'https://github.com/tokuhirom/HTML-TreeBuilder-LibXML/issues/16'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#994457: r-cran-gnm autopkgtest needs to be adapted for lapack 3.10
Processing control commands: > tags -1 upstream Bug #994457 [r-cran-gnm] r-cran-gnm autopkgtest needs to be adapted for lapack 3.10 Added tag(s) upstream. > forwarded -1 Heather Turner Bug #994457 [r-cran-gnm] r-cran-gnm autopkgtest needs to be adapted for lapack 3.10 Set Bug forwarded-to-address to 'Heather Turner '. -- 994457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994457: r-cran-gnm autopkgtest needs to be adapted for lapack 3.10
Control: tags -1 upstream Control: forwarded -1 Heather Turner Hi Heather, the Debian packaged gnm recieved a bug report about a failing test in connection with the upgrade to lapack 3.10.0 on the machine running the test. Please read the bug report below. We admit we need your help to solve this issue that might affect other systems as well. Kind regards Andreas. On Thu, Sep 16, 2021 at 10:59:19AM +0200, Sébastien Villemot wrote: > Package: r-cran-gnm > Version: 1.1-1-2 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: needs-update > > Dear Maintainer, > > Since the upload of lapack 3.10.0-1, the autopkgtest of r-cran-gnm > fails in unstable. See for example: > https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-gnm/15155026/log.gz > > More precisely, test-biplot.R fails, because some results have the > opposite sign compared to the one which is expected. > > My understanding is that this comes from the SVD of barleyMatrix in > that test file, which is different between lapack 3.9 and 3.10. > Mathematically, the SVD is not unique, and lapack 3.10 returns a > different (still valid) solution. More precisely, I verified that one > of the right-singular vector of that matrix has the opposite sign in > lapack 3.10. I also verified that the decomposition is correct by > checking that: > > max(abs(barleySVD$u %*% diag(barleySVD$d) %*% t(barleySVD$v) - > barleyMatrix)) > > is a small value (about 2e-14). > > Also note that the hardcoded expected values already partially differ > from those of the original research paper mentioned in that test > (Gabriel (1998): Generalised bilinear regression). More precisely, half > of the values were hardcoded with the opposite sign. It seems that now > all values need to be hardcoded with the opposite sign. > > The testsuite of r-cran-gnm thus needs to be adapted, by being more > tolerant to such sign changes. > > N.B. : when trying to reproduce the problem, please ensure that your > lapack alternative (as given by “update-alternatives --display > liblapack.so.3-x86_64-linux-gnu) points to /usr/lib/x86_64-linux- > gnu/lapack/liblapack.so.3, and not to the binary provided by either > openblas or atlas (because these two have not yet been recompiled > against lapack 3.10, and thus do not expose the problem). > > Best regards, > > -- > ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot > ⣾⠁⢠⠒⠀⣿⡁ Debian Developer > ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name > ⠈⠳⣄ https://www.debian.org > > ___ > R-pkg-team mailing list > r-pkg-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team -- http://fam-tille.de
Bug#993198: gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40
On Fri, Sep 24, 2021 at 10:07 PM Samuel Henrique wrote: > Leo, from my side you're free to push your changes whenever you want. I will as soon as someone gives me access to the repo ;) Just requested access to the Gnome group, but that may take a while. > Let's try to coordinate things, feel free to perform changes to the > packaging, I will wait until I get your ack to go ahead (if there's > any work left to be done). I'm not a gnome-extension expert, so I'll push my changes so that the package is at least gpb-buildable, and you can then maybe check that the build makes sense and upload it yourself if you want. Cheers Leo
Bug#995150: openmpi: segfault in mca_io_romio_dist_MPI_File_iwrite_all
Source: openmpi Version: 4.1.2~rc1-2 Severity: serious Justification: FTBFS The new version of openmpi seems to be segfaulting in mca_io_romio321.so The segfault is found in nearly all arches in mpi4py tests, https://buildd.debian.org/status/package.php?p=mpi4py (it causes mpi4py to FTBFS) The crash is bad enough that most arches are not able to provide a backtrace, although some arches reference libpthread.so.0 (which could suggest instability from the libc6 2.32 transition) ppc64el and ia64 however provide a full backtrace, both pointing at mca_io_romio321.so (MPIOI_File_iwrite_all) >From ppc64el https://buildd.debian.org/status/fetch.php?pkg=mpi4py=ppc64el=3.1.1-8=1632692000=0 testIReadIWrite (test_io.TestIOSelf) ... ok testIReadIWriteAll (test_io.TestIOSelf) ... [ppc64el-osuosl-01:1381766] *** Process received signal *** [ppc64el-osuosl-01:1381766] Signal: Segmentation fault (11) [ppc64el-osuosl-01:1381766] Signal code: Address not mapped (1) [ppc64el-osuosl-01:1381766] Failing at address: (nil) [ppc64el-osuosl-01:1381766] [ 0] linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x7fff92ec0514] [ppc64el-osuosl-01:1381766] [ 1] [0x0] [ppc64el-osuosl-01:1381766] [ 2] /usr/lib/powerpc64le-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so(mca_io_romio_dist_MPI_File_iwrite_all+0x38)[0x7fff831135e8] [ppc64el-osuosl-01:1381766] [ 3] /usr/lib/powerpc64le-linux-gnu/openmpi/lib/openmpi3/mca_io_romio321.so(mca_io_romio321_file_iwrite_all+0xa8)[0x7fff831100f8] [ppc64el-osuosl-01:1381766] [ 4] /usr/lib/powerpc64le-linux-gnu/libmpi.so.40(PMPI_File_iwrite_all+0x100)[0x7fff9221e890] [ppc64el-osuosl-01:1381766] [ 5] /<>/.pybuild/cpython3_3.9/build/mpi4py/MPI.cpython-39-powerpc64le-linux-gnu.so(+0x12b654)[0x7fff9245b654] [ppc64el-osuosl-01:1381766] [ 6] /usr/bin/python3.9[0x100f9e84] [ppc64el-osuosl-01:1381766] [ 7] /usr/bin/python3.9(_PyEval_EvalFrameDefault+0xa9c)[0x100d2a6c] [ppc64el-osuosl-01:1381766] [ 8] /usr/bin/python3.9(_PyFunction_Vectorcall+0x20c)[0x100f631c]
Bug#993441: marked as done (kleopatra: Creates unsafe ~/.gnupg when not already present)
Your message dated Mon, 27 Sep 2021 07:03:31 + with message-id and subject line Bug#993441: fixed in kleopatra 4:21.08.1-2 has caused the Debian Bug report #993441, regarding kleopatra: Creates unsafe ~/.gnupg when not already present 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.) -- 993441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kleopatra Version: 4:21.08.0-1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team I had previously 'improved' my gnupg configuration, but that is (now) deprecated. So I moved my ~/.gnupg directory to a backup location to start anew. If I then start Kleopatra, but don't do anything with it, that directory gets created, but with the wrong permissions: diederik@bagend:~$ stat .gnupg/ File: .gnupg/ Size: 4096Blocks: 8 IO Block: 4096 directory Device: 10304h/66308d Inode: 12845182Links: 3 Access: (0755/drwxr-xr-x) Uid: ( 1000/diederik) Gid: ( 1000/diederik) Running a gpg command from a Konsole window reports the issue: diederik@bagend:~$ gpg --list-keys gpg: WARNING: unsafe permissions on homedir '/home/diederik/.gnupg' If I uninstall Kleopatra and remove the ~/.gnupg directory (again) and then do 'gpg --list-keys', I get: diederik@bagend:~$ gpg --list-keys gpg: directory '/home/diederik/.gnupg' created gpg: keybox '/home/diederik/.gnupg/pubring.kbx' created gpg: /home/diederik/.gnupg/trustdb.gpg: trustdb created diederik@bagend:~$ stat .gnupg/ File: .gnupg/ Size: 4096Blocks: 8 IO Block: 4096 directory Device: 10304h/66308d Inode: 12845180Links: 2 Access: (0700/drwx--) Uid: ( 1000/diederik) Gid: ( 1000/diederik) So Kleopatra creates ~/.gnupg with incorrect permissions when the directory doesn't exist. Cheers, Diederik -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kleopatra depends on: ii dirmngr2.2.27-2 ii gnupg 2.2.27-2 ii gpgsm 2.2.27-2 ii libassuan0 2.5.5-1 ii libc6 2.31-17 ii libgcc-s1 11.2.0-3 ii libgpg-error0 1.42-3 ii libgpgme11 1.16.0-1 ii libgpgmepp61.16.0-1 ii libkf5codecs5 5.85.0-2 ii libkf5configcore5 5.85.0-2 ii libkf5configgui5 5.85.0-2 ii libkf5configwidgets5 5.85.0-2 ii libkf5coreaddons5 5.85.0-2 ii libkf5crash5 5.85.0-2 ii libkf5dbusaddons5 5.85.0-2 ii libkf5i18n55.85.0-2 ii libkf5iconthemes5 5.85.0-2 ii libkf5itemmodels5 5.85.0-2 ii libkf5libkleo5 [libkf5libkleo5-21.08] 4:21.08.0-1 ii libkf5mime5abi1 [libkf5mime5-21.08]21.08.0-1 ii libkf5notifications5 5.85.0-3 ii libkf5textwidgets5 5.85.0-2 ii libkf5widgetsaddons5 5.85.0-2 ii libkf5windowsystem55.85.0-2 ii libkf5xmlgui5 5.85.0-3 ii libqgpgme7 1.16.0-1 ii libqt5core5a 5.15.2+dfsg-10 ii libqt5dbus55.15.2+dfsg-10 ii libqt5gui5 5.15.2+dfsg-10 ii libqt5network5 5.15.2+dfsg-10 ii libqt5printsupport55.15.2+dfsg-10 ii libqt5widgets5 5.15.2+dfsg-10 ii libstdc++6 11.2.0-3 ii paperkey 1.6-1 ii pinentry-qt1.1.1-1 kleopatra recommends no packages. kleopatra suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: kleopatra Source-Version: 4:21.08.1-2 Done: Norbert Preining We believe
Bug#995134: marked as done (dkms modules fail to build on 5.14.0, error: ‘TIF_IA32’ undeclared)
Your message dated Mon, 27 Sep 2021 06:33:58 + with message-id and subject line Bug#995134: fixed in openafs 1.8.8-1 has caused the Debian Bug report #995134, regarding dkms modules fail to build on 5.14.0, error: ‘TIF_IA32’ undeclared 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.) -- 995134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openafs-modules-dkms Version: 1.8.6-5 Severity: grave Justification: Renders package unusable The openafs dkms modules fail to build on 5.14.0. I've attached /var/lib/dkms/openafs/1.8.6/build/make.log. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openafs-modules-dkms depends on: ii dkms 2.8.4-4 ii libc6-dev 2.32-4 ii perl 5.32.1-6 Versions of packages openafs-modules-dkms recommends: ii openafs-client 1.8.6-5 openafs-modules-dkms suggests no packages. -- no debconf information -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A DKMS make.log for openafs-1.8.6 for kernel 5.14.0-1-amd64 (x86_64) Sun 26 Sep 17:00:15 EDT 2021 checking for gcc... gcc-10 checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc-10 accepts -g... yes checking for gcc-10 option to accept ISO C89... none needed checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to run the C preprocessor... gcc-10 -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for a BSD-compatible install... /usr/bin/install -c checking for flex... no checking for lex... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for libxslt... no checking for saxon... no checking for xalan-j... no checking for xsltproc... xsltproc checking for fop... no checking for dblatex... no checking for docbook2pdf... no checking for kindlegen... no checking for doxygen... no checking for dot... dot checking for library containing strerror... none required checking for pid_t... yes checking for size_t... yes checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... no checking for byacc... no checking if lex is flex... yes checking whether byte order is known at compile time... yes checking whether byte ordering is bigendian... no checking whether printf understands the %z length modifier... yes checking your OS... linux checking for ranlib... (cached) ranlib checking for as... as checking for mv... mv checking for rm... rm checking for ld... ld checking for cp... cp checking for gencat... gencat checking if gcc-10 accepts -march=pentium... no checking if gcc-10 needs -fno-strength-reduce... yes checking if gcc-10 needs -fno-strict-aliasing... yes checking if gcc-10 supports -fno-common... yes checking if gcc-10 supports -pipe... yes checking if linux kbuild requires EXTRA_CFLAGS... no checking if linux kernel module build works... yes checking operation follow_link in inode_operations... no checking operation put_link in inode_operations... no checking operation rename in inode_operations... no checking for linux/cred.h... yes checking for linux/config.h... no checking for linux/exportfs.h... yes checking for linux/freezer.h... yes checking for linux/key-type.h... yes checking for linux/semaphore.h... yes checking for linux/seq_file.h... yes checking for linux/sched/signal.h... yes checking for
Bug#995018: marked as done (jupyter-server breaks jupyterlab-server autopkgtest: No module named 'anyio.to_thread')
Your message dated Mon, 27 Sep 2021 06:33:51 + with message-id and subject line Bug#995018: fixed in jupyter-server 1.11.0-1 has caused the Debian Bug report #995018, regarding jupyter-server breaks jupyterlab-server autopkgtest: No module named 'anyio.to_thread' 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.) -- 995018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jupyter-server Control: found -1 jupyter-server/1.10.2-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of jupyter-server the autopkgtest of jupyterlab-server fails in testing when that autopkgtest is run with the binary packages of jupyter-server from unstable. It passes when run with only packages from testing. In tabular form: passfail jupyter-server from testing1.10.2-1 jupyterlab-server from testing2.4.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Seems like a missing dependency in jupyter-server to me. Currently this regression is blocking the migration of jupyter-server to testing [1]. 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=jupyter-server https://ci.debian.net/data/autopkgtest/testing/amd64/j/jupyterlab-server/15485816/log.gz autopkgtest [05:54:07]: test import: [--- Traceback (most recent call last): File "", line 1, in File "/tmp/autopkgtest-lxc.69igrrrk/downtmp/build.edD/src/jupyterlab_server/__init__.py", line 4, in from .app import LabServerApp File "/tmp/autopkgtest-lxc.69igrrrk/downtmp/build.edD/src/jupyterlab_server/app.py", line 7, in from jupyter_server.extension.application import ExtensionApp, ExtensionAppJinjaMixin File "/usr/lib/python3/dist-packages/jupyter_server/extension/application.py", line 21, in from jupyter_server.serverapp import ServerApp File "/usr/lib/python3/dist-packages/jupyter_server/serverapp.py", line 80, in from jupyter_server.services.contents.filemanager import AsyncFileContentsManager, FileContentsManager File "/usr/lib/python3/dist-packages/jupyter_server/services/contents/filemanager.py", line 15, in from anyio.to_thread import run_sync ModuleNotFoundError: No module named 'anyio.to_thread' autopkgtest [05:54:07]: test import: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: jupyter-server Source-Version: 1.11.0-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of jupyter-server, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated jupyter-server package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Sep 2021 08:11:18 +0200 Source: jupyter-server Architecture: source Version: 1.11.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julien Puydt Closes: 995018 Changes: jupyter-server (1.11.0-1) unstable; urgency=medium . * Declare versioned dep on anyio (Closes: #995018). * New upstream release. * Add lintian overrides. Checksums-Sha1: d70a921ee2ef4d2c0d02e0e210b10471ce0e453e 2447 jupyter-server_1.11.0-1.dsc 184068f001dc610ddda83bb9e6df53af955014b1 296519 jupyter-server_1.11.0.orig.tar.gz 08030c8a51616adf4210e1dc3f2723c615ac9a08 4188 jupyter-server_1.11.0-1.debian.tar.xz 38130274953d05f3d919292b2c63237b8494b60a 8770 jupyter-server_1.11.0-1_source.buildinfo Checksums-Sha256: 414c74061bdf201b18fc31e73e76eadd03fe7c530da000602b6e721e70a1e345 2447 jupyter-server_1.11.0-1.dsc 9a8eef475986cd57dd1ad3a0daa62c5fee2be01dae93b27575eca2a65ba8178b 296519 jupyter-server_1.11.0.orig.tar.gz
