build failure caused by apt-get/dpkg calls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro CI |
Confirmed
|
Undecided
|
Riku Voipio |
Bug Description
Often, we get build failures caused by apt-get/dpkg calls:
+ sudo apt-get build-dep --assume-yes qemu
Reading package lists...
Building dependency tree...
Reading state information...
E: You must put some 'source' URIs in your sources.list
+ dpkg -i live-build_
dpkg: error: dpkg status database is locked by another process
while a work around to check if we can call apt-get/dpkg safely in the job itself can be done, it will be nice to fix it properly (without user intervention).
Danilo suggested that the images have auto-updates on. It could be also caused by the init script which install commonly used packages with apt-get. Could you investigate on the real cause and propose a fix?
Otherwise, the hack to work around the known issue should be documented in the wiki.
Changed in linaro-ci: | |
status: | New → Confirmed |
Changed in linaro-ci: | |
milestone: | none → 2013.12 |
assignee: | nobody → Riku Voipio (riku-voipio) |
Changed in linaro-ci: | |
milestone: | 2013.12 → 2014.01 |
Changed in linaro-ci: | |
milestone: | 2014.01 → 2014.03 |
Changed in linaro-ci: | |
milestone: | 2014.03 → 2014.04 |
work around the issue by moving apt-get/dpkg call into the instance init script to avoid concurrent package installation in the jobs.
I'm looking into using schroot (or aptdaemon) with jenkins for a long term fix.