Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #12915 > unrolled thread

python3- preffix

Back to article view | Back to linux.debian.maint.python

Contents

  python3- preffix Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-04 17:40 +0200
    Re: python3- preffix Andrey Rahmatullin <wrar@debian.org> - 2020-10-04 17:50 +0200
      Re: python3- preffix Dmitry Shachnev <mitya57@debian.org> - 2020-10-04 18:30 +0200
      Re: python3- preffix Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-04 18:30 +0200
    Re: python3- preffix Geert Stappers <stappers@stappers.nl> - 2020-10-04 18:00 +0200

#12915 — python3- preffix

[Multipart message — attachments visible in raw view] — view raw

Hi again.

Debian's packaging documentation requires the packages containing python3
apps to be renamed with a python3 suffix. I do so in debian/control file.
Now I can put that prefix to the source too or not. If I do so then I get a
lintian warning source-package-encodes-python-version but if I don't I get
a conflict warning.

I've renamed the downloaded tarball with the prefix because the build
toolchain expected it. But I left the extracted directory's name untouched.

What's the canonical way?

Thanks in advanced.

[toc] | [next] | [standalone]

#12916

[Multipart message — attachments visible in raw view] — view raw

On Sun, Oct 04, 2020 at 05:39:16PM +0200, Fioddor Superconcentrado wrote:
> Debian's packaging documentation requires the packages containing python3
> 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

[toc] | [prev] | [next] | [standalone]

#12921

[Multipart message — attachments visible in raw view] — view raw

Hi Fioddor!

On Sun, Oct 04, 2020 at 06:24:30PM +0200, Fioddor Superconcentrado wrote:
> 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"

You need to change both debian/control and debian/changelog.

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#12922

[Multipart message — attachments visible in raw view] — view raw

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ó:

> On Sun, Oct 04, 2020 at 05:39:16PM +0200, Fioddor Superconcentrado wrote:
> > Debian's packaging documentation requires the packages containing python3
> > 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
>

[toc] | [prev] | [next] | [standalone]

#12920

On Sun, Oct 04, 2020 at 05:39:16PM +0200, Fioddor Superconcentrado wrote:
> Hi again.
> 
> Debian's packaging documentation requires the packages containing python3
> apps to be renamed with a python3 suffix. I do so in debian/control file.
> Now I can put that prefix to the source too or not. If I do so then I get a
> lintian warning source-package-encodes-python-version but if I don't I get
> a conflict warning.
> 
> I've renamed the downloaded tarball with the prefix because the build
> toolchain expected it. But I left the extracted directory's name untouched.
> 
> What's the canonical way?

Same way as we have learnt walking.

 
> Thanks in advanced.

Yes, also beginners can run out of credit.


Regards
Geert Stappers
-- 
Silence is hard to parse

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web