* Brian Sutherland br...@vanguardistas.net, 2012-05-10, 10:36:
AFAIK, the problem is double build failures because dpkg detects that
there are leftovers/changes from the first build. You end up with
failures when a second build is attempted [1].
This leads people to use workarounds like
On Thu, May 10, 2012 at 12:07:28PM +0200, Jakub Wilk wrote:
* Brian Sutherland br...@vanguardistas.net, 2012-05-10, 10:36:
AFAIK, the problem is double build failures because dpkg detects
that there are leftovers/changes from the first build. You end up
with failures when a second build
Hi!
I got some bug reports from Jakub about double build failures. I have
always found those kind of tests a bit silly, but that's just my
opinion.
Most of the time, the failures are because of the created egg directory
that is not cleaned up by the clean target of setup.py. While
On 04/05/12 18:05, Vincent Bernat wrote:
Hi!
I got some bug reports from Jakub about double build failures. I have
always found those kind of tests a bit silly, but that's just my
opinion.
Most of the time, the failures are because of the created egg directory
* Vincent Bernat ber...@debian.org, 2012-05-04, 19:05:
I got some bug reports from Jakub about double build failures. I have
always found those kind of tests a bit silly, but that's just my
opinion.
Most of the time, the failures are because of the created egg directory
that is not cleaned
On Fri, May 4, 2012 at 7:19 PM, Jakub Wilk jw...@debian.org wrote:
or in setuptools.
Ideally, by burning it with fire.
CPython upstreams are developing a new module to replace distutils and
setuptools: packaging. It might be worth check with them if it will
handle this case.
Regards,
--
On Fri, 04 May 2012, Dmitrijs Ledkovs wrote:
Most of the time, the failures are because of the created egg directory
that is not cleaned up by the clean target of setup.py. While I could
add the appropriate bits to each clean target in debian/rules, it seems
better to fix the
On 04/05/12 18:23, Sandro Tosi wrote:
On Fri, May 4, 2012 at 7:19 PM, Jakub Wilk jw...@debian.org wrote:
or in setuptools.
Ideally, by burning it with fire.
CPython upstreams are developing a new module to replace distutils and
setuptools: packaging. It might be worth check with them if it
* Yaroslav Halchenko deb...@onerussian.com, 2012-05-04, 13:29:
Most of the time, the failures are because of the created egg
directory that is not cleaned up by the clean target of setup.py.
While I could add the appropriate bits to each clean target in
debian/rules, it seems better to fix the
On Friday, May 04, 2012 06:38:30 PM Dmitrijs Ledkovs wrote:
On 04/05/12 18:23, Sandro Tosi wrote:
On Fri, May 4, 2012 at 7:19 PM, Jakub Wilk jw...@debian.org wrote:
or in setuptools.
Ideally, by burning it with fire.
CPython upstreams are developing a new module to replace distutils
On 04/05/12 19:04, Scott Kitterman wrote:
On Friday, May 04, 2012 06:38:30 PM Dmitrijs Ledkovs wrote:
On 04/05/12 18:23, Sandro Tosi wrote:
On Fri, May 4, 2012 at 7:19 PM, Jakub Wilk jw...@debian.org wrote:
or in setuptools.
Ideally, by burning it with fire.
CPython upstreams are
On 4 May 2012 19:06, Dmitrijs Ledkovs x...@debian.org wrote:
ok. what is the relationship between 'distribute' 'packaging'?
Let's see if I get all these right:
distutils: basic packaging functionality, part of the Python standard library
setuptools: third party module to add functionality that
On May 04, 2012, at 07:16 PM, Thomas Kluyver wrote:
On 4 May 2012 19:06, Dmitrijs Ledkovs x...@debian.org wrote:
ok. what is the relationship between 'distribute' 'packaging'?
Let's see if I get all these right:
distutils: basic packaging functionality, part of the Python standard library
On Fri, 04 May 2012, Jakub Wilk wrote:
* Yaroslav Halchenko deb...@onerussian.com, 2012-05-04, 13:29:
Most of the time, the failures are because of the created egg
directory that is not cleaned up by the clean target of
setup.py. While I could add the appropriate bits to each clean
target
14 matches
Mail list logo
