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

updates *always* updating same three (3) packages ???



Recently, apt-get update updates the same three (3) packages -- to
themselves -- since that version to which they update is already
installed, and functioning ;>

# sudo dpkg -l po-debconf spamassassin spamc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  po-debconf     0.7.1          Manage translated Debconf templates files wi
ii  spamassassin   2.55-3         Perl-based spam filter using text analysis
ii  spamc          2.55-3         Client for perl-based spam filtering daemon


# sudo apt-get -u --fix-missing dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages have been kept back
  aptitude debconf kdeartwork libsane synaptic w3m 
The following packages will be upgraded
  po-debconf spamassassin spamc 
3 packages upgraded, 0 newly installed, 0 to remove and 6  not upgraded.
Need to get 0B/591kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n] 
Preconfiguring packages ...
(Reading database ... 98788 files and directories currently installed.)
Preparing to replace po-debconf 0.7.1 (using
.../po-debconf_0.7.1_all.deb) ...
Unpacking replacement po-debconf ...
Preparing to replace spamc 2.55-3 (using
.../archives/spamc_2.55-3_i386.deb) ...
Unpacking replacement spamc ...
Preparing to replace spamassassin 2.55-3 (using
.../spamassassin_2.55-3_all.deb) ...
Stopping SpamAssassin Mail Filter Daemon: spamd.
Unpacking replacement spamassassin ...
Setting up po-debconf (0.7.1) ...

Setting up spamc (2.55-3) ...
Setting up spamassassin (2.55-3) ...
Starting SpamAssassin Mail Filter Daemon: spamd.



I agree, this does not appear to indicate broken functionality; but, I
am quite curious how this can happen.

If dpkg -l knows a package is at a given level, how can apt-get update
even try to install that same package level?

What do you think?

-- 
Best Regards,

mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know.  The more I know, the more I know I don't know . . .
--

Attachment: pgpbDRc3d5WMu.pgp
Description: PGP signature


Reply to: