Changes between Initial Version and Version 1 of Ticket #26918, comment 7


Ignore:
Timestamp:
Jun 1, 2013, 8:07:00 PM (11 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #26918, comment 7

    initial v1  
    11I can confirm seeing the same issue. We see it regardless of whether the underlying nfs filesystem is xfs or ext3.
    22
    3 The culprit appears to be in 'proc fileAttrsAsRoot {file attributes} {' in share/macports/Tcl/port1.0/portutil.tcl
     3The culprit appears to be in `proc fileAttrsAsRoot {file attributes} {` in share/macports/Tcl/port1.0/portutil.tcl
    44
    5 Specifically, the line 'eval file attributes {$file} $attributes' is trying to run (among other things), the following TCL command, which fails:
     5Specifically, the line `eval file attributes {$file} $attributes` is trying to run (among other things), the following TCL command, which fails:
    66
     7{{{
    78file attributes /path/to/foo -readonly 0
     9}}}
    810
    911Arguments about whether running MacPorts on a network aside, would it be possible to subvert this command? It seems to me unnecessary to forcibly state that a file should NOT be read-only.