Project

General

Profile

Actions

Bug #5653

closed

various rpmlint errors

Added by laforge over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
08/21/2022
Due date:
% Done:

100%


Description

The package fails to build on OpenSuSE tumbleweed with a variety of rpmlint errors, see:

[   17s] libosmo-pfcp.src: E: summary-too-long (Badness: 200) libosmo-pfcp: PFCP protocol encoding and decoding, and generic PFCP endpoint implementation
[   17s] The 'Summary:' must not exceed 79 characters.
[   17s] 
[   17s] libosmo-pfcp.src: E: summary-not-capitalized (Badness: 20) libosmo-pfcp: PFCP protocol encoding and decoding, and generic PFCP endpoint implementation
[   17s] Summary doesn't begin with a capital letter.
[   17s] 
[   17s] libosmo-gtlv-devel.x86_64: E: static-library-without-debuginfo /usr/lib64/libosmo-gtlv.a
[   17s] libosmo-pfcp-devel.x86_64: E: static-library-without-debuginfo /usr/lib64/libosmo-pfcp.a
[   17s] The static library doesn't contain any debuginfo. Binaries linking against
[   17s] this static library can't be properly debugged.
[   17s] 
[   17s] libosmo-gtlv0.x86_64: W: shlib-fixed-dependency osmocom-nightly = 202208210002
[   17s] libosmo-pfcp0.x86_64: W: shlib-fixed-dependency osmocom-nightly = 202208210002
[   17s] Your shared library package requires a fixed version of another package. The
[   17s] intention of the Shared Library Policy is to allow parallel installation of
[   17s] multiple versions of the same shared library, hard dependencies likely make
[   17s] that impossible. Please remove this dependency and instead move it to the
[   17s] runtime uses of your library.
[   17s] 
[   17s] libosmo-gtlv-devel.x86_64: E: no-changelogname-tag
[   17s] libosmo-gtlv0.x86_64: E: no-changelogname-tag
[   17s] libosmo-pfcp-devel.x86_64: E: no-changelogname-tag
[   17s] libosmo-pfcp0.x86_64: E: no-changelogname-tag
[   17s] libosmo-pfcp.src: E: no-changelogname-tag
[   17s] There is no changelog. Please insert a '%changelog' section heading in your
[   17s] spec file and prepare your changes file using e.g. the 'osc vc' command.
[   17s] 
[   17s] libosmo-pfcp.src: W: name-repeated-in-summary libosmo-pfcp
[   17s] The name of the package is repeated in its summary. Make the summary brief and
[   17s] to the point without including redundant information in it.
[   17s] 
[   17s] libosmo-gtlv-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/libosmo-gtlv.a
[   17s] libosmo-pfcp-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/libosmo-pfcp.a
[   17s] This archive does not contain a non-empty .text section.  The archive was not
[   17s] created with -ffat-lto-objects option.
[   17s] 
[   17s] libosmo-gtlv-devel.x86_64: W: invalid-url DistURL obs://osmocom/osmocom:nightly/openSUSE_Tumbleweed/c4a5df48c603de71dba7a111f5a3c57d-libosmo-pfcp
[   17s] libosmo-gtlv0.x86_64: W: invalid-url DistURL obs://osmocom/osmocom:nightly/openSUSE_Tumbleweed/c4a5df48c603de71dba7a111f5a3c57d-libosmo-pfcp
[   17s] libosmo-pfcp-devel.x86_64: W: invalid-url DistURL obs://osmocom/osmocom:nightly/openSUSE_Tumbleweed/c4a5df48c603de71dba7a111f5a3c57d-libosmo-pfcp
[   17s] libosmo-pfcp0.x86_64: W: invalid-url DistURL obs://osmocom/osmocom:nightly/openSUSE_Tumbleweed/c4a5df48c603de71dba7a111f5a3c57d-libosmo-pfcp
[   17s] libosmo-pfcp.src: W: invalid-url DistURL obs://osmocom/osmocom:nightly/openSUSE_Tumbleweed/c4a5df48c603de71dba7a111f5a3c57d-libosmo-pfcp
[   17s] ---------------- Badness 20227 exceeds threshold 999, aborting. ----------------
[   17s] Check time report (>1% & >0.1s):
[   17s]     Check                            Duration (in s)   Fraction (in %)  Checked files
[   17s]     TOTAL                                        0.1             100.0             26
[   17s] 
[   17s]  5 packages and 0 specfiles checked; 11 errors, 8 warnings, 20227 badness; has taken 0.1 s 

full log at https://obs.osmocom.org/package/live_build_log/osmocom:nightly/libosmo-pfcp/openSUSE_Tumbleweed/x86_64

I'm surprised that this has been failing all weeek long and it needs me to return back from holidays to have a look.


Related issues

Related to Cellular Network Infrastructure - Bug #5654: OBS errors for libosmo-pfcp, osmo-upf, osmo-hnbgwResolvedosmith08/22/2022

Actions
Actions #1

Updated by laforge over 1 year ago

https://gerrit.osmocom.org/c/libosmo-pfcp/+/29165 tries to fix some of them, please check if it works and investigate the other errors.

Errors like no .text section in .a file seem rather serious to me.

Actions #2

Updated by osmith over 1 year ago

  • Related to Bug #5654: OBS errors for libosmo-pfcp, osmo-upf, osmo-hnbgw added
Actions #3

Updated by osmith over 1 year ago

  • Assignee changed from neels to osmith

I'll look into this as part of #5654.

Actions #4

Updated by osmith over 1 year ago

  • % Done changed from 0 to 90

https://gerrit.osmocom.org/q/topic:pfcp-packaging

with these, it builds for nightly and latest.

Actions #5

Updated by osmith over 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)