Re: Bits from the release team (freeze time line)

2014-02-09 Thread Matthias Klose
Am 27.12.2013 03:16, schrieb Steve McIntyre: On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: On a related note, DSA have concerns with the current arm* and mips* hardware. While there have been promises of new hardware to replace some of the current buggy machines, the offers

Re: Bits from the release team (freeze time line)

2014-01-11 Thread Niels Thykier
On 2013-12-28 15:02, Antonio Terceiro wrote: On Fri, Dec 27, 2013 at 09:47:41PM +0100, Niels Thykier wrote: On 2013-12-27 21:08, Antonio Terceiro wrote: Hi, On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: We are happy to use results from other automated tests (like

Re: Bits from the release team (freeze time line)

2013-12-30 Thread Tim Fletcher
On 27/12/13 11:53, Peter Palfrader wrote: On Fri, 27 Dec 2013, Steve McIntyre wrote: On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: On a related note, DSA have concerns with the current arm* and mips* hardware. While there have been promises of new hardware to replace some

Re: Bits from the release team (freeze time line)

2013-12-29 Thread Jeremiah C. Foster
On Sat, Dec 28, 2013 at 07:51:21PM +, Luca Filipozzi wrote: On Sat, Dec 28, 2013 at 07:14:25PM +0100, Aurelien Jarno wrote: On Sat, Dec 28, 2013 at 03:28:04PM +0100, Philipp Kern wrote: On Fri, Dec 27, 2013 at 02:19:07PM +0100, Andreas Barth wrote: I think that our core point is that

Re: Bits from the release team (freeze time line)

2013-12-29 Thread Aurelien Jarno
Hi, First of all thanks for your answer, it's really appreciated to have more details. On Sat, Dec 28, 2013 at 07:51:21PM +, Luca Filipozzi wrote: On Sat, Dec 28, 2013 at 07:14:25PM +0100, Aurelien Jarno wrote: On Sat, Dec 28, 2013 at 03:28:04PM +0100, Philipp Kern wrote: On Fri, Dec

Re: Bits from the release team (freeze time line)

2013-12-28 Thread Antonio Terceiro
On Fri, Dec 27, 2013 at 09:47:41PM +0100, Niels Thykier wrote: On 2013-12-27 21:08, Antonio Terceiro wrote: Hi, On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: We are happy to use results from other automated tests (like autopkgtest [DEP8]) in the same way, as soon as

Re: Bits from the release team (freeze time line)

2013-12-28 Thread Philipp Kern
On Fri, Dec 27, 2013 at 02:19:07PM +0100, Andreas Barth wrote: However, using words like known-buggy mips* machines is just FUD against the mips*-ports, and plainly inacceptable, so please stop doing that. (For reference, there is no mipsel machine which has hardware bugs affecting daily

Re: Bits from the release team (freeze time line)

2013-12-28 Thread Aurelien Jarno
On Sat, Dec 28, 2013 at 03:28:04PM +0100, Philipp Kern wrote: On Fri, Dec 27, 2013 at 02:19:07PM +0100, Andreas Barth wrote: However, using words like known-buggy mips* machines is just FUD against the mips*-ports, and plainly inacceptable, so please stop doing that. (For reference, there

Re: Bits from the release team (freeze time line)

2013-12-28 Thread Luca Filipozzi
On Sat, Dec 28, 2013 at 07:14:25PM +0100, Aurelien Jarno wrote: On Sat, Dec 28, 2013 at 03:28:04PM +0100, Philipp Kern wrote: On Fri, Dec 27, 2013 at 02:19:07PM +0100, Andreas Barth wrote: However, using words like known-buggy mips* machines is just FUD against the mips*-ports, and

Re: Bits from the release team (freeze time line)

2013-12-28 Thread Martin Zobel-Helas
Hi, On Sat Dec 28, 2013 at 19:51:21 +, Luca Filipozzi wrote: On Sat, Dec 28, 2013 at 07:14:25PM +0100, Aurelien Jarno wrote: On Sat, Dec 28, 2013 at 03:28:04PM +0100, Philipp Kern wrote: On Fri, Dec 27, 2013 at 02:19:07PM +0100, Andreas Barth wrote: However, using words like

Re: Bits from the release team (freeze time line)

2013-12-27 Thread Peter Palfrader
On Fri, 27 Dec 2013, Steve McIntyre wrote: On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: On a related note, DSA have concerns with the current arm* and mips* hardware. While there have been promises of new hardware to replace some of the current buggy machines, the offers

Re: Bits from the release team (freeze time line)

2013-12-27 Thread Andreas Barth
* Steve McIntyre (st...@einval.com) [131227 03:17]: On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: On a related note, DSA have concerns with the current arm* and mips* hardware. While there have been promises of new hardware to replace some of the current buggy machines, the

Re: Bits from the release team (freeze time line)

2013-12-27 Thread Neil Williams
On Fri, 27 Dec 2013 12:53:32 +0100 Peter Palfrader wea...@debian.org wrote: Arm* is a slightly smaller issue because we have no way to remotely power cycle the machines Linaro may be able to help here. We've developed software to allow remote interaction with a selection of APC PDU units and

Re: Bits from the release team (freeze time line)

2013-12-27 Thread Antonio Terceiro
Hi, On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: We are happy to use results from other automated tests (like autopkgtest [DEP8]) in the same way, as soon as someone runs them on the entire archive and gives us a machine-readable list of the results. [DEP8]

Re: Bits from the release team (freeze time line)

2013-12-27 Thread Niels Thykier
On 2013-12-27 21:08, Antonio Terceiro wrote: Hi, On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: We are happy to use results from other automated tests (like autopkgtest [DEP8]) in the same way, as soon as someone runs them on the entire archive and gives us a

Re: Bits from the release team (freeze time line)

2013-12-26 Thread Adam Conrad
On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: With a recent upload, the default gcc version on s390x changed to gcc 4.8. However, on powerpc, ia64 and sparc, the default gcc version is still gcc 4.6. As this version will not be supported in Jessie, we are now giving an

Re: Bits from the release team (freeze time line)

2013-12-26 Thread Steve McIntyre
On Thu, Dec 26, 2013 at 06:08:03PM +0100, Niels Thykier wrote: On a related note, DSA have concerns with the current arm* and mips* hardware. While there have been promises of new hardware to replace some of the current buggy machines, the offers are currently not leading to concrete results.