[Freedombox-discuss] FreedomBox Unstable Image 2013.0405 Available

[Nick Hardiman]

Had a quick check. The bittorrent daemon thinks it's missing one tiny chunk, but otherwise it's all there. 

nick at admin:~$ transmission-remote localhost:8080  --auth user:pass -l
ID     Done       Have  ETA           Up    Down  Ratio  Status       Name
   1   100%  298.0 MiB  Done         0.0     0.0   15.9  Idle         pmagic_2013_01_29.iso
   6   100%    1.3 GiB  Done         0.0     0.0   5.96  Idle         freedombox-unstable_2013.0219
   7   100%  325.7 MiB  Done         0.0     0.0   3.00  Idle         freedombox-unstable_2013.0130
  11   100%    2.5 GiB  Done         0.0     0.0   12.3  Idle         freedombox-unstable_2013.0318
  12    99%  957.8 MiB  Unknown      0.0     0.0   2.37  Idle         freedombox-unstable_2013.0405
Sum:           5.4 GiB               0.0     0.0
nick at admin:~$ 

I would run 
make weekly-image 
and see what happens, but I have just moved house and most of my IT things are in cardboard boxes. :)

Nick Hardiman
nick at internetmachines.co.uk
@intmachines



On 11 Apr 2013, at 13:15, "Nick M. Daly" <nick.m.daly at gmail.com> wrote:

> Nick Hardiman <nick at internetmachines.co.uk> writes:
> 
>> Looks a bit broken. There are three suspiciously small files. 
> 
> Let me know when you've mirrored them and I'll try to boot it off my
> DP.  As I mentioned on IRC, never code while tired: I munged the
> repository into a weird state (pulling vmdebootstrap into the root
> instead of vendor directory), branched my changes off into a separate
> repository, and deleted the separate repository before all the changes
> landed in the original (published) repository again.  So far, I've seen
> one changeset that didn't make it back (naming the VirtualBox image
> correctly), but there are probably others.
> 
> I've also fixed the weekly-directory building bugs in the latest
> commit.  I'd appreciate if anyone could let me know their experiences
> with building this thing.
> 
> Nick