April 2023 - Arch-dev-public - lists.archlinux.org

Consolidating our mkinitcpio hooks
by Morten Linderud 03 Mar '24

03 Mar '24

Hi, Currently we have a lot of our mkinitcpio hooks in several packages which has never been consolidated. This makes it confusing where stuff belong and what is provided where, and I really want to consolidate everything. It would help keeping up the development of the hooks, patch everything and ultimately write a test suite for mkinitcpio. I also have long term plans on moving the default hooks from busybox to systemd, but this will happen at a later point. Initially I really want to move the hooks from `cryptsetup` and `systemd`: * encrypt and sd-encrypt from core/cryptsetup * systemd and udev from core/systemd We could maybe consider a few other hooks from [core] depending on peoples opinion? We are missing a good networking hook for systemd, and that should preferably be solved at some point. A list of possibly other relevant mkinitcpio stuff: Hook Package * btrfs btrfs-progs * dmraid dmraid * mdadm mdadm * mdadm_udev mdadm * lvm2 lvm2 * sd-lvm2 lvm2 * net mkinitcpio-nfs-utils * netconf mkinitcpio-netconf # Migration It's unclear to me how we should best move these hooks. We would need to merge them upstream into `mkinitcpio` first, then remove them from the packages. Is a news item is enough for this? Or do we want to include a couple of package constraints to ensure people are accidentally removing their hooks? What are peoples opinions? -- Morten Linderud PGP: 9C02FF419FECBE16

5 10

bash 5.2.x status
by Tobias Powalowski 29 Oct '23

29 Oct '23

Hi, yesterday anthraxx stated this: - major breakage in potentially a lot of scripts including pacman, dbscripts, devtools and who knows what kind of packages. I tried devtools with 5.2.15 and fixed the only thing I ran into, with this MR: https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/133 shopt handling seems to have changed a bit. I would like to proceed in getting latest bash version into our distribution. Adding bash 5.2.x to staging or testing repository and start fixing eventually borken stuff. Would this ok for you guys? greetings tpowa -- Tobias Powalowski Arch Linux Developer & Package Maintainer (tpowa) https://www.archlinux.org <http://www.archlinux.org> tpowa(a)archlinux.org Archboot Developer https://bit.ly/archboot St. Martin-Apotheke Herzog-Georg-Str. 25 89415 Lauingen https://www.st-martin-apo.de info(a)st-martin-apo.de

3 5

Call for participation: Git packaging POC 🚀🎉
by Morten Linderud 01 May '23

01 May '23

Hi everyone! Levente and I have been busy preparing a test environment for the new git package workflow, which is going to replace the svn repository. To test the new git package setup install `devtools-git-poc` from the [community] repository and use the new `pkgctl` utility. Please check each time if there is a new upgrade before playing around. The goal of the testing is to figure out UX issues, bugs and larger issues that would need to be dealt with before a git migration can happen. It's therefor very important that people sit down and play around with the tools :) Support and feedback will be dealt with in the #archlinux-projects channel. Report bugs in GitLab with the following additional information: - devtools-git-poc package version - full PKGBUILD or pkg repo including the Git hash - terminal input and output The workflow should be the following: Basic setup ----------- ### setup packager Make sure your personal `makepkg.conf` contains your packager identity and gpg key. ### authenticate to gitlab pkgctl auth maintain existing packages -------------------------- ### clone an existing package pkgctl repo clone existing-package ### build a package pkgctl build ### release a package pkgctl release pkgctl db update ### combined UX The last three steps can also be expressed as: pkgctl build --release --db-update ### rebuild into staging vim PKGBUILD pkgctl build --staging pkgctl release --staging pkgctl db update This can be completely condensed by: pkgctl build --rebuild --staging --release --db-update maintain new packages --------------------- ### create a new package repo without history pkgctl repo create new-pkgbase pkgctl repo clone new-pkgbase ### add existing AUR repo cd packagerepo pkgctl repo create pkgctl repo configure ### first official build/release Specify the target repo on first run, as the tool can't know it's destination automatically yet pkgctl build --repo extra pkgctl release --repo extra --db-update --- The packages are uploaded into a test group here: https://gitlab.archlinux.org/bot-test/packages This test also includes junior developer and junior packagers. They can only push packages into staging and testing, and not release into the stable repositories. We currently have a couple of people with these permissions to try and figure out issues on that part of the setup. If anyone is interested helping out on this please reach out on the #archlinux-projects IRC channel on Libera. Background on the changes can be found here: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o… Cheers!

6 8

Python 3.11 in [staging]
by Jelle van der Waa 29 Apr '23

29 Apr '23

Early Easter suprise, After some delay Python 3.11 rebuilds are happening in [staging], so please don't start any rebuild. Thanks to felixonmars for starting and rebuilding! Thanks, Jelle van der Waa

4 3

Away for several weeks
by Laurent Carlier 24 Apr '23

24 Apr '23

Last week I fell from my bike and was diagnosed with a broken pelvis/ankle. So for weeks I must stay on a bed for some weeks - and away from my main computer. I was not able to build amdvlk with last releases, so if some can fix it, it'll be awesome. I hope to be back asap, so take care of you and see you soon. NB: this eMail is not signed because is sent with my phone.

3 2

Arch Linux in March 2023
by Levente Polyak 11 Apr '23

11 Apr '23

## Git packaging sources We have improved a lot of pieces in `pkgctl` according to the feedback from the sandbox environment. Most notably it is possible to provide GitLab tokens via the `DEVTOOLS_GITLAB_TOKEN` environment variable, pass nocheck to the build command for bootstrap builds, handle subrelease pkgrels as well as several bugfixes. We are doing another round of testing and would like to proceed with the rollout afterwards. ## devtools A new version 20230307 has been released adding support for architecture-specific mount config. Furthermore `sogrep` now uses the first mirror that is configured for each repo in `pacman.conf` with a fallback to https://geo.mirror.pkgbuild.com. Additionally we added checks to not allow package releases of `PKGBUILD` sources with only weak cryptographic hashing algorithms. ## namcap A new version 3.4.0 has been released with a huge amount of cleanup and codebase improvements. Furthermore new checks have been added like optdepends and sodepends as well as improved pydepends. ## archiso Starting with `archlinux-2023.03.01-x86_64.iso`, the official ISO supports what is called *file system transposition* (**only on UEFI**). This means the ISO can be simply extracted (using an archiver or by mounting and copying) to the root of a FAT formatted partition and it will work™. Messing with boot loader configuration files is not required anymore. The documentation in [0] and [1] have been updated with the new simplified instructions. # mkinitcpio mkinitcpio version 35 followed by bugfix releases 35.1 and 35.2 are out! A major new feature is support for post-generation hooks a.k.a post hooks. These hooks get run after the initramfs generation and can be used to sign the generated images for Secure Boot. Examples are provided in [2] and [3]. Thanks to improvements in xz reproducibility, mkinitcpio can now use multi-threaded xz compression. [0] https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/docs/README.tr… [1] https://wiki.archlinux.org/title/USB_flash_installation_medium#UEFI_only [2] https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secu… [3] https://wiki.archlinux.org/title/Unified_kernel_image#Signing_the_UKIs_for_…

1 0