AFS-Command 1.0 Deleted
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Add =head1 LICENSE and the text of the license to the main module in your code.
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
- MANIFEST (53) does not match dist (57):
- Missing in MANIFEST: lib/AFS/Command/BOS.pod, lib/AFS/Command/FS.pod, lib/AFS/Command/PTS.pod, lib/AFS/Object.pm, lib/AFS/Object.pod, lib/AFS/Object/ACL.pm, lib/AFS/Object/BosServer.pm, lib/AFS/Object/CacheManager.pm, lib/AFS/Object/Cell.pm, lib/AFS/Object/FileServer.pm, lib/AFS/Object/Group.pm, lib/AFS/Object/Instance.pm, lib/AFS/Object/PTServer.pm, lib/AFS/Object/Partition.pm, lib/AFS/Object/Path.pm, lib/AFS/Object/Principal.pm, lib/AFS/Object/RCS, lib/AFS/Object/Server.pm, lib/AFS/Object/User.pm, lib/AFS/Object/VLDB.pm, lib/AFS/Object/VLDBEntry.pm, lib/AFS/Object/VLDBSite.pm, lib/AFS/Object/VolServer.pm, lib/AFS/Object/Volume.pm, lib/AFS/Object/VolumeHeader.pm
- Missing in Dist: lib/AFS/Command/Result.pm, lib/AFS/Command/Result.pod, lib/AFS/Command/Result/ACL.pm, lib/AFS/Command/Result/BosServer.pm, lib/AFS/Command/Result/CacheManager.pm, lib/AFS/Command/Result/Cell.pm, lib/AFS/Command/Result/FileServer.pm, lib/AFS/Command/Result/Group.pm, lib/AFS/Command/Result/Instance.pm, lib/AFS/Command/Result/PTServer.pm, lib/AFS/Command/Result/Partition.pm, lib/AFS/Command/Result/Path.pm, lib/AFS/Command/Result/Principal.pm, lib/AFS/Command/Result/Server.pm, lib/AFS/Command/Result/User.pm, lib/AFS/Command/Result/VLDB.pm, lib/AFS/Command/Result/VLDBEntry.pm, lib/AFS/Command/Result/VLDBSite.pm, lib/AFS/Command/Result/VolServer.pm, lib/AFS/Command/Result/Volume.pm, lib/AFS/Command/Result/VolumeHeader.pm
Make sure that the main module name and version are the same of the distribution.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Fix MANIFEST (or MANIFEST.SKIP) to exclude dot directories from a distribution. Use an appropriate tool and avoid archiving your working directory by hand. If you switch your version control system, remove old VCS directories after you migrate.
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: AFS::Command::BOS, AFS::Command::Base, AFS::Command::FS, AFS::Command::PTS, AFS::Command::VOS, AFS::Object, AFS::Object::ACL, AFS::Object::BosServer, AFS::Object::CacheManager, AFS::Object::Cell, AFS::Object::FileServer, AFS::Object::Group, AFS::Object::Instance, AFS::Object::PTServer, AFS::Object::Partition, AFS::Object::Path, AFS::Object::Principal, AFS::Object::Server, AFS::Object::User, AFS::Object::VLDB, AFS::Object::VLDBEntry, AFS::Object::VLDBSite, AFS::Object::VolServer, AFS::Object::Volume, AFS::Object::VolumeHeader
Ask the owner of the distribution (the one who released it first, or the one who is designated in x_authority) to give you a (co-)maintainer's permission.
|AFS::Command::BOS||OO API to the AFS bos command||1.0||metacpan|
|AFS::Command::Base||Base OO Class for AFS::Command::* API||1.0||metacpan|
|AFS::Command::FS||OO API to the AFS fs command||1.0||metacpan|
|AFS::Command::PTS||OO API to the AFS pts command||1.0||metacpan|
|AFS::Command::VOS||OO API to the AFS vos command||1.0||metacpan|