From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6520199916203016192 X-Received: by 10.46.56.10 with SMTP id f10mr681540lja.22.1518430097607; Mon, 12 Feb 2018 02:08:17 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.46.12 with SMTP id u12ls1199028lju.4.gmail; Mon, 12 Feb 2018 02:08:16 -0800 (PST) X-Google-Smtp-Source: AH8x22465YjiAiRDdxnX4HIV9cJzYS8CwKvLQFJyvgeiGkFiwFUBxSIfZOp6qpd3+RW3ZT467i5F X-Received: by 10.46.2.69 with SMTP id 66mr672822ljc.23.1518430096972; Mon, 12 Feb 2018 02:08:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518430096; cv=none; d=google.com; s=arc-20160816; b=nTHKpOlDwqtqZERgODqIwe44xW8YPav3lUe18n9cL15kalsWYpnZMxPR+8KSLVkY7L 6Afn6fT4e7KwYuln9NXMOOwOaYUNARm/LH0MqCfZDyvBH33gkk0HWLnqr21gwrPlVbwF rOkwZ5RClXhvZKkubQPNcTYvawKLoa8yPDY5K8Fu4ZzB8728aQAAImm1YYnTwbn1wlxk DvkgKS1BZeI2l+zTl4Q8pFIRuMGPrnJVTgChkQrkKbunLvsfsUSfvpt4ZxLT1zSJQAB5 0OlFfBFp7LfKGjc5CfmeIodYO5eOIUkYelpRPMHGMK0cQOreQ0R8qvgvMyr+o8EYmvzf O1Rg== 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=qoUbYf/lgQvOjO2TH83uCmeDyOvjyaSNB6iStxftP/w=; b=mQdsiDF3mGuWSDFOFDY6KWhC73fMXByVFWodNWvF/wKx03zac0S7qAhiY0NeBubvIo f1EGRR+EWMKsKugOR5vxnEZWMxB/QTHD+82urLRIfjLRaWk7fVDON7JKGoBl/mjD7dUo 53x3+Yf6mLV8pA9vfWlmuhdzI7hVjJSl/YPxLArHgYfSj8lsafqcpSLC3538u8DiPG9h XdhRYnDnx7hA9RbBTPmNh2/+pJU3PFGbUp7GyZpsrWVHnUCvSVtfQIPkRjuwMDrALauL NiXNXdTw8dAbYWa14SvUCnbQ5sAiWC4trNI2SuabNdkMzYyQAc2G/9LxTuE6VvV8E8lw hgKQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id o26si421891ljc.5.2018.02.12.02.08.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 02:08:16 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w1CA8CFf000387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 12 Feb 2018 11:08:14 +0100 Subject: Re: [PATCH v4 2/8] Prioritize isar-apt repo over all others To: Jan Kiszka , isar-users References: <136df397-5fce-9f50-fd74-f35f038fbda2@siemens.com> From: Alexander Smirnov Message-ID: Date: Mon, 12 Feb 2018 13:08:07 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <136df397-5fce-9f50-fd74-f35f038fbda2@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: 1fPWWZdP4qm9 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. Moreover 'man 1 multistrap' states the same: ... The combination of default release, explicit suite and apt preferences can quickly become complex and bugs can be very hard to identify. ... So, from two options: - Rename custom kernel package - Prioritize apt the first one looks more easy and robust. > >> >> For me this approach looks like a good way to have unexpected troubles >> like the following: >> >> 1. You pick current glibc from upstream distro XYZ, let's say v1.0. >> 2. Patch it and put glibc-v1.0-isar to isar-apt. >> 3. Wait for some time until glibc is updated in upstream, let's say to >> v1.1. >> 4. Due to glibc-v1.0-isar is set to be preferred, it's going to be >> installed. But glibc is the core library in distro, and lots of packages >> in XYZ now require glibc-v1.1. So even if you will be able to generate >> image, you can't guarantee it works correctly... > > Well, sure, no one takes away the task from you of properly maintaining > the recipes when upstream updates happen (and you pull them into your > reproducible build). If this is only about specific package[s], I'd suggest to propose this feature as an option to *overwrite* the specific package and do not do this by default for the whole isar-apt. Alex