Quoting GLEP 42 (and besides, it is self-evident): "When performing package moves, developers must also update any relevant Display-If-Installed headers in news files."
Created attachment 434606 [details, diff] proposed patch
What about saying "increment" instead of "update" for Revision to be more clear: Update any <c>Display-If-Installed</c> headers and increment the <c>Revision</c> in <uri link="::general-concepts/news">news items</uri> referencing the package.
Created attachment 434662 [details, diff] proposed patch v2 (In reply to Göktürk Yüksek from comment #2) > What about saying "increment" instead of "update" for Revision to be more > clear: > > Update any <c>Display-If-Installed</c> headers and increment the > <c>Revision</c> in <uri link="::general-concepts/news">news items</uri> > referencing the package. Patch amended, see attachment. I have kept the parentheses though.
I also considered the references in the body text of other news items: ---- Revision: 1 Display-If-Installed: app-misc/foo Foo is obsolete, please upgrade to app-misc/bar ---- When app-misc/bar is moved to add-admin/bar, I think the news item should be updated and revision bumped so that the users upgrade to the correct package. However, I couldn't find a concrete example for this. What do you think? Sorry for not catching this before v2.
Created attachment 434760 [details, diff] proposed patch v3 It cannot harm if we mention it, see v3 attached.
Pushed.
Sorry for not being able to ack in time and making you do all the push on top of the patches. Looks good to me.
