Bug#998024: RFP: node-sass -- The reference implementation of Sass, written in Dart

[Yadd]

Hi,

sadly dart isn't packaged in Debian. As a workaround, you can use 
node-node-sass.


Cheers,
Yadd

Bug#996707: ITP: python-cattr -- Complex custom class converters for attrs Python library.

[Sandro Tosi]

control: owner -1 !

On Sun, 19 Dec 2021 20:56:12 -0500 Sandro Tosi  wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Romain Porte 
> > X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org, 
> > debian-pyt...@lists.debian.org
> >
> > * Package name: python-cattr
> >   Version : 1.8.0
> >   Upstream Author : Tin Tvrtković 
> > * URL : https://github.com/Tinche/cattrs
> > * License : MIT
> >   Programming Lang: Python
> >   Description : Complex custom class converters for attrs Python 
> > library.
>
> what's the status of this ITP? you reported a blocker on poetry, but
> that's been ACCEPTED into unstable.
>
> is there anything else preventing you to complete cattrs packaging?
> (the source package name should also be python-cattrs, given the
> upstream project name is cattrs and to maintain consistency with
> python-attrs/attrs)

I took over this ITP and uploaded python-cattrs to new, as i needed it
urgently for python-requests-cache.
https://ftp-master.debian.org/new/python-cattrs_1.9.0-1.html

Bug#1002678: FTBFS with OCaml 4.13.1

[Stéphane Glondu]

Source: diffoscope
Version: 197
Severity: important
Tags: ftbfs

Dear Maintainer,

Your package FTBFS with OCaml 4.13.1 with the following error:
> XFAIL tests/comparators/test_apk.py::test_android_manifest
> === 1 failed, 671 passed, 22 skipped, 1 xfailed in 411.99s (0:06:51) 
> ===
> E: pybuild pybuild:355: test: plugin distutils failed with: exit code=1: cd 
> /tmp/build/diffoscope-197/.pybuild/cpython3_3.9/build; python3.9 -m pytest 
> -vv -r sxX -l --cov=diffoscope --cov-report=term-missing --cov-report=html

The package builds fine in unstable, so the failure seems introduced
by the update to OCaml 4.13.1... but it's not obvious why (from the
log).

Packages rebuilt with OCaml 4.13.1 are available at:

  https://ocaml.debian.net/transitions/ocaml-4.13.1/


Cheers,

-- 
Stéphane


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

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

Bug#1002677: FTBFS in unstable

[Stéphane Glondu]

Source: liquidsoap
Version: 1.4.4-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

Your package FTBFS in unstable with the following error:
> File "tools/ffmpeg_config.ml", line 38, characters 9-36:
> 38 |  FFmpeg.Avutil.Log.set_level verbosity;
>   ^^^
> Error: Unbound module FFmpeg


Cheers,

-- 
Stéphane

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

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

Bug#994562: cryptsetup: consider exit statuses of keyscripts

[Christoph Anton Mitterer]

Control: forwarded -1 
https://salsa.debian.org/cryptsetup-team/cryptsetup/-/merge_requests/29
Control: tags -1 + patch


I've added some implementation of this... or at least a draft.


Cheers,
Chris.

Bug#1002676: mirror submission for mr.heru.id

[Heru Nugroho]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mr.heru.id
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Maintainer: Heru Nugroho 
Country: ID Indonesia
Location: Jakarta
Sponsor: heru.id https://heru.id




Trace Url: http://mr.heru.id/debian/project/trace/
Trace Url: http://mr.heru.id/debian/project/trace/ftp-master.debian.org
Trace Url: http://mr.heru.id/debian/project/trace/mr.heru.id

Bug#1002672: gdb: please remove annoying license output

[Sergio Durigan Junior]

Control: severity -1 wishlist

On Sunday, December 26 2021, Russell Coker wrote:

> Below are the 15 lines of output from gdb in it's normal mode of operation
> before it does anything related to it's operation.  The first line is useful
> as a screen-cap will contain the version which may affect the result.  The
> next 5 lines are useless.  The fact that it's configured as x86_64-linux-gnu
> could fit on the same line as the version without breaking 80 characters.
> The rest could be covered by the help sectiom.
>
> While this is a minor issue it is important as screenshots of gdb output are
> often used in situations where getting more information is difficult.  If
> there were 13 lines less useless stuff that would mean 13 lines more other
> data related to the debugging session such as previous runs of the same
> program.  This change would be useful not just to people who run gdb but
> also people who receive screenshots of it.

This request/wishlist should be taken upstream, IMO.  It is highly
unlikely that Debian will deviate from the default here; no other distro
does that.

Bear in mind a few things, though:

1) The GNU project requires that interactive programs print an excerpt
containing license text whenever they are invoked.  Other GNU programs
follow this convention as well (GNU guile and GNU poke, for example).
I don't see GDB changing this anytime soon.

2) There is a way to disable the license text in the startup message:
you can invoke GDB with "-q" in the command line, and it will be
silent.

3) Starting from GDB 11.1 (which is not in Debian yet), you can also use
the "set startup-quietly" option into your "gdbearlyinit" startup file.

Honestly, if it were up to me I'd probably close this bug as wontfix,
but I will just lower its severity for now so that zumbi has a change to
comment.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#834724:

[Алексей Трубаков]

Bug#996577: fixed in duplicity 0.8.21-1

[Alexander Zangerl]

clone 996577 -1
retitle -1 hubic backend: init fails with a type error
thanks

On Sun, 26 Dec 2021 16:53:12 +0100, Fabrice Lamareille writes:
>Unfortunately, the hubic backend does not seem to work yet. I now get 
>the following error:
>
>Connection failed, please check your credentials: TypeError __init__() 
>got an unexpected keyword argument 'username'

i'll forward your new bug report upstream, but don't hold your breath:
the hubic service seems to be mostly if not quite entirely dead for
multiple years now, so interest in supporting that is not likely to be high.


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
"Any sufficiently advanced political correctness is indistinguishable
from irony." -- Erik Naggum


signature.asc
Description: Digital Signature

Bug#1002674: fcitx5-qt: reproducible-builds: BuildId differences triggered by RPATH

[Vagrant Cascadian]

Source: fcitx5-qt
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The RPATH contains the build path resulting in different buildid:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fcitx5-qt.html

The attached patch to debian/rules passes
-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override,
which should use a relative path for RPATH.

With this patch applied, fcitx5-qt should build reproducibly on
tests.reproducible-builds.org!

Thanks for maintaining fcitx5-qt!

live well,
  vagrant
From 48f324134e6cf0e3263bd9799caa3e2e5335a9d2 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Mon, 27 Dec 2021 03:53:55 +
Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via
 dh_auto_configure override.

This avoids embedding the full path in RPATH, which triggers BuildId
differences.

https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index a7f20a3..50ee87d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,4 +8,5 @@ export QT_SELECT := 5
 
 override_dh_auto_configure:
 	dh_auto_configure -- \
+	-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \
 	-DENABLE_QT4=0
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#1002673: sphinx-copybutton: reproducible builds: html documentation contains translated content

[Sandro Tosi]

> Various .html files generated and shipped in the .deb package differ
> depending on the locale of the build environment:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/sphinx-copybutton.html
>
>   /usr/share/doc/python-sphinx-copybutton-doc/html/genindex.html
>
>   ... 
> placeholder="Search·the·docs·..."·aria-label="Search·the·docs·..."·autocomplete="off"·>
>
> vs.
>
>   ... 
> placeholder="Dokumentidest·otsimine·..."·aria-label="Dokumentidest·otsimine·..."·autocomplete="off"·>
>
>
> The attached patch fixes this by exporting LANGUAGE=en when calling
> sphinxdoc from debian/rules.

this is a problem that could happen with every package that uses
sphinx and has multi-language doc available.

that said, i dont believe this should be fixed in each individual
package, but it should either be enforced at the sphinx level or in
the build environment.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1002673: sphinx-copybutton: reproducible builds: html documentation contains translated content

[Vagrant Cascadian]

Source: sphinx-copybutton
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Various .html files generated and shipped in the .deb package differ
depending on the locale of the build environment:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/sphinx-copybutton.html

  /usr/share/doc/python-sphinx-copybutton-doc/html/genindex.html

  ... 
placeholder="Search·the·docs·..."·aria-label="Search·the·docs·..."·autocomplete="off"·>

vs.

  ... 
placeholder="Dokumentidest·otsimine·..."·aria-label="Dokumentidest·otsimine·..."·autocomplete="off"·>


The attached patch fixes this by exporting LANGUAGE=en when calling
sphinxdoc from debian/rules.


Thanks for maintaining sphinx-copybutton!


live well,
  vagrant
From 6afc886f7fa911b76a7367e2837741f578150cda Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Mon, 27 Dec 2021 02:57:47 +
Subject: [PATCH] debian/rules: Set LANGUAGE when building documentation.

https://tests.reproducible-builds.org/debian/issues/bookworm/sphinxdoc_translations_issue.html
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index f6ae964..7729685 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@ export PYBUILD_NAME=sphinx-copybutton
 override_dh_auto_build:
 	ln -sf /usr/share/javascript/clipboard.js/clipboard.js sphinx_copybutton/_static/clipboard.min.js
 	dh_auto_build
-	PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs docs/build/html
+	PYTHONPATH=. LANGUAGE=en http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs docs/build/html
 
 override_dh_auto_install:
 	dh_auto_install
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#999448: [External] Re: Bug#999448: atop: Two fixes for debian/rules: activate atopacctd before activating atop, load atop.default into pkg

[李菲]

On Fri, Dec 24, 2021 at 7:18 PM Marc Haber 
wrote:

> On Fri, Dec 24, 2021 at 05:17:07PM +0800, 李菲 wrote:
> > On Fri, Dec 24, 2021 at 3:02 AM Marc Haber <
> mh+debian-packa...@zugschlus.de>
> > wrote:
> >
> > > On Thu, Dec 23, 2021 at 07:48:19PM +0100, Marc Haber wrote:
> > > > The interesting line of code is
> > > >
> > > > deb-systemd-invoke $_dh_action 'atop-rotate.service'
> 'atop-rotate.timer'
> > > 'atop.service' 'atopacct.service
> > > >
> > > > which will instruct systemd to start all those four services. I am
> not
> > > > sure whether it makes sense for atop to explicitly start the two
> > > > atop-rotate units, and I think that systemd decides by itself in
> which
> > > > order the units are started.
> > >
> > > The atopacct unit (systemctl cat atopacct) has an explicit "Before:
> > > atop.service" listed. So, systemd SHOULD take care of starting
> atopacctd
> > > first before atop is started.
> > >
> > Actually I am not sure whether "before: " only guarantees this
> > when the host machine restarts, but not installing packages.
>
> I surely do hope that this also applies to systemctl transactions.
> atop's maintainer scripts group all unit starts into a single
> transaction, leaving the order of execution to systemd. That's done by
> debhelper, and as a package maintainer I am not going to interfere with
> that. The best I can do is to help upstream to properly design their
> systemd units and probably make code changes to make startup more
> robust.

Sure.

>
> > > Can you please verify (maybe from syslog?) that the start order is
> > > actually wrong when you encounter the situation of misbehavior?
> > >
> > > Run `dpkg --purge atop && dpkg -i ../atop_2.6.0+byted3_amd64.deb`,
> > and see the log, just as follows:
> > # journalctl | grep atop
> >
> > Dec 24 17:08:22 n198-252-111 atopacctd[27883]: Terminated by signal 15
> >
> > Dec 24 17:08:22 n198-252-111 systemd[1]: atopacct.service: Succeeded.
> >
> > Dec 24 17:08:22 n198-252-111 systemd[1]: atop.service: Succeeded.
> >
> > Dec 24 17:08:22 n198-252-111 systemd[1]: atop-rotate.timer: Succeeded.
> >
> > Dec 24 17:08:22 n198-252-111 systemd[1]: Stopped Daily atop restart.
> >
> > Dec 24 17:08:31 n198-252-111 systemd[1]: Started Daily atop restart.
> >
> > Dec 24 17:08:32 n198-252-111 atopacctd[29508]: Version: 2.6.0+byted3 -
> > 2021/12/23 17:02:33  
> >
> > Dec 24 17:08:32 n198-252-111 atopacctd[29508]: accounting to
> > /run/pacct_source
>
> Is that reproducible?
>
> > > (2) psacct is installed or not?
> > >
> > Yes,
> >
> > # dpkg -L atop |grep pacct
> >
> > /etc/init.d/atopacct
> >
> > /lib/systemd/system/atopacct.service
> >
> > /usr/sbin/atopacctd
> > /usr/share/man/man8/atopacctd.8.gz
>
> pSacct is a different package, dpkg --list psacct please.
>
Just make sure if the package's name is called psacct.
As after installing v2.6.0 from
https://salsa.debian.org/debian/atop/-/tree/debian/2.6.0-1,
I still can not find this package:

# atop -V

Version: 2.6.0 - 2020/12/21 20:45:10 

# dpkg --list psacct

dpkg-query: no packages found matching psacct

Have a nice day, thanks
Fei

> Greetings
> Marc
>
> --
>
> -
> Marc Haber | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
>

Bug#996577: fixed in duplicity 0.8.21-1

[Fabrice Lamareille]

Hello,

I've just installed duplicity (0.8.21-1) from unstable repository. This 
solves the 'BaseIdentity' bug.


Unfortunately, the hubic backend does not seem to work yet. I now get 
the following error:


Connection failed, please check your credentials: TypeError __init__() 
got an unexpected keyword argument 'username'


Thanks.

Fabrice.

On Sat, 25 Dec 2021 07:33:42 + Debian FTP Masters 
 wrote:


> Source: duplicity
> Source-Version: 0.8.21-1
> Done: Alexander Zangerl 
>
> We believe that the bug you reported is fixed in the latest version of
> duplicity, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed. If you
> have further comments please address them to 996...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Alexander Zangerl  (supplier of updated duplicity package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sat, 25 Dec 2021 16:04:16 +1000
> Source: duplicity
> Architecture: source
> Version: 0.8.21-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Alexander Zangerl 
> Changed-By: Alexander Zangerl 
> Closes: 605878 677215 862005 996577
> Changes:
> duplicity (0.8.21-1) unstable; urgency=medium
> .
> * new upstream release (closes: #996577, #677215, #605878, #862005)
> debhelper compat updated, ditto standards version
> Checksums-Sha1:
> 61e99177789ff86337f7f6602b395ae1266d96f0 2085 duplicity_0.8.21-1.dsc
> 2703806f1397a132b7de7eb365c7d79a32efd0f3 1375469 
duplicity_0.8.21.orig.tar.gz
> 9c1b3952d8bff5c2cf3d8fe2290ef1abf0e88dc0 15868 
duplicity_0.8.21-1.debian.tar.xz
> 420db366ba62e2e86f3e09dc598ebb0575ed602c 11003 
duplicity_0.8.21-1_amd64.buildinfo

> Checksums-Sha256:
> 2b005e4f095fe8a9e9071157536c8ae64fb60ec72f7e745d2700c43695dbd2d6 2085 
duplicity_0.8.21-1.dsc
> 57fea6764674718cd6f6d499e6de92c973ba4f5e74dd94fc5e644713355ca451 
1375469 duplicity_0.8.21.orig.tar.gz
> 51dc04ba05c8606e53b73d76267ef7fefd626d667e0ca3f5beb9135014953a5d 
15868 duplicity_0.8.21-1.debian.tar.xz
> f746a43c0577462cad0c397da1c877c578aec7fd4079c40ab27c9f8ccef8d684 
11003 duplicity_0.8.21-1_amd64.buildinfo

> Files:
> 43f29f44bb3c24ac970b1692bb6db4de 2085 utils optional 
duplicity_0.8.21-1.dsc
> 5227dd503c251d8b678ea663b759cb98 1375469 utils optional 
duplicity_0.8.21.orig.tar.gz
> 924d994ac387df69d6ed8cddc5b80519 15868 utils optional 
duplicity_0.8.21-1.debian.tar.xz
> b010edab19b8a5e644635c710910f949 11003 utils optional 
duplicity_0.8.21-1_amd64.buildinfo

>
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJhxsW8AAoJED06g4g30PqNu2QP/A0irnka8Ql19slOPimc0RDS

Bug#996461: nvidia-kernel-dkms: DKMS tree already contains: nvidia-current-470.74

[Drew Parsons]

Package: nvidia-kernel-dkms
Followup-For: Bug #996461
Control: found -1 470.86-1
Control: fixed -1 495.44-1

This bug seems to be fixed now in 495.44-1.
It was still broken with 470.86-1.

I guess we can close this bug now. Would any more diagnostic data be
useful before closing?

Drew


-- Package-specific info:
uname -a:
Linux sandy 5.15.0-2-amd64 #1 SMP Debian 5.15.5-2 (2021-12-18) x86_64 GNU/Linux

/proc/version:
Linux version 5.15.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-13) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.15.5-2 (2021-12-18)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.44  Fri Oct 22 06:13:12 UTC 
2021
GCC version:  gcc version 11.2.0 (Debian 11.2.0-13) 

lspci 'display controller [030?]':
00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-U GT2 
[UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

2d:00.0 3D controller [0302]: NVIDIA Corporation GP108M [GeForce MX330] 
[10de:1d16] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX330] [17aa:22b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia



-- 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.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 nvidia-kernel-dkms depends on:
ii  dkms   2.8.7-2
pn  nvidia-firmware-495.44 
ii  nvidia-installer-cleanup   20151021+13
ii  nvidia-kernel-support [nvidia-kernel-support--v1]  495.44-1

Versions of packages nvidia-kernel-dkms recommends:
ii  libcuda1   495.44-1
ii  nvidia-driver  495.44-1

nvidia-kernel-dkms suggests no packages.

Versions of packages nvidia-driver depends on:
ii  nvidia-alternative 495.44-1
ii  nvidia-driver-bin  495.44-1
ii  nvidia-driver-libs 495.44-1
ii  nvidia-installer-cleanup   20151021+13
ii  nvidia-legacy-check495.44-1
ii  nvidia-support 20151021+13
ii  nvidia-vdpau-driver495.44-1
ii  xserver-xorg-video-nvidia  495.44-1

Versions of packages nvidia-driver recommends:
ii  libnvidia-cfg1   495.44-1
ii  nvidia-persistenced  470.82.00-1
pn  nvidia-settings  

nvidia-driver suggests no packages.

Versions of packages nvidia-driver-libs:amd64 depends on:
ii  libgl1-nvidia-glvnd-glx  495.44-1
ii  nvidia-egl-icd   495.44-1

Versions of packages nvidia-driver-libs:amd64 recommends:
ii  libgles-nvidia1 495.44-1
ii  libgles-nvidia2 495.44-1
ii  libglx-nvidia0  495.44-1
ii  libnvidia-cfg1  495.44-1
ii  libnvidia-encode1   495.44-1
ii  libopengl0  1.3.4-2+b1
ii  nvidia-driver-libs  495.44-1
ii  nvidia-vulkan-icd   495.44-1

Versions of packages nvidia-driver-libs:i386 depends on:
ii  libgl1-nvidia-glvnd-glx  495.44-1
ii  nvidia-egl-icd   495.44-1

Versions of packages nvidia-driver-libs:i386 recommends:
ii  libgles-nvidia1495.44-1
ii  libgles-nvidia2495.44-1
ii  libglx-nvidia0 495.44-1
ii  libnvidia-encode1  495.44-1
ii  libopengl0 1.3.4-2+b1
ii  nvidia-vulkan-icd  495.44-1

Versions of packages xserver-xorg-video-nvidia depends on:
ii  libc6  2.33-1
ii  libnvidia-glcore   495.44-1
ii  nvidia-alternative 495.44-1
ii  nvidia-installer-cleanup   20151021+13
ii  nvidia-legacy-check495.44-1
ii  nvidia-support 20151021+13
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.13-3

Versions of packages xserver-xorg-video-nvidia recommends:
ii  nvidia-driver495.44-1
pn  nvidia-settings  
ii  nvidia-vdpau-driver  495.44-1

xserver-xorg-video-nvidia suggests no packages.

Versions of packages nvidia-alternative depends on:
ii  dpkg1.21.1
ii  glx-alternative-nvidia  1.2.1
ii  nvidia-legacy-check 495.44-1

Versions of packages glx-alternative-nvidia depends on:
ii  dpkg  1.21.1
ii  glx-alternative-mesa  1.2.1
ii  glx-diversions1.2.1
ii  update-glx1.2.1

Bug#1002671: python-parse-type: reproducible builds: Timestamps, timing and hostname in result.xml

[Vagrant Cascadian]

Source: python-parse-type
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps hostname
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

There are two result.xml files shipped in the .deb package which contain
timestamp, timing, and hostname information about the build environment:

  ./usr/lib/python3/dist-packages/build/testing/report.xml

  - 

vs.
  
  + 


The attached patch fixes this by removing these files from debian/rules
in a dh_install override.


If it is not appropriate to remove the result.xml files, another
approach might be to sanitize out all the timestamps, timing and
hostname, although this might become a game of whack-a-mole over time.


With this patch applied, python-parse-type should build reproducibly on
tests.reproducible-builds.org.


Thanks for maintaining python-parse-type!


live well,
  vagrant
From 385bf9f6385cdbea8bc480290c10936f44df5f89 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Mon, 27 Dec 2021 01:41:53 +
Subject: [PATCH] debian/rules: Delete test suite log from dh_install override.

---
 debian/rules | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/rules b/debian/rules
index 02c38ce..62b5543 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,3 +4,10 @@ export PYBUILD_NAME=parse-type
 
 %:
 	dh $@ --with python3 --buildsystem=pybuild
+
+override_dh_install:
+	# Delete log of test suite which contains dates and timing
+	# information for reproducible builds.
+	find debian/python3-parse-type/usr/lib/python*/dist-packages/build/testing/ \
+		-name report.xml -delete -print
+	dh_install
-- 
2.34.1



signature.asc
Description: PGP signature

Bug#726348: filezilla: Filezilla crashed/hanged while minimized to tray in kde

[Philip Wyett]

Hi,

Maintainer addition.

Affects version 3.52.2-3 in Debian 11 (stable).

No crash while transferring, but as noted doing the minimize and maximise a few 
times leads to the
tray icon crashing and disappearing with filezilla still running in the 
background.

Will do test on latest (3.57.0) filezilla once I have uploaded it to unstable. 
If it still
persists, I will forward upstream.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#1002670: grub2-common: Unable to force MBR/embedding installation

[Elliott Mitchell]

Package: grub2-common
Version: 2.04-20
Severity: important

Hopefully the subject tells the tale.  Due to some odd hardware, I need
to force `grub-install` to install the EFI version of GRUB into the
MBR/boot area gap.  Unfortunately the documentation suggest none of
`grub-install`'s options can get this result.  As a result I've got a
problem.

The background:  I'm trying to get GRUB installed on a very popular ARM64
device which has a full Tianocore/UEFI image available.  Unfortunately
while it is full Tianocore, the device lacks any private NVRAM and thus
is unable to store EFI variables.

`grub-install` tries to do a "normal" UEFI installation, which fails due
to lack of EFI variables.  As a result I need GRUB to install in the
MBR/GPT gap, but none of `grub-install`'s options appear to cause this.

Plan B might be to remove the EFI System UUID from the boot area, but
this solution seems wrong.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#974617: nomacs 3.16 is available upstream

[Vincent Lefevre]

On 2020-11-13 02:19:29 +0100, Vincent Lefevre wrote:
> nomacs 3.16 is available upstream:
> 
>   https://nomacs.org/nomacs-3-16/
> 
> It may have bug fixes.

Also, since the upstream owners no long respond, watch for a potential
fork: https://github.com/nomacs/nomacs/issues/612 (latest comment
posted 7 days ago).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#974616: nomacs: "charset=Ascii" appears before the comment of the image

[Vincent Lefevre]

On 2021-12-26 21:00:13 +, Sergio Gelato wrote:
> My only interest in this bug is that it has kept nomacs out of
> bullseye; I don't need its EXIF support.

EXIF information is very useful in general, but AFAIK, only the
comment is affected. A solution would be to either fix the comment
handling or remove it. (Nowadays, ImageDescription seems to be
preferred to Comment, so that removing Comment support would not
be a big loss.)

> If this package isn't effectively orphaned, perhaps the maintainer
> can lower the bug's severity?

Note that there is a potential security issue. Perhaps not currently
(I'm not sure), but potentially in the future: it suffices that the
exiv internals change (like in the past to fix a security bug) to
make Nomacs behave erratically, possibly with memory corruption.

> (And/or forward the report upstream...)

FYI, I haven't reported the bug upstream because Debian has a very
old version. The package should be upgraded to 3.16 first.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#987054: xserver-xorg-core: modesetting driver fails asking for OpenGL version 2.1 or later

[Ángel]

title xserver-xorg-core: modesetting driver failing requesting OpenGL >= 2.1

Thanks so much Josua!

I was facing the same problem... with a completely different card. An
old NVIDIA GeForce, for which nouveau works for a while to then freezes
with a GPU lockout. Trying to use another driver failed with the same:

> (WW) Require OpenGL version 2.1 or later.
> (EE) modeset(0): Failed to initialize glamor at ScreenInit() time.

So it's not just Vivante GC2000 that suffers this.

The real merit goes to Lubomir for the upstream implementation, of
course, but without this bug, it's unlikely I would have found commit
26004df6.
Plus, your backport worked flawlessly.

Debian X, it would be nice if this could be included in a point
release.


Regards

Bug#1002652: bullseye-pu: package schleuder/3.6.0-3+deb11u1

[Georg Faerber]

Control: retitle -1 bullseye-pu: package schleuder/3.6.0-3+deb11u1
--

Hi,

The proposed package used an incorrect versioning scheme targeting
buster, not bullseye.

The attached debdiff is fixed in this regard.

Sorry for this noise.

Cheers,
Georg
diffstat for schleuder-3.6.0 schleuder-3.6.0

 changelog   |   12 ++
 patches/0031-db-change-boolean-values-to-integers.patch |   77 
 patches/series  |1 
 3 files changed, 90 insertions(+)

diff -Nru schleuder-3.6.0/debian/changelog schleuder-3.6.0/debian/changelog
--- schleuder-3.6.0/debian/changelog2021-07-29 20:36:52.0 +
+++ schleuder-3.6.0/debian/changelog2021-12-26 16:28:29.0 +
@@ -1,3 +1,15 @@
+schleuder (3.6.0-3+deb11u1) bullseye; urgency=medium
+
+  * debian/patches:
+- Pull in upstream patch to migrate boolean values to integers, if the
+  ActiveRecord SQLite3 connection adapter is in use. Since ActiveRecord >=
+  6.0, the relevant code relies on boolean serialization to use 1 and 0,
+  but does not natively recognize 't' and 'f' as booleans were previously
+  serialized. This change made existing mailing lists fail, if people were
+  upgrading buster to bullseye. (Closes: #100262)
+
+ -- Georg Faerber   Sun, 26 Dec 2021 16:28:29 +
+
 schleuder (3.6.0-3) unstable; urgency=medium
 
   * debian/patches:
diff -Nru 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch
--- 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch  
1970-01-01 00:00:00.0 +
+++ 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch  
2021-12-26 16:28:29.0 +
@@ -0,0 +1,77 @@
+Description: DB: change boolean values to integers
+  Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean
+  serialization to use 1 and 0, but does not natively recognize 't' and 'f' as
+  booleans were previously serialized. Accordingly, this patch handles
+  conversion via a database migration of both column defaults and stored data
+  provided by a user.
+Author: Georg Faerber 
+Origin: upstream
+Bug: https://0xacab.org/schleuder/schleuder/-/issues/505
+Applied-Upstream: 9ee12c4a1d6604c860c44073b99d8258bb4bc0ae
+Last-Update: 2021-12-25
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: schleuder/db/migrate/20211106112020_change_boolean_values_to_integers.rb
+===
+--- /dev/null  1970-01-01 00:00:00.0 +
 schleuder/db/migrate/20211106112020_change_boolean_values_to_integers.rb   
2021-12-26 17:28:42.468530957 +
+@@ -0,0 +1,46 @@
++# Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean
++# serialization to use 1 and 0, but does not natively recognize 't' and 'f' as
++# booleans were previously serialized.
++#
++# Accordingly, this migration handles conversion of both column defaults and
++# stored data provided by a user.
++#
++# In contrast to other migrations, only a 'forward' method is provided, a
++# mechanism to 'reverse' is not. Given the nature of this migration, the later
++# is not really required.
++#
++# Unfortunately, we missed this breaking change when bumping ActiveRecord to 
>=
++# 6.0 in Schleuder version 4.0. This caused quite some work upstream, but also
++# in downstream environments and, last but not least, at the side of users.
++#
++# We should extend our CI to explicitly test, and ensure things work as
++# expected, if running a Schleuder setup in real world. As of now, we don't
++# ensure data provided by a user in Schleuder version x still works after
++# upgrading to version y.
++
++class ChangeBooleanValuesToIntegers < ActiveRecord::Migration[6.0]
++  class Lists < ActiveRecord::Base
++  end
++
++  class Subscriptions < ActiveRecord::Base
++  end
++
++  def up
++[Lists, Subscriptions].each do |table|
++  unless 
table.connection.is_a?(ActiveRecord::ConnectionAdapters::SQLite3Adapter)
++return
++  end
++
++  bool_columns_defaults = table.columns.select { |column| column.type == 
:boolean }.map{ |column| [column.name, column.default] }
++
++  bool_columns_defaults.each do |column_name, column_default|
++column_bool = 
ActiveRecord::Type::Boolean.new.deserialize(column_default)
++
++change_column_default :"#{table.table_name}", :"#{column_name}", 
column_bool
++
++table.where("#{column_name} = 'f'").update_all("#{column_name}": 0)
++table.where("#{column_name} = 't'").update_all("#{column_name}": 1)
++  end
++end
++  end
++end
+Index: schleuder/db/schema.rb
+===
+--- schleuder.orig/db/schema.rb2021-12-26 17:28:42.472530996 +
 

Bug#1000335: mmanon plugin: IPv6 anonymization partially broken

[Georg Faerber]

Hi again,

On 21-12-26 23:52:58, Georg Faerber wrote:
> I've built a package now to ease this, and uploaded it to [1]. This
> file is not signed, but this email is. The sha256sum of said file
> should be 1edd0e09abf870146da441e7737fe78f634351c9cbbd0abdb46962911fe38e03.

This package used an incorrect versioning scheme targeting buster, not
bullseye.

A fixed package is available via [1], sha256sum should be
e6ccd338ebabcfea2014972e7b72e83ceb1e71f6a4ef9e3f32e0c718ece10311.

Cheers,
Georg

[1] 
https://people.debian.org/~georg/rsyslog/rsyslog_8.2102.0-2+deb11u1_amd64.deb


signature.asc
Description: PGP signature

Bug#1000335: mmanon plugin: IPv6 anonymization partially broken

[Georg Faerber]

Hi all,

On 21-12-26 23:08:01, Georg Faerber wrote:
> Besides, functional testing of this new package still needs to happen.

I've built a package now to ease this, and uploaded it to [1]. This file
is not signed, but this email is. The sha256sum of said file should be
1edd0e09abf870146da441e7737fe78f634351c9cbbd0abdb46962911fe38e03.

I guess it would make sense if interested parties would test this
package, before reaching out to the SRMs.

Cheers,
Georg


[1] 
https://people.debian.org/~georg/rsyslog/rsyslog_8.2102.0-2+deb10u1_amd64.deb


signature.asc
Description: PGP signature

Bug#1000262: closed by Debian FTP Masters (reply to Nobuhiro Iwamatsu ) (Bug#1000262: fixed in bluez 5.62-1)

[Nobuhiro Iwamatsu]

Hi Salvatore,

2021年12月19日(日) 16:56 Salvatore Bonaccorso :
>
> Control: reopen -1
> Control: notfixed -1 5.62-1
> Control: found -1 5.62-1
>
> Hi Nobuhiro,
>
> On Sun, Dec 19, 2021 at 12:51:03AM +, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the src:bluez package:
> >
> > #1000262: bluez: CVE-2021-41229: memory leak in the SDP protocol handling
>
> This does not look to be fixed with 5.62 upstream. The commit is in
> the repository only after the 5.62 release and the commit was not
> cherry-picked.
>
> Can you please double-check again?

Oops, sorry.
I recheck this issue and upload a fixed version.

Best regards,
  Nobuhiro


-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#507467: libclass-csv-perl: diff for NMU version 1.03-2.3

[gregor herrmann]

Control: tags 507467 + patch
Control: tags 507467 + pending
Control: tags 965627 + patch
Control: tags 965627 + pending
Control: tags 998936 + patch
Control: tags 998936 + pending


Dear maintainer,

I've prepared an NMU for libclass-csv-perl (versioned as 1.03-2.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libclass-csv-perl-1.03/debian/changelog libclass-csv-perl-1.03/debian/changelog
--- libclass-csv-perl-1.03/debian/changelog
+++ libclass-csv-perl-1.03/debian/changelog
@@ -1,3 +1,18 @@
+libclass-csv-perl (1.03-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965627)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #998936)
+  * Fix "Includes dh-make-perl boilerplate in long description":
+Remove boilerplate.
+(Closes: #507467)
+
+ -- gregor herrmann   Mon, 27 Dec 2021 00:15:25 +0100
+
 libclass-csv-perl (1.03-2.2) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libclass-csv-perl-1.03/debian/compat libclass-csv-perl-1.03/debian/compat
--- libclass-csv-perl-1.03/debian/compat
+++ libclass-csv-perl-1.03/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libclass-csv-perl-1.03/debian/control libclass-csv-perl-1.03/debian/control
--- libclass-csv-perl-1.03/debian/control
+++ libclass-csv-perl-1.03/debian/control
@@ -1,7 +1,7 @@
 Source: libclass-csv-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0)
+Build-Depends: debhelper (>= 7.0.0)
 Build-Depends-Indep: perl (>= 5.8.8-12), libclass-accessor-perl, libtext-csv-xs-perl
 Maintainer: Jose Parrella 
 Standards-Version: 3.7.3
@@ -15,5 +15,3 @@
  files from objects. Text::CSV_XS is used for parsing and creating CSV file
  lines, so any limitations in Text::CSV_XS will of course be inherant in this
  module.
- .
- This description was automagically extracted from the module by dh-make-perl.
diff -u libclass-csv-perl-1.03/debian/rules libclass-csv-perl-1.03/debian/rules
--- libclass-csv-perl-1.03/debian/rules
+++ libclass-csv-perl-1.03/debian/rules
@@ -10,7 +10,9 @@
 
 TMP =$(CURDIR)/debian/$(PACKAGE)
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -60,4 +62,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#965628: libbiblio-isis-perl: diff for NMU version 0.24-1.4

[gregor herrmann]

Control: tags 965628 + patch
Control: tags 965628 + pending
Control: tags 999144 + patch
Control: tags 999144 + pending


Dear maintainer,

I've prepared an NMU for libbiblio-isis-perl (versioned as 0.24-1.4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libbiblio-isis-perl-0.24/debian/changelog libbiblio-isis-perl-0.24/debian/changelog
--- libbiblio-isis-perl-0.24/debian/changelog
+++ libbiblio-isis-perl-0.24/debian/changelog
@@ -1,3 +1,15 @@
+libbiblio-isis-perl (0.24-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965628)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999144)
+
+ -- gregor herrmann   Mon, 27 Dec 2021 00:08:54 +0100
+
 libbiblio-isis-perl (0.24-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libbiblio-isis-perl-0.24/debian/compat libbiblio-isis-perl-0.24/debian/compat
--- libbiblio-isis-perl-0.24/debian/compat
+++ libbiblio-isis-perl-0.24/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libbiblio-isis-perl-0.24/debian/control libbiblio-isis-perl-0.24/debian/control
--- libbiblio-isis-perl-0.24/debian/control
+++ libbiblio-isis-perl-0.24/debian/control
@@ -1,7 +1,7 @@
 Source: libbiblio-isis-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0)
+Build-Depends: debhelper (>= 7.0.0)
 Build-Depends-Indep: perl (>= 5.8.8-7)
 Maintainer: Jose Parrella 
 Standards-Version: 3.7.2
diff -u libbiblio-isis-perl-0.24/debian/rules libbiblio-isis-perl-0.24/debian/rules
--- libbiblio-isis-perl-0.24/debian/rules
+++ libbiblio-isis-perl-0.24/debian/rules
@@ -10,7 +10,9 @@
 
 TMP =$(CURDIR)/debian/$(PACKAGE)
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -60,4 +62,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#1000335: mmanon plugin: IPv6 anonymization partially broken

[Georg Faerber]

Hi Michael, all,

On 21-11-30 18:35:36, Michael Biebl wrote:
> I'm very busy atm, but I can try.

I've pushed the proposed upload to the debian/bullseye branch in the
rsyslog repo.

I've cherry-picked your commit
(dfe482df2733940774c8d4f6d7756e5de3ade252) which initially introduced
the fix and the corresponding testbench, but removed the later again, as
the new test script is created with mode 100644, which fails, as the
test setup expects these scripts to be executable.

I'm unsure how to track file permissions via quilt, and a quick research
didn't yield much. Any input how to solve this?

Besides, functional testing of this new package still needs to happen.

Cheers,
Georg

Bug#965629: libclass-pluggable-perl: diff for NMU version 0.022-2.2

[gregor herrmann]

Control: tags 965629 + patch
Control: tags 965629 + pending
Control: tags 998922 + patch
Control: tags 998922 + pending


Dear maintainer,

I've prepared an NMU for libclass-pluggable-perl (versioned as 0.022-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libclass-pluggable-perl-0.022/debian/changelog libclass-pluggable-perl-0.022/debian/changelog
--- libclass-pluggable-perl-0.022/debian/changelog
+++ libclass-pluggable-perl-0.022/debian/changelog
@@ -1,3 +1,15 @@
+libclass-pluggable-perl (0.022-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965629)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #998922)
+
+ -- gregor herrmann   Mon, 27 Dec 2021 00:02:46 +0100
+
 libclass-pluggable-perl (0.022-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libclass-pluggable-perl-0.022/debian/compat libclass-pluggable-perl-0.022/debian/compat
--- libclass-pluggable-perl-0.022/debian/compat
+++ libclass-pluggable-perl-0.022/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libclass-pluggable-perl-0.022/debian/control libclass-pluggable-perl-0.022/debian/control
--- libclass-pluggable-perl-0.022/debian/control
+++ libclass-pluggable-perl-0.022/debian/control
@@ -1,7 +1,7 @@
 Source: libclass-pluggable-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0)
+Build-Depends: debhelper (>= 7.0.0)
 Build-Depends-Indep: perl (>= 5.8.8-12)
 Maintainer:  Sarah Connor 
 Standards-Version: 3.7.3
diff -u libclass-pluggable-perl-0.022/debian/rules libclass-pluggable-perl-0.022/debian/rules
--- libclass-pluggable-perl-0.022/debian/rules
+++ libclass-pluggable-perl-0.022/debian/rules
@@ -19,7 +19,9 @@
 
 TMP =$(CURDIR)/debian/$(PACKAGE)
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -73,4 +75,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#965633: libdata-javascript-anon-perl: diff for NMU version 1.03-2.2

[gregor herrmann]

Control: tags 965633 + patch
Control: tags 965633 + pending


Dear maintainer,

I've prepared an NMU for libdata-javascript-anon-perl (versioned as 1.03-2.2) 
and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libdata-javascript-anon-perl-1.03/debian/changelog libdata-javascript-anon-perl-1.03/debian/changelog
--- libdata-javascript-anon-perl-1.03/debian/changelog
+++ libdata-javascript-anon-perl-1.03/debian/changelog
@@ -1,3 +1,12 @@
+libdata-javascript-anon-perl (1.03-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965633)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 23:57:28 +0100
+
 libdata-javascript-anon-perl (1.03-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libdata-javascript-anon-perl-1.03/debian/compat libdata-javascript-anon-perl-1.03/debian/compat
--- libdata-javascript-anon-perl-1.03/debian/compat
+++ libdata-javascript-anon-perl-1.03/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libdata-javascript-anon-perl-1.03/debian/control libdata-javascript-anon-perl-1.03/debian/control
--- libdata-javascript-anon-perl-1.03/debian/control
+++ libdata-javascript-anon-perl-1.03/debian/control
@@ -1,7 +1,7 @@
 Source: libdata-javascript-anon-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0), cdbs
+Build-Depends: debhelper (>= 7.0.0), cdbs
 Build-Depends-Indep: perl (>= 5.8.8-7), libparams-util-perl, libclass-default-perl
 Maintainer: Taku YASUI 
 HomePage: http://search.cpan.org/dist/Data-JavaScript-Anon/


signature.asc
Description: Digital Signature

Bug#965637: libdatapager-perl: diff for NMU version 0.01-2.2

[gregor herrmann]

Control: tags 965637 + patch
Control: tags 965637 + pending


Dear maintainer,

I've prepared an NMU for libdatapager-perl (versioned as 0.01-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libdatapager-perl-0.01/debian/changelog libdatapager-perl-0.01/debian/changelog
--- libdatapager-perl-0.01/debian/changelog
+++ libdatapager-perl-0.01/debian/changelog
@@ -1,3 +1,12 @@
+libdatapager-perl (0.01-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965637)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 23:53:07 +0100
+
 libdatapager-perl (0.01-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libdatapager-perl-0.01/debian/compat libdatapager-perl-0.01/debian/compat
--- libdatapager-perl-0.01/debian/compat
+++ libdatapager-perl-0.01/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libdatapager-perl-0.01/debian/control libdatapager-perl-0.01/debian/control
--- libdatapager-perl-0.01/debian/control
+++ libdatapager-perl-0.01/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Maintainer: Dmitry E. Oboukhov 
-Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5)
+Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 7)
 Standards-Version: 3.8.0
 Homepage: http://search.cpan.org/~vidul/
 


signature.asc
Description: Digital Signature

Bug#965643: libhtml-popuptreeselect-perl: diff for NMU version 1.6-7.2

[gregor herrmann]

Control: tags 965643 + patch
Control: tags 965643 + pending


Dear maintainer,

I've prepared an NMU for libhtml-popuptreeselect-perl (versioned as 1.6-7.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libhtml-popuptreeselect-perl-1.6/debian/changelog libhtml-popuptreeselect-perl-1.6/debian/changelog
--- libhtml-popuptreeselect-perl-1.6/debian/changelog
+++ libhtml-popuptreeselect-perl-1.6/debian/changelog
@@ -1,3 +1,12 @@
+libhtml-popuptreeselect-perl (1.6-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965643)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 23:42:15 +0100
+
 libhtml-popuptreeselect-perl (1.6-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libhtml-popuptreeselect-perl-1.6/debian/compat libhtml-popuptreeselect-perl-1.6/debian/compat
--- libhtml-popuptreeselect-perl-1.6/debian/compat
+++ libhtml-popuptreeselect-perl-1.6/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libhtml-popuptreeselect-perl-1.6/debian/control libhtml-popuptreeselect-perl-1.6/debian/control
--- libhtml-popuptreeselect-perl-1.6/debian/control
+++ libhtml-popuptreeselect-perl-1.6/debian/control
@@ -1,7 +1,7 @@
 Source: libhtml-popuptreeselect-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0), cdbs, quilt
+Build-Depends: debhelper (>= 7.0.0), cdbs, quilt
 Build-Depends-Indep: perl (>= 5.8.0-7), libhtml-template-perl (>= 2.6)
 Maintainer: Taku YASUI 
 HomePage: http://search.cpan.org/dist/HTML-PopupTreeSelect/


signature.asc
Description: Digital Signature

Bug#1002666: torbrowser-launcher: Package in Bullseye outdated and downloading Tbb fails because of bad certificate

[Richard Z]

Package: torbrowser-launcher
Version: 0.3.3-6
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: r...@linux-m68k.org

Dear Maintainer,


the version in Bullseye seems to old, it never succeeds
downloading the Tor Browser. I see there are newer packages
in testing/unstable, could those be backported?

Best Regards,

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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates20210119
ii  gnupg  2.2.27-2
ii  libdbus-glib-1-2   0.110-6
ii  python33.9.2-3
ii  python3-gpg1.14.0-1+b2
ii  python3-packaging  20.9-2
ii  python3-pyqt5  5.15.2+dfsg-3
ii  python3-requests   2.25.1+dfsg-2
ii  python3-socks  1.7.1+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.4.5.10-1~deb11u1

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.6-10

Bug#1002665: ITP: spidev -- Python bindings for Linux SPI access

[Anton Gladky]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: spidev
  Version : 3.5
  Upstream Author : Volker Thoms 
* URL : https://github.com/doceme/py-spidev/
* License : MIT
  Programming Lang: Python
  Description : Python bindings for Linux SPI access


This project contains a python module for interfacing with SPI devices
from user space via the spidev linux kernel driver.

The package will be maintained under Debian-electronics-team.


Regards,

Anton

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmHI8EIRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wYpeA/7BPOhPMITQo+QGTWy0WajNvFx27XTRq79
kTn8fuJoON4bJPpSXGHCMwU8tuUhjgAho5ZRtzpkq/ZY3ra+CZFYMaosXOzaeBx/
shR4fup5+iciroof1tUdrQ0FXw9s0xIUgs5Cw/m/z5lhBfMO1pnGeTX91mS45xrz
Oi0xqmZ2cjq5PUKldjCrCxHdXNENbymLWsMyYE+pZfAA5DKhd3mH/12rr0W/BePX
93EMQNf+0EMa74aU/YZU4ANEr9GTwlyW4Np54wEtZug6YLlH2Hn7v8taDiYtsCUC
UGx/1EoTVtaSt6vMQB/ij3vMeo4zdqYXFPqwXv0YP4bB/576ay4jBh3MHcqDTDQT
SFXXBAWimMsrfnq6hHVwoeqW+ihO8RqaPqtKrLBXB3BPVP+sItmr5RYVQ4/1YrsE
grVSth7gOPZNTXAba+VRZ7hcuzQKSF2XRhnBr2fR+4H8CXS7v0WXQC/q2xprFlIj
a+4p1nYlaJQ9VpyswO9e9WPHFNZszdU4KkBFCtqr8cJP5ncXP5EAmLrzxOSII4ow
0HA4t0h0rHfclnpkCFQ6DM+qcKX37Oj6P5m+7BGmZM4PlUNCeSK1rZ4odwRqL5z1
t4oBc8/JYAXGc4sMIJORi8/luM1Ygzil8x/wC8kxyRcQ291hpAFfhF+xnsfvbpYg
bZo4g3oCGDs=
=l1pT
-END PGP SIGNATURE-

Bug#965647: libio-dirent-perl: diff for NMU version 0.05-1.1

[gregor herrmann]

Control: tags 965647 + patch
Control: tags 965647 + pending
Control: tags 999278 + patch
Control: tags 999278 + pending


Dear maintainer,

I've prepared an NMU for libio-dirent-perl (versioned as 0.05-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libio-dirent-perl-0.05/debian/control libio-dirent-perl-0.05/debian/control
--- libio-dirent-perl-0.05/debian/control
+++ libio-dirent-perl-0.05/debian/control
@@ -1,7 +1,7 @@
 Source: libio-dirent-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0), perl (>= 5.8.8-7etch1)
+Build-Depends: debhelper (>= 7.0.0), perl (>= 5.8.8-7etch1)
 Maintainer: Ludovic Drolez 
 Standards-Version: 3.9.3
 
diff -u libio-dirent-perl-0.05/debian/rules libio-dirent-perl-0.05/debian/rules
--- libio-dirent-perl-0.05/debian/rules
+++ libio-dirent-perl-0.05/debian/rules
@@ -28,7 +28,9 @@
 CFLAGS += -O2
 endif
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -94,4 +96,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary
diff -u libio-dirent-perl-0.05/debian/changelog libio-dirent-perl-0.05/debian/changelog
--- libio-dirent-perl-0.05/debian/changelog
+++ libio-dirent-perl-0.05/debian/changelog
@@ -1,3 +1,15 @@
+libio-dirent-perl (0.05-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965647)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999278)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 23:36:39 +0100
+
 libio-dirent-perl (0.05-1) unstable; urgency=low
 
   * New upstream release
diff -u libio-dirent-perl-0.05/debian/compat libio-dirent-perl-0.05/debian/compat
--- libio-dirent-perl-0.05/debian/compat
+++ libio-dirent-perl-0.05/debian/compat
@@ -1 +1 @@
-5
+7


signature.asc
Description: Digital Signature

Bug#965652: libjcode-pm-perl: diff for NMU version 2.06-1.1

[gregor herrmann]

Control: tags 965652 + patch
Control: tags 965652 + pending
Control: tags 999237 + patch
Control: tags 999237 + pending


Dear maintainer,

I've prepared an NMU for libjcode-pm-perl (versioned as 2.06-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libjcode-pm-perl-2.06/debian/changelog libjcode-pm-perl-2.06/debian/changelog
--- libjcode-pm-perl-2.06/debian/changelog
+++ libjcode-pm-perl-2.06/debian/changelog
@@ -1,3 +1,15 @@
+libjcode-pm-perl (2.06-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965652)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999237)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 23:28:02 +0100
+
 libjcode-pm-perl (2.06-1) unstable; urgency=low
 
   * New upstream Release.
diff -u libjcode-pm-perl-2.06/debian/compat libjcode-pm-perl-2.06/debian/compat
--- libjcode-pm-perl-2.06/debian/compat
+++ libjcode-pm-perl-2.06/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libjcode-pm-perl-2.06/debian/control libjcode-pm-perl-2.06/debian/control
--- libjcode-pm-perl-2.06/debian/control
+++ libjcode-pm-perl-2.06/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Maintainer: Atsushi KAMOSHIDA 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Standards-Version: 3.7.2
 
 Package: libjcode-pm-perl
diff -u libjcode-pm-perl-2.06/debian/rules libjcode-pm-perl-2.06/debian/rules
--- libjcode-pm-perl-2.06/debian/rules
+++ libjcode-pm-perl-2.06/debian/rules
@@ -30,6 +30,9 @@
 	touch configure-stamp
 
 
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build: build-stamp
 
 build-stamp: configure-stamp 
@@ -103,4 +106,4 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary install configure


signature.asc
Description: Digital Signature

Bug#935980: Found in bullseye version, maybe

[Christopher David Howie]

I still experience this bug in bullseye, but I've done some testing
using the same exact version of jackd as the network master and (so far)
everything seems to be working, so this might only be an issue when
using networked audio with mismatching jackd versions.  I will continue
to test over the next few days and close this bug if there are no more
issues.

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5


IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

Bug#995286: lintian: new-package-should-not-package-python2-module false positive for python-*-doc packages

[Sandro Tosi]

On Wed, 29 Sep 2021 10:13:53 +0300 Andrius Merkys  wrote:
> Package: lintian
> Version: 2.106.1
>
> Hello,
>
> lintian emits false positive
> new-package-should-not-package-python2-module tag for Python
> python-*-doc packages [1]. This could be fixed by skipping binary
> packages from Section: doc.
>
> [1]
> https://lintian.debian.org/tags/new-package-should-not-package-python2-module

this has been reported 3 months ago and it's still happening, please fix asap

Bug#965659: liblog-dispatch-filerotate-perl: diff for NMU version 1.19-1.2

[gregor herrmann]

Control: tags 965659 + patch
Control: tags 965659 + pending
Control: tags 999205 + patch
Control: tags 999205 + pending


Dear maintainer,

I've prepared an NMU for liblog-dispatch-filerotate-perl (versioned as 
1.19-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u liblog-dispatch-filerotate-perl-1.19/debian/changelog liblog-dispatch-filerotate-perl-1.19/debian/changelog
--- liblog-dispatch-filerotate-perl-1.19/debian/changelog
+++ liblog-dispatch-filerotate-perl-1.19/debian/changelog
@@ -1,3 +1,15 @@
+liblog-dispatch-filerotate-perl (1.19-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965659)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999205)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 23:21:45 +0100
+
 liblog-dispatch-filerotate-perl (1.19-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u liblog-dispatch-filerotate-perl-1.19/debian/compat liblog-dispatch-filerotate-perl-1.19/debian/compat
--- liblog-dispatch-filerotate-perl-1.19/debian/compat
+++ liblog-dispatch-filerotate-perl-1.19/debian/compat
@@ -1 +1 @@
-5
+7
diff -u liblog-dispatch-filerotate-perl-1.19/debian/control liblog-dispatch-filerotate-perl-1.19/debian/control
--- liblog-dispatch-filerotate-perl-1.19/debian/control
+++ liblog-dispatch-filerotate-perl-1.19/debian/control
@@ -1,7 +1,7 @@
 Source: liblog-dispatch-filerotate-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5), quilt
+Build-Depends: debhelper (>= 7), quilt
 Build-Depends-Indep: perl (>= 5.6.10-12), liblog-log4perl-perl, libdate-manip-perl, liblog-dispatch-perl, libparams-validate-perl
 Maintainer: Matthias Schmitz 
 Standards-Version: 3.8.1
diff -u liblog-dispatch-filerotate-perl-1.19/debian/rules liblog-dispatch-filerotate-perl-1.19/debian/rules
--- liblog-dispatch-filerotate-perl-1.19/debian/rules
+++ liblog-dispatch-filerotate-perl-1.19/debian/rules
@@ -17,7 +17,9 @@
 
 include /usr/share/quilt/quilt.make
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp: patch
 	dh_testdir
 	# Add commands to compile the package here
@@ -67,4 +69,4 @@
 get-orig-source:
 	uscan --force-download
 
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary install


signature.asc
Description: Digital Signature

