- Arch-projects - lists.archlinux.org

[repod] 2022-12-07 meeting minutes
by Brett Cornwall 07 Dec '22

07 Dec '22

Rendered markdown at https://md.archlinux.org/s/edXOVFGbE Unrendered/raw markdown: # 2022-12-07 repod meeting Date: 2022-12-07T19:30:00Z Location: Jitsi Scribe: brett ## Attendees * alad * artafinde * brett * dvzrv * isaac * lobachevsky * wCPO ## Agenda ### Git and PGP * Evaluating which Git/PGP integration for signing and signature checking to use ([#155](https://gitlab.archlinux.org/archlinux/repod/-/issues/155)). Current ecosystem is not ideal, so finding the "best" solution is difficult. * Ideally a separate service would run alongside repod that would be able to sign * Shelling out to gpg/git commands not ideal since repod integration would be awkward due to output parsing (gpg is particularly awful). * Getting Git integration is more important than GPG integration right now. ### Updating dependencies * Still no integration for renovatebot; It does not parse pyproject.toml (it only integrates into poetry). * Update of mypy was difficult. ### Grouping of repositories Can now add a group number to repositories! Groups must have unique packages in that group and will reject package uploads if that is violated. ### Manpage improvements * Readability of manpages have been improved. ([#153](https://gitlab.archlinux.org/archlinux/repod/-/issues/153)). * Lots of options are exposed and more are coming! Considering grouping the options for better navigation. * Usage of equals sign after the options confused an attendee; It's not a very common pattern but adopted by other projects like systemd. ### Module refactoring Some models are now being used across modules, so work was done to combine them into `common/models.py` Regex verification of package values (`common/regex.py`) not compiled into a regex object: This is a possible improvement if it's do-able. ### Funding Still no funding. Prototype fund didn't pan out. Still waiting for reply from Internet Fund. Valve still hasn't replied. ### Talk at Hacking in Parallel (HIP) https://hip-berlin.de/ December 27-30 2022 in Berlin. Tickets are sold out but dvzrv will be giving a talk: "Pacman can have the cookies and eat the ghosts too" Schedule to be released shortly. All talks on the stages can be recorded and streamed via media.ccc.

1 0

[repod] Next meeting: 2022-12-07 19:30 UTC
by David Runge 03 Dec '22

03 Dec '22

Hi all, the next meeting for repod will take place on 2022-12-07 19:30 UTC. https://meet.jit.si/20221207-repod Best, David -- https://sleepmap.de

1 0

[repod] 2022-11-23 meeting minutes
by Brett Cornwall 23 Nov '22

23 Nov '22

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.

1 0

mkinitcpio v33 released
by Morten Linderud 21 Nov '22

21 Nov '22

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

2 1

[repod] 2022-11-23 19:30 UTC
by David Runge 17 Nov '22

17 Nov '22

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

1 0

[repod] 2022-11-10 meeting minutes
by David Runge 10 Nov '22

10 Nov '22

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

1 0

[repod] Next meeting: 2022-11-10 18:00 UTC
by David Runge 07 Nov '22

07 Nov '22

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

1 0

[repod] 2022-10-26 meeting minutes
by David Runge 26 Oct '22

26 Oct '22

Hi all, here are the meeting minutes from today's meeting (in rendered form): https://md.archlinux.org/s/nqqUhLHQ6 Below the plain markdown version: ``` # 2022-10-26 repod meeting Date: 2022-10-26T17:00:00Z - 18:00:00Z Location: Jitsi Scribe: dvzrv ## Attendees * dvzrv * prawn * polyzen * wCPO ## Agenda ### Community outreach We sent [a mail](https://lists.archlinux.org/archives/list/arch-dev-public@lists.archl… about the internal Arch Linux projects and got one contributor in return! \o/ ### Fixing flaky tests that are flaky Took only three(!) merge requests to finally fix a flaky test... ### Write empty sync databases for empty repositories We are now able to also write empty sync databases for empty repositories [!125](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/125) and [!127](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/127). ### Refactor CLI module The CLI now does not use Tasks and Checks directly anymore, but instead relies upon functions from the `repod.action.workflow` module [!126](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/126). ### Import in bulk in integration tests Circumvent an issue with "newer/ already existing" packages in integration tests, by importing in bulk instead [!128](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/128). ### Use schema_version throughout the codebase We now use `schema_version` for the versioning of objects everywhere [!129](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/129) (thanks Isaac!). ### Track source URL per pkgbase in management repository We are now able to track source URLs (the location where package sources live) per pkgbase. This allows for configuration of a specific set of allowed URLs against which a new package's URL must match [!130](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/130). Existing URLs in the management repository are reused if none are provided. In the future we want to also allow updating/ changing the URL separately from a package addition. ### Use debug repositories per stability layer We can now define debug repositories per stability layer (stable, staging, testing) for each repository [!133](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/133). This allows to have a correct handling of debug packages per repository and the moving of packages between repositories. ### Check filename against contained metadata Work has started to check whether the filename of a given consumed file matches the metadata retrieved from it (e.g. `foo-1:1.0.0-1-any.pkg.tar.zst`) [!132](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/132). ### Outstanding milestone 0.3.0 work * The communication with e.g. forges (with or without APIs), providing package sources ([#120](https://gitlab.archlinux.org/archlinux/repod/-/issues/120) and [#118](https://gitlab.archlinux.org/archlinux/repod/-/issues/118)) needs investigation. Help is much appreciated! * Workflows for further actions need to be defined (e.g. remove [140](https://gitlab.archlinux.org/archlinux/repod/-/issues/140) and move [#141](https://gitlab.archlinux.org/archlinux/repod/-/issues/141)) and implemented. Investigating good approaches and the required checks when moving/removing is much appreciated! * Ensure that a repository is self-contained [#142](https://gitlab.archlinux.org/archlinux/repod/-/issues/142) and make this configurable (can already be hooked into existing "add packages" workflow and is a fairly easy topic). * The workflows need to be extended/ adapted to support bulk actions across repositories (e.g. "move 10 packages from testing to core and 20 packages from community-testing to community in one action") [#145](https://gitlab.archlinux.org/archlinux/repod/-/issues/145), but we currently only support bulk actions per-repository (e.g. "add these 20 packages to that repository"). To deal with this in a sane manner, we need someone to investigate how to do this via the CLI (maybe even define a separate plaintext file input format, defining sources and targets - e.g. what was discussed in https://md.archlinux.org/s/mH-Nb_oOD). * Documentation documentation documentation [#144](https://gitlab.archlinux.org/archlinux/repod/-/issues/144) ``` Best, David -- https://sleepmap.de

1 0

Re: Notification: Arch Linux Repod Meeting @ Wed Oct 26, 2022 (droidbittin@gmail.com)
by Luna Jernberg 25 Oct '22

25 Oct '22

Alright, sorry On Tue, Oct 25, 2022 at 2:19 PM David Runge <dave(a)sleepmap.de> wrote: > > On 2022-10-25 12:24:05 (+0200), Luna Jernberg wrote: > > Hey! > > > > Will miss the repod meeting tomorrow, as it collides with foss-sthlm > > October meetup here in Stockholm: https://foss-sthlm.se/ > > > > On Wed, Oct 19, 2022 at 9:00 AM Google Calendar < > > calendar-notification(a)google.com> wrote: > > > > > Arch Linux Repod Meeting > > > You have been invited by droidbittin(a)gmail.com to attend an event named > > > Arch Linux Repod Meeting on Wednesday Oct 26, 2022. > > > > > > You have an upcoming event > > > > > > Arch Linux Repod Meeting > > > Wednesday Oct 26, 2022 > > > Organizer > > > droidbittin(a)gmail.com > > > Guests > > > View all event details > > > <https://calendar.google.com/calendar/event?action=VIEW&eid=Nm5hYThpOWRidjV1…> > > > > > > Invitation from Google Calendar <https://calendar.google.com/calendar/> > > > > > > You are receiving this email because you are subscribed to calendar > > > notifications. To stop receiving these emails, go to Calendar settings > > > <https://calendar.google.com/calendar/r/settings>, select this calendar, > > > and change "Other notifications". > > > > > > Forwarding this invitation could allow any recipient to send a response to > > > the organizer, be added to the guest list, invite others regardless of > > > their own invitation status, or modify your RSVP. Learn more > > > <https://support.google.com/calendar/answer/37135#forwarding> > > > > > Hey Luna, > > as already mentioned by Brett [1], please abstain from sending these > types of notifications. They create unnecessary traffic on the mailing > lists and in this case even created a new topic. > > If you'd like to attend to the meeting, please just join. There is no > need to let anyone know about your absence or attendance. > > Best, > David > > [1] https://lists.archlinux.org/archives/list/arch-projects@lists.archlinux.org… > > -- > https://sleepmap.de

1 0

[repod] Next meeting: 2022-10-26 19:00 CEST
by David Runge 25 Oct '22

25 Oct '22

Hi all, the next meeting for repod will take place on jitsi on 2022-10-26 19:00CEST. https://meet.jit.si/20221026-repod Best, David -- https://sleepmap.de

1 0