Skip to content

duplicity 3.0.2-1 fails with "ValueError: Unknown level: 'Level NOTICE'"

Description:

When running duplicity recently, the backup fails with:

Traceback (most recent call last):
  File "/usr/lib/python3.12/concurrent/futures/process.py", line 242, in _process_worker
    initializer(*initargs)
  File "/usr/lib/python3.12/site-packages/duplicity/backend_pool.py", line 180, in _process_init
    logger = multiprocessing.log_to_stderr(level=logging.getLevelName(log.LevelName(config.verbosity)))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/multiprocessing/context.py", line 162, in log_to_stderr
    return log_to_stderr(level)
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/multiprocessing/util.py", line 101, in log_to_stderr
    logger.setLevel(level)
  File "/usr/lib/python3.12/logging/__init__.py", line 1514, in setLevel
    self.level = _checkLevel(level)
                 ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/logging/__init__.py", line 213, in _checkLevel
    raise ValueError("Unknown level: %r" % level)
ValueError: Unknown level: 'Level NOTICE'

This is a known upstream issue, fixed in this commit: https://gitlab.com/duplicity/duplicity/-/commit/3f94bf1f9476903747e2dc0982a161beb40c3b46 .

I'm not 100% sure what other package in Archlinux makes this fail (I assume duplicity is not broken on most distros?), and this will be fixed in 3.0.3 when that's released.

Additional info:

Steps to reproduce:

duplicity --verbosity notice \
         --no-encryption \
         --full-if-older-than 60D \
         --num-retries 3 \
         --concurrency 4 \
         --volsize 100 \
         --progress \
         --archive-dir "$archive" \
         --log-file "$log" \
         --exclude /home/drinkcat/nobackup \
         "/home/drinkcat" "$dest"

I believe the issue only happens because of --concurrency 4 and --verbosity notice? (see commit message) But I didn't try.

Edited by Nicolas Boichat
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information