Bug#533267: release-notes: Purging uninstalled packages

[Niels Thykier <niels@thykier.net>]

Control: tags -1 pending

On 2014-11-24 07:40, Andrei POPESCU wrote:
> On Du, 23 nov 14, 22:54:20, Niels Thykier wrote:
>>
>> Note, I opted for using dpkg -l + awk rather than aptitude, because a)
>> all users have dpkg + awk and b) we have started recommending apt-get
>> over aptitude again for upgrades.
>  
> Since aptitude is Priority: standard most systems will have it 
> installed. Could it at lease be mentioned as alternative, as the command 
> is much simpler?
> 
>> [...]
> Kind regards,
> Andrei
> 

Hi,

Thanks for the review, I have applied all of your suggested changes (see
the attached patch).

It has been pushed to trunk and will appear on [1] eventually.  Sadly, I
do not know the rebuild frequency, so I do not know "when" it will be.

If there are more comments, by all means send them my way.  The wording
can still be changed.  :)

~Niels

[1]
https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html#nownownow


>From 87b0e5f78f00b9252f2ed53c0f9b1b12dfc8b1a7 Mon Sep 17 00:00:00 2001
From: nthykier <nthykier@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Mon, 24 Nov 2014 06:56:22 +0000
Subject: [PATCH] en/upgrading: Apply comments from Andrei POPESCU, thanks

Signed-off-by: Niels Thykier <niels@thykier.net>

git-svn-id: svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes@10493 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 en/upgrading.dbk | 23 +++++++++++++++--------
 1 file changed, 15 insertions(+), 8 deletions(-)

diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index 4273400..978d77a 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -1270,17 +1270,16 @@ is complete, but there are some other things that should be taken care of
 <section id="purge-removed-packages">
   <title>Purging removed packages</title>
   <para>
-    It is generally advisable to purge packages have been removed.
-    This is especially true, if these have been removed in an earlier
-    release upgrade (e.g. from the upgrade to &oldreleasename;) or
-    from third-party vendors.  In particular, old init.d scripts have
-    been known to cause issues.
+    It is generally advisable to purge removed packages.  This is
+    especially true, if these have been removed in an earlier release
+    upgrade (e.g. from the upgrade to &oldreleasename;) or from
+    third-party vendors.  In particular, old init.d scripts have been
+    known to cause issues.
   </para>
   <caution>
     <para>
-      Purging a package will generally also purge its log files
-      permanently.  If you want to keep these, you should take
-      a copy of them before purging the package.
+      Purging a package will generally also purge its log files, so
+      you might want to back them up first.
     </para>
   </caution>
   <para>
@@ -1298,6 +1297,14 @@ is complete, but there are some other things that should be taken care of
   <screen>
     # apt-get purge $(dpkg -l | awk '/^rc/ { print $2 }')
   </screen>
+  <para>
+    If you use <systemitem role="package">aptitude</systemitem>, you
+    can also use the following alternative to the commands above:
+  </para>
+  <screen>
+    $ aptitude search '~c'
+    $ aptitude purge '~c'
+  </screen>
 </section>
 
 </section>
-- 
2.1.3