You are not logged in.
Offline
Search better, because it has been reported no less than 4 times already
Offline
Offline
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
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
conflicts=('mono')
simplest solution : rebuild both chicken and mono .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
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
Is a solution below good? mono's PKGBUILD:
pkgname='mono-alt-csc'
provides=('mono')
we are not condemned to write ugly code
Offline
I assume in that pkgbuild you are renaming csc to something else ?
If so you'd want to provide and conflict and replace mono .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline