Re: [fossil-users] Corrupt database at first commit after a Fossil update

[Andy Bradford]

Thus said Stephan Beal on Thu, 08 Nov 2018 02:24:40 +0100:

> Unlike the  mailing list, the  forum allows anonymous posts,  but such
> posts are always moderated before they're visible to the public.

The mailing list actually does allow anonymous posts to a degree.

The From  header does  not have to  match the Envelope  FROM and  can be
whatever one desires, including a bogus address. All that matters to the
mailing list  software is that the  Envelope FROM matches what's  in the
MLM database.

I  exploit this  feature  by making  my From  different  from the  email
address that  is actually  subscribed to the  mailing list;  notice that
here my actual subscriber email address is never exposed:

https://marc.info/?l=fossil-users&m=153400926421821&w=2

If I had wanted, I could have put entirely bogus information in the From
and the MLM would  still send the email as long as  the Envelope FROM is
correct---only  the MLM  owner  knows my  Envelope From  and  it is  not
exposed to anyone.

Andy
-- 
TAI64 timestamp: 40005be4513a


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Corrupt database at first commit after a Fossil update

[Stephan Beal]

On Thu, Nov 8, 2018 at 2:15 AM Zoltán Kócsi  wrote:

> Oh. That's really, really sad. I much prefer mailing lists to any web
> based forum.


Most of us do as well, but: bots and spammers are making it ever more
difficult to manage mailing lists. The forum can send you mail
notifications, but replying requires going through the forum. (i don't know
if there are plans to eventually support replies via email.) Unlike the
mailing list, the forum allows anonymous posts, but such posts are always
moderated before they're visible to the public. "So far" we haven't had any
spammers/bots on the forum, but that might be because it's not yet a big
enough target for them ;).

Well, times are a changin'...
>

We have the spammers and their bots to thank for that :/.

-- 
- stephan beal
https://wanderinghorse.net/home/stephan/

"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Corrupt database at first commit after a Fossil update

[Zoltán Kócsi]

On Thu, 8 Nov 2018 01:21:34 +0100
Stephan Beal  wrote:

> PS: this mailing list is no longer active. Please use the new forums
> for future questions:
> 
> https://fossil-scm.org/forum

Oh. That's really, really sad. I much prefer mailing lists to any web
based forum. Mind you, I'd choose NNTP over any web based thingy any
time. I guess it's because the colour (or lack thereof) of my hair.
Or that I have a mail/usenet client which is much more solid than any
browser and stores data on disk, so it also works off-line to a degree.
Well, times are a changin'...

Regards,

Zoltan
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Corrupt database at first commit after a Fossil update

[Zoltán Kócsi]

On Thu, 8 Nov 2018 01:20:32 +0100
Stephan Beal  wrote:

> You probably just need to run 'rebuild' on the server once (or on a
> clone of it, then re-upload that clone as the main copy).

Yup, that was all.

Thanks a lot!!!

Best Regards,

Zoltan

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Corrupt database at first commit after a Fossil update

[Stephan Beal]

On Thu, Nov 8, 2018 at 1:13 AM Zoltán Kócsi  wrote:

> I've updated Fossil from 1.29 to 2.7 on the server and on a client. The
> database files on the server were left alone.
>

PS: this mailing list is no longer active. Please use the new forums for
future questions:

https://fossil-scm.org/forum

-- 
- stephan beal
https://wanderinghorse.net/home/stephan/

"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Corrupt database at first commit after a Fossil update

[Stephan Beal]

On Thu, Nov 8, 2018 at 1:13 AM Zoltán Kócsi  wrote:


> Error: Database error: table plink has no column named baseid: {INSERT
> OR IGNORE INTO plink(pid, cid, isprim, mtime, baseid)VALUES(2513, 2518,
> 1, 2458430.492028334, NULL)} Round-trips: 1   Artifacts sent: 2
> received: 0 Sync done, sent: 19777  received: 409  ip: 203.16.199.2
> Autosync failed.
>

Version 1.29 was released in Aug. 2014, a few months before the baseid
field was added (Nov. 2014):

https://www.fossil-scm.org/index.html/info/5dd8b2dabead37a4

You probably just need to run 'rebuild' on the server once (or on a clone
of it, then re-upload that clone as the main copy).

You haven't lost anything - it's just a question of getting the schema back
in shape.

-- 
- stephan beal
https://wanderinghorse.net/home/stephan/

"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users