Your message dated Wed, 20 May 2026 10:56:00 +0000
with message-id <[email protected]>
and subject line Bug#1136328: Removed package(s) from unstable
has caused the Debian Bug report #1015597,
regarding pyside2: ftbfs with LTO (link time optimization) enabled
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.)
--
1015597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015597
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pyside2
Version: 5.15.2-2
Severity: minor
Tags: sid bookworm
User: [email protected]
Usertags: ftbfs-lto
This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled. For a background
for LTO please see
https://wiki.debian.org/ToolChain/LTO
The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures. The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.
To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:
export DEB_BUILD_MAINT_OPTIONS = optimize=+lto
Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:
export DEB_BUILD_MAINT_OPTIONS = optimize=-lto
or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/pyside2_5.15.2-2_unstable_dpkglto.log
The last lines of the build log are at the end of this report.
[...]
RUN 5: ======================================================================
RUN 5: FAIL: testBasic (__main__.DebuggerTest)
RUN 5: Interrupt and resume evaluation with QScriptEngineDebugger
RUN 5: ----------------------------------------------------------------------
RUN 5: Traceback (most recent call last):
RUN 5: File
"/<<PKGBUILDDIR>>/sources/pyside2/tests/QtScriptTools/debugger_test.py", line
77, in testBasic
RUN 5: self.assertTrue(self.has_resumed >= 1)
RUN 5: AssertionError: False is not true
RUN 5:
RUN 5: ----------------------------------------------------------------------
RUN 5: Ran 1 test in 0.031s
RUN 5:
RUN 5: FAILED (failures=1)
RUN 5:
RUN 5:
RUN 5: 0% tests passed, 4 tests failed out of 4
RUN 5:
RUN 5: Total Test time (real) = 0.65 sec
RUN 5:
RUN 5: The following tests FAILED:
RUN 5: 17 - pysidetest_qapp_like_a_macro_test (Subprocess aborted)
RUN 5: 142 - QtCore_qflags_test (Failed)
RUN 5: 436 - QtQml_javascript_exceptions (Failed)
RUN 5: 446 - QtScriptTools_debugger_test (Failed)
RUN 5: Errors while running CTest
End of the test run
RES 5: Test #17: FAIL! pysidetest::qapp_like_a_macro_test()
RES 5: Test #142: BFAIL QtCore::qflags_test()
RES 5: Test #436: BFAIL QtQml::javascript_exceptions()
RES 5: Test #446: BFAIL QtScriptTools::debugger_test()
Totals: 4 tests. 0 passed, 1 failed, 0 skipped, 3 blacklisted, 0 bpassed.
********* Finished testing of pyside2 *********
All above projects: 668 tests. 632 passed, 5 failed, 0 skipped, 15 blacklisted,
16 bpassed.
*******************************************************************************
**
* Summary Of All Tests
*
FAIL! FAIL! FAIL! FAIL! FAIL! pyside2:pysidetest::qapp_like_a_macro_test Newly
detected Real test failure!
BFAIL BFAIL BFAIL BFAIL BFAIL pyside2:QtCore::qflags_test Keep
blacklisting ;-(
BFAIL BFAIL BFAIL BFAIL BFAIL pyside2:QtQml::javascript_exceptions Keep
blacklisting ;-(
BFAIL BFAIL BFAIL BFAIL BFAIL pyside2:QtScriptTools::debugger_test Keep
blacklisting ;-(
*
**
*******************************************************************************
Total flaky tests: errors but not always = 0
+++++ Note: please support pyside2-tools +++++
Total time of whole Python script = 113.53 sec
Traceback (most recent call last):
File "/<<PKGBUILDDIR>>/testrunner.py", line 53, in <module>
testing.main()
File "/<<PKGBUILDDIR>>/testing/command.py", line 349, in main
raise ValueError("At least one failure was not blacklisted "
ValueError: At least one failure was not blacklisted and met the criterion
'FAIL! >= 3'
E: pybuild pybuild:369: test: plugin custom failed with: exit code=1:
python3.10 testrunner.py test
dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.10"
--system=custom --test-args "{interpreter} testrunner.py test" returned exit
code 13
make[1]: *** [debian/rules:61: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:30: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Version: 5.15.18-1+rm
Dear submitter,
as the package pyside2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1136328
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
