We check if there is a debug package found in the mirroring debug
repository and mark this as `is_debug` if found. This creates the needed
symlinks for the package pool.

Signed-off-by: Morten Linderud <morten@linderud.pw>

Signed-off-by: Morten Linderud <morten@linderud.pw>

We check if there is a globfile match for a debug package when removing
the package from the main repository.

This also adds a guard to the usual package removal, and removing an
unused variable.

Signed-off-by: Morten Linderud <morten@linderud.pw>

Internally this uses db-move, so this should just do the correct thing.

Signed-off-by: Morten Linderud <morten@linderud.pw>

Signed-off-by: Morten Linderud <morten@linderud.pw>

This ensures we do not have the debug repository at hand when looking at
the SVN state files. However, there is no good way to figure out if we
have a debug package as .BUILDINFO nor .PKGINFO has the information we
need.

We blindly assume that any package where we look up a *-debug repository
is a debug package.

Signed-off-by: Morten Linderud <morten@linderud.pw>

The gist of this change is to always peak into the DEBUGPKGPOOL and
ensure if a ${pkgbase}-debug exists in the debug repository.

Signed-off-by: Morten Linderud <morten@linderud.pw>

Signed-off-by: Morten Linderud <morten@linderud.pw>

We simply remove the -debug prefix if present and ensure we are checking
the SVN repository for the PKGBUILD in the actual repository.

Signed-off-by: Morten Linderud <morten@linderud.pw>

Signed-off-by: Morten Linderud <morten@linderud.pw>

Signed-off-by: Morten Linderud <morten@linderud.pw>

Signed-off-by: Morten Linderud <morten@linderud.pw>

Eli Schwartz authored Mar 14, 2021 and Morten Linderud committed Nov 20, 2021

These are not debug prints, don't stick them in the same commit...

Useful to specify a specific test to run during development/debugging.

db-move: Clarify error message when the specified repo isn't correct for the current dbscripts instance

It's not entirely clear what a "configured repository" is, but hopefully
saying that the given repo isn't a "valid repository" is clearer.

In typical use this will result in an error like this:

    ==> ERROR: extra is not a valid repository for /community/db-move

or this:

    ==> ERROR: community-testing is not a valid repository for /packages/db-move

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Johannes Löthberg authored Oct 01, 2021 and Jelle van der Waa committed Oct 26, 2021

Otherwise if you use the dbscripts for core/extra for community repos,
or vice versa, you'll get an error saying that you don't have
permissions to move packages from or to the given repositories, which
can be confusing if you don't immediately notice your mistake.

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Used with GitLab's test coverage visualization[1] and test coverage
results[2].

[1] https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html
[2] https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request

travisci is no longer used.

This makes it possible to run the tests with podman which has the
benefit of requiring no daemon.

Morten Linderud authored Apr 27, 2021 and Jelle van der Waa committed Oct 17, 2021

We are currently deploying a bunch of AGPL3 software in our devops team
and all the source for the should be available to meet license
requirements.

This is a "hack" so we can access the sources from our Arch Linux
ftpdir.

Signed-off-by: Morten Linderud <morten@linderud.pw>

Luke Shumaker authored Apr 03, 2021 and Jelle van der Waa committed Oct 17, 2021

I hereby confirm that I license my work on dbscripts under the
GPLv2-or-later.

Kristian Klausen authored Jun 23, 2021 and Eli Schwartz committed Jun 23, 2021

All the arch-x@archlinux.org -> arch-x@lists.archlinux.org aliases will
be dropped soon[1].

[1] https://lists.archlinux.org/pipermail/arch-dev-public/2021-June/030462.html



Signed-off-by: Eli Schwartz <eschwartz@archlinux.org>

The official image switched names from "base" to "archlinux".

BUILDDIR is a testsuite requirement, cases might be set manually

Or else it doesn't work if you have packages installed but not from a repo

We tried to optimize out checking packages which aren't even split
packages, by skipping the ones with no pkgbase. But pacman 5.1 always
writes the pkgbase in order to simplify parsing of the .PKGINFO, so this
was no longer reliable. Instead, check how many pkgnames are in the
corresponding PKGBUILD. This is the master source of truth anyway.

Further contributions will need to be consistent with this, and now we
need to hunt down the remaining contributors and clarify the license
status. Fun!

Signed-off-by: Eli Schwartz <eschwartz@archlinux.org>