From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6641861376070385664 X-Received: by 2002:a05:6000:114e:: with SMTP id d14mr121404wrx.5.1547540350660; Tue, 15 Jan 2019 00:19:10 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a7b:ce03:: with SMTP id m3ls286425wmc.10.canary-gmail; Tue, 15 Jan 2019 00:19:10 -0800 (PST) X-Google-Smtp-Source: ALg8bN5cFyAd/8sIVxcOkTLv8ReF3R9DLznn2LGZ4NdCUz5zpK5YoK3jT+j75kI1ugHhqLptC3kq X-Received: by 2002:a1c:860f:: with SMTP id i15mr236726wmd.24.1547540350196; Tue, 15 Jan 2019 00:19:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547540350; cv=none; d=google.com; s=arc-20160816; b=qU0nchtb7yl5jP7dnWuLy4WiwSCSO4elYvgr9Lu8O6136DyX5aUIidvvu+9E2wEZsc 68A2MmrvRNCMdZXVhONhTbSy0Js20YH0vYaiVxgGHa3MylyBMGHjx06QkvbRRqyI0JDh vScUCZr/v1AO8rtOOI9s55zEIJKKiPO08hu//jvaqczTI9SnRKKExSmg3eWSxArBY8SI F8SaWN/34sXmZU52yAltp2XJxkniV0nPJm9i9jQBjXClQjpTVOfZckXh6IiumfnL1t9W OMeGhJ2ANqQx8rQmXwWAYAQ+eJ4PEoMpo01BKj8IBoquwS6vTyOX2zDSYLDZaennB4na F3gA== 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:references:to:from:subject; bh=4dAD7tcvxTtQu7TFW+9JV/xyUjimp4UhymT1FYXwd20=; b=wPZb0H/ze7HoTgLgI3LkrNcL2otoIGARl0hkUpi8EGWo50T2275Rz6tsFOOEr0AaVk Ao8JQrXrYtETY9BtbaMf1b2pSQAZvARAGY8dnGgGWjm9NajrKk/DEyICjFzklHVlPNq7 VWzmGX205JS41vwDr8gKYc1NJPvvt/UlIc5mciqQ/PQgNd1GBsUj2lSaTnnZAeziNCZc 3D9HZnQD/vDHXOtj7Sqt0p1forG+0wUP9nfVoSRowYZ8GqkJmMLd563Y9yib6GZos9as +wHyPQO71EIMMgU6hFXLg05HeUeQcYyOEd/V0iL+lyCh68VSeOELjnCNoru9UtlEJt4o FwMg== 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 x13si3131169wrn.3.2019.01.15.00.19.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Jan 2019 00:19:10 -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 mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x0F8J9Rs001995 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 15 Jan 2019 09:19:09 +0100 Received: from [139.22.114.70] ([139.22.114.70]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x0F8J9fJ009812; Tue, 15 Jan 2019 09:19:09 +0100 Subject: Re: [PATCH 1/7] dpkg-raw: Respect file permissions defined by recipe From: Jan Kiszka To: isar-users , Baurzhan Ismagulov References: <20190107142049.0c5426a3@md1za8fc.ad001.siemens.net> <20190109153706.GB12226@yssyq.m.ilbers.de> <6c2a13e5-513f-243f-3d82-317a8a9df228@siemens.com> Message-ID: <221acaf9-1542-52eb-96fd-9616d25a79dd@siemens.com> Date: Tue, 15 Jan 2019 09:19:08 +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: <6c2a13e5-513f-243f-3d82-317a8a9df228@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: F72lecJ0q50E On 10.01.19 02:19, [ext] Jan Kiszka wrote: > On 09.01.19 23:37, Baurzhan Ismagulov wrote: >> On Mon, Jan 07, 2019 at 02:28:47PM +0100, Jan Kiszka wrote: >>>>> dh_fixperms overwrites the permissions do_install defined carefully. >>>>> Skip this step to avoid that. >> ... >>>>> --- a/meta/classes/dpkg-raw.bbclass >>>>> +++ b/meta/classes/dpkg-raw.bbclass >>>>> @@ -56,9 +56,11 @@ EOF >>>>> deb_create_rules() { >>>>> cat << EOF > ${S}/debian/rules >>>>> #!/usr/bin/make -f >>>>> + >>>>> +override_dh_fixperms: >>>>> + >>>>> %: >>>>> dh \$@ >>>>> - >>>> >>>> I think it is not a good idea to do that in general. While you might >>>> have found an example where dh_fixperms caused problems, there are >>>> probably many where it helps. Say people use "cp" to fill ${D} or >>>> "echo" to fill ${D}/bin/ >>> >>> I'm open for better suggestions. >> >> dh_fixperms -X from a variable / file? >> >> override_dh_fixperms in a conditional makefile include, if exists? > > Something like this? > > diff --git a/meta/classes/dpkg-raw.bbclass b/meta/classes/dpkg-raw.bbclass > index 10fb1b9..fa584ee 100644 > --- a/meta/classes/dpkg-raw.bbclass > +++ b/meta/classes/dpkg-raw.bbclass > @@ -53,11 +53,14 @@ Description: ${DESCRIPTION} > EOF > } > > +FIXPERM_EXCLUSIONS = "${@' '.join(['-X ' + x for x in d.getVar('PRESERVE_PERMS', False).split()])}" > + > deb_create_rules() { > cat << EOF > ${S}/debian/rules > #!/usr/bin/make -f > > override_dh_fixperms: > + dh_fixperms ${EXCLUSIONS} > > %: > dh \$@ > > > Then the user would have to specify the files to be excluded with full > paths: > > PRESERVE_PERMS = "/root/.ssh" > PRESERVE_PERMS += "/etc/network/interfaces.d/wifi" > >> >> That said, I think the right way would be to create proper source packages >> downstream. > > Cannot follow that idea yet: What would be the interface? > >> >> FWIW, meta-eid has a PoC for dh_making a package from bitbake, but one could >> start with manually debianized packages first. >> >> With kind regards, >> Baurzhan. >> > > Jan > Ping. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux