https://bugs.koozali.org/show_bug.cgi?id=11997

--- Comment #7 from Brian Read <[email protected]> ---
yum update on my Centos7 build system is unable to update to the latest
devtools:

Resolving Dependencies
--> Running transaction check
---> Package e-smith-devtools.noarch 0:2.6.0-10.el7.sme will be updated
---> Package e-smith-devtools.noarch 0:2.6.0-12.el7.sme will be an update
--> Finished Dependency Resolution

Dependencies Resolved

=========================================================================================================================
 Package                      Arch               Version                     
Repository                            Size
=========================================================================================================================
Updating:
 e-smith-devtools             noarch             2.6.0-12.el7.sme            
e-smith-devtools-updates              30 k

Transaction Summary
=========================================================================================================================
Upgrade  1 Package

Total download size: 30 k
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for e-smith-devtools-updates
warning:
/var/cache/yum/x86_64/7/e-smith-devtools-updates/packages/e-smith-devtools-2.6.0-12.el7.sme.noarch.rpm:
Header V4 RSA/SHA1 Signature, key ID 56873151: NOKEY
Public key for e-smith-devtools-2.6.0-12.el7.sme.noarch.rpm is not installed
e-smith-devtools-2.6.0-12.el7.sme.noarch.rpm                                   
                  |  30 kB  00:00:00     


Public key for e-smith-devtools-2.6.0-12.el7.sme.noarch.rpm is not installed
[brianr@smebuild contribs10]$ 

And note that this is -12 whereas the required version is -13

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/

Reply via email to