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…
* 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.
A new release of mkinitcpio has been tagged. The release can be downloaded from
GitLab:
https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/releases/v33
Changes since the previous release:
Announcements:
* Development has moved to the Arch Linux GitLab instance. The new
URL is https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio
Changes in mkinitcpio:
* Introduce DECOMPRESS_MODULES in mkinitcpio.conf. Allows the user to
toggle if modules should be recompressed during initramfs creation or
not. Defaults to "yes".
* Support UKI generation on AArch64.
* Introduce a new --remove switch which allows mkinitcpio to remove all
mkinitcpio generated files. Only works together
with the -p/-P switches currently.
* In the initramfs the file /etc/os-release, symlinked to
/etc/initrd-release, is now included. systemd enabled initramfs
environments might need this file.
* Supports finding kernel version in gzipped non-x86 kernels.
* Try to properly resolve symlinks when adding files into the initramfs.
Changes in hooks:
* install/fsck now includes the e2fsck binary and symlinks fsck.ext*
utilities to this binary.
* install/fsck will no longer attempt to include nonexistent fsck
helpers.
* install/kms will attempt to include modules that implement the privacy
screen feature. Currently the module names are hardcoded.
Changes in packaging:
* mkinitcpio-remove and mkinitcpio-install are now unified into a single
script installed to 'libalpm/scripts/mkinitcpio'.
Contributions from: 0x7F, Felix Yan, Hugo Osvaldo Barrera,
Morten Linderud, nl6720, rogueai, Simon Brüggen, Tobias Powalowski
– 2022-11-20
Hi all,
the next meeting for repod will take place on 2022-11-23 19:30 UTC.
https://meet.jit.si/20221123-repod
NOTE: This is later than usual and will likely stay like this, as we are
trying to accomodate people in more timezones!
Best,
David
--
https://sleepmap.de
Hi all,
here are the meeting minutes from today's repod meeting in rendered
form: https://md.archlinux.org/s/eGuBZ71fJ
The raw markdown below:
# 2022-11-10 repod meeting
Date: 2022-11-10T18:00:00Z - 19:00:00Z
Location: Jitsi
Scribe: dvzrv
## Attendees
* dvzrv
* polyzen
* wCPO
## Agenda
## Check package metadata against filename
The metadata of added packages is now also validated against their
filenames
[!132](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/132).
## Fix flaky file detection
Our use of python-magic has been adapted to work around flaky behavior
of the file library when it comes to detection of compressed files
[!134](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/134).
## Remove symlinks on updating packages
The binary package and management repository symlinks for packages and
pkgbases are now removed when updating packages
[!135](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/135).
## Check stability flow (per repository)
The stability flow of repositories is now honored (versions of packages
per repository must follow staging > testing > stable)
[!136](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/136).
## Archiving
Work has started on implementing archiving in repod
[#96](https://gitlab.archlinux.org/archlinux/repod/-/issues/96), to
allow configurable locations (globally and per repository) for archiving
the package files (and their signatures) when they are being added to a
repository successfully.
## Further tickets added for dbscripts feature compatibility
Short meeting with Levente to talk about existing [features and checks
in dbscripts](https://gitlab.archlinux.org/archlinux/repod/-/issues/96)
which led to more tickets for the 0.3.0 milestone:
* to ensure unique packages in a group of repositories, we need to
implement a configurable grouping functionality for repositories
[#149](https://gitlab.archlinux.org/archlinux/repod/-/issues/149)
(overlaps with how archiving works)
* to ensure that we packages can be reproducible, we want to ensure that
they have been built with packages currently in a group of
repositories, with a set of packages about to be added in the same
action or with packages that are now in the archive
[#150](https://gitlab.archlinux.org/archlinux/repod/-/issues/150)
(overlaps with grouping to detect which repositories should be
evaluated).
* for ensuring that a package version has been built using a specific
upstream source repository, we need to check git tags (and their
signatures), checksums and metadata of PKGBUILDs to match the given
binary package's metadata
[#151](https://gitlab.archlinux.org/archlinux/repod/-/issues/151).
This will requirea git backend, which can hopefully later be reused
for the management repository backend. Overlaps with
[#118](https://gitlab.archlinux.org/archlinux/repod/-/issues/118) and
[#120](https://gitlab.archlinux.org/archlinux/repod/-/issues/120).
## Documentation improvement (beginner friendly)
There are some easy first tickets:
* figure out and document differences between existing projects used for
repository management
[#148](https://gitlab.archlinux.org/archlinux/repod/-/issues/148)
* document sought after workflow scenarios
[#144](https://gitlab.archlinux.org/archlinux/repod/-/issues/144)
* configurable enforcement of UID domain
[#92](https://gitlab.archlinux.org/archlinux/repod/-/issues/92) (helps
us to maintain signer trust via WKD)
Best,
David
--
https://sleepmap.de
Hi all,
the next meeting for repod will take place on jitsi on 2022-11-10
18:00UTC.
https://meet.jit.si/20221110-repod
NOTE: This is a Thursday, whereas usually it is a Wednesday!
Best,
David
--
https://sleepmap.de