Zen

Translation

It is also possible to QEMU/KVM guest VMs via libvirt instead of the default VirtualBox. VirtualBox is still the recommended setup since that is what is used by f-droid.org, but there are cases where it is not possible to run VirtualBox, like on a machine that is already running QEMU/KVM guests. While VirtualBox was used in the past, QEMU/KVM guest VMs via libvirt is still the recommended setup since that is what is used by f-droid.org. In order to make the libvirt image files directly readable by `vagrant package`, _libvirt_'s QEMU needs to be configured to always set the ownership to `libvirt.libvirt`.
English type: Plain text
While VirtualBox was used in the past, QEMU/KVM guest VMs via libvirt is still the recommended setup since that is what is used by f-droid.org. In order to make the libvirt image files directly readable by `vagrant package`, _libvirt_'s QEMU needs to be configured to always set the ownership to `libvirt.libvirt`.
521/3140 · 314

Sign in to save the translation.

English Russian Actions
Running builds
Выполнение сборки
When using the buildserver, running `fdroid` directly from a git checkout of _fdroidserver_ will be the easiest. If you don't already have the _fdroidserver_ tools installed and setup, you will need to do that next: [Installing the Server and Repo Tools](../Installing_the_Server_and_Repo_Tools). That provides all of the dependencies needed to run _fdroidserver_ from git.
При использовании buildserver запуск `fdroid` непосредственно из git checkout _fdroidserver_ будет самым простым. Если у вас еще не установлены и не настроены инструменты _fdroidserver_, вам нужно сделать это следующим образом: [Установка сервера и инструментов репо](../Installing_the_Server_and_Repo_Tools). Это обеспечивает все зависимости, необходимые для запуска _fdroidserver_ из git.
Now you are ready to run builds. Test by building the latest fdroid version:
Теперь вы готовы к запуску сборок. Протестируйте сборку последней версии fdroid:
fdroid:~/fdroidserver$ cd ~/fdroiddata
fdroid:~/fdroiddata$ ~/fdroidserver/fdroid build org.fdroid.fdroid -l --server
 
Setting up QEMU/KVM/libvirt
 
While VirtualBox was used in the past, QEMU/KVM guest VMs via libvirt is still the recommended setup since that is what is used by f-droid.org. In order to make the libvirt image files directly readable by `vagrant package`, _libvirt_'s QEMU needs to be configured to always set the ownership to `libvirt.libvirt`.
Также можно запускать гостевые виртуальные машины QEMU/KVM через libvirt вместо стандартного VirtualBox. VirtualBox по-прежнему является рекомендуемой настройкой, поскольку именно она используется на f-droid.org, но бывают случаи, когда VirtualBox невозможно запустить, например, на машине, на которой уже запущены гостевые QEMU/KVM. Чтобы файлы образов libvirt можно было напрямую читать `vagrant package`, _libvirt_ в QEMU должен быть настроен так, чтобы всегда устанавливать право собственности на `libvirt.libvirt`.
root:~# cat << EOF >> /etc/libvirt/qemu.conf
user = "libvirt"
group = "libvirt"
dynamic_ownership = 1
EOF
root:~# service libvirtd restart
 
Debian/bullseye and Ubuntu/xenial
Debian/stretch и Ubuntu/xenial
root:~# adduser fdroid libvirt
root:~# adduser fdroid libvirt-qemu
 
older Debian and Ubuntu
старые версии Debian и Ubuntu
root:~# adduser fdroid libvirtd
root:~# adduser fdroid kvm
 

Loading…

User avatar None

String updated in the repository

  1. F-Droid
  2. Website Docs
  3. Russian
While VirtualBox was used in the past, QEMU/KVM guest VMs via libvirt is still the recommended setup since that is what is used by f-droid.org. In order to make the libvirt image files directly readable by `vagrant package`, _libvirt_'s QEMU needs to be configured to always set the ownership to `libvirt.libvirt`.
Также можно запускать гостевые виртуальные машины QEMU/KVM через libvirt вместо стандартного VirtualBox. VirtualBox по-прежнему является рекомендуемой настройкой, поскольку именно она используется на f-droid.org, но бывают случаи, когда VirtualBox невозможно запустить, например, на машине, на которой уже запущены гостевые QEMU/KVM. Чтобы файлы образов libvirt можно было напрямую читать `vagrant package`, _libvirt_ в QEMU должен быть настроен так, чтобы всегда устанавливать право собственности на `libvirt.libvirt`.
6 months ago
User avatar None

Source string changed

  1. F-Droid
  2. Website Docs
  3. Russian
It is also possible to QEMU/KVM guest VMs via libvirt instead of the default VirtualBox. VirtualBox is still the recommended setup since that is what is used by f-droid.org, but there are cases where it is not possible to run VirtualBox, like on a machine that is already running QEMU/KVM guests. While VirtualBox was used in the past, QEMU/KVM guest VMs via libvirt is still the recommended setup since that is what is used by f-droid.org. In order to make the libvirt image files directly readable by `vagrant package`, _libvirt_'s QEMU needs to be configured to always set the ownership to `libvirt.libvirt`.
6 months ago
Browse all string changes

Things to check

Double space

Translation contains double space

Fix string

Reset

Glossary

English Russian
F-Droid F-Droid Glossary
F-Droid F-Droid Glossary

String information

Source string description
type: Plain text
Flags
md-text
Source string location
_docs/Build_Server_Setup.md
String age
6 months ago
Last updated
6 months ago
Source string age
6 months ago
Translation file
po/_docs.ru.po, string 686