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
Could not find symbol '&parse-string' in installed module, local version works fine. #4316
Comments
From @dnmfarrellWhen I clone my Perl 6 repo Pod::Perl5, and use it, it runs fine. When I install the module using panda and try to use it, I get an error: "Could not find symbol '&parse-string' Steps to reproduce git clone https://github.com/dnmfarrell/Pod-Perl5 |
From @hoelzroOn Wed Jun 10 19:45:42 2015, davidnmfarrell@gmail.com wrote:
I managed to golf it down quite a bit; see the attached tarball. |
From @hoelzro |
The RT System itself - Status changed from 'new' to 'open' |
From @hoelzroOn Wed Jun 10 19:52:14 2015, rob@hoelz.ro wrote:
Sounds similar to https://rt-archive.perl.org/perl6/Ticket/Display.html?id=122773 |
From @AlexDanielThis is no longer reproducible (2017.11,HEAD(e5b660e)), and RT# 122773 seems to be resolved. Any chance we can have a test for it? If not, maybe we can close this particular ticket without tests… On 2015-06-10 19:52:34, rob@hoelz.ro wrote:
|
From @AlexDanieljmerelo++ brought this ticket to my attention during the squashathon and suggested that this ticket can be closed. I've tried reproducing the issue with the provided tarball and couldn't. In fact, the Makefile in that tarball no longer works as expected because things are very different now. Moreover, panda was replaced by zef. I think an issue like this will be promptly noticed today, and chances are we have tests for it already. I think after 3 years we can confidently say that this particular ticket outlived itself. Closing without tests, please file a new ticket if you see similar issues. On 2017-12-02 20:04:23, alex.jakimenko@gmail.com wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125384 (status was 'resolved')
Searchable as RT125384$
The text was updated successfully, but these errors were encountered: