<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user">
    <title>gmane.comp.version-control.subversion.user</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110292"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110291"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110290"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110289"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110288"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110287"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110286"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110285"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110284"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110283"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110282"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110281"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110280"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110279"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110278"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110277"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110276"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110275"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110274"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110273"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110292">
    <title>Constraint Failed on update to externals</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110292</link>
    <description>&lt;pre&gt;Hi,

I found a reference to someone having this problem in 2011, but there
doesn't appear to have been any response or fix. Sorry if this is a repost
or is already being investigated.

I have a path within a Subversion 1.4.4 server (with a 1.7.7 client) which
has an external:

http://svn.mycompany.co.uk/
  |--&amp;gt; /my-repo/src
        |--&amp;gt; build-resources [ points to
http://svn.mycompany.co.uk/my-repo/build-resources ]

I'm moving the external to a different location:
https://othersvn.mycompany.co.uk/new-repo/build-resources

However, after I commit this, anyone who updates the directory gets the
following error:

External failed: my-repo\src\external
Error: sqlite: constraint failed
Error: sqlite: EXTERNALS.def_repos_relpath may not be NULL

The external is updated correctly and the local copy seems to be OK, so
this error is not a blocker. However, I'd prefer not to get the error in
the first place, particularly as I update externals fairly often.

This doesn't happen if the external is on the same repository&lt;/pre&gt;</description>
    <dc:creator>Steven Newson</dc:creator>
    <dc:date>2012-05-22T15:53:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110291">
    <title>Re: Can't execute svn commands through the network</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110291</link>
    <description>&lt;pre&gt;

It's something to do with locking:

open("/usr/home/michael/mount/pw-websites/PW-Websites/baumarkt.de/Website-online
/.svn/wc.db",O_RDWR|0x100000,00) = 3 (0x3)

[...]

fcntl(3,F_SETLK,0x7fffffffbaf0)                  = 0 (0x0)
fcntl(3,F_SETLK,0x7fffffffc2a0)                  = 0 (0x0)
fcntl(3,F_SETLK,0x7fffffffc2a0)                  ERR#11 'Resource deadlock avoid
ed'
fcntl(3,F_SETLK,0x7fffffffc2a0)                  = 0 (0x0)
write(2,"svn: E200030: sqlite: disk I/O e"...,37) = 37 (0x25)
write(2,"svn: E200030: sqlite: disk I/O e"...,37) = 37 (0x25)


I suspect that sqlite is attempting byte range locking and your server
doesn't support it.  I don't know what to do about that.

&lt;/pre&gt;</description>
    <dc:creator>Philip Martin</dc:creator>
    <dc:date>2012-05-22T15:09:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110290">
    <title>Re: Can't execute svn commands through the network</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110290</link>
    <description>&lt;pre&gt;
It seems odd in general to use samba between unix-type machines
instead of nfs - or just using ssh, remote X, or freenx to log into
the machine that has the disk space.  Can you use nfs instead (you can
still share the same space with samba if there are also windows
clients) ?



Linux has a cifs mount option that preserves more of the unix
semantics than smb, but I don't know if that exists in freebsd.

&lt;/pre&gt;</description>
    <dc:creator>Les Mikesell</dc:creator>
    <dc:date>2012-05-22T12:47:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110289">
    <title>Re: Reintegrate merging with sparse checkouts</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110289</link>
    <description>&lt;pre&gt;[ ... ]

Ah ok, I see. It fails with:

svn: E195016: Reintegrate can only be used if revisions 2 through 6
were previously merged from file:///C:/Temp/svn-test
/repos/trunk to the reintegrate source, but this is not the case:
  branches/feature/A
    Missing ranges: /trunk/A:4

where revision 4 is the revision on trunk which affected A\B, which
was missing (excluded by sparseness) from the branch-wc which you used
to do the sync merge.

I believe that this is normal behavior then, with the current
functionality of svn: revision 4 is indeed not synced, and the branch
must be synced completely (there must not be any gaps) for it to be
reintegratable.

OTOH, you could argue that --reintegrate should just work in this
case, similar to the normal sync merge, by only looking at the parts
that are present in the working copy (and using non-inheritable
mergeinfo to mark the parts where the (reintegrate) merge was not
performed in full). Hmmm, otherwise you'd almost always need full
working copies to perform the merg&lt;/pre&gt;</description>
    <dc:creator>Johan Corveleyn</dc:creator>
    <dc:date>2012-05-22T12:31:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110288">
    <title>Re: Can't execute svn commands through the network</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110288</link>
    <description>&lt;pre&gt;
This is correct.


No I don't. strace is only for i386 while I'm running amd64. DTrace
isn't also an option for me, because I would need to rebuild my kernel.
But I'm just a beginner, so I don't think this would end well :)
I tried truss, but I can't do anything with the results. Maybe
they are interesting for you?

http://www.file-upload.net/download-4381573/truss.log.html


Unfortunately mount_smbfs doesn't support the nobrl option.

&lt;/pre&gt;</description>
    <dc:creator>Michael Fausten</dc:creator>
    <dc:date>2012-05-22T12:28:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110287">
    <title>Re: AW: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110287</link>
    <description>&lt;pre&gt;[...]
[...]

Ted,

Please have a look at the (commmercial) CI tool TeamCity.

It is able to do so-called "pre-checked commits", which might help with
your objective, i.e. keeping bad commits out of the codeline.

http://en.wikipedia.org/wiki/TeamCity
http://www.jetbrains.com/teamcity/features/index.html

&lt;/pre&gt;</description>
    <dc:creator>Michael Diers</dc:creator>
    <dc:date>2012-05-22T12:08:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110286">
    <title>AW: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110286</link>
    <description>&lt;pre&gt;Hi, Ted,

Just as an addition:

Von: Les Mikesell [mailto:lesmikesell&amp;lt; at &amp;gt;gmail.com]

At my current employer, we successfully use Jenkins. 

But there are other such systems, for example the java-based http://cruisecontrol.sourceforge.net/ and its .NET cousing http://www.cruisecontrolnet.org/ - both of them were used at one of my former employers place. At another former employers place, we used post-commit hooks triggering a self-written python daemon which ran appropriate scons build files. And AFAIR, Microsoft also provides some auto-build solution for VSS or TFS.

http://en.wikipedia.org/wiki/Continuous_integration#Software contains a list of CI software.

So even if you don't like Hudson or Jenkins for whatever reason, there are lots of alternatives, and I strongly suggest you evaluate continuous integration in your environment.

Best regards

Markus Schaber
&lt;/pre&gt;</description>
    <dc:creator>Markus Schaber</dc:creator>
    <dc:date>2012-05-22T06:21:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110285">
    <title>Re: not suer</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110285</link>
    <description>&lt;pre&gt;Guten Tag Jamie Addison,
am Dienstag, 22. Mai 2012 um 00:47 schrieben Sie:


Try to use it and see if it works? Your question is really hard t
answer because there is no "the application", you can have various
different clients which may even work differently. One can have
command line clients which normally can be executed using svn
--version, TortoiseSVN which is a Windows Explorer integration, you
may just have installed a server only package without any client,
depending on your OS and installation method of whatever you use the
executables may not be in the path etc.

You really should be more descriptive, at least about what you did
that you think you have installed the application without being sure.

Mit freundlichen Grüßen,

Thorsten Schöning

&lt;/pre&gt;</description>
    <dc:creator>Thorsten Schöning</dc:creator>
    <dc:date>2012-05-22T06:08:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110284">
    <title>RE: not suer</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110284</link>
    <description>&lt;pre&gt;You don't want to give much information, do you?

Whatever, try running the command `svn` and see if you get an error or not.  If you told us at least what operating system you use we might be able to help more...

~ mark c

&lt;/pre&gt;</description>
    <dc:creator>Cooke, Mark</dc:creator>
    <dc:date>2012-05-22T06:07:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110283">
    <title>not suer</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110283</link>
    <description>&lt;pre&gt;hi im not sure if i have the applicaTION or not how can i tell
&lt;/pre&gt;</description>
    <dc:creator>Jamie Addison</dc:creator>
    <dc:date>2012-05-21T22:47:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110282">
    <title>line 94: assertion failed</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110282</link>
    <description>&lt;pre&gt;
I just installed the Windows 7, 64-bit version of Subversion into my brand
new Windows7 box.  After installation, I tried to do a GET from our
database, and it gave me the error below.
- I saw a similar error for version 1.7.1 in your database:
(http://svn.haxx.se/users/archive-2011-11/0510.shtml).


---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
 'D:\Development\SVN\Releases\TortoiseSVN-1.7.6\ext\subversion\subversion
\libsvn_client\checkout.c'
 line 94: assertion failed (svn_ur&lt;/pre&gt;</description>
    <dc:creator>Eleazar O Vita</dc:creator>
    <dc:date>2012-05-21T21:56:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110281">
    <title>Re: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110281</link>
    <description>&lt;pre&gt;
I use Centos with yum and the rpm-packaged version and it updates via
the system yum mechanism like everything else.  I assume the ubuntu
package works the same way with apt-get/synaptic or whatever the
system uses.   It is a lot easier to administer everything in one
place instead of having to update every application separately.

&lt;/pre&gt;</description>
    <dc:creator>Les Mikesell</dc:creator>
    <dc:date>2012-05-22T00:04:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110280">
    <title>Re: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110280</link>
    <description>&lt;pre&gt;
Do you mean apt-get updates or Jenkin's self-provided update mechanism? 
  If the later, is that recommended when it is installed via apt-get? 
I've always installed Jenkins by hand.

Blair



&lt;/pre&gt;</description>
    <dc:creator>Blair Zajac</dc:creator>
    <dc:date>2012-05-21T23:52:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110279">
    <title>Re: Subversion 1.7.5 released</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110279</link>
    <description>&lt;pre&gt;It passes my compile and basic behavior checks for RPM compilation, and I'll push the hooks to build it for RHEL ASAP.

On May 17, 2012, at 7:50, Philip Martin &amp;lt;codematters&amp;lt; at &amp;gt;ntlworld.com&amp;gt; wrote:


&lt;/pre&gt;</description>
    <dc:creator>Nico Kadel-Garcia</dc:creator>
    <dc:date>2012-05-21T22:22:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110278">
    <title>Re: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110278</link>
    <description>&lt;pre&gt;
Since he mentioned ubuntu earlier, it is probably even easier to go
with the packaged version:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu
after which the system will know how to pick up updates.

&lt;/pre&gt;</description>
    <dc:creator>Les Mikesell</dc:creator>
    <dc:date>2012-05-21T22:11:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110277">
    <title>Re: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110277</link>
    <description>&lt;pre&gt;

Jenkins is a Continuous Integration system. Continuous Integration
means every time sone one changes the code, you automatically build
the changes. This at least proves that the changes "don't break the
build". More sophisticated analysis can be done too. For example,
running unit tests, checking code for possible bugs, running coverage
tests, checking the code syntax.

This is something that's really quite common in the Java environment
where builds take but a few minutes. It's not as common in the C/C++
world where builds can take hours, but it's beginning to get there.

Jenkins is pretty simple on the surface to setup. Simply download the
Jenkins "war" file, install a Java JDK if you don't have one
installed, and run the following command:

$ java -jar jenkins.war

Then, go to http://localhost:8080 in your browser and see what's
there. Jenkins is pretty simple. If you are somewhat technical, you
should be able to set up a job in a matter of minutes. Just go ahead
and give it a try. There are dozens, if &lt;/pre&gt;</description>
    <dc:creator>David Weintraub</dc:creator>
    <dc:date>2012-05-21T21:56:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110276">
    <title>Re: Reintegrate merging with sparse checkouts</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110276</link>
    <description>&lt;pre&gt;
Sorry about that... see below.


I was able to reproduce the issue, please see the attached
sparse-merge.txt and I captured the output and error that I see in the
attached file out.txt. (Note that I had to rename sparse-merge.bat to
sparse-merge.txt before Gmail would send it).

I am using SVN 1.7.4 on Windows XP.

The high level description of what is going on in the script is:

1. Create a repo using your sample greek tree.
2. Make a sparse working copy of trunk, omitting the A\B directory (trunk_wc)
3. Copy trunk to a feature branch.
4. Make a sparse working copy of the feature branch (omitting A\B -- branch_wc)
5. Make a full working copy of trunk (trunk_b_wc).
6. Now change files in all three working copies and commit (but don't
create conflicts). In particular, in trunk_b_wc, change a file under
A\B.
7. Merge trunk to the feature branch.
8. Reintegrate merge the feature branch back to trunk.
9. Observe that the merge fails, presumably because the changes to A\B
never made it to the feature branch.

Th&lt;/pre&gt;</description>
    <dc:creator>Brian Neal</dc:creator>
    <dc:date>2012-05-21T19:00:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110275">
    <title>Re: svnadmin verify produces "file not found"</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110275</link>
    <description>&lt;pre&gt;Stefan Witzel wrote on Mon, May 21, 2012 at 12:09:46 +0200:

You should set LC_ALL=C in your environment to get these errors in
English for the list.


Note that this most likely means that a revision _later_ than r672 was
corrupted.  You can determine which from the "* Verified revision N."
outputs of svnadmin.


Create an svnsync copy while accessing the corrupted repository through
svn:// or http:// with authz set to deny read access to the offending
file.

Cheers,

Daniel

&lt;/pre&gt;</description>
    <dc:creator>Daniel Shahaf</dc:creator>
    <dc:date>2012-05-21T15:16:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110274">
    <title>Re: Reintegrate merging with sparse checkouts</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110274</link>
    <description>&lt;pre&gt;[ Redirecting back to the list -- please always use "reply all" to
keep the discussion on the list. More below ... ]

On Mon, May 21, 2012 at 3:54 PM, Brian Neal &amp;lt;bgneal&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

Yes, that would be very useful.

I don't have any more ideas at this time (I have no experience with
(reintegrate-)merging combined with sparse working copies, I just
remembered the issues from the issue tracker).

Maybe someone else on the list has experience with that ...

&lt;/pre&gt;</description>
    <dc:creator>Johan Corveleyn</dc:creator>
    <dc:date>2012-05-21T14:01:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110273">
    <title>Re: bug report: svn client 1.7.x silently fails to fetch files via svn:externals under certain conditions.</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110273</link>
    <description>&lt;pre&gt;
Hi Johan and thank you for prompt reply.  Nevertheless I don't agree 
with your reasoning.
Let me give my point of view on this.

I believe that svn:externals feature, when used with operative revision 
(not peg revision, this is important!)
should work the same way as other svn commands, such as for example 
'cat' or 'co'.
In other words, when operative revision is used in svn:externals, it 
should cross copy command boundary.

Getting back to my example, here is the question. Why then, if I, for 
example, run:

svn cat -r 1 file:///`pwd`/repos/A/tags/1.0/file.txt


or

svn co -r 1 file:///`pwd`/repos/A/tags/1.0  tags-checkout


subversion happily prints file.txt contents or downloads it to a working 
copy.
This happens because it is able to cross copy command boundary.  BTW, 
this works fine both in 1.6.x and 1.7.x.
And this is the behavior, which is described in the Red Book "The Peg 
Revision Algorithm" section.
Namely, it says:

--------------------------------------------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Alex Siyanko</dc:creator>
    <dc:date>2012-05-21T12:41:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110272">
    <title>Re: New to subversion, need to find documentation on writing hooks</title>
    <link>http://permalink.gmane.org/gmane.comp.version-control.subversion.user/110272</link>
    <description>&lt;pre&gt;
Conceptually it is a framework where you write simple jobs that are
scheduled or run when you commit something new to your version control
system.  The typical use is to build the trunk version on every
change, run the tests, and email the group if anything is broken, but
a job can do anything you want and there are many plugin extensions.
A master system does the scheduling and collates the results but the
work can be distributed over many slave machines and across target
platforms.

&lt;/pre&gt;</description>
    <dc:creator>Les Mikesell</dc:creator>
    <dc:date>2012-05-21T12:40:59</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.version-control.subversion.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.version-control.subversion.user</link>
  </textinput>
</rdf:RDF>

