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

The future of arch-commits
by Kristian Klausen 12 Sep '22

12 Sep '22

Hi all, I'm in the process of migrating our mailing lists from mailman2 to mailman3[1]. Migrating arch-commits could be a challenge though (+1 million mails) and just deprecating it would be easier :) So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way? [1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/59 Cheers, Kristian Klausen

4 5

Arch Linux in August 2022
by Levente Polyak 07 Sep '22

07 Sep '22

## devtools The code and repository has been restructured [0] as it got out of hand over time. Now it follows a clear distinction and structure with improvements in the build system. The incubating tool `diffpkg` received a lot of new features [1] that will be released shortly. The new tool helps to print differences of the current package build against the last release including file listing, pkginfo, buildinfo, diffoscope. Now it provides additional features for colored output, terminal column width and switch between side-by-side and unified output. ## archlinux-keyring The Web Key Directory (WKD) data for Arch Linux is now automatically generated from the archlinux-keyring repository upon tagging of a new version. This allows for the data to be up-to-date right after a release has been made directly from the source of truth. ## RFC We are formalizing an RFC [2] to merge the pacman repository `[community]` into `[extra]` as well as the packaging VCS location `community` into `packages`. The `[core]` repository remains limited to Developers. New Package Maintainers will be restricted to publish packages solely to `[testing]` for the first two months of their active packaging actions. ## repod The 0.2.0 release as well as subsequent patch-level releases have been made. The new releases introduce rudimentary import of package files and the writing of repository sync databases in configurable repository directories. Upcoming work will focus on establishing a framework for dealing with required steps in common packager workflows. ## buildbot A first workable proof of concept has been created which we continue to iterate over. The current state and an outline of ideas has been posted to `arch-dev-public` [3]. ## Staff We would like to welcome serebit and blakkheim among the Trusted Users [4][5]. On top we would like to welcome kgizdov to their new additional duties as Arch Linux Developers [6]. [0] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/100 [1] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/111 [2] https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/14 [3] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o… [4] https://lists.archlinux.org/pipermail/aur-general/2022-August/036929.html [5] https://lists.archlinux.org/pipermail/aur-general/2022-September/036964.html [6] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.o…

1 0

Dropping some packages
by Filipe Laíns 03 Sep '22

03 Sep '22

Hey all, I am doing some house cleaning on my packages. I am planing to drop some, the list is below, if you want to maintain any of them, feel free to adopt and let me know. The leftovers will probably be dropped next weekend. ghld monkeytype pcbdraw python-connexion python-covdefaults python-flake8-typing-imports python-libcst python-litedram python-liteeth python-liteiclink python-litejesd204b python-litepcie python-litesata python-litescope python-litesdcard python-litex python-litex-boards python-nmigen python-nmigen-boards python-pony python-pydecor python-pyproject2setuppy python-pythondata-cpu-lm32 python-pythondata-cpu-mor1kx python-pythondata-cpu-picorv32 python-pythondata-cpu-vexriscv python-pythondata-software-compiler_rt python-swagger-ui-bundle Cheers, Filipe Laíns

2 2

Future build infrastructure for Arch Linux
by Morten Linderud 02 Sep '22

02 Sep '22

Yo! We decided on supporting the x86_64-v3 microarchitecture but not that much have happened since then. Allan did the legwork to get some basic support into `devtools`, and suggested we start rebuilding some packages. This is a bit tedious because we don't have any infrastructure in place to do this job. Supporting two architectures would end up having us package maintainers do two builds per package that needed the support. After brooding a bit on this personally I wound up taking a stab at creating some build infrastructure for Arch. I have two personal goals: 1. Allow automatic builds and personalized staging repositories. 2. Allow rebuilds of different architectures. I have currently written a POC which does *almost* fulfill both of these goals. It uses `devtools` to build packages, and serves them over HTTP in temporary staging repositories. I decided to go with buildbot as I created something similar many years ago, and it allows us to have a flexible, programmable and independent build infrastructure which is decoupled from our VCS services. https://github.com/buildbot/buildbot The source code for our project can be found on gitlab. https://gitlab.archlinux.org/foxboron/archlinux-buildbot You can visit the buildbot instance on https://buildbot.pkgbuild.com/#/. It is also currently hooked up with keycloak so if you have a staff account you can log inn and mess around with the system. To try things out and build a list of packages, or a todo list, you can visit the "Build Package List" builder and hit the blue button: https://buildbot.pkgbuild.com/#/builders/4 Same thing for "Build Package". https://buildbot.pkgbuild.com/#/builders/1 *Please* keep in mind the builders are running on two small VMs under my TV. Do not build obscene and resource intensive packages :) If we decide we want to move forward with this we'll hook this up with more beefy hardware, but until we get there the builders are going to be some ad-hoc best effort stuff. I also need help developing these things, so please continue to read on if you are interested. It would also be great with feedback from people that have features, ideas or issues that would need to be addressed. # Architecture rebuilds To support rebuilds I have implemented a build thing which currently watches a limited set of packages on svn. An example build of vim can be found here: https://buildbot.pkgbuild.com/#/builders/12/builds/19 If you want to look at the artifacts you can visit here: https://buildbot.pkgbuild.com/srv/ftp/extra/x86_64_v3/ If you want to add packages for rebuilds you can send changes to this file: https://gitlab.archlinux.org/foxboron/archlinux-buildbot/-/blob/master/mast… The same notice applies here and I won't accept huuggee packages to be rebuilt. In the future this restriction won't be there. If anyone reading this want to try hook up risc-v builders, ARM builders or 32 bit builders it would be interesting to try that. Please reach out off-list or on #archlinux-projects @ libera. The hosting is going to be ad-hoc and best effort so there isn't any expectations of uptime :) # Building packages For general package builds I have some ideas on how to do this. But nothing is written and I need help to accomplish this. I don't expect us to deal with the buildbot interface directly, and would much rather have some abstractions in front of this to help us submit builds. Currently I have started a blank repository for `buildctl` where I want to experiment with some easy-to-use build tooling for rebuilds, so-name builds and general package bumps. https://gitlab.archlinux.org/foxboron/buildctl The mock-ups for `buildctl` is on this markdown pad: https://md.archlinux.org/NNgk9PN8QmanxElQsYBxwg It would be great to get more hands these two projects :) Please reach out to me on #archlinux-projects @ libera, or off list for questions. Cheers! -- Morten Linderud PGP: 9C02FF419FECBE16

