Hi Julian,
On 05/01/2014 12:39 AM, Julian Taylor wrote:
On 30.04.2014 22:56, Alex Mestiashvili wrote:
Greetings everybody,
git-buildpackage --git-pbuilder --git-arch=amd64
dh clean --with python2,python3 --buildsystem=pybuild
dh_testdir -O--buildsystem=pybuild
dh_auto_clean
2014-04-30 19:27 GMT+02:00 Jakub Wilk jw...@debian.org:
This tag doesn't catch indirect use of python-support, via dh or cdbs. The
actual number of affect packages is much higher.
Indeed, I erroneously thought it considered build dependencies as well.
I'll propose a new check to take into
On April 30, 2014 1:15:42 PM EDT, Dimitri John Ledkov x...@debian.org wrote:
On 30 April 2014 18:01, Matthias Klose d...@debian.org wrote:
Am 30.04.2014 17:31, schrieb Luca Falavigna:
Hi,
python-central is gone (\o/) and python-support usage is slowly
decreasing in the archive:
On May 01, 2014, at 07:15 AM, Scott Kitterman wrote:
If PEP 404 is ever update to actually release, then it would be
reasonable to expect/demand for PEP 3147 to be implemented / included.
Don't worry, it won't (PEP 404 that is).
-Barry
--
To UNSUBSCRIBE, email to
Hello,
In a particular project (django-model-utils 2.0.3 to be precise), if I have
a debian/rules file containing:
%:
dh $@ --with python2
Then dh_auto_* tools determine that the project comes with a Makefile
(upstream file), and uses that instead of setup.py
How can I force it to use
Hello,
Several times I have made the mistake of building a Debian package while a
virtualenv is active. This results in the paths being incorrect in the
Debian package. Sometimes the package build will fail as a result, this
depends on the package.
Fortunately, so far I have always noticed this
On 2014-05-02 02:48, Brian May wrote:
In a particular project (django-model-utils 2.0.3 to be precise), if I
have a debian/rules file containing:
%:
dh $@ --with python2
Then dh_auto_* tools determine that the project comes with a Makefile
(upstream file), and uses that instead
On 2 May 2014 11:14, Christian Kastner deb...@kvr.at wrote:
%:
dh $@ --with python2 --buildsystem=python_distutils
See also section BUILD SYSTEM OPTIONS of debhelper(7).
Just what I wanted. Thanks.
I did see this in the debhelper(7) man page, but got confused when it
wasn't
Brian May br...@microcomaustralia.com.au writes:
Several times I have made the mistake of building a Debian package
while a virtualenv is active. This results in the paths being
incorrect in the Debian package.
The best way to avoid this is to always use a build tool which builds
the package
Hi Team,
I am looking for a sponsor for my package and maitain it with the DPMT.
The package is python-twython Pure Python wrapper for the Twitter API.
This closes #739010 which is an ITP.
Here is some useful information about the package:
Version : 3.1.2-1
Upstream Author : Ryan McGrath
Hi Brian,
Fortunately, so far I have always noticed this before uploading the
package, however think it is only a matter of time before I stuff up an
upload.
While not directly addressing your question, perhaps this is also a good
opportunity to add some autopkgtest tests to the packages --
11 matches
Mail list logo
