Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: =?UTF-8?Q?Julien_Plissonneau_Duqu=C3=A8ne?= Newsgroups: linux.debian.maint.java Subject: Re: kotlin2 in Debian -- 2025W13 update Date: Sat, 29 Mar 2025 13:50:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Sat Mar 29 12:40:21 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.099 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 MIME-Version: 1.0 User-Agent: Webmail Free/1.6.10 X-Sender: sre4ever@free.fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/23691 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/04eae96b0d33f019beaf12b26ca1e677@free.fr Approved: robomod@news.nic.it Lines: 19 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 29 Mar 2025 13:40:04 +0100 X-Original-Message-ID: <04eae96b0d33f019beaf12b26ca1e677@free.fr> X-Original-References: <5284bacb294ba1ff08f32a5a0b175dd4@free.fr> <8497785db64c2691266dc8269486d7c2@free.fr> <2ec4a44b89889611d1dfa2ee19129e86@free.fr> <6f53f62c9f3bff92fa66c714d62da6d1@free.fr> <965acdffa651fe10e90e6f26728e4af7@free.fr> <2e2ac5f7efc8ae401863382517249ce9@free.fr> <7e2a9e1b7fda03ad83d664582fb89c8d@free.fr> <5650baeeec5223dfb5affa4aa42f1b56@free.fr> <7053663db379b063042e99eb31bdadcd@free.fr> <80615ea609e5fab28e354a494d83e59d@free.fr> <572b182be1c0f0e013ce95cbf563f223@free.fr> <7a6e787cb9984825628a1a365ac6e8a3@free.fr> <1bba0f9e-fb48-699a-5bcd-e41bec750129@apache.org> Xref: csiph.com linux.debian.maint.java:12969 Le 2025-03-29 12:32, Emmanuel Bourg a écrit : >> A not too pleasant surprise was to discover that the upstream project >> decided to use LFS to store a few JPEG images used in the >> documentation (which is way overkill). Fortunately this is supported >> by Salsa and uscan, but it slows down significantly some remote >> operations. These images only appeared in 2.1.0 so the 2.0.21 branch >> should not be impacted. > > I think you can safely skip the documentation stuff and filter out the > JPEG images. I would rather keep the doc if possible, even if we can't build it right now (I haven't evaluated this yet). I'm considering instead opening an upstream issue and/or PR with a few janitorial fixes including this one. I've also opened an issue to try to get them to sign their release tags, currently they aren't even using annotated tags. -- Julien Plissonneau Duquène