From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion to "support/scripts/apply-patches.sh: do not apply patches with renames"
Date: Sat, 15 May 2021 11:40:10 +0200 [thread overview]
Message-ID: <20210515094010.GA2506@scaer> (raw)
In-Reply-To: <87fsyopkcr.fsf@dell.be.48ers.dk>
Peter, Ryota, All,
On 2021-05-15 08:44 +0200, Peter Korsgaard spake thusly:
> >>>>> "Ryota" == Ryota Kinukawa <pojiro.jp@gmail.com> writes:
> > Hi. Thank you for your great work, Buildroot team.
> > I'm writing this email for suggestions to support/scripts/apply-patches.sh.
>
> > Recently, I was working with buildroot to apply patches-4.14.164-rt73.
> > It included a patch((patches-4.14.164-rt73/0462-..)) which renames a file.
> > This caused the build to terminate with an error.
[--SNIP--]
> The problem with such an option is that it describes a property of the
> build host, not of the Buildroot configuration - And we still wouldn't
> be able to use rename patches as long as that option was supported.
>
> So we want apply-patches.sh to work the same for everyone.
>
> But we're now 4 years later, so perhaps it is time to unconditionally
> drop support for GNU patch < 2.7?
>
> GNU patch 2.7 was released in September 2012, so 8.5 years ago:
>
> https://savannah.gnu.org/forum/forum.php?forum_id=7361
>
> Thomas, Yann - Any ideas how common such old patch version are nowadays?
One of the oldest supported distro that was rel;eased before patch 2.7,
is RHEL 6. It has entered Extended Support in late 2020, and is expected
to be supported until mid 2024. However, consdering this is an old
distro, Iand that there were CVes on patch < 2.7 I'd expect that RHEL 6
now packages a newer patch that is >= 2.7.
People that do not update their systems, and are stuck on so old a host
distro, will probably not update their Buildroot version either...
On the Ubuntu side (as another data point), the odest LTS is Trusty,
14.04, and it has patch 2.7.1.
As for Debian, the oldest still supported is Jessie, with Extended LTS
until mid 2022, and it was released in 2015, so presumably has patch >=
2.7 too.
So, I would be OK for requiring patch >= 2.7.
So, lets do it that way;
1. add a check in support/dependencies/dependencies.sh that patch >=
2.7 (just after/before the check for --no-backup-if-mismatch)
2. drop the test for renames in support/scripts/apply-patches.sh
Ryota, would you care to work on that and send the patches to the list,
please?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-05-15 9:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 23:27 [Buildroot] Suggestion to "support/scripts/apply-patches.sh: do not apply patches with renames" Ryota Kinukawa
2021-05-15 6:44 ` Peter Korsgaard
2021-05-15 9:40 ` Yann E. MORIN [this message]
2021-05-15 10:57 ` Romain Naour
2021-05-15 11:19 ` Yann E. MORIN
2021-05-15 11:46 ` Romain Naour
2021-05-15 12:01 ` Yann E. MORIN
2021-05-16 0:51 ` Ryota Kinukawa
2021-05-16 8:18 ` Ryota Kinukawa
2021-05-17 12:46 ` Yann E. MORIN
2021-05-17 18:55 ` Arnout Vandecappelle
2021-05-19 3:28 ` [Buildroot] [PATCH] support/dependencies, scripts: accept patches with renames pojiro.jp at gmail.com
2021-05-19 6:43 ` Yann E. MORIN
2021-05-19 8:34 ` [Buildroot] [PATCH v2] " pojiro.jp at gmail.com
2021-05-19 8:46 ` 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=20210515094010.GA2506@scaer \
--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