[Bug 1190738] New: kernel-default-base does not contain kernel changelog
https://bugzilla.suse.com/show_bug.cgi?id=1190738 Bug ID: 1190738 Summary: kernel-default-base does not contain kernel changelog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: fvogt@suse.com QA Contact: qa-bugs@suse.de CC: jeos-internal@suse.de Found By: --- Blocker: --- kernel-default-base is built from a separate set of .spec and .changes files, making use of the kernel-subpackage facilities. This however means that the changelog of the original kernel packages (kernel-default, -vanilla, etc.) does not end up in the changelog of kernel-default-base. This is especially visible in updates, which only change the binary content and the version number in an unobvious way. There is no mention of any relevant fixed bugs (bsc#, CVE-). It would be very useful to include the kernel changelog in the kernel-default-base package. I don't think it can (or should) be interleaved with the subpackage .changes file, but it could be included as file. The target systems usually have excludedocs enabled though, so marking the file as %doc means it won't get installed. That makes it more complex and annoying... -- 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#c1 --- Comment #1 from Marcus Meissner <meissner@suse.com> --- 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 https://bugzilla.suse.com/show_bug.cgi?id=1190738#c2 Vincent Moutoussamy <vmoutoussamy@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmoutoussamy@suse.com --- Comment #2 from Vincent Moutoussamy <vmoutoussamy@suse.com> --- (In reply to Marcus Meissner from comment #1)
perhaps build it again together with the regular kernel set?
Well the way we are building kernel-default-base right now is definitely an improvement for the JeOS team. I don't think this issue is critical enough to go back to being build together with the regular kernel. -- 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 <vmoutoussamy@suse.com> 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#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Agreed, the separate build allows more flexible ways of adding/removing the modules outside the lengthy and complex kernel packaging process, and that's the exact purpose. Containing the kernel changelog in the package file sounds feasible. I wanted to put the old changelog from the previous SP into a file instead of keeping the full log, in anyway, and it will follow in that line. -- 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 <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com Assignee|kernel-bugs@opensuse.org |msuchanek@suse.com --- Comment #4 from Jiri Slaby <jslaby@suse.com> --- 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#c5 --- Comment #5 from Michal Suchanek <msuchanek@suse.com> --- 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. -- 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 <fvogt@suse.com> --- 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.
participants (1)
-
bugzilla_noreply＠suse.com