Your message dated Sun, 23 Nov 2014 16:13:04 +0100 with message-id <[email protected]> and subject line Re: Bug#706529: Processed: tagging 706529 has caused the Debian Bug report #706529, regarding release-notes: stale whats-new section for stable-updates to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 706529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706529 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: release-notes Severity: normal Tags: patch (I'm handling this separately from my copy-editing sweep since it's a content-modifying change.) The whats-new.dbk section id="stable-updates" announces a change to the Debian repositories that was new in Squeeze (retiring Lenny's "volatile" section). This is not the sort of information that belongs in a chapter about "What's new in Debian GNU/Linux 7.0". (Removing it would also close #622190.) Note that the following paragraph is a new one about the reorganised stable-backports; if we really need to remind people of the existence of stable-updates, a mention could be integrated into that news item. But I recommend just dropping it. This workflow of basing our new-in-Wheezy catalogue on the old stale-since-Squeeze catalogue always strikes me as crazy. Wouldn't it speed things up if the very first thing we did for a new set of release-notes was mark all the pre-existing content of this chapter for deletion? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular packageIndex: whats-new.dbk =================================================================== --- whats-new.dbk (revision 9841) +++ whats-new.dbk (working copy) @@ -494,41 +494,6 @@ </section> -<section id="stable-updates"> - <title>The stable-updates section</title> - <para> - Some packages from <literal>proposed-updates</literal> may also be made - available via the <literal>&releasename;-updates</literal> mechanism. - This path will be used for updates which many users may wish to install - on their systems before the next point release is made, such as updates - to virus scanners and timezone data. All packages from - <literal>&releasename;-updates</literal> will be included in point - releases. - </para> - <para> - Note that this replaces the functionality previously provided by the - <ulink url="http://volatile.debian.org/";>volatile.debian.org archive</ulink>. - </para> - <para> - In order to use packages from <literal>&releasename;-updates</literal>, - you can add an entry to your <filename>sources.list</filename>: - </para> - <programlisting>deb &url-debian-mirror-eg;/debian &releasename;-updates main contrib -deb-src &url-debian-mirror-eg;/debian &releasename;-updates main contrib</programlisting> - <para> - The next time you run <command>apt-get update</command>, the - system will become aware of the packages in the - <literal>&releasename;-updates</literal> section and will consider them - when looking for packages to upgrade. - </para> - <para> - When a new package is made available via <literal>&releasename;-updates</literal>, - this will be announced on the <ulink - url="http://lists.debian.org/debian-stable-announce/";>debian-stable-announce</ulink> mailing list. - </para> - -</section> - <section id="stable-backports"> <title>The stable-backports section</title> <para>
--- End Message ---
--- Begin Message ---On Wed, 1 May 2013 15:33:06 +0200 Julien Cristau <[email protected]> wrote: > On Wed, May 1, 2013 at 12:23:46 +0100, Justin B Rye wrote: > > > Still, we could guard against that by reversing the order of the > > sections... I attach a revised, reordered patch that just takes out > > the line specifically mentioning "volatile". > > > Applied. > > Cheers, > Julien Closing due to ^ Thanks, ~Niels
--- End Message ---
