-
-
Notifications
You must be signed in to change notification settings - Fork 104
Comparing changes
Open a pull request
base repository: NixOS/nixpkgs-channels
base: 1f49029aceac
head repository: NixOS/nixpkgs-channels
compare: e8aadfe74c1e
- 19 commits
- 22 files changed
- 14 contributors
Commits on Nov 6, 2019
-
According to Neomutt's autocrypt manual <https://neomutt.org/guide/autocryptdoc.html>, autocrypt needs to be enabled in the `configureFlags` and `sqlite` is a new dependency.
Configuration menu - View commit details
-
Copy full SHA for 689b963 - Browse repository at this point
Copy the full SHA 689b963View commit details
Commits on Nov 8, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 34b84e8 - Browse repository at this point
Copy the full SHA 34b84e8View commit details -
terraform-providers: group individual repo providers
Marius Bergmann committedNov 8, 2019 Configuration menu - View commit details
-
Copy full SHA for 206f719 - Browse repository at this point
Copy the full SHA 206f719View commit details -
terraform-providers: fix handling of version/rev in provider list
I interpreted the purpose of stripping the first character from the 'version' argument as an attempt to remove a prefixed 'v' (e.g. 'v1.0.0') from a version tag. This works if the tag actually has a 'v' prefix, but also removes the first character if version tags are not prefixed (e.g. '1.0.0'). Additionally, the 'v' was added again when specifying the `rev` for `fetchFromGitHub` in default.nix. As described above, this did also not work when provider repos did not prefix their version tags with 'v'. I changed the implementation as follows: - `version` and `rev` are stored inside data.nix - `version` is used to declare the nix package version - `rev` is used to fetch the proper git ref when building the package - for determining `version`, an optional leading 'v' is trimmed from the tag name Now this has the implication that the latest tag must always be a release tag when using the `update-all` script, but as the result of running `update-all` should always be reviewed before submission, makes this appear a manageable tradeoff to me.
Marius Bergmann committedNov 8, 2019 Configuration menu - View commit details
-
Copy full SHA for 3ddd53e - Browse repository at this point
Copy the full SHA 3ddd53eView commit details -
terraform-providers: update existing providers
Marius Bergmann committedNov 8, 2019 Configuration menu - View commit details
-
Copy full SHA for 610ffc9 - Browse repository at this point
Copy the full SHA 610ffc9View commit details -
terraform-provider-pass: init at 1.2.1
Marius Bergmann committedNov 8, 2019 Configuration menu - View commit details
-
Copy full SHA for bc0a2ad - Browse repository at this point
Copy the full SHA bc0a2adView commit details
Commits on Nov 9, 2019
-
Configuration menu - View commit details
-
Copy full SHA for fb512ea - Browse repository at this point
Copy the full SHA fb512eaView commit details -
Merge pull request #73031 from manveru/crystal-0.31.1
crystal: 0.30.1 -> 0.31.1
Configuration menu - View commit details
-
Copy full SHA for e9e7210 - Browse repository at this point
Copy the full SHA e9e7210View commit details -
* epr: init at 2.3.0b * Apply changes from code review Co-authored-by: zimbatm <zimbatm@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 7cdd581 - Browse repository at this point
Copy the full SHA 7cdd581View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4a589e5 - Browse repository at this point
Copy the full SHA 4a589e5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 954e234 - Browse repository at this point
Copy the full SHA 954e234View commit details -
Merge pull request #72939 from mbrgm/update-terraform-providers
terraform-providers: update and improve update script
Configuration menu - View commit details
-
Copy full SHA for a8f50f0 - Browse repository at this point
Copy the full SHA a8f50f0View commit details -
cloud-custodian: init at 0.8.45.1
Co-Authored-By: Jon <jonringer@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for f302f02 - Browse repository at this point
Copy the full SHA f302f02View commit details -
Configuration menu - View commit details
-
Copy full SHA for 518b5c1 - Browse repository at this point
Copy the full SHA 518b5c1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8e1380b - Browse repository at this point
Copy the full SHA 8e1380bView commit details -
Configuration menu - View commit details
-
Copy full SHA for d602c56 - Browse repository at this point
Copy the full SHA d602c56View commit details -
pytest-black: patch black dependency
This change is pending upstream in #29, but it is stale.
Configuration menu - View commit details
-
Copy full SHA for a4f0c51 - Browse repository at this point
Copy the full SHA a4f0c51View commit details -
Configuration menu - View commit details
-
Copy full SHA for 62e927d - Browse repository at this point
Copy the full SHA 62e927dView commit details -
Configuration menu - View commit details
-
Copy full SHA for e8aadfe - Browse repository at this point
Copy the full SHA e8aadfeView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1f49029aceac...e8aadfe74c1e