Compare commits

..

3 Commits

Author SHA1 Message Date
e199b99947
fix gpg basics ref 2024-07-18 19:42:05 +02:00
6d44a44d0d
expand making torrents 2024-05-29 17:09:10 +02:00
60c5cd829e
rename void locale 2024-05-26 16:00:18 +02:00
3 changed files with 32 additions and 3 deletions

View File

@ -124,7 +124,7 @@ Refreshing keys will tell you if some key you have contains a signature from som
gpg --refresh-keys gpg --refresh-keys
``` ```
You can use the [crontab](../basics/cron.md) to refresh keys. You can use the [crontab](../../basics/cron.md) to refresh keys.
# Export # Export

View File

@ -1,6 +1,6 @@
--- ---
title: "locales" title: "Void locale"
tags: [ "void" ] tags: [ "void", "locale" ]
--- ---
Check the current locales: Check the current locales:

View File

@ -136,3 +136,32 @@ Without the `--anonymize` flag, the torrent file output will have a 'created by'
- udp://explodie.org:6969/announce - udp://explodie.org:6969/announce
- https://tracker.gbitt.info:443/announce - https://tracker.gbitt.info:443/announce
- http://tracker.gbitt.info:80/announce - http://tracker.gbitt.info:80/announce
## Verify
Add your torrent and notes its number:
```bash
transmission-remote -a "$file".torrent
transmission-remote -l
transmission-remote -t "$number" -i
```
The information in the last command shows that it's not verified, so you can verify with `-v`.
```bash
transmission-remote -t "$number" -v
```
If transmission cannot find it, then tell it where to find the torrent:
```bash
transmission-remote -t "$number" --find "$(pwd)"
```
...and of course, make sure the permissions allow transmission to see the target.
```bash
ls -ld "$file"
```