create empty DB_CONFIG for rpm first when updating to rpm >= 5.3 to prevent

incompatible configurations to break berkeley db during upgrade

1 files changed, 16 insertions, 0 deletions

diff --git a/URPM.xs b/URPM.xs
index e4ba8dc..1b11530 100644
--- a/URPM.xs
+++ b/URPM.xs
@@ -3329,6 +3329,22 @@ Trans_add(trans, pkg, ...)
       pretend_distepoch(pkg->h, RPMTAG_REQUIRENAME, RPMTAG_REQUIREFLAGS, RPMTAG_REQUIREVERSION);
     }
     remap_suggests(pkg->h);
+    /* If we're going to update to rpm 5.3, we'll create an empty DB_CONFIG
+     * first iff there's no existing DB_CONFIG in place. This will prevent
+     * switching to possibly incompatible configurations during upgrade.
+     */
+    if (!strcmp(get_name(pkg->h, RPMTAG_NAME), "rpm")) {
+      const char *version = get_name(pkg->h, RPMTAG_VERSION);
+      if (rpmvercmp(version, "5.3") >= 0) {
+	char *fn = rpmGetPath("%{_dbpath}", "/DB_CONFIG", NULL);
+	struct stat st;
+	if (stat(fn, &st)) {
+	  FD_t fd = Fopen(fn, "w");
+	  Fclose(fd);
+	}
+	fn = _free(fn);
+      }
+    }
 
     RETVAL = rpmtsAddInstallElement(trans->ts, pkg->h, (fnpyKey)(1+(long)(pkg->flag & FLAG_ID)), update, relocations) == 0;