[libvirt] update keycodemapdb submodule for 4.1.0 release

Martin Kletzander mkletzan at redhat.com
Fri Mar 2 07:08:45 UTC 2018


On Thu, Mar 01, 2018 at 04:52:09PM +0000, Daniel P. Berrangé wrote:
>On Thu, Mar 01, 2018 at 09:47:32AM -0700, Jim Fehlig wrote:
>> I mistakenly dropped keycodemapdb commit 6b3d716e from our libvirt 4.1.0
>> builds only to stumble across the failures in py3 environments that are
>> fixed by that commit. Should the submodule be updated for the 4.1.0 release?
>
>Since the release is scheduled for tomorrow I'm pretty wary of updating
>the submodule before that.
>
>You show that we we missing CI coverage for python3 though, so we
>should address that. We could make our Fedora Jenkins CI builds use py3,
>along with one of our Travis scenarios, so we get a mix of py2&py3
>coverage in both Jenkins & Travis.
>

Do we?  I think the builds were switched so that we can run unit tests on
virt-manager so now we have CI coverage for py2 as well as py3.

>Regards,
>Daniel
>-- 
>|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
>|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
>|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
>
>--
>libvir-list mailing list
>libvir-list at redhat.com
>https://www.redhat.com/mailman/listinfo/libvir-list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20180302/b685aff1/attachment-0001.sig>


More information about the libvir-list mailing list