View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008019 | Taler | exchange | public | 2023-12-20 09:42 | 2024-03-07 20:47 |
Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | git (master) | ||||
Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
Summary | 0008019: taler-terms-generator does not respect file system hierarchy standard | ||||
Description | The Debian package installs the sample ToS files in /usr/share/taler/terms. That is completely fine. However, the taler-terms-generator then generates files based on that also in /usr/share/taler/terms. That violates the file system hierarchy standard, because /usr/share is supposed to be read-only. Instead, the ToS should be served from /etc/taler/terms or /var/lib/taler/terms. While this sounds like nitpicking, it has caused real issues before: Sandcastle-ng mounts /usr/share/taler/terms as a volume, so the results of taler-terms-generator can be cached between runs. But this also means that newer versions of the sample ToS shipped with the package will not be picked up. Furthermore, the current path encourages users to make modifications that then will be overwritten by package updates. We should not mix up immutable data that is shipped with the package and generated or user-modified files! | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2023-12-20 09:42 | Florian Dold | New Issue | |
2023-12-20 09:42 | Florian Dold | Status | new => assigned |
2023-12-20 09:42 | Florian Dold | Assigned To | => Christian Grothoff |
2023-12-22 07:36 | Christian Grothoff | Note Added: 0020787 | |
2023-12-22 07:36 | Christian Grothoff | Status | assigned => resolved |
2023-12-22 07:36 | Christian Grothoff | Resolution | open => fixed |
2023-12-22 07:37 | Christian Grothoff | Product Version | => git (master) |
2023-12-22 07:37 | Christian Grothoff | Fixed in Version | => 0.9.4 |
2024-03-07 20:47 | Christian Grothoff | Status | resolved => closed |