kcollectd is marked for autoremoval from testing
kcollectd 0.11.0-1 is marked for autoremoval from testing on 2020-07-18 It (build-)depends on packages with these RC bugs: 959675: libgrpc++1: libgrpc++1: endless looping with default settings 961193: libgrpc++1: libgrpc++1 must be linked with libatomic on armel/mips/mipsel/powerpc
Re: Does Plasma/KDE work under Wayland?
On Wed, 10 Jun 2020 at 23:16, Ihor Antonov wrote: > > Hi Borden, > > Unfortunately packaging KDE/Plasma is hard and it takes a lot of time, so > there is also a noticeable delay between upstream releases and packages > availability. Keep testing is the minimum we can do for Debian. But if you > have time and desire - reporting bugs upstream and helping with packaging > are also time-worthy activities/ > Thank you for the comments. What I'm having most difficulty with is finding debugging information when something goes wrong. For example, KMail hangs as soon as I start it up requiring a force-quit. However, I can't find anything in journalctl or the console indicating what went wrong. So that defeats any attempts at filing a bug report. If I knew how to identify failing components (for all I know, it could be a configuration error), then that would be extremely useful for everyone. Suggestions? > > [1] https://kde.org/announcements/plasma-5.19.0 > [2] > https://pointieststick.com/2020/06/08/lenovo-thinkpad-x1-yoga-impressions-bugs-workarounds-and-thoughts-about-the-future/
RE: How do I troubleshoot wireless network dropping?
> Use ps x to see how many copies of wpa_supplicant are running. If you have > multiple copies started from the command line the wifi won't stay connected. > I had the same problem. Thank you for the suggestion. I checked when it started dropping and, not only was there one instance of wpa_supplicant running, it was the same instance (judging from its PID) > Keep off the Intel card when you use the USB dongle, maybe one interfere with > the other Another good suggestion. I've tried disabling it from ifconfig. The interfaces use consistent device naming, so the names shouldn't be getting mixed up. I've isolated, what I think are, the journal lines from when my connection dropped today: wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-DISCONNECTED bssid=a0:##:##:##:##:0a reason=4 locally_generated=1 wpa_supplicant[1555]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wpa_supplicant[1555]: wlp10s0: SME: Trying to authenticate with a0:##:##:##:##:0a (SSID='WiFiNetwork' freq=2462 MHz) wpa_supplicant[1555]: wlp10s0: Trying to associate with a0:##:##:##:##:0a (SSID='MyNetwork' freq=2462 MHz) wpa_supplicant[1555]: wlp10s0: Associated with a0:##:##:##:##:0a wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA wpa_supplicant[1555]: wlp10s0: WPA: Key negotiation completed with a0:##:##:##:##:0a [PTK=CCMP GTK=CCMP] wpa_supplicant[1555]: wlp10s0: CTRL-EVENT-CONNECTED - Connection to a0:##:##:##:##:0a completed [id=0 id_str=] For the purposes of these log entries, "WiFiNetwork" is the SSID of my network, but the log literally shows "MyNetwork" in the next line when it's trying to associate. I have no idea what this network is and I can't find it configured anywhere. So is it possible that someone's trying to MAC-jack my laptop?
qca2_2.3.0-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jul 2020 20:23:57 +0200 Source: qca2 Architecture: source Version: 2.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: qca2 (2.3.0-1) unstable; urgency=medium . * Team upload. * New upstream release. * Add the configuration for the CI on salsa. * Update the build dependencies according to the upstream build system: - bump cmake to 3.4 - bump Qt5 to 5.6 * Update the patches: - define_qca_export.diff: refresh - pipeunittest_more_wait.diff: refresh - hurd_msync.diff: refresh - kubuntu_ignore_filewatch_test.diff: refresh * Update symbols file. * Remove extra trailing whitespaces in changelog. * Small changes to copyright. * Use DEB_CFLAGS_MAINT_APPEND & DEB_CXXFLAGS_MAINT_APPEND to append the visibility build flags, instead of setting CFLAGS & CXXFLAGS directly. * Switch from dhmk to the dh sequencer: - call the right debhelper command instead of $(overridden_command) - manually force the generation of the strict shlibs handling - remove the overrides that do not do anything more than the command itself * Remove debian/not-installed, no more needed now. * Remove the unused 'testsuite' autopkgtest. * Update lintian overrides. * Add Rules-Requires-Root: no. * Build the documentation only in -indep builds: - move doxygen as Build-Depends-Indep - perform the normal build in dh_auto_build-arch, and only build the doc in dh_auto_build-indep - disable dh_auto_install-indep, and auto_test-indep, as there is nothing to do in these cases * Simplify libqca2-doc.install by installing the output directory as a whole - avoid shipping .md5 files * Add graphviz as Build-Depends-Indep to improve the generated HTML apidox. * Bump Standards-Version to 4.5.0, no changes required. * Add the upstream signing key. * Use /usr/share/dpkg/architecture.mk to get $DEB_HOST_MULTIARCH, instead of querying dpkg-architecture manually. Checksums-Sha1: 521b292e961601c6fb5c596bb1b37f086876afa1 2704 qca2_2.3.0-1.dsc b473751d7de77dc1e936c8036d05b8464e25ed0c 729504 qca2_2.3.0.orig.tar.xz 931fffa83368dc4a9b2d1243c82b9063cc4d16f9 833 qca2_2.3.0.orig.tar.xz.asc 8faec6804b6b38bf70e359371f576cb5d3caa234 27384 qca2_2.3.0-1.debian.tar.xz fca56de1374f3cdcd0683025c131919b11713a74 10846 qca2_2.3.0-1_source.buildinfo Checksums-Sha256: 8e35cd270c533495a0e1ef729b7db694b0f7535b862c715811c8b688b50bc34d 2704 qca2_2.3.0-1.dsc 1d68ef41a1b61dc9786beb923a68902a6276a77cced5e5ea7ff985ef113932d7 729504 qca2_2.3.0.orig.tar.xz d5ab0dee0106af3fb9e1a7dc8d3c7ff157403c09477048685576a6712cdfa87c 833 qca2_2.3.0.orig.tar.xz.asc 8dc2787ca9100266cd372882e405baa99c714387a8816f2f9f4b9565dc9e8959 27384 qca2_2.3.0-1.debian.tar.xz 69ae628f507902b7a43867408e1fe5df9eaa6232230a8fdce2472d06817db5e0 10846 qca2_2.3.0-1_source.buildinfo Files: d0f9f34f6d94aa19781ac33d5d758379 2704 libs optional qca2_2.3.0-1.dsc 139829d029fe70248f0b059b43dc4316 729504 libs optional qca2_2.3.0.orig.tar.xz 4672a2ce8cd8d053f2b1d7b0765e17de 833 libs optional qca2_2.3.0.orig.tar.xz.asc 4042f0ce3f3dc313b14ee49f83e92ff9 27384 libs optional qca2_2.3.0-1.debian.tar.xz f12a5ce90c38c25015c20b3270afb89f 10846 libs optional qca2_2.3.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl8CGu8ACgkQLRkciEOx P00NmhAAmGxA2JDqj1lt4mvD389NOjBQH+vwieDNgYL5FtUBIxbVUFNBDnzJTX0p F1RMlmiJ/WoFhLdL+PPG5OTyQKLEggCqhBtvmc/fVl7UH99F+Nqfrl84x0RkhxK+ X3GrXxV+XS7KSPmf0XIoRRimOYses3zJp35I/1LnmkfFQaF/UBLJE75foLx/90H4 6sDQZ5ZBPn1gfwqxApm+ORy2c1fPfh38MKWLmejzTeolDEdZzi7l+Xpyj0yjw0qA HRC6o5IJotQ7P8VjqSVUFX5epyT0z2J0rkDlt9X5O+U/q4WFjeWM5P8gTbuRRpsN GF0fV0VVCdcr8nxMssu/mtIfqQT1ClaSj905gctusV6EAPfPc7ptd2RLEFIpcsYX mwsg0OubijE+t4tdlJUj2BmhZStwrB7XdzTwohS/Tr1047NiW4vJSqL55vWcQv17 gwGS3kCTKmRlpAx3WLln6H+BRpidB87ty359Z/6J3CcrkaepfDK9V+zeQfy79jjx 6c3vJQbut/LLW950iCpb8b+O07lbfvBM8aF9SzuwB66elRvic0AzZFwmNqKURdA4 yPubdk6vpDFGZFc0635K+vE5wdb46DOA1wAyYnO19S1UrbnHKqTD2L7r2HZMvDzk RdhRNyOnVMPyeQsUJrdagHTRYtwjlp/hqOtEH/NRS+YilXyYi/8= =eI6W -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of qca2_2.3.0-1_source.changes
qca2_2.3.0-1_source.changes uploaded successfully to localhost along with the files: qca2_2.3.0-1.dsc qca2_2.3.0.orig.tar.xz qca2_2.3.0.orig.tar.xz.asc qca2_2.3.0-1.debian.tar.xz qca2_2.3.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: Status of Plasma 5.18/5.19?
Hi, I am slowly learning Debian packaging myself. Also I tried to compile KDE myself, while this is not 100% successful it learned my how big KDE is. >From the discussions in this thread, once I asked the question also, it became clear to me that having a small team on one end and a huge amount of packages on the other side will lead to long throughput times in bringing upstream changes to Debian packages. Automation and working together are key-words, (the only?) in shortening the throughput times. I do not know what led to the frictions in the past. But make a plea to look forward, grab help and focus on achieving shorter throughput times in bringing KDE changes to Debian. Let me know if/how I can help. Regards Luc Op zo 5 jul. 2020 om 15:49 schreef Norbert Preining : > Hi Dietz, > > > Would you mind announcing relevant changes from your side (changed > repos, > > discontinued development and so on) also oh debian-kde? > > I don't think this is welcome here, since also on the IRC channel I was > told not to advertise my repositories. > > I suggest you to follow my blog, tag "KDE" to receive updates. > > Thanks > > Norbert > > -- > PREINING Norbert https://www.preining.info > Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 > > -- Luc Castermans mailto:luc.casterm...@gmail.com
Re: Status of Plasma 5.18/5.19?
Hi Dietz, > Would you mind announcing relevant changes from your side (changed repos, > discontinued development and so on) also oh debian-kde? I don't think this is welcome here, since also on the IRC channel I was told not to advertise my repositories. I suggest you to follow my blog, tag "KDE" to receive updates. Thanks Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: Status of Plasma 5.18/5.19?
Hi Norbert, and I have to confess - looks like a really, really decent piece of work you did. Quite a pity, that there seem to be differences on using what you have been producing. Would you mind announcing relevant changes from your side (changed repos, discontinued development and so on) also oh debian-kde? Kindest regards, Dietz Am Sonntag, 28. Juni 2020, 10:14:21 CEST schrieb Norbert Preining: > Hi Jeremy, > > It is now 5.19.2 (and frameworks 5.71), see here > https://www.preining.info/blog/2020/06/kde-plasma-5-19-2-for-debian/ > thanks to the upload of Qt 5.14 to unstable. > > Feel free to try it out but report bugs to me and **not** the Debian BTS. > > And don't break Debian :-D > > Best > > Norbert signature.asc Description: This is a digitally signed message part.
pyside2_5.15.0-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jul 2020 05:13:51 -0500 Source: pyside2 Architecture: source Version: 5.15.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Kurt Kremitzki Closes: 963983 964201 Changes: pyside2 (5.15.0-3) unstable; urgency=medium . [ Dmitry Shachnev ] * Bump Qt build-dependencies to 5.14. As most Qt packages have a Build-Depends-Package field in their symbols files, dpkg-shlibdeps will use that information and generate a runtime dependency on a new enough Qt version (closes: #963983). . [ Kurt Kremitzki ] * Remove Freexian folks and add myself to Uploaders * Correct libshiboken2 CMake include path (Closes: #964201) Checksums-Sha1: be0f9d6924b513347296c6bfe5e727b652f01cf6 7276 pyside2_5.15.0-3.dsc 8eadf5b0845dad2443577f1bb434488e7a7b8076 51772 pyside2_5.15.0-3.debian.tar.xz 8782368b24a78fe9a0145049e5d9a411fe570791 20547 pyside2_5.15.0-3_source.buildinfo Checksums-Sha256: 4ce07893f203f25146dd8272cc74f1635b954fe174caa121bc30812fec1cb85a 7276 pyside2_5.15.0-3.dsc 33c54f235ceaa57b78915aefa7a0960f169d8f6bbcb3bb90ab66e9965780e0c7 51772 pyside2_5.15.0-3.debian.tar.xz 99a129a7a89180ad5135a76c0c9b665501061a078b3931c4db4c2b5b0c1fd3bb 20547 pyside2_5.15.0-3_source.buildinfo Files: 766f0421fe5e3ff34f7a2b0feacfc0b9 7276 python optional pyside2_5.15.0-3.dsc b2cb19576fa3d5009d524e065ae03e07 51772 python optional pyside2_5.15.0-3.debian.tar.xz feece5ba30867bc74cb4b23ae7a839ca 20547 python optional pyside2_5.15.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEERwo36jwR3bV97u6LA0twKzc+z0UFAl8BqUIWHGtrcmVtaXR6 a2lAZGViaWFuLm9yZwAKCRADS3ArNz7PRcN+D/wMRqAFfllBrPd4wYn7SYdtCbps cbkM8oKF0dDuBZLTUN2PLIbFw8RKN3sSkzCOyIzqSG0meSxOS0Rv3JyR6DwqCDrw ZnkbUGe9uLQRDukSeSKYfeQhtdpvv4vpzGJEPIILqSHbMpLEWFBKux8ZgDdPwctd zxUXq2Yduf+KlG6WG3XpVoKUfoOFbMZexuGv9EIEr5N518HZy9xMVh47flIOV6FK xFpBOmCYPwnT9WMitKy+v+hqQtbuB6AsF0Oivk4wY3nHSi05Otgs0ycXAJTAOn6q hiVD+DfTq2LrPNAexNnZGcKmnb+UYlp/AiMB0s6HN5GA5KBwuR/S/MysBP2G/MJm i76q0bw6KjLB92LIGXpeV2Ha9XSbQ/cBE2guoPOOUBnj2KZG0UlBUygOkwIkvX8x 527e/Dyv0n5Nz3XImuoKAhIpX1SwNY675+A9ba3SznDXCyDqvYzjT8+u+bQUxhec Li5I9Qhblh9uPbwApbiYXYaAhhg7Nk0iEH8oV91F4fH8kgsdona83IQgvi03PgoE vNyBZlP+qzQhL2a95i94ZANNkkMABpJpqeE3Izq/p038Cv/IFdpn04jQi6uGP5pO gIIn/r6ptEMawXFzgFvQW27hZsqMnQpsf0QFuHZk+qZGBt6+TBCu88wzPZsGIUjt zRtKbY2n0wc1dJg7zA== =cG7W -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of pyside2_5.15.0-3_source.changes
pyside2_5.15.0-3_source.changes uploaded successfully to localhost along with the files: pyside2_5.15.0-3.dsc pyside2_5.15.0-3.debian.tar.xz pyside2_5.15.0-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#963983: marked as done (python3-pyside2.qtsvg: segfault on import)
Your message dated Sun, 05 Jul 2020 10:33:35 +
with message-id
and subject line Bug#963983: fixed in pyside2 5.15.0-3
has caused the Debian Bug report #963983,
regarding python3-pyside2.qtsvg: segfault on import
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.)
--
963983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyside2.qtsvg
Version: 5.15.0-1
Severity: grave
$ gdb python3
...
Reading symbols from python3...
Reading symbols from
/usr/lib/debug/.build-id/97/0f19629d98e5c631b44f6803fa34a5a07c3806.debug...
(gdb) r
Starting program: /usr/bin/python3
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.8.3 (default, May 14 2020, 11:03:12)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from PySide2 import QtSvg
Program received signal SIGSEGV, Segmentation fault.
0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*, char
const*, char const*, PyType_Spec*, char const**, void (*)(void*),
SbkObjectType*, _object*, unsigned int) ()
from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
(gdb) bt
#0 0x772cf2eb in Shiboken::ObjectType::introduceWrapperType(_object*,
char const*, char const*, PyType_Spec*, char const**, void (*)(void*),
SbkObjectType*, _object*, unsigned int)
() from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15
#1 0x7731ec41 in ?? () from
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#2 0x7732a6a3 in PyInit_QtSvg () from
/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so
#3 0x0067d0aa in _PyImport_LoadDynamicModuleWithSpec (
spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>, fp=) at
../Python/importdl.c:164
#4 0x0067dafd in _imp_create_dynamic_impl (module=,
file=,
spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>) at ../Python/import.c:2221
#5 _imp_create_dynamic (module=, args=,
nargs=) at ../Python/clinic/import.c.h:330
#6 0x005c066c in cfunction_vectorcall_FASTCALL (func=, args=, nargsf=,
kwnames=) at ../Objects/methodobject.c:422
#7 0x005f1da9 in PyVectorcall_Call (callable=, tuple=, kwargs={}) at ../Objects/call.c:199
#8 0x0056d160 in do_call_core (kwdict={},
callargs=(,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>,), func=, tstate=) at
../Python/ceval.c:4983
#9 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3559
#10 0x00565602 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x77677610, for file , line 219,
in _call_with_frames_removed (f=, args=(,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>,), kwds={})) at ../Python/ceval.c:741
#11 _PyEval_EvalCodeWithName (_co=, globals=,
locals=, args=, argcount=,
kwnames=,
kwargs=0x776de7e0, kwcount=, kwstep=1, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0, name='_call_with_frames_removed',
qualname='_call_with_frames_removed')
at ../Python/ceval.c:4298
#12 0x005f12a3 in _PyFunction_Vectorcall (func=,
stack=0x776de7d0, nargsf=, kwnames=) at
../Objects/call.c:435
#13 0x0056c1bf in _PyObject_Vectorcall (kwnames=0x0, nargsf=, args=0x776de7d0, callable=) at
../Include/cpython/abstract.h:127
#14 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x959e20) at ../Python/ceval.c:4963
#15 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3469
#16 0x005f10c6 in PyEval_EvalFrameEx (throwflag=0,
f=Frame 0x776de640, for file ,
line 1357, in create_module (self=, spec=,
origin='/usr/lib/python3/dist-packages/PySide2/QtSvg.cpython-38-x86_64-linux-gnu.so',
loader_state=None, submodule_search_locations=None, _set_fileattr=True,
_cached=None) at remote 0x7760d1f0>)) at
Bug#964201: marked as done (libshiboken2-dev: Wrong include path for CMake in INTERFACE_INCLUDE_DIRECTORIES)
Your message dated Sun, 05 Jul 2020 10:33:35 + with message-id and subject line Bug#964201: fixed in pyside2 5.15.0-3 has caused the Debian Bug report #964201, regarding libshiboken2-dev: Wrong include path for CMake in INTERFACE_INCLUDE_DIRECTORIES 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.) -- 964201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libshiboken2-dev Version: 5.15.0-2 Severity: important Dear Maintainer! Similar to bug #949846, the include path in libshiboken is wrong. Using the same script as in the other bugreport, you can see the following output: -- Shiboken2Config: Using default python: .cpython-38-x86_64-linux-gnu -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.3", minimum required is "3") -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found suitable version "3.8.3", minimum required is "3") -- SHIBOKEN_PYTHON_INCLUDE_DIRS computed to value: '/usr/include/python3.8' -- SHIBOKEN_PYTHON_LIBRARIES computed to value: '' -- libshiboken built for RelWithDebInfo CMake Error at CMakeLists.txt:6 (get_property): get_property could not find TARGET Shiboken2:libshiboken. Perhaps it has not yet been created. Shiboken2::libshiboken AUTOGEN_ORIGIN_DEPENDS = ON Shiboken2::libshiboken AUTOMOC_COMPILER_PREDEFINES = ON Shiboken2::libshiboken AUTOMOC_MACRO_NAMES = Q_OBJECT;Q_GADGET;Q_NAMESPACE Shiboken2::libshiboken AUTOMOC_PATH_PREFIX = ON Shiboken2::libshiboken BINARY_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken BINARY_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken BUILD_WITH_INSTALL_RPATH = OFF Shiboken2::libshiboken IMPORTED = TRUE Shiboken2::libshiboken IMPORTED_CONFIGURATIONS = RELWITHDEBINFO Shiboken2::libshiboken IMPORTED_GLOBAL = FALSE Shiboken2::libshiboken INSTALL_RPATH = Shiboken2::libshiboken INSTALL_RPATH_USE_LINK_PATH = OFF Shiboken2::libshiboken INTERFACE_INCLUDE_DIRECTORIES = /usr/lib/include/shiboken2;/usr/include/python3.8 Shiboken2::libshiboken NAME = Shiboken2::libshiboken Shiboken2::libshiboken POSITION_INDEPENDENT_CODE = True Shiboken2::libshiboken SKIP_BUILD_RPATH = OFF Shiboken2::libshiboken SOURCE_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken SOURCE_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken TYPE = SHARED_LIBRARY Shiboken2::libshiboken TYPE = SHARED_LIBRARY Shiboken2::libshiboken UNITY_BUILD_BATCH_SIZE = 8 -- Configuring incomplete, errors occurred! The include path should be /usr/include/shiboken2 instead of /usr/lib/include/shiboken2 Thank you! Best regards Sebastian -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libshiboken2-dev depends on: ii libshiboken2-py3-5.15 5.15.0-2 ii python3-dev3.8.2-3 ii shiboken2 5.15.0-2 libshiboken2-dev recommends no packages. libshiboken2-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pyside2 Source-Version: 5.15.0-3 Done: Kurt Kremitzki We believe that the bug you reported is fixed in the latest version of pyside2, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated pyside2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jul 2020 05:13:51 -0500 Source: pyside2 Architecture: source Version: 5.15.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Kurt Kremitzki Closes: 963983 964201 Changes: pyside2 (5.15.0-3) unstable;
