runscript converts all newlines to carriage returns

[nega]

minicom's "runscript" replaces all newline sequences in the "send" command with carriage return characters, instead of newline characters.

1) ubuntu 14.04
2) minicom-2.7-1
3) expected behavior:

~/Downloads/minicom-2.7
❯ cat /tmp/foo
send \cnewline here ->\n

~/Downloads/minicom-2.7
❯ ./src/runscript /tmp/foo | xxd
0000000: 6e65 776c 696e 6520 6865 7265 202d 3e0a newline here ->.

4) actual behavior:

~/Downloads/minicom-2.7.old
❯ cat /tmp/foo
send \cnewline here ->\n

~/Downloads/minicom-2.7.old
❯ ./src/runscript /tmp/foo | xxd
0000000: 6e65 776c 696e 6520 6865 7265 202d 3e0d newline here ->.

The attached script fixes the issue

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "minicom_runscript.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Christian Ehrhardt  (paelzer)]

Hi nega,
Thank you so muhc for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue.

Also thanks for going all the way to provide a diff.
But I checked and this is the same in Debian and even upstream still today.

Therefore This sounds like an upstream bug to me. Please can you verify this by building directly from the latest upstream source? If this can be confirmed as an upstream bug, the best route to getting it fixed in Ubuntu in this case would be to file an upstream bug if you're able to do that. Otherwise, I'm not sure what we can do directly in Ubuntu to fix the problem.

Afterwards if all extra constraints are considered and this is accepted upstream with everybody agreeing it might be safe for an SRU to Trusty. But as-is at least my expertise of that area isn't good enough to feel 100% safe not breaking anybody else that might want it as it is (since it is that way upstream for all the time ans still).

If you do end up filing an upstream bug, please link to it from here. Thanks!

[nega (nega)]

Upstream report: https://alioth.debian.org/tracker/index.php?func=detail&aid=315677&group_id=30018&atid=100031

[Nish Aravamudan (nacc)]

@nega, is there a reason you submitted a tracker request (it seems mostly dead, tbh) rather than a normal Debian bug?