| 20 Sep 2022 |
 Linux Hackerman | wait no, that's for the gsettings schemas thing | 12:44:42 |
| Linux Hackerman | what's tree-sitter-markdown got to do with that? | 12:44:51 |
 Izdihar | It seems that when it tries to compile one of the rust dependencies of Lapce (tree-sitter-markdown), this dependency tries to find a file that doesn't exist. Here is the log, also available in the discussion Linux Hackerman | 12:47:13 |
| Linux Hackerman | I just don't understand why you've commented on the gsettings schemas issue, what's that got to do with it? | 12:48:03 |
| Linux Hackerman | (that's not a criticism necessarily, I just don't understand) | 12:48:45 |
| Izdihar | its ok, I know it's not criticism
I commented on this issue because I hope that by bumping the version, that issue could be fixed | 12:50:04 |
| Izdihar | And the tree-sitter-markdown thing happened because I'm trying to bump the version from 0.1.2 to 0.2 | 12:50:35 |
| Linux Hackerman | riiiight | 12:50:41 |
| Linux Hackerman | yeah I'm 99% sure that won't fix the issue, you want wrapGAppsHook as mentioned before :) | 12:50:59 |
| Linux Hackerman | but looking at tree-sitter-markdown I think it's a bug in its build: it assumes that you're building it with the source tree as the working directory https://github.com/dzhou121/tree-sitter-markdown/blob/split_parser/bindings/rust/build.rs#L2 | 12:51:15 |
| Linux Hackerman | which is probably not the case | 12:51:19 |
| Izdihar | In reply to @linus:schreibt.jetzt
yeah I'm 99% sure that won't fix the issue, you want wrapGAppsHook as mentioned before :) alright I'll do this to my PR thank you | 12:52:13 |
| Izdihar | This guy seems to get it and add a flake to build lapce. I don't know what he does differently though. Maybe because he's using crane instead of buildRustPackage? | 12:54:06 |
| Izdihar | Can we even use crane in nixpkgs? | 12:55:28 |
| Izdihar | In reply to @tengkuizdihar:matrix.org
This guy seems to get it and add a flake to build lapce. I don't know what he does differently though. Maybe because he's using crane instead of buildRustPackage? forgot to add the link lol https://github.com/lapce/lapce/issues/1049#issuecomment-1251641329
Linux Hackerman | 12:56:17 |
| Linux Hackerman | Possibly crane makes the difference, I don't know anything about it | 12:57:32 |
| Linux Hackerman | I suspect we can't use it in nixpkgs, but again I don't know anything about it so 🤷 | 12:58:07 |
| Izdihar | In reply to @linus:schreibt.jetzt
I suspect we can't use it in nixpkgs, but again I don't know anything about it so 🤷 searched it in nixpkgs, no crane 👌 | 12:58:32 |
| Izdihar | someone literally just jumps in and said try this and I'm trying it. If it's working, what a chad. | 13:03:32 |
|  pareto-optimal-dev joined the room. | 13:43:22 |
| Izdihar | Linux Hackerman: does it need to be in nativebuildinputs or can I also put it in buildInputs? I've accidentally done that and the issue persists... | 14:13:12 |
| Linux Hackerman | Not 100% sure but I do think it's supposed to be in nativeBuildInputs | 14:13:34 |
|  Gianluca Arbezzano left the room. | 14:22:18 |
| Gianluca Arbezzano joined the room. | 14:22:46 |
| Izdihar | yep still the same error in nativeBuildInputs lmao Linux Hackerman | 14:34:18 |
| Linux Hackerman | Izdihar: ah, I think you also need gsettings-desktop-schemas in buildInputs | 14:36:40 |
| Izdihar | In reply to @linus:schreibt.jetzt
Izdihar: ah, I think you also need gsettings-desktop-schemas in buildInputs alright, its building time | 14:37:17 |
| Izdihar | still doesn't work lmaoo | 14:55:21 |
| Izdihar | I might need to follow this https://github.com/NixOS/nixpkgs/blob/95af2245a32f8e1310ad4e3bf50b76d86ddbbc0a/doc/languages-frameworks/gnome.section.md#frequently-encountered-issues-ssec-gnome-common-issues | 14:57:58 |
| Gianluca Arbezzano | Hello! I think I have a basic question. First time trying to package a Rust project
alexandria = naersk'.buildPackage {
src = builtins.fetchGit {
url = ssh://git@github.com/.../...;
ref = "HEAD";
rev = "asdas";
};
patches = [
./001-remove-buildinfo.patch
];
gitAllRefs = true;
};
The build fails applying the patch with:
can't find file to patch at input line 14
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
I looked at the derivation logs via nix logs and I checked the source archive directory but the files in there looks totally different compared with the one I have as part of the repository. Not sure why and as consequence the patch fails because it can't find all the files it should have
| 15:31:09 |
