[PATCH] Small improvement for the initscripts package

[PATCH] Small improvement for the initscripts package

[Jef.Driesen]

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

Hi,

Attached is a small patch to remove the empty initscripts-{dev,doc,dbg} packages.

For our system, we are using some custom initscripts. Because of that, some files conflict with the initscripts package, and thus the initscript package gets removed from our build. But when trying to build an sdk, somehow the initscripts-dev package gets pulled in, and since that has an automatic dependency on initscripts, our build fails.

I've been trying to find out why this happens, but without much success so far. But I did found a simple workaround: remove the initscripts-dev package completely. Since the initscripts recipe contains some shell scripts the initscript-dev is empty anyway.

I've fixed this locally with a bbappend, but this is probably something that can be applied upstream.

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Remove-empty-packages.patch --]
[-- Type: text/x-patch; name="0001-Remove-empty-packages.patch", Size: 1177 bytes --]

From 93904b97ed3678f6c4a77e6504d2d05e967b0d71 Mon Sep 17 00:00:00 2001
From: Jef Driesen <jef.driesen@niko.eu>
Date: Fri, 29 Sep 2017 09:09:43 +0200
Subject: [PATCH] Remove empty packages

Because the initscripts recipe contains only some shell scripts, the standard
packages (e.g. ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc, etc) are all
empty and can be removed.

Signed-off-by: Jef Driesen <jef.driesen@niko.eu>
---
 meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb b/meta/recipes-core/initscripts/initscripts_1.0.bb
index f90de6e..cb056b7 100644
--- a/meta/recipes-core/initscripts/initscripts_1.0.bb
+++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
@@ -46,7 +46,7 @@ inherit update-alternatives
 DEPENDS_append = " update-rc.d-native"
 DEPENDS_append = " ${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
 
-PACKAGES =+ "${PN}-functions"
+PACKAGES = "${PN}-functions ${PN}"
 RDEPENDS_${PN} = "${PN}-functions \
                   ${@bb.utils.contains('DISTRO_FEATURES','selinux','bash','',d)} \
 		 "
-- 
2.7.4

✗ patchtest: failure for Small improvement for the initscripts package

[Patchwork]

== Series Details ==

Series: Small improvement for the initscripts package
Revision: 1
URL   : https://patchwork.openembedded.org/series/9163/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch            Small improvement for the initscripts package
 Issue             Shortlog does not follow expected format [test_shortlog_format] 
  Suggested fix    Commit shortlog (first line of commit message) should follow the format "<target>: <summary>"

* Issue             Series does not apply on top of target branch [test_series_merge_on_head] 
  Suggested fix    Rebase your series on top of targeted branch
  Targeted branch  master (currently at abf2e9526a)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

Re: [PATCH] Small improvement for the initscripts package

[Alexander Kanavin]

On 09/29/2017 11:38 AM, Jef.Driesen@niko.eu wrote:
> For our system, we are using some custom initscripts. Because of
> that, some files conflict with the initscripts package, and thus the
> initscript package gets removed from our build. But when trying to
> build an sdk, somehow the initscripts-dev package gets pulled in, and
> since that has an automatic dependency on initscripts, our build
> fails.

Please do find out why this happens; that's what you really need to fix.

> I've been trying to find out why this happens, but without much
> success so far. But I did found a simple workaround: remove the
> initscripts-dev package completely. Since the initscripts recipe
> contains some shell scripts the initscript-dev is empty anyway.
> 
> I've fixed this locally with a bbappend, but this is probably
> something that can be applied upstream.

You can use bbappend to instead replace the standard files with the ones 
that you want installed. Or you can add PROVIDES = "initscripts" to your 
recipe with the 'custom' initscripts, and set 
PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that 
installed.


Alex

Re: [PATCH] Small improvement for the initscripts package

[Jef.Driesen]

On 09/29/2017 11:38 AM, Jef.Driesen@niko.eu wrote:
>> For our system, we are using some custom initscripts. Because of
>> that, some files conflict with the initscripts package, and thus the
>> initscript package gets removed from our build. But when trying to
>> build an sdk, somehow the initscripts-dev package gets pulled in, and
>> since that has an automatic dependency on initscripts, our build
>> fails.
>
> Please do find out why this happens; that's what you really need to fix.

I tried, but I couldn't figure out where this came from.

>> I've been trying to find out why this happens, but without much
>> success so far. But I did found a simple workaround: remove the
>> initscripts-dev package completely. Since the initscripts recipe
>> contains some shell scripts the initscript-dev is empty anyway.
>>
>> I've fixed this locally with a bbappend, but this is probably
>> something that can be applied upstream.
>
> You can use bbappend to instead replace the standard files with the ones
> that you want installed. Or you can add PROVIDES = "initscripts" to your
> recipe with the 'custom' initscripts, and set
> PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that
> installed.

Those custom initscripts are not in our own layer. It's in a layer we build upon. So it's a bit more complex.

Anyway, what we have there is the following. In the machine conf file there is:

VIRTUAL-RUNTIME_initscripts = ""

This replaces the default meta/recipes-core/packagegroups/packagegroup-core-boot.bb:

VIRTUAL-RUNTIME_initscripts ?= "initscripts"

So I assume that's how they remove the initscripts package. And then in the image recipe they have:

PACKAGE_EXCLUDE += "initscripts-dev"

But for some reason this doesn't work for us. It fails with this error:

ERROR: Unable to install packages. Command '/home/bob/nhc2/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/smart --log-level=warning --data-dir=/home/bob/nhc2/yocto/build/tmp/work/emperor-poky-linux-gnueabi/image-sdk-niko/1.0-r0/sdk/image/opt/yotta/2.0.3/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/var/lib/smart install --attempt -y initscripts-dbg@armv7a_vfp_neon initscripts-dev@armv7a_vfp_neon ...' returned 1:
Loading cache...
Updating cache...               ######################################## [100%
Computing transaction...warning: Can't install initscripts-dev-1.0-r155.0@armv7a_vfp_neon: it's locked
Traceback (most recent call last):
  File "/home/bob/nhc2/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/smart.real", line 200, in <module>
    main(sys.argv[1:])
  File "/home/bob/nhc2/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/smart.real", line 173, in main
    exitcode = iface.run(opts.command, opts.argv)
  File "/home/bob/nhc2/yocto/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/smart/interface.py", line 53, in run
    result = _command.main(self._ctrl, opts)
  File "/home/bob/nhc2/yocto/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/smart/commands/install.py", line 192, in main
    trans.run()
  File "/home/bob/nhc2/yocto/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/smart/transaction.py", line 1235, in run
    del changeset[pkg]
KeyError: initscripts-dev-1.0-r155.0@armv7a_vfp_neon

DEBUG: Python function do_populate_sdk finished
ERROR: Function failed: do_populate_sdk


I'm not even sure whether PACKAGE_EXCLUDE is supposed to be used from an image recipe, because the documentation refers to local.conf. So that might explain why it doesn't work.

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.

[PATCH v2] Remove empty packages

[Jef Driesen]

Because the initscripts recipe contains only some shell scripts, the standard
packages (e.g. ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc, etc) are all
empty and can be removed.

Signed-off-by: Jef Driesen <jef.driesen@niko.eu>
---
 meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb b/meta/recipes-core/initscripts/initscripts_1.0.bb
index fea4f22..b8b33b7 100644
--- a/meta/recipes-core/initscripts/initscripts_1.0.bb
+++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
@@ -47,7 +47,7 @@ inherit update-alternatives
 DEPENDS_append = " update-rc.d-native"
 PACKAGE_WRITE_DEPS_append = " ${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
 
-PACKAGES =+ "${PN}-functions ${PN}-sushell"
+PACKAGES = "${PN}-functions ${PN}-sushell ${PN}"
 RDEPENDS_${PN} = "${PN}-functions \
                   ${@bb.utils.contains('DISTRO_FEATURES','selinux','${PN}-sushell','',d)} \
 		 "
-- 
2.7.4

✗ patchtest: failure for Small improvement for the initscripts package (rev2)

[Patchwork]

== Series Details ==

Series: Small improvement for the initscripts package (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/9163/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch            [v2] Remove empty packages
 Issue             Shortlog does not follow expected format [test_shortlog_format] 
  Suggested fix    Commit shortlog (first line of commit message) should follow the format "<target>: <summary>"



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

[PATCH v3] initscripts: Remove empty packages

[Jef Driesen]

Because the initscripts recipe contains only some shell scripts, the standard
packages (e.g. ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc, etc) are all
empty and can be removed.

Signed-off-by: Jef Driesen <jef.driesen@niko.eu>
---
 meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb b/meta/recipes-core/initscripts/initscripts_1.0.bb
index fea4f22..b8b33b7 100644
--- a/meta/recipes-core/initscripts/initscripts_1.0.bb
+++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
@@ -47,7 +47,7 @@ inherit update-alternatives
 DEPENDS_append = " update-rc.d-native"
 PACKAGE_WRITE_DEPS_append = " ${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
 
-PACKAGES =+ "${PN}-functions ${PN}-sushell"
+PACKAGES = "${PN}-functions ${PN}-sushell ${PN}"
 RDEPENDS_${PN} = "${PN}-functions \
                   ${@bb.utils.contains('DISTRO_FEATURES','selinux','${PN}-sushell','',d)} \
 		 "
-- 
2.7.4

Re: [PATCH] Small improvement for the initscripts package

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]

On 29 September 2017 at 14:21, <Jef.Driesen@niko.eu> wrote:

> On 09/29/2017 11:38 AM, Jef.Driesen@niko.eu wrote:
> >> For our system, we are using some custom initscripts. Because of
> >> that, some files conflict with the initscripts package, and thus the
> >> initscript package gets removed from our build. But when trying to
> >> build an sdk, somehow the initscripts-dev package gets pulled in, and
> >> since that has an automatic dependency on initscripts, our build
> >> fails.
> >
> > Please do find out why this happens; that's what you really need to fix.
>
> I tried, but I couldn't figure out where this came from.
>
> >> I've been trying to find out why this happens, but without much
> >> success so far. But I did found a simple workaround: remove the
> >> initscripts-dev package completely. Since the initscripts recipe
> >> contains some shell scripts the initscript-dev is empty anyway.
> >>
> >> I've fixed this locally with a bbappend, but this is probably
> >> something that can be applied upstream.
> >
> > You can use bbappend to instead replace the standard files with the ones
> > that you want installed. Or you can add PROVIDES = "initscripts" to your
> > recipe with the 'custom' initscripts, and set
> > PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that
> > installed.
>
> Those custom initscripts are not in our own layer. It's in a layer we
> build upon. So it's a bit more complex.
>
> Anyway, what we have there is the following. In the machine conf file
> there is:
>
> VIRTUAL-RUNTIME_initscripts = ""
>
> This replaces the default meta/recipes-core/packagegroups/packagegroup-
> core-boot.bb:
>
> VIRTUAL-RUNTIME_initscripts ?= "initscripts"
>
> So I assume that's how they remove the initscripts package. And then in
> the image recipe they have:
>
> PACKAGE_EXCLUDE += "initscripts-dev"
>
> But for some reason this doesn't work for us. It fails with this error:
>

I'd definitely be curious as to where initscripts is coming from in the
SDK.  You can use bitbake -g <target> to generate dependency charts.

Ross

