Can't install with packages on volume shared over Netatalk

[dave@…]

--->  Cleaning lzo
--->  Fetching archive for pkgconfig
Error: Target org.macports.archivefetch returned: lchown: /Volumes/Packages/darwin/x86_64: not owner
Error: Failed to install pkgconfig
Log for pkgconfig is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_pkgconfig/main.log
Error: The following dependencies were not installed: pkgconfig readline
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
saturn:~/Library/Keychains dave% 

Commenting out this use of chownAsRoot seemed to allow me to proceed:

# Perform a standard fetch, assembling fetch urls from
# the listed url variable and associated archive file
proc portarchivefetch::fetchfiles {args} {
    global archivefetch.fulldestpath UI_PREFIX
    global archivefetch.user archivefetch.password archivefetch.use_epsv \
           archivefetch.ignore_sslcert
    global portverbose ports_binary_only
    variable archivefetch_urls
    variable ::portfetch::urlmap

    if {![file isdirectory ${archivefetch.fulldestpath}]} {
        if {[catch {file mkdir ${archivefetch.fulldestpath}} result]} {
            elevateToRoot "archivefetch"
            set elevated yes
            if {[catch {file mkdir ${archivefetch.fulldestpath}} result]} {
                return -code error [format [msgcat::mc "Unable to create archive path: %s"] $result]
            }
        }
    }
#    chownAsRoot ${archivefetch.fulldestpath}
    if {[info exists elevated] && $elevated == yes} {

[dave@…]

Cc Me!

[dave@…]

still a problem...

BTW, that change is in /opt/local/share/macports/Tcl/package1.0/portarchivefetch.tcl

[dave@…]

probably the best option here, assuming the original call is useful in ordinary situations, would be to attempt the chown and simply ignore any errors. If we can't change permissions, we'll fail soon enough anyway.

[jmroot (Joshua Root)]

As of r77511, there is no separate archive dir.

[dave@…]

I can't understand how that addresses the problem. If anything, it sounds like you've just made it harder (nearly impossible) for me to store packages on a remotely mounted volume. Am I missing something?