Deactivating the installed version before trying to install the update

[Adam Mercer]

On Sun, Jan 19, 2014 at 10:40 PM, Jeremy Lavergne
<jeremy at lavergne.gotdns.org> wrote:

> What are the file permissions on the DB?

$ pwd
/opt/local/var/macports/registry
$ ls -l
total 69572
drwxr-xr-x  2 root admin       68 Jan 19 17:39 portfiles
-rw-r--r-- 10 root admin 71241728 Jan 19 17:39 registry.db
$

> can we get some debug output?

As I said, there's nothing extra in main.log, all that is displayed
once it's done checking the dependencies is:

DEBUG: fetch phase started at Sun Jan 19 22:56:26 CST 2014
--->  Fetching distfiles for lal
DEBUG: Executing org.macports.fetch (lal)
DEBUG: Privilege de-escalation not attempted as not running as root.
DEBUG: checksum phase started at Sun Jan 19 22:56:26 CST 2014
--->  Verifying checksums for lal
DEBUG: Executing org.macports.checksum (lal)
--->  Checksumming lal-6.12.0.tar.gz
DEBUG: Correct (rmd160) checksum for lal-6.12.0.tar.gz
DEBUG: Correct (sha256) checksum for lal-6.12.0.tar.gz
DEBUG: Privilege de-escalation not attempted as not running as root.
DEBUG: extract phase started at Sun Jan 19 22:56:26 CST 2014
--->  Extracting lal
DEBUG: Executing org.macports.extract (lal)
--->  Extracting lal-6.12.0.tar.gz
DEBUG: setting option extract.args to
'/opt/local/var/macports/distfiles/lal/lal-6.12.0.tar.gz'
DEBUG: Environment: CPATH='/opt/local/include'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_Users_ram_git_mp_testing_science_lal/lal/work/.CC_PRINT_OPTIONS'
LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES'
MACOSX_DEPLOYMENT_TARGET='10.9'
DEBUG: Assembled command: 'cd
"/opt/local/var/macports/build/_Users_ram_git_mp_testing_science_lal/lal/work"
&& /usr/bin/gzip -dc
'/opt/local/var/macports/distfiles/lal/lal-6.12.0.tar.gz' |
/usr/bin/tar -xf -'
DEBUG: Executing command line:  cd
"/opt/local/var/macports/build/_Users_ram_git_mp_testing_science_lal/lal/work"
&& /usr/bin/gzip -dc
'/opt/local/var/macports/distfiles/lal/lal-6.12.0.tar.gz' |
/usr/bin/tar -xf -
DEBUG: euid/egid changed to: 0/0
DEBUG: chowned /opt/local/var/macports/build/_Users_ram_git_mp_testing_science_lal/lal/work
to macports
DEBUG: euid/egid changed to: 502/501
DEBUG: Privilege de-escalation not attempted as not running as root.
DEBUG: patch phase started at Sun Jan 19 22:56:27 CST 2014
DEBUG: Executing org.macports.patch (lal)
DEBUG: Privilege de-escalation not attempted as not running as root.
DEBUG: configure phase started at Sun Jan 19 22:56:27 CST 2014
--->  Configuring lal
DEBUG: Using compiler 'Xcode Clang'
DEBUG: Executing proc-pre-org.macports.configure-configure-0
--->  Deactivating lal @6.11.0_2+swig_python
Error: org.macports.configure for port lal returned: sqlite error:
unable to open database file (14) while executing query: UPDATE
registry.files SET active=0 WHERE actual_path=? AND id=?
DEBUG: Error code: NONE
DEBUG: Backtrace: sqlite error: unable to open database file (14)
while executing query: UPDATE registry.files SET active=0 WHERE
actual_path=? AND id=?
    while executing
"$pre $targetname"
Warning: targets not executed for lal: org.macports.build org.macports.configure
Please see the log file for port lal for details:
    /opt/local/var/macports/logs/_Users_ram_git_mp_testing_science_lal/lal/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port lal failed

> is there a deadlock?

How would I determine that?

> is your hard drive dying?

I certainly hope not, it's been behaving itself recently so I don't
think so. Also Disk Utility isn't reporting any oddness (the disk is
in warranty until April 2017).

> Chances are, the deactivate hook is fine while something else is happening on the system. some tex packages and kde packages have used hte deactivate hook without problems.

Do you know which ones off the top of your head so I can check if I
get the same error with those?

Cheers

Adam