I apologize for insisting here, but I need this RC fixed ASAP for another package relying on it and have no idea what to do now.
Thanks, Ghis On Wed, 2017-01-18 at 17:53 +0000, Ghislain Vaillant wrote: > On Wed, 2017-01-18 at 13:37 +0100, Piotr Ożarowski wrote: > > Hi, > > > > [Ghislain Vaillant, 2017-01-18] > > > Would you be ok if I push the changes required to fix #830399 and > > > #841043 for src:python-jedi and prepare a team-upload? > > > > > > I need the RC fixed for the packaging of spyder. > > > > go ahead. I have almost working package with latest changes from upstream > > git repo but some tests still fail and I don't have time to work on it > > right now. > > Ok, I have got a working package fixing the RC. However, whoever did > the migration from svn to git forgot that the source tree was made of > multiple tarballs (one for jedi, one for jedi-vim) and now the vim > plugin package cannot be produced because of the missing sources [1]. > > [1] > https://anonscm.debian.org/cgit/python-modules/packages/python-jedi.git/tree/ > > > How I should proceed now? > > We could just drop the vim plugin package for now (it does not work > anyway due to #841043), and consider introducing a new source package > for it later. Afterall, they are separate projects on GitHub [2, 3]. > > Otherwise, I guess the svn migration would have to be re-run? I have no > idea how to do it, nor setting up git-dpm to use multiple tarballs. > > [2] https://github.com/davidhalter/jedi > [3] https://github.com/davidhalter/jedi-vim > > > Cheers, > Ghis