[PySide] Build provenance for official PySide6 6.9.2 Windows

[David Ching]

I'm also distributing a proprietary application, using the official
PySide6/Qt binaries, currently version 6.10.2, under LGPLv3.

It hadn't occurred to me that we had to list Qt's embedded dependencies as
you are attempting to do.

I believe I am fulfilling the open source obligations.

See https://dcsoft.com/Products/TimeStitcherAcknowledgements.  Included on
this page:

Third-Party Components Included in Qt
TimeStitcher redistributes official PySide6, Shiboken6, and Qt binaries.
These binaries may incorporate additional open-source components maintained
by third parties.
The Qt Project maintains the corresponding third-party license attributions
and software bill of materials. See:
	Third-Party Code Used in Qt --
https://doc.qt.io/qt-6.10/licenses-used-in-qt.html
	Qt Software Bill of Materials --
https://doc.qt.io/qt-6.10/licenses-used-in-qt.html

I presume these references are sufficient but would be welcome to hear of
corrections.

Thanks,
David


-----Original Message-----
Date: Sun, 18 Oct 2026 14:02:19 +0800
From: Muhamad Rozaimi <admin.zaiclox5 at gmail.com>
To: pyside at qt-project.org
Subject: [PySide] Build provenance for official PySide6 6.9.2 Windows
	x64 wheels
Message-ID:
	<CAMK5wO+b+bP2X4QHVZxObosxkDYgkWorMW+0aCy8o2LPdR6png at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello Qt for Python team,

RZM Network is reviewing the open-source release materials for ZaiMiXplorer,
a Windows application branded ZaiCloX5. We use the official
PySide6_Essentials, PySide6_Addons, and shiboken6 6.9.2 cp39-abi3-win_amd64
wheels. We have the published Qt and PySide source archives, but need to
identify the build inputs and third-party source corresponding to the
binaries in those wheels. Could you point us to a release-specific build
record or SPDX SBOM, or answer the following?

   1. What Qt/PySide/Shiboken source revisions, configuration options,
   build patches, and third-party dependency versions produced the published
   Windows wheels? If a build-specific SBOM exists, where is it available?
   2. The wheel?s qjpeg.dll identifies libjpeg-turbo 3.0.3, whereas the Qt
   6.9.2 source declaration identifies 3.1.1. Which libjpeg-turbo source and
   patches correspond to this binary, and is it statically linked?
   3. Which PDFium revision, build options, and nested third-party
   components produced Qt6Pdf.dll, Qt6PdfWidgets.dll, and qpdf.dll? Where
   are the notices applicable to those wheel binaries?
   4. Which Mesa and LLVM sources, patches, and build settings produced the
   bundled opengl32sw.dll? Its binary indicators point to Mesa 11.2.2 and
   LLVM 3.6.2, but we have not established the exact build provenance.
   5. Are there release-specific materials or instructions for replacing
   LGPL-covered Qt/PySide/Shiboken components from these wheels when
   redistributed in a PyInstaller onedir application?

For unambiguous identification, the PyPI wheel SHA-256 values we reviewed
are:

   - PySide6_Essentials:
   b2f746f795138ac63eb173f9850a6db293461a1b6ce22cf6dafac7d194a38951
   - PySide6_Addons:
   98d2413904ee4b2b754b077af7875fa6ec08468c01a6628a2c9c3d2cece4874f
   - shiboken6:
   68c33d565cd4732be762d19ff67dfc53763256bac413d392aa8598b524980bc4

Thank you for any build records, source links, or a pointer to the
appropriate team.

RZM Network
ZaiCloX5
admin.zaiclox5 at gmail.com