On Fri, Jan 5, 2018 at 10:20 AM, Francesco Romani <fromani(a)redhat.com> wrote:
On 01/05/2018 08:16 AM, Dan Kenigsberg wrote:
>
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/
> is failing since yesterday on
>
> Error:
> Problem 1: conflicting requests
> - nothing provides ovirt-vmconsole >= 1.0.0-0 needed by
> vdsm-4.20.11-7.git4a7f18434.fc27.x86_64
>
> after already passing in the past.
>
> Can this be solved on ovirt-vmconsole side, or should we disable fc27 (again)?
Speaking as maintainer of ovirt-console, it is a good chance to review
what's the status of ovirt-vmconsole, and how we can improve things for
the current state and for the future.
ovirt-vmconsole is pretty stable codewise and featurewise (and, I'd say,
bugwise), in the last 12+ months I hardly gathered material for another
minor release (would be 1.0.5), which
is not planned yet, as further proof that the codebase is stable.
Most of time, the only thing needed is to ship the existing packages for
a new distro release. It seldom may be needed a simple rebuild.
I must say I'm not aware of how the current issue was solved for fc26,
IIRC some manual intervation was applied along the lines above.
Can we automate this step somehow?
Barak and Sandro can surely help with regards to fc27, and may have
ideas on how to automate this to future releases.