From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7032253102499561472 X-Received: by 2002:a19:ee01:: with SMTP id g1mr29902687lfb.44.1637913818699; Fri, 26 Nov 2021 00:03:38 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:3e10:: with SMTP id i16ls66231lfv.3.gmail; Fri, 26 Nov 2021 00:03:37 -0800 (PST) X-Google-Smtp-Source: ABdhPJwBfSWT85gO6Kydn/Y+Ejv4meA2DhLZHGzy47jbqMWlNBY30RO0bBSUjIot6c4bE6yTRYqi X-Received: by 2002:ac2:5932:: with SMTP id v18mr28080090lfi.611.1637913817344; Fri, 26 Nov 2021 00:03:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1637913817; cv=none; d=google.com; s=arc-20160816; b=kzbnuqJAxZn2jCsl33w/ML4lNnTwENEU/g5tKRxxpYSgrOrgF0bG0gD2zQVs94Gpij tq/4HYm51fZMP9QfY8EfevFfUiIYGEb9M+CD1tqHT2UeDS0WRwf+RpVjcRk1dpuO3WL1 wJYhiCSfRViYiqq805Xo+G/I7xGdIOVm1V/b9NjQgAwqGat9IG+dTdHb3OROUY5byvFN Ck6bhDZ4FgXlCg7rFBQ4TwkAcWFs8BjxJW1wC+J2lEYVOCqna1cTUCvjIIWXA5b6uSWO BoWuafDbCmWIMlqlgRldJNwrX+t0Qh5vn1s23PXmNBSK17fKVw0BowXbx/q5lJHKs06T 3o7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:to:from; bh=4UPKqZs99WW68jq798RhS1i8Asp4OH4odrIivZ0ZdjI=; b=y7PRRZJMo8ScimP0GdHBPKyhIHiFh3soupdTaXIxBPxQrpgRNWb6HLCxi+WYC1hV+1 Sir4pGqMpghJ4LyMFBwAbkzythZ95naSFNDb0rkAP/or6yGE6sjuDsXThA699J/j1eAS sVZudgD0eh2ub2DzzBtz1zV+LfBGhv1b/zuJuUD2AXhINRCnJSOE1GjdVQfUPjX51vwE HRwo+bGmqSFmzutJUxBKfTBJYJ8hj2+WqdUpLpc647VUPrgIS3izDEOfV7DNcYff7+X/ 1gPajUYyy3TFmVFKCD/k/vEnbIRtiQb1t0jjvFozBMWypJlPkFL1hrgANdefP9kiApjU /UVw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id i16si534168lfv.2.2021.11.26.00.03.37 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 26 Nov 2021 00:03:37 -0800 (PST) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from hp.localnet (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 1AQ83YGI022461 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 26 Nov 2021 09:03:36 +0100 From: Uladzimir Bely To: isar-users@googlegroups.com, Jan Kiszka Subject: Re: [PATCH v2 00/24] Sbuild/Schroot migration Date: Fri, 26 Nov 2021 11:03:07 +0300 Message-ID: <1976554.YKUYFuaPT4@hp> In-Reply-To: References: <20211119121333.13805-1-ubely@ilbers.de> <2071114.yiUUSuA9gR@home> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: QqRMU0wBmkEG In mail from Friday, 26 Nov 2021. 09:43:58 +03 user Jan Kiszka wrote: > On 23.11.21 14:05, Uladzimir Bely wrote: > >> Current limitations: > >> - there is an unsolved problem with building foreigh architectures > >> using kas-docker. > > What exactly is the problem here? > Actually, the problem was related to UsrMerge. Our Jenkins root is also based on buster, but /bin, /lib are symlinks to /usr/bin, /usr/lib and so on. While in buster-slim used in kas-docker /bin, /lib are separate directories. And schroot version used in buster couldn't work in this case (qemu-*-static packages couldn't find some libraries). But when I schroot version from bullseye seems to support both kinds of rootfs. So, no changes were needed in sbuild patches, I just preinstalled newer schroot (from bullseye) in kas-docker image (in addition to a newer sbuild), and it works. > >> ... > > I've commented on some aspects of you kas patch. It generally looks > feasible, just some smaller details should be improved. > Yes, I saw your comments on github. I'm not yet experienced in kas development, so my implementation is not ideal. > > ... > > So, gitlab will use external ("/m/ws-10/schroot-10a/union") directory on > > host. Also, there should be empty "overlay" and "underlay" directories > > created in it. > > That's also not unrealistic, given that we already need to provide > special runners for the purpose of granting privileges and allowing > binfmt_misc. One target would be > https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci, the backend > for many of our gitlab CI runners that are Isar-compatible. > > Jan Ok, I'll take a look at it. Currently I'm trying to find/fix possible issues in downstreams. I took meta- iot2050 for experiments. For now it seems to use quite old docker image and isar codebase. At first, I made sure it can build with no errors current Isar 'next' branch with using my modified docker image. But for now it is not yet able to build even partial (preparation patches only) sbuild patchset and I'm trying to understand and fix the issues. -- Uladzimir Bely Promwad Ltd. External service provider of ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn, Germany +49 (89) 122 67 24-0 Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov