On Dec 4, 2013, at 7:54 PM, Adam Daughterson
wrote:
> The really interesting part is that the db file is only 119k, so that's nice
> and weird...
>
> me@here:myThing$ ls -alh .svn
> total 144K
> drwxr-xr-x 4 adaughterson adaughterson 4.0K 2013-12-02 15:42 .
> drwxr-xr-x 9 adaughterson adaug
After many hours of apparently pointless googling, I hope to get an
answer here.
I asked a question on unix.stackexchange.com which essentially outlines
my problem:
http://unix.stackexchange.com/questions/103714/svn-failing-to-create-sasl-context
Here is the text of that question:
-
Prior to upgrading to WanDisco's 1.7.14 client, I was able to operate on
working copies which physically live on Windows shares. After the upgrade, I
get the following error when trying to do a fresh checkout:
me@here:tmp$ svn co http://myThing/trunk myThing
svn: E200030: sqlite[S22]: large fil
On Wed, Dec 4, 2013 at 7:09 PM, Pat Haley wrote:
>
>> One thing that didn't stand out in my original Email was the reason
> for the reboot. We turned quotas on. Would svn react poorly
> to this?
Only on a write that exceeds quota.
> It is a generic linux box. However doing dmesg before and
>
On 12/4/2013 5:20 PM, Pat Haley wrote:
You can cause strace to write to a file with "-o myoutputfile"
So if you want to post I'd do:
strace -o myoutputfile -s 0 svnadmin verify
/home/phaley/Papers/2011/ArpitVel/SvnPaper
That line is complaining about a stale file handle:
fcntl(3, F_SETLK, {
On Wednesday, December 4, 2013 3:05:37 PM UTC-7, Ben Reser wrote:
>
> On 12/4/13 12:59 PM, Adam Daughterson wrote:
> > Prior to upgrading to WanDisco svn client 1.7.x I was able to operate on
> > working copies which physically live on Windows shares. After the
> upgrade, I
> > get the followi
Hi Ben,
On 12/4/13 12:52 PM, Pat Haley wrote:
-
(trying local access)
-
mseas(PaperWork)% svn update
svn: Unable to open an ra_local session to URL
svn: Unable to open repository
'file:///home/phaley/Papers/2011/ArpitVel/SvnPaper'
svn: disk I/O error
s
Hi Les,
On Wed, Dec 4, 2013 at 4:31 PM, Pat Haley wrote:
How about 'svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper'?
No, that also fails
mseas(MeanAvg)% svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper
svnadmin: disk I/O error
svnadmin: disk I/O error
So, I'm guessi
On 12/4/13 12:52 PM, Pat Haley wrote:
> -
> (trying local access)
> -
>
> mseas(PaperWork)% svn update
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository
> 'file:///home/phaley/Papers/2011/ArpitVel/SvnPaper'
> svn: disk I/O er
On Wed, Dec 4, 2013 at 4:31 PM, Pat Haley wrote:
>
>> How about 'svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper'?
>
>
> No, that also fails
>
> mseas(MeanAvg)% svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper
> svnadmin: disk I/O error
> svnadmin: disk I/O error
So, I'm gues
Hi Les,
On Wed, Dec 4, 2013 at 4:06 PM, Pat Haley wrote:
svn: Unable to open repository
'file:///home/phaley/Papers/2011/ArpitVel/SvnPaper'
svn: disk I/O error
svn: disk I/O error
Sorry that I forgot to mention it in my original Email,
but yes I can look in the directory, and I seem to
see
On Wed, Dec 4, 2013 at 4:05 PM, Ben Reser wrote:
> On 12/4/13 12:59 PM, Adam Daughterson wrote:
>> Prior to upgrading to WanDisco svn client 1.7.x I was able to operate on
>> working copies which physically live on Windows shares. After the upgrade, I
>> get the following error when trying to do
On Wed, Dec 4, 2013 at 4:06 PM, Pat Haley wrote:
>
>>> svn: Unable to open repository
>>> 'file:///home/phaley/Papers/2011/ArpitVel/SvnPaper'
>>> svn: disk I/O error
>>> svn: disk I/O error
> Sorry that I forgot to mention it in my original Email,
> but yes I can look in the directory, and I seem
Hi Henrik,
Last week we rebooted the NAS server which hosts the disk where
(among other things) our svn repositories reside, in order
to enable quotas on that disk. Since that time, we have been
unable to work with these repositories. We see the following
error messages
-
On 12/4/13 12:59 PM, Adam Daughterson wrote:
> Prior to upgrading to WanDisco svn client 1.7.x I was able to operate on
> working copies which physically live on Windows shares. After the upgrade, I
> get the following error when trying to do a fresh checkout:
>
> me@here:tmp$ svn co http://myThi
> Last week we rebooted the NAS server which hosts the disk where
> (among other things) our svn repositories reside, in order
> to enable quotas on that disk. Since that time, we have been
> unable to work with these repositories. We see the following
> error messages
>
> -
Thanks for your quick reply!
> Log on ^/ shows all revisions; adding -g includes no more revisions.
Yep, that is the problem. IMHO the flag -g should also give output which
shows merge information, not only on deeper levels but also on the root
level of the repository. I can understand if most pe
Hi,
I am not currently a member of this list, so please
cc me on any replies to this message. Thanks.
We are using svn version 1.6.11 in a linux cluster running
CentOS 6.2. We have been using svn for several years. Last
week we rebooted the NAS server which hosts the disk where
(among other
Prior to upgrading to WanDisco svn client 1.7.x I was able to operate on
working copies which physically live on Windows shares. After the upgrade,
I get the following error when trying to do a fresh checkout:
me@here:tmp$ svn co http://myThing/trunk myThing
*svn: E200030: sqlite[S22]: large fi
Henrik Carlqvist writes:
> On Wed, 25 Jul 2012 11:17:55 -0500
> Justin Johnson wrote:
>
>> The command "svn log -vg" is not returning merge info when I execute
>> the command while sitting in a working copy of the root level of a
>> repository or when I pass in the URL to the root level of root
On Wed, 25 Jul 2012 11:17:55 -0500
Justin Johnson wrote:
> The command "svn log -vg" is not returning merge info when I execute
> the command while sitting in a working copy of the root level of a
> repository or when I pass in the URL to the root level of root level
> on the command line. A sim
Ryan Schmidt wrote on Wed, Dec 04, 2013 at 10:06:02 -0600:
> `svnversion` recursively scans the working copy. `svn info` operates
> on the current directory only.
In case it's not clear: 'svn info' operates on the current directory
*node* only; it's like "stat ./", not like "ls ./".
That is, if .
Ryan Schmidt wrote on Wed, Dec 04, 2013 at 06:14:33 -0600:
>
> On Dec 4, 2013, at 06:00, Cooke, Mark wrote:
>
> > I would like to include the svn revision number in my project's version
> > info but I am confused by the results of svnversion. I want the version
> > number of a tagged tree to a
Remember to Reply All so the discussion stays on the mailing list.
On Dec 4, 2013, at 07:52, Cooke, Mark wrote:
>> -Original Message-
>> From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com]
>> Sent: 04 December 2013 12:15
>>
>> On Dec 4, 2013, at 06:00, Cooke, Mark wrote:
>>
>>>
> Hi Folks,
>
> I would like to include the svn revision number in my project's version info
> but I am confused by the results of svnversion. I want the version number of
> a tagged tree to always be the same (i.e. the last commit to the tag) but if
> the
> tag is to be rebuilt using a fresh ch
On Dec 4, 2013, at 06:00, Cooke, Mark wrote:
> I would like to include the svn revision number in my project's version info
> but I am confused by the results of svnversion. I want the version number of
> a tagged tree to always be the same (i.e. the last commit to the tag) but if
> the tag i
Hi Folks,
I would like to include the svn revision number in my project's version info
but I am confused by the results of svnversion. I want the version number of a
tagged tree to always be the same (i.e. the last commit to the tag) but if the
tag is to be rebuilt using a fresh checkout some
28 matches
Mail list logo
