[arch-general] Package conflicts

Doug Newgard scimmia22 at outlook.com
Tue Mar 25 12:17:27 EDT 2014

> Date: Tue, 25 Mar 2014 16:59:29 +0100
> From: admin at progandy.de
> To: arch-general at archlinux.org
> Subject: Re: [arch-general] Package conflicts
> Am 25.03.2014 16:33, schrieb Doug Newgard:
>> ----------------------------------------
>>> Date: Tue, 25 Mar 2014 10:03:59 -0400
>>> From: jdarnold at buddydog.org
>>> To: arch-general at archlinux.org
>>> Subject: [arch-general] Package conflicts
>>> I'm having a problem with the liteide vs gocode-git packages. liteide,
>>> which is an official Pacman package, has recently started to include
>>> the /usr/bin/gocode binary, which I have been using via the AUR
>>> package gocode-git (there is also another AUR package called
>>> gocode-bin but no pacman package).
>>> So now when I try to update I get an error:
>>> error: failed to commit transaction (conflicting files)
>>> liteide: /usr/bin/gocode exists in filesystem
>>> This didn't seem to be right, as I'm trying to install liteide, not
>>> gocode here. So I reported the problem:
>>> https://bugs.archlinux.org/task/39607
>>> and it immediately got closed with the statement that AUR packages
>>> aren't supported so contact the maintainer of the AUR package.
>>> Well, as far as I can tell, there isn't much the maintainer of the AUR
>>> package can do if some other package is going to just put any old
>>> binary wherever it wants without saying anything about it. Shouldn't
>>> the liteide package at least say it provides 'gocode'? Or conflicts or
>>> something besides just letting pacman complain about a file that exists
>>> in the filesystem?
>>> Carrying this a bit further, how would it or should it work if I did
>>> want to keep using gocode-git, but also use liteide?
>>> --
>>> Jonathan Arnold Webstream: http://hieronymus.soup.io
>>> If you want to go fast, go alone. If you want to go far, you
>>> need a team ~ John Wooden
>> As I said, contact the AUR maintainer. There are really two options; first, he can add liteide to the conflicts array, in which case you can't have them installed together. Second, he can move the conflicting binaries. Either way, it's something that needs to be done in the AUR package.
>> Doug
> As far as I know, gocode is a go library (go package?). For python, each
> library is packaged separately, why is it different for go?
> Andreas

3rd party python libraries are packaged separately, libraries that are included as part of the base distribution are not. Same situation here, liteide upstream is including gocode, it's not being pulled separately and simply bundled with liteide.


More information about the arch-general mailing list