Re: [Stretch] Status for architecture qualification

2016-06-14 Thread Emilio Pozuelo Monfort
On 14/06/16 09:06, Philipp Kern wrote: > On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote: >> Philipp Kern: >>> On 2016-06-05 12:01, Niels Thykier wrote: * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el, s390x - *No* blockers at this time from RT

Re: [Stretch] Status for architecture qualification

2016-06-28 Thread Emilio Pozuelo Monfort
On 16/06/16 02:12, Hector Oron wrote: > I have put up the classical wiki page for Stretch at: > https://wiki.debian.org/ArchiveQualification/Stretch > > Please review and comment if required. That page is now outdated wrt mips concerns (see below). Do we need to duplicate the information that w

Re: Bug#895193: transition: openmpi

2018-04-13 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed On 11/04/18 11:12, Alastair McKinstry wrote: > > > On 11/04/2018 10:07, John Paul Adrian Glaubitz wrote: >> On 04/11/2018 10:53 AM, Alastair McKinstry wrote: >>> As of 3.0.1, openmpi now works on Big-Endian powerpc (which was to be a >>> problem; it had been dropped up

Re: Debian/ppc64el feasiability to become an official architecture

2014-07-28 Thread Emilio Pozuelo Monfort
On 25/07/14 01:14, peter green wrote: > When you are added to testing you will be added as a "broken and fucked" > (release team's terminology not mine) architecture. To get out of this state > you > will need to get and keep your port in a healthy state in testing. That will > mean fixing (in som

Re: Debian/ppc64el feasiability to become an official architecture

2014-07-28 Thread Emilio Pozuelo Monfort
On 28/07/14 22:35, Emilio Pozuelo Monfort wrote: > On 25/07/14 01:14, peter green wrote: >> When you are added to testing you will be added as a "broken and fucked" >> (release team's terminology not mine) architecture. To get out of this state >> you >>

Re: binNMUs: please exercise some care

2015-10-23 Thread Emilio Pozuelo Monfort
[ Sorry for the cross-post, but I believe the people in -release and -wb-team should see this ] On 23/10/15 09:05, Thorsten Glaser wrote: > Hi, > > whoever is scheduling binNMUs now should do so with a little > bit more care, please. > > Case in point, frameworkintegration – x32 already was rebu

Re: binNMUs: please exercise some care

2015-10-23 Thread Emilio Pozuelo Monfort
On 23/10/15 11:20, Thorsten Glaser wrote: > On Fri, 23 Oct 2015, Emilio Pozuelo Monfort wrote: > >> I can go back to scheduling binNMUs for release architectures only, or for >> ANY >> -x32. But I don't have the time to look at every architecture and determine &g

Re: binNMUs: please exercise some care

2015-10-23 Thread Emilio Pozuelo Monfort
On 23/10/15 12:23, Wookey wrote: > +++ Emilio Pozuelo Monfort [2015-10-23 11:49 +0200]: >> On 23/10/15 11:20, Thorsten Glaser wrote: > >>> How about, scheduling them all at once, but using the same version >>> number across arches when doing it (i.e. the larges

Re: binNMUs: please exercise some care

2015-10-23 Thread Emilio Pozuelo Monfort
On 23/10/15 13:02, Thorsten Glaser wrote: > On Fri, 23 Oct 2015, Adam D. Barratt wrote: > >> wanna-build does, yes, but at least the Release Team tend to use the "wb" >> wrapper tool which automatically works out the next free number on each >> architecture. > > Ah, cool – so we have only to patc

Re: binNMUs: please exercise some care

2015-10-23 Thread Emilio Pozuelo Monfort
On 23/10/15 13:21, Emilio Pozuelo Monfort wrote: > On 23/10/15 13:02, Thorsten Glaser wrote: >> On Fri, 23 Oct 2015, Adam D. Barratt wrote: >> >>> wanna-build does, yes, but at least the Release Team tend to use the "wb" >>> wrapper tool which automatic