Bug#1023715: marked as done (python-libtmux: autopkgtest failure on armel, armhf and s390x)

[Debian Bug Tracking System]

Your message dated Wed, 09 Nov 2022 07:34:47 +
with message-id 
and subject line Bug#1023715: fixed in python-libtmux 0.15.8-2
has caused the Debian Bug report #1023715,
regarding python-libtmux: autopkgtest failure on armel, armhf and s390x
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.)


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

Source: python-libtmux
Version: 0.15.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package python-libtmux, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


I copied some of the output at the bottom of this report. The name of 
the test hints that the test may be too sensitive to slower test 
environments. If the test passes on retries, a test is flaky, which we 
consider RC too.


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

Paul

[1] https://qa.debian.org/excuses.php?package=python-libtmux

https://ci.debian.net/data/autopkgtest/testing/armel/p/python-libtmux/27460261/log.gz

=== FAILURES 
===
___ test_function_times_out_no_rise 



def test_function_times_out_no_rise() -> None:
ini = time()
def never_true() -> bool:
return False
retry_until(never_true, 1, raises=False)
end = time()
>   assert abs((end - ini) - 1.0) < 0.01
E   assert 0.01221323013305664 < 0.01
E+  where 0.01221323013305664 = abs(((1666538658.7831485 - 
1666538657.7709353) - 1.0))


tests/test_test.py:54: AssertionError
=== short test summary info 

FAILED tests/test_test.py::test_function_times_out_no_rise - assert 
0.0122132...
= 1 failed, 92 passed, 1 deselected in 18.51s 
==

autopkgtest [10:24:29]: test pytest



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-libtmux
Source-Version: 0.15.8-2
Done: Sebastien Delafond 

We believe that the bug you reported is fixed in the latest version of
python-libtmux, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated python-libtmux 
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: Wed, 09 Nov 2022 08:02:32 +0100
Source: python-libtmux
Architecture: source
Version: 0.15.8-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Closes: 1023715
Changes:
 python-libtmux (0.15.8-2) unstable; urgency=medium
 .
   [ Sébastien Delafond ]
   * tests: exclude slow test_function_times_out_no_rise (Closes: #1023715)
Checksums-Sha1:
 ef1f7f56dc0ce6745f4486e056de6c8a745d9e6f 1769 python-libtmux_0.15.8-2.dsc
 ed60852c67f55813e5d16ee822e2d7ebc8659162 3044 
python-libtmux_0.15.8-2.debian.tar.xz
 8073bde6a53f1ba3f015a24e6c542d3d813a9f3d 6574 
python-libtmux_0.15.8-2_amd64.buildinfo
Checksums-Sha256:
 cbb945e535ad54bba82b7226c0e0d517ebec125c5a3c7608dd2f3c06c4df651b 1769 
python-libtmux_0.15.8-2.dsc
 9f643f3efba66aef5ca760fa178399e8f41b3e5e2544db02ecc193d54108ee97 3044 
python-libtmux_0.15.8-2.debian.tar.xz
 3b09bb06ff859594a810c20153982d3311f0a80ade146ab7a00a4dcb8a75157e 6574 
python-libtmux_0.15.8-2_amd64.buildinfo
Files:
 5b6b8aa75cc3b818a613102ee3c6b66f 1769 python optional 
python-libtmux_0.15.8-2.dsc
 b0eb27692c5901f8e28345c92d0c470f 3044 python optional 
python-libtmux_0.15.8-2.debian.tar.xz
 7b5c21db93f30018149d825612a64018 6574 python optional 
python-libtmux_0.15.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAmNrUT4ACgkQEL6Jg/PV

Processed: Re: osmo-msc: FTBFS in sid (libsmpp34 failure)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1023669 serious
Bug #1023669 [src:libsmpp34] osmo-msc: FTBFS in sid (libsmpp34 failure)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: buildbot: FTBFS with dh_auto_test failures

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/buildbot/buildbot/commit/54b8f629
Bug #1021921 [src:buildbot] buildbot: FTBFS with dh_auto_test failures
Set Bug forwarded-to-address to 
'https://github.com/buildbot/buildbot/commit/54b8f629'.

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

Bug#1021921: buildbot: FTBFS with dh_auto_test failures

[s3v]

Control: forwarded -1 https://github.com/buildbot/buildbot/commit/54b8f629
thanks

Dear Maintainer,

After applying this commit from upstream, I was able to build your
package in a sid chroot environment.

Kind Regards

Bug#1023185: marked as done (veusz does not run)

[Debian Bug Tracking System]

Your message dated Wed, 09 Nov 2022 05:20:32 +
with message-id 
and subject line Bug#1023185: fixed in veusz 3.5.3-1
has caused the Debian Bug report #1023185,
regarding veusz does not run
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.)


-- 
1023185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: veusz
Version: 3.3.1-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: didi...@gmail.com

Dear Maintainer,

veusz does not start when launched from the GUI or from the CLI.
Here is the output of trying to run veusz from a terminal:

$  LANG=C veusz
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Traceback (most recent call last):
  File "/usr/bin/veusz", line 33, in 
sys.exit(load_entry_point('veusz==3.3.1', 'gui_scripts', 'veusz')())
  File "/usr/lib/python3/dist-packages/veusz/veusz_main.py", line 369, in
run
app.startup()
  File "/usr/lib/python3/dist-packages/veusz/veusz_main.py", line 267, in
startup
self.splash = makeSplash(self)
  File "/usr/lib/python3/dist-packages/veusz/veusz_main.py", line 69, in
makeSplash
font.setPointSize(font.pointSize()*1.5)
TypeError: setPointSize(self, int): argument 1 has unexpected type 'float'

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

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

Versions of packages veusz depends on:
ii  libjs-sphinxdoc  4.5.0-4
ii  python3  3.10.6-1
ii  python3-numpy1:1.21.5-1+b1
ii  python3-veusz3.3.1-3

veusz recommends no packages.

veusz suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: veusz
Source-Version: 3.5.3-1
Done: Jeremy Sanders 

