Ok, thanks!I have to admit that my main motivation in getting consul fixes is keeping docker.io and podman in testing. I was under the wrong impression that nomad was already out of testing because #973166 hit me in various rebuilds. My bad, happy to upload nomad as well on your behalf.Adrian, Michael, any chance you could advise on what's going on in https://ci.debian.net/data/autopkgtest/testing/amd64/p/patroni/8668662/log.gz and how to resolve this?
Best,-rtOn Mon, Dec 7, 2020 at 12:17 AM El boulangero <elboulangero@gmail.com> wrote:Hello Reinhard!I have no idea what patroni is, so I can't really help.BTW, this upload of consul also broke the nomad build (which was broken anyway), but it was easy to fix, and so there should be soon a new version of nomad ready in Debian.In the consul package there is this note in `debian/README.source`:> Consul must stay in sync with Nomad as the latter may not build with newer
> releases than what upstream vendores with Nomad.So even though I could fix the nomad build, I have no idea of how nomad and consul relate to each other, and I can't say if more things are broken, or if everything is alright. Hopefully everything is alright :)Good luck with the patroni thing,ArnaudOn Mon, Dec 7, 2020 at 5:21 AM Reinhard Tartler <siretart@gmail.com> wrote:Hi Arnaud, hi consul and patroni package maintainers,I took the liberty of uploading your package update to consul in order to get #975584 fixed (in the hope it doesn't lead to removal of docker.io and podman and friends). Unfortunately, it seems that it breaks autopkgtests in the patroni package here:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/patroni/8668662/log.gz
The thing is, I honestly don't get what in consul would break patroni. Is it possible that the autopkgtest broke for reasons unrelated to consul? -- I'm not familiar with python behave tests, and may that makes the log very hard for me to decipher.
What do you think is the best way to proceed from here?--regards,
Reinhard--regards,
Reinhard