Package: wnpp
Severity: wishlist
Owner: Didier 'OdyX' Raboud
X-Debbugs-Cc: debian-devel@lists.debian.org
Package name: typesense
Version : 0.24.1
Upstream Contact: TypeSense team
URL : https://typesense.org
License : GPL-3
Programming Lang: C++
Typo-t
On Tue, 2023-06-06 at 12:45 -0700, Steve Langasek wrote:
> since we don't really have an "i386 porting team"
The release team have registered Adrian Bunk as an i386 porter:
https://release.debian.org/testing/arch_spec.yaml
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Descript
On Tue, 2023-06-06 at 09:33 +0200, Helmut Grohne wrote:
> I've been reading the discussion around i386 a bit and found the
> direction it has taken a little unproductive.
I note that there are a number of packages available on i386 but not
available on amd64, is anyone planning on an MBF about th
On Tue, 2023-06-06 at 11:45 +0100, Simon McVittie wrote:
> When considering the future of i386, a factor that we need to bear in
> mind is that there are two major use-cases for i386, with requirements
> that sometimes conflict:
There was another option mentioned earlier in the thread that could
CONFIRM s2023060623370725133
On Tue, 06 Jun 2023 at 12:27:56 -0600, Gunnar Wolf wrote:
> there is the possible
> case of people running I-don't-know-which proprietay productivity tool
> provided as a binary that cannot be convinced of a 64-bit time_t that
> will receive errors when the timeocalypse approaches
Sure, and that's
Hi Helmut,
On Tue, Jun 06, 2023 at 09:33:22AM +0200, Helmut Grohne wrote:
> On Tue, May 16, 2023 at 09:04:10PM -0700, Steve Langasek wrote:
> > * … but NOT on i386. Because i386 as an architecture is primarily of
> > interest for running legacy binaries which cannot be rebuilt against a new
> >
Hi,
On 06/06/2023 12:45, 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 st
Simon McVittie dijo [Tue, Jun 06, 2023 at 11:45:26AM +0100]:
> On Tue, 06 Jun 2023 at 09:33:22 +0200, Helmut Grohne wrote:
> > Judging from the conversation, killing i386 quite obviously is desired
> > by some participants, but evidently not by all. How quickly we want to
> > kill it is not obvious
Package: wnpp
Severity: wishlist
Owner: Michel Alexandre Salim
X-Debbugs-Cc: debian-devel@lists.debian.org, mic...@michel-slm.name
* Package name: damo
Version : 1.8.3
Upstream Contact: SeongJae Park
* URL : https://damonitor.github.io/
* License : GPL
Progr
On Jun 06, Simon McVittie wrote:
> When considering the future of i386, a factor that we need to bear in
> mind is that there are two major use-cases for i386, with requirements
> that sometimes conflict:
Agreed. I will be more blunt: an i386 port which cannot run old i386
binaries would be almo
Package: wnpp
Severity: wishlist
Owner: Athos Ribeiro
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: php-fig-log-test
Version : 1.1.0
Upstream Contact: Anton Ukhanev
* URL : https://github.com/php-fig/log-test
* License : Expat
Programming Lang:
On Tue, 6 Jun 2023 at 11:46, Simon McVittie wrote:
>
> On Tue, 06 Jun 2023 at 09:33:22 +0200, Helmut Grohne wrote:
> > Judging from the conversation, killing i386 quite obviously is desired
> > by some participants, but evidently not by all. How quickly we want to
> > kill it is not obvious to me.
On Tue, 06 Jun 2023 at 09:33:22 +0200, Helmut Grohne wrote:
> Judging from the conversation, killing i386 quite obviously is desired
> by some participants, but evidently not by all. How quickly we want to
> kill it is not obvious to me.
When considering the future of i386, a factor that we need t
Hi Steve,
On Tue, May 16, 2023 at 09:04:10PM -0700, Steve Langasek wrote:
> * … but NOT on i386. Because i386 as an architecture is primarily of
> interest for running legacy binaries which cannot be rebuilt against a new
> ABI, changing the ABI on i386 would be counterproductive, as mentione
15 matches
Mail list logo
