On 2022-03-10 12:09 -0700, Sam Hartman wrote: > >>>>> "Steve" == Steve McIntyre <st...@einval.com> writes: > > Steve> Why on earth *would* you mess around using Debian revisions > Steve> on a native-format package, though? > > You're trying to produce packages from CI builds or other automation > where you sometimes have native Debian revisions. > > * you are producing a package where you have distinct upstream and > debian branches, and you cannot control the upstream version number.
Doesn't this make it 'not a native debian package'? I thought the whole point of debian native packages was that there was no 'upstream' and it was only for debian so you _are_ in control of the source, the versioning and the releases? As soon as that stops being true then should one not shift to making it a standard 'upstream+debian revision' non-native package? Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
