Bug#1012323: bullseye-pu: package nvidia-graphics-drivers-tesla-418/418.226.00-5~deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu With the tesla-418 driver series having reached EoL upstream, I'd like to update stable to the latest release from that branch along with all packaging fixes and add a NEWS entry for the EoL state. (As we had done with other EoL driver series in the past.) This is a rebuild of the package from sid. The packaging updates have reached stable already in the tesla-450, tesla-470, legacy-390xx and nvidia-graphics-drivers updates. The corresponding request for buster is #1009652 (for nvidia-graphics-drivers). Andreas ngd-tesla-418-418.226.00-5~deb11u1.diff.xz Description: application/xz
Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m
On 2022-06-04, Roman Lebedev wrote: > it would appear, diffoscope is failing when runing agains halide package: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/halide.html > > Unfortunately, i do not know what the more specific problem is. Some things just take a long time to run diffoscope, and tests.reproducible-builds.org only lets diffoscope run for 150m and then kills it to avoid very large unreproducible packages from eating all the resources. Options would be to run diffoscope on two builds of halide locally. The tool reprotest does this and runs diffoscope by default if it is installed. There is also beta.tests.reproducible-builds.org which may not have a diffoscope timeout, so you might be able to find diffoscope output for halide there. There may be improvements that could make diffoscope run faster and avoid the timeout, though I'm not sure this is a fundamental problem of diffoscope. I'll see if I can find you some diffoscope output for halide by running it on a fairly powerful machine I have access to... live well, vagrant signature.asc Description: PGP signature
Bug#1012322: bullseye-pu: package nvidia-graphics-drivers-tesla-460/460.106.00-5~deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu Hi, now that stable(-pu) has nvidia-graphics-drivers-tesla-470, we can turn nvidia-graphics-drivers-tesla-460 into transitional packages to aid switching to it. This is a rebuild of the package from unstable. I've split the diff into two incremental parts: 1.) the packaging changes that were also part of other updates in stable 2.) turning some packages into transitional packages depending on their tesla-470 counterparts The "old" content is still being shipped, but the dependencies on it and the alternative to access it is being removed. This was the least intrusive way. Most of the then useless old packages should be autoremovable after installation. Andreas ngd-tesla-460-460.106.00-5~deb11u1.transitional.diff.xz Description: application/xz ngd-tesla-460-460.106.00-5~deb11u1.packaging.diff.xz Description: application/xz
Bug#1011646: libthrust: autopkgtest: please be more gentle on ci.d.n infrastructure
Hi Andreas, On 04-06-2022 05:49, Andreas Beckmann wrote: On 02/06/2022 21.53, Paul Gevers wrote: On 02-06-2022 21:45, Andreas Beckmann wrote: OK. Could you give -5 a try? That has already happened automatically, as the block has been removed. arm64 still times out on the cuda parts ... :-( waiting for the ppc64el run ... The ppc64el one finished while I was checking. It also timed out and took in total 8 hours. BTW, nvidia-cuda-toolkit currently seems stuck: autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Regression Can you hint against that? Yes, but only because of the explanation you gave below (too big source). nvidia-cuda-toolkit All ppc64el * test suite fails to start properly (disk space in unstable) Sorry, I forgot to file a bug about that. Fetching the source package and unpacking it needs > 20 GB ... Hmm, I think that could be something that autopkgtest could check before starting, apt knows about this, doesn't it? That can't even be prevented with an Architecture setting. Ack, hence not blaming nvidia-cuda-toolkit anymore. PS: I've updated src:cub and reduced the autopkgtest by 50%. It still fails early on arm64/ppc64el (due to some char/uchar mess), I'll take that upstream once I'm running on the latest upstream release. Ack. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1011646: libthrust: autopkgtest: please be more gentle on ci.d.n infrastructure
On 02/06/2022 21.53, Paul Gevers wrote: > On 02-06-2022 21:45, Andreas Beckmann wrote: >> OK. Could you give -5 a try? > > That has already happened automatically, as the block has been removed. arm64 still times out on the cuda parts ... :-( waiting for the ppc64el run ... >> BTW, nvidia-cuda-toolkit currently seems stuck: >> >> autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: >> Regression Can you hint against that? > nvidia-cuda-toolkit All ppc64el * test suite fails to > start properly (disk space in unstable) > > Sorry, I forgot to file a bug about that. Fetching the source package and unpacking it needs > 20 GB ... That can't even be prevented with an Architecture setting. I've now copied the autopkgtest from src:nvidia-cuda-toolkit to src:pycuda - all we need is an installation of nvidia-cuda-toolkit, and that is < 5 GB. If that works, I'll drop the autopkgtest from src:nvidia-cuda-toolkit again. (pycuda didn't have any tests, yet, (its testsuite would want to run cuda code on a gpu), and the new test is fast enough to be run on salsa-ci) Andreas PS: I've updated src:cub and reduced the autopkgtest by 50%. It still fails early on arm64/ppc64el (due to some char/uchar mess), I'll take that upstream once I'm running on the latest upstream release.
Bug#1012018: texlive-bin: FTBFS during separate binary-indep build
On 04/06/2022 00.04, Hilmar Preuße wrote: > We are far from being perfect, i.e. we still do a full build for arch > "all" just to get 2 transitional packages, but this may be sorted out > later. Maybe add an empty override_dh_auto_build-indep: target? Andreas
Bug#978119: pdf2djvu: [INTL:de] updated German po file translation
Hello Jakub, On Fri, Jun 03, 2022 at 08:24:44PM +0200, Jakub Wilk wrote: > Upstream maintainer speaking here. > > * Helge Kreutzmann , 2020-12-26, 09:17: > > Please find the updated German po file translation for pdf2djvu > > attached. > > Thanks, applied upstream: > https://github.com/jwilk/pdf2djvu/commit/2fd1a7bfb19ce0d8 Thanks. > > If you update your template, please use > > 'msgfmt --statistics ' > > to check the po-files for fuzzy or untranslated strings. > > > > If there are such strings, please contact me so I can update the German > > translation. > > I have a script for nudging translators (private/request-translations), but > it uses the Last-Translator field from the PO header, which currently reads: > > > "Last-Translator: Chris Leick \n" > > Do you want me to update the header to put your name and address in it? Yes, for now this probably would be the best solution, as Chris has little time at the moment. I put him in CC so he is aware and we might change the roles back laer again. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
Bug#1012321: Acknowledgement (interpreter incorrectly set to /usr/lib/binfmt-support/run-detectors)
After a reboot of the test VM, I now get $ grep detector /proc/sys/fs/binfmt_misc/* cli:interpreter /usr/lib/binfmt-support/run-detectors jarwrapper:interpreter /usr/lib/binfmt-support/run-detectors llvm-11-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-12-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-13-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-14-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-15-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors wine:interpreter /usr/lib/binfmt-support/run-detectors Now it's additionally set for wine and llvm-11-runtime.binfmt OpenPGP_signature Description: OpenPGP digital signature
Bug#1012321: interpreter incorrectly set to /usr/lib/binfmt-support/run-detectors
Package: binfmt-support Version: 2.2.2-1 Severity: normal I just ran the following command apt install --no-install-recommends binfmtc hatari jarwrapper llvm-11-runtime llvm-12-runtime llvm-13-runtime llvm-14-runtime llvm-15-runtime love mono-runtime python2.7-minimal python3.10-minimal python3.9-minimal sbcl wine-binfmt # grep detector /usr/share/binfmts/* /usr/share/binfmts/cli:detector /usr/lib/cli/binfmt-detector-cli /usr/share/binfmts/jarwrapper:detector /usr/bin/jardetector $ grep detector /proc/sys/fs/binfmt_misc/* cli:interpreter /usr/lib/binfmt-support/run-detectors jarwrapper:interpreter /usr/lib/binfmt-support/run-detectors llvm-12-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-13-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-14-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors llvm-15-runtime.binfmt:interpreter /usr/lib/binfmt-support/run-detectors Why is for llvm-1[2345]-runtime.binfmt the interpreter set to /usr/lib/binfmt-support/run-detectors when the actual config does not set any detector? Is that a bug or am I missing something? Michael -- 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.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 binfmt-support depends on: ii init-system-helpers 1.63 ii libc62.33-7 ii libpipeline1 1.5.6-1 ii lsb-base 11.2 binfmt-support recommends no packages. binfmt-support suggests no packages. -- no debconf information
Bug#1012320: materialize: build-depends on non-existing libjs-anime
Source: materialize Version: 1.1.0~alpha+ds-1 Severity: serious Usertags: edos-uninstallable Hi, materialize build-depends on libjs-anime, which does not exist in sid. -Ralf.
Bug#982456: lintian: systemd SystemCallArchitectures directive incompatible with M-A:foreign
Am 04.06.22 um 00:45 schrieb Michael Biebl: On Wed, 10 Feb 2021 13:42:59 +0100 Guillem Jover wrote: Package: lintian Version: 2.104.0 Severity: wishlist Hi! The systemd unit file directive SystemCallArchitectures is incompatible with Multi-Arch:foreign markings in a package, as that means once you install such foreign package, systemd will refuse to let it run. Only if systemd and the architecture of the service mismatch. You can e.g. run a i386 service on an amd64 system if systemd is also i386. Btw, you can also install say foreign arm64 binaries on and amd64 system which will also refuse to run. There is nothing in dpkg which prevents that. OpenPGP_signature Description: OpenPGP digital signature
Bug#1008279: Alternative fix using getent
Attached is a similar fix we're applying in Ubuntu, except it uses getent rather than id, which seems to be a typical way for solving this type of need. >From 5b6f1ddbb759fad768d64a26e42427617910f9f8 Mon Sep 17 00:00:00 2001 From: Bryce Harrington Date: Wed, 18 May 2022 17:16:20 -0700 Subject: [PATCH] * clamav-base.postinst.in: Quell warning from check for clamav user (LP: #1920217) Signed-off-by: Bryce Harrington --- debian/clamav-base.postinst.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/clamav-base.postinst.in b/debian/clamav-base.postinst.in index 89c116f5..f3d1da9b 100644 --- a/debian/clamav-base.postinst.in +++ b/debian/clamav-base.postinst.in @@ -32,7 +32,7 @@ case "$1" in # Set up the clamav user on new install if [ -z "$2" ]; then -if ! id clamav; then +if ! getent passwd clamav >/dev/null; then adduser --system --no-create-home --quiet \ --disabled-password --disabled-login \ --shell /bin/false --group --home /var/lib/clamav clamav -- 2.25.1
Bug#982456: lintian: systemd SystemCallArchitectures directive incompatible with M-A:foreign
On Wed, 10 Feb 2021 13:42:59 +0100 Guillem Jover wrote: Package: lintian Version: 2.104.0 Severity: wishlist Hi! The systemd unit file directive SystemCallArchitectures is incompatible with Multi-Arch:foreign markings in a package, as that means once you install such foreign package, systemd will refuse to let it run. Only if systemd and the architecture of the service mismatch. You can e.g. run a i386 service on an amd64 system if systemd is also i386. Please tag this as an error. If such a check is added, warning or informational would be more appropriate. OpenPGP_signature Description: OpenPGP digital signature
Bug#1012279: php-horde-turba: CVE-2022-30287
Hello, here is draft for MR: https://salsa.debian.org/horde-team/php-horde-turba/-/merge_requests/1 I would look after it next time on sunday evening. @Mike: Can you please review it? Best Regards, Juri Grabowski
Bug#1012319: RFS: texlive-bin/2022.20220321.62855-4 [RC] -- TeX Live: LuaJIT, modified for use with LuaJITTeX (development part)
Package: sponsorship-requests Severity: important Dear mentors, My GPG key has expired, hence I need a sponsor for this upload. I am looking for a sponsor for my package "texlive-bin": * Package name: texlive-bin Version : 2022.20220321.62855-4 Upstream Author : [fill in name and email of upstream] * URL : https://www.tug.org/texlive/ * License : [fill in] * Vcs : https://github.com/debian-tex/texlive-bin Section : tex The source builds the following binary packages: texlive-binaries - Binaries for TeX Live libkpathsea6 - TeX Live: path search library for TeX (runtime part) libkpathsea-dev - TeX Live: path search library for TeX (development part) libptexenc1 - TeX Live: pTeX encoding library libptexenc-dev - TeX Live: ptex encoding library (development part) libsynctex2 - TeX Live: SyncTeX parser library libsynctex-dev - TeX Live: SyncTeX parser library (development part) libtexlua53 - transitional package (lib) libtexlua53-5 - TeX Live: Lua 5.3, modified for use with LuaTeX libtexlua53-dev - transitional package (dev) libtexlua-dev - TeX Live: Lua 5.3, modified for use with LuaTeX (development part) libtexluajit2 - TeX Live: LuaJIT, modified for use with LuaJITTeX libtexluajit-dev - TeX Live: LuaJIT, modified for use with LuaJITTeX (development part) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/texlive-bin/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/t/texlive-bin/texlive-bin_2022.20220321.62855-4.dsc Changes since the last upload: texlive-bin (2022.20220321.62855-4) unstable; urgency=medium . * Separate "install arch" from "install indep" target (Closes: #1012018). Regards, -- Hilmar Preusse
Bug#1007586: libexpect-perl: please consider upgrading to 3.0 source format
Version: 1.35-1 On Tue, 15 Mar 2022 08:52:03 +0100, Lucas Nussbaum wrote: > This package is among the few (1.9%) that still use source format 1.0 in > bookworm. Please upgrade it to source format 3.0, as (1) this format has many > advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2) > this contributes to standardization of packaging practices. Fixed in 1.35-1, closing with this version. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1012018: texlive-bin: FTBFS during separate binary-indep build
Am 28.05.2022 um 21:53 teilte Andreas Beckmann mit: Hi Andreas, Looks like you need to move some bits that are irrelevant for the binary-indep build to a override_dh_install-arch (or probably better execute_after_dh_install-arch) target. Many thanks for the pointer! I could separate the install indep and the install arch target a little better and therefore (hopefully) solve the issue. We are far from being perfect, i.e. we still do a full build for arch "all" just to get 2 transitional packages, but this may be sorted out later. Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m
Package: diffoscope Version: 214 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it would appear, diffoscope is failing when runing agains halide package: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/halide.html Unfortunately, i do not know what the more specific problem is. Roman. - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages diffoscope depends on: pn diffoscope-minimal Versions of packages diffoscope recommends: pn abootimg ii acl2.3.1-1 pn androguard pn apksigner pn apktool pn binutils-multiarch ii bzip2 1.0.8-5 pn caca-utils pn colord pn db-util pn default-jdk-headless | default-jdk | java-sdk pn device-tree-compiler pn docx2txt ii e2fsprogs 1.46.5-2 pn enjarify ii ffmpeg 10:4.4.2-dmo5 pn fontforge-extras pn fp-utils ii genisoimage9:1.1.11-3.2 ii gettext0.21-6 pn ghc ii ghostscript9.56.1~dfsg-1 pn giflib-tools pn gnumeric ii gnupg 2.2.35-2 ii gnupg-utils2.2.35-2 pn hdf5-tools ii imagemagick-6.q16 [imagemagick]8:6.9.11.60+dfsg-1.3+b2 pn jsbeautifier ii libarchive-tools 3.6.0-1 pn libxmlb-dev ii llvm 1:15.0-55~20220203224054.8 ii lz4 [liblz4-tool] 1.9.3-2 pn mono-utils pn ocaml-nox pn odt2txt pn oggvideotools ii openssh-client 1:9.0p1-1+b1 ii openssl3.0.3-5 pn pgpdump ii poppler-utils 22.02.0-3 pn procyon-decompiler pn python3-argcomplete pn python3-binwalk ii python3-debian 0.1.44 ii python3-defusedxml 0.7.1-1 pn python3-guestfs pn python3-jsondiff pn python3-pdfminer pn python3-progressbar pn python3-pypdf2 pn python3-pyxattr pn python3-rpm pn python3-tlsh pn r-base-core pn radare2 ii rpm2cpio 4.17.0+dfsg1-4 pn sng ii sqlite33.38.5-1 pn squashfs-tools pn tcpdump pn u-boot-tools ii unzip 6.0-26 ii vim-common 2:8.2.4793-1 pn wabt pn xmlbeans ii xxd2:8.2.4793-1 ii xz-utils 5.2.5-2.1 ii zip3.0-12 ii zstd 1.5.2+dfsg-1 Versions of packages diffoscope suggests: ii libjs-jquery 3.6.0+dfsg+~3.5.13-1 -BEGIN PGP SIGNATURE-
Bug#1000626: Bug#1000627: apache2: missing dependency setting
Binding to a specific interface is not the default Apache or OpenSSH configuration. It can thus be argued that if the bug reporter want's to run such a configuration he can easily create a corresponding drop-in via systemctl edit apache2.service or systemctl edit ssh.service containing [Unit] Wants=network-online.target After=network-online.target I'd like to refer to https://systemd.io/NETWORK_ONLINE/ as well. Especially to "Should network-online.target be used?" which suggest better and more robust options then using network-online.target Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1007097: iwd forcefully enabled randomize mac address, cannot disable via /etc/iwd/main.conf
Hi, Could it be that your network provisioning file (/var/lib/iwd/.psk) has: [Settings] AlwaysRandomizeAddress=true According to the man pages this should only be honored if main.conf has AddressRandomization=network... BUT after poking around I identified a bug surrounding that. A fix should be merged soon. In the mean time, if you indeed have AlwaysRandomizeAddress=true, set that to false and it should use the perminant hardware address always. Thanks, James
Bug#981285: Please move fdk-aac to main
> > [1]https://www.gnu.org/licenses/license-list.html#fdk > This clearly states that the FDK license is incompatible with the GPL. > For pipewire that should be okay, because it is Expat, if nothing makes > the whole thing LGPL. For gstreamer and pulseaudio it's pretty much not > okay, because they are some form of GPL. Fedora's official position is that their copy of fdk-aac to be GPL compatible. https://lists.fedoraproject.org/archives/list/le...@lists.fedoraproject.org/thread/OVW25JRWOKOLVMW3XGUX7E4OXFUR2RCG/ Fedora's fdk-aac copy does not include newer AAC features which might be patent-encumbered. https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/F64JBJI2IZFT2A5QDXGHNMPALCQIVJAX/ fdk-aac is of interest to me because gnome-remote-desktop 43 will depend on it for audio forwarding to remote clients. gnome-remote-desktop is in main and so we want fdk-aac to be in main too so that all of gnome-remote-desktop's features work as expected. Thank you, Jeremy Bicha
Bug#1012317: ITP: golang-github-flowstack-go-jsonschema -- Go JSON Schema parser and validator
Package: wnpp Severity: wishlist Owner: Domenico Andreoli * Package name: golang-github-flowstack-go-jsonschema Version : 0.1.1-1 Upstream Author : FlowStack * URL : https://github.com/flowstack/go-jsonschema * License : Expat Programming Lang: Go Description : Go JSON Schema parser and validator The very nice gojsonschema was missing some features and we needed some internal functionality, that was hard to build on top of gojsonschema. . This module uses the excellent jsonparser, which is wy faster than Go's builtin parser.
Bug#1012316: dahdi-dkms: fails to build modules for Linux 5.17
Package: dahdi-dkms Version: 1:2.11.1.0.20170917~dfsg-7.5 Severity: serious DKMS make.log for dahdi-2.11.1.0.20170917~dfsg-7.5 for kernel 5.17.0-3-amd64 (x86_64) Fri Jun 3 20:10:19 UTC 2022 make -C /lib/modules/5.17.0-3-amd64/build KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/include DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-5.17.0-3-amd64' CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/apilib/bt/octapi_bt0.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/apilib/llman/octapi_llman.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/oct612x-user.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/oct612x/oct612x.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/wct4xxp/base.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/wct4xxp/vpm450m.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/wct4xxp/wct4xxp.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/wctc4xxp/base.o /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/wctc4xxp/base.c: In function 'wctc4xxp_net_register': /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.5/build/drivers/dahdi/wctc4xxp/base.c:678:22: warning: passing argument 1 of 'memcpy' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 678 | memcpy(netdev->dev_addr, our_mac, sizeof(our_mac)); |~~^~ In file included from /usr/src/linux-headers-5.17.0-3-common/include/linux/string.h:253, from /usr/src/linux-headers-5.17.0-3-common/include/linux/bitmap.h:11, from /usr/src/linux-headers-5.17.0-3-common/include/linux/cpumask.h:12, from /usr/src/linux-headers-5.17.0-3-common/arch/x86/include/asm/cpumask.h:5, from /usr/src/linux-headers-5.17.0-3-common/arch/x86/include/asm/msr.h:11, from
Bug#1012154: binfmt-support.service errors with "unable to close /proc/sys/fs/binfmt_misc/register: File exists"
Am 02.06.22 um 21:52 schrieb Colin Watson: Control: tag -1 fixed-upstream On Thu, Jun 02, 2022 at 01:01:11PM +0200, Michael Biebl wrote: Since we only need to ensure, that systemd-binfmt.service and binfmt-support.service do not run concurrently (and both trying to access /proc/sys/fs/binfmt_misc/register), we simply need to apply a proper ordering. Thankfully, this is rather simple and the attached patch is even more minimal then the previous one. I chose to run binfmt-support.service after systemd-binfmt.service, as the former is pulled in via multi-user.target and the latter via sysinit.target. Thanks, makes sense. I've pushed this patch upstream (https://gitlab.com/cjwatson/binfmt-support/-/commit/54f0e1af8a). Thank you, Colin! OpenPGP_signature Description: OpenPGP digital signature
Bug#1011609: bogl-bterm: [PATCH] Several improvements
Control: tags -1 + pending Zhang Boyang, le ven. 03 juin 2022 17:04:26 +0900, a ecrit: > Changes in [PATCH V4]: > > Tiny improvement: detect 8K+ monitors and assign 8x scale factor for them. Applied, thanks! Samuel
Bug#1012315: waitress: CVE-2022-31015
Source: waitress Version: 2.1.1-2 Severity: important Tags: security upstream Forwarded: https://github.com/Pylons/waitress/issues/374 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for waitress. CVE-2022-31015[0]: | Waitress is a Web Server Gateway Interface server for Python 2 and 3. | Waitress versions 2.1.0 and 2.1.1 may terminate early due to a thread | closing a socket while the main thread is about to call select(). This | will lead to the main thread raising an exception that is not handled | and then causing the entire application to be killed. This issue has | been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to | close the socket. Instead, that is always delegated to the main | thread. There is no work-around for this issue. However, users using | waitress behind a reverse proxy server are less likely to have issues | if the reverse proxy always reads the full response. 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-2022-31015 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31015 [1] https://github.com/Pylons/waitress/issues/374 [2] https://github.com/Pylons/waitress/security/advisories/GHSA-f5x9-8jwc-25rw [3] https://github.com/Pylons/waitress/commit/4f6789b035610e0552738cdc4b35ca809a592d48 Please adjust the affected versions in the BTS as needed, can you confirm if the assessment that the issue is introduced in 2.1.0 upstream only? Regards, Salvatore
Bug#1012314: maven-shared-utils: CVE-2022-29599
Source: maven-shared-utils Version: 3.3.0-1 Severity: important Tags: security upstream Forwarded: https://issues.apache.org/jira/browse/MSHARED-297 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for maven-shared-utils. CVE-2022-29599[0]: | In Apache Maven maven-shared-utils prior to version 3.3.3, the | Commandline class can emit double-quoted strings without proper | escaping, allowing shell injection attacks. 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-2022-29599 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29599 [1] https://issues.apache.org/jira/browse/MSHARED-297 [2] https://github.com/apache/maven-shared-utils/pull/40 [3] https://github.com/apache/maven-shared-utils/commit/f751e614c09df8de1a080dc1153931f3f68991c9 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1012313: netselect-apt: Security updates format change for Bullseye
Package: netselect-apt Version: 0.3.ds1-29 Severity: important -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/2 CPU threads) 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 netselect-apt depends on: ii curl 7.74.0-1.3+deb11u1 ii netselect 0.3.ds1-29 ii wget 1.21-1+deb11u1 netselect-apt recommends no packages. Versions of packages netselect-apt suggests: ii dpkg-dev 1.20.10 -- no debconf information Ran the command and mirror selection was fine, no errors. $sudo netselect-apt -c US -o temp.list $cat temp.list # Debian packages for stable deb http://mirror.cogentco.com/debian/ stable main contrib # Uncomment the deb-src line if you want 'apt-get source' # to work with most packages. # deb-src http://mirror.cogentco.com/debian/ stable main contrib # Security updates for stable deb http://security.debian.org/ stable/updates main contrib Moved temp.list to /etc/apt/sources.list and an update gave errors: $sudo apt update Get:1 http://mirror.cogentco.com/debian stable InRelease [116 kB] Get:2 http://mirror.cogentco.com/debian stable/main amd64 Packages [8,182 kB] Ign:3 http://security.debian.org stable/updates InRelease Err:4 http://security.debian.org stable/updates Release 404 Not Found [IP: 2a04:4e42:78::644 80] Get:5 http://mirror.cogentco.com/debian stable/main Translation-en [6,241 kB] Get:6 http://mirror.cogentco.com/debian stable/contrib amd64 Packages [50.5 kB] Get:7 http://mirror.cogentco.com/debian stable/contrib Translation-en [46.9 kB] Reading package lists... Done E: The repository 'http://security.debian.org stable/updates Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. The format has apparently changed as of Bullseye stable to be stable-security instead of stable/updates https://debian-handbook.info/browse/en-US/stable/apt.html#sect.apt-sources.list.testing Changing the last line of sources.list to deb http://security.debian.org/ stable-security main contrib fixed the problem.
Bug#1012312: coreutils: tr: confusing error message w.r.t. backwards c-c set points at nonconformant behaviour
Package: coreutils Version: 8.32-4.1 Severity: minor Dear Maintainer, LC_ALL=POSIX tr '\049-!' '0' fails with tr: range-endpoints of '9-!' are in reverse collating sequence order but POSIX.1-2008/2018 says If either or both of the range endpoints are octal sequences of the form \octal, this shall represent the range of specific coded values between the two range endpoints, inclusive. so if coreutils is /actually/ trying to generate a locale-dependent collating sequence: that's invalid (well, in the POSIX locale; it's unspecified in others) if it isn't: the error message is wrong. Similarly: the error is confusing enough as-is even when it's right (note how it presents the decoded sequence, and very helpfully describes it as "range-endpoints in reverse collating sequence order", which probably means something to someone, but it's an insane way of writing '\049 < !'). Best, наб -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: amd64, i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 coreutils depends on: ii libacl1 2.3.1-1 ii libattr1 1:2.5.1-1 ii libc62.33-7 ii libgmp10 2:6.2.1+dfsg-3 ii libselinux1 3.3-1+b4 coreutils recommends no packages. coreutils suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#978119: pdf2djvu: [INTL:de] updated German po file translation
Hi Helge! Upstream maintainer speaking here. * Helge Kreutzmann , 2020-12-26, 09:17: Please find the updated German po file translation for pdf2djvu attached. Thanks, applied upstream: https://github.com/jwilk/pdf2djvu/commit/2fd1a7bfb19ce0d8 If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. I have a script for nudging translators (private/request-translations), but it uses the Last-Translator field from the PO header, which currently reads: "Last-Translator: Chris Leick \n" Do you want me to update the header to put your name and address in it? -- Jakub Wilk
Bug#1012280: fixed in cgal 5.4-3
Hi Joachim, Thanks for the quick update! Best, François signature.asc Description: This is a digitally signed message part
Bug#979115: 660L trash container casters-high quality-save time and cost
Dear Customer, I am Meguel of MIYA METAL CHINA. Are you looking for 4 wheelie trash container caster wheels ? Our trash container caster wheels have strictly passed EN 840-5 standard testing. Samples are availble for check. Are you interested in it? Yours faithfully, Meguel Zheung Overseas Marketing Manager A028, 3rd Floor, No. 1165-1185, Xihuan Road, Shiqiao Street, Panyu District, Guangzhou, China. Whatsapp/Wechat:+86 186 6482 2751
Bug#1012298: linux-image-5.17.0-1-amd64: New partition doesn't appear in /dev anymore with kernel 5.17 (repro script included)
On Fri, Jun 03, 2022 at 03:47:39AM -0400, Michael Schaller wrote:
> # Associate a loop device with the raw disk image.
> losetup --find "${img}"
This ought to use "--partscan". Otherwise your device is not partioned.
Bastian
--
There's a way out of any cage.
-- Captain Christopher Pike, "The Menagerie" ("The Cage"),
stardate unknown.
Bug#1012311: libc6: invalid debug symbol for optind
Package: libc6
Version: 2.31-13+deb11u3
Severity: normal
Dear Maintainer,
Here is a simple example program:
#include
int main()
{
optind = 2;
}
I compiled it with 'gcc -g -O0' and ran it through gdb:
(gdb) b main
Breakpoint 1 at 0x1129: file main.c, line 5.
(gdb) r
Starting program: /home/marionm/test/optind/a.out
Breakpoint 1, main () at main.c:5
5 optind = 2;
(gdb) n
6 }
(gdb) p optind
$1 = 1
(gdb) p
$2 = (int *) 0x77fa1344
(gdb) disassemble
Dump of assembler code for function main:
0x5125 <+0>: push %rbp
0x5126 <+1>: mov%rsp,%rbp
0x5129 <+4>: movl $0x2,0x2ef5(%rip)#
0x8028
0x5133 <+14>:mov$0x0,%eax
=> 0x5138 <+19>:pop%rbp
0x5139 <+20>:ret
End of assembler dump.
(gdb)
We can see that the address used by GDB when accessing 'optind' is not the same
as the one present in the assembly code (0x77fa1344 vs 0x8028).
When running this experiment on Debian with the packaged gdb version 10 and 11,
we get the unexpected behavior described above. The same test run on Fedora with
gdb version 12 results in the expected behavior of seeing the same address on
both sides.
I originally made the silly mistake of believing that 'optind' provided the
index of the current option being processed, while it actually contains the next
option to be processed. When debugging, gdb would show me a value of 1 in optind
(as I wrongly expected) instead of the real value of 3, which led to a difficult
debugging experience.
This issue might also be caused by gdb instead of libc but I don't have
a deep enough understanding of the problem to ensure one or the other.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/12 CPU threads; PREEMPT)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libc6 depends on:
ii libcrypt1 1:4.4.18-4
ii libgcc-s1 10.2.1-6
Versions of packages libc6 recommends:
ii libidn2-0 2.3.0-5
pn libnss-nis
pn libnss-nisplus
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.77
pn glibc-doc
ii libc-l10n 2.31-13+deb11u3
ii locales2.31-13+deb11u3
-- debconf information:
glibc/kernel-not-supported:
glibc/disable-screensaver:
glibc/upgrade: true
glibc/restart-services:
libraries/restart-without-asking: false
glibc/kernel-too-old:
glibc/restart-failed:
Bug#1012298: linux-image-5.17.0-1-amd64: New partition doesn't appear in /dev anymore with kernel 5.17 (repro script included)
Control: forwarded -1
https://lore.kernel.org/linux-block/CALt099JajMVCwHgdRdRSF1uhNC=eo+ttq4t4bg8qdwuo3ux...@mail.gmail.com/T/#u
On Friday, 3 June 2022 15:24:15 CEST Michael Schaller wrote:
> I agree. I've tested patch
> https://lore.kernel.org/r/20220527055806.1972352-1-...@lst.de and it
> fixes the issue.
> However the patch doesn't cleanly apply to 5.18.1 and so I've
> requested a backport to 5.17 and 5.18.
I've made an attempt at backporting it to 5.18.1 and now 'debian/rules orig'
succeeds. I have not tried building a (Debian) kernel with it or verified that
it also fixes the issue with a 5.18.1 kernel.>From b9684a71fca793213378dd410cd11675d973eaa1 Mon Sep 17 00:00:00 2001
From: Christoph Hellwig
Date: Fri, 27 May 2022 07:58:06 +0200
Subject: block, loop: support partitions without scanning
Historically we did distinguish between a flag that surpressed partition
scanning, and a combinations of the minors variable and another flag if
any partitions were supported. This was generally confusing and doesn't
make much sense, but some corner case uses of the loop driver actually
do want to support manually added partitions on a device that does not
actively scan for partitions. To make things worsee the loop driver
also wants to dynamically toggle the scanning for partitions on a live
gendisk, which makes the disk->flags updates non-atomic.
Introduce a new GD_SUPPRESS_PART_SCAN bit in disk->state that disables
just scanning for partitions, and toggle that instead of GENHD_FL_NO_PART
in the loop driver.
Fixes: 1ebe2e5f9d68 ("block: remove GENHD_FL_EXT_DEVT")
Reported-by: Ming Lei
Signed-off-by: Christoph Hellwig
Reviewed-by: Ming Lei
Link: https://lore.kernel.org/r/20220527055806.1972352-1-...@lst.de
Signed-off-by: Jens Axboe
---
block/genhd.c | 2 ++
drivers/block/loop.c | 8
include/linux/blkdev.h | 1 +
3 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/block/genhd.c b/block/genhd.c
index 36532b9318419..27205ae47d593 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -385,6 +385,8 @@ int disk_scan_partitions(struct gendisk *disk, fmode_t mode)
if (disk->flags & (GENHD_FL_NO_PART | GENHD_FL_HIDDEN))
return -EINVAL;
+ if (test_bit(GD_SUPPRESS_PART_SCAN, >state))
+ return -EINVAL;
if (disk->open_partitions)
return -EBUSY;
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 01b4e257016a1..121f96dfc23eb 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1066,7 +1066,7 @@ static int loop_configure(struct loop_device *lo, fmode_t mode,
lo->lo_flags |= LO_FLAGS_PARTSCAN;
partscan = lo->lo_flags & LO_FLAGS_PARTSCAN;
if (partscan)
- lo->lo_disk->flags &= ~GENHD_FL_NO_PART;
+ clear_bit(GD_SUPPRESS_PART_SCAN, >lo_disk->state);
loop_global_unlock(lo, is_loop);
if (partscan)
@@ -1185,7 +1185,7 @@ static void __loop_clr_fd(struct loop_device *lo, bool release)
*/
lo->lo_flags = 0;
if (!part_shift)
- lo->lo_disk->flags |= GENHD_FL_NO_PART;
+ set_bit(GD_SUPPRESS_PART_SCAN, >lo_disk->state);
mutex_lock(>lo_mutex);
lo->lo_state = Lo_unbound;
mutex_unlock(>lo_mutex);
@@ -1295,7 +1295,7 @@ loop_set_status(struct loop_device *lo, const struct loop_info64 *info)
if (!err && (lo->lo_flags & LO_FLAGS_PARTSCAN) &&
!(prev_lo_flags & LO_FLAGS_PARTSCAN)) {
- lo->lo_disk->flags &= ~GENHD_FL_NO_PART;
+ clear_bit(GD_SUPPRESS_PART_SCAN, >lo_disk->state);
partscan = true;
}
out_unlock:
@@ -2045,7 +2045,7 @@ static int loop_add(int i)
* userspace tools. Parameters like this in general should be avoided.
*/
if (!part_shift)
- disk->flags |= GENHD_FL_NO_PART;
+ set_bit(GD_SUPPRESS_PART_SCAN, >state);
atomic_set(>lo_refcnt, 0);
mutex_init(>lo_mutex);
lo->lo_number = i;
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index afad3d1d0dac0..691b4c15b8ce1 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -147,6 +147,7 @@ struct gendisk {
#define GD_DEAD2
#define GD_NATIVE_CAPACITY 3
#define GD_ADDED 4
+#define GD_SUPPRESS_PART_SCAN 5
struct mutex open_mutex; /* open/close mutex */
unsigned open_partitions; /* number of open partitions */
--
2.30.2
signature.asc
Description: This is a digitally signed message part.
Bug#1012310: libexpect-perl: Tests fail on i386 in Ubuntu
Package: libexpect-perl
Version: 1.35-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Dear Maintainer,
libexpect-perl needs to be marked as Multi-Arch: foreign to
resolve test failures on i386. It is causing failures for
reverse dependencies, such as mysql-8.0.
* Mark as Multi-Arch: foreign to resolve i386 test failues
Thanks for considering the patch.
-- System Information:
Debian Release: bookworm/sid
APT prefers kinetic
APT policy: (500, 'kinetic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-27-generic (SMP w/32 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
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
diff -Nru libexpect-perl-1.35/debian/control libexpect-perl-1.35/debian/control
--- libexpect-perl-1.35/debian/control 2022-05-27 14:49:35.0 -0500
+++ libexpect-perl-1.35/debian/control 2022-06-01 16:59:37.0 -0500
@@ -15,6 +15,7 @@
Package: libexpect-perl
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends},
${perl:Depends},
libio-pty-perl,
Bug#1010595: Please make xsimd available on all platforms
Hi again, To sum up upstream's answer [1]: xsimd does not support a fallback mechanism anymore, and pythran should work fine without xsimd. On the ARM side, armel is not supported, as xsimd requires __ARM_ARCH >= 7 [2]. The only solution I see is to package xsimd 8.1.0 and restrict it to amd64, arm64, armhf and i386: this is what I just commited to salsa. Let me know if you have a better solution, otherwise I'll upload the version currently in salsa to unstable. [1] https://github.com/xtensor-stack/xsimd/issues/756#issuecomment-1142521979 [2] https://github.com/xtensor-stack/xsimd/blob/8.1.0/include/xsimd/config/xsimd_config.hpp#L247-L273 Cheers, -- Julien Le 30/05/2022 à 10:28, Julien Lamy a écrit : Hi Ole, I've looked at the code of xsimd 8, and it seems that the fallback has been replaced by another mechanism; however my tests on a mipsel porterbox fail to compile simple programs. I've taken the issue upstream (https://github.com/xtensor-stack/xsimd/issues/756) to see what is the status of the fallback mechanism. Cheers, OpenPGP_signature Description: OpenPGP digital signature
Bug#1012278: kodi web interface does not work
That web interface is so broken that I will be packaging a modern one under the v20 transition. Apart from the files missing, it also has no support for many jsonrpc calls introduced in v18, v19 and v20. For bullseye, it all will be available from a backport repo because I can not add new packages to stable according to Debian Policy. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
Bug#1012028: RFS: dirdiff/2.1-9 [ITA] -- Display and merge changes between two directory trees
Control: tags -1- moreinfo > This has to go to the commit where you introduce the patch. adjusted. > I do not understand this entry at all. Please think of explaining the patch > better. Aslo, there is no "f" word in English. adjusted. > typo in d/copyright (missing h) > Please say "Include the name of the new maintainer" > Please rebase this instead of adding a fixup commit. adjusted > Please do not reintroduce salsa-ci.yml that I have just deleted. This is the > default file that you can just set in the CI settings as > recipes/debian.yml@salsa-ci-team/pipeline. I guess this happened > with your > rebase. adjuste Nilson F. Silva De: Nilson Silva Enviado: quarta-feira, 1 de junho de 2022 23:25 Para: Bastian Germann Assunto: RE: Bug#1012028: RFS: dirdiff/2.1-9 [ITA] -- Display and merge changes between two directory trees Control: tags -1- moreinfo > Please do not create a new repo for working on a package that already has a > Vcs repo. I> nstead, fork it, work on it and when this RFS is sponsored, the sponsor will take back t> he changes to the original repo and maybe grant you access to it. Created and made changes. Thanks for the teaching. > So please recreate your repo as a fork and reapply your changes on it. > Please untag moreinfo when you are done with that. OK. Is ready. I hope it's right. Nilson F. Silva De: Bastian Germann Enviado: terça-feira, 31 de maio de 2022 04:08 Para: Nilson Silva ; 1012...@bugs.debian.org <1012...@bugs.debian.org> Assunto: Re: Bug#1012028: RFS: dirdiff/2.1-9 [ITA] -- Display and merge changes between two directory trees Am 31.05.22 um 04:20 schrieb Nilson Silva: > Control: tags -1- moreinfo Please answer to the RFS bug's address as well so others can see the progress. Also, just sending to me will not take action on the bug with the Control field. > > There is no point in this change alone. There are three bugs open >including a patch that could be upstreamed. > > Please have a look at them. > > Here's the result of the analysis: > ... > > 3. Debian Bug report logs - *#910388 *please allow to use "external viewers" > for n-way diff > This one I applied the path. I hope it's right. > > > If so, follow the repository with the changes: > https://salsa.debian.org/nilsonfsilva/dirdiff Please do not create a new repo for working on a package that already has a Vcs repo. Instead, fork it, work on it and when this RFS is sponsored, the sponsor will take back the changes to the original repo and maybe grant you access to it. So please recreate your repo as a fork and reapply your changes on it. Please untag moreinfo when you are done with that.
Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language
On Fri, Jun 03, 2022 at 09:38:37AM +0900, Nick Hastings wrote:
> * Package name: zig
> * URL : https://github.com/ziglang/zig
> * License : Expat, Apache-2, Apache-2 with LLVM exception,
> CC0, BSD-2-Clause, and LGPL-2+
> * Vcs : https://github.com/NickHastings/zig-debian
> zig - Imperative, general-purpose, statically typed, system programming
> language
Hi!
Worst news first: the copyright file requires a lot more work. I see for
example unlisted Khronos stuff (lib/libc/include/any-windows-any/{GL,KHR}/),
NTP (lib/libc/include/any-linux-any/linux/timex.h), Zope (mingw), ISC,
Apache, APSL, ... And the list of copyright holders is even more
incomplete. This is a big honking waste of time but it's required... :(
The package includes a bunch of tests, and with the likelihood of code not
handling a particular arch, glibc, etc, I'd say it's a must to run them.
Not a strict requirement, but a man page would be greatly appreciated.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi
⠈⠳⣄
Bug#1007222: transition: onetbb
Hi Andrius Thanks for your work on this. My comments below are inlined. On Fri, 3 Jun 2022 at 09:06, Andrius Merkys wrote: > Unrelated FTBFS > === > > freeture - not in testing > gmsh - https://tests.reproducible-builds.org/debian/rb-pkg/gmsh.html > kicad - https://tests.reproducible-builds.org/debian/rb-pkg/kicad.html > limereg - not in testing > madness - https://tests.reproducible-builds.org/debian/rb-pkg/madness.html > mldemos - not in testing > mpqc3 - not in testing > numba - not in testing > olive-editor - not in testing > opencolorio - not in testing > php-facedetect - not in testing > pigx-rnaseq - not in testing > pitivi - https://tests.reproducible-builds.org/debian/rb-pkg/pitivi.html > plastimatch - #1005485 > pytorch-audio - not in testing > pytorch-text - not in testing > pytorch-vision - not in testing > trilinos - https://tests.reproducible-builds.org/debian/rb-pkg/trilinos.html > > Unsatisfiable dependencies > == > > hyperspy - not in testing > poliastro - not in testing > pynpoint - not in testing > python-cogent - not in testing > python-epimodels - not in testing > python-fluids - not in testing > python-loompy - not in testing > python-numpy-groupies - not in testing > python-pynndescent - not in testing > python-sparse - not in testing > sfepy - not in testing > tiledarray - not in testing > umap-learn - not in testing > > Is this enough to remove 'moreinfo'? We can ignore everything that's not in testing, but please do look again at those marked 'Unrelated FTBFS' where I have placed a link to reproducible builds where they do not FTBFS. Regards Graham
Bug#1012210: linux-image-5.10.0-14-amd64: Kernels of Bullseye and Testing (5.10 and 5.17) hang at boot
Am 02.06.2022 23:26, schrieb Markus Kolb: Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb : [...] https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch [...] I've patched the kernel.org 5.10.113 just with these 2 Debian patches and at least I can confirm, that these changes are the cause. Although I don't understand at the moment where the difference of intel_iommu=on with patch and the defaults without patch could be. Will have a closer look tomorrow. I've found the difference, somehow I've had the opinion that with the kernel.org and Debian Buster kernel dmar_disabled would be set to false by default or CONFIG_INTEL_IOMMU_DEFAULT_ON would be enabled by default. But this is not the case. So dmar_disabled is true there without boot config. With the Debian patch in Bullseye and newer this has been enabled implicitly via CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y and dmar_disabled became false. With the older kernels you had to enable it per boot config, and now you need to disable it. So added now this to drivers/iommu/intel/iommu.c and my computer boots without any required kernel boot option with Debian kernels: --- a/drivers/iommu/intel/iommu.c 2022-06-03 14:50:52.248268257 +0200 +++ b/drivers/iommu/intel/iommu.c 2022-06-03 14:48:12.695769217 +0200 @@ -6186,6 +6186,9 @@ dmar_map_gfx = 0; } +/* Q35 integrated gfx dmar support is totally busted. */ +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x29b2, quirk_iommu_igfx); + /* G4x/GM45 integrated gfx dmar support is totally busted. */ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2a40, quirk_iommu_igfx); DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e00, quirk_iommu_igfx); The only related to problem, I've found, is this discussion without result 5 years ago: https://lore.kernel.org/linux-iommu/20161205215841.GA20819@beast/ And this nearly 4 year old bug report without attention: https://bugzilla.kernel.org/show_bug.cgi?id=201185 I've opened https://bugzilla.kernel.org/show_bug.cgi?id=216064 Would you add this patch to Debian kernels?
Bug#1007222: transition: onetbb
Hi On Thu, 2 Jun 2022 at 03:11, M. Zhou wrote: > I personally dislike making the old package libtbb2-dev. > How about we make the old src:tbb package go through NEW again > with the following renames: > > libtbb-dev -> libtbb-legacy-dev, this sounds much better than libtbb2-dev > because it explains itself to be a to-be-deprecated version. I personally don't like tbb-legacy-dev. It's not common in the archive for a -dev package. Most are unversioned, otherwise they match the library package, so libtbb2-dev for libtbb2. See e.g. lmsensors-dev, lmsensors4-dev, libpcre2-dev, libpcre3-dev, libvtk7-dev and libvtk9-dev, etc. Explanations can go in the package description, e.g. from libpcre3-dev "New packages should use the newer pcre2 packages, and existing packages should migrate to pcre2". > In this way we can finish the transition very quickly and leave > longer time for broken packages to migrate to onetbb. > > For me, submitting patches is as well much easier as I only have to > change libtbb-dev -> libtbb-legacy-dev for broken packages. Changing libtbb-dev -> libtbb2-dev should be even easier :). However, we don't **have** to reintroduce the old tbb package, and **you** don't have to be the one maintaining it. If all the packages that FTBFS with the new tbb can be removed from testing, the old tbb can be reintroduced after the transition, by some maintainers who wish to care for it. Regards Graham
Bug#1012309: nextcloud-desktop: Missing Dependency to qml-module-qt-labs-platform, does not launch without it
Package: nextcloud-desktop Version: 3.5.1-1 Severity: important The newest nextcloud-desktop update refuses to launch its gui, because it needs qml-module-qt-labs-platform. This dependency is not listed as such in the dpkg dependency tree. Error line: [ warning default qrc:/qml/src/gui/tray/Window.qml:8 ]:qrc:/qml/src/gui/tray/Window.qml:8:1: module "Qt.labs.platform" is not installed How to reproduce: * Remove qml-module-qt-labs-platform * launch application with nextcloud --logdebug -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 nextcloud-desktop depends on: ii libc6 2.33-7 ii libcloudproviders0 0.3.1-2 ii libgcc-s1 12.1.0-2 ii libglib2.0-0 2.72.1-1 ii libnextcloudsync0 3.5.1-1 ii libqt5core5a 5.15.2+dfsg-16+b2 ii libqt5dbus55.15.2+dfsg-16+b2 ii libqt5gui5 5.15.2+dfsg-16+b2 ii libqt5keychain10.13.2-5 ii libqt5network5 5.15.2+dfsg-16+b2 ii libqt5qml5 5.15.2+dfsg-10 ii libqt5quick5 5.15.2+dfsg-10 ii libqt5quickcontrols2-5 5.15.2+dfsg-4 ii libqt5sql5-sqlite 5.15.2+dfsg-16+b2 ii libqt5svg5 5.15.2-4 ii libqt5webenginecore5 5.15.8+dfsg-1+b2 ii libqt5webenginewidgets55.15.8+dfsg-1+b2 ii libqt5widgets5 5.15.2+dfsg-16+b2 ii libstdc++6 12.1.0-2 ii nextcloud-desktop-common 3.5.1-1 ii nextcloud-desktop-l10n 3.5.1-1 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtqml-models2 5.15.2+dfsg-10 ii qml-module-qtquick-controls2 5.15.2+dfsg-4 ii qml-module-qtquick-layouts 5.15.2+dfsg-10 ii qml-module-qtquick-window2 5.15.2+dfsg-10 ii qml-module-qtquick25.15.2+dfsg-10 Versions of packages nextcloud-desktop recommends: pn nextcloud-desktop-doc nextcloud-desktop suggests no packages. -- no debconf information
Bug#1012298: linux-image-5.17.0-1-amd64: New partition doesn't appear in /dev anymore with kernel 5.17 (repro script included)
Control: tag -1 upstream On Friday, 3 June 2022 09:53:41 CEST Michael Schaller wrote: > Note that on kernel 5.17 we also see this error in the kernel log: > [ 24.206158] I/O error, dev loop0, sector 32640 op 0x0:(READ) flags > 0x80700 phys_seg 1 prio class 0 On Friday, 3 June 2022 13:58:03 CEST Michael Schaller wrote: > I've tested some vanilla stable kernels (without Debian patches) and > can confirm that 5.17.0 and 5.18.1 (latest) are affected. Kernel > 5.16.18 isn't affected. > > a git bisect pointed towards this commit as the first bad commit: > https://github.com/torvalds/linux/commit/1ebe2e5f9d68e94c524aba876f27b945669a7879 https://lore.kernel.org/all/20211122130625.1136848-12-...@lst.de/ is linked in that commit and a recent reply points to sth similar as you see: https://lore.kernel.org/all/Yo4+zEnrBTnoEMCz@T590/ If you agree, then it seems to me that the best course of action seems to get involved in that discussion. signature.asc Description: This is a digitally signed message part.
Bug#1012308: unattended-upgrades: exclude blacklisted packages from kept packages
Package: unattended-upgrades Version: 2.8 Severity: minor Tags: patch We have the backports repository configured on our servers, however it's pinned to a priority of 100 to not install newer versions by default. We also have kernel packages (linux-image.*) blacklisted for unattended-upgrades. apt would not (checked by apt policy) install the newer version from backports, but unattended-upgrades sends an email each day with the information that a package (linux-image-amd64) is on hold. Looking at the code, this behavior happens, because unattended-upgrades assigns each blacklisted package a priority of -32768 (NEVER_PIN) which overrides all other apt pinning and also sets the priority of each and every version of this package to the same number, regardless of its former priority. Therefore, kept_package_excuse() will always find a better version in such cases, regardless of pinning, as it compares the modified (NEVER_PIN) priorities. I have two proposals: 1) take the original priorities in account for finding newer versions, but this will probably be quite a big rework 2) do not report blacklisted packages as kept / on hold, as there is currently no way to discern whether the newer version is a candidate for installation Here is a patch for option 2: --- /usr/bin/unattended-upgrade 2021-02-19 13:11:42.0 +0100 +++ unattended-upgrade 2022-06-03 14:22:53.972635631 +0200 @@ -208,6 +208,8 @@ "dry-run mode.")) return kept_packages for pkg in self: +if pkg.is_installed and pkg.installed.policy_priority == NEVER_PIN: +continue better_version = self.find_better_version(pkg) if better_version: logging.info(self.kept_package_excuse(pkg._pkg, Cheers Volker -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 unattended-upgrades depends on: ii debconf [debconf-2.0] 1.5.79 ii lsb-base 11.2 ii lsb-release11.2 ii python33.9.8-1 ii python3-apt2.3.0+b1 ii python3-dbus 1.2.18-3+b1 ii python3-distro-info1.1 ii ucf3.0043 ii xz-utils 5.2.5-2.1 Versions of packages unattended-upgrades recommends: ii anacron 2.3-32 ii cron [cron-daemon] 3.0pl1-139 ii systemd-sysv250.4-1 Versions of packages unattended-upgrades suggests: pn bsd-mailx ii exim4-daemon-light [mail-transport-agent] 4.95-6 ii needrestart3.6-1 ii powermgmt-base 1.36 ii python3-gi 3.42.1-1 -- debconf information: * unattended-upgrades/enable_auto_updates: true
Bug#1012278: kodi web interface does not work
On 03/06/2022 12:38, Vasyl Gello wrote: Dear Richard! Thanks for investigation! I am going to solve the (missing) webinterface issue by packaging elm-chorus which is the newest rewrite of Chorus2 in Elm maintained by Kodi team members Kolja Lampe (@razze) and GSoC students. What we need now in Debian is Elm compiler for that. I don't understand; the web interface seems to be there, it is just broken, at least in part due to packaging decisions. What do you mean? ttfn/rjk
Bug#1012307: Testing removal
Source: php-symfony-polyfill Version: 1.25.0-3 Severity: serious Control: close -1 1.25.0-4 [ RC-bug filled by the maintainer to see the package autoremoved from testing. ] php-symfony-polyfill has no reverse-dependencies in testing (except the symfony version currently in testing), and should not hold symfony migration because of failing autopkgtest, so maybe getting it autoremoved from testing will do the trick. Asking on #debian-release didn’t help, so the other “right” path would be to add some Breaks or Conflicts against the symfony version currently in testing but I often get them wrong once or twice… Regards David signature.asc Description: PGP signature
Bug#1012283: makedev: erroneous conflict with udev?
Hello, I will analyze this situation in more depth and for now, I am reversing this situation. Thanks
Bug#991768: wireguard-dkms: wireguard-dmks autoinstall fails, not matching BUILD_EXCLUSIVE directive in Bullesye
Control: severity -1 serious Control: retitle -1 wireguard-dkms: useless in bullseye, in mainline kernel since linux 5.6 On Sun, 01 Aug 2021 15:20:34 +0200 Sem wrote: > Package: wireguard-dkms > Version: 1.0.20210219-1 > Setting up linux-headers-5.10.0-8-amd64 (5.10.46-3) ... > /etc/kernel/header_postinst.d/dkms: > dkms: running auto installation service for kernel 5.10.0-8-amd64:Error! The > /var/lib/dkms/wireguard/1.0.20210219/5.10.0-8-amd64/x86_64/dkms.conf for > module wireguard includes a BUILD_EXCLUSIVE directive which > does not match this kernel/arch. This indicates that it should not be built. wireguard was merged into the mainline kernel in 5.6, so this package should not have been released with bullseye at all. It should definitively not be part of bookworm. It may have some use in sid as long as stretch/buster kernels are still supported (in (E)LTS as well) ... Andreas
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
On 02/06/2022 07:27, Jeroen Ploemen wrote: On Sun, 29 May 2022 11:52:53 +0100 Peter wrote: Updated copyright and reverted to Qt5 Thanks, qt5 seems to be the way to go for now. Also, I found that the Qt6 version on Debian had very a small font, with no obvious way of enlarging it. If Strawberry is accepted into Debian, I'd consider updating the package to build both Qt5 & Qt6 versions. With a Strawberry-common, maybe the Qt5 & Qt6 binaries could co-install? Looks like there's an error in the dbus copyright entry though, given that the file linked in the comment is under LGPL rather than GPL? My bad. Fixed. And more importantly: the comment only deals with one of the xml files, but (as far as I can tell) these do not all originate from a single source. For example, org.kde.KGlobalAccel.*.xml files appear in the kglobalaccel package; the Udisks stuff might well be based on [2]; mpris/MediaPlayer2 in turn appears in [3]. I suspect some of the org.freedesktop.*.xml files on the other hand could be based directly on dbus specs [1] or similar generic interface definitions for use with qdbusxml2cpp, possibly autogenerated by qdbus along the lines of: `QT_SELECT=5 qdbus org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.DBus.Introspectable.Introspect` I've created separate Files paragraphs for each group of files. (I'm not sure what the impact of auto-generation is on the copyright. I notice that in [3], the author is the upstream application author, no reference to org.freedesktop) Aside from the dbus xml stuff: what exactly do you mean by the comment in the GPL-3 license paragraph? I'm confused regarding GPL-3 & GPL-3+. We now have a License paragraph for GPL-3 that excludes later versions, but the full text in /usr/share/common-licenses/GPL-3 https://www.gnu.org/licenses/gpl-3.0.html both include it! I'm wondering whether it would be best to have a single GPL-3 licence, or at least to remove the "(version 3 only)". ISTM that failing to explicitly state in a source file header that a later version can be used, does not necessarily mean that right is excluded, especially when its explicitly included in the linked full text Anyway, up to you, I have just removed the comment for now. [1]https://dbus.freedesktop.org/doc/dbus-specification.html [2]https://salsa.debian.org/utopia-team/udisks2/-/blob/debian/master/data/org.freedesktop.UDisks2.xml [3]https://sources.debian.org/src/mpdris2/0.9.1-1/src/mpDris2.in.py/#L133 Thanks for the links. I've put [1] into the copyright file. Cheers, Peter Uploaded to Salsa & Mentors.
Bug#1012289: O: lintian -- Debian package checker
Hi, On Fri, Jun 03, 2022 at 10:17:46AM +0800, Paul Wise wrote: Package: wnpp Severity: normal X-Debbugs-Cc: debian-de...@lists.debian.org, debian-lint-ma...@lists.debian.org Control: affects -1 src:lintian The lintian package is now orphaned as both of the people who were actively working on lintian have stopped that work: https://lists.debian.org/msgid-search/5e4d0e28-a3f4-4302-8364-5afd93d8a...@www.fastmail.com https://lists.debian.org/msgid-search/cafhyt550_6hc-2srjqyv0z9kgpwulpgnnxvoonpohp3r+pa...@mail.gmail.com Please join the lintian group/project on salsa if you want to help maintain the lintian codebase; add tests, update for new policy etc. https://salsa.debian.org/lintian/lintian I have sent the request to join the group to help maintain the lintian package. And I know this is big challenge for me but I will acceppt it. Thank you. Bo The package description is: Lintian dissects Debian packages and reports bugs and policy violations. It contains automated checks for many aspects of Debian policy as well as some checks for common errors. . This package is useful for all people who want to check Debian packages for compliance with Debian policy. Every Debian maintainer should check packages with this tool before uploading them to the archive. . This version of Lintian is calibrated for Debian Policy version 4.6.0.1. -- bye, pabs https://wiki.debian.org/PaulWise -- Best Regards, signature.asc Description: PGP signature
Bug#1012272: colordiffrc: using apt-get to upgrade system I recieve error
The 'Unknown option' error message arises when running colordiff, but there is no explicit call to colordiff during package installation or upgrade. However ... is it possible that you have diff and colordiff aliased or symlinked? If so and the package installation calls a 'diff' this would in turn call 'colordiff'. (I haven't checked, but presumably the package installation script may use 'diff' to check whether /etc/colordiffrc is up to date) In which I can see how this message might arise, since it would maybe be running an older version of colordiff for that diff (until the install is completed). The 'difffile' option was introduced in colordiff 1.0.19 and, if you are running Debian/testing, you'd have been updating from colordiff 1.0.18 to colordiff 1.0.20. Might that explain what you see? Dave. -- Dave Ewart, da...@sungate.co.uk
Bug#1012278: kodi web interface does not work
Dear Richard! Thanks for investigation! I am going to solve the (missing) webinterface issue by packaging elm-chorus which is the newest rewrite of Chorus2 in Elm maintained by Kodi team members Kolja Lampe (@razze) and GSoC students. What we need now in Debian is Elm compiler for that. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다
Bug#977441: linux: Pls. consider CONFIG_DRM_V3D
On 17 Dec 2020 Ryutaroh Matsumoto wrote: > I modprobe'ed v3d.ko on vanilla Linux kernel 5.10.1, > but /dev/dri/render* does not appear like > > https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/comments/14 That comment mentions the following kernel config options: > CONFIG_CLK_RASPBERRYPI=y > CONFIG_ARM_RASPBERRYPI_CPUFREQ=y Those are now available in Debian kernels, although the latter is '=m'. > CONFIG_DRM_V3D=m I have made a branch where that is (also) enabled ... > Simply compiling and loading v3d do not seem to enable DRM/GPU acceleration > on RPi4... We may need some work for enabling GPU acceleration on RPi series. The major missing piece AFAICT was enablement in DeviceTree. Recently a patch set was submitted that seems to contain the missing pieces and I added that to https://salsa.debian.org/diederik/linux/-/commits/rpi-enable-v3d https://lore.kernel.org/all/20220601110249.569540-1-pbrobin...@gmail.com/ is the upstream thread where I got the patches from. If you can build a kernel based on my branch and verify it then works, that would be great. Especially if you could send a "Tested-By " email to that upstream thread which should help in getting the patch set accepted and eventually land in Linus' tree. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1012164: Another crash, different message
Today it crashed again, but this time I got a different message: atanks: src/virtobj.cpp:77: virtual void VIRTUAL_OBJECT::draw(): asserzione "bitmap && "ERROR: VIRTUAL_OBJECT::draw() called without bitmap!"" non riuscita. Shutting down Allegro due to signal #6 I don't know if it's the same bug or a different one. It seems both messages (the one in my original report and this one) refer to something GUI related, they both happen while playing, they are both failed assertions and they both happened during the AI turn, but that's all I have to assume they are related to the same bug.
Bug#1012210: linux-image-5.10.0-14-amd64: Kernels of Bullseye and Testing (5.10 and 5.17) hang at boot
Control: clone -1 -2 Control: notfound -2 linux/5.17.3-1 Control: retitle -2 linux-image-5.10.0-14-amd64: boot failure in VM after upgrading from -13 Control: tag -2 moreinfo On Friday, 3 June 2022 05:35:15 CEST Vicente Olivert Riera wrote: > Package: src:linux > Followup-For: Bug #1012210 This seems to be completely unrelated to that bug, so I've cloned it into a new bug. When responding please only respond to that new bug report/number. > I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021. > The software I'm using is UTM, which uses QEMU under the hood. > > Yesterday I did a system upgrade: > aptitude -y update && aptitude -y full-upgrade && apt -y autoremove General tip: don't do that! With 'update' it seems pointless With 'full-upgrade' you REALLY should review what is about to happen before agreeing to that as it could remove packages (important for you) I'd recommend reviewing the 'autoremove' result too before committing it > I noticed the kernel was upgraded to 5.10.0-14 so I rebooted the VM. After > that Debian was unable to boot. Choosing the previous kernel image > available from Grub (5.10.0-13) allowed Debian to boot normally. Bug 1012210 is about a boot failure on a (wide) variety of kernels, likely related to igpu. Your issue is a regression from -13 to -14. I assumed that you're running Debian Stable *in* a VM (on what host OS?). Please clarify whether that is correct or not. Also provide more info about YOUR boot failure and sent that to the NEW bug number that you should receive. signature.asc Description: This is a digitally signed message part.
Bug#1012305: Acknowledgement (zfsutils-linux: tried to instal zfsutils-linux on 2 systems, it fails to compile the module on both.)
I forgot to add the full install command and listing: andrei@lnadmn078:~$ sudo apt install zfsutils-linux [sudo] password for andrei: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libnvpair3linux libuutil3linux libzfs4linux libzpool4linux python3- distutils python3-lib2to3 zfs-dkms zfs-zed Suggested packages: debhelper nfs-kernel-server zfs-initramfs | zfs-dracut The following NEW packages will be installed: libnvpair3linux libuutil3linux libzfs4linux libzpool4linux python3- distutils python3-lib2to3 zfs-dkms zfs-zed zfsutils-linux 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 4.605 kB of archives. After this operation, 25,3 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://deb.debian.org/debian bullseye/main amd64 python3-lib2to3 all 3.9.2-1 [77,8 kB] Get:2 https://deb.debian.org/debian bullseye/main amd64 python3- distutils all 3.9.2-1 [143 kB] Get:3 https://deb.debian.org/debian bullseye/contrib amd64 zfs-dkms all 2.0.3-9 [2.234 kB] Get:4 https://deb.debian.org/debian bullseye/contrib amd64 libnvpair3linux amd64 2.0.3-9 [61,2 kB] Get:5 https://deb.debian.org/debian bullseye/contrib amd64 libuutil3linux amd64 2.0.3-9 [54,0 kB] Get:6 https://deb.debian.org/debian bullseye/contrib amd64 libzfs4linux amd64 2.0.3-9 [231 kB] Get:7 https://deb.debian.org/debian bullseye/contrib amd64 libzpool4linux amd64 2.0.3-9 [1.247 kB] Get:8 https://deb.debian.org/debian bullseye/contrib amd64 zfsutils- linux amd64 2.0.3-9 [481 kB] Get:9 https://deb.debian.org/debian bullseye/contrib amd64 zfs-zed amd64 2.0.3-9 [75,4 kB] Fetched 4.605 kB in 1s (6.858 kB/s) Preconfiguring packages ... Selecting previously unselected package python3-lib2to3. (Reading database ... 291003 files and directories currently installed.) Preparing to unpack .../0-python3-lib2to3_3.9.2-1_all.deb ... Unpacking python3-lib2to3 (3.9.2-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../1-python3-distutils_3.9.2-1_all.deb ... Unpacking python3-distutils (3.9.2-1) ... Selecting previously unselected package zfs-dkms. Preparing to unpack .../2-zfs-dkms_2.0.3-9_all.deb ... Unpacking zfs-dkms (2.0.3-9) ... Selecting previously unselected package libnvpair3linux. Preparing to unpack .../3-libnvpair3linux_2.0.3-9_amd64.deb ... Unpacking libnvpair3linux (2.0.3-9) ... Selecting previously unselected package libuutil3linux. Preparing to unpack .../4-libuutil3linux_2.0.3-9_amd64.deb ... Unpacking libuutil3linux (2.0.3-9) ... Selecting previously unselected package libzfs4linux. Preparing to unpack .../5-libzfs4linux_2.0.3-9_amd64.deb ... Unpacking libzfs4linux (2.0.3-9) ... Selecting previously unselected package libzpool4linux. Preparing to unpack .../6-libzpool4linux_2.0.3-9_amd64.deb ... Unpacking libzpool4linux (2.0.3-9) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../7-zfsutils-linux_2.0.3-9_amd64.deb ... Unpacking zfsutils-linux (2.0.3-9) ... Selecting previously unselected package zfs-zed. Preparing to unpack .../8-zfs-zed_2.0.3-9_amd64.deb ... Unpacking zfs-zed (2.0.3-9) ... Setting up libnvpair3linux (2.0.3-9) ... Setting up libuutil3linux (2.0.3-9) ... Setting up python3-lib2to3 (3.9.2-1) ... Setting up python3-distutils (3.9.2-1) ... Setting up libzfs4linux (2.0.3-9) ... Setting up zfs-dkms (2.0.3-9) ... Loading new zfs-2.0.3 DKMS files... Building for 5.10.0-14-amd64 Building initial module for 5.10.0-14-amd64 grep: /lib/modules/5.10.0-14-amd64/build/include/linux/miscdevice.h: No such file or directory configure: error: *** None of the expected "global page state" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.0.3-9 *** Compatible Kernels: 3.10 - 5.10 Error! Bad return status for module build on kernel: 5.10.0-14-amd64 (x86_64) Consult /var/lib/dkms/zfs/2.0.3/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 Setting up libzpool4linux (2.0.3-9) ... dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfs-modules | zfs-dkms; however: Package zfs-modules is not installed. Package zfs-dkms which provides zfs-modules is not configured yet. Package zfs-dkms is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Setting up zfsutils-linux (2.0.3-9) ... modprobe: FATAL: Module zfs not found in directory /lib/modules/5.10.0- 14-amd64 Created symlink /etc/systemd/system/zfs-import.target.wants/zfs-import- cache.service →
Bug#1012305: zfsutils-linux: tried to instal zfsutils-linux on 2 systems, it fails to compile the module on both.
Package: zfsutils-linux Version: 2.0.3-9 Severity: important X-Debbugs-Cc: andrei.horn...@ist.ac.at Dear Maintainer, I recently tried to install zfsutils-linux on 2 separate Debian11.2 desktop installation. Initially it was a test instance on my main system, which I dual- booted with the previous system. The initial ubuntu install has zfs installed and working. The installation of zfsutils-linux on the debian 11 install failed at the modules, just like now. This attempts was several months ago. I tried again today on my laptop that also is running Debian 11 desktop just to see if it was fixed. It also failed to install and failed to compile the modules. The relevant section is: Setting up zfs-dkms (2.0.3-9) ... Removing old zfs-2.0.3 DKMS files... -- Deleting module version: 2.0.3 completely from the DKMS tree. -- Done. Loading new zfs-2.0.3 DKMS files... Building for 5.10.0-14-amd64 Building initial module for 5.10.0-14-amd64 grep: /lib/modules/5.10.0-14-amd64/build/include/linux/miscdevice.h: No such file or directory configure: error: *** None of the expected "global page state" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.0.3-9 *** Compatible Kernels: 3.10 - 5.10 Error! Bad return status for module build on kernel: 5.10.0-14-amd64 (x86_64) Consult /var/lib/dkms/zfs/2.0.3/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): Headers are present on the system. The log itself contains only 3 lines: cat /var/lib/dkms/zfs/2.0.3/build/make.log DKMS make.log for zfs-2.0.3 for kernel 5.10.0-14-amd64 (x86_64) Fr 03 Jun 2022 12:09:46 CEST make: *** No targets specified and no makefile found. Stop. Hope this gets fixed soon, would really like to be able to switch to debian 11 on my main system. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/4 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zfsutils-linux depends on: ii init-system-helpers 1.60 ii libblkid12.36.1-8+deb11u1 ii libc62.31-13+deb11u3 ii libnvpair3linux 2.0.3-9 ii libuuid1 2.36.1-8+deb11u1 ii libuutil3linux 2.0.3-9 ii libzfs4linux 2.0.3-9 ii libzpool4linux 2.0.3-9 ii python3 3.9.2-3 Versions of packages zfsutils-linux recommends: ii lsb-base11.1.0 ih zfs-dkms [zfs-modules] 2.0.3-9 iu zfs-zed 2.0.3-9 Versions of packages zfsutils-linux suggests: pn nfs-kernel-server ii samba-common-bin2:4.13.13+dfsg-1~deb11u3 pn zfs-initramfs | zfs-dracut -- Configuration Files: /etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs'
Bug#1012276: sudo: Usefulness of the --enable-admin-flag configuration option in Debian
On Thu, Jun 02, 2022 at 07:39:39PM +0200, Vincent Blut wrote: > At the moment, it does not seem valuable to have it enabled in Debian since > all > it does is creating the empty sudo_as_admin_successful hidden file in the home > directory of the user calling sudo. > > What makes this option interesting in Ubuntu is this code snippet in > /etc/bash.bashrc: > > if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ] > ; then > case " $(groups) " in *\ admin\ *|*\ sudo\ *) > if [ -x /usr/bin/sudo ]; then > cat <<-EOF > To run a command as administrator (user "root"), use "sudo > ". > See "man sudo_root" for details. > > EOF > fi > esac > fi > > Until bash in Debian provides this, I propose that we drop this configuration > option (setting 'Defaults !admin_flag' in /etc/sudoers would work too). If > this > is acceptable to you, I can send a merge request. I'd rather add some more documentation what this does, so that people can add code to their respective scripts. What is the harm done by the option? Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1012304: RM: node-react-audio-player -- ROM; FTBFS and useless
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: 1002...@bugs.debian.org, 1012...@bugs.debian.org Hi, this package is currently broken (#1002863), has no reverse dependencies and is going to be orphaned (#1012212). That's why it could be removed from Debian. Cheers, Yadd
Bug#1005399: Depends on kernel internal crypto API and no longer builds
Control: tag -1 fixed-upstream On Sat, 12 Feb 2022 21:35:59 +0100 Ben Hutchings wrote: > gost-crypto depends on the crypto_cipher API. Since Linux 5.12 this > is internal to the crypto subsystem and is not available to > out-of-tree modules. There is a commit available upstream that seems to fix this issue: https://github.com/GostCrypt/linux-crypto/commit/08bff40a03aeda17416511bee6f7fb331ceca117 Andreas
Bug#1011168: linux-image-5.17.0-2-amd64: rebooting KVM guest crashes kernel
Hi, On Thu, Jun 02, 2022 at 08:56:48PM -0400, Jon wrote: > I did 5 reboots of the guest followed by 5 complete shutdown/startup > cycles of the guest. No kernel panics occurred. > > Based on how frequent the crashes were before, I would say thats a > succesful test. Many thanks for the confirmation. Regards, Salvatore
Bug#1011928: trilinos FTBFS: isinf was not defined in this scope
Control: retitle -1 trilinos: FTBFS with onetbb 2021.5.0 Control: severity -1 important Control: tags -1 + ftbfs Hi On Mon, 30 May 2022 at 13:02, Graham Inggs wrote: > To be clear, does this failure only happen with libtbb-dev/experimental? Assuming so. I have tested building trilinos with libtbb-dev from experimental, and I see the same 'isinf' error as above. However, I believe this is only part of a configuration test, and the actual error is further up in the log (excerpt below). I've discussed with my co-maintainer and he believes it is safe to disable tbb support in trilinos. Regards Graham Processing enabled TPL: TBB (enabled explicitly, disable with -DTPL_ENABLE_TBB=OFF) -- TBB_LIBRARY_NAMES='tbb' -- Searching for libs in TBB_LIBRARY_DIRS='' -- Searching for a lib in the set "tbb": -- Searching for lib 'tbb' ... -- Found lib '/usr/lib/x86_64-linux-gnu/libtbb.so' -- TPL_TBB_LIBRARIES='/usr/lib/x86_64-linux-gnu/libtbb.so' -- Searching for headers in TBB_INCLUDE_DIRS='' -- Searching for a header file in the set "tbb/task_scheduler_init.h": -- Searching for header 'tbb/task_scheduler_init.h' ... -- ERROR: Could not find a header file in the set "tbb/task_scheduler_init.h" -- ERROR: Could not find the include directories for TPL 'TBB'! -- TIP: If the TPL 'TBB' is on your system then you can set: -DTBB_INCLUDE_DIRS=';;...' to point to directories where these header files may be found. Or, just set: -DTPL_TBB_INCLUDE_DIRS=';;...' to point to the include directories which will bypass any search for header files and these include directories will be used without question in the build. (But this will result in a build-time error obviously if the necessary header files are not found in these include directories.) -- ERROR: Failed finding all of the parts of TPL 'TBB' (see above), Aborting! -- NOTE: The find module file for this failed TPL 'TBB' is: /<>/cmake/TPLs/FindTPLTBB.cmake which is pointed to in the file: /<>/TPLsList.cmake TIP: Even though the TPL 'TBB' was explicitly enabled in input, it can be disabled with: -DTPL_ENABLE_TBB=OFF which will disable it and will recursively disable all of the downstream packages that have required dependencies on it. When you reconfigure, just grep the cmake stdout for 'TBB' and then follow the disables that occur as a result to see what impact this TPL disable has on the configuration of Trilinos. CMake Error at cmake/tribits/core/package_arch/TribitsProcessEnabledTpl.cmake:144 (message): ERROR: TPL_TBB_NOT_FOUND=TRUE, aborting! Call Stack (most recent call first): cmake/tribits/core/package_arch/TribitsGlobalMacros.cmake:1581 (tribits_process_enabled_tpl) cmake/tribits/core/package_arch/TribitsProjectImpl.cmake:196 (tribits_process_enabled_tpls) cmake/tribits/core/package_arch/TribitsProject.cmake:93 (tribits_project_impl) CMakeLists.txt:109 (TRIBITS_PROJECT) -- Configuring incomplete, errors occurred!
Bug#1012303: gource: SDL initialization failed - GLEW Error: Unknown error
Package: gource Version: 0.53-1 Severity: normal ~/Projects/xxx:master$ gource gource: SDL initialization failed - GLEW Error: Unknown error Try 'gource --help' for more information. I'm running gnome on wayland. Graphic card is radeon/turks. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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 gource depends on: ii fonts-freefont-ttf 20120503-10 ii libboost-filesystem1.74.0 1.74.0-16 ii libc6 2.33-7 ii libfreetype6 2.12.1+dfsg-2 ii libgcc-s1 12.1.0-2 ii libgl1 1.4.0-1 ii libglew2.2 2.2.0-4 ii libglu1-mesa [libglu1] 9.0.2-1 ii libpcre2-8-0 10.40-1 ii libpng16-161.6.37-5 ii libsdl2-2.0-0 2.0.22+dfsg-4 ii libsdl2-image-2.0-02.0.5+dfsg1-3+b1 ii libstdc++6 12.1.0-2 ii libtinyxml2.6.2v5 2.6.2-6 gource recommends no packages. gource suggests no packages. -- no debconf information
Bug#1012302: apbs: ftbfs on riscv64: error: ‘_FPU_MASK_IM’ undeclared (first use in this function)
Package: apbs Version: 3.4.1-4 Severity: minor Tags: ftbfs, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear Maintainer, The apbs package has ftbfs on riscv64: ``` /<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:17: error: ‘_FPU_MASK_IM’ undeclared (first use in this function) 305 | cw &= ~(_FPU_MASK_IM | _FPU_MASK_ZM | _FPU_MASK_OM); | ^~~~ /<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:17: note: each undeclared identifier is reported only once for each function it appears in /<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:32: error: ‘_FPU_MASK_ZM’ undeclared (first use in this function) 305 | cw &= ~(_FPU_MASK_IM | _FPU_MASK_ZM | _FPU_MASK_OM); |^~~~ [ 8%] Building C object _deps/fetk-build/punc/src/cgcode/CMakeFiles/cgcode.dir/spcgnr.c.o /<>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:47: error: ‘_FPU_MASK_OM’ undeclared (first use in this function) 305 | cw &= ~(_FPU_MASK_IM | _FPU_MASK_ZM | _FPU_MASK_OM); | ^~~~ ``` The full buildd is here: https://buildd.debian.org/status/fetch.php?pkg=apbs=riscv64=3.4.1-3=1654099965=0 And I refer to here[0], becasue the fpu_control.h on riscv64 does not have these macroes are defined, so I am intend to add these macroes in uninit.c by manual. Tha patch attached is fix the issue and it is build ok on localy. ``` Build Architecture: riscv64 Build Type: binary Build-Space: 436052 Build-Time: 1883 Distribution: UNRELEASED Host Architecture: riscv64 Install-Time: 245 Job: /home/vimer/build/06/02_apbs/apbs_3.4.1-4.dsc Lintian: warn Machine Architecture: amd64 Package: apbs Package-Time: 2170 Source-Version: 3.4.1-4 Space: 436052 Status: successful Version: 3.4.1-4 Finished at 2022-06-03T07:43:04Z Build needed 00:36:10, 436052k disk space ``` Please consider to apply it in next upload and if any issue please let me know. PS: I noticed there is different with abps on sala repo and sid. I have to switch the newest repo to build it:) [0]: https://github.com/Electrostatics/FETK/issues/71 --- debian/external_deps/fetk/punc/src/vf2c/uninit-old.c 2022-06-03 17:08:45.698221199 +0800 +++ debian/external_deps/fetk/punc/src/vf2c/uninit.c 2022-06-03 17:15:06.365211794 +0800 @@ -148,6 +148,16 @@ #endif #endif + +#if defined(__riscv) && defined(__riscv_xlen) && __riscv_xlen == 64 +/* Masks for interrupts. */ +#define _FPU_MASK_V 0x0800 /* Invalid operation */ +#define _FPU_MASK_Z 0x0400 /* Division by zero */ +#define _FPU_MASK_O 0x0200 /* Overflow */ +#define _FPU_MASK_U 0x0100 /* Underflow */ +#define _FPU_MASK_I 0x0080 /* Inexact operation */ +#endif + #ifdef MSpc #define IEEE0_done #include "float.h" @@ -178,7 +188,7 @@ } #endif /* MSpc */ -#if defined (__mips) && !defined (__linux__) /* must link with -lfpe */ +#if defined (__mips) && !defined (__linux__) /* must link with -lfpe */ #define IEEE0_done /* code from Eric Grosse */ #include signature.asc Description: PGP signature
Bug#1012299: RM: src:ruby-uglifier/2.7.2+dfsg-2
Control: tags -1 + moreinfo Hi Pirate On Fri, 3 Jun 2022 at 10:06, Pirate Praveen wrote: > Please remove ruby-uglifier from testing to allow migration of > node-source-map to testing. This regression was introduced by webpack 5 in > testing. > > rails no longer build depend on ruby-uglifier. > > ruby-uglifier should be removed from archive eventually. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981224 > > https://lists.debian.org/debian-ruby/2022/06/msg0.html This should wait until the following build-dependencies in testing have been resolved: $ reverse-depends -b -r testing src:ruby-uglifier Reverse-Build-Depends * nanoc (for ruby-uglifier) * rails (for ruby-uglifier) * ruby-sprockets(for ruby-uglifier) * ruby-sprockets-rails (for ruby-uglifier) Regards Graham
Bug#1011952: mesa: FTBFS on kfreebsd
Le 2/06/22 à 18:25, Timo Aaltonen a écrit : Laurent Bigonville kirjoitti 27.5.2022 klo 18.43: Source: mesa Version: 22.1.0~rc5-1 Severity: important Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Forwarded: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4081 Hello, mesa currently FTBFS on kfreebsd The attached patch seems to fix this The patch has been propsed upstream Could you please apply that patch? Is disabling gallium-extra-hud a part of the fix? Yes indeed, should have mentioned it Apparently it requires linux specific wireless headers, disabling it on non-linux/kfreebsd is allowing the package to build
Bug#933730: zsh: pipeline that cannot be interrupted with Ctrl-C (regression)
Control: forwarded -1 https://www.zsh.org/mla/workers/2022/msg00435.html
since there were no replies to my old bug report upstream (2019).
On 2022-06-03 10:30:29 +0200, Vincent Lefevre wrote:
> Version: 5.9-1
>
> On 2019-08-02 16:58:09 +0200, Vincent Lefevre wrote:
> > The following pipeline cannot be interrupted with Ctrl-C:
> >
> > { /bin/sleep 10 ; /bin/sleep 20; } | { /bin/sleep 30 ; /bin/sleep 40; }
>
> Now fixed.
In case someone wishes to backport the fix, the upstream fix is
commit 15bf8ace168a86d0fae90b10e9f706baddd4c0bf on 2022-04-30.
--
Vincent Lefèvre - Web:
Bug#985669: [Pkg-javascript-devel] Bug#985669: RFP: pnpm -- Efficent NPM replacement
Le dim. 21 mars 2021 à 19:42, Calum McConnell a écrit : > Package: wnpp > Severity: wishlist > X-Debbugs-Cc: calumlikesapple...@gmail.com, > pkg-javascript-de...@lists.alioth.debian.org > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > * Package name: pnpm > Version : 5.18.8 > Upstream Author : Zoltan Kochan > * URL : https://pnpm.js.org/ > * License : MIT > Programming Lang: Javascript > Description : Efficent NPM replacement > > PNPM is a disk-efficent replacement for the NPM command. It > prevents duplication of package files across projects by hard > linking files to a content-addressed store. It is a great solution > for developers with limited hard-drive space, or a large number of > projects. > > - > > While I would love to package this myself, I do not work with > JavaScript regularally (in part due to ecosystem problems like > NPM's love of duplication). As such, I am filing this as an RFP, > as opposed to an ITP. I did a quick-and-dirty, *non-free*, package of pnpm (made out of bundled pnpm tarball) https://salsa.debian.org/kapouer/pnpm Allowing pnpm to build itself won't be easy, though, and will come with a huge load of bundled / non-bundled dependencies. Jérémy
Bug#1012301: bacula: Corruption of File media during concurrent backups
Source: bacula Severity: important Tags: upstream Hello, Under a specific type of configuration, a Bacula job may sometimes corrupt a previously written volume, losing all data on it. The following circumstances have been identified : - Multiple concurrent jobs are started at the same time, all using the same Schedule and Pool - That Pool must have a Volume Use Duration which is higher than the frequency of the Jobs in the Schedule (For example, hourly backups with a VUD of 2 hours) - The Pool uses a Device which uses File media Once these conditions, are filled, a job may randomly corrupt a volume, typically when that volume is marked as "Used". This has the following consequences : - The Job status is "OK -- with warnings" - The Job includes the following error from the "mount.c" file : "Hey! WroteVol non-zero !" - One of previously-written volumes is marked in Error - That volume size on the filesystem drops below 1 kB (Effectively erased) - Attempting to restore files from a volume in error fails (Ending up as a mismatch) === Steps to Reproduce === Configure a Bacula cluster with the following conditions : - A Device must use "Media Type = File" - A Pool must have a certain Volume Use Duration (for example, 2 hours) - A Schedule must perform regular jobs with a higher frequency than the Volume Use Duration of the Pool (for example, every hour) - Multiple Jobs must be using this Schedule and Pool - The jobs must run concurrently Under these conditions, a job will eventually corrupt a previously written volume === Additional Information === This bug happens on various releases of Bacula from the official Debian packages (5.2, 7.4 and 9.4 are affected) This bug happens on multiple separated Bacula clusters (Nothing is shared between them) In case it matters, the FDs use PKI Signatures and Encryption This bug does not happen if the Volume Use Duration is set lower than the frequency of backups, ensuring a given Volume is never re-used between "batches" of backups (This is our current workaround) This bug did not happen before we implemented Concurrent Jobs The bug has been declared upstream : https://bugs.bacula.org/view.php?id=2664 -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-18-amd64 (SMP w/32 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1012240: winbind does not return AD groups a user is a member of AT ALL, or only one
03.06.2022 04:00, Matt Grant wrote: Hi! May be best to move the contents of /usr/libexec/samba to samba-libs. No, definitely not. A library is a library, it is multiarch and different arch must be co-installable. It might be more appropriate to move these executables to samba-common-bin as I already mentioned. But before that I need to understand how/when they're used. Maybe some day I will find a time to dig into the code to understand this... /mjt
Bug#1012240: [Pkg-samba-maint] Bug#1012240: winbind does not return AD groups a user is a member of AT ALL, or only one
03.06.2022 05:31, Andrew Bartlett wrote: On Fri, 2022-06-03 at 13:08 +1200, Matt Grant wrote: Otherwise, libwbclient0 ends up being installed when samba-lbs is installed due to depending on samba-libs? I read this like samba-libs uses libwbclient, not like libwbclient uses samba-libs (would be wrong). libwbclient0 should not depend on anything else in Samba (due to licence requirements) so if there is a linking reason for this we should check into this. I did move one more library from samba-libs to libwbclient while packaging 4.16 on debian. Overall, this is the current content of libwbclient0.deb: /usr/lib/x86_64-linux-gnu/libwbclient.so.0.15 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0.0.1 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0 /usr/lib/x86_64-linux-gnu/samba/libiov-buf-samba4.so.0 /usr/lib/x86_64-linux-gnu/samba/libreplace-samba4.so.0 /usr/lib/x86_64-linux-gnu/samba/libsamba-debug-samba4.so.0 /usr/lib/x86_64-linux-gnu/samba/libsocket-blocking-samba4.so.0 /usr/lib/x86_64-linux-gnu/samba/libsys-rw-samba4.so.0 /usr/lib/x86_64-linux-gnu/samba/libtime-basic-samba4.so.0 Some of these has been there before. Some (I think it was just one, can't remember which) were added by me during 4.16 packaging time. One of my todo items about samba states to review which libs are actually used by which binary and move them between packages - somewhat similar to how I moved files between samba-libs and python3-samba packages. When I did 4.16 initially I didn't think much about that aspect, b/c else we'd not have 4.16 now :) Now when I looked at this, I don't see why libsamba-util.so is in there at all. Maybe in 4.13 there was a reason for that, I don't know the reason for it to be there for 4.16. The rest (in /samba/) are ones used by libsamba-utils, it seems. /mjt There have been regressions in the past, so if only expressed in packaging this might be historical.
Bug#1011609: bogl-bterm: [PATCH] Several improvements
Hi,
Changes in [PATCH V3]:
Please refer to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011609#30
Changes in [PATCH V4]:
Tiny improvement: detect 8K+ monitors and assign 8x scale factor for them.
Best Regards,
Zhang BoyangFrom 540b82ac07c5a582da3d6e6ad1cdc2fd83c36b2e Mon Sep 17 00:00:00 2001
From: Zhang Boyang
Date: Mon, 23 May 2022 14:10:52 +0800
Subject: [PATCH v4 1/4] Better font reload handling
Previous font reload code will leak a mmap on each reload. This patch
adds the ability to munmap old font after reload. However, this also
introduces a bug, if font reload is triggered while drawing in progress,
after signal handler returns, the drawing code will continue to use old
font which has been freed, causing crash. So the munmap is temporarily
disabled until we fix async-signal-safety problems completely.
---
bogl-bgf.c | 63 +++---
bogl-bgf.h | 1 +
bterm.c| 9
3 files changed, 55 insertions(+), 18 deletions(-)
diff --git a/bogl-bgf.c b/bogl-bgf.c
index 1032028..beed3c8 100644
--- a/bogl-bgf.c
+++ b/bogl-bgf.c
@@ -5,38 +5,55 @@
#include
#include
#include
+#include
#include "bogl.h"
#include "boglP.h"
#include "bogl-font.h"
+#include "bogl-bgf.h"
+
+struct bogl_bgf {
+ void *f;/* mmap area */
+ off_t size; /* size of mmap area */
+ struct bogl_font font; /* font descriptor */
+};
+#define bgf_of(font) \
+ ((struct bogl_bgf *)((char *)(font) - offsetof(struct bogl_bgf, font)))
struct bogl_font *bogl_mmap_font(char *file)
{
- int fd;
+ struct bogl_bgf *bgf = NULL;
+ struct bogl_font *font = NULL;
+ int fd = -1;
struct stat buf;
- void *f;
- struct bogl_font *font;
+ void *f = MAP_FAILED;
+
+ bgf = (struct bogl_bgf *)malloc(sizeof(struct bogl_bgf));
+ if (!bgf)
+goto fail;
+ font = >font;
fd = open(file, O_RDONLY);
if (fd == -1)
-return 0;
+goto fail;
if (bogl_cloexec(fd) < 0)
-return 0;
+goto fail;
if (fstat(fd, ))
-return 0;
+goto fail;
+ bgf->size = buf.st_size;
+
+ if (buf.st_size < 4)
+goto fail;
f = mmap(0, buf.st_size, PROT_READ, MAP_SHARED, fd, 0);
- if (f == (void *)-1)
-return 0;
+ if (f == MAP_FAILED)
+goto fail;
+ bgf->f = f;
if (memcmp("BGF1", f, 4))
-return 0;
-
- font = (struct bogl_font *)malloc(sizeof(struct bogl_font));
- if (!font)
-return 0;
+goto fail;
memcpy(font, f + 4, sizeof(*font));
font->name = ((void *)font->name - (void *)0) + f;
@@ -44,5 +61,25 @@ struct bogl_font *bogl_mmap_font(char *file)
font->index = ((void *)font->index - (void *)0) + f;
font->content = ((void *)font->content - (void *)0) + f;
+done:
+ if (fd != -1)
+close(fd);
return font;
+
+fail:
+ if (bgf) {
+free(bgf);
+bgf = NULL;
+font = NULL;
+ }
+ if (f != MAP_FAILED)
+munmap(f, buf.st_size);
+ goto done;
+}
+
+void bogl_munmap_font(struct bogl_font *font)
+{
+ struct bogl_bgf *bgf = bgf_of(font);
+ munmap(bgf->f, bgf->size);
+ free(bgf);
}
diff --git a/bogl-bgf.h b/bogl-bgf.h
index e9fb994..f14a260 100644
--- a/bogl-bgf.h
+++ b/bogl-bgf.h
@@ -1,2 +1,3 @@
struct bogl_font *bogl_mmap_font(char *file);
+void bogl_munmap_font(struct bogl_font *font);
diff --git a/bterm.c b/bterm.c
index 605644f..dfae8b9 100644
--- a/bterm.c
+++ b/bterm.c
@@ -224,11 +224,10 @@ void reload_font(int sig)
return;
}
- /* This leaks a mmap. Since the font reloading feature is only expected
- to be used once per session (for instance, in debian-installer, after
- the font is replaced with a larger version containing more characters),
- we don't worry about the leak. */
- free(term->font);
+ /* BUG: Unmapping old font in this signal handler may cause crash if
+ drawing is in progress, so disable this temporarily until we fix
+ async-signal-safety problems completely. */
+ //bogl_munmap_font(term->font);
term->font = font;
term->xstep = bogl_font_glyph(term->font, ' ', 0);
--
2.30.2
From b222a9a15b0a2706927ecde8ce163243b076bbcb Mon Sep 17 00:00:00 2001
From: Zhang Boyang
Date: Tue, 24 May 2022 12:58:01 +0800
Subject: [PATCH v4 2/4] Fix incorrect signal handling
There are problems in signal handlers. Signal handlers must not call any
non-async-signal-safe functions, and they must save-restore errno if
errno is modified inside signal handlers. This patch fixes these
problems by deferring real tasks to main loop. This patch also
introduces bogl_signal(), which wraps around sigaction() thus signal
handlers can be installed in a portable way. Since signal related
problems are fixed, the previously temporarily disabled font unmapping
is now re-enabled.
---
bogl.c | 50 +-
bogl.h | 2 ++
boglP.h | 2 ++
bterm.c | 35 +--
4 files changed, 54 insertions(+), 35 deletions(-)
diff --git a/bogl.c b/bogl.c
index 6b9996b..86bc1e0 100644
--- a/bogl.c
+++ b/bogl.c
@@
Bug#1012300: ITP:php-kelunik-certificate -- Access certificate details and transform between different formats
Package: wnpp * Package name: php-kelunik-certificate Upstream Author : Niklas Keller * License : MIT Description : Access certificate details and transform between different formats . Library to parse certificates and get information about validity a.o. Regards Katharina
Bug#1009290: [debian-mysql] Bug#1009290: mariadb-server-10.6: Fails to start on live system
Faustin,
DL> I will give this a try. I'm curious what filesystem the container uses.
$ podman exec -it sys-test findmnt -J /
{
"filesystems": [
{
"target": "/",
"source": "fuse-overlayfs",
"fstype": "fuse.fuse-overlayfs",
"options":
"rw,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other"
}
]
}
Dan
Urbana, Illinois
Bug#1012280: libcgal-demo: Please update suggested VTK version
Hi Francois, thanks for the report. This change also gets rid of a lot of cmake warnings related to VTK! I'll upload a fixed version later today. Best regards, Joachim
Bug#1012296: ITP:php-kelunik-certificate -- Access certificate details and transform between different formats
Package: wnpp * Package name: php-kelunik-certificate Upstream Author : Niklas Keller * License : MIT Description : Access certificate details and transform between different formats . Library to parse certificates and get information about validity a.o. Regards Katharina
Bug#1012295: RM: libisal [i386] -- ROM; FTBFS on i386
Package: ftp.debian.org Severity: normal Hi, Please remove libisal on the i386 arch. Indeed, it fails to build, because the package is trying to use non-32 bits assembler instructions. Considering what the package does (ie: Erasure coding acceleration) and the fact that there are alternatives (like jerasure) that are doing the exact same thing, I don't see the point spending more time supporting a specific arch. Also, it is very unlikely that someone will want to run such a very CPU intensive code on i386, without SSE registers, anyways. Cheers, Thomas Goirand (zigo)
Bug#1007222: transition: onetbb
Hello, On Wed, 1 Jun 2022 20:29:02 +0200 Graham Inggs wrote:> I noticed some packages in the tracker not appearing in your list; > e.g. openimageio, pcl and yade. These packages have transitive > build-dependencies on libtbb-dev through e.g. libopenvdb-dev or > libvtk9-dev, and should be investigated as well. I have ratt-rebuilt the reverse dependencies (I believe ratt catches the transitive ones). Here are my results: OK == actiona arc-theme asl auto-multiple-choice bcnc beads bowtie bowtie2 budgie-control-center cheese cimg darknet digikam embree empathy esys-particle eviacam f3d finalcif freecad frei0r gearhead2 gfpoken gmic gnome-dvb-daemon gnome-initial-setup gnome-mousetrap gnome-sound-recorder golang-github-thecreeper-go-notify gst-plugins-bad1.0 gstreamer-editing-services1.0 gstreamer-vaapi gst-rtsp-server1.0 gtk4 gudhi kdenlive kylin-scanner lammps libatomic-queue liggghts mathicgb mlt monado mrcal mrgingham mrpt netgen nheko node-opencv nomacs obs-advanced-scene-switcher octave-bim octave-msh odin oggvideotools onednn open3d opencfu opencv opendrop openqa openturns os-autoinst otb pcl planetary-system-stacker pmemkv pmemkv-python pragha psychopy ptl pulseeffects pygmsh pymatgen python-escript python-notify2 python-pcl pytorch pytorch-ignite q2-dada2 qimgv r-cran-luminescence r-cran-openmx r-cran-projpred r-cran-rcppparallel r-cran-rlumshiny r-cran-rstantools r-cran-semplot r-cran-stanheaders r-cran-treescape r-cran-treespace r-cran-uwot ros-image-pipeline ros-opencv-apps ros-perception-pcl ros-vision-opencv sayonara sdaps seer shotcut sight simple-whip-client siril skorch sunpy synfig synfigstudio sysdig therion tpot trinityrnaseq ukui-biometric-auth ukui-biometric-manager ukui-control-center ukui-greeter ukui-screensaver uprightdiff vecgeom vedo visp vtk9 willow yade FTBFS with TBB (bugs reported) == blender deal.ii flexbar gazebo libpmemobj-cpp opencascade openimageio opensubdiv openvdb r-bioc-dada2 r-cran-brms r-cran-lamw r-cran-markovchain r-cran-prophet r-cran-rstan r-cran-rstanarm r-cran-shinystan salmon slic3r-prusa tiny-dnn Unrelated FTBFS === freeture gmsh kicad limereg madness mldemos mpqc3 numba olive-editor opencolorio php-facedetect pigx-rnaseq pitivi plastimatch pytorch-audio pytorch-text pytorch-vision trilinos Unsatisfiable dependencies == hyperspy poliastro pynpoint python-cogent python-epimodels python-fluids python-loompy python-numpy-groupies python-pynndescent python-sparse sfepy tiledarray umap-learn Is this enough to remove 'moreinfo'? Best, Andrius
Bug#1012294: O: jsonnet -- data templating language
Package: wnpp Severity: normal Control: affects -1 src:jsonnet I intend to orphan the jsonnet package, because I'm not interested in it anymore. The package is currently in good shape. The package description is: A data templating language for app and tool developers . * Generate config data * Side-effect free * Organize, simplify, unify * Manage sprawling config . A simple extension of JSON . * Open source (Apache 2.0) * Familiar syntax * Reformatter, linter * Editor & IDE integrations * Formally specified . Eliminate duplication with object-orientation. Or, use functions. Integrate with existing / custom applications. Generate JSON, YAML, INI, and other formats. . This package ships the binary executable. Thank you for using reportbug
