Bug#948041: marked as done (libbpf-dev: please build from https://github.com/libbpf/libbpf)
Your message dated Sat, 11 Apr 2020 22:00:23 +0000
with message-id <E1jNOAp-0005PY-16@fasolo.debian.org>
and subject line Bug#948041: fixed in libbpf 0.0.6-1
has caused the Debian Bug report #948041,
regarding libbpf-dev: please build from https://github.com/libbpf/libbpf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
948041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948041
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-kernel@lists.debian.org
libbpf source has moved to a separate github repo but keeps the kernel
as the true/first source, and updating github repo when release is ready.
In Steve's word the problem they faced is:
> The problem I'm now having is that I'm looking at fixing and updating
> some of the code in this library, and since library versioning is
> critical for applications that depend on it, we need to have a way to
> update the versions, and this does not correspond with the Linux
> versions.
So, looking at libbpf github repo at [1], I can see libbpf has already
released v0.0.6 but we only have v0.0.5 in Debian and there is no way
to update that unless the kernel is updated to v5.5+. And looking at
the kernel repo I can see libbpf people are working on v0.0.7. The full
discussion is at [2].
Do we package libbpf from their github repo independent of the kernel
update? Then we will need to remove the libbpf building bits from the
Debian kernel source and create a separate package for libbpf.
And so, it will be great if kernel team will like to package and maintain
it, if not, then I will be happy to do it. Please reject this bug report
if you think libbpf should not be done separately and should live inside
kernel source package.
[1]. https://github.com/libbpf/libbpf
[2]. https://lore.kernel.org/lkml/20200102234950.GA14768@krava/
--
Regards
Sudip
--- End Message ---
--- Begin Message ---
Source: libbpf
Source-Version: 0.0.6-1
Done: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
We believe that the bug you reported is fixed in the latest version of
libbpf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 948041@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sudip Mukherjee <sudipm.mukherjee@gmail.com> (supplier of updated libbpf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 11 Apr 2020 16:12:37 +0100
Binary: libbpf-dev libbpf0 libbpf0-dbgsym
Source: libbpf
Architecture: amd64 source
Version: 0.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Changed-By: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Closes: 948041
Description:
libbpf-dev - eBPF helper library (development files)
libbpf0 - eBPF helper library (shared library)
Changes:
libbpf (0.0.6-1) unstable; urgency=medium
.
* Package from github. (Closes: #948041)
Checksums-Sha1:
8c294e7a3b26ba7ce90830ce308a26a24fb172b5 1860 libbpf_0.0.6-1.dsc
a8f6bca240c05aa5049bc8b3a20962ff3916c1e4 213791 libbpf_0.0.6.orig.tar.gz
4f6d47ba0e62f7b06a5ae262e16c0c7354edcdab 4396 libbpf_0.0.6-1.debian.tar.xz
f578732ea7a202a5ac716eb4d81cb2fc921f6e13 6622 libbpf_0.0.6-1_source.buildinfo
b8ff39d23b4f4e1c14ba3851667bc1ced862da7d 103984 libbpf-dev_0.0.6-1_amd64.deb
2558fadde7a47a36de557845ea1fd3bf4c77e126 212184 libbpf0-dbgsym_0.0.6-1_amd64.deb
069a3ad42475c9e90d4b98d265cc81c4c8adfaa4 64296 libbpf0_0.0.6-1_amd64.deb
35bca1928f72843b97ea91a742ab411443d3739f 5058 libbpf_0.0.6-1_amd64.buildinfo
Checksums-Sha256:
b9a8bbbfa990399d256f644c9fcad09d1017c8586b3c58fa59ca60c9011ddecf 1860 libbpf_0.0.6-1.dsc
dbed8304077699fd59b0271545ac5923a6e0581db4ef90d6124efa6fe9df84c1 213791 libbpf_0.0.6.orig.tar.gz
afd708b245a14b40ce5f5d74478644bd8dc785b56d3add90c7455232d36602f5 4396 libbpf_0.0.6-1.debian.tar.xz
8d7ccde1b23ce020c72876bb6753e850736afefc35d8583239e4bd93d37e80f8 6622 libbpf_0.0.6-1_source.buildinfo
ae83a5140205808b48a6de35b1d7314c631a358addf689994f37d418abf4c671 103984 libbpf-dev_0.0.6-1_amd64.deb
b914744e8f0b955ee1cb4676c4b62be69260df8b501109faccf7633a5bef9408 212184 libbpf0-dbgsym_0.0.6-1_amd64.deb
b460828dd02f2f96d18f735edf78aaaf020c36e64f9cedd0e6a2c6c93c3efe31 64296 libbpf0_0.0.6-1_amd64.deb
ffdad9e1040a83d4f3511fe3ab069cddd614d63eb06ebc1322387cf431f1657d 5058 libbpf_0.0.6-1_amd64.buildinfo
Files:
8a7cbf5a4b90b2bc5897b787e5fdbd62 1860 libs optional libbpf_0.0.6-1.dsc
73c12c58350bc348907aef564ebd8d81 213791 libs optional libbpf_0.0.6.orig.tar.gz
b67dfcc294200add560b8e4b0e3554ea 4396 libs optional libbpf_0.0.6-1.debian.tar.xz
68a5d8fe6bece30b0519afe04d77c33f 6622 libs optional libbpf_0.0.6-1_source.buildinfo
72eaefec9d7a3635ac72357a25e55891 103984 libdevel optional libbpf-dev_0.0.6-1_amd64.deb
2303b8107ae1e0a573d7ed8de9a755ff 212184 debug optional libbpf0-dbgsym_0.0.6-1_amd64.deb
943e62575a89d20b5a5c04b4b18a2482 64296 libs optional libbpf0_0.0.6-1_amd64.deb
f804aec363c5f5ef192e9ec1aba24f6e 5058 libs optional libbpf_0.0.6-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl6R4hoACgkQ57/I7JWG
EQnqpA//S0dvBBWWf7IAq6qZFfrTGU9M7ur7sWKFWr/9PdtT/yQiuimUaAurIp5/
4VY971n0R/UJ4cB5Z96yMCxftKy+o97rVDV789cua2w4rulb/D2/vXS5+hafN89r
4iPYLry1/CcWCdmwuiWJRqRdo/lqozos3i2dMbVizS/oztX0hFmqW0CYe0Nbj8J3
cCns5YfsNioTRS5Cq+AfMySk9j7uEgn1sb8A2Zphqhn57aCRWs93L8s29yhoaQsH
1hC+kL6/GCtPUbcBZvCdMzNkfMdrZpLvv8oHhawaXyqKyafIJtoSm52gMRoX+q/4
JdBSDmE9XwxpRkNzw/i+frVWvp4QVgjjLteAAGvuEB9aiMxe3PUSn/JknWDFFntg
NYxi/CRNN2SefHjExiDep2bhxsrLerF+X0LQYVeZMZigTzuXlL+I9zxaBwIpMlHW
11/wRYR1jRqaybIy8kR3zFl/Sr9ZwVQTFlYoJgECoXxuMyG9Op78ApXu2rtOyWBw
a7cNSGhMO0ZY+gvcs4WwlVhZ79L0Wv67YY15mCaUjCY33zyQPNe3qEE4pk4I7ajS
BqpIceeGoKTfadtNfhPaA01YR9MozAFk21RXKxBPH+1thqEgKiRvraPF1aNEo9bb
0xFgLNMOFehN2MJR6Np9qcrd23B7mTnDHmcTChMuRyxgp0cHTLg=
=fRIL
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: