Am Mittwoch, den 05.12.2007, 17:46 -0500 schrieb Anuradha Weeraman:
> Hi Sebastian,
>
> Any ideas on what we can do about this?
That's actually a very good question... I really can't rename the ncc
binary as it is used by quite a few build scripts and changing it would
mean that we diverge with
Hi Sebastian,
Any ideas on what we can do about this?
Thanks.
On May 30, 2007 9:44 PM, Anuradha Weeraman <[EMAIL PROTECTED]> wrote:
> Hi Sebastian,
>
> > Ok, now that etch is release what shall we do about this bug, Anuradha?
> > Does your upstream consider to change the name of the binary?
>
>
Hi Sebastian,
Ok, now that etch is release what shall we do about this bug, Anuradha?
Does your upstream consider to change the name of the binary?
Sorry for the late response, but I've been a bit busy lately and I've
not had much time for anything else. But things should change soon,
hopefull
Ok, now that etch is release what shall we do about this bug, Anuradha?
Does your upstream consider to change the name of the binary?
What other solutions would be possible for this?
Bye
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
Package: ncc, nemerle
Severity: serious
Justification: file conflicts between Packages, policy violation
hi,
both ncc and nemerle ship `/usr/bin/ncc' but do not conflict or add a
diversion, thus fail to be installed on the same environment:
dpkg: error processing /var/cache/apt/archives/nemerle
5 matches
Mail list logo