Hi Vagrant,

do you need to be cc:ed?

On Montag, 27. Juli 2015, Vagrant Cascadian wrote:
> Thanks for all your work on reproducible builds!

:-) Thanks for helping on the armhf hardware side! :-)

> So I set about trying to patch u-boot and test reproducibility myself,
> only to discover that the reproducible toolchain didn't include arm
> packages...

yes, we either need to make sure to manually build there in future too, or 
setup some autobuilders...
> So I could build all this infrastructure locally, but figured better to
> offer something to the reproducible builds effort at large. So I'd like
> to make a few armhf build machines available to the project...

very cool!

> I've currently got two up and running, but it sounds like there's more
> work to do on the backend to integrate with jenkins and other
> infrastructure...

yes, we need to make some changes to our infrastructure as well:

- add scheduling for armhf
- have jenkins jobs to prepare pbuilder chroots for armhf on these machines
- add support for building on remote machines
- integrate the armhf build results into the web ui

> The current specs:
> bpi0-armhf-rb.debian.net:
> Banana PI, dual-core, 1GB ram, ~20GB mSATA.
> ssh port: 2222
> ssh fingerprints:
> 2048 8f:0a:d0:77:a8:59:c0:bb:d0:76:de:14:13:5b:a6:56 (RSA)
> 256 af:b4:13:04:21:30:46:b3:e8:79:ff:7d:99:20:86:f0 (ECDSA)
> hb0-armhf-rb.debian.net:
> HummingBoard i2ex, dual-core, 1GB ram, ~20GB mSATA.
> ssh port: 2224
> ssh fingerprints:
> - 2048 04:af:b4:e8:f0:13:13:66:25:7b:e3:d6:ee:b3:0d:0a (RSA)
> - 256 2f:1b:3a:fb:55:cf:27:3f:f6:de:e4:3d:e1:4c:59:c8 (ECDSA)

nice, that should be plenty.

how is the network connectivity? I assume we want to use a proxy, though I 
have no idea whether one for both machines or one on each machine (though with 
20gb diskspace there is not really space for a proxy...)

> I hope to get a wandboard quad-core with 2gb of ram and a 60GB SSD set
> up in a few days, and possibly a cubox-i4pro with similar specs too.
> Let me know if you need access to these machines to configure them.

yes, we need access. Preferedly root/sudo, else user ssh access (account name 
holger for me please) and we need a jenkins users with a quite liberal 

I'll send you an ssh pub key in a seperate mail.

Thanks again for your support!


Attachment: signature.asc
Description: This is a digitally signed message part.

Reproducible-builds mailing list

Reply via email to