psc 2 - linux kernel versioning convention
convention: linux-image-<major>.<minor>.<patch>-parrot<revision>.<true patch><edition> example for linux 4.19.13 linux-image-4.19.0-parrot1.13t <major> major version of the upstream kernel (ie. 4) <minor> minor version of the upstream kernel (ie. 18) <patch> patch version of debian (always 0 in debian) <revision> parrot revision number (incremental index that counts how many times a kernel update was released for that parrot kernel) <true patch> true upstream patch version <edition> parrot edition of the kernel. t for testing s for stable
for the upstream linux 4.18.12, the name of the debian kernel would look like linux-image-4.18.0-2, with the patch always set to zero (why?) and an incremental index at the end representing the debian release version for that branch
because of this strange behavior in handling the patch number, we used in the past to append the true patch version to the abiname string (i.e. linux-image-4.18.0-parrot20 for linux 4.18.20)
we now decided to further improve this convention as we are preparing to roll out parrot 5 LTS.