Hello Thomas, sorry for this late reply, this new year started with a lot of things to do! On Thu, 14 Jan 2016 15:15:59 +0800 Thomas Goirand <zigo@debian.org> wrote: > Hi, > > Since I've seen no progress in this RFS, that the latest keystoneauth1 > needs it (which blocked me), and I know Paultag is a busy person, I have > sponsored the upload of this package. Many thanks for the upload! I supposed the same not receiving an update from paultag! :) > However, I still didn't get a reply on the important topic which I > raise: why not pushing this package to the PKG OpenStack group, rather > than the DPMT, as this seems to be a better fit? I don't see any other > reverse dependency in the archive but the one I just mentioned above. > Please reply to this question. Sorry as I said, I did not reply only because I was very busy at the start of this year. To reply to your question: the only problem I see here is that you can't push commit on DPMT repositories, right? 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? 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)? This way I will be more involved on PKG-OpenStack side and maybe you will have less concern on having betamax on DPMT. :) Cheers, -- Daniele Tricoli 'eriol' https://mornie.org
Attachment:
signature.asc
Description: This is a digitally signed message part.