Re: Porter roll call for Debian Stretch

On Sun, Oct 09, 2016 at 11:13:21PM +0100, Adam D. Barratt wrote: > On Sun, 2016-10-09 at 21:12 +0300, Adrian Bunk wrote: > > [ adding debian-powerpc ] > > > > On Sun, Oct 09, 2016 at 06:54:44PM +0200, Moritz Mühlenhoff wrote: > > > Niels Thykier schrieb: > > > > If I am to

Re: Porter roll call for Debian Stretch

On Sun, 2016-10-09 at 21:12 +0300, Adrian Bunk wrote: > [ adding debian-powerpc ] > > On Sun, Oct 09, 2016 at 06:54:44PM +0200, Moritz Mühlenhoff wrote: > > Niels Thykier schrieb: > > > If I am to support powerpc as a realease architecture for Stretch, I > > > need to know

Re: Porter roll call for Debian Stretch

[ adding debian-powerpc ] On Sun, Oct 09, 2016 at 06:54:44PM +0200, Moritz Mühlenhoff wrote: > Niels Thykier schrieb: > > If I am to support powerpc as a realease architecture for Stretch, I > > need to know that there are *active* porters behind it committed to > > keeping it

Re: Porter roll call for Debian Stretch

Niels Thykier schrieb: > If I am to support powerpc as a realease architecture for Stretch, I > need to know that there are *active* porters behind it committed to > keeping it in the working. People who would definitely catch such > issues long before the release. People who

Re: Porter roll call for Debian Stretch

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 answered the > > roll call for sparc and we

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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. However, we ended up with a

Re: Porter roll call for Debian Stretch

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 ended up with a completely broken and

Re: Porter roll call for Debian Stretch

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 > Jessie. However, we ended up

Re: Porter roll call for Debian Stretch

John Paul Adrian Glaubitz: > 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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

quot;v1" > From: John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> > To: Niels Thykier <ni...@thykier.net>, debian-po...@lists.debian.org > Cc: debian-release@lists.debian.org, debian-de...@lists.debian.org > Message-ID: <3e8c329c-85a2-7c29-f9ec-7fa071ab5...@physik

Re: Porter roll call for Debian Stretch

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 -

Re: Porter roll call for Debian Stretch

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 with a signed email

Re: Porter roll call for Debian Stretch

Aurelien Jarno: > On 2016-08-17 22:05, ni...@thykier.net wrote: >> 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 > Hi, Apologies for the tardiness on my part for this. > Does it really

Re: Porter roll call for Debian Stretch

I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretchj release (est. end of 2020): For mips, mipsel. mips64el I or my team at work - test (most|all) packages on this architecture - run a Debian testing or unstable system on port that I

Re: FTBFS with PIE & bindnow (was: Re: Porter roll call for Debian Stretch)

Hi, thanks for the work on this. I'd like to defer the final decision to the release team, however I'm not keen on having these defaults turned on architectures which already have enough issues on their own. In the recent porters call people claim that turning on these "should not be a problem"

FTBFS with PIE & bindnow (was: Re: Porter roll call for Debian Stretch)

Hi, First of all thanks to Lucas Nussbaum who ran the first test build! 2016-08-31 19:21 GMT+02:00 Steve Langasek : > On Wed, Aug 31, 2016 at 11:26:55AM +0100, Dimitri John Ledkov wrote: >> Hello, >> > Results are available at >> >

Re: Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For s390x, I - triage d-i bugs - test d-i regularly - fix d-i bugs/issues - am currently trying to get an automated test setup running for d-i -

RE: Porter roll call for Debian Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretchj release (est. end of 2020): For mips, mipsel and mips64el, I - can test all packages on this architecture on different hardware

Re: Porter roll call for Debian Stretch

-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 lifetime

Re: Porter roll call for Debian Stretch

On Wed, Aug 31, 2016 at 11:26:55AM +0100, Dimitri John Ledkov wrote: > Hello, > > Results are available at > > https://people.debian.org/~lucas/logs/2016/08/30/pie-bindnow-20160830/ > > I did a full rebuild with bindnow and PIE enabled, then rebuilt all > > failed packages with a pristine

Re: Porter roll call for Debian Stretch

Hi, 2016-08-31 12:26 GMT+02:00 Dimitri John Ledkov : > Hello, > > On 30 August 2016 at 23:07, Lucas Nussbaum wrote: >> On 22/08/16 at 19:12 +0200, Bálint Réczey wrote: >>> Hi Guillem, >>> >>> 2016-08-21 14:02 GMT+02:00 Guillem Jover : >>> >

Re: Porter roll call for Debian Stretch

Hello, On 30 August 2016 at 23:07, Lucas Nussbaum wrote: > On 22/08/16 at 19:12 +0200, Bálint Réczey wrote: >> Hi Guillem, >> >> 2016-08-21 14:02 GMT+02:00 Guillem Jover : >> > Hi! >> > >> > On Sun, 2016-08-21 at 10:24:42 +0200, Bálint Réczey wrote: >> >>

Re: Porter roll call for Debian Stretch

On 22/08/16 at 19:12 +0200, Bálint Réczey wrote: > Hi Guillem, > > 2016-08-21 14:02 GMT+02:00 Guillem Jover : > > Hi! > > > > On Sun, 2016-08-21 at 10:24:42 +0200, Bálint Réczey wrote: > >> I'm testing a set of patches [2] for gcc and dpkg which enable bindnow for > >> all >