Bug#1002664: ITP: opn-cli -- CLI Interface for OPNsense Firewall using API Requests

[debian]

Package: wnpp
Severity: normal

* Package name: opn-cli
* URL: https://github.com/andeman/opn-cli
* License: BSD-2
* Description: CLI Interface for OPNsense Firewall using API Requests
* the OPNsense CLI written in python.

Bug#1002651: Please cherry-pick the commits after the 3.38.6 release from upstream to bullseye-updates

[Amr Ibrahim]

Am Sonntag, dem 26.12.2021 um 20:18 + schrieb Simon McVittie:
> 
> Which commits do you have in mind and what bugs do they fix? The more
> we backport, the higher the risk of regressions is, particularly if
> those commits aren't in a formal release yet.

Yes, they aren't in a formal release yet, however, since they come from
the gnome-3-38 branch, the risk is minimized I believe.


> 0db4ac73 "wayland/subsurface: Check for parent actor before
> unparenting",
> 60afd63e "wayland/subsurface: Handle node unlinking on parent
> destroyed",
> 58343f43 "window-actor/wayland: Remove subsurface actors on dispose"
> seem to be fixing crashes with native Wayland apps that use
> subsurfaces, and in particular Firefox. Is that correct?

Yes, that's correct. They fix this issue in particular:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1892



> bb85f21d "xwayland: Fix condition for queuing a window to
> META_QUEUE_CALC_SHOWING" seems to be preventing unnecessary event
> messages from being sent to X11 apps in Wayland, so it's fixing a
> performance problem. Is that correct?

Correct. That's actually a regression starting from 3.36 due to a typo:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1955



> 5a6b3c4b "wayland/data-offer: Accept final preferrence of drop
> destination" seems to be fixing a protocol error that would result in
> Firefox being terminated during Alt + drag-and-drop. Is that correct?

Yes, correct. It fixes this bug:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1952



> 15ac84da "surface-actor: Fix unobscurred_fraction calculation" seems
> to be fixing an incorrect refresh rate when fullscreen apps in
> multi-monitor setups use Vsync. Is that correct?

Correct. It fixes this bug:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1971



> For a9e60bad "wayland/surface: Switch order for calculating surface
> damage",
> aeda2cbc "wayland/surface: Use correct default viewport for surface
> damage",
> 0b26ad63 "wayland/surface: Do not uncoditionally process surface
> damage"
> I don't understand what bug they are fixing, so I am going to find it
> hard to "sell" this change to the release team: we can't weigh up
> benefit vs. regression risk if we don't understand the benefit. If
> you need these changes, please could you explain the impact to
> bullseye users of not having them?

Unfortunately I also don't have an explanation.


> I've also asked for clarification on the upstream MR
> .

You were also mentioned in the backport MR:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2178

Bug#1002663: busybox: new upstream version

[Christoph Anton Mitterer]

Package: busybox
Version: 1:1.30.1-7+b2
Severity: wishlist

Hey.

Today, 1.35 was released.
Would be nice to see that upgraded :-)

Thanks,
Chris.

Bug#964785: ITP: shutter -- feature-rich screenshot program

[Michael Kogan]

Hello Sebastian, hello everybody!

Sorry to bother again, is there anything else which can be done from
upstream to make things move forward? Thanks!

Merry Christmas!
Michael

Bug#1001368: pygobject: autopkgtest needs update for python3.10: ImportWarning: DynamicImporter.exec_module() not found

[Simon McVittie]

Control: clone -1 -2
Control: tags -1 + pending
Control: retitle -2 pygobject: gi.importer.DynamicImporter should implement 
PEP-0451
Control: severity -2 normal
Control: user debian...@lists.debian.org
Control: usertags -2 - needs-update

On Thu, 09 Dec 2021 at 09:55:49 +0100, Paul Gevers wrote:
> python3-all  FAIL stderr: :671:
> ImportWarning: DynamicImporter.exec_module() not found; falling back to
> load_module()

Minimal reproducer:

$ python3.10 -Wall
>>> from gi.repository import GLib

Good result: no warning; bad result; the same ImportWarning seen above.

For now, I'm going to make the ImportWarning stop failing the test, by
adding the allow-stderr restriction.

This solves the autopkgtest failure, which is RC, but does not solve the
underlying non-RC bug: pygobject should implement the new PEP-0451 methods.

I've cloned "pygobject: gi.importer.DynamicImporter should implement
PEP-0451" to represent the underlying bug. This might become RC when we
go to python3.11 or python3.12 or something, if it is not solved upstream
before then, but is not RC *yet*.

I am not sufficiently familiar with the finer points of the Python import
mechanism to be able to reimplement pygobject's import hooks for PEP-0451.

smcv

Bug#974616: nomacs: "charset=Ascii" appears before the comment of the image

[Sergio Gelato]

Control: tags -1 + upstream

This *is* an upstream bug, as the upstream README.md has build instructions for 
Ubuntu that list libexiv2-dev (no version constraint given) as a required 
package.

As far as I can tell, it's unaddressed as of the current tip of the master 
branch. I don't see that anyone has reported it as an issue on GitHub either. 
(I don't want a GitHub account, so I won't report it myself.)

My only interest in this bug is that it has kept nomacs out of bullseye; I 
don't need its EXIF support. If this package isn't effectively orphaned, 
perhaps the maintainer can lower the bug's severity? (And/or forward the report 
upstream...)

Bug#1002661: gegl: CVE-2021-45463

[Salvatore Bonaccorso]

Source: gegl
Version: 1:0.4.32-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gegl.

CVE-2021-45463[0]:
| GEGL before 0.4.34, as used (for example) in GIMP before 2.10.30,
| allows shell expansion when a pathname in a constructed command line
| is not escaped or filtered. This is caused by use of the system
| library function for execution of the ImageMagick convert fallback in
| magick-load.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-45463
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45463

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#999312: An updated version was just uploaded

[Jose Antonio Quevedo]

Hi there!


I've just uploaded an updated version of this package [0] which will
hopefully fix this bug. I also already fulfilled the consequent RFS bug [1].

Could you provide some more time to let this package being properly
reviewed and uploaded by a mentor before being automatically removed
from the repository please?


[0] https://mentors.debian.net/package/ssed/

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002659


Thanks. Kind regards.

--

Jose Antonio Quevedo Muñoz






OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002660: firmware-sof-signed: Sound/Mic does not work on Dell XPS 17 9710

[Juan Francisco Miranda Aguilar]

Package: firmware-sof-signed
Version: 1.9-1
Severity: important

Hi dear maintainer,

I have updated to the latest version, and my kernel is the latest
available for debian sid, 5.15.0-2.
and it's working fine, both, sound and mic, but when I play a video
from youtube, for example, before it
get started, I can hear like a clack sound, and the same when the
video is ended or paused, and it's always on the
same speaker, the left one. Even sometimes, I cannot hear anything on
this speaker for a while, but if I boot
on Windows, it works without any problem.

Best regards,

Juan Francisco.


El lun, 11 oct 2021 a las 19:12, Juan Francisco Miranda Aguilar (<
jfmira...@gmail.com>) escribió:

> Package: firmware-sof-signed
> Version: 1.7-1
> Severity: important
>
> Dear Maintainer,
>
> I installed the firmware-sof-signed package on a Dell XPS 17 9710 and still 
> no sound nor mic was detected.
> Any advise is welcome!
>
> Thanks!
>
> root@dell:/home/jf# lspci | grep audio
> 00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-H HD Audio 
> Controller (rev 11)
> root@dell:/home/jf# dmesg | egrep "audio|sof|snd"
> [0.852738] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> [0.852739] software IO TLB: mapped [mem 
> 0x4e601000-0x52601000] (64MB)
> [1.040833] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 
> 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
> [1.040841] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 
> 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
> [2.470636] snd_hda_intel :00:1f.3: DSP detected with PCI 
> class/subclass/prog-if info 0x040100
> [2.470791] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ 
> platform, using SOF driver
> [2.510153] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
> class/subclass/prog-if info 0x040100
> [2.510215] sof-audio-pci-intel-tgl :00:1f.3: SoundWire enabled on 
> CannonLake+ platform, using SOF driver
> [2.510247] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 
> 0002)
> [2.510477] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
> class/subclass/prog-if 0x040100
> [2.510517] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops 
> i915_audio_component_bind_ops [i915])
> [2.516978] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
> [2.531676] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4
> [2.532987] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading 
> firmware intel/sof/sof-tgl-h.ri
> [2.532992] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
> 1:7:0-47d07
> [2.533026] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:18:1 
> Kernel ABI 3:18:0
> [2.533028] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man 
> header type 3 size 0x30
> [2.614333] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
> 1:7:0-47d07
> [2.614336] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:18:1 
> Kernel ABI 3:18:0
> [3.691121] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading 
> firmware intel/sof-tplg/sof-tgl-rt711-rt1308-rt715.tplg
> [3.691129] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:18:1 
> Kernel ABI 3:18:0
> [3.710385] sof-audio-pci-intel-tgl :00:1f.3: ASoC: physical link 
> SDW3-Capture (id 4) not exist
> [3.710389] sof-audio-pci-intel-tgl :00:1f.3: ASoC: topology: could 
> not load header: -22
> [3.710526] sof-audio-pci-intel-tgl :00:1f.3: error: tplg component 
> load failed -22
> [3.710531] sof-audio-pci-intel-tgl :00:1f.3: error: failed to load 
> DSP topology -22
> [3.710532] sof-audio-pci-intel-tgl :00:1f.3: ASoC: error at 
> snd_soc_component_probe on :00:1f.3: -22
> [3.710561] sof_sdw sof_sdw: ASoC: failed to instantiate card -22
> [3.720900] sof_sdw sof_sdw: snd_soc_register_card failed -22
> [3.720901] sof_sdw: probe of sof_sdw failed with error -22
>
>

Bug#1002659: RFS: ssed/3.6.2-8 - super sed stream editor

[Jose Antonio Quevedo]

Package: sponsorship-requests

Severity: normal


Dear mentors,

I am looking for a sponsor for my package "ssed":

 * Package name: ssed
   Version : 3.6.2-8
   Upstream Author : Paolo Bonzini
 * URL : http://sed.sf.net/grabbag/ssed/
 * License : GPL-2+
   Section : utils

It builds those binary packages:

  ssed - super sed stream editor

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/ssed/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/s/ssed/ssed_3.62-8.dsc


Changes since the last upload:

  * Added build-arch and build-indep targets (closes: #999312)
  * Added testsuite.
  * Added hardening flags to debian/rules.
  * Upgraded debian source format to 3.0 (quilt).
  * Updated standards version to 4.3.0.
  * Updated copyright to DEP-5 standard.
  * Updated debhelper dependency and compat version to 10.
  * Updated package priority from extra to optional.
  * Updated config.guess config.sub in config.
  * Removed autotools-dev dependency.
  * Removed initial article from description


I would be glad if someone uploaded this package for me.

Kind regards,
--
Jose Antonio Quevedo Muñoz



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002651: Please cherry-pick the commits after the 3.38.6 release from upstream to bullseye-updates

[Simon McVittie]

On Sun, 26 Dec 2021 at 16:28:36 +, Amr Ibrahim wrote:
> Please cherry-pick the commits after the 3.38.6 release from upstream
> gnome-3-38 branch to bullseye-updates. Or maybe upstream could release
> 3.38.7.
> 
> The commits are Wayland fixes mainly for the sake of newer versions of
> Firefox, which can be installed as a flatpak in Debian 11.

Which commits do you have in mind and what bugs do they fix? The more
we backport, the higher the risk of regressions is, particularly if those
commits aren't in a formal release yet.

0db4ac73 "wayland/subsurface: Check for parent actor before unparenting",
60afd63e "wayland/subsurface: Handle node unlinking on parent destroyed",
58343f43 "window-actor/wayland: Remove subsurface actors on dispose"
seem to be fixing crashes with native Wayland apps that use subsurfaces,
and in particular Firefox. Is that correct?

bb85f21d "xwayland: Fix condition for queuing a window to
META_QUEUE_CALC_SHOWING" seems to be preventing unnecessary event messages
from being sent to X11 apps in Wayland, so it's fixing a performance problem.
Is that correct?

5a6b3c4b "wayland/data-offer: Accept final preferrence of drop destination"
seems to be fixing a protocol error that would result in Firefox being
terminated during Alt + drag-and-drop. Is that correct?

15ac84da "surface-actor: Fix unobscurred_fraction calculation" seems to be
fixing an incorrect refresh rate when fullscreen apps in multi-monitor
setups use Vsync. Is that correct?

For
a9e60bad "wayland/surface: Switch order for calculating surface damage",
aeda2cbc "wayland/surface: Use correct default viewport for surface damage",
0b26ad63 "wayland/surface: Do not uncoditionally process surface damage"
I don't understand what bug they are fixing, so I am going to find it hard
to "sell" this change to the release team: we can't weigh up benefit vs.
regression risk if we don't understand the benefit. If you need these changes,
please could you explain the impact to bullseye users of not having them?
I've also asked for clarification on the upstream MR
.

Thanks,
smcv

Bug#1002658: FTBFS with OCaml 4.13.1

[Stéphane Glondu]

Source: xen
Version: 4.14.3+32-g9de3671772-1
Severity: important
Tags: ftbfs

Dear Maintainer,

Your package FTBFS with OCaml 4.13.1 with the following error:
> x86_64-linux-gnu-gcc -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer 
> -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MP -MF 
> .xentoollog_stubs.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
> -ffile-prefix-map=/tmp/build/xen-4.14.3+32-g9de3671772=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Werror -I/usr/lib/ocaml 
> -Wno-declaration-after-statement 
> -I/tmp/build/xen-4.14.3+32-g9de3671772/tools/ocaml/libs/xentoollog/../../../../tools/libs/toollog/include
>  
> -I/tmp/build/xen-4.14.3+32-g9de3671772/tools/ocaml/libs/xentoollog/../../../../tools/include
>   -c -o xentoollog_stubs.o xentoollog_stubs.c
> xentoollog_stubs.c:57: error: "Some_val" redefined [-Werror]
>57 | #define Some_val(v) Field(v,0)
>   | 
> In file included from /usr/lib/ocaml/caml/alloc.h:24,
>  from xentoollog_stubs.c:23:
> /usr/lib/ocaml/caml/mlvalues.h:404: note: this is the location of the 
> previous definition
>   404 | #define Some_val(v) Field(v, 0)
>   | 
> cc1: all warnings being treated as errors

Packages rebuilt with OCaml 4.13.1 are available at:

  https://ocaml.debian.net/transitions/ocaml-4.13.1/


Cheers,

-- 
Stéphane

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

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

Bug#1002657: FTBFS with OCaml 4.13.1

[Stéphane Glondu]

Source: sks
Version: 1.1.6+git20210302.c3ba6d5a-3
Severity: important
Tags: ftbfs

Dear Maintainer,

Your package FTBFS with OCaml 4.13.1 with the following error:
> File "mList.ml", line 203, characters 14-23:
> 203 |   let slist = List.sort compare list in
> ^
> Error (warning 6 [labels-omitted]): label cmp was omitted in the application 
> of this function.
> File "mList.ml", line 211, characters 14-23:
> 211 |   let slist = List.sort compare list in
> ^
> Error (warning 6 [labels-omitted]): label cmp was omitted in the application 
> of this function.

Packages rebuilt with OCaml 4.13.1 are available at:

  https://ocaml.debian.net/transitions/ocaml-4.13.1/


Cheers,

-- 
Stéphane

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

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

Bug#1002654: reportbug: Please report Desktop Environment which a user has logged in

[Sandro Tosi]

control: tags -1 +moreinfo

Hello Nicholas,

> Please consider to include this information to bug reports to help
> maintainers investigate issues in GUI applications. It could looks like

can you elaborate more why this information would be useful? can you
provide at least a handful of bugs example where this information was
missing and instead would have been nice to have early in the
debugging process? please also note that, if you're application really
depends tightly on the DE used, you can collect additional information
using bug scripts:
https://salsa.debian.org/reportbug-team/reportbug/-/blob/master/doc/README.developers#L10

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1000200: reportbug-gtk: cannot close reportbug (on fluxbox)

[Nis Martensen]

control: reassign -1 reportbug-gtk
control: severity -1 important
control: tags -1 - moreinfo


> Update: The bug was introduced with the upload of python3.9 3.9.8-1 to
> unstable on 7 November. Downgrading python3.9 to version 3.9.7-4 fixes
> the problem.
> 
> Next tasks: Identify which change between python 3.9.7 and 3.9.8 is
> responsible, and find out which package needs to change to fix the problem.

The broken code is in reportbug. Reassigning back.

This bug is a case of broken code being exposed by a bug fix elsewhere.
Reportbug was trying to use sys.exit() to exit the program, which does
not work reliably when threading is involved as in the GTK UI. Due to a
bug in python it had only appeared to work.

Bug#1002656: bridge-utils: bridge_hw: add random option like for ifupdown hwaddress

[Martin-Éric Racine]

Package: bridge-utils
Version: 1.7-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It would be desirable for bridge_hw to be able to generate a random MAC address 
as per ifupdown's generic hwaddress syntax.

Possible values for bridge_hw would thereafter be:

MAC
interface
random

MAC|interface would continue working as currently, while random would generate 
a random MAC address for the bridge.

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

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

Versions of packages bridge-utils depends on:
ii  libc6  2.31-13+deb11u2

bridge-utils recommends no packages.

Versions of packages bridge-utils suggests:
ii  ifupdown  0.8.36

- -- Configuration Files:
/etc/default/bridge-utils changed:
BRIDGE_HOTPLUG=yes


- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmHIyO0ACgkQrh+Cd8S0
17Yraw/+ORSlJr3mNO42CukYENJpgIQ+DPGgHNsaJJvzYZIqFR+3NS9hJXQpoEJ/
TmFd10iLwzIshvpyc+Bs7LqceXw+PDYR3wW+rPJy567seD7H9ddf9H0XNdY5diFR
NO4z4IK+NDyfs/Bjy1cn4SuOC5YO8exRnZLZgrDQ/uGNalk6haOmoZag3J637b9y
y7Dw7edhvxo5wQw036mx5cc+46gtMOgaphH4jOmfy9lp3UMxsNMRJCSlzcZIbYy/
0K62PVhHaFDbmk/kSKDenmtVySklPhbow3uQtHuybYTNjGlXOwImA2LTHDPcEECi
ZfdOM3n2h80iwlk2qLFrySDMbSGQDQwR6YMsjPY4Yd6oSGSovlkPgrd4YZ2o6xvf
I91CsdICodkbydQjzJkrvhjnI1W/LqXj49+eeSz5fYqE7TbVqp6KD6uoiclW2yI+
qVUdzP7jJVqUeE3StzvL09sXqiw/JrjXyl1y412hCRoVGJQl2Lgj7vvKYcItRZs7
cMWk8P+KYHhyxXkrddjdGJvVylMquu7H1b6AHNVjniu+ui88vvb1zpLudzvpHwh2
wpdAd4M/a+4/j8/jVl3wydp8rvHmrc9MkB84MsXTB+uaJP86GSJeo24XOas1uN5m
yjIkl8Vexjh1+QQaWcP14T2upnM7uY1Sj/5AyFrjk8SJIL5+mlM=
=P6wb
-END PGP SIGNATURE-

Bug#1002655: mirror listing update for mirror.surf

[Dmitry Shishkin]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: mirror.surf
Type: leaf
Archive-architecture: amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Dmitry Shishkin 
Country: RU Russian Federation
Location: Nizhny Novgorod
Sponsor: Dmitry Shishkin https://shishkin.us




Trace Url: http://mirror.surf/debian/project/trace/
Trace Url: http://mirror.surf/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.surf/debian/project/trace/mirror.surf

Bug#1001977: src:telegram-desktop: fails to migrate to testing for too long: FTBFS on mipsel

[Nicholas Guriev]

Control: fixed -1 3.3.0+ds-2

Hello!

The latest version I have uploaded is successfully built on every
release architecture. And the package is now permitted to go to testing
if no critical issues arise.



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

Bug#965667: libnet-proxy-perl: diff for NMU version 0.12-6.2

[gregor herrmann]

Control: tags 965667 + patch
Control: tags 965667 + pending


Dear maintainer,

I've prepared an NMU for libnet-proxy-perl (versioned as 0.12-6.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libnet-proxy-perl-0.12/debian/changelog libnet-proxy-perl-0.12/debian/changelog
--- libnet-proxy-perl-0.12/debian/changelog
+++ libnet-proxy-perl-0.12/debian/changelog
@@ -1,3 +1,12 @@
+libnet-proxy-perl (0.12-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965667)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 20:17:16 +0100
+
 libnet-proxy-perl (0.12-6.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libnet-proxy-perl-0.12/debian/compat libnet-proxy-perl-0.12/debian/compat
--- libnet-proxy-perl-0.12/debian/compat
+++ libnet-proxy-perl-0.12/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libnet-proxy-perl-0.12/debian/control libnet-proxy-perl-0.12/debian/control
--- libnet-proxy-perl-0.12/debian/control
+++ libnet-proxy-perl-0.12/debian/control
@@ -1,7 +1,7 @@
 Source: libnet-proxy-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0), libmodule-build-perl
+Build-Depends: debhelper (>= 7.0.0), libmodule-build-perl
 Build-Depends-Indep: perl (>= 5.8.8-11.1)
 Maintainer: Michael Ablassmeier 
 Standards-Version: 3.8.0


signature.asc
Description: Digital Signature

Bug#976334: libgtk-3-0: File choser does not display the list of folders on NFS access

[Simon McVittie]

On Thu, 02 Dec 2021 at 21:43:30 +, Ian Campbell wrote:
> On Tue, 2021-11-30 at 11:03 +, Simon McVittie wrote:
> > It seems that this bug occurs when GtkSearchEngineModel is the only
> > backend returning results, so a workaround is to have have a second
> > search backend available (I don't know what this means specifically, but
> > presumably a full GNOME desktop might have a second backend, otherwise
> > this failure mode would have been seen more often).
> 
> There seems to be a network filesystem component too, which I'd guess
> reduces the likelihood of it being seen quite so often as it would
> otherwise be.

I think it might work something like this:

* it is sufficient to have a single working backned;

* if you're on a "full" GNOME desktop, then you have Tracker, which
  provides a separate search backend;

* or if you're on a local filesystem, then GTK's built-in
  GtkSearchEngineSimple can be used (it disables itself automatically on
  remote filesystems because that would be slow);

* but if you're on NFS *and* you don't have Tracker, then you can
  experience this bug

smcv

Bug#1002654: reportbug: Please report Desktop Environment which a user has logged in

[Nicholas Guriev]

Package: reportbug
Severity: wishlist

Dear Maintainers,

reportbug(1) supplies system information when generating a bug template.

> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

I believe it would be desirable to have a line about desktop environment
used by a reporter. The tool can identify DE via the XDG_CURRENT_DESKTOP
environment variable mentioned in Desktop Entry Specification[1].
pam_systemd(8) sets the XDG_SESSION_TYPE, the XDG_SESSION_CLASS, and the
XDG_SESSION_DESKTOP environment variables; they can be taken into
account as well. The legacy and non-standardized DESKTOP_SESSION
environment variable could also be read.

 [1]: 
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html

Please consider to include this information to bug reports to help
maintainers investigate issues in GUI applications. It could looks like

> DE: MATE

or

> DE: XFCE



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

Bug#965668: libmp4-info-perl: diff for NMU version 1.13-1.2

[gregor herrmann]

Control: tags 965668 + patch
Control: tags 965668 + pending
Control: tags 998957 + patch
Control: tags 998957 + pending


Dear maintainer,

I've prepared an NMU for libmp4-info-perl (versioned as 1.13-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libmp4-info-perl-1.13/debian/changelog libmp4-info-perl-1.13/debian/changelog
--- libmp4-info-perl-1.13/debian/changelog
+++ libmp4-info-perl-1.13/debian/changelog
@@ -1,3 +1,15 @@
+libmp4-info-perl (1.13-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965668)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #998957)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 20:06:48 +0100
+
 libmp4-info-perl (1.13-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libmp4-info-perl-1.13/debian/compat libmp4-info-perl-1.13/debian/compat
--- libmp4-info-perl-1.13/debian/compat
+++ libmp4-info-perl-1.13/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libmp4-info-perl-1.13/debian/control libmp4-info-perl-1.13/debian/control
--- libmp4-info-perl-1.13/debian/control
+++ libmp4-info-perl-1.13/debian/control
@@ -1,7 +1,7 @@
 Source: libmp4-info-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0)
+Build-Depends: debhelper (>= 7.0.0)
 Build-Depends-Indep: perl (>= 5.8.0-7), libio-string-perl
 Maintainer: Michael Ablassmeier 
 Standards-Version: 3.8.3
diff -u libmp4-info-perl-1.13/debian/rules libmp4-info-perl-1.13/debian/rules
--- libmp4-info-perl-1.13/debian/rules
+++ libmp4-info-perl-1.13/debian/rules
@@ -10,7 +10,9 @@
 
 TMP =$(CURDIR)/debian/$(PACKAGE)
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -63,4 +65,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#1002653: RFP: rummage -- Rummage is a GUI for grep like searches in Python

[Fabio Fantoni]

Package: wnpp
Severity: wishlist

* Package name    : rummage
  Version : 4.16.4
  Upstream Author : Isaac Muse 
* URL : https://github.com/facelessuser/Rummage
* License : MIT
  Programming Lang: Python
  Description : Rummage is a GUI for grep like searches in Python

Rummage is a cross platform search and replace tool. Rummage crawls 
directories and searches for specified patterns (either regular 
expression or literal) and can optionally replace those targets with 
desired text.


Rummage is written in Python and is currently available on Python 3. 
Rummage by default uses Python's Re regular expression engine, but you 
can also use the fantastic, feature rich Regex search engine and do 
interesting things like fuzzy searching and more.

Bug#1002636: debconf: dpkg-reconfigure locales crashes because /sbin is not in $PATH

[Colin Watson]

Control: reassign -1 util-linux
Control: forcemerge -1 907194

On Sun, Dec 26, 2021 at 06:18:23PM +0100, Lucio Messina wrote:
> I confirm that root's PATH does not contain /usr/sbin in my debian testing
> (bookworm) fresh install. I acquired the root shell using the `su` command.
> Then I ran `dpkg-reconfigure locales` but I got the error `bash:
> dpkg-reconfigure: command not found` so I ran `/usr/sbin/dpkg-reconfigure
> locales` as explained before.

"su" preserves the calling user's PATH by default.  Use "su -l" or "sudo
-i" instead, and see https://bugs.debian.org/907194.

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

Bug#573584: marked as done (RFP: lmfit -- Levenberg-Marquardt least-squares minimization and curve fitting)

[Drew Parsons]

Control: reopen 573584

On 2021-12-26 18:48, Debian Bug Tracking System wrote:

Your message dated Sun, 26 Dec 2021 18:44:10 +0100
with message-id <04a03289d94072077509a6ce8d3fe...@debian.org>
and subject line python3-lmfit is available
has caused the Debian Bug report #573584,
regarding RFP: lmfit -- Levenberg-Marquardt least-squares minimization
and curve fitting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.



Looks like lmfit (C code) got moved to 
https://jugit.fz-juelich.de/mlz/lmfit
(not to be be confused with the fork at https://github.com/NSLS-II/lmfit 
)


Could be value in a nonlinear LM C library, complementing the python API 
in python3-lmfit, so reopening the RFP.


Would be interesting to see a benchmark comparison between the C and 
Python implementations.


Drew

Bug#996712: libcache-memcached-fast-perl: autopkgtest failure on armhf: Fetched all keys / Match results

[Adrian Bunk]

On Fri, Oct 22, 2021 at 06:20:37PM +0200, gregor herrmann wrote:
> On Wed, 20 Oct 2021 21:34:50 +0200, gregor herrmann wrote:
> 
> > I don't know what exacatly is going on, but I note that it now also
> > fails on amd64.
> 
> And all other architectures …
>  
> > I was a bit surprised that the same tests pass during build but the
> > explanation is simple: They are skipped as no memcached is running …
> 
> If I start memcached before running the tests during builds, we get
> the same failures.
> 
> And: They also appear upstream in the Github actions:
> https://github.com/JRaspass/Cache-Memcached-Fast/actions/runs/1369481886

Running autopkgtest was enabled in 0.27-1, disabling them temporarily 
would just restore the status quo in stable and earlier.


> Cheers,
> gregor

cu
Adrian

Bug#1002512: Please remove Build-Depends on r-cran-multicore

[Dirk Eddelbuettel]

This bug now blocks resolution of #1002648 for the removal of r-cran-multicore.
It would be nice if you could adjust the (apparently also dead upstream)
package r-other-mott-happy to just rely on package 'parallel' which is
included in R.

Thanks, Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1002640: bind9 won't start after upgrading from 9.11 - "the working directory is not writable"

[Robert Waldner]

On Sun, 26 Dec 2021 10:47:42 -0500, Simon Deziel writes:
>What's in /etc/default/named? Chroot'ing could cause some issues.

This is stock, AFAICT:
---
#
# run resolvconf?
RESOLVCONF=no

# startup options for the server
OPTIONS="-u bind"
---

>Since you are hitting permission issues, I'd also check dmesg for 
>AppArmor denial messages (`dmesg | grep apparmor`).

At least there's nothing (to me) obvious:

root@fsckv2:~# dmesg | grep apparmor
[6.889374] audit: type=1400 audit(1640488235.484:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=900 comm="apparmor_parser"
[6.889470] audit: type=1400 audit(1640488235.484:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=901 comm="apparmor_parser"
[6.889533] audit: type=1400 audit(1640488235.484:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=889 
comm="apparmor_parser"
[6.889746] audit: type=1400 audit(1640488235.484:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=896 comm="apparmor_parser"
[6.889794] audit: type=1400 audit(1640488235.484:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=894 
comm="apparmor_parser"
[6.889797] audit: type=1400 audit(1640488235.484:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=894 comm="apparmor_parser"
[6.890474] audit: type=1400 audit(1640488235.484:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=891 
comm="apparmor_parser"
[6.890477] audit: type=1400 audit(1640488235.484:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=891 
comm="apparmor_parser"
[6.890479] audit: type=1400 audit(1640488235.484:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=891 
comm="apparmor_parser"
[6.891157] audit: type=1400 audit(1640488235.484:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="named" pid=899 
comm="apparmor_parser"

Kind regards,
Robert
-- 
-- Acronyms explained: TCPA
-- (T)otal (C)ontrol of (P)rivate (A)ssets
--   - captainiglo

Bug#1002640: bind9 won't start after upgrading from 9.11 - "the working directory is not writable"

[Robert Waldner]

On Sun, 26 Dec 2021 14:20:21 +0100, =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= writes:
>Well, what is your working directory and is it writeable by user:group
> under which named runs at your system?

root@fsckv2:~# grep direct /etc/bind/named.conf.options
directory "/etc/bind";

root@fsckv2:~# ls -la /etc/bind/
total 104
drwxrwsr-x   3 root bind  4096 Dec 26 11:35 .

root@fsckv2:~# grep OPTIONS /etc/default/named 
OPTIONS="-u bind"

Running named from buster, 1:9.11.5.P4+dfsg-5.1, started normally from 
 systemd:

root@fsckv2:~# ps auxwww| grep [n]amed
bind  133379  0.0  0.9 1728372 323376 ?  Ssl  12:09   0:04 
/usr/sbin/named -f -u bind

Kind regards,
Robert

Bug#1002299: debian-edu-config: hosts installed via the minimal profile lack libpam-krb5 and fail to mount NFS krb5i shares on TJENER

[Holger Levsen]

On Sun, Dec 26, 2021 at 02:45:59PM +0100, Wolfgang Schweer wrote:
> > When installing a Debian Edu system based on the Minimal installation
> > profile, then the package libpam-krb5 is missing on that host. An installed
> > Minimal system fails to allow users to log in (and get their home directory
> > mounted via NFSv4 and sec=krb5i).
> As far as I can tell, this is done by intention: it's not a system 
> providing user access by default.
> 
> From the documented profile description:
[...]

so maybe we should add to the manual the information how to manually enable
krb5 users to login to such a system?!?

Mike, if you agree, please reassign this bug to src:debian-edu-doc :)


-- 
cheers,
Holger

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

Religion has been more harmful to humanity than cigarettes.


signature.asc
Description: PGP signature

Bug#1002652: bullseye-pu: package schleuder/3.6.0-3+deb10u1

[Georg Faerber]

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

Dear release team,

[ Reason ]
Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean
serialization to use 1 and 0, but does not natively recognize 't' and 'f' as
booleans were previously serialized. This change makes existing mailing lists
fail, after an upgrade of buster to bullseye, due to the involved ActiveRecord
version bump, as Schleuder isn't able anymore to fetch correct values from the
database.

Unfortunately, we missed this breaking change when bumping ActiveRecord to >=
6.0 recently. This caused quite some work upstream, but also in downstream
environments and, last but not least, at the side of users.

This was reported in Debian via #1002622, and fixed in unstable via 3.6.0-4.

[ Impact ]
Severe, as existing and formerly working setups are left broken, after an
upgrade of buster to bullseye. Manual workarounds do exist, and are documented
upstream [1].

[ Tests ]
Extensive testing happened via upstream CI and multiple, manual tests on
various machines which exhibit this problem. The fix is targeted and worked, in
these tests, as expected.

[ Risks ]
The fix was reviewed upstream to ensure it works as expected, and doesn't cause
any harm. It's guarded to only be effective in setups which makes use of
SQLite3, although that's the default, and probably true for the big majority of
Debian-based setups.

[ 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 stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
The fix provided upstream was imported, which adds a database migration to
ensure correct serialization of boolean values, both defaults and
user-provided, if the SQLite3 connection adapter is in use.

Thanks for your work!

Cheers,
Georg


[1] https://0xacab.org/schleuder/schleuder/-/issues/505
diffstat for schleuder-3.6.0 schleuder-3.6.0

 changelog   |   12 ++
 patches/0031-db-change-boolean-values-to-integers.patch |   77 
 patches/series  |1 
 3 files changed, 90 insertions(+)

diff -Nru schleuder-3.6.0/debian/changelog schleuder-3.6.0/debian/changelog
--- schleuder-3.6.0/debian/changelog2021-07-29 20:36:52.0 +
+++ schleuder-3.6.0/debian/changelog2021-12-26 16:28:29.0 +
@@ -1,3 +1,15 @@
+schleuder (3.6.0-3+deb10u1) bullseye; urgency=medium
+
+  * debian/patches:
+- Pull in upstream patch to migrate boolean values to integers, if the
+  ActiveRecord SQLite3 connection adapter is in use. Since ActiveRecord >=
+  6.0, the relevant code relies on boolean serialization to use 1 and 0,
+  but does not natively recognize 't' and 'f' as booleans were previously
+  serialized. This change made existing mailing lists fail, if people were
+  upgrading buster to bullseye. (Closes: #100262)
+
+ -- Georg Faerber   Sun, 26 Dec 2021 16:28:29 +
+
 schleuder (3.6.0-3) unstable; urgency=medium
 
   * debian/patches:
diff -Nru 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch
--- 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch  
1970-01-01 00:00:00.0 +
+++ 
schleuder-3.6.0/debian/patches/0031-db-change-boolean-values-to-integers.patch  
2021-12-26 16:28:29.0 +
@@ -0,0 +1,77 @@
+Description: DB: change boolean values to integers
+  Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean
+  serialization to use 1 and 0, but does not natively recognize 't' and 'f' as
+  booleans were previously serialized. Accordingly, this patch handles
+  conversion via a database migration of both column defaults and stored data
+  provided by a user.
+Author: Georg Faerber 
+Origin: upstream
+Bug: https://0xacab.org/schleuder/schleuder/-/issues/505
+Applied-Upstream: 9ee12c4a1d6604c860c44073b99d8258bb4bc0ae
+Last-Update: 2021-12-25
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: schleuder/db/migrate/20211106112020_change_boolean_values_to_integers.rb
+===
+--- /dev/null  1970-01-01 00:00:00.0 +
 schleuder/db/migrate/20211106112020_change_boolean_values_to_integers.rb   
2021-12-26 17:28:42.468530957 +
+@@ -0,0 +1,46 @@
++# Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean
++# serialization to use 1 and 0, but does not natively recognize 't' and 'f' as
++# booleans were previously serialized.
++#
++# Accordingly, this migration handles conversion of both column defaults and
++# stored data provided by a user.
++#
++# In contrast to other migrations, only a 'forward' method 

Bug#568176: memtest86+: multiboot image is broken

[Fabio Fantoni]

Il 22/12/2021 13:44, Fabio Fantoni ha scritto:

Hi, I'm working on a new build for debian experimental with version 5.31b

work done for now about memtest86+ package is here: 
https://salsa.debian.org/debian/memtest86plus/-/commits/debian/experimental


for now multiboot patch is disabled, I don't have knowledge about 
assembly and the boot part except a little something done years ago 
that I hardly remember anything about, I don't have enough time 
recently to read up and study the parts.


For some tests I can try to adapt the patch from coreboot that is the 
most recent I found: 
https://review.coreboot.org/plugins/gitiles/memtest86plus/+/8cc1aeb540a02d9600491ca5fa799b7c8f25c363 
but I don't know if adapt and make it applicable and build working is 
enough to have multiboot correct and don't cause bugs (from an ubuntu 
issue on launchpad seems that ubuntu binaries have more issue that 
same upstream version and major of source changes is multiboot patch, 
so can be a cause of issue, I'm not sure)


Is there anyone with enough knowledge about it that want help me get 
the correct multiboot part for 5.31b for experimental please?


today I did a fast test applying the "newer" multiboot patch I found 
from coreboot repo 
(https://review.coreboot.org/plugins/gitiles/memtest86plus/+/8cc1aeb540a02d9600491ca5fa799b7c8f25c363 
based on Vladimir Serbinenko taken here), refreshed for 5.31b 
(https://salsa.debian.org/debian/memtest86plus/-/commit/deed716beaefcd25dd676b291801df7421f1fbf0), 
did also a small change to fix build fails 
https://salsa.debian.org/debian/memtest86plus/-/commit/326577b966a18c7c743be36c82985f52c5155804


but testing it on one computer on multiboot entry memtest freeze always 
at start, so seems another changes/fix are needed


if someone want test it: 
https://salsa.debian.org/debian/memtest86plus/-/tree/multiboot-test




OpenPGP_signature
Description: OpenPGP digital signature

Bug#965678: libperlmenu-perl: diff for NMU version 4.0-5.2

[gregor herrmann]

Control: tags 965678 + patch
Control: tags 965678 + pending
Control: tags 999181 + patch
Control: tags 999181 + pending


Dear maintainer,

I've prepared an NMU for libperlmenu-perl (versioned as 4.0-5.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libperlmenu-perl-4.0/debian/changelog libperlmenu-perl-4.0/debian/changelog
--- libperlmenu-perl-4.0/debian/changelog
+++ libperlmenu-perl-4.0/debian/changelog
@@ -1,3 +1,15 @@
+libperlmenu-perl (4.0-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965678)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999181)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 18:24:13 +0100
+
 libperlmenu-perl (4.0-5.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libperlmenu-perl-4.0/debian/compat libperlmenu-perl-4.0/debian/compat
--- libperlmenu-perl-4.0/debian/compat
+++ libperlmenu-perl-4.0/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libperlmenu-perl-4.0/debian/control libperlmenu-perl-4.0/debian/control
--- libperlmenu-perl-4.0/debian/control
+++ libperlmenu-perl-4.0/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: extra
 Maintainer: Deepak Tripathi 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Standards-Version: 3.7.2
 
 Package: libperlmenu-perl
diff -u libperlmenu-perl-4.0/debian/rules libperlmenu-perl-4.0/debian/rules
--- libperlmenu-perl-4.0/debian/rules
+++ libperlmenu-perl-4.0/debian/rules
@@ -4,6 +4,8 @@
 
 TMP= $(CURDIR)/debian/libperlmenu-perl
 
+build-arch: build
+build-indep: build
 build:
 #We don't have to build things.
 
@@ -43,4 +45,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#784658: libpam-ssh cannot authenticate user from "Additional" block in pam.d/common-auth

[Jerome BENOIT]

Hello Ilkka, thanks for your comments.
I apologize for my late reaction.

I understand that the current suggested authenticated scheme
is rather oriented to passwords than to SSH key passphrases.
But you expect the latter. So in the coming package version 2.3+ds-4
three schemes will be available. The current one will stay as default,
the two new scheme follows your expectation. The difference between
them is that one is client oriented ('use_first_pass') and the other
is server oriented ('try_first_pass').

Cheers,
Jerome



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002573: follow-up

[Chris Hofstaedtler]

Control: reassign -1 src:linux

* detlev schmidtke  [211226 18:21]:
> Yes, sorry for having caused this inconvenience
> 
> I repeat and extend the OP:
> 
> 1st error:
> 
> fstrim --verbose --all
> 
> reports nothing, but should due to --verbose
> 
> 2nd error:
> 
> fstrim --verbose /
> 
> gives a wrong error message "fstrim: /: the discard operation is not
> supported"

If the kernel says it's unsupported, than that is not an fstrim
(src:util-linux) problem. Reassigning to src:linux for this.

I guess if you send a full reproduction scenario, that would be more
helpful for everyone involved.

> This happens on Debian 11.2 Bullseye on an Intel hardware
> 
> The root file system is a RAID1 software array, but on a second Intel
> hardware with only one SSD, same Debian version, the behavior of fstrim
> is the same
> 
> On a Raspberry Pi with Debian 10 Buster, everything works fine:

That's like, completely different hardware?

BR,
Chris

Bug#897950: Bug#1002597: curl: temporarily revert adding libssh-dev to Build-Depends

[Daniel Stenberg]

On Sun, 26 Dec 2021, Samuel Henrique wrote:


1. How is it "a better maintained library" ?


I assume this is judging by the amount of recent commits on both projects, 
so it's not a perfect metric and it's gonna be hard to argue for it in case 
of disagreement. My assumption might be wrong though and the people who said 
it could have different metrics for it.


I won't say they are, but it *could* be that some people involved there are 
biased. Of course nobody asked me, but had they, I would have asked for 
clarification on a lot of those points.


Daniel, I won't rush this change and I value your input on this, as both 
curl and libssh2's upstream, so feel free to take your time to reply.


I feel that I'm not on a neutral ground here so I rather avoid taking sides at 
all. I want the decision to based on sound and solid reasons by people who 
understand them. Whatever direction it goes.


On my initial assessment I couldn't find considerable differences that would 
weigh in favour of staying with libssh2, I did stumble upon your blogposts 
talking about performance (libssh2 being better) but they are a bit old and 
I'm not sure if it's still applicable.


Yeah, I haven't done any such comparisons in many years. The situation is much 
likely very different today.


--

 / daniel.haxx.se

Bug#1002573: follow-up

[detlev schmidtke]

Yes, sorry for having caused this inconvenience

I repeat and extend the OP:

1st error:

fstrim --verbose --all

reports nothing, but should due to --verbose

2nd error:

fstrim --verbose /

gives a wrong error message "fstrim: /: the discard operation is not
supported"

This happens on Debian 11.2 Bullseye on an Intel hardware

The root file system is a RAID1 software array, but on a second Intel
hardware with only one SSD, same Debian version, the behavior of fstrim
is the same

On a Raspberry Pi with Debian 10 Buster, everything works fine:

fstrim --verbose /
/: 196.9 MiB (206516224 bytes) trimmed

or:

fstrim --verbose /
/: 0 B (0 bytes) trimmed

On both systems, the version of fstrim is the same:

fstrim --version
fstrim from util-linux 2.36.1

If I use the command from fstrim.service on Debian 11:

/sbin/fstrim --listed-in /etc/fstab:/proc/self/mountinfo --verbose
--quiet-unsupported

I also get no output

Bug#965684: libsendmail-pmilter-perl: diff for NMU version 1.00-1.2

[gregor herrmann]

Control: tags 965684 + patch
Control: tags 965684 + pending
Control: tags 998923 + patch
Control: tags 998923 + pending


Dear maintainer,

I've prepared an NMU for libsendmail-pmilter-perl (versioned as 1.00-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libsendmail-pmilter-perl-1.00/debian/changelog libsendmail-pmilter-perl-1.00/debian/changelog
--- libsendmail-pmilter-perl-1.00/debian/changelog
+++ libsendmail-pmilter-perl-1.00/debian/changelog
@@ -1,3 +1,15 @@
+libsendmail-pmilter-perl (1.00-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965684)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #998923)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 18:10:40 +0100
+
 libsendmail-pmilter-perl (1.00-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libsendmail-pmilter-perl-1.00/debian/compat libsendmail-pmilter-perl-1.00/debian/compat
--- libsendmail-pmilter-perl-1.00/debian/compat
+++ libsendmail-pmilter-perl-1.00/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libsendmail-pmilter-perl-1.00/debian/control libsendmail-pmilter-perl-1.00/debian/control
--- libsendmail-pmilter-perl-1.00/debian/control
+++ libsendmail-pmilter-perl-1.00/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Build-Depends-Indep: perl (>= 5.8.0-7)
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Maintainer: Hilko Bengen 
 Standards-Version: 3.9.1
 
diff -u libsendmail-pmilter-perl-1.00/debian/rules libsendmail-pmilter-perl-1.00/debian/rules
--- libsendmail-pmilter-perl-1.00/debian/rules
+++ libsendmail-pmilter-perl-1.00/debian/rules
@@ -18,7 +18,9 @@
 endif
 TMP =`pwd`/debian/$(PACKAGE)
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -79,4 +81,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#965685: libropkg-perl: diff for NMU version 0.4-1.4

[gregor herrmann]

Control: tags 965685 + patch
Control: tags 965685 + pending
Control: tags 999211 + patch
Control: tags 999211 + pending


Dear maintainer,

I've prepared an NMU for libropkg-perl (versioned as 0.4-1.4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libropkg-perl-0.4/debian/changelog libropkg-perl-0.4/debian/changelog
--- libropkg-perl-0.4/debian/changelog
+++ libropkg-perl-0.4/debian/changelog
@@ -1,3 +1,15 @@
+libropkg-perl (0.4-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965685)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999211)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 18:05:10 +0100
+
 libropkg-perl (0.4-1.3) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libropkg-perl-0.4/debian/compat libropkg-perl-0.4/debian/compat
--- libropkg-perl-0.4/debian/compat
+++ libropkg-perl-0.4/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libropkg-perl-0.4/debian/control libropkg-perl-0.4/debian/control
--- libropkg-perl-0.4/debian/control
+++ libropkg-perl-0.4/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Maintainer: Radu Spineanu 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Build-Depends-Indep: libpod-coverage-perl, libexception-class-perl (>= 1.21-1), libdbi-perl, libclass-singleton-perl, libtest-pod-coverage-perl
 Standards-Version: 3.7.2
 
diff -u libropkg-perl-0.4/debian/rules libropkg-perl-0.4/debian/rules
--- libropkg-perl-0.4/debian/rules
+++ libropkg-perl-0.4/debian/rules
@@ -19,7 +19,9 @@
 
 	touch configure-stamp
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp: configure-stamp
 	dh_testdir
 
@@ -72,3 +74,3 @@
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary
 


signature.asc
Description: Digital Signature

Bug#965690: libtree-multinode-perl: diff for NMU version 1.0.10-2.2

[gregor herrmann]

Control: tags 965690 + patch
Control: tags 965690 + pending


Dear maintainer,

I've prepared an NMU for libtree-multinode-perl (versioned as 1.0.10-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libtree-multinode-perl-1.0.10/debian/changelog libtree-multinode-perl-1.0.10/debian/changelog
--- libtree-multinode-perl-1.0.10/debian/changelog
+++ libtree-multinode-perl-1.0.10/debian/changelog
@@ -1,3 +1,12 @@
+libtree-multinode-perl (1.0.10-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965690)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 17:47:38 +0100
+
 libtree-multinode-perl (1.0.10-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u libtree-multinode-perl-1.0.10/debian/compat libtree-multinode-perl-1.0.10/debian/compat
--- libtree-multinode-perl-1.0.10/debian/compat
+++ libtree-multinode-perl-1.0.10/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libtree-multinode-perl-1.0.10/debian/control libtree-multinode-perl-1.0.10/debian/control
--- libtree-multinode-perl-1.0.10/debian/control
+++ libtree-multinode-perl-1.0.10/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Maintainer: Dmitry E. Oboukhov 
-Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5)
+Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 7)
 Standards-Version: 3.8.0
 Homepage: http://search.cpan.org/~krburton/
 


signature.asc
Description: Digital Signature

Bug#1002597: Bug#897950: Bug#1002597: curl: temporarily revert adding libssh-dev to Build-Depends

[Samuel Henrique]

Hello all,

I have replied to Daniel at #897950 (https://bugs.debian.org/897950)
Discussions about migrating curl to libssh will follow there.

With regards to the libssh-dev build-dep, I have readded it to curl as
7.80.0-3 and Ubuntu will be able to sync again.

Note that 7.80.0-3 is not using libssh other than as a build-dep,
Debian's curl is still linking against libssh2, it's only on Ubuntu
and onwards that they're using libssh.

Thank you everyone.

-- 
Samuel Henrique 

Bug#998716: linux-image-5.14.0-2-amd64: The package size has grown a lot compared to 5.8/5.10 releases

[Fabian Grünbichler]

On Tue, Nov 30, 2021 at 08:18:56PM +0100, Ben Hutchings wrote:
> On Tue, 2021-11-30 at 11:01 +0100, Fabian Grünbichler wrote:
> [...]
> > possibly interesting in that context (I asked/posted the link in 
> > #debian-kernel a few days ago as well) - these BTF sections now actually 
> > reference the BTF info in the kernel image itself (as part of the 
> > deduplication of shared information), which makes the latter part of the 
> > ABI, and AFAICT this is not (yet?) tracked in Debian..
> > 
> > https://lore.kernel.org/all/1637926692.uyvrkty41j.astr...@nora.none/
> > 
> > an otherwise ABI compatible kernel upgrade thus has the potential to 
> > break module loading altogether, and I'd recommend disabling the split 
> > BTF feature for the time being unless you plan on bumping ABI for every 
> > kernel update anyway.
> 
> Yes, that is interesting/concerning.
> 
> If we continue to not bump the ABI number on every update, then I
> think:
> 
> 1. In-tree modules should not be loadable between an upgrade and a
> reboot.  (This can happen already for specific modules, due to symbol
> version changes that we think don't affect out-of-tree modules.) 
> Alternatively, they could still be loadable but then their BTF info
> should be completely discarded.
> 
> 2. Out-of-tree modules should be built without BTF deduplication, or
> without BTF info.
> 
> The main reason for not bumping the ABI number every time is to avoid
> forcing an unnecessary rebuild of out-of-tree modules.  We could try
> switching to something like RHEL's "weak-update" mechanism where ABI-
> compatible out-of-tree modules are automatically linked into a new
> version's modules directory without rebuilding them.  In that case we
> would still need to implement item (2) above.

FWIW, I ran into this issue for real on a Sid system:

booted kernel: Linux host 5.15.0-2-amd64 #1 SMP Debian 5.15.5-1 (2021-11-26) 
x86_64 GNU/Linux
installed kernel: ii  linux-image-5.15.0-2-amd64 5.15.5-2 amd64
Linux 5.15 for 64-bit PCs (signed)

attempting to (auto-)load any module not already loaded before the
upgrade:

Dec 26 17:18:48 host mtp-probe[319902]: checking bus 4, device 3: 
"/sys/devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:05:00.3/usb4/4-4"
Dec 26 17:18:48 host mtp-probe[319902]: bus: 4, device: 3 was not an MTP device
Dec 26 17:18:49 host kernel: scsi 3:0:0:0: Direct-Access  
Multi-Reader  -0 1.00 PQ: 0 ANSI: 6
Dec 26 17:18:49 host kernel: scsi 3:0:0:1: Direct-Access  
Multi-Reader  -1 1.00 PQ: 0 ANSI: 6
Dec 26 17:18:49 host kernel: scsi 3:0:0:2: Direct-Access  
Multi-Reader  -2 1.00 PQ: 0 ANSI: 6
Dec 26 17:18:49 host kernel: scsi 3:0:0:3: Direct-Access  
Multi-Reader  -3 1.00 PQ: 0 ANSI: 6
Dec 26 17:18:49 host kernel: scsi 3:0:0:0: Attached scsi generic sg0 type 0
Dec 26 17:18:49 host kernel: scsi 3:0:0:1: Attached scsi generic sg1 type 0
Dec 26 17:18:49 host kernel: scsi 3:0:0:2: Attached scsi generic sg2 type 0
Dec 26 17:18:49 host kernel: scsi 3:0:0:3: Attached scsi generic sg3 type 0
Dec 26 17:18:49 host kernel: BPF:[86226] ENUM T_CONDITION_MET
Dec 26 17:18:49 host kernel: BPF:size=4 vlen=11
Dec 26 17:18:49 host kernel: BPF:
Dec 26 17:18:49 host kernel: BPF:Invalid name
Dec 26 17:18:49 host kernel: BPF:
Dec 26 17:18:49 host kernel: failed to validate module [sd_mod] BTF: -22

module loading fails until booted and on-disk kernel images match again
- either by downgrading the latter (to 5.15.5-1 in this case), or by
rebooting.

note that just disabling the relevant KConfig doesn't work in my
experience, since it will be automatically enabled again by the presence
of a split-BTF capable pahole version in the build environment. patching
the default value to 'n' does work though[0].

0: 
https://git.proxmox.com/?p=pve-kernel.git;a=commitdiff;h=bc1d1913898940cabcea142f75a2a4759790a503

Bug#965691: libtext-wikiformat-perl: diff for NMU version 0.79-1.2

[gregor herrmann]

Control: tags 965691 + patch
Control: tags 965691 + pending
Control: tags 998984 + patch
Control: tags 998984 + pending


Dear maintainer,

I've prepared an NMU for libtext-wikiformat-perl (versioned as 0.79-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -Nru libtext-wikiformat-perl-0.79/debian/changelog libtext-wikiformat-perl-0.79/debian/changelog
--- libtext-wikiformat-perl-0.79/debian/changelog	2021-01-02 18:52:36.0 +0100
+++ libtext-wikiformat-perl-0.79/debian/changelog	2021-12-26 17:36:38.0 +0100
@@ -1,3 +1,15 @@
+libtext-wikiformat-perl (0.79-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965691)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #998984)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 17:36:38 +0100
+
 libtext-wikiformat-perl (0.79-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru libtext-wikiformat-perl-0.79/debian/compat libtext-wikiformat-perl-0.79/debian/compat
--- libtext-wikiformat-perl-0.79/debian/compat	2011-02-12 21:36:17.0 +0100
+++ libtext-wikiformat-perl-0.79/debian/compat	2021-12-26 17:34:51.0 +0100
@@ -1 +1 @@
-5
+7
diff -Nru libtext-wikiformat-perl-0.79/debian/control libtext-wikiformat-perl-0.79/debian/control
--- libtext-wikiformat-perl-0.79/debian/control	2011-02-12 21:36:17.0 +0100
+++ libtext-wikiformat-perl-0.79/debian/control	2021-12-26 17:34:52.0 +0100
@@ -1,7 +1,7 @@
 Source: libtext-wikiformat-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Build-Depends-Indep: perl (>= 5.6), libmodule-build-perl, liburi-perl
 Maintainer: Benjamin Mako Hill 
 Standards-Version: 3.9.1
diff -Nru libtext-wikiformat-perl-0.79/debian/rules libtext-wikiformat-perl-0.79/debian/rules
--- libtext-wikiformat-perl-0.79/debian/rules	2011-02-12 21:36:17.0 +0100
+++ libtext-wikiformat-perl-0.79/debian/rules	2021-12-26 17:36:18.0 +0100
@@ -29,7 +29,9 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir
@@ -94,4 +96,4 @@
 binary-arch: build install
 
 binary: binary-indep
-.PHONY: build clean binary-indep binary install configure
+.PHONY: build-arch build-indep build clean binary-indep binary install configure


signature.asc
Description: Digital Signature

Bug#965697: libwww-mediawiki-client-perl: diff for NMU version 0.31-2.2

[gregor herrmann]

Control: tags 965697 + patch
Control: tags 965697 + pending
Control: tags 999129 + patch
Control: tags 999129 + pending


Dear maintainer,

I've prepared an NMU for libwww-mediawiki-client-perl (versioned as 0.31-2.2) 
and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -Nru libwww-mediawiki-client-perl-0.31/debian/changelog libwww-mediawiki-client-perl-0.31/debian/changelog
--- libwww-mediawiki-client-perl-0.31/debian/changelog	2021-01-06 17:28:14.0 +0100
+++ libwww-mediawiki-client-perl-0.31/debian/changelog	2021-12-26 17:27:55.0 +0100
@@ -1,3 +1,17 @@
+libwww-mediawiki-client-perl (0.31-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965697)
+  * Fix "missing required debian/rules targets build-arch and/or build-
+indep": Add missing targets.
+(Closes: #999129)
+  * Don't list files in debian/rules which dh_install{docs,changelogs} handle
+automatically.
+
+ -- gregor herrmann   Sun, 26 Dec 2021 17:27:55 +0100
+
 libwww-mediawiki-client-perl (0.31-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru libwww-mediawiki-client-perl-0.31/debian/compat libwww-mediawiki-client-perl-0.31/debian/compat
--- libwww-mediawiki-client-perl-0.31/debian/compat	2011-02-13 02:04:28.0 +0100
+++ libwww-mediawiki-client-perl-0.31/debian/compat	2021-12-26 17:21:53.0 +0100
@@ -1 +1 @@
-5
+7
diff -Nru libwww-mediawiki-client-perl-0.31/debian/control libwww-mediawiki-client-perl-0.31/debian/control
--- libwww-mediawiki-client-perl-0.31/debian/control	2011-02-13 02:04:28.0 +0100
+++ libwww-mediawiki-client-perl-0.31/debian/control	2021-12-26 17:22:00.0 +0100
@@ -1,7 +1,7 @@
 Source: libwww-mediawiki-client-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5.0.0)
+Build-Depends: debhelper (>= 7.0.0)
 Build-Depends-Indep: perl (>= 5.8), libexception-class-perl, libtest-differences-perl, libvcs-lite-perl (>= 0.08), libwww-perl, libxml-libxml-perl
 Maintainer: Benjamin Mako Hill 
 Standards-Version: 3.9.1
diff -Nru libwww-mediawiki-client-perl-0.31/debian/rules libwww-mediawiki-client-perl-0.31/debian/rules
--- libwww-mediawiki-client-perl-0.31/debian/rules	2011-02-13 02:04:28.0 +0100
+++ libwww-mediawiki-client-perl-0.31/debian/rules	2021-12-26 17:27:53.0 +0100
@@ -19,7 +19,9 @@
 
 TMP =$(CURDIR)/debian/$(PACKAGE)
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 
@@ -63,8 +65,8 @@
 #	dh_installcron
 #	dh_installmenu
 #	dh_installexamples
-	dh_installdocs README TODO debian/README.Debian
-	dh_installchangelogs ChangeLog
+	dh_installdocs README TODO
+	dh_installchangelogs
 	dh_perl
 	dh_link
 	dh_strip
@@ -79,4 +81,4 @@
 	@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+.PHONY: build-indep build-arch build clean binary-indep binary-arch binary


signature.asc
Description: Digital Signature

Bug#1002651: Please cherry-pick the commits after the 3.38.6 release from upstream to bullseye-updates

[Amr Ibrahim]

Package: mutter

Hello,

Please cherry-pick the commits after the 3.38.6 release from upstream
gnome-3-38 branch to bullseye-updates. Or maybe upstream could release
3.38.7.

The commits are Wayland fixes mainly for the sake of newer versions of
Firefox, which can be installed as a flatpak in Debian 11.

https://gitlab.gnome.org/GNOME/mutter/-/commits/gnome-3-38

Best,
Amr

Bug#1002650: RM: r-omegahat-xmlrpc -- ROM: retired upstream nine years ago

[Dirk Eddelbuettel]

Package: ftp.debian.org
Severity: normal

The OmegaHat project was once (around 2000) aiming to write 'the next
R'. That never happend.  But R Core member Duncan Temple Lang maintained a
repository for several years with a number of extension packages. But it
ceased to exist years ago and 'https://omegahat.org/' now just states
'deleted site'.

I had packaged 'r-omegahat-xmlrpc' years ago as a Build-Depends: of
'r-cran-rneos' (aka 'rneos' upstream). With OmegaHat gone, 'rneos' included
the parts of this package it needed for XML-based RPC calls, so the package
is no longer needed and can be removed.

Dirk

--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1002649: RFS: check-mk-agent/1:2.0.0p17+dfsg-4 [ITP] -- general purpose monitoring plugin for retrieving data

[Juri Grabowski]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "check-mk-agent":

 * Package name: check-mk-agent
   Version : 1:2.0.0p17+dfsg-4
   Upstream Author : [fill in name and email of upstream]
 * URL : https://checkmk.de
 * License : GPL-2 or GPL-2.0+
 * Vcs : https://salsa.debian.org/gratuxri/check-mk-agent
   Section : admin

It builds those binary packages:

  check-mk-agent - general purpose monitoring plugin for retrieving data
  waitmax - Architecture specific waitmax for Check_MK Agent for Linux
  check-mk-agent-plugin-apache-status - general purpose Apache monitoring 
plugin for retrieving data
  check-mk-agent-plugin-asmcmd - general purpose asmcmd monitoring plugin for 
retrieving data
  check-mk-agent-plugin-dnsclient - general purpose dns monitoring plugin for 
retrieving data
  check-mk-agent-plugin-isc-dhcpd - general purpose isc-dhcpd monitoring plugin 
for retrieving data
  check-mk-agent-plugin-jar-signature - general purpose jar-signature 
monitoring plugin for retrieving data
  check-mk-agent-plugin-kaspersky-av - general purpose kaspersky-av monitoring 
plugin for retrieving data
  check-mk-agent-plugin-lnx-quota - general purpose quota monitoring plugin for 
retrieving data
  check-mk-agent-plugin-lvm - general purpose lvm monitoring plugin for 
retrieving data
  check-mk-agent-plugin-apt-hourly - general purpose apt monitoring plugin for 
retrieving data
  check-mk-agent-plugin-ceph - general purpose ceph monitoring plugin for 
retrieving data
  check-mk-agent-plugin-cups-queues - general purpose CUPS queues monitoring 
plugin for retrieving data
  check-mk-agent-plugin-docker - general purpose docker monitoring plugin for 
retrieving data
  check-mk-agent-plugin-filehandler - general purpose filehandler monitoring 
plugin for retrieving data
  check-mk-agent-plugin-filestats - general purpose filestats monitoring plugin 
for retrieving data
  check-mk-agent-plugin-inotify - general purpose inotify monitoring plugin for 
retrieving data
  check-mk-agent-plugin-inventory - general purpose inventory monitoring plugin 
for retrieving data
  check-mk-agent-plugin-iptables - general purpose iptables monitoring plugin 
for retrieving data
  check-mk-agent-plugin-jolokia - general purpose jolokia monitoring plugin for 
retrieving data
  check-mk-agent-plugin-logins - general purpose logins monitoring plugin for 
retrieving data
  check-mk-agent-plugin-logwatch - general purpose logwatch monitoring plugin 
for retrieving data
  check-mk-agent-plugin-mongodb - general purpose mongodb monitoring plugin for 
retrieving data
  check-mk-agent-plugin-mysql - general purpose MySQL monitoring plugin for 
retrieving data
  check-mk-agent-plugin-nfsiostat - general purpose NFS monitoring plugin for 
retrieving data
  check-mk-agent-plugin-omreport - general purpose DELL monitoring plugin for 
retrieving data
  check-mk-agent-plugin-postgres - general purpose postgres monitoring plugin 
for retrieving data
  check-mk-agent-plugin-scaleio - general purpose scaleio monitoring plugin for 
retrieving data
  check-mk-agent-plugin-site-object-counts - general purpose omd monitoring 
plugin for retrieving data
  check-mk-agent-plugin-sshd-config - general purpose sshd_config monitoring 
plugin for retrieving data
  check-mk-agent-plugin-tinkerforge - general purpose tinkerforge monitoring 
plugin for retrieving data
  check-mk-agent-plugin-mtr - general purpose mtr monitoring plugin for 
retrieving data
  check-mk-agent-plugin-netstat - general purpose netstat monitoring plugin for 
retrieving data
  check-mk-agent-plugin-nfsexports - general purpose nfsexports monitoring 
plugin for retrieving data
  check-mk-agent-plugin-nginx-status - general purpose nginx monitoring plugin 
for retrieving data
  check-mk-agent-plugin-runas - This plugin allows one to run check-mk-agent as 
different user
  check-mk-agent-plugin-smart-hourly - general purpose smart monitoring plugin 
for retrieving data
  check-mk-agent-plugin-symantec-av - general purpose symantec AV monitoring 
plugin for retrieving data
  check-mk-agent-plugin-redis - general purpose redis monitoring plugin for 
retrieving data
  check-mk-agent-plugin-zorp - general purpose zorp monitoring plugin for 
retrieving data

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/check-mk-agent/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/c/check-mk-agent/check-mk-agent_2.0.0p17+dfsg-4.dsc

Changes for the initial release:

 check-mk-agent (1:2.0.0p17+dfsg-4) unstable; urgency=medium
 .
   * Fix: lintian: P: check-mk-agent source: trailing-whitespace debian/rules
   * d/control: check-mk-agent-plugin-runas: spelling-error
   * Fix: lintian: I: waitmax: hardening-no-bindnow usr/bin/waitmax
   * Fix: 

Bug#1002648: RM: r-cran-multicore -- ROM: retired upstream years ago

[Dirk Eddelbuettel]

Package: ftp.debian.org
Severity: normal

The 'multicore' package for R was an early extension (during 2009 to 2011) to
support process-parallel work. Its key parts (especially those that matter
for us on Linux) were replaced / rewritten many years ago by package
'parallel' which is a part of base R and installed with every R installation.
Consequently 'multicore' had a final transition release in 2014 but has
itself been removed from CRAN for several years.

We have kept 'r-cran-multicore' around for some time but it is time to let it
go now. I updated my own two reverse dependencies 'r-cran-dosnow' and
'r-cran-domc', and filed #1002512 to have package 'r-other-mott-happy.hbrem'
updated too.

Dirk

--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1002647: marble-qt: marble does not show legend of maps any more

[Klaumi Klingsporn]

Package: marble-qt
Version: 4:21.08.3-1
Severity: normal

Dear Maintainer,

in the new version marble as well as marble-qt doesn't show anything in the 
legend tab
although there are legend-symbols in the maps-subdirectories for the maps and 
descriptions
in the dgml-files.

klaumi


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (210, 'stable-security'), (200, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:de:en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages marble-qt depends on:
ii  libc6   2.33-1
ii  libgcc-s1   11.2.0-13
ii  libmarblewidget-qt5-28  4:21.08.3-1
ii  libqt5core5a5.15.2+dfsg-14
ii  libqt5dbus5 5.15.2+dfsg-14
ii  libqt5gui5  5.15.2+dfsg-14
ii  libqt5network5  5.15.2+dfsg-14
ii  libqt5printsupport5 5.15.2+dfsg-14
ii  libqt5widgets5  5.15.2+dfsg-14
ii  libstdc++6  11.2.0-13

marble-qt recommends no packages.

marble-qt suggests no packages.

-- no debconf information

Bug#965700: libwww-opensearch-perl: diff for NMU version 0.17-1.2

[gregor herrmann]

Control: tags 965700 + patch
Control: tags 965700 + pending


Dear maintainer,

I've prepared an NMU for libwww-opensearch-perl (versioned as 0.17-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -Nru libwww-opensearch-perl-0.17/debian/changelog libwww-opensearch-perl-0.17/debian/changelog
--- libwww-opensearch-perl-0.17/debian/changelog	2021-01-02 18:53:47.0 +0100
+++ libwww-opensearch-perl-0.17/debian/changelog	2021-12-26 17:11:36.0 +0100
@@ -1,3 +1,14 @@
+libwww-opensearch-perl (0.17-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 8 in debian/compat (to match 8 in debian/control).
+(Closes: #965700)
+  * Additionally drop override_dh_installchangelogs from debian/rules.
+Since compat level 7, dh_installchangelogs finds the upstream changelog.
+
+ -- gregor herrmann   Sun, 26 Dec 2021 17:11:36 +0100
+
 libwww-opensearch-perl (0.17-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru libwww-opensearch-perl-0.17/debian/compat libwww-opensearch-perl-0.17/debian/compat
--- libwww-opensearch-perl-0.17/debian/compat	2013-06-08 21:46:53.0 +0200
+++ libwww-opensearch-perl-0.17/debian/compat	2021-12-26 17:08:32.0 +0100
@@ -1 +1 @@
-5
+8
diff -Nru libwww-opensearch-perl-0.17/debian/rules libwww-opensearch-perl-0.17/debian/rules
--- libwww-opensearch-perl-0.17/debian/rules	2013-06-08 21:46:53.0 +0200
+++ libwww-opensearch-perl-0.17/debian/rules	2021-12-26 17:10:48.0 +0100
@@ -2,7 +2,3 @@
 
 %:
 	dh $@
-
-override_dh_installchangelogs:
-	dh_installchangelogs Changes
-


signature.asc
Description: Digital Signature

Bug#1002628: Using build command fails in Debian WSL

[Roland Clobus]

Hello Leon,

On 25/12/2021 22:58, Leon Heess wrote:

I was following your [tutorials on customizing the live debian 
installation](https://live-team.pages.debian.net/live-manual/html/live-manual/examples.en.html#using-the-examples).
The last command in every tutorial is `lb build 2>&1 | tee build.log`. But 
every time I use it on my Debian WSL2
machine I run into this:

...

mknod: /mnt/c/deb-live-tutorial/chroot/test-dev-null: Operation not supported
E: Cannot install into target '/mnt/c/deb-live-tutorial/chroot' mounted with 
noexec or nodev



Could it be that live-build is not working properly inside WSL2?


The error message says that you need 'exec' and/or 'dev' rights for your 
mount point.


I've not tried this on Windows under WSL yet, but under Linux, with 
/dev/shm, I use: 'sudo mount /dev/shm -odev,exec,remount'


With kind regards,
Roland Clobus



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002564: [pkg-lxc-devel] Bug#1002564: lxc: packaging adjustments for LXD

[Mathias Gibbens]

On Sun, 26 Dec 2021 12:33:43 -0300 Antonio Terceiro
 wrote:
> On Sat, Dec 25, 2021 at 02:25:06PM +, Evgeni Golov wrote:
> > On December 25, 2021 12:35:45 PM UTC, Antonio Terceiro
 wrote:
> > >They probably would need to be provided by a (NEW) lxc-common
package.
> > >If we ever need to transition to liblxc2, we don't want both
liblxc*
> > >packages providing those files.
> > 
> > On Ubuntu, this package us called liblxc-common, which we probably
> > should also use, to make life of other consumers easier?
> 
> Sure! I didn't check there first.

  I think a liblxc-common package should work just fine. I haven't
found any other files in the lxc package that LXD is expecting to have
around, but if I do I'll update this bug.

  I'm happy to help test any changes to the packaging when they're
ready.

Thanks!
Mathias


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

Bug#1002573: please include console output in text form

[Tomas Pospisek]

Hi nst0022,

I have reassigned your bugreport to the correct package, namely 
util-linux.


Please when filing a bug report, assign the bug to the correct package in 
the first place, otherwise:


* you'll be generating triage work for others
* your bug report won't be seen by the maintainers and therefore be
  possibly useles

Also please do *not* attach screenshots, when you can copy/paste text. 
Images are not searchable as oposed to text, which easily is. Also images 
are harder to manage (how do I cite text in your image?).


So could you please write a follow up to your report, that includes the 
*text* only (no screen shot).


Thanks,
*t

Bug#1002640: bind9 won't start after upgrading from 9.11 - "the working directory is not writable"

[Simon Deziel]

On 2021-12-26 06:09, Robert Waldner wrote:

Package: bind9
Version: 1:9.16.22-1~deb11u1
Severity: important

Dear Maintainers,

I upgraded my nameserver from buster to bullseye, afterwards named wouldn't 
start anymore.

Looking at syslog, the relevant part seems to be:
...
Dec 26 11:36:01 fsck named[128029]: configuring command channel from 
'/etc/bind/rndc.key'
Dec 26 11:36:01 fsck named[128029]: command channel listening on 127.0.0.1#953
Dec 26 11:36:01 fsck named[128029]: configuring command channel from 
'/etc/bind/rndc.key'
Dec 26 11:36:01 fsck named[128029]: command channel listening on ::1#953
Dec 26 11:36:01 fsck named[128029]: the working directory is not writable
 ^
Dec 26 11:36:01 fsck named[128029]: loading configuration: permission denied
Dec 26 11:36:01 fsck named[128029]: exiting (due to fatal error)
Dec 26 11:36:01 fsck systemd[1]: named.service: Main process exited, 
code=exited, status=1/FAILURE
Dec 26 11:36:01 fsck systemd[1]: named.service: Failed with result 'exit-code'.

Note that this is straight from systemd trying to start it.

Running named as `named -g -u bind` got the same result (CWD: /home/myuser).

But! starting it manually with a CWD that's writable by group bind (eg. `cd 
/etc/bind; named -g -u bind`) works:
...
26-Dec-2021 11:44:10.434 configuring command channel from '/etc/bind/rndc.key'
26-Dec-2021 11:44:10.434 command channel listening on 127.0.0.1#953
26-Dec-2021 11:44:10.434 configuring command channel from '/etc/bind/rndc.key'
26-Dec-2021 11:44:10.434 command channel listening on ::1#953
26-Dec-2021 11:44:10.434 not using config file logging statement for logging 
due to -g option
26-Dec-2021 11:44:10.434 zone 10.in-addr.arpa/IN: loaded serial 2002041301
...

Now this wouldn't be a problem is systemd could start named, but it can't:

root@fsckv2:/etc/bind# systemctl start named
root@fsckv2:/etc/bind# systemctl status named
● named.service - BIND Domain Name Server
  Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor 
preset: enabled)
  Active: failed (Result: exit-code) since Sun 2021-12-26 11:46:23 CET; 1s 
ago
Docs: man:named(8)
 Process: 130605 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, 
status=1/FAILURE)
Main PID: 130605 (code=exited, status=1/FAILURE)
 CPU: 51ms

Dec 26 11:46:23 fsckv2 systemd[1]: named.service: Scheduled restart job, 
restart counter is at 5.
Dec 26 11:46:23 fsckv2 systemd[1]: Stopped BIND Domain Name Server.
Dec 26 11:46:23 fsckv2 systemd[1]: named.service: Start request repeated too 
quickly.
Dec 26 11:46:23 fsckv2 systemd[1]: named.service: Failed with result 
'exit-code'.
Dec 26 11:46:23 fsckv2 systemd[1]: Failed to start BIND Domain Name Server.

For testing, I also `apt-get -b source`d bind9 from testing/unstable 
(9.17.21-1) but it exhibits the
same non-working bevaviour.

(If needed I can provide all config in private mail, but am loathe to disclose 
them publicly as it's quite
extensive (this is a nameserver for quite some domains, plus the resolver for 
all my internal networks).)


What's in /etc/default/named? Chroot'ing could cause some issues.

Since you are hitting permission issues, I'd also check dmesg for 
AppArmor denial messages (`dmesg | grep apparmor`).


Simon

Bug#965648: libimage-metadata-jpeg-perl: diff for NMU version 0.153-1.3

[gregor herrmann]

Control: tags 965648 + patch
Control: tags 965648 + pending


Dear maintainer,

I've prepared an NMU for libimage-metadata-jpeg-perl (versioned as 0.153-1.3) 
and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libimage-metadata-jpeg-perl-0.153/debian/changelog libimage-metadata-jpeg-perl-0.153/debian/changelog
--- libimage-metadata-jpeg-perl-0.153/debian/changelog
+++ libimage-metadata-jpeg-perl-0.153/debian/changelog
@@ -1,3 +1,12 @@
+libimage-metadata-jpeg-perl (0.153-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965648)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 16:52:19 +0100
+
 libimage-metadata-jpeg-perl (0.153-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libimage-metadata-jpeg-perl-0.153/debian/compat libimage-metadata-jpeg-perl-0.153/debian/compat
--- libimage-metadata-jpeg-perl-0.153/debian/compat
+++ libimage-metadata-jpeg-perl-0.153/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libimage-metadata-jpeg-perl-0.153/debian/control libimage-metadata-jpeg-perl-0.153/debian/control
--- libimage-metadata-jpeg-perl-0.153/debian/control
+++ libimage-metadata-jpeg-perl-0.153/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Maintainer: Rene Weber 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Build-Depends-Indep: perl
 Standards-Version: 3.8.3
 


signature.asc
Description: Digital Signature

Bug#965635: libdigest-whirlpool-perl: diff for NMU version 1.09-1.3

[gregor herrmann]

Control: tags 965635 + patch
Control: tags 965635 + pending


Dear maintainer,

I've prepared an NMU for libdigest-whirlpool-perl (versioned as 1.09-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libdigest-whirlpool-perl-1.09/debian/changelog libdigest-whirlpool-perl-1.09/debian/changelog
--- libdigest-whirlpool-perl-1.09/debian/changelog
+++ libdigest-whirlpool-perl-1.09/debian/changelog
@@ -1,3 +1,12 @@
+libdigest-whirlpool-perl (1.09-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965635)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 16:47:12 +0100
+
 libdigest-whirlpool-perl (1.09-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libdigest-whirlpool-perl-1.09/debian/compat libdigest-whirlpool-perl-1.09/debian/compat
--- libdigest-whirlpool-perl-1.09/debian/compat
+++ libdigest-whirlpool-perl-1.09/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libdigest-whirlpool-perl-1.09/debian/control libdigest-whirlpool-perl-1.09/debian/control
--- libdigest-whirlpool-perl-1.09/debian/control
+++ libdigest-whirlpool-perl-1.09/debian/control
@@ -1,7 +1,7 @@
 Source: libdigest-whirlpool-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 5), perl (>= 5.6.10-12), libdigest-perl
+Build-Depends: debhelper (>= 7), perl (>= 5.6.10-12), libdigest-perl
 Maintainer: James Bromberger 
 Standards-Version: 3.9.2
 Homepage: http://search.cpan.org/dist/


signature.asc
Description: Digital Signature

Bug#965698: libxml-rss-feed-perl: diff for NMU version 2.212-1.4

[gregor herrmann]

Control: tags 965698 + patch
Control: tags 965698 + pending


Dear maintainer,

I've prepared an NMU for libxml-rss-feed-perl (versioned as 2.212-1.4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Jimi Hendrix: Hear My Train A Comin'
diff -u libxml-rss-feed-perl-2.212/debian/changelog libxml-rss-feed-perl-2.212/debian/changelog
--- libxml-rss-feed-perl-2.212/debian/changelog
+++ libxml-rss-feed-perl-2.212/debian/changelog
@@ -1,3 +1,12 @@
+libxml-rss-feed-perl (2.212-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Removal of obsolete debhelper compat 5 and 6 in bookworm":
+Bump to 7 in debian/{compat,control}.
+(Closes: #965698)
+
+ -- gregor herrmann   Sun, 26 Dec 2021 16:41:13 +0100
+
 libxml-rss-feed-perl (2.212-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libxml-rss-feed-perl-2.212/debian/compat libxml-rss-feed-perl-2.212/debian/compat
--- libxml-rss-feed-perl-2.212/debian/compat
+++ libxml-rss-feed-perl-2.212/debian/compat
@@ -1 +1 @@
-5
+7
diff -u libxml-rss-feed-perl-2.212/debian/control libxml-rss-feed-perl-2.212/debian/control
--- libxml-rss-feed-perl-2.212/debian/control
+++ libxml-rss-feed-perl-2.212/debian/control
@@ -2,7 +2,7 @@
 Section: perl
 Priority: optional
 Maintainer: Erik Vetters 
-Build-Depends: debhelper (>= 5), perl, libxml-rss-perl
+Build-Depends: debhelper (>= 7), perl, libxml-rss-perl
 Standards-Version: 3.7.2
 
 Package: libxml-rss-feed-perl


signature.asc
Description: Digital Signature

Bug#1002564: [pkg-lxc-devel] Bug#1002564: lxc: packaging adjustments for LXD

[Antonio Terceiro]

On Sat, Dec 25, 2021 at 02:25:06PM +, Evgeni Golov wrote:
> 
> 
> On December 25, 2021 12:35:45 PM UTC, Antonio Terceiro  
> wrote:
> >On Fri, Dec 24, 2021 at 06:04:04AM +, Mathias Gibbens wrote:
> >> Source: lxc
> >> Version: 1:4.0.10-1
> >> Severity: normal
> >> 
> >>   Work on packaging LXD for Debian (ITP #768073) is getting pretty
> >> close to completion. I've recently started testing the LXD package that
> >> I am able to build locally, making sure everything is working properly
> >> before it's uploaded to NEW once the few remaining dependencies make it
> >> through NEW themselves.
> >> 
> >>   LXD depends on the liblxc1 package, but not on the lxc package
> >> itself. However, there are a few files currently shipped in the lxc
> >> package that LXD needs to properly start. Specifically, the apparmor
> >> profiles (all of /etc/apparmor.d/, except /etc/apparmor.d/usr.bin.lxc-
> >> start) and the /usr/lib/-linux-gnu/lxc/rootfs/ directory.
> >> 
> >>   I'm hoping we can figure out a nice way to make these dependencies of
> >> LXD available without having to pull in lxc itself (plus its own
> >> dependencies). The easiest way might be to just move them to liblxc1,
> >> which both lxc and LXD packages will depend on. Or, there might be some
> >> other solution that could work.
> >
> >They probably would need to be provided by a (NEW) lxc-common package.
> >If we ever need to transition to liblxc2, we don't want both liblxc*
> >packages providing those files.
> 
> On Ubuntu, this package us called liblxc-common, which we probably
> should also use, to make life of other consumers easier?

Sure! I didn't check there first.


signature.asc
Description: PGP signature

Bug#897950: Bug#1002597: curl: temporarily revert adding libssh-dev to Build-Depends

[Samuel Henrique]

Dropping 1002597 from the discussion to focus on 897950.

On Sun, 26 Dec 2021 at 10:59, Daniel Stenberg  wrote:
> What the reason for the switch to begin with? The only reason state in 897950
> seems to be "that's a better maintained library and other distributions
> already switched to it".

Fedora's wiki states a few security improvements[0], though I didn't
double check whether those apply to curl's usage of ssh.

> 1. How is it "a better maintained library" ?

I assume this is judging by the amount of recent commits on both
projects, so it's not a perfect metric and it's gonna be hard to argue
for it in case of disagreement. My assumption might be wrong though
and the people who said it could have different metrics for it.

> 2. Why does it matter what other distros have done? Surely other distros do
> all sorts of crazy decisions all the time. Why is this particular one you
> think is fine to follow?

Let me try to describe where I stand.
By following other distros we benefit from a bigger userbase and thus
increased chances of receiving patches from those distros through
upstream. In the case of syncing with Ubuntu this is even better as
they're constantly sending patches back to us. It's a bit of a
symbiotic relationship cause they also don't wanna carry over deltas
from Debian.
It's also sometimes good to try to standardise the packages on a
certain library and focus on that, instead of maintaining multiple
ones. This is one of the reasons Ubuntu switched to libssh, though I
can't say yet if Debian will benefit from this as well (we usually
support multiple libraries).

This being said, these things don't weigh over "crazy decisions", so
we can always divert if we think it's the right thing.

Daniel, I won't rush this change and I value your input on this, as
both curl and libssh2's upstream, so feel free to take your time to
reply.

On my initial assessment I couldn't find considerable differences that
would weigh in favour of staying with libssh2, I did stumble upon your
blogposts talking about performance (libssh2 being better) but they
are a bit old and I'm not sure if it's still applicable.

>From your message, I believe you are leaning towards sticking with
libssh2, and I would be happy to hear your thoughts on it.

[0] https://fedoraproject.org/wiki/Changes/libssh-in-libcurl

Thank you,

-- 
Samuel Henrique 

Bug#1001999: snapd: packaging not up to Debian standards

[Mathias Gibbens]

  There was something weird with me not receiving Michael's initial
reply. I did review my server's logs, but didn't see anything
indicating what the problem was. I do want to include his reply, so
others who see this bug can have the whole context:

> On Wed, Dec 08, 2021 at 02:01:03PM +0100, Michael Vogt wrote:
> [..]
> >   Specific concerns that I have observed:
> >
> >   * The most recent commit in the snapd salsa repository, which is
> > pointed to by the package's d/control file, was on April 6, 2020.
> > However, new versions of this package have continued to appear and
> been
> > uploaded to the archive; where is the git repo for snapd's
> packaging
> > being maintained?
> 
> 
> I always push my commits to https://salsa.debian.org/mvo/snapd but
> indeed I failed to do MR against the main repo. Sorry for that. I
> added it now.
> 
> I was mostly working in my "mvo" area because I was not intending to
> become the maintainer and just help out but it seems like it's best
> if
> I get more involved - unless someone else is interested of course :)
> 
> >
> >   * snapd 2.37.4-1 was the last upload (February 28, 2019) to the
> > archive by a Maintainer/Uploader. All subsequent uploads to
> unstable
> > have been by Michael Vogt, who is _not_ listed as a
> > Maintainer/Uploader, and doesn't appear to be following the proper
> NMU
> > process.
> 
> 
> Indeed, see above, I mostly just wanted to help a bit and did not
> want
> to step on toes by adding myself but I think I should probably be at
> least in the Uploaders field.
> 
> >
> >   * An outstanding FTBFS bug (#997257) has been open since October
> 23rd
> > of this year, and has yet to receive an acknowledgment.
> 
> 
> Sorry again, I will have a look. I was planning to do a new upload to
> Debian with the latest snapd release anyway before 2021 ends and
> there
> I can tackle this.
> 
> >
> >   * The last d/changelog entry by a Maintainer/Uploader was July
> 27,
> > 2020. Since August 2020, only Michael Vogt and Ian Johnson have
> been
> > making release entries which seem to solely consist of copy-and-
> paste
> > upstream release changelogs.
> 
> 
> I'm not 100% up-to-date with the latest recommendations around
> changelogs, I'm happy to avoid using the upstream changelog and just
> do the debian specific bits. Is that the right approach?
> 
> >
> >   * No care seems to have been recently given to reported lintian
> > errors/warnings, an ancient Standards-Version, dependency on an old
> > version of the `golang` package, etc.
> 
> 
> That is unfortunately correct, as part of this new release I can try
> to address it too. Note that the upstream snapd project defaults to
> fairly old golang releases because they want to be compilable on
> older
> distros too but of course there is no need to enforce this on debian.
> 
> >
> >   * Several outstanding bugs are in the BTS with no interaction
> from
> > snapd's Maintainer or Uploaders, either in bug reports or via
> > d/changelog entries. (One bug was just closed in 2.51.7-2, but I
> have
> > to go back to January 9, 2018 to find the next bug closed by a new
> > release of snapd.)
> 
> 
> Indeed, it's a valid concern, I did not pay enough attention there.
> But then I also just wanted to help a bit with the releases and not
> intended to fully take over maintenance. But it seems I need to try
> to
> also help more in this area.
> 
> >
> >   * d/rules is _ugly_. (Admittedly, this is a subjective call, but
> it
> > could be greatly cleaned up and "un-Ubuntued" by removing logic
> that
> > don't have anything to do with Debian.)
> 
> 
> Heh :) it is a ugly - it's mostly like this for pragmatic reason,
> there is a debian/rules file in the main tree of snapd so it's
> easiest
> to keep the delta small to make syncing changes back easy. But maybe
> it's the wrong trade-off?
> 
> Any help here is welcome btw (from anyone in the CC). I'm a bit rusty
> with the latest Debian policy and my day-job is quite demanding
> 
> Cheers,
>  Michael

  Based on Micahel's comments, it sounds like a couple actions could be
taken that would help more accurately reflect snapd's current state:

  * Formally ping the package maintainer/uploaders (who I haven't seen
any replies from) to ask about filing a RFH/RFA bug against snapd.

  * Also ask them about moving the snapd package into the go-team's
group on salsa, and putting the package under team maintenance. That
would make it a lot easier for individuals to make updates without
stepping on toes.

  Overall it sounds like snapd needs a new maintainer with the time and
interest to maintain the package. As I said, I don't use snaps, and I
don't want to take on packages that I don't actually use. And Michael
sounds pretty busy; I think it may almost be worse to have a barely-
maintained package than an unmaintained one.

Mathias


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

Bug#1002646: apt: please add a pattern that allows one to select packages by codename

[Johannes Schauer Marin Rodrigues]

Package: apt
Version: 2.3.13
Severity: normal
X-Debbugs-Cc: jo...@debian.org

Hi,

I need a pattern that allows me to match codenames in addition to
archive names, so that I can do:

apt-get install 
?narrow(?or(?archive($foo),?codename($foo)),?architecture(amd64),?essential)

Because I don't know whether $foo will be something like "unstable" or
"sid" but both should work.

Thanks!

cheers, josch