python3Packages.coloraide: 6.2 -> 7.0#478631
Conversation
edd94b2 to
05bde15
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for python3Packages.coloraide is: Library to aid in using colors meta.homepage for python3Packages.coloraide is: https://github.com/facelessuser/coloraide 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.
|
|
@9999years Looks like |
|
Yes this is a known upstream issue: IIRC this hydra failure has bothered people before, so here's a fix: |
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python3Packages.coloraide is: Library to aid in using colors
meta.homepage for python3Packages.coloraide is: https://github.com/facelessuser/coloraide
Updates performed
To inspect upstream changes
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 the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached 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-review --extra-nixpkgs-config '{ allowBroken = false; }'Commit:
edd94b2c570e59f946f14063fd6ba0b8acfb503cx86_64-linux✅ 10 packages built:
Maintainer pings
cc @9999years @djacu for testing.
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.