From 424129e8d1e91987a9799a49391f1271b069c5cf Mon Sep 17 00:00:00 2001 From: morganamilo Date: Tue, 5 Nov 2019 23:08:26 +0000 Subject: pacman: clarify error when alpm fails to init Currently pacman is hard coded to print the dbpath, then the error alpm returned. Even though the error could really be caused by anything. So instead just print the arugemnts given to alpm and not assume the resulting error message is releated to either path. Fixes FS#59595 Signed-off-by: morganamilo Signed-off-by: Allan McRae --- src/pacman/conf.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pacman/conf.c b/src/pacman/conf.c index 468a3e02..3b475151 100644 --- a/src/pacman/conf.c +++ b/src/pacman/conf.c @@ -766,8 +766,8 @@ static int setup_libalpm(void) /* initialize library */ handle = alpm_initialize(config->rootdir, config->dbpath, &err); if(!handle) { - pm_printf(ALPM_LOG_ERROR, _("failed to initialize alpm library\n(%s: %s)\n"), - alpm_strerror(err), config->dbpath); + pm_printf(ALPM_LOG_ERROR, _("failed to initialize alpm library:\n(root: %s, dbpath: %s)\n%s\n"), + config->rootdir, config->dbpath, alpm_strerror(err)); if(err == ALPM_ERR_DB_VERSION) { fprintf(stderr, _("try running pacman-db-upgrade\n")); } -- cgit v1.2.3-24-g4f1b