We believe that the bug you reported is fixed in the latest version of
veusz, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Sanders  (supplier of updated veusz 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: Sun, 06 Nov 2022 13:55:00 +0300
Source: veusz
Architecture: source
Version: 3.5.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Jeremy Sanders 
Closes: 1023185
Changes:
 veusz (3.5.3-1) unstable; urgency=low
 .
   * Update to Veusz 3.5.3 (Closes: #1023185)
   * Update Standards-Version to 4.6.1
   * Remove upstreamed patches (sipbuild API and sip6 build system)
   * Remove source causing lintian error source-is-missing
   * Clean up rules
Checksums-Sha1:
 cff590d72cde8b752c67d47b52e457d7483cb4b5 2724 veusz_3.5.3-1.dsc
 ab127b332554347679e6db571194b948da20c671 3319834 veusz_3.5.3.orig.tar.gz
 1cb2f81b3d5012488b934fff351da3e68c3e6e2d 4462007 veusz_3.5.3.orig.tar.gz.asc
 90d10ad1591d481c4f7d7f49ea1b2ff3b2509e10 18372 veusz_3.5.3-1.debian.tar.xz
 0528e4aa09c0b2cbd95804f019e9d338cd719f9a 13750 veusz_3.5.3-1_source.buildinfo
Checksums-Sha256:
 cbea4e8fdd833d0441589b233eafa389dadf2df18fa368fced5149854044cd7a 2724 
veusz_3.5.3-1.dsc
 d4c3c29a4d314a97d7ec25cf154e381df3c8f5910a94e1bd993e7ba1c4d69473 3319834 
veusz_3.5.3.orig.tar.gz
 83ccd9d33c38f344b53222e79413532344d02ba2428d3cb4977a41639f854b54 4462007 
veusz_3.5.3.orig.tar.gz.asc
 225b337753a6c77785afdb53082633c7169deb2957b1bb742258a7290693512c 18372 
veusz_3.5.3-1.debian.tar.xz
 100bc1fc8c322942248db696fbd721f061989c61b24d1da44024f557a3cda337 13750 
veusz_3.5.3-1_source.buildinfo
Files:
 133d9b6b8001de991490a02f0a82b720 2724 science optional veusz_3.5.3-1.dsc
 773b39d1aaa05bef221fe5c7f72c9dbe 3319834 science optional 
veusz_3.5.3.orig.tar.gz
 fd6a2ea5857628aa7ffeee8c4ac68660 4462007 science optional 
veusz_3.5.3.orig.tar.gz.asc
 8c0f28d5eaf45e3855b10178f1b76787 18372 science optional 
veusz_3.5.3-1.debian.tar.xz
 

Processed: affects 1023421, merging 1023421 1023685

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1023421 libhttp-message-perl
Bug #1023421 [src:libdancer-perl] libdancer-perl: FTBFS: 
t/12_response/10_error_dumper_without_clone.t failure
Added indication that 1023421 affects libhttp-message-perl
> merge 1023421 1023685
Bug #1023421 [src:libdancer-perl] libdancer-perl: FTBFS: 
t/12_response/10_error_dumper_without_clone.t failure
Bug #1023685 [src:libdancer-perl] libdancer-perl: FTBFS: 
10_error_dumper_without_clone.t failure
Merged 1023421 1023685
> thanks
Stopping processing here.

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

Processed: retitle 1023422 to minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 'file' not allowed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1023422 minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 
> 'file' not allowed
Bug #1023422 [src:minilla] FTBFS: test failure
Bug #1023689 [src:minilla] minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed
Changed Bug title to 'minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed' from 'FTBFS: test failure'.
Ignoring request to change the title of bug#1023689 to the same title
> thanks
Stopping processing here.

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

Processed: retitle 1023421 to libdancer-perl: FTBFS: t/12_response/10_error_dumper_without_clone.t failure

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1023421 libdancer-perl: FTBFS: 
> t/12_response/10_error_dumper_without_clone.t failure
Bug #1023421 [src:libdancer-perl] FTBFS: test failure in 
t/12_response/10_error_dumper_without_clone.t
Changed Bug title to 'libdancer-perl: FTBFS: 
t/12_response/10_error_dumper_without_clone.t failure' from 'FTBFS: test 
failure in t/12_response/10_error_dumper_without_clone.t'.
> thanks
Stopping processing here.

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

Processed (with 1 error): merging 1023421 1023685

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 1023421 1023685
Bug #1023421 [src:libdancer-perl] FTBFS: test failure in 
t/12_response/10_error_dumper_without_clone.t
Unable to merge bugs because:
affects of #1023685 is 'libhttp-message-perl' not ''
Failed to merge 1023421: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: merging 1023422 1023689

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 1023422 1023689
Bug #1023422 [src:minilla] FTBFS: test failure
Bug #1023689 [src:minilla] minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed
Added tag(s) sid and bookworm.
Merged 1023422 1023689
> thanks
Stopping processing here.

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

Bug#1023303: jhead 1:3.06.0.1-3 deletes EXIF data

[Stefan Pietsch]

On 04.11.22 09:36, Joachim Reichel wrote:

Hi Stefan,

it would have been helpful if you had attached an image that shows this behavior. I have an idea what the problem might be, but having 
access to your test case for verification would be good. Feel free to send it directly to my email address if you prefer.


Best regards,
   Joachim



Hi Joachim,

I have uploaded the test picture here: 
https://salsa.debian.org/IPv4v6/debian-bug-1023303/-/blob/master/IMG_20221102_000230.jpg


Best regards,
Stefan

Bug#1023719: field3d FTBFS: OpenEXR/ImathBox.h: No such file or directory

[Adrian Bunk]

Source: field3d
Version: 1.7.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=field3d=amd64=1.7.2-1%2Bb11=1667935694=0

...
/usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK 
-DBOOST_THREAD_DYN_LINK -DField3D_EXPORTS -DREQUIRE_IOSTREAM 
-I/<>/. -I/<>/src -I/<>/export 
-I/<>/include -I/usr/include/hdf5/serial -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   
-fPIC -Wno-invalid-offsetof -MD -MT 
CMakeFiles/Field3D.dir/src/ClassFactory.cpp.o -MF 
CMakeFiles/Field3D.dir/src/ClassFactory.cpp.o.d -o 
CMakeFiles/Field3D.dir/src/ClassFactory.cpp.o -c 
/<>/src/ClassFactory.cpp
In file included from /<>/export/Types.h:56,
 from /<>/export/Traits.h:54,
 from /<>/export/Field.h:55,
 from /<>/export/ClassFactory.h:50,
 from /<>/src/ClassFactory.cpp:44:
/<>/export/StdMathLib.h:41:10: fatal error: OpenEXR/ImathBox.h: No 
such file or directory
   41 | #include 
  |  ^~~~
compilation terminated.
make[3]: *** [CMakeFiles/Field3D.dir/build.make:79: 
CMakeFiles/Field3D.dir/src/ClassFactory.cpp.o] Error 1

Bug#1019806: marked as pending in sooperlooper

[Olly Betts]

On Tue, Sep 20, 2022 at 09:18:52PM +, Dennis Braun wrote:
> Control: tag -1 pending
> 
> Hello,
> 
> Bug #1019806 in sooperlooper reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
> 
> https://salsa.debian.org/multimedia-team/sooperlooper/-/commit/f8994f33f1dbfae2d7f4820f7c35af60b14501db
> 
> 
> Transition to wxWidgets 3.2 (Closes: #1019806)
> 

This was tagged "pending" 7 weeks ago, but hasn't been uploaded yet.

Could one of the maintainers please make an upload soon?

I see recent uploads were sponsored - if lack of a sponsor is the blocker
I can sponsor.

Cheers,
Olly

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Sudip Mukherjee]

On Tue, Nov 8, 2022 at 6:06 PM Pavel Odintsov  wrote:
>
> Hello!
>
> I think I have one more question.
>
> For most of the platforms we support libbpf 1.0.1 works fine but I noticed 
> issues with Debian 11 and Ubuntu 20 about enum declarations:

Can you please give me the steps to reproduce this enum error. libbpf
1.0.1 is not available in Debian-11, so I built a backport package for
libbpf/1.0.1 and then tried building fastnetmon with the backported
libbpf in a Bullseye chroot. I did not see the enum issue, but I got a
different error:

/<>/src/fastnetmon.cpp: In function ‘int main(int, char**)’:
/<>/src/fastnetmon.cpp:1540:14: error: ‘std::filesystem’
has not been declared
 1540 | if (std::filesystem::exists(backtrace_path)) {
  |  ^~
/<>/src/fastnetmon.cpp:1550:14: error: ‘std::filesystem’
has not been declared
 1550 | std::filesystem::remove(backtrace_path);
  |  ^~
make[3]: *** [CMakeFiles/fastnetmon.dir/build.make:85:
CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o] Error 1

Note: I saw that you have commented on the upstream issue about the
enum problem and noticed you are using "latest C++ compiler (not from
Linux distro) and C++ 2022."

-- 
Regards
Sudip

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Sudip Mukherjee]

On Tue, Nov 8, 2022 at 4:55 PM Pavel Odintsov  wrote:
>
> Hello!
>
> Added copy to all.
>
> I think I fixed it with these commits: 
> https://github.com/pavel-odintsov/fastnetmon/commit/c48497a6f109fc1a9f5da596b055c3b7cffb96d4
>  and 
> https://github.com/pavel-odintsov/fastnetmon/commit/c718e88d0b25dcfbd724e9820f592fd5782eca6c

Thanks.

>
> I've used 
> https://lore.kernel.org/bpf/20220202225916.3313522-7-and...@kernel.org/ and 
> https://lxr.missinglinkelectronics.com/linux+v5.19/samples/bpf/xdp1_user.c as 
> examples as this code was my reference during implementation.
>
> Would be great if you could review it a second time.

lgtm.


-- 
Regards
Sudip

Processed: eviacam: diff for NMU version 2.1.4-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1019790 + patch
Bug #1019790 [src:eviacam] eviacam: Please transition to wxwidgets3.2
Added tag(s) patch.

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

Bug#1019790: eviacam: diff for NMU version 2.1.4-2.1

[Olly Betts]

Control: tags 1019790 + patch

Dear maintainer,

I've managed to build eviacam using wxwidgets3.2 with a couple of minor
changes (patch attached).

However I can't test my patched build because eviacam doesn't start
(I'm guessing it doesn't like my webcam for some reason) - starting it I
get:

$ eviacam
[ERROR:0@0.016] global ./modules/core/src/persistence.cpp (505) open Can't open 
file: '/usr/share/eviacam/haarcascade_frontalface_default.xml' in read mode
[ERROR:0@0.017] global ./modules/core/src/persistence.cpp (505) open Can't open 
file: '/usr/share/opencv/haarcascades/haarcascade_frontalface_default.xml' in 
read mode
[ERROR:0@0.017] global ./modules/core/src/persistence.cpp (505) open Can't open 
file: '/usr/share/OpenCV/haarcascades/haarcascade_frontalface_default.xml' in 
read mode
[libwebcam] Invalid V4L2 control type encountered: ctrl_id = 0x00980001, name = 
'User Controls', type = 6
[libwebcam] Invalid or unsupported V4L2 control encountered: ctrl_id = 
0x00980001, name = 'User Controls'
[libwebcam] Invalid V4L2 control type encountered: ctrl_id = 0x009A0001, name = 
'Camera Controls', type = 6
[libwebcam] Invalid or unsupported V4L2 control encountered: ctrl_id = 
0x009A0001, name = 'Camera Controls'

(eviacam:184091): Gtk-CRITICAL **: 10:24:53.628: gtk_box_gadget_distribute: 
assertion 'size >= 0' failed in GtkScrollbar
[ WARN:0@3.768] global ./modules/videoio/src/videoio_c.cpp (15) 
cvCreateCameraCapture cvCreateCameraCapture doesn't support legacy API anymore.
$

I also get the same error for the version already in unstable.

Please can you test with my patch, and upload if it works.

Cheers,
Olly
diff -Nru eviacam-2.1.4/debian/changelog eviacam-2.1.4/debian/changelog
--- eviacam-2.1.4/debian/changelog	2020-02-12 02:09:11.0 +1300
+++ eviacam-2.1.4/debian/changelog	2022-11-09 10:14:08.0 +1300
@@ -1,3 +1,11 @@
+eviacam (2.1.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Update to build with wxwidgets-3.2 (new patch
+wx3.2-compat.patch) (Closes: #1019790)
+
+ -- Olly Betts   Wed, 09 Nov 2022 10:14:08 +1300
+
 eviacam (2.1.4-2) unstable; urgency=medium
 
   * Team upload
diff -Nru eviacam-2.1.4/debian/control eviacam-2.1.4/debian/control
--- eviacam-2.1.4/debian/control	2020-02-12 02:09:11.0 +1300
+++ eviacam-2.1.4/debian/control	2022-11-09 10:05:50.0 +1300
@@ -7,7 +7,7 @@
libopencv-dev (>= 2.0),
libpng-dev,
libv4l-dev,
-   libwxgtk3.0-gtk3-dev,
+   libwxgtk3.2-dev,
libgtk-3-dev,
libxext-dev,
libxtst-dev,
diff -Nru eviacam-2.1.4/debian/patches/series eviacam-2.1.4/debian/patches/series
--- eviacam-2.1.4/debian/patches/series	2020-02-12 02:09:11.0 +1300
+++ eviacam-2.1.4/debian/patches/series	2022-11-09 10:14:08.0 +1300
@@ -1 +1,2 @@
 new-opencv.patch
+wx3.2-compat.patch
diff -Nru eviacam-2.1.4/debian/patches/wx3.2-compat.patch eviacam-2.1.4/debian/patches/wx3.2-compat.patch
--- eviacam-2.1.4/debian/patches/wx3.2-compat.patch	1970-01-01 12:00:00.0 +1200
+++ eviacam-2.1.4/debian/patches/wx3.2-compat.patch	2022-11-09 10:14:08.0 +1300
@@ -0,0 +1,29 @@
+Description: Fixes for compatibility with wxWidgets 3.2
+Author: Olly Betts 
+Bug-Debian: https://bugs.debian.org/1019790
+Forwarded: no
+Last-Update: 2022-11-08
+
+--- a/src/wviacam.cpp
 b/src/wviacam.cpp
+@@ -598,7 +598,8 @@
+ 		case (wxLANGUAGE_SPANISH_GUATEMALA):
+ 		case (wxLANGUAGE_SPANISH_HONDURAS):
+ 		case (wxLANGUAGE_SPANISH_MEXICAN):
+-		case (wxLANGUAGE_SPANISH_MODERN):
++		// Same value as wxLANGUAGE_SPANISH in wx3.2:
++		// case (wxLANGUAGE_SPANISH_MODERN):
+ 		case (wxLANGUAGE_SPANISH_NICARAGUA):
+ 		case (wxLANGUAGE_SPANISH_PANAMA):
+ 		case (wxLANGUAGE_SPANISH_PARAGUAY):
+--- a/src/viacamcontroller.cpp
 b/src/viacamcontroller.cpp
+@@ -230,7 +230,7 @@
+ 
+ 			wxSingleChoiceDialog choiceDlg(
+ NULL, _("Choose the camera to use"), _T("Enable Viacam"), strArray, 
+-(char**)NULL, wxDEFAULT_DIALOG_STYLE | wxOK | wxCANCEL | wxCENTRE);
++(void**)NULL, wxDEFAULT_DIALOG_STYLE | wxOK | wxCANCEL | wxCENTRE);
+ 
+ 			if (choiceDlg.ShowModal ()!= wxID_OK) return NULL;
+ 

Bug#1023715: python-libtmux: autopkgtest failure on armel, armhf and s390x

[Paul Gevers]

Source: python-libtmux
Version: 0.15.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package python-libtmux, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


I copied some of the output at the bottom of this report. The name of 
the test hints that the test may be too sensitive to slower test 
environments. If the test passes on retries, a test is flaky, which we 
consider RC too.


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

Paul

[1] https://qa.debian.org/excuses.php?package=python-libtmux

https://ci.debian.net/data/autopkgtest/testing/armel/p/python-libtmux/27460261/log.gz

=== FAILURES 
===
___ test_function_times_out_no_rise 



def test_function_times_out_no_rise() -> None:
ini = time()
def never_true() -> bool:
return False
retry_until(never_true, 1, raises=False)
end = time()
>   assert abs((end - ini) - 1.0) < 0.01
E   assert 0.01221323013305664 < 0.01
E+  where 0.01221323013305664 = abs(((1666538658.7831485 - 
1666538657.7709353) - 1.0))


tests/test_test.py:54: AssertionError
=== short test summary info 

FAILED tests/test_test.py::test_function_times_out_no_rise - assert 
0.0122132...
= 1 failed, 92 passed, 1 deselected in 18.51s 
==

autopkgtest [10:24:29]: test pytest



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023697: Keep out of testing

[Felix Lechner]

Hi,

On Tue, Nov 8, 2022 at 12:00 PM Moritz Muehlenhoff  wrote:
>
> wolfssl has no active maintainer, plenty of open security issues and we 
> already
> have too many TLS libraries in our releases. Keep it out of testing. I'm going
> to file bugs against the handful of reverse deps.

Sorry, I have been out ill, but please do what you think is right.

Kind regards
Felix

Processed: why3 breaks frama-c (autopkgtest): missing versioned Breaks?

[Debian Bug Tracking System]

Processing control commands:

> found -1 why3/1.5.1-1
Bug #1023712 [src:why3] why3 breaks frama-c (autopkgtest): missing versioned 
Breaks?
Marked as found in versions why3/1.5.1-1.

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

Bug#1023712: why3 breaks frama-c (autopkgtest): missing versioned Breaks?

[Paul Gevers]

Source: why3
Control: found -1 why3/1.5.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainer(s),

With a recent upload of why3 the autopkgtest of frama-c fails in testing 
when that autopkgtest is run with the binary packages of why3 from 
unstable. It passes when run with only packages from testing. In tabular 
form:


   passfail
why3   from testing1.5.1-1
frama-cfrom testing20220511-manganese-1.3
all others from testingfrom testing

I copied some of the output at the bottom of this report. The message 
seems serious enough (to my eyes) that you'd want to prevent this on 
partial upgrades and during dist-upgrades. Does why3 (version in 
unstable) really break the version of frama-c in testing? Then adding a 
*versioned* Breaks might be a good idea. Maybe the failure isn't as bad 
as it looks, then please just close this bug report (but be warned, why3 
might migrate then, while the fixed frama-c seems stuck).


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


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

Paul

[1] https://qa.debian.org/excuses.php?package=why3

https://ci.debian.net/data/autopkgtest/testing/amd64/f/frama-c/28047266/log.gz

[kernel] User Error: cannot load plug-in 'frama-c-wp': cannot load module
  Details: implementation mismatch on Why3
[kernel] User Error: Deferred error message was emitted during 
execution. See above messages for more information.

[kernel] Frama-C aborted: invalid user input.
autopkgtest [20:18:19]: test eva



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023711: Missing python_socks

[Yuri D'Elia]

Package: python3-aiohttp-socks
Version: 0.7.1-1
Severity: grave

aiohttp-socks 0.7.1 fails to import:

>>> import aiohttp_socks
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/aiohttp_socks/__init__.py", line 4, in 

from python_socks import (
ModuleNotFoundError: No module named 'python_socks'

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

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

Versions of packages python3-aiohttp-socks depends on:
ii  python3  3.10.6-1
ii  python3-aiohttp  3.8.3-1
ii  python3-attr 22.1.0-1

python3-aiohttp-socks recommends no packages.

python3-aiohttp-socks suggests no packages.

Bug#1023710: jbigkit: autopkgtest failure: unittests-Makefile: No such file or directory

[Paul Gevers]

Source: jbigkit
Version: 2.1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package jbigkit, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


I copied some of the output at the bottom of this report.

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

Paul

[1] https://qa.debian.org/excuses.php?package=jbigkit

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jbigkit/27243460/log.gz

make: unittests-Makefile: No such file or directory
make: *** No rule to make target 'unittests-Makefile'.  Stop.
autopkgtest [15:21:30]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023709: pkwalify: autopkgtest regression: t/pkwalify.t Failed: 22

[Paul Gevers]

Source: pkwalify
Version: 1.23-2
Severity: serious
X-Debbugs-CC: jel...@debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of pkwalify the autopkgtest of pkwalify fails in 
testing when that autopkgtest is run with the binary packages of 
pkwalify from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
pkwalify   from testing1.23-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=pkwalify

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pkwalify/27088725/log.gz

t/Kwalify.t .. 1..100
ok 1 - use Kwalify;
ok 2 - use Schema::Kwalify;
ok 3 - sequence of str
ok 4 - sequence with default type (str)
ok 5 - Non valid data, int in sequence of str
ok 6
ok 7 - mapping
ok 8 - invalid mapping
ok 9
ok 10
ok 11
ok 12 - sequence of mapping
ok 13
ok 14
ok 15
ok 16
ok 17 - mapping of sequence
ok 18
ok 19
ok 20
ok 21 - Many rules
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33 - unique
ok 34
ok 35
ok 36
ok 37
ok 38
ok 39 - valid data against schema with recursive rules (no endless loop)
ok 40 - valid recursive data against schema with recursive rules (no 
endless loop)

ok 41 - valid data against perl schema
ok 42 - invalid data against perl schema
ok 43 - min-ex length pass
ok 44 - min-ex length fail
ok 45 - max-ex length pass
ok 46 - max-ex length fail
ok 47 - min-ex range pass
ok 48 - min-ex range fail
ok 49 - max-ex range pass
ok 50 - max-ex range fail
ok 51 - max length pass
ok 52 - max length fail
ok 53 - max range pass
ok 54 - max range fail
ok 55 - Passing name/classname/desc
ok 56 - Passing name/class/desc
ok 57 - a ref is not a text
ok 58 - undef is not a text
ok 59 - a str is not a text
ok 60 - undef is not a str
ok 61 - a number is not a str
ok 62 - a non-float
ok 63 - a non-number
ok 64 - a non-bool
ok 65 - validate '0' as bool
ok 66 - validate '1' as bool
ok 67 - validate 'yes' as bool
ok 68 - validate 'no' as bool
ok 69 - validate 'true' as bool
ok 70 - validate 'false' as bool
ok 71 - validate float
ok 72 - validate number
ok 73 - validate time
ok 74 - schema must be hash
ok 75 - unknown type
ok 76 - invalid length spec
ok 77 - invalid enum spec
ok 78 - invalid range spec
ok 79 - unknown key in type
ok 80 - unknown key in range
ok 81 - unknown key in length
ok 82 - expected hash in data
ok 83 - wrong seq in schema
ok 84 - wrong seq in schema
ok 85 - wrong seq in schema
ok 86 - wrong data, no sequence
ok 87 - wrong map in schema
ok 88 - wrong map in schema
ok 89 - wrong data, undefined
ok 90 - wrong data, no mapping
ok 91 - An object of class 'Schema::Kwalify' isa 'Schema::Kwalify'
ok 92 - Simple Schema::Kwalify validation
ok 93 - Simple Schema::Kwalify failure
ok 94 - type any with additional check, successful
ok 95 - type any with additional check, failure
ok 96 - enum with defined value
ok 97 - enum with undefined value
ok 98 - legally undefined pattern
ok 99 - legally undefined pattern
ok 100 - No warnings expected
ok
t/compat.t ... 1..2
# Running under perl version 5.034000 for linux
# Current time local: Fri Oct 14 22:02:12 2022
# Current time GMT:   Fri Oct 14 22:02:12 2022
# Using Test.pm version 1.31
ok 1
ok 2
ok
t/pkwalify.t . 1..31
not ok 1 - There are warnings in -f 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/schema05.yaml 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/document05a.yaml


#   Failed test 'There are warnings in -f 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/schema05.yaml 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/document05a.yaml'

#   at t/pkwalify.t line 119.
#  got: ''
# expected: anything else
not ok 2 - Nothing in STDERR

#   Failed test 'Nothing in STDERR'
#   at t/pkwalify.t line 119.
#  got: 'Can't open perl script 
"/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/../blib/script/pkwalify": 
No such file or directory

# '
# expected: ''
not ok 3 - -f 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/schema05.yaml 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/document05a.yaml


#   Failed test '-f 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/schema05.yaml 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/document05a.yaml'

#   at t/pkwalify.t line 119.
#  got: '0'
# expected: '1'
# -f 

Bug#1023707: src:cross-toolchain-base: unsatisfied build dependency in testing: linux-source-5.19

[Paul Gevers]

Source: cross-toolchain-base
Version: 61
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023706: src:cross-toolchain-base-mipsen: unsatisfied build dependency in testing: linux-source-5.19

[Paul Gevers]

Source: cross-toolchain-base-mipsen
Version: 21
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:metview: fails to migrate to testing for too long: FTBFS on mips64el and s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.17.0-1
Bug #1023705 [src:metview] src:metview: fails to migrate to testing for too 
long: FTBFS on mips64el and s390x
Marked as fixed in versions metview/5.17.0-1.
Bug #1023705 [src:metview] src:metview: fails to migrate to testing for too 
long: FTBFS on mips64el and s390x
Marked Bug as done
> block -1 by 1022978
Bug #1023705 {Done: Paul Gevers } [src:metview] src:metview: 
fails to migrate to testing for too long: FTBFS on mips64el and s390x
1023705 was not blocked by any bugs.
1023705 was not blocking any bugs.
Added blocking bug(s) of 1023705: 1022978

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

Bug#1023705: src:metview: fails to migrate to testing for too long: FTBFS on mips64el and s390x

[Paul Gevers]

Source: metview
Version: 5.16.0-2
Severity: serious
Control: close -1 5.17.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1022978

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:metview has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on mips64el and s390x where it built successfully in the past. 
Your package is also stuck behind atlas-ecmwf, which I reported in bug 
#1022978.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=metview



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023697: Keep out of testing

[Moritz Muehlenhoff]

Source: wolfssl
Version: 5.2.0-2
Severity: serious

wolfssl has no active maintainer, plenty of open security issues and we already
have too many TLS libraries in our releases. Keep it out of testing. I'm going
to file bugs against the handful of reverse deps.

Cheers,
Moritz

Bug#1021810: Should firefox-esr be dropped on 32bit architectures in bookworm?

[karogyoker999]

Actually, firefox-esr doesn't even work on real x86_32 CPUs (except
Pentium 4) since years.
It requires SSE2 without the sse2-support package, so basically it is
committing a baseline violation on i386.
Currently, due to some random GCC behavior, it doesn't crash instantly
when I try to open any page. But this can change in any upcoming
versions.

There is a fix, but it is not merged since months:
https://salsa.debian.org/mozilla-team/firefox/-/merge_requests/7

If it was merged, it would close the following bugs:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923785
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961663
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009808
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002600
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019246

Alternatively, epiphany-browser could be used instead of firefox-esr
on i386, because that works without SSE or even without MMX.

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Sean Whitton]

Hello Vincent,

Are you able to test the patch?  Let me know if you need help getting an
installable .deb.  Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1023691: pycuda: autopkgtest failure

[Andreas Beckmann]

Control: tag -1 wontfix

On 08/11/2022 20.19, Sebastian Ramacher wrote:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pycuda/28053345/log.gz


pycuda 2022.1~dfsg-5 needs to migrate together with
nvidia-cuda-toolkit 11.6.2-2 - that combination should have working tests


Andreas

Processed: Re: Bug#1023691: pycuda: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #1023691 [src:pycuda] pycuda: autopkgtest failure
Added tag(s) wontfix.

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

Bug#1023654: liburing 2.3 breaks binary compatibility

[Michael Tokarev]

08.11.2022 17:50, Michael Tokarev wrote:

08.11.2022 17:11, Guillem Jover wrote:
[..]

If you are really seeing samba linked against old liburing not working
with the new liburing, then we'd need to dig further to see what else
might be missing, but I'm currently not seeing it just by a very quick
code staring.


Well. I already deleted my test chroot. I can't say for 100% now that it
breaks the other way around. I'll have to double-check.  It took me quite
quite some time especially due to other urgent things I'm doing today.
I can check if 2.2-compiled samba works with 2.3-uring but a bit later
today.  Even if it works, it is not exactly conclusive, since samba only
uses certain code paths.  But ofc if it doesn't work, it *is* conclusive :)


Ok, I double-verified this: samba compiled against older liburing works
with liburing 2.3 after upgrading liburing2 package.  So it must be just
me being too tired when debugging all this.  So it appears to be backwards-
compatible (non-conclusive! ;)), just needs new lib for newly compiled
programs.

It's a rare case really, because of the rather heavy usage of inline
functions for access, - so parts of the library are actually compiled
into the program, and now you've more pieces to keep in sync.

It's an interesting case really.

Thank you!

/mjt

Bug#1011600: marked as done (opencensus-java: FTBFS with OpenJDK 17 due to new compiler warnings)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 19:26:32 +
with message-id 
and subject line Bug#1011600: fixed in opencensus-java 0.24.0+ds-1
has caused the Debian Bug report #1011600,
regarding opencensus-java: FTBFS with OpenJDK 17 due to new compiler warnings
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.)


-- 
1011600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencensus-java
Version: 0.24.0-1
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17


opencensus-java fails to build with OpenJDK 17 because javac is invoked with
the -Werror flag and the compiler now warns that the source/target level 7
will be removed in a future release.


Compiling with JDK Java compiler API.
warning: [options] source value 7 is obsolete and will be removed in a 
future release
warning: [options] target value 7 is obsolete and will be removed in a 
future release
warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
error: warnings found and -Werror specified
:opencensus-api:compileJava FAILED
:opencensus-api:compileJava (Thread[Task worker for ':' Thread 
4,5,main]) completed. Took 0.748 secs.


Bumping the source level to 8 and removing the -Werror flag would be a good 
idea.
--- End Message ---
--- Begin Message ---
Source: opencensus-java
Source-Version: 0.24.0+ds-1
Done: Olek Wojnar 

We believe that the bug you reported is fixed in the latest version of
opencensus-java, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated opencensus-java 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: Tue, 08 Nov 2022 12:33:20 -0500
Source: opencensus-java
Architecture: source
Version: 0.24.0+ds-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Olek Wojnar 
Closes: 1011600
Changes:
 opencensus-java (0.24.0+ds-1) unstable; urgency=high
 .
   * Refresh packaging
   * Update standards to 4.6.1 (no changes)
   * Build with source level 8 to eliminate warning (Closes: #1011600)
   * Refresh and document modified upstream source
Checksums-Sha1:
 daa2a406178b4d55cab6311836674d67389951d8 2518 opencensus-java_0.24.0+ds-1.dsc
 e452231c47e8834f67fd1d404f413b3dbe0800f0 681192 
opencensus-java_0.24.0+ds.orig.tar.xz
 8e4371b47291672a91dfbf208f8457c94f312849 5416 
opencensus-java_0.24.0+ds-1.debian.tar.xz
 7732e6585950703c442f0f7e6401b8cc3d212847 17304 
opencensus-java_0.24.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 71cba79148a6e5cb88fc95cb31f883c062d9fcd2a85af50915531538cf88cf75 2518 
opencensus-java_0.24.0+ds-1.dsc
 734851072fa1cfc3103e9b2730515eec1e6cf23b5d9b83bbe526c14c4c29f9f1 681192 
opencensus-java_0.24.0+ds.orig.tar.xz
 fc0f65501e290b5315764fdf8f5c8aeed2cfdc723ac2d7e9be07e597598ac5e5 5416 
opencensus-java_0.24.0+ds-1.debian.tar.xz
 b5b71f36ea989766a81866dff72e7ba2675ca0399a44ea8712c6d44cfd2fad53 17304 
opencensus-java_0.24.0+ds-1_amd64.buildinfo
Files:
 4b60577e632ff3536e422518b8522e42 2518 java optional 
opencensus-java_0.24.0+ds-1.dsc
 0cb04fd3a119db9d8b13d1ae5a5b5255 681192 java optional 
opencensus-java_0.24.0+ds.orig.tar.xz
 2c9bb48b3ef68994db69bf32e71089f5 5416 java optional 
opencensus-java_0.24.0+ds-1.debian.tar.xz
 933806994c79454c2337a067d5cb2903 17304 java optional 
opencensus-java_0.24.0+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNqpPMACgkQfYPUBqCd
weSsnBAAhiTtz6ciEFNx5M2cDUOcBhPa5EcztwSSpBAeKFkFRJh3c8gOpuO+RavA
TedSP6NaFzbAVBK9b0/zDLHVZMvG15cLA+kHRHAygGHiHw3OVOdB78wZybLMPOa8
Lc7g/b97q/pnSt2jV9Jm+za+IraHhg/SbHLYNt4SkoCJDg14lPbzTcHQ0JprqNB7
g67QFoZbOXL2ulaxvt1Eud0SvzkAn5//u6xAcvcmuv4NIe8MtMfiLu3T231clouL
xvT3PEwCL0hDO7F9WCiAFNmJPpgJiloHX3uv5IkZ+z1B4v+XFNQaUeIGV35J/XKw
7jx6BIfOO52vm0h1I1NhwLanVK1aX7QPIUNQrNzo62aKKtnGXWz8fufwT9d+IqP+
IzdtNR/0ar9wOJI4UjQ4NmRRnxOFvmRTLefDrnpgKrOh/MzQxvew+tvmJZpl70hg

Bug#1023691: pycuda: autopkgtest failure

[Sebastian Ramacher]

Source: pycuda
Version: 2022.1~dfsg-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pycuda/28053345/log.gz

emoving autopkgtest-satdep (0) ...
autopkgtest [05:23:44]: test compile-stl-headers_g++-11: 
debian/tests/compile-stl-headers g++-11
autopkgtest [05:23:44]: test compile-stl-headers_g++-11: 
[---
algorithm
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not 
expanded with ‘...’:
  435 | function(_Functor&& __f)
  | 
^ 
/usr/include/c++/11/bits/std_function.h:435:145: note: ‘_ArgTypes’
/usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not 
expanded with ‘...’:
  530 | operator=(_Functor&& __f)
  | 
 ^ 
/usr/include/c++/11/bits/std_function.h:530:146: note: ‘_ArgTypes’
FAIL: algorithm
any
array
atomic
barrier
bit
bitset
cassert
ccomplex
cctype
cerrno
cfenv
cfloat
charconv
chrono
cinttypes
ciso646
climits
clocale
cmath
codecvt
compare
complex
complex.h
concepts
condition_variable
coroutine (may fail)
/usr/include/c++/11/coroutine:294:23: error: default member initializer for 
‘std::__n4861::coroutine_handle::__frame::__r’
 required before the end of its enclosing class
  294 |   static __frame _S_fr;
  |   ^
/usr/include/c++/11/coroutine:289:26: note: defined here
  289 | void (*__r)() = __dummy_resume_destroy;
  |  ^~   
/usr/include/c++/11/coroutine:294:23: error: default member initializer for 
‘std::__n4861::coroutine_handle::__frame::__d’
 required before the end of its enclosing class
  294 |   static __frame _S_fr;
  |   ^
/usr/include/c++/11/coroutine:290:26: note: defined here
  290 | void (*__d)() = __dummy_resume_destroy;
  |  ^~   
/usr/include/c++/11/coroutine:304:60: error: redefinition of 
‘std::__n4861::coroutine_handle::__frame 
std::__n4861::coroutine_handle::_S_fr’
  304 |   noop_coroutine_handle::_S_fr{};
  |^

/usr/include/c++/11/coroutine:294:23: note: 
‘std::__n4861::coroutine_handle::__frame 
std::__n4861::coroutine_handle::_S_fr’ 
previously declared here
  294 |   static __frame _S_fr;
  |   ^
Ignored failure: coroutine
csetjmp
csignal
cstdalign
cstdarg
cstdbool
cstddef
cstdint
cstdio
cstdlib
cstring
ctgmath
ctime
cuchar
cwchar
cwctype
cxxabi.h
deque
exception
execution
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not 
expanded with ‘...’:
  435 | function(_Functor&& __f)
  | 
^ 
/usr/include/c++/11/bits/std_function.h:435:145: note: ‘_ArgTypes’
/usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not 
expanded with ‘...’:
  530 | operator=(_Functor&& __f)
  | 
 ^ 
/usr/include/c++/11/bits/std_function.h:530:146: note: ‘_ArgTypes’
FAIL: execution
fenv.h
filesystem
forward_list
fstream
functional
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not 
expanded with ‘...’:
  435 | function(_Functor&& __f)
  | 
^ 
/usr/include/c++/11/bits/std_function.h:435:145: note: ‘_ArgTypes’
/usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not 
expanded with ‘...’:
  530 | operator=(_Functor&& __f)
  | 
 ^ 
/usr/include/c++/11/bits/std_function.h:530:146: note: ‘_ArgTypes’
FAIL: functional
future
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not 
expanded with ‘...’:
  435 | function(_Functor&& __f)
  | 
^ 
/usr/include/c++/11/bits/std_function.h:435:145: note: ‘_ArgTypes’
/usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not 
expanded with ‘...’:
  530 | operator=(_Functor&& __f)
  |   

Bug#1023689: minilla: FTBFS: test failures with git 1:2.38.1-1 : transport 'file' not allowed

[Niko Tyni]

Source: minilla
Version: 3.1.18-1
Severity: serious
Tags: ftbfs

This package fails to build from source on current sid.

   Test Summary Report
   ---
   t/filegatherer.t   (Wstat: 65280 (exited 255) Tests: 
2 Failed: 1)
 Failed test:  2
 Non-zero exit status: 255
 Parse errors: No plan found in TAP output
   t/filegatherer/submodules-recursive.t  (Wstat: 65280 (exited 255) Tests: 
2 Failed: 1)
 Failed test:  2
 Non-zero exit status: 255
 Parse errors: No plan found in TAP output
   t/project/in_submodule.t   (Wstat: 65280 (exited 255) Tests: 
1 Failed: 1)
 Failed test:  1
 Non-zero exit status: 255
 Parse errors: No plan found in TAP output
   Files=62, Tests=170, 105 wallclock secs ( 0.42 usr  0.08 sys + 44.82 cusr 
11.18 csys = 56.50 CPU)
   Result: FAIL
 
The build log is rather hard to read as there are intentional test
failures sprayed all over, but I think the main thing that is new is
messages like this:

  Cloning into '/tmp/uGVjCBrSr3/libfoo'...
  fatal: transport 'file' not allowed
  fatal: clone of 'file:///tmp/hhqN4NFWJc' into submodule path 
'/tmp/uGVjCBrSr3/libfoo' failed

I've tested that building in bookworm succeeds, but injecting
git_1%3a2.38.1-1_amd64.deb (and git-man_1%3a2.38.1-1_all.deb) makes it
fail. I assume this is about

  https://security-tracker.debian.org/tracker/CVE-2022-39253

which was fixed in git 1:2.38.1-1.
-- 
Niko Tyni   nt...@debian.org

Bug#1023457: marked as done (sundials: FTBFS against hypre 2.26 and petsc 3.18)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 19:10:18 +
with message-id 
and subject line Bug#1023457: fixed in sundials 6.4.1+dfsg-1
has caused the Debian Bug report #1023457,
regarding sundials: FTBFS against hypre 2.26 and petsc 3.18
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.)


-- 
1023457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sundials
Version: 5.8.0+dfsg-1
Severity: serious
Justification: FTBFS
Control: affects -1 libhypre-dev libpetsc-real3.18-dev

Testing the build of sundials against Hypre 2.6 and PETSc 3.18, both
available now in experimental, nvector/parhyp fails with the error
message:

[ 55%] Linking C executable ark_diurnal_kry_ph
cd 
/home/drew/projects/misc/build/sundials-5.8.0+dfsg/debian/build/examples/arkode/C_parhyp
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/ark_diurnal_kry_ph.dir/link.txt --verbose=1
/usr/bin/mpicc -fcommon -Wl,-z,relro -Wl,-z,now 
CMakeFiles/ark_diurnal_kry_ph.dir/ark_diurnal_kry_ph.c.o -o ark_diurnal_kry_ph  
-Wl,-rpath,/home/drew/projects/misc/build/sundials-5.8.0+dfsg/debian/build/src/arkode:/home/drew/projects/misc/build/sundials-5.8.0+dfsg/debian/build/src/nvector/parhyp
 ../../../src/arkode/libsundials_arkode.so.4.8.0 
../../../src/nvector/parhyp/libsundials_nvecparhyp.so.5.8.0 -lm 
/usr/lib/x86_64-linux-gnu/librt.a -lHYPRE -lHYPRE 
In file included from 
/usr/lib/petscdir/petsc3.18/x86_64-linux-gnu-real/include/petscsys.h:1274,
 from 
/usr/lib/petscdir/petsc3.18/x86_64-linux-gnu-real/include/petscvec.h:9,
 from 
/usr/lib/petscdir/petsc3.18/x86_64-linux-gnu-real/include/petscmat.h:7,
 from 
/usr/lib/petscdir/petsc3.18/x86_64-linux-gnu-real/include/petscdm.h:6,
 from 
/home/drew/projects/misc/build/sundials-5.8.0+dfsg/examples/arkode/C_petsc/ark_petsc_ex25.c:32:
/home/drew/projects/misc/build/sundials-5.8.0+dfsg/examples/arkode/C_petsc/ark_petsc_ex25.c:
 In function ‘main’:
/usr/lib/petscdir/petsc3.18/x86_64-linux-gnu-real/include/petscoptions.h:182:5: 
error: expected expression before ‘do’
  182 | do { \
  | ^~
/home/drew/projects/misc/build/sundials-5.8.0+dfsg/examples/arkode/C_petsc/ark_petsc_ex25.c:112:10:
 note: in expansion of macro ‘PetscOptionsBegin’
  112 |   ierr = PetscOptionsBegin(PETSC_COMM_WORLD,NULL,"Advection-reaction 
options","");
  |  ^


Actually the error is specifically triggered from petscoptions.h, so
perhaps the problem is in petsc 3.18 not sundials. And line 182 in
petscoptions.h does look malformed.  We'll close or move this bug
to petsc if that proves to be the source of the problem. Might have to
check the petsc source repo upstream.



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

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: sundials
Source-Version: 6.4.1+dfsg-1
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
sundials, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated sundials 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: Mon, 07 Nov 2022 16:37:01 +0100
Source: sundials
Binary: libsundials-arkode5 libsundials-arkode5-dbgsym libsundials-cvode6 
libsundials-cvode6-dbgsym libsundials-cvodes6 libsundials-cvodes6-dbgsym 
libsundials-dev libsundials-fortran-dev libsundials-ida6 
libsundials-ida6-dbgsym libsundials-idas5 libsundials-idas5-dbgsym 
libsundials-kinsol6 libsundials-kinsol6-dbgsym libsundials-nvecparallel-hypre6 

Bug#1023688: improper permissions on fcgiwrap systemd socket lead to privilege escalation to www-data under default config

[Anton Luka Šijanec]

Package: fcgiwrap
Version: 1.1.0-12
Severity: critical
Tags: patch, security

On a default installation of Debian 11 (bullseye) with other releases probably 
also affected, systemd socket file /lib/systemd/system/fcgiwrap.socket from 
package fcgiwrap contains no Mode= configuration parameter, making systemd pick 
the default 0666. The socket is therefore world accessible and any user on the 
system may, when package fcgiwrap is installed, elevate privileges and execute 
code as www-data user by communicating with the socket via fastcgi protocol. 
www-data is specified as User= and Group= in 
/lib/systemd/system/fcgiwrap.service, also supplied by package fcgiwrap.

Proof of concept terminal recording: http://upload.sijanec.eu/f.mp4

Solution: add SocketMode=0660, SocketUser=www-data, Group=www-data to 
/lib/systemd/system/fcgiwrap.socket --- this would, however, break existing 
configurations that rely on /run/fcgiwrap.socket being world connectable.

Is this intended behaviour? Doesn't it break user's expectations, as suddenly 
everyone can influence httpd (nginx slaves also run under www-data, for 
example)?

- BEGIN PATCH -
Author: Anton Luka Šijanec 
Description: Modify default user/group and listening mode of socket
Forwarded: no

--- a/systemd/fcgiwrap.socket
+++ b/systemd/fcgiwrap.socketfixed
@@ -3,6 +3,9 @@ Description=fcgiwrap Socket

 [Socket]
 ListenStream=/run/fcgiwrap.sock
+Mode=0660
+SocketUser=www-data
+SockerGroup=www-data

 [Install]
 WantedBy=sockets.target
- END PATCH -

Attachments:
root@host:~# ls -lah /run/fcgiwrap.socket
srw-rw-rw- 1 root root 0 Nov  8 19:42 /run/fcgiwrap.socket

=> /lib/systemd/system/fcgiwrap.socket
[Unit]
Description=fcgiwrap Socket

[Socket]
ListenStream=/run/fcgiwrap.socket

[Install]
WantedBy=sockets.target



=> /lib/systemd/system/fcgiwrap.service
[Unit]
Description=Simple CGI Server
After=nss-user-lookup.target
Requires=fcgiwrap.socket

[Service]
Environment=DAEMON_OPTS=-f
EnvironmentFile=-/etc/default/fcgiwrap
ExecStart=/usr/sbin/fcgiwrap ${DAEMON_OPTS}
User=www-data
Group=www-data

[Install]
Also=fcgiwrap.socket

-- 
Anton Luka Šijanec 
F4C3E3A4DFB7254397A9F993E76135F49802CD14
http://splet.sijanec.eu/pgp-key.txt

Processed: block 1023666 with 1008979 994108 978511 1022184 1008981 1022181 1022180

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1023666 with 1008979 994108 978511 1022184 1008981 1022181 1022180
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023678 1023679 1023677 1023681 1023682 1023671 1023687 
1023684 1023674
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1022184, 978511, 1008979, 1022181, 1022180, 
1008981, and 994108
> thanks
Stopping processing here.

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

Processed: simde build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023681 1023671 1023679 1023677 1023682 1023674 1023684 
1023678
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023687
> close -1 0.7.3~0git20210929204341.90523a2-1
Bug #1023687 [src:simde] simde build depends on gcc-10 that should not be in 
bookworm
Marked as fixed in versions simde/0.7.3~0git20210929204341.90523a2-1.
Bug #1023687 [src:simde] simde build depends on gcc-10 that should not be in 
bookworm
Marked Bug as done

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

Bug#1023687: simde build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: simde
Version: 0.7.2-6
Severity: serious
Control: block 1023666 by -1
Control: close -1 0.7.3~0git20210929204341.90523a2-1

This is already fixed in experimental.

Bug#1023686: readline: Inaccurate copyright file

[Bastian Germann]

Source: readline
Version: 8.2-1.1
Severity: serious
Tags: patch

The debian/copyright file is missing some information (copyright statements and 
at least one license).
I have put together and attached machine-readable versions of the two copyright 
files with added info.

You should repack to get rid of the embedded rlwrap copy and the non-source doc 
files (#1023683),
which would simplify maintaining the copyright files.

The licenses of the embedded fonts are not included in the attached copyright 
file.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment:
This is Debian GNU/Linux's prepackaged version of the FSF's GNU
Readline library.
 .
This package was put together by Matthias Klose ,
derived from the bash package by Guy Maor .
Upstream-Name: Readline
Upstream-Contact: 
Chet Ramey 
Jeff Solomon  (examples/excallback.c)
Harold Levy  (examples/rl-fgets.c)
Source: http://ftp.gnu.org/gnu/readline/

Files: *
Copyright:
Copyright (C) 1987-2022 Free Software Foundation, Inc.
License: GPL-3+
Readline 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.
 .
This package is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
 .
You should have received a copy of the GNU General Public License
along with Readline.  If not, see .
Comment:
 On Debian systems, the complete text of the GNU General Public License
 version 3 can be found in `/usr/share/common-licenses/GPL-3'.

Files: examples/readlinebuf.h
   examples/rl-fgets.c
   examples/rlfe/*
   examples/rlwrap-*.tar.gz
Copyright:
Copyright (C) 1987-2022 Free Software Foundation, Inc.
Copyright (c) 2001 by Dimitris Vyzovitis [v...@media.mit.edu]
Copyright (C) 1999 Jeff Solomon (examples/excallback.c)
Copyright (C) 2003-2004 Harold Levy (examples/rl-fgets.c)
Copyright (c) 1993-2002 Juergen Weigert 
(jnwei...@immd4.informatik.uni-erlangen.de)
Copyright (c) 1993-2002 Michael Schroeder 
(mlsch...@immd4.informatik.uni-erlangen.de)
Copyright (C) 1987 Oliver Laumann (examples/rlfe)
Copyright (C) 2004, 1999 Per Bothner
Copyright (C) 2000-2007 Hans Lub
Copyright (C) 1999-2001 Geoff Wing
Copyright (C) Damian Ivereigh 2000
License: GPL-2+
This program 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 2, or (at your option)
any later version.
 .
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
 .
You should have received a copy of the GNU General Public License
along with this program (see the file COPYING); if not, write to the
Free Software Foundation, Inc.,
59 Temple Place - Suite 330, Boston, MA  02111-1307, USA
Comment:
 On Debian systems, the complete text of the GNU General Public License
 version 2 can be found in `/usr/share/common-licenses/GPL-2'.
 .
 The rlwrap example is also available in its own Debian package.
 The code copyrighted by Damian Ivereigh is licensed under LGPL-2.1+.

Files: doc/*.texi doc/*.info doc/*.html doc/*.[03] doc/*.dvi doc/*.pdf doc/*.ps
Copyright:
Copyright (C) 1988-2015 Free Software Foundation, Inc.
License: GFDL-NIV-1.3+
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, no Front-Cover Texts, and
no Back-Cover Texts.  A copy of the license is included in the
section entitled "GNU Free Documentation License".
Comment:
 On Debian systems, the complete text of the GNU Free Documentation
 License can be found in `/usr/share/common-licenses/GFDL'.

Files: support/wcwidth.c
Copyright: Markus Kuhn
License: ISC-no-attribution
 Permission to use, copy, modify, and distribute this software
 for any purpose and without fee is hereby granted. The author
 disclaims all warranties with regard to this software.

Files: debian/*
Copyright:
Copyright (C) 1999-2009 Matthias Klose 
License: GPL-3
 The Debian packaging is licensed under the GPL version 3, 
 see `/usr/share/common-licenses/GPL-3'.
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment:
This is Debian GNU/Linux's prepackaged version of the rlfe program.
This package was put together 

Bug#1023685: libdancer-perl: FTBFS: 10_error_dumper_without_clone.t failure

[Niko Tyni]

Source: libdancer-perl
Version: 1.3513+dfsg-1
Severity: serious
Tags: ftbfs sid bookworm
Control: affects -1 libhttp-message-perl

This package fails to build from source on current sid.

   t/12_response/10_error_dumper.t . 
   1..5
   ok 1 - An object of class 'Dancer::Error' isa 'Dancer::Error'
   ok 2 - Data was censored in the output
   ok 3 - Original data was not overwritten
   ok 4 - Censoring of complex data structures works fine
   ok 5 - recursive censored hash
   ok
   Devel::Hide hides Clone.pm
   Can't locate Clone.pm in @INC (hidden)
   BEGIN failed--compilation aborted at /usr/share/perl5/HTTP/Headers.pm line 8.
   Compilation failed in require at 
/<>/blib/lib/Dancer/Response.pm line 14.
   BEGIN failed--compilation aborted at 
/<>/blib/lib/Dancer/Response.pm line 14.
   Compilation failed in require at 
/<>/blib/lib/Dancer/SharedData.pm line 8.
   BEGIN failed--compilation aborted at 
/<>/blib/lib/Dancer/SharedData.pm line 8.
   Compilation failed in require at /<>/blib/lib/Dancer/Request.pm 
line 13.
   BEGIN failed--compilation aborted at 
/<>/blib/lib/Dancer/Request.pm line 13.
   Compilation failed in require at /<>/blib/lib/Dancer/Route.pm 
line 13.
   BEGIN failed--compilation aborted at 
/<>/blib/lib/Dancer/Route.pm line 13.
   Compilation failed in require at 
/<>/blib/lib/Dancer/Route/Registry.pm line 8.
   BEGIN failed--compilation aborted at 
/<>/blib/lib/Dancer/Route/Registry.pm line 8.
   Compilation failed in require at /<>/blib/lib/Dancer/App.pm 
line 12.
   BEGIN failed--compilation aborted at /<>/blib/lib/Dancer/App.pm 
line 12.
   Compilation failed in require at /<>/blib/lib/Dancer.pm line 10.
   BEGIN failed--compilation aborted at /<>/blib/lib/Dancer.pm 
line 10.
   Compilation failed in require at 
t/12_response/10_error_dumper_without_clone.t line 17.
   BEGIN failed--compilation aborted at 
t/12_response/10_error_dumper_without_clone.t line 17.
   t/12_response/10_error_dumper_without_clone.t ... 
   Dubious, test returned 255 (wstat 65280, 0xff00)
   No subtests run 
 
I assume this broke with libhttp-message-perl 6.44-1, which is currently
blocked from migrating to testing due to a similar autopkgtest regression.

>From the upstream HTTP-Message changelog:

  Changes for version 6.44 - 2022-10-26
  
  - Made the Clone module a hard requirement, so we don't have to provide
a fallback function for HTTP::Headers::clone(). We require at least
Clone 0.46, as that release now supports Perl back to 5.8.1, just like
us. (GH#184) (Neil Bowers)
  - Import clone from Clone rather than inheriting (GH#189) (Graham Knop)

Looking at the above, my guess is that the Dancer test which "hides
Clone.pm" needs to be updated, as it uses HTTP::Headers which now
requires Clone.
-- 
Niko Tyni   nt...@debian.org

Processed: severity of 1022180 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1022180 serious
Bug #1022180 [shim] shim: non-standard gcc used for build (gcc-10)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1022181 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1022181 serious
Bug #1022181 [src:pygccjit] pygccjit: non-standard gcc used for build (gcc-10)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: libdancer-perl: FTBFS: 10_error_dumper_without_clone.t failure

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libhttp-message-perl
Bug #1023685 [src:libdancer-perl] libdancer-perl: FTBFS: 
10_error_dumper_without_clone.t failure
Added indication that 1023685 affects libhttp-message-perl

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

Processed: odb build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023671 1023677 1023682 1023679 1023674 1023681 1023678
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023684

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

Bug#1023684: odb build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: odb
Version: 2.4.0-15
Severity: serious
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.

Processed: severity of 1022184 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1022184 serious
Bug #1022184 [src:grub2] grub2: Update compiler version (currently: gcc-10)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: gringo build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023674 1023671 1023679 1023681 1023678 1023677
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023682

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

Bug#1023682: gringo build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: gringo
Version: 5.4.1-3
Severity: serious
Tags: bookworm sid
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.

Processed: ghdl build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023674 1023678 1023679 1023671 1023677
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023681

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

Bug#1023681: ghdl build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: ghdl
Version: 1.0.0+dfsg-8
Severity: serious
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.

Bug#967010: apache2: Did not reporoduce

[Shai Berger]

Hi,

On Tue, 08 Nov 2022 18:05:23 +0100
"Yadd"  wrote:

> 
> Hi, it's a Buster-only bug, not a Bullseye's one
> 

It was flagged by apt-listbugs on my bookworm/sid system.

Processed: gcc-mingw-w64 build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023674 1023678 1023671 1023677
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023679

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

Bug#1023679: gcc-mingw-w64 build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: gcc-mingw-w64
Version: 24.4
Severity: serious
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.

Bug#1023678: clasp build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: clasp
Version: 3.3.5-4.1
Severity: serious
Control: block 1023666 by -1

Please use the default gcc if possible,
or switch to gcc-12 that is default in bookworm.

Processed: clasp build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023677 1023671 1023674
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023678

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

Processed: bart-cuda build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023674 1023671
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023677

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

Bug#1023677: bart-cuda build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: bart-cuda
Version: 0.8.00-1
Severity: serious
Control: block 1023666 by -1

According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016625#65
gcc-11 might be a temporary workaround (but it might be only gcc-12 that
will be in bookworm).

Bug#1023674: astra-toolbox build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Source: astra-toolbox
Version: 2.1.0-1
Severity: serious
Control: block 1023666 by -1

#1003037 might contain some background information on how to fix this.

Processed: astra-toolbox build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was blocked by: 1023671
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023674

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

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Pavel Odintsov]

Hello!

I think I have one more question.

For most of the platforms we support libbpf 1.0.1 works fine but I noticed
issues with Debian 11 and Ubuntu 20 about enum declarations:

In file included from
/tmp/fastnetmon.build.dir.i2Ak87Hs7Y/fastnetmon/src/xdp_plugin/xdp_collector.cpp:14:
/opt/fastnetmon-community/libraries/libbpf_1_0_1/include/bpf/bpf.h:396:6:
error: use of enum 'bpf_stats_type' without previous declaration
  396 | enum bpf_stats_type; /* defined in up-to-date linux/bpf.h */
  |  ^~
/opt/fastnetmon-community/libraries/libbpf_1_0_1/include/bpf/bpf.h:397:38:
error: use of enum 'bpf_stats_type' without previous declaration
  397 | LIBBPF_API int bpf_enable_stats(enum bpf_stats_type type);
  |  ^~
In file included from
/tmp/fastnetmon.build.dir.i2Ak87Hs7Y/fastnetmon/src/xdp_plugin/xdp_collector.cpp:15:
/opt/fastnetmon-community/libraries/libbpf_1_0_1/include/bpf/libbpf.h:70:54:
error: use of enum 'bpf_link_type' without previous declaration
   70 | LIBBPF_API const char *libbpf_bpf_link_type_str(enum bpf_link_type
t);
  |  ^~~~

Did you experience similar errors previously by any chance?

Thank you!


On Tue, 8 Nov 2022 at 16:55, Pavel Odintsov 
wrote:

> Hello!
>
> Added copy to all.
>
> I think I fixed it with these commits:
> https://github.com/pavel-odintsov/fastnetmon/commit/c48497a6f109fc1a9f5da596b055c3b7cffb96d4
> and
> https://github.com/pavel-odintsov/fastnetmon/commit/c718e88d0b25dcfbd724e9820f592fd5782eca6c
>
> I've used
> https://lore.kernel.org/bpf/20220202225916.3313522-7-and...@kernel.org/
> and
> https://lxr.missinglinkelectronics.com/linux+v5.19/samples/bpf/xdp1_user.c
> as examples as this code was my reference during implementation.
>
> Would be great if you could review it a second time.
>
> Thank you!
>
> On Mon, 7 Nov 2022 at 11:59, Sudip Mukherjee 
> wrote:
>
>> Hi Pavel,
>>
>> On Mon, Nov 7, 2022 at 11:53 AM Pavel Odintsov 
>> wrote:
>> >
>> > Hello!
>> >
>> > Thank you for reaching me.
>> >
>> > Sure, I'll be happy to check.
>> >
>> > May I kindly ask what exactly changed to trigger these errors? I
>> believe it was successfully built previously.
>>
>> Its the update of libbpf to v1.0.1 which removed some of the deprecated
>> API.
>>
>>
>> --
>> Regards
>> Sudip
>>
>
>
> --
> Sincerely yours, Pavel Odintsov
>


-- 
Sincerely yours, Pavel Odintsov

Processed: afl++ silently drops gcc_plugin support when gcc-X-plugin-dev build dependency not on the default gcc

[Debian Bug Tracking System]

Processing control commands:

> block 1023666 by -1
Bug #1023666 [gcc-10] gcc-10 should not be shipped in bookworm
1023666 was not blocked by any bugs.
1023666 was not blocking any bugs.
Added blocking bug(s) of 1023666: 1023671

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

Bug#1023671: afl++ silently drops gcc_plugin support when gcc-X-plugin-dev build dependency not on the default gcc

[Adrian Bunk]

Package: afl++
Version: 4.02c-1
Severity: serious
Control: block 1023666 by -1

https://buildd.debian.org/status/fetch.php?pkg=aflplusplus=amd64=4.02c-1=1662644587=0

...
[*] Checking for gcc plugin development header files...
[-] Oops, can't find gcc header files. Be sure to install 'gcc-X-plugin-dev'.
make[3]: *** [GNUmakefile.gcc_plugin:125: test_deps] Error 1
...


This should be an error, which would then result in someone updating
the build dependency when the default gcc changes.

Bug#999296: marked as done (tagcloud: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 17:09:42 +
with message-id 
and subject line Bug#999296: fixed in tagcloud 1.4-1.3
has caused the Debian Bug report #999296,
regarding tagcloud: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tagcloud
Version: 1.4-1.2
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: tagcloud
Source-Version: 1.4-1.3
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
tagcloud, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated tagcloud 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: Sun, 06 Nov 2022 13:35:39 -0300
Source: tagcloud
Architecture: source
Version: 1.4-1.3
Distribution: unstable
Urgency: medium
Maintainer: Runa Sandvik 
Changed-By: Marcos Talau 
Closes: 999296
Changes:
 tagcloud (1.4-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep} (Closes: #999296).
Checksums-Sha1:
 fb0842a74bea195cf7842d7bf29c504e8fe4e928 1688 tagcloud_1.4-1.3.dsc
 9cec77ac616d83594526504c36f1d8184aef0b1e 1837 tagcloud_1.4-1.3.diff.gz
 b1fa24d1ca6fa6fb569ab21edf044855ade483b7 5809 tagcloud_1.4-1.3_source.buildinfo
Checksums-Sha256:
 19c2cf84ab0ac69103ccf76b2a69dc40ac943d08bf5c616e09daa6612e44f521 1688 
tagcloud_1.4-1.3.dsc
 7fae7c6904bd389a74fa2736771020d6cb6e685c54bfe557afd4a7c620c6a0fd 1837 
tagcloud_1.4-1.3.diff.gz
 77f4db90f802d68ad134699970306f478db9c119030128a158cc2452ac3360ae 5809 
tagcloud_1.4-1.3_source.buildinfo
Files:
 a60e5f3d4e7ccd770b5b1a7a15fc422a 1688 perl optional tagcloud_1.4-1.3.dsc
 925319e8019e2707a8afa1e5bbbee782 1837 perl optional tagcloud_1.4-1.3.diff.gz
 84e6d1f7584be98085569ffe73d9abc7 5809 perl optional 
tagcloud_1.4-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn4qgACgkQ9LqqgNso
ukxgbQ//RntR1dPJvhchlc/CITbTmtmqa0F9hHRU13HU2bpakrppkK12LBv4yFBr
O290GgqtN6q3cvSgZZcnjHASpP71CaV+IPvdz1v4Z6MmZACB+cTTGlyMGP9WiAvU
586fARSco877FdjHPesxPowU+Nl54iv/+KIw5suSE1UEvGftA1OMJX5j3SQs0EEa
SLDUpViZGjx+Hy03kE4cnDlwj9ixhLhDMptW1vSaYqU8MS/pOuVIa1ukmINTQWDZ
et7SeBZuu7uE9f8MiF6uTQbnGhfXwKf9pDI4cirB5U1rvRdTRD8+HLmx3d3au07D
ewdH1ogCWuw7O5XRaQc1kJAy/CY8UjXwXC5YK8wVF5cHzhw5pon+WHhhT28IWWmt
w6QmBfIPURnHunUnM0yB33K09LBRpKur/coxSWt4hHz8x+TD1UO/W3w3u/BIdZ9g
kJZDqvrQ+C329pFSfENilqck1Uy0H7VjDwqGWaD6vEZZVPNB3xgMeBlmDp33hu3g
gAIznHzviZ9BHDkYlEryqxSnjmkvoA2GcY5m6o18F1O1sb6dkRFO203TvfA+2MZD
DzKnxpdKNAqETJl+NDXCUD+J6skmU7qM52sWDOqb0hudwibPFvcNCyJxDOTcnTuW
rKZ5bNnMALShnfg1BWFn76v5oyYPRsxvbvKWrVBNiKMFQ/Q2zyc=
=NcJk
-END PGP SIGNATURE End Message ---

Bug#998965: marked as done (spew: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 17:09:17 +
with message-id 
and subject line Bug#998965: fixed in spew 1.0.8-1.1
has caused the Debian Bug report #998965,
regarding spew: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
998965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spew
Version: 1.0.8-1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: spew
Source-Version: 1.0.8-1.1
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
spew, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated spew 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: Sun, 06 Nov 2022 13:31:22 -0300
Source: spew
Architecture: source
Version: 1.0.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matt Taggart 
Changed-By: Marcos Talau 
Closes: 998965
Changes:
 spew (1.0.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep} (Closes: #998965).
Checksums-Sha1:
 1eaefac701c45f78249ac3f8705b5d3bf8883133 1653 spew_1.0.8-1.1.dsc
 22e8034ebe78f1309c59cb5b9c295d9a6585cf4a 39549 spew_1.0.8-1.1.diff.gz
 7bb25a7d1ff5199c715e31acf6dd0af7bace399e 5961 spew_1.0.8-1.1_source.buildinfo
Checksums-Sha256:
 c4caa9de220b055ec640e93ecde3f132c162d319621ee8817f63023914bd 1653 
spew_1.0.8-1.1.dsc
 7852720db4826b5502d3f716cbde5ede506e63f76510840cc586b0b7e1c68476 39549 
spew_1.0.8-1.1.diff.gz
 03cff6845210d74fab8bd6210ce935b8081b69a5fd491a1d84579a1b33aadc8f 5961 
spew_1.0.8-1.1_source.buildinfo
Files:
 bc5f0887cae930c52e5d0226b5f809de 1653 utils extra spew_1.0.8-1.1.dsc
 d1aa7a693f6238a3ab98930443a82c75 39549 utils extra spew_1.0.8-1.1.diff.gz
 6d1b91ba47949fe32d9534a5968e2ac9 5961 utils extra 
spew_1.0.8-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn4g0ACgkQ9LqqgNso
ukxfGg//TZtzhFbtfEpI+edBUM9AyntPekIOSb0TrsSiLyWOObo78gNhkU1D/kuc
fqLNnhosGRg7Lh6E1I7YB2s9HAnO6c5efbZ2/sjhWeJ1PEPsPBr/Obj/rPi3gDSJ
7Cc6vVTihQfjU2x3gp9YeyN5jshHzBXoJHsA9i/X5hVZFzqNKre50mP9Ruq9fAdX
OkbV6OoxdcrxgRhyvT8hXVMeHHAq/grkj/0mvnLUJhRvpIglAspsoHWvFRHyILRb
9mkvgwMFTGA4iJi4y2ZkBLPE7EKi7hSGvTxJGmpFnqz3ePhx80MuGoYwOLfJVRjN
0DFpDj5rWN4/MLOYAdq7vcHt0HDsp9dCDXgMp+b5IXT33g1iEL2LevWiZoWi+oHb
g4HS0Kif0I1uToB6Hfkj7C3v3Tv9bzAnJrZvuFQx4Rws/9ysiLizknQMsVChMtzW
MHoPqyDnJ3ZhIIShVZraCNsd1BMcmfPfyu/K9EHAQm2zgHlaWQgudn+bet+CWIRg
NAlbFBTiCGpRX+1EJXWmX7vM7f1nGgAvCXJ7+unkTFNFIRZhHy7aG7z7shmvjvux
yoO/b/Z3VWc0pPBcEccXlj5T7MXOhqNJAUvxRj1dP57fBmDOYWPnvPtaiBJTl1IK
JS3tQvhR0iCVSRQ9ICMzBQD10dkuNh7e59rOgHF7BUfnuKOcZq4=
=PRtB
-END PGP SIGNATURE End Message ---

Bug#999332: marked as done (libgcr410: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 17:06:44 +
with message-id 
and subject line Bug#999332: fixed in libgcr410 2.4.0-9.3
has caused the Debian Bug report #999332,
regarding libgcr410: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgcr410
Version: 2.4.0-9.2
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: libgcr410
Source-Version: 2.4.0-9.3
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
libgcr410, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated libgcr410 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: Sun, 06 Nov 2022 13:24:39 -0300
Source: libgcr410
Architecture: source
Version: 2.4.0-9.3
Distribution: unstable
Urgency: medium
Maintainer: Peter De Schrijver (p2) 
Changed-By: Marcos Talau 
Closes: 999332
Changes:
 libgcr410 (2.4.0-9.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep} (Closes: #999332).
Checksums-Sha1:
 f2863bf36cd7111eec17809699713f346d5ee777 1698 libgcr410_2.4.0-9.3.dsc
 4a74922971569b29ee7d9dea6d1f73033f1a65ae 10446 libgcr410_2.4.0-9.3.diff.gz
 c4877683e8698318ef6d4ece58f3a3a151393a05 5878 
libgcr410_2.4.0-9.3_source.buildinfo
Checksums-Sha256:
 2c1abeabc525f66bb2da7da2fc643a6e85ce222b4151ba92175fc9c2c1e2c4b0 1698 
libgcr410_2.4.0-9.3.dsc
 65df2704857b640026ff0169141639ac98dbc73afaa5fca676ef3c5d17bdbe67 10446 
libgcr410_2.4.0-9.3.diff.gz
 7f6c03d4f9b12d764294ff7f7fcad3a712884330d12f3d10315f1eb90455a154 5878 
libgcr410_2.4.0-9.3_source.buildinfo
Files:
 1757e03b7c7be8543864276908080a65 1698 misc optional libgcr410_2.4.0-9.3.dsc
 a7f5713e53f0e398c4310f5f0154c70b 10446 misc optional 
libgcr410_2.4.0-9.3.diff.gz
 269f5ca5b4980164af0df79d175abb0a 5878 misc optional 
libgcr410_2.4.0-9.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn4QsACgkQ9LqqgNso
ukwHFw//SlKWY0hWIi7arS8KMX3f5ZFxbvXAxInRWjgxUUfrmaf4R0c0CzHRjCSB
y3LXeQNMPlqPob8n2UtXWrLQXKv20vnu57Zv1KkfR3pvF/TTtSUKPMC7leYvixo/
BJ9tWTV7qNZWnC4PqWFLlTSpFIxXrkFSrcmYtQdprIhb1wnL0coHyfFrwfNAUDVy
G9w4gnOfKtLR4x1nxUq8lHfVbqkovbHbCpvx6PNEd7owq7CqIqUQ0COmvO3Q0RwX
ND+J/PiXOtc/lfrxAn4Of177zk1gQU78GQZ1V9xnxRpSdw2cmIjiAw3TCIm0UxB5
itAICNTnvwH5CS0XiDZhFg/ernvgfVgfmy7aRvUZSBABaL9Pp6XDgKzrgO98utdV
5lLAlidqoBoFEs2Ey4XapSzDXjLKNEoKX9xSeuKYea9X0VXgfwgKiWzmpdiFuPXB
nSwmsHNo2YBoWjcJJ1lnFBteQgqS5rMSrrNnJTPM4r/j4+QDcaKlFTKqGV+7Ygg5
AHGRDIMDXw2OvvWAYwUctWV/DhNXmhCK1E00omXFZDRMPvBQyYfuLc5+dFg/IWg/
bajZxC2CUkIfaAyqgI1dnlTi+zi+Ct9VcIW3y0KM96w4F6oDClFCe+sh5/14c26z
1PSKZc0njZfbpPkF07KxX+ESRejh2AiFVlFO3+Dlww09W9WY+2M=
=7tEz
-END PGP SIGNATURE End Message ---

Bug#967010: apache2: Did not reporoduce

[Yadd]

Le Mardi, Novembre 08, 2022 16:01 CET, Shai Berger  a écrit:
> Package: apache2
> Followup-For: Bug #967010
>
> Dear Maintainer,
>
> I just installed Apache2 and did not encounter the problem
> as reported in this bug.
>
> It is an old bug, and for some reason full of spam.
>
> Please close and/or delete it.
>
> Thanks.

Hi, it's a Buster-only bug, not a Bullseye's one

Bug#999308: marked as done (xplot: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 16:56:52 +
with message-id 
and subject line Bug#999308: fixed in xplot 1.19-9.1
has caused the Debian Bug report #999308,
regarding xplot: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xplot
Version: 1.19-9
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: xplot
Source-Version: 1.19-9.1
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
xplot, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcos Talau  (supplier of updated xplot 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: Sun, 06 Nov 2022 13:18:50 -0300
Source: xplot
Architecture: source
Version: 1.19-9.1
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith 
Changed-By: Marcos Talau 
Closes: 999308
Changes:
 xplot (1.19-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep} (Closes: #999308).
Checksums-Sha1:
 85ef8f60efba4b0ee103962a3165527de1cdf419 1650 xplot_1.19-9.1.dsc
 d372e2e5eb875a8315c9bafdf823faf86130bff0 4504 xplot_1.19-9.1.debian.tar.xz
 7665afd55f171263ee9e4596f60e9bcef3e5cbf2 6343 xplot_1.19-9.1_source.buildinfo
Checksums-Sha256:
 f24ab743fbfbaf557c4844bd7adc51ac7d61ec3bcb8dc5b6fe4e3b00a5e24199 1650 
xplot_1.19-9.1.dsc
 4183747afab64c0a2fb370476c72a0ec5468c703fd29edc0b866dbd4f7459002 4504 
xplot_1.19-9.1.debian.tar.xz
 24152a8a7acd0e93329a630c0883a2059d71158118dfd789a92ae2fb6a4b37d0 6343 
xplot_1.19-9.1_source.buildinfo
Files:
 1d4de37e127c5c82524e01f4e389c464 1650 science optional xplot_1.19-9.1.dsc
 754023ea7f8f708fe30f0a1da274f409 4504 science optional 
xplot_1.19-9.1.debian.tar.xz
 c17aff30d29c154e73679aa2a9c7f79a 6343 science optional 
xplot_1.19-9.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn3s8ACgkQ9LqqgNso
ukw+eA/7BB5lS16eEzyE/WrMxs5i8JnnDsF3+Xm+LQTSdVOs1J/jzXGjpBv3nRVa
n8bhapmRyemoUZi9yFn33d0H1iHDqiAi6vYeUgV0LOrng5VfLo64zDOstGPSius3
4lxL/Jv/UriQ/MSSOjkxhbu96+EPbdP5ZZcVdmlnOrQ4sfe27y/Yxq90uH70mUfB
R4jFhW7lkPzbIlOh2PS27ZcPTqzIa1dIM9EOKJRJlCFFYoYn8t9/Y4MFL+dbvdEd
FslLuqBV7IVwJ7X5lj5bRdU6RHdKgMldxbvZ00owfsGmlff23DHp7v6xf80fo6zZ
BGTDO+XUreJg4ezuT5TyYsQdW9019TTepAcKEJk0hTYaS/huCqGknUgLCTfPN3/a
+fOhbGJDj+mhmg5iX8is4su8n8dhIfF9xfESN378CVu05nXIb19M4cWKPU5SAm1a
TQ/T2+EZ9xm8LJRsizmvUSqVJHDNF+i0+l9MseThBluY7jHAmAwiuqNvhbMa2YfF
aw9xMjtpIwvZNT0mWmCu6lX0twbC7KzCdfMVxfgUCoAjzqhdlnNrv4Pi0Si032eD
2hI3PW8SjzoM+R59FXDELL3norTRQoB443GcsjgveBQL2C0xCfyH2Ljx8cF7CX5Z
khiaDQnNUo4TF6GbarHnSXXGRKXHFphjO5mE68MHwwjNG753YmU=
=TRnK
-END PGP SIGNATURE End Message ---

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Pavel Odintsov]

Hello!

Added copy to all.

I think I fixed it with these commits:
https://github.com/pavel-odintsov/fastnetmon/commit/c48497a6f109fc1a9f5da596b055c3b7cffb96d4
and
https://github.com/pavel-odintsov/fastnetmon/commit/c718e88d0b25dcfbd724e9820f592fd5782eca6c

I've used
https://lore.kernel.org/bpf/20220202225916.3313522-7-and...@kernel.org/ and
https://lxr.missinglinkelectronics.com/linux+v5.19/samples/bpf/xdp1_user.c
as examples as this code was my reference during implementation.

Would be great if you could review it a second time.

Thank you!

On Mon, 7 Nov 2022 at 11:59, Sudip Mukherjee 
wrote:

> Hi Pavel,
>
> On Mon, Nov 7, 2022 at 11:53 AM Pavel Odintsov 
> wrote:
> >
> > Hello!
> >
> > Thank you for reaching me.
> >
> > Sure, I'll be happy to check.
> >
> > May I kindly ask what exactly changed to trigger these errors? I believe
> it was successfully built previously.
>
> Its the update of libbpf to v1.0.1 which removed some of the deprecated
> API.
>
>
> --
> Regards
> Sudip
>


-- 
Sincerely yours, Pavel Odintsov

Processed: tagging 1011600

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1011600 + pending
Bug #1011600 [src:opencensus-java] opencensus-java: FTBFS with OpenJDK 17 due 
to new compiler warnings
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1023204: (no subject)

[Andre Naujoks]

Just FYI. This is "fixed" in the current samba-libs version.

Am 5. November 2022 19:05:19 MEZ schrieb Andre Naujoks :
>I am also affected by this. I worked around this by installing the samba-libs 
>package from testing and pinning the version to 2:4.16*
>
>This workaround will go away though, when 2:4.17 migrates to testing as well.
>
>-- 
>To unsubscribe, send mail to 1023204-unsubscr...@bugs.debian.org.

Bug#1023666: gcc-10 should not be shipped in bookworm

[Adrian Bunk]

Package: gcc-10
Version: 10.4.0-5
Severity: serious

gcc-10 should not be shipped in bookworm.

Bug#1023665: pdfposter: ModuleNotFoundError: No module named 'PyPDF2.pdf'

[Jakub Wilk]

Package: pdfposter
Version: 0.7.post1-2
Severity: grave

pdfposter doesn't work at all:

$ pdfposter --help
Traceback (most recent call last):
  File "/usr/bin/pdfposter", line 33, in 
sys.exit(load_entry_point('pdftools.pdfposter==0.7.post1', 
'console_scripts', 'pdfposter')())
  File "/usr/bin/pdfposter", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in 
load
module = import_module(match.group('module'))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 992, in _find_and_load_unlocked
  File "", line 241, in 
_call_with_frames_removed
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in 
_find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in 
_call_with_frames_removed
  File "/usr/share/pdfposter/pdftools/pdfposter/__init__.py", line 27, in 

from PyPDF2.pdf import PdfFileWriter, PdfFileReader, PageObject, 
getRectangle, \
ModuleNotFoundError: No module named 'PyPDF2.pdf'


-- System Information:
Architecture: i386

Versions of packages pdfposter depends on:
ii  python3-pypdf2 2.11.1-1
ii  python33.10.6-1
ii  python3-pkg-resources  65.5.0-1
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-underscore   1.13.4~dfsg+~1.11.4-2

--
Jakub Wilk

Processed: Re: Bug#732570: libarch-perl should be removed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #732570 [libarch-perl] libarch-perl should be removed
Severity set to 'serious' from 'normal'
> tags -1 bookworm sid
Bug #732570 [libarch-perl] libarch-perl should be removed
Added tag(s) sid and bookworm.

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

Bug#1023629: marked as done (glib2.0: flaky autopkgtest on armhf and armel (on ci.d.n infra): glib/threadtests.test times out after 300 seconds)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2022 15:49:18 +
with message-id 
and subject line Bug#1023629: fixed in glib2.0 2.74.1-2
has caused the Debian Bug report #1023629,
regarding glib2.0: flaky autopkgtest on armhf and armel (on ci.d.n infra): 
glib/threadtests.test times out after 300 seconds
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.)


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

Source: glib2.0
Version: 2.74.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails since around March 2022 on armel [1] and the 
first of October 2022 on armhf [2].


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/packages/g/glib2.0/testing/armel/
[2] https://ci.debian.net/packages/g/glib2.0/testing/armhf/

https://ci.debian.net/data/autopkgtest/testing/armhf/g/glib2.0/26345811/log.gz

# Executing: glib/threadtests.test
# Executing: glib/threadtests.test
# Executing: glib/threadtests.test
not ok - Test timed out after 300 seconds
# FAIL: glib/threadtests.test (Child process killed by signal 9)
not ok - glib/threadtests.test

[...]

# SUMMARY: total=275; passed=272; skipped=2; failed=1; user=1680.6s; 
system=176.1s; maxrss=154072

# FAIL: glib/threadtests.test (Child process killed by signal 9)


https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27696626/log.gz

not ok - Test timed out after 300 seconds
# FAIL: glib/threadtests.test (Child process killed by signal 9)
not ok - glib/threadtests.test
# Running test: glib/gutils-user-database.test
# random seed: R02Sa857e7d4f9a0241ca5d1865ccc7eafc1
1..1
# Start of gutils tests
ok 1 /gutils/get_user_database_entry
# End of gutils tests
ok - glib/gutils-user-database.test
# SUMMARY: total=284; passed=281; skipped=2; failed=1; user=1566.6s; 
system=169.8s; maxrss=153428

# FAIL: glib/threadtests.test (Child process killed by signal 9)


https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27421159/log.gz

# SUMMARY: total=276; passed=273; skipped=2; failed=1; user=1555.8s; 
system=175.9s; maxrss=170864

# FAIL: glib/threadtests.test (Child process killed by signal 9)


https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27116770/log.gz

# SUMMARY: total=276; passed=273; skipped=2; failed=1; user=1552.2s; 
system=274.3s; maxrss=226436

# FAIL: glib/threadtests.test (Child process killed by signal 9)



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.74.1-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.0, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Tue, 08 Nov 2022 10:32:47 +
Source: glib2.0
Architecture: source
Version: 2.74.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1023629 1023652
Changes:
 glib2.0 (2.74.1-2) unstable; urgency=medium
 .
   * d/patches: Update to upstream 2.74.x branch commit 2.74.1-11-g5ee590045
 - Revert a change to file descriptor management that caused an infinite
   loop in some gnome-keyring-daemon use-cases
 - Fix error behaviour with an invalid proxy address
 - Fix a memory leak
 - Fix a header multiple-inclusion guard
 - Translation updates
   * d/p/tests-Don-t-rely-on-output-locale-of-sort-in-spawn-test.patch:
 Add patch from upstream git to fix a test failure in 

Bug#1023529: subversion: FTBFS: segfault in Python tests with SWIG 4.1.0

[Manuel A. Fernandez Montecelo]

Package: subversion
Followup-For: Bug #1023529
X-Debbugs-Cc: m...@debian.org, 1023529-submit...@bugs.debian.org

Hi,

I built a version of the package with the mentioned patch (debdiff attached), it
built correctly and passed all tests.

This was in riscv64, where the problem was detected, but I expect that it would
apply to all arches.

Hope that helps.

--
Manuel A. Fernandez Montecelo 
diff -Nru subversion-1.14.2/debian/changelog subversion-1.14.2/debian/changelog
--- subversion-1.14.2/debian/changelog  2022-07-12 16:03:54.0 +0200
+++ subversion-1.14.2/debian/changelog  2022-11-08 10:57:37.0 +0100
@@ -1,3 +1,10 @@
+subversion (1.14.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch to fix "FTBFS: segfault in Python tests with SWIG 4.1.0" (Closes: 
#1023529)
+
+ -- Manuel A. Fernandez Montecelo   Tue, 08 Nov 2022 09:57:37 
+
+
 subversion (1.14.2-3) unstable; urgency=medium
 
   * Re-enable the ability to store plaintext passwords (Closes: #995692)
diff -Nru 
subversion-1.14.2/debian/patches/8ff4cfd06ce554e9df31a088c9d09f45278c6de4.patch 
subversion-1.14.2/debian/patches/8ff4cfd06ce554e9df31a088c9d09f45278c6de4.patch
--- 
subversion-1.14.2/debian/patches/8ff4cfd06ce554e9df31a088c9d09f45278c6de4.patch 
1970-01-01 01:00:00.0 +0100
+++ 
subversion-1.14.2/debian/patches/8ff4cfd06ce554e9df31a088c9d09f45278c6de4.patch 
2022-11-08 10:57:37.0 +0100
@@ -0,0 +1,61 @@
+From 8ff4cfd06ce554e9df31a088c9d09f45278c6de4 Mon Sep 17 00:00:00 2001
+From: Yasuhito Futatsuki 
+Date: Tue, 20 Sep 2022 12:57:06 +
+Subject: [PATCH] swig-py: Fix conditionals by SWIG version and by Python
+ version for proxy code.
+
+We are using different code for proxy object, by Python version and by SWIG
+version.  The distinguish between Python 2 and Python 3 was done by SWIG
+macro "SWIGPYTHON_PY3".  However, the macro was dropped since SWIG commit
+a343b7e[1], between SWIG 4.0.2 release and upcoming SWIG 4.1.0 release.
+
+As we already dropped support for the combination of SWIG >= 4.0 and Python 2,
+we should detect Python 2 only in SWIG < 4.0 case. So we can rely on the macro
+only in the case.
+
+* subversion/bindings/swig/include/proxy.swg ():
+  Reorder the conditionals distinguish SWIG versions and Python versions,
+  as described above.
+
+Found by: Jitka Plesnikova (jplesnik {_AT_} redhat.com)
+
+Suggested by: Julien Schueller (schueller {_AT_} phimeca.com) [2]
+
+[1] 
https://github.com/swig/swig/commit/a343b7e254567a64761bc1be7dc55b7b7424ec52
+[2] https://github.com/swig/swig/issues/2373#issuecomment-1250997124
+
+
+git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1904167 
13f79535-47bb-0310-9956-ffa450edef68
+---
+ subversion/bindings/swig/include/proxy.swg | 4 +---
+ 1 file changed, 1 insertion(+), 3 deletions(-)
+
+Index: subversion-1.14.2/subversion/bindings/swig/include/proxy.swg
+===
+--- subversion-1.14.2.orig/subversion/bindings/swig/include/proxy.swg
 subversion-1.14.2/subversion/bindings/swig/include/proxy.swg
+@@ -66,7 +66,6 @@
+ fn()
+ 
+ %}
+-#if defined(SWIGPYTHON_PY3)
+ #if SWIG_VERSION >= 0x04
+ %pythoncode %{
+   # -classic and -modern options have been dropped and this variable
+@@ -76,7 +75,7 @@
+   _set_instance_attr = 
_swig_setattr_nondynamic_instance_variable(object.__setattr__)
+ 
+ %}
+-#else
++#elif defined(SWIGPYTHON_PY3)
+ %pythoncode %{
+   # SWIG classes generated with -modern do not define this variable
+   try:
+@@ -90,7 +89,6 @@
+   _set_instance_attr = _swig_setattr_nondynamic_method(object.__setattr__)
+ 
+ %}
+-#endif
+ #else
+ %pythoncode %{
+   # SWIG classes generated with -classic do not define this variable,
diff -Nru subversion-1.14.2/debian/patches/series 
subversion-1.14.2/debian/patches/series
--- subversion-1.14.2/debian/patches/series 2022-07-12 16:03:54.0 
+0200
+++ subversion-1.14.2/debian/patches/series 2022-11-08 10:57:37.0 
+0100
@@ -10,3 +10,4 @@
 examples-compile-instructions
 workaround_EINVAL_on_kfreebsd
 use-python3-as-the-interpreter-now-for-tests-not-python.patch
+8ff4cfd06ce554e9df31a088c9d09f45278c6de4.patch

Bug#1023662: adv-17v35x-dkms: module fails to build for Linux 6.0

[Andreas Beckmann]

Package: adv-17v35x-dkms
Version: 5.0.6.0-3
Severity: serious

Hi,

the adv-17v35x-dkms module cannot be built for Linux 6.0:

https://ci.debian.net/data/autopkgtest/unstable/amd64/a/adv-17v35x/27922615/log.gz

DKMS make.log for adv-17v35x-5.0.6.0 for kernel 6.0.0-2-amd64 (x86_64)
Fri Nov  4 16:55:27 UTC 2022
make: Entering directory '/usr/src/linux-headers-6.0.0-2-amd64'
  CC [M]  /var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c: In function 
‘serialadv_timeout’:
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c:1190:62: error: ‘struct 
uart_port’ has no member named ‘timeout’
 1190 | mod_timer(>timer, jiffies + poll_timeout(up->port.timeout));
  |  ^
make[1]: *** [/usr/src/linux-headers-6.0.0-2-common/scripts/Makefile.build:254: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o] Error 1
make: *** [/usr/src/linux-headers-6.0.0-2-common/Makefile:1876: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.0.0-2-amd64'


Andreas

Processed: tagging 1010311, tagging 1004795, tagging 983648, tagging 794466, tagging 1022431, tagging 1017058 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1010311 + experimental
Bug #1010311 [src:silkaj] python-duniterpy breaks silkaj autopkgtest: cannot 
import name 'BlockUID' from 'duniterpy.documents'
Added tag(s) experimental.
> tags 1004795 - sid bookworm
Bug #1004795 [src:gazebo] gazebo: FTBFS with ffmpeg 5.0
Removed tag(s) sid and bookworm.
> tags 983648 + experimental
Bug #983648 [kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10: 
uses unknown struct stack_trace
Added tag(s) experimental.
> tags 794466 + experimental
Bug #794466 [src:virtualbox] virtualbox: might not be suitable for stable 
releases due to lack of cooperation from upstream on security support for older 
releases
Added tag(s) experimental.
> tags 1022431 + experimental
Bug #1022431 {Done: Stuart Prescott } [src:sasview] sasview: 
FTBFS: distutils.errors.DistutilsClassError: command class  must subclass Command
Added tag(s) experimental.
> tags 1017058 + sid bookworm
Bug #1017058 {Done: Harlan Lieberman-Berg } [evdi-dkms] 
evdi-dkms: failt to compile drm/drm_irq.h is missing - kernel 5.18.0-3-amd64
Added tag(s) sid and bookworm.
> tags 1023258 + sid bookworm
Bug #1023258 {Done: Étienne Mollier } [pcalendar] uses 
com.sun.org.apache.xml.internal.serialize
Added tag(s) sid and bookworm.
> tags 1020818 + sid bookworm
Bug #1020818 {Done: Mathieu Malaterre } [abi-dumper] 
abi-dumper: abi-dumper 1.2 doesn't work with today's binaries
Added tag(s) sid and bookworm.
> tags 1020404 + sid bookworm
Bug #1020404 {Done: Markus Demleitner } [luakit] luakit: 
aborts at start
Added tag(s) bookworm and sid.
> found 1017063 1.73.1-1
Bug #1017063 {Done: Jeremy Bicha } [src:gjs] fails to start: 
gjs expected 'boxed_type' but got undefined
Marked as found in versions gjs/1.73.1-1.
> tags 1020977 + sid bookworm
Bug #1020977 [src:php-facedetect] FTBFS: *** DH_PHP_VERSIONS cannot be empty.  
Stop.
Added tag(s) bookworm and sid.
> tags 1020978 + sid bookworm
Bug #1020978 [src:tideways] FTBFS: *** DH_PHP_VERSIONS cannot be empty.  Stop.
Added tag(s) bookworm and sid.
> reassign 1020327 gcc-12
Bug #1020327 [gcc] filezilla: FTBFS on i386
Bug reassigned from package 'gcc' to 'gcc-12'.
No longer marked as found in versions 12.
Ignoring request to alter fixed versions of bug #1020327 to the same values 
previously set
> affects 1020327 + src:filezilla
Bug #1020327 [gcc-12] filezilla: FTBFS on i386
Added indication that 1020327 affects src:filezilla
> tags 994695 + sid bookworm
Bug #994695 {Done: Jeremy Bicha } [qreator] qreator: won't 
start
Added tag(s) sid and bookworm.
> found 1019050 0.25
Bug #1019050 {Done: Alastair McKinstry } [dh-fortran-mod] 
postrm template: failed to remove
Marked as found in versions dh-fortran-mod/0.25.
> tags 886052 - buster bullseye
Bug #886052 [src:ogmrip] ogmrip: Depends on gconf
Removed tag(s) buster and bullseye.
> found 1016506 0.16.24
Bug #1016506 {Done: Clint Adams } [haskell-devscripts] 
libghc-shake-{doc,dev,data}: all ship 
/usr/lib/haskell-packages/extra-packages/shake-0.19.6
Marked as found in versions haskell-devscripts/0.16.24.
> tags 1003463 + sid bookworm
Bug #1003463 {Done: Christoph Biedl } 
[arcanist] Functionally broken with current PHP
Added tag(s) bookworm and sid.
> tags 1019300 + sid bookworm
Bug #1019300 {Done: Peter Blackman } 
[src:mp3guessenc] mp3guessenc: autopkgtests failure with grep 3.8: fgrep is 
deprecated
Added tag(s) bookworm and sid.
> tags 1017985 + sid bookworm
Bug #1017985 {Done: Hilko Bengen } [src:roger-router] 
roger-router: Fails to build with evolution-data-server 3.45
Added tag(s) sid and bookworm.
> tags 1018801 + sid bookworm
Bug #1018801 [src:stdx-allocator] stdx-allocator ftbfs: assertThrown failed: No 
Exception was thrown.
Added tag(s) sid and bookworm.
> tags 166 + sid bookworm
Bug #166 [src:haskell-pcre-light] haskell-pcre-light: depends on obsolete 
pcre3 library
Added tag(s) bookworm and sid.
> found 1013218 2:6.1.4.6+dfsg-3
Bug #1013218 {Done: Pirate Praveen } [rails] rails: ftbfs 
SyntaxError: Unexpected token 'export'
Marked as found in versions rails/2:6.1.4.6+dfsg-3.
> tags 1016560 + sid bookworm
Bug #1016560 {Done: Aurelien Jarno } [src:scalpel] glibc 
2.34 breaks scalpel autopkgtest on amd64: bash: line 1:  1961 Segmentation fault
Added tag(s) sid and bookworm.
> tags 938492 - bullseye
Bug #938492 {Done: Thomas Goirand } [src:six] six: Python2 
removal in sid/bullseye
Removed tag(s) bullseye.
> tags 1014483 + sid bookworm
Bug #1014483 {Done: Sandro Tosi } [src:pytest-twisted] 
pytest-twisted: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; 
s390x: pytest7 migration - fixture 'testdir' not found
Added tag(s) sid and bookworm.
> tags 1014623 + sid bookworm
Bug #1014623 [src:xjig] xjig: build-depends on obsolete libnetpbm10-dev, ftbfs 
with libnetpbm11-dev
Added tag(s) sid and bookworm.
> found 1013877 1:1.4.13+dfsg-1
Bug #1013877 {Done: Sergei Golovan } [libtk-img] 
libtk-img: add _TIFFsetString to its internal tiff library
Bug 

Bug#1023654: liburing 2.3 breaks binary compatibility

[Michael Tokarev]

08.11.2022 16:44, Guillem Jover wrote:

Hi!

On Tue, 2022-11-08 at 16:32:25 +0300, Michael Tokarev wrote:

On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev  wrote:

Source: liburing
Version: 2.3-1
Severity: grave

liburing 2.3 broke binary compatibility without bumping the soname.


Indeed. :/ Should make a habit of checking the header diffs, as this
is not the first time this has happened.


Actually this is interesting. Maybe it would be better for me to just
wait till new liburing migrates to testing, and re-run samba autopkgtests,
instead of filing this bugreport...  (Provided it works the other way
around, which I'm not sure about yet).

/mjt

Bug#967010: apache2: Did not reporoduce

[Shai Berger]

Package: apache2
Followup-For: Bug #967010

Dear Maintainer,

I just installed Apache2 and did not encounter the problem
as reported in this bug.

It is an old bug, and for some reason full of spam.

Please close and/or delete it.

Thanks.

-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin2.4.54-3
ii  apache2-data   2.4.54-3
ii  apache2-utils  2.4.54-3
ii  init-system-helpers1.65.2
ii  lsb-base   11.4
ii  mime-support   3.66
ii  perl   5.36.0-4
ii  procps 2:3.3.17-7.1
ii  sysvinit-utils [lsb-base]  3.05-6

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.2

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   107.0.5304.87-1
ii  dillo [www-browser]  3.0.5-7+b1
ii  firefox-esr [www-browser]102.4.0esr-1
ii  konqueror [www-browser]  4:21.12.3-1
ii  lynx [www-browser]   2.9.0dev.10-1+b1

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.0-8
ii  libaprutil1  1.6.1-5+b2
ii  libaprutil1-dbd-sqlite3  1.6.1-5+b2
ii  libaprutil1-ldap 1.6.1-5+b2
ii  libbrotli1   1.0.9-2+b4
ii  libc62.35-4
ii  libcrypt11:4.4.28-2
ii  libcurl4 7.85.0-1
ii  libjansson4  2.14-2
ii  libldap-2.5-02.5.13+dfsg-2+b1
ii  liblua5.3-0  5.3.6-1+b1
ii  libnghttp2-141.50.0-1+b1
ii  libpcre2-8-0 10.40-2
ii  libssl3  3.0.7-1
ii  libxml2  2.9.14+dfsg-1+b1
ii  perl 5.36.0-4
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   107.0.5304.87-1
ii  dillo [www-browser]  3.0.5-7+b1
ii  firefox-esr [www-browser]102.4.0esr-1
ii  konqueror [www-browser]  4:21.12.3-1
ii  lynx [www-browser]   2.9.0dev.10-1+b1

Versions of packages apache2 is related to:
ii  apache2  2.4.54-3
ii  apache2-bin  2.4.54-3

-- no debconf information

Bug#1023654: liburing 2.3 breaks binary compatibility

[Michael Tokarev]

08.11.2022 17:11, Guillem Jover wrote:
[..]

If you are really seeing samba linked against old liburing not working
with the new liburing, then we'd need to dig further to see what else
might be missing, but I'm currently not seeing it just by a very quick
code staring.


Well. I already deleted my test chroot. I can't say for 100% now that it
breaks the other way around. I'll have to double-check.  It took me quite
quite some time especially due to other urgent things I'm doing today.
I can check if 2.2-compiled samba works with 2.3-uring but a bit later
today.  Even if it works, it is not exactly conclusive, since samba only
uses certain code paths.  But ofc if it doesn't work, it *is* conclusive :)

Thanks,

/mjt

Bug#1023654: liburing 2.3 breaks binary compatibility

[Guillem Jover]

Hi!

I've forwarded this upstream now.

On Tue, 2022-11-08 at 14:44:25 +0100, Guillem Jover wrote:
> On Tue, 2022-11-08 at 16:32:25 +0300, Michael Tokarev wrote:
> > On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev  wrote:
> > > In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
> > > their sizes. Both of these structures are parts of io_uring structure
> > > which the main part of the API.  Here's the difference:
> > > 
> > > @@ -43,7 +79,9 @@
> > > @@ -56,13 +94,18 @@
> > > size_t ring_sz;
> > > void *ring_ptr;
> > > -   unsigned pad[4];
> > > +   unsigned ring_mask;
> > > +   unsigned ring_entries;
> > > +
> > > +   unsigned pad[2];
> > 
> > This does not look like it is changing the size actually, - I haven't
> > noticed it adjusts pad[] accordingly. So this is not the issue here.
> > 
> > But the end result is the same: samba compiled with liburing 2.2 does
> > not work with runtime liburing 2.3, and samba compiled with liburing
> > 2.3 does not work with runtime liburing 2.2.

I've checked the code and this is weird, the new code is taking care of
initializing all members with the new shared library. So I'd expect
samba built against the old liburing to work with the new one. But the
problem seems to be that code built against the new liburing will not
work with the old liburing, as that one does not initialize the new
members being used from the inline functions.

If you are really seeing samba linked against old liburing not working
with the new liburing, then we'd need to dig further to see what else
might be missing, but I'm currently not seeing it just by a very quick
code staring.

Thanks,
Guillem

Processed: bug 1023654 is forwarded to https://github.com/axboe/liburing/issues/724

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1023654 https://github.com/axboe/liburing/issues/724
Bug #1023654 [src:liburing] liburing 2.3 breaks binary compatibility
Set Bug forwarded-to-address to 'https://github.com/axboe/liburing/issues/724'.
> thanks
Stopping processing here.

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

Bug#1023650: vlc: Trying to view video files via Vlc 3.0.18~rc2-1+b1 tightly hangs Debian

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2022-11-08 12:09:28 +0300, Сергей Фёдоров wrote:
> Package: vlc
> Version: 3.0.18~rc2-1+b1
> Severity: critical
> Justification: breaks the whole system
> X-Debbugs-Cc: serfyod...@yandex.ru
> 
> Dear Maintainer,
> 
> Trying to view video files via Vlc 3.0.18~rc2-1+b1 tightly hangs Debian

Please provide a verbose log of vlc when this issue happens.

Cheers

> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 vlc depends on:
> ii  vlc-bin  3.0.18~rc2-1+b1
> ii  vlc-plugin-base  3.0.18~rc2-1+b1
> ii  vlc-plugin-qt3.0.18~rc2-1+b1
> ii  vlc-plugin-video-output  3.0.18~rc2-1+b1
> 
> Versions of packages vlc recommends:
> ii  vlc-l10n   3.0.18~rc2-1
> ii  vlc-plugin-access-extra3.0.18~rc2-1+b1
> ii  vlc-plugin-notify  3.0.18~rc2-1+b1
> ii  vlc-plugin-samba   3.0.18~rc2-1+b1
> ii  vlc-plugin-skins2  3.0.18~rc2-1+b1
> ii  vlc-plugin-video-splitter  3.0.18~rc2-1+b1
> ii  vlc-plugin-visualization   3.0.18~rc2-1+b1
> 
> Versions of packages vlc suggests:
> pn  vlc-plugin-fluidsynth  
> pn  vlc-plugin-jack
> pn  vlc-plugin-pipewire
> pn  vlc-plugin-svg 
> 
> Versions of packages libvlc-bin depends on:
> ii  libc62.36-4
> ii  libvlc5  3.0.18~rc2-1+b1
> 
> Versions of packages libvlc5 depends on:
> ii  libc62.36-4
> ii  libvlccore9  3.0.18~rc2-1+b1
> 
> Versions of packages libvlc5 recommends:
> ii  libvlc-bin  3.0.18~rc2-1+b1
> 
> Versions of packages vlc-bin depends on:
> ii  libc6   2.36-4
> ii  libvlc-bin  3.0.18~rc2-1+b1
> ii  libvlc5 3.0.18~rc2-1+b1
> 
> Versions of packages vlc-plugin-access-extra depends on:
> ii  libc62.36-4
> ii  libsrt1.5-gnutls 1.5.1-1
> ii  libvlccore9 [vlc-plugin-abi-3-0-0f]  3.0.18~rc2-1+b1
> ii  libvncclient10.9.13+dfsg-4
> ii  libxcb-composite01.15-1
> ii  libxcb-shm0  1.15-1
> ii  libxcb1  1.15-1
> 
> Versions of packages vlc-plugin-base depends on:
> ii  liba52-0.7.4 0.7.4-20
> ii  libarchive13 3.6.0-1
> ii  libaribb24-0 1.0.3-2
> ii  libasound2   1.2.7.2-1
> ii  libass9  1:0.16.0-1
> ii  libavahi-client3 0.8-6+b1
> ii  libavahi-common3 0.8-6+b1
> ii  libavc1394-0 0.5.4-5
> ii  libavcodec59 7:5.1.2-1
> ii  libavformat597:5.1.2-1
> ii  libavutil57  7:5.1.2-1
> ii  libbluray2   1:1.3.3-1
> ii  libc62.36-4
> ii  libcairo21.16.0-6
> ii  libcddb2 1.3.2-7
> ii  libchromaprint1  1.5.1-2+b1
> ii  libdav1d61.0.0-2
> ii  libdbus-1-3  1.14.4-1
> ii  libdc1394-25 2.2.6-4
> ii  libdca0  0.0.7-2
> ii  libdvbpsi10  1.3.3-1
> ii  libdvdnav4   6.1.1-1
> ii  libdvdread8  6.1.3-1
> ii  libebml5 1.4.4-1
> ii  libfaad2 2.10.1-1
> ii  libflac121.4.2+ds-1
> ii  libfontconfig1   2.13.1-4.5
> ii  libfreetype6 2.12.1+dfsg-3
> ii  libfribidi0  1.0.8-2.1
> ii  libgcc-s112.2.0-9
> ii  libgcrypt20  1.10.1-2
> ii  libglib2.0-0 2.74.1-1
> ii  libgnutls30  3.7.8-4
> ii  libgpg-error01.46-1
> ii  libharfbuzz0b5.2.0-2
> ii  libixml101:1.8.4-2
> ii  libjpeg62-turbo  1:2.1.2-1+b1
> ii  libkate1 0.4.1-11
> ii  liblirc-client0  0.10.1-7.1
> ii  liblua5.2-0  5.2.4-2
> ii  libmad0  0.15.1b-10.1+b1
> ii  libmatroska7 1.7.1-1
> ii  libmpcdec6   2:0.1~r495-2
> ii  libmpeg2-4   0.5.1-9
> ii  libmpg123-0  1.31.1-1
> ii  libmtp9  1.1.20-1
> ii  libncursesw6 6.3+20220423-2
> ii  libnfs13 4.0.0-1

Processed: Re: Bug#1023650: vlc: Trying to view video files via Vlc 3.0.18~rc2-1+b1 tightly hangs Debian

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1023650 [vlc] vlc: Trying to view video files via Vlc 3.0.18~rc2-1+b1 
tightly hangs Debian
Added tag(s) moreinfo.

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

Bug#1023654: liburing 2.3 breaks binary compatibility

[Guillem Jover]

Hi!

On Tue, 2022-11-08 at 16:32:25 +0300, Michael Tokarev wrote:
> On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev  wrote:
> > Source: liburing
> > Version: 2.3-1
> > Severity: grave
> > 
> > liburing 2.3 broke binary compatibility without bumping the soname.

Indeed. :/ Should make a habit of checking the header diffs, as this
is not the first time this has happened.

> > In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
> > their sizes. Both of these structures are parts of io_uring structure
> > which the main part of the API.  Here's the difference:
> > 
> > @@ -43,7 +79,9 @@
> > @@ -56,13 +94,18 @@
> > size_t ring_sz;
> > void *ring_ptr;
> > -   unsigned pad[4];
> > +   unsigned ring_mask;
> > +   unsigned ring_entries;
> > +
> > +   unsigned pad[2];
> 
> This does not look like it is changing the size actually, - I haven't
> noticed it adjusts pad[] accordingly. So this is not the issue here.
> 
> But the end result is the same: samba compiled with liburing 2.2 does
> not work with runtime liburing 2.3, and samba compiled with liburing
> 2.3 does not work with runtime liburing 2.2.
> 
> I'm just too tired now to dig further.

The problem is that this release has deprecated the kring_mask and
kring_entries, and does not have fallback code to use them if they are
being used by the callers.

I'll report this upstream to see how they want to fix this, either
with a SOVERSION bump or trying to add dynamic fallback code or
similar.

For sid, I guess I could bump the affected functions required minimal
versions in the symbols file, and then add breaks on the old packages
using the old ABI, but meh. :/

Thanks,
Guillem

Bug#1023654: liburing 2.3 breaks binary compatibility

[Michael Tokarev]

On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev  wrote:

Source: liburing
Version: 2.3-1
Severity: grave

liburing 2.3 broke binary compatibility without bumping the soname.

In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
their sizes. Both of these structures are parts of io_uring structure
which the main part of the API.  Here's the difference:

@@ -43,7 +79,9 @@
@@ -56,13 +94,18 @@
size_t ring_sz;
void *ring_ptr;
 
-   unsigned pad[4];

+   unsigned ring_mask;
+   unsigned ring_entries;
+
+   unsigned pad[2];


This does not look like it is changing the size actually, - I haven't
noticed it adjusts pad[] accordingly. So this is not the issue here.

But the end result is the same: samba compiled with liburing 2.2 does
not work with runtime liburing 2.3, and samba compiled with liburing
2.3 does not work with runtime liburing 2.2.

I'm just too tired now to dig further.

/mjt

Processed: tagging 1023355, tagging 1023173, tagging 1023171, found 1019768 in 8.2.0-1 ..., tagging 1019172 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1023355 + sid bookworm
Bug #1023355 [limereg] limereg: depends on non-existing 
libboost-program-options1.67.0
Added tag(s) sid and bookworm.
> tags 1023173 + sid
Bug #1023173 {Done: Debian FTP Masters } 
[freeture] freeture: not installable, depends on libaravis-0.6-0
Added tag(s) sid.
> tags 1023171 + sid bookworm
Bug #1023171 [cernlib] cernlib: unsatisfiable dependency on geant321-doc
Added tag(s) bookworm and sid.
> found 1019768 8.2.0-1
Bug #1019768 {Done: Bas Couwenberg } [src:grass] grass: 
Please transition to wxwidgets3.2
Marked as found in versions grass/8.2.0-1.
> found 1019781 5.0+dfsg-6
Bug #1019781 [src:dolphin-emu] dolphin-emu: Please transition to wxwidgets3.2
Marked as found in versions dolphin-emu/5.0+dfsg-6.
> tags 1019172 + sid bookworm
Bug #1019172 [src:opengrm-ngram] opengrm-ngram FTBFS against libfst 1.7.9
Added tag(s) bookworm and sid.
> tags 1017939 + sid bookworm
Bug #1017939 [src:raul] RM: raul -- unmaintaied, RC-buggy, no-reverse-deps
Added tag(s) sid and bookworm.
> tags 1017938 + sid bookworm
Bug #1017938 [src:python-pmw] RM: python-pmw -- RoQA, unmaintained, RC-buggy
Added tag(s) bookworm and sid.
> tags 1015976 + sid bookworm
Bug #1015976 [src:vmm] Should vmm be removed?
Added tag(s) bookworm and sid.
> notfixed 1001239 1.10+dfsg-1
Bug #1001239 {Done: Graham Inggs } [src:python-lupa] 
python-lupa: FTBFS on mipsel during running the test
No longer marked as fixed in versions 1.10+dfsg-1.
> tags 995968 + sid bookworm
Bug #995968 {Done: Christoph Biedl } 
[gkrellm-leds] gkrellm-leds: This gkrellm plugin does not start, Error: 
undefined symbol: XTestFakeKeyEvent
Added tag(s) sid and bookworm.
> tags 996361 + bullseye bookworm sid
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Added tag(s) sid, bullseye, and bookworm.
> fixed 971129 1.38~1+deb10u1
Bug #971129 {Done: Steve McIntyre <93...@debian.org>} [src:shim-signed] 
shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 
15+1533136590.3beb971-7)
Marked as fixed in versions shim-signed/1.38~1+deb10u1.
> tags 1012103 + experimental
Bug #1012103 [src:android-platform-external-doclava] 
android-platform-external-doclava: FTBFS with OpenJDK 17 due to com.sun.javadoc 
removal
Added tag(s) experimental.
> tags 1019799 + experimental
Bug #1019799 [src:libalien-wxwidgets-perl] libalien-wxwidgets-perl: Please 
transition to wxwidgets3.2
Added tag(s) experimental.
> tags 1022281 + experimental
Bug #1022281 [src:iem-plugin-suite] iem-plugin-suite: FTBFS: ld: 
AllRADecoder_artefacts/None/libAllRADecoder_SharedCode.a(juce_core.cpp.o): 
undefined reference to symbol 'inflateEnd'
Added tag(s) experimental.
> tags 1012989 + experimental
Bug #1012989 [src:libsass] libsass: ftbfs with GCC-12
Added tag(s) experimental.
> tags 1016334 + experimental
Bug #1016334 [src:dvdisaster] dvdisaster: FTBFS: make[2]: *** [GNUmakefile:209: 
manual] Error 2
Added tag(s) experimental.
> retitle 1016334 dvdisaster: FTBFS: ! Argument of ? has an extra }.
Bug #1016334 [src:dvdisaster] dvdisaster: FTBFS: make[2]: *** [GNUmakefile:209: 
manual] Error 2
Changed Bug title to 'dvdisaster: FTBFS: ! Argument of ? has an extra }.' from 
'dvdisaster: FTBFS: make[2]: *** [GNUmakefile:209: manual] Error 2'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1001239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001239
1012103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012103
1012989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012989
1015976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015976
1016334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016334
1017938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017938
1017939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017939
1019172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019172
1019768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019768
1019781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019781
1019799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019799
1022281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022281
1023171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023171
1023173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023173
1023355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023355
971129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971129
995968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995968
996361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1023654: liburing 2.3 breaks binary compatibility

[Michael Tokarev]

Source: liburing
Version: 2.3-1
Severity: grave

liburing 2.3 broke binary compatibility without bumping the soname.

In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
their sizes. Both of these structures are parts of io_uring structure
which the main part of the API.  Here's the difference:

@@ -43,7 +79,9 @@
 struct io_uring_sq {
unsigned *khead;
unsigned *ktail;
+   // Deprecated: use `ring_mask` instead of `*kring_mask`
unsigned *kring_mask;
+   // Deprecated: use `ring_entries` instead of `*kring_entries`
unsigned *kring_entries;
unsigned *kflags;
unsigned *kdropped;
@@ -56,13 +94,18 @@
size_t ring_sz;
void *ring_ptr;
 
-   unsigned pad[4];
+   unsigned ring_mask;
+   unsigned ring_entries;
+
+   unsigned pad[2];
 };

...
struct io_uring {
  struct io_uring_sq sq;
  struct io_uring_cq cq;
  ...
}

So, a program which uses struct io_uring compiled with version 2.2 of the
library is completely incompatible when run with version 2.3 of the library,
and vise versa - since many user-visible members of this structure, even when
manipulated by the inline functions offered by uring.h, are completely
incompatible.

This breaks other software.  For example, samba compiled against liburing 2.3
will silently break when liburing 2.2 is used at the run time, and there's no
way for apt/dpkg to tell that liburing2.so upgrade is needed.  The same way,
samba compiled against liburing 2.2 breaks when liburing is upgraded to 2.3,
but in a different way.

Processed: asterisk-prompt-fr-armelle: diff for NMU version 20070613-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 965429 + patch
Bug #965429 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
Removal of obsolete debhelper compat 5 and 6 in bookworm
Ignoring request to alter tags of bug #965429 to the same tags previously set
> tags 965429 + pending
Bug #965429 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
Removal of obsolete debhelper compat 5 and 6 in bookworm
Ignoring request to alter tags of bug #965429 to the same tags previously set
> tags 999033 + patch
Bug #999033 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
missing required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999033 to the same tags previously set
> tags 999033 + pending
Bug #999033 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
missing required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999033 to the same tags previously set

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

Processed: asterisk-prompt-fr-armelle: diff for NMU version 20070613-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 965429 + patch
Bug #965429 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
Removal of obsolete debhelper compat 5 and 6 in bookworm
Added tag(s) patch.
> tags 965429 + pending
Bug #965429 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
Removal of obsolete debhelper compat 5 and 6 in bookworm
Added tag(s) pending.
> tags 999033 + patch
Bug #999033 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
missing required debian/rules targets build-arch and/or build-indep
Added tag(s) patch.
> tags 999033 + pending
Bug #999033 [src:asterisk-prompt-fr-armelle] asterisk-prompt-fr-armelle: 
missing required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#965429: asterisk-prompt-fr-armelle: diff for NMU version 20070613-2.2

[Adrian Bunk]

Control: tags 965429 + patch
Control: tags 965429 + pending
Control: tags 999033 + patch
Control: tags 999033 + pending

Dear maintainer,

I've prepared an NMU for asterisk-prompt-fr-armelle (versioned as 20070613-2.2)
and uploaded it to DELAYED/2. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -u asterisk-prompt-fr-armelle-20070613/debian/changelog asterisk-prompt-fr-armelle-20070613/debian/changelog
--- asterisk-prompt-fr-armelle-20070613/debian/changelog
+++ asterisk-prompt-fr-armelle-20070613/debian/changelog
@@ -1,3 +1,11 @@
+asterisk-prompt-fr-armelle (20070613-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965429)
+  * debian/rules: Add build-arch. (Closes: #999033)
+
+ -- Adrian Bunk   Tue, 08 Nov 2022 14:06:48 +0200
+
 asterisk-prompt-fr-armelle (20070613-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -u asterisk-prompt-fr-armelle-20070613/debian/compat asterisk-prompt-fr-armelle-20070613/debian/compat
--- asterisk-prompt-fr-armelle-20070613/debian/compat
+++ asterisk-prompt-fr-armelle-20070613/debian/compat
@@ -1 +1 @@
-5
+7
diff -u asterisk-prompt-fr-armelle-20070613/debian/rules asterisk-prompt-fr-armelle-20070613/debian/rules
--- asterisk-prompt-fr-armelle-20070613/debian/rules
+++ asterisk-prompt-fr-armelle-20070613/debian/rules
@@ -52,2 +52,3 @@
+build-arch: build
 
-.PHONY: clean binary-indep binary-arch binary install build build-indep
+.PHONY: clean binary-indep binary-arch binary install build build-arch build-indep

Bug#1001022: ruby-pathutil: diff for NMU version 0.16.1-2.1

[Adrian Bunk]

Dear maintainer,

I've prepared an NMU for ruby-pathutil (versioned as 0.16.1-2.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru ruby-pathutil-0.16.1/debian/changelog ruby-pathutil-0.16.1/debian/changelog
--- ruby-pathutil-0.16.1/debian/changelog	2022-08-16 06:14:20.0 +0300
+++ ruby-pathutil-0.16.1/debian/changelog	2022-11-08 13:58:34.0 +0200
@@ -1,3 +1,10 @@
+ruby-pathutil (0.16.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Upload to unstable.
+
+ -- Adrian Bunk   Tue, 08 Nov 2022 13:58:34 +0200
+
 ruby-pathutil (0.16.1-2) experimental; urgency=medium
 
   * Team upload.

Processed: bug 1022735 is forwarded to https://gitlab.com/yade-dev/trunk/-/merge_requests/840

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1022735 https://gitlab.com/yade-dev/trunk/-/merge_requests/840
Bug #1022735 [src:yade] yade: FTBFS: ImportError: cannot import name 'PY3' from 
'IPython.utils.py3compat' 
(/usr/lib/python3/dist-packages/IPython/utils/py3compat.py)
Set Bug forwarded-to-address to 
'https://gitlab.com/yade-dev/trunk/-/merge_requests/840'.
> thanks
Stopping processing here.

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

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

[Vincent Lefevre]

On 2022-11-07 13:36:30 +0100, Vincent Lefevre wrote:
> The removal of gpgme-config due to
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348
> 
> breaks the build of software relying on it, such as Mutt:
> 
>   https://gitlab.com/muttmua/mutt/-/issues/430
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348

I meant https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023599
here.

> It was removed without letting developers adapt their code first.
> Actually I'm not even sure that this is the right long-term decision;
> upstream code should be fixed instead.
> 
> I can see in the changelog:
> 
>* Fix FTBFS after removal of gpg-error-config (Closes: #1022348)
>* gpgme-config not installed anymore
> 
> It seems that the removal of gpg-error-config was a Debian decision
> not to keep it with its build rules:
> https://dev.gnupg.org/T5683 says "Now, we can consider deprecation
> of gpg-error-config, to show preference to gpgrt-config. [...]
> Distributions still can install it (by their own make rule), because
> gpg-error-config will be kept distributed and built well."
> 
> So, if I understand correctly, either gpgme-config should be based on
> gpgrt-config rather than gpg-error-config (this should be an upstream
> change), or gpg-error-config should be re-added as suggested.

Actually gpgrt-config can be used instead of gpgme-config. But
this requires changes in existing code, possibly non trivial,
as now done for Mutt:

  https://gitlab.com/muttmua/mutt/-/issues/430

(not yet in Debian).

So before gpgme-config gets removed (which is a *recent* upstream
change), you should make sure that existing code based on it has
been updated.

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

Processed: Re: azure-cli - incomplete dependences: ModuleNotFoundError

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1023621 [azure-cli] azure-cli - incomplete dependences: ModuleNotFoundError
Added tag(s) moreinfo.

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

Bug#1023621: azure-cli - incomplete dependences: ModuleNotFoundError

[Luca Boccassi]

Control: tags -1 moreinfo

On Mon, 07 Nov 2022 19:36:40 +0100 Bastian Blank 
wrote:
> Package: azure-cli
> Version: 2.42.0-1
> Severity: serious
> 
> Simple VM operations, like start, fail with ModuleNotFoundError.  So
some
> dependencies are incorrect.

Did you have the new python3-azure that just migrated to testing? If
not, can you try again and let me know if it helps?

-- 
Kind regards,
Luca Boccassi


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