https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c1 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent --- Comment #1 from Frederic Crozat --- The workarounds used to get kernel subpackages building with scmsync on IBS are breaking now. We need _multibuild on ALP kernel-source package. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c3 --- Comment #3 from Frederic Crozat --- It is to ensure we track this for ALP. It is a hard requirements for ALP to have all packages using _multibuild. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c5 --- Comment #5 from Jiri Srain --- You have known about this request since months. What's the kernel team's ETA? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c7 --- Comment #7 from Jiri Kosina --- Nevermind, apparently all the technical details are in bsc#1211226. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fcrozat@suse.com) |needinfo?(mls@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c10 --- Comment #10 from Dominique Leuenberger --- (In reply to Jiri Srain from comment #9)

If the main concern is excludebuild getting inherited if you build against the standard ALP repository, we can have it only conditional in our ProjectConfig, based on the project. Will this help?

%if "%_project" == "SUSE:ALP:Source:Standard:Core:1.0:Build" BuildFlags: excludebuild:kernel-source:kernel-qa

as far as I understood, the issue is not coming from the main distro projects (there are no excludes in place for any kernel flavor - even with the old linked packages, kernel-obs-qa for example is being built (see https://bugzilla.suse.com/show_bug.cgi?id=1211226#c11) The special case is in the devel project: * Repo QA shall have only the *qa* kernel flavors * Repo standard (name just coincidentally matches) all the rest. => the excludebuild/onlybuild flags proposed in https://bugzilla.suse.com/show_bug.cgi?id=1211226#c3 sounded like a good starting point - but is limited by the special case that kernel-devel-prj/QA builds against kernel-devel-prj/standard (thus inherits prjconf from both repositories) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c12 --- Comment #12 from Jiri Srain --- Would there be an option to define (in ProjectConfig) new macros for this purpose and let the .spec-file handle the rest? This would allow to solve the issue with inheritance, one could override the inherited value of the macro in any project (and therefore solve the issue with inheriting prjconf from two repos) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c14 --- Comment #14 from Jiri Srain --- Thank you Dominique, for confirming that this idea should work (and IMO it can give enough flexibility even if there is more granularity expected in the future) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c16 --- Comment #16 from Jiri Srain --- Could you, please, explain a bit more in detail what exactly the problem is and how it is solved with the links? Since most of the issues seem to have a solution, could you switch to _multibuild and add the needed macros to your project (we will add them to ALP once submiteed)? Otherwise, as you did not come up with any reason not to proceed as specified in Jiri Kosina’s comment#8, proceed according to it. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c18 Richard Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown@suse.com --- Comment #18 from Richard Brown --- (In reply to Michal Suchanek from comment #17)

The problem is that you can no longer control individual packages with mutibuild while you could with package links.

The flags you can control with package links are 'build' 'publish' and 'use for build'.

Wit multibuild you can control 'build' with gross spec file hacks, the rest cannot be controlled.

This is, of course, only a concern for key packages like kernel or toolchain.

Since conversion to multibuild cross-compilers do not build on devel:gcc. In linked package scenario the native binutils would not be used for build so that binutils breakage could be fixed by uploading new binutils revision.

The cross-binutils are needed to build cross-gcc so in linked situation cross-gcc would build but with multibuild it's unresolvable because binutils are not used for build.

There is similar situation with kernel-obs-build. It should be built in the standard repository but used for build in the QA repository to build kernel-obs-qa, all of these linked from kernel-source together with kernel-default.

Determining which package is to be built and used for build in which repository is OBS's job. It should not be pushed on packagers leading to hacky and incomplete solutions.

If multibuild is to be used in place of package links OBS should be fixed to deal with setting flags for individual multibuild packages.

If we do not have enough people working on OBS to fix up multibuild to be usable, or even so much as comment on bugs concerning multibuild then multibuild should not be used.

I'm now very confused. The premise of the original bug was that 'source links' need to be removed from the kernel package in Tumbleweed. The premise of this bug many months later is that 'source links' need to be removed from the kernel package in Tumbleweed and ALP Dolomite. kernel-obs-build, kernel-obs-qa, packages in devel:gcc, all seem to me to be chaff thrown up to confuse. Unless I'm missing something they seem to be wildly out of scope to the matter at hand - the kernel in our future products needs to be built using methods like multibuild. I don't think anyone minds what happens in devel projects, but our future/now present products are using 'git based source management' and the long communicated changes needed to facilitate that really need to be implimented now. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c20 --- Comment #20 from Jiri Srain --- (In reply to Michal Suchanek from comment #19)

This is not the first time multibuild was suggested for kernel.

https://jira.suse.com/browse/PM-1015

It has been rejected because OBS is not ready for multibuild.

It was not ready then and is not ready now.

(In reply to Jiri Srain from comment #5)

...

You have known about this request since months. What's the kernel team's ETA?

OBS people have known about the request to control repository flags for multibuild flavors individually for years.

https://github.com/openSUSE/open-build-service/issues/3574

Sure, it's possible to implement workarounds in a lot of packages but maybe fixing the root cause would be more productive?

Which other "a lot of packages" do you mean? Kernel is now the only package still using source links in the ALP code base and if I remember Dominique correctly, it is the same for Factory. Everything else (including toolchain you mentioned in previous comment) has meanwhile switched to _multibuild.

There are is an additional problem with OBS multibuild support: package actions are broken for multibuild in the web UI.

https://github.com/openSUSE/open-build-service/issues/12913 https://github.com/openSUSE/open-build-service/issues/7866 https://github.com/openSUSE/open-build-service/issues/7156

Apparently it's confusing repeatedly even to people doing packaging daily, reported repeatedly but not fixed.

This is much worse for kernel developers who are often not packagers and interact with OBS only occasionally. For them sane interface is even more important, and figuring out the workaround less likely. Coupled with the previous issue that makes manual intervention more likely required it's pretty damning.

(In reply to Richard Brown from comment #18) .

...

I'm now very confused.

The premise of the original bug was that 'source links' need to be removed from the kernel package in Tumbleweed.

The premise of this bug many months later is that 'source links' need to be removed from the kernel package in Tumbleweed and ALP Dolomite.

kernel-obs-build, kernel-obs-qa, packages in devel:gcc, all seem to me to be chaff thrown up to confuse.

Unless I'm missing something they seem to be wildly out of scope to the matter at hand - the kernel in our future products needs to be built using methods like multibuild.

I don't think anyone minds what happens in devel projects, but our future/now present products are using 'git based source management' and the long communicated changes needed to facilitate that really need to be implimented now.

Your hyperbolic comments do not contribute to solving the technical problem, and have potential to adding people problem in addition. I want to believe this is hyperbolic and not serious. In any case your contribution towards solving this problem has been less then none.

Well, this can be meant seriously. If you need the links because of any issue with IBS, what prevents you to keep them in your devel project / projects and disable all packages building from _multibuild there? The binaries will build from the same .spec-file and from the same tarball, with the same patches applied, independently whether via links in your project or _multibuild in ALP / Factory. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c22 --- Comment #22 from Michal Suchanek --- (In reply to Jiri Slaby from comment #21)

Do I understand that you are suggesting to build the kernel in devel projects differently in devel projects and Factory. If so, strong NACK from me.

As if it even worked. (In reply to Jiri Srain from comment #20)

Which other "a lot of packages" do you mean? Kernel is now the only package still using source links in the ALP code base and if I remember Dominique correctly, it is the same for Factory. Everything else (including toolchain you mentioned in previous comment) has meanwhile switched to _multibuild.

And their develproject is still broken. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c24 --- Comment #24 from Michal Suchanek --- (In reply to Dominique Leuenberger from comment #13)

That should be doable.. something like:

%repo_conf DEVEL %if "%{_repository}" == "QA" %repo_conf QA %endif

Does not look so. Conditionals are not allowed in the Macros: section because it is dumped into a rpm macro file, and that does not support them. %repo_conf QA on the other hand goes into the Macros: section -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c26 --- Comment #26 from Richard Brown --- Created attachment 871639 --> https://bugzilla.suse.com/attachment.cgi?id=871639&action=edit Packages using multibuild in Factory as of 20240103 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c28 --- Comment #28 from Michal Suchanek --- (In reply to Richard Brown from comment #25)

After all, reviewing the comments here, all the substantive arguments against _multibuild to date ONLY seem to apply to the devel projects. The 'lacking controls' are controls which are not available in the OBS Projects for Factory or our products anyway. Therefore suggesting the devel project could still use source links as long as the submitted kernel to our products used _multibuild seemed like a diplomatic workaround to table.

How would you imagine that to work, specifically?

The alternative would be to continue demanding that the long established hard requirement for _multibuild be finally met, circular discussions would likely continue, meanwhile ALP Product builds remain broken.

Why are long established bugs in multibuild support not fixed if there is hard requirement for using multibuild?

The more esoteric arguments that _multibuild is fundamentally broken are countered by the realities of our codebase In Factory there are a grand total of 688 packages using _multibuild (package list attached) This list does not include the child-packages created as a result of multibuild. ie. this is the de-duplicated number This includes toolchain packages like cmake, gcc, glibc and is approximately 4% of all packages in Factory

I am not disputing that the Factory can be built with _multibuild. However, lack of support for multibuild in OBS degrades OBS usability in general. It also makes maintenance of develprojects and addon projects harder, requiring baroque workarounds. This increases load on package maintainers and detracts from OBS as a selling point of our distribution enabling easy contribution. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c30 --- Comment #30 from Michal Suchanek --- So it does not build. https://build.opensuse.org/package/live_build_log/home:michals:kernel-test/k... Apparently 'needs root for build' is another flag which was available per spec file previously but now is set based on the main spec file. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c32 --- Comment #32 from Richard Brown --- also..isn't the correct syntax #!needsrootforbuild ? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c34 --- Comment #34 from Michal Suchanek --- (In reply to Richard Brown from comment #31)

As I am not an OBS Admin, I wouldn't want to speculate as to why non-multibuild kernels work when multibuild kernels don't, but if you need that flag, I'd say the OBS Admins are the ones to talk to about enabling it

Maybe you could try talking to them if you want this to happen. I tried and got no response. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c36 --- Comment #36 from Dominique Leuenberger --- config whitelisting for the kernel-obs-build has been adjusted in OBS: used to be .*/kernel-obs-build (.*/ to make it build permitted in all projects, for branches) Adrian extended the config to also allow kernel-source:kernel-obs-build; we should soon see a result in the test project -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c38 --- Comment #38 from Michal Suchanek --- Does not work for kernel-source-vanilla or kernel-source${VARIANT} in general: https://build.opensuse.org/project/monitor/Kernel:linux-next -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c40 Adrian Schröter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #40 from Adrian Schröter ---

@Adrian: can you please change the new rule to .*/kernel-source.*:kernel-obs-build ?

that is changed now -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c60 --- Comment #60 from Takashi Iwai --- Now the same problem, the build failure of kernel-obs-build, appears on IBS ALP package build. (And confirmed that the old workaround with MyBS change worked.) Can IBS setup be fixed as well? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c65 --- Comment #65 from Maintenance Automation --- SUSE-SU-2024:0129-1: An update that solves 10 vulnerabilities, contains three features and has 31 security fixes can now be installed. Category: security (important) Bug References: 1179610, 1183045, 1193285, 1211162, 1211226, 1212584, 1214747, 1214823, 1215237, 1215696, 1215885, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218139, 1218184, 1218234, 1218253, 1218258, 1218335, 1218357, 1218447, 1218515, 1218559, 1218569, 1218659 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7322 Sources used: SUSE Real Time Module 15-SP4 (src): kernel-syms-rt-5.14.21-150400.15.65.1, kernel-source-rt-5.14.21-150400.15.65.1 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4-RT_Update_17-1-150400.1.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c67 --- Comment #67 from Maintenance Automation --- SUSE-SU-2024:0115-1: An update that solves 10 vulnerabilities, contains three features and has 40 security fixes can now be installed. Category: security (important) Bug References: 1179610, 1183045, 1211162, 1211226, 1212139, 1212584, 1214117, 1214747, 1214823, 1215237, 1215696, 1215885, 1215952, 1216032, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217822, 1217927, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218092, 1218139, 1218184, 1218229, 1218234, 1218253, 1218258, 1218335, 1218357, 1218397, 1218447, 1218461, 1218515, 1218559, 1218569, 1218643 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7167 Sources used: openSUSE Leap 15.5 (src): kernel-source-rt-5.14.21-150500.13.30.1, kernel-livepatch-SLE15-SP5-RT_Update_9-1-150500.11.3.1, kernel-syms-rt-5.14.21-150500.13.30.1 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5-RT_Update_9-1-150500.11.3.1 SUSE Real Time Module 15-SP5 (src): kernel-source-rt-5.14.21-150500.13.30.1, kernel-syms-rt-5.14.21-150500.13.30.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c70 --- Comment #70 from Maintenance Automation --- SUSE-SU-2024:0113-1: An update that solves eight vulnerabilities, contains two features and has 13 security fixes can now be installed. Category: security (important) Bug References: 1108281, 1109837, 1179610, 1202095, 1211226, 1211439, 1214479, 1215237, 1217036, 1217250, 1217801, 1217936, 1217946, 1217947, 1218057, 1218184, 1218253, 1218258, 1218362, 1218559, 1218622 CVE References: CVE-2020-26555, CVE-2022-2586, CVE-2023-51779, CVE-2023-6121, CVE-2023-6606, CVE-2023-6610, CVE-2023-6931, CVE-2023-6932 Jira References: PED-5021, PED-5023 Sources used: SUSE Linux Enterprise Server for SAP Applications 12 SP5 (src): kernel-source-azure-4.12.14-16.163.1, kernel-syms-azure-4.12.14-16.163.1 SUSE Linux Enterprise High Performance Computing 12 SP5 (src): kernel-source-azure-4.12.14-16.163.1, kernel-syms-azure-4.12.14-16.163.1 SUSE Linux Enterprise Server 12 SP5 (src): kernel-source-azure-4.12.14-16.163.1, kernel-syms-azure-4.12.14-16.163.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c74 --- Comment #74 from Maintenance Automation --- SUSE-SU-2024:0141-1: An update that solves 10 vulnerabilities, contains three features and has 41 security fixes can now be installed. Category: security (important) Bug References: 1108281, 1179610, 1183045, 1211162, 1211226, 1212139, 1212584, 1214117, 1214747, 1214823, 1215237, 1215696, 1215885, 1215952, 1216032, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217822, 1217927, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218092, 1218139, 1218184, 1218229, 1218234, 1218253, 1218258, 1218335, 1218357, 1218397, 1218447, 1218461, 1218515, 1218559, 1218569, 1218643 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7167 Sources used: openSUSE Leap 15.5 (src): kernel-syms-azure-5.14.21-150500.33.29.1, kernel-source-azure-5.14.21-150500.33.29.1 Public Cloud Module 15-SP5 (src): kernel-syms-azure-5.14.21-150500.33.29.1, kernel-source-azure-5.14.21-150500.33.29.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c77 --- Comment #77 from Maintenance Automation --- SUSE-SU-2024:0156-1: An update that solves 10 vulnerabilities, contains three features and has 31 security fixes can now be installed. Category: security (important) Bug References: 1179610, 1183045, 1193285, 1211162, 1211226, 1212584, 1214747, 1214823, 1215237, 1215696, 1215885, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218139, 1218184, 1218234, 1218253, 1218258, 1218335, 1218357, 1218447, 1218515, 1218559, 1218569, 1218659 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7322 Sources used: SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1, kernel-syms-5.14.21-150400.24.103.1 SUSE Linux Enterprise Real Time 15 SP4 (src): kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1, kernel-syms-5.14.21-150400.24.103.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1, kernel-syms-5.14.21-150400.24.103.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1, kernel-syms-5.14.21-150400.24.103.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1, kernel-syms-5.14.21-150400.24.103.1 SUSE Manager Proxy 4.3 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1 SUSE Manager Retail Branch Server 4.3 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1 SUSE Manager Server 4.3 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1 openSUSE Leap 15.4 (src): kernel-obs-qa-5.14.21-150400.24.103.1, kernel-source-5.14.21-150400.24.103.1, kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-livepatch-SLE15-SP4_Update_22-1-150400.9.3.1, kernel-syms-5.14.21-150400.24.103.1 openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1 openSUSE Leap Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1 SUSE Linux Enterprise Micro for Rancher 5.4 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1 SUSE Linux Enterprise Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_22-1-150400.9.3.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): kernel-obs-build-5.14.21-150400.24.103.1, kernel-default-base-5.14.21-150400.24.103.1.150400.24.48.1, kernel-source-5.14.21-150400.24.103.1, kernel-syms-5.14.21-150400.24.103.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1219005 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Libor Miksik changed: What |Removed |Added ---------------------------------------------------------------------------- Group|SUSE Enterprise Partner | Version|Milestone 5 |unspecified Product|Dolomite |SUSE Linux Enterprise Micro | |6.1 Component|Kernel |Kernel/filesystems -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Bug 1218184 depends on bug 1218998, which changed state. Bug 1218998 Summary: cannot abort build/restart build/wipe binaries for multibuild packages https://bugzilla.suse.com/show_bug.cgi?id=1218998 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.