On Mon, 10 Oct 2016 23:10:30 +0300, Niko Tyni wrote: > Help untangling this mess would be very welcome, as both Dominic and I > are rather short on time. Tagging and copying possible candidates :)
Good news: I got the package to build. Bad news: Only by forcing gpg1 even harder in the test suite. For gpg2 I guess we'd need a fake pinentry and maybe also changes to the secret key layout etc. -- Material for dkg maybe :) lib/RT/Test/GnuPG.pm looks interesting for setting the gpg config, lib/RT/Test.pm has import_gnupg_key. What I don't know is if RT4 in the current state now works with gpg2 when the test suite passes with gpg1 ... Maybe forcing it to gpg1 (in etc/RT_Config.pm.in and debian/control) would buy some time. But in general I guess we want gpg2 both at buildtime and runtime. Before getting that far, I had to make some other changes to reduce the build failures to the gpg related ones. After the package built I also fixed some lintian errors :) Additionally I noted that the build tried to connect to IP addresses beyond localhost (my DNS server and my gateway). Attached is a patch series. Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Element of Crime: Nur mit dir
rt4.tar.gz
Description: application/gzip
signature.asc
Description: Digital Signature
