Overview
Request 1142136 revoked
New package task version 3.34.1 is a CLI tool to run build tasks defined as YAML
- Created by jfkw
- In state revoked
- Supersedes 1058040
-
Open review for
opensuse-review-team
- Open review for openSUSE:Factory:Staging:adi:3
found conflict of task-3.19.1-1.2.x86_64 with taskwarrior-2.6.2-1.4.x86_64 /usr/bin/task /usr/share/doc/packages/task/README.md
Request History
jfkw created request
New package task version 3.34.1 is a CLI tool to run build tasks defined as YAML
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
staging-bot added openSUSE:Factory:Staging:adi:3 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:3"
staging-bot accepted review
Picked "openSUSE:Factory:Staging:adi:3"
licensedigger accepted review
The legal review is accepted preliminary. The package may require actions later on.
jfkw revoked request
Revoke for rework to find non-conflicting name for task binary which conflicts with taskwarrior
What;s the relation of this to taskwarrior? Is this in fact the same package, but renamed?
They're unrelated. This task is a build tool while taskwarrior is a relatively popular TODO list manager.
Thanks for identifying the conflict. I will revoke and work with the package contributor to find a non-conflicting name for this task binary. It is a build tool and unrelated to task warrior.
We can create our own non-conflicting name e.g. task-build or taskfile (their build job file) . I checked with upstream to find/ask if they had a recommended non-conflicting name we could harmonize with other distro packages. They do not, see below. As an alternative, would a Conflicts: taskwarrior clause be acceptable for task to enter Factory?
I checked the upstream task issue tracker, and others involved in packaging for various distros have reported the conflict with taskwarrior. https://github.com/go-task/task/issues/697 Upstream declines to rename their binary, citing the number of users with taskwarrior and task on the same system are small, plus side effects breaking task usage e.g. github actions that assume that specific for the binary.
I think on balance a renamed binary will be packager's best option. I am not a user of task (or taskwarrior) but will check with our package contributor @ph03nix for thoughts on how that would impact usability.
@ph03nix I will create an SR to the devel project with a proposed rename and add your review. We can discuss the details or decline in those comments.