Bug#808880: Package uploaded
On 01/30/2016 11:57 PM, Daniele Tricoli wrote:
> To reply to your question: the only problem I see here is that you can't push
> commit on DPMT repositories, right?
That's not the only problem. Betamax will (and currently is) an imporant
dependency of OpenStack packages. Meaning that having it to pop in the
PKG OpenStack makes a lot of sense. Also, usually for OpenStack, I very
much dislike being slowed down because I can't update one of the
dependencies (I do at least 5 or 6 uploads every day).
Or is it that Betamax is about to be used by anything else than OpenStack?
> I will be happy to accept any patch that improve the packaging, and you know
> I'm usually fast on handling issues (yes, writing email has a low priority...
> :D).
> Is this still a concern for you?
Yes, as I would have like to be a co-maintainer, and push updates myself
to the Git, so things can be done in 30 minutes instead of a minimum of
3 days (for emails to go back and forth).
> I was thinking from a bit of time, this email only reminded my thoughts: since
> PKG-OpenStack team maintains also packages not strictly related to OpenStack
> (I'm not involved so I would not be a good choice to help there) it would be
> accepted a request to join the team from me, only to do QA work on OpenStack
> dependencies (To be more clear, I mean packages like python-invocations,
> python-greenio, etc: so general packages used by OpenStack)?
I very much would welcome help. For these 2 packages, I tried to fix
things, and couldn't find a solution yet. As they aren't really used
*yet* (ie: it's to be used by Fuel, which I didn't start uploading to
Debian yet), it has a lower priority. So by all means, please help on
these 2 packages.
> This way I will be more involved on PKG-OpenStack side and maybe you will have
> less concern on having betamax on DPMT. :)
Are you interested in OpenStack? :)
Cheers,
Thomas Goirand (zigo)
Reply to: