MacPorts 2.7.0-beta1 sqlite error: attempt to write a readonly database

Joshua Root jmr at
Thu Apr 29 15:32:15 UTC 2021

On 2021-4-29 13:57 , Joshua Root wrote:
> On 2021-4-29 06:51 , Ken Cunningham wrote:
>> Here’s a quick reproducer on Mojave (or probably any system) for 
>> anyone interested:
>> /opt/local/bin/port install sqlite3
>> cd /tmp
>> git clone 
>> <>
>> cd macports-base
>> ./configure --with-sqlite3prefix=/opt/local 
>> --with-applications-dir=/opt/tester/Applications --prefix=/opt/tester
>> make
>> sudo make install
>> export 
>> PATH=/opt/tester/bin:/opt/tester/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin 
>> /opt/tester/bin/port -v
>> sudo /opt/tester/bin/port -v
>> /opt/tester/bin/port -v
> But it works as expected when built against the system sqlite3? If so, 
> then this must be a regression in the newer sqlite3 version?

It appears that SQLite version 3.35.5 as installed by the sqlite3 port 
deletes a database's -wal and -shm files at least some of the time when 
closing. SQLite version 3.28.0 as shipped as /usr/bin/sqlite3 on 
Catalina does not. The existence of these files is necessary to read a 
WAL mode database in a directory that you don't have write permission on.

- Josh

More information about the macports-dev mailing list