On Thu, Nov 24, 2016 at 12:01:20PM +0000, Dominic Hargreaves wrote: > Firstly, I'm sorry that you didn't get any response on this, and thank > you for pushing this issue. I must confess to being rather frustrated > by the situation as well as not having any spare cycles for Debian > work for a while. > > It seems like at least for RT, any update to a version of > libgnupg-interface-perl which drops support for gpg1 is going to be > quite invasive, because the RT test suite depends on a particular > version of gpg. I note you didn't get any response on the gnupg upstream > portability issue - was there any other progress on that front? It > would certainly be much easier for upstream to take the patchset if > it didn't break compatibility with GPG1 (even if we might be able to > do so in Debian). > > I will try and do some testing with RT and the version of this pacakge > in experimental. Do you have any idea whether the other rdeps are > similarly sensitive? > > FTR, I've just filed #845534 about another related issue which I failed > to spot; RT is currently configured to use gpg1 for tests, but the default > (which is now gpg2) at runtime, and that probably doesn't work. > > (GPG isn't that commonly used in RT, so I wouldn't be surprised if this > hasn't been road tested in sid :( )
FTR: I've filed #845781 against libgnupg-interface-perl, which is probably the right place to continue this discussion. Best, Dominic.
