Le 6 juin 2012 à 14:32, Andreas Tille a écrit :
> On Wed, Jun 06, 2012 at 02:12:07PM +0200, Eric Maeker wrote:
>> I need some help.
>> The problem is the following: freemedforms-emr-resources_0.7.1-1 included some files that were moved in the freemedforms-freedata_0.7.4-1. The freedata is not a replacement of the emr-resources.
>>
>> So now, the freedata breaks the emr-resources. And I should manage this by adding:
>>
>> Package: freemedforms-emr-resources
>> Architecture: all
>> Depends: ${misc:Depends}
>> Description: Data for the FreeMedForms EMR
>> Breaks: freemedforms-data (< $(binary:Version)
>> Conflicts: freemedforms-data (< $(binary:Version)
>>
>> Is that right ?
>
> To be safe I'd add
>
> Provides: freemedforms-data (< $(binary:Version))
> Replaces: freemedforms-data (< $(binary:Version))
>
> Even if this is not really exact content wise it ensures a safe upgrade
> path and is harmless even if not totally correct from the functionality
> because when installing freemedforms-emr-resources the dependencies of
> this package are ensuring that all other freemedforms packages in turn
> will be upgraded.
Ok, so to be fully clear. I should add these four lines:
>> Breaks: freemedforms-data (< $(binary:Version)
>> Conflicts: freemedforms-data (< $(binary:Version)
> Provides: freemedforms-data (< $(binary:Version))
> Replaces: freemedforms-data (< $(binary:Version))
Or only two lines:
> Provides: freemedforms-data (< $(binary:Version))
> Replaces: freemedforms-data (< $(binary:Version))
I guess it is the second solution (according to the policy and what you explained).
EricAttachment:
PGP.sig
Description: =?iso-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=