Date: Sat, 30 Dec 2017 23:11:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224738] Framework doesn't report to user dialog4ports failures Message-ID: <bug-224738-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224738 Bug ID: 224738 Summary: Framework doesn't report to user dialog4ports failures Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: yuri@freebsd.org CC: freebsd-ports-bugs@FreeBSD.org 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 c= ases when dialog4ports fails with nonzero code and prints errors. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224738-13>