id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,port 10226,BUG: port command can't be interrupted cleanly - creates database inconsistency,yaseppochi,macports-tickets@…,"Attempting to upgrade gnupg from 1.4.4_0 to 1.4.5_0 hangs (reported separately). After waiting 5 min, I interrupted the ""port -v upgrade gnupg"" process. This left my ports in the following peculiar state: port info gnupg claims that gnupg is at 1.4.5. The PortIndex file claims that gnupg is at 1.4.5. The Portfile claims that gnupg is at 1.4.5. port outdated doesn't report gnupg as outdated. gnupg 1.4.4_0 has been deactivated, quietly leaving me without gpg. This is really evil, especially considering that the deactivation normally takes place just before activating the new version. By scrolling back to the beginning, I can see that the deactivation took place, but if one habitually runs with port -d, or immediately reruns the upgrade with -d without looking closely at the output, he'll probably miss the fact that gnupg was deactivated. port built 1 Aug 2006 00:07 JST from freshly updated CVS.",defect,closed,High,MacPorts 2.4.0,base,,fixed,,yaseppochi markd@… vinc17@… pguyot jmpp@… blb@… schneider.pj@… nerdling gardnermj@… cooljeanius frozencemetery,