From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Issues while updating fossil to 2.1
Date: Wed, 12 Apr 2017 16:15:58 +0000 [thread overview]
Message-ID: <20170412161558.eihlgkz723n7crcl@abyayala> (raw)
In-Reply-To: <20170412153915.GE5920@jasmine>
Leo Famulari transcribed 0.8K bytes:
> On Tue, Apr 11, 2017 at 10:32:31AM +0000, ng0 wrote:
> > ng0 transcribed 4.7K bytes:
> > > Hi,
> > >
> > > my editor wraps at 80 lines but I hope the errors are obvious for
> > > someone who did fix fossil before (Efraim?).
> > > Could it be that not all tests have been updated for the new format?
> >
> > Looking at their timeline
> > (https://www.fossil-scm.org/index.html/timeline?y=ci), commits like
> > https://www.fossil-scm.org/index.html/info/6167f69a218804bd
> > suggest that there are issues. However I guess we can use nothing after
> > https://www.fossil-scm.org/index.html/timeline?c=303a2084a35beec1&unhide
> > where they updated sqlite to 3.18 beta and later they updated to 3.18
> > (released?).
>
> Has fossil made a release that depends on sqlite 3.18? I think we will
> offer this version of sqlite before most distros, but not immediately;
> it was released only 2 weeks ago.
>
https://fossil-scm.org is always running the HEAD of fossil, and because
they are very closely connected to sqlite I think that's the reason why
the implement use of new versions as soon as possible. No release has
been published, but commits are already made with 3.18.
--
PGP and more: https://people.pragmatique.xyz/ng0/
prev parent reply other threads:[~2017-04-12 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 10:25 Issues while updating fossil to 2.1 ng0
2017-04-11 10:32 ` ng0
2017-04-11 10:44 ` ng0
2017-04-12 15:37 ` Leo Famulari
2017-04-12 15:39 ` Leo Famulari
2017-04-12 16:15 ` ng0 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170412161558.eihlgkz723n7crcl@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).