Hey! Missed the meeting yesterday as it collided with SUSECON Online and openSUSE stuff but have read the logs now, and will try to attend next time
On 6/8/22, Brett Cornwall <ain...@archlinux.org> wrote: > Formatted minutes can be viewed here: > > https://md.archlinux.org/s/HDtd8_C0z > > > > > Raw markdown (Still waiting for an angel to come down and tell me about > markdown conversion to plain text with inline url markers!): > > > > # 2022-06-08 repod meeting > > Date: 2022-06-08T17:00:00Z - 19:20:00Z > Location: Jitsi > Scribe: Brett (ainola/brett) > > ## Attendees > > * artafinde > * brett > * dvzrv > > ## Agenda > > ### macOS build environment > > * pyalpm needed but cannot install on macOS > > * makepkg fails to build in brew due to fakeroot failing to build > > ### Refactoring models > > Huge refactoring for models and some helper functions > ([#39](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/39)) > > * Lots of regexes added to models for validation. Accompanying tests > added. > > * Static analysis isn't necessary because of fixtures > > * Documentation of testing in CONTRIBUTION.md > > * Defaults are set for models > > * PKGINFO schema/parser is the last remaining item > > ([#53](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/39)) > > ### Python pinning > > * This morning saw master branches fail building without any changes due > to Python 3.10.5 making it to `[core]`. > > * Python version pinning not desirable/easy, issues will be handled as > they come. > > ### python-magic > > New dep added for python-magic; the version of python-magic in the Arch > repos does not exist on PyPi, making installation confusing. The Arch > package even points to [file(1)'s homepage](https://darwinsys.com/file/). > > ### Distro agnosticism > > A few members were under the mistaken impression that `repod` was > intending to become a general-purpose project that is distro-agnostic, > i.e. `apt`, `dnf`, `pacman`, et al could be serviced with `repod`. This > is not the case! > > * `repod`'s Python-based runtime should be able to run on any > distribution > > * `repod` is only designed to service pacman-based packages > > * All Arch Linux-based derivatives (i.e. any distro that utilizes > pacman) will be able to use this software. > > It's likely that the confusion came from an off-hand comment some weeks > ago regarding distro-agnosticism. The project README is pretty clear: > >>This project contains tooling to maintain binary package repositories >>for Linux distributions using the pacman package manager. > > It's *possible* for other package managers to add their support here but > it's not a goal of the project. > > ### Funding > > Prototype Fund sadly did not work out. > However, two applications for [NLnet](https://nlnet.nl/) have also been > sent in. > > ### Announcing repod to forks > > Support for multiple architectures is an important future goal for Arch > Linux, and we should strive to e.g. incorporate external ARM efforts > into Arch Linux. > > Other [Arch based > distributions](https://wiki.archlinux.org/title/Arch-based_distributions) > might also be interested in collaborating with repod since they may end > up deploying their own copy of it. > > ### Action items > > * Figure out how [python-magic](https://pypi.org/project/python-magic/) > is to be packaged so it doesn't conflict with the current package > and/or make repod compatible with file's python-magic and python-magic > > * Research all of the notable Arch-based distributions (distrowatch > seems a decent-enough overview of popularity) and contact them about > collaboration with repod: > > * Which ones have their own build automation vs how many directly > use Arch's repositories? (i.e. which distributions would be > interested in collaborating with us on repod to make all of our > lives easier?) > > * Draft up communications for these distributions: Our goal is to > introduce repod/our packaging vision and to solicit their > feedback/help on the project itself. >
