Bug#1007717: Native source package format with non-native version
On Tue, Mar 15, 2022 at 04:29:17PM +0000, Ian Jackson wrote:
> 1. Declare explicitly that there is nothing wrong with a package with
> a native format, but a non-native version number.
> 2. Request that the dpkg maintainer relax the restriction which
> prevents the use of 3.0 native with Debian revision.
One additional point:
We currently have packages in the archive, which must be "3.0 (native)",
but are generated from other packages: all the secure boot signed
Example source package:
| Package: linux-signed-amd64
| Version: 5.17~rc8+1~exp1
is generated from binary package:
| Package: linux-image-amd64-signed-template
| Version: 5.17~rc8-1~exp1
Generating the source package needs to munge the version, just to
appease that version restriction. This also means, adding dependencies
on versions is difficult, as both versions sort differently. And bugs
are assigned to wrong versions, so version tracking does not work.
Kirk to Enterprise -- beam down yeoman Rand and a six-pack.