Babeltrace updates and Python modules#285681
Closed
hacker1024 wants to merge 7 commits intoNixOS:masterfrom
Closed
Babeltrace updates and Python modules#285681hacker1024 wants to merge 7 commits intoNixOS:masterfrom
hacker1024 wants to merge 7 commits intoNixOS:masterfrom
Conversation
github-actions
bot
added
the
6.topic: python
Member
Author
|
Hmm, I'm not sure how this would fit into the |
hacker1024
force-pushed
the
package/python-babeltrace
branch
2 times, most recently
from
7243eda to
60ddae2
Compare
hacker1024
changed the title
hacker1024
changed the title
ofborg
bot
added
10.rebuild-darwin: 1-10
Member
|
There's some options:
What all of these have in common is that the different versions are somehow linked together. Thete might be other ways of doing it though :) |
Member
Author
I have attempted to do this, but it doesn't seem to be passing? |
Member
|
Ahh yeah sorry, I forgot to mention that the CI check has a false positive! It will be fixed once #285089 is used in CI, but for now you can just ignore the failing CI. It looks fine as is! |
Member
|
The PR to fix the |
Separate from babeltrace 1.x as "the Babeltrace 2 project is completely independent from Babeltrace 1". https://github.com/efficios/babeltrace/releases/tag/v2.0.0
A new attribute overriding babeltrace2 is created, rather than enabling Python support in babeltrace2 itself, in order to reduce the closure size and leave babeltrace2 Python-version-agnostic.
…babeltracePackages
…of PYTHON environment variable
hacker1024
force-pushed
the
package/python-babeltrace
branch
from
301b381 to
8831cd4
Compare
Member
Author
Contributor
|
Result of 6 packages marked as broken and skipped:
18 packages failed to build:
41 packages built:
|
Contributor
|
I fixed build failures with Python 3.12. The needed changes are in my branch, which is rebased to It seems that the failures of |
13 tasks
Contributor
|
So I created a draft PR from my branch and run |
Member
Author
|
Thanks @wentasah, I'm happy to close this PR in favour of yours if that works for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
This PR adds the Babeltrace 2 package along with its Python bindings. It is "completely independent from Babeltrace 1".
It also updates Babeltrace 1 to 1.5.11 (which mainly improves compatibility with newer Python and dependency versions) and adds a derivation for its Python bindings as well.
Cross-compilation (targeting aarch64-linux on x86_64-linux) has been tested.
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.
@bjornfor