From: Peter Korsgaard <peter@korsgaard.com>
To: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Bernd Kuhls" <bernd@kuhls.net>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Nicolas Carrier" <nicolas.carrier@nav-timing.safrangroup.com>
Subject: Re: [Buildroot] [PATCH v3 1/1] package/pppd: bump package to fix startup issue
Date: Fri, 31 May 2024 18:53:28 +0200 [thread overview]
Message-ID: <877cf9ncs7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240418085858.126825-1-alexis.lothore@bootlin.com> ("Alexis Lothoré via buildroot"'s message of "Thu, 18 Apr 2024 10:58:58 +0200")
>>>>> "Alexis" == Alexis Lothoré via buildroot <buildroot@buildroot.org> writes:
> pppd fails to start on a systems with buildroot 2024.02.x because of
> missing pppd directory in /var/run. There are some logs hinting at this
> issue:
> Warning: couldn't open ppp database /var/run/pppd/pppd2.tdb
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> Can't create lock file /var/run/pppd/lock/LCK..ppp-tty-fifo1: No such file or directory
> The issue has already been detected and fixed upstream (see [1]) and is
> expected to be released on a v2.5.1, but this release seems to be stalled
> for now (see [2]). Bump on current master, which currently reflects what
> will likely be the 2.5.1.
> [1] https://github.com/ppp-project/ppp/issues/419
> [2] https://github.com/ppp-project/ppp/issues/460
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
> ---
> Changes in v3:
> - bump package instead of backporting patches, based on Bernd Kuhls'
> suggestion
> - remove patches that are now integrated in new version
Committed to 2024.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-31 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 8:58 [Buildroot] [PATCH v3 1/1] package/pppd: bump package to fix startup issue Alexis Lothoré via buildroot
2024-05-09 15:35 ` Thomas Petazzoni via buildroot
2024-05-31 16:53 ` Peter Korsgaard [this message]
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=877cf9ncs7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=alexis.lothore@bootlin.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=nicolas.carrier@nav-timing.safrangroup.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