public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
	Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH] meta/dpkg-raw: fix raw package file ownership
Date: Wed, 7 Nov 2018 17:27:24 +0100	[thread overview]
Message-ID: <93563efe-776b-af38-9576-3ea57ab729c7@siemens.com> (raw)
In-Reply-To: <20181107172509.59d1d663@md1za8fc.ad001.siemens.net>

On 07.11.18 17:25, Henning Schild wrote:
> Am Wed, 7 Nov 2018 17:19:14 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> 
>> On 07.11.18 17:15, [ext] Henning Schild wrote:
>>> Make sure the whole content of the package defaults to ownership
>>> "root:root", deviations will have to be done in postinst.
>>> Before the file ownership was coming from our build environment and
>>> typically was "1000:1000".
>>>
>>> Reported-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
>>> Signed-off-by: Henning Schild <henning.schild@siemens.com>
>>> ---
>>>    meta/classes/dpkg-raw.bbclass | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/meta/classes/dpkg-raw.bbclass
>>> b/meta/classes/dpkg-raw.bbclass index c848f3d..d662422 100644
>>> --- a/meta/classes/dpkg-raw.bbclass
>>> +++ b/meta/classes/dpkg-raw.bbclass
>>> @@ -54,6 +54,6 @@ do_prepare_build() {
>>>    }
>>>    
>>>    dpkg_runbuild() {
>>> -	sudo chown -R root:root ${D}/DEBIAN/
>>> +	sudo chown -R root:root ${D}
>>>    	sudo chroot ${BUILDCHROOT_DIR} dpkg-deb --build
>>> ${PP}/image ${PP} }
>>>    
>>
>> That will overwrite potentially different settings of derived recipes
>> - not optimal.
> 
> I think the only sane way of chowning inside a package is in postinst,
> because you never know the id before-hand. Maybe there are a few exotic
> hard-coded users/groups ...
> So my assumption is that any package doing chowning does that in
> postinst and otherwise all files belong to root. This commit implement
> the assumption. It might be wrong but in that case i want a
> counter-example from you ;).

Fair enough. I only have use case where I can now remove the "chown root:root". 
Should still be documented, specifically in RECIPE-API-CHANGELOG.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2018-11-07 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 16:15 Henning Schild
2018-11-07 16:19 ` Jan Kiszka
2018-11-07 16:25   ` Henning Schild
2018-11-07 16:27     ` Jan Kiszka [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93563efe-776b-af38-9576-3ea57ab729c7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox