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

Announcing whatcanidofor.archlinux.org
by Daniel M. Capella 04 Feb '23

04 Feb '23

Glad to finally announce a new contribution landing page for Arch Linux: https://whatcanidofor.archlinux.org It's a modern take on the asknot family, see the README for more details: https://gitlab.archlinux.org/archlinux/neoasknot/-/blob/main/README.md The Arch Linux theme and navbar we all know and love /will/ be implemented, don't you worry, and maybe even a search bar: https://gitlab.archlinux.org/archlinux/neoasknot/-/issues -- Best, Daniel <https://danielcapella.com>

1 0

Re: ROCm in [community]
by Torsten Keßler 29 Jan '23

29 Jan '23

Hi Sefa, thank you very much for your interest in the ROCm stack. I've just added ROCm meta packages to [community-testing], see [1] for a complete list. For instance, if you would like to use the full stack, install rocm-hip-sdk. Best! Torsten [1] https://docs.amd.com/bundle/ROCm-Installation-Guide-v5.4.2/page/Meta-packag… On 06.01.23 13:08, Sefa Eyeoglu wrote: > Hi Torsten, > > thanks a lot for your work! I am here to ask if it's planned to create > a group for these packages. That would make it a lot easier to install > all of the (currently available) toolchain at once. > > Best, > Sefa > > > On Fri, 2022-12-23 at 16:20 +0100, Torsten Keßler wrote: >> Hi all! >> >> I'm excited to announce that basic ROCm support was added to >> [community-testing] yesterday! >> >> What is ROCm? >> ROCm is AMD's open source framework for GPU programming. It comprises >> an >> OpenCL implementation, HIP (AMD's CUDA) and OpenMP offloading. >> >> Which GPUs are supported? >> Official support is limited, see [1]. >> >> Which parts were added to [community-testing]? >> The low level components (rocminfo, rocm-smi-lib), the OpenCL runtime >> (rocm-opencl-runtime) and the HIP runtime / compiler (hip-runtime- >> amd). >> >> How can I use it? >> Install (hip-runtime-amd rocm-smi-lib rocm-opencl-runtime) to use all >> currently available packages. First check if the amdgpu kernel module >> is >> loaded and add your login user to the video and render groups. Run >> /opt/rocm/bin/rocminfo to validate that the HSA runtime correctly >> detects your hardware. You can also check the output of clinfo for >> OpenCL support. >> >> Use case: blender >> First, install hip-runtime-amd and add /opt/rocm/bin to PATH. Open >> blender, go to Edit -> Preferences and select "HIP" in "System / >> Cycles >> Render Devices". Open your favorite scene and select "GPU compute" in >> "Render Properties". You can monitor the GPU load with >> >> watch -n.1 rocm-smi >> >> if you've installed rocm-smi-lib. >> >> What's next? >> Add the ROCm math libraries (rocblas, rocsparse, rocfft, ..) that are >> needed for Machine Learning and many other applications. >> >> Best! >> Torsten >> >> [1] >> https://docs.amd.com/bundle/Hardware_and_Software_Reference_Guide/page/Hard…

1 0

FOSDEM 2023 Dinner
by Morten Linderud 26 Jan '23

26 Jan '23

Yo! The previous years at FOSDEM we have held a dinner with around 15-20 people. Some maintainers from Arch, and some users that wanted to join. It has been great events and with FOSDEM 2023 happening I thought it was a good idea to do it again :) The dinner will be held Saturday, 4th of February, around 20:00. The dinner is sponsored by the Arch and should cover a drink and a main course. We will cap the attendees to 20 people. Priority for members of the Arch team (developers, trusted users and support staff). Any free spots after this can be taken by anyone interested. Send me an email *offlist* if you want to attend. The users requesting spots will get a heads up the week before FOSDEM to give all staff a chance to reply. Please ask me if you have any questions :) I also plan to announce a pub closer to the FOSDEM weekend, so anyone unable to join the dinner can still come and grab a drink with the rest of us. Cheers! -- Morten Linderud PGP: 9C02FF419FECBE16

1 1

Looking for maintainer of kodi-addon-game-libretro
by Ike Devolder 20 Jan '23

20 Jan '23

Hi, Since I only build these related extensions and never test or use them myself I'm looking for someone who wants to take care of the "gaming" part of Kodi. As part of the update to Kodi 20 I'll rebuild them but if nobody is interested I will drop all of kodi-addon-game-libretro to AUR. -- Ike

1 0

RFC: Increase _FORTIFY_SOURCE level to 3
by Levente Polyak 19 Jan '23

19 Jan '23

