Pau Garcia i Quiles | 29 Oct 22:06 2013

FOSDEM 2014 Desktops DevRoom Call for Talks


As usual, it's time to submit your talk proposal for FOSDEM


FOSDEM is one of the largest gatherings of Free Software contributors in the world and happens each February in Brussels (Belgium). One of the tracks will be the Desktops DevRoom (formerly known as "CrossDesktop DevRoom"), which will host Desktop-related talks.

We are now inviting proposals for talks about Free/Libre/Open-source Software on the topics of Desktop development, Desktop applications and interoperability amongst Desktop Environments. This is a unique opportunity to show novel ideas and developments to a wide technical audience.

Topics accepted include, but are not limited to: Enlightenment, Gnome, KDE, Unity, XFCE/Razor, Windows, Mac OS X, general desktop matters, applications that enhance desktops and web (when related to desktop).

Talks can be very specific, such as developing mobile applications with Qt Quick; or as general as predictions for the fusion of Desktop and web in 5 years time. Topics that are of interest to the users and developers of all desktop environments are especially welcome. The FOSDEM 2013 schedule might give you some inspiration:

Please include the following information when submitting a proposal:

  • Your name
  • The title of your talk (please be descriptive, as titles will be listed with around 250 from other projects)
  • Short abstract of one or two paragraphs
  • Short bio (with photo)
  • Requested time: from 15 to 45 minutes. Normal duration is 30 minutes. Longer duration requests must be properly justified. You may be assigned LESS time than you request.

The deadline for submissions is December 14th 2013. FOSDEM will be held on the weekend of 1-2 February 2014. Please use the following website to submit your proposals:

You can also join the devroom's mailing list, which is the official communication channel for the DevRoom: (subscription page for the mailing list: )

– The Desktops DevRoom 2014 Organization Team


Pau Garcia i Quiles
(Due to my workload, I may need 10 days to answer)
Veracity-users mailing list
Anton Afanasyev | 8 Jul 05:49 2013

Veracity plugin for Powershell

Following a suggestion on the Veracity Q&A board, I'm posting this here.

Inspired by similar developments for Mercurial and Git, I've created a Powershell plugin that adds a custom shell prompt for Veracity working directories, as well as provides tab completion for various vv commands.

You can grab it here: , along with the installation instructions.
If anyone finds it useful - awesome! I don't use Veracity lately, and so have stopped development of the plugin. If someone feels up to the challenge and wants to take up any further development - thank you. Just let me know if you do.

Veracity-users mailing list
ST | 10 Apr 14:38 2013

veracity on shared hosting


is there a tutorial on how to install veracity on a regular shared

Thank you,
Ian Olsen | 25 Mar 22:11 2013

Release: Veracity 2.5

Veracity 2.5 has been released!

You can download installers and source tarballs from

The release notes can be found here:

You can browse changes and clone from the public repository at


Ian Olsen
Veracity Project Manager
ST | 26 Feb 19:06 2013

vv in debian? as fron-end?


1) is there something new with Veracity entering debian repos?
2) will it be possible to use Veracity as web site front-end the way
fossil is used on

Antonio Costa | 18 Feb 05:48 2013

Does Veracity works on OpenBSD?

Hi Guys,

Does someone try to make Veracity work on OpenBSD?

I installed cmake. But when I run make command. That error message appear:


user <at> node-000:~/veracity$ make
[  0%] Built target sqlite3
[  0%] Built target sg_hexdump
[ 10%] Built target sgtemplates
[ 11%] Building C object libraries/sghash/CMakeFiles/sghash.dir/md5.o
/home/user/veracity/src/libraries/sghash/md5.c:38:24: error: sg_defines.h: No such file or directory
/home/user/veracity/src/libraries/sghash/md5.c:39:23: error: sg_stdint.h: No such file or directory
/home/user/veracity/src/libraries/sghash/md5.c:40:31: error: sg_error_typedefs.h: No such file or directory
In file included from /home/user/veracity/src/libraries/sghash/md5.c:41:
======= eof =======

Antonio Costa ( <at> antonio_cfc)
Information Security Researcher(Unix Systems)

Veracity-users mailing list
Ian Olsen | 18 Jan 18:27 2013

WC attachments after update in 2.5

Hi Jace. (I've cc'ed the mailing list.)

We thought we picked sensible defaults, but many users were confused 
about the state of their branch attachment when updating by revision.

In 2.1 (and older):

update -b <branch>
Updates to the head of <branch> and attaches to it. Always.

update -r 10
Updates to revision 10 and always preserves your current attachment, 
even if revision 10 is the head of a different branch or not a branch 
head at all. This confused people. Often they'd inadvertently commit 
changes against the wrong branch.

In 2.5:

update -b <branch>
Updates to the head of <branch> and attaches to it. Always. (No change.)

