dbscripts merge requestshttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests2021-11-20T10:58:16Zhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/32Add more test coverage and BATS_ARGS2021-11-20T10:58:16ZJelle van der WaaAdd more test coverage and BATS_ARGSUseful to specify a specific test to run during development/debugging.Useful to specify a specific test to run during development/debugging.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/31Enable shellcheck in CI2021-11-19T20:07:22ZJelle van der WaaEnable shellcheck in CIhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/30Shellcheck2021-11-19T19:35:21ZJelle van der WaaShellcheckAdd `check` target for shellcheck.Add `check` target for shellcheck.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/29db-move: Clarify error message when the specified repo isn't correct for the...2021-10-27T20:04:20ZJohannes Löthbergdb-move: Clarify error message when the specified repo isn't correct for the...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 cl...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-movehttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/28db-move: Check that the specified repositories are ones dbscripts was configu...2021-10-26T19:31:48ZJelle van der Waadb-move: Check that the specified repositories are ones dbscripts was configured forOtherwise 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 imme...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>https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/27test2021-10-19T22:07:58ZJelle van der Waatesthttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/26Add code coverage job2021-10-17T17:34:28ZKristian KlausenAdd code coverage jobUsed 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-te...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-requesthttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/25db-move: Check that the specified repositories are ones dbscripts was configu...2021-10-26T19:22:52ZJohannes Löthbergdb-move: Check that the specified repositories are ones dbscripts was configured forOtherwise 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 imme...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.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/24Update mailing list address2021-06-23T21:43:43ZKristian KlausenUpdate mailing list addressAll 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.htmlAll 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.htmlhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/23Draft: dbscripts git support2022-12-10T12:09:44ZMorten Linderudfoxboron@archlinux.orgDraft: dbscripts git supportWIP stuffWIP stuffhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/22sourceballs: Add AGPL3 to ALLOWED_LICENSES2021-10-17T12:44:00ZMorten Linderudfoxboron@archlinux.orgsourceballs: Add AGPL3 to ALLOWED_LICENSESWe 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-b...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>https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/21debug package support2021-12-16T19:32:45ZMorten Linderudfoxboron@archlinux.orgdebug package supporthttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/20Wip/debug2021-03-14T18:53:37ZMorten Linderudfoxboron@archlinux.orgWip/debugWIP branch. Rebase once stuff moves.
- [ ] `db-move` support
- [x] `db-remove` support
- [ ] Test suite coverage
This also includes a cache for the built packages. Negible improvements in test suite times but it's *something*.WIP branch. Rebase once stuff moves.
- [ ] `db-move` support
- [x] `db-remove` support
- [ ] Test suite coverage
This also includes a cache for the built packages. Negible improvements in test suite times but it's *something*.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/17Correct a typo in db-move2021-03-14T19:13:05ZFelix Yanfelixonmars@archlinux.orgCorrect a typo in db-movehttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/16config: add zst to allowed extensions2019-10-23T01:08:38ZJelle van der Waaconfig: add zst to allowed extensions*Created by: seatsea*
Since the plan is to switch to zstd, add it to the allowed extensions.*Created by: seatsea*
Since the plan is to switch to zstd, add it to the allowed extensions.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/15Verify update plus rebuild2019-01-11T15:34:29ZJelle van der WaaVerify update plus rebuild*Created by: eli-schwartz*
Perform safety checks to verify that there isn't a testing/staging rebuild in progress which will be invalidated by a db-update. This protects against the case where a Dev/TU performs a global rebuild that tou...*Created by: eli-schwartz*
Perform safety checks to verify that there isn't a testing/staging rebuild in progress which will be invalidated by a db-update. This protects against the case where a Dev/TU performs a global rebuild that touches one package in staging, and then another (the original maintainer, say) tries to update the same package but does not realize it needs to be updated for staging as well.
Also make the testing2x script slightly more useful by handling multiple testing repos. The current script was basically written with packages.git in mind alone.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/14Add reproducible archive of packages.2019-01-10T13:34:49ZJelle van der WaaAdd reproducible archive of packages.*Created by: eli-schwartz*
This partially subsumes the work of archivetools, in creating the initial `packages/${pkgname:0:1}/${pkgname}/${pkgfile}` pool every time a package is uploaded. (Archivetools only runs once per day and can mis...*Created by: eli-schwartz*
This partially subsumes the work of archivetools, in creating the initial `packages/${pkgname:0:1}/${pkgname}/${pkgfile}` pool every time a package is uploaded. (Archivetools only runs once per day and can miss things.)
And we now also test every package to make sure it can only be db-updated if the archive knows about all packages that were installed in the build environment.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/13Don't parse .db files ourselves; use pyalpm instead2018-07-26T17:23:55ZJelle van der WaaDon't parse .db files ourselves; use pyalpm instead*Created by: LukeShu*
In a patchset that I recently submitted, Eli was concerned that I was
parsing .db files with bsdtar+awk, when the format of .db files isn't
"public"; the only guarantees made about it are that libalpm can parse i...*Created by: LukeShu*
In a patchset that I recently submitted, Eli was concerned that I was
parsing .db files with bsdtar+awk, when the format of .db files isn't
"public"; the only guarantees made about it are that libalpm can parse it.
https://lists.archlinux.org/pipermail/arch-projects/2018-June/004932.html
I wasn't too concerned, because `ftpdir-cleanup` and `sourceballs` already
parse the .db files in the same way. Nonetheless, I think Eli is right: we
shouldn't be parsing these files ourselves.
So, add a `dbquery` function that uses pyalpm to parse the .db files:
- It takes as arguments Python 3 expressions;
1. one that that returns a bool deciding whether we want to print
information on a package, and
2. another that returns the string to print for a package.
Currently, all callers use "True" for the decider expression, as
ftpdir-cleanup and sourceballs operate on *every* package. However, I'm
including a way to filter packages because, I'm coming at this from the
context that I want to parse .db files in other places too.
- libalpm doesn't offer an easy way to say "parse this DB file for me";
instead, we must construct a configuration that has a syncdb pointing to
that file, which we then have it sync in to a temporary directory.
As a final note, when re-writing the bit of sourceballs to use dbquery
instead of AWK, I realized that it does not correctly handle licenses that
have a space in them (as of 2018-07-07 there are 67 packages in the Arch
repos that have license containing a space). I did not fix this bug; I
merely translated it from AWK to Python, as the program would also need to
be adjusted elsewhere.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/12Preliminary work on refactoring svn into private functions2018-10-16T16:10:02ZJelle van der WaaPreliminary work on refactoring svn into private functions*Created by: eli-schwartz*
Hopefully one step closer to the dbscripts-rewrite.
/cc @gbsf*Created by: eli-schwartz*
Hopefully one step closer to the dbscripts-rewrite.
/cc @gbsfhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/11Use arrays for filenames instead of strings split on whitespace.2018-07-04T01:54:42ZJelle van der WaaUse arrays for filenames instead of strings split on whitespace.*Created by: eli-schwartz*
Be "more proper" w.r.t. whitespace in filenames.
This should be fairly uncontroversial.*Created by: eli-schwartz*
Be "more proper" w.r.t. whitespace in filenames.
This should be fairly uncontroversial.