Hello Baptiste,
Hi,
Dixit Mario Blättermann, le 25/02/2020 :
>> D'autres questions techniques :
>> - est ce que le nouveau paquet sera identifié « replace:
>> manpages-fr{,-extra} » ?
>> - il faudra penser à faire supprimer les paquets
>> manpages-fr{,-extra}, ou les remplacer par des factices qui
>> dépendent du nouveau paquet ?
>
>Indeed, the upcoming v4.0 of manpages-l10n will replace manpages-fr,
>manpages-fr-dev and manpages-fr-extra (and moreover: manpages-de,
>manpages-de-dev, manpages-pl and manpages-pl-dev).
>
>I don't know how this will be handled regarding Debian's packaging and
>upgrading policies - I'm using Archlinux. But I'm quite sure the new
>manpages-fr will provide manpages-fr-extra virtually, because we don't
>distinguish anymore between "normal" and somewhat "extra" man pages.
>CC'ing Tobias Quathamer, he is the maintainer of the current
>manpages-de package; maybe he can better explain the upgrade process.
(Keeping Tobias in Cc)
I think the new manpages-l10n-fr should have something like
replace: manpages-fr, manpages-fr-extra, manpages-fr-dev
(or maybe provide: ?)
Then, maybe a new upload of these 3 olds to change them as leaf
packages depending on manpages-l10n-fr ?
Moreover, it could then be added as depends in task-l10n-fr (to be
automatically installed in new install).
I don't know what Tobias plans for the packaging. But I assume there won't be any binary packages named manpages-l10n-*. The easiest way to get a proper upgrade path and to avoid confusing the users would be to split the source package manpages-l10n into binary packages named manpages-de, manpages-fr, manpages-pl and so on. Generally I would recommend this way of packaging, also for other distributions.
And moreover, in that case nothing needs to be changed regarding the task-l10n-fr dependency, because manpages-fr still exist as such; only manpages-fr-extra should then appear as a "provides" of manpages-fr.
Best Regards,
Mario