-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-> FAIL Installing Term::ReadKey failed. #7
Comments
Downgrading totally worked fyi |
Hi,
Please can you add the output of "perl -V" and the run the failing test manually with :
In the directory that you downloaded and unpacked the module. If you don't have the source (I don't know whether cpan minus keeps it hanging around anywhere,) you may need to download it directly from e.g. https://cpan.metacpan.org/authors/id/J/JS/JSTOWE/TermReadKey-2.33.tar.gz and unpack it etc. Bear in mind that it is not possible to test against every possible version of perl on every possible operating system before release so these things may happen. |
It might be https://github.com/jonathanstowe/TermReadKey/blob/master/t/02_terminal_functions.t#L41 skipping 1 test but the plan is to run 7 tests. ac5e11f looks like it should workaround it too |
Fixes: shedd/duckpan-vagrant #34 Worksaround: jonathanstowe/TermReadKey#7
Fixes: shedd/duckpan-vagrant #34 Worksaround: jonathanstowe/TermReadKey#7
I'm having problems with this issue as well - is there any chance of the fix being released to CPAN? |
I'm getting this error when performing a Docker build. Running docker with an interactive terminal has all tests passing, and forcing 2.32 also installs fine non-interactively |
This reverts commit da1dd7d. The tests fail in builder when abuild is run without terminal. Upstream bug: jonathanstowe/TermReadKey#7
This should all be fixed up with the v2.34 release which I am just going sending to CPAN now. |
Great timing - thanks! Just found myself on this page following up my own Docker install. |
Let me know how it goes :) |
Hmmm... doesn't seem to work for me (directly from github release).
|
Perl stuff:
|
For info - if you have docker installed and running then this can be reproduced with:
|
Okay that is a bit odd, it's a 5.24.0 thing, it appears that the Makefile doesn't run the scripts with 'blib'; Which is surprising, I've fixed it locally, but it may take a little time to test. |
Thanks for looking into it - will check in later, let me know if I can help |
I've created a specific issue for the above in #21 |
I'm going to close this issue now, as I am fairly certain the original problem is now fixed even if there are certain other issues with the subsequent release. Please make separate issues for any further problems. |
Morning all,
Looks like yesterday's update may have broke something...
I am no perl guy but could this have something to do with the unit tests? Installing this package is part of our deployment scripts for new environments, so we download and install it multiple times per day. This morning I hit this error and I think there was an update last night. I am trying to downgrade now.
Thanks!
The text was updated successfully, but these errors were encountered: