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

Release Notes: no (usable) aptitude on some arches in woody



As aptitude isn't available (mips/mipsel) or usable (hppa) in woody,
here a patch to reflect that. The patch probably needs big adjustments
when the preupgrade of aptitude is introduced as planned.

I also reflected the patch that you can't use woody's aptitude to
update the packages lists if you have changed the sources.list.

Gruesse,
-- 
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/
Index: release-notes.ent
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/release-notes.ent,v
retrieving revision 1.7
diff -u -r1.7 release-notes.ent
--- release-notes.ent	18 May 2005 23:48:21 -0000	1.7
+++ release-notes.ent	21 May 2005 19:29:47 -0000
@@ -92,6 +92,17 @@
 <![ %sparc   [ <!entity % available-2.6 "INCLUDE"> ]]>
                <!entity % available-2.6 "IGNORE">
 
+<!-- aptitude available and usable in old release -->
+<![ %mips    [ <!entity % available-aptitude "IGNORE"> ]]>
+<![ %mipsel  [ <!entity % available-aptitude "IGNORE"> ]]>
+<![ %hppa    [ <!entity % available-aptitude "IGNORE"> ]]>
+               <!entity % available-aptitude "INCLUDE">
+
+<![ %available-aptitude [
+	<!entity oldreleaseapt "aptitude">
+]]>
+	<!entity oldreleaseapt "apt-get" >
+
 <!-- negatives about architectures -->
 <![ %alpha   [ <!entity % not-alpha   "IGNORE"> ]]>
                <!entity % not-alpha   "INCLUDE">
Index: en/release-notes.en.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml,v
retrieving revision 1.33
diff -u -r1.33 release-notes.en.sgml
--- en/release-notes.en.sgml	18 May 2005 23:48:21 -0000	1.33
+++ en/release-notes.en.sgml	21 May 2005 19:29:49 -0000
@@ -301,7 +301,8 @@
 	  <p>Any package installation operation must be run with superuser
           privileges, so either login as root or use <prgn/su/ or
           <prgn/sudo/ to gain the necessary access rights.</p>
-          
+
+<![ %available-aptitude [
           <p>First the <package>aptitude</package> package needs to be installed.
 	  This is done with:</p> 
 
@@ -313,6 +314,7 @@
           install the &oldreleasename; version of
           
 	  <prgn>aptitude</prgn>.</p>
+]]>
 
 <![ %glibcneedsnewkernel [
 
@@ -427,7 +429,7 @@
           using <prgn/aptitude/. With 
 	  
       	  <example>
-aptitude hold | unhold &lt;package&gt;
+&oldreleaseapt; hold | unhold &lt;package&gt;
       	  </example>
     	    </p>
         </sect1>
@@ -619,14 +621,14 @@
 	  in those directories may be deleted during the upgrade or during any
 	  restart).</p>
  
-	  <p>First <prgn>aptitude</prgn> needs to fetch a list of new and
+	  <p>First <prgn>apt</prgn> needs to fetch a list of new and
 	  updated packages for the new release. This is done by executing:</p>
 	  
 	  <p><example>
-aptitude update
+apt-get update
 	  </example></p>
 
-	  <p>Once <prgn>aptitude</prgn> has information on all the available
+	  <p>Once <prgn>apt</prgn> has information on all the available
 	  packages, the system is almost ready to be fully upgraded. First
           however the <package>doc-base</package> package must be upgraded
           <em>if it is installed</em>. You can find out if it is installed
@@ -640,12 +642,12 @@
           must be upgraded before continuing.</p>
 
           <p><example>
-aptitude install doc-base
+&oldreleaseapt; install doc-base
           </example></p>
           <p>You are now ready to continue with the main part of the
           upgrade. Execute:</p>
 	  <p><example>
-aptitude -f --with-recommends dist-upgrade
+&oldreleaseapt; -f --with-recommends dist-upgrade
 	  </example></p>
 
 	  <p>This will perform a complete upgrade of the system, i.e.  install

Reply to: