Skip to content

Taskwarrior 3.0.0 requires user intervention before and after the upgrade

Description:

The 3.0.0 release of Taskwarrior requires the user to migrate the data to the new storage backend used by this release. This package doesn't seem to have automated that neither have we received an email from Arch Linux about the necessary manual intervention. I have verified that the user ends up with an empty task database when upgrading to 3.0.0-1.

Additional info:

Steps to reproduce:

  1. Have task package installed with a release prior to 3.0.0-1
  2. Have a non-empty database (e.g. create some tasks)
  3. Upgrade the task package to 3.0.0-1
  4. Run task to see that no tasks are shown
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information