https://bugzilla.redhat.com/show_bug.cgi?id=1887470
Bug ID: 1887470
Summary: Review Request: libtraceevent - library to parse raw
trace event formats
Product: Fedora
Version: rawhide
Status: NEW
Component: Package Review
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
Target Milestone: ---
Classification: Fedora
SPEC URL:
https://zsun.fedorapeople.org/pub/pkgs/libtraceevent/libtraceevent.spec
SRPM URL:
https://zsun.fedorapeople.org/pub/pkgs/libtraceevent/libtraceevent-0-0.1.20201009git5dd505f.fc32.src.rpm
Description:
Libtraceevent is a library to parse raw trace event formats.
Fedora Account System Username: zsun
Notes:
[ ]: Package does not own files or directories owned by other packages.
Note: Dirs in package are owned also by:
/usr/include/traceevent(trace-cmd-devel), /usr/lib64/traceevent(perf,
trace-cmd-libs), /usr/lib64/traceevent/plugins(perf, trace-cmd-libs)
This is intended. The aim of the upstream traceevent is to make this a shared
library to be consumed by perf, trace-cmd and others. I'm also the trace-cmd
packager and working on solving the dependency after this library is in Fedora.
The perf part will be ready when it's done in upstream kernel repo.
[ ]: SourceX tarball generation or download is documented.
Note: Package contains tarball without URL, check comments
Upstream do not provide tag or tarballs yet. I do have a comment on how to
generate the tarball. Once upstream have a tag I'll switch to use the tag.
RPMlint:
libtraceevent.x86_64: E: no-ldconfig-symlink /usr/lib64/libtraceevent.so.1.1.0
libtraceevent-devel.x86_64: W: no-documentation
libtraceevent-devel.x86_64: W: dangling-relative-symlink
/usr/lib64/libtraceevent.so.1 libtraceevent.so.1.1.0
I'm trying to follow the way glibc separates package, so the real file stays in
libtraceevent while symlink goes to -devel. If this is not the suggested way,
I'd like to know the proper way for it.
Various "shared-lib-without-dependency-information"
I did not find any information for this in the wiki. So if this need to be
fixed, I'd like to learn about the suggested fix.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
