On Tue, 2012-06-26 at 15:17 +0200, David Disseldorp wrote:
> On Tue, 26 Jun 2012 10:42:57 +1000
> Ken McDonell <kenj@xxxxxxxxxxxxxxxx> wrote:
>
> > # --- MakeMaker distmeta section:
> > distmeta : create_distdir metafile
> > $(NOECHO) cd $(DISTVNAME) && $(ABSPERLRUN) -MExtUtils::Manifest=maniadd -e 'eval { maniadd({q{META.yml} => q{Module meta-data (added by MakeMaker)}}) } ' \
> > -e ' or print "Could not add META.yml to MANIFEST: $${'\''@'\''}\n"' --
> >
> > This comes from Perl automake magic that we don't control ... there is
> > no reference to yml in the Makefile.PL that is used to generate
> > Makefile.
>
> Yes, but there is a reference to META.yml in MANIFEST files shipped with
> the pcp-3.6.4-1.src.tar.gz tarball, it is _not_ present in the git tree
> tree.
Where does this tarball come from?
I've tried installing the src RPM (built from a git-based build on
SuSE), and unpacking the pcp-3.6.4-1.src.tar.gz from there and there is
no .yml reference in any of the MANIFEST files, so where does your
tarball come from?
> Full build logs can be found at:
> https://build.opensuse.org/package/rawlog?arch=x86_64&package=pcp&project=home%3Admdiss%3Apcp_perl_manifests&repository=SLE_11_SP2
>
> We will continue to run with the following patch:
> https://build.opensuse.org/package/view_file?file=fix_cpan_pmda_manifest.patch&package=pcp&project=home%3Admdiss%3Apcp_commonspec&rev=0290d15eaae597d4b4dce8d77aa76e7f
Thanks for this, but I'm still in the dark I'm afraid. ... the patch
only makes sense if there is .yml lines in the MANIFEST files, but I
don't yet understand how you get to this starting point.
If someone else understands this better than I, please jump in.
_______________________________________________
pcp mailing list
pcp@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/pcp
|