Bug 6965

Summary:	Produce rpmdiff outputs after each build
Product:	Infrastructure	Reporter:	Samuel Verschelde <stormi-mageia>
Component:	BuildSystem	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	eeeemail, luigiwalser, pterjan, sysadmin-bugs
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Samuel Verschelde 2012-08-06 12:07:44 CEST

It would be useful for QA (and maybe packagers too) to get the output of rpmdiff after a package is built.

Here is a rules proposal:
- use rpmdiff -iT because time changes are not relevant for our use and pollute the output
- for builds in release, produce:
  * diff with previous version of the package, before it's removed from the repository
- for builds in updates_testing:
  * diff with previous version of the package in updates_testing, if any, before it's removed from the repository
  * diff with the latest version in updates, if any
  * with with the version in release
- for builds in backports_testing
  * diff with previous version of the package in backports_testing, if any, before it's removed from the repository
  * diff with the latest version in backports, if any
  * (maybe not) diff with the version in release?

Pascal Terjan 2012-08-06 12:09:04 CEST

Status: NEW => ASSIGNED
CC: (none) => pterjan

Comment 1 Samuel Verschelde 2012-08-06 12:19:24 CEST

it would be good to be able to access the build logs via a meaningful URL, such as pkgsubmit.mageia.org/rpmdiff/by-pkgid/{RPM pkgid} (when there are duplicates, ie for noarch packages, results should still be the same, so it can give the results for the first one) or pkgsubmit.mageia.org/rpmdiff/by-name/{RPM name} 

Or any other solution that allows, from RPM information, to get its diffs

Status: ASSIGNED => NEW

Comment 2 claire robinson 2012-08-22 17:26:49 CEST

This is an excellent suggestion and would indeed be very useful.

claire robinson 2012-08-22 22:34:27 CEST

CC: (none) => eeeemail

Comment 3 David Walser 2013-07-11 22:16:07 CEST

Yes, it'd be even more useful now that we don't have to run depcheck, we could catch unwanted added dependencies in updates.

It'd be nice if it'd also generate an easy to access list of packages generated by a build, for use in the advisory, in the format we use now.  Currently I generate it by opening the full build log, going to the "Wrote: " lines at the end, copy-pasting those into a file, and running this:
awk -F/ '{print $NF}' file.txt | awk -F. 'BEGIN{OFS="."}{NF=NF-2;print}' -

CC: (none) => luigiwalser

Comment 4 Samuel Verschelde 2014-01-17 16:53:23 CET

Madb now offers this for updates candidates (only), but this would still be good to have it directly from the build system.

Madb also gives a full diff of changes between the RPM archives, feature that we can consider to be added to the present enhancement request.

To access the diff, click the "RPMs" links from http://mageia.madb.org/tools/updates