[Borgbackup] Some minor issues

[Hans-Peter Jansen]

On Freitag, 17. Juni 2016 10:33:40 Adrian Klaver wrote:
> On 06/17/2016 10:31 AM, Hans-Peter Jansen wrote:
> > Hi Adrian,
> > 
> > On Freitag, 17. Juni 2016 09:33:56 Adrian Klaver wrote:
> >> Using 1.0.2, when I run create with -v --stats and prune with -v --list I
> >> get the below returned from my cron job:
> >> 
> >> -------------------------------------------------------------------------
> >> --- -- Archive name: b_repo-061616_1830
> >> Archive fingerprint:
> >> 056a38f007392ab1fad5d69caeb1b1982b6ec8947fa1c286392677ce632c490e Time
> >> (start): Thu, 2016-06-16 18:30:02
> >> Time (end):   Thu, 2016-06-16 18:30:02
> >> Duration: 0.23 seconds
> >> Number of files: 6
> >> -------------------------------------------------------------------------
> >> --->> 
> >> -- Original size      Compressed size    Deduplicated size This archive:
> >>           19.80 kB             20.15 kB              1.57 kB All 
archives:
> >>             372.59 kB            379.13 kB             91.36 kB
> >>             
> >>                        Unique chunks         Total chunks
> >> 
> >> Chunk index:                      50                  152
> >> -------------------------------------------------------------------------
> >> ---> 
> > The point is, if you run "borg create --stats" (without -v), it doesn't
> > print the stats, which is rather counter intuitive...
> 
> Well it is documented:
> 
> http://borgbackup.readthedocs.io/en/stable/usage.html
> "
> Type of log output
> 
> The log level of the builtin logging configuration defaults to WARNING.
> This is because we want Borg to be mostly silent and only output
> warnings, errors and critical messages.
> 
> ...
> 
> Warning
> 
> While some options (like --stats or --list) will emit more informational
> messages, you have to use INFO (or lower) log level to make them show up
> in log output. Use -v or a logging configuration.
> "

Well, the term "more" doesn't match users experience, since nothing is printed 
at all. In other words, without looking at the repo with list after create, 
you cannot see, if borg did anything, if -v wasn't given (intentionally).

Let's stop this fruitless discussion, it's suboptimal behavior, and either 
Thomas want to fix it or somebody else (incl. me) sends in a PR with a fix.

The aim of posting this here was discussing the "right" behavior.

Pete