On 2016-06-11, Holger Levsen wrote:
> On Fri, Jun 10, 2016 at 09:18:40AM -0700, Vagrant Cascadian wrote:
>> > thanks for the patch, before I apply something similar I have a
>> > question: does that mean ff2b is gone *forever*?
>>
>> Not 100% sure just yet; it still turns on, but doesn't boot. The
On Fri, Jun 10, 2016 at 09:18:40AM -0700, Vagrant Cascadian wrote:
> > thanks for the patch, before I apply something similar I have a
> > question: does that mean ff2b is gone *forever*?
>
> Not 100% sure just yet; it still turns on, but doesn't boot. The
> recovery process doesn't work, and *som
On 2016-06-10, Holger Levsen wrote:
> On Thu, Jun 09, 2016 at 01:31:39PM -0700, Vagrant Cascadian wrote:
>> Reassign jobs for ff2b-armhf-rb to other nodes, as it is down for the
>> forseeable future.
>
> thanks for the patch, before I apply something similar I have a
> question: does that mean ff2b
On Thu, Jun 09, 2016 at 01:31:39PM -0700, Vagrant Cascadian wrote:
> Reassign jobs for ff2b-armhf-rb to other nodes, as it is down for the
> forseeable future.
thanks for the patch, before I apply something similar I have a
question: does that mean ff2b is gone *forever*?
if so, README and THANKS
Reassign jobs for ff2b-armhf-rb to other nodes, as it is down for the
forseeable future.
Available in the ff2b-reassign branch:
https://anonscm.debian.org/git/users/vagrant/jenkins.debian.net.git
---
job-cfg/reproducible.yaml | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
dif
