| 11 Jan 2025 |
|  j4m3s joined the room. | 01:19:10 |
| 15 Jan 2025 |
|  SomeoneSerge (utc+3) changed their display name from SomeoneSerge (utc+3) to SomeoneSerge. | 19:02:27 |
| 16 Jan 2025 |
| j4m3s set their display name to j4m3s. | 10:27:58 |
| 22 Jan 2025 |
|  samasaur joined the room. | 19:54:23 |
| samasaur | I'm not sure whether this is exactly the right place to put it, but I recently opened a PR attempting to standardize outputs of the JDKs in nixpkgs on darwin. It makes them produce a "JDK bundle" at $out/Library/Java/JavaVirtualMachines/${name}-${version}.jdk (mirroring the install location for JDKs on macOS), and provides a bundle attribute that points to this path. Having this consistency will make it a lot easier to install JDKs properly on darwin. I'd love to hear people's thoughts! | 19:57:48 |
| 31 Jan 2025 |
| SomeoneSerge (utc+3) changed their display name from SomeoneSerge to SomeoneSerge (Bruxelles). | 19:34:48 |
|  raboof changed their display name from raboof to raboof@FOSDEM. | 23:54:20 |
| 2 Feb 2025 |
 Tomodachi94 (they/them) | In reply to@samasaur:matrix.org
I'm not sure whether this is exactly the right place to put it, but I recently opened a PR attempting to standardize outputs of the JDKs in nixpkgs on darwin. It makes them produce a "JDK bundle" at $out/Library/Java/JavaVirtualMachines/${name}-${version}.jdk (mirroring the install location for JDKs on macOS), and provides a bundle attribute that points to this path. Having this consistency will make it a lot easier to install JDKs properly on darwin. I'd love to hear people's thoughts! This sounds like an awesome idea, I'll take a look | 03:18:09 |
| Tomodachi94 (they/them) | I currently don't have access to a NixOS machine though, so I'm limited to just reviewing diffs (this is why I've been so inactive this month) | 03:18:35 |
| Tomodachi94 (they/them) | This is totally up @emily's alley too (darwin and Java) | 03:32:54 |
| samasaur | yeah i was actually talking with emily about it when i did the work originally! they get credit for the idea of putting JDK bundles at the path that mirrors the install location | 03:44:43 |
| samasaur | i'll request their review too | 03:48:49 |
| samasaur | and I just force-pushed | 03:49:19 |
| samasaur | As best I can tell, the PR doesn't introduce any new breakages | 03:49:39 |
| Tomodachi94 (they/them) | I've been meaning to mark a bunch of those Java packages as broken since I did some Ant refactors way back in November/early December, could be a fun project for anyone wanting to do Java stuff | 04:49:46 |
| Tomodachi94 (they/them) | (and potentially make the build reports of some of my PRs more appealing, which is totally unrelated /s 🙃) | 04:50:38 |
|  gmodena joined the room. | 10:54:57 |
| samasaur | funnily enough i actually realized while doing this that I barely use Java anymore | 18:41:55 |
| samasaur | I still keep four JDK versions installed on my mac though | 18:42:12 |
| samasaur | and now I'm committed to getting this queue of changes in | 18:42:38 |
| raboof changed their display name from raboof@FOSDEM to raboof. | 22:18:45 |
| 3 Feb 2025 |
|  Lorenz Leutgeb changed their display name from Lorenz Leutgeb 📞6343 to Lorenz Leutgeb. | 08:53:22 |
| SomeoneSerge (utc+3) changed their display name from SomeoneSerge (Bruxelles) to SomeoneSerge (Gand St. Pieters). | 13:40:23 |
| 4 Feb 2025 |
| samasaur | I'm reaching the limit of my Nix-fu on this PR. I ran a nixpkgs-review run, which gave me a list of broken packages. Then I fed them into hydra-check to eliminate those that were already broken even though they weren't marked broken. But I'm left with a very long list of packages that allegedly were broken by my PR, even though when I test packages from that list locally they don't build before or after the PR | 06:33:31 |
| samasaur | is there some strategy I'm missing to track down which packages, if any, were actually broken by this PR? | 06:33:53 |
 FliegendeWurst | In reply to @samasaur:matrix.org
I'm reaching the limit of my Nix-fu on this PR. I ran a nixpkgs-review run, which gave me a list of broken packages. Then I fed them into hydra-check to eliminate those that were already broken even though they weren't marked broken. But I'm left with a very long list of packages that allegedly were broken by my PR, even though when I test packages from that list locally they don't build before or after the PR By "before your PR", do you mean current master? Or the commit you branched off from master (potentially much older)? | 06:37:26 |
| samasaur | well FWIW I did just rebase two days ago so the difference isn't going to be all that much | 06:42:34 |
| samasaur | when I said "when I test packages from that list locally they don't build before or after the PR" I meant building locally on the tip of my PR vs on the commit I branched off of master | 06:42:56 |
| samasaur | for example I tested gama and it failed to build locally both on the tip of my PR and on the commit I branched off of master, but I know that it built on hydra because when I originally tried to build it locally on the branch-off commit it downloaded from cache.nixos.org and I had to pass --check to nix-build to get it to actually try building (where it then failed) | 06:44:20 |
| samasaur | obviously hydra-check is checking unstable, which I believe is neither current master nor my branch-off commit | 06:45:57 |
