Bug#1064852: incus: missing depends on iproute2

[Helmut Grohne]

Control: tags -1 + moreinfo

Hi Mathias,

On Tue, Feb 27, 2024 at 01:33:08AM +, Mathias Gibbens wrote:
>   iproute2 is Priority: important, which according to Policy §2.5 means
> that it is generally expected to be present on a Debian system. Do you
> have a specific use case where for some reason you don't have iproute2
> installed?

While that means iproute2 is installed by default, it still does not
mean you can rely on its presence. It is "Essential: yes" that allows
you to skip emitting the dependency. Users are entitled to remove
important packages and often do so.

>   I'm initially reluctant to explicitly list iproute2 as a dependency
> for Incus unless there's some very compelling reason.

I think that it is the failure mode that compells me this to be serious.
When iproute2 is missing all the incus commands hang and you spend a
long time digging why this thing doesn't work at all. If incus were
telling me (on the cli) that iproute2 is missing and offering ways of
working without, I'd see things differently.

Conversely, what is the maintenance cost of having this dependency?

Helmut

Processed: Re: incus: missing depends on iproute2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1064852 [incus] incus: missing depends on iproute2
Ignoring request to alter tags of bug #1064852 to the same tags previously set

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

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Daniel Swarbrick]

It appears that bumping prometheus/common to 0.47.0 in the prometheus 
go.mod will reproduce the test failure.


prometheus/common 0.46.0 and earlier does not provoke the test failure.



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1060459: marked as done (scalpel: Scalpel not working on Apple Silicon)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2024 02:58:25 +
with message-id 
and subject line Bug#1060459: fixed in scalpel 1.60+git20240110.6960eb2-1
has caused the Debian Bug report #1060459,
regarding scalpel: Scalpel not working on Apple Silicon
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.)


-- 
1060459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scalpel
Version: 1.60-10
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: goldenrich...@gmail.com

Dear Maintainer,

   * What led up to the situation?

I am the author of Scalpel.  Execution of Scalpel 1.60 (the version
that is currently in the scalpel package on Debian et al) fails
completely on VMs hosted on Apple Silicon because of some
long-standing memory corruption bugs.  It may also work incorrectly on
other platforms.

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

I have placed updated source distros for Scalpel 1.60 as well as the
newer (and more powerful) Scalpel 2.02 on GitHub via
https://github.com/nolaforensix/scalpel-1.60 and
https://github.com/nolaforensix/scalpel-2.02.  My recommendation is to
rebuild the 1.60 package from the updated source and also consdering
adding 2.02.

   * What was the outcome of this action?

Scalpel is broken and I fixed it :)

   * What outcome did you expect instead?

N/A?


-- System Information:
Distributor ID: Kali
Description:Kali GNU/Linux Rolling
Release:2023.4
Codename:   kali-rolling
Architecture: x86_64

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

Versions of packages scalpel depends on:
ii  libc6  2.37-12

scalpel recommends no packages.

scalpel suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: scalpel
Source-Version: 1.60+git20240110.6960eb2-1
Done: Arnaud Rebillout 

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated scalpel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 27 Feb 2024 08:40:12 +0700
Source: scalpel
Architecture: source
Version: 1.60+git20240110.6960eb2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Arnaud Rebillout 
Closes: 1060459
Changes:
 scalpel (1.60+git20240110.6960eb2-1) unstable; urgency=medium
 .
   * Update upstream URLs
   * New upstream version 1.60+git20240110.6960eb2 (Closes: #1060459)
   * Drop patches applied upstream
   * Misc updates: README was renamed, update author email address
Checksums-Sha1:
 97968e23da18a2e82e1befdd5e933613056d52ed 2051 
scalpel_1.60+git20240110.6960eb2-1.dsc
 e421896c4c5ff1ae2f0ba53d7a4be08be807aac3 60680 
scalpel_1.60+git20240110.6960eb2.orig.tar.xz
 7d05b5c7b03dfa43378810daaa474e96cfb737a2 20412 
scalpel_1.60+git20240110.6960eb2-1.debian.tar.xz
 8a3098b6f878f26e2fa6d8e0df17c13be227b2d8 6512 
scalpel_1.60+git20240110.6960eb2-1_source.buildinfo
Checksums-Sha256:
 e5c3ba48c3004e43fcf1fed5b2b97f61b2e2099ef243c10233917d2e41504cdb 2051 
scalpel_1.60+git20240110.6960eb2-1.dsc
 f5f272367e9409feb6a2a5429683a00c00f888e4bd4314ffad35b09f61bdf6d8 60680 
scalpel_1.60+git20240110.6960eb2.orig.tar.xz
 de0048ea47c303d3fc5f22aac276cdce8bb74b3f8f9f633c750b0370240aa7d7 20412 
scalpel_1.60+git20240110.6960eb2-1.debian.tar.xz
 4afa6b928163f07db4975142863591b69f1ccdc62b76706a65cec5c7e0cc4d7b 6512 
scalpel_1.60+git20240110.6960eb2-1_source.buildinfo
Files:
 125bedadbeb8b17aa5b311c2a7fba64e 2051 utils optional 
scalpel_1.60+git20240110.6960eb2-1.dsc
 e7f8c093dde48855247e0c78109e2403 60680 utils optional 
scalpel_1.60+git20240110.6960eb2.orig.tar.xz
 caa8159fde7ef6d7f75606839f30599c 20412 utils optional 
scalpel_1.60+git20240110.6960eb2-1.debian.tar.xz
 

Bug#1062456: marked as done (ipset: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2024 02:48:16 +
with message-id 
and subject line Bug#1062456: fixed in ipset 7.21-2
has caused the Debian Bug report #1062456,
regarding ipset: NMU diff for 64-bit time_t transition
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.)


-- 
1062456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipset
Version: 7.19-1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
ipset as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for ipset
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru ipset-7.19/debian/changelog ipset-7.19/debian/changelog
--- ipset-7.19/debian/changelog 2023-10-28 06:00:43.0 +
+++ ipset-7.19/debian/changelog 2024-02-01 15:40:38.0 +
@@ -1,3 +1,10 @@
+ipset (7.19-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 15:40:38 +
+
 ipset (7.19-1) unstable; urgency=medium
 
   * [a1552d1] New upstream version 7.19
diff -Nru ipset-7.19/debian/control ipset-7.19/debian/control
--- ipset-7.19/debian/control   2023-10-28 06:00:43.0 +
+++ ipset-7.19/debian/control   2024-02-01 15:40:37.0 +
@@ -42,7 +42,7 @@
 Section: libdevel
 Architecture: linux-any
 Multi-Arch: same
-Depends: libipset13 (= ${binary:Version}), libmnl-dev, ${misc:Depends}
+Depends: libipset13t64 (= ${binary:Version}), libmnl-dev, ${misc:Depends}
 Description: development files for IP sets
  IP sets are a framework inside the Linux 2.4.x and 2.6.x kernel which can be
  administered by the ipset(8) utility. Depending on the type, currently an
@@ -64,7 +64,10 @@
  This package contains the development libraries and header files you need to
  develop your programs using the IP sets library.
 
-Package: libipset13
+Package: libipset13t64
+Provides: ${t64:Provides}
+Replaces: libipset13
+Breaks: libipset13 (<< ${source:Version})
 Section: libs
 Architecture: linux-any
 Multi-Arch: same
diff -Nru ipset-7.19/debian/libipset13.install 
ipset-7.19/debian/libipset13.install
--- ipset-7.19/debian/libipset13.install2023-10-28 06:00:43.0 
+
+++ ipset-7.19/debian/libipset13.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru ipset-7.19/debian/libipset13.symbols 
ipset-7.19/debian/libipset13.symbols
--- ipset-7.19/debian/libipset13.symbols2023-10-28 06:00:43.0 
+
+++ ipset-7.19/debian/libipset13.symbols1970-01-01 00:00:00.0 
+
@@ -1,162 +0,0 @@
-libipset.so.13 libipset13 #MINVER#
-* Build-Depends-Package: libipset-dev
- LIBIPSET_1.0@LIBIPSET_1.0 7.0-1~
- LIBIPSET_2.0@LIBIPSET_2.0 7.0-1~
- 

Bug#1064851: marked as done (4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2024 02:42:32 +
with message-id 
and subject line Bug#1064851: fixed in emacs 1:29.2+1-2
has caused the Debian Bug report #1064851,
regarding 4 packages from emacs have an undeclared file conflict on 
/usr/bin/emacsclient.emacs
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.)


-- 
1064851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-gtk,emacs-nox,emacs-pgtk,emacs-lucid
Version: 1:29.2+1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + emacs-bin-common

4 packages from emacs have an undeclared file conflict. This may result
in an unpack error from dpkg.

The file /usr/bin/emacsclient.emacs is contained in the packages
 * emacs-bin-common
   * 1:27.1+1-3.1+deb11u1 as present in bullseye
   * 1:27.1+1-3.1+deb11u2 as present in bullseye-security
   * 1:28.2+1-15 as present in bookworm
   * 1:29.1+1-5 as present in trixie
   * 1:29.1+1-5~bpo12+1 as present in bookworm-backports
 * emacs-gtk/1:29.2+1-1 as present in unstable
 * emacs-lucid/1:29.2+1-1 as present in unstable
 * emacs-nox/1:29.2+1-1 as present in unstable
 * emacs-pgtk/1:29.2+1-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:29.2+1-2
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated emacs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 27 Feb 2024 09:26:29 +0800
Source: emacs
Architecture: source
Version: 1:29.2+1-2
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning 
Changed-By: Sean Whitton 
Closes: 1064851
Changes:
 emacs (1:29.2+1-2) unstable; urgency=medium
 .
   * Fix Breaks/Replaces by prepending missing epoch (Closes: #1064851)
Checksums-Sha1:
 6d91dd4d950232b7622e8711db9f762355bae81f 3103 emacs_29.2+1-2.dsc
 da7d9996fd39de4cf17888c740ef167244e0a9b7 63508 emacs_29.2+1-2.debian.tar.xz
Checksums-Sha256:
 c111f55b0a70ce64f740061ad27bada91fb4326db0c714c0117e207f5af39b9a 3103 
emacs_29.2+1-2.dsc
 bd34d81adc583f7977a7eb5609969eb1392d5bcf8ff3f1e03a156d9fe0d24982 63508 
emacs_29.2+1-2.debian.tar.xz
Files:
 1fe9ab9f577852a9b2276af61035aa69 3103 editors optional emacs_29.2+1-2.dsc
 7ccfaba7794b0354e9b95a807e65c125 63508 editors optional 
emacs_29.2+1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmXdQ6IACgkQaVt65L8G
YkB23w/+KKHJLuzOLvarnMcjiaddMKBxKgJ7sml886p0wCtpjzlsX1TjxjAKprhE
SZVyZBvJ9P3JHp84ojHXmATzzDHHc2svgO8knmLadLc5ajultdojjdBBUo5kGa99
Dv2noetLPmtrVRIy7y1snJR+XS+nK0764/4doFwkpEb7A7bV4ec+JQ9Fsp/+B00U
mizHqGOtUY7rtP+BaHIwt02BDXK621j4Th8VIxPJSrVBMXArNBY6v1o+WZSFFGXy
v7nbcpf9R7Ma4fFISGNhfuPA8lE9smKURuc3bYnPqVgDMf2T+599m6GNI6xkM+a2
/N4D8t7UiiDzGI8T+12xfKQlhJCFgN+o1gL8Z/nf/hnj84pRl5GvpDcauXK/vVDJ
DNk4J3GVAlNY2K8gOlkb98T/59MNw9m/4H0WR3GIAUHURe2jA0P9+G0J+y/fRXF+
FqqD6wE6HndUfppdMlQKAAiSpc5OAQwL2pRMSOlzY2ZIKaMw9X0a04+EcnfbTqr0
R/EwNiCUFnh7DC9pWfJ5lwvytaRiZ7lprq/ZupgYriyg8mfmdCpwKkqIgNob8hbF
ZXhjd2yiYLMTMEmIew5s+UzNMiKyR2zPlpLeMFQtI2UGFpjFBbiRHBS2Zcw1PuiG
gjsdMxksZeRg00moO9oQGh+UHxPQVPBVq+QWdY1/+qpE+lZzsnc=
=/GqI
-END PGP SIGNATURE-



pgpRKP7ARBIDI.pgp
Description: PGP signature
--- End Message ---

Bug#1051425: marked as done (ukwm: undeclared dependency on libqt5-ukui-style1)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2024 10:19:59 +0800
with message-id 

and subject line 
has caused the Debian Bug report #1051425,
regarding ukwm: undeclared dependency on libqt5-ukui-style1
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.)


-- 
1051425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukwm
Version: 1.2.0-1
Severity: serious

I installed ukwm on my Debian GNOME Testing install. This adds a UKUI
entry to the session list on my login screen. It is impossible to log
in to that session: it freezes before the desktop is fully loaded.

My systemd journal indicates this is because this file is missing:
/usr/share/glib-2.0/schemas/org.ukui.style.gschema.xml

It is provided by libqt5-ukui-style1. Installing
qt5-ukui-platformtheme would install that package but nothing in
Debian depends on qt5-ukui-platformtheme

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: ukui-session-manager
Source-Version: 4.0.0.0-1

Close as stated by handsome_feng.

Thanks--- End Message ---

Bug#1060459: scalpel: Scalpel not working on Apple Silicon

[Arnaud Rebillout]

Hello, and thanks for reaching out!

On Thu, 11 Jan 2024 13:44:03 -0600 "Golden G. Richard III" 
 wrote:


> I have placed updated source distros for Scalpel 1.60 as well as the
> newer (and more powerful) Scalpel 2.02 on GitHub via
> https://github.com/nolaforensix/scalpel-1.60 and
> https://github.com/nolaforensix/scalpel-2.02. My recommendation is to
> rebuild the 1.60 package from the updated source and also consdering
> adding 2.02.

I have updated the package to latest commit on 
https://github.com/nolaforensix/scalpel-1.60.


I will consider packaging the 2.02 when I have a bit of time, this week 
or next week hopefully.


Best,

--
Arnaud Rebillout / OffSec / Kali Linux Developer

Processed: Re: incus: missing depends on iproute2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1064852 [incus] incus: missing depends on iproute2
Added tag(s) moreinfo.

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

Bug#1064852: incus: missing depends on iproute2

[Mathias Gibbens]

Control: tags -1 + moreinfo

Hi Helmut,

  iproute2 is Priority: important, which according to Policy §2.5 means
that it is generally expected to be present on a Debian system. Do you
have a specific use case where for some reason you don't have iproute2
installed?

  I'm initially reluctant to explicitly list iproute2 as a dependency
for Incus unless there's some very compelling reason.

Mathias


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

Processed: Re: Bug#1064851: 4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo + pending
Bug #1064851 [emacs-gtk,emacs-nox,emacs-pgtk,emacs-lucid] 4 packages from emacs 
have an undeclared file conflict on /usr/bin/emacsclient.emacs
Removed tag(s) moreinfo.
Bug #1064851 [emacs-gtk,emacs-nox,emacs-pgtk,emacs-lucid] 4 packages from emacs 
have an undeclared file conflict on /usr/bin/emacsclient.emacs
Added tag(s) pending.

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

Bug#1064851: 4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs

[Sean Whitton]

control: tag -1 - moreinfo + pending

Hello,

On Tue 27 Feb 2024 at 09:17am +08, Sean Whitton wrote:

> Hmm, I added Breaks/Replaces, and piuparts is happy.  Requesting manual
> review.  Thank you.

Ah, my relations were missing the 1: epoch.  Uploading shortly.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1064698: marked as done (python-libcst: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2024 01:25:41 +
with message-id 
and subject line Bug#1064698: fixed in python-libcst 1.2.0-1
has caused the Debian Bug report #1064698,
regarding python-libcst: FTBFS: make[1]: *** [debian/rules:16: 
override_dh_auto_build] Error 25
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.)


-- 
1064698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-libcst
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mv native/Cargo.lock native/Cargo.lock.saved
> dh_auto_build
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12  
> * Building wheel...
> WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml 
> does not contain a tool.setuptools_scm section'
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-cpython-312
> creating build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/__init__.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_typed_visitor_base.py -> 
> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_position.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_types.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_batched_visitor.py -> 
> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_version.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_typed_visitor.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_removal_sentinel.py -> 
> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_flatten_sentinel.py -> 
> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/tool.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_type_enforce.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_metadata_dependent.py -> 
> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_add_slots.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_maybe_sentinel.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_visitors.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_tabs.py -> build/lib.linux-x86_64-cpython-312/libcst
> copying libcst/_exceptions.py -> build/lib.linux-x86_64-cpython-312/libcst
> creating build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_visitor.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/__init__.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_deep_replace.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_e2e.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_batched_visitor.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/__main__.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_deep_clone.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_tabs.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_add_slots.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_type_enforce.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_fuzz.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_tool.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_exceptions.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> copying libcst/tests/test_pyre_integration.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/tests
> creating build/lib.linux-x86_64-cpython-312/libcst/_nodes
> copying libcst/_nodes/whitespace.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/_nodes
> copying libcst/_nodes/__init__.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/_nodes
> copying libcst/_nodes/deep_equals.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/_nodes
> copying libcst/_nodes/base.py -> 
> build/lib.linux-x86_64-cpython-312/libcst/_nodes
> copying libcst/_nodes/op.py -> 
> 

Bug#1064851: 4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Mon 26 Feb 2024 at 06:26pm +01, Helmut Grohne wrote:

> 4 packages from emacs have an undeclared file conflict. This may result
> in an unpack error from dpkg.
>
> The file /usr/bin/emacsclient.emacs is contained in the packages
>  * emacs-bin-common
>* 1:27.1+1-3.1+deb11u1 as present in bullseye
>* 1:27.1+1-3.1+deb11u2 as present in bullseye-security
>* 1:28.2+1-15 as present in bookworm
>* 1:29.1+1-5 as present in trixie
>* 1:29.1+1-5~bpo12+1 as present in bookworm-backports
>  * emacs-gtk/1:29.2+1-1 as present in unstable
>  * emacs-lucid/1:29.2+1-1 as present in unstable
>  * emacs-nox/1:29.2+1-1 as present in unstable
>  * emacs-pgtk/1:29.2+1-1 as present in unstable
>
> These packages can be unpacked concurrently, because there is no
> relevant Replaces or Conflicts relation. Attempting to unpack these
> packages concurrently results in an unpack error from dpkg, because none
> of the packages installs a diversion for the affected file.

Hmm, I added Breaks/Replaces, and piuparts is happy.  Requesting manual
review.  Thank you.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: Re: Bug#1064851: 4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #1064851 [emacs-gtk,emacs-nox,emacs-pgtk,emacs-lucid] 4 packages from emacs 
have an undeclared file conflict on /usr/bin/emacsclient.emacs
Added tag(s) moreinfo.

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

Bug#1064713: marked as done (breezy-debian: FTBFS: make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 27 Feb 2024 00:05:46 +
with message-id 
and subject line Bug#1064713: fixed in breezy-debian 2.8.79
has caused the Debian Bug report #1064713,
regarding breezy-debian: FTBFS: make[1]: *** [debian/rules:24: 
override_dh_auto_test] Error 1
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.)


-- 
1064713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breezy-debian
Version: 2.8.78
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> BRZ_CONCURRENCY=8 BRZ_PLUGINS_AT=debian@/<> 
> BRZ_PLUGIN_PATH=-site:-user /usr/bin/brz selftest \
> --parallel=fork -v -s bp.debian
> Error: PyErr { type: , value: 
> ModuleNotFoundError("No module named 'tzlocal'"), traceback: Some( object at 0x7fbbce417980>) }
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/breezy-debian_2.8.78_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=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 mark 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: breezy-debian
Source-Version: 2.8.79
Done: Jelmer Vernooij 

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated breezy-debian 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, 26 Feb 2024 23:42:44 +
Source: breezy-debian
Architecture: source
Version: 2.8.79
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Jelmer Vernooij 
Closes: 1064713
Changes:
 breezy-debian (2.8.79) unstable; urgency=medium
 .
   * Depend on breezy with fixed timezone handling. Closes: #1064713
Checksums-Sha1:
 8385b6de34b5187edcfed0e0144e39daf8a8ae28 1810 breezy-debian_2.8.79.dsc
 40fec25febb29fe8acc62a9e8f27ccb6b614e392 180744 breezy-debian_2.8.79.tar.xz
 e57ab59b0b33c309b3c1914ae57ab0182c252d74 7891 
breezy-debian_2.8.79_source.buildinfo
Checksums-Sha256:
 69c4b88f639789868525368d7fd33d964c383a90c06306795fee414c16b0e16a 1810 
breezy-debian_2.8.79.dsc
 617f19c620756ff78fbab96db9a2644adbd4f6bdc446201ae8ab43ae6f7ecdd1 180744 
breezy-debian_2.8.79.tar.xz
 27f29e8d2f2ba954e46a39bdd998ff0d400ed50dd43ae07dc7acc41d3e791c55 7891 
breezy-debian_2.8.79_source.buildinfo
Files:
 fe49c21c4911ee5556d24d80428e3680 1810 vcs optional breezy-debian_2.8.79.dsc
 22308f341209e8bf255892a216fe8d7f 180744 vcs optional 
breezy-debian_2.8.79.tar.xz
 ab773101145f6e24f6c5e26200322bdc 7891 vcs optional 
breezy-debian_2.8.79_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmXdIz0ACgkQMG8hYYBC
UGZfaAf+L1cjJCxT+cWHF6yZhSYcTgEiuqba5ZaxhVxxdq/fG02LX66O31gZ7qoI
K3X+AKZJknD4lNRVBQouxsiK7vBrsfbWpXYUobef1Vky4raiJHTl8u5mZ96yQLBW
98fg8+4IzFhrNl5hYpgGLHXaN1fvVa5xMYr1LL00aBnT5ygrSerDuV7BUar9L1O5
AhWRumc4/It8XvwamYiTFyxYXBFaCwoF15H/2n43H2pS1KgVuenwGZkK/f0xZ4ul
5PtlJoZ593c1SDblF5h9WChaPmnN4xmwruNOCZCSP5Y/nXBABuIDJk9U1g7H3/eV
QExT9Xz3PRrhuQotQS9he2pMi3LHSQ==
=4duq
-END PGP SIGNATURE-



pgp6CGgCM1BDK.pgp
Description: PGP signature
--- End Message ---

Bug#1064716: marked as done (ros-vcstools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 23:49:41 +
with message-id 
and subject line Bug#1063029: fixed in breezy 3.3.5-6
has caused the Debian Bug report #1063029,
regarding ros-vcstools: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" 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.)


-- 
1063029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-vcstools
Version: 0.1.42-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/git_archive_all.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/git.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/vcs_base.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/common.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/vcs_abstraction.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/hg.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/bzr.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/__version__.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/svn.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> copying src/vcstools/tar.py -> 
> /<>/.pybuild/cpython3_3.12/build/vcstools
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/git_archive_all.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/git.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/vcs_base.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/common.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/vcs_abstraction.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/hg.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/bzr.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/__version__.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/svn.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
> copying src/vcstools/tar.py -> 
> /<>/.pybuild/cpython3_3.11/build/vcstools
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:310: git config --global protocol.file.allow always
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.12/build; 
> python3.12 -m pytest test
> = test session starts 
> ==
> platform linux -- Python 3.12.2, pytest-7.4.4, pluggy-1.4.0
> rootdir: /<>
> collected 148 items
> 
> test/test_base.py ...[  
> 4%]
> test/test_bzr.py EEE [ 
> 17%]
> test/test_code_format.py .   [ 
> 18%]
> test/test_git.py [ 
> 47%]
> test/test_git_subm.py    [ 
> 56%]
> test/test_hg.py ...  [ 
> 74%]
> test/test_svn.py ..  [ 
> 91%]
> test/test_tar.py .   [ 
> 97%]
> test/test_vcs_abstraction.py ... 
> [100%]
> 
>  ERRORS 
> 
>  ERROR at setup of BzrClientTest.testDiffClean 
> _
> 
> self = 
> 
> 

Bug#1063029: marked as done (rust-breezyshim fails autopkg tests with breezy from unstable, blocking migration)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 23:49:41 +
with message-id 
and subject line Bug#1063029: fixed in breezy 3.3.5-6
has caused the Debian Bug report #1063029,
regarding rust-breezyshim fails autopkg tests with breezy from unstable, 
blocking migration
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.)


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

Package: src:rust-breezyshim
Version: 0.1.77-1
Severity: serious
Tags: sid trixie

rust-breezyshim fails autopkg tests with breezy from unstable, blocking 
migration. missing dependency again?


[..]
182s failures:
182s
182s  plugin::tests::test_load_plugins stdout 
182s thread 'plugin::tests::test_load_plugins' panicked at 'called 
`Result::unwrap()` on an `Err` value: PyErr { type: 'ModuleNotFoundError'>, value: ModuleNotFoundError("No module named 
'tzlocal'"), traceback: Some() }', 
src/plugin.rs:7:30

182s stack backtrace:
182s0: rust_begin_unwind
182s  at 
/usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5

182s1: core::panicking::panic_fmt
182s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14

182s2: core::result::unwrap_failed
182s  at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
182s3: core::result::Result::unwrap
182s  at 
/usr/src/rustc-1.70.0/library/core/src/result.rs:1089:23

182s4: breezyshim::plugin::load_plugins::{{closure}}
182s  at ./src/plugin.rs:7:9
182s5: pyo3::marker::Python::with_gil
182s  at 
/usr/share/cargo/registry/pyo3-0.20.2/src/marker.rs:434:9

182s6: breezyshim::plugin::load_plugins
182s  at ./src/plugin.rs:4:5
182s7: breezyshim::plugin::tests::test_load_plugins
182s  at ./src/plugin.rs:17:9
182s8: breezyshim::plugin::tests::test_load_plugins::{{closure}}
182s  at ./src/plugin.rs:16:28
182s9: core::ops::function::FnOnce::call_once
182s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5

182s   10: core::ops::function::FnOnce::call_once
182s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
182s note: Some details are omitted, run with `RUST_BACKTRACE=full` for 
a verbose backtrace.

182s
182s
182s failures:
182s plugin::tests::test_load_plugins
182s
182s test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 
filtered out; finished in 0.07s

182s
182s error: test failed, to rerun pass `--lib`
183s autopkgtest [10:09:37]: test librust-breezyshim-dev:: 
---]
183s autopkgtest [10:09:37]: test librust-breezyshim-dev::  - - - - - - 
- - - - results - - - - - - - - - -

183s librust-breezyshim-dev: FAIL non-zero exit status 101
183s autopkgtest [10:09:37]:  summary
183s rust-breezyshim:@FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: breezy
Source-Version: 3.3.5-6
Done: Jelmer Vernooij 

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated breezy 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, 26 Feb 2024 23:28:52 +
Source: breezy
Architecture: source
Version: 3.3.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Breezy Maintainers 
Changed-By: Jelmer Vernooij 
Closes: 1063029
Changes:
 breezy (3.3.5-6) unstable; urgency=medium
 .
   * Add python3-tzlocal to Depends, rather than Suggests. Closes:
 #1063029
Checksums-Sha1:
 cd350d63e51e66985f5203d2de04c92684e92e39 2629 breezy_3.3.5-6.dsc
 316fe4c9ed40b97ca2607c0bf6b5c9ab00720e75 76220 breezy_3.3.5-6.debian.tar.xz
 e4fddbec1d71f13799caa6a6b1319a36ed8750ca 19787 breezy_3.3.5-6_source.buildinfo
Checksums-Sha256:
 20eff94c7c0fe024fe4c8815181166ac68a57420c0405da485ec46db3f33b1d2 2629 
breezy_3.3.5-6.dsc
 69b513d380d04cce28c6b6e2864285c519877e2420fb9c0762fe548f4aa41f1c 76220 

Processed: tagging 1026584

[Debian Bug Tracking System]

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

> tags 1026584 + pending
Bug #1026584 [src:python-morris] python-morris: FTBFS: AssertionError: Failed 
doctest test for morris
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1064854: Breaks tex-common's configuration

[Debian Bug Tracking System]

Processing control commands:

> affects -1 texlive-binaries
Bug #1064854 [luametatex] Breaks tex-common's configuration
Added indication that 1064854 affects texlive-binaries
> merge -1 1064402
Bug #1064854 [luametatex] Breaks tex-common's configuration
Bug #1064854 [luametatex] Breaks tex-common's configuration
Marked as found in versions luametatex/2.11.01+ds-2.
Bug #1064402 [luametatex] luametatex: "mtxrun --generate": lua error : startup 
file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i'
Merged 1064402 1064854
> affects -1 context
Bug #1064854 [luametatex] Breaks tex-common's configuration
Bug #1064402 [luametatex] luametatex: "mtxrun --generate": lua error : startup 
file: /bin/mtxrun.lua:2438: attempt to assign to const variable 'i'
Added indication that 1064854 affects context
Added indication that 1064402 affects context

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

Bug#1064854: Breaks tex-common's configuration

[Preuße]

Control: affects -1 texlive-binaries
Control: merge -1 1064402
Control: affects -1 context



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed (with 2 errors): Re: Bug#1064854: Breaks tex-common's configuration

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 luametatex
Bug #1064854 [context] Breaks tex-common's configuration
Bug reassigned from package 'context' to 'luametatex'.
No longer marked as found in versions context/2023.05.05.20230730+dfsg-2.
Ignoring request to alter fixed versions of bug #1064854 to the same values 
previously set
> severity -1 grave
Bug #1064854 [luametatex] Breaks tex-common's configuration
Severity set to 'grave' from 'critical'
> merge -1 1064402
Bug #1064854 [luametatex] Breaks tex-common's configuration
Unable to merge bugs because:
affects of #1064402 is 'texlive-binaries' not ''
Failed to merge 1064854: Did not alter merged bugs.

> affects -1 context
Failed to mark 1064854 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/1064854 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1064854 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1064854 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


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

Bug#1064854: Breaks tex-common's configuration

[Preuße]

Control: reassign -1 luametatex
Control: severity -1 grave
Control: merge -1 1064402
Control: affects -1 context

On 26.02.2024 18:50, julien.pu...@gmail.com wrote:

Hi,


since a few days, I saw a configuration issue with the tex-common
package. (What I don't get is why it actually needs configuration since
I don't see uploads since months.)



No, it is in the upgraded luametatex, which is for the upcoming TL 2024 
and should have been uploaded to experimental. Downgrade it and put it 
on hold. apt-listbugs is helpful here. Sorry, for the inconvenience!


Hilmar
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: tags

[Debian Bug Tracking System]

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

> tags 1064650 patch
Bug #1064650 [src:snapd-glib] FTBFS on mips64el, ppc64el and s390x
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#1064759: marked as done (libhttp-nio-java: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.hom

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 22:04:41 +
with message-id 
and subject line Bug#1064759: fixed in libhttp-nio-java 1.1.0+dfsg-3
has caused the Debian Bug report #1064759,
regarding libhttp-nio-java: FTBFS: dh_auto_test: error: gradle --info --console 
plain --offline --stacktrace --no-daemon --refresh-dependencies 
--gradle-user-home .gradle -Duser.home=. -Duser.name=debian 
-Ddebian.package=libhttp-nio-java -Dfile.encoding=UTF-8 --parallel 
--max-workers=8 test returned exit code 1
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.)


-- 
1064759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhttp-nio-java
Version: 1.1.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Putting the version number in the custom pom
> sed 's/\(VERSION_PACKAGE\)/\11.1.0+dfsg/; 
> s/VERSION_PACKAGE\(.*\)+dfsg[0-9]*/\1/' debian/pom.xml.in > debian/pom.xml
> dh_auto_configure
> make[1]: Leaving directory '/<>'
>jh_linkjars
>dh_auto_build
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=libhttp-nio-java -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 jar
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment (build 17.0.10+7-Debian-1)
> OpenJDK 64-Bit Server VM (build 17.0.10+7-Debian-1, mixed mode, sharing)
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-17-openjdk-amd64/bin/java --add-opens 
> java.base/java.lang=ALL-UNNAMED 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 1.052 secs.
> The client will now receive all logging from the daemon (pid: 924327). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-924327.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@70b8209a
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@70b8209a
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@18d58a43
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@1aedad95
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'http-nio']
>   Keep-alive timer started
>   Adding Debian repository to project 'http-nio'
> Parallel execution is an incubating feature.
> Evaluating root project 'http-nio' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/build.gradle' using 
> BuildScriptTransformer.
>   Adding Maven pom generation to project 

Bug#1064859: marked as done (rust-futures-rustls: Fails to build from source)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 21:37:41 +
with message-id 
and subject line Bug#1064859: fixed in rust-futures-rustls 0.24.0-3
has caused the Debian Bug report #1064859,
regarding rust-futures-rustls: Fails to build from 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.)


-- 
1064859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-futures-rustls
Version: 0.24.0-1
Severity: serious
Tags: ftbfs

rust-futures-rustls fails to build from source because of build test failures.

https://buildd.debian.org/status/package.php?p=rust-futures-rustls

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: rust-futures-rustls
Source-Version: 0.24.0-3
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-futures-rustls 
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, 26 Feb 2024 22:03:15 +0100
Source: rust-futures-rustls
Architecture: source
Version: 0.24.0-3
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1064859
Changes:
 rust-futures-rustls (0.24.0-3) unstable; urgency=medium
 .
   * add patch cherry-picked upstream
 to replace expired test certificates;
 closes: bug#1064859.
Checksums-Sha1:
 fbf91060a65269de3136d3574a5556e87aa2a0ed 2833 rust-futures-rustls_0.24.0-3.dsc
 110f13f14ff7cd09dbecc7f909af91466bec7658 25180 
rust-futures-rustls_0.24.0-3.debian.tar.xz
 6bedb0ee57e9323d1c59114c9b07acd43faebc3a 12140 
rust-futures-rustls_0.24.0-3_amd64.buildinfo
Checksums-Sha256:
 34e873a08770f6df449df8a93b328cfe3f871a6ca94867bdb649679febb819aa 2833 
rust-futures-rustls_0.24.0-3.dsc
 affe60ff3585880678deabf6bc76c6f58fdd00fdfa33260f2cdf59a8f0d784cd 25180 
rust-futures-rustls_0.24.0-3.debian.tar.xz
 92ab50ddedf379a44de3c56bff3c3fe610579781e261478a0defaf49c7c7200f 12140 
rust-futures-rustls_0.24.0-3_amd64.buildinfo
Files:
 1865061f1bf88ef4c9718682d97b3f66 2833 rust optional 
rust-futures-rustls_0.24.0-3.dsc
 27ca78cae034b34a763431f3aacf3db5 25180 rust optional 
rust-futures-rustls_0.24.0-3.debian.tar.xz
 1ecdb1cfccde4054393403b0d23d9e58 12140 rust optional 
rust-futures-rustls_0.24.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmXc/SYACgkQLHwxRsGg
ASG3xw//czT0henNysRiAOlCOUpOCHCLQ74aNguEM6tyQCMN3nZGIUZdMKDrYuFl
Yxs1t7UtLK45jn5d/GboWOlW0SX6nTqtS2Y6skqNIoz92FflolGSVy9ahYAUBhYD
CrDyN+gdOnmc7gYhckssuX+yMpXuuZsBT9NdPKouDxs5UBUYznEtVRavNUFfyE7E
tBpb8dvXRBGtDfYG4rg2ScaJvwwjnG1+wJCLuzBv75XgBuXeL+hFV0k+nURWQfuE
Ek1gDRNG24ym4CRkCNOU1FpYBXLpAqPN5xINBOfkWdBH5XgkgvrjK+iHDM6/VB+y
Pc4EM3xFHy6bXuwhfy2V9c+1d3oddoZolFhmS43zZLrRGbwCMpiEpQy5JWxiE96e
1hm1t0MI4zIsZhO2Mi3O0za1yXWsmFbFOKOW+OGOhVInVAGSRHXqj3j/Atc31beZ
00l6MLjGdSsRMrVZWNfj5QvbD9UyQfvdr7iqiLtHR+bgq1DCUZOMjbu1HmhyHswQ
ZkGfInZXpfq3O1y2kYCW0FbAzVk4tmdat5vm3Jwgq7fDW4UVtzv02DPtk3IxqW56
yJgEdcK93kW334On0RDZvJCsikhjaQI/bWhCy8hKvkn4MV1AsdOfTUx8gVXASHWN
02NlZILX8Bya8C9tgkG3IAXt4G6eboEyFLLZYuSXYsJQcCkXo6o=
=DTq3
-END PGP SIGNATURE-



pgpokZLcuG5zH.pgp
Description: PGP signature
--- End Message ---

Bug#1064598: yagv: crashes with "module 'pyglet.graphics' has no attribute 'vertex_list'"

[Gregor Riepl]

Hi,


AttributeError: module 'pyglet.graphics' has no attribute 'vertex_list'


I suspect this may not be trivial to fix.

yagv depends on pyglet 1.x, which relies on the OpenGL fixed function 
pipeline. Debian has switched to 2.x and no longer supports this. [1]


Unfortunately, it appears that upstream project is dead.
The last commit was in 2017, and any requests by @pere on their bug 
tracker fell on deaf ears: [2]


It's regrettable, but I don't think yagv can be kept with the current 
situation.


As you might right recall, I offered to help with a similar situation in 
printrun, but this got stuck due to the significant effort required and 
a lack of time on my side. It's unlikely that I would be able to help 
with yagv either at the moment.


Sorry...


[1] https://pyglet.readthedocs.io/en/latest/programming_guide/migration.html
[2] https://github.com/jonathanwin/yagv/issues/20

Processed: Re: Bug#1064681: retroarch: FTBFS: make[1]: *** [debian/rules:48: override_dh_auto_configure] Error 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - trixie
Bug #1064681 [src:retroarch] retroarch: FTBFS: glslang is disabled and forced 
to build with SPIRV-Cross support.
Removed tag(s) trixie.
> severity -1 important
Bug #1064681 [src:retroarch] retroarch: FTBFS: glslang is disabled and forced 
to build with SPIRV-Cross support.
Severity set to 'important' from 'serious'

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

Bug#1064681: retroarch: FTBFS: make[1]: *** [debian/rules:48: override_dh_auto_configure] Error 1

[Jonathan McDowell]

Control: tags -1 - trixie
Control: severity -1 important

On Sun, Feb 25, 2024 at 08:48:32PM +0100, Lucas Nussbaum via Pkg-games-devel 
wrote:
> Source: retroarch
> Version: 1.16.0.3+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240224 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

This looks like a glslang issue; #1062799 and the associated autopkgtest
failures for glslang's migration to trixie (e.g.
https://ci.debian.net/packages/g/glslang/testing/amd64/43341664/).

I'm dropping this to important until glslang is fixed.

> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' \
> > retroarch.cfg > debian/retroarch.cfg
> > # See ./configure --help for valid flags
> > # disable flags (i.e. --disable-ffmpeg for example) if there is no package 
> > relative to the feature in Build-Depends
> > ./configure --prefix=/usr \
> > --disable-builtinmbedtls \
> > --disable-builtinbearssl \
> > --disable-builtinflac \
> > --disable-builtinglslang \
> > --disable-builtinzlib \
> > --disable-update_assets \
> > --disable-oss \
> > --disable-vg \
> > --enable-dbus \
> > --enable-spirv_cross \
> > --enable-vulkan \
> > --enable-sse
> > Checking operating system ... Linux 
> > Checking for suitable working C compiler ... /usr/bin/gcc works
> > Checking for suitable working C++ compiler ... /usr/bin/g++ works
> > Checking for pkg-config ... /usr/bin/pkgconf
> > Checking for availability of switch -std=gnu99 in /usr/bin/gcc ... yes
> > Checking for availability of switch -std=c++17 in /usr/bin/g++ ... yes
> > Checking for availability of switch -Wno-unused-result in /usr/bin/gcc ... 
> > yes
> > Checking for availability of switch -Wno-unused-variable in /usr/bin/gcc 
> > ... yes
> > Checking function sd_get_machine_names in -lsystemd ... no
> > Checking presence of package bcm_host ... no
> > Checking function bcm_host_init in -lbcm_host ... no
> > Checking presence of header file EGL/eglext.h ... yes
> > Checking presence of package egl ... 1.5
> > Checking function ass_library_init in -lfribidi -lass ... no
> > Checking existence of -msse -msse2 ... yes
> > Checking function pthread_create in -lpthread ... yes
> > Checking function pthread_key_create in -lpthread ... yes
> > Checking presence of package check >= 0.15 ... no
> > Checking presence of header file scsi/sg.h ... yes
> > Checking function dlopen in -ldl ... yes
> > Checking function socket in -lc ... yes
> > Checking function getaddrinfo in -lc ... yes
> > Checking function fcntl in -lc ... yes
> > Checking function getopt_long in -lc ... yes
> > Checking presence of package alsa ... 1.2.10
> > Checking presence of package libsixel >= 1.6.0 ... no
> > Checking presence of predefined macro AUDIO_SETINFO in sys/audioio.h ... no
> > Checking presence of package rsound >= 1.1 ... no
> > Checking presence of package libroar >= 1.0.12 ... no
> > Checking presence of package jack >= 0.120.1 ... 1.9.21
> > Checking presence of package libpulse ... 16.1
> > Checking presence of package sdl >= 1.2.10 ... no
> > Checking presence of package sdl2 >= 2.0.0 ... 2.30.0
> > Checking presence of package Qt5Core >= 5.2 ... 5.15.10
> > Checking presence of package Qt5Gui >= 5.2 ... 5.15.10
> > Checking presence of package Qt5Widgets >= 5.2 ... 5.15.10
> > Checking presence of package Qt5Concurrent >= 5.2 ... 5.15.10
> > Checking presence of package Qt5Network >= 5.2 ... 5.15.10
> > Checking presence of package openssl >= 1.0.0 ... no
> > Checking presence of package flac ... 1.4.3
> > Checking existence of -lmbedtls -lmbedx509 -lmbedcrypto ... no
> > Notice: HID is disabled, libusb support will also be disabled.
> > Checking existence of -ldinput8 ... no
> > Checking existence of -ld3d9 ... no
> > Checking existence of -ldsound ... no
> > Checking existence of -ld3dx8 ... no
> > Checking existence of -ld3dx9 ... no
> > Checking presence of header file GL/gl.h ... yes
> > Checking existence of -lGL ... yes
> > Checking function cgCreateContext in -lCg -lCgGL ... no
> > Checking presence of package zlib ... 1.3
> > Checking presence of package libavcodec >= 57 ... 60.31.102
> > Checking presence of package libavformat >= 57 ... 60.16.100
> > Checking presence of package libavdevice >= 57 ... 60.3.100
> > Checking presence of package libswresample >= 2 ... 4.12.100
> > Checking presence of package libavutil >= 55 ... 58.29.100
> > Checking presence of package libswscale >= 4 ... 7.5.100
> > Checking presence of header file libavutil/channel_layout.h ... yes
> > Checking function dlopen in -ldl ... yes
> > Checking presence of package gbm >= 9.0 ... 24.0.1-1
> > Checking presence of package libdrm ... 2.4.120
> > Checking presence of package dbus-1 ... 1.14.10
> > Checking presence of package libudev ... 255
> > Checking presence of 

Bug#1064859: rust-futures-rustls: Fails to build from source

[Jeremy Bícha]

Source: rust-futures-rustls
Version: 0.24.0-1
Severity: serious
Tags: ftbfs

rust-futures-rustls fails to build from source because of build test failures.

https://buildd.debian.org/status/package.php?p=rust-futures-rustls

Thank you,
Jeremy Bícha

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Fabio Pedretti]

Ubuntu fixed it with this patch:
https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz

Bug#1056441: marked as done (pyrcb2's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 18:42:39 +
with message-id 
and subject line Bug#1064640: Removed package(s) from unstable
has caused the Debian Bug report #1056441,
regarding pyrcb2's autopkg tests fail with Python 3.12
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.)


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

Package: src:pyrcb2
Version: 0.6.2-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pyrcb2's autopkg tests fail with Python 3.12:

[...]
252s === python3.12 ===
252s = test session starts 
==

252s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
252s rootdir: /tmp/autopkgtest.2RAiQ9/autopkgtest_tmp
252s collected 36 items
252s
252s tests/test_accounts.py . 
 [ 69%]
252s tests/test_itypes.py F...F.. 
 [100%]

252s
252s === FAILURES 
===
252s _ TestItypes.test_idefaultdict 
_

252s
252s self = 
252s
252s def test_idefaultdict(self):
252s self.test_idict(cls=partial(IDefaultDict, None))
252s with self.assertRaises(TypeError):
252s IDefaultDict("test")
252s d = IDefaultDict(int)
252s self.assertEqual(d["test"], 0)
252s self.assertEqual(d["test"], 0)
252s expected_repr = "IDefaultDict(%r, [(IStr('test'), 0)])" % int
252s >   self.assertEqual(repr(d), expected_repr)
252s E   AssertionError: "IDefaultDict(, {IStr('test'): 
0})" != "IDefaultDict(, [(IStr('test'), 0)])"

252s E   - IDefaultDict(, {IStr('test'): 0})
252s E   ? ^^  ^
252s E   + IDefaultDict(, [(IStr('test'), 0)])
252s E   ? ^^^  ^^
252s
252s tests/test_itypes.py:62: AssertionError
252s  TestItypes.test_idict 
_

252s
252s self = 
252s cls = 
252s
252s def test_idict(self, cls=IDict):
252s d = cls(test=20)
252s d["Test^"] = 10
252s d["TEST~"] += 5
252s self.assertEqual(d["Test"], 20)
252s self.assertEqual(d["TEST~"], 15)
252s self.assertEqual(str(list(d.keys())[1]), "Test^")
252s if cls is IDict:
252s expected_repr = "IDict([(IStr('test'), 20), 
(IStr('Test^'), 15)])"

252s >   self.assertEqual(repr(d), expected_repr)
252s E   AssertionError: "IDict({IStr('test'): 20, 
IStr('Test^'): 15})" != "IDict([(IStr('test'), 20), (IStr('Test^'), 15)])"

252s E   - IDict({IStr('test'): 20, IStr('Test^'): 15})
252s E   ?   ^^  ^   ^
252s E   + IDict([(IStr('test'), 20), (IStr('Test^'), 15)])
252s E   ?   ^^^   +  + ^   ^^
252s
252s tests/test_itypes.py:52: AssertionError
252s === warnings summary 
===

252s tests/test_accounts.py::TestAccountTracker::test_account_known
252s   /tmp/autopkgtest.2RAiQ9/autopkgtest_tmp/tests/tests.py:90: 
DeprecationWarning: There is no current event loop

252s loop = asyncio.get_event_loop()
252s
252s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
252s === short test summary info 

252s FAILED tests/test_itypes.py::TestItypes::test_idefaultdict - 
AssertionError: ...
252s FAILED tests/test_itypes.py::TestItypes::test_idict - 
AssertionError: "IDict(...
252s === 2 failed, 34 passed, 1 warning in 0.43s 

--- End Message ---
--- Begin Message ---
Version: 0.6.2-2+rm

Dear submitter,

as the package pyrcb2 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/1064640

The version of this package that was in Debian prior to this removal
can still be found using https://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 

Bug#1058431: marked as done (pyrcb2: FTBFS: with self.assertRaises(TypeError):)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 18:42:39 +
with message-id 
and subject line Bug#1064640: Removed package(s) from unstable
has caused the Debian Bug report #1058431,
regarding pyrcb2: FTBFS: with self.assertRaises(TypeError):
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.)


-- 
1058431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyrcb2
Version: 0.6.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd docs && \
> PYTHONPATH=/<> http_proxy='http://127.0.0.1:9/' 
> https_proxy='https://127.0.0.1:9/' \
> sphinx-build -N -E -T -b html . /<>/.pybuild/docs/html/
> Running Sphinx v7.2.6
> WARNING: Invalid configuration value found: 'language = None'. Update your 
> configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable 
> due to : 
> HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
> with url: /3/objects.inv (Caused by ProxyError('Cannot connect to proxy.', 
> NewConnectionError(' 0x7f19e1867e50>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 16 source files that are out of date
> updating environment: [new config] 16 added, 0 changed, 0 removed
> reading sources... [  6%] custom-commands
> reading sources... [ 12%] getting-started
> reading sources... [ 19%] index
> reading sources... [ 25%] installation
> reading sources... [ 31%] reference/bots
> reading sources... [ 38%] reference/index
> reading sources... [ 44%] reference/itypes
> reading sources... [ 50%] reference/messages
> reading sources... [ 56%] reference/other
> reading sources... [ 62%] release-notes/0.1
> reading sources... [ 69%] release-notes/0.2
> reading sources... [ 75%] release-notes/0.3
> reading sources... [ 81%] release-notes/0.4
> reading sources... [ 88%] release-notes/0.5
> reading sources... [ 94%] release-notes/0.6
> reading sources... [100%] release-notes/index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> writing output... [  6%] custom-commands
> writing output... [ 12%] getting-started
> writing output... [ 19%] index
> writing output... [ 25%] installation
> writing output... [ 31%] reference/bots
> writing output... [ 38%] reference/index
> writing output... [ 44%] reference/itypes
> writing output... [ 50%] reference/messages
> writing output... [ 56%] reference/other
> writing output... [ 62%] release-notes/0.1
> writing output... [ 69%] release-notes/0.2
> writing output... [ 75%] release-notes/0.3
> writing output... [ 81%] release-notes/0.4
> writing output... [ 88%] release-notes/0.5
> writing output... [ 94%] release-notes/0.6
> writing output... [100%] release-notes/index
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 2 warnings.
> 
> The HTML pages are in ../.pybuild/docs/html.
> rm -rf /<>/.pybuild/docs/html/.doctrees
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_pyrcb2/build; 
> python3.12 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 36 items
> 
> tests/test_accounts.py . [ 
> 69%]
> tests/test_itypes.py F...F.. 
> [100%]
> 
> === FAILURES 
> ===
> _ TestItypes.test_idefaultdict 
> 

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1059223 https://github.com/mesonbuild/meson/issues/12877
Bug #1059223 [src:meson] src:meson: fails to migrate to testing for too long: 
fails autopkgtest on arm64 and i386
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/12877'.
> thanks
Stopping processing here.

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

Bug#1061502: marked as done (virtaal: Please drop Build-Depends python3-libproxy)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 18:33:08 +
with message-id 
and subject line Bug#1064180: Removed package(s) from unstable
has caused the Debian Bug report #1061502,
regarding virtaal: Please drop Build-Depends python3-libproxy
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.)


-- 
1061502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virtaal
Version: 0.7.1+git20191021+ds1-2
Severity: serious
Tags: ftbfs sid trixie

virtaal Build-Depends on python3-libproxy, but this dependency is not
required for the build.

libproxy 0.5 no longer provides Python 3 bindings. Because it is
expected that Debian 13 will ship with libproxy 0.5, I am dropping the
python3-libproxy package now.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 0.7.1+git20191021+ds1-2+rm

Dear submitter,

as the package virtaal 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/1064180

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1030008: marked as done (virtaal: Should not be included in bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 18:33:08 +
with message-id 
and subject line Bug#1064180: Removed package(s) from unstable
has caused the Debian Bug report #1030008,
regarding virtaal: Should not be included 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.)


-- 
1030008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtaal
Version: 0.7.1+git20191021+ds1-2
Severity: serious
Justification: Not in a fit state for bookworm
X-Debbugs-Cc: stu...@debian.org

Changes within gtk or its python bindings have left bookworm in a
non-working state. Upstream activity is very limited and there is little
prospect of the package being fixed in time for bookworm.

This bug is to allow autoremovals to remove virtaal from bookworm and
can be closed with the upload of a new upstream release that gets it back
into shape.
--- End Message ---
--- Begin Message ---
Version: 0.7.1+git20191021+ds1-2+rm

Dear submitter,

as the package virtaal 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/1064180

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1009966: marked as done (libpam-tacplus: CVE-2016-20014)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 18:32:24 +
with message-id 
and subject line Bug#1064106: Removed package(s) from unstable
has caused the Debian Bug report #1009966,
regarding libpam-tacplus: CVE-2016-20014
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.)


-- 
1009966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpam-tacplus
Version: 1.3.8-2.1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.3.8-2+deb10u1
Control: found -1 1.3.8-2

Hi,

The following vulnerability was published for libpam-tacplus.

CVE-2016-20014[0]:
| In pam_tacplus.c in pam_tacplus before 1.4.1, pam_sm_acct_mgmt does
| not zero out the arep data structure.


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-2016-20014
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-20014
[1] 
https://github.com/kravietz/pam_tacplus/commit/e4c00eba70a0f72c4de77b5f072c69708ec2beab

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1.3.8-2.1+rm

Dear submitter,

as the package libpam-tacplus 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/1064106

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1010066: marked as done (prayer: Depends on private functions that are hidden with tidy 5.8)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 18:31:17 +
with message-id 
and subject line Bug#1063872: Removed package(s) from unstable
has caused the Debian Bug report #1010066,
regarding prayer: Depends on private functions that are hidden with tidy 5.8
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.)


-- 
1010066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prayer
Version: 1.3.5-dfsg1-8
Severity: grave
X-Debbugs-CC: holmg...@debian.org
User: tidy-ht...@packages.debian.org
Usertags: tidy5.8

Dear Debian prayer package maintainer,

When preparing the upload of package tidy-html5 v5.8 onto Debian Unstable, I
noticed that your package FTBFS with the new tidy library:


/usr/bin/ld: ../session/session.a(html_secure_tidy.o): in function
`tidy_tree':
./session/html_secure_tidy.c:311: undefined reference to
`prvTidyDiscardElement'
/usr/bin/ld: ./session/html_secure_tidy.c:322: undefined reference to
`prvTidyRemoveAttribute'
/usr/bin/ld: ./session/html_secure_tidy.c:329: undefined reference to
`prvTidyAddAttribute'
collect2: error: ld returned 1 exit status


This is because that your package uses some of Tidy's unexported internal
functions that are explicitly hidden in Tidy 5.8:


/* Foul layering volation: Tidy doesn't export these functions */

extern void prvTidyDiscardElement( TidyDoc doc, TidyNode node);
extern void prvTidyRemoveAttribute( TidyDoc doc, TidyNode node, TidyAttr
attr);
extern void prvTidyAddAttribute( TidyDoc doc, TidyNode node,
 const char *attr, const char *value);



I believe this change is intentional by upstream, and will not be changed in
the forseeable future. Please consider fixing the build by removing the use of
internal Tidy functions. Thanks!

Best,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1.3.5-dfsg1-8+rm

Dear submitter,

as the package prayer 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/1063872

The version of this package that was in Debian prior to this removal
can still be found using https://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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1061208: Please upgrade to llvm-toolchain-17

[Étienne Mollier]

Hi Christian,

Christian Kastner, on 2024-02-26:
> Hi Sebastian,
> 
> writing to you as you bumped the severity to 'serious': could the rT
> please give us an extension on the autoremoval for this particular bug.

If that helps, the autoremoval timer is reset each time the RC
critical bug triggering the autoremoval is updated, e.g. when
reporting an evolution of the situation in a new comment.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Processed: closing 1064841

[Debian Bug Tracking System]

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

> close 1064841 4.2.0-4
Bug #1064841 [src:mpich] mpich: binary-all FTBFS
Marked as fixed in versions mpich/4.2.0-4.
Bug #1064841 [src:mpich] mpich: binary-all FTBFS
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1064854: Breaks tex-common's configuration

[julien . puydt]

Package: context
Version: 2023.05.05.20230730+dfsg-2
Severity: critical

since a few days, I saw a configuration issue with the tex-common
package. (What I don't get is why it actually needs configuration since
I don't see uploads since months.)

I finally found the time to investigate and report. The error message
is:

Setting up tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... 
mtxrun --generate failed. Output has been stored in
/tmp/mtxrun.F4nq0y9x
Please include this file if you report a bug.

where /tmp/mtxrun.* contains a single line:

lua error : startup file: /usr/bin/mtxrun.lua:2438: attempt to assign
to const variable 'i'


The executable /usr/bin/mtxrun.lua is provided by the context package
(which also wasn't updated also since months...)

In /usr/bin/mtxrun.lua, around line 2438 looks like:
 for i,v in next,t do 
  if type(i)=="table" then
   if tables[i] then
i=tables[i]   <- 2438 is that one
   else
i=copy(i,tables)
   end
  end

my guess is the correct value should be put in another variable than
the for-loop index, but I'm pretty clueless about lua, and it did work
at some point... perhaps a new lua version is pickier?

Anyway I'm filing the bug report against context, since uninstalling it
unbreaks things, and setting the gravity level to critical since it
breaks other packages.

Cheers,

J.Puydt

Processed: 4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + emacs-bin-common
Bug #1064851 [emacs-gtk,emacs-nox,emacs-pgtk,emacs-lucid] 4 packages from emacs 
have an undeclared file conflict on /usr/bin/emacsclient.emacs
Added indication that 1064851 affects emacs-bin-common

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

Bug#1064852: incus: missing depends on iproute2

[Helmut Grohne]

Package: incus
Version: 0.6-1
Severity: serious
Justification: missing dependency

After installing incus any "incus *" command (even incus info) just
hangs with no indication what's wrong. journalctl -u incus eventually
reveals:


Feb 26 16:47:45 testvm incusd[685]: Error: exec: "ip": executable file not 
found in $PATH

After installing iproute2, incus starts and incus commands start
working.

Helmut

Bug#1064851: 4 packages from emacs have an undeclared file conflict on /usr/bin/emacsclient.emacs

[Helmut Grohne]

Package: emacs-gtk,emacs-nox,emacs-pgtk,emacs-lucid
Version: 1:29.2+1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + emacs-bin-common

4 packages from emacs have an undeclared file conflict. This may result
in an unpack error from dpkg.

The file /usr/bin/emacsclient.emacs is contained in the packages
 * emacs-bin-common
   * 1:27.1+1-3.1+deb11u1 as present in bullseye
   * 1:27.1+1-3.1+deb11u2 as present in bullseye-security
   * 1:28.2+1-15 as present in bookworm
   * 1:29.1+1-5 as present in trixie
   * 1:29.1+1-5~bpo12+1 as present in bookworm-backports
 * emacs-gtk/1:29.2+1-1 as present in unstable
 * emacs-lucid/1:29.2+1-1 as present in unstable
 * emacs-nox/1:29.2+1-1 as present in unstable
 * emacs-pgtk/1:29.2+1-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1054736: Do we need versiontools in Debian any more?

[Andreas Tille]

Hi Benjamin,

as far as I can see no other package is using versiontools and it seems
orphaned upstream.  Do you think we need this package in Debian or
should we rather ask ftpmaster for removal?

I personally have no specific interest in this package and was just
hunting some Python3.12 related bugs.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1064768: marked as done (tox-delay: FTBFS: AttributeError: 'Version' object has no attribute 'startswith')

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 15:52:53 +
with message-id 
and subject line Bug#1064768: fixed in tox-delay 0.1.4-1
has caused the Debian Bug report #1064768,
regarding tox-delay: FTBFS: AttributeError: 'Version' object has no attribute 
'startswith'
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.)


-- 
1064768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tox-delay
Version: 0.1.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 tests/functional.py -e '/<>/shell/tox-delay'
> Using UTF-8 settings: LC_ALL 'C.utf8' LANGUAGE ''
> Trying to find the absolute path to the python3 Python interpreter
> Apparently there is no need to set PYTHONPATH at all
> Using /tmp/tmpkwu0shca as a temporary directory
> Got a tox-delay feature version Version(value='0.1.2', 
> components=[VersionComponent(num=0, rest=''), VersionComponent(num=1, 
> rest=''), VersionComponent(num=2, rest='')])
> Traceback (most recent call last):
>   File "/<>/tests/functional.py", line 344, in 
> main()
>   File "/<>/tests/functional.py", line 332, in main
> check_tox_delay_features(cfg, tempd)
>   File "/<>/tests/functional.py", line 190, in 
> check_tox_delay_features
> if not tdver.startswith("0.1."):
>
> AttributeError: 'Version' object has no attribute 'startswith'
> make[1]: *** [debian/rules:7: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/tox-delay_0.1.2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=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 mark 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: tox-delay
Source-Version: 0.1.4-1
Done: Peter Pentchev 

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

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated tox-delay 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, 26 Feb 2024 17:32:03 +0200
Source: tox-delay
Architecture: source
Version: 0.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 1064768
Changes:
 tox-delay (0.1.4-1) unstable; urgency=medium
 .
   * Include dpkg's default.mk for completeness.
   * Use dpkg-build-api 1, drop the implied Rules-Requires-Root: no
 declaration.
   * New upstream release:
 - fix the build with feature-check 2.x; thus, add a version to
   the feature-check build dependency. Closes: #1064768
 - add a version (1.x) to the utf8-locale build dependency
 - drop the tox-4-compat patch, implemented upstream in almost
   the same way
 - follow upstream's switch to yearless copyright notices
   * Add a news entry about the deprecation of tox-delay.
Checksums-Sha1:
 9a395a8ec37702a142e068d8f72496974712e83a 2526 tox-delay_0.1.4-1.dsc
 e9c86aaa1a2f034247c7f54a5432419fe7767c4d 10844 tox-delay_0.1.4.orig.tar.xz
 0fa540ec7d3d6d02e31151ff14ed4a950d2644f9 833 tox-delay_0.1.4.orig.tar.xz.asc
 76378a1766e176580ee4b0e2392921040afe163b 5476 tox-delay_0.1.4-1.debian.tar.xz
Checksums-Sha256:
 

Bug#1064845: fcitx5-keyman build depends on cruft libkmnkbp-dev

[Adrian Bunk]

Source: fcitx5-keyman
Version: 1.0.7-1
Severity: serious
Tags: ftbfs

libkmnkbp-dev is no longer built by src:keyman

Bug#1064160: marked as done (pngcrush FTBFS with libpng 1.6.42)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 14:43:26 +
with message-id 
and subject line Bug#1064160: fixed in pngcrush 1.8.13-1
has caused the Debian Bug report #1064160,
regarding pngcrush FTBFS with libpng 1.6.42
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.)


-- 
1064160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pngcrush
Version: 1.8.13-0.1
Severity: serious
Tags: ftbfs trixie sid
Forwarded: https://sourceforge.net/p/pmt/bugs/82/

https://buildd.debian.org/status/fetch.php?pkg=pngcrush=riscv64=1.8.13-0.1%2Bb1=1708198996=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pngcrush.html

...
pngcrush.c: In function ‘main’:
pngcrush.c:5515:46: error: ‘PNG_IGNORE_ADLER32’ undeclared (first use in this 
function)
 5515 | png_set_option(read_ptr, PNG_IGNORE_ADLER32,
  |  ^~
pngcrush.c:5515:46: note: each undeclared identifier is reported only once for 
each function it appears in
make[2]: *** [Makefile:55: pngcrush.o] Error 1
--- End Message ---
--- Begin Message ---
Source: pngcrush
Source-Version: 1.8.13-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pngcrush 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, 26 Feb 2024 14:50:14 +0100
Source: pngcrush
Architecture: source
Version: 1.8.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Andreas Tille 
Closes: 832958 850927 928797 947765 953528 964021 1064160
Changes:
 pngcrush (1.8.13-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Bump debhelper from deprecated 9 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Update standards version to 4.6.0, no changes needed.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Also use triplet-prefixed gcc as LD.
 Closes: #850927
   * Mark pngcrush Multi-Arch: foreign.
 Closes: #928797
 .
   [ Andreas Tille ]
   * Move packaging to Debian Phototools team
   * Do not build unused Adler32 code
 Closes: #1064160
   * Standards-Version: 4.6.2 (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * watch file standard 4 (routine-update)
   * Remove bit_depth option from manpage since it was removed inside
 the code
 Closes: #832958, #964021
   * Recreate manpage using help2man to get current options of the binary
 Closes: #947765
   * Verify that options -q and -s are properly mentioned in recreated
 manpage
 Closes: #953528
Checksums-Sha1:
 0212caba66f052b1a79374eb6491728513f84b45 2057 pngcrush_1.8.13-1.dsc
 eb6ea13a303f24035edbc346593b6dce97a2b04d 10560 pngcrush_1.8.13-1.debian.tar.xz
 f5abbfeeacc43f1902a344f84e6a75f876132d0a 6964 pngcrush_1.8.13-1_amd64.buildinfo
Checksums-Sha256:
 5ed4bdf459f0bfdd942a22b926366977fad1f8412b33bc97356017a818be405c 2057 
pngcrush_1.8.13-1.dsc
 e44befa16ffe0243db4606ba12e2872a25100292dda9fb7adc4c706f5706b7ac 10560 
pngcrush_1.8.13-1.debian.tar.xz
 2aceb6921ef970072bdc345d34bd0569f2e87965c449f8df95116225ac847dba 6964 
pngcrush_1.8.13-1_amd64.buildinfo
Files:
 c6b59f6d32ec8c15561e90c89272ca4b 2057 graphics optional pngcrush_1.8.13-1.dsc
 b2f130b641feda6976d7a7b0ce36fcc8 10560 graphics optional 
pngcrush_1.8.13-1.debian.tar.xz
 ead0d21a61b7de97adc6cc36b3fdd391 6964 graphics optional 
pngcrush_1.8.13-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXcmY4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGjoA/+NWCeqJgrbV3sVF9WHRytMJsDSqlbDuI6
7Nmb3mJ6A7lSCNhqRAouDJeJEa3KsHM+FSKLVAaHGAsrDbSWgeFji/tOf7FI2U8n
AnQX568CjJtySna8iwYB7Irb+N0+DJh/41ind/utOGCkTzYikWmbL90BbXGD45u2
k7/yFEiYElIqIgO6EPua+xwWb7SVzWx3oMUnOyOp9zVVcr4hqI9mTz+6cedYiQRE
JhvHXYx5x5gGbreJanjDYXerhUeyUj0ujfjSDrdjjU4wD1b8Rvm2YGH0+wL5y8FF

Bug#1064841: mpich: binary-all FTBFS

[Adrian Bunk]

Source: mpich
Version: 4.2.0-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alastair McKinstry 

https://buildd.debian.org/status/fetch.php?pkg=mpich=all=4.2.0-3=1708957279=0

...
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libmpich-dev (10), libmpich12 (6), mpich (7), mpich-doc 
(591)
 * dh_installdocs: libmpich-dev (0), libmpich12 (0), mpich (0), 
mpich-doc (3)
 * dh_installexamples: libmpich-dev (0), libmpich12 (0), mpich (0), 
mpich-doc (28)
 * dh_installman: libmpich-dev (0), libmpich12 (0), mpich (3), 
mpich-doc (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.

Remember to be careful with paths containing "x86_64-linux-gnu", where 
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:100: binary-indep] Error 255




BTW:
When you do an upload to fix this, could you include the one-line
#1032008 upload for ppc64?

Bug#1064838: New package names break APT safety features, ability to co-install different ABIs

[Bastian Blank]

Control: reassign -1 tech-ctte
Control: severity -1 normal

On Mon, Feb 26, 2024 at 02:20:41PM +0100, Julian Andres Klode wrote:
> In addition, this means that the ABI changes within the same package
> names, causing different ABIs to no longer be co-installable, which can
> have drastic effect on thef function of systems:

This is documented.  Unstable and experimental don't need hand holding.

> - modules will fail to load until you reboot

Yes.  That's why I wanted to rename the ABI of the kernel away from the
package name.

> - modules needed to reboot will fail to load until you reboot (if any)

Please provide an example.  Sorry.

Bastian

-- 
The man on tops walks a lonely street; the "chain" of command is often a noose.

Processed: Re: Bug#1064838: New package names break APT safety features, ability to co-install different ABIs

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 tech-ctte
Bug #1064838 [src:linux] New package names break APT safety features, ability 
to co-install different ABIs
Bug reassigned from package 'src:linux' to 'tech-ctte'.
Ignoring request to alter found versions of bug #1064838 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1064838 to the same values 
previously set
> severity -1 normal
Bug #1064838 [tech-ctte] New package names break APT safety features, ability 
to co-install different ABIs
Severity set to 'normal' from 'serious'

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

Processed: Debian bugs #1064734 , #1062369

[Debian Bug Tracking System]

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

> tags 1062369 + pending
Bug #1062369 [src:libhx] libhx: NMU diff for 64-bit time_t transition
Ignoring request to alter tags of bug #1062369 to the same tags previously set
> tags 1064734 + pending
Bug #1064734 [src:libhx] Please include upstream patch
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#1064838: New package names break APT safety features, ability to co-install different ABIs

[Julian Andres Klode]

On Mon, Feb 26, 2024 at 02:20:41PM +0100, Julian Andres Klode wrote:
> Source: linux
> Severity: serious
> X-Debbugs-Cc: j...@debian.org
> 
> After we had discussed the new proposal a couple months ago and were
> left with severe open questions and concerns it seems that these have
> been ignored and the packages uploaded anyway, breaking APT's algorithm
> that ensures the currently booted kernel is not offered for removal, as
> well as possibly others.
> 
> In addition, this means that the ABI changes within the same package
> names, causing different ABIs to no longer be co-installable, which can
> have drastic effect on thef function of systems:
> 
> - modules will fail to load until you reboot
> - modules needed to reboot will fail to load until you reboot (if any)
> 
> I do not believe fucking up our users for convenience of the maintainers
> and lacking of tools on the ftpmaster side to automatically approve new
> ABI renames is the right call here.
> 
> As such if this change is not reverted, I intend to reassign this to
> the technical committee for deliberation.

This is a followup to the discussion in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040901

which we discussed all this in October all these concerns were already
raised in, and lots of open questions remained that we were nowhere near
ready to do this even if we all agreed that was the right move.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1064838: New package names break APT safety features, ability to co-install different ABIs

[Julian Andres Klode]

Source: linux
Severity: serious
X-Debbugs-Cc: j...@debian.org

After we had discussed the new proposal a couple months ago and were
left with severe open questions and concerns it seems that these have
been ignored and the packages uploaded anyway, breaking APT's algorithm
that ensures the currently booted kernel is not offered for removal, as
well as possibly others.

In addition, this means that the ABI changes within the same package
names, causing different ABIs to no longer be co-installable, which can
have drastic effect on thef function of systems:

- modules will fail to load until you reboot
- modules needed to reboot will fail to load until you reboot (if any)

I do not believe fucking up our users for convenience of the maintainers
and lacking of tools on the ftpmaster side to automatically approve new
ABI renames is the right call here.

As such if this change is not reverted, I intend to reassign this to
the technical committee for deliberation.

-- System Information:
Debian Release: trixie/sid
  APT prefers noble
  APT policy: (500, 'noble'), (500, 'mantic-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1010152: marked as done (emacs-gtk: tries to read a config file from another user's home dir)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 15:16:21 +0200
with message-id <878r37z7q2@iki.fi>
and subject line Close another long-fixed bug
has caused the Debian Bug report #1010152,
regarding emacs-gtk: tries to read a config file from another user's home dir
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.)


-- 
1010152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-gtk
Version: 1:27.1+1-3.1+b1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

After wondering why Emacs was hanging on startup after a reinstallation
of machines with Debian 11 at my lab, I looked at the strace output
(strace -o str.out -f /usr/bin/emacs-gtk -Q) and could see:

[...]
380295 openat(AT_FDCWD, "/usr/share/X11/POSIX/app-defaults/Emacs", O_RDONLY) = 
-1 ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/share/X11/POSIX/app-defaults/Emacs", O_RDONLY) = 
-1 ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/share/X11/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/share/X11/POSIX/app-defaults/Emacs", O_RDONLY) = 
-1 ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/share/X11/POSIX/app-defaults/Emacs", O_RDONLY) = 
-1 ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/share/X11/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/lib/X11/POSIX/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/lib/X11/POSIX/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/lib/X11/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/lib/X11/POSIX/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/lib/X11/POSIX/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/usr/lib/X11/app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/home/vlefevre/.app-defaults/POSIX/Emacs", O_RDONLY) = 
-1 ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/home/vlefevre/.app-defaults/Emacs", O_RDONLY) = -1 
ENOENT (No such file or directory)
380295 openat(AT_FDCWD, "/home/vlefevrePOSIX/Emacs", O_RDONLY) = -1 ENOENT (No 
such file or directory)
380295 openat(AT_FDCWD, "/home/vlefevreEmacs", O_RDONLY) = -1 ENOENT (No such 
file or directory)
[...]

So, Emacs tries to open /home/vlefevrePOSIX/Emacs and
/home/vlefevreEmacs, which potentially belong to other users!

Moreover, here, this makes Emacs hang for several dozens of seconds
possibly due to a timeout in the automounter or something like that.

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

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

Versions of packages emacs-gtk depends on:
ii  emacs-bin-common 1:27.1+1-3.1+b1
ii  emacs-common 1:27.1+1-3.1
ii  libacl1  2.3.1-1
ii  libasound2   1.2.6.1-2+b1
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.14.0-1
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.11.1+dfsg-1
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libgif7  5.1.9-2.1
ii  libglib2.0-0 2.72.1-1
ii  libgmp10 2:6.2.1+dfsg-3
ii  libgnutls30  3.7.4-2
ii  libgpm2  1.20.7-10
ii  libgtk-3-0   3.24.33-1
ii  libharfbuzz0b2.7.4-1+b1
ii  libice6  2:1.0.10-1
ii  libjansson4  2.14-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  liblcms2-2   2.12~rc1-2
ii  libm17n-01.8.0-4
ii  libotf1  0.9.16-3
ii  libpango-1.0-0   1.50.6+ds-2
ii  libpng16-16  1.6.37-4
ii  librsvg2-2   2.52.5+dfsg-3+b1
ii  libselinux1  3.3-1+b2
ii  libsm6   2:1.2.3-1
ii  libsystemd0  250.4-1
ii  libtiff5 

Bug#969971: marked as done (emacs: Installation of packages from GNU ELPA fails due to incorrect handling of TLS1.3)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 15:10:27 +0200
with message-id <87edczz7zw@iki.fi>
and subject line Close the bug
has caused the Debian Bug report #956712,
regarding emacs: Installation of packages from GNU ELPA fails due to incorrect 
handling of TLS1.3
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.)


-- 
956712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs
Version: 1:26.1+1-3.2+deb10u1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

This bug seems related to #942413, but a different bug.
After updating emacs-gtk to 1:26.1+1-3.2+deb10u1, installing packages
from GNU ELPA still fails even if verifying by GnuPG succeeds.

It seems that TLS1.3 handling is broken before 26.3[1].

I can workaround by setting:
(setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")
in ~/.emacs.d/init.el, but I believe this should be handled by package.

This issue can be fixed by:
1. add above setq in system-wide init file
2. backport patch in C code,
but I prefer option 2.

Steps to reproduce:

1. Invoke `emacs` with attached init.el
2. `M-x list-packages` gives following error:
error in process sentinel: Error retrieving: 
https://elpa.gnu.org/packages/archive-contents "incomprehensible buffer" [2 
times]
3. eval `(setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")`
4. `M-x list-packages` works properly

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34341

Best regards,
- -- 
Ryo Igarashi, Ph.D.
rigar...@gmail.com

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

Kernel: Linux 4.19.104-microsoft-standard (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages emacs depends on:
ii  emacs-gtk  1:26.1+1-3.2+deb10u1

emacs recommends no packages.

emacs suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQSQVQWnJ6dEuIxNmESAtgFFC/hXNwUCX1jnzhMccmlnYXJhc2hA
Z21haWwuY29tAAoJEIC2AUUL+Fc3wL0A/jRiGtslRjCy6AVNDtlLrTI52ofMhBJf
JLegBhXizedsAQDlqR4yP+k1p7hy4j65iIFUPzQCcY097+fM0bqDCEPQDw==
=pzFi
-END PGP SIGNATURE-
(setq package-archives
  '(("gnu" . "https://elpa.gnu.org/packages/;)))
;;(setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")
--- End Message ---
--- Begin Message ---
Version: 1:26.3+1-2

According to the bug log this was fixed in 2020, but the bug wasn't
closed for reasons that are unclear. Close it now.

-- 
Arto Jantunen--- End Message ---

Bug#956712: marked as done (emacs: https to plain http downgrade after unhandled GNUTLS_E_AGAIN error in TLS1.3 connection)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 15:10:27 +0200
with message-id <87edczz7zw@iki.fi>
and subject line Close the bug
has caused the Debian Bug report #956712,
regarding emacs: https to plain http downgrade after unhandled GNUTLS_E_AGAIN 
error in TLS1.3 connection
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.)


-- 
956712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs
Version: 1:26.1+1-3.2+deb10u1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

When I have tried to install a package from the GNU ELPA repository, I
received a "Bad Request" error. Searching on the Internet for a solution
of this problem led me to this bugreport at debbugs.gnu.org:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34341

I have confirmed, that the bug reported there can be reproduced in my
emacs installation, and that the workaround mentioned there (disabling
TLS1.3) works.

But while playing around with this bug I noticed, that for some reason
after breaking the TLS1.3 connection it makes second connection with
plain http to the port 443 (sic!).

 Steps to reproduce:

1) Run emacs
2) Open scratchpad with "C-x b *scratch*"
3) Write the following snippet and execute it by positioning cursor
after the
last ")" and pressing C-j.
```
(switch-to-buffer (url-retrieve-synchronously "https://duckduckgo.com;)
  (buffer-string))
```

 Results:

A new buffer with following content is opened:
```
HTTP/1.1 400 Bad Request
Server: nginx
Date: Fri, 02 Apr 2020 12:54:12 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 248
Connection: close
X-XSS-Protection: 1;mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: origin
Expect-CT: max-age=0


400 The plain HTTP request was sent to HTTPS
port

400 Bad Request
The plain HTTP request was sent to HTTPS port
nginx


#
```

Also if network traffic was captured with Wireshark, it can be seen,
that breaking of the TLS1.3 connection follows with a plain http request
to port 443 on the same IP address. And the result of this http request
is returned by the url-retrieve-synchronously function.

The same behaviour is seen in network captures of (failing) emacs
package installation process.

Althogh the bug mentioned in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34341 seems to be
currently fixed in upstream emacs 26.3 and 27.1, the related patch fixes
wrong handling of GNUTLS_E_AGAIN error, but not this fallback from https
to plain http. It suggests, that this behaviour may be triggered by
other exceptions.

Heenec



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

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

Versions of packages emacs depends on:
ii  emacs-gtk  1:26.1+1-3.2+deb10u1

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:26.3+1-2

According to the bug log this was fixed in 2020, but the bug wasn't
closed for reasons that are unclear. Close it now.

-- 
Arto Jantunen--- End Message ---

Bug#1025078: closing 1025078

[Jérôme Charaoui]

close 1025078 5.0.3-1
thanks

With now both ruby-faraday and ruby-puppet-forge up to date in sid, this issue
is solved.

Processed: closing 1025078

[Debian Bug Tracking System]

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

> close 1025078 5.0.3-1
Bug #1025078 [ruby-puppet-forge] ruby-puppet-forge breaks after updating 
ruby-faraday to new upstream
Marked as fixed in versions ruby-puppet-forge/5.0.3-1.
Bug #1025078 [ruby-puppet-forge] ruby-puppet-forge breaks after updating 
ruby-faraday to new upstream
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1010170: marked as done (FTBFS: lisp/net/tramp-archive-tests.log contains unexpected results)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 15:07:34 +0200
with message-id <87il2bz84p@iki.fi>
and subject line Close the bug
has caused the Debian Bug report #1010170,
regarding FTBFS: lisp/net/tramp-archive-tests.log contains unexpected results
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.)


-- 
1010170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs
Version: 1:27.1+1-3.1
Severity: serious
Tags: ftbfs

When rebuilding emacs:

SUMMARY OF TEST RESULTS
---
Files examined: 267
Ran 3883 tests, 3832 results as expected, 1 unexpected, 50 skipped
1 files contained unexpected results:
  lisp/net/tramp-archive-tests.log
make[4]: *** [Makefile:320: check-doit] Error 1
make[4]: Leaving directory 
'/home/vlefevre/tmp/emacs-27.1+1/debian/build-lucid/test'
make[3]: *** [Makefile:289: check] Error 2
make[3]: Leaving directory 
'/home/vlefevre/tmp/emacs-27.1+1/debian/build-lucid/test'
make[2]: *** [Makefile:960: check] Error 2
make[2]: Leaving directory '/home/vlefevre/tmp/emacs-27.1+1/debian/build-lucid'
make[1]: *** [debian/rules:341: override_dh_auto_test] Error 2
make[1]: Leaving directory '/home/vlefevre/tmp/emacs-27.1+1'
make: *** [debian/rules:204: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -b failed

The failed test in lisp/net/tramp-archive-tests.log:

Test tramp-archive-test02-file-name-dissect condition:
(ert-test-failed
 ((should
   (string-equal host
 (url-hexify-string ...)))
  :form
  (string-equal 
"file%3A%2F%2F%2Fhome%2Fvlefevre%2Ftmp%2Femacs-27.1%252B1%2Fdebian%2Fbuild-src%2Ftest%2Flisp%2Fnet%2Ftramp-archive-resources%2Ffoo.tar.gz"
 
"file%3A%2F%2F%2Fhome%2Fvlefevre%2Ftmp%2Femacs-27.1%2B1%2Fdebian%2Fbuild-src%2Ftest%2Flisp%2Fnet%2Ftramp-archive-resources%2Ffoo.tar.gz")
  :value nil))
   FAILED  3/8  tramp-archive-test02-file-name-dissect (0.031675 sec)

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

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Version: 1:28.2+1-6

According to an earlier message in the bug log this was fixed by version
1:28.2+1-6 in 2022.

-- 
Arto Jantunen--- End Message ---

Bug#1059436: lxappearance bug still there.

[Franklin McCormick]

I am running Trixie in a VM.  Seg fault after opening. Says it can't
parse "parentrelative" in an Openbox theme.
There is no reference to any theme which might make tracking don the
problem a lot
easier.


-- 
Frank McCormick in Montreal

Processed: Re: Bug#1064704: gtk4: FTBFS: one run of gtk:tools / validate test failed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #1064704 [src:gtk4] gtk4: FTBFS: one run of gtk:tools / validate test failed
Added tag(s) confirmed.

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

Bug#1064704: gtk4: FTBFS: one run of gtk:tools / validate test failed

[Simon McVittie]

Control: tags -1 + confirmed

Context for Mesa maintainers: gtk4 passed its build-time tests on
2024-01-29, but is now failing in a test rebuild. I can reproduce this,
and I think it's a regression triggered by Mesa changes (see also
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10293 upstream).

On Sun, 25 Feb 2024 at 20:37:28 +0100, Lucas Nussbaum wrote:
> > 1332/1515 gtk:tools / validate  
> > FAIL
> > 2.07s   0/9 subtests passed
> > >>> GDK_BACKEND=x11 G_ENABLE_DIAGNOSTIC=0 
> > >>> GTK_QUERY_SETTINGS=/<>/debian/build/deb/tools/gtk4-query-settings
> > >>>  MALLOC_PERTURB_=208 
> > >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
> > >>> GTK_A11Y=test GDK_DEBUG=default-settings GTK_CSD=1 
> > >>> GTK_BUILDER_TOOL=/<>/debian/build/deb/tools/gtk4-builder-tool
> > >>>  GSETTINGS_SCHEMA_DIR=/<>/debian/build/deb/gtk 
> > >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> > >>>  
> > >>> TEST_RESULT_DIR=/<>/debian/build/deb/testsuite/tools/output
> > >>>  GSETTINGS_BACKEND=memory 
> > >>> G_TEST_BUILDDIR=/<>/debian/build/deb/testsuite/tools 
> > >>> G_TEST_SRCDIR=/<>/testsuite/tools TEST_OUTPUT_SUBDIR=x11 
> > >>> /usr/bin/bash validate

Unfortunately, the only log output for this was:

1..9
not ok 1 invalid1
not ok 2 invalid2
not ok 3 invalid3
not ok 4 invalid4
not ok 5 invalid5
not ok 6 valid1
not ok 7 valid2
not ok 8 valid3
not ok 9 valid4

I notice that many tests have this stderr output:

> MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
> libEGL warning: egl: failed to create dri2 screen
> MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
> glx: failed to create drisw screen
> failed to load driver: zink

Looking at the implementation of the testsuite/tools/validate test,
the way it works is: run GTK's validator against a valid or invalid
input, compare the resulting stderr with what was expected, and fail if
they differ. I think the reason why it's failing is that it's seeing this
extra stderr from Zink.

Obviously, this is quite fragile, because anything that emits a diagnostic
message can break it; but I also don't see any way for GTK upstream to get
the behaviour they want ("assert that the validator produces the messages
that we think it should") without that fragility.

Could this output to stderr in Zink perhaps be reconsidered upstream?

smcv

Bug#1064650: Bug#1052429: fixed in snapd-glib 1.63-5.1

[Bo YU]

Hi,
On Sun, Feb 25, 2024 at 06:23:33PM +0100, Paul Gevers wrote:

Control: clone -1 -2
Control: retitle -2 FTBFS on mips64el, ppc64el and s390x
Control: reopen -2


I followed the wiki[0] to update the symbols and has tested it on
mips64el,ppc64el,and s390x even arm64 and i386 also with qemu user mode.
so if someone can upload it with the debdiff?

BR,
Bo

[0]: https://www.eyrie.org/~eagle/journal/2012-01/008.html


Paul





--
Regards,
--
  Bo YU

diff -Nru snapd-glib-1.63/debian/changelog snapd-glib-1.63/debian/changelog
--- snapd-glib-1.63/debian/changelog2024-01-08 16:11:01.0 +0800
+++ snapd-glib-1.63/debian/changelog2024-02-25 22:58:46.0 +0800
@@ -1,3 +1,11 @@
+snapd-glib (1.63-5.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update libsnapd-qt-2-1.symbols again to fix ftbfs on mips64el,
+ppc64el, s390x. (Closes: #-1)
+
+ -- Bo YU   Sun, 25 Feb 2024 22:58:46 +0800
+
 snapd-glib (1.63-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols 
snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols
--- snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols  2024-01-08 
16:10:23.0 +0800
+++ snapd-glib-1.63/debian/libsnapd-qt-2-1.symbols  2024-02-25 
20:59:53.0 +0800
@@ -888,8 +888,8 @@
  (optional=templinst)_ZN5QHashI7QString8QVariantED2Ev@Base 1.58
  
(optional=templinst)_ZN5QListI18QSnapdMarkdownNodeE18detach_helper_growEii@Base 
1.58
  (optional=templinst)_ZN5QListI18QSnapdMarkdownNodeE6appendERKS0_@Base 1.58
-#MISSING: 1.63-1# 
(optional=templinst|arch=amd64)_ZN5QListI18QSnapdMarkdownNodeED1Ev@Base 1.58
-#MISSING: 1.63-1# 
(optional=templinst|arch=amd64)_ZN5QListI18QSnapdMarkdownNodeED2Ev@Base 1.58
+ (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa i386 ia64 m68k 
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN5QListI18QSnapdMarkdownNodeED1Ev@Base 1.63
+ (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa i386 ia64 m68k 
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN5QListI18QSnapdMarkdownNodeED2Ev@Base 1.63
  (optional=templinst)_ZN5QListI7QStringE18detach_helper_growEii@Base 1.58
  (optional=templinst)_ZN5QListI7QStringE6appendERKS0_@Base 1.58
  (optional=templinst)_ZN5QListI7QStringEC1ERKS1_@Base 1.58
@@ -901,8 +901,8 @@
  (optional=templinst)_ZN5QListI8QVariantE6appendERKS0_@Base 1.58
  (optional=templinst)_ZN5QListI8QVariantED1Ev@Base 1.58
  (optional=templinst)_ZN5QListI8QVariantED2Ev@Base 1.58
- (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !m68k !mips64el 
!powerpc !ppc64 !ppc64el !s390x !sh4 !sparc64 !x32)_ZN7QStringC1ERKS_@Base 1.63
- (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !m68k !mips64el 
!powerpc !ppc64 !ppc64el !s390x !sh4 !sparc64 !x32)_ZN7QStringC2ERKS_@Base 1.63
+ (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !sh4 !sparc64 
!x32)_ZN7QStringC1ERKS_@Base 1.63
+ (arch=!alpha !amd64 !arm64 !armel !armhf !hppa !i386 !ia64 !sh4 !sparc64 
!x32)_ZN7QStringC2ERKS_@Base 1.63
  _ZN7QStringD1Ev@Base 1.58
  _ZN7QStringD2Ev@Base 1.58
  (optional=templinst)_ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 
1.58


signature.asc
Description: PGP signature

Processed: retitle 1064681 to retroarch: FTBFS: glslang is disabled and forced to build with SPIRV-Cross support.

[Debian Bug Tracking System]

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

> retitle 1064681 retroarch: FTBFS: glslang is disabled and forced to build 
> with SPIRV-Cross support.
Bug #1064681 [src:retroarch] retroarch: FTBFS: make[1]: *** [debian/rules:48: 
override_dh_auto_configure] Error 1
Changed Bug title to 'retroarch: FTBFS: glslang is disabled and forced to build 
with SPIRV-Cross support.' from 'retroarch: FTBFS: make[1]: *** 
[debian/rules:48: override_dh_auto_configure] Error 1'.
> thanks
Stopping processing here.

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

Processed: retitle 1064766 to gir-rust-code-generator: FTBFS: failed to select a version for the requirement `toml = "^0.7"`; candidate versions found which didn't match: 0.8.8

[Debian Bug Tracking System]

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

> retitle 1064766 gir-rust-code-generator: FTBFS: failed to select a version 
> for the requirement `toml = "^0.7"`; candidate versions found which didn't 
> match: 0.8.8
Bug #1064766 [src:gir-rust-code-generator] gir-rust-code-generator: FTBFS: 
dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
Changed Bug title to 'gir-rust-code-generator: FTBFS: failed to select a 
version for the requirement `toml = "^0.7"`; candidate versions found which 
didn't match: 0.8.8' from 'gir-rust-code-generator: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo build returned exit code 101'.
> thanks
Stopping processing here.

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

Bug#1064223: marked as done (imbalanced-learn: fails tests with sklearn 1.4: needs new versions)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 11:49:58 +
with message-id 
and subject line Bug#1064223: fixed in imbalanced-learn 0.12.0-1
has caused the Debian Bug report #1064223,
regarding imbalanced-learn: fails tests with sklearn 1.4: needs new versions
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.)


-- 
1064223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imbalanced-learn
Version: 0.10.0-2
Severity: serious
Justification: debci

imbalanced-learn 0.10 fails tests with sklearn 1.4.

The problem is fixed upstrema with v0.12.
--- End Message ---
--- Begin Message ---
Source: imbalanced-learn
Source-Version: 0.12.0-1
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated imbalanced-learn 
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, 26 Feb 2024 12:34:42 +0100
Source: imbalanced-learn
Architecture: source
Version: 0.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 1064223
Changes:
 imbalanced-learn (0.12.0-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * New upstream version
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
 .
   [ Michael R. Crusoe ]
   * Add patch to adapt error messages. Closes: #1064223
   * d/tests/python: run for all supported Python versions.
Checksums-Sha1:
 d14d48905d9e0027b9aa9acb627af09e4a547236 2547 imbalanced-learn_0.12.0-1.dsc
 36e0148d620d271295677898890e7a890ab459ac 380740 
imbalanced-learn_0.12.0.orig.tar.gz
 ca390e48aa738bb2099f4fece9c6150b15746b1e 4752 
imbalanced-learn_0.12.0-1.debian.tar.xz
 421d0cdb6bc091c5cc14a18d15fd992422f7a681 11852 
imbalanced-learn_0.12.0-1_source.buildinfo
Checksums-Sha256:
 c8dff99903e2de064c22e3785688b6019e38c35b78a9c7191422b450483504d8 2547 
imbalanced-learn_0.12.0-1.dsc
 7b198c2606c9ab3eb8231ac14e4ce858bf4ffc0b465bf3f7fabba606de7f89e9 380740 
imbalanced-learn_0.12.0.orig.tar.gz
 37bebc1a45dc42644ccb14ade8f59d6315b089d0ac4c71e74518d3902a7633b3 4752 
imbalanced-learn_0.12.0-1.debian.tar.xz
 a84c0ed7be08a3cd9c98da8723276303e72de7dc4103c91e2f482fb1ba2b15e5 11852 
imbalanced-learn_0.12.0-1_source.buildinfo
Files:
 eaadf0a19fad084f21616ac5cdbafa42 2547 science optional 
imbalanced-learn_0.12.0-1.dsc
 262815e932d727b961b4092fe3fb963a 380740 science optional 
imbalanced-learn_0.12.0.orig.tar.gz
 7aa4861f775c828d99b2b1c179c53cda 4752 science optional 
imbalanced-learn_0.12.0-1.debian.tar.xz
 01688085933f54ceffabba26ceeaa77b 11852 science optional 
imbalanced-learn_0.12.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmXcd5EACgkQPCZ2P2xn
5uIiDRAAirhzNA6lFjc+ajkzR5QM7H7I77A8zJvOTPgQhFAh102usgPDyPTnIr6p
SgaieAmqVCQ07466muKfga3A88Us5Jxa0cCTR91UoScLncLOQkIbtd3kWTi60y0K
WL7v9n5aE75n8de14XMOjOfKQkuvXWqrgTrDX9Va3OLe68+opVtPrnhMcl08FYtk
oUquBInYThcCx87uKngJcImT9xXM/AGH6OkJscehPhRv1Xy3I5FObk8UV9yIyIFx
rGcP9DerDKBtiveqWZz0BttS5ExfMNfpaNVDWvWSgidZF4L8oZlSCRcGJeiE0qnM
3FllpJw2XLgXi5Q95gbCVY7u7HrgSMnukmBdYMmoHIeg4a9LX/VJ+GrElTl+/r3g
bWNoNSBSf5phfDvn4t6NvY6Duz9FIC0Zkl0o4CL3xyfZh7wzWe7UemTrQkR2DBrz
Mhp2MdXZlwYHbBZFTd7MCAlZQWJYC1fCW+/ChUPfSRFEShs6dDpxXpUnX6Ze5Q7l
gHyhlSECfffHIU7BsHRXASCGbN2JKMs+glfI/GFaRojt9+69mmfzd0BXuCZipwEH
ZLMMl5S+KCzdN/PHCans1MOWVWXv7gcqlMQeC41N97ypyjVRoDBaCtRQ0yi4ikV4
MhJ9wq45ejqPwj+sHBUyCfugmJECV/zfOUOoiUlDPr8ep/jSEmM=
=IX/C
-END PGP SIGNATURE-



pgpYOgonVORAL.pgp
Description: PGP signature
--- End Message ---

Processed: Re: pkcs11-provider: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #1064735 [src:pkcs11-provider] pkcs11-provider: FTBFS: dh_auto_test: error: 
make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Added tag(s) unreproducible.
> close -1
Bug #1064735 [src:pkcs11-provider] pkcs11-provider: FTBFS: dh_auto_test: error: 
make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Marked Bug as done

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

Bug#1064735: pkcs11-provider: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Luca Boccassi]

Control: tags -1 unreproducible
Control: close -1

On Sun, 25 Feb 2024 20:44:24 +0100 Lucas Nussbaum 
wrote:
> Source: pkcs11-provider
> Version: 0.3-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240224 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Works fine here in a fresh sid chroot and on the buildds, so it must be
a problem in your custom environment.

-- 
Kind regards,
Luca Boccassi


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

Processed: retitle 1064727 to libsoup2.4: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates

[Debian Bug Tracking System]

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

> retitle 1064727 libsoup2.4: FTBFS: Failed to load TLS database: System trust 
> contains zero trusted certificates
Bug #1064727 {Done: Jeremy Bícha } [src:libsoup2.4] 
libsoup2.4: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test 
returned exit code 29
Changed Bug title to 'libsoup2.4: FTBFS: Failed to load TLS database: System 
trust contains zero trusted certificates' from 'libsoup2.4: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb 
LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 29'.
> thanks
Stopping processing here.

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

Processed: retitle 1064704 to gtk4: FTBFS: one run of gtk:tools / validate test failed

[Debian Bug Tracking System]

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

> retitle 1064704 gtk4: FTBFS: one run of gtk:tools / validate test failed
Bug #1064704 [src:gtk4] gtk4: FTBFS: dh_auto_test: error: cd debian/build/deb 
&& DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test 
--setup=x11 -t 1 --no-suite=failing --no-suite=flaky --no-suite=wayland_failing 
--no-suite=wayland_gles_failing returned exit code 1
Changed Bug title to 'gtk4: FTBFS: one run of gtk:tools / validate test failed' 
from 'gtk4: FTBFS: dh_auto_test: error: cd debian/build/deb && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test 
--setup=x11 -t 1 --no-suite=failing --no-suite=flaky --no-suite=wayland_failing 
--no-suite=wayland_gles_failing returned exit code 1'.
> thanks
Stopping processing here.

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

Bug#1064687: marked as done (folium: FTBFS: LookupError: setuptools-scm was unable to detect version for /<>.)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 11:34:16 +
with message-id 
and subject line Bug#1064687: fixed in folium 0.15.1+dfsg1-2
has caused the Debian Bug report #1064687,
regarding folium: FTBFS: LookupError: setuptools-scm was unable to detect 
version for /<>.
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.)


-- 
1064687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: folium
Version: 0.15.1+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:305: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml 
> does not contain a tool.setuptools_scm section'
> Traceback (most recent call last):
>   File "/<>/setup.py", line 44, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
> setup
> return distutils.core.setup(**attrs)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 147, in setup
> _setup_distribution = dist = klass(attrs)
>  
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 485, in 
> __init__
> _Distribution.__init__(
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 283, in __init__
> self.finalize_options()
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 926, in 
> finalize_options
> ep(self)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 946, in 
> _finalize_setup_keywords
> ep.load()(self, ep.name, value)
>   File 
> "/usr/lib/python3/dist-packages/setuptools_scm/_integration/setuptools.py", 
> line 101, in version_keyword
> _assign_version(dist, config)
>   File 
> "/usr/lib/python3/dist-packages/setuptools_scm/_integration/setuptools.py", 
> line 56, in _assign_version
> _version_missing(config)
>   File "/usr/lib/python3/dist-packages/setuptools_scm/_get_version_impl.py", 
> line 112, in _version_missing
> raise LookupError(
> LookupError: setuptools-scm was unable to detect version for /<>.
> 
> Make sure you're either building from a fully intact git repository or PyPI 
> tarballs. Most other sources (such as GitHub's tarballs, a git checkout 
> without the .git folder) don't contain the necessary metadata and will not 
> work.
> 
> For example, if you're using pip, instead of 
> https://github.com/user/proj/archive/master.zip use 
> git+https://github.com/user/proj.git#egg=proj
> E: pybuild pybuild:391: clean: plugin distutils failed with: exit code=1: 
> python3.11 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned 
> exit code 13
> make[1]: *** [debian/rules:9: override_dh_auto_clean] 

Bug#1064699: marked as done (storm: FTBFS: ModuleNotFoundError: No module named 'six')

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 11:21:07 +
with message-id 
and subject line Bug#1064699: fixed in storm 0.26-2
has caused the Debian Bug report #1064699,
regarding storm: FTBFS: ModuleNotFoundError: No module named 'six'
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.)


-- 
1064699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: storm
Version: 0.26-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for version in $(py3versions -sv); do \
>   PYTHONPATH=/<>/.pybuild/cpython3_${version}_storm/build \
>   python$version dev/test; \
> done
> /<>/dev/test:33: DeprecationWarning: pkg_resources is deprecated 
> as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
>   from pkg_resources import parse_version
> Traceback (most recent call last):
>   File "/<>/dev/test", line 242, in 
> runner_func = with_postgresfixture(runner_func)
>   ^
>   File "/<>/dev/test", line 90, in with_postgresfixture
> from six.moves.urllib.parse import urlunsplit
> ModuleNotFoundError: No module named 'six'
> /<>/dev/test:33: DeprecationWarning: pkg_resources is deprecated 
> as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
>   from pkg_resources import parse_version
> Traceback (most recent call last):
>   File "/<>/dev/test", line 242, in 
> runner_func = with_postgresfixture(runner_func)
>   ^
>   File "/<>/dev/test", line 90, in with_postgresfixture
> from six.moves.urllib.parse import urlunsplit
> ModuleNotFoundError: No module named 'six'
> make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/storm_0.26-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=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 mark 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: storm
Source-Version: 0.26-2
Done: Colin Watson 

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated storm 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, 26 Feb 2024 10:56:13 +
Source: storm
Architecture: source
Version: 0.26-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1064699
Changes:
 storm (0.26-2) unstable; urgency=medium
 .
   * Build-depend on python3-six (closes: #1064699).
Checksums-Sha1:
 5796d2b69de7e62e9d738144ba6829cdbcec5b2c 2584 storm_0.26-2.dsc
 2a105fe3c58634b32797a9b70095992933c10388 11780 storm_0.26-2.debian.tar.xz
Checksums-Sha256:
 9b27deeb59a1da466b51d57364a17f45a55996eae4ad0f3d9a7fbbd450f04b7c 2584 
storm_0.26-2.dsc
 01cfef8ace8e0308f93597cd57d4516f16853d05909e76da6fd36b6e0e9e58ee 11780 
storm_0.26-2.debian.tar.xz
Files:
 73bf161c8293acd874ed82fcabe27289 2584 python optional storm_0.26-2.dsc
 c1e91d9844f80f77e13cda0ded831960 11780 python optional 
storm_0.26-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmXcbnQACgkQOTWH2X2G

Processed: Bug#1064699 marked as pending in storm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064699 [src:storm] storm: FTBFS: ModuleNotFoundError: No module named 
'six'
Added tag(s) pending.

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

Bug#1064699: marked as pending in storm

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1064699 in storm 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/python-team/packages/storm/-/commit/dd61f733d074d13a267f6a0176e5ce9f54c3c202


Build-depend on python3-six

Closes: #1064699


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064699

Bug#1059995: marked as done (pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 09:39:04 +
with message-id 
and subject line Bug#1059995: fixed in pdns 4.8.3-4
has caused the Debian Bug report #1059995,
regarding pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set 
up IPC namespacing: Resource temporarily unavailable
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.)


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

Source: pdns
Version: 4.8.3-2
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. The failures seem related on the host that runs 
the test. ci-worker13 is a beefy machine [1] and test seem to fail 
consistently there, while the other amd64 workers are much more moderate 
[2] and tests pass there.


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

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

Paul

[1] https://metal.equinix.com/product/servers/m3-large/
[2] https://aws.amazon.com/ec2/instance-types/m5/

https://ci.debian.net/packages/p/pdns/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pdns/41325109/log.gz

268s + service pdns restart
269s Job for pdns.service failed because the control process exited with 
error code.
269s See "systemctl status pdns.service" and "journalctl -xeu 
pdns.service" for details.

269s + journalctl _SYSTEMD_UNIT=pdns.service -n 10 --no-pager
269s Dec 25 16:13:20 ci-359-77591125 (s_server)[3766]: pdns.service: 
Failed to set up IPC namespacing: Resource temporarily unavailable
269s Dec 25 16:13:20 ci-359-77591125 (s_server)[3766]: pdns.service: 
Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Resource 
temporarily unavailable
269s Dec 25 16:13:21 ci-359-77591125 (s_server)[3852]: pdns.service: 
Failed to set up IPC namespacing: Resource temporarily unavailable
269s Dec 25 16:13:21 ci-359-77591125 (s_server)[3852]: pdns.service: 
Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Resource 
temporarily unavailable
269s Dec 25 16:13:23 ci-359-77591125 (s_server)[3876]: pdns.service: 
Failed to set up IPC namespacing: Resource temporarily unavailable
269s Dec 25 16:13:23 ci-359-77591125 (s_server)[3876]: pdns.service: 
Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Resource 
temporarily unavailable
269s Dec 25 16:13:24 ci-359-77591125 (s_server)[3886]: pdns.service: 
Failed to set up IPC namespacing: Resource temporarily unavailable
269s Dec 25 16:13:24 ci-359-77591125 (s_server)[3886]: pdns.service: 
Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Resource 
temporarily unavailable
269s Dec 25 16:13:25 ci-359-77591125 (s_server)[3915]: pdns.service: 
Failed to set up IPC namespacing: Resource temporarily unavailable
269s Dec 25 16:13:25 ci-359-77591125 (s_server)[3915]: pdns.service: 
Failed at step NAMESPACE spawning /usr/sbin/pdns_server: Resource 
temporarily unavailable

269s ++ mktemp
269s + TMPFILE=/tmp/tmp.jah1Y5TJIa
269s + trap cleanup EXIT
269s + tee /tmp/tmp.jah1Y5TJIa
269s + sdig 127.0.0.1 53 smoke.pgsql.example.org A
279s Fatal: Timeout waiting for data
279s + grep -c '127\.0\.0\.222' /tmp/tmp.jah1Y5TJIa
279s 0
279s + echo smoke.pgsql.example.org could not be resolved
279s smoke.pgsql.example.org could not be resolved
279s + exit 1
279s + cleanup


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pdns
Source-Version: 4.8.3-4
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated pdns 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 

Bug#1042169: marked as done (python-netaddr: FTBFS: AttributeError: module 'py' has no attribute 'test')

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 09:08:02 +
with message-id 
and subject line Bug#1042169: fixed in python-netaddr 0.10.1-1
has caused the Debian Bug report #1042169,
regarding python-netaddr: FTBFS: AttributeError: module 'py' has no attribute 
'test'
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.)


-- 
1042169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-netaddr
Version: 0.8.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> localehelper LANG=en_US.UTF-8 dh_auto_test -- \
>   --system=custom \
>   --test-args='{interpreter} -c "import py; py.test.cmdline.main()"'
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:240: python3.11 -c "import py; py.test.cmdline.main()"
> Traceback (most recent call last):
>   File "", line 1, in 
> AttributeError: module 'py' has no attribute 'test'
> E: pybuild pybuild:388: test: plugin custom failed with: exit code=1: 
> python3.11 -c "import py; py.test.cmdline.main()"
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
> --system=custom "--test-args={interpreter} -c \"import py; 
> py.test.cmdline.main()\"" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/python-netaddr_0.8.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=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 mark 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: python-netaddr
Source-Version: 0.10.1-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-netaddr 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, 26 Feb 2024 09:30:20 +0100
Source: python-netaddr
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team ,
Changed-By: Thomas Goirand 
Closes: 1042169
Changes:
 python-netaddr (0.10.1-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update lintian override info format in
 d/python-netaddr-docs.lintian-overrides on line 1.
   * Bump debhelper from deprecated 9 to 13.
   * Update renamed lintian tag names in lintian overrides.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Name,
 Repository-Browse.
   * Remove constraints unnecessary since buster (oldstable):
 + Build-Depends: Drop versioned constraint on python3-all.
 .
   [ Thomas Goirand ]
   * Switch debian/watch to mode=git, using github URL.
   * Add myself as uploader.
   * New upstream release.
   * Drop Conflicts+Replaces python-netaddr, as Py2 was removed 2 releases ago.
   * d/rules: fixed the way to run tests (Closes: #1042169).
   * Add fix-pytest.ini.patch to fix coverage.
   * Add autopkgtest.
Checksums-Sha1:
 2dba8fe40655fa37efbfe9674fc4e381bc9263e5 2170 python-netaddr_0.10.1-1.dsc
 5b9dbfb384401c672193c73b94553e808c2e2fff 1493916 
python-netaddr_0.10.1.orig.tar.xz
 47fe130ad19f3e637cc275767078a272f1492f0a 6104 
python-netaddr_0.10.1-1.debian.tar.xz
 

Processed: Bug#1042169 marked as pending in python-netaddr

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042169 [src:python-netaddr] python-netaddr: FTBFS: AttributeError: module 
'py' has no attribute 'test'
Added tag(s) pending.

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

Bug#1042169: marked as pending in python-netaddr

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1042169 in python-netaddr 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/python-team/packages/python-netaddr/-/commit/a20c519b3a59420f997479fb39cdc79fa2c516c2


d/rules: fixed the way to run tests (Closes: #1042169).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042169

Bug#1064816: python-wikkid: FTBFS: ModuleNotFoundError: No module named 'tzlocal'

[Lucas Nussbaum]

Source: python-wikkid
Version: 0.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> FAILED (errors=42, skipped=18)
> E: pybuild pybuild:391: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest 
> discover -v 
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m unittest discover -v 
> test_blockquote 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_blockquote)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_blockquote 
> ... 
> /<>/.pybuild/cpython3_3.11/build/wikkid/tests/formatters/test_markdown.py:31:
>  DeprecationWarning: Only valid in 1.8.1 and earlier. Use skipTest instead.
>   self.skip('markdown formatter not available')
> skipped 'markdown formatter not available'
> test_code 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code ... 
> skipped 'markdown formatter not available'
> test_code_blocks 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code_blocks)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code_blocks 
> ... skipped 'markdown formatter not available'
> test_detailed_headings 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_detailed_headings)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_detailed_headings
>  ... skipped 'markdown formatter not available'
> test_emphasis 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_emphasis)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_emphasis ... 
> skipped 'markdown formatter not available'
> test_hr (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_hr)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_hr ... 
> skipped 'markdown formatter not available'
> test_inline_link 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_inline_link)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_inline_link 
> ... skipped 'markdown formatter not available'
> test_lists 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_lists)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_lists ... 
> skipped 'markdown formatter not available'
> test_reference_link 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_reference_link)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_reference_link
>  ... skipped 'markdown formatter not available'
> test_simple_headings 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_simple_headings)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_simple_headings
>  ... skipped 'markdown formatter not available'
> test_unicode 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_unicode)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_unicode ... 
> skipped 'markdown formatter not available'
> test_default_exists 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_exists)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_exists 
> ... ok
> test_default_missing 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_missing)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_missing
>  ... ok
> test_specify_extra_params 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_params)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_params
>  ... ok
> test_specify_extra_whitespace 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_whitespace)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_whitespace
>  ... ok
> test_specify_missing 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_missing)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_missing
>  ... ok
> test_specify_pygments_case_insensitive 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_pygments_case_insensitive)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_pygments_case_insensitive
>  ... ok
> test_simple_text 
> (wikkid.tests.formatters.test_rest.TestRestructuredTextFormatter.test_simple_text)
> wikkid.tests.formatters.test_rest.TestRestructuredTextFormatter.test_simple_text
>  .

Bug#1064815: python-os-vif: FTBFS: failed test: os_vif.tests.unit.test_objects.TestObjectVersions.test_versions

[Lucas Nussbaum]

Source: python-os-vif
Version: 3.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> ==
> FAIL: os_vif.tests.unit.test_objects.TestObjectVersions.test_versions
> os_vif.tests.unit.test_objects.TestObjectVersions.test_versions
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File "/<>/os_vif/tests/unit/test_objects.py", line 67, in 
> test_versions
> self.assertEqual(expected, actual,
>   File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 395, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 482, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: !=:
> reference = {'FixedIPList': '1.0-15ecf022a68ddbb8c2a6739cfc9f8f5e',
>  'RouteList': '1.0-15ecf022a68ddbb8c2a6739cfc9f8f5e',
>  'SubnetList': '1.0-15ecf022a68ddbb8c2a6739cfc9f8f5e'}
> actual= {'FixedIPList': '1.0-29387c5026a3ac4fe1048d7f4f658bec',
>  'RouteList': '1.0-29387c5026a3ac4fe1048d7f4f658bec',
>  'SubnetList': '1.0-29387c5026a3ac4fe1048d7f4f658bec'}
> : Some objects have changed; please make sure the versions have been bumped, 
> and then update their hashes here.
> 
> 
> --
> Ran 75 tests in 8.453s
> 
> FAILED (failures=1)
> + echo ==> STESTR TEST SUITE FAILED FOR python3.12: displaying pip3 
> freeze output...
> ==> STESTR TEST SUITE FAILED FOR python3.12: displaying pip3 freeze 
> output...
> + [ -x /usr/bin/pip3 ]
> + pip3 freeze
> alabaster==0.7.12
> amqp==5.2.0
> anyjson==0.3.3
> appdirs==1.4.4
> attrs==23.2.0
> autopage==0.4.0
> Babel==2.10.3
> bcrypt==3.2.2
> blinker==1.7.0
> cachetools==5.3.0
> certifi==2023.11.17
> cffi==1.16.0
> chardet==5.2.0
> charset-normalizer==3.3.2
> cliff==4.3.0
> cmd2==2.4.3+ds
> confluent-kafka==1.7.0
> coverage==7.2.7
> cryptography==41.0.7
> debtcollector==2.5.0
> decorator==5.1.1
> deprecation==2.0.7
> dnspython==2.6.1
> docutils==0.20.1
> dogpile.cache==1.1.8
> dulwich==0.21.6
> eventlet==0.0.0
> extras==1.0.0
> fasteners==0.18
> fixtures==4.0.1
> flake8==6.1.0
> futurist==2.4.1
> gevent==23.9.1
> greenlet==3.0.1
> hacking==4.1.0
> idna==3.6
> imagesize==1.4.1
> importlib-metadata==4.12.0
> iso8601==1.0.2
> Jinja2==3.1.2
> jmespath==1.0.1
> jsonpatch==1.32
> jsonpointer==2.3
> keystoneauth1==5.3.0
> kombu==5.3.5
> lxml==5.1.0
> Mako==1.3.2.dev0
> MarkupSafe==2.1.5
> mccabe==0.7.0
> monotonic==1.6
> more-itertools==10.2.0
> msgpack==1.0.3
> netaddr==0.8.0
> netifaces==0.11.0
> oauthlib==3.2.2
> openstackdocstheme==3.2.0
> openstacksdk==1.5.0
> os-client-config==2.1.0
> os-service-types==1.7.0
> oslo.concurrency==5.2.0
> oslo.config==9.2.0
> oslo.context==5.2.0
> oslo.i18n==6.1.0
> oslo.log==5.3.0
> oslo.messaging==14.4.1
> oslo.metrics==0.7.0
> oslo.middleware==5.2.0
> oslo.privsep==3.2.0
> oslo.serialization==5.2.0
> oslo.service==3.2.0
> oslo.utils==6.2.1
> oslo.versionedobjects==3.2.0
> oslosphinx==4.18.0
> oslotest==4.5.0
> ovs==3.3.0
> ovsdbapp==2.4.1
> packaging==23.2
> Paste==3.7.1
> PasteDeploy==3.1.0
> pbr==6.0.0
> ply==3.11
> prettytable==3.6.0
> prometheus-client==0.19.0
> psutil==5.9.8
> py==1.11.0
> pyasyncore==1.0.2
> pycodestyle==2.11.1
> pycparser==2.21
> pyflakes==3.1.0
> Pygments==2.17.2
> pyinotify==0.9.6
> PyJWT==2.7.0
> pyparsing==3.1.1
> pyperclip==1.8.2
> pyroute2==0.7.7
> python-dateutil==2.8.2
> python-subunit==1.4.2
> pytz==2024.1
> PyYAML==6.0.1
> pyzmq==24.0.1
> reno==2.11.2
> repoze.lru==0.7
> requests==2.31.0
> requestsexceptions==1.4.0
> rfc3986==2.0.0
> roman==3.3
> Routes==2.5.1
> six==1.16.0
> snowballstemmer==2.2.0
> sortedcontainers==2.4.0
> Sphinx==7.2.6
> statsd==4.0.1
> stestr==4.1.0
> stevedore==5.1.0
> Tempita==0.5.2
> tenacity==8.2.3
> testscenarios==0.5.0
> testtools==2.7.1
> tomlkit==0.12.3
> urllib3==1.26.18
> vine==5.0.0
> voluptuous==0.14.2
> wcwidth==0.2.5
> WebOb==1.8.6
> wrapt==1.15.0
> yappi==1.4.0
> zipp==1.0.0
> zope.event==5.0
> zope.interface==6.1
> + exit 1
> make[1]: *** [debian/rules:20: override_dh_auto_install] Error 1


The full build 

Bug#1064814: ironic-inspector: FTBFS: AttributeError: 'Flask' object has no attribute 'before_first_request'. Did you mean: '_got_first_request'?

[Lucas Nussbaum]

Source: ironic-inspector
Version: 11.7.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> =
> Failures during discovery
> =
> --- import errors ---
> Failed to import test module: ironic_inspector.test.unit.test_acl
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/ironic_inspector/test/unit/test_acl.py", line 29, in 
> 
> from ironic_inspector import main
>   File "/<>/ironic_inspector/main.py", line 199, in 
> @_app.before_first_request
>  ^
> AttributeError: 'Flask' object has no attribute 'before_first_request'. Did 
> you mean: '_got_first_request'?
> 
> Failed to import test module: ironic_inspector.test.unit.test_main
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/ironic_inspector/test/unit/test_main.py", line 32, 
> in 
> from ironic_inspector import main
>   File "/<>/ironic_inspector/main.py", line 199, in 
> @_app.before_first_request
>  ^
> AttributeError: 'Flask' object has no attribute 'before_first_request'. Did 
> you mean: '_got_first_request'?
> 
> Failed to import test module: ironic_inspector.test.unit.test_wsgi_service
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/ironic_inspector/test/unit/test_wsgi_service.py", 
> line 18, in 
> from ironic_inspector import main
>   File "/<>/ironic_inspector/main.py", line 199, in 
> @_app.before_first_request
>  ^
> AttributeError: 'Flask' object has no attribute 'before_first_request'. Did 
> you mean: '_got_first_request'?
> 
> 
> The above traceback was encountered during test discovery which imports all 
> the found test modules in the specified test_path.
> 
> --
> Ran 0 tests in 4.545s
> 
> OK
> + stestr slowest
> make[1]: *** [debian/rules:34: override_dh_install] Error 3


The full build log is available from:
http://qa-logs.debian.net/2024/02/26/ironic-inspector_11.7.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240226;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240226=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 mark 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.

Bug#1064813: fprintd: FTBFS: (fprintd:160601): fprintd-WARNING **: 06:35:58.406: Could not open "/etc/fprintd.conf": No such file or directory

[Lucas Nussbaum]

Source: fprintd
Version: 1.94.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> ==
> 
> 
> Summary of Failures:
> 
>   8/514 fprintd:daemon+fprintd+FPrintdManagerPreStartTests / 
> FPrintdManagerPreStartTests.test_manager_get_no_default_device
> FAIL 0.57s   
> exit status 1
>   9/514 fprintd:daemon+fprintd+FPrintdManagerPreStartTests / 
> FPrintdManagerPreStartTests.test_manager_get_no_devices   
> FAIL 0.60s   
> exit status 1
> 
> Ok: 512 
> Expected Fail:  0   
> Fail:   2   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb 
> LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test -C 
> /<>/obj-x86_64-linux-gnu --print-errorlogs --timeout-multiplier 
> 5 --no-suite PAM returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/02/26/fprintd_1.94.2-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240226;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240226=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 mark 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.

Bug#1064812: barbican: FTBFS: AttributeError: module 'OpenSSL.crypto' has no attribute 'load_pkcs7_data'

[Lucas Nussbaum]

Source: barbican
Version: 1:17.0.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> ==
> FAIL: 
> barbican.tests.plugin.test_snakeoil_ca.SnakeoilCAPluginTestCase.test_create_ca
> barbican.tests.plugin.test_snakeoil_ca.SnakeoilCAPluginTestCase.test_create_ca
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File "/<>/barbican/tests/plugin/test_snakeoil_ca.py", line 
> 367, in test_create_ca
> pkcs7 = crypto.load_pkcs7_data(crypto.FILETYPE_PEM, intermediates)
> ^^
>   File "/usr/lib/python3/dist-packages/cryptography/utils.py", line 71, in 
> __getattr__
> obj = getattr(self._module, attr)
>   ^^^
> AttributeError: module 'OpenSSL.crypto' has no attribute 'load_pkcs7_data'
> 
> 
> --
> Ran 1506 tests in 52.123s
> 
> FAILED (failures=1, skipped=56)
> + echo ==> STESTR TEST SUITE FAILED FOR python3.12: displaying pip3 
> freeze output...
> ==> STESTR TEST SUITE FAILED FOR python3.12: displaying pip3 freeze 
> output...
> + [ -x /usr/bin/pip3 ]
> + pip3 freeze
> alabaster==0.7.12
> alembic==1.13.1.dev0
> amqp==5.2.0
> anyjson==0.3.3
> appdirs==1.4.4
> attrs==23.2.0
> autopage==0.4.0
> Babel==2.10.3
> bandit==1.6.2
> barbican==17.0.0
> bcrypt==3.2.2
> beautifulsoup4==4.12.3
> blinker==1.7.0
> blockdiag==3.0.0
> cachetools==5.3.0
> cairocffi==1.6.1
> CairoSVG==2.7.1
> castellan==4.3.0
> cbor2==5.6.1
> certifi==2023.11.17
> cffi==1.16.0
> chardet==5.2.0
> charset-normalizer==3.3.2
> cliff==4.3.0
> cmd2==2.4.3+ds
> colorama==0.4.6
> confluent-kafka==1.7.0
> coverage==7.2.7
> cryptography==41.0.7
> cssselect2==0.7.0
> ddt==1.6.0
> debtcollector==2.5.0
> decorator==5.1.1
> defusedxml==0.7.1
> deprecation==2.0.7
> dnspython==2.6.1
> docutils==0.20.1
> dogpile.cache==1.1.8
> dulwich==0.21.6
> editables==0.5
> eventlet==0.0.0
> extras==1.0.0
> falcon==3.1.1
> fasteners==0.18
> fixtures==4.0.1
> flake8==6.1.0
> freetype-py==2.4.0
> funcparserlib==1.0.0
> futurist==2.4.1
> gabbi==2.4.0
> gevent==23.9.1
> gitdb==4.0.11
> GitPython==3.1.37
> greenlet==3.0.1
> hacking==4.1.0
> hatch-vcs==0.4.0
> hatchling==1.21.0
> httplib2==0.20.4
> idna==3.6
> imagesize==1.4.1
> importlib-metadata==4.12.0
> iniconfig==1.1.1
> iso8601==1.0.2
> jaraco.classes==3.2.1
> jeepney==0.8.0
> Jinja2==3.1.2
> jmespath==1.0.1
> jsonpatch==1.32
> jsonpath-rw==1.4.0
> jsonpath-rw-ext==1.2.2
> jsonpointer==2.3
> jsonschema==4.19.2
> jsonschema-specifications==2023.12.1
> keyring==24.3.0
> keystoneauth1==5.3.0
> keystonemiddleware==10.4.1
> kombu==5.3.5
> ldap3==2.9.1
> logutils==0.3.5
> lxml==5.1.0
> Mako==1.3.2.dev0
> MarkupSafe==2.1.5
> mccabe==0.7.0
> microversion-parse==1.0.1
> monotonic==1.6
> more-itertools==10.2.0
> msgpack==1.0.3
> netaddr==0.8.0
> netifaces==0.11.0
> oauthlib==3.2.2
> openstackdocstheme==3.2.0
> openstacksdk==1.5.0
> os-api-ref==2.3.0
> os-client-config==2.1.0
> os-service-types==1.7.0
> os-testr==3.0.0
> oslo.cache==3.5.0
> oslo.concurrency==5.2.0
> oslo.config==9.2.0
> oslo.context==5.2.0
> oslo.db==14.1.0
> oslo.i18n==6.1.0
> oslo.log==5.3.0
> oslo.messaging==14.4.1
> oslo.metrics==0.7.0
> oslo.middleware==5.2.0
> oslo.policy==4.2.1
> oslo.serialization==5.2.0
> oslo.service==3.2.0
> oslo.upgradecheck==2.2.0
> oslo.utils==6.2.1
> oslo.versionedobjects==3.2.0
> oslosphinx==4.18.0
> oslotest==4.5.0
> packaging==23.2
> paramiko==2.12.0
> Paste==3.7.1
> PasteDeploy==3.1.0
> pathspec==0.12.1
> pbr==6.0.0
> pecan==1.4.2
> pep8==1.7.1
> pillow==10.2.0
> pluggy==1.4.0
> ply==3.11
> prettytable==3.6.0
> prometheus-client==0.19.0
> psycopg2==2.9.9
> py==1.11.0
> pyasn1==0.4.8
> pyasyncore==1.0.2
> pycadf==3.1.1
> pycairo==1.25.1
> pycodestyle==2.11.1
> pycparser==2.21
> pyflakes==3.1.0
> Pygments==2.17.2
> pyinotify==0.9.6
> PyJWT==2.7.0
> PyKMIP==0.10.0
> PyMySQL==1.0.2
> PyNaCl==1.5.0
> pyOpenSSL==24.0.0
> pyparsing==3.1.1
> pyperclip==1.8.2
> pytest==7.4.4
> python-barbicanclient==5.6.1
> python-binary-memcached==0.31.1
> python-dateutil==2.8.2
> python-keystonecli

Bug#1064770: marked as done (hugo: FTBFS: make[1]: *** [debian/rules:89: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 08:58:08 +0100
with message-id 
and subject line Re: Bug#1064770: hugo: FTBFS: make[1]: *** [debian/rules:89: 
override_dh_auto_build] Error 25
has caused the Debian Bug report #1064770,
regarding hugo: FTBFS: make[1]: *** [debian/rules:89: override_dh_auto_build] 
Error 25
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.)


-- 
1064770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hugo
Version: 0.122.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> go is /usr/bin/go
> go version go1.21.7 linux/amd64
> dh_auto_build -- -ldflags '-X 
> "github.com/gohugoio/hugo/common/hugo.buildDate=2024-02-04T14:35:47Z" -X 
> "github.com/gohugoio/hugo/common/hugo.vendorInfo=debian:0.122.0-1"' -tags 
> 'dev extended'
>   cd _build && go install -trimpath -v -p 8 -ldflags "-X 
> \"github.com/gohugoio/hugo/common/hugo.buildDate=2024-02-04T14:35:47Z\" -X 
> \"github.com/gohugoio/hugo/common/hugo.vendorInfo=debian:0.122.0-1\"" -tags 
> "dev extended" github.com/gohugoio/hugo github.com/gohugoio/hugo/bufferpool 
> github.com/gohugoio/hugo/cache github.com/gohugoio/hugo/cache/filecache 
> github.com/gohugoio/hugo/cache/namedmemcache github.com/gohugoio/hugo/codegen 
> github.com/gohugoio/hugo/commands github.com/gohugoio/hugo/common 
> github.com/gohugoio/hugo/common/collections 
> github.com/gohugoio/hugo/common/constants 
> github.com/gohugoio/hugo/common/herrors github.com/gohugoio/hugo/common/hexec 
> github.com/gohugoio/hugo/common/hreflect 
> github.com/gohugoio/hugo/common/hstrings 
> github.com/gohugoio/hugo/common/htime github.com/gohugoio/hugo/common/hugio 
> github.com/gohugoio/hugo/common/hugo github.com/gohugoio/hugo/common/loggers 
> github.com/gohugoio/hugo/common/maps github.com/gohugoio/hugo/common/math 
> github.com/gohugoio/hugo/common/para github.com/gohugoio/hugo/common/paths 
> github.com/gohugoio/hugo/common/terminal github.com/gohugoio/hugo/common/text 
> github.com/gohugoio/hugo/common/types 
> github.com/gohugoio/hugo/common/types/css 
> github.com/gohugoio/hugo/common/types/hstring 
> github.com/gohugoio/hugo/common/urls github.com/gohugoio/hugo/compare 
> github.com/gohugoio/hugo/config github.com/gohugoio/hugo/config/allconfig 
> github.com/gohugoio/hugo/config/privacy 
> github.com/gohugoio/hugo/config/security 
> github.com/gohugoio/hugo/config/services 
> github.com/gohugoio/hugo/config/testconfig github.com/gohugoio/hugo/create 
> github.com/gohugoio/hugo/create/skeletons github.com/gohugoio/hugo/deploy 
> github.com/gohugoio/hugo/deps github.com/gohugoio/hugo/docshelper 
> github.com/gohugoio/hugo/helpers github.com/gohugoio/hugo/htesting 
> github.com/gohugoio/hugo/htesting/hqt github.com/gohugoio/hugo/hugofs 
> github.com/gohugoio/hugo/hugofs/files github.com/gohugoio/hugo/hugofs/glob 
> github.com/gohugoio/hugo/hugolib github.com/gohugoio/hugo/hugolib/filesystems 
> github.com/gohugoio/hugo/hugolib/paths github.com/gohugoio/hugo/identity 
> github.com/gohugoio/hugo/langs github.com/gohugoio/hugo/langs/i18n 
> github.com/gohugoio/hugo/lazy github.com/gohugoio/hugo/livereload 
> github.com/gohugoio/hugo/markup github.com/gohugoio/hugo/markup/asciidocext 
> github.com/gohugoio/hugo/markup/asciidocext/asciidocext_config 
> github.com/gohugoio/hugo/markup/asciidocext/internal 
> github.com/gohugoio/hugo/markup/blackfriday 
> github.com/gohugoio/hugo/markup/converter 
> github.com/gohugoio/hugo/markup/converter/hooks 
> github.com/gohugoio/hugo/markup/goldmark 
> github.com/gohugoio/hugo/markup/goldmark/codeblocks 
> github.com/gohugoio/hugo/markup/goldmark/goldmark_config 
> github.com/gohugoio/hugo/markup/goldmark/images 
> github.com/gohugoio/hugo/markup/goldmark/internal/extensions/attributes 
> github.com/gohugoio/hugo/markup/goldmark/internal/render 
> github.com/gohugoio/hugo/markup/goldmark/links 
> github.com/gohugoio/hugo/markup/highlight 
> github.com/gohugoio/hugo/markup/highlight/chromalexers 
> github.com/gohugoio/hugo/markup/internal 
> github.com/gohugoio/hugo/markup/internal/attributes 
> github.com/gohugoio/hugo/markup/markup_config 
> github.com/gohugoio/hugo/markup/org github.com/gohugoio/hugo/markup/pandoc 
> github.com/gohugoio/hugo/markup/rst 
> github.com/gohugoio/hugo/markup/tableofcontents 
> github.com/gohugoio/hugo/media 

Bug#1064691: marked as done (postgresfixture: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 09:00:14 +0100
with message-id 
and subject line Re: Bug#1064691: postgresfixture: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13
has caused the Debian Bug report #1064691,
regarding postgresfixture: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.12 3.11" 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.)


-- 
1064691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresfixture
Version: 0.4.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --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:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> copying postgresfixture/utils.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> copying postgresfixture/clusterfixture.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> copying postgresfixture/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> copying postgresfixture/cluster.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> copying postgresfixture/main.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> copying postgresfixture/__main__.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture
> creating 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_cluster.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_main.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_clusterfixture.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/tests
> creating 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/testing
> copying postgresfixture/testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_postgresfixture/build/postgresfixture/testing
> running egg_info
> creating postgresfixture.egg-info
> writing postgresfixture.egg-info/PKG-INFO
> writing dependency_links to postgresfixture.egg-info/dependency_links.txt
> writing entry points to postgresfixture.egg-info/entry_points.txt
> writing requirements to postgresfixture.egg-info/requires.txt
> writing top-level names to postgresfixture.egg-info/top_level.txt
> writing manifest file 'postgresfixture.egg-info/SOURCES.txt'
> reading manifest file 'postgresfixture.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'postgresfixture.egg-info/SOURCES.txt'
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> copying postgresfixture/utils.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> copying postgresfixture/clusterfixture.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> copying postgresfixture/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> copying postgresfixture/cluster.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> copying postgresfixture/main.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> copying postgresfixture/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture
> creating 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_cluster.py -> 
> /<>/.pybuild/cpython3_3.11_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/__init__.py -> 
> 

Bug#1064690: marked as done (python-django-crispy-forms-foundation: FTBFS: TypeError: AccordionHolder.render() missing 1 required positional argument: 'context')

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 09:01:32 +0100
with message-id 
and subject line Re: Bug#1064690: python-django-crispy-forms-foundation: FTBFS: 
TypeError: AccordionHolder.render() missing 1 required positional argument: 
'context'
has caused the Debian Bug report #1064690,
regarding python-django-crispy-forms-foundation: FTBFS: TypeError: 
AccordionHolder.render() missing 1 required positional argument: 'context'
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.)


-- 
1064690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-crispy-forms-foundation
Version: 0.9.0+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. python3 -m pytest tests -v
> = test session starts 
> ==
> platform linux -- Python 3.11.8, pytest-7.4.4, pluggy-1.4.0 -- 
> /usr/bin/python3
> cachedir: .pytest_cache
> django: settings: sandbox.settings.tests (from ini)
> rootdir: /<>
> configfile: setup.cfg
> plugins: django-4.5.2
> collecting ... collected 15 items
> 
> tests/001_ping_demo.py::test_ping_reverse_urlname[home-url_args0-url_kwargs0] 
> PASSED [  6%]
> tests/001_ping_demo.py::test_ping_reverse_urlname[demo:crispy-demo-form-fieldsets-url_args1-url_kwargs1]
>  FAILED [ 13%]
> tests/001_ping_demo.py::test_ping_reverse_urlname[demo:crispy-demo-form-tabs-url_args2-url_kwargs2]
>  FAILED [ 20%]
> tests/001_ping_demo.py::test_ping_reverse_urlname[demo:crispy-demo-form-accordions-url_args3-url_kwargs3]
>  FAILED [ 26%]
> tests/001_ping_demo.py::test_ping_reverse_urlname[demo:crispy-demo-success-url_args4-url_kwargs4]
>  PASSED [ 33%]
> tests/002_layout.py::test_basic[foundation-6] FAILED [ 
> 40%]
> tests/002_layout.py::test_layout[foundation-6] PASSED[ 
> 46%]
> tests/002_layout.py::test_advanced[foundation-6] PASSED  [ 
> 53%]
> tests/003_fields.py::test_fakefield[foundation-6] FAILED [ 
> 60%]
> tests/003_fields.py::test_inlinefield[foundation-6] FAILED   [ 
> 66%]
> tests/003_fields.py::test_inlineswitchfield[foundation-6] FAILED [ 
> 73%]
> tests/004_buttons.py::test_buttongroup[foundation-6] FAILED  [ 
> 80%]
> tests/004_buttons.py::test_buttonelement[foundation-6] FAILED[ 
> 86%]
> tests/005_containers.py::test_tab[foundation-6] FAILED   [ 
> 93%]
> tests/005_containers.py::test_accordion[foundation-6] FAILED 
> [100%]
> 
> === FAILURES 
> ===
> _ 
> test_ping_reverse_urlname[demo:crispy-demo-form-fieldsets-url_args1-url_kwargs1]
>  _
> 
> client = 
> url_name = 'demo:crispy-demo-form-fieldsets', url_args = []
> url_kwargs = {'foundation_version': 6}
> 
> @pytest.mark.parametrize("url_name,url_args,url_kwargs", [
> ("home", [], {}),
> ("demo:crispy-demo-form-fieldsets", [], {"foundation_version": 6}),
> ("demo:crispy-demo-form-tabs", [], {"foundation_version": 6}),
> ("demo:crispy-demo-form-accordions", [], {"foundation_version": 6}),
> ("demo:crispy-demo-success", [], {"foundation_version": 6}),
> ])
> def test_ping_reverse_urlname(client, url_name, url_args, url_kwargs):
> """
> Ping reversed url names
> """
> >   response = client.get(reverse(url_name, args=url_args, 
> > kwargs=url_kwargs))
> 
> tests/001_ping_demo.py:22: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/django/test/client.py:927: in get
> response = super().get(path, data=data, secure=secure, headers=headers, 
> **extra)
> /usr/lib/python3/dist-packages/django/test/client.py:457: in get
> return self.generic(
> /usr/lib/python3/dist-packages/django/test/client.py:609: in generic
> return self.request(**r)
> /usr/lib/python3/dist-packages/django/test/client.py:891: in request
> self.check_exception(response)
> /usr/lib/python3/dist-packages/django/test/client.py:738: in check_exception
> raise exc_value
> /usr/lib/python3/dist-packages/django/core/handlers/exception.py:55: in inner
> response = get_response(request)
> /usr/lib/python3/dist-packages/django/core/handlers/base.py:220: in 
>