6:05 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
now that rpm-kilo is synced from delorean to fedora/master, I see
openstack-neutron-gbp fails due to unsatisfied dependencies (it
currently requires Juno neutron).
I wonder whether that's a good time to move openstack-neutron-gbp
development under delorean roof, and leave fedora/master package as a
downstream just for koji and stuff.
In that way, -gbp package would be able to receive more attention from
neutron maintainers, getting packaging updates in timely manner, and
with review and CI applied.
I'm putting the Fedora package maintainer into CC.
Robert, since you're the maintainer of the Fedora package, could you
please evaluate the option to move the package into Delorean? I think
it would serve both RDO and Fedora and GBP interest better.
Comments?
Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVUzANAAoJEC5aWaUY1u57NIoIAK8940/9xkjZUFvO0CjnPCAc
kiugpBVn0OHaCWPhgV87dGTE3eO+aiP9/a8rLs3BejO1NZ581lDqswJRxEfsMInY
EAa5r9Zzb7eR2EPyzBnqd180yYcSNFSGEh82DBktfmlJKn+wFmjP+FsjrmVgm+le
d4uS5IedcUJJEL8YKhE2+48xnD/J/Yt8EnxOLy26iM1dEEGRKBQKrL+64PemxRw5
ae6v/lmhIVHOoZFB6qIxv2D2GlyYkXrDz+nmPuHt0kr97VkuYllwZmxcu7v7gJIG
VhT4cWs4A2UgwVG9Qb2hTPOfPMUVoDimeiwtChJdFZktSfz0Vj+8t2JhqUBjBEM=
=D4Vt
-----END PGP SIGNATURE-----
2:39 p.m.
Hi Ihar,
GBP development currently trails the main OpenStack development cycle a
bit. Hopefully this lag will shrink substantially for Liberty. We expect
to have a kilo-gbp-3 release out any day that will make sense to package
for RDO and Fedora Kilo versions, and the final Kilo GBP release should
follow soon after. Unfortunately, whats currently packaged still
requires Juno.
Can you explain what exactly it means to "move openstack-neutron-gbp
development under delorean roof"? Does this mean that the Fedora
packages would be generated from the RDO packages? I think that would be
fine. If you will be at the OpenStack summit next week, we can discuss
this there if you like.
-Bob
On 5/13/15 7:05 AM, Ihar Hrachyshka wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
now that rpm-kilo is synced from delorean to fedora/master, I see
openstack-neutron-gbp fails due to unsatisfied dependencies (it
currently requires Juno neutron).
I wonder whether that's a good time to move openstack-neutron-gbp
development under delorean roof, and leave fedora/master package as a
downstream just for koji and stuff.
In that way, -gbp package would be able to receive more attention from
neutron maintainers, getting packaging updates in timely manner, and
with review and CI applied.
I'm putting the Fedora package maintainer into CC.
Robert, since you're the maintainer of the Fedora package, could you
please evaluate the option to move the package into Delorean? I think
it would serve both RDO and Fedora and GBP interest better.
Comments?
Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVUzANAAoJEC5aWaUY1u57NIoIAK8940/9xkjZUFvO0CjnPCAc
kiugpBVn0OHaCWPhgV87dGTE3eO+aiP9/a8rLs3BejO1NZ581lDqswJRxEfsMInY
EAa5r9Zzb7eR2EPyzBnqd180yYcSNFSGEh82DBktfmlJKn+wFmjP+FsjrmVgm+le
d4uS5IedcUJJEL8YKhE2+48xnD/J/Yt8EnxOLy26iM1dEEGRKBQKrL+64PemxRw5
ae6v/lmhIVHOoZFB6qIxv2D2GlyYkXrDz+nmPuHt0kr97VkuYllwZmxcu7v7gJIG
VhT4cWs4A2UgwVG9Qb2hTPOfPMUVoDimeiwtChJdFZktSfz0Vj+8t2JhqUBjBEM=
=D4Vt
-----END PGP SIGNATURE-----
3:05 p.m.
2015-05-14 21:39 GMT+02:00 Robert Kukura <rk(a)theep.net>:
Hi Ihar,
GBP development currently trails the main OpenStack development cycle a bit.
Hopefully this lag will shrink substantially for Liberty. We expect to have
a kilo-gbp-3 release out any day that will make sense to package for RDO and
Fedora Kilo versions, and the final Kilo GBP release should follow soon
after. Unfortunately, whats currently packaged still requires Juno.
Thanks Robert for the heads-up.
I'd rather package as early as possible GBP release, so that we could
test it before the final release. So when kilo-gbp-3 is out, please update the
package in rawhide and ping either apevec or I for RHEL/CentOS builds.
Can you explain what exactly it means to "move
openstack-neutron-gbp
development under delorean roof"? Does this mean that the Fedora packages
would be generated from the RDO packages? I think that would be fine. If you
will be at the OpenStack summit next week, we can discuss this there if you
like.
-Bob
Nope, Delorean is our platform to build packages from master which allows us to
find out and then fix early packaging issues before final releases.
If you're going to Vancouver, please consider attending the RDO meetup !
https://etherpad.openstack.org/p/RDO_Vancouver
If you have questions about Delorean, feel free to ask us, Derek
-Delorean lead- will
be there in Vancouver too.
Regards,
H.
6:50 a.m.
If you have questions about Delorean, feel free to ask us, Derek
-Delorean lead- will
be there in Vancouver too.
And we have docs! Please, before asking Derek, read
https://www.rdoproject.org/packaging/rdo-packaging.html#master-pkg-guide
and let us know or even send PR if something is missing or unclear.
Cheers,
Alan
9:33 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/14/2015 09:39 PM, Robert Kukura wrote:
Hi Ihar,
GBP development currently trails the main OpenStack development
cycle a bit. Hopefully this lag will shrink substantially for
Liberty. We expect to have a kilo-gbp-3 release out any day that
will make sense to package for RDO and Fedora Kilo versions, and
the final Kilo GBP release should follow soon after. Unfortunately,
whats currently packaged still requires Juno.
Can you explain what exactly it means to "move
openstack-neutron-gbp development under delorean roof"? Does this
mean that the Fedora packages would be generated from the RDO
packages? I think that would be fine. If you will be at the
OpenStack summit next week, we can discuss this there if you like.
It's not yet clear what will be the story of official Fedora packages
if/when we exclusively switch to Delorean. It may end up as service
packages (like neutron) being dropped from Fedora. (While Fedora RDO
repos will still be available from RDO project.)
Delorean does not exactly build releases but tracks branches (though I
think there should be a way to generate a repo with particular release
based on a tag; Derek?..)
I will be in Vancouver, so we can chat there, and I will do my best to
explain what Delorean is about.
Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVVgO+AAoJEC5aWaUY1u57oWkH/RvdpU17egd6pC1W3AlmFAvF
6biOZPhXU+wZ+aseF7RJlAm7NFSYtDMNXwMv7HWhnP1oZXxxXGKCorWfX55V3kgK
K7SILSftvmM0JYGfFVtEoqK13zXcI8O0FfRO41S22ZNX+lsIwq9sF3Ngbl+8D7T8
JIGn2MJ8ES3HHOKcydH6Xk7sqsezoKnOfLmYHRWY319Lfloy+lD5Z3cnEUT0h7mA
MLCNqqg+ksd47ZlQfsNN+d3GibjfxDmBy5dtfr9EuiFp0Lz77Um8kozKekKPD1YV
64kyFmWXXWBaSaOmlrn5fvw7CF8k/VFl+ZVXHGnIM+Y4deMjHTWeP6K730TuUXM=
=Peir
-----END PGP SIGNATURE-----
11:40 a.m.
It's not yet clear what will be the story of official Fedora
packages
if/when we exclusively switch to Delorean. It may end up as service
packages (like neutron) being dropped from Fedora. (While Fedora RDO
repos will still be available from RDO project.)
That's premature, let's keep this discussion in separate thread (I
plan to update with +/- points for possible solutions)
For now, dist-git for official RDO builds is in Fedora, GBP packages
are already there and need to be updated in Fedora master branch to
Kilo.
Delorean does not exactly build releases but tracks branches (though
I
think there should be a way to generate a repo with particular release
based on a tag; Derek?..)
Nope. I had locally patched Delorean to build from exactly RC tags but
that doesn't make sense with Delorean design, which is continuous
builds from a branch.
Cheers,
Alan
3480
days inactive
3482
days old
5 comments
4 participants
participants (4)
-
Alan Pevec -
Haïkel -
Ihar Hrachyshka -
Robert Kukura