TOOL-16941 cloud-init: upstream merge conflict resolution#60
Conversation
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: cloud-init Binary: cloud-init Architecture: all Version: 22.3.4-0ubuntu1~20.04.1 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Homepage: https://cloud-init.io/ Standards-Version: 4.4.1 Vcs-Browser: https://github.com/canonical/cloud-init/tree/ubuntu/devel Vcs-Git: https://github.com/canonical/cloud-init -b ubuntu/devel Build-Depends: debhelper-compat (= 10), dh-python, iproute2, pep8, po-debconf, python3, python3-configobj, python3-debconf, python3-httpretty, python3-jinja2, python3-jsonpatch, python3-jsonschema, python3-mock, python3-netifaces, python3-oauthlib, python3-pytest, python3-pytest-mock, python3-requests, python3-serial, python3-setuptools, python3-yaml, python3-responses Package-List: cloud-init deb admin optional arch=all Checksums-Sha1: bf2732a89b1434b445b4f7d1dcf09c7b1dbf567c 1411035 cloud-init_22.3.4.orig.tar.gz c2bccae1a01927291a180d2823aba549982c64df 86892 cloud-init_22.3.4-0ubuntu1~20.04.1.debian.tar.xz Checksums-Sha256: 75ec2eefecda83d4aea6a10e96c089ee63f83d3ab78b80ab61d93474e95b24b3 1411035 cloud-init_22.3.4.orig.tar.gz dc96e494081527100cb81e336044fd946300c3e8f66b87cdd812e31a8222d625 86892 cloud-init_22.3.4-0ubuntu1~20.04.1.debian.tar.xz Files: 33bcc2bf9b6c2bd8207e69939a2f66d9 1411035 cloud-init_22.3.4.orig.tar.gz 17ff17fd4990cd7278489c8b73537261 86892 cloud-init_22.3.4-0ubuntu1~20.04.1.debian.tar.xz Python-Version: all -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE4lRR4CIbV3Pev/F47NrLFgmVrYkFAmM7Lk0ACgkQ7NrLFgmV rYnmSxAAuH/fme74VV6VTZSe6+hu9PDbCPbA9BDs0/jrUhN2uLq2EZ2kJRJTXK9g n7s9IClZClJLw5WiWriiOD3GupenSQF+SEjt/wEYv8srFIQvPpsC6UUGojzoIE0P UQJdg6YDoe8MdbvnEjHhlceazmWs9I2pzi76gXXZBnIBfReUxAgrxipOi9jhhHBI JrNZsCWA4L4Hkdk01WuG6gBTBRtdFuynD7pGVhFVBb8cwoV8cHR05Q1+AZqqZHGJ G6dQ0YoOf77QtcJLVFKqostv0ZgEG5smUMunSuPUCOpKfz1psQpEckEPi75BaVPJ PwbWhDuLKu/eILIcySxY2oh4oMRjveBa/1rL99f1i+c05INrOLLIOvTeQjcqmh9I JzQJzYIQ3GzEkl2DkBqJvcLyabvQJMLdMh8F68PeKqk7zv/ksGArHCihJXrkvbiP sUEjEqXr1FManJKF9Rdh36abn8xzy8xdLEApWgqtpFrnIoULZAXe38WRvNEQJULL vapHBv1dpIJvEAC6eYDqSd/DNMTejESbyWadjj1mff2mhtY+sL9xE8lRETTDb029 KC4hAjeA1Ni0R3JpQcZ8k98y/wXpYsALB2i5sTfboEobHwGdbXbNbfuNaKZ0tSNC t4kzEOfUgmNmltdGabfNxiqRFsU+qiPFY69I5F8vfybg8SOz2Ho= =yEyl -----END PGP SIGNATURE-----
28a2407 to
61d5115
Compare
edc7e59 to
f7e0b65
Compare
0fd6cc2 to
8598288
Compare
|
Could you provide a description of the merge conflicts that were resolved here? It would be nice to know which files were in conflict and why. This could help future merge conflict resolutions. |
here's a link to the output of the non test conflicts were relatively easy to fix.. e.g. here, we added some code downstream #59, and upstream made a change in the line above, so we had to manually merge them together.. but didn't actually conflict (changes to different, but adjacent, lines). here, we just needed to update based on the name changes.. i.e. here, we just needed to update the code to match based on NIC name, instead of mac address.. this is basically to re-apply the work we previously did to new code.. prior work being PRs like #21 and #23.. then, there were also conflicts in test files.. due to us having removed tests previously, and then those tests being modified.. since modifications to code that we've deleted isn't automatically handled, we need to manually resolve that.. I resolved it by just removing the tests (again), and effectively taking our version of the code.. and lastly, some new tests where added, and needed to be updated to reflect the fact that we're matching on NIC name, rather than MAC address.. e.g. in @mmaybee does this help? |
|
Yes, thank you. |
No description provided.