Тут показані розбіжності між вибраною ревізією та поточною версією сторінки.
| Порівняння попередніх версій Попередня ревізія Наступна ревізія | Попередня ревізія | ||
|
software:os:linux:additional_repos [2022/08/17 15:48] charon |
software:os:linux:additional_repos [2023/02/14 19:58] (поточний) charon [Add signing key for repository] |
||
|---|---|---|---|
| Рядок 16: | Рядок 16: | ||
| I think it means if you need to bother with key, then just put it to /// | I think it means if you need to bother with key, then just put it to /// | ||
| + | ===== Using new .sources ===== | ||
| + | .sources file instead of a .list file. This method is relatively new, and uses the deb822 multiline format that is less ambiguous compared to the deb . . . declaration, | ||
| + | Types: deb | ||
| + | Architectures: | ||
| + | Signed-By: / | ||
| + | URIs: https:// | ||
| + | Suites: jammy | ||
| + | Components: main | ||
| + | |||
| ===== How to get the key ===== | ===== How to get the key ===== | ||
| There are two ways, depending on what package developer implemented | There are two ways, depending on what package developer implemented | ||
| - | 1. Download key from keyserver or keyserver pool | + | ==== 1. Download key from keyserver or keyserver pool ==== |
| + | sudo gpg --homedir /tmp --no-default-keyring --keyring / | ||
| + | keyserver.ubuntu.com --recv-keys E298A3A825C0D65DFD57CBB6517111119E084DAB9 | ||
| - | First, download the key from keyserver to local user storage: | + | ==== 2. Download |
| - | | + | |
| - | After that export | + | Check if key is armored (looks like ASCII text and not binary), and if so, unarmor |
| - | gpg --export | + | |
| - | <WRAP center round important 60%> | + | Move the key to /// |
| - | I didn't find out whether key should be ascii-armored or not. Most likely should be unarmored (binary). | + | mv dbeaver.gpg / |
| - | </WRAP> | + | |
| - | + | ===== Links ===== | |
| - | + | | |
| - | [[https:// | + | |