[MacPorts] #29506: sandbox violation fltk-devel
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- fltk-devel was recently installed as dependency (for py26-fipy). Afterward, I noticed the existence of [my user folder]/Library/Preferences/fltk.org with root ownership. It must have been created during the build or destroot of fltk-devel. -- Ticket URL: <https://trac.macports.org/ticket/29506> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- Comment(by macsforever2000@…): I see a folder called fltk.org there but it is owned by me. Inside that folder i see two files. One of which - fluid.prefs - is owned by root. But the output of port contents does not show either of the files or that directory. -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- Comment(by jjstickel@…): Replying to [comment:1 macsforever2000@…]:
I see a folder called fltk.org there but it is owned by me. Inside that folder i see two files. One of which - fluid.prefs - is owned by root. But the output of port contents does not show either of the files or that directory.
I've seen something like this before where files are created in the user directory at build time, but only if those files don't already exist. They don't show up in "port contents". Try deleting (or moving) your fltk.org folder and rebuilding fltk-devel. -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- Comment(by macsforever2000@…): You're right. They show up again and are not in "port contents". What do you propose should be done about it? Ideally in patch form. ;) -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- Comment(by jjstickel@…): Replying to [comment:3 macsforever2000@…]:
You're right. They show up again and are not in "port contents". What do you propose should be done about it? Ideally in patch form. ;)
Sorry. I am not really interested in fltk-devel and don't have time to investigate. Perhaps the maintainer for gmsh or octave could take a look? BTW, I see that gmsh is an "optional" dependency of fipy (and it is gmsh that actually depends on fltk). Should gmsh really be set as a definitive dependency for the fipy port? -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- Comment(by jmr@…): Is this still a problem after the $HOME changes in 2.0.4? -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel -------------------------------+-------------------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: fltk-devel -------------------------------+-------------------------------------------- Comment(by jjstickel@…): Replying to [comment:5 jmr@…]:
Is this still a problem after the $HOME changes in 2.0.4?
Seems to be fixed: I just performed a fresh install of fltk-devel @1.3.x-r9327_0 with no previous fltk files or directories in my $HOME, and as far as I can see, no files or directories were created in $HOME during the install. -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29506: sandbox violation fltk-devel --------------------------+-------------------------------- Reporter: jjstickel@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: fixed | Keywords: Port: fltk-devel | --------------------------+-------------------------------- Changes (by macsforever2000@…): * status: new => closed * resolution: => fixed Comment: Calling this fixed since there have been no further comments. -- Ticket URL: <https://trac.macports.org/ticket/29506#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts