classes/buildhistory: make the package version backwards error non-fatal

Just make it a bb.error when a package version goes backwards, it
doesn't make sense to fail the build immediately; the error(s) will
still be reflected in bitbake's exit code.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>

diff --git a/meta/classes/buildhistory.bbclass b/meta/classes/buildhistory.bbclass
index ba20914f4517596c9a10bfbea0f09d016a1daf2e..f61890328f18e6b502863a03342fbb9a0f160367 100644 (file)
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -158,7 +158,7 @@ python buildhistory_emit_pkghistory() {
                        last_pr = lastversion.pr
                        r = bb.utils.vercmp((pe, pv, pr), (last_pe, last_pv, last_pr))
                        if r < 0:
-                               bb.fatal("Package version for package %s went backwards which would break package feeds from (%s:%s-%s to %s:%s-%s)" % (pkg, last_pe, last_pv, last_pr, pe, pv, pr))
+                               bb.error("Package version for package %s went backwards which would break package feeds from (%s:%s-%s to %s:%s-%s)" % (pkg, last_pe, last_pv, last_pr, pe, pv, pr))
 
                pkginfo = PackageInfo(pkg)
                pkginfo.pe = pe