Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ian Merin via buildroot <buildroot@buildroot.org>
Cc: Ian Merin <Ian.Merin@entrust.com>, "jezz@sysmic.org" <jezz@sysmic.org>
Subject: Re: [Buildroot] [PATCH] package/lxc: add libapparmor optional dependency
Date: Wed, 5 Feb 2025 15:33:53 +0100	[thread overview]
Message-ID: <20250205153353.1f380f10@windsurf> (raw)
In-Reply-To: <BN7PR11MB2788D839BE96640DA8286B62FFEE2@BN7PR11MB2788.namprd11.prod.outlook.com>

Hello Ian,

Thanks for your patch!

On Wed, 29 Jan 2025 19:46:22 +0000
Ian Merin via buildroot <buildroot@buildroot.org> wrote:

> From e56f77419a6516fef7f63746120755400948e5d3 Mon Sep 17 00:00:00 2001
> From: Ian Merin <Ian.Merin@ncipher.com>
> Date: Wed, 29 Jan 2025 11:15:20 -0500
> Subject: [PATCH] package/lxc: add libapparmor optional dependency

You didn't use git send-email to send your patch, which made it
difficult to apply. Indeed, it looks like you pasted the output of "git
format-patch" into the body of an e-mail, making the resulting e-mail
unapplicable by "git am".

> diff --git a/package/lxc/lxc.mk b/package/lxc/lxc.mk
> index b2afb978e6..d2227c3760 100644
> --- a/package/lxc/lxc.mk
> +++ b/package/lxc/lxc.mk
> @@ -13,7 +13,6 @@ LXC_DEPENDENCIES = host-pkgconf
> LXC_INSTALL_STAGING = YES
> 
> LXC_CONF_OPTS = \
> -       -Dapparmor=false \
>        -Dexamples=false \
>        -Dman=false
> 
> @@ -21,6 +20,13 @@ ifeq ($(BR2_PACKAGE_BASH_COMPLETION),y)
> LXC_DEPENDENCIES += bash-completion
> endif
> 
> +ifeq ($(BR2_PACKAGE_APPARMOR),y)

           ^^^^^^^^ This option doesn't exist, so this never triggers.
           The option is named BR2_PACKAGE_LIBAPPARMOR.

I fixed both issues and applied. Thanks!

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-02-05 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 19:46 [Buildroot] [PATCH] package/lxc: add libapparmor optional dependency Ian Merin via buildroot
2025-02-05 14:33 ` Thomas Petazzoni via buildroot [this message]
2025-02-05 14:49   ` [Buildroot] [EXTERNAL] " Ian Merin via buildroot
2025-02-05 15:00     ` Thomas Petazzoni
2025-02-05 15:19       ` Ian Merin via buildroot

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=20250205153353.1f380f10@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Ian.Merin@entrust.com \
    --cc=jezz@sysmic.org \
    --cc=thomas.petazzoni@bootlin.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