On 8/23/22 16:42, Martina Ferrari wrote:
Hi Reinhard, et al. I saw that consul is going to be removed from testing in just 7 days, along with a bunch of packages that depend on it. I was about to prepare a new release for 1.8 to solve some of the issues, but then I saw that you have already backported the fixes I was hoping to include. Is there any reason you have not uploaded yet? Can I help somehow? PS: I have cloned bug #1015218 into #1017982, to separate the CVS issues. So the former can be closed with your patch, while the latter will probably require an upgrade to 1.9.
Hi Martina, thanks for your work. After I poked around with the upstream commits, I realized that the most pragmatic way is likely to just package a new upstream version. However, I'm not familiar with the consul software at all, so I started looking in where it is used. Turns out, that it was rather easy to avoid in the container stack, so I went for that. I personally don't have a strong opinion on whether we ship consul in Debian or not, but I do care about package that might depend on it much more strongly. Can you please point me to some other packages that are affected by the removal of the consul package in testing? Best, -rt
