Package Details: bcc-tools-git 0.11.0.dev0+r1564.g3d21000a-1

Git Clone URL: https://aur.archlinux.org/bcc-git.git (read-only, click to copy)
Package Base: bcc-git
Description: BPF Compiler Collection - Tools - latest git code
Upstream URL: https://github.com/iovisor/bcc
Licenses: Apache
Conflicts: bcc-tools
Provides: bcc-tools
Submitter: mmlb
Maintainer: edh
Last Packager: edh
Votes: 7
Popularity: 0.000000
First Submitted: 2015-09-29 15:09 (UTC)
Last Updated: 2024-01-14 18:15 (UTC)

Dependencies (14)

Required by (3)

Sources (1)

Latest Comments

1 2 Next › Last »

dmitter commented on 2024-01-15 10:40 (UTC)

Thanks for the quick fix! I can confirm that the new version works fine now on my system.

edh commented on 2024-01-14 18:15 (UTC)

@dmitter Thanks for the report! This should be fixed now :)

dmitter commented on 2024-01-11 07:36 (UTC)

I have Python 3.11 installed on my system. It seems that version checking in Python is stricter now as the installation of this package failed for me with the following message:

$ yay -S bcc-git
[...]
/home/daniel/.cache/yay/bcc-git/src/bcc-git/src/cc/frontends/clang/kbuild_helper.cc:84:3: warning: multi-line comment [-Wcomment]
   84 |   // USERINCLUDE    := \
      |   ^
/home/daniel/.cache/yay/bcc-git/src/bcc-git/src/cc/frontends/clang/kbuild_helper.cc:93:3: warning: multi-line comment [-Wcomment]
   93 |   // LINUXINCLUDE    := \
      |   ^
[ 23%] Built target clang_frontend-objects
[ 23%] Building sdist for python3
Traceback (most recent call last):
  File "/home/daniel/.cache/yay/bcc-git/src/bcc-git/build/src/python/bcc-python3/setup.py", line 11, in <module>
    setup(name='bcc',
  File "/usr/lib/python3.11/site-packages/setuptools/__init__.py", line 103, in setup
    return distutils.core.setup(**attrs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 147, in setup
    _setup_distribution = dist = klass(attrs)
                                 ^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 314, in __init__
    self.metadata.version = self._normalize_version(self.metadata.version)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 350, in _normalize_version
    normalized = str(Version(version))
                     ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/packaging/version.py", line 200, in __init__
    raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: '0.11.0.r1561.gd272c0b7'
make[2]: *** [src/python/CMakeFiles/bcc_py_python3.dir/build.make:84: src/python/bcc-python3/dist/bcc-0.11.0.r1561.gd272c0b7.tar.gz] Error 1
make[1]: *** [CMakeFiles/Makefile2:1047: src/python/CMakeFiles/bcc_py_python3.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 23%] Linking CXX shared library libbcc_bpf.so
[ 23%] Built target bpf-shared
make: *** [Makefile:146: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: bcc-git-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
bcc-git - exit status 4

i.e. Python rejects the version identifier "0.11.0.r1561.gd272c0b7" as invalid as per their spec (see https://packaging.python.org/en/latest/specifications/version-specifiers/). I could make it work with the following diff:

diff --git a/PKGBUILD b/PKGBUILD
index 810599f..a2e5ec4 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,7 +5,7 @@

 pkgbase=bcc-git
 pkgname=('bcc-git' 'bcc-tools-git' 'python-bcc-git')

-pkgver=0.11.0.r951.gc65446b7
+pkgver=0.11.0.dev0+r951.gc65446b7
 pkgrel=1
 pkgdesc='BPF Compiler Collection - latest git code'
 arch=('x86_64')

edh commented on 2019-10-13 10:23 (UTC)

@emanuele-f The C bindings should work just fine in the bcc package. Hence, it is separate from python-bcc.

I agree that not having the tools in the PATH is kind of awkward but there are a number of names which would clash with standard Linux tools. Defining a sensible ordering in the PATH IMHO does not make sense and hence I just stick to what upstream has decided to do.

emanuele-f commented on 2019-10-13 09:58 (UTC)

Why python-bcc-git is optional? Tools will fail with "No module named 'bcc'" if that is not installed. It would also be useful to have the tools in the PATH, I had to check the .pkg.tar.gz contents to locate where the tools are installed.

osandov commented on 2019-08-28 19:02 (UTC)

The provides/conflicts directives should be fixed now. Let me know if anyone runs into issues.

gamanakis commented on 2019-08-28 03:21 (UTC)

Please fix the "provides" directive. Instead of bcc-git it should say bcc, otherwise other packages depending on bcc are broken (e.g. bpftrace).

iamazat commented on 2019-05-11 13:32 (UTC)

Maybe this package should provides bcc?

renyuneyun commented on 2018-07-10 08:47 (UTC)

There is a file clash with postfix because of /usr/share/man/man8/trace.8.gz . Probably this should be handled... (Though I can uninstall postfix for me case.)

edh commented on 2018-02-16 08:29 (UTC)

Thanks for the note. That was just a plain mistake, I indeed meant to direct the message at @osandov.

1 2 Next › Last »