From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pppd: bump version to 2.5.3
Date: Fri, 17 Jul 2026 19:02:54 +0200 [thread overview]
Message-ID: <0de8319aeab457805ececec6f65c50d0@free.fr> (raw)
In-Reply-To: <20260715203510.1121926-1-bernd@kuhls.net>
On 15/07/2026 22:35, Bernd Kuhls wrote:
> https://github.com/ppp-project/ppp/releases/tag/v2.5.3
>
> Removed patch 0001 which is not needed anymore due to fixes committed
> to
> all relevant kernel versions:
> https://github.com/ppp-project/ppp/pull/504#issuecomment-2337005682
>
> Removed patches 0002 & 0003 which are included in this release.
>
> Added new patch to fix build errors seen with older gcc versions
> detected by the Gitlab pipelines. These build errors are introduced in
> the new dhcpv6relay plugin which was added to pppd 2.5.3, no backport
> to
> buildroot LTS branches necessary.
>
> Switched back to upstream tarball which now contains the previously
> missing license files added by upstream commit
> https://github.com/ppp-project/ppp/commit/9f612dc02c34509f062ed63b60bcc7e937e25178
> and drop autoreconf as well.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-17 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 20:35 [Buildroot] [PATCH 1/1] package/pppd: bump version to 2.5.3 Bernd Kuhls
2026-07-17 17:02 ` Julien Olivain via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-17 19:19 Bernd Kuhls
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=0de8319aeab457805ececec6f65c50d0@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
/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