Difference between revisions of "Translations:Makepkg/36/ru"

Latest revision as of 09:07, 27 February 2023

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (Makepkg)

The gpg keys are expected to be stored in the user's {{ic|~/.gnupg/pubring.gpg}} file. In case it does not contain the given signature, makepkg shows a warning.
{{hc|makepkg|<nowiki>
[...]
==> Verifying source file signatures with gpg...
pkgname-pkgver.tar.gz ... FAILED (unknown public key 1234567890)
==> WARNING: Warnings have occurred while verifying the signatures.
Please make sure you really trust them.
[...]
</nowiki>}}
To show the current list of gpg keys use the gpg command.
{{bc|gpg --list-keys}}
If the pubring.gpg file does not exist it will be created for you immediatly.
You can now proceed with configuring gpg to allow compiling AUR packages submitted by Arch Linux developers with successful signature checking.
Add the following line to the end of your gpg configuration file to include the pacman keyring in your user's personal keyring.
{{hc|~/.gnupg/gpg.conf|<nowiki>
[...]
keyring /etc/pacman.d/gnupg/pubring.gpg
</nowiki>}}
When configured as before, the output of {{ic|gpg --list-keys}} contains a list of keyrings and developers. Now makepkg can compile AUR packages submitted by Arch Linux developers with successful signature checking.

The gpg keys are expected to be stored in the user's {{ic|~/.gnupg/pubring.gpg}} file. In case it does not contain the given signature, makepkg shows a warning.
{{hc|makepkg|<nowiki>
[...]
==> Verifying source file signatures with gpg...
pkgname-pkgver.tar.gz ... FAILED (unknown public key 1234567890)
==> WARNING: Warnings have occurred while verifying the signatures.
    Please make sure you really trust them.
[...]
</nowiki>}}
To show the current list of gpg keys use the gpg command.
{{bc|gpg --list-keys}}
If the pubring.gpg file does not exist it will be created for you immediatly.
You can now proceed with configuring gpg to allow compiling AUR packages submitted by Arch Linux developers with successful signature checking.
Add the following line to the end of your gpg configuration file to include the pacman keyring in your user's personal keyring.
{{hc|~/.gnupg/gpg.conf|<nowiki>
[...]
keyring /etc/pacman.d/gnupg/pubring.gpg
</nowiki>}}
When configured as before, the output of {{ic|gpg --list-keys}} contains a list of keyrings and developers. Now makepkg can compile AUR packages submitted by Arch Linux developers with successful signature checking.

Ожидается, что ключи gpg будут храниться в файле пользователя ~/.gnupg/pubring.gpg. Если он не содержит заданной подписи, makepkg выдает предупреждение.

makepkg

[...]
==> Verifying source file signatures with gpg...
pkgname-pkgver.tar.gz ... FAILED (unknown public key 1234567890)
==> WARNING: Warnings have occurred while verifying the signatures.
    Please make sure you really trust them.
[...]

Чтобы показать текущий список ключей gpg, используйте команду gpg.

gpg --list-keys

Если файл pubring.gpg не существует, он будет создан немедленно. Теперь вы можете приступить к настройке gpg, чтобы разрешить компиляцию пакетов AUR, предоставленных разработчиками Arch Linux с успешной проверкой подписи. Добавьте следующую строку в конец конфигурационного файла gpg, чтобы включить связку ключей pacman в личную связку ключей своего пользователя.

~/.gnupg/gpg.conf

[...]
keyring /etc/pacman.d/gnupg/pubring.gpg

При настройке, как и раньше, вывод gpg --list-keys содержит список связок ключей и разработчиков. Теперь makepkg может компилировать пакеты AUR, предоставленные разработчиками Arch Linux, с успешной проверкой подписи.