On Mon, 21 Dec 2015 14:00:48 -0600, David C. Rankin wrote: >On 12/21/2015 03:40 AM, Ralf Mardorf wrote: >> On Sun, 20 Dec 2015 20:57:37 -0600, David C. Rankin wrote: >>> error: failed to commit transaction (conflicting files) >>> php-pear: /usr/share/pear/test/Console_Getopt/tests/001-getopt.phpt >>> exists in filesystem >> >> And what packages does cause the conflict? >> >> $ pacman >> -Qo /usr/share/pear/test/Console_Getopt/tests/001-getopt.phpt >> >> *?* >> > >Ralf, Emil, > > Sorry, I thought it was apparent, all conflicting packages are > owned by >php-pear 5.6.16-3 (they are part of the package being upgraded) A package's files cannot conflict with files from itself. There is another package providing the same files. Such a conflict at least require two packages providing files with the same name. Note! We at least had one package providing files in the same path with the same name that were absolutely different software. I don't remember this file anymore, I noticed it because I installed both packages. The maintainers couldn't notice it, because they were not interested in both domains and were not aware about the other software. Upstream of both software accidentally used the same name. $ pacman -Qo /path/to/a/file does show the package a file belongs too. After misusing the force option pacman -Qo might not show the culprit anymore. Assumed you build packages on your own or you're using packages from AUR, they likely will not automagically care about transitions done by the official repositories. Perhaps you missed to maintain AUR or self build packages.
