[kteam-tools 2/2] [verify-release-ready] Also check display name 'linux' for derivative fixes

[Juerg Haefliger]

On 07/03/2017 03:26 PM, Andy Whitcroft wrote:
> On Mon, Jul 03, 2017 at 02:58:18PM +0200, Juerg Haefliger wrote:
> 
>>> That seem inverted to me?  If we are linux- and not linux-lts- then we are
>>> a derivative?
>>
>> This filters out linux and linux-lts- which should leave us with the
>> derivatives (linux-<foo>). I guess I could make this more readable:
>>
>> if ((changelog_source_package != 'linux') and
>>      not changelog_source_package.startswith('linux-lts-'))):
> 
> So linux-lts-foo is not a derivative?  If that is the case (and I am
> slightly confused by the terminology) the linux-hwe{,-edge} are the same
> as linux-lts-*.

linux-lts and linux-hwe are not derivatives, IMHO. There is a distinct
difference in their changelog format, compared to a 'true' derivative.
For the sake of this conversation, I'm distinguishing between master
(the main linux package), lts backports (linux-lts-foo and linux-hwe*)
and derivatives (linux-raspi and the likes).

The package name identified by verify-release-ready is 'linux' for
anything but a derivative. So the tool can resolve bugs reported against
the master package... for anything but derivatives.

Up until a minute ago, I was under the impression that we use standard
Debian libraries to determine the package name but I just realized that
there is some ktl foo involved. I'll take a look if it makes more sense
to modify that library but I'm concerned about ripple effects into other
tools.

...Juerg


> -apw
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 845 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20170703/f6404285/attachment.sig>