@lwfinger - we need an adsjustment on virtualbox here: virtualbox has a Requires: libvncserver0, which is no longer satisfied (the lib is changed to libvncserver1)

Can you please make this a dynamic dependency? (is the dep even real? How does it find the right library?)

The build works when the Requires: libvncserver0 is replaced with Requires: LibVNCServer-devel, which I think satisfies the dynamic dependency. I think the dependency is needed, but I don't use the vnc package.

We do have a problem at the moment. VB 6.0.x requires a new file to be SUID. I created a bug noting the change that was needed. The Security Group needed access to the new code to audit it, thus I pushed version 6.0.4 to Virtualization/virtualbox. They have now agreed that the new file can be white listed, but the new version of permissions have not yet made it to Factory. At the present time, OBS keeps retying the builds that run for about an hour and then fail because RPMLINT gets an error. I was told that the new permissions should be available this week, but it has not yet appeared.

Dominique Leuenberger (dimstar) - over 5 years ago

reviewer

The build works of course irresctive of any requires - the problem is that if libvncserver0 vanishes, the package is no longer installable (still buildable though)

Requiring -devel is definitvely not the right way out of it, as -devel is not for runtime system installations

---

Larry Finger (lwfinger) - over 5 years ago

I have removed all VNC server requires from the spec file. The resulting packages seem OK; however, I am not a user of this feature, and it may fail later. When a user reports a failure, then I will need to address the problem.

Once permissions are updated, I will push the change that removes the requires statement.

---

Petr Gajdos (pgajdos) - over 5 years ago

author source maintainer

I think I may provide libvncserver = %{version} symbol for you. Would that feasible, @dimstar?