Closed classabbyamp closed 1 year ago
Instead of just cryptically exiting 0 when opening a non-existant repodata or stagedata, with the only message existing in the debug output, show an error to the user on stderr.
mentioned in #519
should this PR be expanded to add user-facing messages in other places where the exit condition is cryptic (i.e., just an exit code)?
Should probably use xbps_error_printf for consistency.
xbps_error_printf
Instead of just cryptically exiting 0 when opening a non-existant repodata or stagedata, with the only message existing in the debug output, show an error to the user on stderr.
mentioned in #519