Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

We may want to run the CI pipeline to pull updates from a debian release
backports upstream. Extend this script to handle those branches.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Updates available in -security and -proposed-updates fall into the main Debian repository
after a Debian release point. In case an update has been imported from -security or -proposed-updates,
our main Debian branch stays out of date. Consequently, the Dashboard wrongly complains about an
available update from Debian.

In this scenario, the main Debian branch needs to be synchronized with the
-security or -proposed-updates branch used previously.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

These being essential packages, a script is needed to backup binaries
used to do the upgrade.

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Explicitly attempt a fast forward merge before rebasing.

Currently we always try to rebase, which already doews a fast-forward
merge when possible. The issue is that after that we incoditionally try
to append a new changelog entry and if we're fast-forwarding we should
**not** to that since the changelog will already have a version equal or
newer than the one we're trying to add.

By explicitly attempting a fast-forward merge and exiting early we avoid
that issue.

This has not been a particular issue so far since the mirroring
pipeline which uses the rebasing feature does not usually trigger it
when a fast-forward is possible and will create all the branches in
their final state.

However in some cases unrelated errors encountered during the process
have left repositories in a inconsistent state and this change allows to
recover cleanly from those situations.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

import-debian-package script now runs all the steps automatatically. The
recently added --push-remote option allows creating and pushing the
imported package to apertis remote gitlab instance.

Document the previously manual steps (performed now by the script).

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

gitlab-rulez package is now required to run import-debian-package tests.
Let's test this script on apertis, as it provides the package.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

To import a new package from Debian the current process required several
manual steps. This commit adds the --push-remote option to allow
creating and pushing the imported package to apertis remote gitlab
instance.

The following steps are now automatized:
* package folder is created and import process is performed in there.
* remote repo is created if it doesn't exist.
* remote branches and tags are pushed.
* gitlab settings are applied to remote repo.
* CI pipeline is triggered on all downstream branches.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

With the new application framework, the application bundle is now
implemented using Flatpak, so drop this functionality from ADE.
Keep the sysroot management functionality as well as the
possibility of compile standard applications like dash.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Import GitLabCI tests from `infrastructure/packaging-tools`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

As this tool is now provided as a development package we can depend on it.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Update apt repositories before call build-dep.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

These tools are moved from
`infrastructure/apertis-docker-images/package-source-builder`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

This tool is moved from `infrastructure/packaging-tools`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

By default pipelines do not run in Merge Request context, but that's
exactly what the parent ci-package-builder pipeline is now doing.

Add a rule to run the local pipeline in whatever context the parent
pipeline triggered it.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>