-
-
Notifications
You must be signed in to change notification settings - Fork 17.3k
python3Packages.flask-babel: 4.0.0 -> 4.1.0 #436306
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
python3Packages.flask-babel: 4.0.0 -> 4.1.0 #436306
Conversation
|
searxng seems to be a new failure? @SuperSandro2000 @999eagle do you know anything relevant? |
|
libretranslate is also something I have interest in. Let me see what I can find. |
f6eae21 to
6ecd2b1
Compare
This comment was marked as outdated.
This comment was marked as outdated.
|
Thanks! @NixOS/darwin-maintainers does anyone know if there is a simple Darwin fix to pull in? |
|
The test failure is because of python-babel/flask-babel#242 which I now fetched |
5f47a07 to
ede0a86
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python3Packages.flask-babel is: Adds i18n/l10n support to Flask applications
meta.homepage for python3Packages.flask-babel is: https://github.com/python-babel/flask-babel
meta.changelog for python3Packages.flask-babel is: https://github.com/python-babel/flask-babel/releases/tag/v4.1.0
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-reviewx86_64-linux⏩ 6 packages marked as broken and skipped:
❌ 6 packages failed to build:
✅ 22 packages built:
Maintainer pings
cc @matejc @timokau @7c6f434c @collares 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.