Tom, Graham, Yes that was the issue, with sqlite3, you have to change the permissions on the containing directory.
Armed with that information I have found a way which appears to be robust. Instead of copying the compressed file across from my main server, I crompressed the archive folder/contents, renamed the archive folder on my development server and extracted the compressed folder in its place. Did not even have to set any permissions as it took up the recursive permissions of the weewx-data folder. I have tried this a dozen times and it worked every time. I wonder whether it is worth making a note of this in the documentation as I am sure I won't be last person wanting to move across an existing database file to a new install of WeeWX 5 when it is released. As always thanks very much for your assistance. Ian On Tuesday, May 23, 2023 at 12:43:30 PM UTC+1 Tom Keffer wrote: > That's true. > > Ian: check the permissions and ownership of the parent directory, > /home/igm/weewx-data/archive. > > In the end, this problem will almost surely be due to some overlooked > permissions issue. > > On Tue, May 23, 2023 at 4:26 AM Graham Eddy <g...@geddy.au> wrote: > >> i have a vague memory that to update db file via sqlite3 API you need to >> have write perm on the file’s directory >> *⊣GE⊢* >> >> On 23 May 2023, at 9:23 pm, Tom Keffer <tke...@gmail.com> wrote: >> >> Not sure what you mean by that, Graham. Permissions on a sqlite database >> follow file permissions --- there's no special "update" permission like >> there is on MySQL. Or, do you mean something else? >> >> On Mon, May 22, 2023 at 8:11 PM Graham Eddy <g...@geddy.au> wrote: >> >>> write perm on directory for sqlite3 updates? >>> *⊣GE⊢* >>> >>> On 23 May 2023, at 7:22 am, Tom Keffer <tke...@gmail.com> wrote: >>> >>> This is surely a straightforward permissions and ownership issue. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to weewx-developm...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-development/41EE62C2-ECDE-418F-B4CD-9EC2CEF4EB75%40geddy.au >>> >>> <https://groups.google.com/d/msgid/weewx-development/41EE62C2-ECDE-418F-B4CD-9EC2CEF4EB75%40geddy.au?utm_medium=email&utm_source=footer> >>> . >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to weewx-developm...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-development/F4E6CD15-B0A3-46A9-8EDA-354FE78F6A01%40geddy.au >> >> <https://groups.google.com/d/msgid/weewx-development/F4E6CD15-B0A3-46A9-8EDA-354FE78F6A01%40geddy.au?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/60ee2f06-b163-4bb3-a304-d900932af932n%40googlegroups.com.
