On Tue, 3 Jun 2014 20:06:09 +
Curtis Stiebler wrote:
> we had a power flicker
Power flicker, physical hard disk crashes, fires, shit happens every now
and then...
> We do not have a backup of the repository structure
I was once told that the 3 most important tasks for a sysadm is:
1) backu
On Wed, Jun 04, 2014 at 09:07:30AM +0200, Henrik Carlqvist wrote:
> I was once told that the 3 most important tasks for a sysadm is:
>
> 1) backup
> 2) backup
> 3) backup
>
> It really does seem as if you need a sysadm who takes his job seriously.
Wasn't step 2 supposed to be 'test restore'? :)
Classification: Public
Hi Subversion
I got an exception and just want to inform you:
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information
Hello,
> On 4 Jun 2014, at 13:20, Jonathan Naumann wrote:
>
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.4\ext\subversion\subversion\libsvn_client\commit_util.c'
>
> line 211: assertion failed (repos_root_url && repos_relpath)
Try again with the latest release.
What are you
Hi,
In our company we get code from offshore team and we have couple of developers
working here too. Every day the code from offshore will be replaced(copy the
folders and replace them) by an onsite person first at his local copy which
will show as modified in SVN.
When he tries to update befo
Thanks Andreas and Nico.
Shame that's not possible, but I welcome the global-ignores and autoprops stuff.
The purpose of the repo in question is to store 3rd party distros. I've lost
count of the times over the years that we've fallen foul of files not being
checked in and then only finding out
On Wed, Jun 4, 2014 at 9:50 AM, James French
wrote:
> Thanks Andreas and Nico.
>
> Shame that's not possible, but I welcome the global-ignores and autoprops
> stuff.
>
> The purpose of the repo in question is to store 3rd party distros. I've lost
> count of the times over the years that we've fa
On Wed, 04 Jun 2014 15:50:35 +, James French wrote:
...
> The purpose of the repo in question is to store 3rd party distros. I've lost
> count of the times over the years that we've fallen foul of files not being
> checked in and then only finding out later.
Perhaps you shouldn't build relea
Preaching backup during an uncovered recovery scenario may be fun and make you
feel smirk, but it is rarely useful for the particular problem. Your advice
jumps from generic (image and scan fs) to speculative (data recovery firms).
Would it not be better to address the specific problem?
db/curr
A little difficult to figure out from your wording exactly what you're
doing.
I would suggest that rather than sending just the code to the offshore
team, send a zip of a working copy (assuming they're on the same platform).
Offshore developers should use commands like "svn delete", "svn move", an
On Wed, Jun 4, 2014 at 10:25 AM, Deepthi Pentyala
wrote:
> Hi,
>
>
>
> In our company we get code from offshore team and we have couple of
> developers working here too. Every day the code from offshore will be
> replaced(copy the folders and replace them) by an onsite person first at
> his local
At work, when we release our software, we need to record the last time
each file in our project has changed, and compare that to the last
revision where we recorded a peer review of that file. I need to get
the last actual change to a file, ignoring renames and copies that
didn't modify the file co
On Wed, 4 Jun 2014 17:51:49 +0100
Andreas Stieger wrote:
> Preaching backup during an uncovered recovery scenario may be fun and
> make you feel smirk, but it is rarely useful for the particular problem.
As backups are only useful when taken before the disaster a backup will
not help in this cas
I just got an error from "svnadmin dump" which I have never seen before,
and it seems to be new in 1.8:
svnadmin: E160052: Revprop caching for '/scm/svn/repos/DEV-copy/db'
disabled because SHM infrastructure for revprop caching failed to
initialize.
svnadmin: E13: Can't open file
'/
Hi,
According to https://subversion.apache.org/reporting-issues.html I can only
submit a bug report if my issue has been validated on this mailing list. Is
there any more information I need to provide?
Thanks,
Nathan
From: nathan.a.clem...@hotmail.com
To: users@subversion.apache.org
Subject:
15 matches
Mail list logo