On 29 May 2014 15:57, Stephan Beal <sgb...@googlemail.com> wrote:
> On Thu, May 29, 2014 at 3:35 PM, Michai Ramakers <m.ramak...@gmail.com>
> wrote:
>>
>> In short, syncing with repo seems to work or not depending of
>> perms/ownership of that repo:
>>
>> root@main:/tmp/ftmp# ls -ld * .
>> root@main:/tmp/ftmp# f sync r_w -R f_f
>> ...
>>
>> root@main:/tmp/ftmp# f sync f_f -R r_w
>> Round-trips: 1 Artifacts sent: 0 received: 0
>> Error: Database error: unable to open database file: {CREATE TEMP
>> TABLE onremote(rid INTEGER PRIMARY KEY);}
>
> This is likely (i'm speculating!) a chroot-related problem, because (A) root
> has (at the OS level) no permissions restrictions and (B) fossil always
> chroot's when run as root.
> We recently had a bug where the current dir was
> not being properly determined in a chroot case, and maybe (again,
> speculating) there's a similar case which only triggers in this setup.
>
> (Remember that fossil does not know about OS-level users, with the single
> exception of the root user.)
Alright... I did not realise or forgot about always chrooting.
If anyone wants to pick this up, I would be happy to test/try. I'm
assuming it is easy to reproduce, although 'f_f' and 'r_w' were actual
repos here. (My issue here is long gone, mind - this was caused by
FTP'd repos.)
Michai
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
