date:20220916

Source: grub2
Version: 2.02~beta2-22
Severity: normal

Hello,

In version 1.99~rc1-5, most grub packages were made Multi-Arch: foreign
with the following changelog: 

Mark binary packages as Multi-Arch: foreign (for example, an amd64
kernel installed on an i386 system could use the native architecture's
GRUB).

But this looks incorrect to me, at least for some packages. The
case we have noticed is the grub-ieee1275-bin package in the case
of cross-building the debian installer. Since grub-ieee1275-bin
is multi-arch: foreign, the cross-build will be happy to use
grub-ieee1275-bin:amd64 as a dependency to provide the grub modules to
be included on the ISO image, which is wrong for e.g. cross-building a
powerpc ISO image.

AIUI, grub-ieee1275-bin should for instance rather be Multi-Arch: same,
so that the "build arch" version of grub-ieee1275-bin gets pulled for
building d-i, while still be co-installable along a host-installed
grub-ieee1275-bin package?

The same kind of remark probably applies to most grub arch-specific
packages.

The original discussion is on
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/24

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Bug#1019575: usr-is-merged false-negative on arm64

2022-09-16 Thread Luca Boccassi

On Tue, 13 Sep 2022 07:57:12 +0200 Marco d'Itri  wrote:
> On Sep 12, Boris Kolpackov  wrote:
> 
> > Indeed. A bit more digging revealed that this is systemd-nspawn's
> > "helpful" hand. Specifically, there is no /lib64 before I run
> > systemd-nspawn, it is present during, and it disappears again after
> > systemd-nspawn exits.
> This is caused by src/shared/base-filesystem.c, we are still trying
to 
> figure out if and what needs to be changed.

I'll relax the checks in the maintainer scripts so that we only check
that the arch-specific lib dirs match /usr/lib* - the precise directory
they point to doesn't really matter for our purpose after all.
This fixes the issue and now usr-is-merged can be installed just fine
in nspawn on arm64.

I'll do an NMU shortly so that tomorrow I can begin the transition.

-- 
Kind regards,
Luca Boccassi

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

Bug#1019956: less: backspace-based underlining breaks weirdly for multiple columns at a time

2022-09-16 Thread наб

Package: less
Version: 551-2
Version: 590-1
Severity: normal

Dear Maintainer,

printf 'abcd\b\b\b\b \b\b\b\bABCD'  | less
renders as (with ąĄ for underlined aA):
ą___ ĄBCD
which is "not what I'd expect" at least and given that this works for
individual columns just fine I'd hazard a guess that it's "just wrong".

