| Summary: | patch applied twice? | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | stsp <stsp2> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
stsp
2021-07-07 00:04:59 UTC
I assume that you have an issue on your local repository after updating from git. Indeed, 0000-curses-link.patch has been renumbered to 0001-curses-link.patch with https://git.buildroot.net/buildroot/commit/package/readline?id=575c60ff9aaaa03662555ae9353ad4e441e7fc6f. So, I would advise to delete 0000-curses-link.patch from your local git repository. Applying 0000-curses-link.patch using patch: patching file support/shobj-conf Applying 0001-curses-link.patch using patch: --- OK, I haven't noticed the names are different: 0000-curses-link.patch 0001-curses-link.patch So there are indeed 2 similar patches under different names. Please remove one. Seems 0000-curses-link.patch is already removed, but for me - just set as untracked. Strange... |