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
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
On Sep 26, 2017, at 9:01 AM, Warren Young <war...@etr-usa.com> wrote:
> On Sep 26, 2017, at 7:10 AM, Lonnie Abelbeck <li...@lonnie.abelbeck.com>
> wrote:
>>
>> sqlite3 /mnt/kd/fossil/astlinux.fossil .dump >
>> "$CUSTOM_BACKUP_DIR/astlinux.fossil.dum
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
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
>
On Mar 5, 2017, at 10:15 AM, Richard Hipp <d...@sqlite.org> wrote:
> On 3/5/17, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote:
>> For what is planned for Fossil 2.1, will new repos created using 2.1 using:
>> --
>> fossil init --sha1 repo.fossil
>> --
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.
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 <li...@lonnie.abelbeck.com> wrote:
> I recently upgraded fossil to 1.37 for our project (cross-compiled from
> source).
>
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
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
On Jul 1, 2016, at 3:42 PM, Ross Berteig <r...@cheshireeng.com> 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.
&g
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
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
On Aug 29, 2015, at 2:57 PM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> 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, clear
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
On Aug 28, 2015, at 11:40 AM, Ron W ronw.m...@gmail.com wrote:
On Thu, Aug 27, 2015 at 9:47 PM, Lonnie Abelbeck li...@lonnie.abelbeck.com
wrote:
On Aug 27, 2015, at 6:27 PM, Ron W ronw.m...@gmail.com wrote:
Why a and not d (developer)? Seems to me that would cover the needed
Hi Ron,
On Aug 27, 2015, at 6:27 PM, Ron W ronw.m...@gmail.com 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
Hi Warren,
On Aug 26, 2015, at 5:28 PM, Warren Young w...@etr-usa.com wrote:
On Aug 26, 2015, at 2:12 PM, Lonnie Abelbeck li...@lonnie.abelbeck.com
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
19 matches
Mail list logo