On Mon, Nov 12, 2007 at 08:13:43AM +0100, Michael Ablassmeier wrote:
> Package: par, libpar-packer-perl
> Severity: serious
> Justification: policy violation
> both par and libpar-packer-perl do ship `/usr/bin/par' but neither conflict or
> add a diversion, thus fail to be installed in the same e
Kapil Hari Paranjape <[EMAIL PROTECTED]> writes:
> Seriously, there seem to be (at least) two solutions:
> 1. We can rename the /usr/bin/par from one of the two
> packages. Here the "par" package seems to be the older kid on
> the block.
> 2. We can rename both the /usr/b
Hello,
On Mon, 12 Nov 2007, Michael Ablassmeier wrote:
> Package: par, libpar-packer-perl
> Severity: serious
> Justification: policy violation
> both par and libpar-packer-perl do ship `/usr/bin/par' but neither conflict or
> add a diversion, thus fail to be installed in the same environment:
W
Package: par, libpar-packer-perl
Severity: serious
Justification: policy violation
hi,
both par and libpar-packer-perl do ship `/usr/bin/par' but neither conflict or
add a diversion, thus fail to be installed in the same environment:
> Unpacking libpar-packer-perl (from libpar-packer-perl_0.976
4 matches
Mail list logo