Bug#757127: sudo-ldap segfaults if ldap is being used
On Tue, Aug 05, 2014 at 10:41:14AM -0400, Mauricio Tavares wrote: > 4) If anyone wants to be lazy, here is the patch as applied to > http://ftp.de.debian.org/debian/pool/main/s/sudo/sudo_1.8.9p5.orig.tar.gz > > diff -u sudo-1.8.9p5/plugins/sudoers/ldap.c ldap.c I see this in the sudo source in Debian unstable. Can you confirm that this issue doesn't apply any more to current Debian? Greetings Marc
Bug#983375: cysignals: reduce Build-Depends
Source: cysignals Version: 1.10.2+ds-5 Tags: patch User: debian-cr...@lists.debian.org Usertags: cross-satisfiability cysignals cannot be cross built from source, because it has unsatisfiable Build-Depends. It mostly separates the documentation build from an arch-only build already, but the sphinxdoc addon is still requested there. Please consider applying the attached patch to also move that to B-D-I. Beyond that it switches all dh addons to declarative syntax and drops the unused texlive-plain-generic. Helmut diff --minimal -Nru cysignals-1.10.2+ds/debian/changelog cysignals-1.10.2+ds/debian/changelog --- cysignals-1.10.2+ds/debian/changelog2020-11-15 23:50:46.0 +0100 +++ cysignals-1.10.2+ds/debian/changelog2021-02-23 08:09:24.0 +0100 @@ -1,3 +1,13 @@ +cysignals (1.10.2+ds-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Reduce Build-Depends: (Closes: #-1) ++ Declaratively request dh addons. ++ Demote sphinx dependencies to B-D-I. ++ Drop unused texlive-plain-generic. + + -- Helmut Grohne Tue, 23 Feb 2021 08:09:24 +0100 + cysignals (1.10.2+ds-5) unstable; urgency=medium [ Jreome Benoit ] diff --minimal -Nru cysignals-1.10.2+ds/debian/control cysignals-1.10.2+ds/debian/control --- cysignals-1.10.2+ds/debian/control 2020-11-15 23:27:01.0 +0100 +++ cysignals-1.10.2+ds/debian/control 2021-02-23 08:09:19.0 +0100 @@ -6,23 +6,23 @@ Rules-Requires-Root: no Build-Depends: debhelper-compat (= 12), + dh-sequence-python3, help2man, - dh-python, python3-setuptools, python3-all, python3-distutils, - python3-sphinx, libpython3-all-dev, cython3 (>= 0.28), libpari-dev (>= 2.9), gdb Build-Depends-Indep: + dh-sequence-sphinxdoc, python3-docutils, + python3-sphinx, latexmk, texlive-latex-base, texlive-latex-recommended, texlive-fonts-recommended, - texlive-plain-generic, texlive-latex-extra Standards-Version: 4.5.0 X-Python3-Version: >= 3.6 diff --minimal -Nru cysignals-1.10.2+ds/debian/rules cysignals-1.10.2+ds/debian/rules --- cysignals-1.10.2+ds/debian/rules2019-10-26 10:23:37.0 +0200 +++ cysignals-1.10.2+ds/debian/rules2021-02-23 08:08:35.0 +0100 @@ -16,7 +16,7 @@ @uscan --no-conf --dehs --report || true %: - dh $@ --with python3 --with sphinxdoc --buildsystem=pybuild + dh $@ --buildsystem=pybuild override_dh_auto_configure-arch: $(call adhoc_dh_auto_configure_do,bare)
Bug#983374: cvxopt: separate documentation dependencies to B-D-I
Source: cvxopt Version: 1.2.5+dfsg-3 Tags: patch User: debian-cr...@lists.debian.org Usertags: cross-satisfiability cvxopt cannot be cross built from source, because its Build-Depends are not satisfiable. It already separates its documentation to a -doc package and skips the documentation build during an arch-only build, however it still requires the sphinxdoc addon for arch-only builds and requires all the documentation dependencies as well. Please consider applying the attached patch to fully separate them. In the process, I also dropped the entirely unused texlive-plain-generic and converted both dh addons to the declarative dependency style. Helmut diff --minimal -Nru cvxopt-1.2.5+dfsg/debian/changelog cvxopt-1.2.5+dfsg/debian/changelog --- cvxopt-1.2.5+dfsg/debian/changelog 2020-10-15 19:29:19.0 +0200 +++ cvxopt-1.2.5+dfsg/debian/changelog 2021-02-23 07:58:41.0 +0100 @@ -1,3 +1,10 @@ +cvxopt (1.2.5+dfsg-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Separate documentation dependencies to B-D-I. (Closes: #-1) + + -- Helmut Grohne Tue, 23 Feb 2021 07:58:41 +0100 + cvxopt (1.2.5+dfsg-3) unstable; urgency=medium * Team upload diff --minimal -Nru cvxopt-1.2.5+dfsg/debian/control cvxopt-1.2.5+dfsg/debian/control --- cvxopt-1.2.5+dfsg/debian/control2020-10-14 14:04:55.0 +0200 +++ cvxopt-1.2.5+dfsg/debian/control2021-02-23 07:58:38.0 +0100 @@ -5,24 +5,24 @@ Testsuite: autopkgtest-pkg-python Priority: optional Build-Depends: debhelper-compat (= 13), - dh-python, + dh-sequence-python3, dvipng, libblas-dev, liblapack-dev, - python3-sphinx, - latexmk, libglpk-dev, libfftw3-dev, libgsl-dev, libdsdp-dev, - texlive-latex-base, - texlive-latex-recommended, - texlive-latex-extra, - texlive-fonts-recommended, - texlive-plain-generic, python3-all-dev, - python3-sphinx-rtd-theme, python3-setuptools +Build-Depends-Indep: dh-sequence-sphinxdoc, + python3-sphinx, + latexmk, + texlive-latex-base, + texlive-latex-recommended, + texlive-latex-extra, + texlive-fonts-recommended, + python3-sphinx-rtd-theme, Standards-Version: 4.5.0 Rules-Requires-Root: no Vcs-Browser: https://salsa.debian.org/science-team/cvxopt diff --minimal -Nru cvxopt-1.2.5+dfsg/debian/rules cvxopt-1.2.5+dfsg/debian/rules --- cvxopt-1.2.5+dfsg/debian/rules 2020-10-15 17:28:46.0 +0200 +++ cvxopt-1.2.5+dfsg/debian/rules 2021-02-23 07:57:33.0 +0100 @@ -8,7 +8,7 @@ export PYBUILD_TEST_ARGS=-s tests %: - dh $@ --with python3,sphinxdoc --buildsystem=pybuild + dh $@ --buildsystem=pybuild override_dh_auto_clean: dh_auto_clean @@ -19,11 +19,9 @@ find debian/python*-cvxopt -name cvxopt -type d -empty -delete override_dh_auto_build-indep: -ifeq (,$(filter nodoc,$(DEB_BUILD_OPTIONS))) # $(pyrun) 'make --directory=doc html latex' make --directory=doc html latex make --directory=doc/build/latex all-pdf -endif override_dh_auto_test-indep:
Bug#983373: gzip-win32: Link gzip.exe with static libssp library
Package: gzip-win32 Version: 1.10-2 Severity: serious Affects: win32-loader Tags: d-i pending Owner: Milan Kupcevic Submitter: Thomas Gaugler Merge request opened 6 months ago by Thomas Gaugler: I noticed that gzip-win32 1.10-2 depends on the libssp-0.dll dynamic link library. Therefore gzip.exe is no longer able to run standalone within win32-loader.exe. wine also exhibits the issue: $ wine gzip.exe 0009:err:module:import_dll Library libssp-0.dll (which is needed by L"Z:\\tmp\\gzip.exe") not found 0009:err:module:attach_dlls Importing dlls for L"Z:\\tmp\\gzip.exe" failed, status c135 The proposed patch links gzip.exe with the static libssp library. From: Thomas Gaugler Date: Wed, 5 Aug 2020 20:32:39 +0200 Subject: [PATCH] Link gzip.exe with static libssp library --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 2861a82..a82aacf 100755 --- a/debian/rules +++ b/debian/rules @@ -76,7 +76,7 @@ configure-indep-stamp: reconf-stamp dh_testdir mkdir -p builddir-indep cd builddir-indep && ../configure --host=i686-w64-mingw32 \ - LIBS="-Wl,--as-needed -lssp" --disable-silent-rules + LIBS="-l:libssp.a" --disable-silent-rules :>$@ build: build-stamp build-indep-stamp -- 2.20.1
Bug#976801: Bug#982871: lintian-brush: Should not set "Testsuite: autopkgtest-pkg-perl" if debian/tests/control is present
Hi Felix, On 2021-02-16 12:29, Felix Lechner wrote: > On Mon, Feb 15, 2021 at 10:45 PM Andrius Merkys wrote: >> >> I filed that as a bug in lintian, #976801. > > Your bug was resolved for both teams in Git on the day you filed. It > was not marked pending, however, because I accidentally appended a > digit to the bug number in the commit message. (I had just started to > use a keyboard layout [1] that reverses the Shift function on digits > for easier access to the symbols; the closing parenthesis became a > zero.) Here is the corresponding commit: > > > https://salsa.debian.org/lintian/lintian/-/commit/920143ae57ed8b7607ac3160ba8f7ef766b3407a Thank you for letting me know! > Please note that, in any event, the fix came too late for 'bullseye'. > In consideration of public opinion, we are not presently updating > Lintian in the archive. [2] Thank you! Sure, no problem. > [1] https://salsa.debian.org/lechner/rocket-layout > [2] https://lists.debian.org/debian-devel/2021/01/msg00236.html Best wishes, Andrius
Bug#983372: linux-image-5.10.0-3-amd64: Graphic glitches / distortions when using Desktop (Plasma / KDE)
Package: src:linux X-Debbugs-Cc: user2...@web.de Version: 5.10.13-1 Severity: important Dear Maintainer, i encountered weired graphical glitches on my desktop / opened programmes after one of the last "apt-get dist-upgrade" (KDE / Plasma) After searching the web maybe same as https://bugzilla.redhat.com/ show_bug.cgi?id=1843274, an screenshot-video of the behaviour can be found at https://www.reddit.com/r/Fedora/comments/ll8lh5/ weird_graphical_glitches_on_fedora_33/ (not mine, but similar) *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? > Possibly update to one of the latest testing-kernel * What exactly did you do (or not do) that was effective (or ineffective)? > Grub-Option "i915.mitigations=off" seems to work as a workaround, but is obviously no solution * What was the outcome of this action? > No glitches * What outcome did you expect instead? -- Package-specific info: ** Version: Linux version 5.10.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.13-1 (2021-02-06) ** Command line: BOOT_IMAGE=/vmlinuz-5.10.0-3-amd64 root=/dev/# ro quiet i915.mitigations=off ** Hardware Thinkpad T440p Intel Core I7-4700mq -- System Information: Debian Release: bullseye/sid Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.10.0-3-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.139 ii kmod28-1 ii linux-base 4.6 Versions of packages linux-image-5.10.0-3-amd64 recommends: ii apparmor 2.13.6-9 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.10.0-3-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.04-15 pn linux-doc-5.10 Versions of packages linux-image-5.10.0-3-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- mail: user2...@web.de
Bug#983352: htop: Hardware dependent?
Control: forwarded -1 https://github.com/htop-dev/htop/issues/529 Am 22.02.21 um 22:43 schrieb rv: Hope I'm not spamming... Your bug report is of high quality and thus definitely not spam. But you had already found the upstream bug report and reported your info there, too. That is more useful than a Debian bug as there is nothing we can do about this via packaging htop better. After the bullseye release there will be more users with VIA Eden or AMD Phenom processors where htop does currently not show temperatures. So may be they find this bug and not create duplicates. We can always hope :).
Bug#983371: linux: backport binfmt_misc: pass binfmt_misc flags to the interpreter
Package: src:linux Version: 5.10.13-1 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20210222=2347961b11d4079deace3c81dceed460c08a8fc1 This patch is for qemu to be aware whether P flag is set. -- YunQiang Su
Bug#970460: fixed in qemu 1:5.2+dfsg-6
On Tue, 16 Feb 2021 13:11:15 + (UTC) Thorsten Glaser wrote: > Debian FTP Masters dixit: > > > * fix the brown-paper bag bug: wrong argument order > > in the linux-user-binfmt patch (really closes: #970460) > > Confirmed, thanks! The new kernel patch to pass P flag info by auxval has launched in Linux-next. > > bye, > //mirabilos > -- > "Using Lynx is like wearing a really good pair of shades: cuts out >the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL." > -- Henry Nelson, March 1999 > >
Bug#983345: therion: FTBFS with PROJ 8.0.0
On 2/22/21 11:42 PM, Wookey wrote: > On 2021-02-22 18:23 +0100, Bas Couwenberg wrote: >> Your package FTBFS with PROJ 8.0.0, it hung at `make samples`: >> faketime "" /usr/bin/make samples > > This is an issue with faketime, which was added to make the package > reproducible. For some reason I don't understand it works on the > buildds bug hangs under a local sbuild build unless you do that build > as root. > > Fiddling with Rule-Requires-Root doesn't seem to affect this. > > So I am pretty certain that this is an artifact of the way you are > doing the build test, rather than a genuine issue with Proj v8. > > I would like to remove this issue because I have to remember to do > builds as root. Knowing why it works OK on the real buildds would be helpful. You can close this issue as notfound if you can confirm that it builds successfully with proj from experimental. I don't use sbuild. I used pdebuild with --use-pdebuild-internal to not require the build dependencies outside the chroot for the clean target. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#983370: uim-anthy: does not respect UTF-8
Package: uim-anthy Version: 1:1.8.8-7 Followup-For: Bug #983370 Control: tags -1 +patch Dear Maintainer, I have created a merge request to fix this problem. https://salsa.debian.org/debian/uim/-/merge_requests/13 Thanks in advance, -- YOSHINO Yoshihito -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/1 CPU thread) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 uim-anthy depends on: ii anthy 1:0.4-2 ii uim 1:1.8.8-7 ii uim-data 1:1.8.8-7 uim-anthy recommends no packages. uim-anthy suggests no packages. -- no debconf information
Bug#983370: uim-anthy: does not respect UTF-8
Package: uim-anthy Version: 1:1.8.8-7 Severity: important Dear Maintainer, uim-anthy installs EUC-JP (anthy) and UTF-8 (anthy-utf8) modules. However, the module order does not respect UTF-8: currently anthy EUC-JP module is the default. This is critical to normal UTF-8 installations. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/1 CPU thread) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 uim-anthy depends on: ii anthy 1:0.4-2 ii uim 1:1.8.8-7 ii uim-data 1:1.8.8-7 uim-anthy recommends no packages. uim-anthy suggests no packages. -- no debconf information
Bug#963197: sudo: listpw=never is broken
bug not present on stretch 9,
bug appears upon stretch 9 --> buster 10 upgrade, (breaking existing
functionality, hence I'd advocate Severity: important, however there does
exist workaround, so Severity debatable)
bug still present with sudo 1.8.27-1+deb10u3 on buster 10.8
bug not present with sudo 1.9.5p2-2 on bullseye
bug still present with sudo 1.8.27-1+deb10u3 on buster 10.8,
demonstration (minimal example relative to defaults):
# dpkg -l sudo 2>&1 | awk '{if($1=="ii")print $2,$3;}'
sudo 1.8.27-1+deb10u3
# cat /etc/debian_version
10.8
# awk '{if(NF>=1 && $1 !~ /^#/ )print;}' /etc/sudoers /etc/sudoers.d/*
Defaultsenv_reset
Defaultsmail_badpass
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
Defaultslistpw=never
rootALL=(ALL:ALL) ALL
%sudo ALL=(ALL:ALL) ALL
# su - michael
$ sudo -l
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for michael:
Expected behavior - it shouldn't prompt for password, per sudoers(5):
SUDOERS(5) BSD File Formats Manual SUDOERS(5)
listpwThis option controls when a password will be required when
never The user need never enter a password to use the
-l option.
bug not present with sudo 1.9.5p2-2 on bullseye:
# dpkg -l sudo 2>&1 | awk '{if($1=="ii")print $2,$3;}'
sudo 1.9.5p2-2
# cat /etc/debian_version
bullseye/sid
# awk '{if(NF>=1 && $1 !~ /^#/ )print;}' /etc/sudoers /etc/sudoers.d/*
Defaultsenv_reset
Defaultsmail_badpass
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
Defaultslistpw=never
rootALL=(ALL:ALL) ALL
%sudo ALL=(ALL:ALL) ALL
@includedir /etc/sudoers.d
# su - michael
$ sudo -l
Sorry, user michael may not run sudo on small.
$
From upstream we have:
https://bugzilla.sudo.ws/show_bug.cgi?id=869
If I add listpw=never in sudoers and run sudo -l it always ask for
user's password.
The workaround I found was to add a new entry with NOPASSWD: to that
user letting it to run /usr/bin/false and change listpw to any.
https://www.sudo.ws/changes.html
2019-01-22 Todd C. Miller
* plugins/sudoers/parse.c:
Fix listpw=never and verifypw=never. Bug #869
[ecb89088a884]
And that and similar workarounds appear to work.
Workaround:
E.g. applying and
testing workaround to
sudo 1.8.27-1+deb10u3 on buster 10.8 as otherwise shown above:
# dpkg -l sudo 2>&1 | awk '{if($1=="ii")print $2,$3;}'
sudo 1.8.27-1+deb10u3
# cat /etc/debian_version
10.8
# SUDO_EDITOR=ed visudo
691
/listpw
Defaultslistpw=never
d
w
669
q
# SUDO_EDITOR=ed visudo -f /etc/sudoers.d/local
0a
ALL ALL=(nobody:nogroup) NOPASSWD: /bin/true ""
.
w
48
q
# awk '{if(NF>=1 && $1 !~ /^#/ )print;}' /etc/sudoers /etc/sudoers.d/*
Defaultsenv_reset
Defaultsmail_badpass
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
rootALL=(ALL:ALL) ALL
%sudo ALL=(ALL:ALL) ALL
ALL ALL=(nobody:nogroup) NOPASSWD: /bin/true ""
# su - michael
$ sudo -l
Matching Defaults entries for michael on small:
env_reset, mail_badpass,
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin
User michael may run the following commands on small:
(nobody : nogroup) NOPASSWD: /bin/true \"\"
$
"Of course" this requires the otherwise spurious sudo command to be added
to the configuration, but as far as I've been able to tell from what
I've read and tested, as long as the user has access to so much as a
least one NOPASSWD command, if listpw is set to any (or defaults to
such), for that(/those) user(s), it will behave as if listpw=never were
set (at least for that/those users).
Thanks.
From: "Marc Haber"
Subject: Re: Bug#963197: sudo: listpw=never is broken
Date: Mon, 22 Feb 2021 17:06:36 +0100
tags #963197 unreproducible
severity #963197 normal
thanks
Hi Michael,
On Sat, Jun 20, 2020 at 12:06:52PM +, Michael Paoli wrote:
* justification for Severity: (>=) important:
Broken in buster (stable) (at least 1.8.27-1+deb10u2).
I don't agree with that justification, reducing to normal. This issue is
unlikely to be fixed in buster.
Works for me:
|[2/2568]mh@testbuster83:~ $ sudo -l
|Matching Defaults entries for mh on testbuster83:
|env_reset, mail_badpass,
|
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin
|
|User mh may run the following commands on testbuster83:
|(ALL : ALL) ALL
|[3/2568]mh@testbuster83:~ $
I cannot make sense of that. What exactly does sudo not do as
documented?
Can you please verify that sudo 1.9.5p2 in bullseye/sid performs as
expected? If you don't reply, I plan to close this issue by the end of
Bug#983369: linphone-desktop: chat msgs and (missed) incoming calls dates are wrong
Package: linphone-desktop Version: 4.2.5-3 Severity: normal Tags: upstream Dear Maintainer, In the chat room 'panel', the date is wrong, although times are correct, wether for chat msgs or missed incoming call 'reports' The app centers the date, and today (Feb 22, 2021) it says -- Sunday, February 21, 2021 -- Thanks, David -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linphone-desktop depends on: ii libbctoolbox1 4.4.13-2 ii libbelcard14.4.13-2 ii libc6 2.31-9 ii libgcc-s1 10.2.1-6 ii liblinphone++104.4.21-1 ii liblinphone10 4.4.21-1 ii libmediastreamer11 1:4.4.21-3 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus55.15.2+dfsg-4 ii libqt5gui5 5.15.2+dfsg-4 ii libqt5network5 5.15.2+dfsg-4 ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-4 ii libqt5quick5 5.15.2+dfsg-4 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5svg5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-4 ii libstdc++6 10.2.1-6 ii linphone-common4.4.21-1 ii qml-module-qt-labs-platform5.15.2+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-dialogs 5.15.2-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-4 ii qml-module-qtquick-window2 5.15.2+dfsg-4 ii qml-module-qtquick25.15.2+dfsg-4 linphone-desktop recommends no packages. linphone-desktop suggests no packages. -- no debconf information
Bug#983368: linphone-desktop: 'About' version numbers are wrong
Package: linphone-desktop Version: 4.2.5-3 Severity: normal Dear Maintainer, The 'Settings - About' dialog reports Desktop - Qt5.15.2 Core 4.4.0 But it should be Desktop 4.2.5-3 - Qt5.15.2 Core 4.4.21-1 Thanks, David -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linphone-desktop depends on: ii libbctoolbox1 4.4.13-2 ii libbelcard14.4.13-2 ii libc6 2.31-9 ii libgcc-s1 10.2.1-6 ii liblinphone++104.4.21-1 ii liblinphone10 4.4.21-1 ii libmediastreamer11 1:4.4.21-3 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus55.15.2+dfsg-4 ii libqt5gui5 5.15.2+dfsg-4 ii libqt5network5 5.15.2+dfsg-4 ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-4 ii libqt5quick5 5.15.2+dfsg-4 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5svg5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-4 ii libstdc++6 10.2.1-6 ii linphone-common4.4.21-1 ii qml-module-qt-labs-platform5.15.2+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-dialogs 5.15.2-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-4 ii qml-module-qtquick-window2 5.15.2+dfsg-4 ii qml-module-qtquick25.15.2+dfsg-4 linphone-desktop recommends no packages. linphone-desktop suggests no packages. -- no debconf information
Bug#983367: gvfs: autopkg test always fails on qemu testbed
Source: gvfs Version: 1.46.2-1 Severity: normal Tags: sid bullseye Dear Maintainer, I made an autopkg qemu testbed by debci setup -f -s sid -a amd64 -b qemu. Then I run autopkgtest -B -U -u debci gvfs -- qemu It always fails with autopkgtest [11:13:45]: test integration: [--- We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper sudo: a password is required autopkgtest [11:13:46]: test integration: ---] autopkgtest [11:13:46]: test integration: - - - - - - - - - - results - - - - - - - - - - integration FAIL non-zero exit status 1 This seems a bug in testsuite. The log is attached. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.16-preempt (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled gvfs-log.tar.xz Description: application/xz
Bug#983366: linphone-desktop: Settings popup menu
Package: linphone-desktop Version: 4.2.5-3 Severity: normal Dear Maintainer, * What led up to the situation? 1- the settings pop menu appears 'detached' from the main app window; also, it uses a font and font size that are not the 'upstream' app font and size (fwiw); 2- it only works once: if you close and try to open the settingss popup again, it fails to do so, and displays the following message in the teminal where i launched linphone; (linphone:83987): Gdk-WARNING **: 23:13:05.180: Couldn't map as window 0x555cd9b47560 as popup because it doesn't have a parent Thanks, David -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linphone-desktop depends on: ii libbctoolbox1 4.4.13-2 ii libbelcard14.4.13-2 ii libc6 2.31-9 ii libgcc-s1 10.2.1-6 ii liblinphone++104.4.21-1 ii liblinphone10 4.4.21-1 ii libmediastreamer11 1:4.4.21-3 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus55.15.2+dfsg-4 ii libqt5gui5 5.15.2+dfsg-4 ii libqt5network5 5.15.2+dfsg-4 ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-4 ii libqt5quick5 5.15.2+dfsg-4 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5svg5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-4 ii libstdc++6 10.2.1-6 ii linphone-common4.4.21-1 ii qml-module-qt-labs-platform5.15.2+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-dialogs 5.15.2-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-4 ii qml-module-qtquick-window2 5.15.2+dfsg-4 ii qml-module-qtquick25.15.2+dfsg-4 linphone-desktop recommends no packages. linphone-desktop suggests no packages. -- no debconf information
Bug#930210: I've found a solution.
This problem can be solved by manually installing the "fcitx-tools" package. Also, I thought this package should be a dependency on "fcitx- libpinyin", but it's not. -- Zheng Xueke
Bug#983365: linphone-desktop: chat messages
Package: linphone-desktop Version: 4.2.5-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, 1- chat messages (history) are not displayed when I launch the app, although I can see they are in the .local/share/linphone/linphone.db file (using sqliteb or sqlitebrowser); 2- when someone sends me a message, it 'pops' a notification with the message text (even if I am in front of the app) but the message is not displayed by the application itself, nor the little numbered circle that appears (on the appimage 4.2.5 version, to compare) i the left panel, in(on top of) the user 'entry', nor in the user chat 'room'. I also verified that the message isn't added in the chat_message_content of the linphone.db table, and i can see the following 'trace' in the terminal i used to launchh the app: [22:11:12:653][0x1ff9eb0][Info]components/sip-addresses/SipAddressesModel.cpp:485: "Update (`sip:sender.na...@sip.linphone.org`, `sip:my.n...@sip.linphone.org`) from chat message." Thanks, David -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linphone-desktop depends on: ii libbctoolbox1 4.4.13-2 ii libbelcard14.4.13-2 ii libc6 2.31-9 ii libgcc-s1 10.2.1-6 ii liblinphone++104.4.21-1 ii liblinphone10 4.4.21-1 ii libmediastreamer11 1:4.4.21-3 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus55.15.2+dfsg-4 ii libqt5gui5 5.15.2+dfsg-4 ii libqt5network5 5.15.2+dfsg-4 ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-4 ii libqt5quick5 5.15.2+dfsg-4 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5svg5 5.15.2-2 ii libqt5widgets5 5.15.2+dfsg-4 ii libstdc++6 10.2.1-6 ii linphone-common4.4.21-1 ii qml-module-qt-labs-platform5.15.2+dfsg-2 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtquick-controls5.15.2-2 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-dialogs 5.15.2-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-4 ii qml-module-qtquick-window2 5.15.2+dfsg-4 ii qml-module-qtquick25.15.2+dfsg-4 linphone-desktop recommends no packages. linphone-desktop suggests no packages. -- no debconf information
Bug#983364: postfix: autopkg test failure only on the qemu testbed
Source: postfix Version: 3.5.6-1 Severity: important Tags: sid bullseye Dear Maintainer, I made a qemu autopkg testbed by debci setup -f -s sid -a amd64 -b qemu. Then autopkgtest -U -B -u debci postfix -- qemu always fails with ...F... == FAIL: test_10_sending_mail_direct_auth (__main__.PostfixTest) Mail authentication -- Traceback (most recent call last): File "/tmp/autopkgtest.4Xod7n/build.X4K/src/debian/tests/test-postfix.py", line 328, in test_10_sending_mail_direct_auth self.assertRaises(smtplib.SMTPAuthenticationError, self.s.login, 'root', 'crapcrapcrap') AssertionError: SMTPAuthenticationError not raised by login -- It seems a real error in postfix. On the other hand, the testsuite always passes on the lxc testbed and ci.debian.net. If the maintainer considers this as a bug in autopkgtest, please reassign this. The log is attached. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.16-preempt (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled postfix-log.tar.xz Description: application/xz
Bug#983363: unattended-upgrades: autopkg test failure only on qemu testbed
Source: unattended-upgrades
Version: 2.8
Severity: important
Tags: sid bullseye
Dear Maintainer,
I made a qemu autopkg testbed by debci setup -f -s sid -a amd64 -b qemu.
Then the test suite in unattended-upgrades 2.8 always fails with
autopkgtest [09:56:54]: test kernel-patterns: [---
DEBUG:root:Package linux-image-5.10.0-3-amd64-dbg matched linux.*-5\.10\.0\-3
and .*5\.10\.0\-3\-amd64, but did not match
re.compile('(^linux-.*-5\\.10\\.0\\-3\\-amd64$|^linux-.*-5\\.10\\.0\\-3$|^kfreebsd-.*-5\\.10\\.0\\-3\\-amd64$|^kfreebsd-.*-5\\.10\\.0\\-3$|^gnumach-.*-5\\.10\\.0\\-3\\-amd64$|^gnumach-.*-5\\.10\\.0\\-3$|^.*-modu)
DEBUG:root:Package linux-image-5.10.0-3-amd64-unsigned matched
linux.*-5\.10\.0\-3 and .*5\.10\.0\-3\-amd64, but did not match
re.compile('(^linux-.*-5\\.10\\.0\\-3\\-amd64$|^linux-.*-5\\.10\\.0\\-3$|^kfreebsd-.*-5\\.10\\.0\\-3\\-amd64$|^kfreebsd-.*-5\\.10\\.0\\-3$|^gnumach-.*-5\\.10\\.0\\-3\\-amd64$|^gnumach-.*-5\\.10\\.0\\-3$|^.*-modu)
F
==
FAIL: test_versioned (__main__.TestKernelPatterns)
kernel package patterns should cover versioned packages
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.ODZ97z/build.j9G/src/test/autopkgtest_kernel_patterns.py",
line 51, in test_versioned
self.assertTrue(not not_matched,
AssertionError: False is not true : kernel packages not matched:
linux-image-5.10.0-3-amd64-unsigned linux-image-5.10.0-3-amd64-dbg
--
Ran 1 test in 0.543s
FAILED (failures=1)
This seems a real error.
The log is attached.
Best regards, Ryutaroh Matsumoto
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.16-preempt (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
unattended-upgrades-log.tar.xz
Description: application/xz
Bug#980686: ldc: FTBFS: dh_auto_configure: error: cd bootstrap-stage2
Hi Ivo! Am Di., 23. Feb. 2021 um 00:03 Uhr schrieb Ivo De Decker : > > Hi Matthias, > > On Wed, Jan 20, 2021 at 09:48:32PM +0100, Lucas Nussbaum wrote: > > Source: ldc > > Version: 1:1.24.0-1 > > Severity: serious > > Justification: FTBFS on amd64 > > Tags: bullseye sid ftbfs > > Usertags: ftbfs-20210120 ftbfs-bullseye > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > Are you aware of this bug? Looking at > https://tests.reproducible-builds.org/debian/history/ldc.html > it seems the change that triggered it must have been uploaded fairly recently > (probaby in January). No I didn't, thanks for the ping! The problem is dpkg adding DFLAGS="-frelease" to the environment, which messes up ldmd2. I'll have a look at fixing that. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#983362: libnfs: autopkg testsuite always fails
Source: libnfs Version: 4.0.0-1 Severity: normal Tags: sid bullseye Dear Maintainer, I made a qemu testbed by debci setup -f -s sid -a amd64 -b qemu. Then I run autopkgtest -B -U -u debci libnfs -- qemu The testsuite always fails with the following message We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper sudo: a password is required The log is attached. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.16-preempt (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled libnfs.tar.xz Description: application/xz
Bug#983360: multipath-tools: autopkgtest failure on the qemu testbed
Source: multipath-tools Version: 0.8.5-1 Severity: important Tags: bullseye sid Dear Maintainer, I run autopkgtest -U -B -u debci mutipath-tools -- qemu with a testbed made by debci setup -f -s sid -a amd64 -b qemu. The testsuite gives kpartx-file-loopback FAIL stderr: Warning: Partition table header claims that the size of partition table tgtbasedmpaths FAIL non-zero exit status 1 Looking at the log, failure of tgtbasedmpaths seems a real error. The log is attached. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.16-preempt (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled multipath-tools-autopkgtest.tar.xz Description: application/xz
Bug#983361: global.c: update the file
Source: nn Version: 6.7.3-14 Severity: normal Tags: patch Dear Maintainer, changes made: Define "active_directory". Define a name for a constant number and substitute the name for that number. Improve prototypes by adding declarations to the argument list. Use the "n"-version of "sprintf" and "vsprintf". Create a new directory "active_directory" if not existent. Use "invalid" instead of "illegal", see GNU standard. Add text to some messages. Remove the "NEED_STRDUP" configuration constant and the associated code for the definition of "strdup". The patch is in the attachment. Signed-off-by: Bjarni Ingi Gislason --- global.c | 103 ++- 1 file changed, 56 insertions(+), 47 deletions(-) -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.9-1 (SMP w/2 CPU threads) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- debconf information excluded -- Bjarni I. Gislason 0001-global.c-update-file.txt.gz Description: application/gzip
Bug#829321:
I was unable to reproduce this. If it still happens with Emacs 27.1, I encourage you to send a complete, minimal example to the Emacs developers using M-x report-emacs-bug.
Bug#972885:
Gnus no longer exists outside of Emacs. I suggest you report this with M-x report-emacs-bug. I note that `article' is not documented as one of the variables one can use in `gnus-summary-highlight'.
Bug#983349: hplip: while scanning , error 9 : impossible to scan
On Mon 22 Feb 2021 at 22:17:52 +0100, alain wrote: > Package: hplip > Version: 3.21.2+dfsg1-1 > Followup-For: Bug #983349 > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr > > your command : simple-scan escl:http://127.0.0.1:6 was nearly ok . > > simple-scan started to connect and , quickly , closed itself : "cannot > connect" That is a possible upstream bug in SANE for this device. > i've read your texts . > > the only thing i understood is that usb connections has become now like > network > connections > > alain@sid:~$ lsusb -v | grep -A 3 bInterfaceClass.*7 > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 4 > iInterface 0 > -- > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 2 Bidirectional > iInterface 0 > -- > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 4 > iInterface 0 > can't get debug descriptor: Resource temporarily unavailable > Couldn't open device, some information will be missing > -- > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 4 > iInterface 0 > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > Couldn't open device, some information will be missing > > new ipp-over-usb seems to be not compatible with libsane-hpaio (my driver) ipp-usb has taken control of the USB endpoints detailed above and libsane-hpaio is unable to access them. This is a consquence of how IPP-over-USB interworks with USB. It is not a bug in either ipp-usb or libsane-hpaio. > so i have a big problem . > > don't know the solution . Please install sane-airscan and give scanimage -L Cheers, Brian.
Bug#956443:
I can reproduce this with current Emacs master. I encourage you to report this to the Emacs developers using M-x report-emacs-bug.
Bug#983297: Substitute "mktemp" with "mkstemp"
>From 9e118ddc9b66faa71e517117d7dc4349d9e9466f Mon Sep 17 00:00:00 2001 >From: Bjarni Ingi Gislason >Date: Mon, 22 Feb 2021 22:51:39 + >Subject: [PATCH] Remove declaration of "mkstemp" Warning from the compiler: cc -Iconf -Wall -c -o nntp.o nntp.c nntp.c:123:17: error: conflicting types for 'mkstemp' 123 | extern char*mkstemp(); | ^~~ In file included from nntp.c:17: /usr/include/stdlib.h:688:12: note: previous declaration of 'mkstemp' was here 688 | extern int mkstemp (char *__template) __nonnull ((1)) __wur; |^~~ nntp.c: Remove declaration of "mkstemp" as it is defined in , see "man 3 mktemp". contrib/rcmail.c: likewise Signed-off-by: Bjarni Ingi Gislason --- contrib/recmail.c | 2 +- nntp.c| 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/recmail.c b/contrib/recmail.c index 25e5f45..40dfe1f 100644 --- a/contrib/recmail.c +++ b/contrib/recmail.c @@ -48,7 +48,7 @@ extern char *getlogin(); extern char *getenv(); extern char *malloc(); -extern char *mkstemp(); +/* extern char *mkstemp(); defined in , see "man 3 mkstemp" */ extern struct passwd *getpwnam(); void get_host_name(); diff --git a/nntp.c b/nntp.c index c1bee4c..11327a4 100644 --- a/nntp.c +++ b/nntp.c @@ -120,7 +120,7 @@ int nntp_debug = 0; extern char*home_directory; extern int silent; -extern char*mkstemp(); +/* extern char*mkstemp(); defined in , see "man 3 mkstemp" */ static FILE*nntp_in = NULL;/* fp for reading from server */ static FILE*nntp_out = NULL;/* fp for writing to server */ -- 2.30.0 -- Bjarni I. Gislason
Bug#926025:
"X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139" is https://debbugs.gnu.org/37895 (amongst others) This is marked as fixed in Emacs 27.1. If the issue still occurs for you with Emacs 27.1, I suggest reporting it using M-x report-emacs-bug. Reporting Emacs bugs that aren't specific to Debian (eg packaging) as Debian bugs tends not to lead anywhere.
Bug#983301: mmdebstrap: --mode=chrootless fails with E: cannot open /etc/dpkg/dpkg.cfg.d/99mmdebstrap
Hi,
Quoting Tobias Frost (2021-02-22 09:04:41)
> I was playing with mmdebstrap to see if I could bootstrap a system even
> without dpkg,
> suitable for some embedded device… However, I could not get --mode=chrootless
> to work:
>
> I'm not sure if this is PEBKAC or a bug… If the former, I'd apprecicate some
> hints…
>
> (I ran this as root in a chroot env, bootstraped for convenience reasons with
> pbuilder;
> but I get the same results when doing that as non-root outside of a chroot.)
>
> The command I run:
>
> mmdebstrap --mode=chrootless --aptopt='Acquire::http { Proxy
> "http://10.243.48.3:3142;; }' --dpkgopt='path-exclude=/usr/share/man/*'
> --dpkgopt='path-include=/usr/share/man/man[1-9]/*'
> --dpkgopt='path-exclude=/usr/share/locale/*'
> --dpkgopt='path-include=/usr/share/locale/locale.alias'
> --dpkgopt='path-exclude=/usr/share/doc/*'
> --dpkgopt='path-include=/usr/share/doc/*/copyright'
> --dpkgopt='path-include=/usr/share/doc/*/changelog.Debian.*'
> --dpkgopt='path-exclude=/usr/share/{doc,info,man,omf,help,gnome/help}/*'
> --variant=essential --format=directory --architecture=armhf stable target2
> W: running chrootless mode as root might damage the host system
> I: skipping emulation check in chrootless mode
> E: cannot open /etc/dpkg/dpkg.cfg.d/99mmdebstrap: No such file or directory
> W: listening on child socket failed:
>
>
> root@isildor:~/mm# ls -la /etc/dpkg/dpkg.cfg.d/99mmdebstrap
> -rw-r--r-- 1 root root 0 Feb 22 07:56 /etc/dpkg/dpkg.cfg.d/99mmdebstrap
>
> root@isildor:~/mm# ls -la target2/etc/
> total 12
> drwxr-xr-x 3 root root 4096 Feb 22 07:56 .
> drwxr-xr-x 5 root root 4096 Feb 22 07:56 ..
> drwxr-xr-x 5 root root 4096 Feb 22 07:56 apt
>
> Possibly mmdeboostrap needs to copy this file to TARGET? Or do I need to do
> so with hooks?
I already explained in the other mail why chrootless mode is currently broken
due to missing support for DPKG_ROOT in debconf and other essential packages.
But even if support was there, what you try to do above would not work because
currently one cannot pass any other configuration than the one in /etc/dpkg to
dpkg. Since in chrootless mode, we never "chroot", dpkg will always use the
system configuration and completely ignore whatever you put into your chroot
using the --dpkgopt option.
I talked about this with guillem in #debian-dpkg on IRC and he is aware of the
issue but I don't think there is an open bug about this.
What we could do on the mmdebstrap side, is to warn the user or error out if
the user tries to run chrootless mode with --dpkgopt.
Thanks!
cheers, josch
signature.asc
Description: signature
Bug#980686: ldc: FTBFS: dh_auto_configure: error: cd bootstrap-stage2
Hi Matthias, On Wed, Jan 20, 2021 at 09:48:32PM +0100, Lucas Nussbaum wrote: > Source: ldc > Version: 1:1.24.0-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20210120 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Are you aware of this bug? Looking at https://tests.reproducible-builds.org/debian/history/ldc.html it seems the change that triggered it must have been uploaded fairly recently (probaby in January). Thanks, Ivo
Bug#983317: kcoreaddons: The libfam-dev build dependency should be [!linux-any]
Le lundi 22 février 2021, 12:30:46 CET Adrian Bunk a écrit : > Source: kcoreaddons > Version: 5.78.0-2 > Severity: normal Dear Adrian, > Unless I am misreading the code, the HAVE_FAM code is only > used as a fallback when inotify is not available. CMakeLists says the following : PURPOSE "Provides file alteration notification facilities using a separate service. FAM provides additional support for NFS.") I’ve not checked and am no specialist but is it not a valid fallback use case for it ? Happy hacking, -- Aurélien
Bug#983345: therion: FTBFS with PROJ 8.0.0
On 2021-02-22 18:23 +0100, Bas Couwenberg wrote: > Your package FTBFS with PROJ 8.0.0, it hung at `make samples`: > faketime "" /usr/bin/make samples This is an issue with faketime, which was added to make the package reproducible. For some reason I don't understand it works on the buildds bug hangs under a local sbuild build unless you do that build as root. Fiddling with Rule-Requires-Root doesn't seem to affect this. So I am pretty certain that this is an artifact of the way you are doing the build test, rather than a genuine issue with Proj v8. I would like to remove this issue because I have to remember to do builds as root. Knowing why it works OK on the real buildds would be helpful. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#983328: pandas: sparse test_from_coo fails with scipy 1.6.1
On 22/02/2021 12:44, Drew Parsons wrote: v1.2.2 is the latest pandas release Has this error in test_from_coo been fixed in that latest release? Not obviously, but I haven't tried actually running that. Is scipy 1.6.1 intended for bullseye?
Bug#941081: O: clipit -- lightweight GTK+ clipboard manager
control: retitle -1 ITA: clipit -- lightweight GTK+ clipboard manager control: owner -1 ! I've missed the point when this package was orphaned. I have a desire to pick it up since I use it all the time and developers didn't abandoned it. Let return it back into Debian on next cycle. Thank you.
Bug#983239: libbio-db-ncbihelper-perl: (autopkg)test failures when network is available
Hi Aaron, Hi Gregor, Aaron M. Ucko, on 2021-02-21 17:57:37 -0500: > Étienne Mollier writes: > > > I have been looking in the issue below in the package > > libbio-db-ncbihelper-perl. If I understood correctly, the main > > point of the package is to rely on resources made available on > > the Internet. > > I'm not sure I've been personally involved with this package, but that's > my understanding as well. > > > a perhaps magic index to refer to human genome, but maybe it is > > a "well known index".) > > Per [1], taxonomic ID *numbers* are stable in general, but the > associated *names* occasionally change to reflect improved > understandings of the underlying science. AFAICT from [2] (as linked > from [3]), this change is correct and legitimate; moreover, it looks > like 'Actinobacteria' should now appear in $n->common_names, if anyone > wants to verify that. > > [1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7408187/ > [2] > https://www.microbiologyresearch.org/content/journal/ijsem/10.1099/ijsem.0.003920 > [3] > https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?mode=Info=1760=3=f=1=1 Thank you very much! I humbly have to admit I know nothing to taxonomy classification, but it's nice to know that people try to keep improving one of the references. This was enough to brighten my day. :) Will see how upstream changes the entry, but given our thoughts, I would guess updating the expected $n->scientific_name with the new value would be the way to go. Out of curiosity, from the $n->common_names I obtained the character string: authorityActinomycetia (Stackebrandt et al. 1997) Salam et al. 2020 gregor herrmann writes: > I see your point, and in the end it's a matter of taste, I guess; or > a choice between two bad options: > - skipping tests and missing bugs > - enabling tests and having to deal with failures because of internet > problems, server problems, changes in returned data etc. > > Having seen too much of the latter, I prefer the former but as I > said, that's not the only option :) In doubt, since the package is team maintained and developer time is precious, I believe I will defer to your experience. I replace the "needs-internet" by "superficial", and set NO_NETWORK_TESTING=1 in debian/tests/pkg-perl/smoke-env. Hopefully if further offline testing became possible, that would allow us to remove the "superficial" flag in the future. > As a side note to the autopkg-tests: The "heavy" tests don't exists, > that was just an idea when we started with the framework, so you can > remove the last paragraph. Thanks for the side note, I removed the entry. Thanks again to you both for your time, Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#898177: [related feature respect /etc/mailname] Re: please add MAILFROM to cron
Hi all, On 21.02.21 15:46, Laurent Combe wrote: > near 3 years i report this issue > i joined a patch > and after all that time nothing, not even a "confirmed" tag. > > very disappointing. What can I do to help this issue be accepted more quickly > ? I can't speak for Javier, but in the meantime, I myself have mostly given up on cron, in the sense that I consider systemd timers a superior solution. I think we can integrate this patch still in time for bullseye, it's small enough. However, it is missing a crucial feature: the validation of the contents of MAILFROM, just as MAILTO is validated. This is a security issue, as the contents of this variable are passed to /usr/bin/sendmail, and it shouldn't contain eg: options to modify the latter's working. The cronie code has a safe_p function to validate this; it is more sophisticated than our own function. I'll import that. Best, Christian
Bug#983352: htop: Hardware dependent?
Package: htop Version: 3.0.5-4 Followup-For: Bug #983352 X-Debbugs-Cc: riveravaldezm...@gmail.com Maybe this is too obvious, but just in case, in the first hardware (previous message) the bug is present, but not in the second hardware (the one of this message). **First hardware (bug present):** ``` $ sudo lshw debian description: Desktop Computer product: M68M-S2P vendor: Gigabyte Technology Co., Ltd. width: 64 bits capabilities: smbios-2.4 dmi-2.4 smp vsyscall32 configuration: boot=normal chassis=desktop uuid=36434630-3439-3942-4235-3133 *-core description: Motherboard product: M68M-S2P vendor: Gigabyte Technology Co., Ltd. physical id: 0 version: x.x *-firmware description: BIOS vendor: Award Software International, Inc. physical id: 0 version: F1 date: 11/18/2009 size: 128KiB capacity: 1MiB capabilities: pci pnp apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification *-cpu description: CPU product: AMD Phenom(tm) 8650 Triple-Core Processor vendor: Advanced Micro Devices [AMD] physical id: 3 bus info: cpu@0 version: AMD Phenom(tm) 8650 Triple-Core ProcessorR slot: Socket M2 size: 1150MHz capacity: 3200MHz width: 64 bits clock: 200MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs hw_pstate vmmcall npt lbrv svm_lock cpufreq (...) ``` **Second hardware, from which this report is being sent (bug is NOT present, htop works as expected):** ``` $ sudo lshw debian description: Notebook product: 4298A26 vendor: LENOVO version: ThinkPad X220 Tablet serial: R9P31TD width: 64 bits capabilities: smbios-2.6 dmi-2.6 smp vsyscall32 configuration: administrator_password=disabled chassis=notebook family=ThinkPad X220 Tablet power-on_password=disabled uuid=8125C6A9-E843-CB11-8E90-B848DEED99EE *-core description: Motherboard product: 4298A26 vendor: LENOVO physical id: 0 version: Not Available serial: 1ZMDP45NFS3 slot: Not Available *-cpu description: CPU product: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz serial: Not Supported by CPU slot: CPU size: 812MHz capacity: 3200MHz width: 64 bits clock: 100MHz capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts cpufreq configuration: cores=2 enabledcores=2 threads=4 (...) ``` Hope I'm not spamming... Best regards. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages htop depends on: ii libc6 2.30-8 ii libncursesw6 6.2+20201114-2 ii libnl-3-200 3.4.0-1+b1 ii libnl-genl-3-200 3.4.0-1+b1 ii libtinfo6 6.2+20201114-2 htop recommends no packages. Versions of packages htop suggests: ii lm-sensors 1:3.6.0-7 ii lsof4.93.2+dfsg-1.1 pn strace -- no debconf information
Bug#980135: closing 980135
Unfortunately the daily limit is exceeded again at the moment. I am switching to the default 'geoclue' key for now. Kind regards, Harm te Hennepe
Bug#983359: ntfs-3g has a wrong Pre-Depends
Package: ntfs-3g Version: 1:2017.33.23AR.3-3 User: ubuntu-de...@lists.ubuntu.com Usertags: hirsute origin-ubuntu Hi Laszlo, The ntfs-3g package has a Pre-Depends on fuse. This is improper; Pre-Depends should only be used when one package is required to be configured before another package is unpacked. Since ntfs-3g has no preinst script, this is not the case for ntfs-3g and the Pre-Depends should be moved to Depends. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#983358: cypari2: demote sphinx dependency to B-D-I
Source: cypari2 Version: 2.1.2-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: cross-satisfiability cypari2 cannot be cross built from source, becuase its Build-Depends are not satisfiable. Part of the issue is the sphinx dependency. Fortunately, the documentation is separated into an arch:all package already. All that is missing here is actually skipping the documentation build during an arch:only build and demoting the relevant dependencies to Build-Depends-Indep. Please consider applying the attached patch. Helmut diff --minimal -Nru cypari2-2.1.2/debian/changelog cypari2-2.1.2/debian/changelog --- cypari2-2.1.2/debian/changelog 2020-11-07 12:01:53.0 +0100 +++ cypari2-2.1.2/debian/changelog 2021-02-22 20:48:32.0 +0100 @@ -1,3 +1,10 @@ +cypari2 (2.1.2-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Demote sphinx dependency to B-D-I. (Closes: #-1) + + -- Helmut Grohne Mon, 22 Feb 2021 20:48:32 +0100 + cypari2 (2.1.2-1) unstable; urgency=medium * New upstream version. (Closes: #973351) diff --minimal -Nru cypari2-2.1.2/debian/control cypari2-2.1.2/debian/control --- cypari2-2.1.2/debian/control2020-11-07 11:55:19.0 +0100 +++ cypari2-2.1.2/debian/control2021-02-22 20:48:32.0 +0100 @@ -6,15 +6,17 @@ Build-Depends: debhelper (>= 11), dh-python (>= 3.20180313), + dh-sequence-python3, cython3 (>= 0.26), libgmp-dev, libpari-dev (>= 2.9), pari-doc (>= 2.9), pari-gp (>= 2.9), - libjs-mathjax, python3-all-dev, python3-cysignals-pari (>= 1.8.1), python3-setuptools, +Build-Depends-Indep: + dh-sequence-sphinxdoc, python3-sphinx, Standards-Version: 4.5.0 Homepage: https://github.com/sagemath/cypari2 diff --minimal -Nru cypari2-2.1.2/debian/rules cypari2-2.1.2/debian/rules --- cypari2-2.1.2/debian/rules 2020-03-08 19:11:27.0 +0100 +++ cypari2-2.1.2/debian/rules 2021-02-22 20:48:32.0 +0100 @@ -4,12 +4,11 @@ export PYBUILD_NAME = cypari2 %: - dh $@ --with autoreconf --with python3,sphinxdoc --buildsystem=pybuild + dh $@ --with autoreconf --buildsystem=pybuild -override_dh_auto_build: export http_proxy=127.0.0.1:9 -override_dh_auto_build: export https_proxy=127.0.0.1:9 -override_dh_auto_build: - dh_auto_build +execute_after_dh_auto_build-indep: export http_proxy=127.0.0.1:9 +execute_after_dh_auto_build-indep: export https_proxy=127.0.0.1:9 +execute_after_dh_auto_build-indep: cd docs && $(MAKE) html override_dh_auto_test:
Bug#982579: Solution for loading firmware
please also add BananaPi M3 support. >From 216a0bda280e7b361c335f545156e86a059d9551 Mon Sep 17 00:00:00 2001 From: maximilian attems Date: Mon, 22 Feb 2021 22:18:36 +0100 Subject: [PATCH 2/2] WHENCE: add missing symlink for BananaPi M3 Fixes (Debian bug #982579): > [ 11.957171] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt (-2) > [ 11.967106] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware > [ 11.977035] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.txt (-2) > [ 12.994756] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 Reported-by: Bernhard Signed-off-by: maximilian attems --- WHENCE | 1 + 1 file changed, 1 insertion(+) diff --git a/WHENCE b/WHENCE index 11c0970..b569990 100644 --- a/WHENCE +++ b/WHENCE @@ -2717,6 +2717,7 @@ File: "brcm/brcmfmac43430-sdio.AP6212.txt" Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt -> brcmfmac43430-sdio.AP6212.txt Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt -> brcmfmac43430-sdio.AP6212.txt Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt -> brcmfmac43430-sdio.AP6212.txt +Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt -> brcmfmac43430-sdio.AP6212.txt File: "brcm/brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt" File: "brcm/brcmfmac43430-sdio.MUR1DX.txt" File: "brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt" -- 2.30.0
Bug#898177: [related feature respect /etc/mailname] Re: please add MAILFROM to cron
Greets all. I've added those suggestions to the cron wiki page (https://wiki.debian.org/cron) in the hope that people that would like to help to move cron in Debian move forward can jump in and do things that are possible and useful. I hope that's fine with you guys! *t On Mon, 22 Feb 2021, Tomas Pospisek wrote: Hi Laurent, let me start by saying the gentlemen above are probably working on cron in their free time. They do not owe anybody anything. So I think you can be disapointed, but saying so will probably not have a positive impact. Maybe it will on the contrary drain them. That said, thanks for your offer for help. I want to explore a bit how you (or I?) could help. After I've seen your email I visited the package page: https://packages.debian.org/search?keywords=cron and I've noticed, that the `cron` in experimental is in fact `cronie` (coming from RH/Fedora) which reminded that the plan was to replace cron in Debian with cronie, since cron is not maintained upstream any more. You can read about it here: https://wiki.debian.org/cron So I think the following things would be helpful: * port features that Debian's cron has, but cronie is missing from cron to cronie. Since both Debian's cron and cronie are forks of the original cron, the should be somewhat compatible. Also Debian cron has now split off its diff from the original cron into patches under debian/patches. So the theory would be that you can take one patch after the other, see what feature it implements and port it over to cronie. Once the port is done you could submit that patch upstream with the accompanying rationale that this feature is needed for Debian in order to be able to migrate to cronie. Also you could fork Debian's cronie repo and submin pull requests, so Debian can integrate the missing features into cronie. * you could install cronie on your systems and see what's missing or if its working how it should and submit error or success reports to the Samba repo (I guess). * you could go through cron's bugs page https://bugs.debian.org/cron and see which of those bugs is fixed in cronie and comment inside the bug. Maybe the maintainers would like to add a tag "implemented-in-cronie" or such, so that they can see at a glance, which bugs would be automatically closed by cronie. What do you think? *t On Sun, 21 Feb 2021, Laurent Combe wrote: near 3 years i report this issue i joined a patch and after all that time nothing, not even a "confirmed" tag. very disappointing. What can I do to help this issue be accepted more quickly ?
Bug#983349: hplip: while scanning , error 9 : impossible to scan
Package: hplip Version: 3.21.2+dfsg1-1 Followup-For: Bug #983349 X-Debbugs-Cc: compte.perso.de-al...@bbox.fr your command : simple-scan escl:http://127.0.0.1:6 was nearly ok . simple-scan started to connect and , quickly , closed itself : "cannot connect" i've read your texts . the only thing i understood is that usb connections has become now like network connections alain@sid:~$ lsusb -v | grep -A 3 bInterfaceClass.*7 Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 can't get debug descriptor: Resource temporarily unavailable Couldn't open device, some information will be missing -- bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 4 iInterface 0 Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing new ipp-over-usb seems to be not compatible with libsane-hpaio (my driver) so i have a big problem . don't know the solution . -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'testing'), (100, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hplip depends on: ii adduser3.118 ii cups 2.3.3op2-3 ii hplip-data 3.21.2+dfsg1-1 ii libc6 2.31-9 ii libcups2 2.3.3op2-3 ii libdbus-1-31.12.20-2 ii libhpmud0 3.21.2+dfsg1-1 ii libpython3.9 3.9.1-4 ii libsane-hpaio 3.21.2+dfsg1-1 ii libsane1 1.0.31-4 ii lsb-base 11.1.0 ii printer-driver-hpcups 3.21.2+dfsg1-1 ii python33.9.1-1 ii python3-dbus 1.2.16-5 ii python3-gi 3.38.0-2 ii python3-pexpect4.8.0-1 ii python3-pil8.1.0-1 ii python3-reportlab 3.5.59-1 ii wget 1.21-1+b1 ii xz-utils 5.2.5-1.0 Versions of packages hplip recommends: ii avahi-daemon 0.8-5 ii policykit-1 0.105-30 ii printer-driver-postscript-hp 3.21.2+dfsg1-1 ii sane-utils1.0.31-4 Versions of packages hplip suggests: pn hplip-doc ii hplip-gui 3.21.2+dfsg1-1 ii python3-notify20.3-4 ii system-config-printer 1.5.14-1 -- no debconf information
Bug#898177: [related feature respect /etc/mailname] Re: please add MAILFROM to cron
Hi Laurent, let me start by saying the gentlemen above are probably working on cron in their free time. They do not owe anybody anything. So I think you can be disapointed, but saying so will probably not have a positive impact. Maybe it will on the contrary drain them. That said, thanks for your offer for help. I want to explore a bit how you (or I?) could help. After I've seen your email I visited the package page: https://packages.debian.org/search?keywords=cron and I've noticed, that the `cron` in experimental is in fact `cronie` (coming from RH/Fedora) which reminded that the plan was to replace cron in Debian with cronie, since cron is not maintained upstream any more. You can read about it here: https://wiki.debian.org/cron So I think the following things would be helpful: * port features that Debian's cron has, but cronie is missing from cron to cronie. Since both Debian's cron and cronie are forks of the original cron, the should be somewhat compatible. Also Debian cron has now split off its diff from the original cron into patches under debian/patches. So the theory would be that you can take one patch after the other, see what feature it implements and port it over to cronie. Once the port is done you could submit that patch upstream with the accompanying rationale that this feature is needed for Debian in order to be able to migrate to cronie. Also you could fork Debian's cronie repo and submin pull requests, so Debian can integrate the missing features into cronie. * you could install cronie on your systems and see what's missing or if its working how it should and submit error or success reports to the Samba repo (I guess). * you could go through cron's bugs page https://bugs.debian.org/cron and see which of those bugs is fixed in cronie and comment inside the bug. Maybe the maintainers would like to add a tag "implemented-in-cronie" or such, so that they can see at a glance, which bugs would be automatically closed by cronie. What do you think? *t On Sun, 21 Feb 2021, Laurent Combe wrote: near 3 years i report this issue i joined a patch and after all that time nothing, not even a "confirmed" tag. very disappointing. What can I do to help this issue be accepted more quickly ?
Bug#983349: hplip: while scanning , error 9 : impossible to scan
On Mon 22 Feb 2021 at 21:16:17 +0100, alain wrote: > Package: hplip > Version: 3.21.2+dfsg1-1 > Followup-For: Bug #983349 > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr > > thanks Brian . > > here are what you asked me : > > alain@sid:~$ systemctl list-units "ipp-usb*" | grep service > ipp-usb.service loaded active running Daemon for IPP over USB printer > support ipp-usb is active, as designed. I suggest you read sections 13, 14 and 15 at https://wiki.debian.org/CUPSDriverlessPrinting > alain@sid:~$ scanimage -L > device `escl:http://127.0.0.1:6' is a HP ENVY 5530 series [FE04D6] (USB) > flatbed scanner > device `hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX' is a > Hewlett-Packard > ENVY_5530_series all-in-one > > is that what you wanted ? Yes, thanks. Can you scan with simple-scan escl:http://127.0.0.1:6 ? > tried vuescan : no works no more . Not one of ours, but an interesting data point. Cheers, Brian.
Bug#924401: #924401 base-files fails postinst when base-passwd is unpacked
Hi, for everybody else who is reading this bug and was not reading debian-devel at the same time, here is the thread that Tim started there for more context: https://lists.debian.org/alpine.deb.2.20.2102211635290.6...@einstein.home.woodall.me.uk Quoting Tim Woodall (2021-02-22 18:28:56) > On Mon, 22 Feb 2021, Helmut Grohne wrote: > > On Mon, Feb 22, 2021 at 07:33:10AM +, Tim Woodall wrote: > >> A. /etc/passwd is part of base-passwd's interface and base-files is > >>right in relying on it working at all times. Then base-passwd is rc > >>buggy for violating a policy must. Fixing this violation is > >>technically impossible. > >> > >> > >> I seem to have hit this same issue independently. > >> > >> Could you explain why "Fixing this violation is technically impossible" > > > > The requirement here is that base-passwd needs to work when unpacked. > > The only way to make that work is making /etc/passwd a conffile. That > > would technically be possible, but it would be very annoying, because > > this file is different on virtually any Debian installation. So we > > cannot make it a conffile in practice. The next bet would be ensuring > > that base-passwd.postinst is run before other packages' postint somehow. > > Such an ordering mechanism does not exist at present and it would be > > prone to dependency loops. > > > >> As far as I can see, making base-passwd not essential, only required, > >> and then making passwd and base-files pre-depend on base-passwd the > >> system seems to bootstrap /etc/passed and /etc/group OK. > > > > What you write is almost certainly self-contradictory. base-files is > > essential. Anything it depends on (including base-passwd in your > > scenario) is pseudo-essential and thus inherits all the same > > requirements except for actually being essential. You gained nothing. > > And you didn't explain how you'd make base-passwd non-essential. > > > >> That also seems to conform to the debian policy. The oddity is that > >> base-files and passwd only actually need to depend on base-passwd, not > >> pre-depend on it as they only use /etc/passwd and /etc/group in the > >> postinst scripts but the debian policy doesn't seem to consider this > >> case. > > > > They don't have to depend on base-passwd at all, because dependencies on > > essential packages should be omitted. > > If base-passwd wasn't essential then passwd and base-files should depend > on it. > > If passwd and base-files (pre)depend on base-passwd then base-passwd > will be configured before passwd or base-files postinst is run. In your mails to debian-devel and to this bug you are mixing some orthogonal problems. Please note, that Debian policy does *not* describe how to create a Debian chroot from zero. Specifically it does not cover the situation in which a package was *never* configured. So when it says that packages in the Essential:yes set must work even without being configured, then this is talking about package upgrades where packages from the Essential:yes set can find themselves in the configure stage but still have to work. Yes, this should be clarified in Debian policy. Since Debian policy does *not* talk about the debootstrap scenario, you can *not* make the argument of "you have to add the Depends because Debian policy says so". Remember, that Debian policy documents existing practice, so if we want to at some point document the debootstrap scenario in Debian policy, we first have to make it work properly in the first place. For reasons that Colin and Helmut already listed, I don't think adding more dependencies between Essential:yes packages or dropping Essential:yes is the right way forward. If you start adding dependencies between packages in the Essential:yes set, depending on what they use, you will very quickly end up with a lot of circular dependencies and you are back at square one. As the author of one of the debootstrap programs (mmdebstrap) I would welcome you investing time in properly solving this problem. For this I suggest you open a bug against dpkg because I think it's there that this has to be solved. > > I suggest that you detail on the practical issue you have been hitting. > > Doing so allows evaluating prospective solutions against all relevant > > use cases. > > > > What I am doing - which seems similar to what others are doing with > other tools, is to: > > 1. unpack apt, dpkg and debian-archive-keyring data.tar.xz into tmpdir/ > (This provides a set of config that apt needs to run) > > 2. create a sources.list in tmpdir and touch image/var/lib/dpkg/status > (dpkg needs this file to exist) > > 3. apt-get install -o RootDir=tmpdir -d $ESSENTIAL > (This resolves all of the dependencies and downloads every package that > needs to be installed. I cannot see a way to get apt to do this without > jumping through the hoops of step 1 and 2 as --reinstall doesn't > re-download dependencies) > > 4. unpack the data.tar.xz from every deb downloaded in 3 into image/ >
Bug#965088: Waiting for release 2.3
On 2021-02-22 21:13:40, Diederik de Haas wrote: > On Sat, 14 Nov 2020 23:14:12 +0100 Ulrike Uhlig wrote: >> I did not forget about this, but I'm waiting for 2.3 to be released, as >> there has been some huge refactoring which concerns the packaging of >> Onionshare, see https://github.com/micahflee/onionshare/pull/1208. > > Version 2.3 has been released (and tag added yesterday). > Is it too late for Bullseye? Probably. -- Everyone is a terrorist. You're just not pissed enough.
Bug#983357: Netinst crashes xen domU when loading kernel
Package: debian-installer Version: 20201202 Every bullseye netinst image I have tried to boot in a xen domU has crashed and rebooted the domU after choosing any entry from the boot menu. I thought there might have been something wrong with my xen server, which was running Ubuntu 18.04, but I rebuilt it the other day using bullseye as the dom0, and I still can't install bullseye in a domU.
Bug#983355: put-dns: [INTL:de] updated German debconf translation
Package: put-dns Version: 0.0.2-3 Severity: wishlist Tags: patch l10n Please find the updated German debconf translation for put-dns attached. Please place this file in debian/po/ as de.po for your next upload. 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. Greetings Helge # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the put-dns package. # Helge Kreutzmann , 2021. # msgid "" msgstr "" "Project-Id-Version: put-dns 0.0.2-3\n" "Report-Msgid-Bugs-To: put-...@packages.debian.org\n" "POT-Creation-Date: 2021-02-22 08:32+\n" "PO-Revision-Date: 2021-02-22 21:34+0100\n" "Last-Translator: Helge Kreutzmann \n" "Language-Team: German \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:1001 msgid "Automatically update domain in put-dns.conf?" msgstr "Domain in put-dns.conf automatisch aktualisieren?" #. Type: boolean #. Description #: ../templates:1001 msgid "" "If enabled put-dns will, on configuration, try to detect a valid external " "domain name on the current system and update the put-dns.conf configuration " "file to use it. If disabled then the configuration will not be automatically " "updated." msgstr "" "Falls aktiviert, wird Put-dns während seiner Konfiguration versuchen, einen " "gültigen externen Domain-Namen auf dem aktuellen System zu erkennen und die " "Konfigurationsdatei put-dns.conf aktualisieren, diesen zu verwenden. Falls " "deaktiviert, wird die Konfiguration nicht automatisch aktualisiert."
Bug#983356: inspircd: GnuTLS module sometimes sees data delayed
Package: inspircd
Version: 2.0.27-1+deb10u1
Severity: normal
Tags: patch upstream
Dear Maintainer,
I found a bug affecting (mostly?) local SSL connections vie GnuTLS.
Sometimes the data sent by the client is seen by the server only when
follwing data has been sent. See
https://github.com/inspircd/inspircd/issues/1848 (Messages from SSL
client are not always handled when available (inspircd v2))
The appended patch fixed the issue for me.
-- System Information:
Debian Release: 10.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.10.0-1127.8.2.vz7.151.14 (SMP w/1 CPU core)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages inspircd depends on:
ii libc6 2.28-10
ii libgcc11:8.3.0-6
ii libgeoip1 1.6.12-1
ii libgnutls303.6.7-4+deb10u6
ii libldap-2.4-2 2.4.47+dfsg-3+deb10u6
ii libmariadb31:10.3.27-0+deb10u1
ii libpcre3 2:8.43-1+0~20200703.7+debian9~1.gbpbfc49f
ii libpq5 11.10-0+deb10u1
ii libsqlite3-0 3.27.2-3+deb10u1
ii libstdc++6 8.3.0-6
ii libtre50.8.0-6
ii lsb-base 10.2019051400
inspircd recommends no packages.
Versions of packages inspircd suggests:
ii default-mysql-server 1.0.5
pn gnutls-bin
pn ldap-server
pn postgresql
ii sqlite3 3.27.2-3+deb10u1
-- Configuration Files:
/etc/default/inspircd changed [not included]
/etc/inspircd/inspircd.conf [Errno 13] Permission denied:
'/etc/inspircd/inspircd.conf'
/etc/inspircd/inspircd.motd [Errno 13] Permission denied:
'/etc/inspircd/inspircd.motd'
/etc/inspircd/inspircd.rules [Errno 13] Permission denied:
'/etc/inspircd/inspircd.rules'
-- no debconf information
diff -Nru inspircd-2.0.27/debian/changelog inspircd-2.0.27/debian/changelog
--- inspircd-2.0.27/debian/changelog2020-09-11 07:59:09.0 +0200
+++ inspircd-2.0.27/debian/changelog2021-02-21 21:34:31.0 +0100
@@ -1,3 +1,10 @@
+inspircd (2.0.27-1+deb10u1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch gnutls module may not fully read available data
+
+ -- Michael Kosinets Sun, 21 Feb 2021
21:34:31 +0100
+
inspircd (2.0.27-1+deb10u1) buster-security; urgency=high
* Patch denial-of-service security vulnerabilities (Closes: #960650)
diff -Nru inspircd-2.0.27/debian/patches/07_gnutls_delayed_data.patch
inspircd-2.0.27/debian/patches/07_gnutls_delayed_data.patch
--- inspircd-2.0.27/debian/patches/07_gnutls_delayed_data.patch 1970-01-01
01:00:00.0 +0100
+++ inspircd-2.0.27/debian/patches/07_gnutls_delayed_data.patch 2021-02-21
21:32:13.0 +0100
@@ -0,0 +1,16 @@
+diff -Naur inspircd-2.0.27.orig/src/modules/extra/m_ssl_gnutls.cpp
inspircd-2.0.27/src/modules/extra/m_ssl_gnutls.cpp
+--- inspircd-2.0.27.orig/src/modules/extra/m_ssl_gnutls.cpp2021-02-19
22:47:56.846343368 +0100
inspircd-2.0.27/src/modules/extra/m_ssl_gnutls.cpp 2021-02-21
21:31:08.536997908 +0100
+@@ -703,9 +703,11 @@
+ if (ret > 0)
+ {
+ recvq.append(buffer, ret);
++ int mask = FD_WANT_POLL_READ;
+ // Schedule a read if there is still data in
the GnuTLS buffer
+ if (gnutls_record_check_pending(session->sess)
> 0)
+-
ServerInstance->SE->ChangeEventMask(user, FD_ADD_TRIAL_READ);
++ mask |= FD_ADD_TRIAL_READ;
++ ServerInstance->SE->ChangeEventMask(user, mask);
+ return 1;
+ }
+ else if (ret == GNUTLS_E_AGAIN || ret ==
GNUTLS_E_INTERRUPTED)
diff -Nru inspircd-2.0.27/debian/patches/series
inspircd-2.0.27/debian/patches/series
--- inspircd-2.0.27/debian/patches/series 2020-09-11 07:59:09.0
+0200
+++ inspircd-2.0.27/debian/patches/series 2021-02-21 21:33:01.0
+0100
@@ -3,3 +3,4 @@
04_reproducible_builds.diff
05_cve-2019-20917.diff
06_cve-2020-25269.diff
+07_gnutls_delayed_data.patch
Bug#983354: uses unsafe KillMode=none in systemd unit
Package: plymouth Version: 0.9.5-2 Severity: important Hi, my syslog is full of: Feb 22 21:23:05 fan systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. Please consider rewriting the systemd unit to get rid of this. Greetings Marc -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.11.0-zgws1 (SMP w/12 CPU threads) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plymouth depends on: ii init-system-helpers 1.60 ii initramfs-tools 0.139 ii libc62.31-9 ii libdrm2 2.4.104-1 ii libplymouth5 0.9.5-2 ii lsb-base 11.1.0 ii systemd 247.3-1 ii udev 247.3-1 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 11.0.1 ii plymouth-themes 0.9.5-2 -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=solar -- no debconf information
Bug#965088: Waiting for release 2.3
On Sat, 14 Nov 2020 23:14:12 +0100 Ulrike Uhlig wrote: > I did not forget about this, but I'm waiting for 2.3 to be released, as > there has been some huge refactoring which concerns the packaging of > Onionshare, see https://github.com/micahflee/onionshare/pull/1208. Version 2.3 has been released (and tag added yesterday). Is it too late for Bullseye? signature.asc Description: This is a digitally signed message part.
Bug#983349: hplip: while scanning , error 9 : impossible to scan
Package: hplip Version: 3.21.2+dfsg1-1 Followup-For: Bug #983349 X-Debbugs-Cc: compte.perso.de-al...@bbox.fr thanks Brian . here are what you asked me : alain@sid:~$ systemctl list-units "ipp-usb*" | grep service ipp-usb.service loaded active running Daemon for IPP over USB printer support alain@sid:~$ scanimage -L device `escl:http://127.0.0.1:6' is a HP ENVY 5530 series [FE04D6] (USB) flatbed scanner device `hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX' is a Hewlett-Packard ENVY_5530_series all-in-one is that what you wanted ? tried vuescan : no works no more . -- Package-specific info: Saving output in log file: /home/alain/hp-check.log HP Linux Imaging and Printing System (ver. 3.21.2) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version Gtk-Message: 21:13:29.004: Failed to load module "canberra-gtk-module" warning: debian-unstable version is not supported. Using debian-10.7 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux Host: sid Proc: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux Distribution: debian unstable Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.21.2 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for debian distro unstable version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.21.2 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=no gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=no foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.21.2 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no class-driver=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [commands] scan = /usr/bin/simple-scan %SANE_URI% [fax] email_address = voice_phone = [last_used] device_uri = hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX printer_name = HP_ENVY_5530_series working_dir = . [polling] device_list = enable = false interval = 5 [refresh] enable = false rate = 30 type = 1 [settings]
Bug#983351: isync: diff for NMU version 1.3.0-2.1
Dear maintainer,
I've prepared an NMU for isync (versioned as 1.3.0-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru isync-1.3.0/debian/changelog isync-1.3.0/debian/changelog
--- isync-1.3.0/debian/changelog 2018-09-02 19:31:35.0 +0200
+++ isync-1.3.0/debian/changelog 2021-02-22 21:09:21.0 +0100
@@ -1,3 +1,16 @@
+isync (1.3.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Ond??ej Nov?? ]
+ * d/watch: Use https protocol
+
+ [ Salvatore Bonaccorso ]
+ * reject funny mailbox names from IMAP LIST/LSUB (CVE-2021-20247)
+(Closes: #983351)
+
+ -- Salvatore Bonaccorso Mon, 22 Feb 2021 21:09:21 +0100
+
isync (1.3.0-2) unstable; urgency=medium
* Update vcs-* to point to salsa.d.o
diff -Nru isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch
--- isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch 1970-01-01 01:00:00.0 +0100
+++ isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch 2021-02-22 21:09:21.0 +0100
@@ -0,0 +1,68 @@
+>From 45e2bdc439a01974b6b990bfb8a8968192c3b721 Mon Sep 17 00:00:00 2001
+From: Oswald Buddenhagen
+Date: Sun, 14 Feb 2021 20:42:37 +0100
+Subject: [PATCH] CVE-2021-20247: reject funny mailbox names from IMAP LIST/LSUB
+
+in particular, '..' in the name could be used to escape the Path/Inbox
+of a Maildir Store, which could be exploited for stealing or deleting
+data, or staging a (mild) DoS attack.
+---
+ src/drv_imap.c | 31 ++-
+ 1 file changed, 30 insertions(+), 1 deletion(-)
+
+diff --git a/src/drv_imap.c b/src/drv_imap.c
+index 810479e..fbe2fed 100644
+--- a/src/drv_imap.c
b/src/drv_imap.c
+@@ -1258,11 +1258,12 @@ static int
+ parse_list_rsp_p2( imap_store_t *ctx, list_t *list, char *cmd ATTR_UNUSED )
+ {
+ string_list_t *narg;
+- char *arg;
++ char *arg, c;
+ int argl, l;
+
+ if (!is_atom( list )) {
+ error( "IMAP error: malformed LIST response\n" );
++ listbad:
+ free_list( list );
+ return LIST_BAD;
+ }
+@@ -1302,6 +1303,34 @@ parse_list_rsp_p2( imap_store_t *ctx, list_t *list, char *cmd ATTR_UNUSED )
+ warn( "IMAP warning: ignoring mailbox %s (reserved character '/' in name)\n", arg );
+ goto skip;
+ }
++ // Validate the normalized name. Technically speaking, we could tolerate
++ // '//' and '/./', and '/../' being forbidden is a limitation of the Maildir
++ // driver, but there isn't really a legitimate reason for these being present.
++ for (const char *p = narg->string, *sp = p;;) {
++ if (!(c = *p) || c == '/') {
++ uint pcl = (uint)(p - sp);
++ if (!pcl) {
++error( "IMAP warning: ignoring mailbox '%s' due to empty name component\n", narg->string );
++free( narg );
++goto skip;
++ }
++ if (pcl == 1 && sp[0] == '.') {
++error( "IMAP warning: ignoring mailbox '%s' due to '.' component\n", narg->string );
++free( narg );
++goto skip;
++ }
++ if (pcl == 2 && sp[0] == '.' && sp[1] == '.') {
++error( "IMAP error: LIST'd mailbox name '%s' contains '..' component - THIS MIGHT BE AN ATTEMPT TO HACK YOU!\n", narg->string );
++free( narg );
++goto listbad;
++ }
++ if (!c)
++break;
++ sp = ++p;
++ } else {
++ ++p;
++ }
++ }
+ narg->next = ctx->boxes;
+ ctx->boxes = narg;
+ skip:
+--
+2.29.2.2.g268056bf11.dirty
+
diff -Nru isync-1.3.0/debian/patches/series isync-1.3.0/debian/patches/series
--- isync-1.3.0/debian/patches/series 2018-09-02 19:31:35.0 +0200
+++ isync-1.3.0/debian/patches/series 2021-02-22 21:09:21.0 +0100
@@ -1 +1,2 @@
01_sni.patch
+reject-funny-mailbox-names--1.3.patch
diff -Nru isync-1.3.0/debian/watch isync-1.3.0/debian/watch
--- isync-1.3.0/debian/watch 2018-09-02 19:31:35.0 +0200
+++ isync-1.3.0/debian/watch 2021-02-22 21:09:21.0 +0100
@@ -1,2 +1,2 @@
version=3
-http://sf.net/isync/ isync-(.*)\.tar\.gz
+https://sf.net/isync/ isync-(.*)\.tar\.gz
Bug#983353: gnome-control-center is still not accessible with Orca screenreader
Package: release-notes Hi, To avoid to forget it On 21-02-2021 22:15, Samuel Thibault wrote: > Paul Gevers, le sam. 06 févr. 2021 10:10:33 +0100, a ecrit: >> One release further. Can somebody, e.g. from the Debian Accessibility >> Team, please at least check if this is still an issue? If not, we can >> close the bug, if so, we can document it *again* [1] as I'm not >> expecting it to get fixed in these last months if it's not fixed already. > > I had a look, it looks like it is exactly in the same state as before: > having to press right arrow twice, having to use control-f then esc to > get back to the panel list (not able to select a result element with the > keyboard). So the same text would be needed. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#983352: htop: "Also show CPU temperature" option shows "N/A"
Package: htop Version: 3.0.5-4 Severity: normal X-Debbugs-Cc: riveravaldezm...@gmail.com Hi, seems to be an upstream issue: https://github.com/htop-dev/htop/issues/529 "Temperature is showing as N/A when enabled on a Via Eden x2 u4200 even though libsensors is actually installed. O.S.: Arch Linux Device: HP t510 Thin Client" (I reported my case there.) And related to: https://github.com/htop-dev/htop/issues/538 "At the moment htop has hardcoded list of x86-64 cpu sensors. So it does not read them on my computers ;( For now I added 'acpitz' to hardcoded list but that's not a good solution." But, just in case, I'm informing here too. Let me know if I can do anything else. Thanks a lot and best regards! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/3 CPU threads) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages htop depends on: ii libc6 2.30-8 ii libncursesw6 6.2+20201114-2 ii libnl-3-200 3.4.0-1+b1 ii libnl-genl-3-200 3.4.0-1+b1 ii libtinfo6 6.2+20201114-2 htop recommends no packages. Versions of packages htop suggests: ii lm-sensors 1:3.6.0-7 ii lsof4.93.2+dfsg-1.1 pn strace -- no debconf information
Bug#983335: sdbus-cpp: support Multiarch and nodoc/nocheck build profiles/options
On Tue, 2021-02-23 at 01:52 +0800, Shengjing Zhu wrote:
> On Mon, Feb 22, 2021 at 05:44:16PM +, Luca Boccassi wrote:
> > > I have verified with `sbuild --profiles=nodoc --no-arch-all`.
> > > Is there anything I miss?
> >
> > I was testing in a pbuilder chroot, and without doxygen installed
> > "DEB_BUILD_OPTIONS=nodoc DEB_BUILD_PROFILES=nodoc dpkg-buildpackage"
> > would fail at the arch-dependent configure.
> >
>
> Could you try `dpkg-buildpackage --build-profiles=nodoc`?
>
> At least I can't find a way to run this command.
> Whenever I pass DEB_BUILD_PROFILES=nodoc to sbuild, or --profiles=nodoc,
> the actual dpkg-buildpackage command becomes:
>
> dpkg-buildpackage --sanitize-env -Pnodoc -us -uc -G -rfakeroot
Ok, that works - interesting.
Attached patch to make the -bin package Multiarch: allowed, verified in
a chroot that libsdbus-c++-dev:i386 can be installed with libsdbus-c++-
bin:amd64. Would be great to have this in Buster, so that multiarch
works.
--
Kind regards,
Luca Boccassi
From 3a060916559800bdfa563f94c4f31b44e63ad546 Mon Sep 17 00:00:00 2001
From: Luca Boccassi
Date: Mon, 22 Feb 2021 20:03:53 +
Subject: [PATCH] Mark libsdbus-c++-bin as Multi-Arch: allowed
Allows libsdbus-c++-dev:i386 to be installable with libsdbus-c++-bin:amd64
---
debian/control | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index c992b73..212784b 100644
--- a/debian/control
+++ b/debian/control
@@ -21,6 +21,7 @@ Vcs-Browser: https://salsa.debian.org/zhsj/sdbus-cpp
Package: libsdbus-c++-bin
Section: utils
Architecture: linux-any
+Multi-Arch: allowed
Depends:
${misc:Depends},
${shlibs:Depends},
@@ -35,7 +36,7 @@ Package: libsdbus-c++-dev
Architecture: linux-any
Multi-Arch: same
Depends:
- libsdbus-c++-bin (= ${binary:Version}),
+ libsdbus-c++-bin:any (= ${binary:Version}),
libsdbus-c++0 (= ${binary:Version}),
${misc:Depends},
${shlibs:Depends},
--
2.29.2
signature.asc
Description: This is a digitally signed message part
Bug#983351: isync: diff for NMU version 1.3.0-2.1
Control: tags 983351 + patch
Control: tags 983351 + pending
Dear maintainer,
I've prepared an NMU for isync (versioned as 1.3.0-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru isync-1.3.0/debian/changelog isync-1.3.0/debian/changelog
--- isync-1.3.0/debian/changelog 2018-09-02 19:31:35.0 +0200
+++ isync-1.3.0/debian/changelog 2018-10-01 09:35:31.0 +0200
@@ -1,3 +1,16 @@
+isync (1.3.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Ond??ej Nov?? ]
+ * d/watch: Use https protocol
+
+ [ Salvatore Bonaccorso ]
+ * reject funny mailbox names from IMAP LIST/LSUB (CVE-2021-20247)
+(Closes: #983351)
+
+ -- Ond??ej Nov?? Mon, 01 Oct 2018 09:35:31 +0200
+
isync (1.3.0-2) unstable; urgency=medium
* Update vcs-* to point to salsa.d.o
diff -Nru isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch
--- isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch 1970-01-01 01:00:00.0 +0100
+++ isync-1.3.0/debian/patches/reject-funny-mailbox-names--1.3.patch 2018-10-01 09:35:31.0 +0200
@@ -0,0 +1,68 @@
+>From 45e2bdc439a01974b6b990bfb8a8968192c3b721 Mon Sep 17 00:00:00 2001
+From: Oswald Buddenhagen
+Date: Sun, 14 Feb 2021 20:42:37 +0100
+Subject: [PATCH] CVE-2021-20247: reject funny mailbox names from IMAP LIST/LSUB
+
+in particular, '..' in the name could be used to escape the Path/Inbox
+of a Maildir Store, which could be exploited for stealing or deleting
+data, or staging a (mild) DoS attack.
+---
+ src/drv_imap.c | 31 ++-
+ 1 file changed, 30 insertions(+), 1 deletion(-)
+
+diff --git a/src/drv_imap.c b/src/drv_imap.c
+index 810479e..fbe2fed 100644
+--- a/src/drv_imap.c
b/src/drv_imap.c
+@@ -1258,11 +1258,12 @@ static int
+ parse_list_rsp_p2( imap_store_t *ctx, list_t *list, char *cmd ATTR_UNUSED )
+ {
+ string_list_t *narg;
+- char *arg;
++ char *arg, c;
+ int argl, l;
+
+ if (!is_atom( list )) {
+ error( "IMAP error: malformed LIST response\n" );
++ listbad:
+ free_list( list );
+ return LIST_BAD;
+ }
+@@ -1302,6 +1303,34 @@ parse_list_rsp_p2( imap_store_t *ctx, list_t *list, char *cmd ATTR_UNUSED )
+ warn( "IMAP warning: ignoring mailbox %s (reserved character '/' in name)\n", arg );
+ goto skip;
+ }
++ // Validate the normalized name. Technically speaking, we could tolerate
++ // '//' and '/./', and '/../' being forbidden is a limitation of the Maildir
++ // driver, but there isn't really a legitimate reason for these being present.
++ for (const char *p = narg->string, *sp = p;;) {
++ if (!(c = *p) || c == '/') {
++ uint pcl = (uint)(p - sp);
++ if (!pcl) {
++error( "IMAP warning: ignoring mailbox '%s' due to empty name component\n", narg->string );
++free( narg );
++goto skip;
++ }
++ if (pcl == 1 && sp[0] == '.') {
++error( "IMAP warning: ignoring mailbox '%s' due to '.' component\n", narg->string );
++free( narg );
++goto skip;
++ }
++ if (pcl == 2 && sp[0] == '.' && sp[1] == '.') {
++error( "IMAP error: LIST'd mailbox name '%s' contains '..' component - THIS MIGHT BE AN ATTEMPT TO HACK YOU!\n", narg->string );
++free( narg );
++goto listbad;
++ }
++ if (!c)
++break;
++ sp = ++p;
++ } else {
++ ++p;
++ }
++ }
+ narg->next = ctx->boxes;
+ ctx->boxes = narg;
+ skip:
+--
+2.29.2.2.g268056bf11.dirty
+
diff -Nru isync-1.3.0/debian/patches/series isync-1.3.0/debian/patches/series
--- isync-1.3.0/debian/patches/series 2018-09-02 19:31:35.0 +0200
+++ isync-1.3.0/debian/patches/series 2018-10-01 09:35:31.0 +0200
@@ -1 +1,2 @@
01_sni.patch
+reject-funny-mailbox-names--1.3.patch
diff -Nru isync-1.3.0/debian/watch isync-1.3.0/debian/watch
--- isync-1.3.0/debian/watch 2018-09-02 19:31:35.0 +0200
+++ isync-1.3.0/debian/watch 2018-10-01 09:35:31.0 +0200
@@ -1,2 +1,2 @@
version=3
-http://sf.net/isync/ isync-(.*)\.tar\.gz
+https://sf.net/isync/ isync-(.*)\.tar\.gz
Bug#946118: synaptics touchpad does not work in debian installer graphical mode
Holger Wansing, le sam. 20 févr. 2021 20:45:59 +0100, a ecrit: > Samuel Thibault wrote (Sat, 7 Dec 2019 22:54:09 +0100): > > Samuel Thibault, le mer. 04 déc. 2019 01:52:36 +0100, a ecrit: > > > Thinking of it... IIRC the touchpad is not working on my DELL XPS13 > > > laptop in g-i. > > > > Indeed, it doesn't work. > > Now that the graphical installer uses libinput instead of evdev, maybe it's > worth it to try if it works for you now with latest builds? It does work for me in the latest builds that use libinput, indeed. Samuel
Bug#736803: dh_dkms could automatically replace #MODULE_VERSION#
On Sun, 26 Jan 2014 22:19:34 +0100 Julian Andres Klode wrote: > I think it would make sense if dh_dkms automatically behaves > as if -V is present if #MODULE_VERSION# is set in the dkms > file. This would reduce the need for an override. Seconded. Does using -V on a .dkms file without #MODULE_VERSION# have any effect currently? If not, turning on -V by default (even without the option to turn it off again) should be transparent to all packages. Well, it will break packages that want a literal #MODULE_VERSION# in their installed .dkms file. But I'd consider these already broken ;-) Andreas
Bug#983349: hplip: while scanning , error 9 : impossible to scan
severity 983349 important tags 983349 - upstream thanks On Mon 22 Feb 2021 at 19:18:06 +0100, alain wrote: > Package: hplip > Version: 3.21.2+dfsg1-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr > > last weekend , while scanning a document , hp-scan went wrong . > > no more xsane , simple-scan or hp-scan work Thank you for your report, alain. Please provide systemctl list-units "ipp-usb*" | grep service and scanimage -L Regards, Brian..
Bug#983351: isync: CVE-2021-20247: reject funny mailbox names from IMAP LIST/LSUB
Source: isync Version: 1.3.0-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for isync. CVE-2021-20247[0]: | isync/mbsync data leak/destruction vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-20247 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20247 [1] https://www.openwall.com/lists/oss-security/2021/02/22/1 Regards, Salvatore
Bug#983346: Update gitlab to 13.7.7 (installation fails - need help)
On Mon, 22 Feb 2021 22:59:51 +0530 Pirate Praveen wrote: > Package: gitlab > Severity: important > Control: tags -1 help > > I'm trying to update gitlab to 13.7.7 (master-13.7 branch in salsa), > > but installation fails with Installing 13.7.7 on a clean system (after purge) works, but fails when upgrading from 13.6.7.
Bug#983350: titan manuals not packaged
Package: eclipse-titan Version: 7.2.0-1 Severity: minor the upstream eclipse-titan package contains an extensive set of user manuals in asciidoc format. If enabled, those asciidoc files are compiled into PDF manuals. It would be great if building the documentation was enabled by the debian package, and the resulting manuals could be made available for example in a eclipse-titan-doc package. This way, users would always have the matching documentation for the version they have installed, without having to obtain it from third-party sources. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages eclipse-titan depends on: ii expect5.45.4-2+b1 ii gcc 4:10.2.1-1 ii libc6 2.31-9 ii libedit-dev 3.1-20191231-2+b1 ii libedit2 3.1-20191231-2+b1 ii libgcc-s1 10.2.1-6 ii libpcap-dev 1.10.0-2 ii libpcre3-dev 2:8.39-13 ii libsctp-dev 1.0.18+dfsg-1 ii libssl-dev1.1.1j-1 ii libssl1.1 1.1.1j-1 ii libstdc++610.2.1-6 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxml2-dev 2.9.10+dfsg-6.3+b1 ii make 4.3-4 ii perl 5.32.1-2 ii python3 3.9.1-1 Versions of packages eclipse-titan recommends: ii default-jdk 2:1.11-72 eclipse-titan suggests no packages. -- no debconf information
Bug#720096: marked as pending in rsyslog
Am 22.02.2021 um 18:57 schrieb Harald Dunkel: Sorry to say, but this is not a fix. A fix would avoid the race condition, no matter whats written in the config files. Your "fix" is just a workaround. If I add If you have a better solution, I'm all ears. OpenPGP_signature Description: OpenPGP digital signature
Bug#983141: libkf5kiocore5: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
And indeed, rebuilding the identical package versions from source (to poke around and debug), fixed this problem for me. As the system I am running is somewhat of a mix of stable, testing and unstable, could there be some incomplete package dependency that was not capturing a missing symbol in some related package? It's a pity that klauncher does not give a more detailed error message when loading fails. Maybe an strerror(errno) output in the right place might help here? Cheers, //Urs On Mon, Feb 22, 2021 at 07:01:44PM +0900, Norbert Preining wrote: > Hi Urs, > > > At the same time, the akonadi server prints: > > kf.kio.core: couldn't create slave: "klauncher said: Error loading > > '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'." > > I got a very similar report from a friend running OpenSuse ... very > strange. > > I cannot really guess what it might be though without access to the > computer. You could install the debug symbols and try to debug it, > but not an easy task considering that all these things are dynamically > loaded. > > Best > > Norbert > > -- > PREINING Norbert https://www.preining.info > Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 >
Bug#978621: pipewire: Drag and drop a file in Dolphin makes pipewire crash KDE Plasma Wayland
Dear Sjoerd, Initially the journal recorded a crash of pipewire when the grapical UI crashed. When I tried to move a file today I noticed 2 things: now it only happens when I drag the file over the popup information and a new crash information that supports your supposition: Feb 22 19:06:34 systemname kernel: kwin_wayland[12033]: segfault at e8 ip 7fbbe21d5268 sp 7ffe4b5000b0 error 4 in libKWaylandServer.so. 5.20.5[7fbbe217d000+b6000] Feb 22 19:06:34 systemname kernel: Code: 00 00 48 8b 47 10 48 8b 40 48 c3 90 66 0f 1f 44 00 00 41 57 41 56 41 55 41 54 41 89 f4 55 48 89 fd 53 48 83 ec 18 4c 8b 7f 10 <49> 8b 87 c8 00 00 00 8b 48 0c 8b 58 08 89 4c 24 0c 89 5c 24 08 39 Feb 22 19:06:34 systemname org.kde.ActivityManager[12179]: The Wayland connection broke. Did the Wayland compositor die? Feb 22 19:06:34 systemname org.kde.ActivityManager[12179]: QSocketNotifier: Invalid socket 6 and type 'Read', disabling... Feb 22 19:06:34 systemname org.kde.ActivityManager[12179]: KCrash: crashing... crashRecursionCounter = 2 Feb 22 19:06:34 systemname org.kde.ActivityManager[12179]: KCrash: Application Name = kactivitymanagerd path = /usr/lib/x86_64-linux-gnu/libexec pid = 12179 Feb 22 19:06:34 systemname org.kde.ActivityManager[12179]: KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kactivitymanagerd Feb 22 19:06:34 systemname org.kde.ActivityManager[12179]: KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi Feb 22 19:06:34 systemname pulseaudio[12137]: X connection to :1 broken (explicit kill or server shutdown). From your developer view, does it make sense to move the bug report to kwin_wayland and, if yes, can you? Best regards Silverio Am Sonntag, 21. Februar 2021, 11:16:45 CET schrieb Sjoerd Simons: > On Tue, Dec 29, 2020 at 11:46:22AM +0100, Silvério Santos wrote: > > Package: pipewire > > Version: 0.3.15-1 > > Severity: normal > > > > Dear Maintainer, > > > > Since the update to KDE Plasma 5.20 Dolphin makes the whole session crash, > > displaying the login screen instead of completing the following process: > > 1. Grab a .ly file > > 2. Drag it to a subfolder > > 3. Before reaching the subfolder, the session is closed and the SDDM login > > screen is displayed. This also happens when trying to drag outside of the > > fie list to avoid hovering over other files. > > Does this still happen with newer pipewire ? But more importantly why the > conclusion that this is a pipewire bug not a dolphin (or another plasma > component)? > > Regards, > Sjoerd
Bug#983349: hplip: while scanning , error 9 : impossible to scan
Package: hplip Version: 3.21.2+dfsg1-1 Followup-For: Bug #983349 X-Debbugs-Cc: compte.perso.de-al...@bbox.fr sorry , i have just seen : not unstable compatible . so , if you think there's a solution , it will be good . also , i am looking for a canon lide 25 scanner in order to solve the problem . was searching a canonscan lide 300 but lide 25 was cheapiest . shipped in germany . -- Package-specific info: Saving output in log file: /home/alain/hp-check.log HP Linux Imaging and Printing System (ver. 3.21.2) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version Gtk-Message: 19:31:40.843: Failed to load module "canberra-gtk-module" warning: debian-unstable version is not supported. Using debian-10.7 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux Host: sid Proc: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux Distribution: debian unstable Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.21.2 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for debian distro unstable version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.21.2 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=no gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=no foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.21.2 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no class-driver=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [commands] scan = /usr/bin/simple-scan %SANE_URI% [fax] email_address = voice_phone = [last_used] device_uri = escl:http://127.0.0.1:6 printer_name = HP_ENVY_5530_series working_dir = . [polling] device_list = enable = false interval = 5 [refresh] enable = false rate = 30 type = 1 [settings] systray_messages = 0 systray_visible = 0 [upgrade] last_upgraded_time = 1613842662 notify_upgrade = true pending_upgrade_time = 0 [installation] date_time = 02/22/21 19:31:41 version = 3.21.2 - | External Dependencies | - error: cups CUPS - Common Unix Printing System REQUIRED1.1 - INCOMPAT 'CUPS may not be installed or not running' gs GhostScript - PostScript and PDF language interpreter and previewer REQUIRED7.059.53.3 OK - Gtk-Message: 19:31:42.385: Failed to load module
Bug#981384: clamtk: The app doesn't scan files/folders on demand
On Sun, 7 Feb 2021 13:46:16 +0100 Ulrich Harttig wrote: > Hello, > > > clamtk > > *** unhandled exception in callback: > > *** FATAL: invalid GtkDialogFlags value no-separator, expecting: > > modal / GTK_DIALOG_MODAL, destroy-with-parent / > > GTK_DIALOG_DESTROY_WITH_PARENT, use-header-bar / > > GTK_DIALOG_USE_HEADER_BAR at /usr/share/perl5/Gtk3.pm line 1136. *** > > ignoring at /usr/share/perl5/Gtk3.pm line 572. > > This bug also affects the "Analysis" function and is caused by an error in two > modules of ClamTk, /usr/share/perl5/ClamTk/Analysis.pm > and /usr/share/perl5/ClamTk/Scan.pm > There, Gtk3::Dialog->new is called with the parameter "no-separator" > which is invalid for Gtk3 as the error message states (it was valid in > Gtk2 > https://developer.gnome.org/gtk2/stable/GtkDialog.html#GtkDialogFlags) > > In Gtk3.pm, prior to the current version, the handling of the flags in > Gtk3::Dialog->new was buggy . This was changed in version 0.038 , see > https://github.com/GNOME/perl-gtk3/commit/ac5ace1e5839b992693fad13ebdc08ec7cab1876, > > so this problem only appears with the most recent version of Gtk3.pm > > with best regards > > Ulrich Harttig Hello, it seems that this bug is now fixed in version 6.08 by the author, see also https://gitlab.com/dave_m/clamtk with best regards Ulrich Harttig pgpExDp7FLhMK.pgp Description: Digitale Signatur von OpenPGP
Bug#979865: m2crypto FTBFS on IPV6-only buildds
Hi, On 22-02-2021 05:48, Sandro Tosi wrote: >>> it would be easier to enforce to have all buildds configured equally so >>> the package does not fail on a random buildd. >> >> I *guess* that's not trivial as I think it depends on the network their in. > > OTOH it's not ideal to have machines that are supposed to be similar, > being different enough to cause build failure (due to their > configuration, not due to resource constraint). Some discussion has evolved from this and somebody promised me to talk to the responsible people to see if this could be improved. >> m2crypto needs another upload anyways. Without a proper IPv6 solution >> for the tests, can the failing network tests please be disabled in the >> next upload? > > given the 29 failures are all part of test_ssl.py (and make up more > than half of the tests in it) i'm going to skip that file entirely. i > would argue that testing SSL is important for this package, so this > solution is very suboptimal. Ack and agree. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#983112: cheetah: reduce Build-Depends
Control: tag -1 + confirmed pending Thanks for your report, (the essence of) your patch has been merged into the cheetah packaging on git: https://salsa.debian.org/python-team/packages/cheetah/-/commit/887722262dbf3fa8f5dcb03bedaf9adf1afcdc8a pgpdtVfkmarOY.pgp Description: OpenPGP digital signature
Bug#982984: Mirror blocked due to repeated errors
Hey Eduard, On Mon, 2021-02-22 at 00:43 +0100, Eduard Bloch wrote: [...] > It would be good to receive some feedback by Wednesday, then I am > planing to approach the release team (expecting the "usual" messy > discussion). > > Best regards, > Eduard. > Building apt-cacher-ng cloned from ssh://g...@salsa.debian.org/blade/apt-cacher-ng failed in my environment (gbp-buildpackage) due to the upstream/3.6.1 tag being missing. But this is a different story. Snapshot build downloaded from https://www.unix-ag.uni-kl.de/~bloch/acng/snap3.6.1/ works for me. Cheers, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#983349: hplip: while scanning , error 9 : impossible to scan
Package: hplip
Version: 3.21.2+dfsg1-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
last weekend , while scanning a document , hp-scan went wrong .
no more xsane , simple-scan or hp-scan work .
here are my logs :
alain@sid:~$ hp-scan
HP Linux Imaging and Printing System (ver. 3.21.2)
Scan Utility ver. 2.2
Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
-
| SELECT DEVICE |
-
Num Scan device URI
-
0 escl:http://127.0.0.1:6
1*hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX
Enter number 0...1 for device (q=quit, =default: 1*) ?
warning: No destinations specified. Adding 'file' destination by default.
Using device hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX
Opening connection to device...
error: SANE: Error during device I/O (code=9)
alain@sid:~$ hp-scan
HP Linux Imaging and Printing System (ver. 3.21.2)
Scan Utility ver. 2.2
Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
-
| SELECT DEVICE |
-
Num Scan device URI
-
0 escl:http://127.0.0.1:6
1*hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX
Enter number 0...1 for device (q=quit, =default: 1*) ?0
warning: No destinations specified. Adding 'file' destination by default.
Using device escl:http://127.0.0.1:6
Opening connection to device...
error: SANE: Out of memory (code=10)
printing works good but scanning not at all .
i wonder if hplip ahsn't gone down .
-- Package-specific info:
Saving output in log file: /home/alain/hp-check.log
HP Linux Imaging and Printing System (ver. 3.21.2)
Dependency/Version Check Utility ver. 15.1
Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling
the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper
dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball
has
the proper dependencies installed to successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will
check both of the above cases (both compile- and run-time dependencies).
Check types:
a. EXTERNALDEP - External Dependencies
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION
Status Types:
OK
MISSING - Missing Dependency or Permission or Plug-in
INCOMPAT - Incompatible dependency-version or Plugin-version
Gtk-Message: 19:14:36.397: Failed to load module "canberra-gtk-module"
warning: debian-unstable version is not supported. Using debian-10.7 versions
dependencies to verify and install...
---
| SYSTEM INFO |
---
Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux
Host: sid
Proc: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) GNU/Linux
Distribution: debian unstable
Bitness: 64 bit
---
| HPLIP CONFIGURATION |
---
HPLIP-Version: HPLIP 3.21.2
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for debian
distro unstable version
Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf. Generated from hplip.conf.in by configure.
[hplip]
version=3.21.2
[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
Bug#983046: kjs: please make the opcodes.h file reproducible
Hi Norbert, > Do you want that this is also included into unstable and uploaded now > during the freeze, or is post-release fine? Post-release would be totally fine… but I suppose if you do end up uploading kjs for some other issue, it would be nice to include it. (Not sure what the current Release Manager policy is regarding including these kinds of fixes in unblock requests, mind you.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#720096: marked as pending in rsyslog
Sorry to say, but this is not a fix. A fix would avoid the race
condition, no matter whats written in the config files.
Your "fix" is just a workaround. If I add
/var/log/logfile1
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
 /usr/lib/rsyslog/rsyslog-rotate
 endscript
}
/var/log/logfile2
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
 /usr/lib/rsyslog/rsyslog-rotate
 endscript
}
in another config file, then the problem is back.
Bug#983335: sdbus-cpp: support Multiarch and nodoc/nocheck build profiles/options
On Mon, Feb 22, 2021 at 05:44:16PM +, Luca Boccassi wrote: > > I have verified with `sbuild --profiles=nodoc --no-arch-all`. > > Is there anything I miss? > > I was testing in a pbuilder chroot, and without doxygen installed > "DEB_BUILD_OPTIONS=nodoc DEB_BUILD_PROFILES=nodoc dpkg-buildpackage" > would fail at the arch-dependent configure. > Could you try `dpkg-buildpackage --build-profiles=nodoc`? At least I can't find a way to run this command. Whenever I pass DEB_BUILD_PROFILES=nodoc to sbuild, or --profiles=nodoc, the actual dpkg-buildpackage command becomes: dpkg-buildpackage --sanitize-env -Pnodoc -us -uc -G -rfakeroot
Bug#909750: applications tries to write to /usr/* directories via libfontconfig1
Control: tag -1 + patch Fix was in v2.13.91 (c4324f54ee16e648ba91f3e9c66af13ab3b1754c) [1] which removed the relevant codepath. If anyone still deems this worth addressing in 2.13.1, the attached patch fontconfig-2.13.1-909750-access-w_ok.patch silences the warning through an added writability check. However, while looking into this I ran into test suite issues: - test/run-test-conf.sh needs dash.patch to work with dash as /bin/sh - test/run-test.sh fails if /bin/bwrap (package bubblewrap) is installed; disable-bwrap.patch patches it out. IMO this bug is also a good candidate for a bullseye-ignore if no new upload is made because it only manifested with a non-Debian AppArmor profile for Firefox, breaks essentially nothing, and also because I had to manually delete .uuid files below /usr/share/fonts/* to get it to reproduce. Regards, Dennis. 1: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/c4324f54ee16e648ba91f3e9c66af13ab3b1754c fontconfig-2.13.1-909750-access-w_ok.patch.gz Description: application/gzip dash.patch.gz Description: application/gzip disable-bwrap.patch.gz Description: application/gzip
Bug#983335: sdbus-cpp: support Multiarch and nodoc/nocheck build profiles/options
On Tue, 2021-02-23 at 00:44 +0800, Shengjing Zhu wrote: > On Mon, Feb 22, 2021 at 04:33:32PM +, Luca Boccassi wrote: > > > > Subject: [PATCH 5/5] Add support for nodoc build option/profile > > > > > > > > > > Applied without check nodoc in d/rules. As building doc is already in > > > -indep target. And the -doc is the only arch all package. > > > > That adds an additional requirement though - doing a binary build > > together with the nodoc profile. Also, the binary build will fail > > without passing -DBUILD_DOC=OFF to the binary configure, since it's > > default-enabled and will fail when looking for the doxygen binary. > > > > I have verified with `sbuild --profiles=nodoc --no-arch-all`. > Is there anything I miss? I was testing in a pbuilder chroot, and without doxygen installed "DEB_BUILD_OPTIONS=nodoc DEB_BUILD_PROFILES=nodoc dpkg-buildpackage" would fail at the arch-dependent configure. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#983208: lynx: embeds path to various binaries that differ with usrmerge
On 2021-02-21 Vagrant Cascadian wrote: > On 2021-02-21, Andreas Metzler wrote: [...] > Thanks for applying. > > I don't get the point of trying to do reproducible builds on systems > > that differ significantly (usrmerge or not), it feels like make-work. > I get that, for sure. > The current reproducible builds test infrastructure is geared towards > finding issues so that we can fix them; some of the issues may seem to > be nuanced corner-cases. > In the case of usrmerge, both usrmerge and non-usrmerge systems exist in > the wild; having fewer variables that affect the build makes it > significantly easier to reproduce a build and more resilient. Bugs > triggered by building in a usrmerge environment have actually resulted > in functionally broken packages in several cases, too, so it does seem > to me important to find them early. Ok, I see. Thankfully we will get rid of that major source of make-work (supporting both usrmerge and unmerged) post bullseye ;-) #981582 Thanks, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#253115: mailutils: Dependency on mysql libs should be recommends/suggests.
Control: found -1 1:3.11.1-5 On Mon, 07 Jun 2004 04:46:15 -0500 Christopher Cashell wrote: > I'd like to request that the dependency on libmysqlclient10 be changed > to suggests or recommends. My experience is that most (all?) of the > mailutils applications/tools can be used without MySQL (or its client > library) being present, and many of us have no desire to have unecessery > (and unwanted) libraries installed. On a quite bare-bones system, I wanted to install 'at' which then wanted to install MySQL, MariaDB and PostgreSQL libraries. I noticed it before on other (bare-bones) systems, where I needed f.e. a (simple) MTA (for cron's local mail), which (quite understandably) depended on mailutils and that brought in those DB libraries. I understand that some people may want to have support for *a* database (thus and OR relation seems more appropriate), but most people don't need or want that. Can't the database support be split off into another package which mailutils then recommends (or suggests)? Diederik signature.asc Description: This is a digitally signed message part.
Bug#983330: ITP: python-browserstack-local -- Python library for BrowserStack Local
Hi, On Mon, Feb 22, 2021 at 12:03:08PM +0100, Romain Porte wrote: > Package: wnpp > Severity: wishlist > Owner: Romain Porte > X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org > > * Package name: python-browserstack-local > Version : 1.2.2 > Upstream Author : francisf > * URL : https://github.com/browserstack/browserstack-local-python > * License : Expat > Programming Lang: Python > Description : Python library for BrowserStack Local > > This library is used to access run commercial BrowserStack service > locally. It is able to download and execute the BrowserStack binaries > automatically. (Include the long description here.) > > This package is introduced as a dependency for the gftools package. It > is planned to be maintained with the help of the Debian Python team. Note that downloading and running binaries from arbitrary locations is is not suitable to Debian main. signature.asc Description: PGP signature
Bug#983347: lintian-brush: postrm is skipped by the fixer of maintainer-script-without-set-e
Package: lintian-brush Version: 0.97 Severity: normal Dear Maintainer, I launched lintian-brush 0.97 in the tree of my package jalview and it fixed the maintainer-script-without-set-e by modifying debian/config and debian/postinst but not debian/postrm, although the three of them were starting with #!/bin/sh -e and then a blank line. To reproduce, you may clone the jalview Salsa repository and be back to revision HEAD^^^ as of today (after commit 936ed870: Updating changelog) on the master branch, then run lintian-brush from there. Thanks for all the work on lintian-brush which is definitely a precious tool, Cheers, Pierre -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian-brush depends on: ii devscripts 2.20.5 ii ognibuild0.0.1~git20201031.4cbc8df-1.1 ii python3 3.9.1-1 ii python3-breezy 3.1.0-8 ii python3-debian 0.1.39 ii python3-debmutate0.20 ii python3-distro-info 1.0 ii python3-dulwich 0.20.15-1 ii python3-iniparse 0.4-3 ii python3-ruamel.yaml 0.16.12-2 ii python3-upstream-ontologist 0.1.9-1 Versions of packages lintian-brush recommends: ii decopy 0.2.4.4-0.1 ii dos2unix 7.4.1-1 ii gpg 2.2.20-1 ii libdebhelper-perl13.3.3 ii lintian 2.104.0 ii python3-asyncpg 0.21.0-1+b2 ii python3-bs4 4.9.3-1 ii python3-levenshtein 0.12.1-1 ii python3-pyinotify0.9.6-1.3 ii python3-toml 0.10.1-1 Versions of packages lintian-brush suggests: pn breezy-debian pn gnome-pkg-tools ii po-debconf 1.0.21+nmu1 pn postgresql-common -- no debconf information
Bug#924401: #924401 base-files fails postinst when base-passwd is unpacked
On Mon, 22 Feb 2021, Helmut Grohne wrote: On Mon, Feb 22, 2021 at 07:33:10AM +, Tim Woodall wrote: A. /etc/passwd is part of base-passwd's interface and base-files is right in relying on it working at all times. Then base-passwd is rc buggy for violating a policy must. Fixing this violation is technically impossible. I seem to have hit this same issue independently. Could you explain why "Fixing this violation is technically impossible" The requirement here is that base-passwd needs to work when unpacked. The only way to make that work is making /etc/passwd a conffile. That would technically be possible, but it would be very annoying, because this file is different on virtually any Debian installation. So we cannot make it a conffile in practice. The next bet would be ensuring that base-passwd.postinst is run before other packages' postint somehow. Such an ordering mechanism does not exist at present and it would be prone to dependency loops. As far as I can see, making base-passwd not essential, only required, and then making passwd and base-files pre-depend on base-passwd the system seems to bootstrap /etc/passed and /etc/group OK. What you write is almost certainly self-contradictory. base-files is essential. Anything it depends on (including base-passwd in your scenario) is pseudo-essential and thus inherits all the same requirements except for actually being essential. You gained nothing. And you didn't explain how you'd make base-passwd non-essential. That also seems to conform to the debian policy. The oddity is that base-files and passwd only actually need to depend on base-passwd, not pre-depend on it as they only use /etc/passwd and /etc/group in the postinst scripts but the debian policy doesn't seem to consider this case. They don't have to depend on base-passwd at all, because dependencies on essential packages should be omitted. If base-passwd wasn't essential then passwd and base-files should depend on it. If passwd and base-files (pre)depend on base-passwd then base-passwd will be configured before passwd or base-files postinst is run. I suggest that you detail on the practical issue you have been hitting. Doing so allows evaluating prospective solutions against all relevant use cases. What I am doing - which seems similar to what others are doing with other tools, is to: 1. unpack apt, dpkg and debian-archive-keyring data.tar.xz into tmpdir/ (This provides a set of config that apt needs to run) 2. create a sources.list in tmpdir and touch image/var/lib/dpkg/status (dpkg needs this file to exist) 3. apt-get install -o RootDir=tmpdir -d $ESSENTIAL (This resolves all of the dependencies and downloads every package that needs to be installed. I cannot see a way to get apt to do this without jumping through the hoops of step 1 and 2 as --reinstall doesn't re-download dependencies) 4. unpack the data.tar.xz from every deb downloaded in 3 into image/ 5. repeat step 2 but in image/ 6. chroot image/ apt-get update apt-get install $ESSENTIAL And expect that to create a fully configured system. For buster at least, the _only_ sticking point is apt not configuring base-passwd early enough so one or the other of base-files and passwd postinst fails. I've created local copies of those two that have an explicit dependency on base-passwd and the problem is solved. I haven't tried with unstable or bullseye yet but I don't immediately see any other issues. Tim.
Bug#983346: Update gitlab to 13.7.7 (installation fails - need help)
Package: gitlab Severity: important Control: tags -1 help I'm trying to update gitlab to 13.7.7 (master-13.7 branch in salsa), but installation fails with Bundle complete! 212 Gemfile dependencies, 393 gems now installed. Gems in the groups development and test were not installed. Use `bundle info [gemname]` to see where a bundled gem is installed. gitlab_production database is not empty, skipping gitlab setup fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git Attention: used pure ruby version of MurmurHash3 rake aborted! Feature::InvalidFeatureFlagError: Feature flag 'api_kaminari_count_with_limit' is al ready defined in '/usr/share/gitlab/config/feature_flags/ops/api_kaminari_count_with _limit.yml' /usr/share/gitlab/lib/feature/definition.rb:165:in `block in load_all_from_path!' /usr/share/gitlab/lib/feature/definition.rb:161:in `each' /usr/share/gitlab/lib/feature/definition.rb:161:in `load_all_from_path!' /usr/share/gitlab/lib/feature/definition.rb:146:in `block in load_all!' /usr/share/gitlab/lib/feature/definition.rb:145:in `each' /usr/share/gitlab/lib/feature/definition.rb:145:in `each_with_object' /usr/share/gitlab/lib/feature/definition.rb:145:in `load_all!' /usr/share/gitlab/lib/feature/definition.rb:102:in `reload!' /usr/share/gitlab/lib/feature.rb:141:in `register_definitions' /usr/share/gitlab/config/initializers/0_inject_feature_flags.rb:5:in ` )>' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:318:in `load' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:318:in `block in load' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:291:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:318:in `load' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/engine.rb:666:in `block in load_config_initializer' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/no tifications.rb:182:in `instrument' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/engine.rb:665:in `load_config_initializer' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/engine.rb:625:in `block (2 levels) in ' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/engine.rb:624:in `each' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/engine.rb:624:in `block in ' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/initializable.rb :32:in `instance_exec' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/initializable.rb :32:in `run' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/initializable.rb :61:in `block in run_initializers' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/initializable.rb :50:in `each' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/initializable.rb :50:in `tsort_each_child' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/initializable.rb :60:in `run_initializers' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/application.rb:3 63:in `initialize!' /usr/share/gitlab/config/environment.rb:5:in `' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:324:in `require' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:324:in `block in require' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:291:in `load_dependency' /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/de pendencies.rb:324:in `require' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/application.rb:3 39:in `require_environment!' /usr/share/rubygems-integration/all/gems/railties-6.0.3.4/lib/rails/application.rb:5 23:in `block in run_tasks_blocks' /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in ` >' Tasks: TOP => db:migrate => db:load_config => environment (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit st atus 1 Errors were encountered while processing: gitlab E: Sub-process /usr/bin/dpkg returned an error code (1) Usually such errors come from an obsolete initializer, but 0_inject_feature_flags.rb mentioned in the log is still present in upstream version. Help in fixing this error welcome.
Bug#895091: openldap: Please replace 'c_rehash' with 'openssl rehash'
Control: tag -1 fixed-upstream https://git.openldap.org/openldap/openldap/-/commit/58caa2f8877d0c8562932fe063c401b0be9c19c6
Bug#983344: ffmpeg: FTBFS on hppa - Please remove dependence on librsvg
Source: ffmpeg Version: 7:4.3.2-0+deb11u1 Severity: normal Dear Maintainer, The rust compiler is needed to build the librsvg package and for dh_cargo. It is not supported on hppa and several other architectures in Debian ports. Would you please change ffmpeg to build without librsvg on hppa. Thanks, Dave Anglin -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.10.17+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#962259: ruby-rqrcode 1.1.2-3 breaks 2FA settings page
Hi, I actually found the culprit — it's actually ruby-rqrcode. Downgrading to 0.4.2-3 fixed the issue of the 2FA page. I also found this in my logs: Started GET "/-/profile/two_factor_auth" for 10.32.5.1 at 2021-02-22 17:25:44 +0100 Processing by Profiles::TwoFactorAuthsController#show as HTML Completed 500 Internal Server Error in 368ms (ActiveRecord: 14.7ms | Elasticsearch: 0.0ms | Allocations: 89772) NoMethodError (undefined method `module_count' for # Did you mean? modules): app/controllers/profiles/two_factor_auths_controller.rb:134:in `build_qr_code' app/controllers/profiles/two_factor_auths_controller.rb:39:in `show' app/controllers/application_controller.rb:499:in `set_current_admin' lib/gitlab/session.rb:11:in `with_session' So, apparently, the newer ruby-rqrcode version breaks the 2FA settings page. Best, Maximilian OpenPGP_signature Description: OpenPGP digital signature
Bug#983343: xrootd: demote sphinx dependency to B-D-I
Source: xrootd Version: 5.0.3-4 Tags: patch User: debian-cr...@lists.debian.org Usertags: cross-satisfiability Hi, xrootd cannot cross built from source, because its sphinx dependency is not satisfiable. Since the documentation is already split to an arch:all package and the documentation is only built during an arch-only build, all that needs doing is restricting the usage of the shpinxdoc addon to the indep part. Please consider applying the attached patch. Nilesh diff --git a/debian/control b/debian/control index 02c4c08..3df1f2c 100644 --- a/debian/control +++ b/debian/control @@ -20,11 +20,13 @@ Build-Depends: graphviz, libsystemd-dev [linux-any], python3-dev, - python3-sphinx, libjson-c-dev, libmacaroons-dev, uuid-dev, voms-dev +Build-Depends-Indep: + dh-sequence-sphinxdoc, + python3-sphinx Homepage: http://xrootd.org/ Maintainer: Mattias Ellert Vcs-Browser: https://salsa.debian.org/ellert/xrootd diff --git a/debian/rules b/debian/rules index 389bf2f..0bd7da6 100755 --- a/debian/rules +++ b/debian/rules @@ -2,7 +2,7 @@ # -*- makefile -*- %: - dh $@ --with python3 --with sphinxdoc + dh $@ --with python3 override_dh_auto_configure: dh_auto_configure -- \
Bug#586264: SV: Bug#586264: probably belongs to sudo
Hi Marc I can, unfortunately, not. My laptop from back then has been buried since a long time ago and my current one does not have a driver for the fingerprint reader, so I have not been using fprint for years. Best regards Rasmus Rasmus Bøg Hansen Sent from phone Marc Haber skrev >On Fri, Aug 27, 2010 at 06:25:01PM +0100, Jonathan Wiltshire wrote: >> Given the bug in upstream sudo [1], I think this should be reassigned to >> it. >> >> 1: http://www.sudo.ws/bugs/show_bug.cgi?id=388 > >That issue was marked as fixed in the mean time. Rasmus, can you please >verify that sudo in current Debian works with libpam-fprint? > >If you don't reply, I plan closing this bug report by the end of June >2021. > >Greetings >Marc >
Bug#983335: sdbus-cpp: support Multiarch and nodoc/nocheck build profiles/options
On Mon, Feb 22, 2021 at 04:33:32PM +, Luca Boccassi wrote: > > > Subject: [PATCH 5/5] Add support for nodoc build option/profile > > > > > > > Applied without check nodoc in d/rules. As building doc is already in > > -indep target. And the -doc is the only arch all package. > > That adds an additional requirement though - doing a binary build > together with the nodoc profile. Also, the binary build will fail > without passing -DBUILD_DOC=OFF to the binary configure, since it's > default-enabled and will fail when looking for the doxygen binary. > I have verified with `sbuild --profiles=nodoc --no-arch-all`. Is there anything I miss?
Bug#983342: python3-simpletal: cgi.escape removed in python3.8
Package: python3-simpletal
Version: 5.2-1.1
Severity: important
Tags: patch upstream
X-Debbugs-Cc: cont...@olivieraubert.net
Dear Maintainer,
the cgi.escape method (which is used in simpleTALUtils) has been marked as
deprecated since python 3.2, and removed in python3.8. To make it work
with current python versions, cgi.escape should be replaced by html.escape
Here is a patch for fixing this issue. I also have reported it upstream.
Best regards, and thanks for you work
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-simpletal depends on:
ii python3 3.9.1-1
python3-simpletal recommends no packages.
python3-simpletal suggests no packages.
-- no debconf information
diff --git a/lib/simpletal/simpleTALUtils.py b/lib/simpletal/simpleTALUtils.py
index ee78690..860d74f 100644
--- a/lib/simpletal/simpleTALUtils.py
+++ b/lib/simpletal/simpleTALUtils.py
@@ -34,7 +34,7 @@
Module Dependencies: None
"""
-import io, os, stat, threading, sys, codecs, cgi, re, types, logging
+import io, os, stat, threading, sys, codecs, html, re, types, logging
from . import __version__, simpleTAL
# This is used to check for already escaped attributes.
@@ -114,7 +114,7 @@ def tagAsText (tag,atts):
# We already have some escaped characters in here, so
assume it's all valid
result += ' %s="%s"' % (name, value)
else:
- result += ' %s="%s"' % (name, cgi.escape (value))
+ result += ' %s="%s"' % (name, html.escape (value))
result += ">"
return result
@@ -195,11 +195,11 @@ def cmdEndTagEndScope (self, command, args):
self.file.write (str (str
(resultVal), 'ascii'))
else:
if (isinstance (resultVal, str)):
- self.file.write (cgi.escape (resultVal))
+ self.file.write (html.escape
(resultVal))
elif (isinstance (resultVal, bytes)):
- self.file.write (cgi.escape (str
(resultVal, 'ascii')))
+ self.file.write (html.escape (str
(resultVal, 'ascii')))
else:
- self.file.write (cgi.escape (str (str
(resultVal), 'ascii')))
+ self.file.write (html.escape (str (str
(resultVal), 'ascii')))
if (self.outputTag and not args[1]):
self.file.write ('')
Bug#983335: sdbus-cpp: support Multiarch and nodoc/nocheck build profiles/options
On Tue, 2021-02-23 at 00:22 +0800, Shengjing Zhu wrote: > On Mon, Feb 22, 2021 at 02:47:20PM +, Luca Boccassi wrote: > > Source: sdbus-cpp > > Version: 0.8.3-3 > > Tags: patch > > > > Dear Maintainer, > > > > Please find attached some patches to enable multiarch support and > > nodoc/nocheck build profiles (for easier > > crossbuild/bootstrap/backport). > > > > -- > > Kind regards, > > Luca Boccassi > > Subject: [PATCH 1/5] libsdbus-c++-dev: downgrade Depends on libsdbus-c++-bin > > to Suggests > > > > It is not actually necessary to use the library headers and link against > > the shared object, it's a useful development tool. A Suggests is enough > > and doesn't have side effects on Multiarch installations. > > --- > > Will apply after bullseye. Otherwise anbox will FTBFS. This is required for multiarch though. An alternative could be to mark the dependency as :native and the bin package as "Multi-Arch: allowed". Then it should be satisfiable from another architecture (eg: libsdbuscpp-dev:i386 can be installed with libsdbuscpp-bin:amd64). > > Subject: [PATCH 2/5] Enable Multiarch support > > Applied > > > From 14bff4c1d7c4c1af021d189ff4df378e41d50141 Mon Sep 17 00:00:00 2001 > > From: Luca Boccassi > > Date: Mon, 22 Feb 2021 13:43:34 + > > Subject: [PATCH 3/5] Add support for nocheck build option/profile > > > > Applied without checking DEB_BUILD_PROFILES. > The spec says: > > Builds that set this profile must also add nocheck to DEB_BUILD_OPTIONS > > So the DEB_BUILD_OPTIONS is always available. With DEB_BUILD_OPTIONS and > debhelper-compat 13, there's no need to check nocheck in dh_auto_test. > > > Subject: [PATCH 4/5] Mark d/rules as executable > > > > Applied. > > > Subject: [PATCH 5/5] Add support for nodoc build option/profile > > > > Applied without check nodoc in d/rules. As building doc is already in > -indep target. And the -doc is the only arch all package. That adds an additional requirement though - doing a binary build together with the nodoc profile. Also, the binary build will fail without passing -DBUILD_DOC=OFF to the binary configure, since it's default-enabled and will fail when looking for the doxygen binary. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#983335: sdbus-cpp: support Multiarch and nodoc/nocheck build profiles/options
On Mon, Feb 22, 2021 at 02:47:20PM +, Luca Boccassi wrote: > Source: sdbus-cpp > Version: 0.8.3-3 > Tags: patch > > Dear Maintainer, > > Please find attached some patches to enable multiarch support and > nodoc/nocheck build profiles (for easier > crossbuild/bootstrap/backport). > > -- > Kind regards, > Luca Boccassi > Subject: [PATCH 1/5] libsdbus-c++-dev: downgrade Depends on libsdbus-c++-bin > to Suggests > > It is not actually necessary to use the library headers and link against > the shared object, it's a useful development tool. A Suggests is enough > and doesn't have side effects on Multiarch installations. > --- Will apply after bullseye. Otherwise anbox will FTBFS. > Subject: [PATCH 2/5] Enable Multiarch support Applied > From 14bff4c1d7c4c1af021d189ff4df378e41d50141 Mon Sep 17 00:00:00 2001 > From: Luca Boccassi > Date: Mon, 22 Feb 2021 13:43:34 + > Subject: [PATCH 3/5] Add support for nocheck build option/profile > Applied without checking DEB_BUILD_PROFILES. The spec says: Builds that set this profile must also add nocheck to DEB_BUILD_OPTIONS So the DEB_BUILD_OPTIONS is always available. With DEB_BUILD_OPTIONS and debhelper-compat 13, there's no need to check nocheck in dh_auto_test. > Subject: [PATCH 4/5] Mark d/rules as executable > Applied. > Subject: [PATCH 5/5] Add support for nodoc build option/profile > Applied without check nodoc in d/rules. As building doc is already in -indep target. And the -doc is the only arch all package.
Bug#924401: #924401 base-files fails postinst when base-passwd is unpacked
On Mon, Feb 22, 2021 at 07:33:10AM +, Tim Woodall wrote: > A. /etc/passwd is part of base-passwd's interface and base-files is >right in relying on it working at all times. Then base-passwd is rc >buggy for violating a policy must. Fixing this violation is >technically impossible. > > > I seem to have hit this same issue independently. > > Could you explain why "Fixing this violation is technically impossible" The requirement here is that base-passwd needs to work when unpacked. The only way to make that work is making /etc/passwd a conffile. That would technically be possible, but it would be very annoying, because this file is different on virtually any Debian installation. So we cannot make it a conffile in practice. The next bet would be ensuring that base-passwd.postinst is run before other packages' postint somehow. Such an ordering mechanism does not exist at present and it would be prone to dependency loops. > As far as I can see, making base-passwd not essential, only required, > and then making passwd and base-files pre-depend on base-passwd the > system seems to bootstrap /etc/passed and /etc/group OK. What you write is almost certainly self-contradictory. base-files is essential. Anything it depends on (including base-passwd in your scenario) is pseudo-essential and thus inherits all the same requirements except for actually being essential. You gained nothing. And you didn't explain how you'd make base-passwd non-essential. > That also seems to conform to the debian policy. The oddity is that > base-files and passwd only actually need to depend on base-passwd, not > pre-depend on it as they only use /etc/passwd and /etc/group in the > postinst scripts but the debian policy doesn't seem to consider this > case. They don't have to depend on base-passwd at all, because dependencies on essential packages should be omitted. I suggest that you detail on the practical issue you have been hitting. Doing so allows evaluating prospective solutions against all relevant use cases. Helmut
Bug#580606: can be done differently
On Fri, May 21, 2010 at 01:37:00PM +0200, martin f krafft wrote: > Anyway, I think it would make more sense to do this analogously to > NOPASSWD. So this issue can be closed now? Greetings Marc
Bug#586264: probably belongs to sudo
On Fri, Aug 27, 2010 at 06:25:01PM +0100, Jonathan Wiltshire wrote: > Given the bug in upstream sudo [1], I think this should be reassigned to > it. > > 1: http://www.sudo.ws/bugs/show_bug.cgi?id=388 That issue was marked as fixed in the mean time. Rasmus, can you please verify that sudo in current Debian works with libpam-fprint? If you don't reply, I plan closing this bug report by the end of June 2021. Greetings Marc
Bug#983341: ITP: python-epimodels -- simple interface to simulate mathematical epidemic models in Python3
Package: wnpp Severity: wishlist Subject: ITP: python-epimodels -- simple interface to simulate mathematical epidemic models in Python3 Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: python-epimodels Version : 0.3.18 Upstream Author : Flávio Codeço Coelho * URL : https://github.com/fccoelho/epimodels * License : MIT Programming Lang: Python Description : simple interface to simulate mathematical epidemic models in Python3 This library provides a simple interface to simulate mathematical epidemic models in Python3. It is a precondition for the program epigrass. Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/python-epimodels
