If you use Artix testing repos, you should also use Arch testing repo, libidn2 is there and soon will be in ours.
You say “should” but this is the first time I encounter such a rule.
So this is the problem we will attempt to solve today without help from Artix, no manual, no wiki, not even a correct template of pacman.conf with commented out features of what may be necessary to patch things up in the future.
warning: cannot resolve "libidn2", a dependency of "libpsl" :: The following package cannot be upgraded due to unresolvable dependencies: libpsl
So now we will attempt to modify the /etc/pacman.conf file and make the Arch repositories look like this:
[extra] Include = /etc/pacman.d/mirrorlist-arch # for those willing to try Arch's testing of community pkgs # [community-testing] # Include = /etc/pacman.d/mirrorlist-arch [community] Include = /etc/pacman.d/mirrorlist-arch # to break Artix or return to Arch this is what you need # [core] # Include = /etc/pacman.d/mirrorlist-arch # this is what is meant by Arch-testing, not core-testing or extra-testing but plain testing [testing] Include = /etc/pacman.d/mirrorlist-arch
$ pacman -S libidn2
[extra] Include = /etc/pacman.d/mirrorlist-arch # for those willing to try Arch's testing of community pkgs # [community-testing] # Include = /etc/pacman.d/mirrorlist-arch [community] Include = /etc/pacman.d/mirrorlist-arch # to break Artix or return to Arch this is what you need # [core] # Include = /etc/pacman.d/mirrorlist-arch # this is what is meant by Arch-testing, not core-testing or extra-testing but plain testing # [testing] # Include = /etc/pacman.d/mirrorlist-arch
Important: make sure that you run pacman -Sy again to make the db forget all that there was in Arch’s testing.
For those who haven’t understood yet:
Artix began as a systemd-free Arch, is aimed towards intermediate to advanced users and never promised nobody anything. Take it or leave it.
Should this be revised and mean experienced ARCH users?
Because experience in other linux results in not knowing what to do.
@Artoo ‘s statements from day 1 about the smooth move from Manjaro to Artix have been false just to let Manjaro off the hook (as an unofficially declared systemd-ONLY distribution). This has nothing to do with Manjaro other than Artoo quitting Manjaro (OpenRC-xfce) to work on Artix.
Deep inside all the “kids” in Artix are nice and hardworking. A bit sloppy, fast, and immature in terms of responsibilities to users. It is as if they are working on a distribution for themselves and their buddies (probably game designers) and the secret got out and some of us outside the “inner circle” are benefiting from utilizing the secret.
If you want to see further reference to pacman.conf and repository handling here is a hint:
Wait a damn minute, there is “indirect implication” that there exists, in unlike artix-philosophy of repository naming, a [testing] repository. So let us try this pacman -Sy AGAIN for the n-th time. (reference: https://wiki.archlinux.org/index.php/DeveloperWiki:Community_move_to_devtools about the only one I found in wiki and manuals in Arch)
Another half day lost in Artix “mysticism”.
PS If you like using AUR repositories you will find that this libidn2 identical package exist in AUR and you could install it using one of the package managers that use AUR, like pamac, yaourt, octopi .. etc. But you may never hear Artix developers tell you to use AUR for anything as they are purists in an Arch sense. And ofcourse extensive use of AUR may get you burned. One way is what installing something and pulling also AUR dependencies, eventually an artix package may exist that requires the same packages but as they are already installed from AUR the ones cleansed for Artix will not install. This may result to a package not working or even the system not booting, if a dependency will be one of the core system.
Had you used something like pamac with AUR enabled to do an update today you might not have realized there was a dependency missing.