Re: desktop-command-not-in-package: link to an arch-dependent package in a arch-independent package
On Sun, Jan 10, 2010 at 15:47:39 +0100, Xavier Roche wrote:
> 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):
>
> 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
>
> Playing with 'Conflicts: A (<= old), B (<= old)' and/or 'Replaces: A
> (<= old), B (<= old)' does not seem to do any good. Humm, I'm
> wondering if the "Let's ignore the minor lintian warning" is not the
> correct solution after all.
>
No. You don't need any conflicts, you need
Replaces: B (<< new)
in the new A and upgrades will work just fine.
Cheers,
Julien
Reply to: