How to properly use dh_python3 as lintian suggests to move files from usr/lib/python3.7 to usr/lib/python3

[Andreas Tille]

Hi,

for the new version of python-pyvcf[1] I get

W: python3-pyvcf: python-module-in-wrong-location 
usr/lib/python3.7/dist-packages/vcf/ usr/lib/python3/dist-packages/vcf/
W: python3-pyvcf: python-module-in-wrong-location 
usr/lib/python3.7/dist-packages/vcf/parser.py 
usr/lib/python3/dist-packages/vcf/parser.py


I'm curious what to do to fix this.

Kind regards

 Andreas.


[1] https://salsa.debian.org/med-team/python-pyvcf

-- 
http://fam-tille.de

Re: Is there a tool to debianize for the first time a package from pypi

[Adrian Vondendriesch]

Hi Frederic,

Am Freitag, den 03.08.2018, 13:28 + schrieb PICCA Frederic-
Emmanuel:
> Hello, I need to create a new package for 
> 
> spyder_kernels.
> 
> Is there a tool which allows to create the first version of a package
> which create the debian/directory from the setup.py files ?

There is stdeb [1]. I've used it in the past to create the initial
debian/ files. However, most of the generated files needs to be
adjusted manually.

[1]: https://pypi.org/project/stdeb/

Cheers,
 - Adrian

RE:Is there a tool to debianize for the first time a package from pypi

[PICCA Frederic-Emmanuel]

no problem Ghislain, I am on it :))

Cheers

Fred

Re: Is there a tool to debianize for the first time a package from pypi

[Sandro Tosi]

https://packages.debian.org/unstable/pypi2deb
On Fri, Aug 3, 2018 at 9:45 AM PICCA Frederic-Emmanuel
 wrote:
>
> Hello, I need to create a new package for
>
> spyder_kernels.
>
> Is there a tool which allows to create the first version of a package which 
> create the debian/directory from the setup.py files ?
>
> thanks
>
> Frederic



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Re: Is there a tool to debianize for the first time a package from pypi

[Ghislain Vaillant]

Hi Fred,

You can probably use one of the packaging for one of the Spyder plugins as
the basis for src:spyder-kernels.

Otherwise, I can do it if you prefer?

Le ven. 3 août 2018 à 14:45, PICCA Frederic-Emmanuel <
frederic-emmanuel.pi...@synchrotron-soleil.fr> a écrit :

> Hello, I need to create a new package for
>
> spyder_kernels.
>
> Is there a tool which allows to create the first version of a package
> which create the debian/directory from the setup.py files ?
>
> thanks
>
> Frederic
>

Is there a tool to debianize for the first time a package from pypi

[PICCA Frederic-Emmanuel]

Hello, I need to create a new package for 

spyder_kernels.

Is there a tool which allows to create the first version of a package which 
create the debian/directory from the setup.py files ?

thanks

Frederic

Re: git-dpm -> gbp conversion (mass-change)

[Sandro Tosi]

> 1. convert git-dpm -> gbp

thanks for doing this!

> 2. change default branch to debian/master

please dont. a quick check to the perl team and it seems they dont
require it, so should we? if someone wants to follow DEP-14 then just
do so and document it on debian/README.source (and repoint HEAD),
leaving many of the (very!) simple packages away from an unnecessary
complication?

thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Re: git-dpm -> gbp conversion (mass-change)

[W. Martin Borgert]

On 2018-08-03 10:08, W. Martin Borgert wrote:
> On 2018-08-03 08:04, Simon McVittie wrote:
> > There is no upstream/master, upstream/unstable, upstream/stretch or
> > similar in DEP-14, because:
> 
> I did not suggest mingling upstream branches with Debian
> versions, which seems to be your impression. I just (maybe
> wrongly) thought, that upstream/master whatever upstream does in
^ follows
> their master/tip/trunk (just as upstream/latest always follows
> the latest upstream release). I don't remember, where I got that
> idea from. Unreliable sources :~)

Re: git-dpm -> gbp conversion (mass-change)

[W. Martin Borgert]

On 2018-08-03 08:04, Simon McVittie wrote:
> There is no upstream/master, upstream/unstable, upstream/stretch or
> similar in DEP-14, because:

I did not suggest mingling upstream branches with Debian
versions, which seems to be your impression. I just (maybe
wrongly) thought, that upstream/master whatever upstream does in
their master/tip/trunk (just as upstream/latest always follows
the latest upstream release). I don't remember, where I got that
idea from. Unreliable sources :~)

Re: git-dpm -> gbp conversion (mass-change)

[Simon McVittie]

On Fri, 03 Aug 2018 at 08:21:28 +0200, W. Martin Borgert wrote:
> In fact, I thought that "upstream/master" were DEP-14-ish, but
> only "upstream/latest" (for the newest release) is.

Yes. The simple case for DEP-14 is that you are only following one
upstream branch, which is upstream/latest; the more complex case
is that you are also following an upstream stable-branch or something,
for which naming like upstream/1.2.x is suggested for the older (stable)
branch.

dbus  and glib2.0
 are examples
of DEP-14 packages that track more than one upstream branch.

There is no upstream/master, upstream/unstable, upstream/stretch or
similar in DEP-14, because:

* if uploads to a particular Debian suite are tracking upstream versions
  older than the latest, they presumably meet some sort of criteria
  for which versions are acceptable, most commonly "is from the same
  stable-branch as the previous release"; the branch is named after
  those criteria rather than the target suite, because multiple suites
  might be sharing an upstream release series

* if there is no upstream version that is acceptable for e.g. stable,
  then new upstream versions won't get imported for that suite, so
  there's no need to maintain a branch that they could be imported into
  (if using pristine-tar, it uses commits, not branches, to check out
  upstream source)

smcv