-
Notifications
You must be signed in to change notification settings - Fork 236
diff does not report updated packages #297
Comments
hey @scopev24, thanks for the issue. would you be interested in contributing a |
Hi, sorry for the delay. I wrote about yum because that's what you typically use. So let me rephrase the issue I think I'm seeing: If you just run a bash in the aforementioned images, and the run
in both - you'll get a list of packages. Just save that as a text file and diff it using your favorite tool. So, since container-diff has a rpm differ, I'd expect it to pickup all changed packages. I implemented my own simple rpm differ, which does just that, run the rpm list command mentioned above and diffs the two resulting lists. Here's the output of container-diff when diffing centos:7.6.1810 and centos:7.5.1804:
And here's the output of my own tool:
As you can see, a whole lot more packages changed. It seems as if container-diff only compares the rpm version, not the release. As such, if the version changes (e.g. audit-libs from 2.8.1 to 2.8.4) the change is picked up. But if only the release changes (e.g. zlib from 1.2.7-17 to 1.2.7-18) the change is omitted. These are mainly security updates, so I think it is very important for them to show up in the rpm diff. |
@scopev24 ahh, sorry I misunderstood your issue originally. I think you're right, it looks like the rpm differ is ignoring the release when retrieving the list of packages from the database: container-diff/differs/rpm_diff.go Lines 52 to 55 in 2f96a09
I haven't tested it, but I think just by changing the format of the query passed to |
Hi! |
NP. Looks like we've got a fix for it. |
When comparing images using diff, there seem to be a lot of packages missing, specifically those from a "yum upgrade" run.
Expected behavior
I'd expect to see the packages that got upgraded during "yum upgrade":
Actual behavior
Only package tzdata shows up:
Information
Steps to reproduce the behavior
The upgrade process shows and upgrades the aformentioned packages.
The text was updated successfully, but these errors were encountered: