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

Bug#401317: marked as done (release-notes: Chapt 4. use of aptitude etc. for upgrade)

Your message dated Wed, 4 Apr 2007 05:57:46 -0700
with message-id <20070404125746.GG17393@dario.dodds.net>
and subject line Chapt 4. use of aptitude etc for upgrade
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: release-notes
Version: etch-cvs-20061201
Severity: normal
Tags: patch

I understand "Chapter 4 - Upgrades from previous releases" gives generic
description for upgrade and it has been recommending to use aptitude.

But its contents looks still just as the result of  s/apt-get/aptitude/
and s/apt-cache/aptitude/ .

Considering aptitude's cli was a new additional feature and aptitude
comes with very solid visual mode, we should use it.  It also had great
enhancement for etch.

The most of the required package management activity can be done just
with aptitude (no special purpose packages such as dpig, waijig, etc.) .

Also why we mention just -f option for using aptitude.  Once after we do
partial upgrade of aptitude, we have access to new "Resolver" feature.

In light of above thoughts, I provide attached patch.  I will appreciate
if someone polish my English and include some of the valid contents to
release-notes :-)  (Oh, I bet there are some spell and grammar issues.)


REFERENCE DATA:

  # aptitude -y -s -f --without-recommends install aptitude
...
8 packages upgraded, 17 newly installed, 0 to remove and 118 not upgraded.
Need to get 0B/11.9MB of archives. After unpacking 19.6MB will be used.

This is for the mini upgrade.  20 MB is not much.  So partial upgrade
should not be too much of system trouble.  libc is upgraded in this
process.
-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
        Osamu Aoki <osamu@debian.org>  Yokohama Japan, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://qref.sf.net and http://people.debian.org/~osamu
 `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract


--- release-notes.en.sgml-old	2006-12-02 13:35:16.000000000 +0900
+++ release-notes.en.sgml-new	2006-12-02 23:02:17.000000000 +0900
@@ -388,6 +388,8 @@
           directly related to the upgrade process but which could still be
           relevant.</p>
 
+       <sect1><heading>Backup any data or configuration information</heading>
+
           <p>Before upgrading your system, it is strongly recommended that
           you make a full backup, or at least backup any data or
           configuration information you can't afford to lose. The upgrade
@@ -417,11 +419,18 @@
           reboot will not normally be necessary, unless you also plan to
           upgrade your kernel.</p>
 
-          <!-- TODO: Is not necessary to change the kernel? e.g. udev ? -->
+       <sect1><heading>Prepair for the safe environment for upgrade</heading>
 
-          <p>Distribution upgrade should be done either locally from a
-          textmode virtual console (or a directly connected serial
-          terminal), or remotely via an <prgn/ssh/ link.</p>
+          <p>Distribution upgrade should better be done locally from a
+          textmode virtual console or a directly connected serial
+          terminal.</p>
+
+	  <p>If the upgrade needed to be done remotely with reasons, you should
+	  connect to the system via <prgn/ssh/ link.  In order to gain extra
+	  safety margin, we suggest you to run upgrade processes in the virtual
+	  console provided by the <prgn/screen/ program which enables the safe
+	  reconnection and ensures the uninterrupted upgrade processes even if
+	  the remote connection process fails by chance.
 
           <p><strong/Important!/ You should <em/not/ upgrade using <prgn/telnet/,
           <prgn/rlogin/, <prgn/rsh/, or from an X session managed by <prgn/xdm/,
@@ -432,6 +441,7 @@
 
           <!-- TODO: surely gdm/kdm are sane? -->
 
+
           <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>
@@ -439,6 +449,13 @@
           <p>The upgrade has a few preconditions; you should check them
           before actually executing the upgrade.</p>
 
+       <sect1><heading>Make system compatible with upgrades</heading>
+
+	  <p>If upgrades require particular configuration or package mentioned
+	  in <ref id="information">, please update and install them first. You
+	  must pay attention to the requrement for the kernel and its
+	  relatede programs such as <package/udev/.
+	  
        <sect1><heading>Make sure you have sufficient space for the upgrade</heading>
 
        <p>You have to make sure before upgrading your system that you have
@@ -482,9 +499,17 @@
        <p>
        <list>
 <!-- JFS: Does aptitude to 'apt-get autoclean' by itself? -->
+<!--  OA: yes if configured.  Default is no, I think.
+               From config option: "Aptitude::Autoclean-After-Update" or 
+               from menu:          "Options → Miscellaneous" -->
        <item>Remove packages that have been previously downloaded for
        installation (at <file>/var/cache/apt/archive</file>), cleaning up the
-       package cache by running <prgn>apt-get clean</prgn>.
+       package cache by running <prgn>apt-get autoclean</prgn> or
+       <prgn>aptitude autoclean</prgn> will remove unused package files.  If
+       that does not give you enough space, you can clean up the package cache
+       further by running <prgn>apt-get clean</prgn> or <prgn>aptitude
+       clean</prgn>.  Please note <prgn/aptitude/ has visual mode so you can do
+       everything interactively.
 
 <!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ?
      Enrico's script shows files that occupy space in a given partition
@@ -495,13 +520,22 @@
        <prgn/popcon-largest-unused/ to list the packages you do not use in the
        system that occupy the most space. You can also use <prgn/deborphan/
        or <prgn/debfoster/ to find obsolete packages (see 
-       <ref id="obsolete">)
+       <ref id="obsolete">) . Alternatively you can start <prgn/aptitude/ into
+       "visual mode" and find obsolete packages under "Obsolete and Locally
+       Created Packages".
        
        <item>Remove packages that take up too much space and you do not 
        have an immediate need for (you can always reinstall them after the
-       upgrade). You can list packages that take up most of the disk space
-       with <prgn/dpigs/ (available in the  <prgn/debian-goodies/ package)
-       or with <prgn/wajig/ (running <prgn>wajig size</prgn>).
+       upgrade). You can list packages that take up most of the disk space with
+       <prgn/aptitude/ .  Start <prgn/aptitude/ into "visual mode", select
+       "Views" and "New Flat Package List" (this menu entry is available only
+       after etch version), press "l" and enter "~i", press "S" and enter
+       "~installsize", then it will give you nice list to work with.  Doing
+       this after partial upgrade described in <ref id="upgrading_aptitude">
+       should give you access to this new feature.
+       You can also do the same with
+       <prgn/dpigs/ (available in the  <prgn/debian-goodies/ package)
+       or with <prgn/wajig/ (running <prgn>wajig size</prgn>). 
        
        <item>Temporarily move to another system, or permanently remove, system
        logs residing under <file>/var/log/</file>.
@@ -509,7 +543,7 @@
        </list></p>
         </sect1>
 
-        <sect1 id="glibc-kernel"><heading>Support for 2.2-kernels has been dropped</heading>
+        <sect1 id="glibc-kernel"><heading>Support for 2.4-kernels has been dropped</heading>
           <p>In case you run a kernel prior to 2.4.1,
           you need to upgrade to (at least) the
           2.4-series before upgrading the <package/glibc/, which means:
@@ -568,7 +602,7 @@
           or
 
           <example>
-# dpkg --get-selections &gt; ~/curr-pkgs.txt
+# dpkg --get-selections "*" &gt; ~/curr-pkgs.txt
           </example></p>
 
           <p>It is desirable to remove any holds before upgrading. If any
@@ -583,6 +617,9 @@
 # aptitude search "~ahold" | grep "^.h"
           </example></p>
 
+	  Alternatively, from <prgn/aptitude/ "visual mode", you can gain nice
+	  list interactively by pressing "l" and enter "~ahold" .
+
           <p>If you want to check which packages you had on hold for
           <prgn/apt-get/, you should use
           <example>
@@ -599,6 +636,9 @@
 # aptitude hold <var>package_name</var>
           </example>
           </p>
+  
+	  Alternatively, from <prgn/aptitude/ "visual mode", you can hold
+	  package interactively by pressing "=".
 
           <p>If there is anything you need to fix, it is best to make sure your
           <file/sources.list/ still refers to &oldreleasename; as explained in
@@ -834,6 +874,8 @@
 
 
 <!-- FJP: This next section can probably be dropped for etch -->
+<!--  OA: This next section may probably be dropped after etch but not for etch -->
+
         <sect1 id="upgrading_aptitude"><heading>Upgrading aptitude</heading>
 
           <p>Upgrade tests have shown that &releasename;'s version of
@@ -892,6 +934,16 @@
           <package/apt/ to attempt to correct a system with broken
           dependencies in place. <package/apt/ does not allow broken package
           dependencies to exist on a system.</p>
+	  
+	  <p>Alternatively, if <prgn/aptitude/ is run without <tt/--fix-broken/
+	  (or just <tt/-f/) option in above example, you will be presented with
+	  following prompt when some conflict resolution is needed.
+<example>
+Do you want to continue? [Y/n/?]
+</example>
+	  Press "Y" if you want to proceed or press "e" if you interactively
+	  want to resolve conflicts.  (The etch version of <prgn/aptitude/ has
+	  very advanced resolution mechanism under "Resolver".)
 
         </sect1>

--- End Message ---
--- Begin Message --- 
Hi Osamu,

Thank you for all of your work to test upgrades from sarge to etch.  We
believe that the current version of the release notes documents a viable
upgrade path that addresses all of the upgrade issues reported here.

If you believe this is not the case, it would be helpful if you would open a
new bug report for clarity which lists just those problems that still apply,
since this bug log is now quite long and would surely be a distraction from
resolving your specific problem.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

--- End Message ---
Reply to: