Paul Gevers <[email protected]> writes: > I rather expect in the tool-chain. Has anybody seen the recent change in > Perl? Your remarks about including ./ in the Perl path sounds exactly > like the change that was recently made: > > https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html
Oh, nice find. So then it seems it _is_ only the missing '.' in @INC. In that case, either of my two proposed patches should work to solve the problem (and there is no need for the -U in the second patch). Otto, I'd suggest committing the second patch, adding `perl -I.` on the command line to run the test (you can omit the -U). This should be quite safe, and it sounds like it will fix the problem. And I'll see if I can fix mysql-test-run.pl upstream to not need '.' in @INC. Otherwise, this problem will probably show up in other places sooner or later... > Indeed, and you can even run it on your own system (which I also since > recently do) by installing autopkgtest. > > adt-run --user debci --output-dir /tmp/output-dir ./ --shell-fail > --apt-upgrade --- lxc --sudo adt-sid-amd64 > > runs the test-suite in the current (./) package directory and gives you Ok, cool, I thought I'd need eg. some kind of virtual/container image and/or a system running unstable.... Thanks, - Kristian.
