"linux" apport package hook
You-Sheng Yang
vicamo.yang at canonical.com
Wed Feb 12 17:25:59 UTC 2020
How about let each kernel package install their own symbolic link? That
would probably take many duplicated works for each variant (perhaps just
generate it from a common script), but it's a more clean and formal way to
maintain package hooks, and then apport source package can then be freed
from maintaining an endless list that is really not related to itself.
You-Sheng
Seth Forshee <seth.forshee at canonical.com> 於 2020年2月13日 週四 01:06 寫道:
> On Mon, Feb 10, 2020 at 04:38:33PM -0800, Brian Murray wrote:
> > I'm working on fixing LP: #1861446 where the apport package hooks
> > (shipped via apport) are not run for some linux packages. I've currently
> > added in symlinks for linux-signed-5.4, linux-signed-oem-5.4, linux-5.4,
> > and linux-oem-5.4[1]. Am I missing anything else?
>
> What do we currently do for derivatves, like cloud kernels, linux-kvm,
> linux-raspi2, and hwe kernels? Those are all likely to have the same
> problem.
>
> This is also going to continue to pop up as we move upstream kernel
> versions and package names change. I wonder if it might be worth
> considering some more generalized way of doing these mappings for kernel
> packages, instead of creating dozens of symlinks.
>
> Thanks,
> Seth
>
> --
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20200213/6956ebae/attachment.html>
More information about the kernel-team
mailing list