Bug#1031152: system-config-printer: unlock button in system-config-printer provides no elevated permissions dialog

2023-04-14 Thread Kevin Otte 
Package: system-config-printer
Version: 1.5.18-1
Followup-For: Bug #1031152

Workaround suggested by original reporter (sudo) ineffective on sway due to 
Wayland security model.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages system-config-printer depends on:
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  gir1.2-glib-2.0   1.74.0-3
ii  gir1.2-gtk-3.03.24.37-2
ii  gir1.2-handy-11.8.1-1
ii  gir1.2-notify-0.7 0.8.1-1
ii  gir1.2-packagekitglib-1.0 1.2.6-3
ii  gir1.2-pango-1.0  1.50.12+ds-1
ii  gir1.2-polkit-1.0 122-3
ii  python3   3.11.2-1+b1
ii  python3-cups  2.0.1-5+b4
ii  python3-cupshelpers   1.5.18-1
ii  python3-dbus  1.3.2-4+b1
ii  python3-gi3.42.2-3+b1
ii  system-config-printer-common  1.5.18-1

Versions of packages system-config-printer recommends:
ii  avahi-utils 0.8-9
ii  system-config-printer-udev  1.5.18-1

Versions of packages system-config-printer suggests:
pn  gnome-software  

-- no debconf information

Processed: tagging 993849

