From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-amarula@amarulasolutions.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/vtun: update the patches to be applied with fuzz 0
Date: Mon, 8 Jul 2024 22:21:48 +0200 [thread overview]
Message-ID: <20240708222148.2e99f88d@windsurf> (raw)
In-Reply-To: <20240707121556.4039945-1-dario.binacchi@amarulasolutions.com>
On Sun, 7 Jul 2024 14:15:56 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> Commit 8f88a644ed7d6 ("support/scripts/apply-patches.sh: set the maximum
> fuzz factor to 0") reduced the fuzz factor.
>
> Due to this change, vtun fails to build with output:
>
> Applying 0002-fix-ssl-headers-checks.patch using patch:
> patching file configure.in
> Hunk #1 succeeded at 169 (offset 3 lines).
> Hunk #2 succeeded at 179 (offset 3 lines).
> Hunk #3 FAILED at 193.
> Hunk #4 FAILED at 208.
> 2 out of 4 hunks FAILED -- saving rejects to file configure.in.rej
>
> This commit refreshes the package patch on the current package version.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> package/vtun/0002-fix-ssl-headers-checks.patch | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-08 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 12:15 [Buildroot] [PATCH 1/1] package/vtun: update the patches to be applied with fuzz 0 Dario Binacchi
2024-07-08 20:21 ` Thomas Petazzoni via buildroot [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=20240708222148.2e99f88d@windsurf \
--to=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@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