[request-tracker-maintainers] Bug#839580: request-tracker4: FTBFS in testing (failed tests)

[Dominic Hargreaves]

On Wed, Nov 23, 2016 at 06:26:45PM -0500, Daniel Kahn Gillmor wrote:
> On Tue 2016-10-11 23:48:15 -0400, Daniel Kahn Gillmor wrote:
> > Those patches are posted here:
> >
> >  https://github.com/bestpractical/gnupg-interface/pull/1
> >
> > I'd like to upload them to debian as well, though they are *not*
> > interoperable with versions of GnuPG prior to 2.1.x, due to GnuPG's
> > non-portable interface :/ I've pushed a proposed upload to experimental
> > to the move-to-modern-gnupg branch on
> > https://anonscm.debian.org/git/pkg-perl/packages/libgnupg-interface-perl.git
> >
> > (see also discussion around this portability issue here:
> > https://lists.gnupg.org/pipermail/gnupg-devel/2016-October/031800.html)
> >
> > sigh...
> >
> > Any thoughts on the right thing to do with libgnupg-interface-perl?
> 
> I haven't heard anything about this -- either from upstream, or from
> other debian perl or gnupg folks.  I've gone ahead with the experimental
> upload, so please let me know if you see this causing trouble.

Hi Daniel,

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 :( )

Cheers,
Dominic.