Sandro Tosi 于2022年1月14日周五 13:54写道：
>
> YunQiang,
>
> On Tue, Jan 4, 2022 at 9:48 AM PICCA Frederic-emmanuel
> wrote:
> >
> >
> > > > In case #1000435 (matplotlib crashes on mips64el) is not already on
> > > > your radar, would you please take a look?
> > > >
> > >
> > > Thank you. I will work on
YunQiang,
On Tue, Jan 4, 2022 at 9:48 AM PICCA Frederic-emmanuel
wrote:
>
>
> > > In case #1000435 (matplotlib crashes on mips64el) is not already on
> > > your radar, would you please take a look?
> > >
> >
> > Thank you. I will work on it right now.
>
> Hello, I just added some information abou
> > In case #1000435 (matplotlib crashes on mips64el) is not already on
> > your radar, would you please take a look?
> >
>
> Thank you. I will work on it right now.
Hello, I just added some information about this problem on this bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72
Hello,
2021-10-02 11:57 Graham Inggs:
Hi
We are doing a roll call for porters of all prospective release
architectures. If you are an active porter behind one of these
architectures [1] and intend to continue for the development cycle of
Debian Bookworm (est. release mid-2023), please respond
Graham Inggs 于2021年12月26日周日 21:58写道：
>
> Hi YunQiang Su
>
> On Sun, 26 Dec 2021 at 11:17, YunQiang Su wrote:
> >
> > For mipsel and mips64el, I
> > - test most packages on this architecture
> > - run a Debian testing or unstable system on port that I use regularly
> > - fix toolchain issu
On 2021-10-02, Graham Inggs wrote:
> * Which architectures are you committing to be an active porter for?
armhf, arm64
> * Please describe recent relevant porter contributions.
Maintaining u-boot (bootloader used on many arm64 and armhf plaforms),
arm-trusted-firmware (arm64 firmware), and oc
Hi YunQiang Su
On Sun, 26 Dec 2021 at 11:17, YunQiang Su wrote:
>
> For mipsel and mips64el, I
> - test most packages on this architecture
> - run a Debian testing or unstable system on port that I use regularly
> - fix toolchain issues
> - triage arch-specific bugs
> - fix arch-relat
For mipsel and mips64el, I
- test most packages on this architecture
- run a Debian testing or unstable system on port that I use regularly
- fix toolchain issues
- triage arch-specific bugs
- fix arch-related bugs
- triage d-i bugs
- test d-i regularly
- fix d-i bugs/issues
- m
Hi
A friendly reminder about the porter roll call for bookworm.
On Sat, 2 Oct 2021 at 11:57, Graham Inggs wrote:
> We are doing a roll call for porters of all prospective release
> architectures. If you are an active porter behind one of these
> architectures [1] and intend to continu
Inggs wrote:
> Hi
>
> We are doing a roll call for porters of all prospective release
> architectures. If you are an active porter behind one of these
> architectures [1] and intend to continue for the development cycle of
> Debian Bookworm (est. release mid-2023), please res
Hi
We are doing a roll call for porters of all prospective release
architectures. If you are an active porter behind one of these
architectures [1] and intend to continue for the development cycle of
Debian Bookworm (est. release mid-2023), please respond with a signed
email containing the
On Sun, Dec 06, 2020 at 01:03:17PM +0100, Matthias Klose wrote:
> On 12/1/20 5:02 AM, YunQiang Su wrote:
> > I am sorry for the later response.
> >Hi,
> >
> > I am an active porter for the following architectures and I intend
> > to continue this for the lifetime of the Bullseye release (
Hi,
sorry for the late reply and thanks a lot Graham for pinging me
directly. I didn't monitor -devel closely lately, but
I am an active porter for the following architecture and I intend
to continue this for the lifetime of the Bullseye release (est. end
of 2024):
For ppc64el, I
- test most pack
On 2020-11-02 22:23 +0200, Graham Inggs wrote:
> Hi
>
> We are doing a roll call for porters of all release architectures. If
> you are an active porter behind one of the release architectures [1]
> for the entire lifetime of Debian Bullseye (est. end of 2024), please
> res
On Sun, Dec 06, 2020 at 01:03:17PM +0100, Matthias Klose wrote:
> On 12/1/20 5:02 AM, YunQiang Su wrote:
> > I am sorry for the later response.
> >Hi,
> >
> > I am an active porter for the following architectures and I intend
> > to continue this for the lifetime of the Bullseye release (
On 12/1/20 5:02 AM, YunQiang Su wrote:
> I am sorry for the later response.
>Hi,
>
> I am an active porter for the following architectures and I intend
> to continue this for the lifetime of the Bullseye release (est. end
> of 2024):
>
> For mipsel and mips64el, I
> - test most pac
On 2020-11-20, Graham Inggs wrote:
> A friendly reminder about the porter roll call for bullseye.
>
> On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote:
>> We are doing a roll call for porters of all release architectures. If
>> you are an active porter behind one of the rel
Hi
A friendly reminder about the porter roll call for bullseye.
On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote:
> We are doing a roll call for porters of all release architectures. If
> you are an active porter behind one of the release architectures [1]
> for the entire lifetime
Hi
We are doing a roll call for porters of all release architectures. If
you are an active porter behind one of the release architectures [1]
for the entire lifetime of Debian Bullseye (est. end of 2024), please
respond with a signed email containing the following before Friday,
November 27
On Sat, 2016-10-01 at 15:48 +0200, John Paul Adrian Glaubitz wrote:
> On 10/01/2016 02:17 PM, Ben Hutchings wrote:
> >
> > >
> > > This isn't the case for PowerPC32 where upstream development is still very
> > > active because it's part of the PowerPC kernel which is maintained by
> > > IBM.
> >
On Fri, 2016-09-30 at 22:34 +0200, John Paul Adrian Glaubitz wrote:
> On 09/30/2016 09:04 PM, Niels Thykier wrote:
> >
> > As for "porter qualification"
> > =
> >
> > We got burned during the Jessie release, where a person
On Sat, 2016-10-01 at 02:28 +0200, Adam Borowski wrote:
> On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote:
[...]
> > I have not heard from the ppc64el porters, but I suspect ppc64 will
> > not be a release arch. So you need to take into consideration that for
> > powerpc to remain
On Sat, Oct 1, 2016 at 2:28 AM, Adam Borowski wrote:
> On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote:
>> On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz
>> wrote:
>> [...]
>> > On the other hand, some packages dropped support for PowerPC32 like Mono
>> > but this i
On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote:
> On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz
> wrote:
> [...]
> > On the other hand, some packages dropped support for PowerPC32 like Mono
> > but this isn't a concern for most users, I would say.
> [...]
>
> Howe
On 09/20/2016 05:46 PM, John Paul Adrian Glaubitz wrote:
> On 09/20/2016 11:16 PM, Niels Thykier wrote:
>>- powerpc: No porter (RM blocker)
>
> I'd be happy to pick up powerpc to keep it for Stretch. I'm already
> maintaining powerpcspe which is very similar to powerpc.
>
Thank you Adrian f
Adrian,
On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz
wrote:
[...]
> On the other hand, some packages dropped support for PowerPC32 like Mono
> but this isn't a concern for most users, I would say.
[...]
Thanks very much for stepping up as porter, you have my vote !
However I need
On 09/30/2016 09:04 PM, Niels Thykier wrote:
> As for "porter qualification"
> =
>
> We got burned during the Jessie release, where a person answered the
> roll call for sparc and we kept sparc as a release architecture for
> Jessie.
Niels Thykier:
> [...]
>
> As for "porter qualification"
> =
>
> We got burned during the Jessie release, where a person answered the
> roll call for sparc and we kept sparc as a release architecture for
> Jessie. However, we end
On Fri, 2016-09-30 at 19:04 +, Niels Thykier wrote:
> As for "porter qualification"
> =
>
> We got burned during the Jessie release, where a person answered the
> roll call for sparc and we kept sparc as a release architecture for
> J
ch was "Assume there are no powerpc porters
for Stretch".
As for "porter qualification"
=====
We got burned during the Jessie release, where a person answered the
roll call for sparc and we kept sparc as a release architecture for
Jessie. However, we e
On Fri, Sep 30, 2016 at 10:03:47AM +0200, Mathieu Malaterre wrote:
> [Let's assume that we can't find a powerpc porter in time for Stretch.]
Two potential porters stepped up, who might or might not be accepted.
> 1. Will `powperpc` automatically be downgraded to simple port ? Or is
> this also no
On 09/30/2016 06:08 PM, Niels Thykier wrote:
> I strongly /suspect/ that "no porters" for powerpc will imply the
> removal of powerpc for Stretch. It may or may not be moved to ports
> (assuming someone is willing to support it there).
So, I take this as a "no" for the offer from me and Christoph
Mathieu Malaterre:
> Hi all,
>
> [...]
>
> [Let's assume that we can't find a powerpc porter in time for Stretch.]
>
> 1. Will `powperpc` automatically be downgraded to simple port ? Or is
> this also not automated and the port may simply be removed (eg. sparc)
> ?
> 2. Apart from loosing the au
You have a porter for PowerPC. See email from Adrian. ;-)
-- Christian
Sent from my iPhone
> On 30 Sep 2016, at 10:03, Mathieu Malaterre wrote:
>
> Hi all,
>
>> On Fri, Sep 23, 2016 at 3:54 PM, Matthias Klose wrote:
>>> On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote:
On 09/20/2016
Hi all,
On Fri, Sep 23, 2016 at 3:54 PM, Matthias Klose wrote:
> On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote:
>> On 09/20/2016 11:16 PM, Niels Thykier wrote:
>>>- powerpc: No porter (RM blocker)
>>
>> I'd be happy to pick up powerpc to keep it for Stretch. I'm already
>> maintaining
John Paul Adrian Glaubitz wrote...
> On 09/20/2016 11:16 PM, Niels Thykier wrote:
> >- powerpc: No porter (RM blocker)
>
> I'd be happy to pick up powerpc to keep it for Stretch. I'm already
> maintaining powerpcspe which is very similar to powerpc.
For somewhat personal reasons I'm interest
On 09/23/2016 03:54 PM, Matthias Klose wrote:
> No, you are not maintaining powerpcspe as a release architecture, and that's
> something different than building packages for some of the ports
> architectures.
> If you can get powerpcspe accepted as a release architecture, then maybe you
> gain som
On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote:
> On 09/20/2016 11:16 PM, Niels Thykier wrote:
>>- powerpc: No porter (RM blocker)
>
> I'd be happy to pick up powerpc to keep it for Stretch. I'm already
> maintaining powerpcspe which is very similar to powerpc.
No, you are not maintaini
On 09/21/2016 08:41 AM, Riku Voipio wrote:
> AFAIK Address space randomizing is not really helpful on 32 bit
> architectures - there is just not that many places to randomize to[1].
Well, sure, but there's still a huge difference in an explot with
100% reliability, or an exploit that will just cr
On Tue, Sep 20, 2016 at 09:16:00PM +, Niels Thykier wrote:
> Over all, most people (who answered it) was positive towards the switch.
> Based on this, I suspect that if we make PIE default in Stretch, then
> we will do it for all architectures. That said, you will be notified if
> that defaul
On 09/20/2016 11:16 PM, Niels Thykier wrote:
>- powerpc: No porter (RM blocker)
I'd be happy to pick up powerpc to keep it for Stretch. I'm already
maintaining powerpcspe which is very similar to powerpc.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian
ni...@thykier.net:
> Hi,
>
> Like last release, we are doing a roll call for porters of all release
> architectures. If you are an active porter behind one of the [release
> architectures] for the entire lifetime of Debian Stretch (est. end of
> 2020), please respond w
On 15.09.2016 22:43, Helge Deller wrote:
> Hi Matthias,
>
> On 10.09.2016 00:48, Matthias Klose wrote:
>> While the Debian Release team has some citation about the quality of the
>> toolchain on their status page, it is not one of the release criteria
>> documented
>> by the release team. I'd li
Hi Matthias,
On 10.09.2016 00:48, Matthias Klose wrote:
> While the Debian Release team has some citation about the quality of the
> toolchain on their status page, it is not one of the release criteria
> documented
> by the release team. I'd like to document the status how I do understand it
>
On 10.09.2016 09:59, Paul Gevers wrote:
> Hi,
>
> On 10-09-16 00:48, Matthias Klose wrote:
>> - fpc not available on powerpc anymore (may have changed recently)
>
> For whatever it is worth, this was finally fixed this week. It is
> missing on mips*, ppc64el and s390x though, while at least some
On 09/10/2016 12:48 AM, Matthias Klose wrote:
> Uncovered by the upstream primary and secondary platforms are the mips*
> architectures and powerpc. For the uncovered archs I would expect somehow
> more
> and pro-active Debian maintenance, however I fail to see this happen.
>
> - see the histor
Hi,
On 10-09-16 00:48, Matthias Klose wrote:
> - fpc not available on powerpc anymore (may have changed recently)
For whatever it is worth, this was finally fixed this week. It is
missing on mips*, ppc64el and s390x though, while at least some form of
MIPS is supported upstream.
Paul
signatu
While the Debian Release team has some citation about the quality of the
toolchain on their status page, it is not one of the release criteria documented
by the release team. I'd like to document the status how I do understand it for
some of the toolchains available in Debian.
I appreciate that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 17 Aug 2016 22:05:06 +0200
ni...@thykier.net wrote:
> Like last release, we are doing a roll call for porters of all release
> architectures. If you are an active porter behind one of the [release
> architectures] for the entire
Hi!
On Sun, 2016-08-21 at 08:22:09 +0200, Niels Thykier wrote:
> Kurt Roeckx:
> > On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote:
> >> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
> >>also apply to this port? [0]
> >
> > If -fPIE is the default
Hi,
2016-08-21 8:22 GMT+02:00 Niels Thykier :
> Kurt Roeckx:
>> On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote:
>>> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
>>>also apply to this port? [0]
>>
>> If -fPIE is the default will -fPIC override it
Kurt Roeckx:
> On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote:
>> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
>>also apply to this port? [0]
>
> If -fPIE is the default will -fPIC override it?
>
> It will also default to tell the linker to use
On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote:
> * If we were to enable -fPIE/-pie by default in GCC-6, should that change
>also apply to this port? [0]
If -fPIE is the default will -fPIC override it?
It will also default to tell the linker to use -pie, but then
don't do
Martin Michlmayr:
> * ni...@thykier.net [2016-08-17 22:05]:
>> 2020), please respond with a signed email containing the following
>> before Friday, the 9th of September:
>
> Can you please specify where to respond to? I don't think dozens of
> emails to -ports and -devel make any sense.
>
Ah,
* ni...@thykier.net [2016-08-17 22:05]:
> 2020), please respond with a signed email containing the following
> before Friday, the 9th of September:
Can you please specify where to respond to? I don't think dozens of
emails to -ports and -devel make any sense.
Maybe debian-release with CC debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Like last release, we are doing a roll call for porters of all release
architectures. If you are an active porter behind one of the [release
architectures] for the entire lifetime of Debian Stretch (est. end of
2020), please respond with a
Hello!
On 09/25/2013 05:09 AM, Nobuhiro Iwamatsu wrote:
> I am an active porter for the following architectures and I intend
> to continue this for the lifetime of the jessie release:
>
> For sh4, I
> - test packages on this architecture
> - triage arch-specific bugs
> - fix arch-related bugs
> -
在 2014年1月21日，下午9:51，Aníbal Monsalve Salazar 写道：
> On Tue, Jan 21, 2014 at 01:43:55PM +0100, Matthias Klose wrote:
>> Am 16.01.2014 13:31, schrieb Aníbal Monsalve Salazar:
>>> For mips/mipsel, I - fix toolchain issues together with other
>>> developers at ImgTec
>>
>> It is nice to see such a co
On Tue, Jan 21, 2014 at 01:43:55PM +0100, Matthias Klose wrote:
> Am 16.01.2014 13:31, schrieb Aníbal Monsalve Salazar:
>> For mips/mipsel, I - fix toolchain issues together with other
>> developers at ImgTec
>
> It is nice to see such a commitment, however in the past I didn't see
> any such cont
Am 16.01.2014 13:31, schrieb Aníbal Monsalve Salazar:
> For mips/mipsel, I - fix toolchain issues together with other developers at
> ImgTec
It is nice to see such a commitment, however in the past I didn't see any such
contributions.
Matthias
--
To UNSUBSCRIBE, email to debian-sparc-requ...
Hi,
Just for the record.
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For mips/mipsel, I
- test packages on these architectures on my own machines at home and at
ImgTec
- fix toolchain issues together with other dev
...@lists.debian.org
Cc: debian-de...@lists.debian.org; debian-po...@lists.debian.org;
debian-m...@lists.debian.org; Dragoslav Sicarov; Jurica Stanojkovic; Petar
Jovanovic
Subject: Re: Roll call for porters of architectures in sid and testing
Hi everyone,
I am part of the group of MIPS porters, and we missed
...@lists.debian.org
Cc: debian-de...@lists.debian.org; debian-po...@lists.debian.org;
debian-m...@lists.debian.org; Dragoslav Sicarov; Jurica Stanojkovic; Petar
Jovanovic
Subject: Re: Roll call for porters of architectures in sid and testing
Hi everyone,
I am part of the group of MIPS porters, and
Hi everyone,
I am part of the group of MIPS porters, and we missed to officially
respond to this email. Here is for the record:
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For MIPS,MIPSEL,MIPS64,MIPS64EL, I
On Wed, Oct 02, 2013 at 04:07:25PM +0100, Wookey wrote:
> +++ Niels Thykier [2013-10-02 09:45 +0200]:
> > armel: Wookey (DD), Gatis Visnevskis (!DD), Nobuhiro Iwamatsu (DD), Steve
> > McIntyre (DD)
> > armhf: Jeremiah Foster (!DD, but NM?), Wookey (DD), Justus Winter (!DD),
> > Lennart Sorensen (
On Sun, Sep 01, 2013 at 09:33:51AM +0200, Niels Thykier wrote:
> If you are (or intend to become) an active porter for the lifetime of
> jessie, then please send a signed email explaining your involvement in
> the port to the Release Team before
> 1st of October 2013. Please explain the level of y
(!DD),
> Robert Millan (DD), Steven Chamberlain (!DD), Guillem Jover (DD)
> mips: Graham Whaley (!DD), Andreas Barth (DD)
> mipsel: Graham Whaley (!DD), Andreas Barth (DD)
> powerpc: [Roger Leigh (DD)], Geoff Levand (!DD), Lennart Sorensen (!DD)
> sparc: Axel Beckert (DD)
>
>
On Wed, Oct 02, 2013 at 10:59:26AM +0200, Ansgar Burchardt wrote:
> On 10/02/2013 09:45, Niels Thykier wrote:
> > Summary table:
> > Arch || DDs || NMs/DMs || Other || Total
> > ---++-++-++---++--
> [...]
> > sparc[2] || 1 || 0 || 0 ||
Hi,
On Thu, Oct 03, 2013 at 02:09:18PM +0200, Axel Beckert wrote:
> Hi,
>
> Michael Cree wrote:
> > On Thu, Oct 03, 2013 at 01:06:01AM +0200, Axel Beckert wrote:
> > > Julien Cristau wrote:
> > > > On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> > > > > Yesterday I tried to setup a
Hi,
Michael Cree wrote:
> On Thu, Oct 03, 2013 at 01:06:01AM +0200, Axel Beckert wrote:
> > Julien Cristau wrote:
> > > On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> > > > Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> > > > my Sparcs, but the currently do
On Thu, Oct 03, 2013 at 01:06:01AM +0200, Axel Beckert wrote:
> Julien Cristau wrote:
> > On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> > > Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> > > my Sparcs, but the currently documented way[1] to do so failed[2]
Him
Julien Cristau wrote:
> On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> > Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> > my Sparcs, but the currently documented way[1] to do so failed[2] due
> > to outdated packages. On a first glance it looks like mis
On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> my Sparcs, but the currently documented way[1] to do so failed[2] due
> to outdated packages. On a first glance it looks like missing BinNMUs
> for the Perl 5.14 t
I'm interesting in helping on ia64. I'm not fluent in ia64 assembly, but I
can get around pretty well. I'm very experienced in C/C++/Java and
debugging. I've got a fully functional system running Xorg/Mesa3D/sound, so
I can reproduce, test, and fix issues as time permits.
Patrick Baggett
On Wed,
Hello, all.
I am not currently a porter but I would like to be one for the s390x
architecture.
I am familiar with zSeries system programming and have a lot of
experience in running Linux in virtual environments, mostly z/VM on
large IBM processors.. I use Linux for 11 year, family with cross
co
On Wed, Oct 02, 2013 at 04:07:25PM +0100, Wookey wrote:
>+++ Niels Thykier [2013-10-02 09:45 +0200]:
>> Hi,
>>
>> The final results are in:
>>
>> Summary table:
>> Arch || DDs || NMs/DMs || Other || Total
>> ---++-++-++---++--
>> armel || 3 ||
+++ Niels Thykier [2013-10-02 09:45 +0200]:
> Hi,
>
> The final results are in:
>
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
> armel || 3 || 0 || 1 ||4
> armhf || 3 || 1 ||
Add me for armel.
Bastien
Le 2 oct. 2013 09:46, "Niels Thykier" a écrit :
> Hi,
>
> The final results are in:
>
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
> armel || 3 || 0 || 1 ||4
> armhf
Hi,
[I've replaced debian-ports with debian-sparc in the recipients list]
Niels Thykier wrote:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
[…]
> sparc[2] || 1 || 0 || 0 ||1
[…]
> [2] By the looks of it, if sparc w
On 10/02/2013 09:45, Niels Thykier wrote:
> Summary table:
> Arch || DDs || NMs/DMs || Other || Total
> ---++-++-++---++--
[...]
> sparc[2] || 1 || 0 || 0 ||1
>
> [2] By the looks of it, if sparc was replaced by sparc64, we could be
>
off Levand (!DD), Lennart Sorensen (!DD)
sparc: Axel Beckert (DD)
Maybes for ia64 (?): Martin Lucina (!DD), Émeric MASCHINO (!DD), Mark Wickens
(!DD)
(Some inaccuracies can occur in the (xN) below; /me got confused and may have
lost count for some of them)
Items suggested in the roll
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For sh4, I
- test packages on this architecture
- triage arch-specific bugs
- fix arch-related bugs
- maintain buildds
For armel and armhf, I
- test packages on this ar
Hi,
I am not currently a porter but I would like to be one for the Hurd.
I do some test on QEMU and public Hurd host.
I am familiar with system programming and have some embedded and printer
driver development experience. I use Linux for 11 year, family with cross
compiling tool chain.
I never
Hi,
b...@decadent.org.uk said:
> > I've also provided a couple of kernel patches in the past. I'm cross
> > testing with Gentoo to ensure that bugs I report are Debian-specific
> > or ia64-generic.
> >
> > I'll continue testing/software development activity on ia64 for the
> > Jessie cycle, and m
Hello,
I am an active tester/user for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For powerpc, ppc64, I
- test most base packages on this architecture
- test d-i on this architecture
- follow debian-powerpc on at least a daily basis
-
On 21-Sep-13, at 7:23 PM, Ben Hutchings wrote:
I'll continue testing/software development activity on ia64 for the
Jessie cycle, and more generally, until Debian drops ia64. I'm
already
waiting for Wayland on ia64 and other big updates.
So please, keep ia64 in the bandwagon ;-)
But I don't
On Sat, 2013-09-21 at 19:36 +0200, Émeric MASCHINO wrote:
> Hi,
>
> I'm a long-time ia64 Debian user (> 10 years). I'm mostly focused on
> desktop aspects (GNOME, Iceweasel, LibreOffice, Qt Creator, C++ 3D
> software development) while most other ia64 users that I know are more
> inclined on serve
Hi,
Although I'm not a DD/DM, I currently do the majority of the Debian
unstable package
builds for parisc. As noted by Helge, these are available at www.parisc-linux.org
. While
not fully complete, the archive contains several thousand packages
that are constantly
being updated. We are
Hi,
I'm a long-time ia64 Debian user (> 10 years). I'm mostly focused on
desktop aspects (GNOME, Iceweasel, LibreOffice, Qt Creator, C++ 3D
software development) while most other ia64 users that I know are more
inclined on server use.
I'm not a DD/DM, but daily update my ia64 workstation, report
On Fri, Sep 20, 2013 at 11:19:24AM -0400, Federico Sologuren wrote:
> i have a HP Visualize B2000 that i managed to install last night from iso
> distribution that i found after a lot of looking. at this point only
> terminal is working. will keep reading to get debian up and running.
>
> i would
i have a HP Visualize B2000 that i managed to install last night from iso
distribution that i found after a lot of looking. at this point only
terminal is working. will keep reading to get debian up and running.
i would like to get involved. will need some additional information on what
is needed
software software
engineer
Sent from Samsung Mobile
Original message
From: Gasha
Date: 09/20/2013 9:32 AM (GMT+00:00)
To: Debian Release Team
Cc: debian-po...@lists.debian.org,debian-de...@lists.debian.org
Subject: Re: Roll call for porters of architectures in sid and testing
FWIW, I am a porter of the Alpha architecture in the following ways:
- run a buildd
- kernel support
- work with upstreams for toolchain support
- general porting work including filing bugs and patches
I doubt if I will continue that for the life cycle of Jessie given that
many of the former
Hi,
I am an active tester (not always porter) for the following architectures and I
intend
to continue this for the lifetime of the jessie release:
i386, amd64, armel
- test most base packages on this architecture (every day tasks)
- test arch-related things
- test lots of ipv6 related issues
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm particularly keen to see communication packages working on as many
architectures as possible because otherwise two-way communications
opportunities are missed if some users are excluded.
In short, I'm not formally volunteering, but if people
On Thu, Sep 19, 2013 at 10:38:29AM +0200, Niels Thykier wrote:
> Here is a little status update on the mails we have received so far.
> First off, thanks to all the porters who have already replied!
>
> So far, the *no one* has stepped up to back the following architectures:
>
>hurd-i386
>
On Sun, 2013-09-01 at 09:33 +0200, Niels Thykier wrote:
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For hurd-i386, I
- test most packages on this architecture
- fix toolchain issues
- triage arch-specific bugs
- f
Hi!
I'm not a DD or DM, but an upstream contributor and maintainer for the
toolchain, both for different things at work, and in my free time for the
Hurd. I have no plans to stop this, so this will cover the jessie
lifetime. As time permits, I also work on the Hurd itself, and advise
contributor
pefully teach me to remember to include the "in unstable"
restriction to the next "roll call". :) Anyhow, if you are working on
these architectures on debian-ports and saw a new name in the list
above, this might be an opportunity to recruit new people.
We also received a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am not currently a porter but I would like to be one for the
architecture parisc/hppa.
I currently have lots of parisc hardware (5 workstations and 4 servers),
all currently running debian unstable from our own debian repository
at www.pari
1 - 100 of 109 matches
Mail list logo
