mercurialFull: 4.9.1 -> 5.0 #60993
Closed
mercurialFull: 4.9.1 -> 5.0 #60993
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mercurial-full/versions
|
tortoisehg also needs to be updated. |
tomberek
reviewed
May 6, 2019
|
Please always update mercurial and tortoisehg together, and/or set the dependencies for tortoisehg to the appropriate mercurial version range. |
danbst
added a commit
to danbst/nixpkgs
that referenced
this pull request
Aug 6, 2019
When I've added `tortoisehg` package, it turned out that mercurial updates sometimes broke thg. I've added a comment to `mercurial/default.nix` to update torotisehg version during mercurial updates, but this worked the other way round: mercurial stopped to be updated regularly (NixOS#60993). And sadly it didn't solve the issue - NixOS#61759. Here I'm trying to untie them. Tortoisehg will build a custom mercurial package if versions don't match. This makes updating tortoisehg more complicated, but it is still better than current situation.
danbst
added a commit
that referenced
this pull request
Aug 18, 2019
* tortoisehg: untie from mercurial When I've added `tortoisehg` package, it turned out that mercurial updates sometimes broke thg. I've added a comment to `mercurial/default.nix` to update torotisehg version during mercurial updates, but this worked the other way round: mercurial stopped to be updated regularly (#60993). And sadly it didn't solve the issue - #61759. Here I'm trying to untie them. Tortoisehg will build a custom mercurial package if versions don't match. This makes updating tortoisehg more complicated, but it is still better than current situation. * expose custom mercurial from thg package
|
This is now outdated. Mercurial will be updated in separate PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mercurial-full/versions.
meta.description for mercurialFull is: '"A fast, lightweight SCM system for very large distributed projects"'.
Checks done (click to expand)
Rebuild report (if merged into master) (click to expand)
75 total rebuild path(s)
20 package rebuild(s)
20 x86_64-linux rebuild(s)
19 i686-linux rebuild(s)
17 x86_64-darwin rebuild(s)
19 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
cabal2nix
dep2nix
devpi-client
gitAndTools.git-remote-hg
gitAndTools.gitFastExport
hydra
mbed-cli
mercurial
mercurialFull
mx
nbstripout
nix-prefetch-hg
nix-prefetch-scripts
nix-update-source
pypi2nix
python27Packages.hglib
python27Packages.hgsvn
python37Packages.hglib
reposurgeon
tortoisehg
Instructions to test this update (click to expand)
Either download from Cachix:
(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
cc @edolstra for testing.