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

RFC Final Comment Period: Merge package repositories
by Levente Polyak 26 Sep '22

26 Sep '22

An RFC has now entered Final Comment Period. In 14 days, discussion will end and the proposal will either be accepted, rejected or withdrawn: 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. New Package Maintainers will be restricted to publish packages solely to `[testing]` for the first two months of their active packaging actions. Cheers, Levente

1 0

News post draft: Dropping python2 from the repositories
by Morten Linderud 22 Sep '22

22 Sep '22

Yo, We are just missing a couple of packages before we can fully remove python2 from the repositories. Thanks to Jelle for all the hard work<3 Here is a suggestion for a news entry for the removal itself Subject: Removing python2 from the repositories We have removed python2 from the main repositories. If you still require the python2 package you need to build it from the AUR, or use an [unofficial user repository](https://wiki.archlinux.org/title/Unofficial_user_repositories). -- Morten Linderud PGP: 9C02FF419FECBE16

4 4

Remove ipw2100-fw and ipw2200-fw from [core]?
by Tobias Powalowski 22 Sep '22

22 Sep '22

Hi, while cleaning up archboot: https://fedoraproject.org/wiki/Changes/RemoveWirelessExtensions Those 2 firmware package can be removed, it's only for very old Intel boards which I guess are not even x86_64. Any objections? greetings tpowa -- Tobias Powalowski Arch Linux Developer & Package Maintainer (tpowa) https://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

2 2

Experimental RISC-V port
by Felix Yan 19 Sep '22

19 Sep '22

Hi, As you may or may not have noticed, I have started an unofficial RISC-V port attempt targeting 64-bit RISC-V ISA (riscv64gc) since 2019. There is a simple intro page currently hosted at: https://archriscv.felixc.at/ In the past year, we have a boost in progress and currently ~87.5% of Arch x86_64 packages are available in the riscv64 repository. IMHO The current patch amount is still too high to consider adding riscv64 as an official supported architecture, but we are trying hard on upstreaming them. Yesterday I noticed that Manjaro has imported packages from this port and formed a Manjaro RISC-V port. Their repository is now available at https://repo-riscv.manjaro.org/ This reminds me that we should probably make the port more visible to get more hands on it. Would you consider adding a subdomain at pkgbuild.com or archlinux.org? -- Regards, Felix Yan

5 6

New main key holder (replace Giancarlo)
by Levente Polyak 13 Sep '22

13 Sep '22

Hi all, I've had some chats with Giancarlo and he is currently unexpectedly very busy and stuffed with a lot of work. Thew new MK did not proceed currently to fill in the missing slot. Together we concluded that it would be the best to adapt to the current situation, revoke the newly created key and proceed with a new MK holder. This would allow him to spend his available time on the current responsibilities and projects. After some talks with David, we thought Johannes (demize) would be a good fit. I've approached him and after his careful consideration and review of the responsibilities he would happily fill in the slot. Therefore I'm proposing we replace Giancarlo's key and pass on the duties to Johannes. -- Many thanks to Giancarlo that he intended to help us out and to Johannes for jumping in. cheers, Levente

4 3

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