A new RFC (request for comment) has been opened here: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/17 Please visit the above link for discussion. Summary: Adjust packaging CFLAGS from -D_FORTIFY_SOURCE=2 to -D_FORTIFY_SOURCE=3 for better fortification coverage

1 0

base-devel and multilib-devel meta-package
by Levente Polyak 16 Jan '23

16 Jan '23

Hi all, I'd like to inform upfront that now would finally be a good time to implement the `base-devel` meta-package orthogonal to our already existing `base` meta-package. We haven't really pushed it for quite some time as nothing in `base-devel` changed in the past. Now the situation looks slightly different as we lately added `debugedit` in order to provide debug packages via makepkg. This lead to a couple of followup issues with missing installations and people running into such an issue on multiple occasions. Hence I've prepared the `base-devel` meta-package and will put it into [testing] soon. I'll also add a TODO list to remove the group declaration once its available in [core]. This will ensure any changes to the `base-devel` set will automatically be reflected on hosts that need that set available like chroots, AUR build environments or dev machines. Cheers, Levente

1 0

Upcoming PHP 8.2 update and introduction of legacy packages
by Pierre Schmitz 16 Jan '23

16 Jan '23

With the release to PHP 8.2 I will introduce a new set of packages to solve most of the issues with PHP updates. There are two valid requirements: On one hand people need the latest version to use its features or to develop new applications. And on the other hand users want to run third party applications that might not yet be compatible with the latest PHP runtime. I'll make the following changes to support both use cases while still keeping the rolling release model: The php package we already provide will be updated to 8.2 and be kept up-to-date with the latest upstream releases. php7 packages will be removed as this version is end-of-life and will no longer receive security updates. A new set of php-legacy packages will be introduced which always provide the oldest version actively supported by upstream*. This version is usually one year behind the latest release, but still receives bug and security fixes. It will be possible to install and use this version alongside the latest php packages. The binaries and configuration path will have a suffix named "-legacy", which will require configuration changes if you want to switch between legacy and non-legacy versions. In contrast to e.g. the php7 package, this version will also follow a rolling release model and will receive minor and even major updates. In the end this would result in the following release schedule: php: currently 8.1 soon 8.2 December 2023: 8.3 php-legacy: currently: 8.1 December 2023: 8.2 (upstream provides security updates till December 2024; so we have some room to postpone when issues arise.) I will provide a news item once all these changes are ready for the stable repositories. For packaging: I'll take care of the module rebuilds. Most modules are already compatible or at least have patches. Similar to php7 I'll make use of split packages to build a module for both PHP branches. One exception is the uwsgi plugin which is known for being a less active project. For now it would only be possible to provide it for php-legacy. Application packages might use the virtual php-interpreter dependency which provides the minor version. As stated above switching between legacy and non-legacy versions will require user interaction. For some packages that are known for almost never being compatible with latest PHP versions, it might be easier to depend on php-legay right away. Greetings, Pierre *) https://www.php.net/supported-versions.php -- Pierre Schmitz, https://pierre-schmitz.com

3 11

Need help testing pacman 6.0.2 debug packages
by Morten Linderud 15 Jan '23

15 Jan '23

Yo! With the release of pacman 6.0.2 we have now support for debug packages through `debugedit` as opposed to the awk hack used previously. https://gitlab.archlinux.org/pacman/pacman/-/commit/ae2f506ddfd1 This should resolve several issues we have had with the existing debug packages and I want people to test this support. Please recreate your build chroots and/or reinstall base-devel locally. Enable debug in a diverse set of packages you maintain. And help validate the current assumptions: * Debug packages for Rust, Go* and Julia should work * Weird /build directories should not exist * We should have header files * The source files should be located in `/usr/src/debug/${pkgbase}-${pkgver}` You can list them easily with `bsdtar -tf *.pkg.tar.zst` Note pacman is currently in [testing]. In the case for Go we need to disable compressed dwarf headers with `-ldflags=-compressdwarf=false`. It should be the case for any binaries with these headers as well. They can be recognized with the weird "DWARF version 0 unhandled" error string during stripping. Please report back if things look good, or you are looking at weird debug package structures :) If everything looks fine I intend to write an RFC for blanket enabling debug packages in devtools! -- Morten Linderud PGP: 9C02FF419FECBE16

6 14

[news draft] PHP 8.2 update and introduction of legacy branch
by Pierre Schmitz 12 Jan '23

12 Jan '23

