Archlabs update pacman

Hi boys, after installing the last pacman this sentence is exited with yay and yaourt:

archlabs% yay -S yay -d
:: Checking for conflicts...
:: Checking for inner conflicts...
[Repo: 1]  pacman-5.2.0-2
[Aur: 1]  yay-9.4.2-1

  1 yay                              (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
:: PKGBUILD up to date, Skipping (1/1): yay
  1 yay                              (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
:: Parsing SRCINFO (1/1): yay
risoluzione delle dipendenze in corso...
ricerca dei pacchetti in conflitto in corso...

Pacchetti (1) pacman-5.2.0-2

Dimensione totale dei pacchetti da scaricare:    0,73 MiB
Dimensione totale dei pacchetti da installare:   4,42 MiB
Dimensione netta dell'aggiornamento:            -0,18 MiB

:: Vuoi procedere con l'installazione? [S/n] s
:: Download dei pacchetti in corso...
 pacman-5.2.0-2-x86_64    744,6 KiB  1361K/s 00:01 [----------------------] 100%
(1/1) verifica delle chiavi presenti nel porta...  [----------------------] 100%
(1/1) verifica dell'integrità dei pacchetti        [----------------------] 100%
(1/1) caricamento dei file dei pacchetti           [----------------------] 100%
(1/1) controllo dei conflitti in corso             [----------------------] 100%
(1/1) controllo dello spazio disponibile sul d...  [----------------------] 100%
:: Elaborazione delle modifiche al pacchetto...
(1/1) aggiornamento in corso di pacman             [----------------------] 100%
attenzione: /etc/makepkg.conf è stato installato come /etc/makepkg.conf.pacnew
attenzione: /etc/pacman.conf è stato installato come /etc/pacman.conf.pacnew
:: Esecuzione degli hook di post-transazione...
(1/1) Arming ConditionNeedsUpdate...
==> ATTENZIONE: PACKAGER deve essere nel formato 'Nome d'esempio <indirizzo@email.nonvalido>'
==> Creazione del pacchetto: yay 9.4.2-1 (gio 24 ott 2019, 23:16:21)
==> Download dei sorgenti in corso...
  -> Download di yay-9.4.2.tar.gz in corso...

Translate sentence

attention: /etc/makepkg.conf was installed as /etc/makepkg.conf.pacnew
attention: /etc/pacman.conf has been installed as /etc/pacman.conf.pacnew
:: Performing post-transaction hooks ...
(1/1) Arming ConditionNeedsUpdate ...
==> ATTENTION: PACKAGER must be in the format 'Example name <address@email.not valid>'

I remember someone mention yay didn’t work with the new pacman version: it required pacman<=5.1.3 My trizen works well.

Edit: the new yay version (9.4.2-1) depends on pacman>=5.2. You need to update yay first.

I don’t know what this entails.

These aren’t an issue, common when upgrading some packages. This is when a file is different on your system than the new package, so pacman tries to not break anything and writes the new file to a .pacnew file of the same name.

You can check the two files and compare the changes, possibly copy into your existing file of the same name and remove the *.pacnew version when done. If you don’t want to then you can safely remove the .pacnew files.

I haven’t seen this warning before so I’ll assume it’s from yay, it’s likely just a warning that the PKGBUILD for whatever package is being built is not up to par. I’m not sure though.

I also have it in trizen for some time ago.


Installs the dependency for yay, then also installs pacman.