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
mutt: 2.0.4 -> 2.0.5 #110449
mutt: 2.0.4 -> 2.0.5 #110449
Conversation
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
It contains a security fix for CVE-2021-3181. We should probably backport this commit: https://gitlab.com/muttmua/mutt/-/commit/4a2becbdb4422aaffe3ce314991b9d670b7adf17i, but I would wait for the more information. |
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 2 packages built:
|
@rnhmjoj why would we need to backport a commit from mutt if the release contains a security fix? |
@matthiasbeyer I mean backport to the NixOS 20.09. We can't simply bump the version to 2.0.4 because 2.0 has breaking changes. |
Agreed. Sad that the "1.y.z" branch of mutt is not maintained anymore... would be nice for security fixes like this. |
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 2 packages built:
|
I will stop contributing via the github UI now. It starts to annoy me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks all good.
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)