Switch Nix packaging to use mach-nix #1175
No reviewers
Labels
No Label
Benchmarking and Performance
HTTP Storage Protocol
Nevow Removal
Python 3 Porting
not-for-merge
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tahoe-lafs/tahoe-lafs#1175
Loading…
Reference in New Issue
No description provided.
Delete Branch "3867.mach-nix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3867
Coverage decreased (-0.02%) to 95.689% when pulling
9ba17ba8d1
on 3867.mach-nix into6480e0c8d3
on master.Thanks for doing this, I would not have managed it. Other than two minor comments, you'll also need to make nix 19.09 not required in GitHub settings.
Maybe add explanatory comment about what this does? Or the overall process? This is quite opaque, and the linked page only covers the push part.
@ -0,0 +1,62 @@
{
I assume this will occasionally need to be updated. Can you document how to do so?
Thanks for the review. This definitely ended up about 5x more complicated than I expected. :( But hopefully the upside makes it worthwhile (we should not really have to write any more per-package Nix expressions).
I clicked GitHub buttons to remove "ci/circleci: nixos-19-09" from the required status list for the "master" branch protection configuration for the project.