Link to formatted notes: https://md.archlinux.org/s/7sRUcSzjC Raw notes in markdown: # 2022-11-23 repod meeting Date: 2022-11-23T19:30:00Z Location: Jitsi Scribe: brett ## Attendees * brett * dvzrv * prawn * yitz ## Agenda ### Archiving * Not much documentation yet, but some info available in manpage * Functions similarly to db-scripts at the moment * Source tarball archiving/handling is not implemented yet * Plan to continue using archive.org as long-term package archival * Current archive.org archival is a separate [detached process](https://gitlab.archlinux.org/archlinux/archivetools); It's unlikely (though still possible) that repod will handle this archival. ### Build requirements check * Checks if packages in archive are around and their specific version * Allows us to only add packages that are reproducible * manpage readability could be improved * Error handling in task/do functions also needs improvement * Better formatting than a runtime error desirable * This would improve accessibility to development/usage ### Mypy and dependency updates * Pip dropped as a direct dependency; Now an implicit dependency * Used to produce bizarre error messages when used in conjunction with poetry * pdm.lock file needs manual updating at the moment (can't even update metadata) due to [missing features](https://github.com/renovatebot/renovate/issues/10187) ### Other dependencies * Checking for existing PKGBUILDs/sha256sum (and a number of other tasks) requires Git migration * GPG pypi package woefully outdated; Mailing list is [silent/ignoring patches](https://lists.gnupg.org/pipermail/gnupg-devel/2022-November/035158.html) * pygit not desirable for use; pygit2/dulwich preferred ### Funding No funding yet - one more application in progress ### Good first issues Collaboration welcome for tackling some of the "simpler" tickets! (e.g. documentation tasks such as #154, #148 or adding checks such as #143, #142 #92) ### Project file reorganization Some of the Python source files are getting quite large and are potentially going to be split into smaller files. Even some of the smaller files can be a little difficult to grasp due to complexity/unexpected run orders.