[med-svn] r24972 - trunk/community/website/docs

[Andreas Tille]

Author: tille
Date: 2018-01-10 15:25:20 +0000 (Wed, 10 Jan 2018)
New Revision: 24972

Modified:
   trunk/community/website/docs/policy.xml
Log:
No packages in SVN any more.  TODO: Migration of this text and other information to Git


Modified: trunk/community/website/docs/policy.xml
===================================================================
--- trunk/community/website/docs/policy.xml	2018-01-10 12:51:01 UTC (rev 24971)
+++ trunk/community/website/docs/policy.xml	2018-01-10 15:25:20 UTC (rev 24972)
@@ -190,90 +190,6 @@
 				<ulink url="http://wiki.debian.org/Alioth/SSH">this wiki article</ulink>.
 			</para>
 		</sect2>
-		<sect2 id="svn-repository-structure">
-			<title>Subversion usage is deprecated</title>
-			<para>The Debian Med team is migrating from SVN to Git to catch up with the close
-			      down of Alith.  The deprecated SVN repository is structured as follows:<programlisting>
-debian-med/
- └ trunk/
-    ├ community/
-    │  ├ debtags/
-    │  ├ infrastructure/
-    │  └ website/
-    └ packages/
-       ├ <package A>/
-       │  ├ branches/
-       │  ├ tags/
-       │  └ trunk/
-       │     └ debian/
-       ├ <package B>/
-       │  ├ branches/
-       │  ├ tags/
-       │  └ trunk/
-       │     └ debian/
-       …</programlisting>
-      </para>
-		</sect2>
-		<sect2 id="subversion-to-git">
-		  <title>Migration of a source package from Subversion to Git</title>
-		    <para>
-			If you touch a package in SVN you should consider strongly to move the packaging to Git.
-		    </para>
-		  <para>
-		    For packages were we set the <literal>mergeWithUpstream</literal>
-		    property, which excludes the upstream sources, there is no easy way to
-		    prepare a Git repository from our Subversion repository that would look
-		    like the package was always managed in Git. Nevertheless, the following
-		    recipe will generate a Git repository that contains all the history of
-		    the debian directory.
-			<programlisting>
-svn checkout svn://anonscm.debian.org/debian-med/trunk/helper-scripts
-cd helper-scripts
-./convert_svn_2_git <package>
-cd <package>  # check that debian/ dir exists - if not check logfile!!
-git branch upstream
-gbp import-orig --pristine-tar <orig.tar.gz_of_last_uploaded_version>
-vi debian/control # replace Vcs-Fields from SVN to Git
-dch "Moved packaging from SVN to Git"
-../inject-into-alioth-git # this should work nicely to inject your package into git.debian.org
-			</programlisting>
-			In case <filename>convert_svn_2_git</filename> might fail for whatever reason your last resort is
-			<programlisting>
-gbp import-dscs --debsnap
-			</programlisting>
-			Please help the Debian Med team with the SVN to Git migration.
-			</para>
-		</sect2>
-		<sect2 id="subversion-tips">
-			<title>Once you moved the package to Git drop a note in Subversion </title>
-			<para>The conversion process from SVN to Git does not conserve tags.
-			      This is no real issue since a tag is actually what we upload and
-			      the uploaded code is available at snapshot.debian.org.  So all
-			      <filename>tags</filename> will be deleted from SVN and
-			      <filename>trunk</filename> is cleaned up.  In the end we drop a
-			      note about the removal:
-			<programlisting>
-svn checkout svn+ssh://svn.debian.org/svn/debian-med/trunk/packages/<package>
-cd <package>
-svn rm tags
-svn rm trunk/debian
-svn commit -m "Moved packaging to Git"
-svn update      # THIS IS IMPORTANT! Blame SVN for this!
-# Leave a yaml file to document the move to Git
-cat >trunk/README.status <<EOT
----
-Format: 1
-Status: git
-SVNDeleteRevision: <SVNcommitID>
-URL: https://git.debian.org/git/debian-med/<package>.git
-Comment: <
-  This package is now managed in a Git repository.
-EOT
-svn add trunk/README.status
-svn commit -m "Document packaging to Git"
-			</programlisting>
-			</para>
-		</sect2>
 		<sect2 id="git-repository-structures">
 			<title>Common Git repository structures</title>
 			<para>
@@ -820,9 +736,7 @@
 		<sect2 id="vcs">
 			<title>Version control systems</title>
 			<para>
-				We are forced to use Git since SVN support will be droped.  As
-				explained above <link linkend="subversion-to-git">above</link>
-				we are migrating the formerly used SVN to Git.
+				The Debian Med team is using Git as VCS.
 			</para>
 			<sect3 id="vcs-git">
 				<title>Source package stored in a Git repository</title>