Hm, so, we've never shipped the testdata. All the way back to the first tag (0.0.0.dev20151104-1), we've removed the testdata. It's only for the test cases, so we don't ship it out in the debs.
An update to the python version caused the way that it was being deleted to break a while ago, it looks like. A user reported it to me recently because it was causing chkrootkit to trip on their systems, so I fixed the removal in 8bb2938. I'm not sure what we should do here. Shipping the testdata isn't a huge amount of resources for the end user, though it's a bit annoying that it's causing some security stuff to complain. We could create an intermediary package that just ships the testdata that we could B-D on, but that seems potentially unnecessary for the additional load on the ftpmasters and the archive. We could also ask upstream to ship the testdata that each package needs with each package. Thoughts? On Sun, Mar 25, 2018 at 10:45 AM, Andrew Starr-Bochicchio <a...@debian.org> wrote: > On Sun, Mar 25, 2018 at 9:47 AM, Jeremy Bicha <jbi...@debian.org> wrote: >> >> error: [Errno 2] No such file or directory: >> '/usr/lib/python3/dist-packages/certbot/tests/testdata/rsa512_key.pem' >> >> Full build log at >> https://launchpad.net/ubuntu/+source/python-certbot-dns-clou >> dflare/0.22.0-1/+build/14491162 >> > > Looks like this was caused by this change in the main certbot package: > > https://salsa.debian.org/letsencrypt-team/certbot/certbot/commit/ > 8bb2938afb15594cb79f8661d951724323f0e754 > > Harlan, any more context on that or concerns about reverting? > > Thanks, > > -- Andrew Starr-Bochicchio > > Debian Developer <http://qa.debian.org/developer.php?login=asb> > Ubuntu Developer <https://launchpad.net/~andrewsomething> > PGP/GPG Key ID: 3B56E2BBD53FDCB1 > > -- Harlan Lieberman-Berg ~hlieberman
