getting this warning when running sudo pacman -Fy etc.
warning: config file /etc/pacman.conf, line 20: directive ‘SyncFirst’ in section ‘options’ not recognised.
Yes I do know why it’s there but why does pacman not know?
Are you sure?
Are you up to date? pacman 6.1.0-7 should make that disappear automatically. 
Yes I am and it did not change /etc/pacman.conf but this is a new build so perhaps the build system is not updated?
Made A new ROM today and just checked and /etc/pacman.conf still has the sync line
Just done sudo pacman -S pacman
warning: config file /etc/pacman.conf, line 20: directive 'sync first' in section 'options' not recognised. warning: pacman-6.1.0-7 is up to date -- reinstalling resolving dependencies... looking for conflicting packages...
Someone should tell @philm the correct word is “deprecated”. 
Anyway, was kind of hoping to see how many tens of users will cry about that warning in the next announcement thread. 
Would be good for pacnew awareness.
4 Likes
The point is it does not work, as stated above, and yes I do have pacman 6.1.0-7
Just searched for pacman.install, from root, and it was not found.
Found it I think I downgraded pacman to 6.1.0-3 and got the pacnew file change it over and on update saw Removing depreciated SyncFirst line from pacman.conf file … this does not appear to work with 6.1.0-7 if the sync line is there.
Yes if the sync line is there 6.1.0-7 just gives a warning and does not remove it.
If other users have this warning they can remove SyncFirst from configuration with sed commands from the commit
sudo sed -i -e '/# If upgrades are available for these packages they will be asked for first/d' /etc/pacman.conf`
sudo sed -i -e '/SyncFirst/d' /etc/pacman.conf
1 Like
I think you just did. 
English is my native language and I only figured out the difference between deprecated and depreciated not too long ago myself, so don’t be too hard on a Deutschsprachiger (if I translated it properly).
5 Likes
the bottom line is for whatever reason 6.1.0-7 does not remove sync line if present
should it? does it need to be fixed?
Should be handled just as any other config change – with merging a pacnew.
Anyway, problem is in
if (( $(vercmp $2 6.1.0-6) < 0 )); then
This will only be true if previous pacman version is less than 6.1.0-6.
So it will work just fine for stable. Anyone else should know enough to be able to handle it manually.
Hopefully it’s ok if I report my similar problem here.
Normally, after installing a new kernel, it switches to this kernel after a reboot. But with kernel 6.9 it does not. I have uninstalled the kernel again, reinstalled it and restarted it again and unfortunately it stays with 6.8.
I have tried with
sudo mhwd-kernel --listinstalled
Output is same as from the topic starter:
Currently running: 6.8.12-1-MANJARO (linux68)
The following kernels are installed in your system:
Warnung: Konfigurations-Datei /etc/pacman.conf, Zeile 20: Direktive »SyncFirst« in Sektion »options« wird nicht erkannt.
- linux66
- linux68
- linux69
Warnung: Konfigurations-Datei /etc/pacman.conf, Zeile 20: Direktive »SyncFirst« in Sektion »options« wird nicht erkannt.
So how did my pacman.conf looks like:
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc manjaro-system
# If upgrades are available for these packages they will be asked for first
SyncFirst = manjaro-system archlinux-keyring manjaro-keyring
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
Is there something wrong with me? Thanks!
I hope not - but the solution is to remove the line from pacman.conf.
2 Likes
Because that line was removed. You should have a pacnew file, which you should look at and make the appropriate changes.
So save the file as below, right?
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc manjaro-system
# If upgrades are available for these packages they will be asked for first
#SyncFirst = manjaro-system archlinux-keyring manjaro-keyring
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
And then restart or anything else action is needed? Thank you!
If you want to live - yes 
It is just an application config - why should it?
1 Like
Ok, but I still have the problem, that the new kernel is not used.
Removed it again, restarted, installed it again and restarted. But it is not active.
Any suggestions?
Hit ESC at boot to see the menu → select it and boot
1 Like
Thanks to all of you guys!
Selected it in the boot menu. Deinstalled the old one. Restarted, no issues!
It would seem to me that the reason I had this SyncFirst in pacman.conf, is that I build my own ROM’s. It still appears, so it is either in the build system? or it’s Calamares doing it? I think the patch is wrong? it would be better if it checked for SyncFirst being present and if it is removing it? Just Checked it’s the Build system, no idea why it’s wrong?
@philm
As it is now - as it is in the example above:
it is present, but commented out,
which means:
it is a default setting
and it can stay
when you want to change the default, uncomment it and add your change