date:20221118

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

The build path is embedded in various .html files:

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

Some local diffoscope output revealed this example:

│ │ │ ├── ./usr/share/doc/libpresage-doc/html/variable_8h_source.html
...
│ │ │ │ -presage: 
/tmp/reprotest.mC8kkh/const_build_path/src/lib/core/variable.h Source 
File
│ │ │ │ +presage: 
/tmp/reprotest.mC8kkh/build-experiment-1/src/lib/core/variable.h Source 
File

The attached patch to the upstream doc/Doxyfile.in fixes this by setting
FULL_PATH_NAMES to "NO" to avoid embedding the build path.

According to my local tests, with this patch applied presage should build
reproducibly on tests.reproducible-builds.org!

Thanks for maintaining presage!

live well,
  vagrant
From 5afba5986ec2cad849d6c04922bf11ee2a1d5695 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sat, 19 Nov 2022 04:55:29 +
Subject: [PATCH] doc/Doxyfile.in: Set FULL_PATH_NAMES to "NO" to avoid
 embedding build paths in documentation.

https://tests.reproducible-builds.org/debian/issues/unstable/build_dir_in_documentation_generated_by_doxygen_issue.html
---
 doc/Doxyfile.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/Doxyfile.in b/doc/Doxyfile.in
index 24efbaf..e221d9f 100644
--- a/doc/Doxyfile.in
+++ b/doc/Doxyfile.in
@@ -119,7 +119,7 @@ INLINE_INHERITED_MEMB  = NO
 # path before files name in the file list and in the header files. If set
 # to NO the shortest path that makes the file name unique will be used.
 
-FULL_PATH_NAMES= YES
+FULL_PATH_NAMES= NO
 
 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
 # can be used to strip a user-defined part of the path. Stripping is
-- 
2.38.1



signature.asc
Description: PGP signature

Bug#1023769: efi-reader: Please add support for "riscv64" arch

2022-11-18 Thread Manuel A. Fernandez Montecelo

Hi Steve,

On Sun, 13 Nov 2022 at 00:05, Steve McIntyre  wrote:
>
> Hey Manuel!
>
> On Wed, Nov 09, 2022 at 10:57:56PM +0100, Manuel A. Fernandez Montecelo wrote:
> >Source: efi-reader
> >Version: 0.16
> >Severity: wishlist
> >Tags: ftbfs patch
> >User: debian-ri...@lists.debian.org
> >Usertags: riscv64
> >X-Debbugs-Cc: m...@debian.org, debian-ri...@lists.debian.org
> >
> >Hi,
> >
> >Please enable this architecture, with the patch attached or an equivalent.
> >
> >I built it locally on hardware, it built fine just by enabling the 
> >architecture
> >in debian/control, no other changes needed.
>
> Are you sure you need to build efi-reader here? It's mostly a no-op
> package on the existing arches already, and I'd be surprised if there
> is any use for it on on riscv64.

Actually I didn't pay much attention to what the program does, I
stumbled upon it when trying to find small packages to test building
infra and that was it.  At the end of the tests I was submitting these
requests for several of the packaes.

Being part of debian-installer I imagined that it's needed in some
circumstances even if it's a tiny --but perhaps important-- part...
there's not much info to go by in the descriptions, and I'm not very
familiar with the installer other than as a user.

So dunno, I think that you're in a better position to decide whether
it's needed or not, I'm happy if you prefer to close this report.

Cheers!
-- 
Manuel A. Fernandez Montecelo

Bug#1022526: python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

Control: tags -1 fixed-upstream

On Sun, Nov 13, 2022 at 10:04:04AM +0200, Stefano Rivera wrote:
> Hi Helmut (2022.11.04_11:36:41_+0200)
> > And no, updating it to 3.4 does not fix the ftbfs.
> 
> Updating it to 3.4.1 might. It includes this commit:
> https://github.com/DinoTools/python-ssdeep/commit/fce02106c07ff56a84097dec0df02fb00ef69dc7
> which moves the setuptools import above the first distutils import,
> which should resolve this issue.

I can confirm that 3.4.1 does fix the build
(but I am reluctant to update it myself).

> SR

cu
Adrian

Bug#1024355: opensysusers: fails to first-install

2022-11-18 Thread Samuel Thibault

Andrea Pappacoda, le sam. 19 nov. 2022 00:21:08 +0100, a ecrit:
> Anyway, would you simply suggest to drop the `u` shell option?

I'd say so. Here the preinst script definitely is expected to see either
$2 set or not.

Samuel

Bug#1020258: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver

2022-11-18 Thread Sean Whitton

Hello,

On Sat 19 Nov 2022 at 06:50AM +09, Tatsuya Kinoshita wrote:

> On 2022-11-18 at 11:44 -0700, Sean Whitton wrote:
>> I can't reproduce this locally, and looking at the package tracker for a
>> few of those packages you've listed, piuparts is now passing
>
> The piuparts tests with the listed pacakges may succeed when emacs
> (or emacs{-gtk,-lucid,-nox}) isn't installed.  To reproduce, use
> `piuparts elpa-elscreen_*.deb` because it brings emacs-nox|emacs.
>
>>   ld: cannot find crti.o: No such file or directory
>
> It seems native compilation requires crti.o provided by libc6-dev,
> so adding libc6-dev to the Depends line of emacs{-gtk,-lucid,-nox}
> may prevent this problem, though I don't know whether it should be
> fixed in libgccjit0.

It's a pretty heavy dependency, and as you say, it might not be
src:emacs that has the bug.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1024355: opensysusers: fails to first-install

2022-11-18 Thread Andrea Pappacoda

Hi Samuel, thank you very much for the report.

On Fri, 18 Nov 2022 09:40:11 +0100 Samuel Thibault 
 wrote:

> Version 0.7.3-1 of opensysusers made it uninstallable:
>
> (Reading database ... 936343 files and directories currently 
installed.)

> Preparing to unpack .../opensysusers_0.7.3-1_all.deb ...
> Adding 'diversion of /bin/systemd-sysusers to 
/bin/systemd-sysusers.real by opensysusers'

> /var/lib/dpkg/tmp.ci/preinst: 15: 2: parameter not set
> dpkg: error processing archive 
/var/cache/apt/archives/opensysusers_0.7.3-1_all.deb (--unpack):
>  new opensysusers package pre-installation script subprocess 
returned error exit status 2

>
> Indeed, preinst uses set -u, and then tries [ -n "$2" ] (expanded 
from

> dh_installinit), thus deemed to fail under first installation.

Strange... I too noticed that version 0.7.3-1 introduced a piuparts 
error, but the release is pretty much identical to 0.7.2-1, as 0.7.2-1 
already contained the only new upstream commit in 0.7.3.

Anyway, would you simply suggest to drop the `u` shell option? I added 
it only because I usually do so, but there's no strong motivation 
behind it.

Thanks again :)

Bug#1023386: pacman-package-manager: Please backport to bullseye-backports

2022-11-18 Thread Ben Westover

Bonjour Dylan,

On 11/14/22 09:41, Dylan Aïssi wrote:
>> I've elected to just build it with the nocheck profile.
>
> Currently, without adding at least python3-distutils (and maybe other?) in BD,
> pcm fails at the dh_auto_configure step with:
>
>> ModuleNotFoundError: No module named 'distutils.core'
>> ../meson.build:31:0: ERROR:  
>> ['/usr/bin/python3']> is not a valid python or it is missing setuptools
>> dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
>> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
>> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dkeyringd
>
> This is easily reproducible with salsa-ci by setting RELEASE to
> bullseye like I did here:
>> https://salsa.debian.org/daissi/pacman/-/jobs/3514447
>
> My point is this issue is hidden in sid because python3-distutils is
> pulled by dependencies,
> but it (or python3-all) must be added in the Build-Deps of pcm even
> for sid. Moreover,
> based on the meson.build, it looks like python3 is not an optional build-deps.

Interesting, didn't show up with my local sbuild runs for my personal
archive. I had unmodified backports build fine with a nodoc flag. But if
I test nodoc with Salsa it fails as you showed me. Strange.

Thanks,
--
Ben Westover


OpenPGP_signature
Description: PGP signature

Bug#983815: python-crc32c: diff for NMU version 2.3-1.1

Control: tags 983815 + pending

Dear maintainer,

I've prepared an NMU for python-crc32c (versioned as 2.3-1.1) and 
uploaded it to DELAYED/4. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -Nru python-crc32c-2.3/debian/changelog python-crc32c-2.3/debian/changelog
--- python-crc32c-2.3/debian/changelog	2022-09-17 16:36:38.0 +0300
+++ python-crc32c-2.3/debian/changelog	2022-11-19 00:42:32.0 +0200
@@ -1,3 +1,10 @@
+python-crc32c (2.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix baseline violation on x86 and arm. (Closes: #983815)
+
+ -- Adrian Bunk   Sat, 19 Nov 2022 00:42:32 +0200
+
 python-crc32c (2.3-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru python-crc32c-2.3/debian/patches/0001-Fix-baseline-violations-on-x86-and-arm.patch python-crc32c-2.3/debian/patches/0001-Fix-baseline-violations-on-x86-and-arm.patch
--- python-crc32c-2.3/debian/patches/0001-Fix-baseline-violations-on-x86-and-arm.patch	1970-01-01 02:00:00.0 +0200
+++ python-crc32c-2.3/debian/patches/0001-Fix-baseline-violations-on-x86-and-arm.patch	2022-11-19 00:42:32.0 +0200
@@ -0,0 +1,46 @@
+From 252ffe48a20f8897f02986752aae3f5d2b40535f Mon Sep 17 00:00:00 2001
+From: Adrian Bunk 
+Date: Sat, 19 Nov 2022 00:47:00 +0200
+Subject: Fix baseline violations on x86 and arm
+
+These extensions are not part of the baseline of any port.
+---
+ common.h | 6 --
+ setup.py | 4 
+ 2 files changed, 10 deletions(-)
+
+diff --git a/common.h b/common.h
+index cdf02de..3b163a3 100644
+--- a/common.h
 b/common.h
+@@ -26,12 +26,6 @@
+ #ifndef _COMMON_H_
+ #define _COMMON_H_
+ 
+-#if defined(__x86_64__) || defined(_M_X64) || defined(i386) || defined(__i386__) || defined(__i386) || defined(_M_IX86)
+-# define IS_INTEL
+-#elif defined(__aarch64__) || defined(_M_ARM64)
+-# define IS_ARM
+-#endif
+-
+ /* inline support (it's not a keyword in MSVC for C code) */
+ #if defined(_MSC_VER)
+ # define CRC32C_INLINE __inline
+diff --git a/setup.py b/setup.py
+index a6192b8..f0b0037 100644
+--- a/setup.py
 b/setup.py
+@@ -39,10 +39,6 @@ def get_extra_compile_args(is_intel, is_arm):
+ comp = distutils.ccompiler.get_default_compiler()
+ if comp == 'msvc':
+ return ['/O2']
+-elif is_intel:
+-return ['-O3', '-msse4.2', '-mpclmul']
+-elif is_arm:
+-return ['-O3', '-march=armv8-a+crc+crypto']
+ else:
+ return ['-O3']
+ 
+-- 
+2.30.2
+
diff -Nru python-crc32c-2.3/debian/patches/series python-crc32c-2.3/debian/patches/series
--- python-crc32c-2.3/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ python-crc32c-2.3/debian/patches/series	2022-11-19 00:42:32.0 +0200
@@ -0,0 +1 @@
+0001-Fix-baseline-violations-on-x86-and-arm.patch

Bug#1017907: ffado-mixer-qt4 fails to start with python 3.10

2022-11-18 Thread Alexandre Lymberopoulos

Package: ffado-mixer-qt4
Version: 2.4.6-1
Followup-For: Bug #1017907

Dear Maintainer,

I confirm the mentioned bug. Benoît proposed a solution that seems legit.

Best, Alexandre

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

Kernel: Linux 6.0.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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)

Versions of packages ffado-mixer-qt4 depends on:
ii  ffado-dbus-server2.4.6-1
ii  ffado-tools  2.4.6-1
ii  python3  3.10.6-1
ii  python3-dbus 1.3.2-1
ii  python3-dbus.mainloop.pyqt5  5.15.7+dfsg-2
ii  python3-pyqt55.15.7+dfsg-2

ffado-mixer-qt4 recommends no packages.

ffado-mixer-qt4 suggests no packages.

-- no debconf information

Bug#997915: pipewire issues with M-Audio 410

2022-11-18 Thread Alexandre Lymberopoulos


Hello, Dylan!

Things are going much better with the new releases: 996367 seems to be 
solved, but 997915 persists. For the latter it seems to be something 
like capturing sources with different sample rates (like 48Khz and 
44Khz). This guess is due to the resulting sound: the "default" 
recording device (as selected with pavucontrol - have pipewire, pulse 
and jack installed here! more on this later) have nice sound and the 
other sounds like playing a standard 33rpm vinyl in 45rpm (revealing my 
age here) with a lot of clips.


To make things tidy and clean here I would like to know if there is a 
way to keep just pipewire running here (over ALSA, probably) and if 
there are some mixer software to use with pipewire (ffado-mixer stopped 
working with M-Audio 410 here).


Best,
Alexandre

===
Alexandre Lymberopoulos - lym...@gmail.com
===


On Fri, Nov 18 2022 at 02:54:57 PM +01:00:00, Dylan Aïssi 
 wrote:

Hello Alexandre,

My apologies for not responding earlier.

Do you still have these problems with pipewire or have they been 
solved

with the new versions?

Best,
Dylan

Bug#1024000: pink-pony: diff for NMU version 1.4.1-3.1

Control: tags 880943 + pending
Control: tags 1024000 + patch
Control: tags 1024000 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru pink-pony-1.4.1/debian/changelog pink-pony-1.4.1/debian/changelog
--- pink-pony-1.4.1/debian/changelog	2022-01-29 04:59:32.0 +0200
+++ pink-pony-1.4.1/debian/changelog	2022-11-19 00:18:31.0 +0200
@@ -1,3 +1,11 @@
+pink-pony (1.4.1-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix compilation with libimath-dev. (Closes: #1024000)
+  * Add upstream fix for Fancy Water. (Closes: #880943)
+
+ -- Adrian Bunk   Sat, 19 Nov 2022 00:18:31 +0200
+
 pink-pony (1.4.1-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru pink-pony-1.4.1/debian/control pink-pony-1.4.1/debian/control
--- pink-pony-1.4.1/debian/control	2022-01-29 04:56:56.0 +0200
+++ pink-pony-1.4.1/debian/control	2022-11-19 00:18:31.0 +0200
@@ -11,7 +11,7 @@
  libftgl-dev,
  libglfw3-dev,
  libglu1-mesa-dev,
- libilmbase-dev,
+ libimath-dev,
  libprotobuf-dev (>= 2),
  libsdl-mixer1.2-dev,
  libsdl1.2-dev,
diff -Nru pink-pony-1.4.1/debian/patches/0001-Fix-compile-issues-caused-by-Imath-being-moved-out-o.patch pink-pony-1.4.1/debian/patches/0001-Fix-compile-issues-caused-by-Imath-being-moved-out-o.patch
--- pink-pony-1.4.1/debian/patches/0001-Fix-compile-issues-caused-by-Imath-being-moved-out-o.patch	1970-01-01 02:00:00.0 +0200
+++ pink-pony-1.4.1/debian/patches/0001-Fix-compile-issues-caused-by-Imath-being-moved-out-o.patch	2022-11-19 00:18:15.0 +0200
@@ -0,0 +1,42 @@
+From 72a83f01d196e943a5549f0ff81c013d2bbd0a8c Mon Sep 17 00:00:00 2001
+From: Thomas Weber 
+Date: Sat, 2 Oct 2021 13:49:12 +0200
+Subject: Fix compile issues caused by Imath being moved out of IlmBase
+
+diff --git a/src/Line.cc b/src/Line.cc
+index 10a8193..c757b57 100644
+--- a/src/Line.cc
 b/src/Line.cc
+@@ -1,15 +1,15 @@
+ #include "Line.hh"
+-#include 
++#include 
+ 
+-#define EPSILON limits::epsilon()
++#define EPSILON std::limits::epsilon()
+ 
+ bool Line::intersects(const Line& seg)
+-{
++{
+ double ax = a.x, ay = a.y;
+ double bx = b.x, by = b.y;
+ double cx = seg.a.x, cy = seg.a.y;
+ double dx = seg.b.x, dy = seg.b.y;
+-
++
+ double S = (((cx*(dy - ay)) + (dx*(ay - cy)) + (ax*(cy - dy)))/(((bx - ax)*(dy - cy)) + ((by - ay)*(cx - dx;
+ double T = 1.0 - S)*ay) + (S*by) - cy)/(dy - cy));
+ 
+@@ -22,7 +22,7 @@ V2d Line::intersection(const Line& seg)
+ double bx = b.x, by = b.y;
+ double cx = seg.a.x, cy = seg.a.y;
+ double dx = seg.b.x, dy = seg.b.y;
+-
+-double S = (((cx*(dy - ay)) + (dx*(ay - cy)) + (ax*(cy - dy)))/(((bx - ax)*(dy - cy)) + ((by - ay)*(cx - dx; 
++
++double S = (((cx*(dy - ay)) + (dx*(ay - cy)) + (ax*(cy - dy)))/(((bx - ax)*(dy - cy)) + ((by - ay)*(cx - dx;
+ 	return (1-S) * a + S * b;
+ }
+-- 
+2.30.2
+
diff -Nru pink-pony-1.4.1/debian/patches/0001-Various-fixes.patch pink-pony-1.4.1/debian/patches/0001-Various-fixes.patch
--- pink-pony-1.4.1/debian/patches/0001-Various-fixes.patch	1970-01-01 02:00:00.0 +0200
+++ pink-pony-1.4.1/debian/patches/0001-Various-fixes.patch	2022-11-19 00:18:31.0 +0200
@@ -0,0 +1,25 @@
+From f2eb8f0dc1d403428b9f287d414e925a006b2d70 Mon Sep 17 00:00:00 2001
+From: Thomas Weber 
+Date: Sat, 3 Nov 2018 21:44:31 +0100
+Subject: Various fixes
+
+---
+ resources/GLSL/water.frag | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/resources/GLSL/water.frag b/resources/GLSL/water.frag
+index 4264d24..7c25a46 100644
+--- a/resources/GLSL/water.frag
 b/resources/GLSL/water.frag
+@@ -26,7 +26,7 @@ float dispf(vec2 p)
+ 
+ vec3 displacement(vec3 wp, float dist)
+ {
+-return wp + normal * (dispf(wp.xz) * min(1.0,2.0/pow(dist,1)) * 0.5 + 0.5) * 4.0;
++return wp + normal * (dispf(wp.xz) * min(1.0,2.0/dist) * 0.5 + 0.5) * 4.0;
+ }
+ 
+ void main (void)
+-- 
+2.30.2
+
diff -Nru pink-pony-1.4.1/debian/patches/series pink-pony-1.4.1/debian/patches/series
--- pink-pony-1.4.1/debian/patches/series	2022-01-29 04:48:50.0 +0200
+++ pink-pony-1.4.1/debian/patches/series	2022-11-19 00:18:31.0 +0200
@@ -2,3 +2,5 @@
 datadir.patch
 tinyxml.patch
 glfw3.patch
+0001-Fix-compile-issues-caused-by-Imath-being-moved-out-o.patch
+0001-Various-fixes.patch
diff -Nru pink-pony-1.4.1/debian/SConstruct pink-pony-1.4.1/debian/SConstruct
--- pink-pony-1.4.1/debian/SConstruct	2022-01-29 04:48:50.0 +0200
+++ pink-pony-1.4.1/debian/SConstruct	2022-11-19 00:18:31.0 +0200
@@ -7,7 +7,7 @@
 env['LIBS'] = ['GLU', 'GL', 'protobuf', 'IL']
 env['CPPPATH'] = ['#', '#/src', '#/external/flextGL/', '/usr/include/OpenEXR']
 
-env.ParseConfig("pkg-config IlmBase --cflags --libs")
+env.ParseConfig("pkg-config Imath --cflags --libs")
 env.ParseConfig("pkg-config glfw3 --cflags --libs")

Bug#1006996: Bug #1006996: mate-polkit: On arm64 architecture mate-polkit tries to open an amd64 file and fails

2022-11-18 Thread Mike Gabriel


Hi Thomas, dear DD colleagues (et al.),

On  Fr 18 Nov 2022 20:55:39 CET, Thomas Uhle wrote:


Dear maintainers,

in addition to Christian Britz' report, the autostart desktop file  
should also be in mate-polkit because of the architecture triplet in  
the path to polkit-mate-authentication-agent-1, and the provided  
manpage has not yet been moved to mate-polkit-bin what causes a  
lintian issue.


I have prepared a patch that should fix all these packaging issues.

Best regards,

Thomas Uhle


The change-over of the XDG autostart file from common:pkg  
mate-polkit-common to bin:pkg mate-polkit is not as simple as it seems.


This is why I am cross-posting to the debian-devel mailing list and  
would like to ask for ideas...


Here is the challenge:

The flaw in mate-polkit is that the  
/etc/xdg/autostart/.desktop file so far has been shipped  
in mate-polkit-common (which usually got built on amd64 builders) and  
that that .desktop file contains a multi-arch path in the Exec= key.


So, for non-amd64 architectures, the .desktop files tries to execute a  
polkit-agent binary at some amd64 multi-arch path. Thanks to Christian  
and Thomas for dealing with this and reporting the issue.


With the next upload of mate-polkit src:pkg I want to achieve these things:

  * move /etc/xdg/autostart/.desktop from  
mate-polkit-common (arch:all) to

mate-polkit (arch:any), ... and yes, I have seen #595112

  * as the Exec= field in this file definitely needs to get updated  
on non-amd64 machines

(see #1006996), I most certainly don't want to keep versions of that
file (stemming from arch-indep mate-polkit-common) that got  
modified by the site/machine
admin. In most cases, I want to install the new version from the  
arch-dep package mate-polkit.


  * so for non-amd64 architectures, the best solution probably is to  
remove the
previous .desktop (mate-polkit-common) file and  
replace it by the new

.desktop file (ignoring local changes)

Question to DD colleagues: How can this be achieve in a clean way  
without piuparts (or other QA tools) yelling at me afterwards? Any  
spontaneous ideas???


To simplify life (and yes, this is debatable): Do situations exist,  
where an enforced conffile update (overwriting it) is allowed /  
justifiable? If so, do you know example packages that exercise this?


Thanks in advance for any feedback!
Mike




--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp3xKzepzJj6.pgp
Description: Digitale PGP-Signatur

Bug#1024395: Downgrading fixes the problem.


downgrading to 1+2.06+3~deb11x

grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin 
grub-efi-amd64-signed grub2-common  shim-helpers-amd64-signed


fix the error.

However the mokutils --list-enrolled command is still void.

-- eric

Bug#1024395: inconsistencies between shim-signed versions (= 15.4-7) and shim-helpers-amd64-signed shim (= 15.6-1)


dpkg -s shim-signed
Package: shim-signed
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 937
Maintainer: Debian EFI Team 
Architecture: amd64
Multi-Arch: same
Source: shim-signed (1.38)
Version: 1.38+15.4-7
Depends: shim-signed-common (>= 1.38+15.4-7), grub-efi-amd64-bin, 
shim-helpers-amd64-signed (>= 1+15.4+2), grub2-common (>= 2.02+dfsg1-16)

Recommends: secureboot-db
Description: Secure Boot chain-loading bootloader (Microsoft-signed binary)
 This package provides a minimalist boot loader which allows verifying
 signatures of other UEFI binaries against either the Secure Boot DB/DBX or
 against a built-in signature database.  Its purpose is to allow a small,
 infrequently-changing binary to be signed by the UEFI CA, while allowing
 an OS distributor to revision their main bootloader independently of 
the CA.

 .
 This package contains the version of the bootloader binary signed by the
 Microsoft UEFI CA.
Built-Using: shim (= 15.4-7)

dpkg -s shim-helpers-amd64-signed
Package: shim-helpers-amd64-signed
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 934
Maintainer: Debian EFI team 
Architecture: amd64
Version: 1+15.6+1
Replaces: shim (<< 15+1533136590.3beb971-3~), shim-signed (<< 1.29)
Depends: shim-unsigned (>= 15.6-1)
Breaks: shim-signed (<< 1.29)
Conflicts: shim (<< 15+1533136590.3beb971-3~)
Description: boot loader to chain-load signed boot loaders (signed by 
Debian)

 This package provides a minimalist boot loader which allows verifying
 signatures of other UEFI binaries against either the Secure Boot DB/DBX or
 against a built-in signature database.  Its purpose is to allow a small,
 infrequently-changing binary to be signed by the UEFI CA, while allowing
 an OS distributor to revision their main bootloader independently of 
the CA.

 .
 This package contains the MOK manager and fall-back manager signed by the
 Debian UEFI CA to be used by shim-signed.
Built-Using: shim (= 15.6-1)

-- eric

Bug#1020258: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver

2022-11-18 Thread Tatsuya Kinoshita

On 2022-11-18 at 11:44 -0700, Sean Whitton wrote:
> I can't reproduce this locally, and looking at the package tracker for a
> few of those packages you've listed, piuparts is now passing

The piuparts tests with the listed pacakges may succeed when emacs
(or emacs{-gtk,-lucid,-nox}) isn't installed.  To reproduce, use
`piuparts elpa-elscreen_*.deb` because it brings emacs-nox|emacs.

>   ld: cannot find crti.o: No such file or directory

It seems native compilation requires crti.o provided by libc6-dev,
so adding libc6-dev to the Depends line of emacs{-gtk,-lucid,-nox}
may prevent this problem, though I don't know whether it should be
fixed in libgccjit0.

Thanks,
--
Tatsuya Kinoshita

pgpRCKLpfm9vV.pgp
Description: PGP signature

Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1

2022-11-18 Thread Étienne Mollier

Control: tags -1 + patch

Hi Sébastien,

orthanc-dicomweb is currently affected by a failure to build
from source (Bug#1023738).  I took the liberty to have a look,
and it seems that since axios 1.0 the dist/axios.map file is not
provided anymore.  This is causing the following cmake error:

CMake Error at debian/ThirdPartyDownloads/JavaScriptLibraries.cmake:29 
(file):
  file COPY_FILE failed to copy

/usr/share/nodejs/axios/dist/axios.map

  to

/<>/Build/javascript-libs/js/axios.min.map

Scanning through the source code, I noticed that axios.min.map
file was not used anywhere (only mention is in a cmake file
which is patched out in Debian context).  When removing the
reference this way, I got the package to build again:

---8<--8<--8<--8<---
--- a/debian/ThirdPartyDownloads/JavaScriptLibraries.cmake
+++ b/debian/ThirdPartyDownloads/JavaScriptLibraries.cmake
@@ -26,11 +26,6 @@ file(COPY_FILE
   ${JAVASCRIPT_LIBS_DIR}/js/axios.min.js
   )
 
-file(COPY_FILE
-  /usr/share/nodejs/axios/dist/axios.map
-  ${JAVASCRIPT_LIBS_DIR}/js/axios.min.map
-  )
-
 file(COPY
   
${CMAKE_SOURCE_DIR}/debian/ThirdPartyDownloads/bootstrap-vue/bootstrap-vue.min.css
   
${CMAKE_SOURCE_DIR}/debian/ThirdPartyDownloads/bootstrap-vue/bootstrap-vue.min.css.map
--->8-->8-->8-->8---

Since my knowledge of the nodejs ecosystem is near zero, I'd
rather ask: would such change look sound or do you foresee any
adverse effects?

In hope this helps,
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Haken - Bound By Gravity


signature.asc
Description: PGP signature

Bug#1021530: wireplumber: conflict with pulseaudio?

2022-11-18 Thread Francois Le Hir

Hi Dylan,

I did not mask pipewire-pulse.service.
I believe my system started with just pulseaudio and sound was working fine.

At some point I know I installed libpipewire-0.3-dev because of a dependency 
with something else. I am not sure if this means pipewire was installed or 
configured at that point... but sound was still working so I didn't notice any 
issue.

The upgrade of wireplumber to 0.4.12-1 is what made the issue visible as sound 
was no longer working after that.

Removing pulseaudio and completing the migration to pipewire fixed the issue.

Regards,

Francois

On Friday, November 18, 2022 at 10:59:01 AM EST, Dylan Aïssi 
 wrote: 

Hi Francois,

Le jeu. 13 oct. 2022 à 22:21, Francois Le Hir  a écrit :
>
> I was able to fix the issue on my side.
> The problem (for my situation) was a conflict between pulseaudio and pipewire 
> as both were running on my system at the same time and pipewire-pulse.service 
> was masked meaning the sound was not going through pipewire.

>

And I guess you did not manually mask pipewire-pulse.service before?

The pulseaudio.service probably started during the update of pipewire
instead of restarting the new pipewire-pulse.service.

I have both pulseaudio and pipewire-pulse installed but I have never seen this
issue. I wanted to avoid marking pipewire-pulse and pulseaudio in conflict
to allow users the possibility to switch but it looks like I will have to
do it anyway before the release of Bookworm.

Best,
Dylan

Bug#1024412: claws-mail: reproducible builds: Embeds timezone-dependent build date in manpages

Source: claws-mail
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps timezone
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build date is embedded in various manpages in a timezone-dependent
way:

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

  /usr/share/man/man7/claws-mail-acpi-notifier.7.gz

  .TH·CLAWS-MAIL-ACPI-NOTIFIER·7·"2022-10-31"·"4.1.1-1"·"Claws·Mail"
  vs.
  .TH·CLAWS-MAIL-ACPI-NOTIFIER·7·"2022-11-01"·"4.1.1-1"·"Claws·Mail"

The attached patch to debian/rules fixes this by setting ISO_DATE using
the UTC timezone.

According to my local tests, With this patch applied claws-mail should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining claws-mail!

live well,
  vagrant
From 13fb8991ce22369f131130f727584c8b02f9a6e1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Fri, 18 Nov 2022 21:24:22 +
Subject: [PATCH] debian/rules: Use UTC for manpage date.

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index d0b28572..e9f31342 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,7 @@ include /usr/share/dpkg/pkg-info.mk
 
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 TMP := $(CURDIR)/debian/tmp
-ISO_DATE := $(shell date +%Y-%m-%d -d @$(SOURCE_DATE_EPOCH))
+ISO_DATE := $(shell date +%Y-%m-%d -u -d @$(SOURCE_DATE_EPOCH))
 
 MANUAL =
 XDOCPKG =
-- 
2.38.1



signature.asc
Description: PGP signature

Bug#1020351: task-hungarian-desktop: transition gsfonts/gsfonts-x11 --> fonts-urw-base35

2022-11-18 Thread Holger Wansing

Control: tags -1 + pending


Hi,

fab...@debian.org wrote (Tue, 20 Sep 2022 18:18:25 +0200):
> Package: task-hungarian-desktop
> Severity: normal
> 
> Hi,
> 
> you are receiving this bug report, because your package declares a
> relationship with the gsfonts and/or gsfonts-x11 packages. Both
> packages have been replaced by fonts-urw-base35 since version
> 20200910-2 and are now merely transitional dummy packages. In order
> to make it possible to remove these transitional packages, please
> adjust the relationships for your package accordingly.
> 
> In the worst case, you will have to adjust some hard-coded font file
> paths since the font files have been renamed between the gsfonts and
> fonts-urw-base35 packages. Users of fontconfig to locate the font
> files will most probably not notice any difference.

Fixed in GIT.

Tagging this bug as pending


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1024411: RM: gkrellm-x86info -- RoQA; unmaintained, RC-buggy, dead upstream, replacement exists

Package: ftp.debian.org
Severity: normal

Please remove gkrellm-x86info. The last maintainer upload was in 2011, it's 
RC-buggy,
dead upstream and dropped from testing for almost a year. And 1002714 indicates 
a
replacement exists.

Bug#1024410: RM: dvbsnoop -- RoQA; unmaintained, RC-buggy, dead upstream

Package: ftp.debian.org
Severity: normal

Please remove dvbsnoop. The last maintainer upload was in 2013, it's RC-buggy,
dead upstream and dropped from testing for almost a year.

Bug#1024407: RM: scim-canna -- RoQA; unmaintained, RC-buggy, dead upstream

Package: ftp.debian.org
Severity: normal

Please remove scim-canna. The last maintainer upload was in 2010, it's RC-buggy,
dead upstream and dropped from testing for almost a year.

Bug#1024409: RM: vsdump -- RoQA; unmaintained, RC-buggy, dead upstream

Package: ftp.debian.org
Severity: normal

Please remove vsdump. The last maintainer upload was in 2010, it's RC-buggy,
dead upstream and dropped from testing for almost a year.

Bug#1024408: RM: ibam -- RoQA; unmaintained, RC-buggy, dead upstream

Package: ftp.debian.org
Severity: normal

Please remove ibam. The last maintainer upload was in 2011, it's RC-buggy,
dead upstream and dropped from testing for almost a year.

Bug#1024406: RM: cryptcat -- RoQA; unmaintained, RC-buggy, dead upstream

Package: ftp.debian.org
Severity: normal

Please remove cryptcat. The last maintainer upload was in 2008, it's RC-buggy,
dead upstream and dropped from testing for almost a year.

Bug#1024399: xrprof: reproducible-builds: build path embedded in /usr/bin/xrprof

On 2022-11-18, Dirk Eddelbuettel wrote:
> On 18 November 2022 at 11:49, Vagrant Cascadian wrote:
> | The build path is embedded in /usr/bin/xrprof:
> | 
> |   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/xrprof.html
> | 
> |   /build/1st/xrprof-0.3.1/src/xrprof.c:71
> |   vs.
> |   /build/2/xrprof-0.3.1/2nd/src/xrprof.c:71
> | 
> | The attached patch to debian/rules fixes this by passing the default
> | CFLAGS to dh_auto_build, which includes the -ffile-prefix-map argument.
>
> Nice!
>
> If it is that simple .. I will happily do so.  Thanks for the patch!

For clarity, I have only done build testing, not testing that the
installed program behaves correctly, but most of the default debian
flags *should* be fine... :)

If you want to be extra careful you might want to review the build logs
and check which flags are actually used with and without the patch.

Another option might be to patch the upstream Makefile(s) to use "CFLAGS
+=" instead of "CFLAGS =", though that still may change which flags are
actually used.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1024149: linux-image-amd64: 32-bit mmap() puts large files at non-random address

2022-11-18 Thread Jakub Wilk

I've bisected this; the first bad commit is 1854bc6e24204726 
("mm/readahead: Align file mappings for non-DAX").


--
Jakub Wilk

Bug#925591: grub-install fails on raid1+efi setup

2022-11-18 Thread Mark Nipper

Package: grub2-common
Version: 2.06-5
Followup-For: Bug #925591

It looks like the Ubuntu folks have added this as a template named
grub-efi/install_devices in their templates.in located in the source for
package:
---
https://packages.ubuntu.com/source/kinetic/grub2-unsigned

related to their bug of this same problem:
---
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868553

I assume it would be possible to incorporate the same fix easily enough
into the Debian version of this package to properly support this
scenario.

-- 
Mark Nipper

Bug#1024405: ifupdown: up command not run on alias interface

2022-11-18 Thread MK

Package: ifupdown
Version: 0.8.39+b1
Severity: minor


Dear Maintainer,


Editing /etc/network/interfaces


It appears that the 'up' command in an alias interface does not work correctly.
Moreover, since the 'up' command is run before the second alias interface is 
brought it, simply moving it does not help.

Fail1: brings up both the primary and alias IPs, but does NOT set up the route
Fail2: does not bring up the second alias interface at all.
Working: Brings up both IPs and the route.

This may just be a documentation issue (if you can't use aliases this way), but 
it appears to be a bug.
No journalctl messages are logged on the failures- just no route created.


=== START FAILING EXAMPLE 1 ===
allow-hotplug ens192
iface ens192 inet static
        address 123.123.123.146/24
        gateway 123.123.123.1


iface ens192 inet static
        address 10.200.2.201/16
        gateway 10.200.0.1
        up ip route add 10.201.0.0/16 dev $IFACE via 10.200.0.1
        down ip route del 10.201.0.0/16 dev $IFACE via 10.200.0.1 || true
=== END FAILING EXAMPLE 1 ===


=== START FAILING EXAMPLE 2 ===
allow-hotplug ens192
iface ens192 inet static
        address 123.123.123.146/24
        gateway 123.123.123.1
        up ip route add 10.201.0.0/16 dev $IFACE via 10.200.0.1
        down ip route del 10.201.0.0/16 dev $IFACE via 10.200.0.1 || true


iface ens192 inet static
        address 10.200.2.201/16
        gateway 10.200.0.1
=== END FAILING EXAMPLE 2 ===


=== START WORKING EXAMPLE ===
allow-hotplug ens192
iface ens192 inet static
        address 123.123.123.146/24
        gateway 123.123.123.1
        up ip addr add 10.200.2.201/16 dev $IFACE label $IFACE:0
        down ip addr del 10.200.2.201/16 dev $IFACE label $IFACE:0 || true
        up ip route add 10.201.0.0/16 dev $IFACE via 10.200.0.1
        down ip route del 10.201.0.0/16 dev $IFACE via 10.200.0.1 || true
=== END WORKING EXAMPLE ===


-- Package-specific info:
--- /etc/network/interfaces.d/*:
cat: '/etc/network/interfaces.d/*': No such file or directory


--- up and down scripts installed:
/etc/network/if-down.d:
total 4
-rwxr-xr-x 1 root root 759 Sep 27 09:09 resolved


/etc/network/if-post-down.d:
total 0


/etc/network/if-pre-up.d:
total 4
-rwxr-xr-x 1 root root 344 Jun 30  2016 ethtool


/etc/network/if-up.d:
total 12
-rwxr-xr-x 1 root root 1685 Jun 30  2016 ethtool
-rwxr-xr-x 1 root root 4663 Sep 27 09:09 resolved




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


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


Versions of packages ifupdown depends on:
ii  adduser   3.129
ii  iproute2  6.0.0-1+b1
ii  libc6     2.36-4


Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.4.3-P1-1


Versions of packages ifupdown suggests:
pn  ppp     
pn  rdnssd  


-- no debconf information

Bug#1024404: gitlint: reproducible-builds: python tracebacks in gitlint.1 man page

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

The output of a python traceback including the build path is embedded in
the gitlint.1 man page:

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

  /usr/share/man/man1/gitlint.1.gz

  
.TH·TRACEBACK·"1"·"December·2021"·"Traceback·(most·recent·call·last):"·"User·Commands"
  ...
  
File·"/build/1st/gitlint\-0.17.0/debian/gitlint/usr/bin/gitlint",·line·33,·in·
  vs.
  
File·"/build/2/gitlint\-0.17.0/2nd/debian/gitlint/usr/bin/gitlint",·line·33,·in·
  ...
  import·click
  ModuleNotFoundError:·No·module·named·'click'

Though embedding the build path revealed the problem, the real problem
is caused by missing dependencies...

The attached patch to debian/control fixes this by passing adding
several python3 packages to Build-Depends, as using help2man requires
the run-time dependencies at build-time.

According to my local tests, with this patch applied gitlint should
build reproducibly on tests.reproducible-builds.org as a side-effect of
fixing the real problem!

Thanks for maintaining gitlint!

live well,
  vagrant
From 00d8df53ff0425c801103417db027819541fa132 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Fri, 18 Nov 2022 20:19:38 +
Subject: [PATCH] debian/control: Add Build-Depends on python3-arrow,
 python3-click and python3-sh, which are used when generated the gitlint.1
 manpage.

---
 debian/control | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/control b/debian/control
index 80ce548..036ea43 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,10 @@ Build-Depends:
  git,
  help2man,
  python3-all,
+ python3-arrow,
+ python3-click,
  python3-setuptools,
+ python3-sh,
 Rules-Requires-Root: no
 Standards-Version: 4.6.0
 Homepage: https://jorisroovers.com/gitlint/
-- 
2.38.1



signature.asc
Description: PGP signature

Bug#1024399: xrprof: reproducible-builds: build path embedded in /usr/bin/xrprof

2022-11-18 Thread Dirk Eddelbuettel



Hi Vagrant,

On 18 November 2022 at 11:49, Vagrant Cascadian wrote:
| Source: xrprof
| Severity: normal
| Tags: patch
| User: reproducible-bui...@lists.alioth.debian.org
| Usertags: buildpath
| X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
| 
| The build path is embedded in /usr/bin/xrprof:
| 
|   
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/xrprof.html
| 
|   /build/1st/xrprof-0.3.1/src/xrprof.c:71
|   vs.
|   /build/2/xrprof-0.3.1/2nd/src/xrprof.c:71
| 
| The attached patch to debian/rules fixes this by passing the default
| CFLAGS to dh_auto_build, which includes the -ffile-prefix-map argument.

Nice!

If it is that simple .. I will happily do so.  Thanks for the patch!

| According to my local tests, with this patch applied xrprof should build
| reproducibly on tests.reproducible-builds.org!
| 
| Thanks for maintaining xrprof!

Thanks for looking reproducible builds! I have a few other packages that do
not comply but I am a little out of my depth. (I get patches for R builds and
some other things to not embed time/date etc.)

Best,  Dirk
 
| live well,
|   vagrant
| From dcf2ad058ef860eb7f9ac64a83149cbe267662e3 Mon Sep 17 00:00:00 2001
| From: Vagrant Cascadian 
| Date: Fri, 18 Nov 2022 19:44:54 +
| Subject: [PATCH] debian/rules: Pass default CFLAGS to dh_auto_build.
| 
| ---
|  debian/rules | 2 +-
|  1 file changed, 1 insertion(+), 1 deletion(-)
| 
| diff --git a/debian/rules b/debian/rules
| index 0da069d..c8bdedc 100755
| --- a/debian/rules
| +++ b/debian/rules
| @@ -4,7 +4,7 @@
|   dh $@
|  
|  override_dh_auto_build:
| - dh_auto_build -- prefix=/usr
| + dh_auto_build -- prefix=/usr CFLAGS="$(CFLAGS)"
|  
|  override_dh_auto_install:
|   dh_auto_install -- prefix=/usr
| -- 
| 2.38.1
| 
| x[DELETED ATTACHMENT signature.asc, application/pgp-signature]

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1024271: python-cffi: FTBFS on hppa - c/test_c.py test faults and drops core

2022-11-18 Thread John David Anglin


On 2022-11-18 4:00 a.m., stefa...@debian.org wrote:

Hi John (2022.11.17_23:22:15_+)

If the python-cffi test checks the passing of structs larger than 8
bytes, then maybe there is a problem:

 From a quick look at the test suite, there are a lot of tests that do
that.

I submitted a patch upstream to fix the libffi test failures on hppa and 
rebuilt libffi for hppa:
https://buildd.debian.org/status/fetch.php?pkg=libffi=hppa=3.4.4-1%2Bb1=1668799491=0

The testsuite is now clean.  Unfortunately, the python-cffi test still fails in 
the same way:

dave@mx3210:~/debian/python-cffi/python-cffi-1.15.1$ gdb -c core
GNU gdb (Debian 12.1-4) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "hppa-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
    .

For help, type "help".
Type "apropos word" to search for commands related to "word".
[New LWP 25666]
Core was generated by `python3.10 -m pytest c/ testing/'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0  0xf8d03f94 in ?? ()
(gdb) bt
#0  0xf8d03f94 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) disass 0xf8d03f94-8,0xf8d03f94+8
Dump of assembler code from 0xf8d03f8c to 0xf8d03f9c:
   0xf8d03f8c:  break 0,0
   0xf8d03f90:  depd,z,* r18,39,44,r22
=> 0xf8d03f94:  #f8d03f90
   0xf8d03f98:  depd,z,*= r18,35,52,r22
End of assembler dump.

Dave

--
John David Anglin  dave.ang...@bell.net

Bug#1024403: RFS: evilwm/1.4.2-1 -- minimalist window manager for X11

2022-11-18 Thread Mateusz Łukasik


Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : evilwm
   Version  : 1.4.2-1
   Upstream contact :https://www.6809.org.uk/ciaran/
 * URL  :https://www.6809.org.uk/evilwm/
 * License  : AEWM
 * Vcs  :https://github.com/mati75/evilwm.git
   Section  : x11

The source builds the following binary packages:

  evilwm - minimalist window manager for X11

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

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

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

  dget -xhttps://mentors.debian.net/debian/pool/main/e/evilwm/evilwm_1.4.2-1.dsc

Changes since the last upload:

 evilwm (1.4.2-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Update renamed lintian tag names in lintian overrides.
   * Set field Upstream-Contact in debian/copyright.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata (already
 present in machine-readable debian/copyright).
 .
   [ Mateusz Łukasik ]
   * New upstream release. (Closes: #1023516)

Regards,
--
  Mateusz Łukasik

Bug#1024402: RFS: jgmenu/4.4.1-1 -- Simple X11 menu

2022-11-18 Thread Mateusz Łukasik


Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : jgmenu
   Version  : 4.4.1-1
   Upstream contact : Johan Malm
 * URL  :https://jgmenu.github.io/
 * License  : Expat, LGPL-2+, GPL-2+, GPL-2, LGPL-3+
 * Vcs  :https://github.com/mati75/jgmenu
   Section  : x11

The source builds the following binary packages:

  jgmenu - Simple X11 menu
  jgmenu-xfce4-panel-applet - xfce4-panel applet for jgmenu

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

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

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

  dget -xhttps://mentors.debian.net/debian/pool/main/j/jgmenu/jgmenu_4.4.1-1.dsc

Changes since the last upload:

 jgmenu (4.4.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Bump Standards Version to 4.6.1.

Regards,
--
  Mateusz Łukasik

Bug#1006996: Bug #1006996: mate-polkit: On arm64 architecture mate-polkit tries to open an amd64 file and fails

2022-11-18 Thread Thomas Uhle


Control: affects -1 mate-polkit-bin
Control: tags -1 patch

Dear maintainers,

in addition to Christian Britz' report, the autostart desktop file should 
also be in mate-polkit because of the architecture triplet in the path to 
polkit-mate-authentication-agent-1, and the provided manpage has not yet 
been moved to mate-polkit-bin what causes a lintian issue.


I have prepared a patch that should fix all these packaging issues.

Best regards,

Thomas Uhle



On Thu, 10 Mar 2022, Christian Britz wrote:


Package: mate-polkit
Version: 1.24.0-2
Severity: important
X-Debbugs-Cc: cbr...@t-online.de

Dear Maintainer,

on arm64 architecture, mate-polkit tries to open an amd64 file and fails:

mate-polkit &
[1] 25011
cbritz@raspberrypi:~$ /usr/bin/mate-polkit: 3: 
/usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-agent-1: not 
found

This renders the package unusable on arm64.

Regards,
Christian

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

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

Versions of packages mate-polkit depends on:
ii  accountsservice0.6.55-3
ii  libc6  2.31-13+deb11u2
ii  libgdk-pixbuf2.0-0 2.40.2-2
ii  libglib2.0-0   2.66.8-1
ii  libgtk-3-0 3.24.24-4
ii  libpolkit-agent-1-00.105-31+deb11u1
ii  libpolkit-gobject-1-0  0.105-31+deb11u1
ii  mate-polkit-common 1.24.0-2
ii  policykit-10.105-31+deb11u1

mate-polkit recommends no packages.

mate-polkit suggests no packages.
diff --git a/debian/control b/debian/control
index e1ccb8c..990d5cc 100644
--- a/debian/control
+++ b/debian/control
@@ -23,10 +23,10 @@
 Vcs-Git: https://salsa.debian.org/debian-mate-team/mate-polkit.git
 
 Package: mate-polkit-bin
-Architecture: all
-Depends: mate-polkit (>= ${source:Version}),
+Architecture: any
+Depends: mate-polkit (= ${binary:Version}),
  ${misc:Depends},
-Breaks: mate-polkit (<< 1.12.0-3~),
+ ${shlibs:Depends},
 Description: MATE authentication agent for PolicyKit-1 (executable wrapper script)
  The mate-polkit package provides a D-Bus session bus service that is used to
  bring up authentication dialogs used for obtaining privileges.
@@ -40,9 +40,8 @@
 
 Package: mate-polkit
 Architecture: any
-Multi-Arch: same
 Depends: accountsservice,
- mate-polkit-common (= ${binary:Version}),
+ mate-polkit-common (>= ${source:Version}),
  policykit-1,
  ${misc:Depends},
  ${shlibs:Depends},
@@ -54,10 +53,9 @@
  This package contains the MATE policy kit authentication agent.
 
 Package: mate-polkit-common
-Architecture: any
+Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends},
- ${shlibs:Depends},
 Breaks: mate-polkit (<< 1.8.0),
 Description: MATE authentication agent for PolicyKit-1 (common files)
  The mate-polkit package provides a D-Bus session bus service that is used to
diff --git a/debian/mate-polkit.install b/debian/mate-polkit.install
index b0bfa1a..3d97aa9 100644
--- a/debian/mate-polkit.install
+++ b/debian/mate-polkit.install
@@ -1 +1,2 @@
+etc/
 usr/lib/*/polkit-mate/
diff --git a/debian/mate-polkit-common.install b/debian/mate-polkit-common.install
index 7034e54..2568e1f 100644
--- a/debian/mate-polkit-common.install
+++ b/debian/mate-polkit-common.install
@@ -1,2 +1 @@
-etc/
 usr/share/locale/
diff --git a/debian/mate-polkit.manpages b/debian/mate-polkit.manpages
deleted file mode 100644
index 43f8a64..000
--- a/debian/mate-polkit.manpages
+++ /dev/null
@@ -1 +0,0 @@
-debian/man/mate-polkit.1
diff --git a/debian/mate-polkit-bin.manpages b/debian/mate-polkit-bin.manpages
new file mode 100644
index 000..43f8a64
--- /dev/null
+++ b/debian/mate-polkit-bin.manpages
@@ -0,0 +1 @@
+debian/man/mate-polkit.1

Bug#1024401: emacs-gtk (28.2) fails to start on sway/xwayland: cannot open display: :0

2022-11-18 Thread Erich Wälde

Package: emacs-gtk
Version: 1:28.2+1-6
Severity: normal

Dear Maintainer,

thank you very much for packaging emacs 28 for Debian!


   * What led up to the situation?

Installing emacs-gtk from unstable on a system using sway/xwayland.

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

start emacs from foot/bash prompt.

   * What was the outcome of this action?
(emacs:6069): Gtk-WARNING **: 20:54:52.756: cannot open display: :0

   * What outcome did you expect instead?
emacs starting and drawing a window.

Further information:

At the end of an strace I find this:

socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_UNIX, sun_path="/run/user/1000/:0"}, 20) = -1 ENOENT 
(No such file or directory)
close(4)= 0
getpeername(2, 0x7ffdb0480040, [128])   = -1 ENOTSOCK (Socket operation on 
non-socket)
futex(0x7f89ca48dfe8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {B38400 opost isig icanon echo ...}) = 0
getpid()= 3004
newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=2298, 
...}, 0) = 0
write(2, "\n(emacs:3004): Gtk-\33[1;33mWARNIN"..., 89) = 89
close(1)= 0
close(2)= 0
exit_group(1)   = ?

I can confirm that /run/user/1000/:0 does not exist.

emacs -nw does work and runs in said foot terminal
an older 28.1.50 version built from sources does work fine!

ii  sway   1.7-6amd64i3-compatible Wayland compositor
ii  xwayland   2:22.1.5-1   amd64X server for running X clients 
under Wayland




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

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

Versions of packages emacs-gtk depends on:
ii  emacs-bin-common 1:28.2+1-6
ii  emacs-common 1:28.2+1-6
ii  libacl1  2.3.1-1
ii  libasound2   1.2.7.2-1
ii  libc62.36-5
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.4-1
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgccjit0   12.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgif7  5.2.1-2.5
ii  libglib2.0-0 2.74.1-2
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libgnutls30  3.7.8-4
ii  libgpm2  1.20.7-10+b1
ii  libgtk-3-0   3.24.34-4
ii  libharfbuzz0b5.2.0-2+b1
ii  libice6  2:1.0.10-1
ii  libjansson4  2.14-2
ii  libjpeg62-turbo  1:2.1.2-1+b1
ii  liblcms2-2   2.13.1-1+b1
ii  libm17n-01.8.0-4
ii  libotf1  0.9.16-3+b1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpng16-16  1.6.38-2
ii  librsvg2-2   2.54.5+dfsg-1
ii  libselinux1  3.4-1+b3
ii  libsm6   2:1.2.3-1
ii  libsystemd0  252.1-1
ii  libtiff5 4.4.0-5+b1
ii  libtinfo66.3+20220423-2
ii  libx11-6 2:1.8.1-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxml2  2.9.14+dfsg-1.1+b2
ii  libxrender1  1:0.9.10-1.1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages emacs-gtk recommends:
pn  fonts-noto-color-emoji  

Versions of packages emacs-gtk suggests:
ii  emacs-common-non-dfsg  1:28.2+1-2

-- no debconf information

Bug#1024396: brewtarget: reproducible builds: Embeds kernel version in /usr/bin/brewtarget

Control: retitle 1024396 brewtarget: reproducible builds: Embeds kernel version 
in /usr/bin/brewtarget

On 2022-11-18, Vagrant Cascadian wrote:
> The build date is embedded in /usr/bin/brewtarget:

I *meant* to say kernel version! Sorry for the confusion

>   
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/brewtarget.html
>
>   Linux-5.10.0-19-amd64
>   vs.
>   Linux-5.19.0-0.deb11.2-amd64

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1012636: isync: license conflict with libsasl2

2022-11-18 Thread Pierre-Elliott Bécue

Hi Oswald,

Bastian Germann  wrote on 12/11/2022 at 16:46:44+0100:

> I see that in git there is now LicenseRef-isync-GPL-exception applied to 
> mbsync.

Would you agree to release isync 1.4.5 or do I need to import your
license exception?

Cheers!
-- 
PEB


signature.asc
Description: PGP signature

Bug#1024400: net-luminis-build-plugin: broken maintainer field

2022-11-18 Thread Adam D. Barratt

Source: net-luminis-build-plugin
Version: 0.2.0-4
Severity: serious
X-Debbugs-Cc: ta...@debian.org

Hi,

The upload of net-luminis-build-plugin which orphaned it appears to
have generated a broken Maintainer field:


Package: net-luminis-build-plugin
Binary: libnet-luminis-build-plugin-java
Version: 0.2.0-4
Maintainer: Debian QA Group 
 Mathieu Malaterre 


I'm assuming the second line is a failed attempt at removing the
Uploaders field, as mentioned in the changelog, which originally read:

Uploaders:  Mathieu Malaterre 

Amongst other things, this breaks the scripts in the BTS which generate
lists of RC bugs in unstable and testing for britney, meaning that
those lists have not been updated since Monday morning.

Regards,

Adam

Bug#1024399: xrprof: reproducible-builds: build path embedded in /usr/bin/xrprof

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

The build path is embedded in /usr/bin/xrprof:

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

  /build/1st/xrprof-0.3.1/src/xrprof.c:71
  vs.
  /build/2/xrprof-0.3.1/2nd/src/xrprof.c:71

The attached patch to debian/rules fixes this by passing the default
CFLAGS to dh_auto_build, which includes the -ffile-prefix-map argument.

According to my local tests, with this patch applied xrprof should build
reproducibly on tests.reproducible-builds.org!

Thanks for maintaining xrprof!

live well,
  vagrant
From dcf2ad058ef860eb7f9ac64a83149cbe267662e3 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Fri, 18 Nov 2022 19:44:54 +
Subject: [PATCH] debian/rules: Pass default CFLAGS to dh_auto_build.

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 0da069d..c8bdedc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,7 @@
 	dh $@
 
 override_dh_auto_build:
-	dh_auto_build -- prefix=/usr
+	dh_auto_build -- prefix=/usr CFLAGS="$(CFLAGS)"
 
 override_dh_auto_install:
 	dh_auto_install -- prefix=/usr
-- 
2.38.1



signature.asc
Description: PGP signature

Bug#1024398: lintian-brush: suggests removing moving udebs to oldlibs

2022-11-18 Thread Simon McVittie

Package: lintian-brush
Version: 0.136
Severity: normal

To reproduce: clone source package gdk-pixbuf, reset to
debian/2.42.9+dfsg-1 and run lintian-brush.

Expected result: libgdk-pixbuf2.0-0-udeb remains in
Section: debian-installer and is not moved to Section: oldlibs.

Actual result: lintian-brush suggests moving it to oldlibs,
which causes a Lintian warning:

> W: libgdk-pixbuf2.0-0-udeb udeb: wrong-section-for-udeb oldlibs
> N:
> N:   udeb packages should have "Section: debian-installer".
> ...

I think Lintian is correct here: I would interpret "udebs should be in
Section: debian-installer" as a higher-precedence rule than "transitional
packages should be in Section: oldlibs".

smcv

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

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

Versions of packages lintian-brush depends on:
ii  devscripts   2.22.2
ii  python3  3.10.6-3
ii  python3-asyncpg  0.27.0-1+b1
ii  python3-breezy   3.3.0+bzr7661-4+b1
ii  python3-debian   0.1.48
ii  python3-debmutate0.62
ii  python3-distro-info  1.2
ii  python3-dulwich  0.20.50-1+b1
ii  python3-iniparse 0.5-1
ii  python3-iso8601  1.0.2-1
ii  python3-levenshtein  0.12.2-2+b3
ii  python3-pyinotify0.9.6-2
ii  python3-ruamel.yaml  0.17.16-1
ii  python3-semver   2.10.2-3
ii  python3-tomlkit  0.11.6-1
ii  python3-tqdm 4.64.0-2
ii  python3-upstream-ontologist  0.1.30-1

Versions of packages lintian-brush recommends:
ii  debhelper 13.10.1
ii  decopy0.2.4.7-0.2
ii  dos2unix  7.4.3-1
ii  gpg   2.2.40-1
ii  lintian   2.115.3
ii  ognibuild 0.0.13-1
ii  python3-bs4   4.11.1-2
ii  python3-docutils  0.17.1+dfsg-2
ii  python3-lxml  4.9.1-1+b2
ii  python3-markdown  3.4.1-2

Versions of packages lintian-brush suggests:
pn  brz-debian 
ii  git-buildpackage   0.9.29
ii  gnome-pkg-tools0.22.7
ii  po-debconf 1.0.21+nmu1
pn  postgresql-common  

-- no debconf information

Bug#1024397: debian-cd: Please remove references to transitional packages in tasks

2022-11-18 Thread Simon McVittie

Package: debian-cd
Severity: normal

libgdk-pixbuf2.0-0-udeb (historical package name) has been superseded by
libgdk-pixbuf-2.0-0-udeb (Policy-compliant name + "-udeb") since bullseye
and I'd like to remove the old name, but according to codesearch,
tasks/*/Debian-edu-full in debian-cd seems to still have references to it.
Is it safe to remove the transitional udeb anyway?

I also notice that libgdk-pixbuf2.0-0, another transitional package, is
also listed in that file. Does that inclusion block removal of
the transitional libgdk-pixbuf2.0-0?

It would probably be good to replace transitional packages in the various
package lists with their dependencies at some point.

smcv

Bug#305722: xfsdump reports ERROR: does not identify a file system

2022-11-18 Thread Christoph Biedl

Michael Lueck wrote...

> xfsdump: ERROR: /srv/shares/pdoxdata/ does not identify a file system

Came across that problem as well today. From a little probing - I did
not check the sources, though - it seems xfsdump is pretty pedantic
about that path. I guess it must exactly match the specification as read
from /etc/mtab, in other words: xfsdump will fail if the path given on
the command line ...

* is relative,
* is different when running from within a chroot,
* ends with a trailing slash..

It would be nice if xfsdump could be a little more flexible here.

Christoph


signature.asc
Description: PGP signature

Bug#1024160:

2022-11-18 Thread evereve

Can confirm the issue on Debian Testing. Downgrading to version 3.36.0-1 (from 
Stable) solves the problem.

Bug#1013876: Please close this bug report for keepassxc-browser to migrate to testing

2022-11-18 Thread Bruno Kleinert

Am Donnerstag, dem 17.11.2022 um 13:52 + schrieb Amr Ibrahim:
> On Sat, 24 Sep 2022 21:37:45 +0200 Guillem Jover  wrote:
> 
> > I've kept the package on hold since, but try to upgrade from time to
> > time to see whether its fixed. Last time I did with the latest version
> > currently in sid, it seemed to be still broken.
> 
> Is this still broken in Chromium?

Yes it is, I just confirmed.

> There is no problem in Firefox, and this bug report is preventing the package 
> to migrate to testing

I do not have time to investigate and fix the issue in the mid-term.
I'd appreciate if someone could jump in and provide a patch against the
package, I'd be glad to merge and upload!

From a past attempt to track it down, I *think* to remember there was
an issue with a variable 'browser' expected by Chromium not being
defined.

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

Bug#1020258: elpa-*: fails to install: libgccjit.so: error: error invoking gcc driver

2022-11-18 Thread Sean Whitton

control: reopen -1
control: notfixed -1 1:28.2+1-5

Hello,

On Fri 18 Nov 2022 at 11:44AM -07, Sean Whitton wrote:

>> elpa-treemacs-magit=2.8-2
>> elpa-use-package-chords=2.4.1-1
>> elpa-weechat=0.5.0-5
>>
>> I cannot reproduce this in testing (which still has emacs 1.27),
>> so this seems to stem from emacs 1.28 (and not gcc 12).
>
> I can't reproduce this locally, and looking at the package tracker for a
> few of those packages you've listed, piuparts is now passing if it's
> been re-run recently.  So I believe this one is fixed.

... except that it's still showing up in failing autopkgtests, e.g. for
emacs-deferred.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1024389: python3-ledger: sefault during garbage collection

2022-11-18 Thread David Bremner

Marcin Owsiany  writes:

> Package: python3-ledger
> Version: 3.2.1-8+b5
> Severity: normal
>
> Dear Maintainer,
>
> Here is a short repro script, that generates a segmentation violation on
> completion. I include a backtrace from GDB, but unfortunately I could not find
> debugging symbols for the ledger extension nor libboost-python.
>

Did you try python3-ledger-dbgsym? You need to enable the debian-debug
archive [1]

[1]: https://wiki.debian.org/HowToGetABacktrace

Bug#1024396: brewtarget: reproducible builds: Embeds build date in /usr/bin/brewtarget

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

The build date is embedded in /usr/bin/brewtarget:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/brewtarget.html

  Linux-5.10.0-19-amd64
  vs.
  Linux-5.19.0-0.deb11.2-amd64

The attached patch to src/main.cpp fixes this by removing
CMAKE_HOST_SYSTEM and CMAKE_SYSTEM, which includes the kernel version.

According to my local tests, With this patch applied brewtarget should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining brewtarget!

live well,
  vagrant
From b3b4f7b8bc2b3f08f32a1d3ead764468c0bdf23a Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Fri, 18 Nov 2022 18:35:14 +
Subject: [PATCH] src/main.cpp: do not embed the value of CMAKE_HOST_SYSTEM or
 CMAKE_SYSTEM.

This embeds the version of the running kernel, breaking reproducible
builds.

https://tests.reproducible-builds.org/debian/issues/unstable/captures_kernel_version_via_CMAKE_SYSTEM_issue.html
---
 src/main.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main.cpp b/src/main.cpp
index 227d530..2cc767f 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -195,7 +195,7 @@ int main(int argc, char **argv) {
  "Starting" << CONFIG_APPLICATION_NAME_UC << "v" << CONFIG_VERSION_STRING << " (app name" <<
  app.applicationName() << ") on " << QSysInfo::prettyProductName();
   qInfo() <<
- "Built at" << BUILD_TIMESTAMP << "on" << CMAKE_HOST_SYSTEM << "for" << CMAKE_SYSTEM << "with" <<
+ "Built at" << BUILD_TIMESTAMP <<
  CMAKE_CXX_COMPILER_ID << "compiler";
   qInfo() << "Log directory:" << Logging::getDirectory().absolutePath();
   qInfo() << "Using Qt runtime v" << qVersion() << " (compiled against Qt v" << QT_VERSION_STR << ")";
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#982145: [PATCH] add missing copyright for nanosvg, fix wlr license name

I have looked around to find what that "MIT-like" license is and the
closest match I could find is the HPND-sell-variant license, as per:

https://spdx.org/licenses/HPND-sell-variant.html

The non-sell variant is approved by the OSI board:

https://opensource.org/licenses/HPND

... and it looks like a free license to me. Using the right SPDX token
here might make the FTP-master's job easier.

I also reorder the Files: blocks so that the debian/ one is at the
end, as idiomatic.
---
 debian/copyright | 33 -
 1 file changed, 28 insertions(+), 5 deletions(-)

diff --git a/debian/copyright b/debian/copyright
index b718e85..78f2102 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -7,14 +7,19 @@ Files: *
 Copyright: 2019 Daniel Eklöf 
 License: Expat
 
+Files: 3rd-party/nanosvg/*
+Copyright: 2002-2004, Maxim Shemanarev (McSeem) (http://www.antigrain.com/)
+   2013-2014, Mikko Mononen 
+License: Zlib
+
+Files: external/wlr-layer-sghell-unstable-v1.xml
+Copyright: 2017 Drew DeVault 
+License: HPND-sell-variant
+
 Files: debian/*
 Copyright: 2021 Peter Colberg 
 License: Expat
 
-Files: external/wlr-layer-shell-unstable-v1.xml
-Copyright: 2017 Drew DeVault 
-License: MIT-like
-
 License: Expat
  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
@@ -34,7 +39,7 @@ License: Expat
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  SOFTWARE.
 
-License: MIT-like
+License: HPND-sell-variant
  Permission to use, copy, modify, distribute, and sell this software and its
  documentation for any purpose is hereby granted without fee, provided that the
  above copyright notice appear in all copies and that both that copyright 
notice
@@ -52,3 +57,21 @@ License: MIT-like
  DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER 
TORTIOUS
  ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
  SOFTWARE.
+
+License: Zlib
+ This software is provided 'as-is', without any express or implied
+ warranty.  In no event will the authors be held liable for any damages
+ arising from the use of this software.
+ .
+ Permission is granted to anyone to use this software for any purpose,
+ including commercial applications, and to alter it and redistribute it
+ freely, subject to the following restrictions:
+ .
+ 1. The origin of this software must not be misrepresented; you must not
+ claim that you wrote the original software. If you use this software
+ in a product, an acknowledgment in the product documentation would be
+ appreciated but is not required.
+ 2. Altered source versions must be plainly marked as such, and must not be
+ misrepresented as being the original software.
+ 3. This notice may not be removed or altered from any source distribution.
+
-- 
2.35.1

Bug#1024000: pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs' exited 1

2022-11-18 Thread Steve Langasek

IMHO this should be considered a bug in imath, which has taken over
libilmbase-dev with a Provides: (and ilmbase has been removed from the
archive), but does not provide all the interfaces necessary to actually be
compatible.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1024395: If I try to enroll the same key again : no chnage.


So apparently the keys is still there but mokutil does not see it.

Strange!

-- eric

Bug#1024395: grub-efi-amd64-signed: after upgrade to 1+2.06+5 I get errors when booting (although I manage to boot)

Package: grub-efi-amd64-bin
Version: 1+2.06+5
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

After upgrade to 2.06-5, I get an error message "prohibited by secure boot 
policy" and it boot
with a strange look with \xe7caracaters instead of lines.

I build my own kernel and enrolled my owns keys, sign the linux kernel binarry 
and the mdoules with the keys.
Everythong was working fine with 2.06-3.

I also noticed that my enrolled keys is no more listed via "mokutil 
--list-enrolled". Although no key were cleared.


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

Kernel: Linux 5.10.155 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages grub-efi-amd64-signed depends on:
ii  grub-common  2.06-5

Versions of packages grub-efi-amd64-signed recommends:
ii  shim-signed  1.38+15.4-7

grub-efi-amd64-signed suggests no packages.

Versions of packages grub-efi-amd64-bin depends on:
ii  grub-common  2.06-5

Versions of packages grub-efi-amd64-bin recommends:
ii  efibootmgr  17-1

-- no debconf information

Bug#1024394: tftpd-hpa: If ipv6 is disabled system-wide, tftpd-hpa will not start unless --ipv4 is specified

2022-11-18 Thread elyograg

Package: tftpd-hpa
Version: 5.2+20150808-1.2build2
Severity: normal

Dear Maintainer,

I disabled ipv6 on the whole system with a kernel parameter on boot.
This is something I routinely do on any server I manage, because in the
past I have had weird problems that disabling ipv6 solved.  I am not
using ipv6 at all. Disabling it means I do not usually have to worry
about any complications it might introduce.

I didn't notice for several weeks after disabling ipv6 that my tftp
server wasn't working.  When I did, I tracked down the problem to a log
entry saying that tftpd-hpa couldn't bind to ipv6.  Instead of starting 
with ipv4, it simply refused to run.  Adding --ipv4 to the options in
/etc/default/tfdpd-hpa got it working again.

I think the program should have started, logging the ipv6 error.

I initially filed this report with Ubuntu because I am using Ubuntu.
They indicated I should file the bug upstream.

https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1996846

-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-1007-oem (SMP w/48 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tftpd-hpa depends on:
ii  adduser3.118ubuntu5
ii  debconf [debconf-2.0]  1.5.79ubuntu1
ii  libc6  2.35-0ubuntu3.1
ii  libwrap0   7.6.q-31build2

tftpd-hpa recommends no packages.

Versions of packages tftpd-hpa suggests:
pn  pxelinux  

-- debconf information:
  tftpd-hpa/username: tftp
  tftpd-hpa/directory: /var/lib/tftpboot
  tftpd-hpa/address: :69
  tftpd-hpa/options: --secure --ipv4 --create --permissive --umask 027

Bug#1024393: RM: pyparsing2 -- ROM (team); no rdeps; newer version in Debian

2022-11-18 Thread Bastian Germann


Package: ftp.debian.org

pyparsing2 should be removed in favour of pyparsing (version 3).
It does not have any reverse dependencies.

Bug#1023624: RM: pytoml -- ROM; obsoleted by upstream; alternatives exist

2022-11-18 Thread Bastian Germann


Control: severity -1 serious

Raising the severity to keep this out of testing.
The package is not in violation of the Policy but I think it would be bad to 
have it in bookworm.
Please lower the severity again if you want to keep it.

Bug#982145: RFS: fuzzel/1.5.1-1 [ITP] -- Application launcher for wlroots based Wayland compositors

On 2022-11-12 18:17:23, Peter Colberg wrote:
> Dear Debian mentors,
>
> I have updated the fuzzel package to version 1.8.2-1 [1]. I will
> push a signed tag once the package has been accepted into unstable.

Hi!

So a quick review of the package...

It looks like it ships a third-party library, nanosvg. I don't know if
that's already packaged in Debian, but it might make the FTP-masters
unhappy, especially since it's not mentioned in debian/copyright. So the
latter should be fixed, at the very least, and we might consider
packaging that library separately...

... that said, it looks like many other packages do ship a copy of that
library, maybe it's the way it's designed to be shipped?

https://codesearch.debian.net/search?q=nanosvg=1

wxwidgets just vendors it, but does mention it in the debian/copyright,
however:

https://sources.debian.org/src/wxwidgets3.2/3.2.1%2Bdfsg-1/debian/copyright/#L28

So there's that: at least add that to the debian/copyright.

Also, I've had trouble reproducing the upstream tarball. I tried to
build the package with git-buildpackage:

gbp buildpackage --git-debian-branch=main --git-upstream-tag=1.8.2

... but that gives me a different tarball than
upstream. git-buildpackage generates a tarball with foot-1.8.2/ as a
top directory, while upstream has foot/. I'm not sure how to resolve
this, but you should at least provide the upstream tarball ... somewhere
so that it can be uploaded safely.

You might want to configure git-buildpackage or some other git-building
tool in the package as well, since it seems that (git) is what you rely
on to build this.

I can probably just live with the upstream tarball for now, but that
might be something you want to consider documenting in
debian/README.source or something.

Otherwise this is almost ready to go, as far as I'm concerned, and I'll
be happy to sponsor this once it has a proper debian/copyright. Try
running decopy on the source to see what comes up...

a.
-- 
There is no cloud, it's just someone else's computer.
   - Chris Watterson

signature.asc
Description: PGP signature

Bug#1024388: libtepl-6-1: missing (unversioned) Breaks+Replaces: libtepl-6-0

2022-11-18 Thread Jeremy Bicha

Control: severity -1 important

On Fri, Nov 18, 2022 at 12:51 PM Andreas Beckmann  wrote:
> Package: libtepl-6-1
> Version: 6.2.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>
> From the attached log (scroll to the bottom...):
>
>   Preparing to unpack .../libtepl-6-1_6.2.0-2_amd64.deb ...
>   Unpacking libtepl-6-1:amd64 (6.2.0-2) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb (--unpack):
>trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/tepl-6.mo', which is 
> also in package libtepl-6-0:amd64 6.1.2-1+b2
>   Errors were encountered while processing:
>/var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb
>
>
> The *.mo files have the same name in both packages.

I am downgrading the severity because nothing in Debian used libtepl-6-0

Nevertheless, we still ought to split the translations to a separate
binary package so we didn't run into this issue again later.

Thanks,
Jeremy Bicha

Bug#1024391: gtk4: FTBFS on big-endian: some dependency made border-image-excess-size reftest regress

2022-11-18 Thread Simon McVittie

Source: gtk4
Version: 4.8.2+ds-1
Severity: serious
Tags: ftbfs help
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-s...@lists.debian.org, debian-powe...@lists.debian.org
Control: clone -1 -2
Control: retitle -2 gtk+3.0: FTBFS on big-endian: some dependency made
border-image-excess-size reftest regress
Control: reassign -2 src:gtk+3.0 3.24.34-3

gtk4 4.8.2+ds-2 failed to build from source on s390x and ppc64. This is
*not* a regression caused by the changes in 4.8.2+ds-2: I built 4.8.2+ds-1
on the s390x porterbox zelenka, and it failed in the same way in either
bookworm or sid.

gtk+3.0 3.24.34-3 has the equivalent issue, originally seen in 3.24.34-4.
I suspect this is not a GTK bug, but was instead caused by some library
that GTK depends on and that has changed since 2022-10-29.

Unfortunately, a lot of dependencies have changed in that time,
porterboxes can't run debbisect with an unprivileged container because
/proc/sys/kernel/unprivileged_userns_clone is disabled, and I don't
have root on a big-endian machine to be able to bisect this. Possible
candidates include mesa, pixman and tiff.

To reproduce: build gtk+3.0 or gtk4 from source. For a quicker re-test,
after compiling GTK once, you can run this (in gtk4):

dbus-run-session -- debian/tests/run-with-display x11 meson test -C
debian/build/deb --setup=x11 --print-errorlogs "reftest
border-image-excess-size.ui"

or this (in gtk+3.0):

dbus-run-session -- xvfb-run -a
debian/build/deb/testsuite/reftests/gtk-reftest -o
debian/build/deb/testsuite/reftests/output -d
debian/build/deb/testsuite/reftests
testsuite/reftests/border-image-excess-size.ui

Expected result: tests pass

Actual result: the "border-image-excess-size" test fails. Images are
written to
debian/build/deb/testsuite/reftests/output/x11/border-image-excess-size.{ref,out,diff}.png
(in gtk4) or to
debian/build/deb/testsuite/reftests/output/border-image-excess-size.{ref,out,diff}.png
(in gtk+3.0).

The .ref.png file is the result of rendering a simpler scene that should
produce the same pixels as the test.

The .out.png file is the result of rendering the actual feature under test.

In this case, the expected rendering is a 10x10 pixel square with green
corners and black everywhere else, and the actual rendering is a 10x10
pixel square with magenta corners and black everywhere else. This makes me
suspect that colour channels might be in the wrong order or something.

I'll ignore this test failure for now and downgrade these bugs to non-RC.

smcv

Bug#1024048: pyliblo: diff for NMU version 0.10.0-5.1

2022-11-18 Thread Stefano Rivera

Control: tags 1024048 + patch
Control: tags 1024048 + pending

Dear maintainer,

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

Regards.

SR
diff -Nru pyliblo-0.10.0/debian/changelog pyliblo-0.10.0/debian/changelog
--- pyliblo-0.10.0/debian/changelog	2021-11-21 17:07:07.0 +0200
+++ pyliblo-0.10.0/debian/changelog	2022-11-18 20:04:17.0 +0200
@@ -1,3 +1,10 @@
+pyliblo (0.10.0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.11 support (Closes: #1024048)
+
+ -- Stefano Rivera   Fri, 18 Nov 2022 20:04:17 +0200
+
 pyliblo (0.10.0-5) unstable; urgency=medium
 
   * Team upload
diff -Nru pyliblo-0.10.0/debian/patches/python3.11.patch pyliblo-0.10.0/debian/patches/python3.11.patch
--- pyliblo-0.10.0/debian/patches/python3.11.patch	1970-01-01 02:00:00.0 +0200
+++ pyliblo-0.10.0/debian/patches/python3.11.patch	2022-11-18 20:03:57.0 +0200
@@ -0,0 +1,164 @@
+Merge branch 'callable-callback'
+
+Includes migrating to inspect.getfullargspec() in Python 3.
+
+Origin: https://github.com/dsacre/pyliblo/commit/33999ca8178a01c720e99856df769f1986c7e912
+--- a/src/liblo.pyx
 b/src/liblo.pyx
+@@ -23,6 +23,7 @@
+ from liblo cimport *
+ 
+ import inspect as _inspect
++import functools as _functools
+ import weakref as _weakref
+ 
+ 
+@@ -249,7 +250,6 @@
+ free(url)
+ 
+ cb = cb_data
+-func = cb.func.func
+ 
+ func_args = (_decode(path),
+  args,
+@@ -257,20 +257,42 @@
+  src,
+  cb.user_data)
+ 
+-# call function
+-if _inspect.getargspec(func)[1] == None:
+-# determine number of arguments to call the function with
+-n = len(_inspect.getargspec(func)[0])
+-if _inspect.ismethod(func):
+-n -= 1  # self doesn't count
+-r = cb.func(*func_args[0:n])
+-else:
+-# function has argument list, pass all arguments
+-r = cb.func(*func_args)
++# call the function
++r = cb.func(*func_args[:cb.nargs])
+ 
+ return r if r != None else 0
+ 
+ 
++cdef int _callback_num_args(func):
++"""
++Return the number of arguments that should be passed to callback *func*.
++"""
++getargspec = (_inspect.getargspec if PY_VERSION_HEX < 0x0300
++ else _inspect.getfullargspec)
++
++if isinstance(func, _functools.partial):
++# before Python 3.4, getargspec() did't work for functools.partial,
++# so it needs to be handled separately
++argspec = getargspec(func.func)
++nargs = len(argspec.args) - len(func.args)
++if func.keywords is not None:
++nargs -= len(func.keywords)
++else:
++if (hasattr(func, '__call__') and
++not (_inspect.ismethod(func) or _inspect.isfunction(func))):
++func = func.__call__
++
++argspec = getargspec(func)
++nargs = len(argspec.args)
++
++if _inspect.ismethod(func):
++nargs -= 1  # self doesn't count
++
++# use all 5 arguments (path, args, types, src, user_data) if the
++# function has a variable argument list
++return nargs if argspec.varargs is None else 5
++
++
+ cdef int _bundle_start_callback(lo_timetag t, void *cb_data) with gil:
+ cb = cb_data
+ r = cb.start_func(_timetag_to_double(t), cb.user_data)
+@@ -446,11 +468,16 @@
+ 
+ self._check()
+ 
++# determine the number of arguments to call the function with
++nargs = _callback_num_args(func)
++
+ # use a weak reference if func is a method, to avoid circular
+ # references in cases where func is a method of an object that also
+ # has a reference to the server (e.g. when deriving from the Server
+ # class)
+-cb = struct(func=_weakref_method(func), user_data=user_data)
++cb = struct(func=_weakref_method(func),
++user_data=user_data,
++nargs=nargs)
+ # keep a reference to the callback data around
+ self._keep_refs.append(cb)
+ 
+--- a/test/test_liblo.py
 b/test/test_liblo.py
+@@ -15,6 +15,7 @@
+ import re
+ import time
+ import sys
++import functools
+ import liblo
+ 
+ 
+@@ -24,7 +25,7 @@
+ 
+ 
+ class Arguments:
+-def __init__(self, path, args, types, src, data):
++def __init__(self, path, args, types=None, src=None, data=None):
+ self.path = path
+ self.args = args
+ self.types = types
+@@ -178,6 +179,50 @@
+ with self.assertRaises(RuntimeError):
+ self.server.recv()
+ 
++def testCallbackVarargs(self):
++def foo(path, args, *varargs):
++self.cb = Arguments(path, args)
++self.cb_varargs = varargs
++self.server.add_method('/foo', 'f', foo, user_data='spam')
++self.server.send(1234, '/foo', 123.456)
++self.assertTrue(self.server.recv())
++

Bug#1024379: ITP: libnginx-mod-http-upstream-fair -- Nginx module libnginx-mod-http-upstream-fair

Le ven. 18 nov. 2022 à 15:39, Jan Mojzis  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jan Mojzis 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: libnginx-mod-http-upstream-fair
>   Version : git20120408
>   Upstream Author : Grzegorz Nosek
> * URL : https://github.com/gnosek/nginx-upstream-fair
> * License : BSD
>   Programming Lang: C
>   Description : libnginx-mod-http-upstream-fair module for Nginx
>
>
> libnginx-mod-http-upstream-fair module is currently a part of Debian Nginx
> package.
>
> I would like to move the module to the separate package
> libnginx-mod-http-upstream-fair.
>
>
> I would like to maintain the package using
> https://salsa.debian.org/nginx-team/libnginx-mod-http-upstream-fair
> Currently is the Debian package maintained here
> https://salsa.debian.org/janmojzis/libnginx-mod-http-upstream-fair
>
> I need sponsor only for the first upload (I'm DM).
> Thank You!
>
>
ACK

Bug#1024377: ITP: libnginx-mod-nchan -- Nginx module libnginx-mod-nchan

Le ven. 18 nov. 2022 à 15:30, Jan Mojzis  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jan Mojzis 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: libnginx-mod-nchan
>   Version : 1.3.5
>   Upstream Author : Leo Ponomarev
> * URL : https://github.com/slact/nchan
> * License : BSD
>   Programming Lang: C
>   Description : libnginx-mod-nchan module for Nginx
>
>
> libnginx-mod-nchan module is currently a part of Debian Nginx package.
>
> I would like to move the module to the separate package libnginx-mod-nchan.
>
>
> I would like to maintain the package using
> https://salsa.debian.org/nginx-team/libnginx-mod-nchan
> Currently is the Debian package maintained here
> https://salsa.debian.org/janmojzis/libnginx-mod-nchan
>
> I need sponsor only for the first upload (I'm DM).
> Thank You!
>
>
ACK

Bug#1024374: ITP: libnginx-mod-rtmp -- Nginx module libnginx-mod-rtmp

Le ven. 18 nov. 2022 à 15:21, Jan Mojzis  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jan Mojzis 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: libnginx-mod-rtmp
>   Version : 1.2.2
>   Upstream Author : Roman Arutyunyan
> * URL : https://github.com/arut/nginx-rtmp-module
> * License : BSD
>   Programming Lang: C
>   Description : libnginx-mod-rtmp module for Nginx
>
>
> libnginx-mod-rtmp module is currently a part of Debian Nginx package.
>
> I would like to move the module to the separate package libnginx-mod-rtmp.
>
>
> I would like to maintain the package using
> https://salsa.debian.org/nginx-team/libnginx-mod-rtmp
> Currently is the Debian package maintained here
> https://salsa.debian.org/janmojzis/libnginx-mod-rtmp
>
> I need sponsor only for the first upload (I'm DM).
> Thank You!
>
>
ACK

Bug#1024372: ITP: libnginx-mod-http-geoip2 -- Nginx module libnginx-mod-http-geoip2

Le ven. 18 nov. 2022 à 15:15, Jan Mojzis  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jan Mojzis 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: libnginx-mod-http-geoip2
>   Version : 3.4
>   Upstream Author : Lee Valentine
> * URL : https://github.com/leev/ngx_http_geoip2_module
> * License : BSD
>   Programming Lang: C
>   Description : libnginx-mod-http-geoip2 module for Nginx
>
>
> libnginx-mod-http-geoip2 module is currently a part of Debian Nginx
> package.
>
> I would like to move the module to the separate package
> libnginx-mod-http-geoip2.
>
>
> I would like to maintain the package using
> https://salsa.debian.org/nginx-team/libnginx-mod-http-geoip2
> Currently is the Debian package maintained here
> https://salsa.debian.org/janmojzis/libnginx-mod-http-geoip2
>
> I need sponsor only for the first upload (I'm DM).
> Thank You!
>
>
ACK

Bug#1024371: ITP: libnginx-mod-http-dav-ext -- Nginx module libnginx-mod-http-dav-ext

Le ven. 18 nov. 2022 à 15:09, Jan Mojzis  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jan Mojzis 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: libnginx-mod-http-dav-ext
>   Version : 3.0.0
>   Upstream Author : Roman Arutyunyan
> * URL : https://github.com/arut/nginx-dav-ext-module
> * License : BSD
>   Programming Lang: C
>   Description : libnginx-mod-http-dav-ext module for Nginx
>
>
> libnginx-mod-http-dav-ext module is currently a part of Debian Nginx
> package.
>
> I would like to move the module to the separate package
> libnginx-mod-http-dav-ext.
>
>
> I would like to maintain the package using
> https://salsa.debian.org/nginx-team/libnginx-mod-http-dav-ext
> Currently is the Debian package maintained here
> https://salsa.debian.org/janmojzis/libnginx-mod-http-dav-ext
>
> I need sponsor only for the first upload (I'm DM).
> Thank You!
>
>
ACK

Bug#1024370: ITP: libnginx-mod-http-subs-filter -- Nginx module libnginx-mod-http-subs-filter

Le ven. 18 nov. 2022 à 15:03, Jan Mojzis  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jan Mojzis 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: libnginx-mod-http-subs-filter
>   Version : 0.6.4
>   Upstream Author : Weibin Yao
> * URL :
> https://github.com/yaoweibin/ngx_http_substitutions_filter_module
> * License : BSD
>   Programming Lang: C
>   Description : libnginx-mod-http-subs-filter module for Nginx
>
>
> libnginx-mod-http-subs-filter module is currently a part of Debian Nginx
> package.
>
> I would like to move the module to the separate package
> libnginx-mod-http-subs-filter.
>
>
> I would like to maintain the package using
> https://salsa.debian.org/nginx-team/libnginx-mod-http-subs-filter
> Currently is the Debian package maintained here
> https://salsa.debian.org/janmojzis/libnginx-mod-http-subs-filter
>
> I need sponsor only for the first upload (I'm DM).
> Thank You!
>

ACK

Bug#982145: RFS: fuzzel/1.5.1-1 [ITP] -- Application launcher for wlroots based Wayland compositors

2022-11-18 Thread Peter Colberg

Hi Antoine,

On Fri, Nov 18, 2022 at 12:06:19PM -0500, Antoine Beaupré wrote:
> On 2022-11-12 18:17:23, Peter Colberg wrote:
> > I have updated the fuzzel package to version 1.8.2-1 [1]. I will
> > push a signed tag once the package has been accepted into unstable.
> >
> > [1] 
> > https://salsa.debian.org/swaywm-team/fuzzel/-/commit/8ae19155129c7e7bf20246a105702c74a148ff03
> 
> Are you still looking for a sponsor for this?

Yes, thank you, that would be great!

Peter

Bug#982145: RFS: fuzzel/1.5.1-1 [ITP] -- Application launcher for wlroots based Wayland compositors

2022-11-18 Thread Birger Schacht


Hi,

On 11/18/22 18:06, Antoine Beaupré wrote:

On 2022-11-12 18:17:23, Peter Colberg wrote:

Dear Debian mentors,

I have updated the fuzzel package to version 1.8.2-1 [1]. I will
push a signed tag once the package has been accepted into unstable.

[1] 
https://salsa.debian.org/swaywm-team/fuzzel/-/commit/8ae19155129c7e7bf20246a105702c74a148ff03


Are you still looking for a sponsor for this?

@sway team: is there any reason why another DD should hold off on
reviewing and uploading this to NEW?

No! Please go ahead! I think there is just no time for sponsoring 
packages in the swaywm team, but that should not prevent anyone else 
from sponsoring!


cheers,
Birger


OpenPGP_0xCB06EA7B78DBE151_and_old_rev.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024390: dracut-core,dracut-network: both ship usr/lib/dracut/modules.d/95virtfs/{module-setup,mount-virtfs,parse-virtfs}.sh

Package: dracut-core,dracut-network
Version: 057+157-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

 Selecting previously unselected package dracut-network.
  Preparing to unpack .../17-dracut-network_057+157-1_all.deb ...
  Unpacking dracut-network (057+157-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-f61UUB/17-dracut-network_057+157-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/dracut/modules.d/95virtfs/module-setup.sh', 
which is also in package dracut-core 057+157-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-f61UUB/17-dracut-network_057+157-1_all.deb

These files are in both packages:

/usr/lib/dracut/modules.d/95virtfs/module-setup.sh
/usr/lib/dracut/modules.d/95virtfs/mount-virtfs.sh
/usr/lib/dracut/modules.d/95virtfs/parse-virtfs.sh


cheers,

Andreas


dracut-core=057+157-1_dracut-network=057+157-1.log.gz
Description: application/gzip

Bug#1022172: Bug#1024082: Bug#1022172: /lib/modprobe.d/50-nfs.conf causes initramfs-tools to stop including sunrpc module for nfs

2022-11-18 Thread Andras Korn

On Tue, Nov 15, 2022 at 10:00:43PM +0100, Salvatore Bonaccorso wrote:

Hi,

> > Try something like this in /lib/udev/rules.d/60-nfs.rules:
> > 
> > ACTION=="add", SUBSYSTEM=="module", KERNEL=="sunrpc", \
> >   RUN+="/sbin/sysctl -q --pattern ^sunrpc --system"
> > ACTION=="add", SUBSYSTEM=="module", KERNEL=="rpcrdma", \
> >   RUN+="/sbin/sysctl -q --pattern ^sunrpc.svc_rdma --system"
> > ACTION=="add", SUBSYSTEM=="module", KERNEL=="lockd", \
> >   RUN+="/sbin/sysctl -q --pattern ^fs.nfs.n[sl]m --system"
> > ACTION=="add", SUBSYSTEM=="module", KERNEL=="nfsv4", \
> >   RUN+="/sbin/sysctl -q --pattern 
> > ^fs.nfs.(nfs_callback_tcpport|idmap_cache_timeout) --system"
> > ACTION=="add", SUBSYSTEM=="module", KERNEL=="nfs", \
> >   RUN+="/sbin/sysctl -q --pattern ^fs.nfs --system"
> > 
> > Differently from the original file I tired anchoring the patterns, which 
> > looks more correct to me.
> 
> Thanks, I will try to test this and bring to nfs-utils upstream.
> Michael or Andras, if you can help testing it in your use cases that
> would be helpful.

I don't have a real world test case for this; I don't set any of those sysctls.

Incidentally, busybox sysctl doesn't support --pattern, so if this 
functionality is important, nfs-kernel-server needs to force inclusion of the 
"big" /sbin/sysctl in the initramfs.

András

-- 
 To understand recursion, we must first understand recursion.

Bug#1024389: python3-ledger: sefault during garbage collection

2022-11-18 Thread Marcin Owsiany

Package: python3-ledger
Version: 3.2.1-8+b5
Severity: normal

Dear Maintainer,

Here is a short repro script, that generates a segmentation violation on
completion. I include a backtrace from GDB, but unfortunately I could not find
debugging symbols for the ledger extension nor libboost-python.

porridge@fujitsu:~/Pulpit/debian/devel/ledgerhelpers/ledgerhelpers$ cat dtor.py 
import ledger
session = ledger.Session()
j = session.read_journal_from_string("""
2017-11-23 example
acct1  1 USD
acct2
""")

for post in j.query(""):
pass
print("Done.")
porridge@fujitsu:~/Pulpit/debian/devel/ledgerhelpers/ledgerhelpers$ gdb python3
GNU gdb (Debian 12.1-3) 12.1
[...]
Reading symbols from python3...
Reading symbols from 
/usr/lib/debug/.build-id/a4/6363cf9ae192e452957ceab1943bb70c310035.debug...
(gdb) r dtor.py 
Starting program: /usr/bin/python3 dtor.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Done.

Program received signal SIGSEGV, Segmentation fault.
0x7735efd8 in ledger::journal_t::clear_xdata() () from 
/usr/lib/python3/dist-packages/ledger.cpython-310-x86_64-linux-gnu.so
(gdb) bt full
#0  0x7735efd8 in ledger::journal_t::clear_xdata() () from 
/usr/lib/python3/dist-packages/ledger.cpython-310-x86_64-linux-gnu.so
No symbol table info available.
#1  0x77456af2 in ?? () from 
/usr/lib/python3/dist-packages/ledger.cpython-310-x86_64-linux-gnu.so
No symbol table info available.
#2  0x7745350d in ?? () from 
/usr/lib/python3/dist-packages/ledger.cpython-310-x86_64-linux-gnu.so
No symbol table info available.
#3  0x775e1a4f in ?? () from 
/lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
No symbol table info available.
#4  0x556edc76 in subtype_dealloc (self=) at 
../Objects/typeobject.c:1460
_tstate = 
type_needs_decref = 1
type = 
base = 0x77602680
basedealloc = 0x775e1a30
has_finalizer = 
#5  0x7745880d in 
boost::python::objects::value_holder, 
__gnu_cxx::__normal_iterator > > > >::~value_holder() ()
   from /usr/lib/python3/dist-packages/ledger.cpython-310-x86_64-linux-gnu.so
No symbol table info available.
#6  0x775e1a4f in ?? () from 
/lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
No symbol table info available.
#7  0x556edc76 in subtype_dealloc (self=) at 
../Objects/typeobject.c:1460
_tstate = 
type_needs_decref = 1
type = 
base = 0x77602680
basedealloc = 0x775e1a30
has_finalizer = 
#8  0x775e94a5 in ?? () from 
/lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
No symbol table info available.
#9  0x556d001b in _PyObject_MakeTpCall (tstate=0x55b4eab0, 
callable=, args=, nargs=1, keywords=0x0)
at ../Objects/call.c:215
call = 
argstuple = (,)
kwdict = 0x0
result = 0x0
#10 0x556f1d83 in _PyObject_VectorcallTstate 
(nargsf=9223372036854775809, kwnames=0x0, args=0x7fffdba8, 
callable=, 
tstate=0x55b4eab0) at ../Include/cpython/abstract.h:112
nargs = 1
func = 
res = 
func = 
res = 
nargs = 
#11 PyObject_CallOneArg (arg=, func=) at ../Include/cpython/abstract.h:184
_args = {, 
}
args = 0x7fffdba8
tstate = 0x55b4eab0
nargsf = 9223372036854775809
_args = 
args = 
tstate = 
nargsf = 
#12 handle_callback (ref=, callback=) at ../Objects/weakrefobject.c:952
cbresult = 
#13 0x556ee5e1 in PyObject_ClearWeakRefs (object=) at 
../Objects/weakrefobject.c:998
callback = 
current = 
count = 1
err_type = 0x0
err_value = 0x0
err_tb = 0x0
list = 
#14 0x775e1a76 in ?? () from 
/lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
No symbol table info available.
#15 0x556edc76 in subtype_dealloc (self=) at 
../Objects/typeobject.c:1460
_tstate = 
type_needs_decref = 1
type = 
base = 0x77602680
basedealloc = 0x775e1a30
has_finalizer = 
#16 0x556b99c9 in _Py_Dealloc (op=) at 
../Objects/object.c:2300
dealloc = 
dealloc = 
#17 _Py_DECREF (op=) at ../Include/object.h:500
No locals.
#18 _Py_XDECREF (op=) at ../Include/object.h:567
No locals.
#19 free_keys_object (keys=0x55c13a60) at ../Objects/dictobject.c:628
entries = 
i = 12
n = 13
state = 
#20 0x556b97b4 in dictkeys_decref (dk=) at 
../Objects/dictobject.c:337
No locals.
#21 dict_dealloc (mp=0x7773dec0) at ../Objects/dictobject.c:2076
_tstate = 0x55b4eab0
state = 
values = 0x0
keys = 0x55c13a60
i = 
n = 
#22 0x557c9890 in _Py_DECREF (op=) at 
../Include/object.h:500
No locals.
#23 _Py_XDECREF (op=) at ../Include/object.h:567
No locals.
#24

Bug#1023994:

2022-11-18 Thread Matt Hickford

Following the instructions at
https://go-team.pages.debian.net/packaging.html to use dh-make-golang
I have a draft package at
https://salsa.debian.org/hickford/golang-github-hickford-git-credential-oauth

I tried to push to
https://salsa.debian.org/go-team/packages/golang-github-hickford-git-credential-oauth
but I don't have permissions.

Bug#1024388: libtepl-6-1: missing (unversioned) Breaks+Replaces: libtepl-6-0

Package: libtepl-6-1
Version: 6.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libtepl-6-1_6.2.0-2_amd64.deb ...
  Unpacking libtepl-6-1:amd64 (6.2.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/tepl-6.mo', which is 
also in package libtepl-6-0:amd64 6.1.2-1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb


The *.mo files have the same name in both packages.


cheers,

Andreas


libtepl-6-0=6.1.2-1+b2_libtepl-6-1=6.2.0-2.log.gz
Description: application/gzip

Bug#1024387: python3-pastedeploy-tpl: missing Breaks+Replaces: python-pastedeploy-tpl (<< 3)

Package: python3-pastedeploy-tpl
Version: 3.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-pastedeploy-tpl_3.0.1-1_all.deb ...
  Unpacking python3-pastedeploy-tpl (3.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pastedeploy-tpl_3.0.1-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/paster_templates/paste_deploy/+package+/sampleapp.py_tmpl', which 
is also in package python-pastedeploy-tpl 2.1.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-pastedeploy-tpl_3.0.1-1_all.deb


cheers,

Andreas


python-pastedeploy-tpl=2.1.1-2_python3-pastedeploy-tpl=3.0.1-1.log.gz
Description: application/gzip

Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

2022-11-18 Thread Andreas Metzler

On 2022-11-16 Andreas Metzler  wrote:
[...]
> Assuming the changes work as advertised (no tests on my side, I will not
> have time till weekend) I think both m4 files should be updated in
> Debian without waiting for an upstream release. gpgme.m4 is the
> important one, the change for gpg-error.m4 is a performance improvement,
> avoiding testing for gpgrt twice when both AM_PATH_GPGME (new version) and
> AM_PATH_GPG_ERROR (unpatched) are used.

Hello,

Quick test: updating gpgme.m4 from gpgme GIT lets mutt 2.2.7-1 build
successfully if mutt's local copy m4/gpgme.m4 is removed. Afaiu aclocal
documentation there is nothing we can do more, the included outdated
gpgme.m4 is preferred.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1024386: libksba: Machine-readable copyright

2022-11-18 Thread Bastian Germann


Source: libksba
Version: 1.6.2-3
Severity: minor
Tags: patch

Hi,

Please consider applying the debian/copyright file to the machine-readable 
format.
I have enclosed a converted file, adding some missing info.

Thanks,
BastianFormat: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment:
 This package was debianized by Marcus Brinkmann  on
 Thu, 25 Jul 2002 21:50:21 +0200.
 It was later taken over by Matthias Urlichs , and is now
 maintained by Andreas Metzler , Eric Dorland
 .
Source: https://gnupg.org/ftp/gcrypt/libksba/
Upstream-Contact:
 g10 Code GmbH and Fabio Fiorina
 Bug reports: https://bugs.gnupg.org
 Security related bug reports: 

Files: *
Copyright:
 | Copyright (C) 2001, 2002, 2003, 2004, 2005, 2006, 2010, 2011
 |   2012, 2013, 2014, 2015, 2018, 2019 2020 2021 g10 Code GmbH
 | Copyright (C) 2001, 2002, 2003, 2007 Free Software Foundation, Inc.
 | Copyright (C) 2000, 2001 Fabio Fiorina
Comment:
 The library and the header files are distributed under the following
 terms (LGPLv3+/GPLv2+).
 On Debian systems, the complete text of the GNU General Public License
 version 2 can be found in `/usr/share/common-licenses/GPL-2'
 and the GNU Lesser General Public License version 3 can be found in
 `/usr/share/common-licenses/LGPL-3'.
License: LGPL-3+ or GPL-2+
 | KSBA is free software; you can redistribute it and/or modify
 | it under the terms of either
 |
 |   - the GNU Lesser General Public License as published by the Free
 | Software Foundation; either version 3 of the License, or (at
 | your option) any later version.
 |
 | or
 |
 |   - the GNU General Public License as published by the Free
 | Software Foundation; either version 2 of the License, or (at
 | your option) any later version.
 |
 | or both in parallel, as here.
 |
 | KSBA is distributed in the hope that it will be useful, but WITHOUT
 | ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
 | or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public
 | License for more details.

Files: *ChangeLog-2011 README NEWS THANKS
   autogen.sh
   m4/gpg-error.m4
   m4/libgcrypt.m4
   src/ksba-config.in
   src/ksba.m4
   src/versioninfo.rc.in
   tests/mkoidtbl.awk
Copyright: 2001-2021 g10 Code GmbH
   1999, 2002, 2011 Free Software Foundation, Inc.
License: FSFULLR

Files: doc/* tests/* configure.ac *Makefile.am
Copyright: 2001-2019 g10 Code GmbH
Comment:
 The other parts (e.g. manual, build system, tests) are distributed
 under the following terms (GPLv3).
 On Debian systems, the complete text of the GNU General Public License
 can be found in `/usr/share/common-licenses/GPL-3'.
License: GPL-3+
 | KSBA is free software; you can redistribute it and/or modify
 | it under the terms of the GNU General Public License as published by
 | the Free Software Foundation; either version 3 of the License, or
 | (at your option) any later version.
 |
 | KSBA is distributed in the hope that it will be useful,
 | but WITHOUT ANY WARRANTY; without even the implied warranty of
 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 | GNU General Public License for more details.

Files: src/cms.asn
Copyright:
 Copyright (C) 2001 g10 Code GmbH
 Copyright (C) The Internet Society (1999).  All Rights Reserved.
Comment:
 The ASN.1 definition for CMS is based on a specification published
 under the following terms (see src/cms.asn):
 On Debian systems, the complete text of the GNU General Public License
 version 2 can be found in `/usr/share/common-licenses/GPL-2'
 and the GNU Lesser General Public License version 3 can be found in
 `/usr/share/common-licenses/LGPL-3'.
License: LGPL-3+ or GPL-2+, and RFC
 | KSBA is free software; you can redistribute it and/or modify
 | it under the terms of either
 |
 |   - the GNU Lesser General Public License as published by the Free
 | Software Foundation; either version 3 of the License, or (at
 | your option) any later version.
 |
 | or
 |
 |   - the GNU General Public License as published by the Free
 | Software Foundation; either version 2 of the License, or (at
 | your option) any later version.
 |
 | or both in parallel, as here.
 |
 | KSBA is distributed in the hope that it will be useful, but WITHOUT
 | ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
 | or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public
 | License for more details.
 |
 | This module is based on the one given in appendix A of RFC2630 which
 | exhibits this copyright notice:
 |
 | Copyright (C) The Internet Society (1999).  All Rights Reserved.
 |
 | This document and translations of it may be copied and furnished to
 | others, and derivative works that comment on or otherwise explain it
 | or assist in its implementation may be prepared, copied, published
 | and distributed, in whole or in part, without restriction of any
 | kind, provided that the above copyright notice and this paragraph are

Bug#1024382: seabios: Unable to boot KVM ISA guest with "-device isa-vga"

2022-11-18 Thread Michael Tokarev


Control: tag -1 + confirmed pending

18.11.2022 18:24, Rich wrote:

Package: seabios
Version: 1.14.0-2
Severity: normal
X-Debbugs-Cc: rsahlen...@gmail.com

Dear Maintainer,

Attempting to launch a KVM with "-machine isapc" and "-device isa-vga"
produces "Could not open option rom 'vgabios.bin': No such file or directory"
from QEMU / KVM and "Guest has not initialized the display (yet)." in
the KVM vconsole.

This is easy to workaround by creating the following symlink in 
/usr/share/seabios:
ln -s vgabios-isavga.bin vgabios.bin


Oh yeah.. It is the forgotten "alternative" name. You're absolutely right.
It *was* there before, but at some point I lost this symlink somewhere.. :)

Will fix this in the next upload. Thank you!

/mjt

Bug#1012506: Fix for 64bit big-endian systems

2022-11-18 Thread David Bürgin

Hello Martin,

thank you for the patches.

Martin Grimm:
> Building opendkim with --with-gnutls disables support for ed25519, so I've 
> taken a closer look at the problematic code and found the culprit code.
> 
> The error comes from the call to the openssl function RSA_sign in 
> libopendkim/dkim.c:3945:
> 
> RSA_sign takes as fifth argument a reference to an unsigned int (4 byte) 
> variable to return the length of the signature.
> The opendkim-code uses a reference to the variable l of type size_t (unsigned 
> long, 8 bytes on s390x) casted as (signed) int reference for this.
> This is fatal for a big endian system.
> 
> I've attached to patches:
> 1.) fix-RSA_sign-call.patch: fixes the call to RSA_sign by using a temporary 
> variable ui_l of the correct type unsigned int to get back the length from 
> RSA_sign and savely assigns the returned value to l after the call.
> 2.) fix-printf-types.patch: fixes several calls of printf in dkim.c that use 
> the signed int specifier "%d" to print size_t arguments. For C99-code "%zu" 
> should be used for size_t variables.

Regarding patch 1: I don’t have access to an s390x machine and I don’t
want to spend too much time assessing this patch. I can apply it, but
please confirm that you have verified that this is the right fix and
that it does not impact the current working build. If someone else can
try it and report back, that would be useful, too.

Regarding patch 2: There are lots of compiler warnings today (eg also
for our current use of OpenSSL APIs). I can apply the patch, but
generally code cleanup is something I prefer done upstream (yeah, I
know …) instead of maintained as Debian patches.

Ciao,
David

Bug#1023807: seqan-needle: /usr/bin/needle is already shipped by emboss

Followup-For: Bug #1023807
Control: found -1 1.0.1.0.0.git.3011926+ds-2

Something didn't work with the moving of the binary to /usr/lib/debian-med/bin 
...

drwxr-xr-x root/root 0 2022-11-16 17:00 ./
drwxr-xr-x root/root 0 2022-11-16 17:00 ./usr/
drwxr-xr-x root/root 0 2022-11-16 17:00 ./usr/bin/
-rwxr-xr-x root/root879920 2022-11-16 17:00 ./usr/bin/needle
drwxr-xr-x root/root 0 2022-11-16 17:00 ./usr/share/
...
lrwxrwxrwx root/root 0 2022-11-16 17:00 ./usr/bin/seqan-needle -> 
../lib/debian-med/bin/needle

Andreas

Bug#1024385: bullseye-pu: package openvpn-auth-radius/2.1-7+deb11u1

2022-11-18 Thread Shengjing Zhu

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: z...@debian.org

[ Reason ]

Fix #954264: Support for verify-client-cert openvpn 2.4 directive.

[ Impact ]
The current version doesn't work with openvpn version (2.5.1) in stable.
The old workaround only works for openvpn 2.4.

[ Tests ]
On #954264, one reporter is someone I know and trust, and he has verified on
his vpn server.
But I don't have a openvpn server with radius, so I only reviewed the code.

[ Risks ]
The patch is trivial and easy to review.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]

+ if (param == "verify-client-cert")
+ {
+ this->deletechars();
+ if (line != 
"verify-client-certrequired")
+ {
+ 
this->clientcertnotrequired=true;
+ }
+ }

Add a new check for directive "verify-client-cert".

[ Other info ]
No.
diff -Nru openvpn-auth-radius-2.1/debian/changelog 
openvpn-auth-radius-2.1/debian/changelog
--- openvpn-auth-radius-2.1/debian/changelog2018-10-28 20:10:22.0 
+0800
+++ openvpn-auth-radius-2.1/debian/changelog2022-11-19 00:59:14.0 
+0800
@@ -1,3 +1,10 @@
+openvpn-auth-radius (2.1-7+deb11u1) bullseye; urgency=medium
+
+  * Add patch to support verify-client-cert directive in openvpn 2.4
+(Closes: #954264)
+
+ -- Shengjing Zhu   Sat, 19 Nov 2022 00:59:14 +0800
+
 openvpn-auth-radius (2.1-7) unstable; urgency=low
 
   * QA upload.
diff -Nru 
openvpn-auth-radius-2.1/debian/patches/0006-Support-verify-client-cert-directive-in-openvpn-2.4.patch
 
openvpn-auth-radius-2.1/debian/patches/0006-Support-verify-client-cert-directive-in-openvpn-2.4.patch
--- 
openvpn-auth-radius-2.1/debian/patches/0006-Support-verify-client-cert-directive-in-openvpn-2.4.patch
   1970-01-01 08:00:00.0 +0800
+++ 
openvpn-auth-radius-2.1/debian/patches/0006-Support-verify-client-cert-directive-in-openvpn-2.4.patch
   2022-11-19 00:59:14.0 +0800
@@ -0,0 +1,29 @@
+From: Shengjing Zhu 
+Date: Sat, 12 Nov 2022 19:25:57 +0800
+Subject: Support verify-client-cert directive in openvpn 2.4
+
+Bug-Debian: #954264
+Forwarded: no
+---
+ Config.cpp | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/Config.cpp b/Config.cpp
+index b600fab..d914818 100644
+--- a/Config.cpp
 b/Config.cpp
+@@ -180,6 +180,14 @@ int Config::parseConfigFile(const char * configfile)
+ 
this->clientcertnotrequired=true;
+ }
+ }
++if (param == "verify-client-cert")
++{
++this->deletechars();
++if (line != 
"verify-client-certrequired")
++{
++
this->clientcertnotrequired=true;
++}
++}
+ if (param == 
"username-as-common-name")
+ {
+ this->deletechars();
diff -Nru openvpn-auth-radius-2.1/debian/patches/series 
openvpn-auth-radius-2.1/debian/patches/series
--- openvpn-auth-radius-2.1/debian/patches/series   2018-10-28 
18:45:40.0 +0800
+++ openvpn-auth-radius-2.1/debian/patches/series   2022-11-19 
00:59:14.0 +0800
@@ -3,3 +3,4 @@
 30_build-with-debug-symbols.diff
 35_verbose_built.diff
 40_use_cppflags.diff
+0006-Support-verify-client-cert-directive-in-openvpn-2.4.patch

Bug#982145: RFS: fuzzel/1.5.1-1 [ITP] -- Application launcher for wlroots based Wayland compositors

And for what it's worth, I tested the latest package from salsa, as per:

commit 8ae19155129c7e7bf20246a105702c74a148ff03 (HEAD -> main, origin/main, 
origin/HEAD)
Author: Peter Colberg 
Date:   Sat Nov 12 17:53:29 2022 -0500

Update changelog

... and it works well. I have only reviewed the debian/ directory, not
upstream's code, but I can confirm the code in the sals repo matches the
upstream, as far as git is concerned.

That thing is fast and beautiful. :)

a.
-- 
Freedom is being able to make decisions that affect mainly you. Power
is being able to make decisions that affect others more than you. If
we confuse power with freedom, we will fail to uphold real freedom.
- Richard Stallman

Bug#1024384: RFS: selint/1.3.0-1 -- Static code analysis of refpolicy style SELinux policies

2022-11-18 Thread Christian Göttsche

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: selinux-de...@lists.alioth.debian.org, bi...@debian.org


Dear mentors,

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

 * Package name : selint
   Version  : 1.3.0-1
   Upstream contact : Daniel Burgener 
 * URL  : https://github.com/SELinuxProject/selint
 * License  : Apache-2.0
 * Vcs  : https://salsa.debian.org/selinux-team/selint
   Section  : devel

The source builds the following binary packages:

  selint - Static code analysis of refpolicy style SELinux policies

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/selint/selint_1.3.0-1.dsc

Changes since the last upload:

 selint (1.3.0-1) unstable; urgency=medium
 .
   * New upstream version 1.3.0
 .
   * debian: update repository location
   * d/watch: update format
   * d/patches: cherry-pick documentation fixes from upstream
   * d/control: bump to std version 4.6.1 (no further changes)
   * d/rules: enable werror via configure flag


This upload should fix #1024185, since version 1.3.0 includes a fix
for https://github.com/SELinuxProject/selint/issues/244.
The changelog does not include a Closes: directive since I prepared
the upload a while ago, but Laurent, the usual sponsor and member of
the SELinux team, is quite busy and has not yet had time for a
sponsorship.


Regards,
-- 
  Christian Göttsche

Bug#1024383: luseradd username not getting parsed correctly

2022-11-18 Thread Baumann Edwin

Package: libpopt0
Version: 1.19+dfsg-1 amd64
Tags: bookworm
Severity: normal

The Problem:

When trying to add a new user like this:
luseradd -g 221 -u 219814 testuser

Instead of using the given name it will use "default_useradd"
vi /etc/passwd
default_useradd:x:219814:221:default_useradd:/home/default_useradd:/bin/bash

The user also really doesn't exist with the given name.
deluser testuser
/usr/sbin/deluser: The user `testuser' does not exist.

Versions:

libuser: 1:0.63~dfsg-4+b1 amd64
kernel: Debian 5.16.14-1 x86_64 GNU/Linux
libc: Version: 2.36-4
In der elektronischen Korrespondenz kann die im Schriftverkehr übliche 
Vertraulichkeit nicht gewährleistet werden. Bitte überprüfen Sie daher 
sorgfältig, welche Mitteilungen und Beilagen Sie per E-Mail senden und erhalten 
möchten. Falls Sie dieses E-Mail irrtümlicherweise erhalten haben, bitten wir 
Sie, die absendende Person zu kontaktieren und dieses E-Mail mit allen Anhängen 
von Ihrem System zu löschen.
***
Avec la communication par courrier électronique, la confidentialité des 
informations n'est pas garantie comme elle l'est usuellement dans la 
correspondance écrite. Veuillez donc être vigilant lorsque vous envoyez ou 
recevez des communications et pièces jointes par courriel. Si vous avez reçu ce 
courriel par erreur, nous vous prions de contacter l'expéditeur/trice et de 
l'effacer avec toutes les pièces jointes de votre système. 
***
Nella corrispondenza elettronica, la confidenzialità dei dati non può essere 
garantita come nella corrispondenza scritta. Controlli quindi attentamente i 
messaggi e gli allegati che invia e riceve via e-mail. Se ha ricevuto questa 
e-mail per errore, contattati il/la mittente e cancelli il messaggio e tutti 
gli allegati dal suo sistema.

Bug#982145: RFS: fuzzel/1.5.1-1 [ITP] -- Application launcher for wlroots based Wayland compositors

On 2022-11-12 18:17:23, Peter Colberg wrote:
> Dear Debian mentors,
>
> I have updated the fuzzel package to version 1.8.2-1 [1]. I will
> push a signed tag once the package has been accepted into unstable.
>
> [1] 
> https://salsa.debian.org/swaywm-team/fuzzel/-/commit/8ae19155129c7e7bf20246a105702c74a148ff03

Are you still looking for a sponsor for this?

@sway team: is there any reason why another DD should hold off on
reviewing and uploading this to NEW?

-- 
Either you're with us or you're with the terrorist state.

Bug#1024057: slapd: service restart does not always restart slapd

2022-11-18 Thread Quanah Gibson-Mount





--On Thursday, November 17, 2022 8:39 PM + Alister Winfield 
 wrote:



Last time I had this slapd was waiting until all clients disconnect..
Perhaps that still happens.


This would not be the case.  In fact you can see from the log snippet that 
was provided that when slapd got a shutdown notice, it disconnected all the 
existing clients (which caused a lot of the connection_read messages).


--Quanah

Bug#1020903: pipewire-pulse: Is the conflict with pulseaudio necessary?

2022-11-18 Thread Dylan Aïssi

Bonjour Alain,

Es tu le Alain de debian-facile, ici :
https://debian-facile.org/viewtopic.php?pid=388561#p388561

Le sam. 12 nov. 2022 à 10:03, alain  a écrit :
>
> yes the conflict between pulse audio and pipewire-pulse is still going on.
> I just updated my sid.
> so pipewire-pulse has been installed.
> and on reboot my sound server was broken.
> i read a lot of things .
> including the need to install pipewire-audio-client-libraries.
> I didn't understand this.
> indeed, its setting required to copy and configure conf files that do not 
> exist
> under debian .
> others ask to uninstall pulse audio.
> I don't really want to do it.
> I prefer, since it is the cause, to uninstall pipewire-pulse.

Si oui, comme dit dans mon mail précédent, pourrais-tu installer wireplumber et
arrêter d'épingler des paquets au hasard? Je veux dire par là que si gnome-core
n'avais pas été épinglé alors il serait à jour et wireplumber serait installé.
Tu n'aurais donc pas de problème de son.

Tu dit que tu ne veux pas de pipewire et rester à pulseaudio, pourquoi ?
Debian Gnome est passé de pulseaudio à pipewire, en forçant le maintien de
pulseaudio, tu te retrouve dans une configuration non supporté donc ce n'est pas
sûr que tu puisse trouver de l'aide pour les conflits engendrés.

Pourrais-tu ouvrir ton propre rapport de bug la prochaine fois au lieu
de commenter
au hasard les bugs déjà ouvert, cela rend la tache plus facile pour résoudre
les différents bugs sans avoir du bruit parasite.

Merci
Dylan

Bug#998681: tor: fails to start on boot, needs manual restart later

2022-11-18 Thread Domenico Cufalo

Il giorno ven 18 nov 2022 alle ore 09:51 Peter Palfrader 
ha scritto:

> On Wed, 16 Nov 2022, Domenico Cufalo wrote:
>
> > Package: tor
> > Version: 0.4.7.11-1~bpo11+1
> > Followup-For: Bug #998681
> >
> > Dear Maintainer,
> >
> > this bug still persists.
> >
> > As far it seems, tor service needs to be launched AFTER networking. (1)
>
> I think think should be fixed in git.  If you want, you could try the
> nightly builds on deb.torproject.org.
>
>
> https://gitlab.torproject.org/tpo/core/debian/tor/-/commit/46e6de4646204a8b81d15a30d2f7045dfa38b8a8
>
>
Obviously with this patch it works .

Many thanks,
Domenico

Bug#1020527: pam-p11: diff for NMU version 0.3.1-1.2

Control: tags 1020527 + patch
Control: tags 1020527 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru pam-p11-0.3.1/debian/changelog pam-p11-0.3.1/debian/changelog
--- pam-p11-0.3.1/debian/changelog	2022-05-21 15:54:14.0 +0300
+++ pam-p11-0.3.1/debian/changelog	2022-11-18 18:02:03.0 +0200
@@ -1,3 +1,10 @@
+pam-p11 (0.3.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with --disable-strict. (Closes: #1020527)
+
+ -- Adrian Bunk   Fri, 18 Nov 2022 18:02:03 +0200
+
 pam-p11 (0.3.1-1.1) unstable; urgency=low
 
   * Non-maintainer upload
diff -Nru pam-p11-0.3.1/debian/rules pam-p11-0.3.1/debian/rules
--- pam-p11-0.3.1/debian/rules	2022-05-21 15:51:40.0 +0300
+++ pam-p11-0.3.1/debian/rules	2022-11-18 18:02:03.0 +0200
@@ -8,4 +8,4 @@
 	dh $@
 
 override_dh_auto_configure:
-	dh_auto_configure -- --libdir=/lib/$(DEB_HOST_MULTIARCH)
+	dh_auto_configure -- --libdir=/lib/$(DEB_HOST_MULTIARCH) --disable-strict

Bug#1021530: wireplumber: conflict with pulseaudio?

2022-11-18 Thread Dylan Aïssi

Hi Francois,

Le jeu. 13 oct. 2022 à 22:21, Francois Le Hir  a écrit :
>
> I was able to fix the issue on my side.
> The problem (for my situation) was a conflict between pulseaudio and pipewire 
> as both were running on my system at the same time and pipewire-pulse.service 
> was masked meaning the sound was not going through pipewire.
>

And I guess you did not manually mask pipewire-pulse.service before?

The pulseaudio.service probably started during the update of pipewire
instead of restarting the new pipewire-pulse.service.

I have both pulseaudio and pipewire-pulse installed but I have never seen this
issue. I wanted to avoid marking pipewire-pulse and pulseaudio in conflict
to allow users the possibility to switch but it looks like I will have to
do it anyway before the release of Bookworm.

Best,
Dylan

Bug#1024299: pythonmagick: b-d on python3-all-dev, but not built for all supported Python3 versions

2022-11-18 Thread Stefano Rivera

Control: retitle -1 pythonmagick: only default python3 version extension is 
published in deb

Hi Graham (2022.11.17_11:40:02_+0200)
> This package build-depends on python3-all-dev, but does not build
> extensions/libraries for all supported python3 versions.

It was trying to, but they were stomping on each other.

That's an easy fix. However... the resulting binary fails to import
under Python 3.11. That needs more debugging.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#924685: RFP: cumin -- An automation and orchestration framework