[opensuse-factory] libevtlog
Hi, The libevtlog package is a dependency of syslog-ng. As far as I know no other package is using it. With syslog-ng version 3.11.1 libeventlog was merged into syslog-ng as having it as a separate package cause more confusion than good. I plan to update syslog-ng to 3.12.1 to resolve compile issues on Tumbleweed. How can I check if any other package uses libevtlog? If nothing, it is safe to drop it after syslog-ng 3.12.1 arrived to Tumbleweed. Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2017-11-29 at 14:52 +0100, Peter Czanik wrote:
Hi,
The libevtlog package is a dependency of syslog-ng. As far as I know no other package is using it. With syslog-ng version 3.11.1 libeventlog was merged into syslog-ng as having it as a separate package cause more confusion than good.
I plan to update syslog-ng to 3.12.1 to resolve compile issues on Tumbleweed.
How can I check if any other package uses libevtlog? If nothing, it is safe to drop it after syslog-ng 3.12.1 arrived to Tumbleweed.
osc whatdependson openSUSE:Factory libevtlog standard x86_64
hi Peter, libevtlog : syslog-ng So at this moment, syslog-ng is indeed the only consumer. cheers Dominique
Hi, On 11/29/2017 02:55 PM, Dominique Leuenberger / DimStar wrote:
How can I check if any other package uses libevtlog? If nothing, it
is safe to drop it after syslog-ng 3.12.1 arrived to Tumbleweed. hi Peter,
osc whatdependson openSUSE:Factory libevtlog standard x86_64 libevtlog : syslog-ng
So at this moment, syslog-ng is indeed the only consumer.
OK. In this case I update the syslog-ng package to 3.12.1, merge fixes from Richard ( https://build.opensuse.org/request/show/544690# ), test the package and submit it. Once it's in, we can drop libevtlog. (libevtlog is a library developed by the guy / company as syslog-ng) Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Wed, Nov 29, 2017 at 3:17 PM, Peter Czanik <peter@czanik.hu> wrote:
OK. In this case I update the syslog-ng package to 3.12.1, merge fixes from Richard ( https://build.opensuse.org/request/show/544690# ), test the package and submit it. Once it's in, we can drop libevtlog. (libevtlog is a library developed by the guy / company as syslog-ng)
This conflict was also found by repo-check: https://build.opensuse.org/project/show/openSUSE:Factory:Staging:adi:67 Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2017-11-30 at 08:37 +0100, Peter Czanik wrote:
Hi,
On Wed, Nov 29, 2017 at 3:17 PM, Peter Czanik <peter@czanik.hu> wrote:
OK. In this case I update the syslog-ng package to 3.12.1, merge fixes from Richard ( https://build.opensuse.org/request/show/544690# ), test the package and submit it. Once it's in, we can drop libevtlog. (libevtlog is a library developed by the guy / company as syslog- ng)
This conflict was also found by repo-check: https://build.opensuse.org/project/show/openSUSE:Factory:Staging:adi: 67
For the public record (I mentioned the same on the submit request): Repo checker is right. The packaging guidelines about 'merging packages' was not adhered to: https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a_package Once this is adhered to, r-c won't complain and let this package pass. Cheers, Dominique
Hi, On 11/30/2017 03:48 PM, Dominique Leuenberger / DimStar wrote:
On Thu, 2017-11-30 at 08:37 +0100, Peter Czanik wrote:
Hi,
On Wed, Nov 29, 2017 at 3:17 PM, Peter Czanik <peter@czanik.hu> wrote:
OK. In this case I update the syslog-ng package to 3.12.1, merge fixes from Richard ( https://build.opensuse.org/request/show/544690# ), test the package and submit it. Once it's in, we can drop libevtlog. (libevtlog is a library developed by the guy / company as syslog- ng) This conflict was also found by repo-check: https://build.opensuse.org/project/show/openSUSE:Factory:Staging:adi: 67 For the public record (I mentioned the same on the submit request): Repo checker is right.
The packaging guidelines about 'merging packages' was not adhered to:
https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a_package
Once this is adhered to, r-c won't complain and let this package pass. OK. So I should revoke this request.
Is it OK if I modify packages this way? Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13 and: Provides: libevtlog-devel = 0.2.13 Obsoletes: libevtlog-devel <= 0.2.13 Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2017-12-01 at 09:01 +0100, Peter Czanik wrote:
For the public record (I mentioned the same on the submit request): Repo checker is right.
The packaging guidelines about 'merging packages' was not adhered to:
https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a_pac kage
Once this is adhered to, r-c won't complain and let this package pass.
OK. So I should revoke this request.
Is it OK if I modify packages this way?
Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13
This one no: the right thing here is to also split libevtlog0 in the new souece package (syslog-ng), according to the shared library packaging policy. Then, as the name stays the same, no provides/obsoletes are needed
and:
Provides: libevtlog-devel = 0.2.13 Obsoletes: libevtlog-devel <= 0.2.13
This one yes; alternatively you could also split out a libevtlog-devel package out of the syslog-ng source build; but since there is no consumer (yet?) this might be overkill Cheers, Dominique
On 12/01/2017 09:06 AM, Dominique Leuenberger / DimStar wrote:
For the public record (I mentioned the same on the submit request): Repo checker is right.
The packaging guidelines about 'merging packages' was not adhered to:
https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a_pac kage
Once this is adhered to, r-c won't complain and let this package pass. OK. So I should revoke this request.
Is it OK if I modify packages this way?
Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13 This one no: the right thing here is to also split libevtlog0 in the new souece package (syslog-ng), according to the shared library
On Fri, 2017-12-01 at 09:01 +0100, Peter Czanik wrote: packaging policy. Then, as the name stays the same, no provides/obsoletes are needed
But why, if no other package is using it? (history: originally it was developed as a generic logging library for RFC 5424 syslog, but as actually syslog-ng was the only user for many years, it was merged) Bye, CzP
and:
Provides: libevtlog-devel = 0.2.13 Obsoletes: libevtlog-devel <= 0.2.13 This one yes; alternatively you could also split out a libevtlog-devel package out of the syslog-ng source build; but since there is no consumer (yet?) this might be overkill
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2017-12-01 at 10:30 +0100, Peter Czanik wrote:
On 12/01/2017 09:06 AM, Dominique Leuenberger / DimStar wrote:
On Fri, 2017-12-01 at 09:01 +0100, Peter Czanik wrote:
For the public record (I mentioned the same on the submit request): Repo checker is right.
The packaging guidelines about 'merging packages' was not adhered to:
https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a _pac kage
Once this is adhered to, r-c won't complain and let this package pass.
OK. So I should revoke this request.
Is it OK if I modify packages this way?
Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13
This one no: the right thing here is to also split libevtlog0 in the new souece package (syslog-ng), according to the shared library packaging policy. Then, as the name stays the same, no provides/obsoletes are needed
But why, if no other package is using it? (history: originally it was developed as a generic logging library for RFC 5424 syslog, but as actually syslog-ng was the only user for many years, it was merged)
There are header files and a public library - hence it has to adhere to the shared library packaging policy. The fact that nothing else uses it yet does not justify to ignore this specific packaging guideline. libevtlog.so.0 has to live in the libevtlog0 package (which you can generate from the syslog-ng sources, no problem with that) Cheers Dominique
On 12/01/2017 10:44 AM, Dominique Leuenberger / DimStar wrote:
On 12/01/2017 09:06 AM, Dominique Leuenberger / DimStar wrote:
For the public record (I mentioned the same on the submit request): Repo checker is right.
The packaging guidelines about 'merging packages' was not adhered to:
https://en.opensuse.org/openSUSE:Package_dependencies#Merging_a _pac kage
Once this is adhered to, r-c won't complain and let this package pass. OK. So I should revoke this request.
Is it OK if I modify packages this way?
Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13 This one no: the right thing here is to also split libevtlog0 in
On Fri, 2017-12-01 at 09:01 +0100, Peter Czanik wrote: the new souece package (syslog-ng), according to the shared library packaging policy. Then, as the name stays the same, no provides/obsoletes are needed But why, if no other package is using it? (history: originally it was developed as a generic logging library for RFC 5424 syslog, but as actually syslog-ng was the only user for many years, it was merged) There are header files and a public library - hence it has to adhere to
On Fri, 2017-12-01 at 10:30 +0100, Peter Czanik wrote: the shared library packaging policy. The fact that nothing else uses it yet does not justify to ignore this specific packaging guideline.
libevtlog.so.0 has to live in the libevtlog0 package (which you can generate from the syslog-ng sources, no problem with that) OK, changed the spec file but ran into a few problems. How can I make sure that the resulting package is called libevtlog0 instead of syslog-ng-libevtlog0 and add the necessary post scriptlets? Now I get:
[ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig-postin (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %post scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig-postun (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %postun scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: shlib-policy-name-error (Badness: 10000) libevtlog-3_12-0 [ 173s] Your package contains a single shared library but is not named after its [ 173s] SONAME. Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2017-12-01 at 11:51 +0100, Peter Czanik wrote:
[ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig- postin (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %post scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig- postun (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %postun scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: shlib-policy-name-error (Badness: 10000) libevtlog-3_12-0 [ 173s] Your package contains a single shared library but is not named after its [ 173s] SONAME.
Bye, CzP
%package -n libevtlog0 instead of %package libevtlog0 Cheers Dominique
On Fri, 2017-12-01 at 11:51 +0100, Peter Czanik wrote:
[ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig- postin (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %post scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig- postun (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %postun scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: shlib-policy-name-error (Badness: 10000) libevtlog-3_12-0 [ 173s] Your package contains a single shared library but is not named after its [ 173s] SONAME. Bye, CzP %package -n libevtlog0 instead of %package libevtlog0 Thanks. Unfortunately it sill does not resolve the problem, as the name of the library is now tied to the syslog-ng version. So there is no more
On 12/01/2017 11:54 AM, Dominique Leuenberger / DimStar wrote: libevtlog0 but libevtlog-3_12-0 [ 153s] libevtlog0.x86_64: E: shlib-policy-name-error (Badness: 10000) libevtlog-3_12-0 [ 153s] Your package contains a single shared library but is not named after its [ 153s] SONAME. Does it mean that I have to rename the package to libevtlog-3_12-0 and add: Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13 Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2017-12-01 at 12:19 +0100, Peter Czanik wrote:
On 12/01/2017 11:54 AM, Dominique Leuenberger / DimStar wrote:
On Fri, 2017-12-01 at 11:51 +0100, Peter Czanik wrote:
[ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig- postin (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %post scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: library-without-ldconfig- postun (Badness: 300) /usr/lib64/libevtlog-3.12.so.0.0.0 [ 173s] This package contains a library and provides no %postun scriptlet containing a [ 173s] call to ldconfig. [ 173s] [ 173s] syslog-ng-libevtlog0.x86_64: E: shlib-policy-name-error (Badness: 10000) libevtlog-3_12-0 [ 173s] Your package contains a single shared library but is not named after its [ 173s] SONAME. Bye, CzP
%package -n libevtlog0 instead of %package libevtlog0
Thanks. Unfortunately it sill does not resolve the problem, as the name of the library is now tied to the syslog-ng version. So there is no more libevtlog0 but libevtlog-3_12-0
[ 153s] libevtlog0.x86_64: E: shlib-policy-name-error (Badness: 10000) libevtlog-3_12-0 [ 153s] Your package contains a single shared library but is not named after its [ 153s] SONAME.
Does it mean that I have to rename the package to libevtlog-3_12-0
yes
and add: Provides: libevtlog0 = 0.2.13 Obsoletes: libevtlog0 <= 0.2.13
no; shared library packages are not obsoleting other shared libraries; and the provides would be wrong, as the library is no logner called libevtlog.so.0 apparently and as such does not provide those capabilities. I wrongly assumed that the library would still be called libevtlog.so.0; which is apparently not true anymore. Apologies for misleading you. Cheers Dominique
participants (2)
-
Dominique Leuenberger / DimStar -
Peter Czanik