[MacPorts] #16246: sudo port activate does not work
#16246: sudo port activate does not work --------------------------------------+------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: port activate activating | --------------------------------------+------------------------------------- sudo port activate kdeaccessibility3 ---> Activating kdeaccessibility3 Never finishes, never returns an error, never activates package sudo port activate gsed ---> Activating gsed 4.1.5_3 Never finishes, never returns an error, never activates package -- Ticket URL: <http://trac.macports.org/ticket/16246> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not work ------------------------------------+--------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: port activate activating ------------------------------------+--------------------------------------- Comment (by dluke@macports.org): Try adding the -dv flags to see what is happening: % sudo port -dv activate gsed If it isn't obvious, feel free to attach the output so someone can try to figure out what is going wrong. -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not work ------------------------------------+--------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: port activate activating ------------------------------------+--------------------------------------- Comment (by robert@hellometro.com): DELLOSX420:~ robert$ sudo port -dv activate kdeaccessibility3 Password: ---> Activating kdeaccessibility3 -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not work ------------------------------------+--------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: port activate activating ------------------------------------+--------------------------------------- Comment (by robert@hellometro.com): My last comment: the new line after kdeaccessibility3 and after Password: were removed, just so you know that is not how I entered it into my Terminal nor is it how the output looked. Now I know that next time I have to use the paragraph or new line button in the comment editor. Question: Can I edit my previous comment in trac? -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not work ------------------------------------+--------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: port activate activating ------------------------------------+--------------------------------------- Comment (by robert@hellometro.com): Work Around: cd /opt/local/var/macports/receipts[[BR]] sudo rm file_map.db.lock[[BR]] Suggested Fixes: Short Term: fix port so that -dv causes port -dv activate to output the fact that it is waiting for a lock Long Term: find out why the lock was there: I ran sudo port install kde, but then in stayed on the ---> Activating kdeaccessibility3 step for 24 hours before I killed it. I was only running one instance of port. So there is a bug somewhere, and a deficiency in the activate command (-dv does not provide any additional verbosity or debug info) -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not work ------------------------------------+--------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Resolution: | Keywords: port activate activating ------------------------------------+--------------------------------------- Comment (by ryandesign@macports.org): Replying to [comment:3 robert@hellometro.com]:
My last comment: the new line after kdeaccessibility3 and after Password: were removed, just so you know that is not how I entered it into my Terminal nor is it how the output looked. Now I know that next time I have to use the paragraph or new line button in the comment editor. Question: Can I edit my previous comment in trac?
You cannot edit prior comments. You do not need to use the paragraph or new line button; you need to enclose literal output in !{{{ and }}}. See WikiFormatting. -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not return waiting for a lock ------------------------------------+--------------------------------------- Reporter: robert@hellometro.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: port activate activating ------------------------------------+--------------------------------------- Changes (by afb@macports.org): * summary: sudo port activate does not work => sudo port activate does not return waiting for a lock * component: ports => base * milestone: => MacPorts base bugs -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not return waiting for a lock --------------------------------------+------------------------------------- Reporter: robert@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.6.0 Keywords: port activate activating | Port: --------------------------------------+------------------------------------- Comment(by jmr@…): Are you sure there was only one instance of port? It shows up as `tclsh` in ps output. -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#16246: sudo port activate does not return waiting for a lock ------------------------------------+--------------------------------------- Reporter: robert@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.6.0 Resolution: fixed | Keywords: port activate activating Port: | ------------------------------------+--------------------------------------- Changes (by jmr@…): * cc: jmr@… (added) * status: new => closed * resolution: => fixed * milestone: MacPorts Future => MacPorts 1.8.0 Comment: After r51133, MP will release the filemap lock after each operation is done with it, so the locking situation is now as good as it can really get. -- Ticket URL: <http://trac.macports.org/ticket/16246#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts