Re: pbs python
On 31 March 2014 18:54, Jelmer Vernooij wrote: > Note that Brian is also a DD and maintainer of various packages. He should > be > aware of the process. :) > http://qa.debian.org/developer.php?login=bam Need to think about it if is worth while for Debian as a whole. I am starting to get an accumulation of Packages that in my private repository, some of these perhaps should get pushed to Debian. http://code.vpac.org/debian/dists/sid/main/binary-amd64/Packages Generally, there are three categories: * Packages that are not in Debian, but I need. * Packages that are too old (and in some cases completely broken) in Debian (e.g. django-celery). * Packages that are buggy in Debian, and are unusable without patching (e.g. django-south). Getting back on track, I have an old version of pbs_python (using the non-debian complaint name used by upstream debian/control file), , however was looking at the latest version. It isn't a high priority. In fact, I am not even sure how to test it. I have inherited django-pbs, which requires it. http://code.vpac.org/debian/pool/main/p/pbs-python/ Unfortunately, pbs_python seems to be rather ... creative ... in its packaging techniques. eg. autoconf builds Makefile and setup.py from Makefile.in and setup.py.in, and the Makefile calls setup.py. My initial attempts at creating a Debian package result in errors from the Makefile (looks like it is trying to install the LICENSE.openpbs file in /). My limited understanding is that python packages are suppose to be distributed with a setup.py, not a setup.py.in. -- Brian May
Re: pbs python
On 31 March 2014 20:03, Piotr Ożarowski wrote:
> > (I think this might have been renamed recently to python-sh, but can't
> find
> > the reference right now)
>
Here is the reference:
https://pypi.python.org/pypi/pbs/0.110
Maybe we should be removing the existing python-pbs from Debian? It looks
like it isn't supported any more...
it shouldn't be a problem (""pbs" != "bps")
>
Oops. No wonder I couldn't find the above page :-)
--
Brian May
Re: recommended numpy dependency ranges?
> > I'm pretty sure a recompile will fix it, the question I have is how often
> > does numpy break binary compatibility?
> >
> > Should set your numpy dependencies to something like:
> >
> > python-numpy (>= 1.8, < 1.9)
>
> do not "hard code" -- add calls to dh_numpy (dh_numpy3) to your
> rules and make sure you have ${python:Depends} in your Depends
I didn't know about dh_numpy, is there a recommended dh target to use?
Its use doesn't seem that consistent in codesearch.d.o.
Diane
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2707048.BARnNtrk0i@myrada
Re: recommended numpy dependency ranges?
On 31.03.2014 17:08, Diane Trout wrote: > Hi, > > I have a small package the depends on numpy and it recently stopped working. > >> Traceback (most recent call last): >> File "/usr/local/lib/R/site- > library/DEXSeq/python_scripts/dexseq_prepare_annotation.py", >> line 33, in >> import HTSeq >> File "/usr/lib/python2.7/dist-packages/HTSeq/__init__.py", line 9, >> in >> from _HTSeq import * >> File "numpy.pxd", line 155, in init HTSeq._HTSeq (src/_HTSeq.c:33074) >> ValueError: numpy.dtype has the wrong size, try recompiling > > > I'm pretty sure a recompile will fix it, the question I have is how often > does > numpy break binary compatibility? > > Should set your numpy dependencies to something like: > > python-numpy (>= 1.8, < 1.9) > numpy doesn't break compatibility often on purpose, the goal is never as its a major pain for windows users. The last accidental break was in 1.6 which we solved by just recompiling the rdepends. Are you sure you are not picking up something from /usr/local? import HTSeq works for me in unstable. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5339af51.9070...@googlemail.com
Re: recommended numpy dependency ranges?
On Mon, 31 Mar 2014, Diane Trout wrote:
> Hi,
> I have a small package the depends on numpy and it recently stopped working.
> > Traceback (most recent call last):
> > File "/usr/local/lib/R/site-
> library/DEXSeq/python_scripts/dexseq_prepare_annotation.py",
> > line 33, in
> > import HTSeq
> > File "/usr/lib/python2.7/dist-packages/HTSeq/__init__.py", line 9,
> > in
> > from _HTSeq import *
> > File "numpy.pxd", line 155, in init HTSeq._HTSeq (src/_HTSeq.c:33074)
> > ValueError: numpy.dtype has the wrong size, try recompiling
> I'm pretty sure a recompile will fix it, the question I have is how often
> does
> numpy break binary compatibility?
> Should set your numpy dependencies to something like:
> python-numpy (>= 1.8, < 1.9)
do not "hard code" -- add calls to dh_numpy (dh_numpy3) to your
rules and make sure you have ${python:Depends} in your Depends
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate, Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140331153746.gi8...@onerussian.com
recommended numpy dependency ranges?
Hi, I have a small package the depends on numpy and it recently stopped working. > Traceback (most recent call last): > File "/usr/local/lib/R/site- library/DEXSeq/python_scripts/dexseq_prepare_annotation.py", > line 33, in > import HTSeq > File "/usr/lib/python2.7/dist-packages/HTSeq/__init__.py", line 9, > in > from _HTSeq import * > File "numpy.pxd", line 155, in init HTSeq._HTSeq (src/_HTSeq.c:33074) > ValueError: numpy.dtype has the wrong size, try recompiling I'm pretty sure a recompile will fix it, the question I have is how often does numpy break binary compatibility? Should set your numpy dependencies to something like: python-numpy (>= 1.8, < 1.9) Diane -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1427058.q2LImEDRuv@myrada
Re: pbs python
[Brian May, 2014-03-31]
> *If* I wanted to get the following package into Debian:
>
> https://oss.trac.surfsara.nl/pbs_python
>
> What should I do?
>
> It seems to clash with a package of the same name (when labelled according
> to policy anyway) that is very different:
>
> https://packages.debian.org/sid/python-pbs
>
> (I think this might have been renamed recently to python-sh, but can't find
> the reference right now)
no matter what name you'll choose for the binary package (python-pbs
is the best choice, but since it's already taken, I'd use
python-pbs-something)...
one of these libraries has to be renamed if you want both in Debian
(current python-pbs provides pbs.py so there will be a file conflict)
> If that is not bad enough, looks like there is another python-bps too:
>
> https://gitorious.org/python-blip
> https://pypi.python.org/pypi/python-bps
it shouldn't be a problem (""pbs" != "bps")
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140331090302.gk30...@sts0.p1otr.com
Re: pbs python
On Mon, Mar 31, 2014 at 04:20:42PM +1100, Ben Finney wrote: > Brian May writes: > > > Hello, > > > > *If* I wanted to get the following package into Debian: > > https://oss.trac.surfsara.nl/pbs_python > > > > What should I do? > > First step: submit a Request For Package bug report against the special > “wnpp” package https://www.debian.org/devel/wnpp/>. It is highly > recommended to di this with the ‘reportbug’ tool:: > > $ reportbug --mua mutt --severity wishlist wnpp > > because it will prompt you for what kind of WNPP bug report this is > (answer: RFP), and then present a template for you to provide > information about the prospective package. Note that Brian is also a DD and maintainer of various packages. He should be aware of the process. :) http://qa.debian.org/developer.php?login=bam > > It seems to clash with a package of the same name > There are means of dealing with this: using a more specific name for the > source package, renaming the resulting binary package and library, etc. > > But this is best done after submitting the RFP bug report and finding an > interested Debian maintainer for the package. Even if the source and binary packages were renamed, this would result in packages that are unrelated and can not be installed together (what would "import pbs" do?) Ideally, one or more of the upstreams should be renamed. Have you checked if they are open to this? Cheers, Jelmer signature.asc Description: Digital signature
