Hello Gianfranco,
>
> a ping when the other package is renamed and in testing even better.
>
I'm finally making effective the ping, as the long-standing naming
conflict has been solved on the latest "jellyfish" version (2.2.6-1) [1]
(which entered testing on 2016-09-06) by the renaming of its
control: block -1 by 819016
Hello Giafranco,
> FWIW adding "u" to the strings indeed fixed the issue
> e.g. 'string' becomes u'string' (IIRC forcing unicode)
thanks, it's been confirmed by upstream and promptly fixed on the
upstream repository [1].
> BTW, the Python policy is something like
>
control: tags -1 moreinfo
Hi
>I'm quite certain that it is indeed a problem with the README (the
>library was initially only available on Python 2, and the README.rst has
>not gone through significant changes since then, even if Python 3
>support was introduced around 0.3.2). I'll follow up on
Thanks Paul and Gianfranco for your clarification in regards to the
style patches, I was confused by the mention of the check-all-things
commands on your initial reply and I appreciate your explanation!
> Just a question:
> the code in README file, works for python3 but not for python.
> However
On Thu, Apr 7, 2016 at 1:57 AM, Diego M. Rodriguez wrote:
> On my earlier attempts (<=0.5.1-1) I did include some patches that were
> aimed towards fixing pep8/flake8 warnings, although I dropped them on
> the 0.5.3 package. The reason was that upstream has expressed his
> willingness to ignore
Thanks for the review, Gianfranco. I have just uploaded a new version of
the package to mentors [1] that fixes some of the issues, although I'd
appreciate some further clarification or guidance on a few others:
> $ codespell --quiet-level=3
>
> $ pyflakes .
>
> $ pyflakes3 .
>
> $ pep8
control: owner -1 !
control: tags -1 moreinfo
Hi, lets review
check-all-the-things:
$ codespell --quiet-level=3
$ pyflakes .
$ pyflakes3 .
$ pep8 --ignore W191 .
one license seems missing
./.run_with_env.cmd::: License: CC0 1.0 Universal:
http://creativecommons.org/publicdomain/zero/1.0/
Thanks a lot for the feedback and help, Víctor!
> # d/patch
>
> Please upstream them (in case they aren't already in 0.5.2).
> ...
> # lintian
>
> there's a spelling error in manpage: accomodate accommodate (upstream
> the fix).
I have forwarded both those issues upstream [1], which combined
About gbp.conf, we at #debian-mentors have realized that if you want to
comply with DPMT's Policy, then you will need to set up the `upstream`
branch by importing only the tar.gzs, without upstream's commit history
on it.
That makes gbp.conf superfluous and also there's no need to think about
I can't sponsor you (I'm just a contributor) but since I packaged
python-jellyfish on my own as I didn't see your ITP first, let me
chime in to be of some help.
# d/watch
It is correct, but from the contents of the orig.tar.gz I see you
have used the one from Github (that contains the docs/ etc)
Hello Nicholas,
> I believe the package also needs Build-Depends on libpython-all-dev and
> libpython3-all-dev, or the C extensions fail (nonfatally) to compile in a
> clean
> chroot environment.
thanks for the hint - the Build-Depends are indeed needed for successfully
building the C
Hey all,
I'm willing to sponsor this package and any related packages.
Paul
On Mon, Dec 28, 2015 at 1:29 PM, Diego M. Rodriguez
wrote:
> Hello Nicholas,
>
> > I believe the package also needs Build-Depends on libpython-all-dev and
> > libpython3-all-dev, or the C
On Tue, Dec 08, 2015 at 09:44:01PM +0100, Diego M. Rodriguez wrote:
> I am looking for a sponsor for my package "python-jellyfish"
>
> * Package name: python-jellyfish
> Version : 0.5.1-1
> Upstream Author : James Turk
> * URL :
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "python-jellyfish"
* Package name: python-jellyfish
Version : 0.5.1-1
Upstream Author : James Turk
* URL :
14 matches
Mail list logo