(The former is a very popular style from the time of actual
 typewriters-as-terminals that I run into constantly.
 I haven't encountered the latter in the wild I think.)

Best,
наб

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

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

Versions of packages less depends on:
ii  libc6  2.31-13+deb11u4
ii  libtinfo6  6.2+20201114-2

less recommends no packages.

less suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1019549: fetchmail: can't accept options while a background fetchmail is running.

2022-09-16 Thread Atsuhito Kohda

Hi,

> Fixed package which no longer enables systemd service for users is on its way.

Great, this is the best fix, I believe.

Thanks for your maintenance.
Best regards,   2022-9-17(Sat)

-- 
 **
 Atsuhito Kohda
 atsuhito_k AT tokushima-u.ac.jp

Bug#969631: can base-passwd provide the user _apt?

2022-09-16 Thread Colin Watson

On Wed, Nov 24, 2021 at 10:51:50AM +0100, Johannes Schauer Marin Rodrigues 
wrote:
> Quoting Johannes Schauer Marin Rodrigues (2021-10-23 12:13:23)
> > from the discussion it seems that there are two separate issues.
> > 
> >  1. giving _apt the static uid 42 for new installations
> > 
> > The policy has an argument against it but Russ argues that might be reading 
> > the
> > policy requirement too strictly.
> > 
> >  2. switching _apt uid on existing installations
> > 
> > This can break setups relying on file:// and copy:// but David Kalnischkies
> > points out a possible migration strategy.
> > 
> > So other than reading the policy in a very strict way, what speaks against
> > adding apt as uid 42 today and then implement the migration path after the 
> > next
> > stable release with warnings of apt as David suggests?
> > 
> > Having _apt with a stable uid does fix problems with uid allocation,
> > dependencies on adduser and DPKG_ROOT today and does not cause any problems 
> > on
> > user's systems. Can we do this now as a first step? Is anything else missing
> > other than the trivial diff I wrote above?
> 
> I was looking into writing a patch to base-passwd that makes this possible but
> I need some help from you. As I initially observed, it seems to be easy to 
> just
> let _apt be user 42 for new installations by adding the respective entry to
> passwd.master. Adding that entry will not change the existing _apt user 
> because
> update-passwd will ignore changes in user ids >= 100.
> 
> It becomes tricky if we want to add a mechanism to convert the _apt uid of
> existing installations because the postinst only runs update-passwd if
> --dry-run found a change. But we don't want --dry-run to find a change unless
> the postinst is run with a low debconf priority (like during 
> dpkg-reconfigure).
> But flag_debconf is not set to 1 under --dry-run.
> 
> Do you see a solution that is not too hacky?

Coming back to this thread, I think I've reached the conclusion that
trying to migrate the uid is too risky due to the various weird and
wonderful things that might need to be changed to match, and it makes
more sense to just add the uid and leave existing systems alone.

The patch you posted earlier has a couple of problems (a missing colon,
and I think it makes more sense to set nogroup as _apt's primary group
rather than gid 42 which is in fact the "shadow" group), but I've gone
ahead and committed this:

  
https://salsa.debian.org/debian/base-passwd/-/commit/dc157c65936b15b44d359fcbd10481f101bd9c15

I tested this both by making a stock chroot and then upgrading
(preserved existing uid), and by using "sudo mmdebstrap --hook-dir
/usr/share/mmdebstrap/hooks/file-mirror-automount --include
./base-passwd_3.6.1_amd64.deb unstable unstable" to ensure that the new
version is installed first (used uid 42).

Last call for objections before upload!

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1019955: elpa-devscripts: errors on emacs startup

2022-09-16 Thread Sean Whitton

control: severity -1 minor

Hello,

On Fri 16 Sep 2022 at 02:07PM -07, Ross Vandegrift wrote:

> Package: elpa-devscripts
> Version: 40.5
> Severity: normal
>
> Hello,
>
> I just installed elpa-devscripts after upgrading to bookworm.  The package
> generates lots of warnings that I don't recall on my bullseye system.  Nothing
> seems broken, once I clear the warnings.

You are seeing the warnings due to the new native compilation feature,
which is significantly noisier about such things.

I think all these are bugs in elpa-devscripts of Severity: minor.  There
is the further question as to whether Emacs should change its defaults
so that you don't see these.  I think that would be a separate bug.

-- 
Sean Whitton

signature.asc
Description: PGP signature

Bug#1019955: elpa-devscripts: errors on emacs startup

2022-09-16 Thread Ross Vandegrift

Package: elpa-devscripts
Version: 40.5
Severity: normal

Hello,

I just installed elpa-devscripts after upgrading to bookworm.  The package
generates lots of warnings that I don't recall on my bullseye system.  Nothing
seems broken, once I clear the warnings.

On the first start up:

Warning (comp): debian-el.el:90:26: Warning: reference to free variable 
‘dired-mode-map’ Disable showing Disable logging
Warning (comp): dpkg-dev-el.el:117:44: Warning: reference to free variable 
‘filename’ Disable showing Disable logging


When I opened a d/changelog file:

Warning (comp): debian-changelog-mode.el:495:13: Warning: Package cl is 
deprecated Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1273:36: Warning: ‘previous-line’ 
is for interactive use only; use ‘forward-line’ with negative argument instead. 
Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1382:4: Warning: ‘easy-menu-add’ 
is an obsolete function (as of 28.1); this was always a no-op in Emacs and can 
be safely removed. Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1382:18: Warning: reference to 
free variable ‘debian-changelog-menu’ Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1423:4: Warning: make-face called 
with 2 arguments, but accepts only 1 Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1428:4: Warning: 
set-face-foreground called with 5 arguments, but accepts only 2-3 Disable 
showing Disable logging
Warning (comp): debian-changelog-mode.el:1750:17: Warning: 
‘imenu-progress-message’ is an obsolete macro (as of 28.1). Disable showing 
Disable logging
Warning (comp): debian-changelog-mode.el:1755:19: Warning: 
‘imenu-progress-message’ is an obsolete macro (as of 28.1). Disable showing 
Disable logging
Warning (comp): debian-changelog-mode.el:1778:11: Warning: 
‘imenu-progress-message’ is an obsolete macro (as of 28.1). Disable showing 
Disable logging
Warning (comp): debian-changelog-mode.el:1683:12: Warning: the function 
‘set-extent-property’ is not known to be defined. Disable showing Disable 
logging
Warning (comp): debian-changelog-mode.el:1676:25: Warning: the function 
‘make-extent’ is not known to be defined. Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1654:18: Warning: the function 
‘delete-extent’ is not known to be defined. Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1653:42: Warning: the function 
‘extent-end-position’ is not known to be defined. Disable showing Disable 
logging
Warning (comp): debian-changelog-mode.el:1652:42: Warning: the function 
‘extent-start-position’ is not known to be defined. Disable showing Disable 
logging
Warning (comp): debian-changelog-mode.el:1651:22: Warning: the function 
‘extent-detached-p’ is not known to be defined. Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:1625:14: Warning: the function 
‘set-keymap-name’ is not known to be defined. Disable showing Disable logging
Warning (comp): debian-changelog-mode.el:880:4: Warning: the function 
‘debian-bug-build-bug-menu’ is not known to be defined. Disable showing Disable 
logging
Warning (comp): debian-bug.el:496:16: Warning: assignment to free variable 
‘debian-bug-menu-action’ Disable showing Disable logging
Warning (comp): debian-bug.el:652:37: Warning: ‘mapcar’ called for effect; 
use ‘mapc’ or ‘dolist’ instead Disable showing Disable logging
Warning (comp): debian-bug.el:652:50: Warning: ‘mapcar’ called for effect; 
use ‘mapc’ or ‘dolist’ instead Disable showing Disable logging
Warning (comp): debian-bug.el:944:41: Warning: ‘next-line’ is for 
interactive use only; use ‘forward-line’ instead. Disable showing Disable 
logging
Warning (comp): debian-bug.el:1792:6: Warning: ‘easy-menu-add’ is an 
obsolete function (as of 28.1); this was always a no-op in Emacs and can be 
safely removed. Disable showing Disable logging
Warning (comp): debian-bug.el:1843:6: Warning: ‘easy-menu-add’ is an 
obsolete function (as of 28.1); this was always a no-op in Emacs and can be 
safely removed. Disable showing Disable logging
Warning (comp): debian-bug.el:2347:20: Warning: Use ‘with-current-buffer’ 
rather than save-excursion+set-buffer Disable showing Disable logging
Warning (comp): debian-bug.el:2276:21: Warning: Use ‘with-current-buffer’ 
rather than save-excursion+set-buffer Disable showing Disable logging
Warning (comp): debian-bug.el:2351:33: Warning: Use ‘with-current-buffer’ 
rather than save-excursion+set-buffer Disable showing Disable logging
Warning (comp): debian-bug.el:2360:10: Warning: ‘easy-menu-remove’ is an 
obsolete function (as of 28.1); this was always a no-op in Emacs and can be 
safely removed. Disable showing Disable logging
Warning (comp): debian-bug.el:2371:10: Warning: ‘easy-menu-remove’ is an 
obsolete

Bug#1019954: kicad: Plugins fail with a python exception error

2022-09-16 Thread raster

Package: kicad
Version: 6.0.7+dfsg-1+b1
Severity: important
X-Debbugs-Cc: rasters...@gmail.com

Dear Maintainer,

I've been using several plugins with Kicad, but since two days ago, if I try to
use any of them, an error window with a python exception appears:

wx._core.PyNoAppError: The wx.App object must be created first!


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 kicad depends on:
ii  libc62.34-8
ii  libcairo21.16.0-6
ii  libcurl4 7.85.0-1
ii  libgcc-s112.2.0-2
ii  libgl1   1.5.0-1
ii  libglew2.2   2.2.0-4
ii  libglib2.0-0 2.73.3-3
ii  libglu1-mesa [libglu1]   9.0.2-1
ii  libgtk-3-0   3.24.34-3
ii  libngspice0  37+ds-1
ii  libocct-data-exchange-7.67.6.3+dfsg1-3
ii  libocct-foundation-7.6   7.6.3+dfsg1-3
ii  libocct-modeling-algorithms-7.6  7.6.3+dfsg1-3
ii  libocct-modeling-data-7.67.6.3+dfsg1-3
ii  libocct-ocaf-7.6 7.6.3+dfsg1-3
ii  libpixman-1-00.40.0-1
ii  libpython3.103.10.7-1
ii  libstdc++6   12.2.0-2
ii  libwxbase3.0-0v5 3.0.5.1+dfsg-5
ii  libwxgtk3.0-gtk3-0v5 3.0.5.1+dfsg-5
ii  python3  3.10.6-1
ii  python3-wxgtk4.0 4.2.0+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages kicad recommends:
ii  kicad-demos  6.0.7+dfsg-1
ii  kicad-libraries  6.0.7+dfsg-1
ii  xsltproc 1.1.35-1

Versions of packages kicad suggests:
ii  extra-xdg-menus 1.0-6
pn  kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-  
ii  kicad-packages3d6.0.7-1

-- no debconf information

Bug#1019953: flamerobin: FTBFS on arm, i386, mips

Source: flamerobin
Version: 0.9.3.12-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

flamerobin 0.9.3.12-1 FTBFS on serveral arches (arm*, i386, mips*).

Relevant log snippets:

cd /<>/obj-aarch64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-aarch64-linux-gnu /<>/obj-aarch64-linux-gnu 
/<>/obj-aarch64-linux-gnu/CMakeFiles/IBPP.dir/DependInfo.cmake 
--color=
make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
make  -f CMakeFiles/IBPP.dir/build.make CMakeFiles/IBPP.dir/build
make[3]: Entering directory '/<>/obj-aarch64-linux-gnu'
[  0%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o
[  1%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_ibpp.cpp.o -c /<>/src/ibpp/_ibpp.cpp
[  2%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o
[  3%] Building CXX object CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_rb.cpp.o -c /<>/src/ibpp/_rb.cpp
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_dpb.cpp.o -c /<>/src/ibpp/_dpb.cpp
/usr/bin/c++ -DFR_INSTALL_PREFIX=\"/usr\" -DIBPP_LINUX -DWXUSINGDLL 
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/res 
-I/<>/src/ibpp -I/<>/src -isystem 
/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT 
CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o -MF 
CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o.d -o 
CMakeFiles/IBPP.dir/src/ibpp/_ibs.cpp.o -c /<>/src/ibpp/_ibs.cpp
In file included from /<>/src/ibpp/ibpp.h:71,
 from /<>/src/ibpp/_ibpp.h:23,
 from /<>/src/ibpp/_rb.cpp:26:
/usr/include/c++/12/decimal/decimal:39:2: error: #error This file requires 
compiler and library support for ISO/IEC TR 24733 that is currently not 
available.
   39 | #error This file requires compiler and library support for ISO/IEC TR 
24733 \
  |  ^
/usr/include/c++/12/decimal/decimal:233:5: error: decimal floating-point not 
supported for this target
  233 | decimal32() : __val(0.e-101DF) {}
  | ^
/usr/include/c++/12/decimal/decimal:319:5: error: decimal floating-point not 
supported for this target
  319 | decimal64() : __val(0.e-398dd) {}
  | ^
/usr/include/c++/12/decimal/decimal:405:5: error: decimal floating-point not 
supported for this target
  405 | decimal128(): __val(0.e-6176DL) {}
  | ^~
In file included from /usr/include/c++/12/decimal/decimal:492:
/usr/include/c++/12/decimal/decimal.h:127:9: error: decimal floating-point not 
supported for this target
  127 | __multiplier = 1.E-1DF;
  | ^~~~
/usr/include/c++/12/decimal/decimal.h:131:7: error: decimal floating-point not 
supported for this target
  131 |   __multiplier = 1.E1DF;
  |   ^~~~
/usr/include/c++/12/decimal/decimal.h:145:9: error: decimal floating-point not 
supported for this target
  145 | __multiplier = 1.E-1DF;
  | ^~~~
/usr/include/c++/12/decimal/decimal.h:149:7: error: decimal floating-point not 
supported for this target
  149 |   __multiplier = 1.E1DF;
  |   ^~~~
/usr/include/c++/12/decimal/decimal.h:163:9: error: decimal floating-point not 
supported for this target
  163 | __multiplier = 1.E-1DD;

Bug#937234: trying to remove python2.7 from bookworm

2022-09-16 Thread Paul Gevers


Hi Mike,

On Mon, 15 Aug 2022 13:54:27 + Mike Gabriel 
 wrote:
in another project context I have a freelancer working on pam-python  
Py3 transition. Will pick up the threads this week (I returned freshly  
from VAC yesterday).


One month went by, is there any progress to report?

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019952: gnome-disk-utility: segfault in libudisks2.so.0.0.0

2022-09-16 Thread piorunz

Package: gnome-disk-utility
Version: 43~rc-1
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

Managed to crash Gnome Disks today. My computer allows to plug and unplug SATA
drives in and out, no problem, just like they were USB drives. I use this
feature all the time when I need it. Debian has no problem with that,
everything is detected in dmesg and it works.

But Gnome Disks has crashed today when I forcibly removed one SATA drive.
Dmesg log:

[74280.712568] ata5: SATA link down (SStatus 0 SControl 300)
[74280.712577] ata5.00: disable device
[74280.712591] ata5.00: detaching (SCSI 4:0:0:0)
[74280.766384] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[74280.766404] sd 4:0:0:0: [sdb] Synchronize Cache(10) failed: Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[74280.766405] sd 4:0:0:0: [sdb] Stopping disk
[74280.766408] sd 4:0:0:0: [sdb] Start/Stop Unit failed: Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[74281.147838] gnome-disks[2098897]: segfault at a0 ip 7f7b10aeefc8 sp
7ffd5bd91c48 error 4 in libudisks2.so.0.0.0[7f7b10adb000+53000]
[74281.147852] Code: e9 0d ce fe ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 53
48 89 fb e8 77 c3 fe ff 48 8b 3b 48 89 c6 e8 bc c0 fe ff 48 89 df 5b <48> 8b 80
a0 00 00 00 ff e0 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44

I can plug in and out this drive, it always work perfectly, but Disks is
crashing sometimes when I do it. Please look into it, Gnome Disks should
gracefully handle all plugging and unplugging, just like kernel does.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-disk-utility depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  libatk1.0-0  2.38.0-1
ii  libc62.34-7
ii  libcairo21.16.0-6
ii  libcanberra-gtk3-0   0.30-10
ii  libdvdread8  6.1.3-1
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.73.3-3
ii  libgtk-3-0   3.24.34-3
ii  libhandy-1-0 1.7.90-1
ii  liblzma5 5.2.5-2.1
ii  libnotify4   0.8.1-1
ii  libpango-1.0-0   1.50.9+ds-1
ii  libpangocairo-1.0-0  1.50.9+ds-1
ii  libpwquality11.4.4-1+b1
ii  libsecret-1-00.20.5-3
ii  libsystemd0  251.4-3
ii  libudisks2-0 2.9.4-3
ii  udisks2  2.9.4-3

gnome-disk-utility recommends no packages.

gnome-disk-utility suggests no packages.

-- no debconf information

Bug#1019951: RM: git-annex [armel armhf] -- ROM; unclear whether we can have git-annex on these archs atm

2022-09-16 Thread Sean Whitton

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 1014...@bugs.debian.org

I don't know whether we can support git-annex on armel, armhf in the
near future.  There was an FTBFS reported in #1014628, but it hasn't
been possible to investigate it for months because the Haskell
transition is stalled on the 32-bit ARM architectures.

I think that it is appropriate to have git-annex's migration to testing
be based only on the other architectures for the time being, and am
therefore requesting a partial removal.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1014628: src:git-annex: fails to migrate to testing for too long: FTBFS on armel and armhf

2022-09-16 Thread Sean Whitton

Hello,

Some time ago Joey suggested uploading something like the attached to
try to debug the build failures of 8.20211123 on the 32-bit ARM archs.
However, it has not been possible to do this for some months because the
Haskell transition is stalled on those architectures.  I'm sending this
mail primarily in order to store this work somewhere public.  However,
we don't know whether the bug still exists, with so much of the Haskell
ecosystem having been updated recently, including git-annex.

My plan is to ask ftpmaster to remove git-annex on armel and armhf and
then downgrade the severity of this bug.  For the time being, we don't
know whether Debian can support git-annex on armel & armhf for bookworm.

-- 
Sean Whitton
From 51e38d17b0f8914f78c3e5f27819016d9bfe1750 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Mon, 18 Jul 2022 15:19:36 -0700
Subject: [PATCH] Add 'ghc -e' command to override_dh_auto_build

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

diff --git a/debian/changelog b/debian/changelog
index 37b6401af..ee0a9ce9a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+git-annex (10.20220724-1+exp1) experimental; urgency=medium
+
+  * Add 'ghc -e' command to override_dh_auto_build.
+Suggestion from upstream for solving an apparently buildd-specific bug.
+
+ -- Sean Whitton   Sun, 21 Aug 2022 15:23:50 -0700
+
 git-annex (10.20220724-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/rules b/debian/rules
index a9c5aff8d..06af0db93 100755
--- a/debian/rules
+++ b/debian/rules
@@ -35,6 +35,7 @@ export ZSH_COMPLETIONS_PATH=/usr/share/zsh/vendor-completions
 ifeq ($(STANDALONE_BUILD),1)
 
 override_dh_auto_build:
+	ghc -e 'import DBus.Client' -e 'print DBus.Client.addMatch' || true
 	make linuxstandalone GIT_ANNEX_PACKAGE_INSTALL=1
 
 override_dh_auto_install:
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#1019787: silverjuke: Please transition to wxwidgets3.2


On Thu, 15 Sep 2022, Dr. Tobias Quathamer wrote:


Am 14.09.22 um 21:42 schrieb s...@techie.net:

Hi,

Please transition silverjuke from wxwidgets3.0 to wxwidgets3.2.

[...]

Some packages may require small patches; I'm happy to help with those
(and I have some already from working on this transition in Fedora 
already).


Hi Scott,

thanks for the information. Currently, the build fails with wxwidgets3.2 due 
to this error:


'const class wxHtmlTag' has no member named 'GetBeginPos'; did you mean 
'GetBeginIter'?


The file in question is src/sjbase/skinml.cpp, line 885[1]. Could you help me 
with a patch or a hint what to do here?


Patch sent:
https://salsa.debian.org/debian/silverjuke/-/merge_requests/1

Regards,
Scott

Bug#1012918: edb-debugger: diff for NMU version 1.3.0-1.1

Control: tags 1012918 + pending

Dear maintainer,

I've prepared an NMU for edb-debugger (versioned as 1.3.0-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru edb-debugger-1.3.0/debian/changelog edb-debugger-1.3.0/debian/changelog
--- edb-debugger-1.3.0/debian/changelog	2021-01-26 16:01:19.0 +0200
+++ edb-debugger-1.3.0/debian/changelog	2022-09-16 22:27:35.0 +0300
@@ -1,3 +1,10 @@
+edb-debugger (1.3.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with gcc 12. (Closes: #1012918)
+
+ -- Adrian Bunk   Fri, 16 Sep 2022 22:27:35 +0300
+
 edb-debugger (1.3.0-1) unstable; urgency=medium
 
   [ Marcio de Souza Oliveira ]
diff -Nru edb-debugger-1.3.0/debian/patches/0001-Gcc-12-includes-fix-815.patch edb-debugger-1.3.0/debian/patches/0001-Gcc-12-includes-fix-815.patch
--- edb-debugger-1.3.0/debian/patches/0001-Gcc-12-includes-fix-815.patch	1970-01-01 02:00:00.0 +0200
+++ edb-debugger-1.3.0/debian/patches/0001-Gcc-12-includes-fix-815.patch	2022-09-16 22:26:22.0 +0300
@@ -0,0 +1,100 @@
+From da04c339559f82257ff54ea62b1d403ee98c1ba0 Mon Sep 17 00:00:00 2001
+From: Sergei Trofimovich 
+Date: Sat, 2 Apr 2022 22:36:50 +
+Subject: Gcc 12 includes fix (#815)
+
+* RegisterViewModelBase.h: add  for unique_ptr
+
+Without the change gcc-12 fails to build edb-debugger as:
+
+[ 20%] Building CXX object src/CMakeFiles/edb.dir/RegisterViewModelBase.cpp.o
+In file included from edb-debugger/src/RegisterViewModelBase.cpp:18:
+edb-debugger/include/RegisterViewModelBase.h:162:14: error:
+  'unique_ptr' in namespace 'std' does not name a template type
+  162 | std::unique_ptr rootItem;
+  |  ^~
+edb-debugger/include/RegisterViewModelBase.h:9:1: note:
+  'std::unique_ptr' is defined in header '';
+did you forget to '#include '?
+8 | #include 
+  +++ |+#include 
+
+* State.h: add  for unique_ptr
+
+Without the change gcc-12 fails to build edb-debugger as:
+
+[ 21%] Building CXX object src/CMakeFiles/edb.dir/State.cpp.o
+In file included from edb-debugger/src/State.cpp:19:
+edb-debugger/include/State.h:93:14:
+  error: 'unique_ptr' in namespace 'std' does not name a template type
+   93 | std::unique_ptr impl_;
+  |  ^~
+edb-debugger/include/State.h:24:1:
+  note: 'std::unique_ptr' is defined in header '';
+did you forget to '#include '?
+   23 | #include "Types.h"
+  +++ |+#include 
+   24 |
+
+* IState.h: add  for unique_ptr
+
+Without the change gcc-12 fails to build edb-debugger as:
+
+[ 69%] Building CXX object plugins/DebuggerCore/CMakeFiles/DebuggerCore.dir/unix/linux/arch/x86-generic/PlatformState.cpp.o
+In file included from edb-debugger/plugins/DebuggerCore/unix/linux/arch/x86-generic/PlatformState.h:22,
+ from edb-debugger/plugins/DebuggerCore/unix/linux/arch/x86-generic/PlatformState.cpp:19:
+edb-debugger/include/IState.h:33:22:
+  error: 'unique_ptr' in namespace 'std' does not name a template type
+   33 | virtual std::unique_ptr clone() const = 0;
+  |  ^~
+edb-debugger/include/IState.h:23:1:
+  note: 'std::unique_ptr' is defined in header '';
+did you forget to '#include '?
+   22 | #include "Register.h"
+  +++ |+#include 
+   23 | #include "Types.h"
+---
+ include/IState.h| 1 +
+ include/RegisterViewModelBase.h | 1 +
+ include/State.h | 1 +
+ 3 files changed, 3 insertions(+)
+
+diff --git a/include/IState.h b/include/IState.h
+index e7cc9a2f..fa5387be 100644
+--- a/include/IState.h
 b/include/IState.h
+@@ -19,6 +19,7 @@ along with this program.  If not, see .
+ #ifndef ISTATE_H_20110315_
+ #define ISTATE_H_20110315_
+ 
++#include 
+ #include "Register.h"
+ #include "Types.h"
+ 
+diff --git a/include/RegisterViewModelBase.h b/include/RegisterViewModelBase.h
+index 3ed1ccf0..fad80510 100644
+--- a/include/RegisterViewModelBase.h
 b/include/RegisterViewModelBase.h
+@@ -6,6 +6,7 @@
+ #include "util/Integer.h"
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ Q_DECLARE_METATYPE(std::vector)
+diff --git a/include/State.h b/include/State.h
+index 13ef40bc..cfb7091e 100644
+--- a/include/State.h
 b/include/State.h
+@@ -19,6 +19,7 @@ along with this program.  If not, see .
+ #ifndef STATE_H_20060715_
+ #define STATE_H_20060715_
+ 
++#include 
+ #include "API.h"
+ #include "Types.h"
+ 
+-- 
+2.30.2
+
diff -Nru edb-debugger-1.3.0/debian/patches/series edb-debugger-1.3.0/debian/patches/series
--- edb-debugger-1.3.0/debian/patches/series	2021-01-26 16:01:19.0 +0200
+++ edb-debugger-1.3.0/debian/patches/series	2022-09-16 22:27:34.0 +0300
@@ -2,3 +2,4 @@
 fix_desktop_entry.patch

Bug#1019724: warning: stray \ before - causes autopkgtest failure

2022-09-16 Thread Paul Gevers

Hi Santiago,

On 15-09-2022 09:26, Paul Gevers wrote:
I am trying to schedule autopkgtests in unstable on amd64 for all source
packages that have one.

All results are now in. Only several test failed due this warning: the
known dpkg and cjet and the newly found nagios-plugins-contrib, logcheck
and xautolock (see links below).

Lucas, are you in the position to do an archive rebuild to check for the
grep warnings (see full history at [1]). When you submit bugs, can you
please file them as important, as apparently upstream wants to turn
these warnings into failures in the future, but in Debian Santiago is
going to silence the warning soon, so FTBFS due to this isn't an RC
problem on the short term.

Santiago, please keep the grep with warning in unstable until either all
tests are finished or we abort this plan.

To be honest, without bug 1019326 in ucf and bug 1019725 in libtool
fixed, I'm not sure how much value an archive rebuild would be at this
stage.

So I think it would be good to silence the warning now in Debian. As
discussed before, ideally with a way to turn it on (or make it error)
such that we can do archive wide QA before the behavior is changed to
error out upstream. I can understand it if you want to wait with
deploying that optional behavior until upstream has implemented it.

Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nagios-plugins-contrib/26117196/log.gz
/37.20211217/check_ssl_cert/check_ssl_cert_2.15.0/check_ssl_cert/ line 1125
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/logcheck/26123766/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/x/xautolock/26130620/log.gz
-->
https://sources.debian.org/src/xautolock/1%3A2.2-7/debian/tests/help/ line 5

OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019950: transition plan for borgbackup 2.x

2022-09-16 Thread Helmut Grohne

Package: borgbackup
Version: 1.2.2-1
X-Debbugs-Cc: Thomas Waldmann 

Hi,

I've been talking to Thomas (borgbackup upstream) about what is going to
happen with borg and it turns out this is not entirely trivial.

Once ugrading to borgbackup 2.x, you cannot continue to use borgbackup
1.x repositories. Rather you have to upgrade them which has to be done
with "borg transfer --upgrader=From12To20 ...". In particular, this will
copy all of the backup data.

So one option is to just upload borgbackup 2.x under the existing
package name. Doing so will immediately break all borg setups during the
upgrade. That's bad. Maybe the next thought is automatically converting
all repositories during upgrade, but this is totally out of question,
because the Debian package doesn't know the repositories and if it did,
it wouldn't be clear that they have sufficient space for temporarily
storing another copy. Quite obviously, this is not as simple as it
seems initially.

So I've been talking to Thomas about this, and we figured that it would
be good to move the borg repository upgrade out of the Debian stable
upgrade process. Quite obviously, you cannot upgrade your repositories
before bookworm as buster doesn't include borgbackup 2.x. So if you want
to do it later, bookworm must include borgbackup 1.x and borgbackup 2.x.
Ideally, doing the dist-upgrade would not switch from borgbackup 1.x to
borgbackup 2.x automatically.

So unless we want to loose sanity, we want two borgbackup source
packages in bookworm. One for 1.x and one for 2.x. Then next question is
what happens to /usr/bin/borg. I think we have basically three options:

a) It belongs to borgbackup 1.x and borgbackup 2.x uses a different name
   (e.g. borg2). Prior art: python3. This makes dist-upgrades easy, but
   everyone will have to change their scripts.
b) It belongs to borgbacku 2.x and borgbackup 1.x uses a different name
   (e.g. borg1). Prior art: openssh-client-ssh1. This makes
   dist-upgrades annoying and everyone will have to change their scripts
   twice (once during dist-upgrade).
c) It is flexible. It could be managed using update-alternatives. I
   suggest that bookworm gives a preference to borgbackup 1.x to make
   dist-upgrades painless.

At this time, I prefer the flexible route.

Beyond the cli, there also is the borg Python module. This presently is
located in /usr/lib/python3/dist-packages and thus importable by other
packages. I think this is wrong. Upstream clearly says[1] that the borg
module should not be used directly. As such, I think it would be better
to package it as a private module and move it to
/usr/lib//.  Once doing so, the
coinstallability of two borg modules becomes trivial.

If we want to follow this plan, borgbackup 2.x should be uploaded rather
sooner than later to clear new.

Do you agree with all of this?

Helmut

[1] 
https://borgbackup.readthedocs.io/en/stable/internals/frontends.html?highlight=stable%20api#all-about-json-how-to-develop-frontends

Bug#995486: pipewire: crash when -media-session connects

2022-09-16 Thread Adam Borowski

On Mon, Sep 12, 2022 at 04:45:36PM +0200, Dylan Aïssi wrote:
> Le sam. 2 oct. 2021 à 01:21, Adam Borowski  a écrit :
> > Upon startup, pipewire crashes for me.  After poking around, it turns out
> > it's not the startup of pipewire itself, but pipewire-media-session connects
> > to the main part soon after.

> If I am not wrong, this crash should not happen anymore since pipewire
> 0.3.52. Could you confirm it is really solved on your side?

I don't have an armhf machine to re-check, sorry.
The laptop this was on is on arm64 these days.

I've just tested, there's no crash -- but this means nothing for a 32-bit
only problem.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
⢿⡄⠘⠷⠚⠋⠀   ./configure --host=zx-spectrum --build=pdp11
⠈⠳⣄

Bug#1019949: numba seems to need autopkgtest dependency on python-is-python3

Source: numba
Version: 0.56.2+dfsg-1
Severity: serious

https://ci.debian.net/data/autopkgtest/unstable/amd64/n/numba/25838468/log.gz

...
==
FAIL: test_nonsense_gdb_binary (numba.tests.test_cli.TestGDBCLIInfoBrokenGdbs)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numba/tests/test_cli.py", line 277, in 
test_nonsense_gdb_binary
self.assertIn("Unknown option", stdout)
AssertionError: 'Unknown option' not found in "GDB 
info:\n\nBinary
 location   : Testing gdb binary failed. Reported 
Error: [Errno 2] No such file or directory: 'python'\nPrint extension location  
: 
/usr/lib/python3/dist-packages/numba/misc/gdb_print_extension.py\nPython 
version: No Python support\nNumPy version   
  : No NumPy support\nNumba printing extension support  
: None\n\nTo load the Numba gdb printing extension, execute the 
following from the gdb prompt:\n\nsource 
/usr/lib/python3/dist-packages/numba/misc/gdb_print_extension.py\n\n\n\n=\nIMPORTANT:
 Before sharing you should remove any information\nin the above that you wish 
to keep private e.g. 
paths.\n=\n\n"

--
Ran 10041 tests in 1454.235s

FAILED (failures=1, skipped=627, expected failures=13)
autopkgtest [10:00:43]: test python3-numba: ---]
autopkgtest [10:00:44]: test python3-numba:  - - - - - - - - - - results - - - 
- - - - - - -
python3-numbaFAIL non-zero exit status 1

Bug#1019809: gentle: Please transition to wxwidgets3.2


On Thu, 15 Sep 2022, Andreas Tille wrote:


Control: tags -1 help

Am Wed, Sep 14, 2022 at 03:42:14PM -0400 schrieb s...@techie.net:

Please transition gentle from wxwidgets3.0 to wxwidgets3.2.


I would like to support this but I have no idea about wxwidgets.


For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev.


Unfortunately this is not enouth in this case.


Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).


I've tagged the bug help and hope you can commit the patches needed.


Merge request with patch:
https://salsa.debian.org/med-team/gentle/-/merge_requests/1

Regards,
Scott

Bug#1019811: treeviewx: Please transition to wxwidgets3.2


On Thu, 15 Sep 2022, Andreas Tille wrote:


Control: tags -1 help

Am Wed, Sep 14, 2022 at 03:42:14PM -0400 schrieb s...@techie.net:

Please transition gentle from wxwidgets3.0 to wxwidgets3.2.


I would like to support this but I have no idea about wxwidgets.


For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev.


Unfortunately this is not enouth in this case.


Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).


I've tagged the bug help and hope you can commit the patches needed.

Here is the link to Salsa CI

  https://salsa.debian.org/med-team/treeviewx/-/jobs/3238712


Merge request with patch:
https://salsa.debian.org/med-team/treeviewx/-/merge_requests/2

Regards,
Scott

Bug#1019947: tortoisehg: thg fails on session restore: -s not recognized

2022-09-16 Thread Ross Boylan

Package: tortoisehg
Version: 5.6.1-1
Severity: normal
X-Debbugs-Cc: rossboy...@stanfordalumni.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

thg threw the error shown in the attachment and asked me to report it upstream.
This happened when logging into KDE after a system restart.  When I last
exited, thg had been running and so this was presumably part of a session
restore.  I made no explicit attempt to start thg.

I believe the key line in the error report is
getopt.GetoptError: option -s not recognized
and my guess is that the session restore is invoking thg with the -s option.
The man page shows no such option.

I *am* still able to launch thg through the menu system, and so this is a small
problem.



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

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

Versions of packages tortoisehg depends on:
ii  mercurial   5.6.1-4
ii  python3 3.9.2-3
ii  python3-pyqt5   5.15.2+dfsg-3
ii  python3-pyqt5.qsci  2.11.6+dfsg-2

Versions of packages tortoisehg recommends:
ii  libjs-jquery  3.5.1+dfsg+~3.5.5-7
ii  libjs-underscore  1.9.1~dfsg-3
pn  python-iniparse   
pn  python-pygments   

Versions of packages tortoisehg suggests:
pn  tortoisehg-nautilus  


-BEGIN PGP SIGNATURE-

iQFSBAEBCgA8FiEEreS674/HIyV9gBfdnAYPmOsbK2AFAmMkuuEeHHJvc3Nib3ls
YW5Ac3RhbmZvcmRhbHVtbmkub3JnAAoJEJwGD5jrGytg3YoH/1e55C6YNjs0c0tL
+e8lgNHrTcN6lqB+NxrXbOyxAwLIx//ykz5dSLnFyiD0iMaZBObP5hmqJcoUoo4a
ztgcZm71u/gYAuw4ZX8yahl3mGAzK7XzzNGyxrSmxYdEptQzTkTyt+9w2HFPv0AQ
9zfmTLP073Ypz612hObCdyXRbz+l4qguBs4EIfippfwSW8DPlsPtDbjUgiiTlpII
WYHrJ0jdj139xT5kI8un1sxoUBhAoNtgveSanNN+X6LEXzdK/vTMRzdwWQWHnBbJ
93+s5GVi2mp816t9413MDfl0gyf9iE8Xou78wq3E3/uPdDvz16W86gxMWs/TPUoR
kGDMkdg=
=45f/
-END PGP SIGNATURE-
#!python
** Mercurial version (5.6.1).  TortoiseHg version (5.6.1)
** Command: -session 
10c7da726c00016633136420041100063_1663349368_946077 -name thg
** CWD: /home/ross
** Encoding: UTF-8
** Extensions loaded: 
** Python version: 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 
20210110]
** System: Linux barley 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 
(2022-09-02) x86_64
** Qt-5.15.2 PyQt-5.15.2 QScintilla-2.11.6
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tortoisehg/hgqt/run.py", line 289, 
in _parse
args = fancyopts.fancyopts(args, globalopts, options)
  File "/usr/lib/python3/dist-packages/mercurial/fancyopts.py", line 367, 
in fancyopts
opts, args = parse(args, shortlist, namelist)
  File "/usr/lib/python3/dist-packages/mercurial/pycompat.py", line 493, in 
getoptb
return _getoptbwrapper(getopt.getopt, args, shortlist, namelist)
  File "/usr/lib/python3/dist-packages/mercurial/pycompat.py", line 330, in 
_getoptbwrapper
opts, args = orig(args, shortlist, namelist)
  File "/usr/lib/python3.9/getopt.py", line 95, in getopt
opts, args = do_shorts(opts, args[0][1:], shortopts, args[1:])
  File "/usr/lib/python3.9/getopt.py", line 195, in do_shorts
if short_has_arg(opt, shortopts):
  File "/usr/lib/python3.9/getopt.py", line 211, in short_has_arg
raise GetoptError(_('option -%s not recognized') % opt, opt)
getopt.GetoptError: option -s not recognized

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tortoisehg/hgqt/run.py", line 342, 
in _runcatch
return runcommand(ui, args)
  File "/usr/lib/python3/dist-packages/tortoisehg/hgqt/run.py", line 368, 
in runcommand
cmd, func, args, options, cmdoptions, alias = _parse(ui, args)
  File "/usr/lib/python3/dist-packages/tortoisehg/hgqt/run.py", line 291, 
in _parse
raise error.CommandError(None, stringutil.forcebytestr(inst))
mercurial.error.CommandError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tortoisehg/hgqt/run.py", line 138, 
in dispatch
return _runcatch(u, args)
  File "/usr/lib/python3/dist-packages/tortoisehg/hgqt/run.py", line 349, 
in _runcatch
if inst.args[0]:
IndexError: tuple index out of range

Bug#1019944: wireplumber: Upgradeing to 0.4.11-5 breaks restoring the target of a stream if it is not the default stream

2022-09-16 Thread Matthias Heinz

Hi,

with the help of NiklvsKoesikovs from the pipewire irc channel we came to the 
conclusion that the order in which pipewire-pulse and wireplumber are started 
matter.

pipewire-pulse has to be startet AFTER wireplumber.

Please add this to the systemd service file.


Thanks
Matthias

Bug#1019935: xorriso: Please make Multi-Arch: foreign

Thomas Schmitt, le ven. 16 sept. 2022 17:55:33 +0200, a ecrit:
> Samuel Thibault wrote:
> > Since AIUI the xorriso package provides only a tool whose behavior is
> > exactly the same on all architectures,
> 
> It depends on libburn which behaves different on Hurd compared to Linux.

I was more thinking about architecture (i386, amd64, arm, etc.)
difference, not OS difference :)

The question at stake is that when a package uses xorriso to cross-build
something (e.g. an iso image or burn a CD), it's fine to use the native
package for the build system, rather than sticking on the architecture
of the package being built. So as to be able to build i386 images on
an amd64 system or the converse, or even build arm images on an amd64
system, etc.

> > could you make it
> > Multi-Arch: foreign
> > so that the Debian Installer can use it as foreign dependency for
> > cross-builds?
> 
> Is the described situation still suitable for Multi-Arch: foreign ?

I'm not sure which situation you are referring to?

> If so: Should libburn, libisofs, and libisoburn get the same change ?

Libraries are sually Multi-Arch: same, meaning they have to be the same
as the packages using them. That's actually already the case for
libburn, libisofs, and libisoburn.

Looking further: cdrskin, xorriso-tcltk, and xorriso-dd-target should
probably also be Multi-Arch: foreign.

Samuel

Bug#493526: exim4-config: mailname not automatically added to MAIN_LOCAL_DOMAINS

2022-09-16 Thread Arthur Marsh

Package: exim4-config
Version: 4.96-4
Followup-For: Bug #493526

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

See also bug #1019941 - by setting a "localhost" mail name and hence
/etc/mailname contained localhost rather than my isp's domain, local 
delivery finally started working again.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Exim version 4.96 #2 built 11-Sep-2022 11:38:26
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2022
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS TLS_resume move_frozen_messages DANE 
DKIM DNSSEC Event I18N OCSP PIPECONNECT PRDR Queue_Ramp SOCKS SRS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 external plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='smarthost'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1'
dc_readhost='internode.on.net'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.internode.on.net'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:localhost
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# options for daemon listening on port 25
SMTPLISTENEROPTIONS=''