[-- Attachment #2: Type: text/html, Size: 2912 bytes --]

Re: [PATCH v3] initscripts: Remove empty packages

[Andre McCurdy]

On Fri, Sep 29, 2017 at 7:06 AM, Jef Driesen <jef.driesen@niko.eu> wrote:
> Because the initscripts recipe contains only some shell scripts, the standard
> packages (e.g. ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc, etc) are all
> empty and can be removed.

Removing empty -dev packages can sometimes cause unexpected problems
for people who create SDKs. I don't know if that's the case here (I
guess not) but unless the empty packages are actually causing a
problem I'd be inclined to leave them alone.

> Signed-off-by: Jef Driesen <jef.driesen@niko.eu>
> ---
>  meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb b/meta/recipes-core/initscripts/initscripts_1.0.bb
> index fea4f22..b8b33b7 100644
> --- a/meta/recipes-core/initscripts/initscripts_1.0.bb
> +++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
> @@ -47,7 +47,7 @@ inherit update-alternatives
>  DEPENDS_append = " update-rc.d-native"
>  PACKAGE_WRITE_DEPS_append = " ${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
>
> -PACKAGES =+ "${PN}-functions ${PN}-sushell"
> +PACKAGES = "${PN}-functions ${PN}-sushell ${PN}"
>  RDEPENDS_${PN} = "${PN}-functions \
>                    ${@bb.utils.contains('DISTRO_FEATURES','selinux','${PN}-sushell','',d)} \
>                  "
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [PATCH] Small improvement for the initscripts package

[Jef.Driesen]

> I'd definitely be curious as to where initscripts is coming from in the SDK.  You can use bitbake -g <target> to generate dependency charts.

There are quite some packages which depend on initscripts:

$ bitbake -g image-sdk-niko -c populate_sdk
NOTE: Started PRServer with DBfile: /home/jdi/develop/yocto/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 42323, PID: 3577
Loading cache: 100% |########################################################################################################################################################################################################| ETA:  00:00:00
Loaded 2701 entries from dependency cache.
Parsing recipes: 100% |######################################################################################################################################################################################################| Time: 00:00:06
Parsing of 2167 .bb files complete (2138 cached, 29 parsed). 2729 targets, 350 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing RunQueue
NOTE: PN build list saved to 'pn-buildlist'
NOTE: PN dependencies saved to 'pn-depends.dot'
NOTE: Package dependencies saved to 'package-depends.dot'
NOTE: Task dependencies saved to 'task-depends.dot'

$ grep initscripts package-depends.dot
"dnsmasq-staticdev" -> "initscripts"
"eudev-dbg" -> "initscripts"
"avahi" -> "initscripts"
"run-postinsts-staticdev" -> "initscripts"
"avahi-doc" -> "initscripts"
"openssh-dev" -> "initscripts"
"syslog-ng-libs-dbg" -> "initscripts"
"ofono-staticdev" -> "initscripts"
"ntp-doc" -> "initscripts"
"syslog-ng-staticdev" -> "initscripts"
"ntp" -> "initscripts"
"eudev" -> "initscripts"
"openssh" -> "initscripts"
"initscripts-functions" [label="initscripts-functions(initscripts) :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts-functions" -> "update-rc.d-native"
"initscripts-functions" -> "virtual/update-alternatives"
"ntpdate" -> "initscripts"
"dbus-lib" -> "initscripts"
"openssh-locale" -> "initscripts"
"busybox-staticdev" -> "initscripts"
"cronie" -> "initscripts"
"ofono" -> "initscripts"
"ntp-dbg" -> "initscripts"
"openssh-dbg" -> "initscripts"
"busybox-mdev" -> "initscripts"
"ofono-tests" -> "initscripts"
"watchdog-dbg" -> "initscripts"
"hostapd" -> "initscripts"
"libavahi-common" -> "initscripts"
"dnsmasq-dev" -> "initscripts"
"cronie-doc" -> "initscripts"
"eudev-hwdb" -> "initscripts"
"dbus-locale" -> "initscripts"
"busybox-doc" -> "initscripts"
"initscripts-locale" [label="initscripts-locale(initscripts) :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts-locale" -> "update-rc.d-native"
"initscripts-locale" -> "virtual/update-alternatives"
"busybox-locale" -> "initscripts"
"avahi-staticdev" -> "initscripts"
"connman-tools" -> "initscripts"
"avahi-daemon" -> "initscripts"
"openssh-sshd" -> "initscripts"
"libavahi-glib" -> "initscripts"
"ofono-doc" -> "initscripts"
"ntp-utils" -> "initscripts"
"hostapd-dbg" -> "initscripts"
"libavahi-client" -> "initscripts"
"syslog-ng-dbg" -> "initscripts"
"connman-locale" -> "initscripts"
"hostapd-staticdev" -> "initscripts"
"busybox-hwclock" -> "initscripts"
"openssh-sftp" -> "initscripts"
"libavahi-ui" -> "initscripts"
"hostapd-locale" -> "initscripts"
"eudev-doc" -> "initscripts"
"initscripts-staticdev" [label="initscripts-staticdev(initscripts) :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts-staticdev" -> "update-rc.d-native"
"initscripts-staticdev" -> "virtual/update-alternatives"
"avahi-dnsconfd" -> "initscripts"
"dbus-doc" -> "initscripts"
"busybox-syslog" -> "initscripts"
"syslog-ng-locale" -> "initscripts"
"syslog-ng-libs-dev" -> "initscripts"
"run-postinsts-dev" -> "initscripts"
"connman-dev" -> "initscripts"
"dnsmasq" -> "initscripts"
"busybox-httpd" -> "initscripts"
"watchdog" -> "initscripts"
"connman-dbg" -> "initscripts"
"eudev-locale" -> "initscripts"
"avahi-dev" -> "initscripts"
"avahi-autoipd" -> "initscripts"
"libavahi-gobject" -> "initscripts"
"connman-tests" -> "initscripts"
"ofono-locale" -> "initscripts"
"openssh-ssh" -> "initscripts"
"busybox" -> "initscripts"
"ofono-dbg" -> "initscripts"
"openssh-keygen" -> "initscripts"
"hostapd-doc" -> "initscripts"
"connman-client" -> "initscripts"
"busybox-dbg" -> "initscripts"
"syslog-ng" -> "initscripts"
"libavahi-core" -> "initscripts"
"initscripts-dev" [label="initscripts-dev(initscripts) :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts-dev" -> "update-rc.d-native"
"initscripts-dev" -> "virtual/update-alternatives"
"syslog-ng-dev" -> "initscripts"
"connman" -> "initscripts"
"initscripts-dbg" [label="initscripts-dbg(initscripts) :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts-dbg" -> "update-rc.d-native"
"initscripts-dbg" -> "virtual/update-alternatives"
"openssh-sftp-server" -> "initscripts"
"sntp" -> "initscripts"
"ntp-dev" -> "initscripts"
"cronie-locale" -> "initscripts"
"dbus-dbg" -> "initscripts"
"run-postinsts-dbg" -> "initscripts"
"ntp-staticdev" -> "initscripts"
"cronie-staticdev" -> "initscripts"
"openssh-scp" -> "initscripts"
"connman-staticdev" -> "initscripts"
"watchdog-dev" -> "initscripts"
"udev-cache" -> "initscripts"
"eudev-dev" -> "initscripts"
"syslog-ng-doc" -> "initscripts"
"avahi-locale" -> "initscripts"
"ntp-locale" -> "initscripts"
"ofono-dev" -> "initscripts"
"connman-doc" -> "initscripts"
"watchdog-staticdev" -> "initscripts"
"connman-vpn" -> "initscripts"
"cronie-dev" -> "initscripts"
"dnsmasq-doc" -> "initscripts"
"run-postinsts-locale" -> "initscripts"
"run-postinsts" -> "initscripts"
"watchdog-locale" -> "initscripts"
"syslog-ng-libs" -> "initscripts"
"avahi-dbg" -> "initscripts"
"dbus" -> "initscripts"
"run-postinsts-doc" -> "initscripts"
"openssh-staticdev" -> "initscripts"
"eudev-staticdev" -> "initscripts"
"busybox-dev" -> "initscripts"
"libudev" -> "initscripts"
"openssh-doc" -> "initscripts"
"dnsmasq-locale" -> "initscripts"
"hostapd-dev" -> "initscripts"
"watchdog-doc" -> "initscripts"
"avahi-utils" -> "initscripts"
"cronie-dbg" -> "initscripts"
"initscripts" [label="initscripts :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts" -> "update-rc.d-native"
"initscripts" -> "virtual/update-alternatives"
"dnsmasq-dbg" -> "initscripts"
"busybox-udhcpc" -> "initscripts"
"busybox-udhcpd" -> "initscripts"
"openssh-misc" -> "initscripts"
"dbus-staticdev" -> "initscripts"
"dbus-dev" -> "initscripts"
"initscripts-doc" [label="initscripts-doc(initscripts) :1.0-r155\n/home/jdi/develop/yocto/meta/recipes-core/initscripts/initscripts_1.0.bb"]
"initscripts-doc" -> "update-rc.d-native"
"initscripts-doc" -> "virtual/update-alternatives"
"ntp-tickadj" -> "initscripts"
"initscripts-staticdev" -> "initscripts-dev" [style=dashed]
"initscripts-dev" -> "initscripts" [style=dashed]
"initscripts" -> "initscripts-functions" [style=dashed]

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.

Re: [PATCH] Small improvement for the initscripts package

[Jef.Driesen]

Alexander Kanavin:
> You can use bbappend to instead replace the standard files with the ones
> that you want installed. Or you can add PROVIDES = "initscripts" to your
> recipe with the 'custom' initscripts, and set
> PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that
> installed.

If I try that, I get a different error:

ERROR: The recipe base-files-emperor is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
   /home/jdi/develop/yocto/build/tmp/sysroots/emperor/sysroot-providers/initscripts
 Matched in manifest-emperor-initscripts.populate_sysroot
Please verify which recipe should provide the above files.
The build has stopped as continuing in this scenario WILL break things, if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error however switching DISTRO_FEATURES on an existing build directory is not supported, you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
ERROR: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /home/jdi/develop/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/base-files-emperor/1.0-r0/temp/log.do_populate_sysroot.8244
ERROR: Task 676 (/home/jdi/develop/yocto/meta-fifthplay-bsp/recipes-fifthplay-bsp/base-files-emperor/base-files-emperor.bb, do_populate_sysroot) failed with exit code '1'

Note: base-files-emperor is the package with the custom init scripts. I added:

PROVIDES = "initscripts"

And in conf/machine/emperor.conf, I added:

PREFERRED_PROVIDER_initscripts = "base-files-emperor"

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.

Re: [PATCH] Small improvement for the initscripts package

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

On 3 October 2017 at 11:03, <Jef.Driesen@niko.eu> wrote:

>
> Note: base-files-emperor is the package with the custom init scripts. I
> added:
>
> PROVIDES = "initscripts"
>
> And in conf/machine/emperor.conf, I added:
>
> PREFERRED_PROVIDER_initscripts = "base-files-emperor"
>

If your initscripts package is a replacement for the oe-core initscripts
package, then also set RPROVIDES_${PN} += "initscripts".

Ross

[-- Attachment #2: Type: text/html, Size: 807 bytes --]

Re: [PATCH] Small improvement for the initscripts package

[Jef.Driesen]

Burton, Ross [ross.burton@intel.com]
> On 3 October 2017 at 11:03, <Jef.Driesen@niko.eu> wrote:
>> Note: base-files-emperor is the package with the custom init scripts. I added:
>>
>> PROVIDES = "initscripts"
>>
>> And in conf/machine/emperor.conf, I added:
>>
>> PREFERRED_PROVIDER_initscripts = "base-files-emperor"
>>
>  If your initscripts package is a replacement for the oe-core initscripts package, then also set RPROVIDES_${PN} += "initscripts".

I tried your suggest, but I still get the error:

"The recipe base-files-emperor is trying to install files into a shared area when those files already exist." error

With base-files-emperor.bb containing:

PROVIDES += "initscripts"
RPROVIDES_${PN} += "initscripts"

What am I still doing wrong?

(I'll try to re-build after wiping the tmp directory tonight. A simple "bitbake -c cleanall initscripts base-files-emperor" didn't help.)

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.

Re: [PATCH] Small improvement for the initscripts package

[Alexander Kanavin]

On 10/03/2017 06:03 PM, Jef.Driesen@niko.eu wrote:
> Burton, Ross [ross.burton@intel.com]
>> On 3 October 2017 at 11:03, <Jef.Driesen@niko.eu> wrote:
>>> Note: base-files-emperor is the package with the custom init scripts. I added:
>>>
>>> PROVIDES = "initscripts"
>>>
>>> And in conf/machine/emperor.conf, I added:
>>>
>>> PREFERRED_PROVIDER_initscripts = "base-files-emperor"
>>>
>>   If your initscripts package is a replacement for the oe-core initscripts package, then also set RPROVIDES_${PN} += "initscripts".
> 
> I tried your suggest, but I still get the error:
> 
> "The recipe base-files-emperor is trying to install files into a shared area when those files already exist." error
> 
> With base-files-emperor.bb containing:
> 
> PROVIDES += "initscripts"
> RPROVIDES_${PN} += "initscripts"
> 
> What am I still doing wrong?
> 
> (I'll try to re-build after wiping the tmp directory tonight. A simple "bitbake -c cleanall initscripts base-files-emperor" didn't help.)

I might be reading it wrong, but the full error message seems to 
indicate you also have a recipe called emperor-intscripts that provides 
(some of) the same files as base-files-emperor, and they clash?

Alex

Re: [PATCH] Small improvement for the initscripts package

[Jef.Driesen]

Alexander Kanavin:
>On 10/03/2017 06:03 PM, Jef.Driesen@niko.eu wrote:
>> Burton, Ross [ross.burton@intel.com]
>>> On 3 October 2017 at 11:03, <Jef.Driesen@niko.eu> wrote:
>>>> Note: base-files-emperor is the package with the custom init scripts. I added:
>>>>
>>>> PROVIDES = "initscripts"
>>>>
>>>> And in conf/machine/emperor.conf, I added:
>>>>
>>>> PREFERRED_PROVIDER_initscripts = "base-files-emperor"
>>>>
>>>   If your initscripts package is a replacement for the oe-core initscripts package, then also set RPROVIDES_${PN} += "initscripts".
>>
>> I tried your suggest, but I still get the error:
>>
>> "The recipe base-files-emperor is trying to install files into a shared area when those files already exist." error
>>
>> With base-files-emperor.bb containing:
>>
>> PROVIDES += "initscripts"
>> RPROVIDES_${PN} += "initscripts"
>>
>> What am I still doing wrong?
>>
>> (I'll try to re-build after wiping the tmp directory tonight. A simple "bitbake -c cleanall initscripts base-files-emperor" didn't help.)
>
> I might be reading it wrong, but the full error message seems to
> indicate you also have a recipe called emperor-intscripts that provides
> (some of) the same files as base-files-emperor, and they clash?

It's the oe-core initscripts recipe that clashes with base-files-emperor. Both recipies have their own /etc/init.d/halt script.

The full rebuild failed as well, with the error "Can't install ntp-4.2.8p8-r0.7@armv7a_vfp_neon: no package provides initscripts-functions"

And that's probably because the oe-core recipe produces a initscripts-functions package. We stil need that package in our image. I assume that due to using PROVIDES, the oe-core initscripts recipe is replaced completely with our own base-files-emperor recipe. And since our custom package doesn't produce an initscripts-functions package (because we still want the one from the oe-core initscripts), the build fails. So it looks like using PROVIDES doesn't work.

Alex
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to which it is addressed. If you receive this e-mail by mistake, please delete this e-mail from your system and destroy all copies of it. It may contain confidential and/or privileged information. You should not copy it or use it for any purpose nor disclose its contents to any person unless allowed by a written document between the sender and the addressee.