-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel tools pkg_tar fails on Fedora 39 #20211
Comments
Hi @neckbosov, Could you please provide complete steps to reproduce this issue? |
Hi @sgowroji, just set up some project which uses BTW found discussion on Google groups, so I'm not sure it's Bazel problem, but you definetely have more ways to investigate. |
@aiuto maybe you have some context on this. |
This is not for rules_pkg
That is the ancient (unsupported) pkg_tar from within Bazel itself. The current rules_pkg release should work with bazel 5.x, so just convert to that. |
"just" lol. Like it is that easy. I have the exact same issue and for reasons I cannot use the version of When I try I get this error:
I love bazel so much. |
Description of the bug:
After updating my host system to fedora 39 I notices failure of
pkg_tar
targets (from@bazel_tools
) in my project with the following traceback:I tried to fix it by installing
absl
to system (python3.six
was already installed) but it didn't help. The only workaround I found is to usepkg_tar
rule from@rules_pkg
. On Fedora 38 both ways worked well.Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Fedora 39
What is the output of
bazel info release
?release 5.4.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
Found similar issue #11663 but it's already closed.
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: