-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strict version dependencies for debian packages #1770
Comments
cc @drzaeus77 |
We should definitely make sure scripts and the library are from the same version...... |
bobrik
added a commit
to bobrik/bcc
that referenced
this issue
Jun 23, 2018
CrackerCat
pushed a commit
to CrackerCat/bcc
that referenced
this issue
Jul 31, 2024
…ovisor#1848) * Strict version dependencies for debian packages, closes iovisor#1770 * Use correct description for libbcc-examples debian package
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have:
We upgraded
bcc-tools
(it's the package end users care about) and it broke, because APIs changed inlibbcc
. I think we should require the same package version for all packages to avoid this.The text was updated successfully, but these errors were encountered: