> From the BZ this is just a problem with cv (aka. current value)
> being None? Looks like it's failing to do a checksum, is that
> the only time this happens?
Yes, that's the likely cause. "yum verify pkg" ran as user triggers
this when pkg contains go-r files. Reporting "checksum does not match"
seems to be redundant in this case.
commit c8180d09929a5b686016d8d4c201bc53674265b4
Author: Zdeněk Pavlas <zpav...@redhat.com>
Date: Fri Nov 9 14:44:29 2012 +0100
"checksum NA" implies "checksum does not match". BZ 825272.
diff --git a/yum/packages.py b/yum/packages.py
index 7a2624a..1ce45f4 100644
--- a/yum/packages.py
+++ b/yum/packages.py
@@ -2027,7 +2027,7 @@ class YumInstalledPackage(YumHeaderPackage):
my_csum = digest_type + ':' + my_csum
my_st_size = fp.read_size
- if pf.verify_digest and my_csum != csum:
+ if pf.verify_digest and my_csum != csum and my_csum:
prob = _PkgVerifyProb('checksum',
'checksum does not match',
ftypes)
prob.database_value = csum
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
