All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/exim: update patches to be applied with fuzz 0
Date: Fri, 28 Jun 2024 08:36:54 +0200	[thread overview]
Message-ID: <20240628083654.6377fe91@booty> (raw)
In-Reply-To: <20240627212547.2194843-1-bernd@kuhls.net>

Hello Bernd,

On Thu, 27 Jun 2024 23:25:47 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:

> Commit 8f88a644ed "support/scripts/apply-patches.sh: set the maximum
> fuzz factor to 0" reduced the fuzz factor.
> 
> Due to this change, exim fails to build with output:
> 
>     Applying 0004-exim_lock-fix-lstat-related-build-errors.patch using patch:
>     patching file src/exim_lock.c
>     Hunk #1 FAILED at 13.
>     Hunk #2 succeeded at 27 (offset 1 line).
>     1 out of 2 hunks FAILED -- saving rejects to file src/exim_lock.c.rej
> 
> This commit rebases the package patches on the current package version
> when needed.
> 
> Fixes:
> http://autobuild.buildroot.net/results/ff27d5ebd7f24ac8cb236b83c67c2c75255e51c6/
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-06-28  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 21:25 [Buildroot] [PATCH 1/1] package/exim: update patches to be applied with fuzz 0 Bernd Kuhls
2024-06-28  6:36 ` Luca Ceresoli via buildroot [this message]
2024-06-28  6:44 ` yann.morin
2024-06-28 20:25 ` Yann E. MORIN

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=20240628083654.6377fe91@booty \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=luca.ceresoli@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 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.