Conversation
a43405e to
1b54a5d
Compare
1b54a5d to
78bb9c7
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/toml11/versions. meta.description for toml11 is: TOML for Modern C++ meta.homepage for toml11 is: https://github.com/ToruNiina/toml11 Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ToruNiina/toml11/releases. meta.description for toml11 is: TOML for Modern C++ meta.homepage for toml11 is: https://github.com/ToruNiina/toml11 Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
78bb9c7 to
e695655
Compare
|
Do you remember @wegank what happened to mark this draft? |
|
From the scary "170 packages failed to build", it could be that some versions of Nix are incompatible with toml11 4.4.0. This is probably no longer the case three months later? I suppose a nixpkgs-review will be necessary to confirm this. |
|
I'll take a look. |
|
closing since #442682 was merged |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ToruNiina/toml11/releases.
meta.description for toml11 is: TOML for Modern C++
meta.homepage for toml11 is: https://github.com/ToruNiina/toml11
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.tests, if any, passedRebuild 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-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
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.
nixpkgs-reviewresultGenerated using
nixpkgs-review.Command:
nixpkgs-reviewx86_64-linux⏩ 1 package blacklisted:
❌ 160 packages failed to build:
✅ 15 packages built:
Maintainer pings
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.Add a 👍 reaction to pull requests you find important.