[MacPorts] #58878: netpbm @10.87.01_0: Destroot failed, backslash in group name

[MacPorts]

#58878: netpbm @10.87.01_0: Destroot failed, backslash in group name
--------------------------+----------------------
 Reporter:  Dave-Allured  |      Owner:  (none)
     Type:  defect        |     Status:  assigned
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:
 Keywords:                |       Port:  netpbm
--------------------------+----------------------
 libnetpbm builds fine, then fails on destroot here:
 {{{
 :debug:destroot system: chown -R 'dallured':'PSD<cr>ain'
 /Volumes/User/dallured/port/254/var/macports/build/_Volumes_User_dallured_port_254_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_netpbm/libnetpbm/work/destroot
 :info:destroot chown: PSD\rain: illegal group name
 :info:destroot Command failed: chown -R 'dallured':'PSD<cr>ain'
 /Volumes/User/dallured/port/254/var/macports/build/_Volumes_User_dallured_port_254_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_netpbm/libnetpbm/work/destroot
 }}}
 It looks like the group name was mangled in the chown command.  The group
 name contains a backslash, so a character escape was processed by mistake.
 Backslash + r was converted to <cr>, then breakage.

 My sys admins recently expanded my unix group name, and added this
 backslash.  I had built netpbm several times before this, with no problem.

 Also please note that I was able to build 180 other ports this week,
 without hitting this name problem.  I scanned all portfiles in
 release/tarballs/ports.  The quoting on that chown command in the netpbm
 portfile is unique among all others.

 What do you think?  Fix the portfile, or try to get my sys admins to redo
 their spiffy new naming system?

-- 
Ticket URL: <https://trac.macports.org/ticket/58878>
MacPorts <https://www.macports.org/>
Ports system for macOS