yahoo-eng-team team mailing list archive

[Igor Galić <me@xxxxxxxxx>]

Public bug reported:

When running tools/tox-venv py3 on FreeBSD, I get the following Error:

sed: 2: ":x; /\\$/ { N; s/\\\n[  ...": unused label 'x; /\\$/ { N;
s/\\\n[ ]*//; tx };'

This suggests to me, that the expression

        sed -e ':x; /\\$/ { N; s/\\\n[ ]*//; tx };' "${tox_ini}" |

is not POSIX compatible.

Looking at GNU sed's documentation, I see the first issue with making
this expression POSIX compliant will be that `N` behaves intentionally
different on GNU sed than on POSIX:

https://www.gnu.org/software/sed/manual/html_node/Reporting-Bugs.html
#Reporting-Bugs

So the solution here might be simply to require GNU sed, and put it's
path/name into an environment variable that can be overriden from the
outside.

** Affects: cloud-init
     Importance: Undecided
         Status: New


** Tags: freebsd

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1853441

Title:
  sed expression in tools/tox-venv is not POSIX compatible

Status in cloud-init:
  New

Bug description:
  When running tools/tox-venv py3 on FreeBSD, I get the following Error:

  sed: 2: ":x; /\\$/ { N; s/\\\n[  ...": unused label 'x; /\\$/ { N;
  s/\\\n[ ]*//; tx };'

  This suggests to me, that the expression

          sed -e ':x; /\\$/ { N; s/\\\n[ ]*//; tx };' "${tox_ini}" |

  is not POSIX compatible.

  Looking at GNU sed's documentation, I see the first issue with making
  this expression POSIX compliant will be that `N` behaves intentionally
  different on GNU sed than on POSIX:

  https://www.gnu.org/software/sed/manual/html_node/Reporting-Bugs.html
  #Reporting-Bugs

  So the solution here might be simply to require GNU sed, and put it's
  path/name into an environment variable that can be overriden from the
  outside.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1853441/+subscriptions