On Sat, 2019-07-27 at 11:36 +0200, Michal Suchánek wrote:
In Factory Virtualbox KMPs should already depend on the kernel version they were built against and become uninstallable when the kernel changes. However, it is not OBS itself checking this rebuild condition. There is a bot somewhere which checks this and rebuilds the packages from time to time. Apparently you can get broken packages released or completely broken Factory due to bad timing. Having a snapshot always checked for uninstallable packages before it is released should be doable, though
Everything is 'doable' - the question is if anybody is willing to pay the price. e.g. I hear statements like: * No package should ever fail to bvuild * No package should ever be uninstallable * Everything should always work Juyst to make some coutner statements: * Currently, there are 244 build failures in TW (~ 2% of all packages). Some fairly recent, Some have been failing for as long as 8 months. Shall we *really* block all future snapshots until ALL build fails are fixed? [0] * The installcheck report has 32 'unique' packages listed as uninstallable (~0.05%, there are ~ 70k binary packages). Many of them are listed for a long time, one I checked for example received a comment by the bot on the package in Oct 2017 - nothing changed. Shall I block all future snapshots until this is resolved? [1] * Everything should always work: very noble goal, but even here: openQA is a tool to aid on deciding, sometimes there are test errors that are due to the tests doing'wrong' stuff, something it code errors. I don't think I've ever seen '0 openQA failures' on a snapshot. Even though this is a goal, so far it is still a goal in the far distance. As for the actual problem with Virtualbox: There is NO indication that it would not be installbale on kernel 5.2.1 in the RPM meta:
rpm -qR virtualbox-host-kmp-default | sort -u /bin/sh coreutils grep kernel-default rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1
This also shows in the fact that virtualbox-host-kmp-default is installable on a workstation qwithout issues - even with only kernel 5.2.1 present. And this is the reason why the bot can't, in any way, detect that virtualbox needs a rebuild. There is something nothing in the stack invalidating the current RPMs. And this is nothing new and has been mentioned multiple times on this list already, e.g. https://lists.opensuse.org/opensuse-factory/2017-11/msg00429.html https://lists.opensuse.org/opensuse-factory/2017-12/msg00160.html https://lists.opensuse.org/opensuse-factory/2018-07/msg00128.html These are just the first ones I found on the topic, I know that Coolo wrote the same already as well. Granted, the 2nd and 3rd link have no details at all, but the 2nd link for example isonly a month apart from the first - which is, imho, quite detailed. Yet, nothing changed. Without change, the bot can't see the issue. Maybe this is now sufficient motivation that this issue is being addressed? Cheers, Dominique [0] https://build.opensuse.org/project/status/openSUSE:Factory [1] https://build.opensuse.org/package/view_file/home:repo-checker/rebuilds/rebu...