[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-users
Subject: Re: Installation of Macports appears to be corrupted.
From: Anand Sharma <anand () p-c ! io>
Date: 2018-09-29 6:14:37
Message-ID: CAMtAC+3Y0QSbbUvWAULL07yBRxyvH85QgWc3OSsQc-sECp9dDg () mail ! gmail ! com
[Download RAW message or body]
Hi! Thanks for your assistance!
This was indeed the problem. Walking from root onwards to:
/opt/local/var/macports/sources
I discovered that:
/opt/local
somehow over the course over the last few days had its permissions set to:
rwxr-x---
Changing this to:
rwxr-xr-x
Fixed the problem.
I hope this information helps someone in the future!
That is, if you experience this issue, "Error: Unable to execute port:
Could not open file:..." that it may well be caused by permissions for
others have been removed.
Thanks again!
On Sat, Sep 29, 2018, 1:19 AM Ryan Schmidt, <ryandesign@macports.org> wrote:
>
>
> On Sep 28, 2018, at 21:10, Anand Pathak Sharma wrote:
>
> > Hi everyone!
> >
> > I cannot figure out what and how happened to cause this issue but today,
> out of the perceived blue, I found that my local nginx/mysql servers
> installed via macports have stopped working. I have a feeling this may be
> related to the user/group ownership of the files in question.
> >
> > I tried uninstalling Nginx then re-installing it and received the
> following error:
> >
> > Error: Unable to execute port: Could not open file:
> /opt/local/var/macports/sources/
> rsync.macports.org/release/tarballs/ports/www/nginx/Portfile
> >
> > On a whim, I tried doing the same for another port and received the same
> message:
> >
> > Error: Unable to execute port: Could not open file:
> /opt/local/var/macports/sources/
> rsync.macports.org/release/tarballs/ports/php/php-timezonedb/Portfile
> >
> > I moved into the directory, "/opt/local/var/macports/sources/
> rsync.macports.org/release/tarballs/ports" and checked the ownership of
> the files in it and they are set to:
> >
> > root:rvm
> >
> > When viewing the ownership of macport files in parent directories, I see
> that they are set to:
> >
> > root:admin
> >
> > This inconsistency makes me feel that somehow ownership has changed and
> caused these issues.
> >
> > I'd greatly appreciate some assistance with working out this matter.
> >
> > Many thanks!
>
> The ownership of the files in /opt/local/var/macports/sources/
> rsync.macports.org should not matter. By default they will be owned by
> the uid and gid that are used on our main rsync server, which happen to be
> uid 500 and gid 505, but those aren't necessarily meaningful uid or gid
> values on your system.
>
> Check the ownership and permissions of each directory leading up to that
> one, though:
>
> ls -ld /opt /opt/local /opt/local/var /opt/local/var/macports
> /opt/local/var/macports/sources
>
> Are read and execute permission ("r-x") for every user present for each of
> those directories?
>
>
[Attachment #3 (text/html)]
<div dir="auto"><div>Hi! Thanks for your assistance! </div><div \
dir="auto"><br></div><div dir="auto">This was indeed the problem. Walking from root \
onwards to:</div><div dir="auto"><br></div><div dir="auto"><span \
style="font-family:sans-serif">/opt/local/var/macports/source</span><span \
style="font-family:sans-serif">s</span><br></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">I discovered that:</span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">/opt/local </span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">somehow over the course over the last few days had its \
permissions set to:</span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">rwxr-x---</span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">Changing this to:</span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">rwxr-xr-x</span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">Fixed the problem. </span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">I hope this information helps someone in the future! \
</span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><font \
face="sans-serif">That is, if you experience this issue, "</font><span \
style="font-family:sans-serif">Error: Unable to execute port: Could not open \
file:..." that it may well be caused by permissions for others have been \
removed. </span></div><div dir="auto"><span \
style="font-family:sans-serif"><br></span></div><div dir="auto"><span \
style="font-family:sans-serif">Thanks again! </span></div><div \
dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br><br><div \
class="gmail_quote" dir="auto"><div dir="ltr">On Sat, Sep 29, 2018, 1:19 AM Ryan \
Schmidt, <<a href="mailto:ryandesign@macports.org">ryandesign@macports.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br> <br>
On Sep 28, 2018, at 21:10, Anand Pathak Sharma wrote:<br>
<br>
> Hi everyone!<br>
> <br>
> I cannot figure out what and how happened to cause this issue but today, out of \
the perceived blue, I found that my local nginx/mysql servers installed via macports \
have stopped working. I have a feeling this may be related to the user/group \
ownership of the files in question.<br> > <br>
> I tried uninstalling Nginx then re-installing it and received the following \
error:<br> > <br>
> Error: Unable to execute port: Could not open file: \
/opt/local/var/macports/sources/<a \
href="http://rsync.macports.org/release/tarballs/ports/www/nginx/Portfile" \
rel="noreferrer noreferrer" \
target="_blank">rsync.macports.org/release/tarballs/ports/www/nginx/Portfile</a><br> \
> <br> > On a whim, I tried doing the same for another port and received the \
same message:<br> > <br>
> Error: Unable to execute port: Could not open file: \
/opt/local/var/macports/sources/<a \
href="http://rsync.macports.org/release/tarballs/ports/php/php-timezonedb/Portfile" \
rel="noreferrer noreferrer" \
target="_blank">rsync.macports.org/release/tarballs/ports/php/php-timezonedb/Portfile</a><br>
> <br>
> I moved into the directory, "/opt/local/var/macports/sources/<a \
href="http://rsync.macports.org/release/tarballs/ports" rel="noreferrer noreferrer" \
target="_blank">rsync.macports.org/release/tarballs/ports</a>" and checked the \
ownership of the files in it and they are set to:<br> > <br>
> root:rvm<br>
> <br>
> When viewing the ownership of macport files in parent directories, I see that \
they are set to:<br> > <br>
> root:admin<br>
> <br>
> This inconsistency makes me feel that somehow ownership has changed and caused \
these issues.<br> > <br>
> I'd greatly appreciate some assistance with working out this matter.<br>
> <br>
> Many thanks!<br>
<br>
The ownership of the files in /opt/local/var/macports/sources/<a \
href="http://rsync.macports.org" rel="noreferrer noreferrer" \
target="_blank">rsync.macports.org</a> should not matter. By default they will be \
owned by the uid and gid that are used on our main rsync server, which happen to be \
uid 500 and gid 505, but those aren't necessarily meaningful uid or gid values on \
your system.<br> <br>
Check the ownership and permissions of each directory leading up to that one, \
though:<br> <br>
ls -ld /opt /opt/local /opt/local/var /opt/local/var/macports \
/opt/local/var/macports/sources<br> <br>
Are read and execute permission ("r-x") for every user present for each of \
those directories?<br> <br>
</blockquote></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic