FS#60199 - [clazy] cannot access '/usr/share/clazy/doc/level0/README*': No such file or directory

Attached to Project: Arch Linux
Opened by Alexander F. Rødseth (xyproto) - Wednesday, 26 September 2018, 09:42 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 30 September 2018, 13:14 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

This command:

clazy --list

Gives the following output:

List of available clazy checkers:

Checks from level0. Very stable checks, 100% safe, no false-positives:
ls: cannot access '/usr/share/clazy/doc/level0/README*': No such file or directory

Checks from level1. Mostly stable and safe, rare false-positives:
ls: cannot access '/usr/share/clazy/doc/level1/README*': No such file or directory

Checks from level2. Sometimes has false-positives (20-30%):
ls: cannot access '/usr/share/clazy/doc/level2/README*': No such file or directory

Checks from level3. Not always correct, high rate of false-positives:
ls: cannot access '/usr/share/clazy/doc/level3/README*': No such file or directory

Additional info:
* clazy 1.4-1

Steps to reproduce:

clazy --list
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 30 September 2018, 13:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  clazy 1.4-3
Comment by Antonio Rojas (arojas) - Wednesday, 26 September 2018, 14:47 GMT
Please report this upstream
Comment by Eli Schwartz (eschwartz) - Wednesday, 26 September 2018, 19:19 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
  • Task assigned to Antonio Rojas (arojas)
Upstream broke this in commit https://github.com/KDE/clazy/commit/4e435138af4184fa5c623fea9b8b83c6eb683e28

They moved the doc files, but didn't update the entrypoint script which hardcodes the old directory...
Comment by Alexander F. Rødseth (xyproto) - Friday, 28 September 2018, 13:16 GMT
It is possible to patch the CMakeLists.txt file with sed in prepare(), while waiting for the next release, where they have fixed this.
Comment by Antonio Rojas (arojas) - Saturday, 29 September 2018, 08:22 GMT
Or you could report it, they would fix it within hours and then we'd backport the fix instead of shipping a custom fix until someone else bothers to report it.
Comment by Alexander F. Rødseth (xyproto) - Sunday, 30 September 2018, 10:09 GMT
One does not exclude the other. You can both patch CMakeLists.txt and also report the issue to https://bugs.kde.org/.
Comment by sergio (sergio) - Sunday, 30 September 2018, 11:00 GMT
Thanks for reporting, this is now fixed.

commit 3a731ebfdcacd23c68d716a657bb6e9a806b7532

Loading...