| 20 Sep 2025 |
|  @98765abc:mozilla.org left the room. | 08:03:36 |
 Tomodachi94 (they/them) | As far as release blockers:
- Definitely remove Gradle 7 before the release, it's unsupported upstream
- Is Java 24 still in tree? We should drop it if so
| 22:24:44 |
| 21 Sep 2025 |
| Tomodachi94 (they/them) | (Assuming that it goes EOL before or during the support cycle) | 00:24:39 |
 msgilligan | Java 24 is EOL as soon as Java 25 is released. | 00:25:25 |
| msgilligan | We’ve still got Java 23 in tree, so we should remove that first. | 00:26:00 |
| Tomodachi94 (they/them) | Tracked at https://github.com/NixOS/nixpkgs/issues/444846 | 03:28:22 |
| 22 Sep 2025 |
 Benedikt Ritter (britter) | Can I get a review here https://github.com/NixOS/nixpkgs/pull/445032 just a version bump | 07:28:42 |
| msgilligan | I ran nixpkgs-review on aarch64 darwin and linux and posted results. | 08:59:58 |
| msgilligan | There was a problem wtih the mac build. Unfortunately it's 2am here and I really need to sleep, so I won't be able to respond for 12 hour or so. | 09:01:19 |
| Benedikt Ritter (britter) | No worries, this is not time critical. | 09:12:02 |
| Benedikt Ritter (britter) | msgilligan: you raised the question about whether or not running the tests of Java packages. I think that's a discussion better held here than in the PR. So from my PoV in nixpkgs we don't want to run the testing of a project we package. I don't feel like that's giving us any significant signal as to whether the package works or not. I think we need nixos/tests tests for apps like stirling that test whether the thing can start on a NixOS host or not. | 18:09:22 |
| Benedikt Ritter (britter) | OTOH there seems to be something going on that only fails on macOS... | 18:09:41 |
| Benedikt Ritter (britter) | But then, maybe these tests also fail outside of building this package with nix. | 18:09:59 |
| Benedikt Ritter (britter) | Would be interesting to see if this also fails when you clone the project directly and then run ./gradlew build on macOS. If that's the case then it doesn't make sense to run with tests in nixpkgs from my PoV | 18:10:35 |
| msgilligan | You don't have a Mac? | 18:11:59 |
| Benedikt Ritter (britter) | No... | 18:13:38 |
| msgilligan | I'll try to build it directly, hang on... | 18:14:33 |
| Benedikt Ritter (britter) | I used to. But then I got fed up with proprietary software and wanted to run most if not all of my compute stack on OSS... So I got myself a Framework 13, ditched my iPhone and replaced it with a Pixel running GrapheneOS, rooted my Kindle and installed KOReader... all in on open source 😅 | 18:14:44 |
| msgilligan | I have the same impulses, but I've been a macOS developer off-and-on for 40 years and Apple's aarch64 hardware is great. So to move more to an OSS stack I started using Nix. Now I use Nix Darwin, Home Manager, have a Nix Linux Builder VM, a nixos-lima VM (sort of like a WSL environment), etc. | 18:17:19 |
| msgilligan | That's my way of keeping one foot on each side of the border. | 18:17:41 |
| msgilligan | So I regularly test Nixpkgs on both aarch64-darwin and aarch64-linux. | 18:18:09 |
| msgilligan | This is cool:
nativeBuildInputs = [
gradle
gradle.jdk # one of the tests also require that the `java` command is available on the command line
makeWrapper
];
| 18:21:36 |
| msgilligan | * This is cool (TIL!):
nativeBuildInputs = [
gradle
gradle.jdk # one of the tests also require that the `java` command is available on the command line
makeWrapper
];
| 18:22:15 |
| msgilligan | tempFileManagement_defaults_and_overrides() | 18:24:06 |
| msgilligan | org.opentest4j.AssertionFailedError: expected: </var/folders/6d/12xt4b4m8xjf3t0059_w18bh0000gn/T/stirling-pdf> but was: </var/folders/6d/12xt4b4m8xjf3t0059_w18bh0000gn/T//stirling-pdf>
at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
at app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1145)
at app//stirling.software.common.model.ApplicationPropertiesLogicTest.tempFileManagement_defaults_and_overrides(ApplicationPropertiesLogicTest.java:40)
at java.base@24.0.2/java.lang.reflect.Method.invoke(Method.java:565)
at java.base@24.0.2/java.util.ArrayList.forEach(ArrayList.java:1604)
at java.base@24.0.2/java.util.ArrayList.forEach(ArrayList.java:1604)
| 18:24:23 |
| msgilligan | For some reason macOS adds an extra / in this path:
/var/folders/6d/<hash>/T//stirling-pdf | 18:25:24 |
| msgilligan | * ApplicationPropertiesLogicTest
tempFileManagement_defaults_and_overrides() | 18:26:01 |
| msgilligan | I posted macOS test results in a thread above. | 18:29:39 |
| Benedikt Ritter (britter) | I kind of started the same way. I wanted a better solution for managing my home environment than putting random text files into a git repository. When I found home manager it was RIP https://github.com/britter/dotfiles | 18:29:44 |
| Benedikt Ritter (britter) | yeah, so it's not a problem related to packaging this app in nixpkgs. It's just that the tests don't work on macOS. For that reason this problem should not block a merge. We can discuss whether we want to create a PR for the project to get it fixed or whether we just set doCheck = false and move on with our lives... | 18:31:06 |