1 0

Orphaning packages
by Jelle van der Waa 02 Sep '22

02 Sep '22

Hey, To reduce my amount of maintained packages, I'm orphaning and maybe dropping it to the AUR if no one picks it up: # Orphans * python-pyaudio * timew * python-pyenchant * rdesktop * tidy # Orphans and unrequired (can be safeuly dropped) * vim-pastie * vim-align * ccd2iso Greetings, Jelle

2 1

RFC: Merge package repositories
by Levente Polyak 01 Sep '22

01 Sep '22

A new RFC (request for comment) has been opened here: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/14 Please visit the above link for discussion. Summary: Merge the pacman repository [community] into [extra] as well as the packaging VCS location `community` into `packages`. The [core] repository remains limited to Developers.

1 0

Dropping Cura from the repositories
by Jelle van der Waa 01 Sep '22

01 Sep '22

Hi, I've maintained Cura (3d printing slicer) for a while but I no longer find the energy to maintain it and keep it updated. If anyone is interested in adopting it feel free, otherwise I will drop it to the AUR in 2 weeks. Note that there is a flatpak available as alternative https://flathub.org/apps/details/com.ultimaker.cura Greetings, Jelle

1 1

Konstantin Gizdov is now a developer
by Sven-Hendrik Haase 31 Aug '22

31 Aug '22

Hey everyone, I internally proposed Konstantin Gizdov to become a developer for his sustained good work on Arch Linux and the need to touch some [extra] packages sometimes. I'm pleased to announce that he has now become a full developer. All the relevant steps have been completed and he should now already be fully onboarded. Welcome aboard, Konstantin! Sven

4 3

repod 0.2.0 release - call for testing and participation
by David Runge 22 Aug '22

22 Aug '22

Hi all, I've just released repod 0.2.0 [1] (it is available as "repod" in our repositories). There are some significant changes in this release which allow for rudimentary handling of binary package repositories in configurable directory structures. For further information please refer to the documentation [2]. I would like to take the time and invite *everyone* (people involved with any distribution making use of pacman as well as their users - especially those with private package repositories) to participate in testing and improving repod. The project is actively maintained (although admittedly currently I am the main developer working on it and additional contributions - although present and valuable - are rare) and does bi-weekly meetings. Repod aims at generically offering the ability to maintain binary package repositories of alpm based packages. As such it transcends Arch Linux as its only client - the software is meant for Arch Linux, downstream distributions and private users alike! TL;DR: Please help the development of repod and associated tooling as it is important for all pacman based distributions and their users. Historically we have had quite a few distribution driven projects which allow us to do the things we do today (e.g. mkinitcpio, archiso, archweb, aurweb, dbscripts, arch-install-scripts, devtools, etc.). All of them have in common, that they lack dedicated development from time to time or are so large/old/deep that they require more than one person to "have the hat on". This being said: I do not feel comfortable being the only/ main person currently developing repod. The project is entwined with our pursuit of moving our packaging infrastructure to a more modern, git based setup in which package sources are separated from the binary packages that are built from them (opposite to how it is currently handled with dbscripts). This process is a gradual one in which we try to decouple the source repositories from the binary package repository state, while offering certain stability guarantees when consuming and handling packages. Upcoming work will entail dealing with necessary checks required for basic movement operations, which will consolidate a lot of (partially unused) code in the dbscripts project. For a more detailed overview for further topics, please have a look at the milestones [3]. Working on the upcoming features could use many more eyes and helping hands! Another piece of the puzzle when looking at moving to a git based workflow and improving our tooling, is the automation for builds/rebuilds (the road between our package source repositories and the binary package repository management software - e.g. repod). For this some solutions exist, some of which are VCS agnostic and some of which we use in larger rebuilds all the time. Morten has started to look at a buildbot based system which could be used for rebuild scenarios and also for building different architectures in the future. To my knowledge this is still very much a WIP, but if you are interested, idle in #archlinux-projects on libera.chat to get exposed to more information (this is also the case for repod btw!). I hope I was able to give a brief overview of what is the current state of things, where we want to go from here and spark some enthusiam about the above projects. There is still a lot of work left to be done for us and any help is much appreciated! :) Best, David [1] https://gitlab.archlinux.org/archlinux/repod/-/tags/0.2.0 [2] https://repod.archilnux.page [3] https://gitlab.archlinux.org/archlinux/repod/-/milestones -- https://sleepmap.de

1 0

Away till end of August
by Leonidas Spyropoulos 12 Aug '22

12 Aug '22

Hello, I will be off till the end of August traveling and taking some time off. While I will have matrix on my phone for IRC communication I won't be having resonably stable internet and easy access to the key for packaging updates. Feel free to update any of my packages along with the ones below which have no co-maintainers except myself. # Packages $ pkgsearch -m artafinde -l 1 corectrl freeplane gdu gitlab-exporter keycloak-archlinux-theme makedumpfile memray polybar prometheus-systemd-exporter vulture Thank you, -- Leonidas Spyropoulos PGP: 59E43E106B247368

1 0