On 13/05/13 10:17, Nathan Scott wrote:
> Hi Ken,
>
> ----- Original Message -----
>> I need someone to help resolve the problem below that I reported several
>> days ago and leaves rpm packaging broken on at least Fedora 18.
>
> Did 3.7.2 work on this host (vm03)? I don't think we've got anything
> new/changed in the perl build since 3.7.2, so seems odd. If it passed
> in 3.7.2, then there might be something strange in the qa host setup -
> the auto-builders here had no problem with f18 (although that's not
> using the Makepkgs script).
Yes ... only started failing in the last week, may be 2 weeks. Is there any
parallel gmake being done in the rpm packaging?
>> == Packaging pcp, log is in /home/kenj/src/pcp-dev/Logs/pcp
>> Packaging failed, see log in /home/kenj/src/pcp-dev/Logs/pcp
>
> (anything interesting in the tail of that log file?)
Not that I can see ... it ends like this
gzip --best PCP-PMDA-1.14.tar
/usr/bin/gmake -f Makefile install DESTDIR=$DIST_ROOT; find $DIST_ROOT//usr
-name .packlist -exec mv '{}' ../../../perl-pcp-pmda.list ';' ; if [ -s
../../../perl-pcp-pmda.list ] ; then _sfx=.gz; false && _sfx=.bz2; false &&
_sfx=.lzma; false && _sfx=.xz; sed -n -e '/\.bs$/d' -e 's/\.[0-9]pm$/&'"$_sfx/"
-e "s@^$DIST_ROOT@@p" ../../../perl-pcp-pmda.list
>../../../perl-pcp-pmda.list.tmp; mv ../../../perl-pcp-pmda.list.tmp
../../../perl-pcp-pmda.list; else echo "Arrgh ... no files to include in
package via ../../../perl-pcp-pmda.list"; exit 1; fi; find $DIST_ROOT//usr
-name perllocal.pod -exec rm -f '{}' ';' ; find $DIST_ROOT//usr -name \*.bs
-exec rm -f '{}' ';' ; find $DIST_ROOT//usr -name PMDA.so -exec chmod 755 '{}'
';'
Files found in blib/arch: installing files in blib/lib into architecture
dependent library tree
Installing
/home/kenj/src/pcp/BUILDROOT/pcp-3.8.0-6.x86_64/home/kenj/perl5/lib/perl5/x86_64-linux-thread-multi/auto/PCP/PMDA/PMDA.bs
Installing
/home/kenj/src/pcp/BUILDROOT/pcp-3.8.0-6.x86_64/home/kenj/perl5/lib/perl5/x86_64-linux-thread-multi/auto/PCP/PMDA/PMDA.so
Installing
/home/kenj/src/pcp/BUILDROOT/pcp-3.8.0-6.x86_64/home/kenj/perl5/lib/perl5/x86_64-linux-thread-multi/PCP/PMDA.pm
Installing
/home/kenj/src/pcp/BUILDROOT/pcp-3.8.0-6.x86_64/usr/share/man/man3/PCP::PMDA.3pm
Appending installation info to
/home/kenj/src/pcp/BUILDROOT/pcp-3.8.0-6.x86_64/home/kenj/perl5/lib/perl5/x86_64-linux-thread-multi/perllocal.pod
Arrgh ... no files to include in package via ../../../perl-pcp-pmda.list
gmake[5]: *** [install] Error 1
gmake[4]: *** [install] Error 2
gmake[3]: *** [install_pcp] Error 2
gmake[3]: Leaving directory `/home/kenj/src/pcp/pcp-3.8.0/src'
gmake[2]: *** [install_pcp] Error 2
gmake[2]: Leaving directory `/home/kenj/src/pcp/pcp-3.8.0'>
> cheers.
>
> --
> Nathan
>
error: Bad exit status from /var/tmp/rpm-tmp.NkTIBk (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.NkTIBk (%install)
> ...
>>> 359 - pmdasystemd failure - all metrics getting illegal pmid
>>> (this is notrun for me, I have no QA hosts sufficiently modern
>>> as yet - on the todo list, but wont happen overnight)
>>> [fche? - see test 652 as well, looks related]
>>
>> Is being run and passing on other hosts, so not sure about this one.
>
> I had another look into this one, and I'd punt this is a test failure.
> this test is susceptible to residual metric names in the namespace, and
> somehow you had pmdasystemd names in the PMNS at the start of the test,>
> cheers.
>
> --
> Nathan
>
> but no pmcd.conf entry for that PMDA. I think.
Hmm OK, we have other QA tests for other PMDAs that have exhibited the same
bogus behaviour, namely leaving names in the PMNS but the PMDA unconfigured.
On vm03 your guess is correct. If I get vm03 working again, I'll investigate
there.
> ...
>>> 652 - another systemd failure - oh, looks like the metrics changed (ISTR
>>> suggesting this) and perhaps the test was not updated? Lets prod
>>> Frank for his verdict, but this looks to me like a bad .out file.
>>> [fche - possibly just a qa/remake needed by kenj?]
>>
>> Can't test due to rpm build issue above. Not obviously run elsewhere.
>>
>
> Should work now, Franks confirmed that a remake was in order.
Need a working vm03 before I can check this.
|