kotlin2 in Debian -- 2025W18 update
- To: debian-java@lists.debian.org
- Subject: kotlin2 in Debian -- 2025W18 update
- From: Julien Plissonneau Duquène <sre4ever@free.fr>
- Date: Fri, 02 May 2025 19:39:55 +0200
- Message-id: <[🔎] c88ba99ac7ce198a5368270f80ea65de@free.fr>
- In-reply-to: <e7d2987d54f803a4ae8bb889e0a13ac1@free.fr>
- References: <c447006d-7f97-72ec-1980-2425466a196b@free.fr> <Zyjt3RNsLhKA91au@laptop-t.office.oeko.net> <c36c79556d74aaccbc6608f8ba99efae@free.fr> <5284bacb294ba1ff08f32a5a0b175dd4@free.fr> <b71605fcbe384879c0238f9413c23735@free.fr> <8497785db64c2691266dc8269486d7c2@free.fr> <2ec4a44b89889611d1dfa2ee19129e86@free.fr> <6f53f62c9f3bff92fa66c714d62da6d1@free.fr> <c766c257fb3305889b628c769373b766@free.fr> <965acdffa651fe10e90e6f26728e4af7@free.fr> <edc8e50ba3b2ae1f219f1180512870b7@free.fr> <b9acefda-d2fb-4f4e-99b1-1ea9753e3028@at.or.at> <2e2ac5f7efc8ae401863382517249ce9@free.fr> <fd7bed1065756d6755c922929c201585@free.fr> <7e2a9e1b7fda03ad83d664582fb89c8d@free.fr> <ce6d7fbffa95bc534b1fc569e4471cab@free.fr> <5650baeeec5223dfb5affa4aa42f1b56@free.fr> <fab2fe12-991d-4fd3-a17f-28483bae3cf9@debian.org> <7053663db379b063042e99eb31bdadcd@free.fr> <80615ea609e5fab28e354a494d83e59d@free.fr> <572b182be1c0f0e013ce95cbf563f223@free.fr> <ac7cff49d09a4ee5e48254d7aabcbc00@free.fr> <7a6e787cb9984825628a1a365ac6e8a3@free.fr> <c0add46a68772eb1de3e916d23ca6f86@free.fr> <07f185f4d07c5acd3e458b01e354be41@free.fr> <3ebae8b9869459ef719d6366190fa5f0@free.fr> <e7d2987d54f803a4ae8bb889e0a13ac1@free.fr>
Good evening,
There was progress on kotlin2, though I'm still removing dependencies on
plugins and libraries that are not yet packaged and are not strictly
necessary for the build.
Le 2025-04-25 22:08, Julien Plissonneau Duquène a écrit :
I have to figure out why it fails to resolve
I was stuck on similar issues for a short while, then decided they were
not worth debugging (that is, not for now) so I just worked around them
by patching the build scripts. At some point I suspected that the issues
could be caused by building with Gradle 8.11.1 instead of the nominal
8.8 so I tried a regular build just changing the Gradle version; some
patching was necessary to make that build succeed because of new
deprecations and a renamed API but that didn't reproduce the class
resolution issues. So I still don't know how I introduced them.
I have some hopes to get the configuration phase of that build script to
work offline by next week, as I think I'm more than halfway done on that
front.
On the side quest stack there now only a single remaining package
(intellij-community-idea) waiting to be sponsored on mentors.debian.net
if any DD has some availability for that.
Cheers,
--
Julien Plissonneau Duquène
Reply to: