Bug 224738 - Framework doesn't report dialog4ports failures to user
Summary: Framework doesn't report dialog4ports failures to user
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-30 23:11 UTC by Yuri Victorovich
Modified: 2022-01-31 21:48 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer freebsd_triage 2017-12-30 23:11:11 UTC 
dialog4ports prints some errors under certain circumstances.
Those errors are lost when printed.
IMO, this should be fixed in the framework.

You might say "But everything works fine! Why do we need to fix this?"
Maybe it does fail somewhere, and it just passes because the errors aren't propagated.

Anyway, my opinion is that framework should be fixed and report errors in cases when dialog4ports fails with nonzero code and prints errors.