dbscripts merge requestshttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests2018-02-15T15:41:44Zhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/1bash cleanup: coding style2018-02-15T15:41:44ZJelle van der Waabash cleanup: coding style*Created by: eli-schwartz*
Use modern bash where possible, streamline some control flow issues, and fix a small bug in `check_repo_permission()` while I'm at it.*Created by: eli-schwartz*
Use modern bash where possible, streamline some control flow issues, and fix a small bug in `check_repo_permission()` while I'm at it.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/2Remove i686 from config2018-02-15T16:18:37ZFlorian PritzRemove i686 from configWe dropped it long ago and this should be reflected here rather than
being changed on our servers only.
Signed-off-by: Florian Pritz <bluewind@xinu.at>We dropped it long ago and this should be reflected here rather than
being changed on our servers only.
Signed-off-by: Florian Pritz <bluewind@xinu.at>https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/4Do real checks against the possible file extensions of a pkgfile2018-02-22T17:12:13ZJelle van der WaaDo real checks against the possible file extensions of a pkgfile*Created by: eli-schwartz*
See various discussion around https://lists.archlinux.org/pipermail/arch-projects/2018-February/004746.html and https://lists.archlinux.org/pipermail/arch-projects/2018-February/004748.html
It may make sens...*Created by: eli-schwartz*
See various discussion around https://lists.archlinux.org/pipermail/arch-projects/2018-February/004746.html and https://lists.archlinux.org/pipermail/arch-projects/2018-February/004748.html
It may make sense to add some version of https://lists.archlinux.org/pipermail/arch-projects/2018-February/004794.html in after the second commit.
@LukeShuhttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/6Misc touchup2018-03-16T04:17:51ZJelle van der WaaMisc touchup*Created by: eli-schwartz*
From @LukeShu
The interesting bits are proper glob handling, and better handling of error cases e.g. in repo-add. I've added a commit to unify the repo-add/repo-remove caller in order to facilitate using th...*Created by: eli-schwartz*
From @LukeShu
The interesting bits are proper glob handling, and better handling of error cases e.g. in repo-add. I've added a commit to unify the repo-add/repo-remove caller in order to facilitate using the same path escape/quoting style for the db as well as for packages.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/7Improve README documentation2018-04-03T01:53:51ZJelle van der WaaImprove README documentation*Created by: LukeShu*
- Fix spelling mistake: "overriden"->"overridden"
- Write an overview of the programs included, to give someone an idea of what they're looking at*Created by: LukeShu*
- Fix spelling mistake: "overriden"->"overridden"
- Write an overview of the programs included, to give someone an idea of what they're looking athttps://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/5Backports from Parabola2018-04-10T00:42:24ZJelle van der WaaBackports from Parabola*Created by: LukeShu*
These are commits from Parabola's dbscripts that I think are
upstreamable. No real theme to them, but because some of them are
wide-sweeping (eg. clean up quoting), they are a good base layer to
apply before ba...*Created by: LukeShu*
These are commits from Parabola's dbscripts that I think are
upstreamable. No real theme to them, but because some of them are
wide-sweeping (eg. clean up quoting), they are a good base layer to
apply before backporting other changes.
I've done my best to look over them, but at least one weird thing did
happen while rebasing them, so it's possible I missed something that
rebased weird.
Some of this duplicates (non-backported) changes in the last patchset
I submitted.
This is currently v2 of the patchset. v1 was submitted on the mailing list. I'm submitting v2 here to get a shiny little confirmation from Travis that I didn't break anything; I'm submitting it to the mailing list as well.
https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/8Unbreak the testsuite by supporting pacman 5.12018-06-19T20:04:11ZJelle van der WaaUnbreak the testsuite by supporting pacman 5.1*Created by: eli-schwartz*
@pierres Is there a particular reason this was initially done via tmpfs?
Note that the specific error condition there will no longer be triggered by pacman 5.1.1 whenever that lands, but I still consider i...*Created by: eli-schwartz*
@pierres Is there a particular reason this was initially done via tmpfs?
Note that the specific error condition there will no longer be triggered by pacman 5.1.1 whenever that lands, but I still consider it sort of bad practice (plus I want to more closely mimic makechrootpkg itself). AFAICT docker creates a new container each time regardless.
If it's especially useful to ensure the /build directory is not persisted between runs (efficiency? I don't know enough about how docker works) I think it makes more sense to use `makepkg --clean` in the testsuite itself.https://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.https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/9test: Fix typoed variables2018-07-04T02:05:21ZJelle van der Waatest: Fix typoed variables*Created by: LukeShu*
- ftpdir-cleanup: ${pkg[0]} -> ${pkgs[0]}
This mistake was introduced in 7628525156110022fa70ad91e4bc13ee8a3cceb0
- test: common.bash: $pkgarches[@] -> ${pkgarches[@]}
This mistake was introduced i...*Created by: LukeShu*
- ftpdir-cleanup: ${pkg[0]} -> ${pkgs[0]}
This mistake was introduced in 7628525156110022fa70ad91e4bc13ee8a3cceb0
- test: common.bash: $pkgarches[@] -> ${pkgarches[@]}
This mistake was introduced in 7628525156110022fa70ad91e4bc13ee8a3cceb0
This is identical to v2 of this patch posted on the mailing list https://lists.archlinux.org/pipermail/arch-projects/2018-June/004915.htmlhttps://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/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/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/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/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/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/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/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/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/31Enable shellcheck in CI2021-11-19T20:07:22ZJelle van der WaaEnable shellcheck in CIhttps://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.