test: update expected checksums

This is necessary as the new version does add new header fields, and so
the binary output, and thus the checksum, changes.

As the tool (rpm builder) is considered a part of the build process,
changing the tool (version) might also change the outcome of the build.

If you want to use the new tool, you need to update the expectation of
the outcome. If you want to keep the expected outcome, you also need
to use the old version of the tool.

Author: ctron

src/it/test17-reproducible-date/verify.groovy

@@ -14,7 +14,7 @@ def verify() {
 def result = verify()
 println "Verify: " + result
 
-def expectedMd5Sum = "a4ce449e0e1b7b9045a6750f7a46301f";
+def expectedMd5Sum = "129cf561ac335e8ddc80da20b27dbb5b";
 def md5sum = generateMD5(new File(basedir, "target/test17-1.0.0-0.200901011100.noarch.rpm"))
 if (md5sum != expectedMd5Sum) {
     System.out.format("RPM MD5 doesn't match -  actual: %s, expected: %s%n", md5sum, expectedMd5Sum);

src/it/test17-reproducible-epoch/verify.groovy

@@ -14,7 +14,7 @@ def verify() {
 def result = verify()
 println "Verify: " + result
 
-def expectedMd5Sum = "36bba4e7aa2b7338cf1537df550db81b";
+def expectedMd5Sum = "03a9d0fcb6021866dd631615235846a4";
 def md5sum = generateMD5(new File(basedir, "target/test17-1.0.0-0.197001010000.noarch.rpm"))
 if (md5sum != expectedMd5Sum) {
     System.out.format("RPM MD5 doesn't match -  actual: %s, expected: %s%n", md5sum, expectedMd5Sum);