Migration script fails with "unterminated substitute pattern"
See original GitHub issueThe migration script to version 1.0 (https://github.com/spring-projects/spring-hateoas/blob/master/etc/migrate-to-1.0.sh) fails when I run it on my macOS machine (Mojave 10.14.6) with the error message sed: 1: "s/Link\.REL_SELF/IanaLi ...": unterminated substitute pattern
repeated for each file matching the pattern.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:8 (1 by maintainers)
Top Results From Across the Web
sed error - unterminated substitute pattern - Stack Overflow
to work, but that creates files that keeps the old files. Removing the -e flag results in an unterminated substitute pattern error. Same...
Read more >sed error unterminated substitute pattern for new line text-bash
Sed works on a line-by-line base, hence it becomes tricky to add the coma to the previous line as that line has already...
Read more >"unterminated `s' command" when doing substitution with sed
This happens because the command substitution (the back-ticked pwd ) is unquoted, i.e. it occurs outside of any single or double quote.
Read more >bash - How do I Find a string in a file and place a string above it?
Produces error : unterminated substitute pattern. – Nicholas Adamou. Jun 6, 2018 at 19:50. @NicholasAdamou are ...
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
... Bug:5012 - "ALSA ebuild error" status:RESOLVED resolution:OBSOLETE ... script for is not working" status:RESOLVED resolution:OBSOLETE severity:major ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I also ran into same issue on mac. thanks to cdlans for figuring out the problem. I modified the script and split the expression into EXPRESSION1 AND EXPRESSION2 each with 32 lines. and then give -e “$EXPRESSON1” -e"$EXPRESSION2" to the sed
On linux it failed too with sed: can’t read : No such file or directory. I had to change the sed command to
sed -i -e "$EXPRESSION" $FILE