+++ Riku Voipio [2013-07-19 06:58 -0000]:
> Looking at package-and-publish-linux-linaro-test configuration, this
> looks still racy. The job runs dpkg outside chroot a few times, which
> could collide with other jobs.
This just temporary code to test the chroot and latest sbuild. As soon
as those packages are installed in the standard image then that code
should be removed and all the (locking) dpkgness should happen inside the chroot
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/
+++ Riku Voipio [2013-07-19 06:58 -0000]: and-publish- linux-linaro- test configuration, this
> Looking at package-
> looks still racy. The job runs dpkg outside chroot a few times, which
> could collide with other jobs.
I presume you mean this bit: repo.linaro. org/ubuntu/ linaro- tools/pool/ main/r/ raring- crosschroot/ ${chrootpackage}
----
wget http://
sudo dpkg -i ${chrootpackage}
dpkg -l raring-crosschroot
wget http:// ppa.launchpad. net/linaro- maintainers/ tools/ubuntu/ pool/main/ s/sbuild/ libsbuild- perl_0. 64.0+repack1- 1wook1_ all.deb ppa.launchpad. net/linaro- maintainers/ tools/ubuntu/ pool/main/ s/sbuild/ sbuild_ 0.64.0+ repack1- 1wook1_ all.deb perl_0. 64.0+repack1- 1wook1_ all.deb sbuild_ 0.64.0+ repack1- 1wook1_ all.deb
wget http://
sudo dpkg -i libsbuild-
dpkg -l sbuild libsbuild-perl
----
This just temporary code to test the chroot and latest sbuild. As soon
as those packages are installed in the standard image then that code
should be removed and all the (locking) dpkgness should happen inside the chroot
Wookey wookware. org/
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://