Re: updating packages

[Brian May]

Christopher Hoskin  writes:

> As sphinx is used for documentation, even if you're building a python2
> package, you can use the python3 sphinx. Build-depends on
> python3-sphinx and Build-Conflicts on python-sphinx.

Yes, was wondering that.

> I was going to look at updating vine, kombu and python-ampq this
> weekend, but the upstream tarballs have been signed by a different key
> pair than the one advertised at:

:-(

Please keep me up-to-date on developments.

Thanks!
-- 
Brian May 

Re: packaging problems with python3.5 and python 3.6

[Norbert Preining]

Hi Steve,

thanks for your answer, very much appreciated.

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

Indeed, but I was choosing between "applications" and "libraries" and
the later one sounded more appropriate.

> 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.

No, my fault, it is python*3*-lxml. Thanks.

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

Ok, thanks a lot.

All the best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Re: packaging problems with python3.5 and python 3.6

[Norbert Preining]

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.

> 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.

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

All the best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13