Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11931] New: Bugs in support/scripts/apply-patches.sh
Date: Tue, 04 Jun 2019 08:20:13 +0000	[thread overview]
Message-ID: <bug-11931-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11931

            Bug ID: 11931
           Summary: Bugs in support/scripts/apply-patches.sh
           Product: buildroot
           Version: 2019.02.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: escape at linux.alibaba.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8076
  --> https://bugs.busybox.net/attachment.cgi?id=8076&action=edit
patch to fix this bug

Code line 120 to line 128 is to check whether the patch containing "rename
from" and "rename to". But it directly use grep to find, ignoring the patch may
be a tar file or else. It can only work on patch of textfile form. Besides, if
version of patch is higher than 2.7, rejecting patches containing "rename from"
and "rename to" is unnecessary, because it can work correctly. So it should
check verison of patch first than unpack the patch to find whether it contains
"rename from"

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-06-04  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04  8:20 bugzilla at busybox.net [this message]
2019-08-15 13:25 ` [Buildroot] [Bug 11931] Bugs in support/scripts/apply-patches.sh bugzilla at busybox.net
2020-10-17 12:45 ` bugzilla at busybox.net

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=bug-11931-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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