Poetry2nix | 315 Members | |
| https://github.com/nix-community/poetry2nix | 60 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Jan 2024 | ||
| I've tried specifying the dependency as both of these ways:
Even when directly pointing it directly at the wheel file, it still gives the same error | 21:46:52 | |
| I can wrap this all up into a github issue if that would work better, the github issue template pointed towards this room as a start | 21:49:29 | |
I just tried manually removing cmake from my poetry.lock file, so that I could try out preferWheels = false;. Strangely, that doesn't seem to have any effect either, I get the same error | 22:15:09 | |
| knkski: there are default overrides for pytorch-lightning that attempt to handle what must have previously been something like a nested tarball. I removed these from a test fork https://github.com/cameronraysmith/poetry2nix/commit/aab624b6f49b5974a57a4be5d034613d6b65c79f and things work as expected when I source it in my flake. I was going to discuss submitting these upstream but it might be necessary to retain them with version guards for backward compatibility | 22:28:51 | |
| cameronraysmith: that worked, thank you! | 22:30:28 | |
| * knkski: there are default overrides for pytorch-lightning that attempt to handle what must have previously been something like a nested tarball. I removed these from a test fork https://github.com/cameronraysmith/poetry2nix/commit/aab624b6f49b5974a57a4be5d034613d6b65c79f and things work as expected when I source it in my flake. I was going to discuss submitting these upstream but it might be necessary to retain them with version guards for backward compatibility I didn't manage to bisect where this must have changed in the pytorch-lightning release history but I tried as far back as 1.9.4 or so. | 22:30:58 | |
| * knkski: there are default overrides for pytorch-lightning that attempt to handle what must have previously been something like a nested tarball. I removed these from a test fork https://github.com/cameronraysmith/poetry2nix/commit/aab624b6f49b5974a57a4be5d034613d6b65c79f and things work as expected when I source it in my flake. I was going to discuss submitting these upstream, but it might be necessary to retain them with version guards for backward compatibility. I didn't manage to bisect where this must have changed in the pytorch-lightning release history but I tried as far back as 1.9.4 or so. | 22:31:39 | |
| * knkski: there are default overrides for `pytorch-lightning` that attempt to handle what must have previously been something like a nested tarball. I removed these from a test fork https://github.com/cameronraysmith/poetry2nix/commit/aab624b6f49b5974a57a4be5d034613d6b65c79f and things work as expected when I source it in my flake. I was going to discuss submitting these upstream, but it might be necessary to retain them with version guards for backward compatibility. I didn't manage to bisect where this must have changed in the pytorch-lightning release history but I tried as far back as 1.9.4 or so. | 22:32:01 | |
| 22:32:15 | ||
| * knkski: there are default overrides for pytorch-lightning that attempt to handle what must have previously been something like a nested tarball. I removed these from a test branch on my fork https://github.com/cameronraysmith/poetry2nix/commit/aab624b6f49b5974a57a4be5d034613d6b65c79f and things work as expected when I source it in my flake. I was going to discuss submitting these upstream, but it might be necessary to retain them with version guards for backward compatibility. I didn't manage to bisect where this must have changed in the pytorch-lightning release history but I tried as far back as 1.9.4 or so. | 22:34:26 | |
| * knkski: there are default overrides for https://github.com/cameronraysmith/poetry2nix/commit/aab624b6f49b5974a57a4be5d034613d6b65c79f and things work as expected when I source it in my flake. I was going to discuss submitting these upstream, but it might be necessary to retain them with version guards for backward compatibility. I didn't manage to bisect where this must have changed in the pytorch-lightning release history but I tried as far back as | 22:45:39 | |
| * knkski: there are default overrides for I didn't manage to bisect where this must have changed in the pytorch-lightning release history but I tried as far back as | 22:46:48 | |
| * knkski: there are default overrides for I could add these if I knew where things changed, but I didn't manage to bisect where this in the pytorch-lightning release history after trying as far back as | 22:48:37 | |
| * knkski: there are default overrides for I could add these if I knew where things changed, but I didn't manage to bisect where that is in the pytorch-lightning release history after trying as far back as | 22:49:09 | |
| * knkski: there are default overrides for I could add these if I knew where things changed, but I didn't manage to bisect where that is in the pytorch-lightning release history after trying as far back as | 22:49:32 | |
| * knkski: there are default overrides for I could add these if I knew where things changed, but I didn't manage to bisect where that is in the pytorch-lightning release history after trying as far back as | 22:50:10 | |
| I'll see if I can help bisect exactly where. I do remember that 1.5.3 installed with no issue, and 1.5.4 had some issue. I don't remember if it was the same one though | 22:50:27 | |
| That sounds like a good start. I'll take a look around that time. | 22:51:02 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 22:58:15 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 22:59:06 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:00:06 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:00:32 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:00:45 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:01:09 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:01:45 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:01:58 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:02:56 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:03:35 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:04:30 | |
| * That sounds like a good start. I'll take a look around that time. Since the | 23:05:05 | |