Processed: Bug#1058449 marked as pending in rally

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058449 [src:rally] rally: FTBFS: KeyError: slice(0, -1, None)
Added tag(s) pending.

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

Bug#1058449: marked as pending in rally

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058449 in rally 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/openstack-team/services/rally/-/commit/0813a42d42c964982ac09dba4873c8fc8248fe77


* Blacklist test_add_point_and_get_zipped_graph_2 that isn't working on
Python 3.12 (Closes: #1058449).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058449

Bug#933981: cdrom: USB, KVM create connect/disconnect loop in level1 (repair) install

[Daniel Hedstrom]

On Mon, 05 Aug 2019 14:28:47 -0400 Tom Sullivan  wrote:
> Package: cdrom
> Severity: grave
> Tags: d-i
> Justification: renders package unusable
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I had another machine that gave kernel panic while upgrading from Stretch to
> Buster. Use of Graphical install was also a problem during re-install due to
> destroyed system. (I reported this issue in another report.) Thus, I chose to
> upgrade an identical machine from level 1 (Debain Repair in GRUB2 boot menu).
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> The scrolling log in the command line display showed repeated
> connect/disconnect loops for USB devices (of many kinds). This applied also to
> USB mice and keyboards connected via KVM.
>
> For what it was worth, I used a local cache of the DVDs on the machine's hard
> drive.
>
> Unplugged all USB, plugged in single USB keyboard only, and directly, not via
> KVM.
>
> * What was the outcome of this action?
>
> Upgraded fine with just the keyboard directly plugged into USB.
>
> * What outcome did you expect instead?
>
> Correct handling of USB, without issues.
>
>
>
>
> -- System Information:
> Debian Release: 10.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>

Sent from my iPhone

Processed: python-ase's autopkg tests fail with Python 3.12

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1056457 [src:python-ase] python-ase's autopkg tests fail with Python 3.12
Severity set to 'important' from 'serious'

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

Bug#1056457: python-ase's autopkg tests fail with Python 3.12

[Graham Inggs]

Control: severity -1 important

Hi s3v

Thank you for all the links to the upstream commits.  I have applied
them, and python-ase now builds successfully (closing #1056184).

However, since spglib stopped building its extension for all supported
Python versions (see #1057858) testing python-ase against Python 3.12
now fails with:

531s INTERNALERROR> Traceback (most recent call last):
531s INTERNALERROR>   File
"/usr/lib/python3/dist-packages/spglib/spglib.py", line 41, in

531s INTERNALERROR> from spglib import _spglib as spg
531s INTERNALERROR> ImportError: cannot import name '_spglib' from
partially initialized module 'spglib' (most likely due to a circular
import) (/usr/lib/python3/dist-packages/spglib/__init__.py)

Therefore, I let python-ase only test against the default Python
version [1], and lower the severity of this bug, until either Python
3.12 is the default, or spglib builds its extension for all supported
Python versions again.

Regards
Graham


[1] 
https://salsa.debian.org/debichem-team/python-ase/-/commit/b33055fd68da81e1806e7a0f0dd65dc5b53fc3b2

Processed: Re: flint-arb: FTBFS: /<>/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1058814 [src:flint-arb] flint-arb: FTBFS: 
/<>/fmpz_extras.h:208:1: error: static declaration of 
‘fmpz_ui_pow_ui’ follows non-static declaration
Added tag(s) upstream.
> forwarded -1 https://github.com/fredrik-johansson/arb/issues/454
Bug #1058814 [src:flint-arb] flint-arb: FTBFS: 
/<>/fmpz_extras.h:208:1: error: static declaration of 
‘fmpz_ui_pow_ui’ follows non-static declaration
Set Bug forwarded-to-address to 
'https://github.com/fredrik-johansson/arb/issues/454'.

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

Bug#1058814: flint-arb: FTBFS: /<>/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/fredrik-johansson/arb/issues/454


-- 
http://fam-tille.de

Processed: retitle 1056461 to python3-future: (other packages)'s autopkg tests fail with Python 3.12

[Debian Bug Tracking System]

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

> retitle 1056461 python3-future: (other packages)'s autopkg tests fail with 
> Python 3.12
Bug #1056461 [python3-future] python-canmatrix's autopkg tests fail with Python 
3.12
Changed Bug title to 'python3-future: (other packages)'s autopkg tests fail 
with Python 3.12' from 'python-canmatrix's autopkg tests fail with Python 3.12'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1059663 closed by Thomas Goirand (Cloud not reproduce)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1059663 {Done: Thomas Goirand } [src:python-editor] 
python-editor: autopkgtest failure with Python 3.12
Bug reopened
Ignoring request to alter fixed versions of bug #1059663 to the same values 
previously set

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

Bug#1059663: closed by Thomas Goirand (Cloud not reproduce)

[Graham Inggs]

Control: reopen -1

Still failing with python-editor/1.0.3-5.

On Sun, 7 Jan 2024 at 15:48, Debian Bug Tracking System
 wrote:
> I couldn't reproduce this. There's no autopkgtest in this package, but
> the autopkgtest-pkg-python, which I believe is only doing an import of
> the python module, which worked for me.

Please try with python3-defaults/3.11.6-1 (i.e. with Python 3.12 as a
supported version).

Bug#1000113: kodi: depends on obsolete pcre3 library

[Vasyl Gello]

Hi Yavor,

Thanks for the patch! Greatly appreciated!!!

Upstream we discussed the pcre PR and there is an old branch porting some stuff 
to std::regex.
I have checked that branch but some problems remained.

I can test your patch because I am both the user and the maintainer as you 
requested.

-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Processed: Re: Bug#1000113: kodi: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1000113 [src:kodi] kodi: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#1000113: kodi: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find attached a patch; I did my best to test it.

I believe the changes to the CRegExp class (xbmc/utils/RegExp.*) are
sane; they are tested in xbmc/utils/test/TestRegexp.cpp and some other
test programs that use CRegExp.  I added three more test cases:
invalid pattern, UTF-8 compilation/matching, and JIT.  The latter two
should pass on all the buildds since PCRE2 is built everywhere with
Unicode support, and on those architectures where JIT support is not
available, m_JitSupported will be false so the related functions in
the methods RegComp and PrivateRegFind will not be invoked.
Furthermore, according to the PCRE2 documentation, an application
doesn't need to check explicitly for JIT support because all of the
PCRE2 JIT-related functions have dummy placeholders and silently do
nothing if JIT support is not available.

The changes to CFTPParse (xbmc/filesystem/FTPParse.cpp) are clumsy,
overly verbose code; I'm not proud of it at all.  I tried to minimize
casting as much as possible.  AFAICS it's used only to obtain an ftp
directory contents.  I tried adding some directories from
ftp.gnustep.org as source, but of course there are no media files
there.  Then I installed an FTP server and populated /srv/ftp/ with
some video files.  Kodi displays their properties and plays them, but
I cannot be sure that CFTPParse methods are actually used.  I can't
put breakpoints in gdb as the app runs in fullscreen mode and I don't
know how to switch to normal mode.  (In hindsight, I guess I could
have added some printf statements but it's too late now and the beast
takes nearly 4 hours to build on my machine.)  An unpleasant obstacle
was that Kodi frequently crashes my videocard driver (nouveau) which
made testing very frustrating.

I guess the patch needs more testing and a closer look by someone
familiar with this package (ideally both as a user and maintainer), on
a machine that is capable of running Kodi.

Please let me know if there are problems that require correction.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/1000113
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2024-01-07
---

--- kodi-20.2+dfsg.orig/cmake/modules/FindPCRE.cmake
+++ kodi-20.2+dfsg/cmake/modules/FindPCRE.cmake
@@ -77,45 +77,34 @@
 
 else()
   # Populate paths for find_package_handle_standard_args
-  find_path(PCRE_INCLUDE_DIR pcre.h)
+  find_path(PCRE_INCLUDE_DIR pcre2.h)
 
-  find_library(PCRECPP_LIBRARY_RELEASE NAMES pcrecpp)
-  find_library(PCRECPP_LIBRARY_DEBUG NAMES pcrecppd)
-
-  find_library(PCRE_LIBRARY_RELEASE NAMES pcre)
-  find_library(PCRE_LIBRARY_DEBUG NAMES pcred)
+  find_library(PCRE_LIBRARY_RELEASE NAMES pcre2-8)
 endif()
   else()
 
 if(PKG_CONFIG_FOUND)
-  pkg_check_modules(PC_PCRE libpcrecpp QUIET)
+  pkg_check_modules(PC_PCRE libpcre2-8 QUIET)
 endif()
 
-find_path(PCRE_INCLUDE_DIR pcrecpp.h
+find_path(PCRE_INCLUDE_DIR pcre2.h
PATHS ${PC_PCRE_INCLUDEDIR})
-find_library(PCRECPP_LIBRARY_RELEASE NAMES pcrecpp
- PATHS ${PC_PCRE_LIBDIR})
-find_library(PCRE_LIBRARY_RELEASE NAMES pcre
+find_library(PCRE_LIBRARY_RELEASE NAMES pcre2-8
   PATHS ${PC_PCRE_LIBDIR})
-find_library(PCRECPP_LIBRARY_DEBUG NAMES pcrecppd
-   PATHS ${PC_PCRE_LIBDIR})
-find_library(PCRE_LIBRARY_DEBUG NAMES pcred
-   PATHS ${PC_PCRE_LIBDIR})
 set(PCRE_VERSION ${PC_PCRE_VERSION})
 
   endif()
 
   include(SelectLibraryConfigurations)
-  select_library_configurations(PCRECPP)
   select_library_configurations(PCRE)
 
   include(FindPackageHandleStandardArgs)
   find_package_handle_standard_args(PCRE
-REQUIRED_VARS PCRECPP_LIBRARY PCRE_LIBRARY 
PCRE_INCLUDE_DIR
+REQUIRED_VARS PCRE_LIBRARY PCRE_INCLUDE_DIR
 VERSION_VAR PCRE_VERSION)
 
   if(PCRE_FOUND)
-set(PCRE_LIBRARIES ${PCRECPP_LIBRARY} ${PCRE_LIBRARY})
+set(PCRE_LIBRARIES ${PCRE_LIBRARY})
 set(PCRE_INCLUDE_DIRS ${PCRE_INCLUDE_DIR})
 if(WIN32)
   set(PCRE_DEFINITIONS -DPCRE_STATIC=1)
@@ -166,5 +155,5 @@
 endif()
   endif()
 
-  mark_as_advanced(PCRE_INCLUDE_DIR PCRECPP_LIBRARY PCRE_LIBRARY)
+  mark_as_advanced(PCRE_INCLUDE_DIR PCRE_LIBRARY)
 endif()
--- kodi-20.2+dfsg.orig/xbmc/utils/RegExp.h
+++ kodi-20.2+dfsg/xbmc/utils/RegExp.h
@@ -13,16 +13,8 @@
 #include 
 #include 
 
-/* make sure stdlib.h is included before including pcre.h inside the
-   namespace; this works around stdlib.h definitions also living in
-   the PCRE namespace */
-#include 
-
-namespace PCRE {
-struct real_pcre_jit_stack; // forward declaration for PCRE without JIT
-typedef struct real_pcre_jit_stack pcre_jit_stack;
-#include 
-}
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 
 class CRegExp
 {

Bug#1057056: marked as done (rust-comrak: Unsatisfiable dependency on rust-emojis)

[Debian Bug Tracking System]

Your message dated Mon, 8 Jan 2024 03:11:27 +
with message-id <9ea89636-5ddc-4244-b904-04e30909d...@debian.org>
and subject line rust-comrak: Unsatisfiable dependency on rust-emojis
has caused the Debian Bug report #1057056,
regarding rust-comrak: Unsatisfiable dependency on rust-emojis
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.)


-- 
1057056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-comrak
Version: 0.18.0-1
Severity: serious
X-Debbugs-CC: sylves...@debian.org, aferra...@debian.org

librust-comrak-dev depends on librust-emojis-0.5+default-dev but that
is not packaged in Debian.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---

Version: 0.18.0-2


librust-comrak-dev depends on librust-emojis-0.5+default-dev but that
is not packaged in Debian.


rust-emojis 0.6 was accepted into Debian on 2024-01-06 and version
0.18.0-2 of rust-comrak relaxed the dependency to allow it.--- End Message ---

Processed: Re: Processed (with 1 error): castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el

[Debian Bug Tracking System]

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

> block 1060205 by 1056116
Bug #1060205 [src:castxml] castxml: BD-Uninstallable: castxml build-depends on 
missing: libclang-17-dev:mips64el
1060205 was not blocked by any bugs.
1060205 was not blocking any bugs.
Added blocking bug(s) of 1060205: 1056116
> thank you
Stopping processing here.

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

Bug#1060205: castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el

[Étienne Mollier]

Control: block -1 by #1056116

Hi Sebastian,

> castxml build-depends on missing:
> - libclang-17-dev:mips64el

Thanks for the heads up, I'm afraid this is a bit out of hands
right now.  According to bug entries #1059465 and #1056116,
llvm-toolchain-16 and -17 fail to build on mips64el at the
moment.  Also, the llvm-toolchain-15 is not planned to ship with
trixie if I trust #1058812.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/0, please excuse my verbosity
   `-on air: Apple Pie - Letters Of A Deadman - Part III - …


signature.asc
Description: PGP signature

Bug#1058007: marked as done (python-wsaccel: runtime dependency on cython)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 18:52:03 +
with message-id 
and subject line Bug#1058007: fixed in python-wsaccel 0.6.3-4
has caused the Debian Bug report #1058007,
regarding python-wsaccel: runtime dependency on cython
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.)


-- 
1058007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-wsaccel
Version: 0.6.3-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython-rt-dep

[This bug is targeted to the upcoming trixie release]

The package build-depends on cython3 or cython3-legacy, and one of the
built binary packages also depends on cython3 or cython3-legacy. That
might be correct, but in most cases there is no runtime dependency for
a tool like cython, that is only used when building the package.

Please check that this dependency can be removed. Most likely this
dependency is generated by pybuild, because the setup.py requires
Cython in it's 'install_requires' attribute.  Please remove that,
after checking that it is not a runtime dependency, and also report
that issue upstream for upcoming releases.

If the runtime dependency is necessary, please just close this bug
report.
--- End Message ---
--- Begin Message ---
Source: python-wsaccel
Source-Version: 0.6.3-4
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-wsaccel 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: Sun, 07 Jan 2024 18:43:51 +0100
Source: python-wsaccel
Architecture: source
Version: 0.6.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1058007
Changes:
 python-wsaccel (0.6.3-4) unstable; urgency=medium
 .
   * Do not runtime depends on cython3 (Closes: #1058007).
Checksums-Sha1:
 a1f218a898bd67a267cb49fc3ea29e3223d91fbe 2083 python-wsaccel_0.6.3-4.dsc
 5ab9ce3425ea94862df7a7b327c8523471a07e07 2576 
python-wsaccel_0.6.3-4.debian.tar.xz
 e6d3ff01dab73d684b5f9dd1c238a9c94a3ceb07 8213 
python-wsaccel_0.6.3-4_amd64.buildinfo
Checksums-Sha256:
 20b28b0dd012991b40de0c03fdaaff31432a97e91348d15595db59884a23ce42 2083 
python-wsaccel_0.6.3-4.dsc
 2d4c9a1835043e52bb84a0210796246be447909e12bde74d13b2f97bf1a08ab6 2576 
python-wsaccel_0.6.3-4.debian.tar.xz
 c98f04bd70e95b07592e27f2b5c6c75a5f9f88366d95d7997602ac275938f447 8213 
python-wsaccel_0.6.3-4_amd64.buildinfo
Files:
 75670a03c1e6736d6ca63855983f4e2a 2083 python optional 
python-wsaccel_0.6.3-4.dsc
 0a46c2310b278966d3002d142fca9687 2576 python optional 
python-wsaccel_0.6.3-4.debian.tar.xz
 d28ee5833b38a8210e56bb9460b54c76 8213 python optional 
python-wsaccel_0.6.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmWa48AACgkQ1BatFaxr
Q/7rLA/9FPXWEnDCepHuDVTLuAqOfQ8zANUnYpCFCs/7Yjd32s1HuJ9LAbFYtA+O
i5csGpQ6XL+5wYzI0osJ6vw1N5QJZFjQDLhy8U5xTwWTeyymAU4SRmziFiHSCAfW
+L+7BxSz8kZUqYVfJLAJLgdAUm/1pnBRel/tUau36o5UIdml30P2MMaXNGq6A2RG
kE41HFqULBFAr0YQqqs9rYHcofIDcGT4AB6sR+jNlivu2NL+tT8aqSAhrsQsXpDV
NDqgrbp+IxmozkJA0w32HRO5OBOuLkLYqRBZTO8UyoQD8txPUG6UshdZncIB/3/a
VUgfi9YmjpzSDiRT7KakzpvZcfSoeYuJTwg2Zj3j86rAMmGi0zMBMHtV1v8MqhpL
NzSXuJs0WHkzcL6bEDAMHXZ7S8EGVgyE0VrHZEnkLwm2ZQEyJ9sk1o6ScYRvz0r8
DBdewrVUZW1Zw0JHH+QfDE1F3GfWPFQCvmnxPUxAFnxX1/JJh/NnpFCNNkN81RNy
REct38MipIJ3NrnNBibQYJrrGasTb1ZXNdV/n995DpsNtMhp/mL1aHsDDbswVxrX
2HKmtgVx3EmrE9q9pd4lU5JRzIQh40HixKdznxGOrrMZ6tryf/NzYLnickporhFO
xEntW41eMqO5C/NzgGpZRl3pz2V5amxmG5MroikO6EY6kLtPbpw=
=bWMo
-END PGP SIGNATURE End Message ---

Bug#1058378: marked as done (python-wsgi-intercept: FTBFS: failed tests)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 18:52:11 +
with message-id 
and subject line Bug#1058378: fixed in python-wsgi-intercept 1.9.3-5
has caused the Debian Bug report #1058378,
regarding python-wsgi-intercept: FTBFS: failed tests
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.)


-- 
1058378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wsgi-intercept
Version: 1.9.3-4
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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; set -x ; for i in 3.12 3.11 ; do \
>   PYMAJOR=`echo $i | cut -d'.' -f1` ; \
>   echo "===> Testing with python$i (python$PYMAJOR)" ; \
>   WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=$i PYTHONPATH=. python$i -m 
> pytest wsgi_intercept/tests ; \
> done
> + echo 3.12
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python3.12 (python3)
> ===> Testing with python3.12 (python3)
> + WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=3.12 PYTHONPATH=. python3.12 -m 
> pytest wsgi_intercept/tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 80 items
> 
> wsgi_intercept/tests/test_http_client.py .ss [  
> 8%]
> wsgi_intercept/tests/test_httplib2.py    [ 
> 18%]
> wsgi_intercept/tests/test_interceptor.py [ 
> 43%]
> wsgi_intercept/tests/test_module_interceptor.py ..   [ 
> 46%]
> wsgi_intercept/tests/test_requests.py .FFsF.ss   [ 
> 61%]
> wsgi_intercept/tests/test_response_headers.py .. [ 
> 63%]
> wsgi_intercept/tests/test_urllib.py ...ss[ 
> 75%]
> wsgi_intercept/tests/test_urllib3.py .FFF.ss [ 
> 88%]
> wsgi_intercept/tests/test_wsgi_compliance.py .   
> [100%]
> 
> === FAILURES 
> ===
> __ test_https 
> __
> 
> def test_https():
> with InstalledApp(wsgi_app.simple_app, host=HOST, port=443) as app:
> >   resp = 
> > requests.get('https://some_hopefully_nonexistant_domain:443/')
> 
> wsgi_intercept/tests/test_requests.py:57: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/requests/api.py:73: in get
> return request("get", url, params=params, **kwargs)
> /usr/lib/python3/dist-packages/requests/api.py:59: in request
> return session.request(method=method, url=url, **kwargs)
> /usr/lib/python3/dist-packages/requests/sessions.py:589: in request
> resp = self.send(prep, **send_kwargs)
> /usr/lib/python3/dist-packages/requests/sessions.py:703: in send
> r = adapter.send(request, **kwargs)
> /usr/lib/python3/dist-packages/requests/adapters.py:486: in send
> resp = conn.urlopen(
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:705: in urlopen
> conn = self._get_conn(timeout=pool_timeout)
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:300: in _get_conn
> return conn or self._new_conn()
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:1038: in _new_conn
> conn = self.ConnectionCls(
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> .HTTPS_WSGIInterceptor 
> object at 0x7f9ae3b7a6c0>
> args = ()
> kwargs = {'cert_file': None, 'host': 'some_hopefully_nonexistant_domain', 
> 'key_file': None, 'port': 443, ...}
> 
> def __init__(self, *args, **kwargs):
> if 'strict' in kwargs and sys.version_info > (3, 0):
> kwargs.pop('strict')
> kwargs.pop('socket_options', None)
> kwargs.pop('key_password', None)
> kwargs.pop('server_hostname', None)
> >   WSGI_HTTPSConnection.__init__(self, *args, **kwargs)
> E   TypeError: HTTPSConnection.__init__() got an unexpected keyword 
> argument 'cert_file'
> 
> wsgi_intercept/_urllib3.py:33: TypeError
> __ test_https_no_ssl_verification_intercepted 
> 

Bug#1058162: marked as done (manila: FTBFS: KeyError: slice(1, None, None))

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 18:27:10 +
with message-id 
and subject line Bug#1058162: fixed in manila 1:17.1.0-1
has caused the Debian Bug report #1058162,
regarding manila: FTBFS: KeyError: slice(1, None, None)
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.)


-- 
1058162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: manila
Version: 1:17.0.0-1
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):
> ==
> FAIL: 
> manila.tests.share.test_migration.ShareMigrationHelperTestCase.test_wait_for_share_server_3_creating
> manila.tests.share.test_migration.ShareMigrationHelperTestCase.test_wait_for_share_server_3_creating
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sqlalchemy/engine/row.py", line 131, 
> in _get_by_key_impl
> rec = self._keymap[key]
>   ^
> KeyError: slice(1, None, None)
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/manila/tests/share/test_migration.py", line 40, in 
> setUp
> self.share = db_utils.create_share()
>  ^^^
>   File "/<>/manila/tests/db_utils.py", line 99, in create_share
> return _create_db_row(db.share_create, share, kwargs)
>^^
>   File "/<>/manila/tests/db_utils.py", line 32, in _create_db_row
> return method(context.get_admin_context(), default_values)
>^^^
>   File "/<>/manila/db/api.py", line 386, in share_create
> return IMPL.share_create(context, share_values,
>
>   File "/<>/manila/db/sqlalchemy/api.py", line 172, in wrapper
> return f(*args, **kwargs)
>^^
>   File "/<>/manila/db/sqlalchemy/api.py", line 2246, in 
> share_create
> _share_instance_create(context, share_ref['id'],
>   File "/<>/manila/db/sqlalchemy/api.py", line 1637, in 
> _share_instance_create
> return share_instance_get(context, share_instance_ref['id'],
>^
>   File "/<>/manila/db/sqlalchemy/api.py", line 172, in wrapper
> return f(*args, **kwargs)
>^^
>   File "/<>/manila/db/sqlalchemy/api.py", line 1739, in 
> share_instance_get
> ).first()
>   ^^^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2824, 
> in first
> return self.limit(1)._iter().first()
>^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/engine/result.py", line 
> 1498, in first
> return self._only_one_row(
>^^^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/engine/result.py", line 
> 559, in _only_one_row
> row = onerow(hard_close=True)
>   ^^^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/engine/result.py", line 
> 1386, in _fetchone_impl
> return self._real_result._fetchone_impl(hard_close=hard_close)
>^^^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/engine/result.py", line 
> 1801, in _fetchone_impl
> row = next(self.iterator, _NO_ROW)
>   
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/loading.py", line 151, 
> in chunks
> rows = [proc(row) for row in fetch]
> ^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/loading.py", line 1019, 
> in _instance
> to_load = _populate_partial(
>   ^^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/loading.py", line 1189, 
> in _populate_partial
> populator(state, dict_, row)
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/strategies.py", line 
> 1893, in load_scalar_from_subq
> collection = collections.get(tuple_getter(row), (None,))
>  ^^^
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/strategies.py", line 
> 1600, in get
>   

Bug#1058007: marked as pending in python-wsaccel

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058007 in python-wsaccel 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/openstack-team/python/python-wsaccel/-/commit/95655ef1e81f06309191615738498ef216ebbc05


Do not runtime depends on cython3 (Closes: #1058007).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058007

Bug#1060005: cifs-utils: Copy file with cp, hangs with a kernel NULL pointer dereference.

[JD Walsh]

Package: src:linux
Version: 6.1.69-1
Followup-For: Bug #1060005

Dear Maintainer,

I'm running Debian 12 6.1.0-17, having recently upgraded from 6.1.0-16.

On my machine, running cp on a file on my NAS causes the computer to hang for a
few seconds before reporting "Killed". The cifs share becomes non-responsive
afterward, requiring a reboot. I can reproduce it every time by choosing
specific files. The problem does not occur if I boot with kernel 6.1.0-16 or
earlier. Changing the SMB
version does not appear to make a difference. I tried SMB 2.1, 3.0, 3.1, and
3.1.1.

Other command line file operations cause similar issues. Running rm on the NAS
sometimes returns without error, but without removing the file. Other times, rm
hangs and the NAS becomes non-responsive.

Once the NAS is non-responsive, umount reports it as busy unless the -l flag is
used.

In a GUI file manager like Konquerer or Dolphin, attempting to copy causes the
file manager to hang. Rebooting requires Debian to disconnect the non-
responsive NAS and kill the still-pending cp or rm file process underlying the
GUI command. Using a GUI application to perform "Save As" appears to be fine.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1303
board_vendor: ASUSTeK COMPUTER INC.
board_name: ROG MAXIMUS Z790 HERO
board_version: Rev 1.xx

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:a700] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8882]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:06.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port 
[8086:a74d] (rev 01) (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. Raptor Lake PCIe 4.0 Graphics Port 
[1043:8882]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:0a.0 Signal processing controller [1180]: Intel Corporation Raptor Lake 
Crashlog and Telemetry [8086:a77d] (rev 01)
Subsystem: ASUSTeK Computer Inc. Raptor Lake Crashlog and Telemetry 
[1043:8882]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_vsec
Kernel modules: intel_vsec

00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device 
NVMe RAID Controller Intel Corporation [8086:a77f]
DeviceName: RAID Controller
Subsystem: ASUSTeK Computer Inc. Volume Management Device NVMe RAID 
Controller Intel Corporation [1043:8882]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: vmd
Kernel modules: vmd

00:14.0 USB controller [0c03]: Intel Corporation Device [8086:7a60] (rev 11) 
(prog-if 30 [XHCI])
DeviceName: USB Controller
Subsystem: ASUSTeK Computer Inc. Device [1043:8882]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: mei_me, xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Device [8086:7a27] (rev 11)
Subsystem: ASUSTeK Computer Inc. Device [1043:8882]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:14.3 Network controller [0280]: Intel Corporation Device [8086:7a70] (rev 11)
Subsystem: Intel Corporation Device [8086:0094]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

00:15.0 Serial bus controller 

Processed: Bug#1058007 marked as pending in python-wsaccel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058007 [src:python-wsaccel] python-wsaccel: runtime dependency on cython
Added tag(s) pending.

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

Processed: Bug#1058378 marked as pending in python-wsgi-intercept

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058378 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: failed 
tests
Ignoring request to alter tags of bug #1058378 to the same tags previously set

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

Bug#1058378: marked as pending in python-wsgi-intercept

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058378 in python-wsgi-intercept 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/openstack-team/python/python-wsgi-intercept/-/commit/039da06619d89d494f3d85801e092933306b4ac6


Add Support_Python_3.12.patch (Closes: #1058378).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058378

Bug#1052800: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[s3v]

Control: forwarded -1 https://github.com/davidhalter/parso/issues/222
thanks

Dear Maintainer,

After adding:

  export PYBUILD_BEFORE_TEST=cp conftest.py {build_dir}

in debian/rules, tests pass with Python 3.11 but still fail with
Python 3.12.
I've opened an issue upstream.


...
make[1]: Leaving directory '/build/parso-0.8.3'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild pybuild:310: cp conftest.py 
/build/parso-0.8.3/.pybuild/cpython3_3.12_parso/build
I: pybuild base:305: cd /build/parso-0.8.3/.pybuild/cpython3_3.12_parso/build; 
python3.12 -m pytest test
 test 
session starts 

platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
rootdir: /build/parso-0.8.3/.pybuild/cpython3_3.12_parso/build
configfile: pytest.ini
collected 1348 items
    

test/test_cache.py .
  [  0%]
test/test_diff_parser.py 
..
   [  6%]
test/test_dump_tree.py ..   
  [  7%]
test/test_error_recovery.py .   
  [  8%]
test/test_file_python_errors.py .   
  [  8%]
test/test_fstring.py 
.   
 [ 13%]
test/test_get_code.py . 
  [ 14%]
test/test_grammar.py .  
  [ 14%]
test/test_load_grammar.py ...   
  [ 15%]
test/test_normalizer_issues_files.py .  
  [ 17%]
test/test_old_fast_parser.py ...
  [ 19%]
test/test_param_splitting.py ...
  [ 19%]
test/test_parser.py 
.
 [ 29%]
.   
  [ 30%]
test/test_parser_tree.py 
... 
 [ 35%]
test/test_pep8.py ...   
  [ 36%]
test/test_pgen2.py 
..
 [ 45%]
.
 [ 56%]
test/test_prefix.py ..  
  [ 57%]
test/test_python_errors.py 
...FF.
 [ 66%]
FF..FFF.F.F..
 [ 78%]
.
 [ 87%]
test/test_tokenize.py 
...
 [ 97%]
.   
  [ 97%]
test/test_utils.py ...  
  [100%]

Processed: bug 1059675 is forwarded to https://github.com/tkaitchuck/aHash/issues/152

[Debian Bug Tracking System]

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

> forwarded 1059675 https://github.com/tkaitchuck/aHash/issues/152
Bug #1059675 [rust-ahash] rust-ahash - autopkgtest failure on s390x.
Set Bug forwarded-to-address to 
'https://github.com/tkaitchuck/aHash/issues/152'.
> thanks
Stopping processing here.

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

Processed: Re: parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/davidhalter/parso/issues/222
Bug #1052800 [src:parso] parso: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.11 returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/davidhalter/parso/issues/222'.

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

Bug#1059648: sip4: autopkgtest failure with Python 3.12

[Dmitry Shachnev]

Hi Gregor!

On Sun, Jan 07, 2024 at 03:40:49PM +0100, Gregor Riepl wrote:
> I can reproduce that, although I should mention that the segfault happens
> during teardown, not when the module is loaded:
> 
> >>> import sip
> >>> print(sip)
>  '/usr/lib/python3/dist-packages/sip.cpython-312-x86_64-linux-gnu.so'>
> >>> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00513a8d in PyMem_Free ()
> (gdb) bt
> #0  0x00513a8d in PyMem_Free ()
> #1  0x7f73de6feaf9 in sip_api_free (mem=) at
> ./siplib/siplib.c:2241
> #2  0x7f73de710c6d in sipOMFinalise (om=) at
> ./siplib/objmap.c:69
> #3  0x7f73de6febaf in finalise () at ./siplib/siplib.c:2143
> #4  0x004591ab in ?? ()
> #5  0x00662d77 in Py_RunMain ()
> #6  0x006232eb in Py_BytesMain ()
> #7  0x7f73deba66ca in __libc_start_call_main (main=main@entry=0x623240,
> argc=argc@entry=1, argv=argv@entry=0x7ffd043a59b8) at
> ../sysdeps/nptl/libc_start_call_main.h:58
> #8  0x7f73deba6785 in __libc_start_main_impl (main=0x623240, argc=1,
> argv=0x7ffd043a59b8, init=, fini=,
> rtld_fini=, stack_end=0x7ffd043a59a8)
> at ../csu/libc-start.c:360
> #9  0x00623171 in _start ()

Yes, I saw the same.

In SIP 6, there were 3 commits to add support for Python 3.12, but the code
diverged a lot so it's not trivial to backport them to SIP 4.

> I'd also like to point out that SIP4 is no longer supported upstream. The
> current version is 6.8.1, which is already packaged for Debian.
> https://www.riverbankcomputing.com/software/sip/download
> 
> > SIP v4 is no longer supported. This is the last release.
> > sip-4.19.25.tar.gz
> 
> Cura was made fit for PyQt6 and SIP6 in April 2022, and I think 5.0 has all
> the needed changes. I will investigate if we can drop the dependency on
> python3-sip-dev. As far as I can see, there are no other users of SIP4 in
> Debian, so maybe it can be dropped completely after fixing Cura.

Unfortunately there are other users:

$ reverse-depends src:sip4 -r sid
Reverse-Recommends
==
* krita [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]

Reverse-Depends
===
* gnuradio [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]
* meteo-qt [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]
* python3-pykdl [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]
* python3-python-qt-binding (for python3-sip-dev)
* python3-python-qt-binding (for sip-dev)
* qutebrowser   (for python3-sip)
* tulip [amd64 arm64 i386 mips64el ppc64el s390x]
* vistrails (for python3-sip)

$ reverse-depends -b src:sip4 -r sid
Reverse-Testsuite-Triggers
==
* geophar   (for python3-sip)

Reverse-Build-Depends
=
* ball  (for python3-sip-dev)
* geophar   (for python3-sip)
* guidata   (for python3-sip)
* krita (for python3-sip-dev)
* libarcus  (for python3-sip-dev)
* libsavitar(for python3-sip-dev)
* openstructure (for sip-dev)
* orocos-kdl(for python3-sip-dev)
* pynest2d  (for python3-sip-dev)
* pyqwt3d   (for python3-sip-dev)
* stimfit   (for python3-sip-dev)
* tulip (for python3-sip-dev)

Reverse-Build-Depends-Indep
===
* eric  (for python3-sip-dev)

krita and pyqwt3d have open bugs to move to sip6, but I will need to file
bugs for the other packages too.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1060206: olive-editor: FTBFS: CMake Generate step failed.

[Sebastian Ramacher]

Source: olive-editor
Version: 20230614+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=olive-editor=amd64=20230614%2Bds-1=1704354645=0

-- Configuring done (1.5s)
CMake Error at ext/KDDockWidgets/src/CMakeLists.txt:306 (target_link_libraries):
  Target "kddockwidgets" links to:

Qt5::WidgetsPrivate

  but the target was not found.  Possible reasons include:

* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.



-- Generating done (0.3s)
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
FETCHCONTENT_FULLY_DISCONNECTED


CMake Generate step failed.  Build files cannot be regenerated correctly.

Cheers
-- 
Sebastian Ramacher

Bug#1060205: castxml: BD-Uninstallable: castxml build-depends on missing: libclang-17-dev:mips64el

[Sebastian Ramacher]

Source: castxml
Version: 0.6.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/package.php?p=castxml

Dependency installability problem for castxml on mips64el:

castxml build-depends on missing:
- libclang-17-dev:mips64el


Cheers
-- 
Sebastian Ramacher

Bug#1059648: sip4: autopkgtest failure with Python 3.12

[Gregor Riepl]

Hi Graham,


sip4's autopkgtests fail with Python 3.12 [1].  I've copied what I
hope is the relevant part of the log below.

[1] https://ci.debian.net/packages/s/sip4/testing/amd64/

22s autopkgtest [20:09:51]: test autodep8-python3: [---
22s Testing with python3.12:
22s 
22s bash: line 1: 1865 Segmentation fault $py -c "import sip; print(sip)"
22s autopkgtest [20:09:51]: test autodep8-python3: ---]


I can reproduce that, although I should mention that the segfault 
happens during teardown, not when the module is loaded:


>>> import sip
>>> print(sip)
'/usr/lib/python3/dist-packages/sip.cpython-312-x86_64-linux-gnu.so'>

>>> 

Program received signal SIGSEGV, Segmentation fault.
0x00513a8d in PyMem_Free ()
(gdb) bt
#0  0x00513a8d in PyMem_Free ()
#1  0x7f73de6feaf9 in sip_api_free (mem=) at 
./siplib/siplib.c:2241
#2  0x7f73de710c6d in sipOMFinalise (om=) at 
./siplib/objmap.c:69

#3  0x7f73de6febaf in finalise () at ./siplib/siplib.c:2143
#4  0x004591ab in ?? ()
#5  0x00662d77 in Py_RunMain ()
#6  0x006232eb in Py_BytesMain ()
#7  0x7f73deba66ca in __libc_start_call_main 
(main=main@entry=0x623240, argc=argc@entry=1, 
argv=argv@entry=0x7ffd043a59b8) at ../sysdeps/nptl/libc_start_call_main.h:58
#8  0x7f73deba6785 in __libc_start_main_impl (main=0x623240, argc=1, 
argv=0x7ffd043a59b8, init=, fini=, 
rtld_fini=, stack_end=0x7ffd043a59a8)

at ../csu/libc-start.c:360
#9  0x00623171 in _start ()


I'd also like to point out that SIP4 is no longer supported upstream. 
The current version is 6.8.1, which is already packaged for Debian.

https://www.riverbankcomputing.com/software/sip/download

> SIP v4 is no longer supported. This is the last release.
> sip-4.19.25.tar.gz

Cura was made fit for PyQt6 and SIP6 in April 2022, and I think 5.0 has 
all the needed changes. I will investigate if we can drop the dependency 
on python3-sip-dev. As far as I can see, there are no other users of 
SIP4 in Debian, so maybe it can be dropped completely after fixing Cura.

Bug#1059663: marked as done (python-editor: autopkgtest failure with Python 3.12)

[Debian Bug Tracking System]

Your message dated Sun, 7 Jan 2024 14:44:56 +0100
with message-id <5a58950b-6048-4298-ad14-1e0062cfe...@debian.org>
and subject line Cloud not reproduce
has caused the Debian Bug report #1059663,
regarding python-editor: autopkgtest failure 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.)


-- 
1059663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-editor
Version: 1.0.3-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

python-editor's autopkgtests fail with Python 3.12 [1].  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-editor/testing/amd64/


35s autopkgtest [20:11:13]: test autodep8-python3: [---
36s Testing with python3.12:
36s Traceback (most recent call last):
36s File "", line 1, in 
36s File "/usr/lib/python3/dist-packages/editor.py", line 11, in 
36s from distutils.spawn import find_executable
36s ModuleNotFoundError: No module named 'distutils'
36s autopkgtest [20:11:14]: test autodep8-python3: ---]
--- End Message ---
--- Begin Message ---

Hi,

I couldn't reproduce this. There's no autopkgtest in this package, but 
the autopkgtest-pkg-python, which I believe is only doing an import of 
the python module, which worked for me.


Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Gregor Riepl]

(sorry for the very late response, I only noticed your message just now)

I did come to the conclusion that Werkzeug 2.3.x has some bigger changes 
that will break most of the existing packages in some way. The main 
differences to Werkzeug 3.x than isn't that big.


Ok, that makes sense!

Although, I'm not 100% convinced that updating to 2.3 in the short run 
to fix some currently broken packages, and then focusing on upgrading to 
3.x isn't a better choice. 2.3 is also closer to 3.x, so that may make a 
transition smoother.


Because a updated flask-login and other (updated) packages have also 
underlying changes that require than a updated package of Werkzeug. And 
some upstream projects did change their source in a way so they can deal 
different versions of Werkzeug. So a usual update is magical fixing 
build issues we did have in older versions against recent Flask/Werkzeug 
versions.


Ok, now I get what mean. Thanks for the clarification and sorry for the 
confusion.

Processed: Bug#1058378 marked as pending in python-wsgi-intercept

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058378 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: failed 
tests
Added tag(s) pending.

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

Bug#1058378: marked as pending in python-wsgi-intercept

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058378 in python-wsgi-intercept 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/openstack-team/python/python-wsgi-intercept/-/commit/af7c6810ec7c165b580bc0ac019b1baf8123da4b


Add Support_Python_3.12.patch (Closes: #1058378).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058378

Bug#1050896: marked as done (packagesearch: Incomplete/Misleading copyright file)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 12:34:10 +
with message-id 
and subject line Bug#1050896: fixed in packagesearch 2.8.1
has caused the Debian Bug report #1050896,
regarding packagesearch: Incomplete/Misleading copyright file
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.)


-- 
1050896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: packagesearch
Version: 2.8.0
Severity: serious
X-Debbugs-Cc: j...@debian.org


The copyright file only states that it is licensed under the GPL,
but not which versions. This seems to imply it is licensed under
the GPL version 1.

The code meanwhile ships the GPL-2 in COPYING.

It's unclear whether the code is GPL-3 compatible. I'm not sure
this can be said, as there have been contributors aside from
the maintainer.

My advise would be to contact all the copyright holders, and
make sure that everyone is onboard with this actually being
GPL-2+ such that when dependencies update to GPL-3 or later
versions, you still remain compatible.

I am not sure if this bug can be reasonably solved right now,
maybe the copyright file can be changed to say GPL-2, I'd certainly
also advise using the machine-readable copyright format for it
to make everything clear rather than this half-assed free form.

The problem to consider with updating the copyright file to just
say GPL-2 is whether contributors knew they were contributing to
a GPL-2 codebase or whether they contributed thinking it was GPL-1.

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

Kernel: Linux 6.3.0-7-generic (SMP w/16 CPU threads; PREEMPT)
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
--- End Message ---
--- Begin Message ---
Source: packagesearch
Source-Version: 2.8.1
Done: Benjamin Mesing 

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

Debian distribution maintenance software
pp.
Benjamin Mesing  (supplier of updated packagesearch 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: Sun, 07 Jan 2024 12:45:11 +0100
Source: packagesearch
Architecture: source
Version: 2.8.1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Mesing 
Changed-By: Benjamin Mesing 
Closes: 1050896
Changes:
 packagesearch (2.8.1) unstable; urgency=medium
 .
   * updated copyright to GPL-3
 - removed spanish translation because I could not reach copyright
   holder
   * introduced machine readable copyright file
   * Copyright fixes Closes: #1050896
Checksums-Sha1:
 da6b64d694822f5ae24549188ed6c315f4c7bfe4 1718 packagesearch_2.8.1.dsc
 773dd28f47db085e52e2fe49a80c406f8b7aa366 541176 packagesearch_2.8.1.tar.xz
 1fb4d9cfea86d4e1c8d79ee9bfd480914cc02efe 12278 
packagesearch_2.8.1_amd64.buildinfo
Checksums-Sha256:
 579febaba240745a08ad6fd2d3b4cc74b0d29c98017f90c9810ac2643546788a 1718 
packagesearch_2.8.1.dsc
 39028fa3da7b89f641a40bf8e25de7fd905dbd331e28ff3d6b513201e0e2a403 541176 
packagesearch_2.8.1.tar.xz
 1e3bd51ddf4fb06ab7d00ca8639bfcefe5d1d6215c9f7c6f25eb100f72f4d3b5 12278 
packagesearch_2.8.1_amd64.buildinfo
Files:
 23e947294b3b5e6e1ccda6cf119494da 1718 admin optional packagesearch_2.8.1.dsc
 9242289fc2a56c12667b5276b9d96f24 541176 admin optional 
packagesearch_2.8.1.tar.xz
 361bf1af44a412ed360c8bdb7ab55c01 12278 admin optional 
packagesearch_2.8.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEC01PPdKKuhRlMWxu7WML0v+pQ/EFAmWaltYACgkQ7WML0v+p
Q/FqwQ/+LI6GgXwtt2Xws8YGfriOR+8Z+CrtOTzcMOt/6EB+bT9U1n9V9jPz+sqE
SRNjR0krGiceYvL8NEsIjNsKi8I3noZyWEltOzszpHl61iNWc0qumgpWWNWE5gmm
CGhol/q1IaF7pDeXNgcRR84D1eqzZsuVSVz8GDXAfJqfikNSnuCy6XHjFtuauV3z

Processed: Bug#1058248 marked as pending in python-diskimage-builder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058248 [src:python-diskimage-builder] python-diskimage-builder: FTBFS: 
ModuleNotFoundError: No module named 'imp'
Added tag(s) pending.

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

Bug#1058248: marked as pending in python-diskimage-builder

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058248 in python-diskimage-builder 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/openstack-team/libs/python-diskimage-builder/-/commit/a6c89726a375bd7d2c0f0e508150e679a17bd278


Add stop-using-the-imp-module.patch (Closes: #1058248).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058248

Bug#1058083: Before I try to tackle this bug - can we move the package to DPT

[Ulises Vitulli]

Hey Andreas!

Feel free to go ahead with my blessing right away!


Cheers,

\d

ps: sorry for the delay, summer holidays in this part of the world!

On 1/4/24 03:49, Andreas Tille wrote:

Ping?  If I do not hear from you in the next couple of days I'll move
the package to DPT at beginning of next week.

Kind regards
 Andreas.

Am Mon, Dec 25, 2023 at 08:34:58AM +0100 schrieb Andreas Tille:

Hi Agustin and Ulises,

I noticed there were several NMUs not commited to the Git repository of
this package.  I'd volunteer to bring the repository in sync with latest
uploads and move it to Debian Python Team before I try to tacke bug
#1058083.

Kind regards
 Andreas.

--
http://fam-tille.de

Bug#1060174: marked as done (rust-lscolors FTBFS: error[E0560]: struct `nu_ansi_term::Style` has no field named `prefix_with_reset`)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 11:51:03 +
with message-id 
and subject line Bug#1060174: fixed in rust-lscolors 0.16.0-2
has caused the Debian Bug report #1060174,
regarding rust-lscolors FTBFS: error[E0560]: struct `nu_ansi_term::Style` has 
no field named `prefix_with_reset`
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.)


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

https://buildd.debian.org/status/logs.php?pkg=rust-lscolors=0.16.0-1

...
error[E0560]: struct `nu_ansi_term::Style` has no field named 
`prefix_with_reset`
   --> src/style.rs:464:13
|
464 | prefix_with_reset: false,
| ^ `nu_ansi_term::Style` does not have this 
field
|
= note: available fields are: `foreground`, `background`, `is_bold`, 
`is_dimmed`, `is_italic` ... and 6 others
...
--- End Message ---
--- Begin Message ---
Source: rust-lscolors
Source-Version: 0.16.0-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-lscolors, 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.
Peter Michael Green  (supplier of updated rust-lscolors 
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: Sun, 07 Jan 2024 10:55:51 +
Source: rust-lscolors
Architecture: source
Version: 0.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1060174
Changes:
 rust-lscolors (0.16.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package lscolors 0.16.0 from crates.io using debcargo 2.6.1
   * Drop update-nu-ansi-term.diff, upstream and Debian are now in sync
 (Closes: #1060174)
   * Mark tests for the no features case as broken.
Checksums-Sha1:
 04a735c74c8fb3dd963a14d44338327f8d1d1316 2366 rust-lscolors_0.16.0-2.dsc
 20578594b3cdb3f74575a3edf070e24c984fff54 3672 
rust-lscolors_0.16.0-2.debian.tar.xz
 cc5c8930a3015fbf55eb5f5e97f2e3833bec5935 8984 
rust-lscolors_0.16.0-2_source.buildinfo
Checksums-Sha256:
 ac6986deea12bd37e58fa156a10a7437e5795e65f7df33af1a0bc0eb565750f8 2366 
rust-lscolors_0.16.0-2.dsc
 98a8e8754129a0a7d4d98a25a4dcc74ea6770bde9463deeeb7a3b30c0010171c 3672 
rust-lscolors_0.16.0-2.debian.tar.xz
 4d64cd5b645d912f8a62874be2922268b45dece9cf53ba6cea3466cb2ae3bd84 8984 
rust-lscolors_0.16.0-2_source.buildinfo
Files:
 44bdb3a4a1afae1d08669aded4590f11 2366 rust optional rust-lscolors_0.16.0-2.dsc
 dcfd087ac940cd7153dbc887b6713f5a 3672 rust optional 
rust-lscolors_0.16.0-2.debian.tar.xz
 8787c13cf36c46443855bfd7c7ebe1f8 8984 rust optional 
rust-lscolors_0.16.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmWaiwQUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xs7SA//blMUn5yvz5KnkPqDx2eTfrN75UUj
shEhHY8BLA45VCVXrLJg3GsIz4yg1Q6ntCj33k9VuP1te9NdFv/RZowanpYull/a
Ta9qUSyL4R4WM9GCJRecudetw7OWahzVLhxsJs6aalh3LC7VxHMoDI8F+k7VZ9Qm
qtYt1zMGw9KvpkllsgP/S7G9OELn71TRvVXtvSM0A3uPlR0Z4mr7JIoz1B95t0d9
GQqpANXAnmC+eOdz6WvUbqvjbVJrPVnFo9YTKdkkeZHJnJSn/2HRLqJdv4+/qM/F
W70qHyCihbEAbqLlUZGBBCvjM6Hnx90oH+JQcwabAQITO6f+tMSapGe6m44Q9H54
IFcUeFLyeErQiduj2/z2ThjWx9xV7ZnLKCttjXlSX1qX22DYKC8mS/BuIumyxcEG
zR98XfTC1XTSyTCUO4P1mhfElUMz2X46OYlO4S2kpymf2jq2VyAbGHunvJPCcUzC
XiOP4CA7fzoVHPZ4PGdof8/L82boo2UA74TIoMBdw61HUcc4+8AHgGZlC3fVXLHF
izA/nDoCQuYhvVUvvgn7YUDgTVvTnq47vhjCixfqaZLHmzHWay7txwxmwiWkQFdg
zbUxvzoQucJ4e+0GX3Glv5uiVYImVyAFAQvwEUUqfOpZp0lIudDpUYApW1SruUTo
ghVlywzeOekG7Q0=
=kjEC
-END PGP SIGNATURE End Message ---

Bug#1056184: marked as done (python-ase: FTBFS: ERROR: Broken link: :git:`COPYING`: Non-existing path: ../COPYING)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 11:50:54 +
with message-id 
and subject line Bug#1056184: fixed in python-ase 3.22.1-4
has caused the Debian Bug report #1056184,
regarding python-ase: FTBFS: ERROR: Broken link: :git:`COPYING`: Non-existing 
path: ../COPYING
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.)


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

Source: python-ase
Version: 3.22.1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During an incremental rebuild of all packages in trixie,
this package failed to build:

[...]
/<>/doc/about.rst:51: ERROR: Broken link: :git:`COPYING`: 
Non-existing path: ../COPYING
/<>/doc/about.rst:51: ERROR: Broken link: :git:`COPYING.LESSER`: 
Non-existing path: ../COPYING.LESSER
/<>/doc/ase/ase.rst:49: WARNING: download file not readable: 
/<>/doc/ase/ase-talk.pdf
/<>/doc/ase/calculators/FHI-aims.rst:110: ERROR: Broken link: 
:git:`ase/test/calculator/aims/test_H2O_aims.py`: Non-existing path: 
../ase/test/calculator/aims/test_H2O_aims.py
/<>/doc/ase/calculators/kim.rst:97: ERROR: Broken link: 
:git:`ase.calculators.kim.kim `: Non-existing path: 
../ase/calculators/kim/kim.py
/<>/doc/ase/calculators/kim.rst:97: ERROR: Broken link: 
:git:`ase.calculators.kim.kimmodel `: Non-existing path: 
../ase/calculators/kim/kimmodel.py
/<>/doc/ase/calculators/qmmm.rst:108: ERROR: Broken link: 
:git:`ase/test/forcefields/test_forceqmmm.py`: Non-existing path: 
../ase/test/forcefields/test_forceqmmm.py
/<>/doc/ase/calculators/turbomole.rst:346: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_H2.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_H2.py
/<>/doc/ase/calculators/turbomole.rst:353: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_h3o2m.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_h3o2m.py
/<>/doc/ase/calculators/turbomole.rst:360: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_au13.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_au13.py
/<>/doc/ase/calculators/turbomole.rst:368: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_optimizer.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_optimizer.py
/<>/doc/ase/calculators/turbomole.rst:373: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_h2o.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_h2o.py
/<>/doc/ase/calculators/turbomole.rst:385: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_qmmm.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_qmmm.py
/<>/doc/ase/calculators/turbomole.rst:415: ERROR: Broken link: 
:git:`ase/test/calculator/turbomole/test_turbomole_2h2o.py`: Non-existing path: 
../ase/test/calculator/turbomole/test_turbomole_2h2o.py

Exception occurred:
  File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 108, in 
role
title = caption % part
^~
TypeError: not all arguments converted during string formatting
The full traceback has been saved in /tmp/sphinx-err-ytvbet8_.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[1]: *** [debian/rules:45: override_dh_sphinxdoc] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log available here, where it also fails:

https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/python-ase.html

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-ase
Source-Version: 3.22.1-4
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated python-ase package)

(This message was generated automatically at their request; if you
believe that there is a 

Processed: Bug#1058162 marked as pending in manila

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058162 [src:manila] manila: FTBFS: KeyError: slice(1, None, None)
Added tag(s) pending.

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

Bug#1058162: marked as pending in manila

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058162 in manila 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/openstack-team/services/manila/-/commit/aa910c7db086cd96e8330762d7b50d1ebfc95b0a


The above fixes FTBFS (Closes: #1058162).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058162

Bug#1052844: deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[s3v]

Dear Maintainer,

after adding:

  export PYBUILD_BEFORE_TEST=cp conftest.py {build_dir}

in debian/rules, I was able to build yout package in a sid
chroot environment.

Kind Regards

Bug#1057595: marked as done (publican: FTBFS: Failed 2/10 test programs)

[Debian Bug Tracking System]

Your message dated Sun, 7 Jan 2024 12:26:22 +0100
with message-id 
and subject line Re: Bug#1057595: publican: FTBFS: Failed 2/10 test programs
has caused the Debian Bug report #1057595,
regarding publican: FTBFS: Failed 2/10 test programs
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.)


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

Package: src:publican
Version: 4.3.2-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --with linktree
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
/usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wl,-z,relro"
WARNING: the following files are missing in your kit:
datadir/Common_Content/common-db5/en-US/scripts/highlight.js/LICENSE
po/de-CH.po
Please inform the author.

Created MYMETA.yml and MYMETA.json

[... snipped ...]

--common_content=sOverride path to Common_Content directory
--nocolours   Disable ANSI colourisation of logging.
--quiet   Disable all logging.
--brand_dir=s Directory to source brand files from.


zt_push
Push translations to Zanata.

Options:
--helpDisplay help message
--config=sUse a nonstandard config file
--common_config=s Override path to Common_Config directory
--common_content=sOverride path to Common_Content directory
--nocolours   Disable ANSI colourisation of logging.
--quiet   Disable all logging.
--brand_dir=s Directory to source brand files from.




=head1 CONFIGURATION AND ENVIRONMENT

Publican requires access to wkhtmltopdf or Apache FOP for creating PDF files.

=head1 DEPENDENCIES

Archive::Tar
Archive::Zip
Carp
Config::Simple
Cwd
DBI
DateTime
DateTime::Format::DateParse
Devel::Cover
Encode
File::Basename
File::Copy::Recursive
File::Find
File::Find::Rule
File::HomeDir
File::Inplace
File::Path
File::Spec
File::Which
File::pushd
Getopt::Long
HTML::FormatText
HTML::FormatText::WithLinks
HTML::FormatText::WithLinks::AndTables
HTML::TreeBuilder
I18N::LangTags::List
IO::String
Lingua::EN::Fathom
List::MoreUtils
List::Util
Locale::Language
Locale::Maketext::Gettext
Locale::Maketext::Lexicon
Locale::Msgfmt
Locale::PO
Module::Build
Pod::Usage
Sort::Versions
String::Similarity
Syntax::Highlight::Engine::Kate
Template
Template::Constants
Term::ANSIColor
Test::More
Test::Pod
Test::Pod::Coverage
Text::CSV_XS
Text::Wrap
Time::localtime
XML::LibXML
XML::LibXSLT
XML::Simple
XML::TreeBuilder
version

=head1 INCOMPATIBILITIES

None reported.

=head1 BUGS AND LIMITATIONS

Bug list at 
L.

Please report any bugs or feature requests to
C, or through the web interface at
L.

=head1 AUTHOR

Jeff Fearn  C<<  >>
=cut
ok 19 - test man output
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/19 subtests
# Testing bin/publican on the Users_Guide
Use of uninitialized value in concatenation (.) or string at 
/<>/blib/script/publican line 1003,  line 14.
Use of uninitialized value in concatenation (.) or string at 
/<>/blib/script/publican line 1003,  line 14.
Use of uninitialized value in concatenation (.) or string at 
/<>/blib/script/publican line 1003,  line 14.
Making portrait pages on USletter paper (8.5inx11in)
[warning] /usr/bin/fop: JVM flavor 'sun' not understood
[warning] /usr/bin/fop: Unable to locate serializer in /usr/share/java
[warning] /usr/bin/fop: Unable to locate xalan2 in /usr/share/java
[warning] /usr/bin/fop: Unable to locate xercesImpl in /usr/share/java
[INFO] FopConfParser - Default page-height set to: 240mm
[INFO] FopConfParser - Default page-width set to: 120mm
[ERROR] FOUserAgent - Image not found. URI: 

Processed: upstream patch available

[Debian Bug Tracking System]

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

> tags 1056440 + patch
Bug #1056440 [src:pyopengl] pyopengl's autopkg tests fail with Python 3.12
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1058269: marked as done (python-pylxd: FTBFS: failed tests)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 11:04:36 +
with message-id 
and subject line Bug#1058269: fixed in python-pylxd 2.2.10-3
has caused the Debian Bug report #1058269,
regarding python-pylxd: FTBFS: failed tests
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.)


-- 
1058269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pylxd
Version: 2.2.10-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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; set -x ; for pyvers in 3.12 3.11; do \
>   python$pyvers -m pytest -v pylxd/deprecated/tests ; \
> done
> + python3.12 -m pytest -v pylxd/deprecated/tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 -- 
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> collecting ... collected 154 items
> 
> pylxd/deprecated/tests/test_certificate.py::LXDAPICertificateTest::test_certificate_operations_1_delete
>  PASSED [  0%]
> pylxd/deprecated/tests/test_certificate.py::LXDAPICertificateTest::test_certificate_operations_2_create
>  PASSED [  1%]
> pylxd/deprecated/tests/test_certificate.py::LXDAPICertificateTest::test_certificate_show
>  PASSED [  1%]
> pylxd/deprecated/tests/test_certificate.py::LXDAPICertificateTest::test_list_certificates
>  PASSED [  2%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_get_connection_1_unix
>  PASSED [  3%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_get_connection_2_unix_path
>  PASSED [  3%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_get_connection_3_https
>  PASSED [  4%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_get_connection_4_https_port
>  PASSED [  5%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_http_connection
>  PASSED [  5%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_https_connection
>  FAILED [  6%]
> pylxd/deprecated/tests/test_connection.py::LXDInitConnectionTest::test_https_proxy_connection
>  FAILED [  7%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_object_1_null
>  PASSED [  7%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_object_2_200
>  PASSED [  8%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_object_3_202
>  PASSED [  9%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_object_4_500
>  PASSED [  9%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_raw_1_null
>  PASSED [ 10%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_raw_2_200
>  PASSED [ 11%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_raw_3_500
>  PASSED [ 11%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_status_1_null
>  PASSED [ 12%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_status_2_200
>  PASSED [ 12%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_status_3_202
>  PASSED [ 13%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_status_4_200
>  PASSED [ 14%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_status_5_500
>  PASSED [ 14%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_ws_1_fake_host
>  PASSED [ 15%]
> pylxd/deprecated/tests/test_connection.py::LXDConnectionTest::test_get_ws_2_None
>  PASSED [ 16%]
> pylxd/deprecated/tests/test_container.py::LXDAPIContainerTestObject::test_container_actions_1_start
>  PASSED [ 16%]
> pylxd/deprecated/tests/test_container.py::LXDAPIContainerTestObject::test_container_actions_2_stop
>  PASSED [ 17%]
> pylxd/deprecated/tests/test_container.py::LXDAPIContainerTestObject::test_container_actions_3_suspend
>  PASSED [ 18%]
> pylxd/deprecated/tests/test_container.py::LXDAPIContainerTestObject::test_container_actions_4_resume
>  PASSED [ 18%]
> pylxd/deprecated/tests/test_container.py::LXDAPIContainerTestObject::test_container_actions_5_reboot
>  PASSED [ 19%]
> 

Bug#1058258: marked as done (networking-sfc: FTBFS: KeyError: slice(1, None, None))

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2024 10:50:38 +
with message-id 
and subject line Bug#1058258: fixed in networking-sfc 17.0.0-2
has caused the Debian Bug report #1058258,
regarding networking-sfc: FTBFS: KeyError: slice(1, None, None)
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.)


-- 
1058258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-sfc
Version: 17.0.0-1
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):
> ==
> FAIL: 
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_service_graph_driver_manager_called
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_service_graph_driver_manager_called
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/networking_sfc/tests/unit/services/sfc/test_plugin.py", 
> line 40, in setUp
> super(SfcPluginTestCase, self).setUp(
>   File "/<>/networking_sfc/tests/unit/db/test_sfc_db.py", line 
> 343, in setUp
> super(SfcDbPluginTestCase, self).setUp(
>   File "/<>/networking_sfc/tests/base.py", line 66, in setUp
> self._subnet = self._make_subnet(
>^^
>   File 
> "/usr/lib/python3/dist-packages/neutron/tests/unit/db/test_db_base_plugin_v2.py",
>  line 601, in _make_subnet
> raise webob.exc.HTTPClientError(code=res.status_int)
> webob.exc.HTTPClientError: The server could not comply with the request since 
> it is either malformed or otherwise incorrect.
> 
> 
> ==
> FAIL: 
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_service_graph_postcommit_driver_manager_exception
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_service_graph_postcommit_driver_manager_exception
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/networking_sfc/tests/unit/services/sfc/test_plugin.py", 
> line 40, in setUp
> super(SfcPluginTestCase, self).setUp(
>   File "/<>/networking_sfc/tests/unit/db/test_sfc_db.py", line 
> 343, in setUp
> super(SfcDbPluginTestCase, self).setUp(
>   File "/<>/networking_sfc/tests/base.py", line 66, in setUp
> self._subnet = self._make_subnet(
>^^
>   File 
> "/usr/lib/python3/dist-packages/neutron/tests/unit/db/test_db_base_plugin_v2.py",
>  line 601, in _make_subnet
> raise webob.exc.HTTPClientError(code=res.status_int)
> webob.exc.HTTPClientError: The server could not comply with the request since 
> it is either malformed or otherwise incorrect.
> 
> 
> ==
> FAIL: 
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_service_graph_precommit_driver_manager_exception
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_service_graph_precommit_driver_manager_exception
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/networking_sfc/tests/unit/services/sfc/test_plugin.py", 
> line 40, in setUp
> super(SfcPluginTestCase, self).setUp(
>   File "/<>/networking_sfc/tests/unit/db/test_sfc_db.py", line 
> 343, in setUp
> super(SfcDbPluginTestCase, self).setUp(
>   File "/<>/networking_sfc/tests/base.py", line 66, in setUp
> self._subnet = self._make_subnet(
>^^
>   File 
> "/usr/lib/python3/dist-packages/neutron/tests/unit/db/test_db_base_plugin_v2.py",
>  line 601, in _make_subnet
> raise webob.exc.HTTPClientError(code=res.status_int)
> webob.exc.HTTPClientError: The server could not comply with the request since 
> it is either malformed or otherwise incorrect.
> 
> 
> ==
> FAIL: 
> networking_sfc.tests.unit.services.sfc.test_plugin.SfcPluginTestCase.test_update_tap_port_chain_consistency
> 

Bug#999989: poco 1.1 uses PCRE3, Mumble 1.5 depends on poco

[Jochen Sprickerhof]

* Chris Knadle  [2024-01-07 00:29]:
The main thing I'd like to understand is how to do coordinate the 
transition (i.e. the release) with the Release Team. I found some 
hints about that here:


https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#lib-trans


The wiki page linked there seems correct. Please ask if you have more 
specific questions. There is also Debian Mentors to help:


https://wiki.debian.org/DebianMentors

Cheers Jochen


signature.asc
Description: PGP signature