summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2007-12-28 18:01:29 +0000
committerZac Medico <zmedico@gentoo.org>2007-12-28 18:01:29 +0000
commit7d4568d88aa55ec458ae6057fc6347785e6630ed (patch)
tree9f124c96cc274c4ef08e66cc88cc2c9b2f392800
parent83b30f85ffb8eb345cca706b27499b1dc59179f9 (diff)
downloadportage-7d4568d88aa55ec458ae6057fc6347785e6630ed.tar.gz
portage-7d4568d88aa55ec458ae6057fc6347785e6630ed.tar.bz2
portage-7d4568d88aa55ec458ae6057fc6347785e6630ed.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). svn path=/main/trunk/; revision=9078
-rw-r--r--pym/portage/dbapi/vartree.py5
1 files changed, 0 insertions, 5 deletions
diff --git a/pym/portage/dbapi/vartree.py b/pym/portage/dbapi/vartree.py
index 0c3a0eacb..ba45330b6 100644
--- a/pym/portage/dbapi/vartree.py
+++ b/pym/portage/dbapi/vartree.py
@@ -647,11 +647,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