Re: [PATCH] buildchroot: Perform upgrade after build dependency installation

[Jan Kiszka <jan.kiszka@siemens.com>]

On 30.01.19 12:49, Maxim Yu. Osipov wrote:
> On 1/22/19 5:22 PM, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> When we partially rebuild after updating the version of a build
>> dependency of another package, we do not properly upgrade that
>> dependency in buildchroot. The reason is that "apt-get install"
>> performs upgrades only for the explicitly listed packages. But we
>> install build dependencies indirectly, we a meta package's dependency.
>>
>> Resolve that be running an explicit "apt-get upgrade" after the
>> build dependency installation. This will ensure pulling the latest
>> versions for isar-apt.
> 
> When ran ci_build.sh -q -f build failed on known problem:
> 
> | The lock file 
> '/workspace/build/isar_mosipov_develop/17/build/downloads/base-apt/db/debian/lockfile' 
> already exists. There might be another instance with the
> | same database dir running. To avoid locking overhead, only one process
> | can access the database at the same time. Do not delete the lock file unless
> | you are sure no other version is still running!
> | There have been errors!
> 
> See log:
> http://isar-build.org:8080/job/isar_mosipov_develop/17/console
> 
> Investigating the problem.

That is what I reported to the list already [1]. Unrelated to this commit, but 
if it helps to reproduce the issue reliably, that would be helpful.

Jan

[1] https://groups.google.com/forum/#!msg/isar-users/ElRP1h_9m9I/rt6yibJuEQAJ

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux