Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!feeds.phibee-telecom.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Fioddor Superconcentrado <fioddor@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: python3- preffix
Date: Sun, 04 Oct 2020 18:30:01 +0200
Message-ID: <AWf3z-8tw-3@gated-at.bofh.it>
References: <AWehb-7RT-9@gated-at.bofh.it> <AWeqR-7W6-5@gated-at.bofh.it>
Old-Return-Path: <fioddor@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0000000000008c7cd805b0dacd73"
Approved: robomod@news.nic.it
Lines: 78
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12922

--0000000000008c7cd805b0dacd73
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you Andrey.

In this case it's a module and therefore needs the prefix.
Ok. renamed the source package with python-.

I get following (translated back to english):
dpkg-buildpackage: information: system architecture amd64
dpkg-source:  failure: source package has 2 conflicting values:
"python-my-package" and "python3-my-package"
dpkg-buildpackage: failure: dpkg-source --before-build . subprocess
returned exit status 25


El dom., 4 oct. 2020 a las 17:46, Andrey Rahmatullin (<wrar@debian.org>)
escribi=C3=B3:

> On Sun, Oct 04, 2020 at 05:39:16PM +0200, Fioddor Superconcentrado wrote:
> > Debian's packaging documentation requires the packages containing pytho=
n3
> > apps to be renamed with a python3 suffix.
> *apps* shouldn't have a prefix, only modules should.
>
> > Now I can put that prefix to the source too or not.
> No. The current best practices for source package names for Python module
> packages are either just foo or python-foo and this wasn't changed when
> dropping py2.
>
> > if I don't I get a conflict warning.
> What do you mean?
>
>
> --
> WBR, wRAR
>

--0000000000008c7cd805b0dacd73
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thank you Andrey.</div><div><br></div><div>In this ca=
se it&#39;s a module and therefore needs the prefix.</div><div>Ok. renamed =
the source package with python-.</div><div><br></div><div>I get following (=
translated back to english):</div><div>dpkg-buildpackage: information: syst=
em architecture amd64<br></div><div>dpkg-source:=C2=A0 failure: source pack=
age has 2 conflicting values: &quot;python-my-package&quot; and &quot;pytho=
n3-my-package&quot;</div><div>dpkg-buildpackage: failure: dpkg-source --bef=
ore-build . subprocess returned exit status 25<br></div><div><br></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">El d=
om., 4 oct. 2020 a las 17:46, Andrey Rahmatullin (&lt;<a href=3D"mailto:wra=
r@debian.org">wrar@debian.org</a>&gt;) escribi=C3=B3:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">On Sun, Oct 04, 2020 at 05:39:16PM +0=
200, Fioddor Superconcentrado wrote:<br>
&gt; Debian&#39;s packaging documentation requires the packages containing =
python3<br>
&gt; apps to be renamed with a python3 suffix. <br>
*apps* shouldn&#39;t have a prefix, only modules should.<br>
<br>
&gt; Now I can put that prefix to the source too or not.<br>
No. The current best practices for source package names for Python module<b=
r>
packages are either just foo or python-foo and this wasn&#39;t changed when=
<br>
dropping py2.<br>
<br>
&gt; if I don&#39;t I get a conflict warning.<br>
What do you mean?<br>
<br>
<br>
-- <br>
WBR, wRAR<br>
</blockquote></div>

--0000000000008c7cd805b0dacd73--