2023-04-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 993849 + fixed-upstream
Bug #993849 [src:gnome-authenticator] gnome-authenticator: Depends on 
deprecated libhandy version 0
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
993849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034220: marked as done (shadowsocks-libev: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

2023-04-14 Thread Debian Bug Tracking System 
Your message dated Sat, 15 Apr 2023 01:05:21 +
with message-id 
and subject line Bug#1034220: fixed in shadowsocks-libev 3.3.5+ds-10
has caused the Debian Bug report #1034220,
regarding shadowsocks-libev: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1034220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shadowsocks-libev
Version: 3.3.5+ds-9
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package shadowsocks-libev is shipping files (.service, 
.socket or
.timer) in /usr/lib/systemd/system.

This is not supported by the version of dh_installsystemd/debhelper currently
in unstable and bookworm (See: #1031695). That means that currently your
service might not be enabled at boot and/or started as expected.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u
--- End Message ---
--- Begin Message ---
Source: shadowsocks-libev
Source-Version: 3.3.5+ds-10
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
shadowsocks-libev, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1034...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated shadowsocks-libev package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Apr 2023 20:46:30 -0400
Source: shadowsocks-libev
Architecture: source
Version: 3.3.5+ds-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Bridges Team 
Changed-By: Boyuan Yang 
Closes: 1034220
Changes:
 shadowsocks-libev (3.3.5+ds-10) unstable; urgency=medium
 .
   * Revert the move of systemd service files from /lib/ to /usr/lib/.
 Still place systemd service files under /lib/systemd/system/.
 (Closes: #1034220)
Checksums-Sha1:
 75bb2d4ecaabc37ae3fcf85e923a4eec3e343f68 2480 shadowsocks-libev_3.3.5+ds-10.dsc
 bc3c68f89129a0c148f60a2c3082ddf99faa9b7c 190972 
shadowsocks-libev_3.3.5+ds.orig.tar.xz
 532f5313e71a570c615c6b4cef24fbf0da7944a2 27832 
shadowsocks-libev_3.3.5+ds-10.debian.tar.xz
 cde6caca8a0e5008d8f3584198eb827383ab9163 8825 
shadowsocks-libev_3.3.5+ds-10_amd64.buildinfo
Checksums-Sha256:
 ba011ecc83e5735509f0afec2a00149b0b6c47b813c4852a5752fb79b842033b 2480 
shadowsocks-libev_3.3.5+ds-10.dsc
 0a5179a73797867396148ca0b8df73279bbd71a8fc90a0a532a05da7a9e8a83f 190972 
shadowsocks-libev_3.3.5+ds.orig.tar.xz
 0f559c86bdc8d3fad28ca2fb4a1fb3bc63587b6ad4167318bc4d8db72fe4ec00 27832 
shadowsocks-libev_3.3.5+ds-10.debian.tar.xz
 ef70cc773dfb25b750275095623617dbcd45747c0d87343fb30cabb00190c7cc 8825 
shadowsocks-libev_3.3.5+ds-10_amd64.buildinfo
Files:
 cc243234aa8cc697870bbf3f47020a53 2480 net optional 
shadowsocks-libev_3.3.5+ds-10.dsc
 a45afaadf54204ff2880c95e5e23ca59 190972 net optional 
shadowsocks-libev_3.3.5+ds.orig.tar.xz
 c1901fc2ab18f1980a13c264c423b2be 27832 net optional 
shadowsocks-libev_3.3.5+ds-10.debian.tar.xz
 4788c22dfd2d876ea7abc7de304fcf3c 8825 net optional 
shadowsocks-libev_3.3.5+ds-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmQ59OgACgkQwpPntGGC
Ws7IYg//arZJoViZ8CVRqQS6NN8SaSPWs6S/8VB5q05ZZ9c6wsk/tLDrnkSbCe+I

Bug#1034361: haveged: autopkgtest fails on bookworm kernel: service fails to start

2023-04-14 Thread Danny van Heumen 
Hi,

I looked into haveged a while back because I ran into some issue. (Don't 
remember exactly what.)

Apparently, the upstream systemd-service contains a conditional to only start 
on old kernels. The strategies that haveged performed are apparently 
incorporated into the kernel. That makes haveged an optional "extra" 
contribution to entropy, but no longer necessary.

A issue on either haveged's github or Qubes-OS's discussed pros/cons for use in 
VMs and IIRC the benefits are doubtful due to depending on healthy input 
entropy and characteristics of VMs (as opposed to actual machines).

Running haveged as userspace tool only has uses because applications/scripts 
can use it as an API to randomness. However, the issue for running haveged 
userspace while the systemd-service is running, was broken for a while. (Not 
sure what the status is now.)

You would need to investigate in detail, as I am not knowledgeable on this 
subject, but from my understanding one would run haveged service on newer 
kernels solely for an overabundance of caution, rather than a necessity to seed 
the entropy pool.

There is an explanation with references on the haveged homepage. The issue 
should be that *if* the service is running, *then* userspace cannot start.

 Original Message 
On Apr 14, 2023, 9:47 PM, Cyril Brulebois < k...@debian.org> wrote:
Paul Gevers (2023-04-13): > The release team has announced [1] that failing 
autopkgtest on amd64 and > arm64 are considered RC in testing. [Release Team 
member hat on] Because > we're currently in the hard freeze for bookworm, I 
have marked this bug as > bookworm-ignore, however, I have a strong suspicion 
that it points out that > the package is broken. Targeted fixes are still 
welcome. The daemon starts just fine in d-i. The daemon starts just fine from 
the service unit on baremetal. I'd like extreme caution to be used before 
considering removing this package. After the 5.4 announce, trying to drop it 
from the installer didn't go quite well[1]. Maybe that's indeed better after 
5.6, but I really don't want to investigate dropping it from the installer for 
Bookworm. 1. https://lists.debian.org/debian-boot/2020/03/msg00182.html and 
replies. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- 
Release team member -- Freelance Consultant

Bug#1034423: php8.2: reproducible-builds: Paths to sed in php-config8.2 and and phpize8.2

2023-04-14 Thread Vagrant Cascadian 
Source: php8.2
Severity: serious
Justification: TC resolution #994388
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The paths to sed are embedded in two scripts shipped in /usr/bin:

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

  /usr/bin/php-config8.2

  SED="/bin/sed"
  vs.
  SED="/usr/bin/sed"

It appears this was attempted to be fixed in an earlier php package, but
the fix was either never effective, or has for some reason become
ineffective:

  https://bugs.debian.org/1015188

The attached patch fixes this by explicitly specifying the /usr/bin
path, which is compatible with both usrmerge and non-usrmerge systems.

Other approaches would be to adapt configure to be able to override the
autodetection of the path for SED, or perhaps ideal would be to specify
SED without any path, assuming it is always run in an environment where
PATH is set correctly.

Unfortunately, there are other outstanding issues and this patch is not
sufficient to make php8.2 reproducible, but it should reduce the
differences.

Thanks for maintaining php8.2!

live well,
  vagrant
From 830b885bf5495bd079bf698c7a3352ccf7a38633 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Thu, 13 Apr 2023 15:59:57 -0700
Subject: [PATCH] scripts/php*.in: Explicitly define the path to sed.

The full path is detected by configure, resulting in a different build
depending on if it is built on a usrmerge or non-usrmerge system.

Since usrmerge systems contain compatibility symlinks for the
non-usrmerge paths, use the non-usrmerge path which is compatible in
both systems.

https://tests.reproducible-builds.org/debian/issues/bookworm/paths_vary_due_to_usrmerge_issue.html
---
 scripts/php-config.in | 2 +-
 scripts/phpize.in | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/php-config.in b/scripts/php-config.in
index 45a07597..05307ee3 100644
--- a/scripts/php-config.in
+++ b/scripts/php-config.in
@@ -1,6 +1,6 @@
 #! /bin/sh
 
-SED="@SED@"
+SED="/bin/sed"
 prefix="@prefix@"
 datarootdir="@datarootdir@"
 exec_prefix="@exec_prefix@"
diff --git a/scripts/phpize.in b/scripts/phpize.in
index 0dcfe21d..0d71e795 100644
--- a/scripts/phpize.in
+++ b/scripts/phpize.in
@@ -7,7 +7,7 @@ exec_prefix="`eval echo @exec_prefix@`"
 phpdir="$prefix/lib/php/@DEBIAN_PHP_API@/build"
 includedir="$prefix/include/php/@DEBIAN_PHP_API@"
 builddir="`pwd`"
-SED="@SED@"
+SED="/bin/sed"
 
 libtool_version=$(dpkg-query -f'${Version}' -W libtool)
 aclocaldir="$prefix/share/aclocal"
-- 
2.39.2



signature.asc
Description: PGP signature

Bug#1034369: marked as done (libcereal: autopkgtest regression on non x86: cc1plus: all warnings being treated as errors)

2023-04-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Apr 2023 19:48:57 +
with message-id 
and subject line Bug#1034369: fixed in libcereal 1.3.2+dfsg-5
has caused the Debian Bug report #1034369,
regarding libcereal: autopkgtest regression on non x86: cc1plus: all warnings 
being treated as errors
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1034369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: libcereal
Version: 1.3.2+dfsg-4
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails on all 
architectures except amd64 and i386 since August 2022. Can you please 
investigate the situation and fix it? I copied some of the output at the 
bottom of this report. (src:gcc-defaults switching to gcc-12 migrated on 
2022-08-10 to testing)


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/libc/libcereal/32116422/log.gz

[ 25%] Building CXX object unittests/CMakeFiles/test_map.dir/map.cpp.o
In file included from 
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.cpp:28:
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp: 
In instantiation of ‘void test_map() [with IArchive = 
cereal::BinaryInputArchive; OArchive = cereal::BinaryOutputArchive]’:
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.cpp:34:68: 
  required from here
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp:65:43: 
error: narrowing conversion of ‘random_value(gen)’ from 
‘std::enable_if::type’ {aka ‘char’} to ‘signed char’ 
[-Werror=narrowing]
   65 |   o_esplmap.insert({random_value(gen),  { 
random_value(gen), random_value(gen) }});

  | ~~^
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp: 
In instantiation of ‘void test_map() [with IArchive = 
cereal::PortableBinaryInputArchive; OArchive = 
cereal::PortableBinaryOutputArchive]’:
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.cpp:39:84: 
  required from here
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp:65:43: 
error: narrowing conversion of ‘random_value(gen)’ from 
‘std::enable_if::type’ {aka ‘char’} to ‘signed char’ 
[-Werror=narrowing]
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp: 
In instantiation of ‘void test_map() [with IArchive = 
cereal::XMLInputArchive; OArchive = cereal::XMLOutputArchive]’:
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.cpp:44:62: 
  required from here
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp:65:43: 
error: narrowing conversion of ‘random_value(gen)’ from 
‘std::enable_if::type’ {aka ‘char’} to ‘signed char’ 
[-Werror=narrowing]
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp: 
In instantiation of ‘void test_map() [with IArchive = 
cereal::JSONInputArchive; OArchive = cereal::JSONOutputArchive]’:
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.cpp:49:64: 
  required from here
/tmp/autopkgtest-lxc.nn60praz/downtmp/autopkgtest_tmp/unittests/map.hpp:65:43: 
error: narrowing conversion of ‘random_value(gen)’ from 
‘std::enable_if::type’ {aka ‘char’} to ‘signed char’ 
[-Werror=narrowing]

cc1plus: all warnings being treated as errors
make[2]: *** [unittests/CMakeFiles/test_map.dir/build.make:76: 
unittests/CMakeFiles/test_map.dir/map.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:556: 
unittests/CMakeFiles/test_map.dir/all] Error 2

make: *** [Makefile:146: all] Error 2


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libcereal
Source-Version: 1.3.2+dfsg-5
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
libcereal, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Bug#1034361: haveged: autopkgtest fails on bookworm kernel: service fails to start

2023-04-14 Thread Cyril Brulebois 
Paul Gevers  (2023-04-13):
> The release team has announced [1] that failing autopkgtest on amd64 and
> arm64 are considered RC in testing. [Release Team member hat on] Because
> we're currently in the hard freeze for bookworm, I have marked this bug as
> bookworm-ignore, however, I have a strong suspicion that it points out that
> the package is broken. Targeted fixes are still welcome.

The daemon starts just fine in d-i.

The daemon starts just fine from the service unit on baremetal.

I'd like extreme caution to be used before considering removing this
package. After the 5.4 announce, trying to drop it from the installer
didn't go quite well[1]. Maybe that's indeed better after 5.6, but I
really don't want to investigate dropping it from the installer for
Bookworm.

 1. https://lists.debian.org/debian-boot/2020/03/msg00182.html
and replies.


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


signature.asc
Description: PGP signature

Bug#1034352: golang-github-azure-go-autorest: autopkgtest regression on arm64: request header doesn't match

2023-04-14 Thread Paul Gevers 

Hi,

On 13-04-2023 19:22, Paul Gevers wrote:

On 13-04-2023 18:17, Shengjing Zhu wrote:

Maybe you haven't rebuilt the lxc image with the new timezone, so it
still uses UTC+8.


That's what I thought so later too. Let's see what tomorrow brings.


So, the testsing container was rebuild on Apr 14 06:29 (UTC) and I just 
ran the golang-github-azure-go-autorest test: 
https://ci.debian.net/data/autopkgtest/testing/arm64/g/golang-github-azure-go-autorest/32898818/log.gz


It still fails.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: libvcflib breaks freebayes autopkgtest: Error: signal 11

2023-04-14 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:libvcflib 1.0.9+dfsg-1
Bug #1032557 [src:freebayes] libvcflib breaks freebayes autopkgtest: Error: 
signal 11
Bug reassigned from package 'src:freebayes' to 'src:libvcflib'.
No longer marked as found in versions freebayes/1.3.6-2.
Ignoring request to alter fixed versions of bug #1032557 to the same values 
previously set
Bug #1032557 [src:libvcflib] libvcflib breaks freebayes autopkgtest: Error: 
signal 11
Marked as found in versions libvcflib/1.0.9+dfsg-1.
> affects -1 src:freebayes
Bug #1032557 [src:libvcflib] libvcflib breaks freebayes autopkgtest: Error: 
signal 11
Added indication that 1032557 affects src:freebayes
> retitle -1 libvcflib breaks ABI without SONAME bump
Bug #1032557 [src:libvcflib] libvcflib breaks freebayes autopkgtest: Error: 
signal 11
Changed Bug title to 'libvcflib breaks ABI without SONAME bump' from 'libvcflib 
breaks freebayes autopkgtest: Error: signal 11'.
> tags -1 - bookworm-ignore
Bug #1032557 [src:libvcflib] libvcflib breaks ABI without SONAME bump
Removed tag(s) bookworm-ignore.

-- 
1032557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032557: libvcflib breaks freebayes autopkgtest: Error: signal 11

2023-04-14 Thread Paul Gevers 

Control: reassign -1 src:libvcflib 1.0.9+dfsg-1
Control: affects -1 src:freebayes
Control: retitle -1 libvcflib breaks ABI without SONAME bump
Control: tags -1 - bookworm-ignore

On Wed, 12 Apr 2023 17:05:47 -0700 Steve Langasek 
 wrote:

This implies that libvcflib has actually broken ABI without
changing its SONAME, and that this is what is causing the segfault.  So I
don't consider it correct to mark this bug as "fixed" in freebayes, as
libvcflib1 needs a rename to block the new library being loaded by old
binaries.


Reassigning to the right package then.

Paul
PS: tille, if you want a bug marked -ignore, please contact 
the release team and don't tag it yourself.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034349: bedtools: autopkgtest fails on bookworm kernel: ulimit: error setting limit (Operation not permitted)

2023-04-14 Thread Paul Gevers 

Hi Andreas,

On 14-04-2023 07:33, Andreas Tille wrote:

Does this mean you want me to revert the change?


Whatever works best for you.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: unarchiving 1021394

2023-04-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unarchive 1021394
Bug #1021394 {Done: Scott Talbert } [src:libcereal] 
src:libcereal: FTBFS on arm, ppc64le, s390x
Unarchived Bug 1021394
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034369: C++ help needed

2023-04-14 Thread Aaron M. Ucko 
tags 1034369 + patch
thanks

Andreas Tille  writes:

> I guess the fix will boil down to a type casting in this line
>
>   
> https://salsa.debian.org/med-team/libcereal/-/blob/master/unittests/map.hpp#L65
> 
>  o_esplmap.insert({random_value(gen),  { random_value(gen), 
> random_value(gen) }});
>
> unfortunately my C++ knowledge is too limited to know whether it is
> really that simple nor how exactly this line needs to be fixed.  The fix
> should be tested at least on arm64 (since the test passes on amd64).

#1034369 looks very similar to #1021394, which worked around
corresponding build-time errors by disabling -Werror but I see left the
autopkgtest's cmake invocation as is; there may be merit in disabling
-Werror on that front too.  At any rate, I would recommend properly
addressing the compiler's concerns by changing random_value to
random_value here and in the other unittests/*map.hpp headers to
match the corresponding containers' declarations, per the attached
patch.  The relevant platform difference is whether plain char is
signed, as it notably is on x86 but not arm*.  (There are other
architectures in each camp.)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Index: b/unittests/map.hpp
===
--- a/unittests/map.hpp
+++ b/unittests/map.hpp
@@ -62,7 +62,7 @@ void test_map()
 
 std::map o_esplmap;
 for(int j=0; j<100; ++j)
-  o_esplmap.insert({random_value(gen),  { random_value(gen), random_value(gen) }});
+  o_esplmap.insert({random_value(gen),  { random_value(gen), random_value(gen) }});
 
 std::ostringstream os;
 {
Index: b/unittests/multimap.hpp
===
--- a/unittests/multimap.hpp
+++ b/unittests/multimap.hpp
@@ -71,7 +71,7 @@ void test_multimap()
 std::multimap o_esplmultimap;
 for(int j=0; j<100; ++j)
 {
-  auto key = random_value(gen);
+  auto key = random_value(gen);
   o_esplmultimap.insert({key,  { random_value(gen), random_value(gen) }});
   o_esplmultimap.insert({key,  { random_value(gen), random_value(gen) }});
 }
Index: b/unittests/unordered_map.hpp
===
--- a/unittests/unordered_map.hpp
+++ b/unittests/unordered_map.hpp
@@ -54,7 +54,7 @@ void test_unordered_map()
 
 std::unordered_map o_esplunordered_map;
 for(int j=0; j<100; ++j)
-  o_esplunordered_map.insert({random_value(gen),  { random_value(gen), random_value(gen) }});
+  o_esplunordered_map.insert({random_value(gen),  { random_value(gen), random_value(gen) }});
 
 std::ostringstream os;
 {
Index: b/unittests/unordered_multimap.hpp
===
--- a/unittests/unordered_multimap.hpp
+++ b/unittests/unordered_multimap.hpp
@@ -71,7 +71,7 @@ void test_unordered_multimap()
 std::unordered_multimap o_esplunordered_multimap;
 for(int j=0; j<100; ++j)
 {
-  auto key = random_value(gen);
+  auto key = random_value(gen);
   o_esplunordered_multimap.insert({key,  { random_value(gen), random_value(gen) }});
   o_esplunordered_multimap.insert({key,  { random_value(gen), random_value(gen) }});
 }

Bug#1034403: php-sparkline: missing (unversioned) Breaks+Replaces: libsparkline-php

2023-04-14 Thread Andreas Beckmann 
Package: php-sparkline
Version: 2.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', 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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../php-sparkline_2.2.0-1_all.deb ...
  Unpacking php-sparkline (2.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/php-sparkline_2.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/php/sparkline/Sparkline.php', which is also 
in package libsparkline-php 0.2-7
  Errors were encountered while processing:
   /var/cache/apt/archives/php-sparkline_2.2.0-1_all.deb

The predecessor package libsparkline-php only existed up to
bullseye, therefore the Breaks+Replaces can be unversioned.


cheers,

Andreas


libsparkline-php=0.2-7_php-sparkline=2.2.0-1.log.gz
Description: application/gzip

Processed: Re: C++ help needed

2023-04-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1034369 + patch
Bug #1034369 [src:libcereal] libcereal: autopkgtest regression on non x86: 
cc1plus: all warnings being treated as errors
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1034369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034310: [digikam] [Bug 466170] Digikam 7.9.0 (and 7.8.0) crashes on startup

2023-04-14 Thread Rainer Dorsch 
Thanks Marco, that is a good link.

I provided a backtrace and upstream acknowledged the bug to be fixed in 8.1.0:

Am Freitag, 14. April 2023, 13:33:51 CEST schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=466170
> 
> --- Comment #6 from Maik Qualmann  ---
> Thanks for the interesting backtrace. We have had these strange crashes in
> connection with the splash screen before, especially with macOS. It's a race
> condition. I'll fix it tonight. The patch will only be officially included
> in digiKam-8.1.0. Alternatively, you could already test it by setting the
> entry "Show Splash=true" to "Show Splash=false" in the digikamrc.
> 
> Maik



-- 
Rainer Dorsch
http://bokomoko.de/

Processed: tagging 1030415

2023-04-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1030415 - bookworm-ignore
Bug #1030415 {Done: William Desportes } [src:php-log] 
php-log: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
Bug #1033834 {Done: William Desportes } [src:php-log] 
php-log: autopkgtest regression: extract-zend2.2.phpt
Removed tag(s) bookworm-ignore.
Removed tag(s) bookworm-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1030415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030415
1033834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034399: python3-pyocd: not compatible with Python version in Debian

2023-04-14 Thread Adrian Friedli 
Package: python3-pyocd
Version: 0.13.1+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: a...@koalatux.ch

Dear Maintainer,

pyOCD does not run with Python version 3.10 or greater.

The last few output lines of simply calling pyocd-gdbserver:

|   File "/usr/lib/python3/dist-packages/pyocd/utility/sequencer.py", line 17, 
in 
| from collections import (OrderedDict, Callable)
| ImportError: cannot import name 'Callable' from 'collections' 
(/usr/lib/python3.11/collections/__init__.py)

While this specific error should be easy to fix (Callable needs to be
imported from collections.abc instead of collections), I wonder if it
makes sense to release Debian 12 with such an old version of pyOCD.

Regards,
Adi


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 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 python3-pyocd depends on:
ii  python33.11.2-1+b1
ii  python3-colorama   0.4.6-2
ii  python3-future 0.18.2-6
ii  python3-intelhex   2.3.0-2
ii  python3-intervaltree   3.0.2-1.1
ii  python3-pkg-resources  66.1.1-1
ii  python3-pyelftools 0.29-1
ii  python3-six1.16.0-4
ii  python3-usb1.2.1-2
ii  python3-websocket  1.2.3-1
ii  python3-yaml   6.0-3+b2

python3-pyocd recommends no packages.

python3-pyocd suggests no packages.

-- no debconf information

Bug#1034369: libcereal: autopkgtest regression on non x86: cc1plus: all warnings being treated as errors

2023-04-14 Thread Michael R. Crusoe 

Control: forwarded -1 https://github.com/USCiLab/cereal/issues/787

I opened an issue upstream

--
Michael R. Crusoe



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: libcereal: autopkgtest regression on non x86: cc1plus: all warnings being treated as errors

2023-04-14 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://github.com/USCiLab/cereal/issues/787
Bug #1034369 [src:libcereal] libcereal: autopkgtest regression on non x86: 
cc1plus: all warnings being treated as errors
Set Bug forwarded-to-address to 'https://github.com/USCiLab/cereal/issues/787'.

-- 
1034369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1033785: marked as done (irssi: CVE-2023-29132)

2023-04-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Apr 2023 09:20:40 +
with message-id 
and subject line Bug#1033785: fixed in irssi 1.4.3-2
has caused the Debian Bug report #1033785,
regarding irssi: CVE-2023-29132
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1033785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: irssi
Version: 1.4.3-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for irssi.

CVE-2023-29132[0]:
| Irssi SA-2023-03 / Use after free in printing routine

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-29132
https://www.cve.org/CVERecord?id=CVE-2023-29132
[1] https://irssi.org/security/irssi_sa_2023_03.txt
[2] 
https://github.com/irssi/irssi/commit/c554a45738712219c066897b09a44d99afeb4240

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: irssi
Source-Version: 1.4.3-2
Done: Rhonda D'Vine 

We believe that the bug you reported is fixed in the latest version of
irssi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rhonda D'Vine  (supplier of updated irssi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Apr 2023 10:25:21 +0200
Source: irssi
Architecture: source
Version: 1.4.3-2
Distribution: unstable
Urgency: critical
Maintainer: Rhonda D'Vine 
Changed-By: Rhonda D'Vine 
Closes: 1033785
Changes:
 irssi (1.4.3-2) unstable; urgency=critical
 .
   * Pull commit c554a4 from upstream to fix CVE-2023-29132 (closes: #1033785)
Checksums-Sha1:
 29176bc08197df484c59c9016082576cbfd4be40 2253 irssi_1.4.3-2.dsc
 2bcf908e611dd36062bd825d77a535d736d7c644 17392 irssi_1.4.3-2.debian.tar.xz
 0b4448e7ca9ac628f062c6485a7a6a156cf132cf 8242 irssi_1.4.3-2_amd64.buildinfo
Checksums-Sha256:
 a697a6f62b2df2b376019cd198b17c516aa4aebc141b7846749418fbd8d649e2 2253 
irssi_1.4.3-2.dsc
 afee365e1b3fb7f920b5e83acbb2373e2787cca6f1260e4ade1a6b8a06cc968f 17392 
irssi_1.4.3-2.debian.tar.xz
 ade613565c14b365602633969d6e57aa7f7de8e2d3a8c8f0191b9cda3c775bed 8242 
irssi_1.4.3-2_amd64.buildinfo
Files:
 529b44b25b8f3f27a08eabd6a87a303e 2253 net optional irssi_1.4.3-2.dsc
 59615ddbafeba1d0ac547a021e344f7c 17392 net optional irssi_1.4.3-2.debian.tar.xz
 586e3a80ae2a5b70a4667f46bb4e7a7c 8242 net optional 
irssi_1.4.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELHLzKO0XByBPs0mU3ugEPuF+uzAFAmQ5FXAACgkQ3ugEPuF+
uzCvtA/+JScqlSOW/DOzsxdHvHgYmG9ONP0IQl29wkhaCxpbUE3LP4QIUN9NKVso
gpbMceH9hPds5r78O23L+so9rmRsWk7legj7aeCoG9uewXZcK1O6mVeigZEuLm+e
FBz9C2WbswOKBraK4aWwP3Qfh71bh8ExewTaAqvCgA9eUR2lz8qG+fZFgRfI/p7f
P8rEnwvzRmXkJ+1zKLCxMpgIAkT7jSpN7ufou3h6BVdWIm2qt8Iy0+AN/zsvPn3C
WyJxDe4v2aCvhxAAMyyQ5lM8egDT99hlmj4zK4EMgQLPpSrQldDM/nXHMndmcKDP
IPypZ1bJpQif34VARDW21GV05PLm3/c5/TGSa3OxSsJ/DPQ7uDB6yQu2XiZ78tvg
F6NbGtKC+dcxZ7bQOpayeQLtbSSgwA6EN4oWCq0RPj8rTOxhktIBEnHfLY8FC3Jm
gaYVvrpCE++NBeOzV0EylapkG5t1Pme7qjRoNRDwU1oe++sjER4q5jaWjybvRqHg
UdU9RVlkYtHomcqCdl/zv6D4GfjpBT6S6vpZ4Bphwg/wrJRC6DRNojBf9dJ/m2ij
MBHzsiRnTRHffrhYgtvx3U5K9H1YqK7OKBL1qdzy9g/u7gquGQVN0yq0AdQ9pHv3
/lDgk8KSleaXoZCnBBv2Brvcvg0mZfD5jGYvh1KPaOzKL88ZQFY=
=n49Q
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1034389: installation-reports: bookworm cannot install base system

2023-04-14 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 important
Bug #1034389 [installation-reports] installation-reports: bookworm cannot 
install base system
Severity set to 'important' from 'grave'
> tag -1 - d-i
Bug #1034389 [installation-reports] installation-reports: bookworm cannot 
install base system
Removed tag(s) d-i.

-- 
1034389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034389: installation-reports: bookworm cannot install base system

2023-04-14 Thread Cyril Brulebois 
Control: severity -1 important
Control: tag -1 - d-i

Hi Steve,

Steve Witt  (2023-04-13):
> Tried installing in both expert mode, and normal mode. After
> partitioning the disks went to the 'Install the base system' step. It
> failed with the text: Cannot install base system. The installer cannot
> figure out how to install the base system. If found no installable
> image, and no valid mirror was configured.

We'll need more details…

> Please make sure that any installation logs that you think would
> be useful are attached to this report. Please compress large
> files using gzip.

Please attach /var/log/syslog (compressed) from the installer
environment.


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


signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#1034233: tlp: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

2023-04-14 Thread Debian Bug Tracking System 
Processing control commands:

> fixed -1 1.5.0-2
Bug #1034233 [tlp] tlp: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
Marked as fixed in versions tlp/1.5.0-2.
> thanks
Unknown command or malformed arguments to command.


-- 
1034233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1034233: tlp: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

2023-04-14 Thread Raphaël Halimi 

Control: fixed -1 1.5.0-2
Control: thanks

Forgot to mention the closed bug in the changelog.

--
Raphaël Halimi

Processed: severity of 1034367 is serious, found 1034367 in 4.34.0-1

2023-04-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 1034367 serious
Bug #1034367 [v2ray] v2ray geoip data has problematic license
Severity set to 'serious' from 'normal'
> found 1034367 4.34.0-1
Bug #1034367 [v2ray] v2ray geoip data has problematic license
Marked as found in versions golang-v2ray-core/4.34.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1034367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems