Bug#990223: pcp-zeroconf: modifies conffiles (policy 10.7.3): /etc/default/pmlogger
[Nathan Scott] > Upstream have created pcp-zeroconf as a non-default part of the PCP > package suite to automate first-time setup of Performance Co-Pilot for > new users in the same, documented fashion across different distros. > > So while it does indeed not meet the packaging requirements here, it is > not a required part of PCP but a convenience mechanism for new users > who are otherwise overwhelmed with the array of choice and in need of > some assistance as to where / how to start. > > As such, this is operating as intended, designed and documented. Any > users not wanting this behaviour would not opt-in to using this > package. A policy compliant way to implement this, and one that do not cause unexpected user visible questions about modified conffiles during upgrades, is to teach the program to read configuration from several locations and files, say /usr/share/pcp/config.d/ and /etc/pcp/config.d/, allowing values in /etc/ to override values in /usr/share/, and place the setup provided by the convenience mechanism pcp-zeroconf as a file in /usr/share/. This approach is known as multilevel configuration. I recommend it over modifying conffiles in /etc/. -- Happy hacking Petter Reinholdtsen
Bug#993707: FTBFS on arm64
Package: linux Version: 5.14-1~exp1 Severity: serious Hi, after applying the perf fixes, it builds for me on amd64, i386, armel, and armhf, but fails on arm64: ---snip--- dh_prep kernel-wedge install-files 5.14.0-trunk install -D -m 644 debian/linux-image-5.14.0-trunk-arm64/boot/vmlinuz-5.14.0-trunk-arm64 debian/kernel-image-5.14.0-trunk-arm64-di/boot/vmlinuz install -d debian/kernel-image-5.14.0-trunk-arm64-di/lib/modules/5.14.0-trunk-arm64 install -m 644 debian/linux-image-5.14.0-trunk-arm64/lib/modules/5.14.0-trunk-arm64/modules.builtin debian/linux-image-5.14.0-trunk-arm64/lib/modules/5.14.0-trunk-arm64/modules.order debian/kernel-image-5.14.0-trunk-arm64-di/lib/modules/5.14.0-trunk-arm64/ install -D -m 644 debian/linux-image-5.14.0-trunk-arm64/boot/System.map-5.14.0-trunk-arm64 debian/kernel-image-5.14.0-trunk-arm64-di/boot/System.map install -d debian/kernel-image-5.14.0-trunk-arm64-di/usr/lib cp -a debian/linux-image-5.14.0-trunk-arm64/usr/lib/linux-image-5.14.0-trunk-arm64 debian/kernel-image-5.14.0-trunk-arm64-di/usr/lib/linux-image-5.14.0-trunk-arm64 kernel-wedge copy-moduleven after applying the perf fixes, es 5.14.0-trunk arm64 5.14.0-trunk-arm64 kernel-wedge find-dups 5.14.0-trunk-arm64 debian/nic-usb-modules-5.14.0-trunk-arm64-di lib/modules/5.14.0-trunk-arm64/kernel/net/core/selftests.ko debian/nic-modules-5.14.0-trunk-arm64-di lib/modules/5.14.0-trunk-arm64/kernel/net/core/selftests.ko some modules are in more than one package command exited with status 1 make[2]: *** [debian/rules.real:570: install-udeb_arm64] Error 2 make[2]: Leaving directory '/build/linux-5.14-1~exp1' make[1]: *** [debian/rules.gen:35: binary-arch_arm64] Error 2 make[1]: Leaving directory '/build/linux-5.14-1~exp1' make: *** [debian/rules:43: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 ---snap--- Regards, Daniel
Processed: Bug#993651 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #993651 [lintian] lintian: "Profile debian/main references unknown checks" when run from Debian package Added tag(s) pending. -- 993651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993651: marked as pending in lintian
Control: tag -1 pending Hello, Bug #993651 in lintian 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/lintian/lintian/-/commit/0b5afce8edbb2cc8f0756a70299d2b4b83c4ce4e Read checks separately from ./lib and ./checks; forego symbolic link. (Closes: #993651) When pkg-js-tools is installed, dpkg does not set the symbolic link /usr/share/lintian/checks, and none of the checks in ./lib/Lintian/Check are found. The error is lengthy. [1] Needed for a proper upgrade path. Reads both locations separately instead. Also does the same for screens, but that was not relevant for the bug. [1] https://lists.debian.org/debian-lint-maint/2021/09/msg5.html Gbp-Dch: ignore (this message was generated automatically) -- Greetings https://bugs.debian.org/993651
Bug#978927: marked as done (xwelltris: ftbfs with autoconf 2.70)
Your message dated Sun, 05 Sep 2021 01:19:38 + with message-id and subject line Bug#978927: fixed in xwelltris 1.0.1-18 has caused the Debian Bug report #978927, regarding xwelltris: ftbfs with autoconf 2.70 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.) -- 978927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xwelltris Version: 1.0.1-17 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/xwelltris_1.0.1-17_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] checking for atexit... yes configure: creating ./config.status config.status: creating src/Make.common config.status: WARNING: 'src/Make.common.in' seems to ignore the --datarootdir setting config.status: creating src/makefile config.status: creating src/include/globals.h config.status: creating src/image/makefile config.status: creating Makefile config.status: creating src/include/config.h --- X Welltris Project -- Configuration: Source code location: . C Compiler: gcc C Compiler flags: -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security C++ Compiler: g++ Libraries:-lm Install path: /usr/bin Man pages path: /usr/man X11 versions: X Visuals:PseudoColor; TrueColor; Image library:GIF --- Type 'make' for building XWelltris binaries, and after that do 'make install' as 'root'. Thank you... make[1]: Leaving directory '/<>' dh_auto_build make -j4 make[1]: Entering directory '/<>' (cd src && make) make[2]: Entering directory '/<>/src' make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. gcc -c mydebug.c -DHAVE_CONFIG_H -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security `sdl-config --cflags` -I./sdl -DHAVE_CONFIG_H -I. -I./.. -I./image -I./include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 In file included from ./include/mydebug.h:4, from mydebug.c:17: ./include/config.h:235:16: error: duplicate ‘unsigned’ 235 | #define size_t unsigned int |^~~~ ./include/config.h:235:25: error: two or more data types in declaration specifiers 235 | #define size_t unsigned int | ^~~ make[2]: *** [makefile:169: mydebug.o] Error 1 make[2]: Leaving directory '/<>/src' make[1]: [Makefile:98: xwelltris] Error 2 (ignored) make[1]: Leaving directory '/<>' dh_auto_test create-stamp debian/debhelper-build-stamp dh_testroot dh_prep dh_installdirs debian/rules override_dh_auto_install make[1]: Entering directory '/<>' /usr/bin/make INSTDIR=/<>/debian/xwelltris/usr/games INSTLIB=/<>/debian/xwelltris/usr/share/games/xwelltris install make[2]: Entering directory '/<>' /usr/bin/install -c -d -m 755 /<>/debian/xwelltris/usr/share/games/xwelltris /usr/bin/install -c -m 644 data/polyomino.dat data/board2.gif data/font2.gif data/topnine.gif data/wellcuts.gif data/wellintro.gif /<>/debian/xwelltris/usr/share/games/xwelltris /usr/bin/install -c -m 666 data/welltris.scores /<>/debian/xwelltris/usr/share/games/xwelltris /usr/bin/install -c -s -m 755 xwelltris /<>/debian/xwelltris/usr/games /usr/bin/install: cannot stat 'xwelltris': No such file or directory make[2]: *** [Makefile:104: install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:11: override_dh_auto_install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: xwelltris Source-Version: 1.0.1-18 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of xwelltris, which is due to be installed in the D
Bug#993694: missing Depends: python3-jinja2
On 2021-09-04 23:45, Diane Trout wrote: Hmm... So dask doesn't think jinja is required for base functionality. It's a dependency for an extended extras. OK, thanks for checking it. ... At dask's end jinja should probably be a suggests or recommends, but since you can use dask without needing widgets I'm not 100% sure jinja needs to build-dependency. That sounds reasonable. dask should be consistent with itself, so if it doesn't Depend on jinja2, if it's only for extra functionality, then Suggests or Recommends is more appropriate than Depends. I had been assuming dask.widgets was a core component. In that case we could move this bug to python-xarray. If xarray wants to access optional functionality then it will need to make sure the required packages are installed. (Do widgets even work on Debian? Last time I tried jupyter widgets I couldn't get them to work.) Good question :) jupyter-sphinx has just been updated, presumably fixing a problem with ipywidgets (#950598 vs #896460). Perhaps that's related to jupyter widget operations.
Bug#976697: webext-umatrix: no longer developed upstream, remove or switch to LibreMatrix or?
On Sat, 2021-09-04 at 17:08 +0200, Axel Beckert wrote: > Also it is unclear to me why the source is the Mozilla XPI while the > package works with both and upstream offers different download files > for Firefox and for Chromium/Chrome. (Then again, I haven't worked on > browser extensions since Mozilla ditched XUL…) I tried updating webext-umatrix to the latest release and immediately encountered this issue too as the build fails with the upstream source instead of the upstream prebuilt XPI file. I think that using prebuilt XPI files when the upstream project has a git repository has a risk of DFSG item 2 violations. Debian using XPI files is one of the reasons I started this discussion about not using upstream packaging ecosystems: Debian choice of upstream tarballs for packaging https://lists.debian.org/msgid-search/937697e40caf519e18119635db07d7b74b37b980.ca...@debian.org That said, I expect building WebExtensions from source properly is going to be a large undertaking that will require lots of node-* packages and other dependencies to be added to Debian. So a reasonable way to start is probably to update to the latest XPI and then start working on the dependencies etc. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#993692:
hello, looks like the error regarding the forced kill is not a debian issue but also happens on ubuntu. Bug should be closed. The message seems curious as it is only produced when docker.service is stopped, not when a container is stopped using docker stop; next to that I do see containers are getting sigterm and correctly process it. sorry for the inconvenience! Tobias.
Bug#993694: missing Depends: python3-jinja2
Hmm...
So dask doesn't think jinja is required for base functionality. It's a
dependency for an extended extras.
>From dask's setup.py
extras_require = {
"array": ["numpy >= 1.18"],
"bag": [], # keeping for backwards compatibility
"dataframe": ["numpy >= 1.18", "pandas >= 1.0"],
"distributed": ["distributed == 2021.08.1"],
"diagnostics": [
"bokeh >= 1.0.0, != 2.0.0",
"jinja2",
],
"delayed": [], # keeping for backwards compatibility
}
At dask's end jinja should probably be a suggests or recommends, but
since you can use dask without needing widgets I'm not 100% sure jinja
needs to build-dependency.
(Do widgets even work on Debian? Last time I tried jupyter widgets I
couldn't get them to work.)
Diane
On Sat, 2021-09-04 at 22:36 +0200, Drew Parsons wrote:
> Package: python3-dask
> Version: 2021.08.1+dfsg-1
> Severity: serious
> Justification: debci
> Control: affects -1 src:python-xarray
>
> dask imports from jinja2 in
> /usr/lib/python3/dist-packages/dask/widgets/widgets.py, but
> Depends: python3-jinja2 has not been declared.
>
> dask's own tests are apparently not testing widget since they're
> passing, but
> the error is triggered by python-xarray, see
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/15028004/log.gz
>
>
> I guess debian/control needs Build-Depends: python3-jinja2
> and then dh_python will take care of the Depends field in the binary
> package.
>
> Drew
>
Processed: found 993303 in 2.2.9-2+deb11u1, affects 993303
Processing commands for cont...@bugs.debian.org: > found 993303 2.2.9-2+deb11u1 Bug #993303 [haproxy] haproxy: Fails to handle URL paths starting with more than one '/' using HTTP/2 Marked as found in versions haproxy/2.2.9-2+deb11u1. > affects 993303 + release.debian.org,security.debian.org Bug #993303 [haproxy] haproxy: Fails to handle URL paths starting with more than one '/' using HTTP/2 Added indication that 993303 affects release.debian.org and security.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 993303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992971: marked as done (grilo: CVE-2021-39365)
Your message dated Sat, 04 Sep 2021 21:34:32 + with message-id and subject line Bug#992971: fixed in grilo 0.3.13-1.1 has caused the Debian Bug report #992971, regarding grilo: CVE-2021-39365 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.) -- 992971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grilo Version: 0.3.13-1 Severity: important Tags: security upstream Forwarded: https://gitlab.gnome.org/GNOME/grilo/-/issues/146 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.3.7-1 Hi, The following vulnerability was published for grilo. CVE-2021-39365[0]: | In GNOME grilo though 0.3.13, grl-net-wc.c does not enable TLS | certificate verification on the SoupSessionAsync objects it creates, | leaving users vulnerable to network MITM attacks. NOTE: this is | similar to CVE-2016-20011. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-39365 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39365 [1] https://gitlab.gnome.org/GNOME/grilo/-/issues/146 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: grilo Source-Version: 0.3.13-1.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of grilo, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated grilo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Sep 2021 23:05:13 +0200 Source: grilo Architecture: source Version: 0.3.13-1.1 Distribution: unstable Urgency: medium Maintainer: Alberto Garcia Changed-By: Salvatore Bonaccorso Closes: 992971 Changes: grilo (0.3.13-1.1) unstable; urgency=medium . * Non-maintainer upload. . [ Alberto Garcia ] * fix-tls-cert-validation.patch: - Fix TLS cert validation not being done for any network call (Closes: #992971, CVE-2021-39365). Checksums-Sha1: ba3bc0ed5fba3a45a283f7f770b229596349a755 2466 grilo_0.3.13-1.1.dsc 9ea068631ea8216e25e8eb91cc82c0cf90300c37 9360 grilo_0.3.13-1.1.debian.tar.xz e8ae5a168fdafe90379ffd5b0bc1621a675c1df2 6597 grilo_0.3.13-1.1_source.buildinfo Checksums-Sha256: 4a367a9bab8b12fabe60be94ef99470825c69bc5857082401ff6828e9c9bfaa1 2466 grilo_0.3.13-1.1.dsc 51776912491eb97188c118592177f21863df166ad4549db42ab40a735071dddf 9360 grilo_0.3.13-1.1.debian.tar.xz 7cd4856ee0a8ea06dd7642a55768ec5704d3ba50f539d9b3607c1256f949427d 6597 grilo_0.3.13-1.1_source.buildinfo Files: fef83b5db514f67e84a86ac69da3af54 2466 libs optional grilo_0.3.13-1.1.dsc c279f9ec3c09d0013796b94fa4df1e4d 9360 libs optional grilo_0.3.13-1.1.debian.tar.xz 554feed6d502638eca5cac6adb4eecd1 6597 libs optional grilo_0.3.13-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmExP1hfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EiqMQAIZXMBMFoh4EpcH4qB6qWOmFK/kyNhrU /wWE+XzFuJyFkFMBPshLHEqOE4wANFRfoggz+3wS1oS65NUmkZ/pQ26cIZLvYQNR ZasXf7QIhFwxvWme587YcfihLmfOoPctbdZJZsgdUGdixkIlcgLYhA6Zjpzp/6YY U4RH8U/GxMEKDaXJbaElwOHnrP3CKD+EZZmF0qnzUvCfzuf4cEONBDBLIgPGWy1u WVP+Pa9NCi5bx08HTDR0fqv3wpY07LFxs2H9sK5PgamsVnGRpfVCFJpkISQP6UIh S17TbOo2WpVajjtb1D9J5E1rsa3Q294/eGimAEQHsWhVaGkkisuSUfhQnJlB6iD3 l9Devsq7Q8d0V/x6A1hItHyvWkNN2/+VgUZsuDCTZslhauIJJmSj+czIBWeOPkgq 8KHnkayD725PpuotD8Y4ieUOQRRFkMkE00pkW4JsFdEo2/Q86tOi7gOMfLI3/rGV dZQAgrA3xeZf167FGPUmoEjor3Wzj+nKiFEoUOncvBYKcDwz9Sw+gtWG0ymRYQYd v8Ud8voYA7Np6YG8Y5Y2hw672EZK+/k22bthBcU0nqem6jy23U6K0u/D8RekJ2cv 074veeH/JFBBHcQiM9+XYAy1WpbrKAspwRIbrlSKx6q4wecHSNALj09SPolQKFGG bXlhh6jY+oa5 =3f40 -END PGP SIGNATURE End Message ---
Processed: missing Depends: python3-jinja2
Processing control commands: > affects -1 src:python-xarray Bug #993694 [python3-dask] missing Depends: python3-jinja2 Added indication that 993694 affects src:python-xarray -- 993694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993694: missing Depends: python3-jinja2
Package: python3-dask Version: 2021.08.1+dfsg-1 Severity: serious Justification: debci Control: affects -1 src:python-xarray dask imports from jinja2 in /usr/lib/python3/dist-packages/dask/widgets/widgets.py, but Depends: python3-jinja2 has not been declared. dask's own tests are apparently not testing widget since they're passing, but the error is triggered by python-xarray, see https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/15028004/log.gz I guess debian/control needs Build-Depends: python3-jinja2 and then dh_python will take care of the Depends field in the binary package. Drew
Bug#993693: ReferenceError: options is not defined
Package: webpack Version: 5.6.0+~cs6.4.0-1~exp2 Severity: grave I was trying to update another js-team package and couldn't understand what was wrong until I tried to just run webpack by itself in another directory: $ webpack [webpack-cli] ReferenceError: options is not defined at Object.apply (/usr/share/nodejs/webpack/lib/config/defaults.js:873:30) at WebpackOptionsApply.process (/usr/share/nodejs/webpack/lib/WebpackOptionsApply.js:453:16) at createCompiler (/usr/share/nodejs/webpack/lib/webpack.js:78:28) at create (/usr/share/nodejs/webpack/lib/webpack.js:115:15) at webpack (/usr/share/nodejs/webpack/lib/webpack.js:123:46) at f (/usr/share/nodejs/webpack/lib/index.js:35:15) at WebpackCLI.createCompiler (/usr/share/nodejs/webpack- cli/lib/webpack-cli.js:176:24) at WebpackCLI.run (/usr/share/nodejs/webpack-cli/lib/webpack- cli.js:268:25) at async runCLI (/usr/share/nodejs/webpack- cli/lib/bootstrap.js:59:9) This means it's broken ; installing unstable's 4.43.0-6 made the error go away, so it's a problem only with the new version. Cheers, J.Puydt
Bug#993692: docker.io: docker.service does not shutdown containers gracefullly
Package: docker.io
Version: 20.10.5+dfsg1-1+b5
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: hostmas...@appelo.org
Dear Maintainer,
install a debian fresh bullsye system. install docker.io and run
nginx as a container. the container is forcefully killed:
"transport: Error while dialing dial unix:///run/containerd/containerd.sock:
timeout\". Reconnecting..." module=grpc
Sep 03 18:59:53 stevie dockerd[717535]: time="2021-09-03T18:59:53.062476364Z"
level=warning msg="grpc: addrConn.createTransport failed to connect to
{unix:///run/containerd/containerd.sock 0 }. Err :connection error:
desc = \"transport: Error while dialing dial
unix:///run/containerd/containerd.sock: timeout\". Reconnecting..." module=grpc
Sep 03 18:59:54 stevie dockerd[717535]: time="2021-09-03T18:59:54.062582937Z"
level=info msg="Container failed to stop after sending signal 3 to the process,
force killing"
Sep 03 18:59:54 stevie dockerd[717535]: time="2021-09-03T18:59:54.062844365Z"
level=error msg="failed to shut down container"
container=e0ab7899bffdf32fa2b47c84a56c29fec1674bbc85749c8b7d9bead8befd1efa
error="Failed to stop container
e0ab7899bffdf32fa2b47c84a56c29fec1674bbc85749c8b7d9bead8befd1efa with error:
Cannot kill container
e0ab7899bffdf32fa2b47c84a56c29fec1674bbc85749c8b7d9bead8befd1efa: connection
error: desc = \"transport: Error while dialing dial
unix:///run/containerd/containerd.sock: timeout\": unavailable"
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 docker.io depends on:
ii adduser 3.118
ii containerd 1.4.5~ds1-2
ii init-system-helpers 1.60
ii iptables 1.8.7-1
ii libc62.31-13
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libsystemd0 247.3-6
ii lsb-base 11.1.0
ii runc 1.0.0~rc93+ds1-5+b2
ii tini 0.19.0-1
Versions of packages docker.io recommends:
ii apparmor 2.13.6-10
ii ca-certificates 20210119
pn cgroupfs-mount
pn git
ii needrestart 3.5-4
ii xz-utils 5.2.5-2
Versions of packages docker.io suggests:
pn aufs-tools
pn btrfs-progs
pn debootstrap
pn docker-doc
ii e2fsprogs 1.46.2-2
pn rinse
pn rootlesskit
pn xfsprogs
pn zfs-fuse | zfsutils-linux
-- no debconf information
Bug#993691: pytest-mpi: autopkgtest regression: Building wheel for mpi4py (PEP 517): finished with status 'error'
Source: pytest-mpi Version: 0.5-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of pytest-mpi the autopkgtest of pytest-mpi fails in testing when that autopkgtest is run with the binary packages of pytest-mpi from unstable. It passes when run with only packages from testing. In tabular form: passfail pytest-mpi from testing0.5-3 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems that the test fell back to downloading all kind of stuff from the internet (I do hope unintended otherwise: please add a needs-internet restriction) and failed. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pytest-mpi https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-mpi/15028995/log.gz py39-mpi-oldpt create: /tmp/autopkgtest-lxc.54h7da0c/downtmp/build.9o5/src/.tox/py39-mpi-oldpt py39-mpi-oldpt installdeps: pytest, pytest-cov, sybil, -cknown_broken_constraints.txt, mpi4py, -cold_pytest.txt ERROR: invocation failed (exit code 1), logfile: /tmp/autopkgtest-lxc.54h7da0c/downtmp/build.9o5/src/.tox/py39-mpi-oldpt/log/py39-mpi-oldpt-1.log == log start === Collecting pytest Downloading pytest-5.4.3-py3-none-any.whl (248 kB) Collecting pytest-cov Downloading pytest_cov-2.12.1-py2.py3-none-any.whl (20 kB) Collecting sybil Downloading sybil-2.0.1-py2.py3-none-any.whl (13 kB) Collecting mpi4py Downloading mpi4py-3.1.1.tar.gz (2.4 MB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing wheel metadata: started Preparing wheel metadata: finished with status 'done' Collecting wcwidth Downloading wcwidth-0.2.5-py2.py3-none-any.whl (30 kB) Collecting packaging Downloading packaging-21.0-py3-none-any.whl (40 kB) Collecting more-itertools>=4.0.0 Downloading more_itertools-8.9.0-py3-none-any.whl (51 kB) Collecting attrs>=17.4.0 Downloading attrs-21.2.0-py2.py3-none-any.whl (53 kB) Collecting py>=1.5.0 Downloading py-1.10.0-py2.py3-none-any.whl (97 kB) Collecting pluggy<1.0,>=0.12 Downloading pluggy-0.13.1-py2.py3-none-any.whl (18 kB) Collecting toml Downloading toml-0.10.2-py2.py3-none-any.whl (16 kB) Collecting coverage>=5.2.1 Downloading coverage-5.5-cp39-cp39-manylinux2010_x86_64.whl (243 kB) Collecting pyparsing>=2.0.2 Downloading pyparsing-2.4.7-py2.py3-none-any.whl (67 kB) Building wheels for collected packages: mpi4py Building wheel for mpi4py (PEP 517): started Building wheel for mpi4py (PEP 517): finished with status 'error' ERROR: Command errored out with exit status 1: OpenPGP_signature Description: OpenPGP digital signature
Bug#993480: marked as done (gcl: Fails to install in unstable)
Your message dated Sat, 04 Sep 2021 20:22:40 + with message-id and subject line Bug#993480: fixed in gcl 2.6.12-103 has caused the Debian Bug report #993480, regarding gcl: Fails to install in unstable 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.) -- 993480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcl Version: 2.6.12-102 Severity: serious Justification: cannot install Hello, gcl cannot be installed in a fresh unstable chroot: Setting up gcl (2.6.12-102) ... /var/lib/dpkg/info/gcl.postinst: 5: tempfile: not found /var/lib/dpkg/info/gcl.postinst: 5: tempfile: not found /var/lib/dpkg/info/gcl.postinst: 27: cannot create : Directory nonexistent dpkg: error processing package gcl (--configure): installed gcl package post-installation script subprocess returned error exit status 2 tempfile was indeed dropped from the debianutils package as of its version 5.0-1 Samuel -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 gcl depends on: ii debconf 1.5.77 ii emacs-gtk [emacsen] 1:27.1+1-3.1 ii gcc 4:10.2.1-1 ii libc62.31-17 ii libgmp10 2:6.2.1+dfsg-1 pn libreadline6 ii libreadline7 7.0-5 ii libreadline8 8.1-2 ii libtcl8.68.6.11+dfsg-1 ii libtk8.6 8.6.11-2 ii libx11-6 2:1.7.2-1 ii ucf 3.0043 gcl recommends no packages. Versions of packages gcl suggests: pn gcl-doc -- Samuel "...very few phenomena can pull someone out of Deep Hack Mode, with two noted exceptions: being struck by lightning, or worse, your *computer* being struck by lightning." (By Matt Welsh) --- End Message --- --- Begin Message --- Source: gcl Source-Version: 2.6.12-103 Done: Camm Maguire We believe that the bug you reported is fixed in the latest version of gcl, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Camm Maguire (supplier of updated gcl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Sep 2021 19:23:26 + Source: gcl Architecture: source Version: 2.6.12-103 Distribution: unstable Urgency: medium Maintainer: Camm Maguire Changed-By: Camm Maguire Closes: 993480 Changes: gcl (2.6.12-103) unstable; urgency=medium . * Bug fix: "Fails to install in unstable", thanks to Samuel Thibault (Closes: #993480). Checksums-Sha1: a90d7158bb35fda76d1b338c651341fe3258e131 2060 gcl_2.6.12-103.dsc a6ece446ae0aec24433e51c3ba87dca127ff5e7e 5158788 gcl_2.6.12-103.debian.tar.xz 3afe27457972dee8b768b52b95bbd1adf5cb708e 7486 gcl_2.6.12-103_source.buildinfo Checksums-Sha256: 9675365163778d1460b43313ed9d73664697c921b98f394a75e9243343cc124c 2060 gcl_2.6.12-103.dsc 2aeb0b7e956f40098d8b009783e0dfc850780f2cba52348e8462973bd10fbddf 5158788 gcl_2.6.12-103.debian.tar.xz 67725a2be7ad362edbeba76923f7f5482e8bd36ca17085767cb2ce0a6b88c569 7486 gcl_2.6.12-103_source.buildinfo Files: 87953a3d3f934405fac56ff1f11e59d5 2060 lisp optional gcl_2.6.12-103.dsc a3ecc01adcf0be56f7a3229f111f6f1d 5158788 lisp optional gcl_2.6.12-103.debian.tar.xz 34e67474e371cb7ddc7f05efb4229d00 7486 lisp optional gcl_2.6.12-103_source.bu
Bug#993532: marked as done (libpod: autopkgtest regression between 29 Aug 2021 and 2 Sep 2021)
Your message dated Sat, 4 Sep 2021 18:56:31 +0200 with message-id and subject line Re: Bug#993532: libpod: autopkgtest regression between 29 Aug 2021 and 2 Sep 2021 has caused the Debian Bug report #993532, regarding libpod: autopkgtest regression between 29 Aug 2021 and 2 Sep 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.) -- 993532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpod Version: 3.0.1+dfsg1-3 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 four days ago 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. Looking at the error, I have no clue why. Can you fix the situation? Paul [1] https://ci.debian.net/packages/libp/libpod/ https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpod/14990105/log.gz dh_auto_build: error: cd _output && go install -trimpath -v -p 2 -tags apparmor,ostree,seccomp,selinux,systemd -ldflags "-X main.buildInfo=3.0.1+dfsg1-3" github.com/containers/podman/cmd/podman github.com/containers/podman/cmd/podman/common github.com/containers/podman/cmd/podman/completion github.com/containers/podman/cmd/podman/containers github.com/containers/podman/cmd/podman/generate github.com/containers/podman/cmd/podman/healthcheck github.com/containers/podman/cmd/podman/images github.com/containers/podman/cmd/podman/inspect github.com/containers/podman/cmd/podman/manifest github.com/containers/podman/cmd/podman/networks github.com/containers/podman/cmd/podman/parse github.com/containers/podman/cmd/podman/play github.com/containers/podman/cmd/podman/pods github.com/containers/podman/cmd/podman/registry github.com/containers/podman/cmd/podman/system github.com/containers/podman/cmd/podman/system/connection github.com/containers/podman/cmd/podman/utils github.com/containers/podman/cmd/podman/validate github.com/containers/podman/cmd/podman/volumes github.com/containers/podman/libpod github.com/containers/podman/libpod/common github.com/containers/podman/libpod/define github.com/containers/podman/libpod/driver github.com/containers/podman/libpod/events github.com/containers/podman/libpod/image github.com/containers/podman/libpod/layers github.com/containers/podman/libpod/linkmode github.com/containers/podman/libpod/lock github.com/containers/podman/libpod/lock/file github.com/containers/podman/libpod/lock/shm github.com/containers/podman/libpod/logs github.com/containers/podman/libpod/logs/reversereader github.com/containers/podman/libpod/network github.com/containers/podman/libpod/plugin github.com/containers/podman/libpod/shutdown github.com/containers/podman/pkg/annotations github.com/containers/podman/pkg/api/handlers github.com/containers/podman/pkg/api/handlers/compat github.com/containers/podman/pkg/api/handlers/libpod github.com/containers/podman/pkg/api/handlers/swagger github.com/containers/podman/pkg/api/handlers/utils github.com/containers/podman/pkg/api/server github.com/containers/podman/pkg/api/server/idle github.com/containers/podman/pkg/api/types github.com/containers/podman/pkg/auth github.com/containers/podman/pkg/autoupdate github.com/containers/podman/pkg/bindings github.com/containers/podman/pkg/bindings/containers github.com/containers/podman/pkg/bindings/generate github.com/containers/podman/pkg/bindings/generator github.com/containers/podman/pkg/bindings/images github.com/containers/podman/pkg/bindings/manifests github.com/containers/podman/pkg/bindings/network github.com/containers/podman/pkg/bindings/play github.com/containers/podman/pkg/bindings/pods github.com/containers/podman/pkg/bindings/system github.com/containers/podman/pkg/bindings/util github.com/containers/podman/pkg/bindings/volumes github.com/containers/podman/pkg/cgroups github.com/containers/podman/pkg/channel github.com/containers/podman/pkg/checkpoint github.com/containers/podman/pkg/copy github.com/containers/podman/pkg/criu github.com/containers/podman/pkg/ctime github.com/containers/podman/pkg/domain/entities github.com/containers/podman/pkg/domain/entities/reports github.com/containers/podman/pkg/domain/filters github.com/containers/podman/pkg/domain/infra github.com/containers/podman/pkg/domain/infra/abi github.com/containers/podman/pkg/domain/infra/abi/parse
Bug#992439: marked as done (libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck)
Your message dated Sat, 04 Sep 2021 16:03:30 + with message-id and subject line Bug#992439: fixed in libconfig-model-dpkg-perl 2.149 has caused the Debian Bug report #992439, regarding libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck 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.) -- 992439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libconfig-model-dpkg-perl Version: 2.143 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Licensecheck seemingly gets blocked from entering stable currently, due to libconfig-model-dpkg-perl 2.143 fialing its autopkgtest: not ok 14 - check scikit-learn copyright # Failed test 'check scikit-learn copyright' # at t/scanner/scan-copyright.t line 27. # --- t/scanner/examples/scikit-learn.out Mon Jan 25 17:34:01 2021 # +++ /tmp/9pPbiX1AYv Tue Aug 17 04:10:11 2021 # @@ -2,3 +2,7 @@ # Copyright: 2007-2019, The scikit-learn developers. # License: BSD-3-clause # # +Files: sklearn/* # +Copyright: no-info-found # +License: BSD-3-clause # + I don't understand exactly what that test does, but seems licensecheck identified the license for one of the files in the example directory: $ licensecheck --lines 0 --deb-fmt --recursive t/scanner/examples/scikit-learn.d t/scanner/examples/scikit-learn.d/COPYING: BSD-3-clause t/scanner/examples/scikit-learn.d/doc/README.md: *No copyright* UNKNOWN t/scanner/examples/scikit-learn.d/sklearn/base.py: *No copyright* UNKNOWN t/scanner/examples/scikit-learn.d/doc/images/inria-small.png: UNKNOWN t/scanner/examples/scikit-learn.d/sklearn/datasets/images/flower.jpg: UNKNOWN t/scanner/examples/scikit-learn.d/sklearn/datasets/images/scikit-learn-logo.bmp: UNKNOWN t/scanner/examples/scikit-learn.d/sklearn/datasets/images/sydney-primary.jpeg: UNKNOWN If this is believed to be a bug in licensecheck, then please provide a shell command to reproduce the issue, and reassign this bugreport to licensecheck. Kind regards, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmEdKgsACgkQLHwxRsGg ASFqtA//Wm1GrIACTRQvDNj6ZR0kSkF+9+hHg6l++VGqUWttP+A2bCQxAHCOTSJ8 h59KkCMATuz8BrbGBHB/Jv7M3zbAOGTIrGYt+AKPBw63kxbtSk/8P6yvpalvX2Zc TTw7tBZ7kNxdN8un4SXU6kzbSCx2E8bwDSqd3dYMm0VtBkdF+6hguND9Tu920mVh H2VMf70X0XVRn7uulBol4lFPpNLMSddFdohhIoH4cz4F4ZxX6aGGWC9AO38CDFAj k3RQDNcAkv/pPokk/5cHPqRKVWIwObC9fOhAA/1CCCSXQVmLcRLKNf2ZNIzikt++ 82kXJD6xZhCvRem5/zxh7FlnQiqvgk/7bNrayudxfybh9Q3qFQWXNx3kD/DG0/ti c3MKauBlTT+F04NmdpaN8bxaAI7mupl262jG1bBOMmpw2DwnvSivHfqPwBjK4SCC cuoksqtn8coo53wL4f9wmB3StEMs/r2P/J0u17xMPXnDCKCf1ZqUKoVHR88yxkc2 FPXRTrN3YpSsh8SGE/Yw6f6O8ln0VKIKGdrliLufG4W5lhlakwJkvfWsIJCf1ibk hCSZnfVYuKfB4VovbpnSVEpPhaG34NIGrRzJ4az3yMdutda/j59/jAAC7Kyj7wi7 XbVE8p2D9q3RBse+f93eaTCDcWShZ5tNkz74MZXlAvmynBy3Aic= =F+YP -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libconfig-model-dpkg-perl Source-Version: 2.149 Done: Dominique Dumont We believe that the bug you reported is fixed in the latest version of libconfig-model-dpkg-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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated libconfig-model-dpkg-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: Sat, 04 Sep 2021 15:33:00 +0200 Source: libconfig-model-dpkg-perl Architecture: source Version: 2.149 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Dominique Dumont Closes: 992439 Changes: libconfig-model-dpkg-perl (2.149) unstable; urgency=medium . * control: add BD-I on libregexp-pattern-license-perl >= 3.9.3 (Closes: 992439) Checksums-Sha1: 929fcdcf091b023115e470a797ab813dd4fe7d3b 2830 libconfig-model-dpkg-perl_2.149.dsc 036a15e1c3299adc67ae74bffcff07e52c4b67c7 499148 libconfig-model-dpkg-perl_2.149.tar.xz 29166328906746a942e4f7d4bba13c278783cef3 5757 libconfig-model-dpkg-perl_2.149_source.buildinfo Checksums-Sha256: 08f114eeaf123dd83731c9fd55658087637b5b046489259eddda05411bc9
Bug#976697: webext-umatrix: no longer developed upstream, remove or switch to LibreMatrix or?
Hi, Paul Wise wrote: > uMatrix is no longer developed upstream: > > https://github.com/gorhill/uMatrix > > This repository has been archived by the owner. It is now read-only. […] > The upstream author has stated they no longer have time for it: > > > https://github.com/uBlockOrigin/uMatrix-issues/issues/291#issuecomment-694988696 > >I've archived uMatrix's repo, I can't and won't be spending any more >time on this project, and neither on all such issues. Despite this he did two stable release (1.4.2 and 1.4.4) in July 2021 a bunch of beta releases in 2020, February and July 2021: https://github.com/gorhill/uMatrix/releases https://chrome.google.com/webstore/detail/empty-title/ogfcmafjalglgifnmanfmnieipoejdcf?ucbcb=1 https://addons.mozilla.org/de/firefox/addon/umatrix/ (And then archived the Github repo again as it seems. *sigh*) So for me it looks like the author still cares about security issues, but has no time for other support. Which IMHO would be OK for a Debian Stable release. > These are the options for solving this issue: > > uMatrix could be removed in favour of uBlock Origin's advanced mode. IMHO this is no real solution. It works completely different and is at least (from an UI/UX aspect) unusable for me. IMHO no alternative. > uMatrix could be removed and LibreMatrix packaged, I think this is a > community fork so it should be a drop-in replacement. > > https://www.librematrix.com/ Seems to have been rather short-lived and is dead and removed already: This site can’t be reached www.librematrix.com’s server IP address could not be found. […] ERR_NAME_NOT_RESOLVED > https://github.com/LibreMatrix/LibreMatrix This as well: 404 This is not the web page you are looking for. The same counts for the according account: https://github.com/LibreMatrix So IMHO continuing with the original source seems (again) the best solution to me. I'd also help packaging 1.4.4 (at least), but the packaging is quite non-standard while no debian/README.source is present. And amo-changelog throws Python errors, probably needs an update wrt. python3-urllib: ~/uMatrix/umatrix → make -f debian/rules get-orig-changelog amo-changelog -p rst umatrix failed to write debian/upstream/changelog.html: module 'urllib' has no attribute 'error' make: *** [debian/rules:11: get-orig-changelog] Error 1 Also it is unclear to me why the source is the Mozilla XPI while the package works with both and upstream offers different download files for Firefox and for Chromium/Chrome. (Then again, I haven't worked on browser extensions since Mozilla ditched XUL…) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#993665: debianutils: tempfile still required in printer-driver-pnm2ppa
Package: debianutils Version: 5.4-3 Severity: critical Justification: breaks unrelated software The tempfile saga is not over. It might be wise grepping through the maintainer scripts of all packages. printer-driver-pnm2ppa still requires it. Best -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.13+ (SMP w/8 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debianutils depends on: ii libc6 2.31-17 debianutils recommends no packages. debianutils suggests no packages. -- no debconf information
Bug#993658: qemu-user-static does not work through binfmt since 6.0
❦ 4 September 2021 15:49 +03, Michael Tokarev: >> Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads) > > Can you please check if it works with not-so-fresh kernel > (eg the one from bullseye)? > > I wont able to do this until late evening today. > > I'm guessing this is the upstream way to detect if we were > called from binfmt subsystem (they done it within kernel) > interferes with my way of doing the same without touching > the kernel. Kernel side is a recent addition. It works fine with 5.10.0-8-amd64 from bullseye. Thanks! -- The Public is merely a multiplied "me." -- Mark Twain
Processed: found 993361 in 3.0.9-1, tagging 993361
Processing commands for cont...@bugs.debian.org: > found 993361 3.0.9-1 Bug #993361 [src:kylin-burner] kylin-burner: Please release 3.0.10 to unstable Marked as found in versions kylin-burner/3.0.9-1. > tags 993361 + bookworm sid Bug #993361 [src:kylin-burner] kylin-burner: Please release 3.0.10 to unstable Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 993361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993658: qemu-user-static does not work through binfmt since 6.0
04.09.2021 14:33, Vincent Bernat wrote: > Package: qemu-user-static > Version: 1:6.1+dfsg-4 > Severity: critical > Hey! Since 6.0, qemu-user-static does not seem to work properly through binfmt. I am a bit lost on how to diagnose that: ... When invoked through binfmt, the binaries seem to go from "I display something wrong" to "I will wipe your entire home". That's what happened to me when using cowbuilder. The chroot was not able to be Ouch. setup correctly and during the clean phase, cowbuilder did not detect the bind mount and/or was not able to undo them, rm -rfing everything that was mounted. Downgrading qemu-user-static to 1:5.2+dfsg-11 fixes the issue. ... Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads) Can you please check if it works with not-so-fresh kernel (eg the one from bullseye)? I wont able to do this until late evening today. I'm guessing this is the upstream way to detect if we were called from binfmt subsystem (they done it within kernel) interferes with my way of doing the same without touching the kernel. Kernel side is a recent addition. Thanks! /mjt
Processed: tagging 991344
Processing commands for cont...@bugs.debian.org: > # Fixed since 1.4.2, see https://github.com/gorhill/uMatrix/releases/tag/1.4.2 > tags 991344 + fixed-upstream Bug #991344 [src:umatrix] umatrix: CVE-2021-36773: Denial of Service Bug #991770 [src:umatrix] umatrix: new upstream release (1.4.4) fixes security issue Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 991344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991344 991770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947667: gabedit: build-depends (unnecessarily?) on deprecated libpangox-1.0-dev
On Sat, 28 Dec 2019 at 21:15:35 +, Simon McVittie wrote: > This package has a build-dependency on libpangox-1.0-dev, the Core X > backend for Pango, which has been deprecated since at least 2012, is > unmaintained upstream and is essentially unmaintained in Debian. ... > There doesn't seem to be a runtime dependency on libpangox-1.0-0, so > perhaps the build-dependency is unnecessary? Yes, the build-dependency is unnecessary. Please consider https://salsa.debian.org/debichem-team/gabedit/-/merge_requests/1 (also attached as a patch, if you prefer those). I've verified using diffoscope that adding this patch does not alter the contents of the binary package. (<3 reproducible builds!) I have not otherwise tested the binary package; sorry, I have no idea what gabedit is or what it does, other than "probably something to do with chemistry" :-) gabedit will be removed from testing soon if this bug is not resolved, and I'm trying to remove pangox-compat from Debian entirely during the bookworm cycle. smcv >From abc83b91de7fdf65fa0e7f0eab9e4224e34015d7 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Sat, 4 Sep 2021 13:13:11 +0100 Subject: [PATCH] Remove unused build-dependency on pangox-compat Closes: #947667 --- debian/control | 1 - debian/rules | 4 ++-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/debian/control b/debian/control index c85035d..c7ac033 100644 --- a/debian/control +++ b/debian/control @@ -11,7 +11,6 @@ Build-Depends: debhelper-compat (= 12), libgtk2.0-dev, libgtkglext1-dev, libpango1.0-dev, - libpangox-1.0-dev, pkg-config, xutils-dev Standards-Version: 4.5.0 diff --git a/debian/rules b/debian/rules index 4a8e443..cd379be 100755 --- a/debian/rules +++ b/debian/rules @@ -12,8 +12,8 @@ PACKAGE=gabedit INSTALL=/usr/bin/install PKG_CONFIG ?= pkg-config -GTKLIB= `$(PKG_CONFIG) --libs gtk+-2.0 gtkglext-1.0 pangox` -GTKCFLAGS = `$(PKG_CONFIG) --cflags gtk+-2.0 gtkglext-1.0 pangox` +GTKLIB= `$(PKG_CONFIG) --libs gtk+-2.0 gtkglext-1.0 pango` +GTKCFLAGS = `$(PKG_CONFIG) --cflags gtk+-2.0 gtkglext-1.0 pango` OGLLIB= -lGL -lGLU OGLCFLAGS = -I/usr/include LIBPTHREAD= -lpthread -- 2.33.0
Bug#993661: drbd-doc: Build-Depends on obsolete libgtkmathview-bin
Source: drbd-doc Version: 8.4~20151102-1 Severity: serious Justification: blocker for resolving other serious bugs User: User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pangox drbd-doc Build-Depends on libgtkmathview-bin, which is obsolete and is blocking the removal of other obsolete packages such as pangox-compat. It looks as though it should be possible to remove this build-dependency by configuring with --disable-mathml. smcv
Bug#993659: firefox-esr: FTBFS and embeded copy of code
Source: src:firefox-esr
Version: FTBFS and embdeded copy
Severity: serious
Tags: upstream ftbfs
Control: clone -1 -2
Control: affects -2 src:firefox
Dear Maintainer,
I could not found the source of the following files
https://sources.debian.org/src/firefox-
esr/78.13.0esr-1/devtools/client/debugger/dist/*.js
https://sources.debian.org/src/firefox-
esr/78.13.0esr-1/devtools/client/debugger/flow-typed/npm/*
Additionnally embdeded copy should be mentionned in README.Source
Thanks
Bastien
Note that header said compiled with babel so technically it is FTBFS for debian
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Bulk Media Downloader
Location: /usr/share/webext/bulk-media-downloader
Package: webext-bulk-media-downloader
Status: enabled
Name: Clair theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Déploiement de DoH
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Dictionnaire français dictionary
Location:
${PROFILE_EXTENSIONS}/fr-dicolle...@dictionaries.addons.mozilla.org.xpi
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: eBay
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Français Language Pack locale
Location: ${PROFILE_EXTENSIONS}/langpack...@firefox.mozilla.org.xpi
Status: enabled
Name: Français Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-fr
Status: enabled
Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled
Name: HTTPS partout
Location: /usr/share/webext/https-everywhere
Package: webext-https-everywhere
Status: enabled
Name: Privacy Badger
Location: /usr/share/webext/privacy-badger
Package: webext-privacy-badger
Status: enabled
Name: Qwant
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Resurrect Pages
Location: ${PROFILE_EXTENSIONS}/{0c8fbd76-bdeb-4c52-9b24-d587ce7b9dc3}.xpi
Status: enabled
Name: Sombre theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Thème par défaut theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled
Name: uBlock Origin
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ublo...@raymondhill.net
Package: webext-ublock-origin-firefox
Status: enabled
Name: Web Compat
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: WebCompat Reporter
Location:
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled
Name: Wikipédia (fr)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
-- Plugins information
-- Addons package information
ii firefox-esr 78.13.0esr-1 amd64Mozilla Firefox web
browser - Extended Support Release (ESR)
ii firefox-esr-l10n-fr 78.13.0esr-1 all French language
package for Firefox ESR
ii webext-bulk-media-downloader 0.2.1-3.1 all Cross-browser
extension to detect and download media resources
ii webext-https-everywhere 2021.7.13-1 all Extension to force
the use of HTTPS on many sites
ii webext-privacy-badger2020.10.7-1 all Privacy Badger
automatically learns to block invisible trackers
ii webext-ublock-origin-firefox 1.37.0+dfsg-1 all lightweight and
efficient ads, malware, trackers blocker (Firefox)
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
-- no debconf information
Processed: Re: Bug#947900: chemical-mime-data: build-depends on unmaintained gnome-mime-data
Processing control commands: > severity -1 serious Bug #947900 [chemical-mime-data] chemical-mime-data: build-depends on unmaintained gnome-mime-data Severity set to 'serious' from 'important' -- 947900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
debian-bugs-rc@lists.debian.org
Your message dated Sat, 04 Sep 2021 11:33:38 +
with message-id
and subject line Bug#993611: fixed in xrootd 5.3.1-2
has caused the Debian Bug report #993611,
regarding xrootd FTBFS on 32bit: error: no matching function for call to
‘max(off64_t, uint64_t&)’
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.)
--
993611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xrootd
Version: 5.3.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=xrootd&ver=5.3.1-1
...
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc: In function ‘ssize_t
ceph_posix_pwrite(int, const void*, size_t, off64_t)’:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: error: no
matching function for call to ‘max(off64_t, uint64_t&)’
803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count
- 1, fr->maxOffsetWritten);
|
^
In file included from /usr/include/c++/10/memory:63,
from
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:36:
/usr/include/c++/10/bits/stl_algobase.h:254:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&)’
254 | max(const _Tp& __a, const _Tp& __b)
| ^~~
/usr/include/c++/10/bits/stl_algobase.h:254:5: note: template argument
deduction/substitution failed:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: note:
deduced conflicting types for parameter ‘const _Tp’ (‘long long int’ and
‘uint64_t’ {aka ‘long long unsigned int’})
803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count
- 1, fr->maxOffsetWritten);
|
^
In file included from /usr/include/c++/10/memory:63,
from
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:36:
/usr/include/c++/10/bits/stl_algobase.h:300:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&,
_Compare)’
300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp)
| ^~~
/usr/include/c++/10/bits/stl_algobase.h:300:5: note: template argument
deduction/substitution failed:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: note:
deduced conflicting types for parameter ‘const _Tp’ (‘long long int’ and
‘uint64_t’ {aka ‘long long unsigned int’})
803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count
- 1, fr->maxOffsetWritten);
|
^
...
--- End Message ---
--- Begin Message ---
Source: xrootd
Source-Version: 5.3.1-2
Done: Mattias Ellert
We believe that the bug you reported is fixed in the latest version of
xrootd, 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 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mattias Ellert (supplier of updated xrootd
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 04 Sep 2021 09:32:33 +0200
Source: xrootd
Architecture: source
Version: 5.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert
Changed-By: Mattias Ellert
Closes: 993611
Changes:
xrootd (5.3.1-2) unstable; urgency=medium
.
* Re-upload source only
* Fix compilation on some 32 bit architectures (Closes: #993611)
* Link to libatomic when needed (riscv64)
Checksums-Sha1:
1922d6628150505e44c368181a4007832c96d697 4139 xrootd_5.3.1-2.dsc
a5707214d0a5b03b91c776c20ee5046490cb26d0 9996 xrootd_5.3.1-2.debian.tar.xz
55a09e356d57351858482fbfa3f7869e4869da60 26682 xrootd_5.3.1-2_amd64.buildinfo
Checksums-Sha256:
7dbdd06a7e495f033c2fb88d001b55e7ad68c916e912aa1a6f07e16a29968073 4139
xrootd_5.3.1-2.dsc
d232b10061815be639dc0355c92821040432594053beda96d3e2e537bfe0648d 9996
xrootd_5.3.1-2.debian.tar.xz
80b6799819fa2b886f1b6df68e6189237ee6e2167eda7da33123057070dc71c8 26682
xrootd_5.3.1-2_amd64.buildinfo
Files:
94e561f82f54f37a96700e0fcb7897b5 4139 net optional xrootd_5.3.1-
Bug#993658: qemu-user-static does not work through binfmt since 6.0
Package: qemu-user-static Version: 1:6.1+dfsg-4 Severity: critical -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Since 6.0, qemu-user-static does not seem to work properly through binfmt. I am a bit lost on how to diagnose that: 13:23 ❱ cat /proc/sys/fs/binfmt_misc/qemu-aarch64 enabled interpreter /usr/libexec/qemu-binfmt/aarch64-binfmt-P flags: POCF offset 0 magic 7f454c46020101000200b700 mask ff00feff 13:23 ❱ ./bin/busybox ls BusyBox v1.30.1 (Debian 1:1.30.1-7) multi-call binary. BusyBox is copyrighted by many authors between 1998-2015. Licensed under GPLv2. See source distribution for detailed copyright notices. [...] 13:25 ❱ file bin/busybox bin/busybox: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=6a67fd6d086c703062f3be2d751adf619aa67bc6, for GNU/Linux 3.7.0, stripped When invoked through binfmt, the binaries seem to go from "I display something wrong" to "I will wipe your entire home". That's what happened to me when using cowbuilder. The chroot was not able to be setup correctly and during the clean phase, cowbuilder did not detect the bind mount and/or was not able to undo them, rm -rfing everything that was mounted. Downgrading qemu-user-static to 1:5.2+dfsg-11 fixes the issue. 13:30 ❱ cat /proc/sys/fs/binfmt_misc/qemu-aarch64 enabled interpreter /usr/libexec/qemu-binfmt/aarch64-binfmt-P flags: POCF offset 0 magic 7f454c46020101000200b700 mask ff00feff 13:31 ❱ ./bin/busybox ls bin usr - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 qemu-user-static depends on no packages. Versions of packages qemu-user-static recommends: ii binfmt-support 2.2.1-1 Versions of packages qemu-user-static suggests: ii sudo 1.9.5p2-3 - -- no debconf information -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmEzWXASHGJlcm5hdEBk ZWJpYW4ub3JnAAoJEJWkL+g1NSX5QgoQAKCvyj4ZvK38O+U4JczjZgEyFr1F3L91 04eRxVhienFsserUx+8qE50kQvAjFXt7iqjugF65o+UpsgC0YCG7f8Ri5KAynHWx X5ChFgyZtjU3W9ZOs/zGBa9g2Dw8v3FcXO4AvjZnlmXHzLM7Xh7OhcmUjnQe5U1s JPXw8tojzJA6gaqjCZRmkBuVZMfLteUSeb/yxbopdUCqlv89bFF5VyHS/Agoxj8Q iRyo8qcyAhur/oqMe0tTCoLP9IWtisF1mO0TZoFe82qzSL/WTayn9nvJ7mhCS/s/ 2PyuVa9z1z4NprnZj4f6L3DFszbIB/rlkZng1/GNd9VwAbFqlgGltHZbww1mAOhP 2+ssNF7TDWuFeNQbUwk/YJyzySM/t9fL+O21onahLOR/Hc+Z+tD0f91AdOhBOxM0 D14cqYjKiyQ3Td+N46ZyEkJXW1ThNE2PLU+tnkyXFJGOCfgVLZdPyIeyV77We/MF 9yV9Jy3XrvwuSuqaZZSmlqTp5HzY86AgfEesYTB7diyBTeFwKPE8qnNKOIBXLakG yqH19GtqReRK4zImsQ+/0UU9qxuvrpwGgaAsClZtAxyeBLLdffsXi2kb4EAJ9B2C HFHwSOF+zC91xm8x1wbezCJf9newuQRxvciAIPcXKmKwut9oLqI/zSDRk5LoZLwy VjloaV/64hIA =15C8 -END PGP SIGNATURE-
Bug#993651: lintian: "Profile debian/main references unknown checks" when run from Debian package
Package: lintian Version: 2.104.0 Severity: serious Hi, Building the Debian package of Lintian from Git (5de96f0301) and then running it, for example, on itself results in the error below. Am assuming it's a dev/prod path issue, and had a glance at the code but couldn't quite work out why it couldn't find the checks in the import path. Profile debian/main references unknown checks: apache2 application-not-library appstream-metadata apt binaries build-systems/automake build-systems/autotools build-systems/autotools/libtool build-systems/cmake build-systems/waf changes-file conffiles continuous-integration/salsa control-files cron cruft deb-format debhelper debian/changelog debian/control debian/copyright debian/copyright/apache-notice debian/copyright/dep5 debian/debconf debian/desktop-entries debian/filenames debian/files debian/line-separators debian/lintian-overrides debian/lintian-overrides/comments debian/manual-pages debian/not-installed debian/patches debian/patches/count debian/patches/dep3 debian/patches/dpatch debian/patches/quilt debian/po-debconf debian/readme debian/rules debian/rules/dh-sequencer debian/source-dir debian/source/include-binaries debian/substvars debian/symbols debian/trailing-whitespace debian/upstream/metadata debian/upstream/signing-key debian/variables debian/version-substvars debian/watch debian/watch/standard desktop/dbus desktop/gnome desktop/gnome/gir desktop/icons desktop/x11 dh-make documentation documentation/doxygen documentation/examples documentation/manual documentation/texinfo emacs emacs/elpa examples fields/architecture fields/bugs fields/built-using fields/changed-by fields/checksums fields/deb822 fields/derivatives fields/description fields/distribution fields/dm-upload-allowed fields/empty fields/essential fields/format fields/homepage fields/installer-menu-item fields/length fields/mail-address fields/maintainer fields/maintainer/team fields/multi-arch fields/multi-line fields/origin fields/package fields/package-relations fields/package-type fields/priority fields/recommended fields/required fields/section fields/source fields/standards-version fields/style fields/subarchitecture fields/terminal-control fields/trimmed fields/unknown fields/uploaders fields/urgency fields/vcs fields/version filename-length files/architecture files/banned files/banned/compiled-help files/banned/lenna files/bugs files/build-path files/compressed files/compressed/bz2 files/compressed/gz files/compressed/lz files/compressed/lzma files/compressed/lzo files/compressed/xz files/compressed/zip files/config-scripts files/contents files/date files/debug files/debug-packages files/desktop files/devhelp files/duplicates files/empty-directories files/empty-package files/encoding files/hard-links files/hierarchy/links files/hierarchy/merged-usr files/hierarchy/path-segments files/hierarchy/standard files/ieee-data files/includes files/init files/ld-so files/licenses files/locales files/missing files/multi-arch files/names files/non-free files/obsolete-paths files/ownership files/p11-kit files/pam files/permissions files/permissions/usr-lib files/pkgconfig files/privacy-breach files/scripts files/sgml files/special files/symbolic-links files/symbolic-links/broken files/unwanted files/usr-merge files/vcs fonts fonts/opentype fonts/postscript/type1 fonts/truetype foreign-operating-systems games group-checks huge-usr-share images images/filenames images/thumbnails includes/config-h init-d languages/fortran/gfortran languages/java languages/java/bytecode languages/javascript/embedded languages/javascript/nodejs languages/ocaml languages/perl languages/perl/perl5 languages/perl/yapp languages/php languages/php/embedded languages/php/pear languages/php/pear/embedded languages/python languages/python/bogus-prerequisites languages/python/dist-overrides languages/python/feedparser languages/python/homepage languages/python/obsolete languages/python/scripts languages/r languages/r/architecture languages/r/site-library languages/ruby languages/rust libraries/shared/obsolete linda lintian mailcap maintainer-scripts/adduser maintainer-scripts/generated md5sums menu-format menus mimeinfo modprobe nmu obsolete-sites origtar pe scripts shared-libs systemd systemd/tmpfiles team/pkg-js/deprecated team/pkg-js/testsuite team/pkg-js/vcs team/pkg-perl/testsuite team/pkg-perl/vcs team/pkg-perl/xs-abi testsuite triggers udev upstream-signature usrmerge vim vim/addons at /usr/share/lintian/bin/../lib/Lintian/Profile.pm line 606. Lintian::Profile::read_profile(Lintian::Profile=HASH(0x564511daa230), undef) called at /usr/share/lintian/bin/../lib/Lintian/Profile.pm line 372 Lintian::Profile::load(Lintian::Profile=HASH(0x564511daa230), undef, ARRAY(0x5645120b1938), 1) called at /usr/bin/lintian line 502 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#992674: marked as done (scipy breaks lmfit-py autopkgtest)
Your message dated Sat, 04 Sep 2021 09:18:32 +
with message-id
and subject line Bug#992674: fixed in lmfit-py 1.0.2-1
has caused the Debian Bug report #992674,
regarding scipy breaks lmfit-py autopkgtest
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.)
--
992674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scipy, lmfit-py
Control: found -1 scipy/1.7.1-1
Control: found -1 lmfit-py/1.0.1-6
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of scipy the autopkgtest of lmfit-py fails in
testing when that autopkgtest is run with the binary packages of scipy
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
scipy from testing1.7.1-1
lmfit-py from testing1.0.1-6
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of scipy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=scipy
https://ci.debian.net/data/autopkgtest/testing/amd64/l/lmfit-py/14750990/log.gz
=== FAILURES
===
___ test_ampgo_local_solver
minimizer_Alpine02 =
def test_ampgo_local_solver(minimizer_Alpine02):
"""Test AMPGO algorithm with local solver."""
kws = {'local': 'Nelder-Mead'}
msg = r'Method Nelder-Mead cannot handle constraints nor bounds'
with pytest.warns(RuntimeWarning, match=msg):
> out = minimizer_Alpine02.minimize(method='ampgo', **kws)
E Failed: DID NOT WARN. No warnings of type (,) was emitted. The list of emitted warnings is: [].
tests/test_ampgo.py:65: Failed
___ test_shgo_scipy_vs_lmfit
___
def test_shgo_scipy_vs_lmfit():
"""Test SHGO algorithm in lmfit versus SciPy."""
bounds = [(-512, 512), (-512, 512)]
result_scipy = scipy.optimize.shgo(eggholder, bounds, n=30,
sampling_method='sobol')
> assert len(result_scipy.xl) == 13
E assert 6 == 13
E+ where 6 = len(array([[ 324.99187533, 216.0475439 ],\n
[-105.87688985, 423.15324143],\n [-242.97923629,
274.38032063],\n [-506.25823477,6.3131022 ],\n [
91.00922754, -391.28375925],\n [-219.40615102, -244.06022436]]))
E+where array([[ 324.99187533, 216.0475439 ],\n
[-105.87688985, 423.15324143],\n [-242.97923629,
274.38032063],\n [-506.25823477,6.3131022 ],\n [
91.00922754, -391.28375925],\n [-219.40615102, -244.06022436]]) =
fun: -582.3062800548453\nfunl: array([-582.30628005,
-565.99778097, -559.78685655, -557.36868733,\n -426,\n
[-506.25823477,6.3131022 ],\n [ 91.00922754,
-391.28375925],\n [-219.40615102, -244.06022436]]).xl
tests/test_shgo.py:32: AssertionError
__ test_shgo_scipy_vs_lmfit_2
__
def test_shgo_scipy_vs_lmfit_2():
"""Test SHGO algorithm in lmfit versus SciPy."""
bounds = [(-512, 512), (-512, 512)]
result_scipy = scipy.optimize.shgo(eggholder, bounds, n=60, iters=5,
sampling_method='sobol')
> assert len(result_scipy.xl) == 39
E assert 74 == 39
E+ where 74 = len(array([[ 479.0454122 , 434.50588415],\n
[-465.69415426, 385.71669786],\n [ 347.32696865,
499.41539073],\n ...,\n [ -86.07840448, -6.42281733],\n [
47.99461331, -1.55083384],\n [ 31.65189625, -85.22716952]]))
E+where array([[ 479.0454122 , 434.50588415],\n
[-465.69415426, 385.71669786],\n [ 347.32696865,
499.41539073],\n ...,\n [ -86.07840448, -6.42281733],\n [
47.99461331, -1.55083384],\n [ 31.65189625, -85.22716952]]) =
fun: -955.2551521442906\nfunl: array([-955.25515214,
-894.57890039, -888.94912527,
