--verbose will not output much information

[lawik]

I believe I tried this when I wanted to confirm whether it was actually doing encrypted delta operations. And I don't think there is any additional output with --verbose during a task.

It would be nice to be able to see how it interprets each resource as it works through a particular task.

[lawik]

And right now I'd love to know if running an upgrade on a grisp2 fw file is hung because broken or just spending a lot of time calculating things :D

[fhunleth]

Yeah, I need to think about what is useful. The grisp2 fw file was getting an error expanding beyond what fwup thought was the end of disk, but since you were operating on a regular file, that should have been ok. That error triggered a bug in resetting fwup's internal cache on error which is why it hung. This was relatively easy to catch using gdb and seeing that a thread was waiting on a condition variable that wasn't going to unblock. I'm not sure if --verbose would have helped with this, but it certainly seems that maybe other things could print more. I'll leave it open for a bit to remind myself to add more informational prints.

[lawik]

So I think it would be helpful for verifying where things get stuck as well as seeing if your intended fwup config is actually being applied.

Logging each on-resource and the args involved, the delta options, any encryption options. Not sure if xdelta3 has some nice output as well but this could be good in tests for things I'm doing as well. Just confirming that fwup is seeing what I intended it to see.

[lawik]

I'd love to have a flag for seeing the operations fwup performs as it performs them from the meta.conf. I'm currently looking at an issue where it seems like uboot_setenv is just not happening but it is hard to introspect :)