Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#68640 - [ttf-nerd-fonts-symbols] [ttf-nerd-fonts-symbols-mono] Mono and non-mono variants shouldn't conflict

Attached to Project: Community Packages
Opened by Oliver Ford (OJFord) - Monday, 16 November 2020, 13:10 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 16 November 2020, 17:21 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Daniel M. Capella (polyzen)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


ttf-nerd-fonts-symbols{,-mono} are specified as conflicting with each other.

Why? I would like the monospace variant as a fallback for my monospace font, and the proportional variant as a fallback for my {sans-}serif fonts.

Steps to reproduce:
- pacman -S ttf-nerd-fonts-symbols{,-mono}
This task depends upon

Comment by mattia (nTia89) - Sunday, 19 September 2021, 08:47 GMT
I confirm the issue
Comment by Daniel M. Capella (polyzen) - Tuesday, 21 September 2021, 02:47 GMT
If you find a solution, please share!
Comment by Oliver Ford (OJFord) - Tuesday, 21 September 2021, 10:50 GMT
Sorry, a solution to what? Why do they need to be marked as conflicting - because of `usr/share/fontconfig/conf.avail/10-nerd-font-symbols.conf` being common to both?