hello, in packaging Python 3.2, i've run into a strange situation regarding the shlib naming policy. Python's shared library is now called "libpython3.2m.so.1.0", "3.2" being python series and "m" a so-called ABI tag. This was part of an upstream attempt to provide a stable ABI for python modules, so we might be stuck with "libpython3.2m" for the next few years. Without the "m", the right name for the library package would be "libpython3_2-1_0". It seems logical that with it, library package would be named "libpython3_2m-1_0". However, the relevant rpmlint check insists the library be called "libpython3_2m1_0". Is this a bug in the rpmlint check, or is there some part of the policy saying that this is how the package should be called? thanks m. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org