insufficient privileges, can't update

816 views
Skip to first unread message

Alex Gorski

unread,
Nov 4, 2015, 1:11:47 AM11/4/15
to Gqrx SDR
Alex, Michael,

Need a little helping hand with an unwilling update.
While trying to get the Oct 17th version, I run into this dialogue in Terminal :


--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 69 bytes  70.00 bytes/sec
total size is 27013120  speedup is 257267.81
receiving file list ... done

sent 36 bytes  received 76 bytes  44.80 bytes/sec
total size is 512  speedup is 4.57
Error: can't create directory "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/tmp": permission denied
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: can't create directory "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/tmp": permission denied
xxxx:~ xxxxxxx$ port upgrade outdated
Error: Insufficient privileges to write to MacPorts install prefix.



The same goes for a macport upgrade to 2.3.4

--->  Updating MacPorts base sources using rsync
MacPorts base version 2.3.3 installed,
MacPorts base version 2.3.4 downloaded.
--->  Updating the ports tree
--->  MacPorts base is outdated, installing new version 2.3.4
Installing new MacPorts release in /opt/local as root:admin; permissions 0755

Error: Error installing new MacPorts base: command execution failed
Please run `port -v selfupdate' for details.
Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed




( X-ed my account name )


I am still on my "old" Yosemite version, no system updates were performed since last GQRX version, permissions were checked and put through the repair routine.

Feel a bit lost here .....

Any advice that could help me ??

Thank you guys.

french alex

Michael Dickens

unread,
Nov 4, 2015, 2:12:13 PM11/4/15
to gq...@googlegroups.com
Hi 'french' Alex - Since you don't list the actual commands you issued, I can only guess that you didn't use "sudo" with themgiven the lack of permission. Most 'port' commands are best done using "sudo port ...", though one can set MacPorts up to keep from having to do so most of the time. If that fails, you can always do "sudo chmod -R a+rw /opt/local/var/macports" and hope for the best :) Hope this helps! - MLD

Alex Gorski

unread,
Nov 4, 2015, 7:43:36 PM11/4/15
to Gqrx SDR
Thx Michael,

Went back tonight to my "problem" and found out that I hadn't yet taken my new Xcode 7.1 out of it's "giftwrap".
Xcode needs to be validated and the license agreed before the "working" elements can be installed.

Since I'm not an Xcode enthusiast, just using it's architecture, it didn't pop up in my mind ..... rather stupid mistake !!

So went back to my sudo commands and this time ......

So, it's all good now .... until the next time I'll loose my mind on this little "detail".

It should be done in a couple of hours, since this one looks like a hefty rewrite with plenty of updated elements ( qt4 and python among those I "recognize"  )



Thank you again Michael, for reacting so quickly.


Au revoir

alex

Reply all
Reply to author
Forward
0 new messages