On Tue, 25 Mar 2014 17:00:57 +0100 Karol Blazewicz <karol.blazewicz@xxxxxxxxx> wrote: > On Tue, Mar 25, 2014 at 4:33 PM, Doug Newgard <scimmia22@xxxxxxxxxxx> > wrote: > > ---------------------------------------- > >> Date: Tue, 25 Mar 2014 10:03:59 -0400 > >> From: jdarnold@xxxxxxxxxxxx > >> To: arch-general@xxxxxxxxxxxxx > >> 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? > > See > https://projects.archlinux.org/svntogit/community.git/log/trunk?h=packages/liteide > -> > https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/liteide&id=58c9d99fd75dbfab1b4fa6f8b5fe0541fffaef4a > > Package from the repos shouldn't conflict with other packages from the > official repos, but there may be an issue with packages from the AUR. > In this case, it's usually up to the AUR package maintainer to work > around it. So what happens if / when gocode moves to the official repo? What would be the expected solution then? -- 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