From 7d4568d88aa55ec458ae6057fc6347785e6630ed Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Fri, 28 Dec 2007 18:01:29 +0000 Subject: [PATCH] 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 --- pym/portage/dbapi/vartree.py | 5 ----- 1 file changed, 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 -- 2.26.2