Opened 5 years ago
Closed 4 years ago
#58878 closed defect (duplicate)
netpbm @10.87.01_0: Destroot failed, backslash in group name
| Reported by: | Dave-Allured (Dave Allured) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | netpbm |
Description
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?
Attachments (1)
Change History (5)
Changed 5 years ago by Dave-Allured (Dave Allured)
comment:1 Changed 5 years ago by jmroot (Joshua Root)
| Owner: | set to ryandesign |
|---|
comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → duplicate |
|---|---|
| Status: | assigned → closed |
Sorry I missed this when it was submitted, but glad you've found the explanation. As far as I know nothing has changed; as I said in comment:ticket:49501:1 as far as we know it is illegal to use a backslash in a group name on UNIX. Your system administrators need to fix this. The reporter of #49501 said in comment:ticket:49501:2 that he got no response from his IT department when he asked them to do this. Maybe if more people report the problem to them they will finally respond. MacPorts and the entire open source community cannot be expected to modify their software to work with illegal user/group names.
main.log