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
opentracing-cpp: 1.5.1 -> 1.6.0 #104567
opentracing-cpp: 1.5.1 -> 1.6.0 #104567
Conversation
This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package failed to build and are new build failure:
1 package built:
|
Still blocked on lightstep-tracer-cpp switching to the 1.6.x OpenTracing release. |
any progress on that? should we close this? |
looks like no updates for 3 years: lightstep/lightstep-tracer-cpp#215 |
lightstep/lightstep-tracer-cpp@0dcb916
|
Oh I just missed that commit. So can we maintain two versions of opentracing-cpp, 1.6.0 (or newer if any) and 1.5.1 for lightstep-tracer-cpp or mark lightstep-tracer-cpp broken (Perhaps this is a more aggressive option, but remove lightstep-tracer-cpp since it seems as if the package is not referenced by any other packages in this repository)? |
The problem is way worse: Opentracing was essentially abandoned. However, too many files inside Nixpkgs depend on it. I am trying to remove some of them, but others are machine-generated. |
Since this package is now rendered useless, I will merge it just because. |
@ofborg build opentracing-cpp |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/opentracing/opentracing-cpp/releases.
meta.description for opentracing-cpp is: "C++ implementation of the OpenTracing API"
meta.homepage for opentracing-cpp is: "https://opentracing.io"
meta.changelog for opentracing-cpp 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.0 with grep in /nix/store/7fp174pp3cpijmk5jwa61ymkbjr6qjax-opentracing-cpp-1.6.0
directory tree listing: https://gist.github.com/d6a511dd809235a63bd5d4c4fe39faf9
du listing: https://gist.github.com/bd93b26a1be2aaa18b6bfcf0a8d51d15
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 failed to build:
1 package built:
Maintainer pings
cc @rbvermaa for testing.