Izzy
@chi-xigua could you maybe make that AppImage (or the one from 0.12.1 should you have built it already) available somewhere? I'm still on 0.11.3, as no newer AppImages exist. And...
@maniac103 as you might have missed the ping, can you please [take a look here](https://gitlab.com/IzzyOnDroid/repo/-/issues/644#note_2190107120) as what's currently preventing the app's inclusion, and let me know if the points can...
> I am not working on this project anymore. In that case, special thanks for still accepting the PR [I've now opened](https://github.com/itsvks19/LayoutEditor/pull/2) – helps us with our repo reorg, so...
@Stypox so your APKs are again using JDK-21 starting with v0.27.4? Then I'd run a manual update on my builder to avoid a double-run (delaying RB result publication) later.
No, I didn't ask for JDK-17 – obfusk and I reported our builders had no issues building it with JDK-21. Our builders are quite flexible, and can easily use JDKs...
> One of our rebuilders already [verified v0.27.4 as well, after switching back to OpenJDK 17](https://github.com/obfusk/rbtlog/commit/5fda54789616d0884a84b8534f60d421ada2760e) 🎉 [make that two](https://codeberg.org/IzzyOnDroid/rbtlog/commit/2842f84cb434600182875d96c840062b8aa8e661) :partying_face:
Though release 0.3.0.1 now is already distributed, so this would need a fresh release to reach everyone (and yes, reproducible build failed at IzzyOnDroid as well, diffs suggest a "dirty...
Unfortunately not. Huge differences in the dex files. ```diff -rw-r--r-- 0.0 unx 120 b- 118 defN 1981-01-01 01:01:02 0137786e META-INF/version-control-info.textproto - -rw-r--r-- 0.0 unx 10126 b- 10126 stor 1981-01-01 01:01:02...
> which seems to have 20 cores and 28 threads Urn… Afraid we cannot match that on a machine with 16 cores… > I'm indeed not building/releasing via a Github...
And has the same `versionCode` as 0.3.1 already had, so: repo/com.w2sv.filenavigator_16.apk already exists; ignoring update for com.w2sv.filenavigator, versionCode 16 already present 🤷♂