[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#687005: marked as done (release notes: unified keyboard settings and stable-updates are not new any more)

Your message dated Thu, 24 Jan 2013 02:01:54 +0100
with message-id <20130124010154.GB28389@beskar.mdcc.cx>
and subject line Re: Bug#687005: release-notes: unified keyboard settings and stable-updates are not new any more
has caused the Debian Bug report #687005,
regarding release notes: unified keyboard settings and stable-updates are not new any more
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 owner@bugs.debian.org

687005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687005
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Tags: wheezy patch

Here's a patch to clear out some old news from the whats-new section.
(Perhaps for jessie we can start the whats-new section with a blank
slate, but it seems too late for that for wheezy.) Thoughts?


Index: whats-new.dbk
--- whats-new.dbk	(revision 9360)
+++ whats-new.dbk	(working copy)
@@ -428,64 +428,6 @@
-<section id="unity-keyboard-settings">
-<title>Unified keyboard settings</title>
-In this new release, the settings for the keyboard have been unified so that
-both the console and the Xorg server use the same settings. The keyboard
-settings are now defined in the <filename>/etc/default/keyboard</filename>
-configuration file which overrides the keyboard defined in Xorg's
-configuration file.
-The <systemitem role="package">console-setup</systemitem> package now
-handles the keyboard for both environments as well as the font
-configuration for the console. You can reconfigure the keyboard layout and
-related settings by executing 
-<command>dpkg-reconfigure keyboard-configuration</command> 
-or by manually editing the <filename>/etc/default/keyboard</filename>
-configuration file.
-<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>
   <title>GNOME 3</title>

--- End Message ---
--- Begin Message ---
for release-notes, pending means closed, see also current status of
release-notes at e.g.
http://www.debian.org/releases/testing/amd64/release-notes/ .



--- End Message ---

Reply to: