Guten Tag PR,
am Sonntag, 6. November 2011 um 20:45 schrieben Sie:
> A/ should I upgrade server first to 1.7.1 and leave the clients at
> 1.4.6 initially and then the clients .. upgraded to 1.7.1 slowly ?
> B/ or migrate the clients first to 1.7.1 slowly leaving the server at
> 1.4.6 and then upg
On Sun, Nov 06, 2011 at 06:49:07PM -0500, Nico Kadel-Garcia wrote:
> /proc, though.. that one might more awkward to protect. Those are
> nominally "files". Has anyone reviewed trying to protect /proc, or in
> the case I mentioned /var/named/chroot/proc, from misapplied patches?
I don't think i
Am 07.11.2011 06:53, schrieb yerra babji:
Is there any way to mandate svn users to check in all the files they
modified?
No.
This in and of itself is also not a problem, I would claim. You are
obviously seeing a problem you would like to "fix" with this. If you
told us what that problem is,
On Sunday, November 06, 2011 6:49 PM, "Nico Kadel-Garcia"
wrote:
> If device nodes and pipes are protected by being "unversioned" and
> impossible to "version",
It's definitely possible to have a special file obstruct a versioned file...
(svn checkout wc; /bin/rm wc/iota; mk{nod,fifo,..} wc/iot
On Mon, Nov 7, 2011 at 3:30 AM, Stefan Sperling wrote:
> On Sun, Nov 06, 2011 at 06:49:07PM -0500, Nico Kadel-Garcia wrote:
>> /proc, though.. that one might more awkward to protect. Those are
>> nominally "files". Has anyone reviewed trying to protect /proc, or in
>> the case I mentioned /var
> On Fri, Nov 4, 2011 at 3:26 PM, j s wrote:
> I have apache running and connect to my repo using http. What is the best
> way to upgrade to latest svn server version? Would gladly appreciate any
> documentation that helps in upgrading
>
> You pretty much just need the new server binaries. You d
On Mon, Nov 7, 2011 at 10:09 AM, Bob Archer wrote:
> > On Fri, Nov 4, 2011 at 3:26 PM, j s wrote:
> > I have apache running and connect to my repo using http. What is the best
> > way to upgrade to latest svn server version? Would gladly appreciate any
> > documentation that helps in upgrading
>
Hello,
I've got installed a VisualSVN in a Windows Server 2003 (it has just a
drive C: with 10GB)
I'm planning to backup a VisualSVN server in this way:
- Make a disk image with Ghost or some other software of my Windows
Server 2003.
- Every night make a copy of the whole folder: 'C:\Repositorie
How do know I have a 1.7.1 working copy? Can I tell by looking at the working
copy on the file system? The older version had .svn directories and the
entries file. What does the new working copy look like?
We are running 1.7.1 and 1.6.17 on two different servers - right now I am not
sure I a
Hi!
Is there any way to do a commit with and empty changeset, but non-empty commit
message?
I made a typo in a commit message. Unfortunately the typo isn't just
cosmetic, since it is right in a revision number referencing another commit.
Even more unfortunately, changing the commit message after
Assuming you have a versioned file called 'iota',
% cp iota iota2
% echo >> iota
% svn ci iota
(editor pops up)
(shell out from editor)
% cp iota2 iota
% exit
(back to editor)
(enter commit message)
(exit editor)
Jö Fahlke wrote on Mon, Nov 07, 2011 at 22:34:53 +0100:
> Hi!
>
> Is there any way
The real answer is "Run tools/dev/wc-format.py".
If you can't do that, look for **/.svn/wc.db. In 1.7, the shell command
% sqlite3 .svn/wc.db 'pragma user_version;'
returns the magic number SVN_WC__FORMAT_NUMBER == 29.
joe.floe...@sungard.com wrote on Mon, Nov 07, 2011 at 20:50:10 +:
> Ho
Am Mon, 7. Nov 2011, 23:57:59 +0200 schrieb Daniel Shahaf:
> Assuming you have a versioned file called 'iota',
>
> % cp iota iota2
> % echo >> iota
> % svn ci iota
> (editor pops up)
> (shell out from editor)
> % cp iota2 iota
> % exit
> (back to editor)
> (enter commit message)
> (exit editor)
I'm attempting to coordinate issue-tracking software with my
subversion repository.
We have an existing Bugzilla database and an existing subversion
repository that is accessed via svn+ssh through a single account, as
described in the manual here:
http://svnbook.red-bean.com/en/1.6/svn.serverconf
Hi all,
We have recently upgraded our subversion servers from 1.6.17 to 1.7.1,
and as I usually do when making the 'semi-major' upgrade, dumped and
reloaded the repository.
Our environment is Ubuntu 10.04.03 LTS server, apache 2.2, subversion
1.7.1 (was 1.6.17). Our clients are mixed windows and
On Tue, 2011-11-08 at 15:07 +1100, Tony Butt wrote:
Hi all,
We have recently upgraded our subversion servers from 1.6.17 to 1.7.1,
and as I usually do when making the 'semi-major' upgrade, dumped and
reloaded the repository.
Our environmen
Hi, Big George,
Von: Big George [mailto:jbet...@gmail.com]
> I've got installed a VisualSVN in a Windows Server 2003 (it has just a drive
> C: with 10GB)
10GB? That's a little small for a Windows Server 2003. Where did you get such
ancient hardware?
If it is a virtual machine, maybe you could
Hi, Joe,
Von: joe.floe...@sungard.com [mailto:joe.floe...@sungard.com]
> How do know I have a 1.7.1 working copy? Can I tell by looking at the
> working copy on the file system? The older version had .svn directories and
> the entries file. What does the new working copy look like?
Normally
18 matches
Mail list logo
