libroot-python-dev package required for non-development use of PyROOT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
root-system (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libroot-python5.18
Installing the libroot-python metapackage, or a versioned instantiation such as libroot-python5.18, does not produce a usable PyROOT system: libroot-python-dev is required to actually provide the ROOT.py file, etc., without which PyROOT can't be used at all.
The conventional package behaviour is that -dev packages are only needed for development on the package itself, or for installation of C/C++ headers: the libroot-python-dev package does contain some headers, but also contains the .py files needed for *non-development* use of PyROOT. Seems to me that these .py files should be provided by the libroot-pythonXXX packages along with the compiled libraries that they load... without this, libroot-python(XXX) are pretty useless packages!
Changed in root-system (Ubuntu): | |
status: | Fix Committed → Fix Released |
will fix in 5.34.01-1