umpf: output version infos to bitbake variables during format-patch

[ejoerns]

This sets PV to the exact umpf version.

This is especially useful when using the series.inc together with the linux-yocto.bbclass version checking which expects PV to match the full kernel version.

[ejoerns]

Note that this currently sets LINUX_VERSION unconditionally which might not be optimal since not all recipes are kernels.
However, I could not find an existing good way to know which software we create the patches for.
Another option might be to just omit this first of all.

[michaelolbrich]

Is is save to overwritePVin general. What about packages other than the kernel?

[ejoerns]

Is is save to overwritePVin general. What about packages other than the kernel?

You can always override PV with a custom value (other than the default taken from the file name).
If that's always desired is a different thing where I am not sure about. The advantage would be that you see the umpf version also in the generated version and compliance artifacts, etc.

It should at least be ensured that the PV value does not imply a lower version when being updated (this would also trigger buildhistory sanity check errors) but that should be the case when using dates as suffix.