summaryrefslogtreecommitdiffstats
path: root/pym
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2007-12-28 18:14:00 +0000
committerZac Medico <zmedico@gentoo.org>2007-12-28 18:14:00 +0000
commit4d58e1ff47c64727eff71fe055cdd161d9f882f5 (patch)
tree51b537269934a5efd94addbe42fa0098467e15ef /pym
parentf7845d0df2b3c61973f28daa58c5fd5f230f2de7 (diff)
downloadportage-4d58e1ff47c64727eff71fe055cdd161d9f882f5.tar.gz
portage-4d58e1ff47c64727eff71fe055cdd161d9f882f5.tar.bz2
portage-4d58e1ff47c64727eff71fe055cdd161d9f882f5.zip
Just ignore it when the global counter file does not match
the highest installed COUNTER since it's normal for them to differ in some cases. For example, the global counter file will contain a higher value if the user merges a package and then immediately unmerges it (unmerge does not update the global counter file, but merge does). (trunk r9078) svn path=/main/branches/2.1.2/; revision=9079
Diffstat (limited to 'pym')
-rw-r--r--pym/portage.py5
1 files changed, 0 insertions, 5 deletions
diff --git a/pym/portage.py b/pym/portage.py
index a6a0aee42..e63ec480e 100644
--- a/pym/portage.py
+++ b/pym/portage.py
@@ -6553,11 +6553,6 @@ class vardbapi(dbapi):
writemsg("!!! Initializing COUNTER to " + \
"value of %d\n" % counter, noiselevel=-1)
- if counter != real_counter:
- changed = True
- writemsg("!!! Initializing COUNTER to " + \
- "value of %d\n" % real_counter, noiselevel=-1)
-
# Never trust the counter file, since having a
# corrupt value that is too low there can trigger
# incorrect AUTOCLEAN behavior due to newly installed