Bug 1330804

Summary:	rpmlint's only-non-binary-in-usr-lib is too vague
Product:	[Fedora] Fedora	Reporter:	Andy Lutomirski <luto>
Component:	rpmlint	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	kevin, tcallawa, tmz, twoerner, ville.skytta
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-29 16:55:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andy Lutomirski 2016-04-27 01:48:18 UTC

I'm doing a review (bug 1040243), and rpmlint says:

capnproto-devel.x86_64: W: only-non-binary-in-usr-lib

This is singularly unhelpful.  What is the alleged binary in /usr/lib?  Other rpmlint warnings about contents of rpms at least tell me what the problematic file is.

FWIW, the actual contents of /usr/lib64 are:

/usr/lib64/libcapnp-rpc.so
/usr/lib64/libcapnp.so
/usr/lib64/libcapnpc.so
/usr/lib64/libkj-async.so
/usr/lib64/libkj.so
/usr/lib64/pkgconfig/capnp-rpc.pc
/usr/lib64/pkgconfig/capnp.pc

all of these are either symlinks or files without x flags set.

Comment 1 Andy Lutomirski 2016-04-27 02:04:29 UTC

I mean bug 1328968.  I faked myself out.

Comment 2 Ville Skyttä 2016-04-27 06:48:25 UTC

There is no single problematic file, this message is about ALL files in the package in /usr/lib(64) being NON binary. See also (although that's not a very good explanation either):

$ rpmlint -I only-non-binary-in-usr-lib

I suppose rpmlint should be smarter about the typical *.so symlink case, https://github.com/rpm-software-management/rpmlint/issues/73

(I suggest closing this as upstream, but will leave that to spot in case you want to track it here.)

Comment 3 Fedora End Of Life 2016-11-25 07:28:51 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.