[MacPorts] #68043: MacPorts 2.8.0 in non-sudo mode, creates source files as `root` and work files as `macports` on M1 Mac
MacPorts
noreply at macports.org
Sat Aug 26 15:33:56 UTC 2023
#68043: MacPorts 2.8.0 in non-sudo mode, creates source files as `root` and work
files as `macports` on M1 Mac
--------------------+--------------------
Reporter: lukaso | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version:
Keywords: | Port:
--------------------+--------------------
This is problematic as it interferes with building GIMP on arm, as the
files have inappropriate sudo settings. It only appears to be happening on
the circleci runner (not my local Mac).
What I'm seeing is `sources` set with user `root` (everything inside is
also `root`):
{{{
% ls -las ~/macports-gimp3-arm64/var/macports
total 8
0 drwxr-xr-x@ 11 circleci staff 352 25 Aug 00:43 .
0 drwxr-xr-x 8 circleci staff 256 25 Aug 00:42 ..
0 drwxr-xr-x 173 circleci staff 5536 26 Aug 15:54 build
0 drwxr-xr-x 98 circleci staff 3136 25 Aug 02:15 distfiles
0 drwxr-xr-x 3 circleci staff 96 25 Aug 00:42 home
0 drwxr-xr-x 173 circleci staff 5536 26 Aug 15:54 logs
8 -rw-r--r-- 1 circleci staff 874 26 Aug 15:54 pingtimes
0 drwxr-xr-x 8 circleci staff 256 25 Aug 00:43 registry
0 drwxrwxrwt 2 circleci staff 64 25 Aug 00:42 sip-workaround
0 drwxr-xr-x 202 circleci staff 6464 26 Aug 15:54 software
0 drwxr-xr-x 3 root staff 96 25 Aug 00:42 sources
}}}
The knock on effect appears to be that `build` folders are then set up as
having user `root` at the top level and then everything inside is user
`macports`.
{{{
% ls -las ~/macports-gimp3-arm64/var/macports/build
total 0
0 drwxr-xr-x 173 circleci staff 5536 26 Aug 15:54 .
0 drwxr-xr-x@ 11 circleci staff 352 25 Aug 00:43 ..
0 drwxr-xr-x 3 root staff 96 25 Aug 00:45
_Users_circleci_macports-
gimp3-arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_brotli
0 drwxr-xr-x 3 root staff 96 26 Aug 15:51
_Users_circleci_macports-
gimp3-arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_bzip2
...
}}}
{{{
% ls -las ~/macports-gimp3-arm64/var/macports/build
/_Users_circleci_macports-
gimp3-arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_brotli
total 0
0 drwxr-xr-x 3 root staff 96 25 Aug 00:45 .
0 drwxr-xr-x 173 circleci staff 5536 26 Aug 15:54 ..
0 drwxr-xr-x 3 macports staff 96 25 Aug 00:45 brotli
}}}
It's very strange and I'm not sure how it can be happening.
--
Ticket URL: <https://trac.macports.org/ticket/68043>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list