Login
You're viewing the techdon.dev public feed.

Replies

  • IzzyIzzyOnDroid@floss.social
    Feb 19, 2026, 7:40 PM

    @Billie builds at @fdroidorg take place before the metadata are being published, yes – and only after either the build succeeded, or is manually disabled because it failed and could not be repaired. So yours is in between "failed" and, hopefully, "repair". According to the build log, the error is "Unsupported class file major version 65" – that would be, JDK-21 was not found. Strange, as our build for your app does not have that installed either, still running with 17+11 as you need. (1/2)

    💬 1🔄 0⭐ 0
  • IzzyIzzyOnDroid@floss.social
    Feb 19, 2026, 7:46 PM

    (2/2) @Billie you still use gradle 7.3.3 according to that log (and according to codeberg.org/Starfish/TinyWeat), which does not even support JDK 21.

    My bet is, @fdroidorg updated to JDK-21 by default – and as no specific JDK was set by their recipe, that causes the crash. So they need to explicitly install JDK 17 in that recipe, and it would, most likely, build fine again.

    I've pinged one of the maintainers there, should be fixed soon™.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • IzzyIzzyOnDroid@floss.social
    Feb 19, 2026, 10:04 PM

    @Billie 7.3.3 is pretty old, considering 9.x is out for a while now. I'd say test with a newer one (at least 8.x) and JDK 17 or 21 (currently we still build TW with 11, as that seems to have been needed), maybe on a separate branch. When you think it's stable, reach out to us for an RB test if you wish (so we can sync our recipes). Once that point is achieved, @fdroidorg should also be informed about any recipe change, and the next release be made.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • IzzyIzzyOnDroid@floss.social
    Feb 19, 2026, 8:00 PM

    @Billie PS for you: sorry for the "messed up" full descriptions on our end! I've just fixed them, will take effect with the next sync.

    For background: they were not set for the proper format, at our end. Most likely, at some point in the past, you had "proper HTML" there – which is no longer there (or I messed up when establishing that here). I've now set it to "fulldescMD", aka Markdown processing, which should work fine (I've checked all affected locales). 🤞

    💬 0🔄 0⭐ 0