[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: desktop-command-not-in-package: link to an arch-dependent package in a arch-independent package

On Sun, Jan 10, 2010 at 03:47:39PM +0100, Xavier Roche wrote:
> Ralf Treinen a écrit :
> >True, but this is really an exceptional case. I suspect the normal case is
> >that one installs both packages.
> Yep, exactly. OTOH, I will just move the small desktop file in the
> arch-dependent one, which is going to spoil some additional bytes,
> but nothing too serious fortunately :)
> The only consequence is a typical conflict when installing the new
> package because a file was moved from a package to another one, with
> dependency issues (something I already experienced):

One uses Replaces to indicate that there is a file conflict.

> installed:package A
> installed:package B contains <desktop file>
> new:package A [new version]  contains <desktop file>
> new:package B [new version]
> Typicall update step when updating A:
> - A depends on B, will update B later
> - remove A
> - installing new A, but <desktop file> already exist
> ==> FAIL

Package: A
Depends: B
Conflicts: B (<< newversion)
Replaces: B (<< newversion)

GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply to: