Skip to content
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

pythonPackages: trezor: 0.10.2 -> 0.11.1 #52741

Merged
merged 1 commit into from Jan 23, 2019
Merged

Conversation

prusnak
Copy link
Member

@prusnak prusnak commented Dec 23, 2018

Motivation for this change

Version update

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@prusnak
Copy link
Member Author

prusnak commented Dec 26, 2018

Don't merge yet, I'll amend the PR to update to upcoming 0.11.1

@prusnak prusnak force-pushed the python-trezor branch 2 times, most recently from 68281ae to 66b17f1 Compare January 2, 2019 11:50
@prusnak prusnak changed the title pythonPackages: trezor: 0.10.2 -> 0.11.0 pythonPackages: trezor: 0.10.2 -> 0.11.1 Jan 2, 2019
@prusnak
Copy link
Member Author

prusnak commented Jan 2, 2019

Amended. Good to merge.

@prusnak
Copy link
Member Author

prusnak commented Jan 9, 2019

@dotlambda Can you please help with the build failure? I think this is a false positive.

@dotlambda
Copy link
Member

@GrahamcOfBorg eval

@prusnak
Copy link
Member Author

prusnak commented Jan 10, 2019

@dotlambda addressed your comments in c220f4c, thanks for the hints!

@prusnak
Copy link
Member Author

prusnak commented Jan 22, 2019

ping @FRidh


# build requires UTF-8 locale
LANG = "en_US.UTF-8";
LOCALE_ARCHIVE = "${glibcLocales}/lib/locale/locale-archive";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is LOCaLE_ARCHIVE still required?

Copy link
Member Author

@prusnak prusnak Jan 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not for master, I can even remove glibcLocales from nativeBuildInputs

When I backport this patch to release-18.09 branch I need to keep glibcLocales in nativeBuildInputs but the line with LOCALE_ARCHIVE can go away.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason for this to be backported?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of them:

  1. we add a lot of features into Trezor and these are not accessible if a user has an older version of python-trezor leading to frustration
  2. I assume NixPkgs Electrum maintainers don't backport security patches individually, but rather the whole package is being updated to the newest stable release. This release might already be depending on the new python-trezor package, using the new API, etc. so it makes sense to upgrade the whole package for python-trezor too.

@Mic92
Copy link
Member

Mic92 commented Jan 23, 2019

@GrahamcOfBorg build python37Packages.keepkey python37Packages.trezor python37Packages.trezor_agent

@Mic92 Mic92 merged commit 20343f0 into NixOS:master Jan 23, 2019
@prusnak prusnak deleted the python-trezor branch January 23, 2019 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants