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
fluent-bit: 1.6.0 -> 1.6.2 #102057
fluent-bit: 1.6.0 -> 1.6.2 #102057
Conversation
Result of 1 package failed to build:
|
@SuperSandro2000 if it's broken currently on master, we should just make this a linux only package. Do you mind trying to build it on master? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already broken in 1.6.0 and adding luajit does not fix the build error described in #102556. |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/fluent/fluent-bit/releases.
meta.description for fluent-bit is: "Log forwarder and processor, part of Fluentd ecosystem"
meta.homepage for fluent-bit is: "https://fluentbit.io"
meta.changelog for fluent-bit is: ""
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 1.6.2 with grep in /nix/store/n9lvjpg1by1vdxziw2qsjyrinqkjb1fi-fluent-bit-1.6.2
directory tree listing: https://gist.github.com/2803cc0bf981a9484ccc9ba74450a4e0
du listing: https://gist.github.com/a83e75570a97f6a52ced6d27429c5ca1
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
11 package built:
Maintainer pings
cc @samrose for testing.