From: Antoine Tenart <atenart@kernel.org>
To: José Pekkarinen <jose.pekkarinen@unikie.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/refpolicy: Treat all modules as custom
Date: Tue, 21 Sep 2021 09:12:46 +0200 [thread overview]
Message-ID: <163220836697.4283.6363157164675068449@kwain> (raw)
In-Reply-To: <CAJPV9MqsdZa5oCYSE-+ZsNi4w1w8CWVeUPd4CohXddt5pcr7zQ@mail.gmail.com>
Quoting José Pekkarinen (2021-09-21 08:29:38)
> On Mon, Sep 20, 2021 at 4:52 PM Antoine Tenart <[1]atenart@kernel.org>
> wrote:
>
> Reproducing locally the modules were correctly listed and enabled.
> However looking at the modules.conf generated on your machine, your
> modules' documentation is included but the modules aren't enabled (as
> modules) by default. There might be some rules in the refpolicy build
> system that can explain such a difference.
>
> I think the issue comes down to understanding how modules are selected
> to be enabled by default (or not enabled), and why your modules are
> impacted. (Then there might be something to improve in Buildroot).
>
> Can this be that I'm working with an out of date version of buildroot?
>
> My project was started with 2021.02 and I observe the refpolicy dates from
> August last year. I plan to start the works on fixing this, since it
> impacts any sort of upstreaming.
You can try with a newer version of refpolicy, in case they did fix a
bug related to this; it's a good first test to make. But there are
chances this is due to how modules are selected by default, there might
be some extra logic we don't know about.
Thanks,
Antoine
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-21 7:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 11:45 [Buildroot] [PATCH] package/refpolicy: Treat all modules as custom José Pekkarinen
2021-08-30 21:14 ` Thomas Petazzoni
2021-09-17 17:22 ` Antoine Tenart
2021-09-20 6:01 ` José Pekkarinen
2021-09-20 9:30 ` Antoine Tenart
2021-09-20 9:44 ` José Pekkarinen
2021-09-20 13:21 ` Antoine Tenart
2021-09-20 13:39 ` José Pekkarinen
2021-09-20 13:52 ` Antoine Tenart
2021-09-21 6:29 ` José Pekkarinen
2021-09-21 7:12 ` Antoine Tenart [this message]
2021-09-21 13:32 ` José Pekkarinen
2021-09-21 13:42 ` Antoine Tenart
2021-09-22 14:00 ` José Pekkarinen
2021-09-22 14:23 ` Antoine Tenart
2021-09-23 6:26 ` José Pekkarinen
2021-09-23 7:59 ` Antoine Tenart
2021-09-23 8:33 ` Antoine Tenart
2021-09-23 8:47 ` José Pekkarinen
2021-09-23 9:08 ` José Pekkarinen
2021-09-23 9:17 ` Antoine Tenart
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=163220836697.4283.6363157164675068449@kwain \
--to=atenart@kernel.org \
--cc=buildroot@buildroot.org \
--cc=jose.pekkarinen@unikie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.