Will i386 released for Trixie and if no can we stop working on it now?
Le Sun, Oct 13, 2024 at 10:20:30AM +, Debian FTP Masters a écrit : > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: > > debian-installer | 20240914 | i386 > > --- Reason --- > ROM; i386 support goes away > -- Hello everybody, I really feel lost regarding the status of i386. It seems that it is falling appart piece by piece, but on the other hand, it is still a release architecture, meaning that for arch:any packages that do not support it the random Debian Developer needs to do a lot of manual work, bug management, uploads, reverse-dependency chain traversals, FTP master removel requests, etc. Plus enduring the anxiety of worrying to carry some social stygma fir not doing enough to support non-amd64 architectures. Can we organise ourselves so that whaterver the future of i386 is, it does not consume unpaid volunteer work for nothing ? If the kernel team and the installer team could withdraw support, can the package maintainers of scientific computing software do so too? Is there a way to do it in a single operation instead of filling plenty of bugs and modifying plenty of debian/control files? Life is too short to spend our time on doing that. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://fediscience.org/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Re: Will i386 released for Trixie and if no can we stop working on it now?
Hi, It seems that it is falling appart piece by piece, but on the other hand, it is still a release architecture, meaning that for arch:any packages that do not support it the random Debian Developer needs to do a lot of manual work, bug management, uploads, reverse-dependency chain traversals, FTP master removel requests, etc. Plus enduring the anxiety of worrying to carry some social stygma fir not doing enough to support non-amd64 architectures. Can we organise ourselves so that whaterver the future of i386 is, it does not consume unpaid volunteer work for nothing ? If the kernel team and the installer team could withdraw support, can the package maintainers of scientific computing software do so too? Is there a way to do it in a single operation instead of filling plenty of bugs and modifying plenty of debian/control files? Life is too short to spend our time on doing that. Statement from the Release Team: https://lists.debian.org/debian-devel-announce/2023/12/msg3.html Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1085046: ITP: harec -- Hare compiler for POSIX-compatible systems
Package: wnpp Severity: wishlist Owner: Miguel Landaeta X-Debbugs-Cc: debian-devel@lists.debian.org, guilhe...@puida.xyz * Package name: harec Version : 0.24.2 Upstream Contact: Drew DeVault * URL : https://harelang.org/ * License : MPL-2.0 Programming Lang: C Description : Hare compiler for POSIX-compatible systems Hare is a systems programming language designed to be simple, stable and robust. Hare uses a static type system, manual memory management, and a minimal runtime. It is well suited to writing operating systems, system tools, compilers, networking software, and other low-level, high performance tasks. . This package installs the Hare compiler. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche
Re: Will i386 released for Trixie and if no can we stop working on it now?
On Sun, 13 Oct 2024 23:37:11 +0900, Charles Plessy wrote: >Le Sun, Oct 13, 2024 at 03:21:11PM +0100, Paul Gevers a écrit : >> >> https://lists.debian.org/debian-devel-announce/2023/12/msg3.html > >Thanks, I read it at the time but I did not understand the meaning: it means that packages will still be built for i386 unless their maintainer decides differently. There will probably be no i386 installer and no i386 kernel, but you still can have i386 in a container or as multiarch, both on amd64 host systems. >do you really expect that we progressively edit thousands of >debian/control files and file thousands of FTP removal bugs? I think that I will be way to lazy to drop i386 support for a package the builds on i386 and will run there. I do not expect that any of my packages will give me trouble on i386 for the time being. Greetings Marc -- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
Re: Will i386 released for Trixie and if no can we stop working on it now?
Le Sun, Oct 13, 2024 at 03:21:11PM +0100, Paul Gevers a écrit : > > https://lists.debian.org/debian-devel-announce/2023/12/msg3.html Thanks, I read it at the time but I did not understand the meaning: do you really expect that we progressively edit thousands of debian/control files and file thousands of FTP removal bugs? To be frank, the result of your current policy is that, defensively, I take the opportunity of dropping 32-bit support as a whole instead of i386 specifically because a) it is easier (just build depend on architecture-is-64-bit), and b) the prospect of re-doing for other 32-bit arches what we do for i386 is really making feel like running away from Debian. I am not complaining about effort to keep useful i386 packages in Debian, but about the lack of tools to remove the other i386 packages in a smarter ways. Can we not just have a way to send a signed email to a bot somewhere with a list of packages, and voilà, they are removed seamlessly and we can focus on other tasks? Have a nice day Chares -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://fediscience.org/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
