Please notice this important news item for D-I. In short, the Subversion repository will be converted to git. For l10n, one plan is to keep the current packages/po directory in SVN. Translators would then continue to commit there while the cronned l10n-sync scripts will take general translation files from SVN then commit back individual packages translations to git. The point is to avoid translators the "hassle" of learning git. So, for now, please avoid committing to D-I SVN (even in packages/po). ----- Forwarded message from Joey Hess <joeyh@debian.org> ----- Date: Sun, 16 Jan 2011 17:51:17 -0400 From: Joey Hess <joeyh@debian.org> To: debian-boot@lists.debian.org Subject: git conversion, probably tomorrow X-Mailing-List: <debian-boot@lists.debian.org> archive/latest/157020 X-CRM114-Status: Good ( pR: 34.4975 ) Immediatly after rc2 is released we plan to convert d-i from svn to git. This will involve locking the svn repository to prevent commits, running a conversion process that will take several hours, unlocking the svn repo, and *removing* most of the content from svn trunk (with the notable exceptions of packages/po and manual/). Then you will need to use the "mr" command to checkout the rest of the d-i tree from its new git repositories. At the moment these things are expected to be temporarily broken by the conversion: * Each system running a daily build will need to be updated to use the new debian-installer git repo, and daily builds will be broken until that is done. * l10n-sync needs to be made git aware, and l10n changes won't be propigated until it is. * Commits tagged "SILENT_COMMIT" and "[l10n]" won't be blocked from irc and the mailing list, until we come up with modified git hook scripts. * If you have uncommitted changes in your d-i checkout now, you will probably get svn conflicts when the changed files are removed from svn. Now would be a convenient time to commit such changes, if you just forgot to do so before. Or you might want to use "svn diff" now to store the patches. Of course, once we've switched to git, you can easily store such changes in a branch. For a full overview of the conversion plan, see http://svn.debian.org/viewsvn/d-i/trunk/scripts/togit/README -- see shy jo ----- End forwarded message ----- --
Attachment:
signature.asc
Description: Digital signature