Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #9179
| From | Ghislain Vaillant <ghisvail@gmail.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Team upload for python-jedi |
| Date | 2017-01-19 19:20 +0100 |
| Message-ID | <t1ptx-4XW-39@gated-at.bofh.it> (permalink) |
| References | <rSB35-3r2-43@gated-at.bofh.it> <t0XGW-469-3@gated-at.bofh.it> <t0XGW-469-1@gated-at.bofh.it> <t12Qj-7py-31@gated-at.bofh.it> <t1p0u-4y6-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 2017-01-19 at 20:45 +0300, Dmitry Shachnev wrote: > Hi Ghislain, > > On Wed, Jan 18, 2017 at 05:53:05PM +0000, Ghislain Vaillant wrote: > > 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]. > > > > 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. > > The SVN to Git migration was done automatically. I think the script was > just not too smart to deal with multiple tarballs properly. Ok. > For now you can just forget about git-dpm, get the sources manually and > copy the Debian directory from Git on top of them. Just to be sure, do you mean I should leave the repository alone and merge my work in a fresh import-dsc of the current package? > Now it is too late to fix the DPMT migration script, but it may be not > too late to make sure the problem does not appear with PAPT. Possibly. Ghis
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Team upload for python-jedi Piotr Ożarowski <piotr@debian.org> - 2017-01-18 13:40 +0100
Re: Team upload for python-jedi Ghislain Vaillant <ghisvail@gmail.com> - 2017-01-18 19:10 +0100
Re: Team upload for python-jedi Ghislain Vaillant <ghisvail@gmail.com> - 2017-01-19 13:20 +0100
Re: Team upload for python-jedi Dmitry Shachnev <mitya57@debian.org> - 2017-01-19 18:50 +0100
Re: Team upload for python-jedi Ghislain Vaillant <ghisvail@gmail.com> - 2017-01-19 19:20 +0100
Re: Team upload for python-jedi Dmitry Shachnev <mitya57@debian.org> - 2017-01-22 13:10 +0100
Team maintained packages and git-dpm (was Re: Team upload for python-jedi) Barry Warsaw <barry@debian.org> - 2017-01-22 23:10 +0100
Re: Team maintained packages and git-dpm (was Re: Team upload for python-jedi) Brian May <bam@debian.org> - 2017-01-23 00:20 +0100
Re: Team maintained packages and git-dpm (was Re: Team upload for python-jedi) Nikolaus Rath <Nikolaus@rath.org> - 2017-01-23 02:20 +0100
Re: Team maintained packages and git-dpm (was Re: Team upload for python-jedi) Nikolaus Rath <Nikolaus@rath.org> - 2017-01-23 02:20 +0100
Re: Team maintained packages and git-dpm (was Re: Team upload for python-jedi) Scott Kitterman <debian@kitterman.com> - 2017-01-23 03:50 +0100
Re: Team maintained packages and git-dpm (was Re: Team upload for python-jedi) Barry Warsaw <barry@debian.org> - 2017-01-23 16:50 +0100
Re: Team upload for python-jedi Piotr Ożarowski <piotr@debian.org> - 2017-01-19 21:10 +0100
Re: Team upload for python-jedi Ghislain Vaillant <ghisvail@gmail.com> - 2017-01-21 13:20 +0100
csiph-web