> Maybe it should only delete these files when you say “fossil set manifest 0”?
Thanks for the info.
I also looked up where this happens in the code (manifest_to_disk() in
checkout.c
[http://fossil-scm.org/index.html/artifact?udc=1&name=30d687f7642ce389&ln=136])
One way to get around this automa
By chance, just stumbled upon a curious issue: When executing 'fossil
open' for a newly created repo, if there're any existing local files
named "manifest" and "manifest.uuid" these get deleted.
---
$ mkdir x
$ cd x
$ ls
$ fossil new ../x.fossil
$ touch manifest manifest.uuid
$ ls
manifes
> (1) Run using "fossil server"
Actually, it runs local to the PC, mainly to [self-]serve Wiki.
Now looking at 'fossil help winsrv' it seems that this would be a
better fit for such a use... Thanks :)
___
fossil-users mailing list
fossil-users@lists.
> project they are working on. Then they use TortoiseSVN to (mostly) commit
> changes to their documents, sometimes to fetch older versions. Many of the
> users are now making almost daily commits, not just just when making
> official releases of their documents.
Thank you for sharing this.
So the
> My guess is that you are probably overflowing a 32-bit integer
> someplace. If so, I fear that this will not be something easily
> fixed.
>
Looks like it's the case at least in one place.
There's int64 => unsigned int overflow at the call to blob_resize()
(blob.c:865
[http://fossil-scm.org/ind
How would you want to use such a GUI?
I mean practically what is a non-programmer user workflow that
involves a VCS interaction via GUI?
The reason I ask, is that on several occasions I tried to convince
"ordinary" users to incorporate a VCS into their daily tasks. Not just
Fossil VCS, but Git and
velopers. Please let me
know of your experinces and ideas. If this makes sense, I may try to
write up some Fossil wiki page with detailed instructions on how to
set up the Fossil project development in IDE.
Artur Shepilko
___
fossil-users mailing list
fossil
> openBSD -current x64
> $ cc -v
> OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0)
> Target: amd64-unknown-openbsd6.3
> Thread model: posix
> InstalledDir: /usr/bin
>
Ok, I think I found the problem. This info was very helpful.
Indeed, the *BSD platforms have all the dl
I made the recent change that moves the -ldl to the end of the link
library list (http://fossil-scm.org/index.html/info/efbc319c32a38fab).
However its effect should be rather trivial, just moving the -ldl to
the end of the library list. Such check was there before, just the
-ldl would be inserted a
> Your suggestions for useful features found in GitHub but missing from
> Fossil, or for pages in GitHub that work especially well and that you
> would like to see replicated in Fossil, are greatly appreciated.
I think the answers depend on specifics of project workflow.
GitHub is a social platfor
> I have used fossil on WinXP for quite sometime now and have many separate
> fossils project wise. Now, I have switched my os to Linux Mint. Fossil is
> able to open the existing fossils created under windows, but I am unable to
> make any changes to them.
Not clear what is your set up and step
>
> But in my experience, fossil revert is a rarely used command.
>
Both `fossil revert afile -r ver` and `fossil update ver afile` seem
to be a synonymous way to fetch a file's revision. HOWEVER, there's an
important distinction, `fossil update` would __merge-in uncommitted
changes__ with the req
Not sure about the objectives the students are learning in this
course, but if it in any way relates to programming, recognizing as
to what to keep under version control is a reasonable objective on its
own. There could be valid reasons to keeping executables and other
build artifacts versioned, b
> I would like to understand these terms, how to interpret the timeline graph,
> and how to do commits against specific versions.
Fossil book is very concise and practical way to learn the basic usage:
http://www.fossil-scm.org/schimpf-book/doc/2ndEdition/fossilbook.pdf
Chapter 4 is about branche
You may try to add a comma to the the asterisk "*,"
fossil set crnl-glob *,
This used to work properly with cmd.exe, so it won't expand the * to a
file-name.
The crnl-glob Fossil setting allows a comma-separated list of glob patterns.
"*," is effectively such list that also includes an empty pa
Just tried the case of "file name contains a newline char" with git.
Looks like git encodes such names with C-like characters ('\n' for x0A
or '\r' for x0D).
Git fast-export outputs such files enquoted as follows:
M 100644 :1 "newline\nfile.txt"
For the same case, fossil export does not encode th
Amazing!
Speaking of Jenkins: someone just recently mentioned an existing
(dusted though) Fossil plugin for Jenkins. May just be worth a try for
your case.
Jenkins would automate interactions with Fossil repo, with all
benefits of a CI/build server.
http://www.mail-archive.com/fossil-users@lists.f
To summarize the findings:
- Sqlite Fossil repo has a number of special cases that do not export
directly, resulting in "git fast-import" crash.
- To accomplish the export, one needs to apply the following fixes to
the __local__ clone of the Sqlite Fossil repo:
fossil set autosync off
fossil repa
Richard, Thank you for the details.
I just realized that the check-in date may be altered via "fossil
amend --date" or from UI via check-in's edit submenu.
This will add the tag "date=" and update the check-ins MTIME.
Looks like both timeline and export indeed pick up the updated MTIME.
I looke
.
If date tag is indeed a way to tune the timeline, perhaps this should
be factored in both the timeline output and the selection of export
recordset.
On Thu, Feb 16, 2017 at 4:54 PM, Artur Shepilko wrote:
> Indeed, in export.c the commits are lined up chronologically.
>
> There'
Indeed, in export.c the commits are lined up chronologically.
There's a way to try to catch such inconsistencies by tracking when
the "from :mark" gets freshly incremented (that is the parent has not
been exported yet):
src/export.c::~581
int next_mark = unused_mark;
zMark = mark_name_
Looking closer at the timeline and manifests shows that the
inconsistency is with
https://www.sqlite.org/src/info/590d4ac1ee0db824
which lists as its parent a tag's manifest
(https://www.sqlite.org/src/info/f228c7ca0682c370).
Normally the link should be to tag's target object, which in this case
is
> commit refs/heads/shunning_error
> mark :56263
> committer drh 1257360677 +
> data 24
> * from :56264
This is a curious case: looks like the branch:"shunning_error" starts
off a tag (https://www.sqlite.org/src/info/f228c7ca0682c370f8c43)
That is its parent is a commit edit/amend eve
> --rename-master renames master
> --rename-trunk renames trunk
> We should strive to keep the command line UI sane.
In my opinion, preserving the long-standing default import target
branch as "trunk" is reasonable, whether we change the semantics of
"--rename-trunk" option or not.
The notion of
> * no more silent renaming of master vs trunk [1]
"fossil import --rename-trunk" already allows a choice for a Fossil
branch name to receive Git's "master" branch.
A bug was missed in src/import.c:~567 if( fossil_strcmp(z,
"master")==0 ) z = "trunk";
In src/import.c this option is stored in g
> So, if everything goes according to plan, I think I could do this
> indefinitely without ever needing to push, pull or sync to a Master
> Repository ? Is this valid and reasonable, or am I missing something
> important here ? Artur Shepilko suggested having Master Repositories on
This sounds familiar, a "pocket-sync" protocol or "virus-taxi" :)
Needs a robust anti-virus for protection.
If I understood it correctly, your main criteria are:
1) One flash drive -- use of flash drive to keep all "master" project
repos on it
2) Many PCs -- work on any project at many field-PC's
Your email subject is somewhat misleading, and it's not April 1 yet in
this part of the universe :)
As you expained it yourself, it's rather "Fossil crashes on opening an
invalid repository file (PDF)"
As for the issue:
This is not really about PDF, just about an invalid non-fossil
repository. It
Attached the test script.
The mailing list seems to have redacted the email addresses used in
the test, which makes the test fail.
On Thu, Jan 5, 2017 at 10:52 PM, Artur Shepilko wrote:
> Saw your message and recalled that I stumbled on the same issue some
> years back. Indeed fossil trum
Saw your message and recalled that I stumbled on the same issue some
years back. Indeed fossil trumps git, so nobody looks back :)
In case you wonder, the reason you saw the email and name getting
swapped is because the email was expected to be in form ,
mind the <>.
I just checked-in the fix
(ht
Just happened to download v1.36 Linux binary off Fossil page to a
Linux x86-32bit box and surprisingly it would not execute
http://fossil-scm.org/index.html/uv/download/fossil-linux-x86-1.36.tar.gz
Turns out it's actually a 64bit binary:
file ./fossil
./fossil: ELF 64-bit LSB exec
src/sqlite3.c:80663
--
if( pOp->p1==1 ){
/* Invalidate all prepared statements whenever the TEMP database
** schema is changed. Ticket #1644 */
sqlite3ExpirePreparedStatements(db);
p->expired = 0;
}
--
SQLITE_PRIVATE void sqlite3ExpirePreparedStatements
Ok, the fix is in:
https://fossil-scm.org/index.html/info/476fe9e932f01133
On Mon, Oct 31, 2016 at 12:42 PM, Artur Shepilko wrote:
> Ok, just dropped the CLA in the mail.
> Sure USPS has an important role in the Fossil project, it probably has
> its own username in the repo too :
be a big deal for step-tracing the execution
in the debugger, but it does conseal code introduced by the
pre-processors.
Thus for debugging purposes the #line directive could be omitted, at
least for MS VisualStudio compiler, so that one could follow the
actually compiled source-code.
On Sat, Oct 29, 20
1.37 release.
And, yes, the issue was spotted from the qtcreator-plugin-fossil, just
now its Windows version got somewhat more attention.
Thanks.
On Mon, Oct 31, 2016 at 5:24 AM, Richard Hipp wrote:
> On 10/31/16, Artur Shepilko wrote:
>> I would've
>> gladly fixed it
This issue seems to be similar to what has been found with 'fossil cat',
and subsequently fixed:
http://www.fossil-scm.org/index.html/info/f2fc37c063af9fae
In brief, when the source-code contains CR/LF line-endings, 'fossil diff'
in non-console output (when run non-interactively) on Windows shows
BTW, in general you may use VisualStudio debugger directly without a
solution, by manually starting the 'devenv' as:
devenv /debugexe fossil.exe
This launches VisualStudio in Debug mode and allows you to 'Step Into' a
new instance of the exe (fossil.exe). By default it breaks in main().
To
dn't manage it as a fossil repository? :)
> Il'll try this asap. I'm using qtcreator for a couple of projects at
> job... (currently with git). I need to find some time to download/compile
> qtcreator sources
> Thanks
> Aldo
>
>
> On 27/10/2016 00:08, Artur She
should also be made available
in the plugin, but that's later.
Hope this clears it.
On Sat, Oct 8, 2016 at 2:10 PM, Artur Shepilko wrote:
> We finally got to release Fossil plugin for QtCreator:
> https://github.com/nomadbyte/qtcreator-plugin-fossil
>
> The Fossil plugin is fre
what has changed from one "state"
vs. another by listing the diffs of such a "meta-project".
Makes sense?
On Sun, Oct 23, 2016 at 5:13 PM, Scott Doctor wrote:
>
> On 10/23/2016 13:59, Artur Shepilko wrote:
>
>> It's not clear what type of project the
It's not clear what type of project the OP is trying to setup, whether it's
a programming-related project, or general document-repo type.
>From personal experience, I once was facing the same question to assess
Fossil "general" viability. For this almost abstract task, Jim Schimpf's
pdf book [http
We finally got to release Fossil plugin for QtCreator:
https://github.com/nomadbyte/qtcreator-plugin-fossil
The Fossil plugin is free and open-source, of course. The README describes
how to build it. The most recent QtCreator version we used it with is
QtCreator-4.0.1, which is included in Qt 5.6.
42 matches
Mail list logo