pcp
[Top] [All Lists]

Re: [pcp] EL6 repo missing pcp-pmda-infiniband and bintray issues

To: Trey Dockendorf <treydock@xxxxxxxx>
Subject: Re: [pcp] EL6 repo missing pcp-pmda-infiniband and bintray issues
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sun, 3 Jan 2016 20:37:11 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <CAJ=Tzi=aZs-rh39OnHA63ZWGCOC27ndaeR8dNXF+Hznck5Ehxw@xxxxxxxxxxxxxx>
References: <CAJ=Tzi=aZs-rh39OnHA63ZWGCOC27ndaeR8dNXF+Hznck5Ehxw@xxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: bOfZMT8rQZTicCzH9FF1XQlj/Z3Q9Q==
Thread-topic: EL6 repo missing pcp-pmda-infiniband and bintray issues
Hi Trey,

----- Original Message -----
> I've noticed the EL6 bintray repo for PCP lacks the pcp-pmda-infiniband
> package. This particular package builds just fine on a CentOS 6.7 system
> once libibmad-devel and libibumad-devel are installed. I haven't yet tested
> the package on a system with infiniband as I'm still in the planning phase
> of deploying PCP.
> 
> Is it possible to get the pcp-pmda-infiniband package added to the bintray
> repo? I see there is a bintray-upload script in PCP source, but not yet
> clear to me if there already exists a mechanism in source to pre-install
> package dependencies for the builds.

I suspect it was an oversight on my part in setting up the build VM.  There
is a qa/admin/check-vm script which verifies machine setup, so I'll get that
fixed up for the next release.

> Also is it intentional that the perfevent package requires libpfm-devel? I
> noticed that in EL6 the papi package contains libpfm.so.3. Is the version is
> EL6 too low to support the perfevent PMDA?

Looking in build/rpm/pcp.spec.in theres a BuildRequires on libpfm-devel,
and a runtime Requires on libpfm4.  Not sure if it works with libpfm.so.3 -
can you try it and let me know?  (the configure.ac code just checks headers
so if those are present, maybe it will work with just a spec file tweak -
not sure).

> Lastly, I am having issues mirroring the bintray repo using Pulp. The issue
> may be a fault of bintray and not the PCP repo itself, but just in case
> something could be fixed I thought I'd mention the issue. I believe the
> issue comes down to repomd.xml for the repo not having a revision defined.

We use ./scripts/bintray-version to set the version info for all repos, so
its possible something is missing there.  AFAICT from the bintray web UI all
version info does seem to be in place though.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>