From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6649357282775662592 X-Received: by 2002:a17:906:5e55:: with SMTP id b21mr1317253eju.14.1548854278420; Wed, 30 Jan 2019 05:17:58 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:1a12:: with SMTP id i18ls472761ejf.7.gmail; Wed, 30 Jan 2019 05:17:57 -0800 (PST) X-Google-Smtp-Source: AHgI3IYyV3bbd5keMBOC0Xhr5+kRiDU0CQNcYvAykYoxNQw2svuPLIa30ShILOOS7saX+AZ8gE4Y X-Received: by 2002:a17:906:a483:: with SMTP id m3mr22113ejz.9.1548854277886; Wed, 30 Jan 2019 05:17:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548854277; cv=none; d=google.com; s=arc-20160816; b=YyBFLSovslmu8fjz6sgUuz0iuavrb/KKkPehQltRVUS7W6n/q3/KO7KZxOyghRNc5i c0G85c2t3N3fljIlwkaUOCDHJhQH+eI0FdGCU6WHgzapTacgd8l8T7CSURW9x/1QV6Ub n31jvzBhOjeGs4IUCrt7pxaHd1wgPQnZsYfcmP2QRT5o5yZVInNGzAVzfz8Xdd9GSqjE 9TN/BAjKHqvuKMdxMDOqJFAvspcCWk6+8CuaZ6DC+bQVDh5zxUv+Vhz7s3as2g4W+RJt cH5HY6kkZLBl2l+Bi2SKVRTIVhQ+fG89ZpAb7xLOCozwIDd+frl0IZGq7Ogb078JAjrE K+nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=MkwWOsAwZTCN2a4g3RXJQv1HPIesqgJOfoRtilDAzds=; b=d4W8Bp/wjU2XYoKtDUlqT/rgCBn5rQVlOvMzZPtcKZu1GWvmnH/s30rHd1FebWUMkt UIDyMokxmhWexcaJpAniBd9CIUIgcjXxyCsdMcZCBa/EHKp2OYLUbUectXDVMv3QZqXP qmr/OxLkWd/aTuBw5Nc5mZ90/qhMPaoOFmhZXpMvpZpL0LYwIDPBWVr3ee7Pzz9OU/49 2crhnexhWM3SAjdHu2TzmJ8dr8ZRIh9d5nua9eCf5knSKZGmhA2A7p/3CRvnvBdvEd3k Mly9UE2ZUmIQqof4RWYBKafchfkq8Q+1fehFOG2VpLR304WwR7fpZyMTdG8Senp/zgZy HBUg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id k25si98988edd.1.2019.01.30.05.17.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Jan 2019 05:17:57 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x0UDHv30012945 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 30 Jan 2019 14:17:57 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x0UDHuG6021659; Wed, 30 Jan 2019 14:17:57 +0100 Subject: Re: [PATCH] buildchroot: Perform upgrade after build dependency installation To: "Maxim Yu. Osipov" , isar-users References: From: Jan Kiszka Message-ID: Date: Wed, 30 Jan 2019 14:17:56 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: F3lmzZwYIe8I On 30.01.19 12:49, Maxim Yu. Osipov wrote: > On 1/22/19 5:22 PM, Jan Kiszka wrote: >> From: Jan Kiszka >> >> 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