[PR #20] [MERGED] Issue #18 - Zmbackup wasn't doing the restore because it loads the wrong config file #165

New issue

Closed

opened 2026-02-27 08:14:42 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 08:14:42 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/lucascbeyeler/zmbackup/pull/20
Author: @lucascbeyeler
Created: 3/22/2017
Status: ✅ Merged
Merged: 3/22/2017
Merged by: @lucascbeyeler

Base: master ← Head: patch-2

📝 Commits (7)

5c23627 Merge pull request #12 from lucascbeyeler/patch-01
7716de6 Merge pull request #14 from lucascbeyeler/patch-01
18f3878 Merge pull request #17 from lucascbeyeler/patch-2
7b59ea6 Including logo
1b48743 Merge branch 'development' of github.com:lucascbeyeler/zmbackup into patch-2
444bf88 Issue #18 - zmbackup restore wasn't executing because was looking for the old config folder
543e92e Updating the version to 1.0.2

📊 Changes

2 files changed (+7 additions, -7 deletions)

View changed files

📝 src/zmbackup (+4 -4)
📝 src/zmbackup-share/zmbackup-validate-config-file (+3 -3)

📄 Description

When someone run the zmbackup -r -ldp, the following error occur:

-su: /etc/zmbkpose/zmbackup.conf: No such file or directory

This happens because the correct folder is zmbackup, and zmbkpose was used before zmbackup reached its first stable release.

This merge is to correct this issue.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/lucascbeyeler/zmbackup/pull/20 **Author:** [@lucascbeyeler](https://github.com/lucascbeyeler) **Created:** 3/22/2017 **Status:** ✅ Merged **Merged:** 3/22/2017 **Merged by:** [@lucascbeyeler](https://github.com/lucascbeyeler) **Base:** `master` ← **Head:** `patch-2` --- ### 📝 Commits (7) - [`5c23627`](https://github.com/lucascbeyeler/zmbackup/commit/5c2362712b86caaf1918bd6e30d965f13b9fe435) Merge pull request #12 from lucascbeyeler/patch-01 - [`7716de6`](https://github.com/lucascbeyeler/zmbackup/commit/7716de64dff2fe0a9260d4cbf7b3a3d33a17827b) Merge pull request #14 from lucascbeyeler/patch-01 - [`18f3878`](https://github.com/lucascbeyeler/zmbackup/commit/18f38781edc7b92c2f35d261cea27fa898282501) Merge pull request #17 from lucascbeyeler/patch-2 - [`7b59ea6`](https://github.com/lucascbeyeler/zmbackup/commit/7b59ea64c0f7fe75948ff0d50510a03fd32969a7) Including logo - [`1b48743`](https://github.com/lucascbeyeler/zmbackup/commit/1b487433f3950ea11c74bdeefb65a59069c714dd) Merge branch 'development' of github.com:lucascbeyeler/zmbackup into patch-2 - [`444bf88`](https://github.com/lucascbeyeler/zmbackup/commit/444bf88ee730626d84441c8f43bd0b0e73a24a6f) Issue #18 - zmbackup restore wasn't executing because was looking for the old config folder - [`543e92e`](https://github.com/lucascbeyeler/zmbackup/commit/543e92eed59517c97b2dbad29aea5f6643dde544) Updating the version to 1.0.2 ### 📊 Changes **2 files changed** (+7 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `src/zmbackup` (+4 -4) 📝 `src/zmbackup-share/zmbackup-validate-config-file` (+3 -3) </details> ### 📄 Description When someone run the zmbackup -r -ldp, the following error occur: `-su: /etc/zmbkpose/zmbackup.conf: No such file or directory` This happens because the correct folder is zmbackup, and zmbkpose was used before zmbackup reached its first stable release. This merge is to correct this issue. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>