Hi, On 27.08.2012 12:34, Olе Streicher wrote: > Shall I just ignore this error? Or shall I assign the bugs to the new > (still unknown to the system) package name "ftools-fv"? yes, in your case it is fine to ignore that error. > Another question is whether I need to somehow propagate the name > change. in debian/control, I have set "Conflicts: fv; Replaces: fv" > Should I also set "Provides: fv"? This would pollute the package > namespace again with a virtual package of this short name which was the > main reason to change it. No, no special care is needed [*]. Technically you could even omit the Conflicts/Replaces as fv wasn't part of Squeeze either. Having that said it is a good idea to keep it for people who could have kept that package installed since 2004 (which may, or may not still work). At very least you can omit the relation for the release which is supposed to make it into Jessie+1, if Jessie features your package with Conflicts/Replaces. Providing fv does not make any sense unless there are packages which depend on it (there must not), or people might be upgrading with a "fv" package installed to hint apt but there is no support for upgrades beyond one release at time. [*] Your upload needs to clear NEW, however. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
Attachment:
signature.asc
Description: OpenPGP digital signature