IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
* Switch to using libvirt+minimal instead of libvirt project,
for shorter build times
* Actually do a git build job in CentOS Stream & AlmaLinux
* Drop AlmaLinux 8
* Update to latest Alpine versions
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
On Alpine, 'musl-dev' won't get pulled in by default, even if gcc is
asked for, and thus C programs won't link.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
The project package lists previously held in libvirt-ci.git are
being moved into their respective project git repos.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Currently translated at 100.0% (182 of 182 strings)
Translation: virt-viewer/virt-viewer
Translate-URL: https://translate.fedoraproject.org/projects/virt-viewer/virt-viewer/zh_Hans/
Signed-off-by: eirik song <eirik.song@gmail.com>
Added translation using Weblate (Chinese (Simplified))
Signed-off-by: eirik song <eirik.song@gmail.com>
Translated using Weblate (Chinese (Simplified) (zh_CN))
Currently translated at 100.0% (182 of 182 strings)
Translation: virt-viewer/virt-viewer
Translate-URL: https://translate.fedoraproject.org/projects/virt-viewer/virt-viewer/zh_CN/
Signed-off-by: eirik song <eirik.song@gmail.com>
The application uses an application-id of
"org.virt-manager.virt-viewer" (see function
remote_viewer_new in src/remote-viewer.c).
So far, there was a mismatch between this
application-id and the desktop file name,
resulting e.g. in no proper window icon being
used when running the app on KDE Plasma Wayland.
Adjust the name of the desktop and appdata
files to match the application-id as expected.
Also update the translatable strings using this
command:
ninja -C _build virt-viewer-pot
Fixes: https://gitlab.com/virt-viewer/virt-viewer/-/issues/135
Signed-off-by: Michael Weghorn <m.weghorn@posteo.de>
The virt-viewer code currently only works with librest 0.7
/ libgovirt < 0.3.9.
Check for this condition in meson to prevent later compile
time errors.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Add a configuration file for codespell; it is tweaked to work on the
current codebase, i.e. skipping non-sources.
Signed-off-by: Pino Toscano <ptoscano@redhat.com>
The connection file created by oVirt contains the trusted CA.
When https://gitlab.gnome.org/GNOME/gtk-vnc/-/merge_requests/24 is
merged, we can pass this CA certificate to gtk-vnc to have it trusted.
This can replace manually putting the cacert.pem into ~/.pki/CA/
Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
The command depends on POSIX-compatible shell being the default shell on
the remote side of SSH, but that might not be the case. To make sure
the command gets parsed correctly this commit encloses it in extra
single quotes (to avoid it being parsed by the remote shell) and passes
that string as a parameter to `sh -c`.
Signed-off-by: Martin Kletzander <nert.pinx@gmail.com>
When using the result of find_program, meson may expand
it to include both an interpretor path and the script
path. If we then add the interpretor path too, we fail.
Using 'full_path()' ensures we get only the script path.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This refresh switches the CI for contributors to be triggered by merge
requests. Pushing to a branch in a fork will no longer run CI pipelines,
in order to avoid consuming CI minutes. To regain the original behaviour
contributors can opt-in to a pipeline on push
git push <remote> -o ci.variable=RUN_PIPELINE=1
This variable can also be set globally on the repository, though this is
not recommended. Upstream repo pushes to branches will run CI.
The use of containers has changed in this update, with only the upstream
repo creating containers, in order to avoid consuming contributors'
limited storage quotas. A fork with existing container images may delete
them. Containers will be rebuilt upstream when pushing commits with CI
changes to the default branch. Any other scenario with CI changes will
simply install build pre-requisite packages in a throaway environment,
using the ci/buildenv/ scripts. These scripts may also be used on a
contributor's local machines.
With pipelines triggered by merge requests, it is also now possible to
workaround the inability of contributors to run pipelines if they have
run out of CI quota. A project member can trigger a pipeline from the
merge request, which will run in context of upstream, however, note
this should only be done after reviewing the code for any malicious
CI changes.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
The container jobs only exist if there was a dockerfile change in the
pipeline, so the dep from the 'codestyle' job needs to be marked as
optional
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>