I wouldn't tag this bug with a medium priority as in the actual state apt-btrfs is broken and potentially harmful.
But what's really disturbing here is that while this error was reported almost a year ago apt-btrfs is still shipped in its current dangerous state!
I wonder what is Ubuntu/Canonical policy about shipping a broken administrative tool that can potentially disrupt a production environment.
If there isn't a tag-line for a fix apt-btrfs should at least be removed from the official repositories until it is working as expected again, we are talking here about a system-level bug, not a fancy GUI one that could be annoying but doesn't jeopardize user's data.
I wouldn't tag this bug with a medium priority as in the actual state apt-btrfs is broken and potentially harmful.
But what's really disturbing here is that while this error was reported almost a year ago apt-btrfs is still shipped in its current dangerous state!
I wonder what is Ubuntu/Canonical policy about shipping a broken administrative tool that can potentially disrupt a production environment.
If there isn't a tag-line for a fix apt-btrfs should at least be removed from the official repositories until it is working as expected again, we are talking here about a system-level bug, not a fancy GUI one that could be annoying but doesn't jeopardize user's data.
My 2c...
Regards!