Re: Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For ppc64el, I - test most packages on this architecture - run a Debian testing or unstable system on port that I use regularly - triage

Re: Porter roll call for Debian Stretch

Sorry for the previous post without signature. Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For mips, mipsel and mips64el, I - test most packages on this architecture - run a

Re: Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For mips, mipsel and mips64el, I - test most packages on this architecture - run a Debian testing or unstable system on port that I

Re: Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of Streth release (est. end of 2020): For mips, mipsel and mips64el, I - run several Debian testing/unstable system on real mipsel/mips64el hardware - maintain 3 mipsel/mips64el machines at

Re: Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretchj release (est. end of 2020): For mips, mipsel and mips64el, I - run a Debian testing system on a real mipsel machine that I use regularly - run a Debian stable system on a

Re: Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretchj release (est. end of 2020): For s390x, I - run a Debian testing system on an emulated s390x machine, that I use regularly - fix toolchain issues, though in practice there is

Re: Porter roll call for Debian Stretch

On 2016-08-17 22:05, ni...@thykier.net wrote: > 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 Does it really concerns *all* release architectures? Traditionally amd64 and i386 have been

RE: Porter roll call for Debian Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For mips, mipsel and mips64el, I - can test all packages on this architecture on different hardware

Re: Porter roll call for Debian Stretch

Hi, On 17/08/16 21:05, 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 lifetime of Debian Stretch (est. end of > 2020), please respond with a

Re: Porter roll call for Debian Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretchj release (est. end of 2020): For ppc64el, I - - test most packages on this architecture - - run a Debian testing or unstable

RE: Porter roll call for Debian Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For mips, mipsel and mips64el, I - can test all packages on this architecture on different hardware

Porter roll call for Debian Stretch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For ppc64el, I - - test most packages on this architecture - - run a Debian testing or unstable

Re: Porter roll call for Debian Stretch

On 08/22/2016 07:12 PM, Bálint Réczey wrote: > Hi Guillem, > > 2016-08-21 14:02 GMT+02:00 Guillem Jover : >> Hi! >> >> On Sun, 2016-08-21 at 10:24:42 +0200, Bálint Réczey wrote: >>> I'm testing a set of patches [2] for gcc and dpkg which enable bindnow for >>> all >>> arches

Re: Porter roll call for Debian Stretch

Hello Mattia, On Mon, Aug 22, 2016 at 03:51:17PM +, Mattia Rizzolo wrote: > On Mon, Aug 22, 2016 at 12:00:50PM -0300, Breno Leitao wrote: > > - maintain/provide hardware for automated tests on ci.d.n, > > jenkins.d.n (etc.) > > At jenkins.d.n we don't have any ppc64el slave; I don't know

Re: Porter roll call for Debian Stretch

Hi Guillem, 2016-08-21 14:02 GMT+02:00 Guillem Jover : > Hi! > > On Sun, 2016-08-21 at 10:24:42 +0200, Bálint Réczey wrote: >> I'm testing a set of patches [2] for gcc and dpkg which enable bindnow for >> all >> arches and PIE for amd64, ppc64el and s390x in sync with Ubuntu.

Re: Porter roll call for Debian Stretch

On Mon, Aug 22, 2016 at 12:00:50PM -0300, Breno Leitao wrote: > - maintain/provide hardware for automated tests on ci.d.n, > jenkins.d.n (etc.) At jenkins.d.n we don't have any ppc64el slave; I don't know whether you recently did private offers to Holger alone about this, but I was not

Porter roll call for Debian Stretch

Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Stretch release (est. end of 2020): For ppc64el, I - test most of the important packages on this architecture - run a Debian testing or unstable system on port that I use regularly -

Re: Porter roll call for Debian Stretch

On 2016-08-17 22:05 +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 lifetime of Debian Stretch (est. end of > 2020), please respond

Re: Porter roll call for Debian Stretch

Ian Campbell: > On Wed, 2016-08-17 at 22:05 +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] > > OOI does this relate somehow to the porter roll-call/architecture > qualification or was this just a

Re: Porter roll call for Debian Stretch

On Wed, 2016-08-17 at 22:05 +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] OOI does this relate somehow to the porter roll-call/architecture qualification or was this just a convenient mail to

Re: Porter roll call for Debian Stretch

Hi! On Sun, 2016-08-21 at 10:24:42 +0200, Bálint Réczey wrote: > I'm testing a set of patches [2] for gcc and dpkg which enable bindnow for all > arches and PIE for amd64, ppc64el and s390x in sync with Ubuntu. > > My assumption was that this set of architectures need the least amount of >

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

> I am an active porter for the following architectures and I intend > to continue this for the lifetime of the Stretch release (est. end > of 2020): Some people have suggested to me that I'm an active porter... maybe it just sort of happens to people. I'll likely continue to help in the

Re: Porter roll call for Debian Stretch

On Wed, Aug 17, 2016 at 10:05:06PM +0200, ni...@thykier.net wrote: > > * Which architectures are you committing to be an active porter for? > * Please describe recent relevant porter contributions. > * Are you running/using Debian testing or sid on said port(s)? > * Are you testing/patching d-i

Re: Porter roll call for Debian Stretch [arm]

* ni...@thykier.net [2016-08-17 22:05]: > * Which architectures are you committing to be an active porter for? > * Please describe recent relevant porter contributions. > * Are you running/using Debian testing or sid on said port(s)? For armel, armhf and arm64, I: * Triage

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

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

Re: Porter roll call for Debian Stretch

* 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

Porter roll call for Debian Stretch

-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