Opened 8 years ago

Closed 7 years ago

#30419 closed defect (fixed)

Groovy fails to build 10.7 Lion Macports 2 17 missing artifacts

Reported by: graphic_innovations@… Owned by: breskeby@…
Priority: Normal Milestone:
Component: ports Version: 2.0.0
Keywords: Cc: mlewis1973
Port: groovy

Description

Might be related to #30305 - removing, modifying, recreating .m2 didn't help. Fresh MacPorts 2 install for Lion. Attached log file.

Attachments (1)

main.log (60.6 KB) - added by graphic_innovations@… 8 years ago.
Groovy build log

Download all attachments as: .zip

Change History (14)

Changed 8 years ago by graphic_innovations@…

Attachment: main.log added

Groovy build log

comment:1 Changed 8 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to breskeby@…

comment:2 Changed 8 years ago by graphic_innovations@…

I'm the OP -- So, I spent more time reading the log and playing with permissions. Turns out the the default location of the .m2 folder (/private/var/root/.m2) has restricted permissions on the 'root' folder. I chmod'ed to 777 and reran the build and it worked. Don't forget to set your permissions back to the default just incase (drwxr-x---). So maybe this is a change with lion? (new permissions on /private/var/root) or the group or user is wrong for the installer?

comment:3 Changed 8 years ago by breskeby@…

Status: newassigned

comment:4 Changed 8 years ago by jhuxhorn@…

I have the following additional info:

This is not just related to Lion. I have the exact same issue on Snow Leopard. The .m2-folder in question looked like this: drwxr-xr-x 3 root staff 102 Jul 2 2010 .m2 It was located in /Users/admin in my case (admin being the sudoer-account) Simply deleting the .m2 folder wasn't sufficient. I had to recreate and chmod 777 .m2 to fix the build.

/private/var/root does not contain a .m2 folder at all in my case.

comment:5 Changed 8 years ago by breskeby@…

I've changed the installation now. I use a custom m2 folder within the working dir of the port. this should avoid permission problems with ~/.m2.

hey guys. can you test this?

comment:6 Changed 8 years ago by breskeby@…

Resolution: fixed
Status: assignedclosed

relocate the local m2 repo into the ports working dir to avoid permission problems that cause this problem

comment:7 Changed 8 years ago by graphic_innovations@…

Verified!

comment:8 Changed 8 years ago by breun (Nils Breunese)

Resolution: fixed
Status: closedreopened

I'm running OS X 10.7.1 and MacPorts 2.0.3 and although this ticket is closed as fixed I get this error. What should I be looking for?

comment:9 Changed 8 years ago by breun (Nils Breunese)

I had a custom ~/.m2/settings.xml pointing to a local Nexus instance. I temporarily renamed that file to settings.xml.disabled and then I was able to run 'sudo port install groovy'.

comment:10 in reply to:  description Changed 8 years ago by mlewis1973

Replying to graphic_innovations@…:

Might be related to #30305 - removing, modifying, recreating .m2 didn't help. Fresh MacPorts 2 install for Lion. Attached log file.

this issue still remains if you are behind a corporate firewall...... I had to insert proxy settings in settings.xml deep in ports file structure to get maven to work. Putting it in /usr/share/maven/conf/settings.xml, /private/var/root/.m2/settings.xml, or MAVEN_OPTS did not work.

comment:11 Changed 8 years ago by mlewis1973

Cc: matthew.lewis@… added

Cc Me!

comment:12 in reply to:  2 Changed 8 years ago by ryandesign (Ryan Schmidt)

Replying to graphic_innovations@…:

Turns out the the default location of the .m2 folder (/private/var/root/.m2) has restricted permissions on the 'root' folder. [...] So maybe this is a change with lion? (new permissions on /private/var/root) or the group or user is wrong for the installer?

This is a change in MacPorts. As of MacPorts 2, the new privilege dropping code is enabled by default. MacPorts no longer gives ports unrestricted access to the user's hard disk. This is a good thing.

comment:13 Changed 7 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: reopenedclosed

Seems fine with the HOME changes in 2.0.4.

Note: See TracTickets for help on using tickets.