From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/9] package/libselinux: bump version to 3.6
Date: Sat, 2 Mar 2024 18:07:15 +0100 [thread overview]
Message-ID: <20240302180715.39edcb20@windsurf> (raw)
In-Reply-To: <20240226205446.842600-3-adam.duskett@amarulasolutions.com>
Hello Adam,
On Mon, 26 Feb 2024 13:54:39 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> Remove upstreamed patches
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Thanks for this update.
However, could you clarify where patch 0002 has been upstreamed? I've
looked at the upstream code as of version 3.6, and it's still using
PYCEXT.
Also patch 0001 has not "really" been upstreamed, the issue has been
fixed in a different way, so I added to the commit log:
"""
Patch 0001-fix-musl-build.patch is no longer needed as the issue has
been fixed by upstream commit
d88597798fdb1a2b344ca47e48f2f80ad433fd95, which resolves the same
issue, in a different way.
"""
But unfortunately, I need additional details about why patch 0002 is no
longer needed.
Also, you missed updating .checkpackageignore, so this patch causes two
new "make check-package" warnings.
Thanks in advance for your feedback!
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
next prev parent reply other threads:[~2024-03-02 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 20:54 [Buildroot] [PATCH 1/9] package/libsepol: bump to version 3.6 Adam Duskett
2024-02-26 20:54 ` [Buildroot] [PATCH 2/9] package/libsemanage: bump version to 3.6 Adam Duskett
2024-02-26 20:54 ` [Buildroot] [PATCH 3/9] package/libselinux: " Adam Duskett
2024-03-02 17:07 ` Thomas Petazzoni via buildroot [this message]
2024-02-26 20:54 ` [Buildroot] [PATCH 4/9] package/policycoreutils: " Adam Duskett
2024-03-02 17:10 ` Thomas Petazzoni via buildroot
2024-02-26 20:54 ` [Buildroot] [PATCH 5/9] package/checkpolicy: " Adam Duskett
2024-02-26 20:54 ` [Buildroot] [PATCH 6/9] package/restorecond: " Adam Duskett
2024-02-26 20:54 ` [Buildroot] [PATCH 7/9] package/semodule-utils: " Adam Duskett
2024-02-26 20:54 ` [Buildroot] [PATCH 8/9] package/selinux-python: " Adam Duskett
2024-02-26 20:54 ` [Buildroot] [PATCH 9/9] package/setools: bump version to 4.4.4 Adam Duskett
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=20240302180715.39edcb20@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--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