Processed: severity of 460232 is normal

[Debian Bug Tracking System]

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

> severity 460232 normal
Bug #460232 [pam] Please clarify license
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1023442: marked as done (systemd FTBFS: python3-pyparsing:native no longer satisfiable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2022 00:34:22 +
with message-id 
and subject line Bug#1023442: fixed in systemd 252-3
has caused the Debian Bug report #1023442,
regarding systemd FTBFS: python3-pyparsing:native no longer satisfiable
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.)


-- 
1023442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 251.4-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Jan Kiszka 

systemd fails to build from source, because dpkg-checkbuilddeps now
rejects python3-pyparsing:native as it got tagged Multi-Arch: foreign. I
think this is a bug #1023438 in dpkg-checkbuilddeps, but short term,
this will have to be fixed in systemd by dropping :native from
python3-pyparsing.

I also think this partially is a failure on Jan's side. He added the
:native annotation without checking whether python3-pyparsing should
have been marked Multi-Arch: foreign first. I also wondered why Jan
needs this change in the first place. Why do you run cross builds
without nocheck?

Helmut
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 252-3
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Luca Boccassi  (supplier of updated systemd 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 14:16:52 +
Source: systemd
Architecture: source
Version: 252-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Luca Boccassi 
Closes: 1023311 1023442
Changes:
 systemd (252-3) unstable; urgency=medium
 .
   * Backport patches to fix tmpfiles error and missing /dev/serial/by-
 id/usb-* (Closes: #1023311)
   * Drop :native suffix from python3-pyparsing build dependency (Closes:
 #1023442)
   * Enable support for libqrencode. dlopen() feature so no additional cost.
 Allows printing out recovery keys in QR format.
Checksums-Sha1:
 628ca5db975d83479f675b410d6bbff9eb928974 6352 systemd_252-3.dsc
 be5bc8d68c44ac5b5febaa1788a9c6736df48354 167488 systemd_252-3.debian.tar.xz
 c536225c91bb1608fd691dd898f793d620904c3d 12287 systemd_252-3_source.buildinfo
Checksums-Sha256:
 282b88145c498277dad3afbc37fbfcab5d0efac31dd564cbf1724e49bb2af9bc 6352 
systemd_252-3.dsc
 fcbe6ea26a53c261fb743fe6299e43458544b69a661f0c879816b6c4abc0a30d 167488 
systemd_252-3.debian.tar.xz
 eccb3a27503f9035c145e5159a16fdc54602749e880e57436390d173ed9e1130 12287 
systemd_252-3_source.buildinfo
Files:
 2142ae5ce46f5ac82f8273abfe49aee8 6352 admin optional systemd_252-3.dsc
 9eebe4f800ac83e61d057b6b633d4f51 167488 admin optional 
systemd_252-3.debian.tar.xz
 1416581d50f266f860ac9599d36dc496 12287 admin optional 
systemd_252-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmNnwjYRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB50Bg//eAFlD2l6lu2IaYsIdA9bkczm+H8CE2gN
oY2h4atcoEBxClFUwDMEBe3szzuYb2k007U2eCpyZ44oACHydB1s+r1piez4bZ5W
oqznv24hwMGy4GVuY2zyuWeH6uXf9Vvx2WQfJq/krDeBZPeblRcOqvP/rbpxF/29
Z6BQyrKK9zK6Nba3wWiOVH3+yVqtz7t1NynBarcKKhmh39bUYNVDA8Q+D6UXusO8
noCHN9RRhVnmzVgQrZakq0lXfJFct622dOLJIBHiyhrGRXbhC9iAmo061XlAsbSq
L5TEk7O3DPyJJYsfVmb+JeEtHU9u3YPjOdYuxmhDbJIqyOPXkEmW1WCSyLzMkpW3
CZ038nke14fsy2cqb+2NxJoxw0Jume4eg5qSA9HNazM+y5uyhTpeq3jPOuDeWXNq
REhfKZbK/ergcm6WLNzzAWHzzPvsx7l3f0D6YOi87EKnt1KwFi2NvrOoCyptFzqB
RBFrUHLP9dzxW0/DgRIOB8k+yOCzC1AhEE5syve+dqD2gxXMIm320q3YsPg6nO0v
WuQs+ColAKPBU9NxLYqlnFbdhYGUVhyl4fYRFJng08QoAsc3j2Hyc6NQjqCElC5N
FziUU6LWB2fs1rvBmgnonksAo00vTjLeU3gcnHF6wXH/UHKWd/dU/Hz0tsj/PqWb
GKHn2dzVkww=
=EpXw
-END PGP SIGNATURE End Message ---

Bug#1019829: marked as done (pgn2web: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2022 00:28:43 +
with message-id 
and subject line Bug#1019829: fixed in pgn2web 0.4-3.1
has caused the Debian Bug report #1019829,
regarding pgn2web: Please transition to wxwidgets3.2
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.)


-- 
1019829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgn2web
Severity: normal
Control: block 1019416 by -1

Hi,

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

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: pgn2web
Source-Version: 0.4-3.1
Done: Olly Betts 

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated pgn2web 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: Mon, 07 Nov 2022 12:06:09 +1300
Source: pgn2web
Architecture: source
Version: 0.4-3.1
Distribution: unstable
Urgency: medium
Maintainer: Jose G. López 
Changed-By: Olly Betts 
Closes: 1019829
Changes:
 pgn2web (0.4-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Update to build with wxwidgets-3.2 (new patch
 wx3.2-compat.patch) (Closes: #1019829)
Checksums-Sha1:
 508cea8f3d43d7a97b8866c9ede5f8cb79eda736 1844 pgn2web_0.4-3.1.dsc
 81a0f20f09345a0363b83a90be794f4b63881f17 5176 pgn2web_0.4-3.1.debian.tar.xz
 696357a31a7677fb76c78348d07f20cb4866918d 11237 pgn2web_0.4-3.1_amd64.buildinfo
Checksums-Sha256:
 7366cc1fdc1a51170d552e98b95941ca1717d21cc62c73913bf4a15f9bed7907 1844 
pgn2web_0.4-3.1.dsc
 c94ed79b23c01f3511c853bd7a02d3e4a85b9e05b068872eeeb8a9b598b70627 5176 
pgn2web_0.4-3.1.debian.tar.xz
 3142209913255af133b7d84907b75a01f8759434e69dea22b8c09db65add6902 11237 
pgn2web_0.4-3.1_amd64.buildinfo
Files:
 77be0bf8e7e8fc5ecf3f914ffbd75c16 1844 web optional pgn2web_0.4-3.1.dsc
 26ba742e651902aadf3d9d629aec0ba0 5176 web optional 
pgn2web_0.4-3.1.debian.tar.xz
 30c4cefb3cf315ee37c781532f4ebfa9 11237 web optional 
pgn2web_0.4-3.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAmNoP6kACgkQGBR7Bzut
KwerYxAAy/dVoEHGcRuIhvn2iQpCBgg3/F3ucXlHPOobdEQC+Ii0xJZJORVZtlIj
4ikzY2FVqIGTAMPug/xKGYTLniy5H3BTz8w57dYhcI3yb6omVPNYaSmret3V00WO
l0l2L5aPOOlq6rrA6z/MGI60OD5fkHM7cLQXgvSnlHyjcCXYZIp5fq5Jrr9ZyqxW
kwEZXi2DVpBCrq4EiE/1wzO9XT6nEvg7MWKrI10BM5yIaBF8ndb9+gIuXkLBMMwV
h7koi0fNS9BxbWa68gv2IxDA0ikbfW9jKlXjol+oUHvyBG0rWiNcqfZuz38Q9w6d
KrdFMb1MZesM+PzhSDLfSEk8sv7Gst7JWC9Ne8kC0oZItZxZdrSiHdOy4T5FLxj9
uC8uRq6XfPK2hcG5Wlw4bwjfM9Vx47QeQyMlOP0uLf9xmf0k796A2Vsc/XgO/wu2
AK9ZyWSSMGjN95HZ9i6ke0IlZDz95cfg0HoGtNhrnRAja8teNOve898VK1z8cI0E
WWrJcevTjYVLK/50qoVWE9Mtr7z++H+tmIuh2yauDC/zzf0nWRYv7RkZAXUhW2gu
bLwpSp32GNL64TO0/1Gu0lyV6HXPT9kkWl9tHH/a9zdeXDKgZULeikkf0M/nhhS6
sX1tCaXj1rYzUirIDpS+PSpA6UpnTySjlCD03uvz3pvRZL3EBe8=
=1cry
-END PGP SIGNATURE End Message ---

Processed: pgn2web: diff for NMU version 0.4-3.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#1019829: pgn2web: diff for NMU version 0.4-3.1

[Olly Betts]

Control: tags 1019829 + patch

Dear maintainer,

I've prepared an NMU for pgn2web (versioned as 0.4-3.1) and
uploaded it to unstable as per the NMU guidelines in the devref:

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines

Cheers,
Olly
diff -Nru pgn2web-0.4/debian/changelog pgn2web-0.4/debian/changelog
--- pgn2web-0.4/debian/changelog	2019-10-17 08:13:27.0 +1300
+++ pgn2web-0.4/debian/changelog	2022-11-07 12:06:09.0 +1300
@@ -1,3 +1,11 @@
+pgn2web (0.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Update to build with wxwidgets-3.2 (new patch
+wx3.2-compat.patch) (Closes: #1019829)
+
+ -- Olly Betts   Mon, 07 Nov 2022 12:06:09 +1300
+
 pgn2web (0.4-3) unstable; urgency=medium
 
   * debian/control:
diff -Nru pgn2web-0.4/debian/control pgn2web-0.4/debian/control
--- pgn2web-0.4/debian/control	2019-10-17 08:13:27.0 +1300
+++ pgn2web-0.4/debian/control	2022-11-07 11:58:56.0 +1300
@@ -2,7 +2,7 @@
 Section: web
 Priority: optional
 Maintainer: Jose G. López 
-Build-Depends: debhelper-compat (= 12), libwxgtk3.0-gtk3-dev
+Build-Depends: debhelper-compat (= 12), libwxgtk3.2-dev
 Standards-Version: 4.4.1
 Rules-Requires-Root: no
 Homepage: http://sourceforge.net/projects/pgn2web/
diff -Nru pgn2web-0.4/debian/patches/series pgn2web-0.4/debian/patches/series
--- pgn2web-0.4/debian/patches/series	2019-10-17 08:13:27.0 +1300
+++ pgn2web-0.4/debian/patches/series	2022-11-07 12:05:17.0 +1300
@@ -2,3 +2,4 @@
 makefile.patch
 install-location.patch
 wx3.0-compat.patch
+wx3.2-compat.patch
diff -Nru pgn2web-0.4/debian/patches/wx3.2-compat.patch pgn2web-0.4/debian/patches/wx3.2-compat.patch
--- pgn2web-0.4/debian/patches/wx3.2-compat.patch	1970-01-01 12:00:00.0 +1200
+++ pgn2web-0.4/debian/patches/wx3.2-compat.patch	2022-11-07 12:06:04.0 +1300
@@ -0,0 +1,17 @@
+Description: Fixes for compatibility with wxWidgets 3.2
+Author: Olly Betts 
+Bug-Debian: https://bugs.debian.org/1019829
+Forwarded: no
+Last-Update: 2022-11-06
+
+--- pgn2web-0.4.orig/gui.cpp
 pgn2web-0.4/gui.cpp
+@@ -367,7 +367,7 @@ void p2wFrame::do_layout()
+   buttonsSizer->Add(convertButton, 0, wxALL, 5);
+   buttonsSizer->Add(quitButton, 0, wxALL, 5);
+   rootSizer->Add(buttonsSizer, 0,
+-		 wxLEFT|wxRIGHT|wxBOTTOM|wxALIGN_CENTER_HORIZONTAL|wxADJUST_MINSIZE, 5);
++		 wxLEFT|wxRIGHT|wxBOTTOM|wxALIGN_CENTER_HORIZONTAL, 5);
+   rootPanel->SetAutoLayout(true);
+   rootPanel->SetSizer(rootSizer);
+   panelSizer->Add(rootPanel, 1, wxEXPAND, 0);

Bug#1021032: vlc: playing videos results in a black screen

[Alexis Murzeau]

Hi,

On Sat, 08 Oct 2022 14:30:43 +0300 =?ISO-8859-1?Q?R=E9mi?= Denis-Courmont 
 wrote:

Le lauantaina 8. lokakuuta 2022, 12.40.56 EEST KeyofBlueS a écrit :
> Hi all. Let's continue here from #1021140
> 
> 
> It seems this issue it's not completely fixed. Before it was always

> reproducible under any circumstance, when now there are at least two ways
> to always trigger it:

I believe that the issue is not fixed at all.

The symptoms started showing up after Debian updated Qt, and affect only the Qt 
GUI. The last attempt to fix it affected the VA-API video decoding path in such 
a way that it will still *fail* at a different pace than it did before the fix. 
Then it will fallback to VDPAU or to software decoding path.


[...]


I'm jumping in to add information, I also get black screen issue after updating 
Qt from 5.15.4 to 5.15.6.

I also get graphical issues in the playlist, when resizing the VLC window. 
These graphical issues appear also in virtualbox-qt.

I've already created a bug on qt: #1023580
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023580

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F

Bug#1023579: lomiri-clock-app: autopkgtest depends on non-existing packages

[Adrian Bunk]

Source: lomiri-clock-app
Version: 3.13~git20221027.60c85a4-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lomiri-clock-app/27859719/log.gz

...
E: Unable to locate package autopilot-touch
E: Unable to locate package libautopilot-qt
E: Unable to locate package python3-autopilot
E: Package 'qt5-default' has no installation candidate
E: Unable to locate package lomiri-ui-toolkit-autopilot
make-testFAIL badpkg


qt5-default was removed some time ago,
I do not know the situation regarding the other packages.

Bug#1011924: marked as done (capsule-nextflow: FTBFS with OpenJDK 17 due to pack200 removal and ambiguous reference to FileSystems.newFileSystem())

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 22:19:10 +
with message-id 
and subject line Bug#1011924: fixed in capsule-nextflow 1.1.1+dfsg-1
has caused the Debian Bug report #1011924,
regarding capsule-nextflow: FTBFS with OpenJDK 17 due to pack200 removal and 
ambiguous reference to FileSystems.newFileSystem()
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.)


-- 
1011924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: capsule-nextflow
Version: 1.1.0+dfsg-4
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17


capsule-nextflow fails to build with OpenJDK 17, the pack200 API has been 
removed
and a new FileSystems.newFileSystem() makes the existing call ambiguous:


  
/<>/capsule-util/src/main/java/co/paralleluniverse/capsule/Jar.java:40:
 error: cannot find symbol
  import java.util.jar.Pack200;
  ^
symbol:   class Pack200
location: package java.util.jar
  
/<>/capsule-util/src/main/java/co/paralleluniverse/capsule/Jar.java:59:
 error: package Pack200 does not exist
  private Pack200.Packer packer;
 ^
  
/<>/capsule-util/src/main/java/co/paralleluniverse/capsule/Jar.java:570:
 error: package Pack200 does not exist
  public Jar setPacker(Pack200.Packer packer) {
  ^
  
/<>/capsule-util/src/main/java/co/paralleluniverse/common/PathClassLoader.java:57:
 error: reference to newFileSystem is ambiguous
  o = FileSystems.newFileSystem(p, null);
 ^
both method newFileSystem(Path,ClassLoader) in FileSystems and method 
newFileSystem(Path,Map) in FileSystems match
  Note: Some input files use or override a deprecated API.
  Note: Recompile with -Xlint:deprecation for details.
  Note: Some input files use unchecked or unsafe operations.
  Note: Recompile with -Xlint:unchecked for details.
  4 errors
  3 warnings
--- End Message ---
--- Begin Message ---
Source: capsule-nextflow
Source-Version: 1.1.1+dfsg-1
Done: Pierre Gruet 

We believe that the bug you reported is fixed in the latest version of
capsule-nextflow, 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.
Pierre Gruet  (supplier of updated capsule-nextflow 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 22:53:37 +0100
Source: capsule-nextflow
Architecture: source
Version: 1.1.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Pierre Gruet 
Closes: 1011924
Changes:
 capsule-nextflow (1.1.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 1.1.1+dfsg
   * Refreshing patches
   * Raising Standards version to 4.6.1 (no change)
   * Supporting OpenJDK 17 (Closes: #1011924):
 - Removing use of java.util.jar.Pack200 package, removed in OpenJDK 17
 - Disambiguation of call to newFileSystem
 - Skipping tests attempting to access security sensitive fields
 - Adding --add-exports and --add-opens in the jar invocation
   * Removing the last lines of the autopkgtest, being useless because of set -e
Checksums-Sha1:
 4232edef55d1be2fe59e2d395eb27a5d35946dc9 2262 capsule-nextflow_1.1.1+dfsg-1.dsc
 bd70bb764e73e5b8db42ff0ef1b1014108ccf769 75536 
capsule-nextflow_1.1.1+dfsg.orig.tar.xz
 ba48b562ef5ef05dba7191d5efa5ea5373764bd0 43492 
capsule-nextflow_1.1.1+dfsg-1.debian.tar.xz
 174fca3de241f495fe17b60fa517af50ee63551f 11291 
capsule-nextflow_1.1.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 c2773be10fc6111c91426d6ab8ae8373479776f33ebfa0cc3ed27e4070d97fc4 2262 
capsule-nextflow_1.1.1+dfsg-1.dsc
 805000a60409e4ef65903a9e87d9316b227952bf4a71e6ff351652317eb20a79 75536 
capsule-nextflow_1.1.1+dfsg.orig.tar.xz
 d958c6e03aaeb07843e3417f4eef50636c082c7ac5623a2a8e942cc6c43f8390 43492 
capsule-nextflow_1.1.1+dfsg-1.debian.tar.xz
 48cd40014455c04ed4a2e52a97ed9faa874e102a9c527143e2e7276bc70ec9d0 11291 
capsule-nextflow_1.1.1+dfsg-1_amd64.buildinfo
Files:
 

Bug#991358: marked as done (guile-2.2 should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 22:11:22 +
with message-id 
and subject line Bug#1023560: Removed package(s) from unstable
has caused the Debian Bug report #991358,
regarding guile-2.2 should not be in bookworm
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.)


-- 
991358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: guile-2.2
Severity: serious
Tags: bookworm sid

guile-2.2 removal didn't happen in bullseye,
but let's have a bug for that in bookworm.
--- End Message ---
--- Begin Message ---
Version: 2.2.7+1-6+rm

Dear submitter,

as the package guile-2.2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023560

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1017222: marked as done (nifti2dicom: FTBFS: build-dependency not installable: libinsighttoolkit4-dev)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 22:09:14 +
with message-id 
and subject line Bug#1023390: Removed package(s) from unstable
has caused the Debian Bug report #1017222,
regarding nifti2dicom: FTBFS: build-dependency not installable: 
libinsighttoolkit4-dev
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.)


-- 
1017222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nifti2dicom
Version: 0.4.11-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), cmake, qtbase5-dev, 
> libinsighttoolkit4-dev, libfftw3-dev, libtclap-dev, libvtk7-qt-dev, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), cmake, qtbase5-dev, 
> libinsighttoolkit4-dev, libfftw3-dev, libtclap-dev, libvtk7-qt-dev, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [415 B]
> Get:5 copy:/<>/apt_archive ./ Packages [495 B]
> Fetched 1867 B in 0s (166 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libinsighttoolkit4-dev but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/nifti2dicom_0.4.11-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.4.11-4+rm

Dear submitter,

as the package nifti2dicom has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023390

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1013157: marked as done (nifti2dicom: vtk[6,7] removal)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 22:09:14 +
with message-id 
and subject line Bug#1023390: Removed package(s) from unstable
has caused the Debian Bug report #1013157,
regarding nifti2dicom: vtk[6,7] removal
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.)


-- 
1013157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nifti2dicom
Severity: important
User: gl...@debian.org
Usertags: vtk6_vtk7_removal

Dear maintainer,

Debian archive has now three major versions of the VTK (The
Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions
(vtk6 and vtk7) are not supported by upstream and the package itself
is not easy for the mainance.

We aim to drop old and deprecated version vtk6 and vtk7 packages
before the freeze of the Debian 12 Bookworm. The severity of this
ticket will be raised to serious some time for the freeze.

Your package depends on vtk6 or vtk7. Thus we ask you to migrate it
to the latest vtk9 package.

Thanks

Anton 
--- End Message ---
--- Begin Message ---
Version: 0.4.11-4+rm

Dear submitter,

as the package nifti2dicom has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023390

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#949355: marked as done (simpleitk FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 22:08:46 +
with message-id 
and subject line Bug#1023389: Removed package(s) from unstable
has caused the Debian Bug report #949355,
regarding simpleitk FTBFS: test failures
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.)


-- 
949355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simpleitk
Version: 1.0.1-3
Severity: serious
Tags: ftbfs bullseye sid

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

...
99% tests passed, 2 tests failed out of 944

Total Test time (real) = 167.65 sec

The following tests FAILED:
244 - BasicFilters.FastMarchingBaseImageFilter (Failed)
375 - BasicFilters.LabelIntensityStatisticsImageFilter (Failed)
Errors while running CTest
make[2]: *** [Makefile:155: test] Error 8


More recent upstream releases (1.1.0 to 1.2.4) are using ITK 4.13,
upgrading will likely fix this bug.
--- End Message ---
--- Begin Message ---
Version: 1.0.1-3+rm

Dear submitter,

as the package simpleitk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1023389

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: raku-json-class: trying to overwrite '/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package raku-json

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:raku-license-spdx
Bug #1023576 [raku-json-class] raku-json-class: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.24-1
Added indication that 1023576 affects src:raku-license-spdx

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

Bug#1023576: raku-json-class: trying to overwrite '/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package raku-js

[Adrian Bunk]

Package: raku-json-class
Version: 0.0.19-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:raku-license-spdx

https://piuparts.debian.org/sid/fail/raku-json-class_0.0.19-1.log

...
  Unpacking raku-json-class (0.0.19-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-EBPyxP/19-raku-json-class_0.0.19-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.24-1
...


This looks similar to #1019579, but the fixed dh-raku was used for
building these packages

Processed: retitle 1023569 to librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1

[Debian Bug Tracking System]

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

> retitle 1023569 librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1
Bug #1023569 [librte-net-af-xdp22] librte-net-af-xdp22 is empty after rebuild 
with 1.0.1
Changed Bug title to 'librte-net-af-xdp22 is empty after rebuild with libbpf 
1.0.1' from 'librte-net-af-xdp22 is empty after rebuild with 1.0.1'.
> thanks
Stopping processing here.

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

Bug#1023574: wolfssl: CVE-2022-42961

[Salvatore Bonaccorso]

Source: wolfssl
Version: 5.2.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for wolfssl.

CVE-2022-42961[0]:
| An issue was discovered in wolfSSL before 5.5.0. A fault injection
| attack on RAM via Rowhammer leads to ECDSA key disclosure. Users
| performing signing operations with private ECC keys, such as in
| server-side TLS connections, might leak faulty ECC signatures. These
| signatures can be processed via an advanced technique for ECDSA key
| recovery. (In 5.5.0 and later, WOLFSSL_CHECK_SIG_FAULTS can be used to
| address the vulnerability.)


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-42961
https://www.cve.org/CVERecord?id=CVE-2022-42961

Regards,
Salvatore

Processed: src:ruby-liquid-c: fails to migrate to testing for too long: Build-Depends on package that can't migrate

[Debian Bug Tracking System]

Processing control commands:

> close -1 4.1.0-2
Bug #1023572 [src:ruby-liquid-c] src:ruby-liquid-c: fails to migrate to testing 
for too long: Build-Depends on package that can't migrate
Marked as fixed in versions ruby-liquid-c/4.1.0-2.
Bug #1023572 [src:ruby-liquid-c] src:ruby-liquid-c: fails to migrate to testing 
for too long: Build-Depends on package that can't migrate
Marked Bug as done
> block -1 by 1023534
Bug #1023572 {Done: Paul Gevers } [src:ruby-liquid-c] 
src:ruby-liquid-c: fails to migrate to testing for too long: Build-Depends on 
package that can't migrate
1023572 was not blocked by any bugs.
1023572 was not blocking any bugs.
Added blocking bug(s) of 1023572: 1023534

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

Bug#1023572: src:ruby-liquid-c: fails to migrate to testing for too long: Build-Depends on package that can't migrate

[Paul Gevers]

Source: ruby-liquid-c
Version: 4.0.0-2
Severity: serious
Control: close -1 4.1.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1023534

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:ruby-liquid-c has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package is stuck 
behind ruby-liquid, which has bug #1023534 filed against it.


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=ruby-liquid-c



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023571: php-cas: CVE-2022-39369: Service Hostname Discovery Exploitation

[Salvatore Bonaccorso]

Source: php-cas
Version: 1.3.8-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.3.6-1

Hi,

The following vulnerability was published for php-cas.

CVE-2022-39369[0]:
| phpCAS is an authentication library that allows PHP applications to
| easily authenticate users via a Central Authentication Service (CAS)
| server. The phpCAS library uses HTTP headers to determine the service
| URL used to validate tickets. This allows an attacker to control the
| host header and use a valid ticket granted for any authorized service
| in the same SSO realm (CAS server) to authenticate to the service
| protected by phpCAS. Depending on the settings of the CAS server
| service registry in worst case this may be any other service URL (if
| the allowed URLs are configured to "^(https)://.*") or may be strictly
| limited to known and authorized services in the same SSO federation if
| proper URL service validation is applied. This vulnerability may allow
| an attacker to gain access to a victim's account on a vulnerable
| CASified service without victim's knowledge, when the victim visits
| attacker's website while being logged in to the same CAS server.
| phpCAS 1.6.0 is a major version upgrade that starts enforcing service
| URL discovery validation, because there is unfortunately no 100% safe
| default config to use in PHP. Starting this version, it is required to
| pass in an additional service base URL argument when constructing the
| client class. For more information, please refer to the upgrading doc.
| This vulnerability only impacts the CAS client that the phpCAS library
| protects against. The problematic service URL discovery behavior in
| phpCAS  1.6.0 will only be disabled, and thus you are not impacted
| from it, if the phpCAS configuration has the following setup: 1.
| `phpCAS::setUrl()` is called (a reminder that you have to pass in the
| full URL of the current page, rather than your service base URL), and
| 2. `phpCAS::setCallbackURL()` is called, only when the proxy mode is
| enabled. 3. If your PHP's HTTP header input `X-Forwarded-Host`,
| `X-Forwarded-Server`, `Host`, `X-Forwarded-Proto`, `X-Forwarded-
| Protocol` is sanitized before reaching PHP (by a reverse proxy, for
| example), you will not be impacted by this vulnerability either. If
| your CAS server service registry is configured to only allow known and
| trusted service URLs the severity of the vulnerability is reduced
| substantially in its severity since an attacker must be in control of
| another authorized service. Otherwise, you should upgrade the library
| to get the safe service discovery behavior.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-39369
https://www.cve.org/CVERecord?id=CVE-2022-39369
[1] https://github.com/apereo/phpCAS/security/advisories/GHSA-8q72-6qq8-xv64

Regards,
Salvatore

Processed: php-cas: CVE-2022-39369: Service Hostname Discovery Exploitation

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.3.6-1
Bug #1023571 [src:php-cas] php-cas: CVE-2022-39369: Service Hostname Discovery 
Exploitation
Marked as found in versions php-cas/1.3.6-1.

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

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

[Eli Zaretskii]

> Date: Sun, 6 Nov 2022 11:44:43 -0800
> Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name,
>  58...@debbugs.gnu.org, 1017...@bugs.debian.org
> From: Paul Eggert 
> 
> On 2022-11-06 11:32, Eli Zaretskii wrote:
> > My question was whether in this scenario, since the parent Emacs
> > exits, the child Emacs can get SIGHUP, simply because its parent
> > exited and the read end of the PTY no longer exists.
> 
> Yes, my sense from the few experiments I tried, is that it's a plausible 
> scenario, though I never observed it actually happening for Emacs doing 
> a subprocess compile.

OK, thanks.  So I hope your suggested patch will solve this issue.

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

[Paul Eggert]

On 2022-11-06 11:32, Eli Zaretskii wrote:

My question was whether in this scenario, since the parent Emacs
exits, the child Emacs can get SIGHUP, simply because its parent
exited and the read end of the PTY no longer exists.


Yes, my sense from the few experiments I tried, is that it's a plausible 
scenario, though I never observed it actually happening for Emacs doing 
a subprocess compile.

Bug#1023569: librte-net-af-xdp22 is empty after rebuild with 1.0.1

[Adrian Bunk]

Package: librte-net-af-xdp22
Version: 21.11-5
Severity: serious

$ dpkg -L librte-net-af-xdp22
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/librte-net-af-xdp22
/usr/share/doc/librte-net-af-xdp22/changelog.Debian.amd64.gz
/usr/share/doc/librte-net-af-xdp22/changelog.Debian.gz
/usr/share/doc/librte-net-af-xdp22/copyright
$

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

[Eli Zaretskii]

> Date: Sun, 6 Nov 2022 11:18:03 -0800
> Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name,
>  58...@debbugs.gnu.org, 1017...@bugs.debian.org
> From: Paul Eggert 
> 
> On 2022-11-05 22:51, Eli Zaretskii wrote:
> 
> > But is it possible for a program like Emacs to get SIGHUP in such a
> > situation, or is that highly improbable?  We have standard streams of
> > the inferior Emacs process connected via PTYs to the parent process, I
> > believe -- does that deliver SIGHUP or SIGPIPE when the parent exits?
> 
> It depends on the OS and the app that invokes Emacs and how that app 
> itself was invoked. It's a hairy area.
> 
> On a POSIX platform it's certainly *possible* for Emacs to get SIGHUP in 
> that situation, because a user can invoke the shell command 'kill -s HUP 
> P', where P is the process ID of the inferior Emacs. Whether it's 
> *likely* is a bit harder to say. I ran a few little experiments on 
> Fedora 36 and Ubuntu 22.10 and found SIGHUP being sent in a few 
> situations and not others and didn't have the time or patience to suss 
> out exactly why or when.

Thanks.  The scenario that is of primary interest in this case is the
following:

 . user starts Emacs
 . Emacs loads some Lisp package and as results starts a subordinate
   Emacs process in batch mode to native-compile the loaded Lisp
 . user exits Emacs

My question was whether in this scenario, since the parent Emacs
exits, the child Emacs can get SIGHUP, simply because its parent
exited and the read end of the PTY no longer exists.

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

[Paul Eggert]

On 2022-11-05 22:51, Eli Zaretskii wrote:


But is it possible for a program like Emacs to get SIGHUP in such a
situation, or is that highly improbable?  We have standard streams of
the inferior Emacs process connected via PTYs to the parent process, I
believe -- does that deliver SIGHUP or SIGPIPE when the parent exits?


It depends on the OS and the app that invokes Emacs and how that app 
itself was invoked. It's a hairy area.


On a POSIX platform it's certainly *possible* for Emacs to get SIGHUP in 
that situation, because a user can invoke the shell command 'kill -s HUP 
P', where P is the process ID of the inferior Emacs. Whether it's 
*likely* is a bit harder to say. I ran a few little experiments on 
Fedora 36 and Ubuntu 22.10 and found SIGHUP being sent in a few 
situations and not others and didn't have the time or patience to suss 
out exactly why or when.

Bug#937049: mini-buildd: Python2 removal in sid/bullseye

[Stephan Sürken]

Hi Moritz,

On Fri, 2022-10-28 at 00:12 +0200, Moritz Mühlenhoff wrote:
> Am Fri, Aug 30, 2019 at 07:26:40AM + schrieb Matthias Klose:
> > Package: src:mini-buildd
> > Version: 1.0.41
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> > 
> > Python2 becomes end-of-live upstream, and Debian aims to remove
> > Python2 from the distribution, as discussed in
> > https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> How close is the 2.x branch in experimental from being a replacement?
> python2 will be dropped in bookworm and also removed from the archive.

it's taking way too long already ;), but I am still quite confident to be
able to upload to unstable this year, i.e., before Debian freeze/bookworm.

Hth!

S

Bug#1022343: marked as done (view3dscene: FTBFS: view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by view3dscene)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 18:58:53 +
with message-id 
and subject line Bug#1022343: fixed in view3dscene 4.2.0-1
has caused the Debian Bug report #1022343,
regarding view3dscene: FTBFS: view3dscene.lpr(63,17) Fatal: Can't find unit 
CastleCubeMaps used by view3dscene
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.)


-- 
1022343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: view3dscene
Version: 4.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>/embedded_data/screen_effects'
> file_to_pascal_string flashlight.glsl screen_effects_flashlight.glsl.inc
> file_to_pascal_string edge_detect.glsl screen_effects_edge_detect.glsl.inc
> make[3]: Leaving directory '/<>/embedded_data/screen_effects'
> make[2]: Leaving directory '/<>'
> fpc -k"-z relro -z now" -dRELEASE -Mobjfpc -Sh -Ci -Sm -Sc -Sg -Si -O2 -Xs 
> -Fu/usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/castle-game-engine  
> code/view3dscene.lpr
> Compiling Release Version
> Free Pascal Compiler version 3.2.2+dfsg-15 [2022/08/20] for x86_64
> Copyright (c) 1993-2021 by Florian Klaempfl and others
> Target OS: Linux for x86-64
> Compiling code/view3dscene.lpr
> view3dscene.lpr(60,21) Warning: Unit "CastleProgress" is deprecated: "use 
> TUIState and WaitForRenderAndCall to display progress of loading operations"
> view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by 
> view3dscene
> Fatal: Compilation aborted
> Error: /usr/bin/ppcx64 returned an error exitcode
> make[1]: *** [debian/rules:53: override_dh_auto_build-arch] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/view3dscene_4.0.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: view3dscene
Source-Version: 4.2.0-1
Done: Abou Al Montacir 

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

Debian distribution maintenance software
pp.
Abou Al Montacir  (supplier of updated view3dscene 
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 18:54:46 +0100
Source: view3dscene
Architecture: source
Version: 4.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Abou Al Montacir 
Closes: 1022343
Changes:
 view3dscene (4.2.0-1) unstable; urgency=medium
 .
   * Updated gbp import filter to exclude automatically generated files.
   * New upstream version 4.2.0 (Closes: Bug#1022343)
   * Updated Debian build rules and patches to fit new release changes.
Checksums-Sha1:
 666cae27490666ce63e6477b9e1061341be5f698 1671 view3dscene_4.2.0-1.dsc
 5b77e81d4dd6626f21ab689f39c3ba9ee6c45f06 463780 view3dscene_4.2.0.orig.tar.xz
 c91acf0fcc14f07f721b39d35fbb6039528a7502 8648 view3dscene_4.2.0-1.debian.tar.xz
 3dd17496e7cfb5506ffcbfd5db89bcc196f95ca0 15629 
view3dscene_4.2.0-1_amd64.buildinfo
Checksums-Sha256:
 9c6cd67f797533e5d5c361809ffd98bf505b5f1c2be1056d6c2dd2f0c79814ac 1671 
view3dscene_4.2.0-1.dsc
 91f21db241b7dc4a60956b43bff054cba42ac40b878495d6e6a7bceff779c459 463780 
view3dscene_4.2.0.orig.tar.xz
 

Bug#1022451: marked as done (qcat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 18:54:35 +
with message-id 
and subject line Bug#1022451: fixed in qcat 1.1.0-5
has caused the Debian Bug report #1022451,
regarding qcat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.10 returned exit code 13
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.)


-- 
1022451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qcat
Version: 1.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner_simple.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/__init__.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/eval_roc.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/cli.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner_base.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/layout.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner_dual.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner_brill.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner_guppy.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/scanner_epi2me.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/eval_full.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/config.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/calibration.py -> 
> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/adapters.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/eval.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> copying qcat/utils.py -> /<>/.pybuild/cpython3_3.10/build/qcat
> creating /<>/.pybuild/cpython3_3.10/build/qcat/resources
> creating /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/PBC096_5p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/NBD114_5p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/NBD114_3p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/simple_extended.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/DUAL_5p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RAB204_RAB214_5p_c.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/NBD104_5p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RAB201_3p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/VMK001.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/PBK004_LWB001_3p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RPB004_RLB001.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/simple_standard.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RAB214_3p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RAB201_5p_c.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RAB204_RAB214_3p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RAB214_5p_a.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/PBK004_LWB001_5p.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RBK001.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/RBK004.yml -> 
> /<>/.pybuild/cpython3_3.10/build/qcat/resources/kits
> copying qcat/resources/kits/NBD104_NBD114_3p.yml -> 
> 

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Sudip Mukherjee]

On Sun, Nov 6, 2022 at 3:51 PM Sebastian Ramacher  wrote:
>
> Source: fastnetmon
> Version: 1.2.3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org, sudipm.mukher...@gmail.com
>
> https://buildd.debian.org/status/fetch.php?pkg=fastnetmon=amd64=1.2.3-1%2Bb1=1667748889=0

oops, sorry I missed it in my list of packages depending on libbpf. It
seems "fastnetmon" added the dependency on libbpf with the last upload
and I generated my list before that.   :(

Please let me know if you want me to help with a patch to port the
code to libbpf.


-- 
Regards
Sudip

Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

[Adrian Bunk]

On Fri, Oct 07, 2022 at 02:16:35PM -0300, Antonio Terceiro wrote:
>...
> But nothing in ruby-ahoy-email codebase uses net/smtp explicitly, so
> this is a bit weird.
>...

$ cat 
/usr/share/rubygems-integration/all/gems/actionmailer-6.1.7/lib/action_mailer/mail_with_error_handling.rb
# frozen_string_literal: true

begin
  require "mail"
rescue LoadError => error
  if error.message.match?(/net\/smtp/)
$stderr.puts "You don't have net-smtp installed in your application. Please 
add it to your Gemfile and run bundle install"
raise
  end
end
$


There is also something that might be related in
https://sources.debian.org/src/rails/2%3A6.1.7%2Bdfsg-2/Gemfile/#L140

Is there a bug in rails?

cu
Adrian

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 17:43:55 +
with message-id 
and subject line Bug#999017: fixed in xfractint 20.4.10-3
has caused the Debian Bug report #999017,
regarding xfractint: 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.)


-- 
999017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfractint
Version: 20.4.10-2.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: xfractint
Source-Version: 20.4.10-3
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
xfractint, 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 xfractint 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:59:43 -0300
Source: xfractint
Architecture: source
Version: 20.4.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 999017
Changes:
 xfractint (20.4.10-3) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group . (see: #1001579)
   * debian/rules: Add build-{arch,indep} (Closes: #999017).
Checksums-Sha1:
 198d665efa9e1781e316afc868e6345c0e67a2ea 1759 xfractint_20.4.10-3.dsc
 ee84de8869f90b68024de192af18d545dedb9997 5366 xfractint_20.4.10-3.diff.gz
 ad4ff55bd2a1e964c7166e75457d4c64fa97e9c8 6323 
xfractint_20.4.10-3_source.buildinfo
Checksums-Sha256:
 87053e28279fc9ae31332a84b5407197dba10e375dd1bcb967509a333bdda3d1 1759 
xfractint_20.4.10-3.dsc
 e7811e43f997c951cc4a215a268d64bd57ca3ba50eb0e702b731a873b0802e5b 5366 
xfractint_20.4.10-3.diff.gz
 995d55c75075b823d0537e0d6f0421e2fca303271eec1d59d78ef698453a1b8f 6323 
xfractint_20.4.10-3_source.buildinfo
Files:
 1b3d89de222cfac8ba64e6cd171a1da8 1759 non-free/graphics optional 
xfractint_20.4.10-3.dsc
 b76710e6b3569469ba6aaab75516adfe 5366 non-free/graphics optional 
xfractint_20.4.10-3.diff.gz
 5e711de050c091b5869909ff72285285 6323 non-free/graphics optional 
xfractint_20.4.10-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn6IEACgkQ9LqqgNso
ukzm4A//WY8A2p8EHd0dGNwyHKOJdDnWJYM0x4wyrYsFjZ0brxq3zLRdqi4SxjyK
PuUuPThFv06TO+ksAOG6Phpfuv2KBDea/sioM/Wcjc8HIvRwhpYQQXGEK/UtdzoS
0qQAtWX22YHWztEg8+nB1tjhXR/VT/VFBpYTVc/WEht0FrjaSsXi/eG+PdHnDgXu
FHM2G6CiYFnBhkVXg7iSW+WwWy7Enubpd2N8ytgJVrpr4yjVytmDDFm/VG6BThMj
NOeQHns1KawHCPqzSREYwchQsiz0Dx+5L+bnaiHgXkKv6cFTZ2kW9TvxxqFnhaOB
PrtUSe3uN9/iNjRydZYa8z3WAtMYclOe6Z3186rbglW1EvcF+AQjCwM3EVhj+orz
Lpa1DXLsoHsfbvUVQdYOlEky8F58I09tcAzReHs48jvXTvPcCDC1xfTyyEvP2kzL
O/VY9YDWq4ClQbuJ7OHyCMhMJ2mzFlHexhCnrpJj2GoUYUN0zplpM0Gc5W7ieBQi
BlPJUQGFBykPop6B4+kg1MevZCcZwp02SuPq0OcIvfTcbhLiPWComcg+h995do02
fuwWUBxNZBckx9l2CwR4nWFc42N2pwANuA5icpAqnBbEPzdKKIk08P29ijLEJ9xG
7gH3PmErPe2fxtgs33a3p2rI+b/CIn2fcGUf6EO2m5yjtwmQmHE=
=dpgi
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 17:36:27 +
with message-id 
and subject line Bug#999035: fixed in gerstensaft 0.3-5
has caused the Debian Bug report #999035,
regarding gerstensaft: 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.)


-- 
999035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gerstensaft
Version: 0.3-4.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: gerstensaft
Source-Version: 0.3-5
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
gerstensaft, 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 gerstensaft 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:57 -0300
Source: gerstensaft
Architecture: source
Version: 0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 999035
Changes:
 gerstensaft (0.3-5) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group . (see: #934422)
   * debian/rules: Add build-{arch,indep} (Closes: #999035).
Checksums-Sha1:
 59183ca39c1aca5da435bbeb03d779a8f66f1b07 1710 gerstensaft_0.3-5.dsc
 08bebd24c8a7b6671d50d24d2ba4ef96890febbd 9304 gerstensaft_0.3-5.diff.gz
 15873ce4907b3ecb1153654877036d8be98210d3 10269 
gerstensaft_0.3-5_source.buildinfo
Checksums-Sha256:
 38ce0c2d1e54863e79f896b6a0810b8844905a5378f583a56d4fbc4117fd8d98 1710 
gerstensaft_0.3-5.dsc
 e5b9b818d46200078a3f503f1093afa212c0a1a4c4af05a1292e251fd17e04c3 9304 
gerstensaft_0.3-5.diff.gz
 de26aa2da08f816a35f5fe1c353115adfb040aae5991b0f8774f3ad1bf126447 10269 
gerstensaft_0.3-5_source.buildinfo
Files:
 c737a2db9748d3731a5e148553a681d8 1710 net extra gerstensaft_0.3-5.dsc
 64fdae17ed1f8685921482c739c6da52 9304 net extra gerstensaft_0.3-5.diff.gz
 1a79768b75f51067d8f66aa09b602181 10269 net extra 
gerstensaft_0.3-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn520ACgkQ9LqqgNso
ukyxwBAAoYc2DyLeZnYifgh8yTnqdfRBaZggXo7RBo7Uw4MDyIPfqn9M+zSk5VDi
6TkbYMBsP18YDpSULn537sHsSmNsO6X0h9++bgL3Krmx+049ACeqNMzzcQ3VsUVG
0WdffrMe1iEHZf9XegEu/0giofsVTJ+CM3xhKBHvKsBvQFdylUfC3nBubzLX6dqJ
kI9idfy7RZgUAWdfI27WDYOI8rOqNvedOfq7T7hb+HHca0XrQRx45iXhH/B8ymjH
Qx12jvY2uvWVOKeTBcWftrTG+7Ql1ayfxKwY1A01l7bj40YJfjC5W8PATzSXwbu1
qcTWskZABLKpXZUNnuY6+ZPL7O+Y9PPZhe5rSbofJg4UIFi9s+9VEk5e0wNIrzjp
Jmfsuj+cykKy08f2ze2TVY1+dFRN8y8+yZj55Z7PqmZUysjH+qw1p0BX0Xj7KKMy
v46CgO7+H4AKT4fbO8P8OZQ9jOOeCizHs4aSkjYISHiOZB0b00gYmuV1t4zKmp+r
Nrxnj6b9fbEym0tELH/KbZsDccKa/gAJ6zJ8qEmsfYGh4ZBixUxP7MCyuv2fLyRm
scJp3xHVxv3IbhvNnZKKZQJnlR3BQFZDml5Og9unc4ls5sTLMGHk/1w0hT1V46X5
EFe0buMS+Ixbjnt9BSWfan8PiedfQbYJC/xZN2d3Qw5tYW9HdzE=
=ndX4
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 17:05:52 +
with message-id 
and subject line Bug#999183: fixed in dhcpdump 1.8-3
has caused the Debian Bug report #999183,
regarding dhcpdump: 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.)


-- 
999183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dhcpdump
Version: 1.8-2.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: dhcpdump
Source-Version: 1.8-3
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
dhcpdump, 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 dhcpdump 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:49:23 -0300
Source: dhcpdump
Architecture: source
Version: 1.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 999183
Changes:
 dhcpdump (1.8-3) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group . (see: #934419)
   * debian/rules: Add build-{arch,indep} (Closes: #999183).
Checksums-Sha1:
 64e8d67a167424126bfe6bfdc63309ee3d98ebb7 1626 dhcpdump_1.8-3.dsc
 0973c32cc7d704c60f1aa8ab181ecbfe90a027e5 5151 dhcpdump_1.8-3.diff.gz
 2d87577e68a674238395678bcc6cfb001b884b6f 4999 dhcpdump_1.8-3_source.buildinfo
Checksums-Sha256:
 a32dcb37258e1f48b6f899b04e60a38294c0b458fab7a5d1645cb4d636017885 1626 
dhcpdump_1.8-3.dsc
 949a77f6843e388e6367e0b3f245803de46c29d4940f0d9daebcd7bb2fd84152 5151 
dhcpdump_1.8-3.diff.gz
 535cd5249a5ee30a58bb829f4d9974797d7c71c47eb6ddb87aec2221419c0895 4999 
dhcpdump_1.8-3_source.buildinfo
Files:
 5fe9a44256b0be2f5ac75eef118e5395 1626 admin optional dhcpdump_1.8-3.dsc
 7d4cfec7838c70b6b5d2ddc7509856cf 5151 admin optional dhcpdump_1.8-3.diff.gz
 d2385c676f8098057523115fa44be837 4999 admin optional 
dhcpdump_1.8-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn5g0ACgkQ9LqqgNso
ukxzJQ//SvR2V/7rgzg4nYMxdiJAlVydulI7wvNeQPyKKkZfv/L+GIqHtheVRrt5
BxWcn+4D0nMPr0MrzOQG7JVV+pCgf0+BPJvTG+IL/sIERwAYVql3gKJmI8+wWc5/
FAcJbPMjQWjuDk0/uv8VuXoc/l+y8eGJnycWiS5dzlpiYAUPQSo7KDloslUcDKPG
PtU1NbUfiWezz3xDHQU0RXbq+Lltpwp5Up8OViyGeONey+mbbPir+cbzRgJet1nv
4uVxwfa4KhtIrgFIGuRJVRda2idU4ElKTD0ILngS2rVUEvwh2LHZx8BU8tfbcSNq
56oAjYu9DqVMstn6L6710rUc3jybEowwXCyFh/fzBEzK3QXxIjXa58z1yZNboGcd
dtmrFLDhWoAA0EzzjaGCtmwg4yQ38ZLckLRK6Jwe5O40WzDjwks1+ctlawFUnKQV
1XM1CmHDRKRL/B1MNnqOyTwjDNmGs9smLPJHGzdCuM/qxRTEYf2JVM9cfObV35X3
KsS+dPd7u/vtvCNU6YF9DYun0xvKhbyNfH5doShOyPipCaxFLSLY4vTHJeCxVRpv
PtouUpusH96zcisV2WpuGdF+r3WcLKez+i8GLEW5oEN0katdy0qxFHqtJzFoXUAU
g15s82fBjQYXqtdTV5wefMKw5mbRCgbf9aV47KdBbZEc8JGoAXI=
=NxLb
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 17:05:59 +
with message-id 
and subject line Bug#999124: fixed in dhis-server 5.3-3
has caused the Debian Bug report #999124,
regarding dhis-server: 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.)


-- 
999124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dhis-server
Version: 5.3-2.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: dhis-server
Source-Version: 5.3-3
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
dhis-server, 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 dhis-server 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:53:05 -0300
Source: dhis-server
Architecture: source
Version: 5.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 999124
Changes:
 dhis-server (5.3-3) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group . (see: #963913)
   * debian/rules: Add build-{arch,indep} (Closes: #999124).
Checksums-Sha1:
 25edc6dcd62a8427889d207a43678402b1884c3b 1724 dhis-server_5.3-3.dsc
 14a6e2a9f867ffdb7185211b8a01b7339fe80ebb 9848 dhis-server_5.3-3.debian.tar.xz
 6d8189388cac527b02644c8cc267804bdb89e93d 5886 
dhis-server_5.3-3_source.buildinfo
Checksums-Sha256:
 4fe0e542146901a4ee3e9e3ae21e0b9d66cab2fb0433b40b7484cc69d374c50c 1724 
dhis-server_5.3-3.dsc
 427b80441b2e767d70f927bb52b380735f1ae1a19c3b80bcaf44b59fd4013675 9848 
dhis-server_5.3-3.debian.tar.xz
 28a610de3e5b3083e12150e41ce64ec88c50f30b88a66966b5e932a0127eff58 5886 
dhis-server_5.3-3_source.buildinfo
Files:
 abc3b75b3c9a09cab78484235b70255e 1724 net optional dhis-server_5.3-3.dsc
 dd683f57e19c8f3e5992235e0034c0d6 9848 net optional 
dhis-server_5.3-3.debian.tar.xz
 88b1114b018e178ecca599faee5781e0 5886 net optional 
dhis-server_5.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn5r8ACgkQ9LqqgNso
ukwCEBAAm7rYt5pcm6shQS3qO49WysfZWSwgFsoA3lCeYB5/DezWMtYhJAhpKKHR
uFCrOBN8AXyVo/JbS9q2Xv6+DqBgPBQfnD2tYIaNI4/Paks3EOfjNc4rZevCXizG
qMy/s6hc5J/JqARV7eegL+2/B1WGJ6HYIodVmPfW9HMRchPM5/FZW9OvrQSJClW3
VVtgbD++HShm2F9UmGDu8mEsUWKXgceUwXyPfr4MgUbfvKdwBg8QLvgMaR9Fp++G
qk3K1tYN/DKI+mFEvcmX4+TQfqxEgNxtKAeWLKa/hFLnK6Z4kNXeB+4bNAw0ADI4
sDsWMjtM6+++Up2rXn4/D4btQLB67gsloHMmQMZq/IxTjhNpDZY0a+Cw8HcENUnq
LiDWDDFmelpBUBeXpGV+4XsqOn3ffLnvl4wiwJXrFCLRlF+2rEK3iOtq5vCcvSuT
RwbCcz23XL9heZ8OOwdnfj/nFcl6ZLRLfv8o0/5dMTN0DM6xc0882TB7fr73RWwI
01wm2M9oITxwPguPmgAGrg66mtvEX3hH1+oj22DkJBDS0Kd+GBcx/p6wOQ5MFVOb
ZNEBMSiblhA3nr1q2+o2UZ9StqxSYUpRK4zOJYgOFaLOu4YLSAyNDc770x9v4w/y
9u1pCiId5YZqLHjgw1h5UBMQ5eLrtbGwg4AuUUJ/UWjiojtpyho=
=JTdd
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 17:04:54 +
with message-id 
and subject line Bug#999096: fixed in cpufreqd 2.4.2-3
has caused the Debian Bug report #999096,
regarding cpufreqd: 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.)


-- 
999096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpufreqd
Version: 2.4.2-2.3
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: cpufreqd
Source-Version: 2.4.2-3
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
cpufreqd, 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 cpufreqd 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:43:54 -0300
Source: cpufreqd
Architecture: source
Version: 2.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 999096
Changes:
 cpufreqd (2.4.2-3) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group . (see: #933160)
   * debian/rules: Add build-{arch,indep} (Closes: #999096).
Checksums-Sha1:
 7928cc5b5278fee15862aca671a7161da21e4e8e 1875 cpufreqd_2.4.2-3.dsc
 5c057ecef94fe067f7c7cbca6248d9c4be1eb59a 11932 cpufreqd_2.4.2-3.debian.tar.xz
 fc541e48639b3ddcd2aa92385a5df7b2279833bd 6103 cpufreqd_2.4.2-3_source.buildinfo
Checksums-Sha256:
 28c722a564391d422d29e6f5831c24b13cf0639723da97a09aeaef4cb299327b 1875 
cpufreqd_2.4.2-3.dsc
 910a560e3fdcadfd4bf357c75f4dcb13f68ea43f2dc7c2f9aa2bf071a4e385a2 11932 
cpufreqd_2.4.2-3.debian.tar.xz
 4d3145ae35e30aafb1c35509aaa13586bb735af81bae86b10be69e6cbd242b83 6103 
cpufreqd_2.4.2-3_source.buildinfo
Files:
 1ad3a8e8e31e021e6d1063c1f6d4f6db 1875 admin optional cpufreqd_2.4.2-3.dsc
 2527d998a574c3da23e67e09449368d3 11932 admin optional 
cpufreqd_2.4.2-3.debian.tar.xz
 947d743c1a4ed51d8f716287e9b569c0 6103 admin optional 
cpufreqd_2.4.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNn5S4ACgkQ9LqqgNso
ukz0OA/+OkClBbgfKjgC0+OUEOihwjAW7pamE6XLNH0mqk+xEG0k5Gm9hhgtZiu4
U3P9LNcENdIH+oS/M25m7IH4/lN3Jf0x5gVfadFzlqvlbIOa3NN0uHTglm0at4OL
CGPo17W8sTu9Em0Cn0svqDSql+QfZzaIR/ZXsINdyXCcoRZtX2Dz5bs+ujTuaPVl
Adi1+vJcCK9CSL1/ylC2ksxIXFSGNxoxONkbLjsSECJxQ+iplxDR3INJ/V6XtGFG
Vy0n9XSCyBchEKwO08M2QNDI5MV9AS7gfQp2MHVMIe11Fu992quPtDJBiQ4wWNr6
Yda60Rz3b+jUh54Asagh7cLzqHglT2IP210Vo0WUzOhgkIBmqkI0gl35DMP4u2e8
BzgbA+ro02KaTh66wsRiqEJBUxMbHdWXsoikxxn0ZF06v1YjSh8tvrGLhOgimQ7+
A6+YNBG8HKyjpO56MgNxMZsqCN19Xf01rZvAxpWHlvXvhyf8gIeDVbbI/S5OoadW
UoW/fJUrxqwUYkEQa6+zG+/jpOQDM2e9B3vNXe7ms0+tgQsM/XWSdVqBbwavk8CU
w9Um6BdiNLz6ODRmtnSEpBWdCrplYBbgJ8w+DmJy+fTlaQr3nPtcAfm8urCi8pFT
reeUlMBZyYp5Ym+zddQig+GVv72czEypQtJfMyKAHCjyYIRWVdQ=
=Kq3f
-END PGP SIGNATURE End Message ---

Processed: tagging 1016279

[Debian Bug Tracking System]

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

> tags 1016279 + fixed
Bug #1016279 {Done: Adrian Bunk } [src:libzypp] libzypp: 
FTBFS: Random.cc:21:27: error: ‘time’ was not declared in this scope
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#999296: tagcloud: diff for NMU version 1.4-1.3

[Marcos Talau]

Control: tags 999296 + patch
Control: tags 999296 + pending


Dear maintainer,

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

Regards.
diff -u tagcloud-1.4/debian/changelog tagcloud-1.4/debian/changelog
--- tagcloud-1.4/debian/changelog
+++ tagcloud-1.4/debian/changelog
@@ -1,3 +1,10 @@
+tagcloud (1.4-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999296).
+
+ -- Marcos Talau   Sun, 06 Nov 2022 13:35:39 -0300
+
 tagcloud (1.4-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u tagcloud-1.4/debian/rules tagcloud-1.4/debian/rules
--- tagcloud-1.4/debian/rules
+++ tagcloud-1.4/debian/rules
@@ -67,4 +67,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary

Processed: tagcloud: diff for NMU version 1.4-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 999296 + patch
Bug #999296 [src:tagcloud] tagcloud: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999296 + pending
Bug #999296 [src:tagcloud] tagcloud: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#1020525: marked as done (ddskk: fails to install with emacs 1.28)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 16:34:32 +
with message-id 
and subject line Bug#1020525: fixed in ddskk 17.1-9
has caused the Debian Bug report #1020525,
regarding ddskk: fails to install with emacs 1.28
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.)


-- 
1020525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ddskk
Version: 17.1-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

  Preparing to unpack .../archives/ddskk_17.1-8_all.deb ...
  Unpacking ddskk (17.1-8) ...
  Setting up ddskk (17.1-8) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install ddskk for emacs
  install/ddskk: Handling install for emacsen flavor emacs
  ERROR: install script from ddskk package failed
  dpkg: error processing package ddskk (--configure):
   installed ddskk package post-installation script subprocess returned error 
exit status 1
  Processing triggers for install-info (6.8-6) ...
  Errors were encountered while processing:
   ddskk

This does not happen in testing which still has emacs 1.27.

(This could be another instance of #1020258, but there is no output
from the actual error available in the log.)

cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: ddskk
Source-Version: 17.1-9
Done: Tatsuya Kinoshita 

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

Debian distribution maintenance software
pp.
Tatsuya Kinoshita  (supplier of updated ddskk 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 01:10:34 +0900
Source: ddskk
Architecture: source
Version: 17.1-9
Distribution: unstable
Urgency: medium
Maintainer: Tatsuya Kinoshita 
Changed-By: Tatsuya Kinoshita 
Closes: 1020525
Changes:
 ddskk (17.1-9) unstable; urgency=medium
 .
   * Prevent native compilation in emacsen-install (closes: #1020525)
   * Remove empty maintainer scripts
   * Update Standards-Version to 4.6.1
   * Update debian/copyright
Checksums-Sha1:
 400d5f7c0fbfd3e0648568a267947115e863d9d0 1813 ddskk_17.1-9.dsc
 faf9e5599656fb0283b81b6565f86aa40a93d11e 13980 ddskk_17.1-9.debian.tar.xz
 03d6053ec09a76a1d671026457aaa688b666dc81 6938 ddskk_17.1-9_amd64.buildinfo
Checksums-Sha256:
 238861e846268bd8edfdafb32be92ce6945ffe4aac590f52bf5e57ccfa2fef83 1813 
ddskk_17.1-9.dsc
 2cd9bf0cb0a86228e5e4a4a652b69530414262e78afc700da4237af7f6b346a1 13980 
ddskk_17.1-9.debian.tar.xz
 647207e790282cc4aedf6846f37570bf5e61b1623e7ed1c6230ed3527fdd7650 6938 
ddskk_17.1-9_amd64.buildinfo
Files:
 dfd28e7cd88cd610f56e7b0e49eb12ce 1813 lisp optional ddskk_17.1-9.dsc
 452e0eb969800ea99c074d44abb45a12 13980 lisp optional ddskk_17.1-9.debian.tar.xz
 2595dbb71da38bb3ae2404be100e2fd6 6938 lisp optional 
ddskk_17.1-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAxxiPZTvHz7xexyE5e+rkAgOpjwFAmNn3fcACgkQ5e+rkAgO
pjwjHg/8CIDRJNqg6pAV20ZiZ3aXvD44VHmrEQUEaMBKAZTPXTybJDp8py1sij24
ZdlBY2zKo1+mpsMW1X30cHdIOrEO6ZVbqdAmL9QY2S8eriPBqUfs5fWXf8wCFzY9
r1P5a3hCZgrRCrfXem7DNV2GVUJRwv4JXJGKVM6tIur/JtWsfIUDlTwS/v59N4Hb
lC1N9UIjJup3rsiN4UIDwySMLoBP39LU5wjE1XGpZFcr6jHpTCxcDKx4y2/2bTRF
mTR/VDTjULjzOEvYOCAhs9dzX3EeZYW4oabvnfkgUdG47ciHjybygFeW4dvkQ+1I
TUYJnpeK+lkjVe5pJaGwORFVMqDIbUdPWubPoBD+J/9EPTyNu9W2Vy54Z2z3o63a
R7XS7sj1QBDPIJRr0lc7YV2Z++JZhmAH2PrmtwJ4XYCTz/GS64yL1AkkJavXnjAH
M4zHQ0mFqu5oPkMdsS2carhoctKK4CBZoIYmujtVku0Dl9M75c4m5Opz4vG376bA
KeJkmd4GiY8IbrJyGPfKQQ4gIIkNWqEnMyqKXSF6hP1CUJish2dphrm6bQvkbb12
OsglYY9nFj9a2NB7A/67/yBL0z+sllAa34MUcvHL8ptNYwxVRefiEwOSZam1skPq
LwdWdTKzgZ+TbH84zh+r3s0tw9dmtaMHuFRjcXG6IU8IykZ56P8=
=fQWo
-END PGP SIGNATURE End Message ---

Processed: spew: diff for NMU version 1.0.8-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 998965 + patch
Bug #998965 [src:spew] spew: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 998965 + pending
Bug #998965 [src:spew] spew: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#1020258: Bug#1020525: ddskk: fails to install with emacs 1.28

[Tatsuya Kinoshita]

On 2022-09-22 at 19:23 +0200, Andreas Beckmann wrote:
> (This could be another instance of #1020258, but there is no output
> from the actual error available in the log.)

As you say, it seems affected by #1020258.

```
  emacsen-common: Handling install of emacsen flavor emacs
  Install ddskk for emacs
  install/ddskk: Handling install for emacsen flavor emacs
  Loading /usr/share/emacs/site-lisp/ddskk/SKK-CFG...
  *** WARNING: Adding advice to subr keyboard-quit without mirroring its 
interactive spec ***
  Eager macro-expansion failure: (native-compiler-error (lambda () 
(let ((f #'abort-recursive-edit)) (funcall f))) "Loading 
/etc/emacs/site-start.d/00debian.el (source)...
  Loading /etc/emacs/site-start.d/50ddskk.el (source)...
  Compiling 
/root/.emacs.d/eln-cache/28.2-310448e3/subr--trampoline-61626f72742d7265637572736976652d65646974_abort_recursive_edit_0.eln...
  ld: cannot find crti.o: No such file or directory
  libgccjit.so: error: error invoking gcc driver
  Debugger entered--Lisp error: (native-ice \"failed to compile\" 
\"/root/.emacs.d/eln-cache/28.2-310448e3/subr--tramp...\" \"error invoking gcc 
driver\")

comp--compile-ctxt-to-file(\"/root/.emacs.d/eln-cache/28.2-310448e3/subr--tramp...\")

comp-compile-ctxt-to-file(\"/root/.emacs.d/eln-cache/28.2-310448e3/subr--tramp...\")
comp-final1()

load-with-code-conversion(\"/tmp/emacs-int-comp-subr--trampoline-61626f72742d7...\"
 \"/tmp/emacs-int-comp-subr--trampoline-61626f72742d7...\" nil t)
command-line-1((\"-l\" 
\"/tmp/emacs-int-comp-subr--trampoline-61626f72742d7...\"))
command-line()
normal-top-level()
```

>   ld: cannot find crti.o: No such file or directory
>   libgccjit.so: error: error invoking gcc driver

BTW, crti.o is provided by libc6-dev.  When libc6-dev is installed,
this problem doesn't occur.

As a workaround, I've set (setq comp-enable-subr-trampolines nil)
in the install/ddskk script.

Thanks,
--
Tatsuya Kinoshita


pgpBo0Egqb3K4.pgp
Description: PGP signature

Bug#998965: spew: diff for NMU version 1.0.8-1.1

[Marcos Talau]

Control: tags 998965 + patch
Control: tags 998965 + pending


Dear maintainer,

I've prepared an NMU for spew (versioned as 1.0.8-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u spew-1.0.8/debian/rules spew-1.0.8/debian/rules
--- spew-1.0.8/debian/rules
+++ spew-1.0.8/debian/rules
@@ -105,4 +105,8 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+
+build-arch: build
+build-indep: build
+
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install
diff -u spew-1.0.8/debian/changelog spew-1.0.8/debian/changelog
--- spew-1.0.8/debian/changelog
+++ spew-1.0.8/debian/changelog
@@ -1,3 +1,10 @@
+spew (1.0.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #998965).
+
+ -- Marcos Talau   Sun, 06 Nov 2022 13:31:22 -0300
+
 spew (1.0.8-1) unstable; urgency=low
 
   * New upstream release. ( Closes: #560523 )

Processed: libgcr410: diff for NMU version 2.4.0-9.3

[Debian Bug Tracking System]

Processing control commands:

> tags 999332 + patch
Bug #999332 [src:libgcr410] libgcr410: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999332 + pending
Bug #999332 [src:libgcr410] libgcr410: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999332: libgcr410: diff for NMU version 2.4.0-9.3

[Marcos Talau]

Control: tags 999332 + patch
Control: tags 999332 + pending


Dear maintainer,

I've prepared an NMU for libgcr410 (versioned as 2.4.0-9.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u libgcr410-2.4.0/debian/changelog libgcr410-2.4.0/debian/changelog
--- libgcr410-2.4.0/debian/changelog
+++ libgcr410-2.4.0/debian/changelog
@@ -1,3 +1,10 @@
+libgcr410 (2.4.0-9.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999332).
+
+ -- Marcos Talau   Sun, 06 Nov 2022 13:24:39 -0300
+
 libgcr410 (2.4.0-9.2) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u libgcr410-2.4.0/debian/rules libgcr410-2.4.0/debian/rules
--- libgcr410-2.4.0/debian/rules
+++ libgcr410-2.4.0/debian/rules
@@ -41,4 +41,7 @@
 
 binary: binary-indep binary-arch
 
+build-arch: build
+build-indep: build
 
+.PHONY: binary binary-arch binary-indep build build-arch build-indep clean install

Bug#1023531: utox: autopkgtest regression on s390x: test_chrono fails

[Aurelien Jarno]

On 2022-11-06 08:12, Paul Gevers wrote:
> Source: utox
> Version: 0.18.1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> Your package has an autopkgtest, great. With a recent upload of glibc it
> started to fail on s390x. Looking at the history [1], I noticed that
> apparently the test can flip from passing for a while to failing for a while
> and back. Unfortunately, we don't keep the logs so long to inspect if
> previous (pre August 2022) failures were due to the same reason.
> Unfortunately, the output of the failure is rather limited (it seems there
> is more info logged, but that log file is not echoed to the autopkgtest log
> or stored as an autopkgtest artifact.
> 
> Can you please investigate the situation? At least this is a autopkgtest
> regression on a release architecture, but maybe (hopefully?) this points at
> more severe issues.
> 
> If you find out that it's really a regression in glibc functionality and the
> upload doesn't "just" trigger faulty behavior in utox, don't hesitate to
> reassign to glibc. Also, don't hesitate to contact the s390x porters if you
> need help figuring out this s390x specific issue.

For the record, this is the contect of the log file:

2/2 Testing: test_chrono
2/2 Test: test_chrono
Command: "/home/aurel32/utox-0.18.1/build/tests/test_chrono"
Directory: /home/aurel32/utox-0.18.1/build/tests
"test_chrono" start time: Nov 06 10:53 UTC
Output:
--
Running suite(s): Chrono

=
==778737==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 24 byte(s) in 1 object(s) allocated from:
#0 0x3ffa94b9173 in __interceptor_malloc 
../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69
#1 0x2aa138068cd in emalloc 
(/home/aurel32/utox-0.18.1/build/tests/test_chrono+0x68cd)

Indirect leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x3ffa94b9173 in __interceptor_malloc 
../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69
#1 0x2aa138068cd in emalloc 
(/home/aurel32/utox-0.18.1/build/tests/test_chrono+0x68cd)

SUMMARY: AddressSanitizer: 32 byte(s) leaked in 2 allocation(s).

=
==778740==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 24 byte(s) in 1 object(s) allocated from:
#0 0x3ffa94b9173 in __interceptor_malloc 
../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69
#1 0x2aa138068cd in emalloc 
(/home/aurel32/utox-0.18.1/build/tests/test_chrono+0x68cd)

Indirect leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x3ffa94b9173 in __interceptor_malloc 
../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69
#1 0x2aa138068cd in emalloc 
(/home/aurel32/utox-0.18.1/build/tests/test_chrono+0x68cd)

SUMMARY: AddressSanitizer: 32 byte(s) leaked in 2 allocation(s).
0%: Checks: 2, Failures: 0, Errors: 2
/home/aurel32/utox-0.18.1/tests/test_chrono.c:59:E:chrono_target:test_chrono_target:0:
 (after this point) Early exit with return value 1
/home/aurel32/utox-0.18.1/tests/test_chrono.c:71:E:chrono_callback:test_chrono_callback:0:
 (after this point) Early exit with return value 1

Test time =   0.06 sec
--
Test Failed.
"test_chrono" end time: Nov 06 10:53 UTC
"test_chrono" time elapsed: 00:00:00
--

End testing: Nov 06 10:53 UTC

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Processed: fix version

[Debian Bug Tracking System]

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

> notfixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-3
Bug #1022893 {Done: Nilesh Patra } 
[src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: binary-any 
FTBFS
No longer marked as fixed in versions 
golang-github-etcd-io-gofail/0.0.0+git.2022.09.25.d0d2a96a6e-3.
> fixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-3
Bug #1022893 {Done: Nilesh Patra } 
[src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: binary-any 
FTBFS
Marked as fixed in versions 
golang-github-etcd-io-gofail/0.0.0+git.2022.09.25.d0d2a96a6e-3.
> stop
Stopping processing here.

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

Processed: xplot: diff for NMU version 1.19-9.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999308 + patch
Bug #999308 [src:xplot] xplot: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 999308 + pending
Bug #999308 [src:xplot] xplot: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#999308: xplot: diff for NMU version 1.19-9.1

[Marcos Talau]

Control: tags 999308 + patch
Control: tags 999308 + pending


Dear maintainer,

I've prepared an NMU for xplot (versioned as 1.19-9.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru xplot-1.19/debian/changelog xplot-1.19/debian/changelog
--- xplot-1.19/debian/changelog	2010-05-27 22:00:50.0 -0300
+++ xplot-1.19/debian/changelog	2022-11-06 13:18:50.0 -0300
@@ -1,3 +1,10 @@
+xplot (1.19-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999308).
+
+ -- Marcos Talau   Sun, 06 Nov 2022 13:18:50 -0300
+
 xplot (1.19-9) unstable; urgency=low
 
   * Build against libforms2.
diff -Nru xplot-1.19/debian/rules xplot-1.19/debian/rules
--- xplot-1.19/debian/rules	2010-05-27 21:59:00.0 -0300
+++ xplot-1.19/debian/rules	2022-11-06 13:18:50.0 -0300
@@ -60,4 +60,7 @@
 	$(checkdir)
 	test root = "`whoami`"
 
-.PHONY: binary binary-arch binary-indep clean checkroot
+build-arch: build
+build-indep: build
+
+.PHONY: build-arch build-indep binary binary-arch binary-indep clean checkroot

Processed: fixed

[Debian Bug Tracking System]

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

> fixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-3
Bug #1022893 [src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: 
binary-any FTBFS
Marked as fixed in versions 
golang-github-etcd-io-gofail/0.0.0+git.2022.09.25.d0d2a96a6e-3.
> close 1022893
Bug #1022893 [src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: 
binary-any FTBFS
Marked Bug as done
> stop
Stopping processing here.

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

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Sebastian Ramacher]

Source: fastnetmon
Version: 1.2.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org, sudipm.mukher...@gmail.com

https://buildd.debian.org/status/fetch.php?pkg=fastnetmon=amd64=1.2.3-1%2Bb1=1667748889=0

/<>/src/xdp_plugin/xdp_collector.cpp: In function ‘void 
start_xdp_collection(process_packet_pointer)’:
/<>/src/xdp_plugin/xdp_collector.cpp:522:5: error: 
‘bpf_prog_load_attr’ was not declared in this scope; did you mean 
‘bpf_prog_load_opts’?
  522 | bpf_prog_load_attr prog_load_attr;
  | ^~
  | bpf_prog_load_opts
/<>/src/xdp_plugin/xdp_collector.cpp:523:5: error: 
‘prog_load_attr’ was not declared in this scope
  523 | prog_load_attr.prog_type = BPF_PROG_TYPE_XDP;
  | ^~
/<>/src/xdp_plugin/xdp_collector.cpp:529:24: error: 
‘bpf_prog_load_xattr’ was not declared in this scope; did you mean 
‘bpf_prog_load_opts’?
  529 | int bpf_load_res = bpf_prog_load_xattr(_load_attr, , 
_fd);
  |^~~
  |bpf_prog_load_opts
/<>/src/xdp_plugin/xdp_collector.cpp:594:28: error: 
‘bpf_set_link_xdp_fd’ was not declared in this scope; did you mean 
‘set_link_xdp_res’?
  594 | int set_link_xdp_res = bpf_set_link_xdp_fd(ifindex, prog_fd, 
opt_xdp_flags);
  |^~~
  |set_link_xdp_res
make[3]: *** [CMakeFiles/xdp_plugin.dir/build.make:79: 
CMakeFiles/xdp_plugin.dir/xdp_plugin/xdp_collector.cpp.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:456: CMakeFiles/xdp_plugin.dir/all] Error 2

Cheers
-- 
Sebastian Ramacher

Processed: severity of 1018906 is serious

[Debian Bug Tracking System]

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

> severity 1018906 serious
Bug #1018906 {Done: Domenico Andreoli } [dwarves] dwarves: 
FTBFS with libbpf 1.0.0
Ignoring request to change severity of Bug 1018906 to the same value.
> thanks
Stopping processing here.

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

Processed: severity of 1018906 is serious

[Debian Bug Tracking System]

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

> severity 1018906 serious
Bug #1018906 {Done: Domenico Andreoli } [dwarves] dwarves: 
FTBFS with libbpf 1.0.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: autopkgtest fails with sqlalchemy 1.4.23+ds1

[Debian Bug Tracking System]

Processing control commands:

> tags 995779 + patch
Bug #995779 [mailman3] autopkgtest fails with sqlalchemy 1.4.23+ds1
Added tag(s) patch.

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

Bug#995779: autopkgtest fails with sqlalchemy 1.4.23+ds1

[Charlemagne Lasse]

Control: tags 995779 + patch

This is the upstream merged fix for sqlalchemy 1.4:
https://gitlab.com/mailman/mailman/-/commit/c926e3d54680d4fac0648cde036368c699976038

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 14:49:28 +
with message-id 
and subject line Bug#999137: fixed in sredird 2.2.1-2.1
has caused the Debian Bug report #999137,
regarding sredird: 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.)


-- 
999137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sredird
Version: 2.2.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: sredird
Source-Version: 2.2.1-2.1
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
sredird, 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 sredird 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: Thu, 03 Nov 2022 19:44:49 -0300
Source: sredird
Binary: sredird sredird-dbgsym
Architecture: source amd64
Version: 2.2.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Russell Coker 
Changed-By: Marcos Talau 
Description:
 sredird- RFC 2217 compliant Telnet serial port redirector
Closes: 999137
Changes:
 sredird (2.2.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep} (Closes: #999137).
Checksums-Sha1:
 0c3b49cc8e14a7824c49b2202b0a626b807a86eb 1631 sredird_2.2.1-2.1.dsc
 6c7ec8681493bcfebcee17dc988eca90358658fb 26473 sredird_2.2.1.orig.tar.gz
 46349258e26432b6a579ef4578a79038e2d46155 372 sredird_2.2.1-2.1.diff.gz
 2bd0eac856ed1085bd81bbdf4d7a68a346787832 3372 
sredird-dbgsym_2.2.1-2.1_amd64.deb
 9e4ef3ee7ed23579822b37b87d68e5bae85661a6 6356 sredird_2.2.1-2.1_amd64.buildinfo
 ece42d9e0d99179abc3d42dc9e9ce4980f87f074 18612 sredird_2.2.1-2.1_amd64.deb
Checksums-Sha256:
 dc009f5bd32e76df4a12829df0bd7098f06a0fe527db62314807cf690b77edc4 1631 
sredird_2.2.1-2.1.dsc
 f5e5ac49cfb38e2edda5ae72ee0751cc1f9dc8f425dfb0b7b16720e72912c34b 26473 
sredird_2.2.1.orig.tar.gz
 5710fe948d5ac51ee1de4f402c747043bb486f74df9dba1b23212c4392e1bcbf 372 
sredird_2.2.1-2.1.diff.gz
 a0549928089d993ad4509532304f5eccd0eba658913326b418aa918d20113307 3372 
sredird-dbgsym_2.2.1-2.1_amd64.deb
 8c6dad444deaaf1570f01efef51e29426e0a90439bde95b973af151668a37357 6356 
sredird_2.2.1-2.1_amd64.buildinfo
 9ad57de042ec8f27366f371c065e5613d7735b5860a5acd798802411f61b899f 18612 
sredird_2.2.1-2.1_amd64.deb
Files:
 32061996a05b3e3229c9c01e70064853 1631 comm optional sredird_2.2.1-2.1.dsc
 c0246bca63888c8b38e6d46529edd010 26473 comm optional sredird_2.2.1.orig.tar.gz
 6c9427df1ca248dc9ec67a9f4441dde0 372 comm optional sredird_2.2.1-2.1.diff.gz
 bbd6d3ed5916c7df2e698a74712279f0 3372 debug optional 
sredird-dbgsym_2.2.1-2.1_amd64.deb
 4c9f34da633112cf1f54f03204b3934a 6356 comm optional 
sredird_2.2.1-2.1_amd64.buildinfo
 a4bb85172fcc73cfb0a4b4b51d0e8b65 18612 comm optional 
sredird_2.2.1-2.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNnxucACgkQ9LqqgNso
ukygwA/9FxEgOKourumUrPRdxzz+3nsk1M0AtbOw+axRQsxsrg8xl4yOXaMnlpvO
MrOhPCa8Hx1sxrg0HoYFmwuW/uycTDkhtl8OEbLXT4iC4GxePJFw7TQgGqeH442a
JvOeDSMGXj7BrhwKicAbmhGYhMW8pn+mq0CnJLVHvcnSPTLxPJ1tfrLnjWxASsRx
GDzOr1zg9s7EDWV6Y8ugfpxpBe+RfnJ9ftVkcDXfK6Cx5Mnm6jhj3HqnU6V8YMwF

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

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 14:49:17 +
with message-id 
and subject line Bug#998950: fixed in mailsync 5.2.7-3.1
has caused the Debian Bug report #998950,
regarding mailsync: 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.)


-- 
998950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailsync
Version: 5.2.7-3
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: mailsync
Source-Version: 5.2.7-3.1
Done: Marcos Talau 

We believe that the bug you reported is fixed in the latest version of
mailsync, 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 mailsync 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: Thu, 03 Nov 2022 18:39:28 -0300
Source: mailsync
Binary: mailsync mailsync-dbgsym
Architecture: source amd64
Version: 5.2.7-3.1
Distribution: unstable
Urgency: medium
Maintainer: Tomas Pospisek 
Changed-By: Marcos Talau 
Description:
 mailsync   - Synchronize IMAP mailboxes
Closes: 998950
Changes:
 mailsync (5.2.7-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep} (Closes: #998950).
Checksums-Sha1:
 5098a107ff43d2d43046da33ab8944d847d959a1 1787 mailsync_5.2.7-3.1.dsc
 1360037daba55801fb3fcff11b790ed68a5df92f 153417 mailsync_5.2.7.orig.tar.gz
 b819485389c05b41393560fc70333aa53cf63dec 73291 mailsync_5.2.7-3.1.diff.gz
 b0de67a5fd310d3ad211eb2018ee02653a1a7af0 808144 
mailsync-dbgsym_5.2.7-3.1_amd64.deb
 cce3cf73ebc0f1691edc07bd01f7b67bd813013b 6781 
mailsync_5.2.7-3.1_amd64.buildinfo
 e70793a395ecaebab64ea7467233bde69a48ee53 62076 mailsync_5.2.7-3.1_amd64.deb
Checksums-Sha256:
 0365f008c4236f1c11b8cc3f3c5e9477a0df32baef9dc5f6bcad3d4142ff3262 1787 
mailsync_5.2.7-3.1.dsc
 1d81575e8ef75f1f65d680dcb8c8472cb6e50f132a4af26ebf97e11bae9577a0 153417 
mailsync_5.2.7.orig.tar.gz
 43fde8aefb61d389bbbd38610ff1e04c2ddb474c63e08bcb8e13773ddc40523e 73291 
mailsync_5.2.7-3.1.diff.gz
 f3a60d9330007cbc061bf3cbf8565add7a52fe757d978f83b038d06fdcfadc8e 808144 
mailsync-dbgsym_5.2.7-3.1_amd64.deb
 a6257ec6de101343fa39c510dff06db2a8d093d52bc778d380e13c5fed4e06af 6781 
mailsync_5.2.7-3.1_amd64.buildinfo
 46720c7ada4e50bcb3a34b1c7322c2a60f9ca48fc4aaed112abcf7f21fd6dfa7 62076 
mailsync_5.2.7-3.1_amd64.deb
Files:
 4e4c423cfd30655fa90f9af7c1604403 1787 mail optional mailsync_5.2.7-3.1.dsc
 494486ed6c97db9efe6a403a7f2319a3 153417 mail optional 
mailsync_5.2.7.orig.tar.gz
 7638395be6c627dd54be9e7719a4be26 73291 mail optional mailsync_5.2.7-3.1.diff.gz
 c985ff1b587ec68e75f88e5e6eef2953 808144 debug optional 
mailsync-dbgsym_5.2.7-3.1_amd64.deb
 b6de9100479273a24775f3a65afd1548 6781 mail optional 
mailsync_5.2.7-3.1_amd64.buildinfo
 834b6c9b257d89faafc17e574869547a 62076 mail optional 
mailsync_5.2.7-3.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmNnxnkACgkQ9LqqgNso
uky2Sw/+OV6n1KvfGPnpQ8kRouQQzBURPOkcnl2I3ItNuvoZo8wpmzHnKAsKepQO
7r6o0EHll7ri7i+rVN4Ww1JCLJO6esJT4QCZkHCtgx5ur9sPEt4OnR+SA0nLLEfo
OQCVkxZQKLQxNgsSI6J6/ojKSRBAiTGVGOKnoY6CX4nCUuBJ9/kTbQI0XJgSNP9O
2VABlzwPmyglagiLEucZM2btw2IryZrgIa2oYO4spyRNsvwApCh2JEdc/uxcPIYs

Processed: pyopengl: migrate to libglut3.12

[Debian Bug Tracking System]

Processing control commands:

> block 1023419 by -1
Bug #1023419 [release.debian.org] transition: freeglut
1023419 was not blocked by any bugs.
1023419 was not blocking any bugs.
Added blocking bug(s) of 1023419: 1023548

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

Bug#1023548: pyopengl: migrate to libglut3.12

[Sebastian Ramacher]

Source: pyopengl
Version: 3.1.5+dfsg-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Control: block 1023419 by -1

pyopengl hardcodes the dependency on freeglut3. As the transition from
freeglut3 to libglut3.12 is currently ongoing, pyopengl needs to be
fixed.

Cheers
-- 
Sebastian Ramacher

Processed: Re: Update bug

[Debian Bug Tracking System]

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

> severity 1023373 important
Bug #1023373 [src:bibledit] bibledit: non-source Google Analytics file
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1023373: Further bug discussion

[Teus Benschop]

Hi Bastian,

Thank you for the extra clarification about what this bug is about, and for the 
extra details.

> We can play a word game but "missing sources" is exactly about 
> "non-source files". If a file is contained in a package that is not a 
> source file then its sources are missing.

Okay, the clarification is clear, and rest assured I was not playing a game on 
words.

[…] 
> Please take a look at analytics.html and think about the question: "Is 
> this a source file or not?”

Here is the file analytics.html:


  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
  ga('create', 'UA-19077541-2', 'auto');
  ga('send', 'pageview');


  
window.heap=window.heap||[],heap.load=function(e,t){window.heap.appid=e,window.heap.config=t=t||{};var
 
r=t.forceSSL||"https:"===document.location.protocol,a=document.createElement("script");a.type="text/javascript",a.async=!0,a.src=(r?"https:":"http:")+"//cdn.heapanalytics.com/js/heap-"+e+".js";var
 
n=document.getElementsByTagName("script")[0];n.parentNode.insertBefore(a,n);for(var
 o=function(e){return 
function(){heap.push([e].concat(Array.prototype.slice.call(arguments,0)))}},p=["addEventProperties","addUserProperties","clearEventProperties","identify","removeEventProperty","setEventProperties","track","unsetEventProperty"],c=0;c I know about that bug report (I have already referenced it here). It was 
> closed without actually fixing it. The quill files are still non-source 
> files because they are not in their preferred form of modification.

Ah, okay, thanks for that clarification too.
When this bug report [1]  titled "Some sources are not included in your 
package” was closed by me,
I genuinely believed that the fix made was fixing the issue the bug was about.
But if you believe that the bug was not fixed, then feel free to re-open it.
We can then continue the discussion there.
I believe that this course of action is clearer since then the topic can be 
discussed in the context of the bug.

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

> So this bug is primarily about the missing source (Policy violation).
> When you have addressed that you can downgrade the severity to important 
> to address the secondary issue of supposed privacy violations.

That is okay. 
So what I suggest is to move the issue of the missing source back to that bug 
where it belongs, to bug #1017083.
That now having been moved there, the current bug, titled "non-source Google 
Analytics file” can then have its severity change to important.
I intend to change that severity soon after.
We may then continue the discussion on that google analytics file here at this 
bug.

As is clear from all of this, my current main concern is that there’s a release 
critical bug against bibledit, but yet it is not very clear why this bug is so 
critical. So changing that severity address this concern.
Being free of that concern now, it’s possible to move on about the content of 
the bug report.

Although I intend to change the severity of the bug titled non-source Google 
Analytics file”
I am not intending to reopen bug #1017083 because currently I believe it is 
fixed.
Please reopen this bug if you believe it’s not fixed yet.

Thanks for all the input on making the package better and better.

Teus.

Bug#1023229: marked as done (f3d: autopkgtest regression on s390x: Compare with ref failed)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 13:34:13 +
with message-id 
and subject line Bug#1023229: fixed in f3d 1.3.1+dfsg-5
has caused the Debian Bug report #1023229,
regarding f3d: autopkgtest regression on s390x: Compare with ref failed
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.)


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

Source: f3d
Version: 1.3.1+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
f3dfrom testing1.3.1+dfsg-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. I note that 
s390x is our only big endian release architecture (just in case that 
matters to the problem at hand).


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=f3d

https://ci.debian.net/data/autopkgtest/testing/s390x/f/f3d/27693775/log.gz

==
Smoke Test
==
No config file found
Loading: /tmp/autopkgtest-lxc.dd0h8lat/downtmp/autopkgtest_tmp/cube.dae

Warning: In 
./library/VTKExtensions/Readers/vtkF3DAssimpImporter.cxx, line 583
vtkF3DAssimpImporter (0x2aa2fdf42f0): Assimp failed to load: 
/tmp/autopkgtest-lxc.dd0h8lat/downtmp/autopkgtest_tmp/cube.dae



No camera available in this file



Camera position: 0,0,1
Camera focal point: 0,0,0
Camera view up: 0,1,0
Camera view angle: 30


===
Generate the new screenshot
===

Compare with ref

Comparing "debian/tests/cube_dae_ref.png" and 
"/tmp/autopkgtest-lxc.dd0h8lat/downtmp/check-cube-dae-artifacts/cube_dae.png"

  Mean error = 0.0898372
  RMS error = 0.250222
  Peak SNR = 12.0335
  Max error  = 0.72549 @ (393, 106, R)  values are 0.92549, 0.92549, 
0.92549 vs 0.2, 0.2, 0.2

  47288 pixels (15.4%) over 1e-06
  47288 pixels (15.4%) over 1e-06
FAILURE
autopkgtest [06:20:10]: test check-cube-dae



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: f3d
Source-Version: 1.3.1+dfsg-5
Done: Francois Mazen 

We believe that the bug you reported is fixed in the latest version of
f3d, 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.
Francois Mazen  (supplier of updated f3d 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 14:17:51 +0100
Source: f3d
Architecture: source
Version: 1.3.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Mazen 
Changed-By: Francois Mazen 
Closes: 1023229
Changes:
 f3d (1.3.1+dfsg-5) unstable; urgency=medium
 .
   * Update changelog to correct typo in the Assimp s390x bug number
 #1023229 instead of #1023212 (Closes: #1023229)
Checksums-Sha1:
 9885e30bbf375bfb95cbf391973b65bd545672f7 2086 f3d_1.3.1+dfsg-5.dsc
 a6976496840ba7e4589dbcaddd18ac2918a3 66248 f3d_1.3.1+dfsg-5.debian.tar.xz
 813cee3353d29f1d6e59d7cba17d1be7122c7d07 23369 
f3d_1.3.1+dfsg-5_source.buildinfo
Checksums-Sha256:
 84fcb8a8fa6393dac23631de581b4ac798a130121a1480a2d1d8721a341ecc09 2086 
f3d_1.3.1+dfsg-5.dsc
 ff3194e60f6a0558cf1dc0c8b66d4e6e5ba803766039de3b948e2a4c04d59a46 66248 
f3d_1.3.1+dfsg-5.debian.tar.xz
 493e58a2641123b23650eb4699bba449e849546797182252931ad1911615c92e 23369 
f3d_1.3.1+dfsg-5_source.buildinfo
Files:
 4a2d9ad39c49f7c07bd3e8cc03cab4c0 2086 graphics optional f3d_1.3.1+dfsg-5.dsc
 ca766e63a767d8f68b087b5a086eba87 66248 graphics optional 

Bug#1022339: marked as done (virt-manager: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 12:35:40 +
with message-id 
and subject line Bug#1022339: fixed in virt-manager 1:4.1.0-2
has caused the Debian Bug report #1022339,
regarding virt-manager: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
1022339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virt-manager
Version: 1:4.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 setup.py --no-update-icon-cache --no-compile-schemas install --force 
> --root=debian/tmp --no-compile -O0
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> Using SYSPREFIX=/usr
> running build
> Generating /<>/build/virt-install
> Generating /<>/build/virt-clone
> Generating /<>/build/virt-xml
> Generating /<>/build/virt-manager
> Generating man/virt-clone.1
> Generating man/virt-install.1
> Generating man/virt-xml.1
> Generating man/virt-manager.1
> Generating build/bash-completion/virt-install
> Generating build/bash-completion/virt-clone
> Generating build/bash-completion/virt-xml
> running build_i18n
> running build_scripts
> copying and adjusting build/virt-manager -> build/scripts-3.10
> copying and adjusting build/virt-clone -> build/scripts-3.10
> copying and adjusting build/virt-install -> build/scripts-3.10
> copying and adjusting build/virt-xml -> build/scripts-3.10
> running install_data
> creating debian/tmp
> creating debian/tmp/usr
> creating debian/tmp/usr/local
> creating debian/tmp/usr/local/share
> creating debian/tmp/usr/local/share/glib-2.0
> creating debian/tmp/usr/local/share/glib-2.0/schemas
> copying data/org.virt-manager.virt-manager.gschema.xml -> 
> debian/tmp/usr/local/share/glib-2.0/schemas
> creating debian/tmp/usr/local/share/virt-manager
> creating debian/tmp/usr/local/share/virt-manager/ui
> copying ui/vmwindow.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/createvol.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/hoststorage.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/createpool.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/createnet.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/createvm.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/snapshots.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/manager.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/netlist.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/migrate.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/host.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/connectauth.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/snapshotsnew.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/console.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/addhardware.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/clone.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/addstorage.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/about.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/vsockdetails.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/createconn.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/delete.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/asyncjob.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/xmleditor.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/storagebrowse.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/tpmdetails.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/hostnets.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/preferences.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/gfxdetails.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/details.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/oslist.ui -> debian/tmp/usr/local/share/virt-manager/ui
> copying ui/fsdetails.ui -> debian/tmp/usr/local/share/virt-manager/ui
> creating debian/tmp/usr/local/share/man
> creating debian/tmp/usr/local/share/man/man1

Processed: Bug#1022339 marked as pending in virt-manager

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022339 [src:virt-manager] virt-manager: FTBFS: dh_install: error: missing 
files, aborting
Ignoring request to alter tags of bug #1022339 to the same tags previously set

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

Bug#1022339: marked as pending in virt-manager

[Pino Toscano]

Control: tag -1 pending

Hello,

Bug #1022339 in virt-manager 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/libvirt-team/virt-manager/-/commit/592f0810d6b06c3ce358cc617a6bb8ab70db6bd4


Explicitly specify --install-layout=deb in the Python module installation;

fixes compatibility with Python 3.10 in Debian.

Closes: #1022339
Gbp-Dch: Full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022339

Bug#1022313: marked as done (gnupg-pkcs11-scd: FTBFS: conftest.c:49:10: fatal error: minix/config.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 10:49:03 +
with message-id 
and subject line Bug#1022313: fixed in gnupg-pkcs11-scd 0.10.0-2
has caused the Debian Bug report #1022313,
regarding gnupg-pkcs11-scd: FTBFS: conftest.c:49:10: fatal error: 
minix/config.h: No such file or directory
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.)


-- 
1022313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg-pkcs11-scd
Version: 0.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> gcc version 12.2.0 (Debian 12.2.0-7) 
> ... rest of stderr output deleted ...
> configure:3932: $? = 0
> configure:3921: gcc -V >&5
> gcc: error: unrecognized command-line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3932: $? = 1
> configure:3921: gcc -qversion >&5
> gcc: error: unrecognized command-line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3932: $? = 1
> configure:3921: gcc -version >&5
> gcc: error: unrecognized command-line option '-version'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3932: $? = 1
> configure:3952: checking whether the C compiler works
> configure:3974: gcc -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
> configure:3978: $? = 0
> configure:4028: result: yes
> configure:4031: checking for C compiler default output file name
> configure:4033: result: a.out
> configure:4039: checking for suffix of executables
> configure:4046: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
> configure:4050: $? = 0
> configure:4073: result: 
> configure:4095: checking whether we are cross compiling
> configure:4103: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
> configure:4107: $? = 0
> configure:4114: ./conftest
> configure:4118: $? = 0
> configure:4133: result: no
> configure:4138: checking for suffix of object files
> configure:4161: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4165: $? = 0
> configure:4187: result: o
> configure:4191: checking whether the compiler supports GNU C
> configure:4211: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4211: $? = 0
> configure:4221: result: yes
> configure:4232: checking whether gcc accepts -g
> configure:4253: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4253: $? = 0
> configure:4297: result: yes
> configure:4317: checking for gcc option to enable C11 features
> configure:4332: gcc  -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4332: $? = 0
> configure:4350: result: none needed
> configure:4466: checking whether gcc understands -c and -o together
> configure:4489: gcc -c conftest.c -o conftest2.o
> configure:4492: $? = 0
> configure:4489: gcc -c conftest.c -o conftest2.o
> configure:4492: $? = 0
> configure:4504: result: yes
> configure:4523: checking dependency style of gcc
> configure:4635: result: none
> configure:4655: checking for stdio.h
> configure:4655: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4655: $? = 0
> configure:4655: result: yes
> configure:4655: checking for stdlib.h
> configure:4655: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4655: $? = 0
> configure:4655: result: yes
> configure:4655: checking for string.h
> configure:4655: gcc -c -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> 

Bug#999145: cappuccino: diff for NMU version 0.5.1-10.1

[Breno Leitao]

On Wed, Nov 02, 2022 at 05:45:26PM -0300, Marcos Talau wrote:
> Control: tags 999145 + patch
> Control: tags 999145 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for cappuccino (versioned as 0.5.1-10.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

That is OK. Thanks for your contribution.

Bug#1023178: marked as done (microprofile: Contains non-free source)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 10:00:10 +
with message-id 
and subject line Bug#1023178: fixed in microprofile 4.0+dfsg-1
has caused the Debian Bug report #1023178,
regarding microprofile: Contains non-free source
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.)


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

Source: microprofile
Version: 3.1+ds-2
Severity: serious

The files src/microprofile*.html contain JavaScript code from 
https://gist.github.com/mjackson/5311256
which never got a license even though people have asked for it. So please 
exclude them.
--- End Message ---
--- Begin Message ---
Source: microprofile
Source-Version: 4.0+dfsg-1
Done: Andrea Pappacoda 

We believe that the bug you reported is fixed in the latest version of
microprofile, 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.
Andrea Pappacoda  (supplier of updated microprofile 
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: Thu, 03 Nov 2022 21:54:56 +0100
Source: microprofile
Binary: libmicroprofile-dev libmicroprofile4 libmicroprofile4-dbgsym
Architecture: source i386
Version: 4.0+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Andrea Pappacoda 
Changed-By: Andrea Pappacoda 
Description:
 libmicroprofile-dev - embeddable CPU/GPU profiler - development
 libmicroprofile4 - embeddable CPU/GPU profiler
Closes: 1023178
Changes:
 microprofile (4.0+dfsg-1) experimental; urgency=medium
 .
   [ Andrea Pappacoda ]
   * New upstream version 4.0+dfsg
   * d/control: libmicroprofile3 -> libmicroprofile4
   * d/copyright: exclude non-free JavaScript code
   * d/copyright: also mention the Unlicense license.
 Upstream originally used the Unlicense, but later relicensed under the
 MIT license. Between the 3.1 and 4.0 releases, though, a third party
 contributor submitted a patch adding a new LICENSE file including the
 Unlicense, and the patch was merged. It is now unclear which portions
 are licensed under the MIT and which ones under the Unlicense (if any),
 so I've marked all the code as licensed under both. It shouldn't matter
 anyway, as the Unlicense is a public domain-equivalent license.
   * d/patches: drop and refresh patches
   * d/patches: replace non-free JavaScript code (Closes: #1023178)
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Submit.
Checksums-Sha1:
 6936da2da5d3429b57226d5f74f931ae6046bef9 1937 microprofile_4.0+dfsg-1.dsc
 ff7ad776ac7412fcfe58353b81d354b9614e24bf 1133520 
microprofile_4.0+dfsg.orig.tar.xz
 70cee708b12c10627a7156e73f4da71e2bbffa68 73652 
microprofile_4.0+dfsg-1.debian.tar.xz
 e9b4f1d57f9ab69397cc0889f02871d405ecbf05 119472 
libmicroprofile-dev_4.0+dfsg-1_i386.deb
 038b9c9641afe065a33600edab95bed1e7028745 173952 
libmicroprofile4-dbgsym_4.0+dfsg-1_i386.deb
 67933c99274eefdf92f0c2aa667932fc39278726 119828 
libmicroprofile4_4.0+dfsg-1_i386.deb
 eb32a9e8a27029a6672063ab06a4fcfd0dfd8977 7167 
microprofile_4.0+dfsg-1_i386.buildinfo
Checksums-Sha256:
 77a5b5770674d9ced9c74404d4db50f9548ebc5d6c8992e068545a603b299caa 1937 
microprofile_4.0+dfsg-1.dsc
 5f4a7e24788b43ed1d730aa8985e5191158d44cba4a4cb92239181feb00b8dd3 1133520 
microprofile_4.0+dfsg.orig.tar.xz
 0b64a202108972c4db810686836702c00f4bb23abff0923c4100e24e4cfc16fe 73652 
microprofile_4.0+dfsg-1.debian.tar.xz
 3b25ef93dd40d66fed364154fc34bfb871a7177f3894086e7e261e7a22f2338f 119472 
libmicroprofile-dev_4.0+dfsg-1_i386.deb
 fa7d11c9b5be4b1d84c30b726e60bbc5fbbb402e3709778c2a97aee270782dfe 173952 
libmicroprofile4-dbgsym_4.0+dfsg-1_i386.deb
 fac65f162cd985fdbd6507f476eccb167601fe50b3647036a575657d5713bf1b 119828 
libmicroprofile4_4.0+dfsg-1_i386.deb
 78db0df57858637637c6242cf8b5163ab18bd253e2bda0c424c9622e45ba0ab1 7167 
microprofile_4.0+dfsg-1_i386.buildinfo
Files:
 946dc4df6bff6adced06fb3dff54d23e 1937 libs optional microprofile_4.0+dfsg-1.dsc
 2e2e76d6062dd0a2a105f5ad80c6cf7d 1133520 libs optional 
microprofile_4.0+dfsg.orig.tar.xz
 

Bug#1023501: marked as done (busybox-static: version 1:1.35.0-3 breaks boot)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 08:49:16 +
with message-id 
and subject line Bug#1023501: fixed in busybox 1:1.35.0-4
has caused the Debian Bug report #1023501,
regarding busybox-static: version 1:1.35.0-3 breaks boot
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.)


-- 
1023501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox-static
Version: 1:1.35.0-2
Severity: normal

Dear Maintainer,

With 1:1.35.0-3, boot ends in initramfs:

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... 
   
mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
mdadm: error opening /dev/md?*: No such file or directory
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically
done.
mdadm: No arrays found in config file or automatically
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or 

Bug#1023427: marked as done (pixman: CVE-2022-44638)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 08:35:44 +
with message-id 
and subject line Bug#1023427: fixed in pixman 0.40.0-1.1
has caused the Debian Bug report #1023427,
regarding pixman: CVE-2022-44638
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.)


-- 
1023427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pixman
Version: 0.40.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://gitlab.freedesktop.org/pixman/pixman/-/issues/63
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for pixman.

CVE-2022-44638[0]:
| In libpixman in Pixman before 0.42.2, there is an out-of-bounds write
| (aka heap-based buffer overflow) in rasterize_edges_8 due to an
| integer overflow in pixman_sample_floor_y.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-44638
https://www.cve.org/CVERecord?id=CVE-2022-44638
[1] https://gitlab.freedesktop.org/pixman/pixman/-/issues/63
[2] 
https://gitlab.freedesktop.org/pixman/pixman/-/commit/a1f88e842e0216a5b4df1ab023caebe33c101395

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: pixman
Source-Version: 0.40.0-1.1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
pixman, 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.
Salvatore Bonaccorso  (supplier of updated pixman 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: Thu, 03 Nov 2022 23:07:46 +0100
Source: pixman
Architecture: source
Version: 0.40.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Salvatore Bonaccorso 
Closes: 1023427
Changes:
 pixman (0.40.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Avoid integer overflow leading to out-of-bounds write (CVE-2022-44638)
 (Closes: #1023427)
Checksums-Sha1: 
 8f67c27d223bbdfb06561f8d323cc31bfa4215ec 2184 pixman_0.40.0-1.1.dsc
 05d2600f10ec9dd4b1e88e4874af066d02269fbc 327509 pixman_0.40.0-1.1.diff.gz
Checksums-Sha256: 
 9b70557c36ce3ac3dba10915b981043201cde21f56cec8821c87f4ab39420a06 2184 
pixman_0.40.0-1.1.dsc
 5c3d8f81d864457c62344caaa9e9c83b38d98ec65f655fb264e12df6cb77e6d5 327509 
pixman_0.40.0-1.1.diff.gz
Files: 
 9890b70ae8bda4dc15a95f368d3ee261 2184 devel optional pixman_0.40.0-1.1.dsc
 0755537f8d070f1f60a5e30a7d88cdb4 327509 devel optional 
pixman_0.40.0-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNkxEpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EDTkP+gPV6uySGI30iv+daGBpS8TMbMvpMChD
jvEWGGGfkjXF8m4oVRGEa+okbQkLLu/Uqy4xvtqEwGVc0Ogl7rY30LhosJl4jPJo
WePC5j7aOF6whaeIa+1FDBnqlULdDICyTvviboD9evrNejyDmhEWqIfYDpsk3Nv7
LZRZQTuafmlxO4cTnQOBwmSdlSsDeA4cC0gJYeAZR5uZ074FvtZfDr5ZSLr+lIrV
qyfPiJJjjtjO0a5fxNQ0/bo4aW3v6jGnroz3HPb468gATojHUj2vowoD4Vf93g/e
PaJ/glO6J1YT/BA72R5Qm3i56Om5NCXRtL5A1Qst/u0E8vKFzjAvDVJNCvPVh+bb
n8UVJeU8ze4qQjnwxO0qcqiuDk1a86dN5PAXa1/zJe9CRLVWr7OowzmyYOj0d88K
pYfK9d6kflm3XRngv2YyhtQXDQhNC7OasrKHzpfgh2FCnqy9PCq5Xp/X+VrFJ9Sm
WJI9z/C4jNcbMuaH4nsjcNG7yNsC4dl9p0LMV8AbPCe8+EGjsDzSZ9ZvgGPOazuC
t5swGeHTl0nT6xcksteKYAtQng3XdSMnK29b7QZ1kwrAYSwR8iE7FesksTrpbomP
C2B4/+WkX9eoFg1cJlTQcmpR24mSOybS691k7KpV0zJ+SwL1NRltX9vwshKl7z3O
D6KLuiweAol2
=ktKz
-END PGP SIGNATURE End Message ---

Bug#1020079: netplan.io: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1

[s3v]

Dear Maintainer,

After switching from deprecated nose to pytest, I was able to build your
package in a sid chroot environment.
I've just applied this PR [1] and updated B-D as suggested in [2]

Kind regards

[1] https://github.com/canonical/netplan/pull/289
[2] https://salsa.debian.org/debian/netplan.io/-/merge_requests/8

Processed: Re: busybox-static: version 1:1.35.0-3 breaks boot on hppa

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #1023501 [busybox-static] busybox-static: version 1:1.35.0-3 breaks boot
Added tag(s) confirmed.

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

Bug#1023501: busybox-static: version 1:1.35.0-3 breaks boot on hppa

[Michael Tokarev]

Control: tag -1 + confirmed

On Sat, 5 Nov 2022 21:18:58 +0100 Robert Luberda  wrote:

severity 1023501 grave
retitle 1023501 busybox-static: version 1:1.35.0-3 breaks boot on hppa 
and amd64

found 1023501 1:1.35.0-3
notfound 1023501  1:1.35.0-2

On Sat, 05 Nov 2022 13:31:51 + John David Anglin 
 wrote:

> Package: busybox-static
> Version: 1:1.35.0-2
> Severity: normal
> 
> Dear Maintainer,
> 
> With 1:1.35.0-3, boot ends in initramfs:
> 
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.

> Begin: Running /scripts/local-premount ... done.
> Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
...
mdadm: No arrays found in config file or automatically
> done.
> Begin: Running /scripts/local-block ... mdadm: No arrays found in config file 
or
automatically

> >
> >  - Missing modules (cat /proc/modules; ls /dev)
> > ALERT!  LABEL=ROOT2 does not exist.  Dropping to a shell!


I had the same issue on amd64.
Removing mdadm package did not help.
Downgrading busybox-static to 1.35.0-2 fixed the issue.


Now this is interesting.  In -3, I included these changes:

commit ac478f88b64d5884d5e81bcd8f8344f0ec72df6a
Author: Michael Tokarev 
Date:   Mon Oct 17 12:52:23 2022 +0300

deb,static: enable blkid applet (useful for rescue purposes)

commit d371992b4a0394f02cd29cb9cb946080414f8afb
Author: Michael Tokarev 
Date:   Mon Oct 17 13:00:16 2022 +0300

deb,static: enable findfs applet (useful for rescue purposes)

Both really are useful for rescue purposes, I've hit this - the lack of
blkid and findfs in busybox - several times, and finally decided to enable
them.. It's a minimal version, it can help in many situations.

But it turns out debian initramfs generator includes its own blkiid, which
is more advanced than busybox's.  For regular (non-static) build, busybox
adds links to itself for applets it have but which aren't provided by other
tools already.  However, for the static build, it has CONFIG_PREFER_APPLETS=y
(in order to be more useful when the filesystem is damaged/incomplete), so
it ignores external implementation of these utilities.  And we end up in
this situation.

And for the static build, it is even more interesting to have these utils
available.

*sigh*

I'll disable one of them for -static build for now, to work around this
issue (have to check which one is to blame, most likely blkid).

But.. *sigh* :)

Thanks,

/mjt

Processed: retitle 1023501 to busybox-static: version 1:1.35.0-3 breaks boot

[Debian Bug Tracking System]

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

> retitle 1023501 busybox-static: version 1:1.35.0-3 breaks boot
Bug #1023501 [busybox-static] busybox-static: version 1:1.35.0-3 breaks boot on 
hppa
Changed Bug title to 'busybox-static: version 1:1.35.0-3 breaks boot' from 
'busybox-static: version 1:1.35.0-3 breaks boot on hppa'.
> thanks
Stopping processing here.

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

Processed: src:ruby-liquid: fails to migrate to testing for too long: new BD not available in testing

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.4.0-2
Bug #1023534 [src:ruby-liquid] src:ruby-liquid: fails to migrate to testing for 
too long: new BD not available in testing
Marked as fixed in versions ruby-liquid/5.4.0-2.
Bug #1023534 [src:ruby-liquid] src:ruby-liquid: fails to migrate to testing for 
too long: new BD not available in testing
Marked Bug as done

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

Bug#1023534: src:ruby-liquid: fails to migrate to testing for too long: new BD not available in testing

[Paul Gevers]

Source: ruby-liquid
Version: 4.0.3-3
Severity: serious
Control: close -1 5.4.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:ruby-liquid has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. In a recent upload you added a 
new Build-Dependency, but that package FTBFS on several architectures 
and isn't available in testing.


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=ruby-liquid



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023531: utox: autopkgtest regression on s390x: test_chrono fails

[Paul Gevers]

Source: utox
Version: 0.18.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. With a recent upload of glibc it 
started to fail on s390x. Looking at the history [1], I noticed that 
apparently the test can flip from passing for a while to failing for a 
while and back. Unfortunately, we don't keep the logs so long to inspect 
if previous (pre August 2022) failures were due to the same reason. 
Unfortunately, the output of the failure is rather limited (it seems 
there is more info logged, but that log file is not echoed to the 
autopkgtest log or stored as an autopkgtest artifact.


Can you please investigate the situation? At least this is a autopkgtest 
regression on a release architecture, but maybe (hopefully?) this points 
at more severe issues.


If you find out that it's really a regression in glibc functionality and 
the upload doesn't "just" trigger faulty behavior in utox, don't 
hesitate to reassign to glibc. Also, don't hesitate to contact the s390x 
porters if you need help figuring out this s390x specific issue.


Paul

[1] https://ci.debian.net/packages/u/utox/testing/s390x/


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022295: marked as done (llvm-toolchain-13: FTBFS: build-dependency not installable: llvm-spirv)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 07:00:37 +
with message-id 
and subject line Bug#1022295: fixed in llvm-toolchain-13 1:13.0.1-9
has caused the Debian Bug report #1022295,
regarding llvm-toolchain-13: FTBFS: build-dependency not installable: llvm-spirv
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.)


-- 
1022295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-13
Version: 1:13.0.1-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10.0), cmake, ninja-build, chrpath, 
> texinfo, sharutils, libelf-dev, libffi-dev, lsb-release, patchutils, 
> diffstat, xz-utils, python3-dev, libedit-dev, libncurses5-dev, swig, 
> python3-six, python3-sphinx (>= 1.3.6), binutils-dev, libxml2-dev, 
> libjsoncpp-dev, pkg-config, lcov, procps, help2man, zlib1g-dev, g++-multilib, 
> libjs-mathjax, python3-recommonmark, doxygen, gfortran, ocaml-base | 
> ocaml-nox, ocaml-findlib, libctypes-ocaml-dev, dh-exec, dh-ocaml, 
> libpfm4-dev, python3-setuptools, libz3-dev, llvm-spirv | hello, spirv-tools | 
> hello, libgrpc++-dev, protobuf-compiler-grpc, libprotobuf-dev, 
> protobuf-compiler, build-essential, fakeroot
> Merged Build-Conflicts: oprofile
> Filtered Build-Depends: debhelper (>= 10.0), cmake, ninja-build, chrpath, 
> texinfo, sharutils, libelf-dev, libffi-dev, lsb-release, patchutils, 
> diffstat, xz-utils, python3-dev, libedit-dev, libncurses5-dev, swig, 
> python3-six, python3-sphinx (>= 1.3.6), binutils-dev, libxml2-dev, 
> libjsoncpp-dev, pkg-config, lcov, procps, help2man, zlib1g-dev, g++-multilib, 
> libjs-mathjax, python3-recommonmark, doxygen, gfortran, ocaml-base, 
> ocaml-findlib, libctypes-ocaml-dev, dh-exec, dh-ocaml, libpfm4-dev, 
> python3-setuptools, libz3-dev, llvm-spirv, spirv-tools, libgrpc++-dev, 
> protobuf-compiler-grpc, libprotobuf-dev, protobuf-compiler, build-essential, 
> fakeroot
> Filtered Build-Conflicts: oprofile
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [820 B]
> Get:5 copy:/<>/apt_archive ./ Packages [743 B]
> Fetched 2526 B in 0s (194 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: llvm-spirv but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/llvm-toolchain-13_13.0.1-7_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-13
Source-Version: 1:13.0.1-9
Done: Sylvestre 

Bug#1023466: marked as done (llvm-toolchain-13: FTBFS with swig 4.1: interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined)

[Debian Bug Tracking System]

Your message dated Sun, 06 Nov 2022 07:00:37 +
with message-id 
and subject line Bug#1023466: fixed in llvm-toolchain-13 1:13.0.1-9
has caused the Debian Bug report #1023466,
regarding llvm-toolchain-13: FTBFS with swig 4.1: interfaces.swig:5: Error: 
Macro '__STDC_LIMIT_MACROS' redefined
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.)


-- 
1023466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-14
Version: 1:14.0.6-7
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

llvm-toolchain-14 FTBFS on i386 on the buildds, but I can reproduce that
locally on amd64 now, too.
Comparing the build logs shows swig 4.0.2-2 being used on the successful
amd64 buildd build and 4.1.0-0.1 on the failing i386 one.
(Please check the other llvm versions, too.)

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-14=i386=1%3A14.0.6-7=1667248227=0

...
[2858/7462] cd 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
&& /usr/bin/swig4.0 -c++ -features autodoc -I/<>/lldb/include 
-I/<>/lldb/bindings -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-I/<>/lldb/bindings/python -c++ -shadow -python -py3 -threads 
-outdir 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
-o 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/LLDBWrapPython.cpp
 /<>/lldb/bindings/python/python.swig
FAILED: tools/lldb/bindings/python/LLDBWrapPython.cpp 
tools/lldb/bindings/python/lldb.py 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/LLDBWrapPython.cpp
 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/lldb.py
cd 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
&& /usr/bin/swig4.0 -c++ -features autodoc -I/<>/lldb/include 
-I/<>/lldb/bindings -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-I/<>/lldb/bindings/python -c++ -shadow -python -py3 -threads 
-outdir 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python 
-o 
/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/bindings/python/LLDBWrapPython.cpp
 /<>/lldb/bindings/python/python.swig
Deprecated command line option: -py3. Ignored, this option is no longer 
supported.
/<>/lldb/bindings/interfaces.swig:5: Error: Macro 
'__STDC_LIMIT_MACROS' redefined,
:1: Error: previous definition of '__STDC_LIMIT_MACROS'.
[2859/7462] /<>/build-llvm/./bin/clang++ -D_FILE_OFFSET_BITS=64 
-D_GNU_SOURCE -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen
 -I/<>/clang/utils/TableGen -I/<>/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/include 
-I/<>/llvm/include -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition 
-fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
-Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor 
-Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion 
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
-fdata-sections 
-ffile-prefix-map=/<>/build-llvm/tools/clang/stage2-bins=build-llvm/tools/clang/stage2-bins
 -ffile-prefix-map=/<>/= -no-canonical-prefixes -fno-common 
-Woverloaded-virtual -Wno-nested-anon-types -O3 -DNDEBUG  -fno-exceptions 
-std=c++14 -MD -MT 
tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/RISCVVEmitter.cpp.o -MF 
tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/RISCVVEmitter.cpp.o.d -o 
tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/RISCVVEmitter.cpp.o -c 
/<>/clang/utils/TableGen/RISCVVEmitter.cpp
[2860/7462] /<>/build-llvm/./bin/clang++ -DHAVE_ROUND 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/utils/TableGen 
-I/<>/lldb/utils/TableGen -I/<>/lldb/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/include 
-I/<>/build-llvm/tools/clang/stage2-bins/include 
-I/<>/llvm/include -I/usr/include/python3.10 
-I/<>/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/lldb/../clang/include
 -I/usr/include/libxml2 

Bug#1023530: nut: flaky autopkgtest: varying failures

[Paul Gevers]

Source: nut
Version: 2.8.0-4
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 (after the fix for bug #1019221).


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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nut/27871546/log.gz

==
FAIL: test_upsmon_notif (__main__.BasicTest)
Test upsmon notifications
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.owbpap0l/downtmp/build.mBX/src/debian/tests/test-nut.py", 
line 357, in test_upsmon_notif

self._nut_setvar('ups.status', 'OB')
  File 
"/tmp/autopkgtest-lxc.owbpap0l/downtmp/build.mBX/src/debian/tests/test-nut.py", 
line 290, in _nut_setvar

self.assertTrue(rc == 0, 'upsrw: ' + report)
AssertionError: False is not true : upsrw: Unexpected response from 
upsd: ERR DRIVER-NOT-CONNECTED




https://ci.debian.net/data/autopkgtest/testing/arm64/n/nut/27920723/log.gz

==
FAIL: test_upsrw (__main__.BasicTest)
Test upsrw
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.6w4eu3i1/downtmp/build.ygz/src/debian/tests/test-nut.py", 
line 348, in test_upsrw
self.assertTrue('Test' in report, 'UPS Model: ' + report + 'should 
be Test')
AssertionError: False is not true : UPS Model: Init SSL without 
certificate database

Error: Driver not connected
should be Test


https://ci.debian.net/data/autopkgtest/testing/armel/n/nut/27915403/log.gz

==
FAIL: test_upsmon_notif (__main__.BasicTest)
Test upsmon notifications
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.o4_4d1j4/downtmp/build.9H9/src/debian/tests/test-nut.py", 
line 357, in test_upsmon_notif

self._nut_setvar('ups.status', 'OB')
  File 
"/tmp/autopkgtest-lxc.o4_4d1j4/downtmp/build.9H9/src/debian/tests/test-nut.py", 
line 290, in _nut_setvar

self.assertTrue(rc == 0, 'upsrw: ' + report)
AssertionError: False is not true : upsrw: Unexpected response from 
upsd: ERR DRIVER-NOT-CONNECTED



==
FAIL: test_upsrw (__main__.BasicTest)
Test upsrw
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.o4_4d1j4/downtmp/build.9H9/src/debian/tests/test-nut.py", 
line 344, in test_upsrw

self._nut_setvar('ups.model', 'Test')
  File 
"/tmp/autopkgtest-lxc.o4_4d1j4/downtmp/build.9H9/src/debian/tests/test-nut.py", 
line 290, in _nut_setvar

self.assertTrue(rc == 0, 'upsrw: ' + report)
AssertionError: False is not true : upsrw: Unexpected response from 
upsd: ERR DRIVER-NOT-CONNECTED



https://ci.debian.net/data/autopkgtest/testing/s390x/n/nut/27879288/log.gz

==
FAIL: test_daemons_pid (__main__.BasicTest)
Test daemons using PID files
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.f33j3uxh/downtmp/build.b5v/src/debian/tests/test-nut.py", 
line 313, in test_daemons_pid

self._testDaemons(daemons)
  File 
"/tmp/autopkgtest-lxc.f33j3uxh/downtmp/build.b5v/src/debian/tests/test-nut.py", 
line 283, in _testDaemons

self.assertTrue(os.path.exists(pidfile), warning)
AssertionError: False is not true : Could not find pidfile 
'/run/nut/dummy-ups-dummy-dev1.pid'


==
FAIL: test_upsmon_notif (__main__.BasicTest)
Test upsmon notifications
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.f33j3uxh/downtmp/build.b5v/src/debian/tests/test-nut.py", 
line 357, in test_upsmon_notif

self._nut_setvar('ups.status', 'OB')
  File 
"/tmp/autopkgtest-lxc.f33j3uxh/downtmp/build.b5v/src/debian/tests/test-nut.py", 
line 290, in _nut_setvar

self.assertTrue(rc == 0, 'upsrw: ' + report)
AssertionError: False is not true : upsrw: Unexpected response from 
upsd: ERR DRIVER-NOT-CONNECTED




OpenPGP_signature
Description: OpenPGP digital signature