| Summary: | python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip) | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Bernard Gray <bernard.gray> |
| Component: | general | Assignee: | Neon Bugs <neon-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | jr, kde, neon-bugs, sitter |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Bernard Gray
2017-06-09 04:08:02 UTC
Ok, I've worked it out what's actually going wrong. Apologies, lack of sleep and soforth: "python3-pykde4" is an ubuntu provided package, that depends on a virtual package "sip-py3api-11.2" provided by python3-sip (< 4.19) The neon repositories now include python3-sip=4.19.2+dfsg-1+16.04+xenial+build3 but this does not provide "sip-py3api-11.2" # apt-cache show python3-sip | egrep -e ^Provides -e ^Version Version: 4.19.2+dfsg-1+16.04+xenial+build3 Provides: sip-py3api-12.0, sip-py3api-12.1 ... Is it possible to build python3-sip to include provides for sip-py3api-11.X AND sip-py3api-12.X? (In reply to Bernard Gray from comment #1) > Is it possible to build python3-sip to include provides for sip-py3api-11.X > AND sip-py3api-12.X? Alternatively, can neon start including compatible builds of python3-pykde4 in their repos? All this means is that pykde4 (and possibly pyqt4) need to be rebuilt in the neon repositories against the current sip4. There's no upstream issue here. Hi Scott, Thanks for the reply. I apologise, but I thought this bugtracker is where I would make neon related requests. I gather from your post that I was wrong - can you point me in the direction of where I should post my request to rebuild python3-pykde4? Honestly, I don't know. I don't have anything to do with Neon, but this isn't a KDE bug, it's a bug in their packaging. Moving to neon. I've done a bit more digging: I ended up finding the following bug/patch on the NixOS github project: https://github.com/NixOS/nixpkgs/issues/24548 https://github.com/NixOS/nixpkgs/commit/8c9b60a8307b4dafffb894b3d652389f6079b68a "This package is broken since 0a3b7f9 (python-sip: 4.18.1 -> 4.19.1). Removing it seems reasonable since we're dropping KDE4 anyway." I suspect that this is precisely what Neon is doing too, although I don't know where to find evidence of it. I've ended up migrating my in-house python package to PyQt5 anyway since finding this :) yes the new sip needed for qt 5.9 breaks current build of pykde4. However I couldn't get pykde4 to build with latest sip/kdelibs/whatever /usr/include/kautomount.h:105:5: error: ‘KAutoUnmount::~KAutoUnmount()’ is private http://build.neon.kde.org/job/xenial_release_forks_pykde4_bin_amd64/1/console (In reply to Jonathan Riddell from comment #8) ... > However I couldn't get pykde4 to build with latest sip/kdelibs/whatever > /usr/include/kautomount.h:105:5: error: ‘KAutoUnmount::~KAutoUnmount()’ is > private > http://build.neon.kde.org/job/xenial_release_forks_pykde4_bin_amd64/1/console Hi Jonathon, thanks for having a look. I had the same issue trying to build pykde4, the packages that depend on it are pretty thin on the ground now, is it worth just committing to it's removal for neon? python3-pykde4 Reverse Depends: python3-pykde4-dbg update-manager-kde apturl-kde update-manager-kde python3-keyring python3-keyrings.alt gdebi-kde apturl-kde Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |