[Rdo-list] Packaging workflow questions

[Mike Burns]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/19/2015 05:37 AM, Alan Pevec wrote:
> 2015-03-19 3:37 GMT+01:00 Lars Kellogg-Stedman <lars at redhat.com>:
>> More packaging workflow questions for y'all... Here is a bug
>> against tuskar-ui in RHEL-OSP that is purportedly fixed: 
>> https://bugzilla.redhat.com/show_bug.cgi?id=1179821 There is a
>> corresponding bug against RDO: 
>> https://bugzilla.redhat.com/show_bug.cgi?id=1176596 Since
>> RHEL-OSP is *downstream* from RDO (which is downstream from 
>> Delorean), I would expect to find the fix in the 
>> openstack-packages/tuskar-ui repository.  But checking that out: 
>> git clone
>> ssh://larsks@review.gerrithub.io:29418/openstack-packages/tuskar-ui
>>
>> 
And running `git log`, the most recent change noted is from back in
>> August...whereas fedora/master shows several commits in October
>> that aren't reflected in the Delorean repository.
>> 
>> What's the story here?
> 
> It's up to the package maintainer to "see the light" and follow 
> proposed master packaging guidelines for openstack packages. AFAICT
> openstack-tuskar* maintainer in Fedora was jomara, who did the last
> build in Koji and jrist took over in pkgdb: 
> https://admin.fedoraproject.org/pkgdb/package/openstack-tuskar-ui/
> 
> Mike, Jason, I see rdo-management has forked specs in 
> https://github.com/rdo-management/tuskar-ui-packaging/ and runs 
> separate Delorean instance
> https://github.com/rdo-management/rdoinfo What's preventing you to
> merge to openstack-packages and use trunk.rdoproject.org aka
> one-true-Delorean instance? Otherwise, we should remove rdo-mgmt
> stuff from https://github.com/redhat-openstack/rdoinfo/ and from 
> openstack-packages to avoid confusion.

IIRC, openstack-packages has a pretty hard rule that it's pure
upstream + patches required for packaging only, right?  That's fine
for a package that lands in the core delorean instance, but is not
sufficient for rdo-manager.  Our requirement is that we need to be
able to take patches (especially speculative patches) more
aggressively from upstream than you're willing to in trunk.

If we remove all the rdo-manager components from trunk, then we end up
without those components being available in core RDO at all.  I think
we need them in both locations going forward and just need to say that
packages in trunk follow true upstream and packages in trunk-mgt are
only for rdo-manager.

As for Koji, I would expect that it would more closely follow the
trunk methodology.

Mike

> 
> 
> Cheers, Alan
> 
> _______________________________________________ Rdo-list mailing
> list Rdo-list at redhat.com 
> https://www.redhat.com/mailman/listinfo/rdo-list
> 
> To unsubscribe: rdo-list-unsubscribe at redhat.com
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVCriZAAoJEFyZ9i2wlykqdLUH/1+9iPxPnFsdTh84KnU3r6lS
xyd/zKSFZ7FQgnWz1i7Gzx85vKW30v97cYWjOqCpduZrz57TPLVjpbMbmINQocWH
2hUaKzcdmUibE7gmXTqSSGVX/KGo6XLM7JiKQfBduGbcsDOMH54L495aWr16vI2p
VIxEVYmpog3FiIiAURP2Mp/oMGUODAqA0RskAVQW7meVlGnX6D+CWUp26hexEa0W
keK3e8l+ST7varMrZ0zn34aPoG/6TYnnJhyZIgOjIAQOw66wmOAHUsNl7aaD71Na
h3bvUMlCl5ScasDNMcLn6HIeAkPMI4cuiRxtzOMeaDTZe7ZQULMzH4euCbiGQ9Q=
=qv18
-----END PGP SIGNATURE-----