>>>>> On Sat, 24 Nov 2018 08:50:37 +0800, "CC" <[email protected]> said:
> The file already contains META information. Why can't it be found? > Why did the first version pass, and subsequent versions fail, without > much change? The file CCLog-0.0.1.tar.gz looks fundamentally different than the files CCLog-0.0.[23456].tar.gz. The difference has been described with this paragraph: > The distribution does not unpack into a single directory and is > therefore not being indexed. Hint: try 'make dist' or 'Build dist'. > (The > directory entries found were: .gitattributes Build.pm6 CCLog LICENSE > META.json META6.json Makefile README.md install.sh) How can I convince you? I illustrate it with this command: : % for f in `seq 1 1 6`; do : for> tar tvzf CCLog-0.0.$f.tar.gz | grep Build.pm6 : for> done : -rw-rw-r-- root/root 1095 2018-11-01 11:30 CCLog-0.0.1/Build.pm6 : -rw-rw-r-- root/root 1111 2018-11-02 11:01 Build.pm6 : -rw-rw-r-- root/root 1111 2018-11-02 12:31 Build.pm6 : -rw-rw-r-- root/root 1111 2018-11-07 15:48 Build.pm6 : -rw-rw-r-- root/root 1111 2018-11-16 05:36 Build.pm6 : -rw-rw-r-- root/root 1111 2018-11-23 15:18 Build.pm6 This should show you that the files 2..6 do unpack the file Build.pm6 into the current directory. This does not match the perl/CPAN packaging conventions. Perl packaging convention seem to have been fulfilled by CCLog-0.0.1.tar.gz: unpack into a single directory. I hope this helps you to find the proper next steps. If not, let us know how we can help you. -- andreas