update -r 10
If revision 10 is the head of (exactly one) branch, update to it and 
attach to its branch. If revision 10 is NOT the head of exactly one 
branch, make the user be explicit about their intentions with either 
--detached or --attach <existing-branch>, or --attach-new 

On 1/18/2013 10:25 AM, Jace Browning wrote:
> Can you explain the justification for the Veracity 2.5 change that can
> now lead to this error:
> $ vv update -r 3d7
> Error: The proper branch cannot be determined automatically; please use
> one of the attach or detached options: The
> target changeset '3d7fd7ac667de193f31455d80113a0ca26b314b0' is not a
> head; you must explicitly attach/detach the WD
> It is rather annoying that I can't easily jump back to an earlier
> version without adding more command line args...
Ian Olsen | 14 Jan 16:51 2013

Re: Veracity 2.5 Nightly Builds

Thanks for the report, Jace.

That's actually a known issue: status with a single revision given was 
JUST implemented. It's in the nightlies starting Friday night, which was 

On 1/14/2013 9:46 AM, Jace Browning wrote:
> I am getting an error attempting to view the status against an earlier tag:
> $ vv version
> (f130254375) [64-bit WINDOWS]
> $ vv status --tag 00.02.000
> Error: Not implemented.
Jeff Slutter | 11 Jan 17:34 2013

Veracity 2.5 nightly slow sync/update

I am using a Nightly from, I believe, two days ago. After installing I 
of course had to wipe and recreate my working copies. Things have been 
working okay, though I noticed things have slowed a little. However, 
today I did a sync/pull and update (via vvdialog/tortoise) and it took 
several minutes, though there was just 21 changed and 11 added. After a 
bit of waiting, I fired up my task manager and saw that vvDialog.exe was 
steadily pulling 3 M/s of IO.

I then launched ProcessMonitor to watch what it was doing and found that 
it was opening and reading a lot of files. In particular, it was reading 
my intermediate build files like .obj and .pch files, which are ignored 
in .vvignores, along with source files that are managed by Veracity.

Some of these files, like .pch are quite large, and so it had a lot of 
work to do. My working folder, with code built, is 3.02 gigs in size, 
but I have never had such a wait like that before. Some experimentation 
has repeated the issue with just 1 changed file (3 minutes 42 seconds to 
sync and update for that small text file change).

It does not always happen though. In trying to reproduce I got '1 
changed file' updates in just 20 seconds (2.1 builds took 8 seconds to 
do the similar update).

It appears that on update Veracity is going through files that are to be 
ignored. For example, if I have VS2008 open and try to update, it will 
fail saying the solution.ncb file is in use and cannot be accessed. I 
have to close my solution in VS2008 to update. .ncb files are in my 

.vvignores is working, as I do not have any files listed in my 'Add 
Files' dialog.

The format of my vvignores is like this:

 <at> /include/**
 <at> /lib/**
 <at> /bin/**

Ian Olsen | 10 Jan 00:06 2013

Veracity 2.5 Nightly Builds

The final release of Veracity 2.5 is just a few weeks away! In 2.5 we 
rewrote the working copy layer for improved performance and stability. 
We've been using it for months, and it's ready for feedback.

Nightly builds are now available, if you'd like an early look:

Please commit any changes before upgrading, as you'll have to check out 
a fresh working copy to work with 2.5.


Ian Olsen
Veracity Project Manager
Kaloyan Tenchov | 30 Dec 23:42 2012

Veracity on Raspberry Pi


I am trying to build Veracity for Raspberry Pi (armv6l).

Everything builds successfully and all but one test pass successfully. The one that fails is:


According to Testing/Temporary/LastTest.log, I get 66/1616 failures and all seem to be the same:

    TestFailed /home/pi/v/veracity/testsuite/u0078_diff.c:1078 [VERIFY_ERR_CHECK_DISCARD][VERIFY_CTX_IS_OK][_u0078__verify_merge(pCtx, pMod2, pAncestor, pMerged, pMod1)]
    Error 78 (sglib): Illegal charset character.

I am trying to figure out details but my guess is that this is somehow related to the OS setup.

I wonder whether somebody else has seen such a failure?

Also, I wonder whether Veracity is usable like this?

I used veracity-source- and followed the instructions for building under Ubuntu here

I had to remove -Werror as suggested in the comments as I was getting error like this with gcc 4.6.3:

/home/pi/v/veracity/src/libraries/ut/sg_base64.c: In function ‘base64_decode_value’:

I am using the latest Raspbian image - . Raspbian ( is based on Debian.

    $ cat /etc/issue
    Debian GNU/Linux 7.0 \n \l

Any feedback will be appreciated.

Thanks and happy holidays,

Attachment ( application/octet-stream, 3201 bytes
Veracity-users mailing list