[opensuse-factory] libnl-1_1 to libnl1
For security:netfilter/libnl-1_1, rpmlint informs me that libnl-1_1.x86_64: W: shlib-legacy-policy-name-error libnl1 Your shared library package is not named after its SONAME, but it has been added to the list of legacy exceptions. Please do not rename the package until SONAME changes, but if you have to rename it for another reason, make sure you name it correctly. Is there a reason not to rename libnl-1_1 to libnl1 now? (There is never going to be a SONAME bump.) AFAICS, it's just an Obsolete-Provides away. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 05.06.2013 16:06, schrieb Jan Engelhardt:
For security:netfilter/libnl-1_1, rpmlint informs me that
libnl-1_1.x86_64: W: shlib-legacy-policy-name-error libnl1 Your shared library package is not named after its SONAME, but it has been added to the list of legacy exceptions. Please do not rename the package until SONAME changes, but if you have to rename it for another reason, make sure you name it correctly.
Is there a reason not to rename libnl-1_1 to libnl1 now? (There is never going to be a SONAME bump.) AFAICS, it's just an Obsolete-Provides away.
I'm afraid I miss something - your question is asked in a way that I wonder "why not?". So why was it named libnl-1_1 originally? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2013-06-05 17:45, Stephan Kulow wrote:
For security:netfilter/libnl-1_1, rpmlint informs me that
libnl-1_1.x86_64: W: shlib-legacy-policy-name-error libnl1 Your shared library package is not named after its SONAME, but it has been added to the list of legacy exceptions. Please do not rename the package until SONAME changes, but if you have to rename it for another reason, make sure you name it correctly.
Is there a reason not to rename libnl-1_1 to libnl1 now? (There is never going to be a SONAME bump.) AFAICS, it's just an Obsolete-Provides away.
I'm afraid I miss something - your question is asked in a way that I wonder "why not?". So why was it named libnl-1_1 originally?
Once upon a time, libnl lived in GNOME:Factory and produced a libnl.binrpm. Why the GNOME people did not start using the shlib package naming, I do not know. This was carried as-is into security:netfilter/libnl-1_1. It is just now that I noticed that libnl-1.1 (superseded by next version since 2010) has received some late stable updates and therefore saw the buildlog again. So I suppose I can just go ahead and make libnl-1_1.srcrpm generate a libnl1.binrpm as intended. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Jan Engelhardt -
Stephan Kulow