borgmatic --info not working #101

New Issue

Closed

opened 2018-10-12 19:46:03 +00:00 by sagaciouskjb · 5 comments

sagaciouskjb commented 2018-10-12 19:46:03 +00:00

Copy Link

Hi I'm having a problem with using the --info option. It just errors and says I haven't specified any repos or archives. However if I add a line to specify the archive or repo, it then complains about unrecognized arguments.

Sorry I don't know how to enter code with this editor. Here is a pastebin.

https://pastebin.com/DakY25zR

OS: Ubuntu 16.04.5
Borg: 1.0.11
Borgmatic: How can I checK? I downloaded with "sudo pip3 install --upgrade borgmatic"

Hi I'm having a problem with using the --info option. It just errors and says I haven't specified any repos or archives. However if I add a line to specify the archive or repo, it then complains about unrecognized arguments. Sorry I don't know how to enter code with this editor. Here is a pastebin. https://pastebin.com/DakY25zR OS: Ubuntu 16.04.5 Borg: 1.0.11 Borgmatic: How can I checK? I downloaded with "sudo pip3 install --upgrade borgmatic"

witten added the

question / support

label 2018-10-12 21:21:16 +00:00

witten commented 2018-10-12 21:23:09 +00:00

Owner

Copy Link

Have you generated a borgmatic configuration with generate-borgmatic-configuration as per the README? Without a configuration file, borgmatic --info won't know what repository to operate on.

And you can check the borgmatic version with pip3 show borgmatic.

Have you generated a borgmatic configuration with `generate-borgmatic-configuration` as per the README? Without a configuration file, `borgmatic --info` won't know what repository to operate on. And you can check the borgmatic version with `pip3 show borgmatic`.

sagaciouskjb commented 2018-10-12 21:48:17 +00:00

Author

Copy Link

pip3 show borgmatic says I'm running 1.2.7

Yes I have /etc/borgmatic/config.yaml as well as a couple in /etc/borgmatic.d/

Here is a pastebin of the config.yaml...

https://pastebin.com/r0cqDhPu

I store backups from my server in /mnt/backups/ as well, and have configuration files for each of my HDDs in the /etc/borgmatic.d/ directory.

It's been creating and checking repos just fine, but I tried --info to see how much space I was using so far and got that.

pip3 show borgmatic says I'm running 1.2.7 Yes I have /etc/borgmatic/config.yaml as well as a couple in /etc/borgmatic.d/ Here is a pastebin of the config.yaml... https://pastebin.com/r0cqDhPu I store backups from my server in /mnt/backups/ as well, and have configuration files for each of my HDDs in the /etc/borgmatic.d/ directory. It's been creating and checking repos just fine, but I tried --info to see how much space I was using so far and got that.

witten commented 2018-10-13 00:05:43 +00:00

Owner

Copy Link

Got it. Thanks for the clarification. Borg version 1.0.11 is pretty old at this point. Have you tried upgrading? I can try to reproduce this later on, but it may be worth trying Borg 1.1.7 or thereabouts, if possible, to see if that fixes this. They may have changed their --info sub-command semantics.

Got it. Thanks for the clarification. Borg version 1.0.11 is pretty old at this point. Have you tried upgrading? I can try to reproduce this later on, but it may be worth trying Borg 1.1.7 or thereabouts, if possible, to see if that fixes this. They may have changed their `--info` sub-command semantics.

sagaciouskjb commented 2018-10-13 10:47:51 +00:00

Author

Copy Link

Yep that fixes it, should have realized that version was too old.

Yep that fixes it, should have realized that version was too old.

sagaciouskjb closed this issue 2018-10-13 10:47:51 +00:00

witten commented 2018-10-13 20:39:34 +00:00

Owner

Copy Link

Glad to hear that upgrading Borg cleared that up. For what it's worth, I've just set up a few more end-to-end tests in continuous integration to catch this sort of issue in the future. I've also mentioned a minimum Borg version in the README. Thanks for reporting the issue!

Glad to hear that upgrading Borg cleared that up. For what it's worth, I've just set up a few more end-to-end tests in continuous integration to catch this sort of issue in the future. I've also mentioned a minimum Borg version in the README. Thanks for reporting the issue!

👍 1

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#101

No description provided.