Thus said David Blanford on Mon, 28 Oct 2013 16:33:11 -0600:
> Fossil internal error: repository does not exist or is in an
> unreadable directory:
Can you cause this to happen again with a different fossil file? If so,
will you share the exact commands you typed to cause this?
Thanks
Hello,
I was setting up a new fossil repository. I decided that I wanted to name
it something else so I deleted the file and created a new file. When I
tried to open it I get the following error:
Fossil internal error: repository does not exist or is in an unreadable
directory:
I read the posts
On Mon, Oct 28, 2013 at 8:39 AM, Jan Nijtmans wrote:
> 2013/10/28 Jan Nijtmans :
> > >fossil sync https://jan.nijtmans:*@
> www.fossil-scm.org/fossil
> > via proxy: http://130.139.104.40:8080
> .
> > So, if this little thing could be fixed as well, it would be perfect!
>
> Foll
On 28 October 2013 15:10, Richard Hipp wrote:
>
>> What's the rationale for even mentioning the deleted file at all? Just
>> for my info.
>
> Probably (I'm guessing) what you are seeing is some kind of bug that
> prevents an unmanaged file that was previous added by not yet committed from
> being
On Mon, Oct 28, 2013 at 10:04 AM, Michai Ramakers wrote:
> Hello,
>
> when I do this:
>
> $ touch plop
> $ fossil addremove
> $ rm plop
> $ fossil addremove
>
> ...I see in 'fossil status' and when doing 'fossil commit' one change,
> namely the deleted file. When I commit, I see a resulting entry
Hello,
when I do this:
$ touch plop
$ fossil addremove
$ rm plop
$ fossil addremove
...I see in 'fossil status' and when doing 'fossil commit' one change,
namely the deleted file. When I commit, I see a resulting entry in the
webpage timeline with no changes.
What's the rationale for even menti
2013/10/28 Jan Nijtmans :
> >fossil sync https://jan.nijtmans:*@www.fossil-scm.org/fossil
> via proxy: http://130.139.104.40:8080
.
> So, if this little thing could be fixed as well, it would be perfect!
Follow-up: If I do the same without specifying the password in the url:
2013/10/27 Jan Danielsson :
>The jan-httpsproxytunnel branch has been tested on NetBSD, Mac OS X,
> Linux and Windows against three different proxies, at two very different
> environments, and it is working well.
>
>Feedback from people more accustomed to the world of http proxies
> would b
8 matches
Mail list logo
