Appendix C. Checkout commands
Prev     Next

Appendix C. Checkout commands

First said, translators don't need to checkout the repository by hand to translate the po files. They can get all files here: 

https://d-i.debian.org/l10n-stats/<LEVEL>/files/<LANGUAGECODE>/

where <LEVEL> is either level1, level2 or level3, and <LANGUAGECODE> is your language code like de, es, zh_CN, ...

POT templates can be found at: 

https://d-i.debian.org/l10n-stats/<LEVEL>/POT/

C.1. Checkout commands

For translators who prefer working from developer's repositories, the following list contains, level by level, all checkout commands to get access to translation material.

C.1. Level 1

  • git clone git@salsa.debian.org:installer-team/d-i.git

C.2. Level 2

C.2.1. Tasksel
  • git clone git@salsa.debian.org:installer-team/tasksel.git
C.2.2. Iso-codes
  • git clone git@salsa.debian.org:debian/iso-codes.git
C.2.3. Popularity-contest
  • git clone git@salsa.debian.org:popularity-contest-team/popularity-contest.git
C.2.4. eject (in util-linux)
  • git clone git@salsa.debian.org:debian/util-linux.git
C.2.5. espeakup
  • git clone git@salsa.debian.org:a11y-team/espeakup.git
C.2.6. grub2
  • git clone git@salsa.debian.org:grub-team/grub.git

C.3. Level 3

C.3.1. Debconf
  • git clone git@salsa.debian.org:pkg-debconf/debconf.git
C.3.2. Newt
  • git clone git@salsa.debian.org:mckinstry/newt.git
C.3.3. Win32-loader
  • git clone -q git@salsa.debian.org:installer-team/win32-loader.git

C.4. Checkout commands for developers

Developers need the following commands to checkout the whole source tree: 

git clone git@salsa.debian.org:installer-team/d-i.git
cd d-i
./scripts/git-setup
mr checkout
Prev     Next
B.5. Changelog entries handling   Home  Appendix D. Reporting bugs against Debian packages