← All tasks
cppGothenburgBitFactory/taskwarrior #4174Not a task: not reproduced

default.theme include path resolves to build directory path instead of installed path

envgap__GothenburgBitFactory__taskwarrior-4174

01 / FAILURE SIGNATURE

As reported upstream

Since Taskwarrior v3.5.0, running task fails immediately with an error about a missing default.theme file. The path in the error message points to a build-time directory (/build/task/src/task/doc/rc/default.theme) rather than the actual installed location.
Not a benchmark task.
  • In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit
c1958786deb9be8b245b4fc4c3efd0258cd70782
Manifest
src/CMakeLists.txt
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

GothenburgBitFactory/taskwarrior #4174 · read the original issue
# Summary

Since Taskwarrior v3.5.0, running task fails immediately with an error about a missing default.theme file. The path in the error message points to a build-time directory (/build/task/src/task/doc/rc/default.theme) rather than the actual installed location.

# Environment

- Taskwarrior version: 3.5.0
- OS: Arch Linux
- Installation method: pacman package

# Steps to reproduce

1. Install Taskwarrior 3.5.0.
2. Run task.

# Expected behavior

Taskwarrior should start normally and display the task list.

# Actual behavior
```
$ task
Could not read include file '/build/task/src/task/doc/rc/default.theme'.
```
The command exits without any further output.

# Suspected reason
Regression introduced in v3.5.0, most likely by PR #4124.

The path /build/task/src/task/doc/rc/default.theme looks like a build-tree path that was substituted at configure/build time instead of the installation path.
Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]