Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <kai.kang@windriver.com>, <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] postfix: do NOT create directory /var/spool/mail
Date: Wed, 12 Apr 2017 14:32:02 -0500	[thread overview]
Message-ID: <ec89de92-7b7e-ee75-e398-35bb5d715b42@windriver.com> (raw)
In-Reply-To: <20170410021815.13689-1-kai.kang@windriver.com>

On 4/9/17 9:18 PM, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
> 
> postfix installs directory /var/spool/mail which conflicts with package
> shadow.
> 
> | Error: Transaction check error:
> |  file /var/spool/mail conflicts between attempted installs of
> |  postfix-3.1.1-r0.ppc64e6500 and shadow-4.2.1-r0.1.ppc64e6500
> 
> Make postfix not create /var/spool/mail that it does NOT create the
> directory on Fedora and Ubuntu either.

I am not sure this is correct.

The two packages have (according to DNF/RPM) different permissions, owner or
group assigned to that particular directory.

I think it's reasonable for both of the packages to create the directory,
however they must match in perms/owner/group.  I would defer to shadow as the
correct source for this information.

It may be necessary though to change shadow's default to something more
reasonable if 'root:root' is not right.

--Mark

> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
>  meta-networking/recipes-daemons/postfix/postfix.inc | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/meta-networking/recipes-daemons/postfix/postfix.inc b/meta-networking/recipes-daemons/postfix/postfix.inc
> index 5bb2491..4c794ff 100644
> --- a/meta-networking/recipes-daemons/postfix/postfix.inc
> +++ b/meta-networking/recipes-daemons/postfix/postfix.inc
> @@ -164,8 +164,6 @@ do_install () {
>      install -m 770 -d ${D}${localstatedir}/spool/postfix
>      chown postfix:postfix ${D}${localstatedir}/spool/postfix
>  
> -    install -m 2755 -d ${D}${localstatedir}/spool/mail
> -    chown postfix:nogroup ${D}${localstatedir}/spool/mail
>      install -m 0755 -d ${D}${localstatedir}/lib/postfix
>      chown postfix:nogroup ${D}${localstatedir}/lib/postfix
>      install -m 0755 -d ${D}${localstatedir}/spool/postfix
> 



  reply	other threads:[~2017-04-12 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  2:18 [meta-networking][PATCH] postfix: do NOT create directory /var/spool/mail kai.kang
2017-04-12 19:32 ` Mark Hatle [this message]
2017-04-13  1:46   ` Kang Kai

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=ec89de92-7b7e-ee75-e398-35bb5d715b42@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=kai.kang@windriver.com \
    --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