From: Joe MacDonald <joe@deserted.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] vsftpd: install volatiles file based on init system
Date: Tue, 11 Mar 2014 13:05:43 -0400 [thread overview]
Message-ID: <20140311170540.GA13065@deserted.net> (raw)
In-Reply-To: <531F372B.8010907@digi.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
[Re: [oe] [meta-networking][PATCH] vsftpd: install volatiles file based on init system] On 14.03.11 (Tue 17:17) Javier Viguera wrote:
> Hi all,
>
> Was this patch finally merged?
Sorry, no, not yet. At the end of the thread I think I had a workable
solution but I've not merged the result. If you have an updated patch
that addresses all of the systemd/sysvinit/systemd+sysvinit
combinations, I'll be happy to merge it instead of my work.
-J.
>
> At the moment building *vsftpd* in a sysvinit-based system is *broken*. The
> failure is:
>
> ERROR: QA Issue: vsftpd: Files/directories were installed but not shipped
> /run
> /run/vsftpd
> /run/vsftpd/empty
> ERROR: QA run found fatal errors. Please consider fixing them.
>
> In such sysvinit systems, '/run' usually is a TMPFS and '/run/vsftpd/empty'
> is created at *runtime* via volatiles bootscript.
>
> Creating the directory in the recipe at build time leads to the above
> mentioned error.
>
> -
> Javier Viguera
> Software Engineer
> Digi International® Spain S.A.U.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-03-11 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 19:00 [meta-networking][PATCH] vsftpd: install volatiles file based on init system Joe MacDonald
2013-12-13 10:33 ` Paul Eggleton
2013-12-13 14:34 ` Joe MacDonald
2013-12-13 14:45 ` Paul Eggleton
2014-03-11 16:17 ` Javier Viguera
2014-03-11 17:05 ` Joe MacDonald [this message]
2014-03-11 17:40 ` Javier Viguera
2014-03-14 12:47 ` Joe MacDonald
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=20140311170540.GA13065@deserted.net \
--to=joe@deserted.net \
--cc=openembedded-devel@lists.openembedded.org \
/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