Bug 14843

Summary:	Need better messages for reproducibility errors where the only difference is in package filename
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Steve Sakoman <steve>
Component:	oe-core other	Assignee:	Unassigned <unassigned>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	randy.macleod, tgamblin, yoann.congal
Version:	4.1
Target Milestone:	6.99
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Steve Sakoman 2022-06-17 14:59:17 UTC

Currently a package name difference between A and B builds will show up as "missing" error:

oe-selftest - INFO - Reproducibility summary for deb: same=11732 different=0 different_excluded=0 missing=5 total=11737

In this particular case there was a difference in the revision field between A and B:

A: liberror-perl-0.17029-r0.0.core2_64.rpm
B: liberror-perl-0.17029-r0.core2_64.rpm

And the code currently classifies this as missing packages in the B build.

Additionally there is no diffoscope output when this happens, so it isn't immediately obvious what is wrong.

Perhaps when "missing" files are detected we should list what is present in the B build?

Comment 1 Randy MacLeod 2023-07-26 21:22:03 UTC

Bulk move of 64 bugs to 4.3 M3 after a quick review.
If a bug is actually fixed, please add a commit link and resolve it.
-- Randy for YP bug team.

Comment 2 Trevor Gamblin 2023-09-14 16:45:43 UTC

Moved to M4.

Comment 3 Randy MacLeod 2023-10-30 15:29:06 UTC

Bulk move to 5.0 M1. -- Randy

Comment 4 Randy MacLeod 2023-12-21 23:28:30 UTC

Bulk move of 52 5.0-M1 bugs to M2.

Comment 5 Randy MacLeod 2024-01-25 14:28:44 UTC

Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.

Comment 6 Randy MacLeod 2024-02-22 19:53:21 UTC

Bulk move of bugs from 5.0-M3 to 5.99.
The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024.

If you disagree, please move back to a 5.[012...]-M* milestone.