---
- branch: MAIN
  date: Fri Jul 17 11:34:59 UTC 2020
  files:
  - new: '1.13'
    old: '1.12'
    path: pkgsrc/shells/pbosh/Makefile
    pathrev: pkgsrc/shells/pbosh/Makefile@1.13
    type: modified
  - new: '1.11'
    old: '1.10'
    path: pkgsrc/shells/pbosh/distinfo
    pathrev: pkgsrc/shells/pbosh/distinfo@1.11
    type: modified
  id: 20200717T113459Z.758389823cbc3f5437346e8f1e9136399c826e33
  log: |
    shells/pbosh: Update to 20200701

    Take maintainership.

    Changelog from AN-2020-07-01:
    - Bourne Shell: A command like

          bosh -c 'var=$({ echo value >&3; } 3>&1); echo $var'

      Did not print "value" as expected, but rather bosh: 3: bad file number

      This is related to the fact that curly brackets do not have an
      own binary node type in the parsed output and the recursive parser
      from the $(cmd) execution needs to reconstruct the text form
      of a command tree. As a result, the command has been translated
      into:

          bosh -c 'var=$( echo value >&3 3>&1); echo $var'

      and this caused the observed problem.

      Note that this basic problem may not be finally fixed, so please
      report in case that other commands with curly brackets together
      with $(cmd) cause problems.

      Thanks to Koichi Nakashima for reporting.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/shells/pbosh'
  unixtime: '1594985699'
  user: micha