| Summary: | Auto-Assigner: Summaries containing port references of form /usr/ports/cat/port are not auto-assigned | ||
|---|---|---|---|
| Product: | Services | Reporter: | Kubilay Kocak <koobs> |
| Component: | Bug Tracker | Assignee: | Oleksandr Tymoshenko <gonzo> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | bugmeister, mmokhi |
| Priority: | Normal | Keywords: | easy, needs-patch, needs-qa |
| Version: | unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
| URL: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198213 | ||
| See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198213 | ||
| Bug Depends on: | |||
| Bug Blocks: | 205735 | ||
|
Description
Kubilay Kocak
2015-03-03 05:05:31 UTC
The auto-assigner only checks for "category/port", not more, not less to avoid false positives with other paths. I do not see a good way to change this without creating more issues. @Marcus What if the path match was limited to /usr/ports/<category>/<portname> ? What other issues can you foresee? We could include /usr/ports/ as valid prefix for a cat/port detection, since this is the FreeBSD default path for ports. Other path constructs however may lead to false positives, esp. if console output is posted in the initial description. Sounds good Marcus. That (matching /usr/ports) covers for the example that spawned this issue. If it occurs in future with different path references we can evaluate any additional opportunities then. |