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


Groups > linux.debian.maint.python > #12058

Re: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub')

From Simon McVittie <smcv@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub')
Date 2019-11-28 18:30 +0100
Message-ID <z7vM5-5m7-13@gated-at.bofh.it> (permalink)
References <z7tAB-44m-1@gated-at.bofh.it> <z7u3E-4eC-5@gated-at.bofh.it> <z7uGl-4Ii-1@gated-at.bofh.it> <z7uGl-4Ii-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, 28 Nov 2019 at 11:15:31 -0500, Sandro Tosi wrote:
> if you install `pubsub` as top-level module, your package must be
> named pythonN-pubsub, if not it violates the policy and it's RC buggy.

That's what I had thought, but I've also seen people asserting that the
Debian package name ought to reflect the egg name in cases where it
differs from the top-level Python module name.

Some examples of where the difference between egg name and module name
matters:

- this one:
  - module: pubsub (-> python3-pubsub)
  - egg: pypubsub-*.egg-info (-> python3-pypubsub)
  - is actually python3-pypubsub (named for the egg)

- src:dbus-python:
  - module: dbus (-> python3-dbus)
  - egg: dbus_python-1.2.14.egg-info (-> python3-dbus-python)
  - is actually python3-dbus (named for the module)

- src:pygobject:
  - module: gi (-> python3-gi) and pygtkcompat
  - egg: PyGObject-3.34.0.egg-info (-> python3-pygobject)
  - is actually python3-gi (named for the module)

(Maybe python3-gi should also have Provides: python3-pygtkcompat?)

Is there consensus that the top-level module name is what matters, and not
following the recommendation is a bug?
https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html
says "The binary package for module foo should preferably be named
python3-foo, if the module name allows" and "import foo should import
the module", which suggests that it is indeed the name of the top-level
importable module, and not the name of the egg, that matters (which would
imply that -dbus and -gi are correct, and -pypubsub is not).

Is there consensus that not following this recommendation is a *RC* bug?
The bits I quoted above say "should" rather than "must".

Thanks,
    smcv

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

autopkgtest-pkg-python fails if package name is python-pyMODULENAME  (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named  'pypubsub') Andreas Tille <andreas@an3as.eu> - 2019-11-28 16:10 +0100
  Re: autopkgtest-pkg-python fails if package name is  python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure:  No module named 'pypubsub') Ondrej Novy <novy@ondrej.org> - 2019-11-28 16:40 +0100
    Bug#945768: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub') Andreas Tille <andreas@an3as.eu> - 2019-11-28 17:20 +0100
      Bug#945768: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub') Sandro Tosi <morph@debian.org> - 2019-11-28 17:20 +0100
        Re: autopkgtest-pkg-python fails if package name is  python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure:  No module named 'pypubsub') Andreas Tille <andreas@an3as.eu> - 2019-11-28 18:30 +0100
        Re: autopkgtest-pkg-python fails if package name is  python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure:  No module named 'pypubsub') Simon McVittie <smcv@debian.org> - 2019-11-28 18:30 +0100
          Re: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub') Scott Kitterman <debian@kitterman.com> - 2019-11-28 21:50 +0100
          Re: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub') "Yao Wei (魏銘廷)" <mwei@debian.org> - 2019-11-29 01:40 +0100
            Re: autopkgtest-pkg-python fails if package name is  python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure:  No module named 'pypubsub') Simon McVittie <smcv@debian.org> - 2019-11-29 09:30 +0100
              Re: autopkgtest-pkg-python fails if package name is  python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure:  No module named 'pypubsub') Simon McVittie <smcv@debian.org> - 2019-11-29 11:50 +0100
                Re: autopkgtest-pkg-python fails if package name is  python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure:  No module named 'pypubsub') Andreas Tille <andreas@an3as.eu> - 2019-11-29 12:10 +0100
                Lintian warning for this issue (Was: autopkgtest-pkg-python fails if  package name is python-pyMODULENAME) Andreas Tille <andreas@an3as.eu> - 2019-12-04 14:50 +0100
      Bug#945768: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub') Ondrej Novy <novy@ondrej.org> - 2019-11-28 19:00 +0100

csiph-web