Bug 6992

Summary:	Create a tool to check for differences between package versions
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Randy Witt <randy.e.witt>
Component:	deployment	Assignee:	Randy Witt <randy.e.witt>
Status:	VERIFIED FIXED	QA Contact:	Lucian Musat <georgex.l.musat>
Severity:	enhancement
Priority:	Medium+	CC:	alexandru.c.georgescu, bluelightning, bogdanx.a.voiculescu, ionutx.chisanovici, richard.purdie
Version:	1.8
Target Milestone:	1.8 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know
Bug Depends on:
Bug Blocks:	6660, 7328

Description Randy Witt 2014-11-21 19:02:28 UTC

Sometimes changes in metadata can cause new packages to be generated even though the package has no meaningful change. An example of this would be adding comments to a task in a recipe.

So it would be useful to have a tool to try and verify that a package (sstate, rpm, ipk) actually had actual changes. This tool could be used in cases like package feed updating or sdk deployment.

Comment 1 Paul Eggleton 2014-11-24 17:24:55 UTC

This relates to bug 6660 - it should be possible to use the same mechanism for both packages and sstate artifacts.

There may also be some benefit to be had by looking into bug 5866 - if we reduce the differences between binaries built at different times or on different machines in the first place, that should make things easier.

Comment 2 Randy Witt 2015-02-16 20:33:00 UTC

The build-compare tool is now in master and all patches have been submitted or accepted to the upstream build-compare tool.

Comment 3 Ionut Chisanovici 2015-02-23 15:25:37 UTC

Hi Randy,

Can you please paste the master commits so we can see informations about this ?
Also, can you please give us some guide lines on how to test this ?

Thank you,
Ionut C

Comment 4 Randy Witt 2015-02-23 21:58:41 UTC

(In reply to comment #3)
> Hi Randy,
> 
> Can you please paste the master commits so we can see informations about
> this ?
> Also, can you please give us some guide lines on how to test this ?
> 
> Thank you,
> Ionut C

Ionut,

The commit is c0a79410b9ac27c79bd53444567de5546db51d0a in origin/master.

Unfortunately there don't appear to be any upstream tests for build-compare itself.

That being said, this currently isn't being built for any of the images since no one is currently using it. The first usage of it will probably be the tool in bug 7328.

So this is really just adding the recipe and the testing would be building build-compare, nativesdk-build-compare and build-compare-native.

I'm not 100% familiar with the process yet, so if I need to add some QA to do that somehow, let me know.

Comment 5 Lucian Musat 2015-04-09 14:35:26 UTC

Verified in commit a146e8ccfcc9d7f957de60c8634b38bb3431ca04.