Will you please take me off your lists.
On Thursday, November 2, 2017, 9:48:37 PM EDT, Andy Bradford
wrote:
Thus said Martin Vahi on Wed, 01 Nov 2017 17:06:00 +0200:
> Neither of the command lines prompted for the password of the user
> martin_vahi, which is the admin username at
Thus said Martin Vahi on Wed, 01 Nov 2017 17:06:00 +0200:
> Neither of the command lines prompted for the password of the user
> martin_vahi, which is the admin username at the remote repository.
You did not tell Fossil that there is a remote user associated with the
repository. This inform
>...
> Date: Tue, 24 Oct 2017 09:14:59 -0400
> From: Karn Kallio
> To: fossil-users@lists.fossil-scm.org
> Subject: Re: [fossil-users] Bug Report: Cloning with --private Fails
> Message-ID: <20171024091459.3053205e@eka>
> ...
>
> Also, with fossil 2.3 after
Also, with fossil 2.3 after cloning a private branch you will likely
encounter errors when trying to synchronize it, such as this :
Error: Database error: UNIQUE constraint failed: private.rid: {INSERT
INTO private VALUES(4)}
Inspecting the source, it seems that in the function content_put_ex in
Thus said Martin Vahi on Mon, 23 Oct 2017 11:27:03 +0300:
> It doesn't even prompt for a password.
You didn't give it a username for which it should prompt.
Try:
time nice -n18 fossil clone --unversioned --private --admin-user
https://usern...@www.softf1.com/cgi-bin/tree1/technology/flaws/silk
An unrelated tip: with that url, anyone can download your whole repo via
your web server, bypassing fossil's login. It's far safer to store your
repo db in a path unreachable by your web server so that the db can only be
accessed via fossil.
- stephan
Sent from a mobile device, possibly from b
It doesn't even prompt for a password.
Both, client side and server side, Fossil binaries
are of version 2.3
---citation--start-
time nice -n18 fossil clone --unversioned --private --admin-user
martin_vahi
https://www.softf1.com/cgi-bin/tree1/technology/flaws/silktorrent.bash/
./repository_st
7 matches
Mail list logo