Hi all, after some time in [testing] and the first patch release I think it is time to move the PHP 8.2 rebuild into the stable repositories. I would like to add a brief news item to describe the introduction of the legacy PHP version. This might be a bumpier update but I believe this should make future updates a lot smoother. Any input on improving this news item is very welcome: (I'll include some links to the packages and upstream version page when actually posting this) --- The php packages have been updated to the latest version 8.2. In addition to this, a new set of php-legacy packages have been introduced. These will follow the oldest but still actively supported PHP branch. This enables users to install the latest version but also introduces the option to use third party applications that might rely on an older version. Both branches will be kept up to date following our rolling release model. php and php-legacy can be installed at the same time as the latter uses a "-legacy" suffix for its binaries and configuration files. In addition to this, the php7 packages have been removed as they reached end of life. The imap extension will no longer be provided as it relies on the c-client library which has been abandoned for many years. -- Pierre Schmitz, https://pierre-schmitz.com

1 1

Git packaging sources: state of the art
by Levente Polyak 10 Jan '23

10 Jan '23

# Introduction Behold, ~~winter~~ Git is coming. We've been working on and off to get Git packaging sources ready for a while now. Today I'd like to outline the final proposal regarding the action plan, workflow, tooling and also the reason for a couple of decisions. Consider this as a late xmas gift to our distro 🎁😻 # Timeline We started with a proof-of-concept from Foxboron and are now closing in with a bunch of production ready changes finished by me in various components such as dbscripts, devtools, svn2git - including the great help of several other contributors related to infrastructure, repo converter and other components. The current plan is to finally get all this rolled out around end of January or most likely right after FOSDEM 2023 where we could hack together on the last outstanding bits. Shortly, we'll also notify a couple of downstream projects so they can prepare themselves. After finishing all followup tasks and feedback loops, we'll communicate the exact migration window. Please look at the Roadmap item for more detailed steps. The plan for the migration window is to have multiple people from different areas block time for a full weekend and start with the rollout on Friday. This would give us the freedom and flexibility to handle all kind of unforeseen issues that may pop up during the rollout. Throughout the main rollout phase, packaging would be shut down completely and packagers will need to update their devtools and local checkouts. # Roadmap The Git packaging sources will be the very first item on our future Roadmap. We'll soon see more cleanup and Epics on our Roadmap for all the bigger changes and improvements we want to prioritize and outline for our distro. The overall idea is to greatly increase transparency, have a better way to visualize and track progress, dependencies as well as action items. https://gitlab.archlinux.org/groups/archlinux/-/epics/7 As I only started this Epic while we were already near the finish line, it mainly consists of a couple of condensed issues with sub-tasks in dependent projects such as infrastructure, dbscripts, devtools, as well as a list of general tasks tied to the Epic. In the future we want to utilize it better by breaking it down into sub-issues in a very early stage. However, the currently available Epic should be a good starting ground that everyone can subscribe to and comment on. # Git repo layout Lets get technical. The Git repo layout is related to RFC-14 (Merge package repositories) and most of its aspects were discussed during that proposal. However, let's summarize what that actually means for the packaging repositories and how all this looks like. Every `pkgbase` will have its own dedicated repository that is stored in a single combined GitLab group called `packages` (e.g. https://gitlab.archlinux.org/archlinux/packaging/packages/foo) This allows us to have a well structured and simple layout, which provides the grounds for a per `pkgbase` issue board on GitLab (note: dealing with the issue boards is not part of the migration). Package maintainers will receive write access to the entire GitLab group. Whenever we completely remove a `pkgbase` from our distro, we will archive the corresponding GitLab repository instead of deleting it. Being able to physically delete the GitLab repository would effectively circumvent force-push and tag protection rules. On top, preserving an auditable history of former packaging sources is actually a good thing. # Git tag format Because of Git tag format limitations (man `git-check-ref-format`), we convert certain characters such as `~` to dots `.` and the epoch delimiter will be a simple dash `-`. All Git tags are expected to be signed using valid packager keys available in archlinux-keyring. Some example pkgver with their matching Git tags: - 1.0-1 ➡ 1.0-1 - 2:1.0-1 ➡ 2-1.0-1 - 1.0~rc2 ➡ 1.0.rc2 # dbscripts The way dbscripts currently works will be simplified: Instead of having two separate checkouts for `packages` and `community`, we will instead only have a single dbscripts instance on repos.archlinux.org managing all packages. https://gitlab.archlinux.org/archlinux/dbscripts/-/merge_requests/37 ACLs will be done on the application level using checks against Unix groups, as described in RFC-14. Once we rolled out the Git migration, we will have `junior-packager` and `junior-dev` Unix groups available for limited interaction with testing/staging repositories. https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0014-merge-p… The current state of the pacman repository will not be stored alongside the `PKGBUILD` anymore as we did with svn (the `repos` directory next to `trunk`). Instead we will use a single state repository, that will keep track of all the information and mapping between git-tags, hashes and repositories. The canonical source of the state repository is repos.archlinux.org and will be mirrored by our GitLab. This way we keep it very simple and get rid of any kind of exfiltrate secrets lying around on repos.archlinux.org just to be able to push directly to GitLab. For consistency checks, dbscripts maintains and updates read-only clones of all packaging source repositories. To reduce cache miss and transfer times, the infra will perform scheduled cache warming. This will be fast enough for most everyday usage. To further speed up huge rebuild sets like haskell or openssl, where this will be noticeable, we may add some complexity to dbscripts in the future that uses parallel with some smart error handling. Any interaction with scripts such as `db-update` will be globally available in `$PATH`. However, interaction that requires to ssh into repos.archlinux.org (or setup local aliases) will be superseded by the new `pkgctl` tooling (more on `pkgctl` in the following sections). # devtools To handle new functionality (e.g. package source repository management, GitLab authentication, etc.) a new unified tooling named `pkgctl` has been created. The old scripts such as `commitpkg` have been reworked into a smarter and more convenient unified interface (the old scripts will remain available for a while). As packagers will need to adapt workflows for Git anyway, now was the best time so everyone only needs to adapt once. https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/126 ## repo management The command `pkgctl repo` will provide a couple of functions to work with our package source repositories. First and foremost the `clone` subcommand allows to conveniently clone and configure a package source repository from our GitLab: > pkgctl repo clone libfoo It is also possible to clone all packages of a maintainer for convenient initial setup and a dedicated flag for mass edits: > pkgctl repo clone --maintainer yourlovelynickname To clone a read-only checkout without a valid ssh setup, simply pass `--unprivileged` to the command: > pkgctl repo clone --unprivileged libfoo Cloning will implicitly call the `repo configure` subcommand, which sets up some git repo settings and author information read from `makepkg.conf`. This for example ensures we use our archlinux identities for packaging even if another one is configured globally. This setup is also important as we will enforce git release tags to be signed by trusted keyring keys. To re-configure existing clones, a simple wildcard can be used in the repo's root directory: > pkgctl repo configure * Use the `repo create` subcommand to create a new repository in GitLab. Due to GitLab limitations, this requires to setup a valid auth token (more about it in the next section): > pkgctl repo create linux-is-awesome ## authentication Certain subcommands such as `repo create` require a valid GitLab token which can be managed with the `auth` command. To let the CLI guide you through the creation and setup: > pkgctl auth login To verify the current token and its validity: > pkgctl auth status This will save the token in `${XDG_CONFIG_DIR}/devtools/gitlab.conf`. ## package release This is one of the workflow steps that will get dramatically smarter and supersedes the `commitpkg` (which is usually used through symlinks such as `communitypkg`) and the `archrelease` scripts, while providing more convenient dbscripts interaction. The commitpkg/archrelease scripts will remain available for now, but should be considered a deprecated interface available during a transition period. The `pkgctl release` command unifies the steps to commit, tag and upload build artifacts. It stages modified version controlled files for commit, creates a Git tag matching the `pkgver` and finally uploads all build artifacts. Before trying to create a new Git tag, the tooling will ensure that the local clone is up-to-date. This should avoid inconsistencies when a package maintainer tries to upgrade and locally tag an already released version. By default the target binary package repository will be auto-detected by querying the repo it is currently released in. When initially adding a new package to the repositories, the target repo must be specified manually. By passing either the `--testing` or `--staging` option, the matching repository such as `multilib-testing` will be resolved. This smart interface obsoletes all the `commitpkg` symlinks (e.g. `extrapkg`, `community-testingpkg`, etc.): > pkgctl release --staging libfoo > pkgctl release --repo extra-testing newpkgthingie By default the `pkgctl release` command will only commit, tag and upload the artifacts to the staging area on repos.archlinux.org. To update the binary package repository as the final step, either pass `--db-update` to the `release` command, or use the dedicated `pkgctl db` command: > pkgctl release --db-update The `pkgctl db` command provides all required subcommands to interact with dbscripts such as move, remove and update. This obsoletes the requirement to setup local shell aliases or ssh directly to repos.archlinux.org to manage the repository sync database state: > pkgctl db update > pkgctl db move extra-staging extra-testing libfoo libbar ## package build The `pkgctl build` command will follow the same principles as `pkgctl release` by providing a smart interface to automatically detect which build target to use and will also provide `--testing` and `--staging` options to build against those special repositories. This will obsolete the need to directly call the currently used build scripts (e.g. `extra-x86_64-build`): > pkgctl build --testing --release --db-update The build command will start as an incubating feature and may change in the future when we wire up a build service to the pkgctl interface. The build command will also receive more convenience options such as setting pkgver without the need to manually adjust the `PKGBUILD` with an editor.

4 4