-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
fetchFromGitHub output changed -- cannot build lua-mode #54641
Comments
That's really weird. One might think that emacs2nix could be at fault here, so I tried to check this by verifying the hashes of all emacs packages, hoping to find a couple more where this would happen. So here's the results: On bf041c3, out of the 4236 attributes in
The emacswiki ones make sense, they don't seem to use persistent urls. But out of the almost 4000 github sources for these packages, only So, either
All of those are very unlikely unfortunately.. I think the best thing to do for now is:
|
If you had it installed before and still have the source in /nix/store you can also just diff it with the new source.
Btw, the rejected #49862 simplifies such things a lot (if you keep it applied for a while).
|
Unfortunately the older sources got garbage collected so I cannot check what is changed in them. |
I can confirm that I experience the same thing. I tried diffing the two sources:
But it doesn't show any difference. However, I am not 100% sure if the diff command is doing the correct thing |
Trying to debug this I checked this, which I guess is one of the steps which I guess is what @infinisil was doing:
When I searched for the new hash on github I found @jwiegley had added the new hash as an override: So I am doing the same for now. In case anyone wants a temporary workaround. |
Any progress on this? While I can at least hack around the expected hash for lua-mode, it's a bit sad to have a bug like this as we head into 19.03. |
Issue description
I cannot install
emacsPackagesNg.melpaPackages.lua-mode
anymore. I am pretty sure it worked on an another machine a couple of weeks ago. Interestingly thesrc
definition was last modified over 10 months ago in b801736. The revision before that fails to build too so the issue seems to be tied to the upstream repository.It seams to me that the archive downloaded by
fetchFromGitHub
itself has changed. I don't know if such breakages are meant to happen but it worries me a bit. If it is something that worth more investigation I may be able to pull the archive having the correct checksum from an another machine to check how the newer one differs from it.Steps to reproduce
The following command fails to run on a fresh (d359b5d) nixpkgs local checkout and on
release-18.09
:Technical details
"x86_64-linux"
Linux 4.19.17, NixOS, 18.09.1985.749a3a0d00b (Jellyfish)
yes
yes
nix-env (Nix) 2.1.3
"nixos-unstable-19.03pre166987.bc41317e243, nixos-18.09.1922.97e0d53d669, blox, home-manager-18.09, mozilla, nixos-hardware"
"mozilla, nixos-unstable-19.03pre162671.44b02b52ea6"
/nix/var/nix/profiles/per-user/root/channels/nixos
The text was updated successfully, but these errors were encountered: