Hi Trey,
----- Original Message -----
> [...]
> Thanks. Is the process used to build the PCP RPMs documented somewhere? I
> am building mine on VM using './Makepkgs --verbose'. I'd be happy to
> submit pull request if I'm able to test my changes using same steps that
> are used to build the official RPMs.
The process is exactly that - using Makepkgs on a clean virtual machine with
dependencies from the qa/admin/check-vm script satisfied as far as possible.
> > 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.
>
> It appears like the issue is lack of "<revision>" value. Looking at repo
> like EPEL I notice this "<revision>1451843961</revision>" while the bintray
> repo has "<revision />". My guess is the API calls to bintray trigger the
> repo creation in some non-standard way which is likely a bintray issue not
> specific to PCP.
Hmmm. I've scanned https://bintray.com/docs/api/ a bit and cannot find a
way to write that value, so I guess you're right and it must be generated
by bintray after uploading (probably in the calc_metadata phase).
cheers.
--
Nathan
|