Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell

[Cyril Brulebois]

Philip Hands  (2021-04-24):
> Steve McIntyre  writes:
> 
> ...
> > From checking (as discussed in IRC with Phil), rescue-mode moved from
> > 1.78 to 1.80 between those two builds. The only changes were in
> > translations, so the problem must be elsewhere. :-(
> 
> I've now caused the test job to record the installed udebs in the
> installer at the end of the session, which can be found here:
> 
> alpha2 (working):
>   https://openqa.debian.net/tests/1565/file/rescue-DI-installed-pkgs.txt
> 
> alpha3 (broken): 
>   https://openqa.debian.net/tests/1582/file/rescue-DI-installed-pkgs.txt
> 
> I attach a wdiff of those showing what changed between working and
> broken.  Sadly I've so far failed to spot the significant difference.

Thanks.




cdebconf-* were updated. There's a change in there but apparently only
for the text frontend.

At least for src:cdebconf's udebs, the libc they were built against is
no longer the same (2.29 vs. 2.31).

This might very well be a red herring, though.



FWIW: I plan to debug (likely starting by bisecting) this somewhen
during the week-end or next week.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell

[Philip Hands]

Steve McIntyre  writes:

...
> From checking (as discussed in IRC with Phil), rescue-mode moved from
> 1.78 to 1.80 between those two builds. The only changes were in
> translations, so the problem must be elsewhere. :-(

I've now caused the test job to record the installed udebs in the
installer at the end of the session, which can be found here:

alpha2 (working):
  https://openqa.debian.net/tests/1565/file/rescue-DI-installed-pkgs.txt

alpha3 (broken): 
  https://openqa.debian.net/tests/1582/file/rescue-DI-installed-pkgs.txt

I attach a wdiff of those showing what changed between working and
broken.  Sadly I've so far failed to spot the significant difference.

Cheers, Phil.


signature.asc
Description: PGP signature
Listing...
[-acpi-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+acpi-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
alsa-utils-udeb/now [-1.2.2-1-] {+1.2.3-1+} none [installed,local]
anna/now [-1.75-] {+1.78+} none [installed,local]
apt-cdrom-setup/now [-1:0.156-] {+1:0.160+} none [installed,local]
apt-mirror-setup/now [-1:0.156-] {+1:0.160+} none [installed,local]
apt-setup-udeb/now [-1:0.156-] {+1:0.160+} none [installed,local]
archdetect/now [-1.139-] {+1.142+} none [installed,local]
[-ata-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+ata-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
base-installer/now [-1.193-] {+1.198+} none [installed,local]
bogl-bterm-udeb/now [-0.1.18-14-] {+0.1.18-16+} none [installed,local]
bootstrap-base/now [-1.193-] {+1.198+} none [installed,local]
brltty-udeb/now [-6.0+dfsg-4+b1-] {+6.1+dfsg-3+} none [installed,local]
[-btrfs-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+btrfs-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
btrfs-progs-udeb/now [-5.4.1-2-] {+5.9-1+} none [installed,local]
busybox-udeb/now [-1:1.30.1-4-] {+1:1.30.1-6+} none [installed,local]
ca-certificates-udeb/now [-20190110-] {+20200601+} none [installed,local]
cdebconf-gtk-terminal/now [-0.38-] {+0.39+} none [installed,local]
cdebconf-gtk-udeb/now [-0.251-] {+0.255+} none [installed,local]
cdebconf-newt-terminal/now [-0.38-] {+0.39+} none [installed,local]
cdebconf-newt-udeb/now [-0.251-] {+0.255+} none [installed,local]
cdebconf-priority/now [-0.251-] {+0.255+} none [installed,local]
cdebconf-text-udeb/now [-0.251-] {+0.255+} none [installed,local]
cdebconf-udeb/now [-0.251-] {+0.255+} none [installed,local]
cdrom-checker/now [-1.46-] {+1.49+} none [installed,local]
[-cdrom-core-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+cdrom-core-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
cdrom-detect/now [-1.88-] {+1.91+} none [installed,local]
cdrom-retriever/now [-1.49-] {+1.52+} none [installed,local]
choose-mirror-bin/now [-2.101-] {+2.108+} none [installed,local]
clock-setup/now [-0.145 none [installed,local]
compress-modules-5.4.0-4-amd64-di/now 5.4.19-1-] {+0.148+} none 
[installed,local]
console-setup-linux-fonts-udeb/now [-1.194-] {+1.199+} none [installed,local]
console-setup-pc-ekmap/now [-1.194-] {+1.199+} none [installed,local]
console-setup-udeb/now [-1.194-] {+1.199+} none [installed,local]
[-crc-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+crc-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
[-crypto-dm-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+crypto-dm-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
[-crypto-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+crypto-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
cryptsetup-udeb/now [-2:2.3.0-1-] {+2:2.3.4-1+} none [installed,local]
debian-archive-keyring-udeb/now 2019.1 none [installed,local]
debian-installer/now [-cdrom-gtk-20200314-] {+cdrom-gtk-20201202+} none 
[installed,local]
debootstrap-udeb/now [-1.0.119-] {+1.0.123+} none [installed,local]
di-utils-mapdevfs/now [-1.133-] {+1.136+} none [installed,local]
di-utils-reboot/now [-1.133-] {+1.136+} none [installed,local]
di-utils-shell/now [-1.133-] {+1.136+} none [installed,local]
di-utils-terminfo/now [-1.133-] {+1.136+} none [installed,local]
di-utils/now [-1.133-] {+1.136+} none [installed,local]
disk-detect/now [-1.139-] {+1.142+} none [installed,local]
dmidecode-udeb/now [-3.2-3-] {+3.3-1+} none [installed,local]
dmsetup-udeb/now [-2:1.02.167-1+b1-] {+2:1.02.173-1+} none [installed,local]
dosfstools-udeb/now 4.1-2 none [installed,local]
e2fsprogs-udeb/now [-1.45.5-2-] {+1.45.6-1+} none [installed,local]
[-efi-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+efi-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]
eject-udeb/now [-2.1.5+deb1+cvs20081104-14+b1-] {+2.36.1-1+} none 
[installed,local]
env-preseed/now [-1.105-] {+1.107+} none [installed,local]
espeak-ng-data-udeb/now [-1.50+dfsg-6-] {+1.50+dfsg-7+} none [installed,local]
espeakup-udeb/now [-1:0.80-16+b1-] {+1:0.80-19+} none [installed,local]
ethdetect/now [-1.139-] {+1.142+} none [installed,local]
[-event-modules-5.4.0-4-amd64-di/now 5.4.19-1-]
{+event-modules-5.9.0-4-amd64-di/now 5.9.11-1+} none [installed,local]

Bug#972570: [Pkg-javascript-devel] Bug#972570: node-lightgallery is built using minified files

[Daniel Ring]

The warnings are already overridden in the current version on Salsa, 
since the Youtube/Vimeo/etc. embeds are only loaded when Lightgallery is 
used to display a video from that source (e.g. by passing it a Youtube 
link).


Sincerely,
Daniel Ring

On 4/23/2021 12:31 PM, Yadd wrote:

Le 23/04/2021 à 19:03, Jonas Smedegaard a écrit :

Quoting Yadd (2021-04-23 17:47:23)

Control: tags -1 + pending

Le 23/04/2021 à 09:44, Daniel Ring a écrit :

Hello Xavier,

It looks like the build process was minifying the source files to the
destination *.js files and copying the pre-minified files to *.min.js. I
corrected it to copy the unminified files directly and minify them to
*.min.js.

I also updated the package on Salsa to exclude the minified
modules/*.min.js files via Files-Excluded in d/copyright, so they're no
longer in the source package at all.

Sincerely,
Daniel Ring


Hi,

looks good to me, thanks! Could you also ignore these warnings in a
debain/lintian-overrides? It looks like false positive

Cheers,
Yadd

  W: node-lightgallery: privacy-breach-generic
usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [
[...]
Those warnings look real to me.

What makes you consider them false positives, Xavier?


Hi Jonas,

yes but the relevant lines are in if/then/else blocks:

   if (isVideo.youtube) {
 ...  video = '

Bug#919696: Not a bug

[Brian Aker]

Here is the longer response:

https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1573594/comments/38

The original author of the bug did not read the internals of the code 
thoroughly enough to realize that the buffer would never be used if an error 
occurred, otherwise memcached_response will NULL terminate the string.

乌

Bug#987176: plasma-desktop: Default application for .deb files is broken on clean install

[Caleb McKay]

application/vnd.debian.binary-package

and

org.kde.apper.desktop

Is what I get on a clean installation.

Perhaps it is different when installing from the live CD? I haven't tried 
installing from the standard installer with Bullseye, but I am pretty sure the 
with Buster I would get the same result even in the standard install. I'd be 
happy to test it if it would be any help.

But I think it isn't so much a problem with mime associations in general. There 
seems to be some outstanding issues with apper when I glance through the bug 
reports. Switching the file association to discover works fines. And when I do 
so I get the same results you do when running

xdg-mime query filetype XXX.deb

org.kde.discover.desktop

Thanks,

Caleb


On Mon, 19 Apr 2021 17:02:55 +0900 Norbert Preining  
wrote:

> Jo

>

> >* What exactly did you do (or not do) that was effective (or

> >  ineffective)? Tried to install a .deb by double clicking on it in 
> > Dolphin

> >* What was the outcome of this action? Nothing happens

>

> With an existing XXX.deb (one that you wanted to open), what does (on

> the command line)

> xdg-mime query filetype XXX.deb

> say?

>

> In my case it is

> application/vnd.debian.binary-package

>

> After that, what does

> xdg-mime query default $(xdg-mime query filetype XXX.deb)

> say?

>

> In my case it is

> org.kde.discover.desktop

>

> This is a problem of mime type associations, and this is - honestly

> spoken - completely broken in Debian at the moment. THere is work going

> on but I am not sure how far this has proceeded.

>

> Best

>

> Norbert

>

> --

> PREINING Norbert  https://www.preining.info

> Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev

> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

>

>

=<161879847068.4985.8620406809901655187.reportbug@caleb-omen>

 

Bug#987448: webkit2gtk regression: liferea: CSS for the posts is broken

[Paul Wise]

Package: libwebkit2gtk-4.0-37
Version: 2.32.0-2
Severity: serious
Control: affects -1 liferea
X-Debbugs-CC: life...@packages.debian.org

The recent upgrade to webkit2gtk 2.32.0-2 broke the CSS that the
liferea RSS reader uses to style the HTML it injects for post metadata.

By default liferea looks like this before and after the upgrade:

https://people.debian.org/~pabs/tmp/webkit2gtk-liferea-regression/before.png
https://people.debian.org/~pabs/tmp/webkit2gtk-liferea-regression/after.png

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental'), 
(500, 'testing-security')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libwebkit2gtk-4.0-37 depends on:
ii  bubblewrap  0.4.1-3
ii  libatk1.0-0 2.36.0-2
ii  libc6   2.31-11
ii  libcairo2   1.16.0-5
ii  libegl1 1.3.2-1
ii  libenchant-2-2  2.2.15-1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgcc-s1   10.2.1-6
ii  libgcrypt20 1.8.7-3
ii  libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii  libgl1  1.3.2-1
ii  libglib2.0-02.66.8-1
ii  libgstreamer-gl1.0-01.18.4-2
ii  libgstreamer-plugins-base1.0-0  1.18.4-2
ii  libgstreamer1.0-0   1.18.3-2
ii  libgtk-3-0  3.24.24-3
ii  libharfbuzz-icu02.7.4-1
ii  libharfbuzz0b   2.7.4-1
ii  libhyphen0  2.8.8-7
ii  libicu6767.1-6
ii  libjavascriptcoregtk-4.0-18 2.32.0-2
ii  libjpeg62-turbo 1:2.0.6-4
ii  libmanette-0.2-00.2.5-1
ii  libnotify4  0.7.9-3
ii  libopenjp2-72.4.0-3
ii  libpango-1.0-0  1.46.2-3
ii  libpng16-16 1.6.37-3
ii  libseccomp2 2.5.1-1
ii  libsecret-1-0   0.20.4-2
ii  libsoup2.4-12.72.0-2
ii  libsqlite3-03.34.1-3
ii  libstdc++6  10.2.1-6
ii  libsystemd0 247.3-3
ii  libtasn1-6  4.16.0-2
ii  libwayland-client0  1.18.0-2~exp1.1
ii  libwayland-egl1 1.18.0-2~exp1.1
ii  libwayland-server0  1.18.0-2~exp1.1
ii  libwebp60.6.1-2+b1
ii  libwebpdemux2   0.6.1-2+b1
ii  libwoff11.0.2-1+b1
ii  libwpe-1.0-11.6.0-1
ii  libwpebackend-fdo-1.0-1 1.8.0-1
ii  libx11-62:1.7.0-2
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxml2 2.9.10+dfsg-6.3+b1
ii  libxslt1.1  1.1.34-4
ii  xdg-dbus-proxy  0.1.2-2
ii  xdg-desktop-portal-gtk  1.8.0-1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages libwebkit2gtk-4.0-37 recommends:
ii  gstreamer1.0-alsa  1.18.4-2
ii  gstreamer1.0-gl1.18.4-2
ii  gstreamer1.0-libav 1.18.4-3
ii  gstreamer1.0-plugins-good  1.18.4-2
ii  gstreamer1.0-pulseaudio1.18.4-2
ii  libgl1-mesa-dri21.0.2-1

libwebkit2gtk-4.0-37 suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#987447: unblock: ddskk/17.1-4+deb11u1

[Tatsuya Kinoshita]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package ddskk.

[ Reason ]
The RC bug #987383, byte-compiling skk-bayesian.el conditionally fails.
  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987383

[ Impact ]
The testing version causes hang during dist-upgrading from buster
if ddskk is upgraded before emacs.

[ Tests ]
I did manual testing with the buster chroot environment, installing the
testing version failed as the RC bug and the updated version succeeded.

[ Risks ]
The skk-bayesian feature is optional and minor.  The fix may
decrease the speed of loading skk-bayesian.el, but it's trivial.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

unblock ddskk/17.1-4+deb11u1

Thanks,
-- 
Tatsuya Kinoshita
diffstat for ddskk-17.1 ddskk-17.1

 changelog |7 +++
 rules |1 +
 2 files changed, 8 insertions(+)

diff -Nru ddskk-17.1/debian/changelog ddskk-17.1/debian/changelog
--- ddskk-17.1/debian/changelog	2021-01-20 21:30:01.0 +0900
+++ ddskk-17.1/debian/changelog	2021-04-23 22:30:33.0 +0900
@@ -1,3 +1,10 @@
+ddskk (17.1-4+deb11u1) unstable; urgency=medium
+
+  * Don't byte-compile skk-bayesian.el to avoid hang during installation
+(closes: #987383)
+
+ -- Tatsuya Kinoshita   Fri, 23 Apr 2021 22:30:33 +0900
+
 ddskk (17.1-4) unstable; urgency=medium
 
   * New patch 030_skk-wrap.patch for org-mode and markdown-mode
diff -Nru ddskk-17.1/debian/rules ddskk-17.1/debian/rules
--- ddskk-17.1/debian/rules	2020-08-16 00:03:30.0 +0900
+++ ddskk-17.1/debian/rules	2021-04-23 22:26:23.0 +0900
@@ -31,6 +31,7 @@
 	dh_installdirs
 
 	cp -R *.el *.in SKK-* maint nicola tut-code/*.el bayesian/*.el debian/$(PACKAGE)/usr/share/$(PACKAGE)
+	perl -pwi -e 's/skk-bayesian/;;skk-bayesian/' debian/$(PACKAGE)/usr/share/$(PACKAGE)/SKK-MK
 	cp -f experimental/*.el debian/$(PACKAGE)/usr/share/$(PACKAGE)
 
 	rm -f debian/$(PACKAGE)/usr/share/$(PACKAGE)/nicola/Makefile


pgpPagESKXBbl.pgp
Description: PGP signature

Bug#987445: kvm: -usbdevice tablet: '-usbdevice' is deprecated, please use '-device usb-...' instead

[Carlos R. Pasqualini]

Package: ganeti-3.0
Version: 3.0.1-2
Severity: normal

Dear Maintainer,

Creating a new instance, looselly following:
https://ahwhattheheck.wordpress.com/2014/12/15/migrating-vms-from-a-libvirt-setup-to-a-ganeti-cluster/
as done before.

gnt-instance add -B vcpus=${VCPUS},minmem=${MINMEM},maxmem=${MAXMEM} \
-H
kvm:kernel_path='',machine_version='q35',nic_type='paravirtual',disk_ty
pe='paravirtual',scsi_controller_type='virtio-scsi-
pci',usb_mouse='tablet',keymap='es',use_guest_agent=true \
-t drbd --disk 0:size=${DISK_SIZE_0} \
-t drbd --disk 1:size=${DISK_SIZE_1} \ 
-n ${NODE1}:${NODE2} \ 
-o debootstrap+default \ 
--net 0:mac=${MAC},link=${VMBR} \ 
--no-ip-check --no-name-check \ 
--no-install --no-wait-for-sync ${VMNAME} 

And then writting a qemu image to the DRBD devices

No errors yet

but, on start I get:

root@hostname:~# gnt-instance start VMNAME 
Waiting for job 60574 for VMNAME ...
Job 60574 for VMNAME has failed: Failure: command execution error:
Could not start instance 'VMNAME': Hypervisor error: Failed to start
instance VMNAME: exited with exit code 1 (kvm: -usbdevice tablet: '-
usbdevice' is deprecated, please use '-device usb-...' instead
)


It seems weird, because the very same was reported and fixed on a pre
3.0 branch: https://github.com/ganeti/ganeti/issues/1338

Spent a few hours on this, but unable to find a workaround


Thanks for the help and, BTW: thanks for this great software


Best Regards

Carlos Pasqualini


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-security')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8),
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ganeti-3.0 depends on:
ii  adduser3.118
ii  bridge-utils   1.7-1
ii  debconf [debconf-2.0]  1.5.75
ii  fping  5.0-1
ii  iproute2   5.10.0-4
ii  iputils-arping 3:20210202-1
ii  libcap2-bin1:2.44-1
ii  lvm2   2.03.11-2.1
ii  openssh-client 1:8.4p1-5
ii  openssh-server 1:8.4p1-5
ii  openssl1.1.1k-1
ii  python33.9.2-2
ii  python3-bitarray   1.6.3-2+b1
ii  python3-openssl20.0.1-1
ii  python3-paramiko   2.7.2-1
ii  python3-psutil 5.8.0-1
ii  python3-pycurl 7.43.0.6-5
ii  python3-pyinotify  0.9.6-1.3
ii  python3-pyparsing  2.4.7-1
ii  python3-simplejson 3.17.2-1
ii  socat  1.7.4.1-3

ganeti-3.0 recommends no packages.

ganeti-3.0 suggests no packages.

-- debconf information:
  ganeti-3.0/abort-removal: true

Bug#987444: gnupg: include alternative dependencies to xloadimage

[Christoph Anton Mitterer]

Package: gnupg
Version: 2.2.27-1
Severity: wishlist


Hi.

It seems gpg can also use display and xdg-open instead of xloadimage.

Thus it would be nice to have those added as alternatives to the
package Suggests.

Cheers,
Chris.

Bug#987264: git-el: fails to install with xemacs21

[Adrian Bunk]

On Tue, Apr 20, 2021 at 05:10:16PM +0200, Andreas Beckmann wrote:
> Package: git-el
> Version: 1:2.30.2-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install if
> xemacs21 is already installed.

Most relevant is that emacs-common is *not* installed,
and neither any other package that ships /usr/share/emacs/site-lisp/

> >From the attached log (scroll to the bottom...):
> 
>   Setting up git-el (1:2.31.0+next.20210315-1) ...
>   Install git for emacs
>   install/git: Handling install of emacsen flavor emacs
>   mkdir: cannot create directory '/usr/share/emacs/site-lisp/git': No such 
> file or directory
>   /usr/lib/emacsen-common/packages/install/git emacs xemacs21 failed at 
> /usr/lib/emacsen-common/lib.pl line 19,  line 1.
>   dpkg: error processing package git-el (--configure):
>installed git-el package post-installation script subprocess returned 
> error exit status 2
>   Processing triggers for libc-bin (2.31-11) ...
>   Errors were encountered while processing:
>git-el
> 
> 
> cheers,
> 
> Andreas

cu
Adrian

Bug#984736:

[Brian Thompson]

>Ideally a maintainer willing to help cron move forward would support the next>major task to be done: moving the Debian-specific patches into cronie and >providing an updated package for cronie replacement that can eventually>replace cron. I’d like to help out here if no one else has responded.  I can read repositories on Salsa but don’t have an account there yet since I’m not officially a part of the Debian org. >Please contact the current maintainer if you can help in maintaining and>improving cron. @Javier, I cc’ed you and I think what is Christian’s email which I pulled from the cron git history. Best regards, Brian 

Bug#982917: nvme-cli: Add a nvme-cli-udeb package?

[Samuel Thibault]

Cyril Brulebois, le ven. 23 avril 2021 23:36:24 +0200, a ecrit:
> Samuel Thibault  (2021-04-23):
> > I don't have any particular pointer beyond stackoverflow
> > https://unix.stackexchange.com/questions/520231/what-are-nvme-namespaces-how-do-they-work
> > 
> > Basically they are a hardware-level partitioning, before the well-known
> > software partitioning: /dev/nvme0n1p1 is device 0, namespace 1,
> > partition 1.
> > 
> > > (My only experience was a fresh install on an NVMe device replacing an
> > > aging SSD, and I haven't had to do anything specific.)
> > 
> > I guess usually NVMe are shipped with a default namespace spanning the
> > whole disk, but that could be not always true.
> 
> OK. Would we expect to have something in the installation guide
> documenting how to create a namespace if there are none? Or would you
> like to implement a change in d-i to handle that in the regular debconf
> question flow?

Ideally we could have questions in d-i, but that seems quite involved
for a probably very rare need. We can however easily add a note about
the nvme manual commands in the guide, yes.

Samuel

Bug#987356: ignores path argument

[Andreas Rönnquist]

On Thu, 22 Apr 2021 17:14:53 +0800 Martin Michlmayr 
wrote:
> I just upgraded from buster to bullseye.  In bulseye, geeqie seems to
> ignore the "path" argument.
> 
> In the past,
> geeqie a/sunflower.jpg
> would work to open that particular photo.
> 
> Now geeqie just loads the current directory, as if I had called
> "geeqie".
> 
> Does "geeqie path" work for you?
> 

Thanks for your report - like Chris I cannot reproduce your problem -
just tested in an unstable VM, but unlike Chris, using Xfce, so it
doesn't seem to be depending on desktop...

Can you think of anything non-standard in your use-case? I have tested
having the image in a folder which is a symlink to the real folder, and
it still works, and have tested both pngs and jpgs, which both works.n

Do you have spaces or characters in the folder names which might cause
problems?

You could try to first backup your config folder 

$(HOME)/.config/geeqie/

and then delete it - it will regenerate a new fresh one when running
geeqie again (PLEASE don't forget to backup it before so you can restore
it after if you need the settings you have), and see if this affects
things.

/Andreas Rönnquist
gus...@debian.org

Bug#987426: juk: Volume slider displays wrong volume level

[Kirill Schmidt]

Package: juk
Version: 4:20.12.3-1
Severity: minor

When opening JuK the volume level is sometimes set to "-2.147.483.648%",
while the actual volume is unchanged. This issue can be resolved by
clicking on the volume slider, in which case it returns to a value
between 0-100%, with the actual volume increasing/decreasing.

-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages juk depends on:
ii  kio5.78.0-4
ii  libc6  2.31-11
ii  libgcc-s1  10.2.1-6
ii  libkf5completion5  5.78.0-3
ii  libkf5configcore5  5.78.0-4
ii  libkf5configwidgets5   5.78.0-2
ii  libkf5coreaddons5  5.78.0-4
ii  libkf5crash5   5.78.0-3
ii  libkf5dbusaddons5  5.78.0-2
ii  libkf5globalaccel-bin  5.78.0-3
ii  libkf5globalaccel5 5.78.0-3
ii  libkf5i18n55.78.0-2
ii  libkf5iconthemes5  5.78.0-2
ii  libkf5jobwidgets5  5.78.0-2
ii  libkf5kiocore5 5.78.0-4
ii  libkf5kiowidgets5  5.78.0-4
ii  libkf5notifications5   5.78.0-2
ii  libkf5textwidgets5 5.78.0-2
ii  libkf5wallet-bin   5.78.0-2
ii  libkf5wallet5  5.78.0-2
ii  libkf5widgetsaddons5   5.78.0-2
ii  libkf5windowsystem55.78.0-2
ii  libkf5xmlgui5  5.78.0-2
ii  libphonon4qt5-44:4.11.1-3
ii  libqt5core5a   5.15.2+dfsg-5
ii  libqt5dbus55.15.2+dfsg-5
ii  libqt5gui5 5.15.2+dfsg-5
ii  libqt5network5 5.15.2+dfsg-5
ii  libqt5svg5 5.15.2-3
ii  libqt5widgets5 5.15.2+dfsg-5
ii  libqt5xml5 5.15.2+dfsg-5
ii  libstdc++6 10.2.1-6
ii  libtag1v5  1.11.1+dfsg.1-3
ii  phonon4qt5 4:4.11.1-3

juk recommends no packages.

Versions of packages juk suggests:
ii  k3b  20.12.2-1

-- no debconf information

Bug#982917: nvme-cli: Add a nvme-cli-udeb package?

[Cyril Brulebois]

Hi,

Samuel Thibault  (2021-04-23):
> I don't have any particular pointer beyond stackoverflow
> https://unix.stackexchange.com/questions/520231/what-are-nvme-namespaces-how-do-they-work
> 
> Basically they are a hardware-level partitioning, before the well-known
> software partitioning: /dev/nvme0n1p1 is device 0, namespace 1,
> partition 1.
> 
> > (My only experience was a fresh install on an NVMe device replacing an
> > aging SSD, and I haven't had to do anything specific.)
> 
> I guess usually NVMe are shipped with a default namespace spanning the
> whole disk, but that could be not always true.

OK. Would we expect to have something in the installation guide
documenting how to create a namespace if there are none? Or would you
like to implement a change in d-i to handle that in the regular debconf
question flow?

Either way, adding a udeb for that doesn't seem like a bad idea.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#939585: installation-reports: confirmed with current installer

[Cyril Brulebois]

Control: tag -1 moreinfo

Norbert Preining  (2021-04-01):
> Same has happened on my system today, with a very recent installer.

Please share the installer's syslog (/var/log/installer), preferably
compressed due to mail size limits.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#982917: nvme-cli: Add a nvme-cli-udeb package?

[Samuel Thibault]

Hello,

Cyril Brulebois, le ven. 23 avril 2021 23:19:08 +0200, a ecrit:
> Samuel Thibault  (2021-02-16):
> > I was reinstalling a laptop after a NVME change, and I realized: what
> > if the NVME did not have any namespace set up? The installer would then
> > not recognize the disk. We would need at least the nvme command to be
> > available on the text console to fix this by hand (Ideally the installer
> > would even automatically propose to configure an NVME namespace).
> > 
> > Perhaps the addition of nvme-cli-udeb would be possible for bullseye
> > already? I could verify that the binary of the nvme-cli package does
> > work already, so it'd be a mere matter of adding the nvme-cli-udeb
> > package that just ships the /usr/sbin/nvme file.
> 
> I have absolutely no idea what NVME namespaces are and what they are
> needed for; would you have some pointers?

I don't have any particular pointer beyond stackoverflow
https://unix.stackexchange.com/questions/520231/what-are-nvme-namespaces-how-do-they-work

Basically they are a hardware-level partitioning, before the well-known
software partitioning: /dev/nvme0n1p1 is device 0, namespace 1,
partition 1.

> (My only experience was a fresh install on an NVMe device replacing an
> aging SSD, and I haven't had to do anything specific.)

I guess usually NVMe are shipped with a default namespace spanning the
whole disk, but that could be not always true.

Samuel

Bug#982745: nginx-common: don't enable TLSv1 or TLSv1.1 in default configuration

[Chris Hofstaedtler]

* didi.deb...@cknow.org  [210423 21:23]:
> TLSv1.2 was defined in 2008, so I don't think it's to 'wild' to use that
> as a default for security in the default configuration of nginx for Bullseye.

You seem to neglect to mention that SSL/TLS is disabled in the
default configuration. I agree that suggesting better defaults would
be preferable, but this is hardly an nginx-only problem, or would
it make nginx unusable.

Chris

Bug#987441: debian-installer: D-I must get ready for Bullseye

[Cyril Brulebois]

Cyril Brulebois  (2021-04-23):
> Carried over from D-I Bullseye RC 1 errata:
>  - amdgpu firmware

There's no “umbrella bug report” for it at the moment, but here's a
thread and pointers to various bug reports:
  https://lists.debian.org/debian-boot/2020/12/msg00026.html


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#982917: nvme-cli: Add a nvme-cli-udeb package?

[Cyril Brulebois]

Hi Samuel,

Samuel Thibault  (2021-02-16):
> I was reinstalling a laptop after a NVME change, and I realized: what
> if the NVME did not have any namespace set up? The installer would then
> not recognize the disk. We would need at least the nvme command to be
> available on the text console to fix this by hand (Ideally the installer
> would even automatically propose to configure an NVME namespace).
> 
> Perhaps the addition of nvme-cli-udeb would be possible for bullseye
> already? I could verify that the binary of the nvme-cli package does
> work already, so it'd be a mere matter of adding the nvme-cli-udeb
> package that just ships the /usr/sbin/nvme file.

I have absolutely no idea what NVME namespaces are and what they are
needed for; would you have some pointers?

(My only experience was a fresh install on an NVMe device replacing an
aging SSD, and I haven't had to do anything specific.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987443: RM: gimp-dcraw -- RoQA; superseded by functionality in gimp

[Chris Hofstaedtler]

Package: ftp.debian.org
Severity: normal

X-Debbugs-CC: gimp-dc...@packages.debian.org

Dear FTP team,

gimp-dcraw is a gimp plugin to read RAW file formats from various camera
vendors. It appears upstream has vanished, and no maintenance is going
on in Debian.
Also, it appears GIMP itself has learned how to import all those various
RAW file formats, and the native functionality looks nicer integrated at
first glance.

I'd say, lets remove the plugin in favor of the native feature.

Thanks,
Chris

Bug#986565: unusable with current git

[Chris Hofstaedtler]

Hi everyone,

* Lisandro Damián Nicanor Pérez Meyer  [210423 21:06]:
> Hi! Indeed it's not working again, so reopening the bug.
> 
> On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov  wrote:
> > Sigh. Now git reverted to using /usr/lib again, and git-flow is broken.

It appears some more coordination between git and related packages
would be in order.

Right now, the versions in testing do not work together:
  git 1:2.30.2-1 installs into /usr/lib
  git-flow 1.12.3-2 installs into /usr/libexec

I guess git 1:2.31.1-1 will be stuck in unstable?

Please somehow coordinate on what the correct path is/should be.

Thanks,
Chris

Bug#987442: node-jquery: package doesn't purge cleanly

[Christoph Anton Mitterer]

Package: node-jquery
Version: 3.5.1+dfsg+~3.5.5-7
Severity: normal


Hi.

When purging the package, stuff remains left over:
Removing node-jquery (3.5.1+dfsg+~3.5.5-7) ...
dpkg: warning: while removing node-jquery, directory 
'/usr/share/nodejs/jquery/dist' not empty so not removed


$ l /usr/share/nodejs/jquery/dist
total 398k
drwxr-xr-x 1 root root  202 Apr 23 22:57 .
drwxr-xr-x 1 root root8 Apr 23 22:57 ..
-rw-r--r-- 1 root root  90k Jan 12 21:55 jquery.min.js
-rw-r--r-- 1 root root  29k Jan 12 21:55 jquery.min.js.brotli
-rw-r--r-- 1 root root  30k Jan 12 21:55 jquery.min.js.gz
-rw-r--r-- 1 root root 138k Jan 12 21:55 jquery.min.map
-rw-r--r-- 1 root root  50k Jan 12 21:55 jquery.min.map.brotli
-rw-r--r-- 1 root root  53k Jan 12 21:55 jquery.min.map.gz

$ dpkg -S /usr/share/nodejs/jquery/dist
dpkg-query: no path found matching pattern /usr/share/nodejs/jquery/dist


Cheers,
Chris.

Bug#987441: debian-installer: D-I must get ready for Bullseye

[Cyril Brulebois]

Source: debian-installer
Version: 20210415
Severity: serious
Justification: meh.

Let's keep track of things that need to be looked at before D-I is
considered ready for the initial Bullseye release (11.0).

Carried over from D-I Bullseye RC 1 errata:
 - amdgpu firmware
 - broken rescue mode

Bugs reported against various packages or installation reports will
block this bug report until they are either fixed or ruled out as not
being actual blockers for the release.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs

[Hilko Bengen]

control: tag -1 confirmed
control: notfound -1 golang-github-hillu-go-yara/4.0.4-1

* Paul Gevers:

> Source: yara, golang-github-hillu-go-yara
> Control: found -1 yara/4.1.0~rc2-1
> Control: found -1 golang-github-hillu-go-yara/4.0.4-1
> Severity: serious
> Tags: sid bullseye ftbfs bullseye-ignore
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
>
> With a recent upload of yara the autopkgtest of
> golang-github-hillu-go-yara fails in testing when that autopkgtest is
> run with the binary packages of yara from unstable. It passes when run
> with only packages from testing. 

As the maintainer of the yara package and (upstream) author of go-yara,
I am aware of the problem. The culprit is the yara package, not
golang-github-hillu-go-yara.

I don't know yet how yara/4.1.0 will address the API/ABI incompatibility
issue that is the root cause of this bug. For the time being I think
I'll leave the yara package in unstable in its current broken state. (My
upload to unstable was an error.)

> Currently this regression is blocking the migration of yara to testing
> [1]. Due to the nature of this issue, I filed this bug report against
> both packages. Can you please investigate the situation and reassign the
> bug to the right package?

Done, see above. (I hope I have whispered the right things at the BTS.)

> With my Release Team member hat on, I have set this bug as
> bullseye-ignore, as without yara migrating, the packages in testing
> don't have a problem. So I really don't mind if this bug is fixed only
> after the bullseye release.

That was pretty much my plan. Thanks.

Cheers,
-Hilko

Bug#987368: Installer fails at first menu "Choose language"

[Cyril Brulebois]

Hello Frédéric,

Frédéric Bonnard  (2021-04-22):
> Boot method: CD
> Image version: 
> http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso
> Date: April 21st 2021
> 
> Machine: Power10 machine but got it on Power8 as well
> 
> This happens randomly when the installer menu starts, I get to the first
> menu "Choose language", but it is red saying "An installation failed...
> The failing step is: Choose language".
> 
> It seems the missing file /var/lib/dpkg/status is causing this.
> Instead I have /var/lib/dpkg/status.bak

I don't know much about ppc (I don't think iBook G4 experience counts
much at this stage), but I see that qemu-system-ppc exists, and that it
provides qemu-system-ppc64. Would you have some guide that could help us
reproduce the issue from say an amd64 host?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987356: ignores path argument

[Chris Hofstaedtler]

Hello Martin,

* Martin Michlmayr  [210423 20:46]:
> Version: 1:1.6-8
> In the past,
> geeqie a/sunflower.jpg
> would work to open that particular photo.
> 
> Now geeqie just loads the current directory, as if I had called
> "geeqie".

I tried reproducing this, but it seems to work just fine for me?
In a fresh bullseye VM in GNOME, that is.

Chris

Bug#987362: jupyter-qtconsole: failst to start on missing dependency

[Chris Hofstaedtler]

Control: tags -1 + moreinfo unreproducible

* Emilian Nowak  [210423 20:39]:
> Package: jupyter-qtconsole
> Version: 5.0.2-2
> Severity: important
[..]
> pkg_resources.VersionConflict: (qtconsole 4.7.6 (/usr/lib/python3/dist-
> packages), Requirement.parse('qtconsole==5.0.2'))
[..]
> ii  python3-qtconsole  4.7.6-1

This combination does not add up, and indeed I cannot reproduce this
when install jupyter-qtconsole from Debian testing. Please let us
know more about your local setup.

Chris

Bug#987371: unblock: at-spi2-core/2.38.0-4

[Cyril Brulebois]

Samuel Thibault  (2021-04-23):
> Ah, formally speaking this would also need an ack for the d-i side.

No objections, ta.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#986339: universal-ctags: diff for NMU version 0+git20200824-1.1

[Adrian Bunk]

Control: tags 986339 + pending

Dear maintainer,

I've prepared an NMU for universal-ctags (versioned as 
0+git20200824-1.1) and uploaded it to DELAYED/3. Please
feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru universal-ctags-0+git20200824/debian/changelog universal-ctags-0+git20200824/debian/changelog
--- universal-ctags-0+git20200824/debian/changelog	2020-08-24 12:57:20.0 +0300
+++ universal-ctags-0+git20200824/debian/changelog	2021-04-23 21:29:07.0 +0300
@@ -1,3 +1,11 @@
+universal-ctags (0+git20200824-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Handle deconfigure and upgrade in the prerm,
+thanks to Antonio Terceiro. (Closes: #986339)
+
+ -- Adrian Bunk   Fri, 23 Apr 2021 21:29:07 +0300
+
 universal-ctags (0+git20200824-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru universal-ctags-0+git20200824/debian/prerm universal-ctags-0+git20200824/debian/prerm
--- universal-ctags-0+git20200824/debian/prerm	2020-08-24 12:57:20.0 +0300
+++ universal-ctags-0+git20200824/debian/prerm	2021-04-23 21:29:07.0 +0300
@@ -3,12 +3,12 @@
 set -e
 
 case "$1" in
-remove)
+remove|deconfigure)
 update-alternatives --remove ctags /usr/bin/ctags-universal
 update-alternatives --remove etags /usr/bin/ctags-universal
 ;;
 
-failed-upgrade)
+upgrade|failed-upgrade)
 ;;
 
 *)

Bug#987440: release-notes: Mention GnuPG no longer reads ~/.gnupg/options

[Christoph Biedl]

Package: release-notes
Severity: normal
X-Debbugs-Cc: pkg-gnupg-ma...@lists.alioth.debian.org

Hello release team,

for the Debian 11 (bullseye) release notes, please consider mentioning
a change in the configuration file handling in GnuPG, related bug is
. Suggested text, as in NEWS.Debian
of 2.2.27-2 uploaded a few moments ago:

  Starting with version 2.2.27-1, per-user configuration of the GnuPG
  suite has completely moved to ~/.gnupg/gpg.conf, and ~/.gnupg/options
  is no longer in use.  Please rename the file if necessary, or move
  its contents to the new location.

By the way, there is *no* code change between 2.2.27-1 (in testing) and
2.2.27-2, only the above notice and an addition to Uploaders: list. So
if you want to unblock right away, I'll certainly not object. Else I
might file an according request soon.

Kind regards,

Christoph


signature.asc
Description: PGP signature

Bug#987439: neutron-vpnaas: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: neutron-vpnaas
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#987438: phonon: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: phonon
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#987437: dump1090-mutability: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: dump1090-mutability
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#987436: libcifpp: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: libcifpp
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#987435: prometheus-blackbox-exporter: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: prometheus-blackbox-exporter
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#987434: prometheus-homeplug-exporter: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: prometheus-homeplug-exporter
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#987420: hplip seems incompatible with current cups

[Yadd]

Le 23/04/2021 à 20:52, Brian Potkin a écrit :
> severity 987420 minor
> thanks
> 
> 
> On Fri 23 Apr 2021 at 18:30:41 +0200, Yadd wrote:
> 
> Thank you for your report, Yadd.
> 
> What is your printer model?

Hi,

it's a HP Envy 4500. It worked until last testing update (today,
previous ~3 days earlier). Xsane no more find it too

Cheers,
Yadd

Bug#987433: prometheus-smokeping-prober: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Adriano Rafael Gomes]

Package: prometheus-smokeping-prober
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#972570: [Pkg-javascript-devel] Bug#972570: node-lightgallery is built using minified files

[Yadd]

Le 23/04/2021 à 19:03, Jonas Smedegaard a écrit :
> Quoting Yadd (2021-04-23 17:47:23)
>> Control: tags -1 + pending
>>
>> Le 23/04/2021 à 09:44, Daniel Ring a écrit :
>>> Hello Xavier,
>>>
>>> It looks like the build process was minifying the source files to the
>>> destination *.js files and copying the pre-minified files to *.min.js. I
>>> corrected it to copy the unminified files directly and minify them to
>>> *.min.js.
>>>
>>> I also updated the package on Salsa to exclude the minified
>>> modules/*.min.js files via Files-Excluded in d/copyright, so they're no
>>> longer in the source package at all.
>>>
>>> Sincerely,
>>> Daniel Ring
>>
>> Hi,
>>
>> looks good to me, thanks! Could you also ignore these warnings in a
>> debain/lintian-overrides? It looks like false positive
>>
>> Cheers,
>> Yadd
>>
>>  W: node-lightgallery: privacy-breach-generic
>> usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [> class="lg-video-object lg-dailymotion '+o+'" '+l+' width="560"
>> height="315"
> [...]
> Those warnings look real to me.
> 
> What makes you consider them false positives, Xavier?

Hi Jonas,

yes but the relevant lines are in if/then/else blocks:

  if (isVideo.youtube) {
...  video = 

Bug#763192: closed by Salvatore Bonaccorso (Re: Bug#763192: [LXC] [nfsd] kernel crash when running nfs-kernel-server in one LXC Container)

[Jean-Marc LACROIX (jeanmarc.lacr...@free.fr)]

Le 23/04/2021 à 20:27, Debian Bug Tracking System a écrit :

This is an automatic notification regarding your Bug report
which was filed against the src:linux package:

#763192: NFSv4 server recovery not supported in container

It has been closed by Salvatore Bonaccorso .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Salvatore Bonaccorso 
 by
replying to this email.



Hi,

Please find here some good news about this issue. It is now possible to 
run NFS server into one LXC container.


One of my current configuration running for 2 years on Debian Buster
on armhf and amd64 architecture is ...

Step 1: hypervisor configuration (target = hc1-260)

This is one arhf octocore odroid hC1 board :
ansible@hc1-260:~$ uname -a
Linux hc1-260 5.10.0-0.bpo.5-armmp-lpae #1 SMP Debian 5.10.24-1~bpo10+1 
(2021-03-29) armv7l GNU/Linux

ansible@hc1-260:~$ cat /etc/debian_version
10.9
ansible@hc1-260:~$ ansible@hc1-260:~$ cat /proc/interrupts
   CPU0   CPU1   CPU2   CPU3   CPU4   CPU5 
  CPU6   CPU7
 57:  0  0  0  0  0  0 
 0  0  COMBINER 187 Edge  mct_comp_irq
 58:   48423896  0  0  0  0  0 
 0  0 GICv2 152 Level mct_tick0
 59:  0   42386303  0  0  0  0 
 0  0 GICv2 153 Level mct_tick1



Because in my configuration, LXC container can not insmod dedicated nfs 
module, it is then mandatory to instert it into hypervisor.

As a result, this is done into /etc/module file

ansible@hc1-260:~$ sudo cat /etc/modules  |grep -v "#" |grep -v ^$
iptable_filter
autofs4
8021q
tun
nfsv4
nfsd


On hypervisor, lxc container running nfs server is ok

ansible@hc1-260:~$ sudo lxc-ls -f |grep nfs
vm-nfs-260RUNNING 1 grp_lxc_start_on_boot 
192.168.22.136, 192.168.24.136, 192.168.25.136


Here is the configuration of LXC container

ansible@hc1-260:~$ sudo  cat  /etc/lxc/auto/vm-nfs-260 |grep -v '#' 
|grep -v ^$

lxc.arch= armv7l
lxc.uts.name= vm-nfs-260
lxc.start.auto  = 1
lxc.start.order = 80
lxc.start.delay = 0
lxc.group   = grp_lxc_start_on_boot
lxc.init.cmd= /sbin/init
lxc.init.uid= 0
lxc.init.gid= 0
lxc.ephemeral= 0

lxc.console.buffer.size = 102400
lxc.console.size= 102400
lxc.log.level   = DEBUG
lxc.log.file= /var/log/lxc/vm-nfs-260.log
lxc.tty.max = 4
lxc.pty.max = 10
lxc.signal.halt = SIGPWR
lxc.signal.reboot= SIGINT
lxc.signal.stop  = SIGKILL
lxc.cgroup.memory.limit_in_bytes = 313M

lxc.cgroup.cpuset.cpus  = 4
lxc.cgroup.cpu.shares   = 1024
lxc.cgroup.devices.deny = a
lxc.autodev = 1
lxc.cgroup.devices.allow= c 1:3 rwm
lxc.cgroup.devices.allow= c 1:5 rwm
lxc.cgroup.devices.allow= c 1:8 rwm
lxc.cgroup.devices.allow= c 1:9 rwm
lxc.cgroup.devices.allow= c 5:1 rwm
lxc.cgroup.devices.allow= c 5:2 rwm
lxc.cgroup.devices.allow= c 136:0 rwm
lxc.cgroup.devices.allow= c 136:1 rwm
lxc.cgroup.devices.allow= c 136:2 rwm
lxc.cgroup.devices.allow= c 136:3 rwm
lxc.cgroup.devices.allow= c 136:4 rwm
lxc.cgroup.devices.allow= c 136:5 rwm
lxc.cgroup.devices.allow= c 136:6 rwm
lxc.cgroup.devices.allow= c 136:7 rwm
lxc.cgroup.devices.allow= c 136:8 rwm
lxc.cgroup.devices.allow= c 136:9 rwm
lxc.cgroup.devices.allow= c 5:0 rwm
lxc.cgroup.devices.allow= c 4:64 rwm
lxc.cgroup.devices.allow= c 4:65 rwm
lxc.cgroup.devices.allow= c 4:0 rwm
lxc.cgroup.devices.allow= c 4:1 rwm
lxc.cgroup.devices.allow= c 4:2 rwm
lxc.cgroup.devices.allow= c 4:3 rwm
lxc.cgroup.devices.allow= c 4:4 rwm
lxc.cgroup.devices.allow= c 4:5 rwm
lxc.cgroup.devices.allow= c 4:6 rwm
lxc.rootfs.mount= /var/lib/lxc/vm-nfs-260/rootfs
lxc.rootfs.path = 
/dev/mapper/vg_vm_nfs_260-lv_rootfs

lxc.rootfs.options  = 

Bug#987432: glibc Vulnerability in Debian Buster

[Jai Bheemsen Rao Dhanwada]

Package: glibc
Version: 2.28-10

There is a HIGH severity vulnerability that is fixed in the bullseye, sid.
Is there a plan to release a fix for it in the future buster releases?
Ref: https://security-tracker.debian.org/tracker/CVE-2019-25013

# apt-cache policy libc-bin libc6
> libc-bin:
>   Installed: 2.28-10
>   Candidate: 2.28-10
>   Version table:
>  *** 2.28-10 100
> 100 /var/lib/dpkg/status
> libc6:
>   Installed: 2.28-10
>   Candidate: 2.28-10
>   Version table:
>  *** 2.28-10 100
> 100 /var/lib/dpkg/status
> # cat /etc/debian_version
> 10.9

# cat /etc/os-release
> PRETTY_NAME="Debian GNU/Linux 10 (buster)"
> NAME="Debian GNU/Linux"
> VERSION_ID="10"
> VERSION="10 (buster)"
> VERSION_CODENAME=buster
> ID=debian
> HOME_URL="https://www.debian.org/;
> SUPPORT_URL="https://www.debian.org/support;
> BUG_REPORT_URL="https://bugs.debian.org/;

Bug#987431: Graphical session or LightDM do not close until unattended-upgrades has applied all updates

[Yvan Masson]

Package: unattended-upgrades
Version: 2.8
Severity: normal

Dear Maintainer,

I am preparing some Debian 11 desktops (for when it will be the new 
stable). The setup is very simple: no root account, one partition, tasks 
desktop/Cinnamon/standard tools/SSH. Unattended-upgrades is configured 
to install updates on shutdown (see 1): upgrading works properly, but is 
very disturbing for the users:


When the user chooses to shutdown or reboot the computer from his 
Cinnamon session, the session does not close until all updates are 
applied. While waiting:

- icons on the desktop disappear
- the usual menu that allows choosing between 
suspend/hibernate/reboot/cancel/shutdown won't appear again (see 2)

- it is still possible to start applications

When a user session has been opened, then closed, and the user clicks on 
shutdown or reboot from LightDM, the behavior is similar: LightDM does 
not stop. It is even possible to log in again, while unattended-upgrades 
is applying updates, but when updates are applied the computer 
shutdowns/reboots as requested originally from LightDM.


I would expect the session to be completely closed, LightDM stopped, and 
the console or Plymouth displaying a message indicating the ongoing 
updates. I am almost sure this has already worked for me in a previous 
Debian version or Ubuntu, with the same setup from me.


Please let me know if you need more information or if you want me to do 
some tests.


Regards,
Yvan


1. Here are the files I create to configure unattended-upgrades:
$ cat /etc/apt/apt.conf.d/21periodic
  APT::Periodic::Unattended-Upgrade "1";
  APT::Periodic::CleanInterval "1";

$ cat /etc/apt/apt.conf.d/51unattended-upgrades-local
Unattended-Upgrade::Origins-Pattern {
  "origin=Debian,codename=bullseye,label=Debian";
  "origin=Debian,codename=bullseye,label=Debian-Security";
  "origin=Debian,codename=bullseye-updates,label=Debian";
};
Unattended-Upgrade::InstallOnShutdown "true";

$ cat /etc/systemd/logind.conf.d/unattended-upgrades.conf
[Login]
# 30 minutes delay
InhibitDelayMaxSec=1800


2. This matches the following error in ~/.xsession-errors:
Cjs-message: 09:26:35.004: JS LOG: Ignored exception from dbus method: 
GIO.IOErrorEnum: GDBus:Error:org.gnome.SessionManager.NotInRunning: 
Shutdown interface is only available during the Running phase



-- 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-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
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 unattended-upgrades depends on:
ii  debconf [debconf-2.0]  1.5.75
ii  lsb-base   11.1.0
ii  lsb-release11.1.0
ii  python33.9.2-2
ii  python3-apt2.1.7
ii  python3-dbus   1.2.16-5
ii  python3-distro-info1.0
ii  ucf3.0043
ii  xz-utils   5.2.5-2

Versions of packages unattended-upgrades recommends:
ii  anacron 2.3-30
ii  cron [cron-daemon]  3.0pl1-137
ii  systemd-sysv247.3-3

Versions of packages unattended-upgrades suggests:
pn  bsd-mailx  
ii  exim4-daemon-light [mail-transport-agent]  4.94-17
ii  needrestart3.5-2
ii  powermgmt-base 1.36
ii  python3-gi 3.38.0-2

-- debconf information excluded



OpenPGP_signature
Description: OpenPGP digital signature

Bug#987032: Info received (Bug#987032: cqrlog: Importing ADIF-logs results in 0 byte logs)

[Federico Grau]

Received sample ADIF file with 61 entries from bug submitter.
Confirmed patched cqrlog imports ADIF OK, with same results as xlog.

donfede


signature.asc
Description: PGP signature

Bug#987430: upgrade-reports: KDE Plasma without panels and without background after upgrade from Buster to Bullseye

[Malvin Gattinger]

Package: upgrade-reports
Severity: important

My previous release is: buster (fully updated)
I am upgrading to: bullseye
Archive date: Fri Apr 23 14:17:55 UTC 2021
Upgrade date: Fri Apr 23 16:00:00 UTC 2021
uname -a before upgrade: Linux hostname 4.19.0-16-amd64 #1 SMP 
Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
uname -a after upgrade: Linux hostname 5.10.0-6-amd64 #1 SMP 
Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux

Method: apt upgrade --without-new-pkgs && apt full-upgrade

I have now upgraded three different machines from (fully updated) 
Buster to Bullseye, and all three times KDE Plasma was not usable 
afterwards.


Symptoms:
- No panels are shown and instead of the desktop/background the 
 screen is black.
- Right-click on the desktop works, but the settings do not allow 
 me to set a background image.
- Pressing the super key opens the launcher menu, next to where 
 the panel should be shown.

- Alt+Tab works, kwin is running normally
- krunner was unusable on two of the machines, but worked on the 
 third.


I think the same problems was described by a reddit user here:
https://www.reddit.com/r/debian/comments/li4vvc/debian_bullseye_has_entered_softfreeze/gnbp9up/?context=3

WORKAROUND:
The problem goes away after reinstalling everything that is 
installed and has "plasma" in the name, but unfortunately I cannot 
say which of those package reinstalls is actually doing the trick:


sudo apt install --reinstall kdeplasma-addons-data 
libkf5plasma5:amd64 libkf5plasmaquick5:amd64 
libplasma-geolocation-interface5 libreoffice-plasma 
plasma-dataengines-addons:amd64 plasma-desktop plasma-desktop-data 
plasma-disks plasma-framework plasma-integration plasma-nm 
plasma-pa plasma-runners-addons:amd64 
plasma-wallpapers-addons:amd64 plasma-widgets-addons 
plasma-workspace plasma-workspace-data



After this and logging out and back in, all of KDE Plasma works as 
normal.

Bug#710938: Packard Bell EasyNote LV need i915.invert_brightness on Linux

[Salvatore Bonaccorso]

Hi,

On Fri, Apr 23, 2021 at 07:28:49PM +0200, Petter Reinholdtsen wrote:
> 
> Version: 5.4.6-1
> 
> [Salvatore Bonaccorso]
> > Thanks for reporting this back. Gut feeling, we should simly close
> > this (old) bugreport by now.
> 
> Yeah, lets close it.  Picked a fairly random version after when I
> believe it was working.

Thanks for confirming.

Regards,
Salvatore

Bug#986492: closed by Salvatore Bonaccorso (Re: Bug#986492: Python Vulnerability in Debian 10 Buster)

[Jai Bheemsen Rao Dhanwada]

Thanks for the update, as per
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983531#25 I see the fix
is available in 10.10. Do we have any rough estimated timelines on the
release date for 10.10?

On Fri, Apr 23, 2021 at 9:30 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the python package:
>
> #986492: Python Vulnerability in Debian 10 Buster
>
> It has been closed by Salvatore Bonaccorso .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Salvatore Bonaccorso <
> car...@debian.org> by
> replying to this email.
>
>
> --
> 986492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986492
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Salvatore Bonaccorso 
> To: Jai Bheemsen Rao Dhanwada ,
> 986492-d...@bugs.debian.org, j...@debian.org
> Cc:
> Bcc:
> Date: Fri, 23 Apr 2021 18:27:26 +0200
> Subject: Re: Bug#986492: Python Vulnerability in Debian 10 Buster
> Hi,
>
> On Tue, Apr 06, 2021 at 03:35:22PM -0700, Jai Bheemsen Rao Dhanwada wrote:
> > Package: Python
> > Version: 2.7.16
> >
> > CVE-2021-3177 is reported on Python which has a fix available in 2.7.18
> > version in bullseye, sid. Can this be addressed in the buster version, so
> > the people like me dependent on Python2.x can make use of the
> Python-2.17.18
> > Ref: https://security-tracker.debian.org/tracker/CVE-2021-3177
> >
> > The latest version of buster only has 2.7.16 and no
>
> Please see https://bugs.debian.org/983531
>
> Regards,
> Salvatore
>
>
> -- Forwarded message --
> From: Jai Bheemsen Rao Dhanwada 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 6 Apr 2021 15:35:22 -0700
> Subject: Python Vulnerability in Debian 10 Buster
> Package: Python
> Version: 2.7.16
>
> CVE-2021-3177 is reported on Python which has a fix available in 2.7.18
> version in bullseye, sid. Can this be addressed in the buster version, so
> the people like me dependent on Python2.x can make use of the Python-2.17.18
> Ref: https://security-tracker.debian.org/tracker/CVE-2021-3177
>
> The latest version of buster only has 2.7.16 and no
>
> # python -V
>> Python 2.7.16
>> # cat /etc/*release*
>> PRETTY_NAME="Debian GNU/Linux 10 (buster)"
>> NAME="Debian GNU/Linux"
>> VERSION_ID="10"
>> VERSION="10 (buster)"
>> VERSION_CODENAME=buster
>> ID=debian
>> HOME_URL="https://www.debian.org/;
>> SUPPORT_URL="https://www.debian.org/support;
>> BUG_REPORT_URL="https://bugs.debian.org/;
>
>
> # apt-cache policy python
>> python:
>>   Installed: 2.7.16-1
>>   Candidate: 2.7.16-1
>>   Version table:
>>  *** 2.7.16-1 500
>> 500 http://deb.debian.org/debian buster/main amd64 Packages
>> 100 /var/lib/dpkg/status
>> #
>
>

Bug#987429: unblock: fdroidcl/0.5.0-3

[Jochen Sprickerhof]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package fdroidcl

[ Reason ]
The F-Droid metadata json format changed slightly moving the App name to
the localized part. The update adds a upstream accepted patch to prefer
that over the general field in case that is empty. It is basically a
copy and paste of what is already done for the summary and description
fields in the lines below the patch.

[ Impact ]
The name of an app is not shown:
$ fdroidcl show org.fdroid.fdroid | grep "^Name"
Name :

[ Tests ]
I tested the change manually.

[ Risks ]
Code change is trivial and popcon is low.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

unblock fdroidcl/0.5.0-3
diff --git a/debian/changelog b/debian/changelog
index a061ba6..d52170b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+fdroidcl (0.5.0-3) unstable; urgency=medium
+
+  * Add patch in case the app name is empty
+
+ -- Jochen Sprickerhof   Fri, 23 Apr 2021 18:42:52 +0200
+
 fdroidcl (0.5.0-2) unstable; urgency=medium
 
   * bump policy and debhelper versions
diff --git 
a/debian/patches/0002-Use-English-app-name-if-the-other-is-empty.patch 
b/debian/patches/0002-Use-English-app-name-if-the-other-is-empty.patch
new file mode 100644
index 000..2dc860a
--- /dev/null
+++ b/debian/patches/0002-Use-English-app-name-if-the-other-is-empty.patch
@@ -0,0 +1,30 @@
+From: Jochen Sprickerhof 
+Date: Fri, 23 Apr 2021 18:34:00 +0200
+Subject: Use English app name if the other is empty
+
+---
+ fdroid/index.go | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/fdroid/index.go b/fdroid/index.go
+index 1716c19..119ea7e 100644
+--- a/fdroid/index.go
 b/fdroid/index.go
+@@ -59,6 +59,7 @@ type App struct {
+ }
+ 
+ type Localization struct {
++  Namestring `json:"name"`
+   Summary string `json:"summary"`
+   Description string `json:"description"`
+ }
+@@ -274,6 +275,9 @@ func LoadIndexJSON(r io.Reader) (*Index, error) {
+   english, enOK = app.Localized["en-US"]
+   }
+ 
++  if app.Name == "" && enOK {
++  app.Name = english.Name
++  }
+   // TODO: why does the json index contain html escapes?
+   app.Name = html.UnescapeString(app.Name)
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 0890fce..08f194a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 0001-Drop-main_test.go.patch
+0002-Use-English-app-name-if-the-other-is-empty.patch

Bug#987420: hplip seems incompatible with current cups

[Brian Potkin]

severity 987420 minor
thanks


On Fri 23 Apr 2021 at 18:30:41 +0200, Yadd wrote:

Thank you for your report, Yadd.

What is your printer model?

-- 
Brian.

Bug#987095: Low-hanging fruits reminder for 2021-04-21, 19:00 UTC (tomorrow)

[gregor herrmann]

On Thu, 22 Apr 2021 21:15:14 +0200, Étienne Mollier wrote:

> > - Do the problems happen with the libgraph-perl version in stable and
> >   testing/unstable as well?
> Yes, problems do happen with unmodified libgraph-perl from
> stable, testing and sid.  That is why I think they are most
> likely unrelated to the security fix you cherry picked.

Thanks!

I guess that's the crucial point (for the question of uploading
libgraph-perl with the changes in git).

And good to see that your analysis matches my gut feeling, that the
libchado-perl problems are not related to libgraph-perl.

So I'll go ahead and upload libgraph-perl.
 
> > - What did you do to run which tests? (I stared at the package bit
> >   but it's not really obvious to me).
> I mostly stuck to running the entire autopkgtest, with bells and
> whistles:

Ok, I see; that's what I tried as well.
 
> that is why I am not too sure how much of a blocker it would be
> for the libgraph-perl upgrade.  Maybe it will be recognized as
> "Not a regression".

Well, as libchado-perl in the archive has no autopkgtests there won't
be any autopkgtest run after the libgraph-perl upload, so there can't
be any automatically detected regression :)
 
> > - Which tests fail how? (I only see ./t/01_okay.t which triest to
> >   load Bio::Chado::LoadDBI which doesn't exist anywhere in Debian ?!)
> By order of appearance in an autodep8 run against the Testing
> distribution, i.e. without the patched libgraph-perl:

Ok, that matches my quick tests.
 
> > - Does this package actually use modules from libgraph-perl?
> >   (Grepping show some Bio::Graphics stuff but libbio-graphics-perl
> >   doesn't depend on libgraph-perl.)  
> It does not appear so on grepping libgraph-perl source code, or
> binary packages content, on my end neither.  

Which is also a good point from an
avoid-regressions-by-uploading-libgraph-perl point of view.

> > - Do you have any output or any other details?
> I added an sbuild with autopkgtest output of the libchado-perl
> against sid in attachment, without dependency to libgraph-perl.
> The output is a bit trimmed down for readability, and reduce the
> weight on mailboxes.

Thanks again.
 
> As far as I can see, although it is a Perl package, it looks
> like provided elements are mostly supposed to be used like a
> regular application.  Maybe all these issues are just not caught
> in regular package usage?

Maybe … My conclusion is that libchado-perl might have some issuses
but that they are neiter caused by libgraph-perl in general and
especially not by the proposed patch in libgraph-perl.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Beatles


signature.asc
Description: Digital Signature

Bug#987428: libwebkit2gtk-4.0-37: only recommned xdg-desktop-portal-gtk

[Alberto Garcia]

On Fri, Apr 23, 2021 at 08:25:32PM +0200, Philippe Cerfon wrote:

> Would it be possible to only recommend xdg-desktop-portal-gtk
> instead of depending on it?
> 
> It seems to be only required for stuff like Flatpak and Snap running
> inside a bupplewrap pseudo-sandbox.

Hi, this has nothing to do with Flatpak or Snap.

WebKit does uses bubblewrap to isolate its processes for security
reasons, and one consequence of that is that xdg-desktop-portal-gtk is
needed for proper font rendering.

This affects Evolution as well, it was actually with Evolution that the
problems was originally identified, see here:

https://bugzilla.redhat.com/show_bug.cgi?id=1845743

> Also it leads to further unnecessary deps, like PipeWire

If this brings a lot of additional dependencies then I can turn it
into a recommendation, I didn't have that impression when I added the
dependency but I can reconsider.

Berto

Bug#987335: ITP: dpa-ext-gnomekeyring -- GNOME keyring extension for dde-polkit-agent

[Tomas Pospisek]

On 22.04.21 04:04, clay stan wrote:

Package: wnpp
Severity: wishlist
Owner: clay stan 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: dpa-ext-gnomekeyring
   Version : 5.0.4
   Upstream Author : linuxdeepin
* URL : https://github.com/linuxdeepin/dpa-ext-gnomekeyring
   License : GPL-3+


Same here, oh please add a description, such as (I'm guessing here): 
This extension makes it possible to access the GNOME keyring from Deepin 
applications.

Bug#987371: unblock: at-spi2-core/2.38.0-4

[Samuel Thibault]

Ah, formally speaking this would also need an ack for the d-i side.

Samuel

Samuel Thibault, le jeu. 22 avril 2021 18:33:05 +0200, a ecrit:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hello,
> 
> Please unblock package at-spi2-core
> 
> [ Reason ]
> The following bug report:
> https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/35
> explains that when using accerciser (the tool to investigate the
> accessibility of application), if one closes the application being
> investigated, accerciser crashes immediately. This is due to a missing
> unlink in the underlying at-spi2-core library, fixed by the proposed
> changes.
> 
> [ Impact ]
> People working on accessibility usually want to repeat
> stopping/restarting the application they hack on, and to avoid
> accerciser crashing they would have to remember to always switch
> accerciser toward another application before stopping/restarting their
> application. Or else have to restart accerciser each time. There is no
> real data loss here, but it's very inconvenient
> 
> [ Tests ]
> I could test by hand the behavior getting fixed, as well as the bug
> reporter. There is no automatic test covering that part of the code
> unfortunately, that is why it went mostly unnoticed so far.
> 
> [ Risks ]
> The code change is a one-liner, made by upstream.
> 
> [ Checklist ]
>   [X] all changes are documented in the d/changelog
>   [X] I reviewed all changes and I approve them
>   [X] attach debdiff against the package in testing
> 
> Thanks!
> 
> unblock at-spi2-core/2.38.0-4

> diff -Nru at-spi2-core-2.38.0/debian/changelog 
> at-spi2-core-2.38.0/debian/changelog
> --- at-spi2-core-2.38.0/debian/changelog  2020-09-12 23:07:32.0 
> +0200
> +++ at-spi2-core-2.38.0/debian/changelog  2021-04-22 13:10:24.0 
> +0200
> @@ -1,3 +1,16 @@
> +at-spi2-core (2.38.0-4) unstable; urgency=medium
> +
> +  * Re-upload to get arch:all built on buildd.
> +
> + -- Samuel Thibault   Thu, 22 Apr 2021 13:10:24 +0200
> +
> +at-spi2-core (2.38.0-3) unstable; urgency=medium
> +
> +  * patches/double-free: Fix double free. Fixes crash of accerciser when
> +closing an application.
> +
> + -- Samuel Thibault   Wed, 21 Apr 2021 23:44:28 +0200
> +
>  at-spi2-core (2.38.0-2) unstable; urgency=medium
>  
>* Upload to unstable.
> diff -Nru at-spi2-core-2.38.0/debian/patches/double-free 
> at-spi2-core-2.38.0/debian/patches/double-free
> --- at-spi2-core-2.38.0/debian/patches/double-free1970-01-01 
> 01:00:00.0 +0100
> +++ at-spi2-core-2.38.0/debian/patches/double-free2021-04-22 
> 00:09:27.0 +0200
> @@ -0,0 +1,24 @@
> +commit 0b551954386543e97370d97ea1b78dd096edb14e
> +Author: Mike Gorse 
> +Date:   Wed Apr 21 16:37:14 2021 -0500
> +
> +Fix double free when removing event listeners
> +
> +Fixes https://gitlab.gnome.org/GNOME/at-spi2-core/issues/35
> +
> +diff --git a/atspi/atspi-event-listener.c b/atspi/atspi-event-listener.c
> +index ca6828f..5455b58 100644
> +--- a/atspi/atspi-event-listener.c
>  b/atspi/atspi-event-listener.c
> +@@ -798,7 +798,10 @@ atspi_event_listener_deregister_from_callback 
> (AtspiEventListenerCB callback,
> +   DBusMessage *message, *reply;
> +   l = g_list_next (l);
> +   if (in_send)
> +-  pending_removals = g_list_append (pending_removals, e);
> ++  {
> ++pending_removals = g_list_remove (pending_removals, e);
> ++pending_removals = g_list_append (pending_removals, e);
> ++  }
> +   else
> + event_listeners = g_list_remove (event_listeners, e);
> +   for (i = 0; i < matchrule_array->len; i++)
> diff -Nru at-spi2-core-2.38.0/debian/patches/series 
> at-spi2-core-2.38.0/debian/patches/series
> --- at-spi2-core-2.38.0/debian/patches/series 2020-09-12 23:07:32.0 
> +0200
> +++ at-spi2-core-2.38.0/debian/patches/series 2021-04-22 00:09:27.0 
> +0200
> @@ -2,3 +2,4 @@
>  disable-test-that-needs-installed-dbus-service.patch
>  test_disable_teamspaces
>  tests
> +double-free

> ___
> Pkg-a11y-devel mailing list
> pkg-a11y-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-a11y-devel

Bug#987428: libwebkit2gtk-4.0-37: only recommned xdg-desktop-portal-gtk

[Philippe Cerfon]

Package: libwebkit2gtk-4.0-37
Version: 2.30.6-1
Severity: wishlist


Hey.

Would it be possible to only recommend xdg-desktop-portal-gtk
instead of depending on it?

It seems to be only required for stuff like Flatpak and Snap
running inside a bupplewrap pseudo-sandbox.
So everyone else not using these probably don't need it?

Also it leads to further unnecessary deps, like PipeWire
(why does one need this, when one e.g. just wants to use
Evolution or anything else, which depends on libwebkit2gtk-4.0-37?)


Thanks for considering,
Philippe

Bug#987172: acl2: run-acl2 in emacs fails

[Camm Maguire]

Greetings, and thanks for your report!  Will get to it, but likely not
before the version currently waiting in new propagates into testing,
after release.

Take care,

florine forine  writes:

> Package: acl2
> Version: 8.3dfsg-2
> Severity: normal
>
> Dear Maintainer,
>
> M-x run-acl2 in emacs fails probably because
> /usr/share/emacs/site-lisp/acl2/mfm.el
> uses an obsolete function string-to-int.
> See 
> https://stackoverflow.com/questions/52726142/emacs-26-symbol-s-function-definition-is-void-string-to-int.
>
> emacs configuration in ~/.emacs:
>
> (setq *acl2-sources-dir* "/usr/share/acl2-8.3dfsg/")
> (setq *acl2-interface-dir* "/usr/share/emacs/site-lisp/acl2/")
> (setq inferior-acl2-program "/usr/bin/acl2")
>
> -- System Information:
> Debian Release: bullseye/sid
> Architecture: amd64 (x86_64)
>
> Versions of packages acl2 depends on:
> ii  libc6 2.31-11
> ii  libgmp10  2:6.2.1+dfsg-1
> ii  libreadline8  8.1-1
> ii  libx11-6  2:1.7.0-2
>
> Versions of packages acl2 recommends:
> ii  acl2-books   8.3dfsg-2
> ii  acl2-source  8.3dfsg-2
>
> Versions of packages acl2 suggests:
> ii  acl2-emacs  8.3dfsg-2
>
> -- no debconf information

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#987159: broadcom-sta-dkms: error(-1) from calls to @wl_dev_intvar_get; @wl_cfg80211_get_tx_power by networkctl

[Philip Stewart]

On Fri, 23 Apr, 2021 at 23:51, Roger Shimizu  
wrote:


I think backports would be more simple, and fast to upload.
Does that work for you?


Works for me, thanks Roger!

Bug#987224: claws-mail: Hangs on attempt to view certain emails

[Ricardo Mones]

control: tags -1 moreinfo

Hi Paul,

On Mon, 19 Apr 2021 22:25:43 +0100
"Paul \"LeoNerd\" Evans"  wrote:

> Package: claws-mail
> Version: 3.17.8-1+b1
> Severity: normal
> 
> A few emails I receive will cause claws-mail to hang in a CPU spin when
> attempting to preview it (by selecting it in the message list for
> preview in the third pane). This CPU spin consumes 100% of one core,
> with nothing visible to strace. The program does not respond to regular
> SIGINT/TERM and requires SIGKILL to quit it.
> 
> These cases are entirely repeatable, and all occur on github issue
> notifications from one particular author. Most notifications from that
> author do not hang, and work as expected. But occasionally one
> notification will cause a hang, and I have noticed the coincidence that
> it is always the same author.
> 
> I shall attach a file directly from my Maildir containing such a case.

Since is not specified I've tried to view your message without plugins, with
litehtml plugin and with dillo plugin. Didn't find any problem viewing the
message in the three cases, so I guess is something particular on your
configuration or machine. To narrow a bit the problem, which other plugins
have you loaded? Does removing any of them (try one at a time) improve the
situation?

Also, since it's reproducible in your machine, and before experimenting with
the plugin list, can you run claws-mail with --debug flag in a terminal and
see if something interesting is printed?

thanks in advance!
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Alas, I am dying beyond my means. -- Oscar Wilde [as he sipped 
 champagne on his deathbed]»


pgp8RkN_zn_Ht.pgp
Description: Firma digital OpenPGP

Bug#987427: unblock: nvidia-graphics-drivers-tesla-460/460.73.01-1

[Luca Boccassi]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-nvidia-de...@lists.alioth.debian.org

Please unblock package nvidia-graphics-drivers-tesla-460

The new upstream version 460.73.01 fixes a CVE and a several bugs,
all of which affect Bullseye. It also adds support for a few new cards.

X.org crash under certain conditions, and a security vulnerability
(CVE-2021-1076 and CVE-2021-1077, and #987222) has been found in the kernel 
driver:
https://nvidia.custhelp.com/app/answers/detail/a_id/5172

The inlined debdiff excludes the binary blobs.

unblock nvidia-graphics-drivers-tesla-460/460.73.01-1

-- 
Kind regards,
Luca Boccassi

diff -Nru --exclude 'NVIDIA*.run' 
nvidia-graphics-drivers-tesla-460-460.32.03/debian/changelog 
nvidia-graphics-drivers-tesla-460-460.73.01/debian/changelog
--- nvidia-graphics-drivers-tesla-460-460.32.03/debian/changelog
2021-03-13 20:31:33.0 +
+++ nvidia-graphics-drivers-tesla-460-460.73.01/debian/changelog
2021-04-23 14:20:03.0 +0100
@@ -1,3 +1,87 @@
+nvidia-graphics-drivers-tesla-460 (460.73.01-1) unstable; urgency=medium
+
+  * New upstream production branch release 460.73.01 (2021-04-14).
+* Fixed CVE-2021-1076, CVE-2021-1077.  (Closes: #987222)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5172
+- Added support for the following GPUs: A10, A10G, A30, PG506-232,
+  RTX A4000, RTX A5000, T400, T600.
+
+  [ Andreas Beckmann ]
+  * Update nv-readme.ids.
+
+ -- Andreas Beckmann   Fri, 23 Apr 2021 15:20:03 +0200
+
+nvidia-graphics-drivers (460.73.01-1) unstable; urgency=medium
+
+  * New upstream production branch release 460.73.01 (2021-04-14).
+* Fixed CVE-2021-1076, CVE-2021-1077.  (Closes: #987216)
+  https://nvidia.custhelp.com/app/answers/detail/a_id/5172
+- Added support for the following GPUs: A10, A10G, A30, PG506-232,
+  RTX A4000, RTX A5000, T400, T600.
+
+  [ Andreas Beckmann ]
+  * Update nv-readme.ids.
+  * Restrict watch file to releases from the 460.xx production branch.
+
+ -- Andreas Beckmann   Fri, 23 Apr 2021 08:59:01 +0200
+
+nvidia-graphics-drivers (460.67-1) unstable; urgency=medium
+
+  * New upstream production branch release 460.67 (2021-03-18).
+- Fixed a bug where using ray tracing extensions on multi-GPU setups could
+  result in application instability if the GPUs did not match.
+- Fixed an issue that prevented G-SYNC from working properly after a mode
+  switch on Kepler-based GPUs.
+
+  [ Luca Boccassi ]
+  * Update nv-readme.ids.
+
+ -- Andreas Beckmann   Sun, 21 Mar 2021 20:51:46 +0100
+
+nvidia-graphics-drivers (460.56-2) unstable; urgency=medium
+
+  * nvidia-alternative: Add libnvidia-ml.so slave alternative if
+libnvidia-ml-dev is installed.  (Closes: #984881)
+
+ -- Andreas Beckmann   Wed, 10 Mar 2021 21:03:59 +0100
+
+nvidia-graphics-drivers (460.56-1) unstable; urgency=medium
+
+  * New upstream production branch release 460.56 (2021-02-25).
+- Added support for the following GPUs: GeForce RTX 3060, CMP 40HX,
+  CMP 30HX.
+- Fixed a bug with indexed ray payloads in Vulkan.
+
+  [ Luca Boccassi ]
+  * Update nv-readme.ids.
+
+  [ Andreas Beckmann ]
+  * Switch to dh-sequence-dkms.
+  * Simplify dh_dkms usage.
+
+ -- Andreas Beckmann   Sun, 28 Feb 2021 00:26:36 +0100
+
+nvidia-graphics-drivers (460.39-1) unstable; urgency=medium
+
+  * New upstream production branch release 460.39 (2021-01-26).
+- Updated the NVIDIA driver to restore functionality of some features,
+  including runtime power management, hotplugging audio-capable display
+  devices, and S0ix-based system suspend, with recent kernels such as
+  Linux 5.10.  (Closes: #981187)
+- Fixed a bug that caused bindless texture samplers to be incorrectly
+  counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS limit.
+- Fixed a bug that could cause the GPU to hang when attempting to
+  perform link training on an HDMI 2.1 Fixed Rate Link (FRL) display,
+  while the display is powered off.
+- Added support for the following GPUs: GeForce RTX 3080 Laptop GPU,
+  GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU,
+  GeForce GT 1010.
+
+  [ Andreas Beckmann ]
+  * Update nv-readme.ids.
+
+ -- Andreas Beckmann   Thu, 28 Jan 2021 01:33:29 +0100
+
 nvidia-graphics-drivers-tesla-460 (460.32.03-3) unstable; urgency=medium
 
   * Switch to dh-sequence-dkms (460.56-1).
@@ -152,10 +236,6 @@
   xf86-video-intel driver.
 - Fixed a bug in a Vulkan barrier optimization that allowed some
   back-to-back copies to run unordered.
-  * New upstream release 450 series.
-- Fixed a performance regression in the NVIDIA X driver which affected
-  some X11 RENDER extension use cases.
-- Added AMD Secure Memory Encryption compatibility.
 
   [ Andreas Beckmann ]
   * Update nv-readme.ids.
@@ -168,11 +248,6 @@
 - Fixed a bug that caused X to crash when the 

Bug#986436: node-tldjs: modifies shipped files: /usr/lib/nodejs/tldjs/rules.json

[Adrian Bunk]

On Tue, Apr 06, 2021 at 12:04:40AM +0200, Andreas Beckmann wrote:
> Package: node-tldjs
> Version: 2.3.1-1.1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package modifies conffiles.
> 
> debsums reports modification of the following files,
> from the attached log (scroll to the bottom...):
> 
> 0m48.9s ERROR: FAIL: debsums reports modifications inside the chroot:
>   /usr/lib/nodejs/tldjs/rules.json
>...

https://sources.debian.org/src/tldjs/2.3.1-1/debian/postinst/#L7

> This only seems to happen if --install-recommends is enabled.

Upgrade (including reinstall) triggers it, reproducer:
  apt-get install node-tldjs
  apt-get --reinstall install node-tldjs

> cheers,
> 
> Andreas



cu
Adrian

Bug#987336: ITP: dtkcommon -- dtk common files

[Tomas Pospisek]

On 22.04.21 05:21, clay stan wrote:

Package: wnpp
Severity: wishlist
Owner: clay stan 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: dtkcommon
   Version : 5.5.2
   Upstream Author : linuxdeepin
* URL : https://github.com/linuxdeepin/dtkcommon
   License : GPL-3+


Please add a description what this package is good for/contains and/or 
respectively what "dtk" is.


Thanks & Greetings,
*t

Bug#987425: popularity-contest: Please update Croatian translation

[Valentin Vidic]

Package: popularity-contest
Severity: wishlist

Dear Maintainer,

Please update the Croatian translation in the package using the
patch attached below.

Thank you,
Valentin
From 05023c51e4d2b9d6e727fa3477732ec0c23d3d9e Mon Sep 17 00:00:00 2001
From: Valentin Vidic 
Date: Fri, 23 Apr 2021 18:20:31 +0200
Subject: [PATCH] Croatian translation update

---
 debian/po/hr.po | 22 +++---
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/debian/po/hr.po b/debian/po/hr.po
index 566d675..c703981 100644
--- a/debian/po/hr.po
+++ b/debian/po/hr.po
@@ -4,18 +4,18 @@ msgstr ""
 "Project-Id-Version: Debian-installer HR\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2006-07-29 12:23+0200\n"
-"PO-Revision-Date: 2006-09-27 12:50+0200\n"
-"Last-Translator: Josip Rodin \n"
+"PO-Revision-Date: 2021-04-23 18:20+0200\n"
+"Last-Translator: Valentin Vidic \n"
 "Language-Team: Croatian \n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=iso-8859-2\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Type: boolean
 #. Description
 #: ../templates:4
 msgid "Participate in the package usage survey?"
-msgstr "Sudjelovati u anketi kori¹tenja paketa?"
+msgstr "Sudjelovati u anketi korištenja paketa?"
 
 #. Type: boolean
 #. Description
@@ -26,9 +26,9 @@ msgid ""
 "influences decisions such as which packages should go on the first "
 "distribution CD."
 msgstr ""
-"Va¹ sustav mo¾e anonimno slati e-po¹tu razvijateljima distribucije sa "
-"statistikama o paketima koje najvi¹e koristite. Ti podaci utjeèu na odluke "
-"kao ¹to je izbor paketa koji æe biti stavljeni na prvi CD."
+"Sustav može autorima distribucije anonimno slati statistiku o paketima "
+"koji se najviše koriste na ovom računalu. Ti podaci utječu na odluke "
+"kao što je izbor paketa koji će se nalaziti na prvom CD-u distribucije."
 
 #. Type: boolean
 #. Description
@@ -38,9 +38,9 @@ msgid ""
 "every week, sending statistics to the distribution developers. The collected "
 "statistics can be viewed on https://popcon.debian.org/.;
 msgstr ""
-"Ako odluèite sudjelovati, automatska skripta æe se pokretati svaki tjedan "
-"i slati statistike razvijateljima distribucije. Sabrane statistike se mogu "
-"vidjeti na https://popcon.debian.org/.;
+"Ako odlučite sudjelovati, automatska skripta će jednom tjedno slati "
+"statistike autorima distribucije. Sabrane statistike mogu se vidjeti na "
+"https://popcon.debian.org/.;
 
 #. Type: boolean
 #. Description
@@ -49,5 +49,5 @@ msgid ""
 "This choice can be later modified by running \"dpkg-reconfigure popularity-"
 "contest\"."
 msgstr ""
-"Uvijek se mo¾ete predomisliti i promijeniti svoj izbor pokretanjem: "
+"Uvijek se možete predomisliti i promijeniti svoj izbor pokretanjem naredbe: "
 "\"dpkg-reconfigure popularity-contest\"."
-- 
2.20.1

Bug#710938: Packard Bell EasyNote LV need i915.invert_brightness on Linux

[Salvatore Bonaccorso]

Hi,

On Sun, Dec 27, 2020 at 08:46:53AM +0100, Petter Reinholdtsen wrote:
> For the record, I reinstalled the machine in question with Ubuntu
> 18.04 a few days ago, and upgraded it since to 20.04, and the
> problem was not present there.
> 
> This make me suspect this issue is fixed in kernel 5.4.0
> and possible earlier versions.
> 
> I am unable to test with a Debian kernel. :(

Thanks for reporting this back. Gut feeling, we should simly close
this (old) bugreport by now.

Regards,
Salvatore

Bug#987424: mgetty-viewfax has mailcap entries with quoted %-escapes

[Marriott NZ]

Package: mgetty-viewfax
Version: 1.2.1-1.1
Tags: security

Dear Maintainer,
the mgetty-viewfax package has mailcap entries with quoted %-escapes. That is 
considered unsafe. Proper escaping should be left to the programs using the 
entry.

This Lintian tag is triggered:
https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html

See also grave bug #930908, which was recently closed because "a Lintian test 
already exists":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908

I'm using the "security" tag because the affected rules in combination with 
certain mail user agents (or document openers) are the cause of a shell command 
injection vulnerability.

/usr/lib/mime/packages/mgetty-viewfax should be changed from:

 image/fax; viewfax '%s'; test=test -n "$DISPLAY"; description="Fax file"
 image/fax-g3; viewfax '%s'; test=test -n "$DISPLAY"; description="G3-encoded 
Fax file"
 image/fax-g4; viewfax '%s'; test=test -n "$DISPLAY"; description="G4-encoded 
Fax file"

to:

 image/fax; viewfax %s; test=test -n "$DISPLAY"; description="Fax file"
 image/fax-g3; viewfax %s; test=test -n "$DISPLAY"; description="G3-encoded Fax 
file"
 image/fax-g4; viewfax %s; test=test -n "$DISPLAY"; description="G4-encoded Fax 
file"

If you need more information let me know.

Thanks,
MNZ

Bug#987423: ITP: chaos-marmosets -- Small chaos monkey programs

[Benjamin Drung]

Package: wnpp
Severity: wishlist
Owner: Benjamin Drung 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: chaos-marmosets
  Version : 0.1
  Upstream Author : Benjamin Drung 
* URL : https://github.com/bdrung/chaos-marmosets
* License : ISC
  Programming Lang: C
  Description : Small chaos monkey programs

 This project contains small programs that behave badly. They can be used for
 chaos engineering to test the system behavior and the infrastructure setup for
 those cases.
 .
 divide-by-zero tries to divide a number by zero. It will immediately exit with
 signal 4 (SIGILL). This program is useful to test the process core dump
 configuration. In case of using a bug reporting system like apport, this
 program allows testing reporting the crash and retracing it.
 .
 leak-memory: This program will eat your memory like Obelix eats cake until it
 will eventually trigger the out of memory (OOM) killer. This program is useful
 to test configured cgroups memory limitations and the OOM killer behavior.
 .
 seg-fault: This program tries write to address zero and will trigger a
 segmentation fault (signal 11). It is useful to test the process core dump
 configuration. In case of using a bug reporting system like apport, this
 program allows testing reporting the crash and retracing it.

I wrote those programs to test our apport and retrace setup as well as the
dump-core script (see Debian bug #857300).

-- 
Benjamin Drung
Senior DevOps Engineer and Debian & Ubuntu Developer

Bug#987422: caca-utils has mailcap entries with quoted %-escapes

[Marriott NZ]

Package: caca-utils
Version: 0.99.beta19-2.2
Tags: patch, security

Dear Maintainer,
the caca-utils package has mailcap entries with quoted %-escapes. That is 
considered unsafe. Proper escaping should be left to the programs using the 
entry.

This Lintian tag is triggered:
https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html

See also grave bug #930908, which was recently closed because "a Lintian test 
already exists":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908

I'm using the "security" tag because the affected rules in combination with 
certain mail user agents (or document openers) are the cause of a shell command 
injection vulnerability.

If you need more information let me know.

Thanks,
MNZ
diff -ru a/debian/caca-utils.mime b/debian/caca-utils.mime
--- a/debian/caca-utils.mime	2021-03-10 14:59:27.0 +0100
+++ b/debian/caca-utils.mime	2021-04-23 18:46:35.794788587 +0200
@@ -1,45 +1,45 @@
-image/gif; /usr/bin/cacaview '%s'; description=GIF Image; nametemplate=%s.gif; test=test -n "$DISPLAY"; priority=1
-image/gif; unset DISPLAY\; /usr/bin/cacaview '%s'; description=GIF Image; nametemplate=%s.gif; needsterminal; priority=1
+image/gif; /usr/bin/cacaview %s; description=GIF Image; nametemplate=%s.gif; test=test -n "$DISPLAY"; priority=1
+image/gif; unset DISPLAY\; /usr/bin/cacaview %s; description=GIF Image; nametemplate=%s.gif; needsterminal; priority=1

-image/jpeg; /usr/bin/cacaview '%s'; description=JPEG Image; nametemplate=%s.jpg; test=test -n "$DISPLAY"; priority=1
-image/jpeg; unset DISPLAY\; /usr/bin/cacaview '%s'; description=JPEG Image; nametemplate=%s.jpg; needsterminal; priority=1
+image/jpeg; /usr/bin/cacaview %s; description=JPEG Image; nametemplate=%s.jpg; test=test -n "$DISPLAY"; priority=1
+image/jpeg; unset DISPLAY\; /usr/bin/cacaview %s; description=JPEG Image; nametemplate=%s.jpg; needsterminal; priority=1

-image/png; /usr/bin/cacaview '%s'; description=PNG Image; nametemplate=%s.png; test=test -n "$DISPLAY"; priority=1
-image/png; unset DISPLAY\; /usr/bin/cacaview '%s'; description=PNG Image; nametemplate=%s.png; needsterminal; priority=1
+image/png; /usr/bin/cacaview %s; description=PNG Image; nametemplate=%s.png; test=test -n "$DISPLAY"; priority=1
+image/png; unset DISPLAY\; /usr/bin/cacaview %s; description=PNG Image; nametemplate=%s.png; needsterminal; priority=1

-image/tiff; /usr/bin/cacaview '%s'; description=TIFF Image; nametemplate=%s.tiff; test=test -n "$DISPLAY"; priority=1
-image/tiff; unset DISPLAY\; /usr/bin/cacaview '%s'; description=TIFF Image; nametemplate=%s.tiff; needsterminal; priority=1
+image/tiff; /usr/bin/cacaview %s; description=TIFF Image; nametemplate=%s.tiff; test=test -n "$DISPLAY"; priority=1
+image/tiff; unset DISPLAY\; /usr/bin/cacaview %s; description=TIFF Image; nametemplate=%s.tiff; needsterminal; priority=1

-image/bmp; /usr/bin/cacaview '%s'; description=BMP Image; nametemplate=%s.bmp; test=test -n "$DISPLAY"; priority=1
-image/bmp; unset DISPLAY\; /usr/bin/cacaview '%s'; description=BMP Image; nametemplate=%s.bmp; needsterminal; priority=1
+image/bmp; /usr/bin/cacaview %s; description=BMP Image; nametemplate=%s.bmp; test=test -n "$DISPLAY"; priority=1
+image/bmp; unset DISPLAY\; /usr/bin/cacaview %s; description=BMP Image; nametemplate=%s.bmp; needsterminal; priority=1

-image/x-ms-bmp; /usr/bin/cacaview '%s'; description=BMP Image; nametemplate=%s.bmp; test=test -n "$DISPLAY"; priority=1
-image/x-ms-bmp; unset DISPLAY\; /usr/bin/cacaview '%s'; description=BMP Image; nametemplate=%s.bmp; needsterminal; priority=1
+image/x-ms-bmp; /usr/bin/cacaview %s; description=BMP Image; nametemplate=%s.bmp; test=test -n "$DISPLAY"; priority=1
+image/x-ms-bmp; unset DISPLAY\; /usr/bin/cacaview %s; description=BMP Image; nametemplate=%s.bmp; needsterminal; priority=1

-image/x-cmu-raster; /usr/bin/cacaview '%s'; description=CMU-RasterFile Image; nametemplate=%s.ras; test=test -n "$DISPLAY"; priority=1
-image/x-cmu-raster; unset DISPLAY\; /usr/bin/cacaview '%s'; description=CMU-RasterFile Image; nametemplate=%s.ras; needsterminal; priority=1
+image/x-cmu-raster; /usr/bin/cacaview %s; description=CMU-RasterFile Image; nametemplate=%s.ras; test=test -n "$DISPLAY"; priority=1
+image/x-cmu-raster; unset DISPLAY\; /usr/bin/cacaview %s; description=CMU-RasterFile Image; nametemplate=%s.ras; needsterminal; priority=1

-image/g3fax; /usr/bin/cacaview '%s'; description=G3-FAX Image; nametemplate=%s.g3; test=test -n "$DISPLAY"; priority=1
-image/g3fax; unset DISPLAY\; /usr/bin/cacaview '%s'; description=G3-FAX Image; nametemplate=%s.g3; needsterminal; priority=1
+image/g3fax; /usr/bin/cacaview %s; description=G3-FAX Image; nametemplate=%s.g3; test=test -n "$DISPLAY"; priority=1
+image/g3fax; unset DISPLAY\; /usr/bin/cacaview %s; description=G3-FAX Image; nametemplate=%s.g3; needsterminal; priority=1

-image/targa; /usr/bin/cacaview '%s'; description=TARGA Image; nametemplate=%s.tga; test=test -n "$DISPLAY"; priority=1

Bug#987421: alsaplayer-{daemon,gtk,text,xosd} has mailcap entries with quoted %-escapes

[Marriott NZ]

Package: alsaplayer-daemon
Version: 0.99.81-2
Tags: patch, security

Dear Maintainer,
the alsaplayer-interface packages have mailcap entries with quoted %-escapes. 
That is considered unsafe. Proper escaping should be left to the programs using 
the entry.

This Lintian tag is triggered:
https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html

See also grave bug #930908, which was recently closed because "a Lintian test 
already exists":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908

I'm using the "security" tag because the affected rules in combination with 
certain mail user agents (or document openers) are the cause of a shell command 
injection vulnerability.

If you need more information let me know.

Thanks,
MNZ
diff -ru a/debian/alsaplayer-daemon.mime b/debian/alsaplayer-daemon.mime
--- a/debian/alsaplayer-daemon.mime	2016-08-27 19:52:55.0 +0200
+++ b/debian/alsaplayer-daemon.mime	2021-04-23 18:40:58.587325996 +0200
@@ -1,9 +1,9 @@
-audio/mpeg; alsaplayer -i daemon '%s'; nametemplate=%s.mp3; priority=6
-audio/mpegurl; alsaplayer -i daemon '%s'; nametemplate=%s.m3u; priority=6
-audio/x-scpls; alsaplayer -i daemon '%s'; nametemplate=%s.pls; priority=6
-audio/x-wav; alsaplayer -i daemon '%s'; nametemplate=%s.wav; priority=6
-application/x-ogg; alsaplayer -i daemon '%s'; nametemplate=%s.ogg; priority=6
-application/ogg; alsaplayer -i daemon '%s'; nametemplate=%s.ogg; priority=6
-audio/flac; alsaplayer -i daemon '%s'; nametemplate=%s.flac; priority=6
-audio/x-flac; alsaplayer -i daemon '%s'; nametemplate=%s.flac; priority=6
-application/x-flac; alsaplayer -i daemon '%s'; nametemplate=%s.flac; priority=6
+audio/mpeg; alsaplayer -i daemon %s; nametemplate=%s.mp3; priority=6
+audio/mpegurl; alsaplayer -i daemon %s; nametemplate=%s.m3u; priority=6
+audio/x-scpls; alsaplayer -i daemon %s; nametemplate=%s.pls; priority=6
+audio/x-wav; alsaplayer -i daemon %s; nametemplate=%s.wav; priority=6
+application/x-ogg; alsaplayer -i daemon %s; nametemplate=%s.ogg; priority=6
+application/ogg; alsaplayer -i daemon %s; nametemplate=%s.ogg; priority=6
+audio/flac; alsaplayer -i daemon %s; nametemplate=%s.flac; priority=6
+audio/x-flac; alsaplayer -i daemon %s; nametemplate=%s.flac; priority=6
+application/x-flac; alsaplayer -i daemon %s; nametemplate=%s.flac; priority=6
diff -ru a/debian/alsaplayer-gtk.mime b/debian/alsaplayer-gtk.mime
--- a/debian/alsaplayer-gtk.mime	2016-08-27 19:52:55.0 +0200
+++ b/debian/alsaplayer-gtk.mime	2021-04-23 18:42:32.267734684 +0200
@@ -1,9 +1,9 @@
-audio/mpeg; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.mp3; priority=7
-audio/mpegurl; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.m3u; priority=7
-audio/x-scpls; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.pls; priority=7
-audio/x-wav; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.wav; priority=7
-application/x-ogg; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.ogg; priority=7
-application/ogg; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.ogg; priority=7
-audio/flac; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.flac; priority=7
-audio/x-flac; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.flac; priority=7
-application/x-flac; alsaplayer -i gtk2 '%s'; test=test "$DISPLAY" != ""; nametemplate=%s.flac; priority=7
+audio/mpeg; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.mp3; priority=7
+audio/mpegurl; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.m3u; priority=7
+audio/x-scpls; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.pls; priority=7
+audio/x-wav; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.wav; priority=7
+application/x-ogg; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.ogg; priority=7
+application/ogg; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.ogg; priority=7
+audio/flac; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.flac; priority=7
+audio/x-flac; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.flac; priority=7
+application/x-flac; alsaplayer -i gtk2 %s; test=test "$DISPLAY" != ""; nametemplate=%s.flac; priority=7
diff -ru a/debian/alsaplayer-text.mime b/debian/alsaplayer-text.mime
--- a/debian/alsaplayer-text.mime	2016-08-27 19:52:55.0 +0200
+++ b/debian/alsaplayer-text.mime	2021-04-23 18:44:07.275361286 +0200
@@ -1,9 +1,9 @@
-audio/mpeg; alsaplayer -i text '%s'; nametemplate=%s.mp3; priority=6
-audio/mpegurl; alsaplayer -i text '%s'; nametemplate=%s.m3u; priority=6
-audio/x-scpls; alsaplayer -i text '%s'; nametemplate=%s.pls; priority=6
-audio/x-wav; alsaplayer -i text '%s'; nametemplate=%s.wav; priority=6
-application/x-ogg; alsaplayer -i text '%s'; nametemplate=%s.ogg; priority=6
-application/ogg; alsaplayer -i text '%s'; 

Bug#637908: [bluetooth] Bluetooth crashes kernel when connecting device

[Salvatore Bonaccorso]

Hi,

On Tue, Aug 16, 2011 at 01:01:40AM +0800, Paolo Scarabelli wrote:
> Package: bluetooth
> Version: 4.94-3
> Severity: grave
> 
> --- Please enter the report below this line. ---
> 
> When I try to connect to my mobile phone using bluetooth the kernel
> suddenly crashes.
> 
> There is nothing in the logs, I attach an image of the screen after the
> crash.

Assuming the issue is not anymore reproducible on recent kernels I'm 
going to close this bugreport by now to clean up the list of src:linux
bugs from very old issues. In case you can reproduce the issue feel
free to reopen the bug.
 
Regards,
Salvatore

Bug#972570: [Pkg-javascript-devel] Bug#972570: node-lightgallery is built using minified files

[Jonas Smedegaard]

Quoting Yadd (2021-04-23 17:47:23)
> Control: tags -1 + pending
> 
> Le 23/04/2021 à 09:44, Daniel Ring a écrit :
> > Hello Xavier,
> > 
> > It looks like the build process was minifying the source files to the
> > destination *.js files and copying the pre-minified files to *.min.js. I
> > corrected it to copy the unminified files directly and minify them to
> > *.min.js.
> > 
> > I also updated the package on Salsa to exclude the minified
> > modules/*.min.js files via Files-Excluded in d/copyright, so they're no
> > longer in the source package at all.
> > 
> > Sincerely,
> > Daniel Ring
> 
> Hi,
> 
> looks good to me, thanks! Could you also ignore these warnings in a
> debain/lintian-overrides? It looks like false positive
> 
> Cheers,
> Yadd
> 
>  W: node-lightgallery: privacy-breach-generic
> usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [ class="lg-video-object lg-dailymotion '+o+'" '+l+' width="560"
> height="315"
> src="//www.dailymotion.com/embed/video/'+t.dailymotion[1]+d+'"
> frameborder="0" allowfullscreen>]
> (//www.dailymotion.com/embed/video/'+t.dailymotion[1]+d+')
> W: node-lightgallery: privacy-breach-generic
> usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [ class="lg-video-object lg-vimeo '+o+'" '+l+' width="560" height="315"
> src="//player.vimeo.com/video/'+t.vimeo[1]+d+'" frameborder="0"
> webkitallowfullscreen mozallowfullscreen allowfullscreen>]
> (//player.vimeo.com/video/'+t.vimeo[1]+d+')
> W: node-lightgallery: privacy-breach-generic
> usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [ class="lg-video-object lg-vk '+o+'" '+l+' width="560" height="315"
> src="//vk.com/video_ext.php?'+t.vk[1]+d+'" frameborder="0"
> allowfullscreen>] (//vk.com/video_ext.php?'+t.vk[1]+d+')
> W: node-lightgallery: privacy-breach-generic
> usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [ class="lg-video-object lg-youtube '+o+'" '+l+' width="560" height="315"
> src="//www.youtube.com/embed/'+t.youtube[1]+d+'" frameborder="0"
> allowfullscreen>] (//www.youtube.com/embed/'+t.youtube[1]+d+')

Those warnings look real to me.

What makes you consider them false positives, Xavier?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#987405: most has mailcap entries with quoted %-escapes

[Benj. Mako Hill]

Thanks for this (and for the patch)! I'll take a look at it right
away. It looks quite straightforward.

Regards,
Mako


-- 
Benjamin Mako Hill
https://mako.cc/


signature.asc
Description: PGP signature

Bug#986515: siconos: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test "ARGS=-E 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest'" ARGS\+=-j1 returned exit code 2

[Stephen Sinclair]

I was unable to reproduce this issue.  The build was successful for me
locally and on Debian Salsa server. The salsa build log can be found
here:
https://salsa.debian.org/science-team/siconos/-/jobs/1562650/raw

My local build log is attached from running dpkg-buildpackage.

regards,
Stephen Sinclair

On Wed, Apr 7, 2021 at 9:01 AM Lucas Nussbaum  wrote:
>
> Source: siconos
> Version: 4.3.1+dfsg-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210406 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in bullseye, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> > Running tests...
> > /usr/bin/ctest --force-new-ctest-process -E 
> > 'COLLECTION|collection|python_test_lcp|dr_iso1|ContactTest' -j1
> > Test project /<>/obj-x86_64-linux-gnu
> >   Start  1: DLSODES-test
> >  1/95 Test  #1: DLSODES-test    Passed
> > 0.01 sec
> >   Start  2: DLSODAR-test
> >  2/95 Test  #2: DLSODAR-test    Passed
> > 0.01 sec
> >   Start  3: DLSODI-test
> >  3/95 Test  #3: DLSODI-test .   Passed
> > 0.02 sec
> >   Start  4: DLSODPK-test
> >  4/95 Test  #4: DLSODPK-test    Passed
> > 0.12 sec
> >   Start  5: DLSODA-test
> >  5/95 Test  #5: DLSODA-test .   Passed
> > 0.01 sec
> >   Start  6: DLSODE-test
> >  6/95 Test  #6: DLSODE-test .   Passed
> > 0.01 sec
> >   Start  7: DLSODIS-test
> >  7/95 Test  #7: DLSODIS-test    Passed
> > 0.01 sec
> >   Start  8: DLSODKR-test
> >  8/95 Test  #8: DLSODKR-test    Passed
> > 0.03 sec
> >   Start  9: DLSOIBT-test
> >  9/95 Test  #9: DLSOIBT-test    Passed
> > 0.04 sec
> >   Start 10: odepacktest10
> > 10/95 Test #10: odepacktest10 ...   Passed
> > 0.00 sec
> >   Start 11: dr1_radau5
> > 11/95 Test #11: dr1_radau5 ..   Passed
> > 0.01 sec
> >   Start 12: dr2_radau5
> > 12/95 Test #12: dr2_radau5 ..   Passed
> > 0.01 sec
> >   Start 13: dr_radau
> > 13/95 Test #13: dr_radau    Passed
> > 0.00 sec
> >   Start 14: dr_radaup
> > 14/95 Test #14: dr_radaup ...   Passed
> > 0.01 sec
> >   Start 15: dr_rodas
> > 15/95 Test #15: dr_rodas    Passed
> > 0.00 sec
> >   Start 16: dr_seulex
> > 16/95 Test #16: dr_seulex ...   Passed
> > 0.00 sec
> >   Start 17: test_op3x3
> > 17/95 Test #17: test_op3x3 ..   Passed
> > 0.26 sec
> >   Start 18: test_timers_interf
> > 18/95 Test #18: test_timers_interf ..   Passed
> > 0.01 sec
> >   Start 19: test_blas_lapack
> > 19/95 Test #19: test_blas_lapack    Passed
> > 0.01 sec
> >   Start 20: test_pinv
> > 20/95 Test #20: test_pinv ...   Passed
> > 0.02 sec
> >   Start 21: tools_projection
> > 21/95 Test #21: tools_projection    Passed
> > 0.01 sec
> >   Start 22: NumericsArrays
> > 22/95 Test #22: NumericsArrays ..   Passed
> > 0.01 sec
> >   Start 23: NM_test
> > 23/95 Test #23: NM_test .   Passed
> > 0.17 sec
> >   Start 24: tools_test_JordanAlgebra
> > 24/95 Test #24: tools_test_JordanAlgebra    Passed
> > 0.01 sec
> >   Start 25: NM_MUMPS_test
> > 25/95 Test #25: NM_MUMPS_test ...   Passed
> > 0.01 sec
> >   Start 26: SBM_test
> > 26/95 Test #26: SBM_test    Passed
> > 0.02 sec
> >   Start 27: SBCM_to_SBM
> > 27/95 Test #27: SBCM_to_SBM .   Passed
> > 0.01 sec
> >   Start 28: SparseMatrix_test
> > 28/95 Test #28: SparseMatrix_test ...   Passed
> > 0.02 sec
> >   Start 29: lcp_test_DefaultSolverOptions
> > 29/95 Test #29: lcp_test_DefaultSolverOptions ...   Passed
> > 0.01 sec
> >   Start 30: MixedLinearComplementarity_ReadWrite_test
> > 30/95 Test #30: MixedLinearComplementarity_ReadWrite_test ...   Passed
> > 0.01 sec
> >   Start 31: MCP_test
> > 31/95 Test #31: MCP_test    Passed
> > 0.01 sec
> >   Start 32: MCP_test1
> > 32/95 Test #32: MCP_test1 ...   Passed
> > 0.01 sec
> >   Start 33: MCP_test2
> > 33/95 Test #33: MCP_test2 

Bug#941071: linux-image-4.19.0-6-amd64: dmesg report error:acpi MSFT0101:00: platform device creation failed: -16

[Salvatore Bonaccorso]

Hi,

On Fri, Apr 23, 2021 at 10:34:15PM +0800, xiao sheng wen(肖盛文） wrote:
> Hi,
> 
>     It don't reproducible in 10.9 kernel:
> 
> uname -a
> Linux atzlinux 4.19.0-16-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.181-1
> (2021-03-19) x86_64 GNU/Linux
> 
> 
> Let's close this bug.

Thanks for reporting back!

Regards,
Salvatore

Bug#973987: Please mention fcitx5 is available in bullseye

[Justin B Rye]

Justin B Rye wrote:
>   
> New Fcitx 5 Input method
   ^
Oh, except that should be "Input Method".
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

Bug#987420: hplip seems incompatible with current cups

[Yadd]

Package: hplip
Version: 3.21.2+dfsg1-2
Severity: grave
Justification: renders package unusable

hplip is broken as reported by hp-check (see below). This renders
package unusable.

Cheers,
Yadd

-- Package-specific info:
Saving output in log file: /home/xavier/dev/lemonldap/ui/manager/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

warning: debian-testing version is not supported. Using debian-10.7 versions 
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) GNU/Linux
 Host: deb007
 Proc: 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) GNU/Linux
 Distribution: debian testing
 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  testing 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:
[installation]
date_time = 04/23/21 18:27:40
version = 3.21.2


 


-
| External Dependencies |
-

 error: cups  CUPS - Common Unix Printing System
   REQUIRED 

Bug#973987: Please mention fcitx5 is available in bullseye

[Justin B Rye]

Shengjing Zhu wrote:
> ===
> 2.2.x New Fcitx 5 Input method
> 
> Fcitx 5 is an input method for Chinese, Japanese, Korean and many
> other languages.  It is the successor of the popular Fcitx 4 in
> Buster. The new version supports Wayland and has better addon support.
> More information including the migration guide can be found [on the
> wiki](https://wiki.debian.org/I18n/Fcitx5).
> ===

Looks good to me.  I'd put it either just before or just after the two
systemd-related items ("cgroupv2" and "persistent-journal"):

  
New Fcitx 5 Input method

 Fcitx 5 is an input method for Chinese, Japanese, Korean and many
 other languages. It is the successor of the popular Fcitx 4 in
 buster. The new version supports Wayland and has better addon
 support. More information including the migration guide can be
 found https://wiki.debian.org/I18n/Fcitx5;>on the
 wiki.

  

("Fcitx 5" could be "fcitx5",
but if so we'd need to be careful to say "fcitx 4" since there isn't a fcitx4
package.  There isn't a binary package "wayland", either!)
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

Bug#987245: apache2: After=network.target should be After=network-online.target

[Chris Hofstaedtler]

Hi,

* Ryutaroh Matsumoto  [210423 16:24]:
[..]
> apache httpd needs those IP addresses being already configured
> when it starts, otherwise the httpd fails to start.
> This ordering dependency is captured by
> After=network-online.target
> Wants=network-online.target

Changing this will help only on the simplest installations under
"best weather" conditions. It would be better to find another
solution (e.g. IP_FREEBIND).

Chris

Bug#986811: python3-adios: leaves alternatives after upgrade from buster: /usr/lib/python3/dist-packages/adios_mpi/adios_mpi.cpython-37m-x86_64-linux-gnu.so -> /etc/alternatives/python-py37-adios-x86_

[Andreas Beckmann]

Followup-For: Bug #986811
Control: tag -1 patch

Hi,

please see the attached patch for cleaning up the obsolete alternative
on upgrades.

Andreas
diff -Nru adios-1.13.1/debian/changelog adios-1.13.1/debian/changelog
--- adios-1.13.1/debian/changelog   2021-03-06 17:35:45.0 +0100
+++ adios-1.13.1/debian/changelog   2021-04-23 15:16:48.0 +0200
@@ -1,3 +1,9 @@
+adios (1.13.1-29) UNRELEASED; urgency=medium
+
+  * Clean up obsolete alternatives on upgrade.  (Closes: #986811)
+
+ -- Andreas Beckmann   Fri, 23 Apr 2021 15:16:48 +0200
+
 adios (1.13.1-28) unstable; urgency=medium
 
   * postinst/prerm: Ensure generated tags correct.
diff -Nru adios-1.13.1/debian/python3-adios.preinst.in 
adios-1.13.1/debian/python3-adios.preinst.in
--- adios-1.13.1/debian/python3-adios.preinst.in1970-01-01 
01:00:00.0 +0100
+++ adios-1.13.1/debian/python3-adios.preinst.in2021-04-23 
15:16:44.0 +0200
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt-nl "1.13.1-29~" ; 
then
+   update-alternatives --remove-all python-py37-adios-@DEB_HOST_MULTIARCH@
+fi
+
+#DEBHELPER#
diff -Nru adios-1.13.1/debian/rules adios-1.13.1/debian/rules
--- adios-1.13.1/debian/rules   2021-03-06 17:35:45.0 +0100
+++ adios-1.13.1/debian/rules   2021-04-23 15:16:48.0 +0200
@@ -9,7 +9,7 @@
 AUTOGENERATED:=   adios_config control libadios-bin.postinst  \
  libadios-mpich-dev.postinst libadios-openmpi-dev.postinst \
  libadios-mpich-dev.prerm libadios-openmpi-dev.prerm \
- python3-adios.postinst python3-adios.prerm
+ python3-adios.preinst python3-adios.postinst 
python3-adios.prerm
 
 MPI_LIBS_OPENMPI:= $(pkg-config ompi-fort --libs)
 MPI_LIBS_MPICH:= $(pkg-config mpich-fort --libs)

Bug#987419: schroot: Incorrect mount/unmount binfmt handler sequence for start/stop schroot stages

[Max A. Dednev]

Package: schroot
Version: 1.6.10-6+b1
Severity: important

Dear Maintainer,

I'm using schroot for building packages with sbuild using qemu-arm-static
binfmt handler in chroot environment.

/etc/setup.d/15binfmt handler script incorrectly tries to perform bind mount
while schroot session is stopping. This leads to the mount error and terminates
schroot session end. So such sessions couldn't be ended. So, 15binfmt script
should take into account current $STAGE value to properly handle requested
operation. My modified script shows example of such handling process:

for emulator in $(update-binfmts --find "$shell"); do
dst="${CHROOT_PATH}$emulator"
if [ ! -e "$emulator" ]; then
info "Missing emulator: $emulator; not enabling binfmt support"
else
if [ "$STAGE" == "setup-start" ] || \
   [ "$STAGE" == "setup-recover" ]; then
[ -e "$dst" ] || { mkdir -p "$(dirname "$dst")"; touch "$dst"; }
mount --bind "$emulator" "$dst"
mount -o remount,ro,bind "$dst"
elif [ "$STAGE" == "setup-stop"  ]; then
umount "$dst"
fi
fi
done

It includes modifications, backported from schroot version 1.6.10-12, line:
...
[ -e "$dst" ] || { mkdir -p "$(dirname "$dst")"; touch "$dst"; }
...



-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 5.10.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages schroot depends on:
ii  libboost-filesystem1.67.0   1.67.0-13+deb10u1
ii  libboost-iostreams1.67.01.67.0-13+deb10u1
ii  libboost-program-options1.67.0  1.67.0-13+deb10u1
ii  libboost-system1.67.0   1.67.0-13+deb10u1
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libpam0g1.3.1-5
ii  libstdc++6  8.3.0-6
ii  libuuid12.33.1-0.1
ii  lsb-base10.2019051400
ii  schroot-common  1.6.10-6

schroot recommends no packages.

Versions of packages schroot suggests:
pn  aufs-tools | unionfs-fuse  
ii  btrfs-progs [btrfs-tools]  4.20.1-2
ii  debootstrap1.0.114
ii  lvm2   2.03.02-3
ii  qemu-user-static   1:3.1+dfsg-8+deb10u8

-- Configuration Files:
/etc/schroot/setup.d/15binfmt changed:
set -e
. "$SETUP_DATA_DIR/common-data"
. "$SETUP_DATA_DIR/common-functions"
. "$SETUP_DATA_DIR/common-config"
if [ "$STAGE" != "setup-start" ] && \
   [ "$STAGE" != "setup-stop"  ] && \
   [ "$STAGE" != "setup-recover" ]; then
exit 0
elif ! which update-binfmts > /dev/null 2>&1; then
info "Missing update-binfmts; not enabling binfmt support"
exit 0
fi
shell="${CHROOT_PATH}/bin/sh"
for emulator in $(update-binfmts --find "$shell"); do
dst="${CHROOT_PATH}$emulator"
if [ ! -e "$emulator" ]; then
info "Missing emulator: $emulator; not enabling binfmt support"
else
if [ "$STAGE" == "setup-start" ] || \
   [ "$STAGE" == "setup-recover" ]; then
[ -e "$dst" ] || { mkdir -p "$(dirname "$dst")"; touch "$dst"; }
mount --bind "$emulator" "$dst"
mount -o remount,ro,bind "$dst"
elif [ "$STAGE" == "setup-stop"  ]; then
umount "$dst"
fi
fi
done


-- no debconf information

Bug#985416: Bug#985634: git (1:2.31.0-1): no longer runs addons from /usr/lib/git-core breaking lots of 3rdpty stuff

[Chris Hofstaedtler]

* Thorsten Glaser  [210423 16:00]:
> Chris Hofstaedtler dixit:
> 
> >installation path. I imagine going back is now hopeless, so either
> >git searches both paths, or all other packages are just rc-buggy.
> 
> I wasn’t considering just packages; unpackaged (or third-party-
> packaged) extensions will also be affected. Both paths is a good
> plan.

#985416 apparently reverted the libexec path change.

It did break git-flow (#986565) again though.

Chris

-- 
|  Segmentation fault (core dumped)
:-)

Bug#973987: Please mention fcitx5 is available in bullseye

[Shengjing Zhu]

Hi,

On Fri, Apr 23, 2021 at 2:42 AM Paul Gevers  wrote:
>
> Hi Shengjing,
>
> On 22-04-2021 16:59, Shengjing Zhu wrote:
> > On Thu, Apr 22, 2021 at 10:49 PM Paul Gevers  wrote:
> >> Can you propose a text?
> >
> > In the Package table in 2.2.1, adding one row.
> >
> > ===
> > Package | Version in 10 (buster)  | Version in 11 (bullseye)
> > Fcitx input method  | 4.2.9.6 (package name is fcitx)  | 5.0.5
> > (package name is fcitx5)
> > ===
> >
> > Does this work for you?
>
> I'm surprised. Sure, we can do that, but is this all? Before this bug
> report I had never heard of fcitx, but also I am Dutch, so ASCII is
> mostly fine for me. Do you think that this line conveys the information
> you want to deliver to the users that would be interested? In other
> words, do you think that every user requiring "input methods" will
> understand that this is a major thing?
>
> I was expecting some text describing what fcitx does and what the delta
> is between fcitx and fcitx5 and how users in some cases may need to
> actively do something if they want the "best" features when upgrading.
> But maybe I was misunderstanding your intent.
>

Please see the updated text

===
2.2.x New Fcitx 5 Input method

Fcitx 5 is an input method for Chinese, Japanese, Korean and many
other languages.  It is the successor of the popular Fcitx 4 in
Buster. The new version supports Wayland and has better addon support.
More information including the migration guide can be found [on the
wiki](https://wiki.debian.org/I18n/Fcitx5).
===

--
Shengjing Zhu

Bug#985617: glibc: flaky autopkgtest on most architectures

[Paul Gevers]

Hi Aurelien,

On 23-04-2021 14:49, Aurelien Jarno wrote:
> Nope, unfortunately it seems the mail didn't reach me or the mailing
> list, maybe it was too big?

It did reach the BTS. I guess size may have been a factor yes, the log
can be picked up in the BTS.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#987360: swaylock: Occassional unlock without password entered

[Chris Hofstaedtler]

* Pelle  [210423 15:45]:
> [..], but then freeze for about half a minute
> and then just disappear and thereby allow access to Sway without the password
> being entered.

Sounds like it crashes?

Please install swaylock-dbgsym and see if you can get a coredump.

Chris

Bug#972570: node-lightgallery is built using minified files

[Yadd]

Control: tags -1 + pending

Le 23/04/2021 à 09:44, Daniel Ring a écrit :
> Hello Xavier,
> 
> It looks like the build process was minifying the source files to the
> destination *.js files and copying the pre-minified files to *.min.js. I
> corrected it to copy the unminified files directly and minify them to
> *.min.js.
> 
> I also updated the package on Salsa to exclude the minified
> modules/*.min.js files via Files-Excluded in d/copyright, so they're no
> longer in the source package at all.
> 
> Sincerely,
> Daniel Ring

Hi,

looks good to me, thanks! Could you also ignore these warnings in a
debain/lintian-overrides? It looks like false positive

Cheers,
Yadd

 W: node-lightgallery: privacy-breach-generic
usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js []
(//www.dailymotion.com/embed/video/'+t.dailymotion[1]+d+')
W: node-lightgallery: privacy-breach-generic
usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js []
(//player.vimeo.com/video/'+t.vimeo[1]+d+')
W: node-lightgallery: privacy-breach-generic
usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [] (//vk.com/video_ext.php?'+t.vk[1]+d+')
W: node-lightgallery: privacy-breach-generic
usr/share/nodejs/lightgallery/dist/js/lg-video.min.min.js [] (//www.youtube.com/embed/'+t.youtube[1]+d+')

Bug#986564: Crash on pool-evolution

[Chris Hofstaedtler]

* Bernhard Übelacker  [210423 15:39]:
> https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/312

To save people some clicking, upstream also referenced:
  https://bugzilla.redhat.com/show_bug.cgi?id=1914917

And patch for 3.38:
  https://gitlab.gnome.org/GNOME/evolution-data-server/commit/1f1017492

Bug#987418: wims-lti: [INTL:de] updated German debconf translation

[Helge Kreutzmann]

Package: wims-lti
Version: 0.4.4.1-1
Severity: wishlist
Tags: patch l10n

Please find the updated German debconf translation for wims-lti
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 wims-lti package.
# Helge Kreutzmann , 2020, 2021.
#
msgid ""
msgstr ""
"Project-Id-Version: wims-lti 4.4.1-1\n"
"Report-Msgid-Bugs-To: wims-...@packages.debian.org\n"
"POT-Creation-Date: 2021-04-19 14:44+0200\n"
"PO-Revision-Date: 2021-04-23 17:09+0200\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: string
#. Description
#: ../templates:1001
msgid "hostname for the service:"
msgstr "Rechnername für den Dienst:"

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"When you use Apache2 + WSGI to deploy the service, it can be implemented as "
"a virtual host. In the example below, the service administration's webpage "
"should be at http://wims-lti.example.com/admin/;
msgstr ""
"Wenn Sie Apache2 und WSGI zur Bereitstellung des Dienstes verwenden, kann "
"dieser als virtueller Rechner implementiert werden. Im nachfolgenden "
"Beispiel sollte die Webseite zur Administration des Dienstes unter http://;
"wims-lti.example.com/admin/ liegen."

#. Type: string
#. Description
#: ../templates:1001
msgid "If unsure, you can keep the default value."
msgstr "Falls Sie sich unsicher sind, können Sie den Vorgabewert beibehalten."

#. Type: string
#. Description
#: ../templates:2001
msgid "email for django's service admin:"
msgstr "E-Mail-Adresse des Administrators des Dienstes django:"

#. Type: string
#. Description
#: ../templates:2001
msgid "Choose a valid email string."
msgstr "Bitte geben Sie eine gültige E-Mail-Adresse an."

#. Type: password
#. Description
#: ../templates:3001
msgid "password for django's service admin:"
msgstr "Passwort des Administrators des Dienstes django:"

#. Type: password
#. Description
#: ../templates:3001
msgid "Choose a strong enough password."
msgstr "Wählen Sie ein hinreichend starkes Passwort."

#. Type: string
#. Description
#: ../templates:4001
msgid "how long to wait for a response from WIMS adm/raw module:"
msgstr "Wie lange auf eine Antwort von einem WIMS-Adm/Raw-Modul gewartet werden 
soll:"

#. Type: string
#. Description
#: ../templates:4001
msgid ""
"Choose an integer value (in seconds). The default value is generally fine. "
"When a server has many active classes, this time should be increased."
msgstr ""
"Wählen Sie einen Ganzzahlwert (in Sekunden). Die Vorgabe ist im Allgemeinen "
"brauchbar. Falls ein Server über viele aktive Klassen verfügt, sollte diese "
"Zeit erhöht werden."

Bug#985956: #985956 - missing kernel module in installer

[Chris Hofstaedtler]

Control: reassign -1 src:linux
Control: retitle -1 Missing kernel module in install for Raspberry Pi 4

Ben already said in this bug report that src:linux also needs to be
fixed for this to work.

Bug#987417: ITP: libcoap3 -- C-Implementation of CoAP, API version 3

[Carsten Schoenert]

Package: wnpp
Severity: wishlist
Owner: Carsten Schoenert 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: libcoap3
  Version : 4.3.0~rc2
  Upstream Author : Olaf Bergmann 
* URL : https://libcoap.net
* License : BSD-2-clause
  Programming Lang: C
  Description : C-Implementation of CoAP, API version 3

Lightweight application-protocol for devices that are constrained their
resources such as computing power, RF range, memory, bandwidth, or
network packet sizes. This protocol, CoAP, is developed in the IETF
working group "CoRE",  and was standardized in RFC
7252.

The libcoap library has been evolved and has now reached the API version
3 which includes changes that makes the library not backward compatible.
To keep the packages from libcoap3 co-installable to the current
upstream version of libcoap will go into a new source package.

The packaging will be done within the IoT packaging group as a team
managed package.

Regards
Carsten

Bug#987038: buster-pu: package clamav/0.103.2+dfsg-0+deb10u1

[Adam D. Barratt]

On Fri, 2021-04-23 at 14:12 +0200, Sebastian Andrzej Siewior wrote:
> On 2021-04-23 08:21:44 [+0100], Adam D. Barratt wrote:
> > Ah, apologies for not spotting that from your earlier mail. An
> > updated
> > draft:
> 
> This is perfect Adam, thank you.

Great, thanks for confirming.

That's now released as SUA 199-1, with the small change from the draft
that I realised that buster actually has 0.102._4_ right now (0.102.3
was previously in buster-updates).

Regards,

Adam

Bug#941071: linux-image-4.19.0-6-amd64: dmesg report error:acpi MSFT0101:00: platform device creation failed: -16

[肖盛文）]

Hi,

    It don't reproducible in 10.9 kernel:

uname -a
Linux atzlinux 4.19.0-16-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.181-1
(2021-03-19) x86_64 GNU/Linux


Let's close this bug.


Thanks!

在 2021/4/23 下午7:26, Salvatore Bonaccorso 写道:
> Control: tags -1 + moreinfo
>
> On Tue, Sep 24, 2019 at 05:34:04PM +0800, Shengwen Xiao wrote:
>> Package: src:linux
>> Version: 4.19.67-2
>> Severity: wishlist
>>
>> Dear Maintainer,
>>
>>My notebook dmesg has the following error info:
>>
>> [0.620736] platform MSFT0101:00: failed to claim resource 1: [mem 
>> 0xfed4-0xfed40fff]
>> [0.620849] acpi MSFT0101:00: platform device creation failed: -16
>>
>> Is this a bug of the kernel ?
> Sorry for the late reply. A while has passed, do you still have this
> reproducible?
>
> Regards,
> Salvatore



OpenPGP_signature
Description: OpenPGP digital signature

Bug#966862: gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple definition of ...

[Lukas Märdian]

Package: gramophone2
Version: 0.8.13a-3.1
Followup-For: Bug #966862
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

GCC >= v10 uses -fno-common by default, which leads to "multiple
definitions of ..." errors during the build.

By defining the -fcommon flag via DEB_CFLAGS_MAINT_APPEND (before the
cdbs includes) the build can be fixed. The attached patch does exactly
this.

Thanks for considering the patch.

  Lukas


-- System Information:
Debian Release: bullseye/sid
  APT prefers hirsute-updates
  APT policy: (500, 'hirsute-updates'), (500, 'hirsute-security'), (500, 
'hirsute')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-16-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gramophone2-0.8.13a/debian/rules gramophone2-0.8.13a/debian/rules
--- gramophone2-0.8.13a/debian/rules2020-03-28 01:24:28.0 +0100
+++ gramophone2-0.8.13a/debian/rules2021-04-23 16:49:39.0 +0200
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+export DEB_CFLAGS_MAINT_APPEND = -fcommon
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/makefile.mk
 include /usr/share/cdbs/1/rules/patchsys-quilt.mk

Bug#987159: broadcom-sta-dkms: error(-1) from calls to @wl_dev_intvar_get; @wl_cfg80211_get_tx_power by networkctl

[Roger Shimizu]

On Tue, Apr 20, 2021 at 4:10 AM Philip Stewart
 wrote:
>
> Hi Roger,
>
> Since installing the experimental package, I've spent some more time
> investigating and it appears the dmesg errors:
>
> 1. never occur if networkctl is executed as root
> 2. always occur if executed as a un-elevated user
> 3. sporadically occur if executed when elevated with sudo
>
> In all cases, the access point MAC address remains zeroed in the
> response.

Thanks for the confirmation!

> Otherwise, the experimental package appears to be an improvement in
> that the txpower is now reported and the access point MAC is visible
> using 'iw wlan0 link'. I assume it won't make it to the bullseye
> release, but do you know if the plan is to merge it into bulleye
> post-release?

I think backports would be more simple, and fast to upload.
Does that work for you?

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#987416: tenace has mailcap entries with quoted %-escapes

[Marriott NZ]

Package: tenace
Version: 0.16-2
Tags: security

Dear Maintainer,
the tenace package has mailcap entries with quoted %-escapes. That is 
considered unsafe. Proper escaping should be left to the programs using the 
entry.

This Lintian tag is triggered:
https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html

See also grave bug #930908, which was recently closed because "a Lintian test 
already exists":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908

I'm using the "security" tag because the affected rules in combination with 
certain mail user agents (or document openers) are the cause of a shell command 
injection vulnerability.

/usr/lib/mime/packages/tenace should be changed from:

 application/bbolin; tenace '%s'; test=test -n "$DISPLAY"

to:

 application/bbolin; tenace %s; test=test -n "$DISPLAY"

If you need more information let me know.

Thanks,
MNZ

Bug#987415: stopmotion has mailcap entries with quoted %-escapes

[Marriott NZ]

Package: stopmotion
Version: 0.8.5-2
Tags: patch, security

Dear Maintainer,
the stopmotion package has mailcap entries with quoted %-escapes. That is 
considered unsafe. Proper escaping should be left to the programs using the 
entry.

This Lintian tag is triggered:
https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html

See also grave bug #930908, which was recently closed because "a Lintian test 
already exists":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908

I'm using the "security" tag because the affected rules in combination with 
certain mail user agents (or document openers) are the cause of a shell command 
injection vulnerability.

If you need more information let me know.

Thanks,
MNZ
diff -ru a/debian/stopmotion.mime b/debian/stopmotion.mime
--- a/debian/stopmotion.mime	2019-11-19 16:43:10.0 +0100
+++ b/debian/stopmotion.mime	2021-04-23 15:54:02.397650992 +0200
@@ -1 +1 @@
-application/x-stopmotion;  /usr/bin/stopmotion  -caption "Animation Creator" '%s';   nametemplate='%s.sto'; test=test "$DISPLAY" != ""; priority=9
+application/x-stopmotion;  /usr/bin/stopmotion  -caption "Animation Creator" %s;   nametemplate=%s.sto; test=test "$DISPLAY" != ""; priority=9

Bug#987414: qgo has mailcap entries with quoted %-escapes

[Marriott NZ]

Package: qgo
Version: 2.1~git-20180413-1
Tags: patch, security

Dear Maintainer,
the qgo package has mailcap entries with quoted %-escapes. That is considered 
unsafe. Proper escaping should be left to the programs using the entry.

This Lintian tag is triggered:
https://lintian.debian.org/tags/quoted-placeholder-in-mailcap-entry.html

See also grave bug #930908, which was recently closed because "a Lintian test 
already exists":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930908

I'm using the "security" tag because the affected rules in combination with 
certain mail user agents (or document openers) are the cause of a shell command 
injection vulnerability.

If you need more information let me know.

Thanks,
MNZ
diff -ru a/debian/qgo.mime b/debian/qgo.mime
--- a/debian/qgo.mime	2012-05-19 12:29:17.0 +0200
+++ b/debian/qgo.mime	2021-04-23 15:53:02.013666799 +0200
@@ -1 +1 @@
-application/x-go-sgf; qgo '%s'; edit=qgo '%s'; test=test "$DISPLAY" != ""; priority=2
+application/x-go-sgf; qgo %s; edit=qgo %s; test=test "$DISPLAY" != ""; priority=2

Bug#987383: ddskk: hangs during installation with emacs 26 (buster)

[Tatsuya Kinoshita]

On 2021-04-22 at 23:36 +0200, Andreas Beckmann wrote:
> It installed fine in 'buster', then the upgrade to 'bullseye' fails.
> The upgrade hangs infinitely if ddskk is upgraded before emacs, which
> happens e.g. when doing
> apt-get upgrade && apt-get dist-upgrade

Thanks for the report.

I've confirmed that byte-compiling skk-bayesian.el is conditionally problematic.

Will be fixed soon.

Thanks,
--
Tatsuya Kinoshita


pgpqgOnt3c52q.pgp
Description: PGP signature

Bug#987413: ITP: onboard-keyman -- Simple On-screen Keyboard that works with Keyman for Linux

[Eberhard Beilharz]

Package: wnpp

Severity: wishlist
Owner: Eberhard Beilharz 

Package Name : onboard-keyman
Version : 1.4.1-5
Upstream Author : Eberhard Beilharz 
URL : https://github.com/keymanapp/onboard-keyman
License : GPL-3+

Description :  On-screen Keyboard with macros, easy layout creation and 
word suggestion that works with Keyman for Linux.


This is an alternative to the onboard package which is based on the same 
code, but has some enhancements so that it works with Keyman for Linux. 
It was decided to provide onboard-keyman as an alternative package to 
onboard in order not to introduce a new dependency to the onboard package.


Keyman for Linux (keyman-config, v14.0.x) already has a recommends 
dependency on onboard-keyman.


X-Debbugs-CC:debian-input-met...@lists.debian.org

Bug#714119: nouveau: upgrade to jessie causes console hard lockup during boot

[Salvatore Bonaccorso]

Hi,

On Tue, Jun 25, 2013 at 11:38:26PM +0100, Graham Cobb wrote:
> Package: src:linux
> Version: 3.9.6-1
> Severity: important
> 
> Dear Maintainer,
> 
> After "apt-get dist-upgrade" from Wheezy to Jessie, could not reboot with the 
> new linux 3.9 kernel.  The boot appeared to stop, with the console hung, 
> shortly after loading the nouveau graphics driver.

Assuming the issue is not anymore reproducible on recent kernels I'm 
going to close this bugreport by now to clean up the list of src:linux
bugs from very old issues. In case you can reproduce the issue feel
free to reopen the bug.
 
Regards,
Salvatore

Bug#717066: linux-image-3.2.0-4-amd64: kernel oops XEN 4.1.4 dom0 wheezy 3.2.0-4 after dd about 1-2.5GB

[Salvatore Bonaccorso]

Hi,

On Tue, Jul 16, 2013 at 02:56:20PM +0200, xen1.ho-pa.cz wrote:
> Package: src:linux
> Version: 3.2.46-1
> Severity: important
> 
> Dear Maintainer,
> 
> PC is accesible ssh only and power switch. Boot fresh Wheezy, with XEN 
> 4.1.4-3+deb7u1 hypervisor, copy some 
> data from one place to other with: dd, cat or natcat, does not matter: /file, 
> /dev/sda5, 
> /dev/md1 (raid1), LVM device, /dev/null.
> After 1-2.5GB of copy (seen in buffer size in top) kernel oops, sometimes 
> reboot (mostly nc), sometimes halt (mostly dd).
> 
> HW: AMD VISHERA FX-4300, two diferent motherboards, 2x 2TB SATA HDD (first 
> 50GB is enough)
> 
> Does not matter where start or end on 2TB hdd. Without XEN hypervisor problem 
> gone !
> Not helped kernel parameters: xsave=0, noxsave, noxsaveopt, xsaveopt=0 
> 
> Repair was done through upgrade kernel to wheezy-backports 
> linux-image-3.9-0.bpo.1-amd64.

Assuming the issue is not anymore reproducible on recent kernels I'm 
going to close this bugreport by now to clean up the list of src:linux
bugs from very old issues. In case you can reproduce the issue feel
free to reopen the bug.
 
Regards,
Salvatore

Bug#722263: linux-image-3.2.0-4-amd64: efivarfs is not supported by the Debian kernel.

[Salvatore Bonaccorso]

Source: linux
Source-Version: 3.11~rc7-1~exp1

On Mon, Sep 09, 2013 at 04:56:08PM +0200, Hendrik Schwartke wrote:
> Package: src:linux
> Version: 3.2.46-1+deb7u1
> Severity: important
> 
> Dear Maintainer,
> 
> we are trying to setup Debin Linux in a UEFI Secure Boot environment using
> our own keying material.
> To be able to write to the UEFI Secure Boot nvram from Linux we need support
> for the efivarfs. Unfortunately this is not supported
> on Debian Linux:
> grep CONFIG_EFIVAR_FS config--amd64
> # CONFIG_EFIVAR_FS is not set
> 
> All tools to introduce new keys, certificates and hashes, like the mokutil
> and the sbsigntools, require this filesystem.
> 
> Please consider supporting the EFIVARFS since it should not create any
> conflict with other options.

Since 3.11~rc7-1~exp1 we have

  * [x86,ia64] fs: Enable EFIVAR_FS as module

Regards,
Salvatore

Bug#721698: linux-image-3.10-2-amd64: kernel panik

[Salvatore Bonaccorso]

Hi,

On Tue, Sep 03, 2013 at 10:18:11AM +0200, Fabian Greffrath wrote:
> Package: src:linux
> Version: 3.10.7-1
> Severity: important
> 
> Dear kernel team,
> 
> today my kernel paniked on my out of nothing. This is the third time within a
> week that I get a kernel panik with 3.10.7, but this time I got my mobile 
> phone
> with me to take a picture of its death. Version 3.9 did not panik a single 
> time
> and I am rather sure 3.10.5 didn't either.

Assuming the issue is not anymore reproducible on recent kernels I'm 
going to close this bugreport by now to clean up the list of src:linux
bugs from very old issues. In case you can reproduce the issue feel
free to reopen the bug.
 
Regards,
Salvatore

Bug#727266: BUG: unable to handle kernel paging request at 0000080000000028

[Salvatore Bonaccorso]

Hi,

On Wed, Oct 23, 2013 at 09:25:15PM +0200, Hans Yntema wrote:
> Package: src:linux
> Version: 3.2.51-1
> Severity: important
> 
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Headless server. Situation occured at somepoint in time
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> I had to reset system to reboot. System only responded to ping. SSH/HTTP 
> server did not respond
> 
>* What was the outcome of this action?
>* What outcome did you expect instead?

Assuming the issue is not anymore reproducible on recent kernels I'm 
going to close this bugreport by now to clean up the list of src:linux
bugs from very old issues. In case you can reproduce the issue feel
free to reopen the bug.
 
Regards,
Salvatore