-- System Information:
Debian Release: bookworm/sid
  APT prefers experimental
  APT policy: (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-rc5+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages exim4-config depends on:
ii  adduser3.129
ii  debconf [debconf-2.0]  1.5.79

Versions of packages exim4-config recommends:
ii  ca-certificates  20211016

exim4-config suggests no packages.

-- Configuration Files:
/etc/email-addresses changed:
amarsh04: arthur.ma...@internode.on.net
root: arthur.ma...@internode.on.net

/etc/exim4/exim4.conf.template changed:
AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS = true
exim_path = /usr/sbin/exim4
.ifndef CONFDIR
CONFDIR = /etc/exim4
.endif
UPEX4CmacrosUPEX4C = 1
domainlist local_domains = MAIN_LOCAL_DOMAINS
domainlist relay_to_domains = MAIN_RELAY_TO_DOMAINS
hostlist relay_from_hosts = MAIN_RELAY_NETS
.ifndef MAIN_PRIMARY_HOSTNAME_AS_QUALIFY_DOMAIN
.ifndef MAIN_QUALIFY_DOMAIN
qualify_domain = ETC_MAILNAME
.else
qualify_domain = MAIN_QUALIFY_DOMAIN
.endif
.endif
.ifdef MAIN_LOCAL_INTERFACES
local_interfaces = MAIN_LOCAL_INTERFACES
.endif
.ifndef LOCAL_DELIVERY
LOCAL_DELIVERY=mail_spool
.endif
gecos_pattern = ^([^,:]*)
gecos_name = $1
.ifndef MAIN_LOG_SELECTOR
MAIN_LOG_SELECTOR = +smtp_protocol_error +smtp_syntax_error 
+tls_certificate_verified +tls_peerdn
.endif

Bug#1019946: exim4-config_files.5.gz should mention /etc/mailname

2022-09-16 Thread Arthur Marsh

Package: exim4-config
Version: 4.96-4
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Local delivery of mail for root on this machine which was aliased to my
username on this machine was instead spamming my ISP, due to 
setting the mail name and hence /etc/mailname to the domain of my ISP-based
email address instead of localhost

The manual page /usr/share/man/man5/exim4-config_files.5.gz should include
and explain /etc/mailname

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Exim version 4.96 #2 built 11-Sep-2022 11:38:26
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2022
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS TLS_resume move_frozen_messages DANE 
DKIM DNSSEC Event I18N OCSP PIPECONNECT PRDR Queue_Ramp SOCKS SRS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 external plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='smarthost'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1'
dc_readhost='internode.on.net'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.internode.on.net'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:localhost
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# options for daemon listening on port 25
SMTPLISTENEROPTIONS=''

-- System Information:
Debian Release: bookworm/sid
  APT prefers experimental
  APT policy: (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-rc5+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages exim4-config depends on:
ii  adduser3.129
ii  debconf [debconf-2.0]  1.5.79

Versions of packages exim4-config recommends:
ii  ca-certificates  20211016

exim4-config suggests no packages.

-- Configuration Files:
/etc/email-addresses changed:
amarsh04: arthur.ma...@internode.on.net
root: arthur.ma...@internode.on.net

/etc/exim4/exim4.conf.template changed:
AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS = true
exim_path = /usr/sbin/exim4
.ifndef CONFDIR
CONFDIR = /etc/exim4
.endif
UPEX4CmacrosUPEX4C = 1
domainlist local_domains = MAIN_LOCAL_DOMAINS
domainlist relay_to_domains = MAIN_RELAY_TO_DOMAINS
hostlist relay_from_hosts = MAIN_RELAY_NETS
.ifndef MAIN_PRIMARY_HOSTNAME_AS_QUALIFY_DOMAIN
.ifndef MAIN_QUALIFY_DOMAIN
qualify_domain = ETC_MAILNAME
.else
qualify_domain = MAIN_QUALIFY_DOMAIN
.endif
.endif
.ifdef MAIN_LOCAL_INTERFACES
local_interfaces = MAIN_LOCAL_INTERFACES
.endif
.ifndef LOCAL_DELIVERY
LOCAL_DELIVERY=mail_spool
.endif
gecos_pattern =

Bug#1019945: python3-numba must depend on python3-llvmlite (>= 0.39)

Package: python3-numba
Version: 0.56.2+dfsg-1
Severity: serious
Control: block 1018786 by -1

https://ci.debian.net/data/autopkgtest/testing/amd64/n/numba/26144527/log.gz

...
autopkgtest [20:15:06]: test python3-numba: [---
[*] Testing with python3.10:
Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 187, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib/python3.10/runpy.py", line 110, in _get_module_details
__import__(pkg_name)
  File "/usr/lib/python3/dist-packages/numba/__init__.py", line 210, in 
_ensure_llvm()
  File "/usr/lib/python3/dist-packages/numba/__init__.py", line 117, in 
_ensure_llvm
raise ImportError(msg)
ImportError: Numba requires at least version 0.39.0 of llvmlite.
Installed version is 0.38.1.
Please update llvmlite.
autopkgtest [20:15:07]: test python3-numba: ---]
autopkgtest [20:15:07]: test python3-numba:  - - - - - - - - - - results - - - 
- - - - - - -
python3-numbaFAIL non-zero exit status 1
...

Bug#1019944: wireplumber: Upgradeing to 0.4.11-5 breaks restoring the target of a stream if it is not the default stream

2022-09-16 Thread Matthias Heinz

Package: wireplumber
Version: 0.4.11-3
Severity: important
X-Debbugs-Cc: m...@familie-heinz.name


Hi,

after upgrade wireplumber from 0.4.11-3 to 0.4.11-5 it fails to somehow realize
what the target of the last stream was, if it was not the default device.
pavucontrol just reports it as "Unknown output" then.

Downgrading to 0.4.11-3 fixes this.



Best regards
Matthias


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
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 wireplumber depends on:
ii  init-system-helpers   1.64
ii  libc6 2.34-8
ii  libglib2.0-0  2.73.3-3
ii  libpipewire-0.3-0 0.3.57-1
ii  libwireplumber-0.4-0  0.4.11-3
ii  pipewire  0.3.57-1

Versions of packages wireplumber recommends:
ii  pipewire-pulse  0.3.57-1

Versions of packages wireplumber suggests:
pn  libspa-0.2-bluetooth  

-- no debconf information

Bug#908894: [Debian lazygit] Go-team lazygit repo conflict issue

2022-09-16 Thread guilherme.lnx

st of all congratulations for all the  if you still intend to package Lazygit? 
done to bring Lazygit to Debian. guys,

First of all congratulations for all the work e interested I can put you as 
uploaders. to bring Lazygit to
Debian.

I wonder if you still intend to package Lazygit?
If not, I would like to continue packaging this program.

If you are interested I can put you as uploaders.
My idea is to keep this pack on the GO team.

It would be a pleasure to work together.

---
Best,
Guilherme

Bug#1019942: pacpl: has unnecessary dependency; please update package's dependencies

2022-09-16 Thread Thomas Uhle


Package: pacpl
Version: 6.1.2-2
Severity: normal

Dear maintainer,

by installing pacpl, also libcddb-perl was to be installed but has never 
been used.  pacpl uses libcddb-get-perl instead that was also installed. 
So could you please update debian/control and drop libcddb-perl from 
dependencies.


Thank you in advance!

Best regards,

Thomas Uhle


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.10.0-17-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pacpl depends on:
ii  libaudio-flac-header-perl 2.4-3+b3
ii  libaudio-scan-perl1.01-1+b3
ii  libcddb-perl  1.222-1.1
ii  libcddb-get-perl  2.28-3
ii  libmp3-tag-perl   1.13-1.2
ii  libparallel-forkmanager-perl  2.02-1
ii  libstring-shellquote-perl 1.04-1
ii  perl  5.32.1-4+deb11u2
ii  vorbis-tools  1.4.0-11+b1

Version of packages pacpl recommends:
ii  cdparanoia3.10.2+debian-13.1
ii  faad  2.10.0-1
ii  ffmpeg10:4.4.2-dmo0~bpo11+3
ii  flac  1.3.3-2+deb11u1
ii  lame  1:3.100-dmo2
un  mplayer   
un  musepack-tools
ii  normalize-audio   0.7.7-16
ii  opus-tools0.1.10-1
ii  sndfile-programs  1.0.31-2
un  sox   
un  speex 
un  wavpack   

Version of packages pacpl suggests:
un  faac 
un  flake
un  twolame

Bug#1019941: exim4-config: mail name explanation in dpkg-reconfigure script is confusing

2022-09-16 Thread Arthur Marsh

Package: exim4-config
Version: 4.96-4
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

The text box information for 'mail name' which sets /etc/mailname is
confusing:

The 'mail name' is the domain name used to 'qualify' mail addresses   │ 
 │ without a domain name.│ 
 │   │ 
 │ This name will also be used by other programs. It should be the single,   │ 
 │ fully qualified domain name (FQDN).   │ 
 │   │ 
 │ Thus, if a mail address on the local host is f...@example.org, the │ 
 │ correct value for this option would be example.org.   │ 
 │   │ 
 │ This name won't appear on From: lines of outgoing messages if rewriting   │ 
 │ is enabled.   │ 
 │   │ 
 │ System mail name:  


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

After incorrectly setting the 'mail name' in the text box to blank and
getting errors, re-running dpkg-reconfigure exim4-conf correctly put
in 'localhost' which should have been there in the first place to enable
local delivery (e.g. messages to root which I have redirected in /etc/aliases
to my username on my local system, amarsh04)

FINALLY, again I have the messages to root hitting my local mail folder
and not spamming my ISP.

Perhaps the text should say, "for local delivery without going through a
smarthost, set mail name to localhost"?

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Exim version 4.96 #2 built 11-Sep-2022 11:38:26
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2022
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS TLS_resume move_frozen_messages DANE 
DKIM DNSSEC Event I18N OCSP PIPECONNECT PRDR Queue_Ramp SOCKS SRS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 external plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='smarthost'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1'
dc_readhost='internode.on.net'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.internode.on.net'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:localhost
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# options for daemon listening on port 25
SMTPLISTENEROPTIONS=''

-- System Information:
Debian Release: bookworm/sid
  APT prefers experimental

Bug#1019940: Update to the current upstream version

2022-09-16 Thread Sebastien Bacher


Package: iio-sensor-proxy
Version: 3.0-2
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

The patch is based on the update in Ubuntu.

You could perhaps also consider moving the package to be team maintained 
(pkg-gnome for example)?


Thanks,
diff -Nur iio-sensor-proxy-3.0/debian/changelog iio-sensor-proxy-3.4/debian/changelog
--- iio-sensor-proxy-3.0/debian/changelog	2021-01-29 08:05:45.0 +0100
+++ iio-sensor-proxy-3.4/debian/changelog	2022-09-16 19:22:55.209417249 +0200
@@ -1,3 +1,17 @@
+iio-sensor-proxy (3.4-1) UNRELEASED; urgency=medium
+
+  * New upstream version
+  * debian/control: 
+- build-depends on libpolkit-gobject-1-dev
+- updated libgudev requirement
+- updated Build-Depends for the new integration tests
+  * debian/patches/proximity-Get-near-level-from-sysfs-if-available.patch,
+debian/patches/build_older_polkit.patch:
+- remove patch upstream, add one to allow building with the
+  unstable polkit version
+
+ -- Sebastien Bacher   Fri, 16 Sep 2022 19:09:35 +0200
+
 iio-sensor-proxy (3.0-2) unstable; urgency=medium
 
   [ Ritesh Raj Sarraf ]
diff -Nur iio-sensor-proxy-3.0/debian/control iio-sensor-proxy-3.4/debian/control
--- iio-sensor-proxy-3.0/debian/control	2021-01-29 08:05:45.0 +0100
+++ iio-sensor-proxy-3.4/debian/control	2022-09-16 19:19:25.452184127 +0200
@@ -4,11 +4,19 @@
 Maintainer: Ritesh Raj Sarraf 
 Build-Depends:
 	debhelper-compat (= 12),
-	libgudev-1.0-dev,
+	libgudev-1.0-dev (>= 1:237),
+	libpolkit-gobject-1-dev,
+	libudev-dev,
 	udev,
 	systemd,
 	gtk-doc-tools (>= 1.0),
-	libgtk-3-dev
+	libgtk-3-dev,
+	meson,
+	gir1.2-umockdev-1.0,
+	python3-dbusmock,
+	python3-gi,
+	python3-psutil,
+	umockdev,
 Standards-Version: 4.5.1
 Rules-Requires-Root: no
 Homepage: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy
diff -Nur iio-sensor-proxy-3.0/debian/files iio-sensor-proxy-3.4/debian/files
--- iio-sensor-proxy-3.0/debian/files	1970-01-01 01:00:00.0 +0100
+++ iio-sensor-proxy-3.4/debian/files	2022-09-16 19:23:01.329335672 +0200
@@ -0,0 +1 @@
+iio-sensor-proxy_3.4-1_source.buildinfo utils optional
diff -Nur iio-sensor-proxy-3.0/debian/patches/build_older_polkit.patch iio-sensor-proxy-3.4/debian/patches/build_older_polkit.patch
--- iio-sensor-proxy-3.0/debian/patches/build_older_polkit.patch	1970-01-01 01:00:00.0 +0100
+++ iio-sensor-proxy-3.4/debian/patches/build_older_polkit.patch	2022-09-16 19:18:08.501181948 +0200
@@ -0,0 +1,29 @@
+Index: iio-sensor-proxy-3.4/src/iio-sensor-proxy.c
+===
+--- iio-sensor-proxy-3.4.orig/src/iio-sensor-proxy.c
 iio-sensor-proxy-3.4/src/iio-sensor-proxy.c
+@@ -33,6 +33,13 @@
+ 
+ #define NUM_SENSOR_TYPES DRIVER_TYPE_PROXIMITY + 1
+ 
++/* This uses a weird Auto prefix to avoid conflicts with later added polkit types. */
++typedef PolkitAuthorizationResult AutoPolkitAuthorizationResult;
++typedef PolkitSubject AutoPolkitSubject;
++
++G_DEFINE_AUTOPTR_CLEANUP_FUNC (AutoPolkitAuthorizationResult, g_object_unref)
++G_DEFINE_AUTOPTR_CLEANUP_FUNC (AutoPolkitSubject, g_object_unref)
++
+ typedef struct {
+ 	GMainLoop *loop;
+ 	GUdevClient *client;
+@@ -437,8 +444,8 @@ check_claim_permission (SensorData   *da
+ 			GError  **error)
+ {
+ 	g_autoptr(GError) local_error = NULL;
+-	g_autoptr(PolkitAuthorizationResult) result = NULL;
+-	g_autoptr(PolkitSubject) subject = NULL;
++	g_autoptr(AutoPolkitAuthorizationResult) result = NULL;
++	g_autoptr(AutoPolkitSubject) subject = NULL;
+ 
+ 	subject = polkit_system_bus_name_new (sender);
+ 	result = polkit_authority_check_authorization_sync (data->auth,
diff -Nur iio-sensor-proxy-3.0/debian/patches/proximity-Get-near-level-from-sysfs-if-available.patch iio-sensor-proxy-3.4/debian/patches/proximity-Get-near-level-from-sysfs-if-available.patch
--- iio-sensor-proxy-3.0/debian/patches/proximity-Get-near-level-from-sysfs-if-available.patch	2021-01-28 16:22:11.0 +0100
+++ iio-sensor-proxy-3.4/debian/patches/proximity-Get-near-level-from-sysfs-if-available.patch	1970-01-01 01:00:00.0 +0100
@@ -1,31 +0,0 @@
-From: Your Name 
-Date: Wed, 25 Mar 2020 11:59:03 +0100
-Subject: proximity: Get near-level from sysfs if available
-MIME-Version: 1.0
-Content-Type: text/plain; charset="utf-8"
-Content-Transfer-Encoding: 8bit
-
-DT based devices can set the near-level via sysfs. Parse it from
-there too.
-
-Signed-off-by: Guido Günther 
-Closes: #297
-(cherry picked from commit ed427251b703dc832a2051b5e4bdd1b51b99b115)

- src/drv-iio-poll-proximity.c | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/src/drv-iio-poll-proximity.c b/src/drv-iio-poll-proximity.c
-index 98bacb1..432cda5 100644
 a/src/drv-iio-poll-proximity.c
-+++ b/src/drv-iio-poll-proximity.c
-@@ -100,6 +100,9 @@ get_near_level (GUdevDevice *device)
- 	gint near_level;
- 
- 	near_level = g_udev_device_get_property_as_int (device, PROXIMITY_NEAR_LEVEL);
-+

Bug#1016299: mkautodoc: diff for NMU version 0.1.0-3.1

Control: tags 1016299 + patch
Control: tags 1016299 + pending

Dear maintainer,

I've prepared an NMU for mkautodoc (versioned as 0.1.0-3.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru mkautodoc-0.1.0/debian/changelog mkautodoc-0.1.0/debian/changelog
--- mkautodoc-0.1.0/debian/changelog	2021-02-01 02:54:41.0 +0200
+++ mkautodoc-0.1.0/debian/changelog	2022-09-16 20:17:48.0 +0300
@@ -1,3 +1,10 @@
+mkautodoc (0.1.0-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Backport upstream fix for Markdown 3.4. (Closes: #1016299)
+
+ -- Adrian Bunk   Fri, 16 Sep 2022 20:17:48 +0300
+
 mkautodoc (0.1.0-3) unstable; urgency=medium
 
   * debian/control
diff -Nru mkautodoc-0.1.0/debian/patches/markdown-etree.patch mkautodoc-0.1.0/debian/patches/markdown-etree.patch
--- mkautodoc-0.1.0/debian/patches/markdown-etree.patch	1970-01-01 02:00:00.0 +0200
+++ mkautodoc-0.1.0/debian/patches/markdown-etree.patch	2022-09-16 20:15:04.0 +0300
@@ -0,0 +1,39 @@
+diff --git a/mkautodoc/extension.py b/mkautodoc/extension.py
+index 86e70b3..64fe7fa 100644
+--- a/mkautodoc/extension.py
 b/mkautodoc/extension.py
+@@ -1,7 +1,7 @@
+ from markdown import Markdown
+ from markdown.extensions import Extension
+ from markdown.blockprocessors import BlockProcessor
+-from markdown.util import etree
++from xml.etree import ElementTree as etree
+ import importlib
+ import inspect
+ import re
+diff --git a/requirements.txt b/requirements.txt
+index 67ec1b1..8a7d94c 100644
+--- a/requirements.txt
 b/requirements.txt
+@@ -1,4 +1,4 @@
+-markdown
++-e .
+ 
+ # Testing
+ black
+diff --git a/setup.py b/setup.py
+index 8cb3b5b..8be283f 100644
+--- a/setup.py
 b/setup.py
+@@ -37,7 +37,7 @@ setup(
+ author='Tom Christie',
+ author_email='t...@tomchristie.com',
+ packages=get_packages('mkautodoc'),
+-install_requires=[],
++install_requires=["Markdown"],
+ python_requires='>=3.6',
+ classifiers=[
+ 'Development Status :: 3 - Alpha',
+-- 
+2.30.2
+
diff -Nru mkautodoc-0.1.0/debian/patches/series mkautodoc-0.1.0/debian/patches/series
--- mkautodoc-0.1.0/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ mkautodoc-0.1.0/debian/patches/series	2022-09-16 20:17:45.0 +0300
@@ -0,0 +1 @@
+markdown-etree.patch

Bug#1016599: mayavi2: vtk[6,7] removal

On Wed, Aug 03, 2022 at 10:39:53PM +0200, Sebastian Ramacher wrote:
> Source: mayavi2
> Version: 4.8.0-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> Tags: sid bookworm
> Control: block 1016597 by -1
> User: gl...@debian.org
> Usertags: vtk6_vtk7_removal
> 
> Based on #1013156 and similar bugs:
> 
> Dear maintainer,
> 
> Debian archive has now three major versions of the VTK (The
> Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions
> (vtk6 and vtk7) are not supported by upstream and the package itself
> is not easy for the mainance.
> 
> We aim to drop old and deprecated version vtk6 and vtk7 packages before
> the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or
> vtk7. Thus we ask you to migrate it to the latest vtk9 package.

Upstream seems to somehow support vtk9:
https://github.com/enthought/mayavi/pull/1159

Trying to build the package in unstable with build + runtime 
dependencies changed to python3-vtk9 works, and in the testsuite
this fixes "FAIL: test_basic_vtk" while not causing any regressions.

> Cheers

cu
Adrian

Bug#1019939: fwupd: Not well documented, what does it actually do on Debian systems?

2022-09-16 Thread J. Pfennig

Package: fwupd
Version: 1.8.4-2
Severity: minor

Dear Maintainer,

A few days ago we had press reports about updates from a specific os
vendor that made some linux machines unbootable. Although that the 
vendor was probably well minded, this was problematic.

Today, at login I had a motd message from fwupd reminding me of a very
similar (or the same update) on my linux systems. Some user might have
installed it already accidentially via discover.

At this point I was looking for documentation about fwupd (mostly I knew
about it via phoronix.com telling me how great is is). But there is very
little to find in the internet (an outdated ubuntu page, or some arch
linux doc). Debian neither provides sufficient documentation.

Having in mind, that this february a satelite network provider
distrubuted a malicious firmware update that destroied thousands of
satelite modems, I choose the uninstall fwupdate on all machines.

Please:

The fwupdt package is very invasive and might be used maliciously. At
least it should be documented in an understandable way or should be
disabled by default.

It should not be used for automatic updates that can be triggered
by unexperienced users (like in discover) at all.

Yours Jürgen

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
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)

Versions of packages fwupd depends on:
ii  libc6  2.34-7
ii  libcurl3-gnutls7.85.0-1
ii  libefiboot137-6
ii  libelf10.187-2
pn  libflashrom1   
ii  libfwupd2  1.8.4-2
pn  libfwupdplugin1
pn  libfwupdplugin7
ii  libglib2.0-0   2.73.3-3
ii  libgnutls303.7.7-2
ii  libgudev-1.0-0 237-2
ii  libgusb2   0.3.10-1
ii  libjcat1   0.1.9-1
ii  libjson-glib-1.0-0 1.6.6-1
ii  libmbim-glib4  1.26.4-1
ii  libmbim-proxy  1.26.4-1
ii  libmm-glib01.18.10-2
ii  libpolkit-gobject-1-0  0.105-33
ii  libprotobuf-c1 1.4.1-1
ii  libqmi-glib5   1.30.8-1
ii  libqmi-proxy   1.30.8-1
pn  libsmbios-c2   
ii  libsqlite3-0   3.39.3-1
ii  libsystemd0251.4-3
ii  libtss2-esys-3.0.2-0   3.2.0-1+b1
pn  libxmlb1   
ii  libxmlb2   0.3.8-1
ii  shared-mime-info   2.2-1

Versions of packages fwupd recommends:
pn  bolt   
ii  dbus   1.14.0-2
pn  fwupd-signed   
pn  jq 
ii  python33.10.6-1
pn  secureboot-db  
ii  udisks22.9.4-3

Versions of packages fwupd suggests:
pn  gir1.2-fwupd-2.0

Bug#1016863: libreoffice: Bad performance especially when dealing with pictures

2022-09-16 Thread Boh Boh

I'm using LxQt and I manually installed libreoffice-gtk3 and it was
automatically enabled, and I couldn't find any way to enable
libreoffice-qt5.

By using backports everything seems to work fine also with
libreoffice-gtk3, but with it installed the Skia rendering backend isn't
available in the options. Also I still not be able to use libreoffice-qt5
(which now isn't a big deal since the gtk3 doesn't blow up my PC).
Thank you for helping!

Regards,
Matteo.

Il giorno lun 8 ago 2022 alle ore 21:41 Rene Engelhard  ha
scritto:

> Hi again,
>
> Am 08.08.22 um 14:10 schrieb Matteo A.:
> > Also installing libreoffice-qt5 the look doesn't change.
>
> Oh, and this actually is completely expected. It only gets c hoosen per
> default if your desktop is KDE (well, kf5 which bases on it). As gtk3
> gets choosen for you per default that isn't the case. You can set it
> though:
>
> cf. e.g. https://wiki.archlinux.org/title/LibreOffice#Theme
>
> Regards,
>
> Rene
>
>

Bug#1019937: elfutils: Missing licenses in d/copyright

Source: elfutils
Severity: serious
Version: 0.187-2

elfutils' debian/copyright file is missing at least the BSD-2-clause license
and the GFDL-NIV-1.3 license.
Please find a machine-readable copyright file attached that includes them.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: This package was debianized by Kurt Roeckx .
Source: https://sourceware.org/elfutils/ftp/

Files: *
debuginfod/debuginfod-find.c
Copyright: (C) 1996-2019 Red Hat, Inc.
(C) 2022 Mark J. Wielaard
(C) 2015, 2016 Oracle, Inc.
(C) 2017 The Qt Company
(C) 2018, 2021 Facebook, Inc.
(C) 2021 Runsafe Security, Inc.
(C) H.J. Lu , 2015.
(C) 2020 Tom Tromey
Comment: Written by:
Ulrich Drepper
Jeff Johnson
Alexander Larsson
Jakub Jelinek
Roland McGrath .
See more in the AUTHORS file.
License: GPL-3+

Files: backends/*
config/*
debuginfod/*
lib*
version.h
debian/patches/mips_cfi.patch
Copyright: (C) 1996-2019 Red Hat, Inc.
(C) 2021, 2022 Mark J. Wielaard
(C) 2015 Oracle, Inc.
(C) 2016, 2017 The Qt Company Ltd.
(C) 2021 Google, Inc.
(C) 2012 Tilera Corporation
(C) 2019 Hangzhou C-SKY Microsystems co.,ltd.
(C) H.J. Lu , 2015.
(c) 2021 Dmitry V. Levin
(C) 2018 Sifive, Inc.
(C) 2018 Kurt Roeckx, Inc.
Comment: Most of the libraries (lib, libelf, libebl, libdw, libdwfl) have
the following license:
License: LGPL-3+ or GPL-2+
This file is free software; you can redistribute it and/or modify
it under the terms of either
.
* the GNU Lesser General Public License as published by the Free
Software Foundation; either version 3 of the License, or (at
your option) any later version
.
or
.
* the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at
your option) any later version
.
or both in parallel, as here.
.
elfutils is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
.
You should have received copies of the GNU General Public License and
the GNU Lesser General Public License along with this program. If
not, see .
Comment:
On Debian GNU/Linux systems, the complete text of the GNU General
Public License version 2 can be found in
`/usr/share/common-licenses/GPL-2' and the complete text of the GNU
Lesser General Public License version 3 can be found in
`/usr/share/common-licenses/LGPL-3'.

Files: lib/stdatomic-fbsd.h
Copyright: (c) 2011 Ed Schouten
David Chisnall
All rights reserved.
License: BSD-2-clause
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

Files: doc/readelf.1
Copyright: (c) 1991\-2018 Free Software Foundation, Inc.
(c) 2019 Red Hat Inc.
License: GFDL-NIV-1.3
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, with no Front-Cover Texts, and with no
Back-Cover Texts. A copy of the license is included in the
section entitled "GNU Free Documentation License".
Comment:
On Debian GNU/Linux systems, the complete text of the GNU
Free Documentation License version 1.3 can be found in
`/usr/share/common-licenses/GFDL-1.3'

Files: libelf/dl-hash.h
libelf/elf.h
Copyright: (C) 1995-2022 Free Software Foundation, Inc.
Comment: This file

Bug#1019936: r-cran-tmb must depend on the exact upstream version of r-cran-matrix it was built with or drop the warning

Package: r-cran-tmb
Version: 1.9.1-1
Severity: serious
Control: affects -1 r-cran-glmmtmb src:r-cran-glmmtmb
Control: block 1017626 by -1

> library(TMB)
Warning message:
In checkMatrixPackageVersion() : Package version inconsistency detected.
TMB was built with Matrix version 1.4.1
Current Matrix version is 1.5.1
Please re-install 'TMB' from source using install.packages('TMB', type = 
'source') or ask CRAN for a binary version of 'TMB' matching CRAN's 'Matrix' 
package
>

This is also causing autopkgtest failures:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tmb/26168759/log.gz

Bug#1019935: xorriso: Please make Multi-Arch: foreign

2022-09-16 Thread Thomas Schmitt

Hi,

such Debian specifics are more a matter of my sponsor's opinion than
of my own. Cc-ing Dominique Dumont, therefore.

Samuel Thibault wrote:
> Since AIUI the xorriso package provides only a tool whose behavior is
> exactly the same on all architectures,

It depends on libburn which behaves different on Hurd compared to Linux.
On Linux it can operate optical drive by SCSI passthrough (SG_IO).
On Hurd it cannot (and i am not aware of a passthrough opportunity there).
Another dependency, libisofs, shows differences when it comes to reading
or writing ACL and xattr.

The use case of creating bootable ISO images is normally not affected by
these differences.

> could you make it
> Multi-Arch: foreign
> so that the Debian Installer can use it as foreign dependency for
> cross-builds?

Is the described situation still suitable for Multi-Arch: foreign ?
If so: Should libburn, libisofs, and libisoburn get the same change ?

Have a nice day :)

Thomas

Bug#1019935: xorriso: Please make Multi-Arch: foreign

Package: xorriso
Version: 1.5.4-2
Severity: normal

Hello,

Since AIUI the xorriso package provides only a tool whose behavior is
exactly the same on all architectures, could you make it

Multi-Arch: foreign

so that the Debian Installer can use it as foreign dependency for
cross-builds?

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Versions of packages xorriso depends on:
ii  libburn4 1.5.4-1
ii  libc62.34-7
ii  libisoburn1  1.5.4-2
ii  libisofs61.5.4-1

xorriso recommends no packages.

Versions of packages xorriso suggests:
pn  cdck   
pn  jigit  
pn  xorriso-tcltk  

-- no debconf information

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#898058: genisoimage: Please make Multi-Arch: foreign

Hello,

Francois Gouget, le dim. 06 mai 2018 06:59:28 -0400, a ecrit:
> brasero-cdrkit and libguestfs0 are Multi-Arch: same but depend on genisoimage 
> because they need to run the tools it provides. This is ok but can only work 
> if 
> genisoimage is marked Multi-Arch: foreign.
> 
> Fortunately since genisoimage only provides tools that should be no issue.

Making genisoimage Multi-Arch: foreign would also allow the
debian-installer to be cross-built, see
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/24

Samuel

Bug#1019934: apt-get gets stuck on unreachable proxy for https sources

2022-09-16 Thread Martin Schmitt


Package: apt
Version: 2.5.2

Hey everyone,

I work in an environment with an APT mirror on the intranet, from where 
clients pull their regular updates.


The mirror is configured to be reached via the DIRECT pseudo proxy in 
apt.conf.d, while all 3rd party sources are supposed to be reached by an 
HTTP proxy, also configured in apt.conf.d.


The clients are at times not connected to the VPN or intranet, and 
there's a split-DNS wildcard record in place on the internet side of 
things (beyond my control something something Letsencrypt) that leads to 
them being redirected to a bogus central HTTPS homepage, which they then 
try to reach by proxy, although the proxy itself is not reachable from 
the outside. In this situation, scheduled update activity, mainly from 
packagekit.service or from apt-daily.timer, leads to eternal lock-ups of 
apt-get that won't ever recover on their own. The clients are then 
blocked from updating for as long as the stuck process remains active, 
until someone kills it manually or the system reboots.


Steps to reproduce:

I have set up an HTTP redirect on http://team-frickel.de/mirror/ that 
will redirect to a bogus https://example.com/mirror/:


RewriteEngine on
RewriteCond %{REQUEST_URI} ^/mirror/
RewriteRule /mirror/(.*) https://example.com/$1 [R,L]

On the client, two sources.list files have been prepared at non-standard 
locations:


/etc/apt/one-source.list:
deb http://team-frickel.de/mirror/ testing main

/etc/apt/two-sources.list:
deb http://team-frickel.de/mirror/ testing main
deb http://team-frickel.de/mirror/ testing-security main

Let's try updating using these lists, with an unresolvable default proxy 
for https.


Attempting an update from the one-source.list configuration fails 
gracefully and correctly complains about the unresolvable proxy:


# apt-get -o Dir::Etc::sourcelist=/etc/apt/one-source.list \
-o Acquire::https::proxy=http://proxy.invalid:3128 update
Ign:1 https://example.com testing InRelease
Ign:1 https://example.com testing InRelease
Ign:1 https://example.com testing InRelease
Err:1 https://example.com testing InRelease
  Could not resolve 'proxy.invalid'
Reading package lists... Done
W: Failed to fetch http://team-frickel.de/mirror/dists/testing/InRelease 
 Could not resolve 'proxy.invalid'
W: Some index files failed to download. They have been ignored, or old 
ones used instead.


Moving on to the two-sources.list configuration, the operation gets 
stuck at "0% [Working]" until interrupted:


# apt-get -o Dir::Etc::sourcelist=/etc/apt/two-sources.list \
-o Acquire::https::proxy=http://proxy.invalid:3128 update
Ign:1 https://example.com testing InRelease
0% [Working]

strace loops these lines while the process is stuck:

pselect6(7, [5 6], [], NULL, {tv_sec=0, tv_nsec=5}, NULL) = 0 
(Timeout)

rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
0% [Working])  = 1313

I believe this is a bug because if apt-get gracefully handles the error 
when operating on a single APT source, it would seem logical to not get 
stuck when operating on multiple sources.


The behaviour was initially observed on Ubuntu 22.04 (apt 2.4.7). It's 
not reproducible on Debian 11 (apt 2.2.4) and Ubuntu 20.04 (apt 2.0.9), 
but it is immediately reproducible on Debian Testing as of apt 2.5.2, 
which is why I'm reporting it as a Debian bug.


The changelog shows that there was work done on https proxy evaluation 
in apt 2.3.10 following bug #990555, so maybe this is a regression from 
that change.


The redirect URL used for testing is up and does not log IP addresses or 
any other client information.


Kind regards,

-martin

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

2022-09-16 Thread Maximilian Stein


> Some time after upgrading to 15.3.2 (but not from the beginning),
> loading of comments in merge requests started to fail.


Apparently, only merge requests with annotations in the diff view are 
affected. That's why I didn't notice the issue from the beginning.

Bug#1019554: Stamp files are not updated

2022-09-16 Thread Helge Kreutzmann

Hello Lance,
On Tue, Sep 13, 2022 at 12:22:07PM +, Lance Lin wrote:
> Thank you for your report. I'm happy to work on this.

I'll try to start anacron manually on Sunday. So if you want to
investigate anything before I do so, please let me know.

Greetings

   Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1019549: fetchmail: can't accept options while a background fetchmail is running.

2022-09-16 Thread Helge Kreutzmann

Hello László,
On Thu, Sep 15, 2022 at 08:32:29PM +0200, László Böszörményi (GCS) wrote:
> Fixed package which no longer enables systemd service for users is on its way.
> Thanks for the feedback,

Thank you very much for your professional and swift handling of this
issue.

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1019932: RFP: briar -- Briar Instant Messenger

2022-09-16 Thread Jeffrey Cliff

Package: wnpp
Severity: wishlist

* Package name: briar
  Upstream Author : Sublime Software Ltd
* URL : https://code.briarproject.org/briar/briar/tree/master
* License : GPLv3
  Programming Lang: java
  Description : Secure messaging, anywhere

Briar is a privacy-preserving, metadata-resistant instant messenger
platform, competitor to Signal ( #842943 ), Telegram/WhatsApp/Meta
Messenger/Slack ( #928708 ), and Cwtch ( #922887 ).  It is primarily
designed for Android but work is well under way to support Debian by
default ( https://code.briarproject.org/briar/briar/-/merge_requests/1252 ).

Bug#1019931: godot: New version of Godot has been released

2022-09-16 Thread Jonas Vejlin

Package: godot3
Version: 3.2.3-stable-1+b3
Severity: wishlist
File: godot
X-Debbugs-Cc: jonas.vej...@gmail.com

Dear Maintainer,

Godot 3.5 has been released a while back and Godot 4.0 beta 1 was released 
yesterday. It would be nice if those new version could be packaged for Debian 
sid and Debian experimental 

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

Kernel: Linux 5.19.0-1-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages godot3 depends on:
ii  libasound2 1.2.7.2-1
ii  libc6  2.34-8
ii  libenet7   1.3.13+ds-1
ii  libfreetype6   2.12.1+dfsg-3
ii  libgcc-s1  12.2.0-2
ii  libgl1 1.5.0-1
ii  libogg01.3.5-1
ii  libopus0   1.3.1-2
ii  libpcre2-32-0  10.40-1
ii  libpng16-161.6.37-5
ii  libpulse0  15.0+dfsg1-4+b1
ii  libsquish0 1.15-1+b11
ii  libstdc++6 12.2.0-2
ii  libtheora0 1.1.1+dfsg.1-16
ii  libvorbis0a1.3.7-1
ii  libvpx71.12.0-1
ii  libwebp7   1.2.2-2+b1
ii  libx11-6   2:1.8.1-2
ii  libxcursor11:1.2.1-1
ii  libxi6 2:1.8-1
ii  libxinerama1   2:1.1.4-3
ii  libxrandr2 2:1.5.2-2+b1
ii  libxrender11:0.9.10-1.1
ii  zlib1g 1:1.2.11.dfsg-4.1

godot3 recommends no packages.

godot3 suggests no packages.

-- no debconf information

Bug#1019930: newt: Several issues with copyright file


Source: newt
Severity: serious
Version: 0.52.21-5

newt's copyright file does not present the package's copyright in a fashion 
that is required by the Policy.
The copyright holder is not included from README (Red Hat) but from COPYING, 
which is the GPL's copyright holder.
The GPL-2+ license, which is applicable to some po files, is not mentioned.

Also, the referenced ftp and http resources are not available anymore.

Please find a machine-readable copyright file attached that fixes these issues.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment:
 This is the Debian version of the newt library.
 newt was written by Erik Troan .
 .
 The original package was put together by Enrique Zanardi .
Source: https://releases.pagure.org/newt/

Files: *
Copyright: (C) 1996-2016  Red Hat, Inc.
License: LGPL-2

Files: listbox.c
Copyright: (C) 1996, 1997 Elliot Lee
License: LGPL-2

Files: debian/patches/icelandic.patch
 po/ast.po   po/ca.popo/cs.popo/da.po
 po/de.popo/dz.popo/fr.popo/ga.po
 po/it.popo/ja.popo/eo.popo/es.po
 po/lt.popo/mr.popo/nb.popo/nds.po
 po/nn.popo/pt_BR.po po/sl.popo/sv.po
 po/vi.popo/zh_CN.po po/zh_TW.po
Copyright: (C) 2003-2006 Free Software Foundation, Inc.
License: LGPL-2

Files: po/tl.po
Copyright: (C) 2005 Eric Pareja
License: LGPL-2

Files: po/ms.po
Copyright: (C) Fedora Project
License: LGPL-2

Files: po/pt.po
Copyright: (C) 2003 Alastair McKinstry 
License: LGPL-2

Files: po/xh.po
Copyright: (C) 2005 Canonical Ltd.
License: LGPL-2

Files: debian/patches/kazakh.patch
Copyright: (C) 2010 HZ
Comment: This file is distributed under the same license as debian-installer.
License: GPL-2+

Files: po/ta.po  po/th.po
Copyright: (C) 2003, 2006 Software in the Public Interest, Inc.
Comment: This file is distributed under the same license as debian-installer.
License: GPL-2+

License: LGPL-2
 This library is free software; you can redistribute it and/or
 modify it under the terms of the GNU Library General Public
 License version 2 as published by the Free Software Foundation.
 .
 This library is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 Library General Public License for more details.
 .
 You should have received a copy of the GNU Library General Public
 License along with this library; if not, write to the Free Software
 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
 .
 newt is available under the terms of the GNU Library General Public
 License, version 2. On Debian GNU/Linux systems, the complete text of this
 license can be found in `/usr/share/common-licenses/LGPL-2'.

License: GPL-2+
 On Debian GNU/Linux systems, the complete text of this
 license can be found in `/usr/share/common-licenses/GPL-2'.

Bug#996663: minetest: English not visible in Japanese locale

Hi Jun-san,

Many thanks for your report and analyis!

I've tested the new upstream version 5.6.0, and it brings 
DroidSansFallbackFull.ttf,
I guess this issue has been fixed, at least I'm getting mixed Japenese and 
English text
in the UI, when I set LANG=ja_JP.UTF-8. But as I'm not speaking Japanese at 
all, this is
just a guess… 

The bug will will be closed with the upload I'm currenty preparing. Please feel 
free to
reopen the bug, if my guessing was wrong.

-- 
Cheers,
tobi

Bug#613997: gnome-games: Backtrace

2022-09-16 Thread Jeremy Bicha

On Fri, Sep 16, 2022 at 7:00 AM Chris Lamb  wrote:
>
> Tobias Hansen wrote:
>
> > I also get a segfault regardless of the locale. Gfx driver is intel.
> > However, when running with gdb the program doesn't crash. This is the 
> > output: [..]
>
> I also get a segfault regardless of locale, and I can reproduce the
> crash under gdb (see below). I therefore wonder whether this bug should
> have a higher severity?

Wow, you're replying today to a bug that hasn't been touched in a decade?

Are you able to report this issue upstream?
https://gitlab.gnome.org/GNOME/quadrapassel/-/issues

It's not clear what version of quadrapassel you're using and what the
steps to reproduce the bug are. Quadrapassel works for me in Spanish.

Thank you,
Jeremy Bicha

Bug#1019929: podman: Subordinate UID/GID ranges not fetched from libsubid

2022-09-16 Thread Sam Morris

Package: podman
Version: 4.2.0+ds1-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I've not got anything in /etc/subuid or /etc/subgid because subordinate
id range info is stored in LDAP.

  $ grep ^subid: /etc/nsswitch.conf
  subid: sss

This is transparent to clients using libsubid:

  $ getsubids sam
  0: sam 2147483648 65536

... but it looks like podman doesn't use this library yet:

$ podman system info
ERRO[] cannot find UID/GID for user sam: no subuid ranges found for 
user "sam" in /etc/subuid - check rootless mode in man pages.
WARN[] Using rootless single mapping into the namespace. This might 
break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not 
using a network user
[...]
  idMappings:
gidmap:
- container_id: 0
  host_id: 1000
  size: 1
uidmap:
- container_id: 0
  host_id: 1000
  size: 1
[...]

- -- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii  conmon   2.1.3+ds1-1
ii  crun 1.5+dfsg-1+b1
ii  golang-github-containers-common  0.48.0+ds1-1
ii  libc62.34-7
ii  libdevmapper1.02.1   2:1.02.185-1
ii  libgpgme11   1.17.1-4.1
ii  libseccomp2  2.5.4-1+b1
ii  systemd [systemd-tmpfiles]   251.4-3

Versions of packages podman recommends:
ii  buildah1.26.1+ds1-1
ii  catatonit  0.1.7-1
ii  dbus-user-session  1.14.0-2
ii  fuse-overlayfs 1.9-1
ii  slirp4netns1.2.0-1
ii  uidmap 1:4.11.1+dfsg1-2

Versions of packages podman suggests:
ii  containers-storage  1.37.2+ds1-1+b2
pn  docker-compose  
ii  iptables1.8.8-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIgEARYIADAWIQTWOGqGn6HETecdzqZOEaKLhlAYigUCYyRZrhIcc2FtQHJvYm90
cy5vcmcudWsACgkQThGii4ZQGIra+wEA9cSULDer04xzpg1djBcsaxdK78eH6avT
szoQ8hl2ERMA/08sN17EOvYQOLB8WwleW1kPCQZdDztMiapcY5Ep7CYI
=DI3R
-END PGP SIGNATURE-

Bug#1019928: ITP: python-phx-class-registry -- module to define global factories and service registries

2022-09-16 Thread Emanuele Rocca

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org

* Package name: python-phx-class-registry
  Version : 3.0.5
  Upstream Author : Phoenix Zerin 
* URL : https://github.com/todofixthis/class-registry
* License : MIT
  Programming Lang: Python
  Description : module to define global factories and service registries

At the intersection of the Registry and Factory patterns lies the
ClassRegistry.
.
This module allows to:
.
* Define global factories that generate new class instances based on
  configurable keys.
* Seamlessly create powerful service registries.
* Integrate with setuptools's entry_points system to make registries
  extensible by 3rd-party libraries.

---

The module is a dependency of backblaze-b2 since 3.5.0: 
https://bugs.debian.org/1019925

Bug#613997: gnome-games: Backtrace

2022-09-16 Thread Chris Lamb

Tobias Hansen wrote:

> I also get a segfault regardless of the locale. Gfx driver is intel.
> However, when running with gdb the program doesn't crash. This is the output: 
> [..]

I also get a segfault regardless of locale, and I can reproduce the
crash under gdb (see below). I therefore wonder whether this bug should
have a higher severity?



  
Thread 1 "quadrapassel" received signal SIGSEGV, Segmentation fault.
0x55567d87 in quadrapassel_key_press_event_cb (event=, 
widget=, self=0x55856310) at 
src/quadrapassel.p/quadrapassel.c:2611
Download failed: Invalid argument.  Continuing without source file 
./obj-x86_64-linux-gnu/src/quadrapassel.p/quadrapassel.c.
2611src/quadrapassel.p/quadrapassel.c: No such file or directory.
(gdb) bt
#0  0x55567d87 in quadrapassel_key_press_event_cb (event=, widget=, self=0x55856310) at 
src/quadrapassel.p/quadrapassel.c:2611
#1  _quadrapassel_key_press_event_cb_gtk_widget_key_press_event 
(_sender=, event=, self=0x55856310) at 
src/quadrapassel.p/quadrapassel.c:561
#2  0x773e9057 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x77a6a500 in g_closure_invoke () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x77a7db36 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x77a83eed in g_signal_emit_valist () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x77a8487f in g_signal_emit () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x77393554 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x772496ff in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x7724b066 in gtk_main_do_event () from 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x76b335a5 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#11 0x76b675b2 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#12 0x77972729 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x779729b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x77972a4c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x77d38d5d in g_application_run () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
#16 0xb509 in quadrapassel_main (args_length1=, 
args=) at src/quadrapassel.p/quadrapassel.c:3243
#17 main (argc=, argv=) at 
src/quadrapassel.p/quadrapassel.c:3253


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1019926: Fwd: Kernel incompatible with Intel Atom Processor (Coprocessor) driver C3758 / C3xxx

2022-09-16 Thread Christian Butterweck

Package:  linux-image-5.10.0-18-amd64
Version: 5.10.0-18-amd64

Problem: The system cannot reboot anymore because the kernel has a problem
unloading the coprocessor driver. Intel Atom Processor (Coprocessor) driver
C3758 / C3xxx

Reproducible: yes (fresh Debian debian-11.5.0-amd64-DVD-1.iso installation)
My motherboard is a MBN802 (you can search the specs with your favourite
search engine if you like).

After first installation i get:
[6.891481] c3xxx :01:00.0: Failed to load MMP firmware
qat_c3xxx_mmp.bin
[6.898666] c3xxx :01:00.0: Failed to load acceleration FW

To install this drivers i have to install them with:
cd /lib/firmware
wget
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_c3xxx.bin
wget
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_c3xxx_mmp.bin

After rebooting i can see them with:

modprobe -D qat_c3xxx
insmod /lib/modules/5.10.0-18-amd64/kernel/crypto/authenc.ko
insmod
/lib/modules/5.10.0-18-amd64/kernel/drivers/crypto/qat/qat_common/intel_qat.ko
insmod
/lib/modules/5.10.0-18-amd64/kernel/drivers/crypto/qat/qat_c3xxx/qat_c3xxx.ko

If i unload it manually i get "kernel tainted" and the system crashes:

modprobe --remove-dependencies -f qat_c3xxx
[  343.834657] qat_c3xxx: module_layout: kernel tainted.

My temporary solution is: Switch to Liquorix kernel. With kernel
5.19.0-9.1-liquorix-amd64 the drivers are running fine.
See howto at:
https://www.linuxcapable.com/how-to-install-liquorix-linux-kernel-on-debian-11-bullseye/

Maybe you can fix this bug in future versions and compare the difference
between the Liquorix and actual Debian kernel.

Thanks. Christian

Bug#1019925: backblaze-b2: new upstream 3.5.0 available

2022-09-16 Thread Emanuele Rocca

Source: backblaze-b2
Severity: wishlist

A new upstream version of backblaze-b2 is available:
https://github.com/Backblaze/B2_Command_Line_Tool/archive/refs/tags/v3.5.0.tar.gz

The new version depends on phx-class-registry, which is currently not
packaged in Debian. See https://github.com/todofixthis/class-registry

Bug#1019923: utf8proc: build-depends on unicode-data (< 14.1) but Unstable has 15.0.0-1

2022-09-16 Thread Jeremy Bicha

Source: utf8proc
Version: 2.7.0-3
Severity: serious
Tags: ftbfs upstream bookworm sid

This week, there is a new Unicode 15 release. In Debian, unicode-data
has been updated to 15.0.0. utf8proc needs to be updated to building
against the current unicode-data in Debian.

This issue was detected by failing autopkgtests triggered by the new
unicode-data release.

Thank you,
Jeremy Bicha

Bug#1019922: debian-archive-keyring: Machine-readable conversion


Source: debian-archive-keyring
Severity: wishlist
Version: 2021.1.1

The attached copyright file is converted to the machine-readable format.
Please consider to replace the copyright file in the package with it.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: This is Debian GNU's GnuPG keyrings of archive keys.

Files: *
Copyright: (none)
License: public-domain
 The keys in the keyrings don't fall under any copyright.
 Everything else in the package is covered by the GNU GPL.

Files: debian/*
   Makefile
   README*
Copyright: (C) 2006 Michael Vogt  
Comment: Debian support files are based on the debian-keyring package
 maintained by James Troup.
License: GPL-2+
 Debian support files for debian-archive-keyring are free software; you
 can redistribute them and/or modify them under the terms of the GNU
 General Public License as published by the Free Software Foundation;
 either version 2, or (at your option) any later version.
 .
 Debian support files for debian-archive-keyring are distributed in the
 hope that they will be useful, but WITHOUT ANY WARRANTY; without even
 the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
 PURPOSE.  See the GNU General Public License for more details.
 .
 You should have received a copy of the GNU General Public License with
 your Debian system, in /usr/share/common-licenses/GPL-2.
 If not, write to the Free Software Foundation, Inc., 51 Franklin Street,
 Fifth Floor, Boston, MA 02110-1301 USA.

Bug#1019921: Kernel incompatible with Intel Atom Processor (Coprocessor) driver C3758 / C3xxx

2022-09-16 Thread Christian Butterweck

Package: Debian Kernel
Version: 5.10.0-18-amd64

Problem: The system cannot reboot anymore because the kernel has a problem
unloading the coprocessor driver. Intel Atom Processor (Coprocessor) driver
C3758 / C3xxx

Reproducible: yes (fresh Debian debian-11.5.0-amd64-DVD-1.iso installation)
My motherboard is a MBN802 (you can search the specs with your favourite
search engine if you like).

After first installation i get:
[6.891481] c3xxx :01:00.0: Failed to load MMP firmware
qat_c3xxx_mmp.bin
[6.898666] c3xxx :01:00.0: Failed to load acceleration FW

To install this drivers i have to install them with:
cd /lib/firmware
wget
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_c3xxx.bin
wget
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_c3xxx_mmp.bin

After rebooting i can see them with:

modprobe -D qat_c3xxx
insmod /lib/modules/5.10.0-18-amd64/kernel/crypto/authenc.ko
insmod
/lib/modules/5.10.0-18-amd64/kernel/drivers/crypto/qat/qat_common/intel_qat.ko
insmod
/lib/modules/5.10.0-18-amd64/kernel/drivers/crypto/qat/qat_c3xxx/qat_c3xxx.ko

If i unload it manually i get "kernel tainted" and the system crashes:

modprobe --remove-dependencies -f qat_c3xxx
[  343.834657] qat_c3xxx: module_layout: kernel tainted.

My temporary solution is: Switch to Liquorix kernel. With kernel
5.19.0-9.1-liquorix-amd64 the drivers are running fine.
See howto at:
https://www.linuxcapable.com/how-to-install-liquorix-linux-kernel-on-debian-11-bullseye/

Maybe you can fix this bug in future versions and compare the difference
between the Liquorix and actual Debian kernel.

Thanks. Christian

Bug#1019920: openqa-client should probably depend on libcpanel-json-xs-perl

2022-09-16 Thread Holger Levsen

Package: openqa-client
Version: 4.6.1653336570.10bff0d-1
Severity: important

Dear Phil,

openqa-client should probably depend on libcpanel-json-xs-perl. Filing this
with severity 'important' as I'm not sure if there are situations where parts
of it are working without it.

https://jenkins.debian.net/view/live/job/reproducible_debian_live_build_smallest-build_sid/267/console

didn't have it  installed and failed with

Can't locate Cpanel/JSON/XS.pm in @INC (you may need to install the 
Cpanel::JSON::XS module) (@INC contains: /usr/share/openqa/script/../lib 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0 
/usr/local/share/perl/5.34.0 /usr/lib/x86_64-linux-gnu/perl5/5.34 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.34 /usr/share/perl/5.34 
/usr/local/lib/site_perl) at /usr/share/openqa/script/../lib/OpenQA/Command.pm 
line 7.
BEGIN failed--compilation aborted at 
/usr/share/openqa/script/../lib/OpenQA/Command.pm line 7.
Compilation failed in require at /usr/share/perl5/Mojo/Base.pm line 134.
BEGIN failed--compilation aborted at 
/usr/share/openqa/script/../lib/OpenQA/CLI/api.pm line 5.
Compilation failed in require at (eval 35) line 1.

openqa-cli there has been called like this:

openqa-cli api -X POST isos ISO=${DESKTOP}_${SUITE}_${TIMESTAMP}.iso 
DISTRI=debian VERSION=${SUITE}_${DESKTOP} FLAVOR=live-build ARCH=x86_64 
BUILD=:${SNAPSHOT_TIMESTAMP}_${SUITE}_${DESKTOP} CHECKSUM=${CHECKSUM} 
TIMESTAMP=${SNAPSHOT_TIMESTAMP} 
ISO_URL=https://tests.reproducible-builds.org/debian_live_build/${ISONAME} 
--odn --apikey ${OPENQA_APIKEY} --apisecret ${OPENQA_APISECRET} 
LIVE_INSTALLER=no

After installing libcpanel-json-xs-perl things work as they should.

Thanks for maintaining openqa in and for Debian!


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Die Faktenlage bzgl. Klimakatastrophe ist so eindeutig und die Folgen sind so
schwerwiegend, dass Parteien und Organisationen, die immer noch wirksame Maß-
nahmen dagegen behindern, als verbrecherisch einzustufen sind.


signature.asc
Description: PGP signature

Bug#989511: (no subject)

2022-09-16 Thread a...@prnet.info


I am seeing the same issue:

Sep 16 08:44:19 sddm-greeter[1596]: QFont::fromString: Invalid 
description '(empty)'

Sep 16 08:44:19 sddm[1448]: Message received from greeter: Connect
...
Sep 16 08:44:19 sddm-greeter[1596]: Loading 
file:///usr/share/sddm/themes/debian-theme/Main.qml...
Sep 16 08:44:19 upowerd[1672]: did not recognise USB path 
/sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001, 
please report
Sep 16 08:44:19 sddm-greeter[1596]: 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/SddmComponents/LayoutBox.qml:35:5: 
QML Connections: Implicitly defined onFoo properties in Connections are 
deprecated. Use this syntax instead: function on>

...
Sep 16 08:44:30 sddm-helper[2373]: [PAM] Conversation with 1 messages
Sep 16 08:44:30 sddm-helper[2373]: gkr-pam: unable to locate daemon 
control file
Sep 16 08:44:30 sddm-helper[2373]: gkr-pam: stashed password to try 
later in open session

Sep 16 08:44:30 sddm-helper[2373]: [PAM] returning.
Sep 16 08:44:30 sddm-helper[2373]: pam_kwallet5(sddm:auth): (null): 
pam_sm_authenticate

Sep 16 08:44:30 sddm[1448]: Authenticated successfully
Sep 16 08:44:30 sddm-greeter[1596]: Message received from daemon: 
LoginSucceeded


Debian (11, Bullseye) up to date, kernel 5.10.0-18-amd64, KDE desktop: 
5.20.5, qt 5.15.2


What needs to be done to get rid of this, to fix this?

Bug#1019742: reprotest: add a variation that sets DEB_BUILD_OPTIONS=nocheck

2022-09-16 Thread Mattia Rizzolo

On Thu, Sep 15, 2022 at 12:14:05PM +0200, Philip Hands wrote:
> BTW If someone can give me a hint where in the code one would define
> such a variation I'll cheerfully give it a go myself, but sadly it seems
> that my python is too weak to find the right spot for myself.

The variations are defined in reprotest/build.py (each variation is a
function) and listed in VARIATIONS.
Then __init__.py will pull them in with some magic.

Overall I don't consider this format particularly programmer-friendly.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1019919: cdebconf: Missing GPL-2+ license in d/copyright

Source: cdebconf
Severity: important
Version: 0.264

The debian/po/* files are licensed under debian-installer's license, which is
GPL-2+.
This license and some copyright statements are missing in your debian/copyright
file.
Please find a copyright file attached that fixes these issues and come in the
machine-readable format.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: CDebConf was initially written by Randolph Chung

Files: *
Copyright: 2000-2009 by Randolph Chung , the d-i team, and
Canonical Ltd.
Anthony Towns
David Whedon
Dan Jacobowitz
Tollef Fog Heen
Attilio Fiandrotti
Colin Watson
Regis Boudin
Comment: CDebConf includes ideas and code from:
debconf - The original, de facto, perl implementation
(c) Joey Hess
apt - The Debian Advanced Package Tool
(c) Jason Gunthorpe
(derived portions are public domain)
License: BSD-2-Clause

Files: debian/po/*
Copyright: 2003-2015, 2017-2018 Software in the Public Interest, Inc.
2000-2012 Free Software Foundation, Inc.
Comment: This file is distributed under the same license as debian-installer.
License: GPL-2+

Files: debian/po/pt.po
Copyright: 2003 Software in the Public Interest, Inc.
2003-2014 Miguel Figueiredo
License: GPL-2+

Files: debian/po/bg.po
Copyright: 2003 Software in the Public Interest, Inc.
2004, 2010 Free Software Foundation, Inc.
2004, 2005, 2006 Ognyan Kulev
2004 Nikola Antonov
2007 Tobias Quathamer
2001, 2004 Georgi Georgiev
2001 Alastair McKinstry
2004 Ognyan Kulev
2006, 2007, 2008, 2009, 2010 Damyan Ivanov
2010 Roumen Petrov
2006-2015, 2017 Damyan Ivanov
License: GPL-2+

Files: debian/po/oc.po
debian/po/kab.po
debian/po/te.po
Copyright: 2006, 2007, 2008 Canonical Ltd, and Rosetta Contributors
License: GPL-2+

Files: debian/po/de.po
Copyright: 2003 Software in the Public Interest, Inc.
2006, the console-setup package'c copyright holder
2006, Matthias Julius
2007-2009 Helge Kreutzmann
2008-2011 Holger Wansing
License: GPL-2+

Files: debian/po/pl.po
Copyright: 2003 Software in the Public Interest, Inc.
2004-2010 Bartosz Feński
License: GPL-2+

Files: debian/po/fi.po
Copyright: 2003 Software in the Public Interest, Inc.
2007 Tobias Toedter
2005-2006, 2008-2010 Free Software Foundation, Inc.
License: GPL-2+

Files: debian/po/ko.po
Copyright: 2003,2004,2005,2008 Software in the Public Interest, Inc.
2001 Alastair McKinstry
2004, 2008, 2009, 2010, 2011 Changwoo Ryu , .
2000, 2001, 2003 Free Software Foundation, Inc.
2001 Eungkyu Song
2001 Jaegeum Choe
2000 Kang, JeongHee
2006-2007 Sunjae Park
2007 Tobias Quathamer
License: GPL-2+

Files: debian/po/sr.po
Copyright: 2010-2012 Software in the Public Interest, Inc.
2008 THE cp6Linux'S COPYRIGHT HOLDER
2003, 2004 Free Software Foundation, Inc.
License: GPL-2+

License: BSD-2-clause
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
.
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
.
THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

License: GPL-2+
On Debian systems, the complete text of the GNU General
Public License version 2 can be found in "/usr/share/common-licenses/GPL-2".

Bug#961654: buster-pu: package bzip2/1.0.6-9.2~deb10u1

2022-09-16 Thread Santiago R.R.

El 16/09/22 a las 09:39, Emilio Pozuelo Monfort escribió:
> Hi Santiago,
> 
> On 15/09/2022 09:52, Emilio Pozuelo Monfort wrote:
> > On 14/09/2022 15:42, Santiago R.R. wrote:
> > > El 14/09/22 a las 13:58, Emilio Pozuelo Monfort escribió:
> > > > On 13/09/2022 16:46, Sylvain Beucler wrote:
> > > > > Hi,
> > > > > 
> > > > > IIUC this is about fixing 2 non-security bugs, that were introduced
> > > > > prior to buster's initial release.
> > > > > 
> > > > > I personally don't think this fits the LTS project scope.
> > > > > Maybe other LTS members will have a different opinion.
> > > > 
> > > > We've had bugfix updates from time to time. They are rare, but not
> > > > forbidden. This should go in a buster suite rather than 
> > > > buster-security, but
> > > > since there's no such suite for LTS, having it in buster-security is the
> > > > lesser evil. Of course we shouldn't flood -security with bug fixes, if 
> > > > that
> > > > was necessary we should consider keeping $stable open and handled by 
> > > > the LTS
> > > > team (but that doesn't seem necessary at this point).
> > > > 
> > > > In this case, since the update has been prepared and looks sensible, 
> > > > I'll go
> > > > ahead with the upload if nobody objects.
> > > > 
> > > 
> > > Thanks, Emilio. Also consider
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961654#15
> > > 
> > > Haven't tested yet myself. But I suppose I should apply it in unstable.
> > 
> > For buster I'd rather use what was proposed for buster-pu, as that's
> > also what is in bullseye.
> 
> I have uploaded that, with a s/buster/&-security/ in d/changelog, and fixing
> your name to be UTF-8.

Thanks!

,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1019918: plasma-workspace-wayland: xdg-desktop-portal-kde should be a dependence for the KDE Wayland session

2022-09-16 Thread Frédéric Parrenin

Package: plasma-workspace-wayland
Version: 4:5.25.4-3
Severity: normal
X-Debbugs-Cc: frederic.parre...@univ-grenoble-alpes.fr

Dear Maintainer,

When installing plasma-workspace-wayland for the KDE wayland session, the xdg-
desktop-portal-kde package is not installed by default.
As a consequence, the screen sharing functionnality does not work.
So I think this package should be a dependence of the KDE Wayland session.


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

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

Versions of packages plasma-workspace-wayland depends on:
ii  kpackagetool5 5.97.0-1
ii  kwayland-integration  5.25.4-1
ii  kwin-wayland  4:5.25.4-2
ii  libc6 2.34-7
ii  libkf5configcore5 5.97.0-2
ii  libkf5configgui5  5.97.0-2
ii  libkf5configwidgets5  5.97.0-1
ii  libkf5coreaddons5 5.97.0-1
ii  libkf5guiaddons5  5.97.0-1
ii  libkf5kcmutils5   5.97.0+really5.97.0-2
ii  libkf5kiogui5 5.97.0-1
ii  libkf5notifications5  5.97.0-1
ii  libkf5package55.97.0-1
ii  libkf5service-bin 5.97.0-1
ii  libkf5service55.97.0-1
ii  libkworkspace5-5  4:5.25.4-3
ii  libphonon4qt5-4   4:4.11.1-4
ii  libqt5core5a  5.15.4+dfsg-5
ii  libqt5dbus5   5.15.4+dfsg-5
ii  libqt5gui55.15.4+dfsg-5
ii  libstdc++612.2.0-1
ii  phonon4qt54:4.11.1-4
ii  plasma-workspace  4:5.25.4-3
ii  qtwayland55.15.4-2

plasma-workspace-wayland recommends no packages.

plasma-workspace-wayland suggests no packages.

-- no debconf information

Bug#927989: RFA: terminaltables -- Python library for printing tables to the console

2022-09-16 Thread Daniel Baumann

retitle 927989 ITA: terminaltables -- Python library for printing tables
owner 927989 Daniel Baumann 
retitle 929658 ITA: colorclass -- ANSI color text library for Python
owner 929658 Daniel Baumann 
thanks

Hi Carl,

On 9/16/22 01:54, Carl Suster wrote:
> Please go ahead! It would make sense to also take on colorclass
> (https://bugs.debian.org/929658) at the same time since it's a
> dependency of terminaltables.

sure; will take care about both then.

Regards,
Daniel

Bug#1019917: /usr/bin/getsubids: Segfaults when nsswitch.conf refers to a libsubid_*.so library that does not exist

2022-09-16 Thread Sam Morris

Package: uidmap
Version: 1:4.11.1+dfsg1-2
Severity: normal
File: /usr/bin/getsubids

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

With:

$ grep ^subid: /etc/nsswitch.conf
subid: sss

I get:

$ getsubids sam
Segmentation fault (core dumped)

GDB reveals that this is happening while handling the failure to open
libsubid_sss.so:

(gdb) where
#0  __vfprintf_internal (s=0x0, format=0x77f94872 "Error opening %s: 
%s\n", ap=ap@entry=0x7fffdbd0, mode_flags=mode_flags@entry=2) at 
./stdio-common/vfprintf-internal.c:1359
#1  0x77d1751f in ___fprintf_chk (fp=, 
flag=flag@entry=1, format=format@entry=0x77f94872 "Error opening %s: %s\n") 
at ./debug/fprintf_chk.c:33
#2  0x77f8318e in fprintf (__fmt=0x77f94872 "Error opening %s: 
%s\n", __stream=) at 
/usr/include/x86_64-linux-gnu/bits/stdio2.h:105
#3  nss_init (nsswitch_path=0x77f94820 "/etc/nsswitch.conf", 
nsswitch_path@entry=0x0) at ./lib/nss.c:94
#4  0x77f831bb in get_subid_nss_handle () at ./lib/nss.c:148
#5  0x77f852db in list_owner_ranges 
(owner=owner@entry=0x7fffe2a6 "sam", id_type=id_type@entry=ID_TYPE_UID, 
in_ranges=in_ranges@entry=0x7fffddd0) at ./lib/subordinateio.c:776
#6  0x77f7efad in get_subid_ranges (ranges=0x7fffddd0, 
id_type=ID_TYPE_UID, owner=owner@entry=0x7fffe2a6 "sam") at 
./libsubid/api.c:48
#7  0x514f in main (argc=2, argv=0x7fffdf18) at 
./src/getsubids.c:38

(gdb) l
89  goto done;
90  }
91  snprintf(libname, 64,  "libsubid_%s.so", token);
92  h = dlopen(libname, RTLD_LAZY);
93  if (!h) {
94  fprintf(shadow_logfd, "Error opening 
%s: %s\n", libname, dlerror());
95  fprintf(shadow_logfd, "Using files\n");
96  subid_nss = NULL;
97  goto done;
98  }

(gdb) p libname
$1 = "libsubid_sss.so", '\000' 

(gdb) p shadow_logfd
$2 = (FILE *) 0x77df3680 <_IO_2_1_stderr_>

(gdb) p dlerror()
$3 = 0x0

Looks like dlerror is returning NULL which causes the crash.

- -- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages uidmap depends on:
ii  libaudit11:3.0.7-1+b1
ii  libc62.34-7
ii  libselinux1  3.4-1+b1
ii  libsubid41:4.11.1+dfsg1-2

uidmap recommends no packages.

uidmap suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIgEARYIADAWIQTWOGqGn6HETecdzqZOEaKLhlAYigUCYyQ5YxIcc2FtQHJvYm90
cy5vcmcudWsACgkQThGii4ZQGIo6aAD/ZVNMtggK8Tvo0OcKDjaIgT9Gv5cBYflG
ymusOSHQ2X4A/1+aBe0EfugsEePoyn2golGRMn44gDj4z9Sk5rrJKKoF
=12CG
-END PGP SIGNATURE-

Bug#905000: minetest: does not use fullscreen resolution over VGA

Control: tags -1 -fixed-upstream +wontfix
Control: severity -1 wishlist

(Dear bot, I don't believe this has been fixed upstream ;-))

The bug has been closed upstream, but i could not find any fixes associated
with them. On top, upstream seems to be reluctant to implement "boderless 
windows" support,
despite this is the (usual) way how to handle it… Sigh. I guess this is nothing 
we can
fix from Debian side…

Upstream seems to suggest to use windowed mode and then use DE means (e.g 
keyboard combination)
to switch that window to fullscreen. This only works if fullscreen mode is 
disabled in
~/.minetest/minetest.conf -- the default value is "disabled".

(FTR, in GNOME you have to set the keyboard shortcut in the Settings first, as 
it is disabled
by default. Afterwards, that shortcut will maximize the minetest window as 
expected.)

I'm downgrading this bug and leave it open to document the workaround.

Cheers,
-- 
tobi

Bug#1019916: node-commist embeds a copy of node-leven

2022-09-16 Thread Yadd

Source: node-commist
Version: 3.1.2-1
Severity: serious
Tags: upstream
Justification: Code duplication

Version 3.1.2 adds a leven.js file. This file is:
 * undeclared in debian/copyright (not same author)
 * a copy of node-leven file

Please drop it from import and replace it by `require("leven")`. Note
that node-leven provides commonjs files (built using mjs2cjs).

Also update debian/copyright years (2014-2022, not 2014)

Bug#1019872: patch

2022-09-16 Thread Thomas Lange




Here's a patch that removes the Diffstat column. I could not test it
because I think it will not run in my local directory.

What do you think about this patch? Does it look OK?


diff --git a/stattrans.pl b/stattrans.pl
index c02fb8a5b75..c9db9fda803 100755
--- a/stattrans.pl
+++ b/stattrans.pl
@@ -489,10 +489,8 @@ foreach $lang (@search_in) {
 } else {
 $o_body .= sprintf "%s", $hits, $base, $base;
 }
-   my $stattd = sprintf 'Click to fetch diffstat data\' 
onClick="setDiffstat(\'%s\', \'%s\', \'%s\', this)">+/-', $file, 
$transversion{"$lang/$file"}, $version{"$orig/$file"};
  if (!defined $status_db{$lang}) {
 $o_body .= sprintf "%s", $msg;
-$o_body .= $stattd;
  }
if ($msg eq 'Wrong translation 
version' || $msg eq 'The original no longer 
exists') {
  if (defined $status_db{$lang}) {
@@ -637,7 +635,6 @@ foreach $lang (@search_in) {
print HTML 'Diff';
  } else {
print HTML 'Comment'."\n";
-   print HTML 'Diffstat'."\n";
print HTML 'Git command 
line';
  }
 print HTML 'Log';

-- 
regards Thomas

Bug#971623: link to wnpp.d.net

2022-09-16 Thread Thomas Lange

Hi,

I just looked at the wnpp.d.net page and found it very nice. Looking
at the git logs of the repo for this domain, you can see that it's
very well maintained and in 2021 the old php code was replace with
django and Python 3. So, this is better maintained than some very old
code in our webwml repository.

I find the idea of linking to wnpp.d.net also very valuable.
And maybe wnpp.d.net will become a debian.org domain in the future.

-- 
regards Thomas

Bug#1019915: bullseye-pu: package dojo/1.15.4+dfsg1-1+deb11u1

2022-09-16 Thread Yadd

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
dojo is vulnerable to prototype pollution (#1014785, CVE-2021-23450)

[ Impact ]
Medium vulnerability

[ Tests ]
No new test here

[ Risks ]
No risk, patch is 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 (old)stable
  [X] the issue is verified as fixed in unstable

Cheers,
Yadd
diff --git a/debian/changelog b/debian/changelog
index bf5c2b47..b861b5a0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+dojo (1.15.4+dfsg1-1+deb11u1) bullseye; urgency=medium
+
+  * Team upload
+  * Fix prototype pollution (Closes: #1014785, CVE-2021-23450)
+
+ -- Yadd   Fri, 16 Sep 2022 10:42:57 +0200
+
 dojo (1.15.4+dfsg1-1) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/patches/CVE-2021-23450.patch 
b/debian/patches/CVE-2021-23450.patch
new file mode 100644
index ..fe66d089
--- /dev/null
+++ b/debian/patches/CVE-2021-23450.patch
@@ -0,0 +1,22 @@
+Description: Fix for CVE-2021-23450, prototype pollution
+Author: Sanchit Chadha
+Bug-Debian: https://bugs.debian.org/970501
+Origin: upstream, https://github.com/dojo/dojo/commit/b7b8b279
+Bug-Debian: https://bugs.debian.org/1014785
+Forwarded: not-needed
+Reviewed-By: Yadd 
+Last-Update: 2022-09-16
+
+--- a/dojo/_base/lang.js
 b/dojo/_base/lang.js
+@@ -31,6 +31,10 @@
+   try{
+   for(var i = 0; i < parts.length; i++){
+   var p = parts[i];
++  // Fix for prototype pollution 
CVE-2021-23450
++  if (p === '__proto__' || p === 
'constructor') {
++  return;
++  }
+   if(!(p in context)){
+   if(create){
+   context[p] = {};
diff --git a/debian/patches/series b/debian/patches/series
index c75b2155..0436f059 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@
 0002-Do-notrun-test-suite-in-build.patch
 0003-Disable-flash-storage.patch
 0004-Fix-shrinksafe-tests-with-new-rhino.patch
+CVE-2021-23450.patch

Bug#823061: Greetings from Mr. Stephen Melvin!!!

2022-09-16 Thread Mr. Stephen Melvin

Hello Dear, I have called you several times but didn't get through the
phone. Please contact me at my email address, I have an important thing to
discuss with you:   mmrstephe...@gmail.com

Bug#1010827: minetest: wrong find_nodes_in_area() volume calculation can crash or hang server

Control: tags -1 +fixed-upstream -patch
Control: forwarded -1 https://github.com/minetest/minetest/pull/11770

> If you are unsure on how to integrate it, I can try to help.

Thanks for the offer, but as upstream is happy with their fix and you
were unsuccesful in convincing them, we'll stick with the upstream solution.

Just on a side node: If you find yourself in disagreement with upstream on
a patch, and upstream is very clear about that they won't take that patch,
pretty please, don't bring that patch to Debian. This feels like you are 
trying to force "your way", and that will only create a bad mood.

I'm putting this note in, because there are other bug reports that somehow
have the same story. Thank you for considering this in the future.

--
tobi

Bug#1012870: defaults should include dbus-daemon

2022-09-16 Thread chrysn

Package: earlyoom
Version: 1.7-1
Followup-For: Bug #1012870

> I have never seen dbus-daemon use more memory than firefox.
> Is there an unfixed memory leak in the Debian version of dbus-deamon?

None that I'm aware of -- but I've just had a similar situation (this
time with killing the systemd user process, which cascades into systemd
going on to a killing spree on the rest of the system), and maybe the
current log can shed some light here (see below). There, I've been
running earlyoom with `-EARLYOOM_ARGS="-r 3600 --avoid
'(^|/)(dbus-daemon)$' --prefer 'contentproc'`.

My I don't have logs of which process has used which amount of memory,
but my guess is that something outside earlyoom's reach has been growing
faster than the small game which earlyoom reached, and so it kept
killing process after process until it found systemd.

Does that help clear up things?

BR
chrysn

PS. When asking for additional information on the bts, consider
group-replying or replying to 1012870-submit...@bugs.debian.org, for
otherwise the mail will only reach users subscribed to the issue or
package, which does not include the original submitter by default.


Sep 16 08:31:30 hephaistos earlyoom[1694]: mem avail:  4073 of 15899 MiB 
(25.62%), swap free:9 of 16279 MiB ( 0.06%)
[... nothing earlyoom or memory related ... ]
Sep 16 08:56:08 hephaistos earlyoom[1694]: mem avail:  1554 of 15899 MiB ( 
9.78%), swap free:  401 of 16279 MiB ( 2.47%)
Sep 16 08:56:08 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:08 hephaistos earlyoom[1694]: sending SIGTERM to process 
3874485 uid 1000 "goa-daemon": badness 800, VmRSS 8 MiB
Sep 16 08:56:08 hephaistos earlyoom[1694]: process exited after 0.1 seconds
Sep 16 08:56:08 hephaistos earlyoom[1694]: mem avail:  1568 of 15899 MiB ( 
9.87%), swap free:  407 of 16279 MiB ( 2.50%)
Sep 16 08:56:08 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:08 hephaistos earlyoom[1694]: sending SIGTERM to process 
3892597 uid 1000 "gvfsd-metadata": badness 800, VmRSS 7 MiB
Sep 16 08:56:09 hephaistos earlyoom[1694]: process exited after 0.1 seconds
Sep 16 08:56:09 hephaistos earlyoom[1694]: mem avail:  1569 of 15899 MiB ( 
9.87%), swap free:  410 of 16279 MiB ( 2.52%)
Sep 16 08:56:09 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:09 hephaistos earlyoom[1694]: sending SIGTERM to process 
3874498 uid 1000 "goa-identity-se": badness 800, VmRSS 7 MiB
Sep 16 08:56:09 hephaistos earlyoom[1694]: process exited after 0.1 seconds
Sep 16 08:56:09 hephaistos earlyoom[1694]: mem avail:  1559 of 15899 MiB ( 
9.81%), swap free:  412 of 16279 MiB ( 2.53%)
Sep 16 08:56:09 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:09 hephaistos earlyoom[1694]: sending SIGTERM to process 
3873747 uid 1000 "dconf-service": badness 800, VmRSS 5 MiB
Sep 16 08:56:09 hephaistos earlyoom[1694]: process exited after 0.1 seconds
Sep 16 08:56:09 hephaistos earlyoom[1694]: mem avail:  1556 of 15899 MiB ( 
9.79%), swap free:  412 of 16279 MiB ( 2.53%)
Sep 16 08:56:09 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:09 hephaistos earlyoom[1694]: memory situation has recovered 
while selecting victim
Sep 16 08:56:29 hephaistos earlyoom[1694]: mem avail:  1586 of 15899 MiB ( 
9.98%), swap free:  412 of 16279 MiB ( 2.53%)
Sep 16 08:56:29 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:29 hephaistos earlyoom[1694]: sending SIGTERM to process 
3874500 uid 1000 "gvfs-afc-volume": badness 800, VmRSS 5 MiB
Sep 16 08:56:29 hephaistos systemd[2015]: gvfs-afc-volume-monitor.service: 
Consumed 3.200s CPU time.
Sep 16 08:56:29 hephaistos earlyoom[1694]: process exited after 0.1 seconds
Sep 16 08:56:29 hephaistos earlyoom[1694]: mem avail:  1495 of 15899 MiB ( 
9.41%), swap free:  392 of 16279 MiB ( 2.41%)
Sep 16 08:56:29 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:29 hephaistos earlyoom[1694]: sending SIGTERM to process 
3874468 uid 1000 "gvfs-udisks2-vo": badness 800, VmRSS 5 MiB
Sep 16 08:56:29 hephaistos earlyoom[1694]: process exited after 0.1 seconds
Sep 16 08:56:29 hephaistos earlyoom[1694]: mem avail:  1527 of 15899 MiB ( 
9.60%), swap free:  371 of 16279 MiB ( 2.28%)
Sep 16 08:56:29 hephaistos earlyoom[1694]: low memory! at or below SIGTERM 
limits: mem 10.00%, swap 10.00%
Sep 16 08:56:29 hephaistos earlyoom[1694]: sending SIGTERM to process 
3892622 uid 1000 "gnome-keyring-d": badness 800, VmRSS 5 MiB
Sep 16 08:56:29 hephaistos org.freedesktop.secrets[3892621]: 
discover_other_daemon: 1
Sep 16 08:56:29 hephaistos

Bug#1019914: Useless in Debian

2022-09-16 Thread Katharina Drexel

Package: adldap2
Severity: serious

[ Reported by a team member to see the package removed from testing ]

adldap2 will be deprecated in favor of LdapRecord
(https://github.com/DirectoryTree/LdapRecord), and I don't see a use case any
more at the moment.
No packages depend on it, so it can be removed from testing easily.

Regards
Katharina

--

Bug#961654: buster-pu: package bzip2/1.0.6-9.2~deb10u1

2022-09-16 Thread Emilio Pozuelo Monfort


Hi Santiago,

On 15/09/2022 09:52, Emilio Pozuelo Monfort wrote:

On 14/09/2022 15:42, Santiago R.R. wrote:

El 14/09/22 a las 13:58, Emilio Pozuelo Monfort escribió:

On 13/09/2022 16:46, Sylvain Beucler wrote:

Hi,

IIUC this is about fixing 2 non-security bugs, that were introduced
prior to buster's initial release.

I personally don't think this fits the LTS project scope.
Maybe other LTS members will have a different opinion.


We've had bugfix updates from time to time. They are rare, but not
forbidden. This should go in a buster suite rather than buster-security, but
since there's no such suite for LTS, having it in buster-security is the
lesser evil. Of course we shouldn't flood -security with bug fixes, if that
was necessary we should consider keeping $stable open and handled by the LTS
team (but that doesn't seem necessary at this point).

In this case, since the update has been prepared and looks sensible, I'll go
ahead with the upload if nobody objects.



Thanks, Emilio. Also consider
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961654#15

Haven't tested yet myself. But I suppose I should apply it in unstable.


For buster I'd rather use what was proposed for buster-pu, as that's also what 
is in bullseye.


I have uploaded that, with a s/buster/&-security/ in d/changelog, and fixing 
your name to be UTF-8.


Cheers,
Emilio

Bug#1018134: [Debian-on-mobile-maintainers] Bug#1018134: Bug#1018134: chatty: bump severity to serious for ongoing evolution transitions

2022-09-16 Thread Evangelos Ribeiro Tzaras

Hi,

On Tue, 2022-09-06 at 08:40 +0200, Guido Günther wrote:
> Just so that everybody is on the same page: the next chatty
> release switches to libcmatrix and we can then switch to libsoup3
> via
> 
>   https://source.puri.sm/Librem5/libcmatrix/-/merge_requests/18   

just a quick update:
There will be a release and upload to Debian very soon now.

During the libsoup3 port a segmentation fault was found in libsoup3
which can happen when using HTTP2 [0]
and I've also filed it in the BTS [1]
since someone is bound to hit this sooner or later
and it also includes a workaround.

[0] https://gitlab.gnome.org/GNOME/libsoup/-/issues/302
[1] https://bugs.debian.org/1019913

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

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

Bug#1019913: libsoup3: segmentation fault when using HTTP2

2022-09-16 Thread Evangelos Ribeiro Tzaras

Source: libsoup3
Version: 3.2.0-1
Severity: important
Forwarded: https://gitlab.gnome.org/GNOME/libsoup/-/issues/302

Dear Maintainer,

libsoup3 sometimes runs into a segmentation fault when using HTTP2
that can be worked around by forcing HTTP1 usage with the environment variable
SOUP_FORCE_HTTP1=1


Logs will show the following type of warnings:

libsoup-http2-WARNING **: 18:32:30.072: 
(../http2/soup-client-message-io-http2.c:410):io_read: runtime check failed: 
(io->in_callback == 0)

before running into a segmentation fault.


Thank you for your work on maintaining libsoup3
and especially your work on the recent transition!


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1010760: minetest: Floating point serialization error on x86