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

Bug#733266: pu: package whois/5.1.0

2013-12-27 Thread Marco d'Itri
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu whois in stable should be updated due to the many changes in the database. I think that the smartest choice would be to reupload the latest release, once it will have transitioned to testing.