From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org,
Ross Burton <ross.burton@intel.com>
Subject: Directories in CONFFILES Was: [meta-webserver][PATCHv4] monkey: new v1.5.1 release.
Date: Wed, 30 Jul 2014 22:12:14 +0200 [thread overview]
Message-ID: <20140730201214.GV16445@jama> (raw)
In-Reply-To: <CAEaCVQjC6f-6o1DhjR_=pCSngLsg8xCFWG+BDCpwZp-kbNKMEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4592 bytes --]
On Sat, Jul 26, 2014 at 09:03:21AM -0600, Eduardo Silva wrote:
> hi Martin,
>
>
> > > My builds are using "distroless" setup, if you're using poky then it's
> > > possible that there is still sysvinit added in your DISTRO_FEATURES
> > > somewhere (check bitbake -e monkay) so the sysv init script isn't
> > > removed in the end for you.
> >
> > I've just noticed that CONFFILES is set to
> > ${sysconfdir}/monkey/
> >
> > so it's not caused by missing init.d script but whole
> > ${sysconfdir}/monkey/ is empty in PN, can you check what's installed
> > there in your builds?
> >
> > It's either not installed when some dependency is missing or it's
> > included in different package in my build (knowing which file to look
> > for would help).
> >
> >
> thanks for tracking this. In my build using Poky i get installed the
> following files:
I think I've finally found the root cause of this
The problem is that ${sysconfdir}/monkey/ is directory and ipk backend doesn't
support directories in conffiles.
This is snipped from opkg-utils/opkg-build:
if [ -f $CONTROL/conffiles ]; then
for cf in `cat $CONTROL/conffiles`; do
if [ ! -f ./$cf ]; then
echo "*** Error: $CONTROL/conffiles mentions conffile $cf which does not exist" >&2
PKG_ERROR=1
fi
done
fi
+ Ross because of following commit in oe-core
Ross, I assume you didn't use os.path.isfile, because
RPM supports directories in conffiles, but maybe you had
plans for opkg-utils?
Do you have patch somewhere to extend opkg-utils to allow
directories in CONFFILES? Fix for this opkg-build check seems
trivial, but I haven't check how opkg will handle this on target.
commit fb87edc881009cf4d582cd95c248884551fe07fe
Author: Ross Burton <ross.burton@intel.com>
Date: Tue Feb 5 21:12:50 2013 +0000
package_ipk: check CONFFILES exist before adding them to metadata
opkg-build verifies that conffiles exist, so verify that the specified files
actually exist before writing them to conffiles.
This mirrors the behaviour of FILES and package_rpm's CONFFILES handling.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
diff --git a/meta/classes/package_ipk.bbclass b/meta/classes/package_ipk.bbclass
index d735051..e5e76ef 100644
--- a/meta/classes/package_ipk.bbclass
+++ b/meta/classes/package_ipk.bbclass
@@ -440,7 +440,8 @@ python do_package_ipk () {
bb.utils.unlockfile(lf)
raise bb.build.FuncFailed("unable to open conffiles for writing.")
for f in conffiles_str.split():
- conffiles.write('%s\n' % f)
+ if os.path.exists(oe.path.join(root, f)):
+ conffiles.write('%s\n' % f)
conffiles.close()
os.chdir(basedir)
Eduardo, temporary work around is either list all CONFFILEs separately or drop
CONFFILES (like I did for world builds)
> root@qemux86:~# find /etc/monkey/
> /etc/monkey/
> /etc/monkey/sites
> /etc/monkey/sites/default
> /etc/monkey/plugins.load
> /etc/monkey/monkey.conf
> /etc/monkey/monkey.mime
> /etc/monkey/plugins
> /etc/monkey/plugins/fastcgi
> /etc/monkey/plugins/fastcgi/fastcgi.conf
> /etc/monkey/plugins/logger
> /etc/monkey/plugins/logger/logger.conf
> /etc/monkey/plugins/mandril
> /etc/monkey/plugins/mandril/mandril.conf
> /etc/monkey/plugins/dirlisting
> /etc/monkey/plugins/dirlisting/dirhtml.conf
> /etc/monkey/plugins/dirlisting/themes
> /etc/monkey/plugins/dirlisting/themes/guineo
> /etc/monkey/plugins/dirlisting/themes/guineo/entry.theme
> /etc/monkey/plugins/dirlisting/themes/guineo/footer.theme
> /etc/monkey/plugins/dirlisting/themes/guineo/header.theme
> /etc/monkey/plugins/cgi
> /etc/monkey/plugins/cgi/cgi.conf
> /etc/monkey/plugins/auth
> /etc/monkey/plugins/auth/monkey.users
> /etc/monkey/plugins/auth/README
> /etc/monkey/plugins/proxy_reverse
> /etc/monkey/plugins/proxy_reverse/proxy_reverse.conf
> /etc/monkey/plugins/cheetah
> /etc/monkey/plugins/cheetah/cheetah.conf
>
> if you need any extra info let me know,
>
> best
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-07-30 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 6:37 [meta-webserver][PATCHv4] monkey: new v1.5.1 release Eduardo Silva
2014-07-17 17:06 ` Eduardo Silva
2014-07-18 18:15 ` Martin Jansa
2014-07-18 18:19 ` Eduardo Silva
2014-07-18 18:27 ` Martin Jansa
2014-07-20 21:15 ` Eduardo Silva
2014-07-20 21:47 ` Martin Jansa
2014-07-25 10:05 ` Martin Jansa
2014-07-26 15:03 ` Eduardo Silva
2014-07-30 20:12 ` Martin Jansa [this message]
2014-08-04 19:57 ` Eduardo Silva
2014-08-05 7:50 ` Martin Jansa
2014-08-07 4:51 ` Eduardo Silva
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=20140730201214.GV16445@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ross.burton@intel.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