https://bugzilla.suse.com/show_bug.cgi?id=1218184 https://bugzilla.suse.com/show_bug.cgi?id=1218184#c17 --- Comment #17 from Michal Suchanek <msuchanek@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.