did you try asking the rally folks about it? Maybe it was a simple oversight? Thanks, Kevin ________________________________________ From: rdo-list-bounces(a)redhat.com [rdo-list-bounces(a)redhat.com] on behalf of Steve Linabery [slinaber(a)redhat.com] Sent: Thursday, September 10, 2015 7:53 AM To: rdo-list(a)redhat.com Cc: apevec(a)redhat.com Subject: [Rdo-list] openstack-rally in delorean I have started investigating packaging rally. One of the problems I'm hitting is something we also hit (and never, afaik, resolved) when packaging openstack-tempest. Upstream does not provide a tarball for rally via launchpad, so building a rally RPM doesn't work quite the same as, say, nova. In particular, the PKG-INFO file which you get from e.g. nova via launchpad is not present in the rally 0.0.4 tarball you get from github. This causes pbr to complain that it's not being run in a git repo and it can't figure out versioning. I've worked around this in my poc spec/rpm by patching in a 'dummy' PKG-INFO file (which I cut-n-pasted from nova). Two questions for this group. 1) What do we think of this approach of including a fabricated PKG-INFO file to define the version info for pbr et al? 2) If we like this idea, how does this fit in with delorean? IIUC, going forward we want to avoid using midstream repos. What about using https://github.com/openstack/rally as the upstream and something in github.com/redhat-openstack as a patches branch containing the PKG-INFO file alone? I guess what I'm asking is where should we maintain a PKG-INFO file of our own creation. Maybe where we keep the spec? Thanks in advance for your thoughts. Steve Linabery (freenode: eggmaster) _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe(a)redhat.com

delorean does not run from those tarballs anyway. It runs from tarballs generated from git using python setup.py sdist, and those include proper PKG-INFO. If you want to have it in RDO, you can just build the tarball yourself and publish it somewhere. Or better, make the project publish correct tarballs on LP or pypi. Ihar

Ask them nicely? :) Or just do the former, you don't even need to publish it somewhere, just provide reproducible steps how to generate it: https://fedoraproject.org/wiki/Packaging:SourceURL#Using_Revision_Control

On Thu, Sep 10, 2015 at 09:20:23PM +0200, Haïkel wrote: Splendid! I am glad I emailed; didn't know the packaging effort was this far along. Victoria, any reason not to use 0.0.4 (current upstream rally release)? s|e

On Fri, Sep 11, 2015 at 11:36:33AM -0300, Victoria Martinez de la Cruz wrote: I updated the spec to use 0.0.4 and changed a path in the %files section for the bash completion config (not sure about that use of macros but it works). Here [1], if it's helpful. Ran mock and rpmlint gives only warnings, no errors. hth s|e [1] https://slinabery.fedorapeople.org/openstack-rally.spec