@@ -51,17 +51,19 @@ The installer takes care of installing them for you.
|
51 | 51 | |
52 | 52 | If you have downloaded the source code: |
53 | 53 | |
54 | | -python setup.py install |
| 54 | +```bash |
| 55 | +python setup.py install |
| 56 | +``` |
55 | 57 | |
56 | 58 | or if you want to obtain a copy from the Pypi repository: |
57 | 59 | |
58 | | -pip install GitPython |
| 60 | +```bash |
| 61 | +pip install GitPython |
| 62 | +``` |
59 | 63 | |
60 | 64 | Both commands will install the required package dependencies. |
61 | 65 | |
62 | | -A distribution package can be obtained for manual installation at: |
63 | | - |
64 | | -http://pypi.python.org/pypi/GitPython |
| 66 | +A distribution package can be obtained for manual installation at: <http://pypi.python.org/pypi/GitPython>. |
65 | 67 | |
66 | 68 | If you like to clone from source, you can do it like so: |
67 | 69 | |
@@ -157,15 +159,15 @@ tarballs.
|
157 | 159 | This script shows how to verify the tarball was indeed created by the authors of |
158 | 160 | this project: |
159 | 161 | |
160 | | -``` |
| 162 | +```bash |
161 | 163 | curl https://files.pythonhosted.org/packages/09/bc/ae32e07e89cc25b9e5c793d19a1e5454d30a8e37d95040991160f942519e/GitPython-3.1.8-py3-none-any.whl > gitpython.whl |
162 | 164 | curl https://files.pythonhosted.org/packages/09/bc/ae32e07e89cc25b9e5c793d19a1e5454d30a8e37d95040991160f942519e/GitPython-3.1.8-py3-none-any.whl.asc > gitpython-signature.asc |
163 | 165 | gpg --verify gitpython-signature.asc gitpython.whl |
164 | 166 | ``` |
165 | 167 | |
166 | 168 | which outputs |
167 | 169 | |
168 | | -``` |
| 170 | +```bash |
169 | 171 | gpg: Signature made Fr 4 Sep 10:04:50 2020 CST |
170 | 172 | gpg: using RSA key 27C50E7F590947D7273A741E85194C08421980C9 |
171 | 173 | gpg: Good signature from "Sebastian Thiel (YubiKey USB-C) <byronimo@gmail.com>" [ultimate] |
@@ -175,19 +177,19 @@ gpg: aka "Sebastian Thiel (In Rust I trust) <sebastian.thiel@icl
|
175 | 177 | You can verify that the keyid indeed matches the release-signature key provided in this |
176 | 178 | repository by looking at the keys details: |
177 | 179 | |
178 | | -``` |
| 180 | +```bash |
179 | 181 | gpg --list-packets ./release-verification-key.asc |
180 | 182 | ``` |
181 | 183 | |
182 | 184 | You can verify that the commit adding it was also signed by it using: |
183 | 185 | |
184 | | -``` |
| 186 | +```bash |
185 | 187 | git show --show-signature ./release-verification-key.asc |
186 | 188 | ``` |
187 | 189 | |
188 | 190 | If you would like to trust it permanently, you can import and sign it: |
189 | 191 | |
190 | | -``` |
| 192 | +```bash |
191 | 193 | gpg --import ./release-verification-key.asc |
192 | 194 | gpg --edit-key 4C08421980C9 |
193 | 195 | |
|