From: Stefan Agner <stefan@agner.ch>
To: openembedded-core@lists.openembedded.org,
alexander.kanavin@linux.intel.com
Cc: Stefan Agner <stefan.agner@toradex.com>
Subject: Re: [PATCH v2 0/3] postinst fixes for opgk/dpkg
Date: Mon, 04 Jun 2018 18:06:56 +0200 [thread overview]
Message-ID: <84556032da03a0e29a955e347028db45@agner.ch> (raw)
In-Reply-To: <20180516091352.29279-1-stefan@agner.ch>
On 16.05.2018 11:13, Stefan Agner wrote:
> From: Stefan Agner <stefan.agner@toradex.com>
>
> Hi,
>
> This follows up on the discussion a while ago:
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg104996.html
>
> Patch 1 is rather simple and really fixes the main issue. The patch
> by itself has been tested with the relevant self test and passes.
>
> Patch 2/3 get rid of /etc/*-postinsts script in cases where the package
> management is present. This avoids a bunch of unnecessary scripts to be
> present on the rootfs. It also avoids the systemd service to be present
> forever with in case no postinst scripts have been deployed:
> Condition: start condition failed at Tue 2018-05-15 10:57:43 UTC; 42s ago
> └─ ConditionPathExistsGlob=/etc/*-postinsts was not met
>
> Self test executed using:
> $ oe-selftest --run-tests runtime_test.Postinst.test_postinst_rootfs_and_boot
Anything holding us back merging this changes?
--
Stefan
>
> Changes since v1:
> - Note that patches are specific for opkg/dpkg
>
> Stefan Agner (3):
> opkg: avoid running postinst scripts twice when using systemd
> run-postinsts: for dpkg/opkg, do not rely on /etc/*-postinsts
> rootfs.py: for dpkg/opkg, don't install postinsts if package
> management is present
>
> meta/lib/oe/rootfs.py | 3 +++
> .../opkg/opkg/opkg-configure.service | 17 -----------------
> meta/recipes-devtools/opkg/opkg_0.3.6.bb | 14 --------------
> .../run-postinsts/run-postinsts/run-postinsts | 21 ++++++++++++---------
> .../run-postinsts/run-postinsts.service | 1 -
> 5 files changed, 15 insertions(+), 41 deletions(-)
> delete mode 100644 meta/recipes-devtools/opkg/opkg/opkg-configure.service
next prev parent reply other threads:[~2018-06-04 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 9:13 [PATCH v2 0/3] postinst fixes for opgk/dpkg Stefan Agner
2018-05-16 9:13 ` [PATCH v2 1/3] opkg: avoid running postinst scripts twice when using systemd Stefan Agner
2018-05-16 9:13 ` [PATCH v2 2/3] run-postinsts: for dpkg/opkg, do not rely on /etc/*-postinsts Stefan Agner
2018-05-16 9:13 ` [PATCH v2 3/3] rootfs.py: for dpkg/opkg, don't install postinsts if package management is present Stefan Agner
2018-06-04 16:06 ` Stefan Agner [this message]
2018-06-04 16:18 ` [PATCH v2 0/3] postinst fixes for opgk/dpkg Alexander Kanavin
2018-06-14 13:57 ` Stefan Agner
2018-06-14 19:08 ` Alexander Kanavin
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=84556032da03a0e29a955e347028db45@agner.ch \
--to=stefan@agner.ch \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.agner@toradex.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.