attachments unless you recognize the sender and know
the content is safe.
On Mon, 23 May 2022 11:03:32 +, "Morin, Michael"
wrote:
>>On Mon, May 23, 2022 at 6:16 AM Morin, Michael
>>wrote:
>>>
>>> In my case, I have no choice in the matter of what ser
Yes, each repository is a distinct Subversion repository. We have about 300
Subversion users located in different departments and 171 repositories.
-Original Message-
From: Nico Kadel-Garcia
Sent: Monday, May 23, 2022 6:58 AM
To: Morin, Michael
Cc: users@subversion.apache.org
Subject
In my case, I have no choice in the matter of what server and OS to move to. We
don't use VisualSVN. We just use Tortoise with Subversion. When we last did a
migration from one Windows server to another, it was a tedious process of
contacting the users of the repository, asking them if the repo
We need to move Subversion off of a Windows 2012 server and onto a Windows 2019
server. Is there a simpler way to do this other than moving each repository one
by one? I have over 170 repositories that I need to migrate to the new server.
Can the entire SVN instance be backed up and
I'm trying to get my new server certificate to work with the Subversion Edge
Console by converting the server.crt file into PKCS12 format and then creating
a JKS file. I am using OpenSSL to do this. When I execute the command, openssl
pkcs12 -export -in E:/csvn/data/conf/server.crt -inkey
I have an automated SVN job which fails when it's run via CA Workload, but when
I run it myself it always goes through. Can anyone tell me why this might be?
The job does the following things:
1) svn update
2) Do some "git" commands to download a repository from another location
