Red Hat Bugzilla – Bug 812067
Treats "\x26" as "&"
Last modified: 2012-06-22 04:29:25 EDT
Description of problem:
This command gives unexpected output:
echo 12 | sed -e "s/\x31\x32/\x33\x26/g"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.echo 12 | sed -e "s/\x31\x32/\x33\x26/g"
for comparision with:
$ echo 12 | sed -e "s/\x31\x32/\x33\x34/g"
The documentation says that "&" is treated as the matched string, and that \xXX is treated as the ASCII character given by the hex digits.
Fixed by upstream commit 0f968ceb7bc1a65773979ef419872ce43677c790.
The component has changed its owner to me, so I'm assigning the bug to myself.
sed-4.2.1-9.fc17 has been submitted as an update for Fedora 17.
I'm submitting the updates for f16 and up right now, fixing this issue. The builds with this issue fixed will be sed-4.2.1-8.fc16, sed-4.2.1-9.fc17 and sed-4.2.1-9.fc18.
Thank you, Tim, for reporting. And you, Paolo, for fixing the bug and pointing me to the commit.
sed-4.2.1-8.fc16 has been submitted as an update for Fedora 16.
This bug seems to have be the cause of my printing issues in Bug #807446. I have updated to the latest version of sed (sed-4.2.1-8.fc16.x86_64) and so far printing seems to be working as expected.
Thanks everyone for your hard work!
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sed-4.2.1-8.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
sed-4.2.1-8.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
sed-4.2.1-9.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.