Skip to content
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

completely unrelated dist searched and nothing found for Text::MeCab::Node #524

Closed
wchristian opened this issue Mar 28, 2012 · 9 comments
Closed

Comments

@wchristian
Copy link
Contributor

See: https://metacpan.org/module/Text::MeCab::Node

@benkasminbullock
Copy link
Contributor

On the following line,

https://metacpan.org/source/TOMITA/Acme-Ikamusume-0.06/lib/Acme/Ikamusume/MAParser.pm#L14

package Text::MeCab::Node;

It looks like a clash which the Text::MeCab::Node in the Text::MeCab release should win but didn't.

@monken
Copy link
Contributor

monken commented Mar 30, 2012

A reindex should fix that

@oalders
Copy link
Member

oalders commented Apr 4, 2012

I just tried a re-index, but no joy so far.

@benkasminbullock
Copy link
Contributor

Maybe I am missing something, but I don't really see why reindexing would solve the problem. The Acme::Ikamusume::MAParser module contains a line which it claims to be Text::MeCab::Node, and the indexer does not spot that this is a mismatch between the name of the module and the stated package name.

@monken
Copy link
Contributor

monken commented Apr 4, 2012

from the 02packages file:

Text::MeCab::Node undef T/TO/TOMITA/Acme-Ikamusume-0.06.tar.gz

So metacpan is actually correct.

@wchristian
Copy link
Contributor Author

If that pull request is released another release of Text::MeCab should fix things, right?

@monken
Copy link
Contributor

monken commented Apr 4, 2012

Yes that should do

@monken
Copy link
Contributor

monken commented Apr 4, 2012

You probably won't need a new release of text::mecap as it will fall back to that automatically

@wchristian
Copy link
Contributor Author

tomi-ru has just merged and released, so this should be resolved soon.

edit: and metacpan shows it fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants