On Wed, Dec 4, 2019 at 10:48 AM Till Maas <till(a)redhat.com> wrote:
Hi,
Am Mi., 4. Dez. 2019 um 08:54 Uhr schrieb Miguel Duarte de Mora
Barroso <mdbarroso(a)redhat.com>:
>
> On Tue, Dec 3, 2019 at 6:31 PM Till Maas <till(a)redhat.com> wrote:
> > these are now the official Copr repositories:
> >
> > nmstate -> tagged releases from master (uses Fedora Rawhide dist-git)
> > nmstate-0.1 -> tagged releases from nmstate-0.1 (uses Fedora 31 dist-git)
> > nmstate-git -> automated rebuild from master git branch
> > nmstate-0.1-git -> automated rebuild from nmstate-0.1 git branch
> >
>
> @Edward Haas vdsm's automation currently runs on fc30.
>
> I don't see how can be supported without either:
> - keeping the old repo
> - also build nmstate for fc30
> - drop fc30 support on the vdsm side (which I think is not possible).
This is unfortunate. NetworkManager in Fedora 30 is at version 1.16
but Nmstate requires at least 1.20. So even if we build Nmstate for
Fedora 30, it will probably not work as expected and we need to remove
the dependency on libnm 1.20 from the spec file. When are you planning
to update the Fedora version? Fedora 30 should be EOL within 6 months.
It's usually done around EOL date (couple of weeks before) ...
> Any alternatives that I'm missing ?
We can enable Fedora 30 in Copr. Which branch are you using in Vdsm
0.1 or master (0.2.* currently)?
We're using master, *but* I'm working on moving it to track 0.1 .
Please enable fedora 30 there :)
This would definitely work for us since we're also updating NM to 1.20
(tracking their 1.20 branch).
Kind regards
Till
--
Till Maas
He/His/Him
Ansible RHEL Networking System Role Maintainer
Red Hat GmbH,
http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill,
Thomas Savage