bh: doc/raw-howtos kolab-kde-client-on-suse91p.txt,1.9,1.10

cvs at intevation.de cvs at intevation.de
Mon Jul 18 21:36:11 CEST 2005


Author: bh

Update of /kolabrepository/doc/raw-howtos
In directory doto:/tmp/cvs-serv26166

Modified Files:
	kolab-kde-client-on-suse91p.txt 
Log Message:
update for the new packages


Index: kolab-kde-client-on-suse91p.txt
===================================================================
RCS file: /kolabrepository/doc/raw-howtos/kolab-kde-client-on-suse91p.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- kolab-kde-client-on-suse91p.txt	28 Jun 2005 11:34:47 -0000	1.9
+++ kolab-kde-client-on-suse91p.txt	18 Jul 2005 19:36:09 -0000	1.10
@@ -4,16 +4,15 @@
 $Id$
 
 Status:
- - description on how to install the prepared package set
-   "kolab2.0-kdepim3.3-aegypten2.0-client".
-   It covers the KDEPIM proko2 branch client for Kolab-2 and all
-   Ägypten-2 components for SMIME/Sphinx email-encryption. 
-   The German localisation is included.
+ - description on how to install the kolab kde client packages.  The
+   packages include the KDEPIM proko2 branch client for Kolab-2 and all
+   Ägypten-2 components for SMIME/Sphinx email-encryption.  The German
+   localisation is included.
  - Description of the update of the kolab2.0-kdepim3.3-aegypten2.0-client
    packages
  - tested as a initial installation on a fresh SUSE 9.1P
    with online-updates as of 20050420.
- - some steps are in German
+ - tested update from earlier versions which used a meta package (20050718)
 
 
 Initial Installation
@@ -37,7 +36,8 @@
 from one of the Kolab mirrors listed here:
 	http://kolab.org/mirrors.html
 
-Just for a installation you need only what is in i586 and noarch.
+You can omit the RPM/src directory if you don't want to download the
+sources as it's not needed to install the software.
 
 
 2. Check the signature of Kolab-Konsortium
@@ -51,7 +51,7 @@
 For each directory of i586, noarch, srpms:
 
 # gpg  --verify md5sums.txt.sig
-# md5sum * | grep -v md5sum  > /tmp/md5sums
+# find . -type f | grep -v md5sums | sort | xargs md5sum > /tmp/md5sums
 # diff /tmp/md5sums md5sums.txt
 
 (For those who wonder why we did not sign the rpm
@@ -60,21 +60,33 @@
 
 3. Install Kolab KDE Client
 
-# cd /tmp/kolab-download
-# rpm -Uvh noarch/kde3-i18n-de-3.2.1.proko2.0.rc3-0.noarch.rpm
-(SUSEs genIS_PLAINcache can't handle noarch)
-
 # yast
 
-Installation steps within yast only in german available:
-	Bei yast unter "Software->Installationquelle wechseln"
-	ein neues Software-Quellmedium  (lokales Dateisystem)
-	hinzufügen und aktivieren: /tmp/kolab-download/i586
-	Anschliessend den Status dieses neuen Eintrages aktualisieren.
+ - Add a new installation source with via "Software->Change Source of
+   Installation". ("Software->Installationquelle wechseln" in the German
+   version).
 
-	In yast unter "Sofware->Installieren oder löschen" das
-	Paket "kolab2.0-kdepim3.3-aegypten2.0-client" selektieren
-	und installieren.
+   Use "Add" ("Hinzufügen") to create a new installation source for the
+   local directory you downloaded the software into
+   (/tmp/kolab-download/).
+
+   Disable any other sources to make the package selection easier.
+
+   Select "Finish" ("Beenden")
+
+ - Use "Install and Remove Software" ("Sofware->Installieren oder
+   löschen") to install the software:
+
+   Go to "Filter->Selections" and choose the "Kolab 2.0 KDE-Client"
+   selection.
+
+   "Accept" ("Übernehmen") the package selection.  A dialog will come up
+   informing you that the packages "newpg" and "cryptplug" will be
+   removed.  This is OK as their functionality is included in the new
+   packages.
+
+   Now the software will be intalled.
+   
 
 
 4. Configuration
@@ -125,27 +137,22 @@
 3. Go to the "Install and Remove Software" ("Software installieren oder
    löschen" in the German version) section of yast.  
 
-   You will get a conflict dialog because the new meta package depends
-   on newer versions of the other components but yast for some reason
-   thinks it has to keep the old version of those packages.
-   E.g. version 1.0.0 depends on kdepim3-3.3.proko2.0.beta2 and 1.0.3
-   requires kdepim3-3.3.proko2.0.rc3.  For some reason yast wants to
-   keep kdepim3 at version 3.3.proko2.0.beta2 even though a newer
-   version of kdepim3 is available.
+   You will get a conflict dialog because the old meta package is still
+   installed.  In the conflict dialog, select the meta package and press
+   space until it's marked for deletion, i.e. with a "-" in the first
+   column.  The select "Solve" ("Lösen").
 
-   Resolve this by selecting those packages in the conflict dialog that
-   are marked with "-i-" instead of a simple "i" and press the space bar
-   twice to turn the "-i-" into an ">" ("-i-" means that the version of
-   the package is fixed while ">" means that it should be updated)
+   A new conflict dialog appears which lists kdepim3 with the "-i-" flag
+   which means that it is to be kept at the old version even though a
+   newer version is available.  Press space until kdepim3 is marked with
+   ">" indicating an update.  Again, select "Solve" ("Lösen").
 
-   Yast doesn't handle the dependency on the kde-i18n package properly,
-   so you need to select the "Ignore All" button.
+   Select "Filter/Installationsüberblick".  This will list several
+   packages with "-i-".  These are the packages the old virtual package
+   depended on.  Select them and mark them for update.
 
-   After you have closed the conflict dialog, "Accept" ("Übernehmen") the
-   package installation and the packages will be installed.
+   Then, "Accept" ("Übernehmen") the package installation and the
+   packages will be installed.
 
    Quit yast.
 
-4. Install the i18n package on the commandline with rpm:
-
-   rpm -Uvh noarch/kde3-i18n-de-3.2.1.proko2.0.rc3-0.noarch.rpm





More information about the commits mailing list