Time to inform users that RHEL7 will be the last with python/liblvm2app library support.
1) Header files, etc will be removed from the next Fedora builds
2) We will need deprecation documentation (release note?)
3) Pull libraries from 7.5?
4) No support for these libraries beyond RHEL7
Just a note that our own lvm2-activation-generator for systemd (found in scripts/lvm2_activation_generator_systemd_red_hat.c) uses lvm2app to read the lvm2 config.
So we need to find an alternative for that. The only one at the moment I can think of quickly is to call something like 'system("/usr/sbin/lvmconfig --type current ...")'. The other option is to share the code somehow better so we can read the config in lvm2-activation-generator directly without a need to call external command.
We will just remove headers (and .so) from the devel sub package.
(In reply to Marian Csontos from comment #3)
> We will just remove headers (and .so) from the devel sub package.
Well, the .so is not in the devel subpackage, it's in lvm2-libs subpackage actually. So you'd remove the lvm2app altogher...
...as another alternative - we can add an option for vgchange (lvchange) -aay to exit immediately if lvmetad is running (and hence autoactivaiton works via pvscan -aay call from udev) and do the activation if lvmetad is not running, something like:
vgchange -aay --skip-if-lvmetad-running ....
Then we don't need the lvm2-activation-generator and we'd just add the units with vgchange calls directly and unconditionally.
(Of course, eventually, this should be covered by SID completely. So I mean this for the period of time we move to SID.)
# dnf repoquery --whatrequires lvm2-libs
So we need to check the collectd and glusterfs-server how they use the lvm2-libs.
# dnf repoquery --whatrequires lvm2-python3-libs
# dnf repoquery --whatrequires lvm2-python-libs
This bug is just about notifying users to prepare them for a future change. Discussion of the actual change should happen elsewhere.
We're not removing anything from the RHEL7.5 packages.
We could consider compile-time and/or run-time warnings - probably just compile-time.
I'm preparing the RHEL 7.5 Release Notes. Do we want to include a note about LVM libraries deprecation there?
If so, could you please give me more information about the impact of the deprecation and whether an alternative exists that users can switch to?
Marian, thanks for the draft doc text. I've edited it, trying to preserve all the technical information in place.
If you have any comments or suggestions regarding the doc text, please let me know. Otherwise, we're ready to publish it as it is.