I tried to follow it and I get a lot of issues.
I've followed the steps, except for the mirror list (I've used the one on the main page)
I've also added:
[lib32-testing]
Include = /etc/pacman.d/mirrorlist
[lib32]
Include = /etc/pacman.d/mirrorlist
Before [multilib]
Basically, after "People coming from Manjaro OpenRC, will additionally need to run" Hell breaks loose.
One part of the issue is all the "-openrc" init scripts breaking the uninstallation of the -nosystemd packages.
When I remove them one by one, I then hit this:
:: device-mapper and device-mapper-nosystemd are in conflict. Remove device-mapper-nosystemd? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: device-mapper and device-mapper-nosystemd are in conflict
Name : device-mapper-nosystemd
Version : 2.02.171-1
Description : Device mapper userspace library and tools
Architecture : x86_64
URL : http://sourceware.org/dm/
Licenses : GPL2 LGPL2.1
Groups : base-nosystemd
Provides : device-mapper=2.02.171
Depends On : glibc eudev
Optional Deps : None
Required By : cryptsetup device-mapper-openrc dmraid grub lvm2-nosystemd parted
Optional For : None
Conflicts With : device-mapper
Replaces : None
Installed Size : 864.00 KiB
Packager : Artoo <
[email protected]>
Build Date : Fri 05 May 2017 10:37:58 PM CEST
Install Date : Sat 20 May 2017 06:25:38 AM CEST
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : Signature
A few tweaking later (removing bunch of packages myself) I hit some corrupted packages:
error: libsodium: signature from "Cromnix (Buildbot) <
[email protected]>" is invalid
:: File /var/cache/pacman/pkg/libsodium-1.0.15-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)
pacman -Ss libsodium
galaxy/libsodium 1.0.15-1 [installed: 1.0.13-1]
P(ortable|ackageable) NaCl-based crypto library
imagemagick (so I remove playonlinux inkscape cups-filters)
then libsodium (that is ultimately depended on NetworkManager)
After enabling all "-testing", I finally passed that step (>_<)
Everything seems ok. Grub too. Alea Jacta Est. (reboot)
With the lts kernel I have no network. (r8168 firmware)
Since it has been automatically been updated for the last few (years?) I didn't checked about that one ...
Let's try again ...
This time it looks it's working (3 hours of time when following the "simple migration" page from the URL)
Now I don't dare to disable the "-testing" repositories but we'll see what comes.
That page is obsolete (and forgotten), use https://artixlinux.org/migrate.php. Make sure you're using the new (non-SF) repositories. (https://artixlinux.org/)
Glad you made it though, for r8168 either use r8168-lts from [community] or r8168-dkms from the AUR (preferred).
I have also not been successful in migrating following those instructions.
And link you posted is 404!
The link had an extra "." and directed erroneously. Here is a corrected link for future reference: https://artixlinux.org/migrate.php (https://artixlinux.org/migrate.php)
I've removed the "-testing" repositores and Scc/Syy. My system now seems to be running adequately (still using r8168-lts for the network driver though)
May I suggest to utterly trash the content of the obsolete page except for the link (and maybe an automatic redirection) to a page that works ?
The current link on the page leads to https://artix-linux.github.io/migrate/artixlinux.org/migrate.php a.k.a 404
I need to understand the benefit of following lts (hopefully stability) vs following the latest kernel.
One would assume that r8168-lts is better suited for linux-lts.
Since I'm mostly interested in development tools, this will do for now.