please find the meeting minutes in rendered form here:
The plain markdown is attached below:
# 2022-08-31 repod meeting
Date: 2022-08-31T17:00:00Z - 2022-08-31T18:30:00Z
## Endeavor OS
- sradjoker from Endeavor OS is describing their setup
- uses own tooling (e.g. Makefile/ scripts based) to maintain packages
- most packages are reused from Arch Linux / Arch Linux ARM
- confused by initial use/ what to expect from repod. adding further
high level information might help first-time users
## Demo by David
David demoed importing a package and how the file structure is created.
David presented the current milestone:
## Evaluate the minimum base set of package attributes
We need to evaluate whether the base set of package attributes needs to
Packagers with very limited/ small setups may otherwise run into issues.
In the future the existence requirement for the various attributes could
please find the rendered meeting minutes here:
The raw markdown below:
# 2022-08-16 repod meeting
Date: 2022-08-16T17:00:00Z - 2022-08-16T
### Milestone 0.2.0
* Create integration for downstream packagers
* More DB/data management
* Rudimentary PGP verification with pacman-key
* Multi-arch improvements
* New fields in the JSON output
* installed packages while building the package
* other system states while package was built
* repod will now complain when not specifying an arch when arch is ambiguous
* A few bugs left to iron out in current MRs
### Future version goals
* Cleanup in management repo logic
* Workflow scenarios
* Group package actions
* Git backend work
* Decide between using plain Git vs the frameworks available to us
* Signed package repo DBs
## Pacman changes
A few internal Pacman changes have caused a little bit of needed reworking.
please find the rendered meeting minutes here: https://md.archlinux.org/s/vyKfwOzzY#
The raw markdown below:
# 2022-08-03 repod meeting
### 0.2.0 Milestone
The [0.2.0 milestone](https://gitlab.archlinux.org/archlinux/repod/-/milestones/1#tab-… needs:
* Consolidation of the management repositories
* More mtadata parsing/management (#20) (#39)
* Debug repositories
* BUILDINFO v2
* Using sha256sum to make checking out pkgbuilds easier
### Debug repositories
The feature for tracking debug repositories of package repositories has
It is now possible to target the debug repository of a package
repository (e.g. move data of consumed package to respective directory
in the management repository layout).
### .BUILDINFO data in management repository
Work has started for adding relevant .BUILDINFO data to the management
the change is fairly trivial, adapting tests to cover this is more
### Source URL tracking in management repository
A ticket [#39](https://gitlab.archlinux.org/archlinux/repod/-/issues/39)
in the current milestone concerns itself with the tracking of the
upstream source URL (the version controlled upstream of the PKGBUILD
from which a given pkgbase has been built). It still needs further
discussion and refinement, as the workflow around this feature is not
### Checks on package consumption
The checks done on package consumption by dbscripts are currently not
translated or implemented by repod. Levente has promised to look into
this to create tickets for repod which will track the checks required
during package consumption.
### Sphinx improvements
Polyzen offered to look into sphinx related documentation improvements
and [#78](https://gitlab.archlinux.org/archlinux/repod/-/issues/78)) in
the current milestone.
### Thoughts on current and future design
While the current milestone concerns itself with the consolidation of
management and package repository data and actions, the upcoming
milestone is about implementing a git-based backend for the management
Changes in the current milestone (e.g.
upcoming changes in pacman (making `pgpsig` a non-required field in the
sync databases) show, that it will not be possible to retain the current
functionality of allowing a roundtrip from sync database to management
repository and back to sync database, as the sync database will not
contain all the data required for the management repository anymore.
Dvzrv did a code walkthrough of the current repository, outlining the
various functionality contained in it.
A short example of importing a package file into the directory structure
maintained by repod has been show-cased as well.
Q: "Is the plan to use git instead of subversion for packages?""
A: Yes, the eventual plan is to move package build sources and package
repository state management to gitlab.archlinux.org.