Opened 13 years ago

Closed 12 years ago

#16246 closed defect (fixed)

sudo port activate does not return waiting for a lock

Reported by: robert@… Owned by: macports-tickets@…
Priority: Normal Milestone: MacPorts 1.8.0
Component: base Version: 1.6.0
Keywords: port activate activating Cc: jmroot (Joshua Root)
Port:

Description

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

Change History (9)

comment:1 Changed 13 years ago by danielluke (Daniel J. Luke)

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.

comment:2 Changed 13 years ago by robert@…

DELLOSX420:~ robert$ sudo port -dv activate kdeaccessibility3 Password: ---> Activating kdeaccessibility3

comment:3 Changed 13 years ago by robert@…

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?

comment:4 Changed 13 years ago by robert@…

Work Around:

cd /opt/local/var/macports/receipts
sudo rm file_map.db.lock

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)

comment:5 in reply to:  3 Changed 13 years ago by ryandesign (Ryan Schmidt)

Replying to 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.

comment:6 Changed 13 years ago by afb@…

Component: portsbase
Milestone: MacPorts base bugs
Summary: sudo port activate does not worksudo port activate does not return waiting for a lock

comment:7 Changed 12 years ago by tobypeterson

Milestone: MacPorts base bugsMacPorts Future

Milestone MacPorts base bugs deleted

comment:8 Changed 12 years ago by jmroot (Joshua Root)

Are you sure there was only one instance of port? It shows up as tclsh in ps output.

comment:9 Changed 12 years ago by jmroot (Joshua Root)

Cc: jmr@… added
Milestone: MacPorts FutureMacPorts 1.8.0
Resolution: fixed
Status: newclosed

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.

Note: See TracTickets for help on using tickets.