This package conflicts with Community (non-AUR) package python-pyxdg. I have AUR programs that depend on python-xdg (such as goobook), and others that depend on python-pyxdg (such as mimeo, which says it depends on python-xdg but actually depends on python-pyxdg).
Is there an effort to make python-xdg API/ABI compatible with python-pyxdg? python-pyxdg has elements such as xdg.BaseDirectory, xdg.DesktopEntry, and xdg.Mime which do not exist in the latest version of python-xdg. Do packages which depend on python-pyxdg need to be updated so they run against the (far simpler) python-xdg? Where should I go next for help?
Pinned Comments
ilai commented on 2023-03-14 05:16 (UTC)
The upstream package was recently modified to avoid an import collision with PyXDG. The package must now be imported as
import xdg-base-dirsinstead ofimport xdg.If a package imports
xdg, it should depend on https://archlinux.org/packages/extra/any/python-pyxdg instead of python-xdg, or the imports should be updated upsteam.