I outlined the changes for a clean implementation in
https://github.com/darkdragon-001/apt-btrfs-snapshot/issues/4
Feel free to create a PR.
** Bug watch added: github.com/darkdragon-001/apt-btrfs-snapshot/issues #4
https://github.com/darkdragon-001/apt-btrfs-snapshot/issues/4
--
You
A temporary workaround (it will be overwritten the next time the package
is updated) is to change line 169 of the files /usr/lib/*/dist-
packages/apt_btrfs_snapshot.py. Currently, it says
source = os.path.join(mp, "@")
Change that whatever your subvolume for root is called.
--
You received
Change that TO whatever ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354927
Title:
Creating snapshots for root-containers other than '@' fails
To manage notifications about this bug go to:
I wanted to report separate bug but this seems very related.
I have upgraded to artful a system that is on subvolume @private. However
subvolume @ exists and contains different ubuntu installation. After upgrade it
seems that @ was forked instead of @private.
Happily upgrade succeeded, but if
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt-btrfs-snapshot (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354927
