On Mon, Mar 30, 2009 at 01:04:23PM +0200, David Paleino wrote:
I'm *NOT* talking in behalf of the Debian Mono Group, but I really think we
shouldn't break existing scripts/programs/workflows/whatever, and call our
binary as cli-csc.
Hi guys,
according to this message and the previous ones
Hi mentors,
I'm asking you help about bug #509367.
Summarizing, new mono packages introduced a /usr/bin/csc file that
conflicts with /usr/bin/csc I used to ship into chicken-bin, so now
there's a conflict between these two packages.
I think there're at least three possible ways to fix it:
1)
On Mon, Mar 30, 2009 at 12:08:41PM +0200, Davide Puricelli wrote:
I'm asking you help about bug #509367.
Summarizing, new mono packages introduced a /usr/bin/csc file that
conflicts with /usr/bin/csc I used to ship into chicken-bin, so now
there's a conflict between these two packages.
I
Le Mon, Mar 30, 2009 at 12:08:41PM +0200, Davide Puricelli a écrit :
Summarizing, new mono packages introduced a /usr/bin/csc file that
conflicts with /usr/bin/csc I used to ship into chicken-bin, so now
there's a conflict between these two packages.
Hello Davide,
This is covered by our
Ciao Davide,
On Mon, 30 Mar 2009 12:08:41 +0200, Davide Puricelli wrote:
Summarizing, new mono packages introduced a /usr/bin/csc file that
conflicts with /usr/bin/csc I used to ship into chicken-bin, so now
there's a conflict between these two packages.
I'm a bit biased here, since I'm part
Hello,
On Mon, 30 Mar 2009, Davide Puricelli wrote:
I'm asking you help about bug #509367.
As you can imagine similar problems have come-up in the past.
2) just putting a Conflicts between mono-devel and chicken-bin,
but I think it's not a good solution for users.
This is not correct since
6 matches
Mail list logo
