This ticket is supposed to document the already established workflows that have been elaborated on. Unfortunately the tooling is not ready for them yet, which makes their place in user facing documentation a problem. Hence I'm moving them here, so they can be worked on again once the tooling has gained more features to even support these workflows: Packager Workflows __________________ In this section the different workflows are listed, to give an overview, what they would mean in the different git repository layouts. Adding a Package ================ **Developer machine/ build server**: 1. Create repository 1. Update, build *package* and commit changes in *package*'s `PKGBUILD`_ 1. Tag release .. note:: Force pushing tags is disallowed. 1. Sign *package* 1. Upload built *package* and signature 1. Call application on repository/ package server to add *package* **Repository server/ package server**: .. important:: The following steps need to be atomic (reversible). 1. Verify user permissions https://gitlab.archlinux.org/archlinux/repod/-/issues/26 1. Verify that an upstream URL is provided for any new `pkgbase` https://gitlab.archlinux.org/archlinux/repod/-/issues/39 1. Lock repository sync databases and management repository https://gitlab.archlinux.org/archlinux/repod/-/issues/117 1. ~~Inspect built files of *package*~~ 1. Lock tags (by storing them in *package*'s bare repository) @heftig @alad @maximbaz (please clarify what this means) 1. ~~Modify management repo to reflect changes~~ 1. Verify *package* file versioning and tag is consistent https://gitlab.archlinux.org/archlinux/repod/-/issues/118 1. ~~Copy built *package* and signature to pool and create symlink to them in target repository~~ 1. ~~Add *package* to the package database~~ 1. Unlock repository sync databases and management repository https://gitlab.archlinux.org/archlinux/repod/-/issues/117 Updating a Package ================== All steps, but the first, of **Developer machine/ build server** in `Adding a Package`_ apply. All steps of **Repository server/ package server** in `Adding a Package`_ apply. 1. Verify user permissions https://gitlab.archlinux.org/archlinux/repod/-/issues/26 1. Lock repository sync databases and management repository https://gitlab.archlinux.org/archlinux/repod/-/issues/117 1. ~~Inspect built files of *package*~~ 1. Lock tags (by storing them in *package*'s bare repository) @heftig @alad @maximbaz (please clarify what this means) 1. ~~Modify management repo to reflect changes~~ 1. Verify *package* file versioning and tag is consistent https://gitlab.archlinux.org/archlinux/repod/-/issues/118 1. ~~Copy built *package* and signature to pool and create symlink to them in target repository~~ 1. ~~Add *package* to the package database~~ 1. Remove symlinks and files of previous versions of package(s) https://gitlab.archlinux.org/archlinux/repod/-/issues/107 1. Unlock repository sync databases and management repository https://gitlab.archlinux.org/archlinux/repod/-/issues/117 Removing a Package ================== **Developer machine/ build server**: 1. Call application on repository/ package server to remove *package* **Repository server/ package server**: .. important:: The following steps need to be transactional (reversible). .. note:: The remove command should be able to remove stale packages (e.g. leftover packages, when removing a member of a split package) 1. Verify user permissions https://gitlab.archlinux.org/archlinux/repod/-/issues/26 1. Lock repository sync databases and management repository https://gitlab.archlinux.org/archlinux/repod/-/issues/117 1. ~~Modify monorepo to reflect changes~~ 1. ~~Remove *package* from the package database~~ 1. Remove built *package* and signature from pool and remove symlink to them in target repository https://gitlab.archlinux.org/archlinux/repod/-/issues/107 1. Unlock package database and monorepo https://gitlab.archlinux.org/archlinux/repod/-/issues/117 Moving a Package ================ **Developer machine/ build server**: 1. Call application on repository/ package server to move *package* **Repository server/ package server**: .. important:: The following steps need to be transactional (reversible). 1. Verify user permissions https://gitlab.archlinux.org/archlinux/repod/-/issues/26 1. Lock repository sync databases and management repository https://gitlab.archlinux.org/archlinux/repod/-/issues/117 1. ~~Modify management repo(s) to reflect changes~~ 1. Remove *package* from the source package database (write to tmp location) https://gitlab.archlinux.org/archlinux/repod/-/issues/105 1. Add *package* to the destination package database (write to tmp location) https://gitlab.archlinux.org/archlinux/repod/-/issues/105 1. Remove symlinks to package and signature files from source repository https://gitlab.archlinux.org/archlinux/repod/-/issues/107 1. ~~Add symlinks to package and signature them to the target repository~~ 1. Unlock source and target package databases and management repo https://gitlab.archlinux.org/archlinux/repod/-/issues/117 .. _PKGBUILD: https://man.archlinux.org/man/pacman/PKGBUILD.5.en