From: Jan Kiszka <jan.kiszka@siemens.com>
To: Harald Seiler <hws@denx.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] dpkg-raw: Fix rebuilding recipes
Date: Tue, 9 Oct 2018 14:17:03 +0200 [thread overview]
Message-ID: <70898627-9e55-4d83-b25c-1f41cf07da51@siemens.com> (raw)
In-Reply-To: <158f4ad6a1cda4cca01e820a4279c11807b281a5.camel@denx.de>
On 09.10.18 12:28, Harald Seiler wrote:
> On Tue, 2018-10-09 at 12:05 +0200, Jan Kiszka wrote:
>> On 09.10.18 11:06, Harald Seiler wrote:
>>> Rebuilding dpkg-raw packages fails because the
>>> DEBIAN directories' ownership is transferred to
>>> root in dpkg_runbuild. This commit ensures the
>>> ownership is reset before attempting to write
>>> metadata.
>>>
>>> Signed-off-by: Harald Seiler <hws@denx.de>
>>> ---
>>> meta/classes/dpkg-raw.bbclass | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/meta/classes/dpkg-raw.bbclass b/meta/classes/dpkg-raw.bbclass
>>> index c848f3d..806a2d4 100644
>>> --- a/meta/classes/dpkg-raw.bbclass
>>> +++ b/meta/classes/dpkg-raw.bbclass
>>> @@ -18,7 +18,8 @@ addtask install after do_unpack before do_prepare_build
>>>
>>> deb_package_prepare() {
>>> sudo rm -rf ${D}/DEBIAN
>>> - mkdir -p ${D}/DEBIAN
>>> + sudo mkdir -p ${D}/DEBIAN
>>> + sudo chown ${USER}:${USER} ${D}/DEBIAN
>>
>> That makes no sense to me: We remove that folder first, and then create it under
>> the name of the current user. These two changes are redundant in that light.
>>
>> Can you describe in more details what you did and how the error messages looked
>> like? I frequently rebuild dpkg-raw packages and never saw such an issue recently.
>
> Sure, the error message is the following:
> mkdir: cannot create directory `[...]/image//DEBIAN`: Permission denied
>
> This makes sense, because image/ seems to somewhere get changed to be owned by root.
> Because of this, the unprivileged mkdir fails when rebuilding. The change I made is
> to run mkdir as root and then change the ownership of the created directory. I chose
> this solutuion because I did not want to touch the permissions of image/.
But if image has the wrong permissions/ownership, that is what should be
changed. It may actually cause other problems down the road.
Jan
>
> I have seen this error with a lot of different packages so I am pretty certain that it
> is not a bug in the recipes I tested.
>
> Harald
>
>>> cat<<-__EOF__ > ${D}/DEBIAN/control
>>> Package: ${PN}
>>> Architecture: ${DISTRO_ARCH}
>>>
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-10-09 12:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 9:06 Harald Seiler
2018-10-09 10:05 ` Jan Kiszka
2018-10-09 10:28 ` Harald Seiler
2018-10-09 12:17 ` Jan Kiszka [this message]
2018-10-09 12:31 ` Jan Kiszka
2018-10-09 14:23 ` Harald Seiler
2018-10-09 15:11 ` Jan Kiszka
2018-10-22 15:57 ` Henning Schild
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=70898627-9e55-4d83-b25c-1f41cf07da51@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=hws@denx.de \
--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