Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

2.4.3.3: "twprint --print-report -t 2" does not list affected files #19

Closed
cboldt opened this issue Feb 26, 2017 · 4 comments
Closed

2.4.3.3: "twprint --print-report -t 2" does not list affected files #19

cboldt opened this issue Feb 26, 2017 · 4 comments

Comments

@cboldt
Copy link

cboldt commented Feb 26, 2017

I have a filesystem with a handful of changes and a handful of errors (missing files that were specifically listed by the policy), and the "-t 2" level of report detail does not give the names of the affected/changed files. The File System Errors are reported, and the summary section reports how many files have been modified/added.

The "-t 1" and "-t 3" levels correctly report the affected filenames, and for "-t 3", the specific reason or reasons for reporting the file.

2.4.3.2 works as expected.

I've preserved the .twr file. It is not encrypted and you should be able to reproduce this for yourself. Let me know if you want a copy.
@brc0x1
Copy link
Member

brc0x1 commented Feb 27, 2017

Hi, thanks for reporting this. I apparently broke this in 2.4.3.3 while chasing lint warnings, and I have a fix on a new dev/2.4.3.4 branch, if you feel like trying it out. I should have this merged to master as soon as I track down a 'make install-strip' issue.

@cboldt
Copy link
Author

cboldt commented Feb 27, 2017

Thank you. I manually made the changes to textreportviewer.cpp, it works here. Best of luck resolving that "make install-strip" thing.

@brc0x1 brc0x1 mentioned this issue Mar 5, 2017
Merged
@brc0x1
Copy link
Member

brc0x1 commented Mar 5, 2017

Ok, this fix is now merged to master.

@cboldt
Copy link
Author

cboldt commented Mar 5, 2017

Thanks again. Installed and tested on three different machines, works as expected.

@cboldt cboldt closed this as completed Mar 5, 2017
@brc0x1 brc0x1 mentioned this issue Apr 7, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brc0x1 @cboldt