On 1/4/11 10:20 AM, "Luis Araujo" <[email protected]> wrote:
>On 01/04/2011 01:42 PM, Wichmann, Mats D wrote: >> [email protected] wrote: >>> On 1/4/2011 9:21 AM, Michael Leibowitz wrote: >>>> On Tue, 2011-01-04 at 08:50 -0800, Ryan Ware wrote: >>>>> Unfortunately, it looks like Nokia has decided to rename the Aegis >>>>> packages to MSSF. :-( The first I heard of it was the >>>>> repositories in Gitorious being renamed. Is the procedure here >>>>> that I create a bug stating that the package names are incorrect >>>>> and that I go through, create new packages with the new names, fix >>>>> the yaml and spec files and submit to testing or is there something >>>>> else that we do for renaming >>> a project? >>>> Please use obsoletes in the spec/yaml to make update work correctly. >>>> This is what it is for. >>> yup >>> >>> one minute thing; if you use obsoletes, please use a versioned >>> obsoletes, like >>> >>> Obsoletes: foo<= 4.23-2 >>> >>> the reason for this is that if you do a "naked" obsoletes like >>> >>> Obsoletes: foo >>> >>> you can never ever go back or use another package with that name, >>> while if it's versioned then the obsoletes is bounded... >> >> is it still the case that it's necessary to use a Conflicts >> /and/ a Provides line (providing the old package name) to >> really get the replacement right? >I think only a Provides should make it: > >Provides: foo > 4.23-2 Thanks folks. Wanted to make sure I do this right. Ryan _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
