so, did we manage to successfully validate that it works? I only saw that build #5 didn't work because there was no BUILD-INFO.txt and build #6 shipped an open license.
Can we get builds with and without the old build name scheme kicked off and validated with open and eula build-info style?
On Wed, Jul 25, 2012 at 11:34 AM, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
W dniu 25.07.2012 11:28, Georgy Redkozubov pisze:
Which is wrong as both builds copied snowball BUILD-INFO.txt
I don't see BUILD-INFO.txt for #5 on snapshots.l.o
That is correct, build 5 was made before pfalcon migrated the configuration template for all builds (whatever that is) to copy build info.
gesha@mombin:~$ ls
/srv/snapshots.linaro.org/www/android/~zkrynicki/origen-ics-gcc47-samsunglt-stable-fakeblob-build-info/5/target/product/pandaboard/ boot.tar.bz2 EULA.txt MD5SUMS system.tar.bz2 u-boot.img userdata.tar.bz2 gesha@mombin:~$ ls
/srv/snapshots.linaro.org/www/android/~zkrynicki/origen-ics-gcc47-samsunglt-stable-fakeblob-build-info/6/target/product/pandaboard/ boot.tar.bz2 BUILD-INFO.txt EULA.txt MD5SUMS system.tar.bz2 u-boot.img userdata.tar.bz2
Build 6 was also correct as I've explained on IRC:
<zyga> gesha, so I've send an email yesterday gesha, but it's no longer accurate, I've made a mistake in my tests gesha, it seems everything _is_ fine gesha, current build should confirm that gesha, I've specified the overlay twice gesha, with the second overlay being what we actually saw
Thanks
ZK
-- Zygmunt Krynicki Linaro Validation Team s/Validation/Android/