On Thu, Sep 12, 2019 at 10:42 AM <[email protected]> wrote: > > > On Wed, Sep 11, 2019 at 8:34 PM <thomas(a)hoberg.net> wrote: > > > > Thanks for the report! > > > > I'll try to handle it soon. Probably something trivial like changing > > the order in that line should be enough. We already did that a few > > times in the past :-( > I don't know if RHEL/CentOS 8 is completely "python2" clean. If not, you > might just create the reverse problem and then there are still other > distributions in transition, I guess.
Indeed. > > Perhaps a helper function needs to identify the python dialect of the > orchestration engine underneath... Something like this, which we did 3 years ago and quickly reverted, at the time: https://gerrit.ovirt.org/#/c/59831/28/src/bin/otopi > > The again I am not sure that Otopi generates the tar ball on the host-to-add > or on the management engine: In theory (and soon in practice) these could be > crossing dialect boundaries as we'll we a mix of v7/v8 hosts being > orchestrated with oVirt for some years perhaps. Right. And it's generated on the engine, and indeed it should be prepared for both. > > > > I wonder how come you are the first one reporting it. I guess not many > > people yet install python3 on CentOS 7. > > Actually I found a previous report and added it as a reference in bugzilla. > At the time the issue was closed as WONTFIX, because Python3 was considered > irrelevant on CentOS 7... Indeed. And the reporter was my team mate, not a real user :-), so I could decide it's not that common. I guess I should now apologize for wasting your time instead of fixing it then. Sorry. If Cinnamon requires python3, that's still not that common (running a GUI on a hypervisor host), but at least somewhat more so. I suppose we should be prepared for more packages requiring python3 even on EL7. > > https://bugzilla.redhat.com/show_bug.cgi?id=1751324 > > Bug 1751324 Thanks and best regards, -- Didi _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/NPJ6HBPYXHVEMGDO4SMLWKGLX6JMBIDX/
