I totally agree. There are also some other outdated packages that prevent up-to-date upstream packages from installing. Many of them have been reported, but for some reason it seems rather slow process to get then updated in Antergos.
You might want to create an issue here:
There is a way to override the Antergos repo.
You can create your own local repo onto your hard disk, and put your AUR version of the vivaldi package there.
Then write info about your local repo into /etc/pacman.conf, just before the [antergos] repo definition.
The whole thing goes something like this:
- create your local repo directory (may want to select a better place…)
mkdir -p $HOME/myrepo cd $HOME/myrepo
- download vivaldi PKGBUILD from AUR
yay -a -G vivaldi
- build vivaldi package
cd vivaldi # yay downloaded PKGBUILD here makepkg PKGBUILD
- move the built package to the repo
mv vivaldi-*.pkg.tar.xz ..
cd .. rm -rf vivaldi
- create the repo
repo-add myrepo.db.tar.xz *.pkg.tar.xz
- edit /etc/pacman.conf, add your new repo info (the following lines) before [antergos] (and change your username!)
[myrepo] Server = file:///home/<username>/myrepo SigLevel = Optional
- and finally, run this (and pray ;))
If it worked, congratulations!
The only minor disadvantage is that when the AUR version changes, you have to build the package again, add it to your repo, and run pacman -Syyu.
Seems that cnchi has a small problem here. Installer’s packages.xml file does not seem to have any catalyst stuff, so those are related to the graphics driver.
You should be able to install the LTS kernel after reboot to the installed system, for example
sudo pacman -S linux-lts linux-lts-headers
Is that what you mean when you mentioned “disks are in wrong order at installer boot”
I mean: when the installer boots, it would be nice to to know which drive is /dev/sda and which is /dev/sdb, so that it doesn’t try installing to the wrong drive (the stick). But I understood that you cannot reach to that point, to get that info?
The BIOS info simply shows which device should be searched first for booting.
What I’d like to see is the output of the following commands:
sudo fdisk -l lsblk -fm
since they would tell many things about the disks and partitions.
So you have another linux installed and working? If so, please plug in the Antergos installer and show the output of the commands above.
My current guess is some sort of BIOS & UEFI mixup. You seem to have a hybrid BIOS, so you in principal can choose any boot mode?
UEFI PC: when I insert the LiveUSB, I switch on and quickly press function key to bring up the boot menu and then select the USB from the list, then press enter to begin installation. Is that the correct method?
Something like that. But you could try selecting CD/DVD instead of USB, although it seems counter-intuitive.
pacman is the mother of all package managers in the Arch world. It is very good with official packages, but it doesn’t support AUR packages and has no GUI.
pamac-manager is quite good overall, it has GUI and supports also AUR packages.
Currently seems that we all recommend yay as a command line tool that support also AUR. It has almost the same syntax as pacman.
By the way, pamac-manager does not support AUR by default, you have to enable that.
Also, remember that AUR packages are not officially supported, so you may use them at your own risk. AUR packages are made by ordinary users, not by the distro’s team.
Entschuldigung, forgot to translate it to your language. Hopefully that’s not a problem.