Hi,
I try to convert gnumed-client to the new Python policy using
python-support. You can have a look at my current packaging at
http://people.debian.org/~tille/packages/gnumed/
In prinzipe the wrapper script /usr/bin/gnumed does the following
python /var/lib/python-support/python2.3/Gnum
On Wed, 9 Aug 2006, Josselin Mouette wrote:
As Gnumed doesn't ship a .pth file, the .path doesn't need to be
updated.
Well, I did so in 0.1 packages but was unsure whether this might be
useful with new Python policy. Would you advise me to continue using
Gnumed.pth that contained
Gnumed
Gn
On Thu, 10 Aug 2006, Josselin Mouette wrote:
Anyway, it is not recommended to put scripts designed to be executed
(like this one) in the python module directories. Now there's just
another good reason not to do so.
My idea was that I've thought a precompiled Python file just makes sense
and be
On Tue, 5 Feb 2008, Piotr O?arowski wrote:
no need to upload it anywhere anymore, just inject it into the repo
(please remember about svn-inject's "-o" option [1]) and ping me.
Well, there are two options for using a SVN reporitory: debian-python
and debian-med. As you can read in the thread s
On Thu, 28 May 2008, Yaroslav Halchenko wrote:
Within your project we are going to make use of OpenOpt project
http://scipy.org/scipy/scikits/wiki/OpenOpt
which as you see is a part of scikits.
Just added the project to Debian Science tasks files and rerendered
the web sentinel page
http://
On Sat, 31 May 2008, Manuel Prinz wrote:
I have a Python application with private extension modules, so the package is
Arch: any. Because there is no way (at least I'm not aware of that) to split
the package because the modules are private, I can't seperate the large part
of the app out to /usr/
On Sun, 1 Jun 2008, Manuel Prinz wrote:
The package is pdb2pqr, you can find it here:
svn://svn.debian.org/svn/debian-med/trunk/packages/pdb2pqr/trunk/
Without having a look into this ...
The current version puts everything to /usr/lib/pdb2pqr as that seems to
please lintian. I tried to spli
Hi,
as you can read in my lightning talk at DebConf
http://people.debian.org/~tille/talks/200808_lightning/
I did some investigation on who is frequently posting
on our mailing lists. I now created graphs until
end of last year and write a short summary for
those lists I regard worth a comme
Hi,
I tried to implement the Python policy [1] using python-support to
the new GNUmed packages but failed. If I try the basic essence
of the /usr/bin/gnumed script I get:
$ python -m Gnumed.wxpython.gnumed
Traceback (most recent call last):
File "/usr/lib/python2.5/runpy.py", line 85, in run_
On Sat, 28 Mar 2009, Emilio Pozuelo Monfort wrote:
That is, you're now shipping some modules in a private location
This is what I understood as recommendation in #516037.
(usr/share is
not in PYTHONPATH), so they are not found when you try to import them.
You could ship Gnumed in /usr/share
On Sun, 29 Mar 2009, Karsten Hilbert wrote:
Well, you are trying to solve two things at once:
1) make the "python -m" calling convention work
2) move GNUmed modules to a private location
While, yes, this WAS recommended in that report I tried furiously
to argue against doing both at once becau
On Sun, 29 Mar 2009, Karsten Hilbert wrote:
-
My suggestion would be:
- call gnumed.py with the python -m ... option if that works
- this would rid us of that hardcoded path - a great thing
- leave modules where they are and GNUmed finds them by default
- if the Debian package ma
On Sun, 29 Mar 2009, Emilio Pozuelo Monfort wrote:
You're missing a 'export' before setting the variable (or call python in the
same line you set it).
Uhm - stupid me. That's a beginners fault ... :-(
In the first releases of gnumed-client package I used Gnumed.pth but
dropped this since I
On Sun, 29 Mar 2009, Emilio Pozuelo Monfort wrote:
In that case the .pyc files won't be loaded, but the .py ones, I guess (please
somebody correct me if I'm wrong). Nothing to worry about as people will usually
be using the default interpreter.
I admit I really prefered the former behaviour of
On Sat, 28 Mar 2009, Emilio Pozuelo Monfort wrote:
I got an
error that mx.DateTime can't be imported, so you probably need to depend on
python-egenix-mxdatetime).
Thanks to Emilio I was able to fix the gnumed-client package which was in fact
lacking the python-egenix-mxdatetime build dependenc
On Mon, 30 Mar 2009, Emilio Pozuelo Monfort wrote:
I think pysupport does this for you. When the default interpreter changes, it
will regenerate all the .pyc files for the new one.
This lets me relax a bit more, but hmmm, I'm not fully convinced ...
And FWIW I've just noticed that your dh_py
On Wed, Jun 24, 2009 at 11:21:45AM +0200, Fabio Tranchitella wrote:
> * 2009-06-24 11:20, Sebastien Douche wrote:
> > Is it possible to keep Python 2.4 with a warning like "we don't provide
> > support on this version" ?
>
> No, it is not possible.
... in Debian stable. What about experimental?
On Tue, Jan 12, 2010 at 07:18:03AM +0100, Sandro Tosi wrote:
>
> > 1) Upload python2.6 to unstable within the next 7 days, or
> > 2) RFA python2.6 and all relevant python packages within the next 7 days.
> ...
>
> Easy as it can be, just leave Python to Debian, and step over. I have
> no doubt th
On Tue, Jan 12, 2010 at 12:06:09AM -0800, Steve Langasek wrote:
>
> A group hijack is still a hijack. I don't know why you try to make this
> sound like some sort of noble enterprise for the good of Debian.
I never said it is a noble enterprise. I would simply call it common
sense that a group
On Tue, Jan 12, 2010 at 02:37:49AM -0800, Steve Langasek wrote:
> Really?
>
> Here are some other words that go hand-in-hand with 'package hijack':
>
> - vigilante
> - antisocial
> - arrogant
> - acrimonious
> - disrespectful
> - demotivating
Are you really sure that these attributes will
On Tue, Jan 12, 2010 at 02:59:35AM -0800, Steve Langasek wrote:
>
> As log as you leave it as the maintainer's prerogative to nack the takeover,
> then that's fine.
Sure. That's what I intended to say when I said: "... if I do not hear
from you until 7 days I assume you agree."
> > The alterna
On Tue, Jan 12, 2010 at 12:21:34PM +0100, Bastian Venthur wrote:
> The information is there, it is unfortunately just well hidden:
>
> http://lists.debian.org/debian-release/2009/12/msg00207.html
Ahh, that's a good catch. I can not tell whether the technical arguing
is correct but at least it gi
Hi,
I wanted to upgrade the package epigrass to recent upstream version and
to build against Python 2.6. Unfortunately I was running into a problem
and I'm wondering what might be the reason.
$ epigrass
Traceback (most recent call last):
File "/usr/bin/epigrass", line 5, in
from pkg_reso
Hi,
I tried to fix #616887 and commited some intermediate packaging stuff to
Vcs-Svn:
svn://svn.debian.org/svn/debian-med/trunk/packages/mgltools/bhtree/trunk/
When trying to build the package I get:
dh_python2
Traceback (most recent call last):
File "/usr/lib/python2.6/logging/__init__
Hi,
On Thu, Apr 07, 2011 at 12:53:51PM +0200, Piotr Ożarowski wrote:
> you're not building extensions for all supported Python versions (see
> previous thread on this mailing list). I will finish namespace feature
> this weekend and ask python-defaults maintainers to upload new version
> to unstab
On Thu, Apr 07, 2011 at 02:07:59PM +0200, Sandro Tosi wrote:
> > (as it can be seen in SVN). However this does not seem to be the
> > correct solution to avoid this problem. Perhaps I missed the point in
> > this advise so what exactly do I have to do to build extensions for all
> > supported Pyt
On Thu, Jun 30, 2011 at 10:08:57AM +0200, Mitar wrote:
> > btw -- we should list it among
> > http://blends.alioth.debian.org/science/tasks/machine-learning
>
> Sure. ;-)
>
> > care to join the project or commit the entry for the tasks page?
>
> I can join the project and commit the entry. Just
On Thu, Jun 30, 2011 at 10:12:50AM +0200, Mitar wrote:
> On Thu, Jun 30, 2011 at 10:08 AM, Mitar wrote:
> > No, but this is also something I will need help with. ;-)
>
> And mostly I think that I have over-complicated rules file. ;-)
Yes. :-)
Have a look into rules files that are using dh and o
On Thu, Jun 30, 2011 at 12:28:21PM +0200, Mitar wrote:
>
> I have been reading all this but I must say it does not help a
> beginner in any way.
Ahh, sorry.
> I think some best-practices examples would be
> most useful. To just copy/paste and adapt. Saying "look into rules
> files" also does not
Hi John,
On Wed, Jul 13, 2011 at 09:12:46AM -0500, John Paulett wrote:
> I am the upstream maintainer of python-hl7 [1] and have packaged it
> for Debian. I was hoping that a DD may be able to review the package
> with me and potentially sponsor the package [2]. I have worked with
> the DPMT bef
On Wed, Jul 13, 2011 at 09:43:39AM -0500, John Paulett wrote:
>
> In regards to the XML file licensing--it is currently a non-issue in
> this release, since that code as not been fully merged upstream. We
> will address any issues upstream before releasing a new version of
> python-hl7.
OK, so t
On Wed, Jul 13, 2011 at 05:02:33PM -0500, John Paulett wrote:
> I corrected debian/copyright in subversion (the parsing error on was
> caused by empty lines inside the license). I also corrected the
> License short name.
Thanks for fixing this.
> As I am packaging novice, please advise if this
Hi Laszlo,
On Fri, Aug 10, 2012 at 12:43:51PM +0200, Laszlo Kajan wrote:
> But sometimes the Debian Med group decides that packs are better off in their
> specialized teams.
That's probably a bit missleading wording. There is no such decision
making process in the Debian Med team - we adopted t
Hi,
On Wed, Nov 07, 2012 at 12:30:41PM +0100, Tomás Di Domenico wrote:
> Thank you very much for your input, Jakub and Dmitry. I'll start working
> on those changes right away. And yes, it would be very nice to try and
> get a Python3 version up. In fact, I'm quite interested in learning how
> to
Hi Tomás,
On Wed, Nov 14, 2012 at 04:42:19PM +0100, Tomás Di Domenico wrote:
> >
> > Ideally, the documentation should be rebuilt from source.
>
> Right, things get a bit blurry for me here. When upstream releases a new
> version, they take a snapshot from their repository and build the
> releas
On Wed, Nov 14, 2012 at 08:04:11PM +0100, Jakub Wilk wrote:
> I'm afraid that this creates false impression that we'd accept
> anyone, without any questions asked. This is not the case. As a DPMT
> admin I required that the applicant:
> 1) either had existing Python-related packages in the archive;
On Wed, Dec 04, 2013 at 11:59:33AM +0800, Paul Wise wrote:
>
> uscan to grow features for removing files from upstream tarballs, in a
> declarative way preferably.
That's in devscripts git and will be included in the next devscripts
version. (see [1])
> The default dh get-orig-source to invoke
Hi,
On Wed, Dec 04, 2013 at 09:12:49AM +0100, Jakub Wilk wrote:
> * Andreas Tille , 2013-12-04, 08:43:
> >>uscan to grow features for removing files from upstream
> >>tarballs, in a declarative way preferably.
> >That's in devscripts git and will be included i
On Wed, Dec 04, 2013 at 08:49:02PM +0900, Charles Plessy wrote:
> > >better solution and migrating the existing information, Andreas
> > >will complain.
> >
> > s/complain/comply/ perhaps?
>
> D'oh as well.
>
> Indeed, I meant "will not complain", sorry for the noise...
I think all readers had
On Wed, Dec 04, 2013 at 11:30:01AM +0100, Jakub Wilk wrote:
>
> AFAICS they way get_main_source_dir() is currently implemented lets
> malicious upstream to plant files in their tarball that would cause
> arbitrary code execution...
Would you mind proposing a proper fix and forward it to the accor
Hi Ben,
On Fri, Dec 06, 2013 at 09:07:01PM +1100, Ben Finney wrote:
> > I was just thinking a link might be useful for folks landing on the
> > LibraryStyleGuide page, but I don't feel strongly about it.
>
> I have written https://wiki.debian.org/BenFinney/software/repack>,
> do you think that is
Hi Gert,
On Tue, Dec 10, 2013 at 12:41:38PM +0100, Gert Wollny wrote:
> I've prepared the new package 'pymia' to close the ITP #694439. I've
> seen that the package python-mia has already been added to the
> debian-med:imaging-development task :). There is also the python 3
> version "python3-mia
Hi folks,
I have commited some packaging for a bioinformatics package arden to
git://anonscm.debian.org/debian-med/arden.git
Since it expects to find its modules under the pretty generic name
"core" I decided to move the modules under
/usr/share/pyshared/arden/core
and tried to patch the
Hi Julian,
On Fri, Feb 07, 2014 at 02:41:10PM +0100, Julian Taylor wrote:
>
> I assume this is a python application and not a library?
It is an application including some private modules which I like to be
compiled into *.pyc.
> don't install into pyshared, its an implementational detail that
Hi folks,
since it worked out pretty well with my more simple question I'm
impudent enough to come up with a more tricky question: I need to
tackle
git://anonscm.debian.org/debian-med/pysam.git
as a predependency of another package but it seems I need to tweek
the build process initially sa
Hi Olivier,
On Fri, Feb 07, 2014 at 06:08:20PM +0100, Olivier Sallou wrote:
>
> You could first try deleting:
>
> 130 from distribute_setup import use_setuptools
> 131 use_setuptools()
>
> if setuptools is already installed.
Patch commited - thanks for the hint.
> > How can I prevent the b
Hi Piotr,
On Mon, Feb 10, 2014 at 12:53:50PM +0100, Piotr Ożarowski wrote:
>
> good that you ask, I will use this opportunity to dispel a myth:
> dh_python* tools (or any other dh_* tool which doesn't have "install" in
> its name AFAIK) do not install files.
>
> dh_python* is not supposed to ins
Hi,
I'm working on python-pysam in the Debian Med team at
git://anonscm.debian.org/debian-med/pysam.git
The package was created nicely until I added an additional binary
package python-pysam-tests covering the test data in a separate file
(since it us usually not needed but might be helpful t
On Tue, Feb 11, 2014 at 09:48:43AM +0100, Piotr Ożarowski wrote:
> [Andreas Tille, 2014-02-11]
> > directory. I can reproduce this behavious by simply deleting the
> > python-pysam-tests paragraph in debian/control.
>
> this part is very important
Obviously.
> >
Hi Piotr,
On Tue, Feb 11, 2014 at 10:21:43AM +0100, Piotr Ożarowski wrote:
> > this part is very important
> >
> > > It seems that there is some problem in dh_python (or a related tool
> >
> > argh! dh_python2 doesn't install files :-P
>
> `echo '/usr/lib/python2.*/*' >> debian/python-pysam.ins
Hi,
I'm trying to package spades[1] and found the following code inside an
__init__.py file:
...
class YAMLObjectMetaclass(type):
"""
The metaclass for YAMLObject.
"""
def __init__(cls, name, bases, kwds):
super(YAMLObjectMetaclass, cls).__init__(name, bases, kwds)
Hi,
I have built the package in pbuilder and wonder why it does not build
in autobuilders. Any clue? The package is maintained at
git://anonscm.debian.org/debian-med/python-pysam.git
Any hint is welcome
Andreas.
- Forwarded message from "Aaron M. Ucko" -
Date: Thu, 20 Feb 20
Hi Jacub,
On Thu, Feb 20, 2014 at 06:44:00PM +0100, Jakub Wilk wrote:
> | running build
> | running build_py
> | creating build
> | creating build/lib.linux-i686-2.7
> | creating build/lib.linux-i686-2.7/pysam
> [...]
> | + env
> PYTHONPATH=/build/python-pysam-fLMqAQ/python-pysam-0.7.5/build/lib.
Hi Piotr,
On Fri, Feb 21, 2014 at 02:42:37PM +0100, Piotr Ożarowski wrote:
> /me continues promoting pybuild:
Thanks for this nice promotion demo - it worked nicely.
Thanks for the patch
Andreas.
PS: What is the best place to read about this in the first place.
--
http://fam-tille.de
Hi,
I tried to work on python-biopython which according to authors request
supports also Python3 and so I tried to put this into the packaging at
svn://anonscm.debian.org/debian-med/trunk/packages/python-biopython/trunk/
The problem is that I seem to have messed up the debian/*.install files
Hi,
On Tue, Mar 04, 2014 at 05:26:51PM +0100, Piotr Ożarowski wrote:
> [Andreas Tille, 2014-03-04]
> > I tried to work on python-biopython which according to authors request
> > supports also Python3 and so I tried to put this into the packaging at
> >
> >
> >
Hi again
On Tue, Mar 04, 2014 at 07:18:08PM +0100, Andreas Tille wrote:
> > you can force pybuild to move BioSQL files to a different location
> > (hint: --ext-dest-dir & --ext-pattern or equivalent PYBUILD_* vars)
> > but IMO it's cleaner to use *.install files
Hi,
On Wed, Mar 05, 2014 at 04:31:22PM +0100, Andreas Tille wrote:
> Besides that the mysterious riddle why the python2 modules all end
> up in the python3 packages and vice versa is not solved yet and I
> have no idea why this happens since this
>
> $ grep Bio debian/*.install
&
On Wed, Mar 12, 2014 at 01:20:38AM -0400, Éric Araujo wrote:
> Le 05/03/2014 10:31, Andreas Tille a écrit :
> >I have noted another problem: I worked a bit
> >on the tests and noticed that those tests that are including compiled C
> >code are failing. Is there anything in
Hi Éric,
On Fri, Mar 14, 2014 at 07:15:26PM -0400, Éric Araujo wrote:
> There are two ways to fix that: either make distutils build the
> extensions alongside the Python modules, or make the test import all
> code from the build directory. I’m surprised that this isn’t a
> common issue for PMPT
Hi Piotr,
On Sat, Mar 15, 2014 at 12:52:41PM +0100, Piotr Ożarowski wrote:
>
> pybuild takes care of "distutils cannot find files it build in previous
> step and has to build them again" problem. I just checked
> python-biopython and all .so files are in the right location
> (yey pybuild! :).
>
Hi,
I have started anyother try to finalise BioPython which is prepared at
Vcs-Svn:
svn://anonscm.debian.org/debian-med/trunk/packages/python-biopython/trunk/
I try to run as much tests of the test suite as possible in the build
process and I also added autopkgtest based on upstream's unit te
On Fri, Apr 25, 2014 at 10:57:33AM +0200, Etienne Millon wrote:
>
> LC_ALL=C.UTF-8 dh_auto_tests -- ...
Works!
Thanks a lot for this really helpful hint
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe
Hi,
as I wrote in my last mail I have started anyother try to finalise
BioPython which is prepared at
Vcs-Svn:
svn://anonscm.debian.org/debian-med/trunk/packages/python-biopython/trunk/
I hope the final problem with the tests is that I get output like
test_GraphicsBitmaps ... skipping. In
Hi,
On Fri, Apr 25, 2014 at 03:05:42PM +0200, Andreas Tille wrote:
> Hi,
>
> as I wrote in my last mail I have started anyother try to finalise
> BioPython which is prepared at
>
>Vcs-Svn:
> svn://anonscm.debian.org/debian-med/trunk/packages/python-biopython/trunk/
[Debian Python Modules Team in CC
since it maintains python-reportlab]
Hi again,
On Fri, Apr 25, 2014 at 03:32:21PM +0200, Andreas Tille wrote:
> >
> > test_GraphicsBitmaps ... Warn: Can't find .pfb for face 'Times-Roman'
> > skipping. Check the fonts needed
Hi,
On Sat, Apr 26, 2014 at 09:12:45PM +0200, Jakub Wilk wrote:
> * Andreas Tille , 2014-04-25, 16:08:
> >[Debian Python Modules Team
> > in CC since it
> >maintains python-reportlab]
>
> ITYM s/maintains/is in Uploaders of/. It makes a big difference here...
Does th
Hi,
On Mon, Apr 28, 2014 at 03:39:59PM +0200, Jakub Wilk wrote:
> >>ITYM s/maintains/is in Uploaders of/. It makes a big difference
> >>here...
> >
> >Does this mean that not any member of the team could upload a
> >fixed package?
>
> I don't know that. What I know is that there were no commits t
Hi Jamie,
thanks for your bug report. I think this should work out of the box but
I personally not comfortable with cpython to know how this could be
fixed. I keep the Debian Python list in CC - perhaps they might have
some helpful advise.
It seems this module is not affected by the test suite
Hi Jamie,
On Sat, May 10, 2014 at 09:22:29AM +1200, Jamie Norrish wrote:
> >
> > from .cpairwise2 import rint, _make_score_matrix_fast
> >
> > should do the trick.
>
> Indeed. This was actually reported and fixed a couple of months ago
> upstream[1]; I foolishly didn't check the closed bugs
Hi,
I intend to update python-biom-format which is maintained at
svn://anonscm.debian.org/debian-med/trunk/packages/python-biom-format/trunk/
Unfortunately the new version has a problem when it comes to build the
documentation. Either does not find the biom Python module or since
I adapted t
Hi Jakub,
On Tue, May 20, 2014 at 11:24:11PM +0200, Jakub Wilk wrote:
> >
> > svn://anonscm.debian.org/debian-med/trunk/packages/python-biom-format/trunk/
>
> (Unrelated to your question:) Since you are already repacking
> .orig.tar, please get rid of these files:
>
> biom-format-2.0.0/biom/_f
On Wed, May 21, 2014 at 12:12:37PM +0200, Jakub Wilk wrote:
> * Andreas Tille , 2014-05-21, 09:52:
> >>> svn://anonscm.debian.org/debian-med/trunk/packages/python-biom-format/trunk/
> >>
> >>(Unrelated to your question:) Since you are already repacking
> >&g
Hi,
sorry for the confusion.
On Wed, May 21, 2014 at 01:02:23PM +0200, Jakub Wilk wrote:
> * Piotr Ożarowski , 2014-05-21, 11:14:
> >>
> >> svn://anonscm.debian.org/debian-med/trunk/packages/python-biom-format/trunk/
> >>
> >>Unfortunately the new version has a problem when it comes to
> >>buil
Hi Jakub,
On Wed, May 21, 2014 at 03:38:36PM +0200, Jakub Wilk wrote:
> I strongly recommend rebuilding everything from source.
With my latest commit I'm recreating the *.c files using cython.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-python-req
Hi,
On Wed, May 21, 2014 at 03:33:22PM +0200, Jakub Wilk wrote:
>
> With the attached patch I got the package almost building. Almost,
> becasue the tests fail:
Just to let you know: The package requires a new versioned
Build-Depends pyqi (>= 0.3.2) which I just uploaded.
Thanks for your help
Hi Gianfranco,
On Sat, Jul 05, 2014 at 10:41:09AM +0100, Gianfranco Costamagna wrote:
> Hi Andreas, thanks for doing this!
>
> I propose also to change the maintainer if you think is better, don't know ;)
IMHO the maintainer should be a team (either Debian Science or Debian
Python) and it seems
Hi Aidan,
I wonder whether you considered providing a patch for this problem.
In any case I CCed Debian Python list.
Thanks for any help
Andreas.
On Tue, 8 Apr 2014 16:46:39 +0200 Andreas Tille wrote:
> Hi Aidan,
>
> thanks for your bug report.
>
> Could you possib
Hi,
I tried to use dicompyler and followed the hint I had received in a
similar case[1] and used:
DEBPKGNAME := $(shell dpkg-parsechangelog | awk '/^Source:/ {print $$2}')
export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/$(DEBPKGNAME)
--install-scripts=/usr/share/$(DEBPKGNAME)
Unfortuna
Hi,
I'm trying to upgrade dicompyler[1] but I seem to have some final
problem:
$ dicompyler
Traceback (most recent call last):
File "/usr/share/dicompyler/dicompyler_app.py", line 10, in
import dicompyler.main
File "/usr/share/dicompyler/__init__.py", line 10, in
from main import st
Hi Piotr,
On Wed, Sep 10, 2014 at 04:03:40PM +0200, Piotr Ożarowski wrote:
>
> if you install your script to the same directory as the application¹ then
> all you need is `dh_link /usr/bin/foo /usr/share/pkgname/foo` in
> debian/rules or adequate line in debian/pkgname.links file.
> No need to wr
Hi Piotr,
On Wed, Sep 10, 2014 at 07:09:37PM +0200, Piotr Ożarowski wrote:
> [Andreas Tille, 2014-09-10]
> > Copying dicompyler.egg-info to
> > /tmp/buildd/dicompyler-0.4.2/debian/dicompyler/usr/share/dicompyler/dicompyler-0.4.2.egg-info
> > running install_scripts
>
Hi,
On Thu, Sep 11, 2014 at 10:30:42AM +0200, Piotr Ożarowski wrote:
> [Andreas Tille, 2014-09-11]
> > pkg_resources.DistributionNotFound: pil>=1.1.7
>
> python{,3}-pil provides Pillow egg-info
> Matthias: should python-imaging provide pil.egg.info file (for older
> lib
Hi,
I tried to upgrade python-pysam[1] but the build endet in a failed test
suite:
LC_ALL=C.UTF-8 dh_auto_test -- --test --system=custom \
--test-args='set -e; \
cp -a /tmp/buildd/python-pysam-0.8.0/tests
{build_dir}/tests ; \
cd {build_dir}/tes
Hi,
in Git[1] I tried to implement the additional hint from upstream
https://github.com/pysam-developers/pysam/issues/34
but this does not change anything. :-(
Any further help would be welcome
Andreas.
On Thu, Sep 25, 2014 at 02:48:25PM +0200, Andreas Tille wrote:
> Hi,
>
Ups, sorry, done. Andreas.
On Thu, Sep 25, 2014 at 03:32:49PM +0200, Gert Wollny wrote:
> Hi Andreas,
>
>
> I tried to have a look, but ...
>
>
> On Thu, 2014-09-25 at 14:48 +0200, Andreas Tille wrote:
> > [1] git://git.debian.org/git/debian-med/python-pysam.git
d this.
Kind regards
Andreas.
> [1]http://web.archiveorange.com/archive/v/WK9riEUrSSGTqb90VM4v
>
>
> On Thu, 2014-09-25 at 16:22 +0200, Andreas Tille wrote:
> > Ups, sorry, done. Andreas.
> >
> > On Thu, Sep 25, 2014 at 03:32:49PM +0200, Gert Wollny wrote:
Hi Jorge,
On Thu, Oct 09, 2014 at 10:27:55AM +0100, Jorge Sebastião Soares wrote:
> > > I think I'm going to delete the fastaq.git project on git alioth and
> > create
> > > a new project. Since the code is python3 only I will call it
> > python3-fastaq.
> >
> > Regarding the name: If it is an *a
Hi,
I realised that python-hl7 is not uploaded since December 2011. I tried
to add myself to uploaders and commit to the Python Modules team SVN but
it seems ACLs are not set to give Debian developers write permissions.
Since we need to be quick if we want to meet the freeze date with the
latest
Hi,
I try to package python-ruffus on behalf of the Debian Med team at
git://anonscm.debian.org/debian-med/python-ruffus.git
Unfortunately I have trouble running the test suite. I tried two
ways to run it:
override_dh_auto_test:
### No idea why this fails :-(
# LC_ALL=C.UTF-8 dh_auto_
Hi,
I intent to package python MISO on behalf of the Debian Med team. The packaging
code is in SVN at
Vcs-Svn: svn://anonscm.debian.org/debian-med/trunk/packages/python-miso/trunk/
It builds and runs the test suite but I'd like to drop the lapack code copy.
I have not found any chance to con
done some investigations (svn up) to drop at least
f2c and has added a remark about lapack in d/README.source. Some
dynamic linking of f2c would help enhancing the package as well.
Kind regards
Andreas.
> 2015-02-16 13:59 GMT+00:00 Andreas Tille :
>
> > Hi,
> >
> > I intent
Hi,
I'm working on python-ruffus (current work not commited to Git since
upstream is preparing a new version - I'm fine to inject Beta to Git if
the abstract description of the problem is not sufficient). Upstream
said it works with tox and thus I tried in debian/rules:
export PYBUILD_TEST_TOX=
Hi Barry,
On Tue, Mar 10, 2015 at 09:56:24AM -0400, Barry Warsaw wrote:
> On Mar 10, 2015, at 01:32 PM, Andreas Tille wrote:
>
> >export PYBUILD_TEST_TOX=1
>
> I'm not sure what's going on in your specific example, but in general I've
> found it less proble
Hi,
I'd like to package python-matplotlib-venn since a Debian Med package
depends from this module. I injected the packaging to
svn://anonscm.debian.org/debian-med/trunk/packages/python-mathplotlib-venn/trunk/
Unfortunately I'm running into:
.pybuild/pythonX.Y_2.7/build/matplotlib_venn/_co
Hi,
I have commited some initial packaging attempt for python-dendropy
Vcs-Git: git://anonscm.debian.org/debian-med/python-dendropy.git
but the clean target fails and I have no idea why:
...
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:170: python2.7 setup.py clean
Traceback (mos
Hi,
I tried to add build-time tests for python-pysam[1]. I admit I'm a bit
confused about the fact that this involves compiler calls like:
...
warning: no files found matching 'tests/tabix_data'
writing manifest file 'pysam.egg-info/SOURCES.txt'
skipping 'pysam/csamtools.c' Cython extension (up-
Hi Afif,
On Thu, Jul 16, 2015 at 10:57:17PM -0700, Afif Elghraoui wrote:
> Hi, Andreas,
>
> On الأربعاء 15 تـمـوز 2015 05:21, Andreas Tille wrote:
> >Hi,
> >
> >I tried to add build-time tests for python-pysam[1]. I admit I'm a bit
> >confused about the
Hi Bas,
On Mon, Jul 20, 2015 at 11:06:22AM +0200, sebastic wrote:
> On 2015-07-20 10:54, Andreas Tille wrote:
> >unfortunately I did not got any response from Debian Python team and
> >I'm simply lost how to run the tests.
>
> Maybe change the dh_auto_test
Hi Piotr,
thanks for your quick help!
On Tue, Jul 21, 2015 at 05:29:18PM +0200, Piotr Ożarowski wrote:
> [Piotr Ożarowski, 2015-07-21]
> > export PYBUILD_TEST_NOSE=1
>
> if tests are not installed, add also:
>
> export PYBUILD_TEST_ARGS={dir}/tests
While it looks a lot more elegant if I do
1 - 100 of 576 matches
Mail list logo
