openttd-jgrpp: 0.64.2 -> 0.65.1#398135
Conversation
github-actions
bot
added
6.topic: games
r-ryantm
changed the title
r-ryantm
force-pushed
the
auto-update/openttd-jgrpp
branch
from
184f014 to
9091c67
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/openttd-jgrpp/versions. meta.homepage for openttd-jgrpp is: https://github.com/JGRennison/OpenTTD-patches meta.changelog for openttd-jgrpp is: https://github.com/JGRennison/OpenTTD-patches/blob/jgrpp-0.65.1/jgrpp-changelog.md 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.
|
|
2 participants
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/openttd-jgrpp/versions.
meta.homepage for openttd-jgrpp is: https://github.com/JGRennison/OpenTTD-patches
meta.changelog for openttd-jgrpp is: https://github.com/JGRennison/OpenTTD-patches/blob/jgrpp-0.65.0/jgrpp-changelog.md
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 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-reviewx86_64-linux✅ 1 package 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.