Richard, your service on all this is exemplary -- anybody who gives
you grief over this should just take a moment and reflect on all
you've done, and the remarkable stability and service we've all
enjoyed for so long.
If you want to "punt" and just have accounts recreated, I'm personally
fine w/ t
On Fri, Aug 30, 2013 at 12:35 AM, B Harder wrote:
> I don't know what the definition of "recent" is, but I think my password
> is same for months, wasn't working at time I sent last msg. I'll work with
> you off-list if necessary.
>
>
I'm still working on the problem. I'll get it fixed as quickl
I've setup a local fossil repository by exactly following these
instructions:
[1]http://write.intellectualmollusc.net/2010/01/setting-up-a-fossil-rep
ository-on-a-public-shared-server/
The server's repository was cloned from a temporary copy of the
original repo. I am able to push new changes
I don't know what the definition of "recent" is, but I think my password is
same for months, wasn't working at time I sent last msg. I'll work with you
off-list if necessary.
Thanks drh,
-bch
On Aug 29, 2013 8:12 PM, "Richard Hipp" wrote:
>
>
>
> On Thu, Aug 29, 2013 at 10:59 PM, B Harder wrot
On Thu, Aug 29, 2013 at 10:59 PM, B Harder wrote:
> Did this nuke accounts/passwords ?
>
Possibly. I restored from backup. But if passwords changed recently, the
backup might have missed them.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users ma
Did this nuke accounts/passwords ?
On 8/29/13, Richard Hipp wrote:
> On Thu, Aug 29, 2013 at 5:33 PM, Joerg Sonnenberger
> > wrote:
>
>> On Thu, Aug 29, 2013 at 04:50:19PM -0400, Richard Hipp wrote:
>> > The database corruption was caused by scenario 1.1 at
>> > http://www.sqlite.org/howtocorrupt
On Thu, Aug 29, 2013 at 6:02 PM, Jan Jurak wrote:
> Dear developers,
>
> First thank you for nice piece of software. I am using fossil for some
> of my projects and some users wants more featured ticket system. For
> example spent time for solving the issue. What is your opinion on
> that. I am t
I've found a minor bug in the way the patched sqlite3 shell handles
opening the db. In particular, this code from shell.c:
if( data.zDbFilename==0 ){
#ifndef SQLITE_OMIT_MEMORYDB
data.zDbFilename = ":memory:";
#else
fprintf(stderr,"%s: Error: no database filename specified\n", Argv0);
Dear developers,
First thank you for nice piece of software. I am using fossil for some
of my projects and some users wants more featured ticket system. For
example spent time for solving the issue. What is your opinion on
that. I am trying avoid installing another software.
TIA
--
Regards
Jan J
On Thu, Aug 29, 2013 at 5:33 PM, Joerg Sonnenberger wrote:
> On Thu, Aug 29, 2013 at 04:50:19PM -0400, Richard Hipp wrote:
> > The database corruption was caused by scenario 1.1 at
> > http://www.sqlite.org/howtocorrupt.html.
> >
> > Apparently, file descriptor 2 was closed.
>
> The question for
On Thu, Aug 29, 2013 at 04:50:19PM -0400, Richard Hipp wrote:
> The database corruption was caused by scenario 1.1 at
> http://www.sqlite.org/howtocorrupt.html.
>
> Apparently, file descriptor 2 was closed.
The question for me would be why. That should not happen and any code
should at most re-op
Cross-posting to sqlite-dev
On Thu, Aug 29, 2013 at 4:56 PM, Stephan Beal wrote:
> On Thu, Aug 29, 2013 at 10:50 PM, Richard Hipp wrote:
>
>> The database corruption was caused by scenario 1.1 at
>> http://www.sqlite.org/howtocorrupt.html.
>>
>
> "Another thread"?
>
>
>> Apparently, file d
On Thu, Aug 29, 2013 at 10:50 PM, Richard Hipp wrote:
> The database corruption was caused by scenario 1.1 at
> http://www.sqlite.org/howtocorrupt.html.
>
"Another thread"?
> Apparently, file descriptor 2 was closed. Then SQLite used file
> descriptor 2 to open a connection to the database fi
The database corruption was caused by scenario 1.1 at
http://www.sqlite.org/howtocorrupt.html.
Apparently, file descriptor 2 was closed. Then SQLite used file descriptor
2 to open a connection to the database file. Then an assert() failed,
wrote to file descriptor 2, and overwrote a portion of t
A corruption occurred in the CONCEALED table on the server. Still don't
know how that happened. I have fixed the table and so downloads should be
working again. Continuing to investigate the source of corruption.
Additional information:
(1) All of the other 77 fossil repositories on that serve
The database has gone corrupt on the server. Give me a few minutes to
figure out what it going on.
On Thu, Aug 29, 2013 at 4:24 PM, Stephan Beal wrote:
> On Thu, Aug 29, 2013 at 10:10 PM, David Given wrote:
>
>> This is head-scratchingly weird:
>>
>> dg@hilfy:/tmp$ fossil clone
>> https:/
On Thu, Aug 29, 2013 at 10:24 PM, Stephan Beal wrote:
> [stephan@host:~/tmp]$ fossil clone http://stephan:x...@fossil-scm.orgf.fsl
> Round-trips: 2 Artifacts sent: 0 received: 6062
> Error: Database error: SQL error: database disk image is malformed
>
BTW:
[stephan@host:~/cvs/fossil/fossi
On Thu, Aug 29, 2013 at 10:10 PM, David Given wrote:
> This is head-scratchingly weird:
>
> dg@hilfy:/tmp$ fossil clone
> https://dg%40cowlark.com:@fossil-scm.org fossil.fossil
> Bytes Cards Artifacts Deltas
> Sent: 53 1 0 0
> Rece
This is head-scratchingly weird:
dg@hilfy:/tmp$ fossil clone
https://dg%40cowlark.com:@fossil-scm.org fossil.fossil
Bytes Cards Artifacts Deltas
Sent: 53 1 0 0
Received: 4000570 12097 1288 4774
Sent:
If you guys are going to get into this more deeply, you should probably
also consider revocation issues. That is, what happens when it is
discovered that a contributor's private key has been compromised?
The discovery date of the compromise is obviously >= the compromise date.
As such, some set o
20 matches
Mail list logo
