All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve Sakoman" <steve@sakoman.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: gmouse@google.com,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [poky][PATCH] run-postinsts: do not remove postinsts directory.
Date: Wed, 24 Mar 2021 09:12:09 -1000	[thread overview]
Message-ID: <CAOSpxdZw3NnynyTGz+FUqyvcAuXCVERDgvht2x4Nx1h_NQnrpw@mail.gmail.com> (raw)
In-Reply-To: <69556966-7994-7866-9766-2124c8e386bc@gmail.com>

On Wed, Mar 24, 2021 at 8:28 AM Khem Raj <raj.khem@gmail.com> wrote:
>
>
>
> On 3/24/21 8:09 AM, Steve Sakoman wrote:
> > On Sun, Mar 21, 2021 at 12:26 AM Anton Kachalov via
> > lists.openembedded.org <gmouse=google.com@lists.openembedded.org>
> > wrote:
> >>
> >> From: "Anton D. Kachalov" <gmouse@google.com>
> >>
> >> When running on the systems having read-only rootfs backed by overlayfs,
> >> removing the whole directory lead to create a special char device file
> >> on the upperdir to reflect directory's removal. Once it is required to
> >> upgrade the whole read-only image that might contain new postinsts scripts,
> >> it will be impossible to run such scripts with a "deletion mark" file
> >> on the overlayfs -- the whole directory will be marked as deleted regardless
> >> new files in it.
> >
> > Is this something that should be considered for backporting to
> > dunfell/gatesgarth?
> >
>
> yes seems so

I thought so too, since I need it :-)  But I didn't want to grab it
just because I liked it!

Steve

> >
> >> Signed-off-by: Anton D. Kachalov <gmouse@google.com>
> >> ---
> >>   .../run-postinsts/run-postinsts/run-postinsts          | 10 ++++------
> >>   1 file changed, 4 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/meta/recipes-devtools/run-postinsts/run-postinsts/run-postinsts b/meta/recipes-devtools/run-postinsts/run-postinsts/run-postinsts
> >> index f84a7e18c8..95dccb9cae 100755
> >> --- a/meta/recipes-devtools/run-postinsts/run-postinsts/run-postinsts
> >> +++ b/meta/recipes-devtools/run-postinsts/run-postinsts/run-postinsts
> >> @@ -72,12 +72,12 @@ exec_postinst_scriptlets() {
> >>                  else
> >>                          echo "ERROR: postinst $i failed."
> >>                          [ "$POSTINST_LOGGING" = "1" ] && eval echo "ERROR: postinst $i failed." $append_log
> >> -                       remove_pi_dir=0
> >> +                       remove_rcsd_link=0
> >>                  fi
> >>          done
> >>   }
> >>
> >> -remove_pi_dir=1
> >> +remove_rcsd_link=1
> >>   if $pm_installed; then
> >>          case $pm in
> >>                  "ipk")
> >> @@ -92,9 +92,7 @@ else
> >>          exec_postinst_scriptlets
> >>   fi
> >>
> >> -# since all postinstalls executed successfully, remove the postinstalls directory
> >> -# and the rcS.d link
> >> -if [ $remove_pi_dir = 1 ]; then
> >> -       rm -rf $pi_dir
> >> +# since all postinstalls executed successfully, remove the rcS.d link
> >> +if [ $remove_rcsd_link = 1 ]; then
> >>          remove_rcsd_link
> >>   fi
> >> --
> >> 2.31.0.rc2.261.g7f71774620-goog
> >>
> >>
> >>
> >>
> >>
> >>
> >> 
> >>

  reply	other threads:[~2021-03-24 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21 10:26 [poky][PATCH] run-postinsts: do not remove postinsts directory Anton Kachalov
2021-03-24 15:09 ` [OE-core] " Steve Sakoman
2021-03-24 18:28   ` Khem Raj
2021-03-24 19:12     ` Steve Sakoman [this message]
2021-04-05 15:59       ` Anton Kachalov

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=CAOSpxdZw3NnynyTGz+FUqyvcAuXCVERDgvht2x4Nx1h_NQnrpw@mail.gmail.com \
    --to=steve@sakoman.com \
    --cc=gmouse@google.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.