archive: Don't use path in error message

path seems to have been freed after the extraction has been started and
therefore we cannot use it any more.

Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

diff --git a/src/libpakfire/archive.c b/src/libpakfire/archive.c
index 280b85c5a9ff82604d1953d2efd3a030bea35ec5..ccd81cc6b630b5c735391071afe845e6cf4b141d 100644 (file)
--- a/src/libpakfire/archive.c
+++ b/src/libpakfire/archive.c
@@ -971,16 +971,14 @@ static int pakfire_archive_extract_entry(struct pakfire_archive* archive,
                        break;
 
                case ARCHIVE_WARN:
-                       ERROR(archive->pakfire, "There was a problem extracting %s: %s\n",
-                               path, archive_error_string(extractor->writer));
+                       ERROR(archive->pakfire, "%s\n", archive_error_string(extractor->writer));
 
                        // Pretend everything has been okay
                        r = ARCHIVE_OK;
                        break;
 
                case ARCHIVE_FATAL:
-                       ERROR(archive->pakfire, "Could not extract file %s: %s\n",
-                               path, archive_error_string(extractor->writer));
+                       ERROR(archive->pakfire, "%s\n", archive_error_string(extractor->writer));
                        return 1;
        }