Your message dated Sun, 29 Mar 2026 02:48:38 +0000
with message-id <[email protected]>
and subject line Bug#1131536: fixed in pyside6 6.10.2-5
has caused the Debian Bug report #1131536,
regarding PySide6Config.abi3.cmake /usr/typesystems
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 [email protected]
immediately.)


-- 
1131536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131536
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpyside6-dev
Version: 6.10.2-4
Severity: normal

Noticed this while building with the new package:

| CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/PySide6/PySide6Config.abi3.cmake:15 (message):
|   File or directory /usr/typesystems referenced by variable
|   PYSIDE_TYPESYSTEMS does not exist !

this is seen at:

set_and_check(PYSIDE_TYPESYSTEMS "/usr/typesystems")
set_and_check(PYSIDE_GLUE "/usr/glue")

which I assume should be:

set_and_check(PYSIDE_TYPESYSTEMS "/usr/share/PySide6/typesystems")
set_and_check(PYSIDE_GLUE "/usr/share/PySide6/typesystems/glue")

according to the installed files.

Similarly, PySide6Targets.cmake has:

set_target_properties(PySide6::pyside6 PROPERTIES
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/PySide6/include"
)

which leads to:

| Imported target "PySide6::pyside6" includes non-existent path
|
|   "/usr/lib/PySide6/include"
|
| in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

yet, the includes seem to be located in /usr/include/PySide6

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

Kernel: Linux 6.19.8+deb14-rt-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpyside6-dev depends on:
ii  libpyside6-py3-6.10  6.10.2-4

libpyside6-dev recommends no packages.

libpyside6-dev suggests no packages.

--- End Message ---
--- Begin Message ---
Source: pyside6
Source-Version: 6.10.2-5
Done: Stuart Prescott <[email protected]>

We believe that the bug you reported is fixed in the latest version of
pyside6, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stuart Prescott <[email protected]> (supplier of updated pyside6 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 29 Mar 2026 13:21:51 +1100
Source: pyside6
Architecture: source
Version: 6.10.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <[email protected]>
Changed-By: Stuart Prescott <[email protected]>
Closes: 1131536 1131974
Changes:
 pyside6 (6.10.2-5) unstable; urgency=medium
 .
   * Remove nocheck annotations for xauth and xvfb to fix FTBFS with the
     nocheck build profile (Closes: #1131974).
   * Rework cmake and pkgconf substitutions to get paths correct
     (Closes: #1131536).
   * Add autopkgtest that reveals and partially checks cmake and pkgconf data.
Checksums-Sha1:
 269c9f011f6e2111df431e6c55f1751715e320b8 9945 pyside6_6.10.2-5.dsc
 28257d6e10f2122dbdbadfd5588b9913b2e022c0 30424 pyside6_6.10.2-5.debian.tar.xz
 f95f750b3456e9478a5ebc4fa20bd00a8db405d7 23347272 pyside6_6.10.2-5.git.tar.xz
 0ea83136887c8c6abf1ba48be61be40376b3b403 17333 
pyside6_6.10.2-5_source.buildinfo
Checksums-Sha256:
 a6ea9f33b395a6b82508c473176491add8b7d1ca738956be239ab94c2608876f 9945 
pyside6_6.10.2-5.dsc
 8739e7d052606460b0d23af6f5ff7c0e17a5b0f6c026834afaf8113b8c8d29c6 30424 
pyside6_6.10.2-5.debian.tar.xz
 6893882b1dc468f7e8b6deb4f6883f8ba20dbdef4a767e84f23a0c9428ccc989 23347272 
pyside6_6.10.2-5.git.tar.xz
 ea4de7f3cc5d989084f28ed063b5d5f6db1a0c834579cb2f66cda11f3f22178c 17333 
pyside6_6.10.2-5_source.buildinfo
Files:
 9759c259727adeaa4d3dfd06bb10aaff 9945 python optional pyside6_6.10.2-5.dsc
 527cc5004979b9c0867c3f0afb9aee1f 30424 python optional 
pyside6_6.10.2-5.debian.tar.xz
 7ef5f220e36ab8d15d17cc5e49bdcdcf 23347272 python None 
pyside6_6.10.2-5.git.tar.xz
 16d7ae01e2e580021629d51a9ce71003 17333 python optional 
pyside6_6.10.2-5_source.buildinfo
Git-Tag-Info: tag=81bcd5f13bf097327574477113feb5a7382b9c27 
fp=90e2d2c1ad146a1b7ebb891dbbc17ebb1396f2f7
Git-Tag-Tagger: Stuart Prescott <[email protected]>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmnIkJAACgkQYG0ITkaD
wHliKw//bYnrzox+6yoPl1hHQIn3WsZElQNWQHvel1ypvdO5tkVwuRFCV+eZV41W
MtVuQs48SuUxtG8fk2PO79HIWzO+IX1j5fBet7Uy4XiZoYl3SEpbSyXboapUGtJx
TAafBV8IcHMrBgvgSLOHfG/7925cRkjzKEMF6I1B4kC3E7/K3V0p/pqoYYVwwrPa
HVTlnn4znK2ILub+2M9gVLnKwlUTK9ZtUCwJfyWCOF5y0DsGcpFzyWVjk4z9Jdz/
WA7Qrgu8NbK92Xi1jdNI4X9J+8zpo3dKou7lg7vU3ZEMmp0mqBti9ZFE5bz9mcTe
kywbdWknlTH23JBEr/5cws7/PKz4kTmdYCzSb9NyfE6TzFKWb7iX5senUjj/3DR0
T6psa6/ztr+vcejsEt1OcHDuelFyI7HAjg7THWU2uTDSYWtVER6pYZuu5xbNv90P
LxlsAFO3dTasoafp9lj/2YnFFal37Rksrvp/eOzYRFQpqqrE1zq00RDp+lD5d/EL
5GpBMs3ZZ2BfWTQ8u7ZwF8m0/RWXIUp3ycBO1qu3eUgN/dFjZONBY53G94MlG4Pd
XjqsHZfLpuJiGn8rRrbFbnes8OwbfK32W9S6nYOhdB+DtYrTSRnWK6F1/oCNj/0i
VRO1FdSs1jYoI6Ehk0TA0Qxye7j1tr6C+iWxoDvaMM/WlSXlQgE=
=qV2e
-----END PGP SIGNATURE-----

Attachment: pgpw7yol14F2V.pgp
Description: PGP signature


--- End Message ---

Reply via email to