Re: python-bz2file packaged; python-screed + khmer updated
On Thu, May 28, 2015 at 05:13:38PM +0000, Michael Crusoe wrote:
> > I removed the empty upstream/metadata template but noticed there are
> > some more templates that could be removed (createmanpages,
> > get-orig-source, inject-into-alioth-git). Also the d/watch file
> > needs to be adapted.
>
> Done. I found the pypi.debian.net service which generates a watch file for
> PyPI hosted projects: http://pypi.debian.net/bz2file/watch
Yep, this definitely helps. However, now there is the following lintian
error:
E: python-bz2file source: debian-watch-file-pubkey-file-is-missing
N:
N: This watch file verifies a cryptographic signature but the upstream
N: public key is missing.
N:
N: Please add upstream public keys in either
N: debian/upstream/signing-key.asc or debian/upstream/signing-key.pgp.
N:
N: Refer to the uscan(1) manual page for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: watch-file, Type: source
N:
gbp:error: '~/bin/git-pbuilder' failed: it exited with 1
(I pushed the upload to unstable commit a bit too early but I think
I can leave this until you either found a signing key or the phrase
is dropped from d/watch.)
> > I see an issue that pure python2 packages will not pass new queue if I
> > understood things correctly - but I see no reason why it should not work
> > with python3 (did I missed something?) At least it was easy to create
> > the python3 package - please thoroughly check my commit.
>
> Thanks, I'm in a Py2 mode at the moment and forgot.
Me too. I was just forced to realise when packages were refused from
new -> unstable migration just because of beeing Python2 only.
> > > python-screed
> >
> > Since it depends from python-bz2file (and python3-screed should depend
> > from python3-bz2file accordingly) we can wait with this until
> > python-bz2file is accepted, right?
>
> Right. This version of python-screed is not Python 3 compatible. The next
> release will be a Python 3 release and I will update the packaging
> accordingly.
Sounds good.
> > > khmer
> >
> > khmer(master) $ grep python.*3 *.py
> > versioneer.py:* Compatible With: python2.6, 2.7, 3.2, 3.3, 3.4, and pypy
> >
> > So please also provide a python3 package - if it is a user application
> > only than stick to python3 exclusively.
> >
>
> Likewise the next release of khmer will be Python 3 based.
Sounds good as well.
> > Thanks for your work on this and please note that my responses will be
> > (drastically) delayed for the next three weeks
>
> I really appreciate the review. Thanks!
Just let me know once you dealt with the signing key issue.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: