https://bugzilla.redhat.com/show_bug.cgi?id=1745478
Mattia Verga changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #12 from Gwyn Ciesla ---
(fedscm-admin): The Pagure repository was created at
https://src.fedoraproject.org/rpms/libbpf
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #11 from Jiri Olsa ---
thanks, requesting repo in here:
https://pagure.io/releng/fedora-scm-requests/issue/17074
jirka
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
Dan Horák changed:
What|Removed |Added
Flags|fedora-review? |fedora-review+
--- Comment #10 from Dan
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #9 from Jiri Olsa ---
(In reply to Dan Horák from comment #8)
> further comments
> - missing BuildRequires: gcc
> - fails to rebuild on ppc64le, because it installs the libs into /usr/lib/ -
>
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #8 from Dan Horák ---
further comments
- missing BuildRequires: gcc
- fails to rebuild on ppc64le, because it installs the libs into /usr/lib/ -
https://github.com/libbpf/libbpf/blob/master/src/Makefile#L57 is wrong
- distro-wide
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #7 from Jiri Olsa ---
(In reply to Dan Horák from comment #1)
> first round of comments
> - drop Group: - it's ignored
> - drop Packager: - filled by the build system
> - drop %clean - rpmbuild does it automagically
> - drop all
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #6 from Jiri Olsa ---
(In reply to Iñaki Ucar from comment #5)
> (In reply to Jiri Olsa from comment #3)
> > however, upstream team decided to keep and maintain GitHub libbpf
> > sources (which are regirarly sync from kernel tree)
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #5 from Iñaki Ucar ---
(In reply to Jiri Olsa from comment #3)
> however, upstream team decided to keep and maintain GitHub libbpf
> sources (which are regirarly sync from kernel tree) to maintain
> compatibility in between
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #4 from Dan Horák ---
For the record, it was Jiri who introduced the libbpf subpackage in
kernel-tools.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
--- Comment #3 from Jiri Olsa ---
(In reply to Iñaki Ucar from comment #2)
> Why is this superseding libbpf in kernel-tools? Won't it break compatibility
> with the official kernel?
>
> Adding the maintainer of kernel-tools to the loop.
the
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
Iñaki Ucar changed:
What|Removed |Added
CC||i.uca...@gmail.com,
|
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
Dan Horák changed:
What|Removed |Added
Flags||fedora-review?
--
You are receiving
https://bugzilla.redhat.com/show_bug.cgi?id=1745478
Dan Horák changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
14 matches
Mail list logo
