On Fri, Oct 12, 2018 at 11:13:30PM +, Thorsten Glaser wrote:
As a (lapsed) porter for x32 here in Debian, I don't think it's worth
keeping. Despite all the touted benefits, no one uses the arch. There's a
That’s wrong. I’ve crossgraded my desktop at work to x32, with
M-A to i386 for a con
Eek! I only saw this by accident, as I’m also not subscribed to
d-devel.
>On Sat, Sep 29, 2018 at 07:48:09AM +0100, Ben Hutchings wrote:
>> - x32 has 64-bit time_t and that never worked quite right. This may
>> have finally been fixed this year by Arnd Bergmann's work, but I'm
>> not sure.
On 03.10.2018 18:01, John Paul Adrian Glaubitz wrote:
>> For s390x I can say that the port was driven without any commercial
>> interest on both Aurelien's and my side
> The question is though: Is there quantifiable amount of users that is
> running Debian on such big iron instead of one of the Lin
Hi Philipp!
On 10/3/18 4:29 PM, Philipp Kern wrote:
> Please excuse my ignorance, but which architecture do we still have with
> 2 GiB address space? The main point of removing s390 was that this was
> unsustainable.
The 32-bit MIPS architectures have this limitation which causes various
build is
ср, 3 окт. 2018 г. в 17:48, Jonathan Dowland :
>
> On Sat, Sep 29, 2018 at 05:05:17PM +0200, John Paul Adrian Glaubitz
> wrote:
> >Well, I have had people from IBM fix 32-bit PowerPC code. There is
> >naturally more involvement behind the 64-bit stuff because that's where
> >the commercial interest
On Sat, Sep 29, 2018 at 05:05:17PM +0200, John Paul Adrian Glaubitz
wrote:
Well, I have had people from IBM fix 32-bit PowerPC code. There is
naturally more involvement behind the 64-bit stuff because that's where
the commercial interests are.
The kernel itself dropped 32bit powerpc support yea
On 29.09.2018 00:30, John Paul Adrian Glaubitz wrote:
> On 9/28/18 11:26 PM, Adam D. Barratt wrote:
>> On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
>>> So, it's not always a purely technical decision whether a port
>>> remains a release architecture. It's also often highly po
On Sat, 2018-09-29 at 17:05 +0200, John Paul Adrian Glaubitz wrote:
> On 9/29/18 8:48 AM, Ben Hutchings wrote:
> > On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
> > [...]
> > > Furthermore, several of the ports are in very healthy condition and
> > > even surpass some release
On Sat, Sep 29, 2018 at 05:11:31PM +0200, John Paul Adrian Glaubitz wrote:
> On 9/29/18 12:02 PM, Adam Borowski wrote:
> > With primary use cases being hosting of multiple containers, and/or running
> > a large number-crunching cluster. Sacrificing lots of human hassle for a 7%
> > speed boost mak
On 9/29/18 12:02 PM, Adam Borowski wrote:
> With primary use cases being hosting of multiple containers, and/or running
> a large number-crunching cluster. Sacrificing lots of human hassle for a 7%
> speed boost makes you a "Gentoo ricer"[1] on a desktop/laptop, but could be
> a nice thing on a $1
On 9/29/18 8:48 AM, Ben Hutchings wrote:
> On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
> [...]
>> Furthermore, several of the ports are in very healthy condition and
>> even surpass some release architectures. The powerpc and ppc64 ports,
>> for example, build more packages
[trimmed cross-post]
On Sat, Sep 29, 2018 at 07:48:09AM +0100, Ben Hutchings wrote:
> On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
> > * x32: maintained by the people who maintain the x86 port of the kernel
>
> H. Peter Anvin did the original port in 2012, but so far as I
On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
[...]
> Furthermore, several of the ports are in very healthy condition and
> even surpass some release architectures. The powerpc and ppc64 ports,
> for example, build more packages than any of the mips* ports.
I would be very ha
On 9/28/18 11:26 PM, Adam D. Barratt wrote:
> On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
>> So, it's not always a purely technical decision whether a port
>> remains a release architecture. It's also often highly political and
>> somehow also influenced by commercial entiti
On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
> So, it's not always a purely technical decision whether a port
> remains a release architecture. It's also often highly political and
> somehow also influenced by commercial entities.
Please don't make implications like that unl
Hello!
I just saw this mail this morning by accident while browsing the
archives, I am not subscribed to debian-devel.
> The ftpmaster team would like to clarify which Debian ports should
and/or would like to continue to be part of Debian unstable and
experimental.
I'm not sure what context you
Hi,
With my debian-ports hat on, let me answer the parts related to that.
First of all as a reminder, debian-ports was originally just there to
help bootstrapping an architecture and prove it meets the ftpmasters
criteria to become an official architecture. It has been used that way
for example f
On Mon, 2018-09-03 at 01:07 +0200, Samuel Thibault wrote:
>
> > So has the debian patch been submitted in #900240 upstream by you or Petter
> > Reinholdtsen yet? I don't believe so!
>
> I don't think so either, it'd be marked forwarded. That doesn't mean you
> can't help with it.
Regardless who
Svante Signell, le lun. 03 sept. 2018 01:18:20 +0200, a ecrit:
> On Mon, 2018-09-03 at 01:07 +0200, Samuel Thibault wrote:
> >
> > > So has the debian patch been submitted in #900240 upstream by you or
> > > Petter
> > > Reinholdtsen yet? I don't believe so!
> >
> > I don't think so either, it'd
On Sun, Sep 02, 2018 at 11:39:08PM +0200, Svante Signell wrote:
> On Sun, 2018-09-02 at 19:46 +0200, Samuel Thibault wrote:
> > If it's not tricky, a NMU should be able to fix it easily.
>
> I'm sorry Samuel, I asked both you and James Clarke, Cc:ed, for help on this
> issue and you both said it w
Svante Signell, le lun. 03 sept. 2018 01:06:11 +0200, a ecrit:
> On Mon, 2018-09-03 at 00:19 +0200, Samuel Thibault wrote:
> > Felix Geyer wrote:
> > > I suggest that instead you respond to questions on bugs you opened.
> > > I'm not interested in maintaining patches for things that clearly
> > > b
On Mon, 2018-09-03 at 00:19 +0200, Samuel Thibault wrote:
>
> > I'm sorry Samuel, I asked both you and James Clarke, Cc:ed, for help on this
> > issue and you both said it was not possible to NMU cmake, even if you are
> > both
> > DD's.
>
> For my part, I was not talking about that patch, but ab
Svante Signell, le dim. 02 sept. 2018 23:39:08 +0200, a ecrit:
> On Sun, 2018-09-02 at 19:46 +0200, Samuel Thibault wrote:
> > Svante Signell, le dim. 02 sept. 2018 19:45:19 +0200, a ecrit:
> > > On Sun, 2018-09-02 at 15:21 +0200, Samuel Thibault wrote:
> > >
> > > >
> > > > > The statistics and
On Sun, 2018-09-02 at 19:46 +0200, Samuel Thibault wrote:
> Svante Signell, le dim. 02 sept. 2018 19:45:19 +0200, a ecrit:
> > On Sun, 2018-09-02 at 15:21 +0200, Samuel Thibault wrote:
> >
> > >
> > > > The statistics and graphs available on the debian-ports page[1] may
> > > > provide some objec
Svante Signell, le dim. 02 sept. 2018 19:45:19 +0200, a ecrit:
> On Sun, 2018-09-02 at 15:21 +0200, Samuel Thibault wrote:
>
> >
> > > The statistics and graphs available on the debian-ports page[1] may
> > > provide some objective statistics or reflection on the actual
> > > suitability of your
On Sun, 2018-09-02 at 15:21 +0200, Samuel Thibault wrote:
>
> > The statistics and graphs available on the debian-ports page[1] may
> > provide some objective statistics or reflection on the actual
> > suitability of your architecture's continued inclusion.
> > [1]: https://buildd.debian.org/sta
Hello,
Luke W Faraone, le lun. 27 août 2018 00:33:58 -0700, a ecrit:
> So, in the first instance, would you like to continue being part of
> unstable/experimental?
Well, I can simply point at what we said last time (IIRC) the question
was raised, here are the importants point we see in being on d
(resending with corrected address for debian-bsd)
Dear ports maintainer,
The ftpmaster team would like to clarify which Debian ports should
and/or would like to continue to be part of Debian unstable and
experimental.
As outlined on the Debian Archive Criteria page[0], the key points to
consider
Dear ports maintainer,
The ftpmaster team would like to clarify which Debian ports should
and/or would like to continue to be part of Debian unstable and
experimental.
As outlined on the Debian Archive Criteria page[0], the key points to
consider are whether the architecture has been part of a st
29 matches
Mail list logo
