You are not logged in.

#1 2017-05-14 21:36:12

makedin
Member
Registered: 2017-05-14
Posts: 2

Packages chicken and mono are in conflict

As of today(ish), the packages mono and chicken are in conflict. The problem appears to be that both packages create a file called "/usr/bin/csc." Should this be reported as a bug? A quick search of the bug database did not find earlier bugs of this type.

Offline

#2 2017-05-14 21:40:38

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,399

Re: Packages chicken and mono are in conflict

Search better, because it has been reported no less than 4 times already

Offline

#3 2017-05-14 21:40:55

loqs
Member
Registered: 2014-03-06
Posts: 2,271

Re: Packages chicken and mono are in conflict

Offline

#4 2017-05-14 21:46:27

makedin
Member
Registered: 2017-05-14
Posts: 2

Re: Packages chicken and mono are in conflict

arojas wrote:

Search better, because it has been reported no less than 4 times already

Right. It also appears to have been marked as conflicting. I have no idea why I missed that. I guess I should avoid sysadmining and bug reporting at night.

Offline

#5 2017-05-17 23:54:14

caelia
Member
Registered: 2016-05-14
Posts: 5

Re: Packages chicken and mono are in conflict

Okay, I have a question about working around this issue. I've read the bug report, so I see what is going on (curious, however, that this conflict has never shown up before - I've had both mono and chicken installed for a long time).

Anyway, following a suggestion I saw in the bug report discussion, I decided to build the mono package myself, adding a line to change the name of the executable from 'csc' to 'mono-csc'. I ran makepkg and verified that the file in question was renamed as expected. And yet, when I try to install my modified mono package, pacman still reports a conflict.

So, how is pacman finding this conflict between chicken and mono? The conflict is not listed in the PKGBUILD, and the conflicting file has been renamed, so I don't understand.

Offline

#6 2017-05-18 08:12:45

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 5,361

Re: Packages chicken and mono are in conflict

chicken PKGBUILD wrote:

conflicts=('mono')

simplest solution : rebuild both chicken and mono .


Booting with apg Openrc, NOT systemd.
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#7 2017-05-18 21:42:42

caelia
Member
Registered: 2016-05-14
Posts: 5

Re: Packages chicken and mono are in conflict

Lone_Wolf wrote:
chicken PKGBUILD wrote:

conflicts=('mono')

simplest solution : rebuild both chicken and mono .

Oh ... yeah. SMH!

I did query the Chicken package, and it didn't show the conflict. But that was the *previous* version that I already had installed.

Offline

#8 2017-06-01 10:55:48

beroal
Member
From: Ukraine
Registered: 2009-06-07
Posts: 250
Website

Re: Packages chicken and mono are in conflict

Is a solution below good? mono's PKGBUILD:

pkgname='mono-alt-csc'
provides=('mono')

we are not condemned to write ugly code

Offline

#9 2017-06-01 11:02:47

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 5,361

Re: Packages chicken and mono are in conflict

I assume in that pkgbuild you are renaming csc to something else ?

If so you'd want to provide and conflict and replace mono .


Booting with apg Openrc, NOT systemd.
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

Board footer

Powered by FluxBB