Re: [OE-core] [PATCH v2 0/3] postinst fixes for opgk/dpkg
No need to be nervous. The patch will make it in; patches do not get quietly rejected. If it hasn't showed up yet, it's most likely because the patch will be tested on the autobuilder in a separate set from the 'regular patches', or (yes, this happens) it has slipped through the cracks. In that case (I know it's impossible to tell from the outside), just resend again. Also, please do help us out with oe-core patch review and recipe maintenance, particularly updating them to latest versions. Alex 2018-06-14 16:57 GMT+03:00 Stefan Agner : > On 04.06.2018 18:18, Alexander Kanavin wrote: >> On 06/04/2018 07:06 PM, Stefan Agner wrote: >> >>> Anything holding us back merging this changes? >> >> Please read the Yocto project status mail: >> >> " · Patch review/merging was slow over the past week due to >> Ross being on vacation and changes in Richard’s employment/hardware >> situation but at least some of the backlog was resolved over the >> weekend and the hardware issues should be worked around now." >> > > Gentle ping on that again. > > This week it read: > "Due to the milestone, patch merging is slowing to stabilize." > > Also, there have been patches merged which were posted after this > patchset... It is really rather important for us since it is hard to fix > in lower layers... > > So I am getting nervous whether it still makes it? > > -- > Stefan > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2 0/3] postinst fixes for opgk/dpkg
On 04.06.2018 18:18, Alexander Kanavin wrote: > On 06/04/2018 07:06 PM, Stefan Agner wrote: > >> Anything holding us back merging this changes? > > Please read the Yocto project status mail: > > " · Patch review/merging was slow over the past week due to > Ross being on vacation and changes in Richard’s employment/hardware > situation but at least some of the backlog was resolved over the > weekend and the hardware issues should be worked around now." > Gentle ping on that again. This week it read: "Due to the milestone, patch merging is slowing to stabilize." Also, there have been patches merged which were posted after this patchset... It is really rather important for us since it is hard to fix in lower layers... So I am getting nervous whether it still makes it? -- Stefan -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2 0/3] postinst fixes for opgk/dpkg
On 06/04/2018 07:06 PM, Stefan Agner wrote: Anything holding us back merging this changes? Please read the Yocto project status mail: " · Patch review/merging was slow over the past week due to Ross being on vacation and changes in Richard’s employment/hardware situation but at least some of the backlog was resolved over the weekend and the hardware issues should be worked around now." Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2 0/3] postinst fixes for opgk/dpkg
On 16.05.2018 11:13, Stefan Agner wrote: > From: Stefan Agner > > 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 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
