The publican package is abandoned and it is a mandatory build dep.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Fedora 33 is replaced with Fedora 35
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The repo-lockdown service used to run as a bot outside GitHub, but has
now switched to using the GitHub Actions workflow framework. This
requires use of a new configuration file.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

We now use lcitool's manifest feature to generate files.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This uses the command "lcitool manifest ci/manifest.yml" to re-generate
all existing dockerfiles and gitlab CI config.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This is to be used with the command "lcitool manifest ci/manifest.yml"
to re-generate all existing dockerfiles and gitlab CI config.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This platform is no longer supported by libvirt.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The current docker:dind container has broken default seccomp filter that
results in clone3 being blocked, which in turn breaks Fedora 35 rawhide.

This custom image has a workaround that causes the seccomp filter to
return ENOSYS for clone3 instad of EPERM, thus triggering glibc to
fallback to clone correctly.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Changes contained in this refresh:
- CentOS 7 is pulled from docker.io registry
- PowerTools repo name regression fix for CentOS Stream
- enhancement for the workaround fix for JDK installation fails on Debian 10
  '-slim' containers
Signed-off-by: Erik Skultety <eskultet@redhat.com>

This makes the dockerfile name match the output container name
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This introduces Fedora 33 and removes some redundant packages.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

With the introduction of automated CI pipelines, we are now ready to switch
to using merge requests for the project. With this switch we longer wish
to have patches sent to the mailing list.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The docs build needs to validate one axis

 - A variety of publican versions

We get coverage for this by running builds across various distros.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This job uses the shared "check-dco" image to validate that all
commits on a branch in a developer's repo fork have a suitable
Signed-off-by statement present.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Libvirt uses GitHub as an automated read-only mirror. The goals were to
have a disaster recovery backup for libvirt.org, a way to make it easy
for people to clone their own private copy of libvirt Git, and finally
as a way to interact with apps like Travis.

The project description was set to a message telling people that we
don't respond to pull requests. This was quite a negative message to
potential contributors, and also did not give them any guidance about
the right way to submit to libvirt. Many also missed the description and
submitted issues or pull requests regardless.

It is possible to disable the issue tracker in GitHub, but there is no
way to disable merge requests. Disabling the issue tracker would also
leave the problem of users not being given any positive information
about where they should be reporting instead.

There is a fairly new 3rd party application built for GitHub that
provides a bot which auto-responds to both issues and merge requests,
closing and locking them, with a arbitrary comment:

   https://github.com/apps/repo-lockdown



This commit adds a suitable configuration file for libvirt, which
tries to give a positive response to user's issue/pullreq and guide
them to the desired contribution path on GitLab.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The "git-publish" tool is a useful git extension for sending patch
series for code review. It automatically creates versioned tags
each time code on a branch is sent, so that there is a record of
each version. It also remembers the cover letter so it does not
need re-entering each time the series is reposted.

With this config file present it is now sufficient[1] to run

  $ git publish

to send all patches in a branch to the list for review, with the
correct subject prefix added for this non-core libvirt module.

[1] Assuming your $HOME/.gitconfig has an SMTP server listed
at least e.g.

   [sendemail]
        smtpserver = smtp.example.com
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Publican blindly overrides the RPM output directory from your
rpmmacros file, so we need to move the RPMs to the right place
at end of the build

* autobuild.sh: Move RPMs to AUTOBUILD_PACKAGE_ROOT/rpm

* autobuild.sh: Force creation of publican directory

* .gitignore: Ignore editor backups
* Makefile: Add a 'install' rule
* autobuild.sh: Run an automated build
* publican-libvirt.spec: Fix source URL

Was previously pointing to libvirt.org/docs/ which was 404.
Now correctly points to libvirt.org/docs.html.

Publican theme for libvirt docs created using

  publican create_brand --name=libvirt --lang=en-US

and then boilerplate text filled in by hand