You could raise the threshold to -report_about "sorry". But messages of
severity "WARNING" are noteworthy, too.
xorriso classifies its stderr messages by a spectrum from "DEBUG" to "FATAL".
(stderr messages without a severity prefix are of severity "NOTE".)
The commands -report_about, -return_with, and -abort_on set thresholds for
message emission, exit value, and premature program end.
This does not affect stdout of xorriso, which is considered to transfer
only result data, which were ordered by inquiry commands like
-report_el_torito or -toc.
Hi,
Paride Legovini wrote: /github. com/canonical/ subiquity/ pull/900
> see https:/
where i see:
- opts="$(xorriso -indev ${OLD_ISO} -report_el_torito as_mkisofs 2>/dev/null)"
+ opts="$(xorriso -indev ${OLD_ISO} -report_el_torito as_mkisofs)"
Consider to reduce verbosity by xorriso command -report_about.
Like:
+ opts="$(xorriso -report_about warning -indev ${OLD_ISO} -report_el_torito as_mkisofs)"
You could raise the threshold to -report_about "sorry". But messages of
severity "WARNING" are noteworthy, too.
xorriso classifies its stderr messages by a spectrum from "DEBUG" to "FATAL".
(stderr messages without a severity prefix are of severity "NOTE".)
The commands -report_about, -return_with, and -abort_on set thresholds for
message emission, exit value, and premature program end.
This does not affect stdout of xorriso, which is considered to transfer
only result data, which were ordered by inquiry commands like
-report_el_torito or -toc.
Have a nice day :)
Thomas