Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/13 v7] support/apply-patches: bail-out on duplicate patch basenames
Date: Wed, 22 Jun 2016 23:01:57 +0200	[thread overview]
Message-ID: <20160622210157.GB3691@free.fr> (raw)
In-Reply-To: <e2fdd776-d144-a0e5-61a6-89c5217e1013@mind.be>

Arnout, All,

On 2016-05-07 22:16 +0200, Arnout Vandecappelle spake thusly:
> On 05/07/16 18:14, Yann E. MORIN wrote:
> >Patches we save can come from various locations;
> >  - bundled with Buildroot
> >  - downloaded
> >  - from one or more global-patch-dir
> >
> >It is possible that two patches lying into different locations have the
> >same basename, like so (first is bundled, second is from an hypothetical
> >global-patch-dir):
> >    package/foo/0001-fix-Makefile.patch
> >    /path/to/my/patches/foo/0001-fix-Makefile.patch
> >
> >In that case, when running legal-info, we'd save only the second patch,
> >overwriting the first. That would be oproblematic, because:
> >
> >  - either the second patch depends on the first, and thus would no longer
> >    apply (this is easy to detect, though),
> >
> >  - or the second patch does not dpend on the first, and the compliance
> >    delivery will not be complete (this is much arder to detect).
> >
> >We fix that by checking that no two patches have the same same basename.
> >If we find that the basename of the patch to be applied collides with
> >that of a previously applied patch, we error out and report the duplicate.
> >
> >The unfortunate side-effect is that existing setups will now break in
> >that situation, but that's a minor, corner-case issue that is easily
> >fixed.
> >
> >Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >Cc: Luca Ceresoli <luca@lucaceresoli.net>
> >Cc: Arnout Vandecappelle <arnout@mind.be>
> >Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> 
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> 
> 
>  Regards,
>  Arnout
> 
>  PS When I wrote earlier that this patch was "controversial", I actually
> meant "a patch that is not strictly needed to fix the
> stuff-missing-from-legal-info issue, and which could be skipped".

That's not my position: this patch (or the alternate proposal) is
required.

Without it, we could end up saving two patches with the sqame basename,
the second (e.g. from a global patch dir) overwriting the first (e.g. a
bundled patch), thus rendering the legal-info moot.

I thought I had that properly explained in the commit log. Did I miss
something, or was it not clear enough?

Regards,
Yann E. MORIN.

> >---
> >Changes v6 -> v7:
> >  - reword error message
> >
> >Changes v5 -> v6:
> >  - don't renumber, detect collision and error out  (Luca, Arnout,
> >    Thomas)
> >---
> > support/scripts/apply-patches.sh | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> >diff --git a/support/scripts/apply-patches.sh b/support/scripts/apply-patches.sh
> >index 20a1552..f8b6ca3 100755
> >--- a/support/scripts/apply-patches.sh
> >+++ b/support/scripts/apply-patches.sh
> >@@ -103,6 +103,14 @@ function apply_patch {
> >         echo "Error: missing patch file ${path}/$patch"
> >         exit 1
> >     fi
> >+    existing="$( grep -E "/${patch}\$" ${builddir}/.applied_patches_list )"
> >+    if [ -n "${existing}" ]; then
> >+        echo "Error: duplicate filename '${patch}'"
> >+        echo "Conflicting files are:"
> >+        echo "  already applied: ${existing}"
> >+        echo "  to be applied  : ${path}/${patch}"
> >+        exit 1
> >+    fi
> >     echo "${path}/${patch}" >> ${builddir}/.applied_patches_list
> >     ${uncomp} "${path}/$patch" | patch -g0 -p1 -E -d "${builddir}" -t -N $silent
> >     if [ $? != 0 ] ; then
> >
> 
> 
> -- 
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-06-22 21:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07 16:14 [Buildroot] [PATCH 00/13 v7] legal-info improvements and completeness (branch yem/legal-4) Yann E. MORIN
2016-05-07 16:14 ` [Buildroot] [PATCH 01/13 v7] support/scripts: add helper to hardlink-or-copy Yann E. MORIN
2016-05-07 18:48   ` Arnout Vandecappelle
2016-05-11 21:23   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 02/13 v7] core/legal-info: use the helper to install source archives Yann E. MORIN
2016-05-07 19:54   ` Arnout Vandecappelle
2016-05-11 21:24   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 03/13 v7] core/pkg-generic: add variable to store the package rawname-version Yann E. MORIN
2016-05-11 21:29   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 04/13 v7] core/legal-info: install source archives in their own sub-dir Yann E. MORIN
2016-05-11 21:40   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 05/13 v7] core/legal-info: add package version to license directory Yann E. MORIN
2016-05-07 20:01   ` Arnout Vandecappelle
2016-05-11 21:43     ` Thomas Petazzoni
2016-05-13 20:11       ` Yann E. MORIN
2016-05-14 21:22         ` Arnout Vandecappelle
2016-05-15  9:49           ` Yann E. MORIN
2016-05-15 17:50           ` Yann E. MORIN
2016-05-16 21:31             ` Arnout Vandecappelle
2016-06-24 13:50   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 06/13 v7] core/apply-patches: store full path of applied patches Yann E. MORIN
2016-05-07 20:09   ` Arnout Vandecappelle
2016-06-22 20:59     ` Yann E. MORIN
2016-06-24 14:02   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 07/13 v7] support/apply-patches: bail-out on duplicate patch basenames Yann E. MORIN
2016-05-07 20:16   ` Arnout Vandecappelle
2016-06-22 21:01     ` Yann E. MORIN [this message]
2016-06-24 14:09   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 08/13 v7] core/legal-info: also save patches Yann E. MORIN
2016-05-07 20:36   ` Arnout Vandecappelle
2016-06-22 21:03     ` Yann E. MORIN
2016-06-24 14:22   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 09/13 v7] core/legal-info: also save extra downloads Yann E. MORIN
2016-05-07 20:42   ` Arnout Vandecappelle
2016-06-24 14:22   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 10/13 v7] legal-info: explicitly state how patches are licensed Yann E. MORIN
2016-06-24 14:25   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 11/13 v7] core/legal-info: generate a hash of all saved files Yann E. MORIN
2016-06-24 15:08   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 12/13 v7] core/pkg-generic: reorder variables definitions for legal-info Yann E. MORIN
2016-06-24 15:10   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 13/13 v7] core/legal-info: ensure legal-info works in off-line mode Yann E. MORIN
2016-06-24 15:11   ` Thomas Petazzoni
2016-06-22 21:12 ` [Buildroot] [PATCH 00/13 v7] legal-info improvements and completeness (branch yem/legal-4) Yann E. MORIN
2016-06-24 15:11 ` Thomas Petazzoni
2016-06-24 17:20   ` 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=20160622210157.GB3691@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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