From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6520199916203016192 X-Received: by 10.46.2.69 with SMTP id 66mr673245ljc.23.1518430296719; Mon, 12 Feb 2018 02:11:36 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.18.79 with SMTP id t76ls1194900lje.15.gmail; Mon, 12 Feb 2018 02:11:36 -0800 (PST) X-Google-Smtp-Source: AH8x2271DJFc9bqUJTfzBX3S7486puJ9mklAHgYRFqXbEYIqDHrPViF1ilAxQKWC5rQxoPvEZg1E X-Received: by 10.46.114.16 with SMTP id n16mr657249ljc.2.1518430296013; Mon, 12 Feb 2018 02:11:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518430295; cv=none; d=google.com; s=arc-20160816; b=Q7K1NvrLOdI+nbyLdX9Pq7WedakUKUrvvC+0kKT6XztMHd/KtNSzorg9YtqRq9aR6s 5TCZ1AfdVPtyoOS9lwU8KA4sQmoF4EVA38JLU80y+mlGC3aGwB08znaGIteCMYZ+872D Nv+UeXTobnsqYTX652jPRYb29hawGfIWuRavTq+0XPlJwYZ+95hl7RuxxfCvBOJhd3J0 UReOJoW93x3a1a+ORNnP4qd7Lk2RlJbIgocCvytSwa3G3MKuI7eq87R6JJHvMzVCPWiz oUJXvLPzx5TDHaiLCOGVV2Pfk5/3vEq4BhkLV0a8LLOp/NXUT+dMoVgrVw4sfPMi1peL CI2w== 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 :arc-authentication-results; bh=UrC3/5ujNbHFD8EXI3JjEQtkl1IEICDjoOVKs6FV+Bo=; b=e9ZQO1Xr5g3yYQetYVXGSObeglUPEKwG/djDQzwlOM6FAzM///tgZMdJMQ6Ehxrlxo b/DyhkKRR3SdN2afqlBX32ffmb5LlsapgVk0+1Xz7B44xusgzUZDY88iXBGUX9/a8+LK uzQ4dA2tKE04VwfkETJZY0kjLwlmOeEPKTIX7ccYggb1lD5e6cNYcjHanCuk//ijBzpb vco/M0ogSMULVCxmfbGDK4FQhDTLU6/gR1TccRd5S0CIT/2z2+8PdfWO4PM/aX7Dc4u+ Iit73ndMa+LVKJt4ZNb1MUMJpKBz7HpJqBgnazpWw3rWEGtjjbI/hixFxcoC2zD0BNUR nMmQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id 25si479642ljt.1.2018.02.12.02.11.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 02:11:35 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w1CABZ8Q015064 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 12 Feb 2018 11:11:35 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w1CABZmq014698; Mon, 12 Feb 2018 11:11:35 +0100 Subject: Re: [PATCH v4 2/8] Prioritize isar-apt repo over all others To: Alexander Smirnov , isar-users References: <136df397-5fce-9f50-fd74-f35f038fbda2@siemens.com> From: Jan Kiszka Message-ID: Date: Mon, 12 Feb 2018 11:11:33 +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 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: PiNAWZBE6xn0 On 2018-02-12 11:08, Alexander Smirnov wrote: > On 02/12/2018 12:41 PM, Jan Kiszka wrote: >> On 2018-02-12 10:33, Alexander Smirnov wrote: >>> On 02/11/2018 06:25 PM, Jan Kiszka wrote: >>>> From: Jan Kiszka >>>> >>>> This ensures that we can override packages from upstream Debian or >>>> other >>>> external sources with our self-built versions. We achieve this for now >>>> by asking multistrap to drop a preferences file for the buildchroot so >>>> that dependency installations use the right priority. For the image >>>> build, this does not work because all packages are pull during the >>>> bootstrap. Therefore, we set aptdefaultrelease to isar to ensure that >>>> our repo gets the higher priority. >>>> >>> >>> I'm not sure that I completely understand this. What is the use-case for >>> this? If you build your own copy of upstream package, this >>> prioritization could be resolved by specifying suffix to version. >> >> Simple example: custom kernel build of linux-cip >> >> This generates a package called linux-image-amd64 (for amd64 as target), >> and that may have a version < debian's kernel. Now, if we do not >> prioritize isar-apt over upstream, the upstream kernel is taken, even >> when you switched PREFERRED_PROVIDER (in fact, the build will break when >> that virtual package linux-cip is selected but can't be installed due to >> the version preference "newest"). > > Ok, but why you can't name you kernel 'linux-cip-image-amd64'? Having > the same name as with original Debian one could be confusing. > That is mandatory, in order to write packages that depend on THE kernel, instead of "my-custom-kernel-in-version-4.4.112". Jan