This could have been a backport of jammy's 4.3.8.12175.20140902+dfsg-0ubuntu15 including jammy's changelog and then version number 4.3.8.12175.20140902+dfsg-0ubuntu15~20.04.1
or it can be 4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4 (as in .N+1 increment on the last upload).
But 4.3.8.12175.20140902+dfsg-0ubuntu14~20.04.3 does not make sense, as this upload is unrelated to 4.3.8.12175.20140902+dfsg-0ubuntu14 which adds v5.10 support which landed as 4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 already.
Uploading this as 4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4.
In the future, if it is desired to ship backports of later development series dkms modules into prior series one can use `backportpackage` command to create correctly versioned backports with devel series changelogs included.
This could have been a backport of jammy's 4.3.8.12175. 20140902+ dfsg-0ubuntu15 including jammy's changelog and then version number 4.3.8.12175. 20140902+ dfsg-0ubuntu15~ 20.04.1
or it can be 4.3.8.12175. 20140902+ dfsg-0ubuntu13~ 20.04.4 (as in .N+1 increment on the last upload).
But 4.3.8.12175. 20140902+ dfsg-0ubuntu14~ 20.04.3 does not make sense, as this upload is unrelated to 4.3.8.12175. 20140902+ dfsg-0ubuntu14 which adds v5.10 support which landed as 4.3.8.12175. 20140902+ dfsg-0ubuntu13~ 20.04.3 already.
Uploading this as 4.3.8.12175. 20140902+ dfsg-0ubuntu13~ 20.04.4.
In the future, if it is desired to ship backports of later development series dkms modules into prior series one can use `backportpackage` command to create correctly versioned backports with devel series changelogs included.