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


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

Re: packaging problems with python3.5 and python 3.6

From Steve Langasek <vorlon@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: packaging problems with python3.5 and python 3.6
Date 2017-07-30 08:50 +0200
Message-ID <u8Qd4-5f8-7@gated-at.bofh.it> (permalink)
References <u8JXX-1cI-1@gated-at.bofh.it> <u8PgZ-4D5-1@gated-at.bofh.it> <u8Q3o-5a6-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

On Sun, Jul 30, 2017 at 03:16:06PM +0900, Norbert Preining wrote:
> Hi Steve,

> Thanks for your answer and your fix!

> > Which "python packaging guide" do you refer to?  A search for "debian python
> > packaging guide" does not return unambiguous results.

> https://wiki.debian.org/Python/LibraryStyleGuide where it states:
> 	You'll want to have at least the following build dependencies: 
> 	...
> 	python3-all
> but the
> 	python[,3]-all-dev
> are never mentioned. So sorry, I didn't know about them and searched
> for the required header files, and added the respective packages.

> > 'python-all-dev, python3-all-dev' - plus the python2 and python3 versions of

> Thanks, maybe one with proper knowledge should fix the wiki, though.

Ok, that was the first hit I got but I discounted it because it spoke of
packaging "libraries", not modules or extensions.

Perhaps someone should make this wiki page a redirect to the python policy
manual?  https://www.debian.org/doc/packaging-manuals/python-policy/

> > Since this package is in collab-maint, I've gone ahead and pushed fixed
> > python3 support to the repo.

> Thanks again. You added a dependency on python-lxml. I don't think this
> is necessary as libxml is only used at compile time. At least building
> in a clean chroot did work out without any problems.

I added python3-lxml because without it, build-time tests failed for
python3.  If I also added python-lxml, that was purely a cut'n'paste error.

> BTW, does it make sense to upload another -1 version to ftp-master
> to replace the one in the NEW queue?

AFAIK you would need to get the ftpmasters to reject the existing -1 first.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

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


Thread

packaging problems with python3.5 and python 3.6 Norbert Preining <norbert@preining.info> - 2017-07-30 02:10 +0200
  Re: packaging problems with python3.5 and python 3.6 Steve Langasek <vorlon@debian.org> - 2017-07-30 07:50 +0200
    Re: packaging problems with python3.5 and python 3.6 Norbert Preining <norbert@preining.info> - 2017-07-30 08:40 +0200
      Re: packaging problems with python3.5 and python 3.6 Steve Langasek <vorlon@debian.org> - 2017-07-30 08:50 +0200
        Re: packaging problems with python3.5 and python 3.6 Norbert Preining <norbert@preining.info> - 2017-07-30 09:20 +0200
        Re: packaging problems with python3.5 and python 3.6 barry@debian.org - 2017-08-02 18:20 +0200
          Re: packaging problems with python3.5 and python 3.6 Steve Langasek <vorlon@debian.org> - 2017-08-02 21:40 +0200
            Re: packaging problems with python3.5 and python 3.6 barry@debian.org - 2017-08-03 15:10 +0200

csiph-web