Hi Aurélien (2025.01.26_20:02:16_+0000) > That’s not correct for the version you’ve mentioned in the bug report. > kdevelop-python 24.12.1-1 has : > > Build-Depends: debhelper-compat (= 13), dh-sequence-kf6, cmake (>= 3.19~), > extra-cmake-modules (>= 6.0.0~), gettext, kdevelop-dev (>= 4:24.12~), > libkf6config-dev (>= 6.0.0~), libkf6coreaddons-dev (>= 6.0.0~), > libkf6i18n-dev (>= 6.0.0~), libkf6parts-dev (>= 6.0.0~), libkf6service-dev > (>= 6.0.0~), libkf6texteditor-dev (>= 6.0.0~), libkf6threadweaver-dev (>= > 6.0.0~), libkf6widgetsaddons-dev (>= 6.0.0~), libkf6xmlgui-dev (>= 6.0.0~), > libpython3.13-dev, python3.13:any, qt6-5compat-dev (>= 6.5.0~), qt6-base-dev > (>= 6.5.0~),
Thanks, that's at least better that depending on the non-default version. > > Please try to avoid explicit Python versions in Build-Depends, you > > should be able to build-depend on "libpython3-dev, python3" (or > > even-better: "libpython3-all-dev, python3-all") > > Kdevelop is and IDE and has specific requirements regarding python versions. > The current version has the following in its CMakeLists.txt [1] : > find_package(Python3 3.4.3...<3.14 COMPONENTS Interpreter Development > REQUIRED) That sounds like it supports any default version between 3.4 and 3.14. Almost all Python packages are in a situation like that. They support a few older versions, and probably support future versions, but they don't know for sure, yet. In that situation, Build-Depending on python3-dev or python3-all-dev is perfectly reasonable to do. When we change the supported versions in the archive, either your package will just work, or it'll fail its tests and you'll get an FTBFS bug report. I don't see any reason why kdevelop needs 3.13 explicitly specified in its build-depends. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
