Bug 3857 - ERROR: Package version for package matchbox-wm-staticdev went backwards which would break package feeds
Summary: ERROR: Package version for package matchbox-wm-staticdev went backwards which...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: graphics (show other bugs)
Version: 1.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4
Assignee: Beth Flanagan
QA Contact:
URL:
Whiteboard: autobuilder
Depends on:
Blocks:
 
Reported: 2013-02-06 18:53 UTC by Nitin Kamble
Modified: 2013-04-16 08:50 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nitin Kamble 2013-02-06 18:53:55 UTC
Build status: FAILURE
Buildslave for this Build: ab04 
Complete logs for all build steps: http://autobuilder.yoctoproject.org:8010/builders/nightly-x86-64/builds/837 
Build Reason: Triggerable(nightly-x86-64) 
Build Source Stamp: [branch master] 451f2d083d6c05454d2c3366bd09c7fb13fd8e47 
Detailed log of last build step: http://autobuilder.yoctoproject.org:8010/builders/nightly-x86-64/builds/837/steps/shell_29/logs/stdio 
Last 20 lines of "shell_29.stdio" Error log:
ERROR: Package version for package matchbox-wm-dbg went backwards which would break package feeds from (0:1.2+git0+f4394eaed475de6e627d373c5b35ee2cf87072e3-r1 to 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0)
ERROR: Package version for package matchbox-wm-staticdev went backwards which would break package feeds from (0:1.2+git0+f4394eaed475de6e627d373c5b35ee2cf87072e3-r1 to 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0)
ERROR: Package version for package matchbox-wm-dev went backwards which would break package feeds from (0:1.2+git0+f4394eaed475de6e627d373c5b35ee2cf87072e3-r1 to 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0)
ERROR: Package version for package matchbox-wm-doc went backwards which would break package feeds from (0:1.2+git0+f4394eaed475de6e627d373c5b35ee2cf87072e3-r1 to 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0)
ERROR: Package version for package matchbox-wm-locale went backwards which would break package feeds from (0:1.2+git0+f4394eaed475de6e627d373c5b35ee2cf87072e3-r1 to 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0)
ERROR: Package version for package matchbox-wm went backwards which would break package feeds from (0:1.2+git0+f4394eaed475de6e627d373c5b35ee2cf87072e3-r1 to 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0)
Summary: There were 6 ERROR messages shown, returning a non-zero exit code. 
Detailed log of last build step: http://autobuilder.yoctoproject.org:8010/builders/nightly-x86-64/builds/837/steps/shell_39/logs/stdio 
Last 20 lines of "shell_39.stdio" Error log:
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed 
Detailed log of last build step: http://autobuilder.yoctoproject.org:8010/builders/nightly-x86-64/builds/837/steps/shell_40/logs/stdio 
Last 20 lines of "shell_40.stdio" Error log:
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
ERROR: Execution of event handler 'check




The issue looks like caused by downgrading PR value of the recipe matchbox-wm from r1 to r0.

~Nitin
Comment 1 Laurentiu Palcu 2013-02-20 15:06:47 UTC
When the build was made, the matchbox-wm recipe has been just upgraded and the PR reset from r1 to r0. The upgrade commit is: 30996a17f155cf94d89becce6ce764674ab95fab

Technically, the new package version is correct.

Richard,

What's the correct behavior in this case? The new package version seems correct: 0:1.2+git0+686178379e5ad00453d9f6f50b53777372a29e68-r0 !
Comment 2 Richard Purdie 2013-02-20 17:04:01 UTC
The PR Service is not enabled on thje autobuilder. If it has been, the git0 would have become git1 and we wouldn't have seen this failure. I'll reassign this to Beth and we need to talk about if/how we are going to enable that.
Comment 3 Richard Purdie 2013-04-16 08:50:13 UTC
We added an option to suppress these warnings on the autobuilder, this issue is resolved now.