We're currently creating a "PackageBases" when the "restore" command is executed. This is problematic for pkgbases that never existed before. In those cases it will create the record but fail in the update.py script. Thus it leaves an orphan "PackageBases" record in the DB (which does not have any related "Packages" record(s)) Navigating to such a packages /pkgbase/... URL will result in a crash since it is not foreseen to have "orphan" pkgbase records. We can safely remove the early creation of that record because it'll be taken care of in the update.py script that is being called We'll also fix some tests. Before it was executing a dummy script instead of "update.py" which might be a bit misleading since it did not check the real outcome of our "restore" action. Signed-off-by: moson-mo <mo-son@mailbox.org> |
||
---|---|---|
.gitlab/issue_templates | ||
.tx | ||
aurweb | ||
cache | ||
conf | ||
doc | ||
docker | ||
examples | ||
LICENSES | ||
logs | ||
migrations | ||
po | ||
schema | ||
static | ||
templates | ||
test | ||
upgrading | ||
util | ||
.coveragerc | ||
.dockerignore | ||
.editorconfig | ||
.env | ||
.git-blame-ignore-revs | ||
.gitignore | ||
.gitlab-ci.yml | ||
.mailmap | ||
.pre-commit-config.yaml | ||
alembic.ini | ||
AUTHORS | ||
cliff.toml | ||
CONTRIBUTING.md | ||
COPYING | ||
docker-compose.aur-dev.yml | ||
docker-compose.override.yml | ||
docker-compose.yml | ||
Dockerfile | ||
INSTALL | ||
logging.conf | ||
logging.prod.conf | ||
logging.test.conf | ||
poetry.lock | ||
pyproject.toml | ||
pytest.ini | ||
README.md | ||
renovate.json | ||
setup.cfg | ||
TESTING |
aurweb
aurweb is a hosting platform for the Arch User Repository (AUR), a collection
of packaging scripts that are created and submitted by the Arch Linux
community. The scripts contained in the repository can be built using makepkg
and installed using the Arch Linux package manager pacman
.
The aurweb project includes
- A web interface to search for packaging scripts and display package details.
- An SSH/Git interface to submit and update packages and package meta data.
- Community features such as comments, votes, package flagging and requests.
- Editing/deletion of packages and accounts by Trusted Users and Developers.
- Area for Trusted Users to post AUR-related proposals and vote on them.
Directory Layout
aurweb
: aurweb Python modules, Git interface and maintenance scriptsconf
: configuration and configuration templatesstatic
: static resource filestemplates
: jinja2 template collectiondoc
: project documentationpo
: translation files for strings in the aurweb interfaceschema
: schema for the SQL databasetest
: test suite and test casesupgrading
: instructions for upgrading setups from one release to another
Documentation
What | Link |
---|---|
Installation | INSTALL |
Testing | test/README.md |
Git | doc/git-interface.txt |
Maintenance | doc/maintenance.txt |
RPC | doc/rpc.txt |
Docker | doc/docker.md |
Links
-
The repository is hosted at https://gitlab.archlinux.org/archlinux/aurweb -- see CONTRIBUTING.md for information on the patch submission process.
-
Bugs can (and should) be submitted to the aurweb bug tracker: https://gitlab.archlinux.org/archlinux/aurweb/-/issues/new?issuable_template=Bug
-
Questions, comments, and patches related to aurweb can be sent to the AUR development mailing list: aur-dev@archlinux.org -- mailing list archives: https://mailman.archlinux.org/mailman/listinfo/aur-dev
Translations
Translations are welcome via our Transifex project at
https://www.transifex.com/lfleischer/aurweb; see doc/i18n.txt
for details.
Testing
See test/README.md for details on dependencies and testing.