[SOLVED]Weird conflict with official packages and aur packages

Question

Hi. I have enchant-zemberek installed on my system. It is my package that i'm maintaining at AUR. Yesterday i tried to install poedit which depends on enchant. Weirdly altoguh enchant-zemberek provides enchant; pacman tried to remove enchant-zemberek and instead install enchant. Otherwise it won't let me install poedit. I have updated enchant-zemberek PKGBUILD and pacman let me install poedit without forcing me to install enchant. Here is what i have in my first PKGBUILD before update:
replaces=("enchant")
provides=("enchant")
conflicts=('enchant')
And after updating;
replaces=("enchant=${pkgver}")
provides=("enchant=${pkgver}")
conflicts=('enchant')
Now, i'm wondering while an AUR package have different package name than the official one why pacman tries to replace it? Why PKGBUILD needs package version in provides tag? Say, if i want to keep my own my-abc-1.0-1.i686.pkg.tar.xz but official package abc-1.1-1.i686.pkg.tar.xz released; must i keep my package only in Ignores array? Should i report this as a bug?
Last edited by tarakbumba (2011-04-07 09:52:41)

Answer 1

No, its not a bug. poedit depends on gtkspell which depends on enchant>=1.5.0 - your original custom enchant package did not provide any specific version of enchant, so pacman pulled in the repo package instead to satisfy the versioned dependency. As you have built your package with replaces=enchant, pacman also honours that.