Your message dated Wed, 24 Dec 2025 09:33:51 +0000 (UTC)
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #1114650,
regarding borgbackup2: NotADirectoryError after 2.0.0b5-1 -> 2.0.0b19-1 
(trixie) migration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1114650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114650
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: borgbackup2
Version: 2.0.0b19-1
Severity: normal

Dear Maintainer,

I just migrated to Trixie, which upgraded borgbackup from 2.0.0b5-1 to 
2.0.0b19-1.

My daily backup command now fails:

    nice -15 borg2 -r /path/to/repo create --compression zstd,22 {now:%Y%m%d} 
/src/dir

with the following error:

    NotADirectoryError: [Errno 20] Not a directory: 
'/path/to/repo/config/readme'

Indeed, config is a file with the following content:

    [repository]
    version = 2
    segments_per_dir = 1000
    max_segment_size = 524288000
    append_only = 0
    storage_quota = 0
    additional_free_space = 0
    id = 87ef3425223d9827bd36113b5c10231d89c0a51f1a6672c39227214d524286e9

Was there a change in the way the config is stored?

Is there a migration path?

The only reference to this error I could find is this GH issue:

    https://github.com/borgbackup/borg/issues/8652

But it doesn't seem relevant to my case (or I didn't understand how).

Thanks.

Jérôme



-- System Information:
Debian Release: 13.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.43+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages borgbackup2 depends on:
ii  libacl1               2.3.2-2+b1
ii  libc6                 2.41-12
ii  liblz4-1              1.10.0-4
ii  libssl3t64            3.5.1-1
ii  libxxhash0            0.8.3-2
ii  libzstd1              1.5.7+dfsg-1
ii  python3               3.13.5-1
ii  python3-argon2        21.1.0-3
ii  python3-borghash      0.1.0-2
ii  python3-borgstore     0.3.0-2
ii  python3-msgpack       1.0.3-3+b4
ii  python3-packaging     25.0-1
ii  python3-platformdirs  4.3.7-1

Versions of packages borgbackup2 recommends:
ii  fuse3            3.17.2-3
ii  python3-pyfuse3  3.4.0-3+b3

Versions of packages borgbackup2 suggests:
pn  borgbackup2-doc  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Hello, it is mentioned in README.Debian that between beta versions the 
configuration might change in an incompatible way.

Sorry for the borgbackup2 changes, but the API is not really stable yet...

G.

--- End Message ---

Reply via email to