Uploaded and tagged, thanks!
--
WBR, wRAR
signature.asc
Description: Digital signature
On Fri, Apr 25, 2014 at 03:05:25PM -0300, Thiago Franco Moraes wrote:
Hi all,
I'm one of developer of InVesalius [1], an open source medical software.
InVesalius is already packaged to Debian thanks to Debian med. Now I'm
updating the package [2] to the last release of InVesalius.
Until
On Tue, Feb 04, 2014 at 06:35:56PM +0800, Thomas Goirand wrote:
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
Since it is team maintained, I don't think it really makes sense. Should
we just close the bug report and remove Sandro
On Tue, Oct 08, 2013 at 12:52:35PM +0800, Thomas Goirand wrote:
Though probably writing in this bug would
have been more efficient than writing in the topic of the IRC channel?
Yes, that's my only mistake.
Though of course it's a fundamental problem with non-DD packages: I've
made a package I
On Fri, Sep 20, 2013 at 04:17:25PM -0700, Thomas Kluyver wrote:
Packaging often takes much longer than a couple of days, especially if the
packager is not experienced. And when the work is published somewhere, but
not yet uploaded, there is no general way to know if it's published and
On Sat, Sep 21, 2013 at 07:02:59AM +0200, Antoine Musso wrote:
I find the ITP/wnpp annoying as well. I usually end up browsing
http://www.debian.org/devel/wnpp/ , opening all links then searching for
my package :-]
I use Google for this.
--
WBR, wRAR
signature.asc
Description: Digital
On Sat, Sep 21, 2013 at 08:50:46AM +0200, Etienne Millon wrote:
I find the ITP/wnpp annoying as well. I usually end up browsing
http://www.debian.org/devel/wnpp/ , opening all links then searching
for my package :-] I then bootup an instance and try to remember
to report the bug against
On Sat, Sep 21, 2013 at 04:36:23PM +1000, Ben Finney wrote:
I keep forgetting filling an ITP. It is usually caught on final review
because for some reason lintian is not being run by default by my
packaging chain :-(
For ‘pbuilder’, you can add a hook that automatically runs Lintian on
Hello.
I'm packaging a new version of python-babel and as it now builds 2.x and
3.x packages I decided to move the locale data into /usr/share and package
it separately. Currently the data is installed using 'package_data'
setup() argument and accessed via os.path.dirname(__file__). I've added
On Fri, Sep 20, 2013 at 03:44:05PM -0700, Thomas Kluyver wrote:
That seems like an unlikely problem in real world cases - how often will
two people decide to package the same, currently unpackaged, piece of
software, within the couple of days or so before the first one publishes
their work.
On Fri, Aug 02, 2013 at 03:15:36PM +0200, Piotr Ożarowski wrote:
Note that adding dh-python to Build-Depends enables multiarch support in
dh_python2
What does this change exactly?
--
WBR, wRAR
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe.
On Tue, Jun 18, 2013 at 08:09:33PM +0200, B. Clausius wrote:
I am packaging Pybik 1.1 that uses python3-pyicu. python3-pyicu is in
Ubuntu, but not in Debian (bug #671361). What should i do?
1. Just Recommends: python3-pyicu and rely the package is coming sometime
2. Recommends: python3-pyicu
On Mon, Feb 25, 2013 at 09:29:05PM +0100, Sandro Tosi wrote:
My understanding was that package has Debian Python Team set as
maintainer, such that improvements and co-maintainership is welcomed.
and they are, but switching python helper or introducing a new package
are huge changes enough to
On Fri, Dec 14, 2012 at 06:36:42PM +0100, Jakub Wilk wrote:
* Tomás Di Domenico td...@tdido.com.ar, 2012-12-11, 19:41:
I'm trying to get the docs for my python-csb package to build from
source. I've declared the binary package in debian/control along
with the dependency to python-epydoc (=
On Tue, Dec 11, 2012 at 10:00:03PM +0100, Christoph Mathys wrote:
I try to package mercurial-keyring. However, if I build the binary
package and then try to build the source package, this process fails
because SOURCES.txt has been modified by the binary package build.
Apparently, dh_python2
On Thu, Nov 15, 2012 at 11:17:40AM +, Thomas Kluyver wrote:
I have been keeping an eye on pkgme, but I'm not sure it solves the
problem. My concern with automated tools is that they tend to to work for
about 75% of stuff, but there's always a substantial proportion of things
that just do
On Tue, May 29, 2012 at 11:21:37AM +0200, Toni Mueller wrote:
After switching python-defaults to python2.7, I'm not sure we discussed
whether to keep python2.6 for Wheezy or not. In theory, we should be able
to
get rid of python2.6 in time for the release (I'd likely be able to act as
Package: wnpp
Severity: wishlist
Owner: Andrey Rahmatullin w...@wrar.name
* Package name: ipdb
Version : 0.6
Upstream Author : Godefroid Chapelle got...@bubblenet.be
* URL : http://pypi.python.org/pypi/ipdb
* License : GPL
Programming Lang: Python
Some results for popular modules:
http://wiki.debian.org/AndreyRahmatullin/PythonTests
--
WBR, wRAR
signature.asc
Description: Digital signature
Hello.
Many Python modules ship unit tests which do not require module
instalation or user interaction and so can be run automatically during the
build time. They can be a very good QA tool, but it looks like they are
not used in all packages.
python-pylons: not used
python-pybabel: not used
On Tue, Feb 22, 2011 at 11:17:47AM -0500, Scott Kitterman wrote:
It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
and didn't run 'make test' in that case, so that the
override_dh_auto_test wasn't necessary. Yah, I should create a bug and
patch for that.
I
On Tue, Feb 22, 2011 at 09:47:20AM -0500, Barry Warsaw wrote:
It would be nice if dh auto-detected a setup.py (and/or missing Makefile) and
didn't run 'make test' in that case, so that the override_dh_auto_test wasn't
necessary. Yah, I should create a bug and patch for that.
Note that tests
On Tue, Feb 22, 2011 at 07:23:51PM +0100, Vincent Bernat wrote:
I wasn't aware of the existence of a test target.
It's a setuptools feature if I understand correctly
(setuptools.command.test) and it needs specific test* arguments to
setup(). Not all modules support it, some have custom
On Fri, Oct 29, 2010 at 08:19:36PM +0200, Tshepang Lekhonkhobe wrote:
I have a lot of packaging experience for ALT Linux and some experience
with Python programming, but no experience with Debian Python packaging (I
have some understanding of general Debian packaging). I want to help with
Hello.
I have a lot of packaging experience for ALT Linux and some experience
with Python programming, but no experience with Debian Python packaging (I
have some understanding of general Debian packaging). I want to help with
Python in Debian, what can I do?
--
WBR, wRAR
signature.asc
201 - 225 of 225 matches
Mail list logo
