Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

restic 0.9.4 -q outputs open repository #2140

Closed
axllent opened this issue Jan 7, 2019 · 4 comments
Closed

restic 0.9.4 -q outputs open repository #2140

axllent opened this issue Jan 7, 2019 · 4 comments
Labels
state: need implementing cause/request established, need work/solution type: bug

Comments

@axllent
Copy link

axllent commented Jan 7, 2019

Output of restic version

restic 0.9.4 compiled with go1.11.4 on linux/amd64

How did you run restic exactly?

restic -r /<repo> backup /<dir> -q

What backend/server/service did you use to store the repository?

Local

Expected behavior

No output unless an error is encountered.

Actual behavior

Outputs open repository

Do you have any idea what may have caused this?

Upgrade from 0.9.3 to 0.9.4

@fd0
Copy link
Member

fd0 commented Jan 7, 2019

Huh, interesting, that's a bug. FYI: This line won't be printed if stdout is not a terminal (e.g. for cron).

@fd0 fd0 added type: bug state: need triaging need categorizing, labeling, next-step decision labels Jan 7, 2019
@axllent
Copy link
Author

axllent commented Jan 7, 2019

I didn't have this issue before on 0.9.3, and yes, this happens when using cron (system backups etc) ;-)

@fd0
Copy link
Member

fd0 commented Jan 7, 2019

Oh, hm. That's annoying. I'll look into it. :)

@kusalananda
Copy link

kusalananda commented Jan 8, 2019

I don't know if it makes any difference, but I'm seeing this exact thing on macOS (latest) too using restic ("restic 0.9.4 compiled with go1.11.4 on darwin/amd64") installed from Homebrew, when running it from cron.

fd0 added a commit that referenced this issue Jan 10, 2019
@fd0 fd0 added state: need implementing cause/request established, need work/solution and removed state: need triaging need categorizing, labeling, next-step decision labels Jan 10, 2019
@fd0 fd0 closed this as completed in #2142 Jan 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: need implementing cause/request established, need work/solution type: bug
Projects
None yet
Development

No branches or pull requests

3 participants