On Oct 18, 2017, at 8:04 AM, Richard Hipp wrote:
> On 10/18/17, Warren Young wrote:
>> On Oct 18, 2017, at 3:44 AM, Warren Young wrote:
>>>
>>> The more web apps that ship with stringent Content-Security-Policy
>>> headers, the fewer arguments we’ll have for allowing JS on web pages.
>
> I'd
On Sep 26, 2017, at 10:35 AM, Warren Young wrote:
>> fossil sqlite3 .dump -R /mnt/kd/fossil/astlinux.fossil > dump2
>> --
>> The dump2 INSERT INTO table names are "double-quoted".
>> ex: INSERT INTO "tag" VALUES(1,'bgcolor’);
>
> The quotes are both legal SQL and unnecessary, since Fossil doesn
On Sep 26, 2017, at 9:01 AM, Warren Young wrote:
> On Sep 26, 2017, at 7:10 AM, Lonnie Abelbeck
> wrote:
>>
>> sqlite3 /mnt/kd/fossil/astlinux.fossil .dump >
>> "$CUSTOM_BACKUP_DIR/astlinux.fossil.dump”
>
> [snip]
>
>> This seems to work well
Greetings,
Our AstLinux Project just added Tarsnap https://www.tarsnap.com support and we
want to (efficiently) backup our Fossil database.
Since Tarsnap does deduplication before compression and encryption, it is most
efficient with uncompressed text-ish files.
So, in my Tarsnap backup pre-sc
On Mar 5, 2017, at 5:01 PM, Richard Hipp wrote:
> The big change is that now Fossil will actually generate SHA3-256
> hashes for new artifacts, if you ask it to, or by default in new
> repositories. See
> https://www.fossil-scm.org/fossil/doc/trunk/www/hashpolicy.wiki for
> details.
Kudos to Ri
On Mar 5, 2017, at 10:15 AM, Richard Hipp wrote:
> On 3/5/17, Lonnie Abelbeck wrote:
>> For what is planned for Fossil 2.1, will new repos created using 2.1 using:
>> --
>> fossil init --sha1 repo.fossil
>> --
>> be compatible with recent Fossil 1.x versions ?
For what is planned for Fossil 2.1, will new repos created using 2.1 using:
--
fossil init --sha1 repo.fossil
--
be compatible with recent Fossil 1.x versions ?
Ref: Add the --sha1 option to the "fossil new" command, to simplify the
creation of new SHA1-only repositories.
http://fossil-scm.org/in
On Jan 28, 2017, at 1:57 PM, Richard Hipp wrote:
> On 1/28/17, Joe Mistachkin wrote:
>>
>> Lonnie Abelbeck wrote:
>>>
>>> BTW, this also segfaults in Fossil 1.35, only discovered it by
>>> randomly clicking, testing 1.37.
>>>
>>
&g
BTW, this also segfaults in Fossil 1.35, only discovered it by randomly
clicking, testing 1.37.
Lonnie
On Jan 28, 2017, at 11:47 AM, Lonnie Abelbeck wrote:
> I recently upgraded fossil to 1.37 for our project (cross-compiled from
> source).
>
> In our case the "no
I recently upgraded fossil to 1.37 for our project (cross-compiled from source).
In our case the "nobody" user has "a" Capabilities. This is desired since
fossil (listening on 127.0.0.1) is accessed via an authenticated HTTPS proxy
using lighttpd.
In the web interface, click on "Login" and whi
On Oct 9, 2016, at 8:31 PM, Richard Hipp wrote:
> https://news.ycombinator.com/item?id=12673229
Our project uses Fossil to track configuration files for various open source
packages, git was a non-starter for our small, embedded 50 MB image.
Fossil's small footprint and efficiency with built-
On Jul 1, 2016, at 3:42 PM, Ross Berteig wrote:
> On 7/1/2016 10:11 AM, Lonnie Abelbeck wrote:
>> It seems the Checksums are on a different site from the downloads,
>> raising the bar for mischief. BTW including 1.35 now.
>> http://www.hwaci.com/fossil_download_checksums.ht
On Jul 1, 2016, at 11:39 AM, Warren Young wrote:
> On Jun 30, 2016, at 7:21 PM, Todd C. Olson wrote:
>>
>> The checksum file on the down load page only has values for up to v1.34
>> Where do we get the values for v1.35
>
> Why do you trust such things in the first case?
>
> If you’re expecti
Hi,
At a quick glance there does not seem any way to determine the Fossil Release
Version from the web interface.
It seems some skins show the Release Version in the footer, and some do not. I
would like to request the default skin to do so as per this trivial patch...
@@ -1,6 +1,6 @@
On Sep 11, 2015, at 7:19 PM, Scott Robison wrote:
> On Fri, Sep 11, 2015 at 6:07 PM, Steve Stefanovich wrote:
> Clever, but awkward in my opinion; the first place to look for such a feature
> would be under diff command. At least for me, that is.
>
> My vote is for diff --from|--to undo, wher
On Aug 29, 2015, at 2:57 PM, Lonnie Abelbeck wrote:
> Hi,
>
> Has anyone here looked into getting Fossil added as an official package with
> the Synology Diskstation ?
>
> Synology currently supplies Git and GitLab, and SVN packages, clearly Fossil
> should also be ther
Hi,
Has anyone here looked into getting Fossil added as an official package with
the Synology Diskstation ?
Synology currently supplies Git and GitLab, and SVN packages, clearly Fossil
should also be there.
There seems to an official process for this...
Synology Dev Center
https://www.synolog
On Aug 28, 2015, at 11:40 AM, Ron W wrote:
> On Thu, Aug 27, 2015 at 9:47 PM, Lonnie Abelbeck
> wrote:
> On Aug 27, 2015, at 6:27 PM, Ron W wrote:
>
> > Why "a" and not "d" (developer)? Seems to me that would cover the needed
> > permissions t
Hi Ron,
On Aug 27, 2015, at 6:27 PM, Ron W wrote:
> Since any HTTPS access to /admin/fossil/ is authenticated by lighttpd, we set
> Fossil's "nobody" permissions to "a" (admin) and add the "admin" user for "s"
> (setup) permissions.
>
> Why "a" and not "d" (developer)? Seems to me that would
Hi Warren,
On Aug 26, 2015, at 5:28 PM, Warren Young wrote:
> On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck
> wrote:
>>
>> we wondered if it could be used to track changes to these configuration
>> files in a way a non-developer type could easily understand.
>
Hi Richard and Fossil folks,
I'm Lonnie Abelbeck, a developer with the AstLinux Open Source project (
http://www.astlinux.org ) an x86 image, only 50 MB in size, geared primarily to
implement the Asterisk PBX, but we do a lot more than just a PBX.
Richard kindly requested I forward some
21 matches
Mail list logo