You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if its just the package name that is the problem or if the binary name is problematic too. If its just the former, then I see no reason why we can't submit as go-task or taskfile. However maybe someone with more Debian packaging experience can suggest the best way forwards.
@danon There's no reason why it cannot be released as go-task. Obviously, the name task is already taken, so that's not going to happen. However, users can just set up their own aliases if they want to. I believe this is what the arch package maintainers did.
At this time, I don't have the bandwidth to go through the process of adding it to apt myself, but anyone else willing to help is more than welcome.
The .deb package that is released in the APT repository listed here is marked as conflicting with the package taskwarrior. This makes it impossible to install the .deb package for task and the .deb package for taskwarrior at the same time. Debian has solutions for conflicting binary names, it seems to me we should use them.
Activity
pd93 commentedon Jan 2, 2025
Just an FYI on this issue. Agreed that it would be nice to have Task on
aptand any help with doing so is welcome.There is an ITP (Intent to Package) that was opened in March 2023 by someone. However, this hasn't progressed much since then. Mainly because of the naming conflict with Taskwarrior.
Related:
I'm not sure if its just the package name that is the problem or if the binary name is problematic too. If its just the former, then I see no reason why we can't submit as
go-taskortaskfile. However maybe someone with more Debian packaging experience can suggest the best way forwards.danon commentedon Jan 24, 2025
@pd93 Given that the related issues are closed now, does this mean that the package can be released for debian-based distros?
pd93 commentedon Jan 24, 2025
@danon There's no reason why it cannot be released as
go-task. Obviously, the nametaskis already taken, so that's not going to happen. However, users can just set up their own aliases if they want to. I believe this is what the arch package maintainers did.At this time, I don't have the bandwidth to go through the process of adding it to apt myself, but anyone else willing to help is more than welcome.
vmaerten commentedon Dec 12, 2025
This is done now! 🔥
https://taskfile.dev/docs/installation#apt
Flimm commentedon Oct 14, 2026
The .deb package that is released in the APT repository listed here is marked as conflicting with the package
taskwarrior. This makes it impossible to install the .deb package fortaskand the .deb package fortaskwarriorat the same time. Debian has solutions for conflicting binary names, it seems to me we should use them.