# pacman Published articles for pacman. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Snagboot v3.0 is released! DevFeed: [Snagboot v3.0 is released!]() Original publisher: [Read original article]() Author: Romain Gantois Published: 2026-08-19T13:23:00Z Content type: release Language: en Sources: [Bootlin]() Topics: [Programming](), [Python](), [Kivy](), [Compression](), [GUI](), [Qualcomm](), [USB](), [Protocol (disambiguation)](), [apt](), [Linux]() Tags: [apt](), [compression](), [gui](), [linux](), [news](), [pacman](), [protocol](), [python](), [python-3-14](), [qualcomm](), [release](), [snagboot](), [technical](), [usb](), [v3]() ### AI overview Snagboot 3.0 replaces its Kivy-based Snagfactory interface with a Qt6 and PySide6 application, enabling Python 3.14 support and a more familiar desktop UI. The release also adds ZStandard-compressed image support, recovery support for Qualcomm and TI platforms, and plans for distro packaging. ### Source excerpt Snagboot has just received its second major version number increase since its initial release in 2023! The jump to 2.0 had been made to mark the introduction of Snagfactory, back in 2024. Almost two years have passed since then, and contributions to the project have been going strong! The milestone which underlies our decision to ... Continue reading "Snagboot v3.0 is released!" ## virtualbox-ext-vnc \>= 7.2.12-2 requires manual intervention DevFeed: [virtualbox-ext-vnc \>= 7.2.12-2 requires manual intervention]() Original publisher: [Read original article]() Author: Christian Hesse Published: 2026-07-21T13:01:46Z Content type: news Language: en Sources: [Arch Linux: Recent news updates]() Topics: [Oracle-VM-VirtualBox](), [pacman](), [upgrade](), [Arch Linux](), [Script]() Tags: [existing](), [files](), [install](), [pacman](), [root](), [run](), [script](), [system](), [upgrade](), [using](), [virtualbox]() ### AI overview An upgrade to virtualbox-ext-vnc version 7.2.12-2 requires manual intervention because its previously installed files were not tracked by pacman. Users should uninstall and reinstall the extension, remove the VNC extension pack as root, or use pacman's overwrite option before upgrading. ### Source excerpt Previously, we installed its contents in a way that made pacman not aware of the files (using VBoxManage extpack install ... from an install script). To mitigate issues during upgrade, you can use one of the following methods: Uninstall virtualbox-ext-vnc before upgrading the system, then installing it again. Run VBoxManage extpack uninstall 'VNC' as root before upgrading the system. Instruct pacman once to overwrite the existing files: pacman -Syu --overwrite '/usr/lib/virtualbox/ExtensionPacks/VNC/*' ## Ansible roles: proxy\_env, ssh, etc\_hosts, libvirt released DevFeed: [Ansible roles: proxy\_env, ssh, etc\_hosts, libvirt released]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2026-05-03T06:03:00Z Content type: release Language: en Sources: [stafwag]() Topics: [Ansible](), [releases](), [ssh]() Tags: [ansible](), [apt](), [archlinux](), [changelog](), [debug](), [documentation](), [freebsd](), [kvm](), [libvirt](), [linux](), [pacman](), [releases](), [service](), [ssh]() ### AI overview The article announces releases for four Ansible roles: proxy_env 2.1.0, ssh 1.1.1, libvirt 2.1.0, and etc_hosts 1.1.1. It lists updates including package-management changes, handler fixes, documentation updates, lint corrections, and virtual-machine SSH host-key support. ### Source excerpt Made some time to do some work for a few Ansible roles that I maintain. You'll find the new releases below. ## .NET packages may require manual intervention DevFeed: [.NET packages may require manual intervention]() Original publisher: [Read original article]() Author: George Rawlinson Published: 2025-12-11T07:01:28Z Content type: news Language: en Sources: [Arch Linux: Recent news updates]() Topics: [.NET](), [pacman](), [upgrade](), [ASP.NET](), [Arch Linux]() Tags: [dependencies](), [dotnet](), [failed](), [net](), [pacman](), [update](), [upgrade]() ### AI overview An upgrade from .NET 9.0 to 10.0 may require manual intervention for several Arch Linux packages, including ASP.NET Runtime, .NET Runtime, and the .NET SDK. The document provides pacman commands for users who need to retain the 9.0 packages. ### Source excerpt The following packages may require manual intervention due to the upgrade from 9.0 to 10.0: aspnet-runtime aspnet-targeting-pack dotnet-runtime dotnet-sdk dotnet-source-built-artifacts dotnet-targeting-pack pacman may display the following error failed to prepare transaction (could not satisfy dependencies) for the affected packages. If you are affected by this and require the 9.0 packages, the following commands will update e.g. aspnet-runtime to aspnet-runtime-9.0: pacman -Syu aspnet-runtime-9.0 pacman -Rs aspnet-runtime ## waydroid \>= 1.5.4-3 update may require manual intervention DevFeed: [waydroid \>= 1.5.4-3 update may require manual intervention]() Original publisher: [Read original article]() Author: George Hu Published: 2025-11-06T00:35:08Z Content type: release Language: en Sources: [Arch Linux: Recent news updates]() Topics: [Arch Linux](), [pacman](), [Python]() Tags: [errors](), [files](), [pacman](), [python](), [update](), [upgrade]() ### AI overview An Arch Linux notice explains that upgrading waydroid to version 1.5.4-3 may conflict with unowned Python byte-code files created by earlier versions. It provides a pacman command to safely overwrite the conflicting files. ### Source excerpt The waydroid package prior to version 1.5.4-2 (including aur/waydroid) creates Python byte-code files (.pyc) at runtime which were untracked by pacman. This issue has been fixed in 1.5.4-3, where byte-compiling these files is now done during the packaging process. As a result, the upgrade may conflict with the unowned files created in previous versions. If you encounter errors like the following during the update: error: failed to commit transaction (conflicting files) waydroid: /usr/lib/waydroid/tools/__pycache__/__init__.cpython-313.pyc exists in filesystem waydroid: /usr/lib/waydroid/tools/actions/__pycache__/__init__.cpython-313.pyc exists in filesystem waydroid: /usr/lib/waydroid/tools/actions/__pycache__/app_manager.cpython-313.pyc exists in filesystem You can safely overwrite these files by running the following command: pacman -Syu --overwrite /usr/lib/waydroid/tools/\*__pycache__/\* ## How to Identify the Package Manager of a Linux System DevFeed: [How to Identify the Package Manager of a Linux System]() Original publisher: [Read original article]() Author: Umara Mushtaq Published: 2025-07-14T02:13:11Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Bash](), [Script](), [dnf](), [snap](), [pacman](), [Ubuntu]() Tags: [apt](), [arch-linux](), [article](), [automated](), [automation](), [bash](), [compatibility](), [debian](), [distribution](), [distributions](), [distro](), [dnf](), [fedora](), [how-to](), [introduction](), [linux](), [linux-distribution](), [linux-how-to](), [linux-mint](), [package-management](), [package-management-scripting-apt-dnf-pacman-snap-yum](), [pacman](), [scripting](), [snap]() ### AI overview Identify a Linux system's likely default package manager by checking its distribution in `/etc/os-release` or with `lsb_release`, then verify whether a tool such as `apt` is installed with `which`. The text cautions that a system can have multiple package managers. Its basic Bash script checks with an `if`/`elif` chain and reports only the first match. The more flexible script loops through a fixed list (`apt`, `yum`, `dnf`, `zypper`, `pacman`, `snap`, `flatpak`) to report all detected tools, then maps selected distribution names to a presumed default. The examples map Ubuntu, Debian, and Linux Mint to `apt`; Fedora and Red Hat to `dnf`; CentOS to `yum`; Arch and Manjaro to `pacman`; and openSUSE to `zypper`. ### Source excerpt Learn different ways to guess or identify the default package manager of a Linux system. The post How to Identify the Package Manager of a Linux System first appeared on Baeldung on Linux. Related Stories How to Check for Available Package Updates in Linux How to Properly Install Valgrind? Background Jobs in a Loop in Bash ## Arch Linux System Maintainance. DevFeed: [Arch Linux System Maintainance.]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2022-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Fernando Cejas Blog]() Topics: [Arch Linux](), [Linux](), [Package Management](), [pacman](), [maintenance](), [upgrade]() Tags: [android](), [culture](), [development](), [engineering](), [guide](), [infrastructure](), [ios](), [java](), [kotlin](), [linux](), [maintenance](), [open-source](), [pacman](), [programming](), [python](), [rust](), [scala](), [software](), [software-development](), [upgrade](), [web-development]() ### AI overview A guide to maintaining Arch Linux installations. It covers system updates, troubleshooting keyring issues, cleaning the pacman cache, removing orphaned and unwanted packages, and managing cache data in the home directory. ### Source excerpt In this guide we will walk through the most important practices **regarding system maintainance for Linux home computers.** Most of them are **Arch Linux** (and variants) specific but we can get ideas on how other distros can use and apply the same principles. ## Clang on Windows DevFeed: [Clang on Windows]() Original publisher: [Read original article]() Published: 2020-01-05T22:46:09Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [c/c++](), [Windows](), [Package Management](), [make](), [Azure](), [CI/CD]() Tags: [azure](), [build](), [c](), [c-plus-plus](), [cache](), [clang](), [continuous-integration](), [make](), [pacman](), [windows]() ### AI overview A tutorial on using MSYS2 to install and run Clang on Windows for building 32-bit and 64-bit C/C++ applications. It also describes integrating the toolchain with Azure Pipelines and caching downloaded packages. ### Source excerpt Thanks to the MSYS2 project, now there is an easy way to utilize Clang to build C/C++ application on Windows. This works equally well for both 32-bit and 64-bit programs. ## My i3 window manager setup DevFeed: [My i3 window manager setup]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2019-04-10T02:12:04Z Content type: article Language: en Sources: [Sam Saffron]() Topics: [Arch Linux](), [Linux](), [pacman](), [Windows](), [Wiki](), [Ubuntu](), [Documentation](), [Firefox]() Tags: [blog](), [blog-post](), [c-sharp](), [developer](), [documentation](), [firefox](), [linux](), [net](), [pacman](), [rails](), [reddit](), [ruby](), [saffron](), [sam](), [sql](), [ubuntu](), [weblog](), [windows](), [youtube]() ### AI overview A developer describes moving from a Windows setup with Ubuntu and i3 to using Arch Linux and i3 as a primary desktop environment. The article discusses the author's early experience, motivations for choosing Arch Linux, and initial customization of the desktop. ### Source excerpt I have been a long time i3 window manager user. But not really. My old Windows 10 based setup involved doing all my console work in an Ubuntu VM running i3. However, the lion's share of the non console work was still done in Windows, including browsing and more. For multiple years now I only partially experienced i3, it showed. My i3 setup was almost vanilla. My move to Arch Linux changed everything. This move completely shifted the way I think about my relationship with my desktop environment. Previously, my relationship with Windows was very simplistic. Windows works the way it works, I simply adapted to that. Sometimes I learned a new shortcut, but the majority of my Windows day-to-day involved dragging windows around, reaching Firefox window and tab saturation, closing windows with the mouse and so on. I am not a great example of a Windows ninja some users go down a far more custom path. I do feel I am pretty typical though of a developer using Windows or Mac. I was given a menu, I learned a tiny bit of it, then I simply threw away the menu and reached for the mouse. In this blog post I would like to talk about what my 3.5 week adventure has looked like and where I am today! Opening moves When I moved to Linux I did not know much of the current state of Linux on the desktop but I did know 2 things: I would be using Arch Linux I would be using the i3 tiling window manager I opted for Arch cause I love not having to worry about upgrading my system every 6-12 months to another major release, I think pacman and the package library on Arch is amazing, if I ever am missing tiny bits from the official library it is trivial for me to just grab a package from the very comprehensive AUR. I also think the documentation in the Arch wiki is fantastic and it helped me enormously. I opted for i3 cause I wanted to fully experience the window manager, not treat it as a glorified tmux like I was for years. A day or so into my move I was uncomfortable with the way my stock install ## Make your open-source project accessible DevFeed: [Make your open-source project accessible]() Original publisher: [Read original article]() Published: 2015-09-21T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Open Source](), [Web Accessibility (a11y)](), [Software](), [Linux](), [Homebrew](), [pacman](), [PyPI](), [npm](), [Ruby](), [rubygems]() Tags: [accessible](), [developers](), [homebrew](), [install](), [linux](), [npm](), [onboarding](), [open-source](), [packages](), [pacman](), [pypi](), [rubygems]() ### AI overview This article explains how open-source projects can improve contributor and user onboarding by making software easier to install. It recommends distribution-level packages such as Linux packages and Homebrew packages, along with language-level packages such as PyPI, Rubygems, and npm. ### Source excerpt I build software products and write on the Internet. ## el-get 1.1, with 174 recipes DevFeed: [el-get 1.1, with 174 recipes]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-12-20T15:45:00Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [Package Management](), [pacman](), [apt]() Tags: [apt](), [emacs](), [hooks](), [package-management](), [packages](), [pacman](), [release]() ### AI overview This release announces el-get 1.1 with 174 recipes. It adds support for pacman, Mercurial, Subversion, and darcs; improves apt-get prompt handling; changes synchronous installation behavior; automatically removes previous failed installations; and overhauls the build facility. ### Source excerpt Yes, you read it well, el-get currently features 174 recipes, and is now reaching the 1.1 release. The reason for this release is mainly that I have two big chunks of code to review and the current code has been very stable for awhile. It seems better to do a release with the stable code that exists now before to shake it this much. If you're wondering when to jump in the water and switch to using el-get, now is a pretty good time.