- Arch-projects - lists.archlinux.org

Hardcoded x86_64 in makerepropkg
by Hugo Osvaldo Barrera 17 Oct '22

17 Oct '22

`makerepropkg` has a hardcoded "x86_64", so fails to run on other [unofficial] architectures, because it tries to use an x86_64-specific makepkg config, which overrides CARCH=x86_64. I tried addressing it with this simple patch: diff --git a/src/makerepropkg.in b/src/makerepropkg.in index b271f25..846af06 100644 --- a/src/makerepropkg.in +++ b/src/makerepropkg.in @@ -92,7 +92,7 @@ get_makepkg_conf() { return 1 fi msg2 "using makepkg.conf from ${fname}" - bsdtar xOqf "${buildtool_file/file:\/\//}" usr/share/devtools/makepkg-x86_64.conf > "${makepkg_conf}" + bsdtar xOqf "${buildtool_file/file:\/\//}" "usr/share/devtools/makepkg-$CARCH.conf" > "${makepkg_conf}" return 0 } This half-works, but the arch derivates still needs to ship a custom `devtools` package with their own `makepkg-$CARCH.conf`. Usually, the only thing that really needs to be changed in the per-architecture custom makepkg.conf is CARCH and CHOST. This is still not ideal, and sounds like it could be refined further into something simpler. The .BUILDINFO file specifies the devtools version originally used, so that makerepropkg can download that specific version and use the right makepkg.conf file for the rebuild. It would be much simpler dump all variables from `makepkg.conf` into .BUILDINFO at build-time, and use these directly when rebuilding to test reproducibility. Instead of the package indicating the version of devtools contains its build configuration, the package just includes the build configuration directly. This removes one level of indirection. This approach would also allow checking the reproducibility of packages that were built with slight different settings (including those built by derivates/unofficial platforms). Any thoughts on this? Side note: the above patch might still have value if merged, at least in the short term. -- Hugo Osvaldo Barrera

1 0

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

13 Oct '22

Hi all, you can find the meeting minutes in rendered form here: https://md.archlinux.org/s/c4y-uNz5M The plain markdown dump below: ``` # 2022-10-12 repod meeting Date: 2022-10-12T17:00:00Z Location: Jitsi Scribe: dvzrv ## Attendees * dvzrv * lobachevsky * prawn * polyzen * Torxed * wCPO ## Agenda ### CPU architecture test The architecture of consumed packages is checked against the architecture of the target repository. Packages of type "any" may still be added to architecture specific repositories [!117](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/117) ### Link between package names and their pkgbases A symlink in the management repository is introduced to link the name of packages to their respective pkgbases. This allows for easily finding the pkgbases (or changes to them) of updated packages. [!118](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/118) ### Bugfix: Parsing of file modes from mtree files The .MTREE files may have file modes such as `66` in them, so we zero-fill the retrieved file modes (to a four char string with leading zeros) to consolidate the data properly. [!119](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/119) ### Cleanup: Type hinting Type hinting got modernized. [!120](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/120) ### Cleanup: Regular expressions for paths Replace regular expressions used for checking relative/absolute paths with `pathlib.Path.is_absolute()` to increase validation speed and mitigate issues with non-word UTF-8 symbols. [!121](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/121) ### Check packages against management repository A set of checks test, that consumed pkgbases are newer than the ones found in the management repository and that packages can safely replace packages of the same name (but of differing pkgbase). [!122](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/122) ### Funding Requests for funding have been sent in to [PrototypeFund](https://prototypefund.de/) and [NLnet](https://nlnet.nl/) for their October round of funding. Also contacted Pierre-Loup of Valve about repod, potential use of it in their own infrastructure and funding. ### Milestone 0.3.0 The following issues (and more) still need solving/ implementing: * Lock files need to be written [#117](https://gitlab.archlinux.org/archlinux/repod/-/issues/117). * Cleanup CLI module [#127](https://gitlab.archlinux.org/archlinux/repod/-/issues/127). * Tracking of source URL [#39](https://gitlab.archlinux.org/archlinux/repod/-/issues/39). * Writing of empty sync databases when there are no packages in the repository [#123](https://gitlab.archlinux.org/archlinux/repod/-/issues/123). * Cleanup of symlinks on update and removal of packages [#107](https://gitlab.archlinux.org/archlinux/repod/-/issues/107). ### Add visualization for repod components Add a visualization of the project and its workflows (current and future) [#133](https://gitlab.archlinux.org/archlinux/repod/-/issues/133). ### Increase exposure for repod and other Arch software projects Add a list of all Arch Linux projects (and a short explanatory sentence) in the [Getting involved wiki article](https://wiki.archlinux.org/title/Getting_involved#Software_project… to increase their exposure and publish the change [#134](https://gitlab.archlinux.org/archlinux/repod/-/issues/134). ``` Best, David -- https://sleepmap.de

3 2

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

12 Oct '22

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

2 2

[repod] 2022-09-28 meeting minutes
by Brett Cornwall 05 Oct '22

05 Oct '22

https://md.archlinux.org/s/dyjtzuJMo Raw markdown: # 2022-09-28 repod meeting Date: 2022-09-28T17:00:00Z Location: Jitsi Scribe: brett ## Attendees * alad * artafinde * brett * dvzrv * polyzen * prawn * torxed * wCPO ## Agenda ### New features * Writing to databases via transactions functionality added. * Lots of work for error checking, such as: * architecture/target checking to help guard against pushing the wrong architecture into a repository * Pushing non-debug packages into debug repo * Pushing a version that's older than the current * "Self-healing" when mistakes like that are made, i.e. corrects state when errors are encountered. Testing against upstream repositories are a little tough right now since there's no repod deployment, i.e. there's no repository yet. ### Source packages Currently, source packages are created by some script somewhere and may or may not be working as expected. repod will likely have functionality that will create/push source packages as part of the build process. It will need to do so based on license parsing. ([Issue #125](https://gitlab.archlinux.org/archlinux/repod/-/issues/125)) (Additionally, archweb doesn't appear to be exposing the source package download.) ### Reaching out to downstreams Reaching out to downstreams led to several visitors in the meetings. Kindly visited by Prawn from Kupfer Linux this time. We've unfortunately yet to be visited again by some of those that have previously expressed interest. It'd be good to somehow retain visitors so we get more contributions and we can all get off the manual scripting hacks we all individually write. Downstreams to contact (again): Asahi Linux, Arch Linux ARM, Valve

2 2

[repod] Next meeting: 2022-09-28 19:00 CEST
by David Runge 27 Sep '22

27 Sep '22

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

2 1

[repod] 2022-09-15 repod follow-up
by David Runge 14 Sep '22

14 Sep '22

Hi all, tomorrow (2022-09-15 17:00 CEST) we will do a short follow-up to refine some tickets: https://meet.jit.si/20220915-repod Feel free to join to help refine/ split our workflow scenarios [1] into more defined/ easier to implement tickets. Best, David [1] https://gitlab.archlinux.org/archlinux/repod/-/issues/49 -- https://sleepmap.de

1 0

[repod] 2022-09-14 meeting minutes
by David Runge 14 Sep '22

14 Sep '22

Hi all, here are the rendered meeting minutes: https://md.archlinux.org/s/niC4zi6w7 Below is the raw markdown: # 2022-09-14 repod meeting Date: 2022-09-14T17:00:00Z - 2022-09-14T20:00:00Z Location: Jitsi Scribe: ## Attendees * dvzrv * wCPO * bittin * polyzen * alad * artafinde * prawn ## Agenda ### Documentation updates Documentation has been restructured to give simple usage examples and focus on getting the user to work with the CLI tooling (e.g. https://repod.archlinux.page/repod/usage.html). ### Tasks and Checks Transactional tasks are implemented to allow rolling back of changes that go wrong ([!108](https://gitlab.archlinux.org/archlinux/repod/-/merge_requests/108)). ### Milestone 0.3.0 The steps described in the packager workflows (see [#49](https://gitlab.archlinux.org/archlinux/repod/-/issues/49)) need to be split into tickets for creating Tasks and Checks. More checks need to be defined for the common packager workflows to be covered (e.g. [#102](https://gitlab.archlinux.org/archlinux/repod/-/issues/102)). More tasks need to be defined for common packager workflows to become atomic (e.g. [#107](https://gitlab.archlinux.org/archlinux/repod/-/issues/107)). The writing of sync databases needs to happen in the context of adding packages, using transactional Tasks (see [#105](https://gitlab.archlinux.org/archlinux/repod/-/issues/105)). ### Future work Implement atomic operations with btrfs snapshots ([#114](https://gitlab.archlinux.org/archlinux/repod/-/issues/114)) Setup git maintenance on management repository ([#115](https://gitlab.archlinux.org/archlinux/repod/-/issues/115)) -- https://sleepmap.de

1 0

[repod] Next meeting: 2022-09-14 19:00 CEST
by David Runge 12 Sep '22

12 Sep '22

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

2 1

[PATCH] archlinux-keyring: harcode using bash as make's shell
by Michel Alexandre Salim 12 Sep '22

12 Sep '22

Dear archlinux-keyring maintainers, Please find attached a patch to make the latest archlinux-keyring release (20220831) build on Debian/Ubuntu, where the default shell is Dash (and the build environment enforces this by passing SHELL=dash). Makefile seems to have acquired some Bash-isms ({} expansion) in 0831 that was not in 0727, and since the usage makes sense, hardcoding the shell to be bash would allow this to work without having to override Debian and Ubuntu builds for the affected targets. Thanks, -- Michel Alexandre Salim identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2

2 3

[repod] 2022-08-31 meeting minutes
by David Runge 31 Aug '22

31 Aug '22

Hi all, please find the meeting minutes in rendered form here: https://md.archlinux.org/s/WeAd-Jd20# The plain markdown is attached below: # 2022-08-31 repod meeting Date: 2022-08-31T17:00:00Z - 2022-08-31T18:30:00Z Location: Jitsi Scribe: ## Attendees * dvzrv * wCPO * polyzen * Segaja * sradjoker * bittin * Prawn ## 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 ([#108](https://gitlab.archlinux.org/archlinux/repod/-/issues/108)) ## Demo by David David demoed importing a package and how the file structure is created. David presented the current milestone: [0.3.0](https://gitlab.archlinux.org/archlinux/repod/-/milestones/2#tab-issu…. ## Evaluate the minimum base set of package attributes We need to evaluate whether the base set of package attributes needs to be reduced: [#109](https://gitlab.archlinux.org/archlinux/repod/-/issues/109). Packagers with very limited/ small setups may otherwise run into issues. In the future the existence requirement for the various attributes could become configurable. -- https://sleepmap.de

1 0