I just did an emerge --sync and while updating the cache, it said there was an invalid ebuild name: Invalid ebuild name: /usr/local/portage/perl-gcpan/junoscript-perl-6.4I0/junoscript-perl-6.4I0-.ebuild Reproducible: Always Steps to Reproduce:
What version of g-cpan was that ebuild created with? Looks like an old bug, but just want to be sure (you can, of course, rm the file/dir, and regenerate it later)
sorry for the double post and the assignment mess, kids hit the keyboard as i was sending
I removed the file. I didn't get a chance to check what version it was generated with. Unfortunately it looks like my g-cpan is broken and I have no idea how to fix it. I get this when I issue this command: g-cpan -a junoscript-perl CPAN: File::HomeDir loaded ok Sorry, we have to rerun the configuration dialog for CPAN.pm due to the following indispensable but missing parameters: mbuild_arg, mbuild_install_arg, mbuild_install_build_command, mbuildpl_arg The next questions deal with Module::Build support. A Build.PL is run by perl in a separate process. Likewise we run './Build' and './Build install' in separate processes. If you have any parameters you want to pass to the calls, please specify them here. Parameters for the 'perl Build.PL' command? Typical frequently used settings: --install_base /home/xxx # different installation directory Your choice: [] Parameters for the './Build' command? Setting might be: --extra_linker_flags -L/usr/foo/lib # non-standard library location Your choice: [] Do you want to use a different command for './Build install'? Sudo users will probably prefer: su root -c ./Build or sudo ./Build or /path1/to/sudo -u admin_account ./Build or some such. Your choice: [./Build] ./Build Parameters for the './Build install' command? Typical frequently used setting: --uninst 1 # uninstall conflicting files Your choice: [] Please remember to call 'o conf commit' to make the config permanent! CPAN: Storable loaded ok Can't call method "can" without a package or object reference at /usr/lib64/perl5/vendor_perl/5.8.8/CPAN.pm line 2904.
That's a result of using g-cpan to upgrade CPAN itself at some point - latest versions of g-cpan properly deal with the newer CPAN.pm versions :)
Closing wrt the comment above.
