From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 7/9] dpkg-raw: Clean DEBIAN dir prior to filling it
Date: Thu, 15 Feb 2018 13:20:49 +0100 [thread overview]
Message-ID: <7664005b-5ec6-7b9a-7466-0616f83dc63b@siemens.com> (raw)
In-Reply-To: <ffdbb880-c04e-4b4b-a997-2a721b0b71d6@ilbers.de>
Hi,
On 02/15/2018 11:30 AM, Alexander Smirnov wrote:
>
>
> On 02/15/2018 01:26 PM, Claudius Heine wrote:
>> On 02/15/2018 10:18 AM, Jan Kiszka wrote:
>>> On 2018-02-15 10:14, Claudius Heine wrote:
>>>> Hi Jan,
>>>>
>>>> On 02/13/2018 09:05 PM, [ext] Jan Kiszka wrote:
>>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>>
>>>>> When we run unprivileged, writing files in that directory will not
>>>>> work
>>>>> after the first run because everything is root-owned at the end.
>>>>>
>>>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>>>> ---
>>>>> meta/classes/dpkg-raw.bbclass | 5 ++---
>>>>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>>>>
>>>>> diff --git a/meta/classes/dpkg-raw.bbclass
>>>>> b/meta/classes/dpkg-raw.bbclass
>>>>> index 44aa078..e3ae9e8 100644
>>>>> --- a/meta/classes/dpkg-raw.bbclass
>>>>> +++ b/meta/classes/dpkg-raw.bbclass
>>>>> @@ -16,10 +16,9 @@ do_install() {
>>>>> do_install[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
>>>>> addtask install after do_unpack before do_deb_package_prepare
>>>>> -# so we can put hooks etc. in there already
>>>>> -do_install[dirs] = "${D}/DEBIAN"
>>>>> -
>>>>> do_deb_package_prepare() {
>>>>> + sudo rm -rf ${D}/DEBIAN
>>>>> + mkdir ${D}/DEBIAN
>>>>> cat<<-__EOF__ > ${D}/DEBIAN/control
>>>>> Package: ${PN}
>>>>> Architecture: ${DISTRO_ARCH}
>>>>>
>>>>
>>>> This:
>>>>
>>>> do_install() {
>>>> sudo install -v -m 755 ${WORKDIR}/postinst ${D}/DEBIAN/postinst
>>>> }
>>>>
>>>> causes now:
>>>>
>>>> install: cannot create regular file ‘/[...]/DEBIAN/postinst’: No
>>>> such
>>>> file or directory
>>>>
>>>> How should that be fixed?
>>>
>>> Simply by removing the install above. "dpkg-raw: Install hooks
>>> automatically" makes it obsolete.
>>
>> Thx! But now it shows:
>>
>> DEBUG: Executing shell function do_deb_package_prepare
>> mkdir: cannot create directory ‘/[...]/DEBIAN’: No such file or
>> directory
>>
>> I suppose it needs "mkdir -p ${D}/DEBIAN".
>
> BTW: this series is already in next and it has passed all CI tests.
> Which git head you use?
I rebased my own branch to next (e7e40a68adbfa60), and my stuff broke.
AFAIK next is there to test stuff with our own setup and provide
feedback, so that commits can be fixed there with sometimes even some
history rewriting.
I wouldn't be against squashing Jans patch into this one on next.
regards,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2018-02-15 12:20 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 20:05 [PATCH v2 0/9] Add support for automatic partial rebuilds on recipe changes Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 1/9] dpkg-raw: Install hooks automatically Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 2/9] Fix indention of base_do_build Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 3/9] Add clean and cleanall tasks Jan Kiszka
2018-02-14 15:14 ` [PATCH v3 " Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 4/9] Enable recipe caching Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 5/9] Move buildchroot mounts into dpkg-base class Jan Kiszka
2018-02-13 20:17 ` Alexander Smirnov
2018-02-13 20:47 ` Jan Kiszka
2018-02-14 5:54 ` Alexander Smirnov
2018-02-14 8:37 ` Jan Kiszka
2018-02-14 8:52 ` [PATCH v3 " Jan Kiszka
2018-02-14 9:09 ` Alexander Smirnov
2018-02-14 9:16 ` Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 6/9] Enable proper rebuilds on dependency changes Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 7/9] dpkg-raw: Clean DEBIAN dir prior to filling it Jan Kiszka
2018-02-15 9:14 ` Claudius Heine
2018-02-15 9:18 ` Jan Kiszka
2018-02-15 10:26 ` Claudius Heine
2018-02-15 10:30 ` Alexander Smirnov
2018-02-15 10:53 ` [PATCH] dpkg-raw: Fix creation of DEBIAN folder Jan Kiszka
2018-02-15 15:39 ` Alexander Smirnov
2018-02-26 11:39 ` Andreas Reichel
2018-02-26 12:03 ` Jan Kiszka
2018-02-26 12:27 ` Andreas Reichel
2018-02-15 12:20 ` Claudius Heine [this message]
2018-02-13 20:05 ` [PATCH v2 8/9] isar-image-base: Clean rootfs folder prior to building Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 9/9] buildchroot: Clean up rootfs prior to populating it Jan Kiszka
2018-02-14 17:43 ` Alexander Smirnov
2018-02-14 17:48 ` Jan Kiszka
2018-02-14 11:33 ` [PATCH v2 0/9] Add support for automatic partial rebuilds on recipe changes Alexander Smirnov
2018-02-14 12:41 ` Jan Kiszka
2018-02-14 12:57 ` Alexander Smirnov
2018-02-14 13:10 ` Jan Kiszka
2018-02-14 13:29 ` Jan Kiszka
2018-02-14 13:38 ` Jan Kiszka
2018-02-14 13:49 ` Jan Kiszka
2018-02-14 14:06 ` Alexander Smirnov
2018-02-14 14:03 ` Alexander Smirnov
2018-02-14 14:10 ` Jan Kiszka
2018-02-14 17:51 ` Alexander Smirnov
2018-02-14 17:54 ` Jan Kiszka
2018-02-14 17:57 ` Alexander Smirnov
2018-02-14 18:02 ` Jan Kiszka
2018-02-14 18:34 ` Alexander Smirnov
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=7664005b-5ec6-7b9a-7466-0616f83dc63b@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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