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
pdf-tools: fix build #41940
pdf-tools: fix build #41940
Conversation
In such cases we typically set the version to the git revision's date and mark it as unstable, like |
4da02c6
to
39b919b
Compare
@xeji Ah, thanks, fixed! |
Thanks. I just tried to build this locally but it failed because emacs packages apparently must have a number as version, so we cannot use the word "unstable" here. Didn't know about that emacs-specific constraint. If you set |
I'm not sure if there's an official policy on this, but I usually version things like this as "${lastVersion}-${gitDate}-git", i.e. I would do "0.80-20180429-git". This way `lib.versionOlder` works as expected and it is unambitious.
|
39b919b
to
1f553bd
Compare
@GrahamcOfBorg build emacsPackagesNg.pdf-tools |
Failure on x86_64-linux (full log) Attempted: emacsPackagesNg.pdf-tools Partial log (click to expand)
|
Failure on x86_64-darwin (full log) Attempted: emacsPackagesNg.pdf-tools Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: emacsPackagesNg.pdf-tools Partial log (click to expand)
|
This still doesn't build. |
Even better would be using the release and adding the relevant commits to patches: patches = [
(fetchpatch {
url = https://github.com/politza/pdf-tools/commit/6505a0e817495b85897c9380161034ae611ddd90.patch;
sha256 = "122ycbja8ckaysp58xqfcv11sgpbcp78pll5mywf9hgr0qap9jsy";
})
(fetchpatch {
url = https://github.com/politza/pdf-tools/commit/ded6341b0e3ad97e8b14f68c1796ba66dc155fd1.patch;
sha256 = "0hd2v4c6xq2jzg2m6s5kzs0fldgygf1pnfqd11v6x4w05zvxn6a2";
})
(fetchpatch {
url = https://github.com/politza/pdf-tools/commit/50a5297b82e26cfd52f6c00645ddc1057099d6a7.patch;
sha256 = "107rqzldg06h8k3pmdinkl78dr4xycm570sp2an4ihjmpmph0z39";
})
]; |
@xeji How are you testing this? |
@jtojnar If I do this, should the version stay at 0.80? |
Yes. |
@pmiddend to test the build with your local nixpkgs clone, you can use |
To fix NixOS#41916, this commit upgrades the emacs package “pdf-tools” to the HEAD revision, since there’s no official release containing the fix.
1f553bd
to
a81fea3
Compare
@GrahamcOfBorg build emacsPackagesNg.pdf-tools |
Success on x86_64-linux (full log) Attempted: emacsPackagesNg.pdf-tools Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: emacsPackagesNg.pdf-tools Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: emacsPackagesNg.pdf-tools Partial log (click to expand)
|
Looks good, thank you. |
Motivation for this change
To fix #41916, this commit upgrades the emacs package “pdf-tools” to the HEAD revision, since there’s no official release containing the fix. I'm not sure what to set the package's "version" to, though. Or what to do about the melpa versions of this package.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)