[Pkg-kde-commits] rev 1680 - branches/kde-3.4.0/packages/kdebase/debian

[Christopher Martin]

Author: chrsmrtn-guest
Date: 2005-09-04 23:42:26 +0000 (Sun, 04 Sep 2005)
New Revision: 1680

Modified:
   branches/kde-3.4.0/packages/kdebase/debian/changelog
   branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS
Log:
Add a NEWS entry for the kdm upgrade.


Modified: branches/kde-3.4.0/packages/kdebase/debian/changelog
===================================================================
--- branches/kde-3.4.0/packages/kdebase/debian/changelog	2005-09-04 23:30:54 UTC (rev 1679)
+++ branches/kde-3.4.0/packages/kdebase/debian/changelog	2005-09-04 23:42:26 UTC (rev 1680)
@@ -1,3 +1,12 @@
+kdebase (4:3.4.2-3) unstable; urgency=low
+
+  +++ Changes by Christopher Martin:
+
+  * Add a NEWS entry that explains the KDM upgrade process for users moving
+    from KDM 3.3.x. (Closes: #326542)
+
+ -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Sun,  4 Sep 2005 09:42:04 -0400
+
 kdebase (4:3.4.2-2) unstable; urgency=low
 
   +++ Changes by Christopher Martin:

Modified: branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS
===================================================================
--- branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS	2005-09-04 23:30:54 UTC (rev 1679)
+++ branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS	2005-09-04 23:42:26 UTC (rev 1680)
@@ -1,31 +1,51 @@
+kdebase (4:3.4.2-3) unstable; urgency=low
+
+  * Users upgrading KDM to a 3.4.x, from 3.3.x, will find that KDM no longer
+    uses the /etc/kde3/kdm/Xservers file, if /etc/kde3/kdm/kdmrc has been
+    updated to the version shipped with KDM 3.4.x. The package upgrade scripts
+    will not remove Xservers even if kdmrc has been upgraded, if they detect
+    local modifications. This should allow administrators to merge their
+    Xservers changes into kdmrc before themselves removing Xservers. The new
+    ServerArgsLocal key in kdmrc is where most old Xservers customizations will
+    be placed.
+
+  * Irrespective of the removal of the Xservers file, we highly recommend that
+    all administrators accept the installation of the updated 3.4.x kdmrc file
+    during the package upgrade. Many important changes to KDM's defaults have
+    been made, and KDM is exceedingly bad at handling anything but the latest
+    kdmrc format, so the nuissance of re-customizing KDM will likely prove less
+    than the nuissance of dealing with a KDM that isn't working properly. If
+    you have already upgraded KDM to a 3.4.x package without accepting the new
+    kdmrc, purging and reinstalling the package should achieve the desired
+    effect.
+
+ -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Sun,  4 Sep 2005 09:42:04 -0400
+
 kdebase (4:3.3.2-1) unstable; urgency=low
 
-  Users upgrading from KDE 3.2 might find that their keyboards
-  seem no longer to work in KDM. This problem is caused by a
-  change in KDE's handling of virtual terminals. The setting
-  which puts KDM on vt7, which was contained in
-  /etc/kde3/kdm/Xservers, has changed, and is also now located
-  in /etc/kde3/kdm/kdmrc.
+  * Users upgrading from KDE 3.2 might find that their keyboards seem no longer
+    to work in KDM. This problem is caused by a change in KDE's handling of
+    virtual terminals. The setting which puts KDM on vt7, which was contained
+    in /etc/kde3/kdm/Xservers, has changed, and is also now located in
+    /etc/kde3/kdm/kdmrc.
 
-  Users who, when upgrading to KDE 3.3, opted to replace their
-  Xservers file with the version shipped by the package, but
-  chose to retain their /etc/kde3/kdm/kdmrc file, will thus
-  have a KDM configuration which nowhere contains a setting
-  which properly places KDM on vt7. This can result in a race
-  condition which has the end effect of breaking the keyboard
-  when using KDM.
+  * Users who, when upgrading to KDE 3.3, opted to replace their Xservers file
+    with the version shipped by the package, but chose to retain their
+    /etc/kde3/kdm/kdmrc file, will thus have a KDM configuration which nowhere
+    contains a setting which properly places KDM on vt7. This can result in a
+    race condition which has the end effect of breaking the keyboard when using
+    KDM.
 
-  The solution to the problem is either to replace both of
-  Xservers and kdmrc, or neither, when upgrading to KDE 3.3
-  for the first time.
+  * The solution to the problem is either to replace both of Xservers and
+    kdmrc, or neither, when upgrading to KDE 3.3 for the first time.
 
-  Users already stuck can, after killing KDE, purge and
-  re-install the kdm package, ensuring that the
-  latest, fresh copies are installed. Alternatively, they
-  can edit /etc/kde3/kdm/kdmrc and add the following line:
+  * Users already stuck can, after killing KDE, purge and re-install the kdm
+    package, ensuring that the latest, fresh copies are installed.
+    Alternatively, they can edit /etc/kde3/kdm/kdmrc and add the following
+    line:
 
-  ServerVTs=-7
+      ServerVTs=-7
 
-  in the [General] section of the file.
+    in the [General] section of the file.
 
- -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Sat, 15 Jan 2005 10:28:28 -0500
+ -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Sun, 23 Jan 2005 16:11:07 +0100