https://bugzilla.suse.com/show_bug.cgi?id=1190738 https://bugzilla.suse.com/show_bug.cgi?id=1190738#c1 --- Comment #1 from Marcus Meissner --- perhaps build it again together with the regular kernel set? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1190738 Vincent Moutoussamy changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1190738 https://bugzilla.suse.com/show_bug.cgi?id=1190738#c4 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com Assignee|kernel-bugs@opensuse.org |msuchanek@suse.com --- Comment #4 from Jiri Slaby --- I think this is for Michal to decide and maybe implement. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1190738 https://bugzilla.suse.com/show_bug.cgi?id=1190738#c6 --- Comment #6 from Fabian Vogt --- One possible approach would be to have an otherwise empty kernel-changelog package which can be required by everything. That also avoids that the changelog is included multiple times for every kernel subpackage, e.g. kernel-default, -extra, -optional, -devel, dtb* packages, -devel, -macros, ... which currently end up in the RPM database without compression or deduplication and take up noticable amounts of space. (In reply to Michal Suchanek from comment #5)

I don't think we can include the kernel changelog.

There are two problems: the kernel-default-base and the kernel changelog would need to be merged. There is a changelog merge tool which orders the entries chronologically which could be used with the caveat that the kernel-default-base changes would be lost among the kernel changes.

The other problem is that the changelog merge would have to be done in the OBS by a service that runs before the package build starts. The build environment should be set up at this point so it should be technically possible to do but this part of OBS is very poorly documented. Also the custom service would have to be included in the official OBS instances.

buildtime services can be provided by any package. -- You are receiving this mail because: You are on the CC list for the bug.