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

tortoisehg : needs version upgrade 4.8 -> 4.9 #61759

Closed
libeako opened this issue May 20, 2019 · 2 comments
Closed

tortoisehg : needs version upgrade 4.8 -> 4.9 #61759

libeako opened this issue May 20, 2019 · 2 comments

Comments

@libeako
Copy link

libeako commented May 20, 2019

Issue description

A simple version upgrade is due in package 'tortoisehg' in NixOS 19.03.

"TortoiseHg" is a front end for the "Mercurial" version manager. NixOS 19.03 uses Mercurial version (4.9), TortoiseHg version (4.8.2), but "This version of TortoiseHg requires Mercurial version 4.7.n to 4.8.n, but found 4.9", thus TortoiseHg does not work at all currently.

danbst added a commit to danbst/nixpkgs that referenced this issue 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 issue 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
@JohnAZoidberg
Copy link
Member

@danbst why doesn't a2ea2a1 solve this issue?

@danbst
Copy link
Contributor

danbst commented Feb 16, 2020

@JohnAZoidberg perhaps wording is bad. Forgot to mention that that PR fixed this particular issue.

@danbst danbst closed this as completed Feb 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants