Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Simon McVittie Newsgroups: linux.debian.bugs.dist,linux.debian.ports.arm,linux.debian.maint.java,linux.debian.devel.release Subject: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Date: Tue, 26 Mar 2024 11:40:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Tue Mar 26 10:39:08 2024 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: 0.201 Reply-To: Simon McVittie , 1036884@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Release Team X-Debian-Pr-Message: followup 1036884 X-Debian-Pr-Package: release.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Debian-User: smcv X-Debian-Message: from BTS X-Mailing-List: archive/latest/1830037 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 23 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-arm@lists.debian.org, debian-java@lists.debian.org X-Original-Date: Tue, 26 Mar 2024 10:35:10 +0000 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.bugs.dist:1191869 linux.debian.ports.arm:13920 linux.debian.maint.java:12732 linux.debian.devel.release:123390 It seems that some of the dependency chains for packages that are still waiting to be rebuilt on armel,armhf now end at openjdk-17, which is the default Java version for most architectures and Build-Depends on itself (with an alternative dependency on openjdk-16, but that no longer exists). evolution-data-server -> libphonenumber-dev is an example. Are the ARM or Java teams intending to re-bootstrap openjdk-17 somehow? Or do maintainers of packages that build both a C/C++ library and Java bindings from a single source package need to disable its Java bindings on the affected architectures, either temporarily or permanently? openjdk-21 is in a similar situation, build-depending on itself, while openjdk-22 and openjdk-23 build-depend on -21 and -22 respectively. Presumably once we have a single OpenJDK version that is installable, it would be possible to step through 18,19,20,21 building each version with the previous one. In the -ports world, hppa doesn't have Java anyway, while m68k, powerpc and sh4 seem to have had a re-bootstrap at some point; so I think it's only the release architectures armel and armhf that have a problem here. smcv