Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.devel > #108126
| From | Simon McVittie <smcv@debian.org> |
|---|---|
| Newsgroups | linux.debian.devel |
| Subject | Re: 64-bit time_t transition for 32-bit archs: a proposal |
| Date | 2023-06-08 11:40 +0200 |
| Message-ID | <GEkhz-etIm-7@gated-at.bofh.it> (permalink) |
| References | <GwgNP-9s1z-1@gated-at.bofh.it> <GDzsl-e0D6-3@gated-at.bofh.it> <GDCqd-e2j4-3@gated-at.bofh.it> <GEgxj-ervP-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 08 Jun 2023 at 11:19:15 +0800, Paul Wise wrote:
> On Tue, 2023-06-06 at 11:45 +0100, Simon McVittie wrote:
>
> > 2. i386 as a multiarch foreign architecture to run legacy binaries on
> > modern x86_64 systems
> > 2a. legacy native Linux i386 binaries
> > 2b. legacy Windows i386 binaries via Wine (which requires a somewhat
> > complete i386 Linux library stack)
>
> Would it be feasible to drop i386 but still support this use-case by
> requiring folks to use historical releases on archive.debian.org?
Not really, for two reasons. Suppose we had done as you suggest in trixie,
and then a user in 2030 tries to run legacy binaries.
- Multiarch co-installability requires a matching version, so you can't
co-install libc6:amd64 from 2030 with libc6:i386 from 2023. That would
mean requiring use of a pure i386 chroot/container to run i386 binaries,
which doesn't really work well for something like Steam or Wine that
wants to provide a mixed x86_64/i386 environment that can run x86_64
or i386 binaries interchangeably. Steam has both x86_64 and i386 games
available (most of which will never be recompiled or updated by their
developers), and Wine wants to provide an environment compatible
with modern Windows, which is essentially the same shape as amd64
Debian in terms of architecture support: it's an x86_64 OS (kernel,
services and core libraries) with a secondary i386 library stack
("WoW64" in Windows' case).
Debian-style multiarch or Fedora/Arch-style multilib is a much, much
more convenient way to handle legacy i386 binaries than a chroot or
container - there's a reason that essentially all distros supporting
x86_64 have one or the other of those.
Even if you use a container framework like Flatpak to run Steam,
it isn't an i386 container - in Debian terminology, it's an x86_64
container with i386 as a foreign architecture (and in fact the fd.o
Flatpak runtimes use Debian-style multiarch paths for this).
- For game-related use cases in particular, 2030 GPU models aren't going
to work with 2023 user-space graphics drivers (typically Mesa or
NVIDIA-proprietary) because the 2030 GPU didn't exist yet at the time
the 2023 driver was written, so if we don't compile a modern Mesa
for i386, all i386 programs will eventually lose the ability to do
accelerated graphics and end up using the 2023 version of llvmpipe.
smcv
Back to linux.debian.devel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-17 06:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-17 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal YunQiang Su <wzssyqa@gmail.com> - 2023-05-17 07:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 22:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Florian Lohoff <f@zz.de> - 2023-05-22 10:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 07:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Marco d'Itri <md@Linux.IT> - 2023-05-18 12:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-18 16:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Wookey <wookey@wookware.org> - 2023-05-18 18:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Olaf Titz <olaf@bigred.inka.de> - 2023-06-26 20:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-18 16:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2023-05-18 21:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Russ Allbery <rra@debian.org> - 2023-05-18 21:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-05-17 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 07:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-05-28 21:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Craig Small <csmall@debian.org> - 2023-05-17 14:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-17 17:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-05-18 03:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 21:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-05-19 05:40 +0200
i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 13:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Luca Boccassi <bluca@debian.org> - 2023-05-19 14:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 16:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "G. Branden Robinson" <g.branden.robinson@gmail.com> - 2023-05-19 16:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Colin Watson <cjwatson@debian.org> - 2023-05-19 16:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "G. Branden Robinson" <g.branden.robinson@gmail.com> - 2023-05-19 17:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 19:40 +0200
Re: i386 in the future Ivan Shmakov <ivan@siamics.net> - 2023-05-25 13:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Simon McVittie <smcv@debian.org> - 2023-05-19 17:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-19 18:00 +0200
partial support for i386 (Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal)) Michael Biebl <biebl@debian.org> - 2023-05-19 19:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Jonathan Carter <jcc@debian.org> - 2023-05-22 12:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-05-19 17:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-19 18:00 +0200
Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386 Ansgar <ansgar@43-1.org> - 2023-05-19 17:40 +0200
Re: Bug#1036358: release-notes: Debian 12 expected to be last release w/ installer for i386 Michael Biebl <biebl@debian.org> - 2023-05-19 19:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "Andrew M.A. Cater" <amacater@einval.com> - 2023-05-19 19:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Cyril Brulebois <kibi@debian.org> - 2023-05-19 19:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Michael Biebl <biebl@debian.org> - 2023-05-19 20:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 19:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Bjørn Mork <bjorn@mork.no> - 2023-05-19 21:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Ansgar <ansgar@43-1.org> - 2023-05-19 22:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Bjørn Mork <bjorn@mork.no> - 2023-05-19 22:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Cyril Brulebois <kibi@debian.org> - 2023-05-20 07:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-20 14:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Diederik de Haas <didi.debian@cknow.org> - 2023-05-31 01:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-31 06:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) John Goerzen <jgoerzen@complete.org> - 2023-05-31 14:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Sven Hoexter <sven@stormbind.net> - 2023-05-31 16:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Gunnar Wolf <gwolf@debian.org> - 2023-05-31 18:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Wookey <wookey@wookware.org> - 2023-05-31 20:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Ansgar <ansgar@43-1.org> - 2023-05-31 21:30 +0200
Re: Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Johannes Schauer Marin Rodrigues <josch@debian.org> - 2023-05-31 07:00 +0200
Re: Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-31 10:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Wouter Verhelst <wouter@debian.org> - 2023-05-31 12:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Alexandre Detiste <alexandre.detiste@gmail.com> - 2023-05-31 13:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Sven Hoexter <sven@stormbind.net> - 2023-05-31 16:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Gunnar Wolf <gwolf@debian.org> - 2023-05-31 18:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Diederik de Haas <didi.debian@cknow.org> - 2023-05-31 23:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "Andrew M.A. Cater" <amacater@einval.com> - 2023-06-01 00:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Adam Borowski <kilobyte@angband.pl> - 2023-06-01 15:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) nick black <dankamongmen@gmail.com> - 2023-06-02 19:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Wouter Verhelst <wouter@debian.org> - 2023-06-02 21:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Diederik de Haas <didi.debian@cknow.org> - 2023-06-02 23:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Paul Wise <pabs@debian.org> - 2023-06-01 03:40 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) "Theodore Ts'o" <tytso@mit.edu> - 2023-06-01 14:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com> - 2023-06-08 02:20 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve Langasek <vorlon@debian.org> - 2023-05-19 17:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Steve McIntyre <steve@einval.com> - 2023-05-19 19:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Guillem Jover <guillem@debian.org> - 2023-05-19 20:10 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-19 20:50 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Ansgar <ansgar@43-1.org> - 2023-05-20 00:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-21 08:00 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) Roger Lynn <Roger@rilynn.me.uk> - 2023-05-26 01:30 +0200
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal) James Addison <jay@jp-hosting.net> - 2023-05-26 06:50 +0200
Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Josh Triplett <josh@joshtriplett.org> - 2023-05-20 09:20 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Simon Richter <sjr@debian.org> - 2023-05-20 11:30 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Adam Borowski <kilobyte@angband.pl> - 2023-05-20 18:50 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] Stephen Kitt <skitt@debian.org> - 2023-05-21 20:00 +0200
Re: Using i386 by mistake on 64-bit hardware [was Re: i386 in the future 32-bit archs: a proposal)] James Addison <jay@jp-hosting.net> - 2023-05-22 14:30 +0200
Re: i386 in the future Wookey <wookey@wookware.org> - 2023-05-20 05:30 +0200
Re: i386 in the future Ansgar <ansgar@43-1.org> - 2023-05-20 10:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-23 03:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-06-08 04:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-06-14 06:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Guillem Jover <guillem@debian.org> - 2023-06-17 17:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-18 08:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-20 02:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Wookey <wookey@wookware.org> - 2023-05-20 13:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Andreas Metzler <ametzler@bebt.de> - 2023-05-20 17:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-23 03:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-05-23 03:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-06-06 09:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-06 12:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Luca Boccassi <bluca@debian.org> - 2023-06-06 13:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Marco d'Itri <md@Linux.IT> - 2023-06-06 17:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Gunnar Wolf <gwolf@debian.org> - 2023-06-06 20:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-06 21:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Alexis Murzeau <amubtdx@gmail.com> - 2023-06-06 21:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-08 21:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-07 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Andreas Metzler <ametzler@bebt.de> - 2023-06-08 07:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-08 21:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-08 07:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Bastien ROUCARIES <roucaries.bastien@gmail.com> - 2023-06-08 08:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Hakan Bayındır <hakan@bayindir.org> - 2023-06-08 10:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Holger Levsen <holger@layer-acht.org> - 2023-06-08 11:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-09 06:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Holger Levsen <holger@layer-acht.org> - 2023-06-09 11:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Ansgar <ansgar@43-1.org> - 2023-06-09 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Bastian Blank <waldi@debian.org> - 2023-06-08 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-08 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Gunnar Wolf <gwolf@debian.org> - 2023-06-08 17:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal nick black <dankamongmen@gmail.com> - 2023-06-09 01:30 +0200
Re: multiarch vs. multilib Simon McVittie <smcv@debian.org> - 2023-06-09 11:00 +0200
Re: multiarch vs. multilib nick black <dankamongmen@gmail.com> - 2023-06-11 10:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-09 05:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-09 11:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-09 06:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Bastian Blank <waldi@debian.org> - 2023-06-09 08:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Wookey <wookey@wookware.org> - 2023-07-05 18:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-06-06 21:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-07 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Helmut Grohne <helmut@subdivi.de> - 2023-06-08 19:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Holger Levsen <holger@layer-acht.org> - 2023-06-08 20:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-06-08 21:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-06-09 19:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Aurelien Jarno <aurel32@debian.org> - 2023-06-26 21:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal James Addison <jay@jp-hosting.net> - 2023-06-27 10:20 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-07-06 11:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-07-06 18:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-07-06 23:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-07-07 01:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Sam Hartman <hartmans@debian.org> - 2023-07-06 22:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Paul Wise <pabs@debian.org> - 2023-06-07 06:40 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Sune Vuorela <nospam@vuorela.dk> - 2023-06-07 09:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal "Peter Van Eynde" <pvaneynd@debian.org> - 2023-06-07 10:30 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Simon McVittie <smcv@debian.org> - 2023-06-07 12:50 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal The Wanderer <wanderer@fastmail.fm> - 2023-06-07 13:10 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Thorsten Glaser <tg@debian.org> - 2023-07-06 19:00 +0200
Re: 64-bit time_t transition for 32-bit archs: a proposal Steve Langasek <vorlon@debian.org> - 2023-07-06 19:20 +0200
[i386] adlibtracker2 and fp-units-i386 Ivan Shmakov <ivan@siamics.net> - 2023-06-07 15:40 +0200
Constructive contributions (was: Re: 64-bit time_t transition for 32-bit archs: a proposal) Jonathan Carter <jcc@debian.org> - 2023-06-09 13:30 +0200
csiph-web