https://bugzilla.suse.com/show_bug.cgi?id=1180377 https://bugzilla.suse.com/show_bug.cgi?id=1180377#c22 --- Comment #22 from Matej Cepl <mcepl@suse.com> --- (In reply to Andreas Taschner from comment #21)

I relayed that message to my customer, who asked for a verification of whether they have understood things correctly : <snip> But just to clarify this situation seems to be arising from indirect reference in the available python libraries. For example eventhough the user might not be using FPE directly, importing the lxml.etree seems to bring in this error.

Yes, the problem we had was only because all packages in SLE-15 were originally built against Python which had fpectl on, so they referred appropriate symbols in it. When the Python interpreter suddenly didn���t contain these symbols, they failed. When those same packages are build against Python interpreters without those symbols in the first place, everything works. Obviously, we have python-lxml working just fine in Factory, build against Python 3.8, which doesn���t have fpectl anymore. Nice explanation about what fpectl is, and why it is not needed (or why it might be actually harmful) is in the old version of fpectl module documentation at https://docs.python.org/3.6/library/fpectl.html . -- You are receiving this mail because: You are on the CC